WO2024033805A1 - Procédés pour indiquer des mesurages de positionnement de nœud iab mobile dans le réseau - Google Patents

Procédés pour indiquer des mesurages de positionnement de nœud iab mobile dans le réseau Download PDF

Info

Publication number
WO2024033805A1
WO2024033805A1 PCT/IB2023/058005 IB2023058005W WO2024033805A1 WO 2024033805 A1 WO2024033805 A1 WO 2024033805A1 IB 2023058005 W IB2023058005 W IB 2023058005W WO 2024033805 A1 WO2024033805 A1 WO 2024033805A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
message
indication
trp
network
Prior art date
Application number
PCT/IB2023/058005
Other languages
English (en)
Inventor
Ritesh SHREEVASTAV
Mohammed Yazid LYAZIDI
Filip BARAC
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2024033805A1 publication Critical patent/WO2024033805A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/005—Moving wireless networks
    • 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

Definitions

  • This application generally relates to wireless communications and more specifically to indicating mobile IAB node positioning measurements.
  • Positioning has been a topic in Long Term Evolution (LTE) standardization since Release (Rel.) 9 of the 3rd Generation Partnership Project (3GPP). The primary objective was initially to fulfill regulatory requirements for emergency call positioning but other use cases like positioning for Industrial Internet of Things (LIoT) are becoming important. Positioning in New Radio (NR) is supported, e.g., by the architecture shown in Fig. 1.
  • the Location Management Function (LMF) is the location node in NR.
  • gNB gNodeB
  • NRPPa NR Positioning Protocol A
  • the interactions between the gNB and the device is supported via the Radio Resource Control (RRC) protocol, while the location node interfaces with the User Equipment (UE) via the LTE Positioning Protocol (LPP).
  • LPP is common to both NR and LTE.
  • Fig. 1 shows both a gNB and a new generation (ng)-eNB, both may not always be present.
  • the NG-C is generally only present for one of them.
  • the NG-Radio Access Network (RAN) can comprise a gNB and a ng-eNB or the NG-RAN can only comprise one of them.
  • the gNB can have several Transmission Reception Points (TRPs) and the ng- eNB can have several Transmission Points (TPs).
  • NR supports RAT dependent positioning methods, such as Downlink (DL)-Time Difference of Arrival (TDOA), Multi- Round Trip Time (RTT), Uplink (UL)-TDOA, DL- Angle of Departure (AoD), UL-AoA, NR-Enhanced Cell IDentityJECID), etc.
  • 5G networks are being designed and deployed considering a dense deployment of small cells in order to simultaneously serve more UEs with higher throughput and lower delay.
  • building from scratch a completely new infrastructure is costly and takes time.
  • Deploying a wireless backhaul is then envisioned to be an economically and technically viable approach to enable flexible and dense network.
  • IAB is based on the Centralized Unit (CU)-Distributed Unit (DU) split that was standardized in Rel. 15.
  • the CU is in charge of the radio resource control (RRC) and the packet data convergence (PCDP) protocol, whereas the DU is in charge of the radio link control (RLC) and media access control (MAC).
  • RRC radio resource control
  • PCDP packet data convergence
  • MAC media access control
  • the Fl interface connects the CU and the DU.
  • the CU-DU split facilitates separate physical CU and DU, while also allowing a single CU to be connected to multiple DUs.
  • Fig. 2 shows the basic architecture of IAB.
  • the architecture of Fig. 2 comprises a single IAB donor connected to the core network.
  • the IAB donor serves three direct IAB child nodes through two collocated DUs at the donor for wireless backhauling.
  • the center IAB node in turn serves two IAB nodes through wireless backhaul. All IAB nodes in the figure backhauls traffic both related to UEs connected to it, and other backhaul traffic from downstream IAB nodes.
  • the main components of the IAB architecture are:
  • IAB Node A node that allows wireless access to the UEs while also backhauling the traffic to other nodes.
  • the IAB node comprises a DU that provides access to connected UEs.
  • the node also comprises a mobile termination (MT) that connects to other IAB nodes or donors in the uplink direction for backhaul.
  • MT mobile termination
  • IAB Donor A node that provides UEs an interface to the core network and wireless functionality to other lAB-nodes to backhaul their traffic to the core network.
  • IAB was standardized with basic support for multi-hop multi-path backhaul for directed acyclic graph (DAG) topology, no mesh-based topology was supported.
  • DAG directed acyclic graph
  • Rel. 16 also supports Quality of Service (QoS) prioritization of backhaul traffic and flexible resource usage between access and backhaul.
  • QoS Quality of Service
  • Current discussions in Rel. 17 are on topology enhancements for IAB with partial migration of IAB nodes for Radio Link Failure (RLF) recovery and load balancing.
  • RLF Radio Link Failure
  • VMR mobile-IAB/vehicle mounted relays
  • One of the main use cases of mobile IAB cell is to serve the UEs which are residing in the vehicle with the vehicle mounted relay.
  • Other relevant use cases for mobile lABs involve a mobile/nomadic IAB network node mounted on a vehicle that provides extended coverage. This involves scenarios where additional coverage is required during special events like concerts, during disasters.
  • the nomadic IAB node provides access to surrounding UEs while the backhaul traffic from the nomadic IAB node is then transmitted wirelessly either with the help of IAB donors or Non-terrestrial networks (NTN).
  • NTN Non-terrestrial networks
  • a nomadic IAB node also reduces or even eliminates signal strength loss due to vehicle penetration for UEs that are present in the vehicles.
  • Advantages of Mobile IAB are: reducing/eliminating the vehicle penetration loss (specially at high frequency), and reducing/eliminating group handover.
  • an IAB node can be a gNB/network node.
  • a mobile IAB node hosting a TRP may provide different measurement results, in terms of latency and accuracy, compared to a static TRP.
  • some positioning methods may not be usable in this case, or the accuracy improvement methods defined in the positioning 3 GPP Rel.17 version may no longer be valid.
  • This disclosure provides support for mobile TRP capability signaling as a new definition in TS 38.305, as well as new code points in the NRPPa and F1AP messages between the gNB-CU and LMF, and the gNB-DU and gNB-CU, respectively. New indicators for the position of the mobile IAB as a new type of measurement result are added in the specific NRPPa and F1AP messages, for the exchange of positioning measurements.
  • a new codepoint or information element (IE) for mobile TRP capability can be added in the F1AP and NRPPA TRP INFORMATION RESPONSE message.
  • the LMF can prepare the recommendation for PRS transmission, positioning with SRS and/or measurement request procedure accordingly.
  • a new codepoint or IE for mobile TRP positioning can be added in the F1AP and NRPPA MEASUREMENT RESPONSE message. Upon reception of such an indication, the LMF can use it for UE’s positioning location estimation.
  • a mechanism for the LMF to inquire the gNB/AMF about the IDs of the UEs onboard the vehicle hosting the mobile IAB node is also provided.
  • the method comprises: sending a first message to a second network node, for requesting a type of network node of the second network node; in response to the first message, receiving an indication of the type of network node of the second network node, the type of network node of the second network node being a mobile network node; sending a second message to the second network node, for requesting location information of the second network node, based on the type of network node; and in response to the second message, receiving an indication of the location information from the second network node.
  • the method comprises: receiving a first message for requesting a type of network node, from a second network node; in response to the first message, sending an indication of the type of network node of the first network node to the second network node, the type of network node of the first network node being a mobile network node; receiving a second message for requesting location information of the first network node, based on the type of network node; and in response to the second message, sending an indication of the location information to the second network node.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the LMF is aware of which TRPs hosted by the gNB/IAB node can be mobile and take appropriate actions (e.g. include the mobile TRP into the positioning assistance data or not).
  • the LMF implicitly knows the position of the other UEs onboard and, thus, it does not have to run a separate positioning procedure for each UE.
  • FIG. 1 illustrates an example of a positioning architecture in NR, where NG-RAN LCS protocols are also shown.
  • Fig. 2 illustrates an example of an IAB basic architecture.
  • Fig. 3 illustrates an example of a signaling diagram between a TRP and LMF according to some embodiments.
  • Fig. 4 illustrates an example of a flow chart of a method in a first network node, according to some embodiments.
  • Fig. 5 illustrates an example of a flow chart of a method in a first network node, according to some embodiments.
  • FIG. 6 shows an example of a communication system, according to an embodiment.
  • Fig. 7 shows a schematic diagram of a UE, according to an embodiment.
  • Fig. 8 shows a schematic diagram of a network node, according to an embodiment.
  • Fig. 9 illustrates a block diagram illustrating a virtualization environment.
  • the mobile IAB as such is used for coverage extension and to improve the passenger’s UE Quality of experience in the vehicle (e.g. bus/train, etc.). It can happen that there are not many static TRPs available and the LMF may need to either include the mobile IAB or exclude the mobile IAB. If the mobile IAB is excluded, the LMF may further use hybrid or other positioning methods, such as Global navigation satellite system (GNSS) Sensor based methods.
  • GNSS Global navigation satellite system
  • the decision to include/exclude the mobile IAB can depend on how accurately the mobile IAB position can be estimated, for example, if it is synchronized with Global Positioning System (GPS) with regards to timing estimations and/or if it is moving with some constant acceleration.
  • GPS Global Positioning System
  • the LMF can obtain the mobile IAB positioning measurements and estimates the positioning error. If the error is within an acceptable limit, it instructs the mobile IAB-DU (TRP(s)) to transmit PRS or perform RTOA measurement.
  • the LMF may also obtain the sensor-based measurements, such as via an accelerometer, and other measurements, such as velocity, and also decide whether the mobile IAB should be included or excluded from the position measurements, even when the mobile IAB is capable of taking part or perform positioning measurements.
  • Fig. 3 an example of a method (or a mechanism) 100 will described, whereby the LMF may decide whether to:
  • [0050] - include or exclude a mobile TRP as part of the assistance data for positioning;
  • the method 100 comprises:
  • step 110 the TRP sends a message to the LMF, indicating to the LMF that it is a mobile IAB node.
  • step 120 the LMF sends a message to the TRP, with a request for positioning measurements, for example.
  • the TRP Upon receipt of the request, the TRP performs the requested measurements. And in step 130, the TRP provides/sends the measurements to the LMF.
  • the LMF Upon receipt of the measurements from the TRP, the LMF decides whether the TRP can be part of the positioning assistance data, in step 140. For example, the LMF can estimate the positioning error. If the error is within an acceptable limit, then the LMF decides to include the TRP to be part of the assistance data for positioning. In this case, in step 150, the LMF instructs the TRP to transmit PRS or measure/perform RTOA measurements.
  • the TRP may receive a message from the LMF requesting the type of the TRP (mobile or not), in step 160 (this step may be optional).
  • This message may be sent using NRPPa signalling.
  • the message can be a TRP INFORMATION REQUEST message. Also, this message may be sent using Fl AP signalling.
  • the gNB upon receiving the TRP INFORMATION REQUEST message from the LMF with a request for TRP types (e.g step 160), the gNB sends a response message indicating which of its hosted TRPs is mobile.
  • This new indication can be as a new codepoint within the TRP Type IE or as separate indication in the TRP Information IE.
  • the gNB can further indicate a list of cells or tracking areas where the mobile TRP may move to.
  • This list of cells can be configured in advance or updated by Operation Administration and Maintenance (AOM).
  • AOM Operation Administration and Maintenance
  • the TRP Information IE contains information for one TRP within an NG-RAN node.
  • TR 21.905 [1] For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1],
  • the suffixes "-based” and “-assisted” refer respectively to the node that is responsible for making the positioning calculation (and which may also provide measurements) and a node that provides measurements (but which does not make the positioning calculation).
  • UE-assisted an operation in which measurements are provided by the UE to the LMF to be used in the computation of a position estimate is described as “UE-assisted” (and could also be called “LMF-based"), while one in which the UE computes its own position is described as “UE-based”.
  • Transmission Point A set of geographically co-located transmit antennas (e.g. antenna array (with one or more antenna elements)) for one cell, part of one cell or one DL-PRS-only TP.
  • Transmission Points can include base station (ng-eNB or gNB) antennas, remote radio heads, a remote antenna of a base station, an antenna of a DL-PRS-only TP, etc.
  • One cell can include one or multiple transmission points. For a homogeneous deployment, each transmission point may correspond to one cell.
  • Reception Point A set of geographically co-located receive antennas (e.g. antenna array (with one or more antenna elements)) for one cell, part of one cell or one UL-SRS-only RP.
  • Reception Points can include base station (ng-eNB or gNB) antennas, remote radio heads, a remote antenna of a base station, an antenna of a UL-SRS-only RP, etc.
  • One cell can include one or multiple reception points. For a homogeneous deployment, each reception point may correspond to one cell.
  • PRS-only TP A TP which only transmits PRS signals and is not associated with a cell.
  • SRS-only RP An RP which only receives SRS signals and is not associated with a cell.
  • Transmission-Reception Point A set of geographically co-located antennas (e.g. antenna array (with one or more antenna elements)) supporting TP and/or RP functionality.
  • Mobile TRP A TRP whose location and/or cell ID may change.
  • the TRP is part of mobile IAB-DU. This also implies that a separate Mobile IAB-MT exist which can perform UE positioning.
  • the TRP may be a part of mobile gNB.
  • NRPPA NRPPA
  • the TRP Information IE contains information for one TRP within an NG-RAN node.
  • This IE contains TRP mobility information.
  • This IE contains the IDs of UEs onboard and served by a mobile IAB node.
  • the LMF upon receiving an indication from the gNB that a TRP is mobile (in step 110 of Fig. 3), the LMF can exclude some positioning methods, when the mobile TRP is used for positioning.
  • the NG-RAN/gNB can signal the mobile TRP location or coordinates (X, Y, Z) as a new positioning measurement during the MEASUREMENT RESPONSE message (step 130 of Fig. 3) in the TRP Measurement Result IE.
  • This information element contains the measurement result.
  • supplementary information about whether the TRP is mobile TRP (e.g. step 110 of Fig. 3) is signalled over F1AP.
  • the TRP Information IE contains information for one TRP within a gNB-DU.
  • This IE contains TRP mobility information.
  • the information on the mobile TRP capability with a list of cells and tracking areas where the TRP can move to can be encoded in F1AP (see also the above table).
  • the gNB-DU signals to gNB-CU the mobile TRP location or coordinates (X, Y, Z) as a new positioning measurement during the MEASUREMENT RESPONSE message in the TRP Measurement Result IE
  • This information element is to provide the measurement result(s).
  • a vehicle hosting the mobile IAB node may carry multiple UEs onboard, with a multitude of these UEs being served by the mobile IAB node. This means that all the UEs onboard are located at approximately the same position. Therefore, when knowing the position of one of the UEs indirectly indicates the position of other UEs onboard as well.
  • the lAB-donor-CU serving the mobile IAB-DU knows the IDs of the UEs connected to the mobile IAB-DU (it is reasonable to assume all these UEs are likely all onboard the vehicle). Hence, if the LMF can obtain the position of one of the UEs onboard, it implicitly obtains the positions of other UEs onboard as well.
  • the NG-RAN node (e.g., the gNB) indicates to the LMF the list of UEs that are onboard the vehicle hosting the mobile IAB node and are connected to it. This information can be conveyed, e.g., together with the positioning information pertaining to one of the UEs onboard. In one variant, the information about other UEs onboard is requested by the LMF from the NG-RAN node. In another vatiant, the NG-RAN node provides this information by default, i.e., without being requested. In one variant, it is the AMF that provides this information to the LMF.
  • the AMF or the NG-RAN node may send updates to the LMF with respect to UEs leaving the vehicle, i.e., being handed over to another RAN node.
  • the LMF may subscribe to the periodic updates of the position of the IAB-MT of the mobile IAB node. By being constantly updated about the position of the mobile IAB-MT, the LMF knows the position of all UEs onboard, without having to execute a dedicated positioning procedure for each UE.
  • the UEs may be identified by an existing identifier or by a newly introduced identifier.
  • the above can be achieved by enhancing the existing network signalling, or by defining dedicated signalling.
  • An implementation example can use the NRPPa signalling as described above.
  • Other signalling can be also used, such as F1AP, etc.
  • Step 210 sending a first message to the second network node for requesting a type of network node of the second network node;
  • Step 220 in response to the first message, receiving an indication of the type of network node of the second network node (e.g. TRP), the type of network node of the second network node being a mobile network node;
  • TRP the type of network node of the second network node
  • Step 230 send a second message to the second network node, the second message for requesting location information of the second network node based on the type of network node; and [0080] Step 240: in response to the second message, receiving an indication of the location information from the second network node.
  • the method receives positioning measurements from the second network node. In some examples, the method may determine a positioning error from the received positioning measurements. In some examples, the method may determine that the second network node is used for positioning assistance data when the positioning error is less than a threshold. In some examples, the method may exclude some positioning methods when the second network node is used for positioning assistance data. In some examples, the method may determine that the second network node is excluded for positioning assistance data when the positioning error is more than a threshold. In some examples, the method may send a third message to the second network node, the third message comprising instructions to the second network node to transmit PRS or perform RTOA measurements.
  • the first message can be the same as the second message.
  • the second message can be a TRP INFORMATION REQUEST message.
  • the second message can be a request for location information as part of positioning measurements (e g. POSITIONING MEASUREMENT REQUEST).
  • the first message can be one of a Fl AP message and a NRPPa message.
  • the receipt of the indication of the type of network node can be received in a TRP INFORMATION RESPONSE message.
  • the receipt of the indication of the location information can be received in a TRP INFORMATION RESPONSE message.
  • the receipt of the indication of the location information can be received in a MEASUREMENT RESPONSE message.
  • the location information can comprise an indication of coordinates of the second network node.
  • the location information can also comprise an indication of velocity of the second network node.
  • the first network node may receive, from the second network node, a list of cells or tracking areas where the second network node can move to.
  • the indication of the coordinates can be comprised in a TRP measurement Result (IE.
  • the first network node may receive a list of UEs onboard of a vehicle served by the second network node.
  • a UE can be identified by an Identifier (ID), a new ID or an existing ID or an existing one that is modified.
  • the list of cell and tracking areas can be received in NRPPa or F 1 AP.
  • the method may receive a location or coordinates of the second network node as a positioning measurement in response to the second message.
  • the method may request a location of a first UE from the list to the second network node.
  • the method may receive the location of the first UE from the second node.
  • the method may determine the location of the rest of the UEs in the list based on the location of the first UE.
  • Step 310 receiving a first message for requesting a type of network node, from a second network node;
  • Step 320 in response to the first message, sending an indication of the type of network node of the first network node to the second network node, the type of network node of the first network node being a mobile network node;
  • Step 330 receiving a second message for requesting location information of the first network node, based on the type of network node;
  • Step 340 in response to the second message, sending an indication of the location information to the second network node.
  • the first message can be the same as the second message.
  • the second message can be a TRP INFORMATION REQUEST.
  • the second message can be a request for location information as part of positioning measurements (e.g. POSITIONING MEASUREMENT REQUEST).
  • the first message can be one of a F1AP message and a NRPPa message.
  • the receipt of the indication of the type of network node can be received in a TRP INFORMATION RESPONSE.
  • the receipt of the indication of the location information can be received in a TRP INFORMATION RESPONSE.
  • the receipt of the indication of the location information can be received in a MEASUREMENT RESPONSE and MEASUREMENT REPORT.
  • the location information can comprise an indication of coordinates of the first network node. The coordinates can be sent as a positioning measurement, for example.
  • the location information can also comprise an indication of velocity of the first network node.
  • the first network node may receive, from the second network node, a list of cells or tracking areas where the first network node can move to.
  • the indication of the coordinates can be comprised in a TRP measurement Result IE.
  • the second network node may send a list of UEs onboard of a vehicle served by the first network node.
  • a UE can be identified by an Identifier (ID), an existing UE ID or a modified existing UE ID.
  • the first network node may perform positioning measurements and send them to the second network node.
  • the method may receive a third message, the third message comprising instructions to the first network node to transmit PRS or perform Relative time of Arrival (RTOA) measurements.
  • the list of cells and tracking areas can be sent in NRPPa or Fl AP.
  • the method may further receive a request of a location of a first UE from the list to the second network node.
  • the method may further send the location of the first UE to the second node.
  • FIG. 6 shows an example of a communication system 600 in accordance with some embodiments.
  • the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a radio access network (RAN), and a core network 606, which includes one or more core network nodes 608.
  • the access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which may be generally referred to as network nodes 610), or any other similar 3 GPP access node or non- 3 GPP access point.
  • the network nodes 610 facilitate direct or indirect connection of UE, such as by connecting UEs 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections.
  • 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 600 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 600 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 612 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 610 and other communication devices.
  • the network nodes 610 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 612 and/or with other network nodes or equipment in the telecommunication network 602 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 602.
  • the core network 606 connects the network nodes 610 to one or more hosts, such as host 616. 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 606 includes one more core network nodes (e.g., core network node 608) 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 608.
  • 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), LMF, etc.
  • 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 616 may be under the ownership or control of a service provider other than an operator or provider of the access network 604 and/or the telecommunication network 602, and may be operated by the service provider or on behalf of the service provider.
  • the host 616 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 600 of Fig. 6 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G wireless local area network
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Micro
  • the telecommunication network 602 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 602. For example, the telecommunications network 602 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 612 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 604.
  • 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 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
  • E-UTRAN Evolved-UMTS Terrestrial Radio Access Network
  • EN-DC New Radio - Dual Connectivity
  • the hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and/or 612d) and network nodes (e.g., network node 610b).
  • the hub 614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 614 may be a broadband router enabling access to the core network 606 for the UEs.
  • the hub 614 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 614 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 614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 614 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 614 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 614 may have a constant/persistent or intermittent connection to the network node 610b.
  • the hub 614 may also allow for a different communication scheme and/or schedule between the hub 614 and UEs (e.g., UE 612c and/or 612d), and between the hub 614 and the core network 606.
  • the hub 614 is connected to the core network 606 and/or one or more UEs via a wired connection.
  • the hub 614 may be configured to connect to an M2M service provider over the access network 604 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 610 while still connected via the hub 614 via a wired or wireless connection.
  • the hub 614 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 610b.
  • the hub 614 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 610b, 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 customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3 GPP, including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • the UE QQ700 includes processing circuitry QQ702 that is operatively coupled via a bus QQ704 to an input/output interface QQ706, a power source QQ708, a memory QQ710, a communication interface QQ712, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Fig. 7. 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 702 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 710.
  • the processing circuitry 702 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 702 may include multiple central processing units (CPUs).
  • the input/output interface 706 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.
  • the power source 708 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 708 may further include power circuitry for delivering power from the power source 708 itself, and/or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 708.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.
  • the memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716.
  • the memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems.
  • the processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712.
  • the communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722.
  • the communication interface 712 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 718 and/or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • Fig. 8 shows a network node 800 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 (NBs), evolved NBs (eNBs) and NR NBs (gNBs)).
  • Aps access points
  • BSs base stations
  • NBs Node Bs
  • eNBs evolved NBs
  • gNBs NR NBs
  • 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 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.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • 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 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808.
  • the network node 800 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 800 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 NBs. In such a scenario, each unique NB and RNC pair, may in some instances be considered a single separate network node.
  • the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs).
  • the network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, 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 800.
  • a core network node has similar components as network node 800. Therefore, the description provided to the network node 800 is also valid for a core network node.
  • the processing circuitry 802 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 800 components, such as the memory 804, to provide network node 800 functionality.
  • the processing circuitry 802 is configured to perform any actions/operations/blocks of method 200 of Fig. 4, when the first network node is a LMF and method 300 of Fig. 5 when the first network node is a mobile TRP/mobile lAB/mobile gNB.
  • the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 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 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814.
  • the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of
  • the memory 804 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), 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 802.
  • 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), 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- transitor
  • the memory 804 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 802 and utilized by the network node 800.
  • the memory 804 may be used to store any calculations made by the processing circuitry 802 and/or any data received via the communication interface 806.
  • the processing circuitry 802 and memory 804 is integrated.
  • the communication interface 806 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 806 comprises port(s)/terminal(s) 816 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 806 also includes radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810. Radio front-end circuitry 818 comprises filters 820 and amplifiers 822.
  • the radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802.
  • the radio front-end circuitry 818 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 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 820 and/or amplifiers 822.
  • the radio signal may then be transmitted via the antenna 810.
  • the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818.
  • the digital data may be passed to the processing circuitry 802.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 800 does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).
  • the antenna 810 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 810 is separate from the network node 800 and connectable to the network node 800 through an interface or port.
  • the antenna 810, communication interface 806, and/or the processing circuitry 802 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 810, the communication interface 806, and/or the processing circuitry 802 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 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein.
  • the network node 800 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 808.
  • the power source 808 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 800 may include additional components beyond those shown in Fig. 8 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 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.
  • Fig. 9 is a block diagram illustrating a virtualization environment 900 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 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 900 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 904 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 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 908a and 908b (one or more of which may be generally referred to as VMs 908), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.
  • the VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, 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 908 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 908, and that part of hardware 904 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 908 on top of the hardware 904 and corresponds to the application 902.
  • Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 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 910, which, among others, oversees lifecycle management of applications 902.
  • hardware 904 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 912 which may alternatively be used for communication between hardware nodes and radio units.
  • computing devices described herein may include the illustrated combination of hardware components
  • other embodiments may comprise computing devices with different combinations of components.
  • these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé exécuté par un premier nœud de réseau est décrit. Le procédé consiste à : envoyer un premier message à un second nœud de réseau, pour demander un type de nœud de réseau du second nœud de réseau ; en réponse au premier message, recevoir une indication du type de nœud de réseau du second nœud de réseau, le type de nœud de réseau du second nœud de réseau étant un nœud de réseau mobile ; envoyer un second message au second nœud de réseau, pour demander des informations d'emplacement du second nœud de réseau, sur la base du type de nœud de réseau ; et en réponse au second message, recevoir une indication des informations d'emplacement en provenance du second nœud de réseau.
