Sensing service authorization method and apparatus, configuration information receiving method and apparatus, and device

By providing a sensing service authorization method in 3GPP mobile networks and using authorization information to determine the provision method of sensing services, the problem of unclear network authorization sensing requests is solved, and the management efficiency of sensing services is improved.

WO2026233414A1PCT designated stage Publication Date: 2026-11-12VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/095469
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-08
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In 3GPP mobile networks, there is no consensus on how the network should authorize sensing requests, resulting in a lack of clear management mechanisms during the execution of sensing services.

Method used

A method for authorizing sensing services is provided, which determines whether to provide sensing services for application functions (AF) based on a request message and authorization information. The authorization information includes AF access, sensing service, reporting type, sensing time, sensing location, user consent, and interoperability information.

Benefits of technology

The authorization method for sensing services on the network side has been clarified, which improves the efficiency and accuracy of managing processes related to sensing services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026095469_12112026_PF_FP_ABST
    Figure CN2026095469_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of communications, and discloses a sensing service authorization method and apparatus, a configuration information receiving method and apparatus, and a device. The sensing service authorization method in embodiments of the present application comprises: a first device receives a first request message, the first request message comprising an identifier of an AF and sensing service information, and the sensing service information being used for indicating a requested sensing service; and on the basis of the first request message and authorization information, the first device determines whether to provide the requested sensing service for the AF, wherein the authorization information comprises at least one of the following: AF access authorization information, sensing service authorization information, reporting type authorization information, sensing time authorization information, sensing location authorization information, user consent information, and first interoperation information.
Need to check novelty before this filing date? Find Prior Art

Description

Sensing service authorization method, configuration information receiving method, device and equipment

[0001] Cross-referencing

[0002] This disclosure claims priority to Chinese Patent Application No. 202510591506.2, filed on May 8, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a sensing service authorization method, a configuration information receiving method, an apparatus, and a device. Background Technology

[0004] Integrated Sensing and Communication (ISAC) technology (also known as sensing services) has a wide range of applications, including target recognition (vehicle, person, animal, etc.), target tracking, environmental monitoring, action recognition, gesture recognition, and facial recognition. Currently, there is discussion about integrating sensing technology into 3GPP mobile networks to implement sensing services within them. In the execution of sensing services, the server first triggers a sensing request; however, how the network authorizes these requests is still undecided. Summary of the Invention

[0005] This application provides a method for authorizing sensing services, a method for receiving configuration information, an apparatus, and a device, which can solve the problem that it is not clear how the network authorizes sensing requests in related technologies.

[0006] In a first aspect, a method for authorizing sensing services is provided, the method being executed by a first device, the method comprising:

[0007] The first device receives a first request message, which includes an identifier of the application function AF and sensing service information, wherein the sensing service information is used to indicate the requested sensing service.

[0008] The first device determines whether to provide the requested sensing service to the AF based on the first request message and the authorization information; wherein the authorization information includes at least one of the following:

[0009] AF access authorization information, which indicates whether AF access is permitted;

[0010] Perception service authorization information, which is used to indicate whether the requested perception service is allowed to be provided to the AF;

[0011] Report type authorization information, which is used to indicate whether the perception result or perception data of the requested perception service is allowed to be provided to the AF;

[0012] Sensing time authorization information, which is used to indicate the time period during which the sensing service requested is allowed to be executed or the time period during which the sensing service requested is not allowed to be executed;

[0013] The location authorization information is used to indicate the location where the requested sensing service is allowed to be executed or the location where the requested sensing service is not allowed to be executed.

[0014] User consent information, which is used to indicate whether the sensing target agrees to have its data collected used for sensing purposes;

[0015] First interoperability information, which indicates that the sensing function SF allows interoperability with the AF.

[0016] Secondly, a configuration information receiving method is provided, which is executed by a sensing entity, the method comprising:

[0017] The sensing entity receives first configuration information sent by the first device, the first configuration information being used to indicate at least one of the following:

[0018] The final determined perception service information is used to indicate the perception services that the AF does not allow and / or the perception services that the AF allows.

[0019] The final determined perception reporting type, which is used to indicate perception reporting types that the AF does not allow and / or perception reporting types that the AF allows;

[0020] The final determined perception time authorization information is used to indicate the time period during which perception services that do not allow AF requests are performed and / or the time period during which perception services that allow the requests are performed.

[0021] The final determined sensing location authorization information is used to indicate the location of the sensing service that does not allow the AF request and / or the location of the sensing service that allows the request.

[0022] The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to the collection of data for perception purposes, and the second perception target is used to indicate disagreement to the collection of data for perception purposes.

[0023] Thirdly, a sensing service authorization device is provided, comprising:

[0024] The first receiving module is configured to receive a first request message, the first request message including the identifier of AF and sensing service information, the sensing service information being used to indicate the requested sensing service;

[0025] The determining module is configured to determine, based on the first request message and authorization information, whether to provide the requested perception service to the AF; wherein the authorization information includes at least one of the following:

[0026] AF access authorization information, which indicates whether AF access is permitted;

[0027] Perception service authorization information, which is used to indicate whether the requested perception service is allowed to be provided to the AF;

[0028] Report type authorization information, which is used to indicate whether the perception result or perception data of the requested perception service is allowed to be provided to the AF;

[0029] Sensing time authorization information, which is used to indicate the time period during which the sensing service requested is allowed to be executed or the time period during which the sensing service requested is not allowed to be executed;

[0030] The location authorization information is used to indicate the location where the requested sensing service is allowed to be executed or the location where the requested sensing service is not allowed to be executed.

[0031] User consent information, which is used to indicate whether the sensing target agrees to have its data collected used for sensing purposes;

[0032] First interoperability information, which indicates that the sensing function SF allows interoperability with the AF.

[0033] Fourthly, a configuration information receiving device is provided, comprising:

[0034] The second receiving module is configured to receive first configuration information sent by the first device, wherein the first configuration information is used to indicate at least one of the following:

[0035] The final determined perception service information is used to indicate the perception services that the AF does not allow and / or the perception services that the AF allows.

[0036] The final determined perception reporting type, which is used to indicate perception reporting types that the AF does not allow and / or perception reporting types that the AF allows;

[0037] The final determined perception time authorization information is used to indicate the time period during which perception services that do not allow AF requests are performed and / or the time period during which perception services that allow the requests are performed.

[0038] The final determined sensing location authorization information is used to indicate the location of the sensing service that does not allow the AF request and / or the location of the sensing service that allows the request.

[0039] The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to the collection of data for perception purposes, and the second perception target is used to indicate disagreement to the collection of data for perception purposes.

[0040] Fifthly, a communication device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0041] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0042] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to receive first configuration information sent by a first device, the first configuration information indicating at least one of the following:

[0043] The final determined perception service information is used to indicate the perception services that the AF does not allow and / or the perception services that the AF allows.

[0044] The final determined perception reporting type, which is used to indicate perception reporting types that the AF does not allow and / or perception reporting types that the AF allows;

[0045] The final determined perception time authorization information is used to indicate the time period during which perception services that do not allow AF requests are performed and / or the time period during which perception services that allow the requests are performed.

[0046] The final determined sensing location authorization information is used to indicate the location of the sensing service that does not allow the AF request and / or the location of the sensing service that allows the request.

[0047] The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to the collection of data for perception purposes, and the second perception target is used to indicate disagreement to the collection of data for perception purposes.

[0048] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0049] A ninth aspect provides a network-side device, including a processor and a communication interface, wherein the communication interface is configured to receive a first request message, the first request message including an identifier of an AF and sensing service information, the sensing service information being used to indicate a requested sensing service; the processor is configured to determine, based on the first request message and authorization information, whether to provide the requested sensing service to the AF; wherein the authorization information includes at least one of the following:

[0050] AF access authorization information, which indicates whether AF access is permitted;

[0051] Perception service authorization information, which is used to indicate whether the requested perception service is allowed to be provided to the AF;

[0052] Report type authorization information, which is used to indicate whether the perception result or perception data of the requested perception service is allowed to be provided to the AF;

[0053] Sensing time authorization information, which is used to indicate the time period during which the sensing service requested is allowed to be executed or the time period during which the sensing service requested is not allowed to be executed;

[0054] The location authorization information is used to indicate the location where the requested sensing service is allowed to be executed or the location where the requested sensing service is not allowed to be executed.

[0055] User consent information, which is used to indicate whether the sensing target agrees to have its data collected used for sensing purposes;

[0056] First interoperability information, which indicates that the sensing function SF allows interoperability with the AF.

[0057] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0058] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the second aspect, and the network-side device can be used to perform the steps of the method as described in the first aspect.

[0059] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0060] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0061] In this embodiment, a first device receives a first request message. The first device determines whether to provide the requested sensing service to the AF based on the first request message and authorization information. The authorization information includes at least one of the following: AF access authorization information, sensing service authorization information, reporting type authorization information, sensing time authorization information, sensing location authorization information, user consent information, and first interoperability information. In this way, the first device can determine whether to provide the requested sensing service to the AF based on the content included in the authorization information. This clarifies how the first device authorizes the first request message sent by the AF for requesting sensing services, helping the network side to better manage the sensing service-related processes. Attached Figure Description

[0062] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0063] Figure 2 is a flowchart of one of the perception service authorization methods provided in an embodiment of this application;

[0064] Figure 3a is a second flowchart of a perception service authorization method provided in an embodiment of this application;

[0065] Figure 3b is a flowchart of a perception service authorization method provided in an embodiment of this application;

[0066] Figure 4 is a flowchart of a configuration information receiving method provided in an embodiment of this application;

[0067] Figure 5 is a structural diagram of a sensing service authorization device provided in an embodiment of this application;

[0068] Figure 6 is a structural diagram of a configuration information receiving device provided in an embodiment of this application;

[0069] Figure 7 is a structural diagram of a communication device provided in an embodiment of this application;

[0070] Figure 8 is a structural diagram of a terminal provided in an embodiment of this application;

[0071] Figure 9 is a structural diagram of a network-side device provided in an embodiment of this application. Detailed Implementation

[0072] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0073] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0074] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0075] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0076] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0077] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0078] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0079] In related technologies, the integration of sensing technology into 3GPP mobile networks is being discussed to enable sensing services within these networks. Typically, the main sensing process includes: 1) the server triggers a sensing request; 2) the network selects an authorized sensing entity; 3) the network initiates the authorized sensing entity to perform the relevant sensing services; 4) the sensing entity performs sensing and reports data to the network; and 5) the network sends the sensing data to the server. It is evident that the server first triggers the sensing request during the execution of the sensing service, but how the network authorizes the sensing request is currently undetermined. To address these issues, this application provides a sensing service authorization method.

[0080] The following description, in conjunction with the accompanying drawings, details the perception service authorization methods, apparatus, and devices provided in this application through some embodiments and application scenarios.

[0081] Please refer to Figure 2, which is a flowchart of one of the perception service authorization methods provided in an embodiment of this application. The method includes the following steps:

[0082] Step 201: The first device receives a first request message, which includes the identifier of the AF and sensing service information, wherein the sensing service information is used to indicate the requested sensing service.

[0083] Optionally, the first device includes at least one of the following: Sensing Function (SF), Network Repository Function (NRF), and Network Exposure Function (NEF).

[0084] The sensing function is a functional entity used to support sensing services. The sensing function can also be called the Sensing Service Management Function (SEMF).

[0085] Optionally, the first request message can be used to indicate a request for the perception service, and can be a perception open request message, a perception registration request message, a discovery request message, a token request message, etc.

[0086] For example, the first device is a NEF, which receives a first request message sent by an AF, the first request message including the AF's identifier and sensing service information. Optionally, the first request message is a sensing open request message.

[0087] Alternatively, the first device is an NRF, which acquires a first request message sent by the NEF, the first request message including the AF's identifier and awareness service information sent by the AF to the NEF; or, the NRF acquires first request information sent by the AF. Optionally, the first request message is a discovery request message or a token request message.

[0088] Alternatively, the first device may be an SF, which receives a first request message sent by a NEF or AF. Optionally, the first request message is a perception registration request message.

[0089] Optionally, the identifier of the AF can be an AF ID. Understandably, based on the identifier of the AF, the first device can determine which AF the first request message originates from, and thus which AF is requesting the sensing service.

