Handing authorization of a MWAB-UE in a wireless network

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A UE transmits, to an AMF, a registration request message, wherein the registration request message comprises an indication that the UE intends to act as a MWAB, and a PLMN for which the UE wants to act as the MWAB, in case that the UE is authorized for the MWAB, receive, from the AMF, a registration accept message including MWAB information, wherein the MWAB information comprises information that the MWAB is authorized or not, and area and time information that the UE is authorized or not optionally for per PLMN, perform a MWAB operation based on the area and time information.

Description

HANDING AUTHORIZATION OF A MWAB-UE IN A WIRELESS NETWORK

[0001] The disclosure is related to wireless communication networks. More particularly, the disclosure is related to a method and system for handing authorization of a mobile wireless access backhaul-user equipment (MWAB-UE) in a wireless network.

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

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

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

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

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

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

[0008] In a first aspect of the disclosure, provided herein is a method performed by a user equipment (UE) in a wireless communication system, the method comprising: transmitting, to an access and mobility management function (AMF), a registration request message, wherein the registration request message comprises an indication that the UE intends to act as a mobile gNB with wireless access backhauling (MWAB), and a public land mobile network (PLMN) for which the UE wants to act as the MWAB; in case that the UE is authorized for the MWAB, receiving, from the AMF, a registration accept message including MWAB information, wherein the MWAB information comprises information that the MWAB is authorized or not, and area and time information that the UE is authorized or not optionally for per public land mobile network (PLMN); and performing a MWAB operation based on the area and time information.

[0009] In a second aspect of the disclosure, provided herein a user equipment (UE) in a wireless communication system, the UE comprising: a transceiver; and at least one processor coupled to the transceiver and configured to: transmit, to an access and mobility management function (AMF), a registration request message, wherein the registration request message comprises an indication that the UE intends to act as a mobile gNB with wireless access backhauling (MWAB), and a public land mobile network (PLMN) for which the UE wants to act as the MWAB, in case that the UE is authorized for the MWAB, receive, from the AMF, a registration accept message including MWAB information, wherein the MWAB information comprises information that the MWAB is authorized or not, and area and time information that the UE is authorized or not optionally for per public land mobile network (PLMN), perform a MWAB operation based on the area and time information.

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

[0011] Fig. 1 is a sequence diagram that illustrates a scenario of handling a change of MWAB authorization in wireless networks according to an embodiment of the disclosure.

[0012] Fig. 2 is a sequence diagram that illustrates a scenario where a UE is authorized to act as a MWAB-UE and MWAB-gNB registering for emergency services according to an embodiment of the disclosure.

[0013] Fig. 3 is a sequence diagram that illustrates a scenario where the MWAB-UE authorization state changes and a served UE is having emergency service according to an embodiment of the disclosure.

[0014] Fig. 4 is a block diagram that illustrates a schematic of the UE implemented to carry out the disclosed subject matter according to an embodiment of the disclosure.

[0015] Fig. 5 is a block diagram that illustrates a schematic of an AMF implemented to carry out the disclosed subject matter according to an embodiment of the disclosure.

[0016] Fig. 6 is a block diagram that illustrates a schematic of a gNB implemented to carry out the disclosed subject matter according to an embodiment of the disclosure.

[0017] Fig. 7 is a block diagram that illustrates a schematic of the MWAB-UE implemented to carry out the disclosed subject matter according to an embodiment of the disclosure.

[0018] Fig. 8 is a sequence diagram that illustrates a scenario of handling change of MWAB authorization in wireless networks according to an embodiment of the disclosure.

[0019] Fig. 9 is a sequence diagram that illustrates a scenario of handling change of MWAB authorization in wireless networks according to an embodiment of the disclosure.

[0020] Fig. 10 is a sequence diagram that illustrates a scenario of authorizing a MWAB to serve UEs according to an embodiment of the disclosure.

[0021] Fig. 11 is a sequence diagram that illustrates a scenario for enabling a network to authorize the MWAB-UE for MWAB services according to an embodiment of the disclosure.

[0022] Fig. 12 is a sequence diagram that illustrates a scenario for updating an authorization for a MWAB service according to an embodiment of the disclosure.

[0023] Fig. 13 is a sequence diagram that illustrates a scenario for handling emergency services for MWAB when the MWAB-UE is registering for emergency services according to an embodiment of the disclosure.

[0024] Fig. 14 is a sequence diagram that illustrates another scenario for handling emergency services for MWAB when the MWAB-UE is registering for emergency services according to an embodiment of the disclosure.

[0025] Fig. 15 is a sequence diagram that illustrates a scenario for handling multiple UEs connected to a CN via the MWAB-UE according to an embodiment of the disclosure.

[0026] Fig. 16 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE in a wireless network by the UE according to an embodiment of the disclosure.

[0027] Fig. 17 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE in a wireless network by the AMF according to an embodiment of the disclosure.

[0028] Fig. 18 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE in a wireless network by the gNB according to an embodiment of the disclosure.

[0029] Fig. 19 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE in a wireless network by the AMF according to an embodiment of the disclosure.

[0030] Fig. 20 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE in a wireless network according to an embodiment of the disclosure.

[0031] It may be noted that to the extent possible, like reference numerals have been used to represent like elements in the drawing. Further, those of ordinary skill in the art will appreciate that elements in the drawing are illustrated for simplicity and may not have been necessarily drawn to scale. For example, the dimension of some of the elements in the drawing may be exaggerated relative to other elements to help to improve the understanding of aspects of the disclosure. Furthermore, the elements may have been represented in the drawing by conventional symbols, and the drawings may show only those specific details that are pertinent to the understanding the embodiments of the disclosure so as not to obscure the drawing with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

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

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

[0034] The accompanying drawings are used to help easily understand various technical features and it is understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the proposed method is construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. used herein to describe various elements, these elements are not be limited by these terms. These terms are generally used to distinguish one element from another.

[0035] The various actions, acts, blocks, steps, or the like in the method is performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like are omitted, added, modified, skipped, or the like without departing from the scope of the proposed method.

[0036] In a MWAB scenario, a mobile base station functions as a gNB for various UEs, facilitating access to 5G networks. This includes establishing a New Radio (NR) access link for UEs, which connects wirelessly to the 5G Core (5GC) through IP connectivity. This connection is achieved via PDU sessions that are set up through an NG-RAN cell where the mobile gNB is stationed. The PDU session can be sourced from either a terrestrial network (TN) or a non-terrestrial network (NTN). Additionally, this mobile gNB can be installed on a moving vehicle, enabling it to serve UEs both inside and outside the vehicle, as well as those entering or exiting it.

[0037] A MWAB functioning within a Public Land Mobile Network (PLMN) utilizes wireless access backhaul to serve nearby UEs and requires authorization. In cases of roaming, the Home PLMN (HPLMN) of the MWAB provides additional support. However, the process for authorizing a MWAB to serve UEs, as well as the procedures for updating and managing the MWAB's authorization status, such as authorizing or de-authorizing a previously unapproved MWAB remains unclear. Furthermore, the method by which the Network (specifically, the serving PLMN, whether HPLMN or VPLMN) grants authorization to the MWAB-UE for MWAB services is also not well defined.

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

[0039] The principal object of the embodiments herein is to handle authorization of a MWAB-UE in a wireless network.

[0040] Another object of the embodiments herein is to disclose methods and systems for authorizing a MWAB to serve UEs and how to update and handle the MWAB authorization status (including de-authorizing, or authorizing a previously not authorized MWAB).

[0041] Yet another object of the embodiments herein is to disclose methods and systems for enabling the network (i.e., the serving PLMN (HPLMN or the VPLMN) of the MWAB-UE) to authorize the MWAB-UE for MWAB services.

[0042] In an embodiment of the disclosure, the objectives are achieved by providing a method for handling authorization of a MWAB-UE in a wireless network. The method includes generating a registration request message including an intention of the UE to act as the MWAB-UE. Further, the method includes transmitting the registration request message to an access and mobility management function (AMF). Further, the method includes receiving a non-access stratum (NAS) message like registration accept message from the AMF. The registration accept message comprises a MWAB information and an indication indicating that MWAB operation is allowed, and starting by the UE the MWAB operation based on the MWAB information. Further, the method includes receiving a NAS message like registration reject message from the AMF. The NAS message like registration rejection message an indication indicating that MWAB operation is not allowed.

[0043] In an embodiment of the disclosure, the objectives are achieved by providing a method for handling authorization of a MWAB-UE in a wireless network. The method includes receiving a registration request message from a UE. The registration request message indicates an intention of the UE to act as the MWAB-UE. Further, the method includes determining whether the UE is authorized to act as a MWAB based on subscription data associated with the UE. Further, the method includes generating a registration accept message comprising MWAB information and an indication indicating that the MWAB operation is allowed, when the UE is authorized to act as the MWAB, and transmitting the registration accept message to the UE. Further, the method includes generating a NAS message like registration reject message comprising an indication indicating that the MWAB operation is not allowed, when the MWAB-UE is unauthorized to perform the MWAB operation, and transmitting the NAS message like registration reject message to the UE.

[0044] In an embodiment of the disclosure, the objectives are achieved by providing a method for handling authorization of a MWAB-UE in a wireless network. The method includes configuring a gNB and the core network with a specific Single-Network Slice Selection Assistance Information (S-NSSAI) and data network name (DNN) for emergency backhaul (BH) sessions. Further, the method includes detecting that a UE is in a CM-IDLE state. Further, the method includes receiving a radio resource control (RRC) connection establishment with an indication of an RRC connection establishment cause code indicating "emergency". Further, the method includes detecting the emergency cause code and initiating the establishment or modification of a BH PDU session for emergency support using the configured S-NSSAI and DNN. Further, the method includes detecting an emergency services Allocation and Retention Priority (ARP) value and associating the emergency PDU session for the UE with the emergency BH PDU session.

[0045] In an embodiment of the disclosure, the objectives are achieved by providing a method for handling authorization of a MWAB-UE in a wireless network. The method includes receiving a UE Context Management (UECM) deregistration notification message from a UDM during an emergency PDU session of the MWAB-UE due to a subscription expiry of the MWAB-UE of a MWAB apparatus. Further, the method includes generating an indication message to be transmitted to the MWAB-UE in the form of a NAS message or an AS message when MWAB operations are not allowed upon receiving the UECM deregistration notification message. The indication message indicates that the MWAB-UE is allowed to be registered only for emergency services and non-emergency PDU sessions are not allowed. Further, the method includes receiving a UE configuration update (UCU) complete message from the MWAB-UE indicating that the MWAB operations have stopped for the serving UEs associated with the MWAB-UE. Further, the method includes generating a UE configuration update command to be transmitted to the MWAB-UE indicating that the MWAB-UE is registered for emergency services.

[0046] In an embodiment of the disclosure, the objectives are achieved by providing a method for handling authorization of a MWAB-UE in a wireless network. The method includes receiving a deregistration　message from an AMF. The deregistration　message indicates that the MWAB-UE should be registered for emergency services and that non-emergency PDU sessions are not allowed. Further, the method includes performing a clean-up process and handing over the UEs to a neighboring Next Generation Radio Access Network (NG-RAN). Further, the method includes transmitting a UE configuration update (UCU) complete message to the AMF indicating that MWAB operations have stopped.

[0047] In an embodiment of the disclosure, the objectives are achieved by providing a UE for handling authorization of a MWAB-UE in a wireless network. The UE includes a processor, a memory coupled to the processor, and a UE authorization handling controller communicatively coupled to the processor and the memory. The UE authorization handling controller generates a registration request message including an intention of the UE to act as the MWAB-UE. Further, the UE authorization handling controller transmits the registration request message to an access and mobility management function (AMF). Further, the UE authorization handling controller receives a non-access stratum (NAS) message like registration accept message from the AMF. The registration accept message comprises a MWAB information and an indication indicating that MWAB operation is allowed, and starting by the UE the MWAB operation based on the MWAB information. Further, the UE authorization handling controller receives a NAS message like registration reject message from the AMF. The NAS message like registration rejection message an indication indicating that MWAB operation is not allowed.

[0048] In an embodiment of the disclosure, the objectives are achieved by providing an AMF for handling authorization of a MWAB-UE in a wireless network. The AMF includes a second processor, a second memory coupled to the second processor, and a first AMF authorization handling controller communicatively coupled to the second processor and the second memory. The first AMF authorization handling controller receives a registration request message from a UE. The registration request message indicates an intention of the UE to act as the MWAB-UE. Further, the first AMF authorization handling controller determines whether the UE is authorized to act as a MWAB based on subscription data associated with the UE. Further, the first AMF authorization handling controller generates a registration accept message comprising MWAB information and an indication indicating that the MWAB operation is allowed, when the UE is authorized to act as the MWAB, and transmitting the registration accept message to the UE. Further, the first AMF authorization handling controller generates a NAS message like registration reject message comprising an indication indicating that the MWAB operation is not allowed, when the MWAB-UE is unauthorized to perform the MWAB operation, and transmitting the NAS message like registration reject message to the UE.

[0049] In an embodiment of the disclosure, the objectives are achieved by providing a gNB for handling authorization of a MWAB-UE in a wireless network. The gNB includes a third processor, a third memory coupled to the third processor, and a gNB authorization handling controller communicatively coupled to the third processor and the third memory. The gNB authorization handling controller configures the gNB with a specific S-NSSAI and data network name (DNN) for emergency backhaul (BH) sessions. Further, the gNB authorization handling controller detects that a UE is in a CM-IDLE state. Further, the gNB authorization handling controller receives a radio resource control (RRC) connection establishment with an indication of an RRC connection establishment cause code indicating "emergency". Further, the gNB authorization handling controller detects the emergency cause code and initiating the establishment or modification of a BH PDU session for emergency support using the configured S-NSSAI and DNN. Further, the gNB authorization handling controller detects an emergency services Allocation and Retention Priority (ARP) value and associating the emergency PDU session for the UE with the emergency BH PDU session.

[0050] In an embodiment of the disclosure, the objectives are achieved by providing an AMF for handling authorization of a MWAB-UE in a wireless network. The AMF includes a second processor, a second memory coupled to the second processor, and a second AMF authorization handling controller communicatively coupled to the second processor and the second memory. The second AMF authorization handling controller receives a UECM deregistration notification message from a UDM during an emergency PDU session of the MWAB-UE due to a subscription expiry of the MWAB-UE of a MWAB apparatus. Further, the second AMF authorization handling controller generates an indication message to be transmitted to the MWAB-UE in the form of a NAS message or an AS message when MWAB operations are not allowed upon receiving the UECM deregistration notification message. The indication message indicates that the MWAB-UE is allowed to be registered only for emergency services and non-emergency PDU sessions are not allowed. Further, the second AMF authorization handling controller receives a UE configuration update (UCU) complete message from the MWAB-UE indicating that the MWAB operations have stopped for the serving UEs associated with the MWAB-UE. Further, the second AMF authorization handling controller generates a UE configuration update command to be transmitted to the MWAB-UE indicating that the MWAB-UE is registered for emergency services.

[0051] In an embodiment of the disclosure, the objectives are achieved by providing a MWAB-UE for handling authorization in a wireless network. The MWAB-UE includes a fourth processor, a fourth memory coupled to the fourth processor, and a MWAB-UE authorization handling controller communicatively coupled to the fourth processor and the fourth memory. The MWAB-UE authorization handling controller receives a deregistration　message from an AMF. The deregistration　message indicates that the MWAB-UE should be registered for emergency services and that non-emergency PDU sessions are not allowed. Further, the MWAB-UE authorization handling controller performs a clean-up process and handing over the UEs to a neighboring Next Generation Radio Access Network (NG-RAN). Further, the MWAB-UE authorization handling controller transmits a UE configuration update (UCU) complete message to the AMF indicating that MWAB operations have stopped.

[0052] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications be made within the scope of the embodiments herein.

[0053] Fig. 1 is a sequence diagram that illustrates a scenario of handling a change of MWAB authorization in wireless networks according to an embodiment of the disclosure. As shown in the sequence diagram, a Unified Data Management (UDM) (102), an AMF (104), a Next Generation Node B (gNB) (106), a mobile gNB with wireless access backhauling-user equipment (MWAB-UE) (108), a MWAB-gNB (110), and a UE 1 (112) are in communication with each other. The MWAB-UE (108) may not be available for e.g. due to below reasons:

[0054] ▶ The UDM (102) can trigger Nudm_UECM_DeregistrationNotification procedure for operator-determined purposes to request the removal of a subscriber's RM (Registration Management) context and PDU Session(s) of the UE 1 (112) when the subscription state of the UE 1 (112) changes.

[0055] ▶ The AMF (104), when it receives such a request from the UDM (102) or on expiry of implicit de-registration timer for the UE 1 (112) triggers Network Initiated deregistration Procedure. At this point what should be the behaviour of the MWAB-UE (108)?

[0056] ▶ The MWAB-UE (108) has entered into forbidden area or in service restricted area (service area restrictions)

[0057] In conventional methods, what actions should network / AMF (104) take before de-registering the MWAB-UE (108) and what actions should the UE's connected via the MWAB-gNB (110) perform to prevent service loss is not defined.

[0058] Fig. 2 is a sequence diagram that illustrates a scenario where a UE is authorized to act as a MWAB-UE (108) and the MWAB-gNB (110) registering for emergency services according to an embodiment of the disclosure. As shown in the sequence diagram, the UDM (102), the AMF (104), the gNB (106), the MWAB-UE (108), the MWAB-gNB (110), and the UE 1 (112) are in communication with each other. The MWAB-gNB (110) is connected to 5G core and is providing NR access link to UEs and connected wirelessly (using NR) through a wireless access backhaul to the 5G Core. If the MWAB-UE (108) registers for emergency services, should the UE / entity continue to act as the MWAB-gNB (110) and provide RAN services to other UEs is not clearly specified in current methods. If the MWAB-UE (108) is not allowed to act as the MWAB-UE (108) when registered for emergency service, what should be the behaviour of connected UEs and the MWAB-UE (108) and the MWAB-gNB (110) is not defined.

[0059] In an example scenario, the network may delay sending UCU message with registered for emergency services to the MWAB-UE (108) when it has at least one PDU session for emergency services and it's the MWAB-UE (108) (i.e. performing MWAB operations).

[0060] Fig. 3 is a sequence diagram that illustrates a scenario where the MWAB-UE (108) authorization state changes and a served UE is having emergency service according to an embodiment of the disclosure. As shown in the sequence diagram, the AMF (104), the gNB (106), the MWAB-UE (108), the MWAB-gNB (110), the UE 1 (112), a UE 2 (114), and a target gNB (302) are in communication with each other.

[0061] The network may delay sending UCU message with registered for emergency services to the MWAB-UE (108). It is not clear as to how the MWAB-UE (108) / MWAB-gNB (110) determines that there is at least one UE that is having emergency call. Further, it is not clear as to how the UE having emergency services, continues to have emergency services when the MWAB-UE (108) / MWAB-gNB (110) subscription has changed or authorization state has changed or it is not allowed to operate as MWAB-UE (108) / MWAB-gNB (110) anymore. Further, it is not clear as to how the MWAB-UE (1080 / MWAB-gNB (110) provides QoS required to connected / served UE(s) for different services (emergency / voice etc.) using the PDU session of the MWAB-UE (108).

[0062] For a 5G system with satellite access, the 5G system shall support service continuity between NR terrestrial access network and NR satellite access networks owned by the same operator or owned by 2 different operators having an agreement. The NTN and TN could either operate in two different frequency bands (e.g. FR1 vs FR2), or in same frequency band (e.g. FR1 or FR2). The terms Satellite 3GPP access, Satellite access, Satellite Access Network, NR Satellite Access Network, Satellite NG-RAN Access Technology and NR Satellite access have been interchangeably used and have the same meaning. The methods, issues or solutions disclosed in the embodiment are explained using NR satellite access or Satellite NG-RAN Access Technology as an example and is not restricted or limited to NR Satellite access only. However, the solutions proposed in the embodiment are also applicable for Satellite E-UTRAN access Technology, NB (Narrow Band)-S1 mode or WB (Wide Band)-S1 mode via satellite E-UTRAN access and / or NB-IOT (Narrowband Internet of Things) or WB-IOT (Wideband Internet of Things) Satellite Access / Architecture. The solutions which are defined for NR (5GC) are also applicable to legacy RATs like E-UTRA / LTE, the corresponding CN entities needs to be replaced by LTE entities for e.g. AMF with MME, g-nodeB with e-nodeB, UDM with HSS etc. But principles of the solution remain same.

[0063] An example list of NAS messages can be, but not limited to, REGISTRATION REQUEST message; DEREGISTRATION REQUEST message; SERVICE REQUEST message; CONTROL PLANE SERVICE REQUEST; IDENTITY REQUEST; AUTHENTICATION REQUEST; AUTHENTICATION RESULT; AUTHENTICATION REJECT; REGISTRATION REJECT; DEREGISTRATION ACCEPT; SERVICE REJECT; SERVICE ACCEPT, and so on.

[0064] The Network used in the embodiment is explained using any 5G Core Network Function for e.g. AMF (104). However, the network could be any 5G / EUTRAN Core Network Entities like AMF (104) / SMF / MME / UPF or the Network could be any 5G / EUTRAN RAN Entity like eNodeB (eNB) or gNodeB (gNB) or NG-RAN etc. The messages used or indicated in the embodiment are shown as an example. The messages could be any signalling messages between UE and the Network Functions / Entities or between different Network functions / entities. The term area / location / geographical area are used in this embodiment may refer to any of cell / cell ID, TAC / TAI, PLMN, MCC / MNC, Latitude / longitude, CAG cell or any geographical location / coordinate.

[0065] The methods, issues or solutions disclosed in the embodiment are explained using NR access or NG-RAN Access Technology as an example and is not restricted or limited to NR access only. However, the solutions proposed in the embodiment are also applicable for E-UTRAN access Technology, NB (Narrow Band)-S1 mode or WB (Wide Band)-S1 mode via E-UTRAN access and / or NB-IOT (Narrowband Internet of Things) or WB-IOT (Wideband Internet of Things) Access / Architecture. The solutions which are defined for NR (5GC) are also applicable to legacy RATs like E-UTRA / LTE, the corresponding CN entities needs to be replaced by LTE entities for e.g. the AMF (104) with MME, g-nodeB with e-nodeB, UDM with HSS etc. But principles of the solution remain same. The Network used in the embodiment is explained using any 5G Core Network Function for e.g. the AMF (104). However, the network could be any 5G / EUTRAN Core Network Entities like the AMF (104) / SMF / MME / UPF or the Network could be any 5G / EUTRAN RAN Entity like eNodeB (eNB) or gNodeB (gNB) or NG-RAN etc. The messages used or indicated in the embodiment are shown as an example. The messages could be any signalling messages between UE and the Network Functions / Entities or between different Network functions / entities. The terms camp and register are used interchangeably and have the same meaning.

[0066] The terms wait timer, DisCo wait timer, Discontinuous Coverage wait timer, Random timer, Random wait timer, DCW Timer are all used interchangeably and have the same meaning. The terms wait range, Disco Wait Range, Discontinuous Coverage Wait Range, DCW Range are all used interchangeably and have the same meaning.

[0067] The term area as used in the embodiment may refer to any of cell / cell ID, TAC / TAI, PLMN, MCC / MNC, Latitude / longitude, any CAG / CAG identifier or any geographical location / coordinate. For the list of possible NAS messages please refer to 3GPP TS 24.501 or 3GPP TS 24.301, for list of AS messages please refer to 3GPP TS 38.331 or 3GPP TS 36.331. The cause names in the embodiment are for illustration purpose and it can have any name. The non-access stratum (NAS) messages and access stratum (AS) messages described in the embodiment is only for illustration purpose it can be any NAS or AS messages as per defined protocol between UE and AMF / MME or UE and gNB(NG-RAN / any RAN node) / eNB.

[0068] Mobile gNB with wireless access backhaul (MWAB): A mobile base station acts as the gNB (106) for other UEs and provide access to the 5G networks, i.e. providing a NR access link to UEs and connected wirelessly to the 5GC (using NR) through an IP connectivity provided by a PDU sessions established via a NG-RAN cell that the mobile gNB can camp on. The PDU session is provided either by a Terrestrial Network or by a Non-Terrestrial Network. Such mobile gNB may be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering / leaving the vehicle).

[0069] Embodiments disclosed herein provide a system and method for handling change of MWAB authorization in wireless networks. When UE general subscription has changed and network decides to trigger Network Initiated deregistration procedure for the MWAB-UE (108) it should indicate to the UE that it should not act as MWAB-UE (108) / MWAB-gNB (110). To do this, the AMF (104) of the MWAB-UE (108) can indicate to the MWAB-UE (108) / MWAB-gNB (110) that it is not allowed to act as an MWAB-UE (108) / MWAB-gNB (110), i.e. the MWAB authorization indication (not authorized), as part of registration / de-registration / UCU or any other procedure. When the MWAB authorization state changes for a registered MWAB node (either authorized, or not authorized), the AMF (104) updates the MWAB-UE (108) and the NG-RAN accordingly. Based on the operator configuration, the AMF (104) may use either Deregistration (including the option with re-registration required indication) or the UE Configuration Update procedure or any other NAS / AS procedure to inform the MWAB-UE (108) regarding the updated authorization status. The AMF (104) shall then initiate deregistration procedure for the UE with existing reject causes.

[0070] In an embodiment of the disclosure, the network indicates the MWAB-UE (108) that its subscription has changed in any message / indication to the MWAB-UE (108) / MWAB-gNB (110) and waits for a time of timer t1 (it can be any timer), before triggering the de-registration procedure for the MWAB-UE (108). The MWAB-UE (108) can then initiate handover of connected UEs to another gNB before the timer t1 expires. Once the MWAB-gNB (110) handovers the connected UEs, the network should then, after some delay, i.e. on expiry of timer t1 trigger the network initiated de-registration procedure to de-register the MWAB-UE (108). The AMF (104) / network must try to delay the deregistration of the MWAB-UE (108) as much as possible. The AMF (104) / Network should avoid to de-register the MWAB-UE (108) with cause re-registration required.

[0071] Visited PLMN (VPLMN): This is a PLMN different from the HPLMN (if the Equivalent HPLMN (EHPLMN) list is not present or is empty) or different from an EHPLMN (if the EHPLMN list is present).

[0072] Allowable PLMN: In the case of a mobile station (MS) operating in MS operation mode A or B, this is a PLMN which is not in the list of "forbidden PLMNs" in the MS. In the case of an MS operating in MS operation mode C or an MS not supporting A / Gb mode and not supporting Iu mode, this is a PLMN which is not in the list of "forbidden PLMNs" and not in the list of "forbidden PLMNs for GPRS service" in the MS.

[0073] Available PLMN: PLMN(s) in the given area which is / are broadcasting capability to provide wireless communication services to the UE.

[0074] Camped on a cell: The MS (mobile equipment (ME) if there is no Subscriber Identity Module (SIM)) has completed the cell selection / reselection process and has chosen a cell from which it plans to receive all available services. Note that the services may be limited, and that the PLMN or the Standalone Non-Public Network (SNPN) may not be aware of the existence of the MS (ME) within the chosen cell.

[0075] EHPLMN: Any of the PLMN entries contained in the Equivalent HPLMN list.

[0076] Equivalent HPLMN list: To allow provision for multiple HPLMN codes, PLMN codes that are present within this list shall replace the HPLMN code derived from the international mobile subscriber identity (IMSI) for PLMN selection purposes. This list is stored on the Universal Subscriber Identify Module (USIM) and is known as the EHPLMN list. The EHPLMN list may also contain the HPLMN code derived from the IMSI. If the HPLMN code derived from the IMSI is not present in the EHPLMN list then it shall be treated as a Visited PLMN for PLMN selection purposes.

[0077] Home PLMN: This is a PLMN where the MCC and MNC of the PLMN identity match the Mobile Country Code (MCC) and Mobile Network Code (MNC) of the IMSI.

[0078] Registered PLMN (RPLMN): This is the PLMN on which certain LR (location registration which is also called as registration procedure) outcomes have occurred. In a shared network the RPLMN is the PLMN defined by the PLMN identity of the CN operator that has accepted the LR.

[0079] Registration: This is the process of camping on a cell of the PLMN or the SNPN and doing any necessary LRs.

[0080] User controlled PLMN (UPLMN): PLMN / access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);

[0081] Operator Controlled PLMN (OPLMN): PLMN / access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order)

[0082] In an embodiment list of NAS messages but not limited to are:

[0083] ▶ REGISTRATION REQUEST message;

[0084] ▶ DEREGISTRATION REQUEST message;

[0085] ▶ SERVICE REQUEST message; and

[0086] ▶ CONTROL PLANE SERVICE REQUEST.

[0087] ▶ IDENTITY REQUEST

[0088] ▶ AUTHENTICATION REQUEST;

[0089] ▶ AUTHENTICATION RESULT;

[0090] ▶ AUTHENTICATION REJECT;

[0091] ▶ REGISTRATION REJECT

[0092] ▶ REGISTRATION ACCEPT

[0093] ▶ DEREGISTRATION ACCEPT

[0094] ▶ SERVICE REJECT

[0095] ▶ SERVICE ACCEPT

[0096] ▶ UE CONFIGURATION UPDATE command

[0097] ▶ UE PARAMETERS UPDATE command

[0098] In an embodiment the term EMM sublayer states are at least one of the below:

[0099] 1) EMM-NULL

[0100] 2) EMM-DEREGISTERED

[0101] a) EMM-DEREGISTERED.NORMAL-SERVICE

[0102] b) EMM-DEREGISTERED.LIMITED-SERVICE

[0103] c) EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH

[0104] d) EMM-DEREGISTERED.PLMN-SEARCH

[0105] e) EMM-DEREGISTERED.NO-IMSI

[0106] f) EMM-DEREGISTERED.ATTACH-NEEDED

[0107] g) EMM-DEREGISTERED.NO-CELL-AVAILABLE

[0108] h) EMM-DEREGISTERED.eCALL-INACTIVE

[0109] 3) EMM-REGISTERED-INITIATED

[0110] 4) EMM-REGISTERED

[0111] a) EMM-REGISTERED.NORMAL-SERVICE

[0112] b) EMM-REGISTERED.ATTEMPTING-TO-UPDATE

[0113] c) EMM-REGISTERED.LIMITED-SERVICE

[0114] d) EMM-REGISTERED.PLMN-SEARCH

[0115] e) EMM-REGISTERED.UPDATE-NEEDED

[0116] f) EMM-REGISTERED.NO-CELL-AVAILABLE

[0117] g) EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM

[0118] h) EMM-REGISTERED.IMSI-DETACH-INITIATED

[0119] 5) EMM-DEREGISTERED-INITIATED

[0120] 6) EMM-TRACKING-AREA-UPDATING-INITIATED

[0121] 7) EMM-SERVICE-REQUEST-INITIATED

[0122] The term 5GMM sublayer state in the embodiment is at least one of the below:

[0123] 1) 5GMM-NULL

[0124] 2) 5GMM-DEREGISTERED

[0125] a) 5GMM-DEREGISTERED.NORMAL-SERVICE

[0126] b) 5GMM-DEREGISTERED.LIMITED-SERVICE

[0127] c) 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION

[0128] d) 5GMM-DEREGISTERED.PLMN-SEARCH

[0129] e) 5GMM-DEREGISTERED.NO-SUPI

[0130] f) 5GMM-DEREGISTERED.NO-CELL-AVAILABLE

[0131] g) 5GMM-DEREGISTERED.eCALL-INACTIVE

[0132] h) 5GMM-DEREGISTERED.INITIAL-REGISTRATION-NEEDED

[0133] 3) 5GMM-REGISTERED-INITIATED

[0134] 4) 5GMM-REGISTERED

[0135] a) 5GMM-REGISTERED.NORMAL-SERVICE

[0136] b) 5GMM-REGISTERED.NON-ALLOWED-SERVICE

[0137] c) 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE

[0138] d) 5GMM-REGISTERED.LIMITED-SERVICE

[0139] e) 5GMM-REGISTERED.PLMN-SEARCH

[0140] f) 5GMM-REGISTERED.NO-CELL-AVAILABLE

[0141] g) 5GMM-REGISTERED.UPDATE-NEEDED

[0142] 5) 5GMM-DEREGISTERED-INITIATED

[0143] 6) 5GMM-SERVICE-REQUEST-INITIATED

[0144] The term RAT as defined in the embodiment can be one of the following:

[0145] ▶ NG-RAN

[0146] ▶ 5G, 4G, 3G, 2G

