Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  18.0.1

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

6.1.4  Coordination between 5GSM and ESMp. 473

6.1.4.1  Coordination between 5GSM and ESM with N26 interfacep. 473

Interworking with EPS is supported for a PDU session, if the PDU session includes the mapped EPS bearer context(s) or has association(s) between QoS flow and mapped EPS bearer after inter-system change from S1 mode to N1 mode. The SMF shall not include any mapped EPS bearer contexts associated with a PDU session for LADN and with a PDU session which is a multi-homed IPv6 PDU session. See coding of the Mapped EPS bearer contexts IE in subclause 9.11.4.8. In an MA PDU session, the UE shall have one set of the mapped EPS bearer contexts. The network can provide the set of the mapped EPS bearer contexts of the MA PDU session via either access of the MA PDU session. In an MA PDU session, the UE shall support modification or deletion via an access of a mapped EPS bearer context of the MA PDU session created via the same or the other access.
Upon inter-system change from N1 mode to S1 mode, the UE shall create the default EPS bearer context and the dedicated EPS bearer context(s) based on the parameters of the mapped EPS bearer contexts or the associations between QoS flow and mapped EPS bearer in the PDU session, if available. The EPS bearer identity assigned for the QoS flow of the default QoS rule becomes the EPS bearer identity of the default bearer in the corresponding PDN connection. If there is no EPS bearer identity assigned to the QoS flow of the default QoS rule of a PDU session associated with 3GPP access, or if there is no corresponding mapped EPS bearer contexts associated with the EPS bearer identity assigned to the QoS flow of the default QoS rule of a PDU session associated with 3GPP access:
  1. the PDU session is not an MA PDU session established over both 3GPP access and non-3GPP access, the UE shall perform a local release of the PDU session; or
  2. the PDU session is an MA PDU session established over both 3GPP access and non-3GPP access, the UE shall perform a local release of the PDU session over 3GPP access and consider that the MA PDU session is established over non-3GPP access only.
If there is no EPS bearer identity assigned to the QoS flow(s) of a PDU session associated with 3GPP access which is not associated with the default QoS rule, or if there is no corresponding mapped EPS bearer contexts associated with the EPS bearer identity assigned to the QoS flow of the non-default QoS rule of a PDU session associated with 3GPP access, unless the PDU session is an MA PDU session established over 3GPP access and over non-3GPP access, the UE shall locally delete the QoS rules and the QoS flow description(s). The UE uses the parameters from each PDU session for which interworking with EPS is supported to create corresponding default EPS bearer context and optionally dedicated EPS bearer context(s) as follows:
  1. the PDU session type of the PDU session shall be mapped to the PDN type of the default EPS bearer context as follows:
    1. the PDN type shall be set to "non-IP" if the PDU session type is "Unstructured";
    2. the PDN type shall be set to "IPv4" if the PDU session type is "IPv4";
    3. the PDN type shall be set to "IPv6" if the PDU session type is "IPv6";
    4. the PDN type shall be set to "IPv4v6" if the PDU session type is "IPv4v6";
    5. the PDN type shall be set to "non-IP" if the PDU session type is "Ethernet", and the UE, the network or both of them do not support Ethernet PDN type in S1 mode; and
    6. the PDN type shall be set to "Ethernet" if the PDU session type is "Ethernet" and the UE and the network support Ethernet PDN type in S1 mode;
  2. the PDU address of the PDU session shall be mapped to the PDN address of the default EPS bearer context as follows:
    1. the PDN address of the default EPS bearer context is set to the PDU address of the PDU session, if the PDU session type is "IPv4", "IPv6" or "IPv4v6"; and
    2. the PDN address of the default EPS bearer context is set to zero, if the PDU session type is "Ethernet" or "Unstructured";
  3. the DNN of the PDU session shall be mapped to the APN of the default EPS bearer context, unless the PDU session is an emergency PDU session;
  4. the APN-AMBR and extended APN-AMBR received in the parameters of the default EPS bearer context of the mapped EPS bearer contexts shall be mapped to the APN-AMBR and extended APN-AMBR of the default EPS bearer context;
  5. for each PDU session in state PDU SESSION ACTIVE, PDU SESSION MODIFICATION PENDING or PDU SESSION INACTIVE PENDING:
    1. if the UE is performing an inter-system change from N1 mode to WB-S1 mode, the UE shall set the state of the mapped EPS bearer context(s) to BEARER CONTEXT ACTIVE; or
    2. if the UE is performing an inter-system change from N1 mode to NB-S1 mode, for the mapped EPS bearer context corresponding to the default EPS bearer, the UE shall set the state of the mapped EPS bearer context to BEARER CONTEXT ACTIVE. Additionally, if the UE is performing an inter-system change from WB-N1 mode to NB-S1 mode, for the mapped EPS bearer context corresponding to a dedicated EPS bearer, if any, the UE shall set the state of the mapped EPS bearer context to BEARER CONTEXT INACTIVE; and
  6. for any other PDU session the UE shall set the state of the mapped EPS bearer context(s) to BEARER CONTEXT INACTIVE.
Additionally, for each mapped EPS bearer context or the association between QoS flow and mapped EPS bearer in the PDU session:
  1. the EPS bearer identity shall be set to the EPS bearer identity received in the mapped EPS bearer context, or the EPS bearer identity associated with the QoS flow;
  2. the EPS QoS parameters shall be set to the mapped EPS QoS parameters of the EPS bearer received in the mapped EPS bearer context, or the EPS QoS parameters associated with the QoS flow;
  3. the extended EPS QoS parameters shall be set to the mapped extended EPS QoS parameters of the EPS bearer received in the mapped EPS bearer context, or the extended EPS QoS parameters associated with the QoS flow; and
  4. the traffic flow template shall be set to the mapped traffic flow template of the EPS bearer received in the mapped EPS bearer context, or the stored traffic flow template associated with the QoS flow, if available.
After inter-system change from N1 mode to S1 mode, the UE shall associate the PDU session identity, the S-NSSAI, and the session-AMBR with the default EPS bearer context, and for each EPS bearer context mapped from one or more QoS flows, associate the QoS rule(s) for the QoS flow(s) and the QoS flow description(s) for the QoS flow(s) with the EPS bearer context.
If the PDU session is associated with the control plane only indication and supports interworking with EPS, after inter-system change from N1 mode to S1 mode, the UE shall associate the EPS bearer context(s) of the PDN connection corresponding to the PDU session with the control plane only indication.
If the PDU session is associated with a PDU session pair ID, after inter-system change from N1 mode to S1 mode, the UE shall associate the default EPS bearer context of the PDN connection corresponding to the PDU session with the PDU session pair ID. If the PDU session is associated with an RSN, after inter-system change from N1 mode to S1 mode, the UE shall associate the default EPS bearer context of the PDN connection corresponding to the PDU session with the RSN.
After inter-system change from N1 mode to S1 mode, the UE and the SMF shall maintain the PDU session type of the PDU session until the PDN connection corresponding to the PDU session is released if the UE supports non-IP PDN type and the PDU session type is "Ethernet" or "Unstructured".
After inter-system change from N1 mode to S1 mode, the UE and the SMF shall maintain the following 5GSM attributions and capabilities associated with the PDU session until the PDN connection corresponding to the PDU session is released:
  1. the always-on PDU session indication;
  2. the maximum number of supported packet filters;
  3. the support of reflective QoS;
  4. the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink and the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink;
  5. the support of multi-homed IPv6 PDU session; and
  6. if the PDU session is an MA PDU session established over 3GPP access, the PDN connection of the default EPS bearer corresponding to the MA PDU session shall be considered as a user-plane resource of the MA PDU session.
After inter-system change from N1 mode to S1 mode, the UE operating in single-registration mode in a network supporting N26 interface shall deem that the following features are supported by the network on the PDN connection corresponding to the PDU session:
  1. PS data off; and
  2. Local address in TFT.
If there is a QoS flow used for IMS signalling, after inter-system change from N1 mode to S1 mode, the EPS bearer associated with the QoS flow for IMS signalling becomes the EPS bearer for IMS signalling.
When the UE is provided with a new session-AMBR in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall discard the corresponding association(s) and associate the new value(s) with the EPS bearer context.
The network may provide the UE with one or more QoS rules by including either one QoS rules parameter, or one QoS rules with the length of two octets parameter, but not both, in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message. The network may provide the UE with one or more QoS flow descriptions corresponding to the EPS bearer context being modified, by including either one QoS flow descriptions parameter, or one QoS flow descriptions with the length of two octets parameter, but not both, in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message.
When the UE is provided with one or more QoS flow descriptions or the EPS bearer identity of an existing QoS flow description is modified in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall check the EPS bearer identity included in the QoS flow description; and:
  1. if the EPS bearer identity corresponds to the EPS bearer context being modified or the EPS bearer identity is not included, the UE shall store the QoS flow description and all the associated QoS rules, if any, for the EPS bearer context being modified for use during inter-system change from S1 mode to N1 mode; and
  2. otherwise the UE shall locally delete the QoS flow description and all the associated QoS rules, if any, and include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #84 "syntactical error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message.
