[go: up one dir, main page]

WO2025153889A1 - Transfert de ntn à l'aide de diagrammes de sauts de faisceau - Google Patents

Transfert de ntn à l'aide de diagrammes de sauts de faisceau

Info

Publication number
WO2025153889A1
WO2025153889A1 PCT/IB2024/063138 IB2024063138W WO2025153889A1 WO 2025153889 A1 WO2025153889 A1 WO 2025153889A1 IB 2024063138 W IB2024063138 W IB 2024063138W WO 2025153889 A1 WO2025153889 A1 WO 2025153889A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran node
beams
node
cells
cell
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.)
Pending
Application number
PCT/IB2024/063138
Other languages
English (en)
Inventor
Angelo Centonza
Ioannis Xirouchakis
Johan Rune
Xiaotian FU
Serban Purge
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
Publication of WO2025153889A1 publication Critical patent/WO2025153889A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18539—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection
    • H04B7/18541—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection for handover of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/083—Reselecting an access point wherein at least one of the access points is a moving node
    • 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 relates to a wireless network having Non-Terrestrial Network (NTN) components and, more specifically, to beam-hopping in such a wireless network.
  • NTN Non-Terrestrial Network
  • FIG. 1 illustrates a Non-Terrestrial Network (NTN) system.
  • NTN Non-Terrestrial Network
  • An NTN system is wireless network that has an NTN component.
  • the NTN component uses a constellation of several satellites (e.g., Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geosynchronous Orbit (GEO) satellites, etc.) that orbit Earth using one or more orbit planes.
  • LEO Low-Earth Orbit
  • MEO Medium-Earth Orbit
  • GEO Geosynchronous Orbit
  • Each satellite provides wireless network access to User Equipments (UEs) positioned on, or near, the Earth's surface via a respective service link. This is done by satellites having on-board antennas that can radiate beams towards (multiple) centers of Earth-Fixed Cells (EFCs).
  • EFCs Earth-Fixed Cells
  • NGEO non-geostationary satellite orbits
  • different EFCs will be served by different beams at different times.
  • the transition from one beam to another is called a beam-switch, or beam hand-over.
  • This can be caused due to the service link switch, i.e., beams come from a different satellite, or a feeder link switch, i.e., beams come from the same satellite, but the data carried within the beams are from gateways located in different geographic areas.
  • the beam-switch there is a period where beams overlap in time to allow UEs to hand-over from one beam to another.
  • a beamswitch due to service link hand-over is shown in Figure 2.
  • beam manager The entity that controls the beam-switch procedure is referred to herein as "beam manager", and it should have the information of the position of the satellites, the gateways, and the EFCs.
  • the actual implementation and location of the beam manager is irrelevant within present disclosure.
  • the end receiver of the beam activation/de- activation commands is the satellite antenna which needs to comply with these commands.
  • Figure 3 illustrates an example of beam activation/de-activation time evolution for a specific EFC.
  • Figure 4 illustrates an example of beam time division multiplexing (beam-hopping). Each beam-hopping pattern is applied in different time slots over different cells.
  • TN Terrestrial Network
  • NTN nodes and satellite antennas are required to provide coverage over an area of thousands of square kilometers (km 2 ). This means that the population spread of cells covered by the same satellite can be extreme, going from almost no users (e.g., remote areas such as sea, mountains, forests, etc.) up to thousands of users (e.g., urban areas when NTN is required to provide coverage in emergency scenarios). This population imbalance between NTN cells will result in a similar traffic load imbalance.
  • Beam-hopping is a method that can reduce this load imbalance by assigning more DL/UL beam illumination time slots to cells that require more traffic, and less time slots to cells with limited traffic.
  • NTN Non-Terrestrial Network
  • a method performed by a node the node being either a User Equipment (UE) or a first a Radio Access Network (RAN) node of a wireless network comprising one or more NTN components comprising receiving, from a second RAN node of the wireless network, beam pattern information for one or more cells or beams and performing one or more actions based on the beam pattern information.
  • UE User Equipment
  • RAN Radio Access Network
  • the beam pattern information comprises information that indicates an on/off schedule of the cell or beam.
  • the node is a first RAN node and the first RAN node is a target RAN node for a handover of a UE, and the second RAN node is a source RAN node for handover of the UE.
  • the one or more cells or beams for which the beam pattern information is received comprise one or more cells operated by the second RAN node.
  • receiving the beam pattern information comprises receiving the beam pattern information from the second RAN node within a handover request, during handover preparation, or before handover preparation.
  • the method further comprises receiving, from the second RAN node, neighbor cell relation information comprising information that indicates cell(s) or beam(s) operated by the first RAN node that are neighbors to the one or more cells or beams operated by the second RAN node for which the beam pattern information is received.
  • performing the one or more actions based on the beam pattern information comprises selecting a target cell or beam operated by the first RAN node for a handover of a UE from one of the one or more cells or beams operated by the second RAN node.
  • the one or more actions further comprise applying a new beam pattern to a selected target cell or beam operated by the first RAN node, the selected target cell or beam being a target cell or beam for handover of a UE from one of the one or more cells operated by the second RAN node.
  • the one or more actions further comprising sending a handover command for the UE to the second RAN node, the handover command comprising information that indicates the target cell or beam and beam pattern information for the target cell or beam.
  • the node is a first RAN node
  • the first RAN node is a source RAN node for a handover of a UE
  • the second RAN node is a target RAN node for handover of the UE.
  • the one or more cells or beams for which the beam pattern information is received comprise one or more cells operated by the second RAN node.
  • the one or more actions comprise selecting a target cell or beam for the handover of the UE from among the one or more cells operated by the second RAN node, based on the beam pattern information.
  • the one or more actions further comprises generating and sending a handover request to the second RAN node, the handover request comprising information that identifies the selected target cell or beam operated by the second RAN node.
  • the node is a UE, and the one or more cells or beams for which the beam pattern information is received comprise one or more cells operated by the second RAN node.
  • the second RAN node is a target RAN node that operates a target cell or beam for a handover of the UE.
  • the one or more actions comprise delaying execution of the handover command until a time at which the target beam or cell is active, as indicated by the beam pattern information.
  • the second RAN node is a serving RAN node of the UE.
  • the beam pattern information further comprises beam pattern information for one or more neighbor cells or beams of a serving cell or beam of the UE.
  • the method further comprises receiving, from the second RAN node, measurement configuration information that configures the UE to perform measurements on at least one of the one or more neighbor cells or beams, wherein performing the one or more actions comprises performing at least one measurement on the at least one of the one or more neighbor cells or beams in accordance with the measurement configuration information and taking into consideration the beam pattern information for the at least one of the one or more neighbor cells or beams.
  • the one or more actions further comprises sending a measurement report to the second RAN node, the measurement report comprising the at least one measurement performed on the at least one of the one or more neighbor cells or beams.
  • Embodiments of a method performed by a RAN node of a wireless network are also disclosed.
  • the method performed by the RAN node comprises sending, to either a UE or another RAN node of the wireless network, beam pattern information for one or more cells or beams.
  • a method performed by a RAN node of a wireless network comprises sending to a UE measurement configuration information that configures the UE to perform measurements on one or more neighbor cells or beams, the measurement configuration information comprising one or more time-based aspects related to on/off schedules of the one or more neighbor cells or beams.
  • Figure 8A is a flow chart that illustrates the operation of a node (i.e., a UE or a RAN node) in accordance with at least some of the embodiments described herein;
  • a node i.e., a UE or a RAN node
  • Figure 10 illustrates the operation of a serving RAN node of a UE in accordance with related embodiments described herein;
  • Figure 11 illustrates the operation of a LIE in accordance with some embodiments of the present disclosure;
  • Figure 12 shows an example of a communication system in accordance with some embodiments of the present disclosure
  • Figure 14 shows a network node in accordance with some embodiments of the present disclosure
  • Figure 15 is a block diagram of a host, which may be an embodiment of the host of Figure 12, in accordance with various aspects of the present disclosure described herein;
  • Figure 16 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.
  • Figure 17 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments of the present disclosure.
  • NTN Non-Terrestrial Network
  • the existing beam-hopping scheme for a NTN system described in the Background section above has consequences resulting from the fact that beams are turned on and off, and consequently the connectivity/service in a certain area comes and goes.
  • a particularly problematic consequence is the impact of the intermittent connectivity/service on handover of a User Equipment (UE) between cells served by different beams.
  • UE User Equipment
  • the source cell and the target cell of a beam hop or handover will not be on/active simultaneously, and there may be a non-negligible time gap between the time that the source cell is turned off and the time that the target cell is turned on. This has significant negative impacts on the performance of the handover, e.g., in terms of connectivity/service interruption time.
  • systems and methods that provide a solution(s) to the aforementioned and/or other challenges are disclosed herein.
  • systems and methods are described based on an exchange of beam pattern information between RAN nodes. By means of exchanging such information, RAN nodes can make better mobility decisions concerning how to select mobility target cells for a given UE.
  • Embodiments of systems and methods disclosed herein enable RAN nodes to be aware of the beam pattern information (i.e., information indicating when in time a beam or cell (also referred to as "beam/cell") is active or not active) of each neighbor cell. With this information, RAN nodes can determine which cell is likely to be active at the time of a handover execution and, by that, they can better select mobility target cells for a UE.
  • beam pattern information i.e., information indicating when in time a beam or cell (also referred to as "beam/cell”
  • embodiments of the present disclosure may provide certain advantages over existing solutions. For example, in systems where beam hopping techniques are used, embodiments of the present disclosure may avoid situations where a UE is moved to target cells that are not active or that are sub-optimal (e.g., due to excessive interference or due to delayed access to the cell due to initial cell deactivation). Therefore, in beam hopping use cases, mobility is performed in full awareness of beam pattern information and can be configured towards cells that will be timely available and in optimal radio conditions at the time of handover execution. By improving the functioning of systems where beam hopping is adopted, embodiments of the solutions described herein may enable beam hopping configurations that lead to considerable energy saving both on network and UEs.
  • Figure 5 illustrates one example of an NTN system 500 in which embodiments of the present disclosure may be implemented.
  • the NTN system 500 includes NTN nodes 502-S and 502-T (e.g., satellites), which are also referred to herein as a source NTN node 502-S and a target NTN node 502-T when referred to within the context of a beam switch or handover.
  • NTN nodes 502-S and 502-T e.g., satellites
  • the NTN node 502-S provides wireless network access to UEs 504 within a cell 506-S (e.g., an Earth-Fixed Cell (EFC)) via a service link provided over a respective NTN node (e.g., satellite) beam(s) (e.g., transmitter beam(s) for downlink (DL) and a receiver beam(s) for uplink (UL)).
  • a cell 506-S e.g., an Earth-Fixed Cell (EFC)
  • EFC Earth-Fixed Cell
  • the cell 506-S is also referred to herein as a source cell 506-S with referred to within the context of a beam switch or handover.
  • the NTN node 502-T provides wireless network access to UEs 504 within a cell 506-T (e.g., an EFC) via a service link provided over a respective NTN node (e.g., satellite) beam(s) (e.g., transmitter beam(s) for downlink (DL) and a receiver beam(s) for uplink (UL)).
  • a respective NTN node e.g., satellite
  • beam(s) e.g., transmitter beam(s) for downlink (DL) and a receiver beam(s) for uplink (UL)
  • the cell 506-T is also referred to herein as a target cell 506-T with referred to within the context of a beam switch or handover.
  • the NTN node 502-S is connected to a gateway 508-S, and the NTN node 502-T is connected to a gateway 508-T.
  • the NTN system 500 also includes RAN nodes 510-S and 510-T, which are also referred to herein as a source RAN node 510-S and a target RAN node 510-T when referred to within the context of a beam switch or handover.
  • the RAN node 510-S may be implemented at the NTN node 502-S, at the gateway 508-S, as a separate network node that is external to and connected to the gateway 508-S.
  • the RAN node 510-S may be implemented in a distributed manner where part of the functionality of the RAN node 510-S is implemented at the NTN node 502-S and part of the RAN node 510-S is implemented at the gateway 508-S and/or at a separate node that is external to and connected to the gateway 508-S.
  • the RAN node 510-T may be implemented at the NTN node 502-T, at the gateway 508-T, as a separate network node that is external to and connected to the gateway 508-T.
  • the RAN node 510-T may be implemented in a distributed manner where part of the functionality of the RAN node 510-T is implemented at the NTN node 502-T and part of the RAN node 510-T is implemented at the gateway 508-T and/or at a separate node that is external to and connected to the gateway 508-T.
  • the RAN nodes 510-S and 510-T are base stations of a cellular communications system (e.g., gNodeBs (gNBs) in the case of 3GPP New Radio (NR)).
  • gNodeBs gNodeBs
  • NR 3GPP New Radio
  • Embodiments of the present disclosure are particularly well-suited to a scenario where two areas are so close to each other that harmful interference would occur if transmissions would occur to/from the areas at the same time.
  • Such an area may be a cell or the footprint of a beam (e.g., the two cells 506-S and 506-T of Figure 5).
  • the 3GPP standard allows a cell to be served (i.e., covered) by one or more beams.
  • the scenario with one beam per cell has been the main focus (which does not preclude multiple beams per cell).
  • the terms "beam” and “cell” are used almost interchangeably in the description provided herein, e.g., sometimes mentioning "cell” when it strictly speaking should be "beam”.
  • beam-hopping pattern/schedule is often mentioned. This may be seen as a time schedule indicating when a beam/cell will be turned on and when it will be turned off.
  • the beam hopping pattern i.e., beam hopping schedule
  • an NTN system (e.g., the NTN system 500 of Figure 5) is able to derive beam-hopping patterns for each cell/beam (e.g., cells 506-S and 506-T or respective beams) and time slot, constructing a two-dimensional beam-hopping matrix of size NxM, where /Vis the number of beams or cells (sometimes referred to herein as "beams/cells") and M ⁇ s the number of time slots.
  • Element (/) j) of the matrix indicates whether cell /will be illuminated (beam-on) or not (beam-off) during time slot j Beam-on is indicated by a logical one, and beam-off is indicated by a logical zero, or vice versa.
  • FIG. 6 is a block diagram of the derivation of the beam-hopping matrix P.
  • the cells/beams considered are those in a list of serving cells, and cells/beams belong to a cluster in which any two cells/beams would interfere harmfully (e.g., above a level deemed as acceptable) if they were active/on at the same time.
  • the construction of matrix P is not the subject of the present disclosure.
  • P is considered herein to be an arbitrary matrix of logical zeros and ones.
  • Each row of matrix P represents the beam on/off decisions for a respective cell/beam for the next M time slots.
  • each bitstream (e.g., gateway 508-S or 508-T) and NTN node or satellite (e.g., NTN node 502-S or NTN 502-T) that this cell is connected to the network, as shown in Figure 7.
  • Figure 7 illustrates transmission of the beam-hopping patterns from matrix Pto the corresponding NTN cells through different gateways and satellites.
  • different beam on/off indicators are required for DL and for UL, i.e., the system designs two P matrices, one for DL and one for UL.
  • each RAN node e.g., each of the RAN nodes 510-S and 510-T of Figure 5
  • a gNB supporting an NTN component signals to another RAN node beam pattern information via a direct node-to- node interface or via an indirect node-to-node interface.
  • Such interface can be a peer-to-peer interface such as the Xn interface or an indirect interface that may, for example, involve forwarding of the information via the core network (e.g., via the 5 th Generation Core (5GC) in the case of a 5 th Generation (5G) system) before reaching the target RAN node, or involving forwarding via an Operations, Administration, and Maintenance (0AM) node or a satellite control center.
  • the core network e.g., via the 5 th Generation Core (5GC) in the case of a 5 th Generation (5G) system
  • 5GC 5 th Generation Core
  • 5G 5 th Generation
  • 5AM Operations, Administration, and Maintenance
  • the RAN node 1 signaling beam pattern information to the RAN node 2 will associate each row of the P matrix to a beam/cell (where each matrix row represents the beam/cell on/off schedule of the beam/cell), which can be identified with a beam/cell identifier, such as a cell global identity (CGI), e.g. a cell global identity of an NR cell (NCGI / NR CGI).
  • CGI cell global identity
  • the RAN node 1 signals the per beam/cell beam pattern information (i.e., the per beam/cell on/off schedule) to RAN node 2 and additionally it may signal the neighbor cell relation between NTN cells served by RAN node 1 and NTN cells served by RAN node 2, wherein the information may, for example, be represented as the following:
  • the information about beam patterns described above, as well as the neighbor cell relation may be signaled from RAN node 2 to RAN node 1 as well, before or during a handover procedure.
  • the Beam Pattern Information may be signaled repetitively.
  • the information described in the table above can be signaled between two RAN nodes at any point in time.
  • this information may be signaled during the setup of an interface between RAN node 1 and RAN node 2, or when the information is updated, or it can be signaled in a message that updates information about RAN node 1 or RAN node 2 configuration, or it can be signaled as part of messages that handle LIE associated signaling, such as the Handover preparation messages.
  • the information is signaled as part of the Handover Preparation signaling, and in particular as part of a Handover Request message from source RAN node (e.g., source RAN node 510-S) to target RAN node (e.g., target RAN node 510-T), the information may be signaled together with information concerning which of the cells of RAN node 1, for which beam pattern information is provided, is the source cell of the UE handover.
  • source RAN node e.g., source RAN node 510-S
  • target RAN node e.g., target RAN node 510-T
  • a cell of RAN node 2 may be reported in the UE measurements received by RAN node 2 as a strong candidate handover target cell, but it may not be suitable as the handover (HO) target because e.g. such cell will not be a neighbor cell of the source RAN node 1 cell at the time the handover will be executed, due to beam patterns followed by the source RAN node 1 cell and the target RAN node 2 cell. For this reason, RAN node 2 uses the information described above received from RAN node 1 to determine, if not known already, to which cell of RAN node 2 the UE will be handed over.
  • HO handover
  • RAN node 2 will deduce which of RAN node 2 cells will be serving the area where the UE will be at the time of handover execution. Namely, the cell serving the area where the UE will be at the time of handover execution depends on the beam pattern of all cells in that neighborhood (namely cells of RAN node 1 and RAN node 2) and RAN node 2 is aware of such beam patterns.
  • This calculation can be done also by taking into account the neighbor relations signaled by RAN node 1 to RAN node 2 and concerning the source cell at RAN node 1.
  • RAN node 1 may signal to RAN node 2 an estimated handover time, namely, a time, calculated in e.g., number of time slots or time in milliseconds or similar, after which the UE will start handover execution towards RAN node 2 target cell(s).
  • a time calculated in e.g., number of time slots or time in milliseconds or similar.
  • RAN node 2 can communicate towards RAN node 1 which cell is the handover target cell.
  • This information can also be included in the HO command generated by RAN node 2 and signaled to the LIE via RAN node 1.
  • RAN node 2 based on the information received from RAN node 1, RAN node 2 is able to determine the cell that will be less interfered at RAN node 2 at the time of handing over the UE to RAN node 2. This is in virtue of knowing the beam pattern information of cells of RAN node 1 and their neighbor relation with the cells of RAN node 2. Hence RAN node 2 can make a decision of which cell to select as handover target cell also based on the interference between cells of RAN node 1 and RAN node 2.
  • neighbor RAN nodes e.g., neighbor gNBs
  • RAN node 510-S and 510-T exchange cell on/off schedules with each other (or are configured with this knowledge), e.g., between RAN nodes serving a certain cluster of cells (and possibly also over cluster borders).
  • the serving RAN node configures the LIE with neighbor cell measurements, and the UE, knowing the on/off schedules of the neighbor cells, measures on each of the neighbor cells (which are part of the measurement configuration) when the neighbor cell is on (according to its on/off schedule) and sends the measurement report (when triggered be a fulfilled condition or in accordance with a configured reporting periodicity) to the serving cell when the serving cell is on (according to the serving cell's on/off schedule). It is possible that the UE measures signals levels of neighbor cells without the configuration of measurement gaps by the source node. In this case the beam patterns for cells of the neighbor RAN node can be used by the UE to decide when to measure neighbor cells.
  • the source RAN node may prepare a time-based Conditional Handover (CHO), wherein the CHO execution time window indicated by the time-based condition (e.g., indicated by the tl-Threshold-rl7 and duration-rl7i s in the ReportConfigNR E) match a suitable on-period (e.g., the next/nearest or currently ongoing on-period) of the (candidate) target cell.
  • the UE executes the CHO towards the (candidate) target cell when the time condition (and any other configured condition) is fulfilled (as in legacy NR NTN).
  • Embodiment 3 involves that during a CHO, the candidate target RAN node may include the on/off schedule of the candidate target cell in a Conditional Handover Command (i.e., the conditional reconfiguration (e.g., the condRRCReconfig- rl6l ).
  • the UE could use this to adapt the timing of the CHO execution (provided that the CHO execution condition(s) is(are) fulfilled), e.g., refine the CHO execution timing within a CHO execution time window defined by the time-based condition (e.g., configured by the tl-Thresho/d-17 and duration-rl 7 IEs in the ReportConfig NR IE) in a time-based CHO configuration.
  • the time-based condition e.g., configured by the tl-Thresho/d-17 and duration-rl 7 IEs in the ReportConfig NR IE
  • Such multiple time windows in a Measurement Object could, as one option, be realized as a common periodicity and on-period duration, but with a neighbor cell specific offset for each neighbor cell covered by the MO, wherein the offset indicates an offset to the start of the series of repetitively recurring time windows.
  • each of the multiple time windows in the Measurement Object could have a full set of time window definition parameters.
  • Such time window(s) in the Measurement Object would in a sense serve as an overlay schedule on top of the Synchronization Signal Block (SSB) Measurement Timing Configuration(s) (SMTC(s)) included in the Measurement Object.
  • SSB Synchronization Signal Block
  • SMTC(s) Measurement Timing Configuration
  • the source RAN node namely RAN node 1, which has received beam pattern information for cells of RAN node 2, is able to efficiently configure the UE to perform measurements of RAN node 2 cells for the purpose of deciding whether a handover should be initiated. Such measurements can be performed considering whether the cells of RAN node 2 are active or not at the time of measuring them by the UE.
  • RAN node 1 may configure measurement gaps for the UE to measure cells of RAN node 2, which occur at times when some or all of the RAN node 2 cells in range of the UE are active. The UE will therefore be able to measure such cells and report their signal levels so that a handover decision towards any of those cells can be made.
  • Figure 8A is a flow chart that illustrates the operation of a node (i.e., a UE or a RAN node) in accordance with at least some of the embodiments described above.
  • the node receives, from a RAN node of a wireless network, beam pattern information for one or more cells or beams (step 800).
  • the wireless network includes one or more NTN components (e.g., the wireless network is the NTN system 500 or a similar NTN system).
  • the beam pattern information for the cell or beam includes information that indicates an on/off schedule of the cell or beam (e.g., information that indicates one or more on-periods (i.e., periods of time in which the cell or beam is on or active and/or information that indicates one or more off-periods (i.e., periods of time in which the cell or beam is off or inactive).
  • the node performs one or more actions based on the beam pattern information (step 802). Further information described above related to the receiving of such beam pattern information, the beam pattern information, and actions performed by the receiving node of the beam pattern information are equally applicable here to Figure 8A (as well as the related Figures 8B- 8E described below). .Some further examples are described below.
  • step 802-2A selecting a target cell or beam from among the one or more cells or beams operated by the target RAN node and for which the beam pattern information is received in step 800 (step 802-2A). This selection may take into consideration the beam pattern information received in step 800 for the one or more cells or beams operated by the target RAN node and, optionally, beam pattern information for a source cell or beam for the handover, which is operated by the source RAN node.
  • the RAN node from which the UE receives the beam pattern information in step 800 is a target RAN node that operates a target cell or beam for a handover of the LIE.
  • the beam pattern information is received in step 800 as part of a HO command received by the UE.
  • the one or more actions performed by the UE in step 802 include, for example, delaying execution of the HO command based on the beam pattern information for the target cell or beam (step 802-3A).
  • the RAN node from which the UE receives the beam pattern information in step 800 is a serving RAN node that operates a target cell or beam for a handover of the UE.
  • the one or more actions performed in step 802 include any one or more of the following:
  • the UE receives, from the serving RAN node, measurement configuration information that configures the UE to perform measurements on at least one of one or more neighbor cells or beams of the serving cell or beam of the UE (step 802-4A). Note that this step is shown as part of step 802; however, this step may also be considered as being separate from step 802. o
  • the beam pattern information received in step 800 includes beam pattern information for one or more neighbor cells or beams of a serving cell or beam of the UE (802-4A(l)).
  • the beam pattern information for the cell or beam includes information that indicates an on/off schedule of the cell or beam (e.g., information that indicates one or more on-periods (i.e., periods of time in which the cell or beam is on or active and/or information that indicates one or more off- periods (i.e., periods of time in which the cell or beam is off or inactive). Further information described above related to the sending of such beam pattern information and the beam pattern information itself are equally applicable here to Figure 9.
  • FIG. 10 illustrates the operation of a serving RAN node of a UE in accordance with related embodiments described above.
  • the serving RAN node sends, to the UE, measurement configuration information that configures the UE to perform measurements on one or more neighbor cells or beams, where the measurement configuration information includes one or more time-based aspects that are aligned, in time, with on-periods of the one or more neighbor cells or beams (step 1000).
  • the one or more time-based aspects related to the on/off schedules of the one or more neighbor cells or beams comprise, for each neighbor cell or beam of the one or more neighbor cells or beams, information that configures one or more time windows that are aligned with on-periods of the neighbor cell or beam.
  • the one or more time-based aspects related to the on/off schedules of the one or more neighbor cells or beams comprise information that configures one or more measurement gaps for the UE to measure the one or more neighbor cells, the one or more measurement gaps comprising, for each neighbor cell or beam of the one or more neighbor cell or beams, one or more measurement gaps that are aligned, in time, with one or more on-periods of the neighbor cell or beam.
  • Figure 11 illustrates the operation of a UE in accordance with some embodiments of the present disclosure.
  • the UE receives, from a serving RAN node of the UE, measurement configuration information that configures the UE to perform measurements on one or more neighbor cells or beams, where the measurement configuration information includes one or more time-based aspects that are aligned, in time, with on-periods of the one or more neighbor cells or beams (step 1100).
  • the one or more time-based aspects related to the on/off schedules of the one or more neighbor cells or beams comprise, for each neighbor cell or beam of the one or more neighbor cells or beams, information that configures one or more time windows that are aligned with on-periods of the neighbor cell or beam.
  • the one or more time-based aspects related to the on/off schedules of the one or more neighbor cells or beams comprise information that configures one or more measurement gaps for the UE to measure the one or more neighbor cells, the one or more measurement gaps comprising, for each neighbor cell or beam of the one or more neighbor cell or beams, one or more measurement gaps that are aligned, in time, with one or more on-periods of the neighbor cell or beam.
  • the communication system 1200 includes a telecommunication network 1202 that includes an access network 1204, such as a Radio Access Network (RAN), and a core network 1206, which includes one or more core network nodes 1208.
  • the access network 1204 includes one or more access network nodes, such as network nodes 1210A and 1210B (one or more of which may be generally referred to as network nodes 1210), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs).
  • 3GPP Third Generation Partnership Project
  • one or more of the network nodes 1210 are RAN nodes including NTN components (e.g., a RAN node implemented at an NTN node such as, e.g., a satellite, a RAN node implemented at a gateway having a feeder link to a NTN node such as, e.g., a satellite, a RAN node having part of its functionality implemented at an NTN node and part of its functionality implemented at a gateway connected to the NTN node via a feeder link, or the like).
  • NTN components e.g., a RAN node implemented at an NTN node such as, e.g., a satellite, a RAN node implemented at a gateway having a feeder link to a NTN node such as, e.g., a satellite, a RAN node having part of its functionality implemented at an NTN node and part of its functionality implemented at a gateway connected to the NTN node via a feeder link, or the like.
  • 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 1202 includes one or more Open-RAN (ORAN) network nodes.
  • ORAN Open-RAN
  • An ORAN network node is a node in the telecommunication network 1202 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 1202, including one or more network nodes 1210 and/or core network nodes 1208.
  • ORAN specification e.g., a specification published by the O-RAN Alliance, or any similar organization
  • 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 O-2 interface defined by the O-RAN Alliance or comparable technologies.
  • 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 1200 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 1200 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • 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 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and/or the telecommunication network 1202, and may be operated by the service provider or on behalf of the service provider.
  • the host 1216 may host a variety of applications to provide one or more service. Examples of such applications include live and prerecorded 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 1200 of Figure 12 enables connectivity between the UEs, network nodes, and hosts.
  • the telecommunication network 1202 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1202. For example, the telecommunication network 1202 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 Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 1212 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204.
  • a UE may be configured for operating in single- or multiRadio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi-Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • a hub 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212C and/or 1212D) and network nodes (e.g., network node 1210B).
  • the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs.
  • the hub 1214 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1214 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 1214 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1214 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 1214 may have a constant/ persistent or intermittent connection to the network node 1210B.
  • the hub 1214 may also allow for a different communication scheme and/or schedule between the hub 1214 and UEs (e.g., UE 1212C and/or 1212D), and between the hub 1214 and the core network 1206.
  • the hub 1214 is connected to the core network 1206 and/or one or more UEs via a wired connection.
  • the hub 1214 may be configured to connect to a Machine-to- Machine (M2M) service provider over the access network 1204 and/or to another UE over a direct connection.
  • M2M Machine-to- Machine
  • UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection.
  • the hub 1214 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 1210B.
  • the hub 1214 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 1210B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 13 shows a UE 1300 in accordance with some embodiments.
  • 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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, vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT Narrowband Internet of Things
  • MTC Machine Type Communication
  • eMTC enhanced MTC
  • a UE may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle-to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehicle-to-Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle-to-Everything
  • 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
  • the UE 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a power source 1308, memory 1310, a communication interface 1312, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 13. 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 input/output interface 1306 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 1300.
  • the processing circuitry 1402 includes a System on a Chip (SOC).
  • the processing circuitry 1402 includes one or more of Radio Frequency (RF) transceiver circuitry 1412 and baseband processing circuitry 1414.
  • RF Radio Frequency
  • the RF transceiver circuitry 1412 and the baseband processing circuitry 1414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of the RF transceiver circuitry 1412 and the baseband processing circuitry 1414 may be on the same chip or set of chips, boards, or units.
  • the memory 1404 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 1402 and utilized by the network node 1400.
  • the memory 1404 may be used to store any calculations made by the processing circuitry 1402 and/or any data received via the communication interface 1406.
  • the processing circuitry 1402 and the memory 1404 are integrated.
  • the communication interface 1406 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 1406 comprises port(s)/terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1406 also includes radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, the antenna 1410.
  • the radio frontend circuitry 1418 comprises filters 1420 and amplifiers 1422.
  • the radio front-end circuitry 1418 may be connected to the antenna 1410 and the processing circuitry 1402.
  • the radio front-end circuitry 1418 may be configured to condition signals communicated between the antenna 1410 and the processing circuitry 1402.
  • the radio front-end circuitry 1418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the RF transceiver circuitry 1412 is part of the communication interface 1406.
  • the communication interface 1406 includes the one or more ports or terminals 1416, the radio front-end circuitry 1418, and the RF transceiver circuitry 1412 as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).
  • the antenna 1410 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1410 may be coupled to the radio front-end circuitry 1418 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1410 is separate from the network node 1400 and connectable to the network node 1400 through an interface or port.
  • the antenna 1410, the communication interface 1406, and/or the processing circuitry 1402 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 1400. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 1410, the communication interface 1406, and/or the processing circuitry 1402 may be configured to perform any transmitting operations described herein as being performed by the network node 1400. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 1408 provides power to the various components of the network node 1400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1400 with power for performing the functionality described herein.
  • the network node 1400 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1408.
  • the power source 1408 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 1400 may include additional components beyond those shown in Figure 14 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 1400 may include user interface equipment to allow input of information into the network node 1400 and to allow output of information from the network node 1400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1400.
  • the memory 1512 may include one or more computer programs including one or more host application programs 1514 and data 1516, which may include user data, e.g. data generated by a UE for the host 1500 or data generated by the host 1500 for a LIE.
  • Embodiments of the host 1500 may utilize only a subset or all of the components shown.
  • the host application programs 1514 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (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, and heads-up display systems).
  • video codecs e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • FLAC Free Lossless Audio Codec
  • AAC Advanced Audio Cod
  • the host application programs 1514 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1500 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 1514 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 (DASH or MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • DASH or MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • 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 1600 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 virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • the virtualization environment 1600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
  • the host 1702 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 1706.
  • the user data is associated with a UE 1706 that shares data with the host 1702 without explicit human interaction.
  • the host 1702 initiates a transmission carrying the user data towards the UE 1706.
  • the host 1702 may initiate the transmission responsive to a request transmitted by the UE 1706.
  • the request may be caused by human interaction with the UE 1706 or by operation of the client application executing on the UE 1706.

Landscapes

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

Abstract

Dans la présente divulgation, des systèmes et des procédés sont décrits, qui sont basés sur un échange d'informations de diagrammes de faisceau entre des nœuds de RAN. Grâce à l'échange de telles informations, des nœuds de RAN peuvent prendre de meilleures décisions de mobilité relatives à la sélection de cellules cibles de mobilité pour un UE donné.
PCT/IB2024/063138 2024-01-19 2024-12-23 Transfert de ntn à l'aide de diagrammes de sauts de faisceau Pending WO2025153889A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR20240100032 2024-01-19
GR20240100032 2024-01-19

Publications (1)

Publication Number Publication Date
WO2025153889A1 true WO2025153889A1 (fr) 2025-07-24

Family

ID=94341397

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2024/063138 Pending WO2025153889A1 (fr) 2024-01-19 2024-12-23 Transfert de ntn à l'aide de diagrammes de sauts de faisceau

Country Status (1)

Country Link
WO (1) WO2025153889A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170105153A1 (en) * 2015-10-13 2017-04-13 Qualcomm Incorporated Method and apparatus for inter-satellite handovers in low-earth orbit (leo) satellite systems
US20230247507A1 (en) * 2021-04-02 2023-08-03 Apple Inc. Enhancement in ntn mobility

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170105153A1 (en) * 2015-10-13 2017-04-13 Qualcomm Incorporated Method and apparatus for inter-satellite handovers in low-earth orbit (leo) satellite systems
US20230247507A1 (en) * 2021-04-02 2023-08-03 Apple Inc. Enhancement in ntn mobility

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Solutions for NR to support non-terrestrial networks (NTN) (Rel-16", 3GPP TR 38.821
"Study on New Radio (NR) to support non-terrestrial networks (Rel-15", 3GPP TECHNICAL REPORT (TR) 38.811
FU I-KANG ET AL: "Satellite and Terrestrial Network Convergence on the Way Toward 6G", IEEE WIRELESS COMMUNICATIONS, COORDINATED SCIENCE LABORATORY; DEPT. ELECTRICAL AND COMPUTER ENGINEERING; UNIVERSITY OF ILLINOIS AT URBANA-CHAMPAIGN, US, vol. 30, no. 1, 1 February 2023 (2023-02-01), pages 6 - 8, XP011937003, ISSN: 1536-1284, [retrieved on 20230320], DOI: 10.1109/MWC.2023.10077212 *

Similar Documents

Publication Publication Date Title
US20250113277A1 (en) Systems and methods for time-based handover in non-terrestrial networks
US20250184854A1 (en) Systems and methods for time-based triggered handover in non-terrestrial networks
EP4569902A1 (fr) Mesures de csi pour mobilité intercellulaire
EP4413773A1 (fr) Configuration de minimisation de tests mobiles
WO2023213984A1 (fr) Configuration de l'ue pour le transfert temporel dans un réseau sans fil tel qu'un réseau non terrestre
WO2023105073A1 (fr) Commande d'admission inter-nœuds de réseau pour un ue relais de liaison latérale
WO2023207433A1 (fr) Procédés et appareils de communication dans un système de communication sans fil avec une caractéristique d'économie d'énergie de réseau
US20250254579A1 (en) Measurement reporting based on measurement configurations using frequency specific priority indications
WO2023152683A1 (fr) Changement de pscell conditionnel initié par un nœud secondaire
US20240323995A1 (en) Secondary node requested measurement gaps at secondary node addition
WO2025153889A1 (fr) Transfert de ntn à l'aide de diagrammes de sauts de faisceau
EP4442028B1 (fr) Configuration de minimization of drive test dans équipement utilisateur
US20250047393A1 (en) Efficient inter-cell l1-rsrp measurement and reporting
WO2025172889A1 (fr) Mobilité pour accès et liaison terrestre sans fil
EP4635230A1 (fr) Systèmes et procédés par un noeud de réseau de gestion pour réduire la probabilité d'utilisation conflictuelle de ressources par des équipements utilisateur
EP4570028A1 (fr) Configuration d'activation/désactivation pour répéteur commandé par réseau
EP4612934A1 (fr) Optimisation de mobilité améliorée à l'aide d'une prédiction de trajectoire d'ue
EP4635231A1 (fr) Systèmes et procédés d'activation de ressources requises pour un transfert conditionnel étendu
WO2025153838A1 (fr) Nœud de réseau de fournisseur de source, nœud de réseau de fournisseur cible et procédés mis en œuvre dans ceux-ci
WO2025071467A1 (fr) Procédé de distribution de charge entre des nœuds de réseau d'accès radio
EP4569918A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2025104082A1 (fr) Procédé et appareil de réduction d'interruption de positionnement dans un ntn
WO2024231172A1 (fr) Gestion d'informations de bande passante associées à sl pour permettre un positionnement sl
WO2025169166A1 (fr) Gestion de budget de retard de paquet d'accès pour des nœuds ran de liaison d'accès sans fil
CN121040140A (zh) 用于层1/层2触发移动性的配置

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: 24841494

Country of ref document: EP

Kind code of ref document: A1