Method and apparatus for managing mwab

Abstract

Embodiments herein disclose methods for managing a MWAB by a MWAB-UE in an electronic device including an MWAB-gNB and the MWAB-UE. The method may comprise receiving configuration information about the MWAB-gNB; and preventing from selecting or reselecting or handover to the MWAB-gNB in the electronic device.

Description

METHOD AND APPARATUS FOR MANAGING MWAB

[0001] Embodiments disclosed herein relate to a wireless communication network, and more particularly to barring a Mobile gNB with wireless access backhaul (MWAB) User Equipment (UE) (MWAB-UE) from selecting / reselecting / handover to its own MWAB-gNB.

[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] A Mobile gNB with wireless access backhaul (MWAB) can be a mobile base station, that acts as a gNB for other UEs and provides access to a 5G network, i.e. providing a NR access link to UEs and connected wirelessly to a 5GC (using a NR) through an internet protocol (IP) connectivity provided by a PDU session established via a NG-RAN cell that a mobile gNB can camp on ((or wireless network (1000)) as depicted in FIG. 1). The PDU session is provided either by a terrestrial Network or by a non-terrestrial network. The mobile gNB may be mounted on a moving vehicle and serve UEs that can be located inside or outside the moving vehicle (or entering / leaving the moving vehicle).

[0009] Consider a scenario, wherein the MWAB-UE (108) is selecting / reselecting / handover to own / self MWAB-gnb. The UE can behave as an MWAB-UE (108) when the UE provides an indication to the network ( e.g. AMF entity (118) or any other network entity) during registration. Based on the UE's subscription data for the MWAB operation or any other information, the selected network entity (for e.g., AMF entity (118) or any other network entity), optionally, performs the MWAB authorization during a UE registration procedure / a UE context setup procedure / a modification procedure. The network may provision the MWAB-gNB (106) with all the required configurations (for e.g., cell id, PLMN, CAG and other configurations) to act as the gNB. Once the MWAB-gNB (106) is provisioned with all the required configurations, the MWAB-gNB (106) shall start acting as the gNB and start broadcasting the MIB and SIB. After the MWAB-gNB (106) is configured and becomes active, the MWAB-UE (108) shall be in a serving range of both the MWAB-gNB (106) and the current serving cell of the MWAB-UE (108). The MWAB-UE (108) may select / reselect or the network may handover to its own / self MWAB-gNB (106) due to any reasons; for example,

[0010] - The MWAB-gNB (106) may have a better signal condition than the cell to which MWAB-UE (108) is currently registered; and

[0011] - The MWAB-gNB (106) may be broadcasting a higher priority PLMN than the cell to which MWAB-UE (108) is currently registered.

[0012] The MWAB-UE (108) shall send the data or / and signalling message to its own MWAB-gNB (106) and the MWAB-gNB (106) will forward the data / signalling message back to the MWAB-UE (108) and the loops will go on infinite. So, data and / or signalling messages sent by the MWAB-UE (108) or / and MWAB-gNB (106) are forwarded into an infinite loop between MWAB-UE (108) and the MWAB-gNB (106). It is not clear how to handle this behaviour of the infinite loop of data or / and signalling message between the MWAB-UE (108) and its own MWAB-gNB (106). Further, the MWAB-UE(s) (108) communicates with a BH-gNB (110) through a NR Uu. The BH-gNB (110) communicates with a BH-5GC (112) through N2 / N3 interface. The BH-5GC (112) communicates with a 5GC servicing UE (114).

[0013] FIG. 2A and FIG. 2B depict an example scenario, wherein a data / signalling message is forwarded into an infinite loop between the MWAB-gNB (106) & the MWAB-UE (108). In step 201, the MWAB-UE (108) performs the registration procedure and indicates its intention to operate as the MWAB-UE (108) in the registration message or any AS / NAS signaling message to the network (for ex- AMF entity (118) or any other network entity) and get registered on cell ID 1 / PLMN 1. In step 202, the MWAB-gNB (106) may get all the required configurations (for e.g., cell id, PLMN, CAG and other configurations) to act as the gNB from the network or a server or may be pre-configured. In step 203, the MWAB-gNB (106) becomes active and starts broadcasting the MIB and SIB with these configurations (for e.g., cell id 2, PLMN 2, CAG and other configurations). In step 204, the MWAB-UE (108) may attempt to select / reselect or the network may handover to its own / self MWAB-gNB (106) due to any reasons; for example,

[0014] - The MWAB-gNB (106) may have a better signal condition than the cell to which MWAB-UE (108) is currently registered; and

[0015] - The MWAB-gNB (106) may be broadcasting a higher priority PLMN than the cell to which MWAB-UE (108) is currently registered.

[0016] It is not clear as to how the MWAB-UE (108) shall send the data or / and signalling message to its own MWAB-gNB (106) and the MWAB-gNB (106) will forward the data / signalling message back to the MWAB-UE (108) and the loops will go on infinite. So, the data and / or signalling messages sent by the MWAB-UE (108) or / and MWAB-gNB (106) is forwarded into the infinite loop between the MWAB-UE (108) and the MWAB-gNB (106).

[0017] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0018] An object of embodiments herein is to disclose methods and systems (or wireless network) for barring a MWAB-UE from selecting / reselecting / handover to its own MWAB-gNB.

[0019] An object of embodiments herein is to disclose that a MWAB-gNB shall not support or / and should not be configured with dedicated S-NSSAI or / and dedicated DNN for MWAB operation. The dedicated S-NSSAI or / and dedicated DNN for MWAB operation can be of the MWAB-UE or the serving UE of the MWAB-gNB.

[0020] An object of embodiments herein is to disclose that an AMF entity may indicate to a gNB that the UE is a MWAB-UE. The MWAB-gNB may indicate that it is a MWAB-gNB to the source gNB or / and to the AMF, optionally when doing Xn or / and N2 handover of the MWAB-UE.

[0021] An object of embodiments herein is to disclose that the AMF entity shall not include the dedicated S-NSSAI or / and dedicated DNN for MWAB operation in the list of allowed S-NSSAI. Optionally, the AMF can reject or / and include the dedicated S-NSSAI or / and dedicated DNN for MWAB operation in the list of Rejected S-NSSAI in any AS or / and NAS message (for example,　Registration Accept, Service Accept, Attach Accept, and so on), if the request is from the MWAB-gNB or / and if the AMF determines that the Requesting UE is connected / camped to a MWAB-gNB.

[0022] An object of embodiments herein is to disclose that the MWAB-gNB may broadcast or indicate an identifier to indicate that it is a MWAB-gNB (for e.g. a new information element (IE)) and not a normal gNB in any broadcast message (for e.g. SIB or MIB) or any AS or NAS message. The MWAB-UE shall not attempt to select or / and reselect and / or handover to the cells that broadcast these MWAB-gNB identifier i.e. bar a cell of the MWAB-gNB.

[0023] According to an embodiment of the present disclosure, a method for managing mobile gNB with wireless access backhaul (MWAB) by an MWAB-user equipment (UE) in an electronic device including an MWAB-gNB and the MWAB-UE is provided. The method may comprise receiving configuration information about the MWAB-gNB; and preventing from selecting or reselecting or handover to the MWAB-gNB in the electronic device.

[0024] Preventing from selecting or reselecting or handover to the MWAB-gNB may comprise attempting to select or reselect or handover to a cell of a gNB or the gNB which does not broadcast information indicating that the gNB is an MWAB-gNB.

[0025] Preventing from selecting or reselecting or handover to the MWAB-gNB may comprise attempting to select or reselect or handover to a cell of a gNB or the gNB which broadcasts information indicating that the gNB is a normal gNB.

[0026] Preventing from selecting or reselecting or handover to the MWAB-gNB may comprise not attempting to select or reselect or handover to a cell which broadcasts information indicating that the gNB is an MWAB-gNB.

[0027] Preventing from selecting or reselecting or handover to the MWAB-gNB may comprise not attempting to select or reselect or handover to a cell of a gNB or the gNB which broadcasts information indicating that the gNB is an MWAB-gNB.

[0028] The configuration information may include at least one of closed access group (CAG) information, a cell identifier (ID), a public land mobile network (PLMN) ID, a tracking area identity (TAI). Preventing from selecting or reselecting or handover to the MWAB-gNB may comprise adding the configuration information in a forbidden list and not attempting to select or reselect or handover based on the forbidden list.

[0029] The configuration information may be transmitted by the MWAB-gNB through a master information block (MIB) or a system information block (SIB).

[0030] The configuration information may be received from an access and mobility management function through a UE configuration update message or a UE parameters update message or an access stratum (AS) message or a non-access stratum (NAS) message.

[0031] According to an embodiment of the present disclosure, a managing mobile gNB with wireless access backhaul (MWAB)-user equipment (UE) in an electronic device including an MWAB-gNB and the MWAB-UE. The MWAB-US may comprise a communicator; and at least one processor coupled to the communicator. The at least one processor may be configured to receive configuration information about the MWAB-gNB, and prevent from selecting or reselecting or handover to the MWAB-gNB in the electronic device.

