Edge capability call caching method, device, management platform and application client

Abstract

The present invention provides an edge capability call caching method, apparatus, management platform, and application client. The method comprises: obtaining a first cache record containing cache information of a target capability called by a target application; and if the capability status of the cached information changes within the valid time of the capability call, sending cache capability update information to the target application. Using this method, the management platform can send the cache capability update information to the target application, enabling the target application to timely update a locally stored second cache record to obtain optimal service capabilities, thereby resolving the issue with existing technologies that cannot guarantee optimal service capabilities.

Description

Technical Field

[0001] The present invention relates to the field of communication network technology, and in particular to an edge capability calling cache method, device, management platform and application client. Background Art

[0002] The edge capability call caching mechanism includes two levels of caching: central caching and local caching. When an application calls a capability, if the platform doesn't already have that capability deployed, it sends a request to the edge capability management platform. The capability management platform selects the optimal capability for the application and stores the capability call record—that is, the capability and location called by the application. Furthermore, after receiving the capability call information, the local application stores the record and can subsequently initiate the same capability call request based on the local cache.

[0003] Based on the aforementioned edge capability caching mechanism, the current edge capability management platform records application capability calls for operational purposes only. It cannot support subsequent capability calls, nor can it coordinate updates of the application capability call cache with capability deployment information. Furthermore, directly accessing the cache for capability call records stored by local applications may result in suboptimal capabilities and inability to detect new capabilities deployed on the network. Summary of the Invention

[0004] The purpose of the technical solution of the present invention is to provide an edge capability call caching method, device, management platform and application client, which are used to solve the problem that the capability call records stored by the edge capability management platform and local applications based on the existing technology cannot guarantee the acquisition of optimal service capabilities.

[0005] One embodiment of the present invention provides an edge capability call caching method, which is applied to a management platform and includes:

[0006] Obtaining a first cache record including cache information of a target application calling a target capability;

[0007] If the capability status of the cache information changes within the valid time of the capability call of the cache information, cache capability update information is sent to the target application.

[0008] Optionally, the edge capability calls a caching method, wherein the method further includes:

[0009] When the cache information is stored in the first cache record, a corresponding capability identifier and the capability call validity period are recorded in correspondence with the cache information; wherein the capability identifier is used to record the capability status of the cache information.

[0010] Optionally, the edge capability calls a caching method, wherein the method further includes:

[0011] Obtain capability deployment update information sent by the capability deployment information module;

[0012] The capability identifier in the first cache record is updated according to the capability deployment update information.

[0013] Optionally, the edge capability calling cache method, wherein obtaining capability deployment update information sent by the capability deployment information module includes:

[0014] Acquire capability deployment update information sent by the capability deployment information module when capability deployment is updated; or

[0015] The capability deployment information acquisition module sends capability deployment update information according to a preset period.

[0016] Optionally, the edge capability calls a caching method, wherein the method further includes:

[0017] When the capability identifier indicates that the cache information is not the optimal capability for the target application to call the target capability, the capability call validity period corresponding to the cache information is set to 0, and / or the first cache record corresponding to the cache information is deleted.

[0018] Optionally, the edge capability calls a caching method, wherein the method further includes:

[0019] When the capability identifier is updated, it is determined whether the capability identifier indicates that the cache information is the optimal capability for the target application to call the target capability.

[0020] Optionally, in the edge capability calling cache method, the capability identifier is used to indicate that the cache information is the optimal capability when the target application calls the target capability.

[0021] Optionally, the edge capability calls a cache method, wherein sending cache capability update information to the target application includes:

[0022] The cache capability update information is sent to the target application via a Domain Name System (DNS) message.

[0023] Optionally, the edge capability calls a caching method, wherein the Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the caching capability update information.

[0024] One embodiment of the present invention further provides an edge capability call caching method, which is used for a target application and includes:

[0025] Obtaining cache capability update information sent by the management platform; wherein the cache capability update information is used to indicate that the cache information of the target capability called by the target application has changed;

[0026] A second cache record is updated according to the cache capability update information, where the second cache record pre-stores cache information of the target application calling the target capability.

