Processing method, communication device and storage medium

Abstract

The invention discloses a processing method, communication equipment and a storage medium. The processing method comprises the following steps: authenticating and / or authorizing a first request; through the technical scheme of the invention, an authentication processing mechanism and / or an authorization processing mechanism for services such as communication perception and / or AI / ML and / or calculation are / is defined.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a processing method, communication device, and storage medium. Background Technology

[0002] Currently, research on 6G services is gradually being carried out, such as studying the service processes of network equipment in communication sensing services and / or AI / ML services and / or computing services.

[0003] In the process of conceiving and implementing this application, the inventors discovered at least the following problems:

[0004] For services such as communication sensing and / or AI / ML and / or computing, the authentication and / or authorization mechanisms are not perfect. Specifically, there is currently no solution for how network devices should authenticate and / or authorize service requests initiated by sensing service consumers (such as AF (Application Function)).

[0005] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Summary of the Invention

[0006] The main purpose of this application is to provide a processing method, communication device and storage medium, which aims to clarify the authentication processing mechanism and / or authorization processing mechanism for communication sensing and / or AI / ML and / or computing services.

[0007] This application provides a processing method applicable to a first device (such as a gateway or NEF), comprising the following steps: S2: Authenticate and / or authorize the first request.

[0008] Optionally, the processing method further includes at least one of the following: The first request is a business-aware request; The first request was sent by the second device; Send the second request based on the first request; Send the first request to the third device; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

[0009] Optionally, the processing method further includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; The first request was sent by the second device via NEF; The first request was sent from the third device to the fifth device; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent to the fourth device; The third device performs the first process based on the first request.

[0010] Optionally, the processing method further includes at least one of the following: The second request is sent by NEF to the fourth device; The first request is sent from the third device to the fifth device via the service control function; The first request sent by the third device to the fifth device includes the sensing entity configuration; The fifth device executes the second process based on the first request; Executing either the first processing step or the second processing step constitutes the execution of the perceived business processing step; Receive the first response sent by the third device; Receive the second response sent by the fourth device; Send the first response to the second device.

[0011] Optionally, the processing method further includes at least one of the following: The first response is a business-aware response; The first response is sent from the fifth device to the third device; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

[0012] This application also provides a processing method applicable to a second device (such as an AF), comprising the following steps: S1: Send a first request to enable the first device to authenticate and / or authorize the first request.

[0013] Optionally, the processing method further includes at least one of the following: The first request is a business-aware request; The first device sends a second request based on the first request; The first request is sent from the first device to the third device; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

[0014] Optionally, the processing method further includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; The first request is sent to the first device via NEF; The first request was sent from the third device to the fifth device; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent from the first device to the fourth device; The third device performs the first process based on the first request.

[0015] Optionally, the processing method further includes at least one of the following: The second request is sent by NEF to the fourth device; The first request is sent from the third device to the fifth device via the service control function; The first request sent by the third device to the fifth device includes the sensing entity configuration; The fifth device executes the second process based on the first request; Executing either the first processing step or the second processing step constitutes the execution of the perceived business processing step; Receive the first response sent by the first device; The first device receives the second response sent by the fourth device.

[0016] Optionally, the processing method further includes at least one of the following: The first response is a business-aware response; The first response is sent from the third device to the first device; The first response is sent from the fifth device to the third device; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

[0017] This application provides a processing method applicable to a third device (such as an SF), comprising the following steps: S3: Perform first processing based on the first request, wherein the first request is authenticated and / or authorized by the first device.

[0018] Optionally, the processing method further includes at least one of the following: The first step is to perform the perception-based business processing. The first request is a business-aware request; The first request is sent by the first device; The first request is sent from the second device to the first device; The first device sends a second request based on the first request; Send the first request to the fifth device; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

[0019] Optionally, the processing method further includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first request is sent from the second device to the first device via NEF; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent from the first device to the fourth device.

[0020] Optionally, the processing method further includes at least one of the following: The second request is sent by NEF to the fourth device; The first request is sent from the third device to the fifth device via the service control function; The first request sent to the fifth device includes the sensing entity configuration; The fifth device executes the second process based on the first request; The second process is to perform the perception business processing; Receive the first response sent by the fifth device; Send a first response to the first device; The first device receives the second response sent by the fourth device; The first device sends a first response to the second device.

[0021] Optionally, the processing method further includes at least one of the following: The first response is a business-aware response; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

[0022] This application provides a processing method applicable to a fifth device (such as an SE), comprising the following steps: S4: Perform second processing based on the first request, wherein the first request is authenticated and / or authorized by the first device.

[0023] Optionally, the processing method further includes at least one of the following: The second process is to perform the perception business processing; The first request is a business-aware request; The first request is sent from the second device to the first device; The first request is sent from the first device to the third device; The first request was sent from the third device to the fifth device; The first device sends a second request based on the first request; The third device performs the first process based on the first request; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

[0024] Optionally, the processing method further includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first request is sent from the second device to the first device via NEF; The first request is sent from the third device to the fifth device via the service control function; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent from the first device to the fourth device.

[0025] Optionally, the processing method further includes at least one of the following: The second request is sent by NEF to the fourth device; The first request includes the configuration of the sensing entity; Send the first response to the third device; The third device sends a first response to the first device; The first device receives the second response sent by the fourth device; The first device sends a first response to the second device.

[0026] Optionally, the processing method further includes at least one of the following: The first response is a business-aware response; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

[0027] This application also provides a processing apparatus, the processing apparatus comprising: The first processing module is used to authenticate and / or authorize the first request.

[0028] This application also provides a processing apparatus, the processing apparatus comprising: The sending module is used to send a first request so that the first device can authenticate and / or authorize the first request.

[0029] This application also provides a processing apparatus, the processing apparatus comprising: The second processing module is used to perform first processing based on a first request, wherein the first request is authenticated and / or authorized by the first device.

[0030] This application also provides a processing apparatus, the processing apparatus comprising: The third processing module is used to perform second processing based on the first request, wherein the first request is authenticated and / or authorized by the first device.

[0031] This application also provides a communication device, including: a memory, a processor, and a processing program stored in the memory and executable on the processor, wherein the processing program, when executed by the processor, implements the steps of any of the processing methods described above.

[0032] The communication device in this application can be a first device (such as a gateway or NEF), a second device (such as an AF), a third device (such as an SF), a fifth device (such as an SE), or a chip (such as a SOC or a baseband chip with communication functions, etc.). The specific meaning needs to be clarified in the context.

[0033] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the processing methods described above.

[0034] In the technical solution of this application, the first device authenticates and / or authorizes the first request, and clarifies the authentication processing mechanism and / or authorization processing mechanism for communication sensing and / or AI / ML and / or computing services. Attached Figure Description

[0035] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0036] Figure 1 A schematic diagram of the hardware structure of a mobile terminal to implement the various embodiments of this application; Figure 2 A communication network system architecture diagram provided for an embodiment of this application; Figure 3 Another communication network system architecture diagram provided in this application embodiment; Figure 4 A schematic diagram of the hardware structure of a controller 140 provided in this application; Figure 5 A schematic diagram of the hardware structure of a network node 150 provided in this application; Figure 6 This is a schematic flowchart illustrating the processing method of the first embodiment of this application; Figure 7 This is a schematic diagram of a scenario flow of the processing method shown in the second embodiment of this application; Figure 8 This is a schematic diagram of a scenario flow of the processing method shown in the third embodiment of this application; Figure 9 This is a schematic flowchart illustrating the processing method of the fourth embodiment of this application; Figure 10This is a schematic flowchart illustrating the processing method of the fifth embodiment of this application; Figure 11 This is a schematic flowchart illustrating the processing method of the sixth embodiment of this application; Figure 12 This is a schematic diagram of the interaction flow of the first device, second device, third device, and fifth device in the processing method shown in the seventh embodiment of this application; Figure 13 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 1 ; Figure 14 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 2 ; Figure 15 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 3 ; Figure 16 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 4 ; Figure 17 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0037] The realization of the objectives, functional features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0038] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0039] 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, and / or, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0040] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, may be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used in this application, may be interpreted as inclusive, or mean any one or any combination thereof. For example, "including at least one of the following: A, B, C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Similarly, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Exceptions to this definition only occur when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0041] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0042] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0043] It should be noted that step designations such as S1 and S2 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the protection scope of this application.

[0044] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0045] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0046] The communication device in this application can be a first device (such as a gateway or NEF), a second device (such as an AF), a third device (such as an SF), a fifth device (such as an SE), or a chip (such as a SOC or a baseband chip with communication functions, etc.). The specific meaning needs to be clarified according to the context.

[0047] Terminal devices can be implemented in various forms. For example, the terminal devices described in this application may include smart terminal devices such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0048] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to the embodiments of this application can also be applied to fixed-type terminal devices.

[0049] Please see Figure 1 This is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application. The mobile terminal 100 may include: a radio frequency unit 101, a WiFi module 102, an audio output unit 103, an A / V (audio / video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that... Figure 1 The mobile terminal structure shown does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0050] The following is combined Figure 1 A detailed introduction to each component of the mobile terminal: The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. And / or, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G, and 6G.

[0051] WiFi is a short-range wireless transmission technology. Mobile terminals using the WiFi module 102 can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 1 WiFi module 102 is shown, but it is understood that it is not a necessary component of a mobile terminal and can be omitted as needed without changing the nature of the invention.

[0052] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, or other modes. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0053] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0054] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0055] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0056] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Optionally, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as touch screen, can collect touch operations on or near the user (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include two parts: touch detection device and touch controller. Optionally, touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to touch controller; touch controller receives touch information from touch detection device, converts it into touch point coordinates, and sends it to processor 110, and can receive and execute commands from processor 110. And / or, touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being specifically limited here.

[0057] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 based on the type of touch event. Although in Figure 1 In this embodiment, the touch panel 1071 and the display panel 1061 are two independent components to realize the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.

[0058] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more components within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.

[0059] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). And / or, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0060] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of the mobile terminal. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.

[0061] The mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components. Preferably, the power supply 111 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0062] although Figure 1 As not shown, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0063] To facilitate understanding of the embodiments of this application, the communication network system on which the mobile terminal of this application is based is described below.

[0064] Please see Figure 2 , Figure 2 This application provides a communication network system architecture diagram. The communication network system is a NR (New Radio) system based on general mobile communication technology, which is at least applied to 5G systems. The communication network system architecture includes 5GC (5G core network) and NG-RAN (5G radio access network). 5GC includes AMF (Access and Mobility Management Function) and UPF (User Plane Function Entity); NG-RAN includes gNB, ng-gNB, etc.

[0065] Optionally, the AMF is used to perform registration, connection, reachability, and mobility management. It provides a session management message transmission channel for the UE (User Equipment) and SMF, and provides authentication and authorization functions for user access. It is the core network control plane access point for the UE and the radio network. The UPF is used for packet routing and forwarding, policy enforcement, traffic reporting, QoS processing, etc. The gNB is a key unit in the 5G (NR) wireless communication system. As a base station in the 5G Radio Access Network (RAN), it is responsible for establishing wireless connections with the UE and for data transmission between the UE and the core network.

[0066] Optionally, the communication network system architecture may also include the following service-based interfaces: Xn interface and NG interface, where Xn is the interface between gNBs (ng-gNBs); and NG is the interface between gNBs (ng-gNBs) and AMF and / or UPF.

[0067] Although the above description uses LTE and NR systems as examples, those skilled in the art should know that this application is not only applicable to LTE and NR systems, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5GA, and future new network systems (such as 6G), etc., without limitation here.

[0068] Please see Figure 3 , Figure 3 This application provides another communication network system architecture diagram. The communication network system is a NR (New Radio) system based on general mobile communication technology, which is at least applied to 5G systems. The network functions (NF) of this communication network system architecture may include: AUSF (Authentication Service Function), AMF (Access and Mobility Management Function), DN (Data Network) (e.g., operator services, Internet access, or third-party services), NEF (Network Exposure Function), NRF (Network Repository Function), NSACF (Network Slice Admission Control Function), NSSAAF (Network Slice-Specific and SNPN Authentication and Authorization Function), NSSF (Network Slice Selection Function), PCF (Policy Control Function), SMF (Session Management Function), UDM (Unified Data Management), UPF (User Plane Function), AF (Application Function), UE (User Equipment), (R)AN (Radio) Access Network, and EASDF (Edge Application Server Discovery Function).

[0069] Optionally, the communication network system architecture may also include the following network entities: SCP (Serving Communication Agent) and multiple interfaces. Specifically, interface N1 is the interface between the UE and AMF, N2 is the interface between the RAN and AMF, N3 is the interface between the RAN and UPF, N4 is the interface between the UPF and SMF, N6 is the interface between the UPF and DN, and N9 is the interface between UPFs.

[0070] Optionally, the communication network system architecture may further include the following service-based interfaces: Namf, Nsmf, Nnef, Npcf, Nudm, Naf, Nnrf, Nnsacf, Nnssf, Nnssaaf, Nausf, Neasdf, and Nupf, wherein Namf is the service-based interface presented by AMF, Nsmf is the service-based interface presented by SMF, Nnef is the service-based interface presented by NEF, Npcf is the service-based interface presented by PCF, Nudm is the service-based interface presented by UDM, Naf is the service-based interface presented by AF, Nnrf is the service-based interface presented by NRF, Nnsacf is the service-based interface presented by NSACF, Nnssf is the service-based interface presented by NSSF, Nnssaaf is the service-based interface presented by NSSAAF, Nausf is the service-based interface presented by AUSF, Neasdf is the service-based interface presented by EASDF, and Nupf is the service-based interface presented by UPF.

[0071] Although the above description uses LTE and NR systems as examples, those skilled in the art should know that this application is not only applicable to LTE and NR systems, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5GA, and future new network systems (such as 6G), etc., without limitation here.

[0072] Figure 4 This is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0073] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0074] Figure 5 This application provides a schematic diagram of the hardware structure of a network node 150. The network node 150 includes a memory 1501 and a processor 1502. The memory 1501 is used to store program instructions, and the processor 1502 is used to call the program instructions in the memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0075] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0076] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0077] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk, SSD), etc.

[0078] Based on the above-described mobile terminal hardware structure and communication network system, various embodiments of this application are proposed.

[0079] Technical terms used in this embodiment: 5GC: 5G Core network; AAA: Authentication, Authorization, and Accounting; SBAAF: Service-Based Authentication and Authorization Function (SBAAF) is a network element that provides authentication and authorization functions based on business requirements. ADRF: Analytics Data Repository Function; AF: Application Function; AMF; Access and Mobility Management Function. AUSF: Authentication Server Function; DN: Data Network; EAP: Extended Authentication Protocol; GPSI: Generic Public Subscription Identifier; NEF: Network Exposure Function. NF: Network Function; NR: New Radio; NRF: Network Repository Function; NWDAF: Network Data Analytics Function; OTT: Over The Top; PCF: Policy Control Function; PDU: Protocol Data Unit; (R)AN: (Radio) Access Network; SMF: Session Management Function; UDM: Unified Data Management, a network element for unified data management; UE: User Equipment, terminal equipment; UPF: User Plane Function; NG-RAN: 5G Radio Access Network; SENF: Sensing Function; GMSENC: Gateway Mobile Sensing Centre; GAD: Universal Geographical Area Description; SUPI: SUbscription Permanent Identifier; SE: Sensing Entity; SCF: Sensing Control Function; SPF: Sensing Processing Function; SF: Sensing Function; SCF: Sensing Control Function; SPF: Sensing Processing Function.

[0080] First Embodiment Reference Figure 6 , Figure 6 This is a flowchart illustrating the processing method of the first embodiment of this application. The processing method of this embodiment can be applied to a first device (such as a gateway or NEF), including step S2: Step S2: The first device authenticates and / or authorizes the first request.

[0081] This embodiment takes into account that the authentication and / or authorization mechanisms for services such as communication sensing and / or AI / ML and / or computing are not perfect. Specifically, there is currently no solution for how network devices should authenticate and / or authorize service requests initiated by sensing service consumers (such as AF).

[0082] Therefore, this embodiment proposes a technical solution in which the first device authenticates and / or authorizes the first request, and can clearly define the authentication processing mechanism and / or authorization processing mechanism for services such as communication sensing and / or AI / ML and / or computing.

[0083] Optionally, the first request is sent from the second device to the first device.

[0084] Optionally, the first device is a gateway or NEF.

[0085] Optionally, the second device is a sensing service consumer (such as AF).

[0086] Optionally, the second device sends a first request based on the needs of the sensing service.

[0087] Optionally, for an untrusted AF, the first request is sent to the gateway by the second device via NEF; alternatively, for a trusted AF, the first request can be sent directly to the gateway.

[0088] Optionally, the first request is a business awareness request.

[0089] Optionally, the first request may include at least one of the following: sensing service type, target sensing service area, sensing report conditions, sensing time conditions, sensing service QoS, required sensing data, consumer address information for receiving sensing data, and terminal device identifier.

[0090] Optionally, if the sensing is related to a terminal device, the sensing service request may include the terminal device identifier.

[0091] Optionally, the terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device.

[0092] Optionally, the first device receives the first request.

[0093] Optionally, the first device authenticates and / or authorizes the first request.

[0094] Optionally, if the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of the perceived failure.

[0095] Optionally, if the first device successfully authenticates and / or authorizes the first request, the first device sends the first request to the third device to enable the third device to perform sensing service processing. Optionally, the first device receives the first response sent by the third device. Optionally, the first response is a sensing service response.

[0096] Optionally, the third device is SF.

[0097] Optionally, if the first request includes a terminal device identifier, the first device sends a second request based on the first request.

[0098] Optionally, the second request may be a request for re-authentication and / or re-authorization of the perceived service.

[0099] Optionally, the second request is sent from the first device to the fourth device.

[0100] Optionally, the second request is sent by NEF to the fourth device.

[0101] Optionally, the fourth device is a UDM.

[0102] Optionally, if the fourth device receives a second request from the first device, the fourth device re-authenticates and / or re-authorizes the sensing service. Optionally, the fourth device sends a second response to the first device or NEF.

[0103] Optionally, the second response is a re-authentication and / or re-authorization response for the perceived service.

[0104] Optionally, the second response includes the result of re-authentication and / or re-authorization of the perceived service, i.e., whether the re-authentication and / or re-authorization was successful or failed.

[0105] Optionally, the first device receives a second response sent by the fourth device.

[0106] Optionally, if the second response includes the result of failure to re-authenticate and / or re-authorize the sensing service, i.e., the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of sensing failure.

[0107] Optionally, if the second response includes a result of successful re-authentication and / or re-authorization of the sensing service, i.e., the first device successfully authenticates and / or authorizes the first request, then the first device sends the first request to the third device.

[0108] Optionally, the first request is sent by the second device to the third device via NEF.

[0109] Optionally, the third device performs the first process based on the first request.

[0110] Optionally, the third device performs the first processing, which is the third device performing sensing service processing.

[0111] Optionally, the third device performing the first processing is the third device coordinating with the fifth device to perform sensing service processing.

[0112] Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0113] Optionally, the third device sends the first request to the fifth device.

[0114] Optionally, the first request may be sent by the third device to the fifth device via a service control function.

[0115] Optionally, the first request sent by the third device to the fifth device includes the perception entity configuration.

[0116] Optionally, the fifth device is an SE.

[0117] Optionally, the fifth device sends a first response to the third device based on the first request.

[0118] Optionally, the first response includes at least one of sensing the result of the business, sensing success, and sensing failure.

[0119] Optionally, the fifth device performs the second processing based on the first request.

[0120] Optionally, the fifth device performs the second processing, which is the fifth device performing sensing service processing.

[0121] Optionally, the fifth device performing the second processing is the fifth device coordinating with the third device to perform sensing service processing. Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0122] Optionally, after the third device performs the sensing service processing, it sends a first response to the first device.

[0123] Optionally, the first device receives a first response sent by the third device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0124] Optionally, the first device sends a first response to the second device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0125] Through the technical solution of this embodiment, the first device authenticates and / or authorizes the first request, thus clarifying the authentication and / or authorization processing mechanisms for services such as communication sensing and / or AI / ML and / or computing.

[0126] Second Embodiment Based on the first embodiment of this application, a second embodiment of this application is proposed, which further discloses a processing method for authenticating and / or authorizing requests for perceived business services.

[0127] This embodiment proposes a technical solution in which the first device authenticates and / or authorizes the first request, and can clearly define the authentication processing mechanism and / or authorization processing mechanism for communication sensing services.

[0128] Optionally, the first request is sent from the second device to the first device.

[0129] Optionally, the first device is a gateway or NEF.

[0130] Optionally, the second device is a sensing service consumer (such as AF).

[0131] Optionally, the second device sends the first request to the gateway or NEF.

[0132] Optionally, for an untrusted AF, the first request is sent to the gateway by the second device via NEF; alternatively, for a trusted AF, the first request can be sent directly to the gateway.

[0133] Optionally, the first request is a business awareness request.

[0134] Optionally, the first request may include at least one of the following: sensing service type, target sensing service area, sensing report conditions, sensing time conditions, sensing service QoS, required sensing data, consumer address information for receiving sensing data, and terminal device identifier.

[0135] Optionally, if the sensing is related to a terminal device, the sensing service request may include the terminal device identifier.

[0136] Optionally, the terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device.

[0137] Optionally, the first device receives the first request.

[0138] Optionally, the first device authenticates and / or authorizes the first request.

[0139] Optionally, if the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of the perceived failure.

[0140] Optionally, if the first device successfully authenticates and / or authorizes the first request, the first device sends the first request to the third device so that the third device can perform the perception service processing.

[0141] Optionally, if the first request includes a terminal device identifier, the first device sends a second request to the fourth device based on the first request, so that the fourth device can re-authenticate and / or re-authorize the sensing service.

[0142] Optionally, such as Figure 7 As shown, the system architecture for authenticating and / or authorizing sensing service requests in this embodiment includes: a first device, a second device, a third device, a fourth device, and a fifth device.

[0143] Optionally, taking the first device as a gateway or NEF, the second device as a sensing service consumer (such as AF), the third device as SF, the fourth device as UDM, and the fifth device as SE as an example, the overall process of authenticating and / or authorizing sensing service requests in this embodiment may include steps 1 to 9: Step 1: The AF sends a sensing service request to the gateway or NEF; Optionally, for untrusted AFs, awareness service requests are sent from the AF to the gateway via NEF.

[0144] Optionally, for trusted AFs, the AF can directly send the sensing service request to the gateway.

[0145] Optionally, the sensing service request includes at least one of the following: sensing service type, target sensing service area, sensing report conditions, sensing time conditions, sensing service QoS, required sensing data, consumer address information for receiving sensing data, and terminal device identifier.

[0146] Optionally, the terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device.

[0147] Step 2: The gateway or NEF authenticates and authorizes the sensed service request; Optionally, if the gateway or NEF fails to authenticate and / or authorize the sensing service request, the gateway or NEF sends a sensing service response to the AF, which carries the result of the sensing failure.

[0148] Optionally, if the gateway or NEF successfully authenticates and / or authorizes the sensing service request, the gateway or NEF sends the sensing service request to the SF so that the SF can perform sensing service processing.

[0149] Step 3a: The gateway or NEF sends a re-authentication and / or re-authorization request for the sensing service; Optionally, if the sensing service request includes a terminal device identifier, the gateway or NEF sends a re-authentication and / or re-authorization request for the sensing service to the UDM based on the sensing service request, so that the UDM can re-authenticate and / or re-authorize the sensing service.

[0150] Step 3b: UDM sends a re-authentication and / or re-authorization response for the sensing service; Optionally, after receiving a re-authentication and / or re-authorization request for the sensing service from the gateway or NEF, the UDM performs re-authentication and / or re-authorization for the sensing service.

[0151] Optionally, the UDM sends a re-authentication and / or re-authorization response for the sensed service to the gateway or NEF.

[0152] Optionally, if the UDM successfully re-authenticates and / or re-authorizes the sensing service, the re-authentication and / or re-authorization response for the sensing service includes the terminal identifier, service type, and the result of successful re-authentication and / or re-authorization.

[0153] Step 4: The gateway or NEF sends a sensing service request to the SF; Optionally, if the re-authentication and / or re-authorization response to the sensing service includes a result of successful re-authentication and / or re-authorization of the sensing service, i.e., the gateway or NEF successfully authenticates and / or authorizes the sensing service request, then the gateway or NEF sends the sensing service request to the SF.

[0154] Step 5: SF sends a service request to SE; Optionally, after receiving the sensing service request, the SF sends the sensing service request to the SE.

[0155] Optionally, the awareness service request is sent by the SF to the SE through the service control function.

[0156] Optionally, the perception service request sent by the SF to the SE includes the perception entity configuration.

[0157] Step 6: SE sends a sensing service response to SF; Optionally, the SE sends a sensing service response to the SF based on the received sensing service request.

[0158] Optionally, the perceived service response includes at least one of perceived service result, perceived success, and perceived failure.

[0159] Step 7: SE and SF perform awareness service processing; Optionally, the SE device collaborates with the SF to perform sensing service processing.

[0160] Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0161] Step 8: SF sends a sensing service response to the gateway or NEF; Optionally, the first response includes the result of sensing the business and / or the result of sensing successful authentication.

[0162] Step 9: The gateway or NEF sends a sensing service response to the AF (authentication successful).

[0163] Optionally, the perceived service response includes the result of the perceived service and / or the result of successful perceived authentication.

[0164] Through the technical solution of this embodiment, the first device authenticates and / or authorizes the first request. If the first request contains a terminal device identifier, the first device sends a second request to the fourth device based on the first request, so that the fourth device re-authenticates and / or re-authorizes the sensing service. This clarifies the authentication processing mechanism and / or authorization processing mechanism for the communication sensing service.

[0165] Third Embodiment Based on any of the above embodiments of this application, a third embodiment of this application is proposed, which further discloses a processing method for authenticating and / or authorizing requests for perceived business services.

[0166] This embodiment proposes a technical solution in which the first device authenticates and / or authorizes the first request, and can clearly define the authentication processing mechanism and / or authorization processing mechanism for communication sensing services.

[0167] Optionally, the first request is sent from the second device to the first device.

[0168] Optionally, the first device is a gateway or NEF.

[0169] Optionally, the second device is a sensing service consumer (such as AF).

[0170] Optionally, the second device sends the first request to the gateway or NEF.

[0171] Optionally, for an untrusted AF, the first request is sent to the gateway by the second device via NEF; alternatively, for a trusted AF, the first request can be sent directly to the gateway.

[0172] Optionally, the first request is a business awareness request.

[0173] Optionally, the first request may include at least one of the following: sensing service type, target sensing service area, sensing report conditions, sensing time conditions, sensing service QoS, required sensing data, consumer address information for receiving sensing data, and terminal device identifier.

[0174] Optionally, if the sensing is related to a terminal device, the sensing service request may include the terminal device identifier.

[0175] Optionally, the terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device.

[0176] Optionally, the first device receives the first request.

[0177] Optionally, the first device authenticates and / or authorizes the first request.

[0178] Optionally, if the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of the perceived failure.

[0179] Optionally, if the first device successfully authenticates and / or authorizes the first request, the first device sends the first request to the third device so that the third device can perform the perception service processing.

[0180] Optionally, if the first request includes a terminal device identifier, the first device sends a second request to the fourth device based on the first request, so that the fourth device can re-authenticate and / or re-authorize the sensing service.

[0181] Optionally, such as Figure 8 As shown, the system architecture for authenticating and / or authorizing sensing service requests in this embodiment includes: a first device, a second device, a third device, a fourth device, and a fifth device.

[0182] Optionally, taking the first device as a gateway or NEF, the second device as a sensing service consumer (such as AF), the third device as SF, the fourth device as UDM, and the fifth device as SE as an example, the overall process of authenticating and / or authorizing sensing service requests in this embodiment may include steps 1 to 3, and step 9: Step 1: The AF sends a sensing service request to the gateway or NEF; Optionally, for untrusted AFs, awareness service requests are sent from the AF to the gateway via NEF.

[0183] Optionally, for trusted AFs, the AF can directly send the sensing service request to the gateway.

[0184] Optionally, the sensing service request includes at least one of the following: sensing service type, target sensing service area, sensing report conditions, sensing time conditions, sensing service QoS, required sensing data, consumer address information for receiving sensing data, and terminal device identifier.

[0185] Optionally, the terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device.

[0186] Step 2: The gateway or NEF authenticates and authorizes the sensed service request; Optionally, if the gateway or NEF fails to authenticate and / or authorize the sensing service request, the gateway or NEF sends a sensing service response to the AF, which carries the result of the sensing failure.

[0187] Optionally, if the gateway or NEF successfully authenticates and / or authorizes the sensing service request, the gateway or NEF sends the sensing service request to the SF so that the SF can perform sensing service processing.

[0188] Step 3a: The gateway or NEF sends a re-authentication and / or re-authorization request for the sensing service; Optionally, if the sensing service request includes a terminal device identifier, the gateway or NEF sends a re-authentication and / or re-authorization request for the sensing service to the UDM based on the sensing service request, so that the UDM can re-authenticate and / or re-authorize the sensing service.

[0189] Step 3b: UDM sends a re-authentication and / or re-authorization response for the sensing service; Optionally, after receiving a re-authentication and / or re-authorization request for the sensing service from the gateway or NEF, the UDM performs re-authentication and / or re-authorization for the sensing service.

[0190] Optionally, the UDM sends a re-authentication and / or re-authorization response for the sensed service to the gateway or NEF.

[0191] Optionally, if the UDM fails to re-authenticate and / or re-authorize the sensed service, the re-authentication and / or re-authorization response for the sensed service includes the terminal identifier, service type, and the result of the re-authentication and / or re-authorization failure.

[0192] Step 9: The gateway or NEF sends a sensing service response (authentication failed) to the AF.

[0193] Optionally, if the re-authentication and / or re-authorization response to the sensing service includes the result of the re-authentication and / or re-authorization failure of the sensing service, i.e. the gateway or NEF fails to authenticate and / or authorize the sensing service request, then the gateway or NEF sends a sensing service response to the AF. Optionally, the sensing service response includes the result of the sensing service and / or the result of the sensing authentication failure.

[0194] Through the technical solution of this embodiment, the first device authenticates and / or authorizes the first request. If the first request contains a terminal device identifier, the first device sends a second request to the fourth device based on the first request, so that the fourth device re-authenticates and / or re-authorizes the sensing service. This clarifies the authentication processing mechanism and / or authorization processing mechanism for the communication sensing service.

[0195] Fourth embodiment Reference Figure 9 , Figure 9 This is a flowchart illustrating the processing method of the fourth embodiment of this application. The processing method of this embodiment can be applied to a second device (such as an AF), and includes step S1: Step S1: The second device sends a first request to enable the first device to authenticate and / or authorize the first request.

[0196] This embodiment proposes a technical solution in which the first device authenticates and / or authorizes the first request, and can clearly define the authentication processing mechanism and / or authorization processing mechanism for services such as communication sensing and / or AI / ML and / or computing.

[0197] Optionally, the first request is sent from the second device to the first device.

[0198] Optionally, the first device is a gateway or NEF.

[0199] Optionally, the second device is a sensing service consumer (such as AF).

[0200] Optionally, the second device sends the first request.

[0201] Optionally, for an untrusted AF, the first request is sent to the gateway by the second device via NEF; alternatively, for a trusted AF, the first request can be sent directly to the gateway.

[0202] Optionally, the first request is a business awareness request.

[0203] Optionally, the first request may include at least one of the following: sensing service type, target sensing service area, sensing report conditions, sensing time conditions, sensing service QoS, required sensing data, consumer address information for receiving sensing data, and terminal device identifier.

[0204] Optionally, if the sensing is related to a terminal device, the sensing service request may include the terminal device identifier.

[0205] Optionally, the terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device.

[0206] Optionally, the first device receives the first request.

[0207] Optionally, the first device authenticates and / or authorizes the first request.

[0208] Optionally, if the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of the perceived failure.

[0209] Optionally, if the first device successfully authenticates and / or authorizes the first request, the first device sends the first request to the third device to enable the third device to perform sensing service processing. Optionally, the first device receives the first response sent by the third device. Optionally, the first response is a sensing service response.

[0210] Optionally, the third device is SF.

[0211] Optionally, if the first request includes a terminal device identifier, the first device sends a second request based on the first request.

[0212] Optionally, the second request may be a request for re-authentication and / or re-authorization of the perceived service.

[0213] Optionally, the second request is sent from the first device to the fourth device.

[0214] Optionally, the second request is sent by NEF to the fourth device.

[0215] Optionally, the fourth device is a UDM.

[0216] Optionally, if the fourth device receives a second request from the first device, the fourth device re-authenticates and / or re-authorizes the sensing service. Optionally, the fourth device sends a second response to the first device or NEF.

[0217] Optionally, the second response is a re-authentication and / or re-authorization response for the perceived service.

[0218] Optionally, the second response includes the result of re-authentication and / or re-authorization of the perceived service, i.e., whether the re-authentication and / or re-authorization was successful or failed.

[0219] Optionally, the first device receives a second response sent by the fourth device.

[0220] Optionally, if the second response includes the result of failure to re-authenticate and / or re-authorize the sensing service, i.e., the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of sensing failure.

[0221] Optionally, if the second response includes a result of successful re-authentication and / or re-authorization of the sensing service, i.e., the first device successfully authenticates and / or authorizes the first request, then the first device sends the first request to the third device.

[0222] Optionally, the first request is sent by the second device to the third device via NEF.

[0223] Optionally, the third device performs the first process based on the first request.

[0224] Optionally, the third device performs the first processing, which is the third device performing sensing service processing.

[0225] Optionally, the third device performing the first processing is the third device coordinating with the fifth device to perform sensing service processing.

[0226] Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0227] Optionally, the third device sends the first request to the fifth device.

[0228] Optionally, the first request may be sent by the third device to the fifth device via a service control function.

[0229] Optionally, the first request sent by the third device to the fifth device includes the perception entity configuration.

[0230] Optionally, the fifth device is an SE.

[0231] Optionally, the fifth device sends a first response to the third device based on the first request.

[0232] Optionally, the first response includes at least one of sensing the result of the business, sensing success, and sensing failure.

[0233] Optionally, the fifth device performs the second processing based on the first request.

[0234] Optionally, the fifth device performs the second processing, which is the fifth device performing sensing service processing.

[0235] Optionally, the fifth device performing the second processing is the fifth device coordinating with the third device to perform sensing service processing. Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0236] Optionally, after the third device performs the sensing service processing, it sends a first response to the first device.

[0237] Optionally, the first device receives a first response sent by the third device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0238] Optionally, the first device sends a first response to the second device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0239] Through the technical solution of this embodiment, the second device sends a first request so that the first device can authenticate and / or authorize the first request, which can clearly define the authentication processing mechanism and / or authorization processing mechanism for services such as communication sensing and / or AI / ML and / or computing.

[0240] Fifth embodiment Reference Figure 10 , Figure 10 This is a flowchart illustrating the processing method of the fifth embodiment of this application. The processing method of this embodiment can be applied to a third device (such as an SF), including step S3: Step S3: The third device performs the first process based on the first request, wherein the first request is authenticated and / or authorized by the first device.

[0241] This embodiment proposes a technical solution whereby a third device performs a first process based on a first request. The first request is authenticated and / or authorized by the first device, and the authentication and / or authorization processing mechanisms for communication sensing and / or AI / ML and / or computing services can be clearly defined.

[0242] Optionally, the first request is sent from the first device to the third device.

[0243] Optionally, the first request is sent from the second device to the first device.

[0244] Optionally, the first device is a gateway or NEF.

[0245] Optionally, the second device is a sensing service consumer (such as AF).

[0246] Optionally, the third device is SF.

[0247] Optionally, the second device sends a first request based on the needs of the sensing service.

[0248] Optionally, for an untrusted AF, the first request is sent to the gateway by the second device via NEF; alternatively, for a trusted AF, the first request can be sent directly to the gateway.

[0249] Optionally, the first request is a business awareness request.

[0250] Optionally, the first request may include at least one of the following: sensing service type, target sensing service area, sensing report conditions, sensing time conditions, sensing service QoS, required sensing data, consumer address information for receiving sensing data, and terminal device identifier.

[0251] Optionally, if the sensing is related to a terminal device, the sensing service request may include the terminal device identifier.

[0252] Optionally, the terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device.

[0253] Optionally, the first device receives the first request.

[0254] Optionally, the first device authenticates and / or authorizes the first request.

[0255] Optionally, if the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of the perceived failure.

[0256] Optionally, if the first device successfully authenticates and / or authorizes the first request, the first device sends the first request to the third device to enable the third device to perform sensing service processing. Optionally, the first device receives the first response sent by the third device. Optionally, the first response is a sensing service response.

[0257] Optionally, if the first request includes a terminal device identifier, the first device sends a second request based on the first request.

[0258] Optionally, the second request may be a request for re-authentication and / or re-authorization of the perceived service.

[0259] Optionally, the second request is sent from the first device to the fourth device.

[0260] Optionally, the second request is sent by NEF to the fourth device.

[0261] Optionally, the fourth device is a UDM.

[0262] Optionally, if the fourth device receives a second request from the first device, the fourth device re-authenticates and / or re-authorizes the sensing service. Optionally, the fourth device sends a second response to the first device or NEF.

[0263] Optionally, the second response is a re-authentication and / or re-authorization response for the perceived service.

[0264] Optionally, the second response includes the result of re-authentication and / or re-authorization of the perceived service, i.e., whether the re-authentication and / or re-authorization was successful or failed.

[0265] Optionally, the first device receives a second response sent by the fourth device.

[0266] Optionally, if the second response includes the result of failure to re-authenticate and / or re-authorize the sensing service, i.e., the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of sensing failure.

[0267] Optionally, if the second response includes a result of successful re-authentication and / or re-authorization of the sensing service, i.e., the first device successfully authenticates and / or authorizes the first request, then the first device sends the first request to the third device.

[0268] Optionally, the first request is sent by the second device to the third device via NEF.

[0269] Optionally, the third device performs the first process based on the first request.

[0270] Optionally, the third device performs the first processing, which is the third device performing sensing service processing.

[0271] Optionally, the third device performing the first processing is the third device coordinating with the fifth device to perform sensing service processing.

[0272] Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0273] Optionally, the third device sends the first request to the fifth device.

[0274] Optionally, the first request may be sent by the third device to the fifth device via a service control function.

[0275] Optionally, the first request sent by the third device to the fifth device includes the perception entity configuration.

[0276] Optionally, the fifth device is an SE.

[0277] Optionally, the fifth device sends a first response to the third device based on the first request.

[0278] Optionally, the first response includes at least one of sensing the result of the business, sensing success, and sensing failure.

[0279] Optionally, the fifth device performs the second processing based on the first request.

[0280] Optionally, the fifth device performs the second processing, which is the fifth device performing sensing service processing.

[0281] Optionally, the fifth device performing the second processing is the fifth device coordinating with the third device to perform sensing service processing. Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0282] Optionally, after the third device performs the sensing service processing, it sends a first response to the first device.

[0283] Optionally, the first device receives a first response sent by the third device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0284] Optionally, the first device sends a first response to the second device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0285] Through the technical solution of this embodiment, the third device performs the first process based on the first request. The first request is authenticated and / or authorized by the first device, which can clearly define the authentication processing mechanism and / or authorization processing mechanism for communication sensing and / or AI / ML and / or computing services.

[0286] Sixth Embodiment Reference Figure 11 , Figure 11 This is a flowchart illustrating the processing method of the sixth embodiment of this application. The processing method of this embodiment can be applied to a fifth device (such as an SE), including step S4: Step S4: The fifth device performs the second processing based on the first request, wherein the first request is authenticated and / or authorized by the first device.

[0287] This embodiment proposes a technical solution whereby the fifth device performs the second processing based on the first request. The first request is authenticated and / or authorized by the first device, and the authentication and / or authorization processing mechanisms for communication sensing and / or AI / ML and / or computing services can be clearly defined.

[0288] Optionally, the first request is sent from the second device to the first device.

[0289] Optionally, the first request is sent from the first device to the third device.

[0290] Optionally, the first request may be sent from the third device to the fifth device.

[0291] Optionally, the first device is a gateway or NEF.

[0292] Optionally, the second device is a sensing service consumer (such as AF).

[0293] Optionally, the third device is SF.

[0294] Optionally, the second device sends a first request based on the needs of the sensing service.

[0295] Optionally, for an untrusted AF, the first request is sent to the gateway by the second device via NEF; alternatively, for a trusted AF, the first request can be sent directly to the gateway.

[0296] Optionally, the first request is a business awareness request.

[0297] Optionally, the first request may include at least one of the following: sensing service type, target sensing service area, sensing report conditions, sensing time conditions, sensing service QoS, required sensing data, consumer address information for receiving sensing data, and terminal device identifier.

[0298] Optionally, if the sensing is related to a terminal device, the sensing service request may include the terminal device identifier.

[0299] Optionally, the terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device.

[0300] Optionally, the first device receives the first request.

[0301] Optionally, the first device authenticates and / or authorizes the first request.

[0302] Optionally, if the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of the perceived failure.

[0303] Optionally, if the first device successfully authenticates and / or authorizes the first request, the first device sends the first request to the third device to enable the third device to perform sensing service processing. Optionally, the first device receives the first response sent by the third device. Optionally, the first response is a sensing service response.

[0304] Optionally, if the first request includes a terminal device identifier, the first device sends a second request based on the first request.

[0305] Optionally, the second request may be a request for re-authentication and / or re-authorization of the perceived service.

[0306] Optionally, the second request is sent from the first device to the fourth device.

[0307] Optionally, the second request is sent by NEF to the fourth device.

[0308] Optionally, the fourth device is a UDM.

[0309] Optionally, if the fourth device receives a second request from the first device, the fourth device re-authenticates and / or re-authorizes the sensing service. Optionally, the fourth device sends a second response to the first device or NEF.

[0310] Optionally, the second response is a re-authentication and / or re-authorization response for the perceived service.

[0311] Optionally, the second response includes the result of re-authentication and / or re-authorization of the perceived service, i.e., whether the re-authentication and / or re-authorization was successful or failed.

[0312] Optionally, the first device receives a second response sent by the fourth device.

[0313] Optionally, if the second response includes the result of failure to re-authenticate and / or re-authorize the sensing service, i.e., the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of sensing failure.

[0314] Optionally, if the second response includes a result of successful re-authentication and / or re-authorization of the sensing service, i.e., the first device successfully authenticates and / or authorizes the first request, then the first device sends the first request to the third device.

[0315] Optionally, the first request is sent by the second device to the third device via NEF.

[0316] Optionally, the third device performs the first process based on the first request.

[0317] Optionally, the third device performs the first processing, which is the third device performing sensing service processing.

[0318] Optionally, the third device performing the first processing is the third device coordinating with the fifth device to perform sensing service processing.

[0319] Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0320] Optionally, the third device sends the first request to the fifth device.

[0321] Optionally, the first request may be sent by the third device to the fifth device via a service control function.

[0322] Optionally, the first request sent by the third device to the fifth device includes the perception entity configuration.

[0323] Optionally, the fifth device is an SE.

[0324] Optionally, the fifth device receives the first request.

[0325] Optionally, the fifth device sends a first response to the third device based on the first request.

[0326] Optionally, the first response includes at least one of sensing the result of the business, sensing success, and sensing failure.

[0327] Optionally, the fifth device performs the second processing based on the first request.

[0328] Optionally, the fifth device performs the second processing, which is the fifth device performing sensing service processing.

[0329] Optionally, the fifth device performing the second processing is the fifth device coordinating with the third device to perform sensing service processing. Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0330] Optionally, after the third device performs the sensing service processing, it sends a first response to the first device.

[0331] Optionally, the first device receives a first response sent by the third device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0332] Optionally, the first device sends a first response to the second device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0333] Through the technical solution of this embodiment, the fifth device performs the second processing based on the first request, the first request being authenticated and / or authorized by the first device, thus clarifying the authentication processing mechanism and / or authorization processing mechanism for communication sensing and / or AI / ML and / or computing services.

[0334] Seventh Embodiment Reference Figure 12 , Figure 12 The seventh embodiment of this application provides a processing method comprising steps S1 to S4, illustrating the interaction flow of the first device, second device, third device, and fifth device in the processing method shown in the seventh embodiment. Step S1: The second device sends a first request to enable the first device to authenticate and / or authorize the first request; Step S2: The first device authenticates and / or authorizes the first request; Step S3: The third device performs the first process based on the first request, wherein the first request is authenticated and / or authorized by the first device; Step S4: The fifth device performs the second processing based on the first request, wherein the first request is authenticated and / or authorized by the first device.

[0335] This embodiment proposes a technical solution whereby a second device sends a first request, the first device authenticates and / or authorizes the first request, a third device performs a first process based on the first request, and a fifth device performs a second process based on the first request. This clearly defines the authentication and / or authorization mechanisms for services such as communication sensing and / or AI / ML and / or computing.

[0336] Optionally, the first request is sent from the second device to the first device.

[0337] Optionally, the first device is a gateway or NEF.

[0338] Optionally, the second device is a sensing service consumer (such as AF).

[0339] Optionally, the second device sends a first request based on the needs of the sensing service.

[0340] Optionally, for an untrusted AF, the first request is sent to the gateway by the second device via NEF; alternatively, for a trusted AF, the first request can be sent directly to the gateway.

[0341] Optionally, the first request is a business awareness request.

[0342] Optionally, the first request may include at least one of the following: sensing service type, target sensing service area, sensing report conditions, sensing time conditions, sensing service QoS, required sensing data, consumer address information for receiving sensing data, and terminal device identifier.

[0343] Optionally, if the sensing is related to a terminal device, the sensing service request may include the terminal device identifier.

[0344] Optionally, the terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device.

[0345] Optionally, the first device receives the first request.

[0346] Optionally, the first device authenticates and / or authorizes the first request.

[0347] Optionally, if the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of the perceived failure.

[0348] Optionally, if the first device successfully authenticates and / or authorizes the first request, the first device sends the first request to the third device to enable the third device to perform sensing service processing. Optionally, the first device receives the first response sent by the third device. Optionally, the first response is a sensing service response.

[0349] Optionally, the third device is SF.

[0350] Optionally, if the first request includes a terminal device identifier, the first device sends a second request based on the first request.

[0351] Optionally, the second request may be a request for re-authentication and / or re-authorization of the perceived service.

[0352] Optionally, the second request is sent from the first device to the fourth device.

[0353] Optionally, the second request is sent by NEF to the fourth device.

[0354] Optionally, the fourth device is a UDM.

[0355] Optionally, if the fourth device receives a second request from the first device, the fourth device re-authenticates and / or re-authorizes the sensing service. Optionally, the fourth device sends a second response to the first device or NEF.

[0356] Optionally, the second response is a re-authentication and / or re-authorization response for the perceived service.

[0357] Optionally, the second response includes the result of re-authentication and / or re-authorization of the perceived service, i.e., whether the re-authentication and / or re-authorization was successful or failed.

[0358] Optionally, the first device receives a second response sent by the fourth device.

[0359] Optionally, if the second response includes the result of failure to re-authenticate and / or re-authorize the sensing service, i.e., the first device fails to authenticate and / or authorize the first request, the first device sends a first response to the second device, the first response carrying the result of sensing failure.

[0360] Optionally, if the second response includes a result of successful re-authentication and / or re-authorization of the sensing service, i.e., the first device successfully authenticates and / or authorizes the first request, then the first device sends the first request to the third device.

[0361] Optionally, the first request is sent by the second device to the third device via NEF.

[0362] Optionally, the third device performs the first process based on the first request.

[0363] Optionally, the third device performs the first processing, which is the third device performing sensing service processing.

[0364] Optionally, the third device performing the first processing is the third device coordinating with the fifth device to perform sensing service processing.

[0365] Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0366] Optionally, the third device sends the first request to the fifth device.

[0367] Optionally, the first request may be sent by the third device to the fifth device via a service control function.

[0368] Optionally, the first request sent by the third device to the fifth device includes the perception entity configuration.

[0369] Optionally, the fifth device is an SE.

[0370] Optionally, the fifth device sends a first response to the third device based on the first request.

[0371] Optionally, the first response includes at least one of sensing the result of the business, sensing success, and sensing failure.

[0372] Optionally, the fifth device performs the second processing based on the first request.

[0373] Optionally, the fifth device performs the second processing, which is the fifth device performing sensing service processing.

[0374] Optionally, the fifth device performing the second processing is the fifth device coordinating with the third device to perform sensing service processing. Optionally, the sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission.

[0375] Optionally, after the third device performs the sensing service processing, it sends a first response to the first device.

[0376] Optionally, the first device receives a first response sent by the third device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0377] Optionally, the first device sends a first response to the second device. Optionally, the first response includes at least one of the following: the result of the sensing service, sensing success, and sensing failure.

[0378] Through the technical solution of this embodiment, the second device sends a first request, the first device authenticates and / or authorizes the first request; the third device performs a first process based on the first request, and the fifth device performs a second process based on the first request, thus clarifying the authentication and / or authorization processing mechanisms for communication sensing and / or AI / ML and / or computing services.

[0379] Eighth embodiment Please see Figure 13 , Figure 13 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 1 The device may be mounted on or be the first device (such as a gateway or NEF) in the above method embodiments. Figure 13 The processing apparatus shown can be used to perform some or all of the functions described in the method embodiments above, such as... Figure 13 As shown, the processing apparatus 140 includes: The first processing module 1401 is used to authenticate and / or authorize the first request.

[0380] Optionally, the processing apparatus further includes at least one of the following: The first request is a business-aware request; The first request was sent by the second device; Send the second request based on the first request; Send the first request to the third device; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

[0381] Optionally, the processing apparatus further includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; The first request was sent by the second device via NEF; The first request was sent from the third device to the fifth device; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent to the fourth device; The third device performs the first process based on the first request.

[0382] Optionally, the processing apparatus further includes at least one of the following: The second request is sent by NEF to the fourth device; The first request is sent from the third device to the fifth device via the service control function; The first request sent by the third device to the fifth device includes the sensing entity configuration; The fifth device executes the second process based on the first request; Executing either the first processing step or the second processing step constitutes the execution of the perceived business processing step; Receive the first response sent by the third device; Receive the second response sent by the fourth device; Send the first response to the second device.

[0383] Optionally, the processing apparatus further includes at least one of the following: The first response is a business-aware response; The first response is sent from the fifth device to the third device; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

[0384] The processing device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[0385] Ninth Embodiment Please see Figure 14 , Figure 14 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 2 The device may be mounted on or be the second device (such as AF) in the above method embodiments. Figure 14 The processing apparatus shown can be used to perform some or all of the functions described in the method embodiments above, such as... Figure 14 As shown, the processing device 150 includes: The sending module 1501 is used to send a first request so that the first device can authenticate and / or authorize the first request.

[0386] Optionally, the processing apparatus further includes at least one of the following: The first request is a business-aware request; The first device sends a second request based on the first request; The first request is sent from the first device to the third device; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

[0387] Optionally, the processing apparatus further includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; The first request is sent to the first device via NEF; The first request was sent from the third device to the fifth device; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent from the first device to the fourth device; The third device performs the first process based on the first request.

[0388] Optionally, the processing apparatus further includes at least one of the following: The second request is sent by NEF to the fourth device; The first request is sent from the third device to the fifth device via the service control function; The first request sent by the third device to the fifth device includes the sensing entity configuration; The fifth device executes the second process based on the first request; Executing either the first processing step or the second processing step constitutes the execution of the perceived business processing step; Receive the first response sent by the first device; The first device receives the second response sent by the fourth device.

[0389] Optionally, the processing apparatus further includes at least one of the following: The first response is a business-aware response; The first response is sent from the third device to the first device; The first response is sent from the fifth device to the third device; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

[0390] The processing device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[0391] Tenth Embodiment Please see Figure 15 , Figure 15 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 3 The device may be mounted on or be the third device in the above method embodiments. Figure 15 The processing apparatus shown can be used to perform some or all of the functions described in the method embodiments above. For example... Figure 15 As shown, the device 160 includes: The second processing module 1601 is used to perform first processing based on a first request, wherein the first request is authenticated and / or authorized by the first device.

[0392] Optionally, the processing apparatus further includes at least one of the following: The first step is to perform the perception-based business processing. The first request is a business-aware request; The first request is sent by the first device; The first request is sent from the second device to the first device; The first device sends a second request based on the first request; Send the first request to the fifth device; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

[0393] Optionally, the processing apparatus further includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first request is sent from the second device to the first device via NEF; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent from the first device to the fourth device.

[0394] Optionally, the processing apparatus further includes at least one of the following: The second request is sent by NEF to the fourth device; The first request is sent from the third device to the fifth device via the service control function; The first request sent to the fifth device includes the sensing entity configuration; The fifth device executes the second process based on the first request; The second process is to perform the perception business processing; Receive the first response sent by the fifth device; Send a first response to the first device; The first device receives the second response sent by the fourth device; The first device sends a first response to the second device.

[0395] Optionally, the processing apparatus further includes at least one of the following: The first response is a business-aware response; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

[0396] The processing device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[0397] Tenth Embodiment Please see Figure 16 , Figure 16 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 4 This device may be mounted on or is the fifth device in the above method embodiments. Figure 16 The processing apparatus shown can be used to perform some or all of the functions described in the method embodiments above. For example... Figure 16 As shown, the device 170 includes: The third processing module 1701 is used to perform second processing based on a first request, wherein the first request is authenticated and / or authorized by the first device.

[0398] Optionally, the processing apparatus further includes at least one of the following: The second process is to perform the perception business processing; The first request is a business-aware request; The first request is sent from the second device to the first device; The first request is sent from the first device to the third device; The first request was sent from the third device to the fifth device; The first device sends a second request based on the first request; The third device performs the first process based on the first request; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

[0399] Optionally, the processing apparatus further includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first request is sent from the second device to the first device via NEF; The first request is sent from the third device to the fifth device via the service control function; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent from the first device to the fourth device.

[0400] Optionally, the processing apparatus further includes at least one of the following: The second request is sent by NEF to the fourth device; The first request includes the configuration of the sensing entity; Send the first response to the third device; The third device sends a first response to the first device; The first device receives the second response sent by the fourth device; The first device sends a first response to the second device.

[0401] Optionally, the processing apparatus further includes at least one of the following: The first response is a business-aware response; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

[0402] See Figure 17 , Figure 17 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Figure 17 As shown, the communication device 180 described in this embodiment can be a terminal device (or a component that can be used in a terminal device), a first device (or a component that can be used in a first device), a second device (or a component that can be used in a second device), or a third device (or a component that can be used in a third device) mentioned in the foregoing method embodiments. The communication device 180 can be used to implement the methods described in the above method embodiments corresponding to a terminal device, a first device, a second device, or a third device, as detailed in the descriptions in the above method embodiments.

[0403] The communication device 180 may include one or more processors 1801, which may also be referred to as processing units, and can perform certain control or processing functions. The processor 1801 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[0404] Optionally, the processor 1801 may also store instructions 1803 or data (e.g., intermediate data). Optionally, instructions 1803 may be executed by the processor 1801 to cause the communication device 180 to perform the methods described in the above method embodiments corresponding to the terminal device, the first device, the second device, or the third device.

[0405] Optionally, the communication device 180 may include a circuit that can perform the functions of sending, receiving, or communicating in the foregoing method embodiments.

[0406] Optionally, the communication device 180 may include one or more memories 1802, which may store instructions 1804 that can be executed on the processor 1801 to cause the communication device 180 to perform the methods described in the above method embodiments.

[0407] Alternatively, the memory 1802 may also store data. The processor 1801 and the memory 1802 can be configured separately or integrated together.

[0408] Optionally, the communication device 180 may further include a transceiver 1805 and / or an antenna 1806. The processor 1801, which may be referred to as a processing unit, controls the communication device 180 (the first device, the second device, or the third device). The transceiver 1805, which may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transmission and reception functions of the communication device 180.

[0409] Optionally, if the communication device 180 is used to implement the operation corresponding to the first device in the above embodiments, for example, the transceiver 1805 may receive the first request; and the processor 1801 may authenticate and / or authorize the first request.

[0410] Optionally, the specific implementation process of the processor 1801 and transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0411] Optionally, if the communication device 180 is used to implement the operation corresponding to the second device in the above embodiments, for example, the transceiver 1805 may send a first request.

[0412] Optionally, the specific implementation process of the processor 1801 and transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0413] The processor 1801 and transceiver 1805 described in this application can be implemented on ICs (Integrated Circuits), analog integrated circuits, RFICs (Radio Frequency Integrated Circuits), mixed-signal integrated circuits, ASICs (Application Specific Integrated Circuits), PCBs (Printed Circuit Boards), electronic devices, etc. The processor 1801 and transceiver 1805 can also be manufactured using various integrated circuit process technologies, such as CMOS (Complementary Metal Oxide Semiconductor), NMOS (N Metal-Oxide-Semiconductor), PMOS (Positive Channel Metal Oxide Semiconductor), BJT (Bipolar Junction Transistor), Bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0414] In this application, the communication device can be a first device (such as a gateway or NEF), a second device (such as an AF), a third device (such as an SF), or a fifth device (such as an SE), depending on the context. Furthermore, the terminal device can be implemented in various forms. For example, the terminal devices described in this application can include mobile terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0415] Although the communication device described in the above embodiments is exemplified by a terminal device, a first device, a second device, or a third device, the scope of the communication device described in this application is not limited to the aforementioned first device, second device, or third device, and the structure of the communication device may vary. Figure 17 There are limitations. Communication equipment can be a standalone device or part of a larger device.

[0416] This application also provides a communication system, including: a terminal device as described in any of the above embodiments; and a first device, a second device, or a third device as described in any of the above embodiments.

[0417] This application also provides a communication device, including a memory and a processor. The memory stores a processing program, and when the processing program is executed by the processor, it implements the steps of the processing method in any of the above embodiments.

[0418] The communication device in this application can be a first device (such as a gateway or NEF), a second device (such as an AF), a third device (such as an SF), a fifth device (such as an SE), or a chip (such as a SOC or a baseband chip with communication functions, etc.). The specific meaning needs to be clarified according to the context.

[0419] This application also provides a computer-readable storage medium storing a processing program, which, when executed by a processor, implements the steps of the processing method in any of the above embodiments.

[0420] In the embodiments of the communication device and storage medium provided in this application, all the technical features of any of the above-described processing method embodiments may be included. The extended and explained contents of the specification are basically the same as the embodiments of the above methods, and will not be repeated here.

[0421] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the methods described in the various possible implementations above.

[0422] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.

[0423] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0424] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0425] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0426] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0427] In this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions are generally described in detail only when they appear for the first time. When they appear again, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions that are not described in detail later can be referred to their previous relevant detailed descriptions.

[0428] In this application, the descriptions of the various embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0429] The technical features of the present application can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.

[0430] Through 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 software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal device, or network device, etc.) to execute the methods of each embodiment of this application.

[0431] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, storage disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0432] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A processing method, characterized in that, Applied to the first device, including the following steps: S2: Authenticate and / or authorize the first request.

2. The method according to claim 1, characterized in that, It also includes at least one of the following: The first request is a business-aware request; The first request was sent by the second device; Send the second request based on the first request; Send the first request to the third device; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

3. The method according to claim 2, characterized in that, It also includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; The first request was sent by the second device via NEF; The first request was sent from the third device to the fifth device; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent to the fourth device; The third device performs the first process based on the first request.

4. The method according to claim 3, characterized in that, It also includes at least one of the following: The second request is sent by NEF to the fourth device; The first request is sent from the third device to the fifth device via the service control function; The first request sent by the third device to the fifth device includes the sensing entity configuration; The fifth device executes the second process based on the first request; Executing either the first processing step or the second processing step constitutes the execution of the perceived business processing step; Receive the first response sent by the third device; Receive the second response sent by the fourth device; Send the first response to the second device.

5. The method according to claim 4, characterized in that, It also includes at least one of the following: The first response is a business-aware response; The first response is sent from the fifth device to the third device; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

6. A processing method, characterized in that, Applied to a second device, including the following steps: S1: Send a first request to enable the first device to authenticate and / or authorize the first request.

7. The method according to claim 6, characterized in that, It also includes at least one of the following: The first request is a business-aware request; The first device sends a second request based on the first request; The first request is sent from the first device to the third device; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

8. The method according to claim 7, characterized in that, It also includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; The first request is sent to the first device via NEF; The first request was sent from the third device to the fifth device; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent from the first device to the fourth device; The third device performs the first process based on the first request.

9. The method according to claim 8, characterized in that, It also includes at least one of the following: The second request is sent by NEF to the fourth device; The first request is sent from the third device to the fifth device via the service control function; The first request sent by the third device to the fifth device includes the sensing entity configuration; The fifth device executes the second process based on the first request; Executing either the first processing step or the second processing step constitutes the execution of the perceived business processing step; Receive the first response sent by the first device; The first device receives the second response sent by the fourth device.

10. The method according to claim 9, characterized in that, It also includes at least one of the following: The first response is a business-aware response; The first response is sent from the third device to the first device; The first response is sent from the fifth device to the third device; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

11. A processing method, characterized in that, Applied to a third device, including the following steps: S3: Perform first processing based on the first request, wherein the first request is authenticated and / or authorized by the first device.

12. The method according to claim 11, characterized in that, It also includes at least one of the following: The first step is to perform the perception-based business processing. The first request is a business-aware request; The first request is sent by the first device; The first request is sent from the second device to the first device; The first device sends a second request based on the first request; Send the first request to the fifth device; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

13. The method according to claim 12, characterized in that, It also includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first request is sent from the second device to the first device via NEF; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent from the first device to the fourth device.

14. The method according to claim 13, characterized in that, It also includes at least one of the following: The second request is sent by NEF to the fourth device; The first request is sent from the third device to the fifth device via the service control function; The first request sent to the fifth device includes the sensing entity configuration; The fifth device executes the second process based on the first request; The second process is to perform the perception business processing; Receive the first response sent by the fifth device; Send a first response to the first device; The first device receives the second response sent by the fourth device; The first device sends a first response to the second device.

15. The method according to claim 14, characterized in that, It also includes at least one of the following: The first response is a business-aware response; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

16. A processing method, characterized in that, Applied to the fifth device, including the following steps: S4: Perform second processing based on the first request, wherein the first request is authenticated and / or authorized by the first device.

17. The method according to claim 16, characterized in that, It also includes at least one of the following: The second process is to perform the perception business processing; The first request is a business-aware request; The first request is sent from the second device to the first device; The first request is sent from the first device to the third device; The first request was sent from the third device to the fifth device; The first device sends a second request based on the first request; The third device performs the first process based on the first request; The first request includes at least one of the following: the type of sensing service, the target sensing service area, the sensing report conditions, the sensing time conditions, the QoS of the sensing service, the required sensing data, the consumer address information for receiving the sensing data, and the terminal device identifier.

18. The method according to claim 17, characterized in that, It also includes at least one of the following: The terminal device identifier includes at least one of GPSI, SUPI, and other identifiers used to identify the terminal device; Sensing service processing includes at least one of sensing data acquisition, sensing result processing, and sensing result transmission; The first request is sent from the second device to the first device via NEF; The first request is sent from the third device to the fifth device via the service control function; The second request is a request for re-authentication and / or re-authorization of the perceived service; The second request is sent from the first device to the fourth device.

19. The method according to claim 18, characterized in that, It also includes at least one of the following: The second request is sent by NEF to the fourth device; The first request includes the configuration of the sensing entity; Send the first response to the third device; The third device sends a first response to the first device; The first device receives the second response sent by the fourth device; The first device sends a first response to the second device.

20. The method according to claim 19, characterized in that, It also includes at least one of the following: The first response is a business-aware response; The first response includes at least one of the following: sensing the result of the business, sensing success, and sensing failure; The second response is a re-authentication and / or re-authorization response for the perceived service; The first device is a gateway or NEF; The second device is for sensing business consumers; The third device is SF; The fourth device is UDM; The fifth device is SE.

21. A communication device, characterized in that, include: A memory and a processor, wherein the memory stores a processing program, and the processing program, when executed by the processor, implements the processing method as described in any one of claims 1 to 20.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a processing program, which, when executed by a processor, implements the processing method as described in any one of claims 1 to 20.

Images