Method to enable parallel or sequential handling of non-access stratum messages with modular NAS framework

Abstract

A user equipment (UE) is provided in which a first UE network function of UE network functions of the UE that determines that a NAS procedure associated with the user equipment has been initiated between the first UE network function and a first core network function of the corresponding core network functions that corresponds to the first UE network function The UE network functions are configured for non-access stratum (NAS) messaging with corresponding core network functions. The UE sends, based on the determining, to each respective other UE network function of the UE network functions, an indication indicating that NAS messages are not allowed between the respective other UE network functions and a corresponding core network function of the corresponding core network functions that corresponds to the respective other UE network function, wherein each other UE network function is different from the first UE network function.

Description

METHOD TO ENABLE PARALLEL OR SEQUENTIAL HANDLING OF NON-ACCESS STRATUM MESSAGES WITH MODULAR NAS FRAMEWORK Technical Field

[0001] The present disclosure generally relates to communication networks. In particular, the present disclosure relates to the handling of non-access stratum messages with a modular NAS framework. Background

[0002] A mobile telecommunication network or cellular network (generally referred to herein as a communication network) enables communications between two or more communication devices (e.g. user equipment (UE)), provides communication devices access to a data network, delivers services provides by third-party applications to communication devices, or provides services offered by the communication network to communication devices.

[0003] A communication network and communication devices may operate in accordance with cellular technologies (otherwise referred to as radio access technologies), such as GSM, UTMS, LTE, LTE-A, and NR. Cellular technologies are standardized by various standards organization, such as the Third Generation Partnership Project (3GPP) or ETSI (European Telecommunications Standards Institute). 3GPP is currently developing standards for 5th generation cellular technologies (generally referred to a 5G or NR standards) and 6thgeneration cellular technologies (generally referred to a 6G standards). Communication networks that operate in accordance with 5G or NR standards are generally referred to as 5G networks and communication networks that operate in accordance with 6G standards are generally referred to as 6G networks.

[0004] A communication network (e.g., a 5G network or a 6G network) includes access networks (e.g., radio access networks) that can communicate wirelessly with one or multiple communication devices by sharing available resources (e.g., bandwidth, transmit power, etc.) of the access network (e.g., radio access network). A communication network can also establish reliable, secure connectivity between communication devices and a core network of the communication network via access networks. A communication network (e.g., a 5G network) may provide enhanced mobile broadband services (e.g., telephony, video, data, short message services messaging services), ultra-reliable low-latency communication services (e.g., XR services), or massive machine type communication services to communication devices.

[0005] Improvements to communication networks are desirable.Summary

[0006] The present disclosure relates to handling of non-access stratum messages within a modular NAS framework.

[0007] In accordance with a first aspect of the present disclosure, there is provided method of a user equipment comprising user equipment network functions configured for non-access stratum (NAS) messaging with corresponding core network functions of a core network of a communication network, the method comprising determining, by a first user equipment network function of the user equipment network functions, that a NAS procedure associated with the user equipment has been initiated between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function; and sending, by the first user equipment network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first user equipment network function and the first core network function, to each respective other user equipment network function of the user equipment network functions, an indication indicating that NAS messages are not allowed between the respective other user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to the respective other user equipment network function, wherein each other user equipment network function of the user equipment network functions is different from the first user equipment network function.

[0008] In accordance with a second aspect of the present disclosure, there is provided apparatus comprising at least one processor and at least one memory storing instructions which, when executed by the at least one processor, cause the user equipment at least to perform determining, by a first user equipment network function of user equipment network functions of the user equipment, that a NAS procedure associated with the user equipment has been initiated between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function; and sending, by the first user equipment network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first user equipment network function and the first core network function, to each respective other user equipment network function of the user equipment network functions, an indication indicating that NAS messages are not allowed between the respective other user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to therespective other user equipment network function, wherein each other user equipment network function of the user equipment network functions is different from the first user equipment network function.

[0009] In accordance with a third aspect of the present disclosure, there is provided a computer program comprising instructions, wherein execution of the computer program by at least one processor of an user equipment causes the apparatus to perform determining, by a first user equipment network function of the user equipment network functions, that a NAS procedure associated with the user equipment has been initiated between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function; and sending, by the first user equipment network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first user equipment network function and the first core network function, to each respective other user equipment network function of the user equipment network functions, an indication indicating that NAS messages are not allowed between the respective other user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to the respective other user equipment network function, wherein each other user equipment network function of the user equipment network functions is different from the first user equipment network function.

[0010] In accordance with a fourth aspect of the present disclosure, there is provided a non-transitory computer-readable medium comprising instructions which, when executed by at least one processor of an apparatus causes the apparatus to perform determining, by a first user equipment network function of user equipment network functions, that a NAS procedure associated with the user equipment has been initiated between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function; and sending, by the first user equipment network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first user equipment network function and the first core network function, to each respective other user equipment network function of the user equipment network functions, an indication indicating that NAS messages are not allowed between the respective other user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to the respective other user equipment network function, wherein each other user equipment network function of the user equipment network functions is different from the first user equipment network function

[0011] In some or all examples of the first, second, third, and fourth aspects, the first user equipment network function comprises a user equipment mobility management function and the first core network function comprises a core network mobility management function.

[0012] In some or all examples of the first, second, third, and fourth aspects the NAS procedure that has been initiated between the first user equipment network function and a first core network function comprises a registration procedure for registering the user equipment with the first core network function; a handover procedure associated with the user equipment; or a procedure related to mobility management of the user equipment.

[0013] In some or all examples of the first, second, third, and fourth aspects the indication indicating that NAS messages are not allowed between the respective other user equipment network functions and the respective corresponding core network function comprises an indication “NAS xx messages prohibited” or an indication “NAS xx messages suspended”, wherein xx indicates a respective other user equipment network function of the user equipment network functions.

[0014] In some or all examples of the first, second, third, and fourth aspects a first other user equipment network function of the user equipment functions comprises one of the following: a user equipment network function configured for non-access stratum (NAS) messaging associated with session management (SM) of a session for the user equipment, a user equipment network function configured for non-access stratum (NAS) messaging associated with short message services (SMS) for the user equipment, a user equipment network function configured for non-access stratum (NAS) messaging associated with location management (LM) for the user equipment, a user equipment network function for non-access stratum (NAS) messaging associated with policy control for the user equipment, or a user equipment network function for non-access stratum (NAS) messaging associated with a transmission of a policy for the user equipment.

[0015] Some or all examples of the first, second, third, and fourth aspects further comprise disallowing, by a first other user equipment network function of the user equipment network functions, based on an indication indicating that NAS messages are not allowed between the first other user equipment network function of the user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to the first other user equipment network function, a NAS message between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function.

[0016] For instance, based on a determination that NAS messages are not allowed between an other user equipment network function of the user equipment network function and a corresponding core network function of the corresponding core network functions that corresponds to the other user equipment network function, the other user equipment network function disallows a NAS message between the other user equipment network function of the other user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to the other user equipment network functions.

[0017] In some or all examples of the first, second, third, and fourth aspects, the disallowing the NAS message between the first other user equipment network function and the corresponding core network function comprises delaying handling of a request from the corresponding core network function that corresponds to the first other user equipment network function; rejecting a request from the corresponding core network function that corresponds to the first other user equipment network function; preventing initiation of a NAS procedure with the corresponding core network function that corresponds to the first other user equipment network function; or preventing transmission of a NAS message to the corresponding core network function that corresponds to the first other user equipment network function.

[0018] Some or all examples of the first, second, third, and fourth aspects further comprise determining, by a first user equipment network function, that the NAS procedure between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function has been completed; and sending, by the first user equipment network function, to each respective other user equipment network function of the user equipment network functions, an indication indicating that NAS messages are to be allowed between the respective other user equipment network function of the user equipment network functions and the corresponding core network function of the corresponding core network functions that corresponds to the respective user equipment network function.

[0019] In some or all examples of the first, second, third, and fourth aspects the determining that the NAS procedure between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function has been completed comprises: receiving an acknowledgement indicating the user equipment is registered with the first core network function; receiving a message indicating a handover procedure for the user equipment has ended; or receiving a message indicating completion of the NAS procedure.

[0020] In some or all examples of the first, second, third, and fourth aspects, the determining that the NAS procedure between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function has been completed comprises: determining the first user equipment network function of the user equipment is registered with the first core network function; determining that handover of the user equipment to an entity of an access network has failed; determining the user equipment has been handed over to an entity of an access network; determining that the NAS procedure has been completed successfully; or determining that the NAS procedure has failed to complete successfully.

[0021] In some or all examples of the first, second, third, and fourth aspects, the indication indicating that the NAS messages are to be allowed between the respective other user equipment network function and the corresponding core network function that corresponds to the respective other user equipment network function comprises one of: a “NAS xx messages allowed” message, or a “NAS xx messages resume” message, wherein xx indicates the respective other user equipment network function.

[0022] Some or all examples of the first, second, third, and fourth aspects further comprise determining, by a first other user equipment network function of the user equipment network functions, based on receipt of an indication indicating that NAS messages are to be allowed between the first other user equipment network function and a corresponding core network function of the corresponding core network functions that corresponds to the first other user equipment network after receipt of an indication indicating that NAS messages are not allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function, that NAS messages are to be allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function.

[0023] Some or all examples of the first, second, third, and fourth aspects further comprise transmitting, by a first other user equipment network function of the user equipment network functions, based on receipt of an indication indicating that NAS messages are to be allowed between the first other user equipment network function and a corresponding core network function that corresponds to the first other user equipment network function after receipt of an indication indicating that NAS messages are not allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function or based on the determining, a NAS message to the corresponding core network function that corresponds to the first other user equipment network functions; or responding, by the first other user equipment network function of the user equipmentnetwork functions, based on receipt of the indication indicating that NAS messages are to be allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function after receipt of the indication indicating that NAS messages are not allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function or based on the determining, to a NAS request from the corresponding core network function that corresponds to the first other user equipment network function.

[0024] Some or all examples of the first, second, third, and fourth aspects further comprise determining, by the first user equipment network function of the user equipment network functions, that another NAS procedure has been initiated between the first user equipment network function and the first core network function of the corresponding core network functions; and sending, by the first user equipment network function, based on the determining that the another NAS procedure has been initiated between the first user equipment network function and the first core network function, another indication indicating that NAS messages are not allowed between the first other user equipment network functions and the corresponding core network function that corresponds to the first other user equipment network function.

[0025] In some or all examples of the first, second, third, and fourth aspects, the another indication comprises another “NAS xx messages prohibited” message or another “NAS xx messages suspended” message, wherein xx indicates a respective other user equipment network function of the user equipment network functions.

[0026] In accordance with a fifth aspect of the present disclosure, there is provided method of a core network entity of a core network of a communication network comprising core network functions configured for non-access stratum (NAS) messaging with corresponding user equipment network functions of a user equipment, the method comprising determining, by a first core network function of the core network entity, the core network functions comprising the first core network function, that a NAS procedure associated with the user equipment has been initiated between the first core network function and a first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function; and sending, by the first core network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first core network function and the first user equipment network function, to each respective other core network function of the core network functions, an indication indicating that NAS messages are not allowed between the respective other core network functions and a corresponding user equipment network function of the correspondinguser equipment network functions that corresponds to the respective other core network function, wherein each other core network function of the core network functions is different from the first core network function.

[0027] In accordance with a sixth aspect of the present disclosure, there is provided apparatus comprising at least one processor and at least one memory storing instructions which, when executed by the at least one processor, cause a core network entity of a core network of a communication network comprising core network functions configured for non-access stratum (NAS) messaging with corresponding user equipment network functions of a user equipment to perform determining, by a first core network function of the core network entity, the core network functions comprising the first core network function, that a NAS procedure associated with the user equipment has been initiated between the first core network function and a first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function; and sending, by the first core network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first core network function and the first user equipment network function, to each respective other core network function of the core network functions, an indication indicating that NAS messages are not allowed between the respective other core network functions and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the respective other core network function, wherein each other core network function of the core network functions is different from the first core network function.

[0028] In accordance with a seventh aspect of the present disclosure, there is provided a computer program comprising instructions, wherein execution of the computer program by at least one processor of an apparatus causes the apparatus to perform determining, by a first core network function of the core network entity, the core network functions comprising the first core network function, that a NAS procedure associated with the user equipment has been initiated between the first core network function and a first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function; and sending, by the first core network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first core network function and the first user equipment network function, to each respective other core network function of the core network functions, an indication indicating that NAS messages are not allowed between the respective other core network functions and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the respective other core networkfunction, wherein each other core network function of the core network functions is different from the first core network function.

[0029] In accordance with a eighth aspect of the present disclosure, there is provided a non-transitory computer-readable medium comprising instructions which, when executed by at least one processor of an apparatus causes the apparatus to perform determining, by a first core network function of the core network entity, the core network functions comprising the first core network function, that a NAS procedure associated with the user equipment has been initiated between the first core network function and a first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function; and sending, by the first core network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first core network function and the first user equipment network function, to each respective other core network function of the core network functions, an indication indicating that NAS messages are not allowed between the respective other core network functions and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the respective other core network function, wherein each other core network function of the core network functions is different from the first core network function

[0030] In some or all examples of the fifth, sixth, seventh, and eighth aspects, the first user equipment network function comprises a user equipment mobility management function and the first core network function comprises a core network mobility management function.

[0031] In some or all examples of the fifth, sixth, seventh, and eighth aspects, the NAS procedure that has been initiated between the first core network function and the first user equipment network function comprises: a registration procedure for registering the user equipment with the first core network function; a handover procedure associated with the user equipment; or a procedure related to mobility management of the user equipment.

[0032] In some or all examples of the fifth, sixth, seventh, and eighth aspects, the indication indicating that NAS messages are not allowed between the respective other core network functions and the respective corresponding user equipment network function comprises an indication “NAS xx messages prohibited” or an indication “NAS xx messages suspended”, wherein xx indicates a respective other core network function of the core network functions.

[0033] In some or all examples of the fifth, sixth, seventh, and eighth aspects, a first other core network function of the core functions comprises one of the following: a core network function configured for non-access stratum (NAS) messaging associated with session management (SM) of a session for the user equipment, a core network function configured for non-access stratum (NAS) messaging associated with short message services (SMS) for the user equipment, a core network function configured for non-access stratum (NAS) messaging associated with location management (LM) for the user equipment, a core network function for non-access stratum (NAS) messaging associated with policy control for the user equipment, or a core network function for non-access stratum (NAS) messaging associated with a transmission of a policy for the user equipment.

[0034] Some or all examples of the fifth, sixth, seventh, and eighth aspects further comprise disallowing, by a first other core network function of the core network functions, based on an indication indicating that NAS messages are not allowed between the first other core network function of the core network functions and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the first other core network function, a NAS message between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function.

[0035] For specification: For instance, based on a determination that NAS messages are not allowed between an other core network function of the core network function and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the other core network function, the other core network function disallows a NAS message between the other core network function of the other core network functions and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the other core network functions.

[0036] In some or all examples of the fifth, sixth, seventh, and eighth aspects, the disallowing the NAS message between the first other core network function and the corresponding user equipment network function comprises: delaying handling of a request from the corresponding user equipment network function that corresponds to the first other core network function; rejecting a request from the corresponding user equipment network function that corresponds to the first other core network function; preventing initiation of a NAS procedure with the corresponding user equipment network function that corresponds to the first other core network function; or preventing transmission of a NAS message to the corresponding user equipment network function that corresponds to the first other core network function.

[0037] Some or all examples of the fifth, sixth, seventh, and eighth aspects further comprise determining, by a first core network function, that the NAS procedure between the first core network function and a firstuser equipment network function of the corresponding user equipment network functions that corresponds to the first core network function has been completed; and sending, by the first core network function, to each respective other core network function of the core network functions, an indication indicating that NAS messages are to be allowed between the respective other core network function of the core network functions and the corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the respective core network function.

[0038] In some or all examples of the fifth, sixth, seventh, and eighth aspects, the determining that the NAS procedure between the first core network function and a first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function has been completed comprises: determining the user equipment is registered with the first core network function; determining a handover procedure for the user equipment has ended; or receiving a message indicating completion of the NAS procedure.

[0039] In some or all examples of the fifth, sixth, seventh, and eighth aspects, the determining that the NAS procedure between the first core network function and a first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function has been completed comprises: determining the first user equipment network function of the user equipment is registered with the first core network function; determining that handover of the user equipment to an entity of an access network has failed; determining the user equipment has been handed over to an entity of an access network; determining the determining that the NAS procedure has been completed successfully; or determining the determining that the NAS procedure has failed.

[0040] In some or all examples of the fifth, sixth, seventh, and eighth aspects, the indication indicating that the NAS messages are to be allowed between the respective other core network function and the corresponding user equipment network function that corresponds to the respective other core network function comprises one of: a “NAS xx messages allowed” message, or a “NAS xx messages resume” message, wherein xx indicates the respective other core network function.

[0041] Some or all examples of the fifth, sixth, seventh, and eighth aspects, further comprise determining, by a first other core network function of the core network functions, based on receipt of an indication indicating that NAS messages are to be allowed between the first other core network function and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the first other core network after receipt of an indication indicating that NAS messages are not allowed between the first other core network function and the corresponding user equipmentnetwork function that corresponds to the first other core network function, that NAS messages are to be allowed between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function.

[0042] Some or all examples of the fifth, sixth, seventh, and eighth aspects further comprise transmitting, by a first other core network function of the core network functions, based on receipt of an indication indicating that NAS messages are to be allowed between the first other core network function and a corresponding user equipment network function that corresponds to the first core network function after receipt of an indication indicating that NAS messages are not allowed between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function or based on the determining, a NAS message to a corresponding user equipment network function that corresponds to the first other core network function; or responding, by the first other core network function of the core network functions, based on receipt of the indication indicating that NAS messages are to be allowed between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function after receipt of the indication indicating that NAS messages are not allowed between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function or based on the determining, to a NAS request from the corresponding user equipment network function that corresponds to the first other core network function.

[0043] Some or all examples of the fifth, sixth, seventh, and eighth aspects further comprise determining, by the first core network function of the core network functions, that another NAS procedure has been initiated between the first core network function and the first user equipment network function of the corresponding user equipment network functions; and sending, by the first core network function, based on the determining that the another NAS procedure associated has been initiated between the first core network function and the first user equipment network function, another indication indicating that NAS messages are not allowed between the first other core network functions and the corresponding user equipment network function that corresponds to the first other core network function.

[0044] In some or all examples of the fifth, sixth, seventh, and eighth aspects, the another indication comprises another “NAS xx messages prohibited” message or another “NAS xx messages suspended” message, wherein xx indicates a respective other core network function of the core network functions.

[0045] It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the presentdisclosure. Other aspects and features of the present disclosure will become apparent to those of ordinary skill in the art upon review of the following description of example implementations in conjunction with the accompanying figures.

[0046] In accordance with a first aspect of the present disclosure, there is provided method of a user equipment comprising user equipment network functions configured for non-access stratum (NAS) messaging with corresponding core network functions of a core network of a communication network, the method comprising: Brief Description of the Drawings

[0047] Reference will now be made, by way of example, to the accompanying drawings which show example embodiments of the present application, and in which:

[0048] FIG.1 is a schematic block diagram illustrating a system comprising a user equipment, a communication network, and a data network in accordance with example embodiments described herein.

[0049] FIG.2 is a schematic diagram illustrating various physical and logical components of an apparatus of the communication network of Figure 1 in accordance with some example embodiments described herein.

[0050] FIG.3 is a schematic diagram illustrating various physical and logical components of a user equipment in accordance with example embodiments described herein.

[0051] FIG.4 is an illustration of a signal and operations illustrating a system comprising a user equipment, a communication network, and a data network in accordance with example. embodiments described herein.

[0052] FIG.5 is an illustration of a signal and operations illustrating a system comprising a user equipment, a communication network, and a data network in accordance with example.

[0053] FIG.6 is a flowchart of a method of a user equipment in accordance with example embodiments described herein.

[0054] FIG.7 is a flowchart of a method of a core network entity in accordance with example embodiments described herein.

[0055] Similar reference numerals may have been used in different figures to denote similar components. Unless otherwise specifically noted, articles depicted in the drawings are not necessarily drawn to scale. Detailed Description of Example Embodiments

[0056] The subject matter is described herein with reference to the accompanying drawings, in which embodiments are shown. However, many different embodiments may be used, and thus the descriptionshould not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same elements, and prime notation is used to indicate similar elements, operations or steps in alternative embodiments. Separate boxes or illustrated separation of functional elements of illustrated systems and devices does not necessarily require physical separation of such functions, as communication between such elements may occur by way of messaging, function calls, shared memory space, and so on, without any such physical separation. As such, functions need not be implemented in physically or logically separated platforms, although such functions are illustrated separately for ease of explanation herein. Different devices may have different designs, such that although some devices implement some functions in fixed function hardware, other devices may implement such functions in a programmable processor with code obtained from a machine-readable medium. Lastly, elements referred to in the singular may be plural and vice versa, except wherein indicated otherwise either explicitly or inherently by context.

[0057] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0058] Referring to Figure 1, an example system 100 that includes a user equipment (UE) 106, a communication network 101 and a data network 108 is shown. The communication network 101 includes an access network 102 and a core network 104 that includes one or more network functions 110 (otherwise referred to herein as network entities 110). The user equipment 106 also includes one or more network functions 107 of the same type of network function of the network functions of the core network 110.

[0059] The access network 102 provides wireless connectivity (e.g., radio connectivity) to the UE 106 and connects the UE 106 to the core network 104 via a backhaul network. The access network 102 may comprise a Radio Access Network, a non-terrestrial network (e.g., a satellite network), a wireless local area network (WLAN) or any other type of network that provides wireless connectivity to the UE 106 and connects the UE 106 to the core network 104. The access network 102 provides wireless connectivity to the UE 106 via at least one access node of the access network. An access node may comprise a gNodeB(gNB), an ng-eNodeB (ng-eNB)), an eNodeB (eNB), or Wireless Local Area Network (WLAN) access point. The backhaul network between the access network 102 and the core network 104 may comprises a fixed network, a satellite network, or a combination thereof. The access network 102 may provide the UE 106 fixed access. The core network 104 connects the access network 102 with a data network (DN) 108 via a N6 interface (not shown) of the core network 104.

[0060] As noted above, the core network 104 is comprised of Network Functions (NF) 110. Each respective network function may be implemented as a software running on dedicated hardware (e.g., one or more physical computing devices, such as servers), as a virtualized network function (VNF) instantiated on a physical or virtual machine, or as a container provided by infrastructure of a cloud computing system. Data network 108 may be an operator external public or private data network, or an intra-operator data network (e.g., for IP Multimedia Subsystem (IMS) services). The UE 106 (also referred to as a mobile terminal) is configured to access the access network 102, register with the core network 104 for example via a mobility management function (MMF) (NF 110) of the core network, establish one or more data sessions with a core network via a session management function (SMF) (NF 110), and access services provided by the core network 104 (for example, via a policy control function (PCF) (NF 110) of the core network or a unified data management (UDM) of the core network (NF 110) and / or application functions (not shown) hosted on application servers (not shown) of the data network 108. For those purposes, the UE 106 includes user equipment network functions 107 and each respective user equipment network function 107 provides functionality for connecting with a corresponding network function 110 of the core network 104 that corresponds to the respective user equipment network functions 107. For example, the user equipment 106 has a user equipment network function 1071, 2, .. xthat corresponds to a core network function 1101, 2, .. xof the core network 104. For example, a user equipment includes a user equipment network function for mobility management via which the user equipment communicates with a corresponding core network function for mobility management. User equipment network functions operate at least as NAS connection terminations.

[0061] FIG.2 shows various physical and logical components of an exemplary apparatus 100 comprising one or more network functions of the communication network, including mobility management function (referred to as MMF or MM herein), session management function (referred to as SMF or SM herein), location management function (referred to as LMF or LM herein), policy management function (referred to as PCF or PF herein), unified data management function (referred to as UDMF or UDM herein) in accordance with an embodiment of the present disclosure. Although an example embodiment of theapparatus 200 is shown and discussed below, other embodiments may be used to implement examples disclosed herein, which may include components different from those shown. Although FIG.2 shows a single instance of each component of the apparatus 200, there may be multiple instances of each component shown.

[0062] The apparatus 200 includes one or more processors 202, such as a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a dedicated logic circuitry, a graphics processing unit (GPU), a tensor processing unit, a neural processing unit, a dedicated artificial intelligence processing unit, a hardware accelerator, or combinations thereof. The one or more processors 202 may collectively be referred to as a processor 202.

[0063] The apparatus 200 also includes one or more memories 204 (collectively referred to herein as “memory 204”), which may include volatile or non-volatile memory (e.g., a flash memory, a random-access memory (RAM), and / or a read-only memory (ROM)). The memory 204 may store machine-executable instructions for execution by at least one of the one or more processors 202. For example, the a machine- executable instructions 206 of a mobility management function, session management function, policy control function, unified data management function described herein may be stored in the memory 204, which may be executed by at least one of the one or more processors 202, cause the apparatus 200 to perform the operations of the mobility management function, session management function, policy control function, unified data management function, and the like described herein. The memory 204 may store machine-executable instructions for execution by the processor 202, such as machine-executable instructions of other network functions of the core network 104 described above in reference to FIG.1.

[0064] The memory 204, in addition to the machine-executable instructions 206 may store data, information, rules, and / or policies. The execution of the machine-executable instructions 206 (or the execution of the instructions of the software code) may for example cause the apparatus 200 to perform one or more operations, including the operations described herein with respect to FIG.7.

[0065] In some examples, the apparatus 200 may also include one or more electronic storage units (not shown), such as a solid-state drive, a hard disk drive, a magnetic disk drive and / or an optical disk drive. In some examples, one or more datasets and / or modules may be provided by an external memory (e.g., an external drive in wired or wireless communication with the computing system 100) or may be provided by a transitory or non-transitory computer-readable medium. Examples of non-transitory computer readable media include a RAM, a ROM, an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a CD-ROM, or other portable memory storage. Thestorage units and / or external memory may be used in conjunction with memory 204 to implement data storage, retrieval, and caching functions of the computing system 100.

[0066] The processor 202 and memory 204 of the apparatus 200 may communicate with each other via a communication bus, for example. In some embodiments, the apparatus 200 is a distributed computing system that includes multiple computing devices (e.g., servers) in communication with each other. The various operations described herein may be performed by different the computing devices (e.g., servers) of a distributed computing system in some embodiments. In some embodiments, the apparatus 200 is a virtual machine provided by a cloud computing platform.

[0067] Referring to FIG.3, an example of user equipment 106 is shown. Although an example embodiment of a user equipment 106 is shown and discussed below, other embodiments may be used to implement examples disclosed herein, which may include components different from those shown. Although FIG.3 shows a single instance of each component of the user equipment, there may be multiple instances of each component shown.

[0068] The user equipment 106 may be any device capable of sending and receiving radio signals. Non- limiting examples of a user equipment include a mobile station (MS), a mobile device such as a mobile phone or what is known as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine-type communications (MTC) device, an Internet of things (IoT) type communication device or any combinations of these or the like.

[0069] The user equipment 106 also includes one or more processors 301, one or more memories 302 (collectively referred to as memory 302) and other components or circuitry 303 for use in software and hardware aided execution of operations the user equipment 106 is configured to perform, including control of access to and communications with radio access networks (e.g., the RAN illustrated in FIG.1). The processor 301 is coupled to the memory 302. The one or more processors 301 may comprise a central processing unit (CPU), a microprocessor, multicore processor, a tensor processing unit (TPU), a graphics processing unit (GPU), a neural processing unit (NPU), a dedicated logic circuit, an application specific integrated circuit, a field programmable gate array (FPGA), a dedicated artificial intelligence processing unit, a hardware accelerator, or any combinations thereof. The memory 302 may include a volatile or non- volatile memory (e.g., a flash memory, a random-access memory (RAM), and / or a read-only memory (ROM)).

[0070] The processor 301 may be configured to execute software code 308 (e.g., the processor mayexecute instructions of the software code 308). The execution of the software code 308 (or the execution of the instructions of the software code) may for example cause the user equipment 106 to perform one or more operations, including the operations described herein with respect to FIG.6. The software code 308 may be stored in the memory 302.

[0071] The user equipment 106 also include an antenna array 304 and a transceiver 306 for transmitting wireless signals (e.g., radio signals) to access nodes of an access network (e.g., a radio access network nodes of a RAN) and / or receiving wireless signals from access nodes of an access network (e.g., a radio access network nodes of a RAN) over an air interface 307. The wireless signals (e.g., radio signals) may carry communications, such as voice, electronic mail (email), text messages, multimedia data, and / or machine data. The antenna array 306 may be arranged internally or externally to the user equipment 106. The antenna array 306 may comprise one or more antenna elements. The antenna array 306 may be a multi-input multi output (MIMO) antenna.

[0072] The processor 301, the at least one memory 302, the transceiver 306 and other components or circuitry 303 of the user equipment 106 (e.g., a modem) can be provided on a circuit board, in chipsets, or in a system on chip (SOC). The circuit board, chipsets or SOC is denoted by reference 304 in Figure 3. The user equipment 106 may optionally include display device 305, such as a touch-sensitive display device. The user equipment 106 also includes a battery (not shown). The user equipment 106 may also include a speaker (not shown) and a microphone (not shown). The user equipment 102 may also include a universal subscriber identity module (USIM) or an embedded subscriber identity module (eSIM).

[0073] With reference to Figure 4, according to a service-based radio access network – core network (RAN-CN) interface architecture for a communication network, the RAN can directly communicate with any network functions (NFs) in the core network (CN), for example via non-access stratum (NAS) messages. The RAN can directly communicate with any network functions (NFs) in principle, as there may be exceptions. For example, due to security reasons, a RAN in a visited public land mobile network (VPLMN) may not be able to communicate directly with an NF in the home public land mobile network (HPLMN).

[0074] In contrast to directly communicating with any network functions (NFs), in 5G communication networks, a RAN can communicate with only an access and mobility management function (AMF) among the NFs in a 5G core (5GC), and a RAN can communicate with only a mobility management entity (MME) among the NFs in an evolved packet core (EPC). A non-exhaustive list of example NAS messages includes NAS messages related to: UE policy delivery, which are exchanged between a UE and a policy control function (PCF) so thatthe PCF can provision UE policies to the UE; UE parameters update (UPU), which are exchanged between a UE and a unified data management function (UDM) so that the UDM can provision parameters in the UE, where the parameters do not impact network selection; and Steering of roaming (SoR), which are exchanged between a UE and a UDM so that the UDM can provision network selection-related parameters in the UE.

[0075] Despite various types of NAS messages being destined for various NFs in the 5GC or EPC for the provision of services by a particular NF (e.g., by the PCR, UDM, etc.), one commonality between 5GC and EPC is that all NAS messages go through a RAN and a single core network (CN) NF (i.e., MME in EPC, AMF in 5GC) before being forwarded to the particular NF, which is obvious because there is only one NF in 5GC or EPC with which the RAN can communicate.

[0076] One of the key features of the RAN-CN interface architecture for a communication network is that a RAN directly sends / receives a NAS message to / from a CN NF terminating the NAS message. For example, compared to the 5G operations where an uplink 5G session management (5GSM) message is sent from a UE to a session management function (SMF) via a RAN and an AMF and a downlink 5GSM message is sent from an SMF to a UE via AMF and RAN, with the RAN-CN interface architecture and distributed NAS connection terminations at a UE, the UE can send an uplink session management (SM) message to an NF handling SM via RAN and an NF handling SM can send a downlink SM message to a UE via RAN. As a result, one hop is reduced.

[0077] FIG.4 is an illustration of a signal and operations illustrating a system comprising a user equipment, a communication network, and a data network in accordance with example embodiments described herein. FIG.4 illustrates the RAN-CN interface architecture for a communication network. UE 10 communicates via RAN 20 with NF 1 – X (e.g., MM NF, SM NF, LM NF, … XX NF). For that purpose, UE 10 includes distributed NAS connection termination interfaces (also referred to herein as user equipment network functions) for communication with NFs of the core network. Each respective NAS connection termination interface of the user equipment is configured to communication with a corresponding NF of the core network. For example, UE has user equipment network functions or modules (depicted as MM, SM, LM, … XX) that correspond to the MM NF, SM NF, LM NF, … XX NF of the core network.

[0078] Various procedures of and / or NAS messages related to a network function of a core network NAS messages may need to be handled in isolation and other types of NAS messages must not be allowed at the same time For example, mobility management (MM) messages (e.g. messages related to mobilitymanagement MM such as those related to a Registration / Deregistration procedure may need to be handled in isolation and other types of NAS messages must not be allowed at this time. However, the modular NAS framework may enable other NAS procedures to be handled in parallel. The present disclosure provides both in the network and in the UE, specific methods to either to allow or prohibit parallel handling of NAS messages in the modular NAS framework. More specifically, since different pairs of corresponding NAS modules / NF functions are assumed to operate independently in the UE and core, the present disclosure provide the ability to control the handing messages by these pairs of corresponding NAS modules / NF functions in parallel or sequential.

[0079] There are two methodologies a disclosed to mitigate this issue for modular NAS framework in 6G.

[0080] A first methodology is denoted prohibit - allow collision handling. In this methodology, NAS xx procedures (i.e., non-MM NAS procedures) can occur in parallel with NAS MM procedures except for specific NAS MM Procedures (e.g., NAS MM Registration / Deregistration procedure) which needs to happen on its own: 1) In the UE, NAS xx modules assume any NAS procedure is “prohibited” until it is informed by the NAS MM module that it is “allowed” to initiate NAS xx procedure. 2) Upon successful completion of the NAS MM Procedure (e.g., NAS MM Registration procedure), both NAS MM module in the UE and MM NF (supporting NAS MM module) in the network indicate “NAS procedures allowed” to NAS xx module(s) in the UE and NFx (supporting NAS xx modules) in the network respectively. 3) When NAS MM Procedure (e.g., NAS MM Deregistration procedure) is triggered, NAS MM module in the UE and MM NF in the network indicate “NAS procedures prohibited” to NAS xx module(s) in the UE and NFx in the network respectively.

[0081] A second methodology is denoted: suspend-resume collision handling. When an NAS MM procedure is ongoing, all other NAS procedures (other than MM) should be suspended. If the NAS modules within the UE are supported independently, the MM NAS module within the UE requests all other NAS modules to “suspend” NAS messages when the MM procedure is ongoing and it also indicates “resume” towards other NAS modules MM procedure is completed. Similarly, NFx only handles non-MM NAS messages and does not have visibility of ongoing MM NAS procedures (known by MM NF). Similarly, NAS MM module may not be aware of all the non-MM NAS procedures that are ongoing.

[0082] Non-MM NAS messages may be suspended / rejected during ongoing MM NAS procedures by one of the following 3 methods:1) For the Uplink, UE MM NAS module indicates “suspend” to other UE NAS xx modules upon triggering mobility management messages and indicates “resume” to other UE NAS xx modules upon completion of the MM procedure. Similarly, for the Downlink, Network MM NF indicates “suspend” and “resume” to other NFx as appropriate. Other NAS modules in the UE and Network (NFx) will suspend NAS xx procedures upon receipt of “suspend” and “resume” NAS procedures as appropriate. Suspend / Resume can be achieved in two ways: NFx can either subscribe to notifications (PUSH) from MM NF / NAS MM module or NFx can query (PULL) MM NF about ongoing MM NAS procedures. The NFx can then decide to either send or suspend initiating NAS xx message based on the notification / response from MM NF / NAS MM module. 2) For the uplink, the network either delays handling of other NAS xx procedures or rejects the NAS xx procedure with a specific cause code e.g. “collision with MM, re-attempt” (when MM procedure is ongoing) if the UE initiates NAS xx procedure when NAS MM procedure is ongoing. For the downlink, the UE either delays handling of other NAS xx procedures or rejects the NAS xx procedure with a specific cause code e.g. “collision with MM, re-attempt". 3) For the downlink, RAN suspends transfer of NAS xx message when NAS MM procedure is ongoing.

[0083] When there is an ongoing NAS MM procedure, indications needs to be sent by the UE and / or the MM NF. For example, in a RRC message carrying the first MM message of a NAS MM procedure, the UE or the MM NF which initiates the NAS MM procedure includes: - an indication that a NAS MM procedure is started; and - optionally, an identifier / index assigned for the NAS MM procedure; and in a RRC message carrying the last message of a NAS MM procedure, the UE or the MM NF which sends the last MM message of the NAS MM procedure includes: - an indication that a NAS MM procedure is completed; and - optionally, an identifier / index assigned for the NAS MM procedure.

[0084] Using these indications, RAN or NN suspends transfer of any non-MM NAS messages after receiving the started indication and before receiving the completed indication of a NAS MM procedure.

[0085] For a NAS MM procedure composed of a single MM message or a NAS MM procedure which does not have to be prioritized over non-MM procedures, the initiator may choose to not include any of the indications above. With that, if RAN or NN receives a NAS MM message without any indications described above, RAN can transfer non-MM NAS messages without any suspension.

[0086] When the UE / Network NAS module is prohibited to send / receive NAS messages, it is simply not possible to even encode / decode NAS message nor possible to transmit as no NAS association is available, also no security context is setup. However, when the UE / Network NAS module is suspended (as in method 2 below), it may be possible to encode / decode NAS message and it is also possible to transmit although it is not desired to do so. The Prohibited / Allowed methodology and the Suspend / Resume methodology can be used in conjunction with each other. In particular, once allowed, NAS messages may thereafter be suspended and resumed.

[0087] With further respect to Figure 4 and the Prohibited-Allowed Collision Handling methodology, within the UE, MM NAS module and within the network, MM NF plays the gate control role as it shall ensure that other NAS modules are not initiated until registration procedure is successfully completed. Similarly, when deregistration procedure has been triggered, UE MM NAS module and MM NF ensure that no other NAS procedure is initiated after that.

[0088] The following actions are required within the UE: 1) Upon initiation of a Registration procedure, the NAS MM Module indicates “ NAS xx messages prohibited” to other NAS modules such as SM, SMS, Location, policy etc. 2) Upon receipt of “NAS xx messages prohibited” indication from NAS MM module, NAS xx module is not allowed anymore to transmit NAS xx messages to the network. 3) Upon successful completion of Registration procedure, NAS MM module indicates “NAS xx messages allowed” to other NAS modules such as SM, SMS, Location, policy etc. 4) Upon receipt of “NAS xx messages allowed” indication from NAS MM module, NAS xx module is now allowed to transmit NAS xx messages to the network. 5) Upon successful completion of Deregistration procedure, NAS MM module indicates “NAS xx messages prohibited” to other NAS modules such as SM, SMS, Location, policy etc.

[0089] The following actions are required within the Network: 1) Upon initiation of a Registration procedure, the MM NF indicates “ NAS xx messages prohibited” to other NAS NFx terminating NAS modules such as SM, SMS, Location, policy etc. 2) Upon receipt of “NAS xx messages prohibited” indication from MM NF, NFx is not allowed anymore to transmit NAS xx messages to the UE. 3) Upon successful completion of Registration procedure, MM NF indicates “NAS xx messages allowed” to other NAS NFx4) Upon receipt of “NAS xx messages allowed” indication from MM NF, NFx is now allowed to transmit NAS xx messages to the UE. 5) Upon successful completion of Deregistration procedure, MM NF indicates “NAS xx messages prohibited” to other NFx terminating NAS modules such as SM, SMS, Location, policy etc.

[0090] FIG.5 is an illustration of a signal and operations illustrating a system comprising a user equipment, a communication network, and a data network in accordance with example embodiments described herein. With further respect to Figure 4 and the Suspend-Resume Collision Handling methodology, When any MM NAS procedure is initiated Non MM NAS procedures shall be suspended until the MM NAS procedure had completed. When a UE’s MM NAS Module detects a MM NAS procedure is initiated and completed it shall send a “Suspend” and “Resume” respectively to all other UE Non MM NAS Modules. Similarly, when the Network MM NAS NF detects a MM NAS procedure is initiated and completed it shall send a “Suspend” and “Resume” respectively to all other UE Non MM NAS NFs.A UE Non MM NAS Module or a Network Non MM NAS NF shall initiate a Non MM NAS procedures only after they have received a “Resume” indication. Successful completion of a MM NAS Deregistration procedure shall result in a “Suspend” being sent by the MM NAS Module / NF.

[0091] The following actions are required within the UE: 1) Upon initiation of a NAS MM procedure, the NAS MM Module indicates “Suspend” to other NAS modules such as SM, SMS, Location, policy etc. 2) Upon receipt of “Suspend” indication from NAS MM module, NAS xx module is not allowed anymore to transmit NAS xx messages to the network. 3) Upon successful completion of NAS MM procedure, NAS MM module indicates “Resume” to other NAS modules such as SM, SMS, Location, policy etc. 3) Upon receipt of “Resume” indication from NAS MM module, NAS xx module is now allowed to transmit NAS xx messages to the network. 4) Upon successful completion of NAS MM Deregistration procedure, NAS MM module indicates “Suspend” to other NAS modules such as SM, SMS, Location, policy etc.

[0092] The following actions are required within the Network: 1) Upon initiation of a NAS MM procedure the MM NF indicates “Suspend” to other NAS NFx terminating NAS modules such as SM, SMS, Location, policy etc.2) Upon receipt of “Suspend” indication from MM NF, NFx is not allowed anymore to transmit NAS xx messages to the UE. 3) Upon successful completion of NAS MM procedure, MM NF indicates “Resume” to other NAS NFx 4) Upon receipt of “Resume” indication from MM NF, NFx is now allowed to transmit NAS xx messages to the UE. 5) Upon successful completion of NAS MM Deregistration procedure, MM NF indicates “Suspend” to other NFx terminating NAS modules such as SM, SMS, Location, policy etc.

[0093] The following suspend-resume optimization options only apply to the network NAS NF’s as UE MM NAS Module shall always send Suspend / Resume to all other UE NAS Modules: Option 1: MM NF sends Suspend / Resume only to those NAS NFs that requested UE Connectivity after last transition to RRC Idle Mode. MM NF maintains a list of those NAS NF’s which requested connectivity with the UE since the UE last transitioned from Idle to Connected Mode(as these NAS NF’s could potentially execute NAS procedures with the UE). MM NF shall send a Suspend / Resume only to these NAS NFs(which could be either a subset or all the NAS NF’s that have a NAS Connection with the UE). When the UE transitions to Idle Mode the MM NF shall clear the above list. Option 2: MM NF sends Suspend to all NAS NF’s which terminate UE NAS Connections NAS NFs which receive a Suspend notification shall explicitly indicate in the Suspend response if a Resume notification is required, otherwise the MM NF will assume one is not required. If a NAS NF does not explicitly request a Resume notification and subsequently needs to communicate with the UE it shall first trigger a request towards the MM NF to determine if Suspend mode is still active or cleared and proceed accordingly. Option 3: MM NF sends Suspend only to those NAS NFs that requested UE Connectivity after last transition to RRC Idle Mode. MM NF behavior is as in Option 1 and NAS NF behavior is as in Option 2 above.

[0094] In all methodologies and instances, when a NAS NFx establishes a NAS Connection with a UE, it may register with the MM NF for notification of suspend, UE reachability etc. MM NF shall keep a record of the NFx instance / NFx set assigned for the given UE and use them to identify the NAS NFx’s which it needs to send notifications to. Non MM NAS NFs(i.e. NFx) may receive Notifications(Prohibited / Allowed / Suspend / Resume) described above regarding initiated or completed NAS procedures either via a PUSH or a PULL mechanisms for a given UE.

[0095] In all methodologies and instances, the case of PUSH each NFx shall Subscribe to the MM NF and when an event is triggered MM NF shall send a Notification to each subscribed NFx. Subscription may occur as a result of an explicit subscription request or may be implicit as a result of an earlier procedure with the MM NF.

[0096] In all methodologies and instances, in the case of PULL, the NFx shall not Subscribe to Notifications from the MM NF but shall, prior to initiating a Non MM NAS procedure, always query the MM NF to learn whether the Non MM NAS procedure is permitted or not. If a Non MM NAS procedure is not permitted the NFx may subsequently either request the MM NF to notify it when the procedure is permitted or query the MM NF once again after a period of time(configurable) has elapsed.

[0097] For example, In the case of PUSH Notifications, if the MM NF detects a Handover has been initiated it shall send a notification to NFx’s instructing them not to initiate NAS procedures and when the MM NF detects the Handover procedure is completed it shall send a notification to NFx’s indicating NAS procedure are allowed.

[0098] The steps (also referred to as operations) in the flowcharts and drawings described herein are for purposes of example only. There may be many variations to these steps (or operations) without departing from the scope of the present disclosure. For instance, the steps may be performed in a differing order, or steps may be added, deleted, or modified, as appropriate.

[0099] FIG.6 is a flowchart of a method 600 of a user equipment in accordance with example embodiments described herein.

[0100] At operation 602, a first user equipment network function of a user equipment having user equipment network functions determines that a NAS procedure associated with the user equipment has been initiated between the first user equipment network function and a first core network function of corresponding core network functions that corresponds to the first user equipment network function; and

[0101] At operation 604, the first user equipment network function sends, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first user equipment network function and the first core network function, to each respective other user equipment network function of the user equipment network functions, an indication indicating that NAS messages are not allowed between the respective other user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to the respective other user equipment network function, wherein each other user equipment network function of the user equipment network functions is different from the first user equipment network function.

[0102] At operation 606, a first other user equipment network function of the user equipment network functions, based on an indication indicating that NAS messages are not allowed between the first other user equipment network function of the user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to the first other user equipment network function, disallows a NAS message between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function.

[0103] At operation 608, the first user equipment network function determines that the NAS procedure between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function has been completed.

[0104] At operation 610, the first user equipment network function sends, to each respective other user equipment network function of the user equipment network functions, an indication indicating that NAS messages are to be allowed between the respective other user equipment network function of the user equipment network functions and the corresponding core network function of the corresponding core network functions that corresponds to the respective user equipment network function.

[0105] FIG.7 is a flowchart of a method 700 of a core network entity in accordance with example embodiments described herein.

[0106] At operation 702, a first core network function of a core network entity having core network functions determines that a NAS procedure associated with the core network entity has been initiated between the first core network function and a first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function; and

[0107] At operation 704, the first core network function sends, based on the determining that the NAS procedure associated with the core network function has been initiated between the first core network function and the first user equipment network function, to each respective other core network function of the core network functions, an indication indicating that NAS messages are not allowed between the respective other core network functions and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the respective other core network function, wherein each other core network function of the core network functions is different from the first core network function.

[0108] At operation 706, a first other core network function of the core network functions, based on an indication indicating that NAS messages are not allowed between the first other core network function ofthe core network functions and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the first other core network function, disallows a NAS message between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function.

[0109] At operation 708, the first user equipment network function determines that the NAS procedure between the first core network function and a first user equipment network function of the corresponding user equipment functions that corresponds to the first core network function has been completed.

[0110] At operation 710, the first core network function sends, to each respective other core network function of the core network functions, an indication indicating that NAS messages are to be allowed between the respective other core network function of the core network functions and the corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the respective core network function.

[0111] Through the descriptions of the preceding embodiments, the subject matter disclosed may be implemented by using hardware only, or by using software and a necessary universal hardware platform, or by a combination of hardware and software. The coding of software for carrying out the above-described methods described is within the scope of a person of ordinary skill in the art having regard to the present disclosure. Based on such understandings, the technical solution of the subject matter disclosed herein may be embodied in the form of a software product. The software product may be stored in a non-volatile or non-transitory storage medium, which can be an optical storage medium, flash drive or hard disk. The software product includes a number of instructions that enable a computing device (personal computer, server, or network device) to execute the methods provided in the embodiments of the present disclosure.

[0112] All values and sub-ranges within disclosed ranges are also disclosed. Also, although the systems, devices and processes disclosed and shown herein may comprise a specific plurality of elements, the systems, devices and assemblies may be modified to comprise additional or fewer of such elements. Although several example embodiments are described herein, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the example methods described herein may be modified by substituting, reordering, or adding steps to the disclosed methods.

[0113] Features from one or more of the above-described embodiments may be selected to create alternate embodiments comprised of a sub-combination of features which may not be explicitly described above. In addition, features from one or more of the above-described embodiments may be selected andcombined to create alternate embodiments comprised of a combination of features which may not be explicitly described above. Features suitable for such combinations and sub-combinations would be readily apparent to persons skilled in the art upon review of the present disclosure as a whole.

[0114] In addition, numerous specific details are set forth to provide a thorough understanding of the example embodiments described herein. It will, however, be understood by those of ordinary skill in the art that the example embodiments described herein may be practiced without these specific details. Furthermore, well-known methods, procedures, and elements have not been described in detail so as not to obscure the example embodiments described herein. The subject matter described herein and in the recited claims intends to cover and embrace all suitable changes in technology.

[0115] Although the subject matter disclosed herein and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the invention as defined by the appended claims.

[0116] The subject matter discussed herein may be embodied in other specific forms without departing from the subject matter of the claims. The described example embodiments are to be considered in all respects as being only illustrative and not restrictive. The subject matter discussed herein intends to cover and embrace all suitable changes in technology. The scope of the present disclosure is, therefore, described by the appended claims rather than by the foregoing description. The scope of the claims should not be limited by the embodiments set forth in the examples, but should be given the broadest interpretation consistent with the description as a whole.

Claims

Claims 1. A method of a user equipment comprising user equipment network functions configured for non-access stratum (NAS) messaging with corresponding core network functions of a core network of a communication network, the method comprising: determining, by a first user equipment network function of the user equipment network functions, that a NAS procedure associated with the user equipment has been initiated between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function; and sending, by the first user equipment network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first user equipment network function and the first core network function, to each respective other user equipment network function of the user equipment network functions, an indication indicating that NAS messages are not allowed between the respective other user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to the respective other user equipment network function, wherein each other user equipment network function of the user equipment network functions is different from the first user equipment network function.

2. The method according to claim 1, wherein the first user equipment network function comprises a user equipment mobility management function and the first core network function comprises a core network mobility management function.

3. The method according to any of claims 1 to 2, wherein the NAS procedure that has been initiated between the first user equipment network function and a first core network function comprises: a registration procedure for registering the user equipment with the first core network function; a handover procedure associated with the user equipment; or a procedure related to mobility management of the user equipment.

4. The method according to any of claims 1 to 3, wherein the indication indicating that NAS messages are not allowed between the respective other user equipment network functions and the respective corresponding core network function comprises an indication “NAS xx messages prohibited” or anindication “NAS xx messages suspended”, wherein xx indicates a respective other user equipment network function of the user equipment network functions.

5. The method according to any of claims 1 to 4, wherein a first other user equipment network function of the user equipment functions comprises one of the following: a user equipment network function configured for non-access stratum (NAS) messaging associated with session management (SM) of a session for the user equipment, a user equipment network function configured for non-access stratum (NAS) messaging associated with short message services (SMS) for the user equipment, a user equipment network function configured for non-access stratum (NAS) messaging associated with location management (LM) for the user equipment, a user equipment network function for non-access stratum (NAS) messaging associated with policy control for the user equipment, or a user equipment network function for non-access stratum (NAS) messaging associated with a transmission of a policy for the user equipment.

6. The method according to any of claims 1 to 5, further comprising: disallowing, by a first other user equipment network function of the user equipment network functions, based on an indication indicating that NAS messages are not allowed between the first other user equipment network function of the user equipment network functions and a corresponding core network function of the corresponding core network functions that corresponds to the first other user equipment network function, a NAS message between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function.

7. The method according to claim 6, wherein the disallowing the NAS message between the first other user equipment network function and the corresponding core network function comprises: delaying handling of a request from the corresponding core network function that corresponds to the first other user equipment network function; rejecting a request from the corresponding core network function that corresponds to the first other user equipment network function;preventing initiation of a NAS procedure with the corresponding core network function that corresponds to the first other user equipment network function; or preventing transmission of a NAS message to the corresponding core network function that corresponds to the first other user equipment network function.

8. The method according to any of claims 1 to 7, further comprising: determining, by a first user equipment network function, that the NAS procedure between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function has been completed; and sending, by the first user equipment network function, to each respective other user equipment network function of the user equipment network functions, an indication indicating that NAS messages are to be allowed between the respective other user equipment network function of the user equipment network functions and the corresponding core network function of the corresponding core network functions that corresponds to the respective user equipment network function.

9. The method according to claim 8, wherein the determining that the NAS procedure between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function has been completed comprises: receiving an acknowledgement indicating the user equipment is registered with the first core network function; receiving a message indicating a handover procedure for the user equipment has ended; or receiving a message indicating completion of the NAS procedure.

10. The method according to claim 8, wherein the determining that the NAS procedure between the first user equipment network function and a first core network function of the corresponding core network functions that corresponds to the first user equipment network function has been completed comprises: determining the first user equipment network function of the user equipment is registered with the first core network function; determining that handover of the user equipment to an entity of an access network has failed; determining the user equipment has been handed over to an entity of an access network; determining that the NAS procedure has been completed successfully; ordetermining that the NAS procedure has failed to complete successfully.

11. The method according to any of claims 8 to 10, wherein the indication indicating that the NAS messages are to be allowed between the respective other user equipment network function and the corresponding core network function that corresponds to the respective other user equipment network function comprises one of: a “NAS xx messages allowed” message, or a “NAS xx messages resume” message, wherein xx indicates the respective other user equipment network function.

12. The method according to any of claims 1 to 11, further comprising: determining, by a first other user equipment network function of the user equipment network functions, based on receipt of an indication indicating that NAS messages are to be allowed between the first other user equipment network function and a corresponding core network function of the corresponding core network functions that corresponds to the first other user equipment network after receipt of an indication indicating that NAS messages are not allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function, that NAS messages are to be allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function.