[0027] Optionally, the edge capability calls a cache method, wherein obtaining cache capability update information sent by the management platform includes:

[0028] Acquire cache capability update information sent by the management platform to the target application via a DNS message.

[0029] Optionally, the edge capability calls a caching method, wherein the Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the caching capability update information.

[0030] Optionally, the edge capability calls a caching method, wherein the method further includes:

[0031] In the updated second cache record, when the cache information of the target capability called by the target application is not the optimal capability, the cache information is deleted.

[0032] One embodiment of the present invention further provides a management platform, comprising a processor and a transceiver, wherein:

[0033] The processor is configured to obtain a first cache record including cache information of a target application calling a target capability;

[0034] The transceiver is configured to send cache capability update information to the target application if the capability status of the cache information changes within the capability call validity period of the cache information.

[0035] One embodiment of the present invention further provides an application client for running a target application, comprising a transceiver and a processor, wherein:

[0036] The transceiver is used to obtain cache capability update information sent by the management platform; wherein the cache capability update information is used to indicate that the cache information of the target capability called by the target application has changed;

[0037] The processor is configured to update the second cache record according to the cache capability update information, where the second cache record pre-stores cache information of the target application calling the target capability.

[0038] One embodiment of the present invention further provides an edge capability call cache device, which is applied to a management platform and includes:

[0039] A first acquisition module, configured to acquire a first cache record including cache information of a target application calling a target capability;

[0040] The sending module is configured to send cache capability update information to the target application if the capability status of the cache information changes within the valid time of the capability call of the cache information.

[0041] One embodiment of the present invention further provides an edge capability call cache device, which is applied to an application client and includes:

[0042] A second acquisition module is configured to acquire cache capability update information sent by the management platform; wherein the cache capability update information is used to indicate that the cache information of the target capability called by the target application has changed;

[0043] The updating module is configured to update the second cache record according to the cache capability update information, wherein the second cache record pre-stores cache information of the target application calling the target capability.

[0044] One embodiment of the present invention further provides a network device, which includes: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the edge capability call caching method as described in any one of the above items.

[0045] One embodiment of the present invention further provides a readable storage medium, wherein the readable storage medium stores a program, and when the program is executed by a processor, the steps in the edge capability call caching method as described in any one of the above items are implemented.

[0046] At least one of the above technical solutions of the present invention has the following beneficial effects:

[0047] In the edge capability call caching method described in the embodiment of the present invention, the management platform records the first cache record when the application calls the edge capability, and records the corresponding capability call validity time. During the capability call validity time, when the capability level of the cache information of the target capability called by the target application changes, the management platform can send cache capability update information to the target application, so that the target application updates the second cache record stored locally in a timely manner to obtain the optimal service capability, thereby solving the problem that the existing technology cannot guarantee the acquisition of the optimal service capability. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 A schematic diagram of the system structure using the edge capability calling cache method according to an embodiment of the present invention;

[0049] Figure 2 A schematic diagram of a flow chart of an edge capability calling cache method according to one embodiment of the present invention;

[0050] Figure 3 This is a flow chart of a method for invoking a cache for edge capabilities according to another embodiment of the present invention;

[0051] Figure 4 This is a schematic diagram of the structure of the management platform according to an embodiment of the present invention;

[0052] Figure 5 This is a schematic diagram of the structure of the application client according to an embodiment of the present invention;

[0053] Figure 6 A schematic diagram of the structure of an edge capability call cache device according to one embodiment of the present invention;

[0054] Figure 7 This is a structural diagram of an edge capability invocation cache device according to another embodiment of the present invention. DETAILED DESCRIPTION

[0055] In order to make the technical problems, technical solutions and advantages to be solved by the present invention clearer, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0056] In order to solve the problem that the capability call records stored by the edge capability management platform and local applications based on the existing technology cannot guarantee the acquisition of the optimal service capability, an embodiment of the present invention provides an edge capability call caching method. When the capability level of the cached information of the target capability called by the target application changes within the effective time of the capability call, the management platform sends cache capability update information to the target application, so that the target application can obtain the optimal service capability in a timely manner.

