Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  19.2.0

Top   Top   Up   Prev   None
1…   4…   5…   5A…   6…   6.1.3   6.1.4…   6.1.4.4…   6.1.5…   6.1A…   6.1B…   6.1B.2.3…   6.1C   6.2…   6.2.3…   6.2.6…   6.2.6.2   6.2.6.3…   6.2.6.3.3   6.2.6.3.4   6.2.6.3.5   6.2.6.3.6…   6.2.7…   6.2.8…   6.2.9…   6.2.13…   6.2A…   6.2B…   6.2B.3   6.2B.4…   6.2C…   6.2D…   6.2E…   6.2F…   6.2H…   6.2H.2.2…   6.2H.2.3…   6.2H.2.4…   6.3…   6.4…   6.5…   6.6…   6.7…   6.7.3…   6.7.4…   6.7.5…   6.8…   6.9…   6.10…   6.11…   6.12…   6.13…   6.14…   6.16…   6.17…   6.18…   6.19…   6.20…   6.21…   6.22…   6.23…   7…   7.4…   7.7…   7.9…   8…   9…   10…   11…   12…   A…

 

A  Methods to handle NAT on IPv4 between UE and AF |R18|p. 377

A.1  Methods to handle NAT on IPv4 between UE and AFp. 377

The following methods can be used to handle the case when there is a NAT between the UE and AF for data collection:
  1. Use IPv6 instead of IPv4 and then use any of the procedures in clauses 6.2.8.2.4.2 to 6.2.8.2.4.4.
  2. Provide GPSI via header enrichment as described in TS 29.244.
  3. Have GPSI as part of the authentication information, or via in-band signalling.
  4. At the establishment of the user plane connection between the UE Application and AF, the AF can use the procedure in clause 4.15.10 of TS 23.502 to get the GPSI.
  5. At the establishment of the user plane connection between the UE Application and a trusted AF, the AF can use the steps 3 to 8 in clause 4.15.10 of TS 23.502, where NEF is replaced by the AF, to retrieve the SUPI of the UE.
In methods 2) to 4), the AF can correlate the UE public IP address and port with the SUPI/GPSI.
Up

$  Change historyp. 378


Up   Top