[go: up one dir, main page]

WO2025060972A1 - Signalisation de commande pour détection et communication intégrées - Google Patents

Signalisation de commande pour détection et communication intégrées Download PDF

Info

Publication number
WO2025060972A1
WO2025060972A1 PCT/CN2024/119013 CN2024119013W WO2025060972A1 WO 2025060972 A1 WO2025060972 A1 WO 2025060972A1 CN 2024119013 W CN2024119013 W CN 2024119013W WO 2025060972 A1 WO2025060972 A1 WO 2025060972A1
Authority
WO
WIPO (PCT)
Prior art keywords
sensing
node
configuration
request
function
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/CN2024/119013
Other languages
English (en)
Inventor
Nathan Edward Tenny
Shiauhe Shawn TSAI
Abhishek Roy
Mehrdad Shariat
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.)
MediaTek Inc
Original Assignee
MediaTek Inc
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 MediaTek Inc filed Critical MediaTek Inc
Publication of WO2025060972A1 publication Critical patent/WO2025060972A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the present disclosure relates to wireless communications, and more specifically to methods of signaling for controlling the activity of sensing nodes in an integrated communication and sensing scheme.
  • sensing capabilities can be integrated to detect objects that are not actively participating in the system.
  • network nodes such as user equipment (UE) or base stations (BS)
  • UE user equipment
  • BS base stations
  • UE user equipment
  • BS base stations
  • UE user equipment
  • BS base stations
  • UE user equipment
  • BS base stations
  • SAC integrated sensing and communication
  • An embodiment discloses a method of sensing and communication.
  • the method comprises receiving, by a sensing node, a sensing configuration request from a Sensing Function, determining, by the sensing node, to support a sensing configuration in response to the sensing configuration request, and configuring a sensing signal of the sensing node according to the sensing configuration.
  • An embodiment discloses a user equipment (UE) comprising a sensor and a processor coupled to the sensor.
  • the sensor is for generating a sensing signal.
  • the processor is used to receive a sensing configuration request from a Sensing Function, determine to support a sensing configuration in response to the sensing configuration request, and configure the sensing signal according to the sensing configuration.
  • FIG. 1 depicts a basic sensing operation between a sensing node and a sensing target according to the embodiments.
  • FIG. 2 depicts a communications system that includes a Sensing Function and multiple sensing nodes according to the embodiments.
  • FIG. 3 depicts protocol stacks for communication between a first sensing node and a Sensing Function located in a Core Network according to the embodiments.
  • FIG. 4 depicts a control-plane protocol stack for communication between a second sensing node and a Sensing Function located in a Core Network according to the embodiments.
  • FIG. 5 depicts a user-plane protocol stack for communication between a second sensing node and a Sensing Function located in a Data Network.
  • FIG. 6 depicts a flow diagram of a sequence of protocol interactions between a Sensing Function and sensing nodes according to the embodiments.
  • FIG. 7 depicts a communications system that includes a Sensing Function and multiple sensing nodes according to the embodiments.
  • FIG. 8 depicts a communications system that includes a Sensing Function and multiple sensing nodes according to the embodiments.
  • FIG. 9 depicts a communications system that includes a Sensing Function and multiple sensing nodes according to the embodiments.
  • FIG. 10 depicts a flow diagram of a sequence of protocol interactions according to the embodiments.
  • FIG. 11 depicts an alternative arrangement of nodes according to the embodiments.
  • FIG. 12 depicts an exemplary protocol stack according to the embodiments.
  • FIG. 13 depicts simplified block diagrams of a UE and a network entity according to the embodiments.
  • multiple access systems include a Code Division Multiple Access (CDMA) system, a Frequency Division Multiple Access (FDMA) system, a Time Division Multiple Access (TDMA) system, an Orthogonal Frequency Division Multiple Access (OFDMA) system, a system, and a Single Frequency Division Multiple Access (SC-FDMA) system.
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Frequency Division Multiple Access
  • Carrier Frequency Division Multiple Access and MC-FDMA (Multi-Carrier Frequency Division Multiple Access) systems.
  • CDMA may be implemented through a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
  • UTRA Universal Terrestrial Radio Access
  • CDMA2000 Code Division Multiple Access 2000
  • TDMA may be implemented through a radio technology such as Global System for Mobile communications (GSM) , General Packet Radio Service (GPRS) , or Enhanced Data rates for GSM Evolution (EDGE) .
  • OFDMA may be implemented through a wireless technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, or Evolved UTRA (E-UTRA) .
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • E-UTRA Evolved UTRA
  • UTRA is part of the Universal Mobile Telecommunications System (UMTS) .
  • 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long-Term Evolution
  • E-UMTS Evolved
  • 3GPP LTE uses OFDMA in downlink (DL) and SC-FDMA in uplink (UL) .
  • Evolution of 3GPP LTE includes LTE-A (Advanced) , LTE-APro, and/or 5G New Radio (NR) .
  • 3GPP RANs can include, for example, global system for mobile communications (GSM) , enhanced data rates for GSM evolution (EDGE) RAN (GERAN) , Universal Terrestrial Radio Access Network (UTRAN) , Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , and/or Next-Generation Radio Access Network (NG-RAN) .
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GERAN GERAN
  • UTRAN Universal Terrestrial Radio Access Network
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • NG-RAN Next-Generation Radio Access Network
  • the RAN can include base stations (cell sites) , radio equipment controllers (RECs) and fronthaul and backhaul networks to transport data between base stations, RECs, and the core network.
  • RECs radio equipment controllers
  • the RAN can include one or more access nodes, which may be referred to as base station, NodeB, evolved NodeB (eNB) , next Generation NodeB (gNB) , 6G nodes, RAN nodes, controllers, transmission reception points (TRPs) , and so forth, and can include ground stations (e.g., terrestrial access points) or satellite stations providing signal coverage within a geographic area (e.g., a cell) .
  • the RAN may include one or more RAN nodes for providing macrocells, picocells, femtocells, or other types of cells.
  • a macrocell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a picocell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having an association with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG) , UEs for users in the home, etc. ) .
  • CSG Closed Subscriber Group
  • a base station used by a RAN may correspond to that RAN.
  • An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also referred to as evolved Node B, enhanced Node B, eNodeB, or eNB) .
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • eNodeB enhanced Node B
  • eNB evolved Node B
  • NG-RAN base station is a next generation Node B (also referred to as a gNodeB or gNB) .
  • a RAN provides its communication services with external entities through its connection to a core network (CN) .
  • CN core network
  • E-UTRAN may utilize an Evolved Packet Core.
  • Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE.
  • RATs radio access technologies
  • the GERAN implements GSM and/or EDGE RAT
  • the UTRAN implements UMTS RAT or other 3GPP RAT
  • the E-UTRAN implements LTE RAT (sometimes referred to as LTE)
  • NG-RAN implements NR RAT (sometimes referred to as 5G RAT, 5G NR RAT, or NR) .
  • the E-UTRAN may also implement NR RAT.
  • NG-RAN may also implement LTE RAT.
  • wireless communication standard documents e.g., 3GPP Specifications
  • any node with the ability to transmit and receive radio signals can function as a sensing node, such as a UE or a BS, or both (combination of a UE and a BS) .
  • These nodes can configure the sensing signals in various ways, taking into account factors like their own communication needs, the performance requirements of the sensing operation, and the characteristics of the operating radio. For example, a node focused on high-speed communication might allocate fewer resources to sensing, while high-accuracy sensing may require more bandwidth for the sensing signals.
  • the frequency of the sensing signals may depend on the size of the area being sensed, for example, with lower frequencies being used for larger areas due to their better propagation characteristics.
  • the ISAC system can employ multiple sensing nodes to combine their sensing information for various purposes. For instance, the system can use techniques like triangulation or trilateration to determine the precise location of a sensed object, referred to as a sensing target. Moreover, the system can combine data about different sensed objects to build a comprehensive model of the surrounding environment.
  • the system may utilize a dedicated function called a Sensing Function (SF) .
  • the SF may be combined with or considered equivalent to another function, such as a location management function (LMF) , which is responsible for handling location-related tasks.
  • LMF location management function
  • the SF can be deployed at different points within the system architecture, depending on the specific requirements and design choices. For example, it can be located in the core network (CN) , which is the central part of the system, or in the radio access network (RAN) , which is closer to the edge and interacts directly with the user devices. In some cases, the SF can even be implemented directly on a mobile device to enable more localized and distributed sensing capabilities and/or to support sensing operation outside the coverage of a network node.
  • CN core network
  • RAN radio access network
  • FIG. 1 depicts a basic sensing operation between a sensing node 110 and a sensing target 120 according to the embodiments.
  • the operation includes three primary steps.
  • Step 1 involves the transmission of sensing signals by the sensing node 110 (e.g., a user equipment) . These signals may be specifically directed towards the sensing target 120 or broadcasted in a directional or omnidirectional manner.
  • the signals that are of particular interest are those that successfully reach the sensing target 120 (e.g., a vehicle) and trigger return signals, which can be reflections of the original sensing signals.
  • the sensing node 110 receives the return signals from the sensing target 120.
  • These return signals can take various forms depending on the specific implementation. They may be simple reflections of the original signals or modified versions that have undergone amplification, modulation, or the embedding of additional information by the sensing target 120 itself.
  • step 3 the sensing node 110 processes and measures different properties of the received return signals.
  • One common measurement is the time difference between the transmission of the original sensing signals and the arrival of the corresponding return signals. This time difference can be utilized to calculate the distance or range between the sensing node 110 and the sensing target 120, based on the known propagation speed of the signals.
  • ISAC The capabilities of ISAC extend beyond what was previously described. In some applications, it can analyze the environment and extract various details, including the presence, location, and movement of objects. Additionally, it can determine an object's range, velocity, size, shape, and even its material properties.
  • FIG. 2 depicts a communications system 200 that includes a Sensing Function (SF) 240 and multiple sensing nodes according to the embodiments.
  • the SF 240 is located within the Core Network (CN) 230, although it is important to note that the SF 240 can be positioned elsewhere in the system as well.
  • CN Core Network
  • the communications system depicted in FIG. 2 comprises an SF 240 in the CN 230, a base station (BS) 210 serving as the first sensing node, and a UE 220 serving as the second sensing node.
  • the UE 220 and the BS 210 are connected via a wireless communication link.
  • the BS 210 can be further connected to one or more nodes or Network Functions (NFs) in the CN 230 through a communication link, which can be wired, wireless, or a combination of both.
  • NFs Network Functions
  • this communication link is represented by a solid line, terminating at a specific node within the CN.
  • This specific node may have "anchor node” functionality, similar to the Access and Mobility Management Function (AMF) in 5G systems, acting as a communication gateway between the RAN and the CN.
  • AMF Access and Mobility Management Function
  • the BS (e.g., BS 220) can be further divided into multiple components, such as a Centralized Unit (CU) and one or more Distributed Units (DUs) .
  • the nodes within the CN e.g., CN 230
  • a service bus as shown in the figure. This allows CN nodes to expose and invoke services across the service bus, a mechanism known as a Service-Based Interface (SBI) .
  • SBI Service-Based Interface
  • one or more RAN nodes may also communicate on the same service bus as the CN, or on a separate service bus, enabling the use of SBIs within the RAN and/or between the RAN and the CN.
  • communications can be realized in different ways: as messages of a protocol on a reference point, as invocations of an Application Programming Interface (API) on an SBI, or a combination of both.
  • API Application Programming Interface
  • the communication link between the BS and the CN can be implemented as either a point-to-point interface or a service-based reference point over an SBI, or a combination of the two.
  • the combination of interfaces enables communication between the sensing nodes and other nodes in the system, particularly allowing the sensing nodes to exchange information with the SF.
  • the DU and the CU communicate over an F1 interface using the F1 Application Protocol (F1AP) .
  • F1AP F1 Application Protocol
  • This protocol is carried over network transport layers that may vary depending on the specific implementation, denoted as “NW transport” and “NW” in the figure.
  • the CU and the AMF communicate over an NG interface (also known as the N2 interface) using the Next Generation Application Protocol (NGAP) , which is also carried over implementation-dependent network transport layers.
  • NGAP Next Generation Application Protocol
  • the AMF and the SF communicate via a service bus using one or more SBIs.
  • the lower layers of the protocol stacks are responsible for providing transport for the SCP. This can be achieved, for example, by encapsulating or containerizing the SCP messages within the communications of the lower layers. It is important to note that the names used for nodes, protocols, and interfaces in this example are illustrative and may differ in other systems.
  • the base stations may have a "monolithic" architecture instead of being split into a CU and DUs. In such scenarios, the protocol stacks may be simpler than the one depicted in the figure.
  • the SCP may be carried over NGAP from the BS to the AMF.
  • the SCP can be carried over any BS-to-CN interface between a BS and an anchor node in the CN.
  • the SCP enables communication between the sensing node (DU) and the SF in the CN, with the lower layers of the protocol stacks providing the necessary transport mechanisms.
  • FIG. 4 depicts a control-plane protocol stack for communication between a second sensing node (e.g., UE 220) and a Sensing Function (e.g., SF 240) located in a Core Network (e.g., CN 230) according to the embodiments.
  • the diagram focuses on a specific portion of the communication system (e.g., communication system 200) , which includes a UE, a Distributed Unit (DU) , a Centralized Unit (CU) , an Access and Mobility Management Function (AMF) , and a Sensing Function (SF) .
  • DU Distributed Unit
  • CU Centralized Unit
  • AMF Access and Mobility Management Function
  • SF Sensing Function
  • the communication between the UE (e.g., UE 220) and the SF (e.g., SF 240) is facilitated by a newly introduced Sensing Control Protocol (SCP) , which is established between these two entities (i.e., UE and SF) .
  • SCP Sensing Control Protocol
  • the UE and the DU communicate over an air interface using one or more protocol layers, such as the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and the Physical (PHY) layer.
  • the DU and the CU communicate over an F1 interface using F1AP, which is carried over implementation-dependent network transport layers, denoted as "NW" in the figure.
  • F1AP Radio Link Control
  • MAC Medium Access Control
  • PHY Physical
  • the DU and the CU communicate over an F1 interface using F1AP, which is carried over implementation-dependent network transport layers, denoted as "NW" in the figure.
  • F1AP implementation-dependent network transport layers
  • the CU and the AMF communicate over an NG interface (also known as the N2 interface) using the Next Generation Application Protocol (NGAP) , which is also carried over implementation-dependent network transport layers.
  • NGAP Next Generation Application Protocol
  • the AMF and the SF communicate via a service bus using one or more Service-Based Interfaces (SBIs) .
  • the UE and the CU do not have direct communication on a specific interface, they mutually communicate over one or more protocol layers, such as the Radio Resource Control (RRC) layer and the Packet Data Convergence Protocol (PDCP) layer.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • the lower layers of the protocol stacks are responsible for providing transport for the SCP, which can be achieved by encapsulating or containerizing the SCP messages within the communications of the lower layers.
  • the SCP enables communication between the sensing node (i.e., UE) and the SF in the CN, with the lower layers of the protocol stacks providing the necessary transport mechanisms.
  • FIG. 5 depicts a user-plane protocol stack for communication between a second sensing node (e.g., UE 220) and a Sensing Function (e.g., SF 240) located in a Data Network (DN) .
  • the diagram focuses on a specific portion of the communication system (e.g., communication system 200) , which includes a UE, a Distributed Unit (DU) , a Centralized Unit (CU) , a User Plane Function (UPF) , and a Sensing Function (SF) .
  • the communication between the UE and the SF is facilitated by a newly introduced Sensing Control Protocol (SCP) , which is established between these two entities (i.e., UE and SF) .
  • SCP Sensing Control Protocol
  • the UE and the DU communicate over an air interface using one or more protocol layers, such as the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and the Physical (PHY) layer.
  • the DU and the CU communicate over an F1 interface using F1AP, which is carried over implementation-dependent network transport layers, denoted as "NW" in the figure.
  • the CU and the UPF communicate over an N3 interface using the GPRS Tunneling Protocol for the User Plane (GTP-U) , which is transported over a User Datagram Protocol (UDP) layer, an Internet Protocol (IP) layer, and implementation-dependent network transport layers.
  • GTP-U GPRS Tunneling Protocol for the User Plane
  • UDP User Datagram Protocol
  • IP Internet Protocol
  • the UPF and the SF communicate over an N6 interface via the DN, using transport layers that are not detailed in the figure.
  • the UPF and the SF may communicate over Service-Based Interfaces (SBIs) within the Core Network (CN) .
  • the UE and the CU mutually communicate over one or more protocol layers, such as the Service Data Application Protocol (SDAP) layer and the Packet Data Convergence Protocol (PDCP) layer.
  • SDAP Service Data Application Protocol
  • PDCP Packet Data Convergence Protocol
  • the UE and the UPF mutually communicate over a Protocol Data Unit (PDU) layer.
  • SDAP Service Data Application Protocol
  • PDCP Packet Data Convergence Protocol
  • PDU Protocol Data Unit
  • the SF can be considered as an application server in the DN, and the UPF can act as a gateway between the nodes of the cellular network and the DN.
  • the SCP is carried between the UE and the SF as user-plane data.
  • This user-plane protocol stack enables the communication between the sensing node (UE) and the SF in the DN, with the lower layers of the stack providing the necessary transport mechanisms.
  • the specific arrangement of nodes and interfaces allows for the seamless integration of the Sensing Function into the existing cellular network architecture.
  • FIG. 6 depicts a flow diagram of a sequence of protocol interactions between a Sensing Function (SF) and sensing nodes according to the embodiments.
  • the communications shown in the FIG. 6 can be either messages of a Sensing Control Protocol (SCP) or invocations of a Service-Based Interface (SBI) .
  • SCP Sensing Control Protocol
  • SBI Service-Based Interface
  • These communications may use various protocol stacks for transport, such as those shown in the previous figures or similar protocol stacks with different terminology. Also, it should be noted that the optional steps are illustrated by dashed arrows.
  • the sequence begins with the SF (e.g., SF 240) determining that a sensing operation is required.
  • the SF sends a sensing configuration request to the sensing nodes (e.g., BS 210 and/or UE 220) , which may initiate a first SCP transaction.
  • This request may include desired characteristics of the sensing signal configuration (hereinafter referred to as “sensing configuration” ) .
  • the request may comprise multiple messages sent separately to different sensing nodes.
  • the sensing configuration (or a part of it) may be delivered to the sensing nodes over the control plane via existing N1 or N2 interfaces or equivalent service-based reference points, as policies for the UE and/or the BS.
  • each sensing node determines a sensing configuration it will support, considering factors such as its radio capabilities, requirements for transmissions of other RF signals, expected controlling interference on the air interface, and the characteristics of the requested sensing configuration (e.g., radio frequency, timing, power, etc. ) .
  • the sensing nodes then respond to the SF with a sensing configuration response, concluding the first SCP transaction.
  • the SF sends a sensing activation request to the sensing nodes in step 604 to cause the sensing node to start transmitting sensing signals, thereby starting a second SCP transaction.
  • the sensing nodes may optionally respond with a sensing activation response, which may be omitted if the activation of a previously confirmed configuration is considered fail-proof. If step 605 is performed, it concludes the second SCP transaction.
  • step 606 the sensing nodes perform transmission and measurement of sensing signals to sensing targets, following procedures similar to those described in FIG. 1.
  • the SF may send a sensing measurement request to the sensing nodes, in step 607, initiating a third SCP transaction, if the sensing activation request in step 604 does not include a request for measurements.
  • the sensing nodes send a sensing measurement report to the SF in step 608, providing the information obtained from the measurements in step 606. Depending on whether step 607 occurred, this report (in step 608) may conclude the third SCP transaction, initiate a new SCP transaction, or conclude the second SCP transaction.
  • step 609 the SF sends a sensing deactivation command to the sensing nodes, instructing them to stop transmitting sensing signals.
  • the sensing nodes may optionally send a sensing deactivation response in step 610, confirming the deactivation of the sensing signals. In some cases, step 610 may be omitted if deactivation is considered fail-proof.
  • the SF evaluates the reported sensing measurements, applies implementation-specific criteria and heuristics, and draws inferences about the sensing targets.
  • the SF may employ different protocols when communicating with different types of sensing nodes. For instance, the SF may use a first sensing control protocol (SCP1) when interacting with a sensing node embodied in a UE; the SF may use a second sensing control protocol (SCP2) when communicating with a sensing node embodied in a BS.
  • SCP1 first sensing control protocol
  • SCP2 second sensing control protocol
  • these protocols may have similar messages and functionality, they are formally considered to have different termination points.
  • FIG. 7 depicts a communications system 700 that includes a Sensing Function and multiple sensing nodes according to the embodiments.
  • the SF 740 shown as an element of the Core Network (CN) 730, uses SCP1 to communicate with a sensing node embodied in a UE 720 and SCP2 to communicate with a sensing node embodied in a BS 710.
  • the protocol layering for the transport of SCP1 and SCP2 may be similar to the protocol stacks illustrated in FIGs. 3, 4, and 5.
  • This approach allows the SF 740 to tailor its communication protocols to the specific requirements and capabilities of different types of sensing nodes.
  • the system can accommodate the unique characteristics and constraints of each type of sensing node while maintaining a consistent set of messages and functionality across the protocols. This flexibility enables the SF 740 to efficiently manage and coordinate the sensing activities of a diverse set of sensing nodes within the network.
  • a SF may communicate with a sensing node embodied in a UE using a first Sensing Transport Protocol STP1 and with a sensing node embodied in a BS using a second Sensing Transport Protocol STP2, with each of STP1 and STP2 carrying messages of SCP.
  • FIG. 8 depicts a communications system 800 that includes a Sensing Function and multiple sensing nodes according to the embodiments.
  • the SF 840 shown as an element of the CN 830, uses a single SCP for communication with sensing nodes embodied in both a BS 810 and a UE 820.
  • the SF employs the first Sensing Transport Protocol STP1 for communication with the sensing node embodied in the UE 820 and the second Sensing Transport Protocol STP2 for communication with the sensing node embodied in the BS 810.
  • the Sensing Transport Protocols STP1 and STP2 may be protocols of limited scope that include "container" messages. These messages may contain a transparent container field capable of encapsulating an SCP message. Such a container field can be implemented using various data types, such as a BIT STRING or OCTET STRING, in an Abstract Syntax Notation One (ASN. 1) message format.
  • ASN. 1 Abstract Syntax Notation One
  • the above-described arrangement offers several advantages. It allows for the definition and maintenance of a single SCP that includes the substantive messages needed for controlling the sensing activities. At the same time, it enables separate maintenance of the transport protocols that communicate over different network nodes. This approach provides flexibility in adapting the transport protocols to the specific requirements and constraints of different types of sensing nodes while maintaining a consistent set of control messages across the system.
  • this design facilitates the evolution and optimization of the sensing control messaging independently of the transport mechanisms. This can lead to a more modular, scalable, and maintainable architecture for the sensing control system within the network.
  • FIG. 9 depicts a communications system 900 that includes a Sensing Function and multiple sensing nodes according to the embodiments.
  • the control of sensing functionality may need to be shared between an SF 940 and a base station (BS) 910.
  • BS base station
  • This scenario may happen when the signals used for sensing are under the direct control of the BS 910, and some operations on these signals, such as activation and deactivation, require low latency and thus are poorly suited for direct control by the SF 940.
  • the BS 910 may have a better understanding of the radio constraints that can affect the scheduling and configuration of sensing signals compared to the SF 940.
  • sensing configurations for the UE 920 acting as a sensing node are negotiated between an SF and one or more BSs, with the BS 910 having direct control of the sensing signals at the UE 920.
  • a Sensing Control Protocol (SCP) is used for communication between the SF 940 and the UE 920.
  • An additional protocol referred to as a Sensing Management Protocol (SMP) is employed for communication between the SF 940 and the BS 910.
  • Radio protocols e.g., RRC, MAC, or PHY are used for communication between the BS 910 and the UE 920.
  • the BS 910 itself is not considered a sensing node. However, if BS-based sensing is also desired, the SF 940 can separately establish a control protocol (e.g., SCP) with the BS as described earlier.
  • a control protocol e.g., SCP
  • This architecture allows for a clear separation of responsibilities between the SF 940 and the BS 910 in controlling the Sensing Functionality of the UE 920.
  • the SF 940 can focus on high-level coordination and management of sensing activities across multiple nodes, while the BS 910 can handle the low-level, latency-sensitive control of sensing signals based on its knowledge of the radio environment and constraints.
  • the system can ensure that the sensing configurations for the UE are appropriately negotiated and aligned with the overall sensing objectives.
  • the use of radio protocols between the BS 910 and the UE 920 enables efficient and responsive control of the sensing signals, taking into account the real-time dynamics of the radio interface.
  • FIG. 10 depicts a flow diagram of a sequence of protocol interactions among a SF, a base station and a sensing node located at a UE, according to the embodiments.
  • the sensing configurations are negotiated between the SF (e.g., SF 940) and the BS (e.g., BS 910) , and then delivered from the BS (e.g., BS 910) to the UE (e.g., UE 920) .
  • the flow diagram of FIG. 10 is a variation of the flow diagram illustrated by FIG. 6, with the involvement of the BS. Also, it should be noted that the optional steps are illustrated by dashed arrows.
  • the process begins with the SF sending a sensing configuration request to the BS in step 1001, potentially specifying the desired characteristics of the sensing signal to fulfill the requirements of the underlying sensing operation.
  • the BS determines the sensing configuration it can support for the UE, considering factors such as the existing signal transmission and reception configuration of the UE, coordination with other UEs in the service area of the BS, and any other implementation-specific criteria.
  • the BS sends a sensing configuration response to the SF in step 1003, indicating the selected configuration, which may differ from the requested configuration in step 1.
  • the BS sends a configuration message (e.g., an RRCReconfiguration message) to the UE, specifying the sensing configuration.
  • the UE may optionally acknowledge the configuration in step 1005 (e.g., with an RRCReconfigurationComplete message) , confirming its receipt and successful application.
  • the step 1005 may be omitted if the configuration delivery is reliable and assumed to always succeed, although it can be beneficial for the BS to know when the UE has finished applying the configuration.
  • the SF sends a sensing activation request to the BS, indicating that the BS should trigger the UE to start transmitting the configured sensing signals.
  • the BS then sends a sensing activation instruction (e.g., a MAC Control Element) to the UE in step 1007, triggering the transmission of the configured sensing signals.
  • the activation instruction may specify which of multiple configured sensing signals should be activated.
  • the UE may optionally acknowledge the activation in step 1008 (e.g., with an uplink MAC Control Element) , confirming the requested activation.
  • the step 1008 may be omitted if activation is assumed to always succeed and occur immediately, and the BS does not require explicit notification of acceptance.
  • the UE transmits sensing signals towards sensing targets and measures the returning signals in step 1009 (similar to step 606 in FIG. 6) .
  • the SF may optionally send a sensing measurement request (e.g., an SCP message) to the UE in step 1010.
  • a sensing measurement request e.g., an SCP message
  • the step 1010 may be omitted if the UE is aware of the involved SF and the activation in step 1007 implicitly instructs the UE to return measurements to the SF. However, if the SF has multiple algorithms requiring different measurements, step 1010 may be necessary to indicate which measurements should be reported.
  • the step 1010 can be performed in an asynchronous manner with steps 1007-1009, as the SF may request measurements anytime after the activation request in step 1006, and the UE would only return measurements once it has activated sensing signals and performed the requested measurements. In some cases, step 1010 may precede step 1009, allowing the UE to consider the request from the SF when determining which signal characteristics (e.g., timing, angle, and phase) to measure.
  • signal characteristics e.g., timing, angle, and phase
  • the UE sends a sensing measurement report (e.g., an SCP message) to the SF in step 1011, including information measured from the returned signals in step 1009.
  • a sensing deactivation request e.g., an SCP message
  • the BS then sends a sensing deactivation instruction (e.g., a MAC Control Element) to the UE in step 1013, indicating that the UE should stop transmitting the configured sensing signals.
  • the UE may optionally acknowledge the deactivation in step 1014, which may be omitted if deactivation cannot fail or no subsequent operation depends on the deactivation timing.
  • FIG. 11 depicts an alternative arrangement of nodes according to the embodiments.
  • the SF 1104 is integrated in a first UE 1101 rather than in the network.
  • the SF 1104 is hosted by the first UE 1101, while a second UE 1102 serves as a sensing node.
  • a control protocol such as the SCP, is used for communication between the first UE 1101 (hosting the SF 1104) and the second UE 1102 (acting as the sensing node) .
  • This control protocol is responsible for controlling the operation of the second UE, instructing it to transmit sensing signals and measure the returning signals from a sensing target.
  • the functionality of this arrangement is similar to the previously described cases where the SF is integrated in the network node.
  • the transport protocols used to carry the SCP messages may differ.
  • the SCP messages may be transported using protocols specifically designed for UE-to-UE communication, such as those used in device-to-device (D2D) or sidelink communication scenarios.
  • D2D device-to-device
  • the SF 1104 hosted on the first UE 1101 may communicate with an SF located in the Core Network (CN) to support the sensing functionality.
  • This communication between the UE-based SF (e.g., SF 1104) and the CN-based SF may be necessary for coordination, synchronization, or exchange of information related to the sensing operation.
  • the exact nature of this communication and the protocols used may depend on the specific implementation and the division of responsibilities between the UE-based and CN-based SFs.
  • the SF 1104 hosted on the first UE 1101 may support the sensing functionality independently, without any coordination with the CN.
  • the UE-based SF e.g., SF 1104
  • the autonomous operation may be suitable for scenarios where the sensing is localized and does not require network-wide coordination, or where the UEs are operating in an ad-hoc manner without a reliable connection to the network infrastructure.
  • FIG. 12 depicts exemplary protocol stacks according to the embodiments.
  • the protocol stacks are used for transporting the SCP between two UEs 1201 and 1202 in a 5G system.
  • the first UE 1201 and the second UE 1202 communicate using the SCP, which is carried directly over the Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • the SCP may be encapsulated within an intermediate control protocol layer, such as the PC5 Radio Resource Control (PC5-RRC) protocol, the PC5 Signaling (PC5-S) protocol, or similar control protocols specifically designed for D2D communication interfaces.
  • PC5-RRC PC5 Radio Resource Control
  • PC5-S PC5 Signaling
  • the PDCP layer sits on top of the RLC layer, which in turn is above the MAC layer.
  • the MAC layer is then positioned above the PHY layer.
  • the D2D protocol stack may include different layers or a different organization of layers compared to the example shown in FIG. 12. Regardless of the specific structure, the central concept is that the SCP can be carried over the upper layers of any such D2D protocol stack.
  • D2D protocol stack allows the SCP to be efficiently transported between UEs 1201 and 1202 without the need for intermediate network nodes.
  • This direct UE-to-UE communication enables fast and low-latency exchange of sensing control information, which is crucial for coordinating and synchronizing the sensing operations between the UEs.
  • D2D communication may allow support of sensing operation when one or more involved UEs are out of coverage of a network node.
  • the SCP can benefit from the reliable and secure communication mechanisms provided by these layers. This ensures that the sensing control messages are delivered accurately and in a timely manner, enabling effective collaboration between the UEs for sensing purposes.
  • FIG. 13 depicts simplified block diagrams of a UE 1301 and a network entity 1311 according to the embodiments.
  • the network entity 1311 which may be integrated into a base station, is equipped with an antenna 1315 for transmitting and receiving radio signals.
  • the antenna is connected to a RF transceiver module 1314, which converts received RF signals to baseband signals and sends them to a processor 1313.
  • the transceiver also converts baseband signals from the processor back to RF signals for transmission via the antenna.
  • the processor 1313 processes the baseband signals and invokes various functional modules to perform the features of the base station 1311.
  • the memory 1312 stores program instructions and data 1320 to control the operations of the base station.
  • the network entity 1311 includes a set of control functional modules and circuit 1390, such as a registration circuit 1331 for handling registration and mobility procedures, a session management circuit 1332 for managing sessions, and a configuration and control circuit 1333 for providing configuration and control parameters to the UEs.
  • control functional modules and circuit 1390 such as a registration circuit 1331 for handling registration and mobility procedures, a session management circuit 1332 for managing sessions, and a configuration and control circuit 1333 for providing configuration and control parameters to the UEs.
  • the UE 1301 comprises a memory 1302, a processor 1303, and a RF transceiver module 1304 connected to an antenna 1305.
  • the RF transceiver converts received RF signals to baseband signals for the processor and converts baseband signals from the processor to RF signals for transmission.
  • the processor 1303 processes the baseband signals and invokes various functional modules and circuits to perform UE features.
  • the memory 1302 stores data and program instructions 1310 for execution by the processor to control UE operations. Suitable processors include special purpose processors, digital signal processors (DSPs) , microprocessors, microcontrollers, application-specific integrated circuits (ASICs) , field programmable gate arrays (FPGAs) , and other types of integrated circuits (ICs) or state machines.
  • DSPs digital signal processors
  • ASICs application-specific integrated circuits
  • FPGAs field programmable gate arrays
  • a processor associated with software can be used to implement and configure the UE 1301 features.
  • the UE 1301 also includes a set of functional modules and control circuits for performing UE tasks.
  • the protocol stacks 1360 may include a SCP layer for communicating with the Sensing Function in the core network, a RRC layer for high-layer configuration and control, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer.
  • a system modules and circuits 1370 implemented and configured by software, firmware, hardware, or a combination thereof, interwork with each other to enable UE 1301 to perform embodiments and functional tasks and features in the network. These modules include a registration circuit 1321 for performing registration and mobility procedures, and a configuration and control circuit 1324 for handling configuration and control parameters.
  • the UE 1311 also includes a sensor 1380 for transmitting the sensing signal to a sensing target and measuring a returned signal reflected from the sensing target. Then, the processor 1303 can generate a measurement report accordingly.
  • sensors include laser altimeters, LiDAR, radar, ranging instruments, and scatterometers, infrared sensors, multispectral sensors, radiometers, microphone and cameras.
  • the sensor 1380 includes active sensors, which involve both the transmission of sensing signals and the measurement of their reflections or returns.
  • the disclosed ISAC control signaling mechanism provides a flexible, scalable, and efficient framework for integrating sensing capabilities into wireless communication networks.
  • the system enables the SF to be located in various parts of the network, such as the core network, radio access network, or even in user equipment. This flexibility allows the system to adapt to different network architectures and use cases while promoting interoperability between different vendors.
  • the control signaling enables the SF to negotiate and configure sensing parameters based on specific task requirements, optimizing radio resource allocation and minimizing the impact on communication performance.
  • the split between the SF and the base station allows for fast and responsive control of time-critical operations, which is crucial for real-time sensing applications.
  • control signaling separates sensing-specific functionality from the underlying communication protocols, facilitating independent evolution and optimization of sensing and communication aspects. Furthermore, the control signaling enhances coordination across multiple nodes, enabling collaborative sensing techniques that improve accuracy, reliability, and coverage of sensing results. Overall, the disclosed ISAC control signaling mechanism provides a comprehensive framework for realizing advanced sensing applications while minimizing the impact on communication performance and allowing for the independent evolution of sensing and communication technologies.
  • UE User equipment
  • the UE may include a device with radio communication capabilities.
  • the UE may include a smartphone (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) .
  • the UE may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs) , pagers, laptop computers, desktop computers, wireless handsets, or any computing device that has a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets or any computing device that has a wireless communications interface.
  • the UE may also be referred to as a client, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device.
  • the UE may include IoT UE, which can include a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • IoT UE can utilize technologies (e.g., M2M, MTC, or mMTC technology) for exchanging data with an MTC server or device via a PLMN, other UEs using ProSe or D2D communications, sensor networks, or IoT networks.
  • technologies e.g., M2M, MTC, or mMTC technology
  • the M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UE, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) .
  • the IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc. ) to facilitate the connections of the IoT network.
  • the UE may be configured to connect or communicatively couple with the Radio Access Network (RAN) through a radio interface, which may be a physical communication interface or layer configured to operate with cellular communication protocols such as a GSM protocol, a CDMA network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and the like.
  • a radio interface which may be a physical communication interface or layer configured to operate with cellular communication protocols such as a GSM protocol, a CDMA network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and the like.
  • the UE and the RAN may use a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising a PHY layer, an MAC layer, an RLC layer, a PDCP layer, and an RRC layer.
  • a DL transmission may be from the RAN to the UE and a UL transmission may be from the UE to the RAN.
  • the UE may further use a sidelink to communicate directly with another UE (not shown) for D2D, P2P, and/or ProSe communication.
  • a ProSe interface may include one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH) , a Physical Sidelink Shared Channel (PSSCH) , a Physical Sidelink Discovery Channel (PSDCH) , and a Physical Sidelink Broadcast Channel (PSBCH) .
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the term “some” refers to one or more.
  • Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C.
  • combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • RAM Random Access Memory
  • ROM Read Only Memory
  • EPROM Electrically Programmable ROM
  • EEPROM Electrically Erasable Programmable ROM
  • registers hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art.
  • RAM Random Access Memory
  • ROM Read Only Memory
  • EPROM Electrically Programmable ROM
  • EEPROM Electrically Erasable Programmable ROM
  • registers hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art.
  • the storage medium is connected to the processor, allowing the processor to read from and write to the medium.
  • the storage medium may be built into the processor itself. Both the processor and the storage medium may reside within an ASIC, which can be located in a remote station.
  • the processor and the storage medium may exist as separate components within a remote station, base station, or server.
  • the computing instructions may be carried out by an operating system, for example, Microsoft Windows, Apple Mac OS X, macOS, or iOS operating systems, some variety of the Linux operating system, Google Android operating system, or the like.
  • an operating system for example, Microsoft Windows, Apple Mac OS X, macOS, or iOS operating systems, some variety of the Linux operating system, Google Android operating system, or the like.
  • the computers may be on a distributed computing network, such as one having any number of clients and/or servers. Each client may run software for implementing client-side portions of the embodiments. In addition, any number of servers may be provided for handling requests received from one or more clients. Clients and servers may communicate with one another via one or more electronic networks, which may be in various embodiments such as the Internet, a wide area network, a mobile telephone network, a wireless network (e.g., Wi-Fi, 5G, and so forth) , or a local area network. Networks may be implemented using any known network protocols.
  • the users may be provided with an opportunity to opt in/out of programs or features that may collect personal information (e.g., information about a user's preferences or usage of a smart device) .
  • personal information e.g., information about a user's preferences or usage of a smart device
  • certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed.
  • a user's identity may be anonymized so that the personally identifiable information cannot be determined for or associated with the user, and so that user preferences or user interactions are generalized (for example, generalized based on user demographics) rather than associated with a particular user.
  • stages that are not order dependent may be reordered and other stages may be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be obvious to those of ordinary skill in the art, so the ordering and groupings presented herein are not an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.

Landscapes

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

Abstract

Un procédé de détection et de communication comprend la réception, par un nœud de détection, d'une demande de configuration de détection provenant d'une fonction de détection, la détermination, par le nœud de détection, de la prise en charge d'une configuration de détection en réponse à la demande de configuration de détection, et la configuration d'un signal de détection du nœud de détection selon la configuration de détection. Le procédé propose un cadre complet pour réaliser des applications de détection avancées tout en réduisant au minimum l'impact sur les performances de communication et permettant l'évolution indépendante des technologies de détection et de communication.
PCT/CN2024/119013 2023-09-22 2024-09-14 Signalisation de commande pour détection et communication intégrées Pending WO2025060972A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363584511P 2023-09-22 2023-09-22
US63/584511 2023-09-22

Publications (1)

Publication Number Publication Date
WO2025060972A1 true WO2025060972A1 (fr) 2025-03-27

Family

ID=95073542

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/119013 Pending WO2025060972A1 (fr) 2023-09-22 2024-09-14 Signalisation de commande pour détection et communication intégrées

Country Status (1)

Country Link
WO (1) WO2025060972A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115811736A (zh) * 2021-09-13 2023-03-17 维沃移动通信有限公司 感知通道的建立方法、装置、通信设备、存储介质及系统
WO2023115545A1 (fr) * 2021-12-24 2023-06-29 Oppo广东移动通信有限公司 Procédé de transmission d'informations, premier dispositif de réseau d'accès, second dispositif de réseau d'accès et terminal

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115811736A (zh) * 2021-09-13 2023-03-17 维沃移动通信有限公司 感知通道的建立方法、装置、通信设备、存储介质及系统
WO2023115545A1 (fr) * 2021-12-24 2023-06-29 Oppo广东移动通信有限公司 Procédé de transmission d'informations, premier dispositif de réseau d'accès, second dispositif de réseau d'accès et terminal

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
VIVO CHINA TELECOM CHINA UNICOM: "Introduction of network based Sensing in 5G Advanced ", 3GPP DRAFT; S2-2106008, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. 20210730, 10 August 2021 (2021-08-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052053654 *
XIAOMI: ""RP-230065 Sensing channel model in LLS and SLS-final"", 3GPP TSG_RAN\TSG_RAN, 13 March 2023 (2023-03-13) *

Similar Documents

Publication Publication Date Title
US20240407046A1 (en) Positioning method and device for same
US10575203B2 (en) Delivery of measurements
JP7632815B2 (ja) ユーザ機器の測位方法及び装置
WO2020156470A1 (fr) Procédé et appareil de communication
CN104885552A (zh) 用于装置-到-装置通信的方法和设备
EP4247013B1 (fr) Procédé de positionnement, appareil de communication et système de communication
CN118525575A (zh) 位置信息提供
US20250063540A1 (en) Positioning method, apparatus, storage medium, and chip
KR20250003963A (ko) 통신 방법 및 관련 장치
CN116250373A (zh) 通信系统
CN115942230A (zh) 位置确定的方法和装置
CN113302992B (zh) 用于处置无线通信网络中的定位的无线装置、无线电网络节点以及在其中执行的方法
US20150110089A1 (en) Network Selection for Mobile Client Devices in Integrated Cellular and Wi-Fi Networks
US12445923B2 (en) Managing multiple subscriber identities in cellular network
WO2023024948A1 (fr) Procédé et appareil de détermination de position
US20230262563A1 (en) Managing multiple subscriber identities in cellular network
WO2025060972A1 (fr) Signalisation de commande pour détection et communication intégrées
CN115735399A (zh) 针对处于空闲或非活动模式中的ue使用下行和上行测量的基于ue和ue辅助的定位
EP4380288A1 (fr) Procédé et appareil de mise à jour de paramètres de configuration
WO2024165342A1 (fr) Gestion de reconfiguration conditionnelle pendant une opération musim dans des réseaux sans fil
WO2023185424A1 (fr) Procédé et appareil de communication sans fil
WO2023173875A1 (fr) Procédé et appareil de détermination de mode de positionnement
WO2018171866A1 (fr) Mécanisme de relation de voisinage pour interfonctionnement radio lte-new pour réseaux sans fil
EP4498708A1 (fr) Procédé d'acquisition d'informations de position, et appareil et système de communication
EP4415439A1 (fr) Positionnement dans des réseaux de communication cellulaires

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024867381

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2024867381

Country of ref document: EP

Effective date: 20251009