Time advance configuration in batch for regenerative non-terrestrial network system

Abstract

A method performed by a terrestrial network management node manages base stations in satellites. The method obtains a list of associations between base stations in satellites and access mobility functions on ground and related time windows indicating when the associations in the list are valid. For each of the base stations in satellites, the method sends to the base station a batch of the associations of the base station to the access mobility functions and related time windows indicating when the associations in the batch are valid. For each of the access mobility functions, the method sends to the access mobility function a batch of the associations of the access mobility function to the base stations in satellites and related time windows indicating when the associations in the batch are valid.

Description

TIME ADVANCE CONFIGURATION IN BATCH FOR REGENERATIVE NON-TERRESTRIAL NETWORK SYSTEMTECHNICAL FIELD

[0001] The present disclosure relates to fixed and mobile communication systems and more particularly to configuring time advance for non-terrestrial network systems.BACKGROUND

[0002] In 3GPP Release 8, the Evolved Packet System (EPS) was specified. EPS is based on the Long-Term Evolution (LTE) radio network and the Evolved Packet Core (EPC). It was originally intended to provide voice and mobile broadband (MBB) services but has continuously evolved to broaden its functionality. Since Release 13 NB-IoT and LTE-M are part of the LTE specifications and provide connectivity to massive machine type communications (mMTC) services.

[0003] In 3GPP Release 15, the first release of the 5G system (5GS) was specified. This is a new generation’s radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and mMTC. 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC). The NR physical and higher layers are reusing parts of the LTE specification, and to that add needed components when motivated by new use cases. One such component is the introduction of a sophisticated framework for beam forming and beam management to extend the support of the 3GPP technologies to a frequency range going beyond 6 GHz.

[0004] In Release 15, 3GPP started the work to prepare NR for operation in a NonTerrestrial Network (NTN). The work was performed within the study item “NR to support Non-Terrestrial Networks”. In Release 16, the work to prepare NR for operation in an NTN network continued with the study item “Solutions for NR to support Non-Terrestrial Network”. In parallel the interest to adapt NB-IoT and LTE-M for operation in NTN is growing. As a consequence, 3GPP Release 17 specified support for operating NB-IoT, LTE-M and NR over an NTN.

[0005] A Non-Terrestrial Network (NTN) is now discussed.

[0006] In 3GPP NTN includes both satellite communication and communications using high-altitude platforms (HAPS). In this section we focus on satellite communication, but theprovided description could also be applied to a HAPS network. A satellite radio access network usually includes the following components.

[0007] A space segment, comprising one or more satellites with a communication payload hosted on a space-borne platform.

[0008] A ground segment, comprising Earth-based ground stations that connect the satellite to a base station or a core network, depending on the choice of architecture.

[0009] Feeder link that refers to the link between a gateway and a satellite.

[0010] Access link or service link that refers to the link between a satellite and a UE.

[0011] Depending on the orbit altitude, a satellite may be categorized as geostationary Earth orbit (GEO) satellite, and non-geo synchronized flying satellites, including, but not limited to low Earth orbit (LEO), medium Earth orbit (MEO), where:• LEO: typical heights ranging from 250 - 1,500 km, with orbital periods ranging from 90 - 120 minutes;• MEO: typical heights ranging from 5,000 - 25,000 km, with orbital periods ranging from 3 - 15 hours; and• GEO: height at about 35,786 km, with an orbital period of 24 hours.

[0012] A communication satellite may implement either a transparent or a regenerative (with on board digital processing) payload. The satellite typically generates several beams over a given area. The footprint of a beam is usually in an elliptic shape, which has been traditionally considered as a cell. The footprint of a beam is also often referred to as a spotbeam. The footprint of a beam may move over the Earth surface with the satellite movement or may be Earth fixed with some beam pointing mechanism used by the satellite to compensate for its motion. The size of a spotbeam depends on the satellite antenna design in NTN system, which may range from tens of kilometers to a few thousands of kilometers.

[0013] Figure 1 shows an example architecture of a satellite network with so-called “bent pipe” transponders, i.e. transparent payload implemented on the satellites where data is transmitted to the satellite, which sends the data directly down to a ground station again like a bent pipe, alternative data RF signals transmitted to the satellite in a given receive band (the transponder bandwidth) are relayed by the satellite to the ground after frequency conversion. The depicted elevation angle of the service link is important as it impacts the distance between the satellite and the device, and the velocity of the satellite relative to the device.

[0014] Figure 2 shows an example architecture of a satellite network with regenerative gNodeB (gNB) processed payload implemented on the satellites. The NG interface is on the feeder link between the Core network and the on-board NTN gNB.

[0015] 3GPP Management and orchestration of the 5G networks are now discussed.

[0016] In 3GPP, management and orchestration of the 5G (Terrestrial) Network has been defined in TS (Technical Specification) 28.532 V18.1.0 (2023-12) (Generic management services) and 28.541 vl 8.6.1 (2024-01) (5G Network Resource Model (NRM)) since release- 15 together with a number of related specifications. To access and manage the resources represented by the NRM, a Service Based Management Architecture (SBMA) has been defined directed to the so-called Management Service (MnS) concept, defined in TS 28.533 vl 8.0.0 (2023-12).

[0017] Parts of the core network AMF function NRM fragment (in 3GPP TS 28.541 V18.6.1 (2024-01)) are shown in Figure 5.2.1.1-2 of 3GPP TS 28.541.

[0018] Figure 4.2.1.1-1 of 3GPP TS 28.541 V18.6.1 (2024-01) illustrates a Network Resource Model for gNB in all deployment scenarios.

[0019] Figure 4.2.1.1-1 of 3GPP TS 28.541 V18.6.1 (2024-01) shows that, for example, GNBDUFunction may contain (be related to) zero or more NRCellDU, and GNBCUCPFunction may contain zero or more NRCellCU. For a description of the various gNB deployment scenarios, see the definitions of GNBDUFunction , GNBCUCPFunction and GNBCUUPFunction in TS 28.541 vl 8.6.1 (2024-01) clauses 4.3.1, 4.3.2 and 4.3.3.

[0020] Figure 4.2.1.1-2 of 3GPP TS 28.541 V18.6.1 (2024-01) illustrates a Network Resource Model for end points for gNB in all deployment scenarios.

[0021] Figure 4.2.1.1-2 of 3GPP TS 28.541 V18.6.1 (2024-01) shows that, for example, GNBCUCPFunction may contain zero or more EP_NgC (NG-C endpoint), where each EP_NgC has a dependency to one AMFFunction.

[0022] The EP_NgC attributes and their definitions according to Rel-18 are listed below:Table 1 illustrates attributes and their definitions of EP_NgC and EP_N2.

[0023] Figure 4.2.1.1-3 of 3GPP TS 28.541 V18.6.1 (2024-01) illustrates a Network Resource Model for NRSectorCarrier, Bandwidth Part (BWP), and BWPSet for all deployment scenarios.

[0024] Figure 4.2.1.1-3 of 3GPP TS 28.541 V18.6.1 (2024-01) shows that, for example, each NRCellDU has a dependency to zero or one NRSectorCarrier, and each NRSectorCarrier has a dependency to zero or one SectorEquipmentFunction.

[0025] The NRSectorCarrier attributes and their definitions according to Rel-18 are listed below. Note: The attribute type “DN” (Distinguished Name) is defined in TS 32.300 vl 8.0.0(2023-12).Table 2 (above) discloses attributes and their definitions of NRSectorCarrier.

[0026] The SectorEquipmentFunction attributes and their definitions according to Rel-18 are listed below in Table 3 (below), which can correspond to the description of 3GPP TS 28.662V17.0.0 (2022-03) Generic Radio Access Network (RAN) Network Resource Model (NRM)Integration Reference Point (IRP); Information Service (IS).Table 3 discloses attributes and their definitions of Sector EquipmentFunction.

[0027] Figure 5.2.1.1-2 of 3GPP TS 28.541 illustrates a Network Resource Model for End points in AMF. The illustration shows that, for example, AMFFunction may contain zero or more EP_N2 (NG-C / N2 endpoint), where each EP_E2 has a dependency to one GNBFunction / GNBCUCPfunction.

[0028] The EP_NG attributes and their definitions according to Rel-18 are the same as for EP_NgC.

[0029] O-RAN Management of fronthaul for 5G RAN is now discussed.

[0030] In O-RAN an architecture where 3GPP DU is split into O-DU and O-RU, connected together by O-RAN Lower-Layer Split (O-RAN LLS), according to Figure 3, which corresponds to Figure 5.1.1-1 in O-RAN. WG4.MP.0-R003-vl4.00. The Lower-Layer Split M- plane (LLS-M) facilitates the initialization, configuration and management of the O-RU to support the stated functional split.

[0031] Figure 3 illustrates an O-RAN Fronthaul functional split.

[0032] A NETCONF / YANG based M-Plane is used for supporting the management features including "start up" installation, software management, configuration management, performance management, fault management and file management towards the O-RU. The M- Plane supports two architectural models:

[0033] First, is a Hierarchical model. As shown on the left side of Figure 3, the O-RU is managed entirely by one or more O-DU(s) (acting as O-RU controller(s)), using a NETCONF based M-Plane interface.

[0034] Second, is a Hybrid model. As shown on the right side of Figure 3, the hybrid architecture enables one or more direct logical interface(s) between management system(s) (also acting as O-RU controller(s)) and O-RU in addition to a logical interface between O-DU and the O-RU.

[0035] The O-RAN M-Plane specification informs as to an O-RU establishing IP connectivity to O-RU controller(s). Operations for O-RU establish IP and NETCONF connectivity to O-RU Controllers as per the O-RAN M-Plane specification, where the O-RUControllers are discovered from DHCP. O-RU Controllers can also be manually assigned or provisioned in the YANG model by an existing O-RU Controller with NETCONF connectivity.

[0036] There currently exist certain challenge(s). For example when non-geo synchronized objects like LEO and MEO satellites are used for the NTN system, then the satellites will not always be at the same position relative the Earth’s surface, and the coverage area on the Earth surface for one satellite varies over time.

[0037] One consequence of non-geosynchronous satellites is that the associations between the entities on ground segment and entities in space segment are changing frequently, typically with a period of one to several minutes.

[0038] Figure 4 illustrates non-geosynchronous satellites in NTN system with transparent satellite payload.

[0039] Figure 4 illustrates this association change in an NTN system with transparent satellite payload. In this case, the ground segment gNB will serve the same spotbeam all the time, while different satellites (satellite 1, 2 and 3) in the space segment will serve the same spotbeam in different time periods as the satellites are approaching and leaving the coverage to the spotbeam over time. From management point of view, it will, for example, impact the association between NRSectorCarrier and SectorEquipmentFunction.

[0040] Figure 5 illustrates non-geosynchronous satellites in NTN with regenerative gNB processed satellite payload.

[0041] In this case, the ground segment Core Network (CN) will serve the same spotbeams all the time, while the space segment gNB on different satellites (satellite 1 , 2 and 3) will serve the spotbeam in different time period as the satellites are approaching and leaving the coverage of the spotbeam over time. From management point of view, it will, for example, impact the association between GNBDUFunction and NRCellDU, between GNBCUCPFunction and NRCellCU, and between GNBCUCPFunction and AMFFunction.

[0042] Another issue is the topology between space segment Managed Element (MnS producer) and the ground-based Management System (MnS consumer): With long distances in between, disturbances (e.g. bad weather conditions), and partial reachability issues (when satellites fly over oceans with no gateway coverage), the latency, availability and reliability of the interface between them (feeder link + Inter-satellite link) are impacted.

[0043] In 3GPP TR 23.700-29 v0.3.0 (2024-01) the problem with dynamic association between TA (timing advance) and cellld has been mentioned, however it has been limited to N2 / NG-C setup / suspension between RAN and CN, and does not cover the problem withassociation between network elements in space segment and ground segment in both transparent satellites and regenerative satellites described above.

[0044] S5-236095 resolves AMF to be configured with the discontinuous coverage availability information for each RAT Type. But it doesn’t solve the problem with association between network elements in space segment and ground segment in both transparent satellites and regenerative satellites described above.