When the UE is provided with one or more QoS rules, or one or more QoS flow descriptions in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall process the QoS rules sequentially starting with the first QoS rule and shall process the QoS flow descriptions sequentially starting with the first QoS flow description. The UE shall check the QoS rules and QoS flow descriptions for different types of errors as follows:
  1. Semantic errors in QoS operations:
    1. When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters" on the default QoS rule and the DQR bit is set to "the QoS rule is not the default QoS rule".
    2. When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters" on a QoS rule which is not the default QoS rule and the DQR bit is set to "the QoS rule is the default QoS rule".
    3. When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is the default QoS rule" when there's already a default QoS rule with different QoS rule identifier.
    4. When the rule operation is "Delete existing QoS rule" on the default QoS rule.
    5. When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters", or "Modify existing QoS rule without modifying packet filters" and two or more QoS rules associated with this PDU session would have identical precedence values.
    6. When the rule operation is "Modify existing QoS rule and delete packet filters", the QoS rule is a QoS rule of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, and the packet filter list in the resultant QoS rule is empty.
    7. When the rule operation is "Create new QoS rule", and there is already an existing QoS rule with the same QoS rule identifier and the existing QoS rule is associated with a QoS flow description stored for the EPS bearer context being modified or the existing QoS rule is not associated with any QoS flow description.
    8. When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters", or "Modify existing QoS rule without modifying packet filters" and there is no existing QoS rule with the same QoS rule identifier associated with a QoS flow description stored for the EPS bearer context being modified.
    9. When the rule operation is "Delete existing QoS rule" and there is no existing QoS rule with the same QoS rule identifier associated with a QoS flow description stored for the EPS bearer context being modified.
    10. When the flow description operation is "Create new QoS flow description" and there is already an existing QoS flow description with the same QoS flow identifier stored for the EPS bearer context being modified.
    11. When the flow description operation is "Modify existing QoS flow description" and there is no existing QoS flow description with the same QoS flow identifier stored for the EPS bearer context being modified.
    12. When the flow description operation is "Delete existing QoS flow description" and there is no existing QoS flow description with the same QoS flow identifier stored for the EPS bearer context being modified.
    13. When the UE determines that:
      1. the default EPS bearer context is associated with one or more QoS flows but the default EPS bearer context is not associated with the default QoS rule.
      2. a dedicated EPS bearer context is associated with one or more QoS flows but the dedicated EPS bearer context is associated with the default QoS rule.
    14. When the rule operation is "Create new QoS rule" and there is already an existing QoS rule with the same QoS rule identifier associated with a QoS flow description stored for an EPS bearer context different from the EPS bearer context being modified and belonging to the same PDN connection as the EPS bearer context being modified.
    15. When the flow description operation is "Create new QoS flow description", and there is already an existing QoS flow description with the same QoS flow identifier stored for an EPS bearer context different from the EPS bearer context being modified and belonging to the same PDN connection as the EPS bearer context being modified.
    16. When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters", or "Modify existing QoS rule without modifying packet filters" and the resultant QoS rule is associated with a QoS flow description stored for an EPS bearer context different from the EPS bearer context being modified.
    17. When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is not the default QoS rule", the QoS rule is provided for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Unstructured".
    18. When the flow description operation is "Create new QoS flow description" or "Modify existing QoS flow description", the QFI associated with the QoS flow description is not the same as the QFI of the default QoS rule, the QoS flow description is provided for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Unstructured".
    19. When the rule operation is "Modify existing QoS rule and add packet filters", the "packet filter list" field contains a match-all packet filter, the resultant QoS rule is the default QoS rule and there is already an existing match-all packet filter associated with the default QoS rule.
    20. When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is not the default QoS rule", or the rule operation is "Modify existing QoS rule and add packet filters" on a QoS rule which is not the default QoS rule or "Modify existing QoS rule and replace all packet filters" on a QoS rule which is not the default QoS rule, and one match-all packet filter is to be associated with the resultant QoS rule.
    In case 5, if the old QoS rule (i.e. the QoS rule that existed before the MODIFY EPS BEARER CONTEXT REQUEST message was received) is not the default QoS rule and the old QoS rule is associated with a QoS flow description stored for the EPS bearer context being modified, the UE shall not diagnose an error, shall further process the new request and, if it was processed successfully, shall delete the old QoS rule which has identical precedence value. Otherwise, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message.
    In case 6, if the QoS rule is not the default QoS rule, the UE shall delete the QoS rule. If the QoS rule is the default QoS rule, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message.
    In case 7, if the existing QoS rule is not the default QoS rule and the DQR bit of the new QoS rule is set to "the QoS rule is not the default QoS rule", the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS rule (i.e. the QoS rule that existed before the MODIFY EPS BEARER CONTEXT REQUEST message was received). If the existing QoS rule is the default QoS rule or the DQR bit of the new QoS rule is set to "the QoS rule is the default QoS rule", the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message.
    In case 9, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the respective QoS rule as successfully deleted.
    In case 10, the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS flow description (i.e. the QoS flow description that existed before the MODIFY EPS BEARER CONTEXT REQUEST message was received).
    In case 12, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the respective QoS flow description as successfully deleted.
    Otherwise, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message.
  2. Syntactical errors in QoS operations:
    1. When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters" or "Modify existing QoS rule and delete packet filters", the packet filter list in the QoS rule is empty, and the QoS rule is provided for a PDN connection of PDN type IPv4, IPv6, IPv4v6 or Ethernet, or for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Ethernet".
    2. When the rule operation is "Delete existing QoS rule" or "Modify existing QoS rule without modifying packet filters" with a non-empty packet filter list in the QoS rule.
    3. When the rule operation is "Modify existing QoS rule and delete packet filters" and the packet filter to be deleted does not exist in the original QoS rule.
    4. Void.
    5. When there are other types of syntactical errors in the coding of the QoS rules parameter, the QoS rules with the length of two octets parameter, the QoS flow descriptions parameter or the QoS flow descriptions with the length of two octets parameter, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list when the rule operation is "delete existing QoS rule" or "create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE), the QoS Rule Identifier is set to "no QoS rule identifier assigned", or the QoS flow identifier is set to "no QoS flow identifier assigned".
    6. When, the
      1. rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters", the UE determines, by using the QoS rule's QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in TS 23.501 Table 5.7.4-1), and there is no QoS flow description with a QFI corresponding to the QFI of the resulting QoS rule.
      2. flow description operation is "Delete existing QoS flow description", and the UE determines, by using the QoS rule's QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in TS 23.501 Table 5.7.4-1) with a QFI corresponding to the QFI of the QoS flow description that is deleted (i.e. there is no associated QoS flow description with the same QFI).
    7. When the flow description operation is "Create new QoS flow description" or "Modify existing QoS flow description", and the UE determines that there is a QoS flow description of a GBR QoS flow (as described in TS 23.501 Table 5.7.4-1) which lacks at least one of the mandatory parameters (i.e., GFBR uplink, GFBR downlink, MFBR uplink and MFBR downlink). If the QoS flow description does not include a 5QI, the UE determines this by using the QFI as the 5QI.
    8. When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters" or "Modify existing QoS rule and replace all packet filters" with a non-empty packet filter list in the QoS rule, and the DQR bit is set to "the QoS rule is the default QoS rule", the QoS rule is provided for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Unstructured".
    In case 3 the UE shall not diagnose an error, further process the deletion request and, if no error according to items c and d was detected, consider the respective packet filter as successfully deleted.
    Otherwise the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #84 "syntactical error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message.
  3. Semantic errors in packet filters:
    1. When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document.
    The UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #44 "semantic errors in packet filter(s)" in the MODIFY EPS BEARER CONTEXT ACCEPT message.
  4. Syntactical errors in packet filters:
    1. When the rule operation is "Modify existing QoS rule and add packet filters" or "Modify existing QoS rule and replace all packet filters", and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers.
    2. When the rule operation is "Create new QoS rule", and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers.
    3. When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier.
    4. Void.
    In case 1, if two or more packet filters with identical packet filter identifiers are contained in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #45 "syntactical error in packet filter(s)" in the MODIFY EPS BEARER CONTEXT ACCEPT message. Otherwise, the UE shall not diagnose an error, further process the MODIFY EPS BEARER CONTEXT REQUEST message and, if it was processed successfully, delete the old packet filters which have the identical packet filter identifiers.
    Otherwise the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #45 "syntactical error in packet filter(s)" in the MODIFY EPS BEARER CONTEXT ACCEPT message.
