ETSITS102744-3-2V1.1.1: Satellite Earth Stations and Systems - Bearer Control Layer

需积分: 5 153 浏览量更新于2024-06-14 收藏 675KB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"ts-1027440302v010101p.pdf" 本文档是ETSI（欧洲电信标准协会）发布的技术规范，标题为"ETSITS102744-3-2V1.1.1(2015-10)"，主要涉及卫星地球站和系统（SES）中的家庭卫星广播接口（Family L-SATellite Radio Interface，简称Family SLS或FSL）的第3部分：控制平面和用户平面的规范，特别是第2子部分：承载控制层操作。这份文档在2015年10月进行了版本更新。关键词包括3GPP、GPRS、GSM、GSO、接口、MSS、无线电、卫星、TDM、TDMA以及UMTS，这些术语反映了该规范涵盖的多个通信领域和技术。3GPP代表第三代合作伙伴计划，是制定移动通信标准的组织；GPRS（通用分组无线服务）和GSM（全球系统 for 移动通信）是2G和2.5G移动通信技术；GSO（地球静止轨道）是指卫星在地球上方特定位置保持静止的轨道；MSS（移动卫星系统）涉及卫星通信网络；无线电技术则与信号传输有关；TDM（时分复用）和TDMA（时分多址）是频谱利用率高的多路复用技术；UMTS（通用移动通信系统）是3G移动通信标准。文档的主要内容可能包括： 1. **控制平面和用户平面规范**：这部分详细定义了卫星通信系统中控制层面和用户层面的操作流程和协议，这涉及到数据传输的管理和用户服务的建立、维护和终止。 2. **承载控制层操作**：承载控制层是通信系统中的一个重要组成部分，它负责管理数据传输的通道，确保数据的正确路由和高效传输。这一部分可能涵盖了信令过程、错误检测和纠正机制、资源分配策略等。 3. **3GPP、GPRS和UMTS的卫星扩展**：由于关键词中包含了3GPP的相关技术，可以推断文档可能描述了如何将3G和3G+技术扩展到卫星通信环境，以便在地面网络覆盖不到的地方提供连续的服务。 4. **接口和协议**：文档可能会定义MSS与其他系统（如地面网络、其他卫星系统）之间的接口，以及相关的通信协议，如GSM和GPRS的卫星版本。 5. **TDM和TDMA的应用**：这些多路复用技术在卫星通信中用于管理多个用户的并发连接，可能在文档中详细解释了如何在卫星链路中实现它们。 6. **GSO卫星的运行**：可能包含关于如何在地球静止轨道上部署和操作卫星的详细信息，包括轨道位置、频率分配、功率控制等方面。 7. **法律和合规性**：ETSI标准通常会考虑法规遵从性，因此文档可能也包含了符合相关国家和地区法律法规的指南。这份技术规范对于设计、开发、测试和维护卫星通信系统，尤其是那些依赖于家庭卫星广播接口的系统，具有重要意义。它为业界提供了统一的标准，确保不同设备和服务之间的互操作性，从而促进全球卫星通信网络的发展和优化。

资源详情

资源推荐

ETSI

ETSI TS 102 744

2 V1.1.1 (2015

10)

The BCt_TM_SECURITY_REQ primitive is used by the Bearer Connection Layer to configure the ciphering

parameters for all Transparent Mode connections. The Bearer Control Layer shall configure the specified TM

connections with the corresponding CK and START parameters at the specified UL and DL Activation Time. Once all

the TM connections are set up, the BCt_TM_SECURITY_CNF shall be returned to the Bearer Connection Layer. Any

failure to configure any connection shall be reported via the BCt_TM_SECURITY_REJ primitive with the

corresponding Rejection Cause code.

The BCt_CONFIGURE_IND primitive is sent to the Connection Layer when a BCt AVP is received that is specified to

set a variable in the Connection Layer.

5.2.3.2 BCt-COM-SAP Primitives and Parameters

The BCt-COM-SAP is used for the transfer of Common Signalling data between Bearer Connection and Control layer.

The BCt-COM-SAP primitives are shown in Table 5.6.

Table 5.6: BCt-COM-SAP Primitives

Primitive

Direction

Parameters

BCt_TxCOMSIG_REQ

To BCt UE_ID-type, UE_NAS_ID, DataSize, AL-ComPDU

BCt_TxCOMSIG_IND To BCn DataSize

BCt_RxCOMSIG_IND To BCn UE_ID-type, UE_NAS_ID, DataSize, AL-ComPDU

The Common BCt Manager (COM_BCt_M) uses the BCt_TxCOMSIG_IND primitive to indicate the capacity

available for the Common Signalling connection in the current frame to the Connection layer. The data handler

(COM_DH) in the connection layer will respond by sending the address (UE_ID-type and UE_NAS_ID) and data

(AL-ComPDU) to be sent using a BCt_TxCOMSIG_REQ signal. On the receive side, Common Signalling messages

are delivered to the Adaptation / Connection Layer via the BCt_RxCOMSIG_IND primitive.

5.2.3.3 CBCt-SAP Primitives and Parameters

The CBCt-SAP is used by the Adaptation Layer to acquire a PSAB, GPS position data and System Information from

the Bearer Control Layer. The CBCt-SAP primitives are shown in Table 5.7.

Table 5.7: CBCt-SAP Primitives

Primitive

Direction

Parameters

CBCt_DISCOVER_REQ To BCt ALPD, Global Discover Flag, SEQUENCE OF

{PSAB Information}

CBCt_DISCOVER_CNF From BCt ALPD, PSAB Information

CBCt_DISCOVER_REJ From BCt ALPD, Rejection Cause

CBCt_POSITION_REQ

To BCt ALPD

CBCt_POSITION_CNF From BCt ALPD, UE GPS Position

CBCt_POSITION_REJ

From BCt ALPD, Rejection Cause

CBCt_SYSTEM_INFORMATION_IND From BCt ALPD, SEQUENCE OF {System Info Index

Version, System Information AVP/SDU Set}

CBCt_AERO_HPA_REQ From BCt ALPD, Requested Power

CBCt_AERO_HPA_CNF To BCt ALPD, Allocated Power

CBCt_AERO_HPA_REJ To BCt ALPD

CBCt_AERO_HPA_IND From BCt ALPD, Returned Power

REGM from the AL will request the BCt layer to find and camp on the identified PSAB by using the

CBCt_DISCOVER_REQ primitive. Where more than one PSAB is indicated, REGM requests the BCt layer to select

and camp on the most suitable PSAB in the list. When successful, the BCtM confirms that it has camped on the

identified PSAB via the BCt_DISCOVER_CNF message. Otherwise, the BCt layer indicates that it cannot find or camp

on any of the identified PSABs using the CBCt_DISCOVER_REJ primitive.

CBCt_POSITION_REQ is used by REGM at the Adaptation layer to request the UE GPS position data from the BCtM.

If available, the BCtM will pass the UE GPS position data to REGM using the CBCt_POSITION_CNF message.

Otherwise, the CBCt_POSITION_REJ message is used to signal failure and specified reason. The

BCt_SYSTEM_INFORMATION_IND message is used by the BCtM to pass received System Information with

Adaptation Layer scope to REGM. The BCtM includes the version number corresponding to each broadcast System

Information element (i.e. a set of AVPs or SDUs of a particular type).

ETSI

ETSI TS 102 744

2 V1.1.1 (2015

10)

- System Information Broadcast Handling unit

- Timing Control

- Physical Bearer Management

- Common Signalling handling (COM_BCt) in the unit

• Connection and Bearer specific UE Bearer Control (UE_BCt) comprising:

- Ciphering Function

- Queue Status Reporting

- Return Scheduling Processing

- Transmit Burst Assembly

- Bearer_Tx buffer

- Bearer_Rx buffer

6.2.1 Bearer Control Manager (BCtM)

6.2.1.0 General

The Bearer Control Manager (BCtM) provides the main management interface to the Connection Layer above and to

the physical layer below. It receives commands from the Connection Layer (via STATUS-SAP) to create or destroy

bearer control units for each UE (UE_BCt). It also creates one data SAP (either BCt-DATA-SAP or BCt-UCDATA-

SAP) for each bearer connection belonging to a UE, and associates it with the corresponding UE_BCt.

The BCtM also receives the queue status for each bearer connection via the STATUS-SAP. These will be passed to the

Scheduling Control unit so that the resource usage can be determined. The BCtM will use the output of the Scheduling

Control unit to determine when each UE_BCt will get the allocated resources.

The BCtM is responsible for receiving broadcast BCt PDUs and return schedules and uses them to configure the

different bearers it is using. System Information is delivered to the AL via the CBCt-SAP. The CBCt-SAP is also used

by the AL to start the search for the Primary Shared Access Bearer (PSAB).

The other functions BCtM include Timing control mechanisms for the mobile terminal.

6.2.1.1 System Information Broadcast Handling Unit

The RNC broadcasts a number of information elements to all UE in order to control how they access the system. The

System Information Broadcast Handling unit is responsible for receiving and decoding this system information. It will

maintain up-to-date system information and is stored in the BCtM for further use.

The Adaptation Layer specific System Information and NAS specific System Information is passed onto the Adaptation

Layer for their use.

Any updates to the System Information will be notified by the RNC using the System-Info-Index SDU, in which case

