Service continuity in integrated sensing and communication (ISAC)

Abstract

Various aspects of this disclosure relate to service continuity in Integrated Sensing and Communication (ISAC). In one aspect, based at least in part on the location of a target entity corresponding to an edge cell associated with a first network entity, the first network entity sends a first request message to at least one second network entity for information associated with a set of one or more third network entities. The first network entity receives a first response message including the information from the at least one second network entity. The first network entity then sends a second request message to at least one of the one or more third network entities in the set of one or more third network entities to continue sensing of the target entity by the at least one third network entity and one or more of at least one wireless device associated with the at least one third network entity. In response to the second request message, the first network entity also receives a report including sensing information associated with the target entity from the at least one third network entity in the set of one or more third network entities. In this way, service continuity in the ISAC system can be guaranteed.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically to achieving service continuity in Integrated Sensing and Communication (ISAC). 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 for 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 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Furthermore, the wireless communication system may also support wireless communication across multiple radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other radio access technologies applicable to 5G and beyond (e.g., sixth-generation (6G)).

[0003] Some wireless communication systems (including some communication devices) can support sensing capabilities and functions. These wireless communication systems may be referred to as Integrated Sensing and Communication (ISAC) systems or Joint Communication and Sensing (JCAS) systems. In some cases, ISAC systems can support intrusion detection in highways, railways, etc., to improve security. However, since some target entities (e.g., target sensing entities) may not be members of the ISAC, it may be desirable to provide improvements to coordinate (e.g., schedule) the sensing of target entities within the ISAC system. Summary of the Invention

[0004] This invention relates to base stations, user equipment, processors, and methods that support service continuity in ISAC.

[0005] Some implementations of the methods and apparatus described herein include: sending a first request message to at least one second network entity, at least in part, based on the location of a target entity corresponding to an edge cell associated with a first network entity, for information associated with a set of one or more third network entities; receiving a first response message from at least one second network entity, the first response message including the information associated with the set of one or more third network entities; sending a second request message to at least one of the one or more third network entities in the set of one or more third network entities to continue sensing of the target entity by at least one of the at least one third network entity and at least one wireless device associated with at least one third network entity; and receiving, in response to the second request message, a report including the sensing information associated with the target entity from at least one of the one or more third network entities in the set of one or more third network entities.

[0006] Some implementations of the methods and apparatus described herein may further include: measuring the quality level of perceived data for a target entity. In some implementations of the methods and apparatus described herein, sending the first request message includes: sending the first request message to at least one second network entity based on the quality level.

[0007] In some implementations of the methods and devices described herein, the first request message indicates the requested coverage area, and the set of one or more third network entities is determined based on the requested area and the corresponding coverage area provided by the set of one or more third network entities.

[0008] In some implementations of the methods and devices described herein, the information includes one or more of the following: a set of one or more identifiers (IDs) associated with a set of one or more third network entities; a set of one or more locations associated with a set of one or more third network entities; a set of one or more station types associated with a set of one or more third network entities; or a set of one or more coverage areas supported by a set of one or more third network entities.

[0009] In some implementations of the methods and apparatus described herein, the information includes first information, and some implementations of the methods and apparatus described herein may further include: determining a subset of one or more third network entities from a set of one or more third network entities, based at least in part on the first and second information. The second information includes one or more of the following: the position of the target entity, the velocity of the target entity, the size of the target entity, or the direction of movement of the target entity.

[0010] Some implementations of the methods and apparatus described herein may further include: obtaining sensing capability information associated with a subset of one or more third network entities, wherein the sensing capability information indicates at least one of the following: sensing capability, sensing mode, a set of one or more resources to be sensed by the subset of one or more third network entities; and, based on the sensing capability information, selecting at least one third network entity from the subset of one or more third network entities to continue sensing the target entity.

[0011] Some implementations of the methods and devices described herein may also include: sending a third request message to a subset of one or more third network entities to perform a perception test on the target entity; receiving a set of one or more results of the perception test from the subset of one or more third network entities; and selecting at least one third network entity from the subset of one or more third network entities to continue perceiving the target entity based on the set of one or more results.

[0012] Some implementations of the methods and devices described herein may also include: sending at least one sensing request for a target entity to a subset of one or more third network entities; receiving feedback from the subset of one or more third network entities regarding the at least one sensing request; and, based on the feedback, selecting at least one third network entity from the subset of one or more third network entities to continue sensing the target entity.

[0013] In some implementations of the methods and devices described herein, the second request message includes a first sensing start request that triggers a sensing process associated with at least one third network entity, and the first sensing start request includes an indication of at least one of the target entity's position, velocity, direction of movement, or size.

[0014] In some implementations of the methods and apparatus described herein, the report includes a second response message, wherein the second response message includes a first rejection indication or a first acceptance indication.

[0015] In some implementations of the methods and devices described herein, the second response message includes a first rejection indication, and the second response message also includes at least one of the following: a rejection reason related to at least one third network entity; or auxiliary information related to the perceived availability of at least one third network entity.

[0016] In some implementations of the methods and devices described herein, at least one of the following: a first sensing start request includes one or more sensing configurations supported by a first network entity; a second response message includes one or more sensing configurations supported by at least one third network entity; and the first sensing start request and the second response message are sent via an Xn interface between the first network entity and at least one third network entity.

[0017] Some implementations of the methods and devices described herein may also include: sending one or more sensing configurations supported by a first network entity in a message other than a first sensing start request; and receiving one or more sensing configurations supported by at least one third network entity in another message other than a second response message.

[0018] Some implementations of the methods and devices described in this paper may also include: using at least one third network entity to perform a perception process on the target entity.

[0019] Some implementations of the methods and devices described herein may include: stopping the sensing of a target entity based on sending a first sensing start request or the expiration of a first time period after sending the first sensing start request; stopping the sensing of a target entity based on receiving a second response message or the expiration of a second time period after receiving the second response message; or stopping the sensing of a target entity based on receiving a sensing result from at least one third network entity or the expiration of a third time period after receiving the sensing result.

[0020] Some implementations of the methods and apparatus described herein may further include: a transmission indication indicating that sensing of a target entity should be stopped based on at least one of the following: determining that the target entity remains within the coverage area of ​​a first network entity; receiving another response message including the acceptance indication from another network entity, which is a subset of one or more third network entities; or receiving a sensing result from that other network entity.

[0021] In some implementations of the methods and apparatus described herein, the second request message includes a wireless device information request for information relating to a set of wireless devices served by at least one third network entity. This wireless device information request triggers a sensing process associated with at least one wireless device in the set of wireless devices, and wherein the request indicates at least one of the following: a request for the wireless device, wherein the request includes at least one of a preferred wireless device location, mobility, expected sensing capability of the wireless device, and location accuracy of the wireless device; second information regarding the location, speed, size, or direction of movement of a target entity; or one or more sensing configurations supported by the first network entity.

[0022] In some implementations of the methods and apparatus described herein, the report includes a third response message, wherein the third response message includes a second rejection indication or a second acceptance indication.

[0023] In some implementations of the methods and apparatus described herein, the third response message includes a second rejection indication, and the third response message also includes at least one of the following: a rejection reason related to a wireless device served by at least one third network entity; or auxiliary information related to the perceived availability of a wireless device served by at least one third network entity.

[0024] In some implementations of the methods and apparatus described herein, the third response message includes a second acceptance indication, and the third response message also includes at least one of the following: an identifier of a subset of wireless devices and a corresponding sensing configuration supported by the subset of wireless devices; or an identifier of at least one wireless device selected by at least one third network entity to continue sensing.

[0025] In some implementations of the methods and devices described herein, the third response message includes an identifier of a subset of wireless devices, and some implementations of the methods and devices described herein may also include: selecting at least one wireless device from the subset of wireless devices for continued sensing.

[0026] Some implementations of the methods and devices described herein may also include: sending at least one indication of at least one wireless device and a configuration indication of the sensing configuration to be used to at least one third network entity; and performing the sensing process using at least one wireless device.

[0027] Some implementations of the methods and devices described herein may also include receiving sensing results from at least one wireless device via at least one third network entity.

[0028] In some implementations of the methods and devices described herein, the second request message includes a second sensing start request that triggers a sensing process associated with at least one third network entity and at least one wireless device.

[0029] Some implementations of the methods and devices described herein may also include receiving, from at least one third network entity, the sensing results of a sensing process performed by the at least one third network entity and at least one wireless device.

[0030] In some implementations of the methods and devices described herein, the report includes a fourth response message, which includes a third acceptance indication or a third rejection indication; and where the fourth response message includes a third rejection indication, the fourth response message also includes at least one of the following: a rejection reason associated with one or more of at least one third network entity or at least one wireless device; or auxiliary information related to the perceived availability of one or more of at least one third network entity or at least one wireless device.

[0031] In some implementations of the methods and devices described herein, the first network entity and at least one third network entity are network base stations, and at least one second network entity is configured with access and mobility functions (AMF).

[0032] Some implementations of the methods and apparatus described herein include: receiving from a first network entity a first request message for information associated with a set of one or more third network entities, wherein the first request message is sent at least in part based on the location of a target entity corresponding to an edge cell associated with the first network entity; and sending to the first network entity a first response message, the first response message including information associated with the set of one or more third network entities.

[0033] In some implementations of the methods and devices described herein, the information includes one or more of the following: a set of one or more identifiers (IDs) associated with a set of one or more third network entities; a set of one or more locations associated with a set of one or more third network entities; a set of one or more station types associated with a set of one or more third network entities; or a set of one or more coverage areas supported by a set of one or more third network entities.

[0034] Some implementations of the methods and apparatus described herein include: receiving a second request message from a first network entity to continue sensing of a target entity by a third network entity and one or more wireless devices associated with the third network entity; and, in response to the second request message, sending a report to the first network entity including sensing information associated with the target entity.

[0035] Some implementations of the methods and devices described herein may also include: receiving a third request message from a first network entity for performing a perception test on a target entity; performing a perception test on the target entity; and sending the results of the perception test to the first network entity.

[0036] Some implementations of the methods and devices described herein may also include: receiving a sensing request for a target entity from a first network entity; and sending a positive or negative response to the sensing request to the first network entity.

[0037] In some implementations of the methods and devices described herein, the second request message includes a first perception start request that triggers a perception process associated with a second network entity, and the first perception start request includes target entity information indicating at least one of the target entity's position, velocity, direction of movement, or size.

[0038] In some implementations of the methods and devices described herein, the report includes a second response message to a first sensing start request, wherein the second response message includes a first rejection indication or a first acceptance indication.

