Communication method and related device and system

Abstract

The present application provides a communication method and a related device and system, which can flexibly respond to sensing requests on the basis of sensing regions, meeting the service requirements of different sensing regions. The method comprises: a sensing function network element receives sensing requests, the sensing requests being used for requesting to sense sensing regions; and the sensing function network element acquires a target service requirement, wherein the target service requirement is determined on the basis of the sensing regions, and the target service requirement is used for determining a sensed KPI.

Description

Communication method and related device and system

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on January 12, 2024, with application number 202410056545.8 and application name “Communication Methods and Related Devices and Systems”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and related devices and systems. Background Art

[0003] In addition to communication capabilities, wireless communication systems also possess perception capabilities. These systems can sense and identify specific areas, objects, or events, addressing perception needs in many scenarios. For example, they can predict the presence of people or objects in an environment.

[0004] In the current perception process, a perception application can directly send a perception request containing the perception area and service requirements to the network element responsible for perception. Alternatively, it can send a request through a network capability exposure function element to the network element responsible for perception, requesting that the perception area be perceived using the service requirements. In response to the perception request, the network element responsible for perception in the communication network can initiate a perception process to perceive the specific perception area using the service requirements.

[0005] However, there are currently no relevant security procedures for sensing in specific sensing areas. Summary of the Invention

[0006] The present application provides a communication method and related devices and systems, in order to flexibly respond to perception requests according to perception areas and meet the restrictions on business requirements of different perception areas.

[0007] In a first aspect, the present application provides a communication method that can be applied to a communication device. For example, the communication device can be a perception function network element, or a component configured in the perception function network element (such as a chip, chip system, etc.), or a logic module or software capable of implementing all or part of the functions of the perception function network element, which is not limited by the present application. For ease of understanding and explanation, the method is described below using the perception function network element as an example of a communication device.

[0008] Exemplarily, the method includes: receiving a perception request, the perception request being used to request perception of a perception area; obtaining a target business requirement, the target business requirement being determined based on the perception area, and the target business requirement being used to determine a key performance indicator (KPI) of perception.

[0009] The perception request indicates the perception area.

[0010] The above-mentioned target service requirements are determined according to the perception area, that is, the service requirements corresponding to the perception area requested to be perceived by the perception request are called target service requirements.

[0011] As you can understand, perception KPIs define information such as confidence intervals, perceived positioning accuracy (both vertical and horizontal), perceived velocity accuracy (both vertical and horizontal), perceived resolution (including area and speed), maximum perceived service latency, and refresh rate. In other words, the parameters included in perception KPIs describe the required accuracy of acquired perception data.

[0012] Based on this technical solution, after receiving a perception request for requesting perception of a perception area, the perception function network element can use the perception area as input to obtain the target service requirements corresponding to the perception area. That is, after receiving different perception requests for requesting perception of different perception areas, the perception function network element can flexibly respond to the perception requests according to the perception area to meet the restrictions on service requirements of different perception areas, solving the problem that all service requirements are the same when perceiving the same service requirements of different perception areas.

[0013] In one possible implementation, obtaining the target service requirement includes: sending a service requirement request to a data management function network element, wherein the service requirement request indicates the perception area; receiving N service requirements from the data management function network element, wherein the N service requirements are determined based on the perception area, and N is a positive integer; and obtaining the target service requirement from the N service requirements.

[0014] The service requirement request is used to obtain the target service requirement.

[0015] Optionally, when N>1, the method further includes: receiving a correspondence between N service requirements and N intervals of the number of terminals from the data management function network element.

[0016] In another possible implementation, obtaining the target business requirement includes: determining the N business requirements based on the perception areas and the mapping relationship, the mapping relationship indicating the correspondence between at least one perception area and at least one business requirement, and N being a positive integer; and obtaining the target business requirement from the N business requirements.

[0017] It can be understood that when each of the at least one perception area corresponds to one service requirement, N=1; when the at least one perception area corresponds to multiple service requirements, N>1.

[0018] Optionally, when the perception area corresponds to N time periods and the N time periods correspond to N business requirements, obtaining the target business requirements from the N business requirements includes: when N>1, obtaining the target business requirements from the N business requirements based on the correspondence between the N business requirements and the N time periods, and the time information of the perception request.

[0019] It can be understood that among the above-mentioned N service requirements and N time periods, at least N time periods are different from each other.

[0020] Since N service requirements correspond to N time periods, a unique service requirement can be obtained from the N service requirements based on the time information of the perception request, and this service requirement is the target service requirement.

[0021] In another possible implementation, the perception request carries N business requirements, where N is a positive integer; and obtaining the target business requirement includes: obtaining the target business requirement from the N business requirements.

[0022] Optionally, when N>1, the perception request also carries a correspondence between N service requirements and N intervals of the number of terminals.

[0023] In combination with the above three possible implementations, when N=1, the N service requirements are the target service requirements.

[0024] Optionally, obtaining the target business requirement from the N business requirements includes: when N>1, obtaining the target business requirement from the N business requirements based on the correspondence between the N business requirements and the N intervals of the number of terminals, and the number of terminals included in the perception area.

[0025] It can be understood that among the N intervals of the N service requirements and the number of terminals, at least N intervals are different from each other.

[0026] Since the N service requirements correspond to N intervals of the number of terminals, a unique service requirement can be obtained from the N service requirements according to the number of terminals included in the sensing area, and the unique service requirement is the target service requirement.

[0027] Optionally, before determining the target service requirement from the N service requirements based on the correspondence between the N service requirements and the N intervals of the number of terminals, and the number of terminals contained in the perception area, the method also includes: obtaining the number of terminals contained in the perception area from the access and mobility management function network element.

[0028] Exemplarily, obtaining the number of terminals contained in the perception area from the access and mobility management function network element includes: sending an acquisition request to the access and mobility management function network element, the acquisition request being used to request obtaining the number of terminals contained in the perception area; receiving an acquisition reply from the AMF network element, the acquisition reply indicating the number of terminals contained in the perception area; and determining the number of terminals contained in the perception area based on the acquisition reply.

[0029] Optionally, before acquiring the target service requirement, the method further includes: determining whether sensing of the sensing area is allowed.

[0030] It is understood that, when it is determined that sensing of the sensing area is not permitted, the acquisition of the target service requirement is replaced by sending a rejection message to the application function network element, where the rejection message is used to reject the sensing request. In other words, the acquisition of the target service requirement is performed when it is determined that sensing of the sensing area is permitted.

[0031] Optionally, the perception request carries at least one of the following: an identifier of an application function network element, an indication of the perception area, a requested service type, and a requested service requirement; the determination of allowing perception of the perception area includes: determining that perception of the perception area is allowed when at least one of the following conditions is met: the perception area belongs to a predefined area range, the service type belongs to a predefined service type that is allowed to be triggered, the perception KPI corresponding to the requested service requirement belongs to a predefined perception KPI interval, the time information of the perception request belongs to a predefined time interval, or the application function network element identified by the identifier of the application function network element belongs to a predefined application function network element that is allowed to be triggered.

[0032] Exemplarily, when the perception request carries the identifier of the application function network element, an indication of the perception area, the requested service type, and the requested service requirements, as long as one or more of the identifier of the application function network element, the perception area, the requested service type, and the requested service requirements meet the aforementioned conditions, it is determined that perception of the perception area is permitted. For example, if the identifier of the application function network element and the perception area meet the aforementioned conditions, but the requested service type and the requested service requirements do not meet the aforementioned conditions, it is determined that perception of the perception area is permitted.

[0033] Optionally, the perception request carries at least one of the following: an identifier of an application function network element, an indication of the perception area, a requested service type, and a requested service requirement; before obtaining the target service requirement, the method further includes: obtaining the target service requirement when it is determined that at least one of the following conditions is met: the perception area belongs to a predefined area range, the service type belongs to a predefined service type that is allowed to be triggered, the perception KPI corresponding to the requested service requirement belongs to a predefined perception KPI interval, the time information of the perception request belongs to a predefined time interval, or the application function network element identified by the identifier of the application function network element belongs to a predefined application function network element that is allowed to be triggered.

[0034] Exemplarily, when the perception request carries the identifier of the application function network element, the indication of the perception area, the requested service type, and the requested service requirement, the target service requirement is obtained as long as one or more of the identifier of the application function network element, the perception area, the requested service type, and the requested service requirement meet the above conditions. For example, if the identifier of the application function network element and the perception area meet the above conditions, but the requested service type and the requested service requirement do not meet the above conditions, the target service requirement is obtained.

[0035] Optionally, the perception request comes from an application function network element, and the perception request carries the requested service requirements. The method also includes: sending a service requirement confirmation request to the application function network element, the service requirement confirmation request is used to request the adoption of the target service requirements, and the target service requirements are different from the requested service requirements; receiving a service requirement confirmation reply from the application function network element, the service requirement confirmation reply indicating whether to agree or disagree to adopt the target service requirements.

[0036] Exemplarily, when the business requirement confirmation reply indicates agreement to adopt the target business requirement, a perception process is initiated based on the target business requirement; or, when the business requirement confirmation reply indicates disagreement to adopt the target business requirement, it is determined that perception is not agreed to.

[0037] Optionally, the method further includes: in a case where it is determined that the perception is not agreed, sending a rejection message to the application function network element, where the rejection message is used to reject the perception request.

[0038] Optionally, the method further includes: receiving a parameter configuration request, the parameter configuration request including a correspondence between at least one perception area and at least one service requirement; and determining the mapping relationship according to the parameter configuration request.

[0039] In a second aspect, the present application provides a communication method that can be applied to a communication device. For example, the communication device can be a data management network element, or a component configured in the data management network element (such as a chip, chip system, etc.), or a logic module or software that can implement all or part of the functions of the data management network element, which is not limited by the present application. For ease of understanding and explanation, the method is described below using a data management network element as an example of a communication device.

[0040] Exemplarily, the method includes: receiving a service requirement request from a perception function network element, the service requirement request indicating a perception area; determining N service requirements based on the perception area and a mapping relationship, the mapping relationship indicating a correspondence between at least one perception area and at least one service requirement; and sending the N service requirements to the perception function network element.

[0041] The service requirement request is used to request a target service requirement, and the target service requirement is used to determine the perceived KPI. The N service requirements include the target service requirement, where N is a positive integer.

[0042] Based on this technical solution, the data management network element can obtain at least one business requirement corresponding to the perception area based on the perception area and the mapping relationship after receiving the business requirement for requesting the target business requirement, and send the obtained at least one business requirement to the perception function network element, so that the perception function network element obtains the target business requirement corresponding to the perception area from the received business requirement. Therefore, the method provided in the embodiment of the present application can flexibly respond to the perception request according to the perception area to meet the restrictions on business requirements of different perception areas, and solves the problem that all business requirements are the same when perceiving the same business requirement of different perception areas.

[0043] Optionally, when N=1, the N service requirements are the target service requirements.

[0044] It can be understood that when each of the at least one perception area corresponds to one service requirement, N=1.

[0045] Optionally, when N=1, determining N business requirements based on the perception area and the mapping relationship includes: determining at least one business requirement based on the perception area and the mapping relationship; determining the N business requirements from the at least one business requirement based on the correspondence between at least one business requirement and at least one time period, and the time information of the business requirement request.

[0046] Since at least one service requirement corresponds to at least one time period, the data management network element determines a unique service requirement according to the time information of the service requirement request, and the service requirement is the target service requirement.

[0047] The time information of the service requirement request may be the time when the data management network element receives the service requirement request.

[0048] Optionally, when N>1, the method further includes: sending a correspondence between the N service requirements and N intervals of the number of terminals to the SF network element, so that the SF can determine a target service requirement from the N service requirements based on the correspondence and the number of terminals in the sensing area.

[0049] Optionally, the method also includes: receiving a perception authorization request from a network capability exposure function network element, the perception authorization request is used to request authorization of a perception request from an application function network element, the perception request is used to request perception of a perception area; determining whether to authorize or not authorize the perception request; if authorization is determined, sending an authorization message to the network capability exposure function network element, the authorization message is used to authorize the perception request; or, if not authorization is determined, sending a rejection of authorization message to the network capability exposure function network element, the rejection of authorization message is used to reject authorization of the perception request.

[0050] Optionally, the determining whether to authorize or not to authorize the perception request includes: determining whether to authorize or not to authorize the perception request based on an identifier of the application function network element.

[0051] Optionally, the method further includes: when determining to authorize the perception request based on the identifier of the application function network element, determining whether the service requirements of the request meet the service requirements corresponding to the perception area included in the mapping relationship; and, if satisfied, determining to authorize the perception request; or, if not satisfied, determining to reject the perception request.

[0052] Optionally, the method further includes: receiving a parameter configuration request, the parameter configuration request including a correspondence between at least one perception area and at least one service requirement; and determining the mapping relationship according to the parameter configuration request.

[0053] In a third aspect, the present application provides a communication method that can be applied to a communication device. For example, the communication device can be a data management network element, or a component configured in the data management network element (such as a chip, chip system, etc.), or a logic module or software that can implement all or part of the functions of the data management network element, which is not limited by this application. For ease of understanding and explanation, the method is described below using a data management network element as an example of a communication device.

[0054] Exemplarily, the method includes: receiving a perception authorization request from a network capability exposure function network element, the perception authorization request is used to request authorization of a perception request from an application function network element, the perception request is used to request perception of a perception area; in the case of determining that the perception request is authorized, determining N service requirements based on the perception area and the mapping relationship, the mapping relationship indicating the correspondence between at least one perception area and at least one service requirement; and sending the N service requirements to the network capability exposure function network element.

[0055] Regarding the description of the data management network element determining N business requirements based on the perception area and mapping relationship, please refer to the relevant description in the second aspect and will not be repeated here.

[0056] Based on this technical solution, the data management network element can, when receiving a perception authorization request and determining to authorize the perception request, obtain at least one business requirement corresponding to the perception area based on the perception area and the mapping relationship, and send the obtained at least one business requirement to the network element capability exposure function network element, and then to the perception function network element, so that the perception function network element can obtain the target business requirement corresponding to the perception area from the received business requirement. Therefore, the method provided in the embodiment of the present application can flexibly respond to the perception request according to the perception area to meet the restrictions on business requirements of different perception areas, and solve the problem that all business requirements are the same when perceiving the same business requirement of different perception areas.

[0057] Optionally, N>1, the method further includes: sending the correspondence between the N service requirements and N intervals of the number of terminals to the network capability exposure function network element.

[0058] Optionally, the perception authorization request carries an identifier of an application function network element, and the method further includes: determining whether to authorize or not to authorize the perception request based on the identifier of the application function network element.

[0059] Exemplarily, the application function network element identified by the identifier of the application function network element belongs to a predefined range of application function network elements allowed to be authorized, and the data management network element may determine to authorize the perception request, otherwise the data management network element determines to reject the perception request.

[0060] Optionally, the perception authorization request also carries the requested service requirements, and the method further includes: when determining to authorize the perception request based on the identifier of the application function network element, determining whether the requested service requirements meet the service requirements corresponding to the perception area included in the mapping relationship; and, if not, determining to reject the perception request; or, if satisfied, determining to authorize the perception request.

[0061] In other words, when the data management network element determines to authorize the perception request based on the identifier of the application function network element, it further determines whether the service requirements of the request meet the service requirements corresponding to the perception area included in the above mapping relationship.

[0062] It can be understood that the N service requirements can be carried in the authorization message; the correspondence between the N service requirements and the N intervals of the number of terminals can also be carried in the authorization message.

[0063] Fourthly, the present application provides a communication method that can be applied to a communication device. For example, the communication device can be an application function network element, or a component configured in the application function network element (such as a chip, chip system, etc.), or a logic module or software that can implement all or part of the application function network element functions, which is not limited by the present application. For ease of understanding and explanation, the following describes the method using the application function network element as an example of a communication device.

[0064] Exemplarily, the method includes: receiving a service requirement confirmation request from a perception function network element, the service requirement confirmation request being used to request the adoption of the target service requirement, the target service requirement being different from the requested service requirement; and sending a service requirement confirmation reply to the perception function network element, the service requirement confirmation reply indicating agreement or disagreement to adopt the target service requirement.

[0065] Optionally, when the service requirement confirmation reply indicates that the target service requirement is not adopted, a rejection message is received from the perception function network element, where the rejection message is used to reject the perception request.

[0066] In the fifth aspect, the present application provides a communication method, which is applied to a system including a perception function network element and a data management network element, the method including: the perception function network element receives a perception request, and the perception request is used to request perception of a perception area; the perception function network element sends a service requirement request to the data management network element, and the service requirement request carries the perception area; the data management network element determines N service requirements based on the perception area and the mapping relationship, and the N service requirements include the target service requirements, and the target service requirements are used to determine the perceived KPI; the data management network element sends the N service requirements to the SF.

[0067] The mapping relationship indicates a corresponding relationship between at least one perception area and at least one service requirement. The service requirement request is used to request to obtain a target service requirement.

[0068] Based on this technical solution, after receiving a business requirement for requesting to obtain the target business requirement from the perception function network element, the data management network element can use the perception area as input, determine the business requirement corresponding to the perception area from at least one business requirement included in the mapping relationship, and send the obtained business requirement to the perception function network element, so that the perception function network element obtains the target business requirement corresponding to the perception area from the received business requirement. Therefore, the method provided in the embodiment of the present application can flexibly respond to the perception request according to the perception area to meet the restrictions on business requirements of different perception areas, and solves the problem that all business requirements are the same when perceiving the same business requirement of different perception areas.

[0069] In a sixth aspect, the present application provides a communication method, which is applied to a system including a perception function network element, the method comprising: the perception function network element receives a perception request, the perception request is used to request perception of a perception area; the perception function network element determines a target service requirement based on the perception area, the target service requirement is determined based on the perception area, and the target service requirement is used to determine a perception KPI.

[0070] Based on this technical solution, after receiving a perception request for requesting perception of a perception area, the perception function network element can use the perception area as input to obtain the target service requirements corresponding to the perception area. That is, after receiving different perception requests for requesting perception of different perception areas, the perception function network element can flexibly respond to the perception requests according to the perception area to meet the restrictions on service requirements of different perception areas, solving the problem that all service requirements are the same when perceiving the same service requirements of different perception areas.

[0071] In the seventh aspect, the present application provides a communication method, which is applied to a system including a data management network element, a network open function network element and a perception function network element, the method including: NEF sends a perception authorization request to the data management network element, the perception authorization request is used to request authorization of the perception request from AF, and the perception request is used to request perception of the perception area; when the data management network element determines to authorize the perception request, N business requirements are determined according to the perception area and the mapping relationship, and the mapping relationship indicates the correspondence between at least one perception area and at least one business requirement; the data management network element sends the N business requirements to the network capability exposure function network element; the network open function network element sends a perception request to the perception function network element, and the perception request carries the N business requirements; the perception function network element determines the target business requirements from the N business requirements, and the target business requirements are used to determine the KPI.

[0072] Based on this technical solution, after receiving a business requirement for requesting to obtain the target business requirement from the perception function network element, the data management network element can use the perception area as input, determine the business requirement corresponding to the perception area from at least one business requirement included in the mapping relationship, and send the obtained business requirement to the perception function network element, so that the perception function network element obtains the target business requirement corresponding to the perception area from the received business requirement. Therefore, the method provided in the embodiment of the present application can flexibly respond to the perception request according to the perception area to meet the restrictions on business requirements of different perception areas, and solves the problem that all business requirements are the same when perceiving the same business requirement of different perception areas.

[0073] In an eighth aspect, the present application provides a communication device comprising modules or units for implementing the method in the first to fourth aspects and any possible implementation of the first to fourth aspects. It should be understood that each module or unit can implement the corresponding function by executing a computer program.

[0074] In a ninth aspect, the present application provides a communication device comprising a processor, wherein the processor is configured to execute the method described in the first to fourth aspects and any possible implementation of the first to fourth aspects.

[0075] The apparatus may further include a memory for storing a computer program and / or a configuration file of the logic circuit. The memory is coupled to the processor, and when the processor executes instructions stored in the memory, the method described in the above aspects may be implemented.

[0076] The apparatus may further include a communication interface, where the communication interface is used for the apparatus to communicate with other devices. Exemplarily, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.

[0077] In the tenth aspect, the present application provides a chip system comprising at least one processor for supporting the implementation of the functions involved in the above-mentioned first to fourth aspects and any possible implementation methods of the first to fourth aspects, for example, receiving or processing the data and / or information involved in the above-mentioned method.

[0078] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0079] The chip system can be composed of chips, or can include chips and other discrete devices.

[0080] In one possible design, the chip system further includes an interface circuit and / or a power supply circuit, where the interface circuit is used to transmit data and the power supply circuit is used to supply power to the chip system.

[0081] In the eleventh aspect, the present application provides a computer-readable storage medium comprising a computer program, which, when executed on a computer, enables the computer to implement the method in the above-mentioned first to fourth aspects and any possible implementation of the first to fourth aspects.

[0082] In the twelfth aspect, the present application provides a computer program product, which includes: a computer program (also referred to as code, or instructions), which, when run, enables the computer to execute the method in the above-mentioned first to fourth aspects and any possible implementation of the first to fourth aspects.

[0083] In a thirteenth aspect, the present application provides a communication system, including the aforementioned perception function network element and data management network element.

[0084] Optionally, the communication system may be used to implement the method described in the fifth aspect and any possible implementation manner of the fifth aspect.

[0085] It should be understood that the eighth to thirteenth aspects of the present application correspond to the technical solutions of the first to fourth aspects of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] FIG1 is a schematic diagram of a converged architecture of a communication system provided in an embodiment of the present application;

[0087] FIG2 is a schematic diagram of an independent architecture of a communication system provided in an embodiment of the present application;

[0088] FIG3 is a schematic diagram of a network architecture based on a service-based architecture (SBA) according to an embodiment of the present application;

[0089] FIG4 is a schematic diagram of a base station performing a sensing operation;

[0090] Figure 5 is a schematic diagram of parameters that affect perception accuracy and resolution;

[0091] 6 to 9 are schematic flow charts of the communication method provided in the embodiments of the present application;

[0092] 10 and 11 are schematic block diagrams of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0093] The technical solution in this application will be described below with reference to the accompanying drawings.

[0094] To facilitate understanding of the embodiments of the present application, the following points are first explained:

[0095] First, in the embodiments of this application, prefixes such as "first" and "second" are used solely to distinguish between different things belonging to the same category and do not constrain the order, size, or quantity of the things. For example, "first mapping relationship" and "second mapping relationship" are simply different mapping relationships; there is no temporal order, size, or priority relationship between the two.

[0096] Second, "sending" and "receiving" in the embodiments of the present application indicate the direction of signal transmission. For example, "sending a perception authorization request to unified data management (UDM)" can be understood as the destination end of the perception authorization request being UDM, and may include other units or modules indirectly sending to UDM. "Receiving a perception authorization request from the network explosure function (NEF)" can be understood as the source end of the perception authorization request being NEF, and may include indirectly receiving from NEF from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface.

[0097] In other words, sending and receiving can be performed between devices, for example, between NEF and UDM; or it can be performed within the device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, traces or interface.

[0098] It is understood that before information is sent from the source to the destination, it may undergo necessary processing, such as encoding and modulation. After receiving the information from the source, the destination may also perform corresponding processing, such as decoding and demodulation, to interpret the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.

[0099] Third, in the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship, but does not exclude the situation where the previous and next associated objects are in an "and" relationship. The specific meaning can be understood in conjunction with the context. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, c can be single or multiple.

[0100] Fourth, in the embodiments of the present application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. The information indicated by a certain information (such as the indication information described below) is called information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated may also be indirectly indicated by indicating other information, wherein the other information has an association relationship with the information to be indicated; or only a part of the information to be indicated may be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information may be achieved by means of the arrangement order of each information agreed in advance (such as predefined by the protocol), thereby reducing the indication overhead to a certain extent. The present application does not limit the specific method of indication.

[0101] It can be understood that, for the sender of the indication information, the indication information can be used to indicate the information to be indicated, and for the receiver of the indication information, the indication information can be used to determine the information to be indicated.

[0102] Fifth, the tables in the embodiments of the present application are only examples. The values ​​of the information in each table are only examples and can be configured as other values, which are not limited by the present application. The tables do not limit the scope of protection of the present application. For example, appropriate deformation adjustments can be made based on the tables in the above text, such as splitting, merging, etc. For another example, the parameter names shown in the titles of the tables can also use other names that can be understood by the communication device, and the values ​​or representations of the parameters can also use other values ​​or representations that can be understood by the communication device. For another example, when implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.

[0103] Sixth, in the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that the device (such as the sensing function (SF) or UDM) will make corresponding processing under certain objective circumstances. It does not limit the time, and does not require the device (such as SF or UDM) to have a judgment action when implemented, nor does it mean that there are other limitations.

[0104] Seventh, the predefined in this application can be understood as: define, predefine, store, pre-store, pre-negotiate, pre-configure, solidify, or pre-burn.

[0105] The technical solutions provided in this application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, sidelink (SL) communication system, world-wide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) mobile communication system or new radio access technology (NR), satellite communication system, etc. Among them, the 5G mobile communication system can include non-standalone (NSA) and / or standalone (SA) networking.

[0106] The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation (6G) mobile communication system, etc. This application does not limit this.

[0107] For ease of understanding, the network architecture applicable to the method provided in the embodiment of the present application is first described in more detail with reference to the accompanying drawings.

[0108] Figures 1 and 2 show two possible architectures in 5G networks: a converged architecture (see Figure 1) and a standalone architecture (see Figure 2). The difference between the converged architecture and the standalone architecture lies in the location of the service-specific SF deployment.

[0109] As shown in Figure 1, in a converged architecture, SF can be deployed in the traditional 5G core network (5GC) and connected to other network elements using the SBA interface. A more detailed description of SBA can be found in Figure 3 and will not be described in detail here. SF is connected to NEF and can interact with servers outside the 5GC through NEF, such as receiving perception request messages from external servers. SF can also be connected to the user plain function (UPF), and radio access network (RAN) equipment such as base stations can send received perception data to SF for processing through the user plane.

[0110] As shown in Figure 2, in a standalone architecture, the SF can be deployed outside the traditional 5GC. The SF cannot connect to other network elements using the SBA interface and may need to interact with other 5GC network elements through the NEF. Alternatively, the SF can connect to the NEF and interact with external servers through the NEF. Alternatively, the SF can interact directly with external servers without the NEF. Alternatively, the SF can connect to RAN equipment to interact with terminal devices.

[0111] It should be understood that the two possible architectures shown in Figures 1 and 2 are merely examples of the 5GC architecture and should not constitute any limitation on the present application. The method provided in this application is not limited to use in the two architectures shown in Figures 1 and 2.

[0112] Figure 3 is a schematic diagram of the network architecture of SBA in a 5G network provided by an embodiment of the present application. As shown in Figure 3, the 5G network architecture may include three parts: terminals, data networks (DNs), and operator networks.

[0113] The following is a brief description of the network elements involved in Figures 1 to 3.

[0114] A terminal may also be referred to as user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal device, a wireless communication device, a user agent, or a user device.

[0115] A terminal is a device with wireless transceiver capabilities. It communicates with one or more core network (CN) devices (also called core devices) via access network equipment (also called access devices) within a wireless access network. Terminals can be deployed on land, indoors or outdoors, handheld or in vehicles; on water (such as ships); or in the air (such as aircraft, balloons, and satellites).

[0116] A terminal can also be a terminal in the Internet of Things (IoT) system, also known as an IoT node. IoT is a crucial component of future information technology development. Its primary technical feature is connecting objects to the Internet through communication technologies, thereby enabling intelligent networks that interconnect humans and machines, and objects and things. Connections can be achieved through broadband or narrowband (NB) technology. IoT technology, for example, utilizes narrowband technology to achieve massive connections, deep coverage, and power-saving terminals.

[0117] In the embodiments of the present application, the device for implementing the functions of the terminal may be a terminal, or a device capable of supporting the terminal in implementing the functions, such as a chip system, which may be installed in the terminal or used in conjunction with the terminal. In the embodiments of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices. In the embodiments of the present application, only the terminal is used as an example to illustrate the device for implementing the functions of the terminal, and the embodiments of the present application are not limited to the solutions of the embodiments of the present application.

[0118] The terminal in this application can be a hardware device, a software function running on dedicated hardware, a software function running on general-purpose hardware, or a virtualized device, for example, implemented by general-purpose hardware and instantiated virtualization functions, or by dedicated hardware and instantiated virtualization functions. The general-purpose hardware can be a server, such as a cloud server.

[0119] Among them, the operator network may include one or more of the following network elements: network slice selection function (NSSF) network element, NEF network element, network repository function (NRF), policy control function (PCF), UDM network element, application function (AF) network element, authentication server function (AUSF) network element, access and mobility management function (AMF) network element, session management function module (SMF) network element, UPF network element, SF network element, and access network (AN) (such as RAN network element). In the above-mentioned operator network, the part other than the RAN network element can be referred to as the core network part. For the convenience of explanation below, the term "network element" is omitted, for example, the AF network element is referred to as AF, the UDM network element is referred to as UDM, the SF network element is referred to as SF, and so on.

[0120] The RAN is a network consisting of multiple RAN nodes that implements radio physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management. The 5G-RAN connects to the user plane function (UPF) via the user plane interface (N3) to transmit data from terminal devices. The 5G-RAN establishes 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.

[0121] RAN nodes provide wireless communication services and connect terminals to wireless networks. RAN nodes can also be called RAN devices or access network devices.

[0122] In one possible scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a sixth-generation (6G) mobile communication system, or a base station in a future mobile communication system. A RAN node may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or a radio controller in a cloud radio access network (CRAN) scenario. Optionally, a RAN node may also be a server.

[0123] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0124] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in an open access network (open RAN, O-RAN or ORAN) system, CU may also be called open CU (O-CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0125] In the embodiments of the present application, the device for implementing the functions of a RAN node may be the RAN node itself; or it may be a device capable of supporting the RAN node in implementing the functions, such as a chip system, a hardware circuit, a software module, or a combination of a hardware circuit and a software module. The device may be installed in the RAN node or used in conjunction with the RAN node. The embodiments of the present application are described using the RAN node as an example, and do not limit the embodiments of the present application.

[0126] The RAN node in this application can be a hardware device, a software function running on dedicated hardware, a software function running on general-purpose hardware, or a virtualized device, for example, implemented by general-purpose hardware and instantiated virtualization functions, or by dedicated hardware and instantiated virtualization functions. The general-purpose hardware can be a server, such as a cloud server.

[0127] SF is mainly responsible for the related processing of perception services, such as determining the perception results based on the acquired perception data, such as whether there is an intrusion, or calculating the distance, direction and position of reflective objects in the perception area.

[0128] AMF is mainly responsible for terminal authentication, terminal mobility management (MM), network slice selection, and SMF selection. It serves as the anchor point for N1 and N2 signaling connections and provides routing for N1 / N2 session management (SM) messages for SMF. It also maintains and manages terminal status information.

[0129] The SMF is primarily responsible for all control plane functions of terminal session management, including UPF selection, Internet Protocol (IP) address allocation, session quality of service (QoS) management, and obtaining PCC (policy and charging control) strategies (from PCF).

[0130] As the anchor point for protocol data unit (PDU) session connections, the UPF is responsible for filtering terminal data packets, data transmission / forwarding, rate control, and generating billing information.

[0131] UDR is mainly used to store user data, including contract data called by UDM, policy information called by PCF, structured data for capability exposure, and application data called by NEF.

[0132] UDM is mainly used to manage and control user data, such as the management of contract information, including obtaining contract information from UDR and providing it to other network elements (such as AMF); generating 3GPP authentication credentials for the terminal; and registering and maintaining the network element currently serving the terminal (for example, the AMF represented by AMF ID1 is the terminal's current serving AMF, serving AMF)).

[0133] NEF is used to connect other internal network elements of the core network and the application function (AF) network elements corresponding to the application server (AS) outside the core network to provide network open capabilities to AF, or provide information provided by AF to core network network elements.

[0134] The AUSF authentication server function is used to perform security authentication on the terminal when the terminal accesses the network.

[0135] The PCF mainly controls quality of service (QoS) and charging policies, provides configuration policy information to terminals, and provides policy information for managing and controlling terminals to network control plane elements (such as AMF and SMF).

[0136] The AF primarily communicates application-side requirements to the network and can be considered an application server or an application server proxy. The AF can interact with core network elements to provide services. For example, it can interact with the PCF to control service policies, 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 data services.

[0137] DN mainly provides business services to users.

[0138] Each network element communicates with each other through an interface. For example, the interface between the terminal and the AMF is the N1 interface, the interface between the AN and the AMF is the N2 interface, the interface between the AN and the UPF is the N3 interface, the interface between the SMF and the UPF is the N4 interface, and the interface between the UPF and the DN is the N6 interface. Some network elements can communicate based on service-based interfaces. Among them, Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nausf, Namf, Nsmf, and Nsf in Figure 1 are service-based service interfaces. Among them, the interface Nsf is only one possible name, and this application does not limit the name of the service-based interface corresponding to the SF.

[0139] The above description of the various network elements in the core network and the interfaces between them is merely illustrative and does not constitute any limitation on this application. Furthermore, the various network elements shown in the figure can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of these network elements.

[0140] It can be understood that the network elements used in future communication systems can be the above-mentioned network elements, or can be network elements with other names that have the same or similar functions. This application does not limit this.

[0141] In the embodiments of the present application, the apparatus for implementing each core network function may be a core network element corresponding to each function; or it may be a device capable of supporting the core network element in implementing its respective function, such as a chip system, hardware circuit, software module, or a combination of hardware circuit and software module. The apparatus may be installed in the core network element or used in conjunction with the core network element. The embodiments of the present application are described using the core network element as an example, and do not limit the embodiments of the present application.

[0142] The core network element in this application can be a hardware device, a software function running on dedicated hardware, a software function running on general-purpose hardware, or a virtualized device, for example, implemented by general-purpose hardware and instantiated virtualization functions, or by dedicated hardware and instantiated virtualization functions. The general-purpose hardware can be a server, such as a cloud server.

[0143] Currently, some base stations or terminals in the RAN possess electromagnetic wave sensing capabilities and can be used as sensing nodes. The implementation of sensing is similar to the principle of radar. Specifically, a transmitter (i.e., a sensing node) emits electromagnetic waves, which are reflected by the object to be sensed and then captured by a receiver. The receiver (i.e., a sensing node) further processes the reflected signal (referred to as raw sensing data) to generate sensing data, which can be used to generate sensing results.

[0144] For example, when a base station is used as a sensing node, it has the functions shown in Table A and Figure 4. Table A is an example of the sensing capabilities of speed radar, monitoring radar, and imaging radar.

[0145] Table A

[0146] Figure 4 is a schematic diagram of a base station performing a sensing operation. Figure 4 is an example of integrated sensing and communication (ISAC). The base station shown in Figure 4 can reuse the electromagnetic wave signals of the communication system for sensing. As shown in Figure 4, the resources used by the base station for communication and sensing can be time-division multiplexed (as shown in Figure 4) or space-division multiplexed. The base station can use electromagnetic wave signals for sensing and detection, and can also receive signals (reflected signals or echo signals) that are transmitted after reaching obstacles (i.e., detected targets) and obtain sensing data based on the echo signals. As shown in Figure 4, the base station can perform serial-to-parallel conversion, phase shift keying, inverse fast Fourier transform (IFFT), parallel-to-serial conversion, digital-to-analog conversion, etc. on the signals to be transmitted. The base station can also perform analog-to-digital conversion, parallel-to-serial conversion, fast Fourier transform (FFT), serial-to-parallel conversion, demodulation, etc. on the received echo signals. The signal to be transmitted may also be sent to the radar processor, so that the radar processor can obtain sensing data based on the signal to be transmitted and the received echo signal (it should be understood that the echo signal here is the echo signal after the above processing). It should be understood that the processing performed by the base station on the signal to be transmitted and the received echo signal shown in Figure 4 is only an example and should not constitute any limitation to this application.

[0147] The sensing nodes in the communication system can sense and identify designated areas, objects, or events, meeting the sensing needs in many areas such as autonomous driving, safety supervision, family health, and weather monitoring. Specific examples are as follows:

[0148] 1. Autonomous Driving

[0149] In V2X and unmanned aerial vehicle (VAU) scenarios, for example, since the perception distance of vehicles or drones is short or non-line of sight (NLOS) paths cannot be perceived, dynamic maps can be generated based on perception data; for example, during the driving process of vehicles or drones, there may be traffic hazards such as the sudden appearance of pedestrians or non-motor vehicles, or pedestrians or non-motor vehicles are in blind spots. Dangerous events can be identified based on perception data and the vehicle or drone can be notified to perform emergency operations; for example, in vehicle or drone autonomous driving assistance, customized high-precision dynamic maps can be generated based on perception data to assist vehicles or drones in autonomous driving.

[0150] 2. Safety Supervision

[0151] In V2X and drone scenarios, it is possible to identify vehicles or drones driving in violation of regulations based on perception data, such as vehicles occupying emergency lanes or drones leaving their routes, and to issue real-time warnings.

[0152] In perimeter security scenarios, based on perception data, it is possible to detect situations such as foreign objects intruding into railway tracks or drones intruding into no-fly zones (such as airports), track illegal objects, and perform real-time emergency response.

[0153] 3. Family Health

[0154] For example, abnormal postures can be identified based on perception data, so that falls and other situations can be identified and timely alarms can be issued; for another example, physiological parameters such as human breathing or heartbeat can be obtained through perception data, so that abnormalities can be identified and timely alarms can be issued.

[0155] 4. Meteorological Monitoring

[0156] It can perceive and predict the environment, climate, weather changes, etc.

[0157] Figure 5 is a schematic diagram of parameters that influence perception accuracy and resolution. Using the Internet of Vehicles (IoV) scenario as an example, Figure 5 illustrates several parameters that influence perception key performance indicators (KPIs): positioning accuracy (both vertical and horizontal), velocity accuracy (both vertical and horizontal), and resolution (both area and velocity).

[0158] 1. Range resolution α: The ability to distinguish adjacent targets at distance, usually measured as the minimum resolvable distance interval, used to identify different vehicles.

[0159] 2. Velocity resolution β: the ability to distinguish targets in radial velocity.

[0160] 3. Angular accuracy θ: The ability of the radar to distinguish adjacent targets in terms of angle, usually measured by the minimum resolvable angle.

[0161] 4. Horizontal field of view (FOV): 120°. For a 30-meter-wide two-way road, the two-way blind spot is less than 18 meters, and the blind spot area ratio is less than 1%.

[0162] In 5G, sensing nodes can be either the RAN or the terminal. Different sensing node combinations yield various sensing modes. Table 1 lists six sensing modes, based on the sensing node's role in the sensing process (transmitter or receiver) and its type (RAN or terminal).

[0163] Table 1

[0164] The six sensing modes shown in Table 1 are differentiated based on the transmitter and receiver of the sensing signal. They are: RAN node self-transmitting and self-receiving, RAN node A transmitting and RAN node B receiving, RAN node transmitting and terminal receiving, terminal transmitting and RAN node receiving, terminal self-transmitting and self-receiving, and terminal A transmitting and terminal B receiving. As can be seen, the transmitter can be either a terminal or a RAN node, and the receiver can be either a terminal or a RAN node.

[0165] In order to better understand the method provided in the embodiments of the present application, the terms involved in the present application are briefly explained below.

[0166] 1. Perception Key Performance Indicators (KPIs): The 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 22.173 defines the following parameters for perception KPIs: confidence interval, perceived positioning accuracy (both vertical and horizontal), perceived velocity accuracy (both vertical and horizontal), perceived resolution (including area and velocity), maximum perceived service latency, and refresh rate. These parameters describe the required accuracy of perception data.

[0167] Of course, these parameters are only an example of perceived KPIs, and this application does not limit the specific parameters included in the perceived KPIs.

[0168] In the existing perception process, the AF / application server (AS) of a perception application can send a perception request message to the NEF. The perception request carries the service type, service requirements, and external area information, requesting the network to perform perception based on the perception request information and provide feedback on the corresponding perception results. The AF, AS, or terminal hosting the perception application can also directly send a perception request message to the network element responsible for perception in the communication network. The service requirements are the requirements that the perception application places on the network for the accuracy of the perception results.

[0169] In the existing perception process, perception applications may impose the same service requirements for the same service type in all areas. However, in actual perception scenarios, different perception areas may have different perception accuracy limitations. For example, in residential areas, accuracy may need to be reduced to protect personal privacy, while in open environments, drone intrusion detection requires higher accuracy to eliminate false alarms caused by objects such as birds. In other words, the service requirements for different perception areas may vary. Therefore, if perception continues to be performed according to the existing perception process, it may not be possible to meet the service requirements of different perception areas.

[0170] In view of this, an embodiment of the present application provides a communication method and related devices and systems. In this method, when the network side receives a perception request from a perception application, the business requirements corresponding to the perception area are determined through the correspondence between the perception area carried by the perception request and the perception area and business requirements pre-stored on the network side, so as to meet the restrictions on perception accuracy in different areas.

[0171] The method provided in the embodiment of the present application is described in detail below in conjunction with Figures 6 to 9. The method provided in the embodiment of the present application can be applied to the network architecture shown in Figure 1 or Figure 2, but the embodiment of the present application is not limited thereto.

[0172] Figure 6 is a schematic flow chart of a communication method 600 provided in an embodiment of the present application. As shown in Figure 6, the method 600 may include S601 and S602. The steps in the method 600 are described in detail below.

[0173] S601: The NEF sends a sensing request to the SF, where the sensing request is used to request sensing of a sensing area. Correspondingly, the SF receives the sensing request from the NEF.

[0174] Alternatively, in S601, the AF sends a sensing request to the SF. Correspondingly, the SF receives the sensing request from the terminal. In this case, the AF does not send the sensing request to the AF via the NEF.

[0175] Alternatively, in S601, the terminal sends a sensing request to the SF, and correspondingly, the SF receives the sensing request from the terminal.

[0176] Among them, the perception request indicates the above-mentioned perception area. The perception area is used to describe the area that needs to be perceived, and the perception area can be described by an identifier of the area to be perceived in the communication system or outside the communication system. The perception area may include one or more of the following: coordinate information, geographic area identifier, address information, tracking area identifier (TAI), cell identifier (cell identifier, cell ID). It should be noted that the perception area may be other information, and this application does not limit this. For the convenience of description below, the perception request from NEF is referred to as perception request #1, and the perception area indicated in perception request #1 is referred to as perception area #1. That is, perception request #1 is used to request perception of perception area #1. The perception request from AF is referred to as perception request #2, and the perception area indicated in perception request #2 is referred to as perception area #2. That is, perception request #2 is used to request perception of perception area #2.

[0177] Sensing area #1 is the identification of the sensing area within the communication system, and sensing area #2 is the identification of the sensing area outside the communication system. Since the AF does not know the identification of the sensing area within the communication system, the sensing area indicated by the AF is the identification of the sensing area outside the communication system to distinguish it from the identification of the sensing area within the communication system.

[0178] Optionally, the perception request received by the SF may also carry at least one of the following items: the AF identifier, the requested service type (hereinafter referred to as service type #1 for convenience of description) and the requested service requirement (hereinafter referred to as service requirement #1 for convenience of description).

[0179] The AF identifier may be an AF ID or other information that can identify the AF.

[0180] Service type #1 is the perception service type information corresponding to the perception request (for example, intrusion detection, traffic flow monitoring, etc.).

[0181] Service type #1 may be one or more of at least one predefined service type. The at least one service type may include, but is not limited to, drone intrusion detection, autonomous driving, security monitoring, home health, or weather monitoring, etc., and the present application includes but is not limited to these.

[0182] Service Type #1 indicates one or more of at least one predefined service type. The service requirements of the request can be used to describe the requirements for the requested perception results. For example, the service requirements may include one or more of the following: perceived location accuracy, perceived velocity accuracy, perceived resolution, or required perception duration. The service requirements can be used to determine the KPIs corresponding to the perception results requested in the perception request.

[0183] S602: SF obtains target service requirements, which are determined according to the sensing area.

[0184] The target business requirement is used to determine the perceived KPIs.

[0185] The target service requirement may be a KPI or may include information used to determine the KPI. If the target service requirement includes information used to determine the KPI, the SF may convert the target service requirement into a KPI. In other words, one possible implementation method for the SF to determine the KPI for perceiving the perception area based on the target service requirement is to determine the target service requirement as a KPI for perceiving the terminal. Another possible implementation method is to convert the target service requirement into a KPI for perceiving the perception area.

[0186] Optionally, the SF obtaining the target service requirement may include: the SF obtaining the target service requirement according to the sensing area; or the UDM obtaining the target service requirement according to the sensing area and returning the result to the SF.

[0187] For example, if the sensing area is a residential area, the privacy of users in the residential area needs to be protected during sensing. Therefore, the target service requirements can be determined as those with lower sensing accuracy. This method of determining target service requirements based on the sensing area can effectively prevent the exposure of user privacy, reduce the leakage of sensitive information, and effectively and flexibly provide network openness.

[0188] Exemplarily, the SF obtains the target service requirement based on the sensing area, including: the SF obtains the target service requirement based on the sensing area and the first mapping relationship. The UDM obtains the target service requirement based on the sensing area, including: the UDM obtains the target service requirement based on the sensing area and the first mapping relationship. Because the specific manner in which the SF obtains the target service requirement will be described in detail later, it is not described in detail here.

[0189] The first mapping relationship in this application indicates that at least one perception area corresponds to at least one service requirement. It should be understood that each perception area in the at least one perception area may correspond to one service requirement; or the at least one perception area may include a specific perception area that corresponds to multiple service requirements.

[0190] It should be understood that the service requirements corresponding to different perception areas may be the same or different.

[0191] The at least one service requirement may include a default service requirement. The default service requirement may be a predefined service requirement. Alternatively, the default service requirement is used to indicate that the service requirement requested in the perception request is determined as the target service requirement. Alternatively, the default service requirement is defined as the service requirement requested by the perception request, without preconfiguring the default service requirement.

[0192] Table 2

[0193] Table 2 shows an example of a first mapping relationship. Position 1, Position 2, and Position 3 shown in Table 2 represent three different perception areas, and the first mapping relationship is used to represent the service requirements corresponding to the three positions of the same service type. The default service requirement is higher than the medium service requirement, and the medium service requirement is higher than the minimum service requirement. For example, the perceived location accuracy in the indicator corresponding to the minimum business requirement is 1m, the perceived location accuracy in the indicator corresponding to the medium business requirement is 1cm, and the perceived location accuracy in the indicator corresponding to the default business requirement is 1mm. Since the accuracy of 1m, 1cm, and 1mm increases in sequence, the level of the default business requirement can be considered to be higher than the medium business requirement, and the level of the medium business requirement is higher than the minimum business requirement. For another example, the perceived resolution in the indicator corresponding to the minimum business requirement is 1m, the perceived resolution in the indicator corresponding to the medium business requirement is 1cm, and the perceived resolution in the indicator corresponding to the default business requirement is 1mm. Since the accuracy of 1m, 1cm, and 1mm increases in sequence, the level of the default business requirement can be considered to be higher than the medium business requirement, and the level of the medium business requirement is higher than the minimum business requirement. For another example, the perceived service delay in the indicator corresponding to the minimum business requirement is 1s, the perceived service delay in the indicator corresponding to the medium business requirement is 1ms, and the perceived service delay in the indicator corresponding to the default business requirement is 0.1ms. Since the accuracy of 1s, 1ms, and 0.1ms increases in sequence, the level of the default business requirement can be considered to be higher than the medium business requirement, and the level of the medium business requirement is higher than the minimum business requirement.

[0194] In an embodiment of the present application, after receiving a perception request for requesting perception of a perception area, SF can use the perception area as input to obtain the target business requirements corresponding to the perception area. That is, after receiving different perception requests for requesting perception of different perception areas, SF can flexibly respond to the perception requests according to the perception areas to meet the restrictions on business requirements of different perception areas, solving the problem that all business requirements are the same when perceiving the same business requirements of different perception areas.

[0195] Optionally, before S601, the method 600 also includes: the NEF sends a perception authorization request to the UDM, which is used to request authorization for a perception request from the AF (hereinafter, for the convenience of description, the perception request from the AF is referred to as perception request #2), which is used to request perception of perception area #2 (for example, a specific location or geographical range); the UDM receives the perception authorization request from the NEF and determines whether to authorize or not to authorize the perception request #2; if authorization is determined, the UDM sends an authorization message to the NEF, which is used to authorize the perception request; or, if not authorization is determined, the UDM sends a rejection of authorization message to the NEF, which is used to reject authorization of the perception request.

[0196] It should be noted that the NEF may continue to execute S601 when the UDM determines that the awareness request is authorized.

[0197] The above-mentioned sensing authorization request indicates sensing area #1, and the above-mentioned sensing request #2 indicates sensing area #2. It should be understood that the sensing areas indicated by sensing request #1 and sensing request #2 correspond to the same geographical location, except that the geographical location indicated by sensing request #1 is in a format that can be recognized by the operator network.

[0198] Exemplarily, the perception authorization request carries the identifier of the AF; the above-mentioned UDM determines whether to authorize or not the perception request, which may include: determining whether to authorize or not the perception request based on the identifier of the AF.

[0199] For example, if the AF identified by the AF identifier belongs to a predefined range of AFs allowed to be authorized, the UDM may determine to authorize the perception request; otherwise, the UDM determines not to authorize the perception request.

[0200] Optionally, the perception authorization request also carries business requirement #1, and the method 600 also includes: UDM determines whether business requirement #1 meets the business requirement corresponding to the perception area #1 included in the first mapping relationship; and, if the business requirement corresponding to the perception area #1 included in the first mapping relationship is met, determines to authorize the perception request; or, if the business requirement corresponding to the perception area #1 included in the first mapping relationship is not met, determines to reject the perception request.

[0201] The above-mentioned business requirement #1 satisfies the business requirement corresponding to the perception area #1 included in the first mapping relationship, which means that the level of business requirement #1 is not higher than the level of the first type of business requirement, and the first type of business requirement is the business requirement corresponding to the perception area #1 included in the first mapping relationship.

[0202] The following are several examples of a first-category service requirement with a higher level than requested service requirement #1: 1. The perceived location accuracy in the metrics corresponding to the first-category service requirement is 1mm, while the perceived location accuracy in the metrics corresponding to service requirement #1 is 1m. Since 1mm accuracy is higher than 1m accuracy, the first-category service requirement is considered to have a higher level than service requirement #1. 2. The perceived resolution in the metrics corresponding to the first-category service requirement is 1m, while the perceived resolution in the metrics corresponding to service requirement #1 is 5m. Since 1m resolution is higher than 5m resolution, the first-category service requirement is considered to have a higher level than service requirement #1. 3. The maximum perceived service latency in the metrics corresponding to the first-category service requirement is 0.2ms, while the maximum perceived service latency in the metrics corresponding to service requirement #1 is 0.5ms. Since 0.2ms latency is shorter than 0.5ms latency, the first-category service requirement is considered to have a higher level than service requirement #1.

[0203] Optionally, before the NEF sends a perception authorization request to the UDM, the method 600 also includes: the AF sends a perception request #2 to the NEF, where the perception request #2 is used to request perception of the perception area #2, and the perception request #2 indicates the perception area #2; the NEF receives the perception request #2 and determines the perception area #2 as the perception area #1.

[0204] For the description of perception area #2 and perception area #1, please refer to the relevant description above and will not be repeated here.

[0205] Optionally, in S602 SF obtains the target service requirements, which may include the following three implementation methods.

[0206] A first possible implementation: SF determines N service requirements according to the sensing area #1 and the first mapping relationship; and obtains a target service requirement from the N service requirements, where N is a positive integer.

[0207] Optionally, when N>1, SF obtains the target service requirement from the N service requirements, including: SF obtains the target service requirement from the N service requirements according to the number of terminals included in the perception area #1 or time information of the perception request.

[0208] For example, the time information of the perception request indicates that the time is during the morning or evening rush hour, such as 7:00-9:00, or 17:00-19:00. When detecting the traffic flow of cars on the road, in order to avoid detecting buses, the target business requirement can be determined as a business requirement with higher perception accuracy.

[0209] For another example, the more terminals included in the perception area, the higher the processing complexity of the perception node, so a low-level business requirement can be used to perceive the perception area; if the number of terminals included in the perception area is small, when perceiving the perception area, the processing capability requirements for the perception node are lower, so a higher-level business requirement can be used to perceive the perception area.

[0210] The time information of the perception request in this application can be used to indicate one or more of the following: the time when the AF initiates the perception request #2, the time when the SF receives the perception request #1, the time when the UDM receives the perception authorization request, or the time of the requested perception carried in the perception request.

[0211] Exemplarily, when N>1, SF obtains the target service requirement from N service requirements based on the number of terminals contained in perception area #1, including: SF obtains the target service requirement from N service requirements based on the correspondence between N service requirements and N intervals of the number of terminals, and the number of terminals contained in perception area #1.

[0212] Exemplarily, when N>1, the SF obtains the target service requirement from the N service requirements based on the time information of the perception request, including: the SF obtains the target service requirement from the N service requirements based on the correspondence between the N service requirements and the N time periods and the time information of the perception request. Exemplarily, the number of terminals included in the perception area #1 in the embodiment of the present application can be obtained from the AMF.

[0213] Table 3

[0214] Table 3 shows the correspondence between N service requirements and N intervals of the number of terminals when N = 4. As shown in Table 3, it represents the service requirements corresponding to 4 intervals of the number of terminals of a specific service type in a specific sensing area.

[0215] Table 4

[0216] Table 4 shows the correspondence between N service requirements and N time periods when N = 2. For example, Table 4 shows the service requirements corresponding to two time periods of a specific service type in a specific sensing area.

[0217] Optionally, when N>1, SF obtains the target service requirement from the N service requirements, including: SF obtains the target service requirement from the N service requirements according to the number of terminals included in the perception area #1 and the time information of the perception request.

[0218] For example, the time information of the perception request indicates the time during the morning or evening rush hour, such as 7:00-9:00 or 17:00-19:00. Since there are more terminals on the subway during these peak hours, higher perception accuracy may lead to the leakage of some privacy or sensitive information. Therefore, the target service requirement can be determined as a service requirement with lower perception accuracy. This method of determining the target service requirement by combining the perception area, the time of the perception request, and the number of terminals within the perception area can effectively prevent the exposure of user privacy, reduce the leakage of sensitive information, and effectively and flexibly provide network openness.

[0219] Exemplarily, when N>1, SF obtains the target service requirement from the N service requirements based on the number of terminals included in the perception area #1 and the time information of the perception request, including: SF determines M (M is an integer greater than 0 and less than N) service requirements from the N service requirements based on the second mapping relationship and the time information of the perception request; SF obtains the target service requirement from the M service requirements based on the correspondence between the M service requirements and the M intervals of the number of terminals, and the number of terminals included in the perception area #1.

[0220] Exemplarily, when N>1, SF obtains the target business requirement from N business requirements based on the number of terminals included in perception area #1 and the time information of the perception request, including: SF determines M business requirements from N business requirements based on the third mapping relationship and the number of terminals included in perception area #1; SF obtains the target business requirement from the M business requirements based on the correspondence between the M business requirements and the M time periods, and the time information of the perception request.

[0221] The second mapping relationship indicates that at least one time period corresponds to at least one service requirement; the third mapping relationship indicates that at least one interval of the number of terminals corresponds to at least one service requirement.

[0222] It can be understood that when the first time period in at least one time period corresponds to multiple service requirements, SF can determine multiple service requirements from N service requirements based on the second mapping relationship and the time information of the perception request, and the first time period is the time period to which the time information of the perception request belongs.

[0223] Similarly, when the first interval in at least one interval of the number of terminals corresponds to multiple service requirements, SF can determine multiple service requirements from N service requirements based on the third mapping relationship and the number of terminals contained in the perception area #1, and the first interval is the interval to which the number of terminals contained in the perception area #1 belongs.

[0224] Table 5

[0225] Table 5 shows an example of a second mapping relationship. As shown in the example in Table 5, it represents the service requirements corresponding to the time period and the number of terminals of a specific service type in a specific sensing area.

[0226] Table 6

[0227] Table 6 shows an example of a third mapping relationship. As shown in the example in Table 6, the service requirements corresponding to the interval and time period of the number of terminals of a specific service type in a specific sensing area are shown.

[0228] Exemplarily, when N>1, SF obtains the target service requirement from N service requirements based on the number of terminals included in perception area #1 and the time information of the perception request, including: SF obtains the target service requirement from N service requirements based on a fourth mapping relationship, the time information of the perception request and the number of terminals included in perception area #1, and the fourth mapping relationship indicates the correspondence between at least one time period, at least one interval of the number of terminals, and at least one service requirement.

[0229] For examples of the fourth mapping relationship, please refer to Table 5 and Table 6. The difference is that SF obtains the target business requirements directly from N business requirements based on the time information of the perception request and the number of terminals included in the perception area #1, rather than first screening out M business requirements from the N business requirements and then obtaining the target business requirements from the M business requirements.

[0230] Optionally, when the service type #1 is carried in the perception request #1, before S602, the method 600 further includes: the SF determines at least one perception area according to the service type #1; and determines the perception area #1 from the at least one perception area.

[0231] Exemplarily, the SF determines at least one perception area according to service type #1, including: the SF determines at least one perception area according to service type #1 and a fifth mapping relationship, where the fifth mapping relationship indicates that at least one service type corresponds to at least one perception area.

[0232] It can be understood that the perception areas corresponding to the service type #1 included in the fifth mapping relationship include the perception area #1.

[0233] Table 7

[0234] Table 7 shows a fifth mapping relationship. The fifth mapping relationship shown in Table 7 includes two service types, and each service type corresponds to two sensing areas.

[0235] The second possible implementation is: SF sends a service requirement request to UDM, where the service requirement request is used to request the target service requirement, and the service requirement request indicates perception area #1; UDM receives the service requirement request and determines N service requirements based on the perception area #1 indicated by the service requirement request; UDM sends the N service requirements to SF; SF receives the N service requirements and obtains the target service requirement from the N service requirements.

[0236] Exemplarily, the UDM determines N service requirements according to the sensing area #1 indicated by the service requirement request, including: the UDM determines the N service requirements according to the sensing area #1 indicated by the service requirement request and the first mapping relationship.

[0237] For the description of the first mapping relationship, please refer to the description of the first possible implementation above, which will not be repeated here.

[0238] When N=1, the above-mentioned UDM determines N business requirements based on the perception area #1 and the first mapping relationship, including: the UDM determines P (P is a positive integer) business requirements based on the perception area #1 indicated by the business requirement request and the first mapping relationship; further, when P>1, the method 600 may also include: the UDM determines N business requirements from the P business requirements based on the time information of the business requirement request.

[0239] Optionally, the UDM determines N service requirements from the P service requirements according to time information of the service requirement requests, including: the UDM determines N service requirements from the P service requirements according to the correspondence between the P service requirements and the P time periods and the time information of the service requirement requests.

[0240] When N=1, the UDM determines N service requirements based on the sensing area #1 and the first mapping relationship, including: the UDM determines the N service requirements based on the sensing area #1 indicated by the service requirement request, time information of the service requirement request, the number of terminals included in the sensing area #1, and the fourth mapping relationship. The fourth mapping relationship includes the first mapping relationship.

[0241] Exemplarily, the number of terminals contained in the perception area #1 can be obtained by the UDM from the AMF or obtained locally.

[0242] When N>1, the above-mentioned UDM determines N business requirements based on the perception area #1 and the first mapping relationship, which may include: the UDM determines P (P is a positive integer) business requirements based on the perception area #1 indicated by the business requirement request and the first mapping relationship; further, when P>1, the method 600 may also include: the UDM determines N business requirements from the P business requirements based on the time information of the business requirement request.

[0243] Optionally, the UDM determines N business requirements from the P business requirements based on the time information of the business requirement request, including: the UDM determines N business requirements from the P business requirements based on the second mapping relationship (or the third mapping relationship) and the time information of the business requirement request.

[0244] The time information of the service requirement request may be the time when the UDM receives the service requirement request, or the time information of the above-mentioned perception request.

[0245] Optionally, when N>1, method 600 further includes: the UDM sending a correspondence between the N service requirements and the N intervals of the number of terminals to the SF. In response, the SF receives the correspondence from the UDM and obtains a target service requirement from the N service requirements based on the correspondence between the N service requirements and the N intervals of the number of terminals and the number of terminals in sensing area #1.

[0246] Similar to the first possible implementation, the service requirement request carries service type #1. Before the UDM determines N service requirements based on the perception area #1 indicated in the service requirement request and the first mapping relationship, the method 600 further includes: the UDM determines at least one perception area based on the service type #1; and determines the perception area #1 from the at least one perception area.

[0247] Exemplarily, the UDM determines at least one perception area according to service type #1, including: the UDM determines at least one perception area according to service type #1 and the fifth mapping relationship; and determines perception area #1 from the at least one perception area.

[0248] A third possible implementation: the sensing request received by the SF carries N service requirements, and the SF determines the target service requirement from the N service requirements.

[0249] Optionally, the above-mentioned perception authorization request indicates perception area #1; the method 600 further includes: the UDM determines N service requirements based on the perception area #1 from the NEF; the UDM sends the N service requirements to the NEF; the NEF receives the N service requirements and executes S601.

[0250] Exemplarily, the UDM determines N service requirements according to the sensing area #1 from the NEF, including: the UDM determines the N service requirements according to the sensing area #1 from the NEF and the first mapping relationship.

[0251] Regarding the description of the UDM determining N service requirements based on the perceived area #1 and the first mapping relationship, please refer to the relevant description in the second possible implementation, which will not be repeated here.

[0252] Optionally, when N>1, the method 600 further includes: when authorization is determined, the UDM sends a correspondence between the N service requirements and the N intervals of the number of terminals to the NEF.

[0253] It is understood that when the NEF receives the correspondence between N service requirements and N intervals of the number of terminals from the UDM, the NEF may also carry the correspondence between the N service requirements and N intervals of the number of terminals in the sent perception request #1. In this case, the SF may obtain the target service requirement from the N service requirements based on the correspondence between the N service requirements and N intervals of the number of terminals received and the number of terminals included in the perception area #1.

[0254] The number of terminals in perception area #1 can be obtained from the AMF. The number of terminals in perception area #1 can also be sent by the UDM to the SF via the NEF. For example, if the UDM determines that the perception request is authorized, the UDM obtains the number of terminals in perception area #1 and sends it to the NEF. The NEF includes the number of terminals in perception area #1 in the perception request and sends it to the SF.

[0255] Similar to the first possible implementation, the perception authorization request also carries service type #1. Before the UDM determines N service requirements based on the perception area #1 from the NEF and the first mapping relationship, the method 600 also includes: the UDM determines at least one perception area based on the service type #1; and determines the perception area #1 from the at least one perception area.

[0256] Exemplarily, the UDM determines at least one perception area according to the service type #1, including: the UDM determines at least one perception area according to the service type #1 and the fifth mapping relationship.

[0257] It should be noted that the process of the UDM determining the N service requirements based on the sensing area #1 from the NEF and the first mapping relationship can be performed when the UDM determines to authorize the sensing request. In this case, the N service requirements sent by the UDM to the NEF can be included in the authorization message.

[0258] With respect to the first to third possible implementations described above, when N=1, the N service requirements are the target service requirements.

[0259] Optionally, before SF obtains the target business requirement from the N business requirements based on the correspondence between the N business requirements and the N intervals of the number of terminals, and the number of terminals included in the perception area, the method 600 also includes: SF sends an acquisition request to AMF, where the acquisition request is used to request the number of terminals included in the perception area; AMF receives the acquisition request and sends an acquisition reply to SF, where the acquisition reply indicates the number of terminals included in the perception area; SF receives the acquisition reply and determines the number of terminals included in the perception area based on the acquisition reply.

[0260] Exemplarily, the acquisition reply includes the number of terminals, or the acquisition reply includes a terminal list. It should be understood that when the acquisition reply includes a terminal list, the SF can count the number of terminals based on the terminal list.

[0261] It can be understood that the above AMF is determined by SF based on perception area #1.

[0262] Optionally, before S602 , the method 600 further includes: the SF determining whether to allow or not to allow sensing area # 1 .

[0263] It should be noted that, when the SF determines that the perception area #1 is allowed to be perceived, the SF may continue to execute S602.

[0264] Example 1: When at least one of the following conditions is met, the SF determines that perception of perception area #1 is allowed; or, when all of the following conditions are not met, the SF determines that perception of perception area #1 is allowed: perception area #1 belongs to a predefined area range, service type #1 belongs to a predefined service type allowed to be triggered, the perception accuracy corresponding to service requirement #1 belongs to a predefined perception accuracy range, the time of the perception request belongs to a predefined time interval, or the AF identified by the AF identifier belongs to a predefined AF allowed to be triggered.

[0265] It can be understood that at least one condition may be a local policy configured by the operator on the SF.

[0266] It is understood that the indication of the sensing area #1, service type #1, service requirement #1, and the identifier of the AF may be carried in the sensing request #1 and sent to the SF. The sensing accuracy corresponding to the service requirement #1 may fall within a predefined sensing accuracy range. For example, any one or more parameters included in the KPI determined according to the service requirement #1 may fall within any one or more predefined sensing accuracy ranges.

[0267] For example, when the sensing request #1 carries these four parameters, when the SF determines that sensing area #1 is allowed to be sensed, if there is a parameter that satisfies the corresponding conditions, the SF can determine that sensing of the sensing area is allowed. It should be noted that this application does not focus on whether other parameters other than the parameters that meet the above conditions meet the above conditions.

[0268] The predefined area range is described by the area information used by the operator. For example, the predefined area range may refer to an area where an important person or a motorcade passes through.

[0269] The predefined service type allowed to be triggered may be described by a service ID. For example, the predefined service type allowed to be triggered may be sensing the time when a user in a residential area goes out or comes home.

[0270] The above-defined perception accuracy range may be divided by an accuracy value. For example, if the accuracy is greater than 1, perception of perception area #1 is allowed, and if the accuracy is less than or equal to 1, perception of perception area #1 is not allowed.

[0271] The predefined time intervals mentioned above can be, for example, peak traffic hours. It is important to note that if the detection is for peak-hour detection on a highway, the time dimension can be triggered alone, that is, as long as the time information of the sensing request falls within the predefined time interval, it will be triggered. If the detection is for peak-hour detection at a traffic intersection, other conditions may also be required to trigger it.

[0272] The predefined AFs that are allowed to be triggered may be, for example, AF 1 and AF 2, and the predefined AFs that are not allowed to be triggered may be, for example, a public safety AF or an authority / regulatory agency AF.

[0273] Optionally, before S602, the method 600 also includes: when at least one of the following conditions is met, SF obtains the target service requirements: perception area #1 belongs to a predefined area range, service type #1 belongs to a predefined service type that is allowed to be triggered, the perception accuracy corresponding to service requirement #1 belongs to a predefined perception accuracy range, the time of the perception request belongs to a predefined time interval, or the application function network element identified by the application function network element identifier belongs to a predefined application function network element that is allowed to be triggered.

[0274] For the description of at least one of the above conditions, please refer to the relevant description above and will not be repeated here.

[0275] Optionally, the business requirements carried in the perception request #1 are perceived. After S602, that is, after the SF obtains the target business requirements, the method 600 further includes: the SF sends a business requirement confirmation request to the AF, and the business requirement confirmation request is used to request the adoption of the target business requirements, which are different from the business requirement #1; the AF sends a business requirement confirmation reply to the SF, and the business requirement confirmation reply indicates whether to agree or disagree to adopt the target business requirements.

[0276] The SF may carry the target service requirement in the service requirement confirmation request, which is used to instruct the AF to use a service requirement different from service requirement #1 to perform the perception process, and to request the AF to confirm whether the target service requirement can be used to perform the perception.

[0277] Exemplarily, when the business requirement confirmation reply indicates agreement to adopt the target business requirement, the SF initiates a perception process based on the target business requirement; or, when the business requirement confirmation reply indicates disagreement to adopt the target business requirement, the SF determines that it disagrees to perform perception.

[0278] Optionally, if it is determined that the SF does not agree to perform the perception, the SF sends a rejection message to the AF, where the rejection message is used to reject the perception request #1.

[0279] Optionally, when it is determined that perception is agreed and the target business requirement is a KPI for perception, SF can initiate the perception process based on the target business requirement; or, when it is determined that perception is agreed and the target business requirement is not a KPI for perception, SF can determine the KPI for perception based on the target business requirement and initiate the perception process based on the KPI.

[0280] Among them, the target business requirements can be KPIs, or include KPIs, or can also include information used to determine KPIs, such as identifiers or parameters corresponding to KPIs, and so on. KPIs are used to describe the accuracy with which perception data needs to be acquired. Exemplarily, KPIs may include one or more of the following indicators: confidence interval, perception positioning accuracy (including vertical and horizontal), perception speed accuracy (including vertical and horizontal), perception resolution (including area and speed), maximum perception service delay or refresh rate. These indicators are only an example of KPIs, and this application does not limit the specific indicators included in KPIs.

[0281] If the target service requirement is a KPI or includes a KPI, the SF may directly obtain the KPI for perceiving the terminal based on the target service requirement, and then initiate a process of perceiving the terminal.

[0282] If the target service requirement includes information for determining a KPI, the SF may convert the target service requirement into a KPI. In other words, one possible implementation method for the SF to determine the KPI perceived by the terminal based on the target service requirement is to determine the target service requirement as the KPI perceived by the terminal. Another possible implementation method is to convert the target service requirement into a KPI perceived by the terminal.

[0283] In one possible implementation, the target service requirement may include an identifier corresponding to a KPI. Based on the identifier in the target service requirement, the Service Provider (SF) may convert the target service requirement into a KPI perceived by the terminal. In another possible implementation, the SF may pre-store a correspondence between at least one identifier and at least one KPI, where each KPI may include one or more indicators. Based on the identifier included in the target service requirement, the SF may search for the KPI corresponding to the identifier from the pre-stored correspondence.

[0284] In another possible implementation, the target service requirement may also include parameters corresponding to KPIs. The SF may convert the target service requirement into a KPI perceived by the terminal based on the parameters in the target service requirement. In one possible implementation, the SF pre-stores a correspondence between at least one set of parameters and at least one KPI. Each set of parameters may include one or more parameters, and each KPI may include one or more indicators. Based on the set of parameters included in the target service requirement, the SF may search for the KPI corresponding to the set of parameters from the pre-stored correspondence.

[0285] This conversion can be based on a predefined mapping between business requirements and KPIs. For example, if the target business requirement is a specific identifier, the SF has a predefined KPI corresponding to that identifier. Alternatively, the parameters in the perception requirement can be translated into KPI parameters. For example, if the parameters in the perception requirement correspond to the parameters in the KPI, the SF will determine the parameters in the perception requirement as the corresponding KPI parameters. The perception requirement can also be equivalent to the KPI, meaning that no translation by the SF is required.

[0286] It can be understood that SF can use any of the six perception modes shown in Table 1 above to initiate the perception process.

[0287] Exemplarily, the SF initiates a perception process, including: the SF selects a perception mode, selects a specific perception node (transmitter and receiver), and instructs the perception node to send and receive perception signals using the perception KPI determined by the target business requirements, and obtains perception data to determine the perception results.

[0288] Optionally, before the SF sends the service requirement confirmation request to the AF, the method 600 further includes: the SF determining whether the target service requirement is the same as service requirement #1.

[0289] Exemplarily, when the target service requirement is different from service requirement #1, the SF sends a service requirement confirmation request to the AF; or, when the target service requirement is the same as service requirement #1, the SF initiates a perception process based on the target service requirement.

[0290] It is understood that the target business requirement being different from business requirement #1 means that the level of the target business requirement is different from the level of business requirement #1. For example, the level of the target business requirement is lower than the level of business requirement #1; or in another example, the level of the target business requirement is higher than the level of business requirement #1.

[0291] In Example 1, the target service requirement is lower than the level of service requirement #1. In this case, the service requirement confirmation request can be understood as a request to the AF to confirm whether the execution-aware service requirement can be downgraded. This service requirement confirmation request can also be called a downgrade confirmation request. Specifically, before the SF sends the service requirement confirmation request to the AF, method 600 also includes: the SF determining whether the target service requirement is downgraded compared to service requirement #1.

[0292] The fact that the target business requirement is downgraded compared to business requirement #1 means that the level of the target business requirement is lower than the level of business requirement #1.

[0293] For example, if the target business requirement obtained by SF is the minimum business requirement and business requirement #1 is the medium business requirement, then it can be considered that the target business requirement is downgraded compared to business requirement #1.

[0294] It should be noted that the level of a business requirement can be determined based on the values ​​of the various indicators in the KPIs it determines. The following examples illustrate several cases where the target business requirement's level is lower than that of business requirement #1. For example, the target business requirement's corresponding indicator has a perceived location accuracy of 1 meter, while business requirement #1's corresponding indicator has a perceived location accuracy of 1 mm. Since 1 mm accuracy is higher than 1 meter accuracy, the target business requirement's level can be considered lower than that of business requirement #1. Another example is the target business requirement's corresponding indicator has a perceived resolution of 5 meters, while business requirement #1's corresponding indicator has a perceived resolution of 1 meter. Since 1 meter resolution is higher than 5 meter resolution, the target business requirement's level can be considered lower than that of business requirement #1. Another example is the target business requirement's corresponding indicator has a maximum perceived service latency of 0.5 ms, while business requirement #1's corresponding indicator has a maximum perceived service latency of 0.2 ms. Since 0.2 ms latency is shorter than 0.5 ms latency, the target business requirement's level can be considered lower than that of business requirement #1.

[0295] In Example 2, the target service requirement is at a higher level than service requirement #1. In this case, the service requirement confirmation request can be understood as a request to the AF to confirm whether or not the execution-aware service requirement can be upgraded. This service requirement confirmation request can also be referred to as an upgrade confirmation request. Specifically, before the SF sends the service requirement confirmation request to the AF, method 600 further includes: the SF determining whether the target service requirement is upgraded compared to service requirement #1.

[0296] The target business requirement being upgraded compared to business requirement #1 means that the level of the target business requirement is higher than the level of business requirement #1.

[0297] For example, if the target business requirement obtained by SF is a medium business requirement and business requirement #1 is a minimum business requirement, then it can be considered that the target business requirement is upgraded compared to business requirement #1.

[0298] The following examples illustrate several scenarios where the target service requirement's level is higher than service requirement #1. For example, the target service requirement's perceived location accuracy is 1mm, while service requirement #1's perceived location accuracy is 1m. Since 1mm accuracy is higher than 1m accuracy, this target service requirement's level is considered higher than service requirement #1. Another example is the target service requirement's perceived resolution is 1m, while service requirement #1's perceived resolution is 5m. Since 1m resolution is higher than 5m resolution, this target service requirement's level is considered higher than service requirement #1. Another example is the target service requirement's maximum perceived service latency is 0.2ms, while service requirement #1's maximum perceived service latency is 0.5ms. Since 0.2ms latency is shorter than 0.5ms latency, this target service requirement's level is considered higher than service requirement #1.

[0299] Exemplarily, when the SF determines that there is a downgrade or upgrade, the SF sends a service requirement confirmation request to the AF; or, when the SF determines that there is no downgrade, the SF initiates a perception process based on the target service requirement.

[0300] Of course, if the target service requirement differs from Service Requirement #1, the SF can also initiate the terminal perception process based on the target service requirement, without confirming with the AF whether the target service requirement is adopted. For example, if the target service requirement is higher than Service Requirement #1, the terminal perception process can be initiated based on the target service requirement, without confirming with the AF whether the target service requirement is adopted. In this case, the SF does not need to determine whether the target service requirement is the same as Service Requirement #1. In other words, the SF sending a service requirement confirmation request to the AF is an optional step and is not required.

[0301] Optionally, before S601, the method 600 also includes: the AF sends a parameter configuration request to the NEF, wherein the parameter configuration request includes a correspondence between at least one perception area and at least one service requirement; the NEF performs an authorization check on the AF and sends a parameter configuration request to the SF or UDM, wherein the parameter configuration request includes a correspondence between at least one perception area and at least one service requirement; the SF or UDM determines a first mapping relationship based on the parameter configuration request.

[0302] Optionally, the parameter configuration request may further include a correspondence between at least one service requirement and at least one time period.

[0303] Optionally, the parameter configuration request may further include a correspondence between at least one service requirement and at least one interval of the number of terminals.

[0304] It can be understood that, for the first possible implementation, the NEF may send a parameter configuration request to the SF; and for the second and third possible implementations, the NEF may send a parameter configuration request to the UDM.

[0305] The following will be based on the embodiment shown in Figure 6 and will be combined with Figures 7 to 9 to provide a more detailed introduction to the communication method provided in the embodiments of the present application. It should be noted that in the embodiments shown in Figures 7 to 9, the same or similar steps as those in the embodiment shown in Figure 6 can be found in the relevant description of method 600 above and will not be repeated here.

[0306] The following takes the first mapping relationship pre-stored in the UDM as an example and describes in detail the method provided in the embodiment of the present application in combination with FIG. 7 and FIG. 8 .

[0307] FIG7 is another schematic flow chart of a communication method provided in an embodiment of the present application. As shown in FIG7 , the method 700 may include steps S701 to S716. The steps in the method 700 are described below.

[0308] S701: The AF sends a first perception request to the NEF, where the first perception request includes the AF identifier, service type #1, service requirement #1, and external perception area information. Correspondingly, the NEF receives the first perception request from the AF.

[0309] Among them, the external area information can be understood as the above-mentioned perception area #2, and the first perception request can be understood as the previous perception request #2.

[0310] S702 , NEF converts the external perception area information into internal perception area information.

[0311] The internal perception area information refers to the area information used by the operator network, which can be understood as the perception area #1 mentioned above.

[0312] S703: The NEF sends a perception authorization request to the UDM. Correspondingly, the UDM receives the perception authorization request from the NEF.

[0313] For the description of the perception authorization request, please refer to the relevant description of the perception authorization request in the previous article, which will not be repeated here.

[0314] S704: UDM determines whether to authorize or not the perception request.

[0315] Exemplarily, the UDM can determine whether to authorize the perception request from the AF based on the AF's identifier; in another possible case, the UDM can further determine whether the business requirements carried in the perception request from the AF meet the business requirements included in the corresponding relationship pre-stored in the UDM; if so, determine to authorize; or, if not, determine not to authorize.

[0316] In the case of determining that the authorization is not granted, a rejection authorization message is sent to the NEF, where the rejection authorization message is used to reject the authorization of the perception request.

[0317] If the authorization is passed, some steps from S705 to S716 are continued to be executed.

[0318] S705: The UDM sends an authorization message to the NEF. Correspondingly, the NEF receives the authorization message from the UDM.

[0319] S706: The NEF sends a second sensing request to the SF, where the second sensing request includes the AF identifier, service type #1, service requirement #1, and internal sensing area information. Correspondingly, the SF receives the second sensing request from the NEF.

[0320] The second perception request can be understood as the perception request #1 mentioned above.

[0321] S707: SF determines whether to allow perception of the perception area based on the second perception request.

[0322] If it is determined that sensing area #1 is allowed, some steps from S708 to S716 are continued; otherwise, the second sensing request is rejected. For the description of determining whether sensing area #1 is allowed, reference can be made to the relevant description above.

[0323] S708: SF sends a service request to UDM. Correspondingly, UDM receives the service request from SF.

[0324] The acquisition request includes internal area information.

[0325] S709 , the UDM determines N service requirements according to the first mapping relationship and the internal area information.

[0326] This process can refer to the above process of the UDM determining N service requirements according to the first mapping relationship and the perception area #1, which will not be repeated here.

[0327] S710: The UDM sends N service requests to the SF. Correspondingly, the SF receives the N service requests from the UDM.

[0328] Optionally, when N is greater than 1, the method 700 further includes: the UDM sends a correspondence between N service requirements and N intervals of the number of terminals to the SF.

[0329] S711, SF obtains the target business requirement from N business requirements.

[0330] This process may refer to the process of obtaining the target business requirements in the second possible implementation of method 600 above, and will not be described in detail here.

[0331] S712, SF determines whether the target business requirement is the same as or different from business requirement #1.

[0332] If they are the same, directly execute S715.

[0333] If they are not the same, continue to execute some steps from S713 to S716.

[0334] S713: The SF sends a service requirement confirmation request to the AF. Correspondingly, the AF receives the service requirement confirmation request from the SF.

[0335] S714: The AF sends a service request confirmation reply to the SF. Correspondingly, the SF receives the service request confirmation reply from the AF.

[0336] If the confirmation reply indicates that the target business requirement is agreed to be adopted, the process continues with S715 , where the SF initiates a perception process based on the target business requirement.

[0337] If the confirmation reply indicates that the target service requirement is not adopted, the process proceeds to S716 , where the SF sends a rejection message to the AF, where the rejection message is used to reject the perception request # 2 . Correspondingly, the AF receives the rejection message from the SF.

[0338] For descriptions of business requirement confirmation requests and business requirement confirmation replies, please refer to the relevant descriptions above.

[0339] In an embodiment of the present application, after receiving a business requirement from SF for requesting to obtain the target business requirement, UDM can determine the business requirement corresponding to the perception area based on the perception area and the first mapping relationship, and send the obtained business requirement to SF, so that SF obtains the target business requirement corresponding to the perception area from the received business requirement. Therefore, the method provided in the embodiment of the present application can flexibly respond to the perception request according to the perception area to meet the restrictions on business requirements of different perception areas, and solves the problem that all business requirements are the same when perceiving the same business requirement in different perception areas.

[0340] FIG8 is another schematic flow chart of a communication method provided in an embodiment of the present application. As shown in FIG8 , the method 800 may include steps S801 to S814. The steps in the method 800 are described below.

[0341] S801: The AF sends a first sensing request to the NEF. Correspondingly, the NEF receives the first sensing request from the AF.

[0342] Among them, the first perception request can be understood as the perception request #2 mentioned above.

[0343] S802, NEF converts the external perception area information into internal perception area information.

[0344] The internal perception area information refers to area information used by the operator's network.

[0345] The internal perception area information may be understood as the perception area #1, and the external area information may be understood as the perception area #2.

[0346] S803: The NEF sends a perception authorization request to the UDM. Correspondingly, the UDM receives the perception authorization request from the NEF.

[0347] S804: UDM determines whether to authorize or not the perception request.

[0348] The description of S801 to S804 can refer to the description of S701 to S704 above, and will not be repeated here.

[0349] In the case of determining that the authorization is not granted, a rejection authorization message is sent to the NEF, where the rejection authorization message is used to reject the authorization of the perception request.

[0350] If the authorization is passed, some steps from S805 to S815 are continued to be executed.

[0351] S805: The UDM determines at least one new service requirement corresponding to the internal area information according to the first mapping relationship and the internal area information.

[0352] This process may refer to S709 in method 700 and will not be described again here.

[0353] S806: The UDM sends an authorization message to the NEF, where the authorization message carries N service requirements. Correspondingly, the NEF receives the authorization message from the UDM.

[0354] Optionally, when N is greater than 1, the authorization message further carries a correspondence between N service requirements and N intervals of the number of terminals.

[0355] S807: The NEF sends a second awareness request to the SF, where the second awareness request carries N service requirements. Correspondingly, the SF receives the second awareness request from the NEF.

[0356] Optionally, when the authorization message also carries the correspondence between N service requirements and N intervals of the number of terminals, the second perception request also carries the correspondence between N service requirements and N intervals of the number of terminals.

[0357] S808. SF determines whether to allow perception of the perception area based on the second perception request.

[0358] If it is determined that sensing area #1 is allowed, some steps from S809 to S815 are continued; otherwise, the second sensing request is rejected. The description of determining whether sensing area #1 is allowed can refer to the relevant description above.

[0359] S809, SF obtains the target business requirement from the N business requirements.

[0360] This process may refer to the process of obtaining the target business requirements in the third possible implementation of method 600 above, and will not be described in detail here.

[0361] S810, SF determines whether the target business requirement is the same as or different from business requirement #1.

[0362] If they are the same, directly execute S813.

[0363] If different, continue to execute some steps from S811 to S814.

[0364] S811, SF sends a service requirement confirmation request to AF. Correspondingly, AF receives the service requirement confirmation request from SF.

[0365] S812: The AF sends a service request confirmation reply to the SF. Correspondingly, the SF receives the service request confirmation reply from the AF.

[0366] If the confirmation reply indicates that the target business requirement is agreed to be adopted, then S813 is executed and the SF initiates a perception process based on the target business requirement.

[0367] If the confirmation reply indicates that the target service requirement is not adopted, the process proceeds to S814, where the SF sends a rejection message to the AF, where the rejection message is used to reject the perception request #2. Correspondingly, the AF receives the rejection message from the SF.

[0368] For descriptions of business requirement confirmation requests and business requirement confirmation replies, please refer to the relevant descriptions above.

[0369] In an embodiment of the present application, the UDM can, when authorizing the perception request from the AF, determine the business requirements corresponding to the perception area based on the perception area carried in the perception authorization request and the first mapping relationship, and send the obtained business requirements to the NEF, and then the NEF sends the obtained business requirements to the SF, so that the SF obtains the target business requirements corresponding to the perception area from the received business requirements. Therefore, the method provided in the embodiment of the present application can flexibly respond to the perception request according to the perception area to meet the restrictions on business requirements of different perception areas, and solves the problem that all business requirements are the same when perceiving the same business requirements of different perception areas.

[0370] The following takes the first mapping relationship pre-stored in SF as an example and describes in detail the method provided in the embodiment of the present application in combination with FIG9 .

[0371] FIG9 is another schematic flow chart of a communication method provided in an embodiment of the present application. As shown in FIG9 , the method 900 may include steps S901 to S914. The steps in the method 900 are described below.

[0372] S901: The AF sends a first sensing request to the NEF. Correspondingly, the NEF receives the sensing request from the AF.

[0373] S902, NEF converts the external perception area information into internal perception area information.

[0374] S903: The NEF sends a perception authorization request to the UDM. Correspondingly, the UDM receives the perception authorization request from the NEF.

[0375] S904: UDM determines whether to authorize or not the perception request.

[0376] In the case of determining that the authorization is not granted, a rejection authorization message is sent to the NEF, where the rejection authorization message is used to reject the authorization of the perception request.

[0377] If the authorization is passed, some steps from S905 to S914 are continued to be executed.

[0378] S905: The UDM sends an authorization message to the NEF. Correspondingly, the NEF receives the authorization message from the UDM.

[0379] S906: The NEF sends a second perception request to the SF. Correspondingly, the SF receives the second perception request from the NEF.

[0380] S907: SF determines whether to allow perception of the perception area based on the second perception request.

[0381] The description of S901 to S907 can refer to the relevant description of S701 to S707 above, and will not be repeated here.

[0382] If it is determined that sensing of perception area #1 is permitted, steps S908 through S914 are continued; otherwise, the second sensing request is rejected. For a description of determining whether sensing of perception area #1 is permitted, refer to the previous description. S908: The SF determines N service requirements based on the first mapping relationship and the internal area information.

[0383] This process can refer to the above process of SF determining N service requirements according to the first mapping relationship and perception area #1, which will not be repeated here.

[0384] S909, SF obtains the target business requirement from the N business requirements.

[0385] This process can refer to the process of obtaining the target business requirements in the first possible implementation of method 600 above, and will not be repeated here.

[0386] S910, SF determines whether the target service requirement is the same as or different from service requirement #1.

[0387] If they are the same, directly execute S913.

[0388] If they are not the same, continue to execute some steps from S911 to S914.

[0389] S911, the SF sends a service requirement confirmation request to the AF. Correspondingly, the AF receives the service requirement confirmation request from the SF.

[0390] S912: The AF sends a service request confirmation reply to the SF. Correspondingly, the SF receives the service request confirmation reply from the AF.

[0391] If the confirmation reply indicates that the target service requirement is agreed to be adopted, the process continues with S913 , where the SF initiates a perception process based on the target service requirement.

[0392] If the confirmation reply indicates that the target service requirement is not adopted, the process proceeds to S914, where the SF sends a rejection message to the AF, where the rejection message is used to reject the perception request #2. Correspondingly, the AF receives the rejection message from the SF.

[0393] For descriptions of business requirement confirmation requests and business requirement confirmation replies, please refer to the relevant descriptions above.

[0394] In an embodiment of the present application, after receiving a perception request for requesting perception of a perception area, SF can obtain the target business requirements corresponding to the perception area based on the perception area as a first mapping relationship. Therefore, the method provided in an embodiment of the present application can flexibly respond to the perception request according to the perception area to meet the restrictions on business requirements of different perception areas, and solve the problem that all business requirements are the same when perceiving the same business requirements of different perception areas.

[0395] The method provided by the embodiment of the present application is described in detail above in conjunction with Figures 6 to 9 , and the device provided by the embodiment of the present application is described in detail below in conjunction with Figures 10 and 11 .

[0396] Figures 10 and 11 are schematic diagrams of possible devices provided by embodiments of the present application. These devices can be used to implement the functions of SF or UDM in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0397] FIG10 is a schematic block diagram of a communication device according to an embodiment of the present application. As shown in FIG10 , the device 1000 includes a transceiver module 1010 and a processing module 1020 .

[0398] One possible design is that the apparatus 1000 is used to implement the function of SF in the method embodiments shown in FIG. 6 to FIG. 9 .

[0399] Exemplarily, the transceiver module 1010 is used to receive a perception request; and the processing module 1020 is used to obtain target service requirements.

[0400] Optionally, the transceiver module 1010 is also used to: send a service requirement request to the data management function network element; and receive N service requirements from the data management function network element, where N is a positive integer; the processing module 1020 is also used to: obtain the target service requirement from the N service requirements.

[0401] Optionally, the processing module 1020 is further configured to: determine the N service requirements according to the perception area and the mapping relationship; and obtain the target service requirement from the N service requirements.

[0402] Optionally, the perception request carries N business requirements, and the processing module 1020 is further used to: obtain the target business requirement from the N business requirements.

[0403] Optionally, the processing module 1020 is further configured to: when N>1, obtain the target service requirement from the N service requirements according to the correspondence between the N service requirements and the N intervals of the number of terminals, and the number of terminals included in the sensing area.

[0404] Optionally, the transceiver module 1010 is further configured to: obtain the number of terminals included in the sensing area from an access and mobility management function network element.

[0405] Optionally, the processing module 1020 is further used to: when N>1, obtain the target business requirement from the N business requirements based on the correspondence between the N business requirements and the N time periods, and the time information of the perception request.

[0406] Optionally, the processing module 1020 is further configured to: determine whether perception of the perception area is allowed.

[0407] Optionally, the processing module 1020 is also used to determine whether perception of the perception area is allowed when at least one of the following conditions is met: the perception area belongs to a predefined area range, the service type belongs to a predefined service type that is allowed to be triggered, the perception KPI corresponding to the requested service requirement belongs to a predefined perception KPI interval, the time information of the perception request belongs to a predefined time interval, or the application function network element identified by the identifier of the application function network element belongs to a predefined application function network element that is allowed to be triggered.

[0408] Optionally, the processing module 1020 is also used to obtain the target service requirements when it is determined that at least one of the following conditions is met: the perception area belongs to a predefined area range, the service type belongs to a predefined service type that is allowed to be triggered, the perception KPI corresponding to the requested service requirement belongs to a predefined perception KPI interval, the time information of the perception request belongs to a predefined time interval, or the application function network element identified by the identifier of the application function network element belongs to a predefined application function network element that is allowed to be triggered.

[0409] Optionally, the transceiver module 1010 is also used to: send a service requirement confirmation request to the application function network element; and receive a service requirement confirmation reply from the application function network element; the processing module 1020 is also used to: when the service requirement confirmation reply indicates agreement to adopt the target service requirement, initiate a perception process based on the target service requirement; or, when the service requirement confirmation reply indicates disagreement to adopt the target service requirement, determine disagreement to perform perception.

[0410] Optionally, the transceiver module 1010 is further used to: when it is determined that the perception is not agreed, send a rejection message to the application function network element, where the rejection message is used to reject the perception request.

[0411] A more detailed description of the transceiver module 1010 and the processing module 1020 can be directly obtained by referring to the relevant descriptions in the embodiments shown in Figures 6 to 9, and will not be repeated here.

[0412] Another possible design is that the apparatus 1000 is used to implement the UDM functions in the above method 600 and the method embodiments shown in FIG. 7 to FIG. 9 .

[0413] Exemplarily, the transceiver module 1010 is used to: receive a service requirement request from a perception function network element; the processing module 1020 is used to: determine N service requirements based on the perception area and mapping relationship; the transceiver module 1010 is also used to: send the N service requirements to the perception function network element.

[0414] Optionally, the processing module 1020 is also used to: determine at least one business requirement based on the perception area and the mapping relationship; and determine the N business requirements from the at least one business requirement based on the correspondence between the at least one business requirement and at least one time period, and the time information of the business requirement request.

[0415] Optionally, when N>1, the transceiver module 1010 is further used to: send the corresponding relationship between the N service requirements and the N intervals of the number of terminals to the perception function network element.

[0416] Optionally, the transceiver module 1010 is further configured to: receive a parameter configuration request; and the transceiver module 1010 is further configured to: determine the mapping relationship according to the parameter configuration request.

[0417] Exemplarily, the transceiver module 1010 is used to: receive a perception authorization request from a network capability exposure function network element; the processing module 1020 is used to: when determining to authorize the perception request, determine N service requirements based on the perception area and the mapping relationship, and the mapping relationship indicates the correspondence between at least one perception area and at least one service requirement; the transceiver module 1010 is also used to: send the N service requirements to the network capability exposure function network element.

[0418] Optionally, when N>1, the transceiver module 1010 is further configured to: send the correspondence between the N service requirements and the N intervals of the number of terminals to the network capability exposure function network element.

[0419] Optionally, the processing module 1020 is further used to determine whether to authorize or not to authorize the perception request based on the identifier of the application function network element.

[0420] Optionally, the processing module 1020 is also used to: when determining to authorize the perception request based on the identifier of the application function network element, determine that the service requirements of the request do not meet the service requirements corresponding to the perception area included in the mapping relationship; and determine not to authorize the perception request.

[0421] A more detailed description of the transceiver module 1010 and the processing module 1020 can be directly obtained by referring to the method 600 and the relevant descriptions in the embodiments shown in Figures 7 to 9, and will not be repeated here.

[0422] It should be noted that device 1000 may include a sending module but not a receiving module. Alternatively, device 1000 may include a receiving module but not a sending module. This may depend on whether the above-mentioned solution executed by device 1000 includes both sending and receiving actions. It is understood that since device 1000 has communication functionality, it can also be referred to as a communication device.

[0423] Figure 11 is another schematic block diagram of a communication device provided in an embodiment of the present application. As shown in Figure 11, communication device 1100 includes at least one processor 1110. The at least one processor 1110 can be configured to execute computer programs or instructions stored in memory to implement the steps performed by the SF, the UDM, or the AF in any of the method embodiments of method 600 and Figures 7 through 9.

[0424] Optionally, the communication device 1100 may further include at least one memory 1120 for storing instructions executed by the processor 1110 or storing input data required by the processor 1110 to execute instructions or storing data generated after the processor 1110 executes instructions. The at least one processor 1110 and the at least one memory 1120 may be provided separately. For example, each memory may be connected to one or more processors so that the connected processors can read information from the memory and store and / or write information in the memory. Alternatively, the at least one processor 1110 and the at least one memory 1120 may be integrated together, for example, one or more memories may be integrated into a processor.

[0425] Optionally, the communication device 1100 further includes an interface circuit 1130, which can be used to transmit data and / or signaling. The at least one processor 1110 and the interface circuit 1130 are coupled to each other. It is understood that the interface circuit 1130 can be a transceiver, an input / output circuit, a bus, a module, a pin, or other type of interface circuit, wherein the input circuit of the input / output circuit can be used for receiving, and the output interface can be used for sending.

[0426] Optionally, the communication device 1100 further includes a power supply circuit 1140 , which can be used to supply power to the communication device 1100 .

[0427] When the communication device 1100 is used in the method described in the above embodiment, at least one processor 1110 is used to perform the functions of the above processing unit, and the interface circuit 1130 is used to perform the functions of the above receiving unit and / or sending unit. Whether the interface circuit 1130 is used for sending or receiving can be determined by whether the communication device 1100 is used to perform a sending action or a receiving action in the solution implemented.

[0428] It is understood that when the communication device 1100 is a communication device (e.g., SF, UDM, or AF), the interface circuit 1130 may be a transceiver, specifically including a transmitter and a receiver, where the transmitter is used to transmit signals and the receiver is used to receive signals. When the communication device 1100 is a chip used in a communication device, the interface circuit 1130 may be an input / output circuit, a bus, a module, a pin, or other type of interface circuit, wherein the input circuit of the input / output circuit can be used for receiving, and the output interface can be used for transmitting.

[0429] It should be understood that in the communication device 1100 shown in FIG. 11 , the processor 1110 may correspond to the processing module 1020 in the above communication device 1000 , and the interface circuit 1130 may correspond to the transceiver module 1010 in the above communication device 1000 .

[0430] It should also be understood that the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. In the embodiments of the present application, the specific connection medium between the at least one processor 1110, the at least one memory 1120, the interface circuit 1130 and the power supply circuit 1140 is not limited. In Figure 11, the embodiment of the present application shows that the processor 1110, the memory 1120, the interface circuit 1130 and the power supply circuit 1140 are connected via a bus 1150. The bus 1150 is represented by a bold line in Figure 11, and the connection method between other components is only for schematic illustration and is not limited. The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 11, but it does not mean that there is only one bus or one type of bus.

[0431] It should be noted that the above method embodiments can be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by hardware integrated logic circuits in the processor or by software instructions.

[0432] The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0433] The steps of the method disclosed in the embodiments of this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0434] The memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0435] The methods provided in the above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product may include one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic disk), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0436] An embodiment of the present application further provides a communication system, which includes the aforementioned SF and UDM.

