Method executed by network node and network node

Abstract

The embodiment of the invention provides a method executed by a network node and the network node. A method performed by a first network node may comprise: sending, by the first network node to a second network node, a first request message related to handover, the first request message comprising a first awareness task transfer request and awareness task configuration information associated with the first network node for reference, the first sensing task transfer request is used for requesting to transfer a sensing task of the UE to a second network node; the first network node receives a first response message responding to the first request message from the second network node, and the first response message comprises information used for indicating whether the second network node accepts the first perception task transfer request or not and information used for indicating whether the second network node accepts the perception task configuration information or not.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of mobile communication, and in particular, the present application relates to a method performed by a network node and a network node. BACKGROUND

[0002] To meet the demand for wireless data traffic "off the charts" due to the deployment of 4G communication systems, there have been efforts to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a "beyond 4G network" or a "post LTE system."

[0003] Wireless communication is one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services has exceeded 5 billion and is still continuing to rapidly grow. As smart phones and other mobile data devices (e.g., tablet computers, notebook computers, netbooks, e-book readers, and machine type devices) are increasingly popular among consumers and enterprises, the demand for wireless data traffic is rapidly growing. In order to meet the high-speed growth of mobile data traffic and support new applications and deployments, it is essential to improve the efficiency and coverage of the wireless interface. SUMMARY

[0004] To at least solve the above problems existing in the prior art, the present application provides a method performed by a network node and a network node.

[0005] According to a first aspect of the embodiments of the present application, a method performed by a first network node is provided, comprising: sending, by the first network node, a first request message related to handover to a second network node, wherein the first request message comprises a first perception task transfer request and perception task configuration information associated with the first network node for reference, wherein the first perception task transfer request is used to request to transfer a perception task of a UE to the second network node; receiving, by the first network node, a first response message responding to the first request message from the second network node, wherein the first response message comprises information indicating whether the second network node accepts the first perception task transfer request, and information indicating whether the second network node accepts the perception task configuration information.

[0006] Optionally, the perception task configuration information comprises at least one of the following: perception mode information of the UE; information of a perception device interacting with a perception signal of the UE; a perception task activation indication; perception task control node information of the UE; and a UE identifier corresponding to a perception report.

[0007] Optionally, the first request message further comprises at least one of the following: a perception task configuration information list; and request information requiring the second network node to participate in or assist the perception task.

[0008] Optionally, each item in the sensing task configuration information list includes at least one of the following: information identifying the first network node; information identifying the sensing task; information on the sensing service type; information related to the sensing device; information on the sensing area of ​​the first network node; information identifying the receiving node of the sensing report; and information on whether the sensing task supports transfer.

[0009] Optionally, the information related to the sensing device includes at least one of the following: information identifying the sensing group; sensing capability information; sensing mode information; sensing result reporting information; and information related to sensing report reporting.

[0010] Optionally, the first response message may further include at least one of the following: information related to the UE's sensing task; and a notification regarding the participation or assistance of a second network node in the sensing task, wherein the information related to the UE's sensing task includes at least one of the following: information identifying the control node of the sensing task; information identifying the receiving node of the sensing report; sensing area information; sensing mode information; and information related to the reporting of the sensing report.

[0011] Optionally, the method further includes: sending a first configuration message from a first network node to the UE, wherein the first configuration message is used to update the perception task configuration to the UE, wherein the first configuration message includes at least one of the following: information identifying the perception task; information on the perception service type; information related to the perception device; information identifying the receiving node of the perception report; information on the perception area; and information on controlling the perception task execution status of the UE.

[0012] Optionally, when the sensing device is a UE, the information related to the sensing device includes at least one of the following: information identifying the sensing device; sensing capability information of the sensing device; sensing mode information; sensing result reporting information; and information related to sensing report reporting.

[0013] Optionally, the method further includes: a first network node receiving a second request message from a second network node, wherein the second request message includes a second sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the second sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the first network node sending a second response message to the second network node in response to the second request message, wherein the second response message includes information indicating whether the first network node accepts the second sensing task transfer request.

[0014] Optionally, the method further includes: a first network node receiving a fourth request message from a fifth network node, wherein the fourth request message includes a third sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the third sensing task transfer request is used to request the transfer of the UE's sensing task to a second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the first network node sending a fourth response message to the fifth network node in response to the fourth request message, wherein the fourth response message includes information indicating whether the first network node accepts the third sensing task transfer request.

[0015] Optionally, each of the second request message and the fourth request message further includes at least one of the following: UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; the reason for requesting the transfer of the sensing task; information on the sensing area of ​​the second network node; and sensing capability information of the second network node.

[0016] Optionally, each of the second response message and the fourth response message further includes at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information related to sensing area updates; and information for controlling the UE's sensing task execution status.

[0017] Optionally, the method further includes: when the first network node determines that the UE has moved out of the first network node's sensing area, the first network node sends a fifth request message to the fifth network node, wherein the fifth request message includes a fourth sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the fourth sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the first network node's sensing area; the first network node receives a fifth response message from the fifth network node in response to the fifth request message, wherein the fifth response message includes information indicating whether the second network node accepts the fourth sensing task transfer request.

[0018] Optionally, the fifth request message may also include at least one of the following: UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information of the cell where the sensing signal with the UE was last detected; information of the sensing area of ​​the first network node; and the reason for requesting the transfer of the sensing task.

[0019] Optionally, the fifth response message may also include at least one of the following: UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information identifying the base station or cell currently accessed by the UE; information on the sensing area of ​​the second network node; and information suggesting an adjustment to the sensing area of ​​the first network node.

[0020] Optionally, the method further includes: a first network node sending a second configuration message to a second network node, wherein the second configuration message includes the sensing task configuration information or a list of sensing task configuration information; and the first network node receiving a second configuration response message from the second network node, wherein the second configuration response message includes information indicating whether the second network node accepts the sensing task configuration information or the configuration information in the list of sensing task configuration information.

[0021] Optionally, when the second configuration message includes the perception task configuration information, the second configuration message also includes information for controlling the perception task execution state of the UE.

[0022] Optionally, the second configuration response message includes at least one of the following: UE identifier; information identifying the sensing task; and sensing capability information of the second network node.

[0023] Optionally, the method further includes: a first network node receiving a third configuration message from a fifth network node, wherein the third configuration message includes the sensing task configuration information or a list of sensing task configuration information; and the first network node sending a third configuration response message to the fifth network node, wherein the third configuration response message includes information indicating whether the first network node accepts the sensing task configuration information or the configuration information in the list of sensing task configuration information.

[0024] Optionally, when the third configuration message includes the perception task configuration information, the third configuration message also includes information for controlling the perception task execution state of the UE.

[0025] Optionally, the third configuration response message may also include at least one of the following: UE identifier; information identifying the sensing task; and sensing capability information of the first network node.

[0026] Optionally, the method further includes: a first network node receiving a first notification message from a second network node, wherein the first notification message includes a perception report reported by the UE to the second network node; and the first network node sending a first notification response message to the second network node, wherein the first notification response message is used to transmit feedback about the first notification message to the second network node, wherein if the perception function is not deployed on the first network node, the first network node forwards the perception report to the node where the perception function is deployed.

[0027] Optionally, the first notification message may also include at least one of the following: information identifying the sensing device or a list of information identifying the sensing device; the UE's sensing area monitoring results.

[0028] Optionally, the perception report includes at least one of the following: UE identifier; information identifying the perception task performed by the UE; perception mode information; perception result; and identifier of the perception device that interacts with the UE to perceive signals.

[0029] Optionally, the method further includes: a first network node receiving a third notification message from a seventh network node, wherein the third notification message includes a fifth perception task transfer request for requesting the transfer of the UE's perception task to the seventh network node; and the first network node sending a third notification response message to the seventh network node, wherein the third notification response message includes information indicating whether the first network node accepts the fifth perception task transfer request.

[0030] Optionally, the third notification message may also include at least one of the following: information identifying the sensing task performed by the UE; the reason for requesting a sensing task transfer; a sensing task configuration update request; the UE's sensing mode information; information on the sensing area of ​​the seventh network node; information on the sensing capability of the seventh network node; and information identifying the sensing device that collected the sensing report.

[0031] Optionally, the third notification response message may also include at least one of the following: UE identifier; information identifying the sensing task performed by the UE; information for controlling the sensing task execution status of the UE; and feedback information for receiving the sensing report.

[0032] Optionally, the information for controlling the UE's perception task execution state includes at least one of the following: activation indication, used to command the UE to start executing the corresponding perception task according to the perception configuration; deactivation indication, used to command the UE to end and / or release the perception task corresponding to the perception configuration; perception pause indication, used to command the UE to pause the transmission or reception of perception signals; perception resume indication, used to command the UE to resume the transmission or reception of perception signals; reporting pause indication, used to command the UE to pause the reporting of perception data; and reporting resume indication, used to command the UE to resume the reporting of perception data.

[0033] According to a second aspect of the embodiments of this application, a method performed by a second network node is provided, comprising: the second network node receiving a first request message related to handover from a first network node, wherein the first request message includes a first sensing task transfer request and sensing task configuration information associated with the first network node for reference, wherein the first sensing task transfer request is used to request the transfer of the sensing task of the UE to the second network node; and the second network node sending a first response message to the first network node in response to the first request message, wherein the first response message includes information indicating whether the second network node accepts the first sensing task transfer request and information indicating whether the second network node accepts the sensing task configuration information.

[0034] Optionally, the first request message may also include at least one of the following: a list of perception task configuration information; and request information requiring the participation or assistance of a second network node in the perception task.

[0035] Optionally, the method further includes: when the second network node determines that the UE has moved out of the sensing area of ​​the first network node, the second network node sends a second request message to the first network node, wherein the second request message includes a second sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the second sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; the second network node receives a second response message from the first network node in response to the second request message, wherein the second response message includes information indicating whether the first network node accepts the second sensing task transfer request.

[0036] Optionally, the method further includes: when the second network node determines that the UE has moved out of the sensing area of ​​the first network node, the second network node sends a third request message to the fifth network node, wherein the third request message includes a sixth sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the sixth sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; the second network node receives a third response message from the fifth network node in response to the third request message, wherein the third response message includes information indicating whether the first network node accepts the sixth sensing task transfer request.

[0037] Optionally, the third request message may also include at least one of the following: UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; the reason for requesting the transfer of the sensing task; information on the sensing area of ​​the second network node; and sensing capability information of the second network node.

[0038] Optionally, the third response message may also include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information related to sensing area updates; and information for controlling the UE's sensing task execution status.

[0039] Optionally, the method further includes: receiving a sixth request message from a fifth network node by a second network node, wherein the sixth request message includes a seventh sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the seventh sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and sending a sixth response message from the second network node to the fifth network node in response to the sixth request message, wherein the sixth response message includes information indicating whether the second network node accepts the seventh sensing task transfer request.

[0040] Optionally, the sixth request message may also include at least one of the following: UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information of the cell where the sensing signal with the UE was last detected; and the reason for requesting the transfer of the sensing task.

[0041] Optionally, the sixth response message may also include at least one of the following: UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information on the sensing area of ​​the second network node; and information suggesting an adjustment to the sensing area range of the first network node.

[0042] Optionally, the method further includes: a second network node receiving a second configuration message from a first network node, wherein the second configuration message includes the perception task configuration information or a list of perception task configuration information; and the second network node sending a second configuration response message to the first network node, wherein the second configuration response message includes information indicating whether the second network node accepts the perception task configuration information or the configuration information in the list of perception task configuration information.

[0043] Optionally, the method further includes: a second network node receiving a fourth configuration message from a fifth network node, wherein the fourth configuration message includes the perception task configuration information or a list of perception task configuration information; and the second network node sending a fourth configuration response message to the fifth network node, wherein the fourth configuration response message includes information indicating whether the first network node accepts the perception task configuration information or the configuration information in the list of perception task configuration information.

[0044] Optionally, when the fourth configuration message includes the perception task configuration information, the fourth configuration message also includes information for controlling the perception task execution state of the UE.

[0045] Optionally, the fourth configuration response message may also include at least one of the following: UE identifier; information identifying the sensing task performed by the UE; and sensing capability information of the second network node.

[0046] Optionally, the method further includes: a second network node receiving a first report message from the UE, wherein the first report message includes a perception report generated by the UE; if the perception function is deployed on the first network node, the second network node sending a first notification message to the first network node and receiving a first notification response message from the first network node, wherein the first notification message includes the perception report, and wherein the first notification response message is used to transmit feedback about the first notification message to the second network node; if the perception function is deployed on the fifth network node, the second network node sending a second notification message to the fifth network node and receiving a second notification response message from the fifth network node, wherein the second notification message includes the perception report, and wherein the second notification response message is used to transmit feedback about the second notification message to the second network node.

[0047] Optionally, the first report message may also include at least one of the following: the UE's sensing area monitoring results; and information that the UE is about to move out of the sensing area, indicating that the UE is about to move out of the sensing area of ​​the second network node.

[0048] Optionally, the second report message may also include updated perception task configuration.

[0049] Optionally, the second notification response message includes at least one of the following: information identifying the sensing task performed by the UE; an identifier or list of identifiers of the sensing device; feedback on the receipt of the sensing report; and feedback or response on the sensing task configuration information.

[0050] According to a third aspect of the embodiments of this application, a method executed by a user equipment (UE) is provided, comprising: the UE receiving a first configuration message from a second network node; and the UE sending a message responding to the first configuration message to the second network node, wherein the first configuration message is included in a first response message sent by the second network node to the first network node, the first response message being a message of the second network node responding to a first request message sent by the first network node, wherein the first request message includes a first sensing task transfer request and sensing task configuration information associated with the first network node for reference, wherein the first sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the first response message includes information indicating whether the second network node accepts the first sensing task transfer request and information indicating whether the second network node accepts the sensing task configuration information.

[0051] Optionally, the method further includes: the UE sending a first report message to a second network node, wherein the first report message includes a perception report generated by the UE.

[0052] Optionally, the first configuration message is a Radio Resource Control (RRC) reconfiguration message, and the first configuration response message is an RRC reconfiguration completion message.

[0053] Optionally, the first configuration message includes at least one of the following: information identifying the sensing task; information on the sensing service type; information related to the sensing device; information identifying the receiving node of the sensing report; information on the sensing area; and information on controlling the execution status of the UE's sensing task.

[0054] According to a fourth aspect of the embodiments of this application, a method performed by a first network node is provided, comprising: the first network node receiving a second request message from a second network node, wherein the second request message includes a second sensing task transfer request and / or information indicating that a UE has moved out of a sensing area, wherein the second sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information indicating that the UE has moved out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the first network node sending a second response message to the second network node in response to the second request message, wherein the second response message includes information indicating whether the first network node accepts the second sensing task transfer request.

[0055] According to a fifth aspect of the embodiments of this application, a method performed by a first network node is provided, comprising: the first network node receiving a fourth request message from a fifth network node, wherein the fourth request message includes a third sensing task transfer request and / or information about a UE moving out of a sensing area, wherein the third sensing task transfer request is used to request the transfer of the UE's sensing task to a second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the first network node sending a fourth response message in response to the fourth request message to the fifth network node, wherein the fourth response message includes information indicating whether the first network node accepts the third sensing task transfer request.

[0056] According to a sixth aspect of the embodiments of this application, a method executed by a first network node is provided, comprising: when the first network node determines that a UE has moved out of the sensing area of ​​the first network node, the first network node sends a fifth request message to a fifth network node, wherein the fifth request message includes a fourth sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the fourth sensing task transfer request is used to request the transfer of the UE's sensing task to a second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the first network node receives a fifth response message from the fifth network node in response to the fifth request message, wherein the fifth response message includes information indicating whether the second network node accepts the fourth sensing task transfer request.

[0057] According to a seventh aspect of the embodiments of this application, a method performed by a first network node is provided, comprising: the first network node sending a second configuration message to a second network node, wherein the second configuration message includes sensing task configuration information or a list of sensing task configuration information associated with the first network node for reference; and the first network node receiving a second configuration response message from the second network node, wherein the second configuration response message includes information indicating whether the second network node accepts the sensing task configuration information or the configuration information in the list of sensing task configuration information.

[0058] According to an eighth aspect of the embodiments of this application, a method performed by a first network node is provided, comprising: the first network node receiving a third configuration message from a fifth network node, wherein the third configuration message includes sensing task configuration information or a list of sensing task configuration information associated with the first network node for reference; and the first network node sending a third configuration response message to the fifth network node, wherein the third configuration response message includes information indicating whether the first network node accepts the sensing task configuration information or the configuration information in the list of sensing task configuration information.

[0059] According to a ninth aspect of the embodiments of this application, a method performed by a first network node is provided, comprising: the first network node receiving a first notification message from a second network node, wherein the first notification message includes a perception report reported by a UE to the second network node; the first network node sending a first notification response message to the second network node, wherein the first notification response message is used to transmit feedback to the second network node regarding the first notification message, wherein if the perception function is not deployed on the first network node, the first network node forwards the perception report to the node where the perception function is deployed.

[0060] According to a tenth aspect of the embodiments of this application, a method performed by a first network node is provided, comprising: the first network node receiving a third notification message from a seventh network node, wherein the third notification message includes a fifth perception task transfer request for requesting the transfer of a UE's perception task to the seventh network node; and the first network node sending a third notification response message to the seventh network node, wherein the third notification response message includes information indicating whether the first network node accepts the fifth perception task transfer request.

[0061] According to an eleventh aspect of the embodiments of this application, a method executed by a second network node is provided, comprising: when the second network node determines that a UE has moved out of the sensing area of ​​a first network node, the second network node sends a second request message to the first network node, wherein the second request message includes a second sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the second sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the second network node receives a second response message from the first network node in response to the second request message, wherein the second response message includes information indicating whether the first network node accepts the second sensing task transfer request.

[0062] According to a twelfth aspect of the present application, a method executed by a second network node is provided, comprising: when the second network node determines that a UE has moved out of the sensing area of ​​a first network node, the second network node sends a third request message to a fifth network node, wherein the third request message includes a sixth sensing task transfer request and / or information indicating that the UE has moved out of the sensing area, wherein the sixth sensing task transfer request is used to request that the sensing task of the UE be transferred to the second network node, and the information indicating that the UE has moved out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the second network node receives a third response message from the fifth network node in response to the third request message, wherein the third response message includes information indicating whether the first network node accepts the sixth sensing task transfer request.

[0063] According to a thirteenth aspect of the present application, a method performed by a second network node is provided, comprising: the second network node receiving a sixth request message from a fifth network node, wherein the sixth request message includes a seventh sensing task transfer request and / or information indicating that a UE has moved out of a sensing area, wherein the seventh sensing task transfer request is used to request that the sensing task of the UE be transferred to the second network node, and the information indicating that the UE has moved out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the second network node sending a sixth response message to the fifth network node in response to the sixth request message, wherein the sixth response message includes information indicating whether the second network node accepts the seventh sensing task transfer request.

[0064] According to a fourteenth aspect of the present application, a method performed by a second network node is provided, comprising: the second network node receiving a second configuration message from a first network node, wherein the second configuration message includes sensing task configuration information or a list of sensing task configuration information associated with the first network node for reference; and the second network node sending a second configuration response message to the first network node, wherein the second configuration response message includes information indicating whether the second network node accepts the sensing task configuration information or the configuration information in the list of sensing task configuration information.

[0065] According to a fifteenth aspect of the embodiments of this application, a method performed by a second network node is provided, comprising: the second network node receiving a fourth configuration message from a fifth network node, wherein the fourth configuration message includes sensing task configuration information or a list of sensing task configuration information associated with a first network node for reference; and the second network node sending a fourth configuration response message to the fifth network node, wherein the fourth configuration response message includes information indicating whether the first network node accepts the sensing task configuration information or the configuration information in the list of sensing task configuration information.

[0066] According to a sixteenth aspect of the embodiments of this application, a method performed by a second network node is provided, comprising: receiving a first report message from a UE by the second network node, wherein the first report message includes a perception report generated by the UE; and sending the perception report to a network node that deploys perception functionality.

[0067] Optionally, the step of sending the perception report to the network node deploying the perception function may include: if the perception function is deployed on a first network node, then a second network node sends a first notification message to the first network node and receives a first notification response message from the first network node, wherein the first notification message includes the perception report, and the first notification response message is used to transmit feedback about the first notification message to the second network node; if the perception function is deployed on a fifth network node, then a second network node sends a second notification message to the fifth network node and receives a second notification response message from the fifth network node, wherein the second notification message includes the perception report, and the second notification response message is used to transmit feedback about the second notification message to the second network node.

[0068] According to a seventeenth aspect of the present application, a network node is provided, comprising: a transceiver for transmitting and receiving signals; and a processor coupled to the transceiver and configured to perform the method performed by the network node as described above.

[0069] According to an eighteenth aspect of the present application, a user equipment is provided, comprising: a transceiver for transmitting and receiving signals; and a processor coupled to the transceiver and configured to perform the method performed by the UE as described above.

[0070] According to a nineteenth aspect of the present application, a computer-readable storage medium for storing instructions is provided, wherein when the instructions are executed by at least one processor, they cause the at least one processor to perform the method described above.

[0071] The beneficial effects of the technical solutions provided in this application will be explained in the following text in conjunction with specific optional embodiments, or can be learned from the description of the embodiments, or can be learned through the implementation of the embodiments. Attached Figure Description

[0072] To more clearly and easily illustrate and understand the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0073] Figure 1 This is a diagram illustrating an exemplary system architecture for System Architecture Evolution (SAE).

[0074] Figure 2 This is a diagram illustrating an exemplary system architecture according to various embodiments of the present disclosure.

[0075] Figure 3A This is a flowchart illustrating a method performed by a first network node according to an exemplary embodiment of the present disclosure.

[0076] Figure 3B This is a signal flow diagram illustrating a first example of an exemplary embodiment according to the present disclosure.

[0077] Figure 4 This is a signal flow diagram illustrating a second example of an exemplary embodiment according to the present disclosure.

[0078] Figure 5 This is a signal flow diagram illustrating a third example of an exemplary embodiment according to the present disclosure.

[0079] Figure 6 This is a signal flow diagram illustrating a fourth example of an exemplary embodiment according to the present disclosure.

[0080] Figure 7 This is a signal flow diagram illustrating a fifth example of an exemplary embodiment according to the present disclosure.

[0081] Figure 8 This is a signal flow diagram illustrating a sixth example of an exemplary embodiment according to the present disclosure.

[0082] Figure 9 This is a signal flow diagram illustrating a seventh example of an exemplary embodiment according to the present disclosure.

[0083] Figure 10 This is a signal flow diagram illustrating an eighth example of an exemplary embodiment according to the present disclosure.

[0084] Figure 11 This is a signal flow diagram illustrating a ninth example of an exemplary embodiment according to the present disclosure.

[0085] Figure 12 This illustrates a method performed by a second network node according to an exemplary embodiment of the present disclosure.

[0086] Figure 13 This is a flowchart illustrating a method performed by a UE according to an exemplary embodiment of this application.

[0087] Figure 14 This is a block diagram illustrating a network node according to an exemplary embodiment of this application.

[0088] Figure 15 This is a block diagram illustrating a UE according to an exemplary embodiment of this application. Detailed Implementation

[0089] The following description, with reference to the accompanying drawings, is provided to aid in a thorough understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. This description includes various specific details to aid understanding but should be considered exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.

[0090] The terms and wording used in the following description and claims are not limited to their dictionary meanings, but are merely used by the inventors to enable a clear and consistent understanding of this disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of this disclosure is for illustrative purposes only and not for limiting the purpose of this disclosure as defined in the appended claims and their equivalents.

[0091] It should be understood that the singular forms of “one,” “an,” and “the” include plural references unless the context clearly indicates otherwise. Thus, for example, the reference to “component surface” includes one or more such surfaces.

[0092] The terms “comprising” or “may include” refer to the presence of a corresponding disclosed function, operation, or component that may be used in the various embodiments of this disclosure, rather than limiting the presence of one or more additional functions, operations, or features. Furthermore, the terms “comprising” or “having” may be interpreted as indicating certain characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be construed as excluding the possibility of the presence of one or more other characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof.

[0093] The term "or" as used in the various embodiments of this disclosure includes any of the listed terms and all combinations thereof. For example, "A or B" may include A, may include B, or may include both A and B.

[0094] Unless otherwise defined, all terms used in this disclosure (including technical or scientific terms) have the same meaning as understood by one of those skilled in the art as described herein. Common terms as defined in dictionaries are to be interpreted as having a meaning consistent with the context in the relevant technical field and should not be interpreted ideally or overly formally unless expressly defined in this disclosure.

[0095] It should be noted that the message or node names in this disclosure (e.g., "first request message," "first response message," "first notification message," "first notification response message," "first network node," "second network node," etc.) are merely examples, and other message or node names may also be used. Furthermore, the use of "first," "second," etc., in the message or node names is simply an example and does not represent a specific order or sequence. Detailed descriptions of irrelevant steps are omitted in this disclosure, and the steps in the various processes within this disclosure can be combined or executed independently. The execution steps of each process are merely examples, and other possible execution orders are not excluded.

[0096] In this disclosure, a base station (BS) can be an LTE base station, a 4G base station (e.g., eNB), a 5G base station (e.g., gNB, ng-eNB), a 6G base station, a non-terrestrial network (NTN) base station, a high-altitude platform station (HAPS), a drone base station, a wireless Fidelity (WIFI) access point, or other types of access points. Furthermore, in this disclosure, when the cell accessed by the UE changes from one cell to another, this behavior can be referred to as handover or cell switch; in the description of this disclosure, "handover" and "cell switch" have the same meaning.

[0097] In this application, "sensing task" refers to the process involving network nodes transmitting / receiving sensing signals and / or collecting and reporting sensing data. It can refer to a sensing task being performed by a single sensing device (a sensing task can also be called a sensing service or sensing business), or it can refer to a sensing task performed jointly by multiple sensing devices. In this disclosure, during a UE handover or cell change, the cell accessed by the UE after the handover or cell change is the target cell or candidate cell, and the corresponding base station can be called the target base station or target network node. The cell accessed by the UE before the handover or cell change is the source cell, and the corresponding base station can be called the source base station or source network node. Furthermore, in this disclosure, "user," "UE," "user terminal," or "user terminal equipment" can have the same meaning, and "node" and "network node" can have the same meaning, for example, they can be UE, base station, core network, or components of a base station (e.g., Centralized Unit (CU), Distributed Unit (DU), etc.).

[0098] Sensor integration is a crucial function of 6G communication systems. In wireless networks, UEs may participate in sensing functions, performing sensing tasks assigned by network nodes, such as sending or receiving sensing signals, collecting and reporting sensing data or results, etc. Appropriate sensor integration technology can improve the accuracy of existing sensing methods and enhance the performance of the communication system through the collected data. However, considering UE mobility, handover may occur when a UE moves between base stations, causing interruptions in the sensing tasks performed by the UE and compromising the continuity of sensing tasks.

[0099] Therefore, this disclosure proposes a solution to ensure the continuity of sensing tasks during UE movement. The following discussion... Figures 1 to 15 The various embodiments used to describe the principles of this disclosure in this patent document are illustrative only and should not be construed in any way as limiting the scope of this disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device. Furthermore, the following literature and standards are incorporated herein by reference as if fully set forth herein: TS 38.300; TS 38.423; TS 38.413; TS 38.413; and TS 38.331.

[0100] Furthermore, this application involves various network nodes, which are described in detail below:

[0101] First network node: can be a network node device. In one example, the first network node can be a BS as described above; in another example, the first network node can be an access point; in one example, when a base station comprises multiple components, the first network node can be a component of the base station, such as the CU of the base station, the control plane portion of the CU of the base station, or the user plane portion of the CU of the base station.

[0102] Second network node: can be the first network node, or a network node device that is different from the first network node.

[0103] The third network node can be a UE served by the first network node.

[0104] The fourth network node can be a UE served by the second network node.

[0105] The fifth network node can be the core network, a network node with sensing capabilities, or a sensing entity / module.

[0106] The seventh network node can be a network node device that is distinct from the first and second network nodes.

[0107] Figure 1 This is an exemplary system architecture 100 of System Architecture Evolution (SAE). User Equipment (UE) 101 is a terminal device used to receive data. Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network, including macro base stations (eNodeB / NodeB) that provide the UE with an interface to access the radio network. Mobility Management Entity (MME) 103 is responsible for managing the UE's mobility context, session context, and security information. Serving Gateway (SGW) 104 primarily provides user plane functions; MME 103 and SGW 104 may reside in the same physical entity. Packet Data Network Gateway (PGW) 105 is responsible for functions such as charging and lawful interception, and may also reside in the same physical entity as SGW 104. Policy and Charging Rules Function Entity (PCRF) 106 provides Quality of Service (QoS) policies and charging criteria. Universal Packet Radio Service Support Node (SGSN) 108 is a network node device in the Universal Mobile Telecommunications System (UMTS) that provides routing for data transmission. The Home Subscriber Server (HSS) 109 is the UE's home subsystem, responsible for protecting user information including the UE's current location, the address of the serving node, user security information, and the UE's packet data context.

[0108] Figure 2 This is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the present disclosure.

[0109] User Equipment (UE) 201 is the terminal equipment used to receive data. Next-Generation Radio Access Network (NG-RAN) 202 is the radio access network, which includes base stations (gNBs or eNBs connected to the 5G core network 5GC; eNBs connected to the 5GC are also called ng-gNBs) that provide the UE with an access radio network interface. Access Control and Mobility Management Function Entity (AMF) 203 is responsible for managing the UE's mobility context and security information. User Plane Function Entity (UPF) 204 primarily provides user plane functions. Session Management Function Entity (SMF) 205 is responsible for session management. Data Network (DN) 206 includes services such as operator services, internet access, and third-party services.

[0110] Figure 3A This is a flowchart illustrating a method performed by a first network node according to an exemplary embodiment of this application.

[0111] like Figure 3A As shown, in step S310, the first network node sends a first request message related to handover to the second network node. The first request message includes a first sensing task transfer request and sensing task configuration information associated with the first network node for reference. The first sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node.

[0112] In this application, the term "handover" can refer to handover behaviors already defined in communication systems such as 4G / 5G, or it can refer to new handover types related to sensing functions. For example, one network node may transfer sensing control behavior for the UE to another network node for execution. Furthermore, in this application, sensing functions (which can be sensing function entities / modules) can be deployed in base stations, components of base stations, existing or new units in the core network, or units independent of the base station and core network. In this application, the sensing function entity / module should possess at least one of the following functions: authentication of sensing tasks, security assurance of sensing tasks, selection of nodes participating in sensing tasks, generation and distribution of sensing task configurations, activation and deactivation of sensing tasks, sensing area management, sensing data processing, provision of sensing reference information, and centralized management and scheduling of sensing tasks for each base station. The base station should possess at least one of the following functions: transmission of sensing signals, reception of sensing signals, collection and transmission of sensing data, selection of nodes participating in sensing tasks, sensing area management, and sensing mobility management. In addition, the UE should have at least one of the following functions: registration of sensing tasks, transmission of sensing signals, reception of sensing signals, collection and transmission of sensing data, and selection of nodes participating in sensing tasks.

[0113] In one exemplary embodiment, in addition to including the first sensing task transfer request and sensing task configuration information associated with the first network node for reference as described above, the first request message may also include at least one of the following: a list of sensing task configuration information; and request information requiring the participation or assistance of a second network node in the sensing task.

[0114] In one exemplary embodiment, the perception task configuration information associated with the first network node for reference may include at least one of the following: UE perception mode information; information of the perception device that interacts with the UE to sense signals; perception task activation indication; UE perception task control node information; and UE identifier corresponding to the perception report.

[0115] In one exemplary embodiment, each item of the sensing task configuration information in the sensing task configuration information list may include at least one of the following: information identifying the first network node; information identifying the sensing task; information on the sensing service type; information related to the sensing device; information on the sensing area of ​​the first network node; information identifying the receiving node of the sensing report; and information on whether the sensing task supports transfer.

[0116] Specifically, the information related to the sensing device may include at least one of the following: information identifying the sensing group; sensing capability information; sensing mode information; sensing result reporting information; and information related to sensing report reporting.

[0117] In one exemplary embodiment, the first request message may be a handover request message; however, this application is not limited to this. The first request message may also be other existing or newly defined XnAP messages, such as newly defined messages for the sensor integration function. Furthermore, the first request message may be a UE-Associated message or a non-UE-Associated message. In addition, the various information contained in the first request message may be transmitted explicitly in the interface or contained in a transparent container.

[0118] In step S320, the first network node receives a first response message from the second network node in response to the first request message. The first response message includes information indicating whether the second network node accepts the first sensing task transfer request and information indicating whether the second network node accepts the sensing task configuration information.

[0119] In one exemplary embodiment, the first response message may further include at least one of the following: information related to the UE's sensing task; and notification regarding the participation or assistance of a second network node in the sensing task.

[0120] In one exemplary embodiment, the information related to the UE's sensing task may include at least one of the following: information identifying the control node of the sensing task; information identifying the receiving node of the sensing report; sensing area information; sensing mode information; and information related to the reporting of the sensing report.

[0121] In addition, the method may further include: sending a first configuration message from a first network node to the UE, wherein the first configuration message is used to update the perception task configuration to the UE.

[0122] In one exemplary embodiment of this application, the first configuration message may include at least one of the following: information identifying the sensing task; information on the sensing service type; information related to the sensing device; information identifying the receiving node of the sensing report; information on the sensing area; and information on controlling the execution state of the sensing task of the UE.

[0123] The following reference Figure 3B The steps mentioned above in the method are described in detail.

[0124] Figure 3B This is a signal flow diagram illustrating a first example of an exemplary embodiment according to this application.

[0125] In this example, the UE and the source base station are in an RRC connection state. When the UE moves from the source base station to the target base station, the source base station makes a decision to switch the UE to the target base station based on the measurement report and Radio Resource Management (RRM) information. This application implements the interaction process of sensing information in this process, so that the target base station can know the relevant information of the sensing task of the source base station, thereby ensuring the continuity of the sensing task during the handover process.

[0126] like Figure 3B As shown, in step 301, the source base station sends a first request message, such as a handover request message, to the target base station.

[0127] In one exemplary embodiment of this application, the first request message may include at least one of the following (i.e., at least one of the following information or information list):

[0128] ■ User identifier (i.e. UE identifier), used to identify a UE that is undergoing a move / handover, such as NG-RAN node UEXnAP ID, Temporary Mobile Subscriber Identity (TMSI), Radio Network Temporary Identity (RNTI), etc.;

[0129] ■ A list of sensing task configuration information. This list informs the target base station about the current UE's sensing task configuration information. This information is generated by the sensing function and sent to the UE via the network. The sensing function may be deployed in the core network or at the source base station. After receiving this information, the target base station can use it as a reference for subsequent sensing task configuration. The sensing task configuration information in this list includes not only information related to the current UE but also information about other network nodes involved in the current sensing task (e.g., the base station, other UEs served by the base station). Each item in the sensing task configuration information list must contain at least one of the following:

[0130] ◆Information that identifies the sensing task, also known as the sensing task identifier, is used to identify the sensing task that the UE is currently executing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0131] ◆Base station identifier, used to indicate that the sensing task configuration information is related to or configured for this base station, such as NG-RAN node ID.

[0132] ◆Information on the sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0133] ◆Information related to sensing devices, also known as a "sensing device information list," includes information about the sensing device's configuration, such as specific device configuration details. Because both base stations and UEs in a communication network have the ability to transmit and receive signals, specific information is needed to indicate the signal transmission and reception combinations and sensing modes involved in the sensing task. Information related to sensing devices must include at least one of the following:

[0134] ● The information identifying the sensing device, also known as the sensing device identifier, is used to indicate the network node sending or receiving sensing signals. It can be a base station identifier (e.g., NG-RAN node ID), a UE identifier (e.g., UEID), or a newly defined device identifier for the sensing device (e.g., Device ID). A new sensing device identifier can be assigned by the sensing function to facilitate the management of all nodes (including base stations and UEs) participating in the sensing task. When a UE identifier is included, it can correspond to other UEs served by that base station.

[0135] ●The information that identifies the sensing group can also be called "sensing device group identifier", "sensing group identifier", "group identifier", "device group identifier", etc. A group of transmitting and receiving nodes of sensing signals is a sensing group. If base station A transmits a sensing signal and UE A receives a sensing signal, then base station A and UE A are a sensing group. This sensing group will have a unique information for identifying the sensing group. If UE A transmits a sensing signal and base station A receives a sensing signal, then UE A and base station A are another sensing group. The information used to identify this sensing group is different from the information used to identify the sensing group consisting of base station A and UE A. The information that identifies the sensing group can correspond to the transmission and reception of sensing signals, which makes it easier to decompose an overall sensing task into the transmission and reception of sensing signals between network nodes.

[0136] ●Perceptual ability information may include at least one of the following:

[0137] The maximum number of sensing tasks that can be supported simultaneously;

[0138] The maximum number of UEs that can participate in the sensing task;

[0139] Supported sensing signal types;

[0140] Supported sensing signal encoding methods;

[0141] Supported resource reuse methods include Time Division Duplexing (TDD), Frequency Division Duplexing (FDD), Code Division Multiple Access (CDMA), and Time Division Multiple Access (TDMA).

[0142] Supported frequency bands for transmitting or receiving sensing signals;

[0143] Supported perception modes;

[0144] Supported methods for submitting perception reports;

[0145] ●Sensing mode information, used to represent the sensing mode of the corresponding device, including at least one of the following expressions:

[0146] Method 1: Indicate whether the corresponding device is a sending node or a receiving node, or both;

[0147] Method 2: Specific signal transmission and reception modes, such as device A sending a sensing signal and device B receiving the sensing signal, where device A and device B can be the same device, and device A / B can be a base station or a UE;

[0148] ●The types of sensing signals, such as signals from existing communication systems, such as Channel Status Information-Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Positioning Reference Signal (PRS), and Sounding Reference Signal (SRS), or signals from non-3GPP communication systems, such as Bluetooth, Wireless Local Area Network (WLAN) signals, or signals specifically sent for sensing functions, such as radar signals;

[0149] ● Signal transmission / reception configuration indication information, which can be one or more integers / indexes.

[0150] / string, used to indicate resource configuration information when sending or receiving signals, including resource configuration information in the time domain, frequency domain, or spatial domain;

[0151] ● Sensing task execution status information, used to indicate the sensing task execution status of a certain sensing device or a sensing group, specifically may include at least one of the following status information:

[0152] The inactive state indicates that the sensing device has been configured with a sensing task, but has not yet sent / received the sensing signals or reported the sensing data as indicated by the sensing task.

[0153] The activated state indicates that the sensing device has been configured with a sensing task and is transmitting / receiving sensing signals or reporting sensing data as indicated by the sensing task.

[0154] The sensing pause state indicates that the transmission / reception of sensing signals by the sensing device is paused. The reason for the sensing pause may be poor network communication function.

[0155] The reporting pause status indicates that although the sensing device is sending or receiving sensing signals and collecting sensing data, the reporting of sensing data is paused. The reason for the reporting pause may be that the network load is too heavy or the reporting link is abnormal.

[0156] Abnormal states are used to indicate that an abnormality has occurred in the execution process of a sensing task. For example, due to some special reasons, an error or abnormality has occurred in the execution process of the sensing task of the sensing device.

[0157] ●Sensing result reporting information. Sensing results may be the direct measurement result of the sensing signal by the sensing device, or an intermediate result after data analysis and processing, or the final sensing result obtained after data analysis and processing. Sensing result reporting information includes at least one of the following:

[0158] Measurement results of the sensed signal, such as the reference signal received power (RSRP), reference signal received quality (RSRQ), path loss, Doppler shift, angle of arrival (AoA), and zenith angle of arrival (ZoA).

[0159] Intermediate results of perception, such as the perceived position and / or shape of an object; the perceived scattering cross section (RCS) of an object; the object's velocity, acceleration, and / or...

[0160] Or direction; sensing environmental information, etc.;

[0161] The final result of a perception task, such as detecting an intruding object, abnormal traffic conditions, or abnormal weather;

[0162] The above-mentioned perception results can be obtained by the sensing device using local computing power, or they can be obtained through external computing power.

[0163] ●Information related to the submission of perception reports includes at least one of the following:

[0164] Reporting cycle;

[0165] The reporting time period;

[0166] The time slot information reported by the UE;

[0167] Report trigger conditions, such as the sensing signal reaching a certain specified threshold;

[0168] One or more integers or strings are used to indicate the reporting method of the sensing device;

[0169] The reported resource configuration information can be one or more integers or strings, used to indicate the resource configuration information required for reporting the sensing results, including time domain, frequency domain, or spatial domain.

[0170] ◆The source base station's sensing area information indicates the range of its sensing area, that is, the area that the source base station's sensing capabilities can cover. Within this area, the UE can perform sensing tasks with the base station regardless of whether it is within the source base station's communication coverage area. The purpose of this information is to enable the target base station to know the sensing areas of both the source base station and the UE, so that when the UE moves out of the source base station's sensing area, the target base station can promptly detect the situation and react (the specific process will be described in detail below). Figure 4 (Detailed description required). The information of the sensing area may include at least one of the following information or a list of information:

[0171] ● A list of cell identifiers, such as the global NG-RAN cell ID list, PCI list, or CGI list, and containing at least one cell identifier;

[0172] ● A list of tracking areas, containing information on at least one Tracking Area Code (TAC);

[0173] ●The Tracking Area Identity (TAI) list (also known as a "list of information identifying the tracking area") contains a set of Public Land Mobile Network (PLMN) IDs and TAC information;

[0174] ● A list of PLMN IDs, containing at least one PLMN ID;

[0175] ●Radio Access Network (RAN) Area ID

[0176] A list containing at least one RAN region ID;

[0177] ● A list of Standalone Non-Public Network (SNPN) IDs, containing at least one SNPN ID;

[0178] ● A list of Cellular Access Gateway (CAG) IDs, containing at least one CAGID;

[0179] ●The physical area in reality refers to the area occupied by a physical location in reality, such as a factory, a piece of land, or a section of a road. This area can be identified by a physical area number.

[0180] ◆The information identifying the receiving node of the perception report, also known as the "perception report receiving node identifier," is used to indicate the information of the network node receiving the perception report. The transmission of this information ensures that the network node the UE connects to after moving can know the receiving node of the UE's perception report, enabling the network node to promptly forward the perception report to the receiving node after receiving it, thus ensuring the continuity of perception data reporting. The perception report receiving node identifier may contain at least one of the following information:

[0181] ● Information that identifies the sensing function, also known as the "sensing function identifier", is used to uniquely identify the logical unit, entity or module corresponding to the sensing function, such as the Sensing Function ID;

[0182] ● The address used for sensing functions, such as an IP address;

[0183] ● Information that identifies the node / entity / module where the sensing function is located, also known as the "identifier of the node / entity / module where the sensing function is located" (i.e., the identifier of the node / entity / module where the sensing function is deployed), such as base station ID (e.g., Global NG-RAN node ID), Access and Mobility Management Function (AMF) ID, Location Management Function (LMF) routing ID (i.e., LMF routing ID);

[0184] ● The address information of the entity or node receiving the perception report, such as IP address, etc.

[0185] ◆Information regarding whether the sensing task supports handover, also known as "sensing task mobility indication," can be of Boolean or Enumerated type. If this information is negative, it means that the sensing task does not support UE mobility, and the UE's sensing configuration will be automatically released when the UE moves to another base station (i.e., switches to another base station). This information may be related to specific application scenarios and their requirements. In some application scenarios, when the UE moves out of the communication coverage area or sensing area of ​​the source base station, sensing is no longer required, and therefore, sensing task handover is not necessary.

[0186] ■ The sensing task configuration information associated with the source base station for reference, also known as "UE-related sensing task configuration information," "UE-level sensing task configuration information," "UE-specific sensing task configuration information," or "UE-related sensing task interaction information," is used to enable interaction between the source and target base stations regarding the subsequent sensing execution method of the currently moving UE. Unlike the base station-level sensing task configuration information (i.e., the sensing task configuration information list) mentioned above, the sensing task configuration information associated with the source base station for reference is specific to the currently moving UE; that is, it is UE-specific. The sensing task configuration information associated with the source base station for reference includes at least one of the following information or a list of information:

[0187] ◆UE perception mode information, used to represent the UE's perception mode, can be expressed in the following ways:

[0188] -Method 1: Indicate whether the UE is a transmitting node or a receiving node, or both;

[0189] -Method 2: Specific signal transmission and reception modes, such as UE sending a sensing signal and UE receiving the sensing signal itself (i.e., UE sending and receiving on its own), or UE sending a sensing signal and base station receiving the sensing signal (i.e., UE sending and base station receiving), or base station sending a sensing signal and UE receiving the sensing signal (i.e., base station sending and UE receiving), or UE A sending a sensing signal and UE B receiving the sensing signal (i.e., UE A sending and UE B receiving), or UE B sending a sensing signal and UE A receiving the sensing signal (i.e., UE B sending and UE A receiving).

[0190] ◆ Information about the sensing device that interacts with the UE to sense signals, such as base station ID, UE ID, or device ID. When the UE's sensing mode is not self-initiated and self-received, other network nodes need to interact with the UE to sense signals. For example, the base station sends a sensing signal and the UE receives the sensing signal, or the UE sends a sensing signal and the base station receives the sensing signal, or the UE sends a sensing signal and other UEs receive the sensing signal, or other UEs send a sensing signal and the UE receives the sensing signal.

[0191] ◆Information related to the execution status of the sensing task, used to represent the execution status of the sensing task, and can be of type Boolean or Enumerated. The status represented by this information can be at least one of the following:

[0192] ● Inactive state, indicating that the UE is configured with a sensing task, but is not transmitting / receiving sensing signals or reporting sensing data as indicated by the sensing task.

[0193] ●Activated state, indicating that the UE has been configured with a sensing task and is transmitting / receiving sensing signals or reporting sensing data as indicated by the sensing task.

[0194] ●Perception pause state indicates that the transmission / reception of perception signals by the UE has been paused. The reason for the perception pause may be poor communication quality of the UE.

[0195] ● Reporting pause status indicates that although the UE is sending or receiving sensing signals and collecting sensing data, the reporting of sensing data is paused. The reason for the reporting pause may be that the network load is too heavy or the reporting link is abnormal.

[0196] ●Abnormal status, used to indicate that an abnormality has occurred in the execution process of the sensing task. For example, due to some special reasons, an error or abnormality occurs in the execution process of the UE's sensing task;

[0197] ◆Sense task activation indication: This indication is for cases where the UE has been configured with a sense task at the source base station but the sense task is not activated. The source base station sends this indication to the target base station, so that the target base station can instruct the UE to activate the transmission / reception of sense signals and measurement collection through lower-level information such as Radio Resource Control (RRC), Media Access Control (MAC) Control Element (CE), or Downlink Control Information (DCI).

[0198] ◆Preferred / suggested / recommended / updated sensing task configuration information, that is, the sensing task configuration information after UE handover. The specific information is as follows: the information related to the sensing device in the sensing task configuration information list above, that is, the case where the sensing device is the UE. This information can be used as a reference when the target base station controls the sensing task.

[0199] ◆UE's perception task control node information, used to represent the control node of the perception task. This control node can be the entity where the perception function is deployed, or the base station that issues the perception task to the UE. The perception task control node can manage the UE's perception configuration, such as adjusting the UE's perception mode, adjusting the parameters of the perception signals related to the UE, and selecting other UEs to participate in perception (e.g., the current UE and other selected UEs transmit perception signals). The control node of the perception function can change as the UE moves. After the UE's perception task control node information is adjusted, the adjusted UE perception task control node information needs to be notified to the node where the perception function is located. The UE's perception task control node information may contain at least one of the following:

[0200] ● Base station identifier, such as Global NG-RAN node ID;

[0201] ● Core network identifier, such as AMF ID;

[0202] ● Information that identifies the sensing function, such as the Sensing Function Routing ID;

[0203] ◆ The UE identifier corresponding to the perception report. This UE identifier can be the same as the aforementioned UE identifier, or it can be a different type of UE identifier. After the UE switches from the source base station (first network node) to the target base station, the UE may send the perception report to the target base station. The target base station can forward the perception report to the source base station. The source base station needs the UE identifier to identify the UE corresponding to the received perception report. For example, the source base station can save the initial NG-RAN node UE XnAPID or NG-RAN node UE NGAP ID and send this information to the UE's target base station. Subsequently, no matter which base station the UE moves to, this information will be passed to the new target base station. After receiving the UE's perception report, the new target base station will forward the UE's perception report along with the UE identifier to the aforementioned source base station. In this way, the source base station can identify the UE corresponding to the perception report.

[0204] ■ Request information requiring the target base station to participate in or assist in sensing. As the UE moves, the execution quality of sensing tasks by both the source base station and the UE may degrade. The source base station can request the target base station, to which the UE is switched, to assist in sensing, provided that the target base station also has sensing capabilities. Adjacent base stations can exchange sensing capabilities in advance via the XnAP interface or other interface messages. In addition to a separate request indication, this request information can also carry specific information regarding the target base station's participation in or assistance with sensing. Specifically, this request information may include at least one of the following:

[0205] ◆The relevant configurations that require the target base station to participate in sensing include, such as sensing device identification, sensing mode information, sensing signal type and its parameters, as described in the corresponding items in the sensing configuration information list above;

[0206] ◆The sensing area information required by the target base station is as described in the sensing area information in the sensing configuration information list above;

[0207] ◆The desired perception quality or effect, such as the accuracy of perception, the result of perception, and the frequency of perception reporting;

[0208] ■ Sensing Task Transfer Request: This request is used to transfer the UE's sensing tasks to the target base station. The following will refer to... Figure 4 The examples are described in detail.

[0209] In this application, the first request message serves to transmit relevant information about the sensing tasks performed by the UE that the target base station needs to know, requesting the target base station to establish communication and / or sensing-related resources for the UE to ensure the continuity of the sensing tasks during UE movement. In other words, the first request message enables the target base station to know relevant information about the sensing tasks during the handover preparation process, ensuring the timely transmission of relevant information and preventing interruption of sensing tasks due to UE movement.

[0210] In step 302, the target base station sends a first response message, such as a handover request confirmation message, to the source base station in response to the first request message.

[0211] In an exemplary embodiment of this application, the first response message may include at least one of the following:

[0212] ■ User Identifier (i.e., UE Identifier): Used to identify the UE undergoing movement or handover, such as the Source NG-RAN node UE XnAP ID, Target NG-RAN node UE XnAP ID, TMSI, RNTI, etc. This information is used to identify the UE undergoing movement / handover.

[0213] ■ Information used to indicate whether the target node accepts the sensing task configuration information, also known as "feedback or response to the sensing task configuration information," is used to notify the source base station (i.e., the first network node) of the status of confirmation or acceptance of the corresponding sensing task configuration information. This information (i.e., the feedback or response) includes at least one of the following:

[0214] ◆ Information that identifies the sensing task, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, and Sensing Session ID;

[0215] ◆Sensing task configuration information confirmation or acceptance indication, used to indicate that the corresponding sensing task configuration information has been confirmed or accepted. This indication can be in the following ways:

[0216] ● Explicit indications, such as flag, bool, or enumerated indications, indicate that the target base station has acknowledged or accepted the sensing task configuration information.

[0217] ● Implicit indications, such as if the first response message is received, it means that the target base station confirms or accepts the sensing task configuration information; or if the sensing task configuration information rejection or failure indication is not received, it means that the target base station confirms or accepts the sensing task configuration information.

[0218] ◆The perception task configuration information rejection or failure indication is used to indicate that the corresponding perception task configuration has failed. In other words, it is used to indicate that the corresponding perception task configuration information has not been confirmed or accepted.

[0219] This instruction can be given in the following manner:

[0220] ● Explicit indicators, such as those of type Flag, Bool, or Enumerated, indicate that the perception task configuration has failed.

[0221] ● Implicit indications, such as receiving a first response message to indicate that the perception task configuration has failed, or not receiving a confirmation indication of the perception task configuration information to indicate that the perception task configuration has failed.

[0222] ◆Rejection or failure reason, used to indicate the reason for rejection or failure of the perception task configuration, includes at least one of the following information:

[0223] ●The target base station does not support sensing functions;

[0224] ●The target base station receives repeated sensing tasks;

[0225] ● The number of sensing tasks supported by the target base station exceeds the maximum value.

[0226] ■ Information related to the UE's perception tasks can also be referred to as "UE-related perception interaction results".

[0227] Includes at least one of the following information or a list of information:

[0228] ◆Information identifying the control node for sensing tasks. After the UE switches from the source base station to the target base station, since the UE can still transmit sensing signals with the source base station within a certain area, the source base station can act as the control node for the UE's sensing tasks. After the UE switches from the source base station to the target base station, since the UE can only communicate with the target base station (because the UE and the target base station are in RRC connection state), the target base station can also act as the UE's sensing task control node to adjust the configuration of sensing tasks related to the UE. For example, it can select a new UE to transmit / receive sensing signals with the original UE and / or the target base station, and send the new sensing task configuration information to the newly selected UE and / or the original UE through RRC messages. The specific sensing task control node after the switch can be determined by the base station.

[0229] ◆The identifier of the sensing device that interacts with the UE to sense signals, used to indicate the network node that sends or receives the sensing signals. It can be a base station identifier, such as NR-RAN node ID, a user identifier (UE ID), or a device identifier newly defined for the sensing device (such as Device ID).

[0230] ◆The information of the identification perception group is as described in step 301;

[0231] ◆Perceive pattern information, specifically as described in step 301;

[0232] ◆The type of sensing signal is as described in step 301;

[0233] ◆Signal transmission / reception configuration indication information, as described in step 301;

[0234] ◆The sensing results are reported as described in step 301;

[0235] ◆Information related to the reporting of perception reports, as described in step 301;

[0236] ◆The information of the receiving node that identifies the perception report is as described in step 301;

[0237] ◆Sensing area information, specifically as described in step 301;

[0238] ■ Regarding the response / notification of the target base station's participation in or assistance with the sensing task, upon receiving information related to the sensing task performed by the UE at the source base station in the first request message, if the target base station also has sensing capabilities, it may decide whether to utilize its own sensing capabilities to participate in the sensing task performed by the UE and perform assisted sensing. The sensing mode after the target base station participates in the sensing task does not necessarily have to be related to the UE; it can also be the target base station itself transmitting and receiving sensing signals, or selecting other UEs to transmit and receive sensing signals. The response / notification regarding the target base station's participation in or assistance with the sensing task may include at least one of the following information:

[0239] ◆Identifier of the sensing device that interacts with the target base station to sense signals, used to indicate the network node that sends or receives sensing signals. It can be a base station identifier (e.g., NG-RAN node ID), a user identifier (UE ID), or a device identifier newly defined for the sensing device (e.g., Device ID);

[0240] ◆The information of the identification perception group is as described in step 301;

[0241] ◆Perceive pattern information, specifically as described in step 301;

[0242] ◆The type of sensing signal is as described in step 301;

[0243] ◆Signal transmission / reception configuration indication information, as described in step 301;

[0244] ◆The sensing results are reported as described in step 301;

[0245] ◆Information related to the reporting of perception reports, as described in step 301;

[0246] ◆Information on the sensing area of ​​the target base station, as described in step 301;

[0247] ■ This information indicates whether the target base station accepts the sensing task transfer request, and can also be referred to as a "response or reply to the UE sensing task transfer request." The following will refer to... Figure 4 The examples are described in detail.

[0248] In this application, the target base station (i.e., the second network node) sends a first response message to the source base station (i.e., the first network node) to report the negotiation results or confirmation information regarding the interaction on the sensing task. In other words, the first response message enables the source base station to know the result of the interaction on the sensing task between the source base station and the target base station, thus completing the complete bidirectional interaction process between the two base stations.

[0249] In step 303, the source base station sends a first configuration message to the UE, such as an RRC reconfiguration message.

[0250] In an exemplary embodiment of this application, the first configuration message may include at least one of the following:

[0251] ■ Information that identifies the sensing task, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, SensingTrace ID, etc.;

[0252] ■ Information on sensing service type or sensing application scenario (e.g., Sensing Service Type or Sensing Use Case) is used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road supervision, weather monitoring, life monitoring, smart factory, etc.

[0253] ■ Information related to sensing devices, also known as a "sensing device information list", is as described in step 301, where the sensing device is the current UE;

[0254] ■ The information that identifies the receiving node of the perception report can also be called the "perception report receiving node identifier".

[0255] Specifically as described in step 301;

[0256] ■ Information about the sensing area, as described in step 301;

[0257] ■ Information that controls the execution status of the UE's sensing tasks, also known as "sensing status control indication," may include at least one of the following:

[0258] ◆Activation indication is used to notify (command) the UE to start performing the corresponding sensing tasks according to the sensing configuration, such as enabling the transmission or reception of sensing signals, the collection and reporting of sensing data as indicated by the sensing configuration;

[0259] ◆Deactivation indicator, used to notify (command) the UE to end and / or release the sensing task corresponding to the sensing configuration;

[0260] ◆Sensing pause indication, used to notify (command) the UE to pause the transmission or reception of sensing signals;

[0261] ◆Sense recovery indication, used to notify (command) the UE to resume sending or receiving sense signals;

[0262] ◆ Reporting pause instruction, used to notify (command) the UE to pause the reporting of sensing data;

[0263] ◆Report recovery instruction, used to notify (command) the UE to resume reporting of sensing data.

[0264] In this application, the aforementioned first configuration message is used to update the sensing task configuration to the UE to ensure the continuity of the sensing task before and after handover. In one example, the first configuration message may be sent by the target base station to the source base station in a first response message via transparent transmission, and the source base station then sends the first configuration message to the UE. In another example, the first configuration message may be an RRC message or a lower-level message generated and sent to the UE by the source base station.

[0265] In this application, the aforementioned first configuration message can be an existing RRC reconfiguration message, a newly defined RRC message, or a lower-level message. The aforementioned first configuration message can be transmitted explicitly or contained within a transparent container.

[0266] Furthermore, after the UE switches from the source base station to the target base station, the source base station receives a UE context release message (i.e., a UE Context Release message) from the target base station. Subsequently, the source base station releases the air interface and control plane resources associated with the UE context. In this application, after a UE receiving a sensing task from the source base station switches from the source base station to the target base station, the source base station can retain the sensing context associated with the UE, such as the UE identifier and the corresponding sensing task configuration information.

[0267] Optionally, after the UE switches from the source base station to the target base station, if there are other UEs transmitting sensing signals with the UE within the communication coverage area of ​​the source base station, the source base station can send an RRC reconfiguration message or a MAC CE or lower-level message to cause these other UEs to release the relevant sensing tasks. The specific message sent by the source base station is the same as the first configuration message containing the deactivation indication in step 303, and will not be described again here.

[0268] In step 304, the UE sends a first configuration response message (e.g., an RRC reconfiguration complete message) to the target base station. This message is a response to the first configuration message. If the UE is switching from the source base station to the target base station, this message can be an RRC reconfiguration complete message, indicating that the UE has successfully accessed the target base station.

[0269] Reference above Figure 3B The process of exchanging sensing information during the handover of a UE from a source base station to a target base station is described. This process enables the target base station to obtain relevant information about the sensing tasks of the source base station, thereby ensuring the continuity of sensing tasks during the handover process.

[0270] In reference Figure 3B In the described example, although the first request message sent by the first network node (i.e., the source base station) to the second network node (i.e., the target base station) includes a first perception task transfer request to transfer the UE's perception tasks to the second network node, the second network node may refuse the perception task transfer for some reason. However, when the UE moves within the communication coverage area of ​​the second network node, the second network node may still request the first network node to transfer the UE's perception tasks to the second network node, or the first network node may still request to transfer the UE's perception tasks to the second network node. This will be described below.

[0271] As described above, when a UE moves beyond the communication coverage of the source base station, the source base station switches the UE to an adjacent base station (i.e., the target base station). However, since the signal strength required for sensing tasks is lower than that required for communication, even after the UE moves out of the source base station's communication coverage, although the UE cannot communicate with the source base station, it can still transmit sensing signals. Therefore, the sensing area can be larger than the communication coverage. Based on this premise, even if the UE moves out of the source base station's communication coverage, it is uncertain whether the UE is still within the source base station's sensing area. Furthermore, as the UE gradually moves out of the source base station's sensing area, the sensing signal may deteriorate, preventing the UE from continuing to perform sensing tasks with the source base station. Therefore, it is necessary to monitor the UE's sensing area, i.e., to monitor whether the UE has moved out of the source base station's sensing area. In this application, the sensing area refers to the area within which the sensing signals sent by the base station can be received by the UE, or it can refer to the area within which the sensing task can be effectively executed. In this application, the sensing area can be configured by the sensing function, the core network, or the base station, or it can be pre-configured by other network nodes.

[0272] To this end, this application also proposes a scheme for monitoring the sensing area of ​​the UE. Specifically, it can be divided into the following two schemes: Scheme 1: The target base station (i.e., the base station that provides communication services to the UE) that the UE switches to monitors whether the UE has moved out of the sensing area of ​​the source base station (i.e., the base station that performs the sensing task with the UE); Scheme 2: The source base station (i.e., the base station that performs the sensing task with the UE) monitors whether the UE has moved out of the sensing area of ​​the source base station.

[0273] The following is for reference Figure 4 Scheme 1 will be described.

[0274] After detecting that the UE has moved out of the sensing area of ​​the source base station, further interaction between network nodes is needed to determine the control node for the subsequent sensing task of the UE. In one example, the UE executes the sensing task issued by the first network node (i.e., the source base station). After the UE switches from the first network node to the second network node (i.e., the target base station), the UE can still transmit sensing signals with the first network node and execute the sensing task. In this example, the second network node can monitor the sensing area of ​​the UE. Although the sensing area of ​​the first network node may be larger than its own communication coverage and include part of the communication coverage of the second network node, the sensing area of ​​the first network node may not necessarily include the entire communication coverage of the second network node. That is, when the UE moves within the communication coverage of the second network node, the UE may move out of the sensing area of ​​the first network node. In this application, the sensing area of ​​the first network node can be sent to the second network node by being included in the sensing task configuration information, for example, as shown in step 301 above or step 701 described later.

[0275] When a UE moves within the communication coverage area of ​​a second network node, if the second network node detects that the UE has moved out of the sensing area of ​​the first network node based on the UE's mobility information, the second network node needs to notify the first network node of this detection. If the UE will continue to participate in the current sensing task subsequently, the first network node needs to transfer the sensing task configuration information related to the UE to the second network node for control and management. If the current sensing task requires the transmission of sensing signals between the UE and the base station, the UE will transmit sensing signals with the second network node after the sensing task is transferred to the second network node for control and management. In this application, this process of changing the sensing task control node due to the UE's mobility can be referred to as sensing task transfer. Furthermore, the sensing task transfer here only applies to the sensing task performed by the UE itself (e.g., the transmission and reception of sensing signals measured by the UE), and does not represent the entire sensing task including the sensing behavior of the base station and other UEs.

[0276] In one exemplary embodiment of this application, Figure 3AThe described method may further include: a first network node receiving a second request message from a second network node, wherein the second request message includes a second sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the second sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the first network node sending a second response message to the second network node in response to the second request message, wherein the second response message includes information indicating whether the first network node accepts the second sensing task transfer request.

[0277] In one exemplary embodiment, the second request message may further include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; the reason for requesting a transfer of the sensing task; information on the sensing area of ​​the second network node; and sensing capability information of the second network node.

[0278] In one exemplary embodiment, the second response message may include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information related to sensing area updates; and information for controlling the sensing task execution status of the UE.

[0279] The following reference Figure 4 This will be described in detail.

[0280] Figure 4 This is a signal flow diagram illustrating a second example of an exemplary embodiment according to this application.

[0281] exist Figure 4 In the described example, the first network node can be, for example, a source base station, and the second network node can be, for example, a target base station.

[0282] exist Figure 4 Prior to step 401, the UE has switched from the first network node (i.e., the source base station) to the second network node (i.e., the target base station), but the UE's sensing tasks have not been transferred to the second network node. Furthermore, the second network node performs sensing area monitoring on the UE and determines whether the UE has moved out of the sensing area of ​​the first network node based on the monitoring results.

[0283] When it is determined that the UE has moved out of the sensing area of ​​the first network node, in step 401, the second network node sends a second request message to the first network node.

[0284] In this application, the second request message may contain at least one of the following information or a list of information:

[0285] ■UE identifier or a list of UE identifiers, such as RAN node XnAP ID, TMSI, Radio Network Temporary Identifier (RNTI), etc.;

[0286] ■ Information about the cell currently accessed by the UE or a list of cell information, such as cell identity and common gateway interface (CGI);

[0287] ■ Information that identifies the sensing task being performed by the UE, also known as the "identifier of the sensing service being performed by the UE", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, SensingSession ID, Sensing Trace ID, etc.;

[0288] ■ Information on sensing service type or sensing application scenario (e.g., Sensing Type or Sensing Use Case) is used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road supervision, weather monitoring, life monitoring, smart factory, etc.

[0289] A perception task transfer request, also known as a "perception task transfer request instruction," is used to request the transfer of the UE's perception task to the target base station. In this example, this request indicates that the second network node has detected that the UE has left the perception area of ​​the first network node, and that within the perception area of ​​the second network node, the UE cannot continue its perception task with the first network node, thus requiring the transfer of the UE's perception task to the second network node. Upon receiving this request, the first network node will consider whether to transfer the UE's perception task to the second network node and release its own control resources regarding the UE's perception task. This request can be an explicit instruction or an implicit instruction, specifically in the following ways:

[0290] ◆ Explicit indications, such as those of type Flag, Bool, or Enumerated, indicate that if the second request message carries such an indication, it means that the second network node is requesting the first network node to transfer the perception task.

[0291] ◆Implicit indications, such as sending the second request message itself indicating that the second network node is requesting the transfer of the sensing task from the first network node;

[0292] In this application, the perception task transfer request can be completed by querying the perception task control node. After the first network node receives the request, if the first network node replies with information identifying the second network node, it means that the first network node accepts the perception task transfer request; if the first network node replies with information identifying the first network node, it means that the first network node rejects the perception task transfer request.

[0293] ■ Reasons for requesting a sensing task transfer, such as detecting that the UE has moved out of the sensing area of ​​the source node, or a handover from the source node to the target node;

[0294] ■ The indication that the UE has moved out of the sensing area is used to notify the first network node that the UE has moved out of its sensing area. Optionally, when the second request message does not include a sensing task transfer request but includes an indication that the UE has moved out of the sensing area, the first network node may also consider that the second network node has requested the first network node to transfer the sensing task, and decide whether to transfer the sensing task to the second network node as appropriate.

[0295] ■ A perception task configuration update request, which can be a Flag, Bool, or Enumerated value. The second network node may send a request to the first network node to update the perception task configuration based on the actual network conditions and the UE's perception task execution status. Upon receiving this information, the first network node can provide the second network node with a preferred / suggested / updated / recommended perception task configuration, which can be used as a reference for the second network node when controlling perception tasks. It should be noted that even when the second network node does not send a perception task configuration update request to the first network node, the first network node can still proactively send preferred / suggested / updated / recommended perception task configuration information to the second network node, as detailed in step 402.

[0296] ■ The current UE's sensing mode information indicates the UE's sensing mode. In other words, this information allows the target base station to know how the UE is currently sensing—specifically, whether it is receiving or transmitting signals, and with which devices it is transmitting and receiving sensing signals. This information can also be included in the sensing task configuration, but because the UE may experience changes in its sensing mode at the second network node (e.g., due to UE movement, the original sensing mode may no longer be possible, or the sensing function may adjust the UE's sensing task configuration), the sensing mode information can be expressed as follows:

[0297] ◆Method 1: Indicate whether the UE is a transmitting node or a receiving node, or both;

[0298] ◆Method 2: Specific signal transmission and reception modes, such as UE sending and receiving sensing signals (i.e., self-transmission and self-reception), or UE sending and base station receiving sensing signals (i.e., UE sending and base station receiving), or base station sending and UE receiving sensing signals (i.e., base station sending and UE receiving), or UE A sending and UE B receiving sensing signals (i.e., UE A sending and UE B receiving), or UE B sending and UE A receiving sensing signals (i.e., UE B sending and UE A receiving), where UE A represents the user terminal itself, and UE B represents other user terminals;

[0299] ■ The current UE's sensing task execution status information is as described in step 301. This information in the second request message serves to inform the first network node of the current UE's sensing signal transmission status, sensing reporting status, and other information, thus providing more reference for the first network node to make a decision on sensing task transfer. For example, if the UE's sensing task execution status information in the second request message indicates an inactive state, and the sensing function is on the first network node, the first network node can decide to release the UE's sensing task configuration based on the sensing task execution status. Similarly, if the UE's sensing task execution status information indicates an abnormal state, the first network node can also decide to release the UE's sensing task configuration. Furthermore, if the UE's sensing task execution status information in the second request message indicates a sensing paused state or a reporting paused state, the first network node can decide to resume sensing or resume reporting based on network conditions.

[0300] ■ Information about the sensing area of ​​the second network node. This information is used to inform the first network node of the range of the second network node's sensing area. The first network node can only decide to transfer the UE's sensing task to the second network node if the cell where the UE is currently located is within the sensing area of ​​the second network node. This information includes at least one of the following or a list of information:

[0301] ◆A list of cell identifiers, such as a global NG-RAN cell ID list, PCI list, or CGI list, containing at least one cell identifier;

[0302] ◆ Tracking area list, containing information on at least one TAC;

[0303] ◆ Tracking area identifier list, containing a set of PLMN ID and TAC information;

[0304] ◆A list of PLMN IDs, containing at least one PLMN ID;

[0305] ◆A list of RAN area IDs, containing at least one RAN area ID;

[0306] ◆A list of SNPN IDs, containing at least one SNPN ID;

[0307] ◆A list of CAG IDs, containing at least one CAG ID;

[0308] ◆The physical area in reality refers to the area occupied by a certain physical location in reality, which can be identified by a physical area number;

[0309] ■ The sensing capability information of the second network node. This information informs the first network node of the second network node's specific sensing capabilities. Only when the second network node's sensing capabilities can support the current sensing task will the first network node decide to transfer the UE's sensing task to the second network node. Based on this sensing capability, the first network node can also rationally allocate network resources for sensing tasks, thereby improving network performance (e.g., throughput). This information includes at least one of the following:

[0310] ◆The maximum number of sensing tasks that can be supported simultaneously;

[0311] ◆Maximum number of UEs that can participate in sensing tasks;

[0312] ◆Supported sensing signals;

[0313] ◆Supported frequency bands for transmitting or receiving sensing signals;

[0314] ◆Supported perception modes;

[0315] ◆Supported methods for submitting perception reports.

[0316] In this application, the second request message is used by the second network node to notify the first network node of the UE's movement between sensing areas (i.e., the UE has moved out of the first network node's sensing area) and request a transfer of sensing tasks. In other words, the second request message includes not only an indication that the UE has moved out of the sensing area (indicating that the UE has moved out of the first network node's sensing area), but also a request for a transfer of sensing tasks. The advantage of the second request message is that it allows the network node currently providing communication services to the UE to interact with the network node that issued the sensing tasks to the UE, transferring the sensing tasks to the current network node when necessary, thus avoiding the interruption of sensing tasks after the UE moves out of the first network node's sensing area.

[0317] The aforementioned second request message can be an existing XnAP message, such as an NG-RANNode Configuration Update message, or a newly defined XnAP message, such as a Sensing Handover Request message. The information in the second request message can be sent explicitly or contained within a transparent container.

[0318] Furthermore, the various examples described in this application do not limit the relationship between the sensing area of ​​the base station and the communication coverage area. The sensing area can be larger than the communication coverage area, or smaller than or equal to the communication coverage area. As long as the base station (target base station or source base station) detects that the UE has moved out of the original sensing area (i.e., the sensing area of ​​the source base station), the target base station and the source base station can interact accordingly.

[0319] After receiving the second request message from the second network node, the first network node will make a decision based on the second request message, namely, whether to transfer the UE's perception task to the second network node for control or management, and then send a second response message.

[0320] Specifically, in step 402, the first network node sends a second response message to the second network node.

[0321] In this application, the second response message includes at least one of the following:

[0322] ■UE identifier or a list of UE identifiers, such as RAN node XnAP ID, TMSI, C-RNTI, etc.;

[0323] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0324] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0325] ■ Information used to indicate whether the first network node accepts the sensing task transfer request, also known as a "response or reply to the sensing task transfer request," can be one of the following:

[0326] ◆Acknowledgement (ACK) of the perception task transfer request: This information represents the response of the first network node after receiving the perception task transfer request and related information from the second network node. If the first network node confirms the perception capability of the second network node, and the UE's perception task execution status in the second network node is normal, the first network node sends an ACK to acknowledge the perception task transfer request. After the first network node agrees to transfer the perception task to the second network node, if the UE subsequently moves to another network node, the information sent by the second network node to the other network nodes (see step 301) needs to update the control node information of the UE's perception task to indicate that the second network node is the control node of the perception task. The ACK for acknowledging the perception task transfer request can be an explicit indication or an implicit indication, as detailed below:

[0327] ● Explicit indications, such as those of type Flag, Bool, or Enumerated, which, if carried in the second response message, indicate that the first network node accepts the second network node's request to transfer the perception task.

[0328] ● Implicit indications, such as sending a second response message itself representing that the first network node accepts the second network node's request to transfer the perception task;

[0329] ◆Negative Acknowledgement (NACK) for the rejection of the sensing task transfer request indicates that the first network node rejects the sensing task transfer request from the second network node. When the response or reply to the sensing task transfer request is a NACK, the second response message may also include the reason for rejecting the sensing task transfer request. The reason for rejecting the sensing task transfer may be, for example, that the source base station chooses to expand the sensing area to continue sensing the UE, or that the sensing task does not support other network nodes controlling the sensing task.

[0330] ■Preferred / Updated / Suggested / Recommended Sensing Task Configuration Information: Based on information related to all network nodes jointly participating in the sensing task and UE sensing task-related information received from the second network node, the first network node provides suggested UE sensing task configuration information and sends this information to the second network node. This suggested UE sensing task configuration information can be used as a reference for the second network node when controlling the sensing task. Specific information is as described in step 301. This information can be sent when the first network node accepts a sensing task transfer request or when the first network node rejects a sensing task transfer request.

[0331] ■ Information used to control the execution status of the UE's sensing tasks, also known as a "sensing status control indication," is used to control the execution status of the sensing tasks of the sensing device. This information can be determined with reference to the current execution status of the UE's sensing tasks, which is included in the second request message in step 401. The specific process of determining the sensing status control indication is implemented based on the base station. The sensing status control indication may include at least one of the following:

[0332] ◆Activation indication is used to notify (or command) the sensing device to start performing the corresponding sensing tasks according to the sensing configuration, such as sending or receiving sensing signals, collecting and reporting sensing data as indicated by the sensing configuration;

[0333] ◆ Deactivation indicator, used to notify (or command) the sensing device to end and / or release the sensing task corresponding to the sensing configuration;

[0334] ◆Sensing pause indication, used to notify (or command) the sensing device to pause the transmission or reception of sensing signals;

[0335] ◆Sensing recovery indication, used to notify (or command) the sensing device to resume sending or receiving sensing signals;

[0336] ◆ Reporting pause instruction, used to notify (or command) sensing devices to pause the reporting of sensing data;

[0337] ◆Report recovery instruction, used to notify (or command) the sensing device to resume reporting sensing data.

[0338] It should be noted that the control / management of the execution state of the perception task can be determined by the first network node as described above, or it can be determined by the second network node through implementation.

[0339] ■ Regarding information related to the sensing area update, the first network node can determine the new sensing area range after the UE moves out of the sensing area range of the first network node based on the sensing area information sent by the second network node and in combination with sensing task control information (such as the sensing task configuration information and / or sensing task configuration information list related to the UE as described above), and send the updated information (i.e. the determined new sensing area range) to the second network node.

[0340] In this application, the first network node sends feedback or negotiation results regarding the transfer of the UE's sensing task to the second network node through a second response message, thereby enabling the second network node to determine the subsequent control node of the UE's sensing task based on the feedback or negotiation results, and allocate the necessary transmission or control resources related to the sensing task to the UE.

[0341] The aforementioned second response message can be an existing XnAP message, such as the NG-RAN Node Configuration Update Acknowledgement message, or a newly defined XnAP message, such as the Sensing Handover Request Acknowledgement message.

[0342] Based on the above references Figure 4 In the example described, after the second network node becomes the perception task control node of the UE (i.e., the third network node), the second network node can select other UEs (e.g., the fourth network node) within the communication coverage area to perform perception tasks. In this case, the second network node sends the perception task configuration information to the fourth network node in the same way as in step 303, which will not be described again here.

[0343] In the above description, refer to Figure 4 The described process is included as a supplementary step. Figure 3A The method described herein is not limited thereto; see also [reference needed]. Figure 4 The described process may be excluded Figure 3A Instead of being described in the method description, it is executed as a separate method, and will not be described again.

[0344] Based on the above references Figure 4 In the example described, the second network node performs sensing area monitoring on the UE, and the second network node directly sends the results of the sensing area monitoring of the UE to the first network node. However, this application is not limited to this. The second network node can also forward the results of the sensing area monitoring of the UE to the first network node through the core network or the network node where the sensing function is deployed.

[0345] Therefore, in one exemplary embodiment of this application, the above references Figure 3A The described method may further include: a first network node receiving a fourth request message from a fifth network node, wherein the fourth request message includes a third sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the third sensing task transfer request is used to request the transfer of the UE's sensing task to a second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and the first network node sending a fourth response message to the fifth network node in response to the fourth request message, wherein the fourth response message includes information indicating whether the first network node accepts the third sensing task transfer request.

[0346] In one exemplary embodiment of this application, the fourth request message may further include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; a reason for requesting a transfer of the sensing task; information on the sensing area of ​​the second network node; and sensing capability information of the second network node.

[0347] In one exemplary embodiment of this application, the fourth response message may further include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information related to sensing area updates; and information for controlling the sensing task execution state of the UE.

[0348] The following reference Figure 5 This will be described in detail.

[0349] Figure 5 This is a signal flow diagram illustrating a third example of an exemplary embodiment of this application.

[0350] exist Figure 5 In the described example, the first network node can be, for example, a source base station, the second network node can be, for example, a target base station, and the fifth network node can be, for example, the core network, other network nodes where the sensing task is deployed, or sensing function entities / modules.

[0351] With reference Figure 4 The example described is similar; prior to step 501, the UE has switched from the first network node to the second network node, but the UE's sensing tasks have not been transferred to the second network node. Furthermore, the second network node performs sensing area monitoring on the UE and determines whether the UE has moved out of the sensing area range of the first network node based on the monitoring results.

[0352] When it is determined that the UE has moved out of the sensing area of ​​the first network node, in step 501, the second network node sends a third request message to the fifth network node.

[0353] In one exemplary embodiment, the third request message may include at least one of the following information or a list of information:

[0354] ■ UE identifier or a list of UE identifiers, such as AMF Next Generation Application Protocol (NGAP) UE ID, RAN NGAP UE ID, TMSI, RNTI; ■ Information about the cell currently accessed by the UE or a list of cell information, such as Cell Identity, CGI, etc.;

[0356] ■ Identifiers associated with the first network node, such as Global NG-RAN node ID, TAI, PLMN ID, SNPNID, etc. Only by carrying this information can the fifth network node (e.g., the core network) know which network node to send the request message to.

[0357] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0358] ■ Information about the sensing service type or sensing use case.

[0359] Used to indicate the type of perception task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road supervision, weather monitoring, life monitoring, smart factory, etc.

[0360] ■The request for a sensory task transfer, also known as an "instruction to request a sensory task transfer," is as described in step 401.

[0361] ■ The reason for requesting the transfer of the perception task is as described in step 401;

[0362] ■ Instruction for the UE to move out of the sensing area, as described in step 401;

[0363] ■ Current UE perception mode information, as described in step 401;

[0364] ■ The current UE's perception task execution status information, as described in step 301;

[0365] ■ The information of the sensing area of ​​the second node is as described in step 401;

[0366] ■ The perception capability information of the second node is as described in step 401.

[0367] In this application, the fifth network node can be the core network, the network node where the sensing function is deployed, or the sensing function entity / module. The function of the third request message is to send the sensing area monitoring results and the corresponding sensing task transfer request to the fifth network node, so that the fifth network node can forward the information contained in the third request message to the network node that needs to receive this information, such as the network node that issues the sensing task or the network node that controls the sensing task. In other words, the benefit of this message is that it allows the second network node to forward the information related to the sensing task transfer to the corresponding network node through the fifth network node, without the second network node needing to send this information through the Xn interface, and without the second network node needing to determine the network node that needs to receive this information. In addition, the third request message also requires the fifth network node to store sensing task-related information, such as the information of the node that issues the sensing task to the UE, the information of the network node that controls the sensing task, and the UE identifier. The network node that issues the sensing task to the UE also needs to store the UE's sensing task-related information, such as sensing task configuration information and UE identifier.

[0368] In one exemplary embodiment, the aforementioned third request message may be an NGAP message or a newly defined network message, and the third request message may be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the third request message may be sent explicitly or contained within a transparent container.

[0369] In step 502, the fifth network node determines, based on the received perception configuration information, that the first network node is the network node that needs to receive the perception task transfer request, and sends a fourth request message to the first network node.

[0370] In one exemplary embodiment of this application, the fourth request message may include at least one of the following information or a list of information:

[0371] ■ UE identifier or a list of UE identifiers, such as AMF NGAP UE ID, RAN NGAP UE ID, TMSI, RNTI. It should be noted that the AMF NGAP UE ID and RANNGAP UE ID sent by the fifth network node (e.g., the core network) to the first network node are context information stored by the fifth network node (e.g., the core network) between the fifth network node and the first network node, and are different from the user identifier in step 501;

[0372] ■ Information about the cell currently accessed by the UE or a list of cell information, such as Cell Identity, CGI, etc.;

[0374] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.

[0375] ■ Information about the sensing service type or sensing use case.

[0376] Used to indicate the type of perception task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0377] ■The request for a sensory task transfer, also known as an "instruction to request a sensory task transfer," is as described in step 401.

[0378] ■ The reason for requesting the transfer of the perception task is as described in step 401;

[0379] ■ Instruction for the UE to move out of the sensing area, as described in step 401;

[0380] ■ Current UE perception mode information, as described in step 401;

[0381] ■ The current UE's perception task execution status information, as described in step 301;

[0382] ■ Information about the sensing area of ​​the second node, as described in step 401;

[0383] ■ The perception capability information of the second node is as described in step 401.

[0384] In this application, the function of the fourth request message is to forward information related to the transfer of the sensing task to the network node (e.g., the first network node) that sends the sensing task. The advantage of this message is that it can directly forward information related to the transfer of the sensing task to the network node that sends the sensing task. Even when the UE is switching between multiple base stations, it is not necessary to transmit information related to the transfer of the sensing task multiple times between these base stations. Instead, the fifth network node (e.g., the core network, the network node where the sensing function is deployed, or the sensing function entity / module) can directly forward the information to the corresponding base station that needs it.

[0385] In one exemplary embodiment, the aforementioned fourth request message may be an NGAP message or a newly defined network message, and the fourth request message may be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the fourth request message may be sent explicitly or contained within a transparent container.

[0386] In step 503, the first network node makes a decision related to the sensing task based on the sensing configuration information received from the fifth network node (e.g., whether to transfer the sensing task of the UE to the second network node for management or control), and sends a fourth response message in response to the fourth request message to the fifth network node.

[0387] In one exemplary embodiment, the fourth response message may include at least one of the following information or a list of information:

[0388] ■UE identifier or a list of UE identifiers, such as AMF NGAP UE ID, RAN NGAP UE ID, TMSI, RNTI, etc. It should be noted that the AMF NGAP UE ID and RAN NGAP UE ID in this message are the same as those in step 502;

[0389] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0390] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0391] ■ Information used to indicate whether the first network node accepts the sensing task transfer request, also known as

[0392] "Response or reply to the request for transfer of perception tasks", as described in step 402;

[0393] ■ Preferred / suggested / recommended / updated perception task configuration information, as described in step 301; ■ Information used to control the perception task execution state of the UE, also referred to as "perception state control indication", as described in step 402;

[0394] ■ Information related to the update of the sensing area, as described in step 402.

[0395] In this application, the fourth response message can be used to provide feedback to the fifth network node on the negotiation results regarding the transfer of perception tasks for the UE, thereby facilitating perception interaction between the first and second network nodes.

[0396] In one exemplary embodiment, the aforementioned fourth response message may be an NGAP message or a newly defined network message, and the fourth response message may be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the fourth request response may be sent explicitly or contained within a transparent container.

[0397] In step 504, after receiving the fourth response message, the fifth network node forwards the information in the message to the second network node, that is, sends the third response message to the second network node.

[0398] In one exemplary embodiment, the third response message may include at least one of the following information and / or a list of information:

[0399] ■UE identifier or a list of UE identifiers, such as AMF NGAP UE ID, RAN NGAP UE ID, TMSI, C-RNTI, etc. It should be noted that the AMF NGAP UE ID and RAN NGAP UE ID in this message are the same as those in step 501;

[0400] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0401] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0402] ■ Information used to indicate whether the first network node accepts the sensing task transfer request, also known as

[0403] "Response or reply to the request for transfer of perception tasks", as described in step 402;

[0404] ■ Preferred / suggested / recommended / updated perception task configuration information, as described in step 301; ■ Information used to control the perception task execution status of the UE, also known as "perception status control indication", as described in step 402;

[0405] ■ Information related to the update of the perceived region, as described in step 402.

[0406] In this application, the function of the third response message is: the fifth network node (e.g., the core network) can forward the response of the perception task control node (e.g., the second network node) to the network node (e.g., the first network node) that initiated the perception task transfer request through this message, thereby completing the interaction between the first network node and the second network node regarding the change of the UE's position within the perception area.

[0407] In one exemplary embodiment, the aforementioned third response message may be an NGAP message or a newly defined network message, and the third response message may be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the third response message may be sent explicitly or contained within a transparent container.

[0408] In the above description, refer to Figure 5 The described process is included as a supplementary step. Figure 3A The method described herein is not limited thereto; see also [reference needed]. Figure 5 The described process may be excluded Figure 3A Instead of being described in the method description, it is executed as a separate method, and will not be described again.

[0409] Based on the above references Figure 4 and Figure 5 In the example described, the second network node performs the sensing area monitoring for the UE. However, this application is not limited to this. For example, the first network node can perform the sensing area monitoring for the UE according to the above-mentioned scheme (2). That is, the sensing area monitoring is performed by the network node that performs the sensing task with the UE.

[0410] Therefore, in one exemplary embodiment of this application, the above references Figure 3AThe described method may further include: when a first network node determines that a UE has moved out of the first network node's sensing area, the first network node sends a fifth request message to a fifth network node, wherein the fifth request message includes a fourth sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the fourth sensing task transfer request is used to request the transfer of the UE's sensing task to a second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the first network node's sensing area; the first network node receives a fifth response message from the fifth network node in response to the fifth request message, wherein the fifth response message includes information indicating whether the second network node accepts the fourth sensing task transfer request.

[0411] In one exemplary embodiment of this application, the fifth request message may further include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information of the cell where the sensing signal with the UE was last detected; information of the sensing area of ​​the first network node; and the reason for requesting the transfer of the sensing task.

[0412] In one exemplary embodiment of this application, the fifth response message may further include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information identifying the base station or cell currently accessed by the UE; information on the sensing area of ​​the second network node; and information suggesting an adjustment to the sensing area range of the first network node.

[0413] The following reference Figure 6 This will be described in detail.

[0414] Figure 6 This is a signal flow diagram illustrating a third example of an exemplary embodiment of this application.

[0415] exist Figure 6In the described example, the first network node can be, for example, a source base station, the second network node can be, for example, a target base station, and the fifth network node can be, for example, the core network, other network nodes where the sensing task is deployed, or sensing function entities / modules. In this example, the first network node is the network node that issues the sensing configuration (in this case, if the sensing function is deployed on the first network node, then the first network node is also the sensing task control node), and the UE switches from the first network node to the second network node during movement. As the UE gradually moves out of the sensing area of ​​the first network node, the first network node can decide to transfer the UE's sensing task to other network nodes based on the signal strength and other relevant measurements. For example, if the strength of the sensing signal in the UE's sensing measurement data received by the first network node is lower than a certain threshold, the first network node can determine that the UE is about to move out of the sensing area of ​​the first network node. Since the first network node cannot determine the location of the UE after it moves out of its sensing area, the first network node needs to send a request message to the fifth network node to notify the fifth network node that the UE has moved out of the sensing area of ​​the first network node. The fifth network node determines that the second network node is the node where the current UE is accessing and performing the perception task, based on the received perception task-related information. In this example, both the first and fifth network nodes need to store the UE's perception task-related context, such as the UE's perception task configuration information and UE identifier.

[0416] Prior to step 601, the UE had switched from the first network node to the second network node, but the UE's sensing tasks were not transferred to the second network node. Furthermore, the first network node performs sensing area monitoring on the UE and determines whether the UE has moved out of the first network node's sensing area based on the monitoring results.

[0417] When the first network node determines that the UE has moved out of the first network node's sensing area, in step 601, the first network node sends a fifth request message to the fifth network node.

[0418] In one exemplary embodiment of this application, the fifth request message may include at least one of the following information or a list of information:

[0419] ■ UE identifier or a list of UE identifiers, such as AMF NGAP UE ID, RAN NGAP UE ID, TMSI, RNTI, etc. It should be noted that the AMF NGAP UE ID and RAN NGAP UE ID in this information are the UE IDs stored by the first network node and the fifth network node (e.g., the core network) when the UE was in the first network node, which is different from the UE identifier (UE ID) in step 602; ■ Information that identifies the sensing task performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.

[0420] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0421] ■ Information about the cell where the sensing signal between the UE and the UE was last detected, such as Cell Indentity, PCI, etc. This information is used to notify the fifth network node (e.g., the core network or sensing function entity / module) of the last position of the UE in the sensing area held by the first network node. It serves as a record of the trajectory of the UE moving in the sensing area of ​​the first network node, which facilitates the coordination of the subsequent sensing task configuration of the UE in the sensing area of ​​other network nodes.

[0422] ■ Information about the sensing area of ​​the first network node. This information is used to notify the fifth network node (e.g., the core network or sensing function entity / module) of the current sensing area range. After receiving this information, the fifth network node can also adjust the sensing area range or other configurations of the first network node by combining information such as the overall sensing task execution status and results, or provide suggestions for adjusting the sensing area range or other configurations of the first network node.

[0423] ■The request for a sensory task transfer, also known as an "instruction to request a sensory task transfer," is as described in step 401.

[0424] ■ Reasons for requesting a transfer of the sensing task, such as loss of sensing signal, UE moving out of the sensing area, etc.; ■ Instructions for the UE to move out of the sensing area, as described in step 401;

[0425] ■ Preferred / updated / suggested / recommended perception task configuration information, as described in step 301; ■ The latest perception task configuration information of the UE stored by the first network node, as described in step 301.

[0426] In this application, the role of the fifth request message is to convey the request for the transfer of the sensing task from the first network node (e.g., the sensing task control node) to the fifth network node (e.g., the core network, other network nodes where the sensing function is deployed, or sensing function entities / modules).

[0427] In one exemplary embodiment, the aforementioned fifth request message may be an NGAP message or a newly defined network message, and the fifth request message may be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the fifth request message may be sent explicitly or contained within a transparent container.

[0428] In step 602, after receiving the fifth request message, the fifth network node determines the network node (e.g., the second network node) currently accessed by the UE based on the UE's information, and sends a sixth request message to that network node.

[0429] In one exemplary embodiment of this application, the sixth request message may include at least one of the following information or a list of information:

[0430] ■UE identifier or UE identifier list, such as AMF NGAP UE ID, RAN NGAP UE ID, TMSI, RNTI, etc. It should be noted that the AMF NGAP UE ID and RAN NGAP UE ID in this information are the UE identifiers stored in the second network node by the fifth network node (e.g., the core network).

[0431] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0432] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0433] ■ Information about the last cell from which a sensing signal was detected between the UE and the network node, such as Cell Indentity and PCI, is used to notify the fifth network node (e.g., the core network or sensing function entity / module) of the UE's last position within the sensing area, as known by the first network node. This information serves as a record of the UE's movement trajectory within the first network node's sensing area and also facilitates coordination with subsequent UEs.

[0434] Configuring sensing tasks within the sensing area of ​​other network nodes;

[0435] ■The request for a sensory task transfer, also known as an "instruction to request a sensory task transfer," is as described in step 401.

[0436] ■ Reasons for requesting a transfer of sensing tasks, such as loss of sensing signal, UE moving out of the sensing area, etc.;

[0437] ■ Instruction for the UE to move out of the sensing area, as described in step 401;

[0438] ■ Preferred / updated / suggested / recommended perception task configuration information, as described in step 301.

[0439] In this application, the function of the sixth request message is as follows: the fifth network node (e.g., the core network or a sensing function entity / module) relays the sensing task transfer request from the first network node to the network node that is providing communication services to the UE. Since the first network node cannot determine whether the UE is within the sensing area of ​​the second network node, the fifth network node can help the first network node determine the location of the second network node, thereby sending a request message to the second network node.

[0440] In one exemplary embodiment, the aforementioned sixth request message may be an NGAP message or a newly defined network message, and the sixth request message may be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the sixth request message may be sent explicitly or contained within a transparent container.

[0441] In addition, it should be noted that this example may require a fifth network node (such as the core network or a sensing function entity / module) to store the sensing task configuration information related to the UE in order to associate the received UE information with the corresponding sensing task and provide the first network node with suggestions related to the sensing task in response.

[0442] In step 603, the second network node sends a sixth response message to the fifth network node.

[0443] In one exemplary embodiment, the sixth response message may include at least one of the following information or a list of information:

[0444] ■UE identifier or a list of UE identifiers, such as AMF NGAP UE ID, RAN NGAP UE ID, TMSI, RNTI, etc. The AMF NGAP UE ID and RAN NGAP UE ID in this information are the same as those in step 602;

[0445] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0446] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0447] ■ Information used to indicate whether the second network node accepts the sensing task transfer request, also known as

[0448] The "response or reply to the request for a sensory task transfer" can be one of the following:

[0449] ◆Accept the request for the task transfer, as described in step 401;

[0450] ◆ The NACK for rejecting the sensing task transfer request is used to indicate that the second network node rejects the first network node's sensing task transfer request for the UE; when the response or reply to the sensing task transfer request is a NACK for rejecting the sensing task transfer request, the sixth response message may also include the reason for rejecting the sensing transfer request, such as the UE is not within the sensing area of ​​the second network node, the number of UEs supported by the second network node to perform sensing tasks exceeds the maximum value, the number of sensing tasks supported by the second network node exceeds the maximum value, etc.

[0451] ■ The sensing area information of the second network node, as described in step 401;

[0452] ■ Information suggesting adjustments to the sensing area of ​​the first network node: Step 602 mentions that the fifth network node (e.g., the core network or sensing function entity / module) can make suggestions to adjust the sensing area of ​​the first network node. Similarly, as an adjacent node of the first network node, after learning about the sensing area of ​​the first network node, the second network node can also make suggestions to adjust the sensing area of ​​the first network node by combining the network's sensing task execution status and some sensing information related to the UE.

[0453] In this application, the sixth response message is used to transmit feedback to the fifth network node regarding the sensing task transfer of the UE. That is, the message is used as a reply from the network node currently serving the UE to the fifth network node (e.g., the core network or sensing function entity / module) to send a sensing task transfer request.

[0454] In one exemplary embodiment, the aforementioned sixth response message may be an NGAP message or a newly defined network message, and the sixth response message may be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the sixth response message may be sent explicitly or contained within a transparent container.

[0455] In step 604, the fifth network node sends a fifth response message to the first network node.

[0456] In one exemplary embodiment, the fifth response message may include at least one of the following information or a list of information:

[0457] ■UE identifier or a list of UE identifiers, such as AMF NGAP UE ID, RAN NGAP UE ID, TMSI, RNTI, etc., where the AMF NGAP UE ID and RAN NGAP UE ID are the same as the user identifier in step 601;

[0458] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0459] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0460] ■ Information used to indicate whether the second network node accepts the sensing task transfer request, also known as a "response or reply to the sensing task transfer request," can be one of the following:

[0461] ◆Accept the request for the task transfer, as described in step 401;

[0462] ◆ A NACK for rejecting a sensing task transfer request indicates that the second network node rejects the first network node's sensing task transfer request for the UE. When the response or reply to the sensing task transfer request is a NACK for rejecting the sensing task transfer request, the fifth response message may also include the reason for rejecting the sensing transfer request, such as the UE being outside the sensing area of ​​the second network node, the second network node supporting more than the maximum number of UEs performing sensing tasks, or the second network node supporting more than the maximum number of sensing tasks. After receiving the NACK for rejecting a sensing task transfer request, the first network node may choose to notify the fifth network node (e.g., the core network or sensing function entity / module) to trigger the process of releasing the UE's sensing task, or the UE may release its own sensing task based on its own implementation.

[0463] ■ Information identifying the base station or cell that the UE is currently accessing. Because the first network node cannot know which network node the UE has moved to, the fifth network node (e.g., the core network) needs to inform the first network node of this information (i.e., the identifier of the base station or cell that the UE is currently accessing) in the response message.

[0464] ■ Information about the sensing area of ​​the second network node, as described in step 401;

[0465] ■ Information suggesting adjustments to the sensing area of ​​the first node. This information may be provided by the fifth network node (e.g., the core network or sensing function entity / module) or by the second network node.

[0466] ■ It is recommended that the first network node be configured with the perception task information, and the specific configuration information be at least one item in the perception task configuration information list in step 301.

[0467] In this application, the fifth response message is used to provide feedback to the first network node regarding the negotiation results of the sensing task transfer for the UE. The function of this message is for the fifth network node (e.g., the core network or sensing function entity / module) to convey a response related to the sensing task transfer request to the network node that initiated the request (e.g., the first network node).

[0468] In one exemplary embodiment, the aforementioned fifth response message may be an NGAP message or a newly defined network message, and the fifth response message may be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the fifth response message may be sent explicitly or contained within a transparent container.

[0469] In the above description, refer to Figure 6 The described process is included as a supplementary step. Figure 3A The method described herein is not limited thereto; see also [reference needed]. Figure 6 The described process may be excluded Figure 3A Instead of being described in the method description, it is executed as a separate method, and will not be described again.

[0470] In addition, the network node that issues the perception task can also act as the perception task control node for the UE. When the UE moves to another network node, the network node that issues the perception task can send the configuration message related to the perception task to the other network node through XnAP or other interfaces. The other network node can also send the message to the UE through RRC reconfiguration message, other RRC message or lower-level message.

[0471] In the example described above, the first network node sends sensing task configuration information (e.g., UE-related sensing task configuration information and / or a list of sensing task configuration information) to the second network node during UE handover. However, this application is not limited to this. Optionally, the first network node may also send the configuration message related to the sensing task to the second network node in the form of an XnAP message, as will be referred to below. Figure 7 The example described is as follows. This configuration message can be a base station-level message, meaning it is independent of a specific UE and its mobility. Alternatively, it can be a UE-level message, meaning it contains configuration information related to a sensing task, or adjusted configuration information related to a sensing task, sent specifically to a UE. Furthermore, the sending of this configuration message can occur before the UE switches from the first network node to the second network node, or it can occur after the UE switches from the first network node to the second network node.

[0472] Accordingly, in one exemplary embodiment of this application, the above references are made to... Figure 3A The described method may further include: a first network node sending a second configuration message to a second network node, wherein the second configuration message includes sensing task configuration information and / or a list of sensing task configuration information associated with the first network node for reference; and the first network node receiving a second configuration response message from the second network node, wherein the second configuration response message includes information indicating whether the second network node accepts the sensing task configuration information and / or the configuration information in the list of sensing task configuration information.

[0473] In one exemplary embodiment of this application, when the second configuration message includes sensing task configuration information associated with the first network node for reference, the second configuration message also includes information for controlling the sensing task execution state of the UE.

[0474] In one exemplary embodiment of this application, the second configuration response message may further include at least one of the following: UE identifier; information indicating a sensing task; and sensing capability information of the second network node.

[0475] The following is for reference Figure 7 This will be described in detail.

[0476] Figure 7 This is a signal flow diagram illustrating a fourth example of an exemplary embodiment according to this application.

[0477] In this example, the sensing function can be deployed on the first network node, or it can be located in the core network or other network nodes.

[0478] In step 701, the first network node sends a second configuration message to the second network node.

[0479] In one exemplary embodiment, the second configuration message may include at least one of the following information or a list of information:

[0480] ■ User identifier (i.e., UE identifier), such as NG-RAN node UE XnAP ID, TMSI, RNTI, etc.;

[0481] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0482] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0483] ■ When the second configuration message is a base station-level message, it contains a list of sensing task configuration information as described in step 301. The network node issuing the sensing task can use this message to send the sensing task configuration to other surrounding network nodes, such as network nodes the UE may move to or network nodes the UE connects to after moving. Through this message, network nodes that did not initially participate in the sensing task can also receive the sensing task configuration and can participate in the sensing task according to the actual situation of the UE's movement when needed later.

[0484] ■ When the second configuration message is a UE-level message, it contains UE-related sensing task configuration information as described in step 301. The first network node can use this message to send the sensing task configuration of a specific UE to the second network node. Additionally, the first network node can also use this message to send information (also referred to as a "sensing state control indication") to UEs within the communication coverage area of ​​the second network node for controlling the UE's sensing task execution state. This information may include at least one of the following:

[0485] ◆Activation indication is used to notify (or command) the UE to start performing the corresponding sensing tasks according to the sensing configuration, such as sending or receiving sensing signals, collecting and reporting sensing data as indicated by the sensing configuration;

[0486] ◆Deactivation indicator, used to notify (or command) the UE to end and / or release the sensing task corresponding to the sensing configuration;

[0487] ◆Sensing pause indication is used to notify (or command) the UE to pause the transmission or reception of sensing signals;

[0488] ◆Sense recovery indication, used to notify (or command) the UE to resume sending or receiving sense signals;

[0489] ◆ Reporting pause instruction, used to notify (or command) the UE to pause the reporting of sensing data;

[0490] ◆Report recovery instruction, used to notify (or command) the UE to resume reporting of sensing data.

[0491] In one exemplary embodiment, the second configuration message can be an existing or newly defined XnAP message, and it can be either a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the second configuration message can be sent explicitly or contained within a transparent container.

[0492] In step 702, the second network node sends a second configuration response message to the first network node.

[0493] In one exemplary embodiment of this application, the second configuration response message may include at least one of the following information or a list of information:

[0494] ■ User identifier (i.e., UE identifier), such as NG-RAN node UE XnAP ID, TMSI, RNTI, etc.;

[0495] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0496] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0497] ■ Information used to indicate whether the second network node accepts the sensing task configuration information and / or the configuration information in the sensing task configuration information list, also referred to as "feedback or response to the sensing task configuration information," is used to notify the first network node of the confirmation or acceptance status of the corresponding sensing task configuration information. This feedback or response includes at least one of the following:

[0498] ◆A confirmation or acceptance instruction for sensing task configuration information, used to indicate that the corresponding sensing task configuration information has been confirmed or accepted. This instruction may be given in at least one of the following ways:

[0499] ● Explicit indication: When the second network node receives confirmation or acceptance of the perception task configuration information, it means that the second network node has confirmed or accepted the perception task configuration information sent by the first network node.

[0500] ● Implicit indication: When no certain information is received (such as a rejection or failure indication of the perception task configuration information), it means that the second network node has acknowledged or accepted the perception task configuration information sent by the first network node.

[0501] ◆Sensing task configuration information rejection or failure indication, used to indicate that the corresponding sensing task configuration has been rejected or failed. In other words, it is used to indicate that the corresponding sensing task configuration information has not been acknowledged or accepted. The indication method includes at least one of the following:

[0502] ● Explicit indication: When a perception task configuration information rejection or failure indication is received, it means that the second network node has not acknowledged or accepted the perception task configuration information sent by the first node, i.e., the perception task configuration has failed.

[0503] ● Implicit indication: When a certain message (such as confirmation or acceptance of the perception task configuration information) is not received, it means that the second network node has not confirmed or accepted the perception task configuration information sent by the first network node, that is, the perception task configuration has failed.

[0504] ◆The reason for the rejection or failure of the task configuration information includes at least one of the following:

[0505] ●The second network node does not support sensing functionality;

[0506] ●The perception task configuration exceeds the perception capability of the second network node;

[0507] ●The UE indicated by the second configuration message is no longer within the communication coverage or sensing area of ​​the second network node;

[0508] ■ Sensing task execution status information, used to inform the first network node of the UE's sensing task execution status at the second network node. This information is only applicable when the UE is performing a sensing task at the second network node. This information includes at least one of the following:

[0509] ◆ Inactive state, indicating that the sensing device is configured with a sensing task, but is not transmitting / receiving sensing signals or reporting sensing data as indicated by the sensing configuration;

[0510] ◆Activated status, indicating that the sensing device has been configured with a sensing task and is sending / receiving sensing signals or reporting sensing data as indicated by the sensing configuration;

[0511] ◆Sensing paused state indicates that the transmission / reception of sensing signals by the sensing device is paused. The reason for the sensing pause may be poor network communication function.

[0512] ◆The reporting pause status indicates that although the sensing device is sending or receiving sensing signals and collecting sensing data, the reporting of sensing data is paused. The reason for the reporting pause may be that the network load is too heavy or the reporting link is abnormal.

[0513] ◆Abnormal state, used to indicate that an abnormality has occurred in the execution process of the sensing task. For example, due to some special reasons, an error or abnormality has occurred in the execution process of the sensing task of the sensing device.

[0514] ■ The perception capability information of the second node. This information informs the first network node of the second network node's specific perception capabilities. Only when the second network node's perception capabilities can support the current perception task will the first network node decide to transfer the UE's perception task to the second network node. This information includes at least one of the following:

[0515] ◆The maximum number of sensing tasks that can be supported simultaneously;

[0516] ◆Maximum number of UEs that can participate in sensing tasks;

[0517] ◆Supported sensing signals;

[0518] ◆Supported frequency bands for transmitting or receiving sensing signals;

[0519] ◆Supported perception modes;

[0520] ◆Supported methods for submitting perception reports.

[0521] In one exemplary embodiment, the aforementioned second configuration response message can be an existing or newly defined XnAP message, and it can be either a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the second configuration response message can be sent explicitly or contained within a transparent container.

[0522] In the above description, refer to Figure 7 The described process is included as a supplementary step. Figure 3A The method described herein is not limited thereto; see also [reference needed]. Figure 7 The described process may be excluded Figure 3A Instead of being described in the method description, it is executed as a separate method, and will not be described again.

[0523] In this application, when the sensing function is not deployed on the local equipment of the base station (e.g., the first network node or the second network node), but is deployed on a network node, core network, or sensing function entity / module outside these base stations (e.g., the fifth network node), the network node, core network, or sensing function entity / module (e.g., the fifth network node) that has deployed the sensing function can send the sensing task configuration information to the base station (e.g., the first network node or the second network node). In one example, the fifth network node can send a configuration message to the first network node or the second network node. In this example, the fifth network node can select a suitable base station to distribute the sensing task configuration information, and then the selected base station selects a suitable UE to distribute the sensing task, or the selected base station distributes the sensing task to the UE selected by the fifth network node under that base station, that is, all configurations are sent through base station-level configuration messages; optionally, the fifth network node can select a suitable base station and a suitable UE to distribute the sensing task, that is, send the UE's sensing task configuration through UE-level configuration messages.

[0524] Accordingly, in one exemplary embodiment of this application, the above references are made to... Figure 3A The described method may further include: a first network node receiving a third configuration message from a fifth network node, wherein the third configuration message includes sensing task configuration information or a list of sensing task configuration information associated with the first network node for reference; and the first network node sending a third configuration response message to the fifth network node, wherein the third configuration response message includes information indicating whether the first network node accepts the sensing task configuration information and / or the configuration information in the list of sensing task configuration information.

[0525] In one exemplary embodiment, when the third configuration message includes the perception task configuration information associated with the first network node for reference, the third configuration message may further include information for controlling the perception task execution state of the UE.

[0526] In one exemplary embodiment, the third configuration response message may further include at least one of the following: UE identifier; information identifying the sensing task; and sensing capability information of the first network node.

[0527] The following is for reference Figure 8 This will be described in detail.

[0528] Figure 8 This is a signal flow diagram illustrating a sixth example of an exemplary embodiment according to this application.

[0529] exist Figure 8In the described example, the first network node and the second network node can be a base station, a component of a base station, an access point, etc., and the fifth network node can be, for example, a core network, other network nodes where the sensing task is deployed, or a sensing function entity / module.

[0530] In step 801, the fifth network node sends a third configuration message to either the first or second network node.

[0531] In one example, the third configuration message may include UE-related sensing task configuration information or a list of sensing task configuration information. When the third configuration message includes UE-related sensing task configuration information, it may also include information for controlling the UE's sensing task execution state (also referred to as "sensing state control indication"), which may include at least one of the following:

[0532] ■ Activation indication is used to notify (or command) the UE to start performing the corresponding sensing tasks according to the sensing configuration, such as sending or receiving sensing signals as indicated by the sensing configuration, collecting and reporting sensing data, etc.

[0533] ■ Deactivation indication, used to notify (or command) the UE to end and / or release the sensing task corresponding to the sensing configuration;

[0534] ■ Sensing pause indication, used to notify (or command) the UE to pause the transmission or reception of sensing signals;

[0535] ■ Sensing recovery indication, used to notify (or command) the UE to resume sending or receiving sensing signals;

[0536] ■ Reporting pause instruction, used to notify (or command) the UE to pause the reporting of sensed data;

[0537] ■ Report recovery instruction, used to notify (or command) the UE to resume reporting of sensing data.

[0538] In one exemplary embodiment, when the third configuration message is a base station-level configuration message, the third configuration message may include a list of sensing task configuration information as described in step 301. The fifth network node (e.g., a network node or core network with deployed sensing functionality) sends the sensing task configuration information to the base station (e.g., the first or second network node) via this message. The base station then sends the sensing task configuration information to the UE selected by the base station, or to the UE selected by the fifth network node under the base station, thereby enabling the base station and the selected UE to participate in the sensing task, performing necessary sensing signal transmission and sensing result measurement and collection.

[0539] In another exemplary embodiment, when the third configuration message is a UE-level configuration message, the third configuration message may include UE-related perception task configuration information as described in step 301.

[0540] In one exemplary embodiment, the aforementioned third configuration message can be an existing NGAP or a newly defined network message, and the third configuration message can be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the third configuration message can be sent explicitly or contained within a transparent container.

[0541] In step 802, the first network node or the second network node sends a third configuration response message to the fifth network node.

[0542] In one exemplary embodiment, the third configuration response message may include at least one of the following information or a list of information:

[0543] ■ User identifier (UE identifier), such as AMF UE NGAP ID, RAN UE NGAP ID, TMSI, RNTI, etc.;

[0544] ■ Information that identifies the sensing task, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, SensingTrace ID, etc.;

[0545] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0546] ■ Information used to indicate whether the first network node accepts the sensing task configuration information or the configuration information in the sensing task configuration information list, also referred to as "feedback or response to the sensing task configuration information," is used to notify the fifth network node of the confirmation or acceptance status of the corresponding sensing task configuration information. This feedback or response includes at least one of the following:

[0547] ◆The task configuration information is confirmed or an instruction is accepted, and the instruction is given in at least one of the following ways:

[0548] ● Explicit indication: When the first / second network node receives confirmation or acceptance of the perception task configuration information, it means that the first / second network node has confirmed the perception task configuration information sent by the fifth network node.

[0549] ● Implicit indication: When no certain information is received (such as a rejection or failure indication of the perception task configuration information), it means that the first / second network node has acknowledged or accepted the perception task configuration information sent by the fifth network node.

[0550] ◆The task configuration information is rejected or failed, and the indication includes at least one of the following methods:

[0551] ● Explicit indication: When a perception task configuration information rejection or failure indication is received, it means that the first / second network node has not acknowledged the perception task configuration information sent by the fifth network node.

[0552] ● Implicit indication: When a certain message (such as confirmation or acceptance of perception task configuration information) is not received, it means that the first / second network node has not confirmed or accepted the perception task configuration information sent by the fifth network node.

[0553] ◆The reason for the rejection or failure of the task configuration information includes at least one of the following:

[0554] ●The first / second network node does not support sensing functionality;

[0555] ●The perception task configuration exceeds the perception capabilities of the first / second network nodes;

[0556] ●The UE indicated by the second configuration message is no longer within the sensing area of ​​the first / second network node;

[0557] ■ Sensing task execution status information, used to notify the UE of the sensing task execution status to the fifth network node (e.g., a network node with sensing capabilities, the core network, or a sensing capability entity / module), and may specifically include at least one of the following information:

[0558] ◆ Inactive state, indicating that the sensing device is configured with a sensing task, but is not transmitting / receiving sensing signals or reporting sensing data as indicated by the sensing configuration;

[0559] ◆Activated status, indicating that the sensing device has been configured with a sensing task and is sending / receiving sensing signals or reporting sensing data as indicated by the sensing configuration;

[0560] ◆Sensing paused state indicates that the transmission / reception of sensing signals by the sensing device is paused. The reason for the sensing pause may be poor network communication function.

[0561] ◆The reporting pause status indicates that although the sensing device is sending or receiving sensing signals and collecting sensing data, the reporting of sensing data is paused. The reason for the reporting pause may be that the network load is too heavy or the reporting link is abnormal.

[0562] ◆Abnormal state, used to indicate that an abnormality has occurred in the execution process of the sensing task. For example, due to some special reasons, an error or abnormality has occurred in the execution process of the sensing task of the sensing device.

[0563] ■ The sensing capability information of the first / second network nodes. The fifth network node (e.g., a network node with sensing capabilities, the core network, or a sensing entity / module) will pre-store the base station's sensing capability information. The base station can also dynamically update the sensing capability information to the fifth network node according to the actual network conditions. The reason for the dynamic change of the sensing capability information may be related to the degree to which base station resources are used for communication. The sensing capability information includes at least one of the following:

[0564] ◆The maximum number of sensing tasks that can be supported simultaneously;

[0565] ◆Maximum number of UEs that can participate in sensing tasks;

[0566] ◆Supported sensing signals;

[0567] ◆Supported frequency bands for transmitting or receiving sensing signals;

[0568] ◆Supported perception modes;

[0569] ◆Supported methods for submitting perception reports.

[0570] In this application, the third configuration response message is used to transmit feedback regarding the perception task configuration to the fifth network node. In one exemplary embodiment, the aforementioned third configuration response message can be an existing NGAP or a newly defined network message, and the third configuration response message can be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the third configuration response message can be sent explicitly or contained in a transparent container.

[0571] In the above description, refer to Figure 8 The described process is included as a supplementary step. Figure 3A The method described herein is not limited thereto; see also [reference needed]. Figure 8 The described process may be excluded Figure 3A Instead of being described in the method description, it is executed as a separate method, and will not be described again.

[0572] In this application, when the UE switches from the source base station to the target base station and communicates with the target base station, since the UE only has an RRC connection with the target base station, the sensing results can only be reported to the target base station. If the sensing function is located at the source base station, and the source base station needs to obtain the UE's sensing results for sensing data analysis, then the target base station needs to report the sensing results to the source base station. The target base station can also send updated / preferred / suggested / recommended sensing task configurations to the source base station. In one example, the first network node is the source base station, and the second network node is the target base station. After the UE switches from the first network node to the second network node, the UE continues to transmit / receive sensing signals and report sensing data at the second network node, such as... Figure 9 The example is shown in the image.

[0573] Accordingly, in one exemplary embodiment, the above references Figure 3A The described method may further include: a first network node receiving a first notification message from a second network node, wherein the first notification message includes a perception report reported by the UE to the second network node; and the first network node sending a first notification response message to the second network node, wherein the first notification response message is used to transmit feedback to the second network node regarding the first notification message, wherein if the perception function is not deployed on the first network node, the first network node forwards the perception report to the node where the perception function is deployed. In this application, the operation of the first network node receiving the first notification message from the second network node is performed after the UE switches from the first network node to the second network node.

[0574] In one exemplary embodiment, the first notification message may further include at least one of the following: information identifying the sensing device or a list of identifiers identifying the sensing device; and the UE's sensing area monitoring results.

[0575] In one exemplary embodiment, the perception report includes at least one of the following: UE identifier; information identifying the perception task performed by the UE; perception mode information; perception result; and identifier of the perception device that interacts with the UE to perceive signals.

[0576] The following is for reference Figure 9 This will be described in detail.

[0577] Figure 9 This is a signal flow diagram illustrating a seventh example of an exemplary embodiment according to this application.

[0578] exist Figure 9In the described example, the first network node may be, for example, a source base station, the second network node may be, for example, a target base station, the third / fourth network node may be, for example, a UE, and the fourth network node may be another UE participating in the sensing task, other than the third node, selected by the second network node according to the sensing task configuration.

[0579] In step 901, the third network node (e.g.) Figure 3B The third or fourth network node (as mentioned in the context) sends a first report message to the second network node. Specifically, the third or fourth network node can transmit / receive sensing signals according to the sensing task configuration and collect sensing data to form a sensing report. When the reporting conditions in the sensing task configuration information are met, the third or fourth network node sends a first report message to the second network node. The first report message may include the sensing report reported by the third network node (e.g., the UE) or the fourth network node to the second network node. The first report message can be an existing RRC message or a reporting message specifically defined for sensing. In addition, the message can be sent using existing signaling radio bearers (SRBs) (e.g., SRB1, SRB4, etc.) or reported using radio bearers specifically defined for sensing, such as SRB6, SRB7, and sensing-dedicated data radio bearers (DRBs). Sensing data can also be sent through the user plane or other newly defined protocol planes.

[0580] In one exemplary embodiment, the first report message includes at least one of the following: ■ User identifier (UE identifier), such as TMSI, C-RNTI, I-RNTI, etc.;

[0581] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0582] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0583] ■ The time or period of data collection, where the time of data collection refers to a specific time, and the period of time refers to a relative time range;

[0584] ■ Reporting time: Since there may be a delay between the time the perceived data is reported and the time the perceived function receives the report, the reporting time can help analyze the intermediate delay.

[0585] ■ Types of sensing signals, such as CSI-RS, DMRS, PRS, SRS, etc.;

[0586] ■ Perceive pattern information, as described in step 301;

[0587] ■The specific perception result includes at least one of the following:

[0588] ◆ Measurement results of the sensed signal, such as the signal's RSRP and / or RSRQ, path loss, Doppler shift, and signal's angle of arrival AoA and ZoA;

[0589] ◆Intermediate results of perception, such as perceiving the position and / or shape of an object; perceiving the scattering cross section (RCS) of an object; the velocity, acceleration and / or direction of an object; perceiving environmental information, etc.

[0590] ◆The final result of the perception task, such as detecting intruding objects, abnormal traffic conditions, abnormal weather, etc.;

[0591] The above-mentioned perception results can be obtained by the sensing device using local computing power, or they can be obtained through external computing power.

[0592] ■ Device identifier of the device that interacts with the UE to sense signals.

[0593] The information listed above constitutes a perception report, which can be sent explicitly or in a transparent container. When sent explicitly to the base station, the base station can use the information in the perception report to assist in network optimization.

[0594] ■ The results of UE's sensing area monitoring, such as UE's indication within the sensing area, UE's indication of moving out of the sensing area, and UE's historical information within the sensing area, will only be carried in the first report message when the UE performs sensing area monitoring.

[0595] ■Information that the UE is about to move out of the sensing area. When the UE detects that it is about to leave the sensing area, it can send a sensing report, and the sensing report can carry this information to inform the network that the UE is about to move out of the sensing area, so that the network can make corresponding adjustments or interactions.

[0596] ■The time when the UE is about to leave the sensing area.

[0597] ■ Data Radio Bearer (DRB) ID is used to represent the DRB resources used by the UE for sensing task-related data transmission.

[0598] In step 902, the second network node sends a first notification message to the first network node.

[0599] In one exemplary embodiment, the first notification message may include at least one of the following information or a list of information:

[0600] ■ User identifier (i.e., UE identifier), such as XnAP NG-RAN UE XnAP ID, TMSI, RNTI, etc.;

[0601] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0602] ■ Information identifying the sensing device or a list of information identifying the sensing device, such as a base station identifier or a user identifier. When the sensing device includes a UE, the first notification message needs to carry the UE identifier corresponding to the sensing report, as described in step 301. This identifier can be an identifier that is transmitted from the source base station to the base station accessed by the UE as it moves. The source base station stores this identifier, and when it receives the sensing report, it can identify the user corresponding to the sensing report based on the user identifier therein.

[0603] ■ The sensing report collected by the corresponding sensing device, with specific information as described in step 901;

[0604] ■ The UE's sensing area monitoring results, such as the UE's indication within the sensing area, the UE's indication of moving out of the sensing area, and the UE's historical information within the sensing area, will only be carried in the first notification message when the UE performs sensing area monitoring.

[0605] ■ Updated / preferred / suggested / recommended perception task configuration information, as described in step 301.

[0606] ■ Indication that the UE is about to leave the sensing area.

[0607] ■The time when the UE is about to leave the sensing area.

[0608] ■DRB ID, used to represent the DRB resources used by the UE for sensing task-related data transmission.

[0609] In this application, the first notification message can be a base station-level message or a UE-level message. The first notification message enables the base station to collect the perception results of the UE during movement in a timely manner, and to update or adjust the perception configuration according to the actual perception situation and network conditions.

[0610] In one exemplary embodiment, the aforementioned first notification message may be an existing XnAP message (e.g., an RRC transmission message) or a newly defined network message. Furthermore, the first notification message may be a UE-Associated message or a non-UE-Associated message. Additionally, the various information contained in the first notification message may be sent explicitly or contained within a transparent container.

[0611] In step 903, the first network node sends a first notification response message to the second network node.

[0612] In one exemplary embodiment, the first notification response message may include at least one of the following information or a list of information;

[0613] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0614] ■ Information identifying sensing devices or a list of information identifying sensing devices, such as base station identifiers or user identifiers;

[0615] ■ Feedback on the receipt of perception reports includes one of the following:

[0616] ◆ A successful receipt indication of the perception report (also referred to as an indication confirming the perception report) may be provided in at least one of the following ways:

[0617] ● Explicit indication: When an indication confirming the perception report is received, it means that the first network node has received the perception report sent by the second network node.

[0618] ● Implicit indication: When a certain message is not received (e.g., a perception report reception failure indication), it means that the first network node has received the perception report sent by the second network node.

[0619] ◆The perception report receives a failure indication, which includes at least one of the following methods:

[0620] ● Explicit indication: When a perception report reception failure indication is received, it means that the first network node has not received the perception report sent by the second network node.

[0621] ● Implicit indication: If a certain message is not received (e.g., a successful reception indication of a perception report), it means that the first network node has not received the perception report sent by the second network node.

[0622] ■ Feedback or response regarding the sensing task configuration information, used to notify the target base station (i.e., the second network node) of the confirmation status of the corresponding sensing task configuration information. This feedback or response includes at least one of the following:

[0623] ◆Confirm or accept the task configuration information, wherein the indication is made in at least one of the following ways:

[0624] ● Explicit indication: When the first network node receives confirmation or acceptance of the perception task configuration information, it means that the first network node has confirmed or accepted the perception task configuration information sent by the second network node.

[0625] ● Implicit indication: When a certain message is not received (such as a rejection or failure indication of the perception task configuration information), it means that the first network node has acknowledged or accepted the perception task configuration information sent by the second network node.

[0626] ◆ Sensing task configuration information rejection or failure indication, the indication method including at least one of the following:

[0627] ● Explicit indication: When a perception task configuration information rejection or failure indication is received, it means that the first network node has not acknowledged the perception task configuration information sent by the second network node.

[0628] ● Implicit indication: When a certain message (such as confirmation of perception task configuration information or acceptance indication) is not received, it means that the first network node has not confirmed the perception task configuration information sent by the second network node.

[0629] In this application, the first notification response message is used to transmit feedback regarding the first notification message to the second network node. Specifically, after receiving the first notification message, if the sensing function is deployed on the first network node, the first network node performs sensing-related calculations based on the information in the received first notification message to obtain the final sensing result, and then sends the first notification response message to the second network node. If the sensing function is not deployed on the first network node, the first network node forwards the sensing report received from the second network node to the network node that has deployed the sensing function. The function of the first notification response message is to provide feedback information from the receiving node of the sensing result or the preferred sensing task configuration information to the sending node.

[0630] In one exemplary embodiment, the aforementioned first notification response message can be an existing XnAP message or a newly defined network message. Furthermore, the first notification message can be a UE-Associated message or a non-UE-Associated message. Additionally, the various information contained in the first notification message can be sent explicitly or contained within a transparent container. Optionally, the first network node may choose not to send the first notification response message to the second network node after receiving the first notification message (including the perception report).

[0631] Furthermore, the above examples apply not only to the case where the sensing function is deployed on the first network node, but also to the case where the first network node needs to collect sensing results (e.g., the first network node needs to use the sensing results for network optimization).

[0632] In the above description, refer to Figure 9 The described process is included as a supplementary step. Figure 3A The method described herein is not limited thereto; see also [reference needed]. Figure 9 The described process may be excluded Figure 3A Instead of being described in the method description, it is executed as a separate method, and will not be described again.

[0633] In this application, when the sensing function is not deployed on the local equipment of the base station, but on other network nodes or the core network, the base station can send the collected sensing reports to the network nodes or core network that have deployed the sensing function, and can also send updated / preferred / recommended / suggested sensing task configuration information to the network nodes or core network that have deployed the sensing function.

[0634] The following reference Figure 10 This will be described in detail.

[0635] Figure 10 This is a signal flow diagram illustrating an eighth example of an exemplary embodiment according to this application.

[0636] exist Figure 10 In the described example, the second network node can be, for example, a target base station, and the fifth network node can be, for example, the core network, other network nodes where the sensing task is deployed, or sensing function entities / modules.

[0637] In step 1001, the second network node sends a second notification message to the fifth network node.

[0638] In one exemplary embodiment, the second notification message may include at least one of the following information or a list of information:

[0639] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0640] ■ Information identifying sensing devices or a list of information identifying sensing devices, such as base station identifiers or user identifiers;

[0641] ■ The perception report collected by the corresponding sensing device, which may be collected by the base station or the UE, and the content of the perception report is as described in step 901;

[0642] ■ Updated / preferred / suggested / recommended perception task configuration information, as described in step 301.

[0643] ■DRB ID, used to represent the DRB resources used by the UE for sensing task-related data transmission.

[0644] As described above, the second notification message may include the perception report reported by the UE in step 901. Furthermore, the second notification message may also include perception data measured and collected by the second network node itself according to the perception configuration. Additionally, the second notification message may include a suggestion for updating the perception task configuration based on the actual network conditions, or the actual updated configuration. Through this message, the second network node can send the collected perception report and the preferred perception task configuration to network nodes or the core network that have deployed perception functionality. This message also allows the base station to collect perception results from the UE during movement in a timely manner, and to update or adjust the perception task configuration according to the actual perception situation and network conditions.

[0645] In one exemplary embodiment, the second notification message can be an existing NGAP message (e.g., a path transition request message) or a newly defined network message, and the first notification message can be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the second notification message can be sent explicitly or contained within a transparent container.

[0646] In step 1002, the fifth network node sends a second notification response message to the second network node.

[0647] In one exemplary embodiment of this application, the second notification response message may include at least one of the following information or a list of information:

[0648] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0649] ■ Information identifying sensing devices or a list of information identifying sensing devices, such as base station identifiers or user identifiers;

[0650] ■ Feedback on the receipt of perception reports includes one of the following:

[0651] ◆ A successful receipt indication of the perception report (also known as an indication confirming the perception report) may be provided, and this indication may include at least one of the following:

[0652] ● Explicit indication: When an indication confirming the perception report is received, it means that the fifth network node has received the perception report sent by the second network node;

[0653] ● Implicit indication: When a certain message is not received (e.g., a perception report reception failure indication), it means that the fifth network node has already received the perception report sent by the second network node.

[0654] ◆The perception report receives a failure indication, which may include at least one of the following methods:

[0655] ● Explicit indication: When a perception report reception failure indication is received, it means that the fifth network node has not received the perception report sent by the second network node.

[0656] ● Implicit indication: When a certain message (such as a successful reception indication of a perception report) is not received, it means that the fifth network node has not received the perception report sent by the second network node.

[0657] ■ Feedback or response regarding the perception task configuration information, used to notify the second network node of the confirmation or non-confirmation status of the corresponding perception task configuration information. This feedback or response includes at least one of the following:

[0658] ◆Confirm or accept the task configuration information, and the method of instruction may include at least one of the following:

[0659] ● Explicit indication: When the fifth network node receives confirmation or acceptance of the perception task configuration information, it means that the fifth network node has confirmed or accepted the perception task configuration information sent by the second network node.

[0660] ● Implicit indication: When no certain information is received (such as a rejection or failure indication of the perception task configuration information), it means that the fifth network node has acknowledged or accepted the perception task configuration information sent by the second network node.

[0661] ◆The task configuration information is perceived as a rejection or failure indication, which may include at least one of the following methods:

[0662] ● Explicit indication: When a perception task configuration information rejection or failure indication is received, it means that the fifth network node has not acknowledged or accepted the perception task configuration information sent by the second network node.

[0663] ● Implicit indication: When a certain message (such as an indication of confirmation or acceptance of the perception task configuration information) is not received, it means that the fifth network node has not confirmed or accepted the perception task configuration information sent by the second network node.

[0664] In this application, the second notification response message is used to transmit feedback regarding the second notification message to the second network node. In an exemplary embodiment, the second notification response message may be an existing NGAP message (e.g., a path transition request response message) or a newly defined network message, and it may be a UE-Associated message or a non-UE-Associated message. Furthermore, the various information contained in the second notification response message may be sent explicitly or contained within a transparent container.

[0665] In the examples described above, the UE handover scenario involves between two base stations (i.e., the first network node and the second network node). However, in reality, a UE's movement may pass through multiple base stations (i.e., multiple network nodes), resulting in multiple handovers. For example, as will be discussed below... Figure 11 In the described example, when the UE moves to a network node other than the second network node (e.g., the seventh network node), if the first node is still the perception task control node or a node that needs to receive perception reports, the seventh network node may need to interact with the first network node in some ways, such as perception task transfer requests, perception task configuration update requests, and perception report sending.

[0666] ■ Perception Task Transfer Request: Perception task transfer may occur during the UE's handover from the first network node to the second network node and from the second network node to other network nodes. However, during UE movement, the first network node may always be the perception task control node (i.e., controlling the UE's perception tasks). Therefore, when the UE moves to other base stations (e.g., as shown in the following reference)... Figure 11In the example described, the seventh network node needs to send a sensing task transfer request to the first network node and perform certain interactions (as described in steps 1101 and 1102 below). Furthermore, to ensure that the seventh network node knows the information of the UE's sensing task control node (…), Figure 11 In the example, the first network node), during each handover process, whenever a UE-related sensing task is sent to the target base station, the corresponding message needs to carry the UE's sensing task control node information (e.g., Global NG-RAN node ID) and the UE identifier that the target base station can recognize (e.g., NG-RAN XnAP UE ID). Thus, after receiving the corresponding message, the target base station (e.g., the seventh network node) can recognize that the first network node is the UE's sensing task control node and send a sensing task transfer request to the first network node.

[0667] ■ Perception Task Configuration Update Request: After the UE moves to the seventh network node, the seventh network node can send a perception task configuration update request to the first network node based on the actual perception status, network resource configuration, etc. The first network node can then send the updated perception task configuration back to the seventh network node.

[0668] ■Perception Report Transmission: The seventh network node may receive perception reports sent by the UE. If the first network node is a network node that has deployed perception functionality or requires perception reports, the seventh network node will send the perception report to the first network node. The perception report can be sent in the following ways:

[0669] ◆ Hop-by-hop forwarding: The seventh network node sends the perception report to the network node that the UE accessed before, and then forwards it hop-by-hop to the previous network nodes until it is finally sent to the first network node.

[0670] ◆Direct Forwarding: The perception task configuration received by the seventh network node contains the identification information of the first network node. If a network interface (e.g., XnAP) exists between the seventh and first network nodes, the seventh network node can directly send the perception report to the first network node through this network interface. The perception report needs to carry a UE identifier that the first network node can recognize, so that the first network node can determine the UE corresponding to the perception report. Furthermore, to ensure that the seventh network node knows the information of the network node that needs to receive the perception report (…), Figure 11In the example, the first network node is used. During each handover process, as long as the UE-related perception task is sent to the target base station, the corresponding message needs to carry the node information that needs to receive the perception report and the UE identifier that the node can recognize (such as NG-RAN XnAP UEID). In this way, after receiving the corresponding message, the seventh network node can recognize that the first network node is the network node that needs to receive the perception report and send the perception report to the first network node.

[0671] ◆ Forwarding via the core network: If there is no available network interface between the seventh network node and the first network node, the perception report can be forwarded to the first network node via the core network.

[0672] Accordingly, in one exemplary embodiment of this application, the above references are made to... Figure 3A The described method may further include: a first network node receiving a third notification message from a seventh network node, wherein the third notification message includes a fifth perception task transfer request for requesting the transfer of the UE's perception task to the seventh network node; and the first network node sending a third notification response message to the seventh network node, wherein the third notification response message includes information indicating whether the first network node accepts the fifth perception task transfer request.

[0673] In one exemplary embodiment, the third notification message may further include at least one of the following: information identifying the sensing task performed by the UE; the reason for requesting a sensing task transfer; a sensing task configuration update request; sensing mode information of the UE; sensing area information of the seventh network node; sensing capability information of the seventh network node; and an identifier of the sensing device that collected the sensing report.

[0674] In one exemplary embodiment, the third notification response message may further include at least one of the following: a UE identifier; information identifying the sensing task performed by the UE; information for controlling the execution state of the sensing task of the UE; and feedback information for receiving the sensing report.

[0675] The following reference Figure 11 This will be described in detail.

[0676] Figure 11 This is a signal flow diagram illustrating a ninth example of an exemplary embodiment according to this application.

[0677] exist Figure 11 In the described example, the first network node can be, for example, a source base station, the second network node can be a base station, and the seventh network node can be, for example, a target base station to which the UE, other than the first and second network nodes, has switched after multiple handover operations.

[0678] exist Figure 11Prior to step 1101, the UE has switched from the first network node to the seventh network node, but the UE's perception tasks have not been transferred to the seventh network node and are still controlled by the first network node. In this case, in step 1101, the seventh network node sends a third notification message to the first network node.

[0679] In one exemplary embodiment, the third notification message may include at least one of the following information or a list of information:

[0680] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0681] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0682] ■ The request for a perception task transfer (i.e., an instruction to request a perception task transfer) and the reason for requesting a perception task transfer are as described in step 401;

[0683] ■ Perception task configuration update request, as described in step 401;

[0684] ■ Current UE perception mode information, as described in step 401;

[0685] ■ The current UE's perception task execution status information, as described in step 401;

[0686] ■Information on the perception area and perception capability of the seventh node, as described in step 401;

[0687] ■ The perception report collected by the seventh node and the identifier of the device that collected the perception report. When the perception device is a UE, it needs to carry a user identifier that can be recognized by the first network node. This user identifier can be obtained from the network node of the previous UE.

[0688] As described above, the third notification message may include a perception task transfer request (i.e., a fifth perception task transfer request) for transferring the UE's perception task to the seventh network node. Specifically, the seventh network node determines, based on the perception task configuration received from the network node that previously served the UE, whether the first network node is the UE's perception task control node or a network node that needs to receive perception reports. Therefore, the seventh network node sends a third notification message to the first network node, which enables the base station most recently accessed by the UE to complete the control process related to the perception task in the event of multiple handovers.

[0689] In step 1102, the first network node sends a third notification response message to the seventh network node.

[0690] In one exemplary embodiment, the third notification response message may include at least one of the following information or a list of information:

[0691] ■ Information that identifies the sensing task being performed by the UE, also known as the "sensing task identifier", is used to identify the sensing task that the UE is currently performing, such as Sensing Service ID, Sensing Task ID, Sensing Session ID, Sensing Trace ID, etc.;

[0692] ■ Information on sensing service type or sensing use case, used to indicate the type of sensing task, such as target object detection, intrusion detection, environmental monitoring, autonomous driving, road monitoring, weather monitoring, life monitoring, smart factory, etc.

[0693] ■ User identifier (i.e., UE identifier), such as NG-RAN node UE XnAP ID, TMSI, RNTI, etc.;

[0694] ■ Information used to indicate whether the first network node accepts the sensing task transfer request, also known as "response or reply to the sensing task transfer request", as described in step 402;

[0695] ■ Preferred / suggested / updated / recommended perception task configuration information, as described in step 402; ■ Information used to control the perception task execution state of the UE, also referred to as "perception state control indication", as described in step 402;

[0696] ■ A successful receipt of the perception report is indicated, as described in step 903;

[0697] ■ A perception report reception failure indication is provided, as described in step 903.

[0698] As described above, the first network node can send a third notification response message to the seventh network node based on the information sent by the seventh network node. This message is used to provide feedback to the seventh network node on the results of the interaction between the first network node and the seventh network node regarding the perception task.

[0699] In the above description, refer to Figure 11 The described process is included as a supplementary step. Figure 3A The method described herein is not limited thereto; see also [reference needed]. Figure 11 The described process may be excluded Figure 3A Instead of being described in the method description, it is executed as a separate method, and will not be described again.

[0700] Figure 12 This illustrates a method performed by a second network node according to an exemplary embodiment of this application.

[0701] like Figure 12 As shown, in step S1210, the second network node receives a first request message related to handover from the first network node. The first request message includes a first sensing task transfer request and sensing task configuration information associated with the first network node for reference. The first sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node.

[0702] In step S1220, the second network node sends a first response message to the first network node in response to the first request message. The first response message includes information indicating whether the second network node accepts the first sensing task transfer request and information indicating whether the second network node accepts the sensing task configuration information.

[0703] In addition, the method may further include: receiving a first configuration response message from the UE by a second network node, the message being a response message to the first configuration message.

[0704] As mentioned above Figure 3B The interaction process between the first network node (i.e., the source base station) and the second network node (i.e., the target base station) has been described in detail, so it will not be repeated here.

[0705] In one exemplary embodiment of this application, Figure 12The method may further include: when the second network node determines that the UE has moved out of the sensing area of ​​the first network node, the second network node sends a second request message to the first network node, wherein the second request message includes a second sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the second sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; the second network node receives a second response message from the first network node in response to the second request message, wherein the second response message is used to indicate whether the first network node accepts the second sensing task transfer request.

[0706] As mentioned above Figure 4 The interaction process between the first network node and the second network node has been described in detail, so it will not be repeated here.

[0707] In one exemplary embodiment of this application, Figure 12 The method may further include: when the second network node determines that the UE has moved out of the sensing area of ​​the first network node, the second network node sends a third request message to the fifth network node, wherein the third request message includes a sixth sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the sixth sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; the second network node receives a third response message from the fifth network node in response to the third request message, wherein the third response message includes information indicating whether the first network node accepts the sixth sensing task transfer request.

[0708] In one exemplary embodiment, the sixth perception task transfer request may be forwarded by the fifth network node to the first network node as the third perception task transfer request as described above.

[0709] In one exemplary embodiment of this application, the third request message may further include at least one of the following: UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; the reason for requesting a transfer of the sensing task; information on the sensing area of ​​the second network node; and sensing capability information of the second network node.

[0710] In one exemplary embodiment of this application, the third response message may further include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information related to sensing area updates; and information for controlling the sensing task execution state of the UE.

[0711] As mentioned above Figure 5The interaction process between the second and fifth network nodes has been described in detail, so it will not be repeated here.

[0712] In one exemplary embodiment of this application, Figure 12 The method may further include: receiving a sixth request message from a fifth network node by a second network node, wherein the sixth request message includes a seventh sensing task transfer request and / or information about the UE moving out of the sensing area, wherein the seventh sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node; and sending a sixth response message from the second network node to the fifth network node in response to the sixth request message, wherein the sixth response message includes information indicating whether the second network node accepts the seventh sensing task transfer request.

[0713] In one exemplary embodiment, the fourth perception task transfer request as described above can be forwarded by the fifth network node to the second network node as the seventh perception task transfer request.

[0714] In one exemplary embodiment of this application, the sixth request message may further include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information of the cell where the sensing signal with the UE was last detected; and the reason for requesting a sensing task transfer.

[0715] In one exemplary embodiment of this application, the sixth response message may further include at least one of the following: a UE identifier or a list of UE identifiers; information identifying the sensing task performed by the UE; information on the sensing area of ​​the second network node; and information suggesting an adjustment to the sensing area range of the first network node.

[0716] As mentioned above Figure 6 The interaction process between the second and fifth network nodes has been described in detail, so it will not be repeated here.

[0717] In one exemplary embodiment of this application, Figure 12 The method may further include: a second network node receiving a second configuration message from a first network node, wherein the second configuration message includes sensing task configuration information or a list of sensing task configuration information associated with the first network node for reference; and the second network node sending a second configuration response message to the first network node, wherein the second configuration response message includes information indicating whether the second network node accepts the sensing task configuration information or the configuration information in the list of sensing task configuration information.

[0718] As mentioned above Figure 7The interaction process between the first network node and the second network node has been described in detail, so it will not be repeated here.

[0719] In one exemplary embodiment of this application, Figure 12 The method may further include: a second network node receiving a fourth configuration message from a fifth network node, wherein the fourth configuration message includes sensing task configuration information or a list of sensing task configuration information associated with a first network node for reference; and the second network node sending a fourth configuration response message to the fifth network node, wherein the fourth configuration response message includes information indicating whether the first network node accepts the sensing task configuration information or the configuration information in the list of sensing task configuration information. In this application, the information contained in the fourth configuration message and the fourth configuration response message are respectively related to the above-mentioned references. Figure 8 The information contained in the described third configuration message and third configuration response message is similar or the same.

[0720] In one exemplary embodiment of this application, when the fourth configuration message includes the perception task configuration information associated with the first network node for reference, the fourth configuration message also includes information for controlling the perception task execution state of the UE.

[0721] In one exemplary embodiment of this application, the fourth configuration response message may further include at least one of the following: UE identifier; information identifying the sensing task performed by the UE; and sensing capability information of the second network node.

[0722] As mentioned above Figure 8 The interaction process between the second and fifth network nodes has been described in detail, so it will not be repeated here.

[0723] In one exemplary embodiment of this application, Figure 12 The method may further include: a second network node receiving a first report message from a UE, wherein the first report message includes a perception report generated by the UE; if the perception function is deployed on a first network node, the second network node sending a first notification message to the first network node and receiving a first notification response message from the first network node, wherein the first notification message includes the perception report, and wherein the first notification response message is used to transmit feedback about the first notification message to the second network node; if the perception function is deployed on a fifth network node, the second network node sending a second notification message to the fifth network node and receiving a second notification response message from the fifth network node, wherein the second notification message includes the perception report, and wherein the second notification response message is used to transmit feedback about the second notification message to the second network node.

[0724] In one exemplary embodiment of this application, the first report message may further include at least one of the following: the UE's sensing area monitoring results; and information that the UE is about to move out of the sensing area, used to indicate that the UE is about to move out of the sensing area of ​​the second network node.

[0725] In one exemplary embodiment of this application, the second report message may further include an updated perception task configuration.

[0726] In one exemplary embodiment of this application, the second notification response message may include at least one of the following: information identifying the sensing task performed by the UE; an identifier or list of identifiers of the sensing device; feedback on receiving the sensing report; and feedback or response on the sensing task configuration information.

[0727] As mentioned above Figure 9 The above-described interaction process between the UE, the first network node, and the second network node is described in detail, and references are made to... Figure 10 The interaction process between the second and fifth network nodes has been described in detail above, so it will not be repeated here.

[0728] Figure 13 This is a flowchart illustrating a method performed by a UE according to an exemplary embodiment of this application.

[0729] like Figure 13 As shown, in step S1310, the UE receives a first configuration message from the second network node from the first network node.

[0730] In this application, the first configuration message may include at least one of the following: information identifying the sensing task; information on the sensing service type; information related to the sensing device; information identifying the receiving node of the sensing report; information on the sensing area; and information controlling the execution status of the UE's sensing task. In this application, the UE can update the sensing task configuration based on the information included in the first configuration message.

[0731] In this application, a first configuration message may be included in a first response message sent by a second network node to a first network node. The first response message may be a message in which the second network node responds to a first request message sent by the first network node. The first request message may include a first sensing task transfer request and sensing task configuration information associated with the first network node for reference. The first sensing task transfer request may be used to request the transfer of the UE's sensing task to the second network node. The first response message includes information indicating whether the second network node accepts the first sensing task transfer request and information indicating whether the second network node accepts the sensing task configuration information.

[0732] In step S1320, the UE sends a message responding to the first configuration message to the second network node.

[0733] also, Figure 13 The method may further include: the UE sending a first report message to a second network node, wherein the first report message includes a perception report generated by the UE. Since the above has already been referred to... Figure 9 This has been described in detail, so it will not be repeated here.

[0734] In one example, as referenced above Figure 3B In the described example, in step 303, the UE may receive a first configuration message from the source base station. This first configuration message may be, for example, an RRC reconfiguration message. In one example, the target base station sends a handover request confirmation message to the source base station, which may include the RRC reconfiguration message. The UE then receives the RRC reconfiguration message from the source base station. In this application, the first configuration message may be an existing RRC reconfiguration message, a newly defined RRC message, or a lower-level message. Furthermore, the first configuration message may be transmitted explicitly or contained within a transparent container.

[0735] In addition, such as Figure 3B As shown, the UE can send a message to the target base station in response to the first configuration message, also known as the "first configuration response message". This message can be, for example, an RRC reconfiguration completion message. This message is a response to the first configuration message (e.g., the RRC reconfiguration message), indicating that the UE has successfully accessed the target base station.

[0736] As mentioned above Figure 3B This has been described in detail, so it will not be repeated here.

[0737] Figure 14 This is a block diagram illustrating a network node according to an exemplary embodiment of this application.

[0738] like Figure 14 As shown, network node 1400 may include transceiver 1410 and processor 1420, wherein transceiver 1410 can be used to transmit and receive signals, and processor 1420 may be coupled to transceiver 1410 and configured to perform the above-described functions. Figures 3A to 12 The method described. Network node 1400 can be the above reference. Figures 3A to 12 Any one of the first network node, second network node, fifth network node, and other network nodes in the described method. For details regarding the operation of the above method, please refer to... Figure 3A and Figure 12 The descriptions will not be repeated here.

[0739] Figure 15 This is a block diagram illustrating a UE according to an exemplary embodiment of this application.

[0740] like Figure 15 As shown, UE 1500 may include a transceiver 1510 and a processor 1520, wherein the transceiver 1510 can be used to transmit and receive signals, and the processor 1520 may be coupled to the transceiver 1510 and configured to perform the above-described functions. Figure 13 The method described. UE 1500 can be referenced above. Figures 3A to 13 The method described refers to any one of the third network node, the fourth network node, or the UE. For details regarding the operation of the above method, please refer to [link to relevant documentation]. Figures 3A to 13 The relevant descriptions in the text will not be repeated here.

[0741] This disclosure provides a computer-readable storage medium for storing instructions that, when executed by at least one processor, cause the at least one processor to perform or implement the steps and corresponding content of the foregoing method embodiments.

[0742] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments.

[0743] The terms “first,” “second,” “third,” “fourth,” “1,” “2,” etc. (if present) in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in a sequence other than that shown in the figures or text.

[0744] It should be understood that although arrows indicate various operation steps in the flowcharts of the embodiments of this disclosure, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of the embodiments of this disclosure, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on the actual implementation scenario. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured as required, and the embodiments of this disclosure do not limit this.

[0745] The above text and accompanying drawings are provided as examples only to help the reader understand this disclosure. They are not intended and should not be construed as limiting the scope of this disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art, based on the content disclosed herein, that changes can be made to the illustrated embodiments and examples, and other similar implementations based on the technical concept of this disclosure can be adopted without departing from the scope of this disclosure, and these modifications and modifications are also within the protection scope of the embodiments of this disclosure.

Claims

1. A method executed by a first network node, comprising: A first network node sends a handover-related first request message to a second network node, wherein the first request message includes a first sensing task transfer request and sensing task configuration information associated with the first network node for reference, wherein the first sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node. The first network node receives a first response message from the second network node in response to the first request message. The first response message includes information indicating whether the second network node accepts the first sensing task transfer request and information indicating whether the second network node accepts the sensing task configuration information.

2. The method according to claim 1, wherein, The perception task configuration information includes at least one of the following: UE's perception mode information; Information about the sensing device that interacts with the UE to sense signals; Perceive task activation indication; UE's perception task control node information; The UE identifier corresponding to the perception report.

3. The method according to claim 1, wherein, The first request message also includes at least one of the following: A list of configuration information for the perception task; and Request information that requires the participation or assistance of a second network node in the sensing task.

4. The method according to claim 3, wherein, Each item in the perception task configuration information list includes at least one of the following: Information identifying the first network node; Identify and perceive information for the task; Perceive information about the type of service; Information related to sensing devices; Information about the sensing area of ​​the first network node; Information about the receiving node of the perception report; and Information on whether the sensing task supports transfer.

5. The method according to claim 4, wherein, The information related to the sensing device includes at least one of the following: Information identifying the perception group; Perceptual ability information; Perceive pattern information; Report the perception results; Information related to the reporting of perception reports.

6. The method according to claim 1, wherein, The first response message also includes at least one of the following: Information related to the UE's perception tasks; and Notification regarding the participation or assistance of a second network node in the sensing task. The information related to the UE's perception task includes at least one of the following: Information identifying the control nodes for the perception task; Information about the receiving node of the perception report; Sensing area information; Perceive pattern information; and Information related to the reporting of perception reports.

7. The method according to claim 1, further comprising: A first network node sends a first configuration message to the UE, wherein the first configuration message is used to update the perception task configuration to the UE, and the first configuration message includes at least one of the following: Identify and perceive information for the task; Perceive information about the type of service; Information related to sensing devices; Information about the receiving node of the perception report; Information from the sensing area; Information used to control the execution status of the UE's sensing tasks.

8. The method according to claim 7, wherein, When the sensing device is a UE, the information related to the sensing device includes at least one of the following: Information about the identification and sensing devices; Information on the sensing capabilities of sensing devices; Perceive pattern information; The results of perception are reported; and Information related to the reporting of perception reports.

9. The method according to claim 1, further comprising: The first network node receives a second request message from the second network node. The second request message includes a second sensing task transfer request and / or information about the UE moving out of the sensing area. The second sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node. A second response message is sent from the first network node to the second network node in response to the second request message. The second response message includes information indicating whether the first network node accepts the second perception task transfer request.

10. The method according to claim 1, further comprising: The first network node receives a fourth request message from the fifth network node. The fourth request message includes a third sensing task transfer request and / or information about the UE moving out of the sensing area. The third sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node. The information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the sensing area of ​​the first network node. The first network node sends a fourth response message to the fifth network node in response to the fourth request message. The fourth response message includes information indicating whether the first network node accepts the third perception task transfer request.

11. The method according to claim 9 or 10, wherein, Each of the second and fourth request messages also includes at least one of the following: UE identifier or list of UE identifiers; Information identifying the sensing tasks performed by the UE; Request the reason for the task transfer; Information about the sensing area of ​​the second network node; and Information on the perception capabilities of the second network node.

12. The method according to claim 9 or 10, wherein, Each of the second and fourth response messages also includes at least one of the following: UE identifier or list of UE identifiers; Information identifying the sensing tasks performed by the UE; Information related to the updating of the perceived area; Information used to control the execution status of the UE's sensing tasks.

13. The method according to claim 1, further comprising: When the first network node determines that the UE has moved out of the first network node's sensing area, the first network node sends a fifth request message to the fifth network node. The fifth request message includes a fourth sensing task transfer request and / or information about the UE moving out of the sensing area. The fourth sensing task transfer request is used to request that the UE's sensing task be transferred to the second network node, and the information about the UE moving out of the sensing area is used to indicate that the UE has moved out of the first network node's sensing area. The first network node receives a fifth response message from the fifth network node in response to the fifth request message, wherein the fifth response message includes information indicating whether the second network node accepts the fourth perception task transfer request.

14. The method according to claim 13, wherein, The fifth request message also includes at least one of the following: UE identifier or list of UE identifiers; Information identifying the sensing tasks performed by the UE; Finally, information about the cell that detects the sensing signal between the UE and the cell is obtained. Information about the sensing area of ​​the first network node; Request the reason for the task transfer.

15. The method according to claim 13, wherein, The fifth response message also includes at least one of the following: UE identifier or list of UE identifiers; Information identifying the sensing tasks performed by the UE; Information identifying the base station or cell currently accessed by the UE; Information about the sensing area of ​​the second network node; Information suggesting adjustments to the sensing area of ​​the first network node.

16. A method performed by a second network node, comprising: The second network node receives a first request message related to handover from the first network node. The first request message includes a first sensing task transfer request and sensing task configuration information associated with the first network node for reference. The first sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node. A first response message is sent from the second network node to the first network node in response to the first request message. The first response message includes information indicating whether the second network node accepts the first sensing task transfer request and information indicating whether the second network node accepts the sensing task configuration information.

17. A method performed by a user equipment (UE), comprising: The UE receives a first configuration message from the second network node from the first network node; as well as The UE sends a message to the second network node in response to the first configuration message. The first configuration message is included in the first response message sent by the second network node to the first network node. The first response message is the message in which the second network node responds to the first request message sent by the first network node. The first request message includes a first sensing task transfer request and sensing task configuration information associated with the first network node for reference. The first sensing task transfer request is used to request the transfer of the UE's sensing task to the second network node. The first response message includes information indicating whether the second network node accepts the first sensing task transfer request, and information indicating whether the second network node accepts the sensing task configuration information.

18. A network node, comprising: A transceiver is used to send and receive signals; as well as A processor, coupled to the transceiver, is configured to perform the method as described in any one of claims 1 to 16.

19. A user equipment, comprising: A transceiver is used to send and receive signals; as well as A processor, coupled to the transceiver, is configured to perform the method as described in claim 17.

20. A computer-readable storage medium for storing instructions, wherein, When the instruction is executed by at least one processor, it causes the at least one processor to perform the method as described in any one of claims 1 to 17.

Images