8.2.24 Destination Interface
29.2443GPPInterface between the Control Plane and the User Plane nodesRelease 17TS
The Destination Interface IE type shall be encoded as shown in Figure 8.2.24-1. It indicates the type of the interface towards which an outgoing packet is sent.
|
Bits |
||||||||||
|
Octets |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
1 to 2 |
Type = 42 (decimal) |
|||||||||
|
3 to 4 |
Length = n |
|||||||||
|
5 |
Spare |
Interface value |
||||||||
|
6 to (n+4) |
These octet(s) is/are present only if explicitly specified |
|||||||||
Figure 8.2.24-1: Destination Interface
The Interface value shall be encoded as a 4 bits binary integer as specified in Table 8.2.24-1.
Table 8.2.24-1: Interface value
|
Interface value |
Values (Decimal) |
|
Access (NOTE 1, NOTE 3, NOTE 4) |
0 |
|
Core (see NOTE 1) |
1 |
|
SGi-LAN/N6-LAN |
2 |
|
CP- Function |
3 |
|
LI Function (see NOTE 2) |
4 |
|
5G VN Internal |
5 |
|
Spare |
6 to 15 |
|
NOTE 1: The "Access" and "Core" values denote a downlink and uplink traffic direction respectively. NOTE 2: LI Function may denote an SX3LIF or an LMISF. See clause 5.7. NOTE 3: For indirect data forwarding, the Source Interface in the PDR and the Destination Interface in the FAR shall both be set to "Access", in the forwarding SGW(s). The Interface value does not infer any traffic direction, in PDRs and FARs set up for indirect data forwarding, i.e. with both the Source and Destination Interfaces set to Access. NOTE 4: For a HTTP redirection, the Source Interface in the PDR to match the uplink packets to be redirected and the Destination Interface in the FAR to enable the HTTP redirection shall both be set to "Access". |
|