CN115695454B

CN115695454B - Data storage method, device and equipment of MEC host and storage medium

Info

Publication number: CN115695454B
Application number: CN202210662074.6A
Authority: CN
Inventors: 李小青; 王钢; 丁小波; 曾显珣; 黄珊珊; 马嘉; 邱志; 杨联金; 邓建明
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Internet Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Internet Co Ltd
Priority date: 2022-06-13
Filing date: 2022-06-13
Publication date: 2023-10-27
Anticipated expiration: 2042-06-13
Also published as: CN115695454A

Abstract

The application provides a data storage method, device and equipment of an MEC host and a storage medium. The method comprises the following steps: the first MEC host responds to an access operation initiated by a target client for a target MEC application instance, and processes the access of the target client for the target MEC application instance. When the first MEC host finishes the access of the target client to the target MEC application instance, a local preset data storage instance is called, and access data generated by the client accessing the target MEC application instance are stored in a merging mode according to a target merging and storing strategy corresponding to the target MEC application instance, wherein the data storage instance is provided with a merging and storing strategy of each MEC application instance in the first MEC host for the data generated by the client accessing. The application can flexibly use a proper merging and storing strategy to store the data generated by the MEC application instance in the client range, thereby saving the storage space of the MEC host.

Description

Data storage method, device and equipment of MEC host and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for storing data of an MEC host.

Background

Cloud computing is rising, making operators and the internet increasingly sophisticated from partner to competitors. In this case, multiple access edge computation occurs. Multi-access edge computing, i.e. (Multi-access Edge Computing, MEC) is commonly used to describe the concept of pushing services to the edge of an operator network, which is the ability to provide users with cloud-based computing capabilities at the edge of the operator network near the mobile users, which users can employ to deploy applications at the network edge.

The European Telecommunications Standardization Institute (ETSI) defines in its specification ETSI GS MEC 003 a reference architecture for multi-access edge computing, which is mainly composed of two parts: MEC host and multi-access edge computing management system.

The MEC hosts (i.e., mobile edge hosts) include MEC platforms, virtualization infrastructure, and MEC applications. Wherein:

the MEC platform mainly comprises service registration and discovery functions and also comprises public services such as a DNS server or a DNS proxy service.

Virtual infrastructure provides virtualized computing, storage, and network resources for MEC applications.

The MEC application is deployed on the MEC host in the form of a virtual machine or container. The MEC application may include, but is not limited to, an internet of things application, a video cache application, and the like. One MEC application may typically have multiple copies, each of which becomes an application instance, and may be deployed on different MEC hosts, respectively. The terminal device may access the application instances deployed on the MEC hosts in the near future through an access network of the telecommunications carrier.

For the same enterprise, multiple applications may be developed, and corresponding to each application, a corresponding at least one MEC application instance may be deployed on the MEC host. The application instances of different applications each process a corresponding user request, generate related data such as access logs, processing results, and the like, and store the related data in the MEC host. The data size of the data is always of a T level, occupies a larger storage space of the MEC host, and the occupied storage space is directly related to the deployment cost of the application instance of the application development enterprise.

For this reason, how to minimize the occupation of the storage space by the MEC application instance as much as possible is one of the problems to be solved currently.

Disclosure of Invention

The application aims to provide a data storage method, device and equipment of an MEC host and a storage medium, which can flexibly use a proper combined storage strategy to store data generated by an MEC application instance in a client range, thereby saving the storage space of the MEC host.

In order to achieve the above object, embodiments of the present application are realized as follows:

in a first aspect, a data storage method of an MEC host is provided, including:

the method comprises the steps that a first MEC host responds to an access operation initiated by a target client for a target MEC application instance, and the target client accesses the target MEC application instance;

when the first MEC host finishes the access of the target client to the target MEC application instance, a local preset data storage instance is called, and access data generated by the client accessing the target MEC application instance are stored in a merging mode according to a target merging and storing strategy corresponding to the target MEC application instance, wherein the data storage instance is provided with a merging and storing strategy of each MEC application instance in the first MEC host for the data generated by the client accessing.

In a second aspect, there is provided a data storage device of an MEC host, comprising:

An access processing module, configured to process, in response to an access operation initiated by a target client for a target MEC application instance, an access of the target client for the target MEC application instance;

and the merging and storing module is used for calling a local preset data storage instance when the access of the target client to the target MEC application instance is completed, and merging and storing the access data generated by the client accessing the target MEC application instance according to a target merging and storing strategy corresponding to the target MEC application instance, wherein the data storage instance is provided with the merging and storing strategy of each MEC application instance in the first MEC host for the data generated by the client accessing.

In a third aspect, there is provided an electronic device comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being executed by the processor:

processing access of a target client to a target MEC application instance in response to an access operation initiated by the target client to the target MEC application instance;

and when the access of the target client to the target MEC application instance is processed, calling a local preset data storage instance, and carrying out merged storage on access data generated by the client accessing the target MEC application instance according to a target merged storage strategy corresponding to the target MEC application instance, wherein the data storage instance is provided with the merged storage strategy of each MEC application instance in the first MEC host for the data generated by the client accessing.

In a fourth aspect, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

The application sets a matched merging and storing strategy aiming at MEC application examples in an MEC host, and writes execution logic which uses the merging and storing strategy to merge and store data generated by a client accessing the MEC application examples into a data storage example for deployment in the MEC host. When the target client initiates access operation for the target MEC application instance to the MEC host, the MEC host can call the data storage instance after the access of the target client is completed, so as to determine a target merge storage strategy corresponding to the target MEC application instance, and merge and store the access data generated by the target client accessing the target MEC application instance, thereby saving the storage space of the MEC host in a merge storage mode.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.

Fig. 1 is a flow chart of a data storage method of an MEC host according to an embodiment of the present application.

Fig. 2 is a schematic diagram of a data storage method of an MEC host according to an embodiment of the present application.

Fig. 3 is a schematic structural diagram of a data storage device of an MEC host according to an embodiment of the present application.

Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the technical solution in the present specification better understood by those skilled in the art, the technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present specification, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

As described above, the data generated by the client accessing the MEC application instance is often T-level, which occupies a larger storage space of the MEC host. For the enterprise of the application instance issuer, deploying the MEC application instance product of its own at the MEC host requires a large cost for providing the storage space, which severely restricts the development of the MEC ecosphere. Therefore, the application aims to provide a technical scheme capable of reducing the occupied storage space of MEC application examples.

In one aspect, an embodiment of the present application provides a data storage method of an MEC host. FIG. 1 is a flow chart of the data storage method, comprising the steps of:

s102, the first MEC host responds to the access operation initiated by the target client for the target MEC application instance, and the access of the target client for the target MEC application instance is processed.

In the application, the client, i.e. the user equipment, can be, but is not limited to, a mobile phone, a PAD, a tablet personal computer, and the like. The target MEC application instance refers to any one of the MEC application instances deployed in the first MEC host, such as live video, shopping online, etc., which is not specifically limited herein.

S104, when the first MEC host processes the access of the target client side to the target MEC application instance, a local preset data storage instance is called, and access data generated by the client side accessing the target MEC application instance are stored in a merging mode according to a target merging and storing strategy corresponding to the target MEC application instance, wherein the data storage instance is provided with the merging and storing strategy of each MEC application instance in the first MEC host for the data generated by the client side access.

The application writes execution logic for performing merged storage on data generated by a client accessing an MEC application instance by using a merged storage policy into a data storage instance for deployment into a first MEC host. After the first MEC host calls the data storage instance, the execution logic in the data storage instance is directly operated, and then the target merging and storing strategy corresponding to the target MEC application instance can be determined.

It should be understood that the merged storage policy of the present application is not unique and can be, but is not limited to, divided into:

1) Merging and storing MEC application instance generation data of different MEC hosts, wherein the merging and storing policy is defined as a first merging and storing policy;

2) The data of the MEC application instances between different application issuers are consolidated and stored, which is defined herein as a second consolidated and stored policy;

3) Data between different MEC application instances is consolidated and stored, where the consolidated and stored policy is defined herein as a third consolidated and stored policy,

