hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.1.3 LLGMM-SUSPEND-REQ
| All LLC links will cease sending PDUs. The parameter page indicates that data shall be sent if available and therefore paging shall be needed. Or the cause indicates that data shall not be sent until a RESUME-REQ is received.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.1.4 LLGMM-RESUME-REQ
| Normal LLC frame sending and reception is possible again.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.1.5 Void
| |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.1.6 Void
| |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.1.7 LLGMM-PAGE-IND
| Requires to send a paging message to the mobile station.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.1.8 LLGMM-PAGE-RESP-IND
| A paging response has been received from the mobile.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.1.9 LL-UNITDATA-REQ
| Request to send a SMM message in unacknowledged mode to the peer entity.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.1.10 LL-UNITDATA-IND
| A SMM message in unacknowledged mode has been received from the peer entity.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.1.11 LLGMM-STATUS-IND
| Indication used by LLC to transfer lower layer failures to the GMM sublayer.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.2 Service primitives for LLSMS-SAP
| Table 10.4.2: Primitives and Parameters at LLSMS-SAP - network side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
LL-UNITDATA-REQ
TLLI, SMS-CP-PDU, protect, cipher
10.4.2.1
LL-UNITDATA-IND
TLLI, SMS-CP-PDU
10.4.2.2
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.2.1 LL-UNITDATA-REQ
| An LLC UI frame will be sent to the peer entity.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.4.2.2 LL-UNITDATA-IND
| An LLC UI frame has been received from the peer entity.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5 Services provided by the GMM for GPRS services
| The GPRS Mobility Management (GMM) sublayer provides services to the Session Management (SM) entity and the Short Message Service Support (SMS) entity for message transfer.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.1 Service primitives for GMMSM-SAP
| Table 10.5.1: Primitives and Parameters at GMMSM-SAP - network side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMSM-RELEASE-IND
-
10.5.1.1
GMMSM-UNITDATA-REQ
SM-PDU
10.5.1.2
GMMSM-UNITDATA-IND
SM-PDU
10.5.1.3
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.1.1 GMMSM-RELEASE-IND
| The GPRS mobility management informs the session management that the MS has been GPRS detached, e.g. by timer expiry, and therefore the PDP contexts are not valid anymore.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.1.2 GMMSM-UNITDATA-REQ
| The GMM is requested to forward a SM PDU to LLC in order to send it in unacknowledged more to the peer entity.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.1.3 GMMSM-UNITDATA-IND
| The GMM forwards a SM PDU, which has been received in unacknowledged mode via LLC from the peer entity.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.2 Service primitives for PMMSMS-SAP
| Table 10.5.2: Primitives and Parameters at PMMSMS‑SAP ‑ Network side
PRIMITIVES
PARAMETERS
(message, info elements of message, other parameters)
REFERENCE
PMMSMS_REL_REQ
-
10.5.2.1
PMMSMS_ERROR _IND
cause
10.5.2.2
PMMSMS_UNITDATA_REQ
SMS-PDU
10.5.2.3
PMMSMS_UNITDATA_IND
SMS-PDU
10.5.2.4
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.2.1 PMMSMS_REL_REQ
| The GMM is requested to release of a PS signalling connection.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.2.2 PMMSMS_ERROR_IND
| The GMM indicates that a PS signalling connection has been released.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.2.3 PMMSMS_UNITDATA_REQ
| The GMM is requested to forward a SMS PDU in order to send to the peer entity.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.2.4 PMMSMS_UNITDATA_IND
| Indication used by GMM to transfer the received data to the GSMS entities.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.3 Service primitives for GMMSS-SAP
| Table 10.5.3: Primitives and Parameters at GMMSS-SAP - network side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMSS-RELEASE-IND
-
10.5.3.1
GMMSS-UNITDATA-REQ
SS-PDU
10.5.3.2
GMMSS-UNITDATA-IND
SS-PDU
10.5.3.3
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.3.1 GMMSS-RELEASE-IND
| The GPRS mobility management informs the Supplementary service that the MS has been GPRS detached, e.g. by timer expiry.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.3.2 GMMSS-UNITDATA-REQ
| The GMM is requested to forward a SS PDU to lower layer in order to send it to the peer entity.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.5.3.3 GMMSS-UNITDATA-IND
| The GMM forwards a SS PDU, which has been received from the peer entity.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.6 Services provided by the Radio Resource Management entity for CTS on the fixed part
| In addition to services described in clause 10.1, the CTS Radio Resource Management (CTS‑RR) inside the RR sublayer provides services to the CTS Mobility Management entity (CTS‑MM).
The CTS‑RR services are used for:
- alive check;
- hunting;
- group alerting.
The CTS Radio Resource Management services are represen... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.6.1 Service primitives
| Table 10.6: Primitives and Parameters at the RR‑SAP – Fixed part side
PRIMITIVES
PARAMETERS
REFERENCE
RR_CTS_ALIVE_CHECK_REQ
CTSMSI
10.6.1.1
RR_ CTS_ALIVE_CHECK_IND
Cause
10.6.1.2
RR_ CTS_HUNTING_REQ
‑
10.6.1.3
RR_ CTS_GROUP_ALERTING_REQ
CTSMSI, display
10.6.1.4
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.6.1.1 RR_ CTS_ALIVE_CHECK_REQ
| Request used by the CTS Mobility Management entity to request an alive check.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.6.1.2 RR_ CTS_ALIVE_CHECK_IND
| Indication to the CTS Mobility Management entity on the results of the alive check.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.6.1.3 RR_ CTS_HUNTING_REQ
| Request to hunt the mobiles.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 10.6.1.4 RR_ CTS_GROUP_ALERTING_REQ
| Request to alert a group of mobiles.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11 L3 Messages
| This clause specifies the generic methods used in the layer 3 protocol specifications to describe messages. It define in particular a generic message structure, that of the "standard L3 messages". Not all messages in layer 3 protocols follow this structure, but many do, and this clause specifies how to interpret the st... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.1 General
| |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.1.1 Messages
| For all concerned protocols, concrete messages are bit strings of variable length, formally a succession of a finite, possibly null, number of bits (i.e., elements of the set {"0", "1"}), with a beginning and an end.
The services provided by lower layers includes the transmission of such bit strings.
Considered as me... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.1.2 Octets
| In many places, a message is described as a succession of octets. An octet is generally a succession of 8 bits. Unless otherwise indicated, the term octet is used more restrictively to refer to a part of message, defined when considering a message as a succession of octets, e.g., the first 8 bits of a message, or the 1... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.1.3 Integer
| In many places, message parts are described as encoding integers. Two generic encoding are defined in this clause.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.1.3.1 Binary
| A message part is said to encode in binary an integer to indicate that concrete strings are mapped, for some usage, on the set of non signed integers with the following rule:
- Let k denote the length of the bit string, and let b(i) denote an integer of value 0 if the ith bit in the string is "0", and 1 otherwise. The... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.1.3.2 2-complement binary
| A message part is said to encode in 2-complement binary an integer to indicate that concrete strings are mapped, for some usage, on the set of signed integers with the following rule:
- Let k denote the length of the bit string, and let b(i) denote an integer of value 0 if the ith bit in the string is "0", and 1 other... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.1.4 Spare parts
| In some cases the specification is that which message instances can be accepted by a receiver comprise more that the legal message instances that can be sent. One example of this is the notion of spare bit. A spare bit has to send as the value indicated in the specification (typically 0), but can be accepted as a 0 or ... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2 Standard L3 messages
| |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.1 Components of a standard L3 message
| A standard L3 message consists of an imperative part, itself composed of a header and the rest of imperative part, followed by a non-imperative part. Both the non-header part of the imperative part and the non-imperative part are composed of successive parts referred as standard information elements.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.1.1 Format of standard information elements
| A standard IE may have the following parts, in that order:
- an information element identifier (IEI);
- a length indicator (LI);
- a value part.
A standard IE has one of the formats shown in table 11.1:
Table 11.1: Formats of information elements
Format
Meaning
IEI present
LI present
Value part present
T
Ty... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.1.1.1 Information element type and value part
| Every standard IE has an information element type which determines the values possible for the value part of the IE, and the basic meaning of the information. The information element type describes only the value part. Standard IEs of the same information element type may appear with different formats. The format used ... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.1.1.2 Length indicator
| For LV or TLV, the length indicator (LI) of a standard IE consists of one octet. For LV-E and TLV-E, the LI of a standard IE consists of two octets where bit 8 of octet n contains the most significant bit and bit 1 of octet n+1 contains the least significant bit (refer to figure 11.9 in clause 11.2.1.1.4 for the relati... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.1.1.3 Information element identifier
| When present, the IEI of a standard IE consists of a half octet or one octet. A standard IE with IEI consisting of a half octet has format TV, and its value part consists of a half octet. The value of the IEI depends on the standard IE, not on its information element type. The IEI, if any, of a given standard IE in a g... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.1.1.4 Categories of IEs; order of occurrence of IEI, LI, and value part
| Totally five categories of standard information elements are defined:
- information elements of format V or TV with value part consisting of 1/2 octet (type 1);
- information elements of format T with value part consisting of 0 octets (type 2);
- information elements of format V or TV with value part that has fixed ... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.2 Description methods for IE structure
| Standard IEs can be further structured in parts called fields. Two description methods are recommended and described hereafter.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.2.1 Tables
| According to this description method, the IE is presented in its maximum format, i.e., T, TV, TLV or TLV-E, in a picture representing the bits in a table, each line representing an octet. Bits appear in the occidental order, i.e., from left of the page to right of the page, and from top of the page to bottom of the pag... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.2.1.1 Compact notation
| The compact notation described in Annex B can be used to describe the value part of a standard IE. This method is recommended for complex structures, or for a branching structure not respecting octet boundaries.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3 Imperative part of a standard L3 message
| The imperative part of a standard L3 message is composed of a header possibly followed by mandatory standard IEs having the format V, LV or LV-E.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.1 Standard L3 message header
| For the MM, GMM, CC and SM protocols defined in 3GPP TS 24.008 [6], the header of a standard L3 message is composed of two octets, and structured in three main parts, the protocol discriminator (1/2 octet), a message type octet, and a half octet used in some cases as a Transaction Identifier, in some other cases as a s... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.1.1 Protocol discriminator
| Bits 1 to 4 of the first octet of a standard L3 message contain the protocol discriminator (PD) information element. The PD (with exception of "extension of the PD to one octet length") identifies the L3 protocol to which the standard layer 3 message belongs. The correspondence between L3 protocols and PDs (with except... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.1.2 Skip indicator
| Bits 5 to 8 of octet 1 of a standard L3 message may be used differently, depending on the protocol and the SAP. The use of this half-octet is consistent for a given PD and SAP. One possibility is that this half-octet contains the skip indicator. Another possibility is that this half-octet is a part of EPD as specified ... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.1.3 Transaction identifier
| A L3 protocol may define that bits 5 to 8 of octet 1 of a standard L3 message of the protocol contains the transaction identifier (TI). The TI allows to distinguish up to 16 different bi-directional messages flows for a given PD and a given SAP. Such a message flow is called a transaction.
An extension mechanism for T... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.1.4 Sub-protocol discriminator
| A L3 protocol may define that bits 5 to 8 of octet 1 of a standard L3 message of the protocol contains the sub-protocol discriminator (SPD). The SPD allows to distinguish between different protocols inside one sublayer.
Table 11.4: Sub-Protocol discriminator values
bits 8 7 6 5
0 0 0 0
Value used by the Skip Indic... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.1.5 EPS bearer identity
| A L3 protocol may define that bits 5 to 8 of octet 1 of a standard L3 message of the protocol contain the EPS bearer identity. The EPS bearer identity is used to identify a message flow.
8
7
6
5
4
3
2
1
EPS bearer identity value
-
-
-
-
octet 1
Figure 11.9a: EPS bearer identity
Table 11.5: E... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.1.6 Security header type
| For EPS protocols, a L3 protocol may define that bits 5 to 8 of octet 1 of a standard L3 message of the protocol contain the security header type.
For 5GS protocols, a L3 protocol may define that bits 1 to 4 of octet 2 of a standard L3 message of the protocol contain the security header type.
11.2.3.1a Procedure tran... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2 Message type octet
| |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.1 Message type octet (when accessing Release 98 and older networks only)
| The message type octet is the second octet in a standard L3 message.
When a standard L3 message is expected, and a message is received that is less than 16 bit long, that message shall be ignored.
When the radio connection started with a core network node of a Release 98 or older network, the message type IE is coded... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.2 Message type octet (when accessing Release 99 and newer networks)
| The message type octet is the second octet in a standard L3 message except:
- for the protocols defined by 3GPP TS 24.501 [31] where the message type octet is the third octet in a standard L3 message; and
- for the AIoT NAS protocol defined by 3GPP TS 24.369 [43], where the message type octet is the second or sixth o... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.3 Sequenced message transfer operation
| Upper layer messages sent using the RR sub-layer transport service from the mobile station to the network can be duplicated by the data link layer in at least the following cases:
- in A/Gb mode, when a channel change of dedicated channels is required (assignment or handover procedure) and the last layer 2 frame has n... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.3.1 Variables and sequence numbers
| |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.3.1.1 Send state variable V(SD)
| The mobile station shall have one associated send state variable V(SD) ("Send Duplicated") for each upper layer message flow. The send state variable denotes the sequence number of the next in sequence numbered message in the flow to be transmitted. The value of the corresponding send state variable shall be incremente... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.3.1.2 Send sequence number N(SD)
| At the time when such a message to be numbered is designated for transmission, the value of N(SD) for the message to be transferred is set equal to the value of the send state variable V(SD).
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.3.2 Procedures for the initiation, transfer execution and termination of the sequenced message transfer operation
| |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.3.2.1 Initiation
| The sequenced message transfer operation is initiated by establishing a RR connection. The send state variables V(SD) are set to 0.
After successful completion of SRVCC handover (see 3GPP TS 23.216 [27]), the mobile station shall set the send state variable V(SD) to 0.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.3.2.2 Transfer Execution
| The core network shall compare the send sequence numbers of pairs of subsequent messages in the same upper layer messages flow.
For the GCC, BCC, and LCS upper layer message flows, in case the send sequence numbers of two subsequent messages in a flow are not identical, no duplication has occurred. In case the send se... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.2.3.2.3 Termination
| The sequenced message transfer operation is terminated by the RR connection release procedure.
Inter system change from A/Gb mode to Iu mode or from Iu mode to A/Gb mode shall not terminate the sequenced message transfer. UMTS SRNC relocation shall not terminate the sequenced message transfer.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.3.3 Standard information elements of the imperative part
| The message type octet of a standard L3 message may be followed by mandatory standard IEs having the format V, LV or LV-E as specified in the message description in the relevant protocol specification.
As a design rule, octet boundaries must be respected. This implies that half-octet standard IEs (i.e., V formatted ty... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.4 Non-imperative part of a standard L3 message
| The imperative part of a standard L3 message is followed by the (possibly empty) non-imperative part. The relevant protocol specification defines where the imperative part of a standard L3 message ends. The non-imperative part of a standard L3 message is composed of (zero, one, or several) standard IEs having the forma... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.5 Presence requirements of information elements
| The relevant protocol specification may define three different presence requirements (M, C, or O) for a standard IE within a given standard L3 message:
- M ("Mandatory") means that the IE shall be included by the sending side, and that the receiver diagnoses a "missing mandatory IE" error when detecting that the IE is... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.2.6 Description of standard L3 messages
| This clause describes a generic description method for standard L3 messages, the tabular description. Protocol specification may follow other methods.
A standard L3 message is described by a table listing the header elements and the standard IEs in the message. For each element is given:
- if applicable the IEI, in h... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3 Non standard L3 messages
| In some protocols, the structure of part or all of the messages might not always follow the standard L3 message structure. As a design rule, this should be consistent for a given protocol, direction and lower layer SAP.
A possibility is to describe the message with the compact notation described in Annex B.
A few con... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3.1 Case A: BCCH and AGCH/PCH messages
| In these cases, the SAP capability is for fixed length messages. The messages are structured as standard L3 messages plus one octet in front, the L2 pseudo length octet, and a rest octet part at the end.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3.1.1 L2 Pseudo Length octet
| This octet, the L2 pseudo length indicator octet, indicates the length in octets of the subsequent octet string that can be analysed as a standard L3 message.
The octet is structured as follows:
Bits 3 to 8 encodes in binary the L2 pseudo length, i.e., the length of the part to be analysed as a standard L3 message;
... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3.1.2 Rest Octets
| The part after the part structured as a standard L3 message, and up to the end of the message as constrained by lower layers, is presented as a non standard IE of variable length (sometime indicated as of type 5), the "rest octets" IE.
The rest octets element may be described by table description, or, preferably, usin... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3.1.3 Description of a modified standard L3 message
| The description can be provided in the same way as a standard L3 message, with in the case of a tabular description one non standard IE at the beginning (of type L2 pseudo length), and one non standard IE at the end.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3.2 Case B: SACCH / SDCCH / FACCH messages sent in unacknowledged mode
| The messages are structured either as standard L3 messages, or in the so-called short header format. The value of the 8th bit (bit 1 of octet 1) of the link layer PDU distinguishes the two cases. In the case of the short header, the L3 message is the same bit string as the link layer PDU, and has a fixed length. The fo... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3.2.1 The first octet
| Bits 1 and 2 are the link layer header. Bit 2 of octet 1 is set to "0", and bit 1 is reserved for the link layer.
A protocol discriminator is the first part of the message (starting bit 8 of octet 1). The protocol discriminator field may have different lengths. The following protocol discriminator is defined:
- 0 RR.... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3.2.2 The rest of the message
| The rest of the structure is not more constrained.
The preferred description method is the one described in Annex B.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3.3 Design guidelines for non standard parts
| The guidelines in this clause apply to non standard parts, such as rest octets, short header broadcast message or fully non standard L3 messages.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.3.3.1 General
| The structure should be as far as possible be such that the analysis can be conducted from beginning to end. In other terms, the conditions determining the syntactic analysis of a part (e.g., tags, lengths) should appear before that part.
The part should be structured as a succession of information elements, each carr... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.4 Handling of superfluous information
| All equipment should be able to ignore any extra information present in an L3 message, which is not required for the proper operation of that equipment. For example, a mobile station may ignore the calling party BCD number if that number is of no interest to the Mobile Station when a SETUP message is received.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.4.1 Information elements that are unnecessary in a message
| The relevant protocol specification may define certain IEs to be under some conditions unnecessary in a L3 message. A protocol entity detecting an unnecessary IE in a received L3 message shall ignore the contents of that IE for treating the message; it is not obliged to check whether the contents of the IE are syntacti... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 11.4.2 Other syntactic errors
| This clause applies to the analysis of the value part of an information element. It defines the following terminology:
- An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved", or if its value part violates syntactic rules given in the specification of the v... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 1 Scope | This Technical Specification (TS) describes the Service Principles for PLMNs specified by 3GPP. Principles and requirements for interworking with WLAN are covered in TS 22.234 [35].
3GPP specifications provide integrated personal communications services. The system will support different applications ranging from narro... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 2.1 Normative references | [1] 3GPP TS 22.105 "Services and Service Capabilities"
[2] Void
[3] 3GPP TS 22.038: "(U)SIM Application Toolkit (USAT); Service description; Stage 1".
[4] 3GPP TS 22.001: "Principles of Circuit telecommunication services supported by a Public Land Mobile Network (PLMN)".
[5] 3GPP TS 22.004: "General on supplementary se... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 2.2 Informative references | [43] GSMA PRD IR.34: "Inter-Service Provider IP Backbone Guidelines"
[58] ETSI TR 103.140 V1.1.1 (2014-04): "eCall for VoIP"
[60] Code of Federal Regulations (CFR) Title 47; https://www.fcc.gov/general/rules-regulations-title-47
[61] 3GPP TR 22.904: "Study on user centric identifiers and authentication".
[62] GSMA SGP.... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 3 Definitions and abbreviations | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [29] and the following apply.
A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [29].
3GPP SSO Authentication: Authentication performed between an SSO-capable UE and 3G... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [29] and the following apply.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [29].
DAP Data Application Provider
IdP Identity Provider
IVS In Vehicle System... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4 General | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.1 Aims of 3GPP specifications | It shall be capable of delivering audio, text, video and graphics direct to people and provide them with access to the next generation of information-based services. It moves mobile and personal communications forward from existing systems, delivering mass market low-cost digital telecommunication and IP-based multimed... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.2 Standardisation of Service Capabilities | Existing systems have traditionally standardised the complete sets of teleservices, applications and supplementary services which they provide. As a consequence, substantial efforts are often required to introduce new services or simply to modify the existing one (customisation). This makes it more difficult for operat... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.2.1 Provision of service capabilities in shared networks | The provision of services and service capabilities that is possible to offer in a network shall not be restricted by the existence of the network sharing It shall be possible for a core network operator to differentiate its service offering from other core network operators within the shared network.
It shall be possib... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3 Efficient Use of Network Resources | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.1 Network Traffic Patterns | Service capabilities shall take account of the discontinuous and asymmetric nature of most teleservices, multimedia services and user applications and consider the overheads and signalling surge caused by frequent transmissions of small amount of data by mobile data application, in order to make efficient use of networ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.2 Mass Simultaneous Registration | When a large number of subscribers enter in a registration area in which they have not registered, the core and radio access network shall be able to provide a capability to optimize the mass simultaneous registration traffic at a given instance of time. The core and radio access network shall be able to keep providing... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.