7/30/2019 Sf 171 90r1 Qc Vsnp Selectedbcm With Mupsap

1/4

Title: X.P0057-A R&F: VSNP & Selected BCM with MUPSAP.

Abstract: X.P0057-A R&F: VSNP & Selected BCM with MUPSAP. Addressescomments 171 & 90

Source: QUALCOMM

George Cherian/Jun Wang {gcherian, jwang}@qualcomm.com

Date: Dec 15, 2010

Recommendation: Review and adopt it.

Notice

QUALCOMM Incorporated grants a free, irrevocable license to 3GPP2 and its Organization 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 Partners name any Organizational Partners standards publication

even though it may include portions of the contribution; and at the Organization Partners sole discretion to permit othersto reproduce in whole or in part such contributions or the resulting Organizational Partners standards publication.

QUALCOMM Incorporated is 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 Partners standard which

incorporates this contribution.

This document has been prepared by QUALCOMM Incorporated to assist the development of specifications by 3GPP2. Itis proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributor.

QUALCOMM Incorporated specifically reserves the right to amend or modify the material contained herein and nothing

herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the

contributor other than provided in the copyright statement above.

7/30/2019 Sf 171 90r1 Qc Vsnp Selectedbcm With Mupsap

2/4

5.9 MUPSAP Support for eHRPD

MUPSAP (Multiple PDN Connections to A Single APN) allows the UE to setup more than one

PDN connections with an APN. Each PDN connection is uniquely identified using PDN Identifier

+ User Context Identifier. This section defines the additional requirements for UE and HSGW to

support MUPSAP over eHRPD.

7/30/2019 Sf 171 90r1 Qc Vsnp Selectedbcm With Mupsap

3/4

5.9.1 PDN Connection Setup and Teardown Procedure

If the UE wants to setup multiple PDN connections to an APN (MUPSAP), then the UE shall

include the User Context Identifier configuration option in the VSNCP Configure Request

message for the first PDN connection for that APN. If the HSGW indicates that multiple

connections to that APN is not supported, then the UE shall not attempt to setup additional PDN

connections to that APN. If multiple connections to the same APN is supported, then for each ofthe PDN connections to that APN, the UE shall choose a unique value for the User Context

Identifier.

If the UE has included User Context Identifier configuration option in the VSNCP Configure

Request message, and if the HSGW supports MUPSAP, then the HSGW includes PDN

Connection Information Element in the Proxy Binding Update message as specified in TS 29.275

Error: Reference source not found. The HSGW chooses a unique PDN Connection Identifier value

for each of the User Context Identifier received from the UE. If the MUPSAP function is

supported by the P-GW, then the received PDN Connection ID information element is included inthe Proxy Binding Acknowledge message sent by the P-GW. Upon receiving PDN Connection ID

in the Proxy Binding Acknowledge message from the P-GW, the HSGW includes the User

Context Identifier configuration option in the VSNCP Configure Ack message with the value set

to the same value of VSNCP Configure-Request message sent from the UE. When the HSGW

sends VSNCP Configure-Request message to the UE, it shall include the User Context Identifier

configuration option with the value set to the same value of VSNCP Configure-Request sent from

the UE.

If the HSGW included the Address Allocation Cause configuration option in the VSNCP

Configuration Ack message sent to the UE with the cause code set to New PDN type due to

network preference, then the UE may request a new PDN connection by sending a VSNCP

Configure Request message to the HSGW with the User Context Identifier configuration option

set to a value that is not already in use, and with the PDN Type configuration option set asfollows:

- If the PDN Type configuration option of VSNCP Configuration Ack message received from

the HSGW is set to IPv4, then the UE should set the PDN Type configuration option of the

new VSNCP Configuration Request message to IPv6

- If the PDN Type configuration option of VSNCP Configuration Ack message received from

the HSGW is set to IPv6, then the UE should set the PDN Type configuration option of the

new VSNCP Configuration Request message to IPv4

If the HSGW included the APN-AMBR configuration option in the VSNCP Configure Requestmessage for more than one PDN connection connecting to same APN, then the UE shall use the

latest value of the APN-AMBR configuration option for that APN.

If the HSGW does not support MUPSAP, it shall not include the PDN Connection ID information

element in the Proxy Binding Update message it sends to the P-GW. If the HSGW does notreceive a PDN connection ID value in the Proxy Binding Acknowledge message sent by the P-

GW, it shall not include the User Context Identifier configuration option in the VSNCPConfigure-Ack message sent to the UE.

The UE or HSGW may initiate termination of a PDN connection. To terminate a MUPSAP PDNconnection, the UE or HSGW includes the PDN Identifier and the User Context Identifier in the

VSNCP Terminate Request message. If the VSNCP Terminate Request message does not include

a User Context Identifier configuration option, it implies all PDN connections to the APN shall be

removed.

7/30/2019 Sf 171 90r1 Qc Vsnp Selectedbcm With Mupsap

4/4

When multiple PDN connections to an APN is setup, and if the VSNP Extend Code is negotiated

for the first PDN connection to that APN, then all the subsequent PDN connections to that APN

shall use the same VSNP Extend Code until all the PDN connections to that APN is torn down. If

the VSNP Extend Code is not negotiated for the first PDN connection to that APN, then none of

the subsequent PDN connections to that APN shall negotiate the VSNP Extend Code until all thePDN connections to that APN isare torn down

5.9.2 Quality of Service

QoS setup procedure is performed for each of the MUPSAP PDN connections using the

procedures specified in section Error: Reference source not found of this specification.

The service connection, (i.e., each concatenation of an RLP flow with an A8+A10 connection,

between the UE and the HSGW) established for an APN may be shared by all the MUPSAP PDN

connections for that APN.

It is expected thatNote: Whetherthe PCRF will select the same Selected Bearer Control Mode for

all PDN connections to the same APN is FFS.