Business processing method and device

Abstract

The invention provides a service processing method and device, and relates to the technical field of communication. The method comprises: a third party AF receiving a service request sent by a UE, the service request carrying service type information and service demand information; the third-party AF requests to call sensing data from core network equipment according to the service type information and the service demand information; and the third-party AF receives request response information returned by the core network equipment, and processes the service request according to the request response information. According to the method and the device, the third-party AF can call the sensing data stored in the core network, so that the service with the requirement on the sensing data can be better executed and returned to the user side, and the experience of the user on the third-party service can be improved.

Description

Business processing method and device Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a service processing method and device. Background Art

[0002] The sixth generation of mobile communication systems (6G) has become a global research hotspot. In the 6G era, user equipment (UE) and networks will have perception capabilities, collecting perception data to support the high-quality data requirements of emerging new services.

[0003] However, the core network currently lacks a solution for processing the perception data called by third-party application function (AF) network elements, which in turn affects the user experience of third-party services.

[0004] Summary of the Invention

[0005] This application proposes a service processing method and device, which provides a processing solution for third-party AF call perception data in the core network, thereby improving the user experience of third-party services.

[0006] The first aspect embodiment of the present application provides a service processing method, which is applied to a third-party AF, where the third-party AF is used to provide third-party services. The method includes: receiving a service request sent by a UE, where the service request carries service type information and service requirement information; based on the service type information and service requirement information, requesting a core network device to call perception data; receiving request response information returned by the core network device, and processing the service request based on the request response information.

[0007] In some embodiments of the present application, the request to call perception data from the core network device based on the service type information and service requirement information includes: determining the perception data information that needs to be requested to call based on the service type information and service requirement information; sending a request to call perception data to the core network device, the request to call perception data carries the perception data information and the identifier of the third-party AF, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call perception data.

[0008] In some embodiments of the present application, the receiving of the request response information returned by the core network device and processing the service request according to the request response information includes: receiving the perception data returned by the core network device that matches the perception data information, wherein the received perception data is returned by the core network device when it determines that the third-party AF has the right to call the perception data; performing service processing based on the received perception data, and returning the service processing result to the UE.

[0009] In some embodiments of the present application, the request for calling perception data also carries the UE identifier of the UE; the receiving of perception data returned by the core network device that matches the perception data information includes: receiving perception data returned by the core network device that matches the perception data information and the UE identifier.

[0010] In some embodiments of the present application, the receiving of the request response information returned by the core network device and processing the service request according to the request response information includes: receiving the call failure information returned by the core network device, the call failure information is returned by the core network device when it determines that the third-party AF has no right to call the perception data; based on the call failure information, returning the response information of the failure of the service request processing to the UE.

[0011] In some embodiments of the present application, the core network device includes: a network exposure function (NEF) network element and a first network element, the first network element is used to store perception data; the request to call perception data from the core network device based on the service type information and service requirement information includes: determining the perception data information that needs to be requested to be called based on the service type information and service requirement information; sending a perception data opening request to the NEF network element, the perception data opening request carrying the perception data information and the identifier of the third-party AF, so that the NEF network element sends the perception data information and the identifier of the third-party AF to the first network element, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data stored in the first network element.

[0012] In some embodiments of the present application, the receiving of the request response information returned by the core network device and processing the service request according to the request response information includes: receiving the perception data returned by the NEF network element that matches the perception data information, wherein the received perception data is returned by the first network element to the NEF network element when it determines that the third-party AF has the right to call the perception data; performing service processing based on the received perception data, and returning the service processing result to the UE.

[0013] In some embodiments of the present application, the perception data open request also carries the UE identifier of the UE; the receiving the perception data returned by the NEF network element that matches the perception data information includes: receiving the perception data returned by the NEF network element that matches the perception data information and the UE identifier.

[0014] In some embodiments of the present application, the receiving of the request response information returned by the core network device and processing the service request according to the request response information includes: receiving the call failure information returned by the NEF network element, the call failure information being returned by the first network element to the NEF network element when determining that the third-party AF has no right to call the perception data; and returning response information of the failure of the service request processing to the UE based on the call failure information.

[0015] In some embodiments of the present application, the service request also carries the public land mobile network (PLMN) identifier (PLMN ID) of the UE; determining the perception data information that needs to be requested based on the service type information and the service requirement information includes: determining the perception data information based on the service type information and the service requirement information, and in combination with the PLMN ID.

[0016] In some embodiments of the present application, the perception data information includes at least one of the following:

[0017] The type of sensed data being requested;

[0018] The uploaded object information corresponding to the perception data requested.

[0019] The second aspect of the present application provides a service processing method, which is applied to a core network device. The method includes: receiving a request for calling perception data sent by a third-party AF, where the third-party AF is used to provide third-party services; and returning request response information to the third-party AF.

[0020] In some embodiments of the present application, the request to call the perception data carries the perception data information to be requested and the identifier of the third-party AF; wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data.

[0021] In some embodiments of the present application, returning the request response information to the third-party AF includes: if it is determined based on the identifier of the third-party AF that the third-party AF has the right to call the perception data, then returning the perception data matching the perception data information to the third-party AF.

[0022] In some embodiments of the present application, the request for calling perception data also carries the UE identifier of the UE; returning the perception data that matches the perception data information to the third-party AF includes: returning the perception data that matches the perception data information and the UE identifier to the third-party AF.

[0023] In some embodiments of the present application, returning request response information to the third-party AF includes: if it is determined according to the identifier of the third-party AF that the third-party AF has no right to call the perception data, returning call failure information to the third-party AF.

[0024] In some embodiments of the present application, the core network device includes: a NEF network element and a first network element, the first network element is used to store perception data; the receiving of the request for calling perception data sent by the third-party AF includes: the NEF network element receives the perception data open request sent by the third-party AF, and the perception data open request carries the perception data information that needs to be requested to be called and the identifier of the third-party AF; the NEF network element sends the perception data information and the identifier of the third-party AF to the first network element, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data stored in the first network element.

[0025] In some embodiments of the present application, after the NEF network element sends the perception data information and the identifier of the third-party AF to the first network element, the method further includes: the NEF network element receives perception data that matches the perception data information, wherein the received perception data is returned to the NEF network element by the first network element when it determines that the third-party AF has the right to call the perception data.

[0026] In some embodiments of the present application, the perception data open request also carries the UE identifier of the UE; the NEF network element receives the perception data that matches the perception data information, including: the NEF network element receives the perception data returned by the first network element that matches the perception data information and the UE identifier.

[0027] In some embodiments of the present application, returning the request response information to the third-party AF includes: the NEF network element returning the received perception data to the third-party AF.

[0028] In some embodiments of the present application, after the NEF network element sends the perception data information and the identifier of the third-party AF to the first network element, the method further includes: the NEF network element receives the returned call failure information, and the call failure information is returned to the NEF network element by the first network element when it determines that the third-party AF has no right to call the perception data.

[0029] In some embodiments of the present application, returning the request response information to the third-party AF includes: the NEF network element returning the received call failure information to the third-party AF.

[0030] In some embodiments of the present application, the perception data information includes at least one of the following:

[0031] The type of sensed data being requested;

[0032] The uploaded object information corresponding to the perception data requested.

[0033] The third aspect of the present application provides a service processing device, which is applied to a third-party AF, and the third-party AF is used to provide third-party services. The device includes: a first receiving module, configured to receive a service request sent by a UE, and the service request carries service type information and service requirement information; a first sending module, configured to request the core network device to call perception data based on the service type information and service requirement information; the first receiving module is also configured to receive the request response information returned by the core network device, and process the service request according to the request response information.

[0034] The fourth aspect embodiment of the present application provides a business processing device, which is applied to a core network device, and the device includes: a second receiving module, configured to receive a request for calling perception data sent by a third-party AF, and the third-party AF is used to provide third-party services; a second sending module, configured to return request response information to the third-party AF.

[0035] The fifth aspect embodiment of the present application provides a communication device, which includes: a transceiver; a memory; a processor, which is connected to the transceiver and the memory respectively, and is configured to control the wireless signal reception and transmission of the transceiver by executing computer-executable instructions on the memory, and can implement the method of the first aspect embodiment or the second aspect embodiment of the present application.

[0036] The sixth aspect embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores computer-executable instructions; after the computer-executable instructions are executed by the processor, the method of the first aspect embodiment or the second aspect embodiment of the present application can be implemented.

[0037] The seventh aspect embodiment of the present application provides a service processing system, a third-party AF and a core network device; the third-party AF is used to execute the method as described in the first aspect embodiment of the present application; the core network device is used to execute the method as described in the second aspect embodiment of the present application.

[0038] The embodiment of the present application provides a service processing method and device. In view of the perception capabilities of UE, network, etc., a processing scheme for third-party AF to call perception data in the 6G core network architecture is provided. Specifically, the third-party AF used to provide third-party services can receive a service request sent by the UE, which carries service type information and service requirement information; the third-party AF requests the core network device to call perception data based on the service type information and service requirement information; then the third-party AF receives the request response information returned by the core network device and processes the UE's service request based on the request response information. By applying the technical solution of this embodiment, the third-party AF can call the perception data stored in the core network, and then better execute the services that require perception data and return them to the user end, thereby improving the user experience of third-party services.

[0039] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0041] FIG1 is a flow chart of a service processing method according to an embodiment of the present application;

[0042] FIG2 is a flow chart of a service processing method according to an embodiment of the present application;

[0043] FIG3 is a flow chart of a service processing method according to an embodiment of the present application;

[0044] FIG4 is a flow chart of a service processing method according to an embodiment of the present application;

[0045] FIG5 is a flow chart of a service processing method according to an embodiment of the present application;

[0046] FIG6 is a flow chart of a service processing method according to an embodiment of the present application;

[0047] FIG7 is a timing diagram of an example of a service processing method according to an embodiment of the present application;

[0048] FIG8 is a block diagram of a service processing device according to an embodiment of the present application;

[0049] FIG9 is a block diagram of a service processing device according to an embodiment of the present application;

[0050] FIG10 is a schematic structural diagram of a communication device according to an embodiment of the present application;

[0051] FIG11 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] The embodiments of the present application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application. It should be noted that the embodiments of the present application and the features in the embodiments may be combined with each other unless there is a conflict.

[0053] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0054] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0055] The sixth-generation mobile communication system (6G) has become a global research hotspot. A variety of new vertical application scenarios, represented by smart cities, smart transportation, intelligent manufacturing, and smart homes, will emerge in the 6G era. These applications require communication devices and users to perceive the physical world and mirror the digital world. The deep integration of communication systems with multiple systems, such as perception and artificial intelligence, has become a new trend in technological development. The development of communication and perception has always been independent and relatively parallel. Therefore, in the 6G synergistic integration, it is necessary to consider both the differences and commonalities between communication and perception, and create minimalist, efficient, and easy-to-deploy 6G synergistic integration equipment and networking models. 6G networks will provide users with a more personalized service experience, and network status and resource supply must be aligned with user needs. Through the collaboration and sharing of synergistic computing software and hardware resources, network elements within the network will achieve deep integration and mutually enhanced multi-dimensional perception, collaborative communication, and intelligent computing capabilities, thereby enabling the network to intelligently interact and process new information flows and achieve wide-area intelligent collaboration.

[0056] With the emergence of a variety of new services on 6G networks, the demand for data quantity and quality will surge. To address this issue, in the 6G era, UEs and networks will have perception capabilities. By collecting perception data, they will support the high-quality data requirements of these new services. However, the core network currently lacks a solution for processing perception data called by third-party AFs, which in turn affects the user experience of third-party services.

[0057] To this end, this embodiment proposes a service processing method and device, providing a processing solution for third-party AF call perception data in a 6G core network architecture, thereby improving the user experience of third-party services.

[0058] The service processing method and device provided in this application are described in detail below with reference to the accompanying drawings.

[0059] Figure 1 shows a flow chart of a service processing method according to an embodiment of the present application. As shown in Figure 1 , the method is applied to a third-party AF, and the method may include the following steps.

[0060] Step 101: A third-party AF receives a service request sent by a UE.

[0061] The third-party AF can be used to provide third-party services. When the UE needs third-party services, it can send a request for related services to the third-party AF. The service request can carry service type information and service requirement information of the service requested by the UE.

[0062] Among them, the business type information may include the type of artificial intelligence (AI) business, the type of model training business, the type of model calculation business, and other business types that require calling perception data, such as AI business types for images, voice, audio, etc.

[0063] Business demand information may include demand information for third-party services. For example, when the UE provides a model algorithm, the third-party AF needs to call the corresponding perception data according to the model algorithm to perform model training, and then return the model training results to the UE; for example, when the UE provides image information to the third-party AF, the third-party AF needs to perform model calculation on the image information based on the perception data, obtain the processing results of the image and return them to the UE, etc.

[0064] Step 102: The third-party AF requests the core network device to call the sensing data according to the service type information and service requirement information carried in the service request.

[0065] This embodiment can store perception data from end-side devices such as UEs (different and / or the same as the UE that sent the service request), base stations, and networks in core network devices. For example, in the core network, perception, computing, and AI functions are orchestrated and integrated into a key component module of a new computing network. The perception data collected from end-side devices such as UEs (different and / or the same as the UE that sent the service request), base stations, and networks is stored in this module to facilitate the retrieval of perception data.

[0066] After receiving the service request sent by the UE, the third-party AF determines that it needs to call the perception data stored in the core network to process the service request based on the service type information and service requirement information carried in the service request, and can request the core network device to call the corresponding perception data.

[0067] Step 103: The third-party AF receives the request response information returned by the core network device, and processes the service request sent by the UE according to the request response information.

[0068] The request response information is the response information returned by the core network device based on the perception data request. The third-party AF processes the service request sent by the UE based on the request response information. If the core network device returns the corresponding perception data, the third-party AF can perform service processing based on the perception data and return the service processing result to the UE.

[0069] By applying the service processing method provided in this embodiment, a processing solution for third-party AF calling perception data in a 6G core network architecture is provided for the perception capabilities of UE, network, etc., which enables the third-party AF to call the perception data stored in the core network, and then better execute services that require perception data and return it to the user end, thereby improving the user experience of third-party services.

[0070] Figure 2 shows a flow chart of a service processing method according to an embodiment of the present application. The method is applied to a third-party AF, as shown in Figure 2, and may include the following steps.

[0071] Step 201: The third-party AF receives a service request sent by a UE.

[0072] The service request may carry service type information and service requirement information of the service requested by the UE.

[0073] Step 202: The third-party AF determines the perception data information that needs to be requested based on the service type information and service requirement information carried in the service request.

[0074] The perception data information may be relevant information of the perception data that needs to be requested. In some examples, the perception data information may include: at least one of the perception data type requested for invocation and the upload object information corresponding to the perception data requested for invocation. The perception data type requested for invocation may include perception data types such as image, voice, and audio. The upload object information corresponding to the perception data requested for invocation may include at least one of the upload objects such as UE (different and / or the same UE as the UE that sends the service request), base station and network, such as requesting the perception data uploaded by UE and base station, or requesting the perception data uploaded by UE, base station and network, etc.

[0075] In some examples, the service request may also carry the PLMN ID of the UE; accordingly, step 202 may specifically include: the third-party AF determines the perception data information that needs to be requested based on the service type information and service requirement information carried in the service request and in combination with the PLMN ID of the UE.

[0076] For example, the third-party AF determines the type of perception data requested to be called based on the service type information and service demand information, and in combination with the PLMN ID of the UE, and the upload object corresponding to the perception data requested to be called is the upload object of the UE and base station within the corresponding range of the PLMN ID, and then determines to obtain the perception data information that needs to be requested to be called.

[0077] Step 203: The third-party AF sends a request to the core network device to call the sensing data.

[0078] The request for calling the perception data carries the perception data information and the identifier of the third-party AF, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data.

[0079] The core network device receives the sensing data information and the third-party AF identifier sent by the third-party AF. First, based on the third-party AF identifier, the core network device determines whether the third-party AF is authorized to access the sensing data stored in the first network element. In this embodiment, if the third-party AF is authorized to access the sensing data, the process shown in steps 204a to 205a may be continued. If the third-party AF is not authorized to access the sensing data, the process shown in steps 204b to 205b may be continued.

[0080] Step 204a: The third-party AF receives the perception data returned by the core network device that matches the perception data information.

[0081] The received perception data is returned by the core network device when it determines that the third-party AF has the right to call the perception data.

[0082] In some examples, the service request sent by the UE and received by the third-party AF may also carry a UE identifier of the UE, such as the UE's Subscriber Permanent Identifier (SUPI). Accordingly, the request for invoking perception data sent by the third-party AF to the core network device may also carry the UE identifier of the UE. Accordingly, step 204a may specifically include: the third-party AF receiving, from the core network device, perception data that matches the perception data information and the UE identifier.

[0083] For example, the core network device obtains the perception data that matches the perception data information and is suitable for the service required by the UE corresponding to the SUPI (UE identifier), and returns the obtained perception data to the third-party AF. In this way, more suitable perception data can be obtained, improving the accuracy of service processing.

[0084] Step 205a: The third-party AF performs service processing based on the received sensing data and returns the service processing result to the UE.

[0085] For example, after obtaining the perception data, the third-party AF uses the perception data for calculation and completes business processing.

[0086] In step 204b, which is parallel to step 204a, the third-party AF receives the call failure information returned by the core network device.

[0087] The call failure information is returned by the core network device when it determines that the third-party AF has no right to call the perception data.

[0088] Step 205b: The third-party AF returns a response message indicating that the service request processing failed to the UE based on the call failure information.

[0089] By applying the service processing method provided in this embodiment, a processing solution for third-party AF calling perception data in a 6G core network architecture is provided for the perception capabilities of UE, network, etc., which enables the third-party AF to call the perception data stored in the core network, and then better execute services that require perception data and return it to the user end, thereby improving the user experience of third-party services.

[0090] Figure 3 shows a flow chart of a service processing method according to an embodiment of the present application. The method is applied to a third-party AF. On the core network device side, the core network device may include: a NEF network element and a first network element (it should be noted that this embodiment does not specifically limit the name of the first network element), that is, the NEF network element and the first network element are network elements in the core network. The first network element can be used to store perception data. For example, in the core network device, the perception, computing, and AI functions are orchestrated and integrated into an important component module of the new computing power network. As the first network element, the perception data collected from the UE, base station, network and other end sides are stored in the first network element to facilitate the call of perception data.

[0091] Based on the above content, in order to illustrate the specific implementation process of this embodiment, as shown in FIG3 , the method may include the following steps.

[0092] Step 301: The third-party AF receives a service request sent by a UE.

[0093] The service request may carry service type information and service requirement information of the service requested by the UE.

