Method and apparatus for handling MWAB configuration of an OAM server in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose methods and systems for handling Mobile Next Generation Node B (gNB) with Wireless Access Backhauling (MWAB) configuration of Operations, Administration and Maintenance (OAM) servers in wireless communication networks. Embodiments herein define as to when a UE shall act as a MWAB-UE. Embodiments herein disclose methods and systems for configuring a MWAB-gNB with the required configurations to act as a gNB, and a network entity for configuring the MWAB-gNB with the required configurations to act as the gNB.

Description

METHOD AND APPARATUS FOR HANDLING MWAB CONFIGURATION OF AN OAM SERVER IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates to wireless communication system. And more particularly, the present disclosure relates to configuration of Operations, Administration and Maintenance (OAM) servers in wireless communication systems.

[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 (THz) 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] The present disclosure relates to method and apparatus for configuration of Operations, Administration and Maintenance (OAM) servers in wireless communication systems.

[0009] According to an aspect of an exemplary embodiment, there is provided a communication method in a wireless communication system.

[0010] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

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

[0012] FIG. 1 illustrates the UE configuration update procedure for transparent UE policy delivery, according to an embodiment of the present disclosure;

[0013] FIG. 2 illustrates the process of updating the UE parameters via a UDM control plane procedure, according to an embodiment of the present disclosure;

[0014] FIG. 3 illustrates the process of configuring the MWAB, according to an embodiment of the present disclosure;

[0015] FIG. 4 illustrates a flowchart depicting the process of handling a gNB with MWAB configuration of an OAM server, according to an embodiment of the present disclosure;

[0016] FIG. 5 depicts the UE, according to an embodiment of the present disclosure;

[0017] FIG. 6 illustrates the configuration of a UE in a wireless communication system according to various embodiments; and

[0018] FIG. 7 illustrates the configuration of a base station or a network entity in a wireless communication system according to various embodiments.

[0019] This application is based on and derives the benefit of Indian Provisional Application IN202441008431, and Indian Complete Patent Application IN 202441008431, all the contents of which are incorporated herein by reference.

[0020] For a Fifth Generation (5G) system with satellite access, the following requirements apply:

[0021] - The 5G system shall support service continuity between New Radio (NR) terrestrial access network and NR satellite access networks owned by the same operator or owned by two different operators having an agreement.

[0022] The Non-Terrestrial Network (NTN) and Terrestrial Network (TN) could either operate in two different frequency bands (for example, FR1, and FR2), or in the same frequency band (for example, FR1, or FR2).

[0023] User Equipment (UE) Route Selection Policy (URSP) or user route selection policies are policies which are configured in the UE, which help the applications running in the UE, to determine how and which specific paths to use to send upload (UL) data, for a matching data type. These policies are used by the UE to determine how to route outgoing traffic. The traffic can be routed to an established Packet Data Unit (PDU) session, can be offloaded to non-3GPP access outside a PDU Session, can be routed via a ProSe Layer-3 UE-to-Network Relay outside a PDU session, or can trigger the establishment of a new PDU Session.

[0024] Each URSP rule contains a traffic descriptor (containing one or more components described in Table 6.6.2.1-2) that determines when the respective rule is applicable. Each URSP rule contains a list of Route Selection Descriptors containing one or multiple Route Selection Descriptors each having a different Route Selection Descriptor Precedence value. Table 1 depicts an example route selection descriptor.

[0025]

[0026]

[0027]

[0028] A URSP rule is determined to be applicable when every component in the traffic descriptor (for traffic descriptor components other than the PIN ID) matches the corresponding information from the application, or matches the information configured for a PIN (if the URSP rule contains a PIN ID traffic descriptor component), or matches the information configured for a Connectivity Group (if the URSP rule contains a Connectivity Group ID traffic descriptor). If a URSP rule is provided that contains a traffic descriptor with two or more components, it is recommended to also provide URSP rule(s) with lower precedence and a Traffic descriptor with less components, to increase the likelihood of URSP rule matching for a particular application.

[0029] The UE configuration may be updated by the network at any time using a UE Configuration update procedure, or any other procedure. The UE configuration includes:

[0030] - Access and Mobility Management related parameters decided and provided by the Access and Mobility Management Function (AMF). This includes the Configured Network Slice Selection Assistance Information (NSSAI), and its mapping to the Subscribed Single - Network Slice Selection Assistance Information (S-NSSAIs), the Allowed NSSAI, and its mapping to Subscribed S-NSSAIs.

[0031] - UE Policy provided by the Policy Control Function (PCF).

[0032] When the AMF wants to change the UE configuration for access and mobility management related parameters, the AMF initiates the re-configuration procedure. When the PCF wants to change or provide new UE Policies in the UE, the PCF initiates the procedure for changing or providing new UE policies to the UE. If the UE Configuration Update procedure requires the UE to initiate a Registration procedure, the AMF indicates this to the UE explicitly. FIG. 1 depicts the UE configuration update procedure for transparent UE policy delivery.

