System, method, and device for sensing in wireless communication network

Abstract

To provide a method and device for coordinating sensing in a wireless communication system.SOLUTION: A method applicable to sensing architecture includes a step of communicating, by a first sensing coordinator (SAF of an NG-RAN node 1304) in a radio access network, a first signal (SSR) with a second sensing coordinator (SensMF 1308) via an interface link via an AMF 1306. The first sensing coordinator includes a sensing protocol layer, and the step of communicating the first signal includes a step of communicating the first signal via the interface link using a sensing protocol.SELECTED DRAWING: Figure 13

Description

[Technical field]

[0001] The present application relates generally to communications, and more particularly to sensing in wireless communications networks. [Background technology]

[0002] In a wireless communication system that includes a core network and one or more radio access networks, the coordination of positioning related sensing is typically based in the core network, and all signaling to request positioning and provide positioning information is routed through the core network. This type of architecture is positioning specific and can significantly limit the availability of positioning capabilities for entities outside the core network. Summary of the Invention

[0003] In general, sensing operations may include more features than positioning. Although positioning can be one of the sensing features for the sensing services disclosed herein, the present disclosure is by no means limited to positioning. Sensing operations may provide real-time or non-real-time sensing information for enhanced communications within the wireless network, as well as independent sensing services, to networks other than the wireless network operator or other network operators.

[0004] The embodiments of the present disclosure provide a sensing architecture, method, and apparatus for coordinating sensing in a wireless communication system. The coordination of sensing may include one or more devices or elements located in a radio access network, or one or more devices or elements located in a core network, or both one or more devices or elements located in a radio access network and one or more devices or elements located in a core network.

[0005] Positioning is a very specific feature related to determining the physical location of a UE within a wireless network (e.g., within a cell). Positioning can be by the UE itself and / or by a network device such as a base station, and can include measuring reference signals and analyzing measured information such as signal delays between the UE and the network device. In real wireless communication and optimized control, the positioning of the UE is just one measurement element among multiple possible measurement metrics. For example, the network can use information about the UE's surroundings, such as channel conditions, surrounding environment, etc., for better communication scheduling and control. During the sensing operation, all relevant measurement information can be obtained for better communication.

[0006] According to one aspect of the disclosure, a method includes communicating, by a first sensing coordinator in a radio access network, a first signal with a second sensing coordinator over an interface link, the first sensing coordinator comprising a sensing protocol layer, and communicating the first signal includes communicating the first signal over the interface link using the sensing protocol.

[0007] An apparatus according to another aspect of the disclosure includes at least one processor and a non-transitory computer-readable storage medium coupled to the at least one processor and storing programming for execution by the at least one processor, the programming including instructions for communicating, by a first sensing coordinator in a radio access network, a first signal with a second sensing coordinator over an interface link, the first sensing coordinator comprising a sensing protocol layer, and communicating the first signal includes communicating the first signal over the interface link using the sensing protocol.

[0008] A computer program product according to another aspect includes a non-transitory computer-readable storage medium storing programming for execution by a processor. The programming includes instructions for communicating a first signal by a first sensing coordinator in a radio access network with a second sensing coordinator over an interface link. As with the other aspects mentioned above, the first sensing coordinator comprises a sensing protocol layer, and communicating the first signal includes communicating the first signal over the interface link using the sensing protocol.

[0009] The present disclosure also encompasses a method that includes communicating a first signal by a second sensing coordinator over an interface link with a first sensing coordinator in a radio access network, the second sensing coordinator comprising a sensing protocol layer, and communicating the first signal includes communicating the first signal over the interface link using the sensing protocol.

[0010] In an apparatus embodiment, the apparatus may include at least one processor and a non-transitory computer-readable storage medium coupled to the at least one processor and storing programming for execution by the at least one processor, the programming including instructions for communicating, by a second sensing coordinator, a first signal with a first sensing coordinator in a radio access network over an interface link, the second sensing coordinator comprising a sensing protocol layer, and communicating the first signal includes communicating the first signal over the interface link using the sensing protocol.

[0011] A computer program product according to another aspect includes a non-transitory computer-readable storage medium storing programming for execution by a processor, the programming including instructions for communicating, by a second sensing coordinator, a first signal with a first sensing coordinator in a radio access network over an interface link. Again, the second sensing coordinator includes a sensing protocol layer, and communicating the first signal includes communicating the first signal over the interface link using the sensing protocol.

[0012] According to yet another aspect of the disclosure, a method includes accessing, by an apparatus, an interface link via a wireless access network, and communicating, by the apparatus, a first signal with a sensing coordinator having a sensing protocol layer, where the communicating includes communicating the first signal via the interface link using the sensing protocol, where the first signal includes a sensing configuration or sensing data.

[0013] In another apparatus embodiment, where the apparatus includes at least one processor and a non-transitory computer-readable storage medium coupled to the at least one processor and storing programming for execution by the at least one processor, the programming may include instructions for accessing, by the apparatus, over a wireless access network, an interface link, and for communicating, by the apparatus, a first signal with a sensing coordinator having a sensing protocol layer, where communicating includes communicating the first signal over the interface link using the sensing protocol, the first signal including a sensing configuration or sensing data.

[0014] A computer program product according to another aspect includes a non-transitory computer-readable storage medium storing programming for execution by a processor, the programming including instructions for accessing, by the device, over a wireless access network, an interface link, and for communicating, by the device, a first signal with a sensing coordinator having a sensing protocol layer. The communicating includes communicating the first signal over the interface link using the sensing protocol. As with the other embodiments mentioned above, the first signal includes a sensing configuration or sensing data.

[0015] Other aspects and features of the embodiments of the present disclosure will become apparent to those of ordinary skill in the art upon review of the following description. [Brief description of the drawings]

[0016] For a more complete understanding of these embodiments, and potential advantages thereof, reference is now made to the following description, by way of example, taken in conjunction with the accompanying drawings, in which:

[0017] [Figure 1] FIG. 1 is a block diagram that illustrates a simplified schematic of a communication system. [Diagram 2] FIG. 2 is a block diagram illustrating another exemplary communication system. [Diagram 3] 1 is a block diagram illustrating exemplary electronic and network devices. [Figure 4] FIG. 2 is a block diagram illustrating units or modules within a device. [Diagram 5] FIG. 1 is a block diagram of a Long Term Evolution (LTE) / New Radio (NR) positioning architecture. [Figure 6A] 1 is a block diagram illustrating a sensing architecture according to an embodiment in which the sensing coordinator is located in the core network. [Figure 6B]FIG. 13 is a block diagram illustrating a sensing architecture according to another embodiment in which the sensing coordinator is located outside the core network and communicates with the RAN via the core network. [Figure 6C] FIG. 13 is a block diagram illustrating a sensing architecture according to a further embodiment in which the sensing coordinator is located outside the core network and communicates directly with the RAN. [Figure 7A] FIG. 6C is a block diagram illustrating a sensing architecture according to an embodiment similar to that of FIGS. 6A to 6C, but having a central unit (CU) / distributed unit (DU) RAN architecture. [Figure 7B] FIG. 6C is a block diagram illustrating a sensing architecture, similar to that of FIGS. 6A-6C, but according to an embodiment including a central unit (CU) / distributed unit (DU) RAN architecture. [Figure 7C] FIG. 6C is a block diagram illustrating a sensing architecture, similar to that of FIGS. 6A-6C, but according to an embodiment including a central unit (CU) / distributed unit (DU) RAN architecture. [Figure 8A] FIG. 8 is a block diagram illustrating a sensing architecture, similar to that of FIGS. 7A to 7C, but according to an embodiment having a CU control plane (CP) / user plane (UP) RAN architecture. [Figure 8B] FIG. 8 is a block diagram illustrating a sensing architecture similar to that of FIGS. 7A to 7C, but according to an embodiment including a CU control plane (CP) / user plane (UP) RAN architecture. [Figure 8C] FIG. 8 is a block diagram illustrating a sensing architecture similar to that of FIGS. 7A to 7C, but according to an embodiment including a CU control plane (CP) / user plane (UP) RAN architecture. [Figure 9A] FIG. 7 is a block diagram illustrating a sensing architecture similar to that of FIGS. 6A to 6C, but in accordance with an embodiment in which sensing coordination is centralized at the RAN. [Figure 9B]FIG. 7 is a block diagram illustrating a sensing architecture similar to that of FIGS. 6A to 6C, but in accordance with an embodiment in which sensing coordination is centralized at the RAN. [Figure 9C] FIG. 7 is a block diagram illustrating a sensing architecture similar to that of FIGS. 6A to 6C, but in accordance with an embodiment in which sensing coordination is centralized at the RAN. [Figure 10A] FIG. 8 is a block diagram illustrating a sensing architecture similar to that of FIGS. 7A to 7C, but in accordance with an embodiment in which sensing coordination is centralized at the RAN. [Figure 10B] FIG. 8 is a block diagram illustrating a sensing architecture similar to that of FIGS. 7A to 7C, but in accordance with an embodiment in which sensing coordination is centralized at the RAN. [Figure 10C] FIG. 8 is a block diagram illustrating a sensing architecture similar to that of FIGS. 7A to 7C, but in accordance with an embodiment in which sensing coordination is centralized at the RAN. [Figure 11A] FIG. 8C is a block diagram showing a sensing architecture similar to that of FIGS. 8A to 8C, but in accordance with an embodiment in which sensing coordination is centralized at the RAN. [Figure 11B] FIG. 8C is a block diagram showing a sensing architecture similar to that of FIGS. 8A to 8C, but in accordance with an embodiment in which sensing coordination is centralized at the RAN. [Figure 11C] FIG. 8C is a block diagram showing a sensing architecture similar to that of FIGS. 8A to 8C, but in accordance with an embodiment in which sensing coordination is centralized at the RAN. [Figure 12] FIG. 13 is a block diagram of a sensing architecture according to a further embodiment. [Figure 13] FIG. 13 is a signal flow diagram illustrating an example method that may be applicable to an architecture of the type shown in FIG. [Figure 14] FIG. 13 is a signal flow diagram illustrating another exemplary method that may be applicable to an architecture of the type shown in FIG. [Figure 15]FIG. 13 is a block diagram of a sensing architecture according to yet another embodiment. [Figure 16] FIG. 16 is a signal flow diagram illustrating an example method that may be applicable to an architecture of the type shown in FIG. [Figure 17] FIG. 13 is a block diagram of a sensing architecture according to a further embodiment. [Figure 18] FIG. 18 is a signal flow diagram illustrating an example method that may be applicable to an architecture of the type shown in FIG. 17. [Figure 19] FIG. 2 is a block diagram of a sensing architecture according to another embodiment. [Figure 20] FIG. 20 is a signal flow diagram illustrating an example method that may be applicable to an architecture of the type shown in FIG. 19. [Figure 21] FIG. 20 is a signal flow diagram illustrating another exemplary method that may be applicable to an architecture of the type shown in FIG. 19. [Figure 22] FIG. 2 is a block diagram illustrating an exemplary protocol stack, according to an embodiment. [Diagram 23] FIG. 2 is a block diagram illustrating an exemplary protocol stack, according to another embodiment. [Figure 24] FIG. 11 is a block diagram illustrating an exemplary protocol stack according to a further embodiment. [Diagram 25] FIG. 2 is a block diagram illustrating an example interface between a core network and a RAN. [Figure 26] FIG. 2 is a block diagram illustrating another example of a protocol stack, according to an embodiment. [Figure 27] FIG. 1 is a block diagram illustrating an example sensing application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] By way of example only, certain exemplary embodiments are now described in more detail below in conjunction with the figures.

[0019] The embodiments described herein provide sufficient information to implement the claimed subject matter and illustrate how such subject matter can be implemented. Upon reading the following description in light of the accompanying figures, one skilled in the art will understand the concepts of the claimed subject matter and recognize applications of these concepts not specifically addressed herein. It is understood that these concepts and applications are within the scope of this disclosure and the accompanying claims.

[0020] Referring to FIG. 1, a simplified schematic diagram of a communication system is presented as a non-limiting illustrative example. The communication system 100 includes a radio access network 120. The radio access network 120 may be a next generation (e.g., sixth generation (6G) or later) radio access network or a legacy (e.g., 5G, 4G, 3G, or 2G) radio access network. One or more communication electric devices (EDs) 110a-120j (collectively referred to as 110) may be interconnected with each other and / or may be connected to one or more network nodes (170a, 170b, collectively referred to as 170) in the radio access network 120. A core network 130 may be part of the communication system and may or may not depend on the radio access technology used in the communication system 100. The communication system 100 also includes a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0021] FIG. 2 illustrates an exemplary communication system 100. In general, the communication system 100 enables multiple wireless or wired elements to communicate data and other content. The purpose of the communication system 100 may be to provide content, such as voice, data, video, and / or text, via broadcast, multicast, unicast, etc. The communication system 100 may operate by sharing resources, such as carrier spectrum bandwidth, among its components. The communication system 100 may include terrestrial and / or non-terrestrial communication systems. The communication system 100 may provide a wide range of communication services and applications, such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc. The communication system 100 may provide a high degree of availability and robustness through the joint operation of the terrestrial and non-terrestrial communication systems. For example, the integration of the non-terrestrial communication systems (or components thereof) into the terrestrial communication system may provide what may be considered a heterogeneous network including multiple layers. Compared with traditional communication networks, heterogeneous networks can achieve better overall performance through efficient multi-link cooperation, more flexible functionality sharing, and faster physical layer link switching between terrestrial and non-terrestrial networks.

[0022] The terrestrial and non-terrestrial communication systems may also be considered as subsystems of the communication system. In the illustrated example, the communication system 100 includes electronic devices (EDs) 110a-110d (collectively referred to as EDs 110), radio access networks (RANs) 120a-120b, a non-terrestrial communication network 120c, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. The RANs 120a-120b include respective base stations (BSs) 170a-170b, which may be collectively referred to as terrestrial transmission / reception points (T-TRPs) 170a-170b. The non-terrestrial communication network 120c includes access nodes 120c, which may be collectively referred to as non-terrestrial transmission / reception points (NT-TRPs) 172.

[0023] Any ED 110 may alternatively or additionally be configured to interface, access, or communicate with any other T-TRP 170a-170b and NT-TRP 172, the Internet 150, the core network 130, the PSTN 140, other networks 160, or any combination of the foregoing. In some examples, ED 110a may communicate uplink and / or downlink transmission signals with T-TRP 170a over interface 190a. In some examples, EDs 110a, 110b, and 110d may also communicate directly with each other over one or more sidelink air interfaces 190b. In some examples, ED 110d may communicate uplink and / or downlink transmission signals with NT-TRP 172 over interface 190c.

[0024] The air interfaces 190a and 190b may use similar communication technologies, such as any suitable radio access technology. For example, the communication system 100 may implement one or more channel access methods in the air interfaces 190a and 190b, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single carrier FDMA (SC-FDMA). The air interfaces 190a and 190b may also utilize other high-dimensional signal spaces, which may include combinations of orthogonal and / or non-orthogonal dimensions.

[0025] The air interface 190c may enable communication between the EDs 110d and one or more NT-TRPs 172 via a wireless link or simply a link. In some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs and one or more NT-TRPs for multicast transmission.

[0026] The RANs 120a and 120b are in communication with the core network 130 to provide various services, such as voice, data, and other services, to the EDs 110a, 110b, and 110c. The RANs 120a and 120b and / or the core network 130 may be in direct or indirect communication with one or more other RANs (not shown), which may or may not be directly served by the core network 130 and which may or may not employ the same radio access technology as the RANs 120a and / or 120b. The core network 130 may serve as a gateway access between (i) the RANs 120a and 120b, or the EDs 110a and 110b and / or 110c, and (ii) other networks (such as the PSTN 140, the Internet 150, and other networks 160). In addition, some or all of the EDs 110a, 110b, 110c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and / or protocols. Instead of (or in addition to) wireless communications, the EDs 110a, 110b, and 110c may communicate with a service provider or switch (not shown) and the Internet 150 via wired communication channels. The PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a network of computers and subnets (intranets) or both and may incorporate protocols such as the Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and the like. The EDs 110a, 110b, and 110c may be multi-mode devices capable of operating with multiple wireless access technologies and may incorporate multiple transceivers necessary to support such technologies.