the UE will reacquire the modified system information.

This unit will keep an up to date record of all the system information.

6.2.1.2 Common Signalling Handler (COM_BCt)

The Common Signalling Handler (COM_BCt) manages the common signalling channel and interfaces to the

Connection Layer via the BCt-COM-SAP. The architecture for the COM_BCt is illustrated in Figure 6.2. The Common

Signalling Manager (COM_BCt_M) is responsible for handling all AVPs associated with the Common Signalling

Channel.

ETSI

ETSI TS 102 744

2 V1.1.1

(2015

10)

6.2.2.2 Queue Status Reporting

The Queue Status Reporting functional entity is responsible for generating reporting of queue status to the RNC for

each connection. The behaviour for queue reporting is dependent upon both the type of Radio Access Bearer (RAB)

connection and the type of signalling specified by the RNC, for instance the following applies:

1) Transparent RABs (for CS voice and ISDN) - no queue status reporting

2) Streaming RABs - queue status reporting periodically only during periods of inactivity

3) Interactive and Background RABs and UE signalling connection - queue status reporting for change of queue

length or change in data rate requirement

4) Common signalling - no queue status reporting

The queue status signalling mechanisms include a Status SDU, for which there is a Status Ack (the Queue Status

Reporting entity being responsible for tracking the association between Status SDU and Status Ack); and

unacknowledged QueueLen and QueueRate SDUs used if instructed by the RNC and supported by the mobile terminal.

The Queue Status Reporting function will generate queue status reports for processing by the Transmit Burst Assembly

function when an opportunity to transmit next arises.

6.2.2.3 Return Schedule Processing

The Return Schedule Processing functional entity interprets the received Return Schedules and any Broadcast AVPs to

determine the opportunity to send in any time-slot. It is responsible for creating a local description of the slots available

for communication by the mobile terminal over a specific return scheduling period, and determines the frequency,

timeslot and the bearer-type to be used.

The description of the time plan includes four categories of slots:

1) UE Specific Reserved Slots

2) Shared Reservation Slots

3) Controlled Random Access Slots

4) Contention Slots

There are strict rules for utilization of these slots within the mobile terminal, these rules being handled within the

Transmit Burst Assembly process.

6.2.2.4 Transmit Burst Assembly

The Transmit Burst Assembly function controls the transmissions from the mobile terminal in the return direction, using

the information provided by the Return Schedule Processing entity which describes the opportunities for the mobile

terminal to transmit.

This entity then determines which of the connections (Common signalling, UE Specific Signalling Connection or Data

Connection(s)) are allowed to transmit in each time-slot and constructs the bursts for transmission.

The Transmit Burst Assembly function is responsible for prioritizing information to send within each burst, and

considers the following requests:

1) Common signalling information

2) Queue status reports generated by the Queue Status Reporting function

3) Link adaptation reports generated by the Forward Link Adaptation function

4) UE specific signalling information

5) User plane data from any supported connections

剩余97页未读，继续阅读

Tosonw

粉丝: 89
资源: 95

ETSITS102744-3-2V1.1.1: Satellite Earth Stations and Systems - B...

最新资源

ETSITS102744-3-2V1.1.1: Satellite Earth Stations and Systems - B...

ts-1027440101v010101p.pdf

ts-1027440202v010101p.pdf

postcss-px-to-viewport.d.ts

vscode报错cmd.exe /d /s /c "ts-node ./cluster.ts"

解析ffmpeg -y -i input.mp4 -vcodec copy -acodec copy -vbsf h264_mp4toannexb output.ts

怎么使用ts-node调试ts文件

ts-node : 无法将“ts-node”项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写，如果包括路径，请确保路 径正确，然后再试一次。

DateTime dtNow = LogConfig.Now(); TimeSpan ts = dtNow - e.EndTime; int waitTimelong = 75 - (int)ts.TotalSeconds; waitTimelong = ((waitTimelong <= 0) ? 0 : waitTimelong * 1000);

ts-node有什么用

ffmpeg 如何将mp4转为 MPEG-PS

error TS5054: A 'tsconfig.json' file is already defined at: 'E:/pro1/react-ts-demo/tsconfig.json'.

Flow-Description in TS29.212

nodemon ts

base64.b64encode(( "admin:DS-8632N-I16-V2").encode('utf-8')).decode('utf-8')的结果

vscode ts-node 调试 Cannot find module 'ts-node/register'

atal: Authentication failed for 'https://e.coding.net/dajiangyouxiaofendui/react-ts-app/react-ts-dome.git/'

error in/node_modules/vue/types/v3-component-props.d.ts

最新资源

ts-node : 无法将“ts-node”项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写，如果包括路径，请确保路径正确，然后再试一次。