Content for TS 23.207 Word version: 16.0.0

1… 5… 6… A… C D…

D.1 Resource reservation with end-to-end RSVP D.2 Resource Reservation with End-to-End RSVP and Service-based Local Policy

D Resource reservation and end-to-end RSVP Word‑p. 32

D.1 Resource reservation with end-to-end RSVP

For this case, RSVP is added to the GPRS bearer establishment procedures specified in TS 23.060, with no Service-based local policy.

NOTE:
The diagrams in this clause depict one possible signalling sequence, however, the alternative signalling sequences below are possible:

to trigger the Create PDP Context Request message after the PATH message.

to trigger the Create PDP Context Request message after the RESV message.

to trigger only one PDP context after all RSVP exchanges have completed.

NOTE:
The diagrams in this clause depict the case when the GGSN is not RSVP aware, however, the alternative of GGSN being RSVP aware is also possible.

The following figure is applicable to the Mobile Originating (MO) side.

(not reproduced yet)

Figure D.1: MO Resource Reservation with End-to-End RSVP

NOTE:
There is no timing relationship between the set of flows for the uplink (above the line) and the downlink (below the line).

Step 1.
The UE sends an Activate (Secondary) PDP Context message to the SGSN with the UMTS QoS parameters.

Step 2.
The SGSN sends the corresponding Create PDP Context message to the GGSN.

Step 3.
The GGSN authorizes the PDP context activation request according to the local operator's IP bearer resource based policy, the local operator's admission control function and the GPRS roaming agreements and sends a Create PDP Context Response message back to the SGSN.

Step 4.
RAB setup is done by the RAB Assignment procedure.

Step 5.
The SGSN sends an Activate (Secondary) PDP Context Accept message to UE.

Step 6.
UE sends an RSVP PATH message to the next hop, through the GGSN. The GGSN does not process the RSVP PATH message. Alternatively, the GGSN may process the RSVP PATH message and forward it to the next hop.

Step 7.
The UE receives the RSVP RESV message in the downlink direction, through the GGSN. The GGSN does not process the RSVP RESV message. Alternatively, the GGSN may process the RSVP RESV message and forward it to the UE.

Step 8.
The UE sends a RSVP RESV-CONF message to the next hop. The use of the RESV-CONF message is optional.

Step 9.
The UE receives a RSVP PATH message in the downlink direction, through the GGSN. The GGSN does not process the RSVP PATH message. Alternatively, the GGSN may process the incoming RSVP PATH message and forward it to the UE.

Step 10.
The UE may send a Modify PDP Context message to the SGSN with the necessary modification to UMTS QoS parameters according to the received RSVP PATH message.

Step 11.
The SGSN sends the corresponding Update PDP Context Request message to the GGSN.

Step 12.
The GGSN authorizes the PDP context modification according to the local operator's IP bearer resource based policy, the local operator's admission control function and the GPRS roaming agreements and sends an Update PDP Context Response message back to the SGSN.

Step 13.
The radio access bearer modification may be performed by the RAB Assignment procedure.

Step 14.
The SGSN sends a Modify PDP Context Accept message to UE.

Step 15.
UE sends the RSVP RESV message to the next hop, through the GGSN. The GGSN does not process the RSVP RESV message. Alternatively, the GGSN may process the RSVP RESV message and forward it to the next hop.

Step 16.
The UE receives the RSVP RESV-CONF message in the downlink direction. The use of the RESV-CONF message is optional.

The following figure is applicable to the Mobile Terminating (MT) side. As the flow is the mirror of the Mobile Originating (MO) side, the step-by-step description is omitted.

(not reproduced yet)

Figure D.2: MT Resource Reservation with End-to-End RSVP

NOTE:
There is no timing relationship between the set of flows for the uplink (above the line) and the downlink (below the line).

D.2 Resource Reservation with End-to-End RSVP and Service-based Local Policy Word‑p. 35

For this case, Service-based Local Policy and RSVP are added to the GPRS bearer establishment procedures specified in TS 23.060.

NOTE:
The diagrams in this clause depict one possible signalling sequence, however, the alternative signalling sequences below are possible:

to trigger the Create PDP Context Request message after the PATH message.

to trigger the Create PDP Context Request message after the RESV message.