[0045] S5-236097 resolves the issue that AMF should be configured with the restrictions to be imposed on accessing an NTN PLMN from a particular location. But it doesn’t solve the problem with association between network elements in space segment and ground segment in both transparent satellites and regenerative satellites described above.

[0046] Various operations related to regenerative NTN system are now described in further detail.

[0047] The NRCellCU attributes and their definitions according to 3GPP Rel-18 are listed below:

[0048] The NRCellDU attributes and their definitions according to Rel-18 are listed below:

[0049] Potential problems that can arise with existing approaches are now described.

[0050] When non-geo synchronized objects like LEO and MEO satellites are used for the NTN system, then the satellites will not always be at the same position relative the earth’s surface, and the coverage area on the earth surface for one satellite varies over time.

[0051] One consequence of non-geosynchronous satellites is that in case of satellite network with regenerative gNB processed payload and with earth-fixed NTN cells or quasiearth fixed NTN cells are applied, the associations between the gNB in space and NTN cells which are fixed with respect to the ground are changing frequently, typically with a period of one to several minutes.

[0052] Figure 20 illustrates this association change in an NTN system with regenerative gNB satellite payload. In this case, the space segment gNB on different satellites (satellite 1, 2 and 3) will serve different spotbeams (NTN cells) in different time period as the satellites are approaching and leaving the coverage of different spotbeams over time. From managementpoint of view, it will e.g. impact the association between GNBDUFunction and NRCellDU, and the association between GNBCUCPFunction and NRCellCU.

[0053] Another issue is the topology between space segment Managed Element (MnS producer) and the ground based Management System (MnS consumer): With long distances in between, disturbances (e.g. bad weather conditions), and partial reachability issues (when satellites fly over oceans with no gateway coverage), the latency, availability and reliability of the interface between them (feeder link + Inter-satellite link) are impacted.

[0054] In 3GPP TR 23.700-29 the problem with dynamic association between TA and cellld has been mentioned, however it has been limited to N2 / NG-C setup / suspension between RAN and CN, and does not address the problem with dynamic association between ground fixed NTN cells and the gNB in space.

[0055] S5-236095 resolves AMF to be configured with the discontinuous coverage availability information for each RAT Type. But it doesn’t solve the problem with dynamic association between ground fixed NTN cells and the gNB in space described above.

[0056] S5-236097 resolves the issue that AMF should be configured with the restrictions to be imposed on accessing an NTN PLMN from a particular location. But it doesn’t solve the problem dynamic association between ground fixed NTN cells and the gNB in space.SUMMARY

[0057] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0058] Some embodiments are directed to a method performed by a terrestrial network management node to manage base stations in satellites. The method obtains a list of associations between base stations in satellites and access mobility functions on ground and related time windows indicating when the associations in the list are valid. For each of the base stations in satellites, the method sends to the base station a batch of the associations of the base station to the access mobility functions and related time windows indicating when the associations in the batch are valid. For each of the access mobility functions, the method sends to the access mobility function a batch of the associations of the access mobility function to the base stations in satellites and related time windows indicating when the associations in the batch are valid.

[0059] Some other embodiments are directed to a method performed by a terrestrial network management node for managing base stations in satellites. The method obtains future time associations between base stations in satellites and Non-Terrestrial Network, NTN, cell coverage on ground. Based on the future time associations, the method determines a list of NTN cell configurations with related time windows indicating when the associations in the list of NTN cell configurations are valid, and sends a batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite.

[0060] Some other embodiments are directed to a method performed by a base station in a satellite for serving ground fixed Non-Terrestrial Network, NTN, cells. The method includes receiving from a terrestrial network management node, a list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid. Responsive to determining that one of the time windows has become valid, the method performs communications using the NTN cell configuration in the list related with the valid time window.

[0061] Some other embodiments are directed to a method performed by a terrestrial network management node for managing O-RU functions in satellites communicating with O- DU functions of base stations on ground. The method includes obtaining a list of associations between O-RUs in satellites and the O-DU functions of the base stations on ground and related time windows indicating when the associations in the list are valid, for each of the O-RUs in satellites, the method sends to the O-RU indications of a batch of the associations of the O-RU to the O-DU functions of the base stations and related time windows indicating when the associations in the batch are valid. For each of the O-DU function of the base station on ground, the method sends to the O-DU function indications of a batch of the associations of the O-DU function to the O-RUs and related time windows indicating when the associations in the batch are valid.

[0062] Certain benefits may be provided by one or more of these embodiments. By performing the batch configuration with time stamp, the problem with interface resiliency between the gNBs in space (Managed Elements) and the management system can be mitigated because the configurations can be sent beforehand with relaxed real time requirement. The embodiments may improve the possibility to extend the configuration of a managed element in a batch with a list of pre-configurations and related time stamps (time windows), and the procedure for potential update / cancellation of the existing pre-configuration.BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Aspects of the present disclosure are illustrated by way of example and are not limited by the accompanying drawings. In the drawings:

[0064] Figure 1 illustrates an example architecture of a satellite network with “bent pipe” transponders which send data directly down to a ground station;

[0065] Figure 2 illustrates an example architecture of a satellite network with regenerative gNodeB (gNB) processed payload implemented on the satellites;

[0066] Figure 3 illustrates an O-RAN Fronthaul functional split;

[0067] Figure 4 illustrates non-geosynchronous satellites in NTN system with transparent satellite payload;

[0068] Figure 5 illustrates non-geosynchronous satellites in NTN with regenerative gNB processed satellite payload;

[0069] Figure 6 illustrates a components and operations for use with a 3GPP management architecture according to some embodiments of the present disclosure;

[0070] Figure 7 illustrates NTN functions for regenerative gNB processed satellite payload;

[0071] Figure 8 illustrates a sequence diagram configuration of gNB / AMF endpoint as a batch according to some embodiments of the present disclosure;

[0072] Figure 9 illustrates location of NTN functions for transparent satellite payload according to 3GPP architecture;

[0073] Figure 10 illustrates a sequence diagram configuration of Sector Carrier / Sector Equipment function associations as a batch according to some embodiments of the present disclosure;

[0074] Figure 11 illustrates location of NTN functions for transparent satellite payload according to O-RAN architecture;

[0075] Figure 12 illustrates a modified establishing of connectivity to O-RU Controller(s) according to some embodiments of the present disclosure;

[0076] Figure 13 illustrates a flowchart of operations performed by the terrestrial network management node in accordance with some embodiments;

[0077] Figure 14 illustrates a flowchart of operations performed by the base station in accordance with some embodiments;

[0078] Figure 15 illustrates a flowchart of operations performed by the access mobility function in accordance with some embodiments;

[0079] Figure 16 illustrates a flowchart of operations performed by the terrestrial network management node in accordance with some embodiments;

[0080] Figure 17 illustrates a flowchart of operations performed by the sector equipment in accordance with some embodiments;

[0081] Figure 18 illustrates a flowchart of operations performed by the base station in accordance with some embodiments;

[0082] Figure 19 illustrates a flowchart of operations performed by the terrestrial network management node in accordance with some embodiments;

[0083] Figure 20 illustrates an association change in an NTN system with regenerative gNB satellite payload;

[0084] Figure 21 illustrates a block diagram of a 3GPP management architecture configured to operate in accordance with present embodiments of the disclosure;

[0085] Figure 22 illustrates locations of NTN functions for performing regenerative gNB processing of satellite payload;

[0086] Figure 23 illustrates a sequence diagram for setup of the batch configuration in advance and the results of the batch configuration in accordance with some embodiments;

[0087] Figure 24 illustrates a sequence diagram of operations performed according to some embodiments of solution 2;

[0088] Figure 25 illustrates a flowchart of operations performed by the terrestrial network management node in accordance with some embodiments;

[0089] Figure 26 illustrates a flowchart of operations performed by the base station in a satellite in accordance with some embodiments;

[0090] Figure 27 shows an example of a communication system in accordance with some embodiments;

[0091] Figure 28 shows a UE in accordance with some embodiments;

[0092] Figure 29 shows a network node in accordance with some embodiments;

[0093] Figure 30 is a block diagram of a host, which may be an embodiment of the host of Figure 27 according to some embodiments of the present disclosure;

[0094] Figure 31 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and

[0095] Figure 32 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.DETAILED DESCRIPTION

[0096] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0097] Timing Advance Configuration in Batch for NTN Systems:

[0098] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In case the orbit of the space segment entities, for example, LEO and MEO satellites, can be sufficiently estimated in advance, the corresponding Earth surface coverage over future time periods can be pre-calculated. The Management system can therefore pre-calculate the future time associations between ground entities and on-board entities in the NTN system.

[0099] These future pre-calculated associations can then be converted to a list of configurations with time stamps (more precisely: time windows), and transmitted to the Managed element as a batch, with the time stamp included for each configuration entry.

[0100] One aspect of the present disclosure includes the possibility to extend the configuration of a managed element in a batch with a list of pre-configurations and related time stamps (time windows), and the procedure for potential update / cancellation of the existing preconfiguration.

[0101] Certain embodiments may provide one or more of the following technical advantage(s). By the batch configuration with time stamp, the problem with interface resiliency between the Managed Element and the Management system can then be mitigated as the configurations can be sent beforehand with relaxed real time requirement. As stated above, the teachings of certain embodiments may improve the possibility to extend the configuration of a managed element in a batch with a list of pre-configurations and related time stamps (time windows), and the procedure for potential update / cancellation of the existing preconfiguration.

[0102] Some operations of the present disclosure are described in the context of being performed by base stations and access mobility functions. A base station can be, without limitation, a gNodeB, gNB, or an eNodeB, eNB. The access mobility function may be, without limitation, an Access and Mobility Function, AMF, or a Mobility Management Entity, MME. Some operations of the present disclosure are described in the context of being performed by a terrestrial network management node which may correspond to a Network Management node.

[0103] Some operations are described in the context of the 3GPP management architecture shown in Figure 6 according to some embodiments of the present disclosure.

[0104] For NTN with regenerative gNB processed satellite payload, it is assumed that the sector equipment and gNB are located at the satellites, while AMF and Network Management are located on ground according to Figure 7.

[0105] Figure 7 illustrates locating of NTN functions for regenerative gNB processed satellite payload.

[0106] As explained above, the interface between functions in the ground segment and space segment is unreliable, and the relationship between the gNB and AMF is changing all the time, therefore there is a need to pre-configure the relation (association) between gNB and AMF end points as a batch in advance.

[0107] In order to realize batch configuration of the association, one possible solution is to modify the EP_NgC (on gNB side) and EP_N2 (on AMF side) instances according to Table 4 below.Table 41 discloses modified attributes and their definition in EP_NgC and EP_N2.

[0108] Attribute remoteAddress, which includes an IP address of the remote AMF / gNB, is replaced by attribute remoteAddressList, which is a list, where each list element includes a timeWindow (start and end time when this association is valid), and IP address of the remote AMF / gNB.

[0109] The sequence diagram for setup of the batch configuration in advance, and the results of the batch configuration, is shown below (the operations, for example, CreateMOI and Modify MOIAttributes), are defined in 3GPP TS 28.532 V18.1.0 (2023-12).

[0110] Figure 8 illustrates sequence diagram configuration of gNB / AMF endpoint as a batch, in accordance with some embodiments of the present disclosure.

[0111] In step 0 of Figure 8, for each gNB in space, Network Management creates a number of Managed Object (MO) EP_NgC (EndPoint Next generation Core) instances for the CUCPFunction (Central Unit Control Plane Function) through NR NRM MnS (New Radio Network Resource Model Management Services). The number of EP_NgC instances shall be equal to the maximum number of simultaneous AMFs (Access and Mobility Management Functions) that the gNB will connect to during its movement in the satellite orbit.

[0112] In step 0 of Figure 8, for each AMF on ground, Network Management creates a number of Managed Object (MO) EP_N2 (EndPoint on the N2 interface) instances for the AMFFunction through 5GC NRM MnS. The number of EP_N2 instances shall be equal to the maximum number of simultaneous gNBs that the AMF will connect to.

[0113] In step 1 of Figure 8, the Network Management receives, from an external entity, a list of the associations between all the gNBs in space and the AMFs on ground over a time period (and related time windows indicating when each association is valid). These associations and time windows are calculated based on , for example, position of the ground gateways, and possibility for the AMFs to connected to these ground gateways, the expected orbit position of the space gNBs over the time period, availability of the feeder link between the ground gateways and satellites over the time period (e.g. expected unavailability due to weather condition), the operation condition of the satellite gNB, ground gateways, ground AMF, transport over the time period, etc. Observe that the Network Management can receive new associations from the external entity before the previous time period ends due to unexpected changes in the NTN system.

[0114] In step 2 of Figure 8, the Network Management sends, to each gNB in space, a batch of its associations to all AMFs during the time period by the NR NRM MnS service ModifyMOIAttributes() with the remote AddressList for all the EP_NgC instances in the gNB. The format of the remoteAddressList is defined above. All remaining batch associations from the previous modification will be discarded when the new modification is received.

[0115] In step 3 of Figure 8, the Network Management sends, to each AMF on ground, a batch of its associations to all gNBs during the time period by the 5GC NRM MnS service ModifyMOIAttributes() with the remoteAddressList for all the EP_N2 in the AMFs. The format of the remoteAddressList is defined above. All remaining batch associations from the previous modification will be discarded when the new modification is received.

[0116] In step 4 of Figure 8, the actual changes of all EP_NgC associations to AMFs for all gNBs over the time period are continuously and timely executed by the gNBs according to the pre-defined time windows, and also logged and transferred back to Network Management through file data report service and / or streaming event service.

[0117] In step 5 of Figure 8, the actual changes of the all EP_N2 associations to gNB for all AMF over the time period are continuously and timely executed by the AMFs according to the pre-defined time windows, and also logged and transfer back to Network Management through file data report service and / or streaming event service.

[0118] Various embodiments which are based on the above example approach illustrated in Figure 8 are now discussed.

[0119] Embodiments related to a terrestrial network management node are initially discussed with reference to Figure 13, which illustrates a flowchart of operations performed by the terrestrial network management node in accordance with some embodiments.

[0120] First, various embodiments are directed to a method performed by a terrestrial network management node for managing base stations in satellites. The method includes obtaining 1300 a list of associations between base stations in satellites and access mobility functions on ground and related time windows indicating when the associations in the list are valid. The method includes, for each of the base stations in satellites, sending 1302 to the base station a batch of the associations of the base station to the access mobility functions and related time windows indicating when the associations in the batch are valid. The method includes, for each of the access mobility functions, sending 1304 to the access mobility function a batch of the associations of the access mobility function to the base stations in satellites and related time windows indicating when the associations in the batch are valid.

[0121] In some embodiments, the access mobility function comprises an Access and Mobility Function, AMF, or a Mobility Management Entity, MME.

[0122] In some embodiments, the base station comprises a gNodeB, gNB, or an eNodeB, eNB.

[0123] In some embodiments, the sending to the base stations in satellites the batch of the associations to the access mobility functions comprises sending a remote address list of the access mobility functions.

[0124] In some embodiments, the remote address list comprises time stamps and remote IP addresses to be used for initialization and / or release of transport to the access mobility functions.

[0125] In some embodiments, the time stamps each comprise a start time and end time when the remote address is valid.

[0126] In some embodiments, the sending to the access mobility functions the batch of the associations to the base stations in satellites comprises sending a remote address list of the base stations.

[0127] In some embodiments, the remote address list comprises time stamps and remote IP addresses to be used for initialization and / or release of transport to the base stations.

[0128] In some embodiments, the time stamps each comprise a start time and end time when the remote address is valid.

[0129] In some embodiments, the method further includes, for each of the base stations in satellites, creating a number of Managed Object, MO, EndPoint Next generation Core, EP_NgC, instances for a Central Unit Control Plane Function, CUCPFunction, through New Radio Network Resource Model Management Services, NR NRM MnS. The method also further includes receiving, from the base stations, changes to the EP_NgC instances.

[0130] In some embodiments, the number of EP_NgC instances is equal to a maximum number of simultaneous access mobility functions that the base station will connect to during satellite orbit.

[0131] In some embodiments, the method further includes, for each of access mobility functions on ground, creating a number of Managed Object, MO, EndPoint on an N2 interface, EP_N2, instances for a Central Unit Control Plane Function, CUCPFunction, through 5G Core Network Resource Model Management Services, 5GC NRM MnS. The method also further includes receiving, from the access mobility functions, changes to the EP_N2 instances.

[0132] In some embodiments, the number of EP_N2 instances is equal to a maximum number of simultaneous base stations that the access mobility function will connect to as the satellites orbit.

[0133] In some embodiments, the associations and time windows are calculated based on at least one of:• positions of ground gateways providing satellite feeder links for access mobility functions;• indication of ability for the access mobility functions to connect to the ground gateways;• expected orbit positions of the base stations in satellites during the time windows;• availability of communication feeder links between the ground gateways and the satellites during the time windows;• operation conditions of the base stations in satellites; and• available access mobility functions during the time windows.

[0134] Second, corresponding embodiments related to a base station are next discussed with reference to Figure 14, which illustrates a flowchart of operations performed by the base station in accordance with some embodiments.

[0135] Various embodiments are directed to a method performed by a base station in a satellite for communicating with access mobility functions on ground. The method includes receiving 1400 from a terrestrial network management node, a list of associations between the base station and the access mobility functions and related time windows indicating when the associations in the list are valid. The method further includes, responsive to determining that one of the time windows in the list of associations has become valid, performing 1402 communications with the access mobility function related to the time window.

[0136] In some embodiments, the method further includes sending to the terrestrial network management node indications of different time windows when the associations between the base station and the access mobility functions are valid.

[0137] In some embodiments, the indications are sent through data report service and / or a streaming event service.

[0138] In some embodiments, the method further includes, responsive to determining that one of the time windows in the list of associations has become valid, changing association of an EndPoint Next generation Core, EP_NgC, instance to the access mobility function related to the time window.

[0139] In some embodiments, the base station comprises a gNodeB, gNB, or an eNodeB, eNB.

[0140] Third, corresponding embodiments related to an access mobility function are discussed with reference to Figure 15, which illustrates a flowchart of operations performed by the access mobility function in accordance with some embodiments.

[0141] Various embodiments are directed to a method performed by an access mobility function on ground for communicating with base stations in satellites. The method includes receiving 1500 from a terrestrial network management node, a list of associations between the access mobility function and the base stations in satellites and related time windows indicating when the associations in the list are valid. The method further includes responsive to determining that one of the time windows in the list of associations has become valid, performing 1502 communications with the base station related to the time window.

[0142] In some embodiments, the method further includes sending to the terrestrial network management node indications of different time windows when the associations between the access mobility function and base stations are valid.

[0143] In some embodiments, the indications are sent through data report service and / or a streaming event service.

[0144] In some embodiments, the method further includes responsive to determining that one of the time windows in the list of associations has become valid, changing association of an EndPoint on an N2 interface, EP_N2, instance to the base station related to the time window.

[0145] In some embodiments, the access mobility function comprises an Access and Mobility Function, AMF, or a Mobility Management Entity, MME.

[0146] For NTN with transparent satellite payload, it is assumed that the sector equipment is located at the satellites, while gNB, AMF (not shown in the figure) and Network Management are located on ground according to Figure 9.

[0147] Figure 9 illustrates location of NTN functions for transparent satellite payload according to 3GPP architecture.

[0148] As explained above, the interface between functions in the ground segment and space segment is unreliable, and the relationships between the gNB and SectorEquipment are changing all the time, therefore there is a need to pre-configure the relation (association)between gNB and SectorEquipment end points as a batch in advance.

[0149] In order to realize batch configuration of the association, one possible solution is to modify NRSectorCarrier (on gNB side on ground) and SectorEquipmentFunction (on sector Equipment side in satellite) instances according to the Table 5 below.Table 5 discloses modified attributes and their definition in NRSectorCarrier.

[0150] For NRSectorCarrier on gNB side, attribute sectorEquipmentFunctionRef, which includes Distinguished Name (DN) of the remote Sector Equipment, is replaced by attribute sectorEquipmentFunctionRefList, which is a list, where each list element includes a timeWindow (start and end time when this association is valid), and DN of the remote SectorEquipment.Table 6 above discloses modified attributes and their definition in SectorEquipmentFunction.

[0151] For SectorEquipmentFunction on Sector Equipment side, attribute theNRSectorCarrierList, which includes Distinguished Name (DN) of a list of remote gNB sector carrier, is replaced by attribute theNRSectorCarrierListList, which is a list, where each list element includes a timeWindow (start and end time when this association is valid), and a list of DN of remote gNB sector carrier.

[0152] The sequence diagram for setup of the batch configuration in advance, and the results of the batch configuration are shown below in Figure 10.

[0153] Figure 10 illustrates a sequence diagram configuration of Sector Carrier / Sector Equipment function associations as a batch, in accordance with some embodiments of the present disclosure.

[0154] In step 0 of Figure 10, for each Sector Equipment in space, Network Management creates Managed Object (MO) SectorEquipmentFunction instances through Generic RAN NRM MnS.

[0155] For each gNB on ground, Network Management creates a number of Managed Object (MO) NRSectorCarrier instances for the GNBDUFunction through NR NRM MnS. The number of NRSectorCarrier instances shall be equal to the maximum number of sector Carriers that the gNB will handle.

[0156] In step 1 of Figure 10, the Network Management receives, from an external entity, a list of the associations between all the sector equipment in space and the gNBs on ground over a time period (and related time windows indicating when each association is valid). These associations and time windows are calculated based on, for example, position of the ground gateways, and possibility for the gNBs to connected to these ground gateways, the expectedorbit position of the space sector equipment over the time period, availability of the feeder link between the ground gateways and satellites over the time period (e.g. expected unavailability due to weather condition), the operation condition of the satellite sector equipment, ground gateways, ground gNB, transport over the time period, etc. Observe that the Network Management can receive new associations from the external entity before the previous time period ends due to unexpected changes in the NTN system.

[0157] In step 2 of Figure 10, the Network Management sends, to each sector equipment in space, a batch of its associations to all sector carriers in one or several specific gNBs during the time period by Generic RAN NRM MnS service ModifyMOIAttributes() with the theNRSectorCarrierListList for all the sectorEquipmentFunctions. The format of the theNRSectorCarrierListList is defined above. All remaining batch associations which are not executed will be deleted when the modification is successfully executed.

[0158] In step 3 of Figure 10, the Network Management sends, to each gNB on ground, a batch of its associations to all sector equipment in space for all sector carriers in all gNBs during the time period by NR NRM MnS service ModifyMOIAttributesQ with the sectorEquipmentFunctionRefList for all the NRSectorCarrier in the gNBs. The format of the sectorEquipmentFunctionRefList is defined above. All remaining batch associations which are not executed will be deleted when the modification is successfully executed.

[0159] In step 4 of Figure 10, the actual changes of the associations to all sector carriers in different gNBs over the time period are continuously and timely executed by the sector equipment according to the pre-defined time windows, and also logged and transferred back to Network Management through file data report service and / or streaming event service.

[0160] In step 5 of Figure 10, the actual changes of the associations to all sector equipment for all sector carriers in all gNBs over the time period are continuously and timely executed by the gNB according to the pre-defined time windows, and also logged and transferred back to Network Management through file data report service and / or streaming event service.

[0161] Various embodiments based on the above example solution illustrated in Figure 10 are now discussed.

[0162] First, embodiments related to a terrestrial network management node are discussed with reference to Figure 16, which illustrates a flowchart of operations performed by the terrestrial network management node in accordance with some embodiments.

[0163] Various embodiments are directed to a method performed by a terrestrial network management node for managing sector equipment functions of base stations in satellites. The method includes obtaining 1600 a list of associations between sector equipment in satellitesand base stations on ground and related time windows indicating when the associations in the list are valid. The method further includes for each of the sector equipment in satellites, sending 1602 to the sector equipment a batch of the associations of the sector equipment to the base stations and related time windows indicating when the associations in the batch are valid. The method also includes for each of the base stations, sending 1604 to the base station a batch of the associations of the base station to the sector equipment in satellites and related time windows indicating when the associations in the batch are valid.

