CN115695454A

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

Info

Publication number: CN115695454A
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-02-03
Anticipated expiration: 2042-06-13
Also published as: CN115695454B

Abstract

The application provides a data storage method, a data storage device, data storage equipment and a data storage medium of an MEC host. The method comprises the following steps: the first MEC host processes 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. When the first MEC host processes and finishes the access of the target client to the target MEC application instance, calling a locally preset data storage instance, and carrying out combined storage on access data generated by the client accessing the target MEC application instance according to a target combined storage policy corresponding to the target MEC application instance, wherein the data storage instance is provided with a combined storage policy of data generated by each MEC application instance in the first MEC host for the client access. The method and the device can flexibly use a proper merging storage 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, equipment and storage medium of MEC host

Technical Field

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

Background

Cloud computing has emerged, making operators and the internet have increasingly turned from partners to competitors. In this case, multiple access edge calculation occurs. Multi-access Edge Computing, MEC, is commonly used to describe the concept of pushing services towards the Edge of an operator network, by providing users with cloud-based Computing capabilities at the Edge of the operator network close to mobile users, which the users can use to deploy applications at the network Edge.

The european telecommunication standardization organization (ETSI) defines in its specification ETSI GS MEC 003 a reference architecture for multiple access edge computing, which is mainly composed of two parts: MEC hosts and a multi-access edge compute management system.

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 some public services, such as a DNS server or a DNS proxy service.

Virtual infrastructure, providing virtualized compute, storage, and network resources for MEC applications.

And the MEC application is deployed on the MEC host in the form of a virtual machine or a container. MEC applications, such as may include, but are not limited to, car networking applications, internet of things applications, video caching applications, and the like. An MEC application may generally have multiple copies, each copy becomes an application instance, and may be deployed on different MEC hosts. The terminal devices may access the application instances deployed on the MEC hosts nearby through the telecommunications operator's access network.

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

Therefore, how to minimize the occupation of the memory space by the MEC application instance as much as possible is one of the problems to be solved at present.

Disclosure of Invention

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

In order to achieve the above purpose, the embodiments of the present application are implemented as follows:

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

the first MEC host responds to an access operation initiated by a target client aiming at a target MEC application instance, and processes the access of the target client aiming at the target MEC application instance;

when the first MEC host processes and finishes the access of the target client to the target MEC application instance, calling a locally preset data storage instance, and carrying out combined storage on access data generated by the client accessing the target MEC application instance according to a target combined storage policy corresponding to the target MEC application instance, wherein the data storage instance is provided with a combined storage policy of data generated by each MEC application instance in the first MEC host for the client access.

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

the access processing module is used for responding to an access operation initiated by a target client aiming at a target MEC application instance, and processing the access of the target client aiming at the target MEC application instance;

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

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

processing an 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;

when the access of the target client to the target MEC application instance is completed, calling a locally preset data storage instance, and performing merged storage on access data generated by the client accessing the target MEC application instance according to a target merged storage policy corresponding to the target MEC application instance, wherein the data storage instance is provided with a merged storage policy of data generated by each MEC application instance in the first MEC host for the client access.

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

The method and the device aim at the MEC application instance in the MEC host to set the matched merging storage strategy, and compile execution logic for merging and storing data generated by the MEC application instance accessed by the client side by using the merging storage strategy into the data storage instance so as to deploy the data storage instance to the MEC host. When the target client initiates an access operation aiming at the target MEC application example to the MEC host, after the MEC host processes and finishes the access of the target client, the MEC host can call the data storage example to determine a target merging storage strategy corresponding to the target MEC application example so as to merge and store the access data generated by the target client accessing the target MEC application example, thereby saving the storage space of the MEC host in a merging and storing manner.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative efforts.

Fig. 1 is a schematic flowchart of a data storage method of an MEC host according to an embodiment of the present disclosure.

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

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

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 those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without making any creative effort shall fall within the protection scope of the present specification.

As described above, data generated by accessing the MEC application instance by the client is often T-level, and occupies a large storage space of the MEC host. For the enterprise of the application instance issuer, the deployment of the MEC application instance product on the MEC host requires a large cost for providing the storage space, which severely restricts the development of the MEC ecosystem. Therefore, the application aims to provide a technical scheme capable of reducing the storage space occupation of the MEC application example.

In one aspect, an embodiment of the present application provides a data storage method for an MEC host. Fig. 1 is a flowchart of the data storage method, including the steps of:

and S102, the first MEC host responds to the access operation initiated by the target client aiming at the target MEC application example, and processes the access of the target client aiming at the target MEC application example.

In the present application, the client, i.e., the user equipment, may be, but is not limited to, a mobile phone, a PAD, a tablet computer, and the like. The target MEC application instance refers to any MEC application instance deployed in the first MEC host, such as an application instance for live video, online shopping, and the like, and is not specifically limited herein.

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

The method and the device for executing the Mec application instance compile the execution logic of executing the Mec application instance to perform the Mec storage on the data generated by the client accessing the MEC application instance by using the Mec storage policy into the data storage instance so as to deploy the data storage instance to the first MEC host. After calling the data storage instance, the first MEC host directly runs an execution logic in the data storage instance, and then a target merging storage strategy corresponding to the target MEC application instance can be determined.

It should be understood that the merged storing strategy of the present application is not exclusive and can be divided into, but not limited to:

1) Performing merge storage across the MEC hosts, that is, merging data generated by MEC application instances of different MEC hosts, where the merge storage policy is defined as a first merge storage policy;

2) Merging and storing the data of the MEC application instances among different application distributors, wherein the merging and storing strategy is defined as a second merging and storing strategy;

3) The merged storing policy is defined as a third merged storing policy,

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

In addition, the merge storage policy of at least part of the MEC application instances in the first MEC host is a second merge storage policy for merge storage with other application issuers. If the target merge storage policy is a second merge storage policy, 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 for the MEC application instance of the second merge storage policy; specifically calling a locally preset data storage instance, and storing data generated by accessing the target MEC application instance by the target client to a storage address shared by an application issuer to which the target MEC application instance belongs and other application issuers according to a target merging storage policy.

In addition, the merge storage policy of at least part of the MEC application instances in the first MEC host is a third merge storage policy for performing merge storage on other MEC application instances; the data storage instance records a storage address used by a target MEC application instance and an MEC application instance in the first MEC host aiming at the MEC application instance adopting a third combined and stored strategy; if the target merge storage policy is the third merge storage policy, this 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 another MEC application instance.

It should be understood that the above three merged storing strategies are only used for exemplary presentation and do not limit the scope of the present disclosure. In practical application, the merge storage policy of the MEC application instance can also be flexibly adjusted.

Such as: the identification information associated with the target MEC application instance may be an issuer identification of an application issuer to which the target MEC application instance belongs. The first MEC host can monitor the total resource occupancy rate of MEC application instances corresponding to each local application issuer and determine a target application issuer with the total resource occupancy rate exceeding a preset standard. And then, the first MEC host determines an MEC application instance which locally adopts the first merge storage strategy and belongs to the target application issuer, and modifies the first merge storage strategy set in the data storage instance by the MEC application instance into a second merge storage strategy, so that the MEC application instance adopting the first merge storage strategy is prevented from occupying excessive storage space of other MEC hosts after being frequently accessed.

In addition, 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 consolidated storage policy for at least some MEC application embodiments of the first MEC host. The target client, upon initiating an access operation for the target MEC application instance, may provide an identification of the target data store instance desired to be invoked. Correspondingly, the first MEC host may invoke the target data storage instance therein to perform merged storage on the related data when processing is completed and the target client accesses the target MEC application instance.

Based on the above, the method of the embodiment of the application sets the matched merge storage policy for the MEC application instance in the MEC host, and compiles the execution logic, which performs merge storage on the data generated by the client accessing the MEC application instance by using the merge storage policy, into the data storage instance, so as to deploy the data storage instance to the MEC host. When the target client initiates an access operation aiming at the target MEC application example to the MEC host, after the MEC host processes and finishes the access of the target client, the MEC host can call the data storage example to determine a target merging storage strategy corresponding to the target MEC application example so as to merge and store the access data generated by the target client accessing the target MEC application example, thereby saving the storage space of the MEC host in a merging and storing manner.

The data storage method according to the embodiment of the present application will be described in detail below.

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

1) MEC host 1

It is assumed that MEC application instance 1, MEC application instance 2, MEC application instance 3, etc. are deployed, and these application instances are assumed to belong to the same enterprise (i.e., application embodiment issuer), and are all set or assigned with an enterprise identity, such as COM1, corresponding to the 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 instance 1 is configured to, in response to an access request of the MEC application instance 1 initiated by a certain terminal device (e.g., UE 1), execute corresponding data processing, and obtain data to be stored — including: access logs, processing results, and the like. After the data needing to be stored is obtained, the data storage example 1 is called in a mode of sending a storage strategy query instruction to the data storage example 1, and coordinated 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 the MEC application instance 1 as a video playing application instance and the access request of the UE1 as a video downloading request as an example, the corresponding log generally includes: the user ID and the user right identifier corresponding to the UE1, the timestamp when the MEC application instance 1 receives the access request, the video source address of the video requested to be downloaded, the play behavior data of the user, and the like.

3) MEC application example 2

The MEC application instance 2 is configured to, in response to an access request of the MEC application instance 2 initiated by a certain terminal device (e.g., UE 1), execute corresponding data processing, and obtain data to be stored — including: access logs, processing results, and the like. After the data needing to be stored is obtained, the data storage example 1 is called to perform the coordinated storage of the data by sending a storage strategy query instruction to the data storage example 1. 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: the user ID and the user authority identification corresponding to the UE1, the timestamp of the MEC application instance 2 receiving the access request, the live broadcast video source address, the browsing behavior data of the user on the commodities in the live broadcast and the like.

The functions and data storage modes of the MEC application examples 3 and 4 are similar to those of the MEC application examples 1 and 2, and are not described again.

4) Data storage example 1

Data storage example 1 is a relatively important module in the present application. The realized functions comprise:

1. storage policy query and collaborative storage functionality

The function is realized in the following steps:

(1) The data storage example 1 responds to a storage policy 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 policy table preset in an MEC host 1; the policy table contains merged storage policies of MEC application instances respectively deployed by different enterprises. For example, the policy table is shown in table 1 below.

Table 1: merging storage policy tables

(2) The data storage example 1 obtains the corresponding merged storage policy by querying the merged storage policy table according to the enterprise identifier and the identifier of the MEC application example included in the storage policy query instruction.

The determination and execution of various types of merged storage policies are illustrated below:

taking the MEC application example 1 as an example, the data storage example 1 determines that the corresponding merging storage policy is 'cross-MEC host merging storage' according to the identification query table of the 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 identifier of the enterprise 1, by inquiring the corresponding relation between the preset identifier of the enterprise 1 and the storage address merged and stored across the MEC host, the address of the MEC host 2, which is configured in advance to the MEC host 1 by the enterprise 1 and used for storing the data of the application example 1, is obtained; and sending the data to be stored and the COM1 to a data storage instance 2 in the MEC host 2 according to the address, and storing the data to a local storage space corresponding to the enterprise 1 by querying a mapping relation between a preset enterprise 1 identifier and a local storage space address through the data storage instance 2 according to the COM1. 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, and therefore the data is merged and stored in the same table, and during merging and storage, the data under the same user ID is also merged and stored, so that the storage resources can be saved as much as possible.

Taking application example 2 as an example:

the data storage example 1 determines that the corresponding merge storage policy is "MEC host 1 local merge storage" according to the identification query table of the COM1 and the application example 1, and then the data storage example 1 acquires the data to be stored of the application example 2, further acquires a preset storage address for locally storing the data of the application example of the enterprise 1, and stores the data into the storage address. Similarly, the data of application instance 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 recognizes that the application example 2 and the application example 3 belong to the same enterprise according to the fact that the application example 2 and the application example 3 both have the same enterprise identifier COM1, so that the data are merged and stored in the same table, and during merging and storage, the data under the same user ID are also merged and stored, so that the storage resources can be saved as much as possible.

Taking application example 4 as an example:

the data storage example 1 determines that the corresponding merged storage policy is "other enterprise collaborative storage (collaborative correspondence: COM1 — COM 2)" according to the identification query table of the COM1 and the application example 1, on one hand, the data storage example 1 acquires the data to be stored of the application example 4, on the other hand, determines that the identification of the collaborative enterprise is COM2 according to the collaborative correspondence "COM1 — COM2" in the policy, thereby further querying and obtaining the storage address of the local data storage space corresponding to COM 2.

And after the data to be stored of the application example 4 is successfully acquired, storing the data into the storage space of the COM2 corresponding to the storage address.

It should be noted that, in the present application, a concept of "saving storage resources by sharing data" is adopted in consideration of collaborative storage by different enterprises.

The enterprise 1 and the enterprise 2 sign an agreement through the offline, can establish a cooperative corresponding relation and set the cooperative corresponding relation to each MEC host. In this way, by sharing data with the enterprise 1 to the enterprise 2, the storage resource can be saved for the enterprise 1, and the enterprise 1 does not need to separately purchase a storage space on the MEC.

2. Merging storage policy modification functions

This function is mainly directed to the case of "merge storage across MEC hosts", starting when certain conditions are met.

A specific consideration is that, as the business of an enterprise develops, an enterprise on the same MEC host (for example, MEC host 1) may have more application instances, and data generated by the application instances may occupy a larger proportion of data generated by all application instances deployed on the MEC host 1.

In such a case, if the application of the enterprise employs "merge storage across MEC hosts", a large data migration amount is involved, and a large amount of transmission resources are consumed.

Therefore, taking table 1 as an example, the application provides that the MEC host 1 monitors the relevant information of the application instance deployed on the MEC host 1 by the enterprise corresponding to the policy of "merging and storing across MEC hosts".

The related information referred to herein includes:

the enterprise adopts the number of application instances of a strategy of 'merging and storing across MEC hosts';

the number of accesses within a specified length of time (e.g., one day or one week) by the enterprise to an application instance that employs a "merge store across MEC hosts" policy;

the enterprise adopts a strategy of 'cross MEC host merging storage' to merge the data volume stored on other MEC hosts into the ratio of 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 permission identifier indicating whether the MEC1 host 1 has a storage policy modification permission for the enterprise; if the authority identifier is 1, the authority is indicated to be possessed, so that the enterprise 'cross MEC host merged storage' in the table 1 is modified into 'local merged storage'; if the authority identifier is 0, it indicates that the MEC host 1 does not have the authority, so that only a notification about excessive data migration is sent to the notification message receiving address specified by the enterprise, so that the enterprise can know the relevant conditions.

On the other hand, corresponding to the method shown in fig. 1, an embodiment of the present application further provides a data storage device of the MEC host. Fig. 3 is a schematic structural 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 an access of a target client to a target MEC application instance in response to an access operation initiated by the target client for the target MEC application instance;

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

The device provided by the embodiment of the application sets a matched merging storage strategy for the MEC application instance in the MEC host, and compiles execution logic for merging and storing data generated by accessing the MEC application instance by the client side by using the merging storage strategy into a data storage instance so as to deploy the data storage instance to the MEC host. When the target client initiates an access operation aiming at the target MEC application example to the MEC host, after the MEC host processes and finishes the access of the target client, the MEC host can call the data storage example to determine a target merging storage strategy corresponding to the target MEC application example so as to merge and store the access data generated by the target client accessing the target MEC application example, thereby saving the storage space of the MEC host in a merging and storing manner.

Optionally, the merge storage policy of at least part of the MEC application instances in the first MEC host is a first merge storage policy for performing merge storage across the MEC hosts; the data storage instance records, for the MEC application instance adopting the first combined storage policy, a storage address of another MEC host for replacing the first MEC host storage client to access data generated by the MEC application instance; if the target merged storing policy is the first merged storing policy, the merged storing module 320 is specifically configured to: calling a locally 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 merging storage policy, wherein the second MEC host is an MEC host which is set by the target merging 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 for storing non-local data aiming at the identification information associated with the target MEC application instance.

Optionally, the merge storage policy of at least a part of the MEC application instances in the first MEC host is a second merge storage policy for merge storage 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 for 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 locally 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 merging storage policy.

And the identification information associated with the target MEC application instance is the issuer identification of the 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 the 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 example which locally adopts a first merge storage strategy and belongs to the target application issuer, and modifying the first merge storage strategy set in the data storage example by the MEC application example into a second merge storage strategy.

Wherein the resource occupancy rate 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 adopting the first merged storing strategy in an application issuer;

the access frequency of all MEC application instances adopting the first combined storage strategy in the application issuer;

and the access ratio of all MEC application instances adopting the first merge storage strategy in the application issuer to all MEC application instances in the application issuer.

Optionally, the merge storage policy of at least part of the MEC application instances in the first MEC host is a third merge storage policy for performing merge storage on other MEC application instances; the data storage instance records storage addresses used by the target MEC application instance and the MEC application instance in the first MEC host aiming at the MEC application instance adopting a third combined and stored 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 locally 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 merging storage strategy.

Obviously, the data storage device shown in fig. 3 of the present application may be used as an execution main body of the method shown in fig. 1, so that steps and functions in the method shown in fig. 1 can be implemented, and are not described in detail herein because the principle is the same.

Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. Referring to fig. 4, at a hardware level, the electronic device includes a processor, and optionally further includes 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, such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.

The processor, the network interface, and the memory may be connected to each other via an internal bus, which may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 4, but that does not indicate only one bus or one type of bus.

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

The processor reads a corresponding computer program from the nonvolatile memory into the memory and then runs the computer program, 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:

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

The electronic device of the embodiment of the application sets a matched merge storage policy for the MEC application instance in the MEC host, and writes execution logic for performing merge storage on data generated by a client accessing the MEC application instance by using the merge storage policy into the data storage instance to be deployed in the MEC host. When a target client initiates an access operation aiming at a target MEC application example to an MEC host, after the MEC host processes and finishes the access of the target client, the MEC host can call a data storage example to determine a target merging storage strategy corresponding to the target MEC application example so as to merge and store access data generated by the target client accessing the target MEC application example, and therefore the storage space of the MEC host is saved in a merging and storing mode.

The method disclosed in the embodiment of fig. 1 in this 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 instructions in the form of software. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed 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 directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in ram, flash, rom, prom, or eprom, registers, etc. as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

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

Of course, besides the software implementation, the electronic device in the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

In addition, an embodiment of the present application also provides a computer-readable storage medium storing one or more programs, where the one or more programs include instructions.

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

and responding to an access operation initiated by a target client aiming at a target MEC application instance, and processing the access of the target client aiming at the target MEC application instance.

When the access of the target client to the target MEC application instance is finished, calling a locally preset data storage instance, and performing combined storage on access data generated by the client accessing the target MEC application instance according to a target combined storage strategy corresponding to the target MEC application instance, wherein the data storage instance is provided with a combined storage strategy of data generated by each MEC application instance in the first MEC host for the client access.

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

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may 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 may also be possible or may be advantageous.

The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification. Moreover, all other embodiments obtained by a person skilled in the art without making any inventive step shall fall within the scope of protection of this document.

Claims

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

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

2. The method of claim 1,

the merge storage policy of at least part of MEC application instances in the first MEC host is a first merge storage policy for performing merge storage across MEC hosts;

the data storage instance records, for the MEC application instance adopting the first combined storage policy, a storage address of another MEC host for replacing the first MEC host storage client to access data generated by the MEC application instance;

if the target merge storage policy is the first merge storage policy, invoking a locally preset data storage instance, and according to the target merge storage policy corresponding to the target MEC application instance, including:

calling a locally 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 merging storage policy, wherein the second MEC host is an MEC host which is set by the target merging 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 for storing non-local data aiming at the identification information associated with the target MEC application instance.

3. The method of claim 2,

the merge storage policy of at least part of MEC application instances in the first MEC host is a second merge storage policy for merge storage 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 for the MEC application instance of the second combined storage policy;

if the target merge storage policy is the second merge storage policy, calling a locally preset data storage instance, and according to the target merge storage policy corresponding to the target MEC application instance, including:

and calling a locally 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 merging storage policy.

4. The method of claim 3,

and the identification information associated with the target MEC application example is the issuer identification of the application issuer to which the target MEC application example belongs.

5. The method of claim 4, further comprising:

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

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

6. The method of claim 5,

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

and all MEC application instances adopting the first merged storing strategy in the application issuer are accessed in the proportion of all MEC application instances in the application issuer.

7. The method of claim 1,

the merge storage policy of at least part of the MEC application instances in the first MEC host is a third merge storage policy for performing merge storage on other MEC application instances;

the data storage instance records a storage address used by the target MEC application instance and an MEC application instance in the first MEC host aiming at an MEC application instance adopting a third combined and stored strategy;

if the target merge storage policy is the third merge storage policy, invoking a locally preset data storage instance, and according to the target merge storage policy corresponding to the target MEC application instance, including:

and calling a locally 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 merging storage strategy.

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

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

9. 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:

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

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