School of Specs 24.501v20.0.0

3GPP 24.501 v20.0.0 — the document's own text

9.11.4.29 Remote UE context list

Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).

The purpose of the Remote UE context list information element is to provide identity and optionally IP address of a 5G ProSe remote UE connected to, or disconnected from, a UE acting as a 5G ProSe layer-3 UE-to-network relay.

The Remote UE context list information element is coded as shown in figure 9.11.4.29.1, figure 9.11.4.29.2, table 9.11.4.29.1 and table 9.11.4.29.2.

The Remote UE context list is a type 6 information element with a minimum length of 16 octets and a maximum length of 65538 octets.

87654321
Remote UE context list IEIoctet 1
Length of remote UE context list contentsoctet 2
octet 3
Number of remote UE contextsoctet 4
Remote UE context 1octet 5
octet a
octet a+1*octet b*
Remote UE context koctet b+1*
octet c*

Figure 9.11.4.29.1: Remote UE context list

Table 9.11.4.29.1: Remote UE context list

Remote UE context (octet 5 etc)
The contents of remote UE context are applicable for one individual UE and are coded as shown in figure 9.11.4.29.2 and table 9.11.4.29.2.
87654321
Length of remote UE contextoctet 5
0Spare0Spare0Spare0SpareRemote UE ID formatRemote UE ID typeoctet 6
Length of remote UE IDoctet 7
Remote UE IDoctet 8
Octet j*
SpareUPRI4ITPRI4IProtocol used by remote UEoctet j+1*
Address informationoctet j+2*octet j+k*
HPLMN IDoctet (j+k+1)*octet (j+k+3)*

Figure 9.11.4.29.2: Remote UE context

Table 9.11.4.29.2: Remote UE context

Remote UE ID type (bits 1 to 3 of octet 6)
Bits
321
001UP-PRUK ID
010CP-PRUK ID
011IMEI
100IMEISV
All other values are reserved.
Remote UE ID format (bit 4 of octet 6) (NOTE)
Bit
4
0Network access identifier (NAI)
164-bit string
Bits 5 to 8 of octet 6 are spare and shall be coded as zero.
Remote UE ID (octet 8 to octet j)
The UP-PRUK ID as specified in 3GPP TS 33.503 [56], the CP-PRUK ID as specified in 3GPP TS 33.503 [56], the IMEI or the IMEISV of the 5G ProSe Remote UE. If the remote UE ID type field indicates "UP-PRUK ID" or "CP-PRUK ID", and the remote UE ID format field indicates "NAI", the remote UE ID field contains the UP-PRUK ID or the CP-PRUK ID in the NAI format as defined in 3GPP TS 23.003 [4], encoded as UTF-8 string. If the remote UE ID type field indicates "UP-PRUK ID", and the remote UE ID format field indicates "64-bit string", the remote UE ID field contains the UP-PRUK ID as a 64-bit string, encoded using binary encoding. If the remote UE ID type field indicates "IMEI" or "IMEISV", the remote UE ID field contains the IMEI or the IMEISV encoded as 5GS mobile identity information element for type of identity "IMEI" or "IMEISV" as specified in clause 9.11.3.4, starting with the fourth octet.
Protocol used by remote UE (octet j+1, bits 1 to 3)Bits
321
000No IP info
001IPv4
010IPv6
100Unstructured
101Ethernet
All other values are reserved.
TCP port range for IPv4 indicator (TPRI4I) (octet j+1, bits 4)
Bit
4
0TCP port range for IPv4 absent
1TCP port range for IPv4 present
UDP port range for IPv4 indicator (UPRI4I) (octet j+1, bits 5)
Bit
5
0UDP port range for IPv4 absent
1UDP port range for IPv4 present
Bits 4 to 8 of octet j+1 are spare and shall be coded as zero.
The length of remote UE ID field contains the binary coded representation of the length of the remote UE ID field. The first bit in transmission order is the most significant bit.
If the Protocol used by remote UE indicates IPv4 and:- TPRI4I bit indicates "TCP port range for IPv4 absent" and UPRI4I bit indicates "UDP port range for IPv4 absent", the Address information in octet j+2 to octet j+5 contains the IPv4 address.- TPRI4I bit indicates "TCP port range for IPv4 present" and UPRI4I bit indicates "UDP port range for IPv4 absent", the Address information in octet j+2 to octet j+9 contains the IPv4 address followed by the TCP port range field.- TPRI4I bit indicates "TCP port range for IPv4 absent" and UPRI4I bit indicates "UDP port range for IPv4 present", the Address information in octet j+2 to octet j+9 contains the IPv4 address followed by the UDP port range field.- TPRI4I bit indicates "TCP port range for IPv4 present" and UPRI4I bit indicates "UDP port range for IPv4 present", the Address information in octet j+2 to octet j+13 contains the IPv4 address followed by the UDP port range field followed by the TCP port range field.See NOTE.The UDP port range field consists of the lowest UDP port number field followed by the highest UDP port number field, of the UDP port range assigned to the remote UE in the NAT function of 5G ProSe layer-3 UE-to-network relay. The TCP port range field consists of the lowest TCP port number field followed by highest TCP port number field, of the TCP port range assigned to the remote UE in the NAT function of 5G ProSe layer-3 UE-to-network relay.Each port number field is two octets long and bit 8 of first octet of the port number field represents the most significant bit of the port number and bit 1 of second octet of the port number field the least significant bit.If the Protocol used by remote UE indicates IPv6, the Address information in octet j+2 to octet j+9 contains the /64 IPv6 prefix of a remote UE. Bit 8 of octet j+2 represents the most significant bit of the /64 IPv6 prefix and bit 1 of octet j+9 the least significant bit.If the Protocol used by remote UE indicates Ethernet, the Address information in octet j+2 to octet j+7 contains the remote UE MAC address. Bit 8 of octet j+2 represents the most significant bit of the MAC address and bit 1 of octet j+7 the least significant bit.If the Protocol used by remote UE indicates Unstructured, the Address information octets are not included.If the Protocol used by remote UE indicates No IP info, the Address information octets are not included
If the Remote UE ID type field indicates "PRUK ID" and the Remote UE ID format field indicates "64-bit string", then the HPLMN ID field is present otherwise the HPLMN ID field is absent. The HPLMN ID field indicates HPLMN ID of the 5G ProSe remote UE and is coded as value part of the PLMN ID information element as specified in 3GPP TS 24.554 [19E] clause 11.3.33 starting with the second octet.
NOTE: In the present release of the specification, providing information for IP protocols other than UDP or TCP is not specified