[0437] An embodiment of the present application also provides a computer program product, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables the computer to execute the method executed by the SF network element in any of the embodiments shown in Figures 6 to 9, or enables the computer to execute the method executed by the UDM network element in any of the embodiments shown in Figures 7 to 9.

[0438] The present application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is executed, the computer executes the method performed by the SF network element in any of the embodiments shown in Figures 6 to 9 , or the method performed by the UDM network element in any of the embodiments shown in Figures 7 to 9 .

[0439] An embodiment of the present application also provides a chip system, which includes at least one processor, used to implement the method executed by the SF network element in any of the embodiments shown in Figures 6 to 9, or used to implement the method executed by the UDM network element in any of the embodiments shown in Figures 7 to 9.

[0440] Optionally, the chip system also includes a memory for storing program instructions and data, and the memory is located inside or outside the processor.

[0441] Optionally, the chip system further includes an interface circuit and / or a power supply circuit, wherein the interface circuit is used to transmit data, and the power supply circuit is used to power the chip system. Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software 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 be beyond the scope of this application.

[0442] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0443] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0444] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0445] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0446] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

[0447] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that, Including: Receiving a sensing request for requesting to sense a sensing area; Obtaining a target service requirement, where the target service requirement is determined according to the sensing area and is used to determine a key performance indicator (KPI) for sensing.

2. The method according to claim 1, wherein The obtaining of the target service requirement includes: Sending a service requirement request to a data management function network element, where the service requirement request indicates the sensing area; Receiving N service requirements from the data management function network element, where the N service requirements are determined according to the sensing area and N is a positive integer; Obtaining the target service requirement from the N service requirements.

3. The method according to claim 1, wherein The obtaining of the target service requirement includes: Determining N service requirements according to the sensing area and a mapping relationship, where the mapping relationship indicates a correspondence between at least one sensing area and at least one service requirement, and N is a positive integer; Obtaining the target service requirement from the N service requirements.

4. The method according to claim 1, wherein The sensing request carries N service requirements, where N is a positive integer; The obtaining of the target service requirement includes: Obtaining the target service requirement from the N service requirements.

5. The method according to claim 3, characterized in that, When N>1, the obtaining of the target service requirement from the N service requirements includes: Obtaining the target service requirement from the N service requirements according to the correspondence between the N service requirements and N time periods and the time information of the sensing request.

6. The method according to any one of claims 2 to 4, characterized in that When N>1, the obtaining of the target service requirement from the N service requirements includes: Obtaining the target service requirement from the N service requirements according to the correspondence between the N service requirements and N intervals of the number of terminals and the number of terminals included in the sensing area.

7. The method according to claim 6, characterized in that, Before obtaining the target service requirement according to the correspondence between the N service requirements and N intervals of the number of terminals and the number of terminals included in the sensing area, the method further includes: Obtaining the number of terminals included in the sensing area from an access and mobility management function network element.

8. The method according to any one of claims 1 to 7, characterized in that, Before obtaining the target service requirement, the method further includes: Determining that sensing of the sensing area is allowed.

9. The method according to claim 8, characterized in that The sensing request carries at least one of the following: an identifier of an application function network element, an indication of the sensing area, a requested service type, or a requested service requirement; The determining that sensing of the sensing area is allowed includes: Determining that sensing of the sensing area is allowed when at least one of the following is satisfied: the sensing area belongs to a predefined area range, the service type belongs to a predefined service type allowed to be triggered, the sensing KPI corresponding to the requested service requirement belongs to a predefined sensing KPI interval, the time information of the sensing request belongs to a predefined time interval, or the application function network element identified by the identifier of the application function network element belongs to a predefined application function network element allowed to be triggered.

10. The method according to any one of claims 1 to 7, characterized in that The sensing request carries at least one of the following: an identifier of an application function network element, an indication of the sensing area, a requested service type, or a requested service requirement; Before obtaining the target service requirement, the method further includes: When it is determined that at least one of the following conditions is met, obtain the target service requirement: the sensing area belongs to a predefined area range, the service type belongs to a predefined service type that allows triggering, the sensing KPI corresponding to the requested service requirement belongs to a predefined sensing KPI range, the time information of the sensing request belongs to a predefined time range, or the application function network element identified by the identifier of the application function network element belongs to a predefined application function network element that allows triggering.

11. The method according to any one of claims 1 to 10, characterized in that, The sensing request comes from an application function network element, and the sensing request carries the requested service requirement. The method further includes: Send a service requirement confirmation request to the application function network element, where the service requirement confirmation request is used to request to adopt the target service requirement, and the target service requirement is different from the requested service requirement; Receive a service requirement confirmation reply from the application function network element, where the service requirement confirmation reply indicates whether to agree or disagree to adopt the target service requirement; and, In the case where the service requirement confirmation reply indicates agreement to adopt the target service requirement, initiate a sensing process based on the target service requirement; or, In the case where the service requirement confirmation reply indicates disagreement to adopt the target service requirement, send a rejection message to the application function network element, where the rejection message is used to reject the sensing request.

12. A communication method, characterized in that, Includes: Receive a service requirement request from a sensing function network element, where the service requirement request indicates a sensing area; Determine N service requirements according to the sensing area and the mapping relationship, where the mapping relationship indicates the corresponding relationship between at least one sensing area and at least one service requirement, and N is a positive integer; Send the N service requirements to the sensing function network element.

13. The method according to claim 12, wherein When N = 1, the N service requirements are the target service requirements.

14. The method according to claim 13, characterized in that The determining N service requirements according to the sensing area and the mapping relationship includes: Determine P service requirements according to the sensing area and the mapping relationship, where P is a positive integer; Determine the N service requirements from the P service requirements according to the corresponding relationship between at least one service requirement and at least one time period, and the time information of the service requirement request.

15. The method according to claim 12, wherein When N > 1, the method further includes: Send the corresponding relationship between the N service requirements and N intervals of the number of terminals to the sensing function network element.

16. The method according to any one of claims 12 to 15, characterized in that, The method further includes: Receive a parameter configuration request, where the parameter configuration request includes the corresponding relationship between at least one sensing area and at least one service requirement; Determine the mapping relationship according to the parameter configuration request.

17. A communication method, characterized in that Includes: Receive a sensing authorization request from a network capability open function network element, where the sensing authorization request is used to request authorization for a sensing request from an application function network element, and the sensing request is used to request to sense a sensing area; In the case of determining to authorize the sensing request, determine N service requirements according to the sensing area and the mapping relationship, where the mapping relationship indicates the corresponding relationship between at least one sensing area and at least one service requirement; Send the N service requirements to the network capability open function network element.

18. The method according to claim 17, wherein When N > 1, the method further includes: Send the correspondence between the N service requirements and the N intervals of the number of terminals to the network capability open function network element.

19. The method according to claim 17 or 18, characterized in that, The identification of the application function network element is carried in the sensing authorization request, and the method further includes: Determine whether to authorize or not authorize the sensing request according to the identification of the application function network element.

20. The method according to claim 19, wherein The service requirements of the request are also carried in the sensing authorization request, and the method further includes: When it is determined to authorize the sensing request according to the identification of the application function network element, determine that the service requirements of the request do not meet the service requirements corresponding to the sensing area included in the mapping relationship; Determine to reject the authorization of the sensing request.

21. A communication device, characterized in that, Comprising one or more functional units for implementing the method according to any one of claims 1 to 11, or for implementing the method according to any one of claims 12 to 16, or for implementing the method according to any one of claims 17 to 20.

22. A communication device, characterized in that, Comprising a processor, the processor is used to execute program code to enable the communication device to implement the method according to any one of claims 1 to 11, or to implement the method according to any one of claims 12 to 16, or to implement the method according to any one of claims 17 to 20.

23. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, the method according to any one of claims 1 to 11 is executed, or the method according to any one of claims 12 to 16 is executed, or the method according to any one of claims 17 to 21 is executed.

24. A computer program product, characterized in that, Comprising a computer program, when the computer program is run, the method according to any one of claims 1 to 11 is executed, or the method according to any one of claims 12 to 16 is executed, or the method according to any one of claims 17 to 20 is executed.

Images