AWARE TASK ALLOCATION TO UEs

Abstract

Aspects of the present disclosure relate to apparatuses and methods for aware task allocation to user equipment (UE). In one aspect, a first apparatus obtains a first state of a UE. The first state of the UE comprises a connection state of the UE or an energy state of the UE. The first device determines, based at least on the first state of the UE, first perception capability information of the UE for allocating a perception task to the UE.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically, to apparatus, methods, and computer-readable media for assigning sensing tasks to user equipment (UE). Background Technology

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

[0003] Wireless sensing technology aims to acquire information about remote objects or their environment and characteristics without physical contact. Several studies and solutions exist regarding how communication technologies such as LTE, NR, and WLAN can be utilized for sensing. Enhancing cellular wireless communication systems by incorporating wireless sensing technologies is being discussed by the 3rd Generation Partnership Project (3GPP). However, how to improve the allocation of sensing tasks to UEs still requires further investigation. Summary of the Invention

[0004] This disclosure relates to apparatus and methods for allocating sensing tasks to a UE. The apparatus and methods can improve the allocation of sensing tasks to the UE by taking into account sensing capability information associated with the UE's connectivity or energy state.

[0005] Some implementations of the first device described herein may include: at least one memory; and at least one processor coupled to the at least one memory and configured such that the first device: acquires a first state of a user equipment (UE), the first state of the UE including a connection state or an energy state of the UE; and determines first sensing capability information of the UE based at least on the first state of the UE for assigning sensing tasks to the UE.

[0006] In some implementations of the first device, the first device for obtaining the first state of the UE includes: receiving a sensing message from a second device; providing a request for the first state to the second device, a third device, or the UE based on the sensing message; and obtaining a response including the first state from the second device, the third device, or the UE.

[0007] In some implementations of the first device, the request indicates whether the UE's connection management (CM) state or the UE's radio resource control (RRC) state is being requested.

[0008] In some implementations of the first device, a request is made to instruct the second device, the third device, or the UE to provide an updated first state based on an update of the first state.

[0009] In some implementations of the first device, the sensing message further includes: a first state set of the UE and a second sensing capability information set of the UE, each sensing capability information in the sensing capability information being associated with a state in the state, and the first state set including a connection state set of the UE or an energy state set of the UE; and the first device for determining the first sensing capability information includes: determining the first sensing capability information based on the first state, the first state set and the second sensing capability information set.

[0010] In some implementations of the first device, the second sensing capability information set includes one of the following: at least one indicator, each of which indicates whether the UE supports sensing in a state; at least one sensing capability parameter; at least one index of at least one set of sensing capability parameters; or at least one index of at least one sensing capability.

[0011] In some implementations of the first device, the UE's connection state includes the UE's connection management (CM) state or the UE's radio resource control (RRC) connection state, and the UE's energy state includes the UE's battery level or the UE's power mode.

[0012] In some implementations of the first device, the first device includes a sensing function (SF), the second device includes an access and mobility management function (AMF), and the third device includes a network data analysis function (NWDAF).

[0013] Some implementations of the second device described herein may include: at least one memory; and at least one processor coupled to the at least one memory and configured such that the second device: receives a first message; determines, based on the first message, a first state of the UE to be provided to the first device, the first state of the UE including a connection state or an energy state of the UE; and provides the first state of the UE to the first device for assigning a sensing task to the UE.

[0014] In some implementations of the second device, receiving the first message includes receiving a sensing message from the UE.

[0015] In some implementations of the second device, receiving the first message includes receiving a request for a first state from the first device.

[0016] In some implementations of the second device, receiving the first message by the second device includes receiving an indication from the UE that instructs the second device to provide the first device with the first state of the UE.

[0017] In some implementations of the second device, the request indicates whether the UE's connection management (CM) state or the UE's radio resource control (RRC) connection state is being requested.

[0018] In some implementations of the second device, a request instructs the second device to provide a first state based on an update of the first state; and wherein the second device that provides the first state of the UE to the first device includes: providing an updated first state to the first device based on determining that the first state has been updated.

[0019] In some implementations of the second device, the sensing message also includes: a first state set of the UE and a second sensing capability information set of the UE, each sensing capability information in the sensing capability information is associated with a state in the state, and the first state set includes the UE's connection state set or the UE's energy state set.

[0020] In some implementations of the second device, the second sensing capability information set includes one of the following: at least one indicator, each of which indicates whether the UE supports sensing in a state; at least one sensing capability parameter; at least one index of at least one set of sensing capability parameters; or at least one index of at least one sensing capability.

[0021] In some implementations of the second device, the UE's connection state includes the UE's connection management (CM) state or the UE's radio resource control (RRC) connection state, and the UE's energy state includes the UE's battery level or the UE's power mode.

[0022] In some implementations of the second device, the first device includes a sensing function (SF), and the second device includes an access and mobility management function (AMF).

[0023] Some implementations of the methods described herein may include: obtaining a first state of a user equipment (UE), the first state of the UE including the UE's connection state or the UE's energy state; and determining, at least based on the first state of the UE, first sensing capability information of the UE for assigning sensing tasks to the UE.

[0024] Some implementations of the method described herein may include: receiving a first message; determining, based on the first message, a first state of the UE to be provided to a first device, the first state of the UE including the connection state of the UE or the energy state of the UE; and providing the first state of the UE to the first device for allocating sensing tasks to the UE.

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

[0026] Figure 1A An example of a wireless communication system that assigns sensing tasks to a UE in accordance with various aspects of this disclosure is illustrated.

[0027] Figure 1B The illustration shows a schematic diagram of a wireless network architecture with sensing capabilities according to various aspects of this disclosure;

[0028] Figure 2 The diagram illustrates a flowchart of a method for allocating sensing tasks to a UE in accordance with various aspects of this disclosure;

[0029] Figure 3A and Figure 3B The following are signaling diagrams illustrating example procedures for supporting UE connection state-based sensing task allocation according to various aspects of this disclosure;

[0030] Figure 4A , Figure 4B as well as Figure 4C The following are signaling diagrams illustrating example processes for UE connection state-based awareness task allocation according to various aspects of this disclosure;

[0031] Figure 5A , Figure 5B , Figure 5C , Figure 5D , Figure 5E as well as Figure 5F The following are signaling diagrams illustrating example processes for UE-based energy state-based sensing task allocation according to various aspects of this disclosure;

[0032] Figure 6A and Figure 6B Signaling diagrams illustrating example procedures for sensing task allocation based on UE energy state, according to other aspects of this disclosure, are shown respectively.

[0033] Figure 7 The illustration shows an example of a device that supports the assignment of sensing tasks to a UE in accordance with some aspects of this disclosure;

[0034] Figure 8 The illustration shows an example of a device for assigning sensing tasks to a UE in accordance with other aspects of this disclosure; and

[0035] Figure 9 The diagram illustrates a flowchart of a method for assigning perception tasks to a UE in accordance with other aspects of this disclosure. Detailed Implementation

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

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

[0038] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the described embodiments may include specific features, structures, or characteristics, but not every embodiment necessarily includes such specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiments. Moreover, when a specific feature, structure, or characteristic is described in conjunction with an embodiment, it is understood that in conjunction with other embodiments, affecting such a feature, structure, or characteristic, whether explicitly described or not, is within the knowledge of those skilled in the art.

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

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

[0041] 3GPP is discussing enhancing cellular wireless communication systems by incorporating wireless sensing technologies. UEs can have different sensing capabilities under different connection or energy states. Therefore, it is necessary to investigate how to improve the allocation of sensing tasks to UEs by taking sensing capability information into account.

[0042] In view of the above, this disclosure provides a solution that supports the allocation of sensing tasks to a UE based on sensing capability information associated with the UE's connection state or energy state. In this solution, a first device (such as a sensing function (SF)) acquires a first state of the UE, and the first state of the UE includes the UE's connection state or energy state. Furthermore, based at least on the UE's first state, the first device determines the UE's first sensing capability information for allocating sensing tasks to the UE. In this way, the UE's connection state or energy state can be taken into account when the first device allocates sensing tasks to the UE, thereby ensuring more accurate and efficient sensing task allocation.

[0043] The aspects of this disclosure are described in the context of a wireless communication system.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0064] Details of core network 106 will be referenced Figure 1B Described.

[0065] Figure 1B The diagram illustrates a wireless network architecture with sensing capabilities according to various aspects of this disclosure. Specifically, Figure 1B The diagram shows... Figure 1A The network entities or network functions (NFs) in the core network 106 shown.

[0066] Core network 106 may include at least one control plane (CP) entity that manages access and mobility. In some implementations, at least one control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.), for one or more UEs 104 served by one or more network entities 102 associated with core network 106. For example, as Figure 1B As shown, at least one control plane entity may include an Access and Mobility Management Function (AMF) 120 or a Mobility Management Entity (MME) (not shown). The AMF 120 may communicate with the UE 104 and RAN node 102 via the N1 and N2 interfaces, respectively. The AMF 120 may also communicate with the SF 122 via the NS1 interface.

[0067] Core network 106 may include at least one network entity that routes packets or interconnects to external networks. For example, at least one network entity may include SF 122, which enables awareness in the 5G network. SF 122 may be a standalone 5GC NF or co-located with an existing 5GC NF (e.g., Location Management Function (LMF)). SF 122 may communicate with AMF 120 via the NS1 interface. SF 122 may include an SF Control (SF-C) portion and an SF User (SF-U) portion.

[0068] As another example, at least one network entity may include a Network Data Analysis Function (NWDAF) 124. A 5GC network function (NF) may be a service consumer that can subscribe to data analysis from the NWDAF 124. The NWDAF 124 can collect data from other 5GC NFs and provide data statistics or forecasts to the service consumer. The SF 122 may communicate with the NWDAF 124 via an NS4 interface.

[0069] Figure 2 The diagram illustrates a flowchart of a method 200 supporting the allocation of sensing tasks to a UE according to some aspects of this disclosure. Method 200 may be implemented at a first device. In some implementations, the first device may perform... Figure 1B SF122 in [the original text]. In other implementations, the first device may perform NF other than SF122. The scope of this disclosure is not limited in this respect. For purposes of discussion, method 200 will refer to [the original text]. Figure 1B Described from the perspective of SF 122.

[0070] At box 210, SF 122 acquires the first state of UE 104. The first state of UE 104 includes either the connection state of UE 104 or the energy state of UE 104.

[0071] At box 220, SF 122 determines first sensing capability information of UE 104 based at least on the first state of UE 104 for use in assigning sensing tasks to UE 104.

[0072] Using method 200, the SF associated with the sensing UE can obtain the UE's connection state or energy state. Furthermore, when assigning sensing tasks to the UE, the SF can consider sensing capability information associated with the UE's connection state or energy state.

[0073] In some implementations, the second device receives the first message. Then, based on the first message, the second device determines and provides the first state of UE 104 to SF 122. Furthermore, the second device provides the first state of UE 104 to SF 122 for allocating sensing tasks to UE 104. Therefore, SF 122 obtains the first state of UE 104 from the second device.

[0074] In some embodiments, the second device may perform Figure 1B The second device is AMF 120. In other implementations, the second device may perform NF other than AMF 120. The scope of this disclosure is not limited in this respect. Hereinafter, some implementations of this disclosure will be described using AMF 120 as an example of the second device.

[0075] In some implementations, the first message may include a sensing message. For example, the sensing message may include a sensing registration request message. AMF 120 can receive sensing messages from UE 104. This will refer to... Figure 3A To describe.

[0076] Figure 3A The illustration shows a signaling diagram of an example procedure 300A supporting UE-based connection state-aware task allocation according to various aspects of this disclosure. Example procedure 300A can be considered as an example implementation of method 200. For discussion purposes, procedure 300A will be referenced... Figure 1B The process 300A can involve UE 104, RAN node 102, AMF 120, and SF122.

[0077] Typically, in procedure 300A, SF 122 can obtain the first state of UE 104 from AMF 120. The first state of UE 104 includes the connection state of UE 104.

[0078] Specifically, UE 104 can perform a sense registration process to SF 122 via AMF 120. UE 104 can trigger the sense registration process by sending an uplink non-access stratum (NAS) message 310 to AMF 120. The uplink NAS message may contain the UE 104's identifier (ID) and sense messages, such as a sense registration request message.

[0079] For example, the ID of UE 104 can be one of the following: Subscription Permanent Identifier (SUPI), General Public Subscription Identifier (GPSI), 5G Globally Unique Temporary UE Identifier (5G-GUTI), or 5G System Architecture Evolution Temporary Mobile Station Identifier (5G-S-TMSI) or other types of ID.

[0080] In some implementations, new payload container types (such as awareness message containers) can be defined for uplink NAS messages. Aware registration request messages can be included within awareness message containers. Aware registration request messages can include the UE 104's ID, such as the UE 104's SUPI.

[0081] In some implementations, the perception registration request message may include perception capability information for UE 104. For example, perception capability information may include at least one of the following: supported perception modes, supported perception accuracy, confidence level, perception resolution, false alarm probability, missed detection probability, refresh rate, maximum perception service latency, user plane connectivity support indicator (or CP / UP support indicator), transmitter (Tx) / receiver (Rx) support indicator, and non-3GPP perception support indicator. The Tx / Rx support indicator indicates whether UE 104 can act as a perception Tx, or a perception Rx, or both. The CP / UP support indicator indicates whether UE 104 supports CP-based perception measurement reporting or UP-based perception measurement reporting, or both.

[0082] Upon receiving an uplink NAS message, the AMF 120 can determine that the container contains a sensing message based on the payload container type. Furthermore, the AMF 120 can perform SF selection based on at least one of the UE location or SF payload. The AMF 120 can be configured with SF information via an Open Application Model (OAM) or a Public Land Mobile Network (PLMN). For example, the SF information includes at least one of the following: SF ID, SF IP address, SF Fully Qualified Domain Name (FQDN), or SF service area.

[0083] Alternatively, SF 122 can be registered with the NRF by providing SF information to the Network Repository Function (NRF). AMF 120 can request SF information from the NRF. The NRF can then check the service area of ​​AMF 120 and locate the corresponding SF 122. The NRF can then provide the SF information to AMF 120.