[0164] In some embodiments, the sending to the sector equipment in satellites the batch of the associations to the base stations comprises sending a carrier list.

[0165] In some embodiments, the carrier list comprises time stamps and carriers for communications with the base stations.

[0166] In some embodiments, the time stamps each comprise a start time and end time when the carrier is valid.

[0167] In some embodiments, the sending to the base stations the batch of the associations to the sector equipment in satellites comprises sending a carrier list of the sector equipment.

[0168] In some embodiments, the carrier list comprises time stamps and carriers for communications with the sector equipment.

[0169] In some embodiments, the time stamps each comprise a start time and end time when the carrier is valid.

[0170] In some embodiments, the method further includes, for each of the sector equipment in satellites, creating a number of Managed Object, MO, SectorEquipmentFunction instances through Generic Radio Access Network, RAN, Network Resource Model Management Services, Generic RAN NRM MnS. The method further includes, receiving, from the sector equipment, changes to the SectorEquipmentFunction instances.

[0171] In some embodiments, the method further includes, for each of the base stations, creating a number of Managed Object, MO, NRSectorCarrier instances for a GNBDUFunction, through New Radio Network Resource Model Management Services, NR NRM MnS. The method further includes receiving, from the base stations, changes to the NRSectorCarrier instances.

[0172] In some embodiments, the number of NRSectorCarrier instances is equal to a maximum number of sector carriers the base station will use.

[0173] In some embodiments, the associations and time windows are calculated based on at least one of:• positions of ground gateways providing satellite feeder links for base stations;• indication of ability for the base stations to connect to the ground gateways;• expected orbit positions of the sector equipment in satellites during the time windows;• availability of communication feeder links between the ground gateways and the satellites during the time windows;• operation conditions of the sector equipment in satellites; and• available base stations during the time windows.

[0174] Second, embodiments related to a sector equipment in a satellite are discussed with reference to Figure 17, which illustrates a flowchart of operations performed by the sector equipment in accordance with some embodiments.

[0175] Various embodiments are directed to a method performed by a sector equipment in a satellite for communicating with base stations on ground. The method includes receiving 1700 from a terrestrial network management node, a list of associations between the sector equipment and the base stations and related time windows indicating when the associations in the list are valid. The method also includes responsive to determining that one of the time windows in the list of associations has become valid, performing 1702 communications with the base stations related to the time window.

[0176] In some embodiments, the method further includes sending to the terrestrial network management node indications of different time windows when the associations between the sector equipment and the base stations are valid.

[0177] In some embodiments, the indications are sent through data report service and / or a streaming event service.

[0178] In some embodiments, the method further includes responsive to determining that one of the time windows in the list of associations has become valid, replacing the old NRSectorCarrierList with an NRSectorCarrierListList which lists one or more NRSectorCarriers belonging to one or more base stations, with a new NRSectorCarrier List in the NRSectorCarrierListList which is a list of lists with a valid time stamp for each list.

[0179] Third, embodiments related to a base station on ground are discussed with reference to Figure 18, which illustrates a flowchart of operations performed by the base station in accordance with some embodiments.

[0180] Various embodiments are directed to a method performed by a base station on ground for communicating with sector equipment in satellites. The method includes receiving 1800 from a terrestrial network management node, a list of associations between the base station and the sector equipment in satellites and related time windows indicating when theassociations in the list are valid. The method also includes responsive to determining that one of the time windows in the list of associations has become valid, performing 1802 communications with the sector equipment related to the time window.

[0181] In some embodiments, the method further includes sending to the terrestrial network management node indications of different time windows when the associations between the base station and sector equipment are valid.

[0182] In some embodiments, the indications are sent through data report service and / or a streaming event service.

[0183] In some embodiments, the method further includes responsive to determining that one of the time windows in the list of associations has become valid, replacing an old sectorEquipmentFunctionRef in sectorEquipmentFunctionRefList with a new sectorEquipmentFunctionRef in the sectorEquipmentFunctionRefList where the timestamp on the new sectorEquipmentFunctionRef is valid, for each sector carrier in a base station.

[0184] In some embodiments, the base station comprises a gNodeB, gNB, or an eNodeB, eNB. The sector carrier may, for example, be a NRSectorCarrier or a EUtranGenericCell (see 3GPP TS28.662 V17.0.0, Fig 4.2.1.1).

[0185] Open Radio Access Network (O-RAN) implementation is now discussed herein.

[0186] For NTN with transparent satellite payload, it is assumed that the O-RU (Open RAN Radio Unit) is located at the satellites, while O-DU (Open RAN Distributed Unit) and Network Management are located on ground according to figure below.

[0187] Figure 11 illustrates location of NTN functions for transparent satellite payload according to O-RAN architecture.

[0188] As mentioned in the above description, the interface between functions on ground segment and space segment are unreliable, and the relationship between the O-DU and O-RU are changing all the time, there is a need to configure the O-RAN LLS M-plane relation between O-RU and O-DU end points as a batch in advance.

[0189] In order to realize batch configuration of the association, one possible solution is to modify the YANG model of O-RAN LLS M-plane interface (o-ran-mplane-int) in O-RU, such as shown in the listing below.

[0190] For each O-RAN client in the O-LLS M-plane (client-info discovered through DHCP, and configured-client-info which is manually assigned or provisioned), two additional attributes, start-time and end-time, are added. These two attributes represent start time and end time when the M-plane association to the O-RU client is valid.

[0191] The sequence diagram for the DHCP discovery and manual NETCONF configuration of o-ran-mplane-int is not changed relative to what is described in O- RAN.WG4.MP.0-R003-vl4.00 chapter 6.2, except the start-time and end-time shall now be included in the O-RU client information in accordance with some embodiments. The setup and release of the M-plane, marked as “Call Home to O-RU Controllers”, is changed according toFigure 12.

[0192] Figure 12 illustrates a modified establishing of connectivity to O-RU Controller(s), in accordance with some embodiments of the present disclosure.

[0193] In prior known approaches, the O-RU Controller (s) connections can be established immediately after reception of the O-RU Controller information. According to some present embodiments, O-RU should now establish the O-RU Controller connectivity first when the start-time requirement is fulfilled. Also, the O-RU has the responsibility to disconnect the M- plane connection to O-RU controller when the stop-time requirement is fulfilled.

[0194] Various embodiments based on the example solution illustrated in Figure 12 are now discussed with reference to Figure 19, which illustrates a flowchart of operations performed by the terrestrial network management node in accordance with some embodiments.

[0195] Some embodiments are directed to a method performed by a terrestrial network management node for managing O-RU functions in satellites communicating with an O-DU function of base stations on ground. The method includes obtaining 1900 a list of associations between O-RUs in satellites and the O-DU function of the base stations on ground and related time windows indicating when the associations in the list are valid. The method includes, for each of the O-RUs in satellites, sending 1902 to the O-RU indications of a batch of the associations of the O-RU to the O-DU function of the base stations and related time windows indicating when the associations in the batch are valid. The method includes, for each of the O-DU function of the base stations on ground, sending 1904 to the O-DU function indications of a batch of the associations of the O-DU function to the O-RUs and related time windows indicating when the associations in the batch are valid.

[0196] In a further embodiment, the sending to the O-RUs in satellites indications of the batch of the associations of the O-RU to the O-DU function of the base stations includes sending a carrier list. The carrier list may include time stamps and carriers for communications with the O-DU function of the base stations.

[0197] In a further embodiment, the time stamps each comprise a start time and end time when the association of the O-RU to the O-DU function and the carrier is valid.

[0198] In a further embodiment, the sending to the O-DU function of the base stations indications of the batch of the associations to the O-RUs in satellites includes sending a carrier list of the O-RUs. The carrier list may include time stamps and carriers for communications with the O-RUs. The time stamps each may include a start time and end time when the carrier is valid.

[0199] In a further embodiment, the method further includes, for each of the O-RUs in satellites, creating a number of Managed Object, MO, SectorEquipmentFunction instances through YANG model of O-RAN LLS interfaces. The method further includes receiving, from the O-RUs, changes to the SectorEquipmentFunction instances.

[0200] In a further embodiment, the method further includes, for each of the O-DU functions of the base stations on ground, creating a number of Managed Object, MO, NRSectorCarrier instances for a GNBDUFunction, through New Radio Network Resource Model Management Services, NR NRM MnS. The method further includes receiving, from the O-DU functions, changes to the NRSectorCarrier instances.

[0201] In a further embodiment, the number of NRSectorCarrier instances is equal to a maximum number of sector carriers the O-DU function will use.

[0202] In a further embodiment, the associations and time windows are calculated based on at least one of:• positions of ground gateways providing satellite feeder links for O-DU functions;• indication of ability for the O-DU functions to connect to the ground gateways;• expected orbit positions of the O-RUs in satellites during the time windows;• availability of communication feeder links between the ground gateways and the satellites during the time windows;• operation conditions of the O-RUs in satellites; and• available O-DU functions during the time windows.EMBODIMENTS DIRECTED TO TIMING ADVANCE CONFIGURATION IN BATCH FOR NTN SYSTEMS:Group Al Embodiments1. A method performed by a terrestrial network management node for managing base stations in satellites, the method comprising: obtaining (1300) a list of associations between base stations in satellites and access mobility functions on ground and related time windows indicating when the associations in the list are valid; for each of the base stations in satellites, sending (1302) to the base station a batch of the associations of the base station to the access mobility functions and related time windows indicating when the associations in the batch are valid; and for each of the access mobility functions, sending (1304) to the access mobility function a batch of the associations of the access mobility function to the base stations in satellites and related time windows indicating when the associations in the batch are valid.2. The method of any of the Group Al Embodiments, wherein the access mobility functioncomprises an Access and Mobility Function, AMF, or a Mobility Management Entity, MME.3. The method of any of the Group Al Embodiments, wherein the base station comprises a gNodeB, gNB, or an eNodeB, eNB.4. The method of any of the Group Al Embodiments, wherein the sending to the base stations in satellites the batch of the associations to the access mobility functions comprises sending a remote address list of the access mobility functions.5. The method of Embodiment 4, wherein the remote address list comprises time stamps and remote IP addresses to be used for initialization and / or release of transport to the access mobility functions.6. The method of Embodiment 5, wherein the time stamps each comprise a start time and end time when the remote address is valid.7. The method of any of the Group Al Embodiments, wherein the sending to the access mobility functions the batch of the associations to the base stations in satellites comprises sending a remote address list of the base stations.8. The method of Embodiment 7, wherein the remote address list comprises time stamps and remote IP addresses to be used for initialization and / or release of transport to the base stations.9. The method of Embodiment 8, wherein the time stamps each comprise a start time and end time when the remote address is valid.10. The method of any of the Group Al Embodiments, further comprising: for each of the base stations in satellites, creating a number of Managed Object, MO, EndPoint Next generation Core, EP_NgC, instances for a Central Unit Control Plane Function, CUCPFunction, through New Radio Network Resource Model Management Services, NR NRM MnS; receiving, from the base stations, changes to the EP_NgC instances.11. The method of Embodiment 10, wherein the number of EP_NgC instances is equal to a maximum number of simultaneous access mobility functions that the base station will connect to during satellite orbit.12. The method of any of the Group Al Embodiments, further comprising: for each of access mobility functions on ground, creating a number of Managed Object, MO, EndPoint on an N2 interface, EP_N2, instances for a Central Unit Control Plane Function, CUCPFunction, through 5G Core Network Resource Model Management Services, 5GC NRM MnS; receiving, from the access mobility functions, changes to the EP_N2 instances.13. The method of Embodiment 12, wherein the number of EP_N2 instances is equal to a maximum number of simultaneous base stations that the access mobility function will connect to as the satellites orbit.14. The method of any of the Group Al Embodiments, wherein the associations and time windows are calculated based on at least one of: positions of ground gateways providing satellite feeder links for access mobility functions; indication of ability for the access mobility functions to connect to the ground gateways; expected orbit positions of the base stations in satellites during the time windows; availability of communication feeder links between the ground gateways and the satellites during the time windows; operation conditions of the base stations in satellites; and available access mobility functions during the time windows.Group A2 Embodiments1. A method performed by a base station in a satellite for communicating with access mobility functions on ground, the method comprising: receiving (1400) from a terrestrial network management node, a list of associations between the base station and the access mobility functions and related time windows indicating when the associations in the list are valid; and responsive to determining that one of the time windows in the list of associations has become valid, performing (1402) communications with the access mobility function related tothe time window.2. The method of any of the Group A2 Embodiments, further comprising: sending to the terrestrial network management node indications of different time windows when the associations between the base station and the access mobility functions are valid.3. The method of the Embodiment 2, wherein the indications are sent through data report service and / or a streaming event service.4. The method of any of the Group A2 Embodiments, further comprising: responsive to determining that one of the time windows in the list of associations has become valid, changing association of an EndPoint Next generation Core, EP_NgC, instance to the access mobility function related to the time window.5. The method of any of the Group A2 Embodiments, wherein the base station comprises a gNodeB, gNB, or an eNodeB, eNB.Group A3 Embodiments1. A method performed by an access mobility function on ground for communicating with base stations in satellites, the method comprising: receiving (1500) from a terrestrial network management node, a list of associations between the access mobility function and the base stations in satellites and related time windows indicating when the associations in the list are valid; and responsive to determining that one of the time windows in the list of associations has become valid, performing (1502) communications with the base station related to the time window.2. The method of any of the Group A3 Embodiments, further comprising: sending to the terrestrial network management node indications of different time windows when the associations between the access mobility function and base stations are valid.3. The method of the Embodiment 2, wherein the indications are sent through data report service and / or a streaming event service.4. The method of any of the Group A3 Embodiments, further comprising: responsive to determining that one of the time windows in the list of associations has become valid, changing association of an EndPoint on an N2 interface, EP_N2, instance to the base station related to the time window.5. The method of any of the Group A3 Embodiments, wherein the access mobility function comprises an Access and Mobility Function, AMF, or a Mobility Management Entity, MME.Group B 1 Embodiments1. A method performed by a terrestrial network management node for managing sector equipment functions of base stations in satellites, the method comprising: obtaining (1600) a list of associations between sector equipment in satellites and base stations on ground and related time windows indicating when the associations in the list are valid; for each of the sector equipment in satellites, sending (1602) to the sector equipment a batch of the associations of the sector equipment to the base stations and related time windows indicating when the associations in the batch are valid; and for each of the base stations, sending (1604) to the base station a batch of the associations of the base station to the sector equipment in satellites and related time windows indicating when the associations in the batch are valid.2. The method of any of the Group Bl Embodiments, wherein the sending to the sector equipment in satellites the batch of the associations to the base stations comprises sending a carrier list.3. The method of Embodiment 2, wherein the carrier list comprises time stamps and carriers for communications with the base stations.4. The method of Embodiment 3, wherein the time stamps each comprise a start time and end time when the carrier is valid.5. The method of any of the Group Bl Embodiments, wherein the sending to the base stations the batch of the associations to the sector equipment in satellites comprises sending a carrier list of the sector equipment.6. The method of Embodiment 5, wherein the carrier list comprises time stamps and carriers for communications with the sector equipment.7. The method of Embodiment 6, wherein the time stamps each comprise a start time and end time when the carrier is valid.8. The method of any of the Group Bl Embodiments, further comprising: for each of the sector equipment in satellites, creating a number of Managed Object, MO, SectorEquipmentFunction instances through Generic Radio Access Network, RAN, Network Resource Model Management Services, Generic RAN NRM MnS; receiving, from the sector equipment, changes to the SectorEquipmentFunction instances.9. The method of any of the Group Bl Embodiments, further comprising: for each of the base stations, creating a number of Managed Object, MO, NRSectorCarrier instances for a GNBDUFunction, through New Radio Network Resource Model Management Services, NR NRM MnS; receiving, from the base stations, changes to the NRSectorCarrier instances.10. The method of Embodiment 9, wherein the number of NRSectorCarrier instances is equal to a maximum number of sector carriers the base station will use.11. The method of any of the Group Bl Embodiments, wherein the associations and time windows are calculated based on at least one of: positions of ground gateways providing satellite feeder links for base stations; indication of ability for the base stations to connect to the ground gateways; expected orbit positions of the sector equipment in satellites during the time windows; availability of communication feeder links between the ground gateways and the satellites during the time windows; operation conditions of the sector equipment in satellites; andavailable base stations during the time windows.Group B2 Embodiments1. A method performed by a sector equipment in a satellite for communicating with base stations on ground, the method comprising: receiving (1700) from a terrestrial network management node, a list of associations between the sector equipment and the base stations and related time windows indicating when the associations in the list are valid; and responsive to determining that one of the time windows in the list of associations has become valid, performing (1702) communications with the base stations related to the time window.2. The method of any of the Group B2 Embodiments, further comprising: sending to the terrestrial network management node indications different time windows when the associations between the sector equipment and the base stations are valid.3. The method of the Group B2 Embodiment 2, wherein the indications are sent through data report service and / or a streaming event service.4. The method of any of the Group B2 Embodiments, further comprising: responsive to determining that one of the time windows in the list of associations has become valid, replacing an old NRSectorCarrierList with an NRSectorCarrierListList which lists one or more NRSectorCarriers belonging to one or more base stations, with a new NRSectorCarrier List in the NRSectorCarrierListList which is a list of lists with a valid time stamp for each list.Group B3 Embodiments1. A method performed by a base station on ground for communicating with sector equipment in satellites, the method comprising: receiving (1800) from a terrestrial network management node, a list of associations between the base station and the sector equipment in satellites and related time windows indicating when the associations in the list are valid; and responsive to determining that one of the time windows in the list of associations has become valid, performing (1802) communications with the sector equipment related to the timewindow.2. The method of any of the Group B3 Embodiments, further comprising: sending to the terrestrial network management node indications of different time windows when the associations between the base station and sector equipment are valid.3. The method of the Embodiment 2, wherein the indications are sent through data report service and / or a streaming event service.4. The method of any of the Group B3 Embodiments, further comprising: responsive to determining that one of the time windows in the list of associations has become valid, replacing an old sectorEquipmentFunctionRef in sectorEquipmentFunctionRefList with a new sectorEquipmentFunctionRef in the sectorEquipmentFunctionRefList where the timestamp on the new sectorEquipmentFunctionRef is valid, for each sector carrier in a base station.5. The method of any of the Group B3 Embodiments, wherein the base station comprises a gNodeB, gNB, or an eNodeB, eNB.Group C Embodiments1. A method performed by a terrestrial network management node for managing O-RU functions in satellites communicating with O-DU functions of base stations on ground, the method comprising: obtaining (1900) a list of associations between O-RUs in satellites and the O-DU functions of the base stations on ground and related time windows indicating when the associations in the list are valid; for each of the O-RUs in satellites, sending (1902) to the O-RU indications of a batch of the associations of the O-RU to the O-DU functions of the base stations and related time windows indicating when the associations in the batch are valid; and for each of the O-DU function of the base station on ground, sending (1904) to the O- DU function indications of a batch of the associations of the O-DU function to the O-RUs and related time windows indicating when the associations in the batch are valid.2. The method of Embodiment 1, wherein the sending to the O-RUs in satellites indicationsof the batch of the associations of the O-RU to the O-DU functions of the base stations comprises sending a carrier list.3. The method of Embodiment 2, wherein the carrier list comprises time stamps and carriers for communications with the O-DU functions of the base stations.4. The method of Embodiment 3, wherein the time stamps each comprise a start time and end time when the carrier is valid.5. The method of any of the Group C Embodiments, wherein the sending to the O-DU functions of the base stations indications of the batch of the associations to the O-RUs in satellites comprises sending a carrier list of the O-RUs.6. The method of Embodiment 5, wherein the carrier list comprises time stamps and carriers for communications with the O-RUs.7. The method of Embodiment 6, wherein the time stamps each comprise a start time and end time when the association of the O-RU to the O-DU function and the carrier is valid.8. The method of any of the Group C Embodiments, further comprising: for each of the O-RUs in satellites, creating a number of Managed Object, MO, SectorEquipmentFunction instances through YANG model of O-RAN LLS interfaces; receiving, from the O-RUs, changes to the SectorEquipmentFunction instances.9. The method of any of the Group C Embodiments, further comprising: for each of the O-DU functions on ground, creating a number of Managed Object, MO, NRSectorCarrier instances for a GNBDUFunction, through New Radio Network Resource Model Management Services, NR NRM MnS; receiving, from the O-DU function, changes to the NRSectorCarrier instances.10. The method of Embodiment 9, wherein the number of NRSectorCarrier instances is equal to a maximum number of sector carriers the O-DU function will use.11. The method of any of the Group C Embodiments, wherein the associations and timewindows are calculated based on at least one of: positions of ground gateways providing satellite feeder links for O-DU functions; indication of ability for the O-DU functions to connect to the ground gateways; expected orbit positions of the O-RUs in satellites during the time windows; availability of communication feeder links between the ground gateways and the satellites during the time windows; operation conditions of the O-RUs in satellites; and available O-DU functions during the time windows.

[0203] Time Advance Cell Configuration for Regenerative NTN System:

[0204] In case the orbit of the space segment entities, e.g. LEO and MEO satellites, can be sufficiently estimated in advance, the corresponding earth surface coverage over future time periods can be pre-calculated. The Management system can therefore pre-calculate the future time associations between the NTN cell coverage and the gNB in space.

[0205] These future pre-calculated associations can then be converted to a list of configurations with time stamps (more precisely: time windows), and transmitted to the Managed element as a batch, with the time stamp included for each configuration entry.

[0206] Figure 25 illustrates a flowchart of operations performed by the terrestrial network management node in accordance with some embodiments.

[0207] Various embodiments are directed to operations performed by a terrestrial network management node for managing base stations in satellites. Operations include obtaining 2500 future time associations between base stations in satellites and Non-Terrestrial Network cell coverage on ground. Operations also include, based on the future time associations, determining 2502 a list of NTN cell configurations with related time windows indicating when the associations in the list of NTN cell configurations are valid. Operations also include sending 2504 a batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite.

[0208] In some of the terrestrial network management node embodiments, the satellites are non-geostationary orbit satellites.

[0209] Figure 26 illustrates a flowchart of operations performed by the base station in a satellite in accordance with some embodiments.

[0210] Various embodiments are directed to operations performed by a base station in a satellite for serving ground fixed Non-Terrestrial Network cells or quasi-ground fixed. NonTerrestrial Network cells. Operations include receiving 2600 from a terrestrial networkmanagement node, a list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid. Operations also include, responsive to determining that one of the time windows has become valid, performing 2602 communications using the NTN cell configuration in the list related with the valid time window.

[0211] In some of the base station in a satellite embodiments the satellite is a non- geostationary orbit satellite.

[0212] In case there is a need of change of the pre-calculated associations due to, e.g., alarm or performance optimization of the network, some embodiments are directed to a procedure for changing / deleting existing configuration entries.

[0213] Some embodiments of the present disclosure are thereby directed to extending the configuration of managed element in a batch with a list of pre-configurations and related time stamps (time windows), and to procedures for potential update / cancellation of the existing preconfiguration.

[0214] A potential advantage of these and other embodiments disclosure herein is that by performing batch configuration with a time stamp, the problem with interface resiliency between the gNBs in space (Managed Elements) and the management system can then be mitigated because the configurations can be sent ahead in-time with relaxed real time requirement.

[0215] Figure 21 illustrates a block diagram of a 3GPP management architecture which can be configured to operate in accordance with present embodiments of the disclosure. Referring to Figure 21, the gNB is managed by the NR NRM MnS producer and may be represented by the GNBDUFunction, GNBCUCPFunction and GNBCUUPFunction IGCs in TS 28.541, in different configurations dependent upon the deployment options.

[0216] For NTN with regenerative gNB processed satellite payload, it is assumed that the gNB are located at the satellites, while Network Management are located on ground. Figure 22 illustrates locations of NTN functions for performing regenerative gNB processing of satellite payload.

[0217] As explained above, the interface between functions in the ground segment and space segment are unreliable, and the relationship between the gNB and the ground fixed NTN cells which the gNB is serving are changing all the time, therefore there is a need to preconfigure the relation (association) between gNB and NTN Cells as a batch in advance.

