WO2025193002A1 - Methods and apparatus for managing non-terrestrial network configuration in wireless communication system - Google Patents

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a management Service (MnS) producer in a non-terrestrial network (NTN) system includes receiving, from an MnS consumer, a create managed object instance (MOI) request for an information object class (IOC) for satellite information, the IOC for satellite information including information related to an ephemeris and a store and forward (S&F) mode of operation; configuring, based on the IOC for satellite information, an MOI for satellite information for a base station; and transmitting, to the MnS consumer, a response indicating successful configuration of the MOI for satellite information.

Description

METHODS AND APPARATUS FOR MANAGING NON-TERRESTRIAL NETWORK CONFIGURATION IN WIRELESS COMMUNICATION SYSTEM

Embodiments disclosed herein relate to non-terrestrial communication networks, and more particularly to managing Non-Terrestrial Network (NTN) configuration(s).

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.

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.

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.

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.

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.

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.

Embodiments of the present disclosure is to provide an apparatus and method for effectively providing a service in Non-Terrestrial Network (NTN) system.

In an embodiment, a method performed by a management Service (MnS) producer in a non-terrestrial network (NTN) system is provided. The method includes receiving, from an MnS consumer, a create managed object instance (MOI) request for an information object class (IOC) for satellite information, the IOC for satellite information including information related to an ephemeris and a store and forward (S&F) mode of operation; configuring, based on the IOC for satellite information, an MOI for satellite information for a base station; and transmitting, to the MnS consumer, a response indicating successful configuration of the MOI for satellite information.

In an embodiment, a method performed by a management Service (MnS) consumer in a non-terrestrial network (NTN) system is provided. The method includes transmitting, to an MnS producer, a create managed object instance (MOI) request for an information object class (IOC) for satellite information, the IOC for satellite information including information related to an ephemeris and a store and forward (S&F) mode of operation; and receiving, from the MnS producer, a response indicating successful configuration of an MOI for satellite information for a base station. The MOI for satellite information is associated with the IOC for satellite information.

In an embodiment, a management Service (MnS) producer in a non-terrestrial network (NTN) system is provided. The MnS producer includes a transceiver and at least one processor. The at least one processor is configured to receive, from an MnS consumer via the transceiver, a create managed object instance (MOI) request for an information object class (IOC) for satellite information, the IOC for satellite information including information related to an ephemeris and a store and forward (S&F) mode of operation, configure, based on the IOC for satellite information, an MOI for satellite information for a base station, and transmit, to the MnS consumer via the transceiver, a response indicating successful configuration of the MOI for satellite information.

In an embodiment, a management Service (MnS) consumer in a non-terrestrial network (NTN) system is provided. The MnS consumer include a transceiver and at least one processor. The and at least one processor is configured to transmit, to an MnS producer, a create managed object instance (MOI) request for an information object class (IOC) for satellite information, the IOC for satellite information including information related to an ephemeris and a store and forward (S&F) mode of operation, and receive, from the MnS producer via the transceiver, a response indicating successful configuration of an MOI for satellite information for a base station. The MOI for satellite information is associated with the IOC for satellite information.

Accordingly, the embodiments herein provide a method for managing a Non-Terrestrial Network (NTN) configuration in at least one satellite by a Management Service (MnS) producer. The method comprises receiving a create Managed Object Instance (MOI) request for a SatelliteInfo Information Object Class (IOC), from a MnS consumer, for allowing at least one NTN connected base station to support a Store and Forward (S&F) mode of operation. The method comprises creating a SatelliteInfo MOI for the NTN connected base station, on receiving the create MOI request. Thereafter, the method comprises configuring the SatelliteInfo IOC for the NTN connected base station. The method comprises sending a response including the created SatelliteInfo MOI, and a successful configuration of the SatelliteInfo IOC to the MnS consumer.

Accordingly, the embodiments herein provide a MnS producer. The MnS producer comprises a processor, and a memory module. The processor is coupled with the memory module. The processor is configured to receive a create MOI request for a SatelliteInfo IOC, from a MnS consumer, for allowing at least one NTN connected base station to support an S&F mode of operation. The processor is configured to create a SatelliteInfo MOI for the NTN connected base station, on receiving the create MOI request. The processor is configured to configure the SatelliteInfo IOC for the NTN connected base station. Further, the processor is configured to send a response including the created SatelliteInfo MOI, and a successful configuration of the SatelliteInfo IOC to the MnS consumer.

These and other aspects of the example 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 example embodiments 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 example embodiments herein without departing from the spirit thereof, and the example embodiments herein include all such modifications.

According to the embodiments in the present disclosure, the NTN function in a regenerative mode can be supported.

According to the embodiments in the present disclosure, a new SatelliteInfo Information Object Class (IOC) for specifying the management of Store and Forward (S&F) satellites can be introduced.

According to the embodiments in the present disclosure, the SatelliteInfo Information IOC can enable at least one NTN connected base station to support an S&F mode of operation.

According to the embodiments in the present disclosure, the SatelliteInfo information related to at least one of an ephemeris, the S&F mode of operation, and one or more parameters for managing the S&F mode of operation can be configured.

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:

FIG. 1 illustrates a Non-Terrestrial Network (NTN), according to an embodiment of the present disclosure;

FIG. 2 illustrates a block diagram of a system for managing an NTN configuration in at least one satellite, according to an embodiment of the present disclosure;

FIG. 3 illustrates a block diagram indicating a plurality of modules of a Management Service (MnS) producer, according to an embodiment of the present disclosure;

FIG. 4 illustrates a method for managing the NTN configuration in at least one satellite by the MnS producer, according to an embodiment of the present disclosure;

FIG. 5 illustrates an example Network Resource Management　(NRM) fragment with the NTN management supporting the S&F mode of operation, according to an embodiment of the present disclosure;

FIG. 6 illustrates an alternate NRM fragment with the NTN management supporting the S&F mode of operation, according to an embodiment of the present disclosure;

FIG. 7 illustrates an alternate NRM fragment with the NTN management supporting the S&F mode of operation, according to an embodiment of the present disclosure;

FIG. 8 illustrates a flow process for managing S&F satellites, according to an embodiment of the present disclosure;

FIG. 9 illustrates a management service (MnS) producer according to an embodiment of the present disclosure; and

FIG. 10 illustrates a management service (MnS) consumer according to an embodiment of the present disclosure.

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.

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.

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.

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.

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.

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.

The embodiments herein provide methods and systems for managing Non-Terrestrial Network (NTN) configuration(s). Referring now to the drawings, and more particularly to FIGS. 1 through 8, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

FIG. 1 illustrates a Non-Terrestrial Network (NTN), according to an embodiment of the present disclosure.

Referring to FIG. 1, the NTN can provide a non-terrestrial New Radio (NR) access to a User Equipment (UE) using an NTN payload, and an NTN gateway. The NTN comprises a service link between the NTN payload and the UE, and a feeder link between the NTN Gateway and the NTN payload. The NTN payload can transparently forward a radio protocol received from the UE (via the service link) to the NTN gateway (via the feeder link) and vice-versa. The following connectivity can be supported by the NTN payload: an NTN gateway may serve multiple NTN payloads, and an NTN payload may be served by multiple NTN gateways. Three types of service links are supported:

- Earth-fixed: provisioned by beam(s) continuously covering the same geographical areas all the time (for example, the case of Geosynchronous Orbit (GSO) satellites);

- Quasi-Earth-fixed: provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (for example, the case of Non-Geostationary Orbit　(NGSO) satellites generating steerable beams); and

- Earth-moving: provisioned by beam(s) whose coverage area slides over the Earth surface (for example, the case of NGSO satellites generating fixed or non-steerable beams).

With NGSO satellites, the gNB can provide either a quasi-earth-fixed service link or an earth-moving service link, while the gNB operating with the GSO satellite can provide an earth fixed service link.

5G system comprises of a 5G Access Network (AN), a 5G core network, and a UE, see TS 23.501. The 5G system can provide optimized support for a variety of communication services, traffic loads, and end-user communities.

For example, the communication services using network slicing may include Vehicle-to-everything (V2X) services. The 5G system aims to enhance its capability to meet Key Performance Indicators (KPIs) required by the emerging V2X applications. For these advanced applications, the requirements, for example, data rate, reliability, latency, communication range, and speed, are made more stringent.

