hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.1.1.2 COUNT-I | The integrity sequence number COUNT-I has length 32 bits. SSR maintains separate COUNT-I parameters for messages transmitted (COUNT-I TX) and messages received (COUNT-I RX). SSR increments COUNT-I TX by one immediately after a message which requires integrity protection is received from any AL agent via the SSR_SIGDATA... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.1.1.3 FRESH | FRESH is a random 32-bit number. There is a different random FRESH parameter value associated with each UE- Specific Signalling connection; FRESH is generated by REGM when the UE Specific Signalling (UESS) is created (at registration) and it is used by both the RNC and UE throughout the lifetime of the connection (unti... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.1.1.4 DIRECTION | DIRECTION is a 1-bit parameter which has the value 0 for messages from the UE to RNC and 1 for messages from the RNC to UE. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.1.1.5 MESSAGE | The definition of the parameter MESSAGE is illustrated in Figure 7.1 (see also ETSI TS 102 744-3-5 [11]). Figure 7.1: Definition of MESSAGE Parameter The maximum length of the MESSAGE parameter is [X19]-1 octets (the variable X19 is defined in [5]). |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.1.2 Method | On receipt of the SSR-SIGDATA-REQ primitive from any AL agent, the (sending) SSR increments COUNT-I TX by one, composes the MESSAGE as shown in Figure 7.2, and computes the Message Authentication Code for Integrity (MAC-I) using the integrity algorithm f9 and the input parameters IK, COUNT-I, FRESH, DIRECTION, and MESS... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.2 Ciphering Control | The Bearer Connection Layer uses a modified version of the UMTS Encryption Algorithm (UEA) f8 as defined in ETSI TS 133 102 [4] and ETSI TS 133 105 [5] to cipher AL PDUs transmitted over the radio interface via the UE-Specific Signalling Connection (via the SIG-SAP). GMMH and MMH in the Adaptation Layer both control an... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.3 Security Mode Set-Up Procedure | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.3.1 Common Procedure | The security set-up procedure in the Adaptation Layer is illustrated in Figure 7.3 and described in the text which follows. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 135 Figure 7.3: Security Mode Set-Up Procedure ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 136 1) The Visitor Location Register (VLR) or SGSN initiates the ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.3.2 Initialization of Synchronization for Ciphering and Integrity Protection | This section contains a summary of clause 6.4.8 of ETSI TS 133 102 [4], changed where required for the satellite network context. See also Figure 7.4. The ciphering and integrity protection algorithms are driven by counters (COUNT-C and COUNT-I) that at connection establishment need to be initialized. For that purpose ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.3.3 Common Procedure - RNC Considerations | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.3.3.1 Integrity Protection | Clause 7.3.1 describes the first time the Common Security Mode Command procedure is being performed. A variation to the Common Procedure is required for the second and subsequent times. This variation applies to the RNC only. When integrity protection is enabled for this first time (i.e. the SSR_SECURITY_REQ primitive ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.3.3.2 Integrity Protection Activation Failure at UE | If integrity protection activation fails at the UE, and if integrity protection is being enabled for the first time, then the GMMH/MMH:SecurityModeFailure PDU will arrive at the RNC SSR unprotected. Therefore, when integrity protection is being enabled for the first time, the RNC SSR shall be prepared to accept a PDU f... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.3.3.3 Ciphering Activation Failure at UE | If integrity protection activation is successful, but ciphering activation fails at the UE, then the GMMH/MMH:SecurityModeFailure PDU will arrive at the SSR protected with the new integrity configuration (and the AL MSN associated with this PDU will be "1"). If integrity protection is being modified by the current proc... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 7.4 UE Position Encryption | REGM in the Adaptation Layer shall use the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP) [6] public key cryptosystem to ensure confidentiality of the UE geographical position in transit over the radio interface. Initially, the satellite network shall use a 640-bit key, but the structure of ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 8 Spot Beam Selection Algorithm | 8.0 General The Spot Beam Map SDU (System Information) contains information about the boundaries of one or more spot beams in the satellite network. REGM performs spot beam selection using this method only when the Spot Beam Map SDU is present in the current System Information. The structure of the Spot Beam Map SDU al... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 8.1 Spot Beam Boundary Generation (Great Circle Polygon) | A great circle is formed by the intersection of the earth with a plane containing the centre of the earth and any two points on the surface of the earth. When a spot beam is described using the Great Circle Polygon method, REGM shall extract the number of vertices (n), and the list of longitude and latitude coordinates... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 8.2 Spot Beam Boundary Generation (Centre/Radius) | Satellite-centred azimuth (Az) and elevation (El) are polar angles similar to longitude and latitude, respectively, except the origin of the right-handed Cartesian coordinate system is at the centre of the satellite instead of the centre of the earth. The positive x-axis points in the direction of north, the positive y... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 8.3 Inclusion Algorithm | This algorithm determines whether or not the UE with longitude θ and latitude φ is inside a polygon with k vertices, P(θ, φ) [0, 1, …, k-1]. REGM shall assume that longitude and latitude form a Cartesian coordinate system (i.e. lines of constant latitude and lines of constant longitude intersect at right angles) and th... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 9 Signalling Examples | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 9.1 PLMN/Spot Beam Selection | Figure 9.1 illustrates an example message sequence for PLMN/Spot Beam Selection. Figure 9.1: Message Sequence for PLMN/Spot Beam Selection NAS REGM UE BCt RAN BCt PLMN_SEARCH_REQ [BGAN PLMN ID] PLMN_SEARCH_CNF [BGAN PLMN ID] SYSTEM_INFORMATION_IND [NAS System Info] CBCt_SYSTEM_INFORMATION_IND (Global Beam) BCt: Bulleti... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 9.2 Registration and First NAS Message | Figure 9.2 illustrates an example message sequence for Registration and Initial NAS Message Transfer. Figure 9.2: Message Sequence for Registration and Initial NAS Message Transfer (CSR Not Shown) GMMAL_ESTABLISH_ REQ [NAS Msg.= GMM:Attach Request, Cause, Priority, CN Domain, UE NAS ID, LAI/RAI] REGM_CONN_REQ [Cause,Pr... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 9.3 Subsequent NAS Messages | Figure 9.3 illustrates an example message sequence for subsequent NAS Message Transfer (following the Initial NAS Message Transfer shown in Figure 9.2). Figure 9.3: Message Sequence for NAS Message Transfer (Subsequent) (GMMH::SSR Primitives Not Shown) BCn_AM_DATA_REQ [GMMH:DownlinkDirect Transfer (NAS Msg.=GMM:Ident. ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 9.4 Handover | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 9.4.1 RNC-Initiated | Figure 9.4 illustrates an example message sequence for RNC-Initiated Handover. Figure 9.4: Message Sequence for RNC-Initiated Handover RBC RNC REGM RELAY RL_ESTABLISH RBC BCn/BCt UE REGM BCn/BCt RRM CBCn_CREATE_REQ (resource query) (resource response) CBCn_HANDOVER_IND [BCt EPDU] (Handover Required) REGM:Handover [BCt ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 9.4.2 UE-Initiated | Figure 9.5 illustrates an example message sequence for UE-Initiated Handover. Figure 9.5: Message Sequence for UE-Initiated Handover RNC REGM RELAY BCn/BCt UE REGM BCn/BCt RRM/ GRM (resource query) (resource response) CBCn_HANDOVER_IND [BCt EPDU] REGM:Handover [BCt EPDU] in Source Beam CBCn_HANDOVER_REQ [BCt EPDU] CBCn... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 1 Scope | The present document defines the Adaptation Layer (AL) peer-to-peer interface of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 2 References | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 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... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 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... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 3 Symbols and abbreviations | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 3.1 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 744-1-4 [4], clause 3 apply. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 744-1-4 [4], clause 3 apply. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 4 Adaptation Layer Interface | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 4.1 Radio Interface Layering | The satellite communication protocol is considered as a number of communication layers, as follows: • Adaptation Layer (AL); • Bearer Connection Layer (BCn); and • Bearer Control Layer (BCt); • Physical Layer (L1). The satellite radio interface protocol stack is designed to seamlessly integrate with UMTS Non-Access Str... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 4.2 Conventions used in the present document | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 4.2.1 Presentation | The following conventions are applied throughout the present document: • In the ASN.1, variable names are always in lower case letters with hyphenation used to improve readability (e.g. ret-bct-pdu-header). Data Types in the ASN1. Always start with an upper case letter and may contain additional upper case letters to i... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 4.2.2 "Reserved" Fields and Values | Fields shown as Reserved BITSTRING (..) in the ASN.1 structures shall be set to zero by the sender and shall be ignored by the receiver. Values not allocated in distinguished value lists shall not be used by the sender and shall be ignored by the receiver. NOTE 1: Distinguished Value Lists of type Integer are being use... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 4.2.3 Boolean Variables | BOOLEAN variables shall be encoded as follows: TRUE ::= 1 FALSE ::= 0 |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 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.3.4 of ETSI TS 102 744-3-1 [6]. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 5 Adaptation Layer | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 5.1 Overview | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 5.1.1 Responsibilities | The Adaptation Layer is responsible for the following: • Registration Management: spot beam selection, system information handling, Non Access Stratum (NAS) system information notification, registration and deregistration (with the RNC), GPS position reporting and GPS position encryption. • Mobility Management Support:... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 5.2 Adaptation Layer use of lower layer Service Access Points | To provide a seamless interface between the satellite network Access Stratum and the UMTS Non-Access Stratum, functional equivalents for a number of UTRAN Radio Resource Control (RRC) messages have been defined. Each RRC message is mapped to an equivalent message for the Satellite Radio Interface. Table 5.1 provides an... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.8 Handover | Ack From UE 6.2.9 UEPositionRequest To UE 6.2.23 UEPositionResponse From UE 6.2.24 RegModeUpdate To UE 6.2.25 SystemInformation To UE 6.2.26 HandoverRequest To RNC 6.2.29 |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6 Adaptation Layer Protocol Data Units | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.0 General | The following clauses define the format of the Protocol Data Units which are used by the Adaptation Layer to signal its peer (AL-PDUs). Clause 6.1 specifies those AL-PDUs which are sent through Common Signalling (AL-ComPDUs), while clause 6.2 specifies those AL-PDUs which are sent on a UE Specific Signalling Connection... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1 Common Signalling Protocol Data Units (ALComPDUs) | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.0 General | Common Signalling PDUs are carried within a Common Protocol Data Unit (PDU) in the Bearer Control sub-layer, where the type of the Common Signalling PDU is carried within the ComSigType field within a Bearer Control PDU (see ETSI TS 102 744-3-1 [6]). ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 12 ALComPDU ::= CHOICE { em... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.1 PagingType1 | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.1.0 General | The PagingType1 Signalling PDU is used by the RNC when the UE is not registered to indicate that the UE should initiate the Registration process. The Adaptation Layer shall inform the Non Access Stratum of the event. The PDU is defined as below, with format shown in Figure 6.1. PagingType1 ::= SEQUENCE { cn-domain-iden... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.1.1 CNDomainIdentity | This parameter identifies the Core Network Domain, which originated the paging request. The parameter definition is the same as for the CNDomainIdentity Information Element (IE) specified in [3], clauses 10.3.1.1 and 11.3 as follows: CNDomainIdentity ::= INTEGER { cs-domain (0), ps-domain (1), bm-domain (2), } (0..3) |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.1.2 PagingCause | This parameter is also sent from the Core Network and hence follows the definition of the PagingCause IE in [3], clauses 10.3.3.22 and 11.3 as follows: PagingCause ::= INTEGER { terminatingConversationalCall (0), terminatingStreamingCall (1), terminatingInteractiveCall (2), terminatingBackgroundCall (3), terminatingHig... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.2 Register | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.2.0 General | The Register Common Signalling PDU is used by the UE to request the initiation of the registration process. Addressing is performed by the Bearer Control Layer using the Initial UE Identity. The Register Common Signalling PDU is defined as below, with structure as shown in Figure 6.2. Register ::= SEQUENCE { reg-ref Re... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.2.1 RegistrationReference | The reg-ref field (Registration-Reference) carries a sequence number generated by the UE used to synchronize the forward and return registration information. This information is used at the RNC to determine whether this is a repeat registration request or a new registration request. RegistrationReference ::= INTEGER (0... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.2.2 RIVersion | The RI-Version field contains the Radio Interface (RI) version number to which the software within the UE was designed to operate. Note that the RI-Version number is used to refer to all layers within the Access Stratum. The interpretation of the RI-Version number is shown in Table 6.1. RIVersion ::= INTEGER { syst-ini... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.2.3 RegistrationCause | This parameter specifies the reason for the registration message. Currently, only normal registration and registration due to emergency call are defined but other values may be allocated in the future. RegistrationCause ::= INTEGER { normal-registration (0), emergency (1) } (0..63) |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.2.4 UEClass | The ue-class field identifies the physical capabilities of the UE (i.e. transmitter EIRP, receiver G/T). The UEClass data structure is defined as follows: UEClass ::= INTEGER { land-A3 (1), land-A4 (2), land-A5 (3), aeronautical-lga (4), maritime-lga (5), aeronautical-high-gain (6), aeronautical-intermediate-gain (7), ... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3 RegisterAck | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.0 General | The RegisterAck Common Signalling PDU is used by the RNC to confirm the completion of the registration process. Addressing is performed by the Bearer Control Layer and is based upon the Initial UE Identity. The Register-Ack Common Signalling PDU is defined as below, with structure as shown in Figure 6.3. RegisterAck ::... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.1 BcnID | The parameter bearer-conn-id is used to uniquely identify a connection within the context of a satellite. BcnID ::= INTEGER (0.. 16777215); Value 0x000000 is reserved. Values in the range 0xFFFFF0 to 0xFFFFFF are reserved for Cell Broadcast connections. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.2 BcnType | The bearer-conn-type field defines the properties of the Bearer Connection and in the RegisterAck message is always set to 2 (Acknowledged Mode, In Sequence Delivery) since the RegisterAck message causes the UE specific signalling connection to be established. For a full specification of BcnType see clause 6.2.2.1. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.3 NumParam | This parameter is used to define the number of bearer connection parameters being transferred as Bearer Connection AVPs in the bcn-param-list. ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 16 NumParam ::= INTEGER (0..15) |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.4 BcnParamList | The bcn-param-list carries a set of parameters for the connection being initiated as well as allowing for the transport of Adaptation Layer AVPs. The list of parameters is dependent upon the connection being initiated. The parameters are transported in BCnAVPs which are described in detail in clause 6.4 while the Adapt... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.5 CtrlFlags | This parameter contains a set of control flags which are defined as follows: CtrlFlags ::= SEQUENCE { bct-epdu-follows BOOLEAN, reserved BIT STRING (SIZE(3)) } The bct-epdu-follows flag indicates whether any Bearer Control Embedded PDUs are present. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.6 BctType | The bct-type field contains the bearer control type to which the UE-specific signalling connection is to be attached. If the bct-type field is different to the current Bearer Control process type, then a handover to a new Bearer Control is taking place. Values are defined as follows: BctType ::= INTEGER { current-beare... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.7 BctID | The bct-id field identifies the specific bearer control process to which the UE-specific signalling connection is to be attached. If this is different to the current bct-id transferred in the Bulletin Board, then a handover to a new bearer control is taking place. BctID ::= INTEGER (0..15) ETSI ETSI TS 102 744-3-5 V1.1... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.8 BCtEPDU | This parameter contains a sequence of Bearer Control Embedded Signalling PDUs which are formulated within the Bearer Control Layer at the RNC and transported with an Adaptation Layer Signalling PDU. The BCtEPDU contains Bearer Control specific configuration information which is to be passed to the Bearer Control Layer ... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.3.9 RegistrationMode | The reg-mode parameter is used by the RNC to control the behaviour of the UE and restrict the actions that the UE may take. For a detailed description of the behaviour related to reg-mode see ETSI TS 102 744-3-6 [8]. The RegistrationMode is defined as follows: RegistrationMode ::= INTERGER { conditional-registration (0... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.4 RegisterRej | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.4.0 General | The RegisterRej Common Signalling PDU is used by the RNC to indicate the failure of the registration process. Addressing is performed by the Bearer Control Layer and is based upon the Initial UE Identity. The Register-Rej Common Signalling PDU is defined as below, with structure as shown in Figure 6.4. RegisterRej ::= ... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.4.1 RejectionCause and ProtocolErrorCause | The cause parameter may either contain a rejection cause or a protocol error cause value. The rej-cause parameter is of type RejectionCause which is defined as follows: RejectionCause ::= INTEGER { rnc-failure (1) congestion (2), unsupported-ai-version(3), unsupported-ue-class(4), usim-required(5) } (0..255) -- valid r... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.5 DeregisterCommon | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.5.0 General | The DeregisterCommon Common Signalling PDU is broadcast by the RNC to deregister all Ues on a particular bearer. To deregister individual Ues, the Deregister message is sent as an AL-Sig-PDU (see clause 6.2.27). The DeregisterCommon Common Signalling PDU is defined as below, with structure as shown in Figure 6.5. Dereg... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.1.5.1 DeregistrationCause and ProtocolErrorCause | The cause parameter may either contain a deregistration cause or a protocol error cause value. The deregistration-cause parameter in the DeregisterCommon message is of type DeregistrationCause and defined as follows: DeregistrationCause ::= INTEGER { register-complete-not-received (1), service-area-barred (2), position... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.0 General | UE-Specific Signalling Protocol Data Units (ALSignallingPDUs) are encapsulated in one or a sequence of BCn-PDUs and are transported over the radio interface in Acknowledged Mode. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.1 ALSignallingPDUStructure | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.1.0 General | The general structure of the ALSignallingPDU is as shown below in Figure 6.6 (without integrity protection) and Figure 6.7 (with integrity protection): (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 al-sig-type Octet 1 0 alpd reserved Octet 2 Octet 3 message Octet n Figure 6.6: ALSignallingPDU Structure (without Integrity Protecti... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.1.1 ALSignalType | This parameter defines the Adaptation Layer Signalling Protocol Data Unit type. For the satellite network, the value for the PDU type is constrained to the range (128..255). ALSignalType ::= INTEGER { empty-al-sig (128), establish (129), establish-ack (130), release (131), release-ack (132), modify (133), modify-ack (1... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.1.2 IntegrityCheckIncluded | The value of the BOOLEAN integrity-check-included (ic) flag determines whether integrity protection information is included within the PDU. IntegrityCheckIncluded ::= BOOLEAN |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.1.3 ALProtocolDiscriminator | The alpd parameter facilitates the routing of messages in the Adaptation Layer and is of type ALProtocolDiscriminator which is defined as follows: ALProtocolDiscriminator ::= INTEGER { regm (1), gmmh (2), mmh (3), rbc-ps (4), rbc-cs (5) } (0..7) See ETSI TS 102 744-3-6 [8] for a detailed description of the usage of thi... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.1.4 ALMsgSeqNumber | The parameter al-msg-seq-no is incremented each time an integrity protected ALSignallingPDU is sent. It is used as an input parameter to the integrity protection algorithm and is of type ALMsgSeqNumber as defined below: ALMsgSeqNumber ::= INTEGER (0..15) See ETSI TS 102 744-3-6 [8] for a detailed description of the usa... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.1.5 Message | The parameter message represents individual al-sig-pdu messages listed in the ALSignallingPDU structure. The data structures for al-sig-pdu messages are defined in clauses 6.2.2 to 6.2.28. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.1.6 MACIntegrity | The parameter mac-I carries the Message Authentication Code for Integrity as specified in [1] within an integrity protected ALSignallingPDU is sent and is of type MACIntegrity as defined below: MACIntegrity ::= BIT STRING (SIZE (32)) |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.2 Establish | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.2.0 General | This message is used by the RNC to establish a new Bearer Connection (Radio Bearer) in the User Plane. The PDU is defined as below, with structure as shown in Figure 6.8. Establish ::= SEQUENCE { bearer-conn-id BcnID, bearer-conn-type BcnType, num-param NumParam, bcn-param-list ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10)... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.2.1 BcnType | The bearer-conn-type field defines the properties of the Bearer Connection and is specified as follows: BcnType ::= INTEGER { tm-bidir-no-err (0), tm-bidir-err (1), am-bidir-in-seq (2), am-bidir-out-seq (3), um-bidir (4), um-unidir (6) }(0..15) Values for BcnType are interpreted as shown in Table 6.2. Table 6.2: Interp... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.2.2 TransactionID | This parameter is used to uniquely associate a response or acknowledgement with a request, and allows multiple requests to be in transit at any one time. TransactionID ::= INTEGER (0..15) |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.3 EstablishAck | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.3.0 General | This message is used by the UE to acknowledge the establishment of new Bearer Connections (Radio Bearer) in the User Plane. The PDU is defined as below, with structure as shown in Figure 6.9. EstablishAck ::= SEQUENCE { bearer-conn-id BcnID, ctrl-flags CtrlFlags, trans-id TransactionID, adaptation-layer-avp-list Adapta... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.3.1 AdaptationLayerAVPList | The parameter adaptation-layer-avp-list is of type AdaptationLayerAVPList which is defined as follows: AdaptationLayerAVPList ::= SEQUENCE { adaptation-layer-avp AdaptationLayerAVP } The data type AdaptationLayerAVP is defined in clause 6.3. ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 25 |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.4 Release | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.4.0 General | This message is used by the RNC to release a Bearer Connection (Radio Bearer) and associated Bearer Connection and Bearer Control Layer resources. The PDU is defined as below, with structure as shown in Figure 6.10. Release ::= SEQUENCE { bearer-conn-id BcnID, ctrl-flags CtrlFlags, trans-id TransactionID, rel-cause Rel... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.4.1 ReleaseCause | This parameter is used to specify a reason for sending the Release message. ReleaseCause ::= INTEGER { normal-release-cn-initiated (0), rnc-security-failure (1) } (0..255) ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 26 |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.5 ReleaseAck | This message is used by the UE to acknowledge the release of a Bearer Connection (Radio Bearer) and associated resources. The PDU is defined as below, with structure as shown in Figure 6.11. ReleaseAck ::= SEQUENCE { bearer-conn-id BcnID, ctrl-flags CtrlFlags, trans-id TransactionID } (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.6 Modify | This message is used by the RNC to modify the Quality of Service attributes of a particular Bearer Connection. The PDU is defined as below, with structure as shown in Figure 6.12. Modify ::= SEQUENCE { bearer-conn-id BcnID, bearer-conn-type BcnType, numparam NumParam, bcn-param-list BcnParamList, ctrl-flags CtrlFlags, ... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.7 ModifyAck | This message is used by the UE to acknowledge the modification the Quality of Service attributes of a particular Bearer Connection. The PDU is defined as below, with structure as shown in Figure 6.13. ModifyAck ::= SEQUENCE { bearer-conn-id BcnID, ctrl-flags CtrlFlags, trans-id TransactionID, adaptation-layer-avp-list ... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.9 HandoverAck | This message is used by the UE to Acknowledge the Handover of a Bearer Connection between Bearer Controls or alteration in the characteristics of a Bearer Control. The PDU is defined as below, with structure as shown in Figure 6.15. HandoverAck ::= SEQUENCE { ctrl-flags CtrlFlags, trans-id TransactionID } (MSB) Bit No ... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.10 RegisterComplete | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.10.0 General | This message is used by the UE to provide the RNC with the UMTS security parameter start for each Core Network service domain and UE capability information. The PDU is defined as below, with structure as shown in Figure 6.16. ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 29 RegisterComplete ::= SEQUENCE { reg-ref Registrat... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.