If the UE detects different errors in the QoS rules and QoS flow descriptions as described in this subclause which requires sending a 5GSM cause parameter in the MODIFY EPS BEARER CONTEXT ACCEPT message, the UE shall include a single 5GSM cause parameter in the MODIFY EPS BEARER CONTEXT ACCEPT message.
Upon successful completion of an EPS attach procedure or tracking area updating procedure after inter-system change from N1 mode to S1 mode (see TS 24.301), unless the PDU session is an MA PDU session established over 3GPP access and over non-3GPP access,
  1. the UE shall delete any UE derived QoS rules of each PDU session which has been transferred to EPS;
  2. the UE and the SMF shall perform a local release of the PDU session(s) associated with 3GPP access which have not been transferred to EPS; and
  3. the UE and the SMF shall perform a local release of QoS flow(s) which have not been transferred to EPS, of the PDU session(s) which have been transferred to EPS. The UE and the SMF shall also perform a local release of any QoS flow description not associated with any QoS rule and not associated with any mapped EPS bearer context. If there is a QoS flow description not associated with any QoS rule, but associated with a mapped EPS bearer context, and after the inter-system change from N1 mode to S1 mode the respective EPS bearer context is active, then the UE shall associate the QoS flow description with the EPS bearer context.
For PDU session(s) associated with non-3GPP access in 5GS, if present, the UE may:
  1. keep some or all of these PDU sessions still associated with non-3GPP access in 5GS, if supported;
  2. release some or all of these PDU sessions explicitly by initiating the UE requested PDU session release procedure(s); or
  3. attempt to transfer some or all of these PDU sessions from N1 mode to S1 mode by initiating the UE requested PDN connectivity procedure(s) with the PDN CONNECTIVITY REQUEST message created as follows:
    1. if the PDU session is an emergency PDU session, the request type shall be set to "handover of emergency bearer services". Otherwise the request type shall be set to "handover";
    2. the PDU session type of the PDU session shall be mapped to the PDN type of the default EPS bearer context as follows:
      1. the PDN type shall be set to "non-IP" if the PDU session type is "Unstructured";
      2. the PDN type shall be set to "IPv4" if the PDU session type is "IPv4";
      3. the PDN type shall be set to "IPv6" if the PDU session type is "IPv6";
      4. the PDN type shall be set to "IPv4v6" if the PDU session type is "IPv4v6";
      5. the PDN type shall be set to "non-IP" if the PDU session type is "Ethernet" and the UE, the network or both of them do not support Ethernet PDN type in S1 mode; and
      6. the PDN type shall be set to "Ethernet" if the PDU session type is "Ethernet" and the UE and the network support Ethernet PDN type in S1 mode;
    3. the DNN of the PDU session shall be mapped to the APN of the default EPS bearer context, unless the PDN connection is an emergency PDN connection; and
    4. the PDU session ID parameter in the Protocol configuration options IE or the Extended protocol configuration options IE shall be set to the PDU session identity of the PDU session.
    If a PDU session associated with non-3GPP access is transferred to EPS, the UE shall associate the PDU session identity with the default EPS bearer context and shall delete any UE derived QoS rules of such PDU session.
Interworking to 5GS is supported for a PDN connection, if the corresponding default EPS bearer context includes a PDU session identity, an S-NSSAI, if the PDN connection is a non-emergency PDN connection, session AMBR and one or more QoS flow descriptions received in the Protocol configuration options IE or Extended protocol configuration options IE (see TS 24.301), or the default EPS bearer context has association with the PDU session identity, the S-NSSAI, if the PDU session is a non-emergency PDU session, the session-AMBR and one or more QoS flow descriptions after inter-system change from N1 mode to S1 mode.
For a PDN connection established in S1 mode, to enable the UE to attempt to transfer the PDN connection from S1 mode to N1 mode in case of inter-system change, the UE shall allocate a PDU session identity, indicate the allocated PDU session identity in the PDU session ID parameter in the Protocol configuration options IE of the PDN CONNECTIVITY REQUEST message and associate the allocated PDU session identity with the default EPS bearer context of the PDN connection. If an N5CW device supports 3GPP access and establishes a new PDN connection in S1 mode, the N5CW device shall refrain from allocating "PDU session identity value 15".
For a PDN connection established in S1 mode, the SMF assigning the QoS rules shall consider that the UE supports 16 packet filters for the corresponding PDU session until the UE indicates a higher number (as specified in subclause 6.4.2.2).
The network may provide the UE with one or more QoS rules by including either one QoS rules parameter, or one QoS rules with the length of two octets parameter, but not both, in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. The network may provide the UE with one or more QoS flow descriptions corresponding to the EPS bearer context being activated, by including either one QoS flow descriptions parameter, or one QoS flow descriptions with the length of two octets parameter, but not both, in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.
When the UE is provided with one or more QoS flow descriptions in the Protocol configuration options IE or Extended protocol configuration options IE of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall check the EPS bearer identity included in the QoS flow description; and:
  1. if the EPS bearer identity corresponds to the EPS bearer context being activated or the EPS bearer identity is not included, the UE shall store the QoS flow description and all the associated QoS rules, if any, for the EPS bearer context being activated for use during inter-system change from S1 mode to N1 mode; and
  2. otherwise the UE shall locally delete the QoS flow description and all the associated QoS rules, if any, and include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #84 "syntactical error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.
