Method and apparatus for handling NAS messages in a communication network system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates and satisfying various service requirements. According to an example of the disclosure, a method performed by a terminal in a wireless communication system is provided. The method may include receiving, from a network, NAS message including first information on a type, second information on an IE, and third information on a value; determining whether the first information and the second information are included in configuration files, the configuration files including at least one entry, an entry including the type of the NAS message, the IE corresponding to the type, the value corresponding to the IE, and an action associated with the IE and the value; if so, executing the action and transmitting, to the network apparatus, an acknowledgement message; and if not, transmitting, to the network apparatus, an accept message.

Description

METHOD AND APPARATUS FOR HANDLING NAS MESSAGES IN A COMMUNICATION NETWORK SYSTEM

[0001] The disclosure is related to the field of wireless communication networks. More particularly, the disclosure is related to a method and system for handling non-access stratum (NAS) messages in a communication network system.

[0002]

[0003] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0004] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0005] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0006] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0007] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0008] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0009] In the field of mobile communications, the Non-Access Stratum (NAS) is a critical component that handles signaling and control messages between the User Equipment (UE) and the core network. NAS messages and Information Elements (IEs) play a pivotal role in various network procedures, including registration, authentication, and mobility management. However, the existing mechanisms for handling updates and changes to NAS messages / IEs present several challenges and limitations.

[0010] One issue arises when there are updates or modifications to NAS messages / IEs, or when new NAS messages / IEs are introduced. For instance, if a new IE is added to an existing NAS message, the UE must perform a series of steps to handle this new IE. These steps typically include checking if the new IE is supported by the UE, decoding the IE, performing actions such as Public Land Mobile Network (PLMN) selection, and barring the cell, checking if it is not in the allowable list. If the new IE is not supported by the UE, the UE ignores the IE. Despite the fact that the necessary functions for these actions (such as obtaining the allowable list of cell IDs and barring the cell) are already defined in the UE, an update to the UE is still required to decode the new IE and follow the necessary procedures.

[0011] The current mechanisms have several inherent limitations due to the hard-coded nature of UE actions and behaviors. These limitations include:

[0012] 1. Incompatibility with New Features: Features introduced in new releases that reuse existing UE actions from older features with different permutations and combinations cannot be applied to legacy UEs. This creates a barrier to the seamless integration of new functionalities and improvements.

[0013] 2. Dependency on UE Implementation: Network operators are heavily dependent on the implementation of programmable features within the UE. This dependency limits the operators' ability to manage and control network behaviors effectively.

[0014] 3. Inconsistent UE Behaviors: Operators cannot control different UE behaviors for the same System Information Block (SIB) values. This inconsistency can lead to unpredictable network performance and user experiences.

[0015] Hence, is desirable to address the above mentioned problems and disadvantages or at least provide a useful alternative.

[0016]

[0017] The disclosure is related to a method and system for handling non-access stratum (NAS) messages in a communication network system.

[0018] Accordingly, an aspect of the disclosure is to provide a method and apparatus for handling NAS messages in a communication network system.

[0019] In addition, an aspect of the disclosure is to achieve a flexible architecture of the communication network system.

[0020] Furthermore, an aspect of the disclosure is to enable the UE to perform actions upon receiving NAS messages, notification messages, UE configuration update (UCU) messages, and the like based on pre-configured configuration files stored in the UE.

[0021] The technical problems to be achieved in the various examples of the disclosure are not limited to those mentioned above, and other technical problems not mentioned can be considered by a person having ordinary skill in the art from the various examples of the disclosure described below.

[0022]

[0023] According to an aspect of the disclosure, a method performed by a terminal in a wireless communication system is provided. The method may include receiving, from a network apparatus, a non-access stratum (NAS) message including first information on a type of the NAS message, second information on a information element (IE), and third information on a value; determining whether the first information and the second information are included in configuration files, wherein the configuration files include at least one entry, an entry of the at least one entry including the type of the NAS message, the IE corresponding to the type, the value corresponding to the IE, and an action associated with the IE and the value; in case that the first information and the second information are included in the configuration files, executing the action and transmitting, to the network apparatus, an acknowledgement message indicating that the first information and the second information are included in the configuration files; and in case that the first information and the second information are not included in the configuration files, transmitting, to the network apparatus, an accept message indicating that the first information and the second information are not included in the configuration files.

[0024] According to an aspect of the disclosure, a method performed by a network apparatus in a wireless communication system is provided. The method may include comprising: generating a non-access stratum (NAS) message including first information on a type of the NAS message, second information on a information element (IE), and third information on a value; transmitting, to a terminal, the NAS message; and receiving, from the terminal, an acknowledgement message indicating that the first information and the second information are included in a configuration files or an accept message indicating that the first information and the second information are not included in the configuration files; wherein the configuration files include at least one entry, an entry of the at least one entry including the type of the NAS message, the IE corresponding to the type, the value corresponding to the IE, and an action associated with the IE and the value.

[0025] According to an aspect of the disclosure, a terminal in a wireless communication system is provided. The terminal may include: a transceiver; a processor coupled to the transceiver; and memory coupled to the processor and storing instructions executable by the processor; wherein the instructions cause the terminal to: receive, from a network apparatus, a non-access stratum (NAS) message including first information on a type of the NAS message, second information on a information element (IE), and third information on a value, determine whether the first information and the second information are included in configuration files, wherein the configuration files include at least one entry, an entry of the at least one entry including the type of the NAS message, the IE corresponding to the type, the value corresponding to the IE, and an action associated with the IE and the value, in case that the first information and the second information are included in the configuration files, execute the action and transmit, to the network apparatus, an acknowledgement message indicating that the first information and the second information are included in the configuration files, and in case that the first information and the second information are not included in the configuration files, transmit, to the network apparatus, an accept message indicating that the first information and the second information are not included in the configuration files.