[0094] Step 302: The third-party AF determines the perception data information that needs to be requested based on the service type information and service requirement information carried in the service request.

[0095] The perception data information may be relevant information of the perception data that needs to be requested. In some examples, the perception data information may include: at least one of the perception data type requested for invocation and the upload object information corresponding to the perception data requested for invocation. The perception data type requested for invocation may include perception data types such as image, voice, and audio. The upload object information corresponding to the perception data requested for invocation may include at least one of the upload objects such as UE (different and / or the same UE as the UE that sends the service request), base station and network, such as requesting the perception data uploaded by UE and base station, or requesting the perception data uploaded by UE, base station and network, etc.

[0096] In some examples, the service request may also carry the PLMN ID of the UE; accordingly, step 302 may specifically include: the third-party AF determines the perception data information that needs to be requested based on the service type information and service requirement information carried in the service request and in combination with the PLMN ID of the UE.

[0097] Step 303: The third-party AF sends a sensing data opening request to the NEF network element.

[0098] The perception data open request carries the perception data information (obtained in step 302) and the identifier of the third-party AF. Further, the NEF network element sends the perception data information and the identifier of the third-party AF to the first network element, wherein the identifier of the third-party AF can be used to determine whether the third-party AF has the right to call the perception data stored in the first network element.

[0099] In this embodiment, the first network element may have network perception capabilities, network computing capabilities, and the ability to store perception data, and may be specifically considered a network unit with computing power. The first network element receives the perception data information and the identifier of the third-party AF sent by the NEF network element, and first determines, based on the identifier of the third-party AF, whether the third-party AF is authorized to access the perception data stored by the first network element.

[0100] For example, it is determined whether the identifier of the third-party AF exists in a preset list, where the identifiers of AFs authorized to access the sensing data stored in the first network element are stored. If the identifier of the third-party AF exists in the preset list, it can be determined that the third-party AF has the authority to access the sensing data stored in the first network element. If the identifier of the third-party AF does not exist in the preset list, it can be determined that the third-party AF does not have the authority to access the sensing data stored in the first network element.

[0101] For this embodiment, if the third-party AF has the right to call the perception data stored in the first network element, the process shown in steps 304a to 305a can be continued; if the third-party AF does not have the right to call the perception data stored in the first network element, the process shown in steps 304b to 305b can be continued.

[0102] Step 304a: The third-party AF receives the sensing data returned by the NEF network element that matches the sensing data information.

[0103] Among them, the perception data received by the third-party AF is returned to the NEF network element by the first network element when it determines that the third-party AF has the right to call the perception data. The NEF network element returns the received perception data that matches the perception data information to the third-party AF.

[0104] In some examples, the service request sent by the UE and received by the third-party AF may also carry a UE identifier of the UE, such as the UE's SUPI. Accordingly, the perception data open request sent by the third-party AF to the NEF network element may also carry the UE identifier of the UE. Accordingly, step 304a may specifically include: the third-party AF receiving, from the NEF network element, perception data that matches the perception data information and the UE identifier.

[0105] For example, the first network element obtains the perception data that matches the perception data information and is suitable for the service required by the UE corresponding to the SUPI (UE identifier), and returns the obtained perception data to the NEF network element. In this way, more suitable perception data can be obtained, improving the accuracy of service processing.

[0106] Step 305a: The third-party AF performs service processing based on the received sensing data and returns the service processing result to the UE.

[0107] For example, after obtaining the perception data, the third-party AF uses the perception data for calculation and completes business processing.

[0108] In step 304b, which is parallel to step 304a, the third-party AF receives the call failure information returned by the NEF network element.

[0109] The call failure information is returned by the first network element to the NEF network element when the first network element determines that the third-party AF has no right to call the sensing data. The NEF network element returns the received call failure information to the third-party AF.

[0110] Step 305b: The third-party AF returns a response message indicating that the service request processing failed to the UE based on the call failure information.

[0111] By applying the service processing method provided in this embodiment, a processing solution for third-party AF calling perception data in a 6G core network architecture is provided for the perception capabilities of UE, network, etc., which enables the third-party AF to call the perception data stored in the core network, and then better execute services that require perception data and return it to the user end, thereby improving the user experience of third-party services.

[0112] Figure 4 shows a flow chart of a service processing method according to an embodiment of the present application. The method is applied to a core network device, as shown in Figure 4, and the method may include the following steps.

[0113] Step 401: The core network device receives a request for invoking perception data sent by a third-party AF.

[0114] The third-party AF is used to provide third-party services. When the third-party AF receives a service request from a UE, if it determines that it needs to call the perception data stored in the core network to process the service request based on the service type information and service requirement information of the service requested by the UE carried in the service request, it can request the core network device to call the corresponding perception data.

[0115] Step 402: The core network device returns request response information to the third-party AF.

[0116] The request response information is the response information returned by the core network device according to the perception data request, and the third-party AF processes the service request sent by the UE according to the request response information.

[0117] By applying the service processing method provided in this embodiment, a processing solution for third-party AF calling perception data in a 6G core network architecture is provided for the perception capabilities of UE, network, etc., which enables the third-party AF to call the perception data stored in the core network, and then better execute services that require perception data and return it to the user end, thereby improving the user experience of third-party services.

[0118] Figure 5 shows a flow chart of a service processing method according to an embodiment of the present application. The method is applied to a core network device, as shown in Figure 5, and the method may include the following steps.

[0119] Step 501: The core network device receives a request for invoking perception data sent by a third-party AF.

[0120] The request for calling the perception data carries the perception data information to be called and the identifier of the third-party AF; wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data.

[0121] The sensory data information may include information related to the sensory data being requested. In some examples, the sensory data information may include at least one of the following: information about the sensory data being requested and information about the upload object corresponding to the sensory data being requested. For details, see the corresponding descriptions in steps 202 and 302, and will not be repeated here.

[0122] In this embodiment, if the third-party AF has the right to call the perception data, the process shown in step 502a may be continued; if the third-party AF does not have the right to call the perception data, the process shown in step 502b may be continued.

[0123] Step 502a: If the core network device determines, based on the identifier of the third-party AF in the request, that the third-party AF has the right to call the perception data, the core network device returns the perception data that matches the perception data information to the third-party AF.

[0124] In some examples, the service request sent by the UE to the third-party AF may also carry the UE identifier of the UE, such as SUPI, etc. Accordingly, the perception data matching the perception data information is returned to the third-party AF, which may specifically include: the core network device returns the perception data matching the perception data information and the UE identifier to the third-party AF.

[0125] For example, the core network device obtains the perception data that matches the perception data information and is suitable for the service required by the UE corresponding to the SUPI (UE identifier), and returns the obtained perception data to the third-party AF. In this way, more suitable perception data can be obtained, improving the accuracy of service processing.

[0126] In step 502b, which is parallel to step 502a, if the core network device determines, based on the identifier of the third-party AF in the request, that the third-party AF has no right to call the sensing data, a call failure message is returned to the third-party AF.

[0127] The third-party AF returns a response message indicating that the service request processing failed to the UE based on the call failure information.

[0128] By applying the service processing method provided in this embodiment, a processing solution for third-party AF calling perception data in a 6G core network architecture is provided for the perception capabilities of UE, network, etc., which enables the third-party AF to call the perception data stored in the core network, and then better execute services that require perception data and return it to the user end, thereby improving the user experience of third-party services.

[0129] Figure 6 is a flow chart of a service processing method according to an embodiment of the present application. The method is applied to core network equipment. On the core network equipment side, the core network equipment may include: a NEF network element and a first network element (it should be noted that this embodiment does not specifically limit the name of the first network element), that is, the NEF network element and the first network element are network elements in the core network. The first network element can be used to store perception data. For example, in the core network equipment, perception, computing, and AI functions are orchestrated and integrated into an important component module of a new computing power network. As the first network element, the perception data collected from the UE, base station, network and other end sides are stored in the first network element to facilitate the call of perception data.

[0130] Based on the above content, in order to illustrate the specific implementation process of this embodiment, as shown in FIG6 , the method may include the following steps.

[0131] Step 601: The NEF network element receives a sensing data opening request sent by a third-party AF.

[0132] The perception data open request carries the perception data information to be requested and the identifier of the third-party AF, wherein the identifier of the third-party AF can be used to determine whether the third-party AF has the right to call the perception data stored in the first network element.

[0133] The perception data information may be information related to the perception data to be requested. In some examples, the perception data information may include at least one of information about the perception data requested and information about an upload object corresponding to the perception data requested.

[0134] Step 602: The NEF network element sends the sensing data information and the identifier of the third-party AF in the sensing data open request to the first network element.

[0135] Step 603: The first network element determines, based on the identifier of the third-party AF, whether the third-party AF has the right to call the sensing data stored in the first network element.

[0136] For example, it is determined whether the identifier of the third-party AF is present in a preset storage location, where the identifiers of various AFs that are not authorized to access the perception data stored by the first network element are stored. If the identifier of the third-party AF is not present in the preset storage location, it can be determined that the third-party AF is authorized to access the perception data stored by the first network element. If the identifier of the third-party AF is present in the preset storage location, it can be determined that the third-party AF is not authorized to access the perception data stored by the first network element.

[0137] For this embodiment, if the third-party AF has the right to call the perception data stored in the first network element, the process shown in steps 604a to 605a can be continued; if the third-party AF does not have the right to call the perception data stored in the first network element, the process shown in steps 604b to 605b can be continued.

[0138] Step 604a: The NEF network element receives the sensing data returned by the first network element that matches the sensing data information.

[0139] The perception data received by the NEF network element is returned to the NEF network element by the first network element when the first network element determines that the third-party AF has the right to call the perception data.

[0140] In some examples, the service request sent by the UE to the third-party AF may also carry a UE identifier of the UE, such as a SUPI. Accordingly, the perception data open request sent by the third-party AF to the NEF network element may also carry the UE identifier of the UE. The NEF network element will send the UE identifier of the UE to the first network element, so that the first network element obtains perception data matching the perception data information and the UE identifier and returns it to the NEF network element. Accordingly, step 604a may specifically include: the NEF network element receives the perception data matching the perception data information and the UE identifier returned by the first network element.

[0141] For example, the first network element obtains the perception data that matches the perception data information and is suitable for the service required by the UE corresponding to the SUPI (UE identifier), and returns the obtained perception data to the NEF network element. In this way, more suitable perception data can be obtained, improving the accuracy of service processing.

[0142] Step 605a: The NEF returns the received sensing data to the third-party AF.

[0143] The third-party AF performs service processing based on the received sensing data and returns the service processing result to the UE.

[0144] In step 604b, which is parallel to step 604a, the NEF network element receives the call failure information returned by the first network element.

[0145] The call failure information is returned by the first network element to the NEF network element when the first network element determines that the third-party AF has no right to call the sensing data.

[0146] Step 605b: The NEF returns the received call failure information to the third-party AF.

[0147] The third-party AF returns a response message indicating that the service request processing failed to the UE based on the call failure information.

[0148] By applying the service processing method provided in this embodiment, a processing solution for third-party AF calling perception data in a 6G core network architecture is provided for the perception capabilities of UE, network, etc., which enables the third-party AF to call the perception data stored in the core network, and then better execute services that require perception data and return it to the user end, thereby improving the user experience of third-party services.

[0149] Furthermore, based on the embodiments shown in Figures 1 to 6, embodiments of the present application provide a service processing system. This system may include a third-party AF and core network equipment. The third-party AF may execute the service processing methods shown in Figures 1 to 3; the core network equipment may execute the service processing methods shown in Figures 4 to 6. The entire system may execute the method shown in Figure 7.

[0150] Figure 7 is a timing diagram of an example of a service processing method according to an embodiment of the present application. This example of the method can be applied to the above service processing system, and is described by taking the core network device including the NEF network element and the first network element as an example.

[0151] Referring to FIG. 7 , the method includes the following steps.

[0152] Step 1: The UE sends a service request to the third-party AF. The service request may carry the UE identifier (such as SUPI, etc.), PLMN ID, and service type information and service requirement information of the service requested by the UE.

[0153] Step 2: After receiving the service request, the third-party AF triggers the perception data call process and sends a perception data open request to the NEF network element in the core network.

[0154] The third-party AF analyzes the service type information and service requirement information carried in the service request to determine the perception data information to be requested from the core network (including the type of perception data requested to be called and the upload object information corresponding to the perception data requested to be called). The third-party AF sends a perception data open request to the NEF network element. The perception data open request may carry the third-party AF identifier (AF ID), the UE's SUPI, and the perception data information requested to be called.

[0155] Step 3: After receiving the sensing data opening request, the NEF network element sends the sensing data request to the Storage module that stores the sensing data.

[0156] The storage module may be the first network element in the embodiment shown above. The sensing data request may carry the identifier (AF ID) of the third-party AF, the SUPI of the UE, and the sensing data information requested to be called.

[0157] Step 4: After receiving the perception data request, the Storage module determines, based on the identifier of the third-party AF, whether the third-party AF has the right to call the perception data stored in the core network.

[0158] If it is determined that the third-party AF does not have the right to call the perception data, a call failure message is returned; if it is determined that the third-party AF has the right to call the perception data, the perception data information requested for call is analyzed and the perception data in the Storage module is matched and queried.

[0159] Step 5: After the matching query is completed, the Storage module returns the sensing data request result to the NEF network element.

[0160] Step 6: The NEF network element returns the sensing data request result to the third-party AF.

[0161] Step 7: After the third-party AF obtains the perception data, it calls the perception data for calculation and completes the business processing.

[0162] Step 8: The third-party AF returns the service processing result to the UE, and the service ends.

[0163] By applying the service processing method provided in this embodiment, a processing solution for third-party AF calling perception data in a 6G core network architecture is provided for the perception capabilities of UE, network, etc., which enables the third-party AF to call the perception data stored in the core network, and then better execute services that require perception data and return it to the user end, thereby improving the user experience of third-party services.

[0164] In the embodiments provided above, the methods provided in the embodiments of the present application are described from the perspectives of the core network and the third-party AF. In order to implement the various functions of the methods provided in the embodiments of the present application, the core network device and the third-party AF may include hardware structures and software modules, and implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. One of the above functions may be executed in the form of hardware structures, software modules, or hardware structures plus software modules.

[0165] Corresponding to the business processing methods provided in the above-mentioned embodiments, the present application also provides a business processing device. Since the business processing device provided in the embodiments of the present application corresponds to the business processing methods provided in the above-mentioned embodiments, the implementation method of the business processing method is also applicable to the business processing device provided in this embodiment and will not be described in detail in this embodiment.

[0166] FIG8 is a schematic structural diagram of a service processing device provided in an embodiment of the present application. The service processing device may be used in a third-party AF, which is used to provide third-party services.

[0167] As shown in Figure 8, the device may include: a first receiving module 81, configured to receive a service request sent by a UE, wherein the service request carries service type information and service requirement information; a first sending module 82, configured to request the core network device to call perception data based on the service type information and service requirement information; the first receiving module 81 is also configured to receive the request response information returned by the core network device, and process the service request according to the request response information.

[0168] In some embodiments, the first sending module 82 is specifically configured to determine the perception data information that needs to be requested based on the business type information and the business demand information; and send a request for calling the perception data to the core network device, wherein the request for calling the perception data carries the perception data information and the identifier of the third-party AF, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data.

[0169] In some embodiments, the first receiving module 81 is specifically configured to receive perception data returned by the core network device that matches the perception data information, wherein the received perception data is returned by the core network device when it determines that the third-party AF has the right to call the perception data; perform business processing based on the received perception data, and return the business processing result to the UE.

[0170] In some embodiments, the request for calling perception data also carries the UE identifier of the UE; the first receiving module 81 is specifically configured to receive the perception data returned by the core network device that matches the perception data information and the UE identifier.

[0171] In some embodiments, the first receiving module 81 is specifically configured to receive the call failure information returned by the core network device, where the call failure information is returned by the core network device when it determines that the third-party AF has no right to call the perception data; and based on the call failure information, return the response information of the service request processing failure to the UE.

[0172] In some embodiments, the core network device includes: a NEF network element and a first network element, the first network element is used to store perception data; a first sending module 82, which is specifically configured to determine the perception data information that needs to be requested based on the service type information and service requirement information; and send a perception data open request to the NEF network element, wherein the perception data open request carries the perception data information and the identifier of the third-party AF, so that the NEF network element sends the perception data information and the identifier of the third-party AF to the first network element, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data stored in the first network element.

[0173] In some embodiments, the first receiving module 81 is specifically configured to receive perception data returned by the NEF network element that matches the perception data information, wherein the received perception data is returned to the NEF network element by the first network element when it determines that the third-party AF has the right to call the perception data; perform business processing based on the received perception data, and return the business processing result to the UE.

[0174] In some embodiments, the perception data open request also carries a UE identifier of the UE; the first receiving module 81 is specifically configured to receive the perception data returned by the NEF network element that matches the perception data information and the UE identifier.

[0175] In some embodiments, the first receiving module 81 is specifically configured to receive the call failure information returned by the NEF network element, where the call failure information is returned to the NEF network element by the first network element when it determines that the third-party AF has no right to call the perception data; and based on the call failure information, return the response information of the service request processing failure to the UE.

[0176] In some embodiments, the service request also carries the PLMN ID of the UE; the first sending module 82 is specifically configured to determine the perception data information according to the service type information and service requirement information in combination with the PLMN ID.

[0177] In some embodiments, the sensory data information includes at least one of the following:

[0178] The type of sensed data being requested;

[0179] The uploaded object information corresponding to the perception data requested.

[0180] By applying the service processing method provided in this embodiment, a processing solution for third-party AF calling perception data in a 6G core network architecture is provided for the perception capabilities of UE, network, etc., which enables the third-party AF to call the perception data stored in the core network, and then better execute services that require perception data and return it to the user end, thereby improving the user experience of third-party services.

[0181] Figure 9 is a schematic diagram of the structure of a service processing device provided in an embodiment of the present application. The service processing device can be used in core network equipment.

[0182] As shown in Figure 9, the device may include: a second receiving module 91, configured to receive a request for calling perception data sent by the third-party AF, and the third-party AF is used to provide third-party services; a second sending module 92, configured to return request response information to the third-party AF.

[0183] In some embodiments, the request for calling the perception data carries the perception data information to be called and the identifier of the third-party AF; wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data.

[0184] In some embodiments, the second sending module 92 is specifically configured to return the perception data matching the perception data information to the third-party AF if it is determined according to the identifier of the third-party AF that the third-party AF has the right to call the perception data.

[0185] In some embodiments, the request for calling the perception data also carries a UE identifier of the UE; the second sending module 92 is specifically configured to return the perception data matching the perception data information and the UE identifier to the third-party AF.

[0186] In some embodiments, the second sending module 92 is specifically configured to return a call failure message to the third-party AF if it is determined according to the identifier of the third-party AF that the third-party AF has no right to call the sensing data.

[0187] In some embodiments, the core network device includes: a NEF network element and a first network element, the first network element is used to store perception data; a second receiving module 91 is specifically configured for the NEF network element to receive a perception data open request sent by the third-party AF, the perception data open request carries the perception data information that needs to be requested to be called and the identifier of the third-party AF; the NEF network element sends the perception data information and the identifier of the third-party AF to the first network element, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data stored in the first network element.

[0188] In some embodiments, the second receiving module 91 is further configured to receive, by the NEF network element, perception data that matches the perception data information, wherein the received perception data is returned to the NEF network element by the first network element when it determines that the third-party AF has the right to call the perception data.

[0189] In some embodiments, the perception data open request also carries a UE identifier of the UE; the second receiving module 91 is specifically configured to receive, by the NEF network element, the perception data returned by the first network element that matches the perception data information and the UE identifier.

[0190] In some embodiments, the second sending module 92 is specifically configured to cause the NEF network element to return the received sensing data to the third-party AF.

[0191] In some embodiments, the second receiving module 91 is specifically configured to receive the returned call failure information by the NEF network element, where the call failure information is returned to the NEF network element by the first network element when determining that the third-party AF has no right to call the sensing data.

[0192] In some embodiments, the second sending module 92 is specifically configured to cause the NEF network element to return the received call failure information to the third-party AF.

[0193] In some embodiments, the sensory data information includes at least one of the following:

[0194] The type of sensed data being requested;

[0195] The uploaded object information corresponding to the perception data requested.

[0196] By applying the service processing method provided in this embodiment, a processing solution for third-party AF calling perception data in a 6G core network architecture is provided for the perception capabilities of UE, network, etc., which enables the third-party AF to call the perception data stored in the core network, and then better execute services that require perception data and return it to the user end, thereby improving the user experience of third-party services.

[0197] Please refer to Figure 10, which is a schematic diagram of the structure of a communication device 1500 provided in this embodiment. Communication device 1500 can be a network device or a user device, or a chip, chip system, or processor that supports the network device to implement the above method. It can also be a chip, chip system, or processor that supports the user device to implement the above method. This device can be used to implement the method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0198] The communication device 1500 may include one or more processors 1501. The processor 1501 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute computer programs, and process computer program data.

[0199] Optionally, the communication device 1500 may further include one or more memories 1502, on which a computer program 1504 may be stored. The processor 1501 executes the computer program 1504, causing the communication device 1500 to perform the method described in the above method embodiment. Optionally, the memory 1502 may also store data. The communication device 1500 and the memory 1502 may be provided separately or integrated together.

[0200] Optionally, the communication device 1500 may further include a transceiver 1505 and an antenna 1506. The transceiver 1505 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, and is configured to implement transceiver functions. The transceiver 1505 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, and is configured to implement a transmitting function.

[0201] Optionally, the communication device 1500 may further include one or more interface circuits 1507. The interface circuit 1507 is configured to receive code instructions and transmit the instructions to the processor 1501. The processor 1501 executes the code instructions to enable the communication device 1500 to perform the method described in the above method embodiment.

[0202] In one implementation, processor 1501 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0203] In one implementation, processor 1501 may store a computer program 1503. Computer program 1503, when executed on processor 1501, enables communication device 1500 to perform the method described in the above method embodiment. Computer program 1503 may be embedded in processor 1301. In this case, processor 1501 may be implemented by hardware.

[0204] In one implementation, the communication device 1500 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0205] The communication device described in the above embodiments may be a network device or a user device, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited to FIG10. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0206] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0207] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0208] (3) ASIC, such as modem;

[0209] (4) Modules that can be embedded in other devices;

[0210] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0211] (6)Others, etc.

[0212] If the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 11. The chip shown in Figure 11 includes a processor 1601 and an interface 1602. The number of processors 1601 can be one or more, and the number of interfaces 1602 can be multiple.

[0213] Optionally, the chip further includes a memory 1603, which is used to store necessary computer programs and data.

[0214] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present application.

[0215] The present application also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0216] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0217] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. Available media may be magnetic media (eg, floppy disks, hard disks, tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state disks (SSDs)).

[0218] Those skilled in the art will understand that the various numerical numbers such as first and second involved in this application are only for the convenience of description and are not used to limit the scope of the embodiments of this application, and also indicate the order of precedence.

[0219] In this application, at least one can also be described as one or more, and multiple can be two, three, four or more, which is not limited in this application. In the embodiments of this application, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0220] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., a magnetic disk, an optical disk, a memory, a programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0221] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0222] Computer systems may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The client and server relationship arises through computer programs running on the respective computers and having a client-server relationship to each other.

[0223] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this application can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of this application can be achieved. This is not limited herein.

[0224] Furthermore, it should be understood that the various embodiments described herein may be implemented individually or in combination with other embodiments where the solution permits.

[0225] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments applied for herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

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

Claims

1. A business processing method, characterized in that: Applied to a third-party application function AF, the third-party AF is used to provide third-party services, and the method includes: receiving a service request sent by a user equipment UE, where the service request carries service type information and service requirement information; Requesting the core network device to call perception data based on the service type information and service requirement information; Receive the request response information returned by the core network device, and process the service request according to the request response information.

2. The method according to claim 1, characterized in that The requesting the core network device to call the perception data according to the service type information and the service requirement information includes: Determining the perception data information that needs to be requested based on the business type information and business requirement information; A request for calling perception data is sent to the core network device, where the request for calling perception data carries the perception data information and the identifier of the third-party AF, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call perception data.

3. The method according to claim 2, characterized in that The receiving the request response information returned by the core network device and processing the service request according to the request response information includes: receiving, from the core network device, perception data that matches the perception data information, wherein the received perception data is returned by the core network device when determining that the third-party AF has the right to call the perception data; Perform service processing according to the received perception data, and return the service processing result to the UE.

4. The method according to claim 3, characterized in that The request for calling the sensing data also carries a UE identifier of the UE; The receiving, returned by the core network device, the perception data that matches the perception data information, includes: Receive perception data returned by the core network device that matches the perception data information and the UE identifier.

5. The method according to claim 2, characterized in that The receiving the request response information returned by the core network device and processing the service request according to the request response information includes: receiving call failure information returned by the core network device, where the call failure information is returned by the core network device when determining that the third-party AF is not authorized to call the perception data; Based on the call failure information, response information indicating that the service request processing failed is returned to the UE.

6. The method according to claim 1, characterized in that The core network device includes: a network capability exposure function NEF network element and a first network element, wherein the first network element is used to store perception data; The requesting the core network device to call the perception data according to the service type information and the service requirement information includes: Determining the perception data information that needs to be requested based on the business type information and business requirement information; Sending a perception data open request to the NEF network element, wherein the perception data open request carries the perception data information and the identifier of the third-party AF, so that the NEF network element sends the perception data information and the identifier of the third-party AF to the third-party AF. A network element, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the sensing data stored in the first network element.

7. The method according to claim 6, characterized in that The receiving the request response information returned by the core network device and processing the service request according to the request response information includes: receiving, from the NEF network element, sensing data that matches the sensing data information, wherein the received sensing data is returned to the NEF network element by the first network element when determining that the third-party AF has the right to call the sensing data; Perform service processing according to the received perception data, and return the service processing result to the UE.

8. The method according to claim 7, characterized in that The perception data open request also carries the UE identifier of the UE; The receiving the perception data returned by the NEF network element and matching the perception data information includes: Receive the perception data returned by the NEF network element and matching the perception data information and the UE identifier.

9. The method according to claim 6, characterized in that The receiving the request response information returned by the core network device and processing the service request according to the request response information includes: receiving call failure information returned by the NEF network element, where the call failure information is returned to the NEF network element by the first network element when determining that the third-party AF has no right to call the perception data; Based on the call failure information, response information indicating that the service request processing failed is returned to the UE.

10. The method according to claim 2 or 6, characterized in that The service request also carries the public land mobile network identifier PLMN ID of the UE; The determining, based on the service type information and the service requirement information, of the perception data information to be requested includes: The perception data information is determined according to the service type information and the service requirement information, and in combination with the PLMN ID.

11. The method according to any one of claims 2 to 10, characterized in that The perception data information includes at least one of the following: The type of sensed data being requested; The uploaded object information corresponding to the perception data requested.

12. A business processing method, characterized in that: Applied to core network equipment, the method includes: receiving a request for calling perception data sent by a third-party application function AF, where the third-party AF is used to provide third-party services; Return request response information to the third-party AF.

13. The method according to claim 12, characterized in that The request for calling the perception data carries the perception data information to be called and the identifier of the third-party AF; wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data.

14. The method according to claim 13, characterized in that The returning the request response information to the third-party AF includes: If it is determined according to the identifier of the third-party AF that the third-party AF has the right to call the perception data, the perception data matching the perception data information is returned to the third-party AF.

15. The method according to claim 14, characterized in that The request for calling the sensing data also carries a UE identifier of the user equipment UE; The returning the perception data matching the perception data information to the third-party AF includes: Returning the perception data that matches the perception data information and the UE identifier to the third-party AF.

16. The method according to claim 13, characterized in that The returning the request response information to the third-party AF includes: If it is determined according to the identifier of the third-party AF that the third-party AF does not have the right to call the perception data, call failure information is returned to the third-party AF.

17. The method according to claim 12, wherein: The core network device includes: a network capability exposure function NEF network element and a first network element, wherein the first network element is used to store perception data; The receiving a request for calling sensing data sent by the third-party AF includes: The NEF network element receives the sensing data open request sent by the third-party AF, where the sensing data open request carries the sensing data information to be requested and the identifier of the third-party AF; The NEF network element sends the perception data information and the identifier of the third-party AF to the first network element, wherein the identifier of the third-party AF is used to determine whether the third-party AF has the right to call the perception data stored in the first network element.

18. The method according to claim 17, characterized in that After the NEF network element sends the sensing data information and the identifier of the third-party AF to the first network element, the method further includes: The NEF network element receives the perception data matching the perception data information, wherein the received perception data is returned to the NEF network element when the first network element determines that the third-party AF has the right to call the perception data.

19. The method according to claim 18, characterized in that The perception data open request also carries a UE identifier of the UE; The NEF network element receives the perception data matching the perception data information, including: The NEF network element receives the perception data returned by the first network element and matching the perception data information and the UE identifier.

20. The method according to any one of claims 18 to 19, characterized in that The returning the request response information to the third-party AF includes: The NEF network element returns the received sensing data to the third-party AF.

21. The method according to claim 17, wherein After the NEF network element sends the sensing data information and the identifier of the third-party AF to the first network element, the method further includes: The NEF network element receives the returned call failure information, where the call failure information is returned to the NEF network element by the first network element when determining that the third-party AF has no right to call the sensing data.

22. The method according to claim 21, characterized in that The returning the request response information to the third-party AF includes: The NEF network element returns the received call failure information to the third-party AF.

23. The method according to any one of claims 13 to 22, characterized in that The perception data information includes at least one of the following: The type of sensed data being requested; The uploaded object information corresponding to the perception data requested.

24. A business processing device, characterized in that: Applied to a third-party application function AF, the third-party AF is used to provide third-party services, and the device includes: A first receiving module is configured to receive a service request sent by a user equipment UE, where the service request carries service type information and service requirement information; A first sending module is configured to request the core network device to call the perception data according to the service type information and the service requirement information; The first receiving module is further configured to receive the request response information returned by the core network device and process the service request according to the request response information.

25. A business processing device, characterized in that: Applied to core network equipment, the device includes: a second receiving module configured to receive a request for calling perception data sent by a third-party application function AF, where the third-party AF is used to provide a third-party service; The second sending module is configured to return request response information to the third-party AF.

26. A communication device, wherein: include: transceiver; Memory; A processor is connected to the transceiver and the memory respectively, and is configured to control the wireless signal reception and transmission of the transceiver by executing computer-executable instructions on the memory, and can implement the method described in any one of claims 1 to 23.

27. A computer storage medium, wherein: The computer storage medium stores computer-executable instructions; after the computer-executable instructions are executed by the processor, the method according to any one of claims 1 to 23 can be implemented.

28. A business processing system, characterized in that: The system includes: a third-party application function AF and a core network device; The third party AF is used to perform the method according to any one of claims 1 to 11; The core network device is configured to execute the method according to any one of claims 12 to 23.

Images