[0039] In some implementations of the methods and devices described herein, the report includes a second response message, wherein the second response message includes a rejection indication, and the second response message further includes at least one of the following: a rejection reason related to a third network entity; or auxiliary information related to the perceived availability of the third network entity.

[0040] In some implementations of the methods and devices described herein, at least one of the following is present: a first sensing start request includes one or more sensing configurations supported by a first network entity; a second response message includes one or more sensing configurations supported by a third network entity; and the first sensing start request and the second response message are sent via an Xn interface between the first network entity and the third network entity.

[0041] Some implementations of the methods and devices described herein may also include: receiving one or more sensing configurations supported by a first network entity in a message other than a first sensing start request; and sending one or more sensing configurations supported by a third network entity in a message other than a second response message.

[0042] Some implementations of the methods and devices described herein may also include: performing a sensing process on the target entity; or using a first network entity to perform a sensing process on the target entity.

[0043] Some implementations of the methods and devices described in this article may also include receiving an instruction to stop sensing a target entity.

[0044] In some implementations of the methods and apparatus described herein, the second request message includes a wireless device information request for information concerning a set of wireless devices served by at least one third network entity. This wireless device information request triggers a sensing process associated with at least one wireless device in the set of wireless devices, and wherein the wireless device information request indicates at least one of the following: a request for the wireless device, wherein the request includes at least one of a preferred wireless device location, mobility, expected sensing capability of the wireless device, and location accuracy of the wireless device; second information regarding the location, velocity, or direction of movement of a target entity; or one or more sensing configurations supported by the first network entity.

[0045] In some implementations of the methods and apparatus described herein, the report includes a third response message, wherein the third response message includes a second rejection indication or a second acceptance indication.

[0046] In some implementations of the methods and apparatus described herein, the third response message includes a second rejection indication, and the third response message also includes at least one of the following: a rejection reason related to the wireless device served by the third network entity; or auxiliary information related to the perceived availability of the wireless device served by the third network entity.

[0047] In some implementations of the methods and devices described herein, the third response message includes a second acceptance indication, and the third response message further includes at least one of the following: an identifier of a subset of wireless devices and a corresponding sensing configuration supported by the subset of wireless devices; or an identifier of at least one wireless device and a sensing configuration selected by a third network entity to continue sensing.

[0048] Some implementations of the methods and devices described herein may also include: receiving at least one indication from at least one wireless device and a configuration indication of a sensing configuration to be used from a first network entity; and performing a sensing process using the first network entity.

[0049] Some implementations of the methods and devices described herein may also include: receiving the sensing results of the sensing process from a first wireless device; and sending the sensing results to a first network entity.

[0050] In some implementations of the methods and devices described herein, the second request message includes a second sensing start request that triggers a sensing process associated with a third network entity and at least one wireless device.

[0051] In some implementations of the methods and devices described herein, the report includes a fourth response message, which includes a third acceptance indication or a third rejection indication, and where the fourth response message includes a third rejection indication, the fourth response message also includes at least one of the following: a rejection reason associated with one or more of at least one third network entity or at least one wireless device; or auxiliary information related to the perceived availability of at least one third network entity or at least one wireless device.

[0052] Some implementations of the methods and devices described herein may also include: sending a request for sensing capability to a set of wireless devices served by a third network entity; receiving corresponding sensing capability information from the set of wireless devices; and selecting at least one wireless device from one or more wireless devices to continue sensing based on the corresponding sensing capability information.

[0053] Some implementations of the methods and devices described herein may also include: determining a sensing configuration for a sensing process; sending the sensing configuration to at least one wireless device; and performing the sensing process using at least one wireless device.

[0054] Some implementations of the methods and devices described herein may also include: sending to a first network entity the sensing results of a sensing process performed by a third network entity using at least one wireless device.

[0055] Some implementations of the methods and apparatus described herein include: receiving an instruction for a sensing configuration from a third network entity serving a wireless device or from a first network entity via a third network entity, the sensing configuration being used by one or more of the third network entity and / or wireless devices to continue a sensing process for a target entity; and using at least one of the first network entity or the third network entity to perform the sensing process.

[0056] Some implementations of the methods and devices described herein may also include transmitting at least one of location information, mobility information, direction of movement information, or sensing capability information to a third network entity. Attached Figure Description

[0057] Figure 1A An example of a wireless communication system supporting transmission optimization according to various aspects of this disclosure is illustrated.

[0058] Figures 1B to 1G The illustration shows an example scenario of the perception service of the ISAC system according to various aspects of this disclosure.

[0059] Figure 2 An example signaling diagram is shown, illustrating an example process for supporting service continuity in ISAC according to various aspects of this disclosure.

[0060] Figure 3A The illustration shows an example signaling diagram of the selection of a third network entity to support service continuity according to various aspects of this disclosure.

[0061] Figure 3B The illustration shows an example signaling diagram of a network-based sensing scenario that supports service continuity in various aspects according to this disclosure.

[0062] Figures 4A to 4B The illustration shows an example signaling diagram of a perception scenario involving a UE that supports service continuity according to various aspects of this disclosure.

[0063] Figures 5 to 8 An example of a device supporting service continuity in ISAC according to various aspects of this disclosure is illustrated.

[0064] Figures 9 to 12 An example of a processor supporting service continuity in ISAC according to various aspects of this disclosure is illustrated.

[0065] Figures 13 to 16 The diagram illustrates a flowchart of a method for supporting service continuity in ISAC according to various aspects of this disclosure.

[0066] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0067] 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. The disclosure described herein can be implemented in various ways different from those described below.

[0068] 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.

[0069] In this disclosure, references to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., indicate that the described embodiments may include a particular feature, structure, or characteristic, but it is not necessary for every embodiment to include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, whether explicitly described or not, it is considered that implementing such a feature, structure, or characteristic in conjunction with other embodiments is within the knowledge of those skilled in the art.

[0070] 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, a first element may also be referred to as a second element without departing from the scope of the embodiments, 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.

[0071] 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, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to include the plural forms. It should also be understood that the terms “comprising,” “having,” and / or “including”, when used herein, specify the presence of the stated 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.

[0072] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as 5G New Radio (NR), LTE, LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband IoT (NB-IoT), etc. Furthermore, communication between the UE and network devices in a communication network can be performed according to any applicable communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), 4G, 4.5G, 5G communication protocols, and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communication technologies, there will also be communication technologies and systems of future types embodying this disclosure. This should not be construed as limiting the scope of this disclosure to the aforementioned systems.

[0073] As used herein, the term "network device" generally refers to a node in a communication network through which a UE can access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), a Radio Access Network (RAN) node, an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), infrastructure equipment for Vehicle-to-Everything (V2X) communication, a Transmit and Receive Point (TRP), a Receive Point (RP), a Remote Radio Header (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femtocell base station (BS), a picocell, etc.). A network device can also refer to a network function (NF) in the core network, such as a Service Management Function (SMF), an Access and Mobility Management Function (AMF), a Policy Control Function (PCF), a User Plane Function (UPF), or devices with similar functions in future network architectures, etc.

[0074] As used herein, the term “UE” or “terminal device” generally refers to any end device capable of wireless communication. By way of example and not limitation, a UE or terminal device may also be referred to as a communication device, end-user equipment, subscriber station (SS), unmanned aerial vehicle (UAV), portable subscriber station, mobile station (MS), or access terminal (AT). The UE may include, but is not limited to, mobile phones, cellular phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable UEs, personal digital assistants (PDAs), portable computers, desktop computers, image capture UEs (such as digital cameras), gaming UEs, music storage and playback devices, in-vehicle wireless UEs, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices (e.g., remote surgical equipment), industrial equipment (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, and so on. In the following description, the terms “UE,” “communication device,” “terminal,” “terminal equipment,” and “UE” are used interchangeably.

[0075] As mentioned above, in ISAC's perception service, perception service scheduling becomes a critical aspect because the target entity is not a member of the communicating parties. That is, since the target entity is not a cooperating communicator, it is difficult to utilize information from the target entity to assist its perception process. Furthermore, perception scheduling is typically performed by core network (CN) devices or functions (e.g., perception management functions, SF). In turn, this perception scheduling mechanism may consume more signaling overhead, such as reports from perception nodes and scheduling configurations from CN devices / functions, and therefore, the "perception handover" delay may be longer.

[0076] In ISAC, several use cases relate to intrusion detection and target tracking, such as pedestrian / animal intrusion detection on highways, perception for railway intrusion detection, and perception for drone intrusion detection. Given the wide coverage and fixed location of base stations, they may be suitable as perception nodes for use cases involving large-area detection and long-distance tracking. In these use cases, the perception node (i.e., the base station, which can collaborate with the perception UE) detects target entities with specific periodicity and configuration. Once a target entity is detected, the perception node reports to the CN / server and tracks the target entity with the corresponding configuration until the target entity moves out of the defined area, such as railways, highways, or smart grid sections.

[0077] In certain scenarios, during the tracking of a target entity, the entity may move out of the current base station's sensing coverage area due to its mobility, resulting in a change of sensing node. Unlike the mobility issues of traditional communication terminal equipment (e.g., UE handover within a cell), the target entity may not be a device and may not support signal transmission and measurement. It is necessary to investigate how to ensure service continuity during sensing node changes. Furthermore, consideration can be given to how to reduce signaling overhead and latency for CN equipment. For clarity, references will be provided. Figures 1B to 1G Let's discuss some specific scenarios further.

[0078] In light of the foregoing discussion, some embodiments of this disclosure provide a solution for implementing service continuity in ISAC. In this solution, based at least in part on the location of a target entity corresponding to an edge cell associated with a first network entity, the first network entity transmits a first request message to at least one second network entity for information associated with a set of one or more third network entities. The first network entity receives a first response message from the at least one second network entity, the first response message including the information associated with the set of one or more third network entities. The first network entity then transmits a second request message to at least one of the at least one third network entity in the set of one or more third network entities, so that awareness of the target entity continues by the at least one third network entity and at least one wireless device associated with the at least one third network entity. In response to the second request message, the first network entity also receives a report from the at least one third network entity in the set of one or more third network entities including the awareness information associated with the target entity.

[0079] In this way, the current network device responsible for the target entity can directly request other suitable network entities (or wireless devices served by these network devices) to assist in continuing to sense the target entity. Thus, if the sensing quality of the current network device fluctuates, for example, if the target entity moves to the edge covered by the first network entity, the continuity of sensing services in ISAC can be guaranteed. Furthermore, the signaling overhead between network devices and CN devices can be reduced, thereby reducing sensing "handover" latency.

[0080] Figure 1A An example of a wireless communication system (or communication network) 100 supporting transmission optimization in an IoT system according to various aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 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 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 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 100 may support radio access technologies beyond 5G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

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

[0082] Network entity 102 may provide a geographic coverage area 112 within which it can provide services (e.g., voice, video, packet data, messaging, broadcasting, etc.) to one or more UEs 104. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, e.g., 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 may overlap, but these different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0083] One or more UEs 104 may be distributed within a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or any other suitable term. In some implementations, UE 104 may be referred to as a unit, site, 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 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0084] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1A The diagram illustrates some examples of UE 104. For example... Figure 1A As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UE 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or other network devices). Additionally or alternatively, UE 104 may support communication with other network entities 102 or UE 104 that can act as relays in the wireless communication system 100.