[0057] Figure 1 The present invention is a schematic diagram of the system structure of the edge capability call caching method according to an embodiment of the present invention. The system includes an application client (also referred to as an application) 10, a capability platform 20, and a management platform 30, wherein the capability platform 20 is used to provide corresponding edge capabilities. The application client 10 stores the capability call record locally, and obtains the required capability through the stored cache information within the validity period of the cache information stored in the capability call record. If the capability to be called does not have cache information stored in the capability call record, that is, when a new capability is called, the capability to be called is obtained by sending a capability call request to the management platform 30 and stored in the local capability call record.

[0058] Typically, the capability call records stored in the application client 10 may not be optimal, and the application client 10 may not be able to perceive new capabilities deployed on the network, thus resulting in the application client 10 being unable to guarantee optimal service capabilities.

[0059] To solve the above technical problems, one embodiment of the present invention provides an edge capability call caching method, which is applied to a management platform, such as Figure 2 As shown, the method includes:

[0060] S210, obtaining a first cache record including cache information of a target application calling a target capability;

[0061] S220: If the capability status of the cache information changes within the valid time of the capability call of the cache information, cache capability update information is sent to the target application.

[0062] In the edge capability call caching method described in this embodiment, the management platform records the first cache record when the application calls the edge capability (that is, the capability call record is stored in the management platform), and records the corresponding capability call validity time. During the capability call validity time, when the capability level of the cache information of the target capability called by the target application changes, the management platform can send cache capability update information to the target application, so that the target application can update the second cache record stored locally (that is, the capability call record stored in the target application) in a timely manner to obtain the optimal service capability.

[0063] Table 1 below is a schematic implementation form of the first cache record stored in the management platform in an embodiment of the present invention:

[0064]

[0065] Specifically, the first cache record stores cache information of the application calling the edge capability. For example, in the example in Table 1 above, application 2 sends a capability call request to the management platform. After calling capability 2 deployed on ECP2, the management platform stores the cache information in the first cache record to record the information of application 2 calling capability 2 deployed on ECP2.

[0066] Optionally, in an embodiment of the present invention, the cache information includes a call capability location and a call duration, wherein the first cache record is further used to record an application identifier, call capability information, and call duration corresponding to the stored cache information.

[0067] Based on the above, the capability call records stored in the management platform may include multiple first cache records, each of which corresponds to an application identifier, calling capability information, calling duration, and corresponding cache information when an application calls an edge capability.

[0068] In this embodiment of the present invention, the application identifier in the first cache record includes, but is not limited to, only the application ID, as long as it can distinguish between applications. The calling capability information is used to record the edge capability called by the application. The calling capability location is used to record the location of the edge capability called by the application. Optionally, the location can be distinguished by the address of the capability platform. The calling duration is used to record the duration of the edge capability called by the application.

[0069] In the edge capability call caching method described in this embodiment of the present invention, compared to the prior art, the stored first cache record also includes a capability call validity period, which is used to set the validity period for calling the cache information stored in the first cache record. Optionally, this capability call validity period can be determined by the target application or set by the management platform based on application requirements.

[0070] In addition, the stored first cache record also includes a capability identifier, which is used to record the capability status of the cache information stored in the first cache record.

[0071] Optionally, the capability identifier is used to record that the cache information is the optimal capability for the target application to call the target capability.

[0072] The edge capability call caching method according to an embodiment of the present invention further includes:

[0073] When the cache information is stored in the first cache record, a corresponding capability identifier and the capability call validity period are recorded in correspondence with the cache information; wherein the capability identifier is used to record the capability status of the cache information.

[0074] Optionally, the capability identifier indicates that the corresponding cache information is the optimal capability with a preset indication value. When the cache information is the optimal capability, the capability identifier indicates the preset indication value. When the cache information is not the optimal capability, the capability identifier does not indicate.

[0075] In another embodiment, the capability identifier optionally uses a first preset indicator value to indicate that the corresponding cache information is at optimal capability, and a second preset indicator value to indicate that the corresponding cache information is not at optimal capability. Specifically, when the cache information is at optimal capability, the capability identifier uses the first preset value; when the cache information is not at optimal capability, the capability identifier uses the second preset value.

