hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.6.0 General | The AES PBX shall implement a SIP User Agent as specified in SIP version 2.0 RFC 3261 [11]. UDP transport shall be used for all SIP signalling. The AES PBX shall send all SIP signalling to the SIP server using UDP destination port 5060 but may select a different UDP port to receive SIP messages. If using a port number ... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.6.1 SIP Registration | After successful activation of the primary PDP Context, the AES PBX shall send a SIP:REGISTER message to the SIP Server at the IP address resolved from the [sip_domain_name] string. The SIP REGISTER message shall comply with the requirements in RFC 3261 [11] clause 10. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.6.2 SIP Call Setup (originating from Aero PBX) | To originate a SIP call, the Aero PBX shall send a SIP INVITE message, which shall conform to the requirements in RFC 3261 [11] clause 10. No SDP Offer is required in the SIP:INVITE for air-to-ground initiated calls. The AES PBX shall always adhere to the SDP Answer returned by the SIP Server; in particular the ptime p... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.6.3 SIP Call Setup (terminating on Aero PBX) | Incoming SIP INVITEs will carry the ICAO based primary MS-ISDN of the AES PBX as the called number in the SIP:To header, the call priority in the SIP:Resource-Priority header, in the format: Field Name Field Value From: <sip:[priority][calling_number]@[sip_domain_name]> To: <sip:[called_number]@[sip_domain_name]> Resou... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.6.4 SIP Call Maintenance | The network may send SIP reINVITE messages at regular intervals on every SIP call to check that the AES PBX is still contactable and to check that the call is active. The network fails the call if the Aero PBX SIP User Agent does not reply or replies negatively. The AES PBX shall respond positively to the re-INVITE if ... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.6.5 SIP Options | The AES PBX shall respond to SIP OPTIONS polling from the network. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.7 Media Handling Requirements | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.7.1 Codec | The Aeronautical Safety AES shall support satellite optimized low data rate codecs for CS and PS calls. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.7.2 PS Codec Frame Packetisation | The Aero PBX shall support sending multiple codec frames in a single RTP packet as determined from the Session Description Protocol (SDP) ptime attribute sent by the network to the Aero PBX in the SIP:INVITE, SIP:183 Session Progress and SIP:200 OK messages. The following ptime values shall be supported: 20, 40, and 80... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.8 Supplementary Services Requirements | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.8.1 CS Domain Supplementary Services Requirements | The Call Forward on Busy (CFB) and Call Waiting (CW) Supplementary Services settings for TS11 (speech) calls configured in the network shall not be modified by the AES PBX as this may cause the Aeronautical Safety Voice service to malfunction. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.8.2 Calling Line Identification Presentation on Inbound Calls | For ground-to-air (mobile terminated) calls delivered over the CS domain, the Calling Number is carried in the CS Call Setup message (within the Calling Party BCD number field). For ground-to-air (mobile terminated) calls delivered via SIP the calling party number is included in the SIP:From header in the format: <sip:... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.8.3 Calling Line Identification Restriction on Outbound Calls | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.8.3.1 CS Domain | For air-to-ground (mobile originated) calls the restriction in presentation of the Calling Number will be enforced by the network by default. If the Calling Line Identity is to be presented to the remote party, i.e. [clir_outbound] is disabled, then the AES PBX shall send a CLIR suppression information element as detai... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.8.3.2 PS Domain | For air-to-ground (mobile originated) calls the restriction in presentation of the Calling Number is controlled via the SIP header field Privacy as defined in RFC 3323 [13]. If [clir_outbound] is enabled (default), then the AES PBX shall request the restriction in the Calling Line Identity within the SIP:Privacy header... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.5 Cabin/Public Calls | An Aeronautical Safety AES as described in the present document, may also optionally provide a non-cockpit based multi-voice service for cabin requirements. This would involve supporting a separate SIP User Agent following the requirements in ETSI TS 102 744-4-1 [14] with the exception that all cabin voice lines are pr... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 1 Scope | The present document defines the necessary control plane behaviour for instantiation and initiation of the User Plane entities, and also describes the operation of the User Plane entities for the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satel... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 2 References | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 3 Symbols and abbreviations | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 3.1 Symbols | For the purposes of the present document, the symbols given in clause 3 of ETSI TS 102 744-1-4 [11] apply. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in clause 3 of ETSI TS 102 744-1-4 [11] apply. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4 User Plane Operation | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.0 Overview | The present document specifies the behaviour of the User Plane in both the RNC and UE and covers the following: • the provision of a circuit switched (CS) 4 kbit/s voice service using a satellite optimized low data rate voice codec; ETSI ETSI TS 102 744-3-9 V1.1.1 (2015-10) 9 • the provision of a circuit switched (CS) ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1 Outline of Circuit Switched User Plane | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.0 General | The circuit switched user plane makes use of the CSH (Circuit Switched Handler) to provide services to the Non Access Stratum at the UE or the Relay function at the RNC. CSH is a satellite network specific sublayer and is specified in this and following clauses. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.1 Architecture | Figure 4.3 shows the architecture of the CSH layer at the UE side. Figure 4.4 shows the architecture of the CSH at the RNC side. The CSH layer consists of a CSH Manager and one data handler per CS connection. Two types of data handler are defined. The Adaptation Layer, a Radio Bearer Control (RBC) entity, configures th... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.2 Functions | The CSH Layer provides its services to the Non Access Stratum (NAS) at the UE or the relay at the Radio Network Controller (RNC). The CSH Layer shall perform the following functions: • Concatenation and separation of circuit switched data frames (satellite optimized low data rate voice codec frames or 640 bit higher la... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.3 Services | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.3.1 Services Provided to Upper Layers | The following services are provided by the CSH Layer towards the upper layers: • Transfer of user data. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.3.2 Services Expected from Bearer Connection Layer | The following services are expected from the Bearer Connection Layer: • Transparent data transfer service. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.4 Elements for layer-to-layer communication | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.4.0 General | The interaction between the CSH layer and other layers is described in terms of primitives where the primitives represent the logical exchange of information and control between CSH and other layers. The primitives shall not specify or constrain implementation. ETSI ETSI TS 102 744-3-9 V1.1.1 (2015-10) 12 |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.4.1 Control Plane Primitives between the CSH layer and adaptation layer | The control primitives between the CSH layer and the adaptation layer are shown in Table 4.1 for the UE side and Table 4.2 for the RNC side. Table 4.1: Control Plane Primitives between the CSH Layer (CSH Manager) and the adaptation layer RBC entity (UE side) SAP Generic Name Parameter _REQ _IND _RESP _CNF CSH-RBC- SAP ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.4.2 Control Plane Primitives between CSH and Call Control Layer | The control primitives between the CSH Manager and the Call Control layer at the UE are shown in Table 4.3. NOTE: The Service Access Point interface to the Call Control layer, shown here, is only for the purpose of illustrating the requirement to pass Circuit Switched Call Type information between CC and CSH and does n... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 4.1.4.3 User Plane Primitives between CSH and upper/lower layers | The user plane primitives between CSH and upper/lower layers are described in clause 5 for the 4 kbit/s voice circuit switched handler, and in clause 6 for the 64 kbit/s circuit switched handler, respectively. 4.1.4.4 Return Direction BCt User Plane Maintenance Bursts Prior to CC:Connect Message Following the establish... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5 CS User Plane for the 4 kbit/s Voice Service | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.1 General Architecture | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.1.0 Overview | The protocol stack for the User Plane providing a circuit switched connection for the low bit rate voice service is shown in Figure 5.1. ETSI ETSI TS 102 744-3-9 V1.1.1 (2015-10) 15 Figure 5.1: Circuit Switched User Plane Protocol Stack with Voice Codec On the radio interface, the Bearer Connection Layer (BCn) is confi... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.1.1 Configuration | Configuration of the VCSH shall be as described in clause 4.1.4. The values of ForwardCSFramesPerPDU and ReturnCSFramesPerPDU are passed to the UE in the RBC: Establish message during the RAB setup. They are set independently of each other and apply for the lifetime of the RAB (i.e. the duration of the call) only. The ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.1 Services Provided to Upper Layers | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.1.0 General | The CS User Plane Handler (VCSH) in the UE provides services directly to the satellite optimized low data rate voice codec through the Voice Codec Service Access Point (VC-SAP), as shown in Figure 5.2. Figure 5.2: Service Access Points to Upper Layers |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.1.1 Service Primitives at VC-SAP | The service primitives at VC-SAP are shown in Table 5.1. Table 5.1: CSH(VCSH)::VC Service Primitives at VC-SAP [UE] Primitive Direction Parameters VC_CSH_DATA_REQ The Voice Codec requests CSH to send a VC Frame to its peer in the RNC To CSH from VC VC Frame, DTX_FLAG VC_CSH_DATA_IND CSH passes a VC Frame to the VC or i... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.2 Services Expected from Lower Layers | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.2.0 General | The VCSH in the UE uses Transparent Mode message transport services provided by the Bearer Connection Layer to communicate with its peer in the RNC through the TM-SAP, as shown in Figure 5.3. Figure 5.3: Service Access Points to Lower Layers The Bearer Connection ID (BCnID) is the reference or handle to a particular SA... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.2.1 Service Primitives at TM-SAP | The service primitives at TM-SAP are shown in Table 5.2. Table 5.2: CSH(VCSH)::BCN Service Primitives at TM-SAP [UE] Primitive Direction Parameters BCn_TM_DATA_REQ CSH requests BCn to transmit the CSH-PDU (containing one or more VC Frames) in Transparent Mode To BCn from CSH CSH-PDU, BCnID, DiscardReq, MUI BCn_TM_DATA_... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.3 VCSH [UE] Architecture and Behaviour | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.3.0 General | The VCSH [UE] consists of a transmit path and a receive path, both being independent of each other. A first-in-first-out (FIFO) buffer is present in both the transmit path and receive path to handle the transmission and reception of multiple VC frames per CSH PDU. Each FIFO has an associated Control Unit, which handles... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.3.1 [UE] Transmit Behaviour [Return] | The VCSH [UE] transmit path buffers ReturnCSFramesPerPDU VC frames (satellite optimized low data rate codec frames) and their associated DTX_FLAGs received via the VC-SAP from the VC at a rate of one VC frame per 20 ms interval (see Figure 5.4). If at least one of the DTX_FLAGs associated with a VC frame is low, all th... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.2.3.2 [UE] Receive Behaviour [Forward] | When the VCSH in the UE receives a Data-PDU from BCn, via the TM-SAP, it shall separate the VC frames and place them in the receive FIFO buffer (see Figure 5.5). At successive 20 ms intervals the VCSH shall pass a single VC frame up to the VC via the VC-SAP. If the buffer is empty, the VCSH shall instead call the VC vi... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.1 Services Provided to Upper Layers | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.1.0 General | The VCSH in the RNC provides services to the satellite optimized low data rate voice codec indirectly via a relay to the Iu UP layer, through the RL-SAP, as shown in Figure 5.6. Figure 5.6: Service Access Points to Upper Layers [RNC] Start Attempt to take a codec frame from the Receive FIFO Buffer at successive 20 ms i... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.1.1 Service Primitives at RL-SAP [RNC] | The service primitives at RL-SAP are shown in Table 5.3. Table 5.3: CSH(VCSH)::IuUP Service Primitives at RL-SAP [RNC] Primitive Direction Parameters RL_CSH_DATA_REQ The Iu UP layer requests CSH to send a VC Frame to its peer in the UE or the IuUP sends a NO_DATA frame to the CSH To CSH from IuUP CHOICE{VC Frame, NO_DA... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.2 Services Expected from Lower Layers | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.2.0 General | The VCSH in the RNC uses Transparent Mode message transport services provided by the Bearer Connection Layer to communicate with its peer in the UE through the TM-SAP, as shown in Figure 5.7. Figure 5.7: Service Access Points to Lower Layers [RNC] |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.2.1 Service Primitives at TM-SAP | The service primitives at TM-SAP are shown in Table 5.4. Table 5.4: CSH(VCSH)::BCN Service Primitives at TM-SAP [RNC] Primitive Direction Parameters BCn_TM_DATA_REQ CSH requests BCn to transmit the CSH-PDU in Transparent Mode To BCn from CSH CSH-PDU, BCnID, DiscardReq, MUI BCn_TM_DATA_IND BCn passes a CSH PDU to CSH th... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.3 VCSH [RNC] Architecture and Behaviour | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.3.1 Iu UP Configuration | For Voice operation, the Iu UP (Iu Interface User Plane Protocol) supports predefined PDU sizes. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.3.2 [RNC] Transmit Behaviour [Forward] | When the VCSH in the RNC receives an Iu UP frame from the Iu UP layer (transmitted from the CN) via the RL-SAP then it shall determine if the frame is a NO_DATA Iu UP frame or contains a single VC frame (see Figure 5.8). If the received frame is a VC frame (SID, tone or voice), the VCSH shall place the received frame i... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.3.3.3 [RNC] Receive Behaviour [Return] | The RNC VCSH awaits delivery of a CSH PDU via the TM-SAP from the BCn layer (see Figure 5.9). On arrival of a CSH PDU the VCSH separates the codec frames within the PDU and places them in the FIFO receive buffer. At successive 20 ms intervals, one VC frame is removed from the buffer and handed to the Iu UP layer via th... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.4.1 Call Control Protocol Supported Codec Information Element | In order to inform the core network Mobile Switching Centre (MSC) of the capability of the UE to support the satellite optimized low data rate voice codec, both the Call Control SETUP (mobile originated case) and CALL CONFIRMED (mobile terminated case) messages generated by the UE shall include the Supported Codec List... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 5.5 DTMF Transmission | Except during use of the satellite optimized low data rate voice codec and the 64 kbit/s '3,1 kHz audio' service, transmission of mobile originated DTMF tones is carried out using the 3GPP DTMF protocol as specified in [3]. For speech calls where the satellite optimized low data rate voice codec is activated, the 3GPP ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.1 General Architecture | The protocol stack for the User Plane providing a circuit switched connection for the UDI/RDI/3,1 kHz services is shown in Figure 6.1. This service offers a 64 kbit/s synchronous transparent bearer to the higher layer, equivalent to an ISDN B channel. ETSI ETSI TS 102 744-3-9 V1.1.1 (2015-10) 26 The BCSH operates using... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2 64 kbit/s CS User Plane Handler (BCSH) - UE Side | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.1 64 kbit/s BCSH Services Provided to Upper Layers [UE] | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.1.0 General | The BCSH in the UE provides services directly to the higher layer through the Higher Layer Service Access Point (HL-SAP), as shown in Figure 6.2. Figure 6.2: 64 kbit/s CS Service Access Points to Upper Layers [UE] |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.1.1 64 kbit/s CS Service Primitives at HL-SAP [UE] | The 64 kbit/s CS Service Primitives at HL-SAP are shown in Table 6.1. Table 6.1: 64 kbit/s CSH(BCSH)::HL Service Primitives at HL-SAP [UE] Primitive Direction Parameters HL_CSH_DATA_REQ The Higher Layer requests CSH to send a User Data Frame to its peer in the RNC To CSH from HL User Data Frame HL_CSH_DATA_IND CSH indi... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.2 64 kbit/s CS Service, Services Expected from Lower Layers [UE] | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.2.0 General | The BCSH in the UE uses Transparent Mode message transport services provided by the Bearer Connection Layer to communicate with its peer in the RNC through the TM-SAP, as shown in Figure 6.3. CSH - CS UP Handler HL - Higher Layer HL-SAP ETSI ETSI TS 102 744-3-9 V1.1.1 (2015-10) 28 Figure 6.3: 64 kbit/s CS Service Acces... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.2.1 64 kbit/s CS Service Primitives at TM-SAP [UE] | The 64 kbit/s CS Service Primitives at TM-SAP are shown in Table 6.2. Table 6.2: 64 kbit/s CSH(BCSH)::BCN Service Primitives at TM-SAP [UE] Primitive Direction Parameters BCn_TM_DATA_REQ CSH requests BCn to transmit the CSH PDU(containing one or more user data frames) in Transparent Mode To BCn from CSH CSH-PDU, BCnID,... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.3 64 kbit/s BCSH [UE] Architecture and Behaviour | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.3.0 General | The BCSH [UE] consists of a transmit and a receive path, both being independent of each other. A first-in-first-out (FIFO) buffer is present in both the transmit and receive path to handle the transmission and reception of single or multiple user data frames per Connection Layer PDU. Each FIFO has an associated Control... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.3.1 64 kbit/s [UE] Transmit Behaviour [Return] | The BCSH transmit path in the UE receives ReturnCSFramesPerPDU user data frames (each of 640 bits) from the higher layer via the HL-SAP (where the frames are intended for onward transmission towards the CN). The reception of user data frames is synchronized to the radio interface transmission time at 10 ms intervals. A... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.2.3.2 64 kbit/s [UE] Receive Behaviour [Forward] | When the UE BCSH receives a CSH PDU passed up from BCn, via the TM-SAP, it shall separate it into its constituent User Data Frames and place them in the receive FIFO buffer (each CSH PDU will contain ForwardCSFramesPerPDU User Data Frames intended for the higher layer). At successive 10 ms intervals, the BCSH shall rem... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3 64 kbit/s CS User Plane Handler (BCSH) - RNC Side | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.1 64 kbit/s Services Provided to Upper Layers [RNC] | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.1.0 General | The BCSH in the RNC provides services to the higher layer indirectly via a relay to the Iu UP layer, through the RL- SAP, as shown in Figure 6.4. Figure 6.4: 64 kbit/s Service Access Points to Upper Layers [RNC] |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.1.1 64 kbit/s Service Primitives at RL-SAP [RNC] | The 64 kbit/s Service Primitives at RL-SAP are shown in Table 6.3. Table 6.3: 64 kbit/s CSH(BCSH)::IuUP Service Primitives at RL-SAP [RNC] Primitive Direction Parameters RL_CSH_DATA_REQ The Iu UP layer requests CSH to send a User Data Frame received from the CN to the UE. To CSH from IuUP User Data Frame RL_CSH_DATA_IN... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.2 64 kbit/s Services Expected from Lower Layers [RNC] | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.2.0 General | The BCSH in the RNC uses Transparent Mode message transport services provided by the Bearer Connection Layer to communicate with its peer in the UE through the TM-SAP, as shown in Figure 6.5. CSH - CS UP Handler Iu User Plane Protocol RL-SAP RL-SAP Relay ETSI ETSI TS 102 744-3-9 V1.1.1 (2015-10) 30 Figure 6.5: 64 kbit/... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.2.1 64 kbit/s Service Primitives at TM-SAP [RNC] | The 64 kbit/s Service Primitives at TM-SAP are shown in Table 6.4. Table 6.4: 64 kbit/s CSH(BCSH)::BCN Service Primitives at TM-SAP [RNC] Primitive Direction Parameters BCn_TM_DATA_REQ CSH requests BCn to transmit the CSH PDU (containing one or more User Data Frames) in Transparent Mode To BCn from CSH CSH-PDU, BCnID, ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.3 64 kbit/s BCSH [RNC] Architecture and Behaviour | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.3.1 Iu UP Configuration | The Iu UP is operated in transparent mode (see [4]). The Core Network receives/transmits Iu UP Frames as specified in [i.4] of 640 bits with a transmission time interval (TTI) of 10 ms resulting in an aggregate stream of 64 000 bits/s. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.3.2 64 kbit/s [RNC] Transmit Behaviour [Forward] | The BCSH in the RNC shall receive Transparent Mode Iu UP PDUs from the CN via the RL-SAP. The Transparent Mode Iu UP PDUs are 640 bit User Data Frames arriving at 10 ms intervals. The BCSH will place the User Data Frames in the FIFO receive buffer. Note that, unlike the case of the Voice Codec service, the 64 kbit/s se... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.3.3.3 64 kbit/s [RNC] Receive Behaviour [Return] | When the RNC BCSH receives a CSH PDU passed up from BCn, via the TM-SAP, it shall separate it into its constituent User Data Frames and place them in the receive FIFO buffer (each CSH PDU contains ReturnCSFramesPerPDU User Data Frames intended for the CN). At 10 ms intervals, the BCSH shall remove a single User Data Fr... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.4.0 General | Plesiochronous and transmission schedule buffering will be required at the User Equipment to support the bit synchronous 64 kbit/s bearer for UDI/RDI and 3,1 kHz audio services. Plesiochronous control shall be exercised to interface the slightly different clock rates between the received data clocks and local data cloc... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.5 Discontinuous Transmission (DTX) for 64 kbit/s Service | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.5.1 General Introduction | In order to achieve power/bandwidth efficiencies in 64 kbit/s Circuit Switched calls, discontinuous transmission will be activated for 64 kbit/s CS bearer connections in the Circuit Switched Handler (BCSH) protocol. When a repeated sequence of bytes is detected, the transmitter stops transmitting on a CSH PDU boundary.... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.5.2 64 kbit/s DTX - Mandatory and Optional Requirements | The capability to operate with Discontinuous Transmission for the 64 kbit/s service is mandatory for the Radio Access Network (RAN) in both forward and return directions. The capability to operate with Discontinuous Transmission for the 64 kbit/s service in the UE is optional in the return direction and mandatory in th... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.5.3 Enabling/Disabling and Selecting DTX algorithm | As previously noted in clause 4.1, the enabling or disabling of forward and return DTX shall be communicated by the RNC to the UE in the RBC: Establish message. The parameter CircuitSwitchedCallType is retrieved from the Call Control layer at the UE. CircuitSwitchedCallType is returned by the UE to the RNC in the RBC: ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.5.4 Terminology | The abbreviation DTX shall be equivalent to the term Discontinuous Transmission. The term Carrier Activation is not used in the present document because it implies transmission in a SCPC (Single Channel Per Carrier) channel, which is not applicable in the satellite network. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.5.5 Choosing the appropriate DTX algorithm | The parameter CircuitSwitchedCallType indicates to BCSH which DTX algorithm to use. The mapping between CircuitSwitchedCallType and DTX algorithm is presented in Table 6.5. Table 6.5: DTX Algorithm Selection for the BCSH CircuitSwitchedCallType DTX Algorithm Clause type-3pt1khz-audio DTX for 3,1 kHz Audio Services - Vo... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.5.6 DTX for 64 kbit/s UDI Service - Data Activated DTX Algorithm | This mechanism can be described as data activated switching. Data from the bearer is only transmitted during bursts of 64 kbit/s "active" (non idle-flag) user data (where user data not classed as "active" is defined by (i) in the algorithm shown in Figure 6.6) sent from transmitter to receiver. The discontinuous transm... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.5.7 DTX for 3,1 kHz Audio Services - Voice Activated DTX algorithm | DTX for 3,1 kHz audio services can be described as voice activated switching whereby the forward transmission of voice frames is turned off in the absence of analogue signals. The transmission of voice frames is restored whenever the equivalent analogue level of the PCM signal is above the threshold level X (where X sh... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 6.5.8 Maintenance Burst for 64 kbit/s DTX (UDI and 3,1 kHz Audio) | In order to ensure that a Bearer Connection is not erroneously cleared by the RNC due to extended periods of DTX , the transmitter shall periodically transmit a CSH-PDU of user data containing (ReturnCSFramesPerPDU × 640 bits) in the return direction. This maintaining burst shall be transmitted at an interval of no gre... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7 Packet Switched User Plane | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.0 Overview | A simplified stack diagram showing the satellite network user plane layers is shown in Figure 7.1. Figure 7.1: User Plane PS Domain The User Plane behaviour of Bearer Connection and Bearer Control layers is specified in ETSI TS 102 744-3-4 [13] and ETSI TS 102 744-3-2 [12] respectively. The PDCP layer is configured by ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.1 PDCP Protocol | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.1.0 General | The Packet Data Convergence Protocol shall perform the following functions: • header compression and decompression of IP data streams (e.g. TCP/IP and RTP/UDP/IP headers for IPv4 and IPv6) at the transmitting and receiving entity, respectively; • transfer of user data. This function is used for conveyance of data betwe... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.