As one of the key technologies, Fixed Mobile Convergence (FMC) (which may include Wireless-To-The-Everything (WTTx), and Fibre-To-The-Everything (FTTx)) can provide native support for network slicing. For optimization and resource efficiency, the 5G system can select the most appropriate 3GPP or non-3GPP access technology for a communication service, potentially allowing multiple access technologies to be used simultaneously for one or more services active on a UE, and massive Internet of Things (IoT) connections (for example, but not limited to, support for massive Internet of Things (mIoT) brings many new requirements in addition to Mobile Broadband (MBB) enhancements).

The communication services with massive IoT connections, for example, smart households, smart grid, smart agriculture, and smart meter may require the support of a large number, and high density IoT devices to be efficient and cost effective. Operators can use one or more network slice instances to provide these communication services, which may require similar network characteristics, to vertical industries. 3GPP TS 28.530 and 28.531 defines the management of network slice in 5G networks. It also defined the concept of communication services, which can be provided using one or multiple network slice. A Network Slice Instance (NSI) may support multiple Communication Service Instances (CSIs). Similarly, a CSI may utilize multiple NSIs. A slice serves users in a particular geographical location knows as slice coverage area.

5G NTN related specification have requirement for Store and Forward (S&F) mode of operations. S&F satellite operation is an operation mode of a 5G system with satellite-access, where the 5G system can provide some level of service (for example, storing and forwarding the data) when satellite connectivity is intermittently/temporarily unavailable. For example, to provide communication service for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment. This is particularly relevant for delay tolerant IoT services via an NGSO space segment.

The current NR-Network Resource Management　(NRM) definitions do not support NTN function in a regenerative mode. The NR-NRM only supports transport mode of operation. In case of regenerative mode of operation, an attribute nTNpLMNInfoList (in NTNFunction IOC) may contradict the attribute pLMNId (in GNBCUCPFunction IOC).

The current network management provisions do not specify the management of S&F satellite. The 5G NRM does not support the management of a gNB that is operating under S&F mode. Several configurations related to storage quota, delivery time and acknowledgement need to be provided to the gNB in order to have this S&F functionality working efficiently. The forwarding policies need to be defined and configured for gNB. The current provisioning mechanism does not support having all the above configurations and policies to be enabled in the gNB.

FIG. 2 illustrates a block diagram of a system for managing an NTN configuration in at least one satellite, according to an embodiment of the present disclosure.

Referring to FIG. 2, the system 200 comprises an　Access and Mobility Management Function (AMF)　202, a　provisioning or Management Service (MnS) producer or an MnS producer 204, a　provisioning MnS consumer or an MnS consumer 206, a base station (gNB) 208, a　satellite　210, and a　UE　212. An NTN may provide New Radio (NR) access to the UE 212, via the　satellite 210,　and an NTN gateway. The　satellite 210　may communicate with the　UE 212　via a service link. The NTN gateway and the　satellite 210　may communicate via a feeder link. The　satellite 210　may forward radio protocol received via the service link from the　UE 212　to the NTN gateway via the feeder link, and vice-versa. The NTN gateway may serve multiple satellites, and　single satellite 210　may be served by multiple NTN gateways. The　satellite 210　may include, but is not limited to, a communication satellite, a navigation satellite, a broadcasting satellite, a fixed satellite, and so on. The　UE 212　may be a system or device such as, a laptop computer, a desktop computer, a Personal Computer (PC), a notebook, a smartphone, a tablet, a server, a network server, a cloud-based server, and so on.

In an embodiment herein, the MnS producer 204 can be configured in the AMF 202. The MnS producer 204 and the AMF 202 can be implemented in a core network. The provisioning MnS consumer 206 can be implemented as Operations & Maintenance (O&M) system. The MnS producer 204 can be a network node for the NTN management.

In an embodiment herein, entities that produce Management Services (MnS) can be referred to as provisioning MnS producers, while entities consuming the MnS can be referred to as MnS consumers. In an embodiment herein, the MnS producer 204, and the MnS consumer 206 can exchange satellite information.

FIG. 3 illustrates a block diagram indicating a plurality of modules of a Management Service (MnS) producer, according to an embodiment of the present disclosure.

Referring to FIG.3, the MnS producer 204 comprises a processor 302, a communication module 304, and a memory module 306.

In an embodiment herein, the processor 302 can configure a new extension that shall provide information to manage Store and Forward (S&F) satellite operation. The provided information can be included as part of an NTN function. The processor 302 further comprises an NTN function module 308, and an S&F managing module 310.

In an embodiment herein, the NTN function module 308 can receive a create Managed Object Instance (MOI) request for an NTN function Information Object Class (IOC), from the MnS consumer 206. The create MOI request is for configuring at least one base station (gNB) 208 with an NTN access. The NTN function module 308 can create an NTN function MOI for the base station 208, on receiving the create MOI request. The NTN function module 308 can send a response including the created NTN function MOI to the MnS consumer 206.

In an embodiment herein, the NTN function module 308 can receive an attribute modify request of a gNB function MOI of the base station 208, from the MnS consumer 206. The attribute modify request is received for connecting the base station 208 with the created NTN function MOI. The NTN function module 308 can update at least one NTN function attribute of the gNB function MOI with a Distinguished Name (DN) of the created NTN function MOI for creating at least one NTN connected base station. The NTN function module 308 can send a response including the updated NTN function attribute to the MnS consumer 206. In an embodiment herein, the gNB function MOI of the NTN connected base station comprises a pLMNId attribute in a gNodeB Central Unit Control Plane Function (GNBCUCPFunction) IOC for providing an NTN specific PLMN information for a regenerative mode of operation.

In an embodiment herein, the S&F managing module 310 can receive a create MOI request for a SatelliteInfo IOC, from the MnS consumer 206. The create MOI request for the SatelliteInfo IOC is received for allowing at least one NTN connected base station to support an S&F mode of operation. The SatelliteInfo IOC comprises information related to at least one of an ephemeris, the S&F mode of operation, and one or more parameters for managing the S&F mode of operation. The parameters comprises at least one of a date retention period, a storage quota per UE, a storage quota per Application Function (AF), an expected Mobile Originated (MO) delivery time to AF, an expected Mobile Terminated (MT) delivery time to UE, an MO acknowledgement availability, an MT acknowledgement availability, and one or more message forwarding priorities to UE 212 and AF. The message forwarding priorities comprises at least one of a first come first forwarded, an AF (MO) based priority, and a UE (MT) based priority.

In an embodiment herein, the S&F managing module 310 can create a SatelliteInfo MOI for the NTN connected base station, on receiving the create MOI request. The S&F managing module 310 can configure the SatelliteInfo IOC for the NTN connected base station. The S&F managing module 310 can send a response including the created SatelliteInfo MOI, and a successful configuration of the SatelliteInfo IOC to the MnS consumer 206.

In an embodiment herein, the processor 302 can process and execute data of a plurality of modules of the MnS Producer 204. The processor 302 can be configured to execute instructions stored in the memory module 306. The processor 302 may comprise one or more of microprocessors, circuits, and other hardware configured for processing. The processor 302 can be at least one of a single processer, a plurality of processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units (CPUs) of different kinds, microcontrollers, special media, and other accelerators. The processor 302 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)).

In an embodiment herein, the plurality of modules of the processor 302 of the MnS Producer 204 can communicate via the communication module 304. The communication module 304 may be in the form of either a wired network or a wireless communication network module. The wireless communication network may comprise, but not limited to, Global Positioning System (GPS), Global System for Mobile Communications (GSM), Wi-Fi, Bluetooth low energy, Near-field communication (NFC), and so on. The wireless communication may further comprise one or more of Bluetooth, ZigBee, a short-range wireless communication (such as Ultra-Wideband (UWB)), and a medium-range wireless communication (such as Wi-Fi) or a long-range wireless communication (such as 3G/4G/5G/6G and non-3GPP technologies or WiMAX), according to the usage environment.

In an embodiment herein, the memory module 306 may comprise one or more volatile and non-volatile memory components which are capable of storing data and instructions of the modules of the MnS Producer 204 to be executed. Examples of the memory module 306 can be, but not limited to, NAND, embedded Multi Media Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid-state drive (SSD), and so on. The memory module 306 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 memory module 306 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 memory module 306 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).

FIG. 3 shows example modules of the MnS Producer 204, but it is to be understood that other embodiments are not limited thereon. In other embodiments, the MnS Producer 204 may include less or more number of modules. Further, the labels or names of the modules are used only for illustrative purpose and does not limit the scope of the invention. One or more modules can be combined together to perform same or substantially similar function in the MnS Producer 204.