[0076] In another embodiment, the capability status may be divided into different levels according to the order of merit, and the capability identifier may also indicate different levels of capability status through different preset indication values.

[0077] Optionally, the edge capability invocation caching method according to the embodiment of the present invention further includes:

[0078] Obtain capability deployment update information sent by the capability deployment information module;

[0079] The capability identifier in the first cache record is updated according to the capability deployment update information.

[0080] Optionally, obtaining capability deployment update information sent by the capability deployment information module includes:

[0081] Acquire capability deployment update information sent by the capability deployment information module when capability deployment is updated; or

[0082] The capability deployment information acquisition module sends capability deployment update information according to a preset period.

[0083] In the above embodiment, the management platform stores capability deployment information, as shown in Table 3 below. The stored capability deployment information may be in the form of:

[0084] Capability platform logo Capability deployment information ECP1.AP1GW1 Abilities 1, 2, 3, and 4 ECP2.AP1GW2 Abilities 2, 4, 5, and 6

[0085] Optionally, when the capability deployment of each capability platform is updated, the management platform updates the capability identifier in each first cache record recorded in the capability call record according to the updated capability deployment information, so that the application call capability cache can be updated in coordination with the capability deployment information and the application capability location, so as to provide the optimal capability call for the application.

[0086] Specifically, in an embodiment of the present invention, when the management platform stores the first cache record through the capability call cache module, an interface is added between the capability deployment information module of the management platform and the capability call cache module for interaction, so that the capability deployment information module can send capability deployment update information to the capability call cache module to update the capability identification of the first cache record.

[0087] Optionally, the capability deployment information module sends capability deployment update information with capability deployment update as a trigger condition, that is, after obtaining the updated capability deployment, the capability deployment update information is sent to the capability call cache module; or, the capability deployment information module sends capability deployment update information with periodicity as a trigger condition, that is, every preset period, the capability deployment information module sends capability deployment update information to the capability call cache module.

[0088] The management platform or the capability call cache module identifies the cache information of the corresponding capability call after the update deployment, that is, updates the capability identifier, to record whether the corresponding cache information is the optimal capability called by the corresponding application.

[0089] The edge capability call caching method described in an embodiment of the present invention may optionally further include: when the capability identifier indicates that the cache information is not the optimal capability for the target application to call the target capability, setting the capability call validity period corresponding to the cache information to 0, and / or deleting the first cache record corresponding to the cache information.

[0090] Optionally, the method further includes: when updating the capability identifier, determining whether the capability identifier indicates that the cache information is an optimal capability for the target application to call the target capability.

[0091] Specifically, during the capability call validity period of the cache information, if the capability status of the cache information changes, and / or, after the capability identifier in the first cache record is updated according to the capability deployment update information, when the capability identifier indicates that the cache information is not the optimal capability for the target application to call the target capability, the capability call validity period corresponding to the cache information is set to 0, and / or the first cache record is deleted. In one embodiment, after the capability status of the cache information changes, and / or, after the capability identifier in the first cache record is updated according to the capability deployment update information, when the capability identifier indicates that the cache information is not the optimal capability for the target application to call the target capability, the capability call validity period is set to 0 to invalidate the first cache record. In this way, when the target application calls the target capability again, the corresponding cache information is determined to be invalid information based on the recorded capability call validity period of 0, and the required capability needs to be rescheduled for the target application.

[0092] In another embodiment, after the capability status of the cached information changes, and / or the capability identifier in the first cache record is updated according to the capability deployment update information, when the capability identifier indicates that the cached information is not the optimal capability for the target application to call the target capability, the first cache record is deleted so that the capability call record stored by the management platform does not contain the first cache record. In this way, when the target application calls the target capability again, the required scheduled capability needs to be rescheduled for the target application.

[0093] In a specific embodiment of the present invention, when the capability status of the stored cache information changes, the management platform sends cache capability update information to the target application.

[0094] Optionally, the cache capability update information includes updated capability deployment information, at least one of a currently callable capability position and a currently optimal capability position.

[0095] In one embodiment, optionally, sending cache capability update information to the target application includes:

[0096] The cache capability update information is sent to the target application via a Domain Name System (DNS) message.