to trigger only one PDP context after all RSVP exchanges have completed.

NOTE:
The diagrams in this clause depict the case when the GGSN is RSVP aware, however, the alternative of GGSN not being RSVP aware is also possible.

This clause provides the flows for bearer establishment, resource reservation and policy control with RSVP.
The following figure is applicable to the Mobile Originating (MO) side.

(not reproduced yet)

Figure D.3: MO Resource Reservation with End-to-End RSVP and Service-based Local Policy

NOTE:
There is no timing relationship between the set of flows for the uplink (above the line) and the downlink (below the line).

Step 1.
The UE sends an Activate (Secondary) PDP Context message to the SGSN with the UMTS QoS parameters. The UE includes the Binding Information in the Activate PDP Context message.

Step 2.
The SGSN sends the corresponding Create PDP Context message to the GGSN.

Step 3.
The GGSN sends a COPS REQ message with the Binding Information to the PDF in order to obtain relevant policy information.

Step 4.
The PDF sends a COPS DEC message back to the GGSN.

Step 5.
The GGSN sends a COPS RPT message back to the PDF.

Step 6.
The GGSN maps IP flow based policy information into PDP context based policy information and uses the PDP context based policy information to accept the PDP activation request, and sends a Create PDP Context Response message back to SGSN. The GGSN may cache the policy information.

Step 7.
RAB setup is done by the RAB Assignment procedure.

Step 8.
The SGSN sends an Activate (Secondary) PDP Context Accept message to UE.

Step 9.
UE sends a RSVP PATH message to GGSN. The UE includes the Binding Information.

NOTE:
If the decision was previously cached locally at the GGSN, it may not be necessary to query the PDF again. Otherwise the GGSN may have to query the PDF.

Step 10.
The GGSN uses the policy information to accept the RSVP PATH message, and forwards the RSVP PATH message to the next hop.

Step 11.
The GGSN receives the RSVP RESV message in the downlink direction.

NOTE:
If the decision was previously cached locally at the GGSN, it may not be necessary to query the PDF again. Otherwise the GGSN may have to query the PDF.

Step 12.
The GGSN uses the policy information to accept the RSVP RESV message, and forwards the RSVP RESV message to the UE.

Step 13.
The UE sends a RSVP RESV-CONF message to the next hop. The use of the RESV-CONF message is optional.

Step 14.
The GGSN receives a RSVP PATH message in the downlink direction.

Step 15.
The GGSN forwards the RSVP PATH message to the UE.

Step 16.
The UE may send a Modify PDP Context message to the SGSN with the necessary modification to UMTS QoS parameters according to the received RSVP PATH message. The UE includes the Binding Information in the Modify PDP Context message.

Step 17.
The SGSN sends the corresponding Update PDP Context message to the GGSN.

NOTE:
If the decision was previously cached locally at the GGSN, it may not be necessary to query the PDF again. Otherwise the GGSN may have to query the PDF.

Step 18.
The GGSN uses the policy information to accept the PDP modification request, and sends a Update PDP Context Response message back to SGSN.

Step 19.
The radio access bearer modification may be performed by the RAB Assignment procedure.

Step 20.
The SGSN sends a Modify PDP Context Accept message to UE.

NOTE:
Steps 16 to 20 are optional if the existing PDP context already satisfies the QoS requirements.

Step 21.
The UE sends a RSVP RESV message to the GGSN. The UE includes the Binding Information in the RSVP RESV message.

NOTE:
If the decision was previously cached locally at the GGSN, it may not be necessary to query the PDF again. Otherwise the GGSN may have to query the PDF.

Step 22.
The GGSN uses the policy information to accept the RSVP RESV message, and forwards the RSVP RESV message to the next hop.

Step 23.
The UE receives the RSVP RESV-CONF message in the downlink direction. The use of the RESV-CONF message is optional.

The following figure is applicable to the Mobile Terminating (MT) side. As the flow is the mirror of the Mobile Originating (MO) side, the step-by-step description is omitted.

(not reproduced yet)

Figure D.4: MT Resource Reservation with End-to-End RSVP and Service-based Local Policy

NOTE:
There is no timing relationship between the set of flows for the uplink (above the line) and the downlink (below the line).

$ Change history Word‑p. 39