hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6d7b23174a450f0b9f5d99cf05b01fc9 | 102 744-1-4 | 5 Overview of IETF RFC References | |
6d7b23174a450f0b9f5d99cf05b01fc9 | 102 744-1-4 | 5.0 General | The following tables list all the IETF RFC references used in the Family SL specification, indicating which IETF RFC specification applies or is replaced by a Family SL technical specification for the satellite radio interface. |
6d7b23174a450f0b9f5d99cf05b01fc9 | 102 744-1-4 | 5.1 Normative references | Table 5.1: Normative IETF RFC References IETF RFC Specification Reference IETF RFC Specification Short Title Referenced in Family-SL Part-subpart IETF RFC Applicability or Indication of Replacement by Family SL Specification RFC 1661 (1994) [32] The Point-to-Point Protocol (PPP) ETSI TS 102 744-1-1 [36] ETSI TS 102 744... |
6d7b23174a450f0b9f5d99cf05b01fc9 | 102 744-1-4 | 5.2 Informative references | Table 5.2: Informative IETF RFC References IETF RFC Specification Reference IETF RFC Specification Short Title Referenced in Family-SL Part-subpart IETF RFC Applicability or Indication of Replacement by Family SL Specification RFC 2507 (1999) [i.10] IP Header Compression ETSI TS 102 744-3-5 [42] The RFC Specification i... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 1 Scope | The present document provides an overview of the Family SL radio interface between the Radio Network Controller (RNC) and the User Equipment (UE). The Family SL radio interface operates in spectrum allocated to mobile satellite services (see ETSI TS 102 744-2-1 [i.7], clauses 5.1.2 and 6.1.2). |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 2 References | |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 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... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 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... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 3 Symbols and abbreviations | |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 3.1 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 744-1-4 [1], clause 3 apply. |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 744-1-4 [1], clause 3 apply. |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 4 Introduction | |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 4.1 Radio interface layering | |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 4.1.0 General | The satellite radio interface is carried over a satellite link and consists of the Non-Access Stratum and Access Stratum layers. The Non-Access Stratum is essentially unchanged from the UMTS Non-Access Stratum, as defined in ETSI TS 124 007 [i.4] and ETSI TS 124 008 [i.5], with some functional extensions to support new... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 4.1.1 Control plane protocol stack | The Control Plane of the protocol stack is shown in Figure 4.1. The Access Stratum and the Non-Access Stratum are separately indicated in the diagram. The parts of the protocol stack that are modified for the Family SL satellite link relative to the standard 3GPP protocols are described in ETSI TS 102 744-1-1 [i.6], cl... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 4.1.2 User plane protocol stack | The protocol stack for the User Plane of the Packet Switched Domain is shown in Figure 4.2. Figure 4.2: Packet Switched User Plane Protocol Stack Layering For the Circuit Switched Domain, the lower layers (L1, BCt and BCn) of the protocol stack are identical, however, the PDCP and PPP/IP layers are replaced by the appr... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 4.2 SDUs and PDUs | Each of the layers exchanges a set of Protocol Data Units (PDUs) with its peer using the capabilities of the lower layers to transport each PDU. Each of the peer-layer entities exchanges a sequence of control messages called Signalling Data Units (SDUs) for the purpose of establishing, maintaining and terminating a con... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 5 Physical Layer | |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 5.1 Shared Access Bearers | The Shared Access Bearers refer to specific physical bearers which support the transfer of data between the RNC and the UEs. Shared Access Bearers can support more than one connection at a time: the mechanisms for sharing of the resource involve a combination of techniques, where each individual packet transferred over... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 5.2 Physical Layer Roles | At the transmitter, the physical layer is responsible for the correct encoding, scrambling and interleaving of the frames or slots, and modulating and filtering the sequence of symbols and transmitting these at the correct frequency, time and power level. At the receiver, the physical layer is responsible for the corre... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 5.3 Physical Layer Characteristics | |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 5.3.1 Range of Bearer Types and Subtypes | The physical layer defines a range of bearer types; operating with a range of modulation schemes (as described below) in the forward and return directions. In the forward direction, the following bearer types are available: • QPSK bearer operating at a symbol rate of 8,4 kBd (for Global Beam Signalling only); • QPSK be... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 5.3.2 Variable Coding Rate | Each bearer type comprises a set of subtypes with a range of different coding rates. This is achieved by puncturing the turbo-code generated parity streams using one of a number of pre-defined puncturing matrices, such that each subtype has a different coding rate. The steps in the coding rate provide nominally 1dB ste... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 5.3.3 Unique Words | The coding rate used in each burst is signalled by the choice of unique word used for the burst. This allows each burst to be correctly demodulated and decoded without a-priori knowledge of the coding rate. Distributed Unique Words are used on some return bursts to improve the performance of the synchronization algorit... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6 Bearer Control Layer operation | |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.1 Role of the Bearer Control Layer | The Bearer Control Layer is responsible for controlling the access to the physical layer (channel resource) for each of the connections which are established. When User Equipment (UEs) transmit on the physical layer, the UE physical layer characteristics need to be continuously monitored, and corrected where necessary.... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.2 Initial Timing Correction | The propagation path for the radio signals can differ in length considerably, owing to the variance in geographical locations of the UEs. To ensure that the UE transmissions do not interfere with each other, the radio interface provides a guard time between UE transmissions and the RNC provides timing correction inform... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.3 Subsequent Timing Corrections | Once the initial timing offsets have been corrected, the timing of transmissions from each individual UE is continuously monitored, and, when necessary, a differential correction mechanism is provided. A timing uncertainty rate may be provided to the UE by the RNC whenever timing correction information is provided. Thi... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.4 Coding Rate and Transmit Power Adjustments | The Bearer Control Layer uses coding rate and/or transmit power adjustments to maintain the packet error rate (PER) of both the forward and return links at a level appropriate to maintain the QoS of each connection. This uses a link adaptation function in the Bearer Control Layer, which evaluates the signal-to-noise ra... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.5 Admission Control | Admission control is the process of determining whether sufficient resources exist at the RNC to allow a new connection to be accepted. Whenever a connection is requested, the quality of service parameters for the connection is used to determine whether the aggregate Quality of Service commitments would exceed a thresh... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.6 Scheduling | Scheduling is the process of allocating resources to each connection being serviced on the set of bearers being managed by the RNC. The scheduling process is driven primarily by the connection Quality of Service parameters, together with information about the state of the queues for each connection being serviced. Depe... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.7 Packing and Unpacking of Bearer Control PDUs | The Bearer Control process is responsible for creating the frame or slot structure necessary for transmission on the physical layer, including calculation of Cyclic Redundancy Check (CRC) bits, and specifying the timing for transmission to the hardware. In addition, the Bearer Control process is responsible for checkin... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.8 Ciphering | The Bearer Control Layer carries out the ciphering and de-ciphering of PDUs in Transparent Mode only. |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.9 Support for Sleep Mode | The Bearer Control process is responsible for managing the sleep-mode operation of UEs. This involves transmission of sleep-mode parameters during registration, and the control of transmission of signalling and control information to UEs which are operating in sleep-mode. The sleep-mode parameters being used by a UE ma... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.10 Different UE Classes | The Bearer Control Layer is responsible for support of UEs which have different capabilities. A set of UE classes are defined (see ETSI TS 102 744-2-2 [i.8]), which are primarily differentiated based on the antenna size, available transmitter EIRP and receiver G/T. Furthermore, the types of physical bearers may be rest... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 6.11 Transmission of System Information | The Bearer Control Layer is also responsible for the transmission of System Information. System Information can be grouped into: • Non-Access Stratum (NAS) System Information relevant to UMTS Layer 3 such as Location and Routing Area Codes, Network Mode of Operation and Attach Flag. • Access Stratum (AS) System Informa... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 7 Bearer Connection Layer operation | |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 7.1 Role of the Bearer Connection Layer | The Bearer Connection Layer performs a number of functions: • buffering and flow control of information from the interface to the layer above; • QoS policing (shaping of information streams where required); • segmentation and reassembly of information; • Automatic Repeat Request (ARQ) (if required for the particular co... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 7.2 Buffering and Flow Control | The Bearer Connection Layer contains an input buffer for the Protocol Data Units (PDUs) from the layer above (Adaptation Layer, PDCP Layer or an entity in the Circuit Switched Domain e.g. voice codec). A header is added to each PDU that allow signalling and data to be discriminated and is also used to transmit addition... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 7.3 QoS Policing | Each Connection is established with a certain set of Quality of Service (QoS) parameters (which may be the default set). Every PDU which is received from the layer above is tagged with a required delivery time (and other information used for local management) which should be achieved in order to meet the QoS commitment... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 7.4 Segmentation and Reassembly | The Bearer Connection Layer can transfer large PDCP layer PDUs (maximum of 2 047 octets). These larger PDUs do not fit within the transmit frame size of any particular shared access bearer, and the PDUs therefore need to be segmented by the transmitting connection layer process, and reassembled within the receiving con... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 7.5 ARQ | The Bearer Connection Layer supports an optional ARQ mechanism to provide reliable transmission, whereby information is delivered error-free and in-sequence. The ARQ selectively requests retransmission of particular segments which are errored or otherwise missing from the received information stream. The ARQ mechanisms... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 7.6 Ciphering | The Bearer Connection Layer also carries out the ciphering and de-ciphering of PDUs in Acknowledged Mode and Unacknowledged Mode (i.e. the non-transparent modes). Ciphering is controlled by the Adaptation Layer. |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 7.7 Connection QoS Parameters | Each connection is associated with a set of QoS parameters , which include the following: • Rate Parameters: Mean Rate and Peak Rate; • Delay Parameters: Target Latency and Discard Latency; and • Connection Type and Priority. NOTE: The Connection QoS parameters are distinct from the UMTS QoS RAB Parameters specified in... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 7.8 Connection types | Each connection has a specific type, with point-point connections being characterized as either non-ARQ or ARQ. Connections with ARQ require additional overhead, and shall only forward information when it has been completely received. Connections which do not operate an ARQ mechanism may be configured to discard incomp... |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 8 Adaptation Layer operation | |
ea5db4b8814e2549afe5d755c62fb04a | 102 744-1-3 | 8.1 Role of the Adaptation Layer | The Adaptation Layer is responsible for the following: • Registration Management: responsible for spot beam selection, system information handling, NAS system information notification, performs registration and deregistration procedures (with RAN), control of ciphering for the UE specific signalling connection, integri... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 1 Scope | The present document provides an overview of the Family SL system operation, and describes fundamental UMTS elements such as mobility management, numbering and addressing, and idle mode behaviour as they apply to the Family SL satellite network. In general, these elements are the same for both terrestrial UMTS and the ... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 2 References | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 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... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 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... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 744-1-4 [5], clause 3 apply. ETSI ETSI TS 102 744-1-2 V1.1.1 (2015-10) 9 |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 4 Stratum introduction | For reference purposes, the functional aspects of the Family SL satellite network are shown in Figure 4.1. The Non-Access Stratum (NAS) groups together all protocols between the UE and the CN. The Access Stratum is divided into an Usl Stratum, which groups all protocols between the UE and RNS and an Iu Stratum, which g... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5 Mobility Management (MM) | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.1 General principles | UMTS Layer 3 in the Control Plane contains two primary sublayers: Mobility Management (MM) and Connection Management (CM); see ETSI TS 124 007 [i.3], Figure 5.6. The CM sublayer controls access to circuit switched, packet switched, messaging, and other supplementary services. The MM sublayer is primarily responsible fo... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.2 RRC States (Idle and Connected Mode) | In terrestrial UMTS, the terms "idle mode" and "connected mode" refers to states of the Radio Resource Control (RRC) protocol layer (see ETSI TS 125 331 [i.5]). The RRC protocol [i.5] is not directly implemented in the satellite network; however, the Adaptation Layer (specifically the REGM entity, see ETSI TS 102 744-3... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.3 UE and Network Operation Modes | A UE can operate in one of three modes: • PS/CS Mode: The UE is attached to both the PS domain and CS domain, and the UE is capable of simultaneously operating PS services and CS services. This mode of operation is equivalent to the GSM GPRS Class-A mode of operation. • PS mode: The UE is attached to the PS domain only... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4 Mobility Management Service States | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.0 General | Each domain has its own service state machine (see Figure 5.3). An UE, that is supporting both CS services and PS services, has a CS service state machine and a PS service state machine. For every UE, there is a corresponding PS state machine and CS state machine in the SGSN and MSC respectively. The two peers of the s... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.1 PS Domain Service State Machine | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.1.0 General | The PS service state machine is called Packet Mobility Management (or PMM). |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.1.1 PMM-DETACHED State | In the PMM-DETACHED state there is no communication between the UE and the SGSN. The UE and SGSN PMM contexts hold no valid location or routing information for the UE. The UE MM state machine does not react on system information related to the SGSN. The UE is not reachable by a SGSN, as the UE location is not known. In... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.1.2 PMM-IDLE State | In the PMM-IDLE state, a complete PS signalling connection is not established between the UE and SGSN, but the UE and SGSN have (previously) established PMM contexts. The UE location is known in the SGSN with an accuracy of a routing area. Paging is needed in order to reach the UE, e.g. for signalling. The UE shall per... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.1.3 PMM-CONNECTED State | The UE location is known in the SGSN with an accuracy of a serving RNC. In the PMM-CONNECTED state, the location of the UE is tracked by the serving RNC. The UE performs the (GMM) Routing Area Update procedure if the RA changes (or if the RAI in the System Information broadcast changes). When an UE and a SGSN are in th... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.1.4 State Transitions and Functions | Figure 5.4 shows the PMM state machine in both the UE and SGSN. Note that the PMM-IDLE and PMM- CONNECTED states are independent of the Session Management state. The activation or deactivation of PDP Contexts by the SM entity does not affect the PMM state. Figure 5.4: PS Domain Service State Machine in UE and SGSN PMM-... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.1.5 Periodic Routing Area Update Timer | Periodic Routing Area Updating (RAU) is used to periodically notify the availability of the UE to the network. The procedure is controlled in the UE by the Periodic RAU Timer, T3312. The value of timer T3312 is sent by the CN to the UE in the messages (GMM) Attach Accept and (GMM) Routing Area Update Accept. The value ... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.1.6 Mobile Reachable Timer | The Mobile Reachable Timer (MRT) function monitors the periodic RAU procedure in the SGSN. The MRT shall be slightly longer than the periodic RAU timer used by the UE. The MRT is stopped when the PMM-CONNECTED state is entered. The MRT is reset and started when the PMM-IDLE state is entered (i.e. the MRT is relevant to... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.2 CS Domain Service State Machine | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.2.0 General | The CS service state machine has the same states as the PS service state machine (PMM) but the state transitions are different (see Figure 5.5). In the present document, the CS service state names follow the convention from ETSI TS 123 221 [i.2] and have the prefix "CMM". Figure 5.5: CS Domain Service State Machine in ... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.2.1 CMM-DETACHED State | In the CMM-DETACHED state there is no communication between the UE and the MSC. The UE and MSC MM contexts hold no valid location information for the UE. The UE is not reachable by a MSC, as the UE location is not known. In order to establish MM contexts in the UE and the MSC, the UE shall perform the IMSI Attach proce... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.2.2 CMM-IDLE State | In the CMM-IDLE state, a complete CS signalling connection is not established between the UE and MSC, but the UE and MSC have established MM contexts. The UE location is known in the MSC with an accuracy of a location area. Paging is needed in order to reach the UE. The UE shall perform the Location Area Update procedu... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.4.2.3 CMM-CONNECTED State | In the CMM-CONNECTED state, a complete CS signalling connection is established between the UE and MSC, and the UE location is known in the MSC with an accuracy of a serving RNC. In the CMM-CONNECTED state, the location of the UE is tracked by the serving RNC. The UE does not perform the Location Area Update procedure, ... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.5 Connection Maintenance | In UMTS, whenever an Iu connection (RNC to CN) is released (using the RANAP Iu Release elementary procedure), the corresponding radio interface connection (UE to RNC) is also released as defined in ETSI TS 125 413 [4]. Release of the Iu signalling connection for a particular CN domain (PS/CS) changes the service state ... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 5.6 Mobility Management Procedures | The GMM protocol operates between the UE and SGSN and is supported by a UE which operates either in the PS/CS mode or the PS (only) mode. Similarly, the MM protocol operates between the UE and the MSC/VLR and is supported by a UE which operates either in the PS/CS mode or the CS (only) mode. GMM and MM procedures for t... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6 Numbering, Addressing and Identification | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.0 General | The Compact Syntax Notation (CSN.1) is used in this clause to describe the structure of information elements in protocol messages. See Annex B of ETSI TS 123 003 [1]. CSN.1 descriptions are typeset in Courier. |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1 Non-Access Stratum | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.0 General | Numbering, addressing, and identification schemes in the Non-Access Stratum are the same as in the UMTS Non-Access Stratum, and, in general, ETSI TS 123 003 [1] applies in its entirety except where noted otherwise in this clause. |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.1 PLMN Identifier (PLMN ID) | ETSI TS 123 003 [1], clause 12.1 applies. The ITU assigns the shared MCC 901 for Global Mobile Satellite Systems (GMSS) - see Recommendation ITU-T E.212 [i.7]. A particular GMSS network is identified by its Mobile Network Code (MNC). Note that for GMSS, the MCC and MNC for GMSS do not relate to the country of domicile ... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.2 International Mobile Subscriber Identity (IMSI) | ETSI TS 123 003 [1], clause 2.2 applies. 6.1.3 Temporary Mobile Subscriber Identity (TMSI) and Packet Temporary Mobile Subscriber Identity (P-TMSI) ETSI TS 123 003 [1], clauses 2.1, 2.4, and 2.7 refer. 6.1.4 International Mobile Station Equipment Identity/Software Version (IMEI/IMEISV) ETSI TS 123 003 [1], clause 6.2 a... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.5 Location Area Identification (LAI) | ETSI TS 123 003 [1], clause 4.1 applies. The Location Area Identifier (LAI) is composed from the following information elements: • Mobile Country Code (MCC): see definition for IMSI. • Mobile Network Code (MNC): see definition for IMSI. • Location Area Code (LAC): The LAC identifies a location area within a PLMN. <LAC>... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.6 Routing Area Identification (RAI) | ETSI TS 123 003 [1], clause 4.2 applies. The RAI is composed from the following information elements: • Location Area Identity (LAI): as defined in clause 6.1.5. • Routing Area Code (RAC): The RAC identifies a routing area within a location area. <RAC> ::= <OCTETSTRING(1)> <RAI> ::= <LAI><RAC> = <MCC><MNC><LAC><RAC> In... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.7 Mobile Station International PSTN/ISDN Number (MSISDN) | ETSI TS 123 003 [1], clause 3.3 applies. The MS International ISDN (MSISDN) numbers are allocated from the Recommendation ITU-T E.164 numbering plan [6], see also Recommendation ITU-T E.213 [i.18]. The MS international ISDN number is composed from the Country Code (CC), the National Destination Code (NDC),and the Subsc... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.8 Mobile Station Roaming Number (MSRN) | ETSI TS 123 003 [1], clause 3.4 applies. |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.9 Mobile Station International Data Number | ETSI TS 123 003 [1], clause 3.5 applies. |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.10 IPv4 Address | ETSI TS 123 003 [1], clause 3.7 applies. |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.11 IPv6 Address | ETSI TS 123 003 [1], clause 3.8 applies. |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.1.12 Access Point Name | ETSI TS 123 003 [1], clause 9 applies. |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.2 Access Stratum (Usl Stratum) | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.2.1 UE Identification | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.2.1.0 General | The UE identification method used in the Usl Stratum depends on the RRC state. |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.2.1.1 RRC-IDLE Mode | In the RRC-IDLE Mode, no UE-Specific Signalling Connection is established between the UE and the RNC. A Non-Access Stratum UE identifier is used in Registration messages to identify a particular UE. The NAS UE identifier is provided to the Usl Stratum in the request from GMM or MM to establish the UE-Specific Signallin... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.2.1.2 RRC-CONNECTED Mode | In the RRC-CONNECTED mode, the Registration procedure has been successfully completed and a UE-Specific Signalling Connection has been established between the UE and the RNC. During the Registration procedure, the RNC assigns a unique Bearer Connection ID (BCnID) to the UE-Specific Signalling connection. The BCnID iden... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.2.2 Radio Resource to Network Layer UE Identity Association | For the purpose of paging coordination, the RNC shall maintain an internal routing table that associates the identity of a particular UE with the corresponding BCnID for the UE-Specific Signalling Connection to that UE. The IMSI is transferred from the CN to the RNC using the RANAP Common ID elementary procedure. When ... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.2.3 Logical Radio Interface Connection Identifiers | The UE-Specific Signalling Connection (Control Plane) and Data Connections (User Plane) are assigned Bearer Connection Identifiers (BCnID) by the RNC Adaptation Layer. The BCnID is then associated with a translated Bearer Connection Identifier (tBCnID) when the connection is attached to a specific Shared Access Bearer.... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.2.4 Other Identifiers | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.2.4.1 Spot Beam ID | Spot Beam ID is an 8-bit identifier used primarily in the System Information (Bulletin Board, see clause 7). Every satellite beam (global, regional spot, and narrow spot) is assigned a different Spot Beam ID value. The scope of Spot Beam ID is a satellite and is therefore not unique throughout the satellite network (un... |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.3 Access Stratum (Iu Stratum) | |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.3.0 General | As with the Non-Access Stratum, the numbering, addressing, and identification schemes in the Iu Stratum are the same as for UMTS. ETSI TS 123 003 [1] and ETSI TS 125 413 [4] apply in their entirety. This clause highlights the areas where the UMTS and Family SL concepts differ. |
ad304659c6d5d3b83178e60f049cf355 | 102 744-1-2 | 6.3.1 PLMN Identifier (PLMN ID) | ETSI TS 123 003 [1], clause 12.1 applies. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.