7 PDUs and parameters
24.3223GPPRelease 17Stage 3TSTunnelling of IP Multimedia Subsystem (IMS) services over restrictive access networks
7.1 PDUs and parameters specific to FTT-IMS protocol
7.1.1 General
The least significant bit of a field is represented by the lowest numbered bit of the highest numbered octet of the field. When the field extends over more than one octet, the order of bit values progressively decreases as the octet number increases.
Figure 7.1.1-1 shows an example of a field where the most significant bit of the field is marked MSB and the least significant bit of the field is marked LSB.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|
|
MSB |
x |
x |
x |
x |
x |
x |
x |
octet 1 |
|
x |
x |
x |
x |
x |
x |
x |
x |
|
|
x |
x |
x |
x |
x |
x |
x |
LSB |
octet N |
Figure 7.1.1-1: Example of bit ordering of a field
7.1.2 Message types of FTT-IMS messages
7.1.2.1 Generic FTT-IMS envelope
Generic FTT-IMS envelope defines structure of messages passed via FTT-IMS.
Generic FTT-IMS envelope is coded according to figure 7.1.2.1-1 and table 7.1.2.1-1.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|
|
Type |
octet 1 |
|||||||
|
Length |
octet 2 octet 3 |
|||||||
|
Payload |
octet 4 octet n |
|||||||
Figure 7.1.2.1-1: Generic FTT-IMS envelope
Table 7.1.2.1-1: Generic FTT-IMS envelope
|
Type field indicates the envelope type. |
|
Length field indicates the length of the generic FTT-IMS envelope in octets. |
|
Payload field is an optional field and its value depends on the envelope type. |
7.1.2.2 IP packet envelope
IP packet envelope is coded according to figure 7.1.2.2-1 and table 7.1.2.2-1.
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|
|
Type |
octet 1 |
|||||||
|
Length |
octet 2 octet 3 |
|||||||
|
IP packet |
octet 4 octet n |
|||||||
Figure 7.1.2.2-1: IP packet envelope
Table 7.1.2.2-1: IP packet envelope
|
Type field is according to subclause 7.1.2.1 and is set to 1. |
|
Length field is according to subclause 7.1.2.1. The Length field value is bigger than 3. |
|
IP packet field contains an IPv4 packet according to IETF RFC 791 [5] or IPv6 packet according to IETF RFC 2460 [7]. |
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2013-08 |
CT1#84 |
C1-133160 |
Skeleton of TS from rapporteur |
0.0.0 |
|||
|
2013-08 |
CT1#84 |
C1-133161 C1-133157 |
Incorporate agreed P-CRs from CT1#84 |
0.0.0 |
0.1.0 |
||
|
2013-10 |
CT1#84bis |
C1-134105 C1-134445 |
Incorporate agreed P-CRs from CT1#84bis |
0.1.0 |
0.2.0 |
||
|
2013-12 |
CT-62 |
CP-130718 |
Version 1.0.0 created for presentation to CT62 for information |
0.2.0 |
1.0.0 |
||
|
2014-01 |
CT1#86 |
C1-140019 |
Minor corrections |
1.0.0 |
1.1.0 |
||
|
2014-02 |
CT-63 |
CP-140111 |
Version 2.0.0 created for presentation to CT-63 for approval |
1.1.0 |
2.0.0 |
||
|
2014-03 |
Post CT-63 |
Version 12.0.0 created after approval at CT-63 |
2.0.0 |
12.0.0 |
|||
|
2014-06 |
CT-64 |
CP-140332 |
0001 |
Editorial corrections |
12.0.0 |
12.1.0 |
|
|
2015-06 |
CT-68 |
CP-150329 |
0002 |
Aligning TLS profiles used by CT1 specifications with SA3 agreed TLS profile |
12.1.0 |
13.0.0 |
|
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
CT-75 |
Upgrade to Rel-14 |
14.0.0 |
||||
|
2018-06 |
SA-80 |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
|
2020-07 |
SA-88e |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
|
2022-03 |
CT-95e- |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |