hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 4.2.3 Boolean Variables | BOOLEAN variables shall be encoded as follows: TRUE ::= 1 FALSE ::= 0 4.2.4 ASN.1 Encoding Rules The ASN.1 presentation provided in the present document for this interface specification is normative. The encoding rules used for this interface specification are provided in clause 4.4.4 of ETSI TS 102 744-3-1 [8]. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 5 NAS Layer Interface | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 5.1 NAS layer use of AL service access points | Protocol entities in the NAS Layer use message transport services provided by the Adaptation Layer to communicate with their peers through two Service Access Points (SAPs): • MMAL-SAP: MM to Adaptation Layer Service Access Point (CS domain) • GMMAL-SAP: GMM to Adaptation Layer Service Access Point (PS domain) • BMMAL-S... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 5.2 NAS Layer MBMS Service Management Messages | The NAS Layer MBMS Service Management messages shown in Table 5.1 are supported between the UE and BMSN. The interfaces between the UE and the BMSN are shown in Figure 7.1 in ETSI TS 102 744-1-1 [6]. ETSI ETSI TS 102 744-3-7 V1.1.1 (2015-10) 10 Table 5.1: Multicast NAS messages NAS Message Direction Key Parameters Acti... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6 NAS Layer Protocol Data Units | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.1 General NAS PDU Structure | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.1.0 General | The following sections define the format of the Protocol Data Units (PDUs) which are used by the NAS Layer to signal its peer (NAS-PDUs). The proposed format is similar to the 3GPP L3 messages as defined in ETSI TS 124 007 [1]. This means that the message consists of the following parts: • protocol discriminator; • tra... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.1.1 NAS PDU Header Common Elements | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.1.1.1 TransactionIdentifier (TI) | The transaction identifier and its use are defined in ETSI TS 124 007 [1]. The TI is defined in ETSI TS 124 007 [1] to half an octet in length, with an option to extend the TI to one and half octet. The structure of TI is as shown in Figure 6.2. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 ti tio protocol-discriminator Octet 1 e... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.1.1.2 ProtocolDiscriminator | The Protocol Discriminator (PD) and its use are defined in ETSI TS 124 007 [1]. Normally the PD is half octet length with all values reserved. All NAS messages towards the BM domain shall utilize a half-octet long PD, adopting the binary value of '1010', representing GPRS Session Management messages. ETSI ETSI TS 102 7... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.1.1.3 NasMessageType | The message type Information Element (IE) and its use are defined in ETSI TS 124 007 [1]. The values used towards the BM domain are as specified for GPRS Session Management and are shown in Table 6.1. Table 6.1: Multicast message type values relevant to the BM domain Bits 8 7 6 5 4 3 2 1 0 1 - - - - - - Session managem... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.2 Format of standard information elements | Standard IE and its use are defined in ETSI TS 124 007 [1] and may have the following parts, in that order: • an information element identifier (IEI) ; • a length indicator (LI); • a value part. ETSI ETSI TS 102 744-3-7 V1.1.1 (2015-10) 13 A standard IE has one of the formats shown in Table 6.2. Table 6.2: Formats of i... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3 NAS MBMS Service Management Messages | NAS PDUs containing NAS messages transferred in the UE-BMSN direction are carried within a UplinkDirectTransfer Adaptation Layer (AL) messages, while NAS PDUs transferred in the BMSN-UE direction are carried within DownlinkDirectTransfer AL messages (see ETSI TS 102 744-3-5 [9]). The NAS messages are passed transparent... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.1 ActivatePDPContextRequest | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.1.0 General | The ActivatePDPContextRequest NAS message is used by the UE to access services within the BM domain as referenced by the Access Point Name (APN). If the UE is GPRS Attached, the UE transmits an ActivatePDPContextRequest(NSAPI, APN) NAS message to the RAN encapsulated in an UplinkDirectTransfer AL message towards the BM... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.1.1 nsapi (Network Service Access Point Identifier) | The nsapi information element is an UE-allocated reference called the Network Service Access Point Identifier. Values in the range 0..15 identify a PDP Context endpoint within the scope of a UE. The nsapi parameter is of type NSAPI which is defined in clause 7.2. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.1.2 requested-llcsapi | The requested-llcsapi is of type LLCSAPI as defined in clause 7.3. This information element is not used by the BM domain of the Core Network (CN) but is left in the definition to be consistent with 3GPP. Default value '00000000'B (requested-llcsapi not assigned). ETSI ETSI TS 102 744-3-7 V1.1.1 (2015-10) 15 |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.1.3 requested-pdp-address (PDPAddress) | The requested-pdp-address is used to request an IP address to utilized for this PDP context, and is of type PDPAddress as defined in clause 7.5. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.1.4 apn (Access Point Name) | Access Point Name value is used to reference an external network domain and is defined in ETSI TS 123 003 [3]. The apn parameter is of type APN which is defined in clause 7.1. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.1.5 requested-qos (QualityOfService) | The requested-qos parameter is of type QualityOfService as specified in clause 7.6, and is used to define the requested quality of service characteristics of the PDP Context. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.2 ActivatePDPContextAccept | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.2.0 General | The ActivatePDPContextAccept NAS message is used by the BMSN to accept an ActivatePDPContextRequest from a UE. When the BMSN receives that the Radio Access Bearer has been established successfully then the BMSN sends this message to the UE via the RAN. The format of an ActivatePDPContextAccept is as shown in Table 6.4.... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.2.1 negotiated-llc-sapi | The negotiated-llcsapi parameter is of type LLCSAPI as defined in clause 7.3. It is not currently used by the BM domain of the CN but is left in the definition to be consistent with 3GPP. Default value '00000000'B (negotiated-llcsapi not assigned). |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.3 ActivatePDPContextReject | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.3.0 General | The ActivatePDPContextReject NAS message is used by the BMSN to reject an ActivatePDPContextRequest from a UE. If the UE is not provisioned in the Broadcast Multicast Service Centre (BMSC) database it will reject the service. The format of an ActivatePDPContextReject is as shown in Table 6.5. Table 6.5: ActivatePDPCont... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.3.1 SMCause | The Information Element sm-cause is of type SMCause, the values of which are defined in clause 7.14, and are similar to those described in 3GPP TR 29.846 [i.1], clause 5.5.1. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.4 ActivateSecondaryContextRequest | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.4.0 General | The ActivateSecondaryContextRequest NAS message is used by the UE to establish PDP contexts with specific QoS requirements to carry specific application traffic via the BM domain. A Primary PDP context shall be in existence, and active on the UE interface via which the Secondary PDP context is to be activated. The form... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.4.1 nsapi (Network Service Access Point Identifier) | The nsapi information element is an UE-allocated reference called the Network Service Access Point Identifier. Values in the range 0..15 identify a PDP Context endpoint within the scope of a UE. The nsapi parameter is of type NSAPI which is defined in clause 7.2. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.4.2 requested-llcsapi | The requested-llcsapi is of type LLCSAPI as defined in clause 7.3. This information element is not used by the BM domain of the CN but is left in the definition to be consistent with 3GPP. Default value '00000000'B (requested-llcsapi not assigned). |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.4.3 linked-ti (Linked TI) | The linked-ti is used to reference the Primary PDP context with which this Secondary PDP context is associated. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.4.4 traffic-flow-template (TFT) | The traffic-flow-template (TFT) information element contains a description of the traffic to be carried via this secondary PDP context. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.4.5 requested-qos (QualityOfService) | The requested-qos parameter is of type QualityOfService as specified in clause 7.6, and is used to define the requested quality of service characteristics of the PDP Context. ETSI ETSI TS 102 744-3-7 V1.1.1 (2015-10) 19 |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.5 ActivateSecondaryContextAccept | The ActivateSecondaryContextAccept NAS message is used by the BMSN to accept an ActivateSecondaryContextRequest from a UE. When the BMSN receives that the Radio Access Bearer has been established successfully then the BMSN sends this message to the UE via the RAN. The format of an ActivateSecondaryContextAccept is as s... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.6 ActivateSecondaryContextReject | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.6.0 General | The ActivateSecondaryContextReject NAS message is used by the BMSN to reject an ActivateSecondaryContextRequest from a UE. If the UE is not provisioned in the BMSC database it will reject the service. The format of an ActivateSecondaryContextReject is as shown in Table 6.8. Table 6.8: ActivateSecondaryContextReject mes... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.6.1 SMCause | The Information Element sm-cause is of type SMCause, the values of which are defined in clause 7.14, and are similar to those described in 3GPP TR 29.846 [i.1], clause 5.5.1. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.7 DeactivatePDPContextRequest | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.7.0 General | The DeactivatePDPContextRequest NAS message is used by the UE to deactivate either a specific secondary PDP context or MBMS context, or the Primary PDP context and all associated secondary PDP context and MBMS contexts (this will release the association between the UE and a specific APN). This NAS message is used by th... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.7.1 tear-down-indicator | The tear-down-indicator information element is of type TearDownIndicator as defined in clause 7.8. It shall be included and set to TRUE when the PDP context being released is a Primary PDP context (in which case all secondary PDP contexts and MBMS contexts shall be deleted). It shall not be included when the PDP contex... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.3.8 DeactivatePDPContextAccept | The DeactivatePDPContextAccept NAS message is used by the BMSN to accept a DeactivatePDPContextRequest. When the UE receives the message from the BMSN it deletes the PDP Context and signals the change of state towards any external interface. The format of a DeactivatePDPContextAccept is as shown in Table 6.10. Table 6.... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.4 ActivateMBMSContextRequest | The ActivateMBMSContextRequest is used by the UE to request the activation of a MBMS service. The format of ActivateMBMSContextRequest is as shown in Table 6.11. Table 6.11: ActivateMBMSContextRequest message content IEI Information Element Type/ Presence Format Length Protocol discriminator Protocol discriminator M V ... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.5 ActivateMBMSContextAccept | The format of ActivateMBMSContextAccept is as shown in Table 6.12. Table 6.12: ActivateMBMSContextAccept message content IEI Information Element Type/ Presence Format Length Protocol discriminator Protocol discriminator M V 0,5 Transaction identifier Transaction identifier M V 0,5 - 1,5 Activate MBMS Context Accept Mes... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.6 ActivateMBMSContextReject | The format of ActivateMBMSContextReject is as shown in Table 6.13. Table 6.13: ActivateMBMSContextReject message content IEI Information Element Type/Reference Presence Format Length Protocol discriminator Protocol discriminator M V 0,5 Transaction identifier Transaction identifier M V 0,5 - 1,5 Activate MBMS Context R... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.7 RequestMBMSContextActivation | The format of RequestMBMSContextActivation is as shown in Table 6.14. Table 6.14: RequestMBMSContextActivation message content IEI Information Element Type/Reference Presence Format Length Protocol discriminator Protocol discriminator M V 0,5 Transaction identifier Transaction identifier M V 0,5 - 1,5 Request MBMS Cont... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 6.8 RequestMBMSContextActivationReject | The format of RequestMBMSContextActivationReject is as shown in Table 6.15. Table 6.15: RequestMBMSContextActivationReject message content IEI Information Element Type/Reference Presence Format Length Protocol discriminator Protocol discriminator M V 0,5 Transaction identifier Transaction identifier M V 0,5 - 1,5 Reque... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7 Information Elements Coding | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.1 Access Point Name | Access Point Name value is defined in ETSI TS 123 003 [3]. For MBMS and PDP Contexts supported by the BM domain it is considered to reference a specific external IP administrative domain. Although the IE is shown as Optional in the MBMS and PDP Context Activation Request messages, it shall always be included for commun... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.2 Network service access point identifier (NSAPI) | The Network service access point identifier value identifies PDP Context or MBMS Context endpoint within the scope of an UE. It is allocated by the UE and is based upon the definition in ETSI TS 124 008 [2], clause 10.5.6.2. The UE should allocate the NSAPI in a sequential order for each subsequent PDP Context, thereby... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.3 LLC SAPI | Logical Link Control (LLC) Service Access Point Identifier (SAPI) is defined in ETSI TS 124 008 [2]. It is a legacy IE and therefore not used in Multicast. Nevertheless, it is kept in the definition to be consistent with 3GPP. The default value should be '00000000'B (LLC SAPI not assigned). LLCSAPI::= INTEGER (0..255);... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.4 Protocol configuration options | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.4.0 General | This optional Information Element is used to transfer external protocol options associated with a PDP Context Activation. It is defined in ETSI TS 124 008 [2], clause 10.5.6.3. ProtocolConfigurationOptions ::= SEQUENCE { protocol-config-options-iei InformationElementIdentifier, protocol-config-options-length INTEGER (S... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.4.1 UE supporting ARP proxy functionality | For the case of i) above, the UE needs to be aware of both the Gateway address and subnet mask that should be used for the APN to allow correct configuration of the ARP proxy functionality, and also the Domain Name System (DNS) addresses that should be used. For this case, the UE shall not send PPP information, but sha... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.4.2 UE Supporting PPP (or PPPoE) interface | When the UE supports a PPP (or PPPoE) interface, the information in the Configuration Protocol Content shall be as specified in PPP (RFC 1661 [4]). Only the Internet Protocol Control Protocol (IPCP) (RFC 1332 [5]), with protocol ID 8021, shall be supported by the BM domain for the trial configuration, although other op... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.5 Packet Data Protocol Address | |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.5.0 General | This information element, defined in ETSI TS 124 008 [2], clause 10.5.6.4, is used to identify the address associated to a primary PDP Context and also to identify the IP Multicast address (or addresses) allocated to a MBMS Context when used in the to-mobile direction. Note that when present in Request MBMS Context Act... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.5.1 pdp-type-organisation | The pdp-type-organisation is used to specify the type of address, and is of type PDPTypeOrganisation: PDPTypeOrganisation::= INTEGER { etsi-allocated-address (0), ietf-allocated-address (1), empty (15) } (SIZE (0..255)) -- the value shall always be set to 1 for BM domain operation |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.5.2 pdp-type-number | The pdp-type-number is used to specify the type of address, and is of type PDPTypeNumber: PDPTypeNumber::= INTEGER { ipv4-address-type (33), ipv6-address=type (87), ipv4-address-and-range-type (161) } (SIZE (0..255) |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.5.3 PDPAddressInfo | The pdp-address-info is used to carry the IP address to be allocated to the PDP context (this is interpreted as a request if carried in an Activate PDP Context Request and an allocation if carried in an Activate PDP Context Accept). If a range of addresses are being allocated (either for the PDP address or for an Multi... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.6 Quality of Service | This information element is defined in ETSI TS 124 008 [2], clause 10.5.6.5. QualityOfService ::= SEQUENCE { qos-iei InformationElementIdentifier, qos-length INTEGER (SIZE 0..255), spare-2bits BIT STRING (SIZE (2)), delay-class DelayClass, reliability-class ReliabilityClass, peak-throughput PeakThroughput, spare-1bit B... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.7 Linked TI | This Information Element is defined in ETSI TS 124 008 [2], clause 10.5.6.7. LinkedTI::= SEQUENCE{ linkedti-iei InformationElementIdentifier, linkedti-length INTEGER (SIZE 0..255), extended-ti-flag BOOLEAN, short-linked-ti SEQUENCE { short-linked-ti INTEGER (SIZE 0..7), spare BIT STRING (SIZE (3)) } extended-linked-ti ... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.8 Tear Down Indicator | This Information Element is defined in ETSI TS 124 008 [2], clause 10.5.6.10. TeardownIndicator::= SEQUENCE{ teardown-iei ShortInformationElementIdentifier, spare BIT STRING (SIZE (3)), teardown-indicator BOOLEAN } For operation with the BM domain, this single-octet information element shall always be present, and the ... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.9 Packet Flow Identifier | This Information Element is defined in ETSI TS 124 008 [2], clause 10.5.6.11. This information element is not used towards the BM domain. |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.10 Traffic Flow Template | This Information Element is defined in ETSI TS 124 008 [2], clause 10.5.6.12. Traffic Flow Template IEI value is 36. TrafficFilterTemplate ::= SEQUENCE { tft-iei InformationElementIdentifier, tft-length INTEGER (SIZE 0..255), tft-operationcode { spare (0), create-new-tft (1), delete-existing-tft (2), add-filters-to-exi... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.11 TMGI | This Information Element is defined in ETSI TS 124 008 [2], clause 10.5.6.13. 3GPP allows the coding of this information element to be of variable length, to allow the inclusion of the Mobile Country Code (MCC) and Mobile Network Code (MNC) fields. This coding is not necessary for operation with the BM domain, and the ... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.12 MBMS Bearer capabilities | The purpose of the MBMS bearer capabilities information element is to indicate the maximum bit rate for downlink supported by the MS for an MBMS context. NOTE: The information element indicates the static physical capabilities of the MS, independent of the radio access (UMTS Terrestrial Radio Access Network (UTRAN) or ... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.13 MBMS protocol configuration options | This Information Element is defined in ETSI TS 124 008 [2], clause 10.5.6.15, however this is currently shown as a string for transparent handling by the RAN for future MBMS specification. The approach here is to adopt the same container-approach as for Protocol Configuration Options. MBMSProtocolConfigurationOptions :... |
b65e1c895f8d97ce262f71305c0a2c52 | 102 744-3-7 | 7.14 SM Cause | The SM cause values are similar to those described in 3GPPP TR 29.846 [i.1], clause 5.5.1, and are shown in Table 7.3. Table 7.3: SMCause information element values Bits 8 7 6 5 4 3 2 1 0 0 0 0 1 0 0 0 Operator Determined Barring 0 0 0 1 1 0 0 0 MBMS bearer capabilities insufficient for the service 0 0 0 1 1 0 1 0 Insu... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 1 Scope | The present document defines the Adaptation Layer (AL) operation of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network. The Adaptation Layer (AL) peer-to-peer interface is described in TS 102 744-3-5 [11]. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 2 References | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 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... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 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... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 3 Symbols and abbreviations | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 3.1 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 744-1-4 [8], clause 3 apply. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 744-1-4 [8], clause 3 apply. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 4 General Architecture | The Adaptation Layer allows the Physical, Radio Link Control (RLC), and Media Access Control (MAC) layers of the terrestrial UMTS radio interface (Uu) between the RNC and UE to be replaced with their equivalents from the satellite network radio interface. The Adaptation Layer is a direct replacement for Radio Resource ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5 AL Control Plane - UE Side | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.1 Services Provided to Upper Layers | The UE Adaptation Layer (AL) provides message transport and event notification services to the UMTS Layer 3 Mobility Management sublayer (GPRS Mobility Management (GMM), Mobility Management (MM), and Radio Access Bearer Management (RABM)) in the Non-Access Stratum via the Service Access Points (SAPs) defined in ETSI TS... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.2 Services Expected from Lower Layers | The UE Adaptation Layer uses message transport services provided by the Bearer Connection layer to communicate with its peer in the RNC through two Service Access Points, as shown in Figure 5.2: • Common Signalling Service Access Point (COM-SAP) • UE-Specific Signalling Service Access Point (SIG-SAP). The SIG-SAP is a ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.3 Agents in the Adaptation Layer | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.3.0 General | The Adaptation Layer in the UE contains four classes of agent: • Registration Manager (REGM); • GMM Service Access Point Handler (GMMH); • MM Service Access Point Handler (MMH); and • Radio Bearer Control (RBC). There is one instance each of REGM, GMMH, and MMH and two instances of RBC (one for the PS domain and one fo... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.3.1 Registration Manager (REGM) | REGM is responsible for: • establishing, maintaining, and releasing the UE Specific Signalling connection by performing the radio interface Registration, Handover, and Deregistration procedures with the RNC; ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 14 • reception and interpretation of System Information Broadcast mess... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.3.2 GMM Service Access Point Handler (GMMH) | GMMH provides RRC-like services to the GMM agent in the Non-Access Stratum. GMMH supports the full suite of service primitives through the GMMAS-SAP as defined in ETSI TS 124 007 [1] and expects GMM Layer 3 behaviour as defined in ETSI TS 124 008 [3]. GMMH is also responsible for integrity protection control and cipher... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.3.3 MM Service Access Point Handler (MMH) | MMH provides RRC-like services to the MM agent in the Non-Access Stratum. MMH supports the full suite of service primitives through the RR-SAP, as defined in ETSI TS 124 007 [1], and expects MM Layer 3 behaviour as defined in ETSI TS 124 008 [3], as shown in Figure 5.5. MMH is also responsible for integrity protection ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.3.4 Radio Bearer Control (RBC) | RBC handles all signalling related to the establishment, modification, and release of radio bearers. RBC configures user plane protocol layers (such as PDCP and CSH) and agents and also provides resource assignment notification services to NAS agents (e.g. RABM and also MM via the MMH), as shown in Figure 5.6. RBC uses... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.3.5 SIG-SAP Router (SSR) | The Adaptation Layer contains a routing function at the SIG-SAP for Protocol Data Units (PDUs) exchanged between peer-to-peer AL agents. The SIG-SAP router is also responsible for the integrity protection of all dedicated signalling messages (see clause 7.1). Routing between the SIG-SAP and AL agents is based on the 'A... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.3.6 CBCn-SAP Router (CSR) | The Adaptation Layer contains a transparent routing function at the CBCn-SAP for all control service primitives exchanged between the Adaptation Layer and the Bearer Connection Manager (see ETSI TS 102 744-3-4 [10]), as shown in Figure 5.8. Routing between the CBCn-SAP and AL agents is based on the ALPD parameter, whic... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4 Protocol Definitions | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1 REGM | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.1 REGM Protocol Data Units | The REGM Protocol Data Units are as shown in Table 5.2. Table 5.2: REGM::REGM Protocol Data Units PDU SAP Direction Addressing Information Elements PagingType1 COM To UE UE NAS ID CN Domain Identity, Paging Cause Register COM From UE UE NAS ID Registration Reference, RI Version, CN Domain Identity, Registration Cause, ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.2 Service Primitives at COM-SAP | The service primitives at COM-SAP are as shown in Table 5.3. Table 5.3: REGM::BCn Service Primitives at COM-SAP [UE] Primitive Direction Information Elements AL_COMDATA_REQ REGM requests the BCn layer to send a PDU to its peer in the RNC To BCn UE NAS ID and Type, {LAI} OPTIONAL, REGM PDU Type, REGM PDU, Retry Count AL... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.3 Service Primitives at REGM-SIG-SAP | The service primitives at REGM-SIG-SAP are as shown in Table 5.4. Table 5.4: REGM::SSR Service Primitives at REGM-SIG-SAP [UE] Primitive Direction Parameters SSR_SIGDATA_REQ REGM requests SSR to send a PDU to its peer in the RNC. To SSR REGM PDU SSR_SIGDATA_IND SSR indicates to REGM that it has received a PDU from the ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.5 Service Primitives at GC-SAP | ETSI TS 125 304 [2] specifies a set of service primitives between RRC and the NAS for the purpose of PLMN Selection and NAS System Information Transport. These service primitives at GC-SAP are shown in Table 5.6. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 20 Table 5.6: REGM::NAS Service Primitives at GC-SAP [UE] Primiti... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.6 Service Primitives at REGM-CBCn-SAP | The service primitives at REGM-CBCn-SAP are as shown in Table 5.7. Table 5.7: REGM::CSR Service Primitives at REGM-CBCn-SAP [UE] Primitive Direction Parameters CBCn_CREATE_REQ REGM requests the BCn layer to create the SIG-SAP with the specified handle (BCnID) and QoS attributes. To CSR ALPD, BCnID (SIG- SAP), BCn/AL Pa... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.7 Service Primitives at CBCt-SAP | The service primitives at CBCt-SAP are as shown in Table 5.8. Table 5.8: REGM::BCt Service Primitives at CBCt-SAP [UE] Primitive Direction Parameters CBCt_DISCOVER_REQ REGM requests the BCt layer to find and camp on the identified PSAB. Where more than one PSAB is indicated, REGM requests the BCt layer to select and ca... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.8 REGM States | The REGM states are as shown in Table 5.9. Table 5.9: REGM States [UE] Number State Description 1 IDLE ("RRC-IDLE") The UE is not registered with the RNC and a UE-Specific signalling connection between the UE and RNC is not established. This state has five substates. >1a IDLE-AWAIT-PLMN- DISCOVERY Initial State REGM h... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9 REGM Behaviour | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.0 General | REGM behaviour in the UE is summarized in the signal-state diagram in Figure 5.9. Substates of the 'IDLE' state ("idle mode behaviour") are shown in Figure 5.10. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 23 Figure 5.9: UE REGM Signal-State Diagram ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 24 Figure 5.10: UE REGM Idle M... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.1 Behaviour in State 'IDLE' | 5.4.1.9.1.1 Behaviour in Substate 'AWAIT-PLMN-DISCOVERY' On entry to this state (i.e. on REGM startup), REGM shall initialize CU13. On receipt of the PLMN_SEARCH_REQ primitive from the Non-Access Stratum (NAS), REGM shall save the type of PLMN search requested (either "Specific PLMN ID" or "All PLMN IDs". In the case o... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.2 Behaviour in State 'REGISTERING' | 5.4.1.9.2.0 General The REGISTERING state has four substates: 'AWAIT-RESPONSE', 'AWAIT-CREATE', and 'AWAIT-CONNECT'. 5.4.1.9.2.1 Behaviour in Substate 'AWAIT-RESPONSE' On receipt of the AL_COMDATA_IND primitive from the COM-SAP, REGM shall examine the PDU type parameter: • 1> if the PDU type is REGM:RegisterAck, then: ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.