Improvements in and relating to Network Slice Access Group (NSAG) Usage

The UE's NAS layer in 5G networks optimally provides S-NSSAI to lower layers based on PDU sessions, addressing incorrect resource allocation and inconsistencies by omitting non-slice-related procedures and non-allowed areas, enhancing network efficiency and resource utilization.

GB2627367BActive Publication Date: 2026-11-13SAMSUNG ELECTRONICS CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
GB2024000418
Authority / Receiving Office
GB · GB
Patent Type
Patents
Current Assignee / Owner
Priority Date
2023-02-16
Filing Date
2024-01-11
Publication Date
2026-11-13
Estimated Expiration
2044-01-11

AI Technical Summary

Technical Problem

Existing solutions for providing Network Slice Selection Assistance Information (S-NSSAI) to lower layers in a UE are problematic, leading to incorrect resource allocation for non-slice-related services, misuse of high-priority resources, and inconsistencies due to non-allowed areas, particularly in 5G networks.

Method used

The UE's Non-Access Stratum (NAS) layer identifies the appropriate S-NSSAI for access attempts related to PDU sessions and provides it to lower layers, while omitting S-NSSAI for non-slice-related procedures and removing non-allowed TAIs from NSAG information.

Benefits of technology

This approach ensures correct resource allocation, prevents misuse of high-priority resources, and maintains consistent UE behavior by aligning access attempts with actual service requirements, reducing inconsistencies and optimizing network usage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000001_0000
    Figure 00000001_0000
  • Figure 00000001_0001
    Figure 00000001_0001
Patent Text Reader

Abstract

A method for performing RACH access in a user equipment (UE) wherein a Non Access Stratum, NAS, layer identifies a slice, S-NSSAI, for which an access attempt is made. Further, no slice, S-NSSAI, is p
Need to check novelty before this filing date? Find Prior Art

Description

The present invention relates to a telecommunication network, particularly one that employs network slicing. Embodiments of the invention find particular, but not exclusive use in Fifth Generation (5G) networks, but the skilled person will appreciate that the teaching herein can be applied in a variety of networks. A set of slices, Single - Network Slice Selection Assistance Information (S-NSSAI), may be known to be part of a group, where the set of slices may be optionally valid with a set of Tracking Area Identities (TAIs), if available, and a certain priority level may also be associated with these slices - and hence the group. If the list of TAIs is not available, then the slices are valid in the entire Public Land Mobile Network (PLMN). The following is an excerpt from section 4.6.2.6 of TS 24.501 about NSAG: “The NSAG information provided by the network and stored in the User Equipment (UE) includes a list of NS AGs each of which contains: a) an NSAG ID; b) a list of S-NSSAI(s), which are associated with the NSAG and shall be part of the configured NSSAI; c) a priority value that is associated with the NSAG; and d) optionally a list of TAIs in which the NSAG is valid. If it is not provided by the network, the NSAG is valid in the PLMN which has sent the NSAG information. The UE NAS layer shall provide the lower layers with. a) the most recent NSAG information stored in the UE (see subclause 4.6.2.2); b) the allowed NSSAI or the requested NSSAI for the purpose of network slicebased cell reselection (see 3GPP TS 23.501); and c) one or more S-NSSAIs related to an access attempt for the purpose of network slice-based random access, when the access attempt is made by the UE in 5GMM-IDLE mode or 5GMM-CONNECTED mode with RRC inactive indication, determined as follows: i) S-NSSAI(s) triggering the initial NAS message (requested NSSAI (if any) in case of the REGISTRATION REQUEST message and S-NSSAI(s) associated with all the PDU sessions included in the Uplink data status IE (if any), PDU session status IE (if any), or Allowed PDU session status IE (if any) in case of the (CONTROL PLANE) SERVICE REQUEST message), if an access attempt occurred due to an initial NAS message; ii) the S-NSSAI associated with the PDU session, if an access attempt occurred due to an uplink user data packet to be sent for a PDU session with suspended user-plane resources or an UL NAS TRANSPORT which carries a 5GSM message for a PDU session associated with an S-NSSAI (if any); or Hi) the allowed NSSAI (if any), if an access attempt occurred for other reason than those specified in bullets i) and ii). Editor's note: It is For Further Study (FFS) how a UE operates in terms of NS AG if the UE has an emergency PDU session or attempts to establish an emergency PDU session. NOTE: The AMF can take local configuration, UE 5GMM capabilities, subscribed S-NSSAIs, HPLMN, etc. to determine the NSAG priority information for the associated NS AG to a UE." Service area restrictions define so called non-allowed areas in which a UE is not able to receive normal services except for emergency services or high priority services (e.g. when the UE is a high priority access UE). The UE can be in a non-allowed area either when the current Tracking Area Identity (TAI) is part of the non-allowed area (which is indicated in the Service area list Information Element (IE)), or when the UE is in a TAI which is outside the TAIs that are considered to be allowed TAIs (where the allowed TAIs can also be indicated in the Service area list IE). The following is from section 5.3.5 of TS 24.501 which describes the details of service area restrictions: “The service area restrictions consist of tracking areas forming either an allowed area, or a non-allowed area. The tracking areas belong to either the registered PLMN or its equivalent PLMNs in the registration area. The allowed area can contain up to 16 tracking areas or include all tracking areas in the registered PLMN and its equivalent PLMN(s) in the registration area. The non-allowed area can contain up to 16 tracking areas. The network conveys the service area restrictions to the UE by including either an allowed area, or a non-allowed area, but not both, in the Service area list IE of a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message. If the network does not convey the service area restrictions to the UE in the Service area list IE of a REGISTRATION ACCEPT message, the UE shall treat all tracking areas in the registered PLMN and its equivalent PLMN(s) in the registration area as allowed area and delete the stored list of "allowed tracking areas" or the stored list of "non-allowed tracking areas". When the UE receives a Service area list IE with an allowed area indication during a registration procedure or a generic UE configuration update procedure: a) if the "Type of list" included in the Service area list IE does not indicate "all TAIs belonging to the PLMNs in the registration area are allowed area", the UE shall delete the old list of "allowed tracking areas" and store the tracking areas in the allowed area as the list of "allowed tracking areas". If the UE has a stored list of "non-allowed tracking areas", the UE shall delete that list; or b) if the "Type of list" included in the Service area list IE indicates "all TAIs belonging to the PLMNs in the registration area are allowed area", the UE shall treat all tracking areas in the registered PLMN and its equivalent PLMN(s) as allowed area and delete the stored list of "allowed tracking areas" or the stored list of "non-allowed tracking areas". When the UE receives a Service area list IE with a non-allowed area indication during a registration procedure or a generic UE configuration update procedure, the UE shall delete the old list of "non-allowed tracking areas" and store the tracking areas in the non-allowed area as the list of "non-allowed tracking areas". If the UE has a stored list of "allowed tracking areas", the UE shall delete that list. If the UE is successfully registered to a PLMN and has a stored list of "allowed tracking areas": a) while the current TAI is in the list of "allowed tracking areas", the UE shall stay in, or enter, the state 5GMM-REGISTERED.NORMAL-SERVICE and is allowed to initiate any 5GMM and 5GSM procedures; and b) while the UE is camped on a cell which is in the registered PLMN or a PLMN from the list of equivalent PLMNs and the current TAI is not in the list of "allowed tracking areas", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and: 1) if the UE is in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication over 3GPP access, the UE: i) shall not include the Uplink data status IE in the registration procedure for mobility and periodic registration update except for emergency services or for high priority access; ii) shall not perform the registration procedure for mobility and periodic registration update with Follow-on request indicator set to "Follow-on request pending", except for: emergency services; high priority access; indicating a change of 3GPP PS data off UE status; sending an SOR transparent container; sending a UE policy container; or sending a UE parameters update transparent container; Hi) shall not initiate a service request procedure or request the lower layers to resume a suspended connection, except for: emergency services; emergency services fallback; high priority access; responding to paging; responding to notification received over non-3GPP access; indicating a change of 3GPP PS data off UE status; sending an SOR transparent container; sending a UE policy container; or sending a UE parameters update transparent container; and 2) if the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, the UE: i) shall not perform the registration procedure for mobility and periodic registration update with Uplink data status IE except for emergency services or for high priority access; ii) shall not initiate a service request procedure except for: emergency services; emergency services fallback; high priority access; responding to paging or responding to notification received over non-3GPP access; Hi) shall not initiate a 5GSM procedure except for: emergency services; high priority access; or indicating a change of 3GPP PS data off UE status; and iv) shall not perform the NAS transport procedure except for the sending: SMS; an LPP message; a location services message; an SOR transparent container; a UE policy container; a UE parameters update transparent container; or a Cellular Internet of Things (CloT) user data container. NOTE 1: The contents of CloT user data container can be data that is not for exception reports, or data that is for exception reports if allowed for the UE (see subclause 6.2.13). If the UE is successfully registered to a PLMN and has a stored list of "non-allowed tracking areas": a) while the UE is camped on a cell which is in the registered PLMN or a PLMN from the list of equivalent PLMNs and the current TAI is not in the list of "non-allowed tracking areas", the UE shall stay in, or enter, the state 5GMM-REGISTERED.NORMAL-SERVICE and is allowed to initiate any 5GMM and 5GSM procedures; and b) while the current TAI is in the list of "non-allowed tracking areas", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and: 1) if the UE is in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication over 3GPP access, the UE: i) shall not include the Uplink data status IE in the registration procedure for mobility and periodic registration update except for emergency services or for high priority access; ii) shall not perform the registration procedure for mobility and periodic registration update with Follow-on request indicator set to "Follow-on request pending", except for: emergency services; high priority access; indicating a change of 3GPP PS data off UE status; sending an SOR transparent container; sending a UE policy container; or sending a UE parameters update transparent container; and Hi) shall not initiate a service request procedure or request the lower layers to resume a suspended connection, except for: emergency services; emergency services fallback; high priority access; responding to paging; responding to notification received over non-3GPP access; indicating a change of 3GPP PS data off UE status; sending an SOR transparent container; sending a UE policy container; or sending a UE parameters update transparent container; and 2) if the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, the UE: i) shall not perform the registration procedure for mobility and periodic registration update with the Uplink data status IE except for emergency services or for high priority access; ii) shall not initiate a service request procedure or request the lower layers to resume a suspended connection, except for: emergency services; emergency services fallback; high priority access; or responding to paging or responding to notification received over non-3GPP access; Hi) shall not initiate a 5GSM procedure except for: emergency services; high priority access; or indicating a change of 3GPP PS data off UE status; and iv) shall not perform the NAS transport procedure except for the sending: SMS; an LPP message; a location services message; an SOR transparent container; a UE policy container; a UE parameters update transparent container; or a CloT user data container. NOTE 2: The contents of CloT user data container can be data that is not for exception reports, or data that is for exception reports if allowed for the UE (see subclause 6.2.13). The list of "allowed tracking areas", as well as the list of "non-allowed tracking areas" shall be erased when: a) the UE is switched off; and b) the UICC containing the USIM is removed or an entry of the "list of subscriber data" with the SNPN identity of the SNPN is updated. When a tracking area is added to the list of "5GS forbidden tracking areas for roaming" or to the list of "5GS forbidden tracking areas for regional provision of service" as specified in the subclauses 5.5.1.2.5 or 5.5.1.3.5, the tracking area shall be removed from the list of "allowed tracking areas" if the tracking area is already present in the list of "allowed tracking areas" and from the list of "non-allowed tracking areas" if the tracking area is already present in the list of "non-allowed tracking areas". ” A problem has been identified with providing the allows NSSAI to the lower layers. As noted above from TS 24.501, the UE provides the following to the lower layers (copied again from above): “c) one or more S-NSSAIs related to an access attempt for the purpose of network slice-based random access, when the access attempt is made by the UE in 5GMM-IDLE mode or 5GMM-CONNECTED mode with RRC inactive indication, determined as follows: i) S-NSSAI(s) triggering the initial NAS message (requested NSSAI (if any) in case of the REGISTRATION REQUEST message and S-NSSAI(s) associated with all the PDU sessions included in the Uplink data status IE (if any), PDU session status IE (if any), or Allowed PDU session status IE (if any) in case of the (CONTROL PLANE) SERVICE REQUEST message), if an access attempt occurred due to an initial NAS message; ii) the S-NSSAI associated with the PDU session, if an access attempt occurred due to an uplink user data packet to be sent for a PDU session with suspended user-plane resources or an UL NAS TRANSPORT which carries a 5GSM message for a PDU session associated with an S-NSSAI (if any); or Hi) the allowed NSSAI (if any), if an access attempt occurred for other reason than those specified in bullets i) and ii).” The last point quoted above requires the UE to provide the allowed NSSAI if an access attempt is made for any other reason than those listed in bullets i) and ii). In these two bullets, it is clear that there is a direct connection between a procedure and the slice (i.e. S-NSSAI in question) e.g. when the UE wants user-plane resources then it provides the S-NSSAI which is associated with the PDU session. However, providing the entire allowed NSSAI (as specified by bullet iii) for all other reasons is problematic for the following reasons: • The UE may perform an access attempt for signalling that is not related to any slice. For example, the UE may want to send Short Message Service (SMS) and hence performs the service request procedure to first transition to connected mode and then send an SMS. The SMS service is not associated with any slice and so providing the allowed NSSAI to the lower layers may erroneously cause the lower layers to use resources which are associated with the allowed NSSAI and which can be of high priority although SMS is a low priority service • Similarly, the UE may perform an access attempt to send location services message which is a service that is independent of slicing and as such the UE may end up using the wrong resources as the lower layers consider the slices in the allowed NSSAI which are not associated with the actual service that the UE wants to use • The same can be said for the case when the UE wants to send SOR (Steering of Roaming) transparent container, UE policy container, UE parameters update transparent container, etc. Additionally, the UE may perform an access attempt to deregister from the network. According to the prior art description from TS 24.501, the UE will provide the allowed NSSAI to the lower layers which will then lead to selection of resources for random access (RACH resources) considering the slices (S-NSSAIs) of the allowed NSSAI. These slices may have prioritized resources, but the UE actually wants to completely deregister from the network and not use any slice. The prior art solution can lead to using prioritized resources although the access attempt is to deregister the UE and this is not a good solution as it consumes prioritized resources for a rather low priority procedure. A further problem is that NSAG information provided to the lower layers only considers Protocol Data Unit (PDU) sessions for which user-plane resources are needed. As mentioned in the excerpt from TS 24.501 above, the S-NSSAI that is provided to the lower layers considers mostly PDU sessions for which user-plane (UP) resources are to be requested (and also considers the session management signalling for the PDU session which is associated with the slice i.e. S-NSSAI). However, a UE may be using CloT 5GS optimization for which the UE sends data over the control plane i.e. over Non-Access Stratum (NAS). Although this actually uses a PDU session with an associated slice (or S-NSSAI), the prior art solution ignores such a use case and therefore the lower layers will not get the correct information for this use-case, thereby risking that the wrong RACH resources will be used by the Radio Resource Control (RRC) layer when the NAS does not indicate the correct slice (i.e. S-NSSAI) for which an access attempt is being made. A still further problem is that NSAG information may erroneously contain a TAI which is a nonallowed area. In general, both the UE and network check for certain errors which may occur at in different procedures or in information elements (lEs) of NAS messages e.g. there are numerous error checks that a UE performs as part of Quality of Service (QoS) parameter handling. Another example is that a TAI may exist in different lists where even though it should only be part of one list. Another problematic situation is that a UE may receive a TAI which is in the service area restriction list such that it is considered to be a non-allowed area, and at the same time the TAI is in the NSAG information which the UE receives. Receiving a non-allowed TAI in the NSAG information may wrongly lead a UE to consider that the slice is accessible for user plane resources or session management signalling although the service area restrictions prohibits the UE from using the associated PDU session or establish a PDU session for that slice when in the non-allowed area. Such a situation may lead to inconsistencies, which could lead to nondefined or erroneous operation. It is desirable that such a situation is resolved in order to have a consistent set of requirements that don’t appear to contradict each other. To give a further example of this, a UE may have a so called always-on PDU session which requires user-plane (UP) resources to be established at any time when the UE is in connected mode. This normally puts a requirement on the UE to always request UP resource establishment (by including the Uplink data status IE, in which the UP resource establishment is requested) at every time the UE transitions to connected mode. However, this requirement is dropped when the UE is in a non-allowed area such that the UE must not request UP resources in a non-allowed area even for an always-on PDU session as quoted below from section 5.6.1.2.1 ofTS 24.501: “When the UE is in a non-allowed area or is not in an allowed area as specified in subclause 5.3.5 and: a) if the uplink signalling pending is to indicate a change of 3GPP PS data off UE status for a PDU session, the UE shall set the service type IE in the SERVICE REQUEST message to "elevated signalling", and shall not include the Uplink data status IE in the SERVICE REQUEST message even if the UE has one or more active always-on PDU sessions associated with the access type over which the SERVICE REQUEST message is sent; or b) otherwise, the UE shall not initiate service request procedure except for emergency services, high priority access or responding to paging or notification. ” From the above, it can be concluded that although there are certain expectations or requirements that are generally to be enforced, the UE verifies other conditions which may then require a change in UE behaviour. The same can be said for the problem that has been described above i.e. receiving a TAI in the NSAG even though the TAI is part of the nonallowed area. It is an aim of embodiments of the present invention to address these and possibly other shortcomings, whether mentioned herein or not. According to the present invention there is provided an apparatus and method as set forth in the appended claims. Other features of the invention will be apparent from the dependent claims, and the description which follows. According to a first aspect of the invention, there is provided a method of performing access, RACH, in a User Equipment, UE, wherein a Non-Access Stratum, NAS, layer identifies a slice, S-NSSAI, for which an access attempt is made that corresponds to a Protocol Data Unit, PDU, session, for which the UE sends data in a CONTROL PLANE SERVICE REQUEST message or a UL NAS TRANSPORT message, and the NAS layer informs a lower layer of the identified slice. According to a second aspect of the invention, there is provided a method of performing access, RACH, in a User Equipment, UE, wherein no slice, S-NSSAI, information is provided by a Non-Access Stratum, NAS, layer to a lower layer if the access attempt is for one of the following: a) a deregistration procedure; b) UE-initiated NAS transport procedure for sending a Short Message, SMS; c) UE-initiated NAS transport procedure for sending LTE Positioning Protocol, LPP; d) UE-initiated NAS transport procedure for sending Steering of Roaming, SOR; e) UE-initiated NAS transport procedure for sending UE policy container; f) UE-initiated NAS transport procedure for sending UE parameters update transparent container; or g) UE-initiated NAS transport procedure for sending location services message. In an embodiment, no slice, S-NSSAI, information is provided either by an absence of information within a message or by a positive indication that no slice information is to be provided. In an embodiment, the UE is in 5GMM-IDLE mode or 5GMM-CONNECTED mode with RRC inactive indication. According to a third aspect of the invention, there is provided apparatus arranged to perform the method of any preceding aspect. Although a few preferred embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes and modifications might be made without departing from the scope of the invention, as defined in the appended claims. For a better understanding of the invention, and to show how embodiments of the same may be carried into effect, reference will now be made, by way of example only, to the accompanying diagrammatic drawings in which: Figure 1 shows a flowchart representation of an embodiment of the invention; and Figure 2 shows a flowchart representation of an embodiment of the invention. In a first embodiment, the UE verifies if the access attempt is for a service which is not related to a slice in order to determine if any S-NSSAI should be provided to the lower layers. When the UE is performing an access attempt for any reason which is not related to any slice (i.e. S-NSSAI) e.g. to send an SMS, location services message, LPP (LTE Positioning Protocol) message, then the UE should not provide any S-NSSAI to the lower layers i.e. the UE does not indicate any S-NSSAI for which the access attempt is being made in this case. The above is applicable for any of the following reasons for access attempt i.e. when the UE wants to send any one or combination of the following: SMS Location services message LPP an SOR transparent container UE policy container UE parameters update transparent container Service-level-AA container Multiple payloads Or any other container or IE which may be defined in the future and which is not related to any S-NSSAI (or which is not related with any PDU session that is in turn associated with an S-NSSAI) • NAS messages as listed in 3GPP TS 24.501 Optionally, the UE (e.g. the NAS) provides the S-NSSAI to the lower layers when it is performing an access attempt to send a service-level-AA container where the S-NSSAI is that which is associated with the PDU session which was used to transfer this information. In other words, if the service-level-AA container was exchanged between the UE and the network using the PDU session establishment procedure, or the PDU session modification procedure, then the UE (e.g. NAS) determines the S-NSSAI as the S-NSSAI associated with that PDU session when an access attempt is being made to send service-level-AA container and hence provides the S-NSSAI to the lower layers. Optionally, the UE (e.g. the NAS) provides an indication to the lower layers that UE is making an attempt for service / attempting to send a NAS message which is not related to any of the S-NSSAI for e.g. registration request message or deregistration request. In another option the UE-NAS can send at least one indication to the lower layers (when both the service / NAS message not related to signalling and data / service / NAS message related to signalling is pending): a) that UE is making an attempt for service / attempting to send a NAS message which is not related to any of the S-NSSAI; and b) that UE is making an attempt for service / attempting to send a NAS message which is related to at least one of the S-NSSAI and includes at least one of the Allowed S-NSSAI, Requested S-NSSAI, partially allowed S-NSSAI or partially rejected S-NSSAI However, an exception to the above is as follows: if the UE, in addition to the services listed above, also requires to request UP resources for at least one PDU session, then the UE will indicate the S-NSSAI for any of the PDU session for which UP resources is required (e.g. by virtue of requesting UP resources in the Uplink data status IE or Allowed PDU session status IE) and providing the S-NSSAI to the lower layers. The above should also apply for the case when the UE wants to deregister form the network i.e. when the UE performs an access attempt in order to send deregistration request message Note that all of the above applies for the case in which the UE is either in 5GMM-IDLE mode or in 5GMM-CONNECTED mode with RRC inactive indication. As an example, the following changes (shown as underlined text) may be made to the specifications to implement the proposals above: “The NS AG information provided by the network and stored in the UE includes a list of NSAGs each of which contains: a) an NSAG ID; b) a list of S-NSSAI(s), which are associated with the NSAG and shall be part of the configured NSSAi; c) a priority value that is associated with the NSAG; and d) optionally a list of TAIs in which the NSAG is valid. If it is not provided by the network, the NSAG is valid in the PLMN which has sent the NSAG information. The UE NAS layer shall provide the lower layers with. a) the most recent NSAG information stored in the UE (see subclause 4.6.2.2); b) the allowed NSSAI or the requested NSSAI for the purpose of network slicebased cell reselection (see 3GPP TS 23.501 [8]); and c) one or more S-NSSAIs related to an access attempt for the purpose of network slice-based random access, when the access attempt is made by the UE in 5GMM-IDLE mode or 5GMM-CONNECTED mode with RRC inactive indication, determined as follows: i) S-NSSAI(s) triggering the initial NAS message (requested NSSAI (if any) in case of the REGISTRATION REQUEST message and S-NSSAI(s) associated with all the PDU sessions included in the Uplink data status IE (if any), PDU session status IE (if any), or Allowed PDU session status IE (if any) in case of the (CONTROL PLANE) SERVICE REQUEST message), if an access attempt occurred due to an initial NAS message; ii) the S-NSSAI associated with the PDU session, if an access attempt occurred due to an uplink user data packet to be sent for a PDU session with suspended user-plane resources or an UL NAS TRANSPORT which carries a 5GSM message for a PDU session associated with an S-NSSAI (if any); or Hi) the allowed NSSAI (if any), if an access attempt occurred for other reason than those specified in bullets i) and ii) and the access attempt is not for sending any of the following: SMS, Location services message, LPP, an SOR transparent container, a UE policy container, a UE parameters update transparent container, and optionally a Service-level-AA container. Editor's note: It is FPS how a UE operates in terms of NSAG if the UE has an emergency PDU session or attempts to establish an emergency PDU session. NOTE: The AMF can take local configuration, UE 5GMM capabilities, subscribed S-NSSAIs, HPLMN, etc. to determine the NSAG priority information for the associated NSAG to a UE." In a second embodiment, the UE also provides an S-NSSAI to the lower layers if it is performing an access attempt to send data over NAS. The prior art standards description ignores the case in which the UE performs an access attempt to send data over NAS for CloT (Cellular Internet of Things). Therefore, when the UE wants to perform an access attempt for the purpose of sending data over NAS, then the UE (e.g. NAS) should determine the S-NSSAI for the access attempt as the S-NSSAI which is associated with the PDU session for which the data is being sent (or for which the data needs to be sent) and, as such, the NAS should provide the S-NSSAI to the lower layer which corresponds to this PDU session. It should be noted that this solution would apply for the case when the UE wants to send data over NAS using either the CONTROL PLANE SERVICE REQUEST message, or the UL NAS TRASNPORT message (where the Payload container type IE indicates “CloT user data container”). The details herein apply for the case when the UE is in 5GMM-IDLE mode (e.g. for the case of CONTROL PLANE SERVICE REQUEST) or in 5GMM-CONNECTED mode with RRC-inactive indication (e.g. for the case of UL NAS TRANSPORT). For example, the following changes (shown as underlined text) may be made to the specifications to implement the proposals above: “The NSAG information provided by the network and stored in the UE includes a list of NS AGs each of which contains: a) an NSAG ID; b) a list of S-NSSAI(s), which are associated with the NSAG and shall be part of the configured NSSAi; c) a priority value that is associated with the NSAG; and d) optionally a list of TAIs in which the NSAG is valid. If it is not provided by the network, the NSAG is valid in the PLMN which has sent the NSAG information. The UE NAS layer shall provide the lower layers with. a) the most recent NSAG information stored in the UE (see subclause 4.6.2.2); b) the allowed NSSAI or the requested NSSAI for the purpose of network slicebased cell reselection (see 3GPP TS 23.501 [8]); and c) one or more S-NSSAIs related to an access attempt for the purpose of network slice-based random access, when the access attempt is made by the UE in 5GMM-IDLE mode or 5GMM-C0NNECTED mode with RRC inactive indication, determined as follows: i) S-NSSAI(s) triggering the initial NAS message (requested NSSAI (if any) in case of the REGISTRATION REQUEST message and S-NSSAI(s) associated with all the PDU sessions included in the Uplink data status IE (if any), PDU session status IE (if any), or Allowed PDU session status IE (if any) in case of the (CONTROL PLANE) SERVICE REQUEST message), if an access attempt occurred due to an initial NAS message; ii) the S-NSSAI associated with the PDU session, if an access attempt occurred due to an uplink user data packet to be sent for a PDU session with suspended user-plane resources or an UL NAS TRANSPORT which carries a 5GSM message for a PDU session associated with an S-NSSAI (if any); or Hi) the S-NSSAI associated with the PDU session if an access attempt occurred for sending CloT user data in a CONTROL PLANE SERVICE REQUEST message or in an UL NAS TRANSPORT message iiiiv) the allowed NSSAI (if any), if an access attempt occurred for other reason than those specified in bullets i) and ii) and the access attempt is not for sending any of the following: SMS, Location services message, LPP, an SOR transparent container, a UE policy container, a UE parameters update transparent container, and optionally a Service-level-AA container. Editor's note: It is FPS how a UE operates in terms of NSAG if the UE has an emergency PDU session or attempts to establish an emergency PDU session. NOTE: The AMF can take local configuration, UE 5GMM capabilities, subscribed S-NSSAIs, HPLMN, etc. to determine the NSAG priority information for the associated NSAG to a UE." Note that the above applies when the UE wants to send CloT user data where this data may be sent inside any IE of the NAS message. For example, the CloT user data may be sent inside a CloT small data container, or inside the Payload container where optionally the Payload container type indicates “CloT user data container”. In a third embodiment, the UE removes any TAI from the NSAG information if the TAI is considered to be a non-allowed TAI. Here, the UE should verify if any of the TAIs in the NSAG is also present in the Service area list IE and is considered to be a non-allowed area, or the TAI is considered to be a nonallowed area even if the TAI is not part of the Service area list IE (e.g. where the TAIs in the IE are indicated as allowed TAI and hence any other TAI is considered to be a non-allowed TAI). If this is the case, i.e. if the UE detects that a TAI in the NSAG is considered to be part of a non-allowed area (or outside the allowed area), then the UE should remove the TAI from the NSAG information. Optionally the UE also removes the associated S-NSSAIs which correspond to this TAI. Alternatively, when the UE is inside any non-allowed area (or not inside an allowed area), the UE does not provide any S-NSSAI to the lower layers i.e. the UE determines that an access attempt in a non-allowed area (or outside of an allowed area) is not triggered by any S-NSSAI. Alternatively, in this case, the UE provides the requested NSSAI or the allowed NSSAI as the S-NSSAIs that triggered the access attempt. Alternatively, the UE can remove the TAIs from non-allowed area list and consider the TAIs as allowed TAIs when those are included as part of NSAG information. Yet another way of implementing this is to retain the TAIs in non-allowed area list but the UE can ignore the respective information and treat the TAIs as allowed TAIs. However, an exception to the above may be when the UE is considered to be a high priority access UE in which case it will determine the S-NSSAI for which the access attempt is being made according to the existing rules and hence provide the S-NSSAIs to the lower layers accordingly. For completeness, Figure 1 shows a first embodiment of the present invention. At S101, a Non-Access Stratum, NAS, layer identifies a slice, S-NSSAI, for which an access attempt is made that corresponds to a Protocol Data Unit, PDU, session, for which the UE sends data in a CONTROL PLANE SERVICE REQUEST message or a UL NAS TRANSPORT message. At S102, the NAS layer informs a lower layer of the identified slice. Figure 2 shows a second embodiment of the present invention. At S201, a determination is made whether one of the following access attempts is being made: a) a deregistration procedure; b) UE-initiated NAS transport procedure for sending a Short Message, SMS; c) UE-initiated NAS transport procedure for sending LTE Positioning Protocol, LPP; d) UE-initiated NAS transport procedure for sending Steering of Roaming, SOR; e) UE-initiated NAS transport procedure for sending UE policy container; f) UE-initiated NAS transport procedure for sending UE parameters update transparent container; or g) UE-initiated NAS transport procedure for sending location services message. At S202, no slice, S-NSSAI, information is provided by a Non-Access Stratum, NAS, layer to a lower layer. In the context of this embodiment, no slice, S-NSSAI, information is provided either by an absence of information within a message or by a positive indication that no slice information is to be provided. At least some of the example embodiments described herein may be constructed, partially or wholly, using dedicated special-purpose hardware. Terms such as ‘component’, ‘module’ or ‘unit’ used herein may include, but are not limited to, a hardware device, such as circuitry in the form of discrete or integrated components, a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), which performs certain tasks or provides the associated functionality. In some embodiments, the described elements may be configured to reside on a tangible, persistent, addressable storage medium and may be configured to execute on one or more processors. These functional elements may in some embodiments include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Although the example embodiments have been described with reference to the components, modules and units discussed herein, such functional elements may be combined into fewer elements or separated into additional elements. Various combinations of optional features have been described herein, and it will be appreciated that described features may be combined in any suitable combination. In particular, the features of any one example embodiment may be combined with features of any other embodiment, as appropriate, except where such combinations are mutually exclusive. Throughout this specification, the term “comprising” or “comprises” means including the component(s) specified but not to the exclusion of the presence of others. Attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and / or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and / or steps are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features. The invention is not restricted to the details of the foregoing embodiment(s). The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed. 10 15

Claims

1. A method of performing access, RACH, in a User Equipment, UE, wherein no slice, S-NSSAI, information is provided by a Non-Access Stratum, NAS, layer to a lower layer if the access attempt is for one of the following, wherein the UE is in 5GMM-CONNECTED mode with RRC inactive indication, and wherein the no slice, S-NSSAI, information is provided either by an absence of information within a message or by a positive indication that no slice information is to be provided:a) a deregistration procedure;b) UE-initiated NAS transport procedure for sending a Short Message, SMS;c) UE-initiated NAS transport procedure for sending LTE Positioning Protocol, LPP;d) UE-initiated NAS transport procedure for sending Steering of Roaming, SOR;e) UE-initiated NAS transport procedure for sending UE policy container;f) UE-initiated NAS transport procedure for sending UE parameters update transparentcontainer; org) UE-initiated NAS transport procedure for sending location services message.2.Apparatus arranged to perform the method of any preceding claim.

Citation Information

Patent Citations

  • ViewWO2022031805A1onEspacenetopensinnewtab

  • ViewWO2022082758A1onEspacenetopensinnewtab