[0097] Optionally, the Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the cache capability update information.

[0098] In this embodiment, the Opcode field or the Z field in the message header of the DNS message is used to identify the type of the DNS message, so as to indicate to the target application that the DNS message is used to send cache capability update information.

[0099] After receiving the cache capability update information sent by the management platform, the target application updates the second cache record stored locally according to the cache capability update information.

[0100] Optionally, in the updated second cache record, when the cache information of the target capability called by the target application is not the optimal capability, the cache information can be deleted. In this way, the next time the target capability is called, it is necessary to re-initiate the capability call request to the management platform to ensure that the target application obtains the optimal service capability in a timely manner.

[0101] One embodiment of the present invention further provides an edge capability call caching method, which is applied to target applications, such as Figure 3 As shown, the method includes:

[0102] S310, obtaining cache capability update information sent by the management platform; wherein the cache capability update information is used to indicate that the cache information of the target capability called by the target application has changed;

[0103] S320: Update the second cache record according to the cache capability update information, where the second cache record pre-stores cache information of the target application calling the target capability.

[0104] In the edge capability call caching method described in the embodiment of the present invention, the target application locally caches capability call records for recording cache information of the target application scheduling edge capabilities.

[0105] Optionally, the capability call record cached locally includes a plurality of second cache records, and each second cache record records corresponding cache information of an edge capability requested to be called by the target application.

[0106] Optionally, the cache information stored in the second cache record includes calling capability information, calling capability location, calling duration, etc. of the called edge capability.

[0107] Optionally, the cache of the second cache record also has a valid time, and the valid time can be set for the target application or can be set by the management platform.

[0108] Among them, within the effective time, if the management platform updates the capability status of the cache information, for example, the cache information cached in the management platform is no longer the optimal capability, and the target application does not update the cache information locally, it will result in the inability to access the optimal capability. Therefore, it is necessary to update the locally stored cache information within the effective time set by the application platform.

[0109] The edge capability calling cache method described in the embodiment of the present invention is that when the capability status of the cache information of the target capability called by the target application stored in the management platform changes, the management platform sends cache capability update information to the target application, so that the target application obtains the cache capability update information and obtains the optimal service capability in a timely manner.

[0110] The edge capability calling cache method according to the embodiment of the present invention may optionally, in step S310, obtain cache capability update information sent by the management platform, including:

[0111] Acquire cache capability update information sent by the management platform to the target application via a DNS message.

[0112] Optionally, the edge capability calls a caching method, wherein the Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the caching capability update information.

[0113] Optionally, the edge capability calls a caching method, wherein the method further includes:

[0114] In the updated second cache record, when the cache information of the target capability called by the target application is not the optimal capability, the cache information is deleted.

[0115] One embodiment of the present invention provides a management platform, such as Figure 4 As shown, the management platform 400 includes a processor 410 and a transceiver 420, wherein:

[0116] The processor 410 is configured to obtain a first cache record including cache information of a target application calling a target capability;

[0117] The transceiver 420 is configured to send cache capability update information to the target application if the capability status of the cache information changes within the valid time of the cache information capability call.

[0118] Optionally, in the management platform, the processor 410 is further configured to:

[0119] When the cache information is stored in the first cache record, a corresponding capability identifier and the capability call validity period are recorded in correspondence with the cache information; wherein the capability identifier is used to record the capability status of the cache information.

[0120] Optionally, in the management platform, the processor 410 is further configured to:

[0121] Obtain capability deployment update information sent by the capability deployment information module;

[0122] The capability identifier in the first cache record is updated according to the capability deployment update information.

[0123] Optionally, in the management platform, the processor 410 obtains the capability deployment update information sent by the capability deployment information module, including:

[0124] Acquire capability deployment update information sent by the capability deployment information module when capability deployment is updated; or

[0125] The capability deployment information acquisition module sends capability deployment update information according to a preset period.

[0126] Optionally, in the management platform, the processor 410 is further configured to:

[0127] When the capability identifier indicates that the cache information is not the optimal capability for the target application to call the target capability, the capability call validity period corresponding to the cache information is set to 0, and / or the first cache record corresponding to the cache information is deleted.

[0128] Optionally, in the management platform, the processor 410 is further configured to: when updating the capability identifier, determine whether the capability identifier indicates that the cache information is the optimal capability for the target application to call the target capability.

[0129] Optionally, in the management platform, the capability identifier is used to indicate that the cache information is the optimal capability when the target application calls the target capability.

[0130] Optionally, in the management platform, the transceiver 420 sending the cache capability update information to the target application includes:

[0131] The cache capability update information is sent to the target application via a DNS message.

[0132] Optionally, in the management platform, the Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the cache capability update information.

[0133] One embodiment of the present invention further provides an application client for executing a target application, such as Figure 5 As shown, the application client 500 includes a transceiver 510 and a processor 520, wherein:

[0134] The transceiver 510 is used to obtain cache capability update information sent by the management platform; wherein the cache capability update information is used to indicate that the cache information of the target capability called by the target application has changed;

[0135] The processor 520 is configured to update a second cache record of the target application according to the cache capability update information, where the second cache record pre-stores cache information of the target application calling the target capability.

[0136] Optionally, in the application client, the transceiver 510 obtains the cache capability update information sent by the management platform, including:

[0137] Acquire cache capability update information sent by the management platform to the target application via a DNS message.

[0138] Optionally, in the application client, the Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the cache capability update information.

[0139] Optionally, in the application client, the processor 520 is further configured to:

[0140] In the updated second cache record, when the cache information of the target capability called by the target application is not the optimal capability, the cache information is deleted.

[0141] One embodiment of the present invention further provides an edge capability call cache device, which is applied to a management platform, such as Figure 6 As shown, the device includes:

[0142] A first acquisition module 610 is configured to acquire a first cache record including cache information of a target application calling a target capability;

[0143] The sending module 620 is configured to send cache capability update information to the target application if the capability status of the cache information changes within the valid time of the capability call of the cache information.

[0144] Optionally, the edge capability calls a cache device, wherein the device further includes:

[0145] The storage module 630 is used to store the cache information in the first cache record, and record the corresponding capability identifier and the capability call validity period corresponding to the cache information; wherein the capability identifier is used to record the capability status of the cache information.

[0146] Optionally, the edge capability calls the cache device, wherein the first acquisition module 610 is further configured to:

[0147] Obtain capability deployment update information sent by the capability deployment information module;

[0148] The capability identifier in the first cache record is updated according to the capability deployment update information.

[0149] Optionally, the edge capability calling cache device, wherein the first acquisition module 610 acquires the capability deployment update information sent by the capability deployment information module, includes:

[0150] Acquire capability deployment update information sent by the capability deployment information module when capability deployment is updated; or

[0151] The capability deployment information acquisition module sends capability deployment update information according to a preset period.

[0152] Optionally, the edge capability calls the cache device, wherein the first acquisition module 610 is further configured to:

[0153] When the capability identifier indicates that the cache information is not the optimal capability for the target application to call the target capability, the capability call validity period corresponding to the cache information is set to 0, and / or the first cache record corresponding to the cache information is deleted.

[0154] Optionally, in the edge capability calling cache device, the first acquisition module 610 is further configured to: when updating the capability identifier, determine whether the capability identifier indicates that the cache information is the optimal capability for the target application to call the target capability.

[0155] Optionally, in the edge capability calling cache device, the capability identifier is used to indicate that the cache information is the optimal capability when the target application calls the target capability.

[0156] Optionally, the edge capability calls the cache device, wherein the sending module 620 sends the cache capability update information to the target application, including:

[0157] The cache capability update information is sent to the target application via a DNS message.

[0158] Optionally, the edge capability calls a cache device, wherein the Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the cache capability update information.

[0159] One embodiment of the present invention further provides an edge capability call cache device, which is applied to target applications, such as Figure 7 As shown, the device includes:

[0160] The second acquisition module 710 is used to obtain cache capability update information sent by the management platform; wherein the cache capability update information is used to indicate that the cache information of the target capability called by the target application has changed;

[0161] The updating module 720 is configured to update the second cache record of the target application according to the cache capability update information, where the second cache record pre-stores cache information of the target application calling the target capability.