[0027] 3 shows another example of ED 110 and network devices, including base stations 170a, 170b and NT-TRP 172 (at 170). ED 110 is used to connect people, objects, machines, etc. ED 110 can be widely used in various scenarios, such as cellular communication, device-to-device communication (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine communication (M2M), machine-type communication (MTC), Internet of Things (IOT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, and mobility.

[0028] Each ED 110 may be any suitable end-user device for wireless operation, and may include (or may be referred to as) a device such as a user equipment / device (UE), a wireless transmit / receive unit (WTRU), a mobile station, a fixed or mobile subscriber unit, a cellular phone, a station (STA), a machine type communication (MTC) device, a personal digital assistant (PDA), a smartphone, a laptop, a computer, a tablet, a wireless sensor, a consumer electronics device, a smartbook, a vehicle, an automobile, a truck, a bus, a train, or an IoT device, an industrial device, or an apparatus (e.g., a communication module, a modem, or a chip) within the aforementioned devices, among other possibilities. The next-generation ED 110 may also be referred to using other terms. The base stations 170a, 170b are T-TRPs, and are hereinafter referred to as T-TRP 170. Also, the NT-TRP shown in FIG. 3 is hereinafter referred to as NT-TRP 172. Each ED 110 connected to the T-TRP 170 and / or NT-TRP 172 may be configured to receive and transmit the signal of connection availability and need. One or more of Depending on the configuration, it may be dynamically or semi-statically turned on (i.e., established, activated, or enabled), turned off (i.e., released, deactivated, or disabled), and / or configured.

[0029] The ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown. One, some, or all of the antennas may alternatively be a panel. The transmitter 201 and the receiver 203 may be integrated, for example, as a transceiver. The transceiver is configured to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver is also configured to demodulate data or other content received by at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received wirelessly or wired. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals.

[0030] The ED 110 includes at least one memory 208. The memory 208 stores instructions and data used, generated, or collected by the ED 110. For example, the memory 208 can store software instructions or modules configured to implement some or all of the functionality and / or embodiments described herein and executed by the processing unit(s) 210. Each memory 208 includes any suitable volatile and / or non-volatile storage and retrieval device. Any suitable type of memory may be used, such as random access memory (RAM), read only memory (ROM), hard disk (disk), optical disk (disc), subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, on-processor cache, etc.

[0031] The ED 110 may further include one or more input / output devices (not shown) or interfaces (such as a wired interface to the Internet 150 of FIG. 1). The input / output devices enable interaction with a user or other devices in a network. Each input / output device includes any suitable structure that includes a network interface communication, such as a speaker, microphone, keypad, keyboard, display, or touch screen for providing information to or receiving information from a user.

[0032] The ED 110 further includes a processor 210 for performing operations including those related to preparing a transmission signal for uplink transmission to the NT-TRP 172 and / or the T-TRP 170, those related to processing a downlink transmission signal received from the NT-TRP 172 and / or the T-TRP 170, and those related to processing a sidelink transmission between another ED 110. Processing operations related to preparing a transmission signal for uplink transmission may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing a downlink transmission signal may include operations such as receive beamforming, demodulation, decoding received symbols, etc. In some embodiments, the downlink transmission signal may be received by the receiver 203, possibly using receive beamforming, and the processor 210 may extract signaling from the downlink transmission signal (e.g., by detecting and / or decoding the signaling). An example of signaling may be a reference signal transmitted by the NT-TRP 172 and / or the T-TRP 170. In some embodiments, the processor 210 implements transmit beamforming and / or receive beamforming based on an indication of beam direction, e.g., beam angle information (BAI), received from the T-TRP 170. In some embodiments, the processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding and obtaining system information, etc. In some embodiments, the processor 210 may perform channel estimation, e.g., using reference signals received from the NT-TRP 172 and / or the T-TRP 170.

[0033] Although not shown, the processor 210 may form part of the transmitter 201 and / or the receiver 203. Although not shown, the memory 208 may form part of the processor 210.

[0034] The processor 210 and the processing components of the transmitter 201 and receiver 203 may each be implemented by the same or different processor or processors configured to execute instructions stored in a memory (e.g., in memory 208). Alternatively, some or all of the processor 210 and the processing components of the transmitter 201 and receiver 203 may be implemented using special purpose circuitry, such as a programmed field programmable gate array (FPGA), a graphics processing unit (GPU), or an application specific integrated circuit (ASIC).

[0035] The T-TRP 170 may be known by other names in some implementations, such as a base station, base transceiver station (BTS), radio base station, network node, network device, network side device, transceiver node, Node B, evolved Node B (eNodeB or eNB), home eNodeB, next generation Node B (gNB), transmission point (TP), site controller, access point (AP), or wireless router, relay station, remote radio head, terrestrial node, terrestrial network device, or terrestrial base station, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc., among other possibilities. The T-TRP 170 may be a macro BS, pico BS, relay node, donor node, etc., or combinations thereof. The T-TRP 170 may be a As mentioned above It may also refer to a device or an apparatus within such a device (eg, a communication module, modem, or chip).

[0036] In some embodiments, parts of the T-TRP 170 may be distributed. For example, some of the modules of the T-TRP 170 may be located away from the equipment housing the antenna of the T-TRP 170 and may be coupled to the equipment housing the antenna through a communication link (not shown), such as a Common Public Radio Interface (CPRI), sometimes known as a fronthaul. Thus, in some embodiments, the term T-TRP 170 may refer to a network-side module that performs processing operations such as determining the location of the ED 110, resource allocation (scheduling), message generation, and encoding / decoding, and is not necessarily part of the equipment housing the antenna of the T-TRP 170. The modules may also be coupled to other T-TRPs. In some embodiments, the T-TRP 170 may actually be multiple T-TRPs operating together to serve the ED 110, for example, by coordinated multipoint transmission.

[0037] The T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown. One, some, or all of the antennas may alternatively be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. The T-TRP 170 further includes a processor 260 for performing operations including those related to preparing a transmit signal for downlink transmission to the ED 110, processing an uplink transmit signal received from the ED 110, preparing a transmit signal for backhaul transmission to the NT-TRP 172, and processing a transmit signal received through the backhaul from the NT-TRP 172. Processing operations related to preparing a transmit signal for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing a transmission signal received on the uplink or through the backhaul may include operations such as receive beamforming, and demodulating and decoding received symbols. The processor 260 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating synchronization signal block (SSB) content, generating system information, etc. In some embodiments, the processor 260 also generates an indication of a beam direction, e.g., BAI, that may be scheduled for transmission by the scheduler 253. The processor 260 performs other network side processing operations described herein, such as determining a location of the ED 110, determining where the NT-TRP 172 should be deployed, etc. In some embodiments, the processor 260 may generate signaling, for example, to configure one or more parameters of the ED 110 and / or one or more parameters of the NT-TRP 172. Any signaling generated by the processor 260 is transmitted by the transmitter 252.It should be noted that "signaling" as used herein may alternatively be referred to as control signaling. Dynamic signaling may be transmitted on a control channel, e.g., the Physical Downlink Control Channel (PDCCH), and static or semi-static higher layer signaling may be included in packets transmitted on a data channel, e.g., the Physical Downlink Shared Channel (PDSCH).

[0038] The scheduler 253 may be coupled to the processor 260. The scheduler 253 may be included within the T-TRP 170 or may be operated separately from the T-TRP 170 and may schedule uplink, downlink, and / or backhaul transmissions, including issuing scheduling grants and / or configuring scheduling-free ("configured grants") resources. The T-TRP 170 further includes a memory 258 for storing information and data. The memory 258 stores instructions and data used, generated, or collected by the T-TRP 170. For example, the memory 258 may also store software instructions or modules configured to implement some or all of the functionality and / or embodiments described herein and executed by the processor 260.

[0039] Although not shown, the processor 260 may form part of the transmitter 252 and / or the receiver 254. Also, although not shown, the processor 260 may implement the scheduler 253. Although not shown, the memory 258 may form part of the processor 260.

[0040] The processor 260, the scheduler 253, and the processing components of the transmitter 252 and the receiver 254 may each be implemented by the same or different processor or processors configured to execute instructions stored in a memory, such as in the memory 258. Alternatively, some or all of the processing components of the processor 260, the scheduler 253, and the transmitter 252 and the receiver 254 may be implemented using special purpose circuitry, such as an FPGA, a GPU, or an ASIC.

[0041] Although the NT-TRP 172 is illustrated as a drone only by way of example, the NT-TRP 172 may be implemented in any suitable non-terrestrial form. The NT-TRP 172 may also be known by other names, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station, in some implementations. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is illustrated. One, some, or all of the antennas may alternatively be panels. The transmitter 272 and the receiver 274 may be integrated as a transceiver. The NT-TRP 172 further includes a processor 276 for performing operations including those related to preparing a transmit signal for downlink transmission to the ED 110, processing an uplink transmit signal received from the ED 110, preparing a transmit signal for backhaul transmission to the T-TRP 170, and processing a transmit signal received through the backhaul from the T-TRP 170. Processing operations related to preparing a transmission signal for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing a transmission signal received on the uplink or through the backhaul may include operations such as receive beamforming, and demodulating and decoding received symbols. In some embodiments, the processor 276 implements transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from the T-TRP 170. In some embodiments, the processor 276 may generate signaling, for example, to configure one or more parameters of the ED 110. In some embodiments, the NT-TRP 172 implements physical layer processing but does not implement higher layer functions, such as functions at the medium access control (MAC) or radio link control (RLC) layers. This is merely an example, so more generally, the NT-TRP 172 may implement higher layer functions in addition to physical layer processing.

[0042] The NT-TRP 172 further includes a memory 278 for storing information and data. Although not shown, the processor 276 may form part of the transmitter 272 and / or the receiver 274. Although not shown, the memory 278 may form part of the processor 276.

[0043] The processor 276 and the processing components of the transmitter 272 and the receiver 274 may each be implemented by one or more of the same or different processors configured to execute instructions stored in a memory, e.g., in the memory 278. Alternatively, some or all of the processing components of the processor 276 and the transmitter 272 and the receiver 274 may be implemented using dedicated circuitry, such as a programmed FPGA, GPU, or ASIC. In some embodiments, the NT-TRP 172 may actually be multiple NT-TRPs operating together, e.g., to serve the ED 110 by coordinated multi-point transmission.

[0044] T-TRP170, NT-TRP172, and / or ED110 may include other components, which have been omitted for clarity.

[0045] One or more steps of the embodiment method provided herein may be implemented by a corresponding unit or module according to FIG. 4. FIG. 4 illustrates units or modules in a device, such as in ED110, T-TRP170, or NT-TRP172. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be implemented by an artificial intelligence (AI) or machine learning (ML) module. Each unit or module may be implemented using hardware, one or more components or devices that execute software, or a combination thereof. For example, one or more of the units or modules may be an integrated circuit, such as a programmed FPGA, GPU, or ASIC. It should be understood that when modules are implemented using software, for example, for execution by a processor, they may be incorporated by the processor in single or multiple instances, individually or together, for processing, in whole or in part, as necessary, and the modules themselves may include instructions for further deployment and instantiation.

[0046] Additional details regarding ED110, T-TRP170, and NT-TRP172 are known to those of skill in the art, and therefore these details are omitted here.

[0047] Moving forward into future wireless networks, the number of new devices with diverse functionalities may also increase exponentially. Also, many new applications and use cases beyond 5G may emerge with more diverse service quality requirements. These bring new Key Performance Indicators (KPIs) for future wireless networks (e.g., 6G networks) that may be extremely challenging, so sensing technologies and AI technologies, especially ML (deep learning) technologies, have been introduced into telecommunications to improve system performance and efficiency.

[0048] AI / ML technology has been applied to communications including AI / ML communications at the physical layer and AI / ML communications at the medium access control (MAC) layer. At the physical layer, AI / ML communications can be useful to optimize component design and improve algorithm performance, such as AI / ML in channel coding, channel modeling, channel estimation, channel decoding, modulation, demodulation, MIMO, waveforms, multiple access, PHY element parameter optimization and update, beamforming and tracking, and sensing and positioning. At the MAC layer, AI / ML communications can utilize AI / ML capabilities including learning, prediction, and make decisions to solve complex optimization problems with better strategies and optimal solutions, for example, to optimize MAC functionality, such as intelligent TRP management, intelligent beam management, intelligent channel resource allocation, intelligent power control, intelligent spectrum utilization, intelligent MCS, intelligent hybrid automatic repeat request (HARQ) strategies, intelligent transmit / receive (Tx / Rx) mode adaptation, etc.

[0049] AI / ML architectures typically include multiple nodes that can be organized in two modes: centralized and distributed, both of which can be deployed in access networks, core networks, or edge computer systems or third-party networks. Centralized training and computer architectures are limited by huge communication overhead and strict user data privacy. Distributed training and computer architectures include several frameworks, e.g., distributed machine learning and federated learning. AI / ML architectures comprise intelligent controllers that can be implemented as single or multi-agents based on joint or individual optimization. New protocols and signaling mechanisms are required to allow the corresponding interface links to be personalized with customized parameters to meet specific requirements while minimizing signaling overhead and maximizing the spectrum efficiency of the entire system through personalized AI techniques.

[0050] Additional terrestrial and non-terrestrial networks can enable a range of new services and applications, such as earth monitoring, remote sensing, passive sensing and positioning, navigation, and tracking, autonomous delivery and mobility. Terrestrial and non-terrestrial network-based sensing can also provide intelligent context-aware networks to enhance the UE experience. For example, terrestrial and non-terrestrial network-based sensing can include opportunities for localization and sensing applications based on new feature sets and service capabilities. Applications such as THz imaging and spectroscopy have the potential to provide continuous real-time physiological information with dynamic, non-invasive, non-contact measurements for future digital health technologies. Simultaneous localization and mapping (SLAM) methods will enable advanced cross-reality (XR) applications as well as enhance the navigation of autonomous objects such as vehicles and drones. Additionally, in terrestrial and non-terrestrial networks, measured channel data, as well as sensing and positioning data, can be acquired with large bandwidth, new spectrum, dense networks, and more line-of-sight (LOS) links. Based on these data, a radio environment map can be drawn using AI / ML methods, and the channel information is linked to its corresponding positioning or environmental information to provide an enhanced physical layer design based on this map.

[0051] Sensing coordinators are nodes in the network that can assist in sensing operations. These nodes may be standalone nodes dedicated to sensing operations alone, or other nodes (e.g., TRP170, ED110, or core network nodes) that perform sensing operations in parallel with communication transmissions. New protocols and signaling mechanisms are needed to allow the corresponding interface links to be implemented with customized parameters to meet specific requirements while minimizing signaling overhead and maximizing the spectral efficiency of the overall system.

[0052] AI / ML and sensing methods are data intensive. To include AI / ML and sensing in wireless communication, more and more data needs to be collected, stored, and exchanged. The characteristics of wireless data are expanding to a very large extent in multi-dimensions, for example, from sub-6 GHz, millimeter to terahertz carrier frequencies, from space, outdoor to indoor scenarios, from text, voice to video. These data collection, processing, and usage operations are performed in a unified framework or in separate frameworks.

[0053] Regarding positioning, FIG. 5 is a block diagram of the LTE / NR positioning architecture.

[0054] In the positioning architecture 500, a core network is indicated at 510, a data network (NW) that may be external to the core network is indicated at 530, and a NG-RAN (Next Generation Radio Access Network) is indicated at 540. The NG-RAN 540 includes a gNB 550 and an Ng-eNB 560, and the UEs to which the NG-RAN provides access to the core network 510 are indicated at 570.

[0055] The core network 510 is shown as a 5th Generation Core Service-Based Architecture (5GC SBA) and includes various functions or elements coupled by a Service-Based Interface (SBI) bus 528. These functions or elements include a Network Slice Selection Function (NSSF) 512, a Policy Control Function (PCF) 514, a Network Exposure Function (NEF) 516, a Location Management Function (LMF) 518, a 5G Location Services (LCS) Entity 520, a Session Management Function (SMF) 522, an Access and Mobility Management Function (AMF) 524, and a User Plane Function (UPF) 526. The AMF 524 and the UPF 526 communicate with other elements outside the core network 510 via interfaces shown as N2, N3, and N6 interfaces.

[0056] Both gNB 550 and Ng-eNB 560 have a CU (Centralized Unit) / DU (Distributed Unit) / RU (or RRU, Remote Radio Unit) architecture, each including one CU 552, CU 562 and two RUs 557 / 559, RU 567 / 569. The gNB 550 includes two DUs 554, DU 556, and the Ng-eNB 560 includes one DU 564. The interfaces through which the gNB 550 and Ng-eNB 560 communicate with each other and with the UE 570 are shown as Xn and Uu interfaces, respectively.

[0057] Those skilled in the art will be familiar with the positioning architecture 500, the elements illustrated in Figure 5, and their operation. This disclosure relates primarily to sensing, and therefore the LMF 518, the LCS entity 520, the AMF 524, and the UPF 526, and their operations related to positioning may be relevant.

[0058] In location services, the 5G LCS entity 520 may request positioning services from the wireless network via the AMF 524, which may then send the request to the LMF 518, and the relevant RAN nodes and UEs may be determined for the positioning services, and the accompanying positioning configuration is initiated by the LMF 518. Location services are provided to clients and give information. These services can be divided into: value-added services (such as route planning information), legal and statutory interception services (such as those that can be used as evidence in legal proceedings), and emergency services (which provide location information to organizations such as police, fire, and ambulance services). For example, to estimate the location of the UE, the network may configure the UE to transmit an uplink reference signal, and multiple base stations may measure the received signal in terms of arrival direction and delay, so that the UE location can be estimated by the network. In wireless networks, apart from the location of the UE itself, more information to support better communication is also required, which may include information about the UE's surroundings, such as channel conditions, surrounding environment, etc., which can be achieved by sensing operations.

[0059] SUMMARY OF THE DISCLOSURE Embodiments of the present disclosure relate to sensing for future wireless communication networks, such as sixth generation networks. Either or both integrated sensing and communication and standalone sensing may be supported. In this disclosure, features disclosed in the context of any embodiment are not necessarily limited to that particular embodiment, but may also or instead be applied to other embodiments.

[0060] Future networks such as 6G networks may include high-precision positioning, mapping and reconstruction, and sensing the environment with gesture / activity recognition, and thus sensing will become an emerging 6G service with various activities and operations by obtaining information about the surrounding environment. 6G networks include terminals, devices, and network infrastructure leading to the following capabilities: The larger the bandwidth, the higher the spectrum, Advanced antenna designs using very large arrays and metasurfaces; Large-scale collaboration between base stations and UEs; Advanced technology for interference cancellation, Integrated advanced signal processing and artificial intelligence (AI).

[0061] Therefore, future networks may use or require new metrics (such as sensing accuracy and sensing resolution) to serve as new KPIs proposed based on different application scenarios. For example, latency may be tight, around 1 cm to 10 cm, and sensing accuracy may be up to 1 mm resolution. Furthermore, since 6G networks may include numerous use cases, such as unmanned aerial vehicles (UAVs), vehicles, and IoT devices to build maps of the environment and virtual environments in cyberspace, 6G networks may use or require new sensing systems and frameworks to provide efficient signal design and coordinate resource allocation in time, frequency, and spatial domains without compromising spectral efficiency and sensing performance. For example, the new sensing system may be an integrated sensing and communications (ISAC) that provides at least one of the following: Sensing-aided communications: To enable medium-aware communications with more deterministic and predictable propagation channels. Sensing-aided communications can provide environmental knowledge acquired by sensing to improve communications, such as environmental knowledge used to optimize beamforming to the UE (medium-aware beamforming), environmental knowledge used to exploit all potential degrees of freedom (DoF) in the propagation channel (medium-aware channel rank boosting), and medium awareness to reduce or mitigate UE-to-UE interference. Sensing benefits to communications can include, for example, improved throughput spectrum utilization and interference mitigation. Sensing-enabled communication: Could also be called backscatter communication, as it offers advantages in scenarios where data is collected by devices with limited processing power (most IoT devices in future systems). An illustrative example is media-based communication, where the communication medium is intentionally changed to convey information. Communication-Aided Sensing: To achieve more efficient and smart sensing by connecting sensing nodes. In this example, the sensing network connects users to achieve on-demand sensing. For example, sensing can be performed based on the request of another node or delegated to another node to enable cooperative sensing where multiple sensing nodes acquire environmental information. All these advanced features require a system design to perform communication between sensing nodes over DL, UL, and SL channels with minimum overhead and maximum sensing efficiency. Sensing-Aided Positioning: Also known as positioning, this involves locating the UE by transmitting or receiving signals to and from the UE. The main potential benefits are a simple operation to obtain precise knowledge of the UE's location, and the ability to obtain many types of information including those that are compromised by multipath, imperfect time / frequency synchronization, limited user sampling / processing capabilities, and the limited dynamic range of the UE.

[0062] Emerging sensing systems and frameworks can be categorized into radio frequency (RF) sensing and non-RF sensing. For example, RF sensing includes learning the environment by transmitting RF signals and receiving and processing reflected signals. Examples of non-RF sensing include utilizing images and videos acquired (e.g., via a camera) from the surrounding environment.

[0063] Sensing is the feature of measuring environmental information around a device associated with a network, which may include, for example, any of positioning, nearby objects, traffic, temperature, channel, etc. Sensing measurements are performed by sensing nodes, which may be nodes dedicated to sensing or communication nodes with sensing capabilities. Sensing nodes may include, for example, any of radar stations, sensing devices, UEs, base stations, mobile access nodes such as drones, UAVs, etc.

[0064] To allow sensing operations to occur, sensing activities are managed and controlled by a sensing control device or function within the network. Two management and control functions for sensing are disclosed herein, which can support integrated sensing and communication, and standalone sensing services.

[0065] These two new functions for sensing include a first function referred to herein as a Sensing Management Function (SensMF) and a Sensing Agent Function (SAF). The SensMF may be implemented in a core network or RAN, such as in a network device in the core network or RAN, and the SAF may be implemented in the RAN where sensing is to be performed. More, less, or different functions may be used in implementing the features disclosed herein, and thus the SensMF and SAF are illustrative examples.

[0066] The SensMF may include various sensing-related features or functions, including, for example, any one or more of the following: Managing and coordinating one or more RAN nodes and / or one or more UEs for sensing activities; Communicating by AMF or otherwise for sensing procedures within the RAN, potentially including any one or more of the following: RAN configuration procedures for sensing, transfer of sensing related information such as sensing measurement data, processed sensing measurement data, and / or sensing measurement data reports; communicating, via UPF or otherwise, for sensing procedures within the RAN, potentially including transfer of sensing related information such as any one or more of sensing measurement data, processed sensing measurement data, and sensing measurement data reports; Processing the sensed measurement data and / or otherwise acting on the sensed measurement data, such as generating a sensed measurement data report.

[0067] The SAF may likewise include various sensing-related features or functions, including, for example, any one or more of the following: Splitting the sensing control plane and the sensing user plane (SAF-CP and SAF-UP), storing or otherwise maintaining the local measurement data and / or other local sensing information; Communicating the sensing measurement data to SensMF; Processing the sensing measurement data; receiving sensing analysis reports from the SensMF for communication control and / or other purposes within the RAN; Managing, coordinating, or otherwise assisting in the overall sensing and / or control process; Interfacing with an AI module or function.

[0068] The SAF may be located or deployed in a sensing node, such as a dedicated device or a base station, and may control the sensing node or a group of sensing nodes. The sensing node may send sensing results to the SAF node, for example, via a backhaul, Uu link, or side link SL, or may send the sensing results directly to the SensMF.

[0069] In summary, a basic sensing operation may involve at least one or more sensing nodes, such as UEs and / or TRPs, to physically perform a sensing activity or procedure, and sensing management and control functions, such as SensMF and SAF, may help organize, manage, configure, and control the entire sensing activity.

[0070] In a RAN including at least one RAN node, for example, the (or each) RAN node may be a base station, a TRP, a drone, a UAV, a satellite station, etc. To enable sensing in the RAN, one or more RAN nodes may include an SAF, but not necessarily all RAN nodes need to include an SAF. One SAF in one RAN node may manage, control, and configure one or more other RAN nodes and / or other electrical devices for sensing. Electrical devices such as UEs and / or RAN nodes having sensing capabilities may be managed, controlled, and / or configured to, for example, sense setup and measurements. In general, the sensing coordinator may be implemented in a network device in a radio access network and may be configured to control one or more other network devices in the radio access network.

[0071] In this disclosure, a sensing coordinator may refer to either a SensMF, a SAF, a sensing device or node, or other device in which a SensMF, a SAF, sensing, or sensing-related features or functions are implemented.

[0072] Sensing may encompass positioning, although the present disclosure is not limited to a particular type of sensing. For example, sensing may include sensing any of a variety of parameters or characteristics. Illustrative examples include position parameters, object size, one or more object dimensions including three-dimensional dimensions, one or more mobility parameters such as either or both of speed and direction, temperature, health care information, and material type such as wood, brick, metal, etc. Any one or more of these parameters or characteristics, or others, may be sensed.

[0073] FIG. 6A is a block diagram illustrating a sensing architecture according to an embodiment in which the sensing coordinator is located in the core network. In the example architecture 600, a third party network 602 interfaces with a core network 606 via a convergence element 604. The core network 606 includes a sensing coordinator, shown as SensMF 608 in FIG. 6A by way of example. The core network 606 connects to a RAN 612 via an interface link and an interface shown at 610. The RAN 612 also includes a sensing coordinator, shown as SAF 614 in FIG. 6A by way of example. The RAN is generally indicated at 612, and the sensing coordinator within the RAN is also generally indicated as SAF 614 to represent any type of RAN node that includes a sensing coordinator.

[0074] The third party network 602 represents any of various types of networks that may interface or interact directly with the core network or the sensing management function, where the third party network 602 may request sensing services through the core network or directly from the SensMF 608. The Internet is an example of a third party network 602, other examples of third party networks include the automation and autonomous driving industry, power monitoring networks, other fixed networks, and the like.

[0075] The convergence element 604 may be implemented in any of a variety of ways to provide a controlled and unified core network interface with other networks (e.g., wired networks). For example, although the convergence element 604 is shown separately in FIG. 6A, one or more network devices in the core network 606 and one or more network devices in the third party network 602 may implement respective modules or functions to support interfaces between the core network and third party networks outside the core network.

[0076] The core network 606 network may be or include, for example, an SBA or other core network. The SensMF 608 in the core network 606 may be a core network function in an SBA in some embodiments, as disclosed by way of example elsewhere herein with reference to FIG.

[0077] The SensMF 608 in the core network 606 may connect to the RAN 612, including the SAF 614, via a backhaul for its control plane and user plane. Thus, a backhaul connection or link is an example of an interface link between a sensing coordinator, such as the SensMF 608, and the SAF 614. The backhaul link, or other interface link, can be wired and / or wireless. In the case of a wireless link, an air interface protocol is used. Examples of air interface links include LTE / NR Uu links, sidelinks, new radio vehicle-to-anything (NR v2x), long-term evolution machine type communications (LTE-M), power class 5 (PC5), Institute of Electrical and Electronics Engineers (IEEE) 802.15.4, or 802.11 air interface links, and air interfaces with new protocols for sensing. Other examples are also presented elsewhere herein.

[0078] Although the RAN 612 is shown as a single block in FIG. 6A, it may include one or more network devices or RAN nodes, such as base stations. The network devices in the RAN may be terrestrial nodes or mobile nodes. Examples of mobile nodes include integrated access backhaul (IAB) nodes, drone-based nodes, unmanned aerial vehicle (UAV)-based nodes, and satellite-based nodes, among others. The SAF 614 may be implemented in a network device in the RAN, and potentially multiple network devices may include an SAF. For example, an SAF in one network device or RAN node may be capable of controlling multiple network devices or RAN nodes.

[0079] Other features disclosed herein, such as those disclosed with reference to Figures 2 to 5, may also or alternatively be applied to the components shown in Figure 6A.

[0080] Further variations from the particular example architecture shown in Figure 6A are also possible. For example, the SensMF 608 external to the RAN 612 may be connected to multiple SAFs, such as 614, which may be implemented in multiple RAN nodes or multiple RANs within the RAN 612. Thus, one core network may interface with multiple RANs, in other words, one or more RANs, such as 612, may provide access to the core network.

[0081] In some examples above, the sensing coordinators SensMF 608 and SAF 614 are described as being implemented as a core network service and within a network device, respectively, but it should be understood that sensing can be configured to be operable as a standalone feature or service, or can be operatively combined with communication operations within a communication network or system.

[0082] 6B is a block diagram illustrating a sensing architecture 620 according to another embodiment, in which a sensing coordinator in the form of a SensMF 628 is placed outside the core network 626 and communicates with the RAN 632 via the core network, and another sensing coordinator in the form of a SAF 634. The SensMF 628 is outside the core network 626 and open to the third party network 622, but in some embodiments connects with the RAN 632, including the SAF 634, via a backhaul for its control plane and user plane. The SensMF 628 may be placed in an edge cloud, such as, for example, a MEC, to obtain powerful computational capabilities. The exemplary sensing architecture 620 also includes an interface 630 and a convergence element 624.

[0083] Most of the example architecture 620 and its components may be substantially similar or the same as the similarly labeled components in FIG. 6A. However, in the example architecture 620 shown in FIG. 6B, the SensMF 628 is external to the core network 626. This may affect how the SensMF 628 interacts with the third party network 622 and the core network 626, and therefore the third party network and the core network are shown with different reference numbers in FIG. 6B than in FIG. 6A. To the extent that this may affect how other components interact with each other, the other components are also shown with different reference numbers in FIG. 6B than in FIG. 6A. One important difference from FIG. 6A is that FIG. 6B introduces a new interface between the SensMF 628 and the core network 626. For example, the new interface may be an application programming interface (API) of the type used for software functionality interfaces, or a newly designed interface for sensing through the core network 626 to the RAN 632, including the SAF 634. It is expected that the other components may be the same as the similarly labeled components in FIG. 6A.

[0084] 6C is a block diagram illustrating a sensing architecture 640 according to a further embodiment, in which a sensing coordinator, illustrated as an example SensMF 648, is placed outside the core network 646 and communicates directly with the RAN 652 via an interface link and an interface 650b. For example, the SensMF 648 may directly connect with the RAN 652, including the SAF 654, via a backhaul for its control plane and user plane. The SensMF 648 may be placed in an edge cloud, such as a MEC, like the SensMF 628 in FIG. 6B. The example sensing architecture 640 also includes a convergence element 644 and an interface 650a through which the core network 646 communicates with the RAN 652.

[0085] Most of the example architecture 640 and its components may be substantially similar or the same as the components similarly labeled in FIG. 6B. However, in the example architecture 640 shown in FIG. 6C, the SensMF 648 interacts directly with the RAN 652. This affects how the SensMF 648 interacts with at least the RAN 652, and thus the RAN is shown with a different reference number in FIG. 6C than in FIG. 6B. To the extent that this may affect how other components interact with each other, the other components are also shown with different reference numbers in FIG. 6C than in FIG. 6A and FIG. 6C. One important difference from FIG. 6B is that FIG. 6C introduces a new interface 650b between the SensMF 648, including the SAF 654, and the SAF 652. For example, the new interface 650b may be a wired-based backhaul or a wireless-based backhaul, and the backhaul protocol may reuse a current protocol or a newly defined protocol specifically for the wireless backhaul design. It is expected that the other components may be the same as similarly labeled components in Figures 6A and / or 6B.

[0086] 7A-7C are block diagrams illustrating a sensing architecture according to an embodiment similar to that of FIGS. 6A-6C, but with a CU / DU RAN architecture.

[0087] In FIG. 7A, similar to FIG. 6A, a third party network 702 interfaces with a core network 706 via a convergence element 704. The core network 706 includes a sensing coordinator, shown as SensMF 708 by way of example. The core network 706 connects to a RAN 712 via an interface link and an interface shown at 710. The RAN 712 also includes a sensing coordinator, shown as SAF 714 by way of example. Most of the example architecture 700 of FIG. 7A and its components may be substantially similar or the same as the components similarly labeled in FIG. 6A. However, within the example architecture 700 shown in FIG. 7A, or at one or more RAN nodes within the RAN, there is a RAN functional or modular division resulting in a CU 716 and a DU 718. For example, the CU 716 may include or support higher protocol layers such as PDCP and RRC for the control plane and PDCP and SDAP for the data plane, and the DU 718 may include lower layers such as RLC, MAC, and PHY. The SAF 714 interacts with either or both of the CU 716 and DU 718 as part of the control and data modules within the RAN or one or more RAN nodes.

[0088] The CU / DU RAN architecture of Figure 7A may affect how the core network 706 and the RAN 712, and thus the SensMF 708 and the SAF 714, interact with one another. Accordingly, these components are shown with different reference numbers in Figure 7A than in Figure 6A. To the extent that this may affect how other components interact with one another, the other components are also shown with different reference numbers in Figure 7A than in Figure 6A. For example, the SAF 714 may interact with the CU 716 and the DU 718 via the control plane and / or the user plane. It is anticipated that at least these other components may be the same as the similarly labeled components in Figure 6A.

[0089] 7B is substantially similar to FIG. 7A and illustrates a sensing architecture 720 in which a sensing coordinator in the form of a SensMF 728 is located outside the core network 726 and communicates with the RAN 732 via the core network, and another sensing coordinator in the form of a SAF 734. The SensMF 728 is outside the core network 726 and open to a third party network 722, and in some embodiments connects with the RAN 732, including the SAF 734, via a backhaul for its control plane and user plane. As in FIG. 7A, the RAN 732, or one or more nodes therein, has a CU / DU architecture with a CU 736 and a DU 738. The exemplary sensing architecture 720 also includes an interface 730 and a convergence element 724.

[0090] Most of the example architecture 720 and its components may be substantially similar or the same as the similarly labeled components in Figure 7A. However, in the example architecture 720 shown in Figure 7B, the SensMF 728 is external to the core network 726. This may affect how the SensMF 728 interacts with the third party network 722 and the core network 726, and thus the third party network and the core network are shown with different reference numbers in Figure 7B than in Figure 7A. To the extent that this may affect how other components interact with each other, the other components are also shown with different reference numbers in Figure 7B than in Figure 7A. Figure 7B also introduces an interface between the SensMF 728 and the core network 726, and examples of such interfaces are at least provided above. It is anticipated that the other components may be the same as the similarly labeled components in Figure 7A.

[0091] 7C is substantially similar to FIG. 7B and illustrates a sensing architecture 740 according to a further embodiment, in which a sensing coordinator, illustratively shown as SensMF 748, is placed outside the core network 746 and communicates directly with the RAN 752 via an interface link and interface 750b. For example, the SensMF 748 may directly connect with the RAN 752, including the SAF 754, via a backhaul for its control plane and user plane. As in FIG. 7A, the RAN 752, or one or more nodes therein, has a CU / DU architecture including a CU 756 and a DU 758. The illustrative sensing architecture 740 also includes a convergence element 744 and an interface 750a through which the core network 746 communicates with the RAN 752.

[0092] Most of the exemplary architecture 740 and its components may be substantially similar or the same as the similarly labeled components in Figure 7B. However, in the exemplary architecture 740 shown in Figure 7C, the SensMF 748 interacts directly with the RAN 752. This affects how the SensMF 748 interacts with at least the RAN 752, and thus the RAN is shown with a different reference number in Figure 7C than in Figure 7B. To the extent that this may affect how other components interact with each other, the other components are also shown with different reference numbers in Figure 7C than in Figures 7A and 7B. Figure 7C also introduces an interface 750b between the SensMF 748 and the RAN 752, and examples of such interfaces are presented at least above. It is anticipated that the other components may be the same as the similarly labeled components in Figures 7A and / or 7B.

[0093] 8A-8C are block diagrams illustrating sensing architectures according to embodiments similar to those of FIGS. 7A-7C, but having a CU control plane (CP) / user plane (UP) RAN architecture.

[0094] FIG. 8A includes a third party network 802, a convergence element 804, a core network 806 including a sensing coordinator exemplarily shown as a SensMF 808, an interface 810, and a RAN 812 including a sensing coordinator exemplarily shown as a SAF 814, as in FIG. 7A. Most of the example architecture 800 and its components of FIG. 8A may be substantially similar or the same as the components similarly labeled in FIG. 7A. However, in the example architecture 800 shown in FIG. 8A, there is further functional or modular division in the RAN 812 or in one or more RAN nodes within the RAN. As shown, the CU is further divided into a control plane and a user plane, a CU-CP 816a and a CU-UP 816b, and there are multiple DUs 818a, 818b. A CU-CP may include one or more CU-UPs, and multiple CU-UPs 816b are shown in FIG. 8A. In other embodiments, a RAN node may include one CU-CP and one CU-UP, or only one CU-UP and no CU-CP. A RAN node with a CU-CP may connect to and control multiple RAN nodes with only CU-UPs. That is, one CU-CP may control one or more CU-UPs. The CU-CP and any CU-UP may connect to a DU via interfaces F1-c and F1-u, respectively. These are shown as examples in FIG. 8A.

[0095] The SAF 814, in some embodiments, may also connect with a CU-CP, such as 816a and CU-UP 816b, via interfaces F1-c and F1-u, respectively. Although not explicitly shown in Figure 8A, the SAF 814 may optionally be split into control plane and user plane elements.

[0096] The sensing architecture 800 of Figure 8A differs from that of Figure 7A in its CU-CP / CU-UP / multi-DU RAN architecture, which may affect how the core network 806 and the RAN 812, and thus the SensMF 808 and the SAF 814, interact with each other. Interactions between other components may also differ between Figures 8A and 7A. The architectures 700, 800 may be implemented in substantially similar ways otherwise.

[0097] Referring to Figure 8B, like the sensing architecture 800 of Figure 8A, the sensing architecture 820 of Figure 8B includes a third party network 822, a convergence element 824, a core network 826 including a sensing coordinator exemplarily shown as a SensMF 828, an interface 830, and a RAN 832 including a sensing coordinator exemplarily shown as a SAF 834. The RAN 832 also has the same type of architecture as Figure 8A, with a CU-CP 836a, multiple CU-UPs 836b, and multiple DUs 838a, 838b. The example architecture 820 of Figure 8B, and most of its components, may be substantially similar or the same as similarly labeled components in Figure 8A or Figure 7B.

[0098] In the sensing architecture 820 shown in FIG. 8B compared to FIG. 7B, the RAN 832 has a different architecture, where the RAN or one or more RAN nodes include a CU-CP 836a, multiple CU-CPs 836b, and multiple DUs 838a, 838b. This may affect how the core network 826 and the RAN 832, and thus the SensMF 828 and the SAF 834, interact with each other in FIG. 8B compared to FIG. 7B. Interactions between other components may also differ between FIG. 8B and FIG. 7B. The architectures 720, 820 may be implemented substantially similarly in other ways.

[0099] Compared to FIG. 8A, the sensing architecture 820 of FIG. 8B differs in that a sensing coordinator in the form of a SensMF 828 is located outside the core network 826 and communicates with the RAN 832 and another sensing coordinator in the form of a SAF 834 via the core network. This may affect how the SensMF 828 interacts with the third party network 822 and the core network 826, and may also or alternatively affect how other components interact with each other. FIG. 8B also introduces an interface between the SensMF 828 and the core network 826, and examples of such interfaces are provided at least above. The sensing architecture 820 may otherwise be implemented substantially similarly to the sensing architecture 800 of FIG. 8A.

[0100] In Figure 8C, the sensing architecture 840 includes a third party network 842, a convergence element 844, a core network 846 including a sensing coordinator exemplarily shown as a SensMF 848, an interface 850a, and a RAN 852 including a sensing coordinator exemplarily shown as a SAF 854. The RAN 852 has the same type of architecture as Figure 8B, with a CU-CP 856a, multiple CU-UPs 856b, and multiple DUs 858a, 858b. Most of the example architecture 840 of Figure 8C and its components may be substantially similar or the same as similarly labeled components in Figure 8B or Figure 7C.

[0101] In the sensing architecture 840 shown in FIG. 8C compared to FIG. 7C, the RAN 852 has a different architecture, and the RAN or one or more RAN nodes include a CU-CP 856a, multiple CU-CPs 856b, and multiple DUs 858a, 858b. This may affect how the core network 846 and the RAN 852, and therefore the SensMF 848 and the SAF 854, interact with each other in FIG. 8C compared to FIG. 7C. Interactions between other components may also differ between FIG. 8C and FIG. 7C. The architectures 740, 840 may be implemented substantially similarly in other ways.

[0102] Compared to FIG. 8B, the sensing architecture 840 of FIG. 8C differs in that the SensMF 848 directly interacts with the RAN 852. This affects how the SensMF 848 interacts with at least the RAN 852, and may also affect how other components interact with each other. FIG. 8C also introduces an interface 850b between the SensMF 848 and the RAN 852, examples of such an interface being provided at least above. In other respects, the implementation of the sensing architecture 840 may be substantially similar to the implementation of the sensing architecture 820 of FIG. 8B.

[0103] 9A to 9C are block diagrams illustrating sensing architectures according to similar embodiments to those of FIG. 6A to 6C, but with sensing coordination centralized in the RAN (or RAN node). Sensing coordination centralized in the RAN refers to both SensMF and SAF being located in the RAN. The SensMF and one SAF may be integrated or combined, for example, in the RAN node or other network devices in the RAN, or may be implemented separately. For ease of reference, the RAN-based SensMF and SAF are primarily referred to herein as "SMAF" (SensMF+SAF), and the SMAF may include various sensing-related features or functions provided by the individual SensMF and SAF, and the SMAF may have associated interface changes due to the two functions (SensMF and SAF) being combined together into one functional module or component. For example, a third party may directly interface with the RAN node to connect to the SMAF. Like the deployment scenario of the SAF, the SMAF may be located or deployed in a dedicated device or in a sensing node such as a base station, and may control a sensing node or a group of sensing nodes. The sensing nodes can send sensing results to the SMAF node, for example via the backhaul, Uu link, or side link SL. A potential advantage of SMAF is reduced communication latency since there is no delay due to communication between a separate SensMF and SAF, which may be particularly important for control procedures and / or other applications with time-sensitive requirements.

[0104] The SMAF may include a variety of sensing-related features or functions, including, for example, any one or more of the following: Managing and coordinating one or more RAN nodes and / or one or more sensing nodes for sensing activities; communicating for sensing procedures at the RAN node potentially including any one or more of: RAN configuration procedures for sensing, transfer of sensing related information such as sensing measurement data, processed sensing measurement data, and / or sensing measurement data reports; communicating, potentially including the transfer of sensing related information such as any one or more of sensing measurement data, processed sensing measurement data, and sensing measurement data reports, for a sensing procedure at the RAN node; Processing the sensed measurement data and / or otherwise acting on the sensed measurement data, such as generating a sensed measurement data report.

[0105] The SMAF may also include various sensing-related features or functions, including, for example, any one or more of the following: Splitting the sensing control plane and the sensing user plane (SMAF-CP and SMAF-UP), storing or otherwise maintaining the local measurement data and / or other local sensing information; Communicating the sensing measurement data; Processing the sensing measurement data; receiving sensing analysis reports for controlling communications within the RAN and / or for other purposes; Managing, coordinating, or otherwise assisting in the overall sensing and / or control process; Interfacing with artificial intelligence (AI) modules or functions.

[0106] Reference to SMAF does not indicate or imply a necessarily combined implementation of SensMF and SAF, nor does it exclude separate implementations of SensMF and SAF.

[0107] Figure 9A includes a third party network 902, a convergence element 904, a core network 906, an interface 910, and a RAN 912, as in Figure 6A. Most of the example architecture 900 of Figure 9A and its components may be substantially similar or the same as the similarly labeled components in Figure 6A. However, in the example architecture 900 shown in Figure 9A, the SensMF and SAF are both located in the RAN 912, as indicated by the SMAF at 914.

[0108] Electrical devices in the core network 906 and / or the third party network 902 access the RAN 912 and the SMAF 914 via interface links to obtain SMAF services. In the case of the third party network 902, such access is via the convergence element 904. The SMAF 914 may be implemented, for example, in a RAN node, and other SAF implementation options disclosed herein may apply to the SMAF implementation. For example, the core network 906 may provide access to multiple SMAFs, which may be implemented in one RAN node or in multiple RAN nodes in the same or different RANs. Protocols between control and data functions in the core network 906 and the SMAF 914 may be used for control configuration and data communication.

[0109] The sensing architecture 900 of FIG. 9A differs from that of FIG. 6A in that the coordination of sensing is centralized in the RAN 912, which may affect how the core network 906 and the RAN interact with each other. For example, to obtain sensing services from the SMAF of FIG. 9A, the RAN node 912 may not need to have explicit signaling going out, and instead of employing an internal connection interface within the RAN node 912, the core network 906 may directly interface with the RAN node 912 where the SMAF 914 is located. Interactions between other components may also differ between FIG. 9A and FIG. 6A. The architectures 600, 900 may be implemented substantially similarly in other ways.

[0110] 9B, similar to the sensing architecture 900 of FIG. 9A, the sensing architecture 920 of FIG. 9B includes a third party network 922, a convergence element 924, a core network 926, an interface 930, and a RAN 932 that includes a SMAF 934. Most of the example architecture 920 of FIG. 9B and its components may be substantially similar or the same as similarly labeled components of FIG. 9A or FIG. 6B.

[0111] Compared to FIG. 6B, the sensing architecture 920 shown in FIG. 9B differs in that there is no SensMF on the core network side of the interface 930, and the third party network 922 can connect to the SMAF 934 to obtain SMAF services via the convergence element 924 and the core network 926, or more directly via the core network. This may affect how the third party network 922 and the core network 926 interact with each other, and therefore how the third party network interacts with the RAN 932 and the RAN-based sensing coordinator (SMAF 934) in FIG. 9B compared to FIG. 6B. For example, to obtain sensing services from the SMAF in FIG. 9B, the RAN node 932 may not need to have explicit signaling going out, and instead of employing an internal connection interface within the RAN node 932, the core network 926 may directly interface with the RAN node 932 where the SMAF 934 is located. Interactions between other components may also differ between FIG. 9B and FIG. 6B. The architectures 620, 920 may be implemented in substantially similar ways.

[0112] Compared to FIG. 9A, the sensing architecture 920 of FIG. 9B differs in that the third party network 922 may communicate with the RAN 932 via the core network 926, and not necessarily via the convergence element 924 either. The communication between the third party network 922 and the RAN 932 may include new interfaces. At least examples of the new core network interface with the SensMF are provided above, and these examples may also apply to the new core network interface with the third party network. This may affect how the third party network 922 and the core network 926 interact with each other, and therefore how the third party network and the RAN 932 and the SMAF 934 interact with each other in FIG. 9B compared to FIG. 9A. This may also, or instead, affect how other components interact with each other. The sensing architecture 920 may otherwise be implemented substantially similarly to the sensing architecture 900 of FIG. 9A.

[0113] In Figure 9C, the sensing architecture 940 includes a third party network 942, a convergence element 944, a core network 946, an interface 950a, and a RAN 952 including a SMAF 954. Most of the sensing architecture 940 of Figure 9C and its components may be substantially similar or the same as similarly labeled components of Figure 9B or Figure 6C.

[0114] In the sensing architecture 940, the third party network 942 can obtain SMAF services directly by connecting to the SMAF 954 in the RAN 952. As with other embodiments, protocols between control and data functions in the third party network 942 and the SMAF 954 can be used for control configuration and data communication. FIG. 9C introduces an interface 950b between the third party network 942 and the RAN 952. Examples of new interfaces between the RAN and the SensMF are presented at least above, and these examples may also apply to new interfaces with third party networks.

[0115] Compared to FIG. 6C, the sensing architecture 940 shown in FIG. 9C differs in that there is no SensMF on the core network side of the interface 950, and the third party network 952 can connect to the SMAF 954 via the convergence element 944 and the core network 946 or directly. This may affect how the third party network 942 and the core network 946 interact with each other, and therefore how the third party network interacts with the RAN 952 and the RAN-based sensing coordinator (SMAF 954) in FIG. 9C compared to FIG. 6C. For example, to obtain sensing services from the SMAF in FIG. 9C, the RAN node 952 may not need to have explicit signaling going out, and instead of employing an internal connection interface within the RAN node 952, the core network 946 may directly interface with the RAN node 952 where the SMAF 954 is located. Interactions between other components may also differ between FIG. 9C and FIG. 6C. The architectures 640, 940 may be implemented substantially similarly in other ways.

[0116] Compared to Figure 9B, the sensing architecture 940 of Figure 9C differs in that the third party network 942 can directly interact with the RAN 952 and the SMAF 954 via the interface 950b. This may also affect how other components interact with each other. In other respects, the implementation of the sensing architecture 940 may be substantially similar to the implementation of the sensing architecture 920 of Figure 9B.

[0117] 10A-10C are block diagrams illustrating sensing architectures according to embodiments similar to those of FIGS. 7A-7C, but with sensing coordination centralized in the RAN.

[0118] In Figure 10A, as in Figure 7A, the third party network 1002 interfaces with the core network 1006 via a convergence element 1004, which connects to the RAN 1012 via interface links and interfaces shown at 1010, the RAN including one or more RAN nodes in the RAN including the CU 1016 and the DU 1018. The sensing architecture 1000 of Figure 10A differs from the sensing architecture 700 of Figure 7A in that the core network 1006 of Figure 10A does not have a SensMF, and the RAN 1012 or one or more nodes in the RAN includes a SMAF 1014. The SMAF 1014 interacts with either or both of the CU 1016 and the DU 1018 as part of the control and data modules in the RAN or one or more RAN nodes.

[0119] In the sensing architecture 1000 of Figure 10A, sensing coordination is centralized in the RAN 1012, which may affect how the core network 1006 and the RAN interact with each other. Interactions between other components may also differ between Figure 10A and Figure 7A. Architectures 700, 1000 may be implemented in substantially similar ways in other ways.

[0120] FIG. 10B is substantially similar to FIG. 10A and shows a sensing architecture 1020 including a third party network 1022, a convergence element 1024, a core network 1026, an interface 1030, and a RAN 1032, which includes a SMAF 1034 and has a CU / DU architecture including a CU 1036 and a DU 1038.

[0121] Compared to FIG. 7B, the sensing architecture 1020 shown in FIG. 10B differs in that there is no SensMF on the core network side of the interface 1030, and the third-party network 1022 can connect to the SMAF 1034 to obtain SMAF services via the convergence element 1024 and the core network 1026, or more directly via the core network. This may affect how the third-party network 1022 and the core network 1026 interact with each other, and therefore how the third-party network interacts with the RAN 1032 and the RAN-based sensing coordinator (SMAF 1034) in FIG. 10B compared to FIG. 7B. The communication between the third-party network 1002 and the RAN 1012 may include new interfaces, examples of which are at least presented above. Interactions between other components may also differ between FIG. 10B and FIG. 7B. The architectures 720, 1020 may be implemented substantially similarly in other ways.

[0122] Compared to FIG. 10A, the sensing architecture 1020 of FIG. 10B differs in that the third party network 1022 may communicate with the RAN 1032 via the core network 1026, and not necessarily via the convergence element 1024 as well. This may affect how the third party network 1022 and the core network 1026 interact with each other, and therefore how the third party network and the RAN 1032 and the SMAF 1034 interact with each other in FIG. 10B compared to FIG. 10A. Again, the communication between the third party network 1022 and the RAN 1032 may include new interfaces, examples of which are at least presented above. This may also, or instead, affect how other components interact with each other. The sensing architecture 1020 may otherwise be implemented substantially similarly to the sensing architecture 1000 of FIG. 10A.

[0123] In Figure 10C, the sensing architecture 1040 includes a third party network 1042, a convergence element 1044, a core network 1046, an interface 1050a, and a RAN 1052, which includes a SMAF 1054 and has a CU / DU architecture including a CU 1056 and a DU 1058. Most of the sensing architecture 1040 and its components may be substantially similar or the same as similarly labeled components in Figure 10B or Figure 7C.

[0124] In the sensing architecture 1040, the third party network 1042 can obtain SMAF services directly by connecting to the SMAF 1054 in the RAN 1052. As with other embodiments, protocols between control and data functions in the third party network 1042 and the SMAF 1054 can be used for control configuration and data communication. Communications between the third party network 1042 and the RAN 1052 may involve new interfaces, at least examples of which are presented above.

[0125] Compared to FIG. 7C, the sensing architecture 1040 shown in FIG. 10C differs in that there is no SensMF on the core network side of the interface 1050, and the third party network 1052 can connect to the SMAF 1054 via the convergence element 1044 and the core network 1046 or directly via the interface 1050b, examples of which are presented at least above. This may affect how the third party network 1042 and the core network 1046 interact with each other, and therefore how the third party network interacts with the RAN 1052 and the RAN-based sensing coordinator (SMAF 1054) in FIG. 10C compared to FIG. 7C. Interactions between other components may also differ between FIG. 10C and FIG. 7C. The architectures 740, 1040 may be implemented substantially similarly in other ways.

[0126] 10B, the sensing architecture 1040 of FIG. 10C differs in that the third-party network 1042 can directly interact with the RAN 1052 and the SMAF 1054 via the interface 1050b. This may also affect how other components interact with each other. In other respects, the implementation of the sensing architecture 1040 may be substantially similar to the implementation of the sensing architecture 1020 of FIG. 10B.

[0127] 11A-11C are block diagrams illustrating a sensing architecture according to an embodiment similar to that of FIGS. 8A-8C, but with sensing coordination centralized in the RAN.

[0128] FIG. 11A includes a third-party network 1102, a convergence element 1104, a core network 1106, an interface 1110, and a RAN 1112, similar to FIG. 8A. Most of the sensing architecture 1100 and its components of FIG. 11A may be substantially similar or the same as the similarly labeled components of FIG. 8A. However, in the example architecture 1100 shown in FIG. 11A, sensing coordination is centralized in the RAN 1112, which includes the SMAF 1114, and there is further functional or modular division of the RAN 1112. The RAN 1112, or one or more RAN nodes within the RAN, includes a CU-CP 1116a and multiple CU-UPs 1116b, as well as multiple DUs 1118a, 1118b. Features disclosed elsewhere herein with respect to the CU-CP / CU-UP / DU architecture may also or instead be applied to the architecture 1100.

[0129] The sensing architecture 1100 of Figure 11A differs from the sensing architecture 800 of Figure 8A in that there is no SensMF in the core network 1106 of Figure 11A, the RAN 1112 or one or more nodes in the RAN includes a SMAF 1114, and the RAN 1112 has a CU-CP / CU-UP / multiple DU architecture. The SMAF 1114 interacts with one or more of the CU-CP 1116a, CU-UP 1116b, and / or one or more of the DUs 1118a, 1118b as part of the control and data modules in the RAN or one or more RAN nodes.

[0130] In the sensing architecture 1100 of Figure 11A, sensing coordination is centralized in the RAN 1112, which may affect how the core network 1106 and the RAN interact with each other. Interactions between other components may also differ between Figure 11A and Figure 8A. Architectures 800, 1100 may be implemented in substantially similar manners in other ways.

[0131] FIG. 11B is substantially similar to FIG. 11A and shows a sensing architecture 1120 including a third party network 1122, a convergence element 1124, a core network 1126, an interface 1130, and a RAN 1132, which includes a SMAF 1134 and has a CU-CP / CU-UP / multi-DU architecture including a CU-CP 1136a, a CU-UP 1136b, and DUs 1138a, 1138b.

[0132] Compared to FIG. 8B, the sensing architecture 1120 shown in FIG. 11B differs in that there is no SensMF on the core network side of the interface 1130, and the third-party network 1122 can connect to the SMAF 1134 to obtain SMAF services via the convergence element 1124 and the core network 1126, or more directly via the core network. This may affect how the third-party network 1122 and the core network 1126 interact with each other, and therefore how the third-party network interacts with the RAN 1132 and the RAN-based sensing coordinator (SMAF 1134) in FIG. 11B compared to FIG. 8B. The communication between the third-party network 1122 and the RAN 1132 may include new interfaces, examples of which are at least presented above. Interactions between other components may also differ between FIG. 11B and FIG. 8B. The architectures 820, 1120 may be implemented substantially similarly in other ways.

[0133] Compared to FIG. 11A, the sensing architecture 1120 of FIG. 11B differs in that the third party network 1122 may communicate with the RAN 1132 via the core network 1126 and a new interface, not necessarily via the convergence element 1124 either. This may affect how the third party network 1122 and the core network 1126 interact with each other, and thus how the third party network and the RAN 1132 and SMAF 1134 interact with each other in FIG. 11B compared to FIG. 11A. This may also, or instead, affect how other components interact with each other. The sensing architecture 1120 may otherwise be implemented substantially similarly to the sensing architecture 1100 of FIG. 11A.

[0134] 11C, the sensing architecture 1140 includes a third party network 1142, a convergence element 1144, a core network 1146, an interface 1150a, and a RAN 1152 that includes a SMAF 1154 and has a CU-CP / CU-UP / multi-DU architecture that includes a CU-CP 1156a, a CU-UP 1156b, and DUs 1158a, 1158b. Most of the sensing architecture 1140 and its components may be substantially similar or the same as similarly labeled components in FIG. 11B or FIG. 8C.

[0135] In the sensing architecture 1140, the third party network 1142 can obtain SMAF services directly by connecting to the SMAF 1154 in the RAN 1152 via interface 1150b, examples of which are presented at least above. As with other embodiments, protocols between control and data functions in the third party network 1142 and the SMAF 1154 can be used for control configuration and data communication.

[0136] Compared to FIG. 8C, the sensing architecture 1140 shown in FIG. 11C differs in that there is no SensMF on the core network side of the interface 1150, and the third party network 1152 can connect to the SMAF 1154 via the convergence element 1144 and the core network 1146 or directly via the interface 1150b. This may affect how the third party network 1142 and the core network 1146 interact with each other, and therefore how the third party network interacts with the RAN 1152 and the RAN-based sensing coordinator (SMAF 1154) in FIG. 11C compared to FIG. 8C. Interactions between other components may also differ between FIG. 11C and FIG. 8C. The architectures 840, 1140 may be implemented substantially similarly in other ways.

[0137] 11B, the sensing architecture 1140 of FIG. 11C differs in that a third party network can directly interact with the RAN 1152 and the SMAF 1154. This may also affect how other components interact with each other. In other respects, the implementation of the sensing architecture 1140 may be substantially similar to the implementation of the sensing architecture 1120 of FIG. 11B.

[0138] Figure 12 is a block diagram of a sensing architecture 1200 according to a further embodiment. The sensing architecture 1200 shows an example where a sensing coordinator (SensMF) is located in the core network and another sensing coordinator (SAF) is located in the RAN, for example in one or more RAN nodes. Other examples of this type of architecture are also shown in Figures 6A, 7A, and 8A.

[0139] In Figure 12, the core network is indicated at 1210, an external network outside the core network is exemplarily indicated as an edge cloud at 1230, and the NG-RAN is indicated at 1240. The NG-RAN 1240 includes base stations (BSs) 1250, 1260, and the UEs to which the NG-RAN provides access to the core network 1210 are indicated at 1270.

[0140] The core network 1210 may be, for example, an SBA network, and in the illustrated embodiment, the core network includes various functions or elements coupled by an SBI bus 1228. These functions or elements include an NSSF 1212, a PCF 1214, a NEF 1216, a SensMF 1218, an SMF 1222, an AMF 1224, and a UPF 1226. The AMF 1224 and the UPF 1226 communicate with other elements outside the core network 1210 via interfaces, shown as N2, N3, and N6 interfaces.

[0141] Both BS1 and BS2 have a CU / DU / RU architecture, each including one CU / SAF 1252, CU / SAF 1262 including an SAF, and two RUs 1257 / 1259, RU 1267 / 1269. BS1 includes two DUs 1254, DU 1256, and BS2 includes one DU 1264. In FIG. 12, the SAF is shown combined with the CU, but the SAF does not necessarily have to be integrated into the CU or otherwise combined with the CU. The interfaces for BS1 and BS2 to communicate with each other and with the UE 1270 are shown as Xn and Uu interfaces, respectively, and the F1CU / DU interface is also shown as an example.

[0142] The architecture representation in FIG. 12 is similar to that in FIG. 5. However, in FIG. 12, the SensMF 1218 is the LMF 5 18 and LCS entities 512 are part of the core network 1210, not SAF 20. BS 1250 and BS 1260 in FIG. 62 Includes.

[0143] Sensing operations in an architecture such as that shown in Figure 12 are described by way of example with reference to the signal flow diagrams of Figures 13 and 14. These examples may also apply, at least to some extent, to other embodiments such as those shown in Figures 6A, 7A, and 8A.

[0144] Figure 13 is a signal flow diagram illustrating an example method that may be applicable to an architecture of the type shown in Figure 12. Although described herein with respect to the sensing architecture shown in Figure 12, methods consistent with Figure 13 or portions thereof may also or instead be applied to different sensing architectures. Similarly, other methods herein may be applied to sensing architectures other than the one in the context in which such methods are described.

[0145] The method illustrated by Figure 13 includes a UE 1302, an NG-RAN node 1304, an AMF 1306, and a SensMF 1308. These components may be, for example, as shown in Figure 12 at 1270, 1250 / 1260, 1224, and 1218, respectively.

[0146] At 1322, a sensing service request (SSR) is sent by the SAF of the NG-RAN node 1304 to the AMF 1306 and received by the AMF 1306. The SSR is more related to communication control, and therefore the SSR message context may include sensing request information more related to communication. For example, the SSR may include information indicating sensing requirements, such as any one or more of positioning, mobility, Doppler, movement direction, beamforming direction or angle, etc., of a particular UE and / or other device, or of a UE and / or other device in a particular area. The SSR may also include sensing configuration parameters, such as sensing node, sensing service period, sensing operation mode, sensing reporting period, joint sensing with other sensors, or individual sensing.

[0147] In some embodiments, the SSR may request vehicle and road traffic measurements via several sensing nodes (e.g., sensing devices and TRPs) and may be timed to be transmitted, for example, at night or when there is little data communication in the wireless network. As a result, the SensMF and SAF may configure the appropriate devices, TRPs, and base stations to achieve the requested service. Information indicating measurements to be taken and / or other sensing parameters or requirements may take any of a variety of forms. The present disclosure is not limited to any particular way of indicating sensing parameters or requirements. Implicit and explicit signaling are possible. The SSR may, for example, explicitly specify measurements to be taken, or such measurements may be implicit in the SSR specifying a particular sensing device that should take the measurements.

[0148] SSR may be triggered periodically or on demand. A demand-based trigger of SSR may be associated with or for a condition configured based on, for example, an application and its sensing data requirements. In an embodiment, when RAN operations are initialized, an Administration and Maintenance (OAM) module may configure one or more RAN nodes to obtain sensing request periodicity or to define events for triggering sensing requests or processes. Such configuration may be semi-static in some embodiments.

[0149] In FIG. 13, the SSR is transmitted by the AMF 1306 to the SensMF 1308 and received by the SensMF 1308 at 1324. Although shown in FIG. 13 as a two-step, two-part process, this transfer of the SSR from the SAF of the NG-RAN node 1304 to the SensMF 1308 is an example of a first sensing coordinator (the SAF of the NG-RAN node 1304) in a radio access network that provides access to a core network of a wireless communications system communicating a first signal (the SSR) with a second sensing coordinator (the SensMF 1308) by or through an interface link, in this example via the AMF 1306.

[0150] 13, 1326 and 1328, respectively, illustrate interactions between the SensMF 1308 and each of the NG-RAN node 1304 and the UE 1302. Although not shown in FIG. 13, for example, prior to 1328 or when the UE 1302 first enters the wireless communications system during initial access, the UE may report its sensing capabilities, including capabilities of any one or more of supported sensing features and supported operational sensing modes, to the SAF and / or SensMF 1308 of the NG-RAN node 1304.

[0151] At 1326, the SensMF 1308 manages and controls one or more NG-RAN nodes for sensing procedures. For example, based on sensing capabilities and sensing requirements, the SensMF 1308 may configure associated RAN nodes for sensing activities that may include delivering sensing data or measurement results to the SensMF for sensing analysis. At 1328, the SensMF 1308 manages and controls one or more UEs for sensing procedures. For example, based on the UE's sensing capabilities (e.g., reported by the UE during initial access to the network) and sensing requirements, the SensMF 1308 and the RAN nodes may configure associated UE nodes for sensing activities that may include delivering sensing data or measurement results to the SensMF for sensing analysis. Communications between sensing devices and the SensMF and / or SAF, such as at 1326 and 1328, are examples of communicating signals between sensing coordinators.

[0152] The SensMF 1308 receives sensing measurement data transmitted from the UE 1302 (and possibly one or more other UEs or sensing devices) and / or the NG-RAN node 1304 (and possibly one or more other nodes) during a sensing procedure 1326, a sensing procedure 1328. Figure 13 includes both an NG-RAN node sensing procedure 1326 and a UE sensing procedure 1328 for illustrative purposes only. Sensing may include either or both of an NG-RAN node sensing procedure and a UE sensing procedure.

[0153] A sensing service response (SSResp) is sent by the SensMF 1308 and received by the AMF 1306 at 1330 and sent by the AMF 1306 and received by the NG-RAN node 1304 at 1332. This is another example of communicating signals between sensing coordinators.

[0154] The SSResp 1330, SSResp 1332 may include any of various types of processed sensing related information by the SensMF 1308 after the SensMF 1308 receives all sensing or measurement information from the associated sensing nodes / sensing devices at 1326 and / or 1328, where the sensing or measurement information is based on the sensing requirements of the communication related SSR 1322, SSR 1324. The SensMF 1308 may use the received raw measurement data to estimate the requested sensing information, for example. The requested sensing information may include specific device sensing information, such as positioning, Doppler, movement direction, beamforming direction / angle, and / or mobility. The requested sensing information may also or instead include sensing information of a group of UEs or other devices in a particular area. Processing the sensing measurement data and / or otherwise acting on the sensing measurement data, such as generating a sensing measurement data report.

[0155] In general, the SensMF 1308 may receive at least sensed measurement data from one or more sensing devices, generate a response or report based on the received sensed measurement data, and transmit the response to or toward the requestor, as shown by way of example at 1326, 1328. The response or report may include one or more of the received raw measurement data, processed data, and / or another form of sensed measurement data report.

[0156] SAF processing of sensing responses or reports such as SSResp at 1334 may include, for example, utilizing the sensing information for optimized control and / or communication. As an example, the sensing reports may provide vehicle traffic information that can help an automated driving or driver avoid high traffic congestion areas by taking alternate routes where the sensing reports indicate low traffic volume.

[0157] Figure 14 is a signal flow diagram illustrating another example method that may be applicable to the type of architecture shown in Figure 12. The operational scenario of Figure 14 is similar to that of Figure 13 and includes a UE 1402, an NG-RAN node 1404, an AMF 1406, and a SensMF 1408. A sensing service center 1410, which may be part of the core network, for example, or in an external network such as the edge cloud 1230 of Figure 12, is also shown in Figure 14 as an example of another entity that may use sensing services.

[0158] The overall signal flow in Figure 14 is similar to that in Figure 13, including the SSR sent by the AMF 1406 and received by the SensMF 1408 at 1422, sensing procedures at 1424, 1426, either or both of which may be implemented, and the SSResp sent by the SensMF 1408 and received by the AMF 1406 at 1428. Figure 14 further illustrates other potential sources of the SSR and / or destinations of the SSResp.

[0159] In particular, the SSR may be sent by the sensing service center 1410 and received by the AMF 1406, as shown at 1420a, self-triggered or originated by the AMF 1406, as shown at 1420b, or sent by the UE 1402 and received by the AMF 1406, as shown at 1420c, where 1420b and 1420c may be sensing requests more related to communication and control. Since the SSR 1420a is from the sensing service center 1410, the SSR message context may include a sensing request context more related to a standalone sensing service. For example, the SSR may include information indicating sensing requirements, such as any one or more of positioning, vehicle traffic load and congestion status, environmental temperature, humidity, etc., of a particular UE and / or other device, or of UEs and / or other devices in a particular area. The SSR may also include sensing configuration parameters such as sensing node, sensing service period, sensing operation mode, sensing reporting period, joint sensing with other sensors or individual sensing, etc. Any or all of these options may be supported, and possibly others, such as the SAF / RAN node SSR as in Figure 13. Regardless of their source, the SSRs are transmitted by the AMF 1406 to the SensMF 1408 in the example shown in Figure 14.

[0160] 14 may include any of various types of processed sensing related information by the SensMF 1408 after the SensMF 1408 receives all sensing or measurement information from the associated sensing nodes / sensing devices at 1424 and / or 1426 (at one or more RAN nodes), where the sensing or measurement information is based on the sensing requirements of the SSRs 1420a, 1420b or / and 1420c. The SensMF 1408 may use the received raw measurement data to estimate requested sensing information, for example. The requested sensing information may include specific device sensing information, such as positioning, vehicle traffic load and congestion, environmental temperature, humidity, Doppler, movement direction, beamforming direction / angle, traffic load, and / or mobility. SSResp 1428 may include individual sensing responses SSResp 1430a, 1430b, or / and 1430c (not shown in FIG. 14), which are the results obtained by sensing service requests SSR 1420a, 1420b, and 1420c, respectively.

[0161] With respect to any of the SSResp 1430a, 1430b, and 1430c, the options illustrated in Figure 14 include the AMF 1406 sending the SSResp, and the sensing service center 1410 receiving the SSResp at 1430a, the AMF 1406 receiving the SSResp and processing or possibly routing the SSResp internally within the core network as shown at 1430b, the AMF 1406 sending the SSResp, and the UE 1402 receiving the SSResp as shown at 1420c, and the AMF 1406 sending the SSResp, and the NG-RAN node 1404 receiving the SSResp as shown at 1432. The option at 1432 illustrates an embodiment in which the SSResp may be sent to the SAF, or more generally, to another entity that does not originate or transmit the SSR. For example, the SAF may update its local sensing information from the sensing analysis report from the SensMF 1408 to obtain more accurate sensing information as well as for better communication control in one or more RAN nodes.

[0162] Any or all of these options, and possibly others, may be supported. In the illustrated example, SSResp is always sent by SensMF 1408 to and received by AMF 1406.

[0163] Similar to FIG. 13, SAF processing of a sensing response or report, such as SSResp, is shown at 1434 in FIG.

[0164] Figure 15 is a block diagram of a sensing architecture 1500 according to yet another embodiment. Referring to Figure 15, a core network is shown at 1510, an external network outside the core network is shown at 1530, and an NG-RAN is shown at 1540. The SensMF 1520 may or may not be connected to the core network 1510. The NG-RAN 1540 includes BS1 1550 and BS2 1560, and UEs to which the NG-RAN provides access to the core network 1510 are shown at 1570.

[0165] Both BS1 and BS2 have a CU / DU / RU architecture, each including one CU / SAF 1552 including an SAF, CU / SAF 1562, and two RUs 1557 / 1559, RU 1567 / 1569. BS1 includes two DUs 1554, DU 1556, and BS2 includes one DU 1564. The interfaces for BS1 and BS2 to communicate with each other and with the UE 1570 are shown as Xn and Uu interfaces, respectively, and an F1CU / DU interface is also shown as an example.

[0166] The sensing architecture 1500 is substantially similar to the sensing architecture 1200 of FIG. 12, except that the sensing coordinator (SensMF 1520) is located outside the core network 1510. The SensMF 1520 can communicate, for example, with the NG-RAN 1540 and with one or more SAFs in one or more RAN nodes, such as BS1 and / or BS2, via the core network 1510 or directly. Other examples of this type of architecture, with a core network or direct communication between the SensMF and the SAF, are also shown in FIG. 6B, FIG. 6C, FIG. 7B, FIG. 7C, FIG. 8B, and FIG. 8C.

[0167] Figure 16 is a signal flow diagram illustrating an example method that may be applicable to the type of architecture shown in Figure 15. The example illustrated in Figure 16 relates to an operational scenario including a UE 1602, an NG-RAN node 1604, a SensMF 1606, and a sensing service center 1608, which may be located in the other network 1530 of Figure 15 as shown. The SAF is located in the NG-RAN node 1604 of Figure 16.

[0168] The SSR is sent by the sensing service center 1608 and received by the SensMF 1606 at 1620 and sent by the SensMF 1606 and received by the NG-RAN node 1604 at 1622. The UE sensing procedure is shown at 1624, in this example an SSResp is generated and sent by the SAF of the NG-RAN node 1604. The SSResp is sent by the NG-RAN node 1604 and received by the SensMF 1606 at 1626. 6 , and then at 1628, the SensMF sends an SSResp, which is received by the sensing service center 1608. In this example, 1622 and 1626 both indicate communicating signals between sensing coordinators (SensMF and SAF), one of which (the SAF of the NG-RAN node 1604) is within the RAN.

[0169] 17 is a block diagram of a sensing architecture according to a further embodiment. A core network 1710 is exemplarily shown as an SBA network, an external network 1730 outside the core network is exemplarily shown as an edge cloud, and an NG-RAN is shown at 1740. The NG-RAN 1740 includes BS1 1750 and BS2 1760, and UEs to which the NG-RAN provides access to the core network 1710 are shown at 1770.

[0170] Both BS1 and BS2 have a CU / DU / RU architecture, each including one CU / SMAF 1752, CU / SMAF 1762, including an SMAF, and two RUs 1757 / 1759, RU 1767 / 1769. BS1 includes two DUs 1754, DU 1756, and BS2 includes one DU 1764. In FIG. 17, the SMAF is shown combined with the CU, but the SMAF does not necessarily have to be integrated into the CU or otherwise combined with the CU. The interfaces for BS1 and BS2 to communicate with each other and with the UE 1770 are shown as Xn and Uu interfaces, respectively, and the F1CU / DU interface is also shown as an example.

[0171] Sensing architecture 1700 is substantially similar to sensing architecture 1200 of Figure 12, except that the SensMF is not external to the NG-RAN 1740. The NG-RAN 1740 includes one or more SMAFs, one of which is implemented in each of the BSs 1750, 1760 in the illustrated example. Other examples of this type of architecture, where sensing coordination is centralized in the RAN and communicates with one or more SMAFs via a core network, are also shown in Figures 9A, 10A, and 11A.

[0172] Figure 18 is a signal flow diagram illustrating an example method that may be applicable to the type of architecture shown in Figure 17. The example illustrated in Figure 18 relates to an operational scenario including a UE 1802, an NG-RAN node 1804, a SensMF 1806, and a sensing service center 1808, which may be located in another network, such as the edge cloud 1730 of Figure 17, as shown. The SAF is located in the NG-RAN node 1804 of Figure 18.

[0173] The overall signal flow of Figure 18 is similar to that of the other signal flow diagrams, including the SSR sent by the AMF 1806 and received by the sensing coordinator (SMAF in the NG-RAN node 1804) at 1822, the UE's sensing procedure at 1824, and the SSResp sent by the sensing coordinator (SMAF in the NG-RAN node 1804) and received by the AMF 1806 at 1826. Potential sources of the SSR in Figure 18 include the sensing service center 1808 as a source sending the SSR that is received by the AMF 1806, as shown at 1820a, or the AMF 1806 as a source that self-originates or self-triggers the SSR, as shown at 1820b, or the UE 1802 as a source sending the SSR that is received by the AMF 1806, as shown at 1820c. The SSR is transmitted by the AMF 1806 to the NG-RAN node 1804 in the example shown in FIG. 18, whether the SSR originates at the AMF 1806 itself or from another entity. Potential destinations of the SSResp in FIG. 18 include the sensing service center 1808 receiving the SSResp transmitted by the AMF 1806, as shown at 1828a, the AMF 1806 receiving the SSResp transmitted by the core network and processing or possibly routing the SSResp within the core network, as shown at 1828b, and the UE 1802 receiving the SSResp transmitted by the AMF 1806, as shown at 1820c. Any or all of these options, and possibly others, may be supported. In the example shown, the SSR and SSResp are communicated at least between the SMAF of the NG-RAN node 1804 and the AMF 1806.

[0174] Although not shown in FIG. 18, there may be other SMAF processes in the NG-RAN node 1804, for example instead of or in addition to the process for generating the SSResp.

[0175] 19 is a block diagram of a sensing architecture according to another embodiment. A core network is shown at 1910, an external network outside the core network is shown at 1930, and an NG-RAN is shown at 1940. A sensing service center 1920 may or may not be connected to the core network 1910. The NG-RAN 1940 includes BS1 1950 and BS2 1960, and UEs are shown at 1970 to which the NG-RAN provides access to the core network 1910.

[0176] Both BS1 and BS2 have a CU / DU / RU architecture, each including one CU / SMAF 1952, CU / SMAF 1962 including an SMAF, and two RUs 1957 / 1959, RU 1967 / 1969. BS1 includes two DUs 1954, DU 1956, and BS2 includes one DU 1964. The interfaces for BS1 and BS2 to communicate with each other and with the UE 1970 are shown as Xn and Uu interfaces, respectively, and an F1CU / DU interface is also shown as an example.

[0177] Sensing architecture 1900 is substantially similar to sensing architecture 1500 of Figure 15, but without a SensMF external to NG-RAN 1940. NG-RAN 1940 includes one or more SMAFs, one of which is implemented in each of BS 1950, BS 1960 in the illustrated example. Other examples of this type of architecture, where sensing coordination is centralized in the RAN and communicates with one or more SMAFs via a core network or directly, are also shown in Figures 9B, 9C, 10B, 10C, 11B, and 11C.

[0178] Figure 20 is a signal flow diagram illustrating an example method that may be applicable to the type of architecture shown in Figure 19. The example illustrated in Figure 20 relates to an operational scenario including a UE 2002, an NG-RAN node 2004, and a sensing service center 2006, which may be located in another network, such as network 1930 of Figure 19, as shown. The SMAF is located in the NG-RAN node 2004 of Figure 20.

[0179] The overall signal flow in Figure 20 is similar to that of the other signal flow diagrams: the SSR is sent by the sensing service center 2006 in this example and received by the sensing coordinator (SMAF in the NG-RAN node 2004) at 2020, the UE sensing procedure is performed at 2022, and the SSResp is sent by the sensing coordinator (SMAF in the NG-RAN node 2004) and received by the sensing service center 2006 at 2024. This is similar to Figure 16, for example, except that there is no SensMF in Figure 20, and similar to Figure 18, except that there is no AMF in Figure 20.

[0180] Although not shown in FIG. 20, there may be other SMAF processes in the NG-RAN node 2004, for example instead of or in addition to the process for generating the SSResp.

[0181] Other procedures or features may also or instead be provided. Figure 21 is a signal flow diagram illustrating another exemplary method that may be applicable to the type of architecture shown in Figure 19, including examples of additional features that may be provided in some embodiments. Notably, within the same operating scenario involving a UE 2102, an NG-RAN node 2104, and a sensing service center 2106, and an SSR / UE sensing procedure / SSResp process at 2120, 2124, 2126, as in Figure 20, Figure 21 also includes an acknowledgement / negative acknowledgement (ACK / NACK) for the SSR sent by the sensing coordinator (the SMAF of the NG-RAN node 2104) to the requestor (the sensing service center 2106) at 2122. A NACK for the SSR may be sent at 2122, for example, if the sensing service is unavailable or the SSR is not able to be processed for another reason.

[0182] 21, other types of signaling may also or instead be used in other embodiments to confirm to the requestor whether the sensing service request has been received and / or processed. It should also be understood that confirmation signaling such as ACK / NACK is in no way limited to embodiments including a SMAF and / or a sensing service center, but may be implemented in combination with other embodiments disclosed herein.

[0183] Figure 22 is a block diagram illustrating an example protocol stack according to an embodiment. Exemplary protocol stacks in the UE, RAN, and SensMF are shown at 2210, 2230, 2260, respectively, for an example based on a uu air interface between the UE and the RAN. Figure 22, and other block diagrams illustrating protocol stacks, are examples only. Other embodiments may include similar or different protocol layers arranged similarly or differently.

[0184] The sensing protocol or SensProtocol (SensP) layer 2212, 2262 shown in the exemplary UE 2210 and SensMF protocol stack 2260 is a higher protocol layer between the SensMF and the UE to support transfer of control information and / or sensing information over the air interface, which in the illustrated example is, or at least includes, a uu interface.

[0185] The non-access stratum (NAS) layer 2214, 2264, also shown in the exemplary UE 2210 and SensMF protocol stack 2260, is another higher protocol layer and, in the illustrated example, forms the highest layer of the control plane between the UE and the core network in the radio interface. The NAS protocol, in the illustrated example, may be responsible for features such as one or more of supporting UE mobility and session management procedures for establishing and maintaining IP connectivity between the UE and the core network. NAS security is an additional feature of the NAS layer that may be provided in some embodiments to support one or more services for the NAS protocol, such as, for example, integrity protection and / or encryption of NAS signaling messages.

[0186] The Radio Resource Control (RRC) layers 2216, 2232 shown in the UE and RAN protocol stacks at 2210, 2230 are responsible for any of the following features: broadcasting system information related to the NAS layer, broadcasting system information related to the Access Stratum (AS), paging, establishing, maintaining and releasing an RRC connection between the UE and a base station or other network device, security functions, etc.

[0187] A Packet Data Convergence Protocol (PDCP) layer 2218, 2234 is also shown in the exemplary UE and RAN protocol stacks 2210, 2230 and is responsible for any of the following features: sequence numbering, header compression and decompression, forwarding of user data, reordering and duplicate detection if in-order delivery to layers above PDCP is required, PDCP Protocol Data Unit (PDU) routing in case of split bearers, ciphering and deciphering, duplication of PDCP PDUs, etc.

[0188] A Radio Link Control (RLC) layer 2220, 2236 is shown in the exemplary UE 2210 and RAN protocol stack 2230 and is responsible for any of the following features: transport of higher layer PDUs, sequence numbering independent of PDCP sequence numbering, automatic repeat request (ARQ) segmentation and resegmentation, service data unit (SDU) reassembly, etc.

[0189] The Medium Access Control (MAC) layers 2222, 2238, further shown in the exemplary UE 2210 and RAN protocol stack 2230, are responsible for any of the following features: mapping between logical channels and transport channels, multiplexing MAC SDUs from one logical channel or different logical channels into transport blocks (TBs) to be delivered to the physical layer on the transport channels, demultiplexing MAC SDUs from one logical channel or different logical channels from TBs delivered from the physical layer on the transport channels, scheduling information reporting, and dynamic scheduling of downlink and uplink data transmissions for one or more UEs.

[0190] The physical (PHY) layer 2224, 2240 may provide or support any of the following features: channel encoding and decoding, bit interleaving, modulation, signal processing, etc. The PHY layer handles all information from the MAC layer transport channels over the air interface and may also work in conjunction with the MAC layer, handling procedures such as link adaptation via adaptive modulation and coding (AMC), power control, cell search for either or both initial synchronization and handover purposes, and / or other measurements.

[0191] The relay 2242 represents the relaying of information through different protocol stacks with protocol conversion from one interface to another, this protocol conversion being between the air interface (between the UE 2210 and the RAN 2230) and the wired interface (between the RAN 2230 and the SensMF 2260).

[0192] The NG (Next Generation) Application Protocol (NGAP) layers 2244, 2266 in the exemplary protocol stack 2260 of the RAN 2230 and the SensMF provide a method for exchanging control plane messages associated with the UE over the interface between the RAN and the SensMF, where the UE association with the RAN at the NGAP layer 2244 is by a UE NGAP ID that is unique within the RAN, and the UE association with the SensMF at the NGAP layer 2266 is by a UE NGAP ID that is unique within the SensMF, and the two UE NGAP IDs may be bound in the RAN and the SensMF upon session setup.

[0193] The exemplary protocol stack 2260 of the RAN 2230 and SensMF also includes Stream Control Transmission Protocol (SCTP) layers 2246, 2268, which may provide similar features as the PDCP layers 2218, 2234, but for the wired SensMF-RAN interface.

[0194] Similarly, the Internet Protocol (IP) layer 2248, 2270, Layer 2 (L2) 2250, 2272, and Layer 1 (L1) 2252, 2274 protocol layers of the illustrated example may provide similar characteristics to the RLC, MAC, and PHY layers of the NR / LTE Uu air interface, but for the wired SensMF-RAN interface of the illustrated example.

[0195] Figure 22 shows an example of protocol layering for SensMF / UE interaction. In this example, SensP is used on top of the current air interface (uu) protocol. In other embodiments, SensP may be used with a newly designed air interface for sensing in lower layers. SensP represents a higher layer protocol for carrying sensing data, optionally with encryption, according to a sensing format defined for data transmission between the UE and a sensing module or coordinator such as SensMF.

[0196] Figure 23 is a block diagram illustrating example protocol stacks according to another embodiment. Exemplary protocol stacks in the RAN and SensMF are shown at 2310 and 2330, respectively. Figure 23 relates to RAN / SensMF interworking and may apply to any of various types of interfaces between the UE and the RAN.

[0197] The SensMFRAN Protocol (SMFRP) layers 2312, 2332 represent higher protocol layers between the SensMF and the RAN nodes to support the transfer of control and sensing information over the interface between the SensMF and the RAN nodes, which in this example is a wired connection interface. Other illustrated protocol layers include the NGAP layers 2314, 2334, the SCTP layers 2316, 2336, the IP layers 2318, 2338, the L2 2320, 2340, and the L1 2312, 2342, which are at least described by way of example above.

[0198] Figure 23 shows an example of protocol layering for SensMF / RAN node interaction. SMFRP can be used on top of the wired connection interface as in the illustrated example, on top of the current air interface (uu) protocol, or with a newly designed air interface for sensing at a lower layer. SensP is another higher layer protocol to carry sensing data, optionally with encryption, with a sensing format defined for data transmission between sensing coordinators, which may include UEs shown in Figure 22, RAN nodes with SAF or SMAF, and / or sensing coordinators such as SensMF implemented in the core network or third party networks.

[0199] FIG. 24 is a block diagram illustrating an example of a protocol stack according to a further embodiment, including a new control plane for sensing and a new user plane for sensing. plane Exemplary control plane protocol stacks in the UE, RAN, and SensMF are shown at 2410, 2430, 2450, respectively, and exemplary user plane protocols for the UE and RAN are shown at 2460 and 2480, respectively.

[0200] The example of Figure 22 is based on the uu air interface between the UE and the RAN, while in the example sensing connectivity protocol stack of Figure 24, the UE / RAN air interface is a newly designed or modified sensing specific interface, indicated by the "s-" label in the protocol layer. In general, the air interface for sensing can be between the RAN and the UE and / or can include wireless backhaul between the SensMF and the RAN.

[0201] The SensP layers 2412, 2452 and the NAS layers 2414, 2454 are described at least by way of example above.

[0202] The s-RRC layers 2416, 2432 may reuse 4G or 5G air interface RRC protocols or may use a newly defined or modified RRC layer for sensing. For example, the s-RRC system information broadcast may include sensing configuration, sensing capability information support, etc. of the device during initial access to the network.

[0203] The s-PDCP layers 2418, 2434 may similarly reuse the 4G or 5G air interface PDCP protocol, or may use a newly defined or modified PDCP layer for sensing, e.g., to provide PDCP routing and relaying through one or more relay nodes.

[0204] The s-RLC layers 2420, 2436 may reuse the 4G or 5G air interface RLC protocol, or may use a newly defined or modified RLC layer for sensing, for example, without SDU segmentation.

[0205] The s-MAC layers 2422, 2438 may reuse the 4G or 5G air interface MAC protocols, or may use a newly defined or modified MAC layer for sensing, for example, using one or more new MAC control elements, one or more new logical channel identifiers, different scheduling, etc.

[0206] Similarly, the s-PHY layers 2424, 2440 may reuse 4G or 5G air interface PHY protocols, or may use newly defined or modified PHY layers for sensing, e.g., using one or more of a different waveform, different encoding, different decoding, different modulation and coding scheme (MCS), etc.

[0207] In an exemplary new user plane for sensing, the following layers are described at least by way of example above: s-PDCP 2464, 2484, s-RLC 2466, 2486, s-MAC 2468, 2488, s-PHY layer 2470, 2490. The Service Data Adaptation Protocol (SDAP) layer is responsible for, for example, mapping between Quality of Service (QoS) flows and data radio bearers and marking QoS Flow Identifiers (QFIs) on both downlink and uplink packets, and a single protocol entity of SDAP is configured for each individual PDU session, except for dual connectivity where two entities can be configured. The s-SDAP layer 2462, 2482 may reuse the 4G or 5G air interface SDAP protocol, or may use a newly defined or modified SDAP layer for sensing, for example to define a QoS flow ID for sensing packets, different from downlink and uplink data bearers, or with a special identification for sensing, etc.

[0208] 25 is a block diagram illustrating an example interface between a core network and a RAN. Example 2500 illustrates an "NG" interface between a core network 2510 and a RAN 2520, with two BSs 2530, 2540 shown as example RAN nodes. BS 2540 has a sensing specific CU / DU architecture including an s-CU 2542 and two s-DUs 2544, 2546. BS 2530 may have the same or similar structure in some embodiments.

[0209] 26 is a block diagram illustrating another example of a protocol stack for CP / UP splitting at a RAN node according to one embodiment. RAN feature based protocol stacks may be split into CU and DU, and such splitting may be applied anywhere from the PHY layer to the PDCP layer in some embodiments.

[0210] In the example 2600, the s-CU-CP protocol stack includes an s-RRC layer 2602 and an s-PDCP layer 2604, the s-CU-UP protocol stack includes an s-SDAP layer 2606 and an s-PDCP layer 2608, and the s-DU protocol stack includes an s-RLC layer 2610, an s-MAC layer 2612, and an s-PHY layer 2614. At least these protocol layers are described above as examples. E1 and F1 interfaces are also shown in FIG. 26 as examples, where the s-CU and s-DU in FIG. 26 indicate legacy CU and DU with SAF or SMAF, or / and sensing nodes with sensing capability.

[0211] The example in Figure 26 shows CU / DU splitting at the RLC layer, where the s-CU includes s-RRC and s-PDCP layers 2602, 2604 (for the control plane) and s-SDAP and s-PDCP layers 2606, 2608 (for the user plane), and the s-DU includes s-RLC, s-MAC, and s-PHY layers 2610, 2612, 2614. Not every RAN node necessarily includes a CU-CP (or s-CU-CP), but at least one RAN node may include one CU-UP (or s-CU-CP) and at least one DU (s-DU). One CU-CP (or s-CU-CP) may be able to connect to and control multiple RAN nodes with CU-UP (or s-CU-CP) and DU (or s-DU).

[0212] FIG. 27 shows a block diagram illustrating an example sensing application.

[0213] A service or application, such as Ultra Reliable Low Latency Communications (URLLC) or URLLC+, may configure parameters, such as time and frequency resources and / or transmission parameters, associated with or coupled to the service or application for a UE. In this scenario, the service configuration may relate to or be coupled to sensing configuration on the sensing planes, illustrated by way of example at 2710, including control plane 2714 and user plane 2712, and work together to achieve application requirements or improve performance, such as increasing reliability. Thus, configuration parameters, such as RRC configuration parameters, for a service may include one or more sensing parameters, such as sensing activity configuration, associated with the service.

[0214] URLLC or URLLC+ use cases or services, as shown by way of example at 2720 and 2730, may have different coupling configurations with the sensing plane. Non-integrated data (or user) plane, sensing plane, and control plane are shown at 2724, 2726, and 2728, and integrated data (or user) plane and control plane with integrated sensing are shown at 2732 and 2734. Similarly, enhanced mobile broadband (eMBB)+ services 2740 and eMBB+ services 2750 may include non-integrated data plane, sensing plane, and control plane 2744, 2746, and 2748, or integrated data plane and control plane with integrated sensing 2752 and 2754, and may have different configurations with the sensing plane. Another example application is massive machine type communications (mMTC)+ services 2760 and mMTC+ services 2770, which may have different configurations with the sensing plane, including non-integrated data plane, sensing plane, and control plane 2764, 2766, and 2768, or integrated data plane and control plane 2772 and 2774 with integrated sensing.

[0215] For example, industrial Internet of Things (IoT) applications in factories or autonomous driving industries require high reliability and extremely low latency. For example, autonomous driving networks can utilize online or real-time sensing information about, for example, road traffic load, environmental conditions in a network (e.g., urban areas) for safe and effective autonomous driving of automobiles. Consider using an example where the sensing architecture in the network is as shown in FIG. 15 (or any of FIG. 6A, FIG. 6B, or FIG. 6C) with the sensing configuration procedure shown in FIG. 16 (for any of FIG. 6A, FIG. 6B, or FIG. 6C, only the interaction between the message exchanges between SensMF and RAN / SAF is focused here, but the complete connection path between SensMF and RAN / SAF is provided above when describing each individual diagram and architecture).

[0216] The autonomous driving network may request sensing services from the wireless network having sensing capabilities at certain time intervals or all the time, and the sensing service request is sent via the sensing service center 1608 of the autonomous driving network (which may be an office in the autonomous driving network). Sent , to a SensMF 1606 associated with a wireless network including the RAN / SAF 1604. To obtain online or real-time sensing information regarding city traffic and road conditions, the sensing service center 1608 may send a sensing service request (SSR) message 1620 to the SensMF 1606 with specific sensing requirements, which in one embodiment may include a request for sensing vehicular traffic across the network by a specific set of sensing nodes at some specific locations (e.g., important roads). The SSR 1620 may be transmitted over an interface link.

[0217] The SensMF 1606 may adjust one or more RAN nodes and / or one or more UEs based on the SSR 1620. For example, the SensMF 1606 determines one or more RAN nodes for performing online or real-time sensing measurements based on the capabilities and services provided by the RAN nodes, and configures them to perform online or real-time sensing measurements through communicating configuration procedures with the one or more RAN nodes. After configuring or adjusting the one or more RAN nodes and / or one or more UEs, the SensMF 1606 sends the SSR 1622 to the NG RAN / SAF 104. For example, the SensMF 1606 may know more details in terms of sensing KPIs, such as measured vehicle mobility, direction, and frequency of sensing reports for each individual sensing node in the sensing area of ​​interest. The SSR 1622 may then be sent to the associated RAN node with the SAF (either directly in the architecture of FIG. 6C or indirectly via the core network in the architectures of FIG. 6A or FIG. 6B) to configure the associated sensing node for sensing operations and tasks.

[0218] For example, the SSR1622 can configure sensing tasks, sensing parameters, sensing resources, or other sensing configurations for online or real-time sensing measurements. One or more of It should be noted that one SensMF 1606 may address multiple RAN nodes with SAFs, and thus multiple SSRs 1622 may be sent accordingly. Each of these sensing nodes may be configured to measure KPIs in its respective vicinity, and the configuration interface may be, for example, an air interface where the configuration signaling may be an RRC message between the SensMF and the sensing node via a sensing specific protocol, which may include SensMF configuration sensing information. For example, the sensing protocol may be any one shown in Figures 23 and 24.

[0219] The RAN node / SAF 1604 performs sensing measurement procedures with one or more UEs 1602. For example, the RAN node can determine one or more UEs based on the UEs' capabilities, mobility, location, or services to perform online or real-time sensing measurements, and receive sensing measurement information or data from the associated UEs. The RAN node can send and share the sensing measurement information or data to the SAF, which can analyze and process the sensing measurement information or data, and forward the sensing measurement information or data to the SensMF 1606 or a sensing analysis report to the SensMF 1606 based on the requirements between the SAF and the SensMF 1606. In another option, each sensing node can send back measurement (e.g., KPI) information to its associated RAN node and SAF 1604 at configured time slots (e.g., duration, and periodic reports).

[0220] In one RAN node / SAF 1604, some or all of the sensing information (e.g., KPIs) from all associated sensing nodes may be collected (and optionally processed for RAN node local use in the SAF, e.g., local communication control) as SSResp 1626 and then sent to SensMF 1606. For example, SSResp 1626 may be any one of sensing measurement information, data, or analysis reports, and the sensing measurement information, data, or analysis reports from each sensing node may be forwarded to the SensMF by applying a sensing-specific protocol via a sensing-related information forwarding path of the control plane or user plane.

[0221] The SensMF 1606 may process the SSResp 1626 from all sensing nodes in the associated sensing RAN node, for example, summing, number averaging and smoothing, interpolation, other analysis methods, and create city maps with real-time vehicle traffic and road conditions for some city areas or streets of interest as the RRS 1628 to send to the sensing service center of the autonomous driving network for online traffic information. Such online and real-time sensing tasks may result in safe and effective automobile autonomous driving operations.

[0222] The above embodiment with sensing functionality may also be applied to other use cases or service cases.

[0223] URLLC solutions can be improved by including sensing features in some scenarios. For example, in the case of URLLC+, sensing information such as sudden movements, environmental changes, and network traffic congestion fluctuations can be of paramount importance for optimizing data transmission control, avoiding accidental events on the fly, and / or for collision control due to emergency situations.

[0224] These features and others may also or instead be applicable to other applications or services that would function in conjunction with sensing operations.

[0225] Various features and embodiments are described in detail above. Disclosed embodiments include, for example, a method including communicating a first signal by a first sensing coordinator in a radio access network with a second sensing coordinator via an interface link. Examples of the first and second sensing coordinators include not only the SAF and SensMF, but also other sensing components, including those in a UE or other electrical device, that may be included in a sensing procedure. For example, multiple sensing coordinators may also be implemented together, as in the SMAF embodiment, or instead.

[0226] The first sensing coordinator may implement or include a sensing protocol layer, and communicating the first signal may include communicating the first signal over an interface link using the sensing protocol. Various examples of sensing protocol stacks including sensing protocol layers that may be included in communicating signals between sensing coordinators are provided in Figures 22 through 26. Figure 23 provides a specific example of a sensing protocol layer in the form of an SMFRP layer 2312 in a RAN protocol stack 2310 that may be included in communicating signals between a first sensing coordinator in the RAN and a second sensing coordinator SensMF that may be located in a CN or in another network. Other examples of sensing protocol layers that may be included in communicating signals between sensing coordinators that may include one or more components in a UE or other device for sensing are shown in Figures 22 through 26.

[0227] The interface link may be or include any of various types of links. The air interface link for sensing may be, for example, between the RAN and the UE and / or a wireless backhaul, for example, between the SensMF and the RAN. New designs are also or instead provided for either or both of the control plane and user plane between the components involved in sensing.

[0228] For example, the interface link may be a uu air interface link between the first sensing coordinator and an electrical device, such as a UE or other device; an NR v2x, LTE-M / PC5, IEEE 802.154, and 802.11 air interface link between the first sensing coordinator and the electrical device; a sensing-specific air interface link between the first sensing coordinator and the electrical device; an NG interface link or a sensing interface link between the first sensing coordinator and a network entity of a core network or a backhaul network, including the examples shown in FIGS. 22 through 26 ; in some embodiments, an NG interface link or a sensing interface link between the first sensing coordinator and a network entity of a core network or a backhaul network in the example architectures shown in FIGS. 6A , 7A , 8A , 9A , 10A , or 11A . In some embodiments, the sensing control link and / or the sensing data link may be or include any one or more of a sensing control link and / or a sensing data link between the first sensing coordinator and a network entity outside the core network or the backhaul network in the example architectures shown in Figures 6B, 6C, 7B, 7C, 8B, 8C, 9B, 9C, 10B, 10C, 11B, or 11C.

[0229] These example interface links refer to sensing-specific air interface links. For example, FIG. 24 illustrates an embodiment in which the sensing-specific air interface link includes sensing-specific s-PHY, s-MAC, and s-RLC protocol layers. These sensing-specific protocol layers are distinct from traditional PHY, MAC, and RLC protocol layers, and any one or more of these sensing-specific protocol layers may be provided in some embodiments.

[0230] Various protocol stack embodiments are also disclosed. For example, the sensing coordinator may include a control plane stack for the sensing protocol, where the upper layers include one or both of s-PDCP and s-RRC, e.g., as in Figure 23, a user plane stack for the sensing protocol, where the upper layers include one or both of s-PDCP and s-SDAP, e.g., as in Figure 24, and any one or more of sensing-specific s-CU or s-DU, such as s-CU-CP, s-CU-UP, and s-DU, shown in Figures 25 and 26 as examples.

[0231] The first sensing coordinator may communicate signals with the second sensing coordinator in any of a variety of ways, which may depend on the implementation. For example, in some embodiments the first sensing coordinator is, includes, or implements a SAF in the radio access network and communicates signals with the second sensing coordinator in the form of a SensMF in the core network. This is consistent with the embodiments shown in, for example, Figures 6A, 7A, and 8A.

[0232] For example, in another embodiment consistent with Figures 6B, 7B, and 8B, the first sensing coordinator may be, include, or implement a SAF in the radio access network and communicate signals via the core network with a second sensing coordinator in the form of a SensMF outside the core network and the radio access network.

[0233] More direct communication is also possible, such as in the case of a first sensing coordinator with a SAF directly communicating signals with a SensMF as a second sensing coordinator outside the core network and radio access network. Examples are shown in Figures 6C, 7C, and 8C.

[0234] These examples of communication between sensing coordinators encompass Figures 6A to 8C. Figures 7A to 8C show CU / DU RAN node architectures. In such architectures, the first sensing coordinator may be, implement or include an SAF that connects to the CU and / or DU of the RAN. The SAF may communicate signals via the CU and / or DU with a SensMF in the core network as a second sensing coordinator, for example as in Figures 7A and 8A. The SAF may also or instead communicate signals between the CU and / or DU and a core network with a second sensing coordinator in the form of a SensMF outside the core network and radio access network, for example as in Figures 7B and 8B. Another possible option that may also or instead be provided is the SAF directly communicating signals via the CU and / or DU with a second sensing coordinator, such as a SensMF outside the core network and radio access network, as shown as an example in Figures 7C and 8C.

[0235] Considering more specific RAN node architecture details in Figures 8A to 8C, in these example architectures, a first sensing coordinator in the RAN may be, implement or include an SAF, which connects to a CU-CP, CU-UP and / or DU of the radio access network. In this context, the SAF may communicate signals with a second sensing coordinator in the form of a SensMF in the core network via the CU-CP, CU-UP and / or DU, as in Figure 8A. The SAF may also, or instead, communicate signals between the CU-CP, CU-UP and / or DU and a core network second sensing coordinator in the form of a SensMF, which is outside the core network and radio access network, as in Figure 8B. Figure 8C illustrates an embodiment in which the SAF may directly communicate signals with a second sensing coordinator, also in this example the SensMF, via the CU-CP, CU-UP and / or DU, which is outside the core network and radio access network.

[0236] The above communication examples are consistent with Figures 6A to 8C. Other examples consistent with Figures 9A to 11C and / or otherwise disclosed herein relate to embodiments in which the first sensing coordinator is, implements, or includes an SAF, and the second sensing coordinator is, implements, or includes a SensMF, and both the SAF and the SensMF are located in the radio access network. For example, in a SMAF embodiment, the sensing coordination is centralized in the radio access network. Other embodiments in which the SAF and SensMF, or features thereof, are implemented in the radio access network are also possible. The illustrative examples below are described in the context of the SAF and SensMF located in the RAN. These examples, and others herein, may be applied to SMAF embodiments and / or other embodiments in which the sensing coordination is centralized in the RAN.

[0237] In addition to the communication of the first signal between the RAN-based SAF and the SensMF, one or both of the SAF and the SensMF may communicate a second signal with an entity in the core network via the core network, for example, as in Figure 9A, Figure 10A, or Figure 11A. One or both of the SAF and the SensMF may also, or instead, communicate signals with an entity outside the core network and the radio access network via the core network, for example, as in Figure 9B, Figure 10B, or Figure 11B. Consistent with, but not limited to, the examples in Figures 9C, 10C, and 11C, one or both of the SAF and the SensMF in the RAN may directly communicate signals with an entity outside the core network and the radio access network.

[0238] In the context of the CU / DU RAN node architecture shown in Figures 10A-10C and 11A-11C as examples, one or both of the SAF and SensMF may connect to a CU and / or DU of a radio access network. The method may then include, for example, one or both of the SAF and SensMF communicating signals with entities in the core network via the CU and / or DU (e.g., see Figures 10A and 11A), with entities outside the core network and radio access network, between the CU and / or DU and the core network (e.g., see Figures 10B and 11B), and / or with entities outside the core network and radio access network directly via the CU and / or DU (e.g., see Figures 10C and 11C).

[0239] 11A-11C illustrate an example RAN node architecture in which one or both of the RAN-based SAF and SensMF may connect to a CU-CP, CU-UP, and / or DU of a radio access network. In this context, the method may include one or both of the SAF and SensMF communicating signals with entities in the core network via the CU-CP, CU-UP, and / or DU, e.g., in the architecture shown in FIG. 11A, with entities outside the core network and radio access network, e.g., in the architecture shown in FIG. 11B, between the CU-CP, CU-UP, and / or DU and the core network, and / or with entities outside the core network and radio access network, e.g., in the architecture shown in FIG. 11C, directly via the CU-CP, CU-UP, and / or DU.

[0240] Signals communicated to the sensing coordinator may include, for example, SSR, SSResp, and any other signaling related to sensing.

[0241] Consider Figure 13 as an example. At 1322, a signal is communicated by the first sensing coordinator in the RAN (SAF in the NG-RAN node 1304) via the AMF 1306 in the core network by sending an SSR to the second sensing coordinator (SensMF 1308).

[0242] Another example of communicating a signal by a first sensing coordinator in the RAN is shown at 1332 and includes receiving an SSResp by the SAF in the NG-RAN node 1304 from a second sensing coordinator (SensMF 1308) via the AMF 1306 in the core network. The SSResp is obtained based on the sensing data and the SSR. For example, in FIG. 13, the SSResp is forwarded from the SensMF 1308 by the AMF 1306 at 1332, and the SensMF obtains the SSResp based on the SSR received from the AMF at 1324, and then collects the data at 1326 and / or 1328. This means that the SSResp is a sensing result or output that is determined or otherwise obtained based on the SSR and the sensing data.

[0243] The SSR is a form of input and may include input information such as sensing models, parameters, and / or services, and the sensing data for output (SSResp) is collected from the sensing target. Thus, the sensing output is determined or otherwise obtained based on the sensing input, such as the SSR, and the sensing data.

[0244] With respect to sensing inputs, a sensing request such as an SSR that may be communicated (transmitted and / or received) by one or both of a first sensing coordinator in the RAN and a second coordinator that may or may not be located in the RAN may include information indicating one or more sensing requirements. Examples of sensing requirements that may be specified in a sensing request include positioning, mobility, environmental temperature, humidity, among others, of a communication device in a particular area. As also described at least one above, a sensing request may be triggered by one or more conditions. For example, one or both of a first sensing coordinator in the RAN and a second coordinator that may or may not be located in the RAN may communicate a sensing request such as an SSR that is triggered according to any one or more of: periodically and on demand. Triggering on demand may relate to or be expressed in terms of conditions that are semi-statically configured in some embodiments, for example based on an application and its sensing data requirements.

[0245] A sensing output such as an SSR does not necessarily have to be received by the same component or element that transmitted the SSR, or only by the same component or element. For example, as shown at 1432 in FIG. 14, communicating a signal by a first sensing coordinator in the RAN (in this example, the SAF at the NG-RAN node 1404) may include receiving a sensing response from a second sensing coordinator (SensMF 1408) via the AMF 1406, where the sensing response is obtained based on the SSR and the sensing data collected at 1424 and / or 1406. In this case, the SSR may have been transmitted by the sensing service center 1410 at 1420a, generated by the AMF 1406 at 1420b, or transmitted by the UE 1402 at 1420c, but the SAF at the NG-RAN node 1404 may receive the SSResp at 1432.

[0246] Sensing procedures for collecting sensing data from one or more sensing targets are shown, by way of example, at 1326, 1328 in FIG. 13 and 1424, 1426 in FIG. 14, as well as in other figures. These procedures may include configuration of one or more electrical devices for sensing, or the configuration may be treated separately. For example, one or both of a first sensing coordinator in the RAN and a second sensing coordinator, which may or may not be located in the RAN, may communicate with one or more electrical devices in the RAN to configure the one or more electrical devices with one or more sensing requirements. Such configuration may be based, for example, on a sensing request. The configured electrical devices may include, for example, one or more components or elements in the RAN, one or more UEs, and / or one or more sensing devices. Particular examples of electrical devices that may be configured with sensing requirements include sensing devices, UEs, drones, TRPs, and base stations. Other types of electrical devices in the radio access network may also or instead be configured with sensing requirements and / or otherwise included in sensing.

[0247] The method may include the first sensing coordinator processing a sensing response, the sensing response received from the second sensing coordinator via the AMF, obtained by the sensing data and the sensing request, as shown as SAF processing at 1334 in Figure 13 and 1434 in Figure 14, for example. Examples of SAF processing are provided elsewhere herein.

[0248] Communicating a signal by the first sensing coordinator in the RAN may also or instead include receiving, by the first sensing coordinator, the sensing request directly from the second sensing coordinator. This is shown as an example in FIG. 16 at 1622, where the SAF in the NG-RAN / SAF node 1604 receives the SSR directly from the SensMF 1606. The reception in this example is not via the AMF as in some of the examples above.

[0249] Another feature that may be provided in some embodiments is for a first sensing coordinator in the RAN to initiate a sensing procedure in the RAN in response to receiving the sensing request. Referring again to Figure 16, this is shown by way of example at 1624, where the UE sensing procedure is initiated by the SAF and NG-RAN / SAF node 1604 in response to receiving the SSR at 1622.

[0250] Communicating the signal may also or instead include, for example, sending a sensing response directly by the first sensing coordinator in the RAN to a second sensing coordinator in the core network, as shown at 1626 in FIG. 16, with the SSResp being sent by the SAF in the NG-RAN / SAF node 1604 to the SensMF 1606.

[0251] SMAF embodiments, and / or other embodiments, may centralize sensing coordination in the RAN. In such embodiments, the SMAF, or more generally one or both of a first sensing coordinator and a second sensing coordinator in the RAN, may provide or support any of a variety of features in the RAN. For example, the method may include one or both of the first and second sensing coordinators receiving a sensing request from an entity outside the core network and the radio access network via an AMF in the core network or directly. Receiving a sensing request via the AMF is shown by way of example at 1822 in FIG. 18, and receiving a sensing request directly is shown by way of example at 2020 and 2120 in FIG. 10 and FIG. 21, respectively.

[0252] The method may also, or alternatively, include a first sensing coordinator and Second One or both of the sensing coordinators may include initiating a sensing procedure in the RAN in response to receiving the sensing request. Examples are shown at 1824 in FIG. 18, 2022 in FIG. 20, and 2124 in FIG. 21.

[0253] One or both of the first sensing coordinator and the second sensing coordinator may also, or instead, send a sensing response via an AMF in the core network or directly to an entity outside the core network and the radio access network, as shown, for example, in 1826 for sending an SSResp via an AMF, and in 2024 in Figure 20 and 2126 in Figure 21 for sending an SSResp directly.

[0254] Some embodiments may include an acknowledgment of the sensing request. For example, one or both of the first sensing coordinator and the second sensing coordinator in the RAN may send an acknowledgment of the sensing request received from an entity outside the core network and the radio access network. Figure 21 shows an example at 2122, but it should be understood that such an acknowledgment is not limited to only the embodiment shown in Figure 21. The acknowledgment may be sent indirectly, for example, via the core network and / or by the AMF or other components or elements in the core network.

[0255] In some embodiments, the sensing is independent of communication service operations, such as cellular service operations, within a wireless communication network including a RAN in which at least the first sensing coordinator is located. The sensing may instead be combined or integrated with communication service operations. Independent or integrated sensing may provide, for example, background sensing, sensing for third party services, and / or sensing for machine learning or AI. Independent or integrated sensing may be applied to any of the various embodiments, including sensing via direct communication or via the core network by elements or functions such as the AMF and / or UPF, sensing via the SensMF and SAF, sensing via the SMAF, and other disclosed embodiments.

[0256] The present disclosure also encompasses a method that includes communicating, by a second sensing coordinator, a first signal with a first sensing coordinator in a radio access network over an interface link. In such an embodiment, the second sensing coordinator may implement or include a sensing protocol layer, and communicating the first signal may include communicating the first signal over the interface link using the sensing protocol.

[0257] Features disclosed herein in the context of other embodiments may also or instead be applied to embodiments relating to such a second sensing coordinator, including, for example, features disclosed above and / or elsewhere herein with reference to the first sensing coordinator.

[0258] Consider an interface link and sensing protocol through which the second sensing coordinator communicates a first signal with a first sensing coordinator in a radio access network. Example sensing protocols are provided elsewhere herein and may also or instead be applied in embodiments that focus on the second sensing coordinator.

[0259] An example interface link includes between the second sensing coordinator and the electrical device in the radio access network: uu Air Interface Link Air interface links of any one of the following types: NR v2x, LTE-M, PC5, IEEE 802.15.4, and IEEE 802.11 As an example, as shown in FIG. 24, a sensing-specific air interface link including one or more of s-PHY, s-MAC, and s-RLC protocol layers.

[0260] The interface link may be or include any of various types of links. The air interface link for sensing may be, for example, between the RAN and the UE and / or a wireless backhaul, for example, between the SensMF and the RAN. New designs may also or instead be provided for either or both of the control plane and user plane between the components involved in sensing.

[0261] Other example interface links include an NG interface link or sensing interface link between the sensing coordinator and a network entity of the core network or the backhaul network, including the examples shown in Figures 22 to 26, a sensing control link and / or a sensing data link between the sensing coordinator and a network entity of the core network or the backhaul network in the example architectures shown in Figures 6A, 7A, 8A, 9A, 10A, or 11A in some embodiments, and a sensing control link and / or a sensing data link between the sensing coordinator and a network entity outside the core network or the backhaul network in the example architectures shown in Figures 6B, 6C, 7B, 7C, 8B, 8C, 9B, 9C, 10B, 10C, 11B, or 11C in some embodiments.

[0262] Various protocol stack embodiments are also disclosed elsewhere in this specification, including a control plane stack for the sensing protocol where the upper layers include one or both of s-PDCP and s-RRC, e.g., as in FIG. 23, a user plane stack for the sensing protocol where the upper layers include one or both of s-PDCP and s-SDAP, e.g., as in FIG. 24, and a sensing-specific s-CU or s-DU, such as s-CU-CP, s-CU-UP, and s-DU, as shown, by way of example, in FIGS. 25 and 26.

[0263] The sensing coordinator may communicate signals in any of a variety of ways, which may depend on the implementation. SAF and SensMF embodiments with respect to the first sensing coordinator are disclosed at least above, and similar examples may apply to embodiments in terms of the second sensing coordinator, such as below. The second sensing coordinator is, includes, or implements a SensMF in the core network and communicates a first signal with a first sensing coordinator in the form of a SAF in the radio access network, e.g., consistent with the embodiments shown in Figures 6A, 7A, and 8A. The second sensing coordinator is a SensMF outside the core network and the radio access network, includes or implements it, and communicates the first signal with the first sensing coordinator, in particular a SAF in the radio access network, via the core network, e.g., consistent with Figures 6B, 7B, and 8B. The second sensing coordinator may be, include, or implement a SensMF outside the core network and the radio access network, and communicates the first signal directly with the first sensing coordinator in the form of a SAF in the radio access network, as shown, for example, in Figures 6C, 7C, and 8C. The second sensing coordinator may be, include or implement a SensMF in the core network, and the first sensing coordinator is in the form of a SAF in the radio access network and connects to a CU and / or DU of the radio access network, where the SensMF communicates a first signal with the SAF via the CU and / or DU, e.g., as shown in Figures 7A and 8A by way of example. Consistent with Figures 7B and 8B, for example, the second sensing coordinator may be, include, or implement a SensMF outside the core network and the radio access network, and a first sensing coordinator in the form of a SAF in the radio access network connects to a CU and / or DU of the radio access network, and the SensMF communicates the SAF and a first signal between the CU and / or DU and the core network. The second sensing coordinator may be, include or implement a SensMF outside the core network and the radio access network, and the first sensing coordinator in the form of a SAF in the radio access network connects to a CU and / or DU of the radio access network, and the SensMF directly communicates a first signal with the SAF via the CU and / or DU, as shown in Figures 7C and 8C for example. With the second sensing coordinator in the form of a SensMF in the radio access network and the first sensing coordinator in the form of a SAF connected to the CU-CP, CU-UP and / or DU of the radio access network, the following further embodiments are possible: the SensMF communicating the first signal with the SAF via the CU-CP, CU-UP and / or DU as shown by way of example in Fig. 8A, the SensMF communicating the first signal between the CU-CP, CU-UP and / or DU and the core network as shown by way of example in Fig. 8B, and the SensMF directly communicating the first signal with the SAF via the CU-CP, CU-UP and / or DU as shown by way of example in Fig. 8C.

[0264] As in other embodiments, signals communicated between sensing coordinators may include, for example, SSR, SSResp, and any other signaling related to sensing.

[0265] Consider Figure 13 as an example. At 1324, a signal is communicated by the sensing coordinator (SensMF 1308) by receiving the SSR via the AMF 1306 in the core network.

[0266] Another example of communicating a signal by the second sensing coordinator is shown at 1330 and includes sending an SSResp by the SensMF 1308 via the AMF 1306 in the core network. The SSResp is obtained based on the sensing data and the SSR. In FIG. 13, the SSR is forwarded by the AMF 1306 to the SensMF 1308 at 1324, and the SensMF obtains the SSResp based on the SSR received from the AMF, and then collects data at 1326 and / or 1328.

[0267] FIG. 14 shows at 1422, 1424 / 1426, and 1428 another example of receiving an SSR via an AMF, initiating a sensing procedure or otherwise obtaining an SSResp, and transmitting an SSResp via an AMF.

[0268] Communicating the signal may also or instead include, for example, sending a sensing request directly to the first sensing coordinator by the second sensing coordinator, as shown at 1622 in FIG. 16, and the SensMF 1606 sending the SSR directly to the SAF at the NG-RAN / SAF node 1604.

[0269] Another feature that may be provided in some embodiments is for the second sensing coordinator to initiate a sensing procedure in the RAN in response to receiving a sensing request, as shown by way of example at 1424, 1426 in FIG. 14 and 1624 in FIG. 16, where the sensing procedure is initiated by the SensMF in response to receiving an SSR, via the AMF (FIG. 14) or directly (FIG. 16).

[0270] The signal may also or alternatively be communicated to a sensing coordinator in the RAN, as shown, for example, at 1626 in FIG. fromThis may include directly receiving a sensing response, where the SSResp is sent by the SAF at the NG-RAN / SAF node 1604 and received by the SensMF 1606.

[0271] The method may include sending a sensing request directly to the sensing coordinator from an entity outside the core network and the radio access network, as shown by way of example at 2020 in FIG. 20 and 2120 in FIG. 21, receiving a sensing response directly from the sensing coordinator to such entity, as shown by way of example at 2024 in FIG. 20 and 2126 in FIG. 21, and / or receiving an acknowledgment of the sensing request sent by such entity directly from the sensing coordinator, by such entity, as shown by way of example at 2122 in FIG. 21.

[0272] As in other embodiments, the sensing coordinator may communicate a sensing request including information indicative of one or more sensing requirements, such as positioning, mobility, environmental temperature, and / or humidity of a communication device within a particular area, and the sensing request may be triggered according to one or more of: periodically and in response to a desire related to or expressed by conditions configured based on the application and its sensing data requirements.

[0273] Another feature that may be provided in some embodiments includes a sensing coordinator, which may be located outside the RAN, communicating with one or more electrical devices within the RAN to configure the one or more electrical devices with sensing requirements.

[0274] Embodiments relating to sensing devices or nodes, such as UEs or other electrical devices in the RAN, are also possible.

[0275] According to one such embodiment, the method includes accessing, by a device over a wireless access network, an interface link, and communicating, by the device, a first signal with a sensing coordinator having a sensing protocol layer, the communicating including communicating the first signal over the interface link using the sensing protocol, the first signal including a sensing configuration or sensing data.

[0276] At least some example interface links disclosed elsewhere herein are applicable to sensing device or sensing node embodiments that include at least a uu air interface link, an air interface link of any one of the following types: NR v2x, LTE-M, PC5, IEEE 802.15.4, and IEEE 802.11, a sensing-specific air interface link including one or more of sensing-specific s-PHY, s-MAC, and s-RLC protocol layers, a sensing control link, and a sensing data link. Examples of all of these types of links are provided elsewhere herein.

[0277] In the sensing device method, communicating may include receiving a first signal from a sensing coordinator that includes a sensing configuration. The sensing configuration may be provided in a signal communicated to the sensing device, for example, during initial access and / or when a sensing procedure is initiated.

[0278] The sensing device method also includes operations such as collecting sensing data based on the sensing configuration and transmitting the sensing data to a sensing coordinator during the sensing procedure, as shown, for example, in Figures 13, 14, 16, 18, 20, and 21.

[0279] In some embodiments, communicating includes transmitting a first signal including the sensing data to the sensing coordinator.

[0280] The sensing coordinator to which the sensing devices communicate signals may be located within the RAN, as shown for example as the UE sensing procedure in Figures 16, 18, 20, and 21, or outside the RAN, as shown for example as the NG-RAN node and UE sensing procedure in Figures 13 and 14.

[0281] The above exemplary method is illustrative of an embodiment, and other embodiments are possible. For example, the method may also or instead include communicating a first signaling with a sensing coordinator that coordinates a sensing procedure for an access network, such as a RAN that provides access to a core network in a wireless communication system. The first signaling is associated with a sensing request for the sensing procedure to be performed in the access network. Such a method may also include communicating a second signaling with the sensing coordinator, the second signaling being associated with a sensing response providing a result of the sensing procedure.

[0282] From the perspective of a service requester, such as the UE 1402, the AMF 1406, or the sensing service center 1410 in Figure 14, communicating such first signaling may include sending the first signaling to a sensing coordinator, which in this example is sending an SSR to the SensMF 1408. An example of communicating second signaling associated with a response is also shown in Figure 14 and includes receiving second signaling (SSResp) from the sensing coordinator (SensMF 1408).

[0283] These examples of communicating signaling, and others herein, may, but need not, include direct communication. For example, in FIG. 14, communicating signaling may include "relaying" such signaling by the AMF and / or one or more other intermediate components. For example, the method may include relaying the first signaling by the AMF 1406 to the sensing service center 1410 or the UE 140 before transmitting the first signaling to the sensing coordinator, which is the SensMF 1408 in this particular example. 2 or 14 , after receiving the second signaling from the sensing coordinator, the method may also or alternatively include transmitting a sensing response to the requester, for example by the AMF 1406 in FIG.

[0284] Looking at the SensMF 1408 in FIG. 14 as an example, the sensing coordinator receives the request, coordinates the sensing, and returns the results. Communicating the first signaling by the sensing coordinator from the perspective of the SensMF 1408 may include receiving the first signaling by the sensing coordinator at 1422, and communicating the second signaling may include sending the second signaling by the sensing coordinator at 1428. The method may also include coordinating, within the access network, performance of the sensing procedure by the sensing coordinator at 1424 and / or 1426.

[0285] From the perspective of a sensing target or device, which may be a UE 1402 and / or an NG-RAN node 1404 in the example shown in Figure 14, the method may include performing a sensing procedure. The sensing procedure may include one or both of an access node sensing procedure, shown by way of example at 1424, and an access terminal sensing procedure, shown by way of example at 1426. Examples of sensing procedures from which sensing data may be collected are provided elsewhere herein.

[0286] Although the sensing procedures referenced above will be implemented in the access network, a sensing coordinator such as a SensMF may be deployed in the core network to which the access network provides access. A sensing coordinator such as a SensMF may instead be deployed outside the core network and configured to communicate with the access network via the core network, or configured to communicate with the access network via an interface to the access network. Various examples of these types of sensing architectures are disclosed herein.

[0287] The disclosed architecture also includes examples where the sensing coordinator is deployed in the access network. Then, communicating the first signaling associated with the sensing request and communicating the second signaling associated with the response may include communicating with the sensing coordinator via a core network, for example, as in Figure 18. Figures 20 and 21 show direct communication where communicating the first signaling associated with the sensing request and communicating the second signaling associated with the response includes communicating with the sensing coordinator via an interface to the access network.

[0288] Although these examples of communicating first and second signaling refer to particular drawings, features disclosed in these examples may also or instead be implemented in other embodiments.

[0289] Some figures, such as Figures 6C, 7C, 8C, 9C, 10C, and 11C, show architectures that provide direct communication with a sensing coordinator in an access network, or at least communication that is more direct than communication via a core network. In the context of such architectures, and possibly others, a method may include communicating signaling between an access system and a sensing requester outside the core network, associated with a sensing procedure to be performed in an access network that provides access to a core network in a wireless communication system. In embodiments that are referred to herein primarily as direct communication embodiments, such communicating may include communicating signaling between the access system and the sensing requester via an access network interface that bypasses the core network.

[0290] Features disclosed elsewhere herein may be implemented in embodiments that include communicating over an access network interface that bypasses the core network. For example, the signaling may be or include the above-referenced first signaling associated with a sensing request for a sensing procedure, and a second signaling associated with a sensing response for providing a result of the sensing procedure. Communicating such signaling as in other embodiments may include transmitting the first signaling to the access network and / or receiving the second signaling from the access network. The method may also or instead include communicating such signaling by receiving the first signaling at the access network and / or transmitting the second signaling from the access network.

[0291] Additional features that are disclosed in other embodiments or that may alternatively be applied to the direct communication embodiment include, among others: performing a sensing procedure in the access network; The sensing procedure may be or include one or both of an access node sensing procedure and an access terminal sensing procedure.

[0292] The present disclosure encompasses these and other methods.

[0293] The embodiments may also or instead be implemented in other forms including, for example, apparatus and non-transitory computer-readable storage media.

[0294] A non-transitory computer-readable storage medium may store, for example, programming for execution by a processor. Such a storage medium may include a computer program product or may be implemented within an apparatus that also includes at least one processor coupled to the storage medium.

[0295] Examples of processors 210, 260, 276 and storage media in the form of memories 208, 258, 278 are also shown in FIG. 3. Thus, an apparatus embodiment may include an ED, shown by way of example at 110 in FIG. 3, a T-TRP, shown by way of example at 170 in FIG. 3, and / or an NT-TRP, shown by way of example at 172 in FIG. 3. In some embodiments, the apparatus may include other components, such as a communication interface to which the processor is coupled. The communication interface may include elements such as those shown by way of example at 201 / 203 / 204, 252 / 254 / 256, and / or 272 / 274 / 280 in FIG. 3. These are illustrative examples of apparatus, and other apparatus embodiments are possible.

[0296] In one embodiment, whether implemented as a computer program product or in an apparatus, the programming stored in the computer-readable storage medium may include instructions for communicating, by a first sensing coordinator in a radio access network, a first signal with a second sensing coordinator over an interface link, the first sensing coordinator including or implementing a sensing protocol layer, and communicating the first signal including communicating the first signal over the interface link using the sensing protocol.

[0297] Features disclosed elsewhere herein may be implemented in such apparatus and / or computer program product embodiments, including, for example, any of the following, either alone or in various combinations: The interface link is or includes one or more of the following: a uu air interface link between the first sensing coordinator and the electrical device, a uu air interface link between the first sensing coordinator and the electrical device of the following types: NR v2x, LTE-M, PC5, IEEE 802.15.4, and IEEE 802.11, a sensing-specific air interface link between the first sensing coordinator and the electrical device, the sensing-specific air interface link including one or more of s-PHY, s-MAC, and s-RLC protocol layers, an NG interface link between the first sensing coordinator and a network entity of the core network or the backhaul network, a sensing control link between the first sensing coordinator and a network entity of the core network or the backhaul network, a sensing data link between the first sensing coordinator and a network entity of the core network or the backhaul network, a sensing control link between the first sensing coordinator and a network entity outside the core network or the backhaul network, and a sensing data link between the first sensing coordinator and a network entity outside the core network or the backhaul network. The first sensing coordinator includes or provides one or more of the following: a control plane stack for a sensing protocol, the upper layer of which includes one or both of an s-PDCP layer and an s-RRC layer, a user plane stack for a sensing protocol, the upper layer of which includes one or both of an s-PDCP layer and an s-SDAP layer, an s-CU-CP for the sensing protocol, an s-CU-UP for the sensing protocol, an s-DU for the sensing protocol. The first sensing coordinator that communicates the first signal with the second sensing coordinator includes one or more of the following: the first sensing coordinator includes a SAF in the radio access network and communicates the first signal with the second sensing coordinator that includes a SensMF in the core network; the first sensing coordinator includes a SAF in the radio access network and communicates the first signal via the core network with the second sensing coordinator that includes a SensMF outside the core network and the radio access network; the first sensing coordinator includes a SAF in the radio access network and communicates the first signal directly with the second sensing coordinator that includes a SensMF outside the core network and the radio access network. The first sensing coordinator includes an SAF in a radio access network, the SAF connects to a CU and / or DU of the radio access network, and the SAF communicates a first signal with a second sensing coordinator including a SensMF in a core network via the CU and / or DU. The first sensing coordinator includes an SAF in a radio access network, the SAF connects to a CU and / or DU of the radio access network, and the SAF communicates a first signal with a second sensing coordinator including a SensMF outside the core network and the radio access network between the CU and / or DU and the core network. The first sensing coordinator includes an SAF in a radio access network, the SAF connects to a CU and / or DU of the radio access network, and the SAF communicates a first signal directly with a second sensing coordinator including a SensMF outside the core network and the radio access network via the CU and / or DU. The first sensing coordinator includes an SAF in a radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a DU of the radio access network, and the SAF communicates a first signal with a second sensing coordinator including a SensMF in a core network via the CU-CP, CU-UP, and / or DU.The first sensing coordinator includes an SAF in a radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a DU of the radio access network, and the SAF communicates a first signal with a second sensing coordinator including a SensMF outside the core network and the radio access network between the CU-CP, the CU-UP, and / or the DU and the core network. The first sensing coordinator includes an SAF in a radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a DU of the radio access network, and the SAF communicates a first signal directly with a second sensing coordinator including a SensMF outside the core network and the radio access network via the CU-CP, the CU-UP, and / or the DU. The first sensing coordinator includes a SAF and the second sensing coordinator includes a SensMF, both the SAF and the SensMF located in the radio access network, and the programming further includes instructions for any one or more of the following: one or both of the SAF and the SensMF communicating the second signal with an entity in the core network via the core network, one or both of the SAF and the SensMF communicating the second signal with an entity outside the core network and the radio access network via the core network, one or both of the SAF and the SensMF directly communicating the second signal with an entity outside the core network and the radio access network, one or both of the SAF and the SensMF communicating the second signal with a CU and / or a SensMF of the radio access network. D.U.and communicating the second signal with an entity in the core network via the CU and / or DU. One or both of the SAF and SensMF connect to a CU and / or DU of the radio access network and communicate a second signal with an entity outside the core network and the radio access network between the CU and / or DU and the core network. One or both of the SAF and SensMF connect to a CU and / or DU of the radio access network and communicate a second signal directly with an entity outside the core network and the radio access network via the CU and / or DU. One or both of the SAF and SensMF connect to a CU-CP, CU-UP, and / or DU of the radio access network and communicate a second signal with an entity in the core network via the CU-CP, CU-UP, and / or DU. One or both of the SAF and SensMF connect to a CU-CP, CU-UP, and / or DU of the radio access network and communicate a second signal with an entity outside the core network and the radio access network between the CU-CP, CU-UP, and / or DU and the core network. One or both of the SAF and SensMF connect to a CU-CP, CU-UP, and / or DU of the radio access network and communicate a second signal with an entity outside the core network and the radio access network directly via the CU-CP, CU-UP, and / or DU. The programming further includes instructions for at least one of the following: communicating includes transmitting, by the first sensing coordinator, the SSR to the second sensing coordinator via the AMF in the core network; communicating includes receiving, by the first sensing coordinator, the SSResp from the second sensing coordinator via the AMF in the core network, the SSResp obtained based on the sensing data and the SSR; processing, by the first sensing coordinator, the SSResp received from the second sensing coordinator via the AMF, the SSResp obtained based on the sensing data and the sensing request; communicating includes receiving, by the first sensing coordinator, the SSR directly from the second sensing coordinator; and initiating, by the first sensing coordinator, a sensing procedure in the radio access network in response to receiving the SSR. The communicating includes sending, by the first sensing coordinator, the SSResp directly to a second sensing coordinator in the core network. One or both of the first sensing coordinator and the second sensing coordinator receiving the SSR from an entity outside the core network and the radio access network via an AMF in the core network or directly. Second One or both of the sensing coordinators initiating a sensing procedure in the radio access network in response to receiving the SSR. One or both of the first sensing coordinator and the second sensing coordinator sending an SSResp to an entity outside the core network and the radio access network via an AMF in the core network or directly. One or both of the first sensing coordinator and the second sensing coordinator sending an acknowledgment of the received SSR from the entity outside the core network and the radio access network to the entity. The sensing is independent of communication service operations in a wireless communication network, including a radio access network. Sensing is integrated with communication service operations in wireless communication networks, including radio access networks. The programming includes instructions for one or both of the first sensing coordinator and the second sensing coordinator to communicate a sensing request that includes information indicating one or more of the following sensing requirements: positioning of a communication device within a particular area, mobility, environmental temperature, and humidity. The programming includes instructions for one or both of the first sensing coordinator and the second sensing coordinator to communicate sensing requests that are triggered periodically and according to one or more of a desire related to or expressed by conditions configured based on the application and its sensing data requirements. The programming includes instructions for one or both of the first sensing coordinator and the second sensing coordinator to communicate with one or more electrical devices in the wireless access network to configure the one or more electrical devices with sensing requirements. The one or more electrical devices may include a sensing device, a UE, a drone, a TRP, a base station, or another electrical device in a radio access network. The apparatus includes a network device in a radio access network that is configured to control one or more other network devices in the radio access network.

[0298] In another embodiment, the programming stored in the computer-readable storage medium may include instructions for communicating, by a second sensing coordinator, a first signal with a first sensing coordinator in the radio access network over an interface link, the second sensing coordinator including or implementing a sensing protocol layer, and communicating the first signal includes communicating the first signal over the interface link using the sensing protocol.

[0299] Features disclosed elsewhere herein may be implemented in such apparatus and / or computer program product embodiments, including, for example, any of the following, either alone or in various combinations: The interface link includes one or more of the following: a uu air interface link between the second sensing coordinator and the electrical device, a uu air interface link between the second sensing coordinator and the electrical device of the following types: NR v2x, LTE-M, PC5, IEEE 802.15.4, and IEEE 802.11, a sensing-specific air interface link between the second sensing coordinator and the electrical device or UE, the sensing-specific air interface link including one or more of s-PHY, s-MAC, and s-RLC protocol layers, an NG interface link between the second sensing coordinator and a network entity of the core network or the backhaul network, a sensing control link between the second sensing coordinator and a network entity of the core network or the backhaul network, a sensing data link between the second sensing coordinator and a network entity of the core network or the backhaul network, a sensing control link between the second sensing coordinator and a network entity outside the core network or the backhaul network, a sensing data link between the second sensing coordinator and a network entity outside the core network or the backhaul network. The second sensing coordinator includes one or more of the following: a control plane stack for a sensing protocol whose upper layers include one or both of an s-PDCP layer and an s-RRC layer, a user plane stack for a sensing protocol whose upper layers include one or both of an s-PDCP layer and an s-SDAP layer, an s-CU-CP for the sensing protocol, an s-CU-UP for the sensing protocol, and an s-DU for the sensing protocol. The second sensing coordinator communicating the first signal with the first sensing coordinator includes one or more of the following: the second sensing coordinator includes a SensMF in the core network and communicates the first signal with the first sensing coordinator including the SAF in the radio access network; the second sensing coordinator includes a SensMF outside the core network and the radio access network and communicates the first signal via the core network with the first sensing coordinator including the SAF in the radio access network; the second sensing coordinator includes a SensMF outside the core network and the radio access network and communicates the first signal directly with the first sensing coordinator including the SAF in the radio access network. The second sensing coordinator includes a SensMF in the core network, and the first sensing coordinator includes a SAF in the radio access network, the SAF connects to a CU and / or DU of the radio access network, and the SensMF communicates the first signal with the SAF via the CU and / or DU. The second sensing coordinator includes a SensMF outside the core network and the radio access network, and the first sensing coordinator includes a SAF in the radio access network, the SAF connects to a CU and / or DU of the radio access network, and the SensMF communicates the first signal with the SAF between the CU and / or DU and the core network. The second sensing coordinator includes a SensMF outside the core network and the radio access network, and the first sensing coordinator includes a SAF in the radio access network, the SAF connects to a CU and / or DU of the radio access network, and the SensMF communicates the first signal directly with the SAF via the CU and / or DU.The second sensing coordinator includes a SensMF in the core network, and the first sensing coordinator includes a SAF in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a DU of the radio access network, and the SensMF communicates the first signal with the SAF via the CU-CP, the CU-UP, and / or the DU. The second sensing coordinator includes a SensMF outside the core network and the radio access network, and the first sensing coordinator includes a SAF in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a DU of the radio access network, and the SensMF communicates the first signal with the SAF between the CU-CP, the CU-UP, and / or the DU and the core network. The second sensing coordinator includes a SensMF outside the core network and the radio access network, and the first sensing coordinator includes a SAF in the radio access network, the SAF connects to a CU-CP, CU-UP, and / or DU of the radio access network, and the SensMF directly communicates a first signal with the SAF via the CU-CP, CU-UP, and / or DU. The programming further includes instructions for at least one of the following: the communicating includes receiving, by the second sensing coordinator, an SSR from the first sensing coordinator via the AMF in the core network; the communicating includes sending, by the second sensing coordinator, an SSResp to the first sensing coordinator via the AMF in the core network, the SSResp obtained based on the sensing data and the SSR; the second sensing coordinator obtaining the SSResp based on the sensing data and the sensing request; the communicating includes sending, by the second sensing coordinator, the SSR directly to the first sensing coordinator; the second sensing coordinator initiating a sensing procedure in the radio access network in response to receiving the SSR. The communicating includes receiving an SSResp directly from the first sensing coordinator by the second sensing coordinator; sending an SSR from an entity outside the core network and radio access network directly to one or both of the first sensing coordinator and the second sensing coordinator; receiving an SSResp to an entity outside the core network and radio access network directly from one or both of the first sensing coordinator and the second sensing coordinator; and receiving an acknowledgment of the SSR sent by the entity by the entity outside the core network and radio access network directly from one or both of the first sensing coordinator and the second sensing coordinator. The sensing is independent of communication service operations in a wireless communication network, including a radio access network. Sensing is integrated with communication service operations in wireless communication networks, including radio access networks. The programming includes instructions for the second sensing coordinator to communicate a sensing request including information indicating any one or more of the following sensing requirements: positioning of a communication device within a particular area, mobility, environmental temperature, and humidity. The programming includes instructions for the second sensing coordinator to communicate sensing requests that are triggered according to one or more of: periodically and in response to a desire related to or represented by conditions configured based on the application and its sensing data requirements. The programming includes instructions for a second sensing coordinator to communicate with one or more electrical devices in the wireless access network to configure the one or more electrical devices with sensing requirements.

[0300] In another embodiment, the programming stored on the computer-readable storage medium may include instructions for accessing, by an apparatus over a wireless access network, an interface link, and communicating, by the apparatus, a first signal with a sensing coordinator having a sensing protocol layer, the communicating including communicating the first signal over the interface link using the sensing protocol, the first signal including a sensing configuration or sensing data.

[0301] Features disclosed elsewhere herein may be implemented in apparatus and / or computer program product embodiments, including, for example, the following, either alone or in various combinations: The interface link is or includes any one or more of the following: a uu air interface link, an air interface link of any one of the following types: NR v2x, LTE-M, PC5, IEEE 802.15.4, and IEEE 802.11, a sensing specific air interface link including one or more of s-PHY, s-MAC, and s-RLC protocol layers, a sensing control link, a sensing data link. The communicating includes receiving a first signal from a sensing coordinator, the first signal including the sensing configuration. The programming further includes instructions for collecting sensing data based on the sensing configuration and transmitting the sensing data to a sensing coordinator. The communicating includes transmitting a first signal including the sensing data to the sensing coordinator. The sensing coordinator is located in the wireless access network. The sensing coordinator is located outside the radio access network. The sensing coordinator includes, for example, a SAF, a SensMF, or both within a SMAF. The sensing is independent of the communication service operation of the devices in the radio access network. The sensing is integrated with the communication service operations of the devices in the radio access network.

[0302] What has been described is merely illustrative of the application of the principles of the presently disclosed embodiments. Other arrangements and methods can be implemented by those skilled in the art.

[0303] For example, although combinations of features are shown in exemplary embodiments, not all of them need to be combined to realize the benefits of various embodiments of the present disclosure. In other words, a system or method designed in accordance with an embodiment of the present disclosure does not necessarily include all of the features shown in any one of the figures, or all of the portions shown generally in the figures. Furthermore, selected features of one exemplary embodiment can be combined with selected features of other exemplary embodiments.

[0304] While the present disclosure has been described with reference to exemplary embodiments, this description is not intended to be construed in a limiting sense. Various modifications and combinations of the exemplary embodiments, as well as other embodiments of the present disclosure, will be apparent to those skilled in the art upon reference to the description. Therefore, the appended claims are intended to cover any such modifications or embodiments.

[0305] Although aspects of the invention have been described with reference to specific features and embodiments thereof, various modifications and combinations can be made thereto without departing from the invention. Thus, the description and drawings should be considered as merely illustrative of some embodiments of the invention as defined by the appended claims, and it is intended to encompass any and all modifications, variations, combinations, or equivalents that fall within the scope of the invention. Thus, while embodiments and potential advantages have been described in detail, various changes, substitutions, and alterations can be made herein without departing from the invention as defined by the appended claims. Moreover, the scope of this application is not intended to be limited to the particular embodiments of the processes, machines, manufactures, compositions of matter, means, methods, and steps described herein. As one skilled in the art will readily appreciate from this disclosure of the invention, any process, machine, manufacture, composition of matter, means, method, or step now existing or later developed that performs substantially the same function or achieves substantially the same result as the corresponding embodiments described herein may be utilized in accordance with the present invention. Thus, it is intended that the appended claims include within their scope such processes, machines, manufactures, compositions of matter, means, methods, or steps.

[0306] Moreover, although described primarily in the context of methods and apparatus, other implementations are also contemplated, such as, for example, instructions stored on a non-transitory computer-readable medium, such medium being capable of storing programming or instructions for performing any of the various methods consistent with the present disclosure.

[0307] Additionally, any module, component, or device illustrated herein that executes instructions may be implemented using information such as computer-readable or processor-readable instructions, data structures, program modules, and / or other data. One or moreThe non-transitory computer-readable or processor-readable storage medium may include or otherwise have access to a non-transitory computer-readable or processor-readable storage medium. A non-exhaustive list of examples of non-transitory computer-readable or processor-readable storage media includes magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, optical disks such as compact disk read-only memory (CD-ROM), digital video disks or digital versatile disks (DVD), Blu-ray Disks™, or other storage, volatile and non-volatile, removable and non-removable media implemented in any manner or technology, random access memory (RAM), read-only memory (ROM), electronically erasable programmable read-only memory (EEPROM), flash memory, or other memory technology. Any such non-transitory computer-readable or processor-readable storage medium may be part of the device or accessible or connectable thereto. The applications or modules described herein may be readable and executable by a computer or processor and may be implemented using instructions that may be stored or otherwise held by such non-transitory computer-readable or processor-readable storage media.

Claims

1. communicating, by a first sensing coordinator in a radio access network, a first signal with a second sensing coordinator over an interface link; The method, wherein the first sensing coordinator comprises a sensing protocol layer, and the step of communicating the first signal comprises the step of communicating the first signal over the interface link using the sensing protocol.

2. The interface link includes: a uu air interface link between the first sensing coordinator and an electrical device; The following types of sensing protocols are supported: New Wireless Vehicle-to-Anything (NR v2x), Long Term Evolution Machine Type Communication (LTE-M), Power Class 5 (PC5), Institute of Electrical and Electronics Engineers (IEEE) 802 (IEEE) 802.11b, between the first sensing coordinator and the electrical device: an air interface link of any one of IEEE 802.15.4 and IEEE 802.11; a sensing-specific air interface link between the first sensing coordinator and an electrical device, the sensing-specific air interface link comprising one or more of a sensing-specific physical (s-PHY) protocol layer, a sensing-specific medium access control (s-MAC) protocol layer, and a sensing-specific radio link control (s-RLC) protocol layer; a next generation (NG) interface link between the first sensing coordinator and a network entity of a core network or a backhaul network; a sensing control link between the first sensing coordinator and a network entity of a core network or a backhaul network; a sensing data link between the first sensing coordinator and a network entity of a core network or a backhaul network; a sensing control link between the first sensing coordinator and a network entity outside a core network or a backhaul network; a sensing data link between the first sensing coordinator and a network entity outside a core network or a backhaul network; The method of claim 1 , comprising one or more of:

3. The first sensing coordinator a control plane stack for the sensing protocol, the upper layer comprising one or both of a sensing-specific packet data convergence protocol (s-PDCP) layer and a sensing-specific radio resource control (s-RRC) layer; a user plane stack for the sensing protocol, the upper layer comprising one or both of an s-PDCP layer and a sensing specific Service Data Adaptation Protocol (s-SDAP) layer; a sensing specific central unit control plane (s-CU-CP) for said sensing protocol; a sensing specific CU-UP for the sensing protocol; and a sensing specific distributed unit (s-DU) for said sensing protocol; The method of claim 1 or claim 2, comprising one or more of:

4. The first sensing coordinator communicating the first signal with the second sensing coordinator includes: The first sensing coordinator communicates the first signal with the second sensing coordinator, the second sensing coordinator comprising a sensing agent function (SAF) in the radio access network and a sensing management function (SensMF) in a core network. The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network and communicates the first signal with the second sensing coordinator comprising a core network and a sensing management function (SensMF) outside the radio access network; The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network and communicates the first signal directly with the second sensing coordinator comprising a core network and a sensing management function (SensMF) outside the radio access network; The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SAF communicates the first signal with a second sensing coordinator comprising a sensing management function (SensMF) in the core network via the CU and / or the DU. The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SAF communicates the first signal between the CU and / or DU and the core network with a second sensing coordinator comprising a sensing management function (SensMF) outside the core network and the radio access network; The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SAF directly communicates the first signal with the second sensing coordinator comprising a sensing management function (SensMF) outside the core network and the radio access network via the CU and / or DU. The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a control unit (CU-CP), a control unit (CU-UP), and / or a distributed unit (DU) of the radio access network, and the SAF communicates the first signal with the second sensing coordinator comprising a sensing management function (SensMF) in a core network via the CU-CP, the CU-UP, and / or the DU. The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and the SAF communicates the first signal between the CU-CP, the CU-UP, and / or the DU and a core network with the second sensing coordinator comprising a sensing management function (SensMF) outside the core network and the radio access network; and The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and the SAF directly communicates the first signal with the second sensing coordinator comprising a sensing management function (SensMF) outside the core network and the radio access network via the CU-CP, the CU-UP, and / or the DU.

4. The method of claim 1 , further comprising one or more of the following:

5. The first sensing coordinator comprises a sensing agent function (SAF), and the second sensing coordinator comprises a sensing management function (SensMF), both the SAF and the SensMF being located within the radio access network, and the method comprises: one or both of the SAF and the SensMF communicating a second signal via a core network with an entity in the core network; one or both of the SAF and the SensMF communicating the second signal via a core network with an entity external to the core network and the radio access network; one or both of the SAF and the SensMF directly communicating the second signal with an entity external to a core network and the radio access network; one or both of the SAF and the SensMF connecting to a central unit (CU) and / or a distributed unit (DU) of the radio access network and communicating the second signal with an entity in a core network via the CU and / or DU; one or both of the SAF and the SensMF connect to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and communicate the second signal between the CU and / or DU and a core network with an entity outside the core network and the radio access network; one or both of the SAF and the SensMF connect to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and communicate the second signal directly with an entity outside a core network and the radio access network via the CU and / or DU; one or both of the SAF and the SensMF connect to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and communicate the second signal with an entity in a core network via the CU-CP, CU-UP, and / or DU; one or both of the SAF and the SensMF connect to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and communicate the second signal between the CU-CP, the CU-UP, and / or the DU and a core network with an entity outside the core network and the radio access network; one or both of the SAF and the SensMF connect to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and directly communicate the second signal with an entity outside a core network and the radio access network via the CU-CP, CU-UP, and / or DU; The method of claim 1 , further comprising one or more of the following:

6. The method comprises the steps of: The communicating step includes sending, by the first sensing coordinator, a sensing request (SSR) to the second sensing coordinator via an Access and Mobility Management Function (AMF) in a core network. The communicating step includes receiving, by the first sensing coordinator, a sensing response (SSResp) from the second sensing coordinator via an AMF in a core network, and the sensing response (SSResp) is obtained based on the sensing data and the SSR. The first sensing coordinator processes a sensing response (SSResp) received from the second sensing coordinator via an AMF, where the sensing response (SSResp) is obtained based on sensing data and a sensing request; the step of communicating includes the step of receiving, by the first sensing coordinator, a sensing request (SSR) directly from the second sensing coordinator; the first sensing coordinator initiating a sensing procedure in the radio access network in response to receiving a sensing request (SSR); the communicating step includes a step of directly transmitting, by the first sensing coordinator, a sensing response (SSResp) to the second sensing coordinator in a core network; one or both of the first sensing coordinator and the second sensing coordinator receiving a sensing request (SSR) from an entity outside the core network and the radio access network via an AMF in the core network or directly; one or both of the first sensing coordinator and the sensing coordinator initiating a sensing procedure in the radio access network in response to receiving a sensing request (SSR); one or both of the first sensing coordinator and the second sensing coordinator sending a sensing response (SSResp) to an entity external to the core network and the radio access network via an AMF of a core network or directly; one or both of the first sensing coordinator and the second sensing coordinator sending, to an entity external to a core network and the radio access network, an acknowledgment of a sensing request (SSR) received from the entity; The method of claim 1 , further comprising at least one of:

7. The method according to any one of claims 1 to 6, wherein sensing is independent of communication service operation in a wireless communication network comprising said radio access network.

8. The method of any one of claims 1 to 6, wherein sensing is integrated with communication service operations in a wireless communication network comprising the radio access network.

9. One or both of the first sensing coordinator and the second sensing coordinator are configured to satisfy the following sensing requirements: Positioning of communication devices within a specific area, mobility, environmental temperature, and humidity 9. The method of claim 1, further comprising communicating a sensing request including information indicative of one or more of:

10. One or both of the first sensing coordinator and the second sensing coordinator Periodically, In response to requirements related to or expressed under conditions that are based on the application and its sensing data requirements, 10. The method of claim 1, further comprising communicating a sensing request triggered by one or more of:

11. 11. The method of claim 1, further comprising: one or both of the first sensing coordinator and the second sensing coordinator communicating with one or more electrical devices in the radio access network to configure the one or more electrical devices with sensing requirements.

12. 12. The method of claim 11, wherein the one or more electrical devices include a sensing device, a user equipment (UE), a drone, a transmit / receive point (TRP), a base station, or other electrical device in the radio access network.

13. The method according to any one of claims 1 to 12, wherein the first sensing coordinator is implemented in a network device in the radio access network and configured to control one or more other network devices in the radio access network.

14. At least one processor; a non-transitory computer-readable storage medium coupled to the at least one processor and storing programming for execution by the at least one processor, the programming including instructions for communicating, by a first sensing coordinator in a radio access network, a first signal with a second sensing coordinator over an interface link; An apparatus comprising: The apparatus, wherein the first sensing coordinator comprises a sensing protocol layer, and communicating the first signal comprises communicating the first signal over the interface link using the sensing protocol.

15. The interface link includes: a uu air interface link between the first sensing coordinator and an electrical device; The following types of sensing protocols are supported: New Wireless Vehicle-to-Anything (NR v2x), Long Term Evolution Machine Type Communication (LTE-M), Power Class 5 (PC5), Institute of Electrical and Electronics Engineers (IEEE) 802 (IEEE) 802.11b, between the first sensing coordinator and the electrical device: an air interface link of any one of IEEE 802.15.4 and IEEE 802.11; a sensing-specific air interface link between the first sensing coordinator and an electrical device, the sensing-specific air interface link comprising one or more of a sensing-specific physical (s-PHY) protocol layer, a sensing-specific medium access control (s-MAC) protocol layer, and a sensing-specific radio link control (s-RLC) protocol layer; a next generation (NG) interface link between the first sensing coordinator and a network entity of a core network or a backhaul network; a sensing control link between the first sensing coordinator and a network entity of a core network or a backhaul network; a sensing data link between the first sensing coordinator and a network entity of a core network or a backhaul network; a sensing control link between the first sensing coordinator and a network entity outside a core network or a backhaul network; a sensing data link between the first sensing coordinator and a network entity outside a core network or a backhaul network; 15. The apparatus of claim 14, comprising one or more of:

16. The first sensing coordinator a control plane stack for the sensing protocol, the upper layer comprising one or both of a sensing-specific packet data convergence protocol (s-PDCP) layer and a sensing-specific radio resource control (s-RRC) layer; a user plane stack for the sensing protocol, the upper layer comprising one or both of an s-PDCP layer and a sensing specific Service Data Adaptation Protocol (s-SDAP) layer; a sensing specific central unit control plane (s-CU-CP) for said sensing protocol; a sensing specific CU-UP for the sensing protocol; and a sensing specific distributed unit (s-DU) for said sensing protocol; 16. Apparatus according to claim 14 or claim 15, comprising one or more of:

17. The first sensing coordinator in the radio access network that communicates the first signal with the second sensing coordinator is configured to: The first sensing coordinator communicates the first signal with the second sensing coordinator, the second sensing coordinator comprising a sensing agent function (SAF) in the radio access network and a sensing management function (SensMF) in a core network. The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network and communicates the first signal with the second sensing coordinator comprising a core network and a sensing management function (SensMF) outside the radio access network; The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network and communicates the first signal directly with the second sensing coordinator comprising a core network and a sensing management function (SensMF) outside the radio access network; The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SAF communicates the first signal with the second sensing coordinator comprising a sensing management function (SensMF) in the core network via the CU and / or the DU. The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SAF communicates the first signal between the CU and / or DU and the core network with the second sensing coordinator comprising a sensing management function (SensMF) outside the core network and the radio access network. The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SAF directly communicates the first signal with the second sensing coordinator comprising a sensing management function (SensMF) outside the core network and the radio access network via the CU and / or DU. The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU control plane (CP), a CU user plane (UP), and / or a distributed unit (DU) of the radio access network, and the SAF communicates the first signal with the second sensing coordinator comprising a sensing management function (SensMF) in a core network via the CU-CP, CU-UP, and / or DU. The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and the SAF communicates the first signal between the CU-CP, the CU-UP, and / or the DU and a core network with the second sensing coordinator comprising a sensing management function (SensMF) outside the core network and the radio access network; and The first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and the SAF directly communicates the first signal with the second sensing coordinator comprising a sensing management function (SensMF) outside the core network and the radio access network via the CU-CP, CU-UP, and / or DU; 17. Apparatus according to any one of claims 14 to 16, comprising one or more of:

18. The first sensing coordinator comprises a sensing agent function (SAF) and the second sensing coordinator comprises a sensing management function (SensMF), both the SAF and the SensMF being located within the radio access network, and the programming includes: one or both of the SAF and the SensMF communicating a second signal via a core network with an entity in the core network; one or both of the SAF and the SensMF communicating the second signal via a core network with an entity external to the core network and the radio access network; one or both of the SAF and the SensMF directly communicating the second signal with an entity external to a core network and the radio access network; one or both of the SAF and the SensMF connect to a Central Unit (CU) and / or a Distributed Unit (DU) of the radio access network, and communicate the second signal with an entity in a core network via the CU and / or DU; one or both of the SAF and the SensMF connect to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and communicate the second signal between the CU and / or DU and a core network with an entity outside the core network and the radio access network; one or both of the SAF and the SensMF connect to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and communicate the second signal directly with an entity outside a core network and the radio access network via the CU and / or DU; one or both of the SAF and the SensMF connect to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and communicate the second signal with an entity in a core network via the CU-CP, CU-UP, and / or DU; one or both of the SAF and the SensMF connect to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and communicate the second signal between the CU-CP, the CU-UP, and / or the DU and a core network with an entity outside the core network and the radio access network; one or both of the SAF and the SensMF connect to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and communicate the second signal directly with an entity outside a core network and the radio access network via the CU-CP, CU-UP, and / or DU; 18. Apparatus according to any one of claims 14 to 17, further comprising instructions for any one or more of:

19. The programming includes: The communicating includes sending, by the first sensing coordinator, a sensing request (SSR) to the second sensing coordinator via an access and mobility management function (AMF) in a core network. The communicating includes receiving, by the first sensing coordinator, a sensing response (SSResp) from the second sensing coordinator via an AMF in a core network, the sensing response (SSResp) being obtained based on the sensing data and the SSR. The first sensing coordinator processes a sensing response (SSResp) received from the second sensing coordinator via an AMF, and the sensing response (SSResp) is obtained based on sensing data and a sensing request; and wherein the communicating includes receiving, by the first sensing coordinator, a sensing request (SSR) directly from the second sensing coordinator. the first sensing coordinator initiating a sensing procedure in the radio access network in response to receiving a sensing request (SSR); The communicating includes sending, by the first sensing coordinator, a sensing response (SSResp) directly to the second sensing coordinator in a core network; and One or both of the first sensing coordinator and the second sensing coordinator receive a sensing request (SSR) from an entity outside the core network and the radio access network via an AMF in the core network or directly; initiating a sensing procedure in the radio access network, in response to receiving a sensing request (SSR), one or both of the first sensing coordinator and the sensing coordinator; one or both of the first sensing coordinator and the second sensing coordinator sending a sensing response (SSResp) to an entity outside the core network and the radio access network via an AMF of a core network or directly; one or both of the first sensing coordinator and the second sensing coordinator sending, to an entity outside the core network and the radio access network, an acknowledgment of a sensing request (SSR) received from the entity; 19. The apparatus of claim 14, further comprising instructions for at least one of:

20. 20. The apparatus of any one of claims 14 to 19, wherein sensing is independent of communication service operation in a wireless communication network comprising the radio access network.

21. 20. The apparatus of any one of claims 14 to 19, wherein sensing is integrated with communication service operations in a wireless communication network comprising the radio access network.

22. The programming comprises: One or both of the first sensing coordinator and the second sensing coordinator are configured to satisfy the following sensing requirements: Positioning of communication devices within a specific area, mobility, environmental temperature, and humidity 22. The apparatus of claim 14, further comprising instructions for communicating a sensing request including information indicative of one or more of:

23. The programming comprises: One or both of the first sensing coordinator and the second sensing coordinator Periodically, In response to requirements related to or expressed under conditions that are based on the application and its sensing data requirements, 23. The apparatus of claim 14, further comprising instructions for communicating a sensing request triggered by one or more of:

24. The programming comprises:

24. The apparatus of claim 14, wherein one or both of the first sensing coordinator and the second sensing coordinator include instructions for communicating with one or more electrical devices in the radio access network to configure the one or more electrical devices with sensing requirements.

25. 25. The apparatus of claim 24, wherein the one or more electrical devices include a sensing device, a user equipment (UE), a drone, a transmit / receive point (TRP), a base station, or other electrical device in the radio access network.

26. 26. The apparatus of any one of claims 14 to 25, comprising a network device in the radio access network configured to control one or more other network devices in the radio access network.

27. 1. A computer program product comprising a non-transitory computer-readable storage medium storing programming for execution by a processor, the programming comprising: Communicating a first signal with a second sensing coordinator over an interface link by a first sensing coordinator in the radio access network. Including instructions for The first sensing coordinator comprises a sensing protocol layer, and communicating the first signal comprises communicating the first signal over the interface link using the sensing protocol.

28. communicating, by a second sensing coordinator, via an interface link, a first signal with a first sensing coordinator in the radio access network; The method, wherein the second sensing coordinator comprises a sensing protocol layer, and the step of communicating the first signal comprises the step of communicating the first signal over the interface link using the sensing protocol.

29. The interface link includes: a uu air interface link between the second sensing coordinator and an electrical device; The following types of sensing protocols are supported: New Wireless Vehicle-to-Anything (NR v2x), Long Term Evolution Machine Type Communication (LTE-M), Power Class 5 (PC5), Institute of Electrical and Electronics Engineers (IEEE) 802 (IEEE) 802.11b, between the second sensing coordinator and the electrical device: an air interface link of any one of IEEE 802.15.4 and IEEE 802.11; a sensing-specific air interface link between the second sensing coordinator and the electrical device, the sensing-specific air interface link comprising one or more of a sensing-specific physical (s-PHY) protocol layer, a sensing-specific medium access control (s-MAC) protocol layer, and a sensing-specific radio link control (s-RLC) protocol layer; a next generation (NG) interface link between the second sensing coordinator and a network entity of a core network or a backhaul network; a sensing control link between the second sensing coordinator and a network entity of a core network or a backhaul network; a sensing data link between the second sensing coordinator and a network entity of a core network or a backhaul network; a sensing control link between the second sensing coordinator and a network entity outside a core network or a backhaul network; a sensing data link between the second sensing coordinator and a network entity outside a core network or a backhaul network; 30. The method of claim 28 comprising one or more of:

30. The second sensing coordinator a control plane stack for the sensing protocol, the upper layer comprising one or both of a sensing-specific packet data convergence protocol (s-PDCP) layer and a sensing-specific radio resource control (s-RRC) layer; a user plane stack for the sensing protocol, the upper layer comprising one or both of an s-PDCP layer and a sensing specific Service Data Adaptation Protocol (s-SDAP) layer; a sensing specific central unit control plane (s-CU-CP) for said sensing protocol; a sensing specific CU-UP for the sensing protocol; and a sensing specific distributed unit (s-DU) for said sensing protocol; 30. The method of claim 28 or claim 29, comprising one or more of:

31. The second sensing coordinator, which communicates the first signal with the first sensing coordinator, The second sensing coordinator comprises a sensing management function (SensMF) in a core network and communicates the first signal with the first sensing coordinator comprising a sensing agent function (SAF) in the radio access network; The second sensing coordinator comprises a sensing management function (SensMF) outside a core network and the radio access network, and communicates the first signal with the first sensing coordinator comprising a sensing agent function (SAF) in the radio access network via the core network; The second sensing coordinator comprises a sensing management function (SensMF) outside a core network and the radio access network, and directly communicates the first signal with the first sensing coordinator comprising a sensing agent function (SAF) within the radio access network; The second sensing coordinator comprises a sensing management function (SensMF) in the core network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SensMF communicates the first signal with the SAF via the CU and / or DU; The second sensing coordinator comprises a sensing management function (SensMF) outside the core network and the radio access network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SensMF communicates the first signal with the SAF between the CU and / or DU and the core network. The second sensing coordinator comprises a sensing management function (SensMF) outside the core network and the radio access network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SensMF directly communicates the first signal with the SAF via the CU and / or DU. The second sensing coordinator comprises a sensing management function (SensMF) in a core network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-Control Plane (CU-CP), a CU-User Plane (CU-UP), and / or a Distributed Unit (DU) of the radio access network, and the SensMF communicates the first signal with the SAF via the CU-CP, the CU-UP, and / or the DU; The second sensing coordinator comprises a sensing management function (SensMF) outside the core network and the radio access network, the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and the SensMF communicates the first signal with the SAF between the CU-CP, the CU-UP, and / or the DU and the core network; and The second sensing coordinator comprises a sensing management function (SensMF) outside the core network and the radio access network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and the SensMF directly communicates the first signal with the SAF via the CU-CP, the CU-UP, and / or the DU; 31. The method of any one of claims 28 to 30, comprising one or more of:

32. The method comprises the steps of: The step of communicating includes receiving, by the second sensing coordinator, a sensing request (SSR) from the first sensing coordinator via an access and mobility management function (AMF) of a core network. The communicating step includes a step of sending a sensing response (SSResp) by the second sensing coordinator to the first sensing coordinator via an AMF in a core network, and the sensing response (SSResp) is obtained based on the sensing data and the SSR. The second sensing coordinator obtains a sensing response (SSResp) based on the sensing data and the sensing request. the step of communicating includes the step of directly transmitting a sensing request (SSR) by the second sensing coordinator to the first sensing coordinator; the second sensing coordinator initiating a sensing procedure in the radio access network in response to receiving a sensing request (SSR); The step of communicating includes a step of receiving, by the second sensing coordinator, a sensing response (SSResp) directly from the first sensing coordinator; and sending a sensing request (SSR) from an entity external to a core network and the radio access network directly to one or both of the first sensing coordinator and the second sensing coordinator; receiving a sensing response (SSResp) directly from one or both of the first sensing coordinator and the second sensing coordinator to an entity external to a core network and the radio access network; receiving, by an entity external to a core network and the radio access network, an acknowledgement of a sensing request (SSR) sent by the entity directly from one or both of the first sensing coordinator and the second sensing coordinator; 32. The method of any one of claims 28 to 31, further comprising at least one of:

33. 33. The method of any one of claims 28 to 32, wherein sensing is independent of communication service operation in a wireless communication network comprising the radio access network.

34. 33. The method of any one of claims 28 to 32, wherein sensing is integrated with communication service operations in a wireless communication network comprising the radio access network.

35. The second sensing coordinator determines the following sensing requirements: Positioning of communication devices within a specific area, mobility, environmental temperature, and humidity 35. The method of claim 28, further comprising communicating a sensing request including information indicative of one or more of:

36. The second sensing coordinator, Periodically, In response to requirements related to or expressed under conditions that are based on the application and its sensing data requirements, 36. The method of claim 28, further comprising communicating a sensing request triggered by one or more of:

37. 37. The method of any one of claims 28 to 36, comprising the second sensing coordinator in communication with one or more electrical devices in the radio access network to configure the one or more electrical devices with sensing requirements.

38. At least one processor; a non-transitory computer-readable storage medium coupled to the at least one processor and storing programming for execution by the at least one processor, the programming including instructions for communicating, by a second sensing coordinator, a first signal over an interface link with a first sensing coordinator in a radio access network; An apparatus comprising: The apparatus, wherein the second sensing coordinator comprises a sensing protocol layer, and communicating the first signal comprises communicating the first signal over the interface link using the sensing protocol.

39. The interface link includes: a uu air interface link between the second sensing coordinator and an electrical device; The following types of sensing protocols are supported: New Wireless Vehicle-to-Anything (NR v2x), Long Term Evolution Machine Type Communication (LTE-M), Power Class 5 (PC5), Institute of Electrical and Electronics Engineers (IEEE) 802 (IEEE) 802.11b, between the second sensing coordinator and the electrical device: an air interface link of any one of IEEE 802.15.4 and IEEE 802.11; a sensing-specific air interface link between the second sensing coordinator and an electrical device or UE, the sensing-specific air interface link comprising one or more of a sensing-specific physical (s-PHY) protocol layer, a sensing-specific medium access control (s-MAC) protocol layer, and a sensing-specific radio link control (s-RLC) protocol layer; a next generation (NG) interface link between the second sensing coordinator and a network entity of a core network or a backhaul network; a sensing control link between the second sensing coordinator and a network entity of a core network or a backhaul network; a sensing data link between the second sensing coordinator and a network entity of a core network or a backhaul network; a sensing control link between the second sensing coordinator and a network entity outside a core network or a backhaul network; a sensing data link between the second sensing coordinator and a network entity outside a core network or a backhaul network; 40. The apparatus of claim 38, comprising one or more of:

40. The second sensing coordinator a control plane stack for the sensing protocol, the upper layer comprising one or both of a sensing-specific packet data convergence protocol (s-PDCP) layer and a sensing-specific radio resource control (s-RRC) layer; a user plane stack for the sensing protocol, the upper layer comprising one or both of an s-PDCP layer and a sensing specific Service Data Adaptation Protocol (s-SDAP) layer; a sensing specific central unit control plane (s-CU-CP) for said sensing protocol; a sensing specific CU-UP for the sensing protocol; and a sensing specific distributed unit (s-DU) for said sensing protocol; 40. Apparatus according to claim 38 or claim 39, comprising one or more of:

41. The second sensing coordinator, which communicates the first signal with the first sensing coordinator, The second sensing coordinator comprises a sensing management function (SensMF) in a core network and communicates the first signal with the first sensing coordinator comprising a sensing agent function (SAF) in the radio access network; The second sensing coordinator comprises a sensing management function (SensMF) outside a core network and the radio access network, and communicates the first signal with the first sensing coordinator comprising a sensing agent function (SAF) in the radio access network via the core network; The second sensing coordinator comprises a sensing management function (SensMF) outside a core network and the radio access network, and directly communicates the first signal with the first sensing coordinator comprising a sensing agent function (SAF) within the radio access network; The second sensing coordinator comprises a sensing management function (SensMF) in the core network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SensMF communicates the first signal with the SAF via the CU and / or DU; The second sensing coordinator comprises a sensing management function (SensMF) outside the core network and the radio access network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SensMF communicates the first signal with the SAF between the CU and / or DU and the core network. The second sensing coordinator comprises a sensing management function (SensMF) outside the core network and the radio access network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a central unit (CU) and / or a distributed unit (DU) of the radio access network, and the SensMF directly communicates the first signal with the SAF via the CU and / or DU. The second sensing coordinator comprises a sensing management function (SensMF) in a core network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-Control Plane (CU-CP), a CU-User Plane (CU-UP), and / or a Distributed Unit (DU) of the radio access network, and the SensMF communicates the first signal with the SAF via the CU-CP, the CU-UP, and / or the DU; The second sensing coordinator comprises a sensing management function (SensMF) outside the core network and the radio access network, the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and the SensMF communicates the first signal with the SAF between the CU-CP, the CU-UP, and / or the DU and the core network; and The second sensing coordinator comprises a sensing management function (SensMF) outside the core network and the radio access network, and the first sensing coordinator comprises a sensing agent function (SAF) in the radio access network, the SAF connects to a CU-CP, a CU-UP, and / or a distributed unit (DU) of the radio access network, and the SensMF directly communicates the first signal with the SAF via the CU-CP, the CU-UP, and / or the DU; 41. Apparatus according to any one of claims 38 to 40, comprising one or more of:

42. The programming includes: The communicating includes receiving, by the second sensing coordinator, a sensing request (SSR) from the first sensing coordinator via an access and mobility management function (AMF) of a core network. The communicating includes sending, by the second sensing coordinator, a sensing response (SSResp) to the first sensing coordinator via an AMF in a core network, the sensing response (SSResp) being obtained based on the sensing data and the SSR. The second sensing coordinator obtains a sensing response (SSResp) based on the sensing data and the sensing request. and communicating with the second sensing coordinator by transmitting a sensing request (SSR) directly to the first sensing coordinator. the second sensing coordinator initiating a sensing procedure in the radio access network in response to receiving a sensing request (SSR); The communicating includes receiving, by the second sensing coordinator, a sensing response (SSResp) directly from the first sensing coordinator; and sending a sensing request (SSR) from an entity external to a core network and the radio access network directly to one or both of the first sensing coordinator and the second sensing coordinator; receiving a sensing response (SSResp) directly from one or both of the first sensing coordinator and the second sensing coordinator to an entity external to a core network and the radio access network; receiving, by an entity external to a core network and the radio access network, an acknowledgement of a sensing request (SSR) sent by the entity directly from one or both of the first sensing coordinator and the second sensing coordinator; 42. The apparatus of any one of claims 38 to 41, further comprising instructions for at least one of:

43. 43. The apparatus of any one of claims 38 to 42, wherein sensing is independent of communication services operation in a wireless communication network comprising the radio access network.

44. 43. The apparatus of any one of claims 38 to 42, wherein sensing is integrated with communication service operations in a wireless communication network comprising the radio access network.

45. The programming comprises: The second sensing coordinator determines the following sensing requirements: Positioning of communication devices within a specific area, mobility, environmental temperature, and humidity 45. The apparatus of claim 38, further comprising instructions for communicating a sensing request including information indicative of one or more of:

46. The programming comprises: The second sensing coordinator, Periodically, In response to requirements related to or expressed under conditions that are based on the application and its sensing data requirements, 46. ​​The apparatus of claim 38, further comprising instructions for communicating a sensing request triggered by one or more of:

47. The programming comprises:

47. The apparatus of any one of claims 38 to 46, wherein the second sensing coordinator comprises instructions for communicating with one or more electrical devices in the radio access network to configure the one or more electrical devices with sensing requirements.

48. 1. A computer program product comprising a non-transitory computer-readable storage medium storing programming for execution by a processor, the programming comprising: communicating a first signal by the second sensing coordinator over an interface link with a first sensing coordinator in the radio access network; Including instructions for the second sensing coordinator comprises a sensing protocol layer, and communicating the first signal comprises communicating the first signal over the interface link using the sensing protocol.

49. accessing an interface link via a wireless access network by a device; communicating, by the device, a first signal with a sensing coordinator having a sensing protocol layer; wherein the communicating step includes communicating the first signal over the interface link using a sensing protocol, the first signal including a sensing configuration or sensing data.

50. The interface link includes: a uu air interface link; The following types are available: New Radio Vehicle-to-Anything (NR v2x), Long Term Evolution Machine Type Communications (LTE-M), Power Class 5 (PC5), and Institute of Electrical and Electronics Engineers (IEEE) 802. an air interface link of any one of IEEE 802.15.4 and IEEE 802.11; a sensing-specific air interface link comprising one or more of a sensing-specific physical (s-PHY) protocol layer, a sensing-specific medium access control (s-MAC) protocol layer, and a sensing-specific radio link control (s-RLC) protocol layer; a sensing control link; A sensing data link; 50. The method of claim 49 comprising any one or more of:

51. 51. The method of claim 49 or claim 50, wherein the communicating step comprises receiving the first signal including the sensing configuration from the sensing coordinator.

52. collecting the sensing data based on the sensing configuration; transmitting the sensing data to the sensing coordinator; 52. The method of claim 51, further comprising:

53. 51. The method of claim 49 or claim 50, wherein the communicating step includes the step of transmitting the first signal including the sensing data to the sensing coordinator.

54. 54. The method of any one of claims 49 to 53, wherein the sensing coordinator is located within the radio access network.

55. 54. The method of any one of claims 49 to 53, wherein the sensing coordinator is located outside the radio access network.

56. 56. The method of any one of claims 49 to 55, wherein the sensing coordinator comprises one or both of a sensing agent function (SAF) and a sensing management function (SensMF).

57. 57. A method according to any one of claims 49 to 56, wherein sensing is independent of communication service operation of the device in the radio access network.

58. 57. A method according to any one of claims 49 to 56, wherein sensing is integrated with communication service operation of the device in the radio access network.

59. At least one processor; a non-transitory computer-readable storage medium coupled to the at least one processor and storing programming for execution by the at least one processor, the programming comprising: accessing an interface link via a wireless access network by said device; and communicating a first signal with a sensing coordinator having a sensing protocol layer by the device; and wherein said communicating includes communicating the first signal over the interface link using a sensing protocol, the first signal including a sensing configuration or sensing data.

60. The interface link includes: a uu air interface link; The following types are available: New Radio Vehicle-to-Anything (NR v2x), Long Term Evolution Machine Type Communications (LTE-M), Power Class 5 (PC5), and Institute of Electrical and Electronics Engineers (IEEE) 802. an air interface link of any one of IEEE 802.15.4 and IEEE 802.11; a sensing-specific air interface link comprising one or more of a sensing-specific physical (s-PHY) protocol layer, a sensing-specific medium access control (s-MAC) protocol layer, and a sensing-specific radio link control (s-RLC) protocol layer; a sensing control link; Sensing data link and 60. The apparatus of claim 59, comprising any one or more of:

61. 61. The apparatus of claim 59 or claim 60, wherein the communicating comprises receiving the first signal including the sensing configuration from the sensing coordinator.

62. The programming comprises: collecting the sensing data based on the sensing configuration; and Transmitting the sensing data to the sensing coordinator.

62. The apparatus of claim 61, further comprising instructions for:

63. 61. The apparatus of claim 59 or claim 60, wherein the communicating comprises transmitting the first signal including the sensing data to the sensing coordinator.

64. 64. The apparatus of any one of claims 59 to 63, wherein the sensing coordinator is located within the radio access network.

65. 64. The apparatus of any one of claims 59 to 63, wherein the sensing coordinator is located outside the radio access network.

66. 66. The apparatus of any one of claims 59 to 65, wherein the sensing coordinator comprises one or both of a sensing agent function (SAF) and a sensing management function (SensMF).

67. 67. The apparatus of any one of claims 59 to 66, wherein sensing is independent of communication service operation of the apparatus in the radio access network.

68. 67. The apparatus of any one of claims 59 to 66, wherein sensing is integrated with communication service operation of the apparatus in the radio access network.

69. 1. A computer program product comprising a non-transitory computer-readable storage medium storing programming for execution by a processor, the programming comprising: accessing an interface link via a wireless access network by the device; and communicating a first signal with a sensing coordinator having a sensing protocol layer by the device; and wherein the communicating includes communicating the first signal over the interface link using a sensing protocol, the first signal including a sensing configuration or sensing data.

Images