[0026] According to an aspect of the disclosure, a network apparatus in a wireless communication system is provided. The network apparatus may include a transceiver; a processor coupled to the transceiver; and memory coupled to the processor and storing instructions executable by the processor; wherein the instructions cause the network apparatus to: generate a non-access stratum (NAS) message including first information on a type of the NAS message, second information on a information element (IE), and third information on a value, transmit, to a terminal, the NAS message, and receive, from the terminal, an acknowledgement message indicating that the first information and the second information are included in a configuration files or an accept message indicating that the first information and the second information are not included in the configuration files, and wherein the configuration files include at least one entry, an entry of the at least one entry including the type of the NAS message, the IE corresponding to the type, the value corresponding to the IE, and an action associated with the IE and the value.

[0027] In an aspect, the objectives are achieved by providing a method for handling NAS messages in a communication network system. The method includes receiving a NAS message from a network apparatus. The NAS message includes a type of message, an information element (IE) corresponding to the type of message, and a value corresponding to the IE. Further, the method includes determining whether the type of message and the IE corresponding to the type of message provided in the NAS message are present in configuration files that are pre-configured at the UE. The configuration files include the types of messages, IEs corresponding to the types of messages, values corresponding to the IEs, and actions to perform based on the IEs and the values. Further, the method includes implementing the actions in a sequence defined within the configuration files for the IE with the value when the type of message and the IE corresponding to the type of message provided in the NAS message are present in configuration files. Further the method includes executing by the UE the actions as configured in the configuration files when the respective NAS message with the IE and values are received. Further, the method includes transmitting accept message to the network apparatus, when the type of message and the IE corresponding to the type of message provided in the NAS message is not present in the configuration files.

[0028] In an aspect, the objectives are achieved by providing a method for handling NAS messages in a communication network system. Further, the method includes generating a NAS message that includes a type of message, an IE corresponding to the type of message, and a value corresponding to the IE. Further, the method includes transmitting the NAS message to the UE. Further, the method includes receiving an acknowledgment message that indicates that the type of message and the IE corresponding to the type of message provided in the NAS message are present in configuration files that are pre-configured at the UE.

[0029] In another aspect, the objectives are achieved by providing a UE for handling NAS messages in a communication network system. The UE includes a processor, a Memory, and a NAS Handling Controller communicatively coupled to the processor and the Memory. The NAS Handling Controller receives a NAS message from a network apparatus. The NAS message includes a type of message, an IE corresponding to the type of message, and a value corresponding to the IE. Further, the NAS Handling Controller determines whether the type of message and the IE corresponding to the type of message provided in the NAS message are present in configuration files that are pre-configured at the UE. The configuration files include the types of messages, IEs corresponding to the types of messages, values corresponding to the IEs, and actions to performed by the UE based on the IEs and the values. Further, the NAS Handling Controller implements the actions in a sequence defined within the configuration files for the IE with the value when the type of message and the IE corresponding to the type of message provided in the NAS message are present in configuration files and when the respective NAS message is received from the network. Further, the NAS Handling Controller transmits an accept message to the network apparatus (200), when the type of message and the IE corresponding to the type of message provided in the NAS message is not present in the configuration files.

[0030] In another aspect, the objectives are achieved by providing a network apparatus for handling NAS messages in a communication network system. The network apparatus includes a processor, a memory, and a NAS handling controller communicatively coupled to the processor and the memory. The NAS handling controller generates a NAS message that comprises a type of message, an IE corresponding to the type of message, and a value corresponding to the IE. Further, the NAS handling controller transmits the NAS message to the UE. Further, the NAS handling controller receives an acknowledgment message that indicates that the type of message and the IE corresponding to the type of message provided in the NAS message are present in configuration files that are pre-configured at the UE.

[0031] These and other aspects of the examples will be better understood with the following description and accompanying drawings. The descriptions, while indicating preferred examples and specific details, are for illustration and not limitation. Many changes and modifications can be made within the scope of the examples.

[0032] According to the examples of the disclosure, a UE may flexibly handle NAS messages, notification messages, UE configuration update (UCU) messages, and the like based on pre-configured configuration files stored in the UE, without requiring additional signaling.

[0033] In addition, according to the examples of the disclosure, a communication network system may achieve a more flexible architecture by enabling UE-side action control for NAS-related procedures, by reducing signaling overhead and improving system scalability.

[0034] The effects that can be obtained from the disclosure are not limited to the effects mentioned in the various examples, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the disclosure belongs from the description below.

[0035]

[0036] These and other features, aspects, and advantages of the examples are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The examples herein will be better understood from the following description with reference to the drawings, in which:

[0037] Figure 1 is a sequence diagram that illustrates an existing method for handling a new IE / message.

[0038] Figure 2 is a schematic diagram that illustrates a schematic of a UE apparatus implemented to carry out the disclosed subject matter according to an example as disclosed herein.

[0039] Figure 3 is a schematic diagram that illustrates a schematic of a network apparatus implemented to carry out the disclosed subject matter according to an example of the disclosure.

[0040] Figure 4a is a sequence diagram that illustrates the existing method for NAS message communication between an AMF and the UE.

[0041] Figure 4b is a sequence diagram that illustrates the proposed method for NAS message communication between the AMF and the UE according to an example of the disclosure.

[0042] Figure 5a is a sequence diagram that illustrates an existing method for notification message communication between the AMF and the UE.

[0043] Figure 5b is a sequence diagram that illustrates the proposed method for notification message communication between the AMF and the UE according to an example of the disclosure.

[0044] Figure 6a is a sequence diagram that illustrates the existing method for UCU Message (Registered for emergency services) communication between the AMF and the UE.

[0045] Figure 6b is a sequence diagram that illustrates the proposed method for UCU Message (Registered for emergency services) communication between the AMF and the UE according to an example of the disclosure.