[0162] Optionally, the edge capability calls the cache device, wherein the second acquisition module 710 acquires the cache capability update information sent by the management platform, including:

[0163] Acquire cache capability update information sent by the management platform to the target application via a DNS message.

[0164] Optionally, the edge capability calls a cache device, wherein the Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the cache capability update information.

[0165] Optionally, the edge capability calls the cache device, wherein the updating module 720 is further configured to:

[0166] In the updated second cache record, when the cache information of the target capability called by the target application is not the optimal capability, the cache information is deleted.

[0167] One embodiment of the present invention further provides a network device, which includes: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the edge capability call caching method as described in any one of the above items.

[0168] Among them, the network device can be the above-mentioned management platform or application client, and the specific method and process of the edge capability calling cache method implemented when the program is executed by the processor can be referred to the detailed description above and will not be explained here.

[0169] In addition, a specific embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the steps in any one of the above-described edge capability call caching methods.

[0170] Specifically, the computer-readable storage medium is applied to the above-mentioned management platform or application client. When applied to the management platform or application client, the execution steps of the edge capability calling cache method are as described in detail above and will not be repeated here.

[0171] In the several embodiments provided in this application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection of some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0172] In addition, the functional units in various embodiments of the present invention may be integrated into a single processing unit, each unit may be physically included separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or hardware plus software functional units.

[0173] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to perform some of the steps of the sending and receiving methods described in various embodiments of the present invention. The aforementioned storage medium includes: a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, an optical disk, and other media that can store program code.

[0174] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary personnel in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for caching edge capability calls, characterized in that: Applied to a management platform, the method includes: Obtaining a first cache record including cache information of a target application calling a target capability; the first cache record is used to record the capability call validity time and capability identifier corresponding to the cache information; the capability identifier is used to record the capability status of the cache information; If the capability state of the cache information changes within the valid time of the capability call corresponding to the cache information, cache capability update information is sent to the target application; The method further comprises: Obtain capability deployment update information sent by the capability deployment information module; updating the capability identifier in the first cache record according to the capability deployment update information; When the capability identifier indicates that the cache information is not the optimal capability for the target application to call the target capability, the capability call validity period corresponding to the cache information is set to 0, and / or the first cache record corresponding to the cache information is deleted.

2. The edge capability call caching method according to claim 1, characterized in that: The method further comprises: When the cache information is stored in the first cache record, the corresponding capability identifier and the capability call validity period are recorded in correspondence with the cache information.

3. The edge capability call caching method according to claim 1, characterized in that: Get capability deployment update information sent by the capability deployment information module, including: Acquire capability deployment update information sent by the capability deployment information module when capability deployment is updated; or The capability deployment information acquisition module sends capability deployment update information according to a preset period.

4. The edge capability call caching method according to claim 1, characterized in that: The method further comprises: When the capability identifier is updated, it is determined whether the capability identifier indicates that the cache information is the optimal capability for the target application to call the target capability.

5. The edge capability call caching method according to claim 1, characterized in that: The capability identifier is used to indicate that the cache information is the optimal capability when the target application calls the target capability.

6. The edge capability call caching method according to claim 1, characterized in that: Sending cache capability update information to the target application includes: The cache capability update information is sent to the target application via a Domain Name System (DNS) message.

7. The edge capability call caching method according to claim 6, characterized in that: The Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the cache capability update information.

8. An edge capability call caching method, characterized in that: For the target application, the method comprises: Obtaining cache capability update information sent by a management platform; wherein the cache capability update information is used to indicate that cache information for calling a target capability by the target application has changed; wherein the cache capability update information is determined based on a first cache record of the management platform, the first cache record being used to record, on the management platform, a capability call validity period and a capability identifier corresponding to the cache information; the capability identifier being used to record a capability status of the cache information; wherein, when the capability identifier in the first cache record indicates that the cache information is not an optimal capability for calling the target capability by the target application, the capability call validity period corresponding to the cache information is 0, and / or the first cache record corresponding to the cache information is deleted; A second cache record is updated according to the cache capability update information, where the second cache record pre-stores cache information of the target application calling the target capability.

