Method and apparatus for handling a session in a wireless communication system

Abstract

Accordingly, the embodiments disclosed herein disclose a method performed by a user equipment (UE) in a wireless communication system. The method includes receiving a non-access stratum (NAS) message from an access and mobility management function (AMF), wherein the non-access stratum (NAS) message includes information indicating whether the UE is registered for emergency services and determining registration for emergency services based on the NAS message.

Description

Technical Field

[0001] The present invention relates to a wireless communication network, and more particularly, to a method and a user equipment (UE) for processing a protocol data unit (PDU) session when multiple PDU sessions are released in the wireless communication network. Background Art

[0002] To meet the increased demand for wireless data traffic since the deployment of the fourth generation (4G) communication system, efforts have been made to develop improved fifth generation (5G) or pre-5G communication systems. 5G or pre-5G communication systems are also referred to as "beyond 4G networks" or "post long term evolution (LTE) systems". 5G communication systems are considered to be implemented in higher (millimeter wave) frequency bands, such as the 60GHz band, to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-size MIMO (FD-MIMO), array antennas, analog beamforming and massive antenna technology are discussed for 5G communication systems. In addition, in 5G communication systems, improvements and developments are being made based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, system networks, collaborative communications, collaborative multi-point (CoMP), receiving end interference elimination, etc.

[0003] In 5G systems, hybrid frequency shift keying (FSK) and Feher's quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code division multiple access (SCMA) as advanced access technologies.

[0004] The Internet is a human-centered connected network in which people generate and consume information. Today, the Internet is developing into the Internet of Things (IoT), in which distributed entities (such as objects) exchange and process information without human intervention. The Internet of Everything (IoE) has now emerged, which is a combination of IoT technology and big data processing technology realized by connecting to cloud servers. Since technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" have been required for IoT implementation, 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 objects. Through the integration and combination between existing information technology (IT) and various industrial technologies, IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances and advanced medical services.

[0005] Accordingly, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud RAN, which is the above-mentioned big data processing technology, can also be considered as an example of the fusion between 5G technology and IoT technology.

[0006] As described above, various services can be provided according to the development of wireless communication systems, and thus a method for easily providing such services is required.

[0007] The above information is presented as background information only to assist in understanding the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above may be applicable as prior art in the field of the present disclosure. Summary of the invention

[0008] Technical issues

[0009] Accordingly, the embodiments disclosed herein disclose a method performed by a user equipment (UE) in a wireless communication system. The method includes receiving a non-access stratum (NAS) message from an access and mobility management function (AMF), wherein the non-access stratum (NAS) message includes information indicating whether the UE is registered for emergency services, and determining registration for emergency services based on the NAS message. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The method and UE are illustrated in the accompanying drawings, where the same reference letters indicate corresponding parts in the various drawings. The embodiments of the present invention will be better understood from the following description with reference to the accompanying drawings, wherein:

[0011] Figure 1 is a timing diagram showing a UE for processing a PDU session when an SMF entity sends a release PDU session request to an AMF entity according to the prior art;

[0012] Figure 2 is a timing diagram showing a UE for processing a PDU session based on a deregistration notification according to the prior art;

[0013] Figure 3 is an overview diagram of a system for processing a PDU session according to an embodiment disclosed herein.

[0014] Figure 4 Various hardware components of a UE for processing a PDU session according to the embodiments disclosed herein are shown;

[0015] Figure 5 is a flowchart illustrating a method for processing a PDU session according to an embodiment of the present disclosure.

[0016] Figure 6 is a timing diagram illustrating a UE for processing a PDU session when an AMF entity sends a NAS message indicating at least one UE registered for emergency services according to an embodiment disclosed herein;

[0017] Figure 7 is a timing diagram illustrating a UE for handling a PDU session when an AMF entity sends a NAS message indicating at least one UE registered for emergency services and the UE moves from a normal area to an emergency area according to an embodiment disclosed herein;

[0018] Figure 8 is another sequence diagram illustrating a UE for handling a PDU session when the UE attempts to trigger a non-emergency service and the AMF entity sends a NAS message indicating at least one UE registered for emergency services according to embodiments disclosed herein;

[0019] Fig. 9 is another sequence diagram illustrating a UE for handling a PDU session when an AMF entity indicates that the UE is registered for at least one emergency service as part of a PDU session release procedure according to embodiments disclosed herein;

[0020] Fig.10 Schematically illustrates a network entity according to an embodiment of the present disclosure; and

[0021] Fig.11A user equipment (UE) according to an embodiment of the present disclosure is schematically illustrated.

[0022] Throughout the drawings, like reference numerals will be understood to refer to like parts, components, and structures. DETAILED DESCRIPTION

[0023] Best Mode

[0024] Accordingly, embodiments herein disclose a method for processing a PDU session by a UE. The method includes receiving, by the UE, a NAS message from a network entity. The NAS message indicates that the UE is registered for emergency services. In addition, the method includes performing an action by the UE in response to receiving a NAS message indicating that the UE is registered for emergency services. The action includes at least one of the following: registering the UE with the network entity for at least one emergency service, locally releasing a PDU session corresponding to an ongoing normal service, and avoiding requesting a normal service from the network entity.

[0025] In one embodiment, receiving, by the UE, a NAS message from a network entity includes detecting, by the network entity, at least one of the following items: the UE moves from a normal area to a restricted area, the current registration area of ​​the UE is converted to a restricted area, the UE initiates a registration process in an area where normal services are not allowed to be received, and receiving, by the UE, a NAS message from the network entity based on the detection.

[0026] In one embodiment, the NAS message is at least one of a UE configuration update message and a registration accept message.

[0027] In one embodiment, the network entity is an AMF entity.

[0028] Accordingly, an embodiment of the present invention discloses a UE for processing a PDU session. The UE includes a processor coupled to a memory. The processor is configured to receive a NAS message from a network entity. The NAS message indicates that the UE is registered for emergency services. The processor is configured to perform an action in response to receiving a NAS message indicating that the UE is registered for emergency services. The action includes at least one of the following items: registering the UE with the network entity for at least one emergency service, locally releasing a PDU session corresponding to an ongoing normal service, and avoiding requesting a normal service from the network entity.

[0029] Accordingly, the embodiments disclosed herein disclose a method performed by a user equipment (UE) in a wireless communication system. The method may include receiving a non-access stratum (NAS) message from an access and mobility management function (AMF), wherein the non-access stratum (NAS) message includes information indicating whether the UE is registered for emergency services. In addition, the method may include determining registration for emergency services based on the NAS message.

[0030] In one embodiment, the method further comprises: when the information indicates that the UE is registered for emergency services, determining to register the UE for emergency services.

[0031] In one embodiment, the method further comprises: when the information indicates that the UE is registered for emergency services, releasing a protocol data unit (PDU) session not associated with the emergency services.

[0032] In one embodiment, the UE is not currently registered for emergency services.

[0033] Accordingly, the embodiments herein disclose a method performed by an access and mobility management function (AMF) in a wireless communication system. The method includes: sending a non-access stratum (NAS) message to a user equipment (UE), wherein the non-access stratum (NAS) message includes information indicating whether the UE is registered for emergency services, and whether the UE is registered for emergency services is determined based on the NAS message.

[0034] These and other aspects of the embodiments herein will be better understood and appreciated when considered in conjunction with the following description and accompanying drawings. It should be understood, however, that the following description, although indicating preferred embodiments and many of their specific details, is given by way of illustration and not limitation. Various changes and modifications may be made within the scope of the present embodiments without departing from the spirit of the embodiments herein, and embodiments of the present invention include all such modifications.

[0035] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout the disclosure. The terms "include" and "comprising" and their derivatives are meant to include, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean to include, be included, interconnected with, contain, be contained within, connect to or be connected with, be coupled to or coupled with, be communicative with, cooperate with, interleave, juxtapose, be in proximity to, be combined with or be combined with, have, possess, and the like; and the term "controller" refers to any device, system, or portion thereof that controls at least one operation, which may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0036] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and implemented in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, programs, functions, objects, classes, instances, related data or a part thereof that are suitable for implementation with appropriate computer-readable program codes. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD) or any other type of memory. "Non-transient" computer-readable media does not include wired, wireless, optical or other communication links that transmit transient electrical signals or other signals. Non-transient computer-readable media include media that can permanently store data and media that can store data and overwrite data afterwards, such as rewritable optical discs or erasable storage devices.

[0037] Definitions for certain words and phrases are provided in this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of the defined words and phrases.

[0038] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout the disclosure. The terms "include" and "comprising" and their derivatives are meant to include, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean to include, be included in, interconnect with, contain, be contained in, connect to or be connected with, be coupled to or coupled with, be communicative with, cooperate with, interleave, juxtapose, be close to, be combined with or be combined with, have, possess, and the like; and the term "controller" refers to any device, system, or part thereof that controls at least one operation, which may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0039] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and implemented in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, programs, functions, objects, classes, instances, related data or a part thereof that are suitable for implementation with appropriate computer-readable program codes. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD) or any other type of memory. "Non-transient" computer-readable media does not include wired, wireless, optical or other communication links that transmit transient electrical signals or other signals. Non-transient computer-readable media include media that can permanently store data and media that can store data and overwrite data afterwards, such as rewritable optical discs or erasable storage devices.

[0040] Definitions for certain words and phrases are provided in this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of the defined words and phrases.

[0041] Invention Mode

[0042] Discussed below Figures 1 to 11 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustrative purposes only and should not be considered to limit the scope of the present disclosure in any way. Those skilled in the art should understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0043] The embodiments herein 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 following description. The description of well-known components and processing techniques is omitted herein to avoid unnecessary confusion of the embodiments herein. In addition, the various embodiments described herein are not necessarily mutually exclusive, because some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise stated, the term "or" used herein refers to a non-exclusive "or". The examples used herein are intended only to promote the understanding of the ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be interpreted as limiting the scope of the embodiments herein.

[0044] As a conventional practice in the field, the embodiment can be described and illustrated according to the square frame of performing one or more functions described. These square frames can be referred to as units or modules in this article, etc., and are implemented in physical form by analog 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 can be optionally driven by firmware and software. For example, the circuit can be implemented in one or more semiconductor chips, or located on substrate supports such as printed circuit boards, etc. The circuit constituting the square frame can be implemented by dedicated hardware or by a processor (for example, one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware for performing some functions of the square frame and a processor for performing other functions of the square frame. Without departing from the scope of the present invention, each square frame of the embodiment can be physically separated into two or more interacting and discrete square frames. Similarly, without departing from the scope of the present invention, the square frame of the embodiment can be physically combined into more complex square frames.

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

[0046] In this disclosure, whenever it is mentioned that the UE should consider itself registered only for emergency services, it implicitly means that the UE should locally release all non-emergency bearers that have not been explicitly deactivated by the network. In other words, the UE locally releases the PDU session corresponding to the ongoing normal service. The term locally indicates that the UE will release the PDU session without peer to peer signaling between the UE and the network. That is, the UE (100) will locally release the PDU session without performing the PDU session release procedure.

[0047] Accordingly, embodiments herein disclose a method for processing a PDU session by a UE. The method includes receiving, by the UE, a NAS message from a network entity. The NAS message indicates that the UE is registered for emergency services. In addition, the method includes performing an action by the UE in response to receiving a NAS message indicating that the UE is registered for emergency services. The action includes at least one of the following: registering the UE with the network entity for at least one emergency service, locally releasing a PDU session corresponding to an ongoing normal service, and avoiding requesting a normal service from the network entity.

[0048] Unlike conventional methods and systems, in the proposed method, the AMF entity indicates to the UE in the NAS message that the UE is registered only for emergency services. Based on this indication, the UE continues to remain registered, but only for emergency services, and the UE should not initiate any non-emergency related services. This avoids wasting network resources.

[0049] According to the present disclosure, the UE does not need to be in a normal service state. That is, in the prior art, it is not possible to receive an indication ("registering for emergency services") during the registration process (i.e., in the prior art, receiving the indication is only applicable after the registration process). However, according to the present disclosure, it is allowed to receive the indication during the registration process.

[0050] According to the present disclosure, at least one emergency PDU session is not required. That is, the method and apparatus disclosed in the present disclosure do not consider retaining the existing emergency PDU session.

[0051] According to the present disclosure, the methods and apparatus disclosed in the present disclosure do not rely on the expiration of a subscription.

[0052] Network accepted mobility and periodic registration updates: If the UE is not currently registered for emergency services and the 5GS Registration Result IE value in the REGISTRATION ACCEPT message is set to "Registered for emergency services", the UE shall consider itself registered for emergency services and shall locally release PDU Session(s) not associated with emergency services (if any).

[0053] Generic UE Configuration Update Accepted by UE: If the UE is not currently registered for emergency services and the 5GS Registration Result IE in the CONFIGURATION UPDATE COMMAND message is set to "Registered for Emergency Services", the UE shall consider itself registered for emergency services.

[0054] The main purpose of the embodiments herein is to provide a method and UE for handling a PDU session when multiple PDU sessions are released in a wireless communication network.

[0055] Referring now to the drawings, and more particularly to the Figures 1 to 11 , in which a preferred embodiment is shown.

[0056] Figure 1 It is a timing diagram showing a UE (100) for processing a PDU session when a session management function (SMF) entity (250) sends a release PDU session request to an access and mobility management function (AMF) entity (200).

[0057] Assume that: UE (100) is registered with the network. UE (100) is having "n" number of active PDU sessions and an active emergency PDU session. The SMF entity (250) initiates a PDU session release procedure for the UE (100). In one example, in S102, the SMF entity (250) sends a release PDU session request to the AMF entity (200). Based on receiving the release PDU session request from the SMF entity (250), in S104, the AMF entity (200) releases all applicable PDU sessions except the emergency PDU session. After releasing all PDU sessions except the emergency PDU session, in S106, the UE (100) then uses an uplink (UL) non-access stratum (NAS) transport message to establish a new PDU session or SMS, etc. (i.e., the UE (100) attempts to trigger a non-emergency service). Based on the UL NAS TRANSPORT message, in S108, the AMF entity (200) processes the new request (i.e., the AMF entity (200) can process the SMS request or the new PDU session establishment request, etc. without causing any problems.

[0058] Figure 2 is a sequence diagram showing a UE (100) for handling a PDU session based on a deregistration notification according to the prior art.

[0059] Assume that the UE (100) is registered with the network. The UE (100) has "n" number of active PDU sessions and an active emergency PDU session.

[0060] The AMF entity (200) may decide to deregister the UE (100) based on receiving a deregistration notification from other entities in the wireless communication network or UE mobility. In S202, the AMF entity (200) releases all PDU sessions except emergency PDU sessions. In S204, the UE (100) sends a UL NAS TRANSPORT message to the AMF entity (200) to establish a new PDU session or SMS (i.e., the UE (100) triggers a non-emergency service). After receiving the UL NAS TRANSPORT message from the UE (100), in S206, the AMF entity (200) cannot process the request because the UE (100) is in an emergency registration-only state. In S208a, S208b, S208c, the AMF entity (200) cannot use the existing rejection cause to indicate this to the UE (100) because the existing rejection cause will affect the emergency services (i.e., if the NAS message is rejected, the UE (100) will enter the deregistered state and affect the emergency services).

[0061] In addition, the UE (100) will continue to send uplink requests when the retry timer expires, but the AMF entity (200) cannot process the request. This will continue to happen and affect network resources.

[0062] based on Figure 1 and Figure 2 , when all PDU sessions are released from the UE (100), the UE (100) is not aware of the purpose of releasing all PDU sessions.

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

[0064] Figure 3 is an overview diagram of a system (300) for processing a PDU session according to an embodiment disclosed herein.

[0065] In one embodiment, the system (300) includes a UE (100) and an AMF entity (200). The UE (100) may be, for example but not limited to, a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a tablet computer, a laptop computer, an Internet of Things (IoT), a virtual reality device, a smart watch, etc.

[0066] Assume that the UE (100) is registered with the network. The UE (100) has "n" number of active PDU sessions and the UE (100) also has an active emergency PDU session.

[0067] In the present disclosure, "n" number of PDU sessions may mean at least one PDU session. For example, the number of PDU sessions may be 2. For example, the number of PDU sessions may be more than 2.

[0068] In one embodiment, the UE (100) moves from a normal area to a prohibited area or an emergency area. The AMF entity (200) deregisters the UE (100). Based on receiving a DeregistrationNotification from other entities in the wireless communication network or the AMF entity (200) itself identifying that the UE has entered a prohibited area or an emergency area or a non-permitted area, etc., the AMF entity (200) releases all PDU sessions except the emergency PDU session. The AMF entity (200) sends a NAS message (e.g., UE configuration update, etc.) to the UE (100). The NAS message includes an information element (IE) indicating that the UE (100) is registered for emergency services. When the UE (100) receives a NAS message including an IE indicating that the UE (100) is registered for emergency services, the UE (100) should regard itself as registered only for emergency services, locally release all PDU sessions not related to emergency services, and should not initiate normal services, such as new PDU sessions (related to normal services).

[0069] In another embodiment, based on receiving a deregistration notification or the AMF entity (200) itself identifying that the UE (100) has entered a prohibited area, an emergency area, a non-allowed area, etc., the AMF entity (200) releases all PDU sessions except the emergency PDU session. The UE (100) triggers the establishment of a new PDU session or SMS using an UL NAS TRANSPORT message (i.e., the UE (100) attempts to trigger a non-emergency service). The AMF entity (200) sends a NAS message (e.g., a DL NAS transport message, etc.) to the UE (100). The NAS message includes an information element (IE) indicating that the UE (100) is registered for this emergency service. When the UE (100) receives a NAS message including an IE indicating that the UE (100) is registered for emergency services, all PDU sessions not related to emergency services are released locally, and the UE (100) should regard itself as registered only for emergency services, and should not initiate normal services, such as new PDU sessions (related to normal services).

[0070] In another embodiment, based on receiving a deregistration notification or the AMF entity (200) itself identifying that the UE (100) has entered a prohibited area, an emergency area, a non-allowed area, etc., the AMF entity (200) releases all PDU sessions except the emergency PDU session. As part of the PDU session release process, the AMF entity (200) sends an IE indicating that the UE (100) is registered for emergency services. When the UE (100) receives a NAS message including an IE indicating that the UE (100) is registered for emergency services, all PDU sessions not related to emergency services are released locally, and the UE (100) should regard itself as registered only for emergency services and should not initiate normal services, such as new PDU sessions (related to normal services).

[0071] Figure 4 Various hardware components of a UE (100) according to embodiments disclosed herein are shown.

[0072] In one embodiment, the UE (100) includes a processor (410), a communicator (420), a memory (430), a PDU session-based emergency service providing device (140), and a PDU session-based service ongoing processing device (150). The processor (410) is coupled with the communicator (420), the memory (430), the PDU session-based emergency service providing device (140), and the PDU session-based service ongoing processing device (150).

[0073] In one embodiment, the processor (410) is configured to receive a NAS message from a network entity (i.e., the AMF entity (200)). The NAS message indicates that the UE (100) is registered for emergency services. The NAS message may be, for example, but not limited to, a UE configuration update, a DL NAS transport message, a deregistration message, a registration acceptance message, etc.

[0074] In response to receiving a NAS message indicating registration of the UE (100) for emergency services, the PDU session based emergency service providing apparatus (140) is configured to register with a network entity for at least one emergency service.

[0075] In response to receiving a NAS message indicating that the UE (100) is registered for emergency services, a PDU session-based ongoing service processing device (150) is configured to locally release a PDU session corresponding to an ongoing normal service.

[0076] In response to receiving a NAS message indicating that the UE (100) is registered for emergency services, the PDU session based ongoing service processing means (1150) is configured to avoid requesting normal services from a network entity.

[0077] The processor (410) is configured to execute instructions stored in the memory (430) and perform various processes. The communicator (420) is configured to communicate internally between internal hardware components and to communicate with external devices via one or more networks.

[0078] In addition, the memory (430) also stores instructions to be executed by the processor (410). The memory (430) 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 an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory (430) may be regarded as a non-transient storage medium. The term "non-transient" may indicate that the storage medium is not implemented in a carrier or propagation signal. However, the term "non-transient" should not be interpreted as the memory (430) being non-removable. In some examples, the memory (430) may be configured to store a larger amount of information than the memory. In some examples, the non-transient storage medium may store data that can change over time (e.g., stored in a random access memory (RAM) or a cache).

[0079] although Figure 4 Various hardware components 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 components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present invention. One or more components may be combined together to perform the same or substantially similar functions to process a PDU session.

[0080] Figure 5 is a flow chart (S500) illustrating a method for handling a PDU session according to an embodiment disclosed herein. Operations (S502, S504a, S504b, S504c) are performed by a processor (410). In S502, the method includes receiving a NAS message from a network entity (i.e., an AMF entity (200)). The NAS message indicates that the UE (100) is registered for emergency services. In S504a, the method includes registering with the network entity for at least one emergency service in response to receiving a NAS message indicating that the UE (100) is registered for emergency services. In S504b, the method includes releasing a PDU session corresponding to an ongoing normal service in response to receiving a NAS message indicating that the UE (100) is registered for emergency services. In S504c, the method includes avoiding requesting normal services from the network entity in response to receiving a NAS message indicating that the UE (100) is registered for emergency services.

[0081] The various actions, operations, boxes, steps, etc. in the flow chart (S500) can be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some actions, operations, boxes, steps, etc. can be omitted, added, modified, skipped, etc. without departing from the scope of the present invention.

[0082] Figure 6 1 is a timing diagram illustrating a UE (100) for processing a PDU session when an AMF entity (200) sends a NAS message indicating at least one emergency service registered UE (100) according to an embodiment disclosed herein.

[0083] Assume that: UE (100) is registered with the network. UE (100) has "n" number of active PDU sessions and UE (100) also has an active emergency PDU session. Because UE (100) has entered a prohibited area, an emergency area, a non-allowed area, etc., a DeregistrationNotification is sent. Based on receiving a DeregistrationNotification from other entities in the wireless communication network or the AMF entity (200) itself identifying that UE (100) has entered a prohibited area, an emergency area, a non-allowed area, etc., the AMF entity (200) releases all PDU sessions except the emergency PDU session in S602. In S604, the AMF entity (200) sends a NAS message (e.g., UE configuration update, etc.) to the UE (100). The NAS message includes an information element (IE) indicating that the UE (100) is registered for this emergency service. In S606, when the UE (100) receives a NAS message including an IE indicating that the UE (100) is registered for emergency services, the UE (100) should regard itself as registered only for emergency services, locally release all PDU sessions not related to emergency services, and should not initiate normal services, such as new PDU sessions (related to normal services).

[0084] Figure 7 is a timing diagram showing a UE (100) for processing a PDU session when an AMF entity (200) sends a NAS message indicating that the UE (100) is registered for at least one emergency service and the UE (100) moves from a normal area to a prohibited area or an emergency area according to an embodiment disclosed herein.

[0085] Assume that: UE (100) is registered with the network. UE (100) has "n" number of active PDU sessions and UE (100) also has an active emergency PDU session. In S702, UE (100) moves from a normal area to a prohibited area or the current normal area is converted to a prohibited area. The AMF entity (200) receives the deregistration process of UE (100). Based on the received DeregistrationNotification, the AMF entity (200) itself recognizes that the UE (100) has entered a prohibited area or an emergency area or a non-allowed area, etc., and the AMF entity (200) releases all PDU sessions except the emergency PDU session in S704. In S706, the AMF entity (200) sends a NAS message (e.g., UE configuration update, etc.) to the UE (100). The NAS message includes an information element (IE) indicating that the UE (100) is registered for emergency services. In S708, when the UE (100) receives a NAS message including an IE indicating that the UE (100) is registered for emergency services, all PDU sessions not related to emergency services are released locally, the UE (100) should regard itself as registered only for emergency services, and should not initiate normal services, such as new PDU sessions (related to normal services).

[0086] Figure 7 The process in is also applicable when the current registration area of ​​the UE (100) is converted into a forbidden area, and the UE (100) initiates a registration process in an area where the area is not allowed to receive normal services.

[0087] Figure 8 is another timing diagram illustrating a UE (100) for processing a PDU session when the UE (100) attempts to trigger a non-emergency service and the AMF (200) entity sends a NAS message indicating that the UE (100) is registered for at least one emergency service according to an embodiment disclosed herein.

[0088] Assume that a UE (100) is registered with the network. The UE (100) has "n" number of active PDU sessions and an active emergency PDU session. The AMF entity (200) receives the deregistration process of the UE (100). Based on receiving a DeregistrationNotification from other entities in the wireless communication network or the AMF entity (200) itself identifying that the UE (100) has entered a prohibited area, an emergency area, a non-allowed area, etc., the AMF entity (200) releases all PDU sessions except the emergency PDU session in S802. In S804, the UE (100) uses a UL NAS TRANSPORT message to trigger the establishment of a new PDU session or SMS (i.e., the UE attempts to trigger a non-emergency service). In S806, the AMF entity (200) sends a NAS message (e.g., a DL NAS transport message, etc.) to the UE (100). The NAS message includes an information element (IE) indicating that the UE (100) is registered for this emergency service. In S808, when the UE (100) receives a NAS message including an IE indicating that the UE (100) is registered for emergency services, the UE (100) should regard itself as registered only for emergency services and should not initiate normal services, such as a new PDU session (related to normal services).

[0089] Fig. 9 is another sequence diagram illustrating the UE (100) handling a PDU session when the AMF entity (200) indicates that the UE (100) is registered for at least one emergency service as part of a PDU session release procedure according to an embodiment disclosed herein.

[0090] Assume that: UE (100) is registered with the network. UE (100) has "n" number of active PDU sessions and UE (100) also has an active emergency PDU session. The AMF entity (200) receives the deregistration process of UE (100). Based on receiving DeregistrationNotification from other entities in the wireless communication network or the AMF entity (200) itself identifying that UE (100) has entered a prohibited area or an emergency area or a non-allowed area, etc., the AMF entity (200) releases all PDU sessions except the emergency PDU session in S902. As part of the PDU session release process, the AMF entity (200) sends an IE indicating that UE (100) is registered for emergency services. In S904, when UE (100) receives a NAS message including an IE indicating that UE (100) is registered for emergency services, UE (100) should regard itself as registered only for emergency services and should not initiate normal services, such as new PDU sessions (related to normal services).

[0091] In yet another embodiment, when all normal PDU sessions are released by the network, the UE (100) may trigger a registration process with the network and in response to the registration message, the network may indicate to the UE (100) in a NAS message that the UE (100) is only registered for emergency services or that the UE (100) continues to be available for normal services.

[0092] In yet another embodiment, when the AMF entity (220) receives a UL NAS TRANSPORT with a message not for emergency services or SMS or control plane data, i.e. the UE (100) has triggered a procedure to initiate normal services, then if the AMF entity (200) is in an emergency registration state for that UE (100), the AMF entity (200) may ignore the message.

[0093] Assume that the AMF entity (200) initiates the deregistration process only after the wireless network initiates the deregistration process. This case should be considered as an example. This also applies to the case where other core network elements including the AMF entity (200) meet the triggering conditions for executing the deregistration process but cannot initiate the deregistration process due to at least one emergency PDU session being active.

[0094] Assumption: Whenever it is mentioned that the UE (100) should consider itself as registered only for emergency services, this implicitly means that the UE (100) should locally release all non-emergency bearers that have not been explicitly deactivated by the network, i.e. locally release the PDU sessions corresponding to ongoing normal services. The term locally means that the UE (100) will release the PDU sessions without peer to peer signaling between the UE and the network, i.e., the UE (100) will locally release the PDU sessions without performing the PDU session release procedure.

[0095] Fig.10 The network entities according to the embodiments of the present disclosure are schematically shown.

[0096] The network entity 100 may correspond to an AMF (eg, AMF entity 200).

[0097] Reference Fig.10 , the network entity 1000 may include a processor 1010, a transceiver 1020, and a memory 1030. However, all the components shown in the figure are not required. The network entity 1000 may be composed of Fig.10 The components shown in the figure may be implemented with more or fewer components. In addition, according to another embodiment, the processor 1010, the transceiver 1020, and the memory 1030 may be implemented as a single chip.

[0098] The above-mentioned components will now be described in detail.

[0099] The processor 1010 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. The operations of the network entity 1000 may be implemented by the processor 1010.

[0100] The transceiver 1020 may include an RF transmitter for up-converting and amplifying a transmitted signal, and an RF receiver for down-converting the frequency of a received signal. However, according to another embodiment, the transceiver 1020 may be implemented by more or fewer components than those shown in the components.

[0101] The transceiver 1020 may be connected to the processor 1010 and transmit and / or receive signals. The signals may include control information and data. In addition, the transceiver 1020 may receive signals through a wireless channel and output the signals to the processor 1010. The transceiver 1020 may transmit signals output from the processor 1010 through a wireless channel.

[0102] The memory 1030 may store control information or data included in a signal obtained by the network entity 1000. The memory 1030 may be connected to the processor 1010 and store at least one instruction or protocol or parameter for the proposed function, process and / or method. The memory 1030 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0103] In one embodiment, the transceiver 1020 may transmit at least one signal to a user equipment (UE) for selecting a plurality of non-CAG cells available in a location where the UE is located, and the plurality of non-CAG cells are connected to the UE based on the at least one signal and provide at least one emergency service to the UE.

[0104] In one embodiment, the transceiver 1020 can be configured to send a non-access stratum (NAS) message to a user equipment (UE), wherein the non-access stratum (NAS) message may include information indicating whether the UE is registered for emergency services, and wherein whether the UE is registered for emergency services can be determined based on the NAS message.

[0105] In one embodiment, when the information indicates that the UE is registered for emergency services, it may be determined that the UE is registered for emergency services.

[0106] In one embodiment, when the information indicates that the UE is registered for emergency services, protocol data unit (PDU) sessions not associated with emergency services may be released.

[0107] In one embodiment, the UE may not currently be registered for emergency services.

[0108] Fig.11 A user equipment (UE) according to an embodiment of the present disclosure is schematically illustrated.

[0109] Reference Fig.11 UE 1100 may include a processor 1110, a transceiver 1120, and a memory 1130. However, not all components shown in the figure are required. UE 1100 may include a processor 1110, a transceiver 1120, and a memory 1130. Fig.11 The components shown in the figure may be implemented with more or fewer components. In addition, according to another embodiment, the processor 1110, the transceiver 1120, and the memory 1130 may be implemented as a single chip.

[0110] The above-mentioned components will now be described in detail.

[0111] The processor 1110 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. The operations of the UE 1100 may be implemented by the processor 1110.

[0112] The transceiver 1120 may include an RF transmitter for up-converting and amplifying a transmitted signal, and an RF receiver for down-converting the frequency of a received signal. However, according to another embodiment, the transceiver 1120 may be implemented by more or fewer components than those shown in the components.

[0113] The transceiver 1120 may be connected to the processor 1110 and transmit and / or receive signals. The signals may include control information and data. In addition, the transceiver 1120 may receive signals through a wireless channel and output the signals to the processor 1110. The transceiver 1120 may transmit signals output from the processor 1110 through a wireless channel.

[0114] The memory 1130 may store control information or data included in a signal obtained by the UE 1100. The memory 1130 may be connected to the processor 1110 and store at least one instruction or protocol or parameter for the proposed function, process and / or method. The memory 1130 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0115] In one embodiment, the processor 1110 may be configured to receive a non-access stratum (NAS) message from an access and mobility management function (AMF), wherein the non-access stratum (NAS) message includes an indication of whether the UE is registered for emergency services. The processor 1110 may be configured to determine to register for emergency services based on the NAS message.

[0116] In one embodiment, the processor 1110 may be further configured to determine that the UE is registered for the emergency service when the information indicates that the UE is registered for the emergency service.

[0117] In one embodiment, the processor 1110 may be further configured to release a protocol data unit (PDU) session not associated with the emergency service when the information indicates that the UE is registered for the emergency service.

[0118] In one embodiment, the UE may not currently be registered for emergency services.

[0119] The embodiments disclosed herein describe methods and systems for handling emergency services in a wireless network. Therefore, it is understood that the scope of protection extends to such a program, and in addition to a computer-readable device having a message therein, such a computer-readable storage device also includes a program code device for implementing one or more steps of this method when the program is running on a server or a mobile device or any suitable programmable device. This method is implemented in a preferred embodiment by a software program written in another programming language such as a very high speed integrated circuit hardware description language (VHDL) or implemented together with a finger, or by one or more VHDL or multiple software modules being executed on at least one hardware device. The hardware device can be any type of programmable portable device. This device can also include a device, such as a hardware device such as an ASIC, or a combination of hardware and software devices, such as an ASIC and an FPGA, or at least one microprocessor and at least one memory having a software module thereon. The method embodiments described herein can be implemented partially in hardware and partially in software. Alternatively, the present invention can be implemented on different hardware devices, for example, using multiple CPUs.

[0120] Although the present disclosure has been described with various embodiments, various changes and modifications may occur to those skilled in the art. The present disclosure is intended to encompass changes and modifications that fall within the scope of the appended claims.

[0121] The embodiments disclosed herein may be implemented using at least one software program running on at least one hardware device and performing network management functions to control the elements.

[0122] The above description of specific embodiments will fully reveal the general nature of the embodiments herein, so that others can easily modify and / or adapt to various applications of such specific embodiments by applying current knowledge without departing from the general concept, and therefore, such changes and modifications should and are intended to be understood as being within the meaning and scope of equivalent forms of the disclosed embodiments. It should be understood that the wording or terminology used herein is 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 in the spirit and scope of the embodiments described herein.

[0123] Although the present disclosure has been described with various embodiments, various changes and modifications may occur to those skilled in the art. The present disclosure is intended to encompass changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method comprising: Receive non-access stratum NAS messages from the access and mobility management function AMF entity; as well as In case the NAS message includes information indicating that the UE is registered for at least one emergency service, at least one protocol data unit (PDU) session not associated with the at least one emergency service is released by identifying that the UE is registered only for the at least one emergency service.

2. A method performed by an access and mobility management function (AMF) entity in a wireless communication system, the method comprising: releasing at least one protocol data unit (PDU) session not associated with at least one emergency service; generating a non-access stratum (NAS) message, the NAS message comprising information indicating a user equipment (UE) registered for the at least one emergency service; as well as sending the NAS message to the UE, Wherein, in a case where the NAS message includes information indicating that the UE is registered for the at least one emergency service, the UE is identified as being registered only for the at least one emergency service.

3. A user equipment UE executed in a wireless communication system, the UE comprising: Transceiver; as well as at least one processor coupled to the transceiver and configured to: Receiving Non-Access Stratum (NAS) messages from the Access and Mobility Management Function (AMF) entity, and In case the NAS message includes information indicating that the UE is registered for at least one emergency service, at least one protocol data unit (PDU) session not associated with the at least one emergency service is released by identifying that the UE is registered only for the at least one emergency service.

4. An access and mobility management function AMF entity executed in a wireless communication system, the AMF entity comprising: Transceiver; as well as at least one processor coupled to the transceiver and configured to: releasing at least one protocol data unit (PDU) session not associated with at least one emergency service, generating a non-access stratum (NAS) message, the NAS message comprising information indicating a user equipment (UE) registered for the at least one emergency service, and sending the NAS message to the UE, Wherein, in a case where the NAS message includes information indicating that the UE is registered for the at least one emergency service, the UE is identified as being registered only for the at least one emergency service.

Images