The merged storing strategy of at least part of MEC application instances in the first MEC host is a first merged storing strategy for merging and storing across MEC hosts. If the target merged storing policy is the third merged storing policy, the data storing instance records, for the MEC application instance adopting the first merged storing policy, a storing address of other MEC hosts for replacing the data generated by the first MEC host storing client accessing the MEC application instance. Correspondingly, the step calls a local preset data storage instance to send data generated by the target client accessing the target MEC application instance and identification information associated with the target MEC application instance to the second MEC host according to the target merge storage policy. The second MEC host refers to a MEC host set by the target merge storage policy for storing data instead of the first MEC host. In the application, the second MEC host is provided with a dedicated storage address for storing non-local data aiming at the identification information associated with the target MEC application instance.

In addition, the consolidated storage policy of at least some of the MEC application instances in the first MEC host is a second consolidated storage policy that is consolidated with other application issuers. If the target merged storing policy is the second and storing policies, the data storing instance records a storage address shared by an application issuer to which the target MEC application instance belongs and other application issuers aiming at the MEC application instance of the second merged storing policy; the method specifically calls a local preset data storage instance, and stores data generated by a target client accessing a target MEC application instance into a storage address shared by an application issuer to which the target MEC application instance belongs and other application issuers according to a target merge storage policy.

In addition, the merged storing policy of at least part of the MEC application instances in the first MEC host is a third merged storing policy for merging and storing other MEC application instances; the data storage instance records the storage addresses for the target MEC application instance and the MEC application instance in the first MEC host aiming at the MEC application instance adopting the third merged storage strategy; if the target merge storage policy is the third merge storage policy, the step may call a locally preset data storage instance, and store, according to the target merge storage policy, data generated by the target client accessing the target MEC application instance to a storage address shared by the target MEC application instance and other MEC application instances.

It should be understood that the above three consolidated storage strategies are for exemplary purposes only and are not limiting on the scope of the present application. In practical application, the merge storage strategy of the MEC application instance can be flexibly adjusted.

Such as: the identification information associated with the target MEC application instance may be an issuer identification of the application issuer to which the target MEC application instance belongs. The first MEC host may monitor a total resource occupancy rate of MEC application instances corresponding to local application issuers, and determine a target application issuer whose total resource occupancy rate exceeds a preset standard. And then, the first MEC host determines an MEC application instance which locally adopts a first merged storing strategy and belongs to a target application issuer, and modifies the first merged storing strategy set by the MEC application instance in the data storing instance into a second merged storing strategy, so that the condition that excessive storage space of other MEC hosts is occupied after the MEC application instance adopting the first merged storing strategy is frequently accessed is avoided.

Furthermore, in practical applications, the first MEC host may be provided with a plurality of data storage instances, each data storage instance being provided with a corresponding merged storage policy for at least part of the MEC application embodiments of the first MEC host. The target client may provide an identification of the target data store instance that is desired to be invoked when initiating an access operation for the target MEC application instance. Correspondingly, when the first MEC host finishes the access of the target client to the target MEC application instance, the first MEC host invokes the target data storage instance to store the related data in a merging way.

Based on the foregoing, it can be seen that, in the method of the embodiment of the present application, a matched merge storage policy is set for an MEC application instance in an MEC host, and execution logic for performing merge storage on data generated by a client accessing the MEC application instance by using the merge storage policy is written into a data storage instance for deployment into the MEC host. When the target client initiates access operation for the target MEC application instance to the MEC host, the MEC host can call the data storage instance after the access of the target client is completed, so as to determine a target merge storage strategy corresponding to the target MEC application instance, and merge and store the access data generated by the target client accessing the target MEC application instance, thereby saving the storage space of the MEC host in a merge storage mode.

The data storage mode of the embodiment of the application is described in detail below.

Referring to fig. 2, fig. 2 is a schematic architecture diagram of a data storage method according to the present application, including:

1) MEC host 1

On which it is assumed that MEC application instance 1, MEC application instance 2, MEC application instance 3, etc. are deployed, which application instances are assumed to belong to the same enterprise (i.e. application embodiment issuer), each set or assigned an enterprise identification, such as COM1, corresponding to that enterprise.

In addition, in the MEC host 1, a data storage instance 1 corresponding to the enterprise COM1 is also deployed.

2) MEC application example 1

The MEC application example 1 is configured to perform corresponding data processing in response to an access request of the MEC application example 1 initiated by a certain terminal device (such as UE 1), and obtain data to be saved, where the data includes: access logs, processing results, and the like. After the data to be saved is obtained, the data storage example 1 is called by sending a storage strategy query instruction to the data storage example 1, and the coordination storage of the data is carried out. The storage policy query instruction includes an enterprise identifier COM1 corresponding to the MEC application instance 1, and an identifier of the MEC application instance 1.

Taking MEC application example 1 as a video playing application example, and taking an access request of UE1 as a video downloading request as an example, the corresponding log generally includes: the user ID corresponding to the UE1, the user permission identifier, the timestamp of the access request received by the MEC application instance 1, the video source address of the video requested to be downloaded, the playing behavior data of the user, and the like.

3) MEC application example 2

The MEC application instance 2 is configured to perform corresponding data processing in response to an access request of the MEC application instance 2 initiated by a certain terminal device (such as UE 1), and obtain data to be saved, where the data includes: access logs, processing results, and the like. After the data to be saved is obtained, the data storage example 1 is called by sending a storage strategy query instruction to the data storage example 1, and the coordination storage of the data is carried out. The storage policy query instruction includes an enterprise identifier COM1 corresponding to the MEC application instance 1 and an identifier of the MEC application instance 2.

Taking the MEC application instance 2 as a live shopping application instance, and the access request of the UE1 as a live video playing request as an example, the corresponding log generally includes: user ID corresponding to UE1, user authority identification, time stamp of the MEC application instance 2 receiving the access request, live video source address, browsing behavior data of the user for commodity in live broadcast, etc.

The function and data storage manner of the MEC application examples 3 and 4 are similar to those of the MEC application examples 1 and 2 described above, and will not be described again.

4) Data storage example 1

Data storage example 1, a module of greater importance in the present application. The functions realized by the method comprise:

1. storage policy query and collaborative storage function

The specific implementation process of the function is as follows:

(1) The data storage example 1 responds to a storage strategy query instruction initiated by an MEC application example (such as MEC application example 1/2/3/4) before data storage, and acquires a combined storage strategy table preset in the MEC host 1; the policy table contains the merged storage policies of the MEC application instances deployed by the different enterprises. For example, the policy table is shown in table 1 below.

Table 1: merging storage policy tables

(2) And the data storage example 1 acquires a corresponding combined storage strategy by inquiring the combined storage strategy table according to the enterprise identifier and the identifier of the MEC application example contained in the storage strategy inquiry instruction.

The following illustrates the determination and execution of various types of merged storage policies, respectively:

taking the MEC application example 1 as an example, the data storage example 1 determines that the corresponding merged storing policy is 'merging storing across MEC hosts' according to the identification query tables of COM1 and the application example 1; the data storage example 1 acquires the data to be stored of the application example 1 from the application example 1; further, according to the identification of the enterprise 1, obtaining the address of the MEC host 2 which is preconfigured in the MEC host 1 by the enterprise 1 and is used for storing the data of the application example 1 by inquiring the corresponding relation between the preset identification of the enterprise 1 and the storage address which is stored in a merging way across the MEC hosts; according to the address, the data to be stored and COM1 are sent to a data storage example 2 in the MEC host 2, and the data storage example 2 stores the data to a local storage space corresponding to the enterprise 1 according to the COM1 by inquiring a preset mapping relation between the enterprise 1 identification and the local storage space address. The specific implementation process is shown in fig. 2.

When the data of the application example 1 is stored in the MEC host 2, if the data storage example 2 recognizes that other application examples all have the enterprise identifier COM1 according to the enterprise identifier COM1 of the application example 1, it is determined that the application examples belong to the same enterprise, so that the data are stored in the same table in a merging manner, and when the data are stored in a merging manner, the data under the same user ID are also stored in a merging manner, so that storage resources can be saved as much as possible.

Taking application example 2 as an example:

according to the identification query tables of the COM1 and the application example 1, the data storage example 1 determines that the corresponding merge storage policy is "MEC host 1 local merge storage", and then the data storage example 1 obtains the data to be stored of the application example 2, further obtains a preset storage address for storing the data of the application example of the enterprise 1 locally, and stores the data in the storage address. Similarly, the data of application example 3 is also stored locally.

When the data of the application example 2 and the application example 3 are stored locally, the data storage example 1 is provided with the same enterprise identifier COM1 according to the application example 2 and the application example 3, and identifies that the data belong to the same enterprise, so that the data are stored in the same table in a merging way, and in the merging way, the data under the same user ID are also stored in a merging way, so that storage resources can be saved as much as possible.

Taking application example 4 as an example:

according to the identification query tables of the COM1 and the application example 1, the data storage example 1 determines that the corresponding merged storage strategy is "other enterprises collaborative storage (collaborative correspondence: COM 1-COM 2)", and on the one hand, the data storage example 1 acquires the data to be stored of the application example 4, and on the other hand, according to the collaborative correspondence in the strategy is "COM 1-COM 2", the identification of the collaborative enterprises is determined as COM2, so that the storage address of the local data storage space corresponding to COM2 is further queried.

After the data to be stored of the application example 4 is successfully acquired, the data is stored in the storage space of the COM2 corresponding to the storage address.

It should be noted that, in the present application, the thought of "exchanging data sharing for storage resource saving" is adopted in consideration of the collaborative storage of different enterprises.

Enterprise 1 and enterprise 2 can establish a collaborative correspondence and set up in each MEC host through an offline subscription protocol. In this way, by sharing data to enterprise 2 by enterprise 1, it is possible to achieve a saving of storage resources for enterprise 1, and enterprise 1 does not need to purchase storage space on the MEC separately.

2. Merging storage policy modification functions

The function is mainly aimed at the case of 'merging and storing across MEC hosts', and is started when a specific condition is met.

In particular, as business progresses, there may be more and more application instances of an enterprise on the same MEC host (such as MEC host 1), and the data generated by these application instances may occupy a larger proportion of the data generated by all application instances deployed on the MEC host 1.

In such a case, if the application of the enterprise adopts "merge storage across MEC hosts", a larger data migration volume is involved, and more transmission resources are consumed.

Therefore, taking table 1 as an example, the present application proposes that the MEC host 1 monitor the relevant information of the application instance deployed on the MEC host 1 by the enterprise corresponding to the "merge storage across MEC hosts" policy.

The relevant information here includes:

the enterprise adopts the quantity of application instances of the 'cross MEC host merging and storing' strategy;

the enterprise adopts the access times of application instances of the 'cross MEC host merging and storing' strategy in a specified time length (such as one day or one week);

the enterprise adopts a cross-MEC host merge storage strategy to merge the ratio of the data volume stored on other MEC hosts to the data volume generated by all application instances deployed on the MEC host 1 by the enterprise.

If any of the above values is greater than the corresponding preset number threshold (e.g., the number of application instances is greater than the preset number threshold). The MEC host 1 reads a locally stored rights identification indicating whether the MEC1 host 1 has storage policy modification rights for the enterprise; if the permission mark is 1, indicating that the permission is provided, so that the cross MEC host merging storage of the enterprise in the table 1 is modified into local merging storage; if the permission mark is 0, the MEC host 1 does not have the permission, so that only the notification about the excessive data migration quantity is sent to the notification message receiving address appointed by the enterprise, and the enterprise can know the related situation.

On the other hand, corresponding to the method shown in fig. 1, the embodiment of the application further provides a data storage device of the MEC host. FIG. 3 is a schematic diagram of a data storage device system 300 according to an embodiment of the present application, including:

an access processing module 310, configured to process, in response to an access operation initiated by a target client for a target MEC application instance, an access of the target client for the target MEC application instance;

and the merge storage module 320 is configured to invoke a locally preset data storage instance when the access of the target client to the target MEC application instance is completed, and merge and store access data generated by the client accessing the target MEC application instance according to a target merge and storage policy corresponding to the target MEC application instance, where the data storage instance is provided with a merge and storage policy of each MEC application instance in the first MEC host for data generated by the client accessing.

The device of the embodiment of the application sets a matched merging and storing strategy for the MEC application instance in the MEC host, and writes the execution logic for merging and storing the data generated by the client accessing the MEC application instance by using the merging and storing strategy into the data storage instance for deployment into the MEC host. When the target client initiates access operation for the target MEC application instance to the MEC host, the MEC host can call the data storage instance after the access of the target client is completed, so as to determine a target merge storage strategy corresponding to the target MEC application instance, and merge and store the access data generated by the target client accessing the target MEC application instance, thereby saving the storage space of the MEC host in a merge storage mode.

Optionally, the merged storing policy of at least some MEC application instances in the first MEC host is a first merged storing policy of merged storing across MEC hosts; the data storage instance records the storage address of other MEC hosts for replacing the data generated by the first MEC host storage client accessing the MEC application instance aiming at the MEC application instance adopting the first merged storage strategy; if the target merged storing policy is the first merged storing policy, the merged storing module 320 is specifically configured to: and calling a local preset data storage instance, and sending data generated by the target client accessing the target MEC application instance and identification information associated with the target MEC application instance to the second MEC host according to the target merge storage policy, wherein the second MEC host is an MEC host which is set by the target merge storage policy and used for replacing the first MEC host to store data, and a special storage address used for storing non-local data is set by the second MEC host for the identification information associated with the target MEC application instance.

Optionally, the merged storing policy of at least some MEC application instances in the first MEC host is a second merged storing policy that is merged storing with other application issuers; the data storage instance records a storage address shared by an application issuer to which the target MEC application instance belongs and other application issuers aiming at the MEC application instance of the second merged storage strategy; if the target merged storing policy is the second merged storing policy, the merged storing module 320 is specifically configured to: and calling a local preset data storage instance, and storing data generated by the target client accessing the target MEC application instance into a storage address shared by an application issuer to which the target MEC application instance belongs and other application issuers according to the target merged storage policy.

The identification information associated with the target MEC application instance is an issuer identification of an application issuer to which the target MEC application instance belongs. The data storage device further includes: the storage strategy modification module is used for monitoring the total resource occupancy rate of MEC application instances corresponding to each local application issuer and determining a target application issuer with the total resource occupancy rate exceeding a preset standard; and determining an MEC application instance locally adopting a first merged storing policy and belonging to the target application issuer, and modifying the first merged storing policy set by the MEC application instance in the data storing instance into a second merged storing policy.

Wherein the resource occupancy corresponding to any application issuer in the first MEC host is determined based on at least one of:

the number of all MEC application instances in the application issuer that employ the first consolidated storage policy;

the access frequency of all MEC application instances adopting the first merged storing policy in the issuer of the application;

the access duty of all MEC application instances in the application issuer that employ the first consolidated storage policy in all MEC application instances in the application issuer.

Optionally, the merged storing policy of at least some MEC application instances in the first MEC host is a third merged storing policy for merging storing other MEC application instances; the data storage instance records the storage addresses for the target MEC application instance and the MEC application instance in the first MEC host aiming at the MEC application instance adopting the third merged storage strategy; if the target merged storing policy is the third merged storing policy, the merged storing module 320 is specifically configured to: and calling a local preset data storage instance, and storing data generated by the target client accessing the target MEC application instance into a storage address shared by the target MEC application instance and other MEC application instances according to the target merged storage policy.

It is obvious that the data storage device shown in fig. 3 of the present application may be used as an execution body of the method shown in fig. 1, so that the steps and functions in the method shown in fig. 1 can be implemented, and the details are not repeated herein because the principles are the same.

Fig. 4 is a schematic structural view of an electronic device according to an embodiment of the present specification. Referring to fig. 4, at the hardware level, the electronic device includes a processor, and optionally an internal bus, a network interface, and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory (non-volatile Memory), such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.

The processor, network interface, and memory may be interconnected by an internal bus, which may be an ISA (Industry Standard Architecture ) bus, a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus, or EISA (Extended Industry Standard Architecture ) bus, among others. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in FIG. 4, but not only one bus or type of bus.

And the memory is used for storing programs. In particular, the program may include program code including computer-operating instructions. The memory may include memory and non-volatile storage and provide instructions and data to the processor.

The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs, and the data storage device of the MEC host is formed on a logic level. Correspondingly, the processor executes the program stored in the memory and is specifically configured to perform the following operations:

in response to an access operation initiated by a target client for a target MEC application instance, processing access by the target client for the target MEC application instance.

The electronic equipment of the embodiment of the application sets a matched merging and storing strategy aiming at the MEC application instance in the MEC host, and writes execution logic for merging and storing data generated by the client accessing the MEC application instance by using the merging and storing strategy into a data storage instance for deployment into the MEC host. When the target client initiates access operation for the target MEC application instance to the MEC host, the MEC host can call the data storage instance after the access of the target client is completed, so as to determine a target merge storage strategy corresponding to the target MEC application instance, and merge and store the access data generated by the target client accessing the target MEC application instance, thereby saving the storage space of the MEC host in a merge storage mode.

The method disclosed in the embodiment shown in fig. 1 of the present specification can be applied to a processor and implemented by the processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It should be understood that the electronic device according to the embodiment of the present application may enable the service processing apparatus to implement steps and functions corresponding to those in the method shown in fig. 1. Since the principle is the same, the description is not repeated here.

Of course, in addition to the software implementation, the electronic device in this specification does not exclude other implementations, such as a logic device or a combination of software and hardware, that is, the execution subject of the following process is not limited to each logic unit, but may also be hardware or a logic device.

Furthermore, an embodiment of the present application also proposes a computer-readable storage medium storing one or more programs, the one or more programs including instructions.

Wherein the instructions, when executed by a portable electronic device comprising a plurality of applications, cause the portable electronic device to perform the steps of the method shown in fig. 1, comprising:

It will be appreciated by those skilled in the art that embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the present specification may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The foregoing is merely an example of the present specification and is not intended to limit the present specification. Various modifications and alterations to this specification will become apparent to those skilled in the art. Any modifications, equivalent substitutions, improvements, or the like, which are within the spirit and principles of the present description, are intended to be included within the scope of the claims of the present description. Moreover, all other embodiments obtained by those skilled in the art without making any inventive effort shall fall within the scope of protection of this document.

Claims

1. A method of data storage for an MEC host, comprising:

when the first MEC host finishes the access of the target client to the target MEC application instance, calling a local preset data storage instance, and carrying out merged storage on access data generated by the target client accessing the target MEC application instance according to a target merged storage strategy corresponding to the target MEC application instance, wherein the data storage instance is provided with a merged storage strategy of each MEC application instance in the first MEC host for the data generated by the client access;

the merged storing strategy of at least part of MEC application instances in the first MEC host is a first merged storing strategy for merging and storing across MEC hosts; the data storage instance records the storage address of other MEC hosts for replacing the data generated by the first MEC host storage client accessing the MEC application instance aiming at the MEC application instance adopting the first merged storage strategy; if the target merge storage policy is the first merge storage policy, invoking a local preset data storage instance, and performing merge storage on access data generated by the target client accessing the target MEC application instance according to the target merge storage policy corresponding to the target MEC application instance, wherein the method comprises the following steps:

And calling a local preset data storage instance, and sending data generated by the target client accessing the target MEC application instance and identification information associated with the target MEC application instance to a second MEC host according to the target merge storage policy, wherein the second MEC host is an MEC host which is set by the target merge storage policy and used for replacing the first MEC host to store data, and a special storage address used for storing non-local data is set by the second MEC host aiming at the identification information associated with the target MEC application instance.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the merged storing strategy of at least part of MEC application instances in the first MEC host is a second merged storing strategy which is merged storing with other application issuers;

the data storage instance records a storage address shared by an application issuer to which the target MEC application instance belongs and other application issuers aiming at the MEC application instance of the second merged storage strategy;

and if the target merge storage policy is the second merge storage policy, invoking a local preset data storage instance, and performing merge storage on access data generated by the target client accessing the target MEC application instance according to the target merge storage policy corresponding to the target MEC application instance, wherein the method comprises the following steps:

And calling a local preset data storage instance, and storing data generated by the target client accessing the target MEC application instance into a storage address shared by an application issuer to which the target MEC application instance belongs and other application issuers according to the target merged storage policy.

3. The method of claim 2, wherein the step of determining the position of the substrate comprises,

the identification information associated with the target MEC application instance is an issuer identification of an application issuer to which the target MEC application instance belongs.

4. A method according to claim 3, further comprising:

the first MEC host monitors the total resource occupancy rate of MEC application instances corresponding to local application issuers and determines a target application issuer with the total resource occupancy rate exceeding a preset standard;

the first MEC host determines an MEC application instance which locally adopts a first merged storing policy and belongs to the target application issuer, and modifies the first merged storing policy set by the MEC application instance in the data storing instance into a second merged storing policy.

5. The method of claim 4, wherein the step of determining the position of the first electrode is performed,

the resource occupancy corresponding to any application issuer in the first MEC host is determined based on at least one of:

the access frequency of all MEC application instances in the application issuer adopting the first merged storing policy;

all MEC application instances in the application issuer that employ the first consolidated storage policy have access to all MEC application instances in the application issuer.

6. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the merged storing strategy of at least part of MEC application examples in the first MEC host is a third merged storing strategy for merging and storing other MEC application examples;

the data storage instance records a storage address shared by the target MEC application instance and the MEC application instance in the first MEC host aiming at the MEC application instance adopting the third merged storage strategy;

and if the target merge storage policy is the third merge storage policy, invoking a local preset data storage instance, and performing merge storage on access data generated by the target client accessing the target MEC application instance according to the target merge storage policy corresponding to the target MEC application instance, wherein the method comprises the following steps:

and calling a local preset data storage instance, and storing data generated by the target client accessing the target MEC application instance into a storage address shared by the target MEC application instance and other MEC application instances according to the target merged storage policy.

7. A data storage device of an MEC host, comprising:

the merging and storing module is used for calling a local preset data storage instance when the target client accesses the target MEC application instance, merging and storing the access data generated by the target client accessing the target MEC application instance according to a target merging and storing strategy corresponding to the target MEC application instance, wherein the data storage instance is provided with a merging and storing strategy of each MEC application instance in the first MEC host for the data generated by the client accessing;

the merged storing strategy of at least part of MEC application instances in the first MEC host is a first merged storing strategy for merging and storing across MEC hosts; the data storage instance records the storage address of other MEC hosts for replacing the data generated by the first MEC host storage client accessing the MEC application instance aiming at the MEC application instance adopting the first merged storage strategy; if the target merge storage policy is the first merge storage policy, the merge storage module invokes a local preset data storage instance, and sends data generated by the target client accessing the target MEC application instance and identification information associated with the target MEC application instance to a second MEC host according to the target merge storage policy, wherein the second MEC host is an MEC host set by the target merge storage policy and used for replacing the first MEC host to store data, and the second MEC host is provided with a dedicated storage address used for storing non-local data for the identification information associated with the target MEC application instance.

8. An electronic device includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the computer program is executed by the processor to:

when the access of the target client to the target MEC application instance is processed, a local preset data storage instance is called, access data generated by the target client to access the target MEC application instance is stored in a merging mode according to a target merging and storing strategy corresponding to the target MEC application instance, and the data storage instance is provided with a merging and storing strategy of each MEC application instance in the first MEC host for the data generated by the client access;

9. A computer readable storage medium having a computer program stored thereon, the computer program when executed by a processor performing the steps of:

The merged storing strategy of at least part of MEC application instances in the first MEC host is a first merged storing strategy for merging and storing across MEC hosts; the data storage instance records, for an MEC application instance adopting a first merge storage policy, a storage address of data generated by using other MEC hosts to replace the first MEC host to store a client to access the MEC application instance, and if the target merge storage policy is the first merge storage policy, invokes a locally preset data storage instance, and performs merge storage on access data generated by using the target client to access the target MEC application instance according to a target merge storage policy corresponding to the target MEC application instance, where the method includes: