A capability opening method, device, communication equipment and storage medium

Abstract

The present application discloses a capability opening method, apparatus, communication device and storage medium. The method comprises: a first device receives capability opening rule configuration information from a second device, the capability opening rule configuration information comprises a capability opening mode; the capability opening mode is used to indicate the first device as a capability opening mode of a third device.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a capability opening method, apparatus, communication equipment and storage medium. Background Art

[0002] As a new generation of communication technology, the fifth generation mobile communication technology (5G) has many advantages such as large bandwidth, low latency, high reliability, high connectivity, and ubiquitous network, thus promoting the rapid development and change of vertical industries, such as the rise of smart medical care, smart education, and smart agriculture.

[0003] Multi-access edge computing (MEC) technology, as one of the key technologies for 5G evolution, is an information technology (IT) general platform with wireless network information application program interface (API) interaction capabilities, as well as computing, storage, and analysis functions. Relying on MEC technology, traditional external applications can be brought into the operator to provide users with localized application services, which are closer to users, thereby improving user experience and bringing more value into the edge network.

[0004] Combining 5G and MEC technologies can introduce different technology combinations for different industry demand scenarios, such as Quality of Service (QoS), end-to-end network slicing, network capability exposure, edge cloud, etc., to provide customized solutions.

[0005] Related technologies use Figure 1 The solution shown in Figure 5 combines 5G and MEC technology, which has security risks. Therefore, in some scenarios, by setting up equipment (or gateway), a service proxy for network capability opening between the core network and the MEC platform (MEP) and between the user plane function (UPF) and the MEP is implemented, thereby ensuring and improving the network security capabilities of the communication system. However, in this scenario, there is currently no effective solution for how to open up network capabilities. Summary of the invention

[0006] To solve the existing technical problems, the embodiments of the present application provide a capability opening method, apparatus, communication device and storage medium.

[0007] The technical solution of the embodiment of the present application is implemented as follows:

[0008] In a first aspect, an embodiment of the present application provides a capability opening method, the method comprising:

[0009] The first device receives capability exposure rule configuration information from the second device, where the capability exposure rule configuration information includes a capability exposure mode;

[0010] The capability opening mode is used to indicate a mode in which the first device opens capabilities to a third device.

[0011] In the above solution, the capability opening method includes: direct opening method and / or indirect opening method.

[0012] In the above solution, the capability opening rule configuration information further includes: an identity identifier of a third device and a capability identifier corresponding to the third device.

[0013] In the above solution, the capability opening rule configuration information also includes: capability opening conditions.

[0014] In the above solution, the method further includes: the first device sends a capability exposure information list to the third device; the capability exposure information list is used to indicate the capabilities that the first device can provide and the form of the exposed capabilities.

[0015] In the above solution, the capability exposure information list includes a capability list and a capability form list;

[0016] The capability list includes capability identifiers corresponding to capabilities that the first device can provide; and the capability form list includes information on how to obtain the capabilities.

[0017] In the above scheme, the method further comprises:

[0018] The first device receives a capability opening request from the third device, where the capability opening request is used to request the first device to open a capability;

[0019] The first device sends first information to the third device, where the first information is used to indicate a capability basis file that needs to be provided by the third device;

[0020] The first device receives a capability-based document from the third device;

[0021] The first device processes the capability exposure information based on the capability profile, and sends the processed capability exposure information to the third device.

[0022] In the above solution, the capability includes at least one of the following: location service capability, wireless network information service capability, monitoring capability, pre-configuration capability, and policy / billing capability.

[0023] In the above solution, the first information includes at least one capability identifier.

[0024] In the above solution, the first device receives the capability basis file from the third device, including:

[0025] The first device receives second information from the third device, where the second information includes the at least one capability identifier and a capability reference file corresponding to each capability identifier.

[0026] In the above scheme, the method further comprises:

[0027] When the first device cannot obtain the processed capability exposure information based on the capability reference file, it sends third information to the third device, wherein the third information includes reason indication information for not providing the processed capability exposure information and a capability identifier corresponding to the reason indication information.

[0028] In the above solution, the capability-based document includes at least one of the following:

[0029] Map file, clock frequency of the analysis and processing capability open information, time range of the analysis and processing capability open information, and basis information of the analysis and processing capability open information.

[0030] In the above solution, before the first device receives the capability opening rule configuration information from the second device, the method further includes:

[0031] The first device completes access authentication with the second device and the third device;

[0032] The first device obtains capability exposure information from the fourth device.

[0033] In the above solution, the capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / billing capability identifier.

[0034] In a second aspect, an embodiment of the present application further provides a capability opening method, the method comprising:

[0035] The second device sends capability exposure rule configuration information to the first device, where the capability exposure rule configuration information includes a capability exposure mode;

[0036] The capability opening mode is used to indicate a mode in which the first device opens capabilities to a third device.

[0037] In the above solution, the capability opening method includes: direct opening method and / or indirect opening method.

[0038] In the above solution, the capability opening rule configuration information further includes: an identity identifier of a third device and a capability identifier corresponding to the third device.

[0039] In the above solution, the capability opening rule configuration information also includes: capability opening conditions.

[0040] In the above scheme, the method further comprises:

[0041] The second device and the third device complete access authentication of the first device.

[0042] In the above solution, the capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / billing capability identifier.

[0043] In a third aspect, an embodiment of the present application further provides a capability opening method, the method comprising:

[0044] The third device sends a capability opening request to the first device, where the capability opening request is used to request the first device to open a capability;

[0045] The third device receives first information from the first device, where the first information is used to indicate a capability basis file that needs to be provided by the third device;

[0046] The third device sends a capability basis file to the first device;

[0047] The third device receives the processed capability exposure information from the first device; the processed capability exposure information is obtained by the first device processing the capability exposure information based on the capability reference file.

[0048] In the above solution, the capability includes at least one of the following: location service capability, wireless network information service capability, monitoring capability, pre-configuration capability, and policy / billing capability.

[0049] In the above solution, the first information includes at least one capability identifier.

[0050] In the above solution, the third device sends the capability basis file to the first device, including:

[0051] The third device sends second information to the first device, where the second information includes the at least one capability identifier and a capability reference file corresponding to each capability identifier.

[0052] In the above solution, when the third device does not receive the processed capability opening information from the first device, the method further includes:

[0053] The third device receives third information from the first device, where the third information includes reason indication information for not providing the processed capability exposure information and a capability identifier corresponding to the reason indication information.

[0054] In the above solution, the capability-based document includes at least one of the following:

[0055] Map file, clock frequency of the analysis and processing capability open information, time range of the analysis and processing capability open information, and basis information of the analysis and processing capability open information.

[0056] In the above scheme, the method further comprises:

[0057] The third device and the second device complete access authentication of the first device.

[0058] In the above scheme, the method further comprises:

[0059] The third device receives a capability exposure information list from the first device, where the capability exposure information list is used to indicate capabilities that the first device can provide and a form of the exposed capabilities.

[0060] In the above solution, the capability exposure information list includes a capability list and a capability form list;

[0061] The capability list includes capability identifiers corresponding to capabilities that the first device can provide; and the capability form list includes information on how to obtain the capabilities.

[0062] In the above solution, the capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / billing capability identifier.

[0063] In a fourth aspect, an embodiment of the present application further provides a capability opening device, the device comprising a first receiving unit for receiving capability opening rule configuration information from a second device, the capability opening rule configuration information comprising a capability opening mode; the capability opening mode is used to indicate a mode in which the first device opens capabilities to a third device.

[0064] In the fifth aspect, an embodiment of the present application also provides a capability opening device, which includes a second sending unit for sending capability opening rule configuration information to a first device, wherein the capability opening rule configuration information includes a capability opening mode; the capability opening mode is used to indicate the mode in which the first device opens the capability to a third device.

[0065] In a sixth aspect, an embodiment of the present application further provides a capability opening device, the device comprising: a third sending unit and a third receiving unit; wherein,

[0066] The third sending unit is used to send a capability opening request to the first device, where the capability opening request is used to request the first device to open a capability;

[0067] The third receiving unit is configured to receive first information from the first device when the opening mode of the capability requested to be opened is an indirect opening mode, wherein the first information is used to indicate a capability basis file that needs to be provided by the third device;

[0068] The third sending unit is further used to send a capability basis file to the first device;

[0069] The third receiving unit is further configured to receive processed capability exposure information from the first device; the processed capability exposure information is obtained by the first device processing the capability exposure information based on the capability basis file.

[0070] In the seventh aspect, the embodiments of the present application further provide a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the method described in the first aspect, the second aspect or the third aspect of the embodiments of the present application are implemented.

[0071] In the eighth aspect, an embodiment of the present application also provides a communication device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the method described in the first aspect, the second aspect, or the third aspect of the embodiment of the present application are implemented.

[0072] The capability opening method, apparatus, communication device and storage medium provided in the embodiments of the present application, on the one hand, the first device receives capability opening rule configuration information from the second device, and the capability opening rule configuration information includes a capability opening mode; the capability opening mode is used to indicate the first device as a capability opening mode for the third device. Using the technical solution of the embodiments of the present application, a new capability opening mode based on the industry gateway (i.e., the first device) is proposed, in which the second device directly configures the opening mode of each capability of the first device. This mode can ensure the feasibility of the network capability opening function under the industry cloud network fusion system architecture, and enrich the industry's application scenarios in network capability opening.

[0073] On the other hand, the third device sends a capability opening request to the first device, the capability opening request is used to request the first device to open a capability; the third device receives first information from the first device, the first information is used to indicate a capability basis file that needs to be provided by the third device; the third device sends a capability basis file to the first device; the third device receives the processed capability opening information from the first device; the processed capability opening information is obtained by the first device processing the capability opening information based on the capability basis file. Using the technical solution of the embodiment of the present application, an indirect capability opening method based on an industry gateway (i.e., the first device) is proposed, in which the capability opening information obtained from the capability source by the industry gateway (i.e., the first device) is processed and provided to the third device in an indirect opening manner. This indirect opening method can save bandwidth and MEP computing resources and reduce the latency of network capability opening. BRIEF DESCRIPTION OF THE DRAWINGS

[0074] Figure 1 This is a schematic diagram of the system structure combining 5G and MEC technologies in related technologies;

[0075] Figure 2 This is a schematic diagram of the system structure of 5G industry cloud network integration according to an embodiment of the present application;

[0076] Figure 3 The process diagram of the capability opening method of the embodiment of the present application is as follows: Figure 1 ;

[0077] Figure 4 The process diagram of the capability opening method of the embodiment of the present application is as follows: Figure 2 ;

[0078] Figure 5 The process diagram of the capability opening method of the embodiment of the present application is as follows: Figure 3 ;

[0079] Figure 6 The process diagram of the capability opening method of the embodiment of the present application is as follows: Figure 4 ;

[0080] Figure 7 This is a schematic diagram of the network capability exposure architecture of 5G industry cloud-network integration in the application embodiment of this application;

[0081] Figure 8 The interactive process of the capability opening method of the embodiment of the present application is shown as follows Figure 1 ;

[0082] Fig. 9 The interactive process of the capability opening method of the embodiment of the present application is shown as follows Figure 2 ;

[0083] Fig.10 The structure diagram of the capability opening device in the embodiment of the present application is shown in FIG. Figure 1 ;

[0084] Fig.11 The structure diagram of the capability opening device in the embodiment of the present application is shown in FIG. Figure 2 ;

[0085] Fig.12 The structure diagram of the capability opening device in the embodiment of the present application is shown in FIG. Figure 3 ;

[0086] Fig.13 A schematic diagram of the hardware composition structure of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0087] The present application is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0088] like Figure 1 As shown in the figure, among the related technologies, the solutions combining 5G and MEC technologies mainly include:

[0089] 1) To enable low-latency, high-bandwidth, and high-reliability edge applications in vertical industries, UPF is deployed in the industry customer park, close to the MEC edge server (also known as the MEC platform (MEP)), and forwards data to the MEP through the local traffic diversion technology of UPF (i.e., uplink filter / IPv6 branching point (UL-CL / IPv6 BP)).

[0090] 2) The application function (AF) in the core network is moved down to the MEP side to provide better data flow control strategies (such as encoding strategies, QoS strategies, routing strategies, etc.) for applications deployed on the MEP.

[0091] but Figure 1 The solution shown in the figure that combines 5G and MEC technologies has the following security risks:

[0092] First, the security risks caused by the deployment location of UPF and MEP.

[0093] Specifically, UPF and MEP are separate in terms of functional logic, but can be deployed in two ways: combined deployment and separate deployment; where combined deployment means deploying UPF and MEP in the same machine room or even on the same physical device; separate deployment means deploying UPF and MEP in different machine rooms. In actual application, the combined deployment method is not suitable for vertical industries (such as smart medical care, smart education, smart agriculture, etc.) because: if UPF and MEP are deployed in the operator's machine room, it violates the security requirements of industry customers that their application data cannot leave the park; and if UPF and MEP are deployed in the industry customer's park machine room, it is very unfavorable for the operator's operation and maintenance, and will increase the security risk for the entire core network. Therefore, for vertical industry applications, UPF and MEP should be deployed separately. Specifically, UPF can be deployed in the operator's machine room, and MEP can be deployed in the industry customer's park machine room. However, in the scenario where UPF and MEP are deployed separately, the data security between UPF and MEP cannot be guaranteed, and there is a security risk.

[0094] Second, security risks caused by ubiquitous network access.

[0095] Specifically, Figure 1 The architecture shown does not involve access and data transmission of non-5G networks. In other words, the relevant technology does not provide an access solution for non-5G networks when 5G and MEC technologies are combined. There are many types of access technologies for terminals in vertical industries. In addition to 5G, they also include the fourth generation mobile communication technology (4G), wireless fidelity (Wi-Fi), Bluetooth, Zigbee, narrowband Internet of Things (NB-IoT), wired network, etc. The terminal data accessed by these non-5G networks may not be transmitted to the MEP through the 5G network, making it impossible for the MEP to perform access control, traffic control and security monitoring on the terminal data of various access technology types, and unable to ensure the network and data security of the MEP, which poses a security risk.

[0096] Third, security risks caused by the opening of network capabilities.

[0097] Specifically, Figure 1As shown, in the related technology, the network capability exposure function (Service Capability Exposure Function, abbreviated as SCEF) of the MEP is realized by connecting the AF on the MEP with the network exposure function (NEF) of the 5G core network (5GC, 5G Core). However, due to the different security levels on each MEP, when the MEP opens its network capabilities to the outside, the core network may be attacked due to security vulnerabilities in the network capability application on a certain MEP or problems with the security mechanism of a certain MEP itself, posing a security risk.

[0098] In addition, in related technologies, MEP can only obtain network capabilities from 5GC, and the network capabilities that 5GC can provide cannot fully meet and accurately cover the business needs of vertical industries, such as the location information of terminals that are not connected to 5G networks. At the same time, the MEP network capability acquisition data sources are diverse, including 5GC, Radio Access Network (RAN) and third-party systems, but related technologies lack unified authentication, unified supervision and unified settlement solutions for network capabilities.

[0099] Fourth, security risks caused by local diversion.

[0100] Specifically, Figure 1 As shown, in the related technology, data forwarding from the terminal to the local MEP relies on the UL-CL / IPv6 BP technology of the UPF, which implements local traffic diversion based on the IP quintuple or prefix of the message. In actual application, for vertical industries, using the UL-CL / IPv6 BP technology for local traffic diversion will expose the IP address information of the MEP of industry users on the public network, which not only poses the risk of user privacy data leakage, but also may lead to network attacks against the MEP IP address, posing network security risks.

[0101] Among them, in actual application, in order to avoid the network security risks caused by using UL-CL / IPv6 BP technology for local diversion, it is also possible to consider setting a dedicated data network name (DNN) for the MEP to achieve local diversion. However, this method requires a separate DNN to be configured for each MEP, and a large number of DNN configurations need to be performed in the core network. In addition, for the scenario where a terminal accesses multiple MEPs, the user needs to constantly switch DNNs on the terminal, which seriously affects the user experience.

[0102] In addition, in actual applications, in vertical industry application scenarios, in addition to the need for local diversion, there is also a need for wide-area interconnection between MEPs, such as data sharing between different hospitals, remote collaborative diagnosis and other scenarios. However, in related technologies, UPF only supports terminal-to-data network (DN) protocol data unit (PDU) sessions, and does not support DN-to-DN connections. In other words, UPF only supports terminal-to-MEP data connections, and does not support interconnection between MEPs.

[0103] Based on this, in various embodiments of the present application, such as Figure 2 As shown, an industry gateway (also called a gateway) is set up, and through the industry gateway, a business agent for network capability exposure between the core network and MEP and between UPF and MEP is realized; in this way, the data security of the communication system can be guaranteed, the network security capability of the communication system can be improved, thereby improving the user experience.

[0104] For example, in actual applications, the industry gateway is set between UPF and MEP; MEP can be a device in the MEC network.

[0105] At least based on Figure 2 The system structure shown is schematically illustrated, and the following embodiments of the present application are proposed.

[0106] An embodiment of the present application provides a capability opening method. Figure 3 The process diagram of the capability opening method of the embodiment of the present application is as follows: Figure 1 ;like Figure 3 As shown, the method includes:

[0107] Step 101: A first device receives capability exposure rule configuration information from a second device, where the capability exposure rule configuration information includes a capability exposure mode; the capability exposure mode is used to indicate a capability exposure mode of the first device as a third device.

[0108] The capability opening method of this embodiment is applied to a first device. Figure 2 The industry gateway shown in may also be referred to as a gateway, a gateway device, etc., and may be expressed as iGW in English. The second device may be a management system or an operation system, such as a business support system (BSS) / operation support system (OSS). The third device may be Figure 2The MEP shown in may also be referred to as an MEC platform, an MEC server, etc. The embodiment of the present application does not limit the names of the first device, the second device, and the third device, as long as the respective functions of the first device, the second device, and the third device can be realized.

[0109] In this embodiment, before the first device performs the service agent of network capability opening, it first needs to obtain capability opening rule configuration information from the second device, the capability opening rule configuration information or also called configuration information, and the configuration information includes capability opening rules. The capability opening rule configuration information includes opening rules for each capability that can be opened.

[0110] In this embodiment, the capability exposure rule configuration information at least includes a capability exposure mode, wherein, optionally, the capability exposure mode includes: a direct exposure mode and / or an indirect exposure mode. The direct exposure mode indicates a mode in which the first device directly sends the acquired capability exposure information (or data) to the third device; the indirect exposure mode indicates a mode in which the first device processes the acquired capability exposure information (or data) and sends the processed capability exposure information to the third device; the processing of the capability exposure information (or data) includes but is not limited to calculation processing, encapsulation operation, etc., and can be indirectly provided to the third device in the form of, for example, an analysis report.

[0111] In each embodiment of the present application, the capability exposure information is the capability exposure information that can be obtained by the third device from the network capability source (fourth device) through the service proxy function of the first device, and the capability exposure information can also be called capability exposure data, network capability exposure information (or data), etc. Among them, the network capability source (fourth device) can be at least one device in a wireless access network, a core network, and a third-party network that can provide capabilities.

[0112] In some optional embodiments, the capability opening rule configuration information further includes: an identity identifier of a third device and a capability identifier corresponding to the third device.

[0113] The capabilities described in each embodiment of the present application may also be referred to as network capabilities. The capabilities that the first device can open (that is, the capabilities that the network capability source can provide) include at least one of the following: location service capabilities, wireless network information service capabilities, monitoring capabilities, pre-configuration capabilities, and policy / billing capabilities.

[0114] Correspondingly, the capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / charging capability identifier. The capability identifier may also be referred to as a network capability identifier.

[0115] In this embodiment, the capability exposure rule configuration information includes the capability exposure rules of each third device connected to the first device, that is, the capability exposure rule configuration information includes the identity of each third device, all capability identifiers corresponding to each third device, and the capability exposure mode corresponding to each capability identifier (direct exposure mode and / or indirect exposure mode).

[0116] In some optional embodiments, the capability exposure rule configuration information also includes: capability exposure conditions. Exemplarily, the capability exposure conditions represent the conditions under which users in the third device can obtain capability exposure information of the corresponding capability. For example, in a third device, for the location service capability identifier, the corresponding capability exposure condition may be available to all users, that is, all users in the third device can obtain the capability exposure information corresponding to the location service capability; and for the monitoring capability identifier, the corresponding capability exposure condition may be the highest-level user, that is, the highest-level user in the third device can obtain the capability exposure information corresponding to the monitoring capability.

[0117] Exemplarily, the content included in the above-mentioned capability exposure rule configuration information can be referred to as shown in Table 1, for example, including the identifier of the second device (such as MEP) accessing the first device, the capability identifier used by each second device, the capability exposure method corresponding to each capability identifier (direct exposure method and / or indirect exposure method) and the capability exposure condition; of course, the content included in the capability exposure rule configuration information is not limited to the above examples, and can also include other content, for example, other content can be carried in "other constraints".

[0118] Table 1

[0119]

[0120]

[0121] In some optional embodiments of the present application, the method further includes: the first device sending a capability exposure information list to the third device; the capability exposure information list is used to indicate capabilities that the first device can provide and the form of the exposed capabilities.

[0122] In this embodiment, after obtaining the capability exposure rule configuration information from the second device, the first device sends a capability exposure information list to the connected third device, and the capability exposure information list may also be referred to as a capability exposure data list, a capability exposure information (data) set, etc. The capability exposure information list is used to provide the third device with the capabilities authorized by the first device and the form of each capability being exposed, so as to indicate which capabilities the third device can obtain from the first device and the form of each capability being exposed.

[0123] Optionally, the capability exposure information list includes at least a capability list and a capability form list; wherein the capability list includes capability identifiers corresponding to the capabilities that the first device can provide, that is, the capability list includes at least one capability identifier; the capability form list includes capability acquisition method information (direct acquisition and / or indirect acquisition, and corresponding to the above-mentioned capability exposure method).

[0124] Exemplarily, the content included in the above capability exposure information list can refer to Table 2, for example, including capability identifiers corresponding to the capabilities that the first device can provide, and a method for obtaining the capabilities corresponding to each capability identifier, etc. Among them, the method for obtaining the capabilities is, for example, the wireless network information service capability report, the real-time heat map of location distribution, the motion trajectory distribution map, etc. shown in Table 2.

[0125] Table 2

[0126] Capability Identification How to acquire abilities Positioning capability indicator Real-time heat map of UE location distribution, UE movement trajectory distribution map Wireless Network Information Service Capability Identifier Wireless Network Information Service Capability Report … …

[0127] In each embodiment of the present application, the first device can open the capabilities obtained from the fourth device to the third device, and the capabilities include at least one of the following: location service capabilities, wireless network information service capabilities, monitoring capabilities, pre-configuration capabilities, and policy / billing capabilities.

[0128] Each capability corresponds to a unique capability identifier, and the function of the capability identifier is to indicate the open capability.

[0129] Exemplarily, the capability identifier may be implemented in the following ways: bitmap, string, numerical parameter, etc. Among them:

[0130] Bitmap implementation method: Each capability identifier can be represented by a bit in the bitmap. For example, the bitmap uses N bits (bits) to store field information. For example, the 0th to 4th bits in Table 3 can be used to represent the wireless network information service (RNIS) capability identifier, location service (LBS) capability identifier, monitoring capability identifier, pre-configuration capability identifier and policy / billing capability identifier in turn; other bits are reserved for identifiers of other network capability types. When it is necessary to support the opening of a certain type of capability, the corresponding bit is set to 1, and if it is not supported, it is set to 0. For example, when the first device supports opening the location service capability and the wireless network information service (RNIS) capability to the third device, the first bit and the second bit from the right side of Table 3 are set to 1, and the remaining bits are set to 0.

[0131] Table 3

[0132] 0 …… 0 0 0 0 0 0 1 1

[0133] String implementation: Each capability identifier can be represented by a string, for example, "ce-RNIS" can be used to represent the wireless network information service capability identifier, and "ce-LBS" can be used to represent the location service capability identifier. Of course, the embodiments of the present application are not limited to using the above-mentioned strings to represent the corresponding capability identifiers, and any set string can be used to represent the corresponding capability identifier.

[0134] Numeric parameter implementation method: Each capability identifier can be represented by a number. For example, 01 represents the wireless network information service (RNIS) capability identifier, 02 represents the location service capability identifier, 03 represents the monitoring capability identifier, 04 represents the pre-configuration capability identifier, 05 represents the policy / billing capability identifier, etc. Of course, the embodiments of the present application are not limited to using the above numbers to represent the corresponding capability identifiers, and any set numbers can be used to represent the corresponding capability identifiers.

[0135] In each embodiment of the present application, the capability form list includes the acquisition form of the capability corresponding to the capability identifier, that is, the capability exposure mode (direct exposure mode and / or indirect exposure mode) corresponding to each capability. The capability exposure mode identifier in this embodiment corresponds to the capability exposure mode, which is used to indicate the form in which the first device exposes the capability to the third device.

[0136] In each embodiment of the present application, three capability exposure forms may be used to identify the corresponding three capability exposure modes:

[0137] Direct open mode flag: used to indicate that the first device opens the capability to the third device in a direct open mode;

[0138] Indirect open form identifier: used to indicate that the first device opens the capability to the third device in an indirect open manner;

[0139] Both direct open form and indirect open form support identification: used to indicate that the first device opens the capability to the third device in a direct open mode and an indirect open mode;

[0140] Exemplarily, the implementation of the capability exposure form identifier includes at least three of the following: bitmap, string, numerical parameter, etc. Among them:

[0141] Bitmap implementation: Each capability exposure form identifier can be represented by a bit in the bitmap. For example, the bitmap uses 3 bits to store field information, similar to the above Table 3, from bit 0 to bit 2, it represents the direct exposure form identifier, the indirect exposure form identifier, and the direct exposure form and indirect exposure form support identifier. When a capability exposure form is supported, the corresponding bit is set to 1, and the remaining positions are set to 0.

[0142] String implementation: Each capability exposure form identifier can be represented by a string. For example, "direct-ce" represents a direct exposure form identifier, "indirect-ce" represents an indirect exposure form identifier, and "optional-ce" represents an identifier that is supported by both direct and indirect exposure forms. Of course, the embodiments of the present application are not limited to using the above-mentioned strings to represent the corresponding capability exposure form identifiers, and any set string can be used to represent the corresponding capability exposure form identifier.

[0143] Numeric parameter implementation method: Each capability exposure form identifier can be represented by a number. For example: 01 represents a direct exposure form identifier, 02 represents an indirect exposure form identifier, and 03 represents an identifier that supports both direct and indirect exposure forms. Of course, the embodiments of the present application are not limited to using the above numbers to represent the corresponding capability exposure form identifiers, and any set numbers can be used to represent the corresponding capability exposure form identifiers.

[0144] In some optional embodiments of the present application, before the first device receives the capability opening rule configuration information from the second device, the method further includes: completing access authentication between the first device, the second device, and the third device.

[0145] In this embodiment, before executing step 101, access authentication is completed between the first device, the second device, and the third device. The access authentication process between the first device, the second device, and the third device at least includes: when the first device accesses the second device, it reports its authentication requirements and a list of supported capability information, the second device sends authentication information about the third device to the first device, and the second device authenticates the accessed third device based on the authentication information.

[0146] In some optional embodiments of the present application, the method further includes: the first device obtains capability opening information from a fourth device.

[0147] In this embodiment, after the first device completes access authentication, the first device may obtain capability exposure information from the fourth device. The capability exposure information is information or data provided by the fourth device, and may also be referred to as capability data (or capability information).

[0148] In some optional embodiments of the present application, based on the above embodiments, such as Figure 4 As shown, the method may also include:

[0149] Step 102: The first device receives a capability opening request from the third device, where the capability opening request is used to request the first device to open a capability;

[0150] Step 103: The first device sends first information to the third device, where the first information is used to indicate a capability reference file that needs to be provided by the third device;

[0151] Step 104: The first device receives the capability document from the third device;

[0152] Step 105: The first device processes the capability exposure information based on the capability basis file, and sends the processed capability exposure information to the third device.

[0153] In each embodiment of the present application, the capability opening request may also be referred to as a request. In this embodiment, the name of the request is not limited, as long as it can realize the request to open the capability of the first device. In other implementations, the first device may also receive indication information from the third device, and the indication information includes a capability opening request for requesting the first device to open capabilities, and indicating which capabilities to open and how to open the capabilities.

[0154] Exemplarily, the capability opening request (or the above-mentioned indication information) includes a capability opening request identifier and a capability opening information list corresponding to the requested capability. Among them, the implementation method of the capability opening information list can refer to the above-mentioned embodiment, which will not be repeated here. The capability opening information list can be used as a sub-parameter in the capability opening request (or the above-mentioned indication information) to request which capabilities the first device opens and indicate the opening method of each capability.

[0155] The capability opening request identifier is used to indicate a request for the first device to open a capability. Exemplarily, the capability opening request identifier can be implemented in at least the following ways: a Boolean variable, a string, a numerical variable, or a bitmap.

[0156] Exemplarily, as shown in Table 4, the capability opening request identifier is represented by a Boolean variable, for example: "False" represents not requesting capability opening, and "True" represents requesting capability opening; the capability opening request identifier is represented by a string, that is, a string is used to identify whether capability opening is requested, for example, "No" represents not requesting capability opening, and "Yes" represents requesting capability opening; the capability opening request identifier is represented by a numerical variable, that is, a numerical number is used to identify whether network capability opening is requested, for example, 0 represents not requesting capability opening, and the remaining numbers represent requesting capability opening; the capability opening request identifier is represented by a bitmap, for example, a bit is used to identify whether capability opening is requested, such as the bit position is 1, indicating requesting capability opening, and the bit position is 0, indicating not requesting capability opening.

[0157] Table 4

[0158]

[0159]

[0160] In this embodiment, after receiving a capability opening request from a third device, the first device sends a first message to the third device. The first message may also be referred to as indication information. The naming of the first message is not limited in this embodiment. The first message is used to indicate the capability basis file that needs to be provided by the third device. This embodiment mainly deals with the indirect opening method. In the indirect opening method, the first device cannot directly send capability opening information to the third device. It is necessary to process the capability opening information and then send the processed capability opening information to the third device. Therefore, the first device needs to send the above-mentioned first message to the third device to indicate to the third device its (i.e., the first device) indirectly opened capability and require the third device to provide the capability basis file of the corresponding capability. Among them, the capability basis file may also be referred to as a network capability basis file, a capability opening basis file, a network capability opening basis file, etc. The naming of the file is not limited in this embodiment.

[0161] In some optional embodiments, the first information includes a capability-based file identifier, which is used to indicate which capability-based files corresponding to which capabilities the third device needs to provide. In some optional embodiments, the first information also includes at least one capability identifier.

[0162] Exemplarily, the first information includes at least the following two parameters: capability identification and capability based file identification. The implementation of the capability identification is shown in the above embodiment and will not be repeated here. It should be noted that, in this embodiment, the capability disclosure mode corresponding to the capability identification is an indirect disclosure mode.

[0163] In this embodiment, each capability-based file identifier corresponds to a specific capability-based file. The capability-based file indicates the necessary files or information required when the first device indirectly opens a certain type of capability to the third device in a specific implementation form. The first device needs to process the capability-based information (such as calculation processing, packaging processing, etc.) based on the capability-based file, so as to provide the processed capability-based information to the third device.

[0164] In this embodiment, a capability identifier in the first information may correspond to at least one capability-based file identifier.

[0165] Exemplarily, the capability may be represented at least by a bitmap, a string, a numerical parameter, etc. according to the file identifier.

[0166] Bitmap implementation method: Each capability based file identifier can be represented by a bit in the bitmap. For example, the bitmap uses N bits to store field information, similar to the above Table 3, from bit 0 to bit 7, it represents the map file identifier, clock frequency identifier, UE trajectory marking method identifier, heat map marking method identifier, UE activity time range identifier, network performance parameter identifier, network quality classification index basis identifier, network performance analysis time range identifier, etc.; other bits are reserved for capability based file identifiers of other capability types. When a capability based file is required, the bit of the corresponding capability based file identifier is set to 1, and the bit of the unnecessary capability based file identifier is set to 0.

[0167] String implementation: Each capability-based file identifier can be represented by a string, for example, "heat-map" represents the map file identifier for marking the UE activity heat map, "trajectory-marking" represents the UE trajectory marking method identifier, etc. Of course, the embodiments of the present application are not limited to using the above-mentioned strings to represent the corresponding capability-based file identifiers, and any set string can be used to represent the corresponding capability-based file identifier.

[0168] Implementation of numerical parameters: Each capability based on file identification can be represented by a number. For example: 01 represents the map file identification, 02 represents the clock frequency identification, 03 represents the UE trajectory marking method identification, 04 represents the heat map marking method identification, 05 represents the UE activity time range identification, 06 represents the network performance parameter identification, 07 represents the identification of the basis for judging the network quality classification index, and 08 represents the time range identification of the network performance analysis. Of course, the embodiments of the present application are not limited to using the above-mentioned numbers to represent the corresponding capability based on file identification, and any set numbers can be used to represent the corresponding capability based on file identification.

[0169] Exemplarily, as described in the above embodiments, the first device may open at least five types of capabilities, namely, location service capability, wireless network information service capability, monitoring capability, pre-configuration capability, and policy / billing capability. When each type of capability is opened to the third device, it may have an implementation form as shown in Table 5. For example, when the first device opens the location service (LBS) capability to the third device in an indirect opening manner, if it is necessary to provide the third device with the location activity information of the UE in the form of a heat map, the capability-based file provided by the third device to the first device may specifically include: a map file for marking, a heat map marking method file indicating how to color and mark the activity level of the UE in a certain area on the map file, and other capability-based files.

[0170] Table 5

[0171]

[0172] In some optional embodiments of the present application, the first device receives a capability basis file from the third device, including: the first device receives second information from the third device, the second information includes the at least one capability identifier, and the capability basis file corresponding to each capability identifier.

[0173] In this embodiment, the second information sent by the third device to the first device includes the at least one capability identifier and a capability reference file corresponding to each capability identifier.

[0174] Optionally, the capability basis file includes at least one of the following: a map file, a clock frequency of analyzing and processing capability opening information, a time range of analyzing and processing capability opening information, and basis information of analyzing and processing capability opening information.

[0175] In this embodiment, the time range for analyzing and processing capability exposure information is, for example, the UE activity time range, the network performance analysis time range, etc. The basis information for analyzing and processing capability exposure information may include, for example, at least one of the following: UE trajectory marking method, heat map marking method, network performance parameters, basis for judging network quality classification indicators, etc.

[0176] Exemplarily, the above capabilities can be referred to as shown in Table 6 according to the explanation of the document. Among them, the map file is a map file within a certain area range. The file format should support existing mainstream map file formats. For example, the file formats include Geographic Data File (GDF) format, PRM format, etc. The clock frequency is used to provide the clock frequency of a certain capability data (or capability open data), which can be represented in the form of a string (string). For example, it is represented by the string "5ms" to provide capability data (or capability open data) at a time frequency of 5ms; or it can be represented by a numerical parameter (number). For example, 5 is used to provide capability data (or capability open data) at a time frequency of 5ms. The UE trajectory marking method represents the method of marking the trajectory on the map. For example, it includes what form of graphic marking is used and what the principle of making the marking is, etc. The heat map marking method represents the method of marking the UE activity heat map on the map. For example, it includes the different frequencies of the UE appearing at different points on the map, what colors the points are marked respectively, and what the UE activity level represented by the frequency is, etc. The UE activity time range represents a time range used to indicate the activity situation of the UE within which time range. The UE activity time range can be represented by a string. For example, "2020.12.30.00.00.00-2020.12.31.00.00.00" represents the time range from 0:00:00 on December 30, 2020 to 0:00:00 on December 31, 2020. The network performance parameters represent the relevant network performance parameters used to form a network quality analysis report. Exemplarily, the network performance parameters include parameters such as rate, bandwidth, delay, throughput, etc. The network performance parameters can be represented by a string. For example, "delay:30ms" represents that the current real-time network delay is 30ms. The basis for judging the network quality grading index is used to indicate the basis for how to judge the grading of the network quality. For example, the maximum delay, minimum rate, minimum throughput, minimum network bandwidth, etc. corresponding to the three levels of excellent / good / poor network quality judgment. For example, "10ms < delay <= 20ms" represents that one of the parameter requirements for judging the network quality as medium is that the delay is greater than 10ms but less than or equal to 20ms. The time range of network performance analysis represents the time range for providing the network performance analysis report, indicating which time range of the network performance analysis report should be provided, and can be represented by a string. For example, "2020.12.30.00.00.00-2020.12.31.00.00.00" represents the time range from 0:00:00 on December 30, 2020 to 0:00:00 on December 31, 2020.

[0177] Table 6

[0178]

[0179] In this embodiment, after the first device sends the above-mentioned first information to the third device, based on the instructions in the first information, the first device receives the corresponding capability basis file from the third device, and processes the capability exposure information obtained from the fourth device based on the capability basis file (such as calculation processing, encapsulation processing, etc.), and sends the processed capability exposure information to the third device.

[0180] In this embodiment, the first device processes the capability exposure information according to the rules defined in the capability basis file; the information sent by the first device to the third device includes at least: capability identifier, capability basis file identifier, and processed capability exposure information.

[0181] In some optional embodiments of the present application, the method also includes: when the first device cannot obtain the processed capability disclosure information based on the capability basis file, sending third information to the third device, the third information including reason indication information for not providing the processed capability disclosure information and a capability identifier corresponding to the reason indication information.

[0182] Optionally, the processed capability exposure data (i.e., processed capability exposure data) may also be referred to as indirectly exposed capability exposure data (i.e., indirectly exposed capability data), and this naming is not limited in this embodiment. Exemplarily, the processed capability exposure data at least includes: capability exposure data processed by the first device according to the capability basis file. In the case where the first device cannot obtain the processed capability exposure information based on the capability basis file, the third information provided to the third device includes reason indication information for not providing the processed capability exposure information and a capability identifier corresponding to the reason indication information.

[0183] Exemplarily, the type of the processed capability exposure data (or indirectly opened capability exposure data) may be of different types depending on the specific circumstances, and may be negotiated between the first device and the third device. As shown in Table 7, the processed capability exposure data (or indirectly opened capability exposure data) includes at least one of the following: a map showing the movement trajectory of the UE, a map showing a heat map of UE activities, a real-time network performance analysis report, a network performance analysis report for a certain period of time, and the like. The reason indication information for not providing the processed capability exposure information in the third information may be represented in the form of a specific string indicating the reason indication a and the reason indication b shown in Table 7; or the above two pieces of information may be referred to by numerical data (for example, 01 represents "reason indication a", and 02 represents "reason indication b").

[0184] Table 7

[0185]

[0186]

[0187] Based on the above embodiments, the embodiments of the present application also provide a capability opening method. Figure 5 The process diagram of the capability opening method of the embodiment of the present application is as follows: Figure 3 ;like Figure 5 As shown, the method includes:

[0188] Step 201: The second device sends capability exposure rule configuration information to the first device, where the capability exposure rule configuration information includes a capability exposure mode; the capability exposure mode is used to indicate the capability exposure mode of the first device to the third device.

[0189] The capability opening method of this embodiment is applied to a second device. Exemplarily, the second device may be a management system or an operation system, such as a BSS / OSS. Figure 2 The industry gateway shown in can also be called a gateway, a gateway device, etc., and can be expressed as iGW in English. The third device is Figure 2 The MEP shown in may also be referred to as an MEC platform, an MEC server, etc. The embodiment of the present application does not limit the names of the first device, the second device, and the third device, as long as the respective functions of the first device, the second device, and the third device can be realized.

[0190] In this embodiment, the second device sends capability exposure rule configuration information to the first device, the capability exposure rule configuration information may also be referred to as configuration information, and the configuration information includes capability exposure rules. The capability exposure rule configuration information includes an exposure rule for each capability that can be exposed.

[0191] In this embodiment, the capability exposure rule configuration information at least includes a capability exposure mode, wherein, optionally, the capability exposure mode includes: a direct exposure mode and / or an indirect exposure mode. The direct exposure mode indicates a mode in which the first device directly sends the acquired capability exposure information (or data) to the third device; the indirect exposure mode indicates a mode in which the first device processes the acquired capability exposure information (or data) and sends the processed capability exposure information to the third device.

[0192] In some optional embodiments, the capability opening rule configuration information further includes: an identity identifier of a third device and a capability identifier corresponding to the third device.

[0193] In this embodiment, the capability exposure rule configuration information includes the capability exposure rules of each third device connected to the first device, that is, the capability exposure rule configuration information includes the identity of each third device, all capability identifiers corresponding to each third device, and the capability exposure mode corresponding to each capability identifier (direct exposure mode and / or indirect exposure mode).

[0194] In some optional embodiments, the capability exposure rule configuration information also includes: capability exposure conditions. Exemplarily, the capability exposure conditions represent the conditions under which users in the third device can obtain capability exposure information of the corresponding capability. For example, in a third device, for the location service capability identifier, the corresponding capability exposure condition may be available to all users, that is, all users in the third device can obtain the capability exposure information corresponding to the location service capability; and for the monitoring capability identifier, the corresponding capability exposure condition may be the highest-level user, that is, the highest-level user in the third device can obtain the capability exposure information corresponding to the monitoring capability.

[0195] In some optional embodiments of the present application, the method further includes: the second device and the third device complete access authentication of the first device.

[0196] Here, access authentication is completed between the first device, the second device, and the third device. The access authentication process between the first device, the second device, and the third device at least includes: when the first device accesses the second device, it reports its authentication requirements and a list of supported capability information, the second device sends authentication information about the third device to the first device, and the second device authenticates the accessed third device based on the authentication information.

[0197] In some optional embodiments, the capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / charging capability identifier.

[0198] Based on the above embodiments, the embodiments of the present application also provide a capability opening method. Figure 6 The process diagram of the capability opening method of the embodiment of the present application is as follows: Figure 4 ;like Figure 6 As shown, the method includes:

[0199] Step 301: The third device sends a capability opening request to the first device, where the capability opening request is used to request the first device to open a capability;

[0200] Step 302: The third device receives first information from the first device, where the first information is used to indicate a capability reference file that needs to be provided by the third device;

[0201] Step 303: The third device sends a capability reference file to the first device;

[0202] Step 304: the third device receives the processed capability exposure information from the first device; the processed capability exposure information is obtained by the first device processing the capability exposure information based on the capability reference file.

[0203] The capability opening method of this embodiment is applied to a third device. Figure 2 The MEP shown in may also be referred to as a MEC platform, a MEC server, etc. The first device is Figure 2 The industry gateway shown in may also be referred to as a gateway, a gateway device, etc., and may be expressed as iGW in English. The second device may be a management system or an operation system, such as a BSS / OSS. The second device may be a management system or an operation system, such as a BSS / OSS.

[0204] In some optional embodiments, the capability includes at least one of the following: location service capability, wireless network information service capability, monitoring capability, pre-configuration capability, and policy / billing capability.

[0205] In this embodiment, exemplarily, the capability opening request includes a capability opening request identifier and a capability opening information list corresponding to the requested capability. The implementation method of the capability opening information list can refer to the above embodiment, which will not be repeated here. The capability opening information list can be used as a sub-parameter in the capability opening request to request which capabilities the first device opens and indicate the opening method of each capability.

[0206] In this embodiment, the third device receives the first information from the first device. The first information can also be called indication information. In this embodiment, the naming of the first information is not limited. The first information is used to indicate the capability basis file that needs to be provided by the third device. This embodiment mainly deals with the indirect opening method. In the indirect opening method, the first device cannot directly send capability opening information to the third device. It is necessary to process the capability opening information and then send the processed capability opening information to the third device. Therefore, the first device needs to send the above-mentioned first information to the third device to indicate to the third device its (i.e., the first device) indirectly open capability and require the third device to provide the capability basis file of the corresponding capability. Among them, the capability basis file can also be called network capability basis file, capability opening basis file, network capability opening basis file, etc. The naming of this file is not limited in this embodiment.

[0207] In some optional embodiments, the first information includes a capability-based file identifier, which is used to indicate which capability-based files corresponding to which capabilities the third device needs to provide. In some optional embodiments, the first information includes at least one capability identifier.

[0208] Exemplarily, the first information includes at least the following two parameters: capability identification and capability based file identification. The implementation of the capability identification is shown in the above embodiment and will not be repeated here. It should be noted that, in this embodiment, the capability disclosure mode corresponding to the capability identification is an indirect disclosure mode.

[0209] In this embodiment, each capability-based file identifier corresponds to a specific capability-based file. The capability-based file indicates the necessary files or information required when the first device indirectly opens a certain type of capability to the third device in a specific implementation form. The first device needs to process the capability-based information (such as calculation processing, packaging processing, etc.) based on the capability-based file, so as to provide the processed capability-based information to the third device.

[0210] In this embodiment, a capability identifier in the first information may correspond to at least one capability-based file identifier.

[0211] In some optional embodiments of the present application, the third device sends a capability basis file to the first device, including: the third device sends second information to the first device, the second information includes the at least one capability identifier and the capability basis file corresponding to each capability identifier.

