Communication method and related device and system

Abstract

The invention provides a communication method, a related device and a related system, which can flexibly respond to a sensing request according to a sensing area and meet the limitation of different sensing areas on service requirements. The method comprises the following steps: a perception function network element receives a perception request, wherein the perception request is used for requesting to perceive a perception area; the perception function network element obtains a target service requirement, the target service requirement is determined according to the perception area, and the target service requirement is used for determining the perceived KPI.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a communication method, related devices, and systems. Background Art

[0002] In addition to communication capabilities, wireless communication systems also have sensing capabilities. A wireless communication system with sensing capabilities can sense and identify specific areas, objects, or events, and solve sensing requirements in many scenarios. For example, it can sense and predict the presence of people or objects in the environment.

[0003] In the current sensing process, a sensing application can directly send a sensing request carrying a sensing area and service requirements to a network element responsible for sensing in the network, or can also send it to a network element responsible for sensing in the network through a network capability open function network element, in order to request to use the service requirements to sense the sensing area. In response to the sensing request, a network element responsible for the sensing function in the communication network can initiate a sensing process of using the service requirements to sense a specific sensing area.

[0004] However, there is currently no relevant security process for sensing a specific sensing area. Summary of the Invention

[0005] This application provides a communication method, related devices, and systems, in order to flexibly respond to a sensing request according to a sensing area and meet the restrictions of different sensing areas on service requirements.

[0006] In a first aspect, this application provides a communication method, which can be applied to a communication device. For example, the communication device can be a sensing function network element, or a component (such as a chip, chip system, etc.) configured in a sensing function network element, or can also be a logic module or software capable of implementing all or part of the functions of a sensing function network element. This application does not make any limitations in this regard. For ease of understanding and description hereinafter, an example of a sensing function network element as a communication device is used to describe this method.

[0007] Exemplarily, the method includes: 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 the target service requirement is used to determine the key performance indicator (KPI) of the sensing.

[0008] Wherein, the sensing request indicates the sensing area.

[0009] The above-mentioned target service requirement is determined according to the sensing area, that is to say, the service requirement corresponding to the sensing area requested by the sensing request is called the target service requirement.

[0010] It can be understood that the perceived KPIs define information such as confidence intervals, perceived positioning accuracy (including vertical and horizontal), perceived speed accuracy (including vertical and horizontal), perceived resolution (including area and speed), maximum perceived service delay, and refresh rate. Or rather, the parameters included in the perceived KPIs are used to describe the accuracy with which perceived data needs to be obtained.

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

[0012] In a possible implementation manner, the obtaining of the target service requirements includes: sending a service requirement request to the data management functional network element, where the service requirement request indicates the perception area; receiving N service requirements from the data management functional network element, where the N service requirements are determined according to the perception area, and N is a positive integer; and obtaining the target service requirement from the N service requirements.

[0013] This service requirement request is used to obtain the target service requirement.

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

[0015] In another possible implementation manner, the obtaining of the target service requirements includes: determining the N service requirements according to the perception area and the mapping relationship, where the mapping relationship indicates the correspondence between at least one perception area and at least one service requirement, and N is a positive integer; and obtaining the target service requirement from the N service requirements.

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

[0017] Optionally, when the perception area corresponds to N time periods and the N time periods correspond to N service requirements, the obtaining of the target service requirement from the N service requirements includes: when N>1, obtaining the target service requirement from the N service requirements according to the correspondence between the N service requirements and the N time periods, and the time information of the perception request.

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

[0019] Since the N service requirements correspond to the N time periods, according to the time information of the sensing request, a unique service requirement can be obtained from the N service requirements, and this service requirement is the target service requirement.

[0020] In another possible implementation, the sensing request carries N service requirements, where N is a positive integer; obtaining the target service requirement includes: obtaining the target service requirement from the N service requirements.

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

[0022] Combining the above three possible implementation manners, when N = 1, the N service requirements are the target service requirements.

[0023] Optionally, obtaining the target service requirement from the N service requirements includes: when N > 1, 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, obtaining the target service requirement from the N service requirements.

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

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

[0026] Optionally, before determining 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, the method further includes: obtaining the number of terminals included in the sensing area from the access and mobility management function network element.

[0027] Exemplarily, obtaining the number of terminals included in the sensing area from the access and mobility management function network element includes: sending a request for obtaining to the access and mobility management function network element, where the request for obtaining is used to request obtaining the number of terminals included in the sensing area; receiving an obtaining reply from the AMF network element, where the obtaining reply indicates the number of terminals included in the sensing area; determining the number of terminals included in the sensing area according to the obtaining reply.

[0028] Optionally, before obtaining the target service requirement, the method further includes: determining that sensing of the sensing area is allowed.

[0029] It can be understood that in the case where it is determined that sensing of the sensing area is not allowed, obtaining the target service requirement is replaced with: sending a rejection message to the application function network element, where the rejection message is used to reject the sensing request. That is to say, obtaining the target service requirement is executed when it is determined that sensing of the sensing area is allowed.

[0030] Optionally, 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, and a requested service requirement; 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 conditions is met: 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 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 that allows triggering.

[0031] Exemplarily, when the sensing request carries an identifier of an application function network element, an indication of the sensing area, a requested service type, and a requested service requirement, it is determined that sensing of the sensing area is allowed as long as one or more of the identifier of the application function network element, the sensing area, the requested service type, and the requested service requirement meet the above conditions. For example, when the identifier of the application function network element and the sensing area meet the above conditions, and the requested service type and the requested service requirement do not meet the above conditions, it is determined that sensing of the sensing area is allowed.

[0032] Optionally, 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, and a requested service requirement; before obtaining the target service requirement, the method further includes: determining to obtain the target service requirement when at least one of the following conditions is met: 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 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 that allows triggering.

[0033] Exemplarily, when the identifier of the application function network element, the indication of the sensing area, the type of the requested service, and the requirements of the requested service are carried in the sensing request, as long as one or more of the identifier of the application function network element, the sensing area, the type of the requested service, and the requirements of the requested service meet the above conditions, the target service requirements are obtained. For example, when the identifier of the application function network element and the sensing area meet the above conditions, but the type of the requested service and the requirements of the requested service do not meet the above conditions, the target service requirements are obtained.

[0034] Optionally, the sensing request comes from an application function network element, and the sensing request carries the requirements of the requested service. The method further includes: sending 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 requirements, and the target service requirements are different from the requirements of the requested service; receiving a service requirement confirmation reply from the application function network element, where the service requirement confirmation reply indicates whether to agree or not to adopt the target service requirements.

[0035] Exemplarily, in the case where the service requirement confirmation reply indicates agreement to adopt the target service requirements, a sensing process is initiated based on the target service requirements; or, in the case where the service requirement confirmation reply indicates disagreement to adopt the target service requirements, it is determined that sensing is not agreed to be performed.

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

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

[0038] In a second aspect, the present application provides a communication method, which can be applied to a communication device. For example, the communication device can be a data management network element, or a component (such as a chip, a chip system, etc.) configured in the data management network element, or can also be a logic module or software capable of implementing all or part of the functions of the data management network element. The present application does not make any limitation in this regard. For the convenience of understanding and description hereinafter, an example where the data management network element is the communication device is used to describe this method.

[0039] Exemplarily, the method includes: receiving a service requirement request from a sensing function network element, where the service requirement request indicates a sensing area; determining N service requirements according to the sensing area and the mapping relationship, where the mapping relationship indicates the correspondence between at least one sensing area and at least one service requirement; sending the N service requirements to the sensing function network element.

[0040] Among them, the service requirement request is used to request the target service requirement, and the target service requirement is used to determine the perceived KPI. The above N service requirements include the target service requirement, and N is a positive integer.

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

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

[0043] It can be understood that when each sensing area in at least one sensing area corresponds to one service requirement, N = 1.

[0044] Optionally, when N = 1, determining the N service requirements according to the sensing area and the mapping relationship includes: determining at least one service requirement according to the sensing area and the mapping relationship; determining the N service requirements from the at least one service requirement according to the corresponding relationship between the at least one service requirement and at least one time period, and the time information of the service requirement request.

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

[0046] Among them, the time information of the service requirement request may be the time when the data management network element receives this service requirement request.

[0047] Optionally, when N>1, the method further includes: sending the corresponding relationship between the N service requirements and N intervals of the number of terminals to the SF network element, so that the SF can determine the target service requirement from the N service requirements according to this corresponding relationship and the number of terminals included in the sensing area.

[0048] Optionally, the method further includes: receiving 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 sensing of a sensing area; determining whether to authorize or not authorize the sensing request; in the case of determining authorization, sending an authorization message to the network capability open function network element, where the authorization message is used to authorize the sensing request; or, in the case of determining non-authorization, sending a rejection authorization message to the network capability open function network element, where the rejection authorization message is used to reject authorization for the sensing request.

[0049] Optionally, the determining whether to authorize or not authorize the sensing request includes: determining whether to authorize or not authorize the sensing request according to the identifier of the application function network element.

[0050] Optionally, the method further includes: in the case of determining to authorize the sensing request according to the identifier of the application function network element, determining whether the service requirements of the request meet the service requirements corresponding to the sensing area included in the mapping relationship; and, in the case of meeting, determining to authorize the sensing request; or, in the case of not meeting, determining to reject the sensing request.

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

[0052] In a third aspect, the present application provides a communication method, which can be applied to a communication device. For example, the communication device can be a data management network element, or a component (such as a chip, a chip system, etc.) configured in the data management network element, or can also be a logic module or software capable of implementing all or part of the functions of the data management network element, and the present application does not limit this. For ease of understanding and description below, the method is described by taking the data management network element as an example of the communication device.

[0053] Exemplarily, the method includes: receiving 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 sensing of a sensing area; in the case of determining to authorize the sensing request, determining N service requirements according to the sensing area and the mapping relationship, where the mapping relationship indicates a correspondence between at least one sensing area and at least one service requirement; sending the N service requirements to the network capability open function network element.

[0054] For the description of the data management network element determining N service requirements according to the sensing area and the mapping relationship, reference can be made to the relevant description in the second aspect, and details are not repeated here.

[0055] Based on this technical solution, when the data management network element receives a sensing authorization request and determines to authorize the sensing request, it can obtain at least one service requirement corresponding to the sensing area based on the sensing area and the mapping relationship, and send the obtained at least one service requirement to the network capability open function network element, and then send it to the sensing function network element, so that the sensing function network element can obtain the target service requirement corresponding to the sensing area from the received service requirements. Therefore, the method provided in the embodiments of the present application can flexibly respond to the sensing request according to the sensing area to meet the restrictions of different sensing areas on service requirements, and solves the problem that all service requirements are the same when sensing the same service requirement for different sensing areas.

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

[0057] Optionally, the sensing authorization request carries the identifier of the application function network element, and the method further includes: determining whether to authorize or not authorize the sensing request according to the identifier of the application function network element.

[0058] Exemplarily, if the application function network element identified by the identifier of the application function network element belongs to the range of predefined application function network elements allowed to be authorized, the data management network element can determine to authorize the sensing request, otherwise the data management network element determines to reject the sensing request.

[0059] Optionally, the sensing authorization request further carries the requested service requirement, and the method further includes: when it is determined to authorize the sensing request according to the identifier of the application function network element, determining whether the requested service requirement meets the service requirement corresponding to the sensing area included in the mapping relationship; and, when it does not meet, determining to reject the sensing request; or, when it meets, determining to authorize the sensing request.

[0060] Or, when the data management network element determines to authorize the sensing request according to the identifier of the application function network element, further determining whether the requested service requirement meets the service requirement corresponding to the sensing area included in the above mapping relationship.

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

[0062] Fourth aspect, the present application provides a communication method, which can be applied to a communication device. For example, the communication device can be an application function network element, or a component (such as a chip, a chip system, etc.) configured in the application function network element, or can also be a logical module or software capable of implementing all or part of the functions of the application function network element. The present application does not make any limitation in this regard. For the convenience of understanding and description hereinafter, the application function network element is taken as an example of the communication device to describe this method.

[0063] Exemplarily, the method includes: receiving a service requirement confirmation request from a sensing 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; sending a service requirement confirmation reply to the sensing function network element, where the service requirement confirmation reply indicates whether to agree or disagree to adopt the target service requirement.

[0064] Optionally, in the case where the service requirement confirmation reply indicates disagreement to adopt the target service requirement, receiving a rejection message from the sensing function network element, where the rejection message is used to reject the sensing request.

[0065] Fifth aspect, the present application provides a communication method, which is applied to a system including a sensing function network element and a data management network element. The method includes: the sensing function network element receives a sensing request, where the sensing request is used to request to sense a sensing area; the sensing function network element sends a service requirement request to the data management network element, and the service requirement request carries the sensing area; the data management network element determines N service requirements according to the sensing area and the mapping relationship, where the N service requirements include the target service requirement, and the target service requirement is used to determine the sensing KPI; the data management network element sends the N service requirements to the SF.

[0066] Wherein, the mapping relationship indicates the corresponding relationship between at least one sensing area and at least one service requirement. The service requirement request is used to request to obtain the target service requirement.

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

[0068] In a sixth aspect, the present application provides a communication method applied to a system including a sensing function network element. The method includes: the sensing function network element receives a sensing request for requesting sensing of a sensing area; the sensing function network element determines a target service requirement according to the sensing area, where the target service requirement is determined according to the sensing area and is used to determine a KPI for sensing.

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

[0070] In a seventh aspect, the present application provides a communication method applied to a system including a data management network element, a network exposure function network element, and a sensing function network element. The method includes: the NEF sends a sensing authorization request to the data management network element, where the sensing authorization request is used to request authorization for a sensing request from the AF, and the sensing request is used to request sensing of a sensing area; when the data management network element determines to authorize the sensing request, it determines N service requirements according to the sensing area and a mapping relationship, where the mapping relationship indicates a corresponding relationship between at least one sensing area and at least one service requirement; the data management network element sends the N service requirements to the network capability exposure function network element; the network exposure function network element sends a sensing request carrying the N service requirements to the sensing function network element; the sensing function network element determines a target service requirement from the N service requirements, and the target service requirement is used to determine a KPI.

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

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

[0073] In a ninth aspect, the present application provides a communication device, including a processor configured to execute the methods described in the above first to fourth aspects and any possible implementation manners in the first to fourth aspects.

[0074] The device 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 the instructions stored in the memory, the methods described in the above aspects can be implemented.

[0075] The device may further include a communication interface for the device 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.

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

[0077] In a possible design, the chip system further includes a memory for storing program instructions and data, and the memory is located inside or outside the processor.

[0078] The chip system may be composed of chips or may include chips and other discrete devices.

[0079] In a possible design, the chip system further includes an interface circuit and / or a power supply circuit. The interface circuit is used for transmitting data, and the power supply circuit is used for supplying power to the chip system.

[0080] In an eleventh aspect, the present application provides a computer-readable storage medium, including a computer program, which when running on a computer, enables the computer to implement the methods in the above first to fourth aspects and any possible implementation manners in the first to fourth aspects.

[0081] In a twelfth aspect, the present application provides a computer program product, which includes: a computer program (which may also be referred to as code or instructions), and when the computer program is run, enables the computer to execute the methods in the above first to fourth aspects and any possible implementation manners in the first to fourth aspects.

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

[0083] Optionally, this communication system can be used to implement the methods described in the aforementioned fifth aspect and any possible implementation manner of the fifth aspect.

[0084] It should be understood that the technical solutions of the eighth to thirteenth aspects of the present application correspond to those of the first to fourth aspects of the present application, and the beneficial effects obtained by each aspect and the corresponding feasible implementation manners are similar, and will not be elaborated herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] Figure 1 is a schematic diagram of the integrated architecture of the communication system provided by an embodiment of the present application;

[0086] Figure 2 is a schematic diagram of the independent architecture of the communication system provided by an embodiment of the present application;

[0087] Figure 3 is a schematic diagram of a network architecture based on a service-based architecture (SBA) provided by an embodiment of the present application;

[0088] Figure 4 is a schematic diagram of a base station performing a sensing operation;

[0089] Figure 5 is a schematic diagram of parameters affecting sensing accuracy and resolution;

[0090] Figures 6 to 9 is a schematic flowchart of the communication method provided by an embodiment of the present application;

[0091] Figure 10 and Figure 11 is a schematic block diagram of the communication device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0092] Next, the technical solutions in the present application will be described in conjunction with the accompanying drawings.

[0093] For the convenience of understanding the embodiments of the present application, the following explanations are made first:

[0094] First, in the embodiments of the present application, the use of prefix words such as "first" and "second" is only for the convenience of distinguishing and describing different things belonging to the same name category, and does not restrict the order, size, or quantity of things. For example, the "first mapping relationship" and the "second mapping relationship" are only different mapping relationships, and there is no relationship of time sequence, size, or priority between them.

[0095] Second, the "send" and "receive" in the embodiments of the present application represent the direction of signal transmission. For example, "sending a sensing authorization request to the unified data management (UDM)" can be understood as the destination of the sensing authorization request being the UDM, and it can include other units or modules indirectly sending to the UDM. "Receiving a sensing authorization request from the network exposure function (NEF)" can be understood as the source of the sensing authorization request being the NEF, and it can include receiving indirectly from the NEF through other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

[0096] In other words, sending and receiving can be carried out between devices. For example, between the NEF and the UDM; it can also be carried out within a device. For example, sending or receiving between components within a device, between modules, between chips, between software modules or between hardware modules through a bus, trace or interface.

[0097] It can be understood that before the information is sent from the source to the destination, necessary processing may be performed, such as encoding, modulation, etc. After the destination receives the information from the source, corresponding processing can also be performed, such as decoding, demodulation, etc., so as to interpret the valid information from the source. Similar expressions in the present application can be understood similarly and will not be elaborated here.

[0098] Third, in the embodiments of the present application, "at least one" means one or more, and "a plurality of" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the front and back associated objects, but does not exclude the case where it represents a "and" relationship between the front and back associated objects. The specific meaning represented can be understood in combination with the context. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a, b, and c. Where a, b, and c can be single or multiple.

[0099] 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 piece of information (such as the indication information described below) is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. For example, but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated, etc. It is also possible to indirectly indicate the information to be indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated; it is also possible to only indicate a part of the information to be indicated, while the other parts of the information to be indicated are known or pre-agreed. For example, the arrangement order of each piece of information pre-agreed (such as protocol pre-definition) can be used to indicate specific information, thereby reducing the indication overhead to a certain extent. The present application does not limit the specific manner of indication.

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

[0101] Fifth, the tables in the embodiments of the present application are only examples. The values of the information in each table are only for illustration and can be configured as other values, which are not limited by the present application. Each table does not limit the protection scope of the present application. For example, appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. For another example, the parameter names shown in the titles of each table can also be other names understandable by the communication device, and the values or representation methods of its parameters can also be other values or representation methods understandable 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 maps, etc.

[0102] 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 perform corresponding processing under a certain objective situation, which does not limit the time, and does not require the device (such as SF or UDM) to have a judgment action when implementing, nor does it mean other limitations.

[0103] Seventh, the pre-definition in the present application can be understood as: definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-firing.

[0104] The technical solutions provided by this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD), SideLink (SL) communication systems, Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) mobile communication systems or New Radio Access Technology (NR), satellite communication systems, etc. Among them, the 5G mobile communication system can include Non-Standalone (NSA) and / or Standalone (SA).

[0105] The technical solutions provided by this application can also be applied to future communication systems, such as 6th Generation (6G) mobile communication systems, etc. This application does not make any limitations in this regard.

[0106] For ease of understanding, first, the network architecture applicable to the method provided in the embodiments of this application will be described in more detail with reference to the accompanying drawings.

[0107] Figure 1 and Figure 2 respectively show two possible architectures in the 5G network: the converged architecture (see Figure 1 ) and the standalone architecture (see Figure 2 ). The difference between the converged architecture and the standalone architecture lies in the location where the SF dedicated to the sensing service is deployed.

[0108] As Figure 1 shown, in the converged architecture, the SF can be deployed in the traditional 5G Core Network (5GC), and is connected to other network elements using the SBA interface. For a more detailed description of SBA, reference can be made to Figure 3 , which will not be elaborated here for the time being. The SF is connected to the NEF and can interact with servers outside the 5GC through the NEF, such as receiving sensing request messages from external servers. The SF can also be connected to the User Plane Function (UPF), and radio access network (RAN) devices such as base stations can send the received sensing data to the SF for processing through the user plane.

[0109] As Figure 2As shown, in the stand-alone architecture, the SF deployment can be outside the traditional 5GC. The SF and other network elements cannot be connected using the SBA interface and may need to interact with other 5GC network elements through the relay of the NEF. On the one hand, the SF can also be connected to the NEF to interact with external servers through the NEF, or the SF can directly interact with external servers without going through the NEF relay. On the other hand, the SF can be connected to the RAN device to interact with the terminal device.

[0110] It should be understood that Figure 1 and Figure 2 The two possible architectures shown respectively are only exemplified by taking the architecture of 5GC as an example, and should not constitute any limitation to this application. The method provided by this application is not limited to being used in Figure 1 and Figure 2 the two architectures shown.

[0111] Figure 3 This is a schematic diagram of the SBA network architecture in the 5G network provided by the embodiments of this application. As Figure 3 shown, the 5G network architecture can include three parts, namely the terminal, the data network (DN), and the operator network.

[0112] The following briefly describes the network elements involved in Figures 1 to 3 this.

[0113] The terminal can also be called a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile device, 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.

[0114] The terminal is a device with wireless transceiver functions. The terminal can communicate with one or more core network (CN) devices (or called core devices) through access network devices (or called access devices) in the radio access network. The terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (such as an airplane, a balloon, and a satellite, etc.).

[0115] The terminal can also be a terminal in the internet of things (IoT) system and can also be called an IoT node. The IoT is an important part of the future development of information technology. Its main technical feature is to connect items to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and thing-thing interconnection. The connection can be through broadband technology or through narrow band (NB) technology. The IoT technology can achieve massive connections, deep coverage, and power saving of the terminal through, for example, narrow band technology.

[0116] In the embodiments of the present application, the device for implementing the functions of the terminal may be the terminal itself, or a device capable of supporting the terminal to implement such functions, such as a chip system. This device may be installed in the terminal or used in combination with the terminal. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete components. In the embodiments of the present application, only the case where the device for implementing the functions of the terminal is the terminal is taken as an example for illustration, which does not limit the solutions of the embodiments of the present application.

[0117] The terminal in the present application may be a hardware device, or a software function running on dedicated hardware, or a software function running on general hardware, or a virtualized device. For example, it can be implemented through general hardware and instantiated virtualization functions, or dedicated hardware and instantiated virtualization functions. Among them, the general hardware may be a server, such as a cloud server.

[0118] 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 (SMF) network element, UPF network element, SF network element, and access network (AN) (such as RAN network element), etc. In the above operator network, the part other than the RAN network element can be called the core network part. For the convenience of description hereinafter, the term "network element" is omitted. For example, the AF network element is abbreviated as AF, the UDM network element is abbreviated as UDM, the SF network element is abbreviated as SF, and so on.

[0119] RAN is a network composed of multiple RAN nodes, which implements functions such as wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management functions. 5G-RAN can be connected to the user plane function (UPF) through the user plane interface N3 for transmitting data of terminal devices; 5G-RAN establishes a control plane signaling connection with the access and mobility management function (AMF) through the control plane interface N2 for implementing functions such as wireless access bearer control.

[0120] RAN nodes can provide wireless communication function services to connect terminals to the wireless network. RAN nodes can also be referred to as RAN devices, access network devices, etc.

[0121] In a possible scenario, RAN nodes can be base stations, evolved NodeBs (eNodeBs), access points (APs), transmission reception points (TRPs), next generation NodeBs (gNBs), next generation base stations in the 6th generation (6G) mobile communication system, or base stations in future mobile communication systems. RAN nodes can be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, or wireless controllers in the cloud radio access network (CRAN) scenario. Optionally, RAN nodes can also be servers.

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

[0123] In different systems, the CU (or CU-CP and CU-UP), DU, or RU can also have different names, but those skilled in the art can understand their meanings. For example, in an open RAN (O-RAN or ORAN) system, the CU can also be called an open CU (O-CU), the DU can also be called an O-DU, the CU-CP can also be called an O-CU-CP, the CU-UP can also be called an O-CU-UP, and the RU can also be called an O-RU. For the convenience of description, in this application, the CU, CU-CP, CU-UP, DU, and RU are taken as examples for description. Any one of the 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.

[0124] In the embodiments of this application, the device for implementing the functions of the RAN node can be the RAN node itself; it can also be a device capable of supporting the RAN node to implement this function, such as a chip system, a hardware circuit, a software module, or a combination of a hardware circuit and a software module. This device can be installed in the RAN node or used in matching with the RAN node. In the embodiments of this application, only the case where the device for implementing the functions of the RAN node is the RAN node is taken as an example for illustration, which does not limit the solutions of the embodiments of this application.

[0125] The RAN nodes in this application can be hardware devices, or software functions running on dedicated hardware, or software functions running on general hardware, and can also be virtualized devices. For example, they can be implemented through general hardware and instantiated virtualization functions, or through dedicated hardware and instantiated virtualization functions. Among them, the general hardware can be a server, such as a cloud server.

[0126] The SF is mainly responsible for the relevant processing of the sensing service. For example, it determines the sensing result based on the obtained sensing data, such as whether there is an intrusion, or calculates the distance, direction, and position of the reflective object within the sensing area.

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

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

[0129] As the anchor point of the protocol data unit (PDU) session connection, the UPF is responsible for filtering terminal data packets, data transmission / forwarding, rate control, generating charging information, etc.

[0130] The UDR is mainly used to store user data, including subscription data called by the UDM, policy information called by the PCF, structured data for capability open, application data called by the NEF, etc.

[0131] The UDM is mainly used to manage user data. For example, it manages subscription information, including obtaining subscription information from the UDR and providing it to other network elements (such as the AMF); generates 3GPP authentication credentials for the terminal; registers and maintains the network elements currently serving the terminal (for example, the AMF represented by AMF ID1 is the current serving AMF of the terminal, serving AMF).

[0132] The NEF is used for the interaction between other internal network elements of the core network and the application function (AF) network elements corresponding to the external application servers (AS) of the core network, so as to provide network open capabilities to the AF or provide the information provided by the AF to the core network elements.

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

[0134] The PCF mainly performs policy control such as quality of service (QoS) policies and charging policies. It provides configuration policy information for the terminal and policy information for controlling the terminal for network control plane network elements (such as the AMF and SMF).

[0135] The AF mainly transmits the requirements of the application side for the network side and can be regarded as an application server or an agent of the application server. The AF can interact with core network elements to provide some services. For example, it interacts with the PCF for service policy control, interacts with the NEF to obtain some network capability information or provide some application information to the network, and provides some data network access point information to the PCF to generate corresponding routing information for data services.

[0136] The DN mainly provides service services for users.

[0137] Each network element communicates 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, Figure 1 Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nausf, Namf, Nsmf, and Nsf in [] are service-based interfaces based on services. Among them, the interface Nsf is only a possible name, and this application does not limit the name of the service-based interface corresponding to the SF.

[0138] The above description of each network element in the core network and the interfaces between each network element is only an exemplary illustration and should not constitute any limitation to this application. In addition, each network element shown in the figure can be understood as a network element in the core network for implementing different functions. For example, it can be combined into network slices as needed. These core network elements can be independent devices or can be integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.

[0139] It can be understood that the network elements applied in future communication systems can be the above network elements, or they can also be network elements with other names having the same or similar functions. This application does not limit this.

[0140] In the embodiments of the present application, the device for implementing each function of the core network may be a core network element corresponding to each function; or it may be a device capable of supporting the core network element to implement its respective 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 core network element or used in combination with the core network element. In the embodiments of the present application, only the case where the device for implementing the core network function is a core network element is taken as an example for illustration, which does not limit the solutions of the embodiments of the present application.

[0141] The core network element in the present application may be a hardware device, or a software function running on dedicated hardware, or a software function running on general hardware, or a virtualized device, for example, implemented by general hardware and instantiated virtualization functions, or dedicated hardware and instantiated virtualization functions. Among them, the general hardware may be a server, such as a cloud server.

[0142] Currently, some base stations or terminals in the RAN have the sensing ability brought by electromagnetic waves and can be used as sensing nodes. The realization of sensing is similar to the principle of radar. That is, the transmitter (i.e., the sensing node) emits electromagnetic waves, and the electromagnetic waves are reflected by the object to be sensed and then acquired by the receiver. The receiver (i.e., the sensing node) can further process the acquired reflected signal (which can be called sensing raw data) to obtain sensing data, and this sensing data can be used to obtain sensing results.

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

[0144] Table A

[0145]

[0146]

[0147] Figure 4 is a schematic diagram of the base station performing sensing operations. Figure 4 is an example of integrated sensing and communication (ISAC). Figure 4 The base station shown can reuse the electromagnetic wave signal of the communication system for sensing. As Figure 4 shown, the resources for the base station to communicate and the resources for sensing can be time-division multiplexed (as Figure 4As shown, it can also be space-division multiplexed. The base station can use electromagnetic wave signals for sensing detection, and at the same time can also receive the signals (which can be simply referred to as reflected signals or echo signals) that are transmitted back after reaching the obstacle (i.e., the detected target object), and obtain sensing data based on the echo signals. For example Figure 4 As shown, 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 signal to be transmitted. The base station can also perform analog-to-digital conversion, parallel-to-serial conversion, fast Fourier transform, serial-to-parallel conversion, demodulation, etc. on the received echo signal. The signal to be transmitted can 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 can be understood that the echo signal here is the echo signal after the above processing). It should be understood that Figure 4 the processing performed by the base station on the signal to be transmitted and the received echo signal shown is only an example and should not constitute any limitation to this application

[0148] The sensing nodes in the communication system can sense and identify specified areas, specified objects or events, and meet sensing requirements in multiple aspects such as autonomous driving, safety supervision, home health, and meteorological monitoring. Specific examples are as follows

[0149] I. Autonomous driving

[0150] In the V2X and unmanned aerial vehicle (UAV) scenarios, for example, due to the short sensing distance of the vehicle or UAV or the inability to sense the non-line-of-sight (NLOS) path, a dynamic map can be generated based on the sensing data; for another example, during the driving process of the vehicle or UAV, there may be traffic hazard events such as pedestrians or non-motor vehicles suddenly appearing or pedestrians or non-motor vehicles being in the blind spot of the field of vision. The hazard events can be identified based on the sensing data and the vehicle or UAV can be notified to perform emergency operations; for still another example, in the autonomous driving assistance of the vehicle or UAV, a customized high-precision dynamic map can be generated based on the sensing data to assist the vehicle or UAV in autonomous driving

[0151] II. Safety supervision

[0152] In the V2X and UAV scenarios, it is possible to identify illegal driving of vehicles or UAVs based on sensing data, such as a vehicle occupying the emergency lane, a UAV leaving the route for driving, etc., and real-time warnings can be executed

[0153] In perimeter security scenarios, foreign objects intruding into railway tracks or drones intruding into no-fly zones (such as airports) can be detected based on perception data, and the illegal objects can be tracked and real-time emergency processing can be performed.

[0154] 3. Family Health

[0155] For example, abnormal postures can be identified based on the perception data, so that falls and other situations can be identified and timely alarms can be issued. For another example, the perception data can be used to obtain physiological parameters such as human breathing or heartbeat, so that abnormalities can be identified and timely alarms can be issued.

[0156] 4. Meteorological monitoring

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

[0158] Figure 5 Schematic diagram of parameters that affect perception accuracy and resolution. Figure 5 Taking the Internet of Vehicles scenario as an example, several parameters affecting the key performance indicators (KPIs) of perception, including perception positioning accuracy (including vertical and horizontal), perception speed accuracy (including vertical and horizontal), and perception resolution (including area and speed), are shown.

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

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

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

[0162] 4. Horizontal field of view (FOV): 120°. When the width of a two-way road is 30 meters, the two-way blind spot range is less than 18 meters, and the blind spot area ratio is <1%.

[0163] The sensing nodes in 5G can be RAN and terminal. According to the combination of different sensing nodes, multiple sensing modes can be obtained. According to the role of the sensing node in the sensing process: transmitter or receiver, and the type of sensing node: RAN or terminal, six sensing modes can be obtained as shown in Table 1.

[0164] Table 1

[0165]

[0166] The six sensing modes shown in Table 1 are distinguished for the transmitter and receiver of the sensing signal, specifically: the RAN node sends and receives by itself, RAN node A sends and RAN node B receives, the RAN node sends and the terminal receives, the terminal sends and the RAN node receives, the terminal sends and receives by itself, and terminal A sends and terminal B receives. It can be seen that the transmitter can be a terminal or a RAN node; the receiver can be a terminal or a RAN node.

[0167] To better understand the method provided in the embodiments of the present application, the following will briefly explain the terms involved in the present application.

[0168] 1. Key Performance Indicators (KPIs) of sensing: The 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 22.173 defines the following parameters for sensing KPIs: confidence interval, sensing positioning accuracy (including vertical and horizontal), sensing speed accuracy (including vertical and horizontal), sensing resolution (including area and speed), maximum sensing service delay, and refresh rate, etc. These parameters can be used to describe how precisely the sensing data needs to be obtained.

[0169] Of course, these parameters are only an example of the sensing KPIs, and the present application does not limit the specific parameters included in the sensing KPIs.

[0170] In the existing sensing process, the AF / application server (AS) of the sensing application can send a sensing request message to the NEF, and carry the service type, service requirements, and external area information in the sensing request, for requesting the network to perform sensing according to the sensing request information and feedback the corresponding sensing result. The AF, AS of the sensing application, or the terminal carrying the sensing application can also directly send a sensing request message to the network element responsible for the sensing function in the communication network. The service requirements are those put forward by the sensing application to the network for describing the accuracy requirements of the sensing application for the sensing result.

[0171] In the existing sensing process, the sensing application may put forward the same service requirements for the same service type in all areas. However, in the actual sensing scenario, there may be different sensing accuracy limitations in different sensing areas. For example, for residential areas, the accuracy needs to be reduced to protect personal privacy, while for the detection of drone intrusion in an open environment, the accuracy needs to be increased to eliminate false alarms caused by objects such as birds, that is, the service requirements corresponding to different sensing areas may be different. Therefore, if the existing sensing process continues to be used to sense the sensing area, it may not be able to meet the limitations of the service requirements for different sensing areas.

[0172] In view of this, embodiments of the present application provide a communication method, related devices, and a system. In this method, when the network side receives a sensing request from a sensing application, the service requirement corresponding to the sensing area is determined by using the correspondence between the sensing area carried in the sensing request and the pre-stored sensing area and service requirement on the network side, so as to meet the sensing accuracy limitations for different areas.

[0173] The following combines Figures 6 to 9 to describe in detail the method provided by the embodiments of the present application. The method provided by the embodiments of the present application can be applied to Figure 1 or Figure 2 the network architectures shown, but the embodiments of the present application are not limited thereto.

[0174] Figure 6 FIG. is a schematic flowchart of a communication method 600 provided by the embodiments of the present application. As Figure 6 shown, the method 600 may include S601 and S602. The following details each step in the method 600.

[0175] S601, the NEF sends a sensing request to the SF, and this sensing request is used to request sensing of a sensing area. Correspondingly, the SF receives the sensing request from the NEF.

[0176] Alternatively, in S601, the AF sends a sensing request to the SF. Correspondingly, the SF receives the sensing request from the terminal. At this time, the AF does not send a sensing request to the AF through the NEF.

[0177] Alternatively, in S601, the terminal sends a sensing request to the SF. Correspondingly, the SF receives the sensing request from the terminal.

[0178] Among them, the sensing request indicates the above-mentioned sensing area. The sensing area is used to describe the area that needs to be sensed, and the area to be sensed can be described by using the identifier of the area to be sensed in or outside the communication system. The sensing area may include one or more of the following: coordinate information, geographical area identifier, address information, tracking area identifier (TAI), cell identifier (cell ID). It should be noted that the sensing area may be other information, and the present application does not make any limitation thereto. For the convenience of description hereinafter, the sensing request from the NEF is referred to as sensing request #1, and the sensing area indicated in the sensing request #1 is referred to as sensing area #1. That is, the sensing request #1 is used to request sensing of the sensing area #1. The sensing request from the AF is referred to as sensing request #2, and the sensing area indicated in the sensing request #2 is referred to as sensing area #2. That is, the sensing request #2 is used to request sensing of the sensing area #2.

[0179] The above-mentioned sensing area #1 is the identifier of the sensing area in the communication system, and the sensing area #2 is the identifier of the sensing area outside the communication system. Since the AF does not know the identifier of the sensing area in this communication system, the sensing area indicated by the AF is the identifier outside the communication system to distinguish it from the identifier of the sensing area in the communication system.

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

[0181] Among them, the identifier of the AF may be the AF ID or other information that can identify the AF.

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

[0183] Service type #1 may be one or more of at least one predefined service type. The at least one service type may include, for example, but is not limited to, drone intrusion detection, autonomous driving, security supervision, home health, or meteorological monitoring, etc. This application includes but is not limited to this.

[0184] Service type #1 is used to indicate one or more of at least one predefined service type; the requested service requirements can be used to describe the requirements for the sensing result of the request. For example, the requested service requirements include one or more of the following: sensing location accuracy, sensing speed accuracy, sensing resolution, or the duration required for sensing. The service requirements can be used to determine the KPI corresponding to the sensing result requested by this sensing request.

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

[0186] The target service requirements are used to determine the KPI of the sensing.

[0187] Among them, the target service requirements may be the KPI or may include information for determining the KPI. If the target service requirements include information for determining the KPI, the SF can convert the target service requirements into the KPI. In other words, one possible implementation of the SF based on the target service requirements to determine the KPI for sensing the sensing area is to determine the target service requirements as the KPI for sensing the terminal, and another possible implementation is to convert the target service requirements into the KPI for sensing the sensing area.

[0188] 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 then returning it to the SF.

[0189] For example, if the sensing area is a residential area and privacy of users in the residential area is to be protected during sensing, the target service requirement can be determined as a service requirement with relatively low sensing accuracy. This way of determining the target service requirement in combination with the sensing area can effectively prevent user privacy from being exposed, reduce the leakage of sensitive information, and effectively and flexibly provide network openness capabilities.

[0190] Exemplarily, the SF obtaining the target service requirement according to the sensing area includes: the SF obtaining the target service requirement according to the sensing area and the first mapping relationship. The UDM obtaining the target service requirement according to the sensing area includes: the UDM obtaining the target service requirement according to the sensing area and the first mapping relationship. Since the specific method for the SF to obtain the target service requirement will be described in detail later, it will not be elaborated here for the time being.

[0191] The first mapping relationship in this application indicates that at least one sensing area corresponds to at least one service requirement. It should be understood that each sensing area in the at least one sensing area may correspond to one service requirement; or, one of the at least one sensing areas includes a specific sensing area that corresponds to multiple service requirements.

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

[0193] Among them, the above at least one service requirement may include a default service requirement. The default service requirement may be a predefined service requirement. Or, the default service requirement is used to indicate that the service requirement carried in the sensing request is determined as the target service requirement. Or, the default service requirement is defined as the service requirement requested by the sensing request without pre-configuring the default service requirement.

[0194] Table 2

[0195] Perception area Service requirements Location 1 Default service requirements Location 2 Minimum service requirements Location 3 Medium service requirements

[0196] Table 2 shows an example of a first mapping relationship. Positions 1, 2, and 3 shown in Table 2 represent three different sensing regions, and the first mapping relationship is used to represent the service requirements corresponding to the three positions of the same service type. Among them, the level of the default service requirement is higher than that of the medium service requirement, and the level of the medium service requirement is higher than that of the lowest service requirement. For example, in the indicators corresponding to the lowest service requirement, the sensing position accuracy is 1 m, in the indicators corresponding to the medium service requirement, the sensing position accuracy is 1 cm, and in the indicators corresponding to the default service requirement, the sensing position accuracy is 1 mm. Since the accuracies of 1 m, 1 cm, and 1 mm increase in sequence, it can be considered that the level of the default service requirement is higher than that of the medium service requirement, and the level of the medium service requirement is higher than that of the lowest service requirement; for another example, in the indicators corresponding to the lowest service requirement, the sensing resolution is 1 m, in the indicators corresponding to the medium service requirement, the sensing resolution is 1 cm, and in the indicators corresponding to the default service requirement, the sensing resolution is 1 mm. Since the accuracies of 1 m, 1 cm, and 1 mm increase in sequence, it can be considered that the level of the default service requirement is higher than that of the medium service requirement, and the level of the medium service requirement is higher than that of the lowest service requirement; for another example, in the indicators corresponding to the lowest service requirement, the sensing service delay is 1 s, in the indicators corresponding to the medium service requirement, the sensing service delay is 1 ms, and in the indicators corresponding to the default service requirement, the sensing service delay is 0.1 ms. Since the accuracies of 1 s, 1 ms, and 0.1 ms increase in sequence, it can be considered that the level of the default service requirement is higher than that of the medium service requirement, and the level of the medium service requirement is higher than that of the lowest service requirement.

[0197] In the embodiment of the present application, after receiving a sensing request for requesting sensing of a sensing region, the SF may use the sensing region as an input to obtain the target service requirement corresponding to the sensing region. That is to say, after receiving different sensing requests for requesting sensing of different sensing regions, the SF can flexibly respond to the sensing requests according to the sensing regions to meet the restrictions of different sensing regions on service requirements, and solves the problem that all service requirements are the same when sensing the same service requirement for different sensing regions.

[0198] Optionally, before S601, the method 600 further includes: the NEF sends a sensing authorization request to the UDM, and the sensing authorization request is used to request authorization for a sensing request from the AF (hereinafter, for convenience of description, the sensing request from the AF is referred to as sensing request #2), and the sensing request #2 is used to request sensing of a sensing region #2 (for example, a specific location or a geographical range); the UDM receives the sensing authorization request from the NEF and determines whether to authorize or not authorize the sensing request #2; in the case of determining authorization, the UDM sends an authorization message to the NEF, and the authorization message is used to authorize the sensing request; or, in the case of determining non-authorization, the UDM sends a rejection authorization message to the NEF, and the rejection authorization message is used to reject authorization for the sensing request.

[0199] It should be noted that when the UDM determines an authorization awareness request, the NEF can continue to execute S601.

[0200] The above-mentioned awareness authorization request indicates the awareness area #1, and the above-mentioned awareness request #2 indicates the awareness area #2. It should be understood that the geographical locations corresponding to the awareness areas indicated by the awareness request #1 and the awareness request #2 are the same, except that the form of the geographical location indicated by the awareness request #1 is the form recognizable by the operator network.

[0201] Exemplarily, the identifier of the AF is carried in the awareness authorization request; the UDM determines whether to authorize or not authorize the awareness request, which may include: determining whether to authorize or not authorize the awareness request according to the identifier of the AF.

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

[0203] Optionally, the awareness authorization request also carries service requirement #1, and the method 600 further includes: the UDM determines whether service requirement #1 meets the service requirement corresponding to the awareness area #1 included in the first mapping relationship; and, when service requirement #1 meets the service requirement corresponding to the awareness area #1 included in the first mapping relationship, determines to authorize the awareness request; or, when service requirement #1 does not meet the service requirement corresponding to the awareness area #1 included in the first mapping relationship, determines to reject the awareness request.

[0204] The above-mentioned service requirement #1 meets the service requirement corresponding to the awareness area #1 included in the first mapping relationship means that the level of service requirement #1 is not higher than the level of the first type of service requirement, and the first type of service requirement is the service requirement corresponding to the awareness area #1 included in the first mapping relationship.

[0205] Several examples where the level of the first type of service requirement is higher than the requested service requirement #1 are shown below: 1. Among the metrics corresponding to the first type of service requirement, the perceived position accuracy is 1 mm, and among the metrics corresponding to service requirement #1, the perceived position accuracy is 1 m. Since the accuracy of 1 mm is higher than that of 1 m, it can be considered that the level of this first type of service requirement is higher than the level of service requirement #1. 2. Among the metrics corresponding to the first type of service requirement, the perceived resolution is 1 m, and among the metrics corresponding to service requirement #1, the perceived resolution is 5 m. Since the perceived resolution of 1 m is higher than that of 5 m, it can be considered that the level of this first type of service requirement is higher than the level of service requirement #1. 3. Among the metrics corresponding to the first type of service requirement, the maximum perceived service latency is 0.2 ms, and among the metrics corresponding to service requirement #1, the maximum perceived service latency is 0.5 ms. Since the latency of 0.2 ms is shorter than that of 0.5 ms, it can be considered that the level of this first type of service requirement is higher than the level of service requirement #1.

[0206] Optionally, before the NEF sends a sensing authorization request to the UDM, the method 600 further includes: the AF sends a sensing request #2 to the NEF, where the sensing request #2 is used to request sensing of the sensing area #2, and the sensing area #2 is indicated in the sensing request #2; the NEF receives the sensing request #2 and determines the sensing area #2 as the sensing area #1.

[0207] For the descriptions of the sensing area #2 and the sensing area #1, reference can be made to the relevant descriptions above, and details are not repeated here.

[0208] Optionally, the SF obtaining the target service requirement in S602 may include the following three implementation manners.

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

[0210] Optionally, when N > 1, the SF obtaining the target service requirement from the N service requirements includes: The SF obtains the target service requirement from the N service requirements according to the number of terminals included in the sensing area #1 or the time information of the sensing request.

[0211] For example, if the time indicated by the time information of the sensing request is during the morning rush hour or the 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 service requirement can be determined as the service requirement with a higher sensing accuracy.

[0212] For another example, the larger the number of terminals included in the sensing area, the higher the processing complexity of the sensing node. Therefore, a lower-level service requirement can be adopted to sense the sensing area. If the number of terminals included in the sensing area is small, when sensing the sensing area, the processing capability requirement for the sensing node is low. Therefore, a higher-level service requirement can be adopted to sense the sensing area.

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

[0214] Exemplarily, when N>1, the SF obtains the target service requirement from the N service requirements according to the number of terminals included in the sensing area #1, including: the SF obtains 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 #1.

[0215] Exemplarily, when N>1, the SF obtains the target service requirement from the N service requirements according to the time information of the sensing request, including: the SF obtains the target service requirement from the N service requirements according to the correspondence between the N service requirements and the N time periods, and the time information of the sensing request. Exemplarily, the number of terminals included in the sensing area #1 in the embodiments of this application can be obtained from the AMF.

[0216] Table III

[0217] Number of terminals (pcs) Service requirements Within 5 Default service requirements 6-15 Medium service requirements 16-50 Minimum service requirements 50+ Reject

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

[0219] Table IV

[0220] Time period Service requirements 5:00 - 7:00 Default service requirements Other time periods Minimum service requirements

[0221] Table IV shows the correspondence between the N service requirements and the N time periods when N = 2. As shown in the example of Table IV, it represents the service requirements corresponding to the 2 time periods of a specific service type in a specific sensing area.

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

[0223] For example, if the time indicated by the time information of the sensing request falls during the morning or evening rush hours, such as 7:00 - 9:00 or 17:00 - 19:00, there are a relatively large number of terminals on the subway during the morning and evening rush hours, and a sensing with a relatively high sensing accuracy may involve the leakage of some privacy or sensitive information. Therefore, the target service requirement can be determined as a service requirement with a relatively low sensing accuracy. This method of determining the target service requirement by combining the sensing area, the time of the sensing request, and the number of terminals included in the sensing area can effectively prevent the exposure of user privacy, reduce the leakage of sensitive information, and can effectively and flexibly provide network openness capabilities.

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

[0225] Exemplarily, when N > 1, the SF obtains the target service requirement from the N service requirements according to the number of terminals included in the sensing area #1 and the time information of the sensing request, including: the SF determines M service requirements from the N service requirements according to the third mapping relationship and the number of terminals included in the sensing area #1; the SF obtains the target service requirement from the M service requirements according to the correspondence between the M service requirements and the M time periods, and the time information of the sensing request.

[0226] Wherein, 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.

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

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

[0229] Table Five

[0230]

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

[0232] Table 6

[0233]

[0234] Table 6 shows an example of a third mapping relationship. As shown in the example of Table 6, it represents the service requirements corresponding to the range of the number of terminals and the time period in a specific sensing area for a specific service type.

[0235] Exemplarily, when N>1, the SF obtains the target service requirement from N service requirements according to the number of terminals included in the sensing area #1 and the time information of the sensing request, including: the SF obtains the target service requirement from N service requirements according to the fourth mapping relationship, the time information of the sensing request, and the number of terminals included in the sensing area #1, and the fourth mapping relationship indicates the corresponding relationship between at least one time period, at least one range of the number of terminals, and at least one service requirement.

[0236] For an example of the fourth mapping relationship, reference can be made to Table 5 and Table 6. The difference is that the SF directly obtains the target service requirement from N service requirements according to the time information of the sensing request and the number of terminals included in the sensing area #1, rather than first screening out M service requirements from N service requirements and then obtaining the target service requirement from the M service requirements.

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

[0238] Exemplarily, the SF determines at least one sensing area according to the service type #1, including: the SF determines at least one sensing area according to the service type #1 and the fifth mapping relationship, and the fifth mapping relationship indicates the corresponding relationship between at least one service type and at least one sensing area.

[0239] It can be understood that the sensing area corresponding to the service type #1 included in the fifth mapping relationship includes the sensing area #1.

[0240] Table 7

[0241]

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

[0243] Second possible implementation: The SF sends a service requirement request to the UDM. This service requirement request is used to request the acquisition of target service requirements, and the service requirement request indicates the sensing area #1. The UDM receives this service requirement request and determines N service requirements according to the sensing area #1 indicated by the service requirement request. The UDM sends the N service requirements to the SF. The SF receives the N service requirements and obtains the target service requirement from the N service requirements.

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

[0245] For the description of the first mapping relationship, reference can be made to the description in the first possible implementation above, and details will not be elaborated here.

[0246] When N = 1, the UDM determines N service requirements according to the sensing area #1 and the first mapping relationship as described above, including: The UDM determines P (P is a positive integer) service requirements according to the sensing area #1 indicated by the service requirement request and the first mapping relationship. Further, when P > 1, the method 600 may further include: The UDM determines N service requirements from the P service requirements according to the time information of the service requirement request.

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

[0248] When N = 1, the UDM determines N service requirements according to the sensing area #1 and the first mapping relationship as described above, including: The UDM determines N service requirements according to the sensing area #1 indicated by the service requirement request, the time information of the service requirement request, the number of terminals included in the sensing area #1, and the fourth mapping relationship. Among them, the fourth mapping relationship includes the first mapping relationship.

[0249] Exemplarily, the number of terminals included in the sensing area #1 can be obtained by the UDM from the AMF or obtained locally.

[0250] When N > 1, the UDM determines N service requirements according to the sensing area #1 and the first mapping relationship as described above, which may include: The UDM determines P (P is a positive integer) service requirements according to the sensing area #1 indicated by the service requirement request and the first mapping relationship. Further, when P > 1, the method 600 may further include: The UDM determines N service requirements from the P service requirements according to the time information of the service requirement request.

[0251] Optionally, the UDM determines N service requirements from P service requirements according to the time information requested by the service requirements, including: the UDM determines N service requirements from P service requirements according to the second mapping relationship (or the third mapping relationship) and the time information requested by the service requirements.

[0252] Wherein, the time information requested by the service requirements may be the time when the UDM receives the service requirements request, or the time information of the above-mentioned sensing request.

[0253] Optionally, when N>1, the method 600 further includes: the UDM sends the correspondence between N service requirements and N intervals of the number of terminals to the SF. Correspondingly, the SF receives the correspondence from the UDM, and obtains the target service requirement from the N service requirements according to the correspondence between N service requirements and N intervals of the number of terminals, and the number of terminals included in the sensing area #1.

[0254] Similar to the first possible implementation, the service type #1 is carried in the service requirements request. Before the UDM determines N service requirements according to the sensing area #1 indicated by the service requirements request and the first mapping relationship, the method 600 further includes: the UDM determines at least one sensing area according to the service type #1; and determines the sensing area #1 from the at least one sensing area.

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

[0256] The 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.

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

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

[0259] Regarding the description of the UDM determining N service requirements according to the sensing area #1 and the first mapping relationship, reference may be made to the relevant description in the second possible implementation, which will not be elaborated here.

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

[0261] It can be understood that when the NEF receives the correspondence between the N service requirements and the N intervals of the number of terminals from the UDM, the NEF can also carry the correspondence between the N service requirements and the N intervals of the number of terminals in the sent sensing request #1. At this time, the SF can obtain the target service requirement from the N service requirements according to the received 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 #1.

[0262] Among them, the number of terminals included in the sensing area #1 can be obtained from the AMF. The number of terminals included in the sensing area #1 can also be sent by the UDM to the SF through the NEF. Exemplarily, when the UDM determines to authorize the sensing request, the UDM obtains the number of terminals included in the sensing area #1 and sends it to the NEF, and the NEF includes the number of terminals included in the sensing area #1 in the sensing request and sends it to the SF.

[0263] Similar to the first possible implementation, the service type #1 is also carried in the sensing authorization request. Before the UDM determines the N service requirements according to the sensing area #1 and the first mapping relationship from the NEF, the method 600 further includes: the UDM determines at least one sensing area according to the service type #1; and determines the sensing area #1 from the at least one sensing area.

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

[0265] It should be noted that the process of the UDM determining the N service requirements according to the sensing area #1 and the first mapping relationship from the NEF can be executed when the UDM determines to authorize the sensing request. At this time, the N service requirements sent by the UDM can be carried in the authorization message.

[0266] For the above first to third possible implementations, when N = 1, the N service requirements are the target service requirement.

[0267] Optionally, before the SF obtains 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, the method 600 further includes: the SF sends an acquisition request to the AMF, where the acquisition request is used to request to obtain the number of terminals included in the sensing area; the AMF receives the acquisition request and sends an acquisition response to the SF, where the acquisition response indicates the number of terminals included in the sensing area; the SF receives the acquisition response and determines the number of terminals included in the sensing area according to the acquisition response.

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

[0269] It can be understood that the above AMF is determined by the SF according to the sensing area #1.

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

[0271] It should be noted that when the SF determines to allow sensing of the sensing area #1, the SF can continue to execute S602.

[0272] Example 1, when at least one of the following conditions is satisfied, the SF determines to allow sensing of the sensing area #1; or, when all of the following conditions are not satisfied, the SF determines to allow sensing of the sensing area #1: the sensing area #1 belongs to a predefined area range, the service type #1 belongs to a predefined service type that allows triggering, the sensing accuracy corresponding to the service requirement #1 belongs to a predefined sensing accuracy range, the time of the sensing request belongs to a predefined time interval, or the AF identified by the identifier of the AF belongs to a predefined AF that allows triggering.

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

[0274] It can be understood that the indication of the above sensing area #1, service type #1, service requirement #1, and the identifier of the AF can be carried in the sensing request #1 and sent to the SF. Among them, the sensing accuracy corresponding to the service requirement #1 belongs to a predefined sensing accuracy range. For example, it can be that any one or more parameters included in the KPI determined according to the service requirement #1 belong to any one or more predefined sensing accuracy ranges.

[0275] Exemplarily, when carrying these four types of parameters in the sensing request #1, when the SF determines to allow sensing of the sensing area #1, if there is a parameter that can meet the corresponding conditions above, the SF can determine to allow sensing of the sensing area. It should be noted that this application does not care whether other parameters except those that meet the above conditions meet the above conditions.

[0276] The above-mentioned 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 important people or a motorcade pass by.

[0277] The above-mentioned predefined service types allowed to be triggered can be described by the service ID. For example, the predefined service types allowed to be triggered may be to sense the time when users in a residential area go out or return home, etc.

[0278] The above-mentioned predefined sensing accuracy range can be divided by an accuracy value. For example, if it is greater than accuracy 1, sensing of the sensing area #1 is allowed; if it is less than or equal to accuracy 1, sensing of the sensing area #1 is not allowed.

[0279] The above-mentioned predefined time interval can be, for example, the peak hour of the flow of people. Here, it should be noted that: if it is for detecting the peak period of a highway, it can be triggered separately in the time dimension, that is, as long as the time information of the sensing request belongs to the predefined time interval, it can be triggered; if it is for detecting the peak period of a traffic intersection, it may also need to be triggered in combination with other conditions.

[0280] The above-mentioned predefined AFs allowed to be triggered can be, for example, AF 1 and AF 2, and the predefined AFs not allowed to be triggered can be, for example, public safety AF, or authority / regulatory agency AF.

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

[0282] For the description of the above at least one condition, reference can be made to the relevant description above, and details are not repeated here.

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

[0284] The SF may carry the target service requirements in the service requirement confirmation request. The service requirement request is used to indicate to the AF that the sensing process will be performed using service requirements different from the service requirements #1, and is used to request the AF to confirm whether the target service requirements can or cannot be adopted for sensing.

[0285] Exemplarily, in the case where the service requirement confirmation reply indicates agreement to adopt the target service requirements, the SF initiates a sensing process based on the target service requirements; or, in the case where the service requirement confirmation reply indicates disagreement to adopt the target service requirements, the SF determines that sensing is not agreed to be performed.

[0286] Optionally, in the case where it is determined that sensing is not agreed to be performed, the SF sends a rejection message to the AF, and the rejection message is used to reject the sensing request #1.

[0287] Optionally, in the case where it is determined that sensing is agreed to be performed and the target service requirements are the KPIs for sensing, the SF may initiate a sensing process based on the target service requirements; or, in the case where it is determined that sensing is agreed to be performed and the target service requirements are not the KPIs for sensing, the SF may determine the KPIs for sensing according to the target service requirements and initiate a sensing process according to the KPIs.

[0288] Among them, the target service requirements may be KPIs, or include KPIs, or may also include information for determining KPIs, such as identifiers or parameters corresponding to the KPIs, and so on. The KPIs are used to describe how precisely the sensing data needs to be obtained. Exemplarily, the KPIs may include one or more of the following indicators: confidence interval, sensing positioning accuracy (including vertical and horizontal), sensing speed accuracy (including vertical and horizontal), sensing resolution (including area and speed), maximum sensing service delay or refresh rate. These indicators are only an example of the KPIs, and the present application does not limit the specific indicators included in the KPIs.

[0289] If the target service requirements are KPIs or include KPIs, the SF may directly obtain the KPIs for sensing the terminal based on the target service requirements, and then initiate a sensing process for the terminal.

[0290] If the target service requirement includes information for determining the KPI, the SF can convert the target service requirement into a KPI. In other words, one possible way for the SF to determine the KPI for terminal perception based on the target service requirement is to determine the target service requirement as the KPI for terminal perception, and another possible way is to convert the target service requirement into the KPI for terminal perception.

[0291] In one possible implementation, the target service requirement may include an identifier corresponding to the KPI. The SF can convert the target service requirement into a KPI for terminal perception according to the identifier in the target service requirement. One possible implementation is that the SF pre-stores the correspondence between at least one identifier and at least one KPI, and each KPI may include one or more metrics. The SF can find the KPI corresponding to the identifier from the pre-stored correspondence according to the identifier included in the target service requirement.

[0292] In another possible implementation, the target service requirement may also include parameters corresponding to the KPI. The SF can convert the target service requirement into a KPI for terminal perception according to the parameters in the target service requirement. One possible implementation is that the SF pre-stores the 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 metrics. The SF can find the KPI corresponding to the set of parameters from the pre-stored correspondence according to the set of parameters included in the target service requirement.

[0293] It can be converted according to the predefined correspondence between the service requirement and the KPI. For example, the target service requirement is a specific identifier, and the SF has a predefined KPI corresponding to the specific identifier. It can also be that the parameters in the perception requirement are translated into the parameters of the KPI. For example, the parameters in the perception requirement correspond one-to-one with the parameters of the KPI, and the SF determines the parameters in the perception requirement as the corresponding KPI parameters respectively. The perception requirement can also be equivalent to the KPI, that is, no translation by the SF is required.

[0294] It can be understood that the SF can initiate the perception process using any one of the six perception modes shown in Table 1 above.

[0295] Exemplarily, the SF initiates the perception process, including: the SF selects a perception mode, selects specific perception nodes (transmitter and receiver), and instructs the perception nodes to send and receive perception signals using the perception KPI determined by the target service requirement, and obtains perception data to determine the perception result.

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

[0297] 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 sensing process based on the target service requirement.

[0298] It can be understood that the fact that the above-mentioned target service requirement is different from service requirement #1 means that the level of the target service requirement is different from the level of service requirement #1. For example, the level of the target service requirement is lower than the level of service requirement #1; or, for another example, the level of the target service requirement is higher than the level of service requirement #1.

[0299] Example 1: When the level of the target service requirement is lower than the level of service requirement #1, this service requirement confirmation request can be understood as a request for the AF to confirm whether the service requirement for performing sensing can or cannot be downgraded, and 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, the method 600 further includes: the SF determines whether there is a downgrade of the target service requirement compared to service requirement #1.

[0300] Among them, the fact that there is a downgrade of the target service requirement compared to service requirement #1 means that the level of the target service requirement is lower than the level of service requirement #1.

[0301] For example, if the target service requirement obtained by the SF is the lowest service requirement and service requirement #1 is the medium service requirement, then it can be considered that there is a downgrade of the target service requirement compared to service requirement #1.

[0302] It should be noted that the level of the service requirement can be determined according to the values of each index in the KPI determined by it. The following shows several examples where the level of the target service requirement is lower than the level of service requirement #1: For example, in the indicators corresponding to the target service requirement, the sensing position accuracy is 1m, and in the indicators corresponding to service requirement #1, the sensing position accuracy is 1mm. Since the accuracy of 1mm is higher than the accuracy of 1m, it can be considered that the level of this target service requirement is lower than the level of service requirement #1. For another example, in the indicators corresponding to the target service requirement, the sensing resolution is 5m, and in the indicators corresponding to service requirement #1, the sensing resolution is 1m. Since the sensing resolution of 1m is higher than the sensing resolution of 5m, it can be considered that the level of this target service requirement is lower than the level of service requirement #1. For another example, in the indicators corresponding to the target service requirement, the maximum sensing service delay is 0.5ms, and in the indicators corresponding to service requirement #1, the maximum sensing service delay is 0.2ms. Since the delay of 0.2ms is shorter than the delay of 0.5ms, it can be considered that the level of the target service requirement is lower than the level of service requirement #1.

[0303] Example 2: The level of the target service requirement is higher than that of Service Requirement #1. In this case, the service requirement confirmation request can be understood as a request for the AF to confirm whether the service requirement for execution awareness can or cannot be upgraded. This service requirement confirmation request can also be referred to as an upgrade confirmation request. Specifically, before the SF sends a service requirement confirmation request to the AF, the method 600 further includes: The SF determines whether there is an upgrade of the target service requirement compared to Service Requirement #1.

[0304] Among them, that there is an upgrade of the target service requirement compared to Service Requirement #1 means that the level of the target service requirement is higher than that of Service Requirement #1.

[0305] For example, if the target service requirement obtained by the SF is a medium service requirement and Service Requirement #1 is the lowest service requirement, then it can be considered that there is an upgrade of the target service requirement compared to Service Requirement #1.

[0306] The following shows several examples where the level of the target service requirement is higher than that of Service Requirement #1: For example, among the indicators corresponding to the target service requirement, the perception position accuracy is 1 mm, and among the indicators corresponding to Service Requirement #1, the perception position accuracy is 1 m. Since the accuracy of 1 mm is higher than that of 1 m, it can be considered that the level of this target service requirement is higher than that of Service Requirement #1. Another example, among the indicators corresponding to the target service requirement, the perception resolution is 1 m, and among the indicators corresponding to Service Requirement #1, the perception resolution is 5 m. Since the perception resolution of 1 m is higher than that of 5 m, it can be considered that the level of this target service requirement is higher than that of Service Requirement #1. Another example, among the indicators corresponding to the target service requirement, the maximum perception service delay is 0.2 ms, and among the indicators corresponding to Service Requirement #1, the maximum perception service delay is 0.5 ms. Since the delay of 0.2 ms is shorter than that of 0.5 ms, it can be considered that the level of the target service requirement is higher than that of Service Requirement #1.

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

[0308] Of course, when the target service requirement is different from Service Requirement #1, the SF may initiate a sensing process for the terminal based on the target service requirement without confirming with the AF whether it agrees to adopt the target service requirement. For example, when the level of the target service requirement is higher than that of Service Requirement #1, the SF may initiate a sensing process for the terminal based on the target service requirement without confirming with the AF whether it agrees to adopt the target service requirement. In this case, the SF does not need to determine whether the target service requirement is the same as that of Service Requirement #1. In other words, it is an optional step for the SF to send a service requirement confirmation request to the AF, and it is not necessarily executed.

[0309] Optionally, before S601, the method 600 further includes: the AF sends a parameter configuration request to the NEF, where the parameter configuration request includes the correspondence between at least one sensing 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 the UDM, where the parameter configuration request includes the correspondence between at least one sensing area and at least one service requirement; the SF or the UDM determines a first mapping relationship according to the parameter configuration request.

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

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

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

[0313] The following will be based on Figure 6 the embodiments shown and will separately combine Figures 7 to 9 to introduce the communication method provided by the embodiments of the present application in more detail. It should be noted that Figures 7 to 9 in the embodiments shown, the steps that are the same or similar to those Figure 6 in the embodiments shown can refer to the relevant descriptions in combination with the method 600 above and will not be repeated.

[0314] Taking the UDM pre-storing the first mapping relationship as an example, the method provided by the embodiments of the present application will be described in detail in combination with Figure 7 and Figure 8 below.

[0315] Figure 7 is another schematic flowchart of the communication method provided by the embodiments of the present application. As Figure 7 shown, the method 700 may include S701 to S716. Each step in the method 700 will be described below.

[0316] In S701, the AF sends a first sensing request to the NEF. The first sensing request includes the identifier of the AF, service type #1, service requirement #1, and external sensing area information. Correspondingly, the NEF receives the first sensing request from the AF.

[0317] Among them, the external area information can be understood as the above-mentioned sensing area #2, and the first sensing request can be understood as the sensing request #2 in the previous text.

[0318] In S702, the NEF converts the external sensing area information into internal sensing area information.

[0319] The internal sensing area information refers to the area information used by the operator network and can be understood as the sensing area #1 in the previous text.

[0320] In S703, the NEF sends a sensing authorization request to the UDM. Correspondingly, the UDM receives the sensing authorization request from the NEF.

[0321] For the description of the sensing authorization request, refer to the relevant description of the sensing authorization request in the previous text, which will not be elaborated here.

[0322] In S704, the UDM determines whether to authorize or not to authorize the sensing request.

[0323] Exemplarily, the UDM can determine whether to authorize the sensing request from the AF according to the identifier of the AF; in another possible case, the UDM can further determine whether the service requirement carried in the sensing request from the AF meets the service requirement included in the corresponding relationship pre-stored in the UDM; in the case of meeting, determine to authorize; or, in the case of not meeting, determine not to authorize.

[0324] In the case of determining not to authorize, a rejection authorization message is sent to the NEF, and the rejection authorization message is used to reject the authorization of the sensing request.

[0325] In the case of authorization passing, continue to execute some steps in S705 to S716.

[0326] In S705, the UDM sends an authorization message to the NEF. Correspondingly, the NEF receives the authorization message from the UDM.

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

[0328] The second sensing request can be understood as the sensing request #1 in the previous text.

[0329] S707, the SF determines whether to allow sensing of the sensing area according to the second sensing request.

[0330] In the case of determining to allow sensing of the sensing area #1, continue to execute some steps in S708 to S716; otherwise, reject the second sensing request. The description of determining to allow sensing of the sensing area #1 can refer to the relevant description above.

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

[0332] The acquisition request includes internal area information.

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

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

[0335] S710, the UDM sends N service requirements to the SF. Correspondingly, the SF receives the N service requirements from the UDM.

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

[0337] S711, the SF obtains the target service requirement from the N service requirements.

[0338] This process can refer to the process of obtaining the target service requirement in the second possible implementation of the method 600 above, and will not be elaborated here.

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

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

[0341] If they are different, continue to execute some steps in S713 to S716.

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

[0343] S714, the AF sends a service requirement confirmation reply to the SF. Correspondingly, the SF receives the service requirement confirmation reply from the AF.

[0344] If the confirmation response indicates agreement to adopt the target service requirements, then S715 is continued, and the SF initiates a sensing process based on the target service requirements.

[0345] If the confirmation response indicates disagreement to adopt the target service requirements, then S716 is continued, and the SF sends a rejection message to the AF, and this rejection message is used to reject the sensing request #2. Correspondingly, the AF receives the rejection message from this SF.

[0346] For the descriptions of the service requirement confirmation request and the service requirement confirmation response, reference can be made to the relevant descriptions above.

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

[0348] Figure 8 It is another schematic flowchart of the communication method provided in the embodiments of the present application. As Figure 8 shown, the method 800 may include S801 to S814. Each step in the method 800 is described below.

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

[0350] Among them, the first sensing request can be understood as the sensing request #2 above.

[0351] S802, the NEF converts the external sensing area information into internal sensing area information.

[0352] This internal sensing area information refers to the area information used by the operator network.

[0353] Among them, the internal sensing area information can be understood as the sensing area #1 above, and the external area information can be understood as the sensing area #2 above.

[0354] S803, the NEF sends a sensing authorization request to the UDM. Correspondingly, the UDM receives the sensing authorization request from this NEF.

[0355] S804, the UDM determines whether to authorize or not to authorize this sensing request.

[0356] For the descriptions of S801 to S804, reference can be made to the descriptions of S701 to S704 above, which will not be elaborated here.

[0357] In the case of determining non-authorization, a rejection authorization message is sent to the NEF, and this rejection authorization message is used to reject the authorization for the sensing request.

[0358] In the case of successful authorization, some steps in S805 to S815 are continued to be executed.

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

[0360] This process can refer to S709 in method 700, which will not be elaborated here.

[0361] S806, the UDM sends an authorization message to the NEF, and N service requirements are carried in this authorization message. Correspondingly, the NEF receives the authorization message from this UDM.

[0362] Optionally, when N is greater than 1, the corresponding relationship between the N service requirements and N intervals of the number of terminals is also carried in this authorization message.

[0363] S807, the NEF sends a second sensing request to the SF, and N service requirements are carried in this second sensing request. Correspondingly, the SF receives the second sensing request from this NEF.

[0364] Optionally, when the corresponding relationship between the N service requirements and N intervals of the number of terminals is also carried in the authorization message, the corresponding relationship between the N service requirements and N intervals of the number of terminals is also carried in this second sensing request.

[0365] S808, the SF determines whether to allow sensing of the sensing area according to the second sensing request.

[0366] In the case of determining to allow sensing of the sensing area #1, some steps in S809 to S815 are continued to be executed; otherwise, this second sensing request is rejected. Among them, the description of determining to allow sensing of the sensing area #1 can refer to the relevant description above.

[0367] S809, the SF obtains the target service requirement from the N service requirements.

[0368] This process can refer to the process of obtaining the target service requirement in the third possible implementation of method 600 above, which will not be elaborated here.

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

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

[0371] If they are different, continue to execute some steps in S811 to S814.

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

[0373] S812, the AF sends a service requirement confirmation reply to the SF. Correspondingly, the SF receives the service requirement confirmation reply from this AF.

[0374] If the confirmation reply indicates agreement to adopt the target service requirement, then continue to execute S813, and the SF initiates a sensing process based on the target service requirement.

[0375] If the confirmation reply indicates disagreement to adopt the target service requirement, then continue to execute S814, and the SF sends a rejection message to the AF, and this rejection message is used to reject the sensing request #2. Correspondingly, the AF receives the rejection message from this SF.

[0376] For the descriptions of the service requirement confirmation request and the service requirement confirmation reply, reference can be made to the relevant descriptions above.

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

[0378] Next, taking the SF pre-storing the first mapping relationship as an example, in combination with Figure 9 Describe in detail the method provided in the embodiments of the present application.

[0379] Figure 9 is another schematic flowchart of the communication method provided in the embodiments of the present application. As Figure 9 shown, the method 900 may include S901 to S914. The following describes each step in the method 900.

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

[0381] S902, the NEF converts the external sensing area information into internal sensing area information.

[0382] In S903, the NEF sends a sensing authorization request to the UDM. Correspondingly, the UDM receives the sensing authorization request from the NEF.

[0383] In S904, the UDM determines whether to authorize or not to authorize the sensing request.

[0384] In the case of determining not to authorize, a rejection authorization message is sent to the NEF, and the rejection authorization message is used to reject the authorization of the sensing request.

[0385] In the case of successful authorization, some steps in S905 to S914 are continued to be executed.

[0386] In S905, the UDM sends an authorization message to the NEF. Correspondingly, the NEF receives the authorization message from the UDM.

[0387] In S906, the NEF sends a second sensing request to the SF. Correspondingly, the SF receives the second sensing request from the NEF.

[0388] In S907, the SF determines whether to allow sensing of the sensing area according to the second sensing request.

[0389] For the descriptions of S901 to S907, reference can be made to the relevant descriptions of S701 to S707 above, and will not be elaborated here.

[0390] In the case of determining to allow sensing of the sensing area #1, some steps in S908 to S914 are continued to be executed; otherwise, the second sensing request is rejected. Among them, for the description of determining to allow sensing of the sensing area #1, reference can be made to the relevant descriptions above. In S908, the SF determines N service requirements according to the first mapping relationship and the internal area information.

[0391] This process can refer to the process above about the SF determining N service requirements according to the first mapping relationship and the sensing area #1, and will not be elaborated here.

[0392] In S909, the SF obtains the target service requirement from the N service requirements.

[0393] This process can refer to the process of obtaining the target service requirement in the first possible implementation of the method 600 above, and will not be elaborated here.

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

[0395] If they are the same, S913 is directly executed.

[0396] If they are different, some steps in S911 to S914 are continued to be executed.

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

[0398] S912, the AF sends a service requirement confirmation reply to the SF. Correspondingly, the SF receives the service requirement confirmation reply from the AF.

[0399] If the confirmation reply indicates agreement to adopt the target service requirement, then S913 is continued, and the SF initiates a sensing process based on the target service requirement.

[0400] If the confirmation reply indicates disagreement to adopt the target service requirement, then S914 is continued, and the SF sends a rejection message to the AF, and the rejection message is used to reject the sensing request #2. Correspondingly, the AF receives the rejection message from the SF.

[0401] For the descriptions of the service requirement confirmation request and the service requirement confirmation reply, reference can be made to the relevant descriptions above.

[0402] In the embodiments of the present application, after receiving a sensing request for requesting sensing of a sensing area, the SF can obtain the target service requirement corresponding to the sensing area according to the sensing area and the first mapping relationship. Therefore, the method provided by the embodiments of the present application can flexibly respond to the sensing request according to the sensing area to meet the restrictions of different sensing areas on service requirements, and solves the problem that all service requirements are the same when sensing the same service requirement for different sensing areas.

[0403] As described above in combination with Figures 6 to 9 the method provided by the embodiments of the present application is described in detail. Below in combination with Figure 10 and Figure 11 the apparatus provided by the embodiments of the present application is described in detail.

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

[0405] Figure 10 is a schematic block diagram of a communication apparatus provided by the embodiments of the present application. As Figure 10 shown, the apparatus 1000 includes a transceiver module 1010 and a processing module 1020.

[0406] A possible design is that the apparatus 1000 is used to implement the function of the SF in the method embodiment shown above Figures 6 to 9 therein.

[0407] Exemplarily, the transceiver module 1010 is used to: receive a sensing request; the processing module 1020 is used to: obtain the target service requirement.

[0408] Optionally, the transceiver module 1010 is further 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 further used to: obtain the target service requirement from the N service requirements.

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

[0410] Optionally, the N service requirements are carried in the sensing request, and the processing module 1020 is further used to: obtain the target service requirement from the N service requirements.

[0411] Optionally, the processing module 1020 is further used to: when N>1, obtain 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.

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

[0413] Optionally, the processing module 1020 is further used to: when N>1, obtain 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.

[0414] Optionally, the processing module 1020 is further used to: determine that sensing of the sensing area is allowed.

[0415] Optionally, the processing module 1020 is further used to: determine that sensing of the sensing area is allowed when at least one of the following conditions is met: 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.

[0416] Optionally, the processing module 1020 is further configured to: obtain the target service requirement when at least one of the following conditions is met: 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 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 allowed to be triggered.

[0417] Optionally, the transceiver module 1010 is further configured 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 further configured to: initiate a sensing process based on the target service requirement when the service requirement confirmation reply indicates agreement to adopt the target service requirement; or determine not to perform sensing when the service requirement confirmation reply indicates disagreement to adopt the target service requirement.

[0418] Optionally, the transceiver module 1010 is further configured to: send a rejection message to the application function network element when it is determined not to perform sensing, and the rejection message is used to reject the sensing request.

[0419] For a more detailed description of the above transceiver module 1010 and processing module 1020, reference can be directly made to the relevant descriptions in the embodiments shown in Figures 6 to 9 which will not be elaborated here.

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

[0421] Exemplarily, the transceiver module 1010 is configured to: receive a service requirement request from a sensing function network element; the processing module 1020 is configured to: determine N service requirements according to the sensing area and the mapping relationship; the transceiver module 1010 is further configured to: send the N service requirements to the sensing function network element.

[0422] Optionally, the processing module 1020 is further configured to: determine at least one service requirement according to the sensing area and the mapping relationship; and determine the N service requirements from the at least one service requirement according to the corresponding relationship between the at least one service requirement and at least one time period, and the time information of the service requirement request.

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

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

[0425] Exemplarily, the transceiver module 1010 is configured to: receive a sensing authorization request from a network capability open function network element; the processing module 1020 is configured to: when 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; the transceiver module 1010 is further configured to: send the N service requirements to the network capability open function network element.

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

[0427] Optionally, the processing module 1020 is further configured to: determine whether to authorize or not authorize the sensing request according to the identifier of the application function network element.

[0428] Optionally, the processing module 1020 is further configured to: when determining to authorize the sensing request according to 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 sensing area included in the mapping relationship; and determine not to authorize the sensing request.

[0429] For a more detailed description of the above transceiver module 1010 and processing module 1020, reference can be directly made to the relevant descriptions in method 600 and Figures 7 to 9 the relevant descriptions in the embodiments shown in

[0430] It should be noted that the device 1000 may include a sending module but not a receiving module. Or, the device 1000 may include a receiving module but not a sending module. Specifically, it depends on whether the above solution executed by the device 1000 includes a sending action and a receiving action. It can be understood that since the device 1000 has a communication function, it can also be called a communication device.

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

[0432] Optionally, the communication device 1100 may further include at least one memory 1120, which is used to store instructions executed by the processor 1110, or input data required for the processor 1110 to run the instructions, or data generated after the processor 1110 runs the instructions. The at least one processor 1110 and the at least one memory 1120 may be separately arranged. For example, each memory may be connected to one or more processors, so that the connected processors can read information from the memory, 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 in one processor.

[0433] 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 can be understood that the interface circuit 1130 may be a transceiver, an input / output circuit, a bus, a module, a pin, or other types of interface circuits. Among them, the input circuit in the input / output circuit can be used for receiving, and the output interface can be used for sending.

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

[0435] When the communication device 1100 is used for the method shown in the above embodiments, the at least one processor 1110 is used to execute the functions of the above processing unit, and the interface circuit 1130 is used to execute the functions of the above receiving unit and / or sending unit. Whether the interface circuit 1130 is used for sending or receiving specifically depends on whether the communication device 1100 executes a sending action or a receiving action in the solution it executes.

[0436] It can be understood that when the communication device 1100 is a communication device (such as an SF, a UDM, or an AF), the interface circuit 1130 may be a transceiver, specifically including a transmitter and a receiver. The transmitter is used to send signals, and the receiver is used to receive signals. When the communication device 1100 is a chip applied to a communication device, the interface circuit 1130 may be an input / output circuit, a bus, a module, a pin, or other types of interface circuits. Among them, the input circuit in the input / output circuit can be used for receiving, and the output interface can be used for sending.

[0437] It should be understood that Figure 11 In the shown communication device 1100, 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.

[0438] 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 interaction 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 the embodiments of the present application Figure 11 is connected by a bus 1150 between the processor 1110, the memory 1120, the interface circuit 1130 and the power supply circuit 1140. The bus 1150 is Figure 11 shown in thick lines, and the connection manners between other components are only for illustrative purposes and are not to be taken as limiting. 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 the convenience of representation, Figure 11 only one thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

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

[0440] The above-mentioned processor can 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 devices, discrete gate or transistor logic devices, discrete hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0441] The steps of the method disclosed in the embodiments of the present application can be directly embodied as being 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 mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0442] The memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus 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.

