hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.1.4 LLGMM-RESUME-REQ | Normal LLC frame sending and reception is possible again. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.1.5 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.1.6 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.1.7 LLGMM-PAGE-IND | Requires to send a paging message to the mobile station. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.1.8 LLGMM-PAGE-RESP-IND | A paging response has been received from the mobile. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.1.9 LL-UNITDATA-REQ | Request to send a SMM message in unacknowledged mode to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.1.10 LL-UNITDATA-IND | A SMM message in unacknowledged mode has been received from the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.1.11 LLGMM-STATUS-IND | Indication used by LLC to transfer lower layer failures to the GMM sublayer. |
bbc07dc9647184161b1f5af7180e8116 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.2.1 LL-UNITDATA-REQ | An LLC UI frame will be sent to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.2.2 LL-UNITDATA-IND | An LLC UI frame has been received from the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.5.2.1 PMMSMS_REL_REQ | The GMM is requested to release of a PS signalling connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.5.2.2 PMMSMS_ERROR_IND | The GMM indicates that a PS signalling connection has been released. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.5.2.4 PMMSMS_UNITDATA_IND | Indication used by GMM to transfer the received data to the GSMS entities. |
bbc07dc9647184161b1f5af7180e8116 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.5.3.3 GMMSS-UNITDATA-IND | The GMM forwards a SS PDU, which has been received from the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 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 represented by the CTS‑RR service primitives. |
bbc07dc9647184161b1f5af7180e8116 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.6.1.1 RR_ CTS_ALIVE_CHECK_REQ | Request used by the CTS Mobility Management entity to request an alive check. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.6.1.3 RR_ CTS_HUNTING_REQ | Request to hunt the mobiles. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.6.1.4 RR_ CTS_GROUP_ALERTING_REQ | Request to alert a group of mobiles. |
bbc07dc9647184161b1f5af7180e8116 | 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 standard description.
This clause also addresses basic aspects of the handling of messages received but not compliant with the allowed structure. In most cases, only the conditions that lead to the diagnosis of an error are described. The reaction of an entity receiving a message leading to such a diagnosis is in general specified for each protocol in the relevant protocol specification. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 11.1 General | |
bbc07dc9647184161b1f5af7180e8116 | 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 messages, these bit strings follow some structure (the syntax), enabling to organize bits in information pieces of a different meaning level.
The term message is used as well for a concrete message (i.e., a bit-string, as defined by the giving of all its bits, in practice appearing at one point of time in a concrete dialog), as for a class of concrete messages sharing a common structure. A concrete message is an instance of the corresponding class of messages. Message classes can be described as sets of potential bit strings, and of a common structure, enabling in particular to identify parts meaningful for the co-operation functions the protocol supports.
In general, in the rest of the clause as in the protocol specifications, the term message will be used to refer to the class. It may be used, when the context prevents ambiguity, to refer to a message instance (e.g., a received is usually a message instance). In the rest of this clause, the term message instance will be used when needed to refer unambiguously to specific concrete message, i.e. to a specific bit string.
A message (message class) can be described directly as a set of bit strings, using the formal notation described in Annex B.
A message can also be described as a standard L3 message, in which case the interpretation of the message description in term of a set of bit strings is specified in the next clauses.
In all cases, structuring messages is based on the underlying bit string. Thus, the following terms are used:
- a part of a message instance is a sub-string of the corresponding string; a part of a message (as a class) is described by a definition applicable to all instances; a part of a message then is both a structural attribute of the message as a class, and a set of sub-strings, composed of the sub-strings obtained by applying the definition to each possible instance; for instance, « the first octet » of a message instance is defined from the moment its length is greater than 8, and is the sub-string composed of the first 8 bits of the message instance; the « first octet » of a message as a class is the structural definition given above, and the set of all 8-bit octet strings that can be obtained as the first octet of one instance of the class;
- "part A follows part B" means that in the message the sub-string corresponding to part B is concatenated with the sub-string of part A;
- the length of a message instance, or of part of message instance, is the number of bits of the corresponding sub string; rigorously speaking, a message as a class (or a part seen as a class) has a length only if all the corresponding instances have the same length; by extension, sentences such as « a message as a length in the range so and so » means that the length of an instances of the class always fall in the range. |
bbc07dc9647184161b1f5af7180e8116 | 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 17th to the 23rd, form an octet, but not the second bit to the 9th.
Unless specified otherwise, the numbering conventions are the following:
- Octets in a message or in a part are numbered from 1 onward, starting at the beginning of the bit string. This numbering can be strictly applied only for message instances, and for the first part of a message structurally identical for all instances.
- Bits in octets are numbered from 8 down to 1, starting at the beginning of the octet.
- When represented as tables showing the different bit positions, octets are presented in the natural occidental order, i.e., from the top of a page downward. Bits in octets are presented with the first bit on the left of the page. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 11.1.3 Integer | In many places, message parts are described as encoding integers. Two generic encoding are defined in this clause. |
bbc07dc9647184161b1f5af7180e8116 | 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 encoded integer n respects the equation: |
bbc07dc9647184161b1f5af7180e8116 | 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 otherwise. The encoded integer n respects the equation: |
bbc07dc9647184161b1f5af7180e8116 | 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 a 1 by the receiver without error diagnosis. A spare field is a field composed entirely of spare bits. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 11.2 Standard L3 messages | |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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
Type only
yes
no
no
V
Value only
no
no
yes
TV
Type and Value
yes
no
yes
LV
Length and Value
no
yes
yes
TLV
Type, Length and Value
yes
yes
yes
LV-E
Length and Value
no
yes
yes
TLV-E
Type, Length and Value
yes
yes
yes
Some IEs may appear in the structure, but not in all instances of messages. An IE is then said to be present or not present in the message instance. If an IE is not present in a message instance, none of the three parts is present. Otherwise, parts must be present according to the IE format.
In the message structure, an IE that is allowed not to be present in all message instances is said not to be mandatory. Other IEs are said to be mandatory.
LV-E and TLV-E are used by for example, 5GS Mobility Management (5GMM), 5GS Session Management (5GSM), EPS Mobility Management (EMM), EPS Session Management (ESM), GPRS Mobility Management (GMM) and GPRS Session Management (SM). The use of LV-E and TLV-E is specified for each protocol in the relevant protocol specification (e.g. 3GPP TS 24.301 [25], 3GPP TS 24.501 [31], 3GPP TS 24.587 [34], 3GPP TS 24.193 [35]). In GPRS GMM and GPRS SM messages, IEs of format LV-E and TLV-E may be used only after MS and network have successfully negotiated support of such IEs. |
bbc07dc9647184161b1f5af7180e8116 | 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 for a given standard IE in a given message is specified within the description of the message.
The value part of a standard IE either consists of a half octet or one or more octets; the value part of a standard IE with format LV or TLV consists of an integral number of octets, between 0 and 255 inclusive; it then may be empty, i.e., consist of zero octets; if it consists of a half octet and has format TV, its IEI consists of a half octet, too. For LV-E and TLV-E, the value part of a standard IE consists of an integral number of octets, between 0 and 65535 inclusive. The value part of a standard IE may be further structured into parts, called fields. |
bbc07dc9647184161b1f5af7180e8116 | 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 relative ordering of the 2 octets). The LI contains the binary encoding of the number of octets of the IE value part. The LI of a standard IE with empty value part indicates 0 octets. Standard IE of an information element type such that the possible values may have different values must be formatted with a length field, i.e., LV, TLV, LV-E or TLV-E. |
bbc07dc9647184161b1f5af7180e8116 | 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 given message is specified within the description of the message. In some protocol specifications, default IEI values can be indicated. They are to be used if not indicated in the message specification. Non mandatory standard IE in a given message, i.e., IE which may be not be present (formally, for which the null string is acceptable in the message), must be formatted with an IEI, i.e., with format T, TV, TLV or TLV-E. |
bbc07dc9647184161b1f5af7180e8116 | 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 length of at least one octet (type 3);
- information elements of format LV or TLV with value part consisting of zero, one or more octets and a maximum of 255 octets (type 4);
- information elements of format LV-E or TLV-E with value part consisting of zero, one or more octets and a maximum of 65535 octets (type 6). This category is used in 5GS, EPS and GPRS only.
Type 1 standard information elements of format V provide the value in bit positions 8, 7, 6, 5 of an octet (see figure 11.1) or bits 4, 3, 2, 1 of an octet (see figure 11.2).
Figure 11.1: Type 1 IE of format V
Figure 11.2: Type 1 IE of format V
Type 1 standard information elements of format TV have an IEI of a half octet length; they provide the IEI in bit positions 8, 7, 6, 5 of an octet and the value part in bit positions 4, 3, 2, 1 of the same octet, see figure 11.3.
Figure 11.3: Type 1 IE of format TV
A type 2 standard IE has format T; its IEI consists of one octet, its value part is empty, see figure 11.4.
Figure 11.4: Type 2 IE
A type 3 standard information element has format V or TV; if it has format TV, its IEI consists of one octet and precedes the value part in the IE. The value part consists of at least one octet. See figure 11.5 and figure 11.6.
Figure 11.5: Type 3 IE of format V (k = 0, 1, 2, ...)
Figure 11.6: Type 3 IE of format TV (k = 1, 2, ...)
A type 4 standard information element has format LV or TLV. Its LI has one octet and precedes the value part, which consists of zero, one, or up to 255 octets; if present, its IEI has one octet length and precedes the LI. See figure 11.7 and figure 11.8.
Figure 11.7: Type 4 IE of format LV (k = 0, 1, 2, ...)
Figure 11.8: Type 4 IE of format TLV (k = 1, 2, ...)
A type 6 standard information element has format LV-E or TLV-E. Its LI has 2 octets and precedes the value part, which consists of zero, one or up to 65535 octets; if present, its IEI has one octet length and precedes the LI. See figure 11.9 and figure 11.10.
Figure 11.9: Type 6 IE of format LV-E (k = 1, 2, ...)
Figure 11. 10: Type 6 IE of format TLV-E (k = 1, 2, ...)
NOTE: In the 5GS protocol 5GMM, certain type 6 IEs of format TLV-E can also be included within a Type 6 IE container information element in the standard L3 message (see 3GPP TS 24.501 [31], clause 9.11.3.98). |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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 page.
Boxes so delimited contains typically the field name, possibly an indication of which bits in the field are in the box, and possibly a value (e.g., for spare bits).
A specific method can be used in the IE description to describe a branching structure, i.e., a structure variable according to the value of particular fields in the IE. This design is unusual outside type 4 and type 6 IEs, and as, a design rule, should be used only in type 4 and type 6 IEs.
a) The octet number of an octet within the IE is defined typically in the table. It consists of a positive integer, possibly of an additional letter, and possibly of an additional asterisk, see clause f). The positive integer identifies one octet or a group of octets.
b) Each octet group is a self contained entity. The internal structure of an octet group may be defined in alternative ways.
c) An octet group is formed by using some extension mechanism. The preferred extension mechanism is to extend an octet (N) through the next octet(s) (Na, Nb, etc.) by using bit 8 in each octet as an extension bit.
- The bit value "0" indicates that the octet group continues through to the next octet. The bit value "1" indicates that this octet is the last octet of the group. If one octet (Nb) is present, the preceding octets (N and Na) shall also be present.
- In the format descriptions of the individual information elements, bit 8 is marked "0/1 ext" if another octet follows. Bit 8 is marked "1 ext" if this is the last octet in the extension domain.
- Additional octets may be defined in later versions of the protocols ("1 ext" changed to "0/1 ext") and equipments shall be prepared to receive such additional octets; the contents of these octets shall be ignored. However the length indicated in the formal description of the messages and of the individual information elements only takes into account this version of the protocols.
d) In addition to the extension mechanism defined above, an octet (N) may be extended through the next octet(s) (N+1, N+2 etc.) by indications in bits 7-1 (of octet N).
e) The mechanisms in c) and d) may be combined.
f) Optional octets are marked with asterisks (*). As a design rule, the presence or absence of an optional octet should be determinable from information in the IE and preceding the optional octet. Care should be taken not to introduce ambiguities with optional octets.
g) At the end of the IE, additional octets may be added in later versions of the protocols also without using the mechanisms defined in c) and d). Equipments shall be prepared to receive such additional octets; the contents of these octets shall be ignored. However the length indicated in the formal description of the messages and of the individual information elements only takes into account this version of the protocols. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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 sub-protocol discriminator, and called skip indicator otherwise.
For the EPS protocols EMM and ESM, a standard L3 message can be either a plain NAS message or a security protected NAS message:
- The header of a plain NAS message is composed of two or three octets, and structured in four main parts, the protocol discriminator (1/2 octet), a half octet used in some cases as security header type and in other cases as an EPS bearer identity (1/2 octet), a message type octet, and one octet included in some cases and used as a procedure transaction identity (PTI). If the procedure transaction identity is present, it is preceding the message type octet.
- The header of a security protected NAS message is composed of six octets, and structured in four main parts, the protocol discriminator (1/2 octet), a half octet used as security header type, a message authentication code of four octets, and a sequence number of one octet. This header is followed by a complete plain NAS message (i.e. including the header of this plain NAS message).
For the 5GS protocols 5GMM and 5GSM, a standard L3 message can be either a plain 5GS NAS message or a security protected 5GS NAS message:
- The header of a plain 5GS NAS message is composed of three octets for 5GMM NAS messages and composed of four octets for 5GSM NAS messages, and structured in four main parts, namely, the extended protocol discriminator (1 octet); an octet used as security header type (1/2 octet) plus a spare half octet in case of 5GMM NAS messages, and a PDU session identity of one octet in case of 5GSM NAS messages; an octet for procedure transaction identity (PTI) in case of 5GSM NAS messages; and one octet for message type. If the procedure transaction identity is present, it is preceding the message type octet.
- The header of a security protected 5GS NAS message is composed of seven octets, and structured in four main parts, the extended protocol discriminator (1 octet), an octet used as security header type (1/2 octet) plus a spare half octet, a message authentication code of four octets, and a sequence number of one octet. This header is followed by a complete plain 5GS NAS message (i.e. including the header of this plain 5GS NAS message). |
bbc07dc9647184161b1f5af7180e8116 | 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 exception of "extension of the PD to one octet length") is one-to-one.
When the PD is set to "extension of the PD to one octet length", the first octet of a standard L3 message contains the extended protocol discriminator (EPD) information element as specified in clause 11.2.3.1.1A.
The PD can take the following values:
Table 11.2: Protocol discriminator values
bits 4 3 2 1
0 0 0 0
group call control
0 0 0 1
broadcast call control
0 0 1 0
EPS session management messages
0 0 1 1
call control; call related SS messages
0 1 0 0
GPRS Transparent Transport Protocol (GTTP)
0 1 0 1
mobility management messages
0 1 1 0
radio resources management messages
0 1 1 1
EPS mobility management messages
1 0 0 0
GPRS mobility management messages
1 0 0 1
SMS messages
1 0 1 0
GPRS session management messages
1 0 1 1
non call related SS messages
1 1 0 0
Location services specified in 3GPP TS 44.071 [8a]
1 1 1 0
extension of the PD to one octet length
1 1 1 1
used by tests procedures described in 3GPP TS 44.014 [5a], 3GPP TS 34.109 [17a], 3GPP TS 36.509 [26] and 3GPP TS 38.509 [29].
If the network receives, on a SAP where it expects standard L3 messages, a message with a protocol discriminator different from those specified in table 11.2, the network may ignore the message or initiate the channel release procedure defined in 3GPP TS 44.018 [6b].
If the Mobile Station receives, on a SAP where it expects standard L3 messages, a standard L3 message with a protocol discriminator different from those specified in table 11.2, or for a protocol that it does not support, the Mobile Station shall ignore the message.
11.2.3.1.1A Extended protocol discriminator (EPD)
When the PD is set to "extension of the PD to one octet length" as specified in clause 11.2.3.1.1, bits 1 to 8 of the first octet of a standard L3 message contain the extended protocol discriminator (EPD) information element.
The EPD identifies the L3 protocol to which the standard layer 3 message belongs. The correspondence between L3 protocols and EPDs is one-to-one.
The EPD can take the values specified in table 11.2.3.1.1A.1.
Table 11.2.3.1.1A.1: EPD values
EPD value (octet 1, bit 1 to bit 8)
Bits
8
7
6
5
4
3
2
1
0
0
0
0
1
1
1
0
reserved
0
0
0
1
1
1
1
0
reserved
0
0
1
0
1
1
1
0
5GS session management messages
0
0
1
1
1
1
1
0
reserved
0
1
0
0
1
1
1
0
reserved
0
1
0
1
1
1
1
0
reserved
0
1
1
0
1
1
1
0
reserved
0
1
1
1
1
1
1
0
5GS mobility management messages
1
0
0
0
1
1
1
0
reserved
1
0
0
1
1
1
1
0
reserved
1
0
1
0
1
1
1
0
reserved
1
0
1
1
1
1
1
0
reserved
1
1
0
0
1
1
1
0
reserved
1
1
0
1
1
1
1
0
reserved
1
1
1
0
1
1
1
0
reserved
1
1
1
1
1
1
1
0
reserved
NOTE: Bits 4 to 1 of each EPD value contain "extension of the PD to one octet length" as specified in clause 11.2.3.1.1.
If the network receives, on a SAP where it expects standard L3 messages, a message with an EPD different from those specified in table 11.2.3.1.1A.1, the network may ignore the message, may initiate the RRC connection release procedure defined in 3GPP TS 36.331 [24], or may initiate the RRC connection release procedure defined in 3GPP TS 38.331 [28].
If the Mobile Station receives, on a SAP where it expects standard L3 messages, a standard L3 message with an EPD different from those specified in table 11.2.3.1.1A.1, or for a protocol that it does not support, the Mobile Station shall ignore the message. |
bbc07dc9647184161b1f5af7180e8116 | 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 in clause 11.2.3.1.1A. Unless otherwise specified in the protocol, the skip indicator IE is a spare field. |
bbc07dc9647184161b1f5af7180e8116 | 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 TI is also defined. This mechanism allows to distinguish up to 256 different bi-directional messages flows for a given PD and a given SAP. The extension mechanism shall not be used unless explicitly stated in the core specification(s) for the protocol. The TI IE is coded as shown in figure 11.9 and table 11.3. It is composed of the TI value and the TI flag.
The TI value and the TI flag occupy bits 5 - 7 and bit 8 of the first octet respectively.
The extended TI shall not be used unless TI values of 7 or greater are needed.
Where the extended TI is used, the TI IE includes a second octet. The TI value in the first octet is ignored, and the TI value is encoded in bits 7-1 of the second octet.
NOTE: In other specifications, in respect to error handling, there are references to TI value "111". This refers to the binary encoding of bits 5 –7 in octet 1. For protocols which do not use the extended TI this '111' encoding is still handled as an error case.Transactions are dynamically created, and their TI value is assigned at creation time. TI values are assigned by the side of the interface initiating a transaction. At the beginning of a transaction a free TI value (i.e., a value not yet used for the given PD, the given SAP, and with the given initiator) is chosen and assigned to this transaction. It then remains fixed for the lifetime of the transaction. After a transaction ends, the associated TI value is free and may be reassigned to a later transaction.
Two identical TI values may be used when each value pertains to a transaction initiated by the different sides of the interface. In this case the TI flag shall avoid ambiguity. The transaction identifier flag can take the values "0" or "1". The TI flag is used to identify which side of the interface initiated the transaction. A message has a TI flag set to "0" when it belongs to transaction initiated by its sender, and to "1" otherwise.
Hence the TI flag identifies who allocated the TI value for this transaction and the only purpose of the TI flag is to resolve simultaneous attempts to allocate the same TI value.
The TI extension mechanism may in future evolution of the L3 protocols be further extended by setting the EXT flag in octet 2 to "0" (see figure 11.9).
8
7
6
5
4
3
2
1
TI flag
TIO
-
-
-
-
Octet 1
1
EXT
TIE
Octet 2 *
Figure 11.9: Transaction identifier
Table 11.3: Transaction identifier
TI flag (octet 1)
Bit
8
0
The message is sent from the side that originates the TI
1
The message is sent to the side that originates the TI
TIO (octet 1)
Bits
7 6 5
0 0 0
TI value 0
0 0 1
‑ ‑ 1
0 1 0
‑ ‑ 2
0 1 1
‑ ‑ 3
1 0 0
‑ ‑ 4
1 0 1
‑ ‑ 5
1 1 0
‑ ‑ 6
1 1 1
The TI value is given by the TIE in octet 2
TIE (octet 2)
Bits 7-1
0000000
0000001
0000010
0000011
0000100
0000101
0000110
Reserved.
All other values
The TI value is the binary representation of TIE
Where bit 7 is the most significant bit
And bit 1 is the least significant bit |
bbc07dc9647184161b1f5af7180e8116 | 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 Indicator (see 11.2.3.1.2)
0 0 0 1
CTS sub-protocol
0 0 1 0
\
To
} all other values are reserved
1 1 1 1
/ |
bbc07dc9647184161b1f5af7180e8116 | 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: EPS bearer identity
EPS bearer identity value (octet 1)
Bits
8
7
6
5
0
0
0
0
No EPS bearer identity assigned
0
0
0
1
EPS bearer identity value 1
0
0
1
0
EPS bearer identity value 2
0
0
1
1
EPS bearer identity value 3
0
1
0
0
EPS bearer identity value 4
0
1
0
1
EPS bearer identity value 5
0
1
1
0
EPS bearer identity value 6
0
1
1
1
EPS bearer identity value 7
1
0
0
0
EPS bearer identity value 8
1
0
0
1
EPS bearer identity value 9
1
0
1
0
EPS bearer identity value 10
1
0
1
1
EPS bearer identity value 11
1
1
0
0
EPS bearer identity value 12
1
1
0
1
EPS bearer identity value 13
1
1
1
0
EPS bearer identity value 14
1
1
1
1
EPS bearer identity value 15 |
bbc07dc9647184161b1f5af7180e8116 | 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 transaction identity
A L3 protocol may define that a standard L3 message of the protocol contains the procedure transaction identity (PTI). The PTI allows distinguishing up to 254 different bi-directional messages flows for a given PD and a given SAP. Such a message flow is called a transaction. The procedure transaction identity is released when the procedure is completed.
Table 11.6: Procedure transaction identity
Bits
8
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
No procedure transaction identity assigned
0
0
0
0
0
0
0
1
\
to
} Procedure transaction identity value
1
1
1
1
1
1
1
0
/
1
1
1
1
1
1
1
1
Reserved
11.2.3.1b PDU session identity
A L3 protocol may define that octet 2 of a standard L3 message of the protocol contains the PDU session identity. The PDU session identity is used to identify a PDU session.
The range of PDU session identity values indicated in table 11.2.3.1c.1 is shared between the PDU sessions over 3GPP access and the PDU sessions over non-3GPP access.
8
7
6
5
4
3
2
1
PDU session identity
octet 1
Figure 11.2.3.1c.1: PDU session identity
Table 11.2.3.1c.1: PDU session identity
PDU session identity value (octet 1, bit 1 to bit 8)
Bits
8
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
No PDU session identity assigned
0
0
0
0
0
0
0
1
PDU session identity value 1
0
0
0
0
0
0
1
0
PDU session identity value 2
0
0
0
0
0
0
1
1
PDU session identity value 3
0
0
0
0
0
1
0
0
PDU session identity value 4
0
0
0
0
0
1
0
1
PDU session identity value 5
0
0
0
0
0
1
1
0
PDU session identity value 6
0
0
0
0
0
1
1
1
PDU session identity value 7
0
0
0
0
1
0
0
0
PDU session identity value 8
0
0
0
0
1
0
0
1
PDU session identity value 9
0
0
0
0
1
0
1
0
PDU session identity value 10
0
0
0
0
1
0
1
1
PDU session identity value 11
0
0
0
0
1
1
0
0
PDU session identity value 12
0
0
0
0
1
1
0
1
PDU session identity value 13
0
0
0
0
1
1
1
0
PDU session identity value 14
0
0
0
0
1
1
1
1
PDU session identity value 15
All other values are reserved (see NOTE).
NOTE: Values 64 up to and including 95 are used by the core network as specified in TS 29.571 [37] and are unavailable for future usage in NAS. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 11.2.3.2 Message type octet | |
bbc07dc9647184161b1f5af7180e8116 | 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 as shown in figure 11.10a and 11.10x.
Bit 8 is encoded as "0"; value "1" is reserved for possible future use as an extension bit. A protocol entity expecting a standard L3 message, and receiving a message containing bit 8 of octet 2 encoded as "1" shall diagnose a " message not defined for the PD" error and treat the message accordingly.
In messages of MM, CC, SS (via CS domain), GCC and BCC protocol sent using the transmission functionality provided by the RR layer to upper layers, and sent from the mobile station or the LMU to the network, bit 7 of octet 2 is used for send sequence number, see clause 11.2.3.2.3.
In messages of the LCS protocol sent using the transmission functionality provided by the RR layer to upper layers, and sent from the type A LMU to the network, bit 7 of octet 2 is used for send sequence number, see clause 11.2.3.2.3.
In all other standard layer 3 messages, except for RR messages, bit 7 is set to a default value. A protocol entity expecting a standard L3 message, and not using the transmission functionality provided by the RR layer, and receiving a message containing bit 7 of octet 2 encoded different to the default value shall diagnose a "message not defined for the PD" error and treat the message accordingly.
The default value for bit 7 is 0 except for the SM protocol where the default value is 1. No default value for bit 7 is specified for RR protocol. For RR message types see 3GPP TS 44.018.
Figure 11.10a: Message type IE (MM, CC, SS, GCC, BCC and LCS)
Figure 11.10x: Message type IE (protocol other than MM, CC, SS, GCC, BCC and LCS)
For MM, CC, SS, GCC, BCC and LCS protocols bits 1 to 6 of octet 2 of standard L3 messages contain the message type. For all other L3 protocols bits 1 to 8 of octet 2 of standard L3 message contain the message type.
The message type determines the function of a message within a protocol in a given direction. The meaning of the message type is therefore dependent on the protocol (the same value may have different meanings in different protocols), and the direction (the same value may have different meanings in the same protocol, when sent from the Mobile Station to the network and when sent from the network to the Mobile Station).
Each protocol defines a list of allowed message types for each relevant SAP. A message received analysed as a standard L3 message, and with a message type not in the corresponding list leads to the diagnosis "message not defined for the PD". Some message types may correspond to a function not implemented by the receiver. They are then said to be not implemented by the receiver.
The reaction of a protocol entity expecting a standard L3 message and receiving a message with message type not defined for the PD or not implemented by the receiver and the reception conditions is defined in the relevant protocol specification. As a general rule, a protocol specification should not force the receiver to analyse the message further. |
bbc07dc9647184161b1f5af7180e8116 | 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.
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 99 or later network, the message type IE is coded dependent on the PD as shown in figures 11.10b, c and d.
In messages of MM, CC and SS (via CS domain) protocol sent using the transmission functionality provided by the RR and/or access stratum layer to upper layers, and sent from the mobile station or the LMU to the network, bits 7 and 8 of octet 2 are used for send sequence number, see clause 11.2.3.2.3.
In messages of GCC and BCC protocol sent using the transmission functionality provided by the RR layer to upper layers, and sent from the mobile station or the LMU to the network, only bit 7 of octet 2 is used for send sequence number. Bit 8 is set to the default value.
In messages of the LCS protocol sent using the transmission functionality provided by the RR layer to upper layers, and sent from the type A LMU to the network, only bit 7 of octet 2 is used for send sequence number. Bit 8 is set to the default value.
In all other standard layer 3 messages, except for RR messages, bits 7 and 8 are set to the default value. A protocol entity expecting a standard L3 message, and not using the transmission functionality provided by the RR and/or access stratum layer, and receiving a message containing bit 7 or bit 8 of octet 2 encoded different to the default value shall diagnose a "message not defined for the PD" error and treat the message accordingly.
In messages of the RR protocol entity, bit 8 of octet 2 is set to the default value. The other value is reserved for possible future use as an extension bit .If an RR protocol entity expecting a standard L3 message receives message containing bit 8 of octet 2 encoded different from the default value it shall diagnose a "message not defined for the PD" error and treat the message accordingly.
The default value for bit 8 is 0. The default value for bit 7 is 0 except for the SM protocol which has a default value of 1. No default value for bit 7 is specified for RR protocol. For RR message types see 3GPP TS 44.018.
For EPS; the default value for bit 7 is 1. The value for bit 8 is 0 for the EMM protocol and 1 for the ESM protocol.
For 5GS; the default value for bit 7 is 1. The value for bit 8 is 0 for the 5GMM protocol and 1 for the 5GSM protocol.
Figure 11.10b: Message type IE (MM, CC and SS)
Figure 11.10c: Message type IE (GCC, BCC and LCS)
Figure 11.10d: Message type IE (protocol other than MM, CC, SS, GCC, BCC and LCS)
For MM, CC, SS, GCC, BCC and LCS protocols bits 1 to 6 of octet 2 of standard L3 messages contain the message type. For all other L3 protocols bits 1 to 8 of octet 2 of standard L3 message contain the message type.
The message type determines the function of a message within a protocol in a given direction. The meaning of the message type is therefore dependent on the protocol (the same value may have different meanings in different protocols), and the direction (the same value may have different meanings in the same protocol, when sent from the Mobile Station to the network and when sent from the network to the Mobile Station).
Each protocol defines a list of allowed message types for each relevant SAP. A message received analysed as a standard L3 message, and with a message type not in the corresponding list leads to the diagnosis "message not defined for the PD". Some message types may correspond to a function not implemented by the receiver. They are then said to be not implemented by the receiver.
The reaction of a protocol entity expecting a standard L3 message and receiving a message with message type not defined for the PD or not implemented by the receiver and the reception conditions is defined in the relevant protocol specification. As a general rule, a protocol specification should not force the receiver to analyse the message further. |
bbc07dc9647184161b1f5af7180e8116 | 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 not been acknowledged by the peer data link layer before the mobile station leaves the old channel;
- in Iu mode, when an RLC re-establishment occurs (e.g. due to relocation) and the RLC layer has not acknowledged the last one or more RLC PDUs before RLC re-establishment;
- an inter-system change from Iu mode to A/Gb mode is performed and the RLC layer has not acknowledged the last one or more RLC PDUs;
- an inter-system change from A/Gb mode to Iu mode is performed and the last layer 2 frame in A/Gb mode has not been acknowledged by the peer data link layer before the mobile station leaves the old channel.
In these cases, the mobile station does not know whether the network has received the messages correctly. Therefore, the mobile station has to send the messages again when the channel change is completed.
The network must be able to detect the duplicated received messages. Therefore, each concerned upper layer messages must be marked with a send sequence number.
To allow for different termination points in the infrastructure of the messages of different PDs, the sequence numbering is specific to each PD. For historical reasons, an exception is that messages sent with the CC, SS (via CS domain) and MM PDs share the same sequence numbering. In the following, the phrase upper layer message flow refers to a flow of messages sharing the same sequence numbering. The different upper layer flows are MM+CC+SS (via CS domain), GCC, BCC and LCS. The GMM, EMM, SM, ESM, SMS, SS (via PS domain) and TC (Test Control, see 3GPP TS 44.014 [5a], 3GPP TS 34.109 [17a] and 3GPP TS 36.509 [26]) protocols do not use layer 3 sequence numbering.
In a shared network with a MOCN configuration, Network Sharing non-supporting UEs can be redirected between CN operators (see 3GPP TS 23.251 [22]). When the redirection takes place, the CN node of the redirecting CN operator shall forward via the RAN the value of N(SD) of the last message received on the MM+CC+SS (via CS domain) message flow to the CN node of the next CN operator (3GPP TS 25.413 [23]).
11.2.3.2.3.1 Variables and sequence numbers
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 incremented by one with each numbered message transmission.
For the MM+CC+SS (via CS domain) upper layer message flow:
- when the RR connection starts with a core network of Release 98 or earlier, arithmetic operations on V(SD) are performed modulo 2. The mobile station shall keep using modulo 2 for the duration of the RR connection;
- when the RR connection starts with a core network of Release 99 or later, arithmetic operations on V(SD) are performed modulo 4. The mobile station shall keep using modulo 4 for the duration of the RR connection;
- after successful completion of SRVCC handover (see 3GPP TS 23.216 [27]), the mobile station shall perform modulo 4 arithmetic operations on V(SD). The mobile station shall keep using modulo 4 until the release of the RR connection established at SRVCC handover.
NOTE 1: In A/Gb mode, the release supported by the core network is indicated in the MSCR bit and in the SGSNR bit in the system information broadcast (see 3GPP TS 44.018 [6b] and 3GPP TS 44.060 [10a]).
NOTE 2: During SRVCC handover the MSCR bit is not provided to the mobile station, and therefore the mobile station assumes to access to a Release 99 or later core network.
For the GCC, BCC, and LCS upper layer message flows, arithmetic operations on V(SD) are performed modulo 2.
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).
11.2.3.2.3.2 Procedures for the initiation, transfer execution and termination of the sequenced message transfer operation
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.
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 sequence numbers are identical, the network must ignore the second one of the received messages.
For the MM+CC+SS (via CS domain) upper layer message flow:
- when accessed by a release 98 or earlier mobile station, in case the send sequence numbers of two subsequent messages in the flow are identical, the core network shall discard the second one of the received messages;
- when accessed by a release 99 or later mobile station, the core network shall discard any message whose N(SD) is not the increment by one (modulo 4) of the N(SD) of the last accepted message.
NOTE: The release supported by the mobile station is indicated by the revision level in the Mobile Station Classmark 1 or Mobile Station Classmark 2 information element, or by the revision level indicator in the MS network capability information element (see 3GPP TS 24.008, clause 10.5).
In a shared network with a MOCN configuration, the core network node to which the mobile station was redirected shall compare the send sequence number of the first message received after the redirection in the MM+CC+SS (via CS domain) message flow with the value of N(SD) received during the redirection procedure (see 3GPP TS 23.251 [22]):
- when accessed by a release 98 or earlier mobile station, if the two send sequence numbers are identical, the core network shall discard the received message from the mobile station;
- when accessed by a release 99 or later mobile station, the core network shall discard any message whose N(SD) is not the increment by one (modulo 4) of the N(SD) received during the redirection procedure.
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. |
bbc07dc9647184161b1f5af7180e8116 | 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 type 1 standard IEs) must appear by pair. The first half-octet IE occupies bits 1 to 4 of octet N, the second half-octet IE bits 5 to 8 of octet N, the third half-octet IE bits 1 to 4 of octet N + 1 etc. If the number of half-octet IEs is odd then bits 5 to 8 of the last octet occupied by these half-octet IEs contains a spare half-octet IE in format V.
If message is received as a standard L3 message, and that is too short to contain the complete imperative part as specified in the relevant protocol specification, an imperative message part error is diagnosed. (The same error may be diagnosed at detection of certain contents of the imperative part of a message; this is defined in the relevant protocol specification.) The treatment of an imperative message part error is defined in the relevant protocol specification. |
bbc07dc9647184161b1f5af7180e8116 | 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 format T, TV, TLV or TLV-E. The receiver of a standard L3 message shall analyse the non imperative part as a succession of standard IEs each containing an IEI, and shall be prepared for the non-imperative part of the message to contain standard IEs that are not specified in the relevant protocol specification.
An IEI may be known in a message or unknown in a message. Each protocol specification lists, for each message (i.e., according to the message type, the direction and the lower layer SAP), the known standard IEs in the non-imperative part.
An IEI that is known in a message designates the IE type of the IE the first part of which the IEI is, as well as the use of the information. Which IE type it designates is specified in the relevant protocol specification. Within a message, different IEIs may designate the same IE type if that is defined in the relevant protocol specification.
Whether the second part of an IE with IEI known in a message is the length or not (in other words, whether the IEI is the first part of an IE formatted as TLV, TLV-E or not) is specified in the relevant protocol specification.
Unless otherwise specified in the protocol specification, the receiver shall assume that IE with unknown IEI are TV formatted type 1, T formatted type 2, TLV formatted type 4 or TLV-E formatted type 6 standard IEs. The IEI of unknown IEs together with, when applicable, the length indicator, enable the receiver to determine the total length of the IE, and then to skip unknown IEs. The receiver shall assume the following rule for IEs with unknown IEI:
Bit 8 of the IEI octet is set to "1" indicates a TV formatted type 1 standard IE or a T formatted type 2 IEs. Hence, a 1 valued bit 8 indicates that the whole IE is one octet long. The respective IEI includes a value in the range from hexadecimal 8 to F in bits 8 to 5.
Furthermore, for the EPS protocols EMM and ESM:
Bit 8 of the IEI octet set to "0" and bits 7 to 4 set to "1" indicates a TLV-E formatted type 6 IE, i.e. the following two octets are length octets. The respective IEI value range is from hexadecimal 78 to 7F. Bit 8 of the IEI octet set to "0" and bit 7 to 4 set to any other bit combination indicates a TLV formatted type 4 IE, i.e. the following octet is a length octet. The respective IEI value range is from hexadecimal 00 to 77.
Furthermore, for the 5GS protocols 5GMM and 5GSM:
Bit 8 of the IEI octet set to "0" and bits 7 to 5 set to "1" indicates a TLV-E formatted type 6 IE, i.e. the following two octets are length octets. The respective IEI value range is from hexadecimal 70 to 7F. Bit 8 of the IEI octet set to "0" and bit 7 to 5 set to any other bit combination indicates a TLV formatted type 4 IE, i.e. the following octet is a length octet. The respective IEI value range is from hexadecimal 00 to 6F.
The above rule for the IEI value encoding for 5GMM and 5GSM is not applicable to the IEIs of type 6 IEs included in the Type 6 IE container information element specified in 3GPP TS 24.501 [31], clause 9.11.3.98. The IEIs in such an information element can take any value in the range 00 to FF (hexadecimal).
IEI assignment in 3GPP TS 24.334 [36] shall comply with the above rule for the EPS protocols EMM and ESM.
IEI assignment in 3GPP TS 24.519 [33], 3GPP TS 24.587 [34], 3GPP TS 24.193 [35], 3GPP TS 24.554 [38], 3GPP TS 24.572 [40], 3GPP TS 24.514 [41] and 3GPP TS 24.577 [42] shall comply with the above rule for the 5GS protocols 5GMM and 5GSM.
IEI assignment for UE policy delivery service in 3GPP TS 24.501 [31] shall comply with the above rule for the 5GS protocols 5GMM and 5GSM.
For all other protocols:
Bit 8 of the IEI octet set to "0" indicates a TLV formatted type 4 IE. Hence, the following octet is a length octet.
As a design rule, it is recommended that IEIs of any TV formatted type 1, T formatted type 2, TLV formatted type 4 or TLV-E formatted type 6 IE follow the rule, even if assumed to be known by all potential receivers.
As a design rule, it is recommended that no T formatted type 2 IE is added to the non-imperative part of a standard L3 message.
NOTE 1: Type 2 IEs restrict the number of possible type 1 IEs which can be used in a message and type 2 IEs cannot be extended or modified once introduced.
As a design rule, it is recommended that no new TV formatted type 3 IE is added to the non-imperative part of a standard L3 message except in the first release of a protocol specification which specifies the standard L3 message.
NOTE 2: For example, for the 5GS protocols 5GMM and 5GSM, Release 15 is the first release of a protocol specification for REGISTRATION REQUEST message.
A message may contain two or more IEs with equal IEI. Two IEs with the same IEI in a same message must have the same format, and, when of type 3, the same length. More generally, care should be taken not to introduce ambiguities by using an IEI for two purposes. Ambiguities appear in particular when two IEs potentially immediately successive have the same IEI but different meanings and when both are non-mandatory. As a recommended design rule, messages should contain a single IE of a given IEI.
Each protocol specification may put specific rules for the order of IEs in the non-imperative part. An IE known in the message, but at a position non compliant with these rules is said to be out of sequence. An out of sequence IE is decoded according to the format, and, when of type 3 the length, as defined in the message for its IEI. |
bbc07dc9647184161b1f5af7180e8116 | 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 not present. An IE belonging to the imperative part of a message has presence requirement M. An IE belonging to the non-imperative part of a message may have presence requirement M;
- C ("Conditional") means:
* that inclusion of the IE by the sender depends on conditions specified in the relevant protocol specification;
* that there are conditions for the receiver to expect that the IE is present and/or conditions for the receiver to expect that the IE is not present in a received message of a given PD, SAP and message type; these conditions depend only on the content of the message itself, and not for instance on the state in which the message was received, or on the receiver characteristics; they are known as static conditions;
* that the receiver detecting that the IE is not present when sufficient static conditions are fulfilled for its presence, shall diagnose a "missing conditional IE" error;
* that the receiver detecting that the IE is present when sufficient static conditions are fulfilled for its non-presence, shall diagnose an "unexpected conditional IE" error.
- Only IEs belonging to the non-imperative part of a message may have presence requirement C;
- O ("Optional") means that the receiver shall never diagnose a "missing mandatory IE" error, a "missing conditional IE" error, or an "unexpected conditional IE" error because it detects that the IE is present or that the IE is not present. (There may however be conditions depending on the states, resources, etc. of the receiver to diagnose other errors.) Only IEs belonging to the non-imperative part of a message may have presence requirement O.
Unless otherwise specified the presence of a IE of unknown IEI or of an out of sequence IE shall not lead by itself to an error. An alternative specification is the 'comprehension required' scheme. A type 4 IE is encoded as 'comprehension required' if bits 5, 6, 7 and 8 of its IEI are set to zero. A type 6 IE is encoded as 'comprehension required' if bit 8 is set to zero and bits 2, 3, 4, 5, 6, and 7 of its IEI are set to one.
NOTE: In earlier versions of this specification, type 6 IEs with IEI values 7C and 7D were defined as 'comprehension required'. I.e., dependent on the protocol, receipt of such an IE by a UE or network implemented according to an earlier version of this specification can result in detection of an "invalid mandatory information" error. Therefore, IEIs 7C and 7D can be used for type 6 IEs only if the sender of the message knows that the receiver does not treat these IEs as unknown 'comprehension required' IEs.
The 'comprehension required' scheme is to be applied if explicitly indicated in the protocol specification. The reaction on the reception of an unknown or out of sequence IE coded as 'comprehension required' is specified in the relevant protocol specification. |
bbc07dc9647184161b1f5af7180e8116 | 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 hexadecimal representation (one digit followed by and hyphen for TV formatted type 1, and two digits for the other cases);
- the name of the IE (this is used in particular for the description of conditional presence rules);
- the type of the information element, with a reference of where the internal structure of the value part is specified;
- the format of the standard IE (T, V, TV, LV, TLV, LV-E or TLV-E); and
- the length, or the range of lengths, of the whole standard IE, including when applicable the T and L parts.
The list of elements is given in the table in the order they appear in the resulting bit string, with the exception of half‑octet elements in the imperative part: half octets in a pair are inverted. This applies in particular for the two first header elements: the protocol discriminator appears first in a table describing a standard L3 message. |
bbc07dc9647184161b1f5af7180e8116 | 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 consistent structures are found in the present protocol specifications, and are described hereafter.
Other structures can be described directly in the protocol specifications. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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;
Bit 2 is set to "0";
Bit 1 is set to "1".
A receiver expecting a message so structured and receiving a message with bit 1 of octet 1 (i.e., the 8th bit of the message) set to "1" and bit 2 of octet 1 (i.e., the 7th bit of the message) different from "0", shall abandon the analysis of the message.
A receiver expecting a message so structured and receiving a message on AGCH/PCH:
- with an L2 pseudo length indicator encoding 0 or 1 shall skip the indicated number of octets and not try to analyse the standard L3 message part;
- with a L2 pseudo length indicator bigger than what is compatible with the SAP capability shall abandon the analysis of the message. |
bbc07dc9647184161b1f5af7180e8116 | 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, using the compact notation described in Annex B of the present document. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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 following description includes the 2-bit link layer header. |
bbc07dc9647184161b1f5af7180e8116 | 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.
All additional PD defined for this structure shall start by 1. The reception of a message with bit 8 of octet 1 set to 1 when expecting a message structured as defined by this clause shall be diagnosed as an unknown PD, and the message ignored.
As a design rule, a message type field should follow the PD, and of a length such that the PD and the message type fit in the 6 first bits of the message. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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 carrying an elementary semantic information. An information element should be composed of (possibly) a tag, than (possibly) a length indicator, then a value part.
Tags can be of fixed or variable length, their extent being analysable from beginning to end. A typical tagging is the one bit tagging, which should preferably used as follows: value "0" indicates that the IE is no more than the tag bit, and "1" indicates that the IE continues at least with the next bit.
Variable length tagging should be used to distinguish between several possible formats of the element. Tag lengths are then chosen according to packing efficiency criteria.
The T field of standard IEs can be presented as a variable tagging with only two lengths: 4 and 8 bits.
The length indicator can be of fixed or variable length, their extent being analysable from beginning to end. It should preferably be presented as encoding the length in bits of the value part.
The L field of standard IEs can be presented as a fixed length (one octet) length indicator which can encode only lengths multiple of 8 bits.
The value part can be described as further structured, in a similar way. This can be used to help the reading, and to cover some presence dependence. |
bbc07dc9647184161b1f5af7180e8116 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 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 syntactically correct. |
bbc07dc9647184161b1f5af7180e8116 | 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 value part. - It is not a syntactical error that a type 4 and type 6 standard IE specifies in its length indicator a greater length than possible according to the value part specification: extra bits shall be ignored. - It should not be considered a syntactical error if a type 4 and type 6 IE is received with a shorter length than defined in this version of the specification if the IE is correctly encoded according to an earlier version of the specification. - A message is defined to have semantically incorrect contents if it contains information which, possibly dependant on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part. Annex A (informative): MN‑Services arrow diagram Figure A.1: Mobile originated Call Setup. Successful case Figure A.2: Mobile terminated Call Setup. Successful case Figure A.3: Mobile originated, Call Release and Channel Release. Successful case Figure A.4: Location updating. Successful case Figure A.5: Handover. Successful case Figure A.6: Establishment of parallel transactions (General view) Figure A.7: Release of parallel transactions (General view) Annex B (informative): Description of CSN.1 The goal of the notation described hereafter is to describe the structure of the syntactically correct messages for a given signalling protocol, or of part of such messages. The notation addresses the cases where the concrete messages are binary strings. The notation allows to describe sets of strings: the structure of a message defined a protocol defines a set of allowable bit strings. It also allows to put labels on parts of strings that follow a given structure. One aspect of the specification of message set is to define the set of strings that are acceptable as when received. All the strings that cannot be recognized as syntactically correct messages are to be rejected for syntactical reasons. In many cases, only a subset of this set are allowed to be sent. The notation allows also to distinguish the set of the strings that can be sent and the set of strings that are recognized as syntactically correct. Another aspect of the specification of messages is the splitting of an acceptable string in a number of sub-strings that will be use to derive the exact significance of the message. The notation provides this function by labelling sub-strings. These labels can then in turn be used in textual or formal semantic descriptions which are not covered in the present document. The notation described here could be enhanced in the future, with the addition of new rules. B.1 The Basic Rules The following rules (B1 to B6) form the core part of the notation, more or less directly inherited from BNF. Rules B7 to B8 add what is needed in addition to encode the rest octet parts of fixed length messages as defined in 3GPP TS 24.008 [6]. Rule A1 is not needed to describe sets of strings at this stage. It is the one allowing to label parts of messages. B.1.1 Core Rules B.1.1.1 Rule B1: Bits A "bit string" is an ordered sequence of symbols, each belonging to a two-value set. The character "0" and "1" are used to indicate one bit, respectively of one or the other value. Formally, the notations « 0 » and « 1 » denote each a set composed of a single bit string of a single bit, of different values. In addition the word "bit" denotes the set of the two 1-bit long strings, namely 0 and 1. B.1.1.2 Rule B2: Null String Where needed, the word "null" call be used to indicate the null string, i.e., the string of no symbols. Formally, the notation « null » denote the set composed of a single bit string, the empty string. B.1.1.3 Rule B3: Concatenation A succession of two string descriptions describe the concatenation of the strings. More formally: a succession of two string descriptions describes the strings obtained by concatenation of one string taken in the subset described by the first string description and then one string taken in the subset described by the second string description. The rule extends to any number of string descriptions. For instance: 00 This denotes the set composed of the single bit string of length 2 composed of two zeros. B.1.1.4 Rule B4: Choice A list of choices is noted using as separator the character "|". An alternative notation uses instead the word "or" (this is not used in the present document). NOTE: An idea is to allow not to used strange characters, by giving in each case a verbose equivalent. This is not done systematically yet in the present document. Formally: the notation A | B, where A and B are string set descriptions, describes the set of the strings which are in the set described by A or in the set described by B, that is the union of sets described by A and B. The concatenation has a higher precedence than the choice. Examples: 00 | 01 This indicates that bit strings 00 and 01 are part of the set (10 and 11 are not). 0 | 1 Denotes the same set as "bit". The characters "{" and "}" are used for delimiting a string set description from what follows and/or precedes. 0 {0|1} This indicates the same set of bit strings as in the previous case. Precedence example: 10 | 11 1 0|1 Because of the priority rule, the two descriptions are not equivalent, the second noting the set (10, 1). It is allowed that the different sets in a choice have non null intersections. To allow message decoding, a rule must then be given to choose the branch. The rule is that any matching set can be chosen (the concatenation is a true set union). In practice, it is preferable to have non intersecting choice sets. Moreover, the ability to select the branch to take rapidly is important for obtaining simple message decoders. Except for strong reasons, a design should only include choice construction that can be rewritten using only constructions matching the pattern {a1 s1 |a2 s2} where a1 and a2 are non‑intersecting sets of strings of the same non-null length. A tolerable derogation is to use intersecting an. Examples: {100 xx | 001 zz} is acceptable. {00 xx | 010 yy | 011 zz} is acceptable, since it can be rewritten {00 xx | 01 {0 yy | 1 zz}}}. {{00|01|10} xx | {00|11} yy} is not recommended (the start 00 is ambiguous). In practice this covers fixed length tagging (like tagging by an IEI, or 1-bit tagging in rest octets), and also non-intersecting variable length tagging as used for instance in the frequency list IE (tag list such as 0, 100, 101, 110, 11100, 11101, 11110, 11111, where no tag is the start of another one). B.1.1.5 Rule B5: Naming The characters "<" and ">" are used to delimit a reference to the description of a string set. This can be used inside a string set description, to refer to a string set described elsewhere. For compilability, the name must be used somewhere else to define the corresponding string set. For a simple description, the description of the reference could be done by normal text. The name, that is the part sequence of characters between "<" and ">" must not be empty, and is constituted freely of characters, with the exception of "<" and ">". Case is not significant, nor are heading or tailing spaces. Any succession of space characters is treated as a single character. To avoid difficulties with more advanced rules, the use of the characters ":", "=", "(" and ")" should be avoided. More generally, it is not recommended to use many other characters, such as "<" for instance. The space character can (and should!) be used, to allow a good legibility for human beings. Example: <bit pair> B.1.1.6 Rule B6: Definition A reference followed by the character sequence "::=" followed by a string set description is used to associate the description with the reference, terminated when needed to separate it from a following definition and when compilability is looked for, by a semi-colon ' ;. Recursive definition is allowed, e.g., the reference can appears on the right hand side of the "::=". To avoid too much difficulties for would-be-compilers, only tail recursivity should be used, i.e., a recursive term should appear only as the last term of a definition. Examples: <bit pair> ::= 00 | 01 | 10 | 11 ; This could have been noted as well: <bit pair> ::= {00 | 01 | 10 | 11} ; or <bit pair> ::= {0|1} {0|1} ; Recursive example: <all bit strings> ::= null | { {0 | 1} <all bit strings>} ; Another recursive, but not tail-recursive (and then not recommended) example: <all bit strings> ::= null | {<all bit strings> {0 | 1}} ; B.1.2 Spare parts For the purpose of message description it is in many cases needed to specify differently the set of bit strings that are acceptable when received and the corresponding set of bit strings which may be sent. The second set is included in the first. A first example are the spare parts. Notations related to spare parts are different in nature from the bit string set description seen so far. They define two sets as the same time, the sent set and the received set. A construction rule of general application will be defined in advanced rules. For the moment, only two ad-hoc constructions are described. B.1.2.1 Rule B7: Spare bits The following construction: <spare bit> describes a 0 when emitted and a bit (0 or 1) in reception. B.1.2.2 Rule B8: Padding bits An issue specific to the GSM radio interface protocols is that in some cases the messages cannot take arbitrary lengths. Padding is then necessary to fill up the message up to the desired length. Moreover, the padding uses a particular sequence of bits, of fixed position, i.e., the value of a padding bit depends on its position relative to the start of the message. The padding sequence is protocol-specific. In most cases it is constituted of all 0 values, in which case the following notation is of no use. In the case of GSM 04.08, the padding sequence is the repetition of octet 00101011, starting on an octet boundary. The special notations "L" and "H" are used to denote the respectively the bit value corresponding to the padding spare bit for that position, and the other value. The notations "0", "1", "null", "L" and "H" are the only terminals in CSN.1. Padding spare bits are bits which are set to the indicated value in emission whereas in reception any bit string is acceptable. The following notation: <spare L> describes a bit which has a logical value L in emission, and is a bit (0 or 1) in reception. The term <spare padding> denotes the required padding spare bits needed to fill up the message. The construction can be developed only partially from the rules described so far, because the length limitation does not appear in the following description: < spare padding> ::= <spare L> {null | < spare padding>}; B.1.3 Predefined sets The notation allows a modular description of the messages. This means in particular the possibility to build a library of bit string set definitions to be used wherever needed. The following is an example of an elementary library, which could be specified once and can be used in other specifications without being redefined. <bit> ::= 0|1 ; <bit (1)> ::= <bit>; <bit (2)> ::= <bit> <bit>; <bit (3)> ::= <bit (2)> <bit>; <bit (4)> ::= <bit (3)> <bit>; <bit (5)> ::= <bit (4)> <bit>; <bit (6)> ::= <bit (5)> <bit>; <bit (7)> ::= <bit (6)> <bit>; <octet> ::= <bit (7)> <bit>; <half octet> ::= <bit (4)>; <spare half octet> ::= <spare bit><spare bit><spare bit><spare bit>; <spare padding> ::= <spare L> {null | <spare padding>}; <octet string(i)> ::= <octet>(i) ; -- for any positive or null integer i <bit(i)> ::= <bit>(i); -- for any positive or null integer I <bit string> ::= bit**; <octet string> ::= <octet>**; NOTE 1: The definition of generic constructions such as <bit string(i)> is somewhat cumbersome with only the basic rules. More advanced rules would allow a much more compact notation. NOTE 2: The use of the characters "(" and ")" within a reference is done consistently with potential advanced rules. NOTE 3: This basic library is not exhaustive and can be extended when the needs arise. B.1.4 Labelling Parts B.1.4.1 Rule A1: Labels Delimited names as defined by Rule B6 identify sets of sub strings. In many cases this can be used within the context of a message to refer to the specific part of the message. However, this is not of general application, since it may happen that two parts of a message follow the same structure, and economy of notation requires that the structure is described but once. The general syntax that follows allows to refer to a part inside a description: <name1 : string description> For the definition of string sets, this is equivalent to the string description being used alone. The name used as a label can be built according to the rules applicable to parenthesed references. Examples: <Tag : 000 > <Field : <Field type>> <Field : octet> The third example shows the use of a non parentheses reference to obtain a more elegant expression than, for instance, the second example. At this stage, labels has no use for describing message syntax, but can be used to refer to the corresponding part of the string, e.g., in the description of the message specifying the relationship between the syntactical content and the semantical contents of the message, or to associate properties with effective sub-strings in effective messages (rather than with sets of sub strings). Syntactical use of the semantical identifier are presented in more advanced rules. The same name may appear in several places. Designers have to be careful to use non ambiguous names if non‑ambiguous reference is desired. B.1.5 Goodies B.1.5.1 Rule G1: Comments Comments can be added, starting with the term "--" and ended by the end of line. Comments can be used in particular to indicate the section where a particular description can be found. B.2 Advanced rules B.2.1 Rule A2: Exponent notation An arithmetic expression used as exponent after a delimited string description is used to indicate repetitions. A numerical expression between parentheses indicates a fixed number of repetitions. <octet> ::= {0 | 1}(8) ; is equivalent to <octet> ::= {0 | 1} {0 | 1} {0 | 1} {0 | 1} {0 | 1} {0 | 1} {0 | 1} {0 | 1} ; This could also be written: <octet> ::= bit(8) ; When the exponent is negative or equal to 0, the exponentiated construction is equivalent to the null string. An example of a common construction is the following: <name : bit(5)> Simple arithmetic, using numbers, terms "+", "-", "*" and "/", and parentheses are allowed in expressions. Example: <octet string(40)> ::= <octet>(8*(4+1)) ; A star used alone between parentheses, or a double star, indicates a finite, possibly null, but indeterminate, number of repetitions. (The star used as an exponent can be understood also as meaning the union of all the sets obtained by replacing the star by zero or some positive integer). <all bit strings> ::= {0 |1}(*) ; <all bit strings> ::= {0 |1}** ; This allows a shorter notation of recursive constructions such as: <all bit strings> ::= {0|1} <all bit strings> | null; A shorter notation is allowed when the expression has a single term, consisting of a star followed by the term: <octet> ::= {0 | 1}*8 ; <octet string(40)> ::= <octet>*(8*(4+1)) ; <all bit strings> ::= bit**; Application note: The indefinite exponent is usually combined with some mean to indicate to the decoder the end of the repetition. Different techniques exist, such as indicating in a previous field the number of repetitions. Another technique is one-bit tagging, an example of which follows: {1 <item>}** 0. Annex C (informative): GPRS‑Services sequence diagram Instead of providing a complete set of all scenarios, the intention of this clause is to provide some typical examples. It shall be noted, that within the figures only those parameters of the PDUs and the service primitives are shown, which are needed for a general understanding of the examples. Furthermore during the examples below (except C.17) no cell re‑selection takes place. NOTE: The standalone PDP context modification procedure should use graceful disconnection of the LLC link. Annex D (informative): Change history TSG SA# Spec Version CR Rev Rel New Version Subject Comment Jun 1999 GSM 04.07 7.1.0 Transferred to 3GPP CN CN#04 24.007 3.0.0 CN#5 24.007 3.0.0 002 1 R99 3.1.0 Addition of LL-STATUS_IND CN#6 24.007 3.0.1 004 1 R99 3.2.0 Uplink L3 Message Sequencing CN#6 24.007 3.0.1 005 R99 3.2.0 Mirror R99 LCS CR to 04.07 CN#6 24.007 3.0.1 003 5 R99 3.2.0 Using MM sublayer for PS-SMS message transfer CN#6 24.007 3.0.1 001 5 R99 3.2.0 Transaction Identifier Extension CN#7 24.007 3.2.0 006 1 R99 3.3.0 Updating Session Management (SM) for R99 CN#7 24.007 3.2.0 007 R99 3.3.0 Removal of Anonymous Access CN#7 24.007 3.2.0 008 R99 3.3.0 PMMSMS-REL-Req deletion in MS side CN#7 24.007 3.2.0 010 1 R99 3.3.0 Integrity checking of signalling messages for UMTS - 24.007 3.3.0 - - R99 3.3.1 Editorial changes TSGN TSGN-number WG Number Spec CR Rev Rel Cat Old vers New ver Title WI Notes/Date CN#8 NP-000270 N1-000620 24.007 006 2 R99 F 3.3.1 3.4.0 Updating SM for R99 GSM/UMTS Interworking CN#8 NP-000270 N1-000619 24.007 012 R99 F 3.3.1 3.4.0 Remove GRR primitive descriptions and make reference to other document GSM/UMTS Interworking CN#8 NP-000269 N1-000763 24.007 014 2 R99 F 3.3.1 3.4.0 Change of the GMM Ready Timer behaviour GPRS CN#08 NP-000269 N1-000668 24.007 015 R99 C 3.3.1 3.4.0 New PD for LLC for use by DTM (Dual Transfer Mode) mobiles GPRS CN#8 NP-000270 N1-000669 24.007 016 R99 C 3.3.1 3.4.0 Services provided by the Radio Resource Management entity GSM/UMTS Interworking CN#9 NP-000443 N1-001032 24.007 013 3 R99 F 3.4.0 3.5.0 SAPs and Service primitives for UMTS, PS mode. GSM/UMTS Interworking adapted to adjust the older used release of the spec CN#9 NP-000443 N1-000880 24.007 018 R99 F 3.4.0 3.5.0 Protocol discriminator value for UE special conformance testing functions GSM/UMTS Interworking CN#9 NP-000443 N1-001015 24.007 019 1 R99 F 3.4.0 3.5.0 Correction of send sequence number method applied protocols GSM/UMTS Interworking CN#9 NP-000443 N1-000930 24.007 020 R99 F 3.4.0 3.5.0 Editorial corrections!! GSM/UMTS Interworking CN#9 NP-000441 N1-000969 24.007 021 R99 F 3.4.0 3.5.0 Protocol Discriminator for DTM (simple class A) GPRS NP-10 NP-000673 N1-001188 24.007 024 R99 F 3.5.0 3.6.0 Removal of Flow Id from RR-SAP TEI NP-10 NP-000670 N1-001367 24.007 025 1 R99 F 3.5.0 3.6.0 RABMAS-SAP and RABMSM-SAP adaptation for Handling of unsynchronized PDP contexts GPRS NP-10 NP-000671 N1-001246 24.007 027 R99 F 3.5.0 3.6.0 Updating CS/PS protocol architecture figure with RABM GSM/UMTS Interworking NP-10 NP-000671 N1-001256 24.007 028 R99 F 3.5.0 3.6.0 Alignment of 24.007 to other specs GSM/UMTS Interworking NP-11 NP-010123 N1-010101 24.007 025 2 R99 F 3.6.0 3.7.0 Addition of Stream Identifier and NAS Synchronization Indicator to the primitives GSM/UMTS interworking 03-2001 NP-11 NP-010123 N1-010083 24.007 032 R99 F 3.6.0 3.7.0 Change MMAS-SAP to RR-SAP in fig. 5.6 GSM/UMTS interworking 03-2001 NP-11 NP-010207 N1-010486 24.007 034 R99 F 3.6.0 3.7.0 Transfer of the N(SD) duplication avoidance protocol from GSM 04.18 GSM/UMTS interworking 03-2001 NP-11 NP-010205 N1-010447 24.007 035 R99 F 3.6.0 3.7.0 Deletion of cause 'unsynchronousPDP' in RABMAS-SAP TEI 03-2001 NP-11 NP-010206 N1-010444 24.007 031 3 Rel-4 B 3.7.0 4.0.0 Adaptation of SS protocol to PS domain TEI 03-2001 NP-14 NP-010682 N1-011811 24.007 043 1 Rel-4 A 4.0.0 4.1.0 Clarification of the send sequence number mechanism GSM/UMTS interworking 12-2001 NP-16 NP-020218 N1-021341 24.007 047 2 Rel-4 A 4.1.0 4.2.0 RR protocol message type octet GSM/UMTS interworking 06-2002 NP-16 NP-020222 N1-020893 24.007 049 1 Rel-4 A 4.1.0 4.2.0 Clarification of the extension mechanism for type 4 IEs TEI 06-2002 NP-16 NP-020224 N1-021367 24.007 053 1 Rel-4 F 4.1.0 4.2.0 Various clean-up of wrong references, eg towards 44.018 and 23.271 TEI4 06-2002 NP-16 24.007 Rel-5 4.2.0 5.0.0 Plenary decision to make this TS also for Rel-5. 06-2002 NP-17 NP-020383 N1-021836 24.007 057 1 Rel-5 F 5.0.0 5.1.0 Clarification of the CN release indicators TEI5 09-2002 NP-22 NP-030485 N1-031653 24.007 059 1 Rel-6 F 5.1.0 6.0.0 Don't use SAPI to differentiate between messages of the same message type. TEI6 12-2003 NP-24 NP-040185 N1-040967 24.007 063 1 Rel-6 A 6.0.0 6.1.0 Corrections concerning the use of the LCS protocol LCS 06-2004 NP-25 NP-040377 N1-041625 24.007 064 1 Rel-6 B 6.1.0 6.2.0 Update of the Session Management services - MBMS MBMS 09-2004 NP-25 NP-040375 N1-041645 24.007 067 4 Rel-6 B 6.1.0 6.2.0 Sequence number handling during redirection in MOCN sharing scenario NTShar 09-2004 NP-26 NP-040501 N1-04844 24.007 070 A 6.2.0 6.3.0 Sequence numbering for SS via PS TEI4 12-2004 NP-27 NP-050068 N1-050045 24.007 072 Rel-6 A 6.3.0 6.4.0 Addition of maximum data rate to RR_SYNC_IND and MMCC_SYNC_IND SCUDIF 03-2005 CP-29 CP-050361 C1-050966 24.007 074 Rel-6 F 6.4.0 6.5.0 Use of short header format on SDCCH / FACCH TEI6 09-2005 CP-29 CP-050366 C1-051030 24.007 075 1 Rel-7 F 6.5.0 7.0.0 Handling of the L2 Pseudo Length TEI7 09-2005 CP-42 CP-080866 C1-085163 24.007 0078 2 Rel-8 B 7.0.0 8.0.0 Support of EPS NAS protocols SAES 12-2008 CP-43 CP-090125 C1-091296 24.007 0082 2 Rel-8 F 8.0.0 8.1.0 UE side architecture figure without CSFB SAES 03-2009 CP-43 CP-090153 C1-091320 24.007 0083 2 Rel-8 F 8.0.0 8.1.0 Architecture figure for EPS UE + CSFB SAES-CSFB 03-2009 CP-43 CP-090130 C1-091182 24.007 0085 1 Rel-8 F 8.0.0 8.1.0 Message duplication in S1 mode SAES 03-2009 CP-43 CP-090125 C1-091106 24.007 0086 1 Rel-8 F 8.0.0 8.1.0 Add reference of LTE test control specification SAES 03-2009 CP-43 CP-090126 C1-091350 24.007 0087 2 Rel-8 F 8.0.0 8.1.0 Clarification of format of LV-E/TLV-E Length Indicator format SAES 03-2009 CP-43 24.007 Rel-8 8.0.0 8.1.0 Editorial cleanup by MCC 03-2009 CP-44 CP-090422 C1-092120 24.007 0090 1 Rel-8 F 8.1.0 8.2.0 Handling of sequence numbers SAES-SRVCC 06-2009 CP-46 Rel-9 8.2.0 9.0.0 Upgrade to Rel-9 by MCC 12-2009 CP-51 Rel-10 9.0.0 10.0.0 Upgrade to Rel-10 by MCC 03-2011 CP-56 CP-120309 C1-121630 24.007 0094 2 Rel-11 F 10.0.0 11.0.0 Clarify maintenance concept for this specification TEI11 06-2012 CP-60 CP-130264 C1-131596 24.007 0095 1 Rel-12 F 11.0.0 12.0.0 CM sublayer of EPS services TEI12 06-2012 CP-60 CP-130264 C1-131744 24.007 0096 2 Rel-12 11.0.0 12.0.0 Clarify on specification maintenance TEI12 06-2012 CP-70 24.007 Rel-13 12.0.0 13.0.0 Upgrade to Rel-13 by MCC 12-2015 Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2017-03 CP-75 CP-170129 0099 2 B Addition of ePCO for GPRS 14.0.0 2018-03 CP-79 CP-180075 0100 1 B Extended protocol discriminator 15.0.0 2018-03 CP-79 CP-180075 0101 1 B Update of protocol discriminator values for test procedures for 5GS 15.0.0 2018-03 CP-79 CP-180075 0103 2 B For 5GS - UE protocol architecture 15.0.0 2018-03 CP-79 CP-180075 0104 2 B For 5GS – message and security headers and PDU session identities 15.0.0 2018-03 CP-79 CP-180075 0107 B Format of standard IE for 5GS 15.0.0 2018-03 CP-79 CP-180075 0108 1 B Scope update for 5GS 15.0.0 2018-03 CP-79 CP-180075 0110 B Definition of 5GS NAS message type for 5GS 15.0.0 2018-06 CP-80 CP-181057 0111 1 B Specification of security protected 5GS NAS message header 15.1.0 2018-06 CP-80 CP-181069 0112 2 B EPS bearer identity in NAS message header 15.1.0 2018-06 CP-80 CP-181057 0113 1 B Include TS 24.501 and TS 24.502 among the layer 3 related Technical Specification 15.1.0 2018-06 CP-80 CP-181058 0114 2 B PDU session identity 15.1.0 2018-09 CP-81 CP-182128 0116 2 F Interaction when uplink user data packet is to be sent via a PDU session with suspended user-plane resources 15.2.0 2018-09 CP-81 CP-182128 0117 1 F Correction on PTI definition 15.2.0 2018-09 CP-81 CP-182128 0118 1 F Multiple access technologies in NG-RAN carrying 5GS NAS 15.2.0 2018-12 CP-82 CP-183030 0121 2 F Value range of IEs for 5GMM and 5GSM protocols 15.3.0 2018-12 CP-82 CP-183030 0122 F Correction to scope 15.3.0 2019-03 CP-83 CP-190105 0123 F EPS bearers not released when moving to EMM-IDLE 16.0.0 2019-06 CP-84 CP-191145 0124 F EPS bearers not released when moving to EMM-IDLE 16.1.0 2020-03 CP-87e CP-200128 0128 3 D Correcting reference 16.2.0 2020-06 CP-88e CP-201131 0129 1 F Type 3 IE is not recommended to be used as an optional IE 16.3.0 2020-09 CP-89e CP-202170 0130 1 F IEI assignment rule between TSN AF and TSN translator 16.4.0 2020-12 CP-90e CP-203188 0132 F Updates due to eV2XARC 16.5.0 2020-12 CP-90e CP-203218 0133 F Include TS 24.519 among the layer 3 related Technical Specifications 16.5.0 2020-12 CP-90e CP-203179 0134 1 F Updates due to ATSSS 16.5.0 2020-12 CP-90e CP-203213 0138 F Updates due to ProSe signalling messages sent over the PC3 or PC5 interfaces 16.5.0 2020-12 CP-90e CP-203214 0131 1 F Recommendation about the use of type 2 IEs 17.0.0 2020-12 CP-90e CP-203168 0135 1 F PDU session IDs exclusive for the 5G core network 17.0.0 2020-12 CP-90e CP-203168 0136 F IEI assignment from UE policy delivery service 17.0.0 2020-12 CP-90e CP-203214 0139 F Coding of successive half-octet IEs 17.0.0 2021-03 CP-91e CP-210116 0140 F UE policy delivery service missing 17.1.0 2021-06 CP-92e CP-211150 0141 1 Corrections to L3 Messages description 17.2.0 2022-03 CP-95e CP-220268 0142 - B Add new TS 24.554 17.3.0 2022-06 CP-96 CP-221111 0144 1 B Include TS 24.538 among the layer 3 related technical specifications 17.4.0 2022-09 CP-97 CP-222158 0146 1 C Correction of the comprehension required criterion 17.5.0 2023-09 CP-101 CP-232201 0148 3 B Addition of Location Services user plane protocol 18.0.0 2023-12 CP-102 CP-233190 0149 1 F Correction to the applicability of TS 24.587 18.1.0 2023-12 CP-102 CP-233128 0150 - B Addition of Location Services user plane protocol 18.1.0 2024-06 CP-104 CP-241153 0154 1 F Include TS 24.572 among the layer 3 related Technical Specifications 18.2.0 2024-06 CP-104 CP-241192 0153 1 F Update to support rangingsl 18.2.0 2024-06 CP-104 CP-241202 0156 2 F Include TS 24.577 among the layer 3 related Technical Specifications 18.2.0 2024-09 CP-105 CP-242193 0157 2 F Aligning the extended PC5 signalling protocol for ranging and sidelink positioning usage across the specs 18.3.0 2024-09 CP-105 CP-242201 0158 1 F Correction to use of type 6 IEs 19.0.0 2024-12 CP-106 CP-243200 0159 1 F Adding a reference to Type 6 IE container IE 19.1.0 2024-12 CP-106 CP-243196 0161 - F Correction of EPD for 5GS message routing 19.1.0 |
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 narrow-band to wide-band communications capability with integrated personal and terminal mobility to meet the user and service requirements of the 21st century.
3GPP specifications allow the realisation of a new generation of mobile communications technology for a world in which personal communications services should allow person-to-person calling, independent of location, the terminal used, the means of transmission (wired or wireless) and the choice of technology. Personal communication services should be based on a combination of fixed and wireless/mobile services to form a seamless end-to-end service for the user.
3GPP specifications should be in compliance with the following objectives:
a) to provide a single integrated system in which the user can access services in an easy to use and uniform way in all environments;
b) to allow differentiation between service offerings of various serving networks and home environments;
c) to provide a wide range of telecommunications services including those provided by fixed networks and requiring user bit rates of up to 100 Mbit/s as well as services special to mobile communications. These services should be supported in residential, public and office environments and in areas of diverse population densities. These services are provided with a quality comparable with that provided by fixed networks such as ISDN and fixed broadband Internet access;
d) to provide services via hand held, portable, vehicular mounted, movable and fixed terminals (including those which normally operate connected to fixed networks), in all environments (in different service environments - residential, private domestic and different radio environments) provided that the terminal has the necessary capabilities;
e) to provide support of roaming users by enabling users to access services provided by their home environment in the same way even when roaming.
f) to provide audio, data, video and particularly multimedia services;
g) to provide for the flexible introduction of telecommunication services;
h) to provide within the residential environment the capability to enable a pedestrian user to access all services normally provided by fixed networks;
i) to provide within the office environment the capability to enable a pedestrian user to access all services normally provided by PBXs and LANs;
j) to provide a substitute for fixed networks in areas of diverse population densities, under conditions approved by the appropriate national or regional regulatory authority.
k) to provide support for interfaces which allow the use of terminals normally connected to fixed networks. |
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.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. |
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 services"
[6] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)"
[7] 3GPP TS 22.066: "Support of Mobile Number Portability (MNP); Service description; Stage 1"
[8] 3GPP TS 22.079: "Support of Optimal Routeing (SOR); Service definition; Stage 1".
[9] 3GPP TS 22.129: "Handover Requirements between UTRAN and GERAN or other Radio Systems".
[10] Void
[11] 3GPP TS 22.011: "Service Accessibility".
[12] 3GPP TS 22.016: "International mobile Station Equipment Identities (IMEI)".
[13] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 Specification".
[14] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[15] 3GPP TS 21.133: "Security Threats and Requirements".
[16] 3GPP TS 33.120: "Security Principles".
[17] 3GPP TS 22.042: "Network Identity and Time Zone, Service Description, Stage 1".
[18] Void
[19] 3GPP TS 31.102: "USIM Application Characteristics".
[20] 3GPP TS 23.221: "Architectural Requirements".
[21] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)".
[22] Void
[23] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[24] 3GPP TR 23.972: "Circuit switched multimedia telephony".
[25] 3GPP TS 22.140: "Multimedia Messaging Service (MMS); Stage 1".
[26] 3GPP TS 22.226: "Global Text Telephony, Stage 1".
[27] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1".
[28] RFC 3261: "SIP: Session Initiation Protocol".
[29] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[30] 3GPP TS 26.233: "Packet Switched Streaming Service (PSS); General Description".
[31] 3GPP TS 26.234: "Packet Switched Streaming Service (PSS); Protocols and Codecs".
[32] Void
[33] Void
[34] 3GPP TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface Release 4)".
[35] 3GPP TS 22.234: "Requirements on 3GPP system to wireless local area network (WLAN) interworking".
[36] 3GPP TS 31.101: "UICC-terminal interface; Physical and logical characteristics".
[37] OMA Device Management V1.2 specifications
[38] OMA Client Provisioning V1.1 specifications
[39] Void
[40] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
[41] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1".
[42] 3GPP TS 22.278: "Service Requirements for the Evolved Packet System (EPS)".
[44] 3GPP TS 22.071: "Location Services (LCS); Service description; Stage 1".
[45] 3GPP TR 22.985: "Service requirement for the 3GPP User Data Convergence (UDC), Release 9".
[46] EN 15722:2015: "Intelligent transport systems - eSafety - eCall minimum set of data (MSD)"
[47] 3GPP TS 23.226: "Global text telephony (GTT); Stage 2"
[48] 3GPP TS 22.220: "Service requirements for Home Node B (HNB) and Home eNode B (HeNB) ".
[49] ETSI TS 181 019 V2.0.0 (2007-11): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Business Communication Requirements".
[50] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows; stage 2".
[51] OpenID Foundation: "OpenID Authentication 2.0", http://openid.net/specs/openid-authentication-2_0.html.
[52] 3GPP TS 22.368: "Service requirements for Machine-Type Communications (MTC); Stage 1".
[53] OMA Presence API: "OMA-TS-REST_NetAPI_Presence-V1_0-20130212-C".
[54] IETF RFC-5491: "GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations".
[55] IETF RFC-5139: "Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)".
[56] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[57] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
[59] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
[64] 3GPP TS 32.130: "Network Sharing; Concepts and requirements" |
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.21: "RSP Architecture".
[63] GSMA SGP.01: "Embedded SIM Remote Provisioning Architecture". |
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 3GPP SSO Identity Provider using Operator-controlled credentials and without requiring user involvement.
3GPP SSO Identity Provider: An entity that maintains Operator-controlled identity and credential information for a user, performs 3GPP SSO Authentication, and asserts the user's identity to a Data Application Provider.
3rd Party SSO Identity Provider: An entity that maintains identity and credential information (that is not Operator-controlled) for a user, performs authentication, and asserts the user's identity to a Data Application Provider.
Attended Data Traffic: Data traffic of which the user is aware he/she initiated, e.g. based on the screen/keypad lock being deactivated, length of time since the UE last received any input from the user, known type of application (e.g. an application monitoring a user's health – "mHealth" – which may need its data always treated as Attended Data Traffic.)
eCall: A manually or automatically initiated emergency call (TS12 or IMS emergency call), from a vehicle, supplemented with a minimum set of emergency related data (MSD).
Data Application Provider: An entity that offers data application services to users (e.g., over the public Internet). The data applications can be browser or non-browser based services.
Free-to-air (FTA) TV: A TV service characterised by no content encryption and being made available at no additional cost to the end user.
Free-to-view (FTV) TV: A TV service characterised by optional content encryption and being made available at no additional cost to the end user.
Gateway UE: a UE, which acts as a gateway providing access to and from the 3GPP network for one or more non-3GPP devices that are connected to the gateway UE.
GERAN or UTRAN Sharing: The sharing of GERAN or UTRAN among a number of operators.
Hosting E-UTRAN/NG-RAN Operator: The Operator that has operational control of a Shared E-UTRAN and/or NG-RAN. With regard to management of the Shared E-UTRAN the Hosting E-UTRAN/NG-RAN Operator is a Master Operator [64].
Hosting RAN: The Shared RAN that is owned or controlled by the Hosting RAN Operator.
Hosting RAN Operator: The Operator that has operational control of a Shared NG-RAN, Shared E-UTRAN, Shared GERAN or UTRAN.
IMS Centralized Services: The provision of communication services wherein services and service control are based on IMS mechanisms and enablers, and support is provided for a diversity of access networks (including CS domain and IP based, wireless and wireline), and for service continuity between access networks.
MSD: The Minimum Set of Data [46] forming the data component of an eCall sent from a vehicle to a Public Safety Answering Point or other designated emergency call centre. The MSD has a maximum size of 140 bytes and includes, for example, vehicle identity, location information and time-stamp.
NG-RAN: A radio access network connecting to the 5G core network which uses NR, E-UTRA, or both.
Participating Operator: Authorized operator that is using Shared NG-RAN, Shared E-UTRAN, Shared GERAN or UTRAN resources provided by a Hosting RAN Operator.
RAN user plane congestion: The situation where the demand for RAN resources to transfer user data exceeds the available RAN capacity to deliver the user data for a significant period of time in the order of few seconds or longer.
(S)Gi-LAN: The network infrastructure connecting to 3GPP network over the SGi or Gi reference point that provides various IP-based services (e.g. NAT, antimalware, parental control, DDoS protection, video optimization).
Shared E-UTRAN: E-UTRAN that is shared among a number of operators.
Shared RAN: GERAN, UTRAN, E-UTRAN or NG-RAN that is shared among a number of operators.
Shared GERAN or UTRAN: GERAN or UTRAN that is shared among a number of operators.
Shared NG-RAN: NG-RAN that is shared among a number of operators.
SSO Provider: An entity that provides SSO Service. The SSO Provider enables a user to authenticate to an IdP and thereby to have their identity asserted to a DAP. Each data application, whether provided by different DAPs or the same DAP, may have its own policy regarding authentication. In the 3GPP SSO Service, the SSO Provider is the 3GPP Operator.
SSO Service: A service in which the user of a data application is authenticated once, and as a result of that authentication is provided with seamless and transparent access to multiple data applications offered by one or more Data Application Providers.
SSO Local User Authentication: Authentication performed by the UE that establishes the presence of the registered user of the data application by requiring input which only the registered user would be able to provide.
Subscribed TV service: A TV service which is characterised by requiring a subscription (to content owner, content provider, or MNO) in order to access the service.
Test eCall: A non-emergency services call that includes MSD transfer and other eCall features and helps verify support of eCall by an IVS.
Unattended Data Traffic: Data traffic of which the user is unaware he/she initiated, e.g. based on the screen/keypad lock being activated, length of time since the UE last received any input from the user, known type of app (e.g. an application monitoring a user's health – "mHealth" – may need its data never treated as Unattended Data Traffic.)
User: As defined in TR 21.905 [29]: An entity, not part of the 3GPP System, which uses 3GPP System services. Example: a person using a 3GPP System mobile station as a portable telephone.
Additional examples for a user in the context of this TS: a non-3GPP device connected to the 3GPP system via a gateway, or an application running on a UE.
User Identity: information representing a user in a specific context. A user can have several user identities, e.g. a User Identity in the context of his profession, or a private User Identity for some aspects of private life.
User Identifier: a piece of information used to identify one specific User Identity in one or more systems.
User Identity Profile: A collection of information associated with the User Identities of a user.
MUSIM UE: An ME with multiple USIMs. |
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 (eCall terminal and associated sub-systems in vehicle)
ME Mobile Equipment
OTT Over The Top
PC Personal Computer
SSO Single Sign-On |
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 multimedia services.
The aims are:
- to enable users to access a wide range of telecommunications services, including many that are today undefined as well as multi-media and high data rates.
- to facilitate the provision of a high quality of service (particularly speech quality) similar to that provided by fixed networks;
- to facilitate the provision of small, easy to use, low cost terminals with long talk time and long standby operation;
- to provide an efficient means of using network resources (particularly radio spectrum). |
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 operators to differentiate their services. At the same time however, this may reduce the complexity of providing a service across different operators' networks.
3GPP shall therefore preferentially standardise service capabilities. In circumstances where the service is meant to be used across different operators' networks, hence a common specification set is of paramount importance, the service should be standardised to a level of detail sufficient to ensure interoperability and interworking across different operators' networks. Service capabilities consist of bearers defined by QoS parameters and the mechanisms needed to realise services. These mechanisms include the functionality provided by various network elements, the communication between them and the storage of associated data. This TS provides a conceptual description of a service architecture and architecture requirements which aim to provide service capabilities. It is intended that these standardised capabilities should provide a defined platform which will enable the support of speech, video, multi-media, messaging, data, teleservices, user applications and supplementary services and enable the market for services to be determined by users and home environments. |
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 possible to control the access to service capabilities offered by a shared network according to the core network operator the user is subscribed to. |
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 network resources (particularly radio resources). |
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 the service (e.g. mobile originated and mobile terminated services) without interruption for those subscribers who are originally in the cell which receive the mass simultaneous registration traffic. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.3 Radio Interface | Service capabilities shall be provided in a wide range of radio operating environments (where a radio environment is characterised in terms of propagation environment, mobile equipment relative speeds and traffic characteristics). Although 3GPP aims to minimise the number of radio interfaces and to maximise commonality between them, it may utilise several radio interfaces, each optimised for different environments. Each radio interface may provide differing service capabilities. 3GPP specifications include UTRA(N) radio interface supporting two modes (TDD and FDD), an Evolved UTRA(N) radio interface and GERAN radio interface. Additionally, it may be possible to connect to the 3GPP system using radio interfaces and fixed access technologies specified outside of 3GPP.
3GPP specifications shall provide a mechanism which will enable a piece of user equipment (UE) to adapt to different radio interfaces as necessary and to determine the service capabilities available. The specifications shall also provide a mechanism which will enable a UE to select radio interfaces capable of providing appropriate service capabilities and support mobility between multiple radio interfaces. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.4 Real-time Resource Usage | To enable network operators to render services efficiently, dimension their networks and set tariffs that more accurately reflect radio resource usage, real time information on resource usage is needed. When requested, it shall be possible for the serving cell type (e.g. RAT), cell ID / UTRAN Service Area Identity and cell / Service Area capability usage (e.g. HSDPA, E-DCH) information to be made available to the core network. Cell / Service Area capability usage information may include, for example, user(s) identity, start and finish time of data transfer, up-link and down-link data rates, volumes of data and other statistical information. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.5 Selected IP Traffic Offload (SIPTO) for PS Domain only | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.5.1 Common Requirements for SIPTO in the Mobile Operator Network and SIPTO at the Local Network | The 3GPP system shall be able to offload selected traffic (e.g. internet) towards a defined IP network close to the UE's point of attachment to the access network.
The following requirements apply to Selected IP Traffic Offload:
- The mobile operator may enable/disable Selected IP Traffic Offload on a per UE per defined IP network basis (e.g. based on tariff, subscription type etc.).
- It shall be possible for IP traffic of a UE associated with a particular defined IP network to be offloaded while IP traffic of that same UE associated with other defined IP network(s) is not offloaded.
- It shall be possible to perform Selected IP Traffic Offload for pre-Release 10 UEs.
- Offloading selected IP traffic for a UE shall not affect services running in parallel for the same UE.
- The mobile operator shall be able to collect signalling performance measurements (e.g. session connection/disconnection, etc) related to Selected IP Traffic Offload for each user.
- Selected IP Traffic Offload shall not compromise the security of the mobile operator's network.
- Service Continuity of IP data session(s) for Selected IP Traffic Offload may be supported during the following mobility events:
- mobility between the macro network and H(e)NBs; and
- mobility between H(e)NBs.
During both these mobility events, based on home mobile operator policies, the impact of mobility events as perceived by the user shall be reduced by minimising any interruption to the data flow.
- It shall be possible for the HPLMN to provide the VPLMN with the following information for a particular user:
- An indication of whether the user's IP traffic is permitted to be subjected to Selected IP Traffic Offload in the visited network;
- The defined IP network(s) for which Selected IP Traffic Offload is permitted.
Requirements specific to SIPTO at the local residential/enterprise IP network can be found in section 5.9 in [48].
Some types of services (e.g. streaming services, VOIP, VPN, HTTPS-Based Services) cannot tolerate a change of IP address of the UE without disruption of the service.
SIPTO can be performed with or without coordination between the UE and the network. The following requirements apply to coordinated SIPTO:
- The 3GPP system shall be able to support multiple connections that are associated with the same defined IP network where each connection may or may not support IP address preservation.
- The 3GPP system shall be able to determine if an IP flow requires IP address preservation or not. Based on this determination, the 3GPP network shall be able to offload selected IP traffic in coordinated manner between UE and the network, in order to minimize service disruption.
- The 3GPP system shall be able to detect when a connection becomes suboptimal and decide when to establish a new optimal connection to the same defined IP network or use an existing connection.
Note 1: The definition of optimal and suboptimal can be based on a number of implementation criteria like geography, topology and load balancing etc.
- The 3GPP system shall minimize the number of connections of a UE without disrupting the UE’s services, e.g. to ensure economical use of network resources.
- The 3GPP system shall be able to ensure that the actual average aggregate bit rate for IP flows of packet data network connections associated with the same packet data network does not significantly exceed the subscribed aggregate maximum bit rate for this packet data network when two connections are used with the same defined IP network.
Note 2: Requirements for Coordinated SIPTO do not apply to IMS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.5.2 Requirements for SIPTO in the Mobile Operator Network | The following requirements apply to Selected IP Traffic Offload in the mobile operator network:
- The mobile operator shall be able to enable/disable Selected IP Traffic Offload for certain parts of the network.
- Selected IP Traffic Offload shall not compromise integrity and confidentiality of offloaded traffic.
- The mobile operator shall be able to collect statistics for the offloaded traffic for each user.
- The network shall be able to perform Selected IP Traffic Offload without any user interaction based on mobile operator policies.
- Service Continuity of IP data session(s) within the mobile operator network shall be supported for Selected IP Traffic Offload. Based on home mobile operator policies, the impact of mobility events within the macro network as perceived by the user shall be reduced by either:
- minimising any interruption to the data flow; or
- preventing interruption to the data flow e.g. for voice services.
- Service Continuity of IP data session(s) for Selected IP Traffic Offload may be supported during the following mobility events:
- mobility between the macro network and H(e)NBs; and
- mobility between H(e)NBs.
During both these mobility events, based on home mobile operator policies, the impact of mobility events as perceived by the user shall be reduced by preventing interruption to the data flow e.g. for voice services. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.6 Paging policy selection for LTE | The 3GPP core network shall be able to use these additional criteria for selecting a paging policy:
- mobility information on the UE (e.g. the UE is stationary, or moving only in a specified area)
- application characteristics that are known and trusted at the serving network (e.g. communication pattern, expected QoS (e.g. latency, reliability), and priority)
- likely location of the UE within the paging area |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.4 Compatibility with Global Standards | 3GPP specifications aim to be compatible with IMT-2000 and to provide global terminal mobility (roaming), enabling the user to take his/her terminal to different regions of the world and to be provided with services. It is probable that different regions of the world will adopt different radio interface technologies. IMT-2000, as a global standard, should therefore enable a IMT-2000 terminal to determine the radio interface technology and the radio interface standard used in a region. Global terminal roaming also requires the global standardisation of service capabilities. As far as possible the method of indication of the radio interface standard and available service capabilities shall be aligned with IMT-2000.
3GPP specifications shall enable users to access the services provided by their home environment in the same way via any serving network provided the necessary service capabilities are available in the serving network.
The 3GPP specifications will be available for the partner organisations to adopt as their regional standards. For example in Europe, ETSI may adopt them as standards for both GSM and UMTS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.5 Void |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.