PCT/IB2023/058005 2022-08-08 2023-08-08 Procédés pour indiquer des mesurages de positionnement de nœud iab mobile dans le réseau WO2024033805A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263395941P 2022-08-08 2022-08-08
US63/395,941 2022-08-08

Publications (1)

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

Family

ID=87762438

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2023/058005 WO2024033805A1 (fr) 2022-08-08 2023-08-08 Procédés pour indiquer des mesurages de positionnement de nœud iab mobile dans le réseau

Country Status (1)

Country Link
WO (1) WO2024033805A1 (fr)

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architecture enhancements for vehicle-mounted relays (Release 18)", no. V0.3.0, 25 May 2022 (2022-05-25), pages 1 - 63, XP052182537, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/23_series/23.700-05/23700-05-030.zip 23700-05-030_MCCclean.docx> [retrieved on 20220525] *
3GPP TECHNICAL REPORT (TR) 22.839
FILIP BARAC ET AL: "Discussion of SA2 FS_VMR Solutions", vol. 3GPP RAN 3, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), XP052244235, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG3_Iu/TSGR3_119/Docs/R3-230390.zip R3-230390 - Discussion of SA2 FS_VMR Solutions.docx> [retrieved on 20230217] *
FILIP BARAC ET AL: "Support of mobile TRP location information", vol. 3GPP RAN 3, no. Toulouse, FR; 20230821 - 20230825, 7 August 2023 (2023-08-07), XP052437534, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG3_Iu/TSGR3_121/Docs/R3-233806.zip R3-233806 - (CR TS 38.473) Support for mobile TRP Location Information.docx> [retrieved on 20230807] *
LARS NORD ET AL: "KI#5, Sol#7: Update to address EN", vol. 3GPP SA 2, no. Online; 20220516 - 20220520, 6 May 2022 (2022-05-06), XP052167486, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_151E_Electronic_2022-05/Docs/S2-2204113.zip S2-2204113 Update solution 7 (VMR).doc> [retrieved on 20220506] *
STEPHEN EDGE ET AL: "New Solution for KI#5: Support of location services for an MBSR with provision of MBSR Location", vol. 3GPP SA 2, no. Online; 20220516 - 20220520, 24 May 2022 (2022-05-24), XP052168342, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_151E_Electronic_2022-05/Docs/S2-2204995.zip S2-2204995 was 4708r02-FS_VMR-pCR 23.700-05 New Solution on location support for MBSR access.docx> [retrieved on 20220524] *