[0085] UE (or terminal device) 104 may also support direct wireless communication with other UEs 104 via communication link 114. For example, UE 104 may 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 may support direct wireless communication with another UE 104 via a PC5 interface.

[0086] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or other network interfaces). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or other network interfaces). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or 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 radio heads, smart radio heads, or transmit-receive points (TRPs).

[0087] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (e.g., a network configuration led by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near-real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) system, or any combination thereof.

[0088] 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). One or more components of network entity 102 in a decomposed RAN architecture can be located in the same location, or one or more components of network entity 102 can be located in distributed locations (e.g., different 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)).

[0089] The functional decomposition between CU, DU, and RU can be flexible and can support different functionalities depending on 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, a protocol stack functional decomposition can be used between the CU and DU, allowing the CU to support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., RRC, Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functionalities, such as Layer 1 (L1) (e.g., Physical Layer (PHY)) or L2 (e.g., Radio Link Control (RLC) layer, MAC layer) functionalities and signaling, and each DU or RU can be at least partially controlled by the CU.

[0090] Alternatively or concurrently, a functional split of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack, while the RU can support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and DU, or between the DU and RU, can be within a protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer can be performed by another of the CU, DU, or RU).

[0091] The CU can also be functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul 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 midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between protocol stack layers supported by the respective network entities 102 communicating via such communication links.

[0092] 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 (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) and user plane entities that route packets or interconnect with external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)). In some implementations, control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) of one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0093] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or other network interfaces). 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 with core network 106 via network entity 102 (e.g., Protocol Data Unit (PDU) session, etc.). Core network 106 can use the established session (e.g., established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session can serve as an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0094] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (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 sets of parameters.

[0095] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0096] Time intervals for resources (e.g., communication resources) can be organized according to frames (also called 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.

[0097] Alternatively or additionally, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include several time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz can respectively utilize one 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. Each time slot may include several (e.g., a certain number) symbols (e.g., OFDM symbols). In some implementations, the number (e.g., the quantity) of time slots in a subframe may depend on the parameter set. 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 interval), a time slot may include 12 symbols. For both normal and extended cyclic prefixes, the relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame can depend on the parameter set. It should be understood that the first parameter set (e.g., μ=0) associated with the first subcarrier interval (e.g., 15 kHz) can be used interchangeably between subframes and slots.

