Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.401  Word version:  16.7.0

Top   Top   Up   Prev   Next
1…   4…   4.2.2…   4.3…   4.3.6…   4.3.8…   4.3.12…   4.3.16…   4.3.20…   4.3.25…   4.4…   4.6…   4.7…   5…   5.1.2…   5.3…   5.3.2   5.3.3…   5.3.3.2   5.3.3.3…   5.3.4…   5.3.4B   5.3.5…   5.3.8   5.3.9…   5.4…   5.4.4…   5.5…   5.5.1.2   5.5.2…   5.5.2.2   5.5.2.3   5.5.2.4…   5.6…   5.7.3…   5.7A…   5.10   5.11…   5.19…   D…   D.3…   D.3.4   D.3.5   D.3.6   D.3.7   D.3.8   E   F…   J…   K…   L…   M…

 

F (Normative)  Dedicated bearer activation in combination with the default bearer activation at Attach and UE requested PDN connectivity proceduresWord‑p. 409
Dedicated bearer activation in combination with the default bearer activation at Attach and UE requested PDN connectivity procedures
For WB-E-UTRAN, it shall be possible for the PDN GW to initiate the activation of dedicated bearers (as specified in clause 5.4.1) as part of the attach procedure (as specified in clause 5.3.2.1) or as part of the UE requested PDN connectivity procedure (as specified in clause 5.10.2) over WB-E-UTRAN. However, the result of the dedicated bearer activation procedure shall be logically separate from the Attach procedure, meaning that the result of the Attach procedure is not dependent on whether the Dedicated bearer activation procedure succeeds or not. On the other hand, the dedicated bearer activation may only be regarded as successful if the Attach procedure completes successfully.
The messages of the Dedicated bearer activation can be sent together with the messages of the Attach procedure or of the UE requested PDN connectivity procedure (i.e. Attach accept or PDN Connectivity Accept), as shown in the Figure and explanation below.
On the S1 and Uu interfaces the messages for the default bearer activation at Attach and UE requested PDN connectivity procedures and for the Dedicated Bearer Activation procedure are combined into a single message. If the MME has sent an Attach Accept message towards the eNodeB, and then the MME receives a Create Bearer Request before the MME receives the Attach Complete message, the MME shall wait for the Attach procedure to complete before the MME continues with Dedicated Bearer Activation procedure.
It shall be possible that multiple dedicated bearers can simultaneously be activated in the signalling flow shown below.
Reproduction of 3GPP TS 23.401, Figure F.1: Dedicated bearer activation in combination with the default bearer activation at attach or UE requested PDN connectivity
Up
Figure F.1 describes the activation of dedicated bearer(s) in combination with the default bearer activation either as part of the Attach procedure (with specific steps 1a, 7a, 10a) or as part of the UE requested PDN connectivity procedure (with specific steps 1b, 7b, 10b). The following steps below require special attention:
Step 5.
(On the P-GW-S-GW interface) Create Session Response message of the Attach procedure or UE-requested PDN connectivity procedure is combined with Create Bearer Request message of the Dedicated Bearer Activation Procedure
Step 6.
(On the S-GW-MME interface) Create Session Response message of the Attach procedure or UE-requested PDN connectivity procedure is combined with the Create Bearer Request message of the Dedicated Bearer Activation Procedure
Step 7a.
For Attach procedure: If the MME receives a Create Session Response message combined with a Create Bearer Request message, the MME shall send the S1-AP Initial Context Setup Request message to the eNodeB, including the NAS parts for both the Attach Accept message of the Attach procedure and the Bearer Setup Request of the Dedicated Bearer Activation Procedure.
Step 7b.
For UE requested PDN connectivity procedure: If the MME receives a Create Session Response message combined with a Create Bearer Request message, the MME shall send the S1-AP Bearer Setup Request message to the eNodeB, including the NAS parts for both the PDN Connectivity Accept message and the Bearer Setup Request of the Dedicated Bearer Activation Procedure.
Step 8-9.
The radio bearer establishment of the default and dedicated bearer(s) is performed in the same RRC message.
Step 10a.
For Attach procedure: The eNodeB sends the S1-AP Initial Context Setup Response message to the MME.
The MME shall be prepared to receive this message either before or after, some or all, of the Uplink NAS Uplink Transport messages sent in step 12.
Step 10b.
For UE requested PDN connectivity procedure: The eNodeB sends the S1-AP Bearer Setup Response message to the MME.
The MME shall be prepared to receive this message either before or after, some or all, of the Uplink NAS Uplink Transport messages sent in step 12.
Step 11.
For the Attach procedure: The UE sends the eNodeB a Direct Transfer message containing the Attach Complete (Session Management Response for the Default Bearer) message as response of the attach procedure, and Direct Transfer messages containing the Session Management Responses of the dedicated bearer setup procedure.
For the UE requested PDN connectivity procedure: The UE NAS layer builds a PDN Connectivity Complete (Session Management Response) for the Default Bearer Activation and Dedicated Bearer Activation Procedures. The UE then sends Direct Transfer (PDN Connectivity Complete) message to the eNodeB.
The NAS messages to establish the EPS bearers shall be handled individually by the UE and be sent in separate RRC Direct Transfer messages.
Step 12.
The eNodeB sends an Uplink NAS Transport message to the MME, which contains the NAS messages from the RRC message in step 11. There may be multiple Uplink NAS Transport messages when the UE sends multiple RRC messages containing NAS messages in step 11.
Step 13.
Upon reception of the response messages in both step 10 and step 12, the Modify Bearer Request message of the Attach procedure or UE requested PDN connectivity procedure is combined with the Create Bearer Response message of the Dedicated Bearer Activation Procedure. After that, the Serving GW continues with sending a Create Bearer Response message to the PDN GW.
Up

GVoid

H (Normative)  Mapping between temporary and area identitiesWord‑p. 413
The mapping between temporary and area identities is defined in TS 23.003.

I  Guidance for contributors to this specificationWord‑p. 414
Guidance for contributors to this specification
The following guidance is provided for drafting figures for this specification that contain specific steps which are different in TS 23.402 due to the PMIP-based S5/S8 interface:
  • Message flows to this specification will contain the complete procedures applicable for GTP-based S5/S8 only.
  • In this specification, clause(s) of a message flow that is different for PMIP-based S5/S8 interface are shown surrounded by shaded box indexed by an upper-case letter in ascending order, e.g. "A", "B", "C", etc.
For example, at the bottom of the flow, the following text should be included:
"NOTE: Procedure steps (A) and (B) for an PMIP-based S5/S8 interface are defined in TS 23.402."
  • Further guidance for drafting procedures for TS 23.402 can be found in that specification itself.
Up

Up   Top   ToC