[0046] Figure 7 is a schematic diagram that illustrates different actions for the UE to perform when an AI model is triggered according to an example of the disclosure.

[0047] Figure 8 is a sequence diagram that illustrates the proposed flexible configuration architecture according to an example of the disclosure.

[0048] Figure 9 is a sequence diagram that illustrates the proposed method of handling a new IE / Message in the flexible configuration architecture according to an example of the disclosure.

[0049] Figure 10 is a flow diagram that illustrates a method for handling NAS messages in a communication network system by the UE according to an example of the disclosure.

[0050] Figure 11 is a flow diagram that illustrates a method for handling NAS messages in a communication network system by the network apparatus according to an example of the disclosure.

[0051]

[0052] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with a plurality of other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

[0053] As is existing in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions.　These blocks, which referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, and the like, and optionally be driven by firmware and software. The circuits, for example, be embodied in a plurality of semiconductor chips, or on substrate supports such as printed circuit boards, and the like.　The circuits constituting a block be implemented by dedicated hardware, or by a processor (e.g., a plurality of programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method.　Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

[0054] The drawings help explain the technical features, but the embodiments are not limited to them. The proposed method includes any modifications, equivalents, and substitutes beyond those shown. Terms like first, second, etc., are used to distinguish elements and do not limit them.

[0055] Figure 1 is a sequence diagram that illustrates an existing method for handling of a new IE / message. As shown, the sequence diagram includes a UE (100), a network apparatus (200), and a device vendor OAM (300) in communication with each other. At step 1, the network apparatus (200) (for example, 6GC, 5GC, or any core network entity) sends a message M4 / IE4 to the UE (100). Even though the UE (100) has the required function / actions to execute to support message M4 / IE4, it discards the message M4 / IE4 as the UE (100) does not support it. At step 2, when the device vendor OAM (300) sends a new message(M4) / IE(IE4) to the UE (100), an update is needed to support message(M4) / IE(IE4).

[0056] In the proposed solution, the network apparatus (200) sends a NAS message type -M1 with Information element - IE1 and value V1. The UE (100) on receiving any the NAS message from the network apparatus (200) shall perform the following steps: Check if the received message type is present in the configuration file(s); Check if the decoded IE(s) for this message type is present in the configuration file(s); If present then execute the actions in the sequence defined the corresponding Actions in the configuration file(s) for the IE1 with value V1; If the received message type or IE is not present in configuration file(s) then the UE (100) may discard the message or IE OR default actions may be configured in the configuration files to follow in case the IE or message is missing in the file. Optionally, the UE (100) may send an indication / response to the network apparatus (200) that the message M1 with IE1 is not present in the configuration file(s) or / and not supported by the UE (100). Further, optionally, the UE (100) may send the ack / indication / response / Accept / Reject message to the network apparatus (200).

[0057] Figure 2 is a schematic diagram illustrating an example user equipment (UE) (100) configured to implement the disclosed subject matter. The UE (100) may include, for example, consumer electronics (such as mobile phones and smartphones), tablets, wearable devices, computing devices (such as laptops, notebooks, desktops, and workstations), Internet of Things (IoT) devices, automotive systems (including connected vehicles, autonomous vehicles, and vehicle-to-everything (V2X) communication devices), enterprise devices (including robotics), specialised equipment (such as certain medical devices and public safety devices), and media devices (such as gaming consoles and streaming devices). These examples are provided for illustration and are not limiting.

[0058] As shown in Figure 2, the UE (100) includes a processor (102), a memory (104), an input / output (I / O) interface (106), and a NAS handling controller (108) for handling non-access stratum (NAS) messages in a communication network system. The NAS handling controller (108) is operatively coupled to the processor (102) and the memory (104). The components are described below.

[0059] The processor (102) is operatively coupled to the memory (104), the I / O interface (106), and the NAS handling controller (108). The processor (102) is configured to execute instructions stored in the memory (104) to perform one or more operations of the UE (100). In various implementations, the processor (102) includes one or more processing units, such as a central processing unit (CPU), an application processor (AP), a graphics processing unit (GPU), a visual processing unit (VPU), or other processing circuitry available within the UE architecture. The processor (102) may further support power management, parallel processing, and / or hardware acceleration features as provided by the UE platform.

[0060] The memory (104) stores information used for operation of the UE (100), including one or more configuration files stored at the UE (100), one or more NAS messages received from a network apparatus (200), and related data. The memory (104) may include volatile memory and non-volatile memory, and may be implemented using one or more computer-readable storage media, including flash memory, EEPROM, EPROM, and other suitable storage technologies. In an implementations, the memory (104) may include error detection and / or correction features and may support access speeds suitable for processing by the UE (100).

[0061] The I / O interface (106) provides communication between internal components of the UE (100) and one or more external and / or peripheral devices. The I / O interface (106) may include one or more buses, ports, and / or interface circuitry for data transfer. The NAS handling controller (108) is operatively coupled to the I / O interface (106) and the memory (104) to exchange NAS-related data and control information. This arrangement enables the NAS handling controller (108) for handling non-access stratum (NAS) messages in a communication network system to support handling of NAS messages in the communication network system.

[0062] The NAS handling controller (108) for handling non-access stratum (NAS) messages in a communication network system is a hardware-only element implemented as dedicated electronic circuitry within the UE (100). In an implementations, the NAS handling controller (108) is realised as an integrated circuit (IC), an application-specific integrated circuit (ASIC), a system-on-chip (SoC) hardware block, or a field-programmable gate array (FPGA) configuration. The NAS handling controller (108) is not implemented as software executed by the processor (102) and does not rely on execution of program instructions by the processor (102) to perform its NAS message handling functions. The NAS handling controller (108) includes dedicated hardware logic configured to perform NAS message handling operations as described herein, including, for example, one or more finite-state machines (FSMs), combinational / sequential logic, and / or fixed-function processing blocks configured to interpret received NAS messages and apply NAS-related procedures based on stored configuration and received signalling.

[0063] The NAS Handling Controller (108) receives a NAS message from a network apparatus (200), wherein the NAS message comprises a type of message, an IE corresponding to the type of message, and a value corresponding to the IE. The NAS Handling Controller (108) determines whether the type of message and the IE corresponding to the type of message provided in the NAS message are present in configuration files that are pre-configured at the UE (100), wherein the configuration files include the types of messages, IEs corresponding to the types of messages, values corresponding to the IEs, and actions to perform based on the IEs and the values. When the type of message and the IE corresponding to the type of message provided in the NAS message is present in the configuration files, the NAS Handling Controller (108) implements / executes / run the actions in a sequence defined within the configuration files for the IE with the value. Further, the NAS Handling Controller (108) transmits an accept message to the network apparatus (200), when the type of message and the IE corresponding to the type of message provided in the NAS message is not present or present in the configuration files to indicate to the network apparatus (200) whether the message + IE combination is present or not present in the UE (100).

[0064] Figure 3 is a block diagram illustrating an example network apparatus (200) configured to implement the disclosed subject matter. The network apparatus (200) may be implemented as, or form part of, a radio access network (RAN) node and / or a core network node. By way of example, the network apparatus (200) may include a base station (such as a macro cell, small cell, femtocell, or picocell), a gNB / eNB component (including a distributed unit (DU) and / or a centralized unit (CU)), an access and mobility management function (AMF), a user plane function (UPF), or other network entity included in providing connectivity and signalling for user equipment. The network apparatus (200) may further include, or be coupled to, antennas and radio-frequency (RF) units (including MIMO and beamforming circuitry), edge computing nodes (such as MEC servers), backhaul and transport equipment, network management systems, and security elements. These examples are illustrative and do not limit the scope of the network apparatus (200).

[0065] As shown in Figure 3, the network apparatus (200) includes a processor (202), a memory (204), an input / output (I / O) interface (206), and a NAS handling controller (208) for handling non-access stratum (NAS) messages in a communication network system. The NAS handling controller (208) is operatively coupled to the processor (202) and the memory (204). The components are described below.

[0066] The processor (202) is operatively coupled to the memory (204), the I / O interface (206), and the NAS handling controller (208). The processor (202) is configured to execute instructions stored in the memory (204) to perform one or more operations of the network apparatus (200). In various implementations, the processor (202) includes one or more processing units, such as a central processing unit (CPU), an application processor (AP), a general-purpose processing unit, or other processing circuitry available within the network apparatus architecture. The specific processor type may vary based on whether the network apparatus (200) is implemented as a RAN node, a core network node, or a computing platform executing one or more network functions.

[0067] The memory (204) stores information used for operation of the network apparatus (200). In an implementations, the memory (204) stores one or more NAS messages and / or NAS-related information, including a message type, one or more information elements (IEs) associated with the message type, and one or more values corresponding to the IEs, as described herein. The memory (204) may include volatile memory and non-volatile memory, and may be implemented using one or more computer-readable storage media, including flash memory, EEPROM, EPROM, and other suitable storage technologies. In an implementations, the memory (204) may include error detection and / or correction features.

[0068] The I / O interface (206) provides communication between internal components of the network apparatus (200) and one or more external devices and / or network elements. The I / O interface (206) may include one or more buses, ports, fronthaul / backhaul interfaces, and / or interface circuitry for data transfer. The NAS handling controller (208) is operatively coupled to the I / O interface (206) and the memory (204) to exchange NAS-related data and control information. This arrangement enables the NAS handling controller (208) for handling non-access stratum (NAS) messages in a communication network system to support NAS message handling operations in the network apparatus (200).

[0069] The NAS handling controller (208) for handling non-access stratum (NAS) messages in a communication network system is a hardware-only element implemented as dedicated electronic circuitry within the network apparatus (200). In an implementations, the NAS handling controller (208) is realised as an integrated circuit (IC), an application-specific integrated circuit (ASIC), a system-on-chip (SoC) hardware block, or a field-programmable gate array (FPGA) configuration. The NAS handling controller (208) is not implemented as software executed by the processor (202) and does not rely on execution of program instructions by the processor (202) to perform its NAS message handling functions. The NAS handling controller (208) includes dedicated hardware logic configured to perform NAS message handling operations as described herein, including, for example, generating and / or processing NAS messages, determining a NAS message type, associating one or more information elements (IEs) with the message type, and processing corresponding IE values based on stored configuration and received signalling.

[0070] The NAS handling controller (208) generates a NAS message that comprises a type of message, an IE corresponding to the type of message, and a value corresponding to the IE. The NAS handling controller (208) transmits the NAS message to the UE (100). The NAS handling controller (208) receives an acknowledgement message that indicates whether the type of message and the IE corresponding to the type of message provided in the NAS message are present or not present in configuration files that are pre-configured at the UE (100). When the NAS message is received by the UE (100), the UE (100) executes / run the set of actions / rules that are configured in the configuration files for the precise combination of the NAS message with message type and IE(with the sent value).

[0071] Figure 4a is a sequence diagram that illustrates the existing method for NAS message communication between an access and mobility management function (AMF) (400) and the UE (100). The following table 1 illustrates an example of the action library defined in standard, not limited hereto.

[0072] Action LibraryA1Initialize timerA2Move to REGISTERED stateA3Select PLMN

[0073] At step 1, the AMF (400) sends a NAS Message to the UE (100). The UE (100) will then initialize timer and select PLMN which is a fixed behavior of the UE (100). This steps are defined in the standard for the UE (100) to execute when the NAS message is received from the network apparatus (200). At step 2, the UE (100) sends the NAS reply message to the AMF (400).

[0074] Figure 4b is a sequence diagram that illustrates proposed method for NAS message communication between the AMF (400) and the UE (100) according to an example as disclosed herein. The below Table 2 and Table 3 illustrate the UE configuration file, different actions per the UE (100) for same Message / IE.

[0075] Configuration forUE-1M1:XX:VVA1, A3M1:XX:AAA1, A2M1:YY:VVA1, A2, A3

[0076] Configuration forUE-2M1:XX:VVA2, A3M1:XX:AAMove to REGISTERED stateM1:YY:VVSelect PLMN

[0077] In an example, at step 1, the AMF (400) sends a NAS Message to the UE (100). The UE (100) reads the configuration comprising Message Type, Type of IE, TAG, Value and Actions. The actions configured in the configuration file is A1 and A3. The UE (100) then performs A1 and A3. At step 2, the UE (100) sends the NAS reply message to the AMF (400). At the same time when UE-2 receives same message with same IE i.e. M1:XX:VV the actions performed by UE-2 are different i.e. A2 and A3. Thus, the network apparatus (200) is in full control of what the UE (100) should execute based on the action library available for that release.

[0078] In an example, the following advantages are observed: end result can still be same - i.e. the UE (100) will still initialize the timer and select PLMN. But, based on configuration or AI models configured in the UE (100), each UE can behave differently, thus bringing in dynamicity / programmability aspect.

[0079] Figure 5a is a sequence diagram that illustrates an existing method for notification message communication between the AMF (400) and the UE (100). The notification message over non-3GPP access type feature is used to save paging resources of network, instead of paging network will send unicast message to the UE (100) saving precious broadcast resources. However, UE vendors may have less interest to implement such feature because there is no benefit to UEs. Thus, operators are dependent on UE vendors for operator specific requirements.

[0080] At step 1, the AMF (400) sends a Notification Message (Access type: N3GPP) comprising Message Type: 101, IEI: 10 and Value:1 to the UE (100). Further, the UE (100) drops the message because it cannot identify Message Type:101.

[0081] The following Table 4 illustrates the Action Library defined in standard.

[0082] Action LibraryA1Trigger Service request messageA2....A3,,,,

[0083] Figure 5b is a sequence diagram that illustrates the proposed method for notification message communication between the AMF (400) and the UE (100) according to an example as disclosed herein. At step 1, the AMF (400) sends a Notification Message (Access type: N3GPP) comprising Message Type: 101, IEI: 10 and Value:1 to the UE (100). At step 2, the UE (100) then reads the configuration comprising Message Type, Type of IE, TAG, Value, Actions. Then the UE (100) performs A1. At step 3, the UE (100) sends a Service request message to the AMF (400).

[0084] Figure 6a is a sequence diagram that illustrates the existing method for UCU Message (Registered for emergency services) communication between the AMF (400) and the UE (100). In Rel-16 a new feature was introduced when a subscription of the UE (100) is expired at the network apparatus (200), and if there is emergency PDU session ongoing, then the network apparatus (200) will send UCU to indicate to the UE (100) that its registered for emergency services. This feature cannot be used by Rel-15 UEs as it was implemented in Rel-16.

[0085] At step 1, the AMF (400) sends an UCU Message (Registered for emergency services) comprising Message Type: 84, IEI:44, Value:1 to the UE (100) (for example, Rel-15 UE). The UE (100) then ignores the IEI because it cannot identify IEI:44.

[0086] The following Table 5 illustrates the Action to be executed by the UE (100).

[0087] Action LibraryA1Enter emergency registered stateA2Release non-emergency PDUsA3,,,,

[0088] Figure 6b is a sequence diagram that illustrates the proposed method for UCU Message (Registered for emergency services) communication between the AMF (400) and the UE (100) according to an example as disclosed herein.

[0089] In an example, at step 1, the AMF (400) sends an UCU Message (Reg. for emergency, PDU status) comprising Message Type: 84, IEI:44, Value:1 to the UE (100) (for example, Rel-15 UE). At step 2, the UE (100) reads configuration comprising Message Type, Type of IE, TAG, Value, Actions. The UE (100) performs A1 and A2. At step 3, the UE (100) sends a configuration update complete message to the AMF (400).

[0090] In an example, the following advantages are observed: a) There is a zero implementation effort for this feature on the UE (100); b) Rel-15 UEs can use this Rel-16 feature because actions A1(Registered for emergency services) and A2 (for example, using PDU session status IE) are already available in the UE (100) for other reasons / triggers or other procedures.

[0091] Figure 7 is a schematic diagram that illustrates different actions for the UE (100) to perform when an AI model (702) is triggered according to an example as disclosed herein. Though the proposed solution principles are discussed with NAS as an example, it can also be applied between any two entities (for example, any two network functions (or on any layer) ). For example, between RAN node and the UE (100) i.e. at the access stratum layer or for the SIB messages or between two network functions or between Application function and the NF or the UE (100) or like so.

[0092] The AI model (702) consists of the following criteria:

[0093] 1) Dynamic conditions based on learning, history etc.

[0094] 2) Operator specific requirement

[0095] 3) The UE (100) support of the feature

[0096] 4) Depending on the UE (100) or environment of the network apparatus (200); and

[0097] 5) Many more criteria(s) which are up to implementation.

[0098] In an example, as illustrated in Figure 7, the UE (100) can execute a different action because: in each UEs action(s) defined for SIB value: XX is different. The action has to be part of the action library of the respective layer. i.e. the UE (100) has a configuration file for a combination of the broadcast information to the action, i.e. for SIB-X value v1 the UE (100) may be configured to execute actions A1, A2 and A3. When the UE (100) reads the SIB-X with value v1 the UE (100) executes the actions configured in its configuration file. The UE (100) receives broadcast information from a RAN node, with the value designated as SIB-X set to V1. The UE (100) determines the actions to take when the value is designated as SIB-X set to V1, based on the configuration files that are pre-configured in the UE (100). Further, the UE executes the actions that were determined when the value is designated as SIB-X set to V1.

[0099] In an example, to avoid these update for minor changes and ease and faster rollout of new IE(s) or NAS message(s) supports which uses already defined actions in any sequence or order, a new configuration based flexible architecture can be introduced.

[0100] In an example, the UE (100) shall be preconfigured with the below files in flexible configuration based architecture:

[0101] Table 6 illustrates the configuration file(s) containing the mapping between the Message(s), IE(s), Value(s) and the corresponding sequence of Actions it needs to execute.

[0102] MessageTagValueActionsM1IE1V1[A1,A2,A3]M1IE1V2[A4,A6,A9]M1IE2V4[A2,A4,A5]M2IE3V5[A0,A6,A7]

[0103] Table 7 illustrates the Action file(s) which contains all the required action(s) for functionality of the UE (100).

[0104] Action NameFunction definitionA0Delete 5G-GUTIA1Perform PLMN selectionA2Bar the current cellA3Perform service request procedureA4Enter 5GMM_DEREGISTERED state.............

[0105] Figure 8 is a sequence diagram that illustrates the proposed flexible configuration architecture according to an example as disclosed herein. As shown in the sequence diagram, the UE (100) and the network apparatus (200) are in communication with each other. Each step is explained in further detail below.

[0106] In an example, at step 1, the network apparatus (200) sends a NAS message M1 with IE1 and value V1. At step 2, the UE (100) on receiving any the NAS message from the network apparatus (200) shall follow below steps:

[0107] a) Check if the received message type is present in the configuration file(s).

[0108] b) Check if the decoded IE(s) for this message type is present in the configuration file(s).

[0109] c) If present then execute the actions in the sequence defined the corresponding Actions in the configuration file(s) for the IE1 with value V1.

[0110] d) If the received message type or IE is not present in configuration file(s) then the UE (100) may discard the message or IE OR default actions may be configured in the configuration files to follow in case the IE or message is missing in the file. Optionally, the UE (100) may send an indication / response to the network apparatus (200) that the message M1 with IE1 is not present in the configuration file(s) or / and not supported by the UE (100).

[0111] At step 3, optionally, the UE (100) may send the ack / indication / response / Accept / Reject message to the network apparatus (200).

[0112] In an example, whenever there are any changes in the message(s) / IE(s) or if any new NAS message(s) / IE(s) is introduced which uses the Action(s) already defined in the UE (100) (i.e. already present in the Action file(s)), then the network apparatus (200) may send the updated configuration to the UE (100) in any NAS message or by any other mechanism.

[0113] For example, a new IE (e.g. IE4) gets added in any NAS message which needs the UE (100) to follow below steps:

[0114] 1) Check if new IE is supported by the UE (100) or not.

[0115] 2) If supported, then follow below steps:

[0116] a) Decode the IE

[0117] b) Perform PLMN selection (A1).

[0118] c) Bar the cell if not in allowable list (A2).

[0119] 3) If not supported, then bar the cell(A2).

[0120] Table 8 illustrates the Pre-configured Action file(s) present in the UE (100) has all the required action(s) to support the new IE (IE4).

[0121] Action NameFunction definitionA0Delete 5G-GUTIA1Perform PLMN selectionA2Bar the current cellA3Perform service request procedureA4Enter 5GMM_DEREGISTERED state.............

[0122] Figure 9 is a sequence diagram that illustrates the proposed method of handling of new IE / Message in the flexible configuration architecture according to an example as disclosed herein. As shown in the sequence diagram, the UE (100) and the network apparatus (200) are in communication with each other. Each step is explained in further detail.

[0123] In an example, as the UE (100) has all the required actions (A1 and A2) the network apparatus (200) may send an updated configuration file with support for this new IE as below:

[0124] 1) The network apparatus (200) sends the new configuration file with support for new IE(IE4) in any NAS message.

[0125] For example, New configuration file with support for new IE(IE4) in any NAS message is shown as Table 9, not limited hereto.

[0126] MessageTagValueActionsM4IE4V8[A1,A2]

[0127] 2) The UE (100) shall update the configuration file with the new IE(IE4).

[0128] For example, the updated configuration is shown as Table 10, not limited hereto.

[0129] MessageTagValueActionsM1IE1V1[A1,A2,A3]M1IE1V2[A4, A6, A9]M1IE2V4[A2,A4,A5]M2IE3V5[A0,A6,A7]M4IE4V8[A1,A2]

[0130] 3) Optionally, the UE (100) may send the ack / indication / response message to the network apparatus (200)

[0131] In an example, the benefits for users are early access to new features. The benefits for OAM / Vendor are faster development of new features, easy code maintenance and cost saving in code base development and maintenance. The benefits for Network operators are: remove dependency on the OAM Vendors for rollout of features which are using existing functions or procedures, faster rollout of new features and cost saving in beta testing as new features can be easily tested with a configuration file(s) update.

[0132] In an example, the configuration file is assumed to be pre-configured in the UE (100), but it can be dynamically configured in the UE (100) using any of the NAS or AS message or any type of message piggybacking the configuration file and providing to the UE (100). This can utilize the control plane path or the user plane path or OTA update or any other mechanism network can use to configure the configuration into the file.

[0133] The message type, Information element (IE) and value (acting like input) this terms are used to create a pair to the actions. i.e. the UE (100) will identity what actions it has to execute when particular input is received in the message. In general, the message has an information "X" (input) and there is pairing defined in the UE (100) when information "X" is received what actions UE has to execute like A1, A2, A3 etc. The actions can be at least one of the actions performed as defined in TS 24.501 or TS 24.301 i.e. cell selection, cell reselection, PLMN selection, start a timer, bar a cell, back-off to send NAS signalling, back-off to send one or more or any combination of the NAS procedure, trigger a NAS procedure, not trigger a NAS procedures for a period of time, back-off to send an information element in one or more of the NAS messages, enter a particular state(REGISTERED, DEREGISTERED, REGISTERED INITIATED, PLMN SEARCH) or a substate PLMN SEARCH, NO CELL AVAILABLE, ATTEMPTING TO UPDATE etc. Each step which the UE (100) can execute as per the TS 24.301 or TS 24.501 is defined as an action in this example.

[0134] The actions in the UE (100) are executed when an input or information (e.g. message type, Information element(IE) and value) is received as part of the message from the network apparatus (200) is described only for illustration purpose. The UE (100) can execute the configured actions for different other triggers too, for e.g. when a particular timer expires or the UE (100) enters an area (TAI or cell or geographical area or CAG cell) etc or when the SIB values or broadcast information has changed etc and not limited to the one mentioned here. In general, the actions in the UE (100) can be executed based on the information(i.e. input information) received from the network apparatus (200) or internal triggers within the UE (100).

[0135] In an example, the following are the advantages of the proposed solution:

[0136] 1) Not all UEs implement the features required by operator. If it's under the control of operator (in best effort basis) its desirable.

[0137] 2) Static behaviour is not desirable for any kind of automation / intelligent system. First step towards intelligence based system is dynamic behaviour realization.

[0138] 3) On the fly required features by operator can be realized without changing the code (or contacting the UE vendors).

[0139] 4) Per UE specific behaviour can be defined for same broadcasted value or the IE (code point) NAS or AS message given to the UE (100).

[0140] 5) Over the period of time say in few years there will be very few newer actions we can think off. Thus, new features can be deployed in the field without / very less need for any UE code changes or network code changes - can be managed by intelligent configurations

[0141] 6) Time to market can be reduced drastically because actions library is already available and it's a matter of only configuring the destination node with intelligence.

[0142] Figure 10 is a flow diagram that illustrates a method for handling NAS messages in a communication network system by the UE (100) according to an example as disclosed herein. The method includes steps (1002-1008). Each step is explained in further detail below.

[0143] At step (1002), the method includes receiving by the UE (100) a NAS message from the network apparatus (200). The NAS message includes a type of message, an information element (IE) corresponding to the type of message, and a value corresponding to the IE.

[0144] At step (1004), the method includes determining by the UE (100) whether the type of message and the IE corresponding to the type of message provided in the NAS message are present in configuration files. The configuration files are pre-configured at the UE (100). The configuration files include the types of messages, IEs corresponding to the types of messages, values corresponding to the IEs, and actions to perform based on the IEs and the values.

[0145] If step (1004) is yes, then at step (1006), the method includes implementing by the UE (100) the actions in a sequence defined within the configuration files for the IE with the value. This occurs when the type of message and the IE corresponding to the type of message provided in the NAS message is present in configuration files. For instance, the actions include, but not limited to actions comprise at least one of deleting a globally unique temporary identifier (GUTI), performing a public land mobile network (PLMN) selection procedure, barring a current cell, performing at least one of the NAS procedure, entering a NAS state or the NAS sub-state, starting a NAS timer, stopping the NAS timer, and the like.

[0146] If step (1004) is no, then at step (1008), the method includes transmitting by the UE (100) an accept message to the network apparatus (200). The response message or accept message is transmitted when the type of message and the IE corresponding to the type of message provided in the NAS message is not present in the configuration files. Apart for this, the UE (100) can also perform at least one of::

[0147] 1) Discarding the NAS message received from the network apparatus (200), when the type of message and the IE corresponding to the type of message provided in the NAS message is not present in the configuration files

[0148] 3) Configuring one or more default actions in the configuration files to follow

[0149] The UE (100) transmits an acknowledgement message to the network apparatus (200) that indicates whether the type of message and the IE corresponding to the type of message provided in the NAS message, when present in the configuration files.

[0150] Figure 11 is a flow diagram that illustrates a method for handling NAS messages in a communication network system by the network apparatus (200) according to an example as disclosed herein. The method includes steps (1102-1106). Each step is explained in further detail below.

[0151] At step (1102), the method includes generating by the network apparatus (200) a NAS message. The NAS message includes a type of message, an IE corresponding to the type of message, and a value corresponding to the IE. The generation process includes selecting the appropriate message type and IE based on the current network conditions and the operational requirements of the UE (100). The network apparatus (200) utilizes its NAS protocol stack to construct the message, ensuring that all necessary information elements are included and correctly formatted.

[0152] At step (1104), the method includes transmitting by the network apparatus (200) the NAS message to the UE (100). The transmission is carried out over a secure communication channel, ensuring that the NAS message is delivered reliably and without any unauthorized access. The network apparatus (200) may employ various transmission techniques, such as encryption and error correction, to enhance the security and integrity of the NAS message during transit.

[0153] At step (1106), the method includes receiving by the network apparatus (200) an acknowledgement message that indicates whether the type of message and the IE corresponding to the type of message provided in the NAS message. This information is present in configuration files that are pre-configured at the UE (100). The acknowledgement message serves as a confirmation that the UE (100) has successfully processed the NAS message and performed the necessary actions as defined in its configuration files. The network apparatus (200) may log the receipt of the acknowledgement message for record-keeping and further analysis, ensuring that the communication process is fully documented.

[0154] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a terminal in a wireless communication system, the method comprising:receiving, from a network apparatus, a non-access stratum (NAS) message including first information on a type of the NAS message, second information on a information element (IE), and third information on a value;determining whether the first information and the second information are included in configuration files, wherein the configuration files include at least one entry, an entry of the at least one entry including the type of the NAS message, the IE corresponding to the type, the value corresponding to the IE, and an action associated with the IE and the value;in case that the first information and the second information are included in the configuration files, executing the action and transmitting, to the network apparatus, an acknowledgement message indicating that the first information and the second information are included in the configuration files; andin case that the first information and the second information are not included in the configuration files, transmitting, to the network apparatus, an accept message indicating that the first information and the second information are not included in the configuration files.2.The method of claim 1, further comprising:in case that the first information and the second information are not included in the configuration files, discarding the NAS message and executing at least one default action based on the configuration files.3.The method of claim 1, further comprising:receiving, from the network apparatus, a configuration file including a first type of message, a first IE corresponding to the first type, a first value corresponding to the first IE, and a first action associated with the first IE and first the value;updating the configuration files with the configuration file; andtransmitting, to the network apparatus, an indication message indicating that the configuration file is updated with the configuration files.4.The method of claim 1, further comprising:receiving, from a base station associated with the network apparatus, a system information block (SIB) corresponding to a second IE with a second value; andidentifying whether the second IE and the second value are included in the configuration files;in case that the second IE and the second value are included in the configuration files, performing the action based on the second IE and the second value.5.The method of claim 1,wherein the action includes at least one of:deleting a globally unique temporary identifier (GUTI),performing a public land mobile network (PLMN) selection procedure;barring a current cell;performing at least one of the NAS procedure;entering a NAS state or the NAS sub-state;starting a NAS timer; andstopping the NAS timer.6.A method performed by a network apparatus in a wireless communication system, the method comprising:generating a non-access stratum (NAS) message including first information on a type of the NAS message, second information on a information element (IE), and third information on a value;transmitting, to a terminal, the NAS message; andreceiving, from the terminal, an acknowledgement message indicating that the first information and the second information are included in a configuration files or an accept message indicating that the first information and the second information are not included in the configuration files;wherein the configuration files include at least one entry, an entry of the at least one entry including the type of the NAS message, the IE corresponding to the type, the value corresponding to the IE, and an action associated with the IE and the value.7.The method of claim 5, further comprising:transmitting, to the terminal, a configuration file including a first type of message, a first IE corresponding to the first type, a first value corresponding to the first IE, and a first action associated with the first IE and the first value; andreceiving, from the terminal, an indication message indicating that the configuration file is updated with the configuration files.8.The method of claim 5,wherein the action includes at least one of:deleting a globally unique temporary identifier (GUTI),performing a public land mobile network (PLMN) selection procedure;barring a current cell;performing at least one of the NAS procedure;entering a NAS state or the NAS sub-state;starting a NAS timer; andstopping the NAS timer.9.A terminal in a wireless communication system, the terminal comprising:a transceiver;a processor coupled to the transceiver; andmemory coupled to the processor and storing instructions executable by the processor;wherein the instructions cause the terminal to:receive, from a network apparatus, a non-access stratum (NAS) message including first information on a type of the NAS message, second information on a information element (IE), and third information on a value,determine whether the first information and the second information are included in configuration files, wherein the configuration files include at least one entry, an entry of the at least one entry including the type of the NAS message, the IE corresponding to the type, the value corresponding to the IE, and an action associated with the IE and the value,in case that the first information and the second information are included in the configuration files, execute the action and transmit, to the network apparatus, an acknowledgement message indicating that the first information and the second information are included in the configuration files, andin case that the first information and the second information are not included in the configuration files, transmit, to the network apparatus, an accept message indicating that the first information and the second information are not included in the configuration files.10.The terminal of claim 9,wherein the instructions further cause the terminal to, in case that the first information and the second information are not included in the configuration files, discard the NAS message and execute at least one default action based on the configuration files.11.The terminal of claim 9,wherein the instructions further cause the terminal to:receive, from the network apparatus, a configuration file including a first type of message, a first IE corresponding to the first type, a first value corresponding to the first IE, and a first action associated with the first IE and first the value,update the configuration files with the configuration file, andtransmit, to the network apparatus, an indication message indicating that the configuration file is updated with the configuration files.12.The terminal of claim 9,wherein the instructions further cause the terminal to:receive, from a base station associated with the network apparatus, a system information block (SIB) corresponding to a second IE with a second value; andidentify whether the second IE and the second value are included in the configuration files;in case that the second IE and the second value are included in the configuration files, perform the action based on the second IE and the second value, andwherein the action includes at least one of:deleting a globally unique temporary identifier (GUTI),performing a public land mobile network (PLMN) selection procedure;barring a current cell;performing at least one of the NAS procedure;entering a NAS state or the NAS sub-state;starting a NAS timer; andstopping the NAS timer.13.A network apparatus in a wireless communication system, the network apparatus comprising:a transceiver;a processor coupled to the transceiver; andmemory coupled to the processor and storing instructions executable by the processor;wherein the instructions cause the network apparatus to:generate a non-access stratum (NAS) message including first information on a type of the NAS message, second information on a information element (IE), and third information on a value,transmit, to a terminal, the NAS message, andreceive, from the terminal, an acknowledgement message indicating that the first information and the second information are included in a configuration files or an accept message indicating that the first information and the second information are not included in the configuration files, andwherein the configuration files include at least one entry, an entry of the at least one entry including the type of the NAS message, the IE corresponding to the type, the value corresponding to the IE, and an action associated with the IE and the value.14.The network apparatus of claim 13,wherein the instructions further cause the network apparatus to:transmit, to the terminal, a configuration file including a first type of message, a first IE corresponding to the first type, a first value corresponding to the first IE, and a first action associated with the first IE and the first value, andreceive, from the terminal, an indication message indicating that the configuration file is updated with the configuration files.15.The network apparatus of claim 13,wherein the action includes at least one of:deleting a globally unique temporary identifier (GUTI),performing a public land mobile network (PLMN) selection procedure;barring a current cell;performing at least one of the NAS procedure;entering a NAS state or the NAS sub-state;starting a NAS timer; andstopping the NAS timer.

Images