Method and MWAB-GNB for creating mobile interface between first GNB, and neighboring network entity

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose an Xn architecture for MWAB. Embodiments herein disclose a multihop architecture for MWAB. In an embodiment, the method can be used for creating a mobile interface between a first Next Generation Node B (gNB), and at least one neighboring network entity. The method includes requesting, by a mobile gNB with wireless access backhaul (MWAB) (MWAB-gNB) (106), a protocol data unit (PDU) session establishment to a MWAB-User Equipment (UE) (MWAB-UE) (108). Further, the method includes receiving, by the MWAB-gNB (106), an internet protocol (IP) connectivity from the MWAB-UE (108), upon establishment of a PDU session with a first network entity or modifying an existing PDU session with the first network entity. Further, the method includes creating, by the MWAB-gNB (106), the mobile interface with the at least one neighboring second network entity through the PDU session associated with the MWAB-UE (108).

Description

METHOD AND MWAB-GNB FOR CREATING MOBILE INTERFACE BETWEEN FIRST GNB, AND NEIGHBORING NETWORK ENTITY

[0001] Embodiments disclosed herein relate to wireless communication networks, and more particularly to an Xn interface and a multi-hop architecture for a mobile gNB with wireless access backhaul (MWAB).

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

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

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

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

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

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

[0008] In MWAB (mobile gNB with wireless access backhaul) (104), a mobile base station acts as a gNB for other User Equipment’s (UEs) and provides access to a fifth generation (5G) networks, i.e. providing a new radio (NR) access link to the UEs and connected wirelessly to a fifth generation core (5GC) (using NR) through an internet protocol (IP) connectivity provided by a PDU session established via NG-RAN cell that the mobile gNB can camp on. The PDU session is provided either by a Terrestrial Network or by a Non-Terrestrial Network. Such a mobile gNB may be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering / leaving the vehicle). FIG. 1 depicts a MWAB session.

[0009] In NR / 5G architecture, Xn interface is used for handover of UE(s) (102) from one gNB to another gNB. Xn interface is also used for other procedures such as: Retrieve UE Context Procedure, Data Forwarding Address Indication Procedure, RAN Paging Procedure,Secondary Node Addition, Secondary Node Modification, Dual Connectivity procedures, Secondary Node Release etc. In a MWAB architecture (1000), the MWAB-UE (108) can be mobile (or moving) and thus the MWAB-gNB (106) associated with the MWAB-UE (108) cannot have permanent (fixed or wireline) established Xn interfaces with other gNBs. Due to mobile nature of MWAB-gNB, it is not clear to how the MWAB-gNB (106) knows neighbouring gNB(s) for which it can provide measurement configurations to different UE(s) and handover the UE(s) to.

[0010] In the MWAB architecture (1000), normal / other UEs (102) may connect to the MWAB-gNB (106) / the MWAB-UE (108) to avail services. But the MWAB-UE(s) (108) may also connect to the MWAB-gNB (106) to provide backhaul services to the MWAB-gNB (106). The current architecture does not have provisions to provide services from the MWAB-UE (108) connected to the 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).

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

[0012] Accordingly, the embodiments herein provide a method for creating a mobile interface between a first Next Generation Node B (gNB), and at least one neighboring network entity. The method includes requesting, by a mobile gNB with wireless access backhaul (MWAB) (MWAB-gNB), a protocol data unit (PDU) session establishment to a MWAB-User Equipment (UE) (MWAB-UE). Further, the method includes receiving, by the MWAB-gNB, an internet protocol (IP) connectivity from the MWAB-UE, upon establishment of a PDU session with a first network entity or modifying an existing PDU session with the first network entity. Further, the method includes creating, by the MWAB-gNB, the mobile interface with the at least one neighboring second network entity through the PDU session associated with the MWAB-UE.

[0013] Accordingly, the embodiments herein provide a MWAB-gNB including an interface creation controller coupled with a processor and a memory. The interface creation controller is configured to request a PDU session establishment to a MWAB-UE. Further, the interface creation controller is configured to receive an internet protocol (IP) connectivity from the MWAB-UE, upon establishment of a PDU session with a first network entity or modifying an existing PDU session with the first network entity. The interface creation controller is configured to create a mobile interface with the at least one neighboring second network entity through the PDU session associated with the MWAB-UE.

[0014] In an embodiment, the first network entity is a network which is serving the MWAB-UE.

[0015] In an embodiment, the second network entity is a MWAB broadcasted Public Land Mobile Network (PLMN), and the MWAB-gNB is acting as a gNB of a MWAB broadcasted PLMN.

[0016] In an embodiment, the first network entity and the second network entity are the same network entity.

[0017] In an embodiment, the first network entity and the second network entity are different network entity.

[0018] In an embodiment, the method includes connecting, by the MWAB-gNB, the at least one neighboring second network entity through the mobile interface.

[0019] In an embodiment, the at least one neighboring network entity is a Next Generation Radio Access Network (NG-RAN) node.

[0020] In an embodiment, the MWAB-UE establishes or modifies the PDU session based on at least one of: a User Equipment Route Selection Policy (URSP) rule and a local configuration.

[0021] In an embodiment, the mobile interface is an Xn interface, the PDU session is a backhaul (BH) PDU session, and the Xn interface of the MWAB-gNB is tunnelled through the BH PDU session.

[0022] 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 spirit thereof, and the embodiments herein include all such modifications.

[0023] The principal object of embodiments herein is to disclose a method and a MWAB-gNB for creating a mobile interface between a first Next Generation Node B (gNB), and at least one neighboring network entity.

[0024] Another object of embodiments herein is to request a PDU session establishment to a MWAB-User Equipment (UE) (MWAB-UE) by a mobile gNB with wireless access backhaul (MWAB) (MWAB-gNB).

[0025] Another object of embodiments herein is to receive an internet protocol (IP) connectivity from the MWAB-UE, by the MWAB-gNB, upon establishment of a PDU session with a first network entity or modifying an existing PDU session with the first network entity.

[0026] Another object of embodiments herein is to create the mobile interface with the at least one neighboring second network entity through the PDU session associated with the MWAB-UE by the MWAB-gNB.

[0027] Another object of embodiments herein is to connect the at least one neighboring second network entity through the mobile interface by the MWAB-gNB.

[0028] Another object of embodiments herein is to establish or modify the PDU session, by the MWAB-UE, based on at least one of: a User Equipment Routing Selection Policy (URSP) rule and a local configuration.

[0029] Another object of embodiments herein is to disclose an Xn architecture for MWAB.

[0030] Another object of embodiments herein is to disclose a multihop architecture for MWAB.

[0031] 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:

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

[0033] FIG. 2 depicts a Xn interface for MWAB, according to embodiments as disclosed herein;

[0034] FIG. 3 depicts a multihop architecture for MWAB, according to embodiments as disclosed herein;

[0035] FIG. 4 shows various hardware components of a MWAB-gNB, according to embodiments as disclosed herein; and

[0036] FIG. 5 is a flow chart illustrating a method for creating a mobile interface between a first Next Generation Node B (gNB), and at least one neighboring network entity, according to embodiments as disclosed herein.

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

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

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

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

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

[0042] The embodiments herein achieve an Xn architecture and a multihop architecture for MWAB. The embodiments herein also achieve a method for creating a mobile interface between a first Next Generation Node B (gNB), and at least one neighboring network entity.The method includes requesting, by a mobile gNB with wireless access backhaul (MWAB) (MWAB-gNB), a protocol data unit (PDU) session establishment to a MWAB-User Equipment (UE) (MWAB-UE). Further, the method includes receiving, by the MWAB-gNB, an internet protocol (IP) connectivity from the MWAB-UE, upon establishment of a PDU session with a first network entity or modifying an existing PDU session with the first network entity. Further, the method includes creating, by the MWAB-gNB, the mobile interface with the at least one neighboring second network entity through the PDU session associated with the MWAB-UE.

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

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

[0045] 3GPP: Third Generation Partnership Project

[0046] 5GC: 5G Core

[0047] 5GCN: 5G Core Network

[0048] 5GMM: 5G Mobility Management

[0049] 5GS: 5G System

[0050] AMF: Access and Mobility Management Function

[0051] AS: Access Stratum

[0052] CAG: Closed access group

[0053] CAG ID: Closed Access Group Identifier

[0054] DL: Downlink

[0055] EHPLMN: Equivalent Home Public Land Mobile Network

[0056] EMM: EUTRA Mobility Management

[0057] eNB: Evolved Node-B

[0058] EPS: Evolved Packet System

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

[0060] EUTRAN: Evolved Universal Mobile Telecommunication Access Network

[0061] FPLMN: Forbidden Public Land Mobile Network

[0062] GEO: Geostationary Orbit

[0063] GERAN: GSM Edge Radio Access Network

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

[0065] gNB: Next generation Node-B

[0066] GPRS: General Packet Radio Service

[0067] GSM: Global System for Mobile Communication

[0068] HPLMN: Home Public Land Mobile Network

[0069] IAB: Integrated access and backhaul

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

[0071] IE: Information Element

[0072] LEO: Low Earth Orbit

[0073] MCC: Mobile Country Code

[0074] ME: Mobile Equipment

[0075] MEO: Medium Earth Orbit

[0076] MME: Mobility Management Entity

[0077] MNC: Mobile Network Code

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

[0079] MWAB: Mobile Wireless Access Backhaul

[0080] NAS: Non-Access Stratum

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

[0082] NPN: Non-Public Networks

[0083] NR: New Radio

[0084] NTN: Non Terrestrial Networks

[0085] NW: Network

[0086] PDU: Packet Data Unit

[0087] PLMN ID: Public Land Mobile Network Identity

[0088] PSM: Power Saving Mode

[0089] RPLMN: Registered Public Land Mobile Network

[0090] RRC: Radio Resource Control

[0091] SAT: Satellite

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

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

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

[0095] SIM: Subscriber Identity Module

[0096] SNPN: Standalone Non-Public Networks

[0097] SUCI: Subscription Concealed Identifier

[0098] TAC: Tracking Area Code

[0099] TAI: Tracking Area Identity

[0100] TAU: Tracking Area Update

[0101] TER: Terrestrial

[0102] TN: Terrestrial Networks

[0103] UCU: UE Configuration Update

[0104] UDM: Unified Data Management Function

[0105] UE: User Equipment

[0106] UL: Uplink

[0107] ULI: User Location Information

[0108] UPU: UE Parameters Update

[0109] USIM: Universal Subscriber Identification Module

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

[0111] VPLMN: Visited Public Land Mobile Network

[0112] 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).

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

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

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

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

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

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

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

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

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

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

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

[0124] The term 5GMM sublayer states in this embodiment are at least one of the below:

[0125] 1) 5GMM-NULL

[0126] 2) 5GMM-DEREGISTERED

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

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

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

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

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

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

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

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

[0135] 3) 5GMM-REGISTERED-INITIATED

[0136] 4) 5GMM-REGISTERED

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

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

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

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

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

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

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

[0144] 5) 5GMM-DEREGISTERED-INITIATED

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

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

[0147] 1) EMM-NULL

[0148] 2) EMM-DEREGISTERED

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

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

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

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

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

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

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

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

[0157] 3) EMM-REGISTERED-INITIATED

[0158] 4) EMM-REGISTERED

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

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

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

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

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

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

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

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

[0167] 5) EMM-DEREGISTERED-INITIATED

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

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

[0170] The term RAT as defined in this embodiment can be one of the following: NG-RAN, 5G, 4G, 3G, 2G, EPS, 5GS, NR,

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

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

[0173] PLMN selection as per 23.122 without RPLMN:

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

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

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

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

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

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

[0180] PLMN selection as per 23.122 with RPLMN:

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

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

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

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

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

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

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

[0188] For a 5G system with satellite access, the following requirements apply:

[0189] The 5G system shall support service continuity between NR terrestrial access network and NR satellite access networks owned by the same operator or owned by 2 different operators having an agreement.

[0190] The NTN and TN could either operate in two different frequency bands (e.g. FR1 vs FR2), or in same frequency band (e.g. FR1 or FR2).

[0191] The terms Satellite 3GPP access, Satellite access, Satellite Access Network, NR Satellite Access Network, Satellite NG-RAN Access Technology and NR Satellite access have been interchangeably used and have the same meaning.

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

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

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

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

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

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

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

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

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

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

[0202] The terms wait timer, DisCo wait timer, Discontinuous Coverage wait timer, Random timer, Random wait timer, DCW Timer are all used interchangeably and have the same meaning.

[0203] The terms wait range, Disco Wait Range, Discontinuous Coverage Wait Range, DCW Range are all used interchangeably and have the same meaning.

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

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

[0206] 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 is only for illustration purpose it can be any NAS or AS messages as per defined protocol between UE and AMF / MME or UE and gNB(NG-RAN / any RAN node) / eNB.

[0207]

[0208] FIG. 2 depicts a Xn interface for the MWAB. The Xn interface between 2 gNBs is required to support Xn interface functions, such as, but not limited to, mobility management procedures, dual connectivity procedures, and so on. Since the Xn interfaces may not be established directly between a MWAB-gNB (106) and another NG-RAN(gNB) or between one MWAB-gNB (106) and another MWAB-gNB, the gNB (MWAB-gNB) (106) may use a BH PDU session to establish Xn interface with other gNBs. The Xn interface functions mentioned below will be performed via the tunnel Backhaul PDU session. The N2 / N3 / Xn interfaces of the MWAB-gNB (106) are tunnelled through Backhaul PDU session(s) and connected to a 5GC serving the UE (102) and another one or more gNB(s). During the handover procedure, the messages (such as, but not limited to, forwarding of data from a source gNB to a target gNB, release resources sent from the target gNB to the source gNB, and so on) are exchanged between 2 NG-RANs (e.g., MWAB-gNB (106) and normal gNB or MWAB-gNB (106) and another MWAB-gNB (106)). The MWAB-gNB (106) tunnels through BH-5GC (112) for N2 / N3 and Xn interfaces. The MWAB-UE (108)(s) acting as normal UE (102) can be served by the MWAB-gNB (106). The Xn interface functions as defined in 3GPP TS 38.420 / 38.421 / 38.422.

[0209] 6 Xn interface procedures

[0210] 6.1 General: The Xn interface supports procedures over the control plane (Xn-C) and user plane (Xn-U).

[0211] 6.2 Control plane protocol procedures

[0212] 6.2.1 Mobility management procedures: The mobility management procedures are used to manage the UE mobility in Connected or RRC_Inactive modes:

[0213] - Handover Preparation

[0214] - Handover Cancel

[0215] - SN Status Transfer

[0216] - Retrieve UE Context

[0217] - RAN Paging

[0218] - Xn-U Address Indication

[0219] - UE Context Release

[0220] - Handover Success Indication

[0221] - Conditional Handover Cancel

[0222] - Retrieve UE Context Confirm

[0223] Xn interface procedures:

[0224] 6.2.2 Dual Connectivity procedures: The dual connectivity procedures are used to add, modify and releases resources for the operation of Dual Connectivity:

[0225] - S-NG-RAN-node Addition Preparation

[0226] - S-NG-RAN-node Reconfiguration Completion

[0227] - M-NG-RAN-node initiated S-NG-RAN-node Modification Preparation

[0228] - S-NG-RAN-node initiated S-NG-RAN-node Modification

[0229] - M-NG-RAN-node initiated S-NG-RAN-node Release

[0230] - S-NG-RAN-node initiated S-NG-RAN-node Release

[0231] - S-NG-RAN-node Counter Check

[0232] - RRC Transfer

[0233] - Notification Control Indication

[0234] - Activity Notification

[0235] - Secondary RAT Data Usage Report

[0236] - Conditional PSCell Change Cancel

[0237] 6.2.3 Global procedures: The global procedures are used to exchange configuration level data between two NG-RAN nodes, or to remove Xn connectivity between two NG-RAN nodes in a controlled manner:

[0238] - Xn Setup

[0239] - NG-RAN-node Configuration Update

[0240] - Xn Removal

[0241] 6.2.4 Interface Management procedures: The interface management procedures are used to align resources between two NG-RAN nodes in the event of failures, and to report detected protocol errors:

[0242] - Reset

[0243] - Error Indication

[0244] 6.2.5 Energy saving procedures: Cell Activation procedure: enables an NG-RAN node to request the activation of a previously deactivated cell or SSB beam hosted in another NG-RAN node.

[0245] 6.2.7 UE Tracing procedures: The following procedures are used to trace the UE:

[0246] - Trace Start procedure

[0247] - Deactivate Trace procedure

[0248] - Cell Traffic Trace

[0249] 6.2.8 Load management procedures: The load management procedures are used by NG-RAN nodes to indicate resource status, overload and traffic load to each other.

[0250] - Resource Status Reporting Initiation

[0251] - Resource Status Reporting

[0252] 6.2.9 Data exchange for self-optimisation procedures: The data exchange for self-optimisation procedures are used to transfer failure, access and mobility related information among NG-RAN nodes to enable self-optimisation

[0253] - Failure Indication

[0254] - Handover report

[0255] - Mobility Settings Change

[0256] - Access and Mobility Indication

[0257] - SCG Failure Information Report

[0258] - SCG Failure Transfer

[0259] - RACH Indication

[0260] 6.2.10 IAB procedures: The IAB procedures are used to enable the transfer of F1 / non-F1 traffic for IAB, to exchange information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, to enable the delivery of F1-C traffic between the M-NG-RAN node and the S-NG-RAN node serving a dual-connected non-boundary IAB-node, to exchange resource multiplexing related information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, to exchange information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of a mobile IAB-node, to exchange resource multiplexing related information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of the mobile IAB-node, to exchange information, e.g., the authorization status, of IAB-nodes or mobile IAB-nodes:

[0261] - F1-C Traffic Transfer

[0262] - IAB Transport Migration Management

[0263] - IAB Transport Migration Modification

[0264] - IAB Resource Coordination

[0265] The MBS management procedures are used to manage the MBS Session:

[0266] - RAN Multicast Group Paging procedure

[0267] 6.2.12 Small data transmission procedures

[0268] - Partial UE Context Transfer: enables exchange of information between NG-RAN nodes for SDT transmission without anchor relocation

[0269] Small data transmission is also supported by the following procedures:

[0270] - RRC Transfer

[0271] - Retrieve UE Context Confirm

[0272] - RAN Paging

[0273] 6.2.13 QMC support procedures: The following procedures are used to transfer QMC configuration and session information to the target NG-RAN node during UE intra-system intra-RAT mobility:

[0274] - Handover Preparation.

[0275] - Retrieve UE Context.

[0276] The following procedure is used to transfer QMC configuration and session information to the target NG-RAN node during UE intra-system inter-RAT mobility:

[0277] - Handover Preparation.

[0278] The following procedures are used to coordinate QMC configuration and reporting between the M-NG-RAN node and the S-NG-RAN node:

[0279] - S-NG-RAN node Addition Preparation

[0280] - M-NG-RAN node initiated S-NG-RAN node Modification Preparation

[0281] - S-NG-RAN node initiated S-NG-RAN node Modification

[0282] - S-NG-RAN node initiated S-NG-RAN node Change

[0283] - RRC Transfer

[0284] 6.2.14 AI / ML support procedures: The following procedures are used to initiate data collection and report collected data to support, e.g., AI / ML for NG-RAN:

[0285] - Data Collection Reporting Initiation

[0286] - Data Collection Reporting

[0287] 6.3 User plane protocol procedures

[0288] The user plane protocol procedures are used to exchange user plane information between Xn-U protocol peers:

[0289] - Transfer of Downlink User Data procedure: enables the node hosting the NR PDCP entity to provide user plane information to the corresponding node.

[0290] - Downlink Data Delivery Status procedure: enables the corresponding node to provide feedback to the node hosting the NR PDCP entity.

[0291] - Transfer of Assistance Information: enables the corresponding node to provide assistance information to the node hosting the NR PDCP entity.

[0292] - Transfer of PDU Session Information procedure: enables an NG-RAN node to provide user plane information associated with the forwarding of data towards a peer NG-RAN node, when using PDU session tunnels.

[0293] The MWAB-gNB (106) establishes Xn interface(s) with it’s neighboring gNB (NG-RAN nodes) dynamically using the IP connectivity provided by the backhaul PDU session provided by the MWAB-UE. The MWAB-gNB (106) uses this Xn interface over IP connectivity to perform all functions and execute all procedures defined in 3GPP TS 38.420 / 38.421 / 38.422.

[0294] Neighbor gNB information for MWAB-gNB (106): The MWAB-gNB (106) will fetch the (dynamic) neighbour gNB information and other broadcast parameters and its cell information from OAM server by providing the current location of the MWAB-gNB (106). The MWAB-UE (108) will get the details of OAM server during MWAB authorization performed during MWAB-UE (108) registration or in any other NAS or AS message. The MWAB-gNB (106) will get the location information from the MWAB-UE (108) and use this information to fetch the neighbouring gNB (NG-RAN) information from the OAM server (or provide this information to OAM server so that OAM server can provide correct configuration and cell details as well as broadcast information to the MWAB-gNB(106)). The MWAB-gNB (106) may also fetch the broadcast information (System Information) and cell details such as cell-id / TAC etc. from the OAM server. The MWAB-gNB (106) may periodically fetch the updated information from the OAM server, or it may fetch it based on the updated location.In another embodiment, the MWAB-UE (108) will fetch the information from OAM server and provide this information to the MWAB-gNB (106). The MWAB-UE (108) connects to OAM server using the OAM server details configured in the MWAB-UE (108), downloads the information from OAM server which is required to act as gNB following legacy mechanisms. 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). Further, the gNB communicates with the 5GC servicing UE (114) and the BH-5GC (112).

[0295]

[0296] FIG. 3 depicts a multihop architecture for MWAB. In the proposed architecture, the UE (102) connected to and being served by any MWAB-gNB (106) may itself be an MWAB-UE (108). The MWAB-UE (108)(s) acting as a normal UE (102) can be served by the MWAB-gNB (106). The second MWAB-gNB (106) serving other UE(s) gets connected (establishes N2 / N3 / Xn interfaces with 5GC) to the 5GC via the PDU session provided by the second MWAB-UE (108). The second MWAB-UE (108) is connected via first MWAB-gNB (106) (as NG-RAN / gNB). The first MWAB-gNB (106) serving other UE(s) and second MWAB-UE (108) gets connected (establishes N2 / N3 / Xn interfaces with 5GC) to 5GC via the PDU session provided by the first MWAB-UE (108). In another embodiment, the MWAB-gNB (106) can continue to act as a normal gNB, providing no restriction on the type of UE (MWAB UE or normal UE (102)) which can connect to it.

[0297]

[0298] FIG. 4 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 (410), a communicator (420), a memory (430), and an interface creation controller (440). The processor (410) is coupled with the communicator (420), the memory (430), and the interface creation controller (440).

[0299] The interface creation controller (440) is configured to request the PDU session establishment to the MWAB-UE (108). Further, the interface creation controller (440) receives the IP connectivity from the MWAB-UE (108), upon establishment of the PDU session with the first network entity or modifying an existing PDU session with the first network entity. Further, the interface creation controller (440) creates a mobile interface with the at least one neighboring second network entity through the PDU session associated with the MWAB-UE (108).

[0300] In an embodiment, the interface creation controller (440) connects the at least one neighboring second network entity through the mobile interface.

[0301] In an embodiment, the interface creation controller (440) establishes or modifies the PDU session based on at least one of: a User Equipment Routing Selection Policy (URSP) rule and a local configuration.

[0302] In an embodiment, the at least one neighboring network entity is a Next Generation Radio Access Network (NG-RAN) node.

[0303] In an embodiment, the first network entity is a network which is serving the MWAB-UE (108). In an embodiment, the second network entity is a MWAB broadcasted Public Land Mobile Network (PLMN), and the MWAB-gNB (106) is acting as an gNB of a MWAB broadcasted PLMN. In an embodiment, the first network entity and the second network entity are the same network entity. In an embodiment, the first network entity and the second network entity are different network entity.

[0304] In an embodiment, the mobile interface is a Xn interface, the PDU session is a backhaul (BH) PDU session, and the Xn interface of the MWAB-gNB (106) is tunneled through the BH PDU session.

[0305] The interface creation controller (440) 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.

[0306] The processor (410) 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 (410) may include multiple cores and is configured to execute the instructions stored in the memory (430).

[0307] Further, the processor (410) is configured to execute instructions stored in the memory (430) and to perform various processes. The communicator (420) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (430) also stores instructions to be executed by the processor (410). The memory (430) 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 (430) 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 (430) 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).

[0308] Although FIG. 4 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).

[0309]

[0310] FIG. 5 is a flow chart (S500) illustrating the method for creating the mobile interface between the first Next Generation Node B (gNB), and the at least one neighboring network entity, according to embodiments as disclosed herein. The operations (S502-S506) are handled by the interface creation controller (440).

[0311] At S502, the method includes requesting the PDU session establishment to the MWAB-UE (108). At S504, the method includes receiving the IP connectivity from the MWAB-UE (108), upon establishment of the PDU session with the first network entity or modifying an existing PDU session with the first network entity. At S506, the method includes creating the mobile interface with the at least one neighboring second network entity through the PDU session associated with the MWAB-UE (108).

[0312] The UE enables to provide IP connectivity to the gNB. The gNB using the IP connectivity to connect to another gNB. i.e. Xn interface is tunnelled through backhaul (BH) PDU session of the MWAB-UE (108). This removes the need for fixed wireline access between two gNBs and enables for the two gNBs to be mobile because they are not connected by wireline access.

[0313] The proposed architecture and method will help provide Xn interface between the MWAB-gNB (106) and other NG-RAN / gNBs using the backhaul PDU session of the MWAB UE (108). This will help the MWAB-GNB (106) achieve connection with the dynamically changing neighbour gNB(s) when the MWAB-gNB (106) is in mobility. The MWAB-gNB (106) will be able to provide measurement configurations to served UE(s) based on Xn interface availability with neighbour cells. The MWAB gNB can also handover served UE(s) to neighbour cell using the Xn interface over backhaul PDU session.

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

[0315] The embodiment disclosed herein describes an Xn architecture and a multihop architecture for MWAB. 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 device or 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 atleast 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.

[0316] 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 creating a mobile interface between a first Next Generation Node B (gNB), and at least one neighboring network entity, comprising:requesting, by a mobile gNB with wireless access backhaul (MWAB) (MWAB-gNB) (106), a protocol data unit (PDU) session establishment to a MWAB-User Equipment (UE) (MWAB-UE) (108);receiving, by the MWAB-gNB (106), an internet protocol (IP) connectivity from the MWAB-UE (108), upon establishment of a PDU session with a first network entity or modifying an existing PDU session with the first network entity; andcreating, by the MWAB-gNB (106), the mobile interface with the at least one neighboring second network entity through the PDU session associated with the MWAB-UE (108).2.The method as claimed in claim 1, wherein the first network entity is a network which is serving the MWAB-UE (108).3.The method as claimed in claim 1, wherein the second network entity is a MWAB broadcasted Public Land Mobile Network (PLMN), and the MWAB-gNB (106) is acting as an gNB of a MWAB broadcasted PLMN.4.The method as claimed in claim 1, wherein the first network entity and the second network entity are same network entity.5.The method as claimed in claim 1, wherein the first network entity and the second network entity are different network entity.6.The method as claimed in claim 1, wherein the method comprises:connecting, by the MWAB-gNB (106), the at least one neighboring second network entity through the mobile interface.7.The method as claimed in claim 1, wherein the at least one neighboring network entity is a Next Generation Radio Access Network (NG-RAN) node.8.The method as claimed in claim 1, wherein the MWAB-UE (108) establishes or modifies the PDU session based on at least one of: a User Equipment Routing Selection Policy (URSP) rule and a local configuration.9.The method as claimed in claim 1, wherein the mobile interface is a Xn interface, the PDU session is a backhaul (BH) PDU session, and the Xn interface of the MWAB-gNB (106) is tunnelled through the BH PDU session.10.A mobile gNB with wireless access backhaul (MWAB) gNB) (MWAB-gNB (106), comprising:a processor (410);a memory (430); andan interface creation controller (440), coupled with the processor (410) and the memory (430), configured to:request a protocol data unit (PDU) session establishment to a MWAB-User Equipment (UE) (MWAB-UE) (108);receive an internet protocol (IP) connectivity from the MWAB-UE (108), upon establishment of a PDU session with a first network entity or modifying an existing PDU session with the first network entity; andcreate a mobile interface with the at least one neighboring second network entity through the PDU session associated with the MWAB-UE (108).11.The MWAB-gNB as claimed in claim 10, wherein the first network entity is a network which is serving the MWAB-UE.12.The MWAB-gNB as claimed in claim 10, wherein the second network entity is a MWAB broadcasted Public Land Mobile Network (PLMN), and the MWAB-gNB (106) is acting as an gNB of a MWAB broadcasted PLMN.13.The MWAB-gNB as claimed in claim 10, wherein the first network entity and the second network entity are same network entity.14.The MWAB-gNB as claimed in claim 10, wherein the first network entity and the second network entity are different network entity.15.The MWAB-gNB as claimed in claim 10, wherein the interface creation controller is further configured to:connect, by the MWAB-gNB, the at least one neighboring second network entity through the mobile interface.

Images