Method and UE for enhancing NAS signaling in radio capability signaling optimization

Abstract

Methods and UEs for enhancing NAS signaling in the RACS of a wireless network are disclosed. The NAS signaling between the UE and the server is enhanced by performing one of the following steps: sending a registration complete message to the server using existing NAS signaling and enabling a release timer without responding to the deletion of the IE of RC_ID in the received registration acceptance message; and sending a registration complete message to the server without responding to the deletion of the IE of RC_ID in the received registration acceptance message. Resume the registration process based on the stored RC_ID.

Description

[0001] Cross - reference to related applications

[0002] This application claims priority to Indian Provisional Patent Application No. 202041034334, filed on August 10, 2020, with the Indian Intellectual Property Office, the disclosure of which is hereby incorporated by reference in its entirety. Technical field

[0003] The present disclosure relates to a NAS (Non - Access Stratum) signaling, and more particularly, to a method and a UE for enhancing NAS signaling in UERACS (User Equipment Radio - Ability Signaling Optimization) of a wireless network. Background art

[0004] In the current 3GPP specifications (Third Generation Partnership Project specifications), based on the maximum size in ASN.1 (Abstract Syntax Notation One), the estimated theoretical maximum size of the UE radio - ability for NR (New Radio) or EN - DC (E - UTRAN New Radio - Dual Connectivity) is about 10000 kilobytes. However, based on the experience and analysis of LTE (Long Term Evolution) and NR, considering ~1024 band combinations and up to 4 bands per band combination during the registration process, the estimated actual size of RF (Radio Frequency) parameters (e.g., UE radio - ability) is about 11 to 12 kilobytes.

[0005] FIG. 1A is an example scenario showing the registration process of a UE without using UE RACS in a wireless network (e.g., server, LTE, NR, EN - DC, etc.). The wireless network includes multiple Tracking Area Identifiers (TAIs). At S1a, the UE in TAI - 1 sends a registration request to the wireless network. At S2a, the UE in TAI - 1 receives a capability request from the wireless network. At S3a, in response to receiving the capability request, the UE sends capability information about TAI - 1 (e.g., LTE) to the wireless network. At S4a, as part of the registration process, the UE receives a registration response from the wireless network. Now, consider the scenario where the UE moves to a new location / area such as TAI - 2. In this scenario, the UE has to perform a registration - request process with mobility update and repeat the signaling process (S5a - S8a) on TAI - 2, which results in an increase in signaling overhead in the wireless network. Therefore, RACS has been introduced to optimize the transmission of UE radio - ability.

[0006] RACS is a feature designed to optimize the transmission of the ever-increasing UE radio capabilities related to the radio interface associated with the AS (Access Stratum) signaling messages exchanged with the wireless network. The AS is a functional layer in some (e.g., LTE) radio access protocols between the UE and the wireless network. RACS works by allocating an identifier (i.e., Radio Capability ID / RC_ID) to represent the set of UE radio capabilities. The RC_ID is used as a substitute for the AS capability signaling message. The value of the RC_ID can be assigned by the manufacturer or the wireless network. The RC_ID assigned by the manufacturer is pre-configured or sent by the manufacturer via Open Mobile Alliance (OMA) Device Management (DM), is applicable only to the current UE radio configuration, and can be used in all PLMNs (Public Land Mobile Networks).

[0007] Figure 1B is an example scenario showing the registration process of a UE using UE RACS in a wireless network according to the prior art. At S1b, the UE in TAI-1 sends a registration request to the wireless network. At S2b, the UE in TAI-1 receives a capability request from the wireless network. At S3b, in response to receiving the capability request, the UE sends the capability information about TAI-1 to the wireless network. At S4b, in response to sending the capability information, the UE receives RC_ID-1 (in the registration response) from the wireless network in TAI-1. The RC_ID-1 is applicable only to the serving PLMN / Standalone Non-Public Network (SNPN) and the current radio capability configuration of the UE when the RC_ID is assigned. At S5b - S6b, consider the scenario where the UE moves to a new location / area such as TAI-2. In this scenario, the UE does not perform UE capability signaling in TAI-2 because the UE has an applicable RC_ID-1 (to be used for subsequent registration requests) for the current PLMN / SNPN and radio capability combination. In TAI-2, RC_ID-1 will be used instead of the RRC UE radio capability transfer process to indicate the UE radio access capability information from the UE to the wireless network, which results in a reduction in signaling overhead in the wireless network.

[0008] According to 3GPP TS 23.501, TS 24.501, and TS 24.301, the traditional RACS feature / process is inefficient due to inappropriate signaling conditions. For example,

[0009] a. Start timer T3540 according to the conditions defined in section 5.3.1.3 of 3GPP 24.501 V16.5.1 for releasing the NAS signaling connection after receiving a registration acceptance message with a UE radio capability deletion indication information element (IE) from the wireless network, which results in an additional 10-second delay in the registration process after deleting the UE RC_ID and unnecessary overhead on the UE waiting for the established RRC connection to be interrupted or released.

[0010] b. After receiving a registration acceptance message with a UE radio capability deletion indication IE from the wireless network, send a registration completion message to the wireless network as an acknowledgement, which results in signaling overhead in both the UE and the wireless network.

[0011] c. After receiving a new UE RC_ID in the registration acceptance message, it is not clear whether the UE can continue to use the newly received ID in case of a transmission failure of the registration completion message.

[0012] d. After receiving a UE RC_ID in the registration acceptance message for the current PLMN, even when the new PLMN or TAC (Tracking Area Code) belongs to the same Access and Mobility Management Function (AMF) / Mobility Management Entity (MME), the UE and the wireless network will re - negotiate the radio capability identifier after moving to the new PLMN or TAC.

[0013] Regarding FIGS. 2A to 2D, a detailed explanation of the inappropriate signaling conditions associated with traditional RACS features / processes is provided. Traditional RACS features / processes result in NAS signaling overhead, latency in NAS signaling, and waste of radio resources in NAS signaling. In some scenarios of NAS signaling, there is scope to improve the efficiency of the RACS process / management and negotiation between the UE and the wireless network. Therefore, it is desirable to provide at least a useful alternative for the RACS process / management and NAS signaling. Summary of the Invention

[0014] Embodiments herein provide a method for enhancing NAS signaling in UE RACS in a wireless network. The method includes the UE receiving an RC_ID_IE (Radio Capability Identification Information Element) from a server of the wireless network to optimize the UE's transmission. Further, the method includes the UE sending a registration request message to the server to establish NAS signaling between the UE and the server. Further, the method includes the UE establishing NAS signaling between the UE and the server. Further, the method includes the UE enhancing the NAS signaling between the UE and the server by performing one of the following steps: (a) receiving a registration acceptance message with an RC_ID deletion IE from the server, sending a registration completion message to the server using existing NAS signaling, and not enabling a release timer in response to receiving the RC_ID deletion IE in the registration acceptance message; and (b) receiving a registration acceptance message with an RC_ID deletion IE from the server and not sending a registration completion message to the server in response to receiving the RC_ID deletion IE in the registration acceptance message.

[0015] The embodiments described herein provide a UE for enhancing NAS signaling in a UE RACS in a wireless network. The UE includes a NAS signaling controller operably connected to a processor and a memory. The NAS signaling controller is configured to receive an RC_ID_IE with an RC_ID from a server of the wireless network to optimize transmissions of the UE. Further, the NAS signaling controller is configured to send a registration request message to the server to establish NAS signaling between the UE and the server. Further, the NAS signaling controller is configured to establish NAS signaling between the UE and the server. Further, the NAS signaling controller is configured to enhance the NAS signaling between the UE and the server by performing one of the following: (a) receive a registration acceptance message with an RC_ID deletion IE from the server, send a registration complete message to the server using existing NAS signaling, and not enable a release timer in response to receiving the RC_ID deletion IE in the registration acceptance message; and (b) receive a registration acceptance message with an RC_ID deletion IE from the server and send a registration complete message to the server without responding to the RC_ID deletion IE received in the registration acceptance message.

[0016] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. However, it is to be understood that the following description, although indicating embodiments and many of its specific details, is given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein, and the embodiments herein include all such modifications. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Embodiments of the present disclosure are illustrated in the accompanying drawings, in which like reference numerals refer to corresponding parts throughout the several views. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0018] FIG. 1A is an example scenario showing a registration process of a UE without using UE RACS in a wireless network according to the prior art;

[0019] FIG. 1B is an example scenario showing a registration process of a UE using UE RACS in a wireless network according to the prior art;

[0020] FIGS. 2A, 2B, 2C, and 2D are sequence diagrams showing various signaling for establishing NAS signaling between a UE and a server using conventional RACS features / processes according to the prior art;

[0021] Figure 3 A block diagram of a UE for enhancing NAS signaling in a UE RACS in a wireless network according to an embodiment disclosed herein is shown;

[0022] Figure 4 is a flowchart showing a method for enhancing NAS signaling in UE RACS in a wireless network according to an embodiment disclosed herein; and

[0023] Figure 5 , Figure 6 , Figure 7 and Figure 8 are sequence diagrams showing various signaling for enhancing NAS signaling between a UE and a server in a wireless network according to an embodiment disclosed herein. DETAILED DESCRIPTION

[0024] Embodiments herein are more fully explained with reference to the non - limiting embodiments shown in the drawings and detailed in the following description. Descriptions of well - known components and processing techniques are omitted so as not to unnecessarily obscure the embodiments herein. Moreover, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise stated, the term "or" as used herein refers to a non - exclusive or. The examples used herein are only intended to assist in understanding the manner in which the embodiments herein can be practiced and further enable those skilled in the art to practice the embodiments herein. Therefore, these examples should not be construed as limiting the scope of the embodiments herein.

[0025] As is traditional in the art, embodiments can be described and illustrated in terms of blocks that perform the one or more functions. These blocks may be referred to herein as managers, units, modules, hardware components, etc., which 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, hard - wired circuits, etc.) and may optionally be driven by firmware. For example, these circuits may be included in one or more semiconductor chips or on a substrate support such as a printed circuit board. The circuits constituting the blocks can be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware performing some functions of the block and a processor performing other functions of the block. Without departing from the scope of the present disclosure, each block of an embodiment can be physically divided into two or more interacting and discrete blocks. Similarly, without departing from the scope of the present disclosure, the blocks of an embodiment can be physically combined into more complex blocks.

[0026] The accompanying drawings are used to assist in easily understanding various technical features, and the embodiments presented herein are not limited by the accompanying drawings. Thus, the present disclosure should be construed as extending to any variations, equivalents, and alternatives other than those specifically set forth in the accompanying drawings. Although terms such as first and second may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another element.

[0027] Accordingly, embodiments herein provide a method for enhancing NAS signaling in UE RACS in a wireless network. The method includes the UE receiving an RC_ID in an RC_ID_IE from a server of the wireless network to optimize the transmission of the UE. Further, the method includes the UE sending a registration request message to the server to establish NAS signaling between the UE and the server. Further, the method includes the UE establishing NAS signaling between the UE and the server. Further, the method includes the UE enhancing the NAS signaling between the UE and the server by performing one of the following steps: (a) receiving a registration acceptance message with an RC_ID deletion IE from the server, sending a registration complete message to the server using existing NAS signaling, and not enabling a release timer in response to receiving the RC_ID deletion IE in the registration acceptance message; and (b) receiving a registration acceptance message with an RC_ID deletion IE from the server, and sending a registration complete message to the server without responding to the received RC_ID deletion IE in the registration acceptance message.

[0028] Accordingly, embodiments herein provide a UE for enhancing NAS signaling in UE RACS in a wireless network. The UE includes a NAS signaling controller coupled to a processor and a memory. The NAS signaling controller is configured to receive an RC_ID_IE from a server of the wireless network to optimize the transmission of the UE. Further, the NAS signaling controller is configured to send a registration request message to the server to establish NAS signaling between the UE and the server. Further, the NAS signaling controller is configured to establish NAS signaling between the UE and the server. Further, the NAS signaling controller is configured to enhance the NAS signaling between the UE and the server by performing one of the following operations: (a) receiving a registration acceptance message with an RC_ID deletion IE from the server, sending a registration complete message to the server using existing NAS signaling, and not enabling a release timer in response to receiving the RC_ID deletion IE in the registration acceptance message; and (b) receiving a registration acceptance message with an RC_ID deletion IE from the server, and sending a registration complete message to the server without responding to the received RC_ID deletion IE in the registration acceptance message.

[0029] Unlike existing methods and systems, the method described herein may allow a UE to retain a NAS signaling connection after deleting the UE RC_ID stored in the UE for the current PLMN, where the UE RC_ID is deleted based on receiving a registration acceptance message from the radio network. Further, a timer T3540 shall be enabled in the UE in response to receiving a deleted registration acceptance message with the UE RC_ID. Accordingly, the UE may immediately initiate a registration procedure using the existing NAS signaling connection. This may help reduce the latency to complete the registration procedure and save radio resources associated with the UE and the radio network.

[0030] Unlike existing methods and systems, the method described herein may allow a UE to remove the redundant requirement of sending a registration complete message as an acknowledgement to the radio network after receiving a registration acceptance message that causes the deletion of the UE RC_ID from the radio network. This may help reduce the signaling overhead in both the UE and the radio network.

[0031] Unlike existing methods and systems, the method described herein may allow a UE to consider that the UE RC_ID received in the registration acceptance message is valid for the current PLMN and reusable when the registration procedure is restarted due to a TAI change or a lower layer failure. This may help reduce the signaling exchange between the UE and the radio network when the UE attempts to restart the registration procedure using the UE radio capability IE included in the registration request message.

[0032] Unlike existing methods and systems, when the newly resident TAC is not in the UE's TAI list, the method described herein may allow the UE to use the same RC_ID received in the registration acceptance message. If the AMF / MME is the same, a new UE RC_ID will not be allocated. If the AMF / MME changes, the existing procedure for new UE RC_ID allocation will be followed. This may help reduce the signaling exchanged between the UE and the radio network in a mobility scenario.

[0033] Throughout this disclosure, the terms "registration request" and "registration request message" may be used interchangeably and may be understood to have the same meaning. Throughout this disclosure, the terms "registration acceptance" and "registration acceptance message" may be used interchangeably and may be understood to have the same meaning. Throughout this disclosure, the terms "registration complete" and "registration complete message" may be used interchangeably and may be understood to have the same meaning. Throughout this disclosure, the terms "radio network", "network", and "N / W" may be used interchangeably and may be understood to have the same meaning. Throughout this disclosure, the terms "UE RC_ID_IE" and "RC_ID_IE" may be used interchangeably and may be understood to have the same meaning.

[0034] Figures 2A, 2B, 2C, and 2D are sequence diagrams showing various signaling for establishing NAS signaling between a UE (10) (e.g., a UE, a network node, an IAB node, etc.) and a server (20) (e.g., a server, a core network, a cloud network, a wireless network, a 5GC NW (20b), an NR RRC (20a), etc.) using traditional RACS features / processes according to the prior art.

[0035] Referring to Figure 2A: At S201a, the UE (10) performs an initial operation (e.g., power-on, layer initialization, SIM reading) to establish a connection with the server (20). At S202a to S203a, the UE (10) determines that there is no valid RC_ID_IE stored in the memory of the UE (10). The UE (10) encodes the registration request message without using the RC_ID_IE. At S204a to S205a, the UE (10) sends a registration request to the server (20) to establish NAS signaling between the UE (10) and the server (20), where the registration request message does not include the RC_ID_IE. At S206a to S209a, the server (20) obtains the current RC information and assigns a new RC_ID to the current UE radio configuration. At S210a, the server (20) sends a UERC_ID_IE to the UE (10) in the registration acceptance. At S211a, the UE (10) sends a registration complete to the server (20) in response to receiving the registration acceptance. At S212a to S213a, the UE (10) stores the UE RC_ID_IE for the current PLMN and the current UE radio capability configuration and releases the connection.

[0036] At S214a to S215a, the UE (10) performs the initial operation again to establish a connection with the server (20). At S216a, the UE (10) determines that a valid RC_ID (S212a) is stored in the memory of the UE (10). At S217a, the UE (10) sends the UE RC_ID_IE with the RC_ID to the server (20) in the registration request. At S218a, the UE (10) establishes NAS signaling with the server (20). At S219a, the server (20) sends a UE RC_ID deletion IE to the UE (10) in the registration acceptance.

[0037] In S220a, the UE (10) enables a timer (e.g., T3540) in the UE (10) based on receiving a UE RC_ID deletion IE from the server (20). In S221a to S226a, the UE (10) sends registration complete to the server (20), deletes all valid RC_IDs stored (S212a) in the memory of the UE (10), and initiates a registration procedure. Based on receiving a registration acceptance message, the UE (10) enables a timer for local release of the NAS signaling connection, and this prevents the UE (10) from sending any signaling messages. Thus, only after the timer (224a) expires, the registration procedure triggered due to the UE RC_ID deletion IE can be sent to the server (20) after performing a release procedure and a new signaling connection.

[0038] In S227a, the UE (10) encodes a registration request message without using the RC_ID_IE. In S228a, the UE (10) sends a registration request to the server for mobility registration update, where the registration request message does not include the RC_ID_IE. In S229a to S230a, the server (20) sends a registration acceptance without using the RC_ID_IE, and the UE (10) does not send registration complete to the server (20).

[0039] Next, one or more impacts due to the signaling of Figure 2A are explained. When the UE (10) enables the timer, there is no uplink (UL) or downlink (DL) service that can be provided to the UE (10) for up to 10 seconds. Thus, additional, unnecessary overhead is imposed on the UE (10) to wait for an established RRC connection to be interrupted or to be released / local released by the server (20), perform a cell selection procedure to camp on the same cell, and re - establish the RRC connection again to send a pending registration request known to both the UE (10) and the server (20). Thus, traditional RACS features / procedures need to be improvised, and Figure 5 an improvised solution is described.

[0040] Refer to Figure 2B: At S201b, the UE (10) performs an initial operation to establish a connection with the server (20). At S202b to S203b, the UE (10) determines that there is no valid RC_ID stored in the memory of the UE (10). The UE (10) encodes the registration request message without using the RC_ID_IE. At S204b to S205b, the UE (10) sends a registration request to the server (20) to establish NAS signaling between the UE (10) and the server (20), where the registration request message does not include the RC_ID_IE. At S206b to S209b, the server (20) obtains the current radio capability information and assigns a new RC_ID to the current UE radio capability configuration. At S210b, the server (20) sends the UE RC_ID_IE to the UE (10) in the registration acceptance. At S211b, the UE (10) sends a registration completion to the server (20) in response to receiving the registration acceptance. At S212b - S213b, the UE (10) stores the UE RC_ID for the current PLMN and the current UE radio configuration and releases the connection.

[0041] At S214b to S215b, the UE (10) performs the initial operation again to establish a connection with the server (20). At S216b, the UE (10) determines that a valid RC_ID is stored in the memory of the UE (10) (S212b). At S217b, the UE (10) sends the UE RC_ID_IE with the RC_ID to the server (20) in the registration request. At S218b, the UE (10) establishes NAS signaling with the server (20). At S219b, the server (20) sends the UE RC_ID deletion IE to the UE (10) in the registration acceptance.

[0042] At S220b, when receiving the UE RC_ID deletion IE from the server (20) in the registration acceptance, the UE (10) encodes the registration completion message. At S221b to S223b, the UE (10) sends a registration completion to the server (20) and detects that the transmission of the registration completion fails due to the cell changing to a TA not registered in the same PLMN (transmission failure). As a result, the UE (10) does not perform the deletion of the UE RC_ID associated with the current PLMN.

[0043] At S224b, the UE (10) initiates a registration process for mobility. At S225b, the UE (10) encodes the registration request using the stored RC_ID in the RC_ID_IE. At S226b, the UE (10) sends a registration request to the server (20) for mobility update. At S227b, the server (20) sends a UE RC_ID deletion IE to the UE (10) in the registration acceptance. At S228b, when the UE RC_ID deletion IE is received in the registration acceptance from the server (20), the UE (10) encodes a registration completion message. At S229b, the UE (10) sends a registration completion to the server (20).

[0044] At S230b to S231b, the UE (10) deletes all valid RC_IDs stored in the memory of the UE (10) (S212b) and initiates a registration process. After deleting all valid RC_IDs stored in the memory (S212b), the registration process is mandatory. At S232b, the UE (10) sends a registration request to the server, where the registration request message does not include the RC_ID_IE. At S233b - S234b, the server (20) sends a registration acceptance without using the RC_ID_IE, and the UE (10) does not send a registration completion to the server (20).

[0045] Next, one or more impacts due to the signaling of Figure 2B are explained. The forced sending of a registration completion after receiving the UE RC_ID deletion IE, deleting the RC_ID and then initiating a registration process again are considered multiple actions taken by the UE (10) for the same purpose. This results in signaling overhead in both the UE (10) and the network side (e.g., the server (20)). For example, when the registration completion fails (transmission failure) due to a cell change to a TA not registered in the same PLMN, it leads to increased signaling between the UE (10) and the server (20) (e.g., S222b to S228b). Therefore, traditional RACS features / processes require improvisation, and regarding Figure 6 an improvisational solution is described.

[0046] Referring to Figure 2C, at S201c, the UE (10) performs an initial operation to establish a connection with the server (20). At S202c to S203c, the UE (10) determines that there is no valid RC_ID stored in the memory of the UE (10). The UE (10) encodes the registration request message without using the RC_ID_IE. At S204c to S205c, the UE (10) sends a registration request to the server (20) to establish NAS signaling between the UE (10) and the server (20), where the registration request message does not include the RC_ID_IE. At S206c to S209c, the server (20) obtains the current radio capability information and assigns a new RC_ID to the current UE radio capability configuration. At S210c, the server (20) sends the UE RC_ID in the RC_ID_IE to the UE (10) in the registration acceptance. At S211c to S214c, the UE (10) sends a registration complete to the server (20) in response to receiving the registration acceptance, detects that the transmission of the registration complete fails due to the cell changing to a TA not registered in the same PLMN (transmission failure), and the UE (10) does not store the received UE RC in the memory of the UE (10). Therefore, the UE (10) must retry the registration process.

[0047] At S215c to S216, the UE (10) sends a registration request to the server (20) to establish NAS signaling between the UE (10) and the server (20), where the registration request message does not include the RC_ID_IE. At S217c to S220c, the server (20) obtains the current radio capability information and assigns a new RC_ID to the current UE radio capability configuration. At S221c, the server (20) sends the UE RC_ID in the RC_ID_IE to the UE (10) in the registration acceptance. At S222c, the UE (10) sends a registration complete to the server (20) in response to receiving the registration acceptance.

[0048] Next, one or more impacts due to the signaling in Figure 2C are explained. When the server (20) assigns the RC_ID_IE in the registration acceptance but has not received the registration complete due to a lower layer failure or due to a change in the TAI, the behavior of both the UE (10) and the server (20) will result in signaling overhead. In addition, the overall goal of the RACS is not effectively utilized. Furthermore, in some cases, such as a lower layer failure without a TAI change before sending the registration complete, although the current 3GPP specifications indicate that the UE implements the UE (e.g., through the UE (10)), restarting the registration is the conventional solution for discovering all networks. Therefore, the traditional RACS features / processes need to be improvised, and regarding Figure 7 describe the improvised solutions.

[0049] Referring to FIG. 2D, at S201d, the UE (10) performs an initial operation to establish a connection with the server (20). At S202d to S203d, the UE (10) determines that no valid RC_ID is stored in the memory of the UE (10). The UE (10) encodes the registration request message without using the RC_ID_IE. At S204d to S205d, the UE (10) sends a registration request to the server (20) to establish NAS signaling between the UE (10) and the server (20), where the registration request message does not include the RC_ID_IE. At S206d to S209d, the server (20) obtains the current radio capability information and assigns a new RC_ID to the current UE radio capability configuration. At S210d, the server (20) sends the UE RC_ID_IE to the UE (10) in the registration acceptance. At S211d to S213d, the UE (10) sends a registration complete to the server (20) in response to receiving the registration acceptance, stores the received UE RC_ID_IE in the memory of the UE (10), and releases the connection.

[0050] At S214d, the UE (10) reselects to a new PLMN / TAC and detects that the reselected PLMN (20cb) / TAC belongs to the same AMF (20c). At S215d, the UE (10) triggers a registration request again to negotiate a new UE RC_ID. At S216d to S217d, the UE (10) sends a registration request to the server (20) to establish NAS signaling between the UE (10) and the server (20), where the registration request message does not include the RC_ID_IE. At S218d to S221d, the server (20) obtains the current radio capability information and assigns a new RC_ID to the current UE radio capability configuration. At S222d, the server (20) sends the RC_ID in the RC_ID_IE to the UE (10) in the registration acceptance. At S223d to -S224d, the UE (10) sends a registration complete to the server (20) in response to receiving the registration acceptance and stores the received UE RC_ID in the memory of the UE (10).

[0051] Next, one or more impacts caused by the signaling in FIG. 2D are explained. After receiving the UE RC_ID in the RC_ID_IE in the registration acceptance message for the current PLMN, even if the new PLMN or TAC belongs to the same AMF (20c), the current 3GPP specification states that the UE (10) will initiate a registration process to renegotiate the UERC_ID after moving to the new PLMN or TAC. Therefore, the traditional RACS features / processes need to be improvised, and regarding Figure 8 Describe the improvised solution.

[0052] Now referring to the drawings, and more particularly, to the drawings from Figures 3 to 8 which illustrate several embodiments, where like reference numerals throughout the drawings consistently denote corresponding features.

[0053] Figure 3 A block diagram of a UE (100) for enhancing NAS signaling in UE RACS in a wireless network according to an embodiment disclosed herein is shown.

[0054] In an embodiment, the UE (100) includes a memory (110), a processor (120), a communicator (130), and a NAS signaling controller (140).

[0055] In an embodiment, the memory (110) is configured to store RC_ID, TAC, and TAI lists. The memory (110) stores instructions to be executed by the processor (120). The memory (110) may include non-volatile storage elements. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or in the form of an electrically programmable memory (EPROM) or electrically erasable programmable (EEPROM) memory. Additionally, in some examples, the memory (110) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be construed to mean that the memory (110) is non-removable. In certain examples, the non-transitory storage medium may store data that can change over time (e.g., in a random access memory (RAM) or a cache). The memory (110) may be an internal storage unit of the UE (100), or an external storage unit, cloud storage, or any other type of external storage of the UE (100).

[0056] The processor (120) communicates with the memory (110), the communicator (130), and the NAS signaling controller (140). The processor (120) is configured to execute the instructions stored in the memory (110) and perform various processes. The processor (120) may include one or more processors and may be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), etc., a graphics processing unit only (such as a graphics processing unit (GPU)), a vision processing unit (VPU), and / or an artificial intelligence (AI) dedicated processor (such as a neural processing unit (NPU)).

[0057] The communicator (130) is configured to perform internal communication among internal hardware components (e.g., the memory (110), the processor (120), and the NAS signaling controller (140)) and communicate with external devices (e.g., one or more servers (200)) via one or more networks (e.g., the Internet, Wi-Fi, radio channels, etc.). The communicator (130) includes electronic circuits dedicated to implementing standards for wired and / or wireless communication.

[0058] The NAS signaling controller (140) is implemented by processing circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, etc., and can optionally be driven by firmware. For example, the circuit can be embodied in one or more semiconductor chips or on a substrate support such as a printed circuit board.

[0059] In an embodiment, the NAS signaling controller (140) is configured to receive the RC_ID in the RC_ID_IE from the server (200) of the wireless network (1000) to optimize the transmission of the UE (100). In addition, the NAS signaling controller (140) is configured to send a registration request message to the server (200) to establish NAS signaling between the UE (100) and the server (200). In addition, the NAS signaling controller (140) is configured to establish NAS signaling between the UE (100) and the server (200). In addition, the NAS signaling controller (140) is configured to enhance the NAS signaling between the UE (100) and the server (200) by performing one of the following operations: (a) receiving a registration acceptance message with the RC_ID deletion IE from the server (200), and sending a registration completion message to the server (200) using the existing NAS signaling, and not enabling a release timer in response to receiving the RC_ID deletion IE in the registration acceptance message; and (b) receiving a registration acceptance message with the RC_ID deletion IE from the server (200), and sending a registration completion message to the server (200) without responding to the RC_ID deletion IE received in the registration acceptance message.

[0060] In an embodiment, the NAS signaling controller (140) is configured to forcibly initiate a registration process for mobility using the existing NAS signaling connection in the connected mode after receiving the RC_ID deletion IE in the registration acceptance message, where the registration process in the connected mode reduces the NAS signaling latency and the use of radio resources between the UE (100) and the server (200).

[0061] In an embodiment, the NAS signaling controller (140) is configured to determine that the RC_ID is not stored in the UE (100). Further, the NAS signaling controller (140) is configured to encode a registration request message without using the RC_ID_IE in response to determining that the RC_ID_IE is not stored in the UE (100). Further, the NAS signaling controller (140) is configured to send the registration request message to the server (200) to establish NAS signaling between the UE (100) and the server (200), wherein the registration request message does not include the RC_ID_IE. Further, the NAS signaling controller (140) is configured to receive a registration acceptance message from the server (200), wherein the registration acceptance message includes the RC_ID_IE.

[0062] In an embodiment, the NAS signaling controller (140) is configured to perform one of the following operations: store the received RC_ID in the UE (100) and send a registration completion message to the server (200); send a registration completion message to the server (200) and store the received RC_ID in the UE (100); store the received RC_ID in the UE (100) and restart the registration process due to one of a change in the tracking area identity (TAI) and a lower layer failure or a transmission failure of the registration completion message to the server (200); and send a registration completion message to the server (200), store the received RC_ID in the UE (100), and restart the registration process based on a change in the TAC (tracking area code) in the serving public land mobile network (PLMN) of the radio network (1000).

[0063] In an embodiment, the NAS signaling controller (140) is configured to detect that the registration completion message is not received at the server (200). Further, the NAS signaling controller (140) is configured to retain the stored RC_ID. Further, the NAS signaling controller (140) is configured to restart the registration process by using the retained RC_ID in a registration request with the RC_ID_IE.

[0064] In an embodiment, the NAS signaling controller (140) is configured to determine whether the TAC is associated with the TAI and whether the serving PLMN is associated with the server (200), wherein the TAI is received from the server (200) in the registration acceptance message. Further, the NAS signaling controller (140) is configured to trigger the registration process by using the stored RC_ID in response to determining that the TAC is not associated with the TAI and the serving PLMN is associated with the server (200); and restart the registration process by using a new RC_ID in response to determining that the TAC is not associated with the TAI and the serving PLMN is not associated with the server (200).

[0065] In an embodiment, the RC_ID includes a set of radio capabilities of the UE (100), where the RC_ID is used as a replacement for AS signaling messages in the radio network (1000), and where the RC_ID is assigned by the server (200) of the radio network (1000) during the registration process or by the OEM (Original Equipment Manufacturer) by using the manufacturer RC_ID stored in the UE (100).

[0066] In an embodiment, the RC_ID of the UE (100) is updated via the Open Mobile Alliance (OMA) Device Management (DM) of the radio network (1000), and where the assigned RC_ID is only applicable to the current radio configuration of the UE (100) and is available in all PLMNs.

[0067] In an embodiment, the UE (100) deletes all stored RC_IDs assigned by the server (200) associated with the serving PLMN based on the deletion of the RC_ID IE in the received registration acceptance message.

[0068] Although Figure 3 various hardware components of the UE (100) are shown, it will be understood that other embodiments are not limited thereto. In other embodiments, the UE (100) may include fewer or greater numbers of components. Additionally, the labels or names of the components are for illustrative purposes only and do not limit the scope of the teachings herein. One or more components may be combined to perform the same or substantially similar functions to enhance NAS signaling.

[0069] Figure 4 is a flowchart (S400) showing a method for enhancing NAS signaling in UE RACS in a radio network (1000) according to an embodiment disclosed herein.

[0070] At S402, the UE (100) performs initial operations (e.g., power-on, layer initialization, SIM reading) to establish a connection with the server (200). At S404, the UE (100) determines whether any valid RC_ID is stored in the memory (110) of the UE (100). At S406, in response to determining that no valid RC_ID is stored in the memory (110) of the UE (100) (S404 = No), the UE (100) determines whether any valid manufacturer-assigned UE RC_ID is stored in the memory (110) of the UE (100). At S408, when the UE (100) has any valid RC_ID stored in the memory (110) or any valid manufacturer-assigned UE RC_ID stored in the memory (110) (S404 = Yes), the UE (100) encodes the registration request message using the UE RC_ID_IE.

[0071] At S410, the UE (100) sends a registration request to the server (20) to establish NAS signaling between the UE (100) and the server (200), where the registration request message does not include the UE RC_ID_IE. At S412, if the UE (100) does not have the RC_ID of the current UE radio configuration, the server (200) obtains the current radio capability information and assigns a new RC_ID to the current UE radio capability configuration. Then, the server (200) sends the UE RC_ID_IE to the UE (100) in the registration acceptance.

[0072] At S414, the UE (100) determines whether it receives the UE RC_ID_IE with the RC_ID in the registration acceptance. At S416, in response to determining that the UE RC_ID_IE is received in the registration acceptance (S414 = Yes), the UE (100) stores the UE RC_ID in the memory (110) and sends a registration completion to the server (200) of the network or N / W including the server (200). At S418, in response to determining that the UE RC_ID_IE is not received in the registration acceptance (S414 = No), the UE (100) determines whether it receives a UE RC_ID_IE deletion from the server (200).

[0073] At S420, the UE (100) deletes the UE RC_ID of the current PLMN from the memory (110) in response to determining that the UE RC_ID_IE deletion is received from the server (200) (S418=No) and stores the pending registration trigger due to the UE RC_ID_IE deletion. At S422, the UE (100) determines whether a registration completion must be sent to the server (200). At S424, the UE (100) determines whether the transmission is successful in response to determining that the registration completion must be sent to the server (200) (S422=Yes).

[0074] At S426, the UE (100) determines whether any pending registration process is stored in response to determining one of the following: the transmission is successful; the registration completion is not sent to the server (200); and the UE RC_ID_IE deletion is not received from the server (200). At S428, the UE (100) determines whether any pending registration process is stored for the UE RC_ID_IE deletion in response to determining that any pending registration process is stored (S426=Yes). At S429, the UE (100) enables a timer in response to determining that no pending registration process is stored for the UE RC_ID_IE deletion (S428=No). At S430, the registration is completed in response to determining that no pending registration process is stored (S426=No), or the registration is completed after the timer is enabled at S429.

[0075] The various actions, motions, blocks, steps, etc. in the flow chart (S400) may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some actions, motions, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the teachings herein or the scope of the present invention to which the teachings herein are directed.

[0076] Figure 5 , Figure 6 , Figure 7 and Figure 8 is a sequence diagram showing various signaling for enhancing NAS signaling between a UE (100) and a server (200) in a wireless network (1000) according to an embodiment disclosed herein.

[0077] Reference Figure 5, at S501, the UE (100) performs initial operations (e.g., power-on, layer initialization, SIM reading) to establish a connection with the server (200). At S502 to S503, the UE (100) determines that there is no valid RC_ID_IE stored in the memory (110) of the UE (100). The UE (100) encodes the registration request message without using the RC_ID_IE. At S504 to S505, the UE (100) sends a registration request to the server (20) to establish NAS signaling between the UE (100) and the server (200), where the registration request message does not include the RC_ID_IE. At S506 to S509, the server (200) obtains the current RC information and assigns a new RC_ID to the current UE radio configuration. At S510, the server (200) sends the E RC_ID in the RC_ID_IE to the UE (100) in the registration acceptance. At S511, the UE (100) sends a registration complete to the server (200) in response to receiving the registration acceptance. At S512 to S513, the UE (100) stores the UE RC_ID_IE for the current PLMN and the current UE radio configuration and releases the connection (NAS and AS connections).

[0078] At S514 to S515, the UE (100) performs the initial operations again to establish a connection with the server (200). At S516, the UE (100) determines that a valid RC_ID (S212a) is stored in the memory (110) of the UE (100). At S517, the UE (100) sends the UE RC_ID in the RC_ID_IE to the server (200) in the registration request. At S518, the UE (100) establishes NAS signaling with the server (200). At S519, the server (200) sends a UE RC_ID deletion IE to the UE (100) in the registration acceptance.

[0079] At S520 to S522, the UE (100) does not enable a timer (i.e., T3540) based on receiving the UE RC_ID deletion IE in the registration acceptance and retains the N1 signaling connection for the current PLMN after deleting the UE RC_ID stored in the UE (100). The timer should not be enabled in the UE (100) so that the UE (100) can immediately initiate the registration process on the existing NAS signaling connection. This can help reduce the latency of completing the process and save resources from the perspectives of the UE (e.g., UE (100)) and the server (200).

[0080] At S524 to S525, the UE (100) starts the registration process when deleting the stored UE RC_ID and encodes the registration request without using the UERC_ID_IE. At S526, the UE (100) sends a registration request to the server for mobility registration update, where the registration request message does not include the RC_ID_IE. At S527, the server (200) sends a registration acceptance without using the RC_ID_IE, and the UE (100) does not send a registration complete to the server (200).

[0081] Refer to Figure 6 : At S601, the UE (100) performs an initial operation to establish a connection with the server (200). At S602 to S603, the UE (100) determines that there is no valid RC_ID stored in the memory (110) of the UE (100). The UE (100) encodes the registration request message without using the RC_ID_IE. At S604 to S605, the UE (100) sends a registration request to the server (20) to establish NAS signaling between the UE (100) and the server (200), where the registration request message does not include the RC_ID_IE. At S606 to S609, the server (200) obtains the current radio capability information and assigns a new RC_ID to the current UE radio capability configuration. At S610, the server (200) sends the UE RC_ID_IE to the UE (100) in the registration acceptance. At S611, the UE (100) sends a registration complete to the server (200) in response to receiving the registration acceptance. At S612 to S613, the UE (100) stores the UE RC_ID for the current PLMN and the current UE radio configuration and releases the connection.

[0082] At S614 to S615, the UE (100) performs the initial operation again to establish a connection with the server (200). At S616, the UE (100) determines that a valid RC_ID is stored in the memory (110) of the UE (100) (S612). At S617, the UE (100) sends the UE RC_ID in the RC_ID_IE to the server (200) in the registration request. At S618, the UE (100) establishes NAS signaling with the server (200). At S619, the server (200) sends the UE RC_ID deletion IE to the UE (100) in the registration acceptance.

[0083] In S620 to S628, since the registration process is initiated based on receiving the UE RC_ID deletion IE, the redundant requirement of sending a registration completion message as an acknowledgement to the server (200) can be removed. This will further reduce the signaling exchange between the UE (100) and the server (200). Therefore, based on receiving the UE RC_ID deletion IE, the UE (100) can continue to initiate the registration process for mobility after deleting the applicable UE RC_ID from the memory (110). This enables the server (200) to allocate any new UE RC_ID to the UE (100), or use the manufacturer - allocated UE RC_ID that is already available in the UE (100). Sending the registration completion is not necessary because it does not serve any specific purpose.

[0084] Refer to Figure 7 : In S701, the UE (100) performs an initial operation to establish a connection with the server (200). In S702 to S703, the UE (100) determines that no valid RC_ID is stored in the memory (110) of the UE (100). The UE (100) encodes the registration request message without using the RC_ID_IE. In S704 to S705, the UE (100) sends a registration request to the server (200) to establish NAS signaling between the UE (100) and the server (200), where the registration request message does not include the RC_ID_IE. In S706 to S709, the server (200) obtains the current radio capability information and assigns a new RC_ID to the current UE radio capability configuration. In S710, the server (200) sends the UERC_ID with the RC_ID_IE to the UE (100) in the registration acceptance. In S711, the UE (100) stores the received UE RC_ID_IE for the current PLMN and radio configuration. In S712 to S713, the UE (100) sends a registration completion to the server (200) in response to receiving the registration acceptance, and detects that the transmission of the registration completion fails (transmission failure) due to the unit changing to a TA that is not registered in the same PLMN.

[0085] In S714 to S718, when restarting the registration process due to TAI change or lower layer failure, the UE (100) may consider the UE RC_ID received in the registration acceptance message to be valid for the current PLMN. Since the server (200) either retransmits the registration acceptance message or directly enters the registration state in case of any failure in receiving the registration complete message from the UE (100), this method will not result in any violation from the perspectives of the UE (100) and the server (200). Therefore, in case of a transmission failure of the registration complete message, the UE (100) will consider the most recently received UE RC_ID to be valid and, if it restarts the process, may send the UE RC_ID_IE in the registration request message to the server (200), provided that the UE (100) always remains in the same PLMN. When receipt of registration complete is not possible and when moving to the registration state, the server (200) will retain the allocated UE RC_ID. This will reduce the signaling exchanged between the UE (100) and the network when the UE (100) attempts to restart the registration process.

[0086] Refer to Figure 8 : In S801, the UE (100) performs an initial operation to establish a connection with the server (200). In S802 - S803, the UE (100) determines that no valid RC_ID is stored in the memory of the UE (100). The UE (100) encodes the registration request message without using the RC_ID_IE. In S804 to S805, the UE (100) sends a registration request to the server (200) to establish NAS signaling between the UE (100) and the server (200), where the registration request message does not include the RC_ID_IE. In S806 to S809, the server (200) obtains the current radio capability information and allocates a new RC_ID to the current UE radio capability configuration. In S810, the server (200) sends the UE RC_ID in the RC_ID_IE to the UE (100) in the registration acceptance. In S811 to S813, the UE (100) sends a registration complete to the server (200) in response to receiving the registration acceptance, stores the received UE RC_ID in the memory (110) of the UE (100), and releases the connection. In S814, the UE (100) reselects a PLMN / TAC and detects that the reselected PLMN (200cb) / TAC belongs to the same AMF (200c).

[0087] In S815 to S821, when the TAC is not part of the TAI list of the UE (100) shared by the server (200) during registration acceptance, the UE (100) cannot know whether the TAC it is camped on belongs to the same AMF (200c). Therefore, the UE (100) will use the currently valid RC_ID during registration. If the reselected PLMN (200cb) / TAC belongs to the same AMF (200c), a new RC_ID will not be allocated.

[0088] In S822 to S824, when the AMF changes, the existing process for new RC_ID allocation will be followed.

[0089] If the radio access network (RAN) has changed, the AMF will share this capability with the RAN via the N1 interface. Thus, in terms of mobility, when the UE (100) moves to a new PLMN or TAC belonging to the same AMF, the UE (100) can avoid sending a registration process to renegotiate the RC_ID again. This will reduce the signaling exchanged between the UE (100) and the server (200) in the mobility scenario.

[0090] As elaborated above, the embodiments herein provide the ability to retain the NAS signaling connection after deleting the UERC_ID stored in the UE for the current PLMN, where the deletion of the UE RC_ID is based on receiving a registration acceptance message from the wireless network. In addition, the timer T3540 in the UE does not need to be started in response to receiving the registration acceptance message, which is the basis for deleting the UERC_ID. As a result, the UE can immediately initiate the registration process based on the existing NAS signaling connection. This can help reduce the latency in completing the registration process and save radio resources associated with the UE and the wireless network.

[0091] Also as elaborated above, the redundant requirement of sending a registration complete message to the wireless network as an acknowledgement to the wireless network after receiving the registration acceptance message and deleting the UE RC_ID from the wireless network is removed. This can help reduce the signaling overhead in both the UE and the wireless network.

[0092] Also as elaborated above, when the registration process is restarted due to TAI change or lower layer failure or registration complete failure, the UE RC_ID received in the registration acceptance message can be considered valid for the current PLMN. This can help reduce the signaling exchanged between the UE and the wireless network when the UE attempts to restart the registration process.

[0093] As also explained above, it is possible to determine whether the newly resident TAC is part of the UE's TAI list received in the registration acceptance message. When the newly resident TAC is not in the UE's TAI list, the UE uses the same RC_ID received in the registration acceptance message. If the AMF / MME is the same, a new UE RC_ID will not be allocated. If the AMF / MME changes, the existing procedure for new UE RC_ID allocation will be followed. This can help reduce the signaling exchanged between the UE and the radio network in a mobility scenario.

[0094] Embodiments disclosed herein can be implemented using at least one hardware device and performing network management functions to control elements.

[0095] The foregoing description of specific embodiments will so fully disclose the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt various applications of the specific embodiments without departing from the general concept. Therefore, such adaptations and modifications are intended to be understood 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. Thus, although the embodiments herein have been described in terms of embodiments, those skilled in the art will recognize that embodiments herein can be practiced with modifications within the scope of the embodiments as described herein.

Claims

1. A method for enhancing non-access stratum signaling in radio capability signaling optimization of a wireless network, the method comprises: receiving, by a user equipment, radio capability identification information element with a radio capability identification from a server of the wireless network to optimize transmission of the user equipment; sending, by the user equipment, a registration request message to the server to establish non-access stratum signaling between the user equipment and the server; establishing, by the user equipment, non-access stratum signaling between the user equipment and the server; and enhancing, by the user equipment, the non-access stratum signaling between the user equipment and the server by performing one of the following steps: receiving, from the server, a registration acceptance message with a radio capability identification deletion information element, sending a registration completion message to the server using existing non-access stratum signaling, and not enabling a release timer in response to receiving the radio capability identification deletion information element in the registration acceptance message; and receiving, from the server, a registration acceptance message with the radio capability identification deletion information element, and not sending the registration completion message to the server in response to receiving the radio capability identification deletion information element in the registration acceptance message.

2. The method according to claim 1, further comprises: after receiving the radio capability identification deletion information element in the registration acceptance message, forcibly starting, by the user equipment, a registration process for mobility in a connected mode using existing non-access stratum signaling, wherein the registration process for mobility in the connected mode reduces non-access stratum signaling latency and usage of radio resources between the user equipment and the server.

3. The method according to claim 1, wherein receiving, by the user equipment, the radio capability identification in the radio capability identification information element from the server of the wireless network to optimize transmission of the user equipment comprises: determining, by the user equipment, that the radio capability identification is not stored in the user equipment; encoding, by the user equipment, the registration request message without using the radio capability identification information element; sending, by the user equipment, the registration request message to the server to establish non-access stratum signaling between the user equipment and the server, wherein the registration request message does not include the radio capability identification information element; and receiving, by the user equipment, the registration acceptance message from the server, wherein the registration acceptance message includes the radio capability identification in the radio capability identification information element.

4. The method according to claim 3, further comprises: performing, by the user equipment, one of the following steps: storing the received radio capability identification in the user equipment and then sending the registration completion message to the server; sending the registration completion message to the server and then storing the received radio capability identification in the user equipment; Store the received radio capability identifier in the user equipment, and subsequently restart the registration process due to at least one of a change in the tracking area identifier and a lower layer failure or a transmission failure of the registration completion message to the server; And Send the registration completion message to the server, subsequently store the received radio capability identifier in the user equipment, and subsequently restart the registration process based on a change in the tracking area code of the serving public land mobile network of the wireless network.

5. The method according to claim 4, Wherein, Restarting the registration process due to at least one of the change in the tracking area identifier and the lower layer failure includes: The user equipment detects that the registration completion message is not received at the server; The user equipment retains the stored radio capability identifier; and The user equipment restarts the registration process by using the retained radio capability identifier in the radio capability identifier information element in the registration request message.

6. The method according to claim 4, Wherein, Restarting the registration process based on a change in the tracking area code of the serving public land mobile network includes: The user equipment determines whether the tracking area code is associated with the tracking area identifier and whether the serving public land mobile network is associated with the server, wherein the tracking area identifier is received in the registration acceptance message from the server; and The user equipment performs one of the following steps: In response to determining that the tracking area code is not associated with the tracking area identifier and the serving public land mobile network is associated with the server, trigger the registration process by using the stored radio capability identifier; and In response to determining that the tracking area code is not associated with the tracking area identifier and the serving public land mobile network is not associated with the server, restart the registration process by using the stored radio capability identifier.

7. The method according to claim 1, Wherein, The radio capability identifier includes a set of radio capabilities of the user equipment, wherein the radio capability identifier information element is used as an alternative to the access stratum signaling message in the wireless network, and wherein the radio capability identifier is allocated by the server of the wireless network during the registration process, or the radio capability identifier includes the manufacturer radio capability identifier stored in the user equipment by the original equipment manufacturer.

8. The method according to claim 7, Wherein, The radio capability identifier of the user equipment is updated through the Open Mobile Alliance Device Management of the wireless network, and wherein the allocated radio capability identifier is only applicable to the current radio configuration of the user equipment and can be used in all public land mobile networks.

9. The method according to claim 1, further Includes: The user equipment deletes all stored radio capability identifiers assigned by the server and associated with the serving public land mobile network of the wireless network, based on the radio capability identifier deletion information element received in the registration acceptance message.

10. A user equipment for enhancing non-access stratum signaling in radio capability signaling optimization of a wireless network, the user equipment comprises: a memory; a processor; and a non-access stratum signaling controller operatively connected to the memory and the processor and configured to: receive, from a server of the wireless network, a radio capability identifier information element with a radio capability identifier to optimize transmission of the user equipment; send a registration request message to the server to establish non-access stratum signaling between the user equipment and the server; establish non-access stratum signaling between the user equipment and the server; and enhance the non-access stratum signaling between the user equipment and the server by performing at least one of the following: receive a registration acceptance message with a radio capability identifier deletion information element from the server, send a registration completion message to the server using existing non-access stratum signaling, and not enable a release timer in response to receiving the radio capability identifier deletion information element in the registration acceptance message; and receive a registration acceptance message with the radio capability identifier deletion information element from the server, and not send the registration completion message to the server in response to receiving the radio capability identifier deletion information element in the registration acceptance message.

11. The user equipment according to claim 10, wherein the user equipment is configured to perform: after receiving the radio capability identifier deletion information element in the registration acceptance message, the user equipment forcibly initiates a registration process for mobility in a connected mode using an existing non-access stratum signaling connection, wherein the registration process for mobility in the connected mode reduces non-access stratum signaling latency and the use of radio resources between the user equipment and the server.

12. The user equipment according to claim 10, wherein receiving the radio capability identifier in the radio capability identifier information element from a server of the wireless network to optimize transmission of the user equipment includes: determining that the radio capability identifier is not stored in the user equipment; encoding the registration request message without using the radio capability identifier information element; sending the registration request message to the server to establish non-access stratum signaling between the user equipment and the server, wherein the registration request message does not include the radio capability identifier information element; and receiving the registration acceptance message from the server, wherein the registration acceptance message includes the radio capability identifier in the radio capability identifier information element.

13. The user equipment according to claim 12, wherein the user equipment is configured to perform one of the following operations: Store the received radio capability identifier in the user equipment and then send the registration completion message to the server; Send the registration completion message to the server and then store the received radio capability identifier in the user equipment; Store the received radio capability identifier in the user equipment and then restart the registration process due to at least one of a change in the tracking area identifier and a lower layer failure or a transmission failure of the registration completion message to the server; And Send the registration completion message to the server, then store the received radio capability identifier in the user equipment, and then restart the registration process based on a change in the tracking area code in the serving public land mobile network of the wireless network.

14. The user equipment according to claim 13, wherein, Restarting the registration process due to at least one of the tracking area identifier and the lower layer failure includes: The user equipment detects that the registration completion message is not received at the server; The user equipment retains the stored radio capability identifier; and The user equipment restarts the registration process by using the retained radio capability identifier in the radio capability identifier information element of the registration request message.

15. The user equipment according to claim 13, wherein, Restarting the registration process based on a change in the tracking area code in the serving public land mobile network includes: Determine whether the tracking area code is associated with the tracking area identifier and whether the serving public land mobile network is associated with the server, wherein the tracking area identifier is received in the registration acceptance message from the server; and Perform one of the following operations: In response to determining that the tracking area code is not associated with the tracking area identifier and the serving public land mobile network is associated with the server, trigger the registration process by using the stored radio capability identifier; and In response to determining that the tracking area code is not associated with the tracking area identifier and the serving public land mobile network is not associated with the server, restart the registration process by using the stored radio capability identifier.

16. The user equipment according to claim 10, wherein, The radio capability identifier includes a set of radio capabilities of the user equipment, wherein the radio capability identifier is used as a substitute for the access stratum signaling message in the wireless network, and wherein the radio capability identifier is assigned by the server of the wireless network during the registration process, or the radio capability identifier includes a manufacturer radio capability identifier stored by the original equipment manufacturer in the user equipment.

17. The user equipment according to claim 16, wherein, Updating the radio capability identifier of the user equipment through the Open Mobile Alliance Device Management of the wireless network, and wherein the assigned radio capability identifier is only applicable to the current radio configuration of the user equipment and can be used in all public land mobile networks.

18. The user equipment according to claim 10, wherein, the user equipment deletes all stored radio capability identifiers assigned by the server and associated with the serving public land mobile network of the wireless network based on the radio capability identifier deletion information element in the received registration acceptance message.

Images