[0032] Accordingly, the embodiments herein provide a method for managing mobile gNB with wireless access backhaul (MWAB). The method includes transmitting, by a gNB, an identifier indicating that the gNB is a normal gNB or a MWAB-gNB in a message. Further, the method includes transmitting, by a MWAB-gNB, an identifier indicating that the MWAB-gNB is the MWAB-gNB in the message. Further, the method includes receiving, by a MWAB-UE, the identifier indicating that the gNB is the normal gNB or the MWAB-gNB in the message from the gNB. Further, the method includes receiving, by the MWAB-UE, the identifier indicating that the MWAB-gNB is the MWAB-gNB in the message from the MWAB-gNB. Further, the method includes determining, by the MWAB-UE, that the received identifier indicates that the gNB is the MWAB-gNB and not a normal gNB in the message received from the gNB. Further, the method includes performing, by the MWAB-UE, at least one of: the MWAB-UE attempts to select or reselect or handover to at least one of: a cell and the gNb that does not broadcast the identifier associated with MWAB-gNB, the MWAB-UE attempts to select or reselect or handover to at least one of the cell and the gNB that broadcasts the identifier that the gNB is the normal gNB, the MWAB-UE does not attempt to select or reselect or handover to at least one cell and gNB that broadcasts the identifier that the MWAB-gNB is the MWAB-gNB, and the MWAB-UE bar at least one of: a network identifier, the cell and the gNB that broadcasts the identifier that the MWAB-gNB is the MWAB-gNB.

[0033] In an embodiment, the message includes at least one of: a broadcast message and a signalling message. The broadcast message and the signalling message includes at least one of: a system information block (SIB) message, a master information block (MIB) message, a non-access stratum (NAS) message and an access stratum (AS) message. The network identifier is a network parameter. The network parameter includes at least one of: frequency, a Physical Cell Identifier (PCI), band, E-UTRA, Absolute Radio Frequency Channel Number (EARFCN), Absolute Radio Frequency Channel Number (ARFCN), a radio access technology (RAT), and Access.

[0034] Accordingly, the embodiments herein provide a method for managing mobile gNB with wireless access backhaul (MWAB). The method includes configuring, by a network entity in a MWAB-gNB, at least one of: the MWAB-gNB does not support and the MWAB-gNB is not configured with at least one of: a dedicated Single Network Slice Selection Assistance Information (S-NSSAI) for a MWAB operation and a Data Network Name (DNN) for the MWAB operation. At least one of: the dedicated S-NSSAI and the DNN for the MWAB operation belongs to one of: a MWAB-UE or a serving UE of the MWAB-gNB. Further, the method includes managing, by the MWAB-gNB, the MWAB based on the configuration.

[0035] In an embodiment, the method includes determining, by the MWAB-gNB, at least one of: an AS signaling message or a NAS signaling message from the UE requesting at least one of: the dedicated S-NSSAI for the MWAB operation and the DNN for the MWAB operation. Further, the method includes performing, by the MWAB-gNB, at least one of: rejecting the request in at least one of: the AS signaling message and the NAS signaling message, including in at least one of: the AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of rejected S-NSSAI, and not including in at least one of: AS signaling message and the NAS signaling message in at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of allowed S-NSSAI.

[0036] Accordingly, the embodiments herein provide a method for managing MWAB. The method includes receiving, by an Access & Mobility Management Function (AMF) entity, at least one of: an AS signaling message and a NAS signaling message from at least one of: a UE requesting at least one of: a dedicated S-NSSAI for a MWAB operation and a DNN for a MWAB operation and a gNB requesting for at least one of a serving UE at least one of: the dedicated S-NSSAI) for the MWAB operation and the DNN for the MWAB operation. Further, the method includes determining, by the AMF entity, that the request is received from the MWAB-gNB and the requesting UE is connected or camped to the MWAB-gNB. Further, the method includes managing, by the AMF entity, the MWAB, based on the determination, by performing, by the AMF entity, at least one of: rejecting the request in at least one of: the AS signaling message and the NAS signaling message, including in at least one of: AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of rejected S-NSSAI; and not including in at least one of: the AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of allowed S-NSSAI.

[0037] Accordingly, the embodiments herein provide a method for managing MWAB. The method includes determining, by at least one of: a source gNB entity and an AMF entity, that a handover procedure is initiated or ongoing for a MWAB-UE. Further, the method includes indicating, by at least one of: the source gNB entity and the AMF entity, to a target gNB, that the UE for which handover is requested is the MWAB-UE. Further, the method includes determining, by the target gNB, that the target gNB is a MWAB-gNB based on the handover request received from the MWAB-UE. Further, the method includes performing at least one of: indicating, by the target gNB, to at least one of the source gNB entity and the AMF entity, that the target gNB is the MWAB-gNB; and rejecting, by the target gNB, the handover procedure of the MWAB-UE to at least one of the source gNB entity and the AMF entity. Further, the method includes performing, by at least one of: the source gNB entity and the AMF entity, based on at least one of a reject message for the handover procedure from the target gNB or the indication that the target gNB is the MWAB-gNB, at least one of: rejecting the handover procedure of the MWAB-UE to the target gNB; and selecting another target gNB, other than the current selected target gNB, for the handover procedure of MWAB-UE.

[0038] In an embodiment, the handover procedure is at least of: an Xn handover of the MWAB-UE and a N2 handover of the MWAB-UE.

[0039] Accordingly, the embodiments herein provide a MWAB-UE includes a MWAB controller coupled with a processor and a memory. The MWAB controller is configured to receive an identifier indicating that a gNB is a normal gNB or a MWAB-gNB in a message from the gNB. Further, the MWAB controller is configured to receive an identifier indicating that the MWAB-gNB is the MWAB-gNB in the message from the MWAB-gNB. Further, the MWAB controller is configured to determine that the received identifier indicates that the gNB is the MWAB-gNB and not a normal gNB in the message received from the gNB. In an embodiment, the MWAB controller is configured to perform that the MWAB-UE attempts to select or reselect or handover to at least one of: a cell and the gNb that does not broadcast the identifier associated with MWAB-gNB. In another embodiment, the MWAB controller is configured to perform that the MWAB-UE attempts to select or reselect or handover to at least one of the cell and the gNB that broadcasts the identifier that the gNB is the normal gNB. In another embodiment, the MWAB controller is configured to perform that the MWAB-UE does not attempt to select or reselect or handover to at least one cell and gNB that broadcasts the identifier that the MWAB-gNB is the MWAB-gNB. In another embodiment, the MWAB controller is configured to perform that the MWAB-UE bar at least one of: a network identifier, the cell and the gNB that broadcasts the identifier that the MWAB-gNB is the MWAB-gNB.

[0040] Accordingly, the embodiments herein provide a MWAB-gNB including a MWAB controller, coupled with a processor and a memory. The MWAB controller is configured to configure at least one of: the MWAB-gNB does not support and the MWAB-gNB is not configured with at least one of: a dedicated Single Network Slice Selection Assistance Information (S-NSSAI) for a MWAB operation and a Data Network Name (DNN) for the MWAB operation, wherein at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation belongs to one of: a MWAB-UE or a serving UE of the MWAB-gNB. Based on the configuration, the MWAB controller is configured to manage the MWAB.

[0041] Accordingly, the embodiments herein provide an AMF entity including a MWAB controller coupled with a processor and a memory. Further, the MWAB controller is configured to receive at least one of: an AS signaling message and a NAS signaling message from at least one of: a UE requesting at least one of: a dedicated S-NSSAI for a MWAB operation and a DNN for a MWAB operation and a gNB requesting for at least one of a serving UE at least one of: the dedicated S-NSSAI for the MWAB operation and the DNN for the MWAB operation. Further, the MWAB controller is configured to determine that the request is received from the MWAB-gNB and the requesting UE is connected or camped to the MWAB-gNB. Further, the MWAB controller is configured to manage the MWAB, based on the determination, by performing, at least one of: rejecting the request in at least one of: the AS signaling message and the NAS signaling message, including in at least one of: AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of rejected S-NSSAI, and not including in at least one of: the AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of allowed S-NSSAI.

[0042] Accordingly, the embodiments herein provide a wireless network including at least one of: a source gNB entity and an AMF entity, determining that a handover procedure is initiated or ongoing for a MWAB-UE. The at least one of: the source gNB entity and the AMF entity, indicates, to a target gNB, that the UE for which handover is requested is the MWAB-UE. The target gNB, determines, that the target gNB is a MWAB-gNB based on the handover request received from the MWAB-UE. In an embodiment, the target gNB indicates to at least one of the source gNB entity and the AMF entity, that the target gNB is the MWAB-gNB. In another embodiment, the target gNB, rejects, the handover procedure of the MWAB-UE to at least one of the source gNB entity and the AMF entity. In another embodiment, at least one of: the source gNB entity and the AMF entity, perform, based on at least one of a reject message for the handover procedure from the target gNB or the indication that the target gNB is the MWAB-gNB, at least one of: reject the handover procedure of the MWAB-UE to the target gNB; and select another target gNB, other than the current selected target gNB, for the handover procedure of MWAB-UE.

[0043] 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 at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the scope thereof, and the embodiments herein include all such modifications.

[0044] Embodiments herein 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 following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0045] FIG. 1 depicts a MWAB session, according to existing arts;

[0046] FIG. 2A and FIG. 2B depict an example scenario, wherein a data / signalling message is forwarded into an infinite loop between a MWAB-gNB and a MWAB-UE, according to existing arts;

[0047] FIG. 3A, FIG. 3B and FIG. 3C depict an example scenario, where the MWAB-UE selects / reselects / handover to own / self MWAB-gNB, according to embodiments as disclosed herein;

[0048] FIG. 4A and FIG. 4B depict a scenario, in which a network side handles a handover or / and redirection or / and mobility restriction for the MWAB-UE to its own MWAB-gNB, according to embodiments as disclosed herein;

[0049] FIG. 5 is a sequence diagram depicting the process of managing the MWAB-gNB, according to embodiments as disclosed herein;

[0050] FIG. 6A and FIG. 6B are another sequence diagram depicting the process of managing the MWAB-gNB, according to embodiments as disclosed herein;

[0051] FIG. 7A and FIG. 7B depict an example sequence diagram of managing the MWAB, according to embodiments as disclosed herein;

[0052] FIG. 8 shows various hardware components of a MWAB-UE, according to embodiments as disclosed herein;

[0053] FIG. 9 shows various hardware components of the MWAB-gNB, according to embodiments as disclosed herein;

[0054] FIG. 10 shows various hardware components of an AMF entity, according to embodiments as disclosed herein;

[0055] FIG. 11 is a flow chart illustrating a method, implemented by the MWAB-UE, for managing the MWAB, according to embodiments as disclosed herein;

[0056] FIG. 12 is a flow chart illustrating a method, implemented by the MWAB-gNB, for managing the MWAB, according to embodiments as disclosed herein;

[0057] FIG. 13 is a flow chart illustrating a method, implemented by the AMF entity, for managing the MWAB, according to embodiments as disclosed herein; and

[0058] FIG. 14 is a flow chart illustrating a method for managing the MWAB, according to embodiments as disclosed herein.

[0059] 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. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0060] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.,", "i.e.," are merely used herein to mean "serving as an example, instance, or illustration. Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0061] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be 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 may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more 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 may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0062] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0063] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0064] The embodiments herein achieve methods and systems (or wireless network) for barring a MWAB-UE from selecting / reselecting / handover to its own MWAB-gNB.

[0065] In an embodiment, the MWAB-gNB shall not support or / and should not be configured with dedicated S-NSSAI or / and dedicated DNN for MWAB operation. This dedicated S-NSSAI or / and dedicated DNN for MWAB operation can be of the MWAB-UE or the serving UE of the MWAB-gNB.

[0066] In an embodiment, the AMF entity may indicate to the gNB that the UE is a MWAB-UE. The MWAB-gNB may indicate that it is a MWAB-gNB to the source gNB or / and to the AMF entity, optionally when doing Xn or / and N2 handover of the MWAB-UE.

[0067] In an embodiment, the AMF entity shall not include the dedicated S-NSSAI or / and dedicated DNN for MWAB operation in the list of allowed S-NSSAI. Optionally, the AMF entity can reject or / and include the dedicated S-NSSAI or / and dedicated DNN for MWAB operation in the list of Rejected S-NSSAI in any AS or / and NAS message (for example, Registration Accept, Service Accept, Attach Accept, and so on), if the request is from the MWAB-gNB or / and if the AMF entity determines that the Requesting UE is connected / camped to a MWAB-gNB.

[0068] In an embodiment, the MWAB-gNB may broadcast or indicate an identifier to indicate that it is a MWAB-gNB (for e.g. a new IE) and not a normal gNB in any broadcast message (for e.g. SIB or MIB) or any AS or NAS message. The MWAB-UE shall not attempt to select or / and reselect and / or handover to the cells that broadcast these MWAB-gNB identifier i.e. bar the cells of MWAB-gNB.

[0069] Without the proposed method, the MWAB-UE may (re-) select / camp / register / Handover on its own MWAB-gNB and any data or / and signalling messages will be in infinite loop between the MWAB-UE and the MWAB-gNB. Based on the proposed method, the MWAB-UE shall not camp / access on its own MWAB-gNB to avoid infinite loop. Optionally, the method can be used to avoid multi-hop backhauling by restricting access to other gNb. This will help to provide uninterrupted service to the MWAB-UE.

[0070] Referring now to the drawings, and more particularly to FIGS. 3A through 14, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0071] The following definitions and abbreviations have been referred to herein:

[0072] 3GPP: Third Generation Partnership Project

[0073] 5GC: 5G Core

[0074] 5GCN: 5G Core Network

[0075] 5GMM: 5G Mobility Management

[0076] 5GS: 5G System

[0077] 5GSM: 5GS Session Management

[0078] AMF: Access and Mobility Management Function

[0079] AS: Access Stratum

[0080] CAG: Closed access group

[0081] CAG ID: Closed Access Group Identifier

[0082] DL: Downlink

[0083] DU: Distributed Unit

[0084] EHPLMN: Equivalent Home Public Land Mobile Network

[0085] EMM: EUTRA Mobility Management

[0086] eNB: Evolved Node-B

[0087] EPLMN: Equivalent Public Land Mobile Network

[0088] EPS: Evolved Packet System

[0089] eSIM: embedded Subscriber Identity Module

[0090] E-UTRA: Evolved Universal Mobile Telecommunication Access

[0091] EUTRAN: Evolved Universal Mobile Telecommunication Access Network

[0092] FPLMN: Forbidden Public Land Mobile Network

[0093] GEO: Geostationary Orbit

[0094] GERAN: GSM Edge Radio Access Network

[0095] GERAN EC-GSM-IoT: GSM Edge Radio Access Network Extended Coverage - GSM - Internet of Things

[0096] gNB: Next generation Node-B

[0097] GPRS: General Packet Radio Service

[0098] GSM: Global System for Mobile Communication

[0099] HPLMN: Home Public Land Mobile Network

[0100] IAB: Integrated access and backhaul

[0101] IAB-UE: The part of the IAB node that supports the Uu interface towards the IAB-donor or another parent IAB-node (and thus manages the backhaul connectivity with either PLMN or SNPN it is registered with) is referred to as an IAB-UE.

[0102] IE: Information Element

[0103] LEO: Low Earth Orbit

[0104] MBSR: Mobile Base Station Relay

[0105] MCC: Mobile Country Code

[0106] ME: Mobile Equipment

[0107] MEO: Medium Earth Orbit

[0108] MME: Mobility Management Entity

[0109] MNC: Mobile Network Code

[0110] MS: Mobile Station. The present document makes no distinction between MS and UE.

[0111] MWAB: Mobile Wireless Access Backhaul

[0112] NAS: Non-Access Stratum

[0113] NB-S1 Mode: Narrow Band with S1 Interface

[0114] NG-RAN: Next Generation Radio Access Network

[0115] NPN: Non-Public Networks

[0116] NR: New Radio

[0117] NTN: Non Terrestrial Networks

[0118] NW: Network

[0119] PDU: Packet Data Unit

[0120] PLMN ID: Public Land Mobile Network Identity

[0121] RAT: Radio Access Technology

[0122] RPLMN: Registered Public Land Mobile Network

[0123] RRC: Radio Resource Control

[0124] RU: Registration Update

[0125] SAT: Satellite

[0126] Satellite: An artificial body placed in orbit round the earth or moon or another planet in order to collect information or for communication.

[0127] Satellite Constellation: Group of satellites, placed in orbit round the earth or moon or another planet in order to collect information or for communication.

[0128] Service User: An individual who has received a priority level assignment from a regional / national authority (i.e., an agency authorised to issue priority assignments) and has a subscription to a mobile network operator

[0129] SIM: Subscriber Identity Module

[0130] SNPN: Standalone Non-Public Networks

[0131] SW: Software

[0132] TAC: Tracking Area Code

[0133] TAI: Tracking Area Identity

[0134] TAU: Tracking Area Update

[0135] TER: Terrestrial

[0136] TN: Terrestrial Networks

[0137] UCU: UE Configuration Update

[0138] UDM: Unified Data Management Function

[0139] UE: User Equipment

[0140] UL: Uplink

[0141] ULI: User Location Information

[0142] UPU: UE Parameters Update

[0143] USIM: Universal Subscriber Identification Module

[0144] Uu: The radio interface between the UE and the Node B

[0145] VPLMN: Visited Public Land Mobile Network

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

[0147] Allowable PLMN: In the case of an 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.

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

[0149] Camped on a cell: The MS (ME if there is no 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 SNPN may not be aware of the existence of the MS (ME) within the chosen cell.

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

[0151] 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 IMSI for PLMN selection purposes. This list is stored on the 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.

[0152] Home PLMN: This is a PLMN where the MCC and MNC of the PLMN identity match the MCC and MNC of the IMSI.

[0153] 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.

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

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

[0156] 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)

[0157] Examples of the 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, REGISTRATION ACCEPT, DEREGISTRATION ACCEPT, SERVICE REJECT, SERVICE ACCEPT, UE CONFIGURATION UPDATE command, UE PARAMETERS UPDATE command, and so on.

[0158] The term 5GMM sublayer statesin this embodiment are at least one of the below:

[0159] 5GMM-NULL

[0160] 5GMM-DEREGISTERED

[0161] - 5GMM-DEREGISTERED.NORMAL-SERVICE

[0162] - 5GMM-DEREGISTERED.LIMITED-SERVICE

[0163] - 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION

[0164] - 5GMM-DEREGISTERED.PLMN-SEARCH

[0165] - 5GMM-DEREGISTERED.NO-SUPI

[0166] - 5GMM-DEREGISTERED.NO-CELL-AVAILABLE

[0167] - 5GMM-DEREGISTERED.eCALL-INACTIVE

[0168] - 5GMM-DEREGISTERED.INITIAL-REGISTRATION-NEEDED

[0169] 5GMM-REGISTERED-INITIATED

[0170] 5GMM-REGISTERED

[0171] - 5GMM-REGISTERED.NORMAL-SERVICE

[0172] - 5GMM-REGISTERED.NON-ALLOWED-SERVICE

[0173] - 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE

[0174] - 5GMM-REGISTERED.LIMITED-SERVICE

[0175] - 5GMM-REGISTERED.PLMN-SEARCH

[0176] - 5GMM-REGISTERED.NO-CELL-AVAILABLE

[0177] - 5GMM-REGISTERED.UPDATE-NEEDED

[0178] 5GMM-DEREGISTERED-INITIATED

[0179] 5GMM-SERVICE-REQUEST-INITIATED

[0180] In this embodiment, the term EMM sublayer states are at least one of the below:

[0181] EMM-NULL

[0182] EMM-DEREGISTERED

[0183] - EMM-DEREGISTERED.NORMAL-SERVICE

[0184] - EMM-DEREGISTERED.LIMITED-SERVICE

[0185] - EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH

[0186] - EMM-DEREGISTERED.PLMN-SEARCH

[0187] - EMM-DEREGISTERED.NO-IMSI

[0188] - EMM-DEREGISTERED.ATTACH-NEEDED

[0189] - EMM-DEREGISTERED.NO-CELL-AVAILABLE

[0190] - EMM-DEREGISTERED.eCALL-INACTIVE

[0191] EMM-REGISTERED-INITIATED

[0192] EMM-REGISTERED

[0193] - EMM-REGISTERED.NORMAL-SERVICE

[0194] - EMM-REGISTERED.ATTEMPTING-TO-UPDATE

[0195] - EMM-REGISTERED.LIMITED-SERVICE

[0196] - EMM-REGISTERED.PLMN-SEARCH

[0197] - EMM-REGISTERED.UPDATE-NEEDED

[0198] - EMM-REGISTERED.NO-CELL-AVAILABLE

[0199] - EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM

[0200] - EMM-REGISTERED.IMSI-DETACH-INITIATED

[0201] EMM-DEREGISTERED-INITIATED

[0202] EMM-TRACKING-AREA-UPDATING-INITIATED

[0203] EMM-SERVICE-REQUEST-INITIATED

[0204] The term RAT as defined in this embodiment can be one of the following: NG-RAN, 5G, 4G, 3G, 2G, EPS, 5GS, NR, NR in unlicensed bands, NR(LEO) satellite access, NR(MEO) satellite access, NR(GEO) satellite access, NR(OTHERSAT) satellite access, NR RedCap, E-UTRA, E-UTRA in unlicensed bands, NB-IoT, WB-IoT, LTE-M, and so on

[0205] 5GS registration type can be, but not limited to, initial registration, mobility registration updating, periodic registration updating, emergency registration, SNPN onboarding registration, disaster roaming initial registration, disaster roaming mobility registration updating, and so on.

[0206] PLMN selection as per 23.122 without RPLMN:

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

[0208] - 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);

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

[0210] - 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);

[0211] - other PLMN / access technology combinations with received high quality signal in random order; and

[0212] - other PLMN / access technology combinations in order of decreasing signal quality.

[0213] PLMN selection as per 23.122 with RPLMN:The MS selects and attempts registration on any PLMN / access technology combinations, if available and allowable, in the following order:

[0214] either the RPLMN or the Last registered PLMN;

[0215] 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);

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

[0217] 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);

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

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

[0220] A Closed Access Group (CAG) identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. The 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).

[0221] Applicable time slot / timer for CAG IDis 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 consists 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.

[0222] 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, the UE will not access the CAG.

[0223] CAG IDs expiration information is the information of expiry of all the CAG-IDs configured in the UE.

[0224] The methods, issues or solutions disclosed in this 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 this 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.

[0225] 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 entity (118) with a MME, g-nodeB with e-nodeB, a UDM entity (120) with Home Subscriber Server　(HSS) etc. But principles of the solution remains same.

[0226] The network used in this embodiment is explained using any 5G core network function for e.g., AMF entity. 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.

[0227] The messages used or indicated in this 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.

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

[0229] The term area as used in this 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.

[0230] 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

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

[0232] The term Bar or / and Barring or / and Restricting used in this embodiment may refer to Barring per cell or / and per TAI or / and per PLMN or / and per CAG. That is UE shall consider them as forbidden and does not select, reselect or network will not handover.

[0233] Further, the mobility restrictions consists of RAT restriction, Forbidden Area, Service Area Restrictions, Core Network type restriction and Closed Access Group information, as defined in spec 23.501.

[0234] FIGS. 3A to 3C depict an example scenario, wherein the MWAB-UE (108) selects / reselects / handover to own / self MWAB-gNB (106). In step 301, the MWAB-UE (108) performs the registration procedure and indicates its intention to operate as a MWAB-UE (108) in a registration message or any AS / NAS signaling message to the network (for example, AMF entity (118) or any other network entity) and get registered on cell ID 1 / PLMN 1.

[0235] In step 302, the MWAB-gNB (106) may get all the required configurations (for e.g., Cell id, PLMN, CAG and other configurations) to act as a gNB from the network or server or may be pre-configured. In step 303, the MWAB-gNB (106) becomes active and starts broadcasting the MIB and SIB with these configurations (for e.g., Cell id 2, PLMN 2, CAG and other configurations).

[0236] In step 304, the MWAB-UE / MWAB-gNB / network may follow any of the below mechanisms to bar the MWAB-UE (108) from selecting / reselecting / handover to its own / self MWAB-gNB (106) in any of the below combinations:

[0237] 4a) The MWAB-UE (108) shall not support the CAG mechanism when acting as MWAB-UE / MWAB, i.e., it should not select / reselect to a CAG cell.

[0238] 4b) MWAB-gNB (106) shall provide its area information e.g., CAG information or cell id or PLMN ID and / or TAI and / or CAG information to the MWAB-UE (108). The MWAB-UE (108) may add this information in the forbidden list and shall bar those cells or / and PLMN or / and TAI or / and CAG broadcasting respective area information. The MWAB-UE (108) may optionally indicate to the NG-RAN or / and 5GC (for example, AMF, UDM entity (120) or any other NF) this forbidden information, the 5GC uses this for handover restrictions.

[0239] 4c). The AMF entity (118) (or any other NF) using UPU or UCU or any other NAS message or data path (using PDU session and DNN), indicates to MWAB-UE (108) the cells(s) information (for e.g., cell id, PLMN, TAI, CAG information, area) broadcasted by its own MWAB-gNB, so that the MWAB-UE (108) may add this information in a forbidden list and shall bar those cells or / and PLMN or / and TAI or / and CAG broadcasting respective area information.

[0240] 4d) The MWAB-gNB (106) shall broadcast or indicate an identifier to indicate that it is a MWAB-gNB (106) (for e.g., using separate or dedicated subset value in the CAG-ID and not including this CAG-ID) and not a normal gNB in any broadcast message (for e.g., SIB or MIB) or any AS or NAS message. The MWAB-UE (108) shall not attempt to select or / and reselect and / or handover to the cells that broadcast this MWAB-gNB (106) identifier; i.e., bar the cells of the MWAB-gNB (106).

[0241] This MWAB-gNB (106) identifier can be:

[0242] - specific to this MWAB of which MWAB-UE (108) is part of, in such a configuration the MWAB-UE (108) bars the cells of this MWAB-gNB (106).

[0243] - Common to all MWAB-gNBs in such a case MWAB-UE (108) may not select any of the MWAB-gNB (106) cells.

[0244] - specific to this MWAB of which MWAB-UE (108) is not part of, in such a configuration the MWAB-UE (108) bars the cells of this MWAB-gNB (106).

[0245] In summary, using the MWAB-gNB identifier, the MWAB-UE (108) bars the respective cells which indicates the MWAB-gNB (106) identifier it can be part of its own MWAB or optionally some other MWAB.

[0246] The MWAB-UE (108) identifies the MWAB-gNB identifier by at least one of the below mechanisms:

[0247] - is pre-configured in the MWAB-UE (108).

[0248] - MWAB-gNB (106) informs the MWAB-UE (108) within MWAB.

[0249] - 5GC NF like AMF, SMF, the UDM entity (120) or any other 5GC NF or AF informs the MWAB-UE (108) using at least one of the NAS(5GMM or 5GSM procedure) or AS procedure as defined in TS 24.501 / TS 23.501 / TS 23.402 or using UE parameter update procedure as described in TS 23.501 or using steering of roaming procedure as described in TS 23.122 or using the data path using PDU session for e.g. DNN / S-NSSAI.

[0250] - It can be part of the broadcast information by the MWAB-gNB (106) or any other NG-RAN.

[0251] - Or any other mechanism.

[0252] 4e) The AMF entity (118) (or any other NF e.g., UDM) should not configure the CAG-IDs which are broadcasted by the MWAB-gNB (106) in the Allowed CAG list (i.e., CAG cell is not authorized based on the "allowed CAG list") of the MWAB-UE (108). That is, the cell should be part of CAG restrictions and should not be allowed to be accessed by the MWAB-UE (108). The CAG restrictions are defined below:

[0253] The CAG Restrictions applied to the UE (102) in accessing a PLMN's 5GCN via:

[0254] a non-CAG cell if the entry for the PLMN in the UE's "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells"; or

[0255] a CAG cell if none of the CAG-ID(s) supported by the CAG cell is authorized based on the "allowed CAG list" for the PLMN in the UE's "CAG information list".

[0256] 4f) The MWAB-gNB (106) shall reject or indicate using any data or / and signalling message(AS message) from the UE (102) indicating or / and requesting to operate as MWAB-UE (108) in any of AS or NAS message. The MWAB-UE (108) shall identify that the current camped cell belongs to MWAB-gNB (106) and it should bar that cell.

[0257] The MWAB-gNB (106) shall broadcast or indicate the identifier to indicate that it is a MWAB-gNB (106) (for e.g., using separate or dedicated subset value in the CAG-ID and by not including such CAG-IDs as part of an authorized list of the "allowed CAG list" for the MWAB-UE (108). i.e. such cells or CAG cells are barred from selecting for MWAB-UE (108).

[0258] This barring may be per PLMN or / and per cell or / and per TAI or / and per CAG. This barring is applicable only when the UE (102) is registered for MWAB services or PDU session is established for MWAB services. The UE (102) shall delete or / and remove or / and replace this cells or / and PLMN or / and TAI or / and CAG information from the forbidden list when acting as normal UE or / and whenever the MWAB-gNB configurations are changed (for e.g., the cell id, PLMN or CAG information or any authorization state or / and subscription change).

[0259] Optionally, in all of the above solutions, the MWAB-gNB (106) may not be the own / self MWAB-gNB (106) of the MWAB-UE (108) (i.e., it can be MWAB-gNB (106) of any other MWAB-UE).

[0260] In an embodiment, the term cell select / cell selection is used but it can also be cell reselection / cell handover or PLMN selection all those procedures can be used interchangeably without changing the scope of the idea.

[0261] In this embodiment, the term cell barring is used which implies the UE (102) does not perform cell selection / cell reselection / cell handover or PLMN selection on the respective cell / area / TAI / PLMN. Optionally, the barring can be only for the MWAB services when the UE wants to act as the MWAB-UE (108).

[0262] FIG. 4A and FIG. 4B depict a scenario in which a network side handles handover or / and redirection or / and mobility restriction for the MWAB-UE (108) to its own MWAB-gNB). In step 401, the MWAB-gNB (106) or / and MWAN-UE (106) or / and network may follow the below steps in any order or combinations:

[0263] 401a) the MWAB-gNB (106) shall provide its area information e.g., CAG information's or cell id or PLMN ID and / or TAI and / or CAG information to the MWAB-UE (108).

[0264] 401b) the MWAB-gNB (106) shall reject or indicate using any data or / and signalling message(AS message) to the UE (102) indicating or / and requesting to operate as MWAB-UE (108) in any of AS or NAS message

[0265] In step 402, the MWAB-UE (108) shall add this information in the forbidden list and shall bar those cells or / and PLMN or / and TAI or / and CAG broadcasting respective area information.

[0266] In step 403, the MWAB-UE (108) may send this forbidden area information (e.g., CAG information or cell id or PLMN ID and / or TAI and / or CAG information) to any NF function in any of the below combinations:

[0267] 403a) MWAB-UE (108) may send these forbidden area information e.g., CAG information's or cell id or PLMN ID and / or TAI and / or CAG information to gNB or any other NF (e.g., AMF) by using any of the NAS or AS message; for e.g., registration request or initial setup.

[0268] 403b) The gNB may forward these forbidden area information e.g., CAG information's or cell id or PLMN ID and / or TAI and / or CAG information to AMF entity (118) or any other NF (e.g., UDM entity (120)).

[0269] 403c) The AMF entity (118) may forward this forbidden area information e.g., CAG information or cell id or PLMN ID and / or TAI and / or CAG information to UDM entity (120) or any other NF.

[0270] In another embodiment, 403a) the MWAB-UE (108) may provide these forbidden area information e.g., CAG information or cell id or PLMN ID and / or TAI and / or CAG information to the AMF entity (118) or any other NF (e.g., UDM). 403b) the AMF entity (118) may forward this forbidden area information e.g., CAG information or cell id or PLMN ID and / or TAI and / or CAG information to the UDM entity (120) or any other NF.

[0271] In step 404, the RAN / gNB or / and 5GC ( e.g. AMF entity (118) or / and UDM entity (120)) may enforce the restrictions on the handover or / and redirection or / and mobility restriction for the MWAB-UE (108) to its own MWAB-gNB (106) in any of the below combinations:

[0272] 404a) The UDM entity (120) may store this forbidden area information (e.g., CAG information or cell id or PLMN ID and / or TAI and / or CAG information) and enforce handover or / and redirection or / and mobility restriction for the MWAB-UE (108). 404b) The UDM entity (120) may provide these handover or / and redirection or / and mobility restriction for the MWAB-UE (108) to the AMF entity (118) or any other NF (e.g., gNB).

[0273] 404c) The AMF entity (118) may forward these handover or / and redirection or / and mobility restrictions for MWAB-UE (108) to the gNB or any other NF.

[0274] In another embodiment, 404a) the AMF entity (118) may store this forbidden area information (e.g., CAG information or cell id or PLMN ID and / or TAI and / or CAG information) and restrict handover or / and restrict redirection or / and apply mobility restriction for the MWAB-UE (108). 404b) The AMF entity (118) may forward these handover or / and redirection or / and mobility restrictions for MWAB-UE (108) to the gNB or any other NF.

[0275] In step 405, the gNB (116) may store this forbidden area information (e.g., CAG information or cell id or PLMN ID and / or TAI and / or CAG information) and restrict handover or / and restrict redirection or / and apply mobility restriction for the MWAB-UE (108). In this embodiment, to enforce the restrictions on the handover or / and redirection or / and mobility restriction for the MWAB-UE (108) to its own MWAB-gNB (106) or to any otherMWAB-gNB (106) implies that the cells of target MWAB-gNB or other MWAB-gNB are not the candidates cells to handover / redirect the MWAB-UE (108). The NG-RAN should never hand over the UE (102) to MWAB-gNB (106). That is, it should not execute the handover procedure / redirection procedure on the UE (102) to this MWAB-gNB (106). In yet another embodiment, the UE (102) may not report this cells of MWAB-gNB (106) as part of measurement report or measurement procedure. Thus, the gNB (116) does not consider the cells of MWAB-gNB (106) as the candidate cells for handover procedure or redirection procedure. The MWAB-gNB (106) can be part of MWAB which is part of MWAB-UE (108) or it can be part of some other MWABs. The forbidden area information can also be called as handover restriction list.

[0276] FIG. 5 is a sequence diagram depicting the process of managing the MWAB-gNB (106). In step 501a, the UE (102) may indicate in the AS or NAS message (for example, Registration Request, TAU Request, RRC setup Request) that it is the MWAB-UE (108) to any Network Function (for example, gNB, AMF). In yet another embodiment, the UE (102) may request for the dedicated S-NSSAI(s) / DNN for MWAB operation in any AS or NAS message (for example, Registration Request, TAU Request, RRC setup Request) and based on these dedicated S-NSSAI(s) / DNN for MWAB operations, the AMF entity (118) may determine that the UE (102) is the MWAB-UE (108). Based on the UE subscription or / and UE location or / and UE context, in step 501b, the UDM entity (120) may indicate that the UE is a MWAB-UE (108) to the AMF entity (118) or any other Network Function (NFs). In step 502, the AMF entity (118) may indicate to the gNB that the UE is the MWAB-UE (108).

[0277] FIG. 6A and FIG. 6B are another sequence diagram depicting the process of managing the MWAB-gNB (106). In step 601, the MWAB-gNB (106) may connect via a Xn interface or S1-AP interface to the gNB (116). The MWAB-gNB (106) may indicate that it is a MWAB-gNB (106) to the gNB (116). In yet another embodiment, the gNB (116) or the AMF entity (118) may be locally configured that the connected gNB via Xn or S1-AP interface is the MWAB-gNB (106). In yet another embodiment, if the target gNB is MWAB-gNB (106), then the MWAB-gNB (106) may indicate that it is the MWAB-gNB (106) to the source gNB or / and to the AMF entity (118), optionally when doing Xn or / and N2 handover of the MWAB-UE (108). In yet another embodiment, the BH-RAN or / and BH-5GC (for example, the AMF entity (118) or any other NF) may locally configure that the gNB is the MWAB-gNB (106), optionally based on Operations, Administration, and Maintenance (OAM) configuration(s) or indicated by the MWAB-gNB (106).

[0278] In step 602, the MWAB-gNB (106) shall indicate using any new identifier or / and indication in any AS or NAS or broadcast message (for example, MIB or SIB) message that it is a gNB to the UE(s).