[0090] It should be noted that the perception service refers to a service that can use radio signals to collect and provide information about the characteristics of objects and / or the environment, which may include, but is not limited to, services such as personal identification, personal tracking, motion monitoring, and environmental monitoring.

[0091] Step 202: The first device determines whether to provide the requested sensing service to the AF based on the first request message and authorization information.

[0092] The authorization information includes at least one of the following:

[0093] AF access authorization information, which indicates whether AF access is permitted;

[0094] Perception service authorization information, which is used to indicate whether the requested perception service is allowed to be provided to the AF;

[0095] Report type authorization information, which is used to indicate whether the perception result or perception data of the requested perception service is allowed to be provided to the AF;

[0096] Sensing time authorization information, which is used to indicate the time period during which the sensing service requested is allowed to be executed or the time period during which the sensing service requested is not allowed to be executed;

[0097] The location authorization information is used to indicate the location where the requested sensing service is allowed to be executed or the location where the requested sensing service is not allowed to be executed.

[0098] User consent information, which is used to indicate whether the sensing target agrees to have its data collected used for sensing purposes;

[0099] First interoperability information, which indicates that the sensing function SF allows interoperability with the AF.

[0100] For example, the authorization information includes the AF access authorization information. If the AF access authorization information indicates that the AF is allowed to access, the first device determines that the network allows the AF to access based on the AF access authorization information, and the first device determines to provide the requested sensing service to the AF based on the authorization information. If the AF access authorization information indicates that the AF is not allowed to access, the first device determines that the network does not allow the AF to access based on the AF access authorization information, and the first device determines not to provide the requested sensing service to the AF based on the authorization information.

[0101] For example, the authorization information includes the sensing service authorization information. If the sensing service authorization information indicates that the requested sensing service is permitted to be provided to the AF, the first device can determine to provide the requested sensing service to the AF based on the authorization information. If the sensing service authorization information indicates that the requested sensing service is not permitted to be provided to the AF, the first device can determine not to provide the requested sensing service to the AF based on the authorization information.

[0102] For example, the authorization information includes the reporting type authorization information. If the reporting type authorization information indicates that the AF is allowed to provide the perception result of the requested perception service, the first device can determine, based on the authorization information, to provide the AF with the perception result of the requested perception service. If the reporting type authorization information indicates that the AF is allowed to provide the AF with the perception data of the requested perception service, the first device can determine, based on the authorization information, to provide the AF with the perception data of the requested perception service. The reporting type authorization information is used to indicate whether to report perception data or to report perception results. For example, if it indicates reporting perception data, it means that the perception function should provide the AF with the original perception data; if it indicates reporting perception results, it means that the perception function should provide the AF with the perception results generated from the perception data.

[0103] For example, the authorization information includes the sensing time authorization information. If the sensing time authorization information indicates a time period during which the requested sensing service is permitted, the first device can determine, based on the authorization information, to provide the requested sensing service to the AF within the time period indicated by the sensing time authorization information. If the sensing time authorization information indicates a time period during which the requested sensing service is not permitted, the first device can determine, based on the authorization information, not to provide the requested sensing service to the AF within the time period indicated by the sensing time authorization information. It should be noted that the time period in this application can refer to a time range during which sensing is permitted or not permitted, such as 8:00~12:00, 10:00~24:00, etc., and is not specifically limited here.

[0104] For example, the authorization information includes the sensing location authorization information. If the sensing location authorization information indicates a location where the requested sensing service is permitted, the first device can determine, based on the authorization information, to provide the requested sensing service to the AF at the location indicated by the sensing location authorization information. If the sensing location authorization information indicates a location where the requested sensing service is not permitted, the first device can determine, based on the authorization information, not to provide the requested sensing service to the AF at the location indicated by the sensing location authorization information. Here, the sensing location can indicate a range or area where sensing is permitted or not permitted.

[0105] For example, the authorization information includes user consent information, which indicates whether the target of perception agrees to have its data collected for perception purposes. If the user consent information indicates that the target of perception agrees to have its data collected for perception purposes, the first device can determine to provide the requested perception service to the AF based on the authorization information. If the user consent information indicates that the target of perception does not agree to have its data collected for perception purposes, the first device can determine not to provide the requested perception service to the AF based on the authorization information. The target of perception can refer to the target that needs to be perceived. The target of perception is usually a natural person and can be identified using information such as a Subscription Permanent Identifier (SUPI), a group ID, or area information (such as an Area of ​​Interest (AoI)).

[0106] For example, if the authorization information includes first interoperability information indicating that the SF allows interoperability with the AF, then the first device can determine to provide the requested sensing service to the AF based on the authorization information. Here, "SF allows interoperability with AF" can be understood as "SF allows operations such as sensing message and sensing data transmission with AF".

[0107] In this embodiment, the first device receives a first request message. Based on the first request message and authorization information, the first device determines whether to provide the requested sensing service to the AF. The authorization information includes at least one of the following: AF access authorization information, sensing service authorization information, reporting type authorization information, sensing time authorization information, sensing location authorization information, user consent information, and first interoperability information. In this way, the first device can determine whether to provide the requested sensing service to the AF based on the content included in the authorization information. This clarifies how the first device authorizes the first request message sent by the AF for requesting sensing services, helping the network side to better manage the sensing service-related processes.

[0108] Understandably, the authorization information includes AF access authorization information, which enables the network side to determine whether the AF can access the network.

[0109] The authorization information includes sensing service authorization information, which enables the network side to determine whether AF can enable sensing services.

[0110] The authorization information includes reporting type authorization information, which clarifies whether the AF can obtain perception results or perception data.

[0111] The authorization information includes sensing time authorization information, which allows for the identification of time periods during which the AF is permitted to perform sensing services and time periods during which the AF is not permitted to perform sensing services.

[0112] The authorization information includes sensing location authorization information, which allows for the clear definition of the location ranges where the AF is permitted to perform sensing services and the location ranges where the AF is not permitted to perform sensing services.

[0113] The authorization information includes user information. Through the user consent information, it can be clearly determined whether the target of perception agrees to have data collected for perception purposes.

[0114] The authorization information includes first interoperability information, through which the network side can know whether the SF allows interoperability with the AF.

[0115] Understandably, before determining whether to provide the requested sensing service to the AF based on the authorization information, the first device needs to obtain the authorization information.

[0116] Optionally, the method further includes:

[0117] The first device obtains second configuration information from SF, the second configuration information including the authorization information; or,

[0118] The first device obtains the authorization information from the Policy Function (PF) based on the requested perception service.

[0119] For example, the first device is an NRF, which obtains second configuration information including the authorization information from the SF, or the authorization information is pre-configured on the NRF.

[0120] For example, the first device is an SF (Sensitive Device). The SF obtains the authorization information from the PF (Policy Function) based on the requested sensing service. It should be noted that the SF can obtain the authorization information from different policy functions (such as AMF, PCF, UDM, NRF, OAM, etc.) depending on the requested sensing service. For example, the SF can obtain the sensing service authorization information, the reporting type authorization information, and the sensing time authorization information from OAM or NRF. Alternatively, the SF may have the authorization information pre-configured, and the SF obtains second configuration information from its own context, where the second configuration information includes the authorization information.

[0121] In this embodiment of the application, the first device can obtain the authorization information based on any of the above methods, making the way the first device obtains the authorization information more flexible.

[0122] Optionally, the first device obtains the authorization information from the PF according to the requested perception service, including at least one of the following:

[0123] 1) When the requested sensing service is location-related, the first device obtains the sensing location authorization information from Operations, Administration and Maintenance (OAM) or NRF, the authorization information including the sensing location authorization information; for example, when the requested sensing service is a sensing target-related sensing service such as environmental monitoring, the SF can obtain the sensing location authorization information from OAM or NRF, thereby ensuring that the SF can determine, based on the sensing location authorization information, which location ranges are allowed to provide the requested sensing service to the AF.

[0124] 2) When the requested sensing service is related to a user or user equipment (UE), the first device obtains the user consent information from the Unified Data Management (UDM), and the authorization information includes the user consent information. For example, when the requested sensing service is a sensing service whose sensing target is a user, such as personal identification, personal tracking, or motion monitoring, the SF can obtain the user consent information from the UDM to ensure that the SF can determine whether to provide the requested sensing service to the AF based on the user consent information. The user consent information is used to indicate whether the sensing target (user or UE used to identify the user, etc.) agrees to have data collected used for sensing purposes, such as sensing, personal identification, personal tracking, and motion monitoring.

[0125] In this embodiment of the application, the sensing service information is further used to indicate at least one of the following: the requested sensing reporting type, the requested sensing location, the requested sensing time, the requested sensing target, and the second interoperability information; wherein, the second interoperability information is used to indicate that the AF allows interoperability with the SF.

[0126] Understandably, based on the perception service information, the first device can also obtain at least one of the following: the perception reporting type requested by the AF, the perception location corresponding to the perception service requested by the AF, the perception time corresponding to the perception service requested by the AF, the perception target corresponding to the perception service requested by the AF, and the second interoperability information that the AF allows to interoperate with the SF. This helps the first device better determine whether to provide the requested perception service to the AF based on the perception service information and the aforementioned authorization information.

[0127] Optionally, the first device determines whether to provide the requested sensing service to the AF based on the first request message and authorization information, including at least one of the following:

[0128] The first device determines whether to allow the AF access based on the AF access authorization information;

[0129] The first device determines whether to allow the AF to be provided with the requested sensing service based on the sensing service authorization information;

[0130] The first device determines whether to allow the AF to provide the requested perception reporting type based on the reporting type authorization information;

[0131] The first device determines whether the requested sensing time or the current time is a time when the requested sensing service is permitted, based on the sensing time authorization information.

[0132] The first device determines whether the requested sensing location is a location where the requested sensing service is permitted based on the sensing location authorization information.

[0133] The first device determines whether the target of perception agrees to have its data collected for perception purposes based on the user consent information.

[0134] The first device determines whether to allow interoperability with the AF based on the first interoperability information and the second interoperability information.

[0135] For example, if the AF access authorization information indicates that the AF access is allowed, the first device determines that the AF access is allowed based on the AF access authorization information; if the AF access authorization information indicates that the AF access is not allowed, the first device determines that the AF access is not allowed based on the AF access authorization information.

[0136] If the perception service authorization information indicates that the requested perception service is allowed to be provided to the AF, then the first device determines that the requested perception service is allowed to be provided to the AF based on the perception service authorization information; if the perception service authorization information indicates that the requested perception service is not allowed to be provided to the AF, then the first device determines that the requested perception service is not allowed to be provided to the AF based on the perception service authorization information.

[0137] If the reporting type authorization information indicates that the perception result or perception data of the requested perception service is allowed to be provided to the AF, then the first device determines that the perception reporting type of the request is allowed to be provided to the AF based on the reporting type authorization information; if the reporting type authorization information indicates that the perception result or perception data of the requested perception service is not allowed to be provided to the AF, then the first device determines that the perception reporting type of the request is not allowed to be provided to the AF based on the reporting type authorization information.

[0138] The perception time authorization information is used to indicate the time period during which the requested perception service is allowed or not allowed to be executed. The first device can then determine whether the requested perception time or the current time is a time during which the requested perception service is allowed based on the perception time authorization information.

[0139] The sensing location authorization information is used to indicate the location where the requested sensing service is allowed or not allowed to be performed. The first device can then determine whether the requested sensing location is a location where the requested sensing service is allowed based on the sensing location authorization information.

[0140] If the user consent information indicates that the sensing target agrees to have its data collected for sensing purposes, then the first device can determine, based on the user consent information, that the sensing target agrees to have its data collected for sensing purposes; if the user consent information indicates that the sensing target does not agree to have its data collected for sensing purposes, then the first device can determine, based on the user consent information, that the sensing target does not agree to have its data collected for sensing purposes.

[0141] The first interoperability information is used to indicate that the sensing function SF is allowed to interoperate with the AF, and the second interoperability information is used to indicate that the AF is allowed to interoperate with the SF. Then, the first device can determine whether to allow interoperability with the AF based on the first interoperability information and the second interoperability information.

[0142] In this embodiment of the application, the first device can determine whether to provide the requested perception service to the AF based on the specific information content of the above authorization information, effectively clarifying how the first device authorizes the perception service requested by the AF.

[0143] Optionally, the method further includes:

[0144] If the first device determines, based on the first request message and authorization information, that it will not provide the requested sensing service to the AF, the first device rejects the first request message through an authorization rejection message;

[0145] The authorization rejection message includes a rejection reason value, which includes at least one of the following:

[0146] Unauthorized AF;

[0147] Unauthorized sensing services;

[0148] Unauthorized perception reporting type;

[0149] Unauthorized perception of time;

[0150] Unauthorized sensing location;

[0151] Unauthorized perceived targets;

[0152] Interoperability is not allowed.

[0153] In this embodiment, if the first device determines, based on the first request message and authorization information, that it will not provide the requested sensing service to the AF, then the first device sends an authorization denial message to the device that sent the first request message. For example, if the first device obtained the first request message from the AF, then the first device sends the authorization denial message to the AF; if the first device obtained the first request message from the NEF or NRF, then the first device sends the authorization denial message to the NEF or NRF, and the NEF or NRF may further send the authorization denial message to the AF. For better description, in subsequent embodiments, a second device is used as the device that sends the first request message for explanation and illustration; for example, the second device can be the AF, NEF, or NRF.

[0154] The authorization rejection message includes a rejection reason value, which allows the AF, NEF, or NRF to know why the requested sensing service was rejected. This avoids the AF, NEF, or NRF sending the first request message multiple times due to an unclear reason for the rejection of the requested sensing service, thus helping to save equipment costs.

[0155] Optionally, the first device determines, based on the first request message and authorization information, not to provide the requested sensing service to the AF, including at least one of the following:

[0156] 1) The first device determines that the AF access is not allowed based on the AF access authorization information;

[0157] 2) The first device determines, based on the perception service authorization information, that it is not allowed to provide all the requested perception services to the AF; for example, if the perception service authorization information indicates that the allowed perception services are A and B, and the requested perception services are C and D, then the first device determines that it will not provide the requested perception services to the AF.

[0158] 3) The first device determines, based on the reporting type authorization information, that it is not allowed to provide the requested perception reporting type to the AF; for example, if the reporting type authorization information indicates that the allowed perception reporting type is perception data reporting and the requested perception reporting type is perception result reporting, then the first device determines that it will not provide the requested perception service to the AF.

[0159] 4) The first device determines, based on the sensing time authorization information, that the requested sensing time or the current time is not a time when the requested sensing service is permitted; for example, if the sensing time authorization information indicates that the permitted sensing time is 8:00-24:00, and the requested sensing service time or the current time is 6:00, then the first device determines not to provide the requested sensing service to the AF.

[0160] 5) The first device determines, based on the sensing location authorization information, that the requested sensing location is not a location where the requested sensing service is permitted; for example, if the sensing location authorization information indicates that the location area where the requested sensing service is not permitted is A or B, and the requested sensing location is A, then the first device determines that it will not provide the requested sensing service to the AF.

[0161] 6) The first device determines, based on the user consent information, that all the sensing targets do not agree to have their data collected for sensing purposes; for example, if all the sensing targets include A, B, and C, and their user consent information indicates that they do not agree to have their data collected for sensing purposes, then the first device determines not to provide the requested sensing service to the AF.

[0162] 7) The first device determines, based on the first interoperability information and / or the second interoperability information, that interoperability with the AF is not permitted. For example, if the first interoperability information is 1 and the second interoperability information is 3, then the first device determines that it will not provide the requested sensing service to the AF.

[0163] For example, when the first device determines that the AF access is not allowed based on the AF access authorization information, the rejection reason value includes unauthorized AF; when the first device determines that the perception service for all the requested requests is not allowed to be provided to the AF based on the perception service authorization information, the rejection reason value includes unauthorized perception service; when the first device determines that the perception reporting type for the requested requests is not allowed to be provided to the AF based on the reporting type authorization information, the rejection reason value includes unauthorized perception reporting type; when the first device determines that the perception time of the request or the current time is not allowed to be performed based on the perception time authorization information... The time of the requested sensing service, the rejection reason value includes unauthorized sensing time; if the first device determines, based on the sensing location authorization information, that the requested sensing location is not a location where the requested sensing service is permitted, the rejection reason value includes unauthorized sensing location; if the first device determines, based on the user consent information, that all sensing targets do not agree to have their data collected for sensing purposes, the rejection reason value includes unauthorized sensing targets; if the first device determines, based on the first interoperability information and / or the second interoperability information, that interoperability with the AF is not permitted, the rejection reason value includes not allowing interoperability.

[0164] In this embodiment of the application, the first device can determine why the requested sensing service is not provided to the AF based on the specific information content of the above authorization information, and the authorization rejection message sent by the first device includes the rejection reason value, so that the second device (e.g., AF, NEF, or NRF) can know the reason why the requested sensing service is rejected.

[0165] Optionally, the method further includes:

[0166] If the first device determines, based on the first request message and authorization information, to provide the requested sensing service to the AF, the first device accepts the first request message through an authorization response message.

[0167] Understandably, if the first device determines that it is providing the requested sensing service to the AF, the first device sends an authorization response message to the second device, thereby enabling the second device to know that its requested sensing service has been authorized, which helps the device to better implement the sensing service.

[0168] Optionally, the authorization response message can be a sense-open response message, a sense-register response message, a discovery response message, a token response message, etc.

[0169] Optionally, the authorization response message includes at least one of the following:

[0170] The finalized perception service information;

[0171] The final determined perception reporting type;

[0172] Finalized authorization information for perception time;

[0173] Finalized location authorization information;

[0174] The final determined perception target;

[0175] The finalized interoperability information.

[0176] Optionally, the first device determines, based on the first request message and authorization information, to provide the requested perception service to the AF, including at least one of the following:

[0177] 1) The first device determines that the AF access is permitted based on the AF access authorization information.

[0178] 2) The first device determines, based on the sensing service authorization information, that the requested sensing service is a sensing service permitted by the AF; or, the first device determines, based on the sensing service authorization information, that the requested sensing service includes either a sensing service not permitted by the AF or a sensing service permitted by the AF. In this case, the authorization response message includes the finally determined sensing service information, which is used to indicate sensing services not permitted by the AF and / or sensing services permitted by the AF. For example, if the sensing service authorization information indicates permitted sensing services A and B, and the requested sensing service is A, then the first device determines to provide the requested sensing service A to the AF, and the finally determined sensing service information can indicate that A is a sensing service permitted by the AF. As another example, if the sensing service authorization information indicates permitted sensing services A and B, and the requested sensing services are A and D, then the first device determines to provide the requested sensing service A to the AF, and the finally determined sensing service information can indicate that A is a sensing service permitted by the AF, or it can indicate that D is a sensing service not permitted by the AF.

[0179] 3) The first device determines, based on the reporting type authorization information, that the requested perception reporting type is a perception reporting type allowed by the AF; or, the first device determines, based on the reporting type authorization information, that the requested perception reporting type includes both perception reporting types not allowed by the AF and perception reporting types allowed by the AF; in this case, the authorization response message includes the finally determined perception reporting type, which is used to indicate perception reporting types not allowed by the AF and / or perception reporting types allowed by the AF. For example, if the reporting type authorization information indicates that the allowed perception reporting type is perception data reporting, and the requested perception reporting type is perception data reporting, then the first device determines to provide the requested perception service to the AF, and the finally determined perception reporting type can indicate that perception data reporting is a perception reporting type allowed by the AF. For example, if the reporting type authorization information indicates that the allowed perception reporting type is perception data reporting, and the requested perception reporting type is perception data reporting and / or perception result reporting, then the first device determines to provide the requested perception service to the AF. However, the finally determined perception reporting type may indicate that perception data reporting is a perception reporting type allowed by the AF, or it may indicate that perception result reporting is a perception reporting type not allowed by the AF.

[0180] 4) The first device determines, based on the sensing time authorization information, that the requested sensing time or the current time is a permitted time for performing the requested sensing service; or, the first device determines, based on the sensing time authorization information, that the requested sensing time or the current time includes both a time when the requested sensing service is not permitted and a time when the requested sensing service is permitted. In this case, the authorization response message includes the finally determined sensing time authorization information, which indicates the time period during which the requested sensing service is not permitted and / or the time period during which the requested sensing service is permitted. For example, if the sensing time authorization information indicates that the permitted sensing time is 8:00-24:00 and the requested sensing service time is 8:00-11:00, then the first device determines to provide the requested sensing service to the AF, and the finally determined sensing time authorization information can indicate that 8:00-11:00 is the permitted time period for performing the requested sensing service. For example, if the perception time authorization information indicates that the allowed perception time is 8:00-24:00 and the requested perception service time is 6:00-10:00, then the first device determines to provide the requested perception service to the AF. However, the final determined perception time authorization information can indicate that 8:00-10:00 is the allowed time period for the requested perception service, or it can indicate that 6:00-8:00 is the disallowed time period for the requested perception service.

[0181] 5) The first device determines, based on the sensing location authorization information, that the requested sensing location is a location where the requested sensing service is permitted; or, the first device determines, based on the sensing location authorization information, that the requested sensing location includes both locations where the requested sensing service is not permitted and locations where the requested sensing service is permitted. In this case, the authorization response message includes the finally determined sensing location authorization information, which is used to indicate locations where the requested sensing service is not permitted and / or locations where the requested sensing service is permitted. For example, if the sensing location authorization information indicates that the location areas where the requested sensing service is not permitted are A and B, and the requested sensing location is C and D, then the first device determines to provide the requested sensing service to the AF, and the finally determined sensing location authorization information can indicate that C and D are locations where the requested sensing service is not permitted. For example, if the location authorization information indicates that the location areas where the requested sensing service is not allowed are A and B, and the requested sensing location is A, C, or D, then the first device determines to provide the requested sensing service to the AF. However, the final determined location authorization information may indicate that A is a location where the requested sensing service is not allowed, or it may indicate that C and D are locations where the requested sensing service is allowed.

[0182] 6) The first device determines, based on the user consent information, that all the sensing targets agree to have their data collected for sensing purposes; or, the first device determines, based on the user consent information, that the sensing targets include sensing targets that agree to have their data collected for sensing purposes and sensing targets that do not agree to have their data collected for sensing purposes. In this case, the authorization response message includes the finally determined sensing targets, which are used to indicate sensing targets that agree to have their data collected for sensing purposes and / or sensing targets that do not agree to have their data collected for sensing purposes. For example, if the sensing targets include A, B, and C, and the user consent information for A, B, and C all indicates that they agree to have their data collected for sensing purposes, then the first device determines to provide the requested sensing service to the AF, and the finally determined sensing targets can indicate that A, B, and C are sensing targets that agree to have their data collected for sensing purposes. For example, if the sensing targets include A, B, and C, where the user consent information for A indicates that they do not agree to have their data collected for sensing purposes, but the user consent information for B and C indicates that they agree to have their data collected for sensing purposes, then the first device determines to provide the requested sensing service to the AF. However, the final determined sensing target may indicate that A is a sensing target that does not agree to have its data collected for sensing purposes, or it may indicate that B and C are sensing targets that do not agree to have their data collected for sensing purposes.

[0183] 7) The first device determines whether to allow interoperability with the AF based on the first interoperability information and the second interoperability information. For example, if the first interoperability information is 1 and the second interoperability information is also 1, then the first device determines to provide the requested sensing service to the AF, and the finally determined interoperability information can indicate that 1 is the interoperability information that allows interoperability.

[0184] In this embodiment of the application, the first device can determine the requested sensing service for AF based on the above method, and can send an authorization response message to the second device (the device that sent the first request message), so that the second device can know that the requested sensing service has been authorized, which helps the second device to better realize sensing.

[0185] Optionally, the final determined perception service information is used to indicate perception services that the AF does not allow and / or perception services that the AF allows; it should be noted that the final determined perception service information may indicate a changed perception service or a perception service that has not been changed.

[0186] The finally determined perception reporting type is used to indicate the perception reporting types that the AF does not allow and / or the perception reporting types that the AF allows; it should be noted that the finally determined perception reporting type may be a changed perception reporting type or a unchanged perception reporting type.

[0187] The final determined perception time authorization information is used to indicate the time period during which the requested perception service is not allowed and / or the time period during which the requested perception service is allowed; it should be noted that the final determined perception time authorization information may be the changed perception time authorization information or the unchanged perception time authorization information.

[0188] The final determined sensing location authorization information is used to indicate the location where the requested sensing service is not allowed and / or the location where the requested sensing service is allowed; it should be noted that the final determined sensing location authorization information may be the changed sensing location authorization information or the unchanged sensing location authorization information.

[0189] The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to have data collected for perception purposes, and the second perception target is used to indicate disagreement to have data collected for perception purposes. It should be noted that the final determined perception target may be a modified perception target or a unchanged perception target.

[0190] The finalized interoperability information is used to indicate information that allows interoperability and / or information that does not allow interoperability; it should be noted that the finalized interoperability information may be modified interoperability information or unchanged interoperability information.

[0191] Understandably, the authorization response message may include at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing time authorization information, the finally determined sensing location authorization information, the finally determined sensing target, and the finally determined interoperability information. This allows the second device to better perform sensing-related processes based on the acquired information, helping to save the second device's energy. For example, based on the finally determined sensing service information, the second device can know which sensing services the AF does not allow to use, and thus avoid requesting these prohibited sensing services, saving device energy. Similarly, based on the finally determined sensing time authorization information, the second device can know which time periods are not allowed to perform the requested sensing service, and thus avoid requesting sensing services during these prohibited time periods, helping to save device energy. Of course, the change information acquired by the second device may also include the finally determined sensing reporting type, the finally determined sensing location authorization information, the finally determined sensing target, the finally determined interoperability information, etc., which are not specifically listed here.

[0192] Optionally, the authorization response message may further include an access token, and the method further includes:

[0193] The first device generates the access token, the access token comprising at least one of the following:

[0194] The AF identifier, the final determined sensing service information, the final determined sensing reporting type, the final determined sensing location authorization information, the final determined sensing time authorization information, the final determined sensing target, and the final interoperability information.

[0195] For example, the first device is an NRF. The AF sends a first request message to the NRF to request a sensing service. If the NRF determines that it will provide the requested sensing service to the AF, the NRF sends an authorization response message to the AF. This authorization response message includes an access token, which includes at least one of the following: the AF's identifier, the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing location authorization information, the finally determined sensing time authorization information, the finally determined sensing target, and the finally determined interoperability information. Furthermore, the AF can better perform sensing-related processes based on this finally determined information included in the access token, and can also use the access token to access the SF to obtain the content permitted by the aforementioned authorization information.

[0196] For example, the first device is an NRF. The NEF sends a first request message to the NRF requesting a sensing service. If the NRF determines that it will provide the requested sensing service to the AF, the NRF sends an authorization response message to the NEF. This authorization response message includes an access token, which includes at least one of the following: the AF's identifier, the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing location authorization information, the finally determined sensing time authorization information, the finally determined sensing target, and the finally determined interoperability information. Furthermore, the NEF can send corresponding finally determined information to the AF based on the information included in the access token, enabling the AF to better perform the sensing-related processes. The NEF can also use the access token to access the SF to obtain the content permitted by the aforementioned authorization information.

[0197] Understandably, based on the final determined sensing service information, the AF can determine which sensing services are allowed and which are not, thus enabling the AF to selectively request the allowed sensing services. Based on the final determined sensing reporting type, the AF can also determine the allowed sensing reporting types, allowing the AF to report sensing data or results based on the allowed types, thus improving the AF's sensing reporting capabilities. Based on the final determined sensing time authorization information, the AF can determine which time periods are allowed and which are not, allowing the AF to avoid requesting sensing services during these prohibited periods, thus saving device energy. Based on the final determined sensing location authorization information, the AF can determine which location ranges are allowed and which are not, allowing the AF to selectively request sensing services within the allowed location ranges, further improving the AF's sensing capabilities. Based on the finally determined perception targets, the AF can determine which perception targets agree to have their data collected for perception purposes and which do not agree to have their data collected for perception purposes. As a result, the AF can request perception services more specifically for the perception targets.

[0198] Optionally, in some implementations, the first request message includes at least one of the following: the finally determined perception service information, the finally determined perception reporting type, the finally determined perception time authorization information, the finally determined perception location authorization information, and the finally determined perception target.

[0199] For example, the first device is the SF, which receives a first request message sent by the NEF. For instance, the AF sends a sensing service request message to the NEF, requesting sensing services. The NEF sends an authorization request message to the NRF. If the NRF determines to provide the requested sensing services to the AF, the NRF sends an authorization response message to the NEF. This authorization response message includes at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing time authorization information, the finally determined sensing location authorization information, and the finally determined sensing target. Further, the NEF sends a first request message to the SF, requesting sensing services. In this case, the first request message may carry at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing time authorization information, the finally determined sensing location authorization information, and the finally determined sensing target. This allows the SF to determine whether to provide the requested sensing services to the AF based on the change information included in the first request message, helping the SF to better clarify whether to provide the requested sensing services to the AF.

[0200] For example, the first device is an SF (Sensitive Detection and Sensing Service). The SF receives a first request message sent by the NRF (Natural Response Force). For instance, the AF (Awareness and Detection Center) sends a sensing service request message to the SF, and the SF sends an authorization request message to the NRF. If the NRF determines that it will provide the requested sensing service to the AF, the NRF sends an authorization response message to the SF. This authorization response message includes at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing time authorization information, the finally determined sensing location authorization information, and the finally determined sensing target. In this case, the first request message may carry at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing time authorization information, the finally determined sensing location authorization information, and the finally determined sensing target. This allows the SF to determine whether to provide the requested sensing service to the AF based on the change information included in the first request message, helping the SF to better clarify whether to provide the requested sensing service to the AF.

[0201] Optionally, the first request message further includes an access token, which includes finally determined sensing service information, finally determined sensing reporting type, finally determined sensing time authorization information, finally determined sensing location authorization information, finally determined sensing target, and finally determined interoperability information. In this case, the method further includes:

[0202] The first device verifies the access token.

[0203] Optionally, the first device verifies the integrity of the access token. If the integrity verification fails, the access token verification fails, and subsequent operations are terminated.

[0204] Optionally, the first device may additionally verify whether the finalized interoperability information in the access token is the same as its own interoperability information. For example, if they are different, the access token verification fails, and subsequent operations can be terminated.

[0205] For example, the first device is an SF. As described above, the SF receives a first request message sent by the NEF. For instance, the AF sends a sensing service request message to the NEF to request sensing services, the NEF sends an authorization request message to the NRF, and if the NRF determines that it will provide the requested sensing services to the AF, the NRF generates an access token and sends an authorization response message to the NEF, which includes the access token. Further, the NEF sends a first request message to the SF to request sensing services. In this case, the first request message may carry the access token, and the access token carries at least one of the following: finally determined sensing service information, finally determined sensing reporting type, finally determined sensing time authorization information, finally determined sensing location authorization information, finally determined sensing target, and finally determined interoperability information. The SF verifies the access token according to the received first request message, and then determines whether to provide the requested sensing services to the AF based on the information carried in the access token.

[0206] For example, the first device is the SF, which receives a first request message from the NRF. For instance, the AF sends a sensing service request message to the SF requesting sensing services, and the SF sends an authorization request message to the NRF. If the NRF determines to provide the requested sensing services to the AF, the NRF generates an access token and sends an authorization response message (i.e., the first request message) to the SF. This authorization response message includes the access token, which includes at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing time authorization information, the finally determined sensing location authorization information, the finally determined sensing target, and the finally determined interoperability information. The SF verifies the access token based on the received first request message and then determines whether to provide the requested sensing services to the AF based on the information carried in the access token.

[0207] In this embodiment of the application, the method further includes:

[0208] The first device performs at least one of the following:

[0209] Configure SF to enable the perception services allowed by AF based on the finally determined perception service information;

[0210] Configure SF to enable the perception reporting types allowed by AF based on the finally determined perception reporting type;

[0211] Configure SF to enable the time period during which the requested sensing service is performed, based on the final determined sensing time authorization information.

[0212] Based on the final determined sensing location authorization information, configure SF to enable the sensing service location that allows the request;

[0213] Based on the finally determined perception target configuration, SF enables the perception target to consent to the use of collected data for perception purposes.

[0214] For example, the first device is SF, which is capable of performing self-sensing configuration based on the aforementioned change information.

[0215] For example, if the final determined perception service information indicates perception services that the AF does not allow and perception services that the AF allows, then the SF performs perception configuration, configuring only the SF to enable the perception services that the AF allows.

[0216] If the finally determined perception reporting type indicates both the perception reporting types that the AF does not allow and the perception reporting types that the AF allows, then the SF performs perception configuration, configuring the SF to enable only the perception reporting types allowed by the AF.

[0217] If the final determined perception time authorization information is used to indicate the time period during which the requested perception service is not allowed and the time period during which the requested perception service is allowed, then SF performs perception configuration, configuring SF to enable only the time period during which the requested perception service is allowed.

[0218] If the final determined sensing location authorization information is used to indicate the locations where the requested sensing service is not allowed and the locations where the requested sensing service is allowed, then SF performs sensing configuration, configuring SF to enable only the locations where the requested sensing service is allowed.

[0219] If the finally determined perception targets are used to indicate perception targets that agree to have their data collected for perception purposes and perception targets that do not agree to have their data collected for perception purposes, then SF performs perception configuration and only configures SF to enable perception targets that agree to have their data collected for perception purposes.

[0220] In this way, SF can configure its own perception based on the finalized information, and thus control perception behavior in accordance with the authorization policy.

[0221] Optionally, the method further includes:

[0222] The first device sends first configuration information to the sensing entity, the first configuration information being used to indicate at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing location authorization information, the finally determined sensing time authorization information, and the finally determined sensing target.

[0223] It should be noted that the sensing entity is a device with sensing capabilities, which may include terminals and access network devices, and may be a sensing receiver or a sensing sender.

[0224] For example, the first device is an SF (Sensitive Detector). The SF can also send first configuration information to the sensing entity to configure the sensing entity. For instance, if the finally determined sensing service information indicates sensing services that the AF (Awareness Detection Center) does not allow and sensing services that the AF allows, the first configuration information sent by the SF is used to indicate the finally determined sensing service information, so that the sensing entity is configured only with the sensing services allowed by the AF.

[0225] If the finally determined perception reporting type indicates both the perception reporting types that the AF does not allow and the perception reporting types that the AF allows, then the first configuration information sent by the SF is used to indicate the finally determined perception reporting type, so that the perception entity only configures the allowed perception reporting types.

[0226] If the final determined perception time authorization information is used to indicate the time period during which the requested perception service is not allowed and the time period during which the requested perception service is allowed, then the first configuration information sent by SF is used to indicate the final determined perception time authorization information, so that the perception entity is configured to perceive only during the allowed time period, or to only send perception results or perception data during the allowed time period.

[0227] If the final determined sensing location authorization information is used to indicate the location where the requested sensing service is not allowed and the location where the requested sensing service is allowed, then the first configuration information sent by SF is used to indicate the final determined sensing location authorization information, so that the sensing entity is configured to only perform sensing in the allowed locations, or only send sensing results or sensing data of the allowed locations.

[0228] If the finally determined perception target is used to indicate perception targets that agree to have their data collected for perception purposes and perception targets that do not agree to have their data collected for perception purposes, then the first configuration information sent by SF is used to indicate the finally determined perception target, such that the perception entity is configured to only allow perception of the agreed perception targets, or only send the perception results or perception data of the agreed perception targets.

[0229] In this way, SF can configure the sensing entity through the first configuration information, thereby better regulating the sensing behavior of the sensing entity.

[0230] To better understand, the technical solutions provided in the embodiments of this application will be described below in conjunction with specific communication scenarios.

[0231] Please refer to Figure 3a, which is a second flowchart of a perception service authorization method provided in an embodiment of this application. The method includes the following steps:

[0232] Step 10a: The AF can register its configuration information with the NRF through the NEF. At this time, the AF's configuration information is bound to the NEF identifier and can be represented by the NRF as NEF ID:AF configuration information.

[0233] AF configuration information may include AF ID and AF interoperability information (the second interoperability information mentioned above).

[0234] Interoperability information in an Alliance Provider (AF) indicates whether the AF permits interoperability with a Private Provider (SF). AF interoperability information may include at least one of the following: interoperability indication, alliance identifier, group identifier, vendor identifier, etc. For example, if the AF and SF have the same alliance identifier and group identifier, it means that the AF and SF can interoperate. Alternatively, if the AF's vendor identifier belongs to the SF's vendor identifier list, it means that the AF and SF can interoperate.

[0235] Step 10b. The NRF obtains the first authorization information (the authorization information mentioned above). Optionally, the sensing function SF registers the first authorization information with the NRF, or the first authorization information is pre-configured on the NRF.

[0236] The first authorization information may include SF ID, AF access authorization information, sensing service authorization information, reporting type authorization information, sensing time authorization information, sensing location authorization information, and SF interoperability information (the aforementioned first interoperability information). Among these:

[0237] 1) AF access authorization information is used to indicate whether AF access is permitted;

[0238] 2) The perception service authorization information is used to indicate whether perception services are permitted for AF;

[0239] 3) The reporting type authorization information is used to indicate whether it is allowed to provide sensing results or sensing data to AF.

[0240] 4) The perception time authorization information is used to indicate the time period during which perception services are allowed or not allowed.

[0241] 5) The sensing location authorization information is used to indicate the location where sensing services are allowed or not allowed.

[0242] 6) SF interoperability information is used to indicate information that SF is allowed to interoperate with AF.

[0243] Step 11: The AF sends a first request message to the NEF. The first request message is used to trigger the sensing service. The first request message may include the AF ID, the requested sensing service, the requested sensing reporting type, the requested sensing location, the requested sensing time, the requested sensing target, and the AF's interoperability information.

[0244] Sensing services can include various services that can be provided through sensing, such as personal identification, personal tracking, motion monitoring, and environmental monitoring.

[0245] The perception reporting type can indicate whether to report perception data or perception results.

[0246] The sensing location can indicate the range of locations that need to be sensed.

[0247] Perception targets can indicate the targets that need to be perceived, such as SUPI or group ID.

[0248] Step 12: NEF sends a first request message (which can be a Token Request or a Discovery Request) to NRF. This message may include AFID, the requested sensing service, the requested sensing reporting type, the requested sensing location, the requested sensing time, and AF interoperability information.

[0249] The NRF determines whether to authorize access to the AF using at least one of the following methods:

[0250] 1) Determine whether to allow AF access based on the AF access authorization information;

[0251] 2) Determine whether to allow the requested perception service to be provided to AF based on the perception service authorization information;

[0252] 3) Determine whether to allow the perception reporting type to be provided to AF based on the reporting type authorization information;

[0253] 4) Whether the requested perception time is the time allowed by the perception time authorization information;

[0254] 5) Whether the requested sensing location is a location permitted by the sensing location authorization information;

[0255] 6) Determine whether interoperability with AF is permitted based on the interoperability instructions of AF and SF.

[0256] Further, based on the above determination results, NRF performs any of the following steps:

[0257] Step a. Reject the first request message (e.g., reply with an authorization rejection message). Optionally, the authorization rejection message may contain a rejection reason value to indicate the reason for the rejection. The rejection reason value may include at least one of the following: unauthorized AF, unauthorized sensing service, unauthorized sensing reporting type, unauthorized sensing time, unauthorized sensing location, unauthorized sensing target, or disallowed interoperability. Specifically, the NRF determines to reject the first request message based on at least one of the following:

[0258] 1) Determine that AF access is not allowed based on the AF access authorization information;

[0259] 2) Determine which perception services are not allowed to be provided to AF for all requests based on the perception service authorization information;

[0260] 3) Determine the perception reporting types that are not allowed to provide all requests to AF based on the reporting type authorization information;

[0261] 4) Determine that the requested sensing time period is entirely within the disallowed time period based on the sensing time authorization information;

[0262] 5) Determine that the requested sensing location is completely in an unauthorized location based on the sensing location authorization information;

[0263] 6) Based on the interoperability instructions of AF and SF, it is determined that interoperability with AF is not allowed.

[0264] Step b. Accept the first request message (e.g., reply with an authorization response message). Optionally, the NRF generates an access token, which may contain the SF ID, NEF ID, AF ID, AF interoperability indication, and may also include additional information elements (IEs) based on the following criteria:

[0265] 1) If the perception service authorization information indicates that there are both disallowed and permitted perception services among the perception services requested by AF, the authorization response message contains the finally determined perception service information to indicate the disallowed and / or permitted perception services; optionally, the Token includes the finally determined perception service information.

[0266] 2) If the reporting type authorization information indicates that there are both disallowed and allowed perception reporting types in the perception reporting type of the AF request, the authorization response message includes the finally determined perception reporting type to indicate the disallowed perception service and / or allowed perception service; optionally, the Token includes the finally determined perception reporting type.

[0267] 3) If the perception time authorization information indicates that there are both disallowed and allowed time periods in the requested perception time period, the authorization response message contains the finally determined perception time authorization information to indicate the disallowed perception time and / or allowed perception time; optionally, the Token includes the finally determined perception time authorization information.

[0268] 4) If the sensing location authorization information indicates that there are both disallowed and permitted locations among the requested sensing locations, the authorization response message contains the finally determined sensing location authorization information to indicate the disallowed and / or permitted sensing locations; optionally, the Token includes the finally determined sensing location authorization information.

[0269] 5) If the user consent information indicates that the requested perception target contains both perception targets that consent to the collection of data for perception purposes and perception targets that do not consent to the collection of data for perception purposes, then the authorization response message includes the finally determined perception target; optionally, the Token includes the finally determined perception target.

[0270] 6) If the interoperability indication of AF and the interoperability indication of SF contain indications that allow interoperability and indications that disallow interoperability, the authorization response message includes the finalized interoperability information. Optionally, the Token includes the finalized interoperability information.

[0271] Step 13: The NRF sends an authorization response message / authorization rejection message to the NEF in response to the first request message. The authorization response message may include a Token, finalized sensing service information, changed reporting type information, finalized sensing time authorization information, finalized sensing location authorization information, finalized sensing target, and finalized interoperability information. Optionally, the Token may include the SFID, NEF ID, AF ID, AF interoperability information, finalized sensing service information, changed reporting type information, finalized sensing time authorization information, finalized sensing location authorization information, finalized sensing target, and finalized interoperability information.

[0272] NEF determines whether to authorize the first request message based on any of the following:

[0273] 1) Determine based on the authorization response message / authorization denial message returned by the NRF;

[0274] 2) Determine based on the locally pre-configured second authorization information. The second authorization information can be the entirety or a subset of the first authorization information (i.e., the authorization response information).

[0275] Based on the judgment result, NEF will perform any of the following steps:

[0276] Step a. Reject the first request message (e.g., reply with a first perception rejection message, which can also be understood as the authorization rejection message mentioned above). Optionally, this message may contain a rejection reason value to indicate the reason for rejecting the first request message. This reason could be unauthorized AF, unauthorized perception service, unauthorized perception reporting type, unauthorized perception time, unauthorized perception location, disallowed interoperability, etc. Specifically, NEF determines to reject the first request message based on at least one of the following:

[0277] 1) An authorization denial message was received;

[0278] 2) A judgment result similar to the NRF rejection of the first request message appears based on the second authorization information.

[0279] Step b. Execute step 15, i.e., send the second sensing request (which can be understood as the aforementioned first request message). Optionally, the second sensing service request may include AF ID, Token, the requested sensing service or the finally determined sensing service information, the requested sensing reporting type or the finally determined sensing reporting type, the requested sensing location or the finally determined sensing location authorization information, the requested sensing time or the finally determined sensing time authorization information, the requested sensing target or the finally determined sensing target, and AF interoperability information.

[0280] Optionally, a first request message can also be accepted (e.g., sending a first sensing response message to the AF, which can also be understood as the aforementioned authorization response message). Optionally, this message can also be used to indicate changes to the service request, and may include finally determined sensing service information, finally determined sensing reporting type, finally determined sensing location authorization information, finally determined sensing time authorization information, and finally determined interoperability information. Specifically, the NEF determines to accept the first request message based on at least one of the following:

[0281] 1) Received the authorization response message;

[0282] 2) A judgment result similar to NRF accepting the first request message appears based on the second authorization information.

[0283] Step 14: NEF sends a first perception rejection / response message to AF in response to the first request message. The message content is as described in step 3.

[0284] Step 15: NEF sends a second perception request to SF. The second perception request is used to trigger the perception service. Optionally, the second perception request may include AF ID, Token, the requested perception service or the finally determined perception service information, the requested perception reporting type or the finally determined perception reporting type, the requested perception location or the finally determined perception location authorization information, the requested perception time or the finally determined perception time authorization information, the requested perception target or the finally determined perception target, and AF interoperability information.

[0285] Step 16: SF obtains third-party authorization information. This third-party authorization information may include the content of the first-party authorization information, and may also include user consent information.

[0286] Optionally, SF obtains authorization information from different policy functions (such as AMF, PCF, UDM, NRF, OAM, etc.) based on the perception service of different requests.

[0287] For example, SF can obtain service authorization information, reporting type authorization information, and sensing time authorization information from OAM / NRF. When the sensing service is environmental monitoring or other sensing targets that are location-related, SF can obtain sensing location authorization information from OAM / NRF. When the sensing service is personal identification, personal tracking, motion monitoring, or other sensing targets that are people, SF can obtain user consent information from UDM.

[0288] The user consent information is used to indicate whether the sensing target (in the case of a UE that is a person or an identifier of a person) agrees to have its data collected for sensing purposes, such as sensing, personal identification, personal tracking, motion monitoring, etc.

[0289] Step 17: SF authorizes the perception service based on the second perception request and / or the third authorization information.

[0290] Specifically, SF determines whether to authorize a second perception request based on one or more of the following:

[0291] a) Based on the change information in the Token carried by the second perception request;

[0292] b) Based on the change information in the second perception request;

[0293] c) Make a judgment based on the information requested in the second perception request and the third authorization information.

[0294] Specifically, for the user consent information unique to the third authorization information, SF can determine whether the user consent information of the sensing target indicates consent to the collection of data for sensing purposes; wherein the sensing target comes from the requested sensing target or is determined based on other information in the sensing request message. The user consent information is used to indicate whether the sensing target (in the case of a UE that is a person or an identified person) consents to the collection of data for sensing purposes, such as sensing, personal identification, personal tracking, motion monitoring, etc.

[0295] Based on the judgment result, SF will perform any of the following steps:

[0296] Step a. Reject the second sensing request, for example, by sending a second sensing rejection message to NEF. Optionally, the message may contain a rejection reason value to indicate the reason for the rejection authorization, including at least one of the following: unauthorized AF, unauthorized sensing service, unauthorized sensing reporting type, unauthorized sensing time, unauthorized sensing location, unauthorized sensing target, or interoperability not allowed.

[0297] Specifically, the SF can make a judgment based on the third authorization information, similar to an NRF rejection of the first request message. In particular, regarding user consent information, if the user consent information of the sensing target indicates that all requesting sensing targets do not agree to have their data collected, then the SF rejects the second sensing request.

[0298] Step b. The SF configures itself for perception and accepts a second perception request (e.g., sending a second perception response message to the NEF). Specifically, this includes at least one of the following:

[0299] 1) If, according to the Token in the second perception request, the finally determined perception service information, or the perception service authorization information in the third authorization information, there are both disallowed and permitted perception services in the perception services of the AF request, then SF performs perception configuration and only configures the permitted perception services.

[0300] 2) If, according to the Token in the second perception request, the finally determined perception reporting type, or the reporting type authorization information in the third authorization information, there are both disallowed and allowed perception reporting types in the perception reporting type of the AF request, then SF will perform perception configuration and only configure the allowed perception reporting types.

[0301] 3) If the requested perception time period indicates that there are both an unacceptable time period and an allowed time period according to the Token in the second perception request, the finally determined perception time authorization information, or the perception time authorization information in the third authorization information, then SF performs perception configuration so that the generated perception result does not have perception information under the unacceptable time period, or removes the perception data of the unacceptable time period from the perception data.

[0302] 4) If the token in the second perception request, the final determined perception location authorization information, or the perception location authorization information in the third authorization information indicates that there are both disallowed and allowed locations in the requested perception location, then SF will perform perception configuration so that the generated perception result does not have perception information under disallowed locations, or remove perception data under disallowed locations from the perception data.

[0303] 5) If the user consent information of the requested sensing target contains both disagreement and consent information, then SF will perform sensing configuration so that the generated sensing result does not contain sensing data of sensing targets with disagreement, or removes sensing data of sensing targets with disagreement from the sensing data.

[0304] Step c. The SF sends sensing configuration information (the aforementioned first configuration information) to the sensing entity to configure the sensing entity and accepts a second sensing request (e.g., sending a second sensing response message to the NEF). Specifically, it includes at least one of the following:

[0305] 1) If the token in the second perception request, the finally determined perception service information, or the perception service authorization information in the third authorization information indicates that there are both disallowed and allowed perception services in the perception services of the AF request, then the SF generates perception configuration information so that the perception entity only configures the allowed perception services.

[0306] 2) If, according to the Token in the second perception request, the finally determined perception reporting type, or the reporting type authorization information in the third authorization information, there are both disallowed and allowed perception reporting types in the perception reporting type of the AF request, then SF generates perception configuration information so that the perception entity is configured only with allowed perception reporting types.

[0307] 3) If the Token in the second perception request or the finally determined perception time authorization information or the perception time authorization information in the third authorization information indicates that there are both disallowed and allowed time periods in the requested perception time period, then SF generates perception configuration information so that the perception entity is configured to perceive only in the allowed time period, or to send only the perception results or perception information in the allowed time period.

[0308] 4) If the token in the second sensing request, the final determined sensing location authorization information, or the sensing location authorization information in the third authorization information indicates that there are both disallowed and allowed locations in the requested sensing location, then SF generates sensing configuration information so that the sensing entity is configured to only sense in the allowed sensing locations, or only send the sensing results or sensing information of the allowed locations.

[0309] 5) If the user consent information of the requested sensing target contains both disagreement and consent, then SF generates sensing configuration information so that the sensing entity only senses the sensing targets that consent, or only sends the sensing results or sensing data of the sensing targets that consent.

[0310] It should be noted that, for steps b and c, the second perception response message is used to indicate that the perception request was successful. Optionally, this message can also be used to indicate changes to the service request, and may include the finalized perception service information, the finalized perception reporting type, the finalized perception location authorization information, the finalized perception time authorization information, and the finalized perception target.

[0311] Step 18: NEF sends a first perception response message to AF in response to the first request message (if SF performs authorization verification, the message in step 14 may be delayed until step 18).

[0312] Please refer to Figure 3b, which is a third flowchart of a perception service authorization method provided in an embodiment of this application. The method includes the following steps:

[0313] Step 20a: The AF can register its own configuration information with the NRF. The AF configuration information may include the AF ID and the AF interoperability instructions.

[0314] Step 20b. The NRF obtains the first authorization information (the authorization information mentioned above). Optionally, the SF registers the first authorization information with the NRF, or the first authorization information is pre-configured on the NRF. The first authorization information may include the SF ID, AF access authorization information, sensing service authorization information, reporting type authorization information, sensing time authorization information, sensing location authorization information, and the SF's interoperability indication.

[0315] Step 21: The AF sends a first request message (or first sensing service request, which may be a Token Request or a service request) to the NRF. This message may include the AF ID, the requested sensing service, the requested sensing reporting type, the requested sensing location, the requested sensing time, and the AF's interoperability information.

[0316] The NRF verifies whether access to the AF is authorized, similar to step 12 above. Based on the judgment result, the NRF can perform: a) reject the first request message (e.g., reply with an authorization rejection message); b) accept the first request message (e.g., reply with an authorization response message). Optionally, the NRF generates a token.

[0317] Step 22: The NRF sends an authorization response / rejection message to the AF in response to the first request message. The authorization response message may include a Token, finalized sensing service information, finalized sensing reporting type, finalized sensing time authorization information, finalized sensing location authorization information, finalized sensing target, and finalized interoperability information. Optionally, the Token includes the SF ID, AF ID, AF interoperability information, finalized sensing service information, changed reporting type information, finalized sensing time authorization information, finalized sensing location authorization information, finalized sensing target, and finalized interoperability information.

[0318] Step 23: The AF sends a second sensing request to the SF. The second sensing request is used to trigger the sensing service. The second sensing request may include the AF ID, Token, the requested sensing service or the finally determined sensing service information, the requested sensing reporting type or the finally determined sensing reporting type, the requested sensing location or the finally determined sensing location authorization information, the requested sensing time or the finally determined sensing time authorization information, the requested sensing target or the finally determined sensing target, and the AF's interoperability information.

[0319] Step 24: Optionally, SF obtains third-party authorization information. In addition to the first-party authorization information, the third-party authorization information may also include user consent information.

[0320] Optionally, SF obtains authorization information from different policy functions (such as AMF, PCF, UDM, NRF, OAM, etc.) based on the perception service of different requests.

[0321] Step 25: SF authorizes the perception service based on the second perception request and / or the third authorization information.

[0322] The SF verifies whether to authorize the AF's service request in the same way as step 17 above. The SF can perform the following actions based on the judgment result: a) reject the second perception request (send a second perception rejection message to NEF); b) configure itself for perception and accept the second perception request (send a second perception response message to NEF); c) send perception configuration information to the perception entity to configure the perception entity and accept the second perception request (send a second perception response message to NEF).

[0323] In this embodiment, authorization verification of whether the AF can access the network is achieved by introducing AF access authorization information; authorization verification of whether the AF can enable the sensing service is achieved by introducing sensing service authorization information; authorization verification of whether the AF can obtain sensing results or sensing data is achieved by introducing reporting type authorization information; authorization verification of whether sensing can be performed within a certain time period is achieved by introducing sensing time authorization information; authorization verification of whether sensing can be performed at a certain location is achieved by introducing sensing location authorization information; authorization verification of whether sensing can be performed on certain sensing targets is achieved by introducing user consent information; and authorization verification of whether interoperability can be performed between the AF and the SF is achieved by introducing interoperability information.

[0324] Please refer to Figure 4, which is a flowchart of a configuration information receiving method provided in an embodiment of this application. As shown in Figure 4, the method includes the following steps:

[0325] Step 401: The sensing entity receives first configuration information sent by the first device, wherein the first configuration information is used to indicate at least one of the following:

[0326] The final determined perception service information is used to indicate the perception services that the AF does not allow and / or the perception services that the AF allows.

[0327] The final determined perception reporting type, which is used to indicate perception reporting types that the AF does not allow and / or perception reporting types that the AF allows;

[0328] The final determined perception time authorization information is used to indicate the time period during which perception services that do not allow AF requests are performed and / or the time period during which perception services that allow the requests are performed.

[0329] The final determined sensing location authorization information is used to indicate the location of the sensing service that does not allow the AF request and / or the location of the sensing service that allows the request.

[0330] The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to the collection of data for perception purposes, and the second perception target is used to indicate disagreement to the collection of data for perception purposes.

[0331] It should be noted that the sensing entity is a device with sensing capabilities, which may include terminals and access network devices, and may be a sensing receiver or a sensing sender.

[0332] Optionally, the sensing entity configures the sensing service based on the first configuration information.

[0333] For example:

[0334] 1) The sensing entity configures allowed and / or disallowed sensing services based on the final determined sensing service information;

[0335] 2) The sensing entity configures the allowed and / or disallowed sensing reporting types based on the finally determined sensing reporting type; for example, reporting sensing data or sensing results.

[0336] 3) The sensing entity configures the time periods during which sensing services are allowed and / or not allowed, based on the final determined sensing time authorization information; for example, it configures sensing services to be performed between 8:00 and 11:00.

[0337] 4) The sensing entity configures the locations where sensing services are allowed and / or not allowed based on the final determined sensing location authorization information; for example, it configures that sensing services are not allowed in areas C and D, and sensing services are allowed in areas A and B.

[0338] 5) Based on the final determined perception target, the perception entity configures the perception targets that agree and / or disagree with the collection of data for perception purposes; for example, it configures that no perception service is provided for targets A and B, or that perception service is provided for targets C and D.

[0339] The relevant concepts and specific implementation processes involved in this embodiment can be referred to the descriptions in the previous embodiments. To avoid repetition, they will not be repeated in this embodiment.

[0340] In this embodiment of the application, the sensing entity receives first configuration information sent by the first device, so that the first device can configure the sensing entity through the first configuration information, thereby better regulating the sensing behavior of the sensing entity.

[0341] The perception service authorization method provided in this application can be executed by a perception service authorization device. This application uses the example of a perception service authorization device executing the perception service authorization method to illustrate the perception service authorization device provided in this application.

[0342] This application provides a sensing service authorization device. As an example, the sensing service authorization device can be a communication device or a component within a communication device, such as a chip. The communication device can be a network-side device or a server, etc. Exemplarily, the network-side device can include, but is not limited to, the types of network-side devices 12 listed above; this application does not impose specific limitations on these types.

[0343] The sensing service authorization device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0344] Please refer to Figure 5, which is a structural diagram of a sensing service authorization device provided in an embodiment of this application. As shown in Figure 5, the sensing service authorization device 500 includes:

[0345] The first receiving module 501 is configured to receive a first request message, the first request message including the identifier of AF and sensing service information, the sensing service information being used to indicate the requested sensing service;

[0346] The determining module 502 is configured to determine, based on the first request message and authorization information, whether to provide the requested perception service to the AF; wherein the authorization information includes at least one of the following:

[0347] AF access authorization information, which indicates whether AF access is permitted;

[0348] Perception service authorization information, which is used to indicate whether the requested perception service is allowed to be provided to the AF;

[0349] Report type authorization information, which is used to indicate whether the perception result or perception data of the requested perception service is allowed to be provided to the AF;

[0350] Sensing time authorization information, which is used to indicate the time period during which the sensing service requested is allowed to be executed or the time period during which the sensing service requested is not allowed to be executed;

[0351] The location authorization information is used to indicate the location where the requested sensing service is allowed to be executed or the location where the requested sensing service is not allowed to be executed.

[0352] User consent information, which is used to indicate whether the sensing target agrees to have its data collected used for sensing purposes;

[0353] First interoperability information, which indicates that the sensing function SF allows interoperability with the AF.

[0354] Optionally, the sensing service information is further used to indicate at least one of the following: the requested sensing reporting type, the requested sensing location, the requested sensing time, the requested sensing target, and the second interoperability information;

[0355] The second interoperability information is used to indicate that the AF allows interoperability with the SF.

[0356] Optionally, the determining module 502 is further configured to perform at least one of the following:

[0357] Determine whether to allow AF access based on the AF access authorization information;

[0358] Determine whether to allow the provision of the requested perception service to the AF based on the perception service authorization information;

[0359] Determine whether to allow the AF to be provided with the perception reporting type of the request based on the reporting type authorization information;

[0360] Based on the perception time authorization information, determine whether the perception time of the request or the current time is a time when the perception service of the request is permitted.

[0361] Based on the sensing location authorization information, determine whether the requested sensing location is a location where the requested sensing service is permitted;

[0362] Based on the user consent information, determine whether the target of perception agrees to have its data collected for perception purposes;

[0363] Whether to allow interoperability with the AF is determined based on the first interoperability information and the second interoperability information.

[0364] Optionally, the device further includes:

[0365] The rejection module is used to reject the first request message by means of an authorization rejection message if it is determined, based on the first request message and authorization information, that the requested perception service will not be provided to the AF.

[0366] The authorization rejection message includes a rejection reason value, which includes at least one of the following:

[0367] Unauthorized AF;

[0368] Unauthorized sensing services;

[0369] Unauthorized perception reporting type;

[0370] Unauthorized perception of time;

[0371] Unauthorized sensing location;

[0372] Unauthorized perceived targets;

[0373] Interoperability is not allowed.

[0374] Optionally, the determining module 502 is further configured to perform at least one of the following:

[0375] Based on the AF access authorization information, it is determined that the AF access is not permitted;

[0376] Based on the perception service authorization information, it is determined that the perception service for all the requested requests is not allowed to be provided to the AF;

[0377] Based on the reporting type authorization information, it is determined that the perception reporting type for the request is not allowed to be provided to the AF;

[0378] Based on the perception time authorization information, it is determined that the perception time of the request or the current time is not a time when the perception service requested is permitted.

[0379] Based on the sensing location authorization information, it is determined that the requested sensing location is not a location where the requested sensing service is permitted.

[0380] Based on the user consent information, it was determined that none of the aforementioned sensing targets agreed to have their data collected for sensing purposes.

[0381] Based on the first interoperability information and / or the second interoperability information, it is determined that interoperability with the AF is not allowed.

[0382] Optionally, the device further includes:

[0383] The receiving module is configured to accept the first request message via an authorization response message when it is determined, based on the first request message and authorization information, that the requested perception service is to be provided to the AF.

[0384] Optionally, the authorization response message includes at least one of the following:

[0385] The finalized perception service information;

[0386] The final determined perception reporting type;

[0387] Finalized authorization information for perception time;

[0388] Finalized location authorization information;

[0389] The final determined perception target;

[0390] The finalized interoperability information.

[0391] Optionally, the determining module 502 is further configured to perform at least one of the following:

[0392] Based on the AF access authorization information, determine whether the AF access is permitted;

[0393] The requested perception service is determined to be a perception service allowed by the AF based on the perception service authorization information, or the requested perception service includes a perception service not allowed by the AF or a perception service allowed by the AF based on the perception service authorization information.

[0394] The perception reporting type of the request is determined to be a perception reporting type allowed by the AF based on the reporting type authorization information, or the perception reporting type of the request includes perception reporting types not allowed by the AF and perception reporting types allowed by the AF based on the reporting type authorization information.

[0395] The perception time or current time of the request is determined based on the perception time authorization information as a time when the perception service of the request is permitted, or the perception time or current time of the request is determined based on the perception time authorization information as including both a time when the perception service of the request is not permitted and a time when the perception service of the request is permitted.

[0396] The requested sensing location is determined to be a location where the requested sensing service is permitted, based on the sensing location authorization information; or, the requested sensing location is determined to include both locations where the requested sensing service is not permitted and locations where the requested sensing service is permitted, based on the sensing location authorization information.

[0397] Based on the user consent information, it is determined that all the perception targets agree to have their data collected for perception purposes, or, based on the user consent information, it is determined that the perception targets include perception targets that agree to have their data collected for perception purposes and perception targets that do not agree to have their data collected for perception purposes.

[0398] Based on the first interoperability information and the second interoperability information, it is determined that interoperability with the AF is permitted.

[0399] Optionally, at least one of the following conditions must also be met:

[0400] The final determined sensing service information is used to indicate the sensing services that the AF does not allow and / or the sensing services that the AF allows.

[0401] The final determined perception reporting type is used to indicate the perception reporting types that the AF does not allow and / or the perception reporting types that the AF allows.

[0402] The final determined perception time authorization information is used to indicate the time period during which the requested perception service is not allowed and / or the time period during which the requested perception service is allowed.

[0403] The final determined sensing location authorization information is used to indicate the location where the requested sensing service is not allowed and / or the location where the requested sensing service is allowed.

[0404] The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to have data collected for perception purposes, and the second perception target is used to indicate disagreement to have data collected for perception purposes.

[0405] The finalized interoperability information is used to indicate information that allows interoperability and / or information that does not allow interoperability.

[0406] Optionally, the first request message includes at least one of the following: the finally determined perception service information, the finally determined perception reporting type, the finally determined perception time authorization information, the finally determined perception location authorization information, and the finally determined perception target.

[0407] Optionally, the first request message further includes an access token: the access token includes the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing time authorization information, the finally determined sensing location authorization information, the finally determined sensing target, and the finally determined interoperability information; the device further includes:

[0408] The verification module is used to verify the access token.

[0409] Optionally, the device further includes:

[0410] An execution module is used to perform at least one of the following:

[0411] Configure SF to enable the perception services allowed by AF based on the finally determined perception service information;

[0412] Configure SF to enable the perception reporting types allowed by AF based on the finally determined perception reporting type;

[0413] Configure SF to enable the time period during which the requested sensing service is performed, based on the final determined sensing time authorization information.

[0414] Based on the final determined sensing location authorization information, configure SF to enable the sensing service location that allows the request;

[0415] Based on the finally determined perception target configuration, SF enables the perception target to consent to the use of collected data for perception purposes.

[0416] Optionally, the device further includes:

[0417] The sending module is used to send first configuration information to the sensing entity. The first configuration information is used to indicate at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing location authorization information, the finally determined sensing time authorization information, and the finally determined sensing target.

[0418] Optionally, the apparatus further includes an acquisition module for:

[0419] Obtain second configuration information from SF, the second configuration information including the authorization information; or...

[0420] The Perception Service obtains the authorization information from the Policy Function (PF) based on the request.

[0421] Optionally, the acquisition module is further configured to perform at least one of the following:

[0422] If the requested sensing service is location-related, the sensing location authorization information is obtained from OAM or NRF, and the authorization information includes the sensing location authorization information.

[0423] If the requested sensing service is related to a user or user device, the user consent information is obtained from the UDM, and the authorization information includes the user consent information.

[0424] Optionally, the authorization response message further includes an access token, and the device further includes:

[0425] A generation module is configured to generate the access token, the access token comprising at least one of the following:

[0426] The AF identifier, the final determined perception service information, the final determined perception reporting type, the final determined perception location authorization information, the final determined perception time authorization information, the final determined perception target, and the final determined interoperability information.

[0427] Optionally, the device is applied to at least one of the following: SF, NRF, NEF.

[0428] The sensing service authorization device 500 provided in this application embodiment can implement all the processes of the above-described sensing service authorization method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0429] Please refer to Figure 6, which is a structural diagram of a configuration information receiving device provided in an embodiment of this application. As shown in Figure 6, the configuration information receiving device 600 includes:

[0430] The second receiving module 601 is configured to receive first configuration information sent by the first device, wherein the first configuration information is used to indicate at least one of the following:

[0431] The final determined perception service information is used to indicate the perception services that the AF does not allow and / or the perception services that the AF allows.

[0432] The final determined perception reporting type, which is used to indicate perception reporting types that the AF does not allow and / or perception reporting types that the AF allows;

[0433] The final determined perception time authorization information is used to indicate the time period during which perception services that do not allow AF requests are performed and / or the time period during which perception services that allow the requests are performed.

[0434] The final determined sensing location authorization information is used to indicate the location of the sensing service that does not allow the AF request and / or the location of the sensing service that allows the request.

[0435] The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to the collection of data for perception purposes, and the second perception target is used to indicate disagreement to the collection of data for perception purposes.

[0436] The configuration information receiving device 600 provided in this application embodiment can implement all the processes of the above configuration information receiving method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0437] As shown in Figure 7, this application embodiment also provides a communication device 700, including a processor 701 and a memory 702. The memory 702 stores programs or instructions that can run on the processor 701. For example, when the communication device 700 is a terminal, the program or instructions executed by the processor 701 implement the various steps of the above-described configuration information receiving method embodiment and achieve the same technical effect. When the communication device 700 is a network-side device, the program or instructions executed by the processor 701 implement the various steps of the above-described perception service authorization method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0438] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG4. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the configuration information receiving device shown in FIG6. Specifically, FIG8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0439] The terminal 800 includes, but is not limited to, at least some of the following components: radio frequency unit 801, network module 802, audio output unit 803, input unit 804, sensor 805, display unit 806, user input unit 807, interface unit 808, memory 809, and processor 810.

[0440] Those skilled in the art will understand that the terminal 800 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 810 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 8 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0441] It should be understood that, in this embodiment, the input unit 804 may include a graphics processor 8041 and a microphone 8042. The graphics processor 8041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0442] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 801 can transmit it to the processor 810 for processing; in addition, the radio frequency unit 801 can send uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0443] The memory 809 can be used to store software programs or instructions, as well as various data. The memory 809 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 809 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 809 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0444] Processor 810 may include one or more processing units; optionally, processor 810 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 810.

[0445] The radio frequency unit 801 is configured to receive first configuration information sent by the first device, wherein the first configuration information is configured to indicate at least one of the following:

[0446] The final determined perception service information is used to indicate the perception services that the AF does not allow and / or the perception services that the AF allows.

[0447] The final determined perception reporting type, which is used to indicate perception reporting types that the AF does not allow and / or perception reporting types that the AF allows;

[0448] The final determined perception time authorization information is used to indicate the time period during which perception services that do not allow AF requests are performed and / or the time period during which perception services that allow the requests are performed.

[0449] The final determined sensing location authorization information is used to indicate the location of the sensing service that does not allow the AF request and / or the location of the sensing service that allows the request.

[0450] The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to the collection of data for perception purposes, and the second perception target is used to indicate disagreement to the collection of data for perception purposes.

[0451] In this embodiment of the application, the terminal receives first configuration information sent by the first device, so that the first device can configure the terminal through the first configuration information, thereby better regulating the terminal's perception behavior.

[0452] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description in the foregoing method embodiments and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0453] Specifically, this application also provides a network-side device. As shown in FIG9, the network-side device 900 includes a processor 901, a network interface 902, and a memory 903. The network-side device may be the Sensing Service Authorization device shown in FIG5. The network interface 902 is, for example, a Common Public Radio Interface (CPRI).

[0454] Among them, network interface 902 is used to receive a first request message, the first request message including the identifier of AF and sensing service information, the sensing service information being used to indicate the requested sensing service;

[0455] The processor 901 is configured to determine, based on the first request message and authorization information, whether to provide the requested perception service to the AF; wherein the authorization information includes at least one of the following:

[0456] AF access authorization information, which indicates whether AF access is permitted;

[0457] Perception service authorization information, which is used to indicate whether the requested perception service is allowed to be provided to the AF;

[0458] Report type authorization information, which is used to indicate whether the perception result or perception data of the requested perception service is allowed to be provided to the AF;

[0459] Sensing time authorization information, which is used to indicate the time period during which the sensing service requested is allowed to be executed or the time period during which the sensing service requested is not allowed to be executed;

[0460] The location authorization information is used to indicate the location where the requested sensing service is allowed to be executed or the location where the requested sensing service is not allowed to be executed.

[0461] User consent information, which is used to indicate whether the sensing target agrees to have its data collected used for sensing purposes;

[0462] First interoperability information, which indicates that the sensing function SF allows interoperability with the AF.

[0463] In addition, the network-side device 900 of this application embodiment also includes: a program or instructions stored in a memory 903 and executable on a processor 901. The processor 901 calls the program or instructions in the memory 903 to execute the methods executed by each module shown in FIG5 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0464] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described perception service authorization method or configuration information receiving method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0465] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0466] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described perception service authorization method or configuration information receiving method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0467] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0468] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described sensing service authorization method or configuration information receiving method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0469] This application also provides a wireless communication system, including a terminal and a network-side device. The terminal can be used to perform the steps of the configuration information receiving method described above, and the network-side device can be used to perform the steps of the sensing service authorization method described above.

[0470] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0471] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0472] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for authorizing perceived services, comprising: The first device receives a first request message, which includes an identifier of the application function AF and sensing service information, wherein the sensing service information is used to indicate the requested sensing service. The first device determines whether to provide the requested sensing service to the AF based on the first request message and the authorization information; wherein the authorization information includes at least one of the following: AF access authorization information, which indicates whether AF access is permitted; Perception service authorization information, which is used to indicate whether the requested perception service is allowed to be provided to the AF; Report type authorization information, which is used to indicate whether the perception result or perception data of the requested perception service is allowed to be provided to the AF; Sensing time authorization information, which is used to indicate the time period during which the sensing service requested is allowed to be executed or the time period during which the sensing service requested is not allowed to be executed; The location authorization information is used to indicate the location where the requested sensing service is allowed to be executed or the location where the requested sensing service is not allowed to be executed. User consent information, which is used to indicate whether the sensing target agrees to have its data collected used for sensing purposes; First interoperability information, which indicates that the sensing function SF allows interoperability with the AF.

2. The method according to claim 1, wherein, The sensing service information is also used to indicate at least one of the following: the type of sensing report requested, the location of sensing requested, the time of sensing requested, the target of sensing requested, and the second interoperability information. The second interoperability information is used to indicate that the AF allows interoperability with the SF.

3. The method according to claim 2, wherein, The first device determines whether to provide the requested sensing service to the AF based on the first request message and authorization information, including at least one of the following: The first device determines whether to allow the AF access based on the AF access authorization information; The first device determines whether to allow the AF to be provided with the requested sensing service based on the sensing service authorization information; The first device determines whether to allow the AF to provide the requested perception reporting type based on the reporting type authorization information; The first device determines whether the requested sensing time or the current time is a time when the requested sensing service is permitted, based on the sensing time authorization information. The first device determines whether the requested sensing location is a location where the requested sensing service is permitted based on the sensing location authorization information. The first device determines whether the target of perception agrees to have its data collected for perception purposes based on the user consent information. The first device determines whether to allow interoperability with the AF based on the first interoperability information and the second interoperability information.

4. The method according to claim 2 or 3, wherein, The method further includes: If the first device determines, based on the first request message and authorization information, that it will not provide the requested sensing service to the AF, the first device rejects the first request message through an authorization rejection message; The authorization rejection message includes a rejection reason value, which includes at least one of the following: Unauthorized AF; Unauthorized sensing services; Unauthorized perception reporting type; Unauthorized perception of time; Unauthorized sensing location; Unauthorized perceived targets; Interoperability is not allowed.

5. The method according to claim 4, wherein, The first device determines, based on the first request message and authorization information, not to provide the requested sensing service to the AF, including at least one of the following: The first device determines that the AF access is not allowed based on the AF access authorization information; The first device determines, based on the perception service authorization information, that it is not allowed to provide all the requested perception services to the AF; The first device determines, based on the reporting type authorization information, that it is not allowed to provide the AF with the perception reporting type of the request; The first device determines, based on the sensing time authorization information, that the requested sensing time or the current time is not a time when the requested sensing service is permitted. The first device determines, based on the sensing location authorization information, that the requested sensing location is not a location where the requested sensing service is permitted. The first device determines, based on the user consent information, that none of the sensing targets agree to have their data collected for sensing purposes. The first device determines, based on the first interoperability information and / or the second interoperability information, that interoperability with the AF is not permitted.

6. The method according to any one of claims 2-5, wherein, The method further includes: If the first device determines, based on the first request message and authorization information, to provide the requested sensing service to the AF, the first device accepts the first request message through an authorization response message.

7. The method according to claim 6, wherein, The authorization response message includes at least one of the following: The finalized perception service information; The final determined perception reporting type; Finalized authorization information for perception time; Finalized location authorization information; The final determined perception target; The finalized interoperability information.

8. The method according to claim 7, wherein, The first device determines, based on the first request message and authorization information, to provide the requested sensing service to the AF, including at least one of the following: The first device determines whether to allow the AF to access based on the AF access authorization information; The first device determines, based on the perception service authorization information, that the requested perception service is a perception service permitted by the AF; or, the first device determines, based on the perception service authorization information, that the requested perception service includes a perception service not permitted by the AF or a perception service permitted by the AF. The first device determines, based on the reporting type authorization information, that the requested perception reporting type is a perception reporting type allowed by the AF; or, the first device determines, based on the reporting type authorization information, that the requested perception reporting type includes both perception reporting types not allowed by the AF and perception reporting types allowed by the AF. The first device determines the requested sensing time or the current time as a time when the requested sensing service is allowed based on the sensing time authorization information; or, the first device determines the requested sensing time or the current time as a time when the requested sensing service is not allowed based on the sensing time authorization information, including both the time when the requested sensing service is not allowed and the time when the requested sensing service is allowed. The first device determines the requested sensing location as a location where the requested sensing service is permitted based on the sensing location authorization information; or, the first device determines the requested sensing location as including both locations where the requested sensing service is not permitted and locations where the requested sensing service is permitted based on the sensing location authorization information. The first device determines, based on the user consent information, that all the sensing targets agree to have their data collected for sensing purposes, or, based on the user consent information, that the sensing targets include sensing targets that agree to have their data collected for sensing purposes and sensing targets that do not agree to have their data collected for sensing purposes. The first device determines that it is allowed to interoperate with the AF based on the first interoperability information and the second interoperability information.

9. The method according to claim 8, wherein, The authorization response message also satisfies at least one of the following: The final determined sensing service information is used to indicate the sensing services that the AF does not allow and / or the sensing services that the AF allows. The final determined perception reporting type is used to indicate the perception reporting types that the AF does not allow and / or the perception reporting types that the AF allows. The final determined perception time authorization information is used to indicate the time period during which the requested perception service is not allowed and / or the time period during which the requested perception service is allowed. The final determined sensing location authorization information is used to indicate the location where the requested sensing service is not allowed and / or the location where the requested sensing service is allowed. The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to have data collected for perception purposes, and the second perception target is used to indicate disagreement to have data collected for perception purposes. The finalized interoperability information is used to indicate information that allows interoperability and / or information that does not allow interoperability.

10. The method according to any one of claims 7-9, wherein, The first request message includes at least one of the following: the finally determined perception service information, the finally determined perception reporting type, the finally determined perception time authorization information, the finally determined perception location authorization information, and the finally determined perception target.

11. The method according to any one of claims 7-9, wherein, The first request message further includes an access token: the access token includes the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing time authorization information, the finally determined sensing location authorization information, the finally determined sensing target, and the finally determined interoperability information. The method further includes: The first device verifies the access token.

12. The method according to any one of claims 7-11, wherein, The method further includes: The first device performs at least one of the following: Configure SF to enable the perception services allowed by AF based on the finally determined perception service information; Based on the final perception reporting type, configure SF to enable the perception reporting types allowed by AF; Configure SF to enable the time period during which the requested sensing service is performed, based on the final determined sensing time authorization information. Based on the final determined sensing location authorization information, configure SF to enable the sensing service location that allows the request; Based on the finally determined perception target configuration, SF enables the perception target to consent to the use of collected data for perception purposes.

13. The method according to any one of claims 7-12, wherein, The method further includes: The first device sends first configuration information to the sensing entity, the first configuration information being used to indicate at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing location authorization information, the finally determined sensing time authorization information, and the finally determined sensing target.

14. The method according to any one of claims 1-13, wherein, The method further includes: The first device obtains second configuration information from SF, the second configuration information including the authorization information; or, The first device obtains the authorization information from the policy function PF based on the requested perception service.

15. The method according to claim 14, wherein, The first device obtains the authorization information from the PF according to the requested perception service, including at least one of the following: When the requested sensing service is location-related, the first device obtains the sensing location authorization information from Operations Management and Maintenance (OAM) or Network Storage Function (NRF), the authorization information including the sensing location authorization information; When the requested sensing service is related to a user or user device, the first device obtains the user consent information from the Unified Data Management Entity (UDM), and the authorization information includes the user consent information.

16. The method according to any one of claims 7-9, wherein, The authorization response message also includes an access token, and the method further includes: The first device generates the access token, the access token comprising at least one of the following: The AF identifier, the final determined perception service information, the final determined perception reporting type, the final determined perception location authorization information, the final determined perception time authorization information, the final determined perception target, and the final determined interoperability information.

17. The method according to any one of claims 1-16, wherein, The first device includes at least one of the following: SF, NRF, and Network Open Function (NEF).

18. A method for receiving configuration information, comprising: The sensing entity receives first configuration information sent by the first device, the first configuration information being used to indicate at least one of the following: The final determined perception service information is used to indicate the perception services that the AF does not allow and / or the perception services that the AF allows. The final determined perception reporting type, which is used to indicate perception reporting types that the AF does not allow and / or perception reporting types that the AF allows; The final determined perception time authorization information is used to indicate the time period during which perception services that do not allow AF requests are performed and / or the time period during which perception services that allow the requests are performed. The final determined sensing location authorization information is used to indicate the location of the sensing service that does not allow the AF request and / or the location of the sensing service that allows the request. The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to the collection of data for perception purposes, and the second perception target is used to indicate disagreement to the collection of data for perception purposes.

19. A sensing service authorization device, comprising: The first receiving module is configured to receive a first request message, the first request message including the identifier of AF and sensing service information, the sensing service information being used to indicate the requested sensing service; The determining module is configured to determine, based on the first request message and authorization information, whether to provide the requested perception service to the AF; wherein the authorization information includes at least one of the following: AF access authorization information, which indicates whether AF access is permitted; Perception service authorization information, which is used to indicate whether the requested perception service is allowed to be provided to the AF; Report type authorization information, which is used to indicate whether the perception result or perception data of the requested perception service is allowed to be provided to the AF; Sensing time authorization information, which is used to indicate the time period during which the sensing service requested is allowed to be executed or the time period during which the sensing service requested is not allowed to be executed; The location authorization information is used to indicate the location where the requested sensing service is allowed to be executed or the location where the requested sensing service is not allowed to be executed. User consent information, which is used to indicate whether the sensing target agrees to have its data collected used for sensing purposes; First interoperability information, which indicates that the sensing function SF allows interoperability with the AF.

20. The apparatus according to claim 19, wherein, The sensing service information is also used to indicate at least one of the following: the type of sensing report requested, the location of sensing requested, the time of sensing requested, the target of sensing requested, and the second interoperability information. The second interoperability information is used to indicate that the AF allows interoperability with the SF.

21. The apparatus according to claim 20, wherein, The determining module is also used for at least one of the following: Determine whether to allow AF access based on the AF access authorization information; Determine whether to allow the provision of the requested perception service to the AF based on the perception service authorization information; Determine whether to allow the AF to be provided with the perception reporting type of the request based on the reporting type authorization information; Based on the perception time authorization information, determine whether the perception time of the request or the current time is a time when the perception service of the request is permitted. Based on the sensing location authorization information, determine whether the requested sensing location is a location where the requested sensing service is permitted; Based on the user consent information, determine whether the target of perception agrees to have its data collected for perception purposes; Whether to allow interoperability with the AF is determined based on the first interoperability information and the second interoperability information.

22. The apparatus according to claim 20 or 21, wherein, The device further includes: The rejection module is used to reject the first request message by means of an authorization rejection message if it is determined, based on the first request message and authorization information, that the requested perception service will not be provided to the AF. The authorization rejection message includes a rejection reason value, which includes at least one of the following: Unauthorized AF; Unauthorized sensing services; Unauthorized perception reporting type; Unauthorized perception of time; Unauthorized sensing location; Unauthorized perceived targets; Interoperability is not allowed.

23. The apparatus according to any one of claims 20-22, wherein, The device further includes: The receiving module is configured to accept the first request message via an authorization response message when it is determined, based on the first request message and authorization information, that the requested perception service is to be provided to the AF.

24. The apparatus according to claim 23, wherein, The authorization response message includes at least one of the following: The finalized perception service information; The final determined perception reporting type; Finalized authorization information for perception time; Finalized location authorization information; The final determined perception target; The finalized interoperability information.

25. The apparatus according to claim 24, wherein, The device further includes: The sending module is used to send first configuration information to the sensing entity. The first configuration information is used to indicate at least one of the following: the finally determined sensing service information, the finally determined sensing reporting type, the finally determined sensing location authorization information, the finally determined sensing time authorization information, and the finally determined sensing target.

26. A configuration information receiving device, wherein, include: The second receiving module is configured to receive first configuration information sent by the first device, wherein the first configuration information is used to indicate at least one of the following: The final determined perception service information, wherein the final determined perception service is used to indicate the perception services that the AF does not allow and / or the perception services that the AF allows; The final determined perception reporting type, which is used to indicate perception reporting types that the AF does not allow and / or perception reporting types that the AF allows; The final determined perception time authorization information is used to indicate the time period during which perception services that do not allow AF requests are performed and / or the time period during which perception services that allow the requests are performed. The final determined sensing location authorization information is used to indicate the location of the sensing service that does not allow the AF request and / or the location of the sensing service that allows the request. The final determined perception target includes a first perception target and a second perception target. The first perception target is used to indicate consent to the collection of data for perception purposes, and the second perception target is used to indicate disagreement to the collection of data for perception purposes.

27. A network-side device, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the perception service authorization method as described in any one of claims 1-17.

28. A terminal, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the configuration information receiving method as described in claim 18.

29. A readable storage medium, wherein, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the perception service authorization method as described in any one of claims 1-17, or the steps of the configuration information receiving method as described in claim 18.

30. A computer program product, wherein, The computer program product is stored in a storage medium and is executed by at least one processor to implement the steps of the perception service authorization method as described in any one of claims 1-17, or to implement the steps of the configuration information receiving method as described in claim 18.