Communication method, communication device, communication system, and program product

By using the first SF to send the sensing context to the second SF in the integrated sensing and communication system, seamless reselection of sensing services is achieved, which solves the flexibility problem of sensing function discovery and reselection in the prior art and improves the adaptability and efficiency of the system.

WO2026232603A1PCT designated stage Publication Date: 2026-11-12BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094100
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In integrated sensing and communication systems, existing technologies struggle to achieve flexibility and efficiency in the discovery and reselection of sensing functions, especially when the sensing object or task changes, making it impossible to quickly and uninterruptedly select the appropriate sensing entity.

Method used

When the reselection conditions are met, the first sensing functional entity (SF) determines and sends the sensing context of the sensing service to the second SF, so that the second SF can provide the sensing service in its place, thereby achieving seamless reselection of the sensing service.

Benefits of technology

This enables flexible reselection of SF (Sensing Service) without interruption, improving the system's adaptability and efficiency and ensuring the continuity of sensing tasks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025094100_12112026_PF_FP_ABST
    Figure CN2025094100_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, and a program product. The method comprises: if a condition for reselecting an SF is met when a sensing service is provided, determining a reselected second SF; and sending a sensing context of the sensing service to the second SF, so that the second SF provides the sensing service on the basis of the sensing context. Embodiments of the present disclosure implement SF reselection without interrupting the sensing service.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods, communication equipment, communication systems and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, terminal, network device, communication system, storage medium, and program product. Background Technology

[0002] Integrated Sensing and Communication (ISAC) involves simultaneously utilizing radio frequency (RF) signals to achieve sensing and communication functions. This integration can improve spectral efficiency, reduce latency, and enhance reliability in a variety of application scenarios. Summary of the Invention

[0003] How to discover and (re)select sensing functions is a key issue in sensing research.

[0004] This disclosure provides communication methods, communication devices, communication systems, storage media, and program products.

[0005] According to a first aspect of the embodiments of this disclosure, a communication method is provided, executed by a first SF, the method comprising:

[0006] When providing perception services, if the conditions for reselecting the SF are met, determine the second SF to be reselected;

[0007] The perception context of the perception service is sent to the second SF so that the second SF provides the perception service based on the perception context.

[0008] According to a second aspect of the embodiments of this disclosure, a communication method is provided, executed by a second SF, the method comprising:

[0009] Receive the perception context of the perception service sent by the first SF;

[0010] Provide perception services based on the perception context.

[0011] According to a third aspect of the embodiments of this disclosure, a communication method is proposed, comprising:

[0012] The first SF meets the conditions for reselecting the SF when providing perception services, and the second SF to be reselected is determined;

[0013] The first SF sends the perception context of the perception service to the second SF;

[0014] If the perception context is successfully transmitted, the second SF provides perception services based on the perception context.

[0015] According to a fourth aspect of the embodiments of this disclosure, a communication device is provided for performing the communication method described in any one of the first and second aspects.

[0016] According to a fifth aspect of the embodiments of this disclosure, a communication system is provided, including at least one of a first SF and a second SF;

[0017] Wherein, the first SF is configured to implement the communication method described in the first aspect, and the second SF is configured to implement the communication method described in the second aspect.

[0018] According to a sixth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform the communication method as described in the first or second aspect.

[0019] According to a seventh aspect of the present disclosure, a program product is provided, comprising at least one of a program and instructions, wherein when the program or instructions are executed by a communication device, the steps of the communication method described in the first or second aspect are implemented.

[0020] The communication method, terminal, network device, communication equipment, communication system, storage medium, and program product provided in this disclosure embodiment, wherein if the first SF meets the condition for reselecting the SF when providing the sensing service, the first SF determines the second SF to be reselected and sends the sensing context of the sensing service to the second SF, so that the second SF replaces the second SF to provide the sensing service according to the sensing context, thereby realizing the reselection of the SF without interruption of the sensing service. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0022] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0023] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

[0024] Figure 3A is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

[0025] Figure 3B is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

[0026] Figure 4 is an interactive schematic diagram of a communication method according to another embodiment of the present disclosure;

[0027] Figure 5A is a schematic diagram of the structure of the first SF proposed in the embodiment of this disclosure;

[0028] Figure 5B is a schematic diagram of the structure of the second SF proposed in the embodiment of this disclosure;

[0029] Figure 6A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure;

[0030] Figure 6B is a schematic diagram of the structure of a chip according to an embodiment of the present disclosure. Detailed Implementation

[0031] This disclosure provides a communication method, a gateway, a first object, a first network element, a communication device, a communication system, a storage medium, and a program product.

[0032] In a first aspect, embodiments of this disclosure propose a communication method executed by a first sensing function (SF), the method comprising:

[0033] When providing perception services, if the conditions for reselecting the SF are met, determine the second SF to be reselected;

[0034] The perception context of the perception service is sent to the second SF so that the second SF provides the perception service based on the perception context.

[0035] In the above embodiments, if the first SF meets the condition for reselecting an SF while providing sensing services, the first SF determines the second SF to be reselected and sends the sensing context of the sensing service to the second SF, so that the second SF can provide sensing services in place of the second SF according to the sensing context, thus realizing the reselection of SFs without interruption of sensing services. If the second SF is providing sensing services, the first SF stops providing sensing services.

[0036] In conjunction with some embodiments of the first aspect, some embodiments further include:

[0037] Receive a first indication, which indicates whether the perception context has been successfully transmitted;

[0038] If the first indication is used to indicate that the perception context transmission is successful, a first message is sent to the perception entity or the first network element, the first message being used to notify that the SF has been reselected;

[0039] The first network element is at least one of the following: Access and Mobility Management Function (AMF), Network Exposure Function (NEF), Gateway Mobile Location Center (GMLC), and Session Management Function (SMF).

[0040] In the above embodiments, the first SF receives a first instruction from the second SF. If the sensing context has been successfully transmitted to the second SF, the source sensing function may send messages to the sensing entity and other network functions (NFs) to notify the SF of the reselection. The first network element in this application can be at least one of AMF, NEF, GMLC and SMF, that is, it supports notifying different types of network elements of the SF of the reselection.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the conditions for reselecting the SF include at least one of the following:

[0042] The first SF detects that it is unable to provide sensing services for at least one of the sensing objects, the environment, or the sensing task;

[0043] A second message is received from the first network element. The second message includes a second indication, which is used to indicate the reselection of the SF.

[0044] In the above embodiments, two conditions for reselecting the SF are provided. One is that the first SF detects that it cannot provide sensing services for at least one of the sensing object, environment, or sensing task. The other is that it receives a second message sent by another network element (the first network element). The first network element can be at least one of AMF, NEF, GMLC, and SMF. The second message includes a second indication, which is used to indicate the reselection of the SF. This embodiment increases the diversity of the conditions for reselecting the SF.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first SF detects that it is unable to provide sensing services for at least one of the sensing object, the environment, or the sensing task, including at least one of the following:

[0046] The sensing object is not located in the service area of ​​the first SF;

[0047] Perceive the mobility of objects;

[0048] Perceive the mobility of entities;

[0049] AMF relocation;

[0050] SMF relocation;

[0051] The first SF is overloaded or congested;

[0052] Receive sensing messages from the sensing entity;

[0053] Perceived entity reselection;

[0054] There is no available sensing entity for the sensing task.

[0055] The perception request is updated, but the updated perception request is not supported;

[0056] It does not meet the perceptual requirements of the perceptual task.

[0057] In the above embodiments, multiple methods are provided for the first SF to self-check whether it is unable to provide sensing services for at least one of the sensing object, environment, or sensing task.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the second message further includes at least one of the information of the second SF and the updated perception request information;

[0059] The information of the second SF includes at least one of the following:

[0060] The identifier of the second SF; and

[0061] The first requirement for the second SF is related to at least one of the SF's capabilities, service area, load, and priority information;

[0062] The updated perception request information includes at least one of the requested service quality, service area, and perception time.

[0063] In the above embodiments, the second message sent by the first network element to the first SF not only instructs the first SF to reselect an SF, but also includes information about the second SF. If the information of the second SF includes the identifier of the second SF, then the first SF directly determines the second SF. If the information of the second SF includes a first requirement for the second SF, then the first SF selects the SF that meets the first requirement from multiple candidate SFs as the second SF according to the first requirement. The second message may also include updated perception request information, which includes at least one of the requested quality of service, service area, and perception time.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the second SF is determined based on at least one of the second message, the perception function profile of at least one other SF, and the SF selection criteria;

[0065] Wherein, the at least one other SF includes the second SF.

[0066] In the above embodiments, the second SF can be determined based on at least one of the second message sent by the first network element, the sensing function configuration file of at least one other SF, and the SF selection criteria. By providing multiple ways to determine the second SF, the second SF can be determined more flexibly.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the awareness function configuration files of other SFs are configured locally on the first SF, stored locally, or obtained from the Network Repository Function (NRF).

[0068] In the above embodiments, the perception function configuration files of other SFs can be pre-configured locally on the first SF, or they can be stored locally. For example, they can be stored after being previously obtained from NRF, or they can be obtained from NRF currently.

[0069] In conjunction with some embodiments of the first aspect, in some embodiments, the SF selection criterion is related to at least one of the following;

[0070] Perceive the type of entity;

[0071] The requested service quality, service area, sensing time, and sensing object are at least one of the following:

[0072] Access type;

[0073] Types of wireless access technologies;

[0074] Configuration information of the Radio Access Network (RAN);

[0075] The service area of ​​SF, the shape of the service area supported by SF, the capabilities of SF, the refresh rate of the maximum perceived result of SF, the load of SF, and the location of SF are at least one of the following:

[0076] Single-event report or multiple-event report instructions;

[0077] Duration of the incident report;

[0078] Network slice information;

[0079] The user plane connection status between at least one of the sensing transmitter and sensing receiver and the SF.

[0080] In the above embodiments, the SF selection criteria are related to many factors, which can improve the flexibility of SF selection.

[0081] In conjunction with some embodiments of the first aspect, in some embodiments where the sensing function profile of the other SF is obtained from the NRF, the method further includes:

[0082] Send a first request to the NRF, the first request being used to request the perception function configuration file of the other SF;

[0083] Receive a first response sent by the NRF, the first response including the sensing function profile of the other SF.

[0084] In the above embodiment, the first SF sends to the NRF.

[0085] In conjunction with some embodiments of the first aspect, in some embodiments, the first request includes at least one of a sensing function indication, an identifier of the other SF, and a second request for the second SF;

[0086] The second requirement relates to at least one of the following: the service area of ​​the SF, the shape of the service area supported by the SF, the capabilities of the SF, and the location of the SF.

[0087] The first response also includes at least one of the following: the validity period of the discovery result, the sensing function load, and the sensing function priority information.

[0088] In conjunction with some embodiments of the first aspect, in some embodiments, the awareness function profile includes at least one of the following: the type of SF, its identifier, its fully qualified domain name, its Internet Protocol address, and a list of service instances.

[0089] Each service instance in the service instance list includes at least one of the following: service name, awareness function service instance identifier, and endpoint address.

[0090] In conjunction with some embodiments of the first aspect, in some embodiments, the perception context includes an AMF identifier; a notification target address; a notification-related identifier; a task identifier; perception service quality; a perception request type; periodic event information; regional event information; motion event information; tracking event information; monitoring event information; an event report message; an event report status; perception target information; target location information; a target cell identifier; perception entity information; perception entity role; perception mode; perception method; perception capability of the perception entity; planned perception time; indoor perception indication; outdoor perception indication; line-of-sight path measurement indication; non-line-of-sight path measurement indication; a cumulative event report timer; at least one of the following: the maximum number of perception reports for the user plane and previous perception messages.

[0091] In conjunction with some embodiments of the first aspect, in some embodiments, the first message further includes at least one of a task identifier, an identifier of the first SF, an address of the first SF, an identifier of the second SF, and an address of the second SF.

[0092] Secondly, embodiments of this disclosure propose a communication method, executed by a second SF, the method comprising:

[0093] Receive the perception context of the perception service sent by the first SF;

[0094] Provide perception services based on the perception context.

[0095] In the above embodiments, the second SF can receive the perception context of the perception service sent by the first SF; if the perception context is successfully transmitted, the second SF provides the perception service according to the perception context, thereby replacing the first SF in providing the perception service according to the perception context, realizing the reselection of the SF without interruption of the perception service. When the second SF provides the perception service, the first SF stops providing the perception service.

[0096] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0097] A first indication is sent to the first SF, the first indication being used to indicate whether the perception context has been successfully transmitted.

[0098] In conjunction with some embodiments of the second aspect, in some embodiments, the conditions for reselecting the SF include at least one of the following:

[0099] The first SF detects that it is unable to provide sensing services for at least one of the sensing objects, the environment, or the sensing task;

[0100] A second message is received from the first network element. The second message includes a second indication, which is used to indicate the reselection of the SF.

[0101] In conjunction with some embodiments of the second aspect, in some embodiments, the first SF detects that it is unable to provide sensing services for at least one of the sensing object, the environment, or the sensing task, including at least one of the following:

[0102] The sensing object is not located in the service area of ​​the first SF;

[0103] Perceive the mobility of objects;

[0104] Perceive the mobility of entities;

[0105] AMF relocation;

[0106] SMF relocation;

[0107] The first SF is overloaded or congested;

[0108] Receive sensing messages from the sensing entity;

[0109] Perceived entity reselection;

[0110] There is no available sensing entity for the sensing task.

[0111] The perception request is updated, but the updated perception request is not supported;

[0112] It does not meet the perceptual requirements of the perceptual task.

[0113] In conjunction with some embodiments of the second aspect, in some embodiments, the second message further includes at least one of the information of the second SF and the updated perception request information;

[0114] The information of the second SF includes at least one of the following:

[0115] The identifier of the second SF; and

[0116] The first requirement for the second SF is related to at least one of the SF's capabilities, service area, load, and priority information;

[0117] The updated perception request information includes at least one of the requested service quality, service area, and perception time.

[0118] In some embodiments of the second aspect, the second SF is determined based on at least one of the second message, the perception function profile of at least one other SF, and the SF selection criteria.

[0119] Wherein, the at least one other SF includes the second SF.

[0120] In conjunction with some embodiments of the second aspect, in some embodiments, the perception function configuration files of the other SF are configured locally in the first SF, stored locally, or obtained from the NRF.

[0121] In conjunction with some embodiments of the second aspect, in some embodiments, the SF selection criterion is related to at least one of the following;

[0122] Perceive the type of entity;

[0123] The requested service quality, service area, sensing time, and sensing object are at least one of the following:

[0124] Access type;

[0125] Types of wireless access technologies;

[0126] Configuration information of the Radio Access Network (RAN);

[0127] The service area of ​​the SF, the shape of the service area supported by the SF, the capabilities of the SF, the refresh rate of the maximum sensing result of the SF, and the location of the SF;

[0128] Single-event report or multiple-event report instructions;

[0129] Duration of the incident report;

[0130] Network slice information;

[0131] The user plane connection status between at least one of the sensing transmitter and sensing receiver and the SF.

[0132] In conjunction with some embodiments of the second aspect, in some embodiments, when the sensing function profile of the other SF is obtained from the NRF, the method further includes:

[0133] Send a first request to the NRF, the first request being used to request the perception function configuration file of the other SF;

[0134] Receive a first response sent by the NRF, the first response including the sensing function profile of the other SF.

[0135] In conjunction with some embodiments of the second aspect, in some embodiments, the first request includes at least one of a sensing function indication, an identifier of the other SF, and a second request for the second SF;

[0136] The second requirement relates to at least one of the following: the service area of ​​the SF, the shape of the service area supported by the SF, the capabilities of the SF, and the location of the SF.

[0137] The first response also includes at least one of the following: the validity period of the discovery result, the sensing function load, and the sensing function priority information.

[0138] In conjunction with some embodiments of the second aspect, in some embodiments, the perception function configuration file includes at least one of the following: the type of SF, its identifier, its fully qualified domain name, its Internet Protocol address, and a list of service instances.

[0139] Each service instance in the service instance list includes at least one of the following: service name, awareness function service instance identifier, and endpoint address.

[0140] In conjunction with some embodiments of the second aspect, in some embodiments, the perception context includes: AMF identifier; notification target address; notification related identifier; task identifier; perception service quality; perception request type; periodic event information; regional event information; motion event information; tracking event information; monitoring event information; event report message; event report status; perception target information; target location information; target cell identifier; perception entity information; perception entity role; perception mode; perception method; perception capability of the perception entity; planned perception time; indoor perception indication; outdoor perception indication; line-of-sight path measurement indication; non-line-of-sight path measurement indication; cumulative event report timer; maximum number of user-plane perception reports; and at least one of previous perception messages.

[0141] Thirdly, embodiments of this disclosure provide a communication method, including:

[0142] The first SF meets the conditions for reselecting the SF when providing perception services, and the second SF to be reselected is determined;

[0143] The first SF sends the perception context of the perception service to the second SF;

[0144] If the perception context is successfully transmitted, the second SF provides perception services based on the perception context.

[0145] According to a fourth aspect of the embodiments of this disclosure, a communication device is provided for performing the communication method described in any one of the first or second aspects.

[0146] According to a fifth aspect of the present disclosure, a communication system is provided, including a first SF and a second SF, wherein the first SF is configured to implement the communication method described in the first aspect, and the second SF is configured to implement the communication method described in the second aspect.

[0147] According to a sixth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform the communication method as described in the first or second aspect.

[0148] According to a seventh aspect of the present disclosure, a program product is provided, comprising at least one of a program and instructions, wherein when the program or instructions are executed by a communication device, the steps of the communication method described in the first or second aspect are implemented.

[0149] It is understood that the aforementioned communication devices, communication systems, storage media, program products, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0150] This disclosure provides embodiments of communication methods, terminals, network devices, communication equipment, communication systems, storage media, and program products. In some embodiments, the terms "communication method" and "information processing method," "communication method," etc., may be used interchangeably.

[0151] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0152] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0153] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0154] In the embodiments of this disclosure, "multiple" refers to two or more.

[0155] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0156] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0157] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0158] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0159] In some embodiments, “including A,” “including A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0160] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0161] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0162] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0163] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0164] In some embodiments, "network" can be interpreted as devices included in the network (e.g., access network devices, core network devices, etc.).

[0165] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0166] In some embodiments, the terms "terminal", "terminal device", "user equipment", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0167] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0168] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0169] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0170] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0171] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0172] Figure 1 is a schematic diagram of the architecture of a communication system according to some embodiments. As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.

[0173] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0174] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0175] Access network equipment includes, for example, nodes or devices that connect terminals to a wireless network. Access network equipment may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation evolved Node B (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul equipment, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0176] In some embodiments, the core network device may be a single device including a first SF, a second SF, and a first network element, or it may be multiple devices or a group of devices, each including all or part of the first SF, second SF, and first network element. A network element may be virtual or physical.

[0177] In some embodiments, the first network element may be at least one of AMF, NEF, GMLC and SMF.

[0178] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0179] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0180] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0181] The rapid development of wireless communication technology and the ever-growing demand for high-quality data transmission have driven the research and development of advanced communication systems. One particularly promising technology is the integration of sensing and communication, which is expected to bring transformative changes to multiple industries, including automotive, healthcare, unmanned aerial vehicles (UAVs), and smart cities.

[0182] ISAC involves simultaneously utilizing RF signals to achieve sensing and communication functions. This integration improves spectrum efficiency, reduces latency, and enhances reliability across a variety of applications. Integrated sensing and communication is particularly important for mobile operators, user equipment manufacturers, automotive manufacturers, and users because it can significantly improve the overall user experience, enhance network efficiency, and create new business opportunities.

[0183] The selection and reselection of sensing entities (SFs) is currently a key issue in sensing research. This key issue aims to investigate how to perform the discovery and (re)selection of sensing entities (ESs) and SFs. Specifically, research needs to address the following aspects:

[0184] Which (or entities) shall perform the discovery and (re)selection of SF;

[0185] What information and / or criteria were considered during the discovery and (re)selection of SFs?

[0186] The discovery and (re)selection process of SF.

[0187] Please refer to Figure 2, which exemplarily illustrates an interaction diagram of the communication method according to an embodiment of this disclosure. As shown in the figure, it includes:

[0188] Step S2101: When the first SF provides sensing services, it meets the conditions for reselecting the SF, and the second SF to be reselected is determined.

[0189] In some embodiments, the first SF provides sensing services to sensing entities and sensing objects through deep integration with the core network architecture and flexible deployment.

[0190] It should be understood that a sensing entity can be a transmitter and a receiver that perform sensing. A sensing object is the target object of sensing. The relationship between a sensing entity and a sensing object is as follows: the sensing transmitter sends a signal to the sensing object, and the sensing receiver receives the signal reflected by the sensing object, thereby realizing the sensing of the sensing object.

[0191] In some embodiments, the first SF serves as a logical functional element of the 5G core network (5GC), supporting both base station awareness and terminal awareness. This architecture achieves synergy between awareness and communication capabilities by reusing core network protocols and interfaces, such as interacting with the AMF to obtain user equipment status, or controlling the awareness data transmission path through the SMF.

[0192] In some embodiments, the first SF can be deployed independently of 5GC, exposing its capabilities to external sensing entities through service-oriented interfaces (such as NEF). This mode is suitable for scenarios with flexible and scalable sensing requirements, such as interfacing with third-party sensing devices or application systems to achieve cross-domain data fusion.

[0193] In some embodiments, the way the first SF provides sensing services to the sensing entity may include:

[0194] The first SF provides a standardized API to sensing entities (such as the application server AF) through NEF, supporting sensing task distribution, data subscription, and result callback. For example, the AF can request drone trajectory data for a specific area through NEF, and the first SF schedules base station resources to complete the sensing and return the results; or

[0195] First, the SF (Signal Array Controller) collaborates with the RAN (Radio Array Controller) to dynamically configure base station parameters (such as beam direction and time slot allocation) based on the needs of the sensed entities, thereby achieving joint optimization of communication and sensing resources. For example, in a vehicle-to-everything (V2X) scenario, the SF can schedule base stations to perform high-frequency sensing of road areas while ensuring vehicle communication bandwidth.

[0196] In some embodiments, the way the first SF provides sensing services to the sensing object may include:

[0197] SF (Sensitive Ground Transmission) integrates sensing functions at the base station side (such as a 5G-A integrated sensing base station), utilizing electromagnetic wave reflection signals to measure distance, speed, and angle of sensed objects (such as drones and vehicles). For example, in low-altitude security scenarios, the first SF can monitor the drone's position in real time and trigger an alarm; or

[0198] By combining RTK differential positioning technology, the first SF can improve the accuracy of base station parameters, thereby achieving high-precision positioning and behavior recognition of the sensed object. For example, in smart cities, the first SF can accurately track the trajectory of logistics drones and optimize delivery routes.

[0199] In some embodiments, the conditions for reselecting the SF include at least one of the following:

[0200] The first SF detects that it is unable to provide sensing services for at least one of the sensing objects, the environment, or the sensing task;

[0201] A second message is received from the first network element. The second message includes a second indication, which is used to indicate the reselection of the SF.

[0202] When providing sensing services, the first SF can perform self-checks periodically or non-periodically to check whether it can provide sensing services for at least one of the sensing object, environment, or sensing task. When it is determined that it cannot provide sensing services for at least one of the sensing object, environment, or sensing task, the conditions for reselecting the SF are met.

[0203] If the first SF receives the second message sent by the first network element, and the second indication in the second message is used to indicate the reselection of the SF, then the first SF determines that the condition for reselecting the SF is met.

[0204] In some embodiments, terms such as "reselection," "change," "handover," "replacement," and "substitution" can be used interchangeably, and these descriptions all refer to the corresponding actions that the device will take under certain objective circumstances.

[0205] In some embodiments, the first SF detects that it is unable to provide sensing services for at least one of the sensed object, the environment, or the sensed task, including at least one of the following:

[0206] The sensing object is not located in the service area of ​​the first SF; for example, in a sensing task that is being monitored, tracked, periodically or triggered.

[0207] Perceive the mobility of objects;

[0208] The mobility of a sensed entity; for example, at least one of the transmitter and receiver of a user equipment;

[0209] AMF relocation;

[0210] SMF relocation;

[0211] The first SF is overloaded or congested;

[0212] Receive sensing messages from sensing entities, such as sensing event reports and monitoring report messages;

[0213] Perceived entity reselection;

[0214] There is no available sensing entity for the sensing task, for example, due to the mobility of the user equipment transmitter or receiver, there is no line-of-sight (LOS) path between the sensing target or object and the sensing entity.

[0215] The perception request is updated, but the updated perception request is not supported;

[0216] It does not meet the perceptual requirements of the perceptual task.

[0217] In some embodiments, the second message sent by the first network element also includes at least one of the information of the second SF and the updated perception request information;

[0218] The information of the second SF includes at least one of the following:

[0219] The identifier of the second SF; and

[0220] The first requirement for the second SF is related to at least one of the SF's capabilities, service area, load, and priority information;

[0221] The updated perception request information includes at least one of the requested service quality, service area, and perception time.

[0222] In some embodiments, the first network element may be at least one of AMF, NEF, GMLC and SMF.

[0223] In some embodiments, the first SF determines the second SF based on at least one of the following: a second message, a perception function profile of at least one other SF, and SF selection criteria. For example, the first SF may directly determine the second SF based on the identifier of the second SF included in the second message; or, for example, the first SF may determine the second SF from at least one other SF based on a first requirement for the second SF in the second message, combined with the perception function profile of at least one other SF; or, for example, the first SF may determine the second SF from at least one other SF based on the perception function profile of at least one other SF, and so on.

[0224] In some embodiments, the awareness feature profile includes at least one of the SF type, identifier, fully qualified domain name, Internet Protocol address, and service instance list;

[0225] Each service instance in the service instance list includes at least one of the following: service name, awareness function service instance identifier, and endpoint address.

[0226] In some embodiments, the SF selection criteria are related to at least one of the following:

[0227] The type of the perceived entity (e.g., terminal, base station, etc.);

[0228] The quality of service requested, such as: SF accuracy (e.g., accuracy of positioning estimation, accuracy of velocity estimation, confidence level, sensing resolution, probability of missed detection, probability of false alarm, etc.), response time / sensing service latency: that is, the time required from issuing a sensing request to receiving a sensing result, refresh rate: that is, the update frequency of the sensing result, etc.

[0229] Service area, which is the specific area or range that needs to be sensed;

[0230] Perceived time refers to the time period or point in time during which the perceived service needs to be executed.

[0231] Perceived object;

[0232] Access type, such as 3GPP access or non-3GPP access;

[0233] The type of radio access technology, such as 6G, 5G NR, eLTE, or any RAT type specified for NR satellite access, and / or the serving access network (AN) node (i.e., gNB or NG-eNB) of the target user equipment (UE);

[0234] Configuration information of the Radio Access Network (RAN);

[0235] SF's service area;

[0236] The shape of the service area supported by SF;

[0237] SF's capabilities include: SF user plane positioning capability: that is, the ability of the sensing function to locate on the user plane; SF artificial intelligence (AI) sensing capability: that is, the ability of the sensing function to use artificial intelligence technology to sense, the ability to support sensing when it involves Mobile Base Station Relay (MBSR), the ability to support sensing when it involves Mobile gNB with Wireless Access Backhauling (MWAB), etc.

[0238] The refresh rate of SF's maximum perceived results;

[0239] SF's load, such as the number of perception requests processed and remaining processing capacity;

[0240] The location of SF, such as geographic location, network location, etc.;

[0241] Single-event or multi-event reporting indication, that is, indicating whether the sensing function reports a single event or multiple events.

[0242] The duration of the incident report, i.e. the length of time during which the incident needs to be reported;

[0243] Network slice information;

[0244] The user plane connection status between at least one of the sensing transmitter and sensing receiver and the SF.

[0245] In some embodiments, the awareness feature profiles of other SFs are configured locally on the first SF, stored locally, or obtained from the Network Repository Feature (NRF).

[0246] In some embodiments, where the perception capability profile of the other SF is obtained from the NRF, the method further includes:

[0247] Send a first request to the NRF, the first request being used to request the perception function configuration file of the other SF;

[0248] Receive a first response sent by the NRF, the first response including the sensing function profile of the other SF.

[0249] In some embodiments, the first request may be an Nnrf_NFDiscovery_Request request, which includes at least one of a sensing capability indication, an identifier of a second SF (which may be multiple), and a second requirement for the second SF (e.g., a requested sensing capability, a requested sensing service area).

[0250] In some embodiments, the second requirement relates to at least one of the SF's service area, the shape of the service area supported by the SF, the capabilities of the SF, and the location of the SF.

[0251] In some embodiments, the first response may be an Nnrf_NFDiscovery_Request response, which includes at least one of the following: the validity period of the discovery result, the sensing function load, and the sensing function priority information.

[0252] Step S2102: The first SF sends the perception context of the perception service to the second SF.

[0253] In some embodiments, the first SF sends a perception context transmission request to the second SF, the request containing the perception context.

[0254] In some embodiments, the first SF sends an Nsf_SensingContextTransfer request to the second SF, the request containing the sensing context.

[0255] In some embodiments, the perception context includes the following information:

[0256] AMF identifier: Used to uniquely identify access and mobility management functions;

[0257] Notification Target Address: The target address to which the perception results or event reports should be sent;

[0258] Notification Correlation ID: An identifier used to associate or track a specific notification;

[0259] Task ID: A unique identifier that identifies a sensing task;

[0260] Sensing QoS: Describes the quality parameters required for sensing services, such as accuracy and latency;

[0261] Sensing request type: Indicates the specific type of sensing request, such as a single sensing request, a periodic or triggered sensing request, a tracking request, etc.

[0262] Periodic event info: Information related to periodically perceived events, such as the cycle in which the events occur;

[0263] Area event info: Information related to events occurring within a specific area;

[0264] Motion event info: Event information related to the direction and trend of movement of a target or perceived entity;

[0265] Tracking event info: Event information related to tracking a specific target;

[0266] Monitoring event info: Event information related to monitoring specific conditions or states;

[0267] Event report message: A message containing detailed information about the perceived event;

[0268] Event reporting status: Indicates the current status of the event report, such as sent, pending, etc.

[0269] Sensing target information: Information about the perceived target, such as target type, identifier, etc.

[0270] Target location information: The location information of the perceived target;

[0271] Target cell ID: The cell ID of the cell where the target is located;

[0272] Sensing entity info: Information about the entities involved in the sensing process (such as sensors, UEs, etc.);

[0273] The role of sensing entities: the role that sensing entities play in the sensing process, such as transmitters and receivers;

[0274] Sensing mode: describes the specific mode of sensing operation, such as single-station sensing, dual-station sensing, etc.

[0275] Sensing method: The specific method or technique used to perform sensing;

[0276] Sensing capabilities of sensing entities: The sensing capabilities possessed by sensing entities, such as measurement range and accuracy;

[0277] Scheduled sensing time: The time scheduled for performing sensing operations;

[0278] Indoor sensing indication: Indicates whether the sensing operation is performed in an indoor environment;

[0279] Outdoor sensing indication: Indicates whether the sensing operation is being performed in an outdoor environment;

[0280] Line-of-sight (LOS) measurement indication: Indicates whether a line-of-sight (LOS) measurement exists during sensing operations;

[0281] Non-line-of-sight (NLOS) measurement indication: Indicates whether the sensing operation only involves non-line-of-sight (NLOS) measurements;

[0282] Cumulative event report timer or the maximum number of sensing reports over the user plane or both: a timer or threshold used to control the frequency or number of event reports;

[0283] Previous sensing messages: such as previous periodic or triggering sensing event report messages, used to provide context or history.

[0284] In some embodiments, the second SF receives the sensing context.

[0285] In some embodiments, the second SF sends a first indication to the first SF. The first indication is used to indicate whether the perception context has been successfully transmitted.

[0286] In some embodiments, the second SF sends a perception context transmission response to the first SF, the response including a first indication.

[0287] In some embodiments, the second SF sends an Nsf_SensingContextTransfer response to the first SF, the response including a first indication.

[0288] In some embodiments, the first SF receives a first indication, and if the first indication indicates that the sensing context transmission is successful, sends a first message to the sensing entity (such as a user equipment or a radio access network node) or a first network element, the first message being used to notify the SF that a reselection has been made.

[0289] In some embodiments, the first message further includes at least one of a task identifier, an identifier of the first SF, an address of the first SF, an identifier of the second SF, and an address of the second SF.

[0290] In some embodiments, when the first SF notifies a first message, the first message may contain the following information:

[0291] First indication: A clear indicator to inform the perceived entity SF that it has been reselected;

[0292] Identifier of the sensing task: The identifier of the sensing task being relocated to ensure that the sensing entity can associate the notification with the correct sensing task.

[0293] The ID or address of the second SF: The identifier or address of the second SF to which the sensing context has been transferred, enabling the sensing entity to communicate with the new SF for subsequent sensing operations.

[0294] In some embodiments, the first SF can send the first message directly to the sensing entity, or it can be sent through the AMF. The first message can be a dedicated notification message, i.e., a message specifically designed to inform the sensing entity that the SF has been reselected to ensure clear and unambiguous communication, or it can be carried in a sensing acknowledgment message or sensing response message, such as an event report acknowledgment message or a monitoring acknowledgment message.

[0295] In some embodiments, for the first network element, the first SF may send a notification message that may or may not instruct the first SF to reselect an SF.

[0296] Step S2103: If the perception context is successfully transmitted, the second SF provides perception services based on the perception context.

[0297] In some embodiments, if the perception context transmission fails, the second SF will not provide perception services or will not replace the first SF in providing perception services; the first SF will still provide perception services.

[0298] In some embodiments, if the second SF provides sensing services, the first SF stops providing sensing services.

[0299] In some embodiments, the second SF performs a perception task (e.g., calculates the perception result, opens the perception result) based on the perception entity information of the perception context.

[0300] The second SF can take over sensing tasks based on the sensing context, ensuring the continuity of sensing services and avoiding service interruptions or data loss due to handover.

[0301] For example, in the vehicle-to-everything (V2X) scenario, a vehicle may need to switch to different SFs (such as the sensing functions of different base stations) while driving. The second SF after switching provides services such as vehicle positioning and obstacle detection.

[0302] For example, when a drone is performing a mission, it may fly over the coverage area of ​​multiple SFs. The second SF after switching provides services such as drone location tracking and environmental awareness.

[0303] For example, in a factory environment, a mobile robot may switch between different SFs (Self-Service Providers), with the second SF providing services such as equipment status monitoring and path planning.

[0304] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0305] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" can be used interchangeably. For example, a codebook can be a collection of one or more codewords / precoding matrices.

[0306] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0307] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0308] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0309] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0310] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.

[0311] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0312] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0313] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0314] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0315] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0316] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", and "panel" can be used interchangeably.

[0317] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0318] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, processing, autonomous implementation, etc. Protocols include, for example, at least one of 3GPP protocols, Wi-Fi protocols, and audio and / or video protocols.

[0319] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0320] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0321] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0322] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0323] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0324] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101, S2102, and S2103. For example, step S2101, step S2102, and step S2103 may be implemented as independent embodiments, but are not limited thereto. Steps S2101+S2102 may be implemented as independent embodiments, but are not limited thereto. Steps S2102+S2103 may be implemented as independent embodiments, but are not limited thereto. Steps S2101+S2103 may be implemented as independent embodiments, but are not limited thereto.

[0325] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0326] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0327] In some embodiments, step S2103 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0328] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0329] Figure 3A is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the present disclosure relates to a communication method, which includes:

[0330] Step S3101: When providing perception services, if the conditions for reselecting the SF are met, determine the second SF to be reselected.

[0331] In some embodiments, the conditions for reselecting the SF include at least one of the following:

[0332] The first SF detects that it is unable to provide sensing services for at least one of the sensing objects, the environment, or the sensing task;

[0333] A second message is received from the first network element. The second message includes a second indication, which is used to indicate the reselection of the SF.

[0334] In some embodiments, the second message sent by the first network element also includes at least one of the information of the second SF and the updated perception request information;

[0335] The information of the second SF includes at least one of the following:

[0336] The identifier of the second SF; and

[0337] The first requirement for the second SF is related to at least one of the SF's capabilities, service area, load, and priority information;

[0338] The updated perception request information includes at least one of the requested service quality, service area, and perception time.

[0339] In some embodiments, the awareness feature profile includes at least one of the SF type, identifier, fully qualified domain name, Internet Protocol address, and service instance list;

[0340] Each service instance in the service instance list includes at least one of the following: service name, awareness function service instance identifier, and endpoint address.

[0341] In some embodiments, the awareness feature profiles of other SFs are configured locally on the first SF, stored locally, or obtained from the Network Repository Feature (NRF).

[0342] In some embodiments, where the perception capability profile of the other SF is obtained from the NRF, the method further includes:

[0343] Send a first request to the NRF, the first request being used to request the perception function configuration file of the other SF;

[0344] Receive a first response sent by the NRF, the first response including the sensing function profile of the other SF.

[0345] In some embodiments, the first request may be an Nnrf_NFDiscovery_Request request, which includes at least one of a sensing capability indication, an identifier of a second SF (which may be multiple), and a second requirement for the second SF (e.g., a requested sensing capability, a requested sensing service area).

[0346] In some embodiments, the first response may be an Nnrf_NFDiscovery_Request response, which includes at least one of the following: the validity period of the discovery result, the sensing function load, and the sensing function priority information.

[0347] The optional implementation of step S3101 can be found in the optional implementation of step S2101 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0348] Step S3102: Send the perception context of the perception service to the second SF.

[0349] In some embodiments, the first SF sends a perception context transmission request to the second SF, the request containing the perception context.

[0350] In some embodiments, the first SF sends an Nsf_SensingContextTransfer request to the second SF, the request containing the sensing context.

[0351] In some embodiments, the second SF receives the sensing context.

[0352] In some embodiments, the second SF sends a first indication to the first SF. The first indication is used to indicate whether the perception context has been successfully transmitted.

[0353] In some embodiments, the second SF sends a perception context transmission response to the first SF, the response including a first indication.

[0354] In some embodiments, the second SF sends an Nsf_SensingContextTransfer response to the first SF, the response including a first indication.

[0355] The optional implementation of step S3102 can be found in the optional implementation of step S2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0356] Step S3103: Receive the first instruction sent by the second SF.

[0357] In some embodiments, the first SF receives a first indication, and if the first indication indicates that the sensing context transmission is successful, sends a first message to the sensing entity (such as a user equipment or a radio access network node) or a first network element, the first message being used to notify the SF that a reselection has been made.

[0358] In some embodiments, the first message further includes at least one of a task identifier, an identifier of the first SF, an address of the first SF, an identifier of the second SF, and an address of the second SF.

[0359] In some embodiments, when the first SF notifies a first message, the first message may contain the following information:

[0360] First indication: A clear indicator to inform the perceived entity SF that it has been reselected;

[0361] Identifier of the sensing task: The identifier of the sensing task being relocated to ensure that the sensing entity can associate the notification with the correct sensing task.

[0362] The ID or address of the second SF: The identifier or address of the second SF to which the sensing context has been transferred, enabling the sensing entity to communicate with the new SF for subsequent sensing operations.

[0363] In some embodiments, the first SF can send the first message directly to the sensing entity, or it can be sent through the AMF. The first message can be a dedicated notification message, i.e., a message specifically designed to inform the sensing entity that the SF has been reselected to ensure clear and unambiguous communication, or it can be carried in a sensing acknowledgment message or sensing response message, such as an event report acknowledgment message or a monitoring acknowledgment message.

[0364] In some embodiments, for the first network element, the first SF may send a notification message that may or may not instruct the first SF to reselect an SF.

[0365] The optional implementation of step S3103 can be found in the optional implementation of step S2103 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0366] In some embodiments, refer to the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, such as the embodiment shown in FIG2, which will not be repeated here.

[0367] Figure 3B is a schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the present disclosure relates to a communication method, which includes:

[0368] Step S3201: Receive the perception context of the perception service sent by the first SF.

[0369] The optional implementation of step S3201 can be found in the optional implementation of step S2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0370] Step S3202: Send a first instruction to the first SF.

[0371] The optional implementations of step S3202 can be found in the optional implementations of steps S2102 and S2103 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0372] Step S3203: If the perception context is successfully transmitted, provide perception services based on the perception context.

[0373] The optional implementations of step S3203 can be found in the optional implementations of steps S2102 and S2103 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0374] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0375] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, the optional implementation methods in each embodiment can be arbitrarily combined. Furthermore, the embodiments can be arbitrarily combined; for example, some or all of the steps in the embodiment shown in FIG. 2 can be arbitrarily combined with some or all of the steps in the embodiment shown in FIG. 3a, and some or all of the steps in the embodiment shown in FIG. 2 can be arbitrarily combined with some or all of the steps in the embodiment shown in FIG. 3b.

[0376] Please refer to Figure 4, which exemplarily illustrates a communication method according to another embodiment of this disclosure, as shown in the figure, including:

[0377] Step S4101: The first SF is determined to meet the conditions for reselecting the SF.

[0378] In some embodiments, the conditions for reselecting the SF include at least one of the following:

[0379] The first SF detects that it is unable to provide sensing services for at least one of the sensing objects, the environment, or the sensing task;

[0380] A second message is received from the first network element. The second message includes a second indication, which is used to indicate the reselection of the SF.

[0381] In cases where other network functions (NFs) instruct the source sensing function (SF) to reselect a sensing function (SF), when the aforementioned network function (NF) detects that a sensing function (SF) needs to be reselected, the network function should send a message to the source network function (NF) that includes a sensing function (SF) reselection instruction, target sensing function (SF) information, and updated sensing request information.

[0382] Target awareness (SF) information includes:

[0383] Sensing Function ID (SF ID), or

[0384] Requests for target perception capabilities (SF) (e.g., requested perception capability, requested perception service area, requested perception load, requested priority information).

[0385] The relevant perception request information includes:

[0386] Requested Quality of Service (QoS)

[0387] Requested sensory area information,

[0388] The requested perceived time information.

[0389] In other cases, the sensing function (SF) detects that the sensing function (SF) needs to be reselected.

[0390] The optional implementation of step S4101 can be found in step S2101 of Figure 2, the optional implementation of step S3101 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0391] Step S4102: The first SF sends a first request to the NRF.

[0392] The first SF requests configuration files from other SFs from the NRF in order to select the second SF. The first SF may include information about other SFs in the first request.

[0393] If the message contains the identifier (SF ID) of the second SF, the first SF will request the configuration file of the specified target SF.

[0394] If the message contains requirements for the second SF (e.g., requested awareness capabilities, requested awareness service areas, etc.), the source SF will request a configuration file of the awareness (SF) that can satisfy those requests.

[0395] In addition, the message will include a sensing function indication to show the NRF that the type of the second SF requested is a sensing function (SF).

[0396] The optional implementation of step S4102 can be found in step S2101 of Figure 2, the optional implementation of step S3101 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0397] Step S4103: NRF sends a first response to the first SF.

[0398] The NRF provides the first SF with a set of SF profiles, the validity period of the discovery results, and SF load and priority information. The SF profile includes: Network Function Type (i.e., SF), SF ID, Fully Qualified Domain Name (FQDN) or Internet Protocol address (IP address) of the SF, a list of service instances, where each service instance has a service name, an SF service instance ID, and optional endpoint addresses(es).

[0399] The NRF sends an Nnrf_NFDiscovery_Request response to the first SF (containing the sensing function configuration file, the validity period of the discovery results, the sensing function load, and the sensing function priority information).

[0400] Note: If the awareness function configuration file has been configured locally in the first SF, or has been previously received and stored from the Network Repository Function (NRF), steps S4102 and S4103 can be skipped.

[0401] The optional implementation of step S4103 can be found in step S2101 of Figure 2, the optional implementation of step S3101 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0402] Step S4104: The first SF determines the second SF to be reselected.

[0403] The first SF determines the second SF based on at least one of the second message, the perception function profile of at least one other SF, and the SF selection criteria.

[0404] The optional implementation of step S4104 can be found in step S2101 of Figure 2, the optional implementation of step S3101 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0405] Step S4105: The first SF sends the perception context of the perception service to the second SF.

[0406] After selecting the second SF, the first SF will initiate a service operation to the selected second SF to transmit the awareness context.

[0407] The perception context includes: AMF identifier; notification target address; notification related identifier; task identifier; perception service quality; perception request type; periodic event information; regional event information; motion event information; tracking event information; monitoring event information; event report message; event report status; perception target information; target location information; target cell identifier; perception entity information; perception entity role; perception mode; perception method; perception capability of the perception entity; planned perception time; indoor perception indication; outdoor perception indication; line-of-sight measurement indication; non-line-of-sight measurement indication; cumulative event report timer; maximum number of perception reports on the user plane; and at least one of the following: previous perception messages.

[0408] The optional implementation of step S4105 can be found in step S2102 of Figure 2, the optional implementation of step S3102 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0409] Step S4106: The second SF sends a first instruction to the first SF.

[0410] The first indication is used to indicate whether the perception context has been successfully transmitted.

[0411] The optional implementation of step S4106 can be found in step S2102 of Figure 2, the optional implementation of step S3102 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0412] Step S4107: The first SF sends a first message to the sensing entity or the first network element.

[0413] The first message is used to notify SF that it has been reselected.

[0414] The first message also includes at least one of the following: task identifier, identifier of the first SF, address of the first SF, identifier of the second SF, and address of the second SF.

[0415] In some embodiments, when the first SF notifies a first message, the first message may contain the following information:

[0416] First indication: A clear indicator to inform the perceived entity SF that it has been reselected;

[0417] Identifier of the sensing task: The identifier of the sensing task being relocated to ensure that the sensing entity can associate the notification with the correct sensing task.

[0418] The identifier or address of the second SF: The identifier or address of the second SF to which the sensing context has been transferred, enabling the sensing entity to communicate with the new SF for subsequent sensing operations.

[0419] In some embodiments, the first SF can send the first message directly to the sensing entity, or it can be sent through the AMF. The first message can be a dedicated notification message, i.e., a message specifically designed to inform the sensing entity that the SF has been reselected to ensure clear and unambiguous communication, or it can be carried in a sensing acknowledgment message or sensing response message, such as an event report acknowledgment message or a monitoring acknowledgment message.

[0420] In some embodiments, for the first network element, the first SF may send a notification message that may or may not instruct the first SF to reselect an SF.

[0421] Optional implementations of step S4107 can be found in step S2103 of Figure 2, optional implementations of step S3103 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0422] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes a unit or module for implementing the steps performed by the sensing transmitter in any of the above methods. Furthermore, another apparatus is proposed that includes a unit or module for implementing the steps performed by the sensing receiver in any of the above methods.

[0423] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0424] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0425] Figure 5A is a schematic diagram of the structure of the first SF according to an embodiment of this disclosure. The first SF 5100 is used to perform any of the above methods. In some embodiments, as shown in Figure 5A, the first SF 5100 may include: a transceiver module 5101 and a processing module 5102. In some embodiments, the transceiver module 5101 is used to send the perception context of the perception service to the second SF. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., step S2102, but not limited thereto) performed by the first SF in any of the above methods, which will not be described in detail here. Optionally, the processing module is used to perform at least one of the other steps performed by the first SF in any of the above methods, which will not be described in detail here.

[0426] Figure 5B is a schematic diagram of the structure of the second SF proposed in an embodiment of this disclosure. The second SF 5200 is used to perform any of the above methods. In some embodiments, as shown in Figure 5B, the second SF 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is used to receive the perception context of the perception service. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the second SF in any of the above methods, which will not be described in detail here. Optionally, the processing module is used to perform at least one of the other steps performed by the second SF in any of the above methods, which will not be described in detail here.

[0427] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0428] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0429] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0430] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0431] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0432] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (e.g., step S2102, but not limited thereto) in the above-described method, such as sending and / or receiving, and the processor 6101 performs at least one of other steps (e.g., step S2102, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0433] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.

[0434] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0435] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.

[0436] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0437] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.

[0438] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., step S2102, but not limited thereto). For example, the interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method means that the interface circuit 6202 performs data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., step S2101, but not limited thereto).

[0439] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0440] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0441] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0442] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method characterized by comprising: The method is performed by a first sensing function (SF), and the method comprises: satisfying a condition of reselecting a SF when providing a sensing service; determining a second SF for reselection; 2. The method of claim 1, wherein, sending a sensing context of the sensing service to the second SF, so that the second SF provides a sensing service according to the sensing context. Further comprising: receiving a first indication indicating whether the sensing context is successfully transmitted; in a case where the first indication indicates that the sensing context is successfully transmitted, sending a first message to a sensing entity or a first network element, the first message being used to notify that the SF has been reselected; 3. The method according to claim 1 or 2, characterized in that, wherein the first network element is at least one of an access and mobility management function (AMF), a network exposure function (NEF), a gateway mobile location center (GMLC), and a session management function (SMF). The condition of reselecting the SF comprises at least one of: the first SF detecting that the first SF cannot provide a sensing service for at least one of a sensing object, an environment, or a sensing task; 4. The method of claim 3, wherein, receiving a second message sent by a first network element, the second message comprising a second indication indicating that the SF is reselected. The first SF detecting that the first SF cannot provide a sensing service for at least one of a sensing object, an environment, or a sensing task comprises at least one of: the sensing object not being located in a service area of the first SF; mobility of the sensing object; mobility of the sensing entity; relocation of the AMF; relocation of the SMF; overload or congestion of the first SF; receiving a sensing message from the sensing entity; reselection of the sensing entity; no available sensing entity for the sensing task; an updated sensing request is received, and the updated sensing request is not supported; 5. The method according to claim 3 or 4, characterized in that, a sensing requirement of the sensing task is not met. The second message further comprises at least one of information of the second SF and updated sensing request information; wherein the information of the second SF comprises at least one of: an identity of the second SF; and a first requirement for the second SF, the first requirement being related to at least one of a capability of the SF, a service area of the SF, a load of the SF, and priority information of the SF; 6. The method according to any one of claims 3-5, characterized in that, the updated sensing request information comprising at least one of a requested quality of service, a service area, and a sensing time. The second SF is determined according to at least one of the second message, a sensing function profile of at least one other SF, and a SF selection criterion; 7. The method of claim 6, wherein, wherein the at least one other SF comprises the second SF.

8. The method according to claim 6 or 7, characterized in that, The sensing function profile of the other SF is configured, stored locally at the first SF, or obtained from a network repository function (NRF). The SF selection criterion is related to at least one of: a type of the sensing entity; at least one of a requested quality of service, a service area, a sensing time, and a sensing object; an access type; a type of a radio access technology; configuration information of a radio access network (RAN); at least one of a service area of the SF, a shape of a service area supported by the SF, a capability of the SF, a refresh rate of a maximum sensing result of the SF, a load of the SF, and a location of the SF; a single-event reporting or a multi-event reporting indication; a duration of event reporting; network slice information; At least one of the perception transmitter and the perception receiver, and a user plane connection state between SFs.

9. The method of claim 7, wherein, In a case where the perception function profile of the other SF is acquired from the NRF, the method further includes: sending, to the NRF, a first request for obtaining the perception function profile of the other SF; receiving a first response sent by the NRF, the first response including the perception function profile of the other SF.

10. The method of claim 9, wherein, The first request includes at least one of a perception function indication, an identity of the other SF, and a second requirement for the second SF; The second requirement is related to at least one of a service area of the SF, a shape of a service area supported by the SF, a capability of the SF, and a location of the SF; The first response further includes at least one of a validity period of a discovery result, a perception function load, and perception function priority information.

11. The method according to any one of claims 6-10, characterized in that, The perception function profile includes at least one of a type of the SF, an identity, a fully qualified domain name, an Internet Protocol address, and a service instance list; Each service instance in the service instance list includes at least one of a service name, a perception function service instance identity, and an endpoint address.

12. The method according to any one of claims 1 to 11, characterized in that, The perception context includes an AMF identity; a notification target address; a notification-related identity; a task identity; a perception service quality; a perception request type; periodic event information; area event information; motion event information; tracking event information; monitoring event information; an event report message; an event report state; perception target information; Target location information; target cell identity; perception entity information; perception entity role; perception mode; perception method; perception capability of the perception entity; planned perception time; Indication of indoor perception; indication of outdoor perception; indication of direct path measurement; indication of non-direct path measurement; cumulative event report timer; At least one of a maximum number of perception reports of the user plane and a previous perception message.

13. The method of claims 2-12, wherein, The first message further includes at least one of a task identity, an identity of the first SF, an address of the first SF, an identity of the second SF, and an address of the second SF.

14. The method of claim 13, wherein, The sending of the first message to the perception entity includes: The sending of the first message to the perception entity by the AMF.

15. A method of communication, comprising: The method is performed by the second SF and includes: receiving a perception context of a perception service sent by a first SF; providing the perception service according to the perception context.

16. The method of claim 15, wherein, Further including: sending a first indication to the first SF, the first indication indicating whether the perception context is successfully transmitted.

17. The method according to claim 15 or 16, characterized in that, The condition of the reselection SF includes at least one of: The first SF detects that it is unable to provide a perception service for at least one of a perception object, an environment, or a perception task; receiving a second message sent by a first network element, the second message including a second indication indicating a reselection SF.

18. The method of claim 17, wherein, The first SF detects that it is unable to provide a perception service for at least one of a perceived object, an environment, or a perception task, including at least one of: The perceived object is not located in a service area of the first SF; mobility of the perceived object; mobility of the perception entity; relocation of the AMF; relocation of the SMF; The first SF is overloaded or congested; A perception message is received from a perception entity; The perception entity is reselected; No available perception entity for the perception task; The perception request is updated and the updated perception request is not supported; The perception requirement of the perception task is not met.

19. The method of claim 17, wherein, The second message further includes at least one of information of the second SF and updated perception request information; The information of the second SF includes at least one of: An identifier of the second SF; and A first requirement for the second SF, the first requirement being related to at least one of a capability of the SF, a service area, a load, and priority information of the SF; The updated perception request information includes at least one of a requested quality of service, a service area, and a perception time.

20. The method of any one of claims 17-19, wherein, The second SF is determined according to at least one of the second message, a perception function profile of at least one other SF, and a SF selection criterion; The at least one other SF includes the second SF.

21. The method of claim 20, wherein, The perception function profile of the other SF is configured, stored locally, or obtained from a NRF locally in the first SF.

22. The method of claim 20 or 21, wherein, The SF selection criterion is related to at least one of: A type of the perception entity; At least one of a requested quality of service, a service area, a perception time, and a perception object; An access type; A type of a radio access technology; Configuration information of a radio access network (RAN); At least one of a service area of the SF, a shape of a service area supported by the SF, a capability of the SF, a refresh rate of a maximum perception result of the SF, and a location of the SF; A single-event report or a multi-event report indication; A duration of the event report; Network slice information; At least one of a perception transmitter and a perception receiver, and a user plane connection state between the SFs.

23. The method of claim 20, wherein, In a case where the perception function profile of the other SF is obtained from the NRF, the method further includes: Sending a first request to the NRF, the first request being used to request to obtain the perception function profile of the other SF; Receiving a first response sent by the NRF, the first response including the perception function profile of the other SF.

24. The method of claim 23, wherein, The first request includes at least one of a perception function indication, an identifier of the other SF, and a second requirement for the second SF; The second requirement is related to at least one of a service area of the SF, a shape of a service area supported by the SF, a capability of the SF, and a location of the SF; The first response further includes at least one of a validity period of a discovery result, a perception function load, and perception function priority information.

25. The method of any one of claims 20-24, wherein, The perception function profile includes at least one of a type, an identifier, a fully qualified domain name, an Internet Protocol address, and a service instance list of the SF; Each service instance in the service instance list includes at least one of a service name, a perception function service instance identifier, and an endpoint address.

26. The method of any of claims 15-25, wherein, The perception context includes an AMF identity; a notification target address; a notification-related identity; a task identity; a perception quality of service; a perception request type; periodic event information; area event information; motion event information; tracking event information; monitoring event information; an event report message; an event report status; and perception target information. Target location information; target cell identity; perception entity information; perception entity role; perception mode; perception method; and perception capability of the perception entity. Indication of indoor perception; indication of outdoor perception; indication of line-of-sight path measurement; indication of non-line-of-sight path measurement; and accumulated event report timer. At least one of a maximum number of perception reports of a user plane and a previous perception message.

27. A communication method, comprising: a first SF determining a second SF for reselection when the first SF meets a condition for reselection of the second SF while providing a perception service; the first SF sending a perception context of the perception service to the second SF; the second SF providing the perception service according to the perception context when the perception context transmission is successful.

28. A communications device, characterized by The communication device is configured to implement the communication method of any one of claims 1-14, 15-26.

29. A communication system, characterized by including at least one of the first SF and the second SF; wherein the first SF is configured to implement the communication method of any one of claims 1-14, and the second SF is configured to implement the communication method of any one of claims 15-26.

30. A storage medium, the storage medium storing instructions, wherein, The instructions, when executed on the communication device, cause the communication device to perform the communication method of any one of claims 1-26.

31. A program product comprising at least one of a program, instructions, characterized in that, The program, instructions, at least one of which, when executed on the communication device, implement the steps of the communication method of claims 1-26.