13. The method according to any of claims 1 to 12, further comprising: transmitting, by a first other user equipment network function of the user equipment network functions, based on receipt of an indication indicating that NAS messages are to be allowed between the first other user equipment network function and a corresponding core network function that corresponds to the first other user equipment network function after receipt of an indication indicating that NAS messages are not allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function or based on the determining, a NAS message to the corresponding core network function that corresponds to the first other user equipment network functions; orresponding, by the first other user equipment network function of the user equipment network functions, based on receipt of the indication indicating that NAS messages are to be allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function after receipt of the indication indicating that NAS messages are not allowed between the first other user equipment network function and the corresponding core network function that corresponds to the first other user equipment network function or based on the determining, to a NAS request from the corresponding core network function that corresponds to the first other user equipment network function.

14. The method according to any of claims 1 to 13, further comprising: determining, by the first user equipment network function of the user equipment network functions, that another NAS procedure has been initiated between the first user equipment network function and the first core network function of the corresponding core network functions; and sending, by the first user equipment network function, based on the determining that the another NAS procedure has been initiated between the first user equipment network function and the first core network function, another indication indicating that NAS messages are not allowed between the first other user equipment network functions and the corresponding core network function that corresponds to the first other user equipment network function.

15. The method according to claim 14, wherein the another indication comprises another “NAS xx messages prohibited” message or another “NAS xx messages suspended” message, wherein xx indicates a respective other user equipment network function of the user equipment network functions.

16. A user equipment comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the user equipment at least to perform the method according to any of claims 1 to 15.

17. A non-transitory computer-readable medium storing instructions which, when executed by at least one processor of a user equipment, cause the user equipment at least to perform the method according to any of claims 1 to 15.

18. A method of a core network entity of a core network of a communication network comprising core network functions configured for non-access stratum (NAS) messaging with corresponding user equipment network functions of a user equipment, the method comprising: determining, by a first core network function of the core network entity, the core network functions comprising the first core network function, that a NAS procedure associated with the user equipment has been initiated between the first core network function and a first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function; and sending, by the first core network function, based on the determining that the NAS procedure associated with the user equipment has been initiated between the first core network function and the first user equipment network function, to each respective other core network function of the core network functions, an indication indicating that NAS messages are not allowed between the respective other core network functions and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the respective other core network function, wherein each other core network function of the core network functions is different from the first core network function.

19. The method according to claim 18, wherein the first user equipment network function comprises a user equipment mobility management function and the first core network function comprises a core network mobility management function.

20. The method according to any of claims 18 to 19, wherein the NAS procedure that has been initiated between the first core network function and the first user equipment network function comprises: a registration procedure for registering the user equipment with the first core network function; a handover procedure associated with the user equipment; or a procedure related to mobility management of the user equipment.

21. The method according to any of claims 18 to 20, wherein the indication indicating that NAS messages are not allowed between the respective other core network functions and the respective corresponding user equipment network function comprises an indication “NAS xx messages prohibited” or an indication “NAS xx messages suspended”, wherein xx indicates a respective other core network function of the core network functions.

22. The method according to any of claims 18 to 21, wherein a first other core network function of the core functions comprises one of the following: a core network function configured for non-access stratum (NAS) messaging associated with session management (SM) of a session for the user equipment, a core network function configured for non-access stratum (NAS) messaging associated with short message services (SMS) for the user equipment, a core network function configured for non-access stratum (NAS) messaging associated with location management (LM) for the user equipment, a core network function for non-access stratum (NAS) messaging associated with policy control for the user equipment, or a core network function for non-access stratum (NAS) messaging associated with a transmission of a policy for the user equipment.

23. The method according to any of claims 18 to 22, further comprising: disallowing, by a first other core network function of the core network functions, based on an indication indicating that NAS messages are not allowed between the first other core network function of the core network functions and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the first other core network function, a NAS message between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function.

24. The method according to claim 23, wherein the disallowing the NAS message between the first other core network function and the corresponding user equipment network function comprises: delaying handling of a request from the corresponding user equipment network function that corresponds to the first other core network function; rejecting a request from the corresponding user equipment network function that corresponds to the first other core network function; preventing initiation of a NAS procedure with the corresponding user equipment network function that corresponds to the first other core network function; orpreventing transmission of a NAS message to the corresponding user equipment network function that corresponds to the first other core network function.

25. The method according to any of claims 18 to 24, further comprising: determining, by the first core network function, that the NAS procedure between the first core network function and the first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function has been completed; and sending, by the first core network function, to each respective other core network function of the core network functions, an indication indicating that NAS messages are to be allowed between the respective other core network function of the core network functions and the corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the respective core network function.

26. The method according to claim 25, wherein the determining that the NAS procedure between the first core network function and the first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function has been completed comprises: determining the user equipment is registered with the first core network function; determining a handover procedure for the user equipment has ended; or receiving a message indicating completion of the NAS procedure.

27. The method according to claim 26, wherein the determining that the NAS procedure between the first core network function and the first user equipment network function of the corresponding user equipment network functions that corresponds to the first core network function has been completed comprises: determining the first user equipment network function of the user equipment is registered with the first core network function; determining that handover of the user equipment to an entity of an access network has failed; determining the user equipment has been handed over to an entity of an access network; determining the determining that the NAS procedure has been completed successfully; or determining the determining that the NAS procedure has failed.

28. The method according to any of claims 25 to 27, wherein the indication indicating that the NAS messages are to be allowed between the respective other core network function and the corresponding user equipment network function that corresponds to the respective other core network function comprises one of: a “NAS xx messages allowed” message, or a “NAS xx messages resume” message, wherein xx indicates the respective other core network function.

29. The method according to any of claims 18 to 28, further comprising: determining, by a first other core network function of the core network functions, based on receipt of an indication indicating that NAS messages are to be allowed between the first other core network function and a corresponding user equipment network function of the corresponding user equipment network functions that corresponds to the first other core network after receipt of an indication indicating that NAS messages are not allowed between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function, that NAS messages are to be allowed between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function.

30. The method according to any of claims 18 to 29, further comprising: transmitting, by a first other core network function of the core network functions, based on receipt of an indication indicating that NAS messages are to be allowed between the first other core network function and a corresponding user equipment network function that corresponds to the first core network function after receipt of an indication indicating that NAS messages are not allowed between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function or based on the determining, a NAS message to a corresponding user equipment network function that corresponds to the first other core network function; or responding, by the first other core network function of the core network functions, based on receipt of the indication indicating that NAS messages are to be allowed between the first other core network function and the corresponding user equipment network function that corresponds to the first other core network function after receipt of the indication indicating that NAS messages are not allowed between the first other core network function and the corresponding user equipment network function that correspondsto the first other core network function or based on the determining, to a NAS request from the corresponding user equipment network function that corresponds to the first other core network function.

31. The method according to any of claims 18 to 30, further comprising: determining, by the first core network function of the core network functions, that another NAS procedure has been initiated between the first core network function and the first user equipment network function of the corresponding user equipment network functions; and sending, by the first core network function, based on the determining that the another NAS procedure has been initiated between the first core network function and the first user equipment network function, another indication indicating that NAS messages are not allowed between the first other core network functions and the corresponding user equipment network function that corresponds to the first other core network function.

32. The method according to claim 31, wherein the another indication comprises another “NAS xx messages prohibited” message or another “NAS xx messages suspended” message, wherein xx indicates a respective other core network function of the core network functions.

33. A core network entity comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the core network entity at least to perform the method according to any of claims 18 to 32.

34. A non-transitory computer-readable medium storing instructions which, when executed by at least one processor of a core network entity, cause the user equipment at least to perform the method according to any of claims 18 to 32.

35. A computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to perform the method according to any of claims 1 to 15 or claims 18 to 32.

Images