[0218] SOEUTION 1 ACCORDING TO SOME EMBODIMENTS:

[0219] In order to realize batch configuration of the association, one solution is to create maximum number of NRCellCU instances and NRCellDU instances that the satellite gNB canhandle simultaneously at the same time, and change the configuration of the NRCellCU and NRCellDU instance according to a list, where each list entry includes (or at least some list entries include) information on time window when it is valid, and the valid configuration attribute for serving the ground fixed NTN Cell during the time window.

[0220] The modified NRCellCU can be described according to the table below, in accordance with some embodiments. All current attributes in NRCellCU have been replaced by one single attribute NRCellCUInfoList, which is a list with entries that include a timeWindow, and NRCellCUInfo with the same attributes as the current attributes in NRCellCU.

[0221] The table below defines the NRCellCUInfo (with some attributes as NRCellCU according to existing standards).

[0222] The modified NRCellDU can be defined according to the following table. All current attributes in NRCellDU have been replaced by one single attribute NRCellDUInfoList, which is a list with entries that include a timeWindow, and NRCellDUInfo, which can have the same attributes as the current attributes in NRCellDU.

[0223] Definition of NRCellDUInfo is provided by the following table, where some attributes can be according to NRCellDU in existing standards.

[0224] A sequence diagram for setup of the batch configuration in advance, and the results of the batch configuration, are shown in Figure 23 in accordance with some embodiments. Some operations, e.g. CreateMOI and ModifyMOI Attributes, can be performed according to 3GPP TS 28.532 [7],

[0225] The numbered steps in Figure 23 are explained below:

[0226] Step 0: For each gNB in space, Network Management creates a number of Managed Object (MO) NRCellCU instances for the GNBCUCPFunction, and a number of Managed Object (MO) NRCellDU instances for the GNBDUFunction through NR NRM MnS The number of NRCellCU and NRCellDU instances shall be at least equal to (e.g., no less than) the max number of ground fixed NTN Cell that the gNB can serve simultaneously, in accordance with some embodiments.

[0227] In some of the terrestrial network management node embodiments, the determining a list of NTN cell configurations with related time windows indicating when the future timeassociations in the list of NTN cell configurations are valid includes creating a number of NRCellCU instances and NRCellDU instances determined based on a maximum number of NRCellCU instances and NRCellDU instances that the base stations in satellites can handle simultaneously at the same time. The determining a list of NTN cell configurations also includes changing configuration of the NRCellCU instances and NRCellDU instances according to the list of NTN cell configurations.

[0228] In some of these embodiments, each NTN cell configuration in the list of NTN cell configurations comprises information indicating the time window when the associated NTN cell configuration is valid and comprises a valid configuration attribute for serving a ground fixed NTN cell coverage during the time window.

[0229] In some other of these embodiments, creating the number of NRCellCU instances and NRCellDU instances further includes creating the number of NRCellCU instances and NRCellDU instances to be no less than a maximum number of ground fixed cells and / or quasi ground fixed cells that the base station in one of the satellites can serve simultaneously.

[0230] In some other of these embodiments, the determining the list of NTN cell configurations with related time windows indicating when the future time associations in the list of NTN cell configurations are valid includes creating a number of NRCellCU instances with configurations and NRCellDU instances with configurations determined to be equal to a maximum number of ground fixed cells and / or quasi-ground fixed cells that the base stations in satellites can serve. The determining the list of NTN cell configurations includes indicating which of the NRCellCU instances and NRCellDU instances are valid in different time periods according to the list of NTN cell configurations.

[0231] In some of the base station in a satellite embodiments, the receiving from the terrestrial network management node, the list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid includes receiving the list of NTN cell configurations with an indication in which time periods NRCellCU instances are valid.

[0232] Step 1: Network Management receives, from an external entity, a list of the associations between all the gNBs in space and the ground fixed NTN cells over a time period (and related time windows indicating when each association is valid). These associations and time windows may be calculated based on any one or more of: minimum elevation angle between the ground fixed NTN cell and space gNB, the expected orbit position of the space gNBs over the time period, availability of the feeder link between the ground gateways and satellites over the time period (e.g., expected unavailability due to weather condition), theoperation condition of the satellite gNB, ground gateways, ground AMF, transport over the time period, etc. It is noted that the Network Management can receive new associations from the external entity before the previous time period ends due to unexpected changes in the NTN system.

[0233] Step 2: Network Management sends, to each gNB in space, a batch of its associations to all ground fixed NTN cells (NTN cell configuration for the gNB-CU-CP part) during the time period by the NR NRM MnS service ModifyMOIAttributes() with the NRCellCUInfoList for all the NRCellCUInfo entries in the gNB. All remaining batch associations from the previous modification may be discarded when the new modification is received.

[0234] In some of the terrestrial network management node embodiments, the sending a batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite includes sending the batch of the list of NTN cell configurations with related time windows to the base station in a satellite through an NR NRM MnS service ModifyMOIAttributes() function.

[0235] In some of these embodiments, the obtaining future time associations between base stations in satellites and NTN cell coverage on ground includes determining a future time association between a base station in a satellite and a NTN cell coverage on ground, based on any one or more of: minimum elevation angle between a base station on ground and the base station in the satellite; an expected orbit position of the base station in the satellite over the time window; availability of a feeder link between the base station on ground and the base station in the satellite over the time window; and an operation condition of at least one of the base station in the satellite, ground gateways, ground Access Mobility Function, and transport over the time period.

[0236] In some of the base station in a satellite embodiments, the receiving from the terrestrial network management node, the list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid includes receiving the list of NTN cell configurations with related time windows from a terrestrial network management node through an NR NRM MnS service ModifyMOIAttributesQ function.

[0237] Step 3: Network Management sends, to each gNB in space, a batch of its associations to all ground fixed NTN cells (NTN cell configuration for the gNB -DU part) during the time period by the NR NRM MnS service ModifyMOIAttributes() with the NRCellDUInfoList for all the NRCellDUInfo entries in the gNB. All remaining batchassociations from the previous modification may be discarded when the new modification is received.

[0238] Step 4: The actual changes of all ground fixed NTN cells (gNB-CU-CP part) associations for all gNBs over the time period are repetitively (e.g., continuously and timely) executed by the gNBs according to the pre-defined time windows, and also logged and transferred back to Network Management through file data report service and / or streaming event service.

[0239] In some of the terrestrial network management node embodiments, operations further include receiving from the base station in the at least one satellite a log of changes to NTN cell configurations that have been performed.

[0240] In some of these embodiments, the log of changes indicates NTN cell configuration changes performed for gNB-CU-CP.

[0241] In some of the base station in a satellite embodiments, operations further include sending a log of changes that indicates NTN cell configuration changes performed for gNB- CU-CP.

[0242] Step 5: The actual changes of all ground fixed NTN cells (gNB-DU part) associations for all gNBs over the time period are repetitively (e.g., continuously and timely) executed by the gNBs according to the pre-defined time windows, and also logged and transferred back to Network Management through file data report service and / or streaming event service.

[0243] In some of the terrestrial network management node embodiments, the log of changes indicates NTN cell configuration changes performed for gNB-DU.

[0244] In some of the base station in a satellite embodiments, operations further include sending a log of changes that indicates NTN cell configuration changes performed for gNB- DU.

[0245] SOLUTION 2 ACCORDING TO SOME EMBODIMENTS:

[0246] For realizing batch configuration of the association, another solution in accordance with some embodiments is to create and configure NRCellCU instances and NRCellDU instances for all the ground fix NTN cells that the satellite gNB can serve, and provide validity of the NRCellCU and NRCellDU instances by a new attribute NRCellValidTimeWindowList, where each list entry (or at least some list entries) includes time window which indicates if the NRCellCU / NRCellDU instance is valid.

[0247] The modified NRCellCU is shown in the table below. The underlined and italics marked attributes are the changes done compared to the definition described above according to the standards.

[0248] The modified NRCellDU is shown in the table below. The underlined and italics marked attributes are the changes done compared to the definition described above according to the standards.

[0249] The definition of the additional attribute NRCellValidTimeWindowList in the modified NRCellCU and NRCellDU is shown in the table below.

[0250] Figure 24 illustrates a sequence diagram of operations performed according to some embodiments of solution 2.

[0251] The numbered steps in Figure 24 are explained below:

[0252] Step 0: For each gNB in space, Network Management creates and configures a number of Managed Object (MO) NRCellCU instances for the GNBCUCPFunction, and a number of Managed Object (MO) NRCellDU instances for the GNBDUFunction through NR NRM MnS. The number of NRCellCU and NRCellDU instances can be set to be equal to the number of all the ground fixed NTN Cells that the gNB can serve.

[0253] Step 1: Network Management receives, from an external entity, a list of the associations between all the gNBs in space and the ground fixed NTN cells over a time period (and related time windows indicating when each association is valid). These associations and time windows may be calculated based on any one or more of: minimum elevation angle between the ground fixed NTN cell and space gNB, the expected orbit position of the space gNBs over the time period, availability of the feeder link between the ground gateways and satellites over the time period (e.g. expected unavailability due to weather condition), the operation condition of the satellite gNB, ground gateways, ground AMF, transport over the time period, etc. It is noted that the Network Management can receive new associations from the external entity before the previous time period ends due to unexpected changes in the NTN system.

[0254] Step 2: Network Management sends, to all NRCellCU instance in each gNB in space, a list indicating in which time periods the NRCellCU (configured to associated to a ground fixed NTN Cell gNB-CU-CP part) instance was valid, by the NR NRM MnS service ModifyMOIAttributes() with the NRCellValidTimeWindowList for all the TimeWindow entries in the gNB. All remaining timeWindow list from the previous modification will be discarded when the new modification is received.

[0255] Step 3: Network Management sends, to all NRCellDU instance in each gNB in space, a list indicating in which time periods the NRCellDU (configured to associated to aground fixed NTN Cell gNB-DU part) instance was valid by the NR NRM MnS service ModifyMOIAttributes() with the NRCellValidTimeWindowList for all the TimeWindow entries in the gNB. All remaining timeWindow list from the previous modification will be discarded when the new modification is received.

[0256] In some of the terrestrial network management node embodiments, the sending the batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite includes sending the batch of the list of NTN cell configurations with an indication in which time periods NRCellCU instances are valid for the base station.

[0257] In some of these embodiments, the sending the batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite includes sending the batch of the list of NTN cell configurations with an indication in which time periods NRCellDU instances are valid.

[0258] In some of these embodiments, the sending of the batch of the list of NTN cell configurations to the base station in at least one satellite is by an NR NRM MnS service ModifyMOIAttributes() function with a NRCellValidTimeWindowList for TimeWindow entries in the base station in the at least one satellite.

[0259] In some of the base station in a satellite embodiments, the receiving from the terrestrial network management node, the list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid includes receiving the list of NTN cell configurations with an indication in which time periods NRCellDU instances are valid.

[0260] Step 4: The actual changes of all NRCellCU validity for all gNBs over the time period are repetitively (e.g., continuously and timely) executed by the gNBs according to the pre-defined time windows, and also logged and transferred back to Network Management through file data report service and / or streaming event service.

[0261] Step 5: The actual changes of all NRCellDU validity for all gNBs over the time period are repetitively (e.g., continuously and timely) executed by the gNBs according to the pre-defined time windows, and also logged and transferred back to Network Management through file data report service and / or streaming event service.

[0262] Example Communication System Configured to Use These Embodiments:

[0263] Figure 27 shows an example of a communication system QQ100 in accordance with some embodiments.

[0264] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network(RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQl lOa and QQllOb (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non- 3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0265] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0266] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves,and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0267] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0268] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more host computing systems, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDE), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0269] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditionsdetected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0270] As a whole, the communication system QQ100 of Figure 27 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0271] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0272] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN- DC).

[0273] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be acontroller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0274] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQl lOb. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0275] Figure 28 shows a UE QQ200 in accordance with some embodiments. The UE QQ200 presents additional details of some embodiments of the UE QQ112 of Figure 27. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wirelesscameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0276] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0277] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 28. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0278] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0279] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch- sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0280] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0281] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0282] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive,external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0283] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0284] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking(SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0285] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0286] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0287] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure 28.

