B.2 Interworking aspects
23.2213GPPArchitectural requirementsRelease 17TS
B.2.1 Interworking scenario: UE assigned private IPv4 address
When IPv4 addressing is used, the UE, for example in case of MTC, is normally assigned a private IPv4 address due to the limitation of the public IPv4 address space. In case of MTC, the MTC Server may reside in the same private IPv4 address space as the UE, or the MTC Server may reside in public IPv4 address space. In the first case, the UE used for MTC and the MTC Server are in the same routable address space. In the latter case, the UE used for MTC and the MTC Server are located in different private IP address spaces.
Figure B.2.1-1: Application Server (e.g. MTC) in a public or private address space and UE in private address space
B.2.2 Use of Device triggering
For indirect and hybrid model, use of device triggering as described in TS 23.682 [38] may be used to handle NAT traversal in situations where the Server (e.g. MTC Server) or Application is attempting to communicate with UEs in a private IP address space. In addition device triggering may be used to get the device to initiate the communication with the Server or Application.
NOTE: The above mechanism can be applied to any application (e.g. MTC) which is able to use device triggering.
B.2.3 Specific APN use
For indirect and direct model (as described in TS 23.682 [38]), use of separate explicit Access Point Names (APN), and IPv4 address allocation performed following procedures as described in 3GPP specifications in TS 23.401 [27] and TS 23.060 [2] and TS 29.061 [37] resolves private IPv4 address usage issues.
Figure B.2.3-1: Example IP address assignment when the Server is owned by the MNO or by Application Provider using specific APNs
In case of MTC, the Server is either deployed by the PLMN operator or by an application provider who owns an MTC Server and uses a specific APN assigned by the PLMN. In both cases a tunnelling mechanism is used between the GGSN/P-GW and the PDN of the Server to allow carrying the IP packets enabling assignment of private IP addresses to the UE used for MTC. The tunnelling allows for connecting the PLMN with the Server(s) using public IP networks. Furthermore that tunnelling allows for setting up private network with multiple GGSNs/P-GWs and multiple Servers where every GGSN, P-GW or the Server can be deployed at a different location. By using a separate APN per application (provider) the Servers from different applications can use the same overlapping private IP addresses as needed without the need for the network to implement a NAT function as the UE used for MTC and servers used for MTC belonging to one application share the same private IP address space.
NOTE: The above mechanism can be applied to other applications using same scenario as described in Figure B.2.3-1.
Annex C (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2011/03 |
SA#51 |
SP-110075 |
0122 |
2 |
F |
Restricting IPv6 interface identifier generation to protect usage patterns |
10.0.0 |
|
2011/12 |
SA#54 |
SP-110737 |
0134 |
2 |
B |
Update of Domain Selection |
10.1.0 |
|
2011/12 |
SA#54 |
SP-110742 |
0132 |
7 |
B |
Normative documentation for SIMTC and IP addressing |
11.0.0 |
|
2011/12 |
SA#54 |
SP-110748 |
0133 |
1 |
C |
Clarification on T-ADS behaviour |
11.0.0 |
|
2012/12 |
SA#58 |
SP-120710 |
0146 |
– |
A |
Restriction of Inter RAT handover/release with redirection to E-UTRAN |
11.1.0 |
|
2012/12 |
SA#58 |
SP-120726 |
0149 |
1 |
F |
Clarification on SDS to ensure that the service can be performed correctly. |
11.1.0 |
|
2013/06 |
SA#60 |
SP-130223 |
0148 |
6 |
F |
Enabling CS services when UE gets IMSI detached |
11.2.0 |
|
2014/06 |
SA#64 |
SP-140251 |
0159 |
3 |
A |
Keeping ongoing IMS voice calls when IMSvoPS indication changes |
11.3.0 |
|
2014/06 |
SA#64 |
SP-140377 |
0157 |
2 |
F |
USSD method selection |
12.0.0 |
|
2014/06 |
SA#64 |
SP-140274 |
0163 |
2 |
B |
Clarification on roaming subscription corresponding to specific RAT for 23.221 |
13.0.0 |
|
2016/09 |
SA#73 |
SP-160642 |
0168 |
7 |
B |
T-ADS factors to support WLAN access |
14.0.0 |
|
2016/12 |
SA#74 |
SP-160826 |
0170 |
3 |
B |
T-ADS consideration for 3GPP Data Off status for MMTel Audio and MMTel Video services during access selection |
14.1.0 |
|
2016/12 |
SA#74 |
SP-160826 |
0172 |
2 |
B |
Mobile originated sessions domain selection and PS Data Off |
14.1.0 |
|
2017/09 |
SA#77 |
SP-170729 |
0174 |
1 |
C |
Update for 3GPP PS DATA OFF Phase 2 |
15.0.0 |
|
2018-12 |
SA#82 |
SP-181080 |
0181 |
– |
A |
Missing Data Off requirement for non-IP PDN connection |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181096 |
0179 |
1 |
F |
Subscription based access restriction for NB-IoT |
16.0.0 |
|
2019-03 |
SA#83 |
SP-190163 |
0182 |
2 |
B |
Introduction of PARLOS |
16.1.0 |
|
2019-06 |
SA#84 |
SP-190406 |
0183 |
– |
C |
Ethernet type PDN connection in EPS and Data Off |
16.2.0 |
|
2022-03 |
SA#95E |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |