Method and UE for handling conflicts in a wireless communication network

Abstract

The present disclosure relates to a communication method and system for integrating a fifth generation (5G) communication system supporting a higher data rate than a fourth generation (4G) system with an Internet of Things (IoT) technology. The present disclosure can be applied to intelligent services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, smart retail, security and safety services. The embodiments of this document disclose a method for handling conflicts in a wireless communication network. The method includes detecting a conflict between a registration process initiated by a UE (100) and a deregistration process initiated by a wireless communication network, and determining whether a cause value received in a deregistration request message is one of the specific cause values ​​of the deregistration process. In addition, the method includes performing one of the following: when it is determined that the cause value is one of the specific cause values ​​of the deregistration process, terminating the deregistration process initiated by the wireless communication network and performing the registration process initiated by the UE (100); and when it is determined that the cause value is not one of the specific cause values ​​of the deregistration process, terminating the registration process initiated by the UE (100) and performing the deregistration process initiated by the wireless communication network.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly, to a method and user equipment for handling conflicts in a wireless communications network. This application is based on and claims the benefit of priority from Indian Application No. 201941017137 filed on April 30, 2019, the disclosure of which is incorporated herein by reference. Background Art

[0002] In order to meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop an improved 5G or quasi-5G communication system. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 60GHz bands) to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, large-scale multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, development of system network improvements is being carried out based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multipoint (CoMP), receiving end interference elimination, etc. In 5G systems, hybrid FSK with QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coded modulation (ACM), as well as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, which is a human-centric connectivity network in which humans produce and consume information, has now evolved into the Internet of Things (IoT), in which distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, which is a combination of IoT technology and big data processing technology through connection with cloud servers. Since IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology", sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been recently studied. Such IoT environments can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to a variety of fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances, and advanced medical services through the integration and combination between existing information technology (IT) and various industrial applications.

[0004] Therefore, various efforts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communication (MTC), and machine-to-machine (M2M) communication can be implemented through beamforming, MIMO, and array antennas. By applying a cloud radio access network (RAN) as described above, big data processing technology can also be considered as an example of the fusion between 5G technology and IoT technology. Summary of the invention

[0005] [Technical issues]

[0006] Generally, the non-access stratum (NAS) layer is a functional layer for exchanging signaling and traffic messages between a user equipment (UE) and a wireless communication network in an evolved packet system (EPS) and a fifth generation system (5GS) protocol stack. The main functions of the NAS layer are to support the mobility of the UE and to support the session management process. However, with the advancement and evolution of technologies associated with wireless communication networks, a number of issues regarding NAS signaling messages have become increasingly prominent.

[0007] One scenario associated with NAS signaling messages is that the UE is in an INACTIVE state and moves from PLMN ID 1 to a public land mobile network (PLMN) ID 2 due to mobility. However, the wireless communication network is unaware that the UE has moved to PLMN ID 2 and sends a NAS message (Deregistration Request message) such as cause #11 to the UE instructing the UE to populate the currently camped PLMN in the forbidden PLMN list. The UE populates PLMN ID 2 in the forbidden PLMN list, while the wireless communication network expects the UE to populate PLMN ID 1 in the forbidden PLMN list (the wireless communication network is unaware that the UE camps in PLMN ID 2). Therefore, due to the erroneous communication between the UE and the wireless communication network, the UE does not attempt to receive service on PLMN ID 2 even though PLMN ID 2 is the only PLMN serving an area. Therefore, the UE is affected by insufficient or no service even though PLMN ID 2 is available in the area.

[0008] In another scenario, when control plane optimization is enabled, cellular Internet of Things (CIoT) uplink user data is sent through the control plane. However, when the CIoT user data is very large, it takes a long time for the UE (100) to complete the transmission of the CIoT UL user data. Since NAS signaling message transmission and CIoT UL user data are transmitted through the same NAS signaling connection, the NAS signaling message transmission is queued when the CIoT UL user data transmission is in progress. Due to the transmission of a large amount of CIoT UL user data, the NAS signaling message transmission is significantly delayed. When the NAS signaling message is, for example, a registration request, the delay will cause the UE to fail to register, and this problem needs to be solved.

[0009] Therefore, there is a need to address the above-mentioned or other disadvantages or at least provide useful alternatives.

[0010] [Technical solution]

[0011] Therefore, an embodiment of the present invention discloses a method for handling a conflict between a registration process initiated by a user equipment (UE) (100) and a deregistration process initiated by a wireless communication network. The method includes the UE (100) initiating a registration process such as mobility and periodic registration updates by sending a registration request message to the wireless communication network; and before completing the registration process for mobility and periodic registration updates initiated by the UE (100), the UE (100) receives a deregistration request message from the wireless communication network for performing a deregistration process. The deregistration request message includes a cause value for the deregistration process. Further, the method includes the UE (100) detecting a conflict between a registration process initiated by the UE (100) and a deregistration process initiated by the wireless communication network, and the UE (100) determining whether the cause value received in the deregistration request message is one of the specific cause values ​​for the deregistration process. In addition, the method includes handling, by the UE (100), a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network by performing one of the following: in response to determining that the cause value received in the deregistration request message is one of the specific cause values ​​of the deregistration procedure, terminating the deregistration procedure initiated by the wireless communication network and performing a registration procedure initiated by the UE (100); and in response to determining that the cause value received in the deregistration request message is not one of the specific cause values ​​of the deregistration procedure, terminating the registration procedure initiated by the UE (100) and performing a deregistration procedure initiated by the wireless communication network.

[0012] In one embodiment, the specific reason value for the logout process is one of #11, #12, #13, and #15.

[0013] In one embodiment, detecting, by the UE (100), a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network includes determining, by the UE (100), that a deregistration request message from the wireless communication network is received before a registration accept message from the wireless communication network is received. The registration accept message indicates a response to a registration procedure initiated by the UE (100) for mobility and periodic registration updates. In addition, the method includes detecting, by the UE (100), a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network.

[0014] In one embodiment, detecting, by the wireless communication network, a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network includes determining, by the wireless communication network, that a registration request message from the UE (100) is received before a deregistration accept message from the UE (100). The deregistration accept indicates a response to the deregistration procedure initiated by the wireless communication network.

[0015] Therefore, an embodiment of the present invention discloses a method for handling a conflict between a registration process initiated by a user equipment (UE) (100) and a deregistration process initiated by a wireless communication network. The method includes initiating a deregistration process by the wireless communication network by sending a deregistration request message to the UE (100); and receiving a registration request message from the UE (100) by the wireless communication network to perform a registration process for mobility and periodic registration updates. The deregistration request message includes a cause value for the deregistration process. Further, the method includes detecting, by the wireless communication network, a conflict between a registration process initiated by the UE (100) and a deregistration process initiated by the wireless communication network, and determining, by the wireless communication network, whether the cause value received in the deregistration request message is one of the specific cause values ​​for the deregistration process. In addition, the method includes handling, by the wireless communication network, a conflict between a registration process initiated by the UE (100) and a deregistration process initiated by the wireless communication network by performing one of the following: in response to determining that the cause value received in the deregistration request message is one of the specific cause values ​​of the deregistration process, terminating the deregistration process initiated by the wireless communication network and performing a registration process initiated by the UE (100); and in response to determining that the cause value received in the deregistration request message is not one of the specific cause values ​​of the deregistration process, terminating the registration process initiated by the UE (100) and performing a deregistration process initiated by the wireless communication network.

[0016] Therefore, embodiments of the present invention disclose a user equipment (UE) (100) for handling a conflict between a registration process initiated by a UE (100) and a deregistration process initiated by a wireless communication network. The UE (100) includes a memory (140) and a processor (160) connected to the memory (140). The processor (160) is configured to: initiate a registration process for mobility and periodic registration updates by sending a registration request message to the wireless communication network; and before completing the registration process for mobility and periodic registration updates initiated by the UE (100), receive a deregistration request message from the wireless communication network for performing a deregistration process. The deregistration request message includes a cause value for the deregistration process. In addition, the processor (160) is configured to detect a conflict between the registration process initiated by the UE (100) and the deregistration process initiated by the wireless communication network, and determine whether the cause value received in the deregistration request message is one of the specific cause values ​​for the deregistration process. In addition, the processor (160) is configured to handle a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network by performing one of the following: in response to determining that the cause value received in the deregistration request message is one of the specific cause values ​​of the deregistration procedure, terminating the deregistration procedure initiated by the wireless communication network and performing a registration procedure initiated by the UE (100); and in response to determining that the cause value received in the deregistration request message is not one of the specific cause values ​​of the deregistration procedure, terminating the registration procedure initiated by the UE (100) and performing a deregistration procedure initiated by the wireless communication network.

[0017] Therefore, the embodiments of the present invention disclose an access and mobility management function (AMF) (1000) of a wireless communication network for handling a conflict between a registration process initiated by a UE (100) and a deregistration process initiated by a wireless communication network. The AMF (1000) includes a memory (1400) and a processor (1600) connected to the memory (1400). The processor (1600) is configured to: initiate a deregistration process by sending a deregistration request message to the UE (100); and receive a registration request message from the UE (100) to perform a registration process for mobility and periodic registration updates. The deregistration request message includes a cause value for the deregistration process. In addition, the processor (1600) is further configured to detect a conflict between a registration process initiated by the UE (100) and a deregistration process initiated by the wireless communication network, and determine whether the cause value received in the deregistration request message is one of the specific cause values ​​for the deregistration process. In addition, the processor (1600) is configured to handle a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network by performing one of the following: in response to determining that the cause value received in the deregistration request message is one of the specific cause values ​​of the deregistration procedure, terminating the deregistration procedure initiated by the wireless communication network and performing a registration procedure initiated by the UE (100); and in response to determining that the cause value received in the deregistration request message is not one of the specific cause values ​​of the deregistration procedure, terminating the registration procedure initiated by the UE (100) and performing a deregistration procedure initiated by the wireless communication network.

[0018] Therefore, embodiments of the present invention disclose a method for managing non-access stratum (NAS) signaling by a user equipment (UE) (100) in a wireless communication network. The method includes generating a first queue and a second queue by the UE (100), and determining by the UE (100) to initiate a NAS message for transmitting control plane user data to the wireless communication network in a connected mode. The second queue includes untransmitted control plane user data. In addition, the method includes determining by the UE (100) whether the first queue includes at least one NAS signaling message that is not transmitted at the UE (100). In addition, the method includes performing one of the following operations by the UE (100): sending at least one NAS signaling message that is not transmitted at the UE (100) from the first queue; and in response to determining that the first queue includes at least one NAS signaling message that is not transmitted at the UE (100), after sending the at least one NAS signaling message that is not transmitted at the UE (100), sending the control plane user data from the second queue to the wireless communication network; and in response to determining that the first queue does not include at least one NAS signaling message that is not transmitted at the UE (100), sending the control plane user data from the second queue to the wireless communication network.

[0019] Therefore, embodiments of the present invention disclose a user equipment (UE) (100) for managing non-access stratum (NAS) signaling in a wireless communication network. The UE (100) includes a memory (140) and a processor (160) connected to the memory (140). In addition, the processor (160) is configured to generate a first queue and a second queue, and to determine to initiate a NAS message for transmitting control plane user data to the wireless communication network in a connected mode. The second queue includes untransmitted control plane user data. In addition, the processor (160) is further configured to determine whether the first queue includes at least one NAS signaling message that is not transmitted at the UE (100). In addition, the processor (160) is further configured to perform one of the following operations: sending at least one NAS signaling message not transmitted at the UE (100) from the first queue; and in response to determining that the first queue includes at least one NAS signaling message not transmitted at the UE (100), after sending the at least one NAS signaling message not transmitted at the UE (100), sending control plane user data from the second queue to the wireless communication network; and in response to determining that the first queue does not include at least one NAS signaling message not transmitted at the UE (100), sending control plane user data from the second queue to the wireless communication network.

[0020] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and accompanying drawings. However, it should be understood that the following description, which indicates the preferred embodiment and numerous specific details thereof, is given by way of illustration and not by way of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit of the embodiments herein, and the embodiments herein include all such modifications.

[0021] [Beneficial Effects]

[0022] Embodiments herein provide a method and user equipment (UE) for handling contention in a wireless communication network. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The present invention is illustrated in the accompanying drawings, in which the same reference numerals represent corresponding parts in the various figures. The embodiments of the present invention will be better understood by the following description with reference to the accompanying drawings, in which:

[0024] Figure 1A is a block diagram of a user equipment (UE) (100) for handling a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by a wireless communication network according to an embodiment disclosed herein;

[0025] Figure 1Bis a block diagram of an access and mobility management function (AMF) (1000) for handling a conflict between a registration procedure initiated by a UE (100) and a deregistration procedure initiated by a wireless communication network according to an embodiment disclosed herein;

[0026] Figure 2A is a flowchart illustrating a method for handling, at a UE (100), a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by a wireless communication network according to an embodiment disclosed herein;

[0027] Figure 2B is a flowchart illustrating a method for handling a conflict between a registration procedure initiated by a UE (100) and a deregistration procedure initiated by the wireless communication network at a wireless communication network according to an embodiment disclosed herein;

[0028] Figure 2C is a flow chart illustrating a method for managing non-access stratum (NAS) signaling by a UE (100) in a wireless communication network according to an embodiment disclosed herein;

[0029] Figure 3A is a signaling diagram illustrating a conflict between a registration procedure initiated by a UE (100) and a deregistration procedure initiated by a wireless communication network according to the prior art;

[0030] Figure 3B is a signaling diagram illustrating a conflict occurring when a UE (100) is in an INACTIVE state according to the prior art;

[0031] Figure 3C is a signaling diagram illustrating a method for handling a conflict between a registration procedure initiated by a UE (100) and a deregistration procedure initiated by a wireless communication network according to an embodiment disclosed herein;

[0032] Figure 4A A scenario is shown in which a NAS signaling message transmission fails due to a UE (100) transmitting a large amount of cellular Internet of Things (CIoT) user data in a 5G communication network according to the prior art;

[0033] Figure 4B A scenario is shown in which NAS signaling message transmission is prioritized over CIoT user data transmission by a UE (100) in a 5G communication network according to an embodiment disclosed herein;

[0034] Figure 5A A scenario is shown in which a NAS signaling message transmission fails due to a UE (100) transmitting a large amount of CIoT user data in a 4G communication network according to the prior art;

[0035] Figure 5BA scenario is shown in which NAS signaling message transmission is prioritized over CIoT user data transmission by a UE (100) in a 4G communication network according to an embodiment disclosed herein;

[0036] Fig. 6A is a signaling diagram showing a failure in NAS signaling message transmission due to a UE (100) transmitting a large amount of CIoT user data in a 5G communication network according to the prior art;

[0037] Figure 6Ba is a signaling diagram illustrating prioritizing NAS signaling messages over CIoT user data by a UE (100) in a 5G communication network according to an embodiment disclosed herein;

[0038] Figure 6Bb is a signaling diagram illustrating prioritizing NAS signaling messages over CIoT user data by a UE (100) in a 5G communication network according to an embodiment disclosed herein;

[0039] Fig. 7A is a signaling diagram showing a failure in NAS signaling message transmission due to a UE (100) transmitting a large amount of CIoT user data in a 4G communication network according to the prior art;

[0040] Figure 7Ba is a signaling diagram illustrating prioritizing NAS signaling messages over CIoT user data by a UE (100) in a 4G communication network according to an embodiment disclosed herein; and Figure 7Bb is a signaling diagram showing prioritization of NAS signaling messages over CIoT user data by a UE (100) in a 4G communication network according to an embodiment disclosed herein. DETAILED DESCRIPTION

[0041] The embodiments of the present invention and their various features and advantageous details are explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the description below. Descriptions of well-known components and processing techniques are omitted so as not to unnecessarily confuse the embodiments of the present invention. In addition, the various embodiments described herein are not mutually exclusive, and some embodiments may be combined with one or more other embodiments to form new embodiments. The term "or" used herein refers to a non-exclusive "or" unless otherwise specified. The examples used herein are intended only to help understand the ways in which the embodiments of the present invention can be practiced, and further enable those skilled in the art to practice the embodiments of the present invention. Therefore, these examples should not be interpreted as limiting the scope of the embodiments of the present invention.

[0042] As is traditional in the art, embodiments may be described and illustrated according to the blocks that perform the one or more functions described. These blocks (herein may be referred to as units or modules, etc.) are physically implemented by analog and 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 be optionally driven by firmware and software. The circuit may be implemented, for example, in one or more semiconductor chips, or implemented on substrate supports such as printed circuit boards. The circuit constituting the block may be implemented by dedicated hardware, or implemented by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware for executing some functions of the block and the processor and a processor for executing other functions of the block. Without separating the scope of the present disclosure, each block of the embodiment may be physically divided into two or more interactive and discrete blocks. Similarly, without separating the scope of the present disclosure, the block of the embodiment may be physically combined into more complex blocks.

[0043] The accompanying drawings are used to help easily understand various technical features, and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. Therefore, the present disclosure should be interpreted as extending to any changes, equivalents and alternative forms except those specifically listed in the accompanying drawings. Although the terms "first", "second" etc. can be used to describe various elements in this article, these elements should not be limited by these terms. These terms are usually only used to distinguish one element from another element.

[0044] Therefore, an embodiment of the present invention discloses a method for handling a conflict between a registration process initiated by a user equipment (UE) (100) and a deregistration process initiated by a wireless communication network. The method includes the UE (100) initiating a registration process for mobility and periodic registration updates by sending a registration request message to the wireless communication network; and the UE (100) receiving a deregistration request message for performing a deregistration process from the wireless communication network before completing the registration process for mobility and periodic registration updates initiated by the UE (100). Further, the method includes the UE (100) detecting a conflict between the registration process initiated by the UE (100) and the deregistration process initiated by the wireless communication network, and the UE (100) determining whether the deregistration request message includes a reason for the deregistration process. In addition, the method includes handling, by the UE (100), a conflict between a registration process initiated by the UE (100) and a deregistration process initiated by the wireless communication network by performing one of the following: in response to determining that the deregistration request message includes a reason for the deregistration process, terminating the deregistration process initiated by the wireless communication network and performing a registration process initiated by the UE (100); and in response to determining that the deregistration request message does not include a reason for the deregistration process, terminating the registration process initiated by the UE (100) and performing a deregistration process initiated by the wireless communication network.

[0045] Referring now to the drawings and more particularly to Figures 1A to 7Bb Preferred embodiments are shown, with like reference numerals consistently indicating corresponding features throughout the drawings.

[0046] Figure 1A A block diagram of a user equipment (UE) (100) for handling a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by a wireless communication network according to embodiments disclosed herein.

[0047] See also Figure 1A UE (100) may be, for example, a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a wearable device, etc. In one embodiment, UE (100) may include a communicator (120), a memory (140), and a processor (160).

[0048] In one embodiment, the communicator (120) is configured to send a registration request message to a wireless communication network; and receive a deregistration request message for performing a deregistration procedure from the wireless communication network before completing a registration procedure for mobility and periodic registration updates initiated by the UE (100).

[0049] The registration procedure initiated by the UE (100) for mobility and periodic registration update is an example of a registration procedure initiated by the UE (100). In addition, the registration procedure triggered by the UE can be used for any purpose. In addition, the registration procedure is similar to the Tracking Area Update (TAU) procedure.

[0050] The memory (140) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or various forms of electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). In addition, in some examples, the memory (140) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not implemented in a carrier wave or propagating signal. However, the term "non-transitory" should not be interpreted as the memory (140) being non-removable. In some examples, the memory (140) may be configured to store a larger amount of information than the memory. In some examples, the non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache).

[0051] The processor (160) includes a conflict detection engine (162), a registration management engine (164), a queue generation engine (166), and a non-access stratum (NAS) signaling management engine (168).

[0052] In one embodiment, the conflict detection engine (162) is configured to detect a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network. This includes determining, by the UE (100), that a deregistration request message is received from the wireless communication network before a registration accept message is received from the wireless communication network. The registration accept message indicates a response to the registration procedure initiated by the UE (100). In addition, the method includes detecting, by the UE (100), a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network.

[0053] The registration process initiated by the UE (100) may be due to the mobility of the UE (100). The deregistration process initiated by the wireless communication network may be due to the expiration of the agreement with the first PLMN. In addition, the conflict detection engine (162) is configured to determine whether the deregistration request message includes a specific cause value for the deregistration process. The specific cause value for the deregistration process is one of #11, #12, #13 and #15. When the cause of the deregistration process is one of #11, #12, #13 and #15, the erroneously prohibited TAI or PLMN will be filled into the corresponding prohibited list. The proposed method discussed for PLMN is also applicable to TAI. The proposed method can be applied to the situation where there is a conflict between the deregistration procedure initiated by the network for reasons #11, #12, #13 or #15 and the registration procedure initiated by the UE (100) in the 5GMM-REGISTERED state for mobility and periodic registration updates, wherein when the UE (100) in the 5GMM-CONNECTED mode with RRC inactivity indication enters a new cell (or optional shared network cell) in the current registration area that belongs to an equivalent PLMN of the registered PLMN and does not belong to the registered PLMN, the registration procedure is initiated by sending a REGISTRATIONREQUEST message to the AMF (1000).

[0054] In one embodiment, the registration management engine (164) is configured to handle a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network by performing one of the following: in response to determining that the cause value received in the deregistration request message is one of the specific cause values ​​of the deregistration procedure, terminating the deregistration procedure initiated by the wireless communication network and performing a registration procedure initiated by the UE (100); and in response to determining that the cause value received in the deregistration request message is not one of the specific cause values ​​of the deregistration procedure, terminating the registration procedure initiated by the UE (100) and performing a deregistration procedure initiated by the wireless communication network.

[0055] The proposed method refers to specific cause values ​​#11, #12, #13, #15, which values ​​may not be limited thereto. Cause value #11 (not allowed PLMN) is a 5GMM cause sent by the wireless communication network to the UE (100) when the UE (100) requests a service, or when the wireless communication network initiates a deregistration request, in a PLMN in which the UE (100) is not allowed to operate, either by subscription or due to operator-determined prohibition.

[0056] Cause value #12 (Not allowed tracking area) is a 5GMM cause sent to the UE (100) when the UE (100) requests service in a tracking area where the HPLMN or SNPN determines that the UE (100) is not allowed to operate through subscription, or if the wireless communication network initiates a deregistration request. Cause value #13 (Not allowed roaming in tracking area) is a 5GMM cause sent to the UE (100) when the wireless communication network initiates a deregistration request in a tracking area where the PLMN or SNPN provides roaming services to UEs (100) not in the tracking area through subscription, or when a UE (100) not in the tracking area requests service in the tracking area. Cause value #15 (No suitable cell in tracking area) is a 5GMM cause sent to the UE (100) when the UE (100) requests service in this case, or if the wireless communication network initiates a deregistration request in this case, in a tracking area where the UE (100) is not allowed to operate through subscription, but when the UE (100) should find another allowed tracking area in the same PLMN or equivalent PLMN or the same SNPN. These causes basically indicate actions from the wireless communication network to the UE (100) based on the current location of the UE (100), so any new cause (100) with the importance of the location of the UE (100) that can be introduced in the standard will also be applicable to the proposed method. The main problem is that when the UE (100) initiates a registration procedure, this may be due to a change in the current location, so in this process, if an action carrying a specific cause value (such as #11, #12, #13, #15) with the importance of the location of the UE (100) is initiated by the wireless communication network in the form of a deregistration procedure, then this action must be ignored by both the UE (100) and the wireless communication network, otherwise it is assumed that the UE (100) is in location 1 while the UE (100) is actually in location 2, and the action initiated by the wireless network does not match. Therefore, in this embodiment, it is proposed that if the wireless communication network is sure that the same action is applicable even for location 2, then the wireless communication network can even perform the action for location 2, for example by re-performing the deregistration procedure, after which the first network should be updated with the new correct location of the UE (100).

[0057] The registration procedure in this embodiment is similar to the tracking area update procedure, the attach procedure, the registration procedure for initial registration, the registration procedure for mobility and the periodic registration update.

[0058] The deregistration process in this embodiment is similar to the separation process.

[0059] In one embodiment, the registration process in this embodiment may be initiated by the UE (100) for any reason known in the prior art, and may not be limited to changes in the location area of ​​the UE (100) (i.e., not only when the UE (100) moves out of the registration area).

[0060] In one embodiment, the queue generation engine (166) is configured to generate a first queue and a second queue. The first queue includes at least one NAS signaling message that has not been transmitted at the UE (100). The second queue includes a plurality of control plane user data to be transmitted at the UE (100). The first queue has a higher priority than the second queue to ensure that the NAS signaling message is sent to the wireless communication network without any delay. Therefore, even if the NAS signaling message and the control plane user data are sent via the same NAS signaling connection using a single NAS count (such as cellular Internet of Things (CIoT) data transmission), the NAS signaling message will not be delayed due to the priority of the queue.

[0061] In one embodiment, the NAS signaling management engine (168) is configured to determine an initiation of a NAS message for transmitting control plane user data to a wireless communication network in a connected mode, and further determine whether the first queue includes at least one NAS signaling message not transmitted at the UE (100). In addition, the NAS signaling management engine (168) is configured to perform one of the following operations: sending at least one NAS signaling message not transmitted at the UE (100) from the first queue; then in response to determining that the first queue includes at least one NAS signaling message not transmitted at the UE (100), after transmitting the at least one NAS signaling message not transmitted at the UE (100), sending the control plane user data from the second queue to the wireless communication network; and in response to determining that the first queue does not include at least one NAS signaling message not transmitted at the UE (100), sending the control plane user data from the second queue to the wireless communication network. The NAS message for transmitting the control plane user data is one of an uplink (UL) NAS transmission message and an EPS session management (ESM) data transmission message. The at least one NAS signaling message is one of a registration request message and a tracking area update (TAU) request message.

[0062] although Figure 1A The hardware elements of the UE (100) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the UE (100) may include fewer or more elements. In addition, the labels or names of the elements are only for illustrative purposes and are not intended to limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions.

[0063] Figure 1B A block diagram of an access and mobility management function (AMF) (1000) for handling a conflict between a registration procedure initiated by a UE (100) and a deregistration procedure initiated by a wireless communication network according to an embodiment disclosed herein.

[0064] refer to Figure 1B , the AMF (1000) includes a transceiver (1200), a memory (1400) and a processor (1600).

[0065] In one embodiment, the transceiver (1200) is configured to initiate a deregistration procedure by sending a deregistration request message to the UE (100), and to receive a registration request message from the UE (100) to perform a registration procedure for mobility and periodic registration updates.

[0066] The memory (1400) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or various forms of electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). In addition, in some examples, the memory (1400) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not implemented in a carrier or propagation signal. However, the term "non-transitory" should not be interpreted as the memory (1400) being non-removable. In some examples, the memory (1400) may be configured to store a larger amount of information than the memory. In some examples, the non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache).

[0067] The processor (1600) includes a conflict detection engine (1620) and a registration management engine (1640). In one embodiment, the conflict detection engine (1620) is configured to determine that a registration request message from the UE (100) is received before a deregistration acceptance message is received from the UE (100), and to detect a conflict between a registration process initiated by the UE (100) and a deregistration process initiated by the wireless communication network. The deregistration acceptance message indicates a response to the deregistration process initiated by the wireless communication network. In addition, the conflict detection engine (1620) is further configured to determine whether the deregistration request message includes a specific cause value for the deregistration process. The specific cause value for the deregistration process is at least one of #11, #12, #13, and #15.

[0068] In one embodiment, the registration management engine (1640) is configured to handle a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network by performing one of the following: in response to determining that the cause value received in the deregistration request message is one of the specific cause values ​​of the deregistration procedure, terminating the deregistration procedure initiated by the wireless communication network and performing a registration procedure initiated by the UE (100); and in response to determining that the cause value received in the deregistration request message is not one of the specific cause values ​​of the deregistration procedure, terminating the registration procedure initiated by the UE (100) and performing a deregistration procedure initiated by the wireless communication network.

[0069] although Figure 1B The hardware components of the AMF (1000) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the AMF (1000) may include fewer or more components. In addition, the labels or names of the components are only for illustrative purposes and do not limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions.

[0070] Figure 2A The invention is a flowchart showing a method for handling, at a UE (100), a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by a wireless communication network according to an embodiment disclosed herein.

[0071] refer to Figure 2A At step 202a, the UE (100) initiates a registration procedure for mobility and periodic registration updates by sending a registration request message to the wireless communication network. Figure 1A In the illustrated UE (100), the processor (160) may be configured to initiate a registration procedure for mobility and periodic registration updates by sending a registration request message to a wireless communication network.

[0072] At step 204a, the UE (100) receives a deregistration request message for performing a deregistration procedure from the wireless communication network before completing the registration procedure for mobility and periodic registration update initiated by the UE (100). Figure 1A In the illustrated UE (100), the communicator (120) may be configured to receive a deregistration request message for performing a deregistration procedure from a wireless communication network before completing a registration procedure for mobility and periodic registration updates initiated by the UE (100).

[0073] At step 206a, the UE (100) detects a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network. Figure 1A In the illustrated UE (100), the processor (160) may be configured to detect a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network.

[0074] At step 208a, the UE (100) determines whether the deregistration request message includes one of the specific reasons #11, #12, #13 and #15 for the deregistration procedure. Figure 1A In the illustrated UE (100), the processor (160) may be configured to determine whether the deregistration request message includes a reason for the deregistration procedure.

[0075] At step 210a, in response to determining that the deregistration request message includes a specific cause value for the deregistration procedure, the UE (100) terminates the deregistration procedure initiated by the wireless communication network and performs a registration procedure initiated by the UE (100). Figure 1A In the UE (100) shown, the processor (160) may be configured to terminate a deregistration process initiated by the wireless communication network and perform a registration process initiated by the UE (100).

[0076] At step 212a, in response to determining that the deregistration request message does not include a specific cause value for the deregistration procedure, the UE (100) terminates the registration procedure initiated by the UE (100) and performs a deregistration procedure initiated by the wireless communication network. Figure 1A In the illustrated UE (100), the processor (160) may be configured to terminate a registration process initiated by the UE (100) and perform a deregistration process initiated by the wireless communication network.

[0077] The various actions, behaviors, frames, steps, etc. in the method may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some actions, behaviors, frames, steps, etc. may be omitted, added, modified, or skipped without separating the scope of the present invention.

[0078] Figure 2B The invention is a flowchart showing a method for handling a conflict between a registration procedure initiated by a UE (100) and a deregistration procedure initiated by the wireless communication network at a wireless communication network according to an embodiment disclosed herein.

[0079] refer to Figure 2B At step 202b, the AMF (1000) initiates the deregistration process by sending a deregistration request message to the UE (100). Figure 1B In the AMF (1000) shown, the processor (1600) can be configured to initiate a deregistration process by sending a deregistration request message to the UE (100).

[0080] At step 204b, the AMF (1000) receives a registration request message from the UE (100) to perform a registration procedure for mobility and periodic registration updates. Figure 1B In the illustrated AMF (1000), the processor (1600) may be configured to receive a registration request message from the UE (100) to perform a registration procedure for mobility and periodic registration updates.

[0081] At step 206b, the AMF (1000) detects a conflict between a registration procedure initiated by the UE (100) and a deregistration procedure initiated by the wireless communication network. Figure 1BIn the AMF (1000) shown, the processor (1600) can be configured to detect a conflict between a registration process initiated by the UE (100) and a deregistration process initiated by the wireless communication network.

[0082] At step 208b, the AMF (1000) determines whether the deregistration request message includes one of the reasons #11, #12, #13 and #15 for the deregistration process. Figure 1B In the AMF (1000) shown, the processor (1600) may be configured to determine whether the deregistration request message includes a reason for the deregistration procedure.

[0083] At step 210a, in response to determining that the deregistration request message includes a reason for the deregistration procedure, the AMF (1000) terminates the deregistration procedure initiated by the wireless communication network and performs a registration procedure initiated by the UE (100). Figure 1B In the AMF (1000) shown, the processor (1600) can be configured to terminate the deregistration process initiated by the wireless communication network and perform the registration process initiated by the UE (100).

[0084] At step 212b, in response to determining that the deregistration request message does not include a reason for the deregistration procedure, the AMF (1000) aborts the registration procedure initiated by the UE (100) and performs a deregistration procedure initiated by the wireless communication network. Figure 1B In the AMF (1000) shown, the processor (1600) can be configured to terminate the registration process initiated by the UE (100) and perform the deregistration process initiated by the wireless communication network.

[0085] The various actions, behaviors, frames, steps, etc. in the method may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some actions, behaviors, frames, steps, etc. may be omitted, added, modified, skipped, etc. without separating the scope of the present invention.

[0086] The various actions, behaviors, frames, steps, etc. in the method may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some actions, behaviors, frames, steps, etc. may be omitted, added, modified, skipped, etc. without separating the scope of the present invention.

[0087] Figure 2C The present invention is a flowchart showing a method for managing NAS signaling by a UE (100) in a wireless communication network according to an embodiment disclosed herein.

[0088] refer to Figure 2C At step 222, the UE (100) detects that a NAS message session is being conducted in the wireless communication network. Figure 1AIn the illustrated UE (100), the processor (160) may be configured to detect that a NAS message session is ongoing in the wireless communication network.

[0089] At step 224, the UE (100) queues at least one NAS signaling message initiated by the UE (100) during the ongoing NAS message session in a first queue. Figure 1A In the illustrated UE (100), the processor (160) may be configured to place at least one NAS signaling message initiated by the UE (100) during an ongoing NAS message session in a first queue.

[0090] At step 226, the UE (100) determines that at least one NAS message transmission of a plurality of NAS messages in the ongoing NAS message session is complete. Figure 1A In the UE (100) shown, the processor (160) may be configured to determine that transmission of at least one NAS message among a plurality of NAS messages in an ongoing NAS message session is completed.

[0091] At step 228, the UE (100) queues the remaining NAS messages of the plurality of NAS messages initiated by the UE (100) during the ongoing NAS message session in a second queue. Figure 1A In the illustrated UE (100), the processor (160) may be configured to place remaining NAS messages of a plurality of NAS messages initiated by the UE (100) during an ongoing NAS message session in a second queue.

[0092] At step 230, the UE (100) sends the at least one NAS signaling message in the first queue that has not been transmitted to the wireless communication network. Figure 1A In the UE (100) shown, the processor (160) may be configured to send at least one NAS signaling message in the first queue that has not been transmitted to the wireless communication network.

[0093] At step 232, the UE (100) resumes transmission of remaining NAS messages in the plurality of NAS messages after sending at least one NAS signaling message that has not been transmitted in the first queue to the wireless communication network. Figure 1A In the UE (100) shown, the processor (160) may be configured to resume transmission of remaining NAS messages in the plurality of NAS messages after sending at least one NAS signaling message in the first queue that has not been transmitted to the wireless communication network.

[0094] The various actions, behaviors, frames, steps, etc. in the method may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some actions, behaviors, frames, steps, etc. may be omitted, added, modified, or skipped without separating the scope of the present invention.

[0095] Figure 3A is a signaling diagram illustrating a conflict between a registration procedure initiated by a UE (100) and a deregistration procedure initiated by a wireless communication network according to the prior art.

[0096] Consider a scenario where the UE (100) is in INACTIVE state on PLMN ID 1. The AMF (1000) has the UE context and knows that the UE (100) is on PLMN ID 1 (step 1b).

[0097] At step 1a, the UE (100) moves from PLMN ID-1 to PLMN ID-2 and initiates a registration procedure by sending a Registration Request message (step 2a).

[0098] Simultaneously, on the network side, at step 1b, the PLMN ID-1 agreement with the AMF (1000) expires, and therefore the AMF (1000) initiates a deregistration procedure for cause #11 (PLMN not allowed) by sending a deregistration request message to the UE (100) (step 2b). Thus, a scenario is caused where a registration procedure initiated by the UE (100) conflicts with a deregistration procedure initiated by the network. Normally, it is expected that the UE (100) populates the PLMN-ID 1 in the forbidden PLMN (FPLMN) list, and based on the FPLMN list, the UE (100) will never attempt to receive services on PLMN ID 1.

[0099] However, at step 3, upon determining that the network has simultaneously initiated a deregistration procedure, the UE (100) and the network abort the registration procedure triggered by the UE (100). In addition, when the UE (100) receives a deregistration request message of cause #11, the UE (100) will populate the currently residing PLMN ID, i.e., PLMN ID 2 in the FPLMN list, in the forbidden PLMN list. However, according to step 2b, the AMF attempts to populate PLMN ID 1 in the FPLMN list instead of the currently populated PLMN ID 2. Therefore, due to the incorrect PLMN ID being populated in the FPLMN list, the UE (100) will never attempt to receive service on PLMN ID 2 (i.e., no registration request), and the UE (100) will maintain limited service in all areas where only PLMN ID 2 is available.

[0100] Figure 3Bis a signaling diagram illustrating a conflict that occurs when a UE (100) is in an INACTIVE state according to the prior art.

[0101] refer to Figure 3B , at step 1, the UE (100) moves from PLMN ID 1 to PLMN ID 2. At step 2, the AMF (1000) is not aware that the UE (100) has moved to PLMN ID 2, but the AMF (1000) is already in CONNECTED mode (in INACTIVE state), so the AMF (1000) immediately sends a NAS message (Deregistration) to the UE (100), which causes a conflict between the Registration Request message triggered by the UE (100) and the Deregistration Request message triggered by the AMF (1000).

[0102] In IDLE mode, the AMF (1000) or MME (4000) will initiate paging and perform RRC procedures, so the AMF (1000) / MME (4000) will know the correct PLMN ID (as part of the RRC procedure and S1-AP procedure) before sending a NAS PDU (Deregistration Request). After knowing that the UE (100) E is on PLMN ID 2, the AMF (1000) / MME (4000) will not send a Deregistration Request message to the UE (100).

[0103] Figure 3C is a signaling diagram illustrating a method for handling a conflict between a registration procedure initiated by a UE (100) and a deregistration procedure initiated by a wireless communication network according to an embodiment disclosed herein.

[0104] Combination Figure 3A And refer to Figure 3C , Figure 3C Steps 1a to 2b in Figure 3A Steps 1a to 2b in are substantially the same, and thus repeated descriptions are omitted.

[0105] At step 3a, the UE (100) determines whether the deregistration request message includes at least one of #11, #12, #13 and #15 as the 5GMM cause of the deregistration process. In addition, when the UE (100) determines that the deregistration request message includes at least one of #11, #12, #13 and #15 as the 5GMM cause of the deregistration process before the registration process for mobility and periodic registration update has been completed, the deregistration process initiated by the wireless communication network is terminated and the registration process initiated by the UE (100) is performed. In addition, when the UE (100) determines that the deregistration request message does not include at least one of #11, #12, #13 and #15 as the 5GMM cause of the deregistration process, the registration process initiated by the UE (100) is terminated and the deregistration process initiated by the wireless communication network is performed.

[0106] Similarly, at step 3b, the wireless communication network determines whether the deregistration request message sent to the UE (100) includes at least one of #11, #12, #13 and #15 as the 5GMM cause of the deregistration process. In addition, the wireless communication network terminates the deregistration process initiated by the wireless communication network and performs the registration process initiated by the UE (100) when it determines that the deregistration request message includes at least one of #11, #12, #13 and #15 as the 5GMM cause of the deregistration process before the registration process for mobility and periodic registration update has been completed. In addition, the wireless communication network terminates the registration process initiated by the UE (100) and performs the deregistration process initiated by the wireless communication network when it determines that the deregistration request message does not include at least one of #11, #12, #13 and #15 as the 5GMM cause of the deregistration process.

[0107] Figure 4A A scenario is shown in which NAS signaling message transmission fails due to UE (100) sending a large amount of CIoT user data in a 5G communication network according to the prior art.

[0108] When the CIoT user data is large, it takes a long time for the UE (100) to complete the transmission of the CIoT UL user data. However, the NAS signaling message transmission and the CIoT UL user data are sent through the same NAS signaling connection using the same pair of NAS counts. Therefore, when the CIoT UL user data transmission is in progress, the transmission of the NAS signaling message enters the queue, which causes a significant delay in the NAS signaling message transmission. In addition, if the wireless communication network also enables the serving PLMN data control and 3GPP enhanced coverage functions, the transmission delay of the NAS signaling message will be further widened. The above issue is part of the specification, and CR193953 was added in 24.501, in which the conflict handling between the NAS signaling message and the UL NAS transmission message depends on the implementation of the UE (100).

[0109] Consider a scenario where CIoT 5GS optimization is enabled. In the CIoT Small Data Container (as described in Section 9.11.3.18B of specification 3GPP 24.501), when control plane CIoT 5GS optimization is enabled, information elements are used to encapsulate CIoT user data, SMS or location service messages, whose size does not exceed 254 octets between the UE (100) and the AMF (1000). The CIoT Small Data Container is a Type 4 information element with a minimum length of 4 octets and a maximum length of 257 octets (as shown below).

[0110]

[0111] Therefore, the transmission of large CIoT user data requires the transmission of multiple CIoT small data containers that carry a portion of the large CIoT user data. In addition, during the transmission of multiple CIoT small data containers, if a NAS signaling message related to, for example, TAU update or registration needs to be sent, the NAS signaling message is delayed until the transmission of multiple CIoT small data containers is completed.

[0112] In addition, the serving PLMN rate control protects the AMF (1000) and signaling radio bearers in E-UTRA from the load generated by user data on the control plane. During the PDU session establishment procedure (as described in subclause 6.4.1 of 3gpp 24.501) or the PDU session modification procedure (as described in subclause 6.4.2 of 3gpp 24.501), the session management function (SMF) notifies the UE (100) of any local serving PLMN rate control. If serving PLMN rate control is enabled, the SMF starts serving PLMN rate control for the PDU session when the first control plane user data is received over the PDU session. The UE (100) limits the rate at which uplink control plane user data is generated to comply with the serving PLMN policy provided by the wireless communication network. The rate indicated in the NAS procedure applies to the PDU session corresponding to the NAS procedure, and the indicated rate remains valid until the PDU session is released.

[0113] In addition, PUSCH repetition in CIoT can be configured in Coverage Enhancement (CE) Mode B, which has up to 15dB coverage enhancement with reference to UE Category 1 coverage enhancement. The transmission power of both the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH) is set to MAX. Since the power is unchanged (i.e., no power control is performed), DCI formats 6-0B and 6-1B do not carry the TPC (Transmit Power Control) field.

[0114] In specification 3GPP 36.213, 8.0, the UE (100) procedures for sending PUSCH are provided in Table 1: ie, PUSCH repetition level (DCI format 6-0B).

[0115] Table 1

[0116]

[0117] If the UE (100) operates in CE mode B, the wireless communication network configures a maximum of 2048 repetitions.

[0118] refer to Figure 4A , consider that 500MB of CIoT user data needs to be sent to the wireless communication network in connected mode. At step 1, UE (100) initiates the transmission of multiple UL NAS transmission messages, which encapsulate the CIoT small data container carrying the CIoT user data. However, the bandwidth available for the uplink (UL) in narrowband IoT (NB-IoT) is very small, for example 200KHz. Therefore, the maximum amount of CIoT user data that can be sent in the CIoT small data container is 254 bytes. In addition, in order to send 500MB of CIoT user data, the CIoT user data is split into multiple fragments so that the CIoT user data can be encapsulated in the CIoT small data container. In addition, the encapsulated data is sent to the wireless communication network in the form of multiple UL NAS transmission messages over a long duration (step 2).

[0119] At step 3, a NAS signaling message is triggered in view of a registration request to be sent, for example due to a UE capability update. In addition, as in step 4, unless all UL NAS transport messages are sent, the NAS signaling message cannot be sent to the wireless communication network. Due to the transmission of the UL NAS transport messages, a considerable delay is witnessed in the transmission of the NAS signaling message, resulting in the registration process failing and the UE (100) being deregistered (step 5). The delay becomes worse in the case where the serving PLMN rate control and 3GPP enhanced coverage functions are enabled in the UE (100) and the AMF (1000). When the serving PLMN rate control is enabled, the UE (100) limits the generation rate of uplink control plane user data to comply with the PLMN rate control policy provided by the wireless communication network. When the wireless communication network has enabled 3GPP enhanced coverage (CE mode B), the maximum number of repeated PUSCH transmissions can be 2048 in the worst case, which further increases the delay of the NAS signaling message transmission.

[0120] Figure 4BA scenario is shown in which NAS signaling message transmission is prioritized over CIoT user data transmission by UE (100) in a 5G communication network according to an embodiment disclosed herein.

[0121] Combination Figure 4A And refer to Figure 4B , Figure 4B Steps 1 to 3 in Figure 4A Steps 1 to 3 in are basically the same, so repeated descriptions are omitted.

[0122] At step 4, the UE (100) prioritizes NAS signaling messages such as registration requests due to UE capability updates, TAU updates, authentication, etc. over UL NAS transmission messages used to send CIoT user data to the wireless communication network. The UE (100) provides higher priority for NAS signaling messages by generating two queues in the NAS layer between the UE (100) and the wireless communication network. The first queue includes NAS signaling messages that have not been transmitted to the wireless communication network, and the second queue includes UL NAS transmission messages. Whenever the UE (100) needs to transmit a UL NAS transmission message, the UE (100) checks whether there is any untransmitted content in the first queue, and prioritizes the content in the first queue for transmission over the content in the second queue.

[0123] Therefore, unlike conventional methods and systems that cause a delay in the transmission of a NAS signaling message in the transmission of a UL NAS transport message, the proposed method ensures that the NAS signaling message is transmitted before the UL NAS transport message.

[0124] Figure 5A The present invention shows a scenario in which NAS signaling message transmission fails due to UE (100) transmitting a large amount of CIoT user data in a 4G communication network according to the prior art.

[0125] Combination Figure 4A And refer to Figure 5A ,about Figure 4A The described problems are highlighted from the perspective of 5G communication networks. However, similar problems may occur with respect to 4G communication networks using ESM DATA TRANSPORT messages to transmit control plane user data.

[0126] At step 1, UE (100) initiates transmission of multiple ESM DATA TRANSPORT messages for transmission of control plane user data. In addition, encapsulated control plane user data is sent to the wireless communication network in multiple ESM DATA TRANSPORT messages over a long duration (step 2).

[0127] At step 3, a NAS signaling message is triggered in view of a TAU update, for example due to a UE capability update. In addition, as in step 4, unless all ESM DATA TRANSPORT messages have been sent, the NAS signaling message cannot be sent to the wireless communication network. Due to the transmission of the ESM DATA TRANSPORT messages, a considerable delay is witnessed in the transmission of the NAS signaling message, resulting in the TAU procedure failing and the UE (100) being deregistered (step 5). The delay becomes worse in the case where the serving PLMN rate control and 3GPP enhanced coverage functions are enabled in the UE (100) and the AMF (1000). When the serving PLMN rate control is enabled, the UE (100) limits the generation rate of uplink control plane user data to comply with the PLMN rate control policy provided by the wireless communication network. When the wireless communication network has enabled 3GPP enhanced coverage (CE mode B), the maximum number of repeated PUSCH transmissions can be 2048 in the worst case, which further increases the delay in the transmission of the NAS signaling message.

[0128] Figure 5B A scenario is shown in which NAS signaling message transmission is prioritized over CIoT user data transmission by UE (100) in a 4G communication network according to an embodiment disclosed herein.

[0129] Combination Figure 5A And refer to Figure 5B , Figure 5B Steps 1 to 3 in Figure 5A Steps 1 to 3 in are basically the same, so repeated descriptions are omitted.

[0130] At step 4, the UE (100) prioritizes NAS signaling messages such as registration requests due to UE capability updates, TAU updates, authentication, etc. over ESM DATA TRANSPORT messages used to send CIoT user data to the wireless communication network. The UE (100) provides a higher priority for NAS signaling messages by generating two queues in the NAS layer between the UE (100) and the wireless communication network. The first queue includes NAS signaling messages to be transmitted to the wireless communication network, and the second queue includes ESM DATA TRANSPORT messages. Whenever the UE (100) needs to transmit an UL NAS transmission message, the UE (100) checks whether there is any untransmitted content in the first queue, and prioritizes the content in the first queue for transmission over the content in the second queue. Therefore, the proposed method ensures that the NAS signaling message is transmitted before the ESM DATA TRANSPORT message.

[0131] Fig. 6Ais a signaling diagram showing a failure in NAS signaling message transmission due to a UE (100) sending a large amount of CIoT user data in a 5G communication network according to the prior art.

[0132] refer to Fig. 6A At step 1, consider a large amount of CIoT user data (e.g., 500MB) transmission triggered by a UE (100). At step 2, multiple UL NAS transmission messages are triggered to send untransmitted UL NAS transmission messages in the multiple UL NAS transmission messages (as shown in steps 2a to 2n). In addition, if the wireless communication network enables at least one of the serving PLMN data control and the 3GPP enhanced coverage feature, the amount of time taken to complete the transmission of the multiple UL NAS transmission messages will increase.

[0133] At step 3, for example, due to a registration request caused by a UE capability update, the UE (100) triggers NAS signaling, and the UE (100) also activates the T3510 (15s+240s) timer (step 4). In addition, at step 5, the UE (100) does not send a NAS signaling message until multiple UL NAS transmission messages are completely transmitted to the wireless communication network, so at step 6, the T3510 timer expires. Since the transmission of CIoT user data is not completed within the expiration of the T3510 timer, the registration update fails. Therefore, in conventional methods and systems, the delay in the complete transmission of multiple UL NAS transmission messages causes the NAS signaling message to not be delivered to the wireless communication network, which may result in various consequences such as a registration update failure at the wireless communication network.

[0134] Figure 6Ba and Figure 6Bb is a signaling diagram showing prioritizing NAS signaling messages over CIoT user data by a UE (100) in a 5G communication network according to an embodiment disclosed herein.

[0135] refer to Figure 6Ba At step 1, the UE (100) generates two queues at the NAS layer between the UE (100) and the 5G communication network. The first queue is generated to store untransmitted NAS signaling messages, and the second queue is generated to store untransmitted control plane user data.

[0136] At step 2, the UE (100) triggers the transmission of a large amount of CIoT user data, for example, 500MB of CIoT user data. The UE (100) determines whether the first queue includes at least one NAS signaling message. When it is determined that the first queue does not include at least one NAS signaling message, at step 3, the UE (100) sends an UL NAS transmission message carrying "User Data 1" that has not been transmitted in the second queue. The control plane user data "User Data 2" is the next available control plane user data in the second queue, as described in step 4.

[0137] At step 5, the UE (100) determines that the triggering NAS signaling is, for example, a registration request due to a UE capability update, and at step 6, the UE (100) activates a T3510 (15s+240s) timer. In addition, at step 7, before transmission of the next available UL NAS transmission message in the second queue, the UE (100) determines whether the first queue includes at least one NAS signaling message. Upon determining that the first queue includes at least one NAS signaling message for registration due to a UE capability update, at step 8, the UE (100) initiates a registration update procedure by sending a NAS signaling message (registration request message) from the first queue to the wireless communication network (step 9).

[0138] refer to Figure 6Bb At step 10, the UE (100) receives a registration accept message from the wireless communication network when the registration process is successfully completed. In addition, the registration accept message is received by the UE (100) before the T3510 (15s+240s) timer expires (step 11).

[0139] At step 12, the UE (100) determines whether the first queue includes at least one NAS signaling message before transmitting the next available UL NAS transmission message in the second queue. When it is determined that the first queue does not include at least one NAS signaling message, at step 13, the UE (100) sends an UL NAS transmission message carrying "User Data 2" from the second queue. The control plane user data "User Data 3" is the next available control plane user data in the second queue, as described in step 14.

[0140] Fig. 7A 1 is a signaling diagram showing a failure in NAS signaling message transmission due to a UE (100) transmitting a large amount of CIoT user data in a 4G communication network according to the prior art.

[0141] refer to Fig. 7AAt step 1, consider a large amount of CIoT user data (e.g., 500MB) transmission triggered by a UE (100). At step 2, multiple ESM DATA TRANSPORT messages are triggered to send untransmitted ESM DATA TRANSPORT messages in the multiple ESM DATA TRANSPORT messages (as shown in steps 2a to 2n). In addition, if the wireless communication network enables at least one of the serving PLMN data control and the 3GPP enhanced coverage feature, the amount of time taken to complete the transmission of the multiple ESM DATA TRANSPORT messages will increase.

[0142] At step 3, for example, a TAU request due to a UE capability update, the UE (100) triggers NAS signaling and also activates a T3430 (15s+240s) timer (step 4). In addition, at step 5, no NAS signaling message is sent until the multiple ESM DATA TRANSPORT messages are completely transmitted to the wireless communication network, and at step 6, the T3430 timer expires. At step 7, if the transmission of the multiple ESM DATA TRANSPORT messages is not completed within the expiration of the T3430 timer, the TAU fails.

[0143] Figure 7Ba and Figure 7Bb is a signaling diagram showing prioritization of NAS signaling messages over CIoT user data by a UE (100) in a 4G communication network according to an embodiment disclosed herein.

[0144] refer to Figure 7Ba At step 1, the UE (100) generates two queues at the NAS layer between the UE (100) and the 4G communication network. The first queue is generated to store untransmitted NAS signaling messages, and the second queue is generated to store untransmitted control plane user data.

[0145] At step 2, the UE (100) triggers the transmission of a large amount of CIoT user data, such as 500MB of CIoT user data. The UE (100) determines whether the first queue includes at least one NAS signaling message before transmitting the CIoT user data. When it is determined that the first queue does not include at least one NAS signaling message, at step 3, the UE (100) sends an ESM DATA TRANSPORT message carrying "User Data 1" that has not been transmitted in the second queue. The control plane user data "User Data 2" is the next available control plane user data in the second queue, as described in step 4.

[0146] At step 5, the UE (100) determines that NAS signaling is triggered, for example, due to a UE capability update causing a TAU to be performed, and at step 6, the UE (100) activates a T3430 (15s+240s) timer. In addition, at step 7, before transmission of the next available ESM DATA TRANSPORT message in the second queue, the UE (100) determines whether the first queue includes at least one NAS signaling message. Upon determining that the first queue includes at least one NAS signaling message (i.e., a TAU request message for performing a TAU due to a UE capability update), at step 8, the UE (100) prioritizes the first queue over the second queue and initiates a TAU update procedure by transmitting a NAS signaling message (i.e., a TAU request message) from the first queue to the 4G communication network (step 9).

[0147] refer to Figure 7Bb At step 10, the UE (100) receives a TAU accept message from the 4G communication network when the TAU procedure is successfully completed. In addition, the TAU accept message is received by the UE (100) before the T3430 (15s+240s) timer expires (step 11).

[0148] At step 12, the UE (100) determines whether the first queue includes at least one NAS signaling message to be transmitted to the 4G communication network before transmitting the next available ESM DATA TRANSPORT message in the second queue. When it is determined that the first queue does not include at least one NAS signaling message, at step 13, the UE (100) sends an ESM DATA TRANSPORT message carrying "User Data 2" from the second queue. The control plane user data "User Data 3" is the next available control plane user data in the second queue, as described in step 14.

[0149] Therefore, unlike conventional methods and systems, in the proposed method, the UE (100) checks whether the NAS signaling message has not been sent before sending each ESMDATA TRANSPORT message, and sends the NAS signaling message first if the NAS signaling message has not been transmitted. Therefore, significant delay in the transmission of the NAS signaling message is avoided.

[0150] The embodiments disclosed herein may be implemented by at least one software program running on at least one hardware device and performing network management functions to control the elements. Figures 1A to 7Bb The elements shown in the drawings include blocks, elements, actions, behaviors, steps, etc., which may be at least one of a hardware device or a combination of a hardware device and a software module.

[0151] The foregoing description of specific embodiments will fully reveal the general nature of the embodiments herein, so that others can easily modify and / or adapt various applications such as these specific embodiments by applying current knowledge without separating the general concepts, and therefore, such adaptations and modifications should and are intended to be understood as belonging to the meaning and scope of the equivalent forms of the disclosed embodiments. It should be understood that the words or terms used herein are for descriptive purposes and not limiting. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the spirit and scope of the embodiments described herein.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method comprising: Sending a Registration Request message for mobility or periodic registration update to the Access and Mobility Management Function (AMF); as well as receiving, before completing the registration procedure for the mobility or the periodic registration update based on the registration request, a deregistration request message for a deregistration procedure from the AMF, Wherein, in a case where the deregistration request message includes a specific cause value, the registration process for the mobility or the periodic registration update is performed and the deregistration process is terminated, Among them, the specific cause value is at least one of the fifth generation system mobility management 5GMM cause values ​​#11, #12, #13 or #15.

2. The method according to claim 1, in, In a case where the specific cause value is not included in the deregistration request message, the registration procedure for the mobility or the periodic registration update is aborted and the deregistration procedure is performed.

3. The method according to claim 1, in, The 5GMM cause value #11 corresponds to information associated with not being allowed to use the public land mobile network PLMN; The 5GMM cause value #12 corresponds to information associated with a tracking area not allowed; The 5GMM cause value #13 corresponds to information associated with roaming not being allowed in a tracking area; and The 5GMM cause value #15 corresponds to information associated with no suitable cell in the tracking area.

4. A method performed by an access and mobility management function (AMF) in a wireless communication system, the method comprising: Sending a deregistration request message for a deregistration process to a user equipment UE; as well as before completing the deregistration procedure based on the deregistration request message, receiving a registration request message for mobility or periodic registration update from the UE, Wherein, in a case where the deregistration request message includes a specific cause value, the deregistration process is terminated and a registration process for the mobility or the periodic registration update is performed, Among them, the specific cause value is at least one of the fifth generation system mobility management 5GMM cause values ​​#11, #12, #13 or #15.

5. The method according to claim 4, in, In a case where the deregistration request message does not include the specific cause value, the registration procedure for the mobility or the periodic registration update is aborted, and the deregistration procedure is performed.

6. The method according to claim 4, in, The 5GMM cause value #11 corresponds to information associated with not being allowed to use the public land mobile network PLMN; The 5GMM cause value #12 corresponds to information associated with a tracking area not allowed; The 5GMM cause value #13 corresponds to information associated with roaming not being allowed in a tracking area; and The 5GMM cause value #15 corresponds to information associated with no suitable cell in the tracking area.

7. A user equipment UE in a wireless communication system, the UE comprising: Transceiver; as well as Processor, configured as: sending, via the transceiver, a registration request message for mobility or periodic registration update to an access and mobility management function, AMF; as well as receiving, before completing the registration procedure for the mobility or the periodic registration update based on the registration request, a deregistration request message for a deregistration procedure from the AMF, Wherein, in a case where the deregistration request message includes a specific cause value, the registration process for the mobility or the periodic registration update is performed and the deregistration process is terminated, Among them, the specific cause value is at least one of the fifth generation system mobility management 5GMM cause values ​​#11, #12, #13 or #15.

8. The UE according to claim 7, in, In a case where the specific cause value is not included in the deregistration request message, the registration procedure for the mobility or the periodic registration update is aborted and the deregistration procedure is performed.

9. The UE according to claim 7, in, The 5GMM cause value #11 corresponds to information associated with not being allowed to use the public land mobile network PLMN; The 5GMM cause value #12 corresponds to information associated with a tracking area not allowed; The 5GMM cause value #13 corresponds to information associated with roaming not being allowed in a tracking area; and The 5GMM cause value #15 corresponds to information associated with no suitable cell in the tracking area.

10. An access and mobility management function AMF in a wireless communication system, the AMF comprising: Transceiver; as well as Processor, configured as: Sending a deregistration request message for a deregistration procedure to a user equipment UE via the transceiver; as well as before completing the deregistration procedure based on the deregistration request message, receiving a registration request message for mobility or periodic registration update from the UE, Wherein, in a case where the deregistration request message includes a specific cause value, the deregistration process is terminated and a registration process for the mobility or the periodic registration update is performed, Among them, the specific cause value is at least one of the fifth generation system mobility management 5GMM cause values ​​#11, #12, #13 or #15.

11. The AMF according to claim 10, in, In a case where the deregistration request message does not include the specific cause value, the registration procedure for the mobility or the periodic registration update is aborted, and the deregistration procedure is performed.

12. The AMF according to claim 10, in, The 5GMM cause value #11 corresponds to information associated with not being allowed to use the public land mobile network PLMN; The 5GMM cause value #12 corresponds to information associated with a tracking area not allowed; The 5GMM cause value #13 corresponds to information associated with roaming not being allowed in a tracking area; and The 5GMM cause value #15 corresponds to information associated with no suitable cell in the tracking area.

Images