Establishment of user plane connections for perception

Abstract

Aspects of the present disclosure relate to a base station, apparatus and method for perceived establishment of UP connections. In one aspect, a first base station receives a first message and, based at least on the first message, sends a request to a first device or a second device for establishment of a perceived UP connection between the first base station and the first device. Further, the first base station receives a response from the first device or the second device. The response includes a first UP address of the first device or a second UP address of the fourth device.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to apparatus and methods for establishing a sensed user plane (UP) connection. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication with one or more user communication devices (which may also be referred to as user equipment (UE), or other suitable terms). The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may support wireless communication across a variety of wireless access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable wireless access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] Wireless sensing technology aims to acquire information about objects or their environment and characteristics without physical contact. This can be achieved using cameras, radar, lidar, etc. There are also investigations and solutions regarding how communication technologies (e.g., Long Term Evolution (LTE), New Radio (NR), Wireless Local Area Networks (WLAN), etc.) can be used for sensing. There are also initiatives to enhance cellular wireless communication systems (e.g., the 5th Generation System (5GS) as defined by the 3rd Generation Partnership Project (3GPP)) to incorporate wireless sensing. In other words, in addition to traditional communication services, wireless systems can perform sensing tasks and report the results to applications, customers, or vertical applications interested in the sensing results. Sensing can also be used within wireless communication systems to improve network performance.

[0004] Integrated Sensing and Communication (ISAC) refers to technologies that combine sensing and communication systems to more effectively utilize wireless resources. In research on ISAC, Sensing Functions (SFs) have been introduced to enable sensing in 5GS networks. SFs can be standalone network functions (NFs) or co-located with existing NFs, such as Location Management Functions (LMFs). Application servers, 5GS NFs, or UEs can all trigger the sensing process.

[0005] The SF can assign sensing tasks to access nodes (e.g., RAN nodes in 3GPP, or WLAN APs in non-3GPP systems) or UEs. If a sensing task is assigned to a RAN node, the RAN node can report sensing measurement data to the SF. Summary of the Invention

[0006] This disclosure relates to a base station, apparatus, and method for establishing a UP connection for sensing. The base station, apparatus, and method enable sensing measurement data to be transmitted from the base station to an apparatus performing sensing functions via the UP connection for sensing.

[0007] Some implementations of the first base station described herein may include: at least one memory; and at least one processor coupled to the at least one memory. The at least one processor is configured to cause the first base station to: receive a first message; send a request to a first device or a second device, at least based on the first message, for the establishment of a sense-based UP connection between the first base station and the first device; and receive a response from the first device or the second device, the response including: a first UP address of the first device or a second UP address of the fourth device.

[0008] In some implementations, the first base station is configured to receive the first message by receiving a sensing registration response message from the first device.

[0009] In some implementations, the first base station is configured to receive a first message by receiving a sensing service request message from a first device or a third device, the sensing service request message including information about a sensing task.

[0010] In some implementations, the first message includes at least one of the following: a first indication indicating that the first device supports the transmission of sensed measurement data via the UP connection, or a second indication indicating that the first device requests the transmission of sensed measurement data via the UP connection; and the first base station is caused to send a request for the establishment of the UP connection based on at least one of the following: the first indication, or the second indication.

[0011] In some implementations, the first base station is configured to receive the first message by receiving information about the sensing task and information about the first device from the second base station during a handover.

[0012] In some implementations, the first base station is configured to send a request for the establishment of a UP connection to the second device via a third device by sending a request for the establishment of a UP connection and a third indication that the UP connection will be established.

[0013] In some implementations, the first message includes the UP address of the first device.

[0014] In some implementations, the first base station is configured to send a request for the establishment of a UP connection to the second device via the third device by sending a request for the establishment of a UP connection including the UP address of the first device.

[0015] Some implementations of the first device described herein may include: at least one memory; and at least one processor coupled to the at least one memory. The at least one processor is configured to cause the first device to: receive from a second device, a base station, or a third device a request for establishing a sensed UP connection between the first base station and the first device; and send a first UP address of the first device to the second device, the base station, or the third device.

[0016] In some implementations, the first device is also configured to send a first message to a base station or a third device.

[0017] In some implementations, the first message includes at least one of the following: a first indication indicating that the first device supports the transmission of sensing measurement data via the UP connection, or a second indication indicating that the first device requests the transmission of sensing measurement data via the UP connection.

[0018] Some implementations of the second device described herein may include: at least one memory; and at least one processor coupled to the at least one memory. The at least one processor is configured to cause the second device to: obtain a first UP address of the first device; send the first UP address of the first device to a fourth device; receive at least one UP address of the fourth device from the fourth device; and send one of the at least one UP addresses of the fourth device to a first base station for establishing a sensing UP connection between the first base station and the first device.

[0019] In some implementations, the second device is configured to obtain the first UP address of the first device by: receiving a request from a third device for establishing a UP connection between the first base station and the first device; sending a request to the first device for the first UP address of the first device; and receiving the first UP address of the first device from the first device.

[0020] In some implementations, the second device is configured to obtain the first UP address of the first device by receiving a request from a third device for establishing a UP connection between the first base station and the first device, the request including the first UP address of the first device.

[0021] In some implementations, at least one UP address of the fourth device includes: a second UP address of the fourth device for transmission from the first base station to the fourth device; and the second device is caused to send the second UP address of the fourth device to the first base station.

[0022] In some implementations, at least one UP address of the fourth device includes: a third UP address of the fourth device for transmission from the first device to the fourth device; and the second device is also configured to send the third UP address of the fourth device to the first device.

[0023] Some implementations of the third device described herein may include: at least one memory; and at least one processor coupled to the at least one memory. The at least one processor is configured to cause the third device to: receive from a first base station or a first device a request for establishing a UP connection for sensing between the first base station and the first device; and send a request to a second device.

[0024] In some implementations, the third device is also configured to: receive a third indication indicating that an UP connection will be established; determine information about the first device based on the third indication; and send information about the first device to the second device.

[0025] In some implementations, the third device is also configured to: receive information about the first device or the first UP address of the first device from the first base station; and send information about the first device or the first UP address of the first device to the second device.

[0026] In some implementations, the third device is also configured to: receive from the first device a response to a request for establishing a UP connection, and a first UP address of the first device; and send the first UP address of the first device and the response to the second device and the first base station, respectively.

[0027] In some implementations, the request to establish a UP connection includes: the first UP address of the first device.

[0028] Some implementations of the first device described herein may include: at least one memory; and at least one processor coupled to the at least one memory. The at least one processor is configured to cause the first device to: receive a second message; and, based at least on the second message, send a first UP address of the first device to a first base station or a second device, and a request for establishing a sensing UP connection between the first base station and the first device.

[0029] In some implementations, the first device is configured to receive the second message by receiving a sensing registration request message from the first base station.

[0030] In some implementations, the first device is made to receive the second message by receiving a sensing task from a consumer of the sensing service.

[0031] In some implementations, the second message includes a fourth indication indicating that: the first base station supports the transmission of sensed measurement data via the UP connection; and the first device is enabled to send a request for the establishment of the UP connection based on the fourth indication.

[0032] In some implementations, the first device is configured to receive the second message by receiving, during handover, one of the following from the second base station: an identifier of the first base station associated with an identifier of a sensing task; or an identifier of the UE associated with handover.

[0033] Some implementations of the method described herein may include: receiving a first message at a first base station; sending a request to a first device or a second device, at least based on the first message, for the establishment of a sensing UP connection between the first base station and the first device; and receiving a response from the first device or the second device, the response including: a first UP address of the first device or a second UP address of the fourth device.

[0034] Some implementations of the method described herein may include: receiving, at a first device, a request from a second device, a base station, or a third device for establishing a sense-based UP connection between the first base station and the first device; and sending the first UP address of the first device to the second device, the base station, or the third device.

[0035] Some implementations of the method described herein may include: obtaining a first UP address of the first device at a second device; sending the first UP address of the first device to a fourth device; receiving at least one UP address of the fourth device from the fourth device; and sending one of the at least one UP address of the fourth device to a first base station for establishing a sensing UP connection between the first base station and the first device.

[0036] Some implementations of the method described herein may include: receiving, at a third device, a request from a first base station or a first device for establishing a sensing UP connection between the first base station and the first device; and sending the request to a second device.

[0037] Some implementations of the method described herein may include: receiving a second message at a first device; and, at least based on the second message, sending a first UP address of the first device to a first base station or a second device, and a request for establishing a sensing UP connection between the first base station and the first device.

[0038] It should be understood that the summary section is not intended to identify key or essential features of the implementation of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become apparent from the following description. Attached Figure Description

[0039] Figure 1A and Figure 1B Examples of wireless communication systems supporting the establishment of UP connections for sensing are shown respectively according to various aspects of this disclosure;

[0040] Figure 2 A flowchart is shown illustrating a method for establishing a sensed UP connection in accordance with other aspects of this disclosure;

[0041] Figure 3 A signaling diagram illustrating an example of a sensing registration process according to various aspects of this disclosure is shown;

