[go: up one dir, main page]

WO2025104082A1 - Procédé et appareil de réduction d'interruption de positionnement dans un ntn - Google Patents

Procédé et appareil de réduction d'interruption de positionnement dans un ntn Download PDF

Info

Publication number
WO2025104082A1
WO2025104082A1 PCT/EP2024/082170 EP2024082170W WO2025104082A1 WO 2025104082 A1 WO2025104082 A1 WO 2025104082A1 EP 2024082170 W EP2024082170 W EP 2024082170W WO 2025104082 A1 WO2025104082 A1 WO 2025104082A1
Authority
WO
WIPO (PCT)
Prior art keywords
positioning
handover
base station
signaling
lmf
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/EP2024/082170
Other languages
English (en)
Inventor
Min Wang
Ming Li
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 WO2025104082A1 publication Critical patent/WO2025104082A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • 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/18513—Transmission in a satellite or space-based system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • H04W36/00725—Random access channel [RACH]-less handover

Definitions

  • the present techniques are generally related to handovers in wireless communications networks, and more particularly related to such handovers in non-terrestrial networks (NTNs).
  • NTNs non-terrestrial networks
  • a UE In connected state, in the 3GPP specifications known as the RRC_CONNECTED state, a UE has an active connection to the network for sending and receiving of data and signaling. In connected state, mobility is controlled by the network to ensure connectivity is retained to the UE with no interruption or noticeable degradation of the provided service as the UE moves between the cells within the network.
  • Connected state mobility is also known as handover.
  • the UE is moved from a source node using a source cell connection, to a target node using a target cell connection where the target cell connection is associated with a target cell controlled by the target node.
  • the UE moves from the source cell to a target cell.
  • the source node and the target node may also be referred to as the source access node and the target access node or the source radio network node and the target radio network node.
  • the source node and the target node are referred to as the source gNB and the target gNB.
  • a UE in RRC_CONNECTED state is required to search and perform measurements on neighbor cells both on the current carrier frequency (intra-frequency) as well as on other carrier frequencies (inter-frequency).
  • the UE does not take any autonomous decisions when to trigger a handover to a neighbor cell (except to a limited extent when the UE is configured for conditional handover, as discussed below). Instead, the UE sends the measurement results from the measurements it performed on serving and neighboring cells to the network, where a decision is taken whether or not to perform a handover to one of the neighbor cells.
  • the network may send a message to the UE to instruct the UE to execute a handover.
  • This message is an RRCReconfiguration message with a reconfigurationWithSync IE.
  • the message is often informally referred to as a "handover command" (although a Handovercommand is really an inter- gNB RRC message which is transferred in the "Target NG-RAN node To Source NG-RAN node Transparent Container" IE in the Handover Request Acknowledge XnAP message during preparation of an Xn handover and in the "Target to Source Transparent Container” IE in the Handover Request Acknowledge NGAP message and the Handover Command NGAP message during preparation of an NG handover).
  • a Handovercommand is really an inter- gNB RRC message which is transferred in the "Target NG-RAN node To Source NG-RAN node Transparent Container" IE in the Handover Request Acknowledge XnAP message during preparation of an Xn handover and in the "Target to Source Transparent Container” IE in the Handover Request Acknowledge NGAP message and the Handover Command NGAP message during preparation of an NG handover).
  • the source node and the target node are different nodes, such as different gNBs. Such a case is referred to as an inter-node or inter-gNB handover.
  • the source node and the target node are one and the same node, such as the same gNB.
  • Such a case is referred to as an intra-node or intra-gNB handover and covers the case when the source and target cells are controlled by the same node.
  • handover is performed within the same cell and thus also within the same node controlling that cell. These cases are referred to as intra-cell handover and may be performed to refresh security parameters.
  • source node or source access node
  • target node target access node
  • a given gNB may serve as source gNB during handover of one UE, while it also serves as the target gNB during handover of a different UE.
  • the same gNB serves both as the source gNB and target gNB for that UE.
  • An inter-node handover in NR can further be classified as an Xn-based or NG-based handover depending on whether the source and target node communicate directly using the Xn interface or indirectly via the Core Network (through one or two AMF(s)) using NG interfaces.
  • the actual handover execution is preceded by a handover preparation phase consisting of communication between the source gNB and the target gNB.
  • the source gNB provides the target gNB with state information related to the UE (referred to as the UE context), e.g., information about the UE's PDU session resources (e.g., QoS flow(s)) and various other configuration information, and the target gNB performs admission control (and assumedly accepts the handover) and returns indications of the admitted PDU session resources (e.g., QoS flow(s)) and the configuration the UE should apply when accessing the target cell.
  • the UE context state information related to the UE
  • the target gNB performs admission control (and assumedly accepts the handover) and returns indications of the admitted PDU session resources (e.g., QoS flow(s)) and the configuration the UE should apply when accessing the target cell.
  • the UE configuration the target gNB provides is included in an inter-gNB RRC message called "HandoverCommand" and is formatted as an RRCReconfiguration message (including a reconfigurationWithSync IE).
  • This RRCReconfiguration message (i.e., the handover command) is then forwarded by the source gNB to the UE and this triggers the UE to execute the handover (by releasing it connection in the source cel I, synchronizing with the target cel I, and initiating a random access procedure in the target cell to establish a connection).
  • the UE sends an RRCReconfigurationComplete message (often referred to as a Handover Complete message) to acknowledge the RRCReconfiguration message that triggered the handover execution and to confirm the successful execution of the handover.
  • RRCReconfigurationComplete message (often referred to as a Handover Complete message) to acknowledge the RRCReconfiguration message that triggered the handover execution and to confirm the successful execution of the handover.
  • Figure 1 shows a simplified signaling flow between the UE, the source gNB and the target gNB during an Xn-based inter-gNB handover in NR.
  • Figure 2 shows a slightly more detailed signaling flow for the same Xn-based inter-gNB handover.
  • control plane data i.e., RRC messages such as the measurement report, handover command and handover complete messages
  • SRBs Signaling Radio Bearers
  • DRBs Data Radio Bearers
  • the UE has an active connection to the source gNB where user data is sent and received to/from the network. Due to some trigger in the source gNB, e.g., a measurement report received from the UE, the source gNB decides to handover the UE to a target (neighbor) cell controlled by the target gNB.
  • some trigger in the source gNB e.g., a measurement report received from the UE
  • the source gNB decides to handover the UE to a target (neighbor) cell controlled by the target gNB.
  • the source gNB sends the XnAP HANDOVER REQUEST message to the target gNB passing a transparent RRC container with necessary information to prepare the handover at the target side.
  • the information includes for example the target cell id, the target security key, the current source configuration and UE capabilities.
  • the target gNB prepares the handover and responds with the XnAP HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which includes the handover command (an RRCReconfiguration message containing the reconfigurationWithSync field) to be sent to the UE.
  • the handover command includes configuration information that the UE should apply once it connects to the target cell, e.g., random access configuration, a new C-RNTI assigned by the target node, security parameters, etc. Steps 101-104 together may be considered to be a Handover Preparation phase 105.
  • the source gNB triggers the handover by sending the handover command (received from the target gNB in the previous step) to the UE.
  • the UE Upon reception of the handover command the UE releases the connection to the old (source) cel I, starts the handover supervision timer T304, and starts to synchronize to the new (target) cell.
  • the source gNB stops scheduling any further DL user data to the UE and sends the XnAP SN STATUS TRANSFER message to the target gNB indicating the latest PDCP SN transmitter and receiver status.
  • the source gNB now also starts to forward DL user data received from the Core Network to the target gNB, which buffers this data for now.
  • Steps 105-110 may be considered to be a Handover Execution phase 1113.
  • the target gNB Upon receiving the handover complete message, the target gNB starts sending (and receiving) user data to/from the UE.
  • the target gNB requests the Core Network (CN) to switch the DL user data path between the User Plane Function (UPF) and the source node to the target node (communication to the CN is not shown in the Figure).
  • the target gNB sends the XnAP UE CONTEXT RELEASE message to the source gNB to release all resources associated to the UE. This step may be considered the Handover Completion phase 114.
  • Mobility in RRC_CONNECTED state is network-controlled as the network has the best information regarding the current overall situation, such as load conditions, resources in different nodes, available frequencies, etc.
  • the network can also take into account the situation of many UEs in the network, from a resource allocation perspective.
  • the network prepares a target cell before the UE accesses that cell.
  • the source gNB provides UE with the RRC configuration to be used in the target cell, including SRB1 configuration to send HO complete.
  • the source gNB receives this RRC configuration from the target gNB in the form of a Handovercommand inter-node RRC message included in the HANDOVER REQUEST ACKNOWLEDGE XnAP message (where the Handovercommand is included in the "Target NG-RAN node To Source NG-RAN node Transparent Container" IE).
  • the target gNB In the RRC configuration the target gNB provides to the UE via the source gNB, the target gNB configures the UE with a C-RNTI to be used in the target cell.
  • the target gNB leverages this C-RNTI to identify the UE from Msg3 on MAC level for the HO complete message (which is an RRCReconfigurationComplete message transmitted by the UE in the target cell to indicate the successful completion of the handover).
  • HO complete message which is an RRCReconfigurationComplete message transmitted by the UE in the target cell to indicate the successful completion of the handover.
  • the network provides needed information on how to access the target cell, e.g., RACH configuration, so the UE does not have to acquire SI (other than the MIB) prior to the handover. This information is included in the Handovercommand and thus in the target cell RRC configuration sent to the UE.
  • the UE may be provided with contention free random access (CFRA) resources (in the above mentioned RRC configuration forwarded to the UE by the source gNB).
  • CFRA resources consist of one or more CFRA preamble(s) and may also contain CFRA occasions (i.e., PRACH transmission resources that are not included in the common PRACH configuration).
  • Msgl random access preamble
  • Security is prepared before the UE accesses the target cell, i.e., security keys must be refreshed before sending the HO complete message (i.e., the RRCReconfigurationComplete message), so that new keys are used to encrypt and integrity protect the HO complete message, enabling verification in the target cell.
  • the HO complete message i.e., the RRCReconfigurationComplete message
  • the target cell RRC configuration may be provided to the UE in two different forms: full configuration or delta configuration.
  • full configuration the provided RRC configuration is complete and self-contained, but a delta configuration only contains the configuration parts that are different in the target cell than in the source cell.
  • delta configuration is that the size of the Handovercommand can be minimized. Interruption in Handover
  • the service interruption time caused by handover is defined as the duration between the point in time when the UE stops transmission/reception with the source gNB and the time when target gNB resumes the transmission/reception with the UE after UE has sent RRCReconfigurationComplete.
  • the handover interruption time itself, which entails RRC procedure delay which is limited to 10 ms for RRCReconfiguration and the interruption time until the UE starts the transmission PRACH to target gNB.
  • This part of the service interruption time comprises:
  • the service interruption time which may be understood as an interruption in connectivity resulting from handover of a user equipment, UE, to or from a gNB an interruption in connectivity resulting from handover of a user equipment, UE, to or from the gNB, may be referred to as Tinterrupt, and may comprise the components and typical values provided in Table 1, for an intra-frequency handover.
  • NTN Non-Terrestrial Networks
  • NTN Non-Terrestrial Network
  • a GEO satellite is fed by one or several satellite -gateways which are deployed across the satellite targeted coverage (e.g., regional or even continental coverage).
  • satellite targeted coverage e.g., regional or even continental coverage.
  • UE in a cell are served by only one sat-gateway o
  • a Non-GEO satellite served successively by one or several satellite -gateways 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 handover
  • a satellite which may implement either a transparent or a regenerative (with on board processing) payload.
  • the satellite or UAS platform
  • the satellite (or UAS platform) generates beams typically generate several beams over a given service area bounded by its field of view.
  • the footprints of the beams are typically of elliptic shape.
  • the field of view of a satellite (or UAS platforms) depends on the on board antenna diagram and min elevation angle.
  • o A transparent payload Radio Frequency filtering, Frequency conversion and amplification. Hence, the waveform signal repeated by the payload is un-changed.
  • a regenerative payload Radio Frequency filtering, Frequency conversion and amplification as well as demodulation/decoding, switch and/or routing, coding/modulation.
  • Inter-satellite links optionally in case of a constellation of satellites. This will require regenerative payloads on board the satellites.
  • ISL may operate in RF frequency or optical bands.
  • Satellites or UAS platforms
  • Example architectures with NTNs are shown in Figures 3, 4, 5, and 6.
  • a UE may be connected and served simultaneously by at least:
  • NTN-based NG-RAN • One NTN-based NG-RAN and one terrestrial-based access (NR or EUTRA), or One NTN-based NG-RAN and another NTN-based NG-RAN.
  • NR or EUTRA terrestrial-based access
  • NTN-based NG-RAN • One NTN-based NG-RAN and another NTN-based NG-RAN.
  • An NTN can have beam-based coverage, e.g., as depicted in Figure 7.
  • Figure 8 shows an example architecture of a satellite network with bent pipe transponders (i.e., the transparent payload architecture).
  • the significant orbit height means that satellite systems are characterized by a path loss that is significantly higher than what is expected in terrestrial networks. To overcome the pathloss it is often required that the access and feeder links are operated in line-of-sight conditions, and that the UE is equipped with an antenna offering high beam directivity.
  • the NTN beam may in comparison to the beams observed in a terrestrial network provide a very wide footprint and may cover an area outside of the area defined by the served cell. Beam covering adjacent cells will overlap and cause significant levels of intercell interference, resulting from the slow decrease of the signal strength in the outwards radial direction. This is due in part to the high elevation angle and long distance to the networkside (satellite-borne) transceiver, which, compared with terrestrial cells, results in a comparatively small relative difference between the distance from the cell center to the satellite and the distance from a point at the cell edge to the satellite.
  • a typical approach in NTN is to configure different cells with different carrier frequencies and polarization modes.
  • NTN Three types of beams or cells are supported in NTN: • Earth-fixed beams/cells: provisioned by beam(s) continuously covering the same geographical areas all the time (e.g., in the case of GEO satellites).
  • Quasi-Earth-fixed beams/cells provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (e.g., in the case of NGSO satellites generating steerable beams).
  • hard switch there are two alternative principles: 1) hard switch; and 2) soft switch.
  • hard switch there is an instantaneous switch from the old to the new cell, i.e., the new cell appears at the same time as the old cell disappears. This makes completely seamless (i.e., interruption free) handover in practice impossible and creates a situation which may lead to overload of the access resources in the new cell, due to potential access attempt peaks when many UEs try to access the new cell right after the cell switch.
  • soft switch there is a time period during which the new and the old cell coexist (i.e. overlap), covering the same geographical area.
  • This coexistence/overlap period allows some time for connected UEs to be handed over and for camping UEs to reselect to the new cell, which facilitates distribution of the access load in the new cell and thereby also provides better conditions for handovers with shorter interruption time.
  • Soft switch is likely to be the most prevalent cell switch principle in quasi-Earth-fixed cell deployments.
  • the time when a pseudo-Earth-fixed cell will stop serving the current area i.e. the time the pseudo- Earth-fixed cell will cease to exist, is indicated by the t-Service-rl7 IE which is broadcast in SIB19 in NR NTN (and in SIB31 in loT NTN).
  • Positioning has been a topic in LTE standardization since 3GPP Release 9.
  • the primary objective of positioning in LTE was to fulfill regulatory requirements for emergency call localization where the target was to achieve ⁇ 50m horizontal accuracy.
  • NR New Radio
  • Positioning in NR is supported by the architecture shown in Figure 9.
  • the interactions between the gNodeB and the device is supported via the Radio Resource Control (RRC) protocol, while the location node interfaces with the UE via the LTE positioning protocol (LPP).
  • RRC Radio Resource Control
  • LPP LTE positioning protocol
  • LMF is the location node in NR.
  • the AMF when the AMF receives a Location Service Request in case of the UE is in CM-IDLE state, the AMF performs a network triggered service request in order to establish a signalling connection with the UE and assign a specific serving gNB or ng-eNB.
  • the UE is assumed to be in connected mode before the beginning of the flow shown in Figure 8; that is, any signalling that might be required to bring the UE to connected mode prior to step la is not shown.
  • the signalling connection may, however, be later released (e.g., by the NG-RAN node as a result of signalling and data inactivity) while positioning is still ongoing.
  • the steps shown in Figure 10 include: la. Either: some entity in the 5GC (e.g., GMLC) requests some location service (e.g., positioning) for a target UE to the serving AMF. lb. Or: the serving AMF for a target UE determines the need for some location service (e.g., to locate the UE for an emergency call). lc. Or: the UE requests some location service (e.g., positioning or delivery of assistance data) to the serving AMF at the NAS level.
  • some entity in the 5GC e.g., GMLC
  • some location service e.g., positioning
  • some location service e.g., positioning
  • some location service e.g., positioning for a target UE to the serving AMF.
  • the AMF transfers the location service request to an LMF.
  • the LMF instigates location procedures with the serving and possibly neighbouring ng- eNB or gNB in the NG-RAN - e.g., to obtain positioning measurements or assistance data.
  • the LMF instigates location procedures with the UE - e.g., to obtain a location estimate or positioning measurements or to transfer location assistance data to the UE.
  • the LMF provides a location service response to the AMF and includes any needed results - e.g., success or failure indication and, if requested and obtained, a location estimate for the UE.
  • step lb the AMF uses the location service response received in step 4 to assist the service that triggered this in step lb (e.g., may provide a location estimate associated with an emergency call to a GMLC).
  • step lc the AMF returns a location service response to the UE and includes any needed results - e.g., a location estimate for the UE.
  • Steps 3a and 3b can involve the use of different position methods to obtain location related measurements for a target UE and from these compute a location estimate and possibly additional information like velocity.
  • Enhanced Cell ID Essentially cell ID information to associate the device to the serving area of a serving cell, and then additional information to determine a finer granularity of UE position.
  • Assisted GNSS GNSS information retrieved by the device, supported by assistance information provided to the device from E-SMLC.
  • UE performs positioning measurement (reference signal time difference (RSTD) measurements in this case) on downlink positioning reference signal (DL-PRS) transmitted by base stations (BSs) and reports them to the E-SMLC for position estimation.
  • RSTD reference signal time difference
  • Uplink TDOA Similar to OTDOA but in uplink (UL) direction. Positioning measurements are done by the network node on UE transmitted reference signal for positioning measurement in UL. The measurements are reported to E-SMLC where the ultimate position estimation is performed.
  • NR positioning In comparison to LTE, NR positioning benefits from larger bandwidth and finer beamforming and can localize a user equipment (UE) with higher accuracy and supports the following positioning methods:
  • the DL TDOA positioning method makes use of the downlink reference signal time difference (DL RSTD) measurement done by UE on positioning reference signal (PRS) transmitted by multiple transmission and reception points (TRPs). This method is similar to OTDOA in LTE.
  • DL RSTD downlink reference signal time difference
  • PRS positioning reference signal
  • TRPs transmission and reception points
  • the Multi-RTT positioning method makes use of multiple round trip time (RTT) measurements for UE position estimation. For each RTT measurement UE Rx-Tx and gNB Rx-Tx time difference measurements are used.
  • RTT round trip time
  • the UL TDOA positioning method makes use of the UL TDOA (and optionally UL SRS-RSRP) at multiple TRPs of uplink signals transmitted from UE.
  • the RPs measure the UL TDOA (and optionally UL SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.
  • the DL AoD positioning method makes use of the measured DL PRS RSRP of downlink signals received from multiple TRPs, at the UE.
  • the UE measures the DL PRS RSRP of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE.
  • the UL-AoA positioning method makes use of the measured azimuth and zenith of arrival at multiple TRPs of uplink signals transmitted from the UE.
  • the TRPs measure A-AoA and Z-AoA of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.
  • NR-ECID NR Enhanced Cell ID (NR E CID) positioning refers to techniques which use additional UE measurements and/or NR radio resource and other measurements to improve the UE location estimate.
  • the NR positioning modes can be categorized into:
  • UE-Assisted The UE performs measurements with or without assistance from the network and sends these measurements to the E-SMLC where the position calculation may take place.
  • the UE performs measurements and calculates its own position with assistance from the network.
  • Standalone The UE performs measurements and calculates its own position without network assistance.
  • the Multi-RTT positioning method is illustrated in Figure 11 and Figure 12.
  • RTT is calculated from (gNB_Rx - gNB_Tx) - (UE_Rx - UE_Tx) .
  • LMF shall be able to estimate the distance between UE and each gNB and in turn the UE position provided gNB position is known.
  • the network should configure the positioning resources. Compared to legacy multi-RTT positioning, network can also configure the period of RTT measurement. After triggering of measurement, UE and network node periodically measure the DL-PRS and transmit UL-SRS resource(s) according to the configured positioning resources. Then, network node and/or UE may report the Rx-Tx time difference every time after measurement or in one shot after all the measurements. After the measurements, LMF determine the RTTs and calculate UE position.
  • a timing sequence for measuring RTT is shown in Figure 13.
  • gNB shall transmit PRS at tdO, satellite receives and transmit PRS to UE at tdl and UE receives and starts to measure PRS at td2.
  • UE transmits SRS at tuO, satellite node receives and transmits SRS to gNB at tul and gNB receives and starts to measure SRS at tu2.
  • Tl indicates when to start or end or trigger or initiate the first RTT measurement occasion
  • T2 indicates when to or end or trigger or initiate the second RTT measurement occasion and so on within one full multi-RTT measurement
  • Tl equal to tdO, tdl, td2, tuO, tul or tu2 depending on different views.
  • the time sequence with respect to Tl, T2 and T3 is often used even when more appropriate terms would be positioning measurement sequence, set of positioning measurement, positioning measurement set, repeating positioning measurement and so on.
  • TRP/satellite node transmitting PRS resource(s) based on which UE perform UE Rx-Tx time difference measurement, i.e., tu2 and tdO in the RTT equation above.
  • PRS resource(s) i.e., tu2 and tdO in the RTT equation above.
  • the assistance data to UE shall include, for example tdl as time instance, when it shall perform positioning measurement on DL PRS resource(s) transmitted by the satellite node.
  • the assistance data to UE shall also include, for example tuO as time instance, to configure UE to start transmission of SRS resource(s) for positioning measurement(s).
  • the variable Pue in the equation above denotes the location of target UE which is estimated by exploiting multiple RTT measurements.
  • the existing NR positioning specification supports multi-RTT based positioning for cellular network where TRPs are at fixed locations that are static and do not change over time.
  • NTN network there may be one or multiple satellites involved in a positioning procedure for an NTN UE.
  • the UE is expected to perform RTT measurement with the same satellite in different locations (as shown in Figure 14).
  • the UE position on earth shall be estimated by the network.
  • LMF provides assistance data for positioning measurement to the UE based on static TRP location
  • NTN assistance data shall consider mobile TRP where multiple RTT measurements are done on the PRS transmitted by the same satellite from different locations at different time instants.
  • multiple measurement instants are taken together to mimic different TRPs.
  • both the UE and the satellite (gNB) need to provide RX-TX difference reports.
  • the UE when the UE needs to be positioned, if there are multiple satellite available, it is also feasible to involve those multiple satellites to perform positioning for the UE.
  • the existing NR positioning specification supports multi-RTT based positioning for terrestrial cellular network where TRPs are at fixed locations that are static and do not change over time.
  • the UE and the gNB need to provide measurements (e.g., RTT measurements) to the LMF before a response time elapses (i.e., the LMF may indicate the time period in the assistance information which is provided to the UE and the gNB by the LMF). If the UE or the gNB is unable to perform the requested measurements, or the Response Time elapses before any of the requested measurements were obtained, the UE or the gNB returns any information that can be provided, which includes a cause indication for the not provided location information.
  • measurements e.g., RTT measurements
  • the LMF may indicate the time period in the assistance information which is provided to the UE and the gNB by the LMF.
  • moving satellite would result in moving or switching cells, especially taking LEO satellites into account.
  • a LEO satellite may be visible to a UE on the ground only for a few seconds or minutes depending on LEO deployments.
  • the UE or the gNB may experience interruption delay due to cell/satellite change.
  • the UE or the gNB may be unable to provide the measurement results to the LMF which may lead to a positioning failure. Therefore, it is necessary to study how to reduce interruption of cell/satellite change to mitigate or avoid impact to positioning procedure from gNB and UE perspective.
  • cell/satellite change and positioning procedure are adapted in case of collision between each other.
  • assistance information is exchanged between NTN UE, NTN gNB operating a serving cell/satellite, NTN gNB(s) operating neighbor cell(s)/satellite(s), and LMF.
  • Example embodiments described in detail below include a method, in a UE, where the method comprises determining that a positioning procedure for the UE cannot be completed prior to an imminent handover and, in response, performing at least one of several actions. These actions include: sending a positioning procedure failure message to a location management function (LMF); informing a serving base station that the UE cannot complete positioning; requesting a neighbor base station to continue and/or start positioning of the UE after handover, and performing measurements of a cell provided by the neighbor base station, after the handover; requesting a neighbor base station to start positioning of the UE immediately, before the handover is completed, and performing measurements of a cell provided by neighbor base station; and sending, to the LMF, an indication of a connectivity interruption time corresponding to the handover.
  • LMF location management function
  • Another example method in a UE comprises the steps of initiating a positioning procedure involving at least one cell in an NTN, performing a RACH-less handover prior to completion of the positioning procedure, and completing the positioning procedure after performing the RACH-less handover.
  • One example method comprises the steps of determining that a positioning procedure for a UE served by the base station cannot be completed prior to an imminent handover and, in response, performing at least one of several actions, where the several actions include: sending a positioning procedure failure message to an LMF; informing the UE that the serving base station cannot complete positioning of the UE; requesting a neighbor base station to continue and/or start positioning of the UE after handover; requesting a neighbor base station to start positioning of the UE immediately, before the handover is completed; and sending, to the LMF, an indication of a connectivity interruption time corresponding to the handover.
  • Another example method in one or more network nodes configured to operate as a base station of a wireless communications network, comprises the steps of determining that a UE served by the base station is to be handed over to a target base station and, in response, including positioning measurement configuration and/or a positioning measurement request in handover messaging and/or in messaging associated with handover messaging.
  • Yet another example method in one or more network nodes configured to operate as a base station of a wireless communications network, comprises the steps of receiving positioning measurement configuration information and/or a positioning measurement request in handover messaging and/or in messaging associated with handover messaging, the handover messaging being for a UE being handed over to the base station and, upon completion of handover of the UE to the base station, performing positioning of the UE based on the positioning measurement configuration information and/or the positioning measurement request.
  • Still other embodiments include a method carried out in one or more network nodes configured to operate as an LMF, where the method comprises receiving an indication of an interruption period caused by a handover for a UE and, in response, performing one or more of the following: sending first signaling to the UE and/or a base station serving the UE, the first signaling indicating that reception and/or transmission of positioning reference signaling by the UE and/or base station can be delayed; sending second signaling to the UE and/or a base station serving the UE, the second signaling indicating that reception and/or transmission of positioning reference signaling by the UE and/or base station should be triggered in advance of the interruption period; sending third signaling to the UE and/or a base station serving the UE, the third signaling indicating additional resources for positioning reference signaling resources for use by transmission points previously configured to transmit positioning reference signaling for use in positioning the UE; and sending fourth signaling to the UE and/or a base station serving the UE, the fourth signaling indicating additional resources for positioning reference
  • Figure 1 shows a simplified signaling flow between the UE, the source gNB and the target gNB during an Xn-based inter-gNB handover in NR.
  • Figure 2 shows a more detailed signaling flow between the UE, the source gNB and the target gNB during an Xn-based inter-gNB handover in NR.
  • Figure 3 shows Networking-RAN architecture with transparent satellite.
  • Figure 4 illustrates a regenerative satellite without ISL, with gNB processed payload.
  • Figure 5 illustrates a regenerative satellite with ISL and a gNB processed payload.
  • Figure 6 shows NG-RAN with a regenerative satellite based on gNB-DU.
  • Figure 7 illustrates a typical non-terrestrial network scenario based on regenerative payload, with beam-based coverage.
  • Figure 8 shows an example architecture of a satellite network with bent pipe transponders (also known as the transparent payload architecture).
  • Figure 9 illustrates the positioning architecture in NR.
  • Figure 10 shows Location Service Support by NG-RAN in TS 38.305 V 17.3.0.
  • FIG 11 illustrates the basis for a round trip time (RTT) calculation.
  • Figure 12 shows an example of cellular network deployment and UE positioning.
  • Figure 13 is a timing sequence for measuring RTT.
  • Figure 14 shows a multi-RTT sequence.
  • Figure 15 is a process flow diagram illustrating an example method as carried out in a network node.
  • Figure 16 is a process flow diagram illustrating an example method as carried out in a wireless device.1
  • Figure 17 is a process flow diagram illustrating another example method as carried out in a network node.
  • Figure 18 is a process flow diagram illustrating another example method as carried out in a wireless device.
  • Figure 19 is a process flow diagram illustrating still another example method as carried out in a network node.
  • Figure 20 is a process flow diagram illustrating yet another example method as carried out in a network node.
  • FIG 21 is a process flow diagram illustrating an example method as carried out in a network node configured to operate as a Location Management Function (LMF).
  • LMF Location Management Function
  • Figure 22 illustrates an example communication network.
  • Figure 23 shows a UE 2300 in accordance with some embodiments.
  • Figure 24 shows a network node 2400 in accordance with some embodiments.
  • Figure 25 is a block diagram of a host 2500.
  • Figure 26 is a block diagram illustrating a virtualization environment 2600 in which functions implemented by some embodiments may be virtualized.
  • Figure 27 shows a communication diagram of a host 2702 communicating via a network node 2704 with a UE 2706 over a partially wireless connection in accordance with some embodiments.
  • terrestrial network node may comprise a radio network node (e.g., BS, gNB, gNB-DU, gNB-CU, relay or IAB node, radio network controller, TRP, etc.) or a core network node (e.g., MSC, MME, O&M, OSS, SON, positioning node, etc.).
  • a radio network node e.g., BS, gNB, gNB-DU, gNB-CU, relay or IAB node, radio network controller, TRP, etc.
  • core network node e.g., MSC, MME, O&M, OSS, SON, positioning node, etc.
  • NTNs Non-Terrestrial Networks
  • NTNs are networks, or segments of networks, using an airborne or space- borne vehicle to embark a transmission equipment relay node or base station.
  • NTN node is used to denote one or more radio network nodes or equipment at an airborne or space-borne vehicle, satellite (e.g., LEO, MEO, GEO, HEO, etc.), UAS platform, etc. capable of at least receiving radio signals from UE operating on the Earth.
  • NTN node's receivers may have specific RF characteristics (e.g., sensitivity) and may operate in specific RF bands dedicated for NTN operation.
  • NTN node may also comprise a gNB of a special type, i.e., capable of NTN operation.
  • location server positioning
  • LMF positioning
  • E-SMLC E-SMLC
  • time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are: symbol, time slot, subframe, radio frame, TTI, interleaving time, slot, sub-slot, mini-slot, etc.
  • gNB gNode B
  • eNB base station
  • satellite TRP
  • serving cell and serving satellite or neighbor cell and neighbor satellite are used interchangeably. In some cases, one of them is used specially, e.g., for a feeder link switch but no satellite change, serving cell and neighbor cell are used. But for the sake of generality, serving satellite and neighbor satellite also are used.
  • a first group of techniques involves cell/satell ite change.
  • a UE is unable to execute UL transmissions or DL measurements for positioning procedure during the interruption.
  • RACH procedure including propagation delay of message transmission is the most critical time-consumed component.
  • the UE and/or the gNB(s) operate to place Tinterrupt, here referring to the duration of an interruption in connectivity caused by handover of a UE, between two (or pre-defined number) consecutive UL transmissions or DL measurements on reference signals to gNB or UE. It also can be interpreted that handover procedure shall be started from end time of a reference signal occasion to the start time of reference signal occasion and ended before the end time of the consecutive reference signal occasion. Tinterrupt may be the practical interruption time or an estimated time period that can cover typical/most of practical time for handover procedure.
  • interruption of handover is treated as a gap for positioning procedure, i.e., positioning procedure, e.g., transmission or reception of reference signals shall not fall into the gap.
  • positioning procedure e.g., transmission or reception of reference signals shall not fall into the gap.
  • reference signals For periodic or semi-periodic or aperiodic positioning reference signal:
  • gNB or UE shall transmit signals before or after Tinterrupt.
  • gNB shall configure TDM pattern between transmitting positioning reference signal and handover command.
  • transmitting positioning reference signal is xl ms earlier than handover command.
  • transmitting positioning reference signal is x2 ms after handover command.
  • UE shall start to process RRCReconfiguration procedure with TDM pattern with transmitting positioning reference signal.
  • transmitting positioning reference signal is x3 ms earlier than processing RRCReconfiguration procedure.
  • transmitting positioning reference signal is x4 ms after processing RRCReconfiguration procedure.
  • gNB or UE shall transmit signals again immediately after Tinterrupt provided aperiodic positioning reference signal is configured.
  • gNB or UE is expected to receive and measure signal before and after Tinterrupt.
  • Tinterrupt to indicate the start time of Tinterrupt which may be interpreted variously, handover command for gNB and processing RRCReconfiguration procedure for UE are taken as references without loss of generality. It shall be noted that other time references in gNB or UE can be defined as start time of Tinterrupt also. The same rules also are applied for end time of Tinterrupt.
  • the gNB or the UE repeats the transmission of the positioning reference signals which are close in time with a Tinterrupt period (i.e., the positioning reference signals may be before, during or after the interruption period).
  • the number of repetitions may be configured/preconfigured to the UE.
  • the number of repetitions may also depend on the length of the interruption period. Longer the interruption period, more repetitions are allowed. Shorter the interruption period, fewer repetitions are allowed.
  • the number of repetitions may also depend on the frequency of the interruption period. More often the interruption period occurs, more repetitions are allowed. Less often the interruption period occurs, fewer repetitions are allowed.
  • RACH-less handover is introduced for positioning procedure.
  • UE or gNB shall report positioning failure to LMF if positioning procedure isn't completed before handover.
  • the gNB triggers a handover earlier or later Xms than the time when the HO is supposed to trigger, to allow the positioning reference signaling transmission or reception occurs without being interrupted.
  • the UE triggers a conditional handover earlier or later Xms than the time when the CHO is supposed to trigger, to allow the positioning reference signaling transmission or reception occurs without being interrupted by the CHO.
  • the UE may execute at the least one of below optional actions:
  • positioning measurement request and configurations to the target gNB is contained in inter-gNB information exchange prior to or within handover, which will facilitate for the target gNB to configure transmission or measurements for a UE.
  • the target gNB after handover doesn't need to be triggered positioning procedure by LMF.
  • the target gNB can be ready to transmit or receive positioning reference signal for the UE immediately after the handover is completed, and therefore beneficial to reduce the HO latency imposed on the positioning procedure.
  • more messages or information on signaling procedure are exchange between the serving gNB and target gNB, e.g., the start/eclipsed time on positioning, the reference signal samples transmitted/received before handover.
  • positioning measurement request and configurations to the target gNB is contained in UL transmission/signaling in a handover, e.g., RACH procedure or instantaneously after the handover, which will facilitate for the target gNB to configure transmission or measurements for a UE.
  • target gNB after handover doesn't need to be triggered positioning procedure by LMF.
  • the target gNB can be ready to transmit or receive positioning reference signal for the UE immediately after the handover is completed, and therefore beneficial to reduce the HO latency imposed on the positioning procedure
  • more messages or information on signaling procedure are exchange between the UE and target gNB, e.g., the start/eclipsed time on positioning, the reference signal samples transmitted/received before handover.
  • the LMF sends positioning requests, configurations and assistance information to gNB supporting RACH-less handover provided UE supports RACH-less handover.
  • the LMF receives a signaling from the gNB or the UE indicating an interruption period caused by a handover for the UE, the LMF may perform one of the below options to mitigate the interruption without affecting the positioning procedure to fail:
  • the LMF sends the signaling to the gNB or the UE indicating that the originally planned/ongoing positioning reference signaling transmission and/or reception can be delayed Xms (e.g., wait until the interruption period ends).
  • Option 2 the LMF the signaling to the gNB or the UE indicating that the originally planned reference signaling transmission and/or reception can be triggered earlier Xms (e.g., before the interruption period starts).
  • Option 3 the LMF the signaling to the gNB or the UE additional positioning reference signaling resources for the current configured TRPs, which can be used for additional positioning measurements by the gNB or the UE. so the negative impact on the positioning procedure can be minimized.
  • the LMF the signaling to the gNB or the UE additional positioning reference signaling resources for the additional TRPs, which can be used for additional positioning measurements by the gNB or the UE. So the negative impact on the positioning procedure can be minimized.
  • the LMF may also signal the gNB or the UE that the on-going positioning procedure is prolonged with Yms to accommodate the interruption period.
  • the LMF may also signal the gNB or the UE that the on-going positioning procedure is terminated earlier with respect to the interruption period.
  • Figures 15-21 each illustrate an example method according to some of the techniques described above. Each of these methods is intended to be a generalization of at least a subset of the techniques described above, with respect to a particular function, node, or set of nodes, in the communications network, e.g., a UE, base station (which may form part of or be associated with a satellite), or positioning node.
  • the terminology used to describe these figures differs from that used above, the terminology used below should be understood, wherever reasonably possible, to at least encompass the similar or clearly related terminology used above.
  • Figure 15 illustrates a method in one or more network nodes configured to operate as a base station of a wireless communications network.
  • This base station may form part of or be associated with a non-terrestrial satellite, in some embodiments.
  • the method shown in Figure 15 includes, as shown at block 1510, adapting the transmitting of one or more positioning reference signals based on an interruption in connectivity resulting from handover of a user equipment, UE, to or from the gNB. As shown at block 1520, the method further comprises adapting timing for triggering a handover of the UE, based on timing of transmitting positioning reference signals.
  • adapting the transmitting of one or more positioning reference signals comprises adapting transmission of a positioning reference signal to be a predetermined time before a handover command for the handover. In some of these or in other embodiments or instances, adapting the transmitting of one or more positioning reference signals may comprise adapting transmission of a positioning reference signal to be a predetermined time after a handover command for the handover.
  • adapting the transmitting of one or more positioning reference signals comprises repeating, after the interruption, transmission of one or more positioning reference signals transmitted during the interruption.
  • adapting the transmitting of one or more positioning reference signals may comprise repeating, after the interruption, transmission of one or more positioning reference signals transmitted within a predetermined interval before or after the interruption. This may comprise repeating transmission of one or more positioning reference signals a number of times that depends on a length or estimated length of the interruption.
  • adapting the transmitting of one or more positioning reference signals comprises skipping transmission of one or more positioning reference signals during the interruption.
  • Figure 16 illustrates an example method, as carried out in a user equipment (UE) or, more generally, a wireless device.
  • the method comprises, as shown at block 1610, initiating a positioning procedure involving at least one cell in a non-terrestrial network, NTN.
  • the method further comprises performing a RACH-less handover prior to completion of the positioning procedure.
  • the method comprises completing the positioning procedure after performing the RACH-less handover.
  • Figure 17 illustrates an example method as carried out in one or more network nodes configured to operate as a base station of a wireless communications network. This example method comprises, as shown at block 1710, determining that a positioning procedure for a UE served by the base station cannot be completed prior to an imminent handover.
  • the method further comprises, in response to this determination, performing at least one of the following actions: sending a positioning procedure failure message to an LMF; informing the UE that the serving base station cannot complete positioning of the UE; requesting a neighbor base station to continue and/or start positioning of the UE after handover; requesting a neighbor base station to start positioning of the UE immediately, before the handover is completed; and sending, to the LMF, and indication of a connectivity interruption time corresponding to the handover.
  • Figure 18 illustrates another example method carried out in a UE.
  • the method comprises determining that a positioning procedure for the UE cannot be completed prior to an imminent handover.
  • the method further comprises, in response to this determination, performing at least one of the following actions: sending a positioning procedure failure message to an LMF; informing a serving base station that the UE cannot complete positioning; requesting a neighbor base station to continue and/or start positioning of the UE after handover, and performing measurements of a cell provided by the neighbor base station, after the handover; requesting a neighbor base station to start positioning of the UE immediately, before the handover is completed, and performing measurements of a cell provided by neighbor base station; and sending, to the LMF, an indication of a connectivity interruption time corresponding to the handover.
  • Figure 19 shows another method implemented in one or more network nodes configured to operate as a base station of a wireless communications network.
  • This example method comprises determining that a UE served by the base station is to be handed over to a target base station, as shown at block 1910.
  • the method further comprises, in response to this determination, including positioning measurement configuration and/or a positioning measurement request in handover messaging and/or in messaging associated with handover messaging.
  • Figure 20 illustrates yet another example method, in one or more network nodes configured to operate as a base station of a wireless communications network.
  • this method comprises the step of receiving positioning measurement configuration information and/or a positioning measurement request in handover messaging and/or in messaging associated with handover messaging, the handover messaging being for UE being handed over to the base station.
  • This method further comprises, as shown at block 2020, the step of performing positioning of the UE based on the positioning measurement configuration information and/or the positioning measurement request, upon completion of handover of the UE to the base station.
  • performing positioning of the UE comprises transmitting positioning reference signals to the UE and/or performing measurements of positioning reference signals transmitted by the UE.
  • Figure 21 shows a method implemented in one or more network nodes configured to operate as a location management function (LMF).
  • This method comprises, as shown at block 2110, receiving an indication of an interruption period caused by a handover for a UE.
  • the method further comprises, as shown at block 2120, performing one or more of the following, in response to the indication: sending first signaling to the UE and/or a base station serving the UE, the first signaling indicating that reception and/or transmission of positioning reference signaling by the UE and/or base station can be delayed; sending second signaling to the UE and/or a base station serving the UE, the second signaling indicating that reception and/or transmission of positioning reference signaling by the UE and/or base station should be triggered in advance of the interruption period; sending third signaling to the UE and/or a base station serving the UE, the third signaling indicating additional resources for positioning reference signaling resources for use by transmission points previously configured to transmit positioning reference signaling for use in positioning the UE; and sending fourth signaling
  • the method may comprise signaling, to the UE or base station, that an ongoing positioning procedure for the UE is to be prolonged to accommodate the interruption period. In other embodiments or instances, the method may comprise signaling, to the UE or base station, that an ongoing positioning procedure for the UE is to be terminated earlier than previously configured, to accommodate the interruption period.
  • FIG 22 shows an example of a communication system 2200 in accordance with some embodiments.
  • this communication system 2200 may include one or more base stations implemented as part of or in association with respective NTN satellites.
  • the communication system 2200 includes a telecommunication network 2202 that includes an access network 2204, such as a radio access network (RAN), and a core network 2206, which includes one or more core network nodes 2208.
  • the access network 2204 includes one or more access network nodes, such as network nodes 2210a and 2210b (one or more of which may be generally referred to as network nodes 2210), 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.
  • the telecommunication network 2202 includes one or more Open-RAN (ORAN) network nodes.
  • ORAN Open-RAN
  • An ORAN network node is a node in the telecommunication network 2202 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 2202, including one or more network nodes 2210 and/or core network nodes 2208.
  • 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 O-RAN Alliance or comparable technologies.
  • the network nodes 2210 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 2212a, 2212b, 2212c, and 2212d (one or more of which may be generally referred to as UEs 2212) to the core network 2206 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 2200 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 2200 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 2212 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 2210 and other communication devices.
  • the network nodes 2210 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 2212 and/or with other network nodes or equipment in the telecommunication network 2202 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 2202.
  • the core network 2206 connects the network nodes 2210 to one or more hosts, such as host 2216. 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 2206 includes one more core network nodes (e.g., core network node 2208) 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 2208.
  • 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 2216 may be under the ownership or control of a service provider other than an operator or provider of the access network 2204 and/or the telecommunication network 2202, and may be operated by the service provider or on behalf of the service provider.
  • the host 2216 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 telecommunication network 2202 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 2202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 2202. For example, the telecommunications network 2202 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 2212 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 2204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 2204.
  • 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 2214 communicates with the access network 2204 to facilitate indirect communication between one or more UEs (e.g., UE 2212c and/or 2212d) and network nodes (e.g., network node 2210b).
  • the hub 2214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 2214 may be a broadband router enabling access to the core network 2206 for the UEs.
  • the hub 2214 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 2214 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 2214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 2214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 2214 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 2214 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 2214 may have a constant/persistent or intermittent connection to the network node 2210b.
  • the hub 2214 may also allow for a different communication scheme and/or schedule between the hub 2214 and UEs (e.g., UE 2212c and/or 2212d), and between the hub 2214 and the core network 2206.
  • the hub 2214 is connected to the core network 2206 and/or one or more UEs via a wired connection.
  • the hub 2214 may be configured to connect to an M2M service provider over the access network 2204 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 2210 while still connected via the hub 2214 via a wired or wireless connection.
  • the hub 2214 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 2210b.
  • the hub 2214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 2210b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • 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 customerpremise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • gaming console or device 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 customerpremise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-loT 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 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 for sale to, or operation by,
  • the UE 2300 includes processing circuitry 2302 that is operatively coupled via a bus 2304 to an input/output interface 2306, a power source 2308, a memory 2310, a communication interface 2312, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 23. 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 2302 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 2310.
  • the processing circuitry 2302 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 2302 may include multiple central processing units (CPUs).
  • the input/output interface 2306 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 2300.
  • 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 2308 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 2308 may further include power circuitry for delivering power from the power source 2308 itself, and/or an external power source, to the various parts of the UE 2300 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 2308.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 2308 to make the power suitable for the respective components of the UE 2300 to which power is supplied.
  • the memory 2310 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 2310 includes one or more application programs 2314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 2316.
  • the memory 2310 may store, for use by the UE 2300, any of a variety of various operating systems or combinations of operating systems.
  • the memory 2310 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 (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as 'SIM card.
  • the memory 2310 may allow the UE 2300 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 2310, which may be or comprise a device-readable storage medium.
  • the processing circuitry 2302 may be configured to communicate with an access network or other network using the communication interface 2312.
  • the communication interface 2312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 2322.
  • the communication interface 2312 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 2318 and/or a receiver 2320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 2318 and receiver 2320 may be coupled to one or more antennas (e.g., antenna 2322) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 2312 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/internet 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/internet 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 2312, 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- or item-t
  • AR Augmented
  • 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 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-loT 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. 24 shows a network node 2400 in accordance with some embodiments.
  • 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, O-DU, O-CU).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • O-RAN nodes or components of an O-RAN node e.g., O-RU, O-DU, O-CU.
  • a network node 2400 may
  • 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 2400 includes a processing circuitry 2402, a memory 2404, a communication interface 2406, and a power source 2408.
  • the network node 2400 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 2400 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 2400 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 2404 for different RATs) and some components may be reused (e.g., a same antenna 2410 may be shared by different RATs).
  • the network node 2400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2400, 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 2400.
  • RFID Radio Frequency Identification
  • the processing circuitry 2402 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 2400 components, such as the memory 2404, to provide network node 2400 functionality.
  • the processing circuitry 2402 includes a system on a chip (SOC).
  • the processing circuitry 2402 includes one or more of radio frequency (RF) transceiver circuitry 2412 and baseband processing circuitry 2414.
  • RF radio frequency
  • the radio frequency (RF) transceiver circuitry 2412 and the baseband processing circuitry 2414 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 2412 and baseband processing circuitry 2414 may be on the same chip or set of chips, boards, or units.
  • the memory 2404 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 2402.
  • 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-
  • the memory 2404 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 2402 and utilized by the network node 2400.
  • the memory 2404 may be used to store any calculations made by the processing circuitry 2402 and/or any data received via the communication interface 2406.
  • the processing circuitry 2402 and memory 2404 is integrated.
  • the communication interface 2406 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 2406 comprises port(s)/terminal(s) 2416 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 2406 also includes radio front-end circuitry 2418 that may be coupled to, or in certain embodiments a part of, the antenna 2410. Radio front-end circuitry 2418 comprises filters 2420 and amplifiers 2422.
  • the radio front-end circuitry 2418 may be connected to an antenna 2410 and processing circuitry 2402.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 2410 and processing circuitry 2402.
  • the radio front-end circuitry 2418 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 2418 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2420 and/or amplifiers 2422.
  • the radio signal may then be transmitted via the antenna 2410.
  • the antenna 2410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2418.
  • the digital data may be passed to the processing circuitry 2402.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 2400 does not include separate radio frontend circuitry 2418, instead, the processing circuitry 2402 includes radio front-end circuitry and is connected to the antenna 2410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2412 is part of the communication interface 2406. In still other embodiments, the communication interface 2406 includes one or more ports or terminals 2416, the radio front-end circuitry 2418, and the RF transceiver circuitry 2412, as part of a radio unit (not shown), and the communication interface 2406 communicates with the baseband processing circuitry 2414, which is part of a digital unit (not shown).
  • the antenna 2410 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 2410 may be coupled to the radio front-end circuitry 2418 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 2410 is separate from the network node 2400 and connectable to the network node 2400 through an interface or port.
  • the antenna 2410, communication interface 2406, and/or the processing circuitry 2402 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 2410, the communication interface 2406, and/or the processing circuitry 2402 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 2408 provides power to the various components of network node 2400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 2408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2400 with power for performing the functionality described herein.
  • the network node 2400 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 2408.
  • the power source 2408 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 2400 may include additional components beyond those shown in Figure 24 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 2400 may include user interface equipment to allow input of information into the network node 2400 and to allow output of information from the network node 2400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2400.
  • FIG 25 is a block diagram of a host 2500, which may be an embodiment of the host 2216 of Figure 22, in accordance with various aspects described herein.
  • the host 2500 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 2500 may provide one or more services to one or more UEs.
  • the host 2500 includes processing circuitry 2502 that is operatively coupled via a bus 2504 to an input/output interface 2506, a network interface 2508, a power source 2510, and a memory 2512.
  • processing circuitry 2502 that is operatively coupled via a bus 2504 to an input/output interface 2506, a network interface 2508, a power source 2510, and a memory 2512.
  • 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 23 and 24, such that the descriptions thereof are generally applicable to the corresponding components of host 2500.
  • the memory 2512 may include one or more computer programs including one or more host application programs 2514 and data 2516, which may include user data, e.g., data generated by a UE for the host 2500 or data generated by the host 2500 for a UE.
  • Embodiments of the host 2500 may utilize only a subset or all of the components shown.
  • the host application programs 2514 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 2514 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 2500 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 2514 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. 26 is a block diagram illustrating a virtualization environment 2600 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 2600 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 2600 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.
  • Applications 2602 (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 2604 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 2606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2608a and 2608b (one or more of which may be generally referred to as VMs 2608), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 2606 may present a virtual operating platform that appears like networking hardware to the VMs 2608.
  • the VMs 2608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2606.
  • a virtualization layer 2606 Different embodiments of the instance of a virtual appliance 2602 may be implemented on one or more of VMs 2608, 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 2608 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 2608, and that part of hardware 2604 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 2608 on top of the hardware 2604 and corresponds to the application 2602.
  • Hardware 2604 may be implemented in a standalone network node with generic or specific components. Hardware 2604 may implement some functions via virtualization. Alternatively, hardware 2604 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 2610, which, among others, oversees lifecycle management of applications 2602.
  • hardware 2604 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 2612 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 27 shows a communication diagram of a host 2702 communicating via a network node 2704 with a UE 2706 over a partially wireless connection in accordance with some embodiments.
  • UE such as a UE 2212a of Figure 22 and/or UE 2300 of Figure 23
  • network node such as network node 2210a of Figure 22 and/or network node 2400 of Figure 24
  • host such as host 2216 of Figure 22 and/or host 2500 of Figure 25
  • embodiments of host 2702 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 2702 also includes software, which is stored in or accessible by the host 2702 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 2706 connecting via an over-the-top (OTT) connection 2750 extending between the UE 2706 and host 2702.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 2750.
  • the network node 2704 includes hardware enabling it to communicate with the host 2702 and UE 2706.
  • the connection 2760 may be direct or pass through a core network (like core network 2206 of Figure 22) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 2206 of Figure 22
  • 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 2706 includes hardware and software, which is stored in or accessible by UE 2706 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 nonhuman user via UE 2706 with the support of the host 2702.
  • a client application such as a web browser or operator-specific "app" that may be operable to provide a service to a human or nonhuman user via UE 2706 with the support of the host 2702.
  • an executing host application may communicate with the executing client application via the OTT connection 2750 terminating at the UE 2706 and host 2702.
  • 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 2750 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 2
  • the OTT connection 2750 may extend via a connection 2760 between the host 2702 and the network node 2704 and via a wireless connection 2770 between the network node 2704 and the UE 2706 to provide the connection between the host 2702 and the UE 2706.
  • the connection 2760 and wireless connection 2770, over which the OTT connection 2750 may be provided, have been drawn abstractly to illustrate the communication between the host 2702 and the UE 2706 via the network node 2704, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 2702 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 2706.
  • the user data is associated with a UE 2706 that shares data with the host 2702 without explicit human interaction.
  • the host 2702 initiates a transmission carrying the user data towards the UE 2706.
  • the host 2702 may initiate the transmission responsive to a request transmitted by the UE 2706.
  • the request may be caused by human interaction with the UE 2706 or by operation of the client application executing on the UE 2706.
  • the transmission may pass via the network node 2704, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2712, the network node 2704 transmits to the UE 2706 the user data that was carried in the transmission that the host 2702 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2714, the UE 2706 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2706 associated with the host application executed by the host 2702.
  • the UE 2706 executes a client application which provides user data to the host 2702.
  • the user data may be provided in reaction or response to the data received from the host 2702.
  • the UE 2706 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 2706. Regardless of the specific manner in which the user data was provided, the UE 2706 initiates, in step 2718, transmission of the user data towards the host 2702 via the network node 2704.
  • the network node 2704 receives user data from the UE 2706 and initiates transmission of the received user data towards the host 2702.
  • the host 2702 receives the user data carried in the transmission initiated by the UE 2706.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 2706 using the OTT connection 2750, in which the wireless connection 2770 forms the last segment. More precisely, the teachings of these embodiments may improve positioning performance in the context of handovers, thus ensuring that OTT services have timely, updated, positioning information.
  • factory status information may be collected and analyzed by the host 2702.
  • the host 2702 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 2702 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 2702 may store surveillance video uploaded by a UE.
  • the host 2702 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 2702 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 2702 and/or UE 2706.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2750 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 2750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2704. 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 2702.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 2750 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.
  • Embodiments of the techniques described above include, but are not limited to, the following examples:
  • a method in one or more network nodes configured to operate as a base station of a wireless communications network, the method comprising: adapting the transmitting of one or more positioning reference signals based on an interruption in connectivity resulting from handover of a user equipment, UE, to or from the gNB; and/or adapting timing for triggering a handover of the UE, based on timing of transmitting positioning reference signals.
  • said adapting the transmitting of one or more positioning reference signals comprises adapting transmission of a positioning reference signal to be a predetermined time before a handover command for the handover.
  • said adapting the transmitting of one or more positioning reference signals comprises adapting transmission of a positioning reference signal to be a predetermined time after a handover command for the handover.
  • a method in a user equipment, UE, the method comprising: initiating a positioning procedure involving at least one cell in a non-terrestrial network, NTN; performing a RACH-less handover prior to completion of the positioning procedure; and completing the positioning procedure after performing the RACH-less handover.
  • a method in one or more network nodes configured to operate as a base station of a wireless communications network, the method comprising: determining that a positioning procedure for a user equipment, UE, served by the base station cannot be completed prior to an imminent handover; and, in response to said determining, performing at least one of the following actions: sending a positioning procedure failure message to a location management function, LMF; informing the UE that the serving base station cannot complete positioning of the UE; requesting a neighbor base station to continue and/or start positioning of the UE after handover; requesting a neighbor base station to start positioning of the UE immediately, before the handover is completed; and sending, to the LMF, an indication of a connectivity interruption time corresponding to the handover.
  • LMF location management function
  • a method in a user equipment, UE, the method comprising: determining that a positioning procedure for the UE cannot be completed prior to an imminent handover; and, in response to said determining, performing at least one of the following actions: sending a positioning procedure failure message to a location management function, LMF; informing a serving base station that the UE cannot complete positioning; requesting a neighbor base station to continue and/or start positioning of the UE after handover, and performing measurements of a cell provided by the neighbor base station, after the handover; requesting a neighbor base station to start positioning of the UE immediately, before the handover is completed, and performing measurements of a cell provided by neighbor base station; and sending, to the LMF, an indication of a connectivity interruption time corresponding to the handover.
  • LMF location management function
  • a method in one or more network nodes configured to operate as a base station of a wireless communications network, the method comprising: determining that a user equipment, UE, served by the base station is to be handed over to a target base station; and, responsive to said determining, including positioning measurement configuration and/or a positioning measurement request in handover messaging and/or in messaging associated with handover messaging.
  • performing positioning of the UE comprises transmitting positioning reference signals to the UE and/or performing measurements of positioning reference signals transmitted by the UE.
  • a method in one or more network nodes configured to operate as a location management function, LMF, the method comprising: receiving an indication of an interruption period caused by a handover for a user equipment, UE; and, responsive to the indication, performing one or more of the following: sending first signaling to the UE and/or a base station serving the UE, the first signaling indicating that reception and/or transmission of positioning reference signaling by the UE and/or base station can be delayed; sending second signaling to the UE and/or a base station serving the UE, the second signaling indicating that reception and/or transmission of positioning reference signaling by the UE and/or base station should be triggered in advance of the interruption period; sending third signaling to the UE and/or a base station serving the UE, the third signaling indicating additional resources for positioning reference signaling resources for use by transmission points previously configured to transmit positioning reference signaling for use in positioning the UE; and sending fourth signaling to the UE and/or a base station serving the UE, the fourth signaling indicating
  • example embodiment 15 further comprising signaling, to the UE or base station, that an ongoing positioning procedure for the UE is to be terminated earlier than previously configured, to accommodate the interruption period.
  • a UE adapted to carry out a method according to example embodiment 9 or 11.
  • a UE comprising radio circuitry configured to communicate with a wireless network and processing circuitry operatively coupled to the radio circuitry, the processing circuitry being configured to control the radio circuitry to carry out a method according to example embodiment 9 or 11.
  • a network node or nodes comprising radio circuitry configured to communicate with one or more user equipments, UE, and processing circuitry operatively coupled to the radio circuitry, the processing circuitry being configured to control the radio circuitry to carry out a method according to any one of example embodiments 1-8, 10, and 12-14.
  • LMF location management function
  • a location management function comprising communication interface circuitry configured to communicate with one or more other nodes in a communication network and further comprising processing circuitry operatively coupled to the communication interface circuitry, the processing circuitry being configured to carry out a method according to example embodiment 15.

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

Des procédés et des appareils de réduction d'interruption de positionnement comprennent un procédé donné à titre d'exemple dans un équipement utilisateur, UE, le procédé donné à titre d'exemple consistant à déterminer qu'une procédure de positionnement pour l'UE ne peut pas être achevée avant un transfert imminent et, en réponse, à effectuer au moins une action parmi plusieurs actions. Ces plusieurs actions consistent à : envoyer un message d'échec de procédure de positionnement à une fonction de gestion d'emplacement, LMF ; informer une station de base de desserte que l'UE ne peut pas effectuer un positionnement ; demander à une station de base voisine de continuer et/ou de démarrer le positionnement de l'UE après le transfert, et effectuer des mesures d'une cellule fournie par la station de base voisine, après le transfert ; demander à une station de base voisine de démarrer le positionnement de l'UE immédiatement, avant que le transfert ne soit achevé, et effectuer des mesures d'une cellule fournie par une station de base voisine ; et envoyer, à la LMF, une indication d'un temps d'interruption de connectivité correspondant au transfert.
PCT/EP2024/082170 2023-11-13 2024-11-13 Procédé et appareil de réduction d'interruption de positionnement dans un ntn Pending WO2025104082A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363548310P 2023-11-13 2023-11-13
US63/548,310 2023-11-13

Publications (1)

Publication Number Publication Date
WO2025104082A1 true WO2025104082A1 (fr) 2025-05-22

Family

ID=93650344

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2024/082170 Pending WO2025104082A1 (fr) 2023-11-13 2024-11-13 Procédé et appareil de réduction d'interruption de positionnement dans un ntn

Country Status (1)

Country Link
WO (1) WO2025104082A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110636571B (zh) * 2018-06-25 2021-03-16 电信科学技术研究院有限公司 一种终端ue位置服务lcs的确定方法、设备及可读存储介质
US11368892B2 (en) * 2018-08-24 2022-06-21 Qualcomm Incorporated Positioning enhancements for narrowband mobile devices
US20230007556A1 (en) * 2020-03-13 2023-01-05 Ofinno, Llc Handover
WO2023003342A2 (fr) * 2021-07-20 2023-01-26 삼성전자 주식회사 Procédé et dispositif de traitement de multiples qualités de service à des fins de positionnement
CN115942450A (zh) * 2021-08-06 2023-04-07 大唐移动通信设备有限公司 配置上行定位参考信号的方法、设备及可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110636571B (zh) * 2018-06-25 2021-03-16 电信科学技术研究院有限公司 一种终端ue位置服务lcs的确定方法、设备及可读存储介质
US11368892B2 (en) * 2018-08-24 2022-06-21 Qualcomm Incorporated Positioning enhancements for narrowband mobile devices
US20230007556A1 (en) * 2020-03-13 2023-01-05 Ofinno, Llc Handover
WO2023003342A2 (fr) * 2021-07-20 2023-01-26 삼성전자 주식회사 Procédé et dispositif de traitement de multiples qualités de service à des fins de positionnement
CN115942450A (zh) * 2021-08-06 2023-04-07 大唐移动通信设备有限公司 配置上行定位参考信号的方法、设备及可读存储介质

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
US20250287461A1 (en) Ephemeris data for conditional handover
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
US20240406760A1 (en) Minimization of Drive Testing for Non-Terrestrial Networks
WO2024035301A1 (fr) Informations d'emplacement pour mobilité en ntn
EP4463950A1 (fr) Systèmes et procédés de transfert temporel dans des réseaux non terrestre
WO2023096556A1 (fr) Systèmes et procédés pour la prise en charge de l'ajustement autonome d'une avance temporelle
WO2024136737A1 (fr) Procédés de positionnement basés sur un réseau de réseau non terrestre (ntn)
US20250203426A1 (en) Reporting of NTN-Related SON Information
WO2024208975A1 (fr) Procédés pour faciliter une mesure du gnss pour un ue ntn ido
EP4666644A1 (fr) Activation d'intervalles de mesure pour ntn
US20250253939A1 (en) System and methods for regulatory-aware access to network resources over satellites
WO2025104082A1 (fr) Procédé et appareil de réduction d'interruption de positionnement dans un ntn
WO2025179533A1 (fr) Procédés et appareils pour un service en mode différé dans un réseau non terrestre (ntn)
WO2024169954A1 (fr) Procédés et appareils de positionnement d'un dispositif terminal
WO2025216685A1 (fr) Indication de transfert intercellulaire réussi lorsque certaines conditions indiquent une défaillance de transfert intercellulaire
WO2025153889A1 (fr) Transfert de ntn à l'aide de diagrammes de sauts de faisceau
WO2024209425A1 (fr) Positionnement de ntn à l'aide de mesures de cellules voisines
WO2024176171A1 (fr) Procédés de chaîne cho dans ntn
WO2025210593A1 (fr) Indication de stockage et de transfert pour ntn
WO2025193131A1 (fr) Nœud de réseau, équipement utilisateur et procédés associés, dans un réseau de communications sans fil
WO2025037214A1 (fr) Positionnement pour équipement utilisateur dans un scénario de connectivité multiple de réseau non terrestre

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

Country of ref document: EP

Kind code of ref document: A1