[0212] Optionally, the capability basis file includes at least one of the following: a map file, a clock frequency of analyzing and processing capability opening information, a time range of analyzing and processing capability opening information, and basis information of analyzing and processing capability opening information.

[0213] In this embodiment, the time range for analyzing and processing capability exposure information is, for example, the UE activity time range, the network performance analysis time range, etc. The basis information for analyzing and processing capability exposure information may include, for example, at least one of the following: UE trajectory marking method, heat map marking method, network performance parameters, basis for judging network quality classification indicators, etc. The explanation of the above-mentioned various capability basis files can refer to the above-mentioned embodiments, and will not be repeated here.

[0214] In this embodiment, the first device processes the capability exposure information according to the rules defined in the capability basis file; the information sent by the first device to the third device includes at least: capability identifier, capability basis file identifier, and processed capability exposure information.

[0215] In some optional embodiments of the present application, when the third device does not receive the processed capability exposure information from the first device, the method further includes: the third device receives third information from the first device, the third information including reason indication information for not providing the processed capability exposure information and a capability identifier corresponding to the reason indication information.

[0216] Optionally, the processed capability exposure data (i.e., processed capability exposure data) may also be referred to as indirectly exposed capability exposure data (i.e., indirectly exposed capability data), and this naming is not limited in this embodiment. Exemplarily, the processed capability exposure data at least includes: capability exposure data processed by the first device according to the capability basis file. In the case where the first device cannot obtain the processed capability exposure information based on the capability basis file, the third information provided to the third device includes reason indication information for not providing the processed capability exposure information and a capability identifier corresponding to the reason indication information.

[0217] In some optional embodiments, the method further includes: the third device and the second device complete access authentication of the first device.

[0218] In this embodiment, access authentication is completed between the first device, the second device, and the third device. The access authentication process between the first device, the second device, and the third device at least includes: when the first device accesses the second device, it reports its authentication requirements and a list of supported capability information, the second device sends authentication information about the third device to the first device, and the second device authenticates the accessed third device based on the authentication information.

[0219] In some optional embodiments, the method further includes: the third device receiving a capability exposure information list from the first device, where the capability exposure information list is used to indicate capabilities that the first device can provide and a form of the exposed capabilities.

[0220] Optionally, the capability exposure information list includes a capability list and a capability form list; wherein the capability list includes capability identifiers corresponding to capabilities that the first device can provide; and the capability form list includes information on how to obtain capabilities.

[0221] In some optional embodiments of the present application, the capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / billing capability identifier.

[0222] Figure 7 This is a schematic diagram of the network capability exposure architecture of 5G industry cloud network integration in the application embodiment of this application; Figure 7As shown, the first device actually acts as an agent for opening network capabilities between MEP and RAN, between MEP and 5GC, and between MEP and third-party systems (which may include third-party networks and third-party network capabilities). On the basis of the industry gateway opening network capabilities through an agent, the industry gateway can also indirectly open the network capabilities to MEP in the form of a report after processing.

[0223] Using the above-mentioned embodiments of the present application, on the one hand, a new capability opening method based on the industry gateway (i.e., the first device) is proposed, in which the second device directly configures the opening method of each capability of the first device. This method can ensure the feasibility of network capability opening functions under the industry cloud network fusion system architecture, and enrich the industry's application scenarios in network capability opening. On the other hand, an indirect capability opening method based on the industry gateway (i.e., the first device) is proposed. After the capability opening information obtained from the capability source by the industry gateway (i.e., the first device) is processed, it is provided to the third device in an indirect opening manner. This indirect opening method can save bandwidth and MEP computing resources and reduce the latency of network capability opening.

[0224] The capability opening method of the embodiment of the present application is described below with reference to specific examples. In the following examples, the first device is an industry gateway, the second device is a BSS / OSS, and the third device is a MEP.

[0225] Example 1

[0226] Figure 8 The interactive process of the capability opening method of the embodiment of the present application is shown as follows Figure 1 ;like Figure 8 As shown, the method includes:

[0227] Step 401: Complete multi-level access authentication between the industry gateway, BSS / OSS, and MEP.

[0228] Here, the multi-level access process includes steps such as the industry gateway reporting its authentication requirements and supported capability information list when accessing the BSS / OSS, and the BSS / OSS sending the MEP authentication information to the industry gateway.

[0229] Step 402: The industry gateway, capability source, and BSS / OSS perform a capability exposure information acquisition process.

[0230] Here, the capability exposure information acquisition process includes steps such as the industry gateway requesting the capability information exposure list from the BSS / OSS; the capability source opening an API for transmitting the capability exposure information to the industry gateway.

[0231] Step 403: BSS / OSS sends capability exposure rule configuration information to the industry gateway.

[0232] Here, BSS / OSS configures the capabilities that can be opened to each connected MEP and the opening rules of each capability based on the MEP authentication information and the capability information of the industry gateway, and sends the configuration information to the industry gateway connected to the MEP. The opening rules of each network include but are not limited to the capability opening conditions and capability opening methods corresponding to the capability.

[0233] Among them, the capability opening methods include: direct opening method and / or indirect opening method.

[0234] Direct opening method: The industry gateway directly forwards the capability opening information obtained from 5GC / RAN / third party to MEP.

[0235] Indirect opening method: The industry gateway processes the capability opening information obtained from 5GC / RAN / third parties and opens it to MEP in the form of reports (for example: UE location heat map report, network performance analysis report, etc.).

[0236] Step 404: The industry gateway sends a capability exposure information list to the MEP.

[0237] Here, the industry gateway sends an authorized capability exposure information list to each connected MEP based on the BSS / OSS configuration of each MEP capability exposure and the industry gateway's ability to process capability exposure information; wherein the capability exposure information list includes a capability list and a capability form list, wherein the capability list includes capability identifiers corresponding to the capabilities that the industry gateway can provide; and the capability form list includes information on how to obtain the capabilities.

[0238] For example, the industry gateway sends a capability exposure information list to the MEP, informing it that it is authorized to obtain the network capability information of positioning, which is obtained in the form of a real-time heat map of UE location distribution, a UE motion trajectory distribution map, and so on.

[0239] Step 405: The MEP sends a capability opening request to the industry gateway to request the capabilities it needs and is authorized to obtain.

[0240] Step 406: After receiving the capability exposure request from the MEP, the industry gateway sends a capability exposure request response to the MEP and establishes a connection for capability exposure information exchange with the MEP.

[0241] Step 407: The industry gateway and the MEP interact with each other in terms of capability exposure information.

[0242] Example 2

[0243] Fig. 9 The interactive process of the capability opening method of the embodiment of the present application is shown as follows Figure 2; This example can be executed based on the above example 1. Fig. 9 As shown, the method includes:

[0244] Step 504: The MEP sends a capability opening request to the industry gateway to request the capabilities it needs and has the authority to obtain.

[0245] Step 505: The industry gateway receives the capability opening request sent by the MEP and determines the capability opening mode corresponding to the capability requested by the MEP.

[0246] When the requested capability opening mode is a direct opening mode, step 503 is executed: the industry gateway directly sends capability opening information to the MEP.

[0247] When the requested capability opening mode is an indirect opening mode, steps 504 to 506 are executed to start the indirect capability opening process.

[0248] Step 504: The industry gateway sends information to the MEP requesting it to provide a capability-based document (ie, the first information in the aforementioned embodiment).

[0249] Step 505: The MEP provides the industry gateway with a capability reference document based on the business requirements indicated by the information.

[0250] Here, the capability-based documents include but are not limited to:

[0251] 1. When the industry gateway is required to provide UE location information services, the map file required by the industry gateway, for example: a map file that marks the UE location and UE movement trajectory on the map.

[0252] 2. When the industry gateway is required to send the requested network capability information, the clock frequency at which the industry gateway sends the network capability information. For example, the clock frequency at which the industry gateway is required to send the expected route of the UE, the analysis report of the current network performance, etc.

[0253] 3. When requiring the industry gateway to send the requested network capability information, the industry gateway provides the time range of the network capability information. For example, the industry gateway is required to send a comprehensive analysis report of network performance within one week before the current time, a UE connection loss event report, etc.

[0254] 4. Provide industry gateways with analysis basis for processing and analyzing network data. For example, the coloring basis for industry gateways to mark UE activity heat maps, network performance status indicators to determine whether a specific service can be implemented, and algorithms for network capability big data services.

[0255] Step 506: The industry gateway processes the capability exposure information based on the capability basis file, and sends the processed capability exposure information to the MEP.

[0256] Here, the industry gateway provides the processed capability exposure information according to the capability basis file provided by the MEP. If the industry gateway cannot provide any one or more processed capability exposure information according to the capability basis file, the industry gateway sends information to the MEP (the third information in the aforementioned embodiment), which should include the reason indication information for not providing the processed capability exposure information, and may also include the capability identifier corresponding to the reason indication information.

[0257] Based on the above embodiments, the embodiments of the present application also provide a capability opening device. Fig.10 The structure diagram of the capability opening device in the embodiment of the present application is shown in FIG. Figure 1 ,like Fig.10 As shown, the capability opening device 100 includes a first receiving unit 11, which is used to receive capability opening rule configuration information from a second device, wherein the capability opening rule configuration information includes a capability opening mode; the capability opening mode is used to indicate the first device as a third device capability opening mode.

[0258] In some optional embodiments, the capability opening method includes: a direct opening method and / or an indirect opening method.

[0259] In some optional embodiments, the capability opening rule configuration information further includes: an identity identifier of a third device and a capability identifier corresponding to the third device.

[0260] In some optional embodiments, the capability opening rule configuration information further includes: capability opening conditions.

[0261] In some optional embodiments, the apparatus 100 further includes a first sending unit 13, configured to send a capability exposure information list to the third device; the capability exposure information list is used to indicate capabilities that the first device can provide and the form of the exposed capabilities.

[0262] In some optional embodiments, the capability exposure information list includes a capability list and a capability form list; wherein the capability list includes capability identifiers corresponding to capabilities that the first device can provide; and the capability form list includes information on how to obtain capabilities.

[0263] In some optional embodiments, the apparatus 100 further includes a first sending unit 13 and a first processing unit 12;

[0264] The first receiving unit 11 is further configured to receive a capability opening request from the third device, wherein the capability opening request is used to request the first device to open a capability;

[0265] The first sending unit 13 is used to send first information to the third device, where the first information is used to indicate a capability basis file that needs to be provided by the third device;

[0266] The first receiving unit 11 is further configured to receive a capability basis file from the third device;

[0267] The first processing unit 12 is used to process the capability exposure information based on the capability basis file;

[0268] The first sending unit 13 is further configured to send the processed capability opening information to the third device.

[0269] In some optional embodiments, the capability includes at least one of the following: location service capability, wireless network information service capability, monitoring capability, pre-configuration capability, and policy / billing capability.

[0270] In some optional embodiments, the first information includes at least one capability identifier.

[0271] In some optional embodiments, the first receiving unit 11 is used to receive second information from the third device, where the second information includes the at least one capability identifier and a capability reference file corresponding to each capability identifier.

[0272] In some optional embodiments, the device 100 also includes a first sending unit 13, which is used to send third information to the third device when the processed capability opening information cannot be obtained based on the capability basis file, and the third information includes reason indication information for not providing the processed capability opening information and a capability identifier corresponding to the reason indication information.

[0273] In some optional embodiments, the capability basis file includes at least one of the following: a map file, a clock frequency of analyzing and processing capability exposure information, a time range of analyzing and processing capability exposure information, and basis information of analyzing and processing capability exposure information.

[0274] In some optional embodiments, the device 100 further includes a first authentication unit and an acquisition unit; wherein,

[0275] The first authentication unit is used to complete access authentication with the second device and the third device;

[0276] The acquiring unit is configured to acquire capability exposure information from the fourth device.

[0277] In some optional embodiments, the capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / charging capability identifier.

[0278] In the embodiment of the present application, the device 100 is applied to a first device. The first processing unit 12 in the device can be implemented by a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU) or a programmable gate array (FPGA); the first receiving unit 11, the first sending unit 13, the first authentication unit and the acquisition unit in the device can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna in actual application.

[0279] The embodiment of the present application also provides a capability opening device. Fig.11 The structure diagram of the capability opening device in the embodiment of the present application is shown in FIG. Figure 2 ;like Fig.11 As shown, the capability opening apparatus 200 includes a second sending unit 21, which is used to send capability opening rule configuration information to the first device, and the capability opening rule configuration information includes a capability opening mode; the capability opening mode is used to indicate the first device as a third device capability opening mode.

[0280] In some optional embodiments, the capability opening method includes: a direct opening method and / or an indirect opening method.

[0281] In some optional embodiments, the capability opening rule configuration information further includes: an identity identifier of a third device and a capability identifier corresponding to the third device.

[0282] In some optional embodiments, the capability opening rule configuration information further includes: capability opening conditions.

[0283] In some optional embodiments, the apparatus further includes a second authentication unit, configured to complete access authentication of the first device with the third device.

[0284] In some optional embodiments, the capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / charging capability identifier.

[0285] In the embodiment of the present application, the device is applied in the second device. The second sending unit 21 and the second authentication unit in the device can be implemented through a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna in actual application.

[0286] The embodiment of the present application also provides a capability opening device. Fig.12 The structure diagram of the capability opening device in the embodiment of the present application is shown in FIG. Figure 3 ;like Fig.12 As shown, the capability opening device 300 includes: a third sending unit 31 and a third receiving unit 32; wherein,

[0287] The third sending unit 31 is used to send a capability opening request to the first device, where the capability opening request is used to request the first device to open a capability;

[0288] The third receiving unit 32 is used to receive first information from the first device when the opening mode of the requested opening capability is an indirect opening mode, wherein the first information is used to indicate a capability basis file that needs to be provided by the third device;

[0289] The third sending unit 31 is further configured to send a capability basis file to the first device;

[0290] The third receiving unit 32 is further configured to receive processed capability exposure information from the first device; the processed capability exposure information is obtained by the first device processing the capability exposure information based on the capability basis file.

[0291] In some optional embodiments, the capability includes at least one of the following: location service capability, wireless network information service capability, monitoring capability, pre-configuration capability, and policy / billing capability.

[0292] In some optional embodiments, the first information includes at least one capability identifier.

[0293] In some optional embodiments, the third sending unit 31 is used to send second information to the first device, where the second information includes the at least one capability identifier and a capability reference file corresponding to each capability identifier.

[0294] In some optional embodiments, the third receiving unit 32 is further used to receive third information from the first device when the processed capability exposure information from the first device is not received, and the third information includes reason indication information for not providing the processed capability exposure information and a capability identifier corresponding to the reason indication information.

[0295] In some optional embodiments, the capability basis file includes at least one of the following: a map file, a clock frequency of analyzing and processing capability exposure information, a time range of analyzing and processing capability exposure information, and basis information of analyzing and processing capability exposure information.

[0296] In some optional embodiments, the apparatus further includes a third authentication unit, configured to complete access authentication of the first device with the second device.

[0297] In some optional embodiments, the third receiving unit 32 is further configured to receive a capability exposure information list from the first device, where the capability exposure information list is used to indicate capabilities that the first device can provide and forms of the exposed capabilities.

[0298] In some optional embodiments, the capability exposure information list includes a capability list and a capability form list; wherein the capability list includes capability identifiers corresponding to capabilities that the first device can provide; and the capability form list includes information on how to obtain capabilities.

[0299] In some optional embodiments, the capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / charging capability identifier.

[0300] In the embodiment of the present application, the apparatus 300 is applied to a third device. The third receiving unit 32, the third sending unit 31 and the third authentication unit in the apparatus 300 can be implemented in practical applications through a communication module (including: a basic communication kit, an operating system, a communication module, a standardized interface and protocol, etc.) and a transceiver antenna.

[0301] It should be noted that: the capability opening device provided in the above embodiment only uses the division of the above program modules as an example when opening the capability. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the capability opening device provided in the above embodiment and the capability opening method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0302] An embodiment of the present application also provides a communication device, which is the first device, the second device or the third device in the aforementioned embodiment. Fig.13 Schematic diagram of the hardware structure of the communication device of the embodiment of the present application. Fig.13As shown, the communication device includes a memory 42, a processor 41, and a computer program stored in the memory 42 and executable on the processor 41. When the processor 41 executes the program, the steps of the capability opening method applied in the first device according to the embodiment of the present application are implemented; or, when the processor 41 executes the program, the steps of the capability opening method applied in the second device according to the embodiment of the present application are implemented; or, when the processor 41 executes the program, the steps of the capability opening method applied in the third device according to the embodiment of the present application are implemented.

[0303] Optionally, the communication device may further include one or more network interfaces 43. It is understood that the various components in the communication device are coupled together via a bus system 44. It is understood that the bus system 44 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 44 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.13 Various buses are labeled as bus system 44 .

[0304] It can be understood that the memory 42 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAM bus random access memory (DRRAM, Direct Rambus Random Access Memory).The memory 42 described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0305] The method disclosed in the above embodiment of the present application can be applied to the processor 41, or implemented by the processor 41. The processor 41 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 41 or the instruction in the form of software. The above processor 41 can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 41 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 42, and the processor 41 reads the information in the memory 42 and completes the steps of the above method in combination with its hardware.

[0306] In an exemplary embodiment, the communication device may be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), FPGA, general purpose processor, controller, MCU, microprocessor, or other electronic components to execute the aforementioned method.

[0307] In an exemplary embodiment, the present application also provides a computer-readable storage medium, such as a memory 42 including a computer program, and the computer program can be executed by a processor 41 of a communication device to complete the steps of the aforementioned method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM; or it can be various devices including one or any combination of the above memories.

[0308] The computer-readable storage medium provided by the embodiment of the present application stores a computer program thereon, and when the program is executed by a processor, the steps of the capability opening method applied in the first device by the embodiment of the present application are implemented; or, when the program is executed by a processor, the steps of the capability opening method applied in the second device by the embodiment of the present application are implemented; or, when the program is executed by a processor, the steps of the capability opening method applied in the third device by the embodiment of the present application are implemented.

[0309] The methods disclosed in several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0310] The features disclosed in several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0311] The features disclosed in several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.

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

[0313] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0314] In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be a separate unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0315] A person of ordinary skill in the art can understand that: all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium, which, when executed, executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, disks or optical disks.

[0316] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.

[0317] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A capability opening method, characterized in that: The method comprises: The first device receives capability exposure rule configuration information from the second device, where the capability exposure rule configuration information includes a capability exposure mode; the capability exposure mode includes: a direct exposure mode and an indirect exposure mode, or the capability exposure mode includes an indirect exposure mode; The capability opening mode is used to indicate the mode in which the first device opens the capability of the third device; The first device receives a capability opening request from the third device, where the capability opening request is used to request the first device to open a capability; the first device sends first information to the third device, where the first information is used to indicate a capability basis file that needs to be provided by the third device; the first device receives the capability basis file from the third device; the first device processes the capability opening information based on the capability basis file, and sends the processed capability opening information to the third device; wherein the capability basis file represents: necessary files or information required when the first device indirectly opens a certain capability to the third device in a specific implementation form.

2. The method according to claim 1, characterized in that The capability opening rule configuration information also includes: an identity identifier of a third device and a capability identifier corresponding to the third device.

3. The method according to claim 2, characterized in that The capability opening rule configuration information also includes: capability opening conditions.

4. The method according to claim 1, characterized in that: The method further comprises: The first device sends a capability exposure information list to the third device; the capability exposure information list is used to indicate capabilities that the first device can provide and the form of the exposed capabilities.

5. The method according to claim 4, characterized in that The capability exposure information list includes a capability list and a capability form list; The capability list includes capability identifiers corresponding to capabilities that the first device can provide; and the capability form list includes information on how to obtain the capabilities.

6. The method according to claim 1, characterized in that The capability includes at least one of the following: location service capability, wireless network information service capability, monitoring capability, pre-configuration capability, and policy / billing capability.

7. The method according to claim 1, characterized in that The first information includes at least one capability identifier.

8. The method according to claim 7, characterized in that The first device receives the capability reference file from the third device, including: The first device receives second information from the third device, where the second information includes the at least one capability identifier and a capability reference file corresponding to each capability identifier.

9. The method according to claim 1, characterized in that: The method further comprises: When the first device cannot obtain the processed capability exposure information based on the capability reference file, it sends third information to the third device, wherein the third information includes reason indication information for not providing the processed capability exposure information and a capability identifier corresponding to the reason indication information.

10. The method according to claim 1, characterized in that The capability document includes at least one of the following: Map file, clock frequency of the analysis and processing capability open information, time range of the analysis and processing capability open information, and basis information of the analysis and processing capability open information.

11. The method according to any one of claims 1 to 5, characterized in that: Before the first device receives the capability opening rule configuration information from the second device, the method further includes: The first device completes access authentication with the second device and the third device; The first device obtains capability exposure information from the fourth device.

12. The method according to claim 2, 5, 7, 8 or 9, characterized in that The capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / charging capability identifier.

13. A capability opening method, characterized in that: The method comprises: The second device sends capability exposure rule configuration information to the first device, where the capability exposure rule configuration information includes a capability exposure mode; the capability exposure mode includes: a direct exposure mode and an indirect exposure mode, or the capability exposure mode includes an indirect exposure mode; The capability opening mode is used to indicate the mode in which the first device opens the capability of the third device; wherein the indirect opening mode includes: The first device receives a capability opening request from the third device, where the capability opening request is used to request the first device to open a capability; the first device sends first information to the third device, where the first information is used to indicate a capability basis file that needs to be provided by the third device; the first device receives the capability basis file from the third device; the first device processes the capability opening information based on the capability basis file, and sends the processed capability opening information to the third device; wherein the capability basis file represents: necessary files or information required when the first device indirectly opens a certain capability to the third device in a specific implementation form.

14. The method according to claim 13, characterized in that The capability opening rule configuration information also includes: an identity identifier of a third device and a capability identifier corresponding to the third device.

15. The method according to claim 14, characterized in that The capability opening rule configuration information also includes: capability opening conditions.

16. The method according to any one of claims 13 to 15, characterized in that The method further comprises: The second device and the third device complete access authentication of the first device.

17. The method according to claim 14, characterized in that The capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / charging capability identifier.

18. A capability opening method, characterized in that: The method comprises: The third device sends a capability opening request to the first device, where the capability opening request is used to request the first device to open a capability; The third device receives first information from the first device, where the first information is used to indicate a capability basis file that needs to be provided by the third device; The third device sends a capability basis file to the first device; The third device receives the processed capability exposure information from the first device; the processed capability exposure information is obtained by the first device processing the capability exposure information based on the capability basis file; wherein the capability basis file represents: the necessary files or information required when the first device indirectly opens a certain capability to the third device in a specific implementation form.

19. The method according to claim 18, characterized in that The capability includes at least one of the following: location service capability, wireless network information service capability, monitoring capability, pre-configuration capability, and policy / billing capability.

20. The method according to claim 18, characterized in that The first information includes at least one capability identifier.

21. The method according to claim 20, characterized in that The third device sends a capability reference file to the first device, including: The third device sends second information to the first device, where the second information includes the at least one capability identifier and a capability reference file corresponding to each capability identifier.

22. The method according to claim 18, characterized in that In a case where the third device does not receive the processed capability opening information from the first device, the method further includes: The third device receives third information from the first device, where the third information includes reason indication information for not providing the processed capability exposure information and a capability identifier corresponding to the reason indication information.

23. The method according to claim 18, characterized in that The capability document includes at least one of the following: Map file, clock frequency of the analysis and processing capability open information, time range of the analysis and processing capability open information, and basis information of the analysis and processing capability open information.

24. The method according to any one of claims 18 to 23, characterized in that The method further comprises: The third device and the second device complete access authentication of the first device.

25. The method according to claim 24, characterized in that The method further comprises: The third device receives a capability exposure information list from the first device, where the capability exposure information list is used to indicate capabilities that the first device can provide and a form of the exposed capabilities.

26. The method according to claim 25, characterized in that The capability exposure information list includes a capability list and a capability form list; The capability list includes capability identifiers corresponding to capabilities that the first device can provide; and the capability form list includes information on how to obtain the capabilities.

27. The method according to any one of claims 20 to 22, characterized in that The capability identifier includes at least one of the following: a location service capability identifier, a wireless network information service capability identifier, a monitoring capability identifier, a pre-configuration capability identifier, and a policy / charging capability identifier.

28. A capability opening device, characterized in that: The device comprises a first receiving unit and a fourth sending unit, wherein: The first receiving unit is used to receive capability exposure rule configuration information from the second device, the capability exposure rule configuration information includes a capability exposure mode; the capability exposure mode includes: a direct exposure mode and an indirect exposure mode, or the capability exposure mode includes an indirect exposure mode; the capability exposure mode is used to indicate the first device as a capability exposure mode of the third device; The first receiving unit is further configured to receive a capability opening request from the third device, where the capability opening request is used to request the first device to open a capability; A fourth sending unit, configured to send first information to the third device, where the first information is used to indicate a capability basis file that needs to be provided by the third device; The first receiving unit is further configured to receive a capability basis file from the third device; The fourth sending unit is further used to process the capability exposure information based on the capability basis file, and send the processed capability exposure information to the third device; wherein the capability basis file represents: the necessary files or information required when the first device indirectly opens a certain capability to the third device in a specific implementation form.

29. A capability opening device, characterized in that: The apparatus comprises a second sending unit, configured to send capability opening rule configuration information to the first device, wherein the capability opening rule configuration information comprises a capability opening mode; The capability opening mode includes: a direct opening mode and an indirect opening mode, or the capability opening mode includes an indirect opening mode; the capability opening mode is used to indicate that the first device is a mode of opening the capability of the third device; wherein the indirect opening mode includes: The first device receives a capability opening request from the third device, where the capability opening request is used to request the first device to open a capability; the first device sends first information to the third device, where the first information is used to indicate a capability basis file that needs to be provided by the third device; the first device receives the capability basis file from the third device; the first device processes the capability opening information based on the capability basis file, and sends the processed capability opening information to the third device; wherein the capability basis file represents: necessary files or information required when the first device indirectly opens a certain capability to the third device in a specific implementation form.

30. A capability opening device, characterized in that: The device comprises: a third sending unit and a third receiving unit; wherein, The third sending unit is used to send a capability opening request to the first device, where the capability opening request is used to request the first device to open a capability; The third receiving unit is configured to receive first information from the first device when the opening mode of the capability requested to be opened is an indirect opening mode, wherein the first information is used to indicate a capability basis file that needs to be provided by the third device; The third sending unit is further configured to send a capability basis file to the first device; The third receiving unit is further used to receive processed capability exposure information from the first device; the processed capability exposure information is obtained by the first device processing the capability exposure information based on the capability basis file; wherein the capability basis file represents: the necessary files or information required when the first device indirectly opens a certain capability to the third device in a specific implementation form.

31. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented; or, When the program is executed by a processor, the steps of the method according to any one of claims 13 to 17 are implemented; or When the program is executed by a processor, the steps of the method according to any one of claims 18 to 27 are implemented.

32. A communication device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the method according to any one of claims 1 to 12 are implemented; or, When the processor executes the program, the steps of the method according to any one of claims 13 to 17 are implemented; or, When the processor executes the program, the steps of the method according to any one of claims 18 to 27 are implemented.

Images