Method and apparatus for handling emergency services in a private network

Abstract

Methods, apparatuses, and computer program products for handling session requests for emergency services are provided. Updated closed access group (CAG) configuration information can be provided to a user equipment (UE) requesting an emergency session with a public land mobile network (PLMN), and the UE can update its CAG information or abort its session request. When the PLMN determines that a session request by the UE to the PLMN is sent via a non-CAG cell, the PLMN can determine whether the session request is for emergency services, in which case the PLMN can decide not to clear or reject the session request, while if the PLMN determines that the session request via the non-CAG cell is for non-emergency services, the PLMN can clear or reject the session request. When the session request is rejected by the PLMN, the UE can enter a logged out state and search for a new PLMN.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority to and the benefit of U.S. Provisional Application Serial No. 62 / 972,912, entitled “METHOD, APPARATUS, AND COMPUTER PROGRAM PRODUCT FOR HANDLING EMERGENCY SERVICES IN A PRIVATE NETWORK” filed February 11, 2020, the entire disclosure of which is hereby incorporated by reference in its entirety for all purposes. TECHNICAL FIELD

[0003] Example embodiments relate generally to managing communications in a communication system, and more particularly to handling emergency services in a private network. BACKGROUND

[0004] A communication system can typically operate as a facility that enables communication sessions between two or more entities, such as user terminals, base stations / access points, and / or other nodes, by providing carriers between the various entities involved in the communication path. The communication system can be provided, for example, by means of a communication network and one or more compatible communication devices. The communication sessions can comprise communication for carrying data, such as speech, electronic mail (email), text message, multimedia and / or content data, etc. Non-limiting examples of services offered can comprise two-way or multi-way calling, data communication or multimedia services, as well as access to a data network system, such as the Internet. In a wireless communication system, at least a portion of the communication sessions between at least two stations occur on wireless links.

[0005] A user can access the communication system by means of a suitable communication device or terminal. The communication device of a user is often referred to as user equipment (UE) or user equipment. The communication device is provided with appropriate signal receiving and transmitting means for enabling communication, such as enabling access to a communication network or direct communication with other users. The communication device can access and transmit and / or receive communication on carriers provided by stations or access points.

[0006] The communication system and the associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are allowed to do and how that should be implemented. Communication protocols and / or parameters which shall be used for the connections are also typically defined. SUMMARY

[0007] Described herein are methods, apparatuses, and computer program products for handling emergency services in a private network, provided in accordance with example embodiments. In some embodiments, a method can include receiving, at a user equipment (UE) from a network entity of a current public land mobile network (PLMN), a configuration update command message including an updated closed access group (CAG) information list; and performing, by the UE, a local release of all protocol data unit (PDU) sessions except an emergency PDU session if an entry for the PLMN in the received CAG information list includes an indication that the UE is only allowed to access the PLMN via a CAG cell and a list of allowed CAGs for the PLMN in the received CAG information list does not include any CAG identity (CAG-ID).

[0008] In some embodiments, the configuration update command message can include one or more of a fifth generation global unique temporary identity (5G-GUTI), a tracking area identity (TAI) list, one or more allowed network slice selection assistance information (NSSAI), one or more mapped single NSSAI, local data network (LADN) information, a service area list, a mobile initiated connection only (MICO) indication, network identity and time zone (NITZ) information, one or more configured NSSAI, one or more rejected NSSAI, a network slice subscription change indication, one or more operator defined access category definitions, a short message service (SMS) indication, an inter-service gap time value, a UE radio capability identity, a 5G system registration result, or a UE radio capability identity deletion indication.

[0009] In some embodiments, the configuration update command message can include a configuration update indication information element including a registration request bit set to indicate that registration is requested.

[0010] In some embodiments, the method can further include sending, from the UE to or toward the network entity of the current PLMN, a PDU session request.

[0011] In some embodiments, an apparatus can include at least one processor, and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receiving, at a user equipment (UE), a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list; performing, by the UE, a local release of all protocol data unit (PDU) sessions except for emergency PDU sessions if an entry for the PLMN in the received CAG information list includes an indication that the UE is only allowed to access the PLMN via a CAG cell and an allowed CAG list for the PLMN in the received CAG information list does not include any CAG identity (CAG-ID).

[0012] In some embodiments, the configuration update command message can include one or more of a fifth generation global unique temporary identity (5G-GUTI), a tracking area identity (TAI) list, one or more allowed network slice selection assistance information (NSSAI), one or more mapped single NSSAI, local data network (LADN) information, a service area list, a mobile initiated connection only (MICO) indication, network identity and time zone (NITZ) information, one or more configured NSSAI, one or more rejected NSSAI, a network slice subscription change indication, one or more operator defined access category definitions, a short message service (SMS) indication, an inter-service gap time value, a UE radio capability identity, a 5G system registration result, or a UE radio capability identity deletion indication.

[0013] In some embodiments, the configuration update command message can include a configuration update indication information element, the configuration update indication information element including a registration request bit, the registration request bit set to indicate that registration is requested.

[0014] In some embodiments, the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform: sending a PDU session request to or towards a network entity of the current PLMN.

[0015] In some embodiments, an apparatus can include means, such as a processor or processing circuitry and a memory storing computer program code, for receiving, from a network entity of a current public land mobile network (PLMN), a configuration update command message, the configuration update command message including an updated closed access group (CAG) information list; and means for performing, if an entry for the PLMN in the received CAG information list includes an indication that the UE is only allowed to access the PLMN via CAG cells and an allowed CAG list for the PLMN in the received CAG information list does not include any CAG-IDs, a local release of all protocol data unit (PDU) sessions except emergency PDU sessions.

[0016] In some embodiments, the configuration update command message can include one or more of a fifth generation global unique temporary identity (5G-GUTI), a tracking area identity (TAI) list, one or more allowed network slice selection assistance information (NSSAI), one or more mapped single NSSAI, local data network (LADN) information, a service area list, a mobile initiated connection only (MICO) indication, network identity and time zone (NITZ) information, one or more configured NSSAI, one or more rejected NSSAI, a network slice subscription change indication, one or more operator defined access class definitions, a short message service (SMS) indication, an inter-service gap time value, a UE radio capability identity, a 5G system registration result, or a UE radio capability identity deletion indication.

[0017] In some embodiments, the configuration update command message can include a configuration update indication information element, the configuration update indication information element including a registration request bit, the registration request bit set to indicate that registration is requested.

[0018] In some embodiments, the apparatus can further include means for sending, from the apparatus, a PDU session request to or toward a network entity of the current PLMN.

[0019] In some embodiments, a computer program product can include a non-transitory computer readable medium comprising computer instructions stored thereon for performing at least the following: receiving, at a user equipment (UE) from a network entity of a current public land mobile network (PLMN), a configuration update command message, the configuration update command message including an updated closed access group (CAG) information list; performing, by the UE, a local release of all protocol data unit (PDU) sessions except emergency PDU sessions if an entry for the PLMN in the received CAG information list includes an indication that the UE is only allowed to access the PLMN via CAG cells and an allowed CAG list for the PLMN in the received CAG information list does not include any CAG-IDs.

[0020] In some embodiments, the configuration update command message can include one or more of a fifth generation globally unique temporary identity (5G-GUTI), a tracking area identity (TAI) list, one or more allowed network slice selection assistance information (NSSAI), one or more mapped single NSSAI, local data network (LADN) information, a service area list, a mobile initiated connection only (MICO) indication, network identity and time zone (NITZ) information, one or more configured NSSAI, one or more rejected NSSAI, a network slice subscription change indication, one or more operator-defined access category definitions, a short message service (SMS) indication, an inter-service gap time value, a UE radio capability identity, a 5G system registration result, or a UE radio capability identity deletion indication.

[0021] In some embodiments, the configuration update command message can include a configuration update indication information element, the configuration update indication information element including a registration request bit set to indicate that registration is requested.

[0022] In some embodiments, the non-transitory computer-readable medium can further include computer instructions stored thereon to perform at least the following operations: sending, from the UE, a PDU session request to or toward a network entity of the current PLMN.

[0023] In some embodiments, a method can include receiving, at a mobility management sublayer of a user equipment, a downlink non-access stratum (NAS) transport message from a network entity of a public land mobile network (PLMN), the downlink NAS transport message including a message requesting session management and a cause value indicating that the UE is not authorized to make the request due to CAG constraints; sending, from the mobility management sublayer of the user equipment, the message requesting session management and an indication that the message requesting session management is not forwarded due to CAG to a session management sublayer of the user equipment; and upon receiving, at the session management sublayer of the user equipment, the message requesting session management and the indication that the message requesting session management is not forwarded due to CAG, stopping a timer associated with the session management request and aborting a procedure for session management.

[0024] In some embodiments, an apparatus can comprise at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receiving, at a mobility management sublayer of a user equipment, a downlink non-access stratum (NAS) transport message from a network entity of a public land mobile network (PLMN), the downlink NAS transport message comprising a message requesting session management and a cause value indicating that the UE is not authorized to make the request due to CAG constraints; sending, from the mobility management sublayer of the user equipment, to a session management sublayer of the user equipment, the message requesting session management together with an indication that the message requesting session management is not forwarded due to CAG; and upon receiving, at the session management sublayer of the user equipment, the indication that the message requesting session management is not forwarded due to CAG together with the message requesting session management, stopping a timer associated with the session management request and aborting a procedure for session management.

[0025] In some embodiments, an apparatus can comprise means, such as a processor or processing circuitry and a memory storing computer program code, for receiving, at a mobility management sublayer of a user equipment, a downlink non-access stratum (NAS) transport message from a network entity of a public land mobile network (PLMN), the downlink NAS transport message comprising a message requesting session management and a cause value indicating that the UE is not authorized to make the request due to CAG constraints; means for sending, from the mobility management sublayer of the user equipment, to a session management sublayer of the user equipment, the message requesting session management together with an indication that the message requesting session management is not forwarded due to CAG; and means for, upon receiving, at the session management sublayer of the user equipment, the indication that the message requesting session management is not forwarded due to CAG together with the message requesting session management, stopping a timer associated with the session management request and aborting a procedure for session management.

[0026] In some embodiments, a computer program product can comprise a non-transitory computer readable medium comprising computer instructions stored thereon for performing at least the following: receiving, at a mobility management sublayer of a user equipment, a downlink non-access stratum (NAS) transport message from a network entity of a public land mobile network (PLMN), the downlink NAS transport message comprising a message requesting session management and a cause value indicating that the UE is not authorized to make the request due to CAG constraints; sending, from the mobility management sublayer of the user equipment, to a session management sublayer of the user equipment, the message requesting session management together with an indication that the message requesting session management is not forwarded due to CAG; and upon receiving, at the session management sublayer of the user equipment, the indication that the message requesting session management is not forwarded due to CAG together with the message requesting session management, stopping a timer associated with the session management request and aborting a procedure for session management.

[0027] In some embodiments, a method can include receiving, at a user equipment, a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list; in an instance in which the configuration update command message is received via a CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency protocol data unit (PDU) session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list; in an instance in which the configuration update command message is received via a CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the current PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session.

[0028] In some embodiments, the method can further include, in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency PDU session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list.

[0029] In some embodiments, the method can further include, in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session.

[0030] In some embodiments, an apparatus can be provided that includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receiving, at a user equipment, a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list; in an instance in which the configuration update command message is received via a particular CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency protocol data unit (PDU) session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list; in an instance in which the configuration update command message is received via a particular CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the current PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session.

[0031] In some embodiments, the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform: in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency PDU session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list.

[0032] In some embodiments, the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform, in an instance in which the configuration update command message is received via a non-CAG cell, the entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access PLMN CAG cells, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session.

[0033] In some embodiments, an apparatus can be provided that comprises means, such as a processor or processing circuitry and a memory storing computer program code, for receiving, at a user equipment, a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message comprising an updated closed access group (CAG) information list; means for entering, in an instance in which the configuration update command message is received via a specific CAG cell, the entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the PLMN via CAG cells, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency protocol data unit (PDU) session with the current PLMN, a deregistered PLMN search state, and applying a PLMN selection procedure based on the updated CAG information list; means for performing, in an instance in which the configuration update command message is received via a specific CAG cell, the entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the current PLMN via CAG cells, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, a local release of all PDU sessions except the emergency PDU session.

[0034] In some embodiments, the apparatus can further comprise means for entering, in an instance in which the configuration update command message is received via a non-CAG cell, the entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access PLMN CAG cells, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency PDU session with the current PLMN, a deregistered PLMN search state, and applying a PLMN selection procedure based on the updated CAG information list.

[0035] In some embodiments, the apparatus can further include means for performing a local release of all PDU sessions except an emergency PDU session in an instance in which the configuration update command message is received via a non-CAG cell, an entry for a current PLMN in the CAG information list includes an indication that the UE is only allowed to access PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN.

[0036] In some embodiments, a computer program product can be provided that includes a non-transitory computer readable medium including computer instructions stored thereon for performing at least the following: receiving, at a user equipment, a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list; entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list in an instance in which the configuration update command message is received via a specific CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency protocol data unit (PDU) session with the current PLMN; and performing a local release of all PDU sessions except the emergency PDU session in an instance in which the configuration update command message is received via the specific CAG cell, the entry for the current PLMN in the CAG information list includes the indication that the user equipment is only allowed to access the current PLMN via CAG cells, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established the emergency PDU session with the current PLMN.

[0037] In some embodiments, the non-transitory computer readable medium can further include computer instructions stored thereon for performing at least the following in an instance in which the configuration update command message is received via a non-CAG cell, an entry for a current PLMN in the CAG information list includes an indication that the UE is only allowed to access PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency PDU session with the current PLMN: entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list.

[0038] In some embodiments, the non-transitory computer-readable medium can further include computer instructions stored thereon for, in an instance in which the session request message includes an initial emergency session request, the entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access CAG cells of the PLMN, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing at least the following: performing a local release of all PDU sessions except the emergency PDU session.

[0039] According to another embodiment, a method can be performed that includes receiving, from a user equipment, a session request message to establish a session with a public land mobile network, in an instance in which the session request message includes an initial emergency session request, sending a session accept message to the user equipment, in an instance in which the session request message does not include an initial emergency session request, determining a cell type through which the session request message was issued, and determining whether the user equipment is allowed to establish a session with the public land mobile network through the determined cell type, and in an instance in which the user equipment is not allowed to establish a session with the public land mobile network through the determined cell type, sending a session reject message to the user equipment.

[0040] In some embodiments, the method can further include, in an instance in which the session request message does not include an initial emergency session request, the session request is issued through a closed access group cell, and a selected closed access group cell identification in the session request message is not included in an allowed closed access group list for the public land mobile network, sending a session reject message to the user equipment.

[0041] In some embodiments, the method can further include, in an instance in which the session request message does not include an initial emergency session request, the session request is issued through a non-closed access group cell, and an entry of a closed access group information list for the public land mobile network includes an indication that the user equipment is only allowed to access the public land mobile network through closed access group cells, sending a session reject message to the user equipment.

[0042] According to another embodiment, an apparatus can be provided that comprises: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: receive, from a user equipment, a session request message to establish a session with a public land mobile network; in an instance in which the session request message comprises an initial emergency session request, send, to the user equipment, a session accept message; in an instance in which the session request message does not comprise an initial emergency session request, determine a cell type through which the session request message was issued, and determine whether the user equipment is allowed to establish a session with the public land mobile network through the determined cell type; and in an instance in which the user equipment is not allowed to establish a session with the public land mobile network through the determined cell type, send, to the user equipment, a session reject message.

[0043] In some embodiments, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: in an instance in which the session request message does not comprise an initial emergency session request, the session request is issued through a closed access group cell, and a selected closed access group cell identity in the session request message is not included in an allowed closed access group list for the public land mobile network, send, to the user equipment, a session reject message.

[0044] In some embodiments, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: in an instance in which the session request message does not comprise an initial emergency session request, the session request is issued through a non-closed access group cell, and an entry of a closed access group information list for the public land mobile network comprises an indication that the user equipment is only allowed to access the public land mobile network through a closed access group cell, send, to the user equipment, a session reject message.

[0045] According to another embodiment, an apparatus can be provided that comprises: means, such as a processor or processing circuitry and a memory storing computer program code, for receiving, from a user equipment, a session request message to establish a session with a public land mobile network; means for, in an instance in which the session request message comprises an initial emergency session request, sending, to the user equipment, a session accept message; means for, in an instance in which the session request message does not comprise an initial emergency session request, determining a cell type through which the session request message was issued and determining whether the user equipment is allowed to establish a session with the public land mobile network through the determined cell type; and means for, in an instance in which the user equipment is not allowed to establish a session with the public land mobile network through the determined cell type, sending, to the user equipment, a session reject message.

[0046] In some embodiments, the apparatus can further include means for sending a session reject message to the user equipment in instances in which the session request message does not include an initial emergency session request, the session request is made through a closed access group cell, and the selected closed access group cell identity in the session request message is not included in an allowed closed access group list for the public land mobile network.

[0047] In some embodiments, the apparatus can further include means for sending a session reject message to the user equipment in instances in which the session request message does not include an initial emergency session request, the session request is made through a non-closed access group cell, and an entry of a closed access group information list for the public land mobile network includes an indication that the user equipment is only allowed to access the public land mobile network through a closed access group cell.

[0048] According to another embodiment, a computer program product can be provided that includes a non-transitory computer readable medium including computer instructions stored therein for performing at least the following operations: receiving a session request message from a user equipment establishing a session with a public land mobile network; in instances in which the session request message includes an initial emergency session request, sending a session accept message to the user equipment; in instances in which the session request message does not include an initial emergency session request, determining a cell type through which the session request message was made, and determining whether the user equipment is allowed to establish a session with the public land mobile network through the determined cell type; and in instances in which the user equipment is not allowed to establish a session with the public land mobile network through the determined cell type, sending a session reject message to the user equipment.

[0049] In some embodiments, the non-transitory computer readable medium can further include computer instructions stored thereon for performing at least the following operation: sending a session reject message to the user equipment in instances in which the session request message does not include an initial emergency session request, the session request is made through a closed access group cell, and the selected closed access group cell identity in the session request message is not included in an allowed closed access group list for the public land mobile network.

[0050] In some embodiments, the non-transitory computer readable medium can further include computer instructions stored thereon for performing at least the following operation: sending a session reject message to the user equipment in instances in which the session request message does not include an initial emergency session request, the session request is made through a non-closed access group cell, and an entry of a closed access group information list for the public land mobile network includes an indication that the user equipment is only allowed to access the public land mobile network through a closed access group cell.

[0051] In some embodiments, a method can be provided that comprises receiving, from a user equipment, a session request message for a public land mobile network; in instances in which the session request message includes an initial emergency session request, sending a session accept message to the user equipment; in instances in which the session request message does not include an initial emergency session request, the session request is made through a closed access group cell, and a selected closed access group cell identity in the session request message is not included in an allowed closed access group list for the public land mobile network, sending a session reject message to the user equipment; and in instances in which the session request message does not include an initial emergency session request, the session request is made through a non-closed access group cell, and an entry of a closed access group information list for the public land mobile network includes an indication that the user equipment is only allowed to access the public land mobile network through closed access group cells, sending a session reject message to the user equipment.

[0052] In some embodiments, an apparatus can be provided that comprises at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to receive, from a user equipment, a session request message for a public land mobile network; in instances in which the session request message includes an initial emergency session request, send a session accept message to the user equipment; in instances in which the session request message does not include an initial emergency session request, the session request is made through a closed access group cell, and a selected closed access group cell identity in the session request message is not included in an allowed closed access group list for the public land mobile network, send a session reject message to the user equipment; and in instances in which the session request message does not include an initial emergency session request, the session request is made through a non-closed access group cell, and an entry of a closed access group information list for the public land mobile network includes an indication that the user equipment is only allowed to access the public land mobile network through closed access group cells, send a session reject message to the user equipment.

[0053] In some embodiments, an apparatus can be provided that comprises means, such as a processor or processing circuitry and a memory storing computer program code, for receiving, from a user equipment, a session request message for a public land mobile network; means, such as a processor or processing circuitry and a memory storing computer program code, for sending, in an instance in which the session request message includes an initial emergency session request, a session accept message to the user equipment; means, such as a processor or processing circuitry and a memory storing computer program code, for sending, in an instance in which the session request message does not include an initial emergency session request, the session request is made through a closed access group cell, and a selected closed access group cell identity in the session request message is not included in an allowed closed access group list for the public land mobile network, a session reject message to the user equipment; and means, such as a processor or processing circuitry and a memory storing computer program code, for sending, in an instance in which the session request message does not include an initial emergency session request, the session request is made through a non-closed access group cell, and an entry of a closed access group information list for the public land mobile network includes an indication that the user equipment is only allowed to access the public land mobile network through closed access group cells, a session reject message to the user equipment.

[0054] In some embodiments, a computer program product can be provided that comprises a non-transitory computer readable medium comprising computer instructions stored thereon for performing at least the following: receiving, from a user equipment, a session request message for a public land mobile network; sending, in an instance in which the session request message includes an initial emergency session request, a session accept message to the user equipment; sending, in an instance in which the session request message does not include an initial emergency session request, the session request is made through a closed access group cell, and a selected closed access group cell identity in the session request message is not included in an allowed closed access group list for the public land mobile network, a session reject message to the user equipment; and sending, in an instance in which the session request message does not include an initial emergency session request, the session request is made through a non-closed access group cell, and an entry of a closed access group information list for the public land mobile network includes an indication that the user equipment is only allowed to access the public land mobile network through closed access group cells, a session reject message to the user equipment.

[0055] In some embodiments, a method can be provided that comprises receiving, at a mobility management sublayer of a user equipment, a session reject message from a network entity of a public land mobile network (PLMN) including an indication that a session request received from the user equipment was not forwarded due to an updated closed access group (CAG) requirement; sending, from the mobility management sublayer of the user equipment, an indication to the session management sublayer of the user equipment that the session request was rejected by the PLMN due to the updated CAG requirement; and upon receiving, at the session management sublayer of the user equipment, the indication that the session request was rejected by the PLMN due to the updated CAG requirement, stopping a timer associated with the session request and aborting the session request.

[0056] In some embodiments, an apparatus can be provided that comprises at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receiving, at a mobility management sublayer of a user equipment, a session reject message from a network entity of a public land mobile network (PLMN) comprising an indication that a session request received from the user equipment was not forwarded due to an updated closed access group (CAG) requirement; sending, from the mobility management sublayer of the user equipment, an indication to a session management sublayer of the user equipment that the session request was rejected by the PLMN due to the updated CAG requirement; and upon receiving, at the session management sublayer of the user equipment, the indication that the session request was rejected by the PLMN due to the updated CAG requirement, stopping a timer associated with the session request and aborting the session request.

[0057] In some embodiments, an apparatus can be provided that comprises: means, such as a processor or processing circuitry and a memory storing computer program code, for receiving, at a mobility management sublayer of a user equipment, a session reject message from a network entity of a public land mobile network (PLMN) comprising an indication that a session request received from the user equipment was not forwarded due to an updated closed access group (CAG) requirement; means for sending, from the mobility management sublayer of the user equipment, an indication to a session management sublayer of the user equipment that the session request was rejected by the PLMN due to the updated CAG requirement; and means for, upon receiving, at the session management sublayer of the user equipment, the indication that the session request was rejected by the PLMN due to the updated CAG requirement, stopping a timer associated with the session request and aborting the session request.

[0058] In some embodiments, a computer program product can be provided that comprises a non-transitory computer readable medium comprising computer instructions stored thereon for performing at least the following: receiving, at a mobility management sublayer of a user equipment, a session reject message from a network entity of a public land mobile network (PLMN) comprising an indication that a session request received from the user equipment was not forwarded due to an updated closed access group (CAG) requirement; sending, from the mobility management sublayer of the user equipment, an indication to a session management sublayer of the user equipment that the session request was rejected by the PLMN due to the updated CAG requirement; and upon receiving, at the session management sublayer of the user equipment, the indication that the session request was rejected by the PLMN due to the updated CAG requirement, stopping a timer associated with the session request and aborting the session request.

[0059] Various further aspects are described in the detailed description and the appended claims below. BRIEF DESCRIPTION OF DRAWINGS

[0060] Having generally described an embodiment of the present disclosure, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0061] Figure 1 illustrates an exemplary architecture for a communication network according to an embodiment;

[0062] Figure 2 illustrates an exemplary architecture for a communication network according to an embodiment;

[0063] Figure 3 illustrates an exemplary architecture for a communication network according to an embodiment;

[0064] Figure 4 illustrates an exemplary computing device for handling emergency services in a private network according to an embodiment;

[0065] Figure 5 illustrates an exemplary computing device for handling emergency services in a private network according to an embodiment;

[0066] Figure 6A illustrates exemplary messaging between a user equipment and a network entity for handling emergency services in a private network according to an embodiment;

[0067] Figure 6B illustrates exemplary messaging between a user equipment and a network entity for handling emergency services in a private network according to an embodiment;

[0068] Figure 7 illustrates exemplary messaging between a user equipment and a network entity for handling emergency services in a private network according to an embodiment;

[0069] Figure 8 is a flowchart illustrating operations for handling emergency services in a private network according to an embodiment, for example, as performed by an apparatus of Figure 4 or Figure 5

[0070] Figure 9 is a flowchart illustrating operations for handling emergency services in a private network according to another embodiment, for example, as performed by an apparatus of Figure 4 or Figure 5

[0071] Figure 10 is a flowchart illustrating operations for handling emergency services in a private network according to a further embodiment, for example, as performed by an apparatus of Figure 4 or Figure 5

[0072] ​​​Figure 11 is a flowchart illustrating operations for handling emergency services in a private network, performed, for example, by an apparatus of Figure 4 or Figure 5

[0073] Figure 12 is a flowchart illustrating operations for handling emergency services in a private network, performed, for example, by an apparatus of Figure 4 or Figure 5 DETAILED DESCRIPTION

[0074] Some embodiments of the application will now be described, by way of example, with reference to the appended drawings. The drawings show some but not all embodiments of the application. In fact, the application can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. As used herein, the terms "data," "content," "information," and similar terms can be used interchangeably to refer to the data being sent, received, and / or stored according to embodiments of the present application. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present application.

[0075] Also, as used herein, the term "circuitry" refers to (a) hardware-only circuitry (e.g., implementations in analog circuitry and / or digital circuitry); (b) combinations of circuits and one or more computer program products incorporating software and / or firmware instructions that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits that require software or firmware for operation but have not yet been provided with such software or firmware. Such a definition of "circuitry" applies to all uses of this term in this document, including in any claims. As a further example, as used herein, the term "circuitry" also includes an implementation that has a processor and / or one or more portions of its software and / or firmware that are dedicated to one or more of the functions described herein, and that are not shared with other functions. As another example, as used herein, the term "circuitry" also includes an implementation that has a processor and / or one or more portions of its software and / or firmware that are dedicated to one or more of the functions described herein, and that are shared with other functions. As yet another example, as used herein, the term "circuitry" also includes an implementation that has a processor and / or one or more portions of its software and / or firmware that are dedicated to one or more of the functions described herein, and that are shared with other functions, as long as the shared hardware for which the function is dedicated is not shared with other functions. As yet another example, as used herein, the term "circuitry" also includes an implementation that has a processor and one or more memory and / or other storage devices and / or storage media and / or other interface circuits and computer readable storage media incorporating a computer program, software, and / or firmware instructions that work together to cause an apparatus to perform one or more functions described herein and / or to cause an apparatus to behave in manner that is not shared with other functions.

[0076] ​​As defined herein, a "computer-readable storage medium" is a non-transitory physical storage medium (e.g., volatile or non-volatile memory device) that can be read by a computer. Thus, a computer-readable storage medium does not inherently communicate to other computers or equipment. A "computer-readable transmission medium" is a computer-readable storage medium that communicates programs, data structures, objects or other computer-readable information over some transmission medium to compute equipment. Such a medium can take many forms, including but not limited to, non-transitory computer-readable storage medium (e.g., non-volatile media, volatile media), and transmission media. Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and carrier waves transmitted over the internet without a wire or cable, such as sound or photos. Signals include the analog or digital information-bearing portions of the carrier waves. Examples of non-transitory computer-readable media include a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic medium, magneto-optical medium, a compact disc read-only memory (CD-ROM), any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a FLASH-EPROM, or any other memory chip or cartridge, or any other non-transitory medium from which a computer can read. The term computer-readable storage medium is used herein to refer to any computer-readable medium except transmission media. However, it should be understood that where embodiments are described to use a computer-readable storage medium, other types of computer-readable media which are

[0077] While various inventive embodiments have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and / or structures for performing the functions and / or obtaining the results and / or one or more of the advantages described herein, and each of such variations and / or modifications is deemed to be within the scope of the inventive embodiments described herein. More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and / or configurations will depend upon the specific application or applications for which a inventive embodiment is used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific inventive embodiments described herein. It is, therefore, to be understood that the foregoing embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, inventive embodiments can be practiced otherwise than as specifically described and claimed. Inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and / or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and / or methods, if such features, systems, articles, materials, kits, and / or methods are not mutually inconsistent, is included within the inventive scope of the present disclosure.

[0078] In the following, certain embodiments are explained with reference to mobile communication devices capable of communicating via a wireless cellular system and a mobile communication system serving such mobile communication devices. Before explaining the example embodiments in detail, it is to be understood that the technology described as examples is not limited in this regard to any particular implementation, as described in the detailed description. Examples of technology that can be employed in accordance with various embodiments now will be described with reference to the accompanying drawings. Figures 1 to 3 Some general principles of wireless communication systems, their access systems and mobile communication devices are briefly explained to help understanding the technology underlying the described examples.

[0079] According to some embodiments, a communication device or terminal can be provided for wireless access via a cell, a base station or a similar wireless transmitter and / or receiver node providing an access point for a radio access system.

[0080] An access point and communication by it is typically controlled by at least one appropriate controller arrangement to enable operation and management of mobile communication devices communicating therewith. In some embodiments, a control arrangement for a node can be integrated with, coupled to and / or otherwise provided for controlling an access point. In some embodiments, the control arrangement can be arranged to allow communication between a user equipment and a core network or a network entity of a core network. To this end, the control arrangement can comprise at least one memory, at least one data processing unit, e.g. a processor, and an input / output interface. Via the interface, the control arrangement can be coupled to relevant other components of the access point. The control arrangement can be configured to execute appropriate software code to provide the control functionality. It will be appreciated that similar components can be provided in a control arrangement that can be provided elsewhere in the network system, e.g. in a core network entity. The control arrangement can be interconnected with other control entities. The control arrangement and functionality can be distributed among several control units. In some embodiments, each base station can comprise a control arrangement. In alternative embodiments, two or more base stations can share a control arrangement.

[0081] An access point and associated controllers can communicate with each other via fixed line connections and / or via a radio interface. Logical connections between base station nodes can be provided, e.g. by means of an X2 or similar interface. The interface can be used, e.g., to coordinate operation of stations and to perform reselection or handover operations.

[0082] A communication device or user equipment can comprise any suitable device that is capable of receiving data wirelessly. For example, the device can be a handheld data processing device, equipped with a radio receiver, data processing and user interface means. Non-limiting examples include a mobile station (MS) such as a mobile phone or so-called "smartphone", a portable computer such as a laptop or tablet computer equipped with a wireless interface card or other wireless interface facility, a personal data assistant (PDA) provided with wireless communication capabilities, or any combination of these or the like. Other examples include wearable wireless devices such as devices integrated with watches or smartwatches, glasses, headgear, hats, clothing, earpieces with wireless connectivity, jewelry, and the like, a universal serial bus (USB) memory stick with wireless functionality, a modem data card, a machine type device, or any combination of these or similar devices.

[0083] In some embodiments, a communication device, e.g. configured for communication with a wireless network or core network entity, can be exemplified by a handheld or other mobile communication device (or user equipment, UE). A mobile communication device can be provided with wireless communication capabilities and appropriate electronic control means to enable it to operate. Thus, the communication device can be provided with at least one data processing entity, e.g. a central processing unit and / or core processor, at least one memory and other possible components, such as additional processors and memories for software and hardware aided execution of tasks that the device is intended to perform. The data processing, storage and other relevant control means can be provided on an appropriate circuit board and / or in chipsets. The data processing and storage functionality provided by the control means of the communication device is configured to cause the control and signaling operations in accordance with certain embodiments described later in this specification. The user can control the operation of the communication device by means of a suitable user interface, such as a touch-sensitive display or a keypad and / or keyboard, one of a number of actuator buttons, voice commands, combinations of these or the like. A speaker and a microphone are also typically provided. Furthermore, the mobile communication device can comprise appropriate connectors (either wired or wireless) to other devices and / or for connecting external accessories, such as headsets.

[0084] In some embodiments, the communication device can communicate wirelessly via appropriate means for receiving and transmitting signals. In some embodiments, a radio part can be connected to the control means of the device. The radio part can comprise a radio section and an associated antenna arrangement. The antenna arrangement can be arranged internally or externally to the communication device.

[0085] Figures 1 to 3Various exemplary architectures of a communication network 100 are illustrated in which various methods, apparatus, and computer program products can be implemented and / or used. In some embodiments, the communication network 100 can include any suitable configuration, number, orientation, positioning, and / or size of components and special-purpose equipment configured to provide over-the-air interface (e.g., New Radio (NR)) communication or connectivity between a user equipment 102 (UE 102) and a data network 116 (DN 116) via a core network 101 (CN 101) of the communication network 100. As Figure 1 As shown in the middle, a communication network 100 can be provided in which a UE 102 is operable to communicate with an AN 104, e.g., by means of a transmitting tower, base station, network node, etc. In some embodiments, the AN 104 can be in communication with the CN 101 or components or entities thereof. In some embodiments, the CN 101 can facilitate communication between the UE 102 and the DN 116, e.g., for sending data, messages, requests, etc. In some embodiments, the DN 116 or the CN 101 can be in communication with an application server or application function 112 (AS / AF 112).

[0086] In the context of fifth generation (5G) networks, for example Figure 2 and Figure 3As shown, the communication network 100 can include a series of connected network devices and dedicated hardware distributed across a service area or country, as well as one or more network entities, which can be stored at and / or hosted by one or more connected network devices or dedicated hardware. In some embodiments, the UE 102 can connect to the AN 104, which can then relay communications between the UE 102 and the CN 101, which connects to the DN 116, which can communicate with one or more AS / AFs 112. In some embodiments, the UE 102 can communicate with a radio access network 104 (RAN 104 or (R)AN 104), which can act as a relay between the UE 102 and other components or services of the CN 101. For example, in some embodiments, the UE 102 can communicate with the RAN 104, which in turn can communicate with an access and mobility management function 108 (AMF 108). In other instances or embodiments, the UE 102 can communicate directly with the AMF 108. In some embodiments, the AMF 108 can communicate with one or more network functions (NFs), such as an authentication server function 120 (AUSF 120), a network slice selection function 122 (NSSF 122), a network repository function 124 (NRF 124), a policy charging function 114 (PCF 114), a network data analytics function 126 (NWDAF 126), a unified data management function 118 (UDM 118), an AS / AF 112, a session management function 110 (SMF 110), and / or the like.

[0087] In some embodiments, the SMF 110 can communicate with one or more user plane functions 106 (UPFs 106, UPF 106a, UPF 106b, collectively referred to as “UPFs 106”). Merely as an example, in some embodiments, the UPFs 106 can communicate with the RAN 104 and the DN 116. In other embodiments, the DN 116 can communicate with a first UPF 106a and the RAN 104 can communicate with a second UPF 106b, while the SMF 110 communicates with the first UPF 106a and the second UPF 106b, and the first UPF 106a and the second UPF 106b communicate with each other.

[0088] In some embodiments, the UE 102 can include a single-mode or dual-mode device such that the UE 102 can connect to one or more RANs 104. In some embodiments, the RAN 104 can be configured to implement one or more radio access technologies (RATs), such as Bluetooth, Wi-Fi, and GSM, UMTS, LTE, or 5G NR, among others, which can be used to connect the UE 102 to the CN 101. In some embodiments, the RAN 104 can include or use a chip (such as a silicon chip) in the UE 102 that can be paired with or otherwise recognized by a similar chip in the CN 101 such that the RAN 104 can establish a connection or communication line between the UE 102 and the CN 101 by recognizing the chip within the UE 102 and pairing it with the chip within the CN 101. In some embodiments, the RAN 104 can implement one or more base stations, towers, or the like to communicate between the UE 102 and the AMF 108 of the CN 101.

[0089] In some embodiments, the communication network 100 or components thereof (e.g., base stations, towers, or the like) can be configured to communicate with a communication device (e.g., the UE 102), such as a cell phone, over a plurality of different frequency bands, such as FR1 (sub-6 GHz), FR2 (mmWave), other suitable frequency bands, sub-bands thereof, or the like. In some embodiments, the communication network 100 can include or employ massive multiple-input and multiple-output (massive MIMO) antennas. In some embodiments, the communication network 100 can include multi-user MIMO (MU-MIMO) antennas. In some embodiments, the communication network 100 can employ edge computing whereby a computing server is closer in communication, physically, computationally, and / or temporally to the communication device (e.g., the UE 102) in order to reduce latency and data traffic congestion. In some embodiments, the communication network 100 can employ other technologies, devices, or techniques, such as small cells, low-power RANs, beamforming of radio waves, WiFi-cellular fusion, non-orthogonal multiple access (NOMA), channel coding, or the like.

[0090] As Figure 3As shown, the UE 102 can be configured to communicate with the RAN 104 in an N1 interface, e.g., according to a non-access stratum (NAS) protocol. In some embodiments, the RAN 104 can be configured to communicate with the CN 101 or components thereof (e.g., the AMF 108) in an N2 interface, e.g., in a control plane between a base station of the RAN 104 and the AMF 108. In some embodiments, the RAN 104 can be configured to communicate with the UPF 106 in an N3 interface, e.g., in a user plane. In some embodiments, the AMF 108 and / or the SMF 110 can be configured to communicate with other services or network entities within the CN 101 in various different interfaces and / or according to various different protocols. For example, in some embodiments, the AMF 108 and / or the SMF 110 can be configured to communicate with the AUSF 120 in an Nausf interface or an N12 interface. In some embodiments, the AMF 108 and / or the SMF 110 can be configured to communicate with the NSSF 122 in an Nnssf interface. In some embodiments, the AMF 108 and / or the SMF 110 can be configured to communicate with the NRF 124 in an Nnrf interface. In some embodiments, the AMF 108 and / or the SMF 110 can be configured to communicate with the PCF 114 in an Npcf interface or an N7 interface. In some embodiments, the AMF 108 and / or the SMF 110 can be configured to communicate with the NWDAF 126 in an Nnwdaf interface. In some embodiments, the AMF 108 and / or the SMF 110 can be configured to communicate with the UDM 118 in an Nudm interface, an N8 interface, or an N10 interface. In some embodiments, the AMF 108 and / or the SMF 110 can be configured to communicate with the AS / AF 112 in an Naf interface. In some embodiments, the SMF 110 can be configured to communicate with the UPF 106 in an N4 interface, which can act as a bridge between a control plane and a user plane, e.g., as a conduit for a protocol data unit (PDU) session during which information is transferred, e.g., between the UE 102 and the CN 101 or components / services thereof.

[0091] It will be appreciated that the example embodiments of the application disclosed and / or otherwise described herein arise in the context of a telecommunications network, including but not limited to a telecommunications network that conforms and / or otherwise incorporates aspects of a Fifth Generation (5G) architecture. Although Figures 1 to 3 Various configurations and / or components of an example architecture of a communication network 100 are illustrated, but many other systems, system configurations, networks, network entities, and paths / protocols for communication therein are contemplated and considered within the scope of the present disclosure.

[0092] Although the methods, devices, and computer program products described herein are described in the context of a fifth generation (5G) core network and system, such as Figures 1 to 3 However, the described methods, devices, and computer program products can be applied in a wider context within any suitable telecommunication system, network, standard, or protocol, as illustrated in Figure 2 and described above.

[0093] In the context of a communication system, e.g. a fifth generation (5G) network, when a user equipment (UE) requests access to the network or services from the network, requests for emergency services are typically prioritized over requests for non-emergency services to be processed. In order for a non-public network to be deployed as part of a public land mobile network (PLMN), closed access group (CAG) cells can be used for network discovery, selection, and access control for such non-public networks, as well as network identification and authentication for non-public networks. When a UE accesses a CAG cell, the network needs to verify whether the UE is allowed to access the CAG cell.

[0094] A non-standalone non-public network is a non-public network (NPN) deployed under the support of a public PLMN using CAG and / or network slicing. As described and claimed herein, a network entity can thus refer to a CAG, NPN, PLMN, or any other entity in such a non- standalone network. When a NPN is available via a PLMN, a UE subscribes to the PLMN to access the network and get services provided by the network. A CAG identifies a group of users that are allowed to access one or more CAG cells. When a UE accesses a CAG cell, the network needs to verify whether the UE is allowed to access the CAG cell. For state transitions and during mobility, the AMF can or should verify whether the CAG identifier received from the next generation radio access network (NG-RAN) is part of the allowed CAG list of the UE as received from the [Unified Data Management] UDM.

[0095] However, in order for the network to verify the UE’s access to a CAG cell, the network needs to know the UE’s subscription permanent identifier (SUPI). According to TS 33.501, during the initial non-access stratum (NAS) procedure (registration procedure), the UE can send a subscription concealed identifier (SUCI) to the network. The serving network only receives the SUPI of the UE from the authentication server function (AUSF) after successful primary authentication. Therefore, if the serving network needs to perform an access control procedure, e.g. as described herein, on the UE during the initial registration procedure, the AMF will have to wait until the primary authentication procedure is successfully completed.

[0096] In some embodiments, when a UE wants to access a system or network (e.g., a Fifth Generation System (5GS)), the UE can first perform an access control check to determine whether access to the network is allowed. In some embodiments, the access control check can be performed for an access attempt defined by the following list of events:

[0097] a) the UE is in idle mode over 3GPP access (e.g., 5G Mobility Management [5GMM]-IDLE mode) and an event occurs that requires a transition to connected mode (e.g., 5GMM-CONNECTED mode); and

[0098] b) the UE is in connected mode (e.g., 5GMM-CONNECTED mode) or connected mode with radio resource control (RRC) inactive indication (e.g., 5GMM-CONNECTED mode) over 3GPP access and one of the following events occurs:

[0099] 1) 5GMM receives from upper layers a management object - multimedia telephone (MO-MMTEL) - voice-call-started indication, MO-MMTEL-video-call-started indication, or MO-SMS-over-IP (SMSoIP) - attempt-started indication;

[0100] 2) 5GMM receives from upper layers a request to send a mobile originated SMS over NAS, unless the request triggers a service request procedure that transitions the UE from 5GMM-IDLE (5GMM-IDLE) mode to 5GMM-CONNECTED (5GMM-CONNECTED) mode;

[0101] 3) 5GMM receives from upper layers a request to send an UL NAS TRANSPORT message for PDU session establishment purposes, unless the request triggers a service request procedure that transitions the UE from 5GMM-IDLE mode to 5GMM-CONNECTED mode;

[0102] 4) 5GMM receives from upper layers a request to send an UL NAS TRANSPORT message for PDU session modification purposes, unless the request triggers a service request procedure that transitions the UE from 5GMM-IDLE mode to 5GMM-CONNECTED mode; and

[0103] 5) 5GMM receives a request to re-establish user plane resources for an existing PDU session.

[0104] In some embodiments, 5GMM specific procedures initiated by NAS in 5GMM-CONNECTED mode can not be affected by access control, e.g. the registration procedure after a PS handover is not prevented by access control. In some embodiments, when NAS detects one of the above events, NAS needs to perform the mapping of the request type to one or more access identities and one access category, and lower layers will perform the access restriction check for the request based on the determined access identities and access category. In some embodiments, NAS can be aware of the above events through an indication provided by upper layers, or when it determines through normal NAS behavior that a 5GMM procedure needs to be initiated, or both.

[0105] In some embodiments, to determine the requested access identity and access category, NAS checks against the set of access identities and access categories defined in 3GPP TS 22.261 for the access reason, the requested service type and the profile of the UE, including UE configuration, i.e.: a) the set of standardized access identities; b) the set of standardized access categories; and c) the set of operator-defined access categories (if available). To determine the applicable access identity from the set of standardized access identities defined in 3GPP TS 22.261, NAS can or should follow the requirements, rules, actions described herein and / or in 3GPP TS 22.261 or otherwise.

[0106] In some embodiments, to determine the applicable access category from the set of standardized access categories and operator-defined access categories defined in 3GPP TS 22.261.

[0107] Turning now to Figure 4 Examples of core network apparatus (CNA) (including core network services: UPF 106, AMF 108, SMF 110, PCF 114, and / or another NF and / or NRF) can be embodied as core network apparatus 200 configured in accordance with example embodiments of the present disclosure. As described below in connection with the flowcharts of Figures 8-12 In any instance, CNA 200 can be more generally embodied by a computing device such as a server, a personal computer, a computer workstation, or other type of computing device (including those used as user equipment and / or wireless local area networks). Regardless of how CNA 200 is embodied, the apparatus of example embodiments can be configured to perform the functions described herein as described below in connection with the flowcharts of Figure 4The illustrated configuration, so as to include, be associated with, or otherwise be in communication with processing circuitry 208 and / or (in some embodiments) communications interface 206, processing circuitry 208 includes, for example, a processor 202 and a memory device 204. In some embodiments, other elements of UE 102 or system 100 can be embodied by a device such as CNA 200. Figure 4

[0108] In processing circuitry 208, processor 202 (and / or a co-processor or any other auxiliary processor or circuitry otherwise associated with the processor) can communicate with memory device 204 via a bus for communicating information to and from the components of CNA 200. The memory device can include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory device can be an electronic memory device (e.g., computer-readable storage medium) that includes gates filled with substrates, which are configured to store data (e.g., bits) that can be retrieved by a machine-based reading device (e.g., computing device like a processor). According to an example embodiment of the application, the memory device can be configured to store information, data, content, applications, instructions, etc. for enabling the apparatus to perform various functions in accordance with an example embodiment of the application. For example, the memory device can be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory can be configured to store instructions for execution by the processor.

[0109] In some embodiments, CNA 200 can be embodied in various computing devices as described above. However, in some embodiments, the apparatus can be embodied as a chip or chip set. In other words, the apparatus can comprise one or more physical packages (e.g., chips) including materials, components and / or wires on a structural assembly (e.g., a baseboard). The structural assembly can provide physical strength, conservation of size, and / or limitation of electrical interaction for component circuitry included thereon. The apparatus can therefore, in some cases, be configured to implement an embodiment of the application on a single chip or as a single "system on a chip." In some cases, a chip or chip set can constitute means for performing one or more operations described herein to provide the functions described herein.

[0110] ​The processor 202 can be embodied in a number of different ways. For example, the processor can be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other circuits or circuitry, including one or more integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special- purpose computer chip, or the like. As such, in some embodiments, the processor can include one or more processing cores configured to perform independently. A multi-core processing device can enable parallel combinatorial operations to improve processing efficiency. Additionally or alternatively, the processor can include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and / or multithreading.

[0111] In one example embodiment, the processor 202 can be configured to execute instructions stored in the memory device 204 or otherwise accessible to the processor. Alternatively or additionally, the processor can be configured to execute hard coded functionality. Thus, whether configured by hardware or software methods, or by a combination thereof, the processor can represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to embodiments of the present disclosure when configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA or the like, the processor can be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of instructions, the instructions can specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processor can be a processor of a particular device (e.g., an encoder or a decoder) configured to employ an embodiment of the present disclosure by further configuration of the processor by instructions for performing the algorithms and / or operations described herein. Further, the processor can include a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor.

[0112] In embodiments that include a communication interface 206, the communication interface can be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and / or transmit data from / to a network and / or any other device or module in communication with the CNA 200 (e.g., NFs, NRF, UE, radio access network, core network services, application servers / functions, databases or other storage devices, etc.). In this regard, the communication interface can include, for example, an antenna (or multiple antennas) and supporting hardware and / or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface can include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle reception of signals received via the antenna(s). In some environments, the communication interface can alternatively or also support wired communication. As such, for example, the communication interface can include a communication modem and / or other hardware / software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms. In some embodiments, the session management function can include a 5GC session management function for any suitable CUPS architecture, such as for a gateway GPRS support node (GGSN-C), TWAG-C, BNG-CUPS, N4, Sxa, Sxb, Sxc, an evolved packet core (EPC) SWG-C, an EPC PGW-C, an EPC TDF-C, etc.

[0113] In some embodiments, the CNA 200 can represent a user equipment configured to connect to other core network entities or network devices. In some embodiments, the user equipment can include a mobile phone (cellular phone), etc.

[0114] As shown, the CNA 200 can include a processor 202 that is in communication with a memory 204 and configured to provide signals to and receive signals from a communication interface 206. In some embodiments, the communication interface 206 can include a transmitter and a receiver. In some embodiments, the processor 202 can be configured to control the functions of the CNA 200 at least partially by sending and receiving signals to and from the communication interface 206. Similarly, the processor 202 can be configured to control the functions of other elements of the CNA 200 by sending and receiving signals to and from these other elements. For example, the processor 202 can be embodied as one or more of various processing elements of a computing device, including but not limited to one or more central processing units (CPUs), one or more semiconductors, one or more integrated circuits (ICs), one or more cores of one or more processors, one or more other processing elements, or a combination of such as similarly, the memory 204 can be embodied as one or more of a variety of memory devices, including but not limited to one or more random access memories (RAM), one or more read only memories (ROM), one or more optical disks, one or more hard disks, one or more solid state drives (SSDs), one or more compact disks (CDs), one or more digital versatile disks (DVDs), one or more flash drives, one or more memories in the cloud, or a combination of such Figure 4 In some example embodiments, the processor 202 can include multiple processors or processing cores.

[0115] The CNA 200 can be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and / or the like. Signals sent and received by the processor 202 can include signaling information in accordance with an air interface standard of an applicable cellular system, and / or any number of different wireline or wireless network

[0116] For example, the CNA 200 and / or cellular modems therein can be capable of operating in accordance with various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third generation (3G) communication protocols, fourth generation (4G) communication protocols, fifth generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP), etc.). For example, the device 10 can be capable of operating in accordance with 2G wireless communication protocols IS- 136, Time Division Multiple Access (TDMA), Global System for Mobile communications (GSM), IS-95, Code Division Multiple Access (CDMA), etc. Also, for example, the device 10 can be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), etc. Further, for example, the CNA 200 can be capable of operating in accordance with 3G wireless communication protocols, such as Universal Mobile

[0117] It should be understood that processor 202 may include circuitry for implementing the audio / video and logic functions of CNA 200. For example, processor 202 may include digital signal processor devices, microprocessor devices, analog-to-digital converters, digital-to-analog converters, etc. The control and signal processing functions of CNA 200 can be distributed among these devices according to their respective capabilities. Processor 202 may additionally include an internal voice encoder (VC), an internal data modem (DM), etc. Furthermore, processor 202 may include the ability to operate one or more software programs, which may be stored in memory 204. Typically, processor 202 and the software instructions stored in memory 206 can be configured to cause CNA 200 to perform actions. For example, processor 202 may be capable of operating connectivity programs, such as web browsers. Connectivity programs may allow CNA 200 to send and receive web page content, such as location-based content, according to protocols such as Wireless Application Protocol, WAP, Hypertext Transfer Protocol, HTTP, etc.

[0118] In some embodiments, CNA 200 may also include a user interface, including, for example, headphones or speakers, a ringer, a microphone, a display, a user input interface, etc., which may be operatively coupled to processor 202. As described above, the display may include a touch-sensitive display on which a user can touch and / or gesture to make selections, input values, etc. Processor 202 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as speakers, ringers, microphones, displays, etc. Processor 202 and / or the user interface circuitry including processor 202 may be configured to control one or more functions of one or more elements of the user interface via computer program instructions (e.g., software and / or firmware) stored on memory 204 accessible to processor 202 (e.g., volatile memory, non-volatile memory, devices including them, etc.). CNA 200 may include a battery for powering various circuitry associated with the mobile terminal (e.g., circuitry providing mechanical vibration as a detectable output). The user input interface may include devices that allow the CNA 200 to receive data, such as a keypad (e.g., a virtual keyboard displayed on the monitor or an externally connected keyboard).

[0119] like Figure 4 As shown, CNA 200 may also include one or more mechanisms for sharing and / or acquiring data, as illustrated by communication interface 206. For example, communication interface 206 of CNA 200 may include a short-range radio frequency (RF) transceiver and / or interrogator, thus enabling data sharing with and / or acquisition from electronic devices based on RF technology. CNA 200 may include other short-range transceivers, such as infrared (IR) transceivers, using Bluetooth...TM Bluetooth TM (BT) transceivers, wireless Universal Serial Bus (USB) transceivers, Bluetooth TM low energy transceivers, ZigBee transceivers, ANT transceivers, cellular device-to-device transceivers, wireless local area network link transceivers, and / or any other short-range radio technology. In some embodiments, the CNA 200, and in particular the short-range transceivers, can be capable of transmitting data to and / or receiving data from electronic devices in the vicinity of the device, such as within about 10 meters. The CNA 200, including a Wi-Fi or wireless local area network modem, can also have the capability to transmit data to and / or receive data from electronic devices according to various wireless network technologies, including 6L0Wpan, Wi-Fi, Wi-Fi low power, WLAN technologies such as IEEE 802.11 technologies, IEEE 802.15 technologies, IEEE 802.16 technologies, and / or the like.

[0120] The CNA 200 can include other memory, such as a Subscriber Identity Module (SIM), a Removable User Identity Module (R-UIM), an eUICC, a UICC, and / or the like, which can store information elements related to a mobile subscriber. In addition to a SIM, the CNA 200 can include other removable and / or fixed memory. The CNA 200 can include volatile memory and / or non-volatile memory, which can include some or all of the memory 204 or can alternatively be a separate memory within or connected to the CNA 200. For example, volatile memory can include Random Access Memory (RAM), including dynamic and / or static RAM, on-board or off-board cache memory, and / or the like. Non-volatile memory, which can be embedded and / or removable, can include, for example, read-only memory, flash memory, magnetic storage devices such as hard disks, floppy disk drives, magnetic tapes, optical disk drives and / or media, non-volatile random access memory (NVRAM), and / or the like. Like volatile memory, non-volatile memory can include a cache area for temporary storage of data. At least portions of the volatile and / or non-volatile memory can be embedded in the processor 202. The memory can store one or more software programs, instructions, pieces of information, data, and / or the like, which can be used by the device for performing operations disclosed herein. Alternatively or additionally, the CNA 200 can be configured to cause operations disclosed herein with respect to base stations, WLAN access points, network nodes including UEs, and / or the like.

[0121] The memory can include an identifier, such as an International Mobile Equipment Identity (IMEI) code, that can uniquely identify the CNA 200. The memory can include an identifier, such as an International Mobile Equipment Identity (IMEI) code, that can uniquely identify the CNA 200. In example embodiments, the processor 202 can be configured and / or provided with the operations disclosed herein for a base station, a WLAN access point, a network node including a UE, etc. using computer code stored in the memory. Likewise, the CNA 200 can be configured as any other component or network device from a core network.

[0122] Some embodiments disclosed herein can be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and / or hardware can reside on memory 204, the control device 202 or electronic components, in some example embodiments, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer-readable medium" can be any non-transitory medium that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, with examples depicted in the figures. A computer-readable medium can comprise a non-transitory computer-readable storage medium that can be any media that can be used to contain or store instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. Figure 4

[0123] Figure 5 Another example of an apparatus 300 (e.g., including or embodying a core network entity, such as a CAN 200, a UE 102, and / or participating in a core network service: a UPF 106, an AMF 108, an SMF 110, a PCF 114, or in communication with a core network service: a UPF 106, an AMF 108, an SMF 110, a PCF 114, and / or another network function (NF) and / or network resource function (NRF)) is illustrated, which can be configured in accordance with example embodiments of the disclosure. As described below in connection with flowcharts, the apparatus 300 of example embodiments can be configured to perform the functions, procedures, and methods described herein, combinations thereof, variations thereof, or portions thereof. Figures 8-12

[0124] ​​In some embodiments, the apparatus 300 is or includes exemplary special-purpose hardware that is specifically designed and configured to perform any of the methods, processes, and procedures described herein. In some embodiments, the apparatus 300 can be part of or in communication with components of the system 100. It should be understood that the apparatus 300 is provided as an example of one embodiment and should not be construed as limiting the scope or spirit of the present disclosure in any way. In this regard, the scope of the present disclosure encompasses many potential embodiments other than those described herein. Thus, although specific embodiments have been described herein, various modifications can be effected without departing from the scope or spirit of the present disclosure, and it is intended that all be within the scope of the present disclosure. Figure 5 FIG. 1 illustrates one example of a configuration of an apparatus for handling emergency services in a private network or other wireless communication system, such as a 5G system, but other configurations can be used to implement certain embodiments of the present disclosure.

[0125] The apparatus 300 can be embodied as a desktop computer, a laptop computer, a mobile terminal, a mobile computer, a mobile telephone, a mobile communication device, a game device, a digital camera / camcorder, an audio / video player, a television device, a radio receiver, a digital video recorder, a positioning device, a chip set, a computing device including a chip set, any combination thereof, or the like. In some example embodiments, the apparatus 300 is embodied as a mobile computing device, such as a mobile telephone, a mobile computer, a personal digital assistant (PDA), a pager, a laptop computer, a desktop computer, a game device, a television, electronic paper, and other types of electronic systems that can employ various embodiments of the present disclosure.

[0126] The apparatus 300 can include a computing device 302 that includes a processor 304, and storage, such as non-volatile memory 306 and / or volatile memory 308. In some embodiments, the processor 304 can be embodied as various means including circuitry, one or more microprocessors with accompanying digital signal processors, one or more processors without accompanying digital signal processors, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits such as, for example, an ASIC (application specific integrated circuit) or FPGA (field programmable gate array), or some combination thereof. Accordingly, although illustrated in Figure 5While shown as a single processor, in some embodiments, processor 304 includes multiple processors. These signals transmitted and received by processor 304 may include signaling information according to the air interface standard of the applicable cellular system and / or any number of different wired or wireless network technologies (including but not limited to Wi-Fi, Wireless Local Access Network (WLAN) technologies such as IEEE 802.11, 802.16, etc.). Furthermore, these signals may include voice data, user-generated data, user-requested data, etc. In this regard, the mobile terminal may be able to operate according to one or more air interface standards, communication protocols, modulation types, access types, etc. More specifically, the mobile terminal may be able to operate according to various first-generation (1G), second-generation (2G), 2.5G, third-generation (3G), fourth-generation (4G), fifth-generation (5G), any frequency band or protocol thereof, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP)), etc. For example, a mobile terminal may be capable of operating according to 2G wireless communication protocols such as IS-136 (Time Division Multiple Access (TDMA)), GSM, and IS-95 (Code Division Multiple Access (CDMA)). Furthermore, for example, a mobile terminal may be capable of operating according to 2.5G wireless communication protocols such as General Packet Radio Service (GPRS) and Enhanced Data GSM Environment (EDGE). Additionally, for example, a mobile terminal may be capable of operating according to 3G wireless communication protocols such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA 2000), Wideband Code Division Multiple Access (WCDMA), and Time Division Synchronous Code Division Multiple Access (TD-SCDMA). A mobile terminal may also be capable of operating according to 3.9G wireless communication protocols such as Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access Network (E-UTRAN). Furthermore, for example, a mobile terminal may be capable of operating according to fourth-generation (4G) wireless communication protocols and / or similar protocols, as well as similar wireless communication protocols that may be developed in the future.

[0127] In addition to broadband systems, some Narrowband Advanced Mobile Phone Systems (NAMPS), and Total Access Communication Systems (TACS), mobile terminals can also benefit from embodiments of the present invention, as should dual-mode or higher mode phones (e.g., digital / analog or TDMA / CDMA / analog phones). Furthermore, device 300 or its components may be capable of operating according to Wi-Fi or Global Microwave Access Interoperability (WiMAX) protocols.

[0128] It is understood that the processor 304 can include circuitry for implementing audio / video and logic functions of the device 300. For example, the processor 304 can include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and / or the like. Control and signal processing functions of the mobile terminal can be allocated between these devices according to their respective capabilities. The processor can additionally include an internal voice coder (VC), an internal data modem (DM), and / or the like. Further, the processor can include functionality to operate one or more software programs, which can be stored in memory. For example, the processor 304 can be capable of operating a connectivity program, such as a web browser. The connectivity program can allow the device 300 to transmit and receive web content, such as location-based content, according to a protocol, such as wireless application protocol (WAP), hypertext transfer protocol (HTTP), and / or the like. The device 300 can be capable of using

[0129] The device 300 can also include a user interface 312, including, for example, an earphone or speaker, a ringer, a microphone, a user display, user input interfaces, and / or the like, which can be operatively coupled to the processor 304. In this regard, the processor 304 can include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as, for example, a speaker, a ringer, a microphone, a display, and / or the like. The processor 304 and / or user interface circuitry comprising the processor 304 can be configured to control one or more functions of one or more elements of the user interface through the use of computer program instructions, e.g., software and / or firmware, stored on a memory accessible to the processor 304, e.g., non- volatile memory 306, volatile memory 308, and / or the like. Although not shown, the device 300 can include a battery for powering various circuits of the device 300, e.g., a circuit providing mechanical vibration as a detectable output. The device 300 can further include a display 314. In some embodiments, the display 314 can be any type of suitable display for an electronic device under discussion, some examples of which include a plasma display panel (PDP), a liquid crystal display (LCD), a light-emitting diode (LED), an organic light-emitting diode display (OLED), a projector, a holographic display, and / or the like. The user interface 312 can include devices allowing the device 300 to receive data, such as a keypad, a touch display (e.g., some example embodiments in which the display 314 is configured as a touch display), a joystick (not shown), and / or other input device. In embodiments including a keypad, the keypad can include the digits (0-9) and associated keys (#, *) and / or other keys for operating the device 300.

[0130] The apparatus 300 can include memory, such as non-removable memory 306 and / or removable memory 308, such as RAM, read only memory (ROM), non-volatile RAM (NVRAM), a subscriber identity module (SIM), a removable user identity module (R-UIM), and / or the like. In addition to memory, the apparatus 300 can include other removable and / or fixed memory. In some embodiments, the removable memory 308 can include random access memory (RAM) including dynamic and / or static RAM, on-board or off-board memory cache, and / or the like. In some embodiments, the non-removable memory 306, which can be embedded and / or removable, can include, for example, read-only memory, flash memory, magnetic storage devices (e.g., hard disks, floppy disk drives, magnetic tape, etc.), optical drives and / or media, non-volatile random access memory (NVRAM), and / or the like. Like the removable memory 308, the non-removable memory 306 can include a cache area for temporary storage of data. The memory can store one or more software programs, instructions, pieces of information, data, and / or similar items which can be utilized to implement functions of the mobile terminal. For example, the memory can include an identifier, such as an international mobile equipment identification (IMEI) code, which uniquely identifies the apparatus 300.

[0131] In some example embodiments, the apparatus 300 includes various means for performing the various functions described herein. These means can include one or more of the processor 304, the non-removable memory 306, the removable memory 308, the user interface 312, or the display 314. Means of the apparatus 300 as described herein can be embodied as, for example, circuitry, hardware elements (for example, a suitably programmed processor, combinational logic circuit, and / or the like), a computer program product including computer-readable program instructions (for example, software or firmware) stored on a computer-readable medium (for example, the memory 306 or 308) that is executable by a suitably configured processing device (for example, the processor 304), or some combination thereof.

[0132] In some example embodiments, Figure 5One or more of the devices shown in FIG. 1 can be embodied as a chip or chip set. In other words, the device 300 can comprise one or more physical packages (for example, chips) including materials, components and / or wires on a structural assembly (for example, a baseboard). The structural assembly can provide physical strength, conservation of size, and / or limitation of electrical interaction for component circuitry included thereon. In this regard, the processor 304, memory 306 and / or 308, user interface 312 and / or display 314 can be embodied as a chip or chip set. The device 300 may, therefore, be configured to implement embodiments of the present application's on a single chip or as a single "system on a chip." In some cases, the chip or chip set can constitute a means for performing one or more operations for providing the functionalities described herein.

[0133] The processor 304 can be embodied in a variety of devices including one or more microprocessors, one or more processors with accompanying digital signal processors, one or more processors without accompanying digital signal processors, one or more co-processors, one or more parallel processors, one or more controllers, processing circuitry, one or more computers, various other processing elements, including integrated circuits such as, for example, an ASIC (application specific integrated circuit) or FPGA (field programmable gate array), one or more other types of hardware processors, or some combination thereof. Accordingly, although illustrated in Figure 5 The processor 304, in some embodiments, comprises multiple processors. The multiple processors can be in operative communication with each other and can be collectively configured to perform one or more functions of the device 100 as described herein. The multiple processors can be embodied on a single computing device or distributed over multiple computing devices collectively configured to function as the device 300. In some embodiments, for example, where the device is embodied as the device 300, the processor 304 can be embodied as or comprise a processor 304 (as described above, for example) and a processor 304' (as described above, for example) in operative communication with each other. In some embodiments, the processor 304 and the processor 304' can be collectively configured to perform one or more functions of the device 100 as described herein. Figure 5The processor 304 is configured, in some example embodiments, to execute instructions stored in the memory 306 and / or 308, or otherwise accessible to the processor 304. These instructions can be for causing the apparatus 300 to perform one or more of the functions of the apparatus 300 as described herein, when executed by the processor 304. As such, the processor 304, whether configured by hardware or software methods, or by a combination thereof, can comprise an entity capable of performing operations according to embodiments of the present application while configured accordingly. Thus, for example, when the processor 304 is embodied as an ASIC, FPGA or the like, the processor 304 can comprise specifically configured hardware for conducting one or more operations described herein. Alternatively, as another example, when the processor 304 is embodied as an executor of instructions, such as can be stored in memory 306 and / or 308, the instructions can specifically configure the processor 304 to perform one or more algorithms and operations described herein.

[0134] The memory 306 and / or 308 can include, for example, volatile memory, non-volatile memory, or some combination thereof. In this respect, the memory 306 and / or 308 can comprise non-transitory computer readable storage medium. Although shown as a single memory in Figure 5 The memory 306 and / or 308 can comprise a plurality of memories. The plurality of memories can be embodied on a single computing device or distributed across a plurality of computing devices collectively configured to function as the apparatus 300. In various example embodiments, the memory 306 and / or 308 can include a hard disk, random access memory, cache memory, flash memory, compact disk read-only memory (CD-ROM), digital versatile disk read-only memory (DVD-ROM), an optical disk, circuitry configured to store the information, or some combination thereof. In some embodiments, the memory 306 and / or 308 can include volatile memory 308 and / or non-volatile memory 306, as Figure 5 The memory 306 and / or 308 can be configured to store information, data, applications, instructions, or the like for enabling the apparatus 300 to carry out various functions in accordance with various example embodiments. For example, in some example embodiments, the memory 306 and / or 308 is configured to buffer input data for processing by the processor 304. Additionally or alternatively, the memory 306 and / or 308 can be configured to store program instructions for execution by the processor 304. The memory 306 and / or 308 can store information in the form of static and / or dynamic information. The stored information can include, for example, images, content, media content, user data, application data, or the like. This stored information can be stored and / or used by the processor 304 in the course of executing its functions.

[0135] In some embodiments, the apparatus 300 can further include a communication interface (not shown) that can be embodied as any device or means embodied in either circuitry, hardware, a computer program product or a combination thereof that is configured to receive and / or transmit data from / to another computing device, that is configured to communicate the data via the bus. In some example embodiments, the communication interface is at least partially embodied as or otherwise controlled by the processor 304. In this regard, the communication interface can be in communication with the processor 304, such as via the bus. The communication interface can include, for example, an antenna, a transmitter, a receiver, a transceiver and / or supporting hardware or software in order to facilitate communication via a wireless network, a wired network, or a combination thereof. In some embodiments, the communication interface is embodied as, or otherwise includes, a transmitter and a receiver. The communication interface can be configured to receive and / or transmit data using any protocol that can be used for communication between computing devices. In this regard, the communication interface can be configured to receive and / or transmit data using any protocol that can be used for transmission of data over a wireless network, a wired network, some combination thereof, or the like on which the apparatus 300 and one or more computing devices can be in communication. As one example, the communication interface can be configured to receive and / or otherwise access content (e.g., web page content, streaming media content, etc.) from a server or other content source over a network. The communication interface can additionally be in communication with the memory 306 and / or 308, the user interface 312, and / or the processor 304, such as via the bus.

[0136] The user interface 312 can be in communication with the processor 304 and configured to receive indications of user input and / or to provide auditory, visual, mechanical, or other output to the user. As such, the user interface 312 can include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, and / or other input / output mechanisms. In embodiments in which the apparatus 300 is embodied as a device 300, the user interface 312 can be embodied as, or otherwise include, a user input interface, such as the display 314 (as Figure 5The user interface 312 can include a display, such as the display 314, and one or more input devices, such as a keypad, a mouse, etc. The user interface 312 can communicate with the memory 306 and / or 308, the communication interface, the sensors, the speaker, and / or the processor 304, such as via a bus. In some example embodiments, the user interface 312 can include a single input / output mechanism. In other embodiments, the user interface 312 can include a content display and a touch display, such as the display 314. In some embodiments, the user interface 312 can include a touch display user interface with a content display portion and a dedicated user input portion, such as a virtual keyboard, a virtual piano, or an application with designated keys for user input.

[0137] The processor 304 can be embodied as various means, such as a circuit, hardware, a computer program product including computer readable program instructions stored on a computer readable medium (e.g., the memory 306 and / or 308) and executed by a processing device (e.g., the processor 304), and in some embodiments, as the processor 304 or otherwise controlled by the processor 304. The processor 304 can further communicate with one or more of the memory 306 and / or 308 or the user interface 312, such as via a bus.

[0138] The processor 304 can be configured to receive user input from the user interface 312, such as a touch display. The user input or signal can carry position information indicative of the user input. In this regard, the position can include a location of the user input in a two-dimensional space, which can be relative to a surface of the touch display user interface. For example, the location can include a coordinate position relative to a two-dimensional coordinate system (e.g., X and Y axes), from which the location can be determined. Accordingly, the processor 304 can determine an element / instruction / command corresponding to a key or image displayed on the touch display user interface at or within a predetermined proximity of the determined location (e.g., within a predefined tolerance range). The processor 304 can be further configured to perform a function or action related to the key corresponding to the element / instruction / command determined by the processor 304 based on the position of the touch-based or other user input.

[0139] Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein can be improved user device or network device configuration. As such, any embodiment of a method, system, approach, device, apparatus, or computer program described or illustrated herein is understood to include any or all of the components, functions, elements, or steps of any other embodiments, so that any method can be performed by the CNA 200, the apparatus 300, or by any other suitable system or device, and likewise can be implemented according to computer program code that is within the scope of this disclosure.

[0140] In the context of a communication system, such as system 100, an emergency service can be requested, e.g., by UE 102, by sending a PDU session request message to AMF 108. For example, in 5G networks, closed access groups (CAGs) can be established or defined. In some embodiments, a CAG can specify that only certain UEs belonging to a certain group are allowed to access the network via a certain cell. However, one problem is that for a UE requesting to establish or having established an emergency session (e.g., an emergency PDU session), the access restrictions to the network should not count, but such CAG restrictions should only be valid for UEs that are prohibited from requesting or have established a “normal” session with the network.

[0141] According to conventional network configurations and functions, e.g., according to the latest 5G protocols, there is currently no solution for identifying emergency session requests from UEs that are connected via a CAG but have been removed from the CAG list. In other words, when the permission is revoked while a session via a CAG is still ongoing after the UE has legally accessed the network via the CAG, there is currently no solution to determine which sessions or session requests to prohibit and which to keep. Then, all sessions should be released except for the potential emergency session. According to typical conventional approaches, the only option to handle the sessions in this case is to prohibit or release all sessions and log off all UEs.

[0142] In some embodiments, in instances where a UE wants to establish a PDU session that is not an emergency session via a non-allowed CAG, the session establishment request can or should be rejected by the AMF and the UE should stop trying to establish the non-emergency session via the non-CAG cell. At the UE side, an interaction between the mobility management (MM) layer and the session management (SM) layer can or should be performed.

[0143] In some embodiments, when the UE is legally connected to the network via a CAG cell, and when the CAG information is updated and the UE has an ongoing emergency PDU session, and when the UE does not pass the CAG access control (e.g., with respect to the updated CAG information), then the AMF can or should perform the local release of all PDU sessions except the emergency PDU session. When the CAG information is updated, the UE should locally release all non-emergency sessions on the UE side - thus, there is also a change on the UE side. When the UE receives a new “CAG information list” and the UE’s session request is a “normal” (non-emergency) session, once the CAG information is updated, the “normal” session can not be allowed to access the network via CAG, then, so far, the procedure has been that the UE can or should enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and can or should apply the PLMN selection procedure. In some embodiments, this procedure or protocol can be extended by considering whether the UE has an emergency PDU session, if so, then the UE can or should perform the local release of all PDU sessions except the emergency PDU session.

[0144] In some embodiments, in instances where the UE wants to establish a non-emergency PDU session via a CAG that is not allowed, the non-emergency PDU session request should be rejected by the AMF and the UE should stop trying. In some embodiments, the UE can then initiate an interaction between the 5G mobility management (5GMM) sublayer of the UE and the 5G session management (5GSM) sublayer of the UE to reconfigure and / or change its state according to the updated CAG information.

[0145] In some embodiments, in instances where the UE is legally connected via a CAG cell, the CAG information is updated, the UE has an ongoing emergency PDU session, and the UE does not pass the CAG access control based on the updated CAG information, then the AMF can or should perform the local release of all PDU sessions except the emergency PDU session. Since in this instance the UE should also locally release all non-emergency sessions on its own side, there is also a change on the UE side. In some embodiments, in instances where the UE receives a new “CAG information list” and the UE’s request for a normal, non-emergency PDU session is no longer allowed to access the network via CAG, then the UE can or should enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and can or should apply the PLMN selection procedure. In some embodiments, this procedure can be extended by adding a determination of whether the UE has an emergency PDU session; if so, then the UE can or should perform the local release of all PDU sessions except the emergency PDU session.

[0146] In some networks, such as fourth generation (4G) networks, CSG is "network-only" and thus does not involve the UE and thus does not provide CSG information to the UE. Thus, conventional methods and standards do not provide for how the UE is to react to such instances. In some embodiments, such as in 4G networks, there is no NAS signaling that allows the UE to update CSG information.

[0147] In some embodiments, such as in 5G networks, upon receiving updated CAG information, the UE can or should enter a deregistered state. In some embodiments, the UE and the network should locally release non- emergency PDU sessions. In other words, both the UE and the network release non-emergency PDU sessions. Without wishing to be bound by any particular theory, out-of-sync PDU session states between the UE and the network can result in unnecessary resource consumption. For example, the UE can request a PDU session that has already been locally released by the network, resulting in the network having to reject the UE session request. Thus, synchronization should be implemented as much as possible.

[0148] In some embodiments, even if the UE does not pass CAG access control, the UE should not be deregistered from the PLMN due to CAG if the UE has an emergency PDU session. Further, if the UE does not pass CAG access control, the UE and the network should locally release non-emergency PDU sessions. In some embodiments, when the AMF updates CAG information, if the UE has an emergency PDU session and the UE does not pass CAG access control with the updated CAG information, the AMF can or should perform local release of all PDU sessions except the emergency PDU session. There are several instances in which the UE should be deregistered from the network upon receiving CAG information. However, if the UE has an emergency PDU session and the UE needs to release non-emergency PDU sessions, deregistration needs to be avoided. The AMF should accept the request from the UE with an emergency PDU session and locally release non-emergency PDU sessions. PDU session synchronization can be implemented with the existing PDU session status IE.

[0149] In some embodiments, the UE configuration update procedure can be initiated by the network. In some embodiments, the AMF can or should initiate the generic UE configuration update procedure by sending a CONFIGURATION UPDATE COMMAND message to the UE. In some embodiments, the AMF can or should include in the CONFIGURATION UPDATE COMMAND message: a) one or more of the following parameters: 5G Global Unique Temporary Identity (5G-GUTI), Tracking Area Identity (TAI) list, Allowed Network Slice Selection Assistance Information (NSSAI) (which can include one or more mapped S-NSSAI), Local Data Network (LADN) information, Service Area List, Mobile Initiated Connection Only (MICO) indication, Network Identity and Time Zone (NITZ) information, Configured NSSAI (which can include mapped S-NSSAI(s)), Rejected NSSAI, Network Slice Subscription Change Indication, Operator-defined Access Class definition, Short Message Service (SMS) indication, Service Gap Time value, “CAG Information List”, UE Radio Capability ID, 5GS Registration Result, or UE Radio Capability ID deletion indication; b) a Configuration Update Indication IE with the Registration Request bit set to “Registration Requested”; or c) a combination of both a) and b).

[0150] In some embodiments, if an acknowledgement from the UE is requested, the AMF can or should indicate “Acknowledgement Requested” in the Acknowledgement bit of the Configuration Update Indication IE in the CONFIGURATION UPDATE COMMAND message and can or should start timer T3555. An acknowledgement can or should be requested for all parameters except in some embodiments when NITZ only is included.

[0151] In some embodiments, to initiate parameter renegotiation between the UE and the network, the AMF can or should indicate “Registration Requested” in the Registration Request bit of the Configuration Update Indication IE in the CONFIGURATION UPDATE COMMAND message. In some embodiments, the AMF can or should indicate “Registration Requested” in the Registration Request bit of the Configuration Update Indication IE and include the Allowed NSSAI IE in the CONFIGURATION UPDATE COMMAND message if the new Allowed NSSAI information or supported S-NSSAIs AMF reconfiguration requires AMF relocation.

[0152] In some embodiments, if the AMF includes a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message and the new configured NSSAI requires AMF relocation as specified in, for example, 3GPP TS 23.501, the AMF can or should indicate "registration requested" in the registration request bit of the configuration update indication IE in the message. In some embodiments, if the AMF indicates "registration requested" in the registration request bit of the configuration update indication IE, the acknowledgement can or should be requested. In some embodiments, if the CONFIGURATION UPDATE COMMAND message is initiated due to change of allowed NSSAI only and these changes require the UE to initiate the registration procedure, but the AMF is unable to determine the allowed NSSAI for the UE as specified in, for example, 3GPP TS 23.501, the CONFIGURATION UPDATE COMMAND message can or should indicate "registration requested" in the registration request bit of the configuration update indication IE and can not or should not include any other parameters. In some embodiments, if the network slice specific authentication and authorization procedure for an S-NSSAI is completed as: successful, the AMF can or should include the S-NSSAI in the allowed NSSAI; or failed, the AMF can or should include the S-NSSAI in the rejected NSSAI and include the rejection cause "S-NSSAI not available due to network slice specific authorization and authentication failure or revocation" in the rejected NSSAI.

[0153] In some embodiments, the allowed NSSAI and the rejected NSSAI can or should be included in the CONFIGURATION UPDATE COMMAND message to reflect the result of the procedure subject to network slice specific authentication and authorization. In some embodiments, if there are multiple S-NSSAIs subject to network slice specific authentication and authorization, it is implementation specific if the AMF informs the UE of the result of the procedure in one or more CONFIGURATION UPDATE COMMAND messages.

[0154] In some embodiments, if the AMF includes the network slice indication IE in the CONFIGURATION UPDATE COMMAND with the network slice subscription change indication set to "network slice subscription changed" and the change of allowed NSSAI requires the UE to initiate the registration procedure, but the AMF is unable to determine the allowed NSSAI for the UE as specified in, for example, 3GPP TS 23.501, the CONFIGURATION UPDATE COMMAND message can or should additionally indicate "registration has been requested" in the registration request bit of the configuration update indication IE and can not or should not include the allowed NSSAI.

[0155] If the AMF needs to update the LADN information, the AMF can or should include the LADN information in the LADN information IE of the CONFIGURATION UPDATE COMMAND message. If the AMF needs to update the "CAG information list", the AMF can or should include the CAG information list IE in the CONFIGURATION UPDATE COMMAND message. If the UE has an emergency PDU session and the UE does not pass the CAG access control with the updated CAG information (e.g., if 1) the UE is in a CAG cell and none of the CAG-ID(s) supported by the CAG cell is included in the "allowed CAG list" for the current PLMN in the updated "CAG information list", or if 2) the UE is in a non-CAG cell and the entry for the current PLMN in the updated "CAG information list" includes an "indication that the UE is only allowed to access the 5GS via CAG cells"), the AMF can or should perform the local release of all PDU sessions except the emergency PDU session.

[0156] During an established 5GMM context, the network can send or not send one or more CONFIGURATION UPDATE COMMAND messages to the UE. If more than one CONFIGURATION UPDATE COMMAND message is sent, the messages need not have the same content.

[0157] In some embodiments, the UE can accept the UE configuration update. In some embodiments, upon reception of the CONFIGURATION UPDATE COMMAND message, if timer T3346 is running, the UE can or should stop timer T3346 and use the contents to update the appropriate information stored within the UE. In some embodiments, if “acknowledgement requested” is indicated in the confirmation bit of the configuration update indication IE in the CONFIGURATION UPDATE COMMAND message, the UE can or should send a CONFIGURATION UPDATE COMPLETE message. In some embodiments, if the UE receives a new 5G-GUTI in the CONFIGURATION UPDATE COMMAND message, the UE can or should consider the new 5G-GUTI valid, the old 5G-GUTI invalid, stop timer T3519 if running, and delete any stored SUCI; otherwise, the UE can or should consider the old 5G-GUTI valid. If the CONFIGURATION UPDATE COMMAND message is sent over non-3GPP access and the UE is in 5GMM-REGISTERED in both 3GPP access and non-3GPP access in the same PLMN, the UE can or should provide the 5G-GUTI to lower layers for 3GPP access.

[0158] If the UE receives a new TAI list in the CONFIGURATION UPDATE COMMAND message, the UE can or should consider the new TAI list valid and the old TAI list invalid; otherwise, the UE can or should consider the old TAI list valid. If the UE receives a new service area list in the CONFIGURATION UPDATE COMMAND message, the UE can or should consider the new service area list valid and the old service area list invalid; otherwise, the UE can or should consider the old service area list (if any) valid. If the UE receives new NITZ information in the CONFIGURATION UPDATE COMMAND message, the UE considers the new NITZ information valid and the old NITZ information invalid; otherwise, the UE can or should consider the old NITZ information valid.

[0159] If the UE receives the LADN information IE in the CONFIGURATION UPDATE COMMAND message, the UE can or shall consider the old LADN information invalid and the new LADN information valid (if any); otherwise, the UE can or shall consider the old LADN information valid. If the UE receives a new allowed NSSAI for an associated access type in the CONFIGURATION UPDATE COMMAND message, the UE can or shall consider the new allowed NSSAI valid for the associated access type, store the allowed NSSAI for the associated access type, and consider the old allowed NSSAI for the associated access type invalid; otherwise, the UE can or shall consider the old allowed NSSAI for the associated access type valid. If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message, the UE can or shall consider the new configured NSSAI valid for the registered PLMN and the old configured NSSAI invalid for the registered PLMN; otherwise, the UE can or shall consider the old configured NSSAI valid for the registered PLMN. The UE can or shall store the new configured NSSAI.

[0160] If the UE receives the network slice indication IE in the CONFIGURATION UPDATE COMMAND message with the network slice subscription change indication set to "network slice subscription changed", the UE can or shall delete the network slice information for each PLMN except the current PLMN. If the UE receives the operator-defined access category definition IE in the CONFIGURATION UPDATE COMMAND message and the operator-defined access category definition IE contains one or more operator-defined access category definitions, the UE can or shall delete any stored operator-defined access category definitions for the registered public land mobile network (RPLMN) and can or shall store the received operator-defined access category definitions for the RPLMN. If the UE receives the operator-defined access category definition IE in the CONFIGURATION UPDATE COMMAND message and the operator-defined access category definition IE does not contain an operator-defined access category definition, the UE can or shall delete any stored operator-defined access category definitions for the RPLMN. If the CONFIGURATION UPDATE COMMAND message does not contain the operator-defined access category definition IE, the UE can or shall not delete any stored operator-defined access category definitions for the RPLMN.

[0161] If the UE receives an SMS indication IE in the CONFIGURATION UPDATE COMMAND message with the SMS availability indication set to: a) "SMS over NAS not available", the UE can or shall consider that the network does not allow SMS over NAS transmission; b) "SMS over NAS available", the UE can request the use of SMS over NAS transmission by performing the registration procedure for mobility and periodic registration update after completing the general UE configuration update procedure.

[0162] If the UE receives a CAG information list IE in the CONFIGURATION UPDATE COMMAND message, the UE can or shall delete any stored "CAG information list" and can or shall store the "CAG information list" received via the CAG information list IE. If the received "CAG information list" includes an entry containing the current PLMN identity, the UE can or shall operate as follows:

[0163] A) If the UE receives the CONFIGURATION UPDATE COMMAND message via a CAG cell, the entry for the current PLMN in the received "CAG information list" or the "allowed CAG list" can not or does not include the CAG-ID(s) supported by the current CAG cell, and:

[0164] i) the entry for the current PLMN in the received "CAG information list" does not include the indication "UE is only allowed to access 5GS via CAG cells", the UE can or shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and can or shall search for a suitable cell with the updated "CAG information list" according to e.g. 3GPP TS 38.304; or

[0165] ii) the entry for the current PLMN in the received "CAG information list" includes the indication "UE is only allowed to access 5GS via CAG cells", and:

[0166] iii) if the "allowed CAG list" for the current PLMN in the received "CAG information list" includes one or more CAG-IDs, the UE can or shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and can or shall search for a suitable cell with the updated "CAG information list" according to e.g. 3GPP TS 38.304; or

[0167] iv) if the entry for the current PLMN in the received "CAG Information List" or the "Allowed CAG List" does not include any CAG-ID, and:

[0168] a) the UE has no emergency PDU session, then the UE can or shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and can or shall apply the PLMN selection procedure defined in e.g. 3GPP TS 23.122 with the updated "CAG Information List"; or

[0169] b) the UE has an emergency PDU session, then the UE can or shall perform local release of all PDU sessions except the emergency PDU session; or

[0170] B) if the UE receives a CONFIGURATION UPDATE COMMAND message via a non-CAG cell and the entry for the current PLMN in the received "CAG Information List" includes an "indication that the UE is only allowed to access 5GS via CAG cells", and:

[0171] i) if the "Allowed CAG List" for the current PLMN in the received "CAG Information List" includes one or more CAG-IDs, then the UE can or shall enter state 5GMM-REGISTERED.LIMITED-SERVICE and can or shall search for a suitable cell according to e.g. 3GPP TS 38.304 with the updated "CAG Information List"; or

[0172] ii) if the entry for the current PLMN in the received "CAG Information List" or the "Allowed CAG List" does not include any CAG-ID, and:

[0173] iii) the UE has no emergency PDU session, then the UE can or shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and can or shall apply the PLMN selection procedure defined in e.g. 3GPP TS 23.122 with the updated "CAG Information List"; or

[0174] iv) the UE has an emergency PDU session, then the UE can or shall perform local release of all PDU sessions except the emergency PDU session.

[0175] if the CONFIGURATION UPDATE COMMAND message indicates "registration has been requested" in the registration request bit of the configuration update indication IE, and:

[0176] a) does not include other parameters or includes at least one of the following parameters: new allowed NSSAI, new configured NSSAI, or network slice subscription change indication, and:

[0177] 1) Emergency PDU session exists, then the UE can or should release the existing N1 NAS signaling connection after completing the general UE configuration update procedure and releasing the emergency PDU session, and initiate the registration procedure for mobility and periodic registration update; or

[0178] 2) Emergency PDU session does not exist, then the UE can or should initiate the registration procedure for mobility and periodic registration update after completing the general UE configuration update procedure and releasing the existing N1 NAS signaling connection; or

[0179] b) includes MICO indication without new allowed NSSAI or new configured NSSAI, then the UE can or should initiate the registration procedure for mobility and registration update to renegotiate the MICO mode with the network after completing the general UE configuration update procedure.

[0180] In some embodiments, the UE receiving a rejected NSSAI in a CONFIGURATION UPDATE COMMAND message takes the following actions based on the rejection cause in the rejected NSSAI:

[0181] “S-NSSAI is not available in the current PLMN [Public Land Mobile Network] or SNPN [Standalone Non-Public Network]”: The UE can or should add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN and does not attempt to use the S-NSSAI in the current PLMN until the UE is turned off, the Universal Integrated Circuit Card (UICC) containing the Universal Subscriber Identity Module (USIM) is removed, or the entry of the “Subscriber Data List” with the SNPN identity of the current SNPN is updated.

[0182] “S-NSSAI is not available in the current registration area”: The UE can or should add the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area and does not attempt to use the S-NSSAI in the current registration area until the UE is turned off, the UE moves out of the current registration area, the Universal Integrated Circuit Card (UICC) containing the Universal Subscriber Identity Module (USIM) is removed, or the entry of the “Subscriber Data List” with the SNPN identity of the current SNPN is updated.

[0183] If the UE receives the T3447 value IE in the CONFIGURATION UPDATE COMMAND message and has indicated "Support for inter-service gap control" in the REGISTRATION REQUEST, the UE can or shall replace the stored T3447 value with the received value in the T3447 value IE and use the received T3447 value when starting the timer T3447 next time if neither zero nor de-activated. If the received T3447 value is zero or de-activated, the UE can or shall stop the timer T3447 if it is running.

[0184] If the UE is not in NB-N1 mode, the UE has set the Radio Application Cloud Server (RACS) bit to "Support for RACS" in the 5GMM capability IE of the REGISTRATION REQUEST message and the CONFIGURATION UPDATE COMMAND message includes:

[0185] a) the UE Radio Capability ID Deletion Indication IE set to "UE Radio Capability ID of network allocation has been requested", the UE can or shall delete any network allocated UE Radio Capability ID associated with the RPLMN or RSNPN stored at the UE, then the UE can or shall initiate the registration procedure for mobility and periodic registration update. If the UE has a manufacturer allocated UE Radio Capability ID applicable to the current UE radio configuration, the UE can or shall include the manufacturer allocated UE Radio Capability ID in the UE Radio Capability ID IE of the REGISTRATION REQUEST message; and

[0186] b) the UE Radio Capability ID IE, the UE can or shall store the UE Radio Capability ID.

[0187] If the UE is not currently registered for emergency services and the 5GS registration result IE in the CONFIGURATION UPDATE COMMAND message is set to "Registered for emergency services", the UE can or shall consider itself registered for emergency services.

[0188] In some embodiments, the AMF can or should accept the REGISTRATION REQUEST message if the UE has an emergency PDU session, even if the UE does not have CAG access control. If a UE not having CAG access control has an emergency PDU session, the AMF can or should perform local release of all non-emergency PDU sessions associated with 3GPP access, and can or should request the SMF to perform local release of all those non-emergency PDU sessions. If the registration update request has been accepted by the network, the AMF can or should send a REGISTRATION ACCEPT message to the UE. If timer T3513 is running in the AMF, the AMF can or should stop timer T3513 if the paging request is sent together with an access type indicating non-3GPP and the REGISTRATION REQUEST message includes the allowed PDU session status IE. If timer T3565 is running in the AMF, the AMF can or should stop timer T3565 upon reception of the REGISTRATION REQUEST message.

[0189] For each of the following information elements: 5GMM capabilities, S1 UE network capabilities, and UE security capabilities, the AMF can or should store all octets received from the UE in the REGISTRATION REQUEST message up to the maximum length defined for the respective information element. In some embodiments, this information can be forwarded to the new AMF during inter-AMF handover, or to the new mobility management entity (MME) during inter-system handover to S1 mode.

[0190] 5G-GUTI reallocation can or should be part of the registration procedure for mobility registration update. 5G-GUTI reallocation shall be part of the registration procedure for periodic registration update. During the registration procedure for mobility registration update, if the AMF has not allocated a new 5G-GUTI through the general UE configuration update procedure, the AMF can or should include the newly allocated 5G-GUTI in the REGISTRATION ACCEPT message. If the 5G-GUTI or SOR transparent container IE is included in the REGISTRATION ACCEPT message, the AMF can or should start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED.

[0191] If the operator-defined access category definition IE or the extended emergency number list IE is included in the REGISTRATION ACCEPT message, the AMF can or shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED. If the UE is not in NB-N1 mode and the UE has set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the AMF can include the UE radio capability ID IE or the UE radio capability ID deletion indication IE in the REGISTRATION ACCEPT message. In this case, the AMF can or shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED.

[0192] The AMF can include in the REGISTRATION ACCEPT message a new TAI list for the UE. The new TAI list can or shall not contain both tracking areas in NB-N1 mode and tracking areas not in NB-N1 mode. The UE can or shall delete its old TAI list upon reception of the REGISTRATION ACCEPT message and store the received TAI list. If no TAI list is received, the UE can or shall consider the old TAI list to be valid. In some embodiments, the AMF can consider the capability of eNodeB to support Cellular Internet of Things (CIoT) 5GS optimization when allocating the TAI list.

[0193] The AMF can also include a list of Equivalent PLMNs in the REGISTRATION ACCEPT message. Each entry in the list contains a PLMN code (e.g., Mobile Country Code [MCC] + Mobile Network Code [MNC]). The UE can or should store the list provided by the network and remove from the list any PLMN code that was already in the “Barred PLMN” list if no emergency PDU session is established. If the UE is not registered for emergency services and an emergency PDU session is established, the UE can or should remove from the Equivalent PLMN list any PLMN code that is present in the “Barred PLMN list” when the emergency PDU session is released. In addition, the UE can or should add to the stored list the PLMN code of the registered PLMN that sent the list. The UE can or should replace the stored list each time a REGISTRATION ACCEPT message is received. If the REGISTRATION ACCEPT message does not contain the list, the UE can or should delete the stored list. In some embodiments, if the UE is not registered for emergency services, and if the PLMN identity of the registered PLMN is a member of the “Barred PLMN” list, any such PLMN identity can or should be removed from the corresponding list(s).

[0194] The AMF can include a new service area restriction in the Service Area List IE in the REGISTRATION ACCEPT message. The UE can receive the REGISTRATION ACCEPT message with the new service area restriction and take action on it, such as described elsewhere herein. If the Service Area List IE is not included in the REGISTRATION ACCEPT message, any tracking area in the registered PLMN and its equivalent PLMN(s) in the registration area are considered as allowed tracking areas.

[0195] In some embodiments, the AMF can or should include the MICO indication IE in the REGISTRATION ACCEPT message only if the MICO indication IE is included in the REGISTRATION REQUEST message, the AMF supports and accepts the use of MICO mode. If the AMF supports and accepts the use of MICO mode, the AMF can indicate “all PLMN registration areas are assigned” in the MICO indication IE in the REGISTRATION ACCEPT message. If “all PLMN registration areas are assigned” is indicated in the MICO indication IE, the AMF can not or should not assign and include a TAI list in the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message includes the MICO indication IE indicating “all PLMN registration areas are assigned”, the UE can or should consider all TAIs in the current PLMN as registration areas and delete its old TAI list. If “strict periodic registration timer is supported” is indicated in the MICO indication IE in the REGISTRATION REQUEST message, the AMF can indicate “strict periodic registration timer is supported” in the MICO indication IE and can include the T3512 value IE in the REGISTRATION ACCEPT message. If the timer value received in the T3512 IE is different from the already stored value of timer T3512 and timer T3512 is running, the UE can or should restart T3512 with the new value received in the T3512 value IE.

[0196] In some embodiments, if the UE requests an active time value in the REGISTRATION REQUEST message and the AMF accepts the use of MICO mode and the use of active time, the AMF can or should include the active time value in the T3324 IE in the REGISTRATION ACCEPT message. In some embodiments, if the UE does not include the MICO indication IE in the REGISTRATION REQUEST message, the AMF can or should disable the MICO mode if the MICO mode has been enabled. In some embodiments, the AMF can include the T3512 value IE in the REGISTRATION ACCEPT message only when the REGISTRATION REQUEST message is sent over 3GPP access. In some embodiments, the AMF can include the non-3GPP de-registration timer value IE in the REGISTRATION ACCEPT message only when the REGISTRATION REQUEST message is sent for non-3GPP access.

[0197] If the UE requests "Control Plane CIoT 5GS Optimization" in the 5GS update type IE, indicates support for Control Plane CIoT 5GS Optimization in the 5GMM capability IE, and the AMF decides to accept the requested CIoT 5GS optimization and the registration request, the AMF can or should indicate "Support of Control Plane CIoT 5GS Optimization" in the 5GS network features support IE of the REGISTRATION ACCEPT message. In some embodiments, if the UE has indicated support for Control Plane CIoT 5GS Optimization and the AMF decides to activate congestion control for the transmission of user data via control plane, the AMF can or should include the T3448 value IE in the REGISTRATION ACCEPT message.

[0198] For inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode, if the UE has included the ngKSI indicating the current 5G NAS security context in the REGISTRATION REQUEST message (the REGISTRATION REQUEST message is integrity protected by the ngKSI), the AMF can or should take one of the following actions:

[0199] a) If the AMF retrieves the current 5G NAS security context indicated by the ngKSI and 5G-GUTI sent by the UE, the AMF can or should perform integrity check of the REGISTRATION REQUEST message using the current 5G NAS security context and integrity protect the REGISTRATION ACCEPT message using the current 5G NAS security context;

[0200] b) If the AMF cannot retrieve the current 5G NAS security context indicated by the ngKSI and 5G-GUTI sent by the UE, the AMF can or should consider the REGISTRATION REQUEST message as integrity check failure and take actions, e.g., according to 3GPP TS 24.501 or 3GPP TS 29.502; or

[0201] c) If the UE has not included the additional GUTI IE, the AMF can consider the REGISTRATION REQUEST message as the previous item, i.e., as if it cannot retrieve the current 5G NAS security context.

[0202] In some embodiments, the procedure for handling as described above when the current 5G NAS security context fails to be retrieved or if the additional GUTI IE is not provided does not preclude the option for the AMF to perform primary authentication and key agreement procedure and create a new native 5G NAS security context. In some embodiments, integrity checking at the AMF for inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode can be FFS (for further study).

[0203] Upon receiving the REGISTRATION ACCEPT message, the UE can or should reset the registration attempt counter and the service request attempt counter, enter the state 5GMM-REGISTERED, and set the 5GS update status to 5U1 UPDATED. In some embodiments, if the UE receives the REGISTRATION ACCEPT message from a PLMN, the UE can or should reset the PLMN-specific attempt counter for that PLMN for the specific access type for which the message was received. The UE can also or should reset the PLMN-specific N1 mode attempt counter for that PLMN for the specific access type for which the message was received. If the message was received via 3GPP access, the UE can or should reset the counter for the event “SIM / USIM considered invalid for GPRS services” and the counter for the event “SIM / USIM considered invalid for non-GPRS services”, if any. If the message was received via non-3GPP access, the UE can or should reset the counter for the event “SIM / USIM considered invalid for 5GS services over non-3GPP access”.

[0204] If the UE receives the REGISTRATION ACCEPT message from a SNPN, the UE can or should reset the SNPN-specific attempt counter for the current SNPN for the specific access type for which the message was received. If the message was received via 3GPP access, the UE can or should reset the counter for the event “entry for the current SNPN considered invalid for 3GPP access”. If the message was received via non-3GPP access, the UE can or should reset the counter for the event “entry for the current SNPN considered invalid for non-3GPP access”.

[0205] In some embodiments, if the REGISTRATION ACCEPT message includes a T3512 value IE, the UE can or should use the value in the T3512 value IE as the periodic registration update timer (e.g., T3512 timer). If the T3512 value IE is not included, the UE can or should use the currently stored value, e.g., from a previous REGISTRATION ACCEPT message. In some embodiments, if the REGISTRATION ACCEPT message includes a T3324 value IE, the UE can or should use the value in the T3324 value IE as the active time timer (e.g., T3324 timer). If the REGISTRATION ACCEPT message does not include the T3324 value IE, the UE can or should not start the timer T3324 until a new value is received from the network.

[0206] In some embodiments, if the REGISTRATION ACCEPT message includes a non-3GPP de-registration timer value IE, the UE can or should use the value in the non-3GPP de-registration timer value IE as the non-3GPP de-registration timer. In some embodiments, if the non-3GPP de-registration timer value IE is not included, the UE can or should use the currently stored value, e.g., from a previous REGISTRATION ACCEPT message. In some embodiments, if the non-3GPP de-registration timer value IE is not included and there is no stored non-3GPP de-registration timer value in the UE, the UE can or should use a default value for the non-3GPP de-registration timer.

[0207] In some embodiments, if the REGISTRATION ACCEPT message contains a 5G-GUTI, the UE can or should return a REGISTRATION COMPLETE message to the AMF to acknowledge the reception of the 5G-GUTI, stop the timer T3519 if it is running, and delete any stored SUCI. In some embodiments, if the REGISTRATION ACCEPT message is sent over non-3GPP access and the UE is in 5GMM-REGISTERED state in both 3GPP access and non-3GPP access in the same PLMN, the UE can or should provide the 5G-GUTI to lower layers for 3GPP access.

[0208] In some embodiments, if the REGISTRATION ACCEPT message contains a network slice indication IE with a network slice subscription change indication set to "network slice subscription changed" or contains a configured NSSAI IE with a new configured NSSAI for the current PLMN and optionally mapped S-NSSAI(s) for the configured NSSAI for the current PLMN, the UE can or should return a REGISTRATION COMPLETE message to the AMF to confirm successful update of network slice information.

[0209] In some embodiments, if the REGISTRATION ACCEPT message contains an operator-defined access category definition IE or an extended emergency number list IE or both, the UE can or should return a REGISTRATION COMPLETE message to the AMF to confirm receipt of the operator-defined access category definition or the extended local emergency number list or both. In some embodiments, if the REGISTRATION ACCEPT message contains a UE radio capability ID IE or a UE radio capability ID deletion indication IE, the UE can or should return a REGISTRATION COMPLETE message to the AMF to confirm receipt of the UE radio capability ID IE or the UE radio capability ID deletion indication IE.

[0210] In some embodiments, if the T3448 value IE is present in the received REGISTRATION ACCEPT message and the value indicates that the timer is neither zero nor deactivated, the UE can or should: a) if timer T3448 is running, stop timer T3448; b) start timer T3448 with the value provided in the T3448 value IE. In some embodiments, if the UE is using 5GS services with control plane CIoT 5GS optimization, the T3448 value IE is present in the REGISTRATION ACCEPT message and the value indicates that the timer is zero or deactivated, the UE can or should ignore the T3448 value IE and proceed as if the T3448 value IE was not present.

[0211] In some embodiments, if a UE in 5GMM-IDLE mode initiates a registration procedure for mobility and periodic registration update, and the REGISTRATION ACCEPT message does not include the T3448 value IE, and if timer T3448 is running, the UE can or should stop timer T3448. In some embodiments, upon receiving the REGISTRATION COMPLETE message, the AMF can or should stop timer T3550 and change to state 5GMM-REGISTERED. In some embodiments, if a 5G-GUTI is sent in the REGISTRATION ACCEPT message, the 5G-GUTI can or should be considered valid, and if a UE radio capability ID is sent in the REGISTRATION ACCEPT message, the UE radio capability ID can or should be considered valid.

[0212] In some embodiments, if the 5GS update type IE is included in the REGISTRATION REQUEST message, with the SMS request bit set to "SMS over NAS supported", and:

[0213] a) the SMSF address is stored in the UE 5GMM context, and:

[0214] 1) the UE is considered available for SMS over NAS; or

[0215] 2) the UE is considered not available for SMS over NAS, and the SMSF has confirmed the activation of SMS service was successful; or

[0216] b) the SMSF address is not stored in the UE 5GMM context, the SMSF selection was successful, and the SMSF has confirmed the activation of SMS service was successful;

[0217] then the AMF can or should set the SMS allowed bit of the 5GS registration result IE in the REGISTRATION ACCEPT message. If the UE 5GMM context does not contain the SMSF address or the UE is not considered available for SMS over NAS, the AMF can or should:

[0218] a) store the SMSF address in the UE 5GMM context if it is not already stored; and

[0219] b) store the value of the SMS allowed bit of the 5GS registration result IE in the UE 5GMM context and consider the UE available for SMS over NAS.

[0220] In some embodiments, if SMSF selection in AMF or SMS activation via SMSF is not successful, or the AMF does not allow the use of SMS over NAS, the AMF can or should set the SMS allowed bit of the 5GS registration result IE to "SMS over NAS not allowed" in the REGISTRATION ACCEPT message.

[0221] In some embodiments, if the 5GS update type IE is included in the REGISTRATION REQUEST message with the SMS request bit set to "SMS over NAS not supported", or the 5GS update type IE is not included in the REGISTRATION REQUEST message, the AMF can or should:

[0222] a) mark the 5GMM context to indicate that the UE is not available for SMS over NAS; and

[0223] b) set the SMS allowed bit of the 5GS registration result IE to "SMS over NAS not allowed" in the REGISTRATION ACCEPT message.

[0224] In some embodiments, the AMF can inform the SMSF that the UE deregistered for SMS over NAS based on local configuration. In some embodiments, when the UE receives the REGISTRATION ACCEPT message, if the UE is also registered to the same PLMN through another access, the UE considers the value indicated by the SMS allowed bit of the 5GS registration result IE applicable for both accesses through which the UE is registered. In some embodiments, if the 5GS update type IE is included in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "NG-RAN radio capability update needed", the AMF can or should delete any stored UE radio capability information for NG-RAN.

[0225] In some embodiments, the AMF can or should include the 5GS registration result IE in the REGISTRATION ACCEPT message. If the 5GS registration result IE value indicates:

[0226] a) "3GPP access", the UE:

[0227] - can or should consider itself registered only to 3GPP access; and

[0228] - if in 5GMM-REGISTERED state over non-3GPP access and on the same PLMN as over 3GPP access, the UE can or shall enter state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION over non-3GPP access and set the 5GS update status to 5U2 NOT UPDATED over non-3GPP access;

[0229] b) "non-3GPP access", then the UE:

[0230] - can or shall consider itself registered only to non-3GPP access; and

[0231] - if in 5GMM-REGISTERED state over 3GPP access and on the same PLMN as over non-3GPP access, the UE can or shall enter state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION over 3GPP access and set the 5GS update status to 5U2 NOT UPDATED over 3GPP access; or

[0232] c) "3GPP access and non-3GPP access", then the UE can or shall consider itself registered to both 3GPP access and non-3GPP access.

[0233] In some embodiments, if the UE is not currently registered for emergency services and the 5GS registration result IE value in the REGISTRATION ACCEPT message is set to "registered for emergency services", the UE can or shall consider itself registered for emergency services and can or shall locally release the PDU session(s) (if any) not associated with emergency services.

[0234] In some embodiments, the AMF can or should include allowed NSSAI for the current PLMN and can or should include, in the REGISTRATION ACCEPT message, the mapped S-NSSAI(s) from the UE for the allowed NSSAI contained in the requested NSSAI (i.e. the Requested NSSAI IE or the Requested mapped NSSAI IE) if available. In some embodiments, if the UE includes the UE status IE with the EMM registration status set to “UE is in EMM-REGISTERED state” in the REGISTRATION REQUEST message and the AMF supports the N26 interface, the S-NSSAI(s) associated with each active PDN connection that supports interworking with 5GS can or should be included in the allowed NSSAI.

[0235] In some embodiments, the AMF can also include the rejected NSSAI in the REGISTRATION ACCEPT message. The rejected NSSAI contains the S-NSSAI(s) included in the requested NSSAI but associated with the rejection reason(s) that are rejected by the network. In some embodiments, if the UE indicates support of network slice specific authentication and authorization and:

[0236] a) if the Requested NSSAI IE includes only S-NSSAI(s) where:

[0237] 1) these S-NSSAI(s) are subject to network slice specific authentication and authorization; and

[0238] 2) network slice specific authentication and authorization procedure has not been initiated for these S-NSSAI(s);

[0239] then the AMF can or should include in the REGISTRATION ACCEPT message:

[0240] 1) a “NSSAA to be performed” indicator in the 5GS registration result IE set to indicate whether network slice specific authentication and authorization procedure will be performed by the network;

[0241] 2) pending NSSAI containing the S-NSSAI(s) for which network slice specific authentication and authorization will be performed; and

[0242] 3) Current registration area in the list of "not allowed tracking areas" in the Service Area List IE; or

[0243] b) If the Requested NSSAI IE includes one or more S-NSSAIs subject to network slice specific authentication and authorization, the AMF can or should include in the REGISTRATION ACCEPT message:

[0244] 1) Allowed NSSAI containing S-NSSAIs or mapped S-NSSAIs that are not subject to network slice specific authentication and authorization or for which network slice specific authentication and authorization has been successfully performed; and

[0245] 2) Pending NSSAI containing one or more S-NSSAIs (if any) for which network slice specific authentication and authorization will be performed.

[0246] In some embodiments, if the UE indicates support for network slice specific authentication and authorization, and if:

[0247] a) the UE does not include Requested NSSAI in the REGISTRATION REQUEST message, or none of the S-NSSAIs in the Requested NSSAI in the REGISTRATION REQUEST message are present in the subscribed S-NSSAIs; and

[0248] b) all S-NSSAIs in the subscribed S-NSSAIs are subject to network slice specific authentication and authorization;

[0249] then the AMF can or should include in the REGISTRATION ACCEPT message:

[0250] a) a "NSSAA to be performed" indicator in the 5GS Registration Result IE to indicate whether a network slice specific authentication and authorization procedure will be performed by the network;

[0251] b) Pending NSSAI containing one or more S-NSSAIs for which network slice specific authentication and authorization will be performed; and

[0252] c) Current registration area in the list of "not allowed tracking areas" in the Service Area List IE.

[0253] In some embodiments, the AMF can include a new configured NSSAI for the current PLMN in the REGISTRATION ACCEPT message if the following conditions are met:

[0254] a) the REGISTRATION REQUEST message does not include a requested NSSAI;

[0255] b) the REGISTRATION REQUEST message includes a requested NSSAI which contains S-NSSAI(s) that are invalid in the serving PLMN;

[0256] c) the REGISTRATION REQUEST message includes a requested NSSAI which contains S-NSSAI(s) with incorrect mapping information to S-NSSAI(s) of the HPLMN;

[0257] d) the REGISTRATION REQUEST message includes a network slice indication IE in which the default configured NSSAI indication bit is set to "requested NSSAI created from default configured NSSAI"; or

[0258] e) the REGISTRATION REQUEST message contains a requested mapped NSSAI.

[0259] In some embodiments, if a new configured NSSAI for the current PLMN is included, the AMF can or should also include in the REGISTRATION ACCEPT message the mapped S-NSSAI(s) for the configured NSSAI for the current PLMN, if available. In such embodiments, the AMF can or should start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED.

[0260] In some embodiments, if the UDM has indicated that the subscription data for a network slice has changed, the AMF can or should include in the REGISTRATION ACCEPT message a network slice indication IE in which the network slice subscription change indication is set to "network slice subscription has changed". In this case, the AMF can or should start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED.

[0261] In some embodiments, if the S-NSSAI(s) associated with the existing PDU session(s) of the UE is not included in the requested NSSAI of the REGISTRATION REQUEST message, the AMF can or should perform the local release of the PDU session(s) associated with the S-NSSAI(s) and can or should request the SMF to perform the local release of these PDU sessions. In some embodiments, the UE receiving the pending NSSAI in the REGISTRATION ACCEPT message can or should store the S-NSSAI. In some embodiments, the UE receiving the rejected NSSAI in the REGISTRATION ACCEPT message takes the following actions based on the rejection reason in the rejected NSSAI:

[0262] “S-NSSAI is not available in the current PLMN or SNPN”: The UE can or should add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN and does not attempt to use the S-NSSAI in the current PLMN until the UE is powered off, the UICC containing the USIM is removed, the entry of the “Subscriber Data List” with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) is removed or deleted.

[0263] “S-NSSAI is not available in the current registration area”: The UE can or should add the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area and does not attempt to use the S-NSSAI in the current registration area until the UE is powered off, the UE moves out of the current registration area, the UICC containing the USIM is removed, the entry of the “Subscriber Data List” with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) is removed or deleted.

[0264] In some embodiments, if the UE sets the NSSAA bit in the 5GMM capability IE to “Network Slice Specific Authentication and Authorization not supported”, and:

[0265] a) If the requested NSSAI IE only includes S-NSSAI subject to network slice specific authentication and authorization and the S-NSSAI(s) of the one or more default subscribed S-NSSAI (containing one or more S-NSSAI, each S-NSSAI can be associated with a new S-NSSAI) is available, the AMF can or should include in the REGISTRATION ACCEPT message:

[0266] 1) Allowed NSSAI containing subscribed S-NSSAI(s) marked as default S-NSSAI(s); and

[0267] 2) Rejected NSSAI containing S-NSSAI(s) subject to network slice specific authentication and authorization with a rejection cause indicating "S-NSSAI is not available in the current PLMN"; or

[0268] b) If the requested NSSAI IE includes one or more S-NSSAI subject to network slice specific authentication and authorization, the AMF can or should include in the REGISTRATION ACCEPT message:

[0269] 1) Allowed NSSAI containing S-NSSAI(s) not subject to network slice specific authentication and authorization or mapped S-NSSAI(s); and

[0270] 2) Rejected NSSAI containing:

[0271] i) S-NSSAI(s) subject to network slice specific authentication and authorization with a rejection cause indicating "S-NSSAI is not available in the current PLMN"; and

[0272] ii) S-NSSAI(s) included in the requested NSSAI but rejected by the network associated with a rejection cause indicating "S-NSSAI is not available in the current PLMN" or a rejection cause indicating "S-NSSAI is not available in the current registration area" if any.

[0273] In some embodiments, for a REGISTRATION REQUEST message with a 5GS registration type IE indicating "mobility registration update", if the UE does not indicate support for network slice specific authentication and authorization and:

[0274] a) The UE is not in NB-N1 mode; and

[0275] b) If:

[0276] 1) The UE did not include requested NSSAI in the REGISTRATION REQUEST message;

[0277] 2) Any S-NSSAI in the requested NSSAI in the REGISTRATION REQUEST message is not present in the subscribed S-NSSAI; or

[0278] 3) all S-NSSAIs in the requested NSSAI in the REGISTRATION REQUEST message are considered to be rejected by the network;

[0279] And the S-NSSAI of one or more subscriptions marked as default is available, the AMF can or should put the S-NSSAI of the subscription marked as default S-NSSAI into the allowed NSSAI of the REGISTRATION ACCEPT message. In some embodiments, the AMF can or should determine the registration area such that all S-NSSAIs of the allowed NSSAI are available in the registration area.

[0280] During the registration procedure for mobility and periodic registration update, the 5GS registration type IE indicates:

[0281] a) "periodic registration update"; or

[0282] b) "mobility registration update" and the UE is in NB-N1 mode;

[0283] The AMF can provide the UE with a new allowed NSSAI in the REGISTRATION ACCEPT message.

[0284] In some embodiments, if the REGISTRATION ACCEPT message contains a network slice indication IE with a network slice subscription change indication set to "network slice subscription changed", the UE can or should delete the network slice information for each PLMN except the current PLMN.

[0285] In some embodiments, if the REGISTRATION ACCEPT message contains an allowed NSSAI, the UE can or should store the included allowed NSSAI together with the PLMN identity and the registration area of the registered PLMN.

[0286] For each of the PDU session(s) active in the UE, if the allowed NSSAI neither contains:

[0287] a) an S-NSSAI matching the S-NSSAI of the PDU session; nor contains

[0288] b) a mapped S-NSSAI matching the mapped S-NSSAI of the PDU session;

[0289] The UE can or should perform a local release of all such PDU sessions except the persistent PDU session(s).

[0290] For each of the PDU session(s) active in the UE, if the allowed NSSAI contains the mapped S-NSSAI matching the mapped S-NSSAI of the PDU session, the UE can or shall update locally the S-NSSAI associated with the PDU session to the corresponding S-NSSAI received in the allowed NSSAI.

[0291] In some embodiments, if the REGISTRATION ACCEPT message contains a configured NSSAI IE, the configured NSSAI IE has a new configured NSSAI for the current PLMN and optionally mapped S-NSSAI(s) for the configured NSSAI of the current PLMN, the UE can or shall store the content of the configured NSSAI IE.

[0292] During a registration procedure for mobility and periodic registration update, the 5GS registration type IE indicates:

[0293] a) "periodic registration update"; or

[0294] b) "mobility registration update" and the UE is in NB-N1 mode;

[0295] If the REGISTRATION ACCEPT message does not contain the allowed NSSAI, the UE considers the previously received allowed NSSAI to be valid.

[0296] In some embodiments, if the uplink data status IE is included in the REGISTRATION REQUEST message:

[0297] a) if the AMF determines that the UE is in a non-allowed area or not in an allowed area, and the PDU session(s) indicated by the uplink data status IE are non-urgent PDU session(s), or the UE is not configured for high priority access in the selected PLMN, the AMF can or shall include in the REGISTRATION ACCEPT message a PDU session reactivation result IE indicating that the user plane resources for the corresponding PDU session(s) cannot be re-established, and can or shall include a PDU session reactivation result error cause IE with the 5GMM cause set to #28 "restricted service area";

[0298] b) otherwise, the AMF can or shall:

[0299] 1) instruct the SMF to re-establish the user plane resources for the corresponding PDU session(s);

[0300] 2) include a PDU Session Re-activation Result IE in the REGISTRATION ACCEPT message to indicate the user plane resource re-establishment result for the PDU Sessions for which the UE requested to re-establish the user plane resources;

[0301] 3) if the corresponding PDU Session is a PDU Session for an LADN, determine the presence of the UE in the LADN service area and forward the presence of the UE in the LADN service area to the SMF.

[0302] In some embodiments, if the Uplink Data Status IE is not included in the REGISTRATION REQUEST message and the REGISTRATION REQUEST message is sent for triggering d), the AMF can indicate to the SMF to re-establish the user plane resources for the PDU Sessions.

[0303] In some embodiments, if the PDU Session Status IE is included in the REGISTRATION REQUEST message, the AMF can or should:

[0304] a) perform a local release of all PDU Sessions in 5GSM state PDU SESSION ACTIVE at the AMF side associated with the access type through which the REGISTRATION REQUEST message is sent but indicated by the UE as in 5GSM state PDU SESSION INACTIVE; and

[0305] b) include a PDU Session Status IE in the REGISTRATION ACCEPT message to indicate which PDU Sessions associated with the access type through which the REGISTRATION REQUEST message is sent are active in the AMF.

[0306] In some embodiments, if the Allowed PDU Session Status IE is included in the REGISTRATION REQUEST message, the AMF can or should:

[0307] a) for each SMF from which only pending downlink signaling is indicated, forward the received 5GSM messages to the UE via the 3GPP access after the REGISTRATION ACCEPT message is sent;

[0308] b) for each SMF from which only pending downlink data is indicated:

[0309] 1) Inform the SMF that re-activation of user plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU Session Status IE; and

[0310] 2) Inform the SMF that re-activation of user plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if the corresponding PDU session ID(s) are indicated in the Allowed PDU Session Status IE.

[0311] c) For each SMF for which pending downlink signaling and data has been indicated:

[0312] 1) Inform the SMF that re-activation of user plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU Session Status IE;

[0313] 2) Inform the SMF that re-activation of user plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if the corresponding PDU session ID(s) are indicated in the Allowed PDU Session Status IE; and

[0314] 3) Discard the received 5GSM message for the PDU session(s) associated with non-3GPP access; and

[0315] d) Include the PDU Session Re-activation Result IE in the REGISTRATION ACCEPT message to indicate the successful re-establishment of user plane resources for the corresponding PDU session, if any.

[0316] In some embodiments, the UE considers the corresponding PDU session to be associated with 3GPP access if the PDU Session Re-activation Result IE is included in the REGISTRATION ACCEPT message indicating that the user plane resources have been successfully re-activated for the PDU session requested by the UE in the Allowed PDU Session Status IE. In some embodiments, the AMF and SMF update the associated access type for the corresponding PDU session if the user plane resources for the PDU session have been successfully re-activated over 3GPP access.

[0317] In some embodiments, if the AMF has included the PDU Session Re-activation Result IE in the REGISTRATION ACCEPT message and there is one or more PDU Sessions for which the user plane resources cannot be re-established, the AMF can include the PDU Session Re-activation Result Error Cause IE to indicate the cause of the failure to re-establish the user plane resources.

[0318] In some embodiments, if the EPS Bearer Context Status IE is included in the REGISTRATION REQUEST message, the AMF processes the received EPS Bearer Context Status IE as specified in, for example, 3GPP TS 23.502.

[0319] In some embodiments, if EPS Bearer Context Status information is generated for the UE during inter-system change from S1 mode to N1 mode as specified in, for example, 3GPP TS 23.502, and the AMF supports the N26 interface, the AMF can or shall include the EPS Bearer Context Status IE in the REGISTRATION ACCEPT message to indicate to the UE which of the mapped EPS Bearer Contexts are active in the network.

[0320] In some embodiments, if the user plane resources cannot be established for a PDU Session, the AMF can or shall include the PDU Session Re-activation Result IE in the REGISTRATION ACCEPT message to indicate that the user plane resources for the corresponding PDU Session cannot be re-established and can or shall include the PDU Session Re-activation Result Error Cause IE with the 5GMM cause set to:

[0321] a) #43 "LADN not available" if the user plane resources cannot be established due to the SMF indicating to the AMF that the UE is outside the LADN service area (see, for example, 3GPP TS 29.502);

[0322] b) #28 "Restricted service area" if the user plane resources cannot be established due to the SMF indicating to the AMF that only prioritized services are allowed (see, for example, 3GPP TS 29.502); or

[0323] c) #92 "User plane resources insufficient for PDU Session" if the user plane resources cannot be established due to the SMF indicating to the AMF that resources are not available in the UPF (see, for example, 3GPP TS 29.502).

[0324] In some embodiments, when to resend the request for user plane re-establishment for the associated PDU session upon receiving a PDU session reactivation result error cause IE with 5GMM cause set to #92 "User plane resources insufficient for PDU session" can depend on UE implementation.

[0325] In some embodiments, if the AMF needs to initiate PDU session status synchronization, the AMF can or should include the PDU session status IE in the REGISTRATION ACCEPT message to indicate to the UE which PDU sessions are active in the AMF.

[0326] The AMF can include the LADN information IE in the REGISTRATION ACCEPT message. The UE, upon receiving the REGISTRATION ACCEPT message with the LADN information IE, can or should delete its old LADN information (if any) and store the received new LADN information.

[0327] In some embodiments, if the AMF does not include the LADN information IE in the REGISTRATION ACCEPT message during the registration procedure for mobility and registration update, the UE can or should delete its old LADN information. In some embodiments, if the PDU session status IE is included in the REGISTRATION ACCEPT message, the UE can or should perform local release of all those PDU sessions that are in 5GSM state PDU SESSION ACTIVE at the UE side but indicated by the AMF to be in 5GSM state PDU SESSION INACTIVE associated with the access type through which the REGISTRATION ACCEPT message is sent.

[0328] In some embodiments, if:

[0329] a) the UE includes the PDU session status IE in the REGISTRATION REQUEST message;

[0330] b) the UE is operating in single registration mode;

[0331] c) the UE is performing an inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode; and

[0332] d) the UE has received the IWK N26 bit set to "Interworking with no N26 interface supported";

[0333] Then, if the PDU Session Status IE is received in the REGISTRATION ACCEPT message, the UE can or shall ignore the PDU Session Status IE.

[0334] In some embodiments, if the EPS Bearer Context Status IE is included in the REGISTRATION ACCEPT message, the UE can or shall locally delete all those QoS Flow Descriptions and all associated QoS Rules (if any) associated with the inactive EPS Bearer Contexts indicated by the AMF in the EPS Bearer Context Status IE. In some embodiments, if the UE includes the S1 mode support indication in the REGISTRATION REQUEST message, the AMF supporting interworking with EPS can or shall set the IWKN 26 bit to:

[0335] a) “No N26 based interworking” if the AMF supports the N26 interface; or

[0336] b) “N26 based interworking supported” if the AMF does not support the N26 interface in the 5GS Network Features support IE in the REGISTRATION ACCEPT message.

[0337] A UE supporting S1 mode can or shall work in the mode for interworking with EPS as follows:

[0338] a) If the IWK N26 bit in the 5GS Network Features support IE is set to “No N26 based interworking”, the UE can or shall work in the single registration mode;

[0339] b) If the IWK N26 bit in the 5GS Network Features support IE is set to “N26 based interworking supported” and the UE supports the dual registration mode, the UE can work in the dual registration mode; or

[0340] c) If the IWK N26 bit in the 5GS Network Features support IE is set to “N26 based interworking supported” and the UE only supports the single registration mode, the UE can or shall work in the single registration mode.

[0341] In some embodiments, the UE can or shall consider the received indication of N26 interface based interworking with EPS for interworking change as valid in the whole PLMN and its equivalent PLMN(s).

[0342] In some embodiments, the network informs the UE about the support of specific features in the 5GS network feature support information element, such as IMS voice over PS session, location services (5G-LCS), emergency services, or emergency services fallback. In a UE with IMS voice over PS session capability, the IMS voice over PS session indicator, the emergency services support indicator, and the emergency services fallback indicator can or should be provided to the upper layers. The upper layers consider the IMS voice over PS session indicator when selecting the access domain for a voice session or call. The upper layers consider the IMS voice over PS session indicator, the emergency services support indicator, and the emergency services fallback indicator when initiating an emergency call. When the UE determines via the IMS voice over PS session indicator that the network does not support IMS voice over PS session in N1 mode, the UE can or should not perform any local release of persistent PDU session if the AMF does not indicate via the PDU session status IE that the PDU session is in 5GSM state PDU SESSION INACTIVE. When the UE determines via the emergency services support indicator that the network does not support emergency services in N1 mode, the UE can or should not perform any local release of emergency PDU session if the AMF does not indicate via the PDU session status IE that the PDU session is in 5GSM state PDU SESSION INACTIVE if the user plane resources associated with this emergency PDU session are established. In a UE with LCS capability, the location services indicator (5G-LCS) can or should be provided to the upper layers.

[0343] In some embodiments, the AMF can or should set the EMF bit in the 5GS network feature support IE to:

[0344] a) “Emergency services fallback supported in NR connected to 5GCN and E-UTRA connected to 5GCN”, if the network supports the emergency services fallback procedure when the UE is in an NR cell connected to 5GCN or in an E-UTRA cell connected to 5GCN;

[0345] b) “Emergency services fallback supported only in NR connected to 5GCN”, if the network supports the emergency services fallback procedure when the UE is in an NR cell connected to 5GCN and the network does not support the emergency services fallback procedure when the UE is in an E-UTRA cell connected to 5GCN;

[0346] c) “Emergency services fallback supported only in E-UTRA connected to 5GCN”, if the network supports the emergency services fallback procedure when the UE is in an E-UTRA cell connected to 5GCN and the network does not support the emergency services fallback procedure when the UE is in an NR cell connected to 5GCN; or

[0347] d) "Emergency services fallback not supported" if the network does not support emergency services fallback procedure when the UE is in any cell connected to 5GCN.

[0348] In some embodiments, if emergency services are not supported in both EPS and 5GS, based on operator policy, the AMF shall set the EMF bit in the 5GS network features support IE to "Emergency services fallback not supported".

[0349] In some embodiments, even if the AMF's support for emergency services fallback is RAT-indicated, the UE's support for emergency services fallback is not RAT-specific, e.g., the UE's support for emergency services fallback is the same for both NR connected to 5GCN and E-UTRA connected to 5GCN.

[0350] In some embodiments, if the UE is not working in SNPN access mode:

[0351] a) The network informs the UE that the use of access identity 1 is valid in the RPLMN or equivalent PLMN by setting the MPS indication bit of the 5GS network features support IE to "Access identity 1 valid" in the REGISTRATION ACCEPT message. Based on operator policy, the AMF sets the MPS indication bit in the REGISTRATION ACCEPT message based on the MPS priority information in the user's subscription context acquired from the UDM;

[0352] b) Upon receiving the REGISTRATION ACCEPT message with the MPS indication bit set to "Access identity 1 valid", the UE can or shall behave as a UE with access identity 1 configured for MPS in all NG-RANs of the registered PLMN and its equivalent PLMNs. The MPS indication bit in the 5GS network features support IE provided in the REGISTRATION ACCEPT message is valid until the UE receives the REGISTRATION ACCEPT message with the MPS indication bit set to "Access identity 1 invalid" or until the UE selects a non-equivalent PLMN. Access identity 1 is only applicable when the UE is in N1 mode;

[0353] c) During an ongoing active PDU session established relying on the MPS indication bit set to "Access identity 1 valid", if the network indicates in the registration update that the MPS indication bit is reset to "Access identity 1 invalid", the UE can or shall no longer behave as a UE with access identity 1 configured for MPS unless the USIM contains a valid configuration for access identity 1 in the RPLMN or equivalent PLMN. In the UE, the ongoing active PDU session is not affected by the change of the MPS indication bit;

[0354] d) The network informs the UE that the use of access identity 2 is valid in the RPLMN or equivalent PLMN by setting the MCS indication bit of the 5GS network features support IE in the REGISTRATION ACCEPT message to "Access Identity 2 Valid". Based on operator policy, the AMF sets the MCS indication bit in the REGISTRATION ACCEPT message based on the MCS priority information in the subscription context of the user obtained from the UDM;

[0355] e) Upon receiving the REGISTRATION ACCEPT message with the MCS indication bit set to "Access Identity 2 Valid", the UE can or shall behave as a UE with access identity 2 configured for MCS in all NG-RANs of the registered PLMN and its equivalent PLMNs. The MCS indication bit in the 5GS network features support IE provided in the REGISTRATION ACCEPT message is valid until the UE receives the REGISTRATION ACCEPT message with the MCS indication bit set to "Access Identity 2 Invalid" or until the UE selects a non-equivalent PLMN. Access identity 2 is only applicable when the UE is in N1 mode; and

[0356] f) During an ongoing active PDU session established relying on the MCS indication bit set to "Access Identity 2 Valid", if the network indicates in the registration update that the MCS indication bit is reset to "Access Identity 2 Invalid", the UE can or shall no longer behave as a UE with access identity 2 configured for MCS unless the USIM contains a valid configuration for access identity 2 in the RPLMN or equivalent PLMN. In the UE, the ongoing active PDU session is not affected by the change of the MCS indication bit.

[0357] In some embodiments, if the UE indicates in the REGISTRATION REQUEST message that it supports restriction on the use of enhanced coverage and the AMF decides to restrict the use of enhanced coverage for the UE, the AMF can or should set the RestrictEC bit to "Use of enhanced coverage restricted" in the 5GS network features support IE in the REGISTRATION ACCEPT message.

[0358] In some embodiments, if the UE is operating in SNPN access mode:

[0359] a) The network informs the UE that the use of access identity 1 is valid in the RS-NPN by setting the MPS indication bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to "access identity 1 valid". Based on operator policy, the AMF sets the MPS indication bit in the REGISTRATION ACCEPT message based on the MPS priority information in the user's subscription context acquired from the UDM;

[0360] b) Upon receiving the REGISTRATION ACCEPT message with the MPS indication bit set to "access identity 1 valid", the UE can or shall behave as a UE with access identity 1 configured for MPS in all NG-RANs of the registered SNPN. The MPS indication bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid until the UE receives a REGISTRATION ACCEPT message with the MPS indication bit set to "access identity 1 invalid" or until the UE selects another SNPN. Access identity 1 is only applicable when the UE is in N1 mode;

[0361] c) During an ongoing active PDU session established relying on the MPS indication bit set to "access identity 1 valid", if the network indicates in the registration update that the MPS indication bit is reset to "access identity 1 invalid", the UE can or shall no longer behave as a UE with access identity 1 configured for MPS unless the unified access control configuration (see e.g. 3GPP TS 23.122) in the "subscriber data list" stored in the ME indicates that the UE is configured for access identity 1 in the RS-NPN. In the UE, the ongoing active PDU session is not affected by the change of the MPS indication bit;

[0362] d) The network informs the UE that the use of access identity 2 is valid in the RS-NPN by setting the MCS indication bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to "access identity 2 valid". Based on operator policy, the AMF sets the MCS indication bit in the REGISTRATION ACCEPT message based on the MCS priority information in the user's subscription context acquired from the UDM;

[0363] e) Upon receiving a REGISTRATION ACCEPT message with the MCS indication bit set to "Access Identity 2 is valid", the UE can or shall behave as a UE with Access Identity 2 configured for MCS in all NG-RANs of the registered SNPN. The MCS indication bit in the 5GS network features support IE provided in the REGISTRATION ACCEPT message is valid until the UE receives a REGISTRATION ACCEPT message with the MCS indication bit set to "Access Identity 2 is not valid" or until the UE selects another SNPN. Access Identity 2 is only applicable when the UE is in N1 mode; and

[0364] f) During an ongoing active PDU session established relying on the MCS indication bit set to "Access Identity 2 is valid", if the network indicates in the registration update that the MCS indication bit is reset to "Access Identity 2 is not valid", the UE can or shall no longer behave as a UE with Access Identity 2 configured for MCS, unless the unified access control configuration (see e.g. 3GPP TS 23.122) in the "Subscriber Data List" stored in the ME indicates that the UE is configured for Access Identity 2 in the RSNPN. In the UE, the ongoing active PDU session is not affected by the change of the MCS indication bit.

[0365] In some embodiments, the AMF can or shall not release the NAS signaling connection immediately after completing the registration procedure, if the UE has set the subsequent request indicator to "subsequent request pending" in the REGISTRATION REQUEST message or the network has downlink signaling pending.

[0366] In some embodiments, the UE is authorized to use vehicle-to-anything (V2X) communication over the PC5 reference point or interface based on:

[0367] a) At least one of the following bits set by the UE in the 5GMM capability IE of the REGISTRATION REQUEST message or in the 5GMM context already stored in the AMF during a previous registration procedure:

[0368] 1) V2X CE PC5 bit set to "V2X communication over E-UTRA-PC5 is supported"; or

[0369] 2) V2X CN PC5 bit set to "V2X communication over NR-PC5 is supported"; and

[0370] b) The user's subscription context as acquired from the UDM as defined in e.g. 3GPP TS 23.287;

[0371] The AMF shall not release the NAS signaling connection immediately after completing the registration procedure.

[0372] In some embodiments, if the requested DRX [Discontinuous Reception] parameter IE is included in the REGISTRATION REQUEST message, the AMF can or should include the negotiated DRX parameter IE in the REGISTRATION ACCEPT message. The AMF can set the negotiated DRX parameter IE based on the received requested DRX parameter IE and operator policy, if available.

[0373] In some embodiments, the AMF can or should include the negotiated extended DRX parameter IE in the REGISTRATION ACCEPT message only if the requested extended DRX parameter IE is included in the REGISTRATION REQUEST message and the AMF supports and accepts the use of eDRX. The AMF can set the negotiated extended DRX parameter IE based on the received requested extended DRX parameter IE, operator policy, and the user’s subscription context obtained from the UDM, if available.

[0374] In some embodiments, if the UE includes the UE state information IE with the Enterprise Mobility Management (EMM) registration state set to “UE is in EMM-REGISTERED state” in the REGISTRATION REQUEST message and the AMF does not support the N26 interface, the AMF can or should operate as described in, for example, 3GPP TS 24.501 or 3GPP TS 29.502.

[0375] In some embodiments, if the UE has indicated support for service gap control in the REGISTRATION REQUEST message, the service gap time value is available in the 5GMM context, the AMF can include the T3447 value IE set to the service gap time value in the REGISTRATION ACCEPT message.

[0376] In some embodiments, if the UE requests an encryption key for encrypted broadcast assistance data in the REGISTRATION REQUEST message and the AMF has valid encryption key data applicable to the UE’s subscription and the current tracking area, the AMF can or should include the encryption key data in the encryption key data IE of the REGISTRATION ACCEPT message.

[0377] In some embodiments, if the UE is not allowed to access the TA due to regional subscription restrictions or access restrictions, but the UE has established an emergency PDU session, the AMF can accept the REGISTRATION REQUEST message and indicate to the SMF to release all non-emergency PDU sessions when initiating the registration procedure in 5GMM-CONNECTED mode. When initiating the registration procedure in 5GMM-IDLE mode, the AMF indicates to the SMF to release all non-emergency PDU sessions and informs the UE via the PDU Session Status IE in the REGISTRATION ACCEPT message. The AMF can not or shall not indicate to the SMF to release the emergency PDU session. The network can or shall behave as if the UE is registered for emergency services.

[0378] In some embodiments, if the REGISTRATION ACCEPT message includes the PDU Session Re-activation Result Error Cause IE with the 5GMM cause set to #28 "Restricted Service Area", the UE can or shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE and behave as specified in, for example, 3GPP TS 24.501 or 3GPP TS 29.502.

[0379] In some embodiments, if the REGISTRATION ACCEPT message includes the SOR transparent container IE and:

[0380] a) the SOR transparent container IE fails the integrity check (see, for example, 3GPP TS 33.501); and

[0381] b) if the UE attempts to acquire services on another PLMN, as specified in, for example, 3GPP TS 23.122;

[0382] then the UE can or shall release the established NAS signaling connection locally after sending the REGISTRATION COMPLETE message.

[0383] In some embodiments, if the REGISTRATION ACCEPT message includes the SOR transparent container IE and the SOR transparent container IE passes the integrity check (see, for example, 3GPP TS 33.501):

[0384] a) the UE can or shall continue the behavior as specified in, for example, 3GPP TS 23.122; and

[0385] b) If the registration procedure is performed over 3GPP access and the UE attempts to get services on another PLMN (as specified in e.g. 3GPP TS 23.122), the UE can locally release the established NAS signaling connection after sending the REGISTRATION COMPLETE message. Otherwise, the UE can or shall send the REGISTRATION COMPLETE message and will not locally release the current N1 NAS signaling connection. If confirmation is requested in the SOR transparent container IE of the REGISTRATION ACCEPT message, the UE confirms in the SOR transparent container IE of the REGISTRATION COMPLETE message.

[0386] In some embodiments, if the SOR transparent container IE passes the integrity check (see e.g. 3GPP TS 33.501) successfully, indicates a list of preferred PLMN / access technology combinations is provided, and the list type indicates:

[0387] a) “PLMN ID and access technology list”, the ME can or shall replace the highest priority entry in the “Operator Controlled PLMN Selector with Access Technology” list stored in the ME and can or shall continue the behavior as specified in e.g. 3GPP TS 23.122; or

[0388] b) “Security data package”, the ME can or shall behave as if an SMS is received with the protocol identifier set to SIM data download, the data coding scheme set to class 2 message, and the SMS payload as the security data package content of the SOR transparent container IE. The SMS payload is forwarded to the UICC as specified in e.g. 3GPP TS 23.040 and the ME can or shall continue the behavior as specified in e.g. 3GPP TS 23.122.

[0389] In some embodiments, the AMF can or shall include the NSSAI inclusion mode IE (see e.g. 3GPP TS 24.501 or 3GPP TS 29.502) in the REGISTRATION ACCEPT message if required by operator policy. Upon reception of the REGISTRATION ACCEPT message:

[0390] a) If the message includes the NSSAI inclusion mode IE, the UE can or shall work in the NSSAI inclusion mode indicated in the NSSAI inclusion mode IE on the current access within the current PLMN and its equivalent PLMN(s) (if any) in the current registration area; or

[0391] b) Otherwise, if:

[0392] 1) The UE has a NSSAI inclusion mode for the current PLMN and the access type stored in the UE, the UE can or shall work in the stored NSSAI inclusion mode; or

[0393] 2) The UE does not have a NSSAI inclusion mode for the current PLMN and the access type stored in the UE, and if the UE is performing the registration procedure by:

[0394] i) 3GPP access, the UE can or shall work in the NSSAI inclusion mode D in the current PLMN and the current access type; or

[0395] ii) Non-3GPP access, the UE can or shall work in the NSSAI inclusion mode C in the current PLMN and the current access type.

[0396] The AMF can include the operator-defined access category definition in the REGISTRATION ACCEPT message.

[0397] In some embodiments, if there is a running T3447 timer in the AMF and the uplink data status IE is included in the REGISTRATION REQUEST message or the subsequent request indicator is set to "subsequent request pending", the AMF can or shall ignore the uplink data status IE or the subsequent request indicator set to "subsequent request pending" and continue as if the uplink data status IE or the subsequent request indicator was not received set to "subsequent request pending", except for the following cases:

[0398] - The PDU session(s) indicated by the uplink data status IE is / are emergency PDU session(s);

[0399] - The UE is configured for high priority access in the selected PLMN;

[0400] - The REGISTRATION REQUEST message is as a paging response; or

[0401] - The UE is establishing an emergency PDU session or performing emergency service fallback.

[0402] In some embodiments, if the UE receives an operator-defined access category definition IE in the REGISTRATION ACCEPT message and the operator-defined access category definition IE contains one or more operator-defined access category definitions, the UE can or should delete any operator-defined access category definitions stored for the RPLMN and can or should store the received operator-defined access category definitions for the RPLMN. In some embodiments, if the UE receives an operator-defined access category definition IE in the REGISTRATION ACCEPT message and the operator-defined access category definition IE does not contain an operator-defined access category definition, the UE can or should delete any operator-defined access category definitions stored for the RPLMN. If the REGISTRATION ACCEPT message does not contain an operator-defined access category definition IE, the UE can or should not delete any operator-defined access category definitions stored for the RPLMN.

[0403] In some embodiments, if the UE has indicated support for service gap control in the REGISTRATION REQUEST message and:

[0404] - the REGISTRATION ACCEPT message contains a T3447 value IE, then the UE can or should store the new T3447 value, erase any previously stored T3447 value (if present), and use the new T3447 value at the next start of timer T3447; or

[0405] - the REGISTRATION ACCEPT message does not contain a T3447 value IE, then the UE can or should erase any previously stored T3447 value (if present) and stop timer T3447 (if running).

[0406] In some embodiments, if the UE has set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the REGISTRATION ACCEPT message includes:

[0407] a) the UE Radio Capability ID Removal indication IE is set to "UE Radio Capability ID Removal requested by network", then the UE can or shall remove any network-assigned UE Radio Capability ID stored at the UE that is associated with the RPLMN or RSNPN, and then the UE can or shall initiate the registration procedure for mobility and periodic registration update as specified in, for example, 3GPP TS 24.501 or 3GPP TS 29.502. In some embodiments, if the UE has a manufacturer-assigned UE Radio Capability ID applicable to the current UE configuration, the UE can or shall include the manufacturer-assigned UE Radio Capability ID in the UE Radio Capability ID IE of the REGISTRATION REQUEST message; and

[0408] b) the UE Radio Capability ID IE, then the UE can or shall store the UE Radio Capability ID.

[0409] The UE is not using 5GS services with control plane CIoT 5GS optimization.

[0410] In some embodiments, if the UE has an emergency PDU session, the AMF can or shall accept the SERVICE REQUEST message even if the UE is not under CAG access control. In some embodiments, if a UE not under CAG access control has an emergency PDU session, the AMF can or shall perform local release of all non-emergency PDU sessions associated with 3GPP access and can or shall request the SMF to perform local release of all those non-emergency PDU sessions.

[0411] For cases other than h), the UE can or shall consider the reception of the SERVICE ACCEPT message as successful completion of the procedure. The UE can or shall reset the service request attempt counter, stop timer T3517, and enter state 5GMM-REGISTERED.

[0412] For case h),

[0413] a) the UE can or shall consider an indication from lower layers as successful completion of the procedure and stop timer T3517 when the UE has changed to S1 mode or is connected to an E-UTRA of a 5GCN (see, for example, 3GPP TS 23.502);

[0414] b) if the UE working in single-registration mode has changed to S1 mode, it can or shall disable N1 mode capability for 3GPP access; and

[0415] c) the AMF can or shall not perform CAG access control.

[0416] In some embodiments, if the AMF needs to initiate PDU session status synchronization or the PDU session status IE is included in the SERVICE REQUEST message, the AMF can or should include the PDU session status IE in the SERVICE ACCEPT message to indicate which PDU sessions associated with the access type through which the SERVICE ACCEPT message is sent are active in the AMF. In some embodiments, if the PDU session status information element is included in the SERVICE ACCEPT message, the UE can or should perform local release of all those PDU sessions that are active at the UE side but are indicated as inactive by the AMF associated with the access type through which the SERVICE ACCEPT message is sent.

[0417] In some embodiments, if the uplink data status IE is included in the SERVICE REQUEST message, the AMF can or should:

[0418] a) instruct the SMF to re-establish user plane resources for the corresponding PDU session;

[0419] b) include the PDU session reactivation result IE in the SERVICE ACCEPT message to indicate the user plane resource re-establishment result for the PDU session for which the UE requested re-establishment of user plane resources; and

[0420] c) if the corresponding PDU session is a PDU session for a LADN, determine the presence of the UE in the LADN service area and forward the presence of the UE in the LADN service area to the SMF.

[0421] In some embodiments, if the allowed PDU session status IE is included in the SERVICE REQUEST message, the AMF can or should:

[0422] a) for each 5GSM message from an SMF for which only pending downlink signaling has been indicated, forward the received 5GSM message to the UE via 3GPP access after the SERVICE ACCEPT message is sent;

[0423] b) for each SMF for which only pending downlink data has been indicated:

[0424] 1) inform the SMF that reactivation of user plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the allowed PDU session status IE; and

[0425] 2) Inform the SMF: If the corresponding PDU Session ID(s) are indicated in the Allowed PDU Session Status IE, then the reactivation of the user plane resources for the corresponding PDU Session(s) associated with non-3GPP access can be performed.

[0426] c) For each SMF that has indicated pending downlink signaling and data:

[0427] 1) Inform the SMF: If the corresponding PDU Session ID(s) are not indicated in the Allowed PDU Session Status IE, then the reactivation of the user plane resources for the corresponding PDU Session(s) associated with non-3GPP access cannot be performed;

[0428] 2) Inform the SMF: If the corresponding PDU Session ID(s) are indicated in the Allowed PDU Session Status IE, then the reactivation of the user plane resources for the corresponding PDU Session(s) associated with non-3GPP access can be performed; and

[0429] 3) Discard the received 5GSM message for the PDU Session(s) associated with non-3GPP access; and

[0430] d) Include the PDU Session Re-activation Result IE in the SERVICE ACCEPT message to indicate the successfully re-established user plane resources for the corresponding PDU Session, if any.

[0431] In some embodiments, if the PDU Session Re-activation Result IE is included in the SERVICE ACCEPT message to indicate that the user plane resources have been successfully reactivated for the PDU Session requested by the UE in the Allowed PDU Session Status IE, the UE considers the corresponding PDU Session to be associated with 3GPP access. If the user plane resources for the PDU Session have been successfully reactivated over 3GPP access, the AMF and SMF update the associated access type for the corresponding PDU Session.

[0432] In some embodiments, if the user plane resources cannot be established for the PDU Session, the AMF can or should include the PDU Session Re-activation Result IE in the SERVICE ACCEPT message to indicate that the user plane resources for the corresponding PDU Session cannot be re-established and can or should include the PDU Session Re-activation Result Error Cause IE with the 5GMM cause set to:

[0433] a) #43 "LADN not available" if user plane resources cannot be established due to the SMF indicating to the AMF that the UE is outside the LADN service area (see, for example, 3GPP TS 29.502);

[0434] b) #28 "restricted service area" if user plane resources cannot be established due to the SMF indicating to the AMF that only prioritized services are allowed (see, for example, 3GPP TS 29.502); or

[0435] c) #92 "user plane resources insufficient for PDU session" if user plane resources cannot be established due to the SMF indicating to the AMF that resources are not available in the UPF (see, for example, 3GPP TS 29.502).

[0436] In some embodiments, when to resend the request for user plane re-establishment for the associated PDU session after receiving a PDU session reactivation result error cause IE with the 5GMM cause set to #92 "user plane resources insufficient for PDU session" can depend on the UE implementation.

[0437] In some embodiments, if the SERVICE REQUEST message is for emergency service fallback, the AMF triggers the emergency service fallback procedure, for example, as specified in, for example, 3GPP TS 23.502.

[0438] In some embodiments, if a UE with an emergency PDU session sends a SERVICE REQUEST message via:

[0439] a) a CAG cell, and none of the CAG-IDs of this CAG cell are included in the "allowed CAG list" for the current PLMN in the UE's subscription; or

[0440] b) a non-CAG cell in a PLMN for which the UE's subscription contains an "indication that the UE is only allowed to access the 5GS via CAG cells";

[0441] then the network can or shall accept the SERVICE REQUEST message and locally release all non-emergency PDU sessions. The emergency PDU session can not or shall not be released.

[0442] In some embodiments, a request to establish a non-emergency PDU session comes from a UE that is only allowed to access a PLMN via CAG cells or a UE that needs to be rejected by an unallowed CAG cell. However, no such mechanism is available. Since the SMF has no CAG information, it needs to be handled by the AMF.

[0443] In some embodiments, if the UE is served by:

[0444] a non-CAG cell of the PLMN via which the UE is only allowed to access CAG cells; or

[0445] an unallowed CAG cell;

[0446] then the UE sends an UL NAS TRANSPORT message containing a message requesting establishment of a non-emergency PDU session, which the AMF rejects by sending a DL NAS TRANSPORT message including the PDU session ID, the request message, and 5GMM cause #76 "not authorized for this CAG or only for CAG cells".

[0447] Upon receiving the DL NAS TRANSPORT message, the UE stops timer T3580 and aborts the PDU session establishment procedure.

[0448] In some embodiments, if the UE is served by:

[0449] a non-CAG cell of the PLMN via which the UE is only allowed to access CAG cells; or

[0450] an unallowed CAG cell;

[0451] then an UL NAS TRANSPORT message containing a message requesting establishment of a non-emergency PDU session is sent, which the AMF rejects by sending a DL NAS TRANSPORT message including the PDU session ID, the request message, and 5GMM cause #76 "not authorized for this CAG or only for CAG cells".

[0452] Upon receiving the DL NAS TRANSPORT message, the UE stops timer T3580 and aborts the PDU session establishment procedure.

[0453] In some embodiments, the following exceptional cases in the AMF are identified:

[0454] a) if the Payload Container Type IE is set to "N1 SM Information" and:

[0455] 1) If the old PDU Session ID IE is not included in the UL NAS TRANSPORT message, the AMF does not have a PDU Session Routing Context for the PDU Session ID and the UE, the Request Type IE is set to "Initial Request" or "MAPDU Request", and the SMF selection fails, the AMF can or shall send back to the UE the 5GSM message that was not forwarded, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502;

[0456] 2) If the old PDU Session ID IE is included in the UL NAS TRANSPORT message, the AMF has a PDU Session Routing Context for the old PDU Session ID and the UE and does not have a PDU Session Routing Context for the PDU Session ID and the UE, the Request Type IE is set to "Initial Request", the AMF receives a reallocation request indication from the SMF indicating that the SMF is going to be reallocated, and the SMF selection fails, the AMF can or shall send back to the UE the 5GSM message that was not forwarded, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502;

[0457] 3) If the AMF does not have a PDU Session Routing Context for the PDU Session ID and the UE, the Request Type IE is set to "Existing PDU Session" or "MAPDU Request", and the user's subscription context retrieved from the UDM does not contain an SMF ID for a PDU Session ID matching the PDU Session ID received from the UE or for a DNN matching the DNN received from the UE, such that the SMF ID includes a PLMN identity corresponding to the HPLMN or the current PLMN of the UE, the AMF can send back to the UE the 5GSM message that was not forwarded, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0458] 4) If the old PDU Session ID IE is included in the UL NAS TRANSPORT message, and the AMF has a PDU Session Routing Context for the old PDU Session ID and the UE and does not have a PDU Session Routing Context for the PDU Session ID and the UE, the Request Type IE is set to "Initial Request", and the AMF has not received a reallocation request indication, the AMF shall select a SMF with the following handling:

[0459] In some embodiments, if the S-NSSAI IE is not included, and the user's subscription context retrieved from the UDM:

[0460] i) contains one default S-NSSAI, then the AMF can or should use the default S-NSSAI as the S-NSSAI;

[0461] ii) contains two or more default S-NSSAIs, then the AMF can or should use one of the default S-NSSAIs selected by the operator policy as the S-NSSAI; and

[0462] iii) contains no default S-NSSAI, then the AMF can or should use an S-NSSAI selected based on the operator policy as the S-NSSAI.

[0463] In some embodiments, if the DNN IE is not included and the user's subscription context is obtained from the UDM:

[0464] i) contains a default DNN for the S-NSSAI, then the AMF can or should use the default DNN as the DNN; and

[0465] ii) contains no default DNN for the S-NSSAI, then the AMF can or should use a locally configured DNN as the DNN; and

[0466] In some embodiments, if the DNN selected by the network is a LADN DNN, the AMF can or should determine the presence of the UE in the LADN service area.

[0467] In some embodiments, if the SMF selection is successful, the AMF should store the PDU session routing context for the PDU session ID and the UE, set the SMF ID in the stored PDU session routing context to the selected SMF ID, and forward the 5GSM message, PDU session ID, old PDU session ID, S-NSSAI, mapped S-NSSAI (if available in roaming scenarios), DNN determined by the AMF, DNN selected by the network (if different from the DNN determined by the AMF), request type, and presence of the UE in the LADN service area (if there is a network-selected DNN corresponding to a LADN DNN) to the SMF ID of the PDU session routing context.

[0468] In some embodiments, if the SMF selection fails, the AMF can or should send the 5GSM message that was not forwarded back to the UE, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0469] 5) If the AMF has a PDU Session Routing Context for the PDU Session ID and the UE, the PDU Session Routing Context indicates that the PDU Session is an emergency PDU Session, the Request Type IE is set to "Initial Emergency Request", the AMF shall forward the 5GSM message, the PDU Session ID, the S-NSSAI (if configured in the AMF Emergency Configuration Data), the DNN (if configured in the AMF Emergency Configuration Data) and the Request Type to the SMF ID of the PDU Session Routing Context.

[0470] 6) If the Request Type IE is set to "Initial Emergency Request" and the S-NSSAI or DNN is received, the AMF ignores the received S-NSSAI or DNN and uses the emergency DNN from the AMF Emergency Configuration Data, if any.

[0471] 7) If the AMF does not have a PDU Session Routing Context for the PDU Session ID and the UE, and the Request Type IE of the UL NAS TRANSPORT message is not provided or is provided but set to a value other than "Initial Request", "Existing PDU Session", "Initial Emergency Request", "Existing Emergency PDU Session" and "MAPDU Request", the AMF can send the unforwarded 5GSM message back to the UE, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0472] 8) If the AMF does not successfully attempt to forward the 5GSM message, the PDU Session ID, the S-NSSAI, the mapped S-NSSAI (if available in roaming scenarios), the DNN and the Request Type (if received) to the SMF ID, the AMF can send the unforwarded 5GSM message back to the UE, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0473] 9) The old PDU Session ID IE is included in the UL NAS TRANSPORT message, the AMF does not have a PDU Session Routing Context for the old PDU Session ID and the UE, the AMF does not have a PDU Session Routing Context for the PDU Session ID and the UE, the Request Type IE is set to "Initial Request", the AMF shall select the SMF with the following processing.

[0474] In some embodiments, if the S-NSSAI IE is not included and the subscription context of the user is obtained from the UDM:

[0475] i) contains one default S-NSSAI, the AMF can or shall use the default S-NSSAI as the S-NSSAI;

[0476] ii) contains two or more default S-NSSAIs, then the AMF can or should use one of the default S-NSSAIs selected by operator policy as the S-NSSAI; and

[0477] iii) does not contain a default S-NSSAI, then the AMF can or should use an S-NSSAI selected based on operator policy as the S-NSSAI.

[0478] In some embodiments, if the DNN IE is not included and the user subscription context is obtained from the UDM:

[0479] i) contains a default DNN for the S-NSSAI, then the AMF can or should use the default DNN as the DNN; and

[0480] ii) does not contain a default DNN for the S-NSSAI, then the AMF can or should use a locally configured DNN as the DNN; and

[0481] In some embodiments, if the DNN selected by the network is a LADN DNN, then the AMF can or should determine the presence of the UE in the LADN service area.

[0482] In some embodiments, if the SMF selection is successful, the AMF shall store the PDU session routing context for the PDU session ID and the UE, set the SMF ID in the stored PDU session routing context to the selected SMF ID, and forward the 5GSM message, PDU session ID, old PDU session ID, S-NSSAI, mapped S-NSSAI if available in roaming scenario, DNN determined by the AMF, DNN selected by the network if different from the DNN determined by the AMF, request type, and presence of the UE in the LADN service area if there is a network selected DNN corresponding to a LADN DNN, to the SMF ID of the PDU session routing context.

[0483] In some embodiments, if the SMF selection fails, the AMF can or should send the 5GSM message that was not forwarded back to the UE, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0484] 10) If the AMF has a PDU Session Routing Context for the PDU Session ID and the UE, the PDU Session Routing Context indicates that the PDU Session is not an emergency PDU Session, and the Request Type IE is included and set to "Existing Emergency PDU Session", the AMF can send the unforwarded 5GSM message back to the UE, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0485] 11) If the AMF has a PDU Session Routing Context for the PDU Session ID and the UE, the PDU Session Routing Context indicates that the PDU Session is an emergency PDU Session, and the Request Type IE is included and set to "Existing PDU Session", the AMF can forward the 5GSM message, the PDU Session ID, the S-NSSAI (if configured in the AMF Emergency Configuration Data), the DNN (if configured in the AMF Emergency Configuration Data), and the Request Type to the SMF identified by the SMF ID of the PDU Session Routing Context.

[0486] 12) If the AMF has a PDU Session Routing Context for the PDU Session ID and the UE, the Request Type IE is set to "Initial Request", the AMF can or shall perform a local release of the PDU Session identified by the PDU Session ID, and can or shall request the SMF to perform a local release of the PDU Session, and continue, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0487] 13) If the Request Type IE is set to "Initial Request", and the S-NSSAI IE contains an S-NSSAI that is not allowed by the network, the AMF can or shall send the unforwarded 5GSM message back to the UE, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0488] 14) If the Request Type IE is set to "Existing PDU Session", the AMF has a PDU Session Routing Context for the PDU Session ID and the UE, the PDU Session Routing Context indicates that the PDU Session is not an emergency PDU Session, and the S-NSSAI associated with the PDU Session identified by the PDU Session ID is not allowed for the target access type, the AMF can or shall send the unforwarded 5GSM message back to the UE, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0489] 15) If the Request Type IE is set to "Initial Request", "Existing PDU Session", "Modification Request" or "MA PDU Request", the UE is not configured for high priority access in the selected PLMN, and the UE is in a non-allowed area or not in an allowed area, the AMF can or should send back to the UE the 5GSM message that was not forwarded and 5GMM cause #28 "Restricted Service Area", e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0490] 16) If the Request Type IE is set to "Initial Request" or "MA PDU Request", the AMF is waiting to receive a REGISTRATION REQUEST message indicating "Mobility Registration Update" in the 5GS Registration Type IE, and there is an emergency PDU session for the UE (see, e.g., 3GPP TS 24.501 or 3GPP TS 29.502), the AMF can or should send back to the UE the 5GSM message that was not forwarded, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0491] 17) If timer T3447 is running and the UE supports service gap control:

[0492] i) the UE is not configured for high priority access in the selected PLMN;

[0493] ii) the current NAS signaling connection is not triggered by paging; and

[0494] iii) no mobile terminated signaling has been sent or no user plane resources have been established for any PDU session since the current NAS signaling connection was established,

[0495] the AMF can or should send back to the UE the 5GSM message that was not forwarded, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0496] 18) If the AMF has a PDU Session Routing Context for the PDU Session ID and the UE, the Request Type IE is not included, the UE is not configured for high priority access in the selected PLMN, and the PDU Session is not an emergency PDU Session, the AMF can or should forward the 5GSM message and PDU Session ID IE to the SMF identified by the SMF ID of the PDU Session Routing Context with the following attributes:

[0497] i) an exemptionInd attribute indicating that the message is exempted from DNN-based congestion activated in the AMF, e.g., as specified in 3GPP TS 29.502, if DNN-based congestion control is activated for the selected DNN;

[0498] ii) an exemptionInd attribute indicating that the message is exempted from S-NSSAI and DNN-based congestion activated in the AMF, e.g., as specified in 3GPP TS 29.502, if S-NSSAI and DNN-based congestion control is activated for the selected S-NSSAI and the selected DNN; or

[0499] iii) an exemptionInd attribute indicating that the message is exempted from S-NSSAI-only congestion activated in the AMF, as specified in 3GPP TS 29.502, if S-NSSAI-only congestion control is activated for the selected S-NSSAI.

[0500] 19) If the Request Type IE is set to "MAPDU Request" and the S-NSSAI IE contains an S-NSSAI that is not allowed by the network on any access, the AMF can or shall send the 5GSM message to the UE without being forwarded, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0501] 20) If the Request Type IE is set to neither "Initial Emergency Request" nor "Existing Emergency PDU Session", the UE sends the UL NAS TRANSPORT message via:

[0502] i) a CAG cell and none of the CAG-ID(s) supported by this CAG cell is included in the UE's "Allowed CAG List" for the current PLMN; or

[0503] ii) a non-CAG cell and the entry of the UE's "CAG Information List" for the current PLMN includes an "Indication that the UE is only allowed to access the 5GS via CAG cells";

[0504] then the AMF can or shall send the 5GSM message to the UE without being forwarded, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0505] b) If the Payload Container Type IE is set to "SMS" and the AMF does not have an SMSF address associated with the UE or the AMF is unable to forward the contents of the Payload Container IE to an SMSF associated with an SMSF address available in the AMF, the AMF can or should abort the procedure.

[0506] c) If the Payload Container Type IE is set to "LTE Positioning Protocol (LPP) Message Container" and if the Additional Information IE is not included in the UL NAS TRANSPORT message or the AMF is unable to forward the contents of the Payload Container IE to an LMF associated with the routing information included in the Additional Information IE, the AMF can or should abort the procedure.

[0507] d) If the Payload Container Type IE is set to "UE Policy Container" and the AMF does not have a PCF address associated with the UE or the AMF is unable to forward the contents of the Payload Container IE to a PCF associated with a PCF address available in the AMF, the AMF can or should abort the procedure.

[0508] e) If the Payload Container Type IE is set to "Location Services Message Container" and if the Additional Information IE is included in the UL NAS TRANSPORT message and the AMF is unable to forward the contents of the Payload Container IE to an LMF associated with the routing information included in the Additional Information IE, the AMF can or should abort the procedure.

[0509] f) If the Payload Container Type IE is set to "SMS" or "LTE Positioning Protocol (LPP) Message Container":

[0510] 1) Timer T3447 is running and the UE supports service gap control;

[0511] 2) The UE is not configured for high priority access in the selected PLMN;

[0512] 3) The current NAS signaling connection is not triggered by paging; and

[0513] 4) No mobile terminated signaling has been sent or no user plane resources have been established for any PDU session since the current NAS signaling connection was established, or the UE in 5GMM-CONNECTED mode receives mobile terminated signaling or downlink data over the user plane,

[0514] then the AMF can or should abort the procedure.

[0515] In some embodiments, in this state, the network can release the N1 NAS signaling connection.

[0516] g) if the Payload Container Type IE is set to "CIoT User Data Container" and:

[0517] 1) if the AMF does not have a PDU Session Routing Context for the PDU Session ID and the UE; or

[0518] 2) if the AMF has unsuccessfully attempted to forward the User Data Container and the PDU Session ID,

[0519] then the AMF can send the unforwarded CIoT User Data Container back to the UE, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0520] h) if the Payload Container Type IE is set to "CIoT User Data Container":

[0521] 1) if timer T3447 is running and the UE supports service gap control;

[0522] 2) the UE is not configured for high priority access in the selected PLMN;

[0523] 3) the current N1 NAS signaling connection is not triggered by paging; and

[0524] 4) no mobile terminated signaling has been sent or no user plane resources have been established for any PDU Session since the current NAS signaling connection was established,

[0525] then the AMF can or shall send the unforwarded CIoT User Data Container back to the UE, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0526] The purpose of the network initiated NAS transport procedure is to provide transport for:

[0527] a) a single 5GSM message;

[0528] b) a short message;

[0529] c) an LPP message;

[0530] d) a SOR transparent container;

[0531] e) a single uplink 5GSM message that was not forwarded due to routing failure;

[0532] f) a single uplink 5GSM message that was not forwarded due to congestion control;

[0533] g) a UE policy container;

[0534] h) single uplink 5GSM message not forwarded because maximum number of PDU sessions for the PLMN has been reached;

[0535] i) single uplink 5GSM message not forwarded due to service area restrictions;

[0536] ia) single uplink 5GSM message not forwarded due to CAG;

[0537] j) UE parameter update transparent container;

[0538] k) location service message;

[0539] l) CIoT user data container;

[0540] li) single uplink CIoT user data container not forwarded due to routing failure;

[0541] l2) single uplink CIoT user data container not forwarded due to congestion control; or

[0542] m) multiple of the above types in a 5GMM message from the AMF to the UE.

[0543] In some embodiments, the AMF initiates the NAS transport procedure by sending a DL NAS TRANSPORT message when the UE is in 5GMM-CONNECTED mode.

[0544] In case a), e.g., upon receiving a 5GSM message for the UE without N1 SM delivery skip allowed indication or a 5GSM message for the UE in 5GMM-CONNECTED mode with N1 SM delivery skip allowed indication from the SMF, the AMF can or should:

[0545] a) include PDU session information (PDU session ID) in the PDU session ID IE;

[0546] b) set the payload container type IE to "N1 SM information"; and

[0547] c) set the payload container IE to the 5GSM message.

[0548] In case b), e.g., upon receiving an SMS payload from the SMSF, the AMF can or should:

[0549] a) set the payload container type IE to "SMS";

[0550] b) set the payload container IE to the SMS payload; and

[0551] c) In case access type selection is needed, the access type is selected to deliver the DL NAS TRANSPORT message as follows:

[0552] 1) If the UE that is to receive the DL NAS TRANSPORT message is registered to the network via both 3GPP access and non-3GPP access, the UE's 5GMM context indicates that SMS over NAS is allowed, the UE is in MICO mode, and the UE is in 5GMM-IDLE mode for 3GPP access and in 5GMM-CONNECTED mode for non-3GPP access, the AMF selects non-3GPP access. Otherwise, the AMF selects 3GPP access or non-3GPP access.

[0553] In some embodiments, the AMF can re-send the DL NAS TRANSPORT message over non-3GPP access if the delivery of the DL NAS TRANSPORT message over 3GPP access fails.

[0554] In some embodiments, the AMF can re-send the DL NAS TRANSPORT message over 3GPP access if the delivery of the DL NAS TRANSPORT message over non-3GPP access fails; and

[0555] 2) Otherwise, the AMF selects 3GPP access.

[0556] In some embodiments, the AMF can select the access type between 3GPP access and non-3GPP access based on operator policy.

[0557] In case c), the AMF can or should, for example, upon reception of the LPP message payload from the LMF:

[0558] a) set the Payload Container Type IE to "LTE Positioning Protocol (LPP) message container";

[0559] b) set the Payload Container IE to the LPP message payload received from the LMF;

[0560] c) set the Additional Information IE to the LCS-related identifier received from the LMF from which the LPP message was received.

[0561] In some embodiments, the LCS-related identifier is initially allocated by the AMF, in addition to the LPP message transfer associated with event reporting for periodic or triggered location, e.g., as described in 3GPP TS 23.273, where the LMF allocates the related identifier. The related identifiers allocated by the AMF and the LMF can be distinguished by implementation-specific convention, e.g., using different number of octets, to enable the AMF to distinguish when the additional information IE in the UL NAS transport message is received.

[0562] In case d), e.g., upon reception of a steering of roaming information from the UDM (see, e.g., 3GPP TS 23.122) to forward to the UE, the AMF can or should:

[0563] a) set the payload container type IE to “SOR transparent container”; and

[0564] b) set the payload container IE to the steering of roaming information received from the UDM (see, e.g., 3GPP TS 23.122).

[0565] In case e), e.g., upon sending a single uplink 5GSM message that was not forwarded due to routing failure, the AMF can or should:

[0566] a) include the PDU session ID in the PDU session ID IE;

[0567] b) set the payload container type IE to “N1 SM information”;

[0568] c) set the payload container IE to the 5GSM message that was not forwarded; and

[0569] d) set the 5GMM cause IE to 5GMM cause #90 “payload not forwarded” or 5GMM cause #91 “DNN not supported or not subscribed in slice”. The AMF sets the 5GMM cause IE to 5GMM cause #91 “DNN not supported or not subscribed in slice” if the 5GSM message could not be forwarded due to SMF selection failure for the following reasons:

[0570] 1) the DNN is not supported in the slice identified by the S-NSSAI used by the AMF; or

[0571] 2) neither the DNN provided by the UE nor the wildcard DNN exists in the list of subscribed DNNs for the UE for the S-NSSAI used by the AMF.

[0572] Otherwise, the AMF sets the 5GMM cause IE to 5GMM cause #90 “payload not forwarded”.

[0573] In case f), e.g., when sending a single uplink 5GSM message that is not forwarded due to congestion control, the AMF can or should:

[0574] a) include the PDU Session ID in the PDU Session ID IE;

[0575] b) set the Payload Container Type IE to "N1 SM Information";

[0576] c) set the Payload Container IE to the 5GSM message that is not forwarded;

[0577] d) set the 5GMM Cause IE to 5GMM Cause #22 "Congestion", 5GMM Cause #67 "Resource insufficient for specific slice and DNN" or 5GMM Cause #69 "Resource insufficient for specific slice"; and

[0578] e) include the Back-off Timer Value IE.

[0579] In case g), e.g., when receiving a UE Policy Container from the PCF to be forwarded to the UE, the AMF can or should:

[0580] a) set the Payload Container Type IE to "UE Policy Container"; and

[0581] b) set the Payload Container IE to the UE Policy Container received from the PCF.

[0582] In case h), e.g., when sending a single uplink 5GSM message that is not forwarded because the maximum number of PDU Sessions for the PLMN has been reached, the AMF can or should:

[0583] a) include the PDU Session ID in the PDU Session ID IE;

[0584] b) set the Payload Container Type IE to "N1 SM Information";

[0585] c) set the Payload Container IE to the 5GSM message that is not forwarded; and

[0586] d) set the 5GMM Cause IE to 5GMM Cause #65 "Maximum number of PDU Sessions reached".

[0587] In case i), e.g., when sending a single uplink 5GSM message that is not forwarded due to service area restrictions, the AMF can or should:

[0588] a) include the PDU Session ID in the PDU Session ID IE;

[0589] b) set the Payload Container Type IE to "N1 SM Information";

[0590] c) set the Payload Container IE to the 5GSM message that is not forwarded; and

[0591] d) set the 5GMM Cause IE to 5GMM Cause #28 "Restricted Service Area".

[0592] In case ia), e.g., when sending a single uplink 5GSM message that is not forwarded due to CAG, the AMF can or should:

[0593] a) include the PDU Session ID in the PDU Session ID IE;

[0594] b) set the Payload Container Type IE to "N1 SM Information";

[0595] c) set the Payload Container IE to the 5GSM message that is not forwarded; and

[0596] d) set the 5GMM Cause IE to 5GMM Cause #76 "Not authorized for this CAG or authorized only for CAG cells".

[0597] In case j), e.g., when receiving UE parameter update data (see, e.g., 3GPP TS 23.502) from the UDM to forward to the UE, the AMF can or should:

[0598] a) set the Payload Container Type IE to "UE Parameter Update Transparent Container"; and

[0599] b) set the content of the Payload Container IE to the UE parameter update data (see, e.g., 3GPP TS 23.502) received from the UDM.

[0600] For case k), e.g., when receiving a location service message payload from a location service application, the AMF can or should:

[0601] a) set the Payload Container Type IE to "Location Service Message Container"; and

[0602] b) set the Payload Container IE to the location service message payload.

[0603] For case k), e.g., when receiving a location service message payload from an LMF, the AMF can or should:

[0604] a) set the Payload Container Type IE to "Location Service Message Container";

[0605] b) set the Payload Container Type IE to "CIoT User Data Container"; and

[0606] c) set the Additional Information IE to routing information associated with the LMF from which the Location Service Message Payload is received.

[0607] NOTE 3: Case k) can support the transfer of the Location Service Message Container between the UE and the AMF and between the UE and the LMF. For the transfer between the UE and the LMF, the Additional Information IE is included and provides routing information for the LMF. For the transfer between the UE and the AMF, the Additional Information IE is not included.

[0608] In case l), e.g., upon reception of a User Data Container Payload from the SMF, the AMF can or should:

[0609] a) include the PDU Session ID in the PDU Session ID IE;

[0610] b) set the Payload Container Type IE to "CIoT User Data Container"; and

[0611] c) set the Payload Container IE to the User Data Container.

[0612] For case li), e.g., upon sending a single uplink CIoT User Data Container that was not forwarded due to service gap control, the AMF can or should:

[0613] a) include the PDU Session ID in the PDU Session ID IE;

[0614] b) set the Payload Container Type IE to "CIoT User Data Container";

[0615] c) set the Payload Container IE to the CIoT User Data Container that was not forwarded; and

[0616] d) set the 5GMM Cause IE to 5GMM Cause #90 "Payload not forwarded".

[0617] In case m), the AMF can or should:

[0618] a) set the Payload Container Type IE to "Multiple Payloads";

[0619] b) set each Payload Container entry of the Payload Container IE, e.g., as follows:

[0620] i) set the Payload Container Type field of the Payload Container entry to the Payload Container Type value set in the Payload Container Type IE as specified for cases a) to k) above;

[0621] ii) the payload container content field of the payload container entry is set to the payload content set in the payload container type IE as specified for cases a) to k) above;

[0622] iii) the optional IE fields (if any) are set to the optional associated information as specified for cases a) to k) above.

[0623] Network initiated NAS message transfer

[0624] Upon reception of the DL NAS TRANSPORT message, the UE can or shall stop timer T3346 (if running).

[0625] Upon reception of the DL NAS TRANSPORT message, if the payload container type IE is set to:

[0626] a) "N1 SM information" and the 5GMM cause IE is not included in the DL NAS TRANSPORT message, the 5GSM message in the payload container IE and the PDU session ID are processed in a 5GSM procedure as specified in clause 6;

[0627] b) "SMS", the UE can or shall forward the content of the payload container IE to the SMS stack entity;

[0628] c) "LTE Positioning Protocol (LPP) message container", the UE can or shall forward the payload container type, the content of the payload container IE and the routing information included in the additional information IE to the upper layer location service application;

[0629] d) "SOR transparent container" and if the payload container IE:

[0630] 1) passes integrity check (see e.g. 3GPP TS 33.501) successfully, indicates a list of preferred PLMN / access technology combinations is provided, and the list type indicates:

[0631] i) "PLMN ID and access technology list", the ME can or shall replace the highest priority entry in the "Operator controlled PLMN selector with access technology" list stored in the ME and can or shall continue the behaviour as specified in e.g. 3GPP TS 23.122; or

[0632] ii) "Secure Data Package", then the ME can or shall behave as if an SMS was received with the protocol identifier set to SIM Data Download, the data coding scheme set to class 2 message, and the SMS payload as the Secure Data Package content of the SOR transparent container IE. The SMS payload is forwarded to the UICC as specified in, for example, 3GPP TS 23.040, and the ME can or shall continue the behavior as specified in, for example, 3GPP TS 23.122; or

[0633] 2) not successfully passed integrity check (see, for example, 3GPP TS 33.501), then the UE can or shall continue the behavior as specified in, for example, 3GPP TS 23.122.

[0634] e) void;

[0635] f) void;

[0636] g) "N1 SM Information", and:

[0637] 1) 5GMM cause IE is set to 5GMM cause #22 "Congestion", then the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to DNN-based congestion control along with the 5GSM message from the PAYLOAD CONTAINER IE of the DL NAS TRANSPORT message and the time value from the BACK-OFF TIMER VALUE IE;

[0638] 2) 5GMM cause IE is set to 5GMM cause #28 "Restricted Service Area", then the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to service area restriction along with the 5GSM message from the PAYLOAD CONTAINER IE of the DL NAS TRANSPORT message, enters state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and if the DL NAS TRANSPORT message was received over a 3GPP access, performs a registration procedure for mobility and periodic registration updates;

[0639] 3) 5GMM cause IE is set to 5GMM cause #65 "Maximum number of PDU Sessions reached", then the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to the maximum number of PDU Sessions of the PLMN being reached along with the 5GSM message from the PAYLOAD CONTAINER IE of the DL NAS TRANSPORT message;

[0640] 4) the 5GMM cause IE is set to 5GMM cause #67 "Resources not sufficient for specific slice and DNN", the UE passes to the 5GMM sublayer an indication that the 5GMM message was not forwarded due to congestion control based on S-NSSAI and DNN together with the 5GMM message from the DL NAS TRANSPORT message's payload container IE and the time value from the back-off timer value IE;

[0641] 5) the 5GMM cause IE is set to 5GMM cause #69 "Resources not sufficient for specific slice", the UE passes to the 5GMM sublayer an indication that the 5GMM message was not forwarded due to congestion control based on S-NSSAI only together with the 5GMM message from the DL NAS TRANSPORT message's payload container IE and the time value from the back-off timer value IE;

[0642] 5a) the 5GMM cause IE is set to 5GMM cause #76 "Not authorized for this CAG or authorized for CAG cells only", the UE passes to the 5GMM sublayer an indication that the 5GMM message was not forwarded due to CAG together with the 5GMM message from the DL NAS TRANSPORT message's payload container IE;

[0643] 6) the 5GMM cause IE is set to 5GMM cause #90 "Payload not forwarded", the UE passes to the 5GMM sublayer an indication that the 5GMM message was not forwarded due to routing failure together with the 5GMM message from the DL NAS TRANSPORT message's payload container IE; or

[0644] 7) the 5GMM cause IE is set to 5GMM cause #91 "DNN not supported or subscribed in slice", the UE passes to the 5GMM sublayer an indication that the 5GMM message was not forwarded due to DNN not supported or subscribed in slice together with the 5GMM message from the DL NAS TRANSPORT message's payload container IE;

[0645] h) "UE policy container", the UE policy container in the payload container IE is processed in the UE policy delivery procedure;

[0646] i) "UE parameter update transparent container", and if the payload container IE:

[0647] 1) passes integrity check (e.g., see 3GPP TS 33.501) successfully:

[0648] i) if the UE parameter update list includes a UE parameter update data set with a UE parameter update data set type indication of "routing indicator update data",

[0649] A) then the ME can or shall behave as if an SMS was received with the protocol identifier set to SIM data download, the data coding scheme set to class 2 message, and the SMS payload as the security data package content of the UE parameter update transparent container IE. The SMS payload is forwarded to the UICC as specified in, for example, 3GPP TS 23.040; and

[0650] B) if the ACK bit of the UE parameter update header in the UE parameter update transparent container is set to "acknowledgement requested" and if the ME receives a status byte from the UICC indicating that the UICC has successfully received the security data package, the ME can or shall send an acknowledgement in the payload container IE of the UL NAS TRANSPORT message with the payload type IE set to "UE parameter update transparent container"; and

[0651] C) if the ME receives a REFRESH command from the UICC as specified in 3GPP TS 31.111 and if the REG bit of the UE parameter update header in the UE parameter update transparent container IE is set to "re-registration requested", and:

[0652] C1) the UE is registered over 3GPP access, then the UE can or shall wait until it enters 5GMM-IDLE mode over 3GPP access or enters 5GMM-CONNECTED mode with RRC inactive indication, and then performs the de-registration procedure, deletes its 5G-GUTI, and initiates the registration procedure for initial registration, for example, as specified in 3GPP TS 24.501 or 3GPP TS 29.502;

[0653] C2) the UE is registered over non-3GPP access and does not have an ongoing emergency service over non-3GPP access, then the UE can or shall locally release the N1 NAS signaling connection and enters 5GMM-IDLE mode over non-3GPP access, performs the de-registration procedure, deletes its 5G-GUTI if the UE is registered to a different PLMN over 3GPP access or the UE is not registered over 3GPP access, and then initiates the registration procedure for initial registration, for example, as specified in 3GPP TS 24.501 or 3GPP TS 29.502; and

[0654] C3) the UE is registered over non-3GPP access and has an ongoing emergency service over non-3GPP access, then the UE can or shall wait until the emergency service is completed, then locally release the N1 NAS signaling connection and enter 5GMM-IDLE mode over non-3GPP access, perform a de-registration procedure, delete its 5G-GUTI if the UE is registered to a different PLMN over 3GPP access or if the UE is not registered over 3GPP access, and then initiate a registration procedure for initial registration, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502.

[0655] ii) if the UE parameter update list includes a UE parameter update data set with a UE parameter update data set type indication of "default configured NSSAI update data",

[0656] A) if the ACK bit of the UE parameter update header in the UE parameter update transparent container is set to "acknowledgement requested" and if the UE parameter update list does not include a UE parameter update data set with a UE parameter update data set type indication of "routing indicator update data", the ME can or shall send an acknowledgement in the payload container IE of the UL NAS TRANSPORT message with the payload type IE set to "UE parameter update transparent container", e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502;

[0657] B) the ME can or shall replace the stored default configured NSSAI with the default configured NSSAI included in the default configured NSSAI update data; and

[0658] C) if the UE parameter update list does not include a UE parameter update data set with a UE parameter update data set type indication of "routing indicator update data", the UE uses the old default configured NSSAI for creating the requested NSSAI in the REGISTRATION REQUEST message, the UE does not have a configured NSSAI for the current PLMN, and the UE has an allowed NSSAI for the current PLMN that contains one or more S-NSSAIs not included in the new default configured NSSAI, then the UE can or shall wait until it enters 5GMM-IDLE mode, and then the UE can or shall initiate a registration procedure for mobility and periodic registration update, e.g., as specified in 3GPP TS 24.501 or 3GPP TS 29.502; and

[0659] 2) without success through integrity check (see e.g. 3GPP TS 33.501), the UE can or shall discard the content of the Payload Container IE;

[0660] j) for the "Location Services Message Container", and the 5GMM cause IE is not included in the DL NAS TRANSPORT message, the UE can or shall forward the Payload Container Type, the content of the Payload Container IE and the Routing Information in the Additional Information IE, if included, to the upper layer Location Services application;

[0661] k) for the "CIoT User Data Container", the UE can or shall forward the content of the Payload Container IE and the PDU Session ID to the 5GSM sublayer; and

[0662] l) for the "CIoT User Data Container", and:

[0663] 1) the 5GMM cause IE is set to 5GMM cause #22 "Congestion", the UE passes to the 5GSM sublayer an indication that the CIoT User Data was not forwarded due to congestion control based on DNN together with the CIoT User Data from the Payload Container IE of the DL NAS TRANSPORT message and the time value from the Back-off Timer Value IE.

[0664] 2) the 5GMM cause IE is set to 5GMM cause #90 "Payload not forwarded", the UE passes to the 5GSM sublayer an indication that the User Data Container was not forwarded due to routing failure together with the User Data Container from the Payload Container IE of the DL NAS TRANSPORT message and the PDU Session ID from the PDU Session ID IE.

[0665] m) for the "Multiple Payloads", the UE can or shall first decode the content of the Payload Container IE to obtain multiple Payload Container entries, and for each Payload Container entry, the UE can or shall:

[0666] 1) decode the Payload Container Type field;

[0667] 2) decode the optional IE fields and the Payload Container Content field in the Payload Container entry; and

[0668] 3) according to the Payload Container Type field, handle the content of each Payload Container entry the same as the content of the Payload Container IE and associated optional IEs as specified in items a) to 1) above.

[0669] According to some embodiments, the following exceptional cases can be identified:

[0670] a) expiry of the timer T3580

[0671] The UE can or shall, at the first expiry of timer T3580:

[0672] - if the PDU SESSION ESTABLISHMENT REQUEST message was sent with the Request Type set to "Initial Emergency Request" or "Existing Emergency PDU Session", the UE can:

[0673] a) inform the upper layer procedure of failure; or

[0674] b) locally deregister, if not already, and attempt initial registration of emergency services.

[0675] - else, retransmit the PDU SESSION ESTABLISHMENT REQUEST message and the PDU session information transmitted with the initial transmission of the PDU SESSION ESTABLISHMENT REQUEST message and can or shall reset and start timer T3580, if still needed. This retransmission can be repeated at most four times, i.e. at the fifth expiry of timer T3580, the UE can or shall abort the procedure, release the allocated PTI and enter the state PROCEDURE TRANSACTION INACTIVE.

[0676] b) upon reception of a PDU SESSION ESTABLISHMENT REQUEST message with an indication that the 5GSM message was not forwarded due to routing failure along with the PDU Session ID IE set to the same value as the PDU Session ID sent by the UE, the UE can or shall stop timer T3580 and can or shall abort the procedure. If the UE sent the PDU SESSION ESTABLISHMENT REQUEST message for a handover between 3GPP access and non-3GPP access for an existing non-emergency PDU session, the UE can or shall consider the PDU session to be associated with the source access type.

[0677] b1) upon reception of a PDU SESSION ESTABLISHMENT REQUEST message with an indication that the 5GSM message was not forwarded due to service area restrictions along with the PDU Session ID IE set to the same value as the PDU Session ID sent by the UE, the UE can or shall abort the procedure.

[0678] b2) Upon receiving the PDU SESSION ESTABLISHMENT REQUEST message with the indication that the 5GSM message was not forwarded due to CAG along with the PDU Session ID IE set to the same value as the PDU Session ID sent by the UE, the UE can or should stop timer T3580 and can or should abort the procedure.

[0679] c) Conflict of UE requested PDU session establishment procedure and network requested PDU session release procedure.

[0680] If the UE receives the PDU SESSION RELEASE COMMAND message after sending the PDU SESSION ESTABLISHMENT REQUEST message to the network, and the PDU Session ID in the PDU SESSION RELEASE COMMAND message is the same as the PDU Session ID in the PDU SESSION ESTABLISHMENT REQUEST message, the UE can or should ignore the PDU SESSION RELEASE COMMAND message and continue the UE requested PDU session establishment procedure.

[0681] In some embodiments, the CNA 200 and / or the apparatus 300 can be configured to perform some or all of any of the methods described herein. For example, with reference again to Figures 1 to 3 the CNA 200 and / or the apparatus 300 can be implemented by a computer- implemented system such as Figure 4 the CNA 200 and / or the apparatus 300 can be implemented by a computer- implemented system such as Figure 5The apparatus 300 of the device performs or partially performs operations to handle emergency services in a private network according to any of the methods described herein. In some embodiments, the CNA 200 and / or the apparatus 300 can include means, such as the processor 202, 304, the memory 204, 306, 308, the communication interface 206, the user interface 312, etc., for transmitting or receiving a UL NAS TRANSPORT message including a message requesting establishment of a non-emergency PDU session. In some embodiments, the CNA 200 and / or the apparatus 300 can include means, such as the processor 202, 304, the memory 204, 306, 308, the communication interface 206, the user interface 312, etc., for accepting the UL NAS TRANSPORT message or rejecting the UL NAS TRANSPORT message by, for example, transmitting a DL NAS TRANSPORT message including a PDU session ID, a request message, and a rejection cause number (e.g., 5GMM cause #76 “Not authorized for this CAG or authorized only for CAG cells”). In some embodiments, the CNA 200 and / or the apparatus 300 can include means, such as the processor 202, 304, the memory 204, 306, 308, the communication interface 206, the user interface 312, etc., for starting and / or stopping a timer (e.g., timer T3580) and / or aborting a PDU session establishment procedure. In some embodiments, the CNA 200 and / or the apparatus 300 can include means, such as the processor 202, 304, the memory 204, 306, 308, the communication interface 206, the user interface 312, etc., for updating CAG information. In some embodiments, the CNA 200 and / or the apparatus 300 can include means, such as the processor 202, 304, the memory 204, 306, 308, the communication interface 206, the user interface 312, etc., for determining whether the user equipment has requested an emergency PDU session and whether the UE fails CAG access control with the updated CAG information in instances where the CAG information has been updated. In some embodiments, the CNA 200 and / or the apparatus 300 can include means, such as the processor 202, 304, the memory 204, 306, 308, the communication interface 206, the user interface 312, etc., for performing a local release of all PDU sessions except for an emergency PDU session, for example, in instances where the CAG information has been updated. In some embodiments, the CNA 200 and / or the apparatus 300 can include means, such as the processor 202, 304, the memory 204, 306, 308, the communication interface 206, the user interface 312, etc., for deregistering the UE from the network upon receiving the CAG information or the updated CAG information.In some embodiments, the CNA 200 and / or the apparatus 300 can include means, such as the processor 202, 304, the memory 204, 306, 308, the communication interface 206, the user interface 312, etc., for checking to see if the UE has established or requested an emergency PDU session, and then only deregistering the UE from the network upon receiving CAG information or updated CAG information, and determining that the UE has not passed CAG access control based on the CAG information or updated CAG information if the UE has not established or registered an emergency PDU session with the network. In some embodiments, the CAG access control procedure can include a procedure as follows: upon receiving a REGISTRATION REQUEST message, etc., a DEREGISTRATION REQUEST message, etc., or a SERVICE REQUEST message, etc., with a “CAG information list” from the UE or another network entity, checking by the AMF in the selected PLMN for which there are entries in the “CAG information list” if the message (e.g., 5GMM message) was sent via a CAG cell, and subsequently if the message was sent via a CAG cell, checking if the selected CAG-ID is included in the UE’s “allowed CAG list” for the current PLMN, or if the message was sent via a non-CAG cell, checking if the entry of the UE’s “CAG information list” for the current PLMN includes an “indication that the UE is only allowed to access the 5GS via CAG cells”. In some embodiments, the CNA 200 and / or the apparatus 300 can include means, such as the processor 202, 304, the memory 204, 306, 308, the communication interface 206, the user interface 312, etc., for terminating the CAG access control procedure by passing the UE through when the selected CAG-ID is included in the “allowed CAG list” for the current PLMN in instances where the 5GMM message was sent via a CAG cell, or if the 5GMM message was sent via a non-CAG cell, terminating the CAG access control procedure and passing the UE through if the “indication that the UE is only allowed to access the 5GS via CAG cells” is not included in the entry of the UE’s “CAG information list” for the current PLMN, otherwise, terminating the CAG access control procedure and failing the UE.

[0682] Reference is now made to Figure 6A, illustrating an UL NAS TRANSPORT message between the UE 102 and the AMF 108. In some embodiments, the AMF 108 can receive the UL NAS TRANSPORT message directly from the UE 102, and in other embodiments, the AMF 108 can receive the UL NAS TRANSPORT message indirectly, e.g., through the RAN 104, etc. In some embodiments, the UL NAS TRANSPORT message can include or contain a PDU SESSION ESTABLISHMENT REQUEST message from the UE 102 in a CAG restricted cell requesting establishment of a non-emergency PDU session. In such instances, from the perspective of the AMF 108, if the payload container type IE in the UL NAS TRANSPORT message is set to “N1 SM information” and if the request type IE is set to neither “initial emergency request” nor “existing emergency PDU session,” and further if the UE 102 sent the UL NAS TRANSPORT message via a CAG cell and the selected CAG-ID is not included in the UE’s “allowed CAG list” for the current PLMN, or if the UE 102 sent the UL NAS TRANSPORT message via a non-CAG cell and the UE’s “CAG information list” for the current PLMN includes an entry with an indication that “the UE is only allowed to access the 5GS via CAG cells,” then the AMF 108 can or should send a DL NAS TRANSPORT message to the UE 102 indicating that the requested 5GSM message (contained in the payload container IE of the UL NAS TRANSPORT message) is rejected due to CAG requirements, as shown in Figure 6B .

[0683] As shown in Figure 6B , once it is determined that the above conditions are not yet met, e.g., the UE 102 did not pass the CAG access control procedure or test, the AMF 108 can send a DL NAS TRANSPORT message to the UE 102 directly or through, e.g., the RAN 104, indicating that the request is rejected due to CAG requirements. To do so, the AMF 108 can or should include the PDU session ID in the PDU session ID IE of the DL NAS TRANSPORT message, set the payload container type IE of the DL NAS TRANSPORT message to “N1 SM information,” set the payload container IE of the DL NAS TRANSPORT message to the unforwarded 5GSM message, and set the 5GMM cause IE of the DL NAS TRANSPORT message to 5GMM cause #76 “not authorized for this CAG or authorized for CAG cells only.”

[0684] Once the UE 102 receives the DL NAS TRANSPORT message from the AMF 108, e.g., through the 5GMM sublayer of the UE 102, the 5GMM sublayer of the UE 102 indicates to the 5GSM sublayer of the UE 102 that there is an issue. When the 5GMM sublayer of the UE 102 receives the DL NAS TRANSPORT message, if the Payload Container Type IE is set to “N1 SM Information” and the 5GMM Cause IE is set to 5GMM Cause #76 “Not authorized for this CAG or authorized for CAG cells only,” the UE 102, or more accurately the 5GMM sublayer of the UE 102, can pass an indication to the 5GSM sublayer of the UE 102 that the 5GSM message was not forwarded due to CAG requirements along with the 5GSM message from the Payload Container IE of the DL NAS TRANSPORT.

[0685] Reference is now made to Figure 7 In instances where the 5GSM sublayer of the UE 102 receives an indication from the 5GMM sublayer of the UE 102 that the 5GSM message was not forwarded due to CAG requirements, and upon receiving the 5GSM message from the Payload Container IE of the DL NAS TRANSPORT message, the 5GSM sublayer of the UE 102 can take action. For example, in some embodiments, upon receiving an indication that the 5GSM message was not forwarded due to CAG requirements along with a PDU SESSION ESTABLISHMENT REQUEST message with the PDU Session ID IE set to the same value as the PDU Session ID sent by the UE 102, the 5GSM sublayer of the UE 102 can or should stop timer T3580 and can or should abort the procedure.

[0686] In instances where the AMF 108 needs to update the CAG information, the AMF 108 can or should include the CAG Information List IE in the CONFIGURATION UPDATE COMMAND message sent to or transmitted to the UE 102. If the UE 102 has an ongoing emergency PDU session and the UE 102 does not pass the CAG access control procedure for the updated CAG information as described above, the AMF 108 can or should perform the local release of all PDU sessions except the emergency PDU session. In this way, even if the UE 102 does not pass the CAG access control procedure or test, the AMF 108 will not release the ongoing emergency PDU session of the UE 102 due to the UE 102 having an established / ongoing emergency PDU session with the CN 101 via the AMF 108. In some embodiments, if the “CAG Information List” received by the UE 102 includes an entry containing the identity of the current PLMN, the UE 102 can or should operate as follows.

[0687] In instances where the UE 102 receives the CONFIGURATION UPDATE COMMAND message from the AMF 108 via a CAG cell, the “Allowed CAG List” for the current PLMN in the received “CAG Information List” does not include the CAG-ID of the current CAG cell (e.g., the cell in which the CONFIGURATION UPDATE COMMAND message is received), and the entry for the current PLMN in the received “CAG Information List” does not include an instance of the “indication that the UE is only allowed to access the 5GS via CAG cells,” the UE 102 can or should enter the state 5GMM-REGISTERED.LIMITED-SERVICE and can or should search for a suitable cell with the updated “CAG Information List,” e.g., according to 3GPP TS 38.304.

[0688] In the instance where the UE 102 receives a CONFIGURATION UPDATE COMMAND message from the AMF 108 via a CAG cell, the “allowed CAG list” for the current PLMN in the received “CAG information list” does not include the CAG-ID of the current CAG cell (e.g., the cell where the CONFIGURATION UPDATE COMMAND message is received), and the entry for the current PLMN in the received “CAG information list” includes an instance of the “indication that the UE is only allowed to access the 5GS via CAG cells”, if the “allowed CAG list” for the current PLMN in the received “CAG information list” includes one or more CAG-IDs, the UE 102 can or should enter the state 5GMM-REGISTERED.LIMITED-SERVICE, and can or should search for a suitable cell with the updated “CAG information list”, e.g., according to 3GPP TS 38.304.

[0689] In the instance where the UE 102 receives a CONFIGURATION UPDATE COMMAND message from the AMF 108 via a CAG cell, the “allowed CAG list” for the current PLMN in the received “CAG information list” does not include the CAG-ID of the current CAG cell (e.g., the cell where the CONFIGURATION UPDATE COMMAND message is received), and the entry for the current PLMN in the received “CAG information list” includes an instance of the “indication that the UE is only allowed to access the 5GS via CAG cells”, if the “allowed CAG list” for the current PLMN in the received “CAG information list” does not include any CAG-IDs, and the UE 102 does not have an emergency PDU session, the UE can or should enter the state 5GMM-DEREGISTERED.PLMN-SEARCH, and can or should apply the PLMN selection procedure defined, e.g., in 3GPP TS 23.122, with the updated “CAG information list”.

[0690] In the instance where the UE 102 receives a CONFIGURATION UPDATE COMMAND message from the AMF 108 via a CAG cell, the "allowed CAG list" for the current PLMN in the received "CAG information list" does not include the CAG-ID of the current CAG cell (e.g., the cell that received the CONFIGURATION UPDATE COMMAND message), and the entry for the current PLMN in the received "CAG information list" includes an instance of the "indication that the UE is only allowed to access the 5GS via CAG cells", if the "allowed CAG list" for the current PLMN in the received "CAG information list" does not include any CAG-ID, and the UE has an emergency PDU session, the UE 102 can or should perform local release of all PDU sessions except the emergency PDU session.

[0691] In the instance where the UE receives a CONFIGURATION UPDATE COMMAND message via a non-CAG cell, and the entry for the current PLMN in the received "CAG information list" includes an instance of the "indication that the UE is only allowed to access the 5GS via CAG cells", if the "allowed CAG list" for the current PLMN in the received "CAG information list" includes one or more CAG-ID, the UE 102 can or should enter the state 5GMM-REGISTERED.LIMITED-SERVICE, and can or should search for a suitable cell with the updated "CAG information list", e.g., according to 3GPP TS 38.304.

[0692] In the instance where the UE 102 receives a CONFIGURATION UPDATE COMMAND message via a non-CAG cell, and the entry for the current PLMN in the received "CAG information list" includes an instance of the "indication that the UE is only allowed to access the 5GS via CAG cells", if the "allowed CAG list" for the current PLMN in the received "CAG information list" does not include any CAG-ID, and the UE 102 does not have an emergency PDU session, the UE can or should enter the state 5GMM-DEREGISTERED.PLMN-SEARCH, and can or should apply the PLMN selection procedure defined, e.g., in 3GPP TS 23.122, with the updated "CAG information list".

[0693] In an instance where the UE 102 receives the CONFIGURATION UPDATE COMMAND message via a non-CAG cell and the entry for the current PLMN in the received "CAG information list" includes an indication that "the UE is only allowed to access the 5GS via CAG cells", if the "allowed CAG list" for the current PLMN in the received "CAG information list" does not include any CAG-ID and the UE has an emergency PDU session, the UE 102 can or should perform local release of all PDU sessions except the emergency PDU session.

[0694] Reference is now made to Figure 8 A method 10 for handling emergency services in a private network can be provided. In some embodiments, the method can be performed by an apparatus, such as the CAN 200 and / or the apparatus 300, which can include components such as a processor, a memory storing computer program code, and / or a communication interface. The method can cause, at 11, receiving, at least at a user equipment (UE), a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list. In some embodiments, the method 10 can further include, at 12, if an entry for the PLMN in the received CAG information list includes an indication that "the UE is only allowed to access the PLMN via CAG cells" and the allowed CAG list for the PLMN in the received CAG information list does not include any CAG-ID, performing, by the UE, local release of all protocol data unit (PDU) sessions except an emergency PDU session.

[0695] Reference is now made to Figure 9A method 20 for emergency services handled in a private network can be provided. In some embodiments, the method can be performed by an apparatus (e.g., CAN 200 and / or apparatus 300), which can include components such as a processor, a memory storing computer program code, and / or a communication interface, the method can cause, at 21, receiving, at least at a mobility management sublayer of a user equipment, a downlink non-access stratum (NAS) transport message from a network entity of a public land mobile network (PLMN), which includes a message requesting session management and a cause value indicating that the UE is not authorized to issue the request due to CAG constraints. In some embodiments, the method 20 can further include, at 22, sending, from the mobility management sublayer of the user equipment, the message requesting session management to the session management sublayer of the user equipment along with an indication that the message requesting session management is not forwarded due to CAG. In some embodiments, the method 20 can further include, at 23, upon receiving, at the session management sublayer of the user equipment, the indication that the message requesting session management is not forwarded due to CAG along with the message requesting session management, stopping a timer associated with the session management request and aborting the procedure for session management.

[0696] Reference is now made to Figure 10A method 30 for handling emergency services in a private network can be provided. In some embodiments, the method 30 can be performed by an apparatus (e.g., CNA 200 and / or apparatus 300), which can include components such as a processor, a memory storing computer program code, and / or a communication interface, the method can cause, at 31, receiving, at least at a user equipment (UE), a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list. In some embodiments, the method 30 can further include: in an instance where the configuration update command message is received via a specific CAG cell, an entry for the current PLMN includes an indication that the user equipment is only allowed to access the PLMN via CAG cells and does not include CAG identification information, and the user equipment has not requested or established an emergency protocol data unit (PDU) session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list, at 32. In some embodiments, the method 30 can further include: in an instance where the configuration update command message is received via a specific CAG cell, an entry for the current PLMN includes an indication that the user equipment is only allowed to access the current PLMN via CAG cells and does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session, at 33. In some embodiments, the method 30 can further include: in an instance where the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency PDU session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list, at 34. In some embodiments, the method 30 can further include: in an instance where the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session, at 35.

[0697] Reference will now be made to Figure 11A method 40 for handling emergency services in a private network can be provided. In some embodiments, the method 40 can be performed by an apparatus (e.g., the CNA 200 and / or the apparatus 300), which can include components such as a processor, a memory storing computer program code, and / or a communication interface, the method can cause, at 41, receiving, from at least a user equipment, a session request message for a public land mobile network. In some embodiments, the method 40 can further include, at 42, in instances where the session request message includes an initial emergency session request, sending, to the user equipment, a session accept message. In some embodiments, the method 40 can further include, at 43, in instances where the session request message does not include an initial emergency session request, the session request is initiated by a closed access group cell, and a selected closed access group cell identity in the session request message is not included in an allowed closed access group list for the public land mobile network, sending, to the user equipment, a session reject message. In some embodiments, the method 40 can further include, at 44, in instances where the session request message does not include an initial emergency session request, the session request is initiated by a non-closed access group cell, and an entry of a closed access group information list for the public land mobile network includes an indication that the user equipment is only allowed to access the public land mobile network through a closed access group cell, sending, to the user equipment, a session reject message.

[0698] Reference is now made to Figure 12 A method 50 for handling emergency services in a private network can be provided. In some embodiments, the method 50 can be performed by an apparatus (e.g., the CNA 200 and / or the apparatus 300), which can include components such as a processor, a memory storing computer program code, and / or a communication interface, the method can cause, at 51, receiving, at a mobility management sublayer of a user equipment, from a network entity of a public land mobile network (PLMN), a session reject message including an indication that a session request received from the user equipment was not forwarded due to an updated closed access group (CAG) requirement. In some embodiments, the method 50 can further include, at 52, sending, from the mobility management sublayer of the user equipment, to a session management sublayer of the user equipment, an indication that the session request was rejected by the PLMN due to the updated CAG requirement. In some embodiments, the method 50 can further include, at 53, upon receiving, at the session management sublayer of the user equipment, the indication that the session request was rejected by the PLMN due to the updated CAG requirement, stopping a timer associated with the session request and aborting the session request.

[0699] As mentioned above, Figures 8 to 12is a flow diagram of a method according to an embodiment of the application that can be performed by a device comprising a computer program product comprising computer program code. It should be understood that each block of the flow diagram and combinations of blocks in the flow diagram can be implemented by various means, such as hardware, firmware, processor, circuitry and / or other device associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above can be embodied by computer program instructions. In this aspect, the computer program instructions which embody the procedures described above can be stored by a memory device (e.g., 204) of a device (e.g., 200) embodying an embodiment of the present application and executed by a processing circuit (e.g., 202) of the device. As will be appreciated, any such computer program instructions can be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flow diagrams' blocks. These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture that, when executed, implements the functions specified in the flow diagrams' blocks. The computer program instructions can also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that are executed on the computer or other programmable apparatus provide operations for implementing the functions specified in the flow diagrams' blocks.

[0700] Accordingly, a computer program product is defined in instances in which computer program instructions, such as portions of computer-readable program code, are stored by at least one non-transitory computer-readable storage medium, where the computer program instructions, such as portions of computer-readable program code, are configured such that when executed implement the functions described above, such as in conjunction with at least Figures 8 to 12 In other embodiments, the computer program instructions, such as portions of computer-readable program code, need not be stored or otherwise tangibly embodied by a non-transitory computer-readable storage medium, but instead, can be tangibly embodied by a transitory medium, where the computer program instructions, such as portions of computer-readable program code, are still configured such that when executed implement the functions described above.

[0701] Accordingly, the blocks of the flow diagrams support combinations for performing the specified functions, and combinations of operations for performing the specified functions. It also should be understood that one or more blocks of the flow diagrams, and combinations of blocks in the flow diagrams, can be implemented by special purpose hardware-based computer systems which perform some or all of the procedures specified in the flow diagrams or combinations of special purpose hardware and computer instructions.

[0702] In some embodiments, certain operations described above may be modified or further amplified. Furthermore, in some embodiments, additional optional operations may be included. Modifications, additions, or amplifications of the above operations can be performed in any order and in any combination.

[0703] This document describes methods, apparatus, and computer program products for handling emergency services in a private network, based on exemplary embodiments. In some embodiments, a method may include: receiving a configuration update command message at a user equipment (UE) from a network entity of a current Public Land Mobile Network (PLMN), the configuration update command message including an updated Closed Access Group (CAG) information list; and if the entries for the PLMN in the received CAG information list include an indication that the UE is only permitted to access the PLMN via a CAG cell and the permitted CAG list for the PLMN in the received CAG information list does not include any CAG-ID, then the UE performs a local release of all PDU sessions except for Emergency Protocol Data Unit (PDU) sessions.

[0704] In some embodiments, an apparatus may include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured together with the at least one processor to cause the apparatus to at least: receive a configuration update command message at a user equipment (UE) from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated Closed Access Group (CAG) information list; and if the entries for the PLMN in the received CAG information list include an indication that the UE is only allowed to access the PLMN via a CAG cell and the allowed CAG list for the PLMN in the received CAG information list does not include any CAG-ID, then the UE performs a local release of all PDU sessions except for Emergency Protocol Data Unit (PDU) sessions.

[0705] In some embodiments, an apparatus may include: components such as a processor or processing circuitry and a memory storing computer program code for receiving a configuration update command message from a network entity of a current Public Land Mobile Network (PLMN), the configuration update command message including an updated Closed Access Group (CAG) information list; and components for performing local release of all PDU sessions except Emergency Protocol Data Unit (PDU) sessions if the entries for the PLMN in the received CAG information list include an indication that the UE is only allowed to access the PLMN via a CAG cell and the allowed CAG list for the PLMN in the received CAG information list does not include any CAG-ID.

[0706] In some embodiments, a computer program product can include a non-transitory computer-readable medium that includes computer instructions stored therein for performing at least the following: receiving, at a user equipment (UE), a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list; performing, by the UE, a local release of all protocol data unit (PDU) sessions except emergency PDU sessions if an indication in the received CAG information list for the PLMN that the UE is only allowed to access the PLMN via CAG cells and an allowed CAG list for the PLMN in the received CAG information list does not include any CAG-IDs.

[0707] In some embodiments, a method can include: receiving, at a mobility management sublayer of a user equipment, a downlink non-access stratum (NAS) transport message from a network entity of a public land mobile network (PLMN) including a message requesting session management and a cause value indicating that the UE is not authorized to make the request due to CAG constraints; sending, from the mobility management sublayer of the user equipment, the message requesting session management to a session management sublayer of the user equipment along with an indication that the message requesting session management is not forwarded due to CAG; and upon receiving, at the session management sublayer of the user equipment, the indication that the message requesting session management is not forwarded due to CAG along with the message requesting session management, stopping a timer associated with the session management request and aborting the procedure for session management.

[0708] In some embodiments, an apparatus can include: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the following: receiving, at a mobility management sublayer of a user equipment, a downlink non-access stratum (NAS) transport message from a network entity of a public land mobile network (PLMN) including a message requesting session management and a cause value indicating that the UE is not authorized to make the request due to CAG constraints; sending, from the mobility management sublayer of the user equipment, the message requesting session management to a session management sublayer of the user equipment along with an indication that the message requesting session management is not forwarded due to CAG; and upon receiving, at the session management sublayer of the user equipment, the indication that the message requesting session management is not forwarded due to CAG along with the message requesting session management, stopping a timer associated with the session management request and aborting the procedure for session management.

[0709] In some embodiments, an apparatus can comprise means, such as a processor or processing circuitry and a memory storing computer program code, for receiving, at a mobility management sublayer of a user equipment, a downlink non-access stratum (NAS) transport message from a network entity of a public land mobile network (PLMN), the downlink NAS transport message comprising a message requesting session management and a cause value indicating that the UE is not authorized to make the request due to CAG constraints; means for sending, from the mobility management sublayer of the user equipment, an indication that the message requesting session management is not forwarded due to CAG to a session management sublayer of the user equipment along with the message requesting session management; and means for, when the indication that the message requesting session management is not forwarded due to CAG is received at the session management sublayer of the user equipment along with the message requesting session management, stopping a timer associated with the session management request and aborting the procedure for session management.

[0710] In some embodiments, a computer program product can comprise a non-transitory computer readable medium comprising computer instructions stored thereon for performing at least the following: receiving, at a mobility management sublayer of a user equipment, a downlink non-access stratum (NAS) transport message from a network entity of a public land mobile network (PLMN), the downlink NAS transport message comprising a message requesting session management and a cause value indicating that the UE is not authorized to make the request due to CAG constraints; sending, from the mobility management sublayer of the user equipment, an indication that the message requesting session management is not forwarded due to CAG to a session management sublayer of the user equipment along with the message requesting session management; and when the indication that the message requesting session management is not forwarded due to CAG is received at the session management sublayer of the user equipment along with the message requesting session management, stopping a timer associated with the session management request and aborting the procedure for session management.

[0711] In some embodiments, a method can include receiving, at a user equipment, a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list; in an instance in which the configuration update command message is received via a CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency protocol data unit (PDU) session with the current PLMN, entering a deregistered-PLMN-search state and applying a PLMN selection procedure based on the updated CAG information list; in an instance in which the configuration update command message is received via a CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the current PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session; in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency PDU session with the current PLMN, entering a deregistered-PLMN-search state and applying a PLMN selection procedure based on the updated CAG information list; and in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session.

[0712] In some embodiments, an apparatus can be provided that includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receiving, at a user equipment, a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list; in an instance in which the configuration update command message is received via a specific CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency protocol data unit (PDU) session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list; in an instance in which the configuration update command message is received via a specific CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the current PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session; in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency PDU session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list; and in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session.

[0713] In some embodiments, an apparatus can be provided that comprises means, such as a processor or processing circuitry and a memory storing computer program code, for receiving, at a user equipment, a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message comprising an updated closed access group (CAG) information list; means for entering, in an instance in which the configuration update command message is received via a specific CAG cell, an entry for the current PLMN in the CAG information list comprises an indication that the user equipment is only allowed to access the PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not comprise CAG identification information, and the user equipment has not requested or established an emergency protocol data unit (PDU) session with the current PLMN, a deregistered-PLMN-search state and applying a PLMN selection procedure based on the updated CAG information list; means for performing, in an instance in which the configuration update command message is received via a specific CAG cell, an entry for the current PLMN in the CAG information list comprises an indication that the user equipment is only allowed to access the current PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not comprise CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, a local release of all PDU sessions except the emergency PDU session; means for entering, in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list comprises an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not comprise CAG identification information, and the user equipment has not requested or established an emergency PDU session with the current PLMN, a deregistered-PLMN-search state and applying a PLMN selection procedure based on the updated CAG information list; and means for performing, in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list comprises an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not comprise CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, a local release of all PDU sessions except the emergency PDU session.

[0714] In some embodiments, a computer program product can be provided that includes a non-transitory computer readable medium that includes computer instructions stored therein for performing at least the following: receiving, at a user equipment, a configuration update command message from a network entity of a current public land mobile network (PLMN), the configuration update command message including an updated closed access group (CAG) information list; in an instance in which the configuration update command message is received via a CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency protocol data unit (PDU) session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list; in an instance in which the configuration update command message is received via a CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the user equipment is only allowed to access the current PLMN via CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session; in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has not requested or established an emergency PDU session with the current PLMN, entering a deregistered PLMN search state and applying a PLMN selection procedure based on the updated CAG information list; and in an instance in which the configuration update command message is received via a non-CAG cell, an entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cells, an allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the user equipment has requested or established an emergency PDU session with the current PLMN, performing a local release of all PDU sessions except the emergency PDU session.

[0715] In some embodiments, a method can be provided that comprises: receiving, from a user equipment, a session r...

Claims

1. A method for handling emergency services in a private network, comprising: At the user equipment (UE), a configuration update command message is received from the network entity of the current public land mobile network (PLMN), the configuration update command message including an updated Closed Access Group (CAG) information list; as well as If the entry for the current PLMN in the received CAG information list includes an indication that the UE is only allowed to access the current PLMN via a CAG cell, and if the allowed CAG list for the current PLMN in the received CAG information list does not include any CAG identifier (CAG-ID), then: -If the UE has requested or established an emergency protocol data unit (PDU) session with the current PLMN, perform local release of all PDU sessions except the emergency PDU session; as well as - If the UE has not yet requested or established an emergency PDU session with the current PLMN, it enters the PLMN deregistration search state and applies the PLMN selection process based on the received CAG information list.

2. The method according to claim 1, wherein, The configuration update command message includes one or more of the following: 5G Global Unique Temporary Identifier (5G-GUTI), Tracking Area Identifier (TAI) list, one or more Allowed Network Slice Selection Assistance Information (NSSAI), one or more Mapped Single NSSAI, Local Data Network (LADN) information, Service Area list, Mobile-Initiated Connection (MICO) indication, Network Identifier and Time Zone (NITZ) information, one or more Configured NSSAI, one or more Rejected NSSAI, Network Slice Subscription Change Indication, one or more Operator-Defined Access Category Definitions, Short Message Service (SMS) Indication, Service Interval Time Value, UE Radio Capability Identifier, 5G System Registration Result, or UE Radio Capability Identifier Deletion Indication.

3. The method according to claim 1, wherein, The configuration update command message includes a configuration update indication information element, which includes a registration request bit, and the registration request bit is set to indicate that registration is requested.

4. The method according to claim 1, further comprising: The UE sends a PDU session request to the network entity of the current PLMN.

5. An apparatus for handling emergency services in a private network, comprising: At least one processor; as well as At least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the device to at least execute: Receive a configuration update command message from a network entity of the current Public Land Mobile Network (PLMN), the configuration update command message including an updated Closed Access Group (CAG) information list; as well as If the entry for the current PLMN in the received CAG information list includes an indication that the device is only allowed to access the current PLMN via a CAG cell, and if the allowed CAG list for the current PLMN in the received CAG information list does not include any CAG identifier (CAG-ID), then: - If the device has requested or established an emergency protocol data unit (PDU) session with the current PLMN, perform local release of all PDU sessions except the emergency PDU session; as well as - If the device has not yet requested or established an emergency PDU session with the current PLMN, it enters the PLMN deregistration search state and applies the PLMN selection process based on the received CAG information list.

6. The apparatus according to claim 5, wherein, The configuration update command message includes one or more of the following: 5G Global Unique Temporary Identifier (5G-GUTI), Tracking Area Identifier (TAI) list, one or more Allowed Network Slice Selection Assistance Information (NSSAI), one or more Mapped Single NSSAI, Local Data Network (LADN) information, Service Area list, Mobile-Initiated Connection (MICO) indication, Network Identifier and Time Zone (NITZ) information, one or more Configured NSSAI, one or more Rejected NSSAI, Network Slice Subscription Change Indication, one or more Operator-Defined Access Category Definitions, Short Message Service (SMS) Indication, Service Interval Time Value, UE Radio Capability Identifier, 5G System Registration Result, or UE Radio Capability Identifier Deletion Indication.

7. The apparatus according to claim 5, wherein, The configuration update command message includes a configuration update indication information element, which includes a registration request bit, and the registration request bit is set to indicate that registration is requested.

8. The apparatus according to claim 5, wherein, The at least one memory and the computer program code are configured, together with the at least one processor, to cause the device to perform at least the following: Send a PDU session request to the network entity of the current PLMN.

9. A method for handling emergency services in a private network, comprising: At the user equipment (UE), a configuration update command message is received from the network entity of the current public land mobile network (PLMN), the configuration update command message including an updated Closed Access Group (CAG) information list; In an instance where the configuration update command message is received via a specific CAG cell, the CAG information list for the current PLMN includes an indication that the UE is only allowed to access the PLMN via a CAG cell, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the UE has not yet requested or established an Emergency Protocol Data Unit (PDU) session with the current PLMN, the UE enters the PLMN deregistration search state and applies the PLMN selection process based on the updated CAG information list; as well as In an instance where the configuration update command message is received via a specific CAG cell, the entry in the CAG information list for the current PLMN includes an indication that the UE is only allowed to access the current PLMN via a CAG cell, the allowed CAG list in the received CAG information list for the current PLMN does not include CAG identification information, and the UE has requested or established an emergency PDU session with the current PLMN, local release of all PDU sessions except the emergency PDU session is performed.

10. The method of claim 9, further comprising: In an instance where the configuration update command message is received via a non-CAG cell, the entry for the current PLMN in the CAG information list includes an indication that the UE is only allowed to access the PLMN CAG cell, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the UE has not yet requested or established an emergency PDU session with the current PLMN, the UE enters the PLMN deregistration search state and applies the PLMN selection process based on the updated CAG information list.

11. The method of claim 10, further comprising: In the instance where the configuration update command message is received via a non-CAG cell, the entry in the CAG information list for the current PLMN includes an indication that the UE is only allowed to access the PLMN CAG cell, the allowed CAG list in the received CAG information list for the current PLMN does not include CAG identification information, and the UE has requested or established an emergency PDU session with the current PLMN, local release of all PDU sessions except the emergency PDU session is performed.

12. An apparatus for processing emergency services in a private network, comprising: At least one processor; as well as At least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the device to at least execute: Receive a configuration update command message from a network entity of the current Public Land Mobile Network (PLMN), the configuration update command message including an updated Closed Access Group (CAG) information list; Upon receiving the configuration update command message via a specific CAG cell, in an instance where the CAG information list for the current PLMN includes an indication that the device is only permitted to access the PLMN via a CAG cell, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the device has not yet requested or established an Emergency Protocol Data Unit (PDU) session with the current PLMN, the device enters the PLMN deregistration search state and applies the PLMN selection process based on the updated CAG information list; as well as In the instance where the configuration update command message is received via a specific CAG cell, the entry for the current PLMN in the CAG information list includes an indication that the device is only allowed to access the current PLMN via the CAG cell, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the device has requested or established an emergency PDU session with the current PLMN, the local release of all PDU sessions except the emergency PDU session is performed.

13. The apparatus according to claim 12, wherein, The at least one memory and the computer program code are configured, together with the at least one processor, to cause the device to perform at least the following: In an instance where the configuration update command message is received via a non-CAG cell, the entry for the current PLMN in the CAG information list includes an indication that the device is only allowed to access the PLMN CAG cell, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the device has not yet requested or established an emergency PDU session with the current PLMN, the device enters the PLMN deregistration search state and applies the PLMN selection process based on the updated CAG information list.

14. The apparatus according to claim 13, wherein, The at least one memory and the computer program code are configured, together with the at least one processor, to cause the device to perform at least the following: In the instance where the configuration update command message is received via a non-CAG cell, the entry for the current PLMN in the CAG information list includes an indication that the device is only allowed to access the PLMN CAG cell, the allowed CAG list for the current PLMN in the received CAG information list does not include CAG identification information, and the device has requested or established an emergency PDU session with the current PLMN, the local release of all PDU sessions except the emergency PDU session is performed.

Images