[0033] The purpose of the control plane solution for update of UE parameters is to allow the Home Public Land Mobile Network (HPLMN) to update the UE with a specific set of parameters, generated and stored in the Unified Data Management (UDM), by delivering protected UDM Update Data, via Non-Access Stratum (NAS) signalling. The HPLMN updates such parameters based on the operator policies. FIG. 2 depicts the process of updating the UE parameters via a UDM control plane procedure. The UDM Update Data may contain one or more UE parameters including:

[0034] - the updated Default Configured NSSAI (final consumer of the parameter is the Mobile Equipment (ME));

[0035] - the updated Routing Indicator Data (final consumer of the parameter is the Universal Subscriber Identity Module (USIM));

[0036] - a "UE acknowledgement requested" indication; and

[0037] - a "re-registration requested" indication.

[0038] A UE can operate as a Mobile Wireless Access Backhaul (MWAB) to provide MWAB / NG-RAN services to other UE(s). For a UE to operate as an MWAB, it needs to get necessary configurations. However, it is not defined as to how the UE would get the necessary configurations required to operate as an MWAB mainly because the MWAB is mobile entity, and it may not be possible to have static connection with it to provide the configuration directly using the methods defined in the provide thus there is a need for a method which is dynamic in nature / does not need a static fibre connection to the gNB.

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

[0040] The principal object of embodiments herein is to disclose methods and systems for handling Mobile Next Generation Node B (gNB) with Wireless Access Backhauling (MWAB) configuration of Operations, Administration and Maintenance (OAM) servers in wireless communication networks.

[0041] Another object of embodiments herein is to define as to when a UE shall act as a MWAB-UE.

[0042] Another object of embodiments herein is to disclose methods and systems for configuring a MWAB-gNB with the required configurations to act as a gNB, and a network entity for configuring the MWAB-gNB with the required configurations to act as the gNB.

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

[0044] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms “comprising”, “having” and “including” are to be construed as open-ended terms unless otherwise noted.

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

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

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

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

[0049] The embodiments herein achieve methods and systems for handling Mobile Next Generation Node B (gNB) with Wireless Access Backhauling (MWAB) configuration of Operations, Administration and Maintenance (OAM) servers in wireless communication networks. Referring now to the drawings, and more particularly to FIGS. 3 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

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

[0051] 3GPP: Third Generation Partnership Project.

[0052] 4G-GUTI: 4G-Globally Unique Temporary Identifier.

[0053] 5G-BRG: 5G Broadband Residential Gateway.

[0054] 5GC: 5G Core.

[0055] 5GCN: 5G Core Network.

[0056] 5G-CRG: 5G Cable Residential Gateway.

[0057] 5G-GUTI: 5G-Globally Unique Temporary Identifier.

[0058] 5GMM: 5G Mobility Management.

[0059] 5G-RG: 5G Residential Gateway.

[0060] 5GS: 5G System.

[0061] 5GSM: 5GS Session Management.

[0062] 5G-S-TMSI: 5G S-Temporary Mobile Subscription Identifier.

[0063] 5G-TMSI: 5G Temporary Mobile Subscription Identifier.

[0064] 5QI: 5G QoS Identifier.

[0065] ACS: Auto-Configuration Server.

[0066] AKA: Authentication and Key Agreement.

[0067] A-KID: AKMA Key Identifier.

[0068] AKMA: Authentication and Key Management for Applications.

[0069] AMBR: Aggregate Maximum Bit Rate.

[0070] AMF: Access and Mobility Management Function.

[0071] APN: Access Point Name.

[0072] ARP: Allocation and Retention Policy.

[0073] AS: Access Stratum.

[0074] A-TID: AKMA Temporary Identifier.

[0075] ATSSS: Access Traffic Steering, Switching and Splitting.

[0076] AUSF: Authentication Server Function.

[0077] CAG: Closed access group.

[0078] CAG ID: Closed Access Group Identifier.

[0079] CHAP: Challenge Handshake Authentication Protocol.

[0080] CU: Centralized Unit.

[0081] DC: Discontinuous Coverage.

[0082] DisCo: Discontinuous Coverage.

[0083] DL: Downlink.

[0084] DND: Do not Disturb.

[0085] DRX: Discontinuous Reception.

[0086] DU: Distributed Unit.

[0087] eDRX : Extended Discontinuous Reception.

[0088] EHPLMN: Equivalent Home Public Land Mobile Network.

[0089] EMM: EUTRA Mobility Management.

[0090] eNB: Evolved Node-B.

[0091] eNPN: Enhanced Non-Public Networks.

[0092] EPC: Evolved Packet Core.

[0093] EPLMN: Equivalent Public Land Mobile Network.

[0094] EPS: Evolved Packet System.

[0095] eSIM: embedded Subscriber Identity Module.

[0096] E-UTRA: Evolved Universal Mobile Telecommunication Access.

[0097] EUTRAN: Evolved Universal Mobile Telecommunication Access Network.

[0098] FPLMN: Forbidden Public Land Mobile Network.

[0099] FR: Frequency Range.

[0100] GEO: Geostationary Orbit.

[0101] GERAN: GSM Edge Radio Access Network.

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

[0103] gNB: Next generation Node-B.

[0104] gNB - CU: Next generation Node-B Control Unit.

[0105] gNB - DU: Next generation Node-B Distributive Unit.

[0106] GPRS: General Packet Radio Service.

[0107] GPS: Global Positioning System.

[0108] GSM: Global System for Mobile Communication.

[0109] HPLMN: Home Public Land Mobile Network.

[0110] IAB: Integrated access and backhaul.

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

[0112] IE: Information Element.

[0113] LADN: Local Area Data Network.

[0114] LCS: Location services.

[0115] LEO: Low Earth Orbit.

[0116] MBSR: Mobile Base Station Relay.

[0117] MCC: Mobile Country Code.

[0118] MCS: Mission Critical Service.

[0119] ME: Mobile Equipment.

[0120] MEC: Multi-Access Edge Computing.

[0121] MEO: Medium Earth Orbit.

[0122] MICO : Mobile Initiated Communication Only.

[0123] MINT: Minimization of service interruption.

[0124] MME: Mobility Management Entity.

[0125] MNC: Mobile Network Code.

[0126] MPS: Multimedia Priority Service.

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

[0128] MWAB: Mobile Wireless Access Backhaul.

[0129] NAS: Non-Access Stratum.

[0130] NB-S1 Mode: Narrow Band with S1 Interface.

[0131] NGAP: Next Generation Application Protocol.

[0132] NG-RAN: Next Generation Radio Access Network.

[0133] NPN: Non-Public Networks.

[0134] NR: New Radio.

[0135] NTN: Non Terrestrial Networks.

[0136] NW: Network.

[0137] OOS: Out of Service.

[0138] OS Upgrade: Operating System Upgrade.

[0139] PDN: Packet Data Network.

[0140] PDU: Packet Data Unit.

[0141] PLMN ID: Public Land Mobile Network Identity.

[0142] PSM: Power Saving Mode.

[0143] QoS: Quality Of Service.

[0144] RAT: Radio Access Technology.

[0145] RPLMN: Registered Public Land Mobile Network.

[0146] RRC: Radio Resource Control.

[0147] RU: Registration Update.

[0148] SAT: Satellite.

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

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

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

[0152] SIM: Subscriber Identity Module.

[0153] SNPN: Standalone Non-Public Networks.

[0154] SUCI: Subscription Concealed Identifier.

[0155] SW: Software.

[0156] TAC: Tracking Area Code.

[0157] TAI: Tracking Area Identity.

[0158] TAU: Tracking Area Update.

[0159] TER: Terrestrial.

[0160] TN: Terrestrial Networks.

[0161] UCU: UE Configuration Update.

[0162] UDM: Unified Data Management Function.

[0163] UE: User Equipment.

[0164] UL: Uplink.

[0165] ULI: User Location Information.

[0166] UPU: UE Parameters Update.

[0167] USIM: Universal Subscriber Identification Module.

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

[0169] VMR: Vehicle Mounted Relay.

[0170] VPLMN: Visited Public Land Mobile Network.

[0171] WB-S1 Mode: Wide Band with S1 Interface.

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

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

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

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

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

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

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

[0179] Registered PLMN (RPLMN): This is the PLMN on which certain location registration (LR) (also referred to herein as a 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.

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

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

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

[0183] The following are an example list of NAS messages: 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, as referred to herein in 3GPP TS 24.501 or 3GPP TS 24.301.

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

[0185] 1) 5GMM-NULL

[0186] 2) 5GMM-DEREGISTERED

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

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

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

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

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

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

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

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

[0195] 3) 5GMM-REGISTERED-INITIATED

[0196] 4) 5GMM-REGISTERED

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

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

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

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

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

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

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

[0204] 5) 5GMM-DEREGISTERED-INITIATED

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

[0206] The term EMM sublayer states are at least one of the below:

[0207] 1) EMM-NULL

[0208] 2) EMM-DEREGISTERED

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

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

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

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

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

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

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

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

[0217] 3) EMM-REGISTERED-INITIATED

[0218] 4) EMM-REGISTERED

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

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

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

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

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

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

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

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

[0227] 5) EMM-DEREGISTERED-INITIATED

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

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

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

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

[0232] 5GS registration types 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.

[0233] PLMN selection as per 23.122 without RPLMN:

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

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

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

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

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

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

[0240] PLMN selection as per 23.122 with RPLMN:

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

[0242] - either the RPLMN or the Last registered PLMN;

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

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

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

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

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

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

[0249] The methods, issues or solutions referred to herein are explained using NR satellite access or Satellite NG-RAN Access Technology as an example and are not restricted or limited to NR Satellite access only. It may be obvious to a person of ordinary skill in the art that the solutions proposed herein are also applicable for Satellite E-UTRAN access Technology, NB (Narrow Band)-S1 mode or WB (Wide Band)-S1 mode via satellite E-UTRAN access and / or NB-IOT (NarrowBand Internet Of Things), or WB-IOT (WideBand Internet Of Things) Satellite Access / Architecture.

[0250] It may be obvious to a person of ordinary skill in the art that the solutions which are defined for NR (5GC) are also applicable to legacy RATs, such as, but not limited to, E-UTRA / LTE, the corresponding CN entities needs to be replaced by LTE entities (for example, AMF with MME, gNB with eNB, UDM with HSS, and so on).

[0251] The network as referred to herein are explained using any 5G Core Network Function; for example, AMF. It may be obvious to a person of ordinary skill in the art that the network could be any 5G / EUTRAN Core Network Entity (such as, but not limited to, AMF / SMF / MME / UPF), or the Network could be any 5G / EUTRAN RAN Entity (such as, but not limited to, eNB, or gNB, or NG-RAN, and so on).

[0252] The messages as referred to herein can be any signalling messages between the UE and the Network Functions / Entities or between different Network functions / entities.

[0253] The terms area / location / geographical area as referred to herein can refer to any of cell / cell ID, TAC / TAI, PLMN, MCC / MNC, Latitude / longitude, CAG cell, or any geographical location / coordinates.

[0254] The terms ‘camp’ and ‘register’ are used interchangeably herein, and have the same meaning.

[0255] The terms ‘wait timer’, ‘DisCo wait timer’, ‘Discontinuous Coverage wait timer’, ‘Random timer’, ‘Random wait timer’, and ‘DCW Timer’ are used interchangeably herein, and have the same meaning.

[0256] The terms ‘wait range’, ‘Disco Wait Range’, ‘Discontinuous Coverage Wait Range’, and ‘DCW Range’ are used interchangeably herein, and have the same meaning.

[0257] A list of possible AS messages have been provided in 3GPP TS 38.331 or 3GPP TS 36.331

[0258] The cause names as referred to herein are for illustration purposes and it can have any name. The non access stratum (NAS) messages and access stratum (AS) messages described herein are for illustration purposes, and it may be obvious to a person of ordinary skill that it can be any NAS or AS messages as per defined in the protocol between the UE, and the AMF / MME, or the UE and the gNB (NG-RAN / any RAN node) / eNB.

[0259] FIG. 3 depicts the process of configuring the MWAB. The 5G network can follow any of the following steps (1A - 4) to configure the MWAB-UE 101A, or / and the MWAB-gNB 101B.

[0260] In an embodiment herein, in step 1A(i), the UE 101 can send an indication to operate as a MWAB-UE 101A in the Registration request to the AMF 103. The AMF 103 can be one of a VPLMN AMF, or a HPLMN AMF. In step 1A(ii), the AMF 103 can send the configurations about the details of the server 105 (for example, OAM server details) in a Registration Accept message, or UE configuration update message, or in any other NAS message or as part of PCO / ePCO in a session management message (such as, but not limited to, PDU session establishment accept or PDU session modification accept), or using a new information element in NAS message (such as, but not limited to, 5GMM or 5GSM message). Examples of the OAM server details can be, but not limited to, Fully Qualified Domain Name (FQDN), Internet Protocol (IP) address, or any other OAM server detail.

[0261] In an alternate embodiment herein, in step 1B (as an alternate to steps 1A(i) & 1A(ii)), a UDM 104 may configure the MWAB-UE 101A using one of UPU (UE parameter Update procedure), or UCU (UE Configuration Update procedure) procedure, with the configurations about the details of the server 105 (for example, OAM server details).

[0262] In an alternate embodiment herein, in step 1B (as an alternate to steps 1A(i) & 1A(ii), and step 1B), the MWAB-UE 101A or / and the MWAB-gNB 101B may be pre-configured with the configurations about the details of the server 105 (for example, OAM server details).

[0263] Optionally, the details of the server 105 (for example, OAM server details) can be per VPLMN or / and per HPLMN.

[0264] In step 2, the MWAB-UE 101A can send the configurations about the details of the server 105 (for example, OAM server details) to the MWAB-gNB 101B / MWAB-UE 101A. In step 3, the MWAB-gNB 101B, and / or the MWAB-UE 101A can use these configurations to connect to the server 105 (for example, OAM server). In step 4, the server 105 can configure the MWAB-gNB 101B with the required configurations which are needed for the MWAB-gNB 101B to act as a gNB. This configuration will comprise at least one of the broadcast information of the SIBs, CAG information which needs to be broadcasted and the behaviour of the MWAB-gNB 101B on receiving this configuration.

[0265] In an embodiment herein, the configurations about the server details (e.g., OAM server details) are at least one of the following, or in any combination of the following:

[0266] - IP address of the server; 105

[0267] - FQDN of the server 105;

[0268] - DNN to be used for PDU session establishment;

[0269] - S-NSSAI to be used for PDU session establishment;

[0270] - Allowed area (term as defined in this embodiment) where the UE 101 is allowed to connect to the server;

[0271] - Allowed time where the UE 101 is allowed to connect to the server 105;

[0272] - Allowed VPLMN or HPLMN (on which the UE 101 is camped or registered with) where the UE 101 is allowed to connect to the server; and

[0273] - For the VPLMN or HPLMN for which the MWAB-gNB 101B can act as a gNB; i.e., the PLMN (also referred to as MWAB Broadcasted PLMN / SNPN) on which the MWAB-gNB 101B needs to integrate and act as a gNB.

[0274] If the UE 101 is not configured with the configurations about the server details (e.g., OAM server details), the UE 101 shall not act as a MWAB, and shall act as a normal UE.

[0275] The UE 101 may trigger the NAS procedure (such as, but not limited to, registration request procedure, UCU procedure, session management procedure, and so on), and indicate to the network function (NF) (for example, AMF or SMF) that it needs the configurations about the server details. Optionally, for the current camped PLMN or the PLMN-2 which needs to be broadcasted by the MWAB-gNB, the MWAB-gNB 101B will act as a gNB of that particular network of PLMN-2. In response to this request, the NF will configure the configurations about the details of the server 105.

[0276] In an embodiment herein, the DNN / S-NSSAI for connecting to the OAM server, may be configured in the MWAB-UE 101A in URSP rules. One or more MWAB-UE DNNs may be added to the DNN selection list in the Route Selection Descriptor (RSD) and / or one or more MWAB-UE N-SSAIs may be added to the Network Slice Selection list in the RSD.

[0277] In an embodiment herein, the MWAB-UE DNN or / and S-NSSAI may be explicitly configured or / and pre-configured in the SIM / USIM / ESIM or / and ME or / and UE.

[0278] In an embodiment herein, the configurations can be explicitly configured or / and pre-configured in the MWAB-UE or / and MWAB-gNB.

[0279] Optionally, the configurations can be configured per PLMN or / and per PLMN per area per time or / and per PLMN per area or / and per PLMN per time, wherein the PLMN can be a VPLMN or a HPLMN.

[0280] In an embodiment herein, the UE 101 connects to a second server over a data path (i.e., through PDU session connectivity) which provides configurations about the server details (e.g., OAM server details). The details to connect to the second server can be at least one of the below:

[0281] - IP address of the second server (e.g., which provides the configurations about the server details (e.g., OAM server details);

[0282] - FQDN of the second server (e.g., which provides the configurations about the server details (e.g., OAM server details);

[0283] - DNN to be used for PDU session establishment;

[0284] - S-NSSAI to be used for PDU session establishment;

[0285] - Allowed area (term as defined in this embodiment) where the UE is allowed to connect to the second server (which provides the configurations about the server details (e.g., OAM server details));

[0286] - Allowed time where the UE is allowed to connect to the second server (which provides the configurations about the server details (e.g., OAM server details));

[0287] - Allowed VPLMN or HPLMN (on which UE is camped or registered with) where the UE is allowed to connect to the second server (which provides the configurations about the server details ( e.g., OAM server details)); and

[0288] - For the VPLMN or HPLMN for which MWAB-gNB can act as a gNB; i.e., the PLMN on which the MWAB-gNB needs to integrate and act as a gNB.

[0289] The details to connect to the second server over the data path can be provided to the UE 101 following the same mechanisms as described in this embodiment to provide the configurations about the server details (e.g., OAM server details); i.e., either in a NAS message (such as, but not limited to, 5GMM, 5GSM), or a PCO / ePCO in a 5GSM message, and so on.

[0290] FIG. 4 is a flowchart depicting the process of handling a gNB with MWAB configuration of an OAM server. In step 401, the MWAB 101 receives the details of the OAM server 105. The details of the OAM server 105 comprises at least one of at least one of the dedicated Data Network Name, and Single - Network Slice Selection Assistance Information (DNN, and S-NSSAI) parameter for establishing a Packet Data Unit (PDU) session; the Internet Protocol (IP) address of the OAM server; and a Fully Qualified Domain Name (FQDN). In an embodiment herein, the OAM server details can be received from the AMF 103 as part of a Non-Access Stratum (NAS) message. In an embodiment herein, the OAM server details can be configured at the MWAB 101. In an embodiment herein, the OAM server details can be pre-configured at the MWAB 101. In an embodiment herein, the MWAB 101 can be configured with at least one configuration parameter on a per PLMN basis, wherein the MWAB uses the configuration parameter for the respective PLMN in the shared network scenario. The at least one configuration parameter comprises for a purpose including an access stratum operation of the MWAB-gNB; broadcast information to be used by the MWAB-gNB; activating / deactivating operation of the MWAB-gNB; and the CAG ID(s), wherein the CAG ID(s) comprise of location and time duration restriction which is used to perform access restriction by the MWAB-gNB. If the MWAB-gNB is serving a PNI-NPN, the CAG can be used for managing the UE's access to the MWAB-gNB cell, with the following additional considerations, The MWAB-gNB is configured either during the communication with the OAM of MWAB-gNB or (pre-)configuration mechanism, with one or more CAG identifiers which are unique within the scope of this PLMN. If the MWAB-gNB is (pre-)configured with the PLMN list supporting PNI-NPN, the corresponding CAG Identifiers per PLMN is also configured in the MWAB. The MWAB-gNB performs UE access control based on the CAG identifier associated with the MWAB-gNB cell. If the CAG identifier is broadcasted by the MWAB-gNB, the UE selects the cells of the MWAB-gNB only if those are part of allowed CAG list configured in the UE, if the UE selects the cell even though CAG ID is not part of allowed CAG list then either the MWAB-gNB or the AMF will reject the UE request and appropriately apply the access control of the UEs accessing the MWAB-gNB. Time validity information may be provided to the UE together with the CAG Identifier(s) of the MWAB-gNB(s) that the UE can access. If the evaluation of the time validity information of an entry in the Allowed CAG list changes, the updated Allowed CAG list will be provided to UE and MWAB-gNB by the AMF for enforcement, to make sure that the UE not accessing the corresponding MWAB-gNB cell outside of the time duration.

[0291] In step 402, the MWAB 101 connects to the OAM server 105 using the received OAM server details. In an embodiment herein, the MWAB 101 establishes a PDU session to connect with the OAM server using the received at least one of the DNN, and S-NSSAI. In an embodiment herein, the MWAB 101 indicates DNN, and S-NSSAI information to the UE using URSP rules. In step 403, the MWAB 101 receives at least one MWAB operations configuration from the OAM server. The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.

[0292] FIG. 5 depicts the UE. The UE 101 can function as a MWAB-UE 101A, and a MWAB-gNB 101B. The UE 101, as depicted, comprises a processing module 501, at least one memory 502, and at least one transceiver 503.

[0293] The processing module 501 can be at least one of a single processor, a plurality of processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units (CPUs) of different kinds, microcontrollers, special media, and other accelerators. The processing module 501 may be an Application Processor (AP), a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU), and / or an Artificial Intelligence (AI)-dedicated processor such as a Neural Processing Unit (NPU).

[0294] In an embodiment herein, the at least one transceiver 503 is configured to enable communication between the UE, and at least one external entity (such as, but not limited to, the HPLMN / VPLMN_1 102, the VPLMN_1 / VPLMN_2 104, and so on) through a network or cloud. The transceiver 503 through which the UE 101 and the at least one external entity communicate may include wired and / or wireless communication medium compatible with one or more different communication protocols. The transceiver 503 may be configured for communication through a network. The network may comprise, but are not limited to, Global Positioning System (GPS), Global System for Mobile Communications (GSM), Local Area Network (LAN), Wireless Fidelity (Wi-Fi) compatibility, Bluetooth Low Energy (BLE), Near-field Communication (NFC), and so on. The wireless communication may further comprise one or more of Bluetooth, Zonal Intercommunication Global Standard (ZigBee), short-range wireless communication such as Ultra-wideband (UWB), medium-range wireless communication such as Wi-Fi, or long-range wireless communication such as Third Generation (3G), Fourth Generation (4G), Fifth Generation (5G), Sixth Generation (6G), or Worldwide Interoperability for Microwave Access (WiMAX), according to the usage environment.

[0295] In the embodiment shown herein, the at least one memory 502 may comprise one or more volatile and non-volatile memory components that are capable of storing data and instructions to be executed. Examples of the at least one memory 502 can be, but are not limited to, NAND, embedded Multimedia Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid-state drive (SSD), and so on. The at least one memory 502 may also include one or more computer-readable storage media. Examples of 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 at least one memory 502 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 to mean that the at least one memory 502 is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (for example, in Random Access Memory (RAM) or cache).

[0296] The processing module 501 can receive the details of the OAM server 105, via the transceiver 503. The details of the OAM server 105 comprises at least one of at least one of the dedicated Data Network Name, and Single - Network Slice Selection Assistance Information (DNN, and S-NSSAI) parameter for establishing a Packet Data Unit (PDU) session; the Internet Protocol (IP) address of the OAM server; and a Fully Qualified Domain Name (FQDN). In an embodiment herein, the processing module 501 can receives the OAM server details from the AMF 103 as part of a Non-Access Stratum (NAS) message. In an embodiment herein, the processing module 501 can configure the OAM server details at the MWAB 101. In an embodiment herein, the OAM server details can be pre-configured at the MWAB 101. In an embodiment herein, the MWAB 101 can be configured with at least one configuration parameter on a per PLMN basis, wherein the MWAB uses the configuration parameter for the respective PLMN in the shared network scenario. The at least one configuration parameter comprises for a purpose including an access stratum operation of the MWAB-gNB; broadcast information to be used by the MWAB-gNB; activating / deactivating operation of the MWAB-gNB; and the CAG ID(s), wherein the CAG ID(s) comprise of location and time duration restriction which is used to perform access restriction by the MWAB-gNB.

[0297] The processing module 501 can connect to the OAM server 105 using the received OAM server details. In an embodiment herein, the processing module 501 can establish a PDU session to connect with the OAM server using the received at least one of the DNN, and S-NSSAI. In an embodiment herein, the processing module 501 can indicate DNN, and S-NSSAI information to the UE using URSP rules. The processing module 501 can receive at least one MWAB operations configuration from the OAM server.

[0298] FIG. 6 is a block diagram of an internal configuration of a UE, according to an embodiment. Furthermore, the UE of FIG. 6 corresponds to the UE of FIG. 3 and FIG. 5.

[0299] As shown in FIG. 6, the UE according to an embodiment may include a transceiver 610, a memory 620, and a processor 630. The transceiver 610, the memory 620, and the processor 630 of the UE may operate according to a communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. In addition, the processor 630, the transceiver 610, and the memory 620 may be implemented as a single chip. Also, the processor 630 may include at least one processor.

[0300] The transceiver 610 collectively refers to a UE receiver and a UE transmitter, and may transmit / receive a signal to / from a base station or a network entity. The signal transmitted or received to or from the base station or a network entity may include control information and data. The transceiver 610 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 610 and components of the transceiver 610 are not limited to the RF transmitter and the RF receiver.

[0301] Also, the transceiver 610 may receive and output, to the processor 630, a signal through a wireless channel, and transmit a signal output from the processor 630 through the wireless channel.

[0302] The memory 620 may store a program and data required for operations of the UE. Also, the memory 620 may store control information or data included in a signal obtained by the UE. The memory 620 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0303] The processor 630 may control a series of processes such that the UE operates as described above. For example, the transceiver 610 may receive a data signal including a control signal transmitted by the base station or the network entity, and the processor 630 may determine a result of receiving the control signal and the data signal transmitted by the base station or the network entity.