[0084] AMF 120 can send a Perception Registration Request message to SF 122. In this way, SF 122 can identify Perception UE 104 located within its service area. In some implementations, an NS1 interface may exist between AMF 120 and SF 122. AMF 120 can assign an AMF UE NS1 AP ID to UE 104 to enable identification of UE 104 via the NS1 interface. AMF 120 can send both the AMF UE NS1 AP ID and the Perception Registration Request message to SF 122. SF 122 can then obtain the UE ID (e.g., SUPI) from the Perception Registration Request message.

[0085] After receiving the awareness registration request message from AMF 120, SF 122 can send an awareness registration response message to AMF 120. Upon receiving the AMF UE NS1 AP ID from AMF 120, SF 122 can assign an SF UE NS1 AP ID to UE 104. In other words, SF 122 can provide AMF 120 with both the AMF UE NS1 AP ID and the SF UE NS1 AP ID (optional) included with the awareness registration response message.

[0086] After receiving the awareness registration response message from SF 122, AMF 120 can forward the awareness registration response message to UE 104 based on the AMF UE NS1 AP ID. Specifically, AMF 120 can send the awareness registration response message to the serving RAN node 102 of UE 104, and the serving RAN node 102 can forward the awareness registration response message to UE 104.

[0087] It is understandable that after UE 104 has registered with SF 122, SF 122 is associated with UE 104. Therefore, SF 122 is also referred to as the SF associated with UE 104.

[0088] In some implementations, based on the awareness message from UE 104, AMF 120 can determine that UE 104 is an awareness UE. Furthermore, AMF 120 can determine that 320 provides SF 122 with the connection status of UE 104.

[0089] In some implementations, the connection state of UE 104 may include the connection management (CM) state or the radio resource control (RRC) state of UE 104. In some implementations, the CM state may include a CM idle state or a CM connected state, and the RRC state may include an RRC idle state, an RRC inactive state, or an RRC connected state.

[0090] In some implementations, if UE 104 is in CM idle state, the corresponding RRC state can be RRC idle state. However, if UE 104 is in CM connected state, the corresponding RRC state can be RRC inactive state or RRC connected state.

[0091] In some implementations, the AMF 120 can provide CM status or RRC status based on predefined values.

[0092] In some implementations, if AMF 120 determines that the connection state of UE 104 has been updated, AMF 120 can determine to provide the updated connection state of UE 104 to SF 122.

[0093] In some implementations, if the RRC status of UE 104 is required, AMF 120 can trigger the N2 notification procedure to request RAN node 102 to provide the RRC status of UE 104. When UE 104 is in CM connected state, the N2 notification procedure can be used to obtain the exact RRC status of UE 104 (e.g., RRC inactive state or RRC connected state). When UE 104 is in CM idle state, the corresponding RRC status is RRC idle state, so AMF 120 can know the RRC status of UE 104 on its own.

[0094] During the N2 notification process, AMF 120 may send a UE connection state transition notification request to the serving RAN node 102 of UE 104. In some implementations, AMF 120 may include the UE ID in the UE connection state transition notification request. For example, the UE ID may be one of the following: AMF UE Next Generation Application Protocol (NGAP) ID, SUPI, GPSI, 5G-GUTI, or 5G-S-TMSI. The AMF UE NGAP ID may be assigned by AMF 120 to identify UE 104 through the NG interface between AMF 120 and RAN node 102. Alternatively, the RAN UE NGAP ID may be used in place of the AMF UE NGAP ID or together with the AMF UE NGAP ID. The RAN UE NGAP ID may be assigned by RAN node 102 to identify UE 104 through the NG interface.

[0095] In some implementations, if the RRC state of UE 104 changes, for example, switching between an RRC inactive state and an RRC connected state, the serving RAN node 102 of UE 104 can send a 330 UE notification message to AMF 120, which includes the current RRC state of UE 104.

[0096] Subsequently, AMF 120 can send the connection status of UE 104 (335) to SF 122. In some implementations, AMF 120 can send both the UE ID (e.g., SUPI, GPSI, 5G-GUTI, 5G-S-TMSI, AMF UE NS1 AP ID, SF UE NS1 AP ID) and the connection status of UE 104 to SF 122. The AMF UE NS1 AP ID or SF UE NS1 AP ID can be assigned by AMF 120 or SF 122 respectively to identify UE 104 through the NS1 interface between AMF 120 and SF 122. In some implementations, the connection status of UE 104 may include the current CM state (e.g., CM idle state or CM connected state) or the current RRC state (e.g., RRC idle state, RRC inactive state, RRC connected state).

[0097] After obtaining the connection status of UE 104, SF 122 can determine at least 340 perception capability information of UE 104 based on the connection status.

[0098] In some implementations, the association or mapping between the connection state of UE 104 and the sensing capability information of UE 104 can be predefined. In such implementations, SF 122 can determine the sensing capability information based on the connection state and the predefined association or mapping.

[0099] Furthermore, SF 122 can assign sensing tasks to UE 104 based on sensing capability information.

[0100] In some implementations, SF 122 can assign sensing tasks to UE 104 in either RRC connected or CM connected state. Alternatively, SF 122 can assign sensing task allocation to UE 104 in both RRC inactive and RRC connected states.

[0101] Alternatively or additionally, if CM status needs to be provided, actions 325 and 330 (i.e., the N2 notification procedure) can be omitted because AMF 120 itself knows the CM status of UE 104.

[0102] Alternatively or additionally, UE 104 can provide SF 122 with the connection status of UE 104 in a sensing message via AMF 120.

[0103] In some implementations, the first message may include a request for connection state. In such an implementation, to obtain the connection state of UE 104, SF 122 may provide a request for connection state to AMF 120 based on a sense message from UE 104. For example, the request for connection state may include a UE connection state subscription message or a UE connection state request message. AMF 120 may determine to provide the connection state to SF 122 based on the request. This will refer to... Figure 3B To describe.

[0104] Figure 3B The illustration shows a signaling diagram of an example procedure 300B supporting UE connection state-based sensing task allocation according to other aspects of this disclosure. Example procedure 300B can also be considered as an example implementation of method 200. For discussion purposes, procedure 300B will be referenced to... Figure 1B The process 300A can involve UE 104, RAN node 102, AMF 120, and SF122.

[0105] Typically, the main difference between process 300B and process 300A lies in the additional action 315 between action 310 and action 320.

[0106] Specifically, in process 300B, after receiving the sensing registration message, SF 122 can send 315 a request to AMF 120 regarding the connection status of UE 104. Then, based on this request, AMF 120 can determine 320 to provide the connection status of UE 104 to SF 122 associated with sensing UE 104. Actions 310, 320, 325, 330, 335, and 340 are related to... Figure 3A The actions described are the same. For the sake of brevity, the details of these actions have been omitted.

[0107] In some implementations, SF 122 may provide AMF 120 with a request for the UE ID (e.g., SUPI, GPSI, 5G-GUTI, or 5G-S-TMSI) along with the connection status. Alternatively, the UE ID may be included in the request for the connection status.

[0108] In some implementations, SF 122 may indicate whether a CM state or an RRC state is requested in a connection state request. For example, a connection state request may include a connection state indication indicating whether a CM state or an RRC state of UE 104 is requested. The connection state indication may be represented by different values ​​to indicate different connection states. In some implementations, a value of 0 indicates that a CM state is required and a value of 1 indicates that an RRC state is required.

[0109] Alternatively, it can be predefined that a request for connection status is used to request the CM status or RRC status of UE 104.

[0110] In some implementations, a request for connection status can instruct the AMF 120 to provide the current connection status of the UE 104 (e.g., the current CM status or RRC status). For example, a request for connection status can instruct a single RRC connection status report.

[0111] Alternatively, in some implementations, a request for connection status can instruct AMF 120 to provide the connection status based on an update. In such an implementation, if AMF 120 determines that the connection status has been updated, AMF 120 can provide the updated connection status to SF 122. In some implementations, a request for connection status can instruct a subsequent report from AMF 120 whenever the connection status changes. For example, if the connection status changes from CM idle state to CM connected state, AMF 120 can provide the subsequent connection status (i.e., CM connected state) to SF 122. For another example, if the connection status changes from RRC inactive state to RRC connected state, AMF 120 can provide the subsequent connection status (i.e., RRC connected state) to SF 122.

[0112] In some implementations, UE 104 can indicate the association or mapping between the connection state of UE 104 and the sensing capability information of UE 104. In such an implementation, SF 122 can determine the sensing capability information based on the connection state and the indicated association or mapping. This will refer to... Figure 4A , 4B And it can be described using 4C.

[0113] Figure 4A The illustration shows a signaling diagram of an example procedure 400A supporting UE connection state-based awareness task allocation according to other aspects of this disclosure. Example procedure 400A can be considered as an example implementation of method 200. For discussion purposes, procedure 400A will be referenced to... Figure 1B The process 400A can involve UE 104, RAN node 102, AMF 120, and SF122.

[0114] Typically, in procedure 400A, in order to obtain the connection status of UE 104, SF 122 can provide a request for connection status to AMF 120 based on the sensing message from UE 104. AMF 120 can then determine the connection status to provide to SF 122 based on this request.

[0115] Specifically, similar to procedures 300A and 300B, UE 104 can perform a sense registration procedure to SF 122 via AMF 120. UE 104 can trigger the sense registration procedure by sending an uplink NAS message 410 to AMF 120. The uplink NAS message may contain UE 104's ID and sense information, such as a sense registration request message.

[0116] Considering that UE 104 may have different sensing capabilities under different connection states, during the sensing registration process, UE 104 can provide an association or mapping between its connection state and sensing capability information. For example, UE 104 can provide this association or mapping in sensing messages (such as sensing registration request messages or other types of sensing messages). Additionally, UE 104 can provide its UE ID (e.g., SUPI, GPSI, 5G-GUTI, 5G-S-TMSI) in the sensing messages.

[0117] In some implementations, UE 104 may or may not support sensing in different connectivity states. In some implementations, sensing capability information may include at least one indicator. Each of the at least one indicator indicates whether UE 104 supports sensing in one connectivity state. For example, sensing capability information may include one of the following: RRC-only connectivity mode indicator, CM-only connectivity state indicator, all connectivity states indicator, or non-3GPP sensing support indicator. The RRC-only connectivity mode indicator may indicate that UE 104 supports sensing only in the RRC connectivity state. The CM-only connectivity state indicator may indicate that UE 104 supports sensing in the CM connectivity state, i.e., it supports sensing in both the RRC inactive state and the RRC connectivity state. The all connectivity states indicator may indicate that UE 104 supports sensing in all connectivity states. The non-3GPP sensing support indicator may indicate that UE 104 supports non-3GPP sensing, such as radar, camera, LiDAR, or Wi-Fi sensing.

[0118] Alternatively, in some implementations, UE 104 can support different sensing capability parameters under different connection states. In such implementations, the sensing capability information may include at least one sensing capability parameter or at least one index of at least one set of sensing capability parameters.

[0119] In some implementations, the sensing capability parameters include at least one of the following: supported sensing modes, supported sensing bandwidth, supported sensing accuracy, confidence level, sensing resolution, false alarm probability, missed detection probability, refresh rate, maximum sensing service latency, user plane connectivity support indicator, CP / UP support indicator, or Tx / Rx support indicator. The Tx / Rx support indicator can indicate whether UE 104 can act as a sensing Tx device, or a sensing Rx device, or both. The CP / UP support indicator can indicate whether UE 104 supports CP-based sensing measurement reporting, UP-based sensing measurement reporting, or both.

[0120] In some implementations, the association or mapping may include a first set of connection states and a second set of sensing capability information associated with the first set of connection states. Each sensing capability information in the second set of sensing capability information is associated with a connection state in the first set of connection states. In such an implementation, the association or mapping may include at least one pair of sensing support indicators associated with connection states in the first set and sensing capability information in the second set. Alternatively, the association or mapping may include at least one pair of connection states in the first set and associated sensing capability parameters in the second set.

[0121] For example, the first connection state set may include the CM idle state, and the second sensing capability information set may include a non-support indicator indicating that UE 104 does not support sensing in the CM-idle state. Therefore, the association or mapping may include a pair (CM idle, non-support indicator).

[0122] For another example, the first set of connectivity states may include CM connectivity states, and the second set of sensing capability information may include a support indicator that indicates UE 104 supports sensing in the CM-connectivity state. Therefore, the association or mapping may include a pair (CM connectivity, support indicator).

[0123] For another example, the association or mapping could include a pair (RRC idle, non-supported indicator), a pair (RRC inactive, supported indicator), and a pair (RRC connected, supported indicator). For yet another example, the association or mapping could include a pair (all connection states, supported indicator).

[0124] In some implementations, the association or mapping may include at least one pair of associated sensing capability parameters from a first set of connection states and a second set of sensing capability parameters. For example, the association or mapping may include a pair of (CM idle, non-support indicator) and a pair of (CM connected, sensing capability parameter #1). For another example, the association or mapping may include a pair of (CM idle, sensing capability parameter #2) and a pair of (CM connected, sensing capability parameter #3). For yet another example, the association or mapping may include a pair of (RRC idle, non-support indicator), a pair of (RRC inactive, sensing capability parameter #4), and a pair of (RRC connected, sensing capability parameter #5). For yet another example, the association or mapping may include a pair of (3GPP, sensing capability parameter #6) and a pair of (non-3GPP, sensing capability parameter #7).

[0125] Alternatively, in some implementations, the sensing capability information may include at least one index of at least one sensing capability. In such an implementation, UE 104 may support different indices of sensing capabilities in different connection states.

[0126] In some implementations, the association or mapping may include a first set of connection states and a second set of awareness indexes. Each index in the indexes is associated with a connection state within the connection states. For example, the association or mapping may include a pair (CM connected, awareness index #1). For another example, the association or mapping may include a pair (CM idle, awareness index #2) and a pair (CM-connected, awareness index #3). For yet another example, the association or mapping may include a pair (RRC inactive, awareness index #4) and a pair (RRC-connected, awareness index #5). For yet another example, the association or mapping may include a pair (3GPP, awareness index #6) and a pair (non-3GPP, awareness index #7).

[0127] Alternatively, in some implementations, the sensing capability information may include at least one index of at least one sensing capability. In such an implementation, UE 104 may support different sensing capability indices in different connection states.

[0128] In some implementations, the association or mapping between the sensing capabilities and the connection state of UE 104 can be predefined or preconfigured by the operator in SF 122 and UE 104. For example, the association or mapping can be predefined or preconfigured as a sensing capability parameter set table. For example, in the sensing capability parameter set table, the value "1" can indicate that sensing capability parameter #1 is supported for the CM-Connected state. Therefore, if SF 122 obtains the value "1" from UE 104, SF 122 can determine that UE 104 supports sensing capability parameter #1 for the CM-Connected state.

[0129] Actions 415a, 420, 425, 430, and 435 in process 400A are similar to actions 315, 320, 325, 330, and 335 in process 300B. For the sake of brevity, the details of these actions are omitted.

[0130] When the connection status of UE 104 is obtained, SF 122 can determine 440 perception capability information based on the obtained connection status of UE 104. When assigning perception tasks to UE 104, SF 122 can consider the perception capability information based on the connection status of UE 104 (e.g., perception support indicator, perception capability parameters, index of perception capability parameter set, or index of perception capability).

[0131] Alternatively, in some implementations, UE 104 may provide its connection status to SF 122 via AMF 120 in a perception message. Alternatively, UE 104 may provide current perception capability information (e.g., perception support indicator, perception capability parameters, index of perception capability parameter set, or index of perception capability) to SF 122 via AMF 120 in a perception message.

[0132] Figure 4B The illustration shows a signaling diagram of an example procedure 400B supporting UE connection state-based awareness task allocation according to other aspects of this disclosure. Example procedure 400B can also be considered as an example implementation of method 200. For discussion purposes, procedure 400B will be referenced to... Figure 1B The process 400B can be described as follows: UE 104, RAN node 102, AMF 120, and SF122.

[0133] Typically, in procedure 400B, AMF 120 can receive an indication from UE 104. The indication tells AMF 120 to provide the connection status of UE 104 to SF 122. AMF 120 can then determine, based on the indication, to provide the connection status to SF 122. In such an implementation, the first message may include the indication from UE 104. The main difference between procedure 400B and procedure 400A is that action 415a in procedure 400A is replaced by action 415b.

[0134] Specifically, in procedure 400B, after UE 104 sends a 410 awareness message to SF 122, UE 104 may send a 415b UE connection status report indicator to AMF 120. This indicator instructs AMF 120 to provide SF 122 with the connection status of UE 104.

[0135] In some implementations, UE 104 can also indicate whether CM status or RRC status is required. For example, UE 104 can provide a CM status report indicator or an RRC status report indicator to AMF120. For another example, a UE connectivity status indicator can be defined. A UE connectivity status indicator equal to 0 means that CM status is required, and a UE connectivity status indicator equal to 1 means that RRC status is required.

[0136] Alternatively or additionally, UE 104 may instruct AMF 120 to support different sensing capability information in different connection states, which also implies that AMF 120 provides SF 122 with the connection state of UE 104.

[0137] Alternatively, UE 104 can directly provide AMF 120 with sensing capability information associated with different connection states of UE 104. This sensing capability information can be the same as described above regarding action 410.

[0138] In some implementations, if AMF 120 knows that UE 104 supports awareness in all UE states, AMF 120 can determine not to provide the connection state of UE 104 to SF 122 associated with UE 104.

[0139] Alternatively, if AMF 120 knows that UE 104 only supports awareness in RRC connected state, AMF 120 can determine to provide the RRC state to SF 122 associated with UE 104. In this case, AMF 122 can provide only two RRC states, such as RRC connected state and non-RRC connected state. Non-RRC connected state includes RRC idle state or RRC inactive state.

[0140] Alternatively, if AMF 122 knows that UE 104 supports different awareness capability information in RRC inactive and RRC connected states, then AMF 120 can determine to provide the RRC state of UE 104 to the SF 122 associated with UE 104. In this case, AMF 122 can provide only two RRC connected states, such as RRC inactive and RRC connected states.

[0141] Actions 410, 420, 425, 430, 435, and 440 Figure 4A The actions described are the same. For the sake of brevity, the details of these actions have been omitted.

[0142] Figure 4C The illustration shows a signaling diagram illustrating an example procedure 400C supporting UE connection state-based awareness task allocation according to other aspects of this disclosure. Example procedure 400C can also be considered as an example implementation of method 200. For discussion purposes, procedure 400C will refer to... Figure 1B The process 400C can be described as follows: UE 104, RAN node 102, AMF 120, and SF122.

[0143] Typically, the main difference between process 400C and processes 400A and 400B is that actions 415a in process 400A and 415b in process 400B are omitted. Similar to action 320 in process 300A, in process 400C, AMF 120 can determine 420 to provide SF 122 with the connection status of UE 104 based on the perception message from UE 104 to SF 122 in action 410. Actions 410, 425, 430, 435, and 440 are related to... Figure 4A The same applies to those in the text. For the sake of brevity, the details of these actions have been omitted.

[0144] In some implementations, SF 122 can provide AMF 120 with sensing tasks that require sensing capabilities. AMF 120 can choose to sense UE 104 or sense RAN node 102 to assign the sensing task. In such an implementation, AMF 120 does not provide UE 104's connectivity status to SF122, and AMF 120 can consider UE 104's connectivity status when assigning sensing tasks to UE 104.

[0145] In some implementations, UE 104 can indicate the association or mapping between the energy state of UE 104 and the sensing capability information of UE 104. In such an implementation, SF 122 can determine the sensing capability information based on the energy state and the indicated association or mapping. This will refer to... Figure 5A , Figure 5B , Figure 5C , Figure 5D , Figure 5E as well as Figure 5F To describe.

[0146] Figure 5A The illustration shows a signaling diagram of an example procedure 500A supporting UE energy state-based sensing task allocation according to various aspects of this disclosure. Example procedure 500A can be considered as an example implementation of method 200. For discussion purposes, procedure 500A will be referenced... Figure 1B The process 500A can involve UE104, RAN node 102, AMF 120, and SF 122.

[0147] Typically, in procedure 500A, to obtain the energy status of UE 104, SF 122 can provide a request for energy status to AMF 120 based on the perception message from UE 104. AMF 120 can then determine to provide the energy status to SF 122 based on the request.

[0148] Specifically, similar to procedures 300A and 300B, UE 104 can perform a sense registration procedure to SF 122 via AMF 120. UE 104 can trigger the sense registration procedure by sending an uplink NAS message 510 to AMF 120. The uplink NAS message may contain UE 104's ID and sense information, such as a sense registration request message.

[0149] Considering that UE 104 can have different sensing capabilities under different energy states, during the sensing registration process, UE 104 can provide an association or mapping between UE 104's energy state and UE 104's sensing capability information. For example, UE 104 can provide this association or mapping in sensing messages, such as sensing registration request messages or other types of sensing messages.

[0150] Additionally, UE 104 can provide the UE ID (e.g., SUPI, GPSI, 5G-GUTI, 5G-S-TMSI) in the awareness message.

[0151] In some implementations, the energy state of UE 104 may include the battery level or power mode of UE 104.

[0152] In some implementations, UE 104 may or may not support sensing in different energy states. In such implementations, sensing capability information may include at least one indicator. Each of the at least one indicator indicates whether UE 104 supports sensing in one of the energy states. For example, sensing capability information may include one of the following: a non-energy-saving mode only indicator, or a threshold for battery level used for sensing. A non-energy-saving mode only indicator may indicate that UE 104 supports sensing only when it is not in energy-saving mode. A threshold for battery level used for sensing may indicate that UE 104 supports sensing only when its battery level is higher than a threshold (e.g., 60%).

[0153] Alternatively, in some implementations, UE 104 can support different sensing capability parameters under different energy states. In such implementations, the sensing capability information may include at least one sensing capability parameter, or at least one index of at least one set of sensing capability parameters.

[0154] In some implementations, the association or mapping may include a first set of energy states and a second set of sensing capability information associated with the first set of energy states. Each sensing capability information in the second set of sensing capability information is associated with an energy state in the first set of energy states. In such an implementation, the association or mapping may include at least one pair of sensing support indicators associated with energy states in the first set of energy states and the second set of sensing capability information. Alternatively, the association or mapping may include at least one pair of sensing capability parameters associated with energy states in the first set of energy states and the second set of sensing capability parameters.

[0155] For example, the first energy state set may include a non-energy-saving mode, and the second sensing capability information set may include a support indicator that instructs UE 104 to support sensing in the non-energy-saving mode. Therefore, the association or mapping may include a pair (non-energy-saving mode, support indicator).

[0156] For example, the first energy state information set may include a battery level threshold, and the second sensing capability information set may include a support indicator that indicates that UE 104 supports sensing when the battery level of UE 104 is higher than the battery level threshold. Therefore, the association or mapping may include a pair (battery level threshold, support indicator).

[0157] For example, an association or mapping could include a pair (energy-saving mode, sensing capability parameter #1) and a pair (non-energy-saving mode, sensing capability parameter #2). For another example, an association or mapping could include a pair (battery level below threshold #1, non-support indicator) and a pair (battery level above threshold #2, sensing capability parameter #3). For yet another example, an association or mapping could include a pair (battery level below threshold #1, sensing capability parameter #4), a pair (battery level above threshold #2 and below threshold #3, sensing capability parameter #5), and a pair (battery level above threshold #3, sensing capability parameter #6).

[0158] Alternatively, in some implementations, the sensing capability information may include at least one index of at least one sensing capability. In such an implementation, UE 104 may support different indices of sensing capabilities under different energy states.

[0159] In some implementations, the association or mapping may include a first set of energy states and a second set of sensing capability indices. Each index in the indices is associated with an energy state. For example, the association or mapping may include a pair (energy-saving mode, sensing capability index #1) and a pair (non-energy-saving mode, sensing capability index #2). For another example, the association or mapping may include a pair (battery level above threshold #2, sensing capability index #3). For yet another example, the association or mapping may include a pair (battery level below threshold #1, sensing capability index #4), a pair (battery level above threshold #2 and below threshold #3, sensing capability index #5), and a pair (battery level above threshold #3, sensing capability index #6).

[0160] Continue to refer to Figure 5A After receiving a sensing message from UE 104, SF 122 can send a 515a request to AMF 120 regarding the energy status of UE 104.

[0161] In some implementations, a request for energy status can instruct the AMF 120 to provide the current energy status of the UE 104 (e.g., current battery level or current power mode). For example, a request for energy status can instruct a single energy status report.

[0162] Alternatively, in some implementations, a request for energy state can instruct AMF 120 to provide connection state based on an update of connection state. For example, a request for energy state can instruct a subsequent report from AMF 120 whenever the energy state changes. In such an implementation, if AMF 120 determines that the energy state has been updated or changed, AMF 120 can provide SF 122 with the updated or subsequent energy state.

[0163] After receiving a request from SF 122, AMF 120 can determine the energy status of UE 104 provided by 520 to SF 122 based on the request.

[0164] Furthermore, AMF 120 can send a 525a Energy State Transition Notification Request to the serving RAN node 102 of UE 104. In such an implementation, the Energy State Transition Notification Request can be a message defined for the NG interface between AMF 120 and RAN node 102.

[0165] Upon receiving a power state transition notification request from AMF 120, the serving RAN node 102 of UE 104 can send 530a UE ID and the current power state of UE 104 to AMF 120. For example, the UE ID can be one of the following: AMF UE NGAP ID, RAN UE NGAP ID, SUPI, GPSI, 5G-GUTI, or 5G-S-TMSI. If the power state of UE 104 changes, such as switching between power-saving and non-power-saving modes, or if the battery level of UE 104 changes from low to high (e.g., above a given threshold), the serving RAN node 102 can trigger action 530a. In some implementations, UE 104 can report its power state to RAN node 102 via an RRC message upon request or when the power state of UE 104 changes.

[0166] Furthermore, AMF 120 can send the energy status of UE 104 (535) to SF 122. In some implementations, AMF 120 can send both the UE ID (e.g., AMF UE XAP ID, SF UE XAP ID, SUPI, GPSI, 5G-GUTI, 5G-S-TMSI) and the energy status to SF 122.

[0167] After obtaining the energy state of UE 104, SF 122 can determine the sensing capability information of UE 104 based on the energy state. Then, SF 122 can assign sensing tasks to UE 104 based on the sensing capability information associated with the energy state. In some implementations, if UE 104 supports sensing in the current energy state, SF 122 can assign a sensing task to UE 104. Alternatively, SF 122 can first determine whether the sensing capability information is eligible to perform a sensing task. If the sensing capability information is eligible to perform a sensing task, SF 122 can assign a sensing task to UE 104.

[0168] Typically, process 500A is similar to process 400A. Therefore, some implementation details already described for process 400A can also be applied to process 500A.

[0169] Figure 5B The illustration shows a signaling diagram of an example procedure 500B supporting UE energy state-based sensing task allocation according to other aspects of this disclosure. Example procedure 500B can also be considered as an example implementation of method 200. For discussion purposes, procedure 500B will be referenced to... Figure 1B The process 500B can involve UE 104, RAN node 102, AMF 120, and SF122.

[0170] Typically, in procedure 500B, AMF 120 can receive an indication from UE 104. This indication tells AMF 120 to provide the power status of UE 104 to SF 122. AMF 120 can then determine, based on the indication, to provide the power status to SF 122. In such an implementation, the first message may include the indication from UE 104.

[0171] The main difference between process 500B and process 500A is that action 515a in process 500A is replaced by action 515b.

[0172] Specifically, in procedure 500B, after UE 104 sends a 510 awareness message to SF 122, UE 104 can send a 515b UE energy status report indicator to AMF 120. This indicator instructs AMF 120 to provide SF 122 with the energy status of UE 104.

[0173] Actions 510, 520, 525a, 530a, 535, and 540 Figure 5A The actions described are the same. For the sake of brevity, the details of these actions have been omitted.

[0174] Typically, process 500B is similar to process 400B. Therefore, some implementation details already described for process 400B can also be applied to process 500B.

[0175] Figure 5C The illustration shows a signaling diagram of an example procedure 500C supporting UE energy state-based sensing task allocation according to other aspects of this disclosure. Example procedure 500C can also be considered as an example implementation of method 200. For discussion purposes, procedure 500C will be referenced to... Figure 1B The process 500C can involve UE 104, RAN node 102, AMF 120, and SF122.

[0176] Typically, the main difference between process 500C and processes 500A and 500B is that process 500C omits operation 515a in process 500A and operation 515b in process 500B. Similar to action 320 in process 300A, in process 500C, AMF 120 can determine, based on the perception message from UE 104 to SF 122 in action 510, to provide the energy state of UE 104 to SF 122. Actions 510, 525a, 530a, 535, and 540 are... Figure 5A The same as in the text. For the sake of brevity, the details of these actions are omitted.

[0177] Typically, process 500C is similar to process 400C. Therefore, some implementation details already described for process 400C can also be applied to process 500C.

[0178] Figure 5D , Figure 5E as well as Figure 5F Signaling diagrams for example procedures 500D, 500E, and 500F, which support UE energy state-based sensing task allocation according to other aspects of this disclosure, are illustrated respectively. Example procedures 500D, 500E, and 500F can also be considered as example implementations of method 200. For discussion purposes, procedures 500D, 500E, and 500F will be referenced. Figure 1B The procedures 500D, 500E, and 500F can involve UE 104, RAN node 102, AMF 120, and SF122.

[0179] Typically, the main difference between processes 500D, 500E, and 500F and processes 500A, 500B, and 500C is that actions 525a and 530a in processes 500A, 500B, and 500C are replaced by actions 525b and 530b.

[0180] Specifically, in procedures 500D, 500E, and 500F, after AMF 120 determines that 520 provides SF 122 with the energy state of UE 104, AMF 120 can send a 525b UE Energy State Transition Notification Request to UE 104. The UE Energy State Transition Notification Request can instruct UE 104 to provide its energy state to AMF 120. In some implementations, the UE Energy State Transition Notification Request can be a type of downlink NAS message. Furthermore, if the energy state changes, UE 104 can provide 530b energy state to AMF 120.

[0181] Actions 510, 515a, 515b, 520, 535, and 540 Figure 5A , Figure 5B as well as Figure 5C The actions described are the same. For the sake of brevity, the details of these actions have been omitted.

[0182] Typically, processes 500D, 500E, and 500F are similar to processes 500A, 500B, and 500C. Therefore, some implementation details already described for processes 500A, 500B, and 500C can also be applied to processes 500D, 500E, and 500F.

[0183] In some implementations, SF 122 can provide sensing tasks with sensing requirements to AMF 120. AMF 120 can choose to sense UE 104 or sense RAN node 102 to assign sensing tasks. In such implementations, AMF 120 does not provide the energy state of UE 104 to SF 122, and AMF 120 can take the energy state of UE 104 into account when assigning sensing tasks to UE 104.

[0184] Figure 6A The illustration shows a signaling diagram of an example procedure 600A supporting UE energy state-based sensing task allocation according to other aspects of this disclosure. Example procedure 600A can be considered as an example implementation of method 200. For discussion purposes, procedure 600A will be referenced to... Figure 1B The process 600A can involve UE 104, RAN node 102, AMF 120, and SF122.

[0185] Typically, in procedure 600A, to obtain the energy status of UE 104, SF 122 can send a request for energy status to UE 104 based on a sensing message from UE 104. Upon receiving the request from SF 122, UE 104 can provide the energy status to SF 122.

[0186] Specifically, similar to procedures 300A and 300B, UE 104 can perform a perception registration procedure to SF 122 via AMF 120. Considering that UE 104 may have different perception capabilities under different energy states, during the perception registration process, UE 104 can provide an association or mapping between UE 104's energy state and UE 104's perception capability information.

[0187] Upon receiving a 610 awareness message from UE 104, SF 122 may provide UE 104 with a 615a UE Energy State Transition Notification Request. The UE Energy State Transition Notification Request instructs UE 104 to provide its energy state to SF 122. The UE Energy State Transition Notification Request can be defined as an awareness message between UE 104 and SF 122.

[0188] In some implementations, SF 122 can send UE ID#1 (e.g., SUPI, GPSI, 5G-GUTI, 5G-S-TMSI) and awareness messages (e.g., UE Energy State Transition Notification Request) to AMF 120. AMF 120 can identify UE 104 based on UE ID#1 and can convert UE ID#1 to UE ID#2 (e.g., AMF UE NGAP ID or RAN UE NGAP ID). AMF 120 can then forward UE ID#2 and the awareness message to the serving RAN node 102 of UE 104. RAN node 102 can then identify UE 104 based on UE ID#2 and can send awareness messages to UE 104 via the air interface. In some implementations, the awareness message can be included in an RRC message. In some implementations, the UE ID (e.g., SUPI, GPSI, 5G-GUTI, 5G-S-TMSI) can also be included in the awareness message.

[0189] Upon receiving a UE energy state transition notification request from SF 122, if the energy state has changed, UE 104 can provide its energy state (620a) to SF 122 via RAN node 102 and AMF 120. For example, UE 104 can provide its energy state in an uplink-aware message.

[0190] Actions 610 and 625 in process 600A are related to Figures 5A to 5F Actions 510 and 540 are identical. For the sake of brevity, the details of these actions have been omitted.

[0191] Figure 6B The illustration shows a signaling diagram of an example procedure 600B supporting UE energy state-based sensing task allocation according to other aspects of this disclosure. Example procedure 600B can be considered as an example implementation of method 200. For discussion purposes, procedure 600B will be referenced to... Figure 1B The process 600B may involve UE 104, RAN node 102, AMF 120, SF 122, and NWDAF 124.

[0192] Typically, in procedure 600B, to obtain the energy state of UE 104, SF 122 can provide a request for energy state to NWDAF 124 based on the sensing message from UE 104. Upon receiving the request from SF 122, NWDAF 124 can provide the energy state of UE 104 to SF 122.

[0193] Specifically, similar to procedures 300A and 300B, UE 104 can perform a perception registration procedure to SF 122 via AMF 120. Considering that UE 104 may have different perception capabilities under different energy states, during the perception registration process, UE 104 can provide an association or mapping between UE 104's energy state and UE 104's perception capability information.

[0194] After receiving the 610 awareness message from UE 104, SF 122 can provide NWDAF 124 with a 615b UE Energy State Transition Notification Request. The UE Energy State Transition Notification Request instructs NWDAF 124 to provide SF 122 with the energy state of UE 104. The UE Energy State Transition Notification Request can be defined as a message between SF 122 and NWDAF 124.

[0195] In some implementations, SF 122 can send UE ID (SUPI, GPSI, 5G-GUTI, 5G-S-TMSI) and UE energy state transition request messages to NWDAF 124. In some implementations, the UE ID can be included in the UE energy state transition request message from SF 122 to NWDAF 124.

[0196] After receiving a UE energy state transition notification request from SF 122, NWDAF 124 can provide SF 122 with the energy state of UE 104 (620b). In some implementations, NWDAF 124 can send both the UE ID (e.g., SUPI, GPSI, 5G-GUTI, 5G-S-TMSI) and the energy state of UE 104 to SF 122.

[0197] Actions 610 and 625 in process 600A are related to Figures 5A to 5F Actions 510 and 540 are identical. For the sake of brevity, the details of these actions have been omitted.

[0198] Figure 7An example of a device 700 supporting the assignment of sensing tasks to UE 104 according to some aspects of this disclosure is illustrated. Device 700 may be an example of a first device (i.e., SF 122) as described herein. Device 700 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 700 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 702, memory 704, transceiver 706, and optionally, I / O controller 708. These components may communicate electronically or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0199] Processor 702, memory 704, transceiver 706, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of this disclosure as described herein. For example, processor 702, memory 704, transceiver 706, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

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

[0201] For example, processor 702 may support wireless communication at device 700 according to examples disclosed herein. Processor 702 may be configured to operate to support components for: acquiring a first state of a user equipment (UE), the first state of the UE including the UE's connectivity state or the UE's energy state; and determining first sensing capability information of the UE based at least on the first state of the UE for assigning sensing tasks to the UE.

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

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

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

[0205] In some implementations, device 700 may include a single antenna 710. However, in other implementations, device 700 may have more than one antenna 710 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 706 may communicate bidirectionally via one or more antennas 710, wired or wireless links, as described herein. For example, transceiver 706 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 706 may also include a modem for modulating packets to provide modulated packets to one or more antennas 710 for transmission, and for demodulating packets received from one or more antennas 710. Transceiver 706 may include one or more transmit chains, one or more receive chains, or combinations thereof.

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

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

[0208] Figure 8An example of a device 800 supporting the assignment of sensing tasks to UE 104 according to other aspects of this disclosure is illustrated. Device 800 may be an example of a second device (i.e., AMF 120) as described herein. Device 800 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 800 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 802, memory 804, transceiver 806, and optionally, I / O controller 808. These components may communicate electronically or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

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

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

[0211] For example, processor 802 may support wireless communication at device 800 according to examples disclosed herein. Processor 802 may be configured to operate to support components for: receiving a first message; determining, based on the first message, a first state of the UE to be provided to a first device, the first state of the UE including a connection state or an energy state of the UE; and providing the first state of the UE to the first device for assigning sensing tasks to the UE.

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

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

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

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

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

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

[0218] Figure 9A flowchart illustrating a method 900 for assigning sensing tasks to a UE in accordance with other aspects of this disclosure is shown. Method 900 may be implemented at a second device. Operation of method 900 may be implemented by a device or components thereof as described herein. For example, operation of method 900 may be performed by an AMF 120 as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0219] At 910, the method may include receiving a first message. The operation of 910 can be performed according to examples as described herein. In some implementations, aspects of the operation of 910 can be performed by the device, as in the reference... Figure 1A As described.

[0220] At 920, the method may include: determining, based on a first message, a first state of the UE to be provided to a first device, the first state of the UE including a connection state or an energy state of the UE. The operation of 920 can be performed according to examples as described herein. In some implementations, aspects of the operation of 920 may be derived from references... Figure 1A The device described performs the operation.

[0221] At 930, the method may include: providing a first state of the UE to a first device for assigning a sensing task to the UE. The operation of 930 can be performed according to examples as described herein. In some implementations, aspects of the operation of 930 may be derived from references... Figure 1A The device described is used to perform this action.

[0222] It should be noted that reference has been made. Figure 2 A to Figure 6B The implementation of this disclosure described herein also applies to method 800. For the sake of brevity, implementation details have been omitted.

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

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

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

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

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

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

Claims

1. A first apparatus comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first apparatus to: obtain a first status of a user equipment (UE), the first status of the UE comprising a connection status of the UE or an energy status of the UE; and determine, based at least on the first status of the UE, first perception capability information of the UE for assigning a perception task to the UE.

2. The first apparatus of claim 1, wherein the first apparatus to obtain the first status of the UE comprises: receive a perception message from a second apparatus; provide, based on the perception message, a request for the first status to the second apparatus, a third apparatus, or the UE; and obtain a response comprising the first status from the second apparatus, the third apparatus, or the UE.

3. The first apparatus of claim 2, wherein the request indicates whether a connection management (CM) status of the UE or a radio resource control (RRC) status of the UE is requested.

4. The first apparatus of claim 2, wherein the request indicates that the second apparatus, the third apparatus, or the UE provides an updated first status based on an update of the first status.

5. The first apparatus of claim 2, wherein the awareness message further comprises: a first set of statuses of the UE and a second set of perception capability information of the UE, each of the perception capability information being associated with one of the statuses, and the first set of statuses comprising a set of connection statuses of the UE or a set of energy statuses of the UE; and wherein the first apparatus to determine the first perception capability information comprises: determine the first perception capability information based on the first status, the first set of statuses, and the second set of perception capability information.

6. The first apparatus of claim 5, wherein the second set of perception capability information comprises one of: at least one indicator, each of the at least one indicator indicating whether the UE supports perception in one of the statuses; at least one perception capability parameter; at least one index of at least one set of perception capability parameters; or at least one index of at least one perception capability.

7. The first apparatus of claim 1, wherein the connection status of the UE comprises a connection management (CM) status of the UE or a radio resource control (RRC) status of the UE, and the energy status of the UE comprises a battery level of the UE or a power mode of the UE.

8. The first apparatus of any one of claims 1 to 7, wherein the first apparatus comprises a sensing function (SF), the second apparatus comprises an access and mobility management function (AMF), and the third apparatus comprises a network data analytics function (NWDAF).

9. A second apparatus comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second apparatus to: receive a first message; determining, based on the first message, to provide a first device with a first status of the UE, the first status of the UE comprising a connection status of the UE or an energy status of the UE; and providing the first status of the UE to the first device for allocating a sensing task to the UE.

10. The second device of claim 9, wherein the second device receiving the first message comprises: receiving a sensing message from the UE.

11. The second device of claim 9, the second device receiving the first message comprising: receiving a request for the first status from the first device.

12. The second device of claim 9, wherein the second device receiving the first message comprises: receiving an indication from the UE, the indication indicating to the second device to provide the first status of the UE to the first device.

13. The second device of claim 11, wherein the request indication is whether a connection management (CM) status of the UE or a radio resource control (RRC) status of the UE is requested.

14. The second device of claim 11, wherein the request indicates that the second device provides the first status based on an update of the first status; and wherein the second device providing the first status of the UE to the first device comprises: based on determining that the first status is updated, providing the first device with the updated first status.

15. The second apparatus of claim 10, wherein the awareness message further comprises: a first set of statuses of the UE and a second set of sensing capability information of the UE, each of the sensing capability information being associated with one of the statuses, and the first set of statuses comprising a set of connection statuses of the UE or a set of energy statuses of the UE.

16. The second device of claim 15, wherein the second set of sensing capability information comprises one of: at least one indicator, each of the at least one indicator indicating whether the UE supports sensing in one of the statuses; at least one sensing capability parameter; at least one index of at least one set of sensing capability parameters; or at least one index of at least one sensing capability.

17. The second device of claim 9, wherein the connection status of the UE comprises a connection management (CM) status of the UE or a radio resource control (RRC) status of the UE, and the energy status of the UE comprises a battery level of the UE or a power mode of the UE.

18. The second device of any one of claims 9 to 17, wherein the first device comprises a sensing function (SF), and the second device comprises an access and mobility management function (AMF).

19. A method performed by a first device, the method comprising: obtaining a first status of a user equipment (UE), the first status of the UE comprising a connection status of the UE or an energy status of the UE; and determining, based at least on the first state of the UE, first awareness capability information of the UE for assigning an awareness task to the UE.

20. A method performed by a second apparatus, the method comprising: receiving a first message; determining, based on the first message, to provide a first apparatus with a first state of the UE, the first state of the UE comprising a connection state of the UE or an energy state of the UE; and providing the first apparatus with the first state of the UE for assigning an awareness task to the UE.

Images