Similar Documents

Publication Publication Date Title
US11838810B2 (en) Report NSA/SA NR indicator
US10993153B2 (en) Measurement gap communication
US11394455B2 (en) Method for enabling new radio (NR) integrated access and backhaul (IAB) nodes to operate in non-standalone (NSA) cells
US11432360B2 (en) Changing GTP TEIP upon UE resume
US20230269630A1 (en) Iab-node handover in inter-cu migration, recursive f1 and rrc signaling aspects
CN111345061B (zh) 通过ran接口的通知控制
US11863323B2 (en) Avoiding multiple retransmissions of signalling transported by 5G NAS transport
US11606833B2 (en) Packet data convergence protocol data recovery
US20210399834A1 (en) Method to manage downlink data delivery status
US20220304104A1 (en) Handling of Session Context
WO2019072904A1 (fr) Notification d&#39;informations sur un type de réseau central (cn)
US20220377595A1 (en) Mapping Information for Integrated Access and Backhaul
US20240073752A1 (en) Co-Existence of Inter-SN and Intra-SN CPC
US20230292185A1 (en) Ei signalling for group handover
JP7407310B2 (ja) 複数のセルについての情報を記憶することを求める要求
US20230269640A1 (en) System and method for steering a wireless device to a network slice
WO2024033805A1 (fr) Procédés pour indiquer des mesurages de positionnement de nœud iab mobile dans le réseau
US12004250B2 (en) Packet data convergence protocol data recovery
WO2022031201A1 (fr) Procédés, appareil et support lisible par machine se rapportant à une migration dans un réseau de communication sans fil
JP2024517572A (ja) ネットワークトラフィック管理
WO2020080999A1 (fr) Procédure de reprise de connexion rrc

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

Country of ref document: EP

Kind code of ref document: A1