9. The edge capability call caching method according to claim 8, characterized in that: Get cache capability update information sent by the management platform, including: Acquire cache capability update information sent by the management platform to the target application via a DNS message.

10. The edge capability calling cache method according to claim 9, characterized in that: The Opcode field or the Z field of the message header of the DNS message includes identification information, and the identification information is used to indicate that the DNS message is used to send the cache capability update information.

11. The edge capability calling cache method according to claim 8, characterized in that: The method further comprises: In the updated second cache record, when the cache information of the target capability called by the target application is not the optimal capability, the cache information is deleted.

12. A management platform, characterized in that: comprising a processor and a transceiver, wherein: The processor is used to obtain a first cache record including cache information of a target application calling a target capability; the first cache record is used to record the capability call validity time and capability identifier corresponding to the cache information; the capability identifier is used to record the capability status of the cache information; The transceiver is configured to send cache capability update information to the target application if the capability state of the cache information changes within the capability call validity period corresponding to the cache information; The processor is further configured to: Obtain capability deployment update information sent by the capability deployment information module; updating the capability identifier in the first cache record according to the capability deployment update information; When the capability identifier indicates that the cache information is not the optimal capability for the target application to call the target capability, the capability call validity period corresponding to the cache information is set to 0, and / or the first cache record corresponding to the cache information is deleted.

13. An application client, for running a target application, comprising a transceiver and a processor, characterized in that: The transceiver is used to obtain cache capability update information sent by the management platform; wherein the cache capability update information is used to indicate that the cache information of the target capability called by the target application has changed; wherein the cache capability update information is determined according to the first cache record of the management platform, and the first cache record is used to record the capability call validity time and capability identifier corresponding to the cache information on the management platform; the capability identifier is used to record the capability status of the cache information; wherein, when the capability identifier in the first cache record indicates that the cache information is not the optimal capability for the target application to call the target capability, the capability call validity time corresponding to the cache information is 0, and / or the first cache record corresponding to the cache information is deleted; The processor is configured to update a second cache record according to the cache capability update information, where the second cache record pre-stores cache information of the target application calling the target capability.

14. An edge capability call cache device, characterized in that: Applied to a management platform, the device includes: A first acquisition module is configured to acquire a first cache record including cache information of a target application calling a target capability; the first cache record is configured to record a valid time of a capability call corresponding to the cache information and a capability identifier; the capability identifier is configured to record a capability status of the cache information; a sending module, configured to send cache capability update information to the target application if the capability state of the cache information changes within the valid time of the capability call corresponding to the cache information; Wherein, the first acquisition module is further used for: Obtain capability deployment update information sent by the capability deployment information module; updating the capability identifier in the first cache record according to the capability deployment update information; When the capability identifier indicates that the cache information is not the optimal capability for the target application to call the target capability, the capability call validity period corresponding to the cache information is set to 0, and / or the first cache record corresponding to the cache information is deleted.

15. An edge capability call cache device, characterized in that: Applied to an application client, the device includes: A second acquisition module is configured to acquire cache capability update information sent by the management platform; wherein the cache capability update information is used to indicate that cache information for a target capability called by a target application has changed; wherein the cache capability update information is determined based on a first cache record of the management platform, the first cache record being used to record, on the management platform, a capability call validity period and a capability identifier corresponding to the cache information; the capability identifier being used to record a capability status of the cache information; wherein, when the capability identifier in the first cache record indicates that the cache information is not an optimal capability for the target application to call the target capability, the capability call validity period corresponding to the cache information is 0, and / or the first cache record corresponding to the cache information is deleted; The updating module is configured to update a second cache record according to the cache capability update information, wherein the second cache record pre-stores cache information of the target application calling the target capability.

16. A network device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the program implements the edge capability call caching method as described in any one of claims 1 to 7, or implements the edge capability call caching method as described in any one of claims 8 to 11.

17. A readable storage medium, characterized in that The readable storage medium stores a program, and when the program is executed by the processor, the program implements the steps of the edge capability calling caching method according to any one of claims 1 to 7, or implements the steps of the edge capability calling caching method according to any one of claims 8 to 11.

Images