[0042] Figure 4A , Figure 4B , Figure 4C as well as Figure 4D Signaling diagrams illustrating example procedures for establishing a sensed UP connection according to various aspects of this disclosure are shown respectively;

[0043] Figure 5A , Figure 5B , Figure 5C , Figure 5D , Figure 5E , Figure 5F , Figure 5G as well as Figure 5H Signaling diagrams illustrating example procedures for establishing a sensed UP connection according to various aspects of this disclosure are shown respectively;

[0044] Figure 6 A flowchart is shown illustrating a method for establishing a sensed UP connection in accordance with other aspects of this disclosure;

[0045] Figure 7A , Figure 7B , Figure 7C , Figure 7D , Figure 7E as well as Figure 7F Signaling diagrams illustrating example procedures for establishing a sensed UP connection according to various aspects of this disclosure are shown respectively;

[0046] Figure 8 Examples of devices supporting the establishment of a sensed UP connection according to some aspects of this disclosure are shown; and

[0047] Figure 9 , Figure 10 as well as Figure 11 Flowcharts of methods for establishing a sensed UP connection, according to other aspects of this disclosure, are shown respectively. Detailed Implementation

[0048] The principles of this disclosure will now be described with reference to some implementations. It should be understood that these implementations are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various ways other than those described below.

[0049] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0050] References to "an implementation," "example implementation," "implementation," "some implementations," etc., in this disclosure indicate that the implementation(s) described may include a particular feature, structure, or characteristic, but not every implementation necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same implementation(s). Moreover, when a particular feature, structure, or characteristic is described in conjunction with an implementation, it is understood that, whether explicitly described or not, the influence of such feature, structure, or characteristic on other implementations is within the knowledge of those skilled in the art.

[0051] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of implementation, a first element may also be referred to as a second element, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0052] The terminology used herein is for the purpose of describing a particular implementation only and is not intended to limit the example implementation. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including,” when used herein, specify the presence of the described features, elements, and / or components, but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0053] The aspects of this disclosure are described in the context of wireless communication systems.

[0054] Figure 1AAn example of a wireless communication system 100A for establishing a sensed UP connection is illustrated according to various aspects of this disclosure. The wireless communication system 100A may include one or more network entities 102-1 and 102-2 (also referred to as network devices (NEs)), one or more user equipments or UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100A may support various radio access technologies. In some implementations, the wireless communication system 100A may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100A may be a 5G network, such as an NR network. In some other implementations, the wireless communication system 100A may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100A may support radio access technologies beyond 5G. In addition, the wireless communication system 100A can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0055] Network entities 102-1 and 102-2 may be collectively referred to as network entity 102, or separately as network entity 102. Alternatively, network entities 102-1 and 102-2 may be referred to as first network entity 102-1 and second network entity 102-2, respectively.

[0056] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100A. One or more network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceivers, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0057] Network entity 102 can provide a geographic coverage area 112 for which it can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some implementations, network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout this specification can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0058] One or more UEs 104 may be distributed throughout the geographical area of ​​the wireless communication system 100A. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100A. In some other implementations, UE 104 may be mobile within the wireless communication system 100A.

[0059] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1A As illustrated, UE 104 can communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Figure 1A As shown in the diagram. Alternatively or additionally, UE 104 may support communication with other network entities 102 or UE 104, which may act as relays in the wireless communication system 100A.

[0060] UE 104 can also wirelessly communicate directly with other UE 104 via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0061] Network entity 102 may support communication with core network 106, or communication with another network entity 102, or both. For example, network entity 102 may be connected to core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other, or communicate indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as a wireless head, a smart wireless head, or a transmit-receive point (TRP).

[0062] In some implementations, network entity 102 can be configured in a decomposed architecture that utilizes protocol stacks physically or logically distributed among two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-Real-Time RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0063] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0064] The functional division among CU, DU, and RU can be flexible and can depend on the different functions supported by the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host higher-layer protocol (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer) functions and signaling, and each of them can be at least partially controlled by the CU 160.

[0065] Alternatively or additionally, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, and RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU, or between DU and RU, can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer can be performed by another of CU, DU, or RU).

[0066] The CU can be further functionally divided into CU control plane (CU-CP) and CU UP (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the mid-range or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by corresponding network entities 102 communicating via such communication links.

[0067] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core network (5GC), and can include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) and UP entities that route or interconnect packets to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or UP Function (UPF)). In some implementations, control plane entities can manage non-access stratum (NAS) functions (such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.)) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0068] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0069] In the wireless communication system 100A, network entity 102 and user equipment 104 can use the resources of the wireless communication system 100A (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital schemes.

[0070] One or more digital schemes can be supported in the wireless communication system 100A, and the digital schemes may include subcarrier spacing and cyclic prefixes. The first digital scheme (e.g.) =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the normal cyclic prefix. In some implementations, the first digital scheme (e.g., 15 kHz) associated with the first subcarrier spacing (e.g., 15 kHz) =0) allows each subframe to utilize one time slot. The second digital scheme (e.g., =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third digital scheme (e.g., =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal or extended cyclic prefix. A fourth digital scheme (e.g., =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth digital scheme (e.g., =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0071] Time intervals for resources (such as communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, such as 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, such as 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0072] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital schemes supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth digital schemes (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. =0、 =1、 =2、 =3、 =4) Each subframe can utilize a single time slot, two time slots per subframe, four time slots per subframe, eight time slots per subframe, or 16 time slots per subframe. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots used for a subframe can depend on the digital scheme. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot for the normal and extended cyclic prefixes, the number of time slots per subframe, and the number of time slots per frame can depend on the digital scheme. It should be understood that the first digital scheme (e.g., 15 kHz) associated with the first digital scheme (e.g., =0) can be used interchangeably between subframes and time slots.

[0073] In the wireless communication system 100A, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100A can support one or more operating frequency bands, such as frequency ranges specified as FR1 (410 MHz – 7.125 GHz), FR2 (24.25 GHz – 52.6 GHz), FR3 (7.125 GHz – 24.25 GHz), FR4 (52.6 GHz – 114.25 GHz), FR4a or FR4-1 (52.6 GHz – 71 GHz), and FR5 (114.25 GHz – 300 GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, along with other devices or equipment, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.

[0074] FR1 can be associated with one or more number schemes (e.g., at least three number schemes). For example, FR1 can be associated with a first number scheme (e.g., =0) associated with, including a 15 kHz subcarrier spacing; a second digital scheme (e.g., =1), including a 30 kHz subcarrier spacing; and a third digital scheme (e.g., =2), including a 60 kHz subcarrier spacing. FR2 can be associated with one or more digital schemes (e.g., at least two digital schemes). For example, FR2 can be associated with a third digital scheme (e.g., =2) associated with, including a 60 kHz subcarrier spacing; and a fourth digital scheme (e.g., =3), including a 120 kHz subcarrier spacing.

[0075] Figure 1B An example of a wireless communication system 100B supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Specifically, Figure 1B It shows Figure 1A The network entities or network functions (NFs) in the core network 106 shown.

[0076] like Figure 1B As shown, the core network 106 may include at least: SF 120, Session Management Function (SMF) 130, Mobility Management Function (AMF) 140 and UP Function (UPF) 150.

[0077] In some implementations, SF 120 enables awareness in 5G networks. SF 120 can be a standalone 5GC NF or co-located with an existing 5GC NF (e.g., LMF). SF 120 may include an SF control plane (SF-C) portion 122 and an SF user plane (SF-U) portion 124. SF 120 can communicate with AMF 140 and UPF 150 via the NS1 and NS7 interfaces, respectively. In some implementations, SF 120 can communicate with base station 102-1 via AMF 140 or UPF 150. Alternatively, SF 120 can communicate directly with base station 102-1.

[0078] In some implementations, the SMF 130 can communicate with the AMF 140 and UPF 150 via interfaces N11 and N4, respectively. In some implementations, the SMF 130 can communicate with the SF 120. For example, the SMF 130 can communicate with the SF-C section 122 of the SF 120.

[0079] In some implementations, the AMF 140 can communicate with the UE 104 and the base station 102 via the N1 interface and the N2 interface, respectively.

[0080] In some implementations, the UPF 150 can communicate with the base station (BS) 102 via the N3 interface. Additionally, the UPF 150 can communicate with the SF 120 and SMF 130 via the NS7 and N4 interfaces, respectively.

[0081] In some implementations, the ISAC can be executed in both wireless communication system 100A and wireless communication system 100B. In the ISAC, SF 120 can assign sensing tasks to base station 102 or UE 104. In this disclosure, base station 102 is considered an entity that performs control (or configuration) of the sensing transmitter(s) and sensing receiver(s), and collects sensing measurement data for the sensing tasks. The sensing transmitter(s) and sensing receiver(s) can be TRPs controlled by base station 102 or UE.

[0082] When base station 102 is performing sensing tasks, a large amount of sensing measurement data will be collected or generated and needs to be transmitted from base station 102 to SF 120 for further processing to obtain sensing results. This large-scale data can be transmitted via the control plane (CP) or via the UP, depending on the indication from base station 102 and / or SF 120 regarding the existence and support of UP transmissions for sensing. Therefore, a UP transmission path or tunnel from base station 102 to SF 120 for sensing applications is necessary and needs to be established and function properly. Furthermore, the scenarios under which the UP path will be established (i.e., the triggering of establishing the UP path between base station 102 and SF-U) also need to be specified.

[0083] In traditional 3GPP networks, the UE triggers Protocol Data Unit (PDU) session establishment by providing a Device Trigger Request message. This PDU session is used for newly detected applications or applications requested by the network. The Device Trigger Request message includes information about the application on the UE side. During the PDU session establishment / modification process, the Policy Control Function (PCF) provides the Session Management (SM) Policy to the Service Management Function (SMF) for the lifecycle of the PDU session. Upon receiving the SM Policy from the PCF, the SMF selects a UPF and configures N4 rules for the UPF to enable packet processing at the UPF side. The selected UPF can respond by providing the requested CN tunnel information for the PDU session. The SMF configures the Quality of Service (QoS) flow, corresponding QoS profile, and Core Network (CN) tunnel information for the RAN node to enable QoS processing at the RAN side. The RAN node responds to the SMF using the Access Network (AN) tunnel information for the PDU session. The SMF then further forwards the AN tunnel information for the PDU session to the UPF. In doing so, an N3 tunnel is established between the RAN node and the UPF for the PDU session. The UE exchanges data with the application server via the N3 tunnel between the RAN node and the UPF.

[0084] If the RAN node needs to perform sensing tasks and generate sensing measurement data, it is highly likely that the RAN node will use the UP connection between the RAN node and the SF to send the sensing measurement data and parameters. However, the current PDU session is used for UP data transmission between the UE and the data network, and the PDU session establishment is triggered by the UE. Therefore, the traditional PDU session concept is no longer applicable to RAN node-based sensing UP reporting and transmission. A new UP connection for sensing needs to be established between the RAN node and the SF.

[0085] In view of the above, the present disclosure provides a solution for supporting the establishment of a UP connection for sensing. In one aspect of the solution, a first base station receives a first message and, based at least on the first message, sends a request to a first device or a second device for establishing a UP connection for sensing between the first base station and the first device. Then, the first base station receives a response from the first device or the second device. The response includes: a first UP address of the first device or a second UP address of the fourth device. In this manner, sensing measurement data can be transmitted from the base station to the device performing sensing via the UP connection.

[0086] The principles disclosed below will refer to Figures 2 to 8 Described.

[0087] Figure 2A flowchart of a method 200 supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Operation of method 200 can be implemented by the device or components thereof described herein. For example, operation of method 200 can be performed by the first base station 102-1 described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions.

[0088] At position 210, the first base station 102-1 receives the first message.

[0089] At point 220, the first base station 102-1 sends a request to the first device or the second device, based at least on a first message, for the establishment of a UP connection for sensing between the first base station and the first device.

[0090] At point 230, the first base station 102-1 receives a response from either the first device or the second device. This response includes either the first UP address of the first device or the second UP address of the fourth device.

[0091] In this disclosure, UP connections can be used interchangeably with UP paths or UP tunnels.

[0092] In some implementations, the first device can perform Figure 1B SF 120 in. Alternatively, the first device can perform... Figure 1B In addition to SF 120, other network functions are included.

[0093] In some implementations, the second device can perform Figure 1B The SMF 130 in the middle. Alternatively, a second device can perform... Figure 1B In addition to the SMF 130, other network functions are also included.

[0094] In some implementations, a third device can perform... Figure 1B The AMF 140 in the middle. Alternatively, a third device can perform... Figure 1B In addition to the AMF 140, other network functions are also included.

[0095] In some implementations, the fourth device can perform Figure 1B UPF 150. Alternatively, a fourth device can perform... Figure 1B In addition to UPF 150, other network functions are included.

[0096] Hereinafter, some implementations of this disclosure will be described using SF 120 as an example of a first device, SMF 130 as an example of a second device, AMF 140 as an example of a third device, and UPF 150 as an example of a fourth device. The scope of protection of this disclosure is not limited in this respect.

[0097] Figure 3 A signaling diagram illustrating an example of a perception registration process 300 according to various aspects of this disclosure is shown. For discussion purposes, process 300 will be referenced. Figure 1B Description. Process 300 may involve Figure 1B The base stations in question are 102, AMF 140, and SF120.

[0098] Typically, in process 300, it is assumed that the first base station 102-1 is a sensing device that performs sensing tasks and sends sensing measurement data to SF120. After the first base station 102-1 performs sensing registration with AMF 140 or SF 120, the first base station 102-1 will receive the sensing task and continue to enforce the sensing task.

[0099] like Figure 3 As shown, the first base station 102-1 sends a 310 uplink (UL) NGAP message to the AMF 140 via the N2 interface. This UL NGAP message includes the identifier (ID) of the first base station 102-1 and a sensing registration request message.

[0100] In some implementations, a dedicated or novel payload container (e.g., a sense message container) can be defined for UL NGAP messages. The sense message container can include sense registration request messages.

[0101] In some implementations, the first base station 102-1 may include its sensing capability information in the sensing registration request message.

[0102] In some implementations, the sensing capability information may include at least one of the following: supported sensing modes, supported sensing accuracy, confidence level, sensing resolution, false alarm probability, missed detection probability, refresh rate, maximum sensing service latency, and indicators supported by UP connections.

[0103] In some implementations, the perceptual mode may include at least one of the following: • Sensing Mode 1: The first base station 102-1 transmits and receives sensing signals; • Sensing mode 2: The first base station 102-1 sends a sensing signal, and the second base station 102-2 receives the sensing signal; • Sensing Mode 3: UE 104 sends a sensing signal, and the first base station 102-1 receives the sensing signal; • Perception Mode 4: UE 104 sends a perception signal, and another UE receives the perception signal; • Sensing Mode 5: The first base station 102-1 transmits a sensing signal, and the UE 104 receives the sensing signal; or • Sensing Mode 6: UE 104 sends a sensing signal and UE 104 receives the sensing signal.

[0104] Upon receiving the UL NGAP message, AMF 140 determines that the container includes the sensing registration request message between the first base station 102-1 and SF 120 based on the payload container type. AMF 140 then performs a 320 SF selection. For example, AMF 140 may perform SF selection based on at least one of the following: the location of the first base station 102-1, the service area of ​​the first base station 102-1, or the load of SF 120.

[0105] In some implementations, AMF 140 is already configured (e.g., via OAM or PLMN) with information about at least one SF. For example, information about SF 120 may include at least one of the following: SF 120's ID, SF 120's Internet Protocol (IP) address or Fully Qualified Domain Name (FQDN), and SF 120's service area. Alternatively, at least one SF may be registered with the Network Repository Function (NRF) by providing information about at least one SF. AMF 140 may request information about at least one SF from the NRF (not shown in the diagram). The NRF will check the service area of ​​AMF 140 and find the corresponding one or more SFs. The NRF will then provide AMF 140 with information about the one or more SFs.

[0106] AMF 140 sends a sensing registration request message 330 to the selected SF (e.g., SF 120). The ID of the first base station 102-1 can be included in the sensing registration request message. In this way, SF 120 can know the sensing base stations located in its service area. Then, SF 120 can select a suitable sensing base station (such as the first base station 102-1) based on the sensing capability information provided by the first base station 102-1 during the sensing registration process and the sensing task requirements.

[0107] SF 120 sends the ID of the first base station 102-1 (340) and the perception registration response message to AMF 140.

[0108] AMF 140 forwards the perception registration response 350 to the first base station 102-1 based on the ID of the first base station 102-1.

[0109] It should be noted that the AMF 140 can select one or more SFs to send a sensing registration request, and optionally send sensing capability information. For example, multiple SFs can be deployed in each given area. In this case, RAN service capabilities can be registered in multiple SFs. In one implementation, the AMF 140 can use the sensing capabilities of the first base station 102-1 (e.g., the type of the first base station 102-1) and the capabilities of multiple SFs to select one or more SFs suitable for (or capable of) serving the first base station 102-1. For example, if the first base station 102-1 supports the collection of non-3GPP sensing data, the AMF 140 can consider selecting an SF specifically for serving (or processing) non-3GPP sensing data. This requires the AMF 140 to have at least knowledge of the type of the first base station 102-1, where more detailed sensing capabilities are transparent to the AMF 140.

[0110] In some implementations, the first base station 102-1 can trigger the process for establishing a UP connection between the first base station 102-1 and SF 120. In such an implementation, the first base station 102-1 can send a request for establishing a UP connection to SMF 130. Alternatively, the first base station 102-1 can directly send a request for establishing a UP connection to SF 120.

[0111] Alternatively, in some implementations, SF 120 can trigger the process for establishing a UP connection between the first base station 102-1 and SF 120. In such an implementation, SF 120 can send a request for establishing the UP connection to the first base station 102-1 via AMF 140. Alternatively, SF 120 can send a request for establishing the UP connection to SMF 130 via AMF 140.

[0112] In some implementations, the UP connection between the first base station 102-1 and SF 120 can be a direct UP connection between the first base station 102-1 and SF 120. That is, the UP connection is established as follows: First base station 102-1 --- SF-U 124. Hereinafter, such a UP connection is also referred to as the first UP connection.

[0113] In some implementations, the UP connection between the first base station 102-1 and SF 120 can be a UP connection between the first base station 102-1 and SF 120 involving or via UPF 150. That is, the UP connection is established as follows: First base station 102-1 --- UPF 150 --- SF-U 124. Hereinafter, such a UP connection is also referred to as a second UP connection.

[0114] Figure 4A A signaling diagram illustrating an example procedure 400A for establishing a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 400A can be considered as an example implementation of method 200. For discussion purposes, procedure 400A will be referenced to... Figure 1B The process 400A may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF120.

[0115] Typically, in process 400A, the first base station 102-1 receives a first message from SF 120. The first message includes a sensing registration response message. Based on the sensing registration response message, the first base station 102-1 triggers a process for establishing a UP connection between itself and SF 120. To trigger the process, the first base station 102-1 sends a request for establishing the UP connection to SMF 130 via AMF 140. The UP connection is a connection between the first base station 102-1 and SF 120 involving or via UPF 150. Therefore, regarding, for example, UL transmission carrying sensing results, the first base station 102-1 needs to learn the address of UPF 150, and UPF 150 needs to learn the UP address of SF 120.

[0116] Specifically, the first base station 102-1 sends a sensing registration request message 410 to the SF 120 via the AMF 140. For example, the first base station 102-1 may send the sensing registration request message to the SF-C part 122 of the SF 120. Action 410 may be similar to... Figure 3 Actions 310, 320, and 330 are included. Therefore, for the sake of brevity, the details of action 410 are omitted.

[0117] Then, the first base station 102-1 receives the 415A sensing registration response message from the SF 120 via the AMF 140. For example, the first base station 102-1 can receive the sensing registration response message from the SF-C part 122 of the SF 120. Action 415A can be similar to... Figure 3 Actions 340 and 350 in the text.

[0118] The first base station 102-1 triggers the process of establishing a UP connection between the first base station 102-1 and SF 120 based on the sensing registration response message.

[0119] In some implementations, as long as the first base station 102-1 receives the registration response message from SF 120, the first base station 102-1 can trigger the process for establishing a UP connection.

[0120] Alternatively, in some implementations, the first base station 102-1 triggers the process for establishing a UP connection only if the registration response message includes a first indication. The first indication indicates that the SF 120 supports the transmission of sensed measurement data via the UP connection. Hereinafter, the first indication is also referred to as the "UP report support indication".

[0121] To trigger the process, the first base station 102-1 sends a 420 request to AMF 140 for the establishment of the UP connection.

[0122] In some implementations, the first base station 102-1 may send a UL NGAP message to the AMF 140. This NGAP message may include a dedicated or novel payload container, such as a sensing message container. The sensing message container may include a request for the establishment of a UP connection. Based on the type of payload container, the AMF 140 may identify that the UL NGAP message includes sensing messages between the first base station 102-1 and the SMF 130.

[0123] In some implementations, the NGAP message may also include a third indication. This third indication specifies that a UP connection will be established. Hereinafter, the third indication is also referred to as the "UP establishment indication." AMF 140 can determine, based on the UP establishment indication, that the first base station 102-1 will establish a UP connection for sensing. Therefore, AMF 140 can determine 425 information about SF 120 during the sensing registration process 300, based on the association between the first base station 102-1 and SF 120.

[0124] In some implementations, information about SF 120 does not include the SF 120's UP address. For example, information about SF 120 may include at least one of the following: the SF 120's ID, the SF 120's CP address, or the SF 120's FQDN. For example, the SF 120's CP address may include the SF 120's CP IP address or the SF 120's FQDN.

[0125] Then, AMF 140 forwards the request for establishing the UP connection and information about SF 120 to the selected SMF (such as SMF 130). In some implementations, AMF 140 may forward the request for establishing the UP connection and information about SF 120 together with the ID of the first base station 102-1.

[0126] In some implementations, AMF 140 can select an SMF from an NRF (not shown in the figure), and the awareness indication can be used by AMF 140 to enforce awareness session transmission by selecting an eligible SMF from the NRF. For example, if SMF 130 supports awareness operations registered by SF 120, AMF 140 can select SMF 130.

[0127] Upon receiving a request to establish a UP connection and information about SF 120, SMF 130 obtains the UP address of SF 120. The UP address of SF 120 is also known as the first UP address of SF 120.

[0128] In some implementations, the UP address of the SF 120 may include the Transport Network Layer (TNL) address of the SF 120. For example, the TNL address of the SF 120 may include the UP IP address and Tunnel Endpoint Identifier (TEID) of the SF 120.

[0129] In some implementations, to obtain the UP address of SF 120, SMF 130 sends a 435 request for the UP address of SF 120 to SF 120. For example, SMF 130 can use information about SF 120 received from AMF 140 to send a request for the UP address of SF 120 to SF-C section 122. Alternatively, SMF 130 can also send the ID of the first base station 102-1, or the ID of the sensing session, or the ID of the sensing task, to let SF 120 know which UP connection will be established.

[0130] When SF-C section 122 receives a request for the UP address of SF 120, it sends 440 a request for the UP address of SF 120 to SF-U section 124.

[0131] When SF-U section 124 receives a request for the UP address of SF 120, it sends 445 UP address of SF 120 to SF-C section 122.

[0132] When SF-C section 122 receives the UP address of SF 120, it sends 450 SF 120's UP address to SMF 130.

[0133] When SMF 130 receives the UP address of SF 120, it sends 455 SF 120's UP address to UPF 150.

[0134] Then, UPF 150 sends at least one UP address of UPF 150 to SMF 130.

[0135] In some implementations, actions 455 and 460 can be performed during the N4 session establishment / modification process. For example, upon receiving the UP address of SF 120, SMF 130 triggers the N4 session establishment / modification process to establish an N4 session between SMF 130 and a selected UPF (such as UPF 150). SMF 130 can select the UPF from the NRF (not shown in the figure), and a sense indication can be used by SMF 130 to select an eligible UPF from the NRF for sense session transmission. During the N4 session establishment / modification process, SMF 130 can provide Packet Detection Rules (PDR), QoS-related information (e.g., MBR for Service Data Flow (SDF), Guaranteed Stream Bit Rate (GFBR) and Maximum Stream Bit Rate (MFBR) for Guaranteed Bit Rate (GBR) QoS flows), corresponding packet tagging information on the SF 120 side, and the UP address of SF 120. UPF 150 replies to SMF 130 with the UP address of UPF 150.

[0136] In some implementations, a new type of N4 session can be established between the SMF 130 and the UPF 150 for use in sensing applications.

[0137] In some implementations, at least one UP address of the UPF 150 may include the UP address of the UPF 150 used for transmissions from the first base station 102-1 to the UPF 150. This UP address of the UPF 150 is also referred to as the UP address of the UPF 150 for UL.

[0138] In some implementations, optionally, a downlink (DL) transmission from SF-U section 124 to UPF 150 may be required for sensing relevant messages. In such an implementation, SMF 130 may send a bidirectional tunneling indication to UPF 150. This bidirectional tunneling indication specifies that the UP address of UPF 150 for UL and the UP address of UPF 150 for DL ​​need to be provided. For example, SMF 130 may send the bidirectional tunneling indication along with the UP address of SF 120 to UPF 150. Therefore, UPF 150 may send the UP address of UPF 150 for UL and the UP address of UPF 150 for DL ​​to SMF 130.

[0139] Then, SMF 130 sends the UP address of UPF 150 for UL to the first base station 102-1 via AMF 140.

[0140] Optionally, if DL transmission is required, SMF 130 can send the UP address of UPF 150 for DL ​​to SF-U section 124.

[0141] After the first base station 102-1 receives the UP address of UPF 150 for UL from SMF 130, a tunnel is established between the first base station 102-1 and UPF 150. After UPF 150 receives the UP address of SF 120 from SMF 130, a tunnel is established between UPF 150 and SF 120-U. Based on these two tunnels, the UP connection from the first base station 102-1 via UPF 150 to SF 120-U is finally established.

[0142] In some implementations, the UP connection between the first base station 102-1 and SF 120 can be per sensing task or per first base station 102-1.

[0143] Figure 4B A signaling diagram illustrating an example procedure 400B supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 400B can be considered as an example implementation of method 200. For discussion purposes, procedure 400B will be referenced... Figure 1B The process 400B may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0144] Typically, in process 400B, the first base station 102-1 receives a first message from SF 120. This first message includes a Sensing Service Request message. Based on the Sensing Service Request message, the first base station 102-1 triggers a process for establishing a UP connection between itself and SF 120. To trigger this process, the first base station 102-1 sends a request for the establishment of the UP connection to SMF 130 via AMF 140. The UP connection is a connection between the first base station 102-1 and SF 120 involving or via UPF 150.

[0145] Specifically, after the sensing registration process (such as sensing registration process 300), the first base station 102-1 receives a 415B sensing service request message from SF 120 via AMF 140. For example, the first base station 102-1 may receive the sensing service request message from the SF-C part 122 of SF 120.

[0146] In some implementations, the perception service request message may include information about the perception task.

[0147] Alternatively or additionally, the sensing service request message may include a second instruction. The second instruction indicates that SF 120 requests the transmission of sensing measurement data via the UP connection. Hereinafter, the second instruction is also referred to as the "UP request instruction".

[0148] Alternatively or otherwise, the awareness service request message may include UP report support instructions and UP request instructions.

[0149] Alternatively or elsewhere, the perception service request message may include an UP report support instruction.

[0150] In some implementations, including an UP request indication in the awareness service request message means that the UP report support indicator has been exchanged and that SF 120 now wants to start a UP transmission.

[0151] The first base station 102-1 triggers the process of establishing a UP connection between the first base station 102-1 and SF 120 based on the sensing service request message.

[0152] In some implementations, as soon as the first base station 102-1 receives a sensing service request message from SF 120, the first base station 102-1 triggers the process for establishing a UP connection.

[0153] Alternatively, in some implementations, the first base station 102-1 triggers the process for establishing a UP connection only if the sensing service request includes at least one of a UP report support indication and a UP request indication.

[0154] Actions 420, 425, 430, 435, 440, 445, 450, 455, 460, 465, and 470 in process 400B are similar to those in process 400A. For the sake of brevity, the details of these actions are omitted.

[0155] In some implementations, the sensing service request message may include the UP address of SF 120. In such an implementation, actions 425, 435, 440, 445, and 450 in process 400B will not be executed. In such an implementation, the first base station 102-1 may provide the UP address of SF 120 to the SMF 130 via the AMF 140. For example, the first base station 102-1 may send a request 420 for the establishment of a UP connection to the AMF 140. The request for the establishment of a UP connection includes the UP address of SF 120. Then, the AMF 140 forwards the request for the establishment of a UP connection including the UP address of SF 120 to the SMF 130 via a forwarding message 430, and further, the SMF 130 sends the UP address of SF 120 via a forwarding message 455 to the UPF 150.

[0156] Figure 4CA signaling diagram illustrating an example procedure 400C for establishing a sensed UP connection, according to various aspects of this disclosure, is shown. Example procedure 400C can be considered as an example implementation of method 200. For discussion purposes, procedure 400C will refer to... Figure 1B The process 400C may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0157] Typically, in process 400C, the first base station 102-1 receives a first message from AMF 140. This first message includes a sensing service request message. Based on the sensing service request message, the first base station 102-1 triggers a process for establishing a UP connection between itself and SF 120. To trigger this process, the first base station 102-1 sends a request for the establishment of the UP connection to SMF 130 via AMF 140. A UP connection is a connection between the first base station 102-1 and SF 120 that involves or is via UPF 150.

[0158] Specifically, SF 120 first assigns sensing tasks to AMF 140 and requests AMF 140 to select sensing tasks and assign them to the base station. For example, SF 120 sends a 410C sensing service request message to AMF 140. This sensing service request message may include information about the sensing tasks.

[0159] Upon receiving a sensing service request message, AMF 140 sends the sensing service request message 415C to the first base station 102-1. This sensing service request message may include information about the sensing task.

[0160] Alternatively or elsewhere, the sense service request message may include an UP request indication.

[0161] Alternatively or otherwise, the awareness service request message may include UP report support instructions and UP request instructions.

[0162] Alternatively or elsewhere, the perception service request message may include an UP report support instruction.

[0163] In some implementations, including a UP request indication in the awareness service request message means that a UP report support indication has been exchanged and that SF 120 now wants to begin a UP transmission.

[0164] The first base station 102-1 triggers the process of establishing a UP connection between the first base station 102-1 and SF 120 based on the sensing service request message.

[0165] In some implementations, as soon as the first base station 102-1 receives a sensing service request message from the AMF 140, the first base station 102-1 triggers the process for establishing a UP connection.

[0166] Alternatively or otherwise, in some implementations, the first base station 102-1 triggers the process for establishing a UP connection only if the sensing service request includes at least one of a UP report support indication and a UP request indication.

[0167] Actions 420, 425, 430, 435, 440, 445, 450, 455, 460, 465, and 470 in process 400B are similar to those in process 400A. For the sake of brevity, the details of these actions are omitted.

[0168] In some implementations, the sensing service request message may include the UP address of SF 120. In such an implementation, actions 425, 435, 440, 445, and 450 in process 400C will not be executed. In such an implementation, the first base station 102-1 may provide the UP address of SF 120 to SMF 130 via AMF 140.

[0169] Figure 4D A signaling diagram illustrating an example procedure 400D supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 400D can be considered as an example implementation of method 200. For discussion purposes, procedure 400D will be referenced to... Figure 1B The process 400D may involve a first base station 102-1, a second base station 102-2, an AMF 140, an SMF 130, a UPF 150, and an SF 120.

[0170] Typically, process 400D involves a handover scenario where it is assumed that the sensed object is moving toward a target base station (such as the first base station 102-1). During the handover, the first base station 102-1 receives the 415D first message from the source base station (such as the second base station 102-2). The first message may include information about the sensed object and information about the SF 120. The information about the SF 120 does not include the SF 120's UP address.

[0171] Based on a first message, the first base station 102-1 triggers a process for establishing a UP connection between itself and SF 120. This UP connection is a connection between the first base station 102-1 and SF 120 involving or via UPF 150. To trigger this process, the first base station 102-1 sends a request 420 for the establishment of the UP connection, along with information about SF 120, to AMF 140. Therefore, AMF 140 does not need to determine information about SF 120 for the first base station 102-1. That is, action 425 in processes 400A to 400C is not executed.

[0172] In some implementations, if the second base station 102-2 (acting as the source base station) directly connects to SF 120-U using the UP address without the involvement of UPF 150, the UP address of SF 120-U can be used by the second base station 102-1 and will be provided to the first base station 102-1 (acting as the target base station). Then, when the first base station 102-1 sends a request to SMF 130 for the establishment of the UP connection, it can send the UP address of SF 120-U to SMF 130. Therefore, actions 435, 440, 445, and 450 in process 400D will not be executed.

[0173] In some implementations, when the first base station 102-1 receives the first message from the second base station 102-2 and then decides to establish a UP connection, the first base station 102-1 may send the ID of the sensing task when sending a request for the establishment of the UP connection to the SMF 130.

[0174] In some implementations, if the first base station 102-1 (acting as the target base station) is outside the service area of ​​SF 120, AMF 140 can notify SF 120 that the sensing task cannot be interrupted after the handover.

[0175] Actions 430, 435, 440, 445, 450, 455, 460, 465, and 470 in process 400D are similar to those in process 400A. For the sake of brevity, the details of these actions are omitted.

[0176] Figure 5A A signaling diagram illustrating an example procedure 500A for establishing a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 500A can be considered as an example implementation of method 200. For discussion purposes, procedure 500A will be referenced... Figure 1B The process 500A may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0177] Similar to process 400A, in process 500A, the first base station 102-1 triggers the establishment of a UP connection between itself and SF 120 based on a sensing registration response message. The UP connection is a direct UP connection between the first base station 102-1 and SF 120. Actions 410 and 415A in process 500A are similar to those in process 400A. For simplicity, the details of these operations are omitted.

[0178] To trigger the process, the first base station 102-1 sends a 520A request to AMF 140 for the establishment of the UP connection.

[0179] In some implementations, the first base station 102-1 may send a UL NGAP message to the AMF 140. This NGAP message may include a dedicated or novel payload container, such as a sensing message container. The sensing message container may include a request for the establishment of a UP connection. Based on the type of payload container, the AMF 140 may identify that the UL NGAP message includes sensing messages between the first base station 102-1 and the SF 120.

[0180] In some implementations, the NGAP message may also include a UP establishment indication. AMF 140 can determine, based on the UP establishment indication, that the first base station 102-1 will establish a UP connection for sensing. Therefore, AMF 140 can determine 525 information about SF 120 during the sensing registration process 300, based on the association between the first base station 102-1 and SF 120.

[0181] In some implementations, information about SF 120 does not include the SF 120's UP address. For example, information about SF 120 may include at least one of the following: the SF 120's ID, the SF 120's CP address, or the SF 120's FQDN. For example, the SF 120's CP address may include the SF 120's CP IP address.

[0182] In some implementations, if a DL transmission from SF 120 to the first base station 102-1 is required, the NGAP message may also include the UP address of the first base station 102-1.

[0183] Then, AMF 140 forwards the request for establishing the UP connection to SF 120. For example, AMF 140 forwards the request for establishing the UP connection to SF-C section 122 of SF 120.

[0184] In some implementations, the AMF 140 can forward the request for establishing a UP connection along with the ID of the first base station 102-1.

[0185] Upon receiving a request to establish a UP connection, SF-C section 122 sends 440 to SF-U section 124 a request for the UP address of SF 120.

[0186] Upon receiving a request for the UP address of SF 120, SF-U section 124 sends 445 SF120's UP address to SF-C section 122.

[0187] Upon receiving the UP address of SF 120, if SF 120 agrees to establish a direct UP connection between the first base station 102-1 and SF 120, then SF-C part 122 sends a 550A response to the request for the establishment of the UP connection to the first base station 102-1. This response includes the UP address of SF 120 to the first base station 102-1.

[0188] In some implementations, the response may also include the ID of the first base station 102-1.

[0189] Upon receiving a response including the UP address of SF 120, the first base station 102-1 may optionally send a 555 acknowledgment message to SF 120, indicating that it has received the UP address of SF 120.

[0190] Figure 5B A signaling diagram illustrating an example procedure 500B supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 500B can be considered as an example implementation of method 200. For discussion purposes, procedure 500B will refer to... Figure 1B The process 500B may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0191] Similar to process 400B, in process 500B, the first base station 102-1 triggers a process for establishing a UP connection between the first base station 102-1 and the SF 120 based on a sensing service request message received from the SF 120. The UP connection is a direct UP connection between the first base station 102-1 and the SF 120. Actions 415B, 440, and 445 in process 500B are similar to those in process 400B. Actions 520A, 525, 530, 550A, and 555 in process 500B are similar to those in process 500A. For brevity, the details of these actions are omitted.

[0192] Figure 5C A signaling diagram illustrating an example procedure 500C for establishing a sensed UP connection, according to various aspects of this disclosure, is shown. Example procedure 500C can be considered as an example implementation of method 200. For discussion purposes, procedure 500C will refer to... Figure 1B The process 500C may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0193] Similar to process 400C, in process 500C, the first base station 102-1 triggers a process for establishing a UP connection between the first base station 102-1 and SF 120 based on a sensing service request message received from AMF 140. The UP connection is a direct UP connection between the first base station 102-1 and SF 120. Actions 410C, 415C, 440, and 445 in process 500C are similar to those in process 400C. Actions 520A, 525, 530, 550A, and 555 in process 500C are similar to those in process 500A. For brevity, the details of these actions are omitted.

[0194] Figure 5D A signaling diagram illustrating an example procedure 500D supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 500D can be considered as an example implementation of method 200. For discussion purposes, procedure 500D will be referenced to... Figure 1B The process 500D may involve a first base station 102-1, a second base station 102-2, an AMF 140, an SMF 130, a UPF 150, and an SF 120.

[0195] Similar to process 400D, process 500D involves a handover scenario where it is assumed that the sensed object is moving toward a target base station (such as the first base station 102-1). During the handover, the first base station 102-1 receives a 415D first message from a source base station (such as the second base station 102-2). This first message may include information about the sensed task and information about SF 120. The information about SF 120 does not include the UP address of SF 120.

[0196] Based on a first message, the first base station 102-1 triggers the process of establishing a UP connection between the first base station 102-1 and SF 120. This UP connection is a direct UP connection between the first base station 102-1 and SF 120.

[0197] Since the first base station 102-1 has information about SF 120, in order to trigger the process, the first base station 102-1 directly sends a 520B request for the establishment of the UP connection to SF 120, without needing to be forwarded by AMF 140. Therefore, action 425 in processes 500A to 500C is not executed.

[0198] Actions 440 and 445 in process 500D are similar to those in process 400D. Actions 550A and 555 in process 500D are similar to those in process 500A. For the sake of brevity, the details of these actions are omitted.

[0199] In some implementations, if the second base station 102-2 (acting as the source base station) directly uses the UP connection of SF 120-U without the participation of UPF 150, then the UP address of SF 120-U can be used by the second base station 102-1, and this UP address will be provided to the first base station 102-1 (acting as the target base station). Then, the first base station 102-1 can directly establish a direct UP connection. Therefore, actions 440, 445, 550A, and 555 in process 500D will not be executed.

[0200] Figure 5E A signaling diagram illustrating an example procedure 500E supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 500E can be considered as an example implementation of method 200. For discussion purposes, procedure 500E will refer to... Figure 1B The process 500E may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0201] Similar to process 400A, in process 500E, the first base station 102-1 triggers a process for establishing a UP connection between the first base station 102-1 and SF 120 based on a sensing registration response message. The UP connection is a UP connection between the first base station 102-1 and SF 120 involving UPF 150.

[0202] Actions 410, 415A, 440, 445, 455, 460, 465, and 470 in process 500E are similar to those in process 400A. Actions 520A, 525, and 530 in process 500E are similar to those in process 500A. For the sake of brevity, details of these actions are omitted.

[0203] The difference between process 500E and processes 400A and 500A lies in actions 550B, 552, and 554.

[0204] Specifically, upon receiving the UP address of SF 120, SF-C section 122 sends a 550B response to AMF 140 for the request to establish a UP connection, along with the UP address of SF 120.

[0205] Then, AMF 140 forwards the response 552 to the first base station 102-1 in response to the request for the establishment of the UP connection.

[0206] Additionally, AMF 140 selects an SMF (such as SMF 130) and provides the UP address of SF 120 along with the UP setup instruction to SMF 130.

[0207] Using process 500E, a UP connection is established between the first base station 102-1 and SF 120 via UPF 150.

[0208] Figure 5F A signaling diagram illustrating an example procedure 500F supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 500F can be considered as an example implementation of method 200. For discussion purposes, procedure 500F will refer to... Figure 1B The process 500F may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0209] Similar to process 400B, in process 500F, the first base station 102-1 triggers a process for establishing a UP connection between the first base station 102-1 and SF 120 based on a sensing service request message received from SF 120. The UP connection is a UP connection between the first base station 102-1 and SF 120 involving UPF 150. Actions 415B, 440, 445, 455, 460, 465, and 470 in process 500E are similar to those actions in process 400B. Actions 520A, 525, 530, 550B, 552, and 554 in process 500F are similar to those actions in process 500E. For brevity, details of these actions are omitted.

[0210] Figure 5G A signaling diagram illustrating an example procedure 500G supporting awareness of UP connections according to various aspects of this disclosure is shown. Example procedure 500G can be considered as an example implementation of method 200. For discussion purposes, procedure 500G will be referenced... Figure 1BThe process described may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0211] Similar to process 400C, in process 500G, the first base station 102-1 triggers a process for establishing a UP connection between the first base station 102-1 and SF 120 based on a sensing service request message received from AMF 140. The UP connection is a UP connection between the first base station 102-1 and SF 120 involving UPF 150. Actions 410C, 415C, 440, 445, 455, 460, 465, and 470 in process 500G are similar to those actions in process 400C. Actions 520A, 525, 530, 550B, 552, and 554 in process 500G are similar to those actions in process 500E. For brevity, details of these actions are omitted.

[0212] Figure 5H A flowchart illustrating an example procedure 500H for establishing a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 500H can be considered as an example implementation of method 200. For discussion purposes, procedure 500H will refer to... Figure 1B The process 500H may involve the first base station 102-1, the second base station 102-2, AMF 140, SMF130, UPF 150, and SF 120.

[0213] Similar to process 400D, process 500H involves a handover scenario where it is assumed that the sensed object is moving toward a target base station (such as the first base station 102-1). During the handover, the first base station 102-1 receives a 415D first message from a source base station (such as the second base station 102-2). The first message may include information about the sensed task and information about SF120. The information about SF120 does not include the UP address of SF120.

[0214] Based on a first message, the first base station 102-1 triggers the process of establishing a UP connection between the first base station 102-1 and SF 120. The UP connection is a UP connection between the first base station 102-1 and SF 120 involving UPF 150.

[0215] Since the first base station 102-1 has information about SF 120, in order to trigger the process, the first base station 102-1 directly sends a 520B request for the establishment of the UP connection to SF 120, without needing to be forwarded by AMF 140.

[0216] Actions 440, 445, 455, 460, 465, and 470 in process 500H are similar to those in process 400D. Actions 520B, 550B, 552, and 554 in process 500H are similar to those in process 500E. For the sake of brevity, details of these actions are omitted.

[0217] In some implementations, it is possible for SF 120 to have the ability to select SMF 130 when sending a request for establishing an UP connection or in response to SMF 130, rather than requesting AMF 140 to perform the selection action. For example, SF 120 can refer to the NRF to determine the appropriate SMF that supports sensing operations.

[0218] Figure 6 A flowchart of a method 600 supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Operation of method 600 may be implemented by the device or components thereof described herein. For example, operation of method 600 may be performed by the first means described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0219] At point 610, the first device receives the second message.

[0220] At point 620, the first device sends, at least based on the second message, a first UP address of the first device and a request for establishing a sensing UP connection between the first base station and the first device to the first base station or the second device.

[0221] Some implementations of this disclosure will be described below using SF 120 as an example of a first device, SMF 130 as an example of a second device, AMF 140 as an example of a third device, and UPF 150 as an example of a fourth device. The scope of this disclosure is not limited in this respect.

