3GPP2 SX r0 TSG-SX WG3 - PDS Title: Overview of the 3GPP TFT change and Possible Solutions Source: TSG-SX WG3 Chair and Vice Chair Abstract: This contribution provides an overview of the 3GPP TFT change and possible solutions in 3GPP2. Recommendation: For discussion and decision. © GPP2 The contributors grant a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. The contributors are also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner's standard which incorporates this contribution. This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. The contributors specifically reserve the right to amend or modify the material contained herein and to any intellectual property of the contributors other than provided in the copyright statement above.

2 1.Overview of 3GPP TFT Changes 2.Solution 1 (SX ) 3.Solution 2 (SX ) 4.Solution 3 5.Solution 4 6.Evaluation of Solutions 7.Annex – Text from C.S0063 Outline

3 3GPP has specified that when TFTs are supplied for the default bearer, an uplink packet must match one of those TFTs or be dropped by the UE. ISSUE: 3GPP2 specifies that when a packet does not match a TFT, it is sent on the best effort bearer, not dropped. How should 3GPP2 align its specifications to provide the same results as are currently found in 3GPP? Overview of 3GPP TFT Changes

4 Solution 1 is defined in SX Solution 1 would require a change so that when packet TFTs are specified for the default bearer and a packet does not match any of these TFTs, the UE would drop the packet. The UE would NOT send the packet on the best effort bearer. Solution 1 is fully aligned with the 3GPP solution. Solution 1 (SX )

5 Solution 1 - example TFT: IP address xxx TFT: IP address yyy UL Packet: IP address xxx UL Packet: IP address zzz Sent on the uplink Dropped in the UE

6 Solution 2 is defined in SX Solution 2 would require creation of a new type of TFT. Current TFTs provide a destination IP address and port number. When the destination address of a packet matches the TFT, the packet is sent. (PDS has called this a “positive TFT”) The new type of TFT proposed in the contribution would create what PDS has called a “negative TFT”. A packet that matched the destination IP address and port number of the TFT would be dropped, not sent. Solution 2 (SX )

7 Solution 2 - example TFT: IP address xxx Negative TFT: IP address zzz UL Packet: IP address xxx UL Packet: IP address zzz Sent on the specified bearer Dropped in the UE UL Packet: IP address yyy Sent on the best effort bearer

8 Solution 3 would use existing 3GPP2 specifications and depend on the HSGW to drop uplink packets that should not be sent. The HSGW already has the packet filter policy from the PCRF and can drop any uplink packets according to that policy. Solution 3

9 Solution 4 would use existing 3GPP specifications and depend on the P-GW to drop uplink packets that should not be sent. The P-GW already has the packet filter policy from the PCRF and can drop any uplink packets according to that policy. Solution 4

10 Solution 1 ­Would require changes (to C.S0063? See Annex) to prevent the UE from sending packets that do not match a TFT, instead of sending those packets on the best effort bearer. ­Legacy devices would continue to send packets that would have to be dropped by the HSGW per PCRF policy. Solution 2 ­Would create a new type of TFT that devices would need to implement. The new TFT type would indicate destination IP addresses that should not be sent. ­Legacy devices would continue to send packets that would have to be dropped by the HSGW or P-GW per PCRF policy. Solution 3 ­All devices would continue to send packets that would have to be dropped by the HSGW per PCRF policy. ­Waste air interface and backhaul resources from RAN to HSGW unnecessarily Solution 4 ­All devices would continue to send packets that would have to be dropped by the P-GW per PCRF policy. ­Waste air interface and backhaul resources from RAN to P-GW unnecessarily Solutions 1 to 3: ­Would require changes to the HSGW to drop uplink packets per PCRF policy. Solution 4: ­The P-GW must drop uplink packets per PCRF policy. Evaluation of the Solutions

11 The transmitter should transmit higher layer octets belonging to a higher layer flow that is not associated with any Link Flow using the Link Flow with ReservationLabel 0xff if the higher layer flow provides an octet stream with octet-based HDLC-like framing to the Enhanced Multi-flow Packet Application. The transmitter may transmit higher layer octets belonging to a higher layer flow identified by a Reservation that is in the Close state using the Link Flow with ReservationLabel 0xff if the higher layer flow provides an octet stream with octet-based HDLC-like framing to the Enhanced Multi- flow Packet Application. The transmitter may transmit higher layer octets belonging to a higher layer flow identified by a Reservation that is bound to a de-activated Link Flow using the Link Flow with ReservationLabel 0xff if the higher layer flow provides an octet stream with octet-based HDLC-like framing to the Enhanced Multi-flow Packet Application. Annex: C.S 0063-B (1)

12 The transmitter should transmit higher layer packets belonging to a higher layer flow that is not associated with any Link Flow using the Link Flow with ReservationLabel 0xfe if the higher layer flow provides an IP packet stream to the Enhanced Multi-flow Packet Application. The transmitter may transmit higher layer packets belonging to a higher layer flow identified by a Reservation that is in the Close state using the Link Flow with ReservationLabel 0xfe if the higher layer flow provides an IP packet stream to the Enhanced Multi-flow Packet Application. The transmitter may transmit higher layer packets belonging to a higher layer flow identified by a Reservation that is bound to a de-activated Link Flow using the Link Flow with ReservationLabel 0xfe if the higher layer flow provides an IP packet stream to the Enhanced Multi-flow Packet Application Annex: C.S 0063-B (2)