When the UE is provided with one or more QoS rules, or one or more QoS flow descriptions in the Protocol configuration options IE or Extended protocol configuration options IE of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall process the QoS rules sequentially starting with the first QoS rule and shall process the QoS flow descriptions sequentially starting with the first QoS flow description. The UE shall check QoS rules and QoS flow descriptions for different types of errors as follows:
  1. Semantic errors in QoS operations:
    1. When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is the default QoS rule" when there's already a default QoS rule.
    2. When the rule operation is received in an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the rule operation is "Create new QoS rule", and there is no rule with the DQR bit set to "the QoS rule is the default QoS rule".
    3. When the rule operation is "Create new QoS rule" and two or more QoS rules associated with this PDU session would have identical precedence values.
    4. When the rule operation is an operation other than "Create new QoS rule".
    5. When the flow description operation is an operation other than "Create new QoS flow description".
    6. When the UE determines that:
      1. the default EPS bearer context is associated with one or more QoS flows but the default EPS bearer context is not associated with the default QoS rules.
      2. a dedicated EPS bearer context is associated with one or more QoS flows but the dedicated EPS bearer context is associated with the default QoS rule.
    7. When the flow description operation is received in an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the flow description operation is "Create new QoS flow description" and there is already an existing QoS flow description with the same QoS flow identifier stored for an EPS bearer context different from the EPS bearer context being activated and belonging to the same PDN connection as the EPS bearer context being activated.
    8. When the rule operation is received in an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the rule operation is "Create new QoS rule" and there is already an existing QoS rule with the same QoS rule identifier stored for an EPS bearer context different from the EPS bearer context being activated and belonging to the same PDN connection as the EPS bearer context being activated.
    9. When the rule operation is received in an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the rule operation is "Create new QoS rule" and the resultant QoS rule is associated with a QoS flow description stored for an EPS bearer context different from the EPS bearer context being activated and belonging to the same PDN connection as the EPS bearer context being activated.
    10. When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is not the default QoS rule" and one match-all packet filter is to be associated with the QoS rule.
    In case 4, if the rule operation is for a non-default QoS rule, the UE shall delete the QoS rule. If the QoS rule is the default QoS rule, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.
    Otherwise for all the cases above, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.
  2. Syntactical errors in QoS operations:
    1. When the rule operation is "Create new QoS rule", the packet filter list in the QoS rule is empty, and the QoS rule is provided for a PDN connection of PDN type IPv4, IPv6, IPv4v6 or Ethernet, or for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Ethernet".
    2. Void.
    3. When there are other types of syntactical errors in the coding of the QoS rules parameter, the QoS rules with the length of two octets parameter, the QoS flow descriptions parameter or the QoS flow descriptions with the length of two octets parameter, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list when the rule operation is "delete existing QoS rule" or "create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE), the QoS Rule Identifier is set to "no QoS rule identifier assigned", or the QoS flow identifier is set to "no QoS flow identifier assigned".
    4. When, the
      1. rule operation is "Create new QoS rule", the UE determines, by using the QoS rule's QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in TS 23.501 Table 5.7.4-1), and there is no QoS flow description with a QFI corresponding to the QFI of the resulting QoS rule.
    5. When the flow description operation is "Create new QoS flow description", and the UE determines that there is a QoS flow description of a GBR QoS flow (as described in TS 23.501 Table 5.7.4-1) which lacks at least one of the mandatory parameters (i.e., GFBR uplink, GFBR downlink, MFBR uplink and MFBR downlink). If the QoS flow description does not include a 5QI, the UE determines this by using the QFI as the 5QI.
    In case 1, case 3 or case 4, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #84 "syntactical error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.
    In case 5, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #84 "syntactical error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.
  3. Semantic errors in packet filters:
    1. When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document.
    The UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #44 "semantic errors in packet filter(s)" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.
  4. Syntactical errors in packet filters:
    1. When the rule operation is "Create new QoS rule" and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers.
    2. When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier.
    The UE shall delete the QoS rule and include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #45 "syntactical error in packet filter(s)" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.
If the UE detects different errors in the QoS rules and QoS flow descriptions as described in this subclause which requires sending a 5GSM cause parameter in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message, the UE shall include a single 5GSM cause parameter in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.
Upon inter-system change from S1 mode to N1 mode, the UE uses the parameters from the default EPS bearer context of each PDN connection for which interworking to 5GS is supported to create a corresponding PDU session associated with 3GPP access as follows, unless the PDN connection is a user-plane resource of an MA PDU session:
  1. the PDN type of the default EPS bearer context shall be mapped to the PDU session type of the PDU session as follows:
    1. if the PDN type is "non-IP":
      • the PDU session type is set to the locally available information associated with the PDN connection (either "Ethernet" or "Unstructured"), if available; or
      • otherwise, the PDU session type is set to "Unstructured";
    2. if the PDN type is "IPv4" the PDU session type is set to "IPv4";
    3. if the PDN type is "IPv6", the PDU session type is set to "IPv6";
    4. if the PDN type is "IPv4v6", the PDU session type is set to "IPv4v6"; and
    5. if the PDN type is "Ethernet", the PDU session type is "Ethernet";
  2. the PDN address of the default EPS bearer context shall be mapped to PDU address of the PDU session, if the PDN type is "IPv4", "IPv6" or "IPv4v6";
  3. the APN of the default EPS bearer context shall be mapped to the DNN of the PDU session, unless the PDN connection is an emergency PDN connection;
  4. for each default EPS bearer context in state BEARER CONTEXT ACTIVE the UE shall set the state of the mapped PDU session to PDU SESSION ACTIVE; and
  5. for any other default EPS bearer context the UE shall set the state of the mapped PDU session to PDU SESSION INACTIVE.
Additionally, the UE shall set:
  1. the PDU session identity of the PDU session to the PDU session identity included by the UE in the Protocol configuration options IE or Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST message, or the PDU session identity associated with the default EPS bearer context;
  2. the S-NSSAI of the PDU session to the S-NSSAI included by the network in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, or the S-NSSAI associated with the default EPS bearer context, if the PDN connection is a non-emergency PDN connection;
  3. the session-AMBR of the PDU session to the session-AMBR included by the network in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message or the MODIFY EPS BEARER CONTEXT REQUEST message, or the session-AMBR associated with the default EPS bearer context;
  4. the SSC mode of the PDU session to "SSC mode 1"; and
  5. the always-on PDU session indication to the always-on PDU session indication maintained in the UE, if any.
Upon inter-system change from S1 mode to N1 mode, the UE shall locally release the PDN connection(s) for which interworking to 5GS is not supported.
Upon inter-system change from S1 mode to N1 mode, for each PDN connection which is a user-plane resource of MA PDU session and for which interworking to 5GS is supported, the UE shall consider that the MA PDU session is established over 3GPP access and, unless the MA PDU session is established over non-3GPP access too, the UE shall set the session-AMBR of the PDU session to the session-AMBR included by the network in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message or the MODIFY EPS BEARER CONTEXT REQUEST message, or the session-AMBR associated with the default EPS bearer context of the PDN connection.
Additionally, for each EPS bearer context of the PDN connection, the UE shall create QoS flow(s) each of which is associated with the QoS flow description received in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, ACTIVATE DEDICATED EPS BEARER REQUEST message, and/or MODIFY EPS BEARER REQUEST message (see TS 24.301), or the QoS flow description associated with EPS bearer context, unless:
  1. the PDU session is an MA PDU session which:
    1. is established over non-3GPP access; and
    2. has a PDN connection as a user-plane resource; and
  2. the QoS flow already exists over the non-3GPP access.
Additionally, for each EPS bearer context of the PDN connection, the UE shall create QoS rules(s), if any, each of which is associated with the QoS rule received in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, ACTIVATE DEDICATED EPS BEARER REQUEST message, or MODIFY EPS BEARER CONTEXT REQUEST message (see TS 24.301), or the QoS rules associated with EPS bearer context, unless:
  1. the PDU session is an MA PDU session which:
    1. is established over non-3GPP access; and
    2. has a PDN connection as a user-plane resource; and
  2. the QoS rule already exists over the non-3GPP access.
Additionally, for each PDU session which was created at inter-system change from S1 mode to N1 mode from a corresponding PDN connection of the "Ethernet" PDN type, the UE shall consider that Ethernet PDN type in S1 mode is supported by the network and the SMF shall consider that Ethernet PDN type in S1 mode is supported by the UE.
The UE and the network shall locally release the PDN connection(s) and EPS bearer context(s) associated with the 3GPP access which have not been transferred to 5GS.
After inter-system change from S1 mode to N1 mode, for each QoS flow mapped from an EPS bearer context the UE shall associate the EPS bearer identity, the EPS QoS parameters, the extended EPS QoS parameters, and the traffic flow template, if available, of the EPS bearer context with the QoS flow.
After inter-system change from S1 mode to N1 mode, for each QoS flow of an MA PDU session which:
  1. is established over non-3GPP access; and
  2. has a PDN connection as a user-plane resource;
such that the QoS flow was received in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, ACTIVATE DEDICATED EPS BEARER REQUEST message, MODIFY EPS BEARER CONTEXT REQUEST message, (see TS 24.301), or associated with EPS bearer context, the UE shall associate the EPS bearer identity, the EPS QoS parameters, the extended EPS QoS parameters, and the traffic flow template, if available, of the EPS bearer context with the QoS flow.
If the EPS bearer context(s) of the PDN connection are associated with the control plane only indication, and the PDN connection supports interworking to 5GS, after inter-system change from S1 mode to N1 mode, the UE shall associate the PDU session corresponding to the PDN connection with the control plane only indication.
If the default EPS bearer context of the PDN connection is associated with the PDU session pair ID, and the PDN connection supports interworking to 5GS, after inter-system change from S1 mode to N1 mode, the UE shall associate the PDU session corresponding to the PDN connection with the PDU session pair ID. If the default EPS bearer context of the PDN connection is associated with the RSN, and the PDN connection supports interworking to 5GS, after inter-system change from S1 mode to N1 mode, the UE shall associate the PDU session corresponding to the PDN connection with the RSN.
If there is an EPS bearer used for IMS signalling, after inter-system change from S1 mode to N1 mode, the QoS flow of the default QoS rule in the corresponding PDU session is used for IMS signalling.
For a PDN connection established when in S1 mode, upon the first inter-system change from S1 mode to N1 mode, the SMF shall determine the PDU session indication as specified in subclause 6.3.2.2.
When the UE is provided with one or more mapped EPS bearer contexts in the Mapped EPS bearer contexts IE of the PDU SESSION MODIFICATION COMMAND message, the UE shall process the mapped EPS bearer contexts sequentially starting with the first mapped EPS bearer context.
When the UE is provided with a new EPS bearer identity, a new EPS QoS parameters, a new extended EPS QoS parameters, a new APN-AMBR or a new extended APN-AMBR in the Mapped EPS bearer context IE of the PDU SESSION MODIFICATION COMMAND message for a QoS flow, the UE shall discard the corresponding association(s) and associate the new value(s) with the QoS flow.
When the UE is provided with a new traffic flow template in the Mapped EPS bearer contexts IE of the PDU SESSION MODIFICATION COMMAND message for a QoS flow, the UE shall check the traffic flow template for different types of TFT IE errors as specified in subclause 6.3.2.3.
When a QoS flow is deleted, the associated EPS bearer context information that are mapped from the deleted QoS flow shall be deleted from the UE and the network if there is no other existing QoS flow associated with this EPS bearer context. When the EPS bearer identity of a QoS flow is deleted, the associated EPS bearer context information that are mapped from the deleted EPS bearer identity shall be deleted from the UE and the network if there is no other existing QoS flow associated with this EPS bearer context. When an EPS bearer is released, all the associated QoS flow descriptions and QoS rules that are mapped from the released EPS bearer shall be deleted from the UE and the network.
Upon inter-system change from N1 mode to S1 mode, if the UE has any PDU sessions associated with one or more MBS multicast sessions, the UE shall locally leave the associated MBS multicast sessions and the network shall consider the UE as removed from the associated MBS sessions.
For the case of handover of an existing PDU session from 3GPP access to non-3GPP access,
  • upon receipt of the PDU SESSION ESTABLISHMENT ACCEPT message, the UE locally deletes the EPS bearer identities for the PDU session, if any (see subclause 6.4.1.3); and
  • after successful handover, the network shall locally delete the EPS bearer identities for the PDU session, if any.
Up

6.1.4.2  Coordination between 5GSM and ESM without N26 interfacep. 486

When the network does not support N26 interface, the SMF does not provide the UE with the mapped EPS bearer context for a PDU session.
Upon inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE shall not transfer a PDU session for LADN to EPS.
Upon inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE shall not transfer a multi-homed IPv6 PDU session to EPS.
Upon inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE shall use the parameters from each PDU session which the UE intends to transfer to EPS to create the contents of a PDN CONNECTIVITY REQUEST message as follows:
  1. if the PDU session is an emergency PDU session, the request type shall be set to "handover of emergency bearer services". Otherwise the request type shall be set to "handover";
  2. the PDU session type of the PDU session shall be mapped to the PDN type of the default EPS bearer context as follows:
    1. the PDN type shall be set to "non-IP" if the PDU session type is "Unstructured";
    2. the PDN type shall be set to "IPv4" if the PDU session type is "IPv4";
    3. the PDN type shall be set to "IPv6" if the PDU session type is "IPv6";
    4. the PDN type shall be set to "IPv4v6" if the PDU session type is "IPv4v6";
    5. the PDN type shall be set to "non-IP" if the PDU session type is "Ethernet" and the UE, the network or both of them do not support Ethernet PDN type in S1 mode; and
    6. the PDN type shall be set to "Ethernet" if the PDU session type is "Ethernet" and the UE and the network support Ethernet PDN type in S1 mode;
  3. the DNN of the PDU session shall be mapped to the APN of the default EPS bearer context, unless the PDU session is an emergency PDU session;
  4. the PDU session ID parameter in the Protocol configuration options IE or Extended protocol configuration options IE shall be set to the PDU session identity of the PDU session; and
  5. if the PDU session is an MA PDU session established over 3GPP access, the ATSSS request parameter shall be included in the Protocol configuration options IE or Extended protocol configuration options IE.
After inter-system change from N1 mode to S1 mode, the UE shall associate the PDU session identity with the default EPS bearer context. If the PDU session being transferred is a non-emergency PDU session, the UE shall in addition associate the S-NSSAI and the PLMN ID of the current PLMN with the default EPS bearer context.
Upon successful completion of an EPS attach procedure after inter-system change from N1 mode to S1 mode (see TS 24.301), the UE shall delete any UE derived QoS rules except when the PDU session is an MA PDU session established over 3GPP access and non-3GPP access.
The UE shall perform a local release of the PDU session(s) and QoS flow(s) associated with the 3GPP access which have not been transferred to EPS. The UE shall also perform a local release of any QoS flow description not associated with any QoS rule.
For PDU session(s) associated with non-3GPP access in 5GS, if present, the UE may:
  1. keep some or all of these PDU sessions still associated with non-3GPP access in 5GS, if supported;
  2. release some or all of these PDU sessions explicitly by initiating the UE requested PDU session release procedure(s); or
  3. attempt to transfer some or all of these PDU sessions from N1 mode to S1 mode by initiating the UE requested PDN connectivity procedure(s) with the PDN CONNECTIVITY REQUEST message created as above.
When the network does not support N26 interface, the MME does not provide the UE with the mapped PDU session for a PDN connection but provides the UE with an S-NSSAI if the PDN connection is not for emergency bearer services. When establishing a new PDN connection in S1 mode, to enable the UE to attempt to transfer the PDN connection from S1 mode to N1 mode in case of inter-system change, the UE shall allocate a PDU session identity, indicate the allocated PDU session identity in the PDU session ID parameter in the Protocol configuration options IE of the PDN CONNECTIVITY REQUEST message and associate the allocated PDU session identity with the default EPS bearer context of the PDN connection. If an N5CW device supports 3GPP access and establishes a new PDN connection in S1 mode, the N5CW device shall refrain from allocating "PDU session identity value 15". The network provides the UE with an S-NSSAI and the related PLMN ID in the Protocol configuration options IE or Extended protocol configuration options IE of the ACTIVATE DEFAULT EPS BEARER REQUEST message, the UE shall delete the stored S-NSSAI and the related PLMN ID, if any, and shall store the S-NSSAI and the related PLMN ID provided in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.
Upon inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode, the UE uses the parameters from the default EPS bearer context of each PDN connection which the UE intends to transfer to 5GS and for which the UE has allocated a PDU session identity to create a PDU SESSION ESTABLISHMENT REQUEST message as follows:
  1. if the PDN connection is for emergency bearer services, the request type shall be set to "existing emergency PDU session". Otherwise the request type shall be set to:
    1. "MA PDU request", if the PDN connection to be transferred is a user-plane resource of an MA PDU session; or
    2. "existing PDU session";
  2. the PDN type of the default EPS bearer context shall be mapped to the PDU session type of the PDU session as follows:
    1. if the PDN type is "non-IP":
      • the PDU session type is set to the locally available information associated with the PDN connection (either "Ethernet" or "Unstructured"), if available; or
      • otherwise, the PDU session type is set to "Unstructured";
    2. if the PDN type is "IPv4" the PDU session type is set to "IPv4";
    3. if the PDN type is "IPv6", the PDU session type is set to "IPv6";
    4. if the PDN type is "IPv4v6", the PDU session type is set to "IPv4v6"; and
    5. if the PDN type is "Ethernet", the PDU session type is set to "Ethernet"; and
  3. the APN of the default EPS bearer context shall be mapped to the DNN of the PDU session, unless the PDN connection is an emergency PDN connection;
  4. the PDU session ID shall be set to the PDU session identity included by the UE in the Protocol configuration options IE or Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST message, or to the PDU session ID associated with the default EPS bearer context; and
  5. if the PDU session is not an emergency PDU session, the S-NSSAI of the PDU session shall be set to the S-NSSAI included by the network in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, if provided by the network, or the S-NSSAI associated with the default EPS bearer context, if available.
The UE shall locally release the PDN connection(s) and EPS bearer(s) associated with the 3GPP access which have not been transferred to 5GS.
Upon inter-system change from N1 mode to S1 mode, if the UE has any PDU sessions associated with one or more MBS multicast sessions, the UE shall locally leave the associated MBS multicast sessions and the network shall consider the UE as removed from the associated MBS sessions.
Up

6.1.4a  Coordination between 5GSM and SM |R16|p. 489

Coordination between 5GSM and SM states is not required.
After the 5G-SRVCC handover from NG-RAN to UTRAN (see TS 23.216), all the PDU sessions of the UE are locally released at the UE and the network. If the UE has any PDU sessions associated with one or more MBS multicast sessions, the UE shall locally leave the associated MBS multicast sessions and the network shall consider the UE as removed from the associated MBS sessions.

6.1.5  Coordination for interworking with ePDG connected to EPC |R16|p. 489

When the UE establishes a new PDN connection via an ePDG connected to EPC, to enable the transfer of the PDN connection to N1 mode over 3GPP access in case of inter-system change, the UE allocates a PDU session identity and indicates its value in the PDU session ID field in the N1_MODE_CAPABILITY Notify payload of the IKE_AUTH request message (see TS 24.302). The network provides the UE with an S-NSSAI in the N1_MODE_INFORMATION Notify payload of the IKE_AUTH response message (see TS 24.302).
Upon inter-system change to N1 mode over 3GPP access, for PDN connection(s) established via an ePDG connected to EPC, if present, the UE may:
  1. keep some or all of these PDN connections still via ePDG connected to EPC, if supported;
  2. release some or all of these PDN connections explicitly by initiating the UE initiated tunnel disconnection procedure(s) as specified in TS 24.302; or
  3. attempt to transfer some or all of these PDN connections to N1 mode over 3GPP access using the parameters of the PDN connection for which the UE has allocated a PDU session identity by initiating the PDU session establishment procedure(s) with the PDU SESSION ESTABLISHMENT REQUEST message created. In that case, for each and every PDN connection to be transferred:
    1. if the PDN connection is for emergency bearer services, the request type shall be set to "existing emergency PDU session". Otherwise the request type shall be set to "existing PDU session";
    2. if the previously allocated home address information for a PDN connection consists of an IPv4 address only for an ePDG connected to EPC according to TS 24.302, the PDU session type shall be set to "IPv4";
    3. if the previously allocated home address information for a PDN connection consists of an IPv6 prefix only for an ePDG connected to EPC according to TS 24.302, the PDU session type shall be set to "IPv6";
    4. if the previously allocated home address information for a PDN connection consists of both an IPv4 address and an IPv6 prefix for an ePDG connected to EPC according to TS 24.302, the PDU session type shall be set to "IPv4v6";
    5. the APN of the PDN connection shall be mapped to the DNN of the PDU session;
    6. the PDU session ID shall be set to the PDU session identity in the N1_MODE_CAPABILITY Notify payload of the IKE_AUTH request message establishing IPsec tunnel of the PDN connection; and
    7. if the PDN connection is not for emergency bearer services, the S-NSSAI of the PDU session shall be set to the S-NSSAI associated with the PDN connection as specified in TS 24.302. The UE shall not request to perform handover of an existing PDN connection to N1 mode over 3GPP access if the associated S-NSSAI is not included in the allowed NSSAI for 3GPP access.
If an existing PDU session is transferred from 3GPP access to an ePDG connected to EPC connection and that existing PDU session is associated with one or more MBS sessions, the UE shall locally leave the associated MBS sessions and the SMF shall consider the UE as removed from the associated MBS sessions.
Up

Up   Top   ToC