[0304] FIG. 7 is a block diagram of an internal configuration of a base station or a network entity, according to an embodiment. Furthermore, the base station or the network entity of FIG. 7 corresponds to the gNB, AMF, UDM, or server of FIG. 3.

[0305] As shown in FIG. 7, the base station(or the network entity receiver) according to an embodiment may include a transceiver 710, a memory 720, and a processor 730. The transceiver 710, the memory 720, and the processor 730 of the base station(or the network entity receiver) may operate according to a communication method of the base station(or the network entity receiver) described above. However, the components of the base station(or the network entity receiver) are not limited thereto. For example, the base station may include more or fewer components than those described above. In addition, the processor 730, the transceiver 710, and the memory 720 may be implemented as a single chip. Also, the processor 730 may include at least one processor.

[0306] The transceiver 710 collectively refers to the base station(or the network entity receiver) and a base station(or the network entity) transmitter, and may transmit / receive a signal to / from a terminal or a network entity or a base station. The signal transmitted or received to or from the terminal or a network entity or the base station may include control information and data. The transceiver 710 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 710 and components of the transceiver 710 are not limited to the RF transmitter and the RF receiver.

[0307] Also, the transceiver 710 may receive and output, to the processor 730, a signal through a wireless channel, and transmit a signal output from the processor 730 through the wireless channel.

[0308] The memory 720 may store a program and data required for operations of the base station(or the network entity receiver). Also, the memory 720 may store control information or data included in a signal obtained by the base station. The memory 720 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0309] The processor 730 may control a series of processes such that the base station(or the network entity receiver) operates as described above. For example, the transceiver 710 may receive a data signal including a control signal transmitted by the terminal or the network entity or the base station, and the processor 730 may determine a result of receiving the control signal and the data signal transmitted by the terminal or the network entity or the base station.

[0310] Accordingly, the embodiments herein provide a method for handling Mobile Next Generation Node B (gNB) with Wireless Access Backhauling (MWAB) configuration of an Operations, Administration and Maintenance (OAM) server. The method comprises a MWAB receiving OAM server details. The method further comprises the MWAB connecting to the OAM server using the received OAM server details; and receiving at least one MWAB operations configuration from the OAM server.

[0311] Accordingly, the embodiments herein provide a Mobile Next Generation Node B (gNB) with Wireless Access Backhauling (MWAB) comprising a processing module; a memory; and a transceiver. The processing module is coupled with the memory, and the transceiver, and configured to receive OAM server details. The processing module is further configured to connect to the OAM server using the received OAM server details; and receive at least one MWAB operations configuration from the OAM server.

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

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

[0314] The embodiments disclosed herein describe methods and systems for handling Mobile Next Generation Node B (gNB) with Wireless Access Backhauling (MWAB) configuration of Operations, Administration and Maintenance (OAM) servers in wireless communication networks. 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 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.

[0315] 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 and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practised with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a Mobile Next Generation Node B (gNB) with Wireless Access Backhauling (MWAB) configuration of an Operations, Administration and Maintenance (OAM) server, the method comprising:receiving, by the MWAB, OAM server details;connecting, by the MWAB, to the OAM server using the received OAM server details; andreceiving, by the MWAB, at least one MWAB operations configuration from the OAM server.2.The method of claim 1, wherein the OAM server details comprises at least one of:at least one of the dedicated Data Network Name, and Single - Network Slice Selection Assistance Information (DNN, and S-NSSAI) parameter for establishing a Packet Data Unit (PDU) session;Internet Protocol (IP) address of the OAM server; andFully Qualified Domain Name (FQDN).3.The method of claim 2, wherein the MWAB establishes a PDU session to connect with the OAM server using the received at least one of the DNN, and S-NSSAI.4.The method of claim 3, wherein the method comprises indicating, by the MWAB, DNN, and S-NSSAI information to the UE using UE Route Selection Policy (URSP) rules.5.The method of claim 1, wherein the OAM server details are at least one of:received from an Access and Mobility Management Function (AMF) as part of a Non-Access Stratum (NAS) message;configured at the MWAB; andpre-configured at the MWAB.6.The method of claim 1, wherein the MWAB comprises a MWAB - User Equipment (UE); and a MWAB-gNB.7.The method of claim 5, wherein the method comprises configuring the MWAB with at least one configuration parameter on a per Public Land Mobile Network (PLMN) basis, wherein the MWAB uses the configuration parameter for the respective PLMN in the shared network scenario, and the at least one configuration parameter comprises:for a purpose including an access stratum operation of the MWAB-gNB;broadcast information to be used by the MWAB-gNB;activating / deactivating operation of the MWAB-gNB; andthe CAG ID(s), wherein the CAG ID(s) comprise of location and time duration restriction which is used to perform access restriction by the MWAB-gNB.8.A Mobile Next Generation Node B (gNB) with Wireless Access Backhauling (MWAB) in a wireless communication system, comprising:a transceiver; andat least one processor coupled with the transceiver and configured to:receive OAM server details;connect to the OAM server using the received OAM server details; andreceive at least one MWAB operations configuration from the OAM server.9.The MWAB of claim 8,wherein the OAM server details comprises at least one of:at least one of the dedicated Data Network Name, and Single - Network Slice Selection Assistance Information (DNN, and S-NSSAI) parameter for establishing a Packet Data Unit (PDU) session;Internet Protocol (IP) address of the OAM server; andFully Qualified Domain Name (FQDN).10.The MWAB of claim 9, wherein the at least one processor is configured to establish a PDU session to connect with the OAM server using the received at least one of the DNN, and S-NSSAI.11.The MWAB of claim 10, wherein the at least one processor is configured to indicate the DNN, and S-NSSAI information to the UE using UE Route Selection Policy (URSP) rules.12.The MWAB of claim 8, wherein the OAM server details are at least one of:received from an Access and Mobility Management Function (AMF) as part of a Non-Access Stratum (NAS) message;configured at the MWAB; andpre-configured at the MWAB.13.The MWAB of claim 8,wherein the MWAB comprises a MWAB - User Equipment (UE); and a MWAB-gNB.14.The MWAB of claim 13, wherein the at least one processor is configured to configure the MWAB with at least one configuration parameter on a per Public Land Mobile Network (PLMN) basis, wherein the processing module is configured to use the configuration parameter for the respective PLMN in the shared network scenario, and the at least one configuration parameter comprises:for a purpose including an access stratum operation of the MWAB-gNB;broadcast information to be used by the MWAB-gNB;activating / deactivating operation of the MWAB-gNB; andthe CAG ID(s), wherein the CAG ID(s) comprise of location and time duration restriction which is used to perform access restriction by the MWAB-gNB.

Images