FIG. 4 illustrates a method for managing the NTN configuration in at least one satellite by the MnS producer, according to an embodiment of the present disclosure.

Referring to FIG. 4, the method 400 comprises receiving a create Managed Object Instance (MOI) request for a SatelliteInfo IOC, from the MnS consumer 206, as depicted in step 402. The SatelliteInfo IOC allows at least one NTN connected base station to support the S&F mode of operation.

The method 400 comprises creating a SatelliteInfo MOI for the NTN connected base station, as depicted in step 404, on receiving the create MOI request. The method 400 comprises configuring the SatelliteInfo IOC for the NTN connected base station, as depicted in step 406, after creating the SatelliteInfo MOI. Thereafter, the method 400 comprises sending a response including the created SatelliteInfo MOI, and a successful configuration of the SatelliteInfo IOC, as depicted in step 408, to the MnS consumer 206.

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.

FIG. 5 illustrates an example Network Resource Management　(NRM) fragment with the NTN management supporting the S&F mode of operation, according to an embodiment of the present disclosure.

Referring to FIG. 5, the GNBCUCPFunction can have direct association (represented by an attribute nTNFunctionRef) with the NTN function with 1..0..1 relation. This implies that a gNB can have a single NTN function configuration available to it. The direct association indicates that a particular gNB is supporting that NR NTN. The nTNpLMNInfoList attribute in the NTN function IOC can be condition mandatory (CM) with the condition of "transparent mode of satellite communication is used". For example, the attribute nTNpLMNInfoList can only be present in the transparent mode. In this case, the attribute pLMNId (in GNBCUCPFunction IOC) may indicate non-NTN PLMN, and the attribute nTNpLMNInfoList (in NTN function IOC) may indicate NTN PLMN. Iin case of regenerative mode of operation, the NTN specific PLMN information provided by the attribute pLMNId in GNBCUCPFunction IOC is applied.

As depicted in the FIG. 5, the SatelliteInfo IOC contains all the satellite related configurations. This IOC is in composition relation with the NTN function IOC with 1...* relation. An S&FConfigInfo attribute contains information related with generic configuration for the satellite 210. In this embodiment herein, the existing 'EphemerisInfos' attribute which is a part of the SatelliteInfo IOC can be added directly to the SatelliteInfo IOC making the existing EphemerisInfoSet IOC obsolete.

FIG. 6 illustrates an alternate NRM fragment with the NTN management supporting the S&F mode of operation, according to an embodiment of the present disclosure.

Referring to FIG. 6, The GNBCUCPFunction can have direct association (represented by an attribute nTNFunctionRef) with the NTN function with 1..0..1 relation. This implies that a gNB can have a single NTN function configuration available to it. The direct association indicates that a particular gNB is supporting NR NTN. The attribute nTNpLMNInfoList in the NTN function IOC can be condition mandatory (CM) with the condition of "transparent mode of satellite communication is used". For example, the attribute nTNpLMNInfoList can only be present in transparent mode. In this case, the attribute pLMNId (in GNBCUCPFunction IOC) may indicate non-NTN PLMN, and the attribute nTNpLMNInfoList (in NTN function IOC) may indicate NTN PLMN. In case of regenerative mode of operation, the NTN specific PLMN information provided by the attribute pLMNId in the GNBCUCPFunction IOC is applied.

In this embodiment herein, the existing EphemerisInfoSet IOC can be retained and can be in direct association with the SatelliteInfo IOC. The new SatelliteInfo IOC is introduced to contain all the satellite related configuration except Ephemeris information. This SatelliteInfo IOC can be in composition relation with the NTN function IOC with 1...* relation. The S&FConfigInfo attribute contains information related with generic configuration for the satellite 210. This S&FConfigInfo IOC can be further extended to include other satellite specific information.

FIG. 7 illustrates an alternate NRM fragment with the NTN management supporting the S&F mode of operation, according to an embodiment of the present disclosure.

