For this case, RSVP is added to the GPRS bearer establishment procedures specified in TS 23.060, with no Service-based local policy.
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
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.
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.
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.
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.
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 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.
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.
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
For this case, Service-based Local Policy and RSVP are added to the GPRS bearer establishment procedures specified in TS 23.060.
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.
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
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.
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.
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.
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