[0279] In step 603, the MWAB-UE (108) or / and MWAB-gNB (106) or / and the network (for example, gNB, AMF entity (118)) may follow any of the below procedures in any order or combination:

[0280] - a. The gNB (116) shall not configure the MWAB-UE (108) with the frequency or / and ARFCN or / and EARFCN for measurement on which the MWAB-gNB (106) is operating; for example, the gNb (116) shall not include Measurement Object (MeasObject) with the Frequency on which the MWAB-gNB (106) is operating in the Measurement Configuration (MeasConfig) IE of the RRC Reconfiguration message for the MWAB-UE (108).

[0281] - b. The gNB (116) shall not handover the MWAB-UE (108) to the MWAB-gNB cell., for example, the gNB shall not include the cell Physical Cell ID of the MWAB-gNB (106) in the TargetPhysCellID IE or the Frequency on which MWAB-gNB (106) is operating in the mobility Control Info (mobilityControlInfo) IE for MWAB-UE (108).

[0282] - c. The gNB (116) shall not redirect the MWAB-UE (108) to MWAB-gNB cell, for example, the gNB (116) shall not include the cell ID or Frequency of the MWAB-gNB (106) in the redirection message / IE for the MWAB-UE (108).

[0283] - d. The MWAB-UE (108) shall not include any cell which is MWAB-gNB (106) (for example, any cell that is broadcasting that it is a MWAB-gNB (106)) in the measurement report sent to the network.

[0284] - e. The gNB or / and AMF entity (118) shall not do any handover or redirection of the MWAB-UE (108) to any MWAB-gNB (106).

[0285] - f. The MWAB-UE (108) shall not select / re-select any cell / gNB broadcasting (for example, in MIB or SIB) or indicating in any AS or NAS message that it's the MWAB-gNB (106).

[0286] In an embodiment, the MWAB-UE (108) or / and the MWAB-gNB (106) or / and the network may follow any of below procedure in any order or combinations:

[0287] The MWAB-UE (108) may switch off the MWAB-gNB (106), optionally act as normal UE when performing handover, cell (re)selection procedures.

[0288] 2 The UE, when acting as MWAB-UE (108), shall not perform handover, cell selection, re-selection procedures.

[0289] 3. The MWAB-UE (108) may remove or restrict its UE capability based on OAM configuration for MWAB, (for example, if the MWAB-gNB (106) is operating with BAND 2 and PLMN1, then the MWAB-UE (108) shall remove or restrict those band combo for BAND 2 and add PLMN1 to the forbidden list till it acts as a MWAB for cell selection and shall reset or delete once it becomes a normal UE or MWAB-gNB (106) configurations are changed).

[0290] 4. The MWAB-gNB (106) may have dedicated network configuration for MWAB-gNB (106) operation(s). The Network shall not perform network selection / reselection / handover on such configurations (for example, band / PLMN, cell id) for the MWAB-UE (108).

[0291] 5. If the network requests a handover or redirects to own MWAB-gNB (106) or any MWAB-gNB (106), then the MWAB-UE (108) may indicate HO failure to the network. Optionally, the MWAB-UE (108) may perform re-selection on the previous cell.

[0292] The MWAB-gNB (106) shall not support or / and should not be configured with dedicated S-NSSAI or / and dedicated DNN for MWAB operation. This dedicated S-NSSAI or / and dedicated DNN for MWAB operation can be of the MWAB-UE (108) or the serving UE of the MWAB-gNB (106).

[0293] The MWAB-gNB (106) shall not include the dedicated S-NSSAI / DNN in any IE (for example,　TAI Slice Support List or / and Extended TAI Slice Support List) of any message over N2 interface to the AMF entity (118) (for example,　NG SETUP REQUEST, RAN CONFIGURATION UPDATE).

[0294] The MWAB-gNB (106) is not expected to be configured to support any dedicated S-NSSAI for the MWAB operation in the MWAB Broadcasted PLMN / SNPN. The support at the MWAB-gNB (106) of S-NSSAIs dedicated to MWAB in the MWAB Broadcasted PLMN / SNPN would mean that the MWAB-gNB (106) could support serving MWAB-UEs (108) BH-PDU sessions in the broadcasted PLMN / SNPN.

[0295] The AMF entity (118) shall store these supported S-NSSAI / DNN that does not include dedicated S-NSSAI / DNN for MWAB operation received from the MWAB-gNB (106).

[0296] The AMF entity (118) shall not include the dedicated S-NSSAI or / and dedicated DNN for MWAB operation in the list of allowed S-NSSAI. Optionally, the AMF entity (118) can reject or / and include the dedicated S-NSSAI or / and dedicated DNN for MWAB operation in the list of Rejected S-NSSAI in any AS or / and NAS message (for example,　Registration Accept, Service Accept, Attach Accept, and so on), if the request is from the MWAB-gNB (106) or / and if the AMF entity (118) determines that the Requesting UE is connected / camped to the MWAB-gNB (106).

[0297] In yet another embodiment, the AMF entity (118) / NG-RAN may handover the UE to another gNB / eNB which supports the dedicated S-NSSAI or / and dedicated DNN for MWAB operations. In yet another embodiment, the AMF entity (118) may send the AMF entity CP relocation indication to the MWAB-gNB (106).

[0298] In yet another embodiment, the UE (102) after receiving the dedicated S-NSSAI or / and dedicated DNN in the list of Rejected S-NSSAI in any AS or NSA message (for example,　Registration Accept, Service Accept, Attach Accept, and so on) or / and not included in the list of Allowed S-NSSAI shall operate as a normal UE without MWAB.

[0299] If at least one S-NSSAI in the Requested NSSAI (for example,　Dedicated S-NSSAI for MWAB operation) is not available in the current UE's Tracking Area, the NSSF may provide a Target NSSAI for the purpose of allowing the NG-RAN to redirect the UE to a cell of a TA in another frequency band supporting network slices not available in the current TA.

[0300] FIG. 7A and FIG. 7B depict an example sequence diagram of managing the MWAB. In step 701, the MWAB-gNB (106) does not include the dedicated S-NSSAI / DNN in the any IE (for example,　TAI Slice Support List or / and Extended TAI Slice Support List) of any message over N2 interface to the AMF entity (118) (for example,　NG SETUP REQUEST, RAN CONFIGURATION UPDATE). In step 702, the AMF entity (118) stores the supported S-NSSAI / DNN that does not include dedicated S-NSSAI / DNN for MWAB operation received from the MWAB-gNB (106).

[0301] In step 703, the UE camps on a MWAB-gNB (106) and sends request with dedicated S-NSSAI or / and dedicated DNN for MWAB operation in the list of requested S-NSSAI in any AS or NAS message (for example,　Registration Request, Service Request, Attach Request). On determining that the gNB (i.e., MWAB-gNB) does not support the requested S-NSSAI, in step 704a, the AMF entity (118) shall not include the dedicated S-NSSAI or / and dedicated DNN for MWAB operation in the list of allowed S-NSSAI. Optionally, the AMF entity (118) can reject or / and include the dedicated S-NSSAI or / and dedicated DNN for MWAB operation in the list of Rejected S-NSSAI in any AS or / and NAS message (for example,　Registration Accept, Service Accept, Attach Accept, and so on). In yet another embodiment, in step 704b, the AMF / NG-RAN may handover the UE to another gNB / eNB which supports the dedicated S-NSSAI or / and dedicated DNN for MWAB operations. In yet another embodiment, after receiving the dedicated S-NSSAI or / and dedicated DNN in the list of Rejected S-NSSAI in any AS or NSA message (e.g. Registration Accept, Service Accept, Attach Accept etc.) or / and not included in the list of Allowed S-NSSAI, in step 705, the UE shall operate as a normal UE without MWAB.

[0302] The MWAB-gNB (106) shall broadcast an indication that its MWAB-gNB (106) in any AS or NAS or broadcast message (for example, SIB, MIB). The UE on reading the broadcast message in any AS or NAS message with the indication that the gNB is MWAB-gNB (106), shall disable the use of MWAB slice; i.e., the UE should not request at least one of the dedicated S-NSSAI and DNN which is configured for MWAB operations; i.e., the UE should not request it in Requested NSSAI in any AS or NAS message (for example, Registration Request, Service Request, Attach Request), Optionally, the MWAB-UE (108) shall operate as a normal UE without MWAB operations. In yet another embodiment, if the UE wants to operate as MWAB-UE (108), the UE may perform cell selection or reselection to another gNB / eNB which broadcasts support of MWAB operations; i.e., to use the dedicated S-NSSAI or / and dedicated DNN for MWAB operation.

[0303] Embodiments herein are illustrated with the MWAB-gNB (106) as an example, but it may be obvious to a person of ordinary skill in the art that the same solution can be applied when the target is MBSR or IAB-node, to avoid the MWAB-UE (108) selecting / reselecting or getting handed over to the NG-RANs of type MBSR or IAB-node.

[0304] In an embodiment, the methods for access control (to restrict MWAB-UE (108) accessing MWAB-gNB (106) cell) is at least one of: MWAB-UE (108) accessing any MWAB-gNB (106) in IDLE and CONNECTED mode and the MWAB-UE (108) accessing the MWAB-gNB (106) belonging to same MWAB.

[0305] In an embodiment, wireless network includes at least one of: a source gNB entity and an AMF entity (118), determining that a handover procedure is initiated or ongoing for a MWAB-UE (108). The at least one of: the source gNB entity and the AMF entity (118), indicates, to a target gNB, that the UE for which handover is requested is the MWAB-UE (108). The target gNB, determines, that the target gNB is a MWAB-gNB based on the handover request received from the MWAB-UE (108). In an embodiment, the target gNB indicates to at least one of the source gNB entity and the AMF entity (118), that the target gNB is the MWAB-gNB (106). In another embodiment, the target gNB, rejects, the handover procedure of the MWAB-UE to at least one of the source gNB entity and the AMF entity (118). In another embodiment, at least one of: the source gNB entity and the AMF entity (118), perform, based on at least one of a reject message for the handover procedure from the target gNB or the indication that the target gNB is the MWAB-gNB, at least one of: reject the handover procedure of the MWAB-UE to the target gNB; and select another target gNB, other than the current selected target gNB, for the handover procedure of the MWAB-UE.

[0306] FIG. 8 shows various hardware components of the MWAB-UE (108), according to embodiments as disclosed herein. In an embodiment, the MWAB-UE (108) includes a processor (810), a communicator (820), a memory (830), and an MWAB controller (840). The processor (810) is coupled with the communicator (820), the memory (830), and the MWAB controller (840).

[0307] The MWAB controller (840) receives the identifier indicating that the gNB is the normal gNB or the MWAB-gNB (106) in the message from the gNB. Further, the MWAB controller (840) is configured to receive the identifier indicating that the MWAB-gNB (106) is the MWAB-gNB(106) in the message from the MWAB-gNB (106). Further, the MWAB controller (840) is configured to determine that the received identifier indicates that the gNB is the MWAB-gNB (106) and not a normal gNB in the message received from the gNB.

[0308] In an embodiment, the MWAB controller (840) is configured to perform that the MWAB-UE (108) attempts to select or reselect or handover to at least one of: a cell and the gNb that does not broadcast the identifier associated with MWAB-gNB (106). In another embodiment, the MWAB controller (840) is configured to perform that the MWAB-UE (108) attempts to select or reselect or handover to at least one of the cell and the gNB that broadcasts the identifier that the gNB is the normal gNB.

[0309] In another embodiment, the MWAB controller (840) is configured to perform that the MWAB-UE (108) does not attempt to select or reselect or handover to at least one cell and gNB that broadcasts the identifier that the MWAB-gNB (106) is the MWAB-gNB (106). In another embodiment, the MWAB controller (840) is configured to perform that the MWAB-UE (108) bar at least one of: a network identifier, the cell and the gNB that broadcasts the identifier that the MWAB-gNB (106) is the MWAB-gNB (106).

[0310] In an embodiment, the message includes at least one of: a broadcast message and a signalling message. The broadcast message and the signalling message includes at least one of: a system information block (SIB) message, a master information block (MIB) message, a non-access stratum (NAS) message and an access stratum (AS) message. The network identifier is a network parameter. The network parameter includes at least one of: frequency, a Physical Cell Identifier (PCI), band, E-UTRA, Absolute Radio Frequency Channel Number (EARFCN), Absolute Radio Frequency Channel Number (ARFCN), a radio access technology (RAT), and Access.

[0311] The MWAB controller (840) is 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 may optionally be driven by firmware.

[0312] The processor (810) may include one or a plurality of processors. The one or the 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 AI-dedicated processor such as a neural processing unit (NPU). The processor (810) may include multiple cores and is configured to execute the instructions stored in the memory (830).

[0313] Further, the processor (810) is configured to execute instructions stored in the memory (830) and to perform various processes. The communicator (820) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (830) also stores instructions to be executed by the processor (810). The memory (830) may include non-volatile storage elements. Examples of such 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. In addition, the memory (830) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (830) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0314] Although FIG. 8 shows various hardware components of the MWAB-UE (108) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the MWAB-UE (108) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention. One or more components can be combined together to perform the same or substantially similar function in the MWAB-UE (108).

[0315] FIG. 9 shows various hardware components of the MWAB-gNB (106), according to embodiments as disclosed herein. In an embodiment, the MWAB-gNB (106) includes a processor (910), a communicator (920), a memory (930), and a MWAB controller (940). The processor (910) is coupled with the communicator (920), the memory (930), and the MWAB controller (940).

[0316] By using the network entity, the MWAB controller (940) configures that at least one of: the MWAB-gNB (106) does not support and the MWAB-gNB(106) is not configured with at least one of: the dedicated S-NSSAI for the MWAB operation and a DNN for the MWAB operation. At least one of: the dedicated S-NSSAI and the DNN for the MWAB operation belongs to one of: the MWAB-UE (108) or the serving UE of the MWAB-gNB (106). The network entity can be, for example, but not limited to, an OAM entity, the AMF entity or any network function entity. Based on the configuration, the MWAB controller (940) manages the MWAB.

[0317] Further, the MWAB controller (940) determines at least one of: the AS signaling message or the NAS signaling message from the UE requesting at least one of: the dedicated S-NSSAI for the MWAB operation and the DNN for the MWAB operation. In an embodiment, the MWAB controller (940) rejects the request in at least one of: the AS signaling message and the NAS signaling message. In another embodiment, the MWAB controller (940) includes, at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of rejected S-NSSAI through at least one of: the AS signaling message and the NAS signaling message. In an embodiment, the MWAB controller (940) does not include at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of allowed S-NSSAI in through at least one of: AS signaling message and the NAS signaling message.

[0318] The MWAB controller (940) is 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 may optionally be driven by firmware.

[0319] The processor (910) may include one or a plurality of processors. The one or the 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 AI-dedicated processor such as a neural processing unit (NPU). The processor (910) may include multiple cores and is configured to execute the instructions stored in the memory (930).

[0320] Further, the processor (910) is configured to execute instructions stored in the memory (930) and to perform various processes. The communicator (920) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (930) also stores instructions to be executed by the processor (910). The memory (930) may include non-volatile storage elements. Examples of such 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. In addition, the memory (930) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (930) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0321] Although FIG. 9 shows various hardware components of the MWAB-gNB (106) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the MWAB-gNB (106) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention. One or more components can be combined together to perform the same or substantially similar function in the MWAB-gNB (106).

[0322] FIG. 10 shows various hardware components of an AMF entity (118), according to embodiments as disclosed herein. In an embodiment, the AMF entity (118) includes a processor (1010), a communicator (1020), a memory (1030), and a MWAB controller (1040). The processor (1010) is coupled with the communicator (1020), the memory (1030), and the MWAB controller (1040).

[0323] The MWAB controller (940) is receives at least one of: the AS signaling message and the NAS signaling message from at least one of: the UE requesting at least one of: the dedicated S-NSSAI for the MWAB operation and the DNN for the MWAB operation and the gNB requesting for at least one of a serving UE at least one of: the dedicated S-NSSAI for the MWAB operation and the DNN for the MWAB operation. Further, the MWAB controller (940) determines that the request is received from the MWAB-gNB (106) and the requesting UE is connected or camped to the MWAB-gNB (106). Further, the MWAB controller (940) is configured to manage the MWAB, based on the determination, by performing, at least one of: rejecting the request in at least one of: the AS signaling message and the NAS signaling message, including in at least one of: AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of rejected S-NSSAI, and not including in at least one of: the AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of allowed S-NSSAI.

[0324] The MWAB controller (1040) is 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 may optionally be driven by firmware.

[0325] The processor (1010) may include one or a plurality of processors. The one or the 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 AI-dedicated processor such as a neural processing unit (NPU). The processor (1010) may include multiple cores and is configured to execute the instructions stored in the memory (1030).

[0326] Further, the processor (1010) is configured to execute instructions stored in the memory (1030) and to perform various processes. The communicator (1020) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (1030) also stores instructions to be executed by the processor (1010). The memory (1030) may include non-volatile storage elements. Examples of such 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. In addition, the memory (1030) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (1030) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0327] Although FIG. 10 shows various hardware components of the AMF entity (118) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the AMF entity (118) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention. One or more components can be combined together to perform the same or substantially similar function in the AMF entity (118).

[0328] FIG. 11 is a flow chart (S1100) illustrating a method, implemented by the MWAB-UE (108), for managing the MWAB, according to embodiments as disclosed herein. The operations (S1106-S1112) are handled by the MWAB controller (840).

[0329] At S1102, the method includes transmitting, by the gNB, the identifier indicating that the gNB is the normal gNB or the MWAB-gNB (106) in the message. At S1104, the method includes transmitting, by the MWAB-gNB (106), the identifier indicating that the MWAB-gNB is the MWAB-gNB(106) in the message.

[0330] At S1106, the method includes receiving, by the MWAB-UE (108), the identifier indicating that the gNB is the normal gNB or the MWAB-gNB (106) in the message from the gNB. At S1108, the method includes receiving, by the MWAB-UE (108), the identifier indicating that the MWAB-gNB (106) is the MWAB-gNB(106) in the message from the MWAB-gNB (106). At S1110, the method includes determining, by the MWAB-UE (108), that the received identifier indicates that the gNB is the MWAB-gNB (106) and not a normal gNB in the message received from the gNB.

[0331] At S1112, the method includes performing, by the MWAB-UE (108), at least one of: the MWAB-UE (108) attempts to select or reselect or handover to at least one of: a cell and the gNb that does not broadcast the identifier associated with MWAB-gNB (106), the MWAB-UE (108) attempts to select or reselect or handover to at least one of the cell and the gNB that broadcasts the identifier that the gNB is the normal gNB, the MWAB-UE (108) does not attempt to select or reselect or handover to at least one cell and gNB that broadcasts the identifier that the MWAB-gNB (106) is the MWAB-gNB (106), and the MWAB-UE (108) bar at least one of: a network identifier, the cell and the gNB that broadcasts the identifier that the MWAB-gNB (106) is the MWAB-gNB (106).

[0332] In an embodiment, the message includes at least one of: a broadcast message and a signalling message. The broadcast message and the signalling message includes at least one of: a system information block (SIB) message, a master information block (MIB) message, a non-access stratum (NAS) message and an access stratum (AS) message. The network identifier is a network parameter. The network parameter includes at least one of: frequency, a Physical Cell Identifier (PCI), band, E-UTRA, Absolute Radio Frequency Channel Number (EARFCN), Absolute Radio Frequency Channel Number (ARFCN), a radio access technology (RAT), and Access.

[0333] FIG. 12 is a flow chart (S1200) illustrating a method, implemented by the MWAB-gNB (106), for managing the MWAB, according to embodiments as disclosed herein. The operations (S1202-S1204) are handled by the MWAB controller (940).

[0334] At S1202, the method includes configuring, by the network entity in the MWAB-gNB (106), at least one of: the MWAB-gNB (106) does not support and the MWAB-gNB(106) is not configured with at least one of: a dedicated Single Network Slice Selection Assistance Information (S-NSSAI) for a MWAB operation and a Data Network Name (DNN) for the MWAB operation. At least one of: the dedicated S-NSSAI and the DNN for the MWAB operation belongs to one of: a MWAB-UE (108) or a serving UE of the MWAB-gNB (106). The network entity can be, for example, but not limited to, an OAM entity, the AMF entity or any network function entity. At S1204, the method includes managing, by the MWAB-gNB (106), the MWAB based on the configuration.

[0335] In an embodiment, the method includes determining, by the MWAB-gNB (106), at least one of: an AS signaling message or a NAS signaling message from the UE requesting at least one of: the dedicated S-NSSAI for the MWAB operation and the DNN for the MWAB operation. Further, the method includes performing, by the MWAB-gNB(106), at least one of: rejecting the request in at least one of: the AS signaling message and the NAS signaling message, including in at least one of: the AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of rejected S-NSSAI, and not including in at least one of: AS signaling message and the NAS signaling message in at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of allowed S-NSSAI.

[0336] FIG. 13 is a flow chart (S1300) illustrating a method, implemented by the AMF entity (118), for managing the MWAB, according to embodiments as disclosed herein. The operations (S1302-S1306) are handled by the MWAB controller (1040).

[0337] At S1302, the method includes receiving, by the AMF entity, at least one of: the AS signaling message and the NAS signaling message from at least one of: the UE requesting at least one of: the dedicated S-NSSAI for the MWAB operation and the DNN for the MWAB operation and the gNB requesting for at least one of a serving UE at least one of: the dedicated S-NSSAI for the MWAB operation and the DNN for the MWAB operation. At S1304, the method includes determining, by the AMF entity (118), that the request is received from the MWAB-gNB (106) and the requesting UE is connected or camped to the MWAB-gNB (106).

[0338] At S1306, the method includes managing, by the AMF entity (118), the MWAB, based on the determination, by performing, by the AMF entity (118), at least one of: rejecting the request in at least one of: the AS signaling message and the NAS signaling message, including in at least one of: AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of rejected S-NSSAI; and not including in at least one of: the AS signaling message and the NAS signaling message at least one of: the dedicated S-NSSAI and the DNN for the MWAB operation in a list of allowed S-NSSAI.

[0339] FIG. 14 is a flow chart (S1400) illustrating a method for managing the MWAB, according to embodiments as disclosed herein.

[0340] At S1402, the method includes determining, by at least one of: a source gNB entity and an AMF entity (118), that a handover procedure is initiated or ongoing for a MWAB-UE (108). At S1404, the method includes indicating, by at least one of: the source gNB entity and the AMF entity (118), to a target gNB, that the UE for which handover is requested is the MWAB-UE (108).

[0341] At S1406, the method includes determining, by the target gNB, that the target gNB is a MWAB-gNB based on the handover request received from the MWAB-UE (108). At S1408, the method includes performing at least one of: indicating, by the target gNB, to at least one of the source gNB entity and the AMF entity (118), that the target gNB is the MWAB-gNB (106); and rejecting, by the target gNB, the handover procedure of the MWAB-UE to at least one of the source gNB entity and the AMF entity (118).

[0342] At S1410, the method includes performing, by at least one of: the source gNB entity and the AMF entity (118), based on at least one of a reject message for the handover procedure from the target gNB or the indication that the target gNB is the MWAB-gNB, at least one of: rejecting the handover procedure of the MWAB-UE to the target gNB; and selecting another target gNB, other than the current selected target gNB, for the handover procedure of MWAB-UE.

[0343] The handover procedure is at least of: an Xn handover of the MWAB-UE (108) and a N2 handover of the MWAB-UE (108).

[0344] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0345] The embodiment disclosed herein describes methods and systems for barring the MWAB-UE (108) from selecting / reselecting / handover to its own MWAB-gNB (106). Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile deviceor any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0346] 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 should and 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 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 for managing mobile gNB with wireless access backhaul (MWAB) by an MWAB-user equipment (UE) in an electronic device including an MWAB-gNB and the MWAB-UE, the method comprising:receiving configuration information about the MWAB-gNB; andpreventing from selecting or reselecting or handover to the MWAB-gNB in the electronic device.2.The method of claim 1, wherein preventing from selecting or reselecting or handover to the MWAB-gNB comprises attempting to select or reselect or handover to a cell of a gNB or the gNB which does not broadcast information indicating that the gNB is an MWAB-gNB.3.The method of claim 1, wherein preventing from selecting or reselecting or handover to the MWAB-gNB comprises attempting to select or reselect or handover to a cell of a gNB or the gNB which broadcasts information indicating that the gNB is a normal gNB.4.The method of claim 1, wherein preventing from selecting or reselecting or handover to the MWAB-gNB comprises not attempting to select or reselect or handover to a cell of a gNB or the gNB which broadcasts information indicating that the gNB is an MWAB-gNB.5.The method of claim 1, wherein the configuration information includes at least one of closed access group (CAG) information, a cell identifier (ID), a public land mobile network (PLMN) ID, a tracking area identity (TAI), andwherein preventing from selecting or reselecting or handover to the MWAB-gNB comprises adding the configuration information in a forbidden list and not attempting to select or reselect or handover based on the forbidden list.6.The method of claim 1, wherein the configuration information is transmitted by the MWAB-gNB through a mater information block (MIB) or a system information block (SIB).7.The method of claim 1, wherein the configuration information is received from an access and mobility management function through a UE configuration update message or a UE parameters update message or an access stratum (AS) message or a non-access stratum (NAS) message.8.A managing mobile gNB with wireless access backhaul (MWAB)-user equipment (UE) in an electronic device including an MWAB-gNB and the MWAB-UE, the MWAB-UE comprising:a communicator; andat least one processor coupled to the communicator, wherein the at least one processor is configured to:receive configuration information about the MWAB-gNB, andprevent from selecting or reselecting or handover to the MWAB-gNB in the electronic device.9.The MWAB-UE of claim 8, wherein to prevent from selecting or reselecting or handover to the MWAB-gNB, the at least one processor is configured to attempt to select or reselect or handover to a cell of a gNB or the gNB which does not broadcast information indicating that the gNB is an MWAB-gNB.10.The MWAB-UE of claim 8, wherein to prevent from selecting or reselecting or handover to the MWAB-gNB, the at least one processor is configured to attempt to select or reselect or handover to a cell of a gNB or the gNB which broadcasts information indicating that the gNB is a normal gNB.11.The MWAB-UE of claim 8, wherein to prevent from selecting or reselecting or handover to the MWAB-gNB the at least one processor is configured not to attempt to select or reselect or handover to a cell of a gNB or the gNB which broadcasts information indicating that the gNB is an MWAB-gNB.12.The MWAB-UE of claim 8, wherein the configuration information includes at least one of closed access group (CAG) information, a cell identifier (ID), a public land mobile network (PLMN) ID, a tracking area identity (TAI), andwherein barring from selecting or reselecting or handover to the MWAB-gNB comprises adding the configuration information in a forbidden list and not attempting to select or reselect or handover based on the forbidden list.13.The MWAB-UE of claim 9, wherein the configuration information is transmitted by the MWAB-gNB through a master information block (MIB) or a system information block (SIB).14.The MWAB-UE of claim 9, wherein the configuration information is received from an access and mobility management function through a UE configuration update message or a UE parameters update message or an access stratum (AS) message or a non-access stratum (NAS) message.

Images