[0098] In the wireless communication system 100, 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 100 can support one or more operating frequency bands, such as frequency ranges specified as FR1 (410MHz–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 through one or more of the operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other equipment or devices, for short-range, high-data-rate capabilities.

[0099] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with: a first parameter set (e.g., μ=0) that includes a subcarrier spacing of 15 kHz; a second parameter set (e.g., μ=1) that includes a subcarrier spacing of 30 kHz; and a third parameter set (e.g., μ=2) that includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with a third parameter set (e.g., μ=2) that includes a subcarrier spacing of 60 kHz; and a fourth parameter set (e.g., μ=3) that includes a subcarrier spacing of 120 kHz.

[0100] Figures 1B to 1G The illustration depicts an example scenario of the perception service of an ISAC system according to various aspects of this disclosure. Figures 1B-1G In the context, network entity 102 can be as follows: Figure 1A The network device 102 shown, and the wireless device (or UE) 104 (e.g., UE 1, UE 2, and UE 3) can be the terminal device 104 shown in FIG1. ​​Furthermore, the target entity is the object to be perceived.

[0101] Specifically, Figures 1B to 1D This relates to service continuity in network-based scenarios. In this disclosure, a network-based sensing scenario can refer to a sensing scenario in which a target entity is sensed by one or more network entities (e.g., a base station), without involving wireless devices (e.g., user equipment) accessing the network via that network entity. Figure 1B As shown, network entity 1 detects the target entity and tracks its trajectory within the perception coverage area of ​​network entity 1. Then, as... Figure 1C As shown, when a target entity moves to the boundary between network entity 1 and network entity 2, various sensing modes can be configured, including a cooperative mode (e.g., network entity 1 sends an RS and network entity 2 receives an RS) to ensure sensing performance and service continuity. Figure 1D As shown, when the target entity moves into the sensing coverage area of ​​network entity 2, network entity 1 may no longer track the target entity, and the target entity will subsequently be sensed by network entity 2.

[0102] Figures 1E to 1G Service continuity in scenarios involving UE participation. In this disclosure, a UE-participated sensing scenario can refer to a sensing scenario in which at least one wireless device participates in sensing a target entity. For example... Figure 1E As shown, initially, network entity 1 and wireless device 3 cooperate to detect and track the target entity. Then, as... Figure 1F As shown, when a target entity moves to the boundary between network entity 1 and network entity 2, network entity 1 cannot find a suitable sensing wireless device within its coverage area (e.g., the positioning accuracy or sensing capability of wireless device 1 is insufficient). In this case, gNB1 can cooperate with wireless device 2 within the coverage area of ​​network entity 2 to track the target entity. Conversely, as... Figure 1G As shown, when a target entity moves into the sensing coverage area of ​​network entity 2, it can request network entity 2 to cooperate with UE2 to track the target entity.

[0103] Additionally, as mentioned above, the scheduling of the perception process for the target entity is typically determined by the CN device (e.g., the SF device). That is, the SF device can request network devices or terminal devices to perform subsequent perception processes, rather than the network devices directly requesting these network devices or terminal devices. With the introduction of a distributed ISAC architecture, network devices can integrate at least a portion of the SF capabilities, responsible for calculating perception results and requesting neighboring gNBs to track the target entity. In this case, the Xn interface between network devices can be extended to support perception-related functions, such as perception activation (deactivation), perception measurement reporting, and perception configuration exchange. Therefore, in a distributed architecture, it is necessary to study the service continuity guarantee issue based on perception scenarios involving the network and / or UE. Consequently, in this case, signaling overhead and handover latency may be reduced.

[0104] Figure 2An example signaling diagram is illustrated, which shows an example process 200 supporting service continuity in ISAC according to various aspects of this disclosure. Process 200 may involve a first network entity 201, a second network entity 203, a third network entity 205, and a wireless device 207. In some examples, examples of the first network entity 201 and the third network entity 205 may be... Figure 1A The network entity 102 shown is an example of the second network entity 203. Figure 1A The core network 206 is shown. An example of wireless device 207 could be... Figure 1A The UE 104 shown is illustrated. It should be understood that although process 200 is applied to... Figure 1A In the communication system 100, this process can also be applied to other communication scenarios with similar problems. In some examples, the first network entity 201, the second network entity 203, and / or the third network entity 205 may include a processor and a transceiver coupled to the processor. The wireless device 207 may include a processor and a transceiver coupled to the processor. For ease of discussion, the signaling process 200 will be referred to... Figures 1A to 1G A description is provided. It should be understood that although signaling procedure 200 is... Figures 1A to 1G This signaling process 200 is described in the context of communication, but it can also be applied to other communication scenarios.

[0105] In process 200, in some examples, the first network entity 201 sends a (211) first request message to at least one second network entity 203, based at least in part on the location of a target entity corresponding to an edge cell associated with the first network entity 201. This first request message is intended to obtain information associated with a set of one or more third network entities. For ease of illustration, an example of at least one second network entity is the illustrated second network entity 203.

[0106] In some embodiments, whether to send the first request message may depend on the sensing results and / or sensing quality at the first network entity 201. For example, if the sensing results indicate that the target entity is located at the edge of the coverage area of ​​the first network entity 201, then the first network entity 201 may trigger a "service continuity procedure," for example, requesting a neighboring network entity to continue sensing. Additionally or alternatively, the first network entity 201 may measure (210) the quality level of the sensing data of the target entity sensed by the first network entity 201, i.e., monitor the sensing performance of the target. Then, based on the quality level, for example, if the quality level is below, above, or equal to a quality threshold, the first network entity 201 may send (211) the first request message 212 to the second network entity 203. In some embodiments, the quality level may be represented by signal strength or a sensing result calculated based on the sensing data. For example, if the signal strength decreases, it can be determined that the target entity is moving away from the first network entity 201. In this case, the first network entity 201 may request other network entities (e.g., neighboring base stations) or wireless devices to continue sensing in order to ensure the continuity of sensing services.

[0107] Upon receiving the first request message (213), the second network entity 203 sends (215) information 216 associated with a set of one or more third network entities to the first network entity 201. Therefore, the first network entity 201 receives (217) information 216 from the second network entity 213 to assist the first network entity 201 in ensuring that the target entity being perceived by the first network entity 201 (e.g., Figures 1B-1G The perceived continuity of the pedestrian (as shown in the figure). In some embodiments, the second network entity 203 may be configured with network functions having information on multiple other network entities (e.g., multiple base stations). For example, the second network entity 203 may be configured with Access and Mobility Management (AMF) functions. Alternatively, the second network entity 203 may be configured with any other similar network functions.

[0108] Additionally, to obtain information about suitable network entities, the first request message 212 may indicate the requested coverage area (i.e., the coverage area provided by a set of one or more third network entities), for example, the area where the target entity is located and / or the area it is moving to. Conversely, the second network entity 203 may determine the set of one or more third network entities based on the requested coverage area and its respective coverage area (i.e., the coverage area of ​​one or more network entities). Furthermore, in some embodiments, information 216 may include at least one of the following: a set of one or more identifiers (IDs) associated with the set of one or more third network entities; a set of one or more locations associated with the set of one or more third network entities; a set of one or more station types associated with the set of one or more third network entities; or a set of one or more coverage areas supported by the set of one or more third network entities. For example, the types of third network entities may include macro stations and micro stations. Generally, macro stations have greater transmission power and coverage area than micro stations, which manage smaller cells.

[0109] See also Figure 2 Using information 216, the first network entity 201 can determine (219) a subset of one or more third network entities to help ensure perception continuity. In some embodiments, based on second information of at least one of the target entity's position, velocity, size, or direction of movement, the first network entity 201 can determine a subset of one or more third network entities from a set of one or more network entities. For example, the first network entity 201 can determine a subset of one or more third network entities whose coverage areas are associated with the target entity's position and direction of movement. In some embodiments, the third network entities in the subset of one or more third network entities may have coverage areas traversed by the possible movement trajectories of the target entity.

[0110] Then, within a subset of one or more third network entities, a selection of a target network entity can be performed to participate in the sensing process of that target entity. In some embodiments, this selection is performed by a first network entity 201. For example, the first network entity 201 may transmit (223) capability requests (223-1 and 223-2) to third network entities within a subset of one or more third network entities. In this disclosure, signaling between network devices (e.g., the first network entity 201 and the third network entity 205) can be transmitted via the Xn interface. Without any limitations, signaling between network devices may also be transmitted via any other interface (e.g., a newly defined interface in the future). In turn, upon receiving (225) capability requests (223-1 and 223-2), a subset of one or more third network entities, including the third network entity 205, may send (227) capability information 229-1 to the first network entity 201. This capability information may indicate at least one of the following: sensing capability, sensing mode, and one or more resource sets for sensing by a subset of one or more third network entities. The sensing mode may include, for example, a bistatic sensing mode, a monostatic sensing mode, etc. Then, based on this capability information, the first network entity 201 can select (233) at least one third network entity for continued sensing. For example, the first network entity 201 can select a third network entity 205. For ease of illustration only, the embodiments are discussed with reference to the third entity 205, which represents at least one third network entity. It should be understood that the first network entity 201 can select the third network entity 205 and one or more other network entities as target third network entities for continued sensing.

[0111] Alternatively, the first network entity 201 may send (221) at least one sensing request for a target entity to a subset of one or more third network entities. Upon receiving (225) the at least one sensing request, the subset of one or more third network entities, including the third network entity 205, may determine whether they are capable of supporting the at least one sensing request for the target entity. Then, the subset of one or more third network entities may send corresponding feedback to the first network entity 201 based on the determination of the at least one sensing request. In a specific example, if a third network entity is capable of supporting the sensing request, then the third network entity may send (227) a positive response 229-1. Otherwise, the third network entity may send (227) a negative response 229-1. Then, the first network entity 201 may select (233) at least one third network entity based on the positive response and / or the negative response.

[0112] Alternatively, at least one third network entity can be selected based on the perception task. In some embodiments, the first network entity 201 can send (221) third request messages (223-1 and 223-2) to a subset of one or more third network entities for performing a perception test on the target entity. For example, the first network entity 201 can trigger a subset of one or more third network entities to perform a perception test task on the target, and then compare the task results to determine whether they are qualified. Subsequently, the first network entity 201 can receive one or more results of the perception test from the third network entities in the subset of one or more third network entities. Based on one or more results, the first network entity 201 can select (233) at least one third network entity from the subset of one or more third network entities for continuing perception, i.e., performing the perception process. Then, after selecting (233) at least one third network entity, the first network entity 201 can request the selected at least one third network entity (e.g., third network entity 205) and / or at least one terminal device served by the third network entity to trigger the perception process to ensure perception continuity. Reference will be made only for ease of discussion. Figure 3A Further discussion on the selection of third network entities.

[0113] Figure 3A The illustration is an example signaling diagram 300A illustrating the selection of a third network entity to support service continuity according to various aspects of this disclosure. Without any limitations, in Figure 3A In this context, gNB1 can be like this: Figure 2 The first network entity 201 shown, AMF can be as follows: Figure 2 The second network entity 203 shown, and the candidate gNB may include, for example, Figure 2 The third network entity 205 shown.

[0114] In signaling diagram 300A, gNB1 can monitor the sensing performance against a target entity. gNB1 can then assess the quality of the sensing data (e.g., via signal strength) or calculate sensing results based on the sensing data to determine whether to trigger subsequent operations. Based on the assessed quality of the sensing data, gNB1 can request (310) neighboring gNB information from AMF 203. The request message (i.e., first request 212) can also indicate the required area for the gNB to provide service / coverage. In turn, AMF 203 responds (320) with gNB information (i.e., information about multiple network devices) to gNB1. The gNB information may include the gNB's ID, location, type (e.g., macro or micro), and coverage area (e.g., multiple other network entities). Specifically, macro stations have greater transmit power and coverage area than micro stations. Micro stations manage small cells.

[0115] Based on the received gNB information and the location and possible direction of movement of the target entity, gNB1 201 can determine candidate gNBs. That is, gNB1 201 can identify one or more neighboring gNBs for target sensing. Then, to determine the target gNB, gNB1 201 can communicate with the selected candidate gNBs via the Xn interface to obtain their sensing capabilities, supported sensing modes, available sensing resources, etc. Based on the obtained information, gNB1 selects one or more gNBs for sensing the target entity.

[0116] Alternatively, in some embodiments, gNB1 201 may trigger these candidate gNBs to perform test perception tasks on the target and compare the results to determine whether they are qualified. Alternatively, gNB1 201 may also send perception requirements to selected candidate gNBs and then determine one or more gNBs for target perception based on the responses from the selected candidate gNBs.

[0117] Return to reference Figure 2 After selecting (233) at least one third network entity, the first network entity 201 sends (235) a second request message 237 to the at least one third network entity to continue sensing of the target entity by the at least one third network entity and one or more of the at least one wireless devices associated with the at least one third network entity. The second request message is used to trigger a sensing process associated with the at least one third network entity and / or the wireless devices served by the at least one third network entity. For example, assuming that the selected third network entity 203 is selected as the at least one third network entity, then the at least one third network entity includes the third network entity. In this case, the second request message 237 can trigger a sensing process associated with the third network entity 205 and the wireless devices served by the third network entity.

[0118] In some embodiments, the second request message can trigger a sensing process in a network-based sensing scenario. In this scenario, a first network entity 201 and at least one third network entity can collaboratively perform a sensing process on a target entity. In process 200, the sensing process for the network-based sensing scenario is mainly discussed through the operations in module 245.

[0119] In some embodiments, the second request message 237 may be a perception start request (also referred to herein as a "first perception start request") that can trigger a perception process associated with the third network entity 205. The first perception start request 237 may include target entity information indicating at least one of the target entity's position, velocity, direction of movement, or size. Furthermore, the first perception start request 237 may also include one or more perception configurations supported by the first network entity 201.

[0120] Furthermore, in response to the first sensing start request 237, i.e., in response to the second request message 237, the third network entity 205 sends a report 243 to the first network entity 201, including sensing information associated with the target entity. In some embodiments, the report 243 may include a first response message. The first response message may include a first rejection indication or a first acceptance indication. Moreover, if the first response message includes a rejection indication, the first response message 243 may also include a rejection reason associated with the third network entity 205, and / or auxiliary information related to the sensing availability of the third network entity 205. In the example, the third network entity 205 may reject the first sensing start request due to reasons such as high workload, lack of sensing capability, or unsupported sensing modes. In this case, the first response message 243 may include a rejection reason and auxiliary information, such as when the third network entity 205 might be available.

[0121] Additionally, if the third network entity 203 accepts the first sensing start request, the first response message 243 may also include one or more sensing configurations supported by the third network entity 203. For example, the first response message may include suggested sensing configurations, such as a collaborative mode.

[0122] Then, the first network entity 201 may accordingly receive (244) a first response message 243. If the first response message 243 includes an acceptance indication, the first network entity 201 may utilize the third network entity 205 to perform a sensing process. To perform the sensing process, the first network entity 201 and the third network entity 205 may pre-perform configuration coordination. For example, as mentioned above, the first network entity 201 and the third network entity 205 may negotiate the sensing configuration to be used via the first sensing start request 237 and the first response message 243. Alternatively, the configuration coordination for the cooperative sensing mode may also be separate from the first sensing start request and the first response message. In some embodiments, the first network entity 201 may send one or more sensing configurations supported by the first network entity 201 in a message other than the first sensing start request. Then, the first network entity 201 may receive one or more sensing configurations supported by the third network entity 205 in another message other than the first response message.

[0123] Additionally, the first network entity 201 (i.e., the current sensing node) can stop sensing the target entity as needed or instruct the third network entity 205 to stop sensing. In some embodiments, the first network entity 201 can stop sensing the target entity after sending the first sensing start request 237 or after a first time period expires following the sending of the first sensing start request 237. Alternatively, the first network entity 201 can stop sensing the target entity after receiving the first response message 243 or after a second time period expires following the receiving of the first response message 243. Alternatively, the first network entity 201 can stop sensing the target entity after receiving a sensing result from the third network entity 205 or after a third time period expires following the receiving of the sensing result. In this case, at least one third network entity (e.g., the third network entity 205) can be responsible for the target entity, i.e., the sensing service switches from the first network entity 201 to at least one third network entity.

[0124] Additionally or alternatively, in some cases, for example, if the perceived quality recovers to an acceptable level, the first network entity 201 may instruct the third network entity 205 to stop the sensing process. For example, if the first network entity 201 determines that the target entity remains within the coverage area of ​​the first network entity, the first network entity 201 may instruct the third network entity 205 to stop the sensing process. Additionally or alternatively, if the first network entity 201 receives another response message including an acceptance indication from another network device of at least one third network entity, the first network entity 201 may instruct the third network entity 205 to stop the sensing process. Additionally or alternatively, if the first network entity 201 receives a sensing result from that other network device, the first network entity 201 may instruct the third network entity 205 to stop the sensing process. Reference will be made only for clarity of discussion. Figure 3B The perception process in network-based perception scenarios will be further discussed.

[0125] Figure 3B An example signaling diagram 300B illustrating a network-based sensing scenario supporting service continuity according to various aspects of this disclosure is shown. Without any limitations, in Figure 3B In this context, gNB1 can be like this: Figure 2 The first network entity 201 shown is shown, while gNB2 can be as follows: Figure 2 At least one third network entity shown (e.g., third network entity 205).

[0126] In signaling diagram 300B, to trigger a neighboring gNB to begin sensing, gNB1 can trigger a neighboring gNB to begin sensing. For example, gNB1 sends a sensing start request 335 to the selected gNB (i.e., gNB2 205). The start request message 335 may include information about the target entity, such as its location, speed, direction of movement, size, etc. Furthermore, message 335 may include a suggested sensing configuration, such as a suggested sensing mode and a configuration for a cooperative mode (e.g., gNB1 sends a reference signal (RS), and gNB2 receives the RS). The selected gNB then responds to gNB1 with a response message 360 ​​(i.e., a first response message). This response message may indicate acceptance or rejection. For example, the selected gNB205 may reject the request due to reasons such as high workload, lack of sensing capability, or unsupported sensing mode. The rejection response message may include the reason for rejection and supplementary information, such as when it will be available. If the selected gNB accepts the request, the acceptance message may include a suggested sensing configuration for, for example, a cooperative mode. Furthermore, the configuration coordination 365 used for collaborative modes can also be separated from the perception start request and response.

[0127] Additionally, as mentioned above, gNB1 201 may stop sensing / tracking a target when it sends a sensing start request to a selected gNB, or after a certain period of time has elapsed since gNB1 201 sent the sensing start request to the selected gNB. Alternatively, gNB1 201 may stop sensing / tracking a target when it receives a valid response (i.e., acceptance) from at least one of the selected gNBs, or after a certain period of time has elapsed since gNB1 201 received a valid response (i.e., acceptance) from at least one of the selected gNBs.

[0128] Alternatively, gNB1 201 may stop sensing / tracking a target when it receives a sensing result 370 from at least one of the selected gNBs indicating that a target entity has been detected, or after a period of time has elapsed since gNB1 201 received the sensing result from at least one of the selected gNBs. Furthermore, if gNB1 detects that a target entity has not moved out of its coverage area, and / or gNB1 receives an active response or sensing result (indicating that a target has been detected) from at least one of the other selected gNBs, gNB1 201 may notify at least one of the selected gNBs 375 to stop sensing the target.

[0129] Return to reference Figure 2In addition to network-based sensing scenarios, or as an alternative to network-based sensing scenarios, the second request message 237 can also trigger a sensing process in a sensing scenario involving the UE. In the first scenario, this sensing process in a sensing scenario involving the UE can be performed by the first network entity 201 and at least one wireless device served by a selected third network entity (e.g., third network entity 205). For the sake of clarity only, as... Figure 1E As shown, this sensing process can be performed by gNB 1 and UE 2. Alternatively, in a second scenario, this sensing process in the sensing scenario involving the UE can be performed by a selected third network entity (e.g., third network entity 205) and at least one radio device served by the selected third network entity. This is merely for clarity. Figure 1E As shown, this sensing process can be performed by gNB 2 and UE 2.

[0130] The first scenario will be further discussed with reference to the operation in block 250. In this case, the second request message 237 may be a wireless device information request, which is directed to information relating to a set of wireless devices served by at least one third network entity. In some embodiments, the wireless device information request may indicate at least one of the following: a request for a wireless device, wherein the request includes at least one of the following: a preferred wireless device location, mobility, the expected sensing capability of the wireless device, the location accuracy provided by the wireless device; second information regarding the location, speed, size, or direction of movement of a target entity; or one or more sensing configurations supported by the first network entity 201.

[0131] Upon receiving the third request 237, at least one third network entity (e.g., third network entity 205) may collect information about the corresponding terminal device. Taking third network entity 205 as an example, third network entity 205 may request the collection of information about the wireless devices served by third network entity 205 based on wireless device information requests. For example, third network entity 205 may request the served terminal devices to report their information, such as the terminal device's location, mobility, sensing capabilities of the wireless device, and the positioning accuracy of the wireless device.

[0132] At least one third network entity (e.g., third network entity 205) may send a second response message to the first network entity 201. For example, the second response message may be included in report 243. The second response message may include at least one of the following: a rejection reason related to the terminal device served by the third network entity 205; or auxiliary information related to the perceived availability of the terminal device served by the third network entity 205.

[0133] For example, the third network entity 205 may reject the request due to reasons such as a lack of suitable sensing UE. If the second response message indicates rejection, the second response message may also include the reason for rejection and auxiliary information, such as when the sensing UE might be available.

[0134] Furthermore, if the second response message indicates acceptance, the first network entity 201 and / or the third network entity 205 can select at least one wireless device (e.g., wireless device 207) to continue sensing. In some embodiments, the at least one wireless device is determined by the first network entity 201. For example, the second response message may also include an identifier of the set of wireless devices selected for the sensing process and a corresponding sensing configuration supported by the set of wireless devices. In this case, based on the second response message, the first network entity 201 can select at least one wireless device (e.g., wireless device 207) from the set of wireless devices for the sensing process. Then, the first network entity 201 can send at least one indication of the at least one wireless device (e.g., the ID of wireless device 207) and a configuration indication of the sensing configuration to be used. Furthermore, the third network entity 205 can notify the determined at least one terminal device (e.g., wireless device 207) that the wireless device 207 has been selected for the sensing process. Additionally, the third network entity 205 can also inform the first network entity 201 of the sensing configuration to be used. The first network entity 201 can then utilize the at least one terminal device (e.g., wireless device 207) to perform the sensing process.

[0135] Alternatively, at least one terminal device used for the sensing process can be determined by a third network entity 205. In this case, the second response message may include the identifier of at least one terminal device, which includes a wireless device selected by the third network entity 205 for the sensing process. The first network entity 201 can then negotiate a sensing configuration with the at least one terminal device selected by the third network entity 205 and accordingly perform the sensing process using the at least one terminal device. In some embodiments, at least one terminal device (e.g., a wireless device) may send sensing results to the first network entity 201 via the third network entity 205. The first network entity 201 may accordingly receive sensing results from the at least one terminal device. (For clarity only, see references to...) Figure 4A The perception process performed by the first network entity 201 and at least one terminal device in a perception scenario involving the UE is further discussed.

[0136] Figure 4A The illustration shows an example signaling diagram 400A of a sensing scenario involving a UE supporting service continuity according to various aspects of this disclosure. Without any limitations, in Figure 4A In this context, gNB1 can be like this: Figure 2The first network entity 201, gNB2 shown can be as follows: Figure 2 At least one third network entity (e.g., third network entity 205) is shown, and the UE can be as follows: Figure 2 The wireless device 207 shown is illustrated.

[0137] Similar to network-based sensing scenarios, gNB1 201 monitors sensing performance against a target. gNB1 201 can then assess the quality of the sensing data (e.g., via signal strength) or calculate sensing results based on the sensing data to determine whether to trigger subsequent operations. In UE-involved sensing scenarios, gNB1 and the UE collaborate to sense / track a target entity, and this UE is located within the coverage area of ​​gNB2. Similarly, gNB1 201 obtains neighboring gNB information from AMF 203. Request messages can also instruct the gNBs to provide service / coverage in the desired area. AMF 203 responds to gNB1 201 with gNB information (i.e., information 216 of multiple network devices). The gNB information may include the gNB's ID, location, and coverage area. Based on the received gNB information and the target entity's location and possible direction of movement, gNB1 determines which gNB (i.e., at least a third network entity) to interact with.

[0138] Then, as Figure 4A As shown, gNB1 201 and selected neighboring gNBs (i.e., at least one third network entity) collaborate to determine the sensed UE (i.e., at least one terminal device including a radio device) and the sensed configuration. gNB1 201 requests (410) sensed UE information from the selected neighboring gNB, i.e., sends a radio device information request. As mentioned above, the request message may indicate requirements for the sensed UE, such as preferred UE location and / or mobility, expected UE sensed capability, required UE location accuracy, etc. Message 410 may also include information about the target entity, such as speed, size, location, etc., which the selected neighboring gNB can use to select a suitable sensed UE and / or provide a suitable configuration for the sensed UE. In addition, the message may also include resources / configurations supported by gNB1 201. Accordingly, based on the third request, gNB2 can obtain (415) sensed UE information from the UE it serves.

[0139] Then, the selected neighboring gNB responds with the sensed UE information to gNB1 201. The response message may indicate acceptance or rejection. For example, the selected neighboring gNB may reject the request due to reasons such as a lack of suitable sensed UE. If the response message indicates rejection, it may also include the reason for rejection and auxiliary information, such as when the sensed UE might be available. If the response message 420 indicates acceptance, it may also include (candidate) sensed UE information, such as UE ID, supported sensed capabilities, supported sensed configurations / resources, etc. If the selected neighboring gNB (i.e., at least one third network entity) identifies the (target) sensed UE (e.g., radio device 207), the response message 420 may include information about the selected sensed UE. Alternatively, if gNB1 identifies the (target) sensed UE, the response message 420 may include information about the candidate sensed UE. In this case, upon receiving the response from the selected neighboring gNB, gNB1 201 identifies the cooperating sensed UE and notifies its serving gNB 425. This message may include sensed configurations for the cooperating sensed UE, such as sensed RS configuration 430, reporting mode, etc. If the cooperating sense UE (e.g., radio device 207) is configured as a measurement sense RS, then the UE needs to report the measurement result 440 to gNB1 via its serving gNB (435). As mentioned above, the Xn interface between network devices can support sense measurement reporting without any restrictions.

[0140] Return to reference Figure 2 In addition to the sensing process performed by the first network entity 201 and the wireless device 207, or as an alternative, the sensing process in the scenario in which the UE participates can also be performed by the third network entity 205 and the wireless device 207, i.e., the second scenario mentioned above.

[0141] In the second scenario, the second request message 237 may be another sensing start request that triggers a sensing process associated with a third network entity and a wireless device. In this disclosure, this other sensing start request may also be referred to as a "second sensing start request".

[0142] The second scenario is further discussed in reference block 260. In this scenario, after receiving the second sensing start request 237, similar to the network-based sensing scenario, at least one third network entity (e.g., third network entity 205) may transmit a response to the second sensing start request to the first network entity 201 in report 243, and this response may also be referred to as a "third response message". The third response message may include a third acceptance indication or a third rejection indication. If the third response message includes a third rejection indication, the third response message may also include at least one of the following: a rejection reason associated with at least one of the third network entity 205 or the wireless device 207; or auxiliary information related to the sensing availability of at least one of the third network entity 205 or the wireless device 207.

[0143] Additionally or alternatively, if at least one third network entity (e.g., third network entity 205) determines that a sensing process can be performed, then third network entity 205 may determine (261) at least one (target) terminal device (e.g., wireless device 207) for use in the sensing process. Then, third network entity 205 and wireless device 207 may perform the sensing process. Furthermore, third network entity 205 may transmit (265) the sensing results of the sensing process to first network entity 201. Therefore, first network entity 201 may receive (269) the sensing results 267. For clarity only, in a sensing scenario involving the UE, refer to... Figure 4B The sensing process performed by the third network entity 205 and at least one terminal device is further discussed.

[0144] Figure 4B The illustration is an example signaling diagram 400B of a UE-participated perception scenario supporting service continuity according to various aspects of this disclosure.

[0145] Similar to the perception process described above, the first network entity 201 can identify at least one third network entity (e.g., third network entity 205) for interaction. Figure 4BAs shown in the example, when a target entity moves to the edge of the sensing coverage area of ​​gNB1 201, gNB1 201 can trigger a neighboring gNB to begin (450) sensing / tracking the target entity, for example, by sending a second sensing start request 237. Upon receiving this request, the selected neighboring gNB selects (455) to sense the UE and cooperates with it, and responds to gNB1, for example, by transmitting a third response message. The sensing process can be similar to that in a network-based scenario, except that the selected neighboring gNB needs to interact with the sensing UE. Furthermore, it should be understood that in a UE-involved sensing scenario, in the same manner as mentioned above, the first network entity 201 (e.g., gNB1) can stop the sensing process and / or notify (475) at least one third network entity (e.g., third network entity 205) to stop the sensing process.

[0146] In view of the above, some embodiments are proposed regarding the continuity of sensing services in network-based sensing scenarios or UE-involved sensing scenarios. In the embodiments for network-based sensing scenarios, a solution for determining neighboring gNBs for target sensing is designed. Signaling and procedures for triggering the selected gNB to sense the target are designed. Conditions for triggering gNB1 to stop tracking the target entity are specified. Furthermore, signaling and procedures for stopping the sensing / tracking functions of neighboring gNBs are also designed.

[0147] In a user equipment-involved sensing scenario embodiment, a solution is proposed where gNB1 and UE collaborate within the coverage area of ​​gNB2 to sense / track target entities. A solution for identifying neighboring gNBs for interaction is designed. A solution for determining the sensing UE and sensing configuration is proposed. The Xn interface needs to support sensing measurement reports. Signaling and procedures for triggering neighboring gNBs to sense / track targets are designed.

[0148] Furthermore, the conditions for triggering gNB1 to stop tracking target entities and when to stop sensing / tracking functions for neighboring gNBs are defined. In this way, service continuity in network-based sensing scenarios and / or service continuity in sensing scenarios involving UEs can be guaranteed.

[0149] Figure 5An example of an apparatus 500 for service continuity in Integrated Sensing and Communication (ISAC) according to various aspects of this disclosure is illustrated. Apparatus 500 may be an example of network entity 102 described herein. Apparatus 500 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Apparatus 500 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 502, memory 504, transceiver 506, and (optionally) I / O controller 508. These components may communicate electronically or be otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0150] Processor 502, memory 504, transceiver 506, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0151] In some implementations, processor 502, memory 504, transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., as a communication management circuitry system). This hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured as or otherwise supporting components for performing the functions described herein. In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 504 are executed by processor 502).

[0152] For example, processor 502 may support wireless communication at device 500 according to the examples disclosed herein. Processor 502 may be configured to operate to support: components for receiving one or more first transmissions from one or more second devices on a first configured resource set; components for determining whether the usage of the first configured resource set meets a threshold; and components for transmitting to at least one second device, based on the determination that the usage of the first configured resource set meets the threshold: i) an indication of a first configuration of a second configured resource set different from the first configured resource set; or ii) an indication of a second configuration of the resource set.

[0153] Processor 502 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 502 may be configured to operate a memory array using a memory controller. In other implementations, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure.

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

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

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

[0157] The transmit chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmit chain may include at least one modulator for modulating data onto a carrier signal, thereby 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 like phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmit chain may also include one or more antennas 510 for transmitting the amplified signal over the air or wireless medium.

[0158] 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 510 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 obtain the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0159] Figure 6An example of an apparatus 600 for service continuity in Integrated Sensing and Communication (ISAC) according to various aspects of this disclosure is illustrated. Apparatus 600 may be an example of network entity 102 and / or core network 206 as described herein. Apparatus 600 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Apparatus 600 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 602, memory 604, transceiver 606, and optional I / O controller 608, which may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0160] Processor 602, memory 604, transceiver 606, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the present disclosure described herein. For example, processor 602, memory 604, transceiver 606, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0161] In some implementations, processor 602, memory 604, transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., as a communication management circuitry system). This hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured as or otherwise supporting components for performing the functions described herein. In some implementations, processor 602 and memory 604 coupled to processor 602 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 604 are executed by processor 602).

[0162] For example, processor 602 may support wireless communication at device 600 according to the examples disclosed herein. Processor 602 may be configured to support: means for transmitting a first data transmission to a first device over a configured resource set; and means for receiving from the first device: i) an indication of a first configuration of a second configured set different from the first configured resource set, or ii) an indication of a second configuration of a resource set, wherein the first configuration or the second configuration is transmitted based on a threshold being met by the usage of the first configured resource set.

[0163] Processor 602 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 602 may be configured to operate a memory array using a memory controller. In other implementations, the memory controller may be integrated into processor 602. Processor 602 may be configured to execute computer-readable instructions stored in memory (e.g., memory 604) to cause device 600 to perform various functions of this disclosure.

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

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

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

[0167] The transmit chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmit chain may include at least one modulator for modulating data onto a carrier signal, thereby 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 like phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmit chain may also include one or more antennas 610 for transmitting the amplified signal over the air or wireless medium.

[0168] 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 610 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 obtain the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0169] Figure 7An example of an apparatus 700 for service continuity in Integrated Sensing and Communication (ISAC) according to various aspects of this disclosure is illustrated. Apparatus 700 may be an example of network entity 102 described herein. Apparatus 700 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Apparatus 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 be otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0170] Processor 702, memory 704, transceiver 706, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure 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.

[0171] In some implementations, processor 702, memory 704, transceiver 706, or various combinations or components thereof may be implemented in hardware (e.g., as a communication management circuitry system). This hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured as or otherwise supporting components for performing the functions described herein. 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).

[0172] For example, processor 702 may support wireless communication at device 700 according to the examples disclosed herein. Processor 702 may be configured to support: components for transmitting a first data transmission to a first device over a configured resource set; and components for receiving from the first device: i) an indication of a first configuration of a second configured set different from the first configured resource set, or ii) an indication of a second configuration of a resource set, wherein the first configuration or the second configuration is transmitted based on a threshold being met by the usage of the first configured resource set.

[0173] 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 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.

[0174] 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. This code may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some implementations, this code may not be directly executable by processor 702, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 704 may in particular include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0175] I / O controller 708 can manage 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 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 708 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In some implementations, I / O controller 708 can 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.

[0176] 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, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously. 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 may communicate bidirectionally with another wireless transceiver. Transceiver 706 may also include a modem for modulating packets, providing modulated packets to one or more antennas 710 for transmission, and 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.

[0177] The transmit chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmit chain may include at least one modulator for modulating data onto a carrier signal, thereby 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 like phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmit chain may also include one or more antennas 710 for transmitting the amplified signal over the air or wireless medium.

[0178] 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 obtain the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0179] Figure 8An example of an apparatus 800 for service continuity in Integrated Sensing and Communication (ISAC) according to various aspects of this disclosure is illustrated. Apparatus 800 may be an example of the UE 104 described herein. Apparatus 800 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Apparatus 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 be otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0180] 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 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.

[0181] In some implementations, processor 802, memory 804, transceiver 806, or various combinations or components thereof may be implemented in hardware (e.g., as a communication management circuitry system). This hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured as or otherwise supporting components for performing the functions described herein. In some implementations, processor 802 and memory 804 coupled to processor 802 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 804 are executed by processor 802).

[0182] For example, processor 802 may support wireless communication at device 800 according to the examples disclosed herein. Processor 802 may be configured to support: components for transmitting a first data transmission to a first device over a configured resource set; and components for receiving from the first device: i) an indication of a first configuration of a second configured set different from the first configured resource set, or ii) an indication of a second configuration of a resource set, wherein the first configuration or the second configuration is transmitted based on a threshold being met by the usage of the first configured resource set.

[0183] 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 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.

[0184] 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. This code may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some implementations, this code may not be directly executable by processor 802, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 804 may in particular include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0185] 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 device. In some implementations, I / O controller 808 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. 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.

[0186] 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, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously. 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, providing modulated packets to one or more antennas 810 for transmission, and 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.

[0187] The transmit chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmit chain may include at least one modulator for modulating data onto a carrier signal, thereby 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 like phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmit chain may also include one or more antennas 810 for transmitting the amplified signal over the air or wireless medium.

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

[0189] Figure 9An example of a processor 900 for service continuity in Integrated Sensing and Communication (ISAC) according to various aspects of this disclosure is illustrated. The processor 900 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 900 may include a controller 902 configured to perform various operations according to the examples described herein. The processor 900 may optionally include at least one memory 904. Additionally or alternatively, the processor 900 may optionally include one or more arithmetic logic units (ALUs) 906. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0190] Processor 900 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset for performing various operations (e.g., receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 900), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), static random access memory (SRAM), ferroelectric random access memory (FeRAM), magnetoresistive random access memory (MRAM), resistive random access memory (RRAM), flash memory, phase-change memory (PCM), etc.)).

[0191] Controller 902 can be configured to manage and coordinate various operations of processor 900 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 900 to support various operations according to the examples described herein. For example, controller 902 can operate as a control unit of processor 900, generating control signals to manage the operation of various components of processor 900. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0192] Controller 902 can be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 904 and determine subsequent instructions(s) to be executed, enabling processor 900 to support various operations according to the examples described herein. Controller 902 can be configured to track the memory addresses of instructions associated with memory 904. Controller 902 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 902 can be configured to interpret instructions and determine control signals to be output to other components of processor 900, enabling processor 900 to support various operations according to the examples described herein. Additionally or alternatively, controller 902 can be configured to manage data flow within processor 900. Controller 902 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 900.

[0193] Memory 904 may include one or more caches (e.g., memory located inside or integrated with processor 900, or other types of memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 904 may reside within or on the processor chipset (e.g., locally on processor 900). In other implementations, memory 904 may reside outside the processor chipset (e.g., remotely from processor 900).

[0194] Memory 904 may store computer-readable, computer-executable code including instructions that, when executed by processor 900, cause processor 900 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. Controller 902 and / or processor 900 may be configured to execute the computer-readable instructions stored in memory 904 to cause processor 900 to perform various functions (e.g., functions or tasks supporting transmission power prioritization). For example, processor 900 and / or controller 902 may be coupled to memory 904, and processor 900, controller 902, and memory 904 may be configured to perform the various functions described herein. In some examples, processor 900 may include multiple processors, and memory 904 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0195] One or more ALU 906s can be configured to support a variety of operations according to the examples described herein. In some implementations, one or more ALU 906s may reside within or on a processor chipset (e.g., processor 900). In other implementations, one or more ALU 906s may reside outside the processor chipset (e.g., processor 900). One or more ALU 906s can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 906s can receive input operands and an opcode, the opcode determining the operation to be performed. One or more ALU 906s can be configured with a variety of logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALU 906s can support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 906s to handle conditional operations, comparisons, and bitwise operations.

[0196] Processor 900 may support wireless communication according to the examples disclosed herein. Processor 902 may be configured or operable to support: components for receiving (i) at least one signal backscattered by a first device based on carrier transmission from at least one second device; or (ii) information determined by the first device based on at least one backscattered signal, wherein the at least one backscattered signal is associated with at least one resource allocated to at least one second device for carrier transmission; and components for determining at least one serving device among the at least one second device for the first device based on the at least one backscattered signal or information. Processor 900 may be configured or operable to support other components for other implementations of method 1300.

[0197] Figure 10 An example of a processor 1000 for service continuity in Integrated Sensing and Communication (ISAC) according to various aspects of this disclosure is illustrated. The processor 1000 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 1000 may include a controller 1002 configured to perform various operations according to the examples described herein. The processor 1000 may optionally include at least one memory 1004. Additionally or alternatively, the processor 1000 may optionally include one or more arithmetic logic units (ALUs) 1006. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0198] Processor 1000 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset for performing various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 1000), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), static random access memory (SRAM), ferroelectric random access memory (FeRAM), magnetoresistive random access memory (MRAM), resistive random access memory (RRAM), flash memory, phase-change memory (PCM), etc.)).

[0199] Controller 1002 can be configured to manage and coordinate various operations of processor 1000 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1000 to support various operations according to the examples described herein. For example, controller 1002 can operate as a control unit of processor 1000, generating control signals to manage the operation of various components of processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0200] Controller 1002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 1004 and determine subsequent instructions(s) to be executed to enable processor 1000 to support various operations according to the examples described herein. Controller 1002 may be configured to track the memory addresses of instructions associated with memory 1004. Controller 1002 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1002 may be configured to interpret instructions and determine control signals to be output to other components of processor 1000 to enable processor 1000 to support various operations according to the examples described herein. Additionally or alternatively, controller 1002 may be configured to manage data flow within processor 1000. Controller 1002 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1000.

[0201] Memory 1004 may include one or more caches (e.g., memory located inside or integrated with processor 1000, or other types of memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 1004 may reside within or on the processor chipset (e.g., locally on processor 1000). In other implementations, memory 1004 may reside outside the processor chipset (e.g., remotely from processor 1000).

[0202] Memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by processor 1000, cause processor 1000 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. Controller 1002 and / or processor 1000 may be configured to execute the computer-readable instructions stored in memory 1004 to cause processor 1000 to perform various functions (e.g., functions or tasks supporting transmission power prioritization). For example, processor 1000 and / or controller 1002 may be coupled to memory 1004, and processor 1000, controller 1002, and memory 1004 may be configured to perform the various functions described herein. In some examples, processor 1000 may include multiple processors, and memory 1004 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0203] One or more ALU 1006s can be configured to support a variety of operations according to the examples described herein. In some implementations, one or more ALU 1006s may reside within or on a processor chipset (e.g., processor 1000). In other implementations, one or more ALU 1006s may reside outside the processor chipset (e.g., processor 1000). One or more ALU 1006s can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 1006s can receive input operands and an opcode, the opcode determining the operation to be performed. One or more ALU 1006s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Additionally or alternatively, one or more ALU 1006 may support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 1006 to handle conditional operations, comparisons, and bitwise operations.

[0204] Processor 1000 may support wireless communication according to the examples disclosed herein. Processor 1002 may be configured or operable to support: components for receiving (i) at least one signal backscattered by a first device based on carrier transmission from at least one second device; or (ii) information determined by the first device based on at least one backscattered signal, wherein the at least one backscattered signal is associated with at least one resource allocated to at least one second device for carrier transmission; and components for determining at least one serving device among the at least one second device for the first device based on the at least one backscattered signal or information. Processor 1000 may be configured or operable to support other components for other implementations of method 1400.

[0205] Figure 11 An example of a processor 1100 for service continuity in Integrated Sensing and Communication (ISAC) according to various aspects of this disclosure is illustrated. Processor 1100 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 1100 may include a controller 1102 configured to perform various operations according to the examples described herein. Processor 1100 may optionally include at least one memory 1104. Additionally or alternatively, processor 1100 may optionally include one or more arithmetic logic units (ALUs) 1106. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0206] Processor 1100 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset for performing various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 1100), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), static random access memory (SRAM), ferroelectric random access memory (FeRAM), magnetoresistive random access memory (MRAM), resistive random access memory (RRAM), flash memory, phase-change memory (PCM), etc.)).

[0207] Controller 1102 can be configured to manage and coordinate various operations of processor 1100 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1100 to support various operations according to the examples described herein. For example, controller 1102 can operate as a control unit of processor 1100, generating control signals to manage the operation of various components of processor 1100. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0208] Controller 1102 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 1104 and determine subsequent instructions(s) to be executed to enable processor 1100 to support various operations according to the examples described herein. Controller 1102 may be configured to track the memory addresses of instructions associated with memory 1104. Controller 1102 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1102 may be configured to interpret instructions and determine control signals to be output to other components of processor 1100 to enable processor 1100 to support various operations according to the examples described herein. Additionally or alternatively, controller 1102 may be configured to manage data flow within processor 1100. Controller 1102 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1100.

[0209] Memory 1104 may include one or more caches (e.g., memory located inside or integrated with processor 1100, or other types of memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 1104 may reside within or on the processor chipset (e.g., locally on processor 1100). In other implementations, memory 1104 may reside outside the processor chipset (e.g., remotely from processor 1100).

[0210] Memory 1104 may store computer-readable, computer-executable code including instructions that, when executed by processor 1100, cause processor 1100 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. Controller 1102 and / or processor 1100 may be configured to execute the computer-readable instructions stored in memory 1104 to cause processor 1100 to perform various functions (e.g., functions or tasks supporting transmission power prioritization). For example, processor 1100 and / or controller 1102 may be coupled to memory 1104, and processor 1100, controller 1102, and memory 1104 may be configured to perform the various functions described herein. In some examples, processor 1100 may include multiple processors, and memory 1104 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0211] One or more ALUs 1106 can be configured to support a variety of operations according to the examples described herein. In some implementations, one or more ALUs 1106 may reside within or on a processor chipset (e.g., processor 1100). In other implementations, one or more ALUs 1106 may reside outside the processor chipset (e.g., processor 1100). One or more ALUs 1106 can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 1106 can receive input operands and an opcode, the opcode determining the operation to be performed. One or more ALUs 1106 can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Additionally or alternatively, one or more ALU 1106 may support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 1106 to handle conditional operations, comparisons, and bitwise operations.

[0212] Processor 1100 may support wireless communication according to the examples disclosed herein. Processor 1102 may be configured or operable to support: components for receiving (i) at least one signal backscattered by a first device based on carrier transmission from at least one second device; or (ii) information determined by the first device based on at least one backscattered signal, wherein the at least one backscattered signal is associated with at least one resource allocated to at least one second device for carrier transmission; and components for determining at least one serving device among the at least one second device for the first device based on the at least one backscattered signal or information. Processor 1100 may be configured or operable to support other components for other implementations of method 1500.

[0213] Figure 12 An example of a processor 1200 for service continuity in Integrated Sensing and Communication (ISAC) according to various aspects of this disclosure is illustrated. Processor 1200 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 1200 may include a controller 1202 configured to perform various operations according to the examples described herein. Processor 1200 may optionally include at least one memory 1204. Additionally or alternatively, processor 1200 may optionally include one or more arithmetic logic units (ALUs) 1206. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0214] Processor 1200 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset for performing various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 1200), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), static random access memory (SRAM), ferroelectric random access memory (FeRAM), magnetoresistive random access memory (MRAM), resistive random access memory (RRAM), flash memory, phase-change memory (PCM), etc.)).

[0215] Controller 1202 can be configured to manage and coordinate various operations of processor 1200 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1200 to support various operations according to the examples described herein. For example, controller 1202 can operate as a control unit of processor 1200, generating control signals to manage the operation of various components of processor 1200. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0216] Controller 1202 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 1204 and determine subsequent instructions(s) to be executed to enable processor 1200 to support various operations according to the examples described herein. Controller 1202 may be configured to track the memory addresses of instructions associated with memory 1204. Controller 1202 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1202 may be configured to interpret instructions and determine control signals to be output to other components of processor 1200 to enable processor 1200 to support various operations according to the examples described herein. Additionally or alternatively, controller 1202 may be configured to manage data flow within processor 1200. Controller 1202 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1200.

[0217] Memory 1204 may include one or more caches (e.g., memory located inside or integrated with processor 1200, or other types of memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 1204 may reside within or on the processor chipset (e.g., locally on processor 1200). In other implementations, memory 1204 may reside outside the processor chipset (e.g., remotely from processor 1200).

[0218] Memory 1204 may store computer-readable, computer-executable code including instructions that, when executed by processor 1200, cause processor 1200 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. Controller 1202 and / or processor 1200 may be configured to execute the computer-readable instructions stored in memory 1204 to cause processor 1200 to perform various functions (e.g., functions or tasks supporting transmission power prioritization). For example, processor 1200 and / or controller 1202 may be coupled to memory 1204, and processor 1200, controller 1202, and memory 1204 may be configured to perform the various functions described herein. In some examples, processor 1200 may include multiple processors, and memory 1204 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0219] One or more ALU 1206s can be configured to support various operations according to the examples described herein. In some implementations, one or more ALU 1206s may reside within or on a processor chipset (e.g., processor 1200). In other implementations, one or more ALU 1206s may reside outside the processor chipset (e.g., processor 1200). One or more ALU 1206s can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 1206s can receive input operands and an opcode, the opcode determining the operation to be performed. One or more ALU 1206s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Additionally or alternatively, one or more ALU 1206 may support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 1206 to handle conditional operations, comparisons, and bitwise operations.

[0220] Processor 1200 may support wireless communication according to the examples disclosed herein. Processor 1202 may be configured or operable to support: components for receiving (i) at least one signal backscattered by a first device based on carrier transmission from at least one second device; or (ii) information determined by the first device based on at least one backscattered signal, wherein the at least one backscattered signal is associated with at least one resource allocated to at least one second device for carrier transmission; and components for determining at least one serving device among the at least one second device for the first device based on the at least one backscattered signal or information. Processor 1200 may be configured or operable to support other components for other implementations of method 1600.

[0221] Figure 13 A flowchart illustrating a method 1300 supporting transmission optimization according to various aspects of this disclosure is shown. Operation of method 1300 may be implemented by a first network entity 201 or components thereof as described herein. For example, operation of method 1300 may be performed by network entity 102 as described herein. In some implementations, the first 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.

[0222] At step 1310, the first network entity 201 sends a first request message to at least one second network entity, based at least in part on the location of a target entity corresponding to an edge cell associated with the first network entity, for information associated with a set of one or more third network entities.

[0223] At step 1320, the first network entity 201 receives a first response message from at least one second network entity, the first response message including information associated with a set of one or more third network entities.

[0224] At step 1330, the first network entity 201 sends a second request message to at least one of the set of one or more third network entities to continue the perception of the target entity by the at least one third network entity and one or more of the at least one wireless device associated with the at least one third network entity.

[0225] At step 1340, in response to the second request message, the first network entity 201 receives a report of perception information associated with the target entity from at least one of a set of one or more third network entities.

[0226] Figure 14A flowchart illustrating a method 1400 supporting transmission optimization according to various aspects of this disclosure is shown. Operation of method 1400 may be implemented by a second network entity 203 or components thereof as described herein. For example, operation of method 1400 may be performed by network entity 102 or core network 206 as described herein. In some implementations, the second network entity may execute a set of instructions to control functional elements of a device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0227] At 1410, the second network entity 203 receives from the first network entity a first request message for information associated with a set of one or more third network entities, wherein the first request message is transmitted based at least in part on the location of a target entity corresponding to an edge cell associated with the first network entity.

[0228] At 1420, the second network entity 203 sends a first response message to the first network entity, the first response message including information associated with a set of one or more third network entities.

[0229] Figure 15 A flowchart illustrating a method 1500 supporting transmission optimization according to various aspects of this disclosure is shown. Operation of method 1500 may be implemented by a third network entity 205 or components thereof as described herein. For example, operation of method 1500 may be performed by network entity 102 as described herein. In some implementations, the third network entity may execute a set of instructions to control functional elements of the device to perform the function. Additionally or alternatively, the device may use dedicated hardware to perform certain aspects of the function.

[0230] At 1510, the third network entity 205 receives a second request message from the first network entity to continue sensing of the target entity by the third network entity and one or more of at least one wireless device associated with the third network entity.

[0231] At 1520, in response to the second request message, the third network entity 205 sends a report to the first network entity, including perception information associated with the target entity.

[0232] Figure 16 A flowchart illustrating a method 1600 supporting transmission optimization according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by the wireless device 207 or components thereof described herein. For example, operation of method 1600 can be performed by the UE 104 described herein. In some implementations, the wireless device can execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device can use dedicated hardware to perform aspects of the described functions.

[0233] At step 1610, the wireless device 207 receives an instruction for a sensing configuration from a third network entity serving the wireless device or from a first network entity via the third network entity, the sensing configuration being used by one or more of the third network entity and / or the wireless device to continue the sensing process of sensing the target entity.

[0234] At step 1610, the wireless device 207 performs a sensing process using at least one of the first network entity or the second network entity.

[0235] 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 also possible. Furthermore, aspects from two or more methods can be combined.

[0236] The various illustrative boxes and components described in connection with this disclosure may 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, which are designed to perform the functions described herein. A 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, a combination of one or more microprocessors with a DSP core, or any other such configuration).

[0237] 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 also 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 a combination thereof. Features implementing these functions may also be physically located in different locations, including being distributed in different locations such that some functions are implemented in different physical locations.

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

[0239] As used herein (including in the claims), the article “a” preceding an element is not limited and should be understood to refer to “at least one” or “one or more” of these elements. The terms “a,” “at least one,” “one or more,” and “at least one or more” are used interchangeably. As used herein (including in the claims), the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “one or two”) indicates an inclusive list, such as a list that makes at least one of A, B, or C mean 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 conditions A and B without departing from the scope of this disclosure. In other words, the phrase “based on” as used herein should be interpreted in the same manner as the phrase “at least partially based on.” Additionally, the term “set” as used herein (including in the claims) can include one or more elements.

[0240] The description provided herein is intended to enable those skilled in the art to implement or use this disclosure. Those skilled in the art will understand that various modifications can be made to this disclosure, and that 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 network entity, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured to cause the first network entity to: Based at least in part on the location of a target entity corresponding to an edge cell associated with the first network entity, a first request message for information associated with a set of one or more third network entities is sent to at least one second network entity. Receive a first response message from at least one second network entity, the first response message including the information associated with the set of one or more third network entities; Send a second request message to at least one of the set of one or more third network entities to continue the perception of the target entity by one or more of the at least one third network entity and at least one wireless device associated with the at least one third network entity; as well as In response to the second request message, a report including perception information associated with the target entity is received from at least one third network entity in the set of one or more third network entities.

2. The first network entity according to claim 1, wherein the information includes one or more of the following: A set of one or more identifiers (IDs) associated with the set of one or more third network entities; A set of one or more locations associated with the set of one or more third network entities; A set of one or more station types associated with the set of one or more third network entities; or A set of one or more coverage areas supported by the set of one or more third network entities.

3. The first network entity according to claim 1 or 2, wherein the information includes first information, and wherein the at least one processor is further configured to cause the first network entity to: Based at least in part on the first and second information, a subset of one or more third network entities is determined from the set of one or more third network entities, wherein the second information includes one or more of the following: the location of the target entity, the speed of the target entity, the size of the target entity, or the direction of movement of the target entity.

4. The first network entity according to claim 3, wherein the at least one processor is further configured to cause the first network entity to: Send a third request message to the subset of one or more third network entities to perform a perception test on the target entity; A set of one or more results of the perception test received from the subset of one or more third network entities; and Based on the set of one or more results, at least one third network entity is selected from the subset of one or more third network entities to continue the perception of the target entity.

5. The first network entity according to claim 3, wherein the at least one processor is further configured to cause the first network entity to: Send at least one sensing request for the target entity to the subset of one or more third network entities; Receive feedback from the subset of one or more third network entities in response to the at least one perception requirement; as well as Based on the feedback, at least one third network entity is selected from the subset of one or more third network entities to continue the perception of the target entity.

6. The first network entity according to any one of claims 1 to 5, wherein: The second request message includes a first perception start request, which triggers a perception process associated with the at least one third network entity, and The first sensing start request includes an indication of at least one of the target entity's position, speed, direction of movement, or size.

7. The first network entity according to claim 6, wherein: The report includes a second response message, wherein the second response message includes a first rejection indication or a first acceptance indication, and The second response message, including the first rejection indication, also includes at least one of the following: The rejection reason associated with the at least one third network entity; or Auxiliary information related to the perceived availability of the at least one third network entity.

8. The first network entity according to claim 7, wherein at least one of the following is present: The first sensing start request includes one or more sensing configurations supported by the first network entity; The second response message includes one or more awareness configurations supported by the at least one third network entity; and The first perception start request and the second response message are sent via the Xn interface between the first network entity and the at least one third network entity.

9. The first network entity of claim 7, wherein the at least one processor is further configured to cause the first network entity to: Send one or more sensing configurations supported by the first network entity in a message other than the first sensing start request; and Receive one or more awareness configurations supported by the at least one third network entity in a message other than the second response message.

10. The first network entity according to any one of claims 7 to 9, wherein the at least one processor is further configured to cause the first network entity to: The sensing of the target entity is stopped based on sending the first sensing start request or the expiration of a first time period after sending the first sensing start request; The perception of the target entity ceases upon receiving the second response message or upon the expiration of a second time period following the receipt of the second response message; or The perception of the target entity is stopped based on the receipt of a perception result from the at least one third network entity or the expiration of a third time period after the receipt of the perception result.

11. The first network entity according to any one of claims 1 to 10, wherein the at least one processor is further configured to cause the first network entity to send an indication indicating that sensing of the target entity is stopped based on at least one of the following: Determine that the target entity remains within the coverage area of ​​the first network entity; Receive another response message including the acceptance indication from another network entity in the subset of one or more third network entities; or The perception result is received from the other network entity.

12. The first network entity according to any one of claims 1 to 5, wherein the second request message includes a wireless device information request, the wireless device information request relating to information concerning a set of wireless devices served by the at least one third network entity, the wireless device information request triggering a sensing process associated with at least one wireless device in the set of wireless devices, and wherein the wireless device information request indicates at least one of the following: Requirements for wireless devices, wherein the requirements include at least one of preferred wireless device location, mobility, expected sensing capability of the wireless device, and location accuracy provided by the wireless device; Second information regarding at least one of the target entity's position, velocity, size, or direction of movement; or One or more perception configurations supported by the first network entity.

13. The first network entity according to claim 12, wherein: The report includes a third response message, and wherein the third response message includes a second rejection indication or a second acceptance indication, and The third response message, including the second rejection indication, also includes at least one of the following: The denial reason related to the wireless device served by the at least one third network entity; or Auxiliary information related to the perceived availability of the wireless device served by the at least one third network entity.

14. The first network entity of claim 13, wherein the third response message includes the second acceptance indication, and the third response message further includes at least one of the following: The identifiers of a subset of wireless devices and the corresponding sensing configurations supported by that subset of wireless devices; or The identification of at least one wireless device and the sensing configuration selected by the at least one third network entity to continue sensing.

15. The first network entity of claim 14, wherein the at least one processor is further configured to cause the first network entity to: Send to the at least one third network entity at least one indication of the at least one wireless device and a configuration indication of the sensing configuration to be used; and The sensing process is performed using the at least one wireless device.

16. The first network entity of claim 15, wherein the at least one processor is further configured to cause the first network entity to: The sensing results from the at least one wireless device are received via the at least one third network entity.

17. The first network entity according to any one of claims 1 to 5, wherein the second request message includes a second sensing start request, the second sensing start request triggering a sensing process associated with both the at least one third network entity and the at least one wireless device.

18. A second network entity, comprising: At least one memory; as well as At least one processor coupled to the at least one memory, the processor being configured to cause the second network entity to: Based at least in part on the location of a target entity corresponding to an edge cell associated with a first network entity, a first request message is received from the first network entity for information associated with a set of one or more third network entities; as well as A first response message is sent to the first network entity, the first response message including the information associated with the set of one or more third network entities.

19. A third network entity, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured to enable a third network entity: A second request message is received from a first network entity to continue the perception of the target entity by one or more of the third network entity and at least one wireless device associated with the third network entity; as well as In response to the second request message, a report including perception information associated with the target entity is sent to the first network entity.

20. A wireless device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured to enable the first wireless device to: The system receives an instruction for a sensing configuration from a third network entity serving the wireless device or from a first network entity via the third network entity, the sensing configuration being used by the third network entity and / or one or more of the wireless devices to continue the sensing process of the target entity. as well as The sensing process is performed using at least one of the first network entity or the second network entity.

Images