[0288] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results ofsuch monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0289] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0290] Figure 29 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0291] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0292] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), basetransceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0293] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0294] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0295] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceivercircuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0296] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device -readable and / or computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0297] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0298] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0299] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0300] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0301] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of abattery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0302] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 29 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300. In some embodiments providing a core network node, such as core network node 108 of FIG. QQ1, some components, such as the radio front-end circuitry QQ318 and the RF transceiver circuitry QQ312 may be omitted.

[0303] Figure 30 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 27, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0304] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 28 and 29, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0305] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FEAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets,desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0306] Figure 31 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0307] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0308] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0309] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0310] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0311] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0312] Figure 32 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 27 and / or UE QQ200 of Figure 28), network node (such as network node QQl lOa of Figure 27 and / or network node QQ300of Figure 29), and host (such as host QQ116 of Figure 27 and / or host QQ400 of Figure 30) discussed in the preceding paragraphs will now be described with reference to Figure 32.

[0313] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0314] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 27) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0315] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE’s client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE’s client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0316] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0317] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0318] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0319] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment.

[0320] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, thehost QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0321] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc. ; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0322] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may beperformed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0323] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.EMBODIMENTS DIRECTED TO TIMING ADVANCE CELL CONFIGURATION FOR REGENERATIVE NTN SYSTEM:Group Cl Embodiments1. A method performed by a terrestrial network management node for managing base stations in satellites, the method comprising: obtaining (2500) future time associations between base stations in satellites and NonTerrestrial Network, NTN, cell coverage on ground;based on the future time associations, determining (2502) a list of NTN cell configurations with related time windows indicating when the associations in the list of NTN cell configurations are valid; sending (2504) a batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite.2. The method of any of the Group Cl Embodiments, wherein the satellites are non- geostationary orbit satellites.3. The method of any of the Group Cl Embodiments, wherein determining a list of NTN cell configurations with related time windows indicating when the future time associations in the list of NTN cell configurations are valid, comprises: creating a number of NRCellCU instances and NRCellDU instances determined based on a maximum number of NRCellCU instances and NRCellDU instances that the base stations in satellites can handle simultaneously at the same time; and changing configuration of the NRCellCU instances and NRCellDU instances according to the list of NTN cell configurations.4. The method of Embodiment 3, wherein each NTN cell configuration in the list of NTN cell configurations comprises information indicating the time window when the associated NTN cell configuration is valid and comprises a valid configuration attribute for serving a ground fixed NTN cell coverage during the time window.5. The method of Embodiment 3, wherein creating the number of NRCellCU instances and NRCellDU instances further comprises: creating the number of NRCellCU instances and NRCellDU instances to be no less than a maximum number of ground fixed cells and / or quasi ground fixed cells that the base station in one of the satellites can serve simultaneously.6. The method of any of the Group Cl Embodiments, wherein sending a batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite, comprises: sending the batch of the list of NTN cell configurations with related time windows to the base station in a satellite through an NR NRM MnS service ModifyMOIAttributes() function.7. The method of any of the Group Cl Embodiments, wherein obtaining future time associations between base stations in satellites and NTN cell coverage on ground, comprises: determining a future time association between a base station in a satellite and a NTN cell coverage on ground, based on any one or more of: minimum elevation angle between a base station on ground and the base station in the satellite; an expected orbit position of the base station in the satellite over the time window; availability of a feeder link between the base station on ground and the base station in the satellite over the time window; and an operation condition of at least one of the base station in the satellite, ground gateways, ground Access Mobility Function, and transport over the time period.8. The method of any of the Group Cl Embodiments, the method further comprising: receiving from the base station in the at least one satellite a log of changes to NTN cell configurations that have been performed.9. The method of Embodiment 8, wherein the log of changes indicates NTN cell configuration changes performed for gNB-CU-CP.10. The method of any of Embodiments 8 to 9, wherein the log of changes indicates NTN cell configuration changes performed for gNB-DU.11. The method of any of the Group Cl Embodiments, wherein determining the list of NTN cell configurations with related time windows indicating when the future time associations in the list of NTN cell configurations are valid, comprises: creating a number of NRCellCU instances with configurations and NRCellDU instances with configurations determined to be equal to a maximum number of ground fixed cells and / or quasi-ground fixed cells that the base stations in satellites can serve; and indicating which of the NRCellCU instances and NRCellDU instances are valid in different time periods according to the list of NTN cell configurations.12. The method of any of the Group Cl Embodiments, wherein sending the batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite, comprises: sending the batch of the list of NTN cell configurations with an indication in which timeperiods NRCellCU instances are valid for the base station.13. The method of any of the Group Cl Embodiments, wherein sending the batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite, comprises: sending the batch of the list of NTN cell configurations with an indication in which time periods NRCellDU instances are valid for the base station.14. The method of any of Embodiments 12-13, wherein the sending of the batch of the list of NTN cell configurations to the base station in at least one satellite is by an NR NRM MnS service ModifyMOIAttributes() function with a NRCellValidTimeWindowList for TimeWindow entries in the base station in the at least one satellite.Group C2 Embodiments1. A method performed by a base station in a satellite for serving ground fixed NonTerrestrial Network, NTN, cells, the method comprising: receiving (2600) from a terrestrial network management node, a list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid; and responsive to determining that one of the time windows has become valid, performing (2602) communications using the NTN cell configuration in the list related with the valid time window.2. The method of any of the Group C2 Embodiments, wherein the satellite is a non- geostationary orbit satellite.3. The method of any of the Group C2 Embodiments, wherein receiving from the terrestrial network management node, the list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid, comprises: receiving the list of NTN cell configurations with related time windows from a terrestrial network management node through an NR NRM MnS service ModifyMOIAttributes() function.4. The method of Embodiment 4, further comprising sending a log of changes that indicates NTN cell configuration changes performed for gNB-CU-CP.5. The method of any of Embodiments 4 to 5, further comprising sending a log of changes that indicates NTN cell configuration changes performed for gNB-DU.6. The method of any of the Group C2 Embodiments, wherein receiving from the terrestrial network management node, the list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid, comprises: receiving the list of NTN cell configurations with an indication in which time periods NRCellCU instances are valid for the base station.7. The method of any of the Group C2 Embodiments, wherein receiving from the terrestrial network management node, the list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid, comprises: receiving the list of NTN cell configurations with an indication in which time periods NRCellDU instances are valid for the base station.REFERENCES[1] 3GPP TR 23.700-29 v0.3.0 (2024-01) Study on integration of satellite components in the 5G architecture; Phase 3[2] 3GPP TR 28.808 V17.0.0 (2021-03) Study on management and orchestration aspects of integrated satellite components in a 5G network[3] 3GPP TR 28.841 V18.0.1 (2023-06) Study on management aspects of Internet of Things (loT) Non-Terrestrial Networks (NTN) enhancements[4] 3GPP TR 28.844 V18.0.0 (2023-12) Study on charging aspects of satellite in the 5G System (5GS)[5] 3GPP TS 28.530 V18.0.0 (2023-12) Management and orchestration; Concepts, use cases and requirements[6] 3GPP TS 28.531 V18.4.0 (2023-12) Management and orchestration; Provisioning[7] 3GPP TS 28.532 V18.1.0 (2023-12) Management and orchestration; Generic management services[8] 3GPP TS 28.533 V18.0.0 (2023-12) Management and orchestration; Architecture framework[9] 3GPP TS 28.540 V17.3.0 (2022-12) Management and orchestration; 5G Network Resource Model (NRM); Stage 1

[0010] 3GPP TS 28.541 vl 8.6.1 (2024-01) Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3

[0011] 3GPP TS 28.552 V18.5.0 (2023-12) 5G performance measurements

[0012] 3GPP TS 28.554 V18.4.0 (2023-12) 5G end to end Key Performance Indicators (KPI)

[0013] 3GPP TS 28.622 V18.5.0 (2023-12) Generic Network Resource Model (NRM)Integration Reference Point (IRP); Information Service (IS)

[0014] 3GPP TS 28.662 V17.0.0 (2022-03) Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)

[0015] Approved 3GPP Rel-18 CR “S5-236095 Rel-18 CR TS 28.541 NTN CoverageAvailability Information Configuration Stage 2” (implemented in TS 28.541 vl 8.6.1)

[0016] Approved 3GPP Rel-18 CR “S5-236097 Rel-18 CR 28.541 NTN Location Restriction Stage-2” (implemented in TS 28.541 vl 8.6.1)

[0017] 3GPP TS 32.300 V18.0.0 (2023-12) Name convention for managed objects

[0018] 0-RAN.WG4.MP.0-R003-vl3.00, O-RAN Working Group 4 (Open Fronthaul Interfaces WG) Management Plane Specification.ABBREVIATIONS

[0324] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).3GPP 3rd Generation Partnership Project5G 5th Generation5GC 5G Core Network5GS 5G System6G 6thGenerationABS Almost Blank SubframeAMF Access and Mobility Management FunctionAR Augmented RealityARQ Automatic Repeat RequestAUSF Authentication Server FunctionAWGN Additive White Gaussian NoiseBCCH Broadcast Control ChannelBCH Broadcast ChannelBWP Bandwidth PartCA Carrier AggregationCC Carrier ComponentCCCH SDU Common Control Channel SDUCDMA Code Division Multiplex AccessCGI Cell Global IdentityCIR Channel Impulse ResponseCN Core NetworkCP Cyclic PrefixCPE Customer-Premise EquipmentCPICH Common Pilot ChannelCQI Channel Quality InformationC-RNTI Cell RNTICSI Channel State InformationCUCPFunction Central Unit Control Plane FunctionDCCH Dedicated Control ChannelDHCP Dynamic Host Configuration ProtocolDE DownlinkDM DemodulationDMRS Demodulation Reference SignalDN Distinguished NameDRX Discontinuous ReceptionDSRC Dedicated Short-Range CommunicationDTX Discontinuous TransmissionDTCH Dedicated Traffic ChannelDUT Device Under TestE-CID Enhanced Cell-ID (positioning method)Ec / No Received energy per chip divided by the power density in the bandECGI Evolved CGIeMBB Enhanced Mobile Broadband eMBMS Evolved Multimedia Broadcast Multicast Services eMTC Enhanced Machine Type Communications EN-DC New Radio - Dual Connectivity eNB E-UTRAN NodeB ePDCCH Enhanced Physical Downlink Control Channel EP_N2 EndPoint on the N2 interface EP_NgC EndPoint Next generation Core EPC Evolved Packet Core EPS Evolved Packet System E-UTRAN Evolved-UMTS Terrestrial Radio Access Network NR NRM MnS New Radio Network Resource Model Management Services E-SMLC Evolved Serving Mobile Location Center E-UTRAN Evolved Universal Terrestrial Radio Access Network FDD Frequency Division Duplex FFS For Further Study GEO Geostationary Earth Orbit gNB gNodeB GNSS Global Navigation Satellite System GSM Global System for Mobile Communications HARQ Hybrid Automatic Repeat Request HAPS High-Altitude Platforms HO Handover HRPD High Rate Packet Data HSPA High Speed Packet Access HSS High Subscriber Server IEEE Institute of Electrical and Electronics Engineers LEE Laptop-Embedded Equipment LEO Low Earth Orbit LOS Line of Sight LLS-M Lower-Layer Split M-plane LME Laptop-Mounted Equipment LPP LTE Positioning Protocol LPWAN Low-Power Wide-Area Network LTE Long-Term Evolution LTE-M Long Term Evolution Machine Type Communication MAC Medium Access Control MAC Message Authentication Code MBB Mobile Broadband MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests MEO Medium Earth Orbit MIB Master Information Block MME Mobility Management Entity mMTC Massive Machine Type Communications MnS Management Service MO Managed Object MR-DC Multi-Radio Dual Connectivity MSC Mobile Switching CenterMTC Machine Type Communications NB-IoT Narrow Band Internet Of Things NEF Network Exposure Function NETCONF Network Configuration Protocol NFC Near Field Communication NPDCCH Narrowband Physical Downlink Control Channel NR New Radio NTN Non-Terrestrial Network OCNG OFDMA Channel Noise Generator O-CU Open Central Unit O-CU-CP O-CU Control Plane O-CU-UP O-CU User Plane O-DU Open RAN Distributed Unit OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access O-RAN Open Radio Access Network O-RAN LLS O-RAN Lower-Layer Split O-RU Open RAN Radio Unit OSS Operations Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDA Personal Digital Assistant PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDP Power Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid- ARQ Indicator Channel PLMN Public Land Mobile Network PMI Precoding Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS Primary Synchronization Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QAM Quadrature Amplitude Modulation RACH Random Access Channel RAN Radio Access Network RAT Radio Access Technology RLC Radio Link Control RLM Radio Link Monitoring RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS Reference SignalRSCP Received Signal Code Power RSRP Reference Symbol Received Power ORReference Signal Received PowerRSRQ Reference Signal Received Quality ORReference Symbol Received QualityRSSI Received Signal Strength Indicator RSTD Reference Signal Time Difference SBMA Service Based Management Architecture SCH Synchronization Channel SCell Secondary Cell SDAP Service Data Adaptation Protocol SDU Service Data Unit SEPP Security Edge Protection Proxy SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SIDF Subscription Identifier De-concealing Function SMF Session Management Function SNR Signal to Noise Ratio SON Self-Organizing Network ss Synchronization Signal sss Secondary Synchronization Signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Time of Arrival TS Technical Specification TSS Tertiary Synchronization Signal TTI Transmission Time Interval UDM Unified Data Management UE User Equipment UE Uplink UMTS Universal Mobile Telecommunications System UPF User Plane Function URLEC Ultra-Reliable and Low Latency Communication USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival V2I V ehicle-to-Infr astructure V2V V ehicle-to- V chicle V2X V ehicle-to-Every thing VoIP Voice Over IP VR Virtual Reality WCDMA Wideband CDMA WiMax Worldwide Interoperability for Microwave Access WLAN Wireless Local Area Network