Referring to FIG. 7, the attribute nTNpLMNInfoList in the NTN function IOC can be Condition Mandatory (CM) with the condition of "transparent mode of satellite communication is used". For example, the attribute nTNpLMNInfoList can only be present in the transparent mode. In this case, the attribute pLMNId (in GNBCUCPFunction IOC) may indicate non-NTN PLMN, and the attribute nTNpLMNInfoList (in NTN function IOC) may indicate NTN PLMN. In case of regenerative mode of operation, the NTN specific PLMN information provided by the attribute pLMNId in the GNBCUCPFunction IOC is applied.

The GNBCUCPFunction can be in direct association (represented by an attribute satelliteInfoRef) with the SatelliteInfo with 1..1 relation. The new SatelliteInfo IOC is introduced to contain all the satellite related configuration except Ephemeris information. This SatelliteInfo IOC can be in composition relation with NTNFunction IOC with 1...* relation. Embodiments herein disclose the S&FConfigInfo attribute, wherein the S&FConfigInfo attribute contains information related with generic configuration for the satellite 210. This IOC can be further extended to include other satellite specific information.

The following extensions are proposed to the NR NRM defined in 3GPPT TS 28.541. The extension shall provide information to manage the S&F satellite operation. This information can be included as part of NTN function as defined in 3GPP TS 28.541.

- S&FConfigInfo: This defines information to manage the S&F satellite operation. The parameters for managing the S&F mode of operation include:

　■- Date retention period: duration for which the data should be stored before it gets discarded.

　■- Storage quota:

　　◆- Per UE (MO): This defines the total storage quota assigned to a single UE.

　　◆- Per AF (MT): This defines the total storage quota assigned to a single AF.

　■- Expected delivery time:

　　◆- MO delivery time to AF

　　◆- MT delivery time to UE

　■- Acknowledgement availability:

　　◆- MO acknowledgement: Yes/No. If the value is YES, the gNB provides acknowledgement to UE after receiving the MO message.

　　◆- MT acknowledgement: Yes/No. If the value is YES, the gNB provides acknowledgement to AF after receiving the MT message.

　■- Forwarding priorities (to UE and AF):

　　◆- First come first forwarded: This will imply that the messages received first will be delivered first to UE and AF in MT and MO respectively.

　　◆- AF (MO) based priority: Various AFs can be provided with the priorities. This will imply that the messages received for a higher priority AF will be delivered first. This can be implemented with a list of AF's Fully Qualified Domain Name　(FQDN) in the chronological order of their priorities.

　　◆- UE (MT) based priority: Various UE can be provided with the priorities. This will imply that the messages received for a higher priority UE will be delivered first. This can be implemented with a list of UE identifier (IMSI, IMEI, Anonymous id, for example C-RNTI, and so on) in the chronological order of their priorities.

FIG. 8 illustrates a flow process for managing S&F satellites, according to an embodiment of the present disclosure.

Referring to FIG. 8, in step 1, when an operator wants to configure a gNB 208 with NTN access, the MnS consumer 206 sends a create MOI request to the MnS producer 204 for instantiation of the NTN function IOC. In case of the regenerative mode of operation, the attribute nTNpLMNInfoList will not be configured. In the transparent mode of operation, the nTNpLMNInfoList will be configured with the PLMN supported by the gNB 208 in case of NTN access. In step 2, the MnS producer 204 creates a NTNFunction MOI and sends a response. In step 3, after the NTNFunction is created, this NTNFunction needs to be connected to the gNB 208. To achieve this, the MnS consumer 206 sends a modifyMOIAttributes request for an existing GNBCUCPFunction MOI to update the value of the attribute nTNFunctionRef with the DN of the NTNFunction MOI (as created in step 2). In step 4, the MnS producer 204 updates the value, and returns the response.

In step 5, the operator decides for the gNB 208 to support S&F mode of operation based on local policies and service contracts. In step 6, the MnS consumer 206 sends a createMOI request for SatelliteInfo IOC. The SatelliteInfo IOC contains information related with ephemeris, and S&F mode of operation. In step 7, the MnS producer 204 configures the information. In step 8, the MnS producer 204 sends the response indicating the successful configuration.

Embodiments herein enable a single NRM model to handle both transparent and regenerative modes of satellite operation.

The GNBCUCPFunciton having a direct relation with NTN function can simplify the NRM model used for management, because now one NTN function can relate to one gNB, and there can be multiple satellites with satellite specific information (ephemeris, S&F), in relation with one single NTN function.

FIG. 9 illustrates a management service (MnS) producer according to an embodiment of the present disclosure.

Referring to the FIG. 9, the MnS producer 900 may include a processor (or a controller) 910, a transceiver 920 and a memory 930. However, all of the illustrated components are not essential. The MnS producer 900 may be implemented by more or less components than those illustrated in FIG. 9. In addition, the processor 910 and the transceiver 920 and the memory 930 may be implemented as a single chip according to another embodiment.

The MnS producer 900 may correspond to MnS producer described above. For example, the MnS producer 900 may correspond to the MnS producer 204 illustrated in FIGs, 2, 3, and 8.

The aforementioned components will now be described in detail.

The processor 910 may include one or more processors or other processing devices that control the proposed function, process, and/or method. Operation of the MnS producer 900 may be implemented by the processor 910.

The transceiver 920 may include a RF transmitter for up-converting and amplifying a transmitted signal, and a RF receiver for down-converting a frequency of a received signal. However, according to another embodiment, the transceiver 920 may be implemented by more or less components than those illustrated in components.

The transceiver 920 may be connected to the processor 910 and transmit and/or receive a signal. The signal may include control information and data. In addition, the transceiver 920 may receive the signal through a wireless channel and output the signal to the processor 910. The transceiver 920 may transmit a signal output from the processor 910 through the wireless channel.

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

FIG. 10 illustrates a management service (MnS) consumer according to an embodiment of the present disclosure.

Referring to the FIG. 10, the MnS consumer 1000 may include a processor (or a controller) 1010, a transceiver 1020 and a memory 1030. However, all of the illustrated components are not essential. The MnS consumer 1000 may be implemented by more or less components than those illustrated in FIG. 10. In addition, the processor 1010 and the transceiver 1020 and the memory 1030 may be implemented as a single chip according to another embodiment.

The MnS consumer 1000 may correspond to the gNB described above. For example, the MnS consumer 1000 may correspond to the MnS producer 206 illustrated in FIGs, 2, 3, and 8.

The aforementioned components will now be described in detail.

The processor 1010 may include one or more processors or other processing devices that control the proposed function, process, and/or method. Operation of the MnS consumer 1000 may be implemented by the processor 1010.

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

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

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

Although this disclosure has been described with an exemplary embodiment, various changes and modifications may be suggested to one skilled in the art. It is intended that this disclosure encompass such changes and modifications as fall within the scope of the appended claims.

Embodiments herein enable efficient configuration of core satellite functionalities including ephemeris information, and S&F information including S&F configuration. This standardized model for configurations enables efficient NTN management in a multi-vendor environment where gNB and OAM components come from different vendors.

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 network elements shown in FIG. 2 and FIG. 3 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

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 practiced with modification within the scope of the embodiments as described herein.

Claims (15)

1. A method performed by a management Service (MnS) producer in a non-terrestrial network (NTN) system, the method comprising:

   receiving, from an MnS consumer, a create managed object instance (MOI) request for an information object class (IOC) for satellite information, the IOC for satellite information including information related to an ephemeris and a store and forward (S&F) mode of operation;

   configuring, based on the IOC for satellite information, an MOI for satellite information for a base station; and

   transmitting, to the MnS consumer, a response indicating successful configuration of the MOI for satellite information.
2. The method of claim 1, wherein the IOC for satellite information includes an IOC for S&F configuration information.
3. The method of claim 2, wherein the IOC for S&F configuration information includes at least one of:

   data retention period information indicating a duration for which data is to be stored before being discarded,

   storage quota information indicating a total storage quota assigned to a user equipment (UE) or an application function (AF),

   estimated delivery time information indicating a mobile originated (MO) delivery time to the AF or a mobile terminated (MT) delivery time to the UE,

   acknowledgement availability information indicating whether the base station is to provide an acknowledgement after receiving an MO message or an MT message, and

   forwarding priority information indicating a priority rule for forwarding a received message.
4. The method of claim 3, wherein the priority rule specifies that:

   a message received first is to be delivered first to the UE or the AF in MT and MO respectively,

   a message received for a higher priority AF is to be delivered first, or

   a message received for a higher priority UE is to be delivered first.
5. A method performed by a management Service (MnS) consumer in a non-terrestrial network (NTN) system, the method comprising:

   transmitting, to an MnS producer, a create managed object instance (MOI) request for an information object class (IOC) for satellite information, the IOC for satellite information including information related to an ephemeris and a store and forward (S&F) mode of operation; and

   receiving, from the MnS producer, a response indicating successful configuration of an MOI for satellite information for a base station,

   wherein the MOI for satellite information is associated with the IOC for satellite information.
6. The method of claim 5, wherein the IOC for satellite information includes an IOC for S&F configuration information.
7. The method of claim 6, wherein the IOC for S&F configuration information includes at least one of:

   data retention period information indicating a duration for which data is to be stored before being discarded,

   storage quota information indicating a total storage quota assigned to a user equipment (UE) or an application function (AF),

   estimated delivery time information indicating a mobile originated (MO) delivery time to the AF or a mobile terminated (MT) delivery time to the UE,

   acknowledgement availability information indicating whether the base station is to provide an acknowledgement after receiving an MO message or an MT message, and

   forwarding priority information indicating a priority rule for forwarding a received message.
8. The method of claim 7, wherein the priority rule specifies that:

   a message received first is to be delivered first to the UE or the AF in MT and MO respectively,

   a message received for a higher priority AF is to be delivered first, or

   a message received for a higher priority UE is to be delivered first.
9. A management Service (MnS) producer in a non-terrestrial network (NTN) system, the MnS producer comprising:

   a transceiver; and

   at least one processor configured to:

   receive, from an MnS consumer via the transceiver, a create managed object instance (MOI) request for an information object class (IOC) for satellite information, the IOC for satellite information including information related to an ephemeris and a store and forward (S&F) mode of operation,

   configure, based on the IOC for satellite information, an MOI for satellite information for a base station, and

   transmit, to the MnS consumer via the transceiver, a response indicating successful configuration of the MOI for satellite information.
10. The MnS producer of claim 9, wherein the IOC for satellite information includes an IOC for S&F configuration information.
11. The MnS producer of claim 10, wherein the IOC for S&F configuration information includes at least one of:

    data retention period information indicating a duration for which data is to be stored before being discarded,

    storage quota information indicating a total storage quota assigned to a user equipment (UE) or an application function (AF),

    estimated delivery time information indicating a mobile originated (MO) delivery time to the AF or a mobile terminated (MT) delivery time to the UE,

    acknowledgement availability information indicating whether the base station is to provide an acknowledgement after receiving an MO message or an MT message, and

    forwarding priority information indicating a priority rule for forwarding a received message.
12. The MnS producer of claim 11, wherein the priority rule specifies that:

    a message received first is to be delivered first to the UE or the AF in MT and MO respectively,

    a message received for a higher priority AF is to be delivered first, or

    a message received for a higher priority UE is to be delivered first.
13. A management Service (MnS) consumer in a non-terrestrial network (NTN) system, the MnS consumer comprising:

    a transceiver; and

    at least one processor configured to:

    transmit, to an MnS producer, a create managed object instance (MOI) request for an information object class (IOC) for satellite information, the IOC for satellite information including information related to an ephemeris and a store and forward (S&F) mode of operation, and

    receive, from the MnS producer via the transceiver, a response indicating successful configuration of an MOI for satellite information for a base station,

    wherein the MOI for satellite information is associated with the IOC for satellite information.
14. The MnS consumer of claim 13, the IOC for satellite information includes an IOC for S&F configuration information.
15. The MnS consumer of claim 13, wherein the IOC for S&F configuration information includes at least one of:

    data retention period information indicating a duration for which data is to be stored before being discarded,

    storage quota information indicating a total storage quota assigned to a user equipment (UE) or an application function (AF),

    estimated delivery time information indicating a mobile originated (MO) delivery time to the AF or a mobile terminated (MT) delivery time to the UE,

    acknowledgement availability information indicating whether the base station is to provide an acknowledgement after receiving an MO message or an MT message, and

    forwarding priority information indicating a priority rule for forwarding a received message, the priority rule specifying that:

    a message received first is to be delivered first to the UE or the AF in MT and MO respectively,

    a message received for a higher priority AF is to be delivered first, or

    a message received for a higher priority UE is to be delivered first.