[go: up one dir, main page]

WO2024035965A1 - Procédés d'accumulation de si dans un ntn ido avec indication de temps d'époque explicite et implicite - Google Patents

Procédés d'accumulation de si dans un ntn ido avec indication de temps d'époque explicite et implicite Download PDF

Info

Publication number
WO2024035965A1
WO2024035965A1 PCT/US2023/030170 US2023030170W WO2024035965A1 WO 2024035965 A1 WO2024035965 A1 WO 2024035965A1 US 2023030170 W US2023030170 W US 2023030170W WO 2024035965 A1 WO2024035965 A1 WO 2024035965A1
Authority
WO
WIPO (PCT)
Prior art keywords
ntn
sib
host
accumulation
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2023/030170
Other languages
English (en)
Inventor
Talha KHAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to CN202380072100.2A priority Critical patent/CN120019591A/zh
Publication of WO2024035965A1 publication Critical patent/WO2024035965A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1851—Systems using a satellite or space-based relay
    • H04B7/18519—Operations control, administration or maintenance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
    • H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • the present disclosure generally relates to the non-terrestrial cellular communication technology.
  • EPS Evolved Packet System
  • LTE Long-Term Evolution
  • EPC Evolved Packet Core
  • 5G 5G system
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low latency communication
  • 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC).
  • NR New Radio
  • GC 5G Core Network
  • the NR physical and higher layers are reusing some parts of the LTE specification, and add needed components.
  • One such component is the introduction of a sophisticated framework for beam forming and beam management to extend the support of the 3 GPP technologies to a frequency range going beyond 6 GHz.
  • Satellite networks could complement mobile networks on the ground by providing connectivity to underserved areas and multicast/broadcast services.
  • 3GPP Release 15 3GPP started the work to prepare NR for operation in a Non-Terrestrial Network (NTN). The work was performed within the study item “NR to support Non-Terrestrial Networks’’ and resulted in 3GPP TR 38.811 [1].
  • NTN Non-Terrestrial Network
  • 3GPP 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”, which has been captured in 3GPP TR 38.821 [2].
  • 3 GPP Release 17 contained both a work item on NR NTN [3] and a study item on NB-IoT and LTE-M support for NTN [4],
  • a satellite radio access network usually includes the following components:
  • An earth-based gateway that connects the satellite to a base station or a core network, depending on the choice of architecture.
  • Feeder link that refers to the link between a gateway and a satellite
  • Access link or service link, that refers to the link between a satellite and a UE.
  • a satellite may be categorized as low earth orbit (LEO), medium earth orbit (MEO), or geostationary earth orbit (GEO) satellite.
  • LEO low earth orbit
  • MEO medium earth orbit
  • GEO geostationary earth orbit
  • 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.
  • GEO height at about 35,786 km, with an orbital period of 24 hours.
  • Transparent pay load also referred to as bent pipe architecture.
  • the satellite forwards the received signal between the terminal and the network equipment on the ground with only amplification and a shift from uplink frequency to downlink frequency.
  • the transparent payload architecture means that the gNB is located on the ground and the satellite forwards signals/data between the gNB and the UE.
  • Regenerative payload The satellite includes on-board processing to demodulate and decode the received signal and regenerate the signal before sending it back to the earth.
  • the regenerative payload architecture means that the gNB is located in the satellite.
  • Figure 1 shows an example architecture of a satellite network with bent pipe transponders (i.e., the transparent payload architecture).
  • the gNB may be integrated in the gateway or connected to the gateway via a terrestrial connection (wire, optic fiber, wireless link).
  • a communication satellite typically generates several beams over a given area.
  • the footprint of a beam is usually in an elliptic shape, which has traditionally been considered as a cell, but cells consisting of the coverage footprint of multiple beams are not excluded in the 3GPP work.
  • the footprint of a beam is also often referred to as a spotbeam.
  • the footprint of a beam may move over the earth’s surface with the satellite movement or may be earth fixed with a beam pointing mechanism used by the satellite to compensate for the satellite’s motion.
  • the size of a spotbeam depends on the system design, which may range from tens of kilometers to a few thousands of kilometers.
  • Propagation delay is an important aspect of satellite communications that is different from the delay expected in a terrestrial mobile system.
  • the roundtrip delay may, depending on the orbit height, range from tens of ms in the case of LEO satellites to several hundreds of ms for GEO satellites.
  • the round-trip delays in terrestrial cellular networks are typically below 1 ms.
  • Table 1 Propagation delay for different orbital heights and elevation angles.
  • the propagation delay may also be highly variable due to the high velocity of the LEO and MEO satellites and change in the order of 10 - 100 ps every second, depending on the orbit altitude and satellite velocity.
  • the long propagation delay means that the timing advance (TA) the UE uses for its uplink transmissions is essential and has to be much greater than in terrestrial networks in order for the uplink and downlink to be time aligned at the gNB, as is the case in NR and LTE.
  • TA timing advance
  • RA random access
  • the random access preamble i.e., the initial message from the UE in the random access procedure
  • the random access preamble has to be transmitted with a timing advance to allow a reasonable size of the RA preamble reception window in the gNB (and to ensure that the cyclic shift of the preamble’s Zadoff-Chu sequence cannot be so large that it makes the Zadoff-Chu sequence, and thus the preamble, appear as another Zadoff-Chu sequence, and thus preamble, based on the same Zadoff-Chu root sequence), but this TA does not have to be as accurate as the TA the UE subsequently uses for other uplink transmissions.
  • the TA the UE uses for the RA preamble transmission in NTN is called “pre-compensation TA”.
  • the UE autonomously calculates the propagation delay between the UE and the satellite, based on the UE’s and the satellite’s respective positions, and the network/gNB broadcasts the propagation delay on the feeder link, i.e., the propagation delay between the gNB and the satellite.
  • the UE acquires its own position using GNSS measurements and the UE obtains the satellite position using satellite orbital data (including satellite position at a certain time) broadcast by the network.
  • the pre-compensation TA is then twice the sum of the propagation delay on the feeder link and the propagation delay between the satellite and the UE.
  • the gNB broadcasts a timestamp (in SIB9), which the UE compares with a reference timestamp acquired from GNSS. Based on the difference between these two timestamps, the UE can calculate the propagation delay between the gNB and the UE, and the precompensation TA is twice as long as this propagation delay.
  • the gNB provides the UE with an accurate (i.e. fine-adjusted) TA in the Random Access Response message (in 4-step RA) or MsgB (in 2-step RA), based on the time of reception of the random access preamble.
  • the gNB can subsequently adjust the UE’s TA using a Timing Advance Command MAC CE (or an Absolute Timing Advance Command MAC CE), based on the timing of receptions of uplink transmissions from the UE.
  • a Timing Advance Command MAC CE or an Absolute Timing Advance Command MAC CE
  • the time advance control framework also includes a time alignment timer that the gNB configures the UE with. The time alignment timer is restarted every time the gNB adjusts the UE’s TA and if the time alignment timer expires, the UE is not allowed to transmit in the uplink without a prior random access procedure (which serves the purpose to provide the UE with a valid timing advance).
  • 3GPP has also agreed that in addition to the gNB’s control of the UE’s TA, the UE is allowed to autonomously update its TA based on estimation of changes in the UE-gNB RTT using the UE’s location (e.g., obtained from Global Navigation Satellite System (GNSS) measurement) and knowledge of the serving satellite’s ephemeris data and feeder link delay information from the gNB.
  • GNSS Global Navigation Satellite System
  • a second relevant aspect is that not only is the propagation delay between the UE and a satellite, or between the UE and a gNB, very long in NTN, but the due to the large distances, the difference in propagation delay to two different satellites, or two different gNBs, may be significant on the timescales relevant for cellular communication, including signaling procedures, even when the satellites/gNBs serve neighboring cells. This has an impact on all procedures involving reception or transmission in two cells served by different satellites and/or different gNBs.
  • a third important aspect related to the long propagation delay/RTT in Non-Terrestrial Networks is the introduction of an additional parameter to compensate for the long propagation delay/RTT.
  • the UE-gNB RTT may range from more or less zero to several tens of microseconds in a cell.
  • a major difference in Non-Terrestrial Networks, apart from the sheer size of the propagation delay/RTT, is that even at the location in the cell where the propagation delay/RTT is the smallest, it will be large and nowhere close to zero. In fact, the variation of the propagation delay/RTT within a NTN cell is small compared to the propagation delay/RTT.
  • Koffset (or sometimes K_offset).
  • Koffset may potentially be used in various timing related mechanisms, but the application mainly in focus is to use it in the scheduling of uplink transmissions on the PUSCH.
  • Koffset is used to indicate an additional delay between the UL grant and the PUSCH transmission resources allocated by UL grant to be added to the slot offset parameter K2 in the DCI containing the UL grant.
  • the offset between the UL grant and the slot in which the PUSCH transmission resources are allocated is thus Koffset + K2.
  • Koffset can be said to serve the purpose to ensure that the UE is never scheduled to transmit at a point in time that, due to the large TA the UE has to apply, would occur before the point in time when the UE receives the UL grant.
  • it is also discussed to let the network’ s configuration of Koffset take into account the TA the UE may have signaled that it has used.
  • a fourth important aspect closely related to the timing is a Doppler frequency offset induced by the motion of the satellite.
  • the access link may be exposed to Doppler shift in the order of 10-100 kHz in sub-6 GHz frequency band and proportionally higher in higher frequency bands. Also, the Doppler shift is varying, with a rate of up to several hundred Hz per second in the S-band and several kHz per second in the Ka-band.
  • TR 38.821 it has been captured that ephemeris data should be provided to the UE, for example to assist with pointing a directional antenna (or an antenna beam) towards the satellite, and to calculate a correct Timing Advance (TA) and Doppler shift. Procedures on how to provide and update ephemeris data have not yet been studied in detail, though, but broadcasting of ephemeris data in the system information is one option.
  • TA Timing Advance
  • a satellite orbit can be fully described using 6 parameters. Exactly which set of parameters is chosen can be decided by the user; many different representations are possible. For example, a choice of parameters used often in astronomy is the set (a, e, i, , ®, t).
  • the semimajor axis a and the eccentricity s describe the shape and size of the orbit ellipse; the inclination i, the right ascension of the ascending node Q, and the argument of periapsis co determine its position in space, and the epoch t determines a reference time (e.g., the time when the satellites moves through periapsis).
  • This set of parameters is illustrated in Figure 2.
  • the TLEs use mean motion n and mean anomaly M instead of a and t.
  • a completely different set of parameters is the position and velocity vector (x, y, z, v x , v y , v z ) of a satellite. These are sometimes called orbital state vectors. They can be derived from the orbital elements and vice versa, since the information they contain is equivalent. All these formulations (and many others) are possible choices for the format of ephemeris data to be used in NTN. To enable further progress, the format of the data should be agreed upon.
  • Non-Terrestrial Network typically features the following elements [3]:
  • Non-Terrestrial Network One or several sat-gateways that connect the Non-Terrestrial Network to a public data network
  • a GEO satellite is fed by one or several sat-gateways which are deployed across the satellite targeted coverage (e.g., regional or even continental coverage).
  • sat-gateways which are deployed across the satellite targeted coverage (e.g., regional or even continental coverage).
  • UE in a cell are served by only one sat-gateway
  • a Non-GEO satellite served successively by one sat-gateway at a time.
  • the system ensures service and feeder link continuity between the successive serving sat-gateways with sufficient time duration to proceed with mobility anchoring and hand-over
  • Table 4.2-2 Reference scenario parameters [3] NOTE 1: Each satellite has the capability to steer beams towards fixed points on earth using beamforming techniques. This is applicable for a period of time corresponding to the visibility time of the satellite.
  • scenario D which is LEO with regenerative payload
  • scenario D both earth-fixed and earth moving beams have been listed. So, when we factor in the fixed/non-fixed beams, we have an additional scenario.
  • the complete list of 5 scenarios in 3GPP TR 38.821 [2] is then:
  • Figure 3 illustrates an NB-IoT system information block (SIB) Type-x (SIBxNB) transmission and related parameter ranges for repetition pattern within a system information (SI) window, the duration of SI window and the periodicity of SI window.
  • SIBxNB system information block
  • the same repetition pattern is used for all SI messages.
  • the network can configure a maximum of 80 repetitions within an SI window assuming a maximum SI window length of 160 frames (i.e., 1600 ms) and a repetition pattern where SIB is repeated in every other frame.
  • the possible SI window periodicities are ⁇ 8, 16, 32, 64, 128, 256, 512 ⁇ frames and the possible SI window lengths are ⁇ I, 2, 5, 10, 15, 20, 40, 60, 80, 120, 160, 200 ⁇ ms.
  • SI messages in LTE-M can be repeated within their respective SI windows to support operation in extended coverage. Possible repetition patterns are ⁇ every frame, every second frame, every fourth frame, and every eighth frame ⁇ throughout the SI window. All SI messages have the same repetition pattern.
  • Common TA Epoch time is implicitly known as a reference time defined by the starting time of a DL slot and/or frame.
  • the UE assumes that it has lost uplink synchronization if new or additional assistance information (i.e. serving satellite ephemeris data or Common TA parameters) is not available within the associated validity duration.
  • new or additional assistance information i.e. serving satellite ephemeris data or Common TA parameters
  • the serving satellite ephemeris and common TA related parameters are signalled in the same SIB message and have the same epoch time.
  • a single validity duration for both serving satellite ephemeris and common TA related parameters is broadcast on the SIB.
  • LEO/MEO/GEO based non-terrestrial access network o Position and velocity state vector ephemeris format is 17 bytes payload.
  • the quantization step is 0.06 m/s for Velocity o Orbital parameter ephemeris format 18 byte payload
  • Epoch time of assistance information is the starting time of a DL sub-frame, indicated by a SFN and a sub-frame number signaled together with the assistance information.
  • epoch time of assistance information i.e. Serving satellite ephemeris and Common TA parameters
  • epoch time of assistance information is the starting time of a DL sub-frame, indicated by a SFN and a sub-frame number.
  • epoch time of assistance information i.e. Serving satellite ephemeris and Common TA parameters
  • the end of the SI window during which the NTN-specific SIB SI message is transmitted is implicitly known as the end of the SI window during which the NTN-specific SIB SI message is transmitted.
  • the quantization step is 1.431 x 10 -8
  • the quantization step is 2.341 x 10 -8 rad
  • the quantization step is 2.341 x 10 -8 rad
  • the quantization step is 2.341 X 10 -8 rad
  • the quantization step is 2.341 X 10 -8 rad
  • loT NTN has introduced two NTN-specific SIBs.
  • the first SIB contains information elements required to synchronize to the cell such as ephemeris information, common TA parameters, the uplink sync validity timer duration, epoch time for assistance information.
  • Some of the agreements of the NTN SIB include.
  • the serving cell ephemeris information (used for LI pre-compensation) is signalled in a new SIB, which is NTN specific.
  • the timing information on when a serving cell is going to stop serving the area is broadcast in the same SIB as the ephemeris information.
  • RAN2#116bis-e • TA common parameters, UL synchronisation validity duration and ephemeris epoch time are signalled in the NTN specific SIB (SIBXX).
  • K_offset and K_mac parameters are signalled in the NTN specific SIB (SIBXX).
  • SIBXX is an essential SIB, i.e. the UE shall consider the cell barred if it is unable to acquire the SIB when scheduled.
  • SIBXX structure is included in RRCReconfiguration message for handover.
  • TXXXX • Introduce a guard timer TXXXX for SIBXX acquisition in connected mode.
  • TXXX expiry, UE triggers RLF (if it can be shown in Q2 that UE will loose RLM when UE tunes away, it can be discussed to skip this timer)
  • SIBXX acquisition is captured in 5.2.2.
  • UE actions upon ul- SyncValidityTimer expiry are described in a new section in 5.3.3, which will refer to 5.2.2 for SIBXX (re)acqui sition
  • SIBXX is included outside mobility Controlinfo, similarly to other dedicated SIB.
  • the IE SystemlnformationBlockTypeS 1 contains satellite assistance information for the serving cell.
  • the second SIB has been introduced to broadcast information that is needed to handle discontinuous coverage scenario in loT NTN, e.g., it includes information elements containing satellite ephemeris of neighbouring and upcoming satellites so that the UE knows when to wake up to receive coverage. This is useful in scenarios e.g., low-density or sparse LEO constellations where the number of satellites in the constellation are not enough to cover the whole earth at a given time.
  • RAN2 will use a new SIB to share the ephemeris information for Discontinuous Coverage with the UEs. Sharing the information using dedicated RRC signalling is FFS.
  • epoch time is included in the NTN SIB. Therefore, the content of the NTN SIB remains unchanged as long as the epoch time remains unchanged (in addition to the common TA parameters, the ephemeris and the validity timer remaining unchanged).
  • epoch time can be indicated up to 5.12 sec into the past or future (with the possibility to indicate epoch time in both the past and the future), or up to 10.24 sec into the future or into the past (with the possibility to indicate the epoch time in the past only or in the future only). Since NTN SIB is an essential SIB, it is expected to be transmitted with a shorter SI periodicity e.g., at least once a second.
  • the epoch time indication range essentially limits the SIB accumulation to shorter SI periodicities of up to 64 frames.
  • Gl A method by a user equipment or network node to facilitate NTN SIB accumulation in NTN to allow operation in coverage limited condition and to avoid decoding error when NTN SIB contents change frequently for either or both implicit and explicit epoch time indication, the method comprising:
  • G4 A user equipment of network node having hardware configured to facilitate
  • NTN SIB accumulation in NTN to allow operation in coverage limited condition and to avoid decoding error when NTN SIB contents change frequently for both implicit and explicit epoch time indication, by performing any of the user equipment or network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.
  • the one or more SI configuration parameters comprises an epoch timer indication range and/or a number of SI windows.
  • A5. The method of embodiment Al or A2, wherein the UE determines whether the network is using explicit or implicit epoch time indication based on one of:
  • A6 The method of embodiment Al or A2, wherein the one or more parameters includes an validity timer update.
  • a method performed by a user equipment (UE) for to facilitate NTN SIB accumulation comprising:
  • a 10 The method of embodiment A9, further comprising decoding an NTN SIB.
  • decoding an NTN SIB comprises:
  • [0108] store the first NTN SIB and receive and store the second NTN SIB in the next SI transmission.
  • a user equipment for facilitating NTN SIB accumulation in NTN to allow operation in coverage limited condition and to avoid decoding error when NTN SIB contents change frequently for either or both implicit and explicit epoch time indication comprising: [0114] processing circuitry configured to perform any of the steps of any of the Group A or General Group embodiments; and
  • power supply circuitry configured to supply power to the processing circuitry.
  • a user equipment (UE) for facilitating NTN SIB accumulation in NTN to allow operation in coverage limited condition and to avoid decoding error when NTN SIB contents change frequently for either or both implicit and explicit epoch time indication comprising: [0117] an antenna configured to send and receive wireless signals;
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; [0119] the processing circuitry being configured to perform any of the steps of any of the Group A or General Group embodiments;
  • an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry
  • an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry
  • a battery connected to the processing circuitry and configured to supply power to the UE.
  • a host configured to operate in a communication system to provide an over-the- top (OTT) service, the host comprising:
  • processing circuitry configured to provide user data
  • a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • the processing circuitry of the host is configured to execute a host application that provides the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • B5. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: [0130] providing user data for the UE; and
  • a communication system configured to provide an over-the-top (OTT) service, the communication system comprising: [0135] a host comprising:
  • processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service;
  • a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • a host configured to operate in a communication system to provide an over-the- top (OTT) service, the host comprising:
  • processing circuitry configured to initiate receipt of user data
  • a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • UE user equipment
  • the processing circuitry of the host is configured to execute a host application that receives the user data
  • the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • a host configured to operate in a communication system to provide an over-the- top (OTT) service, the host comprising:
  • processing circuitry configured to provide user data
  • a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A or General Group embodiments to receive the user data from the host.
  • UE user equipment
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data
  • the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Bl A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising:
  • a host configured to operate in a communication system to provide an over-the- top (OTT) service, the host comprising:
  • processing circuitry configured to provide user data
  • a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A or General Group embodiments to transmit the user data to the host.
  • UE user equipment
  • the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data
  • the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • B24 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: [0172] at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A or General Group embodiments to transmit the user data to the host.
  • UE user equipment
  • Figure 1 shows an example architecture of a satellite network with bent pipe transponders (i.e., the transparent payload architecture).
  • Figure 2 depicts a satellite orbit fully described using 6 parameters.
  • Figure 3 illustrates an NB-IoT SIB Type-x (SIBxNB) transmission and related parameter ranges for repetition pattern within an SI window, the duration of SI window and the periodicity of SI window.
  • SIBxNB SIB Type-x
  • Figure 4 shows an example of a communication system 400 in accordance with some embodiments.
  • Figure 5 shows a UE 500 in accordance with some embodiments.
  • the UE 500 may be an embodiments of the device shown communicating with the satellite in FIG. 1.
  • Figure 6 shows a network node 600 in accordance with some embodiments.
  • Figure 7 is a block diagram of a host 700, which may be an embodiment of the host
  • Figure 8 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized.
  • Figure 9 shows a communication diagram of a host 902 communicating via a network node 904 with a UE 906 over a partially wireless connection in accordance with some embodiments.
  • Figure 10 is a flowchart of a method 1000, according to some embodiments.
  • Figure 11 is a flowchart of a method 1100, according to some embodiments.
  • NTN SIB is beneficial to allow SIB accumulation over those windows to overcome poor coverage. However, if one or more of the NTN SIBs in the accumulated SI windows are different, it may lead to a decoding error and accumulation should be avoided.
  • the content of the NTN SIB(s) is partly dynamic (e.g., the ephemeris data and the Common TA parameters), which is thus problematic when SIB accumulation is needed, e.g., for sufficiently good reception at the cell edge.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the proposed solutions provide methods to facilitate accumulation of NTN- specific SIBs across multiple SI windows for NTN UEs in poor coverage while avoiding decoding errors due to NTN-specific SIB accumulation.
  • SIB accumulation refers to accumulating NTN-specific SIB (which contains satellite ephemeris and/or other assistance information for NTN; and also referred to as NTN SIB) across one or more SI windows.
  • the UE behavior with regards to accumulation of other legacy SIBs That is, the UE might as well accumulate other SIBs as done in terrestrial networks.
  • Example 4 SIB accumulation is prohibited if the SI periodicity exceeds the NTN SIB broadcast periodicity, and/or the number of repetitions configured for the SIBs exceed a certain value.
  • the UE may determine these periodicities and repetition pattern from system information, and then determine if it is allowed to accumulate the NTN SIB or not.
  • one or more of the SI configuration parameters are used by the UE to determine whether NTN SIB accumulation is allowed.
  • the SI periodicity is used by the UE to determine whether NTN SIB accumulation is allowed.
  • SI configuration parameters values for which NTN SIB accumulation is possible can be fixed and specified in the specification, and/or this can be left up to UE implementation.
  • the network may indicate whether or not the UE may use SI configuration parameters to determine if it can accumulate NTN SIB.
  • the UE determines whether or not it is feasible to accumulate NTN SIB by using SI configuration parameters along with other parameters such as the remaining service time before the NTN cell changes (T_service), the satellite orbit or constellation type, satellite beam type (earth-fixed or moving), the previous ephemeris validity timer value stored in the UE, and/or whether it has successfully used NTN SIB accumulation in previous attempt(s), whether it is an NB-IoT or an eMTC UE, epoch time indication range (and/or whether it is indicated in the past or the future), etc.
  • SI configuration parameters such as the remaining service time before the NTN cell changes (T_service), the satellite orbit or constellation type, satellite beam type (earth-fixed or moving), the previous ephemeris validity timer value stored in the UE, and/or whether it has successfully used NTN SIB accumulation in previous attempt(s), whether it is an NB-IoT or an eMTC UE, epoch time indication range (and/or whether it is indicated in
  • one or more of the SI configuration parameters are used by the UE to determine whether NTN SIB accumulation should be performed. For example, if the network does not explicitly indicate information to allow or prohibit NTN SIB accumulation in a cell and leaves it up to the UE to decide, the UE may use SI configuration parameter values to decide if it should accumulate NTN SIBs across SI windows.
  • the SI periodicity is used by the UE to determine whether NTN SIB accumulation should be performed.
  • epoch time is explicitly signalled in the NTN SIB. Even if the ephemeris, the common TA parameters, the validity timer duration and the epoch time remain unchanged, it is the epoch time indication range that will determine how long the can the NTN SIB be transmitted unchanged before it needs to be updated. For example, if the epoch time indication range is 5.12 sec (or 10.24 sec), the time period over which the NTN SIB content may remain unchanged will be up to 5.12 sec (or 10.24 sec). After this time, the contents may need to be updated to correspond to the new epoch time (unless there is additional signalling introduced in the SI to assist the decoding process).
  • NTN SIB Depending on the NTN scenario, it is up to the network how frequently it transmits and updates the NTN SIB. Based on the parameter values for the SI configuration and the validity timer, we analyze the potential scenarios where NTN SIB accumulation may be feasible.
  • Table for eMTC and Table for NB-IoT we observe that there are many combinations of the SI periodicity and the UL synchronization validity timer duration for which the ephemeris is expected to remain unchanged.
  • the smaller validity timer values mainly apply to LEO scenarios whereas the larger validity timer values are for GEO scenarios. Since eMTC supports a much smaller SI periodicity than NB-IoT, the NTN SIB can be transmitted more frequently in eMTC than in NB-IoT.
  • the number of possible NTN SIB that can be accumulated are roughly given by the first row (regardless of the validity timer) assuming an indication range of 5.12 sec; or the first row second row assuming an indication range of 10.24 sec (and a validity timer of 5 sec), or the second row assuming an indication range of 10.24 sec (and a validity timer of 10 sec or higher).
  • SI periodicity value can be used to determine whether or not the UE should accumulate the NTN SIB. Based on the results in the above tables, in one instance, [0217] if it exceeds 64 radio frames, the loT NTN UE may assume that NTN SIB accumulation is not allowed. There is no additional signalling needed in this case as SI periodicity will be signalled by the network anyways which is all the UE needs to decide whether to accumulate NTN SIB.
  • NTN SIB accumulation in eMTC NTN is allowed for the following SI periodicities: ⁇ 8, 16, 32, 64 ⁇ frames.
  • NTN SIB accumulation in eMTC NTN is allowed for the following SI periodicities: ⁇ 8, 16, 32 ⁇ frames.
  • NTN SIB accumulation in NB-IoT NTN is allowed for the following SI periodicities: ⁇ 64 ⁇ frames.
  • the mentioned SI periodicities can be specified in the specification and/or optionally indicated by the network in System Information (other than the NTN SIBs).
  • NTN SIB accumulation is left up to UE implementation.
  • the UE may decide based on the epoch timer indication range, and number of SI windows to decide whether to attempt NTN SIB accumulation.
  • the network indicates it in the SI (other than the NTN SIB) if it using implicit or explicit epoch time indication, e.g., using a 1-bit field in SIB I.
  • the UE can infer based on the parameter signalled if the network is using implicit epoch time or explicit epoch time.
  • NTN SIB may still accumulate and attempt to decode the NTN SIBs if the validity timer is updated in a predictable manner. For instance, if the SI periodicity is 5.12 seconds and the UE determines it can accumulate NTN SIBs, and it attempts to decode using 2 NTN SIBs, it can assume that the validity timer in the second SIB is ⁇ 5 seconds smaller than the first NTN SIB. Since it is aware of the validity timer bits that are different in the two NTN SIBs, it can incorporate this information while combining the two SIBs.
  • the network may indicate in SI whether or not the validity timer indicated in the NTN SIB can be assumed to be constant for NTN SIB accumulation.
  • the validity timer value will change for each SIB according to the validity timer granularity and SI periodicity, even if other content of the NTN SIB remains unchanged.
  • the network uses implicit epoch time indication, it is assumed that the validity timer value will remain unchanged if other content of the NTN SIB remains unchanged.
  • the network uses explicit epoch time indication, it is assumed that the validity timer value will change for each SIB according to the validity timer granularity and SI periodicity, even if other content of the NTN SIB remains unchanged.
  • the satellite orbit determines whether the validity timer indicated in the NTN SIB can be assumed to be constant for NTN SIB accumulation, where this rule can be defined in a specification.
  • the UE may opportunistically attempt to decode the NTN SIB by accumulating across SI windows on a trial-and-error basis. It may also use orbit prediction algorithms or other side information such as uplink synchronization validity timer values or previously acquired satellite ephemeris/common TA parameters to estimate how frequently the satellite ephemeris/common TA etc. will be updated by the network. Then, it can attempt to accumulate the NTN SIB in SI windows which fall within its estimated duration during which the NTN SIB content is expected to remain unchanged.”
  • NTN SIB accumulation regardless of whether the UE has any prior information about NTN SIB decoding.
  • the UE may blindly attempt to accumulate NTN SIBs for decoding purposes even if the network has not indicated any information to assist the UE in deciding whether to accumulate NTN SIBs and/or when to start/stop accumulating NTN SIBs.
  • the UE may use additional information about coverage to aid this decoding process. For example, if the UE can estimate the number of NTN SIBs “X” that it may need to accumulate based on the previous successful acquisition of NTN SIBs or of SIBs other than the NTN SIB, and/or other information related to coverage such as RSRP/RSRQ levels, and/or SI configuration parameters.
  • the UE may begin the decoding process with its assessment of “X” and only combine up to X SI windows or at least X SI windows. If its decoding attempts fail, it may increment the number X until successful decoding.
  • the UE adopts a “sliding window” approach while receiving and combining NTN SIBs for decoding, i.e., the set of “K” NTN SIBs is updated by removing older SIBs and adding newer SIBs if the UE has had a certain number of unsuccessful attempts with decoding using older SIB.
  • the UE may try out combining the first and the second or the second and the third NTN SIBs but these attempts would also fail. Finally, it can attempt to combine all the three SIBs. If this attempt is unsuccessful, UE may flush out the first NTN SIB and acquire another NTN SIB (which will be the third NTN SIB) and attempt to decode with this set of three NTN SIBs. If still unsuccessful, the UE can again remove the first NTN SIB and add a new NTN SIB. If still unsuccessful, the UE may increment X by 1 and restart the entire procedure.
  • the UE may flush out the older NTN SIBs that it had stored for accumulation, e.g., to free memory to stored additional NTN SIBs.
  • the UE may test additional hypothesis depending on whether it assumed the validity timer transmitted in the NTN SIB to remain unchanged (if other SIB content remain unchanged) or not.
  • the SIB accumulation described in this document targets a specific NTN SIB, which is either the NTN SIB needed for uplink synchronization (SystemInformationBlockType31) or the NTN SIB used for discontinuous coverage (SystemInformationBlockType32). This can be specified and/or additionally indicated to the UE. Alternatively, SIB accumulation information is applicable to both NTN SIBs.
  • Figure 4 shows an example of a communication system 400 in accordance with some embodiments.
  • the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408.
  • the access network 404 includes one or more access network nodes, such as network nodes 410a and 410b (one or more of which may be generally referred to as network nodes 410), or any other similar 3 rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points.
  • 3GPP 3 rd Generation Partnership Project
  • 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.
  • network nodes include disaggregated implementations or portions thereof.
  • the telecommunication network 402 includes one or more Open-RAN (ORAN) network nodes.
  • An ORAN network node is a node in the telecommunication network 402 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 402, including one or more network nodes 410 and/or core network nodes 408.
  • ORAN Open-RAN
  • 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).
  • a near-real time control application e.g., xApp
  • rApp non-real time control application
  • 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.
  • an ORAN access node may be a logical node in a physical node.
  • an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized.
  • 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 0-RAN Alliance or comparable technologies.
  • the network nodes 410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 412a, 412b, 412c, and 412d (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections.
  • UE user equipment
  • 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.
  • the communication system 400 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 400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 412 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 410 and other communication devices.
  • the network nodes 410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 412 and/or with other network nodes or equipment in the telecommunication network 402 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 402.
  • the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. 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 406 includes one more core network nodes (e.g., core network node 408) 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 408.
  • 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 (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and/or the telecommunication network 402, and may be operated by the service provider or on behalf of the service provider.
  • the host 416 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 conditions detected 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.
  • the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts.
  • 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.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G wireless local area network
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Micro
  • the telecommunication network 402 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunications network 402 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.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 412 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • 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).
  • MR-DC multi-radio dual connectivity
  • the hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412c and/or 412d) and network nodes (e.g., network node 410b).
  • the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 414 may be a broadband router enabling access to the core network 406 for the UEs.
  • the hub 414 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 414 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.
  • the hub 414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 414 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
  • the hub 414 may have a constant/persistent or intermittent connection to the network node 410b.
  • the hub 414 may also allow for a different communication scheme and/or schedule between the hub 414 and UEs (e.g., UE 412c and/or 412d), and between the hub 414 and the core network 406.
  • the hub 414 is connected to the core network 406 and/or one or more UEs via a wired connection.
  • the hub 414 may be configured to connect to an M2M service provider over the access network 404 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection.
  • the hub 414 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 410b.
  • the hub 414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 5 shows a UE 500 in accordance with some embodiments.
  • the UE 500 may be an embodiments of the device shown communicating with the satellite in FIG. 1 via the access link.
  • 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), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehiclemounted 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.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X).
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • 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).
  • 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).
  • the UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input/output interface 506, a power source 508, a memory 510, a communication interface 512, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 5. 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.
  • the processing circuitry 502 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 510.
  • the processing circuitry 502 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.
  • the processing circuitry 502 may include multiple central processing units (CPUs).
  • the input/output interface 506 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 500.
  • 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.
  • USB Universal Serial Bus
  • the power source 508 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 508 may further include power circuitry for delivering power from the power source 508 itself, and/or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 508.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied.
  • the memory 510 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.
  • the memory 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516.
  • the memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems.
  • the memory 510 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.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • eUICC embedded UICC
  • iUICC integrated UICC
  • SIM card removable UICC commonly known as ‘SIM card.’
  • the memory 510 may allow the UE 500 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 510, which may be or comprise a device-readable storage medium.
  • the processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512.
  • the communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522.
  • the communication interface 512 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 518 and/or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., antenna 522) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 512 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.
  • GPS global positioning system
  • 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/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/intemet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 512, 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).
  • 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.
  • the states of the actuator, the motor, or the switch may change.
  • 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.
  • 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.
  • 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal-
  • AR Augmented Reality
  • VR
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such 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 3 GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • 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.
  • 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.
  • 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.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG. 6 shows a network node 600 in accordance with some embodiments.
  • the network node 600 may be included in embodiments of the satellite shown in FIG. 1.
  • 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.
  • 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, 0-DU, O-CU).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • O-RAN nodes e.g., O-RU, 0-DU, O-CU.
  • 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).
  • DAS distributed antenna system
  • 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), base transceiver 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).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 600 includes a processing circuitry 602, a memory 604, a communication interface 606, and a power source 608.
  • the network node 600 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.
  • the network node 600 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs).
  • the network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, 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 600.
  • RFID Radio Frequency Identification
  • the processing circuitry 602 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 600 components, such as the memory 604, to provide network node 600 functionality.
  • the processing circuitry 602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of radio frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the radio frequency (RF) transceiver circuitry 612 and the baseband processing circuitry 614 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 transceiver circuitry 612 and baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 602 includes one or more of radio frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614.
  • the radio frequency (RF) transceiver circuitry 612 and the baseband processing circuitry 614 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
  • the memory 604 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 computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 602.
  • 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
  • the memory 604 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 602 and utilized by the network node 600.
  • the memory 604 may be used to store any calculations made by the processing circuitry 602 and/or any data received via the communication interface 606.
  • the processing circuitry 602 and memory 604 is integrated.
  • the communication interface 606 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 606 comprises port(s)/terminal(s) 616 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 606 also includes radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610. Radio front-end circuitry 618 comprises filters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to an antenna 610 and processing circuitry 602. The radio front-end circuitry may be configured to condition signals communicated between antenna 610 and processing circuitry 602.
  • the radio front-end circuitry 618 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 618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 620 and/or amplifiers 622.
  • the radio signal may then be transmitted via the antenna 610.
  • the antenna 610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 618.
  • the digital data may be passed to the processing circuitry 602.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 600 does not include separate radio front-end circuitry 618, instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612, as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).
  • the antenna 610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 610 may be coupled to the radio front-end circuitry 618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 610 is separate from the network node 600 and connectable to the network node 600 through an interface or port.
  • the antenna 610, communication interface 606, and/or the processing circuitry 602 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 610, the communication interface 606, and/or the processing circuitry 602 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.
  • the power source 608 provides power to the various components of network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein.
  • the network node 600 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 608.
  • the power source 608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 600 may include additional components beyond those shown in Figure 6 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.
  • the network node 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600.
  • FIG. 7 is a block diagram of a host 700, which may be an embodiment of the host 416 of Figure 4, in accordance with various aspects described herein.
  • the host 700 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 700 may provide one or more services to one or more UEs.
  • the host 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a network interface 708, a power source 710, and a memory 712.
  • processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a network interface 708, a power source 710, and a memory 712.
  • 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 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of host 700.
  • the memory 712 may include one or more computer programs including one or more host application programs 714 and data 716, which may include user data, e.g., data generated by a UE for the host 700 or data generated by the host 700 for a UE.
  • Embodiments of the host 700 may utilize only a subset or all of the components shown.
  • the host application programs 714 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., FLAC, 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 714 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.
  • the host 700 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 714 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.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 8 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • 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 800 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.
  • VMs virtual machines
  • the virtualization environment 800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
  • Applications 802 (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.
  • Hardware 804 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 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 808a and 808b (one or more of which may be generally referred to as VMs 808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808.
  • the VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 806.
  • a virtualization layer 806 Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, 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.
  • NFV network function virtualization
  • a VM 808 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 808, and that part of hardware 804 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.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 808 on top of the hardware 804 and corresponds to the application 802.
  • Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 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 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 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.
  • hardware 804 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.
  • some signaling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 9 shows a communication diagram of a host 902 communicating via a network node 904 with a UE 906 over a partially wireless connection in accordance with some embodiments.
  • host 902 Like host 700, embodiments of host 902 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 902 also includes software, which is stored in or accessible by the host 902 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 906 connecting via an over-the-top (OTT) connection 950 extending between the UE 906 and host 902.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 950.
  • the network node 904 includes hardware enabling it to communicate with the host 902 and UE 906.
  • the connection 960 may be direct or pass through a core network (like core network 406 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 406 of Figure 4
  • one or more other intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 906 includes hardware and software, which is stored in or accessible by UE 906 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 906 with the support of the host 902.
  • 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 906 with the support of the host 902.
  • an executing host application may communicate with the executing client application via the OTT connection 950 terminating at the UE 906 and host 902.
  • 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 950 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
  • the OTT connection 950 may extend via a connection 960 between the host 902 and the network node 904 and via a wireless connection 970 between the network node 904 and the UE 906 to provide the connection between the host 902 and the UE 906.
  • the connection 960 and wireless connection 970, over which the OTT connection 950 may be provided, have been drawn abstractly to illustrate the communication between the host 902 and the UE 906 via the network node 904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 902 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 906.
  • the user data is associated with a UE 906 that shares data with the host 902 without explicit human interaction.
  • the host 902 initiates a transmission carrying the user data towards the UE 906.
  • the host 902 may initiate the transmission responsive to a request transmitted by the UE 906.
  • the request may be caused by human interaction with the UE 906 or by operation of the client application executing on the UE 906.
  • the transmission may pass via the network node 904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 912, the network node 904 transmits to the UE 906 the user data that was carried in the transmission that the host 902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 906 associated with the host application executed by the host 902. [0308] In some examples, the UE 906 executes a client application which provides user data to the host 902. The user data may be provided in reaction or response to the data received from the host 902.
  • the UE 906 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 906.
  • the UE 906 initiates, in step 918, transmission of the user data towards the host 902 via the network node 904.
  • the network node 904 receives user data from the UE 906 and initiates transmission of the received user data towards the host 902.
  • the host 902 receives the user data carried in the transmission initiated by the UE 906.
  • One or more of the various embodiments improve the performance of OTT sendees provided to the UE 906 using the OTT connection 950, in which the wireless connection 970 forms the last segment. More precisely, the teachings of these embodiments may improve the OTT connection with respect to data rate, latency, power consumption and thereby provide benefits such as, e.g., reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime.
  • factory status information may be collected and analyzed by the host 902.
  • the host 902 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 902 may store surveillance video uploaded by a UE.
  • the host 902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 902 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.
  • 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.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 902 and/or UE 906.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 950 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 950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 904. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 902.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 950 while monitoring propagation times, errors, etc.
  • computing devices described herein 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 be performed 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.
  • processing circuitry 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.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 10 is a flowchart of a method 1000 for facilitating non- terrestrial network (NTN) system information block (SIB) accumulation.
  • the method 1000 may be performed by a user equipment, such as the UE 500, to facilitate non-terrestrial network (NTN) system information block (SIB) accumulation.
  • the method 1000 may include an operation 1002 of determining, based on one or more system information (SI) configuration parameters, whether NTN SIB accumulation should be performed.
  • the method 1000 may further include an operation 1004 of performing NTN SIB accumulation when the UE determines NTN SIB accumulation should be performed or an operation 1006 of not performing NTN SIB accumulation when the UE determines NTN SIB accumulation should not be performed.
  • additional operations may include determining that the network does not explicitly indicate whether NTN SIB accumulation should be performed and thereafter determining, based on one or more SI configuration parameters, whether NTN SIB accumulation should be performed.
  • the one or more SI configuration parameters may include an SI periodicity value.
  • the one or more SI configuration parameters may include an epoch timer indication range and/or a number of SI windows.
  • the UE 500 may determine whether the network is using explicit or implicit epoch time indication based on one of: an indication in SI other than the NTN SIB; an assumption of explicit epoch time in the absence of an indication of implicit epoch time; an assumption of implicit epoch time in the absence of an indication of explicit epoch time; or an inference based on a parameters signalled in the SI.
  • the one or more parameters may include an validity timer update.
  • Determining, based on the one or more parameters may include determining based on the absence or one or more parameters whether NTN SIB accumulation should be performed.
  • the method 1000 may further include operations of providing user data and forwarding the user data to a host via the transmission to the network node.
  • Figure 11 is a flowchart of a method 1100 performable by a user equipment (UE) to facilitate NTN SIB accumulation.
  • the method 1100 may include an operation 1102 of determining that NTN SIB accumulation should he performed in the absence of an indication from the network to perform NTN SIB accumulation and an operation 1104 of performing NTN SIB accumulation when the UE determines NTN SIB accumulation should be performed.
  • Embodiments of the method 1100 may further include decoding an NTN SIB.
  • Decoding an NTN SIB may include: attempting to decode the NTN SIB; if the attempting to decode the NTN is successful, storing the NTN SIB and receiving and storing an additional NTN SIB in a next SI transmission, and storing the first NTN SIB and receiving and storing the second NTN SIB in the next SI transmission.
  • the method 1100 may further include attempting to decode the additional NTN SIB without combining the NTN SIB and the additional NTN SIB, or attempting to decode the additional NTN SIB by combining the first stored NTN SIB and the second NTN SIB.
  • Certain aspects of the disclosure and their embodiments may provide solutions to these noted challenges or other challenges.
  • methods and systems are provided for facilitating NTN SIB prohibition or accumulation in NTN to allow operation in coverage limited condition and to avoid decoding error when NTN SIB contents change frequently.
  • systems, methods, and signalling are provided to determine if NTN-specific SIB accumulation across SI windows should be allowed in an loT NTN cell.
  • systems, methods, and signalling are provided to support NTN-specific SIB accumulation across SI windows for UEs in an loT NTN cell
  • systems, methods, and signalling are provided for determining epoch time when NTN-specific SIB accumulation across SI windows is supported.
  • Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of facilitating accumulation of NTN-specific SIBs across multiple SI windows for NTN UEs in poor coverage while avoiding decoding errors due to NTN-specific SIB accumulation.
  • SIB accumulation refers to accumulating NTN-specific SIB (which contains satellite ephemeris and/or other assistance information for NTN; and also referred to as NTN SIB) across one or more SI windows.
  • this disclosure is about NTN SIB accumulation and does not alter the defined UE behavior with regards to accumulation of other legacy SIBs. That is, the UE might as well accumulate other SIBs as done in terrestrial networks.
  • NTN SIBs SystemInformationBlockType31 and SystemInformationBlockType32.
  • the techniques and embodiments disclosed herein can be relevant to both types of NTN SIBs as both may update its ephemeris in between SI windows.
  • SIB accumulation for the NTN SIB is allowed or prohibited depending on how frequently the NTN SIB is updated.
  • NTN SIB may need to be updated very frequently for LEO as compared to GEO. Therefore, one may need to prohibit SIB accumulation to avoid decoding error if a UE in LEO NTN accumulates SIB across multiple SI windows where the SIB content is different. However, no such prohibition is needed for GEO and the default UE behavior is to accumulate SIB if needed.
  • NTN SIB accumulation for loT NTN is prohibited for LEO and/or MEO and/or GEO.
  • the prohibition of the NTN SIB accumulation is indirectly described in terms of the validity timer for uplink synchronization configured by the network. This can be fixed in the specification or the network can indicate it to the UE whether or not it needs to determine NTN SIB prohibition based on the NTN validity timer configuration.
  • SIB accumulation is either prohibited or only allowed within a duration less than the validity timer value.
  • this prohibition is only applicable if the UE has already acquired a validity timer configuration value i.e., no prohibition on SIB accumulation when the UE is acquiring the NTN SIB for the first time and/or has not acquired a validity timer value.
  • SIB accumulation is prohibited if the UE has not acquired a validity timer configuration value or if it is acquiring NTN SIB for the first time.
  • the network configures if NTN SIB accumulation is prohibited in an NTN cell and broadcasts it using SI.
  • the SI window configuration e.g., SI window length, SI periodicity, SI repetition pattern
  • certain rules are defined in the specification which along with broadcast information and/or UE measurement(s), allow the UE to determine if NTN SIB accumulation is prohibited.
  • SIB accumulation is prohibited for UEs based on UE category and/or coverage enhancement class and/or NTN scenario type (LEO/MEO/GEO).
  • SIB accumulation is prohibited for NTN UEs in good coverage (when RSRP threshold exceeds a predefined level) when the configured repetitions within the SI window exceed a predefined threshold. Otherwise, it is not prohibited.
  • SIB accumulation is prohibited if the SI periodicity exceeds the NTN SIB broadcast periodicity, and/or the number of repetitions configured for the SIBs exceed a certain value.
  • the UE may determine these periodicities and repetition pattern from system information, and then determine if it is allowed to accumulate the NTN SIB or not.
  • the prohibited SIB accumulation forces the epoch time to not be optional (i.e. it will be mandatorily present in its SIB if SIB accumulation is allowed for this SIB). This is because if epoch time is not signalled, then the epoch time is based on the starting time of the downlink subframe corresponding to the end of the System Information window. So, if SIB accumulation were to happen, there would be confusions regarding where the epoch time should start or not.
  • the above described ambiguity of the epoch time (when the epoch time is not explicitly indicated but defined by a default rule) caused by repetitions of the concerned SIB (e.g., systemInformationBlockType31) with identical content is alleviated by specifying a rule for when the epoch time is defined in conjunction with SIB repetitions.
  • the SIB is configured in the SI, e.g., in SIB1, the SIB is transmitted in sets of N identical SIBs (i.e.
  • the default epoch time is further configured or specified in relation to a specific one of these SIB transmissions or Si-windows.
  • the default epoch time can be the start time of the downlink subframe corresponding to the end of the first Si-window with identical SIB transmissions.
  • the default epoch time can be the start time of the downlink subframe corresponding to the end of the last Si-window with identical SIB transmissions.
  • the default epoch time may be the start of the downlink subframe corresponding to the start of a certain Si-window in a set of Si-windows with identical SIB transmissions.
  • the default epoch time is defined as the start of the transmission - or the end of the transmission - of a certain one of the consecutive transmissions of SI messages containing the concerned SIB with unchanged content.
  • the UE may opportunistically attempt to decode the NTN SIB by accumulating across SI windows on a trial-and-error basis. It may also use orbit prediction algorithms or other side information such as uplink synchronization validity timer values or previously acquired satellite ephemeris/common TA parameters to estimate how frequently the satellite ephemeris/common TA etc. will be updated by the network. Then, it can attempt to accumulate the NTN SIB in SI windows which fall within its estimated duration during which the NTN SIB content is expected to remain unchanged.
  • NTN SIB accumulation is not prohibited, it is the number of SI windows across which NTN SIBs can be accumulated is specified in the standard specification.
  • the network indicates it to the UE the number of SI windows it can accumulate across.
  • a set of NTN specific SI window lengths is specified. It includes the existing SI window lengths, e.g., ⁇ 160, 320, 480, 960, 1280, 1600 ⁇ ms for NB-IoT, and adds to that additional lengths such as 3200 and 6400 ms.
  • the existing SI window length for LTE-M ⁇ 1, 2, 5, 10, 15, 20, 40, 60, 80, 120, 160, 200 ⁇ ms can also be expanded to include additional lengths such as 240, 280, 320 and 360 ms.
  • the network may configure a larger number of repetitions of the NTN SIB within an SI window. It may eliminate the need to accumulate NTN SIB across multiple SI windows, or reduce the number of SI windows that the UE needs to accumulate across in order to correctly decode the NTN SIB.
  • the new SI window lengths are applicable to all SI windows in NTN. Alternatively, it only applies to the SI window containing the NTN SIBs and information about which SI window contains the SI message with NTN SIB can be either specified or indicated to the UE in SI.
  • the existing values in the set for configuring a SI window length are fully or partially re- interpreted as different values for loT NTN scenarios.
  • the values in the set for configuring a SI window length can be different depending on the satellite orbit altitude (e.g., the set of values is different for LEO and GEO satellite orbits).
  • the existing values in the set for configuring the “si- Periodicity” are either fully re-used or new values are added (e.g., longer values are appended) to it for loT NTN scenarios.
  • the existing values in the set for configuring the “si- Periodicity” are fully or partially re-interpreted as different values for loT NTN scenarios.
  • the values in the set for configuring the “si-Periodicity” can be different depending on the satellite orbit altitude (e.g., the set of values is different for LEO and GEO satellite orbits).
  • the existing values in the set for configuring the “si- RadioFrameOffset” are either fully re-used or new values are added (e.g., longer values are appended) to it for loT NTN scenarios.
  • the existing values in the set for configuring the “si- RadioFrameOffset” are fully or partially re-interpreted as different values for loT NTN scenarios.
  • the values in the set for configuring the “si- RadioFrameOffset” can be different depending on the satellite orbit altitude (e.g., the set of values is different for LEO and GEO satellite orbits).
  • the existing values in the set for configuring the “si- RepetitionPattem” are either fully re-used or new values are added (e.g., longer values are appended) to it for loT NTN scenarios.
  • the existing values in the set for configuring the “si- RepetitionPattem” are fully or partially re-interpreted as different values for loT NTN scenarios.
  • the values in the set for configuring the “si- RepetitionPattem” can be different depending on the satellite orbit altitude (e.g., the set of values is different for LEO and GEO satellite orbits).
  • the network uses one or more of the following methods to indicate one or more of the aforementioned information to the UEs in an NTN cell.
  • the network may indicate 1-bit information about SIB accumulation prohibition using
  • SIB other than the NTN SIB e.g., in SIB1, e.g., in the SI scheduling information
  • Different SLRNTI is defined and specified to indicate NTN SIB accumulation is allowed in addition to the existing SI-RNTI. This enables selectively allowing accumulation per SI message (and thus SIB selective) and may also be dynamically changed between SI message transmissions and Si-windows.
  • the SIB accumulation targets a specific NTN SIB, which is either the NTN SIB needed for uplink synchronization (SystemInformationBlockType31) or the NTN SIB used for discontinuous coverage (SystemInformationBlockType32). This can be specified and/or additionally indicated to the UE. Alternatively, SIB accumulation information is applicable to both NTN SIBs.
  • the number of repeated SIB transmissions (of a certain SIB, e.g., an NTN SIB such as systemInformationBlockType31 or systemInformationBlockType32) can be configured and signaled in another SIB, preferably a SIB in which the content is static, or semi-static, so that the UE can apply SIB accumulation for that SIB without restrictions.
  • a certain SIB e.g., an NTN SIB such as systemInformationBlockType31 or systemInformationBlockType32
  • SIB preferably a SIB in which the content is static, or semi-static
  • the indication would first of all consist of an indication of the number, N, of consecutive SIB transmission without update of the content (i.e. the number of identical repeated SIB transmissions).
  • the transmissions of the concerned SIB will thus be transmitted in repeated sets of N identical transmissions (i.e. with unchanged content). There would hence be a set of N transmissions of the unchanged SIB, followed by another set of N identical SIB transmissions, where updates of the SIB content can only occur between two sets.
  • the N identical transmissions would be followed by a potentially updated transmission, which marks the first transmission of another set of N identical SIB transmissions.
  • the configuration parameter N indicates the number of consecutive identical transmissions of the concerned SIB.
  • N is not indicated in the SI but is specified in a standard specification.
  • different N values may be specified for different network deployment scenarios, e.g., for LEO, MEO, GEO and HAPS/HIBS deployments.
  • N is configured in the USIM, e.g., when the USIM (e.g., on a SIM card) is provisioned, or configured in the USIM using Over-The-Air (OTA) configuration.
  • OTA Over-The-Air
  • the reference for the start of a set of N identical SIB transmission or a set of N Si-windows (in which the SI message containing the concerned SIB is transmitted) the concerned SIB will be unchanged, is configured in the system information, e.g., in SIB1.
  • the network does not necessarily need to send a different SIB after “N” identical transmissions.
  • it may send the same SIB in the next “N” transmissions but as far as the UE behavior is concerned, UE will assume that SIB content can be potentially different after the “N” transmissions and that it should refrain from accumulating SIBs other than the indicated “N” transmissions.
  • TR 38.821 Solutions for NR to support non-terrestrial networks, 3GPP, 16.1.0, June 2021.
  • RP-211601 NB-IoT/eMTC support for Non-terrestrial Networks (NTN), RAN#92-e, Jun
  • NTN Non-Terrestrial Networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Sont divulgués des procédés, des systèmes et des dispositifs qui facilitent l'accumulation de SIB NTN. Par exemple, un procédé mis en œuvre par un équipement utilisateur (UE) pour faciliter l'accumulation de blocs d'informations système non terrestres (SIB NTN), le procédé consiste à déterminer, sur la base d'un ou de plusieurs paramètres de configuration d'informations système (SI), si une accumulation de SIB NTN doit être effectuée ; et à effectuer une accumulation de SIB NTN lorsque l'UE détermine qu'une accumulation de SIB NTN doit être effectuée ou ne pas effectuer une accumulation de SIB NTN lorsque l'UE détermine qu'une accumulation de SIB NTN ne doit pas être effectuée.
PCT/US2023/030170 2022-08-12 2023-08-14 Procédés d'accumulation de si dans un ntn ido avec indication de temps d'époque explicite et implicite Ceased WO2024035965A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202380072100.2A CN120019591A (zh) 2022-08-12 2023-08-14 用于具有显式和隐式历元时间指示的iot ntn中的si累积的方法

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263397657P 2022-08-12 2022-08-12
US63/397,657 2022-08-12

Publications (1)

Publication Number Publication Date
WO2024035965A1 true WO2024035965A1 (fr) 2024-02-15

Family

ID=87974545

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/030170 Ceased WO2024035965A1 (fr) 2022-08-12 2023-08-14 Procédés d'accumulation de si dans un ntn ido avec indication de temps d'époque explicite et implicite

Country Status (2)

Country Link
CN (1) CN120019591A (fr)
WO (1) WO2024035965A1 (fr)

Non-Patent Citations (11)

* Cited by examiner, † Cited by third party
Title
"NB-IoT/eMTC support for Non-terrestrial Networks (NTN", RP-211601, June 2021 (2021-06-01)
"Solutions for NR to support non-terrestrial networks (NTN", RP-193234
"Study on NB-IoT/eMTC support for Non-terrestrial Network, RAN#90", RP-202689, December 2020 (2020-12-01)
"Study on New Radio (NR) to support non-terrestrial networks", TR 38.811
"Support of Non-Terrestrial Network in NB-IoT and eMTC", R2-2203810
3GPP TR 38.811
3GPP TR 38.821
3GPP: "Solutions for NR to support non-terrestrial networks", TR 38.821, June 2021 (2021-06-01)
3GPP: "Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN", TR 36.763, June 2021 (2021-06-01)
ERICSSON: "On SIB accumulation and Timing relationship enhancements in IoT NTN", vol. RAN WG1, no. Toulouse, France; 20220822 - 20220826, 16 August 2022 (2022-08-16), XP052275614, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_110/Docs/R1-2207683.zip R1-2207683 On SIB accumulation and Timing relationship enhancements in IoT NTN.docx> [retrieved on 20220816] *
RP-193235, vol. Study on NB-Io/eMTC support for Non-Terrestrial Ne

Also Published As

Publication number Publication date
CN120019591A (zh) 2025-05-16

Similar Documents

Publication Publication Date Title
US20250097811A1 (en) Systems and methods for reducing system information acquisition during cell reselection in a non-terrestrial network
WO2023014271A1 (fr) Validité de données de système mondial de navigation par satellite dans des réseaux non terrestres
US20250142505A1 (en) Method and Apparatus for SSB Measurement Time Configuration in Communication Network
US20250113277A1 (en) Systems and methods for time-based handover in non-terrestrial networks
US20250159654A1 (en) Paging and system information (si) procedures under adjusted synchronization signal block measurement time configuration (smtc) in non-terrestrial networks (ntn)
US20250184854A1 (en) Systems and methods for time-based triggered handover in non-terrestrial networks
EP4569947A1 (fr) Procédés, appareil et supports lisibles par ordinateur pour déterminer une avance temporelle dans un réseau non terrestre
US20240406760A1 (en) Minimization of Drive Testing for Non-Terrestrial Networks
US20250287461A1 (en) Ephemeris data for conditional handover
WO2024035301A1 (fr) Informations d&#39;emplacement pour mobilité en ntn
WO2023213984A1 (fr) Configuration de l&#39;ue pour le transfert temporel dans un réseau sans fil tel qu&#39;un réseau non terrestre
WO2023096556A1 (fr) Systèmes et procédés pour la prise en charge de l&#39;ajustement autonome d&#39;une avance temporelle
WO2023086001A1 (fr) Systèmes et procédés pour faciliter une longue transmission en liaison montante dans des réseaux non terrestres de l&#39;internet des objets
WO2025037179A1 (fr) Mécanismes pour la prise en charge d&#39;une commutation de liaison satellite ou de liaison de connexion avec une fréquence porteuse et pci inchangées
US20250203426A1 (en) Reporting of NTN-Related SON Information
WO2023152302A1 (fr) Accès à un réseau non terrestre
US20250261092A1 (en) Systems and methods for system information accumulation in internet of things non-terrestrial networks
WO2024035965A1 (fr) Procédés d&#39;accumulation de si dans un ntn ido avec indication de temps d&#39;époque explicite et implicite
US20250133522A1 (en) Systems and methods to facilitate long uplink transmission in internet of things non-terresterial networks
US12487366B2 (en) Methods and systems for signalling ephemeris data in a non-terrestrial network
WO2025177172A1 (fr) Modification d&#39;avance temporelle pour réseaux non terrestres
WO2025210593A1 (fr) Indication de stockage et de transfert pour ntn
WO2025066731A1 (fr) Procédés, dispositifs et support de transfert intercellulaire
WO2024171139A1 (fr) Activation d&#39;intervalles de mesure pour ntn
WO2024176171A1 (fr) Procédés de chaîne cho dans ntn

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23768037

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 202380072100.2

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 202380072100.2

Country of ref document: CN

122 Ep: pct application non-entry in european phase

Ref document number: 23768037

Country of ref document: EP

Kind code of ref document: A1