[0147] ▶ EPS, 5GS

[0148] ▶ NR

[0149] ▶ NR in unlicensed bands

[0150] ▶ NR(LEO) satellite access

[0151] ▶ NR(MEO) satellite access

[0152] ▶ NR(GEO) satellite access

[0153] ▶ NR(OTHERSAT) satellite access

[0154] ▶ NR RedCap

[0155] ▶ E-UTRA

[0156] ▶ E-UTRA in unlicensed bands

[0157] ▶ NB-IoT

[0158] ▶ WB-IoT

[0159] ▶ LTE-M

[0160] 5GS registration type are:

[0161] ▶ initial registration

[0162] ▶ mobility registration updating

[0163] ▶ periodic registration updating

[0164] ▶ emergency registration

[0165] ▶ SNPN onboarding registration

[0166] ▶ "disaster roaming initial registration; or

[0167] ▶ "disaster roaming mobility registration updating"

[0168] PLMN selection as per 23.122 without RPLMN:

[0169] The MS selects and attempts registration on any PLMN / access technology combinations, if available and allowable, in the following order:

[0170] ▶ either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present);

[0171] ▶ each PLMN / access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);

[0172] ▶ each PLMN / access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order);

[0173] ▶ other PLMN / access technology combinations with received high quality signal in random order;

[0174] ▶ Other PLMN / access technology combinations in order of decreasing signal quality.

[0175] PLMN selection as per 23.122 with RPLMN:

[0176] The MS selects and attempts registration on any PLMN / access technology combinations, if available and allowable, in the following order:

[0177] ▶ either the RPLMN or the Last registered PLMN;

[0178] ▶ either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present);

[0179] ▶ each PLMN / access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);

[0180] ▶ each PLMN / access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order);

[0181] ▶ other PLMN / access technology combinations with received high quality signal in random order;

[0182] ▶ other PLMN / access technology combinations in order of decreasing signal quality.

[0183] A Closed Access Group (CAG) identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. CAG is used for the Public network integrated NPNs to prevent UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated cell(s). The applicable time slot / timer for CAG ID is the time slot / time the UE is allowed to access the CAG cell or the time slot UE is not allowed to access the CAG cell. Timer associated with the CAG ID can comprise of start time and end time information or duration after UE has accessed the CAG or any other mechanism in which control of the time can be applied on CAG ID or list of CAG IDs. For example, time slot configured is start time and end time after the end time the timer is considered expired. Based on this timer associated with the CAG ID parameter, the UE determines if it can access the CAG cell or not access the CAG cell. If the time slot is allowed time slot, then the UE will access the CAG otherwise UE will not access the CAG. CAG IDs expiration information provides information of expiry of all the CAG-IDs configured in the UE.

[0184] The methods, issues or solutions disclosed in the embodiment are explained using NR access or NG-RAN Access Technology as an example and is not restricted or limited to NR access only. However, the solutions proposed in the embodiment are also applicable for E-UTRAN access Technology, NB (Narrow Band)-S1 mode or WB (Wide Band)-S1 mode via E-UTRAN access and / or NB-IOT (NarrowBand Internet Of Things) or WB-IOT (WideBand Internet Of Things) Access / Architecture.

[0185] The solutions that are defined for NR(5GC) are also applicable to legacy RATs like E-UTRA / LTE, the corresponding CN entities need to be replaced by LTE entities for e.g. AMF with MME, g-nodeB with e-nodeB, UDM with HSS etc. But principles of the solution remain same.

[0186] The Network used in the embodiment is explained using any 5G Core Network Function for e.g. AMF. However, the network could be any 5G / EUTRAN Core Network Entities like AMF / SMF / MME / UPF or the Network could be any 5G / EUTRAN RAN Entity like eNodeB (eNB) or gNodeB (gNB) or NG-RAN etc.

[0187] The messages used or indicated in the embodiment are shown as an example. The messages could be any signalling messages between UE and the Network Functions / Entities or between different Network functions / entities.

[0188] The terms camp and register are used interchangeably and have the same meaning.

[0189] The term area or location or geographical area as used in the embodiment may refer to any of cell / cell ID, TAC / TAI, PLMN, MCC / MNC, Latitude / longitude, any CAG cell / CAG identifier or any geographical location / coordinate.

[0190] For the list of possible NAS messages please refer to 3GPP TS 24.501 or 3GPP TS 24.301, for list of AS messages please refer to 3GPP TS 38.331 or 3GPP TS 36.331

[0191] The cause names in the embodiment are for illustration purpose and it can have any name. The non-access stratum (NAS) messages and access stratum (AS) messages described in the embodiment is only for illustration purpose it can be any NAS or AS messages as per defined protocol between UE and AMF / MME or UE and gNB(NG-RAN / any RAN node) / eNB.

[0192] In the embodiment, the terms 'MWAB Authorization status', 'MWAB authorization indication', and 'MWAB authorization result' are used interchangeably and have the same meaning.

[0193] Referring now to the drawings, and more particularly to Figs. 4 through 20 where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0194] Fig. 4 is a block diagram that illustrates a schematic of a UE (402) implemented to carry out the disclosed subject matter according to an embodiment of the disclosure. For instance, the UE (402) may include, but not limited to a smartphone, a tablet, a laptop, a personal computer (PC), a television, automotive systems (such as connected cars, autonomous vehicles, vehicle-to-everything (V2X) communication devices, etc.), enterprise Devices such as robotics, specialized Equipment (such as medical devices, public safety devices, etc.), media Devices (such as gaming Consoles, streaming Devices, etc.), and the like. As shown, the UE (402) includes a first processor (404), a first memory (406), a first I / O interface (408), and a UE authorization handling controller (410). Each component is explained in further detail below.

[0195] The first processor (404) communicates with the first memory (406), the first I / O interface (408) and the UE authorization handling controller (410). The first processor (404) is configured to execute instructions stored in the first memory (406) and to perform various processes. The first processor (404) may include one or a plurality of processors, may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0196] The first memory (406) includes storage locations to be addressable through the first processor (404). The first memory (406) is not limited to a volatile memory and / or a non-volatile memory. Further, the first memory (406) may include a plurality of computer-readable storage media. The first memory (406) may include non-volatile storage elements. For example, non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

[0197] The first I / O interface (408) transmits the information between the first memory (406) and external peripheral devices. The peripheral devices are the input-output devices associated with the UE (402). Further, the UE authorization handling controller (410) communicates with the first I / O interface (408) and the first memory (406). The UE authorization handling controller (410) may be communicatively coupled to the first memory (406) and the first processor (404). The UE authorization handling controller (410) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0198] In an embodiment of the disclosure, the UE authorization handling controller (410) generates a registration request message. This message includes an intention of the UE (402) to act as the MWAB-UE (108). The registration request message includes essential information about the UE (402), such as its unique identifier, capabilities, and the specific services it intends to access. The MWAB-UE (108) designation indicates that the UE (402) is equipped to handle multiple wireless access technologies simultaneously, enhancing its connectivity options and overall performance. For instance, the registration request message indicates public land mobile networks (PLMNs) for which the UE (402) intends to act as the MWAB-gNB (110) to the AMF (104).

[0199] In an embodiment of the disclosure, the UE authorization handling controller (410) transmits the registration request message to the AMF (104). The AMF (104) manages the registration and mobility of the UE (402) within the wireless network. Upon receiving the registration request, the AMF (104) processes the information, verifies the identity of the UE (402), checks for any necessary authentication, and determines whether the registration can be granted based on the current network conditions and policies.

[0200] In an embodiment of the disclosure, the UE authorization handling controller (410) receives a non-access stratum (NAS) message like registration accept message from the AMF (104). The registration accept message includes a MWAB information and an indication indicating that MWAB operation is allowed. Upon receiving the MWAB information, the MWAB operation is started by the UE (402). For instance, the MWAB information includes a MWAB-authorized information and a MWAB-unauthorized information. The MWAB-authorized information includes an area and a time for which the UE (402) is authorized for MWAB per PLMN. The MWAB-unauthorized information includes an area and a time for which the UE (402) is not authorized for MWAB per PLMN.

[0201] In an embodiment of the disclosure, the UE authorization handling controller (410) receives a NAS message like registration reject message from the AMF (104). The NAS message like registration rejection message indicating that MWAB operation is not allowed.

[0202] Fig. 5 is a block diagram that illustrates a schematic of the AMF (104) implemented to carry out the disclosed subject matter according to an embodiment of the disclosure. As shown, the AMF (104) includes a second processor (502), a second memory (504), a second I / O interface (506), a first AMF authorization handling controller (508), and a second AMF authorization handling controller (510). The first AMF authorization handling controller (508), and the second AMF authorization handling controller (510) may be communicatively coupled to the second memory (504) and the second processor (502). The first AMF authorization handling controller (508), and the second AMF authorization handling controller (510) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0203] In an embodiment of the disclosure, the first AMF authorization handling controller (508) receives a registration request message from the UE (402). The registration request message indicates an intention of the UE (402) to act as the MWAB-UE (108). The registration request message includes essential information about the UE (402), such as its unique identifier, capabilities, and the specific services it intends to access.

[0204] In an embodiment of the disclosure, the first AMF authorization handling controller (508) determines whether the UE (402) is authorized to act as a MWAB based on subscription data associated with the UE (402). The subscription data includes details about the service plan, access rights, and any specific conditions or limitations that may apply to the UE (402). By analyzing this subscription data, the first AMF authorization handling controller (508) can ascertain whether the UE (402) meets the necessary criteria to be granted access to the MWAB services.

[0205] In an embodiment of the disclosure, the first AMF authorization handling controller (508) generates a registration accept message including MWAB information and an indication indicating that the MWAB operation is allowed. This message is generated when the UE (402) is authorized to act as the MWAB. The registration accept message is then transmitted to the UE (402).

[0206] In an embodiment of the disclosure, the first AMF authorization handling controller (508) generates a NAS message like registration reject message including an indication indicating that the MWAB operation is not allowed. This message is generated when the MWAB-UE is unauthorized to perform the MWAB operation. The NAS message like registration reject message is then transmitted to the UE (402).

[0207] In an embodiment of the disclosure, the second AMF authorization handling controller (510) receives a UECM deregistration notification message from a UDM (102) during an emergency PDU session of the MWAB-UE (108) due to a subscription expiry of the MWAB-UE (108). When the subscription expires, it can lead to various network management actions, including the need to deregister the UE (402) from the network. The emergency PDU session indicates that the MWAB-UE (108) is currently engaged in a critical communication process, which may involve emergency services or urgent data transmission.

[0208] In an embodiment of the disclosure, the second AMF authorization handling controller (510) generates an indication message to be transmitted to the MWAB-UE (108) in the form of a NAS message or an AS message. The indication message is generated when MWAB operations are not allowed upon receiving the UECM deregistration notification message. The indication message indicates that the MWAB-UE (108) is allowed to be registered only for emergency services and non-emergency PDU sessions are not allowed.

[0209] In an embodiment of the disclosure, the second AMF authorization handling controller (510) receives a UE configuration update (UCU) complete message from the MWAB-UE (108) indicating that the MWAB operations have stopped for the serving UEs associated with the MWAB-UE (108). This ensures that the AMF (104) can effectively manage resources and maintain optimal performance for the connected UEs. The second AMF authorization handling controller (510) will then proceed to take appropriate actions based on this update, which may include re-evaluating the current state of the UEs, adjusting resource allocations, or initiating further communication with other network components to ensure seamless service continuity.

[0210] In an embodiment of the disclosure, the second AMF authorization handling controller (510) generates a UE configuration update command to be transmitted to the MWAB-UE (108) indicating that the MWAB-UE (108) is registered for emergency services. The emergency services may include functionalities such as emergency calls, location services for emergency responders, and other critical communication services during emergencies. The UE configuration update command may include various parameters and settings that inform the MWAB-UE (108) about its current status, capabilities, and any specific configurations required to facilitate its access to these essential services.

[0211] Fig. 6 is a block diagram that illustrates a schematic of the gNB (106) implemented to carry out the disclosed subject matter according to an embodiment of the disclosure. As shown, the gNB (106) includes a third processor (602), a third memory (604), a third I / O interface (606), and a gNB authorization handling controller (608). The gNB authorization handling controller (608) may be communicatively coupled to the third memory (604) and the third processor (602). The gNB authorization handling controller (608) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0212] In an embodiment of the disclosure, the gNB authorization handling controller (608) configures the gNB (106) with a specific S-NSSAI and data network name (DNN) for emergency backhaul (BH) sessions. The DNN serves as an identifier for the data network that the gNB (106) will connect to, facilitating the routing of data packets and ensuring that emergency communications are directed to the appropriate network resources. The DNN essential for maintaining reliable and efficient communication during emergency situations, where timely access to data and services can be vital.

[0213] In an embodiment of the disclosure, the gNB authorization handling controller (608) detects that the UE (402) is in a CM-IDLE state. When the UE (402) is in the CM-IDLE state, it means that the UE (402) is not actively engaged in a data session or communication with the wireless network. However, the UE (402) is still registered and capable of receiving incoming calls or messages. This state is essential for conserving battery life and network resources, as the UE (402) does not maintain a continuous connection to the network.

[0214] In an embodiment of the disclosure, the gNB authorization handling controller (608) receives a radio resource control (RRC) connection establishment with an indication of an RRC connection establishment cause code indicating "emergency". Given that the request is categorized as an emergency, the gNB authorization handling controller (608) prioritizes it over regular connection requests. This prioritization is crucial in ensuring that emergency services, such as those related to public safety or urgent medical assistance, are given immediate access to network resources.

[0215] In an embodiment of the disclosure, the gNB authorization handling controller (608) detects the emergency cause code and initiates the establishment or modification of a BH PDU session for emergency support using the configured S-NSSAI and DNN.

[0216] In an embodiment of the disclosure, the gNB authorization handling controller (608) detects an emergency services Allocation and Retention Priority (ARP) value and associating the emergency PDU session for the UE (402) with the emergency BH PDU session. The ARP value assists in determining the priority level for resource allocation and retention in the network, ensuring that emergency communications are given precedence over regular traffic.

[0217] Fig. 7 is a block diagram that illustrates a schematic of the MWAB-UE (108) implemented to carry out the disclosed subject matter according to an embodiment of the disclosure. As shown, the MWAB-UE (108) includes a fourth processor (702), a fourth memory (704), a fourth I / O interface (706), and a MWAB-UE authorization handling controller (708). The MWAB-UE authorization handling controller (708) may be communicatively coupled to the fourth memory (704) and the fourth processor (702). The MWAB-UE authorization handling controller (708) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0218] In an embodiment of the disclosure, the MWAB-UE authorization handling controller (708) receives a deregistration　message from the AMF (104). The deregistration　message indicates that the MWAB-UE (108) should be registered for emergency services and that non-emergency PDU sessions are not allowed. This deregistration message contains information that instructs the MWAB-UE (108) to transition into a state where it is only permitted to access emergency services. This means that while the MWAB-UE (108) can still connect to emergency service networks and utilize features designed for urgent situations, it is prohibited from establishing non-emergency PDU sessions.

[0219] In an embodiment of the disclosure, the MWAB-UE authorization handling controller (708) performs a clean-up process and handing over the UEs to the NG-RAN (1102). During this clean-up process, the MWAB-UE authorization handling controller (708) verifies the status of each UE, ensuring that all ongoing transactions are concluded and that the UEs are in a state ready for transition. This may involve deallocating network resources, updating session states, and notifying relevant network components of the changes.

[0220] In an embodiment of the disclosure, the MWAB-UE authorization handling controller (708) transmits a UE configuration update (UCU) complete message to the AMF (104) indicating that MWAB operations have stopped. The UCU complete message includes all necessary details regarding the current state and configuration of the UEs.

[0221] Fig. 8 is a sequence diagram that illustrates a scenario of handling change of MWAB authorization in wireless networks according to an embodiment of the disclosure. As shown in the sequence diagram, the UDM (102), the AMF (104), the gNB (106), the MWAB-UE (108), the MWAB-gNB (110), the UE 1 (112), and the target gNB (302) are in communication with each other. Each step is explained in further detail below.

[0222] At step 1, the UDM (102) triggers Nudm_UECM_DeregistrationNotification procedure for operator-determined purposes to request the removal of a subscriber's RM context and PDU Session(s) of the MWAB-UE (108) when the subscription state of the MWAB-UE (108) changes. Or UE triggers registration procedure and UE is no more allowed to register with network or the MWAB-UE (108) cannot be served for e.g. because UE is in the forbidden area or the UE is the service restricted area or there is a congestion in the network etc.

[0223] At step 2, the MWAB-UE (108) before getting de-registered / indicated that it is not allowed to remain registered (for e.g. due to registration reject (due to any of the causes) or deregistration message) should be indicated by the AMF (104) or any other network entity with NAS or AS message like UCU (or any other NAS or AS message) that they are not authorized anymore (i.e. MWAB Authorization is ending or has ended) or indicate that it is not allowed remain registered for e.g. due to forbidden reasons. The above procedure is also valid before providing NAS reject causes to the MWAB-UE (108). The complete list of reject causes is defined in TS 24.501. The AMF (104) / UPF or any other network function before sending reject indicates in any NAS / AS message or any other indication to the MWAB-UE (108) / MWAB-gNB (110) that the request is getting rejected so that all served UEs get released / handed over before the MWAB-UE (108) gets de-registered.

[0224] At step 3, the MWAB-UE (108) will indicate / inform the MWAB-gNB (110) that it has to move all the served UEs to other gNBs or to other MWAB-gNBs or to release all the served UEs.

[0225] At step 4, the MWAB-gNB (110) triggers handover procedure for all the possible served UE or the UE 1 (112).

[0226] At step 5a, the MWAB-gNB (110) sends an acknowledgement to the MWAB-UE (108) once all served UEs are handed over or released.

[0227] At step 5b, the MWAB-UE (108) or (optionally the MWAB-gNB (110)) sends the acknowledgement or indication in any other NAS or AS message or through data path after handing over or releasing all served UEs to the AMF (104) indicating that all serving UEs are handed over and it stop operating as the MWAB-gNB (110) or the MWAB-UE (108) in general as MWAB.

[0228] At step 6, once the MWAB-UE (108) receives the acknowledgement from the MWAB-gNB (110), the MWAB-UE (108) can trigger deregistration procedure with network or indicate to network that all UEs are moved to other gNBs through any NAS or AS message. Alternatively, if the acknowledgement was sent to the AMF (104), the AMF (104) triggers the de-registration procedure or registration reject message or any other NAS or AS message for the MWAB-UE (108) / MWAB-gNB (110). Network can send appropriate reject cause related to forbidden area / service area restriction e.g. provide non-allowed area as described in 23.501 / 24.501 etc. The network triggers NAS signalling release procedure i.e. AN release procedure.

[0229] Fig. 9 is a sequence diagram that illustrates a scenario of handling change of MWAB authorization in wireless networks according to an embodiment of the disclosure. As shown in the sequence diagram, the UDM (102), the AMF (104), the gNB (106), the MWAB-UE (108), the MWAB-gNB (110), the UE 1 (112), and the target gNB (302) are in communication with each other. Each step is explained in further detail below.

[0230] At step 1, the UDM (102) triggers Nudm_UECM_DeregistrationNotification procedure for operator-determined purposes to request the removal of a subscriber's RM context and PDU Session(s) of the MWAB-UE (108) when the subscription state of the MWAB-UE (108) changes. Or UE triggers registration procedure and UE is no more allowed to register with network or the MWAB-UE (108) cannot be served for e.g. because UE is in the forbidden area or the UE is the service restricted area or there is a congestion in the network etc.

[0231] At step 2, the MWAB-UE (108) before getting de-registered / indicated that it is not allowed to remain registered (for e.g. due to registration reject (due to any of the causes) or deregistration message) should be indicated by the AMF (104) or any other network entity with NAS or AS message like UCU (or any other NAS or AS message) that they are not authorized anymore (i.e. MWAB Authorization is ending or has ended) or indicate that it is not allowed remain registered for e.g. due to forbidden reasons. The above procedure is also valid before providing NAS / AS reject causes to the MWAB-UE (108). The complete list of reject causes is defined in TS 24.501. The AMF (104) / UPF or any other network function before sending reject indicates in any NAS / AS message or any other indication to the MWAB-UE (108) / MWAB-gNB (110) that the request is getting rejected so that all served UEs get released / handed over before the MWAB-UE gets de-registered. The AMF (104) starts a timer T1 to wait for graceful release of the UE acting as a MWAB for e.g. move all the serving UEs to target NG-RAN and stop acting as the gNB (106) by the MWAB-gNB (110).

[0232] At step 3, the MWAB-UE (108) will indicate / inform the MWAB-gNB (110) that it has to move all the served UEs to other gNBs or to other MWAB-gNBs or to release all the served UEs.

[0233] At step 4, the MWAB-gNB (110) triggers handover procedure for all the possible served UE or the UE 1 (112).

[0234] At step 5, the network can trigger de-registration or registration reject message or any other NAS or AS message for the MWAB-UE (108) / MWAB-gNB (110) after particular time i.e. on expiry of timer (timer t1) set earlier, this time duration can be set such that all connected UEs can be handed over within this time to other gNBs (i.e NG-RAN). The network should trigger NAS signalling connection release procedure.

[0235] In an embodiment for the proposed method when the network indicates to the MWAB-UE (108) that it is no more authorized to act as MWAB or it is not allowed to remain registered or it cannot be served. All these terms have same meaning and implies that the MWAB-UE (108) will not be able to establish the user plane resource and provide backhaul connectivity (i.e. establish N2 or N3 interface) over its PDU session to the MWAB-gNB (110).

[0236] In an embodiment of the disclosure, the AMF (104) may indicate to the MWAB-UE (108) the timer with a value indicating after how long the AMF (104) will clear the session or deregister the UE or provide a reject message after which UE will not be able to act as MWAB. The MWAB is expected to clear the sessions and handover the serving UEs to another gNBs etc.

[0237] In an embodiment of the disclosure, the AMF (104) may start the timer T1 as described in the embodiment and also wait for acknowledgement (ack) from the MWAB-UE (108) / MWAB-gNB (110). If acknowledgement is not received before timer T1 expires then the AMF (104) can act as described in the embodiment on timer expiry / ack reception (i.e. as if ack is received). The acknowledgement in the embodiment is one of the AS or NAS message or any other message or indication.

[0238] When UE general subscription has changed and network decides to trigger Network Initiated deregistration procedure for the MWAB-UE (108) it should:

[0239] ▶ Indicate to UE that it should not act as MWAB-UE (108) / MWAB-gNB (110). To do this, the AMF (104) of the MWAB-UE (108) can indicate to the MWAB-UE (108) / MWAB-gNB (110) that it is not allowed to act as an MWAB-UE (108) / MWAB-gNB (110), i.e. the MWAB authorization indication (not authorized), as part of registration / de-registration / UCU or any other procedure. When the MWAB authorization state changes for a registered MWAB node (either authorized, or not authorized), the AMF (104) updates the MWAB-UE (108) and the NG-RAN accordingly. Based on the operator configuration, the AMF (104) may use either Deregistration (including the option with re-registration required indication) or the UE Configuration Update procedure or any other NAS / AS procedure to inform the MWAB-UE (108) regarding the updated authorization status.

[0240] ▶ The AMF (104) shall then initiate deregistration procedure for the UE with existing reject causes.

[0241] ▶ In an embodiment of the disclosure, the network indicates the MWAB-UE (108) that its subscription has changed in any message / indication to the MWAB-UE (108) / MWAB-gNB (110) and waits for a time of timer t1 (it can be any timer), before triggering the de-registration procedure for the MWAB-UE (108). The MWAB-UE (108) can then initiate handover of connected UEs to another gNB before the timer t1 expires. Once the MWAB-gNB (110) handovers the connected UEs, the network should then, after some delay, i.e. on expiry of timer t1 trigger the Network initiated de-registration procedure to de-register the MWAB UE (108).

[0242] ▶ The AMF (104) / Network must try to delay the de-registration of the MWAB UE (108) as much as possible.

[0243] ▶ The AMF (104) / Network should avoid to de-register the MWAB UE (108) with cause re-registration required.

[0244] Fig. 10 is a sequence diagram that illustrates a scenario of authorizing a MWAB to serve UEs according to an embodiment of the disclosure. As shown in the sequence diagram, the UE (402), the gNB (106), an AMF-1 (104A), and the UDM (102) are in communication with each other. Each step is explained in further detail below.

[0245] At step 1, the NG-RAN or the gNB (106) may broadcast its support of MWAB services or operation or may indicate its support for MWAB services through any of the AS or NAS signalling messages or through any of the IE or identifiers in the broadcast messages.

[0246] In a first option, in step 2a, for the UE (402) to operate as a MWAB (for e.g. the MWAB-UE (108) and / or the MWAB-gNB (110)), the UE (402) shall provide an MWAB-Support indication to the NG-RAN node (for e.g. in AN message) (for e.g. when RRC connection is established). The UE (402) shall send REGISTRATION REQUEST message or any of the AS or NAS signalling message to the network and indicates the intention of becoming the MWAB-UE (108) to the NG-RAN. In an embodiment of the disclosure, the UE (402) (for e.g. the MWAB-UE (108)) may additionally indicate the PLMN(s) or the list of the PLMN(s) for which it wants to act as an MWAB or for which it wants to provide MWAB services. The PLMN(s) or the list of the PLMN(s) indicated by the UE(s) may be in the priority or the preferred order of the PLMN(s) for which the UE (402) wants to provide MWAB services. The PLMN(s) or the List of the PLMN(s) may be configured / pre-configured in the UE (402) / USIM / ME and / or can be indicated / updated by the Network in any of the AS or NAS signalling message. The PLMN(s) or the list of the PLMN(s) may be (pre-)configured / updated in the UE (402), optionally, on a per Location / timeslot basis, optionally by any NF or Application Function (AF). The Max number of entries in the list of the PLMN(s) or the max number of the PLMN(s) may be defined / configured, optionally per location and / or timeslot basis. In step 2b, the NG-RAN node shall indicate to the AMF (104) or any other NF or entity, UE's intention of becoming the MWAB-UE (108) to the AMF (104) (for example in N2 INITIAL UE MESSAGE).

[0247] In a second option, in step 3, the UE (402) shall send a REGISTRATION REQUEST message or any of the AS or NAS signalling message to the network and indicate the intention of becoming the MWAB-UE (108) to the AMF-1 (104A). Additionally, the UE (402) may indicate the PLMN(s) or the list of the PLMN(s) for which it may want to act as MWAB or for which it wants to provide MWAB services. The PLMN(s) or the list of the PLMN(s) indicated by the UE(s) may be in the priority or the preferred order of the PLMN(s) for which the UE (402) wants to provide MWAB services. The PLMN(s) or the List of the PLMN(s) may be configured / pre-configured in the UE (402) / USIM / ME and / or can be indicated / updated by the Network in any of the AS or NAS signalling messages. The PLMN(s) or the list of the PLMN(s) may be (pre-)configured / updated in the UE (402), optionally, on a per Location / timeslot basis, optionally by any NF or Application Function (AF). The Max number of entries in the list of the PLMN(s) or the max number of the PLMN(s) may be defined / configured, optionally per location and / or timeslot basis.

[0248] In step 4, the AMF-1 (104A) or any other NF shall interact with the UDM (102) or other NF, to get the subscription data using which MWAB-Authorization status as described below by the AMF-1 (104A) is determined. For a MWAB, the subscription information / data stored in the UDM (102) / HPLMN indicates whether it is authorized to operate as a MWAB, and the corresponding location and time information, optionally per PLMN. In an embodiment of the disclosure, the AF can configure the location and time information (for e.g. allowed or restricted time and / or location), optionally on a per PLMN basis, for the MWAB services / operation. (for e.g. time duration may decide when the UE (402) is allowed or restricted for operating as a MWAB).

[0249] In an embodiment of the disclosure, in case of roaming, if the MWAB roaming is supported, a roaming agreement between serving PLMN / VPLMN and the HPLMN of the UE (402) (for e.g. the MWAB-UE (108)) regarding MWAB operation shall be in place. The AMF-1 (104A) may use the subscription data and / or operator local policy and take those into consideration for MWAB authorization in the V-PLMN. In an embodiment of the disclosure, the MWAB authorization may also be based on other parameters (but not limited to) like network status, a limit on the number of MWAB(s) operating in certain area, optionally in a time-slot, optionally per PLMN. In an embodiment of the disclosure, the AMF-1 (104A) of the Serving PLMN / VPLMN or the AMF-1 (104A) of the HPLMN of the UE (402) (for e.g. the MWAB-UE (108)) shall authorize the MWAB operation of the UE (402).

[0250] In step 5a, the AMF-1 (104A) sends Registration Accept or any other NAS or AS signalling message to the UE (402) and indicates the MWAB-Authorization status / indication. In an embodiment of the disclosure, if the serving PLMN allows the UE (402) (for e.g. the MWAB-UE (108)) to be registered in the PLMN, the AMF-1 (104A) sends Registration Accept or any other NAS or AS signalling message to the UE (402) and indicates the MWAB-Authorization status / indication. The MWAB-Authorization status / indication includes, one or more of the following in any order or combination:

[0251] a) MWAB-Authorized; (for e.g. MWAB-Authorization Status / Indication (MWAB-Authorized)). The AMF (104) or any other Network function may provide this indication if the MWAB operation is authorized for the UE (402) and / or if the UE (402) is authorized for MWAB operation for at least one of the PLMN(s) indicated by the UE (402) or determined by the AMF (104) / NF. In an embodiment of the disclosure, the AMF (104) or any other Network function may provide the MWAB-Authorized on a per PLMN basis (for e.g. on the basis of the PLMN(s) for which UE (402) indicated its intention to become MWAB and / or on the basis of the PLMN(s) determined by the AMF (104) / NF for which MWAB services / operation is supported / allowed / authorized for the UE (402)). The AMF (104) / NF may additionally include the area / location and the time in which the UE (402) is authorized / allowed for MWAB services (for e.g. allowed / authorized time or allowed / authorized location / area) and / or the area / location and the time in which the UE (402) is not authorized / not allowed / restricted for MWAB services (for e.g. restricted or not allowed time or restricted or not allowed location / area), optionally on a per PLMN basis; or

[0252] b) MWAB-Unauthorized or MWAB-not authorized; (for e.g. MWAB-Authorization Status / Indication (MWAB-UnAuthorized or MWAB-Not Authorized)). The AMF (104) or any other Network function may provide this indication if the MWAB operation is not authorized for the UE (402) and / or if the UE (402) is not authorized for MWAB operation for all the PLMN(s) indicated by the UE (402) or determined by the AMF (104) / NF. In an embodiment of the disclosure, the AMF (104) or any other Network function may provide the MWAB-UnAuthorized or MWAB-Not Authorized on a per PLMN basis (for e.g. on the basis of the PLMN(s) for which the UE (402) indicated its intention to become MWAB and / or on the basis of the PLMN(s) determined by the AMF (104) / NF for which MWAB services / operation is not supported / not allowed / not authorized for the UE (402)). The AMF (104) / NF may additionally include the area / location and the time in which the UE (402) is authorized / allowed for MWAB services (for e.g. allowed / authorized time or allowed / authorized location / area) and / or the area / location and the time in which the UE (402) is not authorized / not allowed / restricted for MWAB services (for e.g. restricted or not allowed or not authorized time or restricted or not allowed or not authorized location / area), optionally on a per PLMN basis. The AMF (104) generates the above information based on the PLMN(s) UE indicated its intention to become MWAB for.

[0253] In an embodiment of the disclosure, the UE (402) may add the PLMN(s) for which MWAB-Unauthorized or MWAB-Not Authorized indication is received into a forbidden PLMN list for MWAB services, optionally for the restricted time and location / area, optionally on a per PLMN basis. In an embodiment of the disclosure, the UE (402) shall store or maintain the list of PLMN(s) (for e.g. authorized and / or not authorized PLMN(s)) with the indicated MWAB-Authorization status / indication, optionally with allowed / authorized and / or not allowed / restricted area / location and / or time, optionally on a per PLMN basis, and may update this list based on the Network updated values. The UE (402) may maintain this list (in ME / USIM) and shall not delete this list during switch on / off. In an embodiment of the disclosure, the UE (402) may delete this list during switch on / off. In an embodiment of the disclosure, the UE (402) shall delete this list when USIM is removed and / or (re-)inserted.

[0254] In step 5b, the AMF-1 (104A) sends a Registration Reject or any other NAS or AS signalling message to the UE (402) and indicates the MWAB-Authorization status / indication as MWAB-Not Authorized or MWAB-UnAuthorized (for e.g. MWAB-Authorization Status / Indication (MWAB-UnAuthorized or MWAB-Not Authorized). In an embodiment of the disclosure, if the serving PLMN does not allow the UE (402) (for e.g. the MWAB-UE (108)) to be registered in the PLMN, the AMF-1 (104A) sends Registration Reject or any other NAS or AS signalling message to the UE (402) and may optionally indicate the MWAB-Authorization status / indication as MWAB-Not Authorized or MWAB-UnAuthorized. The AMF-1 (104A) / NF may additionally include the area / location and the time in which the UE is authorized / allowed for MWAB services (for e.g. allowed / authorized time or allowed / authorized location / area) and / or the area / location and the time in which the UE (402) is not authorized / not allowed / restricted for MWAB services (for e.g. restricted or not allowed or not authorized time or restricted or not allowed or not authorized location / area), optionally on a per PLMN basis;

[0255] In an embodiment of the disclosure, the AMF (104) or NF may send any of the Registration Accept or Registration Reject or any of the AS or NAS signalling messages indicating the MWAB Authorization Status / indication of the UE (402), optionally on a per PLMN basis, optionally including Allowed / Authorized and / or Not Allowed / Restricted / Not Authorized Area / location and / or time, optionally on a per PLMN basis, to the NG-RAN or the gNB (for e.g. over NGAP) and the NG-RAN or the gNB can indicate to the UE (402) in any of the AS / NAS signalling message.

[0256] In an embodiment of the disclosure, the AMF (104) or NF may send any of the Registration Accept or Registration Reject or any of the AS or NAS signalling messages indicating the MWAB Authorization Status / indication of the UE (402), optionally on a per PLMN basis, optionally including Allowed / Authorized and / or Not Allowed / Restricted / Not Authorized Area / location and / or time, optionally on a per PLMN basis, as defined below:

[0257] a) UE (402) can act as the MWAB-UE (108) only (for e.g. the UE (402) cannot behave as a normal UE). The AMF (104) / NF may additionally provide one or more of Allowed NSSAI, S-NSSAI, DNN, FQDN, and IP Address based on MWAB operations, optionally per PLMN, which are allowed for the UE (402) and the UE (402) can access only these.

[0258] b) UE (402) can act as a normal UE only (for e.g. UE is not allowed for MWAB operation). The UE (402) may be allowed to access any PDU sessions or IP addresses.

[0259] c) UE (402) can act as both Normal UE and the MWAB-UE (108). The UE (402) may be allowed to access any PDU sessions or IP addresses.

[0260] d) UE (402) is not allowed to act as Normal UE and not allowed to act as the MWAB-UE (108). The Network may deregister the UE (402) in such cases or indicate Registration Reject or any other AS / NAS signalling message.

[0261] In an embodiment of the disclosure, when the UE (402) (for e.g. the MWAB-UE (108)) receives the MWAB Authorization Status / Indication from the AMF (104) / NG-RAN / any NF, the UE (402) (for e.g. the MWAB-UE (108)) may provide the information about the authorization status / indication / result to the MWAB-gNB (110) component based on any available interface.

[0262] In an embodiment of the disclosure, if the UE (402) is authorized for MWAB operation / service, then it can start operations on the MWAB-gNB (110) to act as MWAB in the area or time on which the UE (402) is authorized to act as MWAB, optionally on a per PLMN basis (for e.g. for which the UE (402) is allowed / authorized). If the UE (402) enters a location or time at which the UE (402) is not authorized to act as MWAB it will stop operating as MWAB.

[0263] In an embodiment of the disclosure, if the UE (402) is not authorized for MWAB operation / service in the area or time (indicated by network) then the UE (402) will not start (or stop) the MWAB operations, optionally on a per PLMN basis. The UE (402) can again attempt to act as MWAB (for e.g. execute from Authorization Procedure) in the area or time where the UE (402) is allowed to act as MWAB or it comes out of area or time where it was not allowed / restricted to be authorized as MWAB.

[0264] Fig. 11 is a sequence diagram that illustrates a scenario for enabling a network to authorize the MWAB-UE (108) for MWAB services according to an embodiment of the disclosure. As shown in the sequence diagram, the UE (402), a NG-RAN (1102), the AMF (104), and the UDM (102) are in communication with each other. When the UE (402) wants to behave as the MWAB-UE (108), the UE (402) may indicate the Network (e.g. to the AMF (104), or any other Core network entity directly) during Registration and based on the UE's subscription data or local operator policy for MWAB operation or any other information, the selected Network Entity (for e.g. the AMF (104) or any other network entity), optionally, performs the MWAB authorization during the UE registration procedure / UE context setup procedure / modification procedure. However, the UE (402) can behave either as a normal UE or as the MWAB-UE (108) based on the subscription data of the UE (402). When the UE (402) performs registration or attempts to register to the Network in any area or PLMN (for example- Home area or roaming area or HPLMN or VPLMN or any PLMN) as a MWAB-UE, either,

[0265] - The Network Entity (for e.g. the AMF (104)) may accept the Registration Request of the MWAB-UE (108); or

[0266] - The Network Entity (for e.g. the AMF (104)) may accept the Registration Request but indicate (for e.g. in any of the IE like 5GS Registration Result IE) that the "The UE (402) is allowed to operate as Normal UE only (i.e., the UE (402) without MWAB)" or "The UE (402) is not allowed to operate as the UE (402) with MWAB" in the current geographical area / TAI or any roaming area or for the selected / camped / registered PLMN (HPLMN / VPLMN or Registered PLMN); or

[0267] - The Network Entity (for e.g. the AMF (104)) may reject the Registration Request of the MWAB-UE (108) with a 5GMM cause value indicating that the UE (402) is not allowed to operate as the MWAB-UE (108) in the current geographical area / TAI or any roaming area or for the selected / camped / registered PLMN (HPLMN / VPLMN or Registered PLMN).

[0268] In a first case, if a Registration Accept or any AS / NAS signalling indicating indication / IE ((for example, 5GS Registration Result IE)) has been accepted from the Network entity (for e.g. the AMF (104)), for the UE (402) with a 5GMM cause value / indication indicating that the "The UE (402) is allowed to operate as Normal UE only (i.e., the UE (402) without MWAB)" or "The UE (402) is not allowed to operate as the UE (402) with MWAB" in the current geographical area / TAI or any roaming area or for the selected / camped / registered PLMN (HPLMN / VPLMN or Registered PLMN), the UE (402) remains camped / registered to the Network as a normal UE / UE(No MWAB). The UE (402) shall remain registered with the selected Network and shall operate as normal UE only and shall not operate as the MWAB UE (108) for the selected or registered PLMN.

[0269] In a second case, if Registration reject or any AS / NAS signalling indicating a reject message / indication / IE has been received from the Network entity (for e.g. the AMF (104)), for the UE (402) with a 5GMM cause value / indication indicating that the UE (402) is not allowed to operate as the MWAB-UE (108) in the current geographical area / TAI or any roaming area or for the selected PLMN (HPLMN / VPLMN or Registered PLMN), the UE (402) may deregister from the Network or may not camp / register on the selected Network. The UE (402), if needed, may optionally register / re-register with the same Network / PLMN / RAT as a normal UE / UE(No MWAB) and may remain camped / registered to the Network as a normal UE

[0270] However, due to the subscription change or authorization change of the UE (402) (for e.g. from Normal UE to the MWAB-UE (108) at the UE (402) or Network side or due to UE mobility (to a new area or a new PLMN or a new RAT) or due to the expiry of the time-period / time-slot / time-window / time after which the UE (402) is allowed to behave as the MWAB-UE (108) or due to any reasons at the UE / Network side, if the UE (402) becomes eligible to behave or the UE (402) can behave as the MWAB-UE (108) in the current area / PLMN / RAT, currently, it is not defined how would UE (402) / Network make the UE (402) to behave as the MWAB-UE (108) or there is no way for the Network to configure the UE (402) to behave as the MWAB-UE (108) or there is no way for the UE (402) to behave as the MWAB-UE (108) in the current area / PLMN / RAT and the UE (402) would continue to behave as a normal UE and would not behave as the MWAB-UE (108).

[0271] This behaviour is not expected at the UE (402) / Network side and a method needs to be defined to allow the UE (402) to behave as the MWAB-UE (108) due to any subscription change or authorization change of the UE (402) (for e.g. from Normal UE to the MWAB-UE (108)) at the UE (402) or Network side or due to UE mobility (to a new area or to a new PLMN or to a new RAT) or due to any reasons at the UE (402) / Network side whenever the UE (402) becomes eligible to behave or the UE (402) can behave as the MWAB-UE (108) in the current area / PLMN / RAT.

[0272] In step 1, the MWAB-UE (108) initiates a registration procedure and indicates its intention to operate as the MWAB-UE (108) in Registration message or any AS / NAS signaling message to the Network (for example, the AMF (104) or any other network entity). In step 2 (which can be optional), the AMF (104) may perform the MWAB-UE (108) authorization for the UE (402) with the UDM (102). The AMF (104) or any Network Function may determine whether the UE (402) is allowed to operate as the MWAB-UE (108) in the selected or camped PLMN or not.

[0273] In step 3a (i.e., the first case, as mentioned above), if the Network (for example, the AMF (104) or AUSF or the UDM (102), etc.) determines the UE (402) is not allowed to operate as the MWAB-UE (108) in the selected or camped PLMN, the Network (for example, the AMF (104) or any other network entity) shall indicate using any indication / IE ((for example, 5GS Registration Result IE)) to the UE (402) in the REGISTRATION ACCEPT message or any AS / NAS signalling indicating "The UE (402) is allowed to operate as Normal UE only (i.e. the UE (402) without MWAB operation)" or "The UE (402) is not allowed to operate as the UE (402) with MWAB" in any of the IE (for example, 5GS Registration Result IE).

[0274] In step 3b (i.e., the first case, as mentioned above), if the Network determines the UE (402) is not allowed to operate as the MWAB-UE (108) in the selected or camped PLMN / Network / RAT, the Network (for example, the AMF (104) or any other network entity) shall indicate to the UE (402) in the REGISTRATION Reject message indicating "The UE (402) is allowed to operate as Normal UE only (i.e., the UE (402) without MWAB operation)" or "The UE (402) is not allowed to operate as the UE (402) with MWAB" in any of the IE (for example, 5GS Registration Result IE) or in any of the 5GMM causes. The UE (402), if needed, may optionally register / re-register or trigger a registration procedure via any AS / NAS signalling message with the same Network / PLMN / RAT as a normal UE (No MWAB) / UE (without MWAB operation) and may remain camped / registered to the selected Network as a normal UE / UE (No MWAB) / UE (without MWAB operation).

[0275] In step 4, the UE (402) shall remain registered with the selected Network and shall operate as normal UE only and shall not operate as a MWAB-UE (108) for the selected or registered PLMN.

[0276] Fig. 12 is a sequence diagram that illustrates a scenario for updating an authorization for a MWAB service according to an embodiment of the disclosure. As shown in the sequence diagram, the UE (402), the NG-RAN (1102), the AMF (104), and the UDM (102) are in communication with each other. Each step is explained in further detail below.

[0277] At step 1, the UE (402) is registered with the selected Network and is operating as a normal UE only and is not operating / not authorized to operate as the MWAB-UE (108), optionally on a per PLMN basis, for the selected or registered PLMN, optionally for the current time and location.

[0278] Due to the subscription change or authorization change of the UE (402) (for e.g. from Normal UE / UE(No MWAB) to UE (With MWAB operation) / UE(MWAB) or MWAB-UE) at the UE (402) or Network side or due to UE mobility (to a new area or to a new PLMN or to a new RAT) or due to the expiry of the time-period / time-slot / time-window / time after which the UE (402) is allowed to behave as an MWAB or due to any reasons at the UE (402) / Network side, in step 2, if the Network (for e.g. the AMF (104) or the NG-RAN (1102)) or the UE (402) determines that the UE (402) becomes eligible to behave or the UE (402) can behave as the MWAB-UE (108) in the current area / PLMN / RAT, optionally on a per PLMN basis, then the Network (for e.g. the AMF (104) or any other network entity) and / or the UE (402) can perform any of the below steps or procedures in any order or combination:

[0279] In step 3, the Network may perform one or more of the following in any order or combination:

[0280] a) The Network (for example, the AMF (104) or any other network entity) shall indicate or inform the UE (402) via any AS / NAS signalling message (for example DEREGISTRATION REQUEST message or DEREGISTRATION REQUEST message with re-registration is required or UE Configuration Update (UCU) procedure or UPU procedure or any AS / NAS signalling procedure) with a cause indicating that the "The UE (402) is allowed to act / behave as the MWAB-UE (108)" (for e.g. MWAB-Authorization status = Authorized), optionally on a per PLMN basis, in the current / selected / registered PLMN / RAT / area / TAI / TAC / geographical location. In an embodiment of the disclosure, the network may indicate the list of PLMN(s) for which the MWAB-Authorization Status / Indication has changed (for e.g. from Not authorized to Authorized). In an embodiment of the disclosure, the network may indicate the list of PLMN(s) for which the MWAB-Authorization Status / Indication is MWAB-Authorized. In an embodiment of the disclosure, the Network may indicate the list of PLMN(s) for which the UE (402) indicated its intention to become MWAB for, with their latest / updated MWAB-Authorization Status / Indication (for e.g. MWAB-Authorized or MWAB-NotAuthorized). In an embodiment of the disclosure, the AMF (104) / NF / Network may additionally include the area / location and the time in which the UE (402) is authorized / allowed for MWAB services (for e.g. allowed / authorized time or allowed / authorized location / area) and / or the area / location and the time in which the UE (402) is not authorized / not allowed / restricted for MWAB services (for e.g. restricted or not allowed or not authorized time or restricted or not allowed or not authorized location / area), optionally on a per PLMN basis. The Network may optionally indicate / inform the UE (402) that the UE (402) should re-register at the end of the Deregistration / UCU / UPU procedure. If the UE (402) registers / re-registers to the network using any AS / NAS signalling after the deregistration / UCU / UPU procedure, the Network shall indicate / inform to the UE (402), optionally as a part of registration procedure in any of the IE / Cause / Indication that the "The UE (402) is allowed to act / behave as a MWAB-UE (108)", optionally on a per PLMN basis, in the current / selected / registered PLMN / RAT / area / TAI / TAC / geographical location.

[0281] In step 4, the UE (402) may perform one or more of the following in any order or combination:

[0282] i) The UE (402) shall register / re-register with the network or the UE (402) shall trigger a registration procedure with the network via any AS / NAS signalling message. The UE (402), optionally, indicates its intention to operate as a MWAB-UE (108) in Registration Request or any AS / NAS signalling message to the Network (for example, the AMF (104) or any other network entity). In an embodiment of the disclosure, the UE (402) (for e.g. the MWAB-UE (108)) may additionally indicate the PLMN(s) or the list of the PLMN(s) for which it wants to act as an MWAB or for which it wants to provide MWAB services. In an embodiment of the disclosure, the UE (402) may indicate the list of PLMN(s) for which the MWAB-Authorization Status / Indication has changed (for e.g. from Not authorized to Authorized). In an embodiment of the disclosure, the UE (402) may indicate the list of PLMN(s) for which the MWAB-Authorization Status / Indication is MWAB-Authorized. In an embodiment of the disclosure, the UE (402) may indicate the list of PLMN(s) for which the UE (402) indicated its intention to become MWAB for, with their latest MWAB-Authorization Status / Indication (for e.g. MWAB-Authorized or MWAB-NotAuthorized). The PLMN(s) or the list of the PLMN(s) indicated by the UE (402) may be in the priority or the preferred order of the PLMN(s) for which UE (402) wants to provide MWAB services. The PLMN(s) or the List of the PLMN(s) may be configured / pre-configured in the UE (402) / USIM / ME and / or can be indicated / updated by the Network in any of the AS or NAS signalling message. The PLMN(s) or the list of the PLMN(s) may be (pre-)configured / updated in the UE (402), optionally, on a per Location / timeslot basis, optionally by any NF or Application Function (AF). The Max number of entries in the list of the PLMN(s) or the max number of the PLMN(s) may be defined / configured, optionally per location and / or timeslot basis.

[0283] ii) The UE (402) shall trigger or complete the deregistration procedure. The UE (402), optionally, triggers / completes the deregistration procedure followed by a registration / re-registration procedure via any AS / NAS signalling message.

[0284] iii) The UE (402) may scan for other / alternate Network / PLMN / RAT and may perform PLMN selection according to PLMN selection as per 23.122 without RPLMN or according to PLMN selection as per 23.122 with RPLMN or PLMN selection as per 3GPP TS 23.122.

[0285] In an embodiment of the disclosure, when the UE (402) (for e.g. the MWAB-UE (108)) receives the MWAB Authorization Status / Indication from the AMF (104) / NG-RAN / any NF, the UE (402) (for e.g. the MWAB-UE (108)) may provide the information about the authorization status / indication / result to its MWAB-gNB component based on any available interface.

[0286] If the UE (402) is authorized for MWAB operation / service, then it can start operations on the MWAB-gNB (110) to act as MWAB in the area or time on which the UE (402) is authorized to act as MWAB, optionally on a per PLMN basis (for e.g. for which the UE (402) is allowed / authorized). If the UE (402) enters a location or time at which the UE (402) is not authorized to act as MWAB it will stop operating as MWAB.

[0287] If the UE (402) is not authorized for MWAB operation / service in the area or time (indicated by network) then the UE (402) will not start (or stop) the MWAB operations, optionally on a per PLMN basis. The UE (402) can again attempt to act as MWAB (for e.g. execute from Authorization Procedure) in the area or time where the UE (402) is allowed to act as MWAB or it comes out of area or time where it was not allowed / restricted to be authorized as a MWAB.

[0288] Embodiments herein disclose a process of updating the authorization (Not allowed / Authorized to Allowed / Authorized) for a MWAB service. In step 1, the UE (402) is registered with the selected Network and is operating / authorized to operate as the MWAB-UE (108), optionally for a per PLMN basis, for the selected or registered PLMN, optionally for the current time and location.

[0289] In step 2, due to the subscription change or authorization change of the UE (402) (for e.g. from the MWAB-UE (108) to Normal UE / UE(No MWAB)) at the UE (402) or Network side or due to UE mobility (to a new area or a new PLMN or a new RAT) or due to the expiry of the time-period / time-slot / time-window / time after which the UE (402) is not allowed to behave as the MWAB-UE (108) or due to any reasons at the UE (402) / Network side, if the Network or the UE (402) determines that the UE (402) is no more eligible to behave or the UE (402) is not allowed to behave or the UE (402) can't behave as the MWAB-UE (108), optionally on a per PLMN basis, in the current area / PLMN / RAT, then the Network (for e.g AMF or any other network entity) and / or the UE (402) can perform any of the below steps or procedures in any order or combination:

[0290] In step 3, the Network may perform one or more of the following in any order or combination:

[0291] a) The Network (for example, the AMF (104) or any other network entity) shall indicate or inform the UE (402) via any AS / NAS signalling message (for example DEREGISTRATION REQUEST message or DEREGISTRATION REQUEST message with re-registration is required or UE Configuration Update (UCU) procedure or UPU procedure or any AS / NAS signalling procedure) with a cause indicating that the "The UE (402) is not allowed to act / behave as the MWAB-UE (108)" (for e.g. MWAB-Authorization status = NotAuthorized), optionally on a per PLMN basis, in the current / selected / registered PLMN / RAT / area / TAI / TAC / geographical location. In an embodiment of the disclosure, the network may indicate the list of PLMN(s) for which the MWAB-Authorization Status / Indication has changed (for e.g. from Not authorized to Authorized). In an embodiment of the disclosure, the network may indicate the list of PLMN(s) for which the MWAB-Authorization Status / Indication is MWAB-NotAuthorized. In an embodiment of the disclosure, the Network may indicate the list of PLMN(s) for which the UE (402) indicated its intention to become MWAB for, with their latest / updated MWAB-Authorization Status / Indication (for e.g. MWAB-Authorized or MWAB-NotAuthorized). In an embodiment of the disclosure, The AMF (104) / NF / Network may additionally include the area / location and the time in which the UE (402) is authorized / allowed for MWAB services (for e.g. allowed / authorized time or allowed / authorized location / area) and / or the area / location and the time in which the UE (402) is not authorized / not allowed / restricted for MWAB services (for e.g. restricted or not allowed or not authorized time or restricted or not allowed or not authorized location / area), optionally on a per PLMN basis.

[0292] The Network may optionally indicate / inform to the UE (402) that the UE (402) should re-register at the end of the Deregistration / UCU / UPU procedure. If the UE (402) registers / re-registers to the network using any AS / NAS signalling after the deregistration / UCU / UPU procedure, the Network shall indicate / inform to the UE (402), optionally as a part of registration procedure in any of the IE / Cause / Indication that the "The UE (402) is not allowed to act / behave as a MWAB-UE" (e.g. MWAB-NotAuthorized), optionally on a per PLMN basis, in the current / selected / registered PLMN / RAT / area / TAI / TAC / geographical location.

[0293] In step 4, the UE (402) may perform one or more of the following in any order or combination:

[0294] i) The UE (402) shall register / re-register with the network or the UE (402) shall trigger a registration procedure with the network via any AS / NAS signalling message. The UE (402), optionally, indicates its intention to operate as the MWAB-UE (108) in Registration Request or any AS / NAS signalling message to the Network (for example, the AMF (104) or any other network entity). In an embodiment of the disclosure, the UE (402) (for e.g. the MWAB-UE (108)) may additionally indicate the PLMN(s) or the list of the PLMN(s) for which it wants to act as an MWAB or for which it wants to provide MWAB services. In an embodiment of the disclosure, the UE (402) may indicate the list of PLMN(s) for which the MWAB-Authorization Status / Indication has changed (for e.g. from Not authorized to Authorized). In an embodiment of the disclosure, the UE (402) may indicate the list of PLMN(s) for which the MWAB-Authorization Status / Indication is MWAB-Authorized. In an embodiment of the disclosure, the UE (402) may indicate the list of PLMN(s) for which the UE (402) indicated its intention to become MWAB for, with their latest MWAB-Authorization Status / Indication (for e.g. MWAB-Authorized or MWAB-NotAuthorized). The PLMN(s) or the list of the PLMN(s) indicated by the UE (402) may be in the priority or the preferred order of the PLMN(s) for which the UE (402) wants to provide MWAB services. The PLMN(s) or the List of the PLMN(s) may be configured / pre-configured in the UE (402) / USIM / ME and / or can be indicated / updated by the Network in any of the AS or NAS signalling message. The PLMN(s) or the list of the PLMN(s) may be (pre-)configured / updated in the UE (402), optionally, on a per Location / timeslot basis, optionally by any NF or Application Function (AF). The Max number of entries in the list of the PLMN(s) or the max number of the PLMN(s) may be defined / configured, optionally per location and / or timeslot basis.

[0295] ii) The UE (402) shall trigger or complete the deregistration procedure. The UE (402), optionally, triggers / completes the deregistration procedure followed by a registration / re-registration procedure via any AS / NAS signalling message.

[0296] iii) The UE (402) may scan for other / alternate Network / PLMN / RAT and may perform PLMN selection according to PLMN selection as per 23.122 without RPLMN or according to PLMN selection as per 23.122 with RPLMN or PLMN selection as per 3GPP TS 23.122.

[0297] In an embodiment of the disclosure, when the UE (402) (for e.g. the MWAB-UE (108)) receives the MWAB Authorization Status / Indication from the AMF (104) / NG-RAN / any NF, the UE (402) (for e.g. the MWAB-UE (108)) may provide the information about the authorization status / indication / result to the MWAB-gNB (110) component based on any available interface.

[0298] If UE (402) is authorized for MWAB operation / service, then it can start operations on the MWAB-gNB (110) to act as MWAB in the area or time on which the UE (402) is authorized to act as MWAB, optionally on a per PLMN basis (for e.g. for which the UE (402) is allowed / authorized). If the UE (402) enters a location or time on which the UE (402) is not authorized to act as MWAB it will stop operating as MWAB.

[0299] If the UE (402) is not authorized for MWAB operation / service in the area or time (indicated by network) then the UE (402) will not start (or stop) the MWAB operations, optionally on a per PLMN basis. The UE (402) can again attempt to act as MWAB (for e.g. execute from Authorization Procedure) in the area or time where the UE (402) is allowed to act as MWAB or it comes out of area or time where it was not allowed / restricted to be authorized as MWAB.

[0300] Fig. 13 is a sequence diagram that illustrates a scenario for handling emergency services for MWAB when the MWAB-UE (108) is registering for emergency services according to an embodiment of the disclosure. As shown in the sequence diagram, the UDM (102), the AMF (104), the gNB (106), the MWAB-UE (108), the MWAB-gNB (110), the UE 1 (112), and the target gNB (302) are in communication with each other. Consider that the MWAB-UE (108) gets registered for emergency services, for example due to the MWAB-UE (108) subscription expiry.

[0301] Solution (based on an acknowledgement):

[0302] Consider that the MWAB-UE (108) / MWAB-gNB (110) are serving multiple UEs. The MWAB-UE (108) triggers an emergency service or registers for emergency services. Optionally, the MWAB-UE (108) also indicates in the emergency registration request message that it is not allowed to act as a MWAB anymore, or the MWAB-UE (108) is having at least one active PDU session for emergency services. The UDM (102) may send Nudm_UECM_DeregistrationNotification to the AMF (104) during Emergency session (Emergency PDU is active) of the MWAB-UE (108), which will cause MWAB-UE (108) registration state to change to Emergency registered.

[0303] In step 1, the MWAB-UE (108) before getting emergency registered, should be indicated by the AMF (104) or any other network entity with NAS or AS message like the UCU (or any other NAS or AS message) that they are not authorized anymore (i.e., MWAB Authorization is ending or has ended or MWAB operation is not allowed) or indicate that it is not allowed remain registered for normal services and registered only for emergency services; for e.g., due to forbidden reasons or indication from the UDM (102) that the UE (402) is not subscribed or it should be deregistered.

[0304] In step 2, the MWAB-UE (108) will indicate / inform the MWAB-gNB (110) that it has to move all the served UEs to other gNBs or to other MWAB-gNBs or to release all the served UEs. The MWAB-UE (108) releases all non emergency PDU sessions.

[0305] In step 3, the MWAB-gNB (110) triggers handover procedure for all the possible served UE or the UE 1 (112).

[0306] In step 4a, the MWAB-gNB (110) sends an acknowledgement to MWAB-UE (108) once all served UEs / UE 1 (112) are handed over or released. In step 4b, the MWAB-UE (108) or (optionally the MWAB-gNB (110)) sends the acknowledgement or indication in any other NAS or AS message like the UCU complete or through data path after handing over or releasing all served UEs to the AMF (104) indicating that all serving UEs are handed over and it stops operating as the MWAB-gNB (110) or the MWAB-UE (108) in general as MWAB.

[0307] In step 5, the AMF (104) sends the NAS message, UE configuration command (or any other NAS or AS message) with registered for emergency services to the UE (402). In an embodiment of the disclosure, when the MWAB-UE (108) is registered for emergency services, the AMF (104) should indicate registered for emergency services to the MWAB-UE (108) in any NAS or AS message, so that the UE (402) releases all other PDU sessions except for MWAB operations.

[0308] Fig. 14 is a sequence diagram that illustrates another scenario for handling emergency services for MWAB when the MWAB-UE (108) is registering for emergency services according to an embodiment of the disclosure. As shown in the sequence diagram, the UDM (102), the AMF (104), the gNB (106), the MWAB-UE (108), the MWAB-gNB (110), the UE 1 (112), and the target gNB (302) are in communication with each other. Consider that the MWAB-UE (108) is registering for emergency services, for example due to the MWAB-UE (108) subscription expiry. Consider that the MWAB-UE (108) / MWAB-gNB (110) are serving multiple UEs. The MWAB-UE (108) triggers an emergency service or registers for emergency services. Optionally, the MWAB-UE (108) also indicates in the emergency registration request message that it is not allowed to act as MWAB anymore. The UDM (102) may send Nudm_UECM_DeregistrationNotification to the AMF (104) during Emergency session (Emergency PDU is active) of MWAB-UE (108) which will cause the MWAB-UE (108) registration state to change to Emergency registered.

[0309] In step 1, the MWAB-UE (108), before getting state changed to emergency registered, should be indicated by the AMF (104) or any other network entity with NAS or AS message like the UCU (or any other NAS or AS message) that they are not authorized anymore (i.e. MWAB Authorization is ending or has ended or MWAB operation is not allowed) or indicate that it is not allowed remain registered for normal services and registered only for emergency services for e.g. due to forbidden reasons. The AMF (104) starts a timer T1 to wait for the graceful release of the UE (402) acting as an MWAB, for e.g., move all the served UEs to the target NG-RAN and stop acting as the gNB (106) by the MWAB-gNB (110).

[0310] In step 2, then the MWAB-UE (108) will indicate / inform the MWAB-gNB (110) that it has to move all the served UEs to other gNBs or to other MWAB-gNBs or to release all the served UEs.

[0311] In step 3, the MWAB-gNB (110) triggers a handover procedure for all the possible served UEs or the UE 1 (112).

[0312] In step 4, the AMF (104) sends the NAS message, UE configuration command or any other NAS or AS message with registered for emergency services to the UE (402) to the MWAB-UE (108) / MWAB-gNB (110) after a particular time; i.e., on expiry of timer (timer t1) set earlier, this time duration can be set such that all connected UEs can be handed over within this time to other gNBs (i.e., NG-RAN). This timer may be pre-configured in the UE (402), or the UE (402) may have an implementation dependent timer and inform the network or it may be provided by the AMF (104) or any other network entity to the UE (402) in any of the NAS or AS message.

[0313] In an embodiment of the disclosure, when the MWAB-UE (108) is registered for emergency services, the AMF (104) should indicate registered for emergency services to the MWAB-UE (108), so that the UE (402) releases all other PDU sessions except for MWAB operations.

[0314] In an embodiment of the disclosure, the MWAB-UE (108) when registered for emergency service, should not act as the MWAB-gNB (110). When the MWAB-UE (108) is registered for emergency services, then it should indicate that the MWAB-operation is not allowed to CN in any of the NAS or AS messages (even though subscription data from the UDM (102) indicates it's allowed to operate as the MWAB-UE (108)). In an embodiment of the disclosure, when the MWAB-UE (108) registers for emergency services, the UDM (102) should not indicate in the AMF (104) subscription data that MWAB-operation is allowed. The MWAB-UE (108) should continue with emergency call. When the MWAB-UE (108) registers for emergency services, it shall handover the UEs connected to it to another available gNB fixed or another MWAB-gNB. The UE Configuration Update (i.e., UCU "registered for emergency services") can be indicated with the delay to the AMF (104) / UPF or any other CN entity so that there is no impact on the connected UEs; i.e., Graceful release of all connected UE will take place. In an embodiment of the disclosure, when the UE (402) is registering for emergency service, it should not indicate that it intends to behave as a MWAB-UE (108) / MWAB-gNB (110) to the network in any AS or NAS signalling message.

[0315] Fig. 15 is a sequence diagram that illustrates a scenario for handling multiple UEs connected to a CN via the MWAB-UE (108) according to an embodiment of the disclosure. As shown in the sequence diagram, the AMF (104), the gNB (106), the MWAB-UE (108), the MWAB-gNB (110), the UE 1 (112), the UE 2 (114), and the target gNB (302) are in communication with each other. Consider that the MWAB-UE (108) subscription has expired or the MWAB-UE (108) is getting de-registered due to any network-determined / UE determined procedures / reasons or due to any NAS / AS reject causes or the MWAB-UE (108) authorization state has changed to not authorized, or the MWAB-UE (108) is registering for emergency services and MWAB-operation is not allowed.

[0316] In step 1, the MWAB-UE (108) before getting de-registered / emergency registered / not authorized for MWAB should be indicated with a NAS message (like UCU) that they are not authorized anymore (i.e. MWAB Authorization is ending or has ended) or indicate that it is not allowed to remain registered (for e.g., due to forbidden reasons). This may be indicated via any NAS or AS message or indication, or via a data path.

[0317] In step 2, then the MWAB-UE (108) will indicate / inform the MWAB-gNB (110) that it has to move all the served UEs to other gNBs or to other MWAB-gNBs or it has to release all the connected UEs except the ones having emergency services. Optionally, the MWAB-gNB (110) should stop broadcasting support for normal services at this point. Broadcast and make the gNB barred except for emergency services. In an embodiment of the disclosure, the MWAB-gNB (110) should not accept connection (RRC connection) from any other UE, which is not already connected to the MWAB-gNB (110).

[0318] In step 3, the MWAB-gNB (110) determines that at least one of the connected UE(s) is having an emergency session going on and cannot be released / handed over. The gNB (106) can determine if any of the served UEs is having emergency session, or if any UE triggers emergency session:

[0319] a) The MWAB-gNB (110) interacts with AMF (104) / SMF and / or sends any NAS / AS message to understand if there is any UE which is using emergency service;

[0320] b) Using ARP (Allocation and retention policy as explained in 23.501); and

[0321] c) Using QOS parameters (or N2 information provided to the UE) of the PDU session.

[0322] After determining served UEs with emergency services, the MWAB-gNB (110) / MWAB-UE (108) does one or any combination of following:

[0323] a) Release all the UEs which are not emergency service;

[0324] b) Optionally, broadcast that only emergency services are supported; and

[0325] c) Keep serving all the UEs till emergency services of the determined UE continues.

[0326] Once emergency session is done, those UEs / All UEs are deregistered or released or handed over to target NG-RAN where they can continue with the emergency sessions.

[0327] In step 4, the MWAB-gNB (110) triggers handover of all connected UE(s) which are not having an emergency session to other gNB or releases them. The MWAB-gNB (110) informs the MWAB-UE (108) (or directly to the AMF (104)) that at least one of the connected UE(s) is having an emergency session. All UE(s) not having an emergency session gets handed over to other gNBs or are released by the MWAB-gNB (110). The MWAB-UE (108) indicates to the AMF (104) that it is serving UE(s) which have emergency services going on and it needs to remain registered.

[0328] In step 5, once the UE(s) having emergency services are done with emergency services, the MWAB-gNB (110) hands over those UE(s) to another gNB or releases their connection. All connected UE(s) have now been handed over to other gNBs. The MWAB-gNB (110) informs the MWAB-UE (108) (or directly to the AMF (104)) that the pending emergency sessions have been completed, and all UE(s) have been handed over to other gNBs.

[0329] In step 6, the MWAB-UE (108) indicates (sends acknowledgement) to the AMF (104) via any NAS or AS message that all connected UE(s) have been handed over. This can be via any NAS or AS or any other message or indication.

[0330] In an embodiment of the disclosure, on receiving the indication / ack / UCU complete from MWAB-UE (108), the AMF (104) triggers the de-registration procedure (or indicates changed authorization state to the MWAB UE (108)) of the MWAB-UE (108), or accepts the emergency registration of the MWAB-UE (108).

[0331] In an embodiment of the disclosure, the MWAB-gNB (110) keeps serving all UE(s) till the emergency services are over for all the UEs, and release / handover all UE(s) once the emergency session is done.

[0332] The MWAB-UE (108) / MWAB-gNB (110) has established a PDU session for servicing all connected / served UEs. This PDU session may be for any type / QoS. PDU session of the MWAB-UE (108) / MWAB-gNB (110) need not be emergency type / QoS but it is serving or may serve in future UEs which require emergency services. To support emergency services for all connected / served UEs, MWAB-UE (108) / MWAB-gNB (110) should do at least one of the following:

[0333] A) MWAB-emergency configuration will be provided by OAM server / AMF (104) / UDM (102) or any other 5GC NF in MWAB configuration - DNN+S-NSSAI+FQDN+IP (or any combination of these) address to be used for such a purpose of emergency services. This can be provided to MWAB-UE (108) / MWAB-gNB (110) in URSP rules or part of configuration in NAS or AS message etc.

[0334] B) When any served UE require emergency services, new emergency PDU session has to be established by the MWAB-UE (108) for emergency session of served UE(s).

[0335] C) The MWAB-UE (108) / AMF (104) / SMF or any entity modifies / enhances the QoS of existing PDU session to support emergency services. Modify PDU session procedure can be used for this purpose.

[0336] D) The default MWAB-UE / MWAB-gNB PDU session should support all types of services which the served UEs require.

[0337] E) Alternatively, the MWAB-gNB (110) should broadcast only those services which can be supported by the current MWAB-UE (108) / MWAB-gNB (110) PDU session.

[0338] F) When the serving UE or UE 1 (112) starts an emergency session, the MWAB-gNB (110) indicates to the MWAB-UE (108), if it is establishing an RRC / NAS connection it will use the establishment cause of emergency services in RRC signalling message, so that admission control is as per emergency session can be achieved at the gNB (106) and the AMF (104). In an embodiment of the disclosure, the UE (402) is configured with emergency numbers and only if those numbers are triggered then the UE (402) determines that it's an emergency session but now the MWAB-UE (108) is dependent on the MWAB-gNB (110) to determine that the session is for emergency session.

[0339] The type 'emergency' can be indicated in all NAS or AS messages such as UL NAS TRANSPORT, etc. to indicate emergency type traffic / data / message / signalling / packets.

[0340] For Normal UE (UE connected to MWAB-gNB):

[0341] If the broadcast information on the CAG IDs have changed and optionally, at least one of the CAG-ID broadcasted is not part of the allowed CAG list of the UE (402) or at least one of the CAG-ID part of the allowed CAG list of the UE (402) for this SNPN / PLMN is not broadcasted by the network (gNB or any other RAN node), then the UE (402) connected to the MWAB-gNB (110) shall perform at-least one of the below steps, in any possible combinations or order:

[0342] A) The UE (402) connected to the MWAB-gNB (110) shall trigger a registration procedure with the network on the same or any other PLMN / access technology combinations (after performing PLMN selection), if available and allowable.

[0343] B) The UE (402) shall enter at least one of the 5GMM sublayer states.

[0344] C) The UE (402) connected to the MWAB-gNB (110) shall perform cell selection or cell reselection procedure or perform the PLMN selection procedure as per "PLMN selection as per 23.122 without RPLMN" or "PLMN selection as per 23.122 with RPLMN" to select and attempt registration on the same or other PLMN / access technology combinations, if available and allowable.

[0345] D) The UE (402) connected to the MWAB-gNB (110) shall trigger Deregistration procedure.

[0346] E) The UE (402) will start timer T3540, on expiry of timer T3540 UE will locally release the NAS signalling connection.

[0347] F) If the services are ongoing, the UE (402) connected to the MWAB-gNB (110) shall release the signalling connection locally immediately or optionally after the service is done or after implementation dependent timer (or this timer can be configured by network in at least one of the NAS or AS signalling message).

[0348] G) If the Emergency services are ongoing, the UE (402) connected to the MWAB-gNB (110) shall release the signalling connection locally after the Emergency service is done.

[0349] The UE (402) starts a timer for each CAG (optionally per UE) or CAG list, if the timer associated with CAG ID / list of CAG IDs has expired optionally, at least one of the CAG-ID broadcasted is not part of the allowed CAG list of the UE or at least one of the CAG-ID part of the allowed CAG list of the UE (402) for this SNPN / PLMN is not broadcasted by the network (gNB or any other RAN node), the allowed CAG list, in this case, is the set of CAG IDs which are considered after removing the CAG IDs for which timer is expired, then the UE (402) connected to the MWAB-gNB (110) shall perform at least one of the below steps, in any possible combinations or order:

[0350] A) The UE (402) shall consider that CAG ID(s) which are expired (or not valid anymore) are not part of the allowed CAG list of the UE (402). The UE (402) shall provide the new allowed CAG list to lower layers.

[0351] B) The UE (402) connected to the MWAB-gNB (110) shall trigger a registration procedure with the network on the same or any other PLMN / access technology combinations (after performing PLMN selection), if available and allowable.

[0352] C) The UE (402) shall enter at least one of the 5GMM sublayer states.

[0353] D) The UE (402) connected to the MWAB-gNB (110) shall perform cell selection or cell reselection procedure or perform the PLMN selection procedure as per "PLMN selection as per 23.122 without RPLMN" or "PLMN selection as per 23.122 with RPLMN" to select and attempt registration on the same or other PLMN / access technology combinations, if available and allowable.

[0354] E) The UE (402) connected to the MWAB-gNB (110) shall trigger Deregistration procedure.

[0355] F) The UE (402) shall release the NAS signaling connection locally optionally after waiting for a specific time guided by the timer value. The timer value can be pre-configured or configured by the network in the UE (402) or it can be UE implementation dependent timer.

[0356] G) The UE (402) will start timer T3540, on expiry of timer T3540 UE will locally release the NAS signalling connection.

[0357] H) If the services are ongoing, the UE (402) connected to the MWAB-gNB (110) shall release the signalling connection locally immediately or optionally after the service is done.

[0358] I) If the Emergency services are ongoing, the UE (402) connected to the MWAB-gNB (110) shall release the signalling connection locally after the Emergency service is done.

[0359] For MWAB UE:

[0360] If the MWAB-UE (108) determines that it should stop operating as MWAB (for e.g., based on an indication from 5GC or if the MWAB-UE (108) determines that it has to remain registered for emergency services only), then the MWAB-UE (108) shall perform at least one of the below steps, in any possible combinations or order:

[0361] A) The MWAB-gNB (110) shall indicate the updated CAG information (i.e. CAG ID information is changed) to the UEs (connected to the MWAB-gNB) via any NAS signalling message. (For example, UE Configuration Update Command or UE Provisioning Update Command).

[0362] B) The MWAB-UE (108) shall trigger Deregistration procedure.

[0363] C) The MWAB-UE (108) shall release the NAS / RRC signaling connection locally optionally after waiting for a specific time guided by the timer value. The timer value can be pre-configured or configured in the MWAB-UE (108) / MWAB-gNB (110) by network or it can be MWAB-UE (108) / MWAB-gNB (110) implementation dependent timer.

[0364] D) If the services are ongoing, the MWAB-gNB (110) shall release the signalling connection for the UE (402) immediately or optionally after the service is done.

[0365] E) If the Emergency services are ongoing, the MWAB-gNB (110) shall release the signalling connection locally after the Emergency service is done.

[0366] If the time period / time-slot / time-window / timer for which the UE (402) behaves as the MWAB-gNB (110) / MWAB-UE (108) is expired (i.e. the UE (402) will behave as a Normal UE (UE Without MWAB behaviour)) then the MWAB-UE (108) / MWAB-gNB (110) shall perform at-least one of the below steps, in any possible combinations or order:

[0367] A) The MWAB-gNB (110) shall stop broadcasting the CAG IDs.

[0368] B) The MWAB-gNB (110) shall indicate the updated CAG information (i.e. CAG ID information is changed) to the UEs (connected to the MWAB-gNB) via any NAS signalling message. (For example, UE Configuration Update Command or UE Provisioning Update Command)

[0369] C) The MWAB-gNB (110) shall stop paging the UEs (connected to the MWAB-gNB).

[0370] D) The MWAB-gNB (110) shall trigger Deregistration procedure.

[0371] E) The MWAB-gNB (110) shall release the NAS / RRC signaling connection locally optionally after waiting for a specific time guided by the timer value. The timer value can be pre-configured or configured in the MWAB UE (108) by network or it can be the MWAB-UE (108) implementation dependent timer.

[0372] F) If the services are ongoing, the MWAB-gNB (110) shall release the signalling connection for the UE (402) connected to the MWAB-gNB (110) immediately or optionally after the service is done.

[0373] G) If the Emergency services are ongoing, the MWAB-gNB (110) shall release the signalling connection for the UE (402) connected to the MWAB-gNB (110) after the Emergency service is done.

[0374] The Network (MWAB-gNB (110)) starts a timer for each CAG / list of CAG IDs (optionally per UE (402)) and if the timer associated with CAG ID / list of CAG IDs has expired then the MWAB-gNB (110) shall perform at least one of the below steps, in any possible combinations or order:

[0375] A) The MWAB-gNB (110) shall stop paging the UEs (connected to the MWAB-gNB (110)).

[0376] B) The MWAB-gNB (110) shall trigger Deregistration procedure.

[0377] C) The MWAB-gNB (110) shall release the NAS signaling connection locally optionally after waiting for a specific time guided by the timer value. The timer value can be pre-configured or configured in the MWAB-gNB (110) / MWAB-UE (108) by network or it can be MWAB-gNB (110) / MWAB-UE (108) implementation dependent timer.

[0378] D) If the services are ongoing, the MWAB-gNB (110) shall release the signalling connection locally immediately or optionally after the service is done.

[0379] E) If the Emergency services are ongoing, the MWAB-gNB (110) shall release the signalling connection locally after the Emergency service is done.

[0380] For Network (AMF or any other network entity):

[0381] If the broadcast information on the CAG IDs has changed and optionally, at least one of the CAG-ID broadcasted is not part of the allowed CAG list of the UE (402) (UE (402) connected to the MWAB-gNB (110)) or network determines that MWAB-UE (108) should stop MWAB operation or act as MWAB, then Network shall perform at least one of the below steps, in any possible combinations or order:

[0382] A) The network shall indicate the updated CAG information (i.e. CAG ID information is changed) to the MWAB-gNB (110) / MWAB-UE (108) via any NAS signalling message; (For example, UE Configuration Update Command or UE Provisioning Update Command).

[0383] B) The network shall trigger the Deregistration procedure.

[0384] C) The network shall release the NAS signalling connection locally optionally after waiting for a specific time guided by the timer value. The timer value can be a network implementation dependent timer.

[0385] D) If the services are ongoing, Network shall release the signalling connection locally immediately or optionally after the service is done.

[0386] E) If the Emergency services are ongoing, Network shall release the signalling connection locally after the Emergency service is done.

[0387] If the time period / time-slot / time-window / timer for which the UE (402) behaves as the MWAB-UE (108) / MWAB-gNB (110) is expired (i.e. the UE (402) will behave as a Normal UE (UE (402) Without MWAB behaviour)) then the Network shall perform at least one of the below steps, in any possible combinations or order:

[0388] A) The network shall stop configuring the CAG IDs.

[0389] B) The network shall indicate the updated CAG information (i.e. CAG ID information is changed) to the MWAB-UE (108) / MWAB-gNB (110) via any NAS signalling message. (For example, UE Configuration Update Command or UE Provisioning Update Command).

[0390] C) The network shall stop paging the MWAB-UE (108).

[0391] D) The network shall trigger Deregistration procedure.

[0392] E) Network shall release the NAS signalling connection locally optionally after waiting for a specific time guided by the timer value. The timer value can be pre-configured or configured in the MWAB-UE (108) by network or it can be MWAB-UE (108) implementation dependent timer.

[0393] F) If the services are ongoing, the network shall release the signalling connection locally immediately or optionally after the service is done.

[0394] G) If the Emergency services are ongoing, the network shall release the signalling connection locally after the Emergency service is done.

[0395] The network starts a timer for each CAG (optionally per UE (402)) and if the timer associated with CAG ID has expired then the network shall perform at least one of the below steps, in any possible combinations or order:

[0396] A) The network shall stop paging the MWAB-UE (108).

[0397] B) The network shall trigger Deregistration procedure.

[0398] C) The network shall release the NAS signalling connection locally optionally after waiting for a specific time guided by the timer value. The timer value can be pre-configured or configured in the MWAB-UE (108) by network or it can be MWAB-UE (108) implementation dependent timer.

[0399] D) If the services are ongoing, the Network shall release the signalling connection locally immediately or optionally after the service is done.

[0400] E) If the Emergency services are ongoing, the Network shall release the signalling connection locally after the Emergency service is done.

[0401] Fig. 16 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE (108) in a wireless network by the UE (402) according to an embodiment of the disclosure. The method includes steps (1602-1608). Each step is explained in further detail below.

[0402] At step 1602, the UE (402) generates a registration request message. This message includes an intention of the UE (402) to act as the MWAB-UE (108). The registration request message contains details regarding the UE (402), including its unique identifier, capabilities, and the specific services it aims to utilize. The designation of MWAB-UE (108) signifies that the UE (402) is capable of managing multiple wireless access technologies at the same time, thereby improving its connectivity options and overall efficiency. For example, the registration request message specifies the public land mobile networks (PLMNs) for which the UE (402) intends to function as the MWAB-gNB (110) in relation to the AMF (104).

[0403] At step 1604, the UE (402) transmits the registration request message to the AMF (104). The AMF (104) manages the registration and mobility of the UE (402) within the wireless network. Upon receiving the registration request, the AMF (104) processes the information, verifies the identity of the UE (402), checks for any necessary authentication, and determines whether the registration can be granted based on the current network conditions and policies.

[0404] At step 1606, the UE (402) receives a non-access stratum (NAS) message like registration accept message from the AMF (104). The registration accept message includes a MWAB information and an indication indicating that MWAB operation is allowed. Upon receiving the MWAB information, the MWAB operation is started by the UE (402). For instance, the MWAB information includes a MWAB-authorized information and a MWAB-unauthorized information. The MWAB-authorized information includes an area and a time for which the UE (402) is authorized for MWAB per PLMN. The MWAB-unauthorized information includes an area and a time for which the UE (402) is not authorized for MWAB per PLMN.

[0405] At step 1608, the UE (402) receives a NAS message like registration reject message from the AMF (104). The NAS message like registration rejection request message provides an indication that MWAB operation is not allowed. When the MWAB determines that the UE connects to the MWAB-gNB has initiated an emergency PDU Session, e.g. via AS layer signalling, or based on the ARP of the PDU Session context, the following handling applies:

[0406] The MWAB may decide to reuse the existing BH PDU Session if the existing BH PDU Session has sufficient QoS to support high availability of the N2 / N3 interface.

[0407] The MWAB may decide to establish a new BH PDU Session, if the HPLMN of MWAB-UE has configured it with specific S-NSSAI and DNN for BH PDU Session(s) to serve emergency PDU Session for UEs accessing this MWAB. The emergency PDU Session establishment procedure for the UE(s) should not be interrupted by the establishment of the new BH PDU Session. To avoid interruption of the establishment of the emergency PDU Sessions, the MWAB-gNB should complete of the emergency PDU Session establishment by using the existing BH PDU Sessions for N3 traffic and then trigger PDU Session resource modification procedure for the emergency PDU Sessions of the UE(s) to associate the emergency PDU Session N3 interface to the new BH PDU Session to serve emergency PDU Session for UEs accessing this MWAB. If there are UEs with emergency services, the MWAB-gNB will not stop operating (e.g. due to de-authorization) as MWAB until it handovers the UEs to other cells as described in clause 5.49.3. Based on configuration for the specific S-NSSAI and DNN for BH PDU Session to serve emergency PDU Sessions, the BH PLMN / SNPN and the MWAB attempt to guarantee the resources of the BH PDU session(s) to serve emergency PDU Session in the BH PLMN / SNPN so that they are not be released when MWAB is serving the emergency services.

[0408] Fig. 17 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE (108) in a wireless network by the AMF (104) according to an embodiment of the disclosure. The method includes steps (1702-1708). Each step is explained in further detail below.

[0409] At step 1702, the AMF (104) receives a registration request message from the UE (402). The registration request message indicates an intention of the UE (402) to act as the MWAB-UE (108). The registration request message includes essential information about the UE (402), such as its unique identifier, capabilities, and the specific services it intends to access.

[0410] At step 1704, the AMF (104) determines whether the UE (402) is authorized to act as a MWAB based on subscription data associated with the UE (402). The subscription information encompasses aspects such as the service plan, access permissions, and any particular terms or restrictions that may pertain to the UE (402). Through the analysis of the subscription information, the AMF (104) can determine if the UE (402) fulfils the required standards to be allowed access to the MWAB services.

[0411] At step 1706, the AMF (104) generates a registration accept message including MWAB information and an indication indicating that the MWAB operation is allowed. This message is generated when the UE (402) is authorized to act as the MWAB. The registration accept message is then transmitted to the UE (402).

[0412] At step 1708, the AMF (104) generates a NAS message like registration reject message including an indication indicating that the MWAB operation is not allowed. This message is generated when the MWAB-UE is unauthorized to perform the MWAB operation. The NAS message like registration reject message is then transmitted to the UE (402).

[0413] Fig. 18 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE (108) in a wireless network by the gNB (106) according to an embodiment of the disclosure. The method includes steps (1802-1810). Each step is explained in further detail below.

[0414] At step 1802, the gNB (106) is configured with a specific S-NSSAI and data network name (DNN) for emergency backhaul (BH) sessions. The DNN functions as a key identifier for the data network to which the gNB (106) will link, enabling the effective routing of data packets and ensuring that emergency communications reach the correct network resources. The DNN is essential for sustaining dependable and efficient communication in emergency scenarios, where prompt access to data and services is often critical.

[0415] At step 1804, the gNB (106) detects that the UE (402) is in a CM-IDLE state. When the UE (402) is in the CM-IDLE state, it indicates that the UE (402) is not currently participating in a data session or communicating with the wireless network. Nevertheless, the UE (402) remains registered and is able to receive incoming calls or messages. This state plays a crucial role in preserving battery life and optimizing network resources, as the UE (402) does not sustain a constant connection to the network.

[0416] At step 1806, the gNB (106) receives an RRC connection establishment with an indication of an RRC connection establishment cause code indicating "emergency". In light of the request being classified as an emergency, the gNB (106) gives it precedence over standard connection requests. This prioritization is essential for guaranteeing that emergency services, including those pertaining to public safety or urgent medical care, receive prompt access to network resources.

[0417] At step 1808, the gNB (106) detects the emergency cause code and initiates the establishment or modification of a BH PDU session for emergency support using the configured S-NSSAI and DNN.

[0418] At step 1810, the gNB (106) detects an emergency services ARP value and associating the emergency PDU session for the UE (402) with the emergency BH PDU session. The ARP value plays an important role in establishing the priority for resource allocation and retention within the network, guaranteeing that emergency communications are prioritized over standard traffic.

[0419] Fig. 19 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE (108) in a wireless network by the AMF (104) according to an embodiment of the disclosure. The method includes steps (1902-1908). Each step is explained in further detail below.

[0420] At step 1902, the AMF (104) receives a UECM deregistration notification message from a UDM during an emergency PDU session of the MWAB-UE (108) due to a subscription expiry of the MWAB-UE (108). Upon the expiration of the subscription, several network management actions may be required, one of which could be deregistration of the UE (402) from the network. The emergency PDU session signifies that the MWAB-UE (108) is actively involved in a vital communication process, potentially related to emergency services or the transmission of urgent data.

[0421] At step 1904, the AMF (104) generates an indication message to be transmitted to the MWAB-UE (108) in the form of a NAS message or an AS message. The indication message is generated when MWAB operations are not allowed upon receiving the UECM deregistration notification message. The indication message indicates that the MWAB-UE (108) is allowed to be registered only for emergency services and non-emergency PDU sessions are not allowed.

[0422] At step 1906, the AMF (104) receives a UCU complete message from the MWAB-UE (108) indicating that the MWAB operations have stopped for the serving UEs associated with the MWAB-UE (108). The AMF (104) is thus able to efficiently oversee resources and uphold peak performance for the connected UEs. Following this update, the AMF (104) will take necessary actions, which may involve reassessing the current status of the UEs, modifying resource distributions, or engaging in additional communication with other network elements to guarantee uninterrupted service delivery.

[0423] At step 1908, the AMF (104) generates a UE configuration update command to be transmitted to the MWAB-UE (108) indicating that the MWAB-UE (108) is registered for emergency services. Emergency services can encompass features like emergency calling, location tracking for responders, and other vital communication tools during crises. The UE configuration update command may consist of multiple parameters and settings that provide the MWAB-UE (108) with information regarding its current status, capabilities, and any particular configurations necessary to ensure access to these crucial services.

[0424] Fig. 20 is a flow diagram that illustrates a method for handling authorization of the MWAB-UE (108) in a wireless network according to an embodiment of the disclosure. The method includes steps (2002-2006). Each step is explained in further detail below.

[0425] At step 2002, the MWAB-UE (108) receives a deregistration　message from the AMF (104). The deregistration message specifies that the MWAB-UE (108) must be registered for emergency services, prohibiting any non-emergency PDU sessions. This message provides guidance for the MWAB-UE (108) to enter a mode that restricts its access solely to emergency services. Consequently, the MWAB-UE (108) retains the ability to connect to emergency service networks and utilize functionalities intended for critical situations, but it is not allowed to initiate non-emergency PDU sessions.

[0426] At step 2004, the MWAB-UE (108) performs a clean-up process and handing over the UEs to the NG-RAN (1102). In the course of this clean-up procedure, the MWAB-UE (108) assesses the condition of each UE, confirming that all active transactions are finalized and that the UEs are prepared for transition. This process may include the reallocation of network resources, modification of session states, and informing pertinent network elements of the updates.

[0427] At step 2006, the MWAB-UE (108) transmits a UCU complete message to the AMF (104) indicating that MWAB operations have stopped. The UCU complete message includes all necessary details regarding the current state and configuration of the UEs.

[0428] According to an embodiment of the disclosure, the method further comprises: in case that the UE enters a location or time that the UE is not authorized to act as the MWAB, stopping the MWAB operation.

[0429] According to an embodiment of the disclosure, wherein a subscription information is retrieved by the AMF from an UDM, and wherein the subscription information comprises whether the UE is authorized to act as the MWAB, and associated location and time information.

[0430] According to an embodiment of the disclosure, the method further comprises: in case that the UE is not authorized for the MWAB, receiving, from the AMF, a registration reject message including the MWAB information.

[0431] According to an embodiment of the disclosure, the method further comprises: receiving, from the AMF, a UE configuration update (UCU) message indicating a MWAB authorization status change; and performing deregistration procedure.

[0432] According to an embodiment of the disclosure, the method further comprises: identifying an emergency session for a serving UE based on emergency cause code or an allocation and retention priority (ARP) value; and establishing a backhaul session for emergency, wherein the UE is configured with single-network slice selection assistance information (S-NSSAI), and a data network name (DNN) associated with the backhaul session for emergency.

[0433] According to an embodiment of the disclosure, the method further comprises: receiving, from the AMF, a UCU message indicating that the UE to be registered for an emergency service; performing handover or release procedure associated with a serving UE; transmitting, to the AMF, a UCU complete message indicating that the MWAB operation has stopped; and receiving, from the AMF, a UCU command indicating to be registered for the emergency service, wherein a deregistration notification associated with the UE is triggered from a UDM to the AMF.

[0434] According to an embodiment of the disclosure, the method further comprises: receiving, from the AMF, a UCU message indicating that the UE is unauthorized for the MWAB; identifying an emergency session associated with a serving UE; transmitting, to the AMF, a message indicating that the emergency service is pending; transmitting, to the AMF, a UCU complete message indicating that the emergency service is completed; and performing deregistration procedure.

[0435] According to an embodiment of the disclosure, wherein the at least one processor is further configured to: in case that the UE is not authorized for the MWAB, receive, from the AMF, a registration reject message including the MWAB information.

[0436] According to an embodiment of the disclosure, wherein the at least one processor is further configured to: receive, from the AMF, a UE configuration update (UCU) message indicating a MWAB authorization status change, perform a deregistration procedure.

[0437] According to an embodiment of the disclosure, wherein the at least one processor is further configured to: identify an emergency session for a serving UE based on emergency cause code or an allocation and retention priority (ARP) value, establish a backhaul session for emergency, wherein the UE is configured with single-network slice selection assistance information (S-NSSAI), and a data network name (DNN) associated with the backhaul session for emergency.

[0438] According to an embodiment of the disclosure, wherein the at least one processor is further configured to: receive, from the AMF, a UCU message indicating that the UE to be registered for an emergency service, perform handover or release procedure associated with a serving UE, transmit, to the AMF, a UCU complete message indicating that the MWAB operation has stopped, receive, from the AMF, a UCU command indicating to be registered for the emergency service, wherein a deregistration notification associated with the UE is triggered from a UDM to the AMF.

[0439] According to an embodiment of the disclosure, wherein the at least one processor is further configured to: receive, from the AMF, a UCU message indicating that the UE is unauthorized for the MWAB, identify an emergency session associated with a serving UE, transmit, to the AMF, a message indicating that the emergency service is pending, transmit, to the AMF, a UCU complete message indicating that the emergency service is completed, perform a deregistration procedure. The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:transmitting, to an access and mobility management function (AMF), a registration request message,wherein the registration request message comprises an indication that the UE intends to act as a mobile gNB with wireless access backhauling (MWAB), and a public land mobile network (PLMN) for which the UE wants to act as the MWAB;in case that the UE is authorized for the MWAB, receiving, from the AMF, a registration accept message including MWAB information,wherein the MWAB information comprises information that the MWAB is authorized or not, and area and time information that the UE is authorized or not optionally for per public land mobile network (PLMN); andperforming a MWAB operation based on the area and time information.2.The method of claim 1, further comprising:in case that the UE enters a location or time that the UE is not authorized to act as the MWAB, stopping the MWAB operation.3.The method of claim 1,wherein a subscription information is retrieved by the AMF from an UDM, andwherein the subscription information comprises whether the UE is authorized to act as the MWAB, and associated location and time information.4.The method of claim 1, further comprising:in case that the UE is not authorized for the MWAB, receiving, from the AMF, a registration reject message including the MWAB information.5.The method of claim 1, further comprising:receiving, from the AMF, a UE configuration update (UCU) message indicating a MWAB authorization status change; andperforming deregistration procedure.6.The method of claim 1, further comprising:identifying an emergency session for a serving UE based on emergency cause code or an allocation and retention priority (ARP) value; andestablishing a backhaul session for emergency,wherein the UE is configured with single-network slice selection assistance information (S-NSSAI), and a data network name (DNN) associated with the backhaul session for emergency.7.The method of claim 1, further comprising:receiving, from the AMF, a UCU message indicating that the UE to be registered for an emergency service;performing handover or release procedure associated with a serving UE;transmitting, to the AMF, a UCU complete message indicating that the MWAB operation has stopped; andreceiving, from the AMF, a UCU command indicating to be registered for the emergency service,wherein a deregistration notification associated with the UE is triggered from a UDM to the AMF.8.The method of claim 1, further comprising:receiving, from the AMF, a UCU message indicating that the UE is unauthorized for the MWAB;identifying an emergency session associated with a serving UE;transmitting, to the AMF, a message indicating that the emergency service is pending;transmitting, to the AMF, a UCU complete message indicating that the emergency service is completed; andperforming deregistration procedure.9.A user equipment (UE) in a wireless communication system, the UE comprising:a transceiver; andat least one processor coupled to the transceiver and configured to:transmit, to an access and mobility management function (AMF), a registration request message,wherein the registration request message comprises an indication that the UE intends to act as a mobile gNB with wireless access backhauling (MWAB), and a public land mobile network (PLMN) for which the UE wants to act as the MWAB,in case that the UE is authorized for the MWAB, receive, from the AMF, a registration accept message including MWAB information,wherein the MWAB information comprises information that the MWAB is authorized or not, and area and time information that the UE is authorized or not optionally for per public land mobile network (PLMN),perform a MWAB operation based on the area and time information.10.The UE of claim 9,wherein a subscription information is retrieved by the AMF from an UDM, andwherein the subscription information comprises whether the UE is authorized to act as the MWAB, and associated location and time information.11.The UE of claim 9, wherein the at least one processor is further configured to:in case that the UE is not authorized for the MWAB, receive, from the AMF, a registration reject message including the MWAB information.12.The UE of claim 9, wherein the at least one processor is further configured to:receive, from the AMF, a UE configuration update (UCU) message indicating a MWAB authorization status change,perform a deregistration procedure.13.The UE of claim 9, wherein the at least one processor is further configured to:identify an emergency session for a serving UE based on emergency cause code or an allocation and retention priority (ARP) value,establish a backhaul session for emergency,wherein the UE is configured with single-network slice selection assistance information (S-NSSAI), and a data network name (DNN) associated with the backhaul session for emergency.14.The UE of claim 9, wherein the at least one processor is further configured to:receive, from the AMF, a UCU message indicating that the UE to be registered for an emergency service,perform handover or release procedure associated with a serving UE,transmit, to the AMF, a UCU complete message indicating that the MWAB operation has stopped,receive, from the AMF, a UCU command indicating to be registered for the emergency service,wherein a deregistration notification associated with the UE is triggered from a UDM to the AMF.15.The UE of claim 9, wherein the at least one processor is further configured to:receive, from the AMF, a UCU message indicating that the UE is unauthorized for the MWAB,identify an emergency session associated with a serving UE,transmit, to the AMF, a message indicating that the emergency service is pending,transmit, to the AMF, a UCU complete message indicating that the emergency service is completed,perform a deregistration procedure.

Images