[0222] Figure 7A A signaling diagram illustrating an example procedure 700A for establishing a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 700A can be considered as an example implementation of method 600. For discussion purposes, procedure 700A will be referenced to... Figure 1B The process 700A may involve the first base station 102-1, AMF 140, and SF 120.

[0223] In process 700A, SF 120 receives the second message 710A from the first base station 102-1 via AMF 140. For example, the SF-C portion 122 of SF120 receives the second message from the first base station 102-1 via AMF 140. This second message includes a sensing registration request message.

[0224] In some implementations, the second message may include a fourth indication indicating that the first base station 102-1 supports the transmission of sensed measurement data via the UP connection. Based on the fourth indication, SF 120 knows that the first base station 102-1 supports UP transmission and is able to proceed with establishing a UP connection with it.

[0225] Based on the sensing registration request message, SF 120 triggers the process for establishing a UP connection between the first base station 102-1 and SF 120. To trigger this process, SF-C part 122 sends a 720 request for the UP address of SF 120 to SF-U part 124.

[0226] When SF-U section 124 receives a request for the UP address of SF 120, it sends 725 UP address of SF 120 to SF-C section 122.

[0227] Upon receiving the UP address of SF 120, SF-C section 122 sends a 730A request for establishing a UP connection and the UP address of SF 120 to the first base station 102-1. Therefore, when the request for establishing a UP connection is received, the first base station 102-1 no longer needs to request the UP address of SF 120. The UP connection is a direct UP connection between the first base station 102-1 and SF 120.

[0228] In some implementations, optionally, the SF-C section 122 may send information about the sensing task, as well as a request for establishing a UP connection and the UP address of SF 120. For example, the information about the sensing task may include the ID of the sensing task.

[0229] In some implementations, AMF 140 may optionally forward the UP address of the first base station 102-1 (provided by the first base station 102-1) to SF 120 to establish a bidirectional transmission path. Typically, if a DL transmission from SF 120 to the first base station 102-1 is required, SF 120 will provide a bidirectional tunnel indication.

[0230] Figure 7B A signaling diagram illustrating an example procedure 700B supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 700B can be considered as an example implementation of method 600. For discussion purposes, procedure 700B will refer to... Figure 1B The process 700B may involve the first base station 102-1, AMF 140, and SF 120.

[0231] In process 700B, SF 120 receives a sensing task 710B from a consumer (not shown) of the sensing service. For example, SF-C portion 122 of SF 120 receives the sensing task from the consumer. Then, SF 120 assigns the sensing task 715B to the first base station 102-1. For future sensing measurement data transmission related to the assigned sensing task, SF 120 triggers a process for establishing a UP connection between the first base station 102-1 and SF 120 based on the sensing task. The UP connection is a direct UP connection between the first base station 102-1 and SF 120.

[0232] Actions 720, 725, 730A, and 735A in process 700B are similar to those in process 700A. For the sake of brevity, the details of these actions are omitted.

[0233] Figure 7C A signaling diagram illustrating an example procedure 700C supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 700C can be considered as an example implementation of method 600. For discussion purposes, procedure 700C will refer to... Figure 1B The process 700C may involve a first base station 102-1, a second base station 102-2, an AMF 140, and an SF 120.

[0234] During process 700C, SF 120 receives a second message 710C from the second base station 102-2 during handover. The second message may include the ID of the first base station 102-1 associated with the ID of the sensing task, or the ID of the UE 104 associated with the handover. During handover, the second base station 102-2 may act as the source base station, and the first base station 102-1 may act as the target base station.

[0235] Then, SF 120 triggers the process of establishing a UP connection between the first base station 102-1 and SF 120 based on the ID of the first base station 102-1 or the ID of the UE 104. This UP connection is a direct UP connection between the first base station 102-1 and SF 120.

[0236] Actions 720, 725, 730A, and 735A in process 700C are similar to those in process 700A. For the sake of brevity, the details of these actions are omitted.

[0237] Figure 7DA signaling diagram illustrating an example procedure 700D supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 700D can be considered as an example implementation of method 600. For discussion purposes, procedure 700D will be referenced to... Figure 1B The process 700D may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0238] Similar to process 700A, in process 700D, SF 120 triggers a process for establishing a UP connection between the first base station 102-1 and SF 120 based on a sensing registration request message received from the first base station 102-1. The UP connection is a UP connection between the first base station 102-1 and SF 120 involving UPF 150.

[0239] Actions 710A, 720, and 725 in process 700D are similar to those in process 700A. For the sake of brevity, the details of these actions are omitted.

[0240] The difference between process 700D and process 700A lies in actions 730B, 735B, 740, 745, 750, and 755.

[0241] Specifically, to trigger the process for establishing a UP connection, SF 120 sends a sensing message to SMF 130 via AMF 140. This sensing message includes a request for establishing a sensing UP connection between the first base station 102-1 and SF 120. The request for establishing the UP connection includes the UP address of SF 120. For example, SF 120 sends a 730B sensing message to AMF 140, which includes a request for establishing a UP connection that includes the UP address of SF 120.

[0242] The AMF 140 identifies the sensing message as being between the SF 120 and the SMF. The AMF 140 then selects an SMF (such as the SMF 130) and forwards the sensing message 735B to the SMF 130.

[0243] Actions 740, 745, 750, and 755 in process 700D are similar to actions 455, 460, 465, and 470 in process 400A. For the sake of brevity, the details of these actions have been omitted.

[0244] Figure 7EA signaling diagram illustrating an example procedure 700E supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 700E can be considered as an example implementation of method 600. For discussion purposes, procedure 700E will refer to... Figure 1B The process 700E may involve the first base station 102-1, AMF 140, SMF 130, UPF 150, and SF 120.

[0245] Similar to process 700B, in process 700E, SF 120 triggers a process for establishing a UP connection between the first base station 102-1 and SF 120 based on a sensing task. The UP connection is a UP connection between the first base station 102-1 and SF 120 involving UPF150.

[0246] Actions 710B and 715B in process 700E are similar to those in process 700B. Actions 720 and 725 in process 700E are similar to those in process 700A. Actions 730B, 735B, 740, 745, 750, and 755 in process 700E are similar to those in process 700D. For the sake of brevity, the details of these operations are omitted.

[0247] Figure 7F A signaling diagram illustrating an example procedure 700F supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Example procedure 700F can be considered as an example implementation of method 600. For discussion purposes, procedure 700F will refer to... Figure 1B The process 700F may involve a first base station 102-1, a second base station 102-2, an AMF 140, an SMF 130, a UPF 150, and an SF 120.

[0248] Similar to procedure 700C, in procedure 700F, SF 120 triggers a process for establishing a UP connection between first base station 102-1 and SF 120 based on a second message received from second base station 102-2. The second message may include the ID of first base station 102-1 associated with the ID of a sensing task, or the ID of UE 104 associated with handover. During handover, second base station 102-2 may act as the source base station, and first base station 102-1 may act as the target base station. The UP connection is a UP connection between first base station 102-1 and SF 120 involving UPF 150.

[0249] Action 710C in process 700F is similar to action 710C in process 700C. Actions 720 and 725 in process 700F are similar to actions 720 and 725 in process 700A. Actions 730B, 735B, 740, 745, 750, and 755 in process 700F are similar to actions 730B, 735B, 740, 745, 750, and 755 in process 700D. For the sake of brevity, the details of these actions are omitted.

[0250] Figure 8 An example of a device 800 supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Device 800 may be an example of a first base station 102-1, SF 120, SMF 130, AMF 140, or UPF 150 as described herein. Device 800 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 800 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 802, memory 804, transceiver 806, and optionally, I / O controller 808. These components may be electrically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0251] Processor 802, memory 804, transceiver 806, or various combinations thereof or various components thereof may be examples of components for performing various aspects of the present disclosure as described herein. For example, processor 802, memory 804, transceiver 806, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0252] In some implementations, processor 802, memory 804, transceiver 806, or various combinations or components thereof, may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include: a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support components for performing the functions described herein. In some implementations, processor 802 and memory 804 coupled to processor 802 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 804 are executed by processor 802).

[0253] For example, processor 802 may support wireless communication at device 800 according to the examples disclosed herein. Processor 802 may be configured to support components for performing: receiving a first message at a first base station; sending a request to a first device or a second device for establishing a sensed UP connection between the first base station and the first device, based at least on the first message; and receiving a response from the first device or the second device, the response including: a first UP address of the first device or a second UP address of the fourth device.

[0254] Alternatively, in some implementations, processor 802 may be configured to support components for performing the following: receiving, at a first device, a request from a second device, a base station, or a third device for establishing a sensed UP connection between the first base station and the first device; and sending a first UP address of the first device to the second device, the base station, or the third device.

[0255] Alternatively, in some embodiments, processor 802 may be configured to support components for performing: obtaining a first UP address of the first device at a second device; sending the first UP address of the first device to a fourth device; receiving at least one UP address of the fourth device from the fourth device; and sending one of the at least one UP address of the fourth device to a first base station for establishing a sensed UP connection between the first base station and the first device.

[0256] Alternatively, in some implementations, processor 802 may be configured to support components for performing the following: receiving, at a third device, a request from a first base station or a first device for establishing a sensing UP connection between the first base station and the first device; and sending a request to a second device.

[0257] Alternatively, in some implementations, processor 802 may be configured to support components for performing: receiving a second message at a first device; and, at least based on the second message, sending a first UP address of the first device to a first base station or a second device, and a request for establishing a sensed UP connection between the first base station and the first device.

[0258] Processor 802 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 802 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into processor 802. Processor 802 may be configured to execute computer-readable instructions stored in memory (e.g., memory 804) to cause device 800 to perform various functions of this disclosure.

[0259] Memory 804 may include random access memory (RAM) and read-only memory (ROM). Memory 804 may store computer-readable, computer-executable code, including instructions that, when executed by processor 802, cause device 800 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executable by processor 802, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 804 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0260] I / O controller 808 can manage input and output signals for device 800. I / O controller 808 can also manage peripheral devices not integrated into device 800. In some implementations, I / O controller 808 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 808 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 808 can be implemented as part of a processor (such as processor 806). In some implementations, a user can interact with device 800 via I / O controller 808 or via hardware components controlled by I / O controller 808.

[0261] In some implementations, device 800 may include a single antenna 810. However, in other implementations, device 800 may have more than one antenna 810 (i.e., multiple antennas), including multiple antenna panels or antenna arrays that can concurrently transmit or receive multiple wireless transmissions. Transceiver 806 can communicate bidirectionally via one or more antennas 810, wired or wireless links, as described herein. For example, transceiver 806 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 806 may also include a modem for modulating packets to provide modulated packets to one or more antennas 810 for transmission, and for demodulating packets received from one or more antennas 810. Transceiver 806 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0262] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes, such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 810 for transmitting the amplified signal over the air or wireless medium.

[0263] Figure 9 A flowchart of a method 900 supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Operation of method 900 may be implemented by the device or components thereof described herein. For example, operation of method 900 may be performed by a first means (such as SF 120) described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Alternatively or additionally, the device may use dedicated hardware to perform aspects of the described functions.

[0264] At 910, the method may include: receiving, at a first device, a request from a second device, a base station, or a third device for establishing a sensing UP connection between the first base station and the first device. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be derived from references... Figure 1B The device described performs the operation.

[0265] At 920, the method may include: sending the first UP address of the first device to a second device, a base station, or a third device. The operation at 920 can be performed according to the examples described herein. In some implementations, aspects of the operation at 920 may be derived from references... Figure 1B The device described performs the operation.

[0266] Figure 10 A flowchart of a method 1000 supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Operation of method 1000 may be implemented by the device or components thereof described herein. For example, operation of method 1000 may be performed by a second means (e.g., SMF 130) described herein. In some implementations, the device may execute an instruction set to control functional elements of the device to perform the described functions. Alternatively or additionally, the device may use dedicated hardware to perform aspects of the described functions.

[0267] At 1010, the method may include: obtaining the first UP address of the first device at the second device. The operation of 1010 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1010 may be derived from references... Figure 1B The device described performs the operation.

[0268] At point 1020, the method may include: sending the first UP address of the first device to the fourth device. The operation at 1020 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1020 may be derived from references... Figure 1B The device described performs the operation.

[0269] At 1030, the method may include: receiving at least one UP address of the fourth device from the fourth device. The operation of 1030 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1030 may be derived from references... Figure 1B The device described performs the operation.

[0270] At 1040, the method may include: sending a UP address from at least one UP address of the fourth device to the first base station, and establishing a sensing UP connection between the first base station and the first device. The operation of 1040 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1040 may be derived from references... Figure 1B The device described performs the operation.

[0271] Figure 11A flowchart of a method 1100 supporting the establishment of a sensed UP connection according to various aspects of this disclosure is shown. Operation of method 1100 may be implemented by the device or components thereof described herein. For example, operation of method 1100 may be performed by a third device (such as AMF 140) described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Alternatively or additionally, the device may use dedicated hardware to perform aspects of the described functions.

[0272] At 1110, the method may include: receiving, at a third device, a request from the first base station or the first device for establishing a sensing UP connection between the first base station and the first device. The operation of 1110 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1110 may be referenced. Figure 1B The device described performs the operation.

[0273] At 1120, the method may include sending a request to the second device. The operation at 1120 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1120 can be referenced. Figure 1B The device described performs the operation.

[0274] A receiver chain can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain may include one or more antennas 810 for receiving signals over the air or a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation techniques applied during signal transmission. The receiver chain may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0275] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0276] The various exemplary frames and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors incorporating a DSP core, or any other such configuration).

[0277] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0278] Computer-readable media include both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.

[0279] As used herein, including in the claims, the article “a (a)” preceding an element is not limited and should be understood to refer to “at least one” or “one or more” of that element. The terms “a (a),” “at least one,” “one or more,” and “at least one of one or more” are used interchangeably. As used herein, including in the claims, the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Moreover, as used herein, including in the claims, “set” can include one or more elements.

[0280] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first base station, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the first base station: Receive the first message; Based at least on the first message, a request for establishing a user plane (UP) connection for sensing between the first base station and the first device is sent to the first device or the second device; as well as Receive a response from the first device or the second device, the response including: the first UP address of the first device or the second UP address of the fourth device.

2. The first base station according to claim 1, wherein the first base station is configured to receive the first message by: Receive a sensing registration response message from the first device.

3. The first base station according to claim 1, wherein the first base station is configured to receive the first message by: The device receives a sensing service request message from either the first or the third device. The sensing service request message includes information about the sensing task.

4. The first base station according to claim 1, wherein: The first message includes at least one of the following: The first indication specifies that the first device supports the transmission of sensing measurement data via the UP connection, or The second instruction indicates that the first device requests the transmission of the sensing measurement data via the UP connection; and The first base station is configured to send the request for establishing the UP connection based on at least one of the following: The first instruction, or The second instruction.

5. The first base station according to claim 1, wherein the first base station is configured to receive the first message by: During the handover, information about the sensing task and information about the first device are received from the second base station.

6. The first base station of claim 1, wherein the first base station is configured to send the request for establishment of the UP connection to the second device via the third device by: Send the request for the establishment of the UP connection, and a third indication that the UP connection will be established.

7. A first device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the first device: Receive a request from a second device, a base station, or a third device for establishing a user plane (UP) connection for sensing between the first base station and the first device; as well as The first UP address of the first device is sent to the second device, the base station, or the third device.

8. A second device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the second device: Obtain the first user plane (UP) address of the first device; Send the first UP address of the first device to the fourth device; Receive at least one UP address of the fourth device from the fourth device; as well as Send one of the at least one UP addresses of the fourth device to the first base station for establishing a sensing UP connection between the first base station and the first device.

9. The second apparatus of claim 8, wherein the second apparatus is configured to obtain the first UP address of the first apparatus by: Receive a request from the third device for establishing a UP connection between the first base station and the first device; Send a request for the first UP address of the first device to the first device; as well as Receive the first UP address of the first device from the first device.

10. The second apparatus of claim 8, wherein the second apparatus is configured to obtain the first UP address of the first apparatus by: A request is received from a third device to establish a UP connection between the first base station and the first device, the request including the first UP address of the first device.

11. The second apparatus according to claim 8, wherein: The at least one UP address of the fourth device includes: a second UP address of the fourth device, the second UP address being used for transmission from the first base station to the fourth device; and The second device is configured to send the second UP address of the fourth device to the first base station.

12. A third device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the third device: Receive a request from the first base station or the first device for establishing a user plane (UP) connection for sensing between the first base station and the first device; as well as The request is sent to the second device.

13. The third device according to claim 12, wherein the third device is further configured to: Receive a third indication that the UP connection will be established; and Information about the first device is determined based on the third indication; and The information about the first device is sent to the second device.

14. The third device according to claim 12, wherein the third device is further configured to: Receive information about the first device or the first UP address of the first device from the first base station; and Send the information about the first device or the first UP address of the first device to the second device.

15. The third device according to claim 12, wherein the third device is further configured to: Receive from the first device a response to the request for establishing the UP connection, and the first UP address of the first device; and The first UP address of the first device and the response are sent to the second device and the first base station, respectively.

16. A first device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the first device: Receive the second message; as well as Based at least on the second message, the first user plane (UP) address of the first device and a request for establishing a sensing UP connection between the first base station and the first device are sent to the first base station or the second device.

17. The first device of claim 16, wherein the first device is configured to receive the second message by: Receive a sensing registration request message from the first base station.

18. The first device of claim 16, wherein the first device is configured to receive the second message by: Receive perception tasks from consumers of perception services.

19. The first apparatus according to claim 17, wherein: The second message includes a fourth indication, which specifies that: the first base station supports the transmission of sensing measurement data via the UP connection; and The first device is caused to send the request for establishing the UP connection based on the fourth instruction.

20. The first device of claim 16, wherein the first device is configured to receive the second message by: During the handover, receive one of the following from the second base station: The identifier of the first base station associated with the identifier of the sensing task; or The identifier of the UE associated with the handover.

Images