Claims

CLAIMS:

1. A method performed by a terrestrial network management node for managing base stations in satellites, the method comprising: obtaining (1300) a list of associations between base stations in satellites and access mobility functions on ground and related time windows indicating when the associations in the list are valid; for each of the base stations in satellites, sending (1302) to the base station a batch of the associations of the base station to the access mobility functions and related time windows indicating when the associations in the batch are valid; and for each of the access mobility functions, sending (1304) to the access mobility function a batch of the associations of the access mobility function to the base stations in satellites and related time windows indicating when the associations in the batch are valid.

2. The method of claim 1, wherein the access mobility function comprises an Access and Mobility Function, AMF, or a Mobility Management Entity, MME.

3. The method of any of claims 1 to 2, wherein the base station comprises a gNodeB, gNB, or an eNodeB, eNB.

4. The method of any of claims 1 to 3, wherein the sending to the base stations in satellites the batch of the associations to the access mobility functions comprises sending a remote address list of the access mobility functions.

5. The method of claim 4, wherein the remote address list comprises time stamps and remote IP addresses to be used for initialization and / or release of transport to the access mobility functions.

6. The method of claim 5, wherein the time stamps each comprise a start time and end time when the remote address is valid.

7. The method of any of claims 1 to 6, wherein the sending to the access mobility functions the batch of the associations to the base stations in satellites comprises sending a remote address list of the base stations.

8. The method of claim 7, wherein the remote address list comprises time stamps and remote IP addresses to be used for initialization and / or release of transport to the base stations.

9. The method of claim 8, wherein the time stamps each comprise a start time and end time when the remote address is valid.

10. The method of any of claims 1 to 9, further comprising: for each of the base stations in satellites, creating a number of Managed Object, MO, EndPoint Next generation Core, EP_NgC, instances for a Central Unit Control Plane Function, CUCPFunction, through New Radio Network Resource Model Management Services, NR NRM MnS; and receiving, from the base stations, changes to the EP_NgC instances.

11. The method of claim 10, wherein the number of EP_NgC instances is equal to a maximum number of simultaneous access mobility functions that the base station will connect to during satellite orbit.

12. The method of any of claims 1 to 11, further comprising: for each of access mobility functions on ground, creating a number of Managed Object, MO, EndPoint on an N2 interface, EP_N2, instances for a Central Unit Control Plane Function, CUCPFunction, through 5G Core Network Resource Model Management Services, 5GC NRM MnS; and receiving, from the access mobility functions, changes to the EP_N2 instances.

13. The method of claim 12, wherein the number of EP_N2 instances is equal to a maximum number of simultaneous base stations that the access mobility function will connect to as the satellites orbit.

14. The method of any of claims 1 to 13, wherein the associations and time windows are calculated based on at least one of: positions of ground gateways providing satellite feeder links for access mobility functions; indication of ability for the access mobility functions to connect to the ground gateways; expected orbit positions of the base stations in satellites during the time windows;availability of communication feeder links between the ground gateways and the satellites during the time windows; operation conditions of the base stations in satellites; and available access mobility functions during the time windows.

15. A method performed by a terrestrial network management node for managing base stations in satellites, the method comprising: obtaining (2500) future time associations between base stations in satellites and NonTerrestrial Network, NTN, cell coverage on ground; based on the future time associations, determining (2502) a list of NTN cell configurations with related time windows indicating when the associations in the list of NTN cell configurations are valid; sending (2504) a batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite.

16. The method of claim 15, wherein determining a list of NTN cell configurations with related time windows indicating when the future time associations in the list of NTN cell configurations are valid, comprises: creating a number of NRCellCU instances and NRCellDU instances determined based on a maximum number of NRCellCU instances and NRCellDU instances that the base stations in satellites can handle simultaneously at the same time; and changing configuration of the NRCellCU instances and NRCellDU instances according to the list of NTN cell configurations.

17. The method of claim 16, wherein each NTN cell configuration in the list of NTN cell configurations comprises information indicating the time window when the associated NTN cell configuration is valid and comprises a valid configuration attribute for serving a ground fixed NTN cell coverage during the time window.

18. The method of claim 16, wherein creating the number of NRCellCU instances and NRCellDU instances further comprises: creating the number of NRCellCU instances and NRCellDU instances to be no less than a maximum number of ground fixed cells and / or quasi ground fixed cells that the base station in one of the satellites can serve simultaneously.

19. The method of any of claims 15 to 18, wherein sending a batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite, comprises: sending the batch of the list of NTN cell configurations with related time windows to the base station in a satellite through an NR NRM MnS service ModifyMOIAttributes() function.

20. The method of any of claims 15 to 19, wherein obtaining future time associations between base stations in satellites and NTN cell coverage on ground, comprises: determining a future time association between a base station in a satellite and a NTN cell coverage on ground, based on any one or more of: minimum elevation angle between a base station on ground and the base station in the satellite; an expected orbit position of the base station in the satellite over the time window; availability of a feeder link between the base station on ground and the base station in the satellite over the time window; and an operation condition of at least one of the base station in the satellite, ground gateways, ground Access Mobility Function, and transport over the time period.

21. The method of any of claims 15 to 20, the method further comprising: receiving from the base station in the at least one satellite a log of changes to NTN cell configurations that have been performed, wherein the log of changes indicates NTN cell configuration changes performed for gNB-CU-CP or gNB-DU.

22. The method of any of claims 15 to 21, wherein determining the list of NTN cell configurations with related time windows indicating when the future time associations in the list of NTN cell configurations are valid, comprises: creating a number of NRCellCU instances with configurations and NRCellDU instances with configurations determined to be equal to a maximum number of ground fixed cells and / or quasi-ground fixed cells that the base stations in satellites can serve; and indicating which of the NRCellCU instances and NRCellDU instances are valid in different time periods according to the list of NTN cell configurations.

23. The method of any of claims 15 to 22, wherein sending the batch of the list of NTN cell configurations with related time windows to a base station in at least one satellite, comprises: sending the batch of the list of NTN cell configurations with an indication in which time periods NRCellCU instances are valid for the base station, orsending the batch of the list of NTN cell configurations with an indication in which time periods NRCellDU instances are valid for the base station.

24. The method of any of claims 15 to 23, wherein the associations and time windows are calculated based on at least one of: minimum elevation angle between the ground fixed cell and base stations in satellites; expected orbit positions of the base stations in satellites during the time windows; positions of ground gateways providing satellite feeder links for base station; indication of ability for the base station to connect to the ground gateways; availability of communication feeder links between the ground gateways and the satellites during the time windows; and operation conditions of the base stations in satellites.

25. A method performed by a base station in a satellite for serving ground fixed NonTerrestrial Network, NTN, cells, the method comprising: receiving (2600) from a terrestrial network management node, a list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid; and responsive to determining that one of the time windows has become valid, performing (2602) communications using the NTN cell configuration in the list related with the valid time window.

26. The method of claim 25, wherein receiving from the terrestrial network management node, the list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid, comprises: receiving the list of NTN cell configurations with related time windows from a terrestrial network management node through an NR NRM MnS service ModifyMOIAttributes() function.

27. The method of any of claims 25 to 26, further comprising sending a log of changes that indicates NTN cell configuration changes performed for gNB-CU-CP or sending a log of changes that indicates NTN cell configuration changes performed for gNB-DU.

28. The method of any of claims 25 to 27, wherein receiving from the terrestrial networkmanagement node, the list of NTN cell configurations and related time windows indicating when the NTN cell configurations in the list are valid, comprises: receiving the list of NTN cell configurations with an indication in which time periods NRCellCU instances are valid for the base station, or receiving the list of NTN cell configurations with an indication in which time periods NRCellDU instances are valid for the base station.

29. A method performed by a terrestrial network management node for managing O-RU functions in satellites communicating with O-DU functions of base stations on ground, the method comprising: obtaining (1900) a list of associations between O-RUs in satellites and the O-DU functions of the base stations on ground and related time windows indicating when the associations in the list are valid; for each of the O-RUs in satellites, sending (1902) to the O-RU indications of a batch of the associations of the O-RU to the O-DU functions of the base stations and related time windows indicating when the associations in the batch are valid; and for each of the O-DU function of the base station on ground, sending (1904) to the O- DU function indications of a batch of the associations of the O-DU function to the O-RUs and related time windows indicating when the associations in the batch are valid.

30. The method of claim 29, wherein the sending to the O-RUs in satellites indications of the batch of the associations of the O-RU to the O-DU functions of the base stations comprises sending a carrier list, and wherein the carrier list comprises time stamps and carriers for communications with the O-DU functions of the base stations.

31. The method of claim 30, wherein the time stamps each comprise a start time and end time when the carrier is valid.

32. The method of any of claims 29 to 31, wherein the sending to the O-DU functions of the base stations indications of the batch of the associations to the O-RUs in satellites comprises sending a carrier list of the O-RUs, wherein the carrier list comprises time stamps and carriers for communications with the O-RUs, and wherein the time stamps each comprise a start time and end time when the association of the O-RU to the O-DU function and the carrier is valid.

33. The method of any of claims 29 to 32, further comprising: for each of the O-RUs in satellites, creating a number of Managed Object, MO, SectorEquipmentFunction instances through YANG model of O-RAN LLS interfaces; receiving, from the O-RUs, changes to the SectorEquipmentFunction instances.

34. The method of any of claims 29 to 33, further comprising: for each of the O-DU functions on ground, creating a number of Managed Object, MO, NRSectorCarrier instances for a GNBDUFunction, through New Radio Network Resource Model Management Services, NR NRM MnS; receiving, from the O-DU function, changes to the NRSectorCarrier instances.

35. The method of claim 34, wherein the number of NRSectorCarrier instances is equal to a maximum number of sector carriers the O-DU function will use.

36. The method of any of claims 29 to 35, wherein the associations and time windows are calculated based on at least one of: positions of ground gateways providing satellite feeder links for O-DU functions; indication of ability for the O-DU functions to connect to the ground gateways; expected orbit positions of the O-RUs in satellites during the time windows; availability of communication feeder links between the ground gateways and the satellites during the time windows; operation conditions of the O-RUs in satellites; and available O-DU functions during the time windows.

Images