Communication method and apparatus, and computer-readable storage medium

Abstract

The present application provides a communication method and apparatus, and a computer-readable storage medium. The method comprises: receiving a first sensing service request for requesting a first sensing service; on the basis of the first sensing service request, respectively sending a sensing control request to sensing signal receiving nodes of a plurality of sensing node groups, wherein the sensing control request is used for requesting sensing data corresponding to the first sensing service, each sensing node group comprises a sensing signal sending node and a sensing signal receiving node, and at least one of each pair of the sensing signal sending node and the sensing signal receiving node of different sensing node groups is different; and respectively acquiring, from the sensing signal receiving nodes of the plurality of sensing node groups, the sensing data corresponding to the first sensing service. According to the embodiments of the present application, the corresponding sensing data can be acquired from a plurality of different sensing node groups, so that the accuracy of a sensing result and the sensing reliability can be ensured.

Description

Communication method, device and computer-readable storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 30, 2023, with application number 202311637523.2 and application name “Communication Method, Device and Computer-readable Storage Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present invention relates to the field of communication perception technology, and in particular to a communication method, device, and computer-readable storage medium. Background Art

[0003] With the evolution of mobile communication technology, wireless communications are using higher and higher frequency bands, such as millimeter wave bands. When access network equipment and terminal devices use millimeter wave bands for wireless communications, they will possess radar-like perception capabilities, addressing sensing needs in a wide range of scenarios. Examples include automated and assisted driving, connected vehicles, intelligent transportation, 3D map reconstruction, smart industry, drone monitoring and management, intelligent interaction, and environmental monitoring.

[0004] Among them, scenarios such as automatic / assisted driving and 3D map reconstruction have high requirements for the accuracy of perception results. Therefore, how to ensure the accuracy of perception results is a concern of the industry. Summary of the Invention

[0005] The embodiments of the present application disclose a communication method, an apparatus, and a computer-readable storage medium, which can ensure the accuracy of perception results and the reliability of perception.

[0006] In a first aspect, a communication method is disclosed, which can be applied to a perception function network element (SF), or to a module (e.g., a processor) in the perception function network element, or to a logic module or software that can implement all or part of the functions of the perception function network element. The following description takes application to a perception function network element as an example, and the communication method may include: receiving a first perception service request, where the first perception service request is used to request a first perception service; based on the first perception service request, sending a perception control request to perception signal receiving nodes in a plurality of perception node groups, respectively, where the perception control request is used to request perception data corresponding to the first perception service, where the perception node groups include perception signal sending nodes and perception signal receiving nodes, where the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item; and obtaining perception data corresponding to the first perception service from the perception signal receiving nodes in the plurality of perception node groups.

[0007] In an embodiment of the present application, SF can send perception control requests to the perception signal receiving nodes in multiple perception node groups based on the first perception service request, that is, perform the first perception service in a redundant perception manner. In this way, perception data can be obtained from different perception node groups respectively, so that multiple perception data corresponding to the first perception service can be obtained. Furthermore, based on the multiple perception data corresponding to the first perception service, SF can detect whether the perception data is incorrect, so as to determine whether the perception result obtained based on the corresponding perception data is accurate. In some cases, SF can even compare the perception data corresponding to each perception node group, exclude the erroneous perception data, and then obtain the perception result based on the correct / accurate perception data, which can ensure the accuracy of the perception result. In addition, SF can also obtain the perception result by integrating multiple accurate perception data, which can reduce errors and improve the accuracy of the perception result.

[0008] Furthermore, SF adopts redundant perception to ensure the security and reliability of perception.

[0009] In combination with the first aspect, in a possible implementation, the first perception service request includes a redundant perception indication, and the sending of perception control requests to the perception signal receiving nodes in multiple perception node groups based on the first perception service request includes: sending perception control requests to the perception signal receiving nodes in multiple perception node groups based on the redundant perception indication.

[0010] In an embodiment of the present application, redundant sensing can be proactively triggered by including a redundant sensing indication in a sensing request. That is, when the sensing request does not include a redundant sensing indication, redundant sensing will not be used for sensing. Only when the sensing request includes a redundant sensing indication will redundant sensing be used for sensing. This avoids requiring redundant sensing for every sensing request, thus conserving sensing resources. Furthermore, in this manner, the sensing requester can choose to include a redundant sensing indication based on actual needs, providing greater flexibility.

[0011] In combination with the first aspect, in a possible implementation, the method further includes: assigning a perception task identification ID to each perception control request, the perception task ID corresponding to the first perception service; obtaining the perception data corresponding to the first perception service from the perception signal receiving nodes in the multiple perception node groups respectively includes: obtaining the perception data corresponding to the first perception service and the perception task ID corresponding to each perception data from the perception signal receiving nodes in the multiple perception node groups respectively; based on the perception task ID corresponding to each perception data, determining that each perception data corresponds to the first perception service.

[0012] In this embodiment of the present application, a corresponding perception task ID can be assigned to each perception control request corresponding to the first perception service request / first perception service, and a corresponding relationship between the perception task ID and the first perception service request / first perception service is maintained. In this way, the SF can subsequently determine the perception data corresponding to the first perception service based on this corresponding relationship to obtain a perception result.

[0013] In combination with the first aspect, in a possible implementation, before sending perception control requests to the perception signal receiving nodes in multiple perception node groups respectively, the method also includes: sending a first perception authorization request to the data management network element based on the first perception service request, and the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service; receiving a first authorization response from the data management network element, and the first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

[0014] In the embodiment of the present application, the data management network element can perform an authorization check for redundant sensing. Only when the authorization is passed can redundant sensing be used for sensing, thereby saving sensing resources. In addition, the data management network element can also be used to specifically restrict the authorization of redundant sensing.

[0015] In combination with the first aspect, in a possible implementation, the first perception authorization request includes one or more of the following: a perception service type, a perception area, an application function identifier, and a redundant perception indication.

[0016] With reference to the first aspect, in a possible implementation, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0017] In the embodiment of the present application, the first authorization response may carry first authorization indication information, which is used to indicate that the redundant perception authorization is passed. Of course, in the case of unauthorized passing, the data management network element may also return a corresponding authorization response, which may carry indication information indicating that the authorization is not passed, or indication information indicating that perception is performed in a non-redundant perception manner.

[0018] For example, the first authorization indication information may be a redundancy perception indication

[0019] In combination with the first aspect, in a possible implementation, the first perception service request is based on sending perception control requests to the perception signal receiving nodes in multiple perception node groups respectively, including: when the first perception service request satisfies the first redundant perception configuration information, sending perception control requests to the perception signal receiving nodes in multiple perception node groups respectively.

[0020] In this embodiment of the present application, the SF can perform a redundant sensing authorization check. When the SF determines that the first sensing service request satisfies the first redundant sensing configuration information, it can be determined that the redundant sensing authorization is passed. Moreover, only when the authorization is passed can redundant sensing be used for sensing, thereby saving sensing resources.

[0021] In combination with the first aspect, in a possible implementation, the first redundant perception configuration information includes one or more of the following: the perception service type allowing redundant perception, the perception area allowing redundant perception, the application function identifier allowing redundant perception, and the time allowing redundant perception.

[0022] In an embodiment of the present application, the conditions for redundant perception can be flexibly configured. For example, only one of the perception service type that allows redundant perception, the perception area that allows redundant perception, the application function identifier that allows redundant perception, and the time that allows redundant perception can be configured, or multiple of them can be configured.

[0023] Furthermore, the perception service request satisfying the first redundant perception configuration information may include multiple situations. One situation is that the information carried in the perception service request satisfies one of the configured items. Another situation is that the information carried in the perception service request satisfies multiple configured items. Yet another situation is that the information carried in the perception service request satisfies multiple configured items, and the multiple items are bound to each other. For details, please refer to the relevant description in the following embodiments.

[0024] In combination with the first aspect, in a possible implementation, the method further includes: receiving a first parameter configuration request from the network capability exposure function network element, the first parameter configuration request including second redundant perception configuration information, and the first redundant perception configuration information including the second redundant perception configuration information.

[0025] In the embodiment of the present application, when the SF performs redundancy sensing authorization checks, the SF can also receive parameter configuration requests from other network elements. This allows for dynamic adjustment of the redundancy sensing configuration information, providing greater flexibility. For example, specific configurations can be made for certain sensing scenarios to enable redundancy sensing in those scenarios.

[0026] In combination with the first aspect, in a possible implementation manner, the first perception service request further includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0027] In combination with the first aspect, in a possible implementation, the first perception service request comes from a terminal device, a network capability exposure function network element, or an application function network element.

[0028] In combination with the first aspect, in a possible implementation, the method further includes: determining a first perception result based on the perception data corresponding to the multiple first perception services.

[0029] In the embodiment of the present application, SF can obtain a perception result based on multiple perception data corresponding to the first perception service, and can ensure the accuracy of the perception result.

[0030] In combination with the first aspect, in a possible implementation, determining the first perception result based on the perception data corresponding to the multiple first perception services includes: obtaining target perception data after excluding the deviation perception data in the perception data corresponding to the multiple first perception services based on the perception data corresponding to the multiple first perception services; and obtaining the first perception result based on the target perception data.

[0031] In an embodiment of the present application, SF can exclude perception data with large deviations based on multiple perception data corresponding to the first perception service, and then obtain a perception result based on the remaining perception data (target perception data), thereby ensuring the accuracy of the perception result.

[0032] The second aspect discloses a communication method, which can be applied to a data management network element (UDM / UDR), or to a module (e.g., a processor) in a data management network element, or to a logic module or software that can implement all or part of the functions of the data management network element. The following description is given using the application to a data management network element as an example. The communication method may include: receiving a first perception authorization request, the first perception authorization request being used to request an authorization check for obtaining multiple perception data corresponding to a first perception service; when the first perception authorization request satisfies the first redundant perception configuration information, sending a first authorization response, the first authorization response being used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

[0033] In an embodiment of the present application, the data management network element can receive a redundancy perception authorization request sent by an authorization requester (such as an NEF, SF, etc.), and can perform a redundancy perception authorization check based on the redundancy perception authorization request. Furthermore, if the redundancy perception authorization is approved, the data management network element can return an authorization response to the corresponding authorization requester, informing the authorization requester of the approval. It should be understood that the redundancy perception authorization can limit the application scenarios of redundancy perception, avoid the abuse of redundancy perception, and thus save perception resources.

[0034] In combination with the second aspect, in a possible implementation, the first redundant perception configuration information includes one or more of the following: the perception service type allowing redundant perception, the perception area allowing redundant perception, the application function identifier allowing redundant perception, and the time allowing redundant perception.

[0035] In combination with the second aspect, in a possible implementation, the first perception authorization request includes one or more of the following: a perception service type, a perception area, an application function identifier, and a redundant perception indication.

[0036] In combination with the second aspect, in a possible implementation, the method further includes: when the first perception authorization request includes a redundant perception indication, performing an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception authorization request and the first redundant perception configuration information.

[0037] In an embodiment of the present application, the data management network element may perform a redundant perception authorization check only when the first perception authorization request carries a redundant perception indication, thereby saving processing resources.

[0038] In combination with the second aspect, in a possible implementation, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0039] In combination with the second aspect, in a possible implementation, the method further includes: receiving a first parameter configuration request from a network capability exposure function network element, the first parameter configuration request including second redundant perception configuration information, and the first redundant perception configuration information including the second redundant perception configuration information.

[0040] In combination with the second aspect, in a possible implementation, the first perception authorization request comes from a network capability exposure function network element or a perception function network element.

[0041] It should be noted that the technical solution of the second aspect of this application may correspond to the solution of the first aspect, and the relevant beneficial effects can refer to the beneficial effects of the first aspect.

[0042] The third aspect discloses a communication method, which can be applied to a network capability exposure function network element, or to a module (for example, a processor) in the network capability exposure function network element, or to a logic module or software that can realize all or part of the network capability exposure function network element functions. The following description is given by taking the application to the network capability exposure function network element as an example. The communication method may include: receiving a second perception service request, the second perception service request is used to request a first perception service; based on the second perception service request, sending a first perception authorization request to a data management network element, the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service; receiving a first authorization response from the data management network element, the first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized; based on the first authorization response, sending a first perception service request to the perception function network element, the first perception service request is used to request the first perception service.

[0043] In an embodiment of the present application, the network capability exposure function network element can receive a first perception service request from other network elements (such as AF), and then perform a redundant perception authorization check through the data management network element. If the authorization is passed, the corresponding perception service request can be sent to the perception function network element so that the perception function network element can execute the first perception service using redundant perception.

[0044] In combination with the third aspect, in a possible implementation, the second perception service request includes one or more of the following: perception service type, perception service requirement, perception area, application function identifier, and redundant perception indication.

[0045] In combination with the third aspect, in a possible implementation, sending a first perception authorization request to the data management network element based on the second perception service request includes: when the second perception service request includes a redundant perception indication, sending a first perception authorization request to the data management network element based on the second perception service request.

[0046] In an embodiment of the present application, the network capability exposure function network element may send a first perception authorization request to the data management network element only when the second perception service request includes a redundant perception indication. In this way, the number of times the first perception authorization request is sent can be reduced, thereby saving transmission resources, and correspondingly saving related processing resources.

[0047] In combination with the third aspect, in a possible implementation, the first perception authorization request includes one or more of the following: a perception service type, a perception area, an application function identifier, and a redundant perception indication.

[0048] In combination with the third aspect, in a possible implementation, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0049] In combination with the third aspect, in a possible implementation, the first perception service request includes one or more of the following: perception service type, perception service requirement, perception area, application function identifier, and redundant perception indication.

[0050] In combination with the third aspect, in a possible implementation, the method further includes: receiving a second parameter configuration request from an application function network element, the second parameter configuration request including third redundant perception configuration information; sending a first parameter configuration request based on the second parameter configuration request, the first parameter configuration request including second redundant perception configuration information, and the second redundant perception configuration information being obtained based on the third redundant perception configuration information.

[0051] In combination with the third aspect, in a possible implementation, sending the first parameter configuration request based on the second parameter configuration request includes: when the application function network element authorization check passes, sending the first parameter configuration request based on the second parameter configuration request.

[0052] In an embodiment of the present application, the network capability exposure function network element may send the first parameter configuration request based on the second parameter configuration request only when the application function network element passes the authorization check, so that unnecessary / erroneous parameter configuration can be avoided.

[0053] In combination with the third aspect, in a possible implementation, the second redundant perception configuration information includes one or more of the following: the perception service type allowing redundant perception, the perception area allowing redundant perception, the application function identifier allowing redundant perception, and the time allowing redundant perception.

[0054] In combination with the third aspect, in a possible implementation, the method also includes: receiving a first perception result from the perception function network element, the first perception result is obtained based on multiple perception data corresponding to the first perception service, the multiple perception data are obtained through multiple perception node groups, the perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending node and the perception signal receiving node in different perception node groups are different in at least one item.

[0055] It should be noted that the technical solution of the third aspect of this application may correspond to the solution of the first aspect, and the relevant beneficial effects can refer to the beneficial effects of the first aspect.

[0056] A fourth aspect discloses a communication method, which can be applied to a network capability exposure function network element, or to a module (for example, a processor) in the network capability exposure function network element, or to a logic module or software that can implement all or part of the network capability exposure function network element functions. The following description is given by taking the application to the network capability exposure function network element as an example. The communication method may include: receiving a second perception service request, the second perception service request being used to request a first perception service, the second perception service request including a redundant perception indication, the redundant perception indication being used to indicate the acquisition of multiple perception data corresponding to the first perception service; and sending a first perception service request to the perception function network element based on the second perception service request, the first perception service request being used to request the first perception service.

[0057] In combination with the fourth aspect, in a possible implementation, the second perception service request further includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0058] In combination with the fourth aspect, in a possible implementation, the first perception service request includes one or more of the following: perception service type, perception service requirement, perception area, application function identifier, and redundant perception indication.

[0059] In combination with the fourth aspect, in a possible implementation, sending a first perception service request to the perception function network element based on the second perception service request includes: sending a second perception authorization request to the data management network element based on the second perception service request, the second perception authorization request being used to request an authorization check for the first perception service; receiving a second authorization response from the data management network element, the second authorization response being used to indicate that the first perception service is authorized; and sending the first perception service request to the perception function network element based on the second authorization response.

[0060] In combination with the fourth aspect, in a possible implementation, the method also includes: receiving a first perception result from a perception function network element, the first perception result is obtained based on multiple perception data corresponding to the first perception service, the multiple perception data are obtained through multiple perception node groups, the perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending node and the perception signal receiving node in different perception node groups are different in at least one item.

[0061] It should be noted that the technical solution of the fourth aspect of this application may correspond to the solution of the first aspect, and the relevant beneficial effects can refer to the beneficial effects of the first aspect.

[0062] The fifth aspect discloses a communication method, which can be applied to a terminal device, an application function network element (AF) or other network elements with perception requirements, and can also be applied to a module (for example, a processor) in a terminal device or an application function network element, and can also be applied to a logic module or software that can realize all or part of the functions of the terminal device or the application function network element. The following description is given using the application to the application function network element as an example. The communication method may include: sending a first perception service request, the first perception service request is used to request a first perception service, the first perception service request includes a redundant perception indication, and the redundant perception indication is used to indicate the acquisition of multiple perception data corresponding to the first perception service.

[0063] In the embodiment of the present application, the AF can carry a redundant sensing indication in the sensing service request to trigger redundant sensing based on actual needs to ensure the accuracy of the sensing result. In addition, this method of triggering redundant sensing by carrying a redundant sensing indication in the sensing request is highly flexible.

[0064] In combination with the fifth aspect, in a possible implementation, the method also includes: receiving a first perception result, the first perception result is obtained based on multiple perception data corresponding to the first perception service, the multiple perception data are obtained through multiple perception node groups, the perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending node and the perception signal receiving node in different perception node groups are different in at least one item.

[0065] In combination with the fifth aspect, in a possible implementation, the method also includes: receiving a second perception result, which is a perception result obtained by executing the first perception service in a non-redundant perception manner; sending the first perception service request includes: sending the first perception service request based on the second perception result.

[0066] In an embodiment of the present application, the AF may trigger redundant sensing based on a sensing result obtained by performing the first sensing service in a non-redundant sensing manner. For example, if the sensing result obtained by performing the first sensing service in a non-redundant sensing manner is not accurate enough, the AF may resend a sensing request and carry a redundant sensing indication therein to trigger redundant sensing.

[0067] In combination with the fifth aspect, in a possible implementation, the first perception service request includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0068] In combination with the fifth aspect, in a possible implementation, before sending the first perception service request, the method also includes: receiving a second perception result, which is a perception result obtained by executing the first perception service in a non-redundant perception manner; sending a second parameter configuration request based on the second perception result, and the second parameter configuration request includes third redundant perception configuration information.

[0069] In an embodiment of the present application, the AF may trigger parameter configuration based on the perception results obtained by executing the first perception service using a non-redundant perception method. For example, if the perception results obtained by executing the first perception service using a non-redundant perception method are not accurate enough, the AF may send a second parameter configuration request to configure third redundant perception configuration information. In this way, when the first perception service or a perception service in a similar scenario is executed again, a redundant perception indication may be triggered, thereby ensuring the accuracy of the perception results.

[0070] In combination with the fifth aspect, in a possible implementation, the third redundant perception configuration information includes one or more of the following: the perception service type allowing redundant perception, the perception area allowing redundant perception, the application function identifier allowing redundant perception, and the time allowing redundant perception.

[0071] In combination with the fifth aspect, in a possible implementation, the sender of the first perception service request is a terminal device or an application function network element.

[0072] A sixth aspect discloses a communication device, which may be a perception function network element or a module (e.g., a processor) in the perception function network element. The communication device includes: a receiving unit for receiving a first perception service request, the first perception service request being used to request a first perception service; a sending unit for sending a perception control request to a plurality of perception signal receiving nodes in a plurality of perception node groups based on the first perception service request, the perception control request being used to request perception data corresponding to the first perception service, the perception node groups including perception signal sending nodes and perception signal receiving nodes, and the perception signal sending nodes and perception signal receiving nodes in different perception node groups differ in at least one item; a processing unit for obtaining the perception data corresponding to the first perception service from the perception signal receiving nodes in the plurality of perception node groups.

[0073] In combination with the sixth aspect, in a possible implementation, the first perception service request includes a redundant perception indication, and the sending unit is specifically used to: send perception control requests to the perception signal receiving nodes in multiple perception node groups respectively based on the redundant perception indication.

[0074] In combination with the sixth aspect, in a possible implementation, the processing unit is further used to: assign a perception task identification ID to each perception control request, where the perception task ID corresponds to the first perception service; obtain the perception data corresponding to the first perception service and the perception task ID corresponding to each perception data from the perception signal receiving nodes in the multiple perception node groups; and determine that each perception data corresponds to the first perception service based on the perception task ID corresponding to each perception data.

[0075] In combination with the sixth aspect, in a possible implementation, before the sending unit sends perception control requests to the perception signal receiving nodes in multiple perception node groups respectively, the sending unit is also used to send a first perception authorization request to the data management network element based on the first perception service request, and the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service; the receiving unit is also used to receive a first authorization response from the data management network element, and the first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

[0076] In combination with the sixth aspect, in a possible implementation, the first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

[0077] In combination with the sixth aspect, in a possible implementation, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0078] In combination with the sixth aspect, in a possible implementation, the sending unit is further used to send perception control requests to the perception signal receiving nodes in multiple perception node groups respectively when the first perception service request satisfies the first redundant perception configuration information.

[0079] In combination with the sixth aspect, in a possible implementation, the first redundant perception configuration information includes one or more of the following: the perception service type allowing redundant perception, the perception area allowing redundant perception, the application function identifier allowing redundant perception, and the time allowing redundant perception.

[0080] In combination with the sixth aspect, in a possible implementation, the receiving unit is also used to receive a first parameter configuration request from the network capability exposure function network element, the first parameter configuration request includes second redundant perception configuration information, and the first redundant perception configuration information includes the second redundant perception configuration information.

[0081] In combination with the sixth aspect, in a possible implementation, the first perception service request further includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0082] In combination with the sixth aspect, in a possible implementation, the first perception service request comes from a terminal device, a network capability exposure function network element, or an application function network element.

[0083] In combination with the sixth aspect, in a possible implementation, the processing unit is further used to determine a first perception result based on the perception data corresponding to the multiple first perception services.

[0084] In combination with the sixth aspect, in a possible implementation, the processing unit is specifically used to: obtain target perception data after excluding the deviation perception data in the perception data corresponding to the multiple first perception services based on the perception data corresponding to the multiple first perception services; and obtain the first perception result based on the target perception data.

[0085] A seventh aspect discloses a communication device, which may be a data management network element or a module (e.g., a processor) in the data management network element. The communication device includes: a receiving unit for receiving a first perception authorization request, the first perception authorization request being used to request an authorization check for obtaining multiple perception data corresponding to a first perception service; and a sending unit for sending a first authorization response when the first perception authorization request satisfies first redundant perception configuration information, the first authorization response being used to indicate that obtaining the multiple perception data corresponding to the first perception service is authorized.

[0086] In combination with the seventh aspect, in a possible implementation, the first redundant perception configuration information includes one or more of the following: the perception service type allowing redundant perception, the perception area allowing redundant perception, the application function identifier allowing redundant perception, and the time allowing redundant perception.

[0087] In combination with the seventh aspect, in a possible implementation, the first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

[0088] In combination with the seventh aspect, in a possible implementation, the communication device also includes: a processing unit, used to perform an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception authorization request and the first redundant perception configuration information when the first perception authorization request includes a redundant perception indication.

[0089] In combination with the seventh aspect, in a possible implementation, the first authorization response includes first authorization indication information, and the first authorization indication information is used to indicate that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0090] In combination with the seventh aspect, in a possible implementation, the receiving unit is also used to receive a first parameter configuration request from a network capability exposure function network element, the first parameter configuration request includes second redundant perception configuration information, and the first redundant perception configuration information includes the second redundant perception configuration information.

[0091] In combination with the seventh aspect, in a possible implementation, the first perception authorization request comes from a network capability exposure function network element or a perception function network element.

[0092] The eighth aspect discloses a communication device, which can be a network capability exposure function network element or a module (for example, a processor) in the network capability exposure function network element. The communication device includes: a receiving unit for receiving a second perception service request, the second perception service request being used to request a first perception service; a sending unit for sending a first perception authorization request to a data management network element based on the second perception service request, the first perception authorization request being used to request an authorization check for obtaining multiple perception data corresponding to the first perception service; the receiving unit is also used to receive a first authorization response from the data management network element, the first authorization response being used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized; the sending unit is also used to send a first perception service request to the perception function network element based on the first authorization response, the first perception service request being used to request the first perception service.

[0093] In combination with the eighth aspect, in a possible implementation, the second perception service request includes one or more of the following: perception service type, perception service requirement, perception area, application function identifier, and redundant perception indication.

[0094] In combination with the eighth aspect, in a possible implementation, the sending unit is specifically used to: when the second perception service request includes a redundant perception indication, send a first perception authorization request to the data management network element based on the second perception service request.

[0095] In combination with the eighth aspect, in a possible implementation, the first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

[0096] In combination with the eighth aspect, in a possible implementation, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0097] In combination with the eighth aspect, in a possible implementation, the first perception service request includes one or more of the following: perception service type, perception service requirement, perception area, application function identifier, and redundant perception indication.

[0098] In combination with the eighth aspect, in a possible implementation, the receiving unit is further used to receive a second parameter configuration request from an application function network element, the second parameter configuration request including third redundant perception configuration information; the sending unit is further used to send a first parameter configuration request based on the second parameter configuration request, the first parameter configuration request including second redundant perception configuration information, and the second redundant perception configuration information is obtained based on the third redundant perception configuration information.

[0099] In combination with the eighth aspect, in a possible implementation, the sending unit sending the first parameter configuration request based on the second parameter configuration request includes: when the application function network element authorization check passes, sending the first parameter configuration request based on the second parameter configuration request.

[0100] In combination with the eighth aspect, in a possible implementation, the second redundant perception configuration information includes one or more of the following: the perception service type allowing redundant perception, the perception area allowing redundant perception, the application function identifier allowing redundant perception, and the time allowing redundant perception.

[0101] In combination with the eighth aspect, in a possible implementation, the receiving unit is also used to receive a first perception result from the perception function network element, where the first perception result is obtained based on multiple perception data corresponding to the first perception service, and the multiple perception data are obtained through multiple perception node groups, where the perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending node and the perception signal receiving node in different perception node groups are different in at least one item.

[0102] A ninth aspect discloses a communication device, which may be a network capability exposure function network element or a module (e.g., a processor) in the network capability exposure function network element. The communication device includes: a receiving unit, configured to receive a second perception service request, the second perception service request being used to request a first perception service, the second perception service request including a redundant perception indication, the redundant perception indication being used to instruct acquisition of multiple perception data corresponding to the first perception service; and a sending unit, configured to send a first perception service request to the perception function network element based on the second perception service request, the first perception service request being used to request the first perception service.

[0103] In combination with the ninth aspect, in a possible implementation, the second perception service request further includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0104] In combination with the ninth aspect, in a possible implementation, the first perception service request includes one or more of the following: perception service type, perception service requirement, perception area, application function identifier, and redundant perception indication.

[0105] In combination with the ninth aspect, in a possible implementation, the sending unit sends a first perception service request to the perception function network element based on the second perception service request, including: sending a second perception authorization request to the data management network element based on the second perception service request, the second perception authorization request is used to request an authorization check for the first perception service; the receiving unit is also used to receive a second authorization response from the data management network element, the second authorization response is used to indicate that the first perception service is authorized; the sending unit is also used to send the first perception service request to the perception function network element based on the second authorization response.

[0106] In combination with the ninth aspect, in a possible implementation, the receiving unit is also used to receive a first perception result from a perception function network element, where the first perception result is obtained based on multiple perception data corresponding to the first perception service, and the multiple perception data are obtained through multiple perception node groups, where the perception node groups include perception signal sending nodes and perception signal receiving nodes, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0107] A tenth aspect discloses a communication device, which may be a terminal device, an application function network element, or other network element with perception requirements, or a module (e.g., a processor) in a terminal device, an application function network element (AF), or other network element with perception requirements. The communication device includes: a sending unit, configured to send a first perception service request, the first perception service request being used to request a first perception service, the first perception service request including a redundant perception indication, the redundant perception indication being used to instruct acquisition of multiple perception data corresponding to the first perception service.

[0108] In conjunction with the tenth aspect, in a possible implementation, the communication device further includes: a receiving unit, configured to receive a first perception result, the first perception result being obtained based on a plurality of perception data corresponding to the first perception service, the plurality of perception data being obtained through a plurality of perception node groups, the perception node groups including perception signal sending nodes and perception signal receiving nodes, the perception signal sending nodes and perception signal receiving nodes in different perception node groups having at least one different

[0109] In combination with the tenth aspect, in a possible implementation, the receiving unit is also used to receive a second perception result, which is a perception result obtained by executing the first perception service in a non-redundant perception manner; the sending unit is specifically used to: send a first perception service request based on the second perception result.

[0110] In combination with the tenth aspect, in a possible implementation, the first perception service request includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0111] In combination with the tenth aspect, in a possible implementation, before sending the first perception service request, the receiving unit is also used to receive a second perception result, which is a perception result obtained by executing the first perception service in a non-redundant perception manner; the sending unit is also used to send a second parameter configuration request based on the second perception result, and the second parameter configuration request includes third redundant perception configuration information.

[0112] In combination with the tenth aspect, in a possible implementation, the third redundant perception configuration information includes one or more of the following: the perception service type allowing redundant perception, the perception area allowing redundant perception, the application function identifier allowing redundant perception, and the time allowing redundant perception.

[0113] In combination with the tenth aspect, in a possible implementation, the sender of the first perception service request is a terminal device or an application function network element.

[0114] The eleventh aspect discloses a communication system, which includes a perception function network element and a data management network element. The perception function network element is used to implement the method provided in the above-mentioned first aspect and any possible implementation of the first aspect; the data management network element is used to implement the method provided in the above-mentioned second aspect and any possible implementation of the second aspect.

[0115] The twelfth aspect discloses a communication system, which includes a perception function network element and an application function network element. The perception function network element is used to implement the method provided in the above-mentioned first aspect and any possible implementation method of the first aspect; the application function network element is used to implement the method provided in the above-mentioned fifth aspect and any possible implementation method of the fifth aspect.

[0116] The thirteenth aspect discloses a communication system, which includes a perception function network element, an application function network element and a network open function network element. The perception function network element is used to implement the method provided in the first aspect and any possible implementation of the first aspect; the application function network element is used to implement the method provided in the fifth aspect and any possible implementation of the fifth aspect; the network open function network element is used to implement the method provided in the third aspect and any possible implementation of the third aspect, or to implement the method provided in the fourth aspect and any possible implementation of the fourth aspect.

[0117] The fourteenth aspect discloses a communication system, which includes a perception function network element, an application function network element, a network open function network element and a data management network element. The perception function network element is used to implement the method provided in the first aspect and any possible implementation of the first aspect; the application function network element is used to implement the method provided in the fifth aspect and any possible implementation of the fifth aspect; the network open function network element is used to implement the method provided in the third aspect and any possible implementation of the third aspect, or to implement the method provided in the fourth aspect and any possible implementation of the fourth aspect; the data management network element is used to implement the method provided in the second aspect and any possible implementation of the second aspect.

[0118] The fifteenth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instructions stored in a memory to implement the method provided in the above-mentioned first aspect and any possible implementation method of the first aspect.

[0119] The sixteenth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instructions stored in a memory to implement the method provided in the above-mentioned second aspect and any possible implementation method of the second aspect.

[0120] The seventeenth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instructions stored in a memory to implement the method provided in the above-mentioned third aspect and any possible implementation method of the third aspect.

[0121] The eighteenth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instructions stored in a memory to implement the method provided in the above-mentioned fourth aspect and any possible implementation method of the fourth aspect.

[0122] The nineteenth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instructions stored in a memory to implement the method provided in the above-mentioned fifth aspect and any possible implementation method of the fifth aspect.

[0123] As a possible implementation, the processors included in the communication device disclosed in the fifteenth aspect, the communication device disclosed in the sixteenth aspect, the communication device disclosed in the seventeenth aspect, the communication device disclosed in the eighteenth aspect, and the communication device disclosed in the nineteenth aspect may be one or more.

[0124] Optionally, the communication device disclosed in the fifteenth aspect, the communication device disclosed in the sixteenth aspect, the communication device disclosed in the seventeenth aspect, the communication device disclosed in the eighteenth aspect, and the communication device disclosed in the nineteenth aspect further include one or more memories.

[0125] The twentieth aspect discloses a computer-readable storage medium having a computer program or computer instructions stored thereon. When the computer program or computer instructions are executed, the method provided in the first aspect and any possible implementation of the first aspect is implemented, or the method provided in the second aspect and any possible implementation of the second aspect is implemented, or the method provided in the third aspect and any possible implementation of the third aspect is implemented, or the method provided in the fourth aspect and any possible implementation of the fourth aspect is implemented, or the method provided in the fifth aspect and any possible implementation of the fifth aspect is implemented.

[0126] A twenty-first aspect discloses a chip comprising a processor for executing a program stored in a memory. When the program is executed, the chip executes the method provided in the first aspect and any possible implementation of the first aspect, or executes the method provided in the second aspect and any possible implementation of the second aspect, or executes the method provided in the third aspect and any possible implementation of the third aspect, or executes the method provided in the fourth aspect and any possible implementation of the fourth aspect, or executes the method provided in the fifth aspect and any possible implementation of the fifth aspect.

[0127] As a possible implementation, the memory is located outside the chip.

[0128] Aspect 22 discloses a computer program product, which includes computer program code. When the computer program code is run, the method provided in the above-mentioned first aspect and any possible implementation of the first aspect is executed, or the method provided in the above-mentioned second aspect and any possible implementation of the second aspect is executed, or the method provided in the above-mentioned third aspect and any possible implementation of the third aspect is executed, or the method provided in the above-mentioned fourth aspect and any possible implementation of the fourth aspect is executed, or the method provided in the above-mentioned fifth aspect and any possible implementation of the fifth aspect is executed.

[0129] It should be understood that the implementation and beneficial effects of the above-mentioned multiple aspects or any possible implementation methods of the present application can be referenced to each other. BRIEF DESCRIPTION OF THE DRAWINGS

[0130] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0131] FIG1 is a schematic diagram of a system architecture of a 5G network provided in an embodiment of the present application;

[0132] FIG2 is a schematic diagram of a service-oriented architecture of a 5G network;

[0133] FIG3 is a schematic diagram of a perception scene;

[0134] FIG4 is a flow chart of a communication method disclosed in an embodiment of the present application;

[0135] Figures 5 to 16 are flowcharts of a group of communication methods disclosed in an embodiment of the present application;

[0136] FIG17 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0137] FIG18 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0138] FIG19 is a schematic structural diagram of a communication device disclosed in an embodiment of the present application;

[0139] FIG20 is a schematic structural diagram of another communication device disclosed in an embodiment of the present application;

[0140] FIG21 is a schematic structural diagram of another communication device disclosed in an embodiment of the present application;

[0141] FIG22 is a schematic structural diagram of another communication device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0142] The embodiments of the present application disclose a communication method, apparatus, and computer-readable storage medium that can ensure the accuracy and reliability of perception results. The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the accompanying drawings.

[0143] In order to better understand the embodiments of the present application, the system architecture of the embodiments of the present application is described below.

[0144] In the embodiments of the present application, some scenarios are illustrated using the fifth generation (5G) communication network as an example, but it should be understood that the solutions in the embodiments of the present application can also be applied to other communication networks, such as the sixth generation (6G) network, and the corresponding names can also be replaced by the names of corresponding functions / devices in other communication networks.

[0145] Please refer to Figure 1, which is a schematic diagram of a 5G network system architecture provided by an embodiment of the present application. As shown in Figure 1, the system architecture may include terminal devices and various network entities, which are described below.

[0146] Terminal equipment, also known as terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), customer premise equipment (CPE), etc., is a device with wireless communication capabilities that can provide voice and / or data connectivity services to users. The terminal device may be a handheld terminal, a laptop computer, an RSU (road side unit), a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a tag, a wireless modem, other processing devices connected to a wireless modem, a handheld device, a laptop computer, a cordless phone or a wireless local loop (WLL) station, a machine type communication (MTC) terminal, a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), an in-vehicle device (such as a car, a bicycle, an electric car, an airplane, a ship, a train, a high-speed train, etc.), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a smart home device (such as a refrigerator, a television, an air conditioner, an electric meter, etc.), an intelligent robot, a workshop device, a wireless terminal in self-driving, a remote medical device, or a similar device. Wireless terminals in smart surgery, smart grids, transportation safety, smart cities, smart homes, aerial devices (such as intelligent robots, hot air balloons, drones, airplanes), and other network-accessible devices can be fixed or mobile. Terminal devices can be deployed on land, indoors or outdoors, handheld, wearable, or in vehicles; on water (such as ships); or in the air (such as aircraft, balloons, and satellites).

[0147] The (Radio) Access Network (R)AN is a network consisting of multiple 5G-RAN nodes, used to implement wireless physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management functions. The 5G-RAN can connect to the user plane function (UPF) via the user plane interface N3 to transmit data from terminal devices. The 5G-RAN can also establish a control plane signaling connection with the access and mobility management function (AMF) via the control plane interface N2 to implement functions such as radio access bearer control. It should be understood that 5G-RAN nodes are also access network devices that primarily provide access to terminal devices. Access network devices can include radio access network (RAN) devices and access node (AN) devices. RAN devices are primarily wireless network devices in 3GPP networks, while AN devices can be access network devices not defined by 3GPP. RAN devices can include various types of base stations, such as macro base stations, micro base stations (also known as small base stations), relay stations, access points, and balloon stations. It is understandable that the RAN network element can be understood as an access network device or a base station in a traditional network.

[0148] AMF is mainly responsible for UE authentication, UE mobility management, network slice selection, and SMF selection. It serves as the anchor point for N1 and N2 signaling connections, provides N1 / N2SM message routing for SMF, and maintains and manages UE status information.

[0149] The session management function (SMF) is responsible for all control plane functions of UE session management, including user plane function (UPF) selection, Internet protocol (IP) address allocation, session quality of service (QoS) management, and obtaining policy and charging control (PCC) policies (from PCF).

[0150] The UPF mainly serves as the anchor point for protocol data unit (PDU) session connections and is responsible for data packet filtering, data transmission / forwarding, rate control, and billing information generation for user equipment.

[0151] The unified data management (UDM) network element is mainly used to manage and control user data, for example, the management of contract information, including obtaining contract information from the unified data repository (UDR) and providing it to other network elements (such as AMF); generating the third generation partnership project (3GPP) authentication credentials for the UE; registering and maintaining the network element currently serving the UE, for example, the AMF currently serving the UE, that is, the serving AMF. Among them, UDR is also one of the network elements in the 5G core network, mainly used to store user data, including contract data called by UDM, policy information called by PCF, structured data for capability opening, application data called by NEF, etc. In the embodiment of the present application, the operations performed by UDM can also be performed by UDR, or performed by UDR and UDM in cooperation. For example, UDM and UDR can be collectively referred to as data management network elements.

[0152] Application function (AF) network elements primarily interact with core network elements to provide services. For example, they interact with the policy and control function (PCF) to perform service policy control, interact with the NEF to obtain network capability information or provide application information to the network, and provide data network access point information to the PCF to generate routing information for corresponding data services.

[0153] The authentication server function (AUSF) is used to perform security authentication on the UE when the UE accesses the network.

[0154] The network slice selection function (NSSF) selects a set of slice instances for the UE, determines the AMF set, allowed NSSAI, etc. for the UE.

[0155] PCF mainly provides configuration policy information for UE and provides policy information for controlling UE to the control plane network elements of the network (for example, AMF, SMF).

[0156] Data network (data network) network elements are used to provide a network for transmitting data.

[0157] The reference points between the above network elements can be seen in Figure 1, such as reference point N1 between UE and AMF, reference point N4 between SMF and UPF, reference point N13 between UDM and AUSF, etc. For the specific description of these reference points, please refer to the relevant definitions in the 5G standard.

[0158] Figure 1 above briefly introduces the reference point-based system architecture. Now, please refer to Figure 2, which shows a schematic diagram of the service-based architecture of a 5G network. As shown in Figure 2, this service-based architecture includes service-based architecture (SBA) interfaces such as Nnssf, Nausf, Nnef, Namf, Npcf, Nsmf, Nudm, and Naf.

[0159] The naming convention for the 5G service-based interface is to add N before the name of the functional entity. For example, Namf is the service-based interface provided by AMF, Nsmf is the service-based interface provided by SMF, Nnef is the service-based interface provided by NEF, Npcf is the service-based interface provided by PCF, and Nudm is the service-based interface provided by UDM.

[0160] It should be understood that the various functional entities in the 5G core network can interact with each other through the SBA interface. For example, the AF can interact with the NEF through the Nnef interface and use the services provided by the NEF. For another example, the NEF can interact with the UDM through the Nudm interface and use the services provided by the UDM.

[0161] Regarding the network exposure function (NEF) network element in Figure 2, it is mainly used to connect the interactions between other internal network elements of the core network and the external application servers of the core network, so as to provide network capability information to the external application servers, or provide information of the external application servers to the core network network elements.

[0162] In the embodiment of the present application, the network architecture shown in Figures 1 and 2 may further include a sensing function (SF) network element. The SF network element is primarily responsible for processing related sensing services. For example, the SF network element may receive sensing service requests from within the network (e.g., a UE) or from outside the network (e.g., an AF), and control the RAN network element to perform sensing based on the sensing service requests.

[0163] It should be noted that the SF network element can be one of the network elements in the 5G core network (5G core, 5GC) or a non-core network element, and this application does not specifically limit this. When the SF network element is one of the network elements in the 5G core network, the SF network element can be connected to other network elements in the 5G core network through the SBA interface, that is, it can communicate with other network elements in the 5G core network through the SBA interface. When the SF network element is a non-core network element, the SF network element cannot be connected to other network elements in the 5G core network through the SBA interface. At this time, it may be necessary to interact with other 5G core network elements through the NEF. Optionally, the SF network element can be implemented by other network elements in the core network.

[0164] It should be understood that Figures 1 and 2 are only schematic diagrams. The architecture shown in Figures 1 and 2 may also include other devices / network elements, such as a location management function (LMF), etc. For details, please refer to the relevant content in the 5G standard.

[0165] It should also be understood that the above network elements or functions can be implemented in the form of hardware, computer software, or a combination of hardware and computer software. For example, the above network elements or functions can be implemented by a single device, or by multiple devices, or by a functional module within a single device, and the embodiments of this application do not specifically limit this.

[0166] Furthermore, the aforementioned "network element" may also be referred to as an entity, device, or module, etc., and this application does not limit this. Furthermore, for ease of description, the term "network element" is omitted in some of the following descriptions. For example, an NEF network element is referred to as NEF. In this case, "NEF" should be understood to refer to an NEF network element or NEF entity. Similar interpretations apply to other network elements or functions. In other words, functions, functional network elements, and functional entities can be equivalent. For example, a UDM, a UDM network element, and a UDM entity can be equivalent.

[0167] It should be understood that the technical solutions provided in the embodiments of the present application can be applied to communication systems of various radio access technologies (RAT), such as: fifth-generation (5G) communication systems, transition systems between 5G communication systems and 6G communication systems (the transition system may also be referred to as 5.5G communication systems), networks integrating multiple systems, etc.; of course, it can also be future communication systems, such as sixth-generation (6G) or even seventh-generation (7G) communication systems.

[0168] It should be noted that the system architecture, network architecture, and business scenarios (or application scenarios) described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of communication network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0169] In order to better understand the embodiments of the present application, the following briefly introduces the relevant contents, terms or nouns involved in the present application.

[0170] 1. Perception

[0171] Perception is primarily achieved through the transmission of electromagnetic waves, enabling perception of the electromagnetic wave propagation environment, such as the detection, positioning, identification, and imaging of targets within that environment. For example, a perception signal transmitter can send electromagnetic waves, which are then reflected by a target and received by a perception signal receiver. Processing equipment can then perform feature extraction and data analysis on the reflected signal and its associated data (such as the time the reflected signal was received) to obtain a perception result. This perception result can reflect information such as the size and outline of the target.

[0172] With the advancement of communication technology, base stations are using increasingly higher frequency bands, such as millimeter wave bands. Higher frequencies provide higher perception resolution (such as spatial resolution) and greater anti-interference capabilities. Therefore, when base stations possess the perception capabilities afforded by millimeter wave bands, wireless communication systems / networks can sense and identify specific areas, objects, or events, addressing perception requirements in many scenarios, such as autonomous driving and drone monitoring. Consequently, perception will become a crucial capability and characteristic of future communication networks, and the integration of communication and perception (referred to as synaesthesia) is also a key development direction for future communication networks.

[0173] For example, the perception capabilities of wireless communication networks can be applied in scenarios such as automated / assisted driving, connected vehicles, intelligent transportation, 3D map reconstruction, smart industry, drone monitoring and management, intelligent interaction, environmental monitoring, and posture detection and recognition. For example, perception can be used to generate high-precision dynamic maps to assist drones / smart cars in autonomous driving. Another example is that during driving, perception can be used to identify dangerous events (such as the sudden appearance of a person or object) and notify the smart car / drone to perform emergency maneuvers. Another example is that perception can be used to identify driving violations, such as vehicles occupying emergency lanes, drones leaving their routes, or drones invading no-fly zones (e.g., airports). Another example is that perception can be used to identify abnormal postures, such as when a person falls, and issue alerts. Another example is that perception can be used for weather monitoring, pollution monitoring, and pest and disease monitoring.

[0174] Common performance indicators of perception include perception accuracy, perception resolution, horizontal field of view (FOV), etc. Perception accuracy can generally indicate the deviation between the perception result and the actual result, and may include distance accuracy, velocity accuracy, angle accuracy, etc. Horizontal FOV refers to the perception angle in the horizontal direction (such as 120°). Perception resolution is the ability to distinguish different perception targets, and may include distance resolution, velocity resolution, angle resolution, etc. Among them, distance resolution is the ability to distinguish adjacent targets in distance, usually measured in terms of the minimum resolvable distance interval. Velocity resolution is the ability to distinguish targets in radial velocity, usually measured in terms of the minimum resolvable velocity. Angular resolution / angular measurement accuracy is the ability to distinguish adjacent targets in angle, usually measured in terms of the minimum resolvable angle.

[0175] 2. Perception Mode

[0176] In the embodiment of the present application, for an access network device or a terminal device, it can be used as a perception signal transmitter or a perception signal receiver. Therefore, there are many combinations of the transmitter and receiver of the perception signal. According to the different combinations of the transmitter and receiver of the perception signal, the perception mode can be divided into the following six types: access network device self-transmission and self-reception (access network device self-transmits perception signal and self-receives reflected signal), terminal device self-transmission and self-reception (terminal device self-transmits perception signal and self-receives reflected signal), collaboration between access network devices (one access network device sends perception signal and the other access network device receives reflected signal), access network device sends and terminal device receives (access network device sends perception signal and terminal device receives reflected signal), terminal device sends and access network device receives (terminal device sends perception signal and access network device receives reflected signal), collaboration between terminal devices (one terminal device sends perception signal and the other terminal device receives reflected signal). The above six perception modes are shown in Table 1 below:

[0177] Table 1 Examples of perception patterns

[0178] In the embodiments of the present application, a perception signal transmitter may also be referred to as a perception signal transmitting node, and a perception signal receiver may also be referred to as a perception signal receiving node. Furthermore, the perception signal receiving node and the perception signal transmitting node may be collectively referred to as a perception node. In the case of autonomous transmission and reception by access network devices and autonomous transmission and reception by terminal devices, the perception signal receiving node and the corresponding perception signal transmitting node are the same node.

[0179] 3. Redundancy Perception

[0180] Redundant perception is a relative concept. For example, in order to obtain the perception result corresponding to a certain perception service, it is sufficient to obtain one perception data corresponding to the perception service under normal circumstances, provided that the perception data is accurate. However, since the accuracy of the perception data cannot be guaranteed, it is possible to obtain more perception data corresponding to the perception service than under normal circumstances (such as 2, 3, 4, etc.) to improve the accuracy of the perception result, and even to identify the perception data with larger deviations. This method is also redundant perception. Among them, the perception data is data obtained based on a specific perception task. The embodiment of the present application does not limit the specific data format. For example, it can be a single data value, or one or more groups of matrix data, or one or more groups of point cloud data, or a combination of the above-mentioned multiple formats of data. The following text uniformly uses perception data to describe. For example, one perception data can be obtained by performing a specific perception task once, and multiple perception data can be obtained by performing multiple perception tasks or performing multiple specific perception tasks.

[0181] As can be seen, redundant sensing requires more sensory data than normal sensing. While normal sensing requires one sensory data point, redundant sensing requires two, three, four, or even more. Furthermore, these sensory data points are typically independent (e.g., obtained by performing the sensing task using different combinations of sensing signal sending and receiving nodes). This allows for improved accuracy of sensing results and even the identification of sensory data with significant deviations.

[0182] For example, under normal circumstances, a perception result can be obtained based on a single perception data set. However, to test whether the perception result is accurate, another perception data set can be obtained. The two perception data sets, or the perception results obtained based on the two perception data sets, can then be compared. If they are substantially identical, the perception result is accurate. If they are different or have a significant deviation, the perception result is inaccurate. Furthermore, to identify perception data with a significant deviation, more perception data can be obtained. For example, if two of the three perception data sets are substantially identical, and another perception data set differs significantly from the two, the two substantially identical perception data sets can be determined as accurate perception data, and the other perception data set can be determined as perception data with a significant deviation. The perception result can then be obtained based on the two normal perception data sets.

[0183] As can be seen from the above description, perception depends on the received reflected signal and the data related to the reflected signal (such as the reception time of the reflected signal, etc.). In some cases, the reflected signal received by the perception signal receiving node or the data related to the reflected signal obtained may be inaccurate, which will lead to a biased perception result. For example, the reflection signal path may be in an area with complex channels (as shown in Figure 3), such as occlusion / multipath caused by complex environments such as cities, which may cause the reflection signal to have a time delay, etc., which will cause the perception result obtained based on the received reflected signal to deviate from the actual situation, such as the distance to the perception target calculated based on the reflection signal is different from the actual distance. In order to solve the above problems, the embodiment of the present application proposes a technical solution for realizing redundant perception in a communication network, which can ensure the accuracy of the perception results and the reliability of perception.

[0184] In order to facilitate understanding of the embodiments of the present application, the relevant contents of the embodiments of the present application are briefly introduced below. First, in the embodiments of the present application, the triggering of the perception request can be triggered by the UE, or by the AF, or by other network elements with perception requirements, and the embodiments of the present application are not limited to this. Secondly, the execution conditions for redundant perception include multiple situations, and several examples are given below. Case 1: It is necessary to carry a redundant perception indication in the perception request. In this case, redundant perception will only be performed if the redundant perception indication is carried in the perception request. If the redundant perception indication is not carried in the perception request, redundant perception will not be performed. Case 2: It is necessary to carry a redundant perception indication in the perception request and redundant perception needs to be authorized. In this case, redundant perception will only be performed if the redundant perception indication is carried in the perception request and redundant perception is authorized. If the redundant perception indication is not carried in the perception request, or the redundant perception indication is carried in the perception request but redundant perception is not authorized, redundant perception will not be performed. Case 3: It is not necessary to carry a redundant sensing indication in the sensing request, but redundant sensing must be authorized. In this case, a redundant sensing authorization check can be performed for each sensing request. If redundant sensing is authorized, redundant sensing can be performed. Conversely, if redundant sensing is not authorized, redundant sensing will not be performed. Three cases are simply listed here, but it should be understood that there are other possible cases. For example, it is not necessary to carry a redundant sensing indication in the sensing request, nor is it necessary to perform a redundant sensing authorization check. Redundant sensing is performed on all sensing requests by default. This embodiment of the present application does not limit this.

[0185] Furthermore, in the case where redundant perception needs to be authorized, there may be multiple situations in which authorization checks are performed. The authorization check for redundant perception may be performed by UDM, or by SF. It should be understood that there are different combinations of the above-mentioned situations (perception request trigger + redundant perception execution conditions + redundant perception authorization situation). Under different combinations, the overall process of redundant perception may be different, but in essence, the (redundant) perception demander first initiates a perception request, and then, when the perception request meets the redundant perception execution conditions (such as the perception request carries a redundant perception indication), the SF sends perception control requests to the corresponding multiple perception nodes respectively to obtain multiple perception data and realize redundant perception. The combination of the above-mentioned situations will be described below through different embodiments.

[0186] Among them, embodiment 1 is a case where the UE initiates a sensing request, which needs to carry a redundant sensing indication, but does not require a redundant sensing authorization check. Embodiment 2 is a case where the AF initiates a sensing request, which needs to carry a redundant sensing indication, but does not require a redundant sensing authorization check. Embodiment 3 is a case where the UE initiates a sensing request, which needs to carry a redundant sensing indication, and the UDM performs a redundant sensing authorization check. Embodiment 4 is a case where the AF initiates a sensing request, which needs to carry a redundant sensing indication, and the UDM performs a redundant sensing authorization check. Embodiment 5 is a case where the UE initiates a sensing request, which does not need to carry a redundant sensing indication, and the UDM performs a redundant sensing authorization check. Embodiment 6 is a case where the AF initiates a sensing request, which does not need to carry a redundant sensing indication, and the UDM performs a redundant sensing authorization check. Embodiment 7 is a case where the UE initiates a sensing request, which needs to carry a redundant sensing indication, and the SF performs a redundant sensing authorization check. Embodiment 8 is a case where the AF initiates a sensing request, which needs to carry a redundant sensing indication, and the SF performs a redundant sensing authorization check. Embodiment 9 is a case where the UE initiates a sensing request, which does not need to carry a redundant sensing indication, and the SF performs a redundant sensing authorization check. The tenth embodiment is a case where the AF initiates a perception request, the perception request does not need to carry a redundant perception indication, and the SF performs a redundant perception authorization check.

[0187] The redundant perception process in the embodiment of the present application mainly involves network elements such as UE, SF, UDM, NEF, and AF. For ease of understanding, the functions of each network element in the embodiment of the present application are briefly described below. Among them, UE and AF are mainly used as the demand side of perception and are used to initiate perception requests. SF mainly receives perception requests from other network elements (such as UE, AF, NEF, etc.), and when the perception request meets the redundant perception trigger condition (such as the redundant perception indication carried in the perception request), it sends perception control requests to the corresponding multiple perception nodes to obtain multiple perception data. UDM mainly performs authorization checks, including authorization checks for redundant perception and / or other authorization checks (such as authorization checks on whether AF has the authority to initiate perception requests, authorization checks on whether AF has the authority to initiate parameter creation requests, etc.). NEF mainly serves as a communication bridge between AF and UDM or AF and SF. Of course, the functions of the above-mentioned network elements are not limited to this, and under the combination of the above-mentioned different situations, the overall process of mutual cooperation between the network elements to achieve redundant perception may also be different.

[0188] The following is an illustrative description of the overall process of the technical solution provided in the embodiments of the present application.

[0189] Please refer to Figure 4, which is a flow chart of a communication method disclosed in an embodiment of the present application. As shown in Figure 4, the method may include but is not limited to the following steps:

[0190] 401. The first network element sends a first perception service request to the SF, where the first perception service request is used to request a first perception service.

[0191] Exemplarily, when there is a redundancy awareness requirement, the first network element may send a first awareness service request to the SF. Correspondingly, the SF may receive the first awareness service request from the first network element.

[0192] Among them, the first network element can be a terminal device, an AF, an NEF, or other network elements with perception requirements, which is not limited in the embodiments of the present application. Optionally, when the first network element is an AF, the AF can send a first perception service request to the SF through the NEF. Optionally, when the first network element is a terminal device, the terminal device can send a first perception service request to the SF through the AMF, or the terminal device can send the first perception service request directly to the SF, for example, directly sending the first perception service request to the SF through the user plane channel.

[0193] It should be understood that the execution conditions of redundant perception in the embodiments of the present application include multiple situations, and several examples are given below. Situation 1: It is sufficient to carry a redundant perception indication in the perception request, and there is no need to perform an authorization check for redundant perception. Situation 2: It is necessary to carry a redundant perception indication in the perception request, and redundant perception needs to be authorized. Situation 3: It is not necessary to carry a redundant perception indication in the perception request, but redundant perception needs to be authorized. For these three situations, please refer to the relevant descriptions above.

[0194] Specifically, for the above-mentioned situation one, the first perception service request may include a redundant perception indication, so as to trigger SF to perform the first perception service in a redundant perception manner. For the above-mentioned situation two, the first perception service request may also include a redundant perception indication, so as to trigger the authorization check of redundant perception, and when redundant perception is authorized, enable SF to perform the first perception service in a redundant perception manner. For the above-mentioned situation three, the first perception service request may not include a redundant perception indication, and the authorization check of redundant perception will be triggered by default, and when redundant perception is authorized, enable SF to perform the first perception service in a redundant perception manner.

[0195] It should be understood that the redundant perception indication in the first perception service request is used to indicate the acquisition of multiple perception data corresponding to the first perception service, or to indicate the execution of the first perception service by / adopting redundant perception, or to indicate the acquisition of the perception result of the first perception service by redundant perception, or to indicate the perception by redundant perception. Alternatively, the indication of the acquisition of multiple perception data corresponding to the first perception service can be understood as an indication of the execution of the first perception service by / adopting redundant perception, or can also be understood as an indication of the acquisition of the perception result of the first perception service by redundant perception. The embodiment of the present application does not specifically limit the definition of the redundant perception indication.

[0196] Optionally, for the above-mentioned cases 1 and 2, the first perception service request may further include one or more of the following: perception service type, perception service requirement, perception area, and application function identifier. For the above-mentioned case 3, the first perception service request may include one or more of the following: perception service type, perception service requirement, perception area, and application function identifier. It should be understood that when the first network element is a terminal device, the first perception service request may not include the application function identifier, but may include the identifier of the terminal device.

[0197] Specifically, the perception service type can be used to indicate the perception service type information corresponding to the first perception service request, that is, the perception service type information of the first perception service, such as a specific perception service type identifier, a perception service type name, etc., which is not limited in the embodiments of the present application. The perception service type can include multiple types, which can be pre-defined or specified by relevant standards. Exemplarily, the perception service type can include drone traffic monitoring, traffic flow monitoring, map reconstruction, illegal driving monitoring, abnormal posture monitoring, weather monitoring, etc. It should be understood that the perception service type can also be divided or defined in other ways.

[0198] The perception service requirement may be used to indicate requirements for the first perception result, and may include one or more of distance accuracy, velocity accuracy, angle accuracy, distance resolution, velocity resolution, angle resolution, perception delay, etc. For example, the perception service requirement in the first perception service request may indicate that the distance accuracy is 10 centimeters (cm) and the distance resolution is 1 cm.

[0199] The perception area can be used to indicate the area that needs to be perceived. The perception area here can be external area information or internal area information. External area information can be area information defined or used by non-operator networks (such as third-party networks to which AF belongs, map navigation service providers, etc.), such as specific geographical locations or geographical ranges. For example, the external area information can be Airport C, District B, City A, Intersection D, District B, City A, etc. Internal area information can be area information defined or used by operator networks, such as tracking area ID, cell ID, base station ID, etc. It should be noted that when the first perception service request comes from AF, the perception area here can be external area information. When the first perception service request comes from a terminal device or NEF, the perception area here can be internal area information or external area information.

[0200] The identification information of the application function identifier (AF) may indicate the corresponding AF. The identification information of the terminal device (terminal device) may indicate the corresponding terminal device. For example, the identification information of the terminal device may be a generic public subscription identifier (GPSI) or a user permanent identifier (SUPI).

[0201] It should be understood that the information included in the above-mentioned first perception service request is merely illustrative and should not be construed as limiting. Except for the redundant perception indication, the embodiments of this application do not specifically limit the information carried in the first perception service request. For example, in addition to the above-mentioned perception service type, perception service requirements, and perception area, the first perception service request may also include other information, such as the execution time of the first perception service, the duration of the first perception service, and the execution frequency.

[0202] 402.SF sends perception control requests to the perception signal receiving nodes in multiple perception node groups based on the first perception service request. Each perception node group includes a perception signal sending node and a perception signal receiving node. The perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0203] After receiving the first perception service request from the first network element, the SF may send perception control requests to the perception signal receiving nodes in the multiple perception node groups based on the first perception service request. Correspondingly, the perception signal receiving nodes in the multiple perception node groups may receive the perception control requests from the SF.

[0204] It should be understood that the SF may also send a sensing control request to each of the sensing signal sending nodes in the multiple sensing node groups, where the sensing control request is used to request the corresponding sensing signal sending node to send a sensing signal. Accordingly, the sensing signal sending nodes in the multiple sensing node groups may each receive the sensing control request from the SF. Thereafter, the sensing signal sending nodes in the multiple sensing node groups may each send a sensing signal based on the corresponding sensing control request, and the sensing signal receiving nodes in the multiple sensing node groups may each receive the corresponding reflected signal and obtain data related to the reflected signal (such as the reflected signal reception time).

[0205] It can be understood that, for the above-mentioned situations one and two, SF can send perception control requests to the perception signal receiving nodes in multiple perception node groups respectively based on the redundant perception indication in the first perception service request. Specifically, for situation one, when SF determines that the first perception service request includes a redundant perception indication, it can directly send perception control requests to the perception signal receiving nodes in multiple perception node groups respectively. For situation two, when SF determines that the first perception service request includes a redundant perception indication, it performs an authorization check for redundant perception based on the first perception service request, and when the authorization is passed (authorized), it sends perception control requests to the perception signal receiving nodes in multiple perception node groups respectively. And for situation three, SF can directly perform an authorization check for redundant perception based on the first perception service request, and when the authorization is passed, it sends perception control requests to the perception signal receiving nodes in multiple perception node groups respectively.

[0206] In the embodiment of the present application, the authorization situations of redundancy perception may include multiple situations. For example, the UDM may be the authorizer of redundancy perception, or the SF may be the authorizer of redundancy perception.

[0207] When the UDM acts as the authorizer for redundant perception, the SF may send a first perception authorization request to the UDM based on the first perception service request. The first perception authorization request is used to request an authorization check for obtaining the multiple perception data corresponding to the first perception service. The request for an authorization check for obtaining the multiple perception data corresponding to the first perception service can also be understood as a request for an authorization check for executing the first perception service through / using redundant perception, which will not be further described below. Accordingly, the UDM may receive the first perception authorization request from the SF. Thereafter, the UDM may perform an authorization check for obtaining the multiple perception data corresponding to the first perception service based on the first perception authorization request and the first redundant perception configuration information. Furthermore, if the first perception authorization request satisfies the first redundant perception configuration information, the UDM may determine that the multiple perception data corresponding to the first perception service is authorized and may send a first authorization response to the SF. The first authorization response is used to indicate that the multiple perception data corresponding to the first perception service is authorized. Accordingly, the SF may receive the first authorization response from the UDM and, based on the first authorization response, determine that the multiple perception data corresponding to the first perception service is authorized. It should be understood that the first authorization response is also the authorization response in response to the first perception authorization request.

[0208] Optionally, when receiving the first perception service request, SF may, by default, use redundant perception to execute the first perception service and be authorized, that is, it is authorized to obtain multiple perception data corresponding to the first perception service. Exemplarily, this situation may be that before SF receives the first perception service request, UDM may first perform an authorization check on the first perception service request. For example, NEF may request UDM to perform an authorization check on obtaining multiple perception data corresponding to the first perception service before sending the first perception service request to SF. After UDM performs an authorization check on obtaining multiple perception data corresponding to the first perception service, that is, after performing an authorization check on executing the first perception service using redundant perception, UDM may reply to NEF with an authorization response message to indicate the authorization result. NEF will only send the first perception service request to SF after obtaining the result of authorization approval. In other words, NEF will send the first perception service request to SF only when it determines that it is authorized to obtain multiple perception data corresponding to the first perception service.

[0209] In some possible implementations, the first perception authorization request may include a redundant perception indication. When the UDM determines that the first perception authorization request includes the redundant perception indication, it performs an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception authorization request and the first redundant perception configuration information.

[0210] Optionally, the first perception authorization request may include one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication. It should be understood that when the first network element is a terminal device, the first perception authorization request may not include the application function identifier, but may include the identifier of the terminal device.

[0211] Optionally, the first authorization response may include first authorization indication information, where the first authorization indication information is used to indicate that obtaining the multiple sensing data corresponding to the first sensing service is authorized. Exemplarily, the first authorization indication information may be a redundant sensing indication.

[0212] When the SF acts as the authorizer of redundant perception, the SF can directly perform an authorization check on the acquisition of multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information. Furthermore, when the first perception service request satisfies the first redundant perception configuration information, the SF can determine that the authorization to obtain the multiple perception data corresponding to the first perception service is passed. It should be understood that, for the above-mentioned second situation, the SF can perform an authorization check on the acquisition of multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information when the first perception service request includes a redundant perception indication.

[0213] The first redundant perception configuration information is used to determine whether the acquisition of multiple perception data corresponding to the first perception service is authorized. Specifically, when the first perception service request satisfies the first redundant perception configuration information, it indicates that the first perception service authorization is performed using redundant perception. Optionally, the first redundant perception configuration information may include one or more of the following: the perception service type that allows redundant perception, the perception area that allows redundant perception, the application function identifier that allows redundant perception, and the time that allows redundant perception. Among them, the first perception service request satisfying the first redundant perception configuration information may be that at least one item of information included in the first perception service request satisfies at least one item of information in the first redundant perception configuration information. For details, please refer to the following relevant description.

[0214] It should be understood that the first redundancy awareness configuration information can be pre-configured, dynamically configured (such as dynamically configured through the service interface of SF or UDM), or configured in other ways, which is not limited in the embodiments of the present application.

[0215] Among them, the perception service types that allow redundant perception are also service types that can perform redundant perception, and may include one or more perception service types, such as 3D map reconstruction, drone monitoring, etc. In the embodiment of the present application, the perception service types that allow redundant perception can be determined based on actual conditions or perception needs. For example, for a specific perception service that requires high accuracy of the perception results (such as a drone traffic monitoring service), it can be configured to allow redundant perception, while for a perception service that does not require high accuracy of the perception results, it is not necessary to configure to allow redundant perception.

[0216] The perception area that allows redundant perception is also the perception area where redundant perception can be performed, and may include one or more perception areas, such as perception area 1 and perception area 2. In the embodiment of the present application, the perception area that allows redundant perception can be determined based on actual conditions or perception needs. For example, for areas with complex channels (such as traffic intersections with high-rise buildings and overpasses), it can be configured to allow redundant perception. For another example, if the perception results of a certain area deviate from the actual situation based on the analysis of historical perception data, the area can be configured to allow redundant perception.

[0217] The time period during which redundant perception is allowed is also the time period during which redundant perception can be performed, and may include one or more time periods. In an embodiment of the present application, the time period during which redundant perception is allowed may be determined based on actual conditions or perception requirements. For example, if the perception results obtained during a certain time period based on analysis of historical perception data are generally different from the actual conditions, the time period may be configured to allow redundant perception. For another example, in certain scenarios where the accuracy of perception results needs to be improved, such as during peak hours at train stations and morning rush hours on highways, redundant perception may be configured to be allowed.

[0218] The identification of the application function that allows redundant perception is used to determine the AF that can perform redundant perception, such as the AF of the Transportation Bureau, the AF of the Air Traffic Control Bureau, etc. The identification of the terminal device that allows redundant perception is used to determine the terminal device that can perform redundant perception, wherein the identification of the terminal device that allows redundant perception can be the identification of the terminal device group or the identification of a specific terminal device. It should be understood that the first redundant perception configuration information here is for the configuration of the SF itself, and does not distinguish between the scenarios where the perception request comes from the terminal device or the AF, and should not constitute a limitation. Of course, for the two situations where the perception request comes from the terminal device or the AF, the redundant perception configuration information can also be configured separately.

[0219] Based on the relevant configuration of the first redundant perception configuration information, the perception authorization party can match the information included in the first perception authorization request with the first redundant perception configuration information to determine whether the first perception authorization request satisfies the first redundant perception configuration information, that is, to determine whether the acquisition of multiple perception data corresponding to the first perception service is authorized. Specifically, the first perception service request satisfies the first redundant perception configuration information may be that at least one item of information included in the first perception authorization request satisfies at least one item of information in the first redundant perception configuration information. In the embodiment of the present application, the specific configuration of the first redundant perception configuration information may include multiple situations, which are introduced below.

[0220] One is to configure only one of the perception service types that allow redundant perception, the perception areas that allow redundant perception, and the time that allows redundant perception. In this case, when the information included in the first perception authorization request meets the corresponding configuration, it can be determined that it is authorized. For example, only the perception service types that allow redundant perception can be configured. After that, SF can check whether the perception service type included in the first perception authorization request belongs to the configured perception service types that allow redundant perception. If it does, it can be determined that the first perception service request meets the first redundant perception configuration information, that is, it can be determined that the authorization to obtain multiple perception data corresponding to the first perception service is passed. For another example, only the time that allows redundant perception can be configured. After that, SF can determine whether the time of receiving the first perception authorization request (defaulted as the execution time of the first perception service) or the execution time of the first perception service carried in the first perception service request is within the configured time period that allows redundant perception. If it does, it can be determined that the first perception service request meets the first redundant perception configuration information.

[0221] The other is to configure multiple types of perception services that allow redundant perception, perception areas that allow redundant perception, and time periods that allow redundant perception, but the first perception service request only needs to meet one of them. For example, the perception service types that allow redundant perception and the perception areas that allow redundant perception can be configured. After that, the SF can check whether the perception service type included in the first perception authorization request belongs to the configured perception service type that allows redundant perception, or whether the perception area included in the first perception authorization request belongs to the configured perception area that allows redundant perception. If one of them does, it can be determined that the first perception service request meets the first redundant perception configuration information.

[0222] Another method is to configure multiple types of sensing services that allow redundant sensing, sensing areas that allow redundant sensing, and times that allow redundant sensing, and the first sensing service request needs to meet multiple of these requirements simultaneously. For example, you can configure the types of sensing services that allow redundant sensing and the sensing areas that allow redundant sensing. After that, the SF can check whether the sensing service type included in the first sensing authorization request belongs to the configured sensing service type that allows redundant sensing, and whether the sensing area included in the first sensing authorization request belongs to the configured sensing area that allows redundant sensing. If both belong, it can be determined that the first sensing service request meets the first redundant sensing configuration information.

[0223] Another is to configure multiple types of perception services that allow redundant perception, perception areas that allow redundant perception, and times that allow redundant perception, and there is a binding relationship between the multiple configurations, and the first perception service request needs to satisfy multiple of them and the corresponding binding relationship at the same time. For example, the perception areas that allow redundant perception and the times that allow redundant perception can be configured, and there is a binding relationship between the two. Exemplarily, it can be configured as perception area 1 + time period 1, perception area 2 + time period 1, perception area 3 + time period 2, etc. Afterwards, SF can check whether the perception area (such as perception area 1) included in the first perception authorization request belongs to the configured perception area that allows redundant perception, and whether the time of receiving the first perception authorization request or the execution time of the first perception service carried in the first perception service request is within the corresponding configured time period that allows redundant perception. If both belong, it can be determined that the first perception service request satisfies the first redundant perception configuration information. For another example, the application function identifier that allows redundant perception and the perception service type that allows redundant perception can be configured, and there is a binding relationship between the two. For example, it can be configured as application function identifier 1+perception service type 1, application function identifier 2+perception service type 1, application function identifier 3+perception service type, etc.

[0224] It can be seen that the redundancy-aware authorization check includes multiple situations and can be flexibly configured according to actual conditions.

[0225] It should be understood that the data types of the information included in the first redundant perception configuration information and the information included in the first perception authorization request may correspond, which can facilitate direct matching. For example, if the perception service type allowed for redundant perception included in the first redundant perception configuration information is a perception service ID, then the perception service type included in the first perception authorization request may also be the corresponding perception service ID. For another example, if the perception area allowed for redundant perception included in the first redundant perception configuration information is a tracking area identifier, then the perception area included in the first perception authorization request may also be the corresponding tracking area identifier.

[0226] It is understandable that the above description of the first redundant perception configuration information is merely illustrative and does not constitute a limitation. In other possible implementations of the present application, the first redundant perception configuration information may further include more information that can be used for authorization checking, such as the identifier of the terminal device that is allowed to perform redundant perception, the identifier of the AF that is allowed to perform redundant perception, etc.

[0227] It is understandable that at least one of the sensing signal sending nodes and sensing signal receiving nodes in different sensing node groups is different, which can ensure that the transmission paths of the sensing signals of different sensing node groups during sensing are different, such as the transmission paths of the reflected signals are different, thereby ensuring the independence of each sensing data, and thus facilitating the acquisition of accurate sensing results. For example, assuming that there are three sensing node groups, namely sensing node group 1 to sensing node group 3, and the reflected signal path of one sensing node group 1 is in a complex channel area, the sensing data corresponding to the sensing node group 1 obtained is significantly different from the sensing data corresponding to the other two sensing node groups (sensing node group 2 and sensing node group 3), and the sensing data corresponding to sensing node group 2 and sensing node group 3 are almost the same. In this case, it can be determined that the sensing data corresponding to sensing node group 1 is biased, and then the sensing result can be obtained based on the sensing data corresponding to sensing node group 2 and sensing node group 3.

[0228] It should be noted that the embodiment of the present application does not limit the number of sensing node groups. Exemplarily, the number of sensing node groups corresponding to different business types can be pre-configured in advance, or can be specified by the sensing demand party in the sensing request according to actual needs, or the number of sensing node groups can be unrestricted. Exemplarily, when the number of sensing node groups corresponding to different business types is pre-configured, for sensing services with higher requirements for the accuracy of sensing results, the number of pre-configured sensing node groups can be larger (such as 5 or more than 5), and for sensing services with relatively low requirements for the accuracy of sensing results, the number of pre-configured sensing node groups can be smaller (such as 2-4). Exemplarily, from the perspective of the demand for sensing results, if it is only necessary to check whether the sensing data or sensing results are wrong, the number of sensing node groups can be 2. In this case, if the sensing data corresponding to the two sensing node groups differ too much or the sensing results obtained based on the sensing data differ too much, such as greater than the first threshold, it can be determined that there is erroneous sensing data or the sensing results in the two sensing data are unreliable. If it is necessary to exclude biased perception data, the number of perception node groups can be 3, 4, 5, or more. In this way, the perception data corresponding to each perception node group can be compared, and the data corresponding to the perception node group with the largest difference can be determined as erroneous perception data. Without limiting the number of perception node groups, the SF can select some or all of the perception nodes from all perception nodes that meet the conditions to form a perception node group. As another example, the SF can select some or all of the perception nodes from all perception nodes that can cover the perception area to form a perception node group. The above number of perception node groups is only an example and should not constitute a limitation. For example, the number of perception node groups may be adjusted based on actual conditions.

[0229] It should be understood that, in the case where the number of perception node groups is specified in the perception request by the perception demand party according to actual needs, the perception request may additionally carry a perception node group number parameter to indicate the required number of perception node groups. Optionally, the redundant perception indication may exist in the form of a perception node group number parameter, that is, when the perception node group number parameter is included in the perception request, it may implicitly indicate that a redundant perception method needs to be used. At this time, the number of perception node groups indicated by the perception node group number parameter is greater than or equal to 2. When the perception node group number parameter is not included in the perception request, it may implicitly indicate that a redundant perception method does not need to be used, that is, it implicitly indicates that a non-redundant perception method is used. Alternatively, when the number of perception node groups indicated by the perception node group number parameter is 1, it may implicitly indicate that a non-redundant perception method is used. When the number of perception node groups indicated by the perception node group number parameter is greater than or equal to 2 (such as 3, 4, 5), it may implicitly indicate that a redundant perception method needs to be used.

[0230] In some possible implementations, when determining the perception node group, SF may consider the information carried in the first perception service request, such as perception requirements, perception area, etc. That is, SF may determine the perception node group based on the information carried in the first perception service request (such as perception requirements, perception area, etc.). For example, when determining the perception node group, SF may determine it from the perception nodes that can cover the corresponding perception area. Moreover, each perception node group needs to be able to meet the corresponding perception requirements, that is, the perception results obtained based on the perception data corresponding to each perception node group can meet the corresponding perception requirements, that is, when determining the perception node group, the capabilities of the perception nodes (such as transceiver capabilities, bandwidth capabilities, etc.) need to be considered. In addition, when determining the perception node group, SF may also consider the priority of the corresponding perception node and may give priority to perception nodes with higher priorities. Of course, the method of determining the perception node group here is only an exemplary explanation and should not constitute a limitation.

[0231] It should be noted that the embodiments of the present application do not limit the perception modes corresponding to the multiple perception node groups determined by the SF. It can be a single perception mode or multiple perception modes. In some possible implementations, the SF can first determine the perception mode and then determine the perception nodes that meet the corresponding perception mode to form a perception node group.

[0232] Optionally, the perception control request includes a perception task identifier (ID). Specifically, in one possible implementation, for each perception node group for the first perception service request, the SF may assign a perception task ID to each perception node group or the perception control request corresponding to each perception node group, and these perception task IDs correspond to the first perception service or the first perception service request, so that the SF can later determine the perception data corresponding to the first perception service or the first perception service request from the received perception data. Among them, the perception task ID corresponding to each perception node group may be different, so that the perception data from different perception node groups can be distinguished. At this time, the SF can maintain the correspondence between multiple different perception task IDs and the first perception service or the first perception service request. In another possible implementation, for each perception node group for the first perception service request, the SF may assign the same perception task ID to each perception node group or the perception control request corresponding to each perception node group, and this perception task ID corresponds to the first perception service or the first perception service request, so that the SF can later determine the perception data corresponding to the first perception service or the first perception service request from the received perception data. It should be understood that the allocation of perception task IDs here is only an exemplary description, and the embodiments of the present application are not limited to this. For example, in some possible implementations, a different sensing task ID may be assigned to each sensing control request.

[0233] Optionally, the perception control request also includes configuration information. Specifically, in order to enable the perception signal sending node and the perception signal receiving node in each perception node group to cooperate to complete the perception process and obtain perception data, the perception control request may also include relevant configuration information, such as the time domain resources, frequency domain resources, transmission time, and transceiver antenna configuration (such as 2T4R, 8T8R, etc.) for the perception signal transmission. Part of the configuration information can be determined based on the perception service requirements. For example, the transceiver antenna configuration can be determined based on the perception resolution. Part of the configuration information can be determined based on internal algorithms, such as scheduling time and frequency resources through a resource scheduling algorithm.

[0234] It should be understood that after the perception signal receiving nodes and the perception signal sending nodes in the multiple perception node groups receive the corresponding perception control requests, the corresponding perception process can be executed so that the perception signal receiving nodes can obtain the perception data. For example, FIG4 takes n perception node groups as an example, as shown in 402a, 402b, and 402c, and the SF can respectively send perception control requests to the perception signal receiving node 1, the perception signal receiving node 2, ..., and the perception signal receiving node n, which can respectively carry the perception task ID_1, the perception task ID_2, ..., and the perception task ID_n. Of course, the SF can also respectively send perception control requests to the corresponding perception signal sending node 1, the perception signal sending node 2, ..., and the perception signal sending node n, which can also respectively carry the perception task ID_1, the perception task ID_2, ..., and the perception task ID_n, which is not shown in FIG4. Perception signal sending node 1, perception signal sending node 2, ..., perception signal sending node n can send perception signals based on corresponding perception control requests, and perception signal receiving node 1, perception signal receiving node 2, ..., perception signal receiving node n can respectively receive corresponding reflected signals to obtain perception data. Where n is an integer greater than or equal to 2, perception signal sending node 1 and perception signal receiving node 1 belong to perception node group 1, perception signal sending node 2 and perception signal receiving node 2 belong to perception node group 2, and perception signal sending node n and perception signal receiving node n belong to perception node group n. It should be noted that the perception signal sending node and perception signal receiving node in a perception node group can be the same perception node or different perception nodes.

[0235] 403. SF obtains the perception data corresponding to the first perception service from the perception signal receiving nodes in the multiple perception node groups.

[0236] The SF may obtain the perception data corresponding to the first perception service from the perception signal receiving nodes in the plurality of perception node groups. Exemplarily, after the perception signal receiving nodes in the plurality of perception node groups obtain the perception data, the perception signal receiving nodes in the plurality of perception node groups may each send a perception control response to the SF, where the perception control response includes the perception data corresponding to the first perception service. Accordingly, the SF may each receive the perception control response from the perception signal receiving nodes in the plurality of perception node groups.

[0237] Among them, the perception data corresponding to the first perception service may include a reflected signal (such as a reflected signal, a digital signal after the reflected signal is converted from analog to digital, etc.), or may include data related to the reflected signal, or may be data determined based on the reflected signal, without limitation.

[0238] In the case where the perception control request includes the corresponding perception task ID, the perception control response sent by the perception signal receiving node may also include the corresponding perception task ID, and the SF may determine that the perception data in the corresponding perception control response is the first perception service or the perception data corresponding to the first perception service request based on the perception task ID in the perception control response. Optionally, the SF may determine that the perception data in the corresponding perception control response is the perception data corresponding to the first perception service or the first perception service request based on the perception task ID in the perception control response and the correspondence between the perception task ID and the first perception service or the first perception service request. That is to say, after the SF receives multiple perception data from the perception signal receiving nodes in the multiple perception node groups and the perception task IDs corresponding to the multiple perception data, it may determine that the multiple perception data is the perception data corresponding to the first perception service or the first perception service request based on the perception task IDs corresponding to the multiple perception data. For example, as shown in 403a, 403b, and 403c in Figure 4, SF can respectively receive perception control responses from perception signal receiving node 1, perception signal receiving node 2, ..., and perception signal receiving node n, which can respectively carry perception task ID_1, perception task ID_2, ..., and perception task ID_n. Based on perception task ID_1, perception task ID_2, ..., and perception task ID_n, SF can determine that the corresponding perception data is the perception data corresponding to the first perception service.

[0239] In some possible implementations, the communication method shown in FIG. 4 may further include step 404 and step 405 .

[0240] 404.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0241] After the SF obtains multiple perception data corresponding to the first perception service, it can obtain a first perception result based on the multiple perception data corresponding to the first perception service.

[0242] In the embodiment of the present application, based on the multiple perception data corresponding to the first perception service, it can be checked whether there is a deviation in the perception data or the perception result, and further, the perception data with deviation can be excluded.

[0243] Exemplarily, in a possible implementation, SF may exclude the deviation perception data from the multiple perception data corresponding to the first perception service to obtain target perception data, where the target perception data is the perception data other than the deviation perception data in the multiple perception data. For example, SF may compare the multiple perception data corresponding to the first perception service. If most (such as more than half) of the perception data are almost the same, and a small portion (such as less than half) of the perception data are significantly different from the majority of the data, then the small portion of data may be determined as deviation perception data and may be ignored. For another example, SF may obtain a perception result based on each of the multiple perception data corresponding to the first perception service, and then compare the multiple perception results. If most (such as more than half) of the perception results are almost the same, and a small portion (such as less than half) of the perception results are significantly different from the majority of the data, then the perception data corresponding to the small portion of the perception results may be determined as deviation perception data and may be ignored. Deviation perception data may also be understood as erroneous / incorrect perception data, or perception data that deviates significantly from the actual situation.

[0244] After obtaining the target perception data, SF can obtain a first perception result based on the target perception data. Specifically, SF can obtain the first perception result based on one perception data in the target perception data, or it can obtain the first perception result based on multiple perception data in the target perception data, such as by comprehensively processing multiple perception data through a specific algorithm to obtain a more accurate perception result. Exemplarily, a perception result can be obtained based on each perception data in the target perception data, and then the multiple perception results obtained can be averaged, so as to ensure the accuracy of the perception result. It should be understood that the process of obtaining the first perception result based on the target perception data may include various processes such as feature extraction and feature fusion. The embodiment of the present application does not limit the specific process of obtaining the first perception result based on the target perception data.

[0245] Optionally, the SF may record relevant information about the sensing node groups performing the sensing service, including information about the sensing signal sending nodes and sensing signal receiving nodes in each sensing node group, as well as the corresponding relationship between the sensing signal sending nodes and sensing signal receiving nodes. Information about a sensing node may include, but is not limited to, the identification and location of the sensing node. Furthermore, based on the acquired deviation sensing data, the SF may record relevant information about the sensing node group that provided the deviation sensing data.

[0246] It should be noted that, in some possible implementations, other network elements may also obtain the first perception result based on multiple perception data corresponding to the first perception service, and this embodiment of the present application does not limit this.

[0247] 405. SF sends the first perception result to the first network element.

[0248] After obtaining the first perception result, the SF may send the first perception result to the first network element, or the SF may open the first perception result through the NEF. Accordingly, the first network element may obtain the first perception result from the NEF.

[0249] For ease of understanding, various possible combinations of situations are exemplified below through Examples 1 to 10, wherein relevant descriptions can refer to the relevant descriptions in the method embodiment shown in FIG4 above.

[0250] [Example 1]

[0251] In the case of the first embodiment, a redundant sensing indication needs to be carried in the sensing request to trigger redundant sensing, but no redundant sensing authorization check is required. Therefore, if the UE requires redundant sensing, the redundant sensing indication can be carried in the sensing request. Conversely, if the UE does not require redundant sensing, the redundant sensing indication can be omitted from the sensing request. The following mainly uses the case of carrying redundant sensing as an example for explanation.

[0252] Please refer to Figure 5, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 5, the method may include but is not limited to the following steps:

[0253] 501. The terminal device sends a first perception service request to the SF, where the first perception service request is used to request a first perception service. The first perception service request includes a redundant perception indication, where the redundant perception indication is used to indicate acquisition of multiple perception data corresponding to the first perception service.

[0254] Exemplarily, when there is a need for redundant perception, the terminal device may send a first perception service request to the SF. Accordingly, the SF may receive the first perception service request from the terminal device. Moreover, in order to execute the first perception service by means of redundant perception, the terminal device may carry a redundant perception indication in the first perception service request, which may be understood as a redundant perception indication of the first perception service. Among them, the indication of obtaining multiple perception data corresponding to the first perception service may also be understood as an indication of executing the first perception service by means of / adopting redundant perception, which will not be elaborated herein.

[0255] Optionally, the first sensing service request may further include one or more of the following: sensing service type, sensing service requirement, sensing area, and terminal device identifier. For descriptions of sensing service type, sensing service requirement, sensing area, and terminal device identifier, reference may be made to the relevant description in step 401 above.

[0256] 502. SF sends a second perception authorization request to UDM based on the first perception service request, where the second perception authorization request is used to request an authorization check for the first perception service.

[0257] After receiving the first perception service request from the terminal device, the SF may send a second perception authorization request to the UDM based on the first perception service request. Accordingly, the UDM may receive the second perception authorization request from the SF. In some possible implementations, the second perception authorization request may include information in the first perception service request and / or other information obtained based on the information in the first perception service request.

[0258] Optionally, the second perception authorization request may include one or more of the following: perception service type, perception area, and identifier of the terminal device.

[0259] Among them, since the internal area information and the external area information may be different, therefore, when the first perception service request carries the external area information, the SF can convert the external area information carried in the first perception service request into the internal area information, and then use the internal area information. For example, the perception area in the second perception authorization request can be the internal area information obtained by conversion. Of course, in other possible implementations, the conversion from external area information to internal area information can also be performed by other network elements.

[0260] 503. UDM performs authorization check on the first perception service based on the second perception authorization request.

[0261] After the UDM receives the second perception authorization request from the SF, it can perform an authorization check on the first perception service based on the second perception authorization request. Specifically, the UDM can obtain the perception authorization configuration information related to the second perception authorization request, such as the perception authorization configuration information configured in the UDM in advance, and then perform an authorization check on the first perception service based on the second perception authorization request and the perception authorization configuration information.

[0262] Exemplarily, the sensing authorization configuration information may include one or more of the sensing service type allowed for sensing, the sensing area allowed for sensing, the terminal device identifier allowed for sensing, the time allowed for sensing, and the like.

[0263] It should be noted that the authorization check for the first perception service here does not include the authorization check for redundant perception. For example, it is possible to only check the perception authority of the initiator of the perception request (such as a terminal device) to see whether it has the authority to initiate the perception request. Similarly, the perception authorization configuration information here is also different from the redundant perception configuration information described below. The perception authorization configuration information here is mainly used to perform authorization checks on the first perception service that do not include redundant perception, while the redundant perception configuration information is mainly used to perform authorization checks on the redundant perception of the first perception service. In order to facilitate the distinction from the redundant perception configuration information described below, the perception authorization configuration information here can be referred to as non-redundant perception configuration information.

[0264] 504. The UDM sends a second authorization response to the SF, where the second authorization response is used to indicate that the first perception service is authorized.

[0265] When the UDM determines that the first awareness service is authorized based on the second awareness authorization request, the UDM may send a second authorization response to the SF. Correspondingly, the SF may receive the second authorization response from the UDM.

[0266] Optionally, the second authorization response may include second authorization indication information, where the second authorization indication information is used to indicate that the first perception service is authorized, that is, to indicate that the first service authorization is passed.

[0267] It should be noted that the above steps 502-504 are optional. In some possible implementations, steps 502-504 may not be performed. In this case, step 505 may be performed directly after step 501. In other words, after receiving the first perception service request from the terminal device, the SF may directly perform step 505.

[0268] 505.SF determines multiple perception node groups based on the redundant perception indication of the first perception service, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0269] SF can determine that redundant perception is required for perception based on the redundant perception indication in the first perception service request. Among them, there are multiple possible situations in which SF determines multiple perception node groups based on the redundant perception indication of the first perception service. For example, one situation may be that after SF receives the first perception service request from the terminal device, it directly determines multiple perception node groups based on the redundant perception indication in the first perception service request. For another example, one situation may be that after SF receives the second authorization response from the UDM, it determines multiple perception node groups based on the redundant perception indication in the first perception service request, that is, when the first perception service is authorized, it determines multiple perception node groups based on the redundant perception indication in the first perception service request.

[0270] For the related operations of SF determining the perception node group, please refer to the related description in the above step 402.

[0271] It should be understood that, in the case where an authorization check is not required for the first perception service, if the first perception service request does not carry a redundant perception indication, then the SF can perform the first perception service in a non-redundant perception manner. In the case where an authorization check is required for the first perception service, if the first perception service request does not carry a redundant perception indication and the first perception service is authorized, then the SF can perform the first perception service in a non-redundant perception manner. If the first perception service request carries / does not carry a redundant perception indication and the first perception service is not authorized, then the SF can reject the first perception service request.

[0272] 506. SF sends a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0273] After determining the multiple sensing node groups, the SF may send a sensing control request to each of the sensing signal receiving nodes in the multiple sensing node groups, where the sensing control request is used to request sensing data corresponding to the first sensing service. Accordingly, the sensing signal receiving nodes in the multiple sensing node groups may each receive the sensing control request from the SF.

[0274] In one possible implementation, the SF may send a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups through an intermediate network element (such as an AMF). Accordingly, the SF may also send a perception control request to each of the perception signal sending nodes in the plurality of perception node groups through an intermediate network element (such as an AMF). In other words, communication between the SF and the terminal device or access network device may be performed through the AMF.

[0275] 507. SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, where the perception control responses include perception data corresponding to the first perception service.

[0276] 508.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0277] 509.SF sends the first perception result to the terminal device.

[0278] After obtaining the first perception result, the SF may send the first perception result to the terminal device, or the SF may open the first perception result through the NEF.

[0279] The principles of steps 506 to 509 are similar to those of steps 402 to 405 above. Please refer to the relevant descriptions of steps 402 to 405 above.

[0280] In some possible implementations, the terminal device in FIG5 may also be replaced by an AF, that is, the operations performed by the terminal device may also be performed by the AF.

[0281] [Example 2]

[0282] Similar to the first embodiment, in the case of the second embodiment, a redundant sensing indication needs to be carried in the sensing request to trigger redundant sensing, but no authorization check for redundant sensing is required. Therefore, if the AF needs to perform redundant sensing, a redundant sensing indication can be carried in the sensing request. Conversely, if the AF does not need to perform redundant sensing, a redundant sensing indication can be omitted from the sensing request. The following mainly uses the case of carrying redundant sensing as an example. Among them, the main difference between the first embodiment and the second embodiment is that the initiator of the sensing request is different, and the two can refer to each other.

[0283] Please refer to Figure 6, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 6, the method may include but is not limited to the following steps:

[0284] 601. AF sends a second perception service request to NEF, where the second perception service request is used to request the first perception service. The second perception service request includes a redundant perception indication, where the redundant perception indication is used to instruct acquisition of multiple perception data corresponding to the first perception service.

[0285] For example, when there is a need for redundant perception, the AF may send a second perception service request to the NEF. Accordingly, the NEF may receive the second perception service request from the AF. Furthermore, in order to execute the first perception service by means of redundant perception, the AF may carry a redundant perception indication in the second perception service request, which may be understood as a redundant perception indication of the first perception service. Indicating the acquisition of multiple perception data corresponding to the first perception service may also be understood as an indication to execute the first perception service by means of / adopting redundant perception, which will not be elaborated herein.

[0286] Optionally, the second perception service request may further include one or more of the following: a perception service type, a perception service requirement, a perception area, and an application function identifier (AFID). For descriptions of the perception service type, perception service requirement, and perception area, reference may be made to the relevant description in step 401 above. However, it should be understood that since the AF is external to the network, the perception area in the second perception service request may be external area information.

[0287] It should be understood that the information included in the above-mentioned second perception service request is only illustrative and should not be construed as limiting. Except for the redundant perception indication, the embodiments of this application do not specifically limit the information carried in the second perception service request. For example, in addition to the above-mentioned perception service type, perception service requirements, perception area, application function identifier, etc., the second perception service request may also include other information, such as the execution time of the first perception service, the duration of the first perception service, the execution frequency, etc.

[0288] 602. The NEF sends a second perception authorization request to the UDM based on the second perception service request, where the second perception authorization request is used to request an authorization check for the first perception service.

[0289] After receiving the second perception service request from the AF, the NEF may send a second perception authorization request to the UDM based on the second perception service request. Correspondingly, the UDM may receive the second perception authorization request from the AF.

[0290] The second perception authorization request may include one or more of the following: perception service type, perception area, and application function identifier.

[0291] Among them, since the second perception service request carries external area information, the NEF can convert the external area information carried in the second perception service request into internal area information, and then use the internal area information. For example, the perception area in the second perception authorization request and the first perception service request sent by the NEF can be the internal area information obtained after conversion.

[0292] 603. UDM performs authorization check on the first perception service based on the second perception authorization request.

[0293] 604. The UDM sends a second authorization response to the NEF, where the second authorization response is used to indicate that the first perception service is authorized.

[0294] If the UDM determines that the first perception service is authorized based on the second perception authorization request, the UDM may send a second authorization response to the NEF. Accordingly, the NEF may receive the second authorization response from the UDM. Optionally, the second authorization response may include second authorization indication information, where the second authorization indication information is used to indicate that the first perception service is authorized.

[0295] It should be noted that the above steps 602-604 are optional. In some possible implementations, steps 602-604 may not be performed. In this case, step 605 may be performed directly after step 601. That is, after receiving the second awareness service request from the AF, the NEF may directly perform step 605.

[0296] Steps 602-604 are similar to steps 502-504. Please refer to the relevant descriptions in the above steps 502-504 and will not be repeated here.

[0297] 605. The NEF sends a first perception service request to the SF, where the first perception service request is used to request a first perception service. The first perception service request includes a redundant perception indication, where the redundant perception indication is used to instruct the acquisition of multiple perception data corresponding to the first perception service.

[0298] There are many possible situations in which the NEF sends the first perception service request to the SF. For example, one situation may be that after receiving the second perception service request from the AF, the NEF directly sends the first perception service request to the SF based on the second perception service request. For another example, another situation may be that after receiving the second authorization response from the UDM, the NEF sends the first perception service request to the SF based on the second perception service request. That is, when the first perception service is authorized, the NEF sends the first perception service request to the SF based on the second perception service request.

[0299] It should be understood that the redundant perception indication in the first perception service request can be understood as the redundant perception indication of the first perception service.

[0300] Optionally, the first awareness service request may further include one or more of the following: awareness service type, awareness service requirement, awareness area, and application function identifier (AFID).

[0301] It is understandable that the first perception service request can be obtained based on the second perception service request. For example, the first perception service request can be the same as the second perception service request, except that the external information in the second perception service request is converted into internal information. In this case, the NEF is equivalent to simply forwarding the second perception service request.

[0302] 606.SF determines multiple perception node groups based on the redundant perception indication of the first perception service, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0303] After the SF receives the first perception service request from the NEF, it can determine that redundant perception needs to be used for perception based on the redundant perception indication in the first perception service request. Therefore, the SF can determine multiple perception node groups.

[0304] It should be understood that, in the case where an authorization check is not required for the first perception service, if the second perception service request does not carry a redundant perception indication, then the SF can subsequently perform the first perception service in a non-redundant perception manner. In the case where an authorization check is required for the first perception service, if the second perception service request does not carry a redundant perception indication and the first perception service is authorized, then the SF can subsequently perform the first perception service in a non-redundant perception manner. If the second perception service request carries / does not carry a redundant perception indication and the first perception service is not authorized, then the NEF can reject the second perception service request.

[0305] For the related operations of SF determining the perception node group, please refer to the related description in the above step 402.

[0306] It should also be understood that, in the case where an authorization check is required for the first perception service, the above is an authorization check initiated by NEF to UDM, but in other possible implementations of the present application, the authorization check may also be initiated by SF to UDM. In this case, steps 601 and 605 may be performed first, and then the authorization check is initiated by SF to UDM. Afterwards, SF may perform corresponding processing according to the authorization situation. For example, if the first perception service is authorized, SF may determine multiple perception node groups based on the redundant perception indication of the first perception service. If the first perception service is not authorized, SF may reject the first perception service request.

[0307] 607. SF sends a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0308] 608. SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, where the perception control responses include perception data corresponding to the first perception service.

[0309] 609.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0310] The principles of steps 607-609 are similar to those of steps 402-404 above, and reference may be made to the relevant descriptions of steps 402-404 above.

[0311] 610. SF sends the first perception result to AF through NEF.

[0312] After obtaining the first perception result, the SF can open the first perception result through the NEF. Correspondingly, the AF can obtain the first perception result from the NEF.

[0313] [Example 3]

[0314] In the case of Example 3, a redundant sensing indication needs to be carried in the sensing request to trigger redundant sensing, and an authorization check for redundant sensing needs to be performed through the UDM. Therefore, if the UE needs to perform redundant sensing, a redundant sensing indication can be carried in the sensing request, and redundant sensing can only be performed if redundant sensing is subsequently authorized. Conversely, if the UE does not need to perform redundant sensing, the redundant sensing indication can be omitted from the sensing request. The following mainly uses the case of carrying redundant sensing as an example for explanation.

[0315] Please refer to Figure 7, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 7, the method may include but is not limited to the following steps:

[0316] 701. The terminal device sends a first perception service request to the SF, where the first perception service request is used to request a first perception service. The first perception service request includes a redundant perception indication, where the redundant perception indication is used to indicate acquisition of multiple perception data corresponding to the first perception service.

[0317] Among them, the instruction to obtain multiple perception data corresponding to the first perception service can also be understood as an instruction to execute the first perception service through / adopting redundant perception, which will not be repeated below.

[0318] Step 701 is similar to step 501 , and reference may be made to the relevant description in step 501 , which will not be repeated here.

[0319] 702. SF sends a first perception authorization request to UDM based on the first perception service request, where the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service.

[0320] After the SF receives the first perception service request from the terminal device, it can determine that redundant perception is required for perception based on the redundant perception indication in the first perception service request, and can send a first perception authorization request to the UDM. Accordingly, the UDM can receive the first perception authorization request from the SF. In some possible implementations, the first perception authorization request may include information in the first perception service request and / or other information obtained based on the information in the first perception service request.

[0321] It should be understood that the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service. It can also be understood as a request for an authorization check for redundant perception of the first perception service, or a request for an authorization check for executing the first perception service through / adopting redundant perception.

[0322] Optionally, the first perception authorization request may include one or more of the following: perception service type, perception area, terminal device identifier, redundant perception indication. It should be understood that when the first perception authorization request includes a redundant perception indication, the redundant perception indication itself is not used for authorization check, but is used to inform the UDM that a redundant perception authorization check is required. On the contrary, if the first perception authorization request does not include a redundant perception indication, it indicates that a redundant perception authorization check is not required, and other authorization checks can be performed (such as the authorization check for the first perception service shown in the above-mentioned embodiment one and embodiment two).

[0323] Among them, since the internal area information and the external area information may be different, therefore, when the perception area carried in the first perception service request is external area information, the SF can convert the external area information carried in the first perception service request into internal area information, and then use the internal area information. For example, the perception area in the first perception authorization request can be the internal area information obtained through conversion. Of course, in other possible implementations, other network elements can also perform the conversion from external area information to internal area information.

[0324] 703. Based on the first perception authorization request and the first redundant perception configuration information, the UDM performs an authorization check on obtaining multiple perception data corresponding to the first perception service.

[0325] After the UDM receives the first perception authorization request from the SF, it can perform an authorization check on the multiple perception data corresponding to the first perception service based on the first perception authorization request and the first redundant perception configuration information. It should be noted that in the embodiment of the present application, authorization and authorization check have the same meaning.

[0326] Optionally, the first redundant perception configuration information includes one or more of the following: the perception service type allowed for redundant perception, the perception area allowed for redundant perception, the time allowed for redundant perception, the identifier of the terminal device allowed for redundant perception, and the application function identifier (AFID) allowed for redundant perception.

[0327] For the description of the redundancy awareness configuration information and the authorization of redundancy awareness, please refer to the relevant description in the above step 402.

[0328] 704. The UDM sends a first authorization response to the SF, where the first authorization response is used to indicate that the acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0329] When the UDM determines that the acquisition of the plurality of sensing data corresponding to the first sensing service is authorized based on the first sensing authorization request and the first redundant sensing configuration information, the UDM may send a first authorization response to the SF. Accordingly, the SF may receive the first authorization response from the UDM.

[0330] Optionally, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that obtaining the multiple sensing data corresponding to the first sensing service is authorized. Exemplarily, the first authorization indication information may be a redundant sensing indication.

[0331] In an embodiment of the present application, when the acquisition of multiple perception data corresponding to the first perception service is not authorized, the UDM includes multiple possible processing situations. One situation is: the UDM directly sends an authorization response to the SF, and the authorization response includes a first indication information, and the first indication information is used to indicate that the first perception service is performed in a non-redundant perception manner, or is used to indicate that the first perception service (request) is rejected. Another situation is: the UDM directly sends an authorization response to the SF, which does not include the first authorization indication information, and the SF determines that the first perception service is performed in a non-redundant perception manner based on the fact that the authorization response information does not include the first authorization indication information. Another situation is: the UDM continues to perform an authorization check on the first perception service (refer to the relevant descriptions in Example 1 and Example 2). When the first perception service is authorized, the UDM can send an authorization response to the SF, and the authorization response includes a first indication information, and the first indication information is used to indicate that the first perception service is performed in a non-redundant perception manner. When the first perception service is not authorized, the UDM can send an authorization response to the SF, and the authorization response includes a second indication information, and the second indication information is used to indicate that the first perception service (request) is rejected. The second situation mentioned above is equivalent to first performing an authorization check on the acquisition of multiple perception data corresponding to the first perception service, and then performing an authorization check on the first perception service when the acquisition of multiple perception data corresponding to the first perception service is not authorized. In other possible implementations of the present application, the authorization of the first perception service may be a prerequisite for the authorization to obtain multiple perception data corresponding to the first perception service, that is, it is necessary to first perform authorization for the first perception service, and only when the first perception service is authorized can further authorization be performed to obtain multiple perception data corresponding to the first perception service, and when the first perception service is not authorized, the first perception service request can be directly rejected. The specific authorization process is related to the relevant implementation method, and the embodiments of the present application do not limit this. The embodiments of the present application mainly focus on the authorization of obtaining multiple perception data corresponding to the first perception service.

[0332] 705. When obtaining multiple perception data corresponding to the first perception service is authorized, the SF determines multiple perception node groups, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0333] After receiving the first authorization response from the UDM, the SF can determine that the acquisition of the plurality of sensing data corresponding to the first sensing service is authorized, and then the SF can determine a plurality of sensing node groups. For the relevant operations of the SF determining the sensing node groups, please refer to the relevant description in the above step 402.

[0334] Optionally, the SF may determine that acquisition of the multiple perception data corresponding to the first perception service is authorized based on the first authorization indication information in the first authorization response.

[0335] It is understandable that, in the case where the first perception service request does not carry a redundant perception indication, the UDM may also perform / not perform an authorization check on the first perception service (refer to the relevant descriptions in Example 1 and Example 2). In the case where there is no need to perform an authorization check on the first perception service, if the first perception service request does not carry a redundant perception indication, then the SF may directly use a non-redundant perception method to execute the first perception service. In the case where an authorization check is required for the first perception service, if the first perception service request does not carry a redundant perception indication, and the first perception service is authorized, then the SF may use a non-redundant perception method to execute the first perception service. If the first perception service request does not carry a redundant perception indication, and the first perception service is not authorized, then the SF may reject the first perception service request.

[0336] 706. SF sends a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0337] 707. SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, where the perception control responses include perception data corresponding to the first perception service.

[0338] 708.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0339] The principles of steps 706-708 are similar to those of steps 402-404 above, and reference may be made to the relevant descriptions of steps 402-404 above.

[0340] 709.SF sends the first perception result to the terminal device.

[0341] In some possible implementations, the terminal device in FIG7 may also be replaced by an AF, that is, the operations performed by the terminal device may also be performed by the AF.

[0342] [Example 4]

[0343] In the case of embodiment 4, it is necessary to carry a redundant perception indication in the perception request to trigger redundant perception, and it is necessary to perform an authorization check for redundant perception through the UDM. Therefore, if the AF needs to perform redundant perception, it can carry a redundant perception indication in the perception request, and redundant perception can only be performed when redundant perception is authorized later. Conversely, if the UE does not need to perform redundant perception, it is possible not to carry a redundant perception indication in the perception request. In addition, when the AF initiates a redundant perception request, there may be two situations that trigger redundant perception authorization, one is that the SF initiates an authorization request for redundant perception to the UDM (Figure 8), and the other is that the NEF initiates an authorization request for redundant perception to the UDM (Figure 9), which are exemplified below.

[0344] Please refer to Figure 8, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 8, the method may include but is not limited to the following steps:

[0345] 801. AF sends a second perception service request to NEF, where the second perception service request is used to request the first perception service. The second perception service request includes a redundant perception indication, where the redundant perception indication is used to instruct acquisition of multiple perception data corresponding to the first perception service.

[0346] Among them, the instruction to obtain multiple perception data corresponding to the first perception service can also be understood as an instruction to execute the first perception service through / adopting redundant perception, which will not be repeated below.

[0347] 802. The NEF sends a second perception authorization request to the UDM based on the second perception service request, where the second perception authorization request is used to request an authorization check for the first perception service.

[0348] 803. UDM performs authorization check on the first perception service based on the second perception authorization request.

[0349] 804. The UDM sends a second authorization response to the NEF, where the second authorization response is used to indicate that the first perception service is authorized.

[0350] It should be noted that the above steps 802-804 are optional. In some possible implementations, steps 802-804 may not be performed. In this case, step 805 may be performed directly after step 801. That is, after receiving the second awareness service request from the AF, the NEF may directly perform step 805.

[0351] 805. The NEF sends a first perception service request to the SF, where the first perception service request is used to request a first perception service. The first perception service request includes a redundant perception indication, where the redundant perception indication is used to instruct the acquisition of multiple perception data corresponding to the first perception service.

[0352] Steps 801-805 are similar to the above steps 601-605. You can refer to the relevant descriptions in the above steps 601-605, including the relevant descriptions of the second perception service request and the first perception service request.

[0353] 806. SF sends a first perception authorization request to UDM based on the first perception service request, where the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service.

[0354] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0355] 807. Based on the first perception authorization request and the first redundant perception configuration information, the UDM performs an authorization check on obtaining multiple perception data corresponding to the first perception service.

[0356] 808. The UDM sends a first authorization response to the SF, where the first authorization response is used to indicate that the acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0357] 809. When obtaining multiple perception data corresponding to the first perception service is authorized, the SF determines multiple perception node groups, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0358] 810. SF sends a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0359] 811. SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, where the perception control responses include perception data corresponding to the first perception service.

[0360] 812.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0361] Steps 806-812 are similar to the above steps 702-708, and reference may be made to the relevant description of the above steps 702-708.

[0362] 813. SF sends the first perception result to AF through NEF.

[0363] Please refer to Figure 9 again, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 9, the method may include but is not limited to the following steps:

[0364] 901. AF sends a second perception service request to NEF, where the second perception service request is used to request the first perception service. The second perception service request includes a redundant perception indication, where the redundant perception indication is used to instruct acquisition of multiple perception data corresponding to the first perception service.

[0365] Among them, the instruction to obtain multiple perception data corresponding to the first perception service can also be understood as an instruction to execute the first perception service through / adopting redundant perception, which will not be repeated below.

[0366] Step 901 is similar to the above step 601 , and reference may be made to the relevant description in the above step 601 .

[0367] 902. The NEF sends a first perception authorization request to the UDM based on the second perception service request, where the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service.

[0368] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0369] After the NEF receives the second perception service request from the AF, it can determine that redundant perception is required for perception based on the redundant perception indication in the second perception service request, and can send a first perception authorization request to the UDM. Accordingly, the UDM can receive the first perception authorization request from the NEF. In some possible implementations, the first perception authorization request may include information in the second perception service request and / or other information obtained based on the information in the second perception service request.

[0370] Optionally, the first perception authorization request may include one or more of the following: perception service type, perception area, application function identifier, redundant perception indication. It should be understood that when the first perception authorization request includes a redundant perception indication, the redundant perception indication itself is not used for authorization check, but is used to inform the UDM that a redundant perception authorization check is required. On the contrary, if the first perception authorization request does not include a redundant perception indication, it indicates that a redundant perception authorization check is not required, and other authorization checks can be performed (such as the authorization check for the first perception service shown in the above-mentioned embodiment one and embodiment two).

[0371] Among them, since the internal area information and the external area information may be different, therefore, when the perception area carried in the second perception service request is external area information, the NEF can convert the external area information carried in the second perception service request into internal area information, and then use the internal area information. For example, the perception area in the first perception authorization request can be the internal area information obtained by conversion. Of course, in other possible implementations, the conversion from external area information to internal area information can also be performed by other network elements.

[0372] 903. Based on the first perception authorization request and the first redundant perception configuration information, the UDM performs an authorization check on obtaining multiple perception data corresponding to the first perception service.

[0373] 904. The UDM sends a first authorization response to the SF, where the first authorization response is used to indicate that the acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0374] Steps 902-904 are similar to steps 702-704, and reference may be made to the relevant descriptions in steps 702-704.

[0375] In an embodiment of the present application, when the acquisition of multiple perception data corresponding to the first perception service is not authorized, the UDM includes multiple possible processing situations. One situation is: the UDM directly sends an authorization response to the NEF, and the authorization response includes a first indication information, and the first indication information is used to indicate that the first perception service is performed in a non-redundant perception manner, or is used to indicate that the first perception service (request) is rejected. Another situation is: the UDM continues to perform an authorization check on the first perception service (refer to the relevant descriptions in Example 1 and Example 2). When the first perception service is authorized, the UDM can send an authorization response to the NEF, and the authorization response includes a first indication information, and the first indication information is used to indicate that the first perception service is performed in a non-redundant perception manner. When the first perception service is not authorized, the UDM can send an authorization response to the NEF, and the authorization response includes a second indication information, and the second indication information is used to indicate that the first perception service (request) is rejected. The specific authorization process is related to the relevant implementation method, and the embodiment of the present application does not limit this.

[0376] 905. When the acquisition of multiple perception data corresponding to the first perception service is authorized, the NEF sends a first perception service request to the SF, where the first perception service request is used to request the first perception service, and the first perception service request includes a redundant perception indication, which is used to indicate the acquisition of multiple perception data corresponding to the first perception service.

[0377] After receiving the first authorization response from the UDM, the NEF may determine that the acquisition of the plurality of perception data corresponding to the first perception service is authorized, and then the NEF may send the first perception service request to the SF. Accordingly, the SF may receive the first perception service request from the NEF.

[0378] Exemplarily, the NEF may determine, based on the first authorization indication information in the first authorization response, that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0379] Optionally, the first awareness service request may further include one or more of the following: awareness service type, awareness service requirement, awareness area, and application function identifier (AFID).

[0380] It is understood that the first perception service request can be obtained based on the second perception service request. For example, the first perception service request can be the same as the second perception service request, except that the external information in the second perception service request is converted into internal information. Of course, the first perception service request can also include more or less information than the first perception service request, which is not limited here.

[0381] Step 905 is similar to step 605 , and reference may be made to the relevant description in step 605 .

[0382] 906.SF determines multiple perception node groups based on the redundant perception indication of the first perception service, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0383] After the SF receives the first perception service request from the NEF, it can determine that redundant perception needs to be used for perception based on the redundant perception indication in the first perception service request, and can determine multiple perception node groups.

[0384] In some possible implementations, the SF may require a redundancy awareness authorization check by default in the local policy. In this case, after the SF receives the first awareness service request from the NEF, it can initiate a redundancy awareness authorization request to the UDM. For details, please refer to the relevant description in the above steps 702-704.

[0385] 907.SF sends a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0386] 908. SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, where the perception control responses include perception data corresponding to the first perception service.

[0387] 909.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0388] Steps 906-909 are similar to the above steps 606-609, and reference may be made to the relevant description of the above steps 606-609.

[0389] 910. SF sends the first perception result to AF through NEF.

[0390] [Example 5]

[0391] In the case of Example 5, the terminal device does not need to carry a redundant perception indication in the perception request to trigger redundant perception. By default, each perception request is subjected to a redundant perception authorization check through UDM. If redundant perception is authorized, redundant perception can be performed. Conversely, if redundant perception is not authorized, redundant perception will not be performed. It can be understood that the main difference between Example 5 and Example 3 is that Example 3 is to trigger the authorization of redundant perception by actively carrying a redundant perception indication in the perception request according to actual needs by the terminal device, thereby triggering redundant perception, while Example 5 is to actively trigger the authorization of redundant perception by the core network element (NEF, SF, etc.), thereby triggering redundant perception. Therefore, Example 5 and Example 3 can refer to each other.

[0392] Please refer to Figure 10, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 10, the method may include but is not limited to the following steps:

[0393] 1001. The terminal device sends a first perception service request to the SF, where the first perception service request is used to request a first perception service.

[0394] For example, when a terminal device has a redundancy perception requirement, it may send a first perception service request to the SF. Correspondingly, the SF may receive the first perception service request from the terminal device.

[0395] Optionally, the first sensing service request may include one or more of the following: sensing service type, sensing service requirement, sensing area, and terminal device identifier. For detailed descriptions of the sensing service type, sensing service requirement, etc., please refer to the relevant description in step 401.

[0396] It should be understood that the information included in the above-mentioned first perception service request is merely illustrative and should not be construed as limiting. For example, in addition to the above-mentioned perception service type, perception service requirements, and perception area, the first perception service request may also include other information, such as the execution time of the first perception service, the duration of the first perception service, and the execution frequency.

[0397] 1002. SF sends a first perception authorization request to UDM based on the first perception service request, where the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service.

[0398] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0399] After receiving the first perception service request from the terminal device, the SF may send a first perception authorization request to the UDM based on the first perception service request. Accordingly, the UDM may receive the first perception authorization request from the SF. In some possible implementations, the first perception authorization request may include information in the first perception service request and / or other information obtained based on the information in the first perception service request.

[0400] Optionally, the first perception authorization request may include one or more of the following: perception service type, perception area, and identifier of the terminal device.

[0401] Optionally, the first perception authorization request may further include a redundant perception indication. Specifically, since in the fifth embodiment, a redundant perception authorization check is required for each perception request by default, the SF may carry a redundant perception indication in the authorization request sent to the UDM. The redundant perception indication itself is not used for authorization check, but is used to inform the UDM that a redundant perception authorization check is required.

[0402] Step 1002 is similar to step 702 , and reference may be made to the relevant description in step 702 .

[0403] 1003. Based on the first perception authorization request and the first redundant perception configuration information, the UDM performs an authorization check on obtaining multiple perception data corresponding to the first perception service.

[0404] After receiving the first perception authorization request from the SF, the UDM may perform an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception authorization request and the first redundant perception configuration information.

[0405] Step 1003 is similar to step 703 , and reference may be made to the relevant description in the above step 703 .

[0406] 1004. The UDM sends a first authorization response to the SF, where the first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

[0407] When the UDM determines that the acquisition of the plurality of sensing data corresponding to the first sensing service is authorized based on the first sensing authorization request and the first redundant sensing configuration information, the UDM may send a first authorization response to the SF. Accordingly, the SF may receive the first authorization response from the UDM.

[0408] Optionally, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that obtaining the multiple sensing data corresponding to the first sensing service is authorized. Exemplarily, the first authorization indication information may be a redundant sensing indication.

[0409] Step 1004 is similar to step 704 , and reference may be made to the relevant description in the above step 704 .

[0410] 1005. When the acquisition of multiple perception data corresponding to the first perception service is authorized, the SF determines multiple perception node groups based on the redundant perception indication of the first perception service, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0411] After receiving the first authorization response from the UDM, the SF can determine that the acquisition of the plurality of sensing data corresponding to the first sensing service is authorized based on the first authorization response, and can determine a plurality of sensing node groups. For the relevant operations of the SF in determining the sensing node groups, please refer to the relevant description in the above step 402.

[0412] Exemplarily, the NEF may determine, based on the first authorization indication information in the first authorization response, that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0413] 1006.SF sends a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0414] 1007. SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, where the perception control responses include perception data corresponding to the first perception service.

[0415] 1008.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0416] The principles of steps 1006-1008 are similar to those of steps 402-404 above, and reference may be made to the relevant descriptions of steps 402-404 above.

[0417] 1009.SF sends the first perception result to the terminal device.

[0418] In some possible implementations, the terminal device in FIG10 may also be replaced by an AF, that is, the operations performed by the terminal device may also be performed by the AF.

[0419] [Example 6]

[0420] In the case of Example 6, the AF does not need to carry a redundant perception indication in the perception request to trigger redundant perception. By default, each perception request is subject to a redundant perception authorization check through the UDM. If redundant perception is authorized, redundant perception can be performed. Conversely, if redundant perception is not authorized, redundant perception will not be performed. Moreover, in this way, there may be two situations in which redundant perception authorization is triggered. One is that the SF initiates a redundant perception authorization request to the UDM (Figure 11), and the other is that the NEF initiates a redundant perception authorization request to the UDM (Figure 12), which are explained below. It can be understood that the main difference between Example 6 and Example 4 is that Example 4 is that Example 4 is that the AF actively carries a redundant perception indication in the perception request according to actual needs to trigger the authorization of redundant perception, thereby triggering redundant perception, while Example 6 is that the core network element (NEF, SF, etc.) actively triggers the authorization of redundant perception, thereby triggering redundant perception. Therefore, Example 6 and Example 4 can refer to each other.

[0421] Please refer to Figure 11, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 11, the method may include but is not limited to the following steps:

[0422] 1101. AF sends a second perception service request to NEF, where the second perception service request is used to request the first perception service.

[0423] For example, when there is a redundancy awareness requirement, the AF may send a second awareness service request to the NEF. Correspondingly, the NEF may receive the second awareness service request from the AF.

[0424] Optionally, the second awareness service request may include one or more of the following: awareness service type, awareness service requirement, awareness area, and application function identifier (AFID). For detailed descriptions of the awareness service type, awareness service requirement, etc., please refer to the relevant description in step 501.

[0425] 1102. The NEF sends a second perception authorization request to the UDM based on the second perception service request, where the second perception authorization request is used to request an authorization check for the first perception service.

[0426] 1103. UDM performs authorization check on the first perception service based on the second perception authorization request.

[0427] 1104. UDM sends a second authorization response to NEF, where the second authorization response is used to indicate that the first perception service is authorized.

[0428] It should be noted that the above steps 1102-1104 are optional. In some possible implementations, steps 1102-1104 may not be performed. In this case, step 1105 may be performed directly after step 1101. That is, after receiving the second awareness service request from the AF, the NEF may directly perform step 1105.

[0429] Steps 1102-1104 are similar to the above steps 602-604, and reference may be made to the relevant descriptions in the above steps 602-604.

[0430] 1105. The NEF sends a first perception service request to the SF, where the first perception service request is used to request a first perception service.

[0431] Optionally, the first sensing service request may include one or more of the following: sensing service type, sensing service requirement, sensing area, and application function identifier. For detailed descriptions of the sensing service type, sensing service requirement, etc., please refer to the relevant description in step 401.

[0432] Optionally, the first perception service request may further include a redundant perception indication. Specifically, since in the sixth embodiment, a redundant perception authorization check is required for each perception request by default, the NEF may carry a redundant perception indication in the perception request sent to the SF. The redundant perception indication is used to instruct the acquisition of multiple perception data corresponding to the first perception service, and may also be understood as an indication to the SF that a redundant perception authorization check is required to determine whether to perform perception in a redundant perception manner.

[0433] Step 1105 is similar to step 605 , and reference may be made to the relevant description in step 605 .

[0434] 1106. SF sends a first perception authorization request to UDM based on the first perception service request. The first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service.

[0435] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0436] After the SF receives the first perception service request from the NEF, it may send a first perception authorization request to the UDM based on the first perception service request. Correspondingly, the UDM may receive the first perception authorization request from the SF. For example, the SF may determine that redundant perception is required for perception based on the redundant perception indication in the first perception service request. Therefore, the SF may first send a first perception authorization request to the UDM to perform an authorization check for redundant perception.

[0437] In some possible implementations, the first awareness authorization request may include information in the first awareness service request and / or other information obtained based on the information in the first awareness service request.

[0438] Optionally, the first perception authorization request may include one or more of the following: perception service type, perception area, and application function identifier.

[0439] Optionally, the first perception authorization request may further include a redundancy perception indication, which is not used for authorization check itself, but is used to inform the UDM that a redundancy perception authorization check is required.

[0440] Step 1106 is similar to step 702 , and reference may be made to the relevant description in step 702 .

[0441] 1107. Based on the first perception authorization request and the first redundant perception configuration information, the UDM performs an authorization check on obtaining multiple perception data corresponding to the first perception service.

[0442] Step 1107 is similar to step 703 , and reference may be made to the relevant description in the above step 703 .

[0443] 1108. The UDM sends a first authorization response to the SF, where the first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

[0444] Optionally, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that obtaining the multiple sensing data corresponding to the first sensing service is authorized. Exemplarily, the first authorization indication information may be a redundant sensing indication.

[0445] Step 1108 is similar to step 704 , and reference may be made to the relevant description in step 704 .

[0446] 1109. When the acquisition of multiple perception data corresponding to the first perception service is authorized, the SF determines multiple perception node groups, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0447] After receiving the first authorization response from the UDM, the SF may determine, based on the first authorization response, that the acquisition of the plurality of perception data corresponding to the first perception service is authorized, and may determine a plurality of perception node groups. For information on the SF's operation of determining the perception node groups, please refer to the description of step 402 above. For example, the NEF may determine, based on the first authorization indication information in the first authorization response, that the acquisition of the plurality of perception data corresponding to the first perception service is authorized.

[0448] 1110. SF sends a perception control request to each perception signal receiving node in a plurality of perception node groups, where the perception control request is used to request perception data corresponding to the first perception service.

[0449] 1111.SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, and the perception control responses include perception data corresponding to the first perception service.

[0450] 1112.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0451] The principles of steps 1110-1112 are similar to those of steps 402-404 above, and reference may be made to the relevant descriptions of steps 402-404 above.

[0452] 1113. SF sends the first perception result to AF through NEF.

[0453] Please refer to Figure 12 again, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 12, the method may include but is not limited to the following steps:

[0454] 1201. AF sends a second perception service request to NEF, where the second perception service request is used to request the first perception service.

[0455] Step 1201 is similar to the above step 1101 , and reference may be made to the relevant description in the above step 1101 .

[0456] 1202. NEF sends a first perception authorization request to UDM based on the second perception service request, where the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service.

[0457] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0458] After receiving the second perception service request from the AF, the NEF may send a first perception authorization request to the UDM based on the second perception service request. Accordingly, the UDM may receive the first perception authorization request from the SF. In some possible implementations, the first perception authorization request may include information in the second perception service request and / or other information obtained based on the information in the second perception service request.

[0459] Optionally, the first perception authorization request may include one or more of the following: perception service type, perception area, and application function identifier.

[0460] Optionally, the first perception authorization request may further include a redundant perception indication. Specifically, since in the fifth embodiment, a redundant perception authorization check is required for each perception request by default, the NEF may carry a redundant perception indication in the authorization request sent to the UDM. The redundant perception indication itself is not used for authorization check, but is used to inform the UDM that a redundant perception authorization check is required.

[0461] Step 1202 is similar to step 902 , and reference may be made to the relevant description in step 902 .

[0462] 1203. Based on the first perception authorization request and the first redundant perception configuration information, the UDM performs an authorization check on obtaining multiple perception data corresponding to the first perception service.

[0463] 1204. The UDM sends a first authorization response to the NEF, where the first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

[0464] When the UDM determines that the acquisition of the plurality of sensing data corresponding to the first sensing service is authorized based on the first sensing authorization request and the first redundant sensing configuration information, the UDM may send a first authorization response to the NEF. Accordingly, the NEF may receive the first authorization response from the UDM.

[0465] Optionally, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that obtaining the multiple sensing data corresponding to the first sensing service is authorized. Exemplarily, the first authorization indication information may be a redundant sensing indication.

[0466] Steps 1202-1204 are similar to steps 902-904, and reference may be made to the relevant descriptions in the above steps 902-904.

[0467] 1205. When the acquisition of multiple perception data corresponding to the first perception service is authorized, the NEF sends a first perception service request to the SF, where the first perception service request is used to request the first perception service, and the first perception service request includes a redundant perception indication, which is used to indicate the acquisition of multiple perception data corresponding to the first perception service.

[0468] After receiving the first authorization response from the UDM, the NEF may determine that the acquisition of the plurality of perception data corresponding to the first perception service is authorized, and then the NEF may send the first perception service request to the SF. Accordingly, the SF may receive the first perception service request from the NEF.

[0469] Exemplarily, the NEF may determine, based on the first authorization indication information in the first authorization response, that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0470] It should be understood that when the acquisition of multiple perception data corresponding to the first perception service is not authorized, if the UDM carries the first indication information in the authorization response, the first perception service request sent by the NEF to the SF does not include a redundant perception indication, and the first indication information is used to indicate that the first perception service is performed in a non-redundant perception manner.

[0471] Step 1205 is similar to step 605 , and reference may be made to the relevant description in the above step 605 .

[0472] 1206.SF determines multiple perception node groups based on the redundant perception indication of the first perception service, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0473] After the SF receives the first perception service request from the NEF, it can determine that redundant perception needs to be used for perception based on the redundant perception indication in the first perception service request, and can determine multiple perception node groups.

[0474] In some possible implementations, the SF may require a redundancy awareness authorization check by default in the local policy. In this case, after the SF receives the first awareness service request from the NEF, it can initiate a redundancy awareness authorization request to the UDM. For details, please refer to the relevant description in the above steps 702-704.

[0475] 1207.SF sends a perception control request to each perception signal receiving node in multiple perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0476] 1208.SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, and the perception control responses include perception data corresponding to the first perception service.

[0477] 1209.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0478] The principles of steps 1207-1209 are similar to those of steps 402-404 above, and reference may be made to the relevant descriptions of steps 402-404 above.

[0479] 1210. SF sends the first perception result to AF through NEF.

[0480] [Example 7]

[0481] In the case of the seventh embodiment, a redundant sensing indication needs to be carried in the sensing request to trigger redundant sensing, and an authorization check for redundant sensing needs to be performed by the SF. Therefore, if the UE needs to perform redundant sensing, the redundant sensing indication can be carried in the sensing request, and redundant sensing can only be performed when redundant sensing is subsequently authorized. Conversely, if the UE does not need to perform redundant sensing, the redundant sensing indication can be omitted from the sensing request. The following mainly uses the case of carrying redundant sensing as an example for explanation.

[0482] Please refer to Figure 13, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 13, the method may include but is not limited to the following steps:

[0483] 1301. The terminal device sends a first perception service request to the SF, where the first perception service request is used to request a first perception service. The first perception service request includes a redundant perception indication, where the redundant perception indication is used to indicate acquisition of multiple perception data corresponding to the first perception service.

[0484] Among them, the instruction to obtain multiple perception data corresponding to the first perception service can also be understood as an instruction to execute the first perception service through / adopting redundant perception, which will not be repeated below.

[0485] Accordingly, the SF may receive a first perception service request from the terminal device.

[0486] Step 1301 is similar to step 501 , and reference may be made to the relevant description in step 501 , which will not be repeated here.

[0487] 1302.SF performs an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information.

[0488] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0489] After SF receives the first perception service request from the terminal device, it can determine that redundant perception needs to be used for perception based on the redundant perception indication in the first perception service request. Therefore, SF can first perform an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information.

[0490] Optionally, the first redundant perception configuration information includes one or more of the following: the perception service type allowed for redundant perception, the perception area allowed for redundant perception, the time allowed for redundant perception, the application function identifier (AFID) allowed for redundant perception, and the identifier of the terminal device allowed for redundant perception.

[0491] Step 1302 is similar to step 703 , and reference may be made to the relevant description in the above step 703 .

[0492] 1303. When the acquisition of multiple perception data corresponding to the first perception service is authorized, the SF determines multiple perception node groups based on the redundant perception indication of the first perception service, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0493] After the SF determines that the acquisition of multiple perception data corresponding to the first perception service is authorized based on the first perception service request and the first redundant perception configuration information, it can determine multiple perception node groups.

[0494] It is understandable that, in the case where the first perception service request does not carry a redundant perception indication, SF can also perform / not perform an authorization check on the first perception service through UDM (refer to the relevant descriptions in Example 1 and Example 2). In the case where there is no need to perform an authorization check on the first perception service, if the first perception service request does not carry a redundant perception indication, then SF can directly use a non-redundant perception method to execute the first perception service. In the case where an authorization check is required for the first perception service, if the first perception service request does not carry a redundant perception indication, and the first perception service is authorized, then SF can use a non-redundant perception method to execute the first perception service. If the first perception service request does not carry a redundant perception indication, and the first perception service is not authorized, then SF can reject the first perception service request.

[0495] For the related operations of SF determining the perception node group, please refer to the related description in the above step 402.

[0496] 1304.SF sends a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0497] 1305. SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, where the perception control responses include perception data corresponding to the first perception service.

[0498] 1306.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0499] The principles of steps 1304-1306 are similar to those of steps 402-404 above, and reference may be made to the relevant descriptions of steps 402-404 above.

[0500] 1307.SF sends the first perception result to the terminal device.

[0501] In some possible implementations, the terminal device in FIG13 may also be replaced by an AF, that is, the operations performed by the terminal device may also be performed by the AF.

[0502] [Embodiment 8]

[0503] In the eighth embodiment, a redundant sensing indication needs to be carried in the sensing request to trigger redundant sensing, and the redundant sensing authorization check needs to be performed by the SF. Therefore, if the AF needs to perform redundant sensing, the redundant sensing indication can be carried in the sensing request, and redundant sensing can only be performed if redundant sensing is authorized. Conversely, if the UE does not need to perform redundant sensing, the redundant sensing indication can be omitted in the sensing request.

[0504] Please refer to Figure 14, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 14, the method may include but is not limited to the following steps:

[0505] 1401. AF sends a second perception service request to NEF, where the second perception service request is used to request the first perception service. The second perception service request includes a redundant perception indication, where the redundant perception indication is used to instruct acquisition of multiple perception data corresponding to the first perception service.

[0506] Among them, the instruction to obtain multiple perception data corresponding to the first perception service can also be understood as an instruction to execute the first perception service through / adopting redundant perception, which will not be repeated below.

[0507] 1402. NEF sends a second perception authorization request to UDM based on the second perception service request, where the second perception authorization request is used to request an authorization check for the first perception service.

[0508] 1403. UDM performs authorization check on the first perception service based on the second perception authorization request.

[0509] 1404. UDM sends a second authorization response to NEF, where the second authorization response is used to indicate that the first perception service is authorized.

[0510] It should be noted that the above steps 1402-1404 are optional. In some possible implementations, steps 1402-1404 may not be performed. In this case, step 1405 may be performed directly after step 1401. That is, after receiving the second awareness service request from the AF, the NEF may directly perform step 1405.

[0511] 1405.NEF sends a first perception service request to SF, where the first perception service request is used to request a first perception service. The first perception service request includes a redundant perception indication, where the redundant perception indication is used to indicate acquisition of multiple perception data corresponding to the first perception service.

[0512] Steps 1401-1405 are similar to the above steps 601-605, and reference may be made to the relevant descriptions in the above steps 601-605.

[0513] 1406.SF performs an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information.

[0514] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0515] After SF receives the first perception service request from AF, it can determine that redundant perception needs to be used for perception based on the redundant perception indication in the first perception service request. Therefore, SF can first perform an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information.

[0516] Optionally, the first redundant perception configuration information includes one or more of the following: the perception service type allowed for redundant perception, the perception area allowed for redundant perception, the time allowed for redundant perception, the application function identifier (AFID) allowed for redundant perception, and the identifier of the terminal device allowed for redundant perception.

[0517] Step 1406 is similar to step 703 , and reference may be made to the relevant description in the above step 703 .

[0518] 1407. When the acquisition of multiple perception data corresponding to the first perception service is authorized, the SF determines multiple perception node groups, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0519] After the SF determines that the acquisition of multiple perception data corresponding to the first perception service is authorized based on the first perception service request and the first redundant perception configuration information, it can determine multiple perception node groups.

[0520] Step 1407 is similar to step 705 , and reference may be made to the relevant description in step 705 .

[0521] 1408.SF sends a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0522] 1409.SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, and the perception control responses include perception data corresponding to the first perception service.

[0523] 1410.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0524] The principles of steps 1408 - 1410 are similar to those of steps 402 - 404 above, and reference may be made to the relevant descriptions of steps 402 - 404 above.

[0525] 1411. SF sends the first perception result to AF through NEF.

[0526] [Example 9]

[0527] In the case of Example 9, the terminal device does not need to carry a redundant perception indication in the perception request to trigger redundant perception. By default, each perception request is subject to a redundant perception authorization check through the SF. If redundant perception is authorized, redundant perception can be performed. Conversely, if redundant perception is not authorized, redundant perception will not be performed. It can be understood that the main difference between Example 9 and Example 7 is that Example 7 is to trigger the authorization of redundant perception by the terminal device actively carrying a redundant perception indication in the perception request according to actual needs, thereby triggering redundant perception, while Example 9 is to trigger the authorization of redundant perception by the core network element (SF, etc.), thereby triggering redundant perception. Therefore, Example 9 and Example 7 can refer to each other.

[0528] Please refer to Figure 15, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 15, the method may include but is not limited to the following steps:

[0529] 1501. The terminal device sends a first perception service request to the SF, where the first perception service request is used to request a first perception service.

[0530] Accordingly, the SF may receive a first perception service request from the terminal device.

[0531] Step 1501 is similar to step 1001 , and you can refer to the relevant description in step 1001 , which will not be repeated here.

[0532] 1502.SF performs an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information.

[0533] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0534] For example, the SF local policy may be configured to perform a default authorization check for redundant perception on each perception request. Therefore, after receiving the first perception service request from the terminal device, the SF may perform an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information.

[0535] Step 1503 is similar to step 703 , and reference may be made to the relevant description in step 703 .

[0536] 1503. When the acquisition of multiple perception data corresponding to the first perception service is authorized, the SF determines multiple perception node groups, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0537] After the SF determines that the acquisition of multiple perception data corresponding to the first perception service is authorized based on the first perception service request and the first redundant perception configuration information, it can determine multiple perception node groups.

[0538] 1504.SF sends a perception control request to each perception signal receiving node in a plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0539] 1505.SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, and the perception control responses include perception data corresponding to the first perception service.

[0540] 1506.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0541] The principles of steps 1504-1506 are similar to those of steps 402-404 above, and reference may be made to the relevant descriptions of steps 402-404 above.

[0542] 1507.SF sends the first perception result to the terminal device.

[0543] In some possible implementations, the terminal device in FIG15 may also be replaced by an AF, that is, the operations performed by the terminal device may also be performed by the AF.

[0544] [Example 10]

[0545] In the case of the tenth embodiment, the AF does not need to carry a redundant sensing indication in the sensing request to trigger redundant sensing. By default, each sensing request is subject to a redundant sensing authorization check by the SF. If redundant sensing is authorized, redundant sensing can be performed. Conversely, if redundant sensing is not authorized, redundant sensing will not be performed. It can be understood that the main difference between the tenth embodiment and the eighth embodiment is that the eighth embodiment is to trigger the authorization of redundant sensing by the AF actively carrying a redundant sensing indication in the sensing request according to actual needs, thereby triggering redundant sensing, while the tenth embodiment is to trigger the authorization of redundant sensing by the core network element (NEF, SF, etc.), thereby triggering redundant sensing. Therefore, the tenth embodiment and the eighth embodiment can refer to each other.

[0546] Please refer to Figure 16, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 16, the method may include but is not limited to the following steps:

[0547] 1601. AF sends a second perception service request to NEF, where the second perception service request is used to request the first perception service.

[0548] 1602. The NEF sends a second perception authorization request to the UDM based on the second perception service request. The second perception authorization request is used to request an authorization check for the first perception service.

[0549] 1603. UDM performs authorization check on the first perception service based on the second perception authorization request.

[0550] 1604. UDM sends a second authorization response to NEF, where the second authorization response is used to indicate that the first perception service is authorized.

[0551] It should be noted that the above steps 1602-1604 are optional. In some possible implementations, steps 1602-1604 may not be performed. In this case, step 1605 may be performed directly after step 1601. That is, after receiving the second perception service request from the AF, the NEF may directly perform step 1605.

[0552] 1605. The NEF sends a first perception service request to the SF, where the first perception service request is used to request a first perception service.

[0553] Optionally, the first sensing service request may include one or more of the following: sensing service type, sensing service requirement, sensing area, and application function identifier. For detailed descriptions of the sensing service type, sensing service requirement, etc., please refer to the relevant description in step 401.

[0554] Optionally, the first perception service request may further include a redundant perception indication. Specifically, since in the tenth embodiment, the SF is required to perform a redundant perception authorization check on each perception request by default, the NEF may carry a redundant perception indication in the perception request sent to the SF. The redundant perception indication is used to instruct the acquisition of multiple perception data corresponding to the first perception service, and can also be understood as indicating that the SF needs to perform a redundant perception authorization check to determine whether to use redundant perception for perception.

[0555] Steps 1601-1605 are similar to the above steps 601-605, and reference may be made to the relevant descriptions in the above steps 601-605.

[0556] 1606.SF performs an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information.

[0557] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0558] For example, the SF local policy may be configured to perform a default authorization check for redundant perception on each perception request. Therefore, after receiving the first perception service request from the NEF, the SF may perform an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information.

[0559] Optionally, SF can determine that redundant perception is required for perception based on the redundant perception indication in the first perception service request, and can perform an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception service request and the first redundant perception configuration information.

[0560] Step 1606 is similar to step 703 , and reference may be made to the relevant description in step 703 .

[0561] 1607. When the acquisition of multiple perception data corresponding to the first perception service is authorized, the SF determines multiple perception node groups, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0562] After the SF determines that the acquisition of multiple perception data corresponding to the first perception service is authorized based on the first perception service request and the first redundant perception configuration information, it can determine multiple perception node groups.

[0563] Step 1607 is similar to step 705, and reference may be made to the relevant description in the above step 705.

[0564] 1608.SF sends a perception control request to each perception signal receiving node in a plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0565] 1609.SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, and the perception control responses include perception data corresponding to the first perception service.

[0566] 1610.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0567] The principles of steps 1608-1610 are similar to those of steps 402-404 above, and reference may be made to the relevant descriptions of steps 402-404 above.

[0568] 1611. SF sends the first perception result to AF through NEF.

[0569] The redundant perception technical solution provided by the embodiments of the present application is exemplified above through Examples 1 to 10. For Examples 1, 2, 3, 4, 7, and 8, the perception demand party (such as terminal equipment, AF, etc.) actively carries redundant perception instructions in the perception request to trigger redundant perception according to actual needs. Therefore, in a possible scenario, the perception demand party can initiate a perception request again when the perception result obtained by non-redundant perception meets the first condition, and carry a redundant perception instruction in the perception request to trigger redundant perception. The following is an exemplified explanation based on Example 4, which can be used as a reference for Examples 1, 2, 3, 7, and 8.

[0570] Please refer to Figure 17, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 17, the method may include but is not limited to the following steps:

[0571] 1701. AF sends a third perception service request to NEF, where the third perception service request is used to request the second perception result of the first perception service.

[0572] When the AF does not need to obtain the perception result corresponding to the first perception service in a non-redundant perception manner, it can send a third perception service request to the NEF, and the third perception service request does not carry a redundant perception indication.

[0573] 1702. The NEF sends a fourth perception service request to the SF based on the third perception service request, where the fourth perception service request is used to request the second perception result of the first perception service.

[0574] After receiving the third perception service request from the AF, the NEF may send a fourth perception service request to the SF based on the third perception service request, where the fourth perception service request is used to request the second perception result of the first perception service. The fourth perception service request does not carry a redundant perception indication.

[0575] 1703. SF sends the second perception result to AF through NEF.

[0576] After receiving the fourth sensing service request from the NEF, the SF may determine that it needs to perform the first sensing service using a non-redundant sensing method and may send a sensing control request to the corresponding sensing node. The sensing node may then perform a sensing operation based on the sensing control request, obtain corresponding sensing data, and send the sensing data to the SF. After receiving the sensing data from the sensing node, the SF may obtain a second sensing result based on the sensing data. In other words, the second sensing result is the sensing result obtained by performing the first sensing service using a non-redundant sensing method.

[0577] It should be understood that the above steps 1701-1703 are mainly for eliciting the second perception result, and are not described in detail, and some steps are omitted. For details, please refer to the relevant description in the above-mentioned related embodiments.

[0578] 1704. When it is determined that the second perception result meets the first condition, the AF sends a second perception service request to the NEF, where the second perception service request is used to request the first perception service. The second perception service request includes a redundant perception indication, which is used to indicate the acquisition of multiple perception data corresponding to the first perception service.

[0579] When the AF determines that the second perception result meets the first condition, it can send a second perception service request to the NEF and carry a redundant perception indication therein.

[0580] The second perception result satisfies the first condition, including a variety of possible configuration situations. For example, the second perception result satisfies the first condition may be that the perception accuracy of the second perception result is insufficient, such as one or more of the distance accuracy, speed accuracy, and angle accuracy are insufficient. Insufficient distance accuracy may be that the distance accuracy is greater than a certain threshold (10cm), that is, the distance perception error is greater than a certain threshold. Similarly, insufficient speed accuracy may be that the speed accuracy is greater than a certain threshold, and insufficient angle accuracy may be that the angle accuracy is greater than a certain threshold. In one possible implementation, AF determines that the second perception result is insufficient in accuracy, and it may be that the second perception result is compared with the actual observation result to determine that the deviation between the two is greater than a certain threshold, including one or more of the distance deviation, speed deviation, and angle deviation. AF determines that the second perception result is insufficient in accuracy, or it may be that the accuracy is insufficient based on an internal algorithm, and the embodiments of the present application are not limited to this.

[0581] It should be noted that the second perception result satisfying the first condition may indicate that the second perception result is inaccurate / precise. Therefore, the second perception result satisfying the first condition may also include other situations that may indicate that the second perception result is inaccurate.

[0582] 1705. The NEF sends a second perception authorization request to the UDM based on the second perception service request. The second perception authorization request is used to request an authorization check for the first perception service.

[0583] 1706. UDM performs authorization check on the first perception service based on the second perception authorization request.

[0584] 1707. UDM sends a second authorization response to NEF, where the second authorization response is used to indicate that the first perception service is authorized.

[0585] 1708.NEF sends a first perception service request to SF, where the first perception service request is used to request a first perception service. The first perception service request includes a redundant perception indication, where the redundant perception indication is used to indicate acquisition of multiple perception data corresponding to the first perception service.

[0586] Among them, the instruction to obtain multiple perception data corresponding to the first perception service can also be understood as an instruction to execute the first perception service through / adopting redundant perception, which will not be repeated below.

[0587] 1709.SF sends a first perception authorization request to UDM based on the first perception service request. The first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service.

[0588] 1710. Based on the first perception authorization request and the first redundant perception configuration information, the UDM performs an authorization check on obtaining multiple perception data corresponding to the first perception service.

[0589] Among them, requesting an authorization check for obtaining multiple perception data corresponding to the first perception service can also be understood as requesting an authorization check for executing the first perception service through / adopting redundant perception, which will not be repeated below.

[0590] 1711. UDM sends a first authorization response to SF, where the first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

[0591] 1712. When the acquisition of multiple perception data corresponding to the first perception service is authorized, the SF determines multiple perception node groups, each perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item.

[0592] 1713.SF sends a perception control request to each perception signal receiving node in a plurality of perception node groups, where the perception control request is used to request the perception data corresponding to the first perception service.

[0593] 1714.SF receives perception control responses from the perception signal receiving nodes in the multiple perception node groups respectively, and the perception control responses include perception data corresponding to the first perception service.

[0594] 1715.SF obtains a first perception result based on multiple perception data corresponding to the first perception service.

[0595] 1716. SF sends the first perception result to AF through NEF.

[0596] For a more detailed description of steps 1705 - 1716 , please refer to the relevant description in the above embodiment.

[0597] It is understandable that for Examples 3 to 10, redundant perception authorization checks are required. In some cases, the redundant perception authorization conditions configured by the current redundant perception authorizer (such as UDM or SF, etc.) may not meet the perception request sent by the perception demander (such as terminal equipment, AF, etc.). In this case, even if the redundant perception indication is carried in the perception request, perception will not be performed in a non-redundant perception manner, and may be performed in a non-redundant perception manner. However, the perception results obtained by perception in a non-redundant perception manner cannot guarantee their accuracy. Therefore, for this situation, the redundant perception authorization conditions can be dynamically configured for the redundant perception authorizer so that perception can be performed in a redundant perception manner. In one possible scenario, the perception demander can configure the corresponding redundant perception configuration information through a parameter configuration request when the perception result obtained by using a non-redundant perception manner meets the first condition, that is, configure the authorization conditions for redundant perception. The following is an example explanation using UDM as the redundant perception authorizer and AF initiating a parameter configuration request. For the case where the redundant perception authorizer is other network elements (such as SF) or other network elements (such as terminal equipment) initiating a parameter configuration request, similar reference can be made and no detailed description will be given.

[0598] Please refer to Figure 18, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 18, the method may include but is not limited to the following steps:

[0599] 1801. AF sends a third perception service request to NEF, where the third perception service request is used to request the second perception result of the first perception service.

[0600] Optionally, the third perception service request may include one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0601] 1802. The NEF sends a fourth perception service request to the SF based on the third perception service request, where the fourth perception service request is used to request the second perception result of the first perception service.

[0602] 1803. SF sends the second perception result to AF through NEF.

[0603] Steps 1801-1803 are similar to steps 1701-1703, and reference may be made to the relevant descriptions in the above steps 1701-1703.

[0604] 1804. When it is determined that the second perception result meets the first condition, the AF sends a second parameter configuration request to the NEF based on the third perception service request, and the second parameter configuration request includes third redundant perception configuration information.

[0605] Among them, when it is determined that the second perception result meets the first condition, there are multiple possible situations for sending the second parameter configuration request (Nnef_parameterProvision) to the NEF. One situation is: for the situation in which the redundant perception indication is not carried in the perception request in Example 5, Example 6, Example 9, Example 10, etc., and redundant perception authorization is performed for each perception request by default, if the AF determines that the second perception result meets the first condition, it can be considered that the third perception service request does not meet the current redundant perception configuration information. Therefore, the second parameter configuration request can be sent to the NEF for corresponding configuration, so that subsequent perception of the same or similar perception service requests can be performed through redundant perception. Another situation is: for the situation in which the redundant perception indication is carried in the perception request in Example 3, Example 4, Example 7, Example 8, etc., if the third perception service request carries a redundant perception indication, but the AF determines that the second perception result meets the first condition, in this case, it can also be considered that the third perception service request does not meet the current redundant perception configuration information. Therefore, the second parameter configuration request can be sent to the NEF for corresponding configuration, so that subsequent perception of the same or similar perception service requests can be performed through redundant perception.

[0606] The main basis for the above-mentioned belief that the third perception service request does not meet the current redundant perception configuration information is that the perception results obtained by performing the perception task in a redundant perception manner will not meet or will not meet the first condition with a high probability (such as greater than 90%).

[0607] The third redundant perception configuration information may be obtained based on the third perception service request. For example, the triple redundant perception configuration information may include all or part of the information in the third perception service request, such as one or more of the perception service type, perception area, application function identifier, and perception service execution time in the third perception service request. It is understood that the third perception service request can be considered the perception service request corresponding to the second perception result.

[0608] The third redundant perception configuration information may include one or more of the following: a perception service type for which redundant perception is allowed, a perception area for which redundant perception is allowed, an application function identifier for which redundant perception is allowed, and a time for which redundant perception is allowed. Exemplarily, the perception service type for which redundant perception is allowed may be the perception service type in the third perception service request, the perception area for which redundant perception is allowed may also be the perception area in the third perception service request, the application function identifier for which redundant perception is allowed may be the application function identifier in the third perception service request, and the time for which redundant perception is allowed may be the execution time of the perception service in the third perception service request.

[0609] 1805. The NEF performs an authorization check on the AF based on the second parameter configuration request.

[0610] In some possible implementations, after receiving the second parameter configuration request from the AF, the NEF may perform an authorization check on the AF to determine whether the AF has the authority to initiate the second parameter configuration request. If the AF has the authority, further processing may be performed based on the second parameter configuration request; if the AF does not have the authority, the second parameter configuration request may be rejected or ignored.

[0611] Exemplarily, the NEF may determine whether the AF has the authority to initiate the second parameter configuration request based on a local policy. In another exemplary embodiment, the NEF may request authorization check information from the UDM, and then determine whether the AF has the authority to initiate the second parameter configuration request based on the authorization check information.

[0612] 1806. The NEF sends a first parameter configuration request to the UDM based on the second parameter configuration request, where the first parameter configuration request includes second redundant perception configuration information, and the second redundant perception configuration information is obtained based on the third redundant perception configuration information.

[0613] Since the third redundant sensing configuration information may include some external information, such as information about the sensing area allowed for redundant sensing being an external area, the NEF may convert the external information in the third redundant sensing configuration information into internal information, such as converting the external area information into internal area information, to obtain the second redundant sensing configuration information. The NEF may then send a first parameter configuration request (Nudm_parameterProvision) to the UDM, where the first parameter configuration request includes the second redundant sensing configuration information.

[0614] It can be understood that when the redundant perception authorization party is SF, NEF can send a first parameter configuration request (Nsf_parameterProvision) to SF based on the second parameter configuration request, and the first parameter configuration request includes the second redundant perception configuration information, and the second redundant perception configuration information is obtained based on the third redundant perception configuration information.

[0615] 1807. UDM applies the second redundant perception configuration information.

[0616] After receiving the first parameter configuration request from NEF, UDM can apply the second redundant perception configuration information in the first parameter configuration request so that it can perceive the corresponding perception service request through redundant perception.

[0617] With respect to the above-mentioned third to tenth embodiments, the first redundant awareness configuration information may include the second redundant awareness configuration information.

[0618] The above processing flow provides various ways to trigger redundant perception, including different perception demanders (AF, terminal devices, etc.), whether redundant perception authorization checks are required, and who performs the redundant perception authorization checks when redundant perception authorization checks are required. These different situations, when combined, include a variety of possible implementations, and reference can be made to the relevant descriptions of Examples 1 to 10 above. Based on Examples 1 to 10, other embodiments can also be derived, such as combinations of certain steps in different embodiments, which should also be included within the scope of protection of this application.

[0619] In summary, the above-mentioned redundant sensing method for performing sensing services can ensure the precision / accuracy of the sensing results and the reliability of the sensing. In addition, the above description also illustrates the process of actively triggering redundant sensing on the AF side and the process of actively configuring parameters, respectively, using Figures 17 and 18, which provide high flexibility.

[0620] It should be noted that the relevant information (ie, the same information or similar information) and related descriptions in the above different embodiments can refer to each other.

[0621] The above mainly introduces the communication method provided in the embodiment of the present application. It can be understood that in order to realize the corresponding functions mentioned above, the above-mentioned SF, AF, NEF, UDM and terminal equipment may include hardware structures and / or software modules corresponding to the execution of each function. In combination with the units and steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of the present application.

[0622] In the embodiment of the present application, the functional modules of SF, AF, NEF, UDM and terminal devices can be divided according to the above method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0623] FIG19 shows a possible structural diagram of a communication device 1900, in which each functional module is divided according to its function. The communication device 1900 includes a receiving unit 1901, a sending unit 1902, and a processing unit 1903. In one possible design, the communication device 1900 may be the aforementioned perception function network element, or may be a chip in the perception function network element, or may be a processing system in the perception function network element.

[0624] The receiving unit 1901 is configured to receive a first perception service request, where the first perception service request is used to request a first perception service;

[0625] a sending unit 1902, configured to send, based on the first sensing service request, a sensing control request to each of the sensing signal receiving nodes in the plurality of sensing node groups, where the sensing control request is used to request sensing data corresponding to the first sensing service, the sensing node groups including sensing signal sending nodes and sensing signal receiving nodes, and the sensing signal sending nodes and the sensing signal receiving nodes in different sensing node groups differ in at least one aspect;

[0626] The processing unit 1903 is configured to respectively obtain the perception data corresponding to the first perception service from the perception signal receiving nodes in the multiple perception node groups.

[0627] Exemplarily, the processing unit 1903 may obtain, through the receiving unit 1901 , the perception data corresponding to the first perception service from the perception signal receiving nodes in the multiple perception node groups.

[0628] In a possible implementation, the first perception service request includes a redundant perception indication, and the sending unit 1902 is specifically configured to: send perception control requests to the perception signal receiving nodes in the multiple perception node groups respectively based on the redundant perception indication.

[0629] In one possible implementation, the processing unit 1903 is further used to: assign a perception task identification ID to each perception control request, where the perception task ID corresponds to the first perception service; obtain the perception data corresponding to the first perception service and the perception task ID corresponding to each perception data from the perception signal receiving nodes in the multiple perception node groups; and determine that each perception data corresponds to the first perception service based on the perception task ID corresponding to each perception data.

[0630] In one possible implementation, before the sending unit 1902 sends perception control requests to the perception signal receiving nodes in multiple perception node groups respectively, the sending unit 1902 is also used to send a first perception authorization request to the data management network element based on the first perception service request, and the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service; the receiving unit 1901 is also used to receive a first authorization response from the data management network element, and the first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

[0631] In one possible implementation, the first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

[0632] In a possible implementation, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0633] In a possible implementation, the sending unit 1902 is further configured to send a perception control request to each perception signal receiving node in the plurality of perception node groups when the first perception service request satisfies the first redundant perception configuration information.

[0634] In one possible implementation, the first redundant perception configuration information includes one or more of the following: a perception service type for which redundant perception is allowed, a perception area for which redundant perception is allowed, an application function identifier for which redundant perception is allowed, and a time for which redundant perception is allowed.

[0635] In a possible implementation, the receiving unit 1901 is further configured to receive a first parameter configuration request from the network capability exposure function network element, the first parameter configuration request includes second redundant perception configuration information, and the first redundant perception configuration information includes the second redundant perception configuration information.

[0636] In a possible implementation, the first perception service request further includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0637] In one possible implementation, the first perception service request comes from a terminal device, a network capability exposure function network element, or an application function network element.

[0638] In combination with the sixth aspect, in a possible implementation, the processing unit 1903 is further configured to determine a first perception result based on the perception data corresponding to the multiple first perception services.

[0639] In one possible implementation, the processing unit 1903 is specifically used to: obtain target perception data after excluding deviation perception data in the perception data corresponding to the multiple first perception services based on the perception data corresponding to the multiple first perception services; and obtain the first perception result based on the target perception data.

[0640] The specific operations of each unit in the above-mentioned communication device 1900 can be found in the corresponding description of SF in the above-mentioned method embodiment, which will not be repeated here.

[0641] Figure 20 shows a possible structural diagram of a communication device 2000. The communication device 2000 includes a receiving unit 2001, a sending unit 2002, and the communication device 2000 may also include a processing unit 2003. In one possible design, the communication device 2000 may be the above-mentioned data management network element, or may be a chip in the data management network element, or may be a processing system in the data management network element, etc.

[0642] The receiving unit 2001 is configured to receive a first perception authorization request, where the first perception authorization request is used to request an authorization check for obtaining a plurality of perception data corresponding to a first perception service;

[0643] The sending unit 2002 is used to send a first authorization response when the first perception authorization request meets the first redundant perception configuration information. The first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

[0644] In one possible implementation, the first redundant perception configuration information includes one or more of the following: a perception service type for which redundant perception is allowed, a perception area for which redundant perception is allowed, an application function identifier for which redundant perception is allowed, and a time for which redundant perception is allowed.

[0645] In one possible implementation, the first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

[0646] In one possible implementation, the communication device also includes: a processing unit 2003, which is used to perform an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception authorization request and the first redundant perception configuration information when the first perception authorization request includes a redundant perception indication.

[0647] In a possible implementation, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0648] In a possible implementation, the receiving unit 2001 is further configured to receive a first parameter configuration request from a network capability exposure function network element, the first parameter configuration request including second redundancy awareness configuration information, and the first redundancy awareness configuration information including the second redundancy awareness configuration information.

[0649] In a possible implementation, the first perception authorization request comes from a network capability exposure function network element or a perception function network element.

[0650] The specific operations of each unit in the above communication device 2000 can be found in the corresponding description of UDM in the above method embodiment, which will not be repeated here.

[0651] Figure 21 shows a possible structural diagram of a communication device 2100. The communication device 2100 includes a receiving unit 2101 and a sending unit 2102. In one possible design, the communication device 2100 can be the above-mentioned network capability exposure function network element, or can be a chip in the network capability exposure function network element, or can be a processing system in the network capability exposure function network element, etc.

[0652] The receiving unit 2101 is configured to receive a second perception service request, where the second perception service request is used to request a first perception service;

[0653] The sending unit 2102 is configured to send a first perception authorization request to the data management network element based on the second perception service request, where the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service;

[0654] The receiving unit 2101 is further configured to receive a first authorization response from the data management network element, where the first authorization response is used to indicate that obtaining the multiple sensing data corresponding to the first sensing service is authorized;

[0655] The sending unit 2102 is further configured to send a first perception service request to the perception function network element based on the first authorization response, where the first perception service request is used to request the first perception service.

[0656] In a possible implementation, the second perception service request includes one or more of the following: perception service type, perception service requirement, perception area, application function identifier, and redundant perception indication.

[0657] In a possible implementation, the sending unit 2102 is specifically configured to: when the second perception service request includes a redundant perception indication, send a first perception authorization request to the data management network element based on the second perception service request.

[0658] In one possible implementation, the first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

[0659] In a possible implementation, the first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that acquisition of the multiple perception data corresponding to the first perception service is authorized.

[0660] In a possible implementation, the first perception service request includes one or more of the following: perception service type, perception service requirement, perception area, application function identifier, and redundant perception indication.

[0661] In one possible implementation, the receiving unit 2101 is further used to receive a second parameter configuration request from an application function network element, where the second parameter configuration request includes third redundant perception configuration information; the sending unit 2102 is further used to send a first parameter configuration request based on the second parameter configuration request, where the first parameter configuration request includes second redundant perception configuration information, and the second redundant perception configuration information is obtained based on the third redundant perception configuration information.

[0662] In a possible implementation, the sending unit 2102 sending the first parameter configuration request based on the second parameter configuration request includes: when the application function network element authorization check passes, sending the first parameter configuration request based on the second parameter configuration request.

[0663] In one possible implementation, the second redundant perception configuration information includes one or more of the following: a perception service type for which redundant perception is allowed, a perception area for which redundant perception is allowed, an application function identifier for which redundant perception is allowed, and a time for which redundant perception is allowed.

[0664] In one possible implementation, the receiving unit 2101 is also used to receive a first perception result from the perception function network element, where the first perception result is obtained based on multiple perception data corresponding to the first perception service, and the multiple perception data are obtained through multiple perception node groups. The perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending node and the perception signal receiving node in different perception node groups are different in at least one item.

[0665] The specific operations of each unit in the above communication device 2000 can refer to the corresponding description of NEF in the above method embodiment, which will not be repeated here.

[0666] In one possible design, the communication device 2100 may be the aforementioned network capability exposure function network element, or may be a chip in the network capability exposure function network element, or may be a processing system in the network capability exposure function network element, etc.

[0667] The receiving unit 2101 is configured to receive a second perception service request, where the second perception service request is used to request a first perception service, and the second perception service request includes a redundant perception indication, where the redundant perception indication is used to instruct acquisition of multiple perception data corresponding to the first perception service;

[0668] The sending unit 2102 is used to send a first perception service request to the perception function network element based on the second perception service request, where the first perception service request is used to request the first perception service.

[0669] In a possible implementation, the second perception service request further includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0670] In a possible implementation, the first perception service request includes one or more of the following: perception service type, perception service requirement, perception area, application function identifier, and redundant perception indication.

[0671] In one possible implementation, the sending unit 2102 sends the first perception service request to the perception function network element based on the second perception service request, including: sending a second perception authorization request to the data management network element based on the second perception service request, and the second perception authorization request is used to request an authorization check for the first perception service; the receiving unit 2101 is also used to receive a second authorization response from the data management network element, and the second authorization response is used to indicate that the first perception service is authorized; the sending unit 2102 is also used to send the first perception service request to the perception function network element based on the second authorization response.

[0672] In one possible implementation, the receiving unit 2101 is also used to receive a first perception result from a perception function network element. The first perception result is obtained based on multiple perception data corresponding to the first perception service. The multiple perception data are obtained through multiple perception node groups. The perception node group includes a perception signal sending node and a perception signal receiving node. The perception signal sending node and the perception signal receiving node in different perception node groups are different in at least one item.

[0673] The specific operations of each unit in the above communication device 2000 can be found in the corresponding description of NEF in the above method embodiment, which will not be repeated here.

[0674] In one possible design, the communication device 2100 may be the aforementioned terminal device or application function network element, or may be a chip in the terminal device or application function network element, or may be a processing system in the terminal device or application function network element, etc.

[0675] The sending unit 2102 is used to send a first perception service request, which is used to request a first perception service. The first perception service request includes a redundant perception indication, which is used to indicate the acquisition of multiple perception data corresponding to the first perception service.

[0676] In one possible implementation, the communication device also includes: a receiving unit 2101, used to receive a first perception result, where the first perception result is obtained based on multiple perception data corresponding to the first perception service, and the multiple perception data are obtained through multiple perception node groups, where the perception node group includes a perception signal sending node and a perception signal receiving node, and the perception signal sending node and the perception signal receiving node in different perception node groups are different in at least one item.

[0677] In one possible implementation, the receiving unit 2101 is also used to receive a second perception result, which is a perception result obtained by executing the first perception service in a non-redundant perception manner; the sending unit 2102 is specifically used to: send a first perception service request based on the second perception result.

[0678] In a possible implementation, the first perception service request includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

[0679] In one possible implementation, before sending the first perception service request, the receiving unit 2101 is also used to receive a second perception result, which is a perception result obtained by executing the first perception service in a non-redundant perception manner; the sending unit 2102 is also used to send a second parameter configuration request based on the second perception result, and the second parameter configuration request includes third redundant perception configuration information.

[0680] In one possible implementation, the third redundant perception configuration information includes one or more of the following: a perception service type for which redundant perception is allowed, a perception area for which redundant perception is allowed, an application function identifier for which redundant perception is allowed, and a time for which redundant perception is allowed.

[0681] In one possible implementation, the sender of the first perception service request is a terminal device or an application function network element.

[0682] The specific operations of each unit in the above-mentioned communication device 2000 can be found in the corresponding descriptions of AF and terminal equipment in the above-mentioned method embodiment, and will not be repeated here.

[0683] In one possible implementation, in the communication devices shown in Figures 19, 20, and 21, the processing unit may be one or more processors / logic circuits, the sending unit may be a transmitter, and the receiving unit may be a receiver. The sending unit and the receiving unit may be integrated into a single device, such as a transceiver. In the embodiments of the present application, the processor and the transceiver may be coupled, etc., and the embodiments of the present application do not limit the connection method between the processor and the transceiver. During the execution of the above method, the process of sending information (such as sending a perception control request, a perception control response, etc.) in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After being output by the processor, the above information may also need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information (such as receiving a perception control request, a perception control response, etc.) in the above method can be understood as the process of the processor receiving the input information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed further before being input into the processor.

[0684] In another possible implementation, in the communication devices shown in Figures 19, 20, and 21, the processing unit may be one or more processors / logic circuits. The sending unit may be an output interface, and the receiving unit may be an input interface. The sending unit and the receiving unit are integrated into a single unit, such as an input / output interface, also known as a communication interface, an interface circuit, or an interface.

[0685] Figure 22 shows a schematic diagram of a possible hardware structure of a communication device 2200 provided in an embodiment of the present application. Communication device 2200 may include a communication interface 2204 and at least one processor 2202. Optionally, it may also include a bus 2203. Further optionally, it may also include at least one memory 2201, wherein memory 2201, processor 2202, and communication interface 2204 are connected via bus 2203.

[0686] Memory 2201 is used to provide storage space for storing data such as an operating system and computer programs. Memory 2201 can be one or a combination of random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0687] The processor 2202 is a module that performs arithmetic operations and / or logical operations, and can specifically be one or more combinations of processing modules such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor unit (MPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and a complex programmable logic device (CPLD).

[0688] The communication interface 2204 is used to receive data sent externally and / or send data externally. It can be a wired link interface such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, etc.). Optionally, the communication interface 2204 can also include a transmitter (such as a radio frequency transmitter, antenna, etc.) or a receiver coupled to the interface.

[0689] In one design, the communication device 2200 can be used to perform the functions of the SF in the aforementioned embodiment. For details, please refer to the relevant descriptions in Figures 4 to 18 above, and will not be repeated here.

[0690] In another design, the communication device 2200 can be used to perform the UDM function in the aforementioned embodiment. For details, please refer to the relevant descriptions in Figures 4 to 18 above, and no further details will be given here.

[0691] In another design, the communication device 2200 can be used to perform the AF function in the aforementioned embodiment. For details, please refer to the relevant descriptions in Figures 4 to 18 above, and no further details will be given here.

[0692] In another design, the communication device 2200 can be used to perform the NEF function in the aforementioned embodiment. For details, please refer to the relevant descriptions in Figures 4 to 18 above, and no further details are given here.

[0693] In another design, the communication device 2200 can be used to perform the functions of the terminal device in the aforementioned embodiment. For details, please refer to the relevant descriptions in Figures 4 to 18 above, and no further details will be given here.

[0694] In one possible design, the processor 2202 in the device 2200 is used to read the computer program stored in the memory 2201, and to execute the operations performed by the SF, UDM, AF, NEF or terminal device in the aforementioned communication method, such as the communication method described in any one of the embodiments in Figures 4-18.

[0695] It should be noted that the communication device 2200 shown in Figure 22 is only one implementation method of the embodiment of the present application. In actual applications, the communication device 2200 may also include more or fewer components, which is not limited here.

[0696] An embodiment of the present application also discloses a communication system, which includes a perception function network element and a data management network element. The perception function network element is used to execute the operations performed by the perception function network element in any of the above method embodiments, and the data management network element is used to execute the operations performed by the data management network element in any of the above method embodiments.

[0697] An embodiment of the present application also discloses a communication system, which includes a perception function network element and an application function network element. The perception function network element is used to execute the operations performed by the perception function network element in any of the above method embodiments, and the application function network element is used to execute the operations performed by the application function network element in any of the above method embodiments.

[0698] An embodiment of the present application also discloses a communication system, which includes a perception function network element, an application function network element and a network open function network element. The perception function network element is used to execute the operations executed by the perception function network element in any of the above-mentioned method embodiments, the application function network element is used to execute the operations executed by the application function network element in any of the above-mentioned method embodiments, and the network open function network element is used to execute the operations executed by the network open function network element in any of the above-mentioned method embodiments.

[0699] An embodiment of the present application also discloses a communication system, which includes a perception function network element, an application function network element and a network open function network element. The perception function network element is used to execute the operations performed by the perception function network element in any of the above-mentioned method embodiments, the application function network element is used to execute the operations performed by the application function network element in any of the above-mentioned method embodiments, the network open function network element is used to execute the operations performed by the network open function network element in any of the above-mentioned method embodiments, and the data m...

Claims

1. A communication method, characterized in that: include: The perception function network element receives a first perception service request, where the first perception service request is used to request a first perception service; Sending a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups based on the first perception service request, wherein the perception control request is used to request the perception data corresponding to the first perception service, the perception node groups comprising a perception signal sending node and a perception signal receiving node, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item; The perception data corresponding to the first perception service is respectively obtained from the perception signal receiving nodes in the multiple perception node groups.

2. The method according to claim 1, characterized in that The first perception service request includes a redundant perception indication, and sending perception control requests to the perception signal receiving nodes in the plurality of perception node groups respectively based on the first perception service request includes: Based on the redundant sensing indication, a sensing control request is respectively sent to the sensing signal receiving nodes in the plurality of sensing node groups.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Allocating a sensing task identification ID to each sensing control request, where the sensing task ID corresponds to the first sensing service; The acquiring, from the perception signal receiving nodes in the plurality of perception node groups, the perception data corresponding to the first perception service respectively comprises: Acquire, from the sensing signal receiving nodes in the plurality of sensing node groups, sensing data corresponding to the first sensing service and a sensing task ID corresponding to each sensing data; Based on the perception task ID corresponding to each perception data, it is determined that each perception data corresponds to the first perception service.

4. The method according to any one of claims 1 to 3, characterized in that: Before respectively sending the perception control request to the perception signal receiving nodes in the plurality of perception node groups, the method further includes: Sending a first perception authorization request to a data management network element based on the first perception service request, where the first perception authorization request is used to request an authorization check for obtaining a plurality of perception data corresponding to the first perception service; A first authorization response is received from the data management network element, where the first authorization response is used to indicate that obtaining the multiple perception data corresponding to the first perception service is authorized.

5. The method according to claim 4, characterized in that The first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

6. The method according to claim 4 or 5, characterized in that: The first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that obtaining the multiple perception data corresponding to the first perception service is authorized.

7. The method according to any one of claims 1 to 3, characterized in that: The sending, based on the first perception service request, perception control requests to the perception signal receiving nodes in the plurality of perception node groups respectively, comprises: When the first perception service request satisfies the first redundant perception configuration information, a perception control request is sent to each of the perception signal receiving nodes in the plurality of perception node groups.

8. The method according to claim 7, characterized in that The first redundant perception configuration information includes one or more of the following: a perception service type that allows redundant perception, a perception area that allows redundant perception, an application function identifier that allows redundant perception, and a time that allows redundant perception.

9. The method according to claim 7 or 8, characterized in that: The method further comprises: A first parameter configuration request is received from the network capability exposure function network element, where the first parameter configuration request includes second redundancy awareness configuration information, and the first redundancy awareness configuration information includes the second redundancy awareness configuration information.

10. The method according to any one of claims 1 to 9, characterized in that: The first perception service request also includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

11. The method according to any one of claims 1 to 10, characterized in that: The first perception service request comes from a terminal device, a network capability exposure function network element or an application function network element.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: A first perception result is determined based on the perception data corresponding to the multiple first perception services.

13. The method according to claim 12, characterized in that The determining the first perception result based on the perception data corresponding to the plurality of first perception services comprises: Obtaining target perception data after eliminating deviation perception data from the perception data corresponding to the multiple first perception services based on the perception data corresponding to the multiple first perception services; The first perception result is obtained based on the target perception data.

14. A communication method, characterized in that: include: The data management network element receives a first perception authorization request, where the first perception authorization request is used to request an authorization check for obtaining multiple perception data corresponding to the first perception service; When the first perception authorization request satisfies the first redundant perception configuration information, a first authorization response is sent, where the first authorization response is used to indicate that obtaining multiple perception data corresponding to the first perception service is authorized.

15. The method according to claim 14, characterized in that The first redundant perception configuration information includes one or more of the following: a perception service type that allows redundant perception, a perception area that allows redundant perception, an application function identifier that allows redundant perception, and a time that allows redundant perception.

16. The method according to claim 14 or 15, characterized in that The first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

17. The method according to claim 16, characterized in that The method further comprises: When the first perception authorization request includes a redundant perception indication, an authorization check is performed on obtaining multiple perception data corresponding to the first perception service based on the first perception authorization request and the first redundant perception configuration information.

18. The method according to any one of claims 14 to 17, characterized in that: The first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that obtaining the multiple perception data corresponding to the first perception service is authorized.

19. The method according to any one of claims 14 to 18, characterized in that: The method further comprises: A first parameter configuration request is received from a network capability exposure function network element, where the first parameter configuration request includes second redundancy awareness configuration information, and the first redundancy awareness configuration information includes the second redundancy awareness configuration information.

20. The method according to any one of claims 14 to 19, characterized in that: The first perception authorization request comes from a network capability exposure function network element or a perception function network element.

21. A communication device, characterized in that: include: A receiving unit, configured to receive a first perception service request, wherein the first perception service request is used to request a first perception service; a sending unit, configured to send, based on the first perception service request, perception control requests to perception signal receiving nodes in a plurality of perception node groups, respectively, wherein the perception control requests are used to request perception data corresponding to the first perception service, the perception node groups comprising perception signal sending nodes and perception signal receiving nodes, and the perception signal sending nodes and the perception signal receiving nodes in different perception node groups are different in at least one item; The processing unit is used to respectively obtain the perception data corresponding to the first perception service from the perception signal receiving nodes in the multiple perception node groups.

22. The communication device according to claim 21, characterized in that The first awareness service request includes a redundancy awareness indication, and the sending unit is specifically configured to: Based on the redundant sensing indication, a sensing control request is respectively sent to the sensing signal receiving nodes in the plurality of sensing node groups.

23. The communication device according to claim 21 or 22, characterized in that: The processing unit is further used for: Allocating a sensing task identification ID to each sensing control request, where the sensing task ID corresponds to the first sensing service; Acquire, from the sensing signal receiving nodes in the plurality of sensing node groups, sensing data corresponding to the first sensing service and a sensing task ID corresponding to each sensing data; Based on the perception task ID corresponding to each perception data, it is determined that each perception data corresponds to the first perception service.

24. The communication device according to any one of claims 21 to 23, characterized in that: Before the sending unit sends the perception control request to the perception signal receiving nodes in the plurality of perception node groups respectively, the sending unit is further configured to send a first perception authorization request to the data management network element based on the first perception service request, where the first perception authorization request is used to request an authorization check for obtaining the plurality of perception data corresponding to the first perception service; The receiving unit is further used to receive a first authorization response from the data management network element, where the first authorization response is used to indicate that obtaining the multiple perception data corresponding to the first perception service is authorized.

25. The communication device according to claim 24, characterized in that The first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

26. The communication device according to claim 24 or 25, characterized in that: The first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that obtaining the multiple perception data corresponding to the first perception service is authorized.

27. The communication device according to any one of claims 21 to 23, characterized in that: The sending unit is further configured to send a perception control request to each of the perception signal receiving nodes in the plurality of perception node groups when the first perception service request satisfies the first redundant perception configuration information.

28. The communication device according to claim 27, characterized in that The first redundant perception configuration information includes one or more of the following: a perception service type that allows redundant perception, a perception area that allows redundant perception, an application function identifier that allows redundant perception, and a time that allows redundant perception.

29. The communication device according to claim 27 or 28, characterized in that: The receiving unit is further used to receive a first parameter configuration request from the network capability exposure function network element, the first parameter configuration request includes second redundancy awareness configuration information, and the first redundancy awareness configuration information includes the second redundancy awareness configuration information.

30. The communication device according to any one of claims 21 to 29, characterized in that: The first perception service request also includes one or more of the following: perception service type, perception service requirement, perception area, and application function identifier.

31. The communication device according to any one of claims 21 to 30, characterized in that: The first perception service request comes from a terminal device, a network capability exposure function network element or an application function network element.

32. The communication device according to any one of claims 21 to 31, characterized in that: The processing unit is further used to determine a first perception result based on the perception data corresponding to the multiple first perception services.

33. The communication device according to claim 32, characterized in that: The processing unit is specifically used for: Obtaining target perception data after eliminating deviation perception data from the perception data corresponding to the multiple first perception services based on the perception data corresponding to the multiple first perception services; The first perception result is obtained based on the target perception data.

34. A communication device, characterized in that: include: A receiving unit, configured to receive a first perception authorization request, wherein the first perception authorization request is used to request an authorization check for obtaining a plurality of perception data corresponding to a first perception service; A sending unit is used to send a first authorization response when the first perception authorization request satisfies the first redundant perception configuration information, wherein the first authorization response is used to indicate that the acquisition of multiple perception data corresponding to the first perception service is authorized.

35. The communication device according to claim 34, characterized in that The first redundant perception configuration information includes one or more of the following: a perception service type that allows redundant perception, a perception area that allows redundant perception, an application function identifier that allows redundant perception, and a time that allows redundant perception.

36. The communication device according to claim 34 or 35, characterized in that: The first perception authorization request includes one or more of the following: perception service type, perception area, application function identifier, and redundant perception indication.

37. The communication device according to claim 36, characterized in that: The communication device further comprises: A processing unit is used to perform an authorization check on obtaining multiple perception data corresponding to the first perception service based on the first perception authorization request and the first redundant perception configuration information when the first perception authorization request includes a redundant perception indication.

38. The communication device according to any one of claims 34 to 37, characterized in that: The first authorization response includes first authorization indication information, where the first authorization indication information is used to indicate that obtaining the multiple perception data corresponding to the first perception service is authorized.

39. The communication device according to any one of claims 34 to 38, characterized in that: The receiving unit is further used to receive a first parameter configuration request from a network capability exposure function network element, the first parameter configuration request includes second redundancy awareness configuration information, and the first redundancy awareness configuration information includes the second redundancy awareness configuration information.

40. The communication device according to any one of claims 34 to 39, characterized in that: The first perception authorization request comes from a network capability exposure function network element or a perception function network element.

41. A communication system, characterized in that: The communication system includes a perception function network element and a data management network element, the perception function network element is used to implement the method described in any one of claims 1-13; the data management network element is used to implement the method described in any one of claims 14-20.

42. A communication system, characterized in that: The communication system includes a perception function network element and an application function network element, and the perception function network element is used to implement the method described in any one of claims 1-13.

43. A communication device, characterized in that: It comprises a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instruction stored in a memory to implement the method according to any one of claims 1 to 13.

44. A communication device, characterized in that: It comprises a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instruction stored in a memory to implement the method as described in any one of claims 14-20.

45. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program or computer instructions, and the computer program or computer instructions are executed by a processor to implement the method described in any one of claims 1 to 13; or, the computer program or computer instructions are executed by a processor to implement the method described in any one of claims 14 to 20.

46. ​​A computer program product, characterized in that The computer program product comprises computer program codes or computer instructions, and when the computer program codes or computer instructions are executed, the method according to any one of claims 1 to 13 is implemented, or the method according to any one of claims 14 to 20 is implemented.

Images