Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 33.128  Word version:  18.7.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.7…   6…   6.2.2.2A…   6.2.3…   6.2.3.2.7…   6.2.3.3…   6.2.4…   6.3…   6.3.2.2A…   6.3.3…   6.3.3.2…   6.3.3.2.4…   6.3.3.2A…   7…   7.3…   7.3.3…   7.3.3.2.21…   7.3.3.2.42…   7.3.3.2.63…   7.3.4…   7.4…   7.4.3.8…   7.5…   7.6…   7.7…   7.7.4…   7.8…   7.8.4…   7.9…   7.10…   7.10.4…   7.11…   7.12…   7.13…   7.13.3…   7.13.3.4…   7.14…   7.15…   8…   A…   D…   E…   M…

 

6.3.3.2A  Triggering of the CC-POI from CC-TF over LI_T3p. 157

When CUPS architecture is used and the interception of user plane packets is required, the CC-TF present in the SGW-C/PGW-C sends a trigger to the CC-POI present in the SGW-U/PGW-U over the LI_T3 interface.

6.3.3.3  Generation of xCC at CC-POI in the SGW/PGW and ePDG over LI_X3p. 158

6.3.3.3.1  Non-CUPS architecturep. 158
The CC-POI present in the SGW/PGW and ePDG shall send xCC over LI_X3 for each IP packet belonging to the target's communication.
Each X3 PDU shall contain the contents of the user plane packet given using the GTP-U, IP or Ethernet payload format.
The CC-POI present in the SGW/PGW and ePDG shall set the payload format to indicate the appropriate payload type (5 for IPv4 Packet, 6 for IPv6 Packet, 7 for Ethernet frame or 12 for GTP-U packet as per ETSI TS 103 221-2 [8] clause 5.4).
If it is required to send the ICE-type for the xCC, the CC-POI shall set the NFID attribute (see ETSI TS 103 221-2 [8] clause 5.3.7) to the appropriate value from the ICE-type enumeration in TS 33.108 Annex B.10 as a single octet. As an example, an ICE-type of "sgw" is indicated by setting the attribute to value 3.
Up
6.3.3.3.2  CUPS architecturep. 158
When CUPS architecture is used, the CC-POI in the SGW-U/PGW-U is provisioned by the CC-TF in the SGW-C/PGW-C using a Triggering message (i.e. ActivateTask message) as described in clause 6.3.3.0.
The CC-POI present in the SGW-U/PGW-U shall send xCC over LI_X3 for each IP packet matching the criteria specified in the Triggering message (i.e. ActivateTask message) received over LI_T3 from the CC-TF in the SGW-C/PGW-C.
Each X3 PDU shall contain the contents of the user plane packet given using the GTP-U, IP or Ethernet payload format.
The CC-POI present in the SGW-U/PGW-U shall set the payload format to indicate the appropriate payload type (5 for IPv4 Packet, 6 for IPv6 Packet, 7 for Ethernet frame or 12 for GTP-U Packet as described in ETSI TS 103 221-2 [8] clauses 5.4 and 5.4.13.
If handover of the entire GTP-U packet is required over LI_HI3 (see clause 6.2.3.8), then consideration shall be made of the correct choice of LI_X3 payload type to ensure that the MDF3 has the necessary CC information. Support for delivery of LI_X3 as payload type 12 (GTP-U packet) is mandatory.
Up

6.3.3.4  Generation of IRI over LI_HI2p. 158

When an xIRI is received over LI_X2 from the IRI-POI in the SGW/PGW or ePDG, the MDF2 shall generate the corresponding IRI message and deliver it over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received in the xIRI over LI_X2.
When option 2 specified in clause 6.3.1 is used, the MDF2 shall generate IRI messages based on the proprietary information received from the SGW/PGW or ePDG and provide it over LI_HI2 without undue delay.
The IRI messages shall include an IRI payload encoded according to clause 10.5 and TS 33.108 Annex B.9. The MDF2 shall encode the correct value of LIID in the IRI message, replacing the value "LIIDNotPresent" given in the xIRI (see clause 6.3.2.2).
The IRI messages shall be delivered over LI_HI2 according to ETSI TS 102 232-7 [10] clause 10.
Up

6.3.3.5  Generation of CC over LI_HI3p. 158

When xCC is received over LI_X3 from the CC-POI in the SGW/PGW or ePDG, the MDF3 shall generate the corresponding CC and deliver it over LI_HI3 without undue delay. The CC message shall contain a copy of the relevant xCC received over LI_X3.
When option 2 specified in clause 6.3.1 is used, the MDF3 shall generate CC based on the proprietary information received from the SGW/PGW or ePDG and provide it over LI_HI3 without undue delay.
The CC shall include a CC payload encoded according to TS 33.108 Annex B.10.
The CC shall be delivered over LI_HI3 according to ETSI TS 102 232-7 [10] clause 10.
Up

6.4  3Gp. 159

The Present document does not specify details of the LI interfaces for 3G / UMTS. Details for this release are specified in TS 33.108.

Up   Top   ToC