[0443] The method provided in the foregoing embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may 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 processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. 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 wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more integrated available media. The available medium may be a magnetic medium (such as a floppy disk, hard disk, magnetic disk), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc.

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

[0445] An embodiment of the present application further provides a computer program product, which includes: a computer program (which may also be referred to as code or instructions). When the computer program is run, it causes the computer to execute the method executed by the SF network element in any one of the embodiments shown in Figures 6 to 9 or causes the computer to execute the method executed by the UDM network element in any one of the embodiments shown in Figures 7 to 9

[0446] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program (which may also be referred to as code or instructions). When the computer program is run, it causes the computer to execute the method executed by the SF network element in any one of the embodiments shown in Figures 6 to 9 or causes the computer to execute the method executed by the UDM network element in any one of the embodiments shown in Figures 7 to 9

[0447] An embodiment of the present application further provides a chip system, which includes at least one processor for executing the method executed by the SF network element in any one of the embodiments shown in Figures 6 to 9 or for implementing the method executed by the UDM network element in any one of the embodiments shown in Figures 7 to 9 ​​The method executed by the UDM network element in any of the illustrated embodiments.

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

[0449] Optionally, the chip system further includes an interface circuit and / or a power supply circuit. The interface circuit is used for data transmission, and the power supply circuit is used to power the chip system. Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0450] Those skilled in the art can 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 foregoing method embodiments and will not be elaborated herein.

[0451] In 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 illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, 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 displayed or discussed mutual coupling, direct coupling, or communication connection can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical, or other forms.

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

[0453] In addition, the functional units in each embodiment of this application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0454] When the above-mentioned 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 this application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The foregoing storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories, random access memories, magnetic disks, or optical discs.

[0455] As described above, the above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed in this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

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

2. The method according to claim 1, characterized in that 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, characterized in that, 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, wherein 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 a correspondence between the N service requirements and N time periods, and 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 a 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, wherein 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 sensed area belongs to a predefined area range, the service type belongs to a predefined service type that allows triggering, the sensed KPI corresponding to the requested service requirement belongs to a predefined sensed 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 sensed area; Determine N service requirements according to the sensed area and the mapping relationship, where the mapping relationship indicates the corresponding relationship between at least one sensed 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, characterized in that, 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 sensed area and the mapping relationship includes: Determine P service requirements according to the sensed 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, characterized in that, 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 sensed 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 sensed area; In the case of determining to authorize the sensing request, determine N service requirements according to the sensed area and the mapping relationship, where the mapping relationship indicates the corresponding relationship between at least one sensed 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, characterized in that, The requested service requirement is further 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 requested service requirement does not meet the service requirement corresponding to the sensing area included in the mapping relationship; Determine to reject authorizing the sensing request.

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

22. A communication device, characterized in that, It includes a processor, and the processor is used to execute program code so that the communication device implements the method described in any one of claims 1 to 11, or implements the method described in any one of claims 12 to 16, or implements the method described in 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 the processor, the method described in any one of claims 1 to 11 is executed, or the method described in any one of claims 12 to 16 is executed, or the method described in any one of claims 17 to 21 is executed.

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

Images