CN110098947B - Application deployment method, device and system - Google Patents

Application deployment method, device and system Download PDF

Info

Publication number
CN110098947B
CN110098947B CN201810097147.5A CN201810097147A CN110098947B CN 110098947 B CN110098947 B CN 110098947B CN 201810097147 A CN201810097147 A CN 201810097147A CN 110098947 B CN110098947 B CN 110098947B
Authority
CN
China
Prior art keywords
application
mec
network element
identifier
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810097147.5A
Other languages
Chinese (zh)
Other versions
CN110098947A (en
Inventor
韩霆军
郑智宏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201810097147.5A priority Critical patent/CN110098947B/en
Publication of CN110098947A publication Critical patent/CN110098947A/en
Application granted granted Critical
Publication of CN110098947B publication Critical patent/CN110098947B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Abstract

The application deployment method, device and system are used for enabling an application server to deploy applications on MEC network element equipment as required, and reducing the cost and complexity of application deployment. The method in the embodiment of the application comprises the following steps: the edge gateway equipment receives a service request from the terminal equipment, wherein the service request comprises a service address; the edge gateway equipment performs header enhancement processing on the service request to obtain header enhancement information, wherein the header enhancement information comprises a mobile edge computing MEC position identifier, and the MEC position identifier is used for identifying the network position of MEC network element equipment corresponding to the edge gateway equipment; the edge gateway device sends the header enhancement information to the application server corresponding to the service address, so that the application server can determine that the MEC network element device corresponding to the MEC position identifier needs to deploy the application according to the header enhancement information.

Description

Application deployment method, device and system
Technical Field
The present application relates to the field of communications, and in particular, to a method, device, and system for deploying an application.
Background
Currently, an application service provider generally deploys an application server in The Internet (Internet), where a service may specifically be an Internet application service (Over The Top, OTT) service, as shown in fig. 1, a User Equipment (UE) performs a service data interaction process with The application server, The UE accesses a Mobile Broadband service (MBB) core network through a base station (eNodeB, eNB) and requests The application server for service data, and The application server issues The service data requested by The UE to The UE through The MBB core network and The eNB. However, the network path between the UE and the application server is long, and there are problems of Internet network capacity, etc., which inevitably causes a delay, and cannot satisfy a service with a high real-time requirement.
An existing method for solving the service delay is as follows: the application service of the service is deployed in an MEC network element close to the UE by using a Mobile Edge Computing (MEC) technology, which is actually to deploy physical equipment provided by the application service provider in an MEC machine room of a Mobile operator, and the application service is pre-configured on the physical equipment. Therefore, the application service aiming at the service on the application server is transferred to the MEC network element from the Internet, the UE only needs to transmit the service data with the nearby MEC network element, the network path is obviously shortened, and the time delay is reduced.
However, the application service is pre-configured on the physical device in the MEC network element, is statically deployed, and is not deployed according to the service requirement; and the physical devices deployed among different application service providers are mutually independent, that is, physical resource sharing cannot be realized among application services of different services, and if a new service needs to be deployed, a new physical device needs to be deployed to an MEC network element, so that rapid deployment cannot be realized. Therefore, the implementation cost of the above method for solving the service delay is high, and the service can not be deployed as required quickly.
Disclosure of Invention
The application deployment method, device and system are used for realizing application of an application server on MEC network element equipment to be deployed as required, and reducing the cost and complexity of application deployment.
A first aspect of the present application provides a deployment method of an application, including: the method comprises the steps that an edge gateway device receives a service request from a terminal device, wherein the service request comprises a service address, the service address is a network address for providing service for an application server, and the network address can be a domain name address or an Internet Protocol (IP) address; the method comprises the steps that an edge gateway device performs header enhancement processing on a service request to obtain header enhancement information, wherein the header enhancement information comprises an MEC position identifier, the MEC position identifier is used for identifying a network position of an MEC network element device corresponding to the edge gateway device, a mobile operator deploys the MEC network element device on a wireless access side in order to provide high-bandwidth and low-delay transmission capability, generally, the MEC network element device sinks to the vicinity of the edge gateway device on a service plane, or the MEC network element device is deployed nearby the edge gateway device on a physical position, for example, a bypass is deployed on the edge gateway device, after the MEC network element device is deployed, an MEC position identifier is distributed to the MEC network element device, and the edge gateway device acquires the MEC position identifier of the corresponding MEC network element device; the edge gateway equipment sends the header enhancement information to the application server corresponding to the service address, so that the application server can determine whether the MEC network element equipment corresponding to the MEC position identifier needs to deploy the application corresponding to the service request according to the header enhancement information, if the application server determines that the MEC network element equipment needs to deploy the application, the application server deploys the application to the MEC network element equipment, so that the terminal equipment can establish a service channel with the application deployed in the MEC network element equipment through the edge gateway equipment, therefore, the application server realizes the deployment of the application on the MEC network element equipment as required, and the cost and the complexity of application deployment are reduced.
With reference to the first aspect of the present application, in a first possible implementation manner, performing, by an edge gateway device, header enhancement processing on a service request to obtain header enhancement information includes: the edge gateway equipment acquires an MEC position identifier of corresponding MEC network element equipment; the edge gateway device adds location header field information to header information of a service request to obtain header enhancement information, where the location header field information includes a location header field identifier and an MEC location identifier, the service request may be based on different protocols, such as HyperText Transfer Protocol (HTTP), secure Transport Layer Protocol (TLS), or Transport Layer Control Protocol (TCP), and the methods for performing header enhancement are not consistent if the different protocols are different, for example, using the HTTP Protocol, a piece of location header field information may be added to the HTTP request, and the location header field information marks the MEC location identifier of the HTTP request; the encrypted TLS Protocol is used for transmission, and the MEC position identification can be marked through an Application-Layer Protocol Negotiation (ALPN) field extension; and transmitting by using a TCP protocol, wherein the MEC position identification is carried in the TCP connection request extension, so that the header enhancement processing of the service request is realized, and the header enhancement information with the MEC position identification is obtained.
With reference to the first aspect of the present application, in a second possible implementation manner, after the edge gateway device sends the header enhancement information to the application server corresponding to the service address, the method further includes: after the MEC network element device deploys an application corresponding to a service request, the MEC network element device obtains an application IP address according to the position where the application is installed, sends an application public Domain Name and the IP address to a Domain Name System (DNS) proxy server, when the edge gateway device receives a DNS request of a specified public Domain Name sent by a terminal device, the edge gateway device sends the public Domain Name to the DNS proxy server, the DNS proxy server carries out DNS analysis on the public Domain Name to obtain the application IP address, the DNS proxy server feeds the application IP address back to the edge gateway device, the edge gateway device receives the application IP address fed back by the DNS proxy server, the application IP address is used as a DNS response to be fed back to the terminal device, and the terminal device establishes a service channel according to the IP address in the DNS response and the application.
With reference to any one of the first aspect to the second possible implementation manner of the first aspect, in a third possible implementation manner, before the MEC location identifier of the MEC network element device is configured by an Operation Maintenance (OM) function, and the edge gateway device receives a service request from the terminal device, the method further includes: the edge gateway equipment acquires OM information, wherein the OM information comprises an MEC position identifier of MEC network element equipment; the edge gateway device acquires registration information of the application server, wherein the registration information comprises network addresses of services which can be supported by the application server. The MEC location identifier may specifically be a unique identifier representing a network location, or may be a network slice in which the MEC network element device is located, or may be represented by combining the network slice and the network location. The registration information of the application server refers to a network address of a service supported by the application server, and is generally a network address for providing a service.
A second aspect of the present application provides a deployment method of an application, including: the method comprises the steps that an application server receives header enhancement information sent by edge gateway equipment, the header enhancement information is obtained by performing header enhancement processing on a service request by the edge gateway equipment, the header enhancement information comprises an MEC position identifier, and the MEC position identifier is used for identifying the network position of MEC network element equipment corresponding to the edge gateway equipment; when the application server determines that the MEC network element equipment corresponding to the MEC position identifier needs to deploy the application according to the header enhancement information, the application server generates an application deployment request and sends the application deployment request to the MEC network element equipment corresponding to the MEC position identifier, wherein the application deployment request comprises the application identifier which is used for identifying the application, so that the MEC network element equipment completes deployment of the application according to the application deployment request, the terminal equipment can obtain service data through the application in the MEC network element equipment, the service delay is reduced, meanwhile, the application server deploys the application on the MEC network element equipment as required, and the cost and the complexity of application deployment are reduced.
With reference to the second aspect of the present application, in a first possible implementation manner, the at least one piece of header enhancement information is provided, each piece of header enhancement information includes an MEC location identifier, and the determining, by the application server, that the MEC network element device corresponding to the MEC location identifier needs to deploy the application corresponding to the service request includes: the application server obtains at least one MEC position identifier according to the head enhancement information; the application server judges whether the quantity of the MEC position identifications meets a threshold value; if the threshold is met, the application server determines that the MEC network element equipment corresponding to the MEC position identifier needs to deploy the application; and if the threshold value is not met, the application server determines that the MEC network element equipment corresponding to the MEC position identification does not need to deploy the application. The edge gateway device sending the header enhancement information to the application server is not limited to one, and may receive multiple header enhancement information sent by multiple edge gateway devices at the same time, and each edge gateway device may also process service requests for multiple services sent by multiple terminal devices at the same time, the application server, for multiple header enhancement information sent by one edge gateway device, first analyzes the header enhancement information to obtain multiple MEC location identifiers, and determines whether the number of the MEC location identifiers meets a threshold, the threshold is set according to a hot spot service criterion, if the number of the MEC location identifiers exceeds the threshold, it indicates that the service request corresponding to the header enhancement information is a hot spot service, and it is necessary to deploy an application corresponding to the hot spot service to the MEC network element device; if the number of the MEC position identifications does not exceed the threshold value, the fact that the application is not required to be deployed to the MEC network element equipment is indicated, the steps are sequentially carried out on each edge gateway equipment, and the MEC network element equipment which needs to be deployed with the application can be determined.
A third aspect of the present application provides a deployment method of an application, including: the method comprises the steps that an MEC network element device receives an application deployment request sent by an application server, wherein the application deployment request comprises an application identifier, and the application identifier is used for identifying a provided application; and the MEC network element equipment deploys the application corresponding to the application identifier according to the application deployment request. The application deployment request sent by the application server is obtained according to the header enhancement information, the header enhancement information is obtained by performing header enhancement processing on the service request sent by the terminal equipment by the edge gateway equipment, the header enhancement information comprises an MEC position identifier of the MEC network element equipment, if the application server determines that the MEC network element equipment needs to deploy the application corresponding to the service request, the application server sends the application deployment request to the MEC network element equipment, and the MEC network element equipment implements deployment of the application corresponding to the service request according to the application deployment request, so that the terminal equipment can establish a service channel with the application deployed in the MEC network element equipment through the edge gateway equipment, and therefore, the application server implements deployment on the MEC network element equipment as required, and the cost and complexity of application deployment are reduced.
With reference to the third aspect of the present application, in a first possible implementation manner, the application deployment request further includes a common domain name and an application storage address, where the common domain name is a network address for providing a service for the application server, the application storage address is a storage address in a mirror file library of the application server, and the application corresponding to the application identifier deployed by the MEC network element device according to the application deployment request includes: the MEC network element equipment obtains an application identifier, a public domain name and an application storage address according to the application deployment request; the MEC network element equipment obtains an application image file of an application corresponding to the application identifier from an image file library of the application server according to the application storage address; the MEC network element equipment installs the application according to the application mirror image file; when the application is started, the MEC network element equipment obtains the IP address of the application according to the position where the application is installed, and sends the public domain name and the corresponding relation of the IP address to the DNS proxy server, so that when the terminal equipment requests the service of the public domain name, the DNS proxy server can feed the IP address of the application back to the terminal equipment through DNS analysis, and the service channel is established between the terminal equipment and the application instead of between the terminal equipment and the application server.
A fourth aspect of the present application provides an edge gateway device, including: the receiving module is used for receiving a service request sent by the terminal equipment, wherein the service request comprises a service address, the service address is a network address for providing services for the application server, and the network address can be a domain name address or an IP address; a header enhancement module, configured to perform header enhancement processing on a service request to obtain header enhancement information, where the header enhancement information includes a mobile edge computing MEC location identifier, the MEC location identifier is used to identify a network location of an MEC network element device corresponding to an edge gateway device, and a mobile operator deploys the MEC network element device on a wireless access side in order to provide high-bandwidth and low-delay transmission capability, and generally sinks near the edge gateway device on a service plane, which may be a physical location deployed nearby the edge gateway device, such as a bypass deployed on the edge gateway device, and after the MEC network element device is deployed, allocates an MEC location identifier for the MEC network element device, and the header enhancement module obtains the MEC location identifier of the corresponding MEC network element device; the sending module is used for sending the header enhancement information to the application server corresponding to the service address, so that the application server determines whether the MEC network element equipment corresponding to the MEC position identifier needs to deploy the application corresponding to the service request according to the header enhancement information, if the application server determines that the MEC network element equipment needs to deploy the application, the application server deploys the application to the MEC network element equipment, and the terminal equipment can establish a service channel with the application deployed in the MEC network element equipment through the edge gateway equipment, so that the application server can deploy the application on the MEC network element equipment as required, and the cost and complexity of application deployment are reduced.
With reference to the fourth aspect of the present application, in a first possible implementation manner, the header enhancement module is specifically configured to obtain an MEC location identifier of a corresponding MEC network element device; and the header enhancement module is further used for adding position header field information in the header information of the service request to obtain the header enhancement information, wherein the position header field information comprises a position header field identifier and an MEC position identifier. The service request may be based on different protocols, such as HTTP, TLS, or TCP, and the methods for performing header enhancement by the different protocols are not consistent, for example, using the HTTP protocol, a location header field information may be added to the HTTP request, and the location header field information marks the MEC location identifier of the HTTP request; the encrypted TLS protocol is used for transmission, and the MEC position identification can be marked through ALPN field extension; and transmitting by using a TCP protocol, wherein the MEC position identification is carried in the TCP connection request extension, so that the header enhancement processing of the service request is realized, and the header enhancement information with the MEC position identification is obtained.
With reference to the fourth aspect of the present application, in a second possible implementation manner, the receiving module is further configured to receive, after the MEC network element device deploys an application corresponding to the service request, a DNS request that specifies a public domain name and is sent by the terminal device, where the DNS request includes the public domain name, and the public domain name is a domain name address used for providing a service by the server; the sending module is also used for sending the public domain name to the DNS proxy server so that the DNS proxy server carries out DNS analysis on the public domain name to obtain an application IP address; the receiving module is also used for receiving the IP address of the application fed back by the DNS proxy server; and the sending module is further used for feeding back the IP address of the application to the terminal equipment as a DNS response, so that the terminal equipment establishes a service channel with the application according to the DNS response. The application server deploys an application on the MEC network element equipment, after the application is started, because a network address of a service processed by the application server is a public domain name, when the service is transferred to the application of the MEC network element equipment, when a receiving module receives a DNS request of a public domain name designated by the terminal equipment, an IP address obtained after DNS analysis of the public domain name needs to be obtained from a DNS proxy server, and the IP address is fed back to the terminal equipment as a DNS response, so that the terminal equipment and the application on the MEC network element equipment establish a service channel.
In combination with any one of the fourth aspect to the second possible implementation manner of the fourth aspect of the present application, in a third possible implementation manner, the receiving module is further configured to obtain OM information, where the OM information includes an MEC location identifier of an MEC network element device; the receiving module is further configured to obtain registration information of the application server, where the registration information includes a network address where the application server provides a service. The MEC location identifier may be a unique representation of a network location, may be a network slice in which the MEC network element device is located, or may be a representation of a combination of a network slice and a network location. The registration information of the application server refers to a network address of a service provided by the application server, and is generally a network address for providing a service.
A fifth aspect of the present application provides an application server, comprising: the receiving module is used for receiving header enhancement information sent by the edge gateway equipment, the header enhancement information is obtained by performing header enhancement processing on a service request by the edge gateway equipment, the service address is a network address used for providing services by a server, the header enhancement information comprises an MEC position identifier, and the MEC position identifier is used for identifying the network position of MEC network element equipment corresponding to the edge gateway equipment; the processing module is used for determining an application which needs to be deployed by the MEC network element equipment and corresponds to the MEC position identifier according to the header enhancement information, and generating an application deployment request, wherein the application deployment request comprises an application identifier, and the application identifier is used for identifying the application; the sending module is used for sending the application deployment request to the MEC network element equipment corresponding to the MEC position identifier, so that the MEC network element equipment completes the deployment of the application according to the application deployment request, the terminal equipment can acquire service data through the application in the MEC network element equipment, the time delay of the service is reduced, the application server can deploy the application on the MEC network element equipment according to the requirement, and the cost and the complexity of the application deployment are reduced.
With reference to the fifth aspect of the present application, in a first possible implementation manner, at least one piece of header enhancement information is included, each piece of header enhancement information includes an MEC location identifier, and the processing module is further configured to obtain at least one MEC location identifier according to the header enhancement information; the processing module is further used for judging whether the quantity of the MEC position identifications meets a threshold value; the processing module is further configured to determine that the MEC network element device corresponding to the MEC location identifier needs to deploy an application when the number of the MEC location identifiers meets a threshold; and the processing module is further configured to determine that the MEC network element device corresponding to the MEC location identifier does not need to deploy an application when the number of the MEC location identifiers does not satisfy the threshold. The edge gateway device sending the header enhancement information to the application server is not limited to one, and may receive the header enhancement information sent by multiple edge gateway devices at the same time, and each MEC network element device may also process service requests for multiple services sent by multiple terminal devices at the same time, the processing module, for multiple header enhancement information sent by one edge gateway device, first analyzes multiple header enhancement information to obtain multiple MEC location identifiers, and determines whether the number of MEC location identifiers meets a threshold, the threshold is set according to a hot spot service criterion, if the number of MEC location identifiers exceeds the threshold, the service of the service request corresponding to the header enhancement information is a hot spot service, and the application corresponding to the hot spot service needs to be deployed to the MEC network element device; if the number of the MEC location identifiers does not exceed the threshold, it indicates that the application does not need to be deployed to the MEC network element device, and the above steps are sequentially performed for each edge gateway device, so that the MEC network element device in which the application needs to be deployed can be determined.
A sixth aspect of the present application provides an MEC network element device, including: the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an application deployment request sent by an application server, the application deployment request comprises an application identifier, and the application identifier is used for identifying an application; and the application deployment module is used for deploying the application corresponding to the application identifier according to the application deployment request. The application deployment request sent by the application server is obtained according to the header enhancement information, the header enhancement information is obtained by performing header enhancement processing on the service request sent by the terminal equipment by the edge gateway equipment, the header enhancement information comprises an MEC position identifier of the MEC network element equipment, if the application server determines that the MEC network element equipment needs to deploy the application corresponding to the service request, the application server sends the application deployment request to the MEC network element equipment, and the MEC network element equipment implements deployment of the application corresponding to the service request according to the application deployment request, so that the terminal equipment can establish a service channel with the application deployed in the MEC network element equipment through the edge gateway equipment, and therefore, the application server implements deployment on the MEC network element equipment as required, and the cost and complexity of application deployment are reduced.
With reference to the sixth aspect of the present application, in a first possible implementation manner, the application deployment request further includes a public domain name and an application storage address, where the public domain name provides a network address of a service for the application server, the application storage address is a storage address in a mirror image file library of the application server, and the application deployment module is specifically configured to obtain the application identifier, the public domain name, and the application storage address according to the application deployment request; the application deployment module is also used for obtaining an application image file of the application corresponding to the application identifier from an image file library of the application server according to the application storage address; the application deployment module is also used for installing the application according to the application image file; the application deployment module is further used for obtaining an application IP address according to the position of the installed application when the application is started, and sending the public domain name and the corresponding relation of the IP address to the DNS proxy server, so that when the terminal equipment requests the application service of the public domain name, the DNS proxy server can feed the application IP address back to the terminal equipment through DNS analysis, and the service channel is established between the terminal equipment and the application, but not between the terminal equipment and the application server.
A seventh aspect of the present application provides an edge gateway device, including: a transceiver and at least one processor, the transceiver and the at least one processor being interconnected by a line, and the transceiver being configured to perform an operation of information transceiving on the edge gateway device side in the first aspect or any optional implementation manner of the first aspect; the at least one processor performs information processing or control operations performed at the edge gateway device side in the first aspect or any optional implementation manner of the first aspect.
With reference to the seventh aspect of the present application, in a possible implementation manner, the MEC network element device further includes: a memory having instructions stored therein for execution by the at least one processor; the memory is interconnected with the transceiver and the at least one processor by wires.
An eighth aspect of the present application provides an application server, including: a transceiver and at least one processor, the transceiver and the at least one processor being interconnected by a line, the transceiver being configured to perform an operation of transceiving information on the application server side in the second aspect or any optional implementation manner of the second aspect; the at least one processor performs the information processing or control operations performed at the application server side in the second aspect or the first possible implementation manner of the second aspect.
With reference to the eighth aspect of the present application, in a possible implementation manner, the application server further includes: a memory having instructions stored therein for execution by the at least one processor; the memory is interconnected with the transceiver and the at least one processor by wires.
A ninth aspect of the present application provides an MEC network element device, including: a transceiver and at least one processor, where the transceiver and the at least one processor are interconnected by a line, and the transceiver is configured to perform an operation of transceiving information on the MEC network element device side in the third aspect or the first possible implementation manner of the third aspect.
With reference to the ninth aspect of the present application, in a possible implementation manner, the MEC network element device further includes: a memory having instructions stored therein for execution by the at least one processor; the memory is interconnected with the transceiver and the at least one processor by wires.
A tenth aspect of the present application provides a deployment system of an application, including: the edge gateway equipment and the MEC network element equipment corresponding to the edge gateway equipment; the edge gateway device performs information processing or control operations in the first aspect or any optional implementation manner of the first aspect; the MEC network element device performs information processing or control operations in the third aspect or the first possible implementation manner of the third aspect.
An eleventh aspect of the present application provides a chip system, comprising: the edge gateway device is applied to an edge gateway device, the chip system comprises at least one processor and an interface circuit, and the transceiver and the at least one processor are interconnected through a line; the processor performs the operations of the edge gateway device in the first aspect or any optional implementation manner of the first aspect.
A twelfth aspect of the present application provides a chip system, comprising: the chip system comprises at least one processor and an interface circuit, the transceiver and the at least one processor are interconnected through a line, and the processor executes the operation of the application server in the second aspect or the first possible implementation manner of the second aspect.
A thirteenth aspect of the present application provides a chip system, comprising: the method is applied to the MEC network element device, the chip system includes at least one processor and an interface circuit, the transceiver and the at least one processor are interconnected through a line, and the processor executes the operation of the MEC network element device in the third aspect or the first possible implementation manner of the third aspect.
A fourteenth aspect of the present application provides a computer-readable storage medium, which is applied to an edge gateway device, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer is caused to perform the operations of the edge gateway device in the first aspect or any optional implementation manner of the first aspect.
A fifteenth aspect of the present application provides a computer-readable storage medium, which is applied to an application server, and has stored therein instructions, which, when executed on a computer, cause the computer to perform the operations of the application server in the second aspect or the first possible implementation manner of the second aspect.
A sixteenth aspect of the present application provides a computer-readable storage medium, which is applied to an MEC network element device, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer is caused to perform the operations of the MEC network element device in the third aspect or the first possible implementation manner of the third aspect.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments and the prior art will be briefly described below.
Fig. 1 is a schematic diagram of a conventional UE performing service data interaction with an application server;
fig. 2 is a schematic architecture diagram of a 5G communication system network provided in the present application;
fig. 3 is a schematic signaling interaction diagram of an application deployment method provided in the present application;
fig. 4 is a schematic flowchart of an application server deploying an application to MEC network element equipment according to the present application;
FIG. 5 is a schematic diagram illustrating interaction between functional modules of the devices provided in the present application;
FIG. 6 is a schematic diagram illustrating interaction between functional modules of the devices provided in the present application;
fig. 7 is a schematic structural diagram of an embodiment of an edge gateway device provided in the present application;
FIG. 8 is a schematic structural diagram of an application server according to an embodiment of the present disclosure;
fig. 9 is a schematic structural diagram of an embodiment of an MEC network element device provided in the present application;
FIG. 10 is a schematic structural diagram illustrating an embodiment of a deployment system for an application provided herein;
fig. 11 is a schematic structural diagram of another embodiment of an edge gateway device provided in the present application;
fig. 12 is a schematic structural diagram of an embodiment of a chip system provided in the present application.
Detailed Description
The application deployment method, device and system are used for realizing application deployment on MEC network element equipment by a server according to needs, and reducing the cost and complexity of application deployment.
The terms "upstream" and "downstream" appearing in the present application are used in some scenarios to describe the direction of data/information transmission, for example, the "upstream" direction is the direction of data/information transmission from the terminal device to the network side, the "downstream" direction is the direction of data/information transmission from the network side device to the terminal device, the "upstream" and "downstream" are used only to describe the direction, and the specific devices from which the data/information transmission starts and ends are not limited.
The term "and/or" appearing in the present application may be an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this application generally indicates that the former and latter related objects are in an "or" relationship.
Various objects such as various messages/information/devices/network elements/systems/devices/actions/operations/flows/concepts may be named in the present application, but these specific names do not constitute limitations on related objects, and the named names may vary with factors such as scenes, contexts or usage habits, and understanding of technical meaning of related objects should be mainly determined from functions and technical effects embodied/executed in the technical solutions.
The terms "first," "second," and the like in the description and in the claims of the present application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Moreover, the terms "comprises," "comprising," and any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not expressly listed or inherent to such process, method, article, or apparatus. The naming or numbering of the steps appearing in the present application does not mean that the steps in the method flow have to be executed in the chronological/logical order indicated by the naming or numbering, and the named or numbered process steps may be executed in a modified order depending on the technical purpose to be achieved, as long as the same or similar technical effects are achieved. The division of the modules presented in this application is a logical division, and in practical applications, there may be another division, for example, multiple modules may be combined or integrated into another system, or some features may be omitted, or not executed, and in addition, the shown or discussed coupling or direct coupling or communication connection between each other may be through some interfaces, and the indirect coupling or communication connection between the modules may be in an electrical or other similar form, which is not limited in this application. The modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in a plurality of circuit modules, and some or all of the modules may be selected according to actual needs to achieve the purpose of the present disclosure.
First, a system architecture or scenario in which the present application is applied will be briefly described.
The application is applied to a wireless communication network system, as shown in fig. 2, an application server is deployed in the internet for providing services, and the application server is connected with the mobile network capability, can deploy applications, manage the image files of the applications, and realize the basic services of the application server on the internet; in the User Plane of the 5G Network, a main User Plane Function (a-UPF) is responsible for mastering the global situation and mainly provides an internet exit of mobile Data, and the UPF also replaces a Service Gateway (SGW) and a Public Data Network Gateway (PGW) which execute routing and forwarding functions in the 4G Network; a terminal device (UE) provides a wireless internet service to a User, and includes a fixed terminal device such as a Personal Computer (PC), an IP phone, and a facsimile machine, and a mobile terminal device such as a mobile phone and a tablet Computer; an access network device (eNodeB) is a control device providing wireless access, and may specifically be a base station; a Local User Plane Function (L-UPF) mainly provides a service data distribution service, and ensures that a specific service can be directly distributed to MEC network element devices, which may also be referred to as Local Gateway (RGW) or edge Gateway; the MEC network element equipment can deploy application so as to locally process the service; a Service Management Function (SMF) mainly provides a related control Function in a wireless network; the Network Exposure Function (NEF) is specifically an Application Programming Interface (API) gateway, the NEF of each Network element provides an open capability to the outside, an internet service provider can call an operator mobile Network capability through an NEF entry, the NEF may include an edge NEF and a center NEF, and sensing and distinguishing are not required in actual Application.
The following describes a deployment method applied to the above system architecture, which is provided by the present application, by an embodiment.
Referring to fig. 3, an embodiment of the present application provides a method for deploying an application, including:
301. the edge gateway equipment receives a service request from the terminal equipment;
in this embodiment, in order to provide a transmission capability with high bandwidth and low delay, a mobile operator deploys an MEC network element device on a wireless Access side, generally sinks near an edge gateway device in a service plane, and may be deployed near the edge gateway device in a physical location, for example, deployed by-pass on the edge gateway device, after the MEC network element device is deployed, the mobile operator allocates an MEC location identifier to the MEC network element device, where the MEC location identifier is used to identify a network location of the MEC location identifier, and the MEC location identifier may set a unique number for each MEC network element device, may be a fragment identifier of a network fragment in a 5G network, may also be a combination of a fragment identifier of a network fragment and the unique number, or may also correspond to a conventional Access Point Name (Access Point Name, APN). The same MEC location identity is not restricted to correspond to one MEC network element device. The application service provider and the network operator have signed a contract, that is, the MEC network element device knows the service address of the service provided by the application server, and the service address may be a domain name or an IP address, but considering the complexity of the IP address, the service address used by the user on the terminal device usually uses a domain name, such as www.aidou.com. When a user needs to use the terminal equipment to perform service, the user inputs a service request of the service at the terminal equipment, the service request comprises a service address, the service address provides a network address of the service for the application server, and the edge gateway equipment receives the service request reported by the terminal equipment.
302. The edge gateway equipment performs header enhancement processing on the service request to obtain header enhancement information;
in this embodiment, as the MEC network element device is pre-deployed, the MEC network element device has assigned an MEC location identifier, the MEC location identifier indicates a network location of the MEC network element device, and the edge gateway device knows the MEC location identifier of the corresponding MEC network element device, and performs header enhancement processing on the service request, so that the header enhancement information includes the MEC location identifier.
303. The edge gateway equipment sends the header enhancement information to an application server corresponding to the service address, and the application server receives the header enhancement information sent by the edge gateway equipment;
in this embodiment, since the application service provider and the network operator have signed a contract, that is, the MEC network element device knows the service address of the service provided by the application service provider, the MEC network element device may determine the corresponding application server from the service address in the service request, the MEC network element device sends the header enhancement information to the application server corresponding to the service address, and the application server receives the header enhancement information sent by the MEC network element device.
304. The application server determines that the MEC network element equipment corresponding to the MEC position identification needs to deploy the application according to the header enhancement information;
in this embodiment, after the application server receives the header enhancement information, since the header enhancement information is obtained by the edge gateway device according to the service request processing of the terminal device and includes the MEC location identifier of the MEC gateway device corresponding to the edge gateway device, the application server can determine, according to the header enhancement information, that the MEC network element device corresponding to the MEC location identifier needs to deploy the application corresponding to the service request sent by the terminal device.
305. The method comprises the steps that an application server sends an application deployment request to MEC network element equipment corresponding to an MEC position identifier, and the MEC network element equipment receives the application deployment request sent by the application server;
in this embodiment, after determining that the MEC network element device corresponding to the MEC location identifier needs to deploy the application, the application server may generate an application deployment request according to a pre-deployed program, or an application operator inputs the application deployment request to the application server according to a situation that the application needs to be deployed, the application server sends the application deployment request to the MEC network element device corresponding to the MEC location identifier, the MEC network element device receives the application deployment request sent by the application server, the application deployment request includes the application identifier, and the application identifier is used to identify the application.
306. And the MEC network element equipment deploys the application corresponding to the application identifier according to the application deployment request.
In this embodiment, after receiving the application deployment request, the MEC network element device may determine, according to the application identifier included in the application deployment request, the application to be deployed, and may obtain the installer of the application through a network or a database, thereby completing the deployment of the application. After the application is deployed in the MEC network element device, the terminal device only needs to establish a service channel with the application in the MEC network element device, and does not need to acquire service data from an application server deployed in the internet.
In the embodiment of the application, when the edge gateway device receives a service request sent by the terminal device, header enhancement processing is adopted, the MEC position identifier of the MEC network element device is carried in header enhancement information, the MEC network element device sends the header enhancement information to the application server, the application server can determine the MEC network element device needing to deploy the application according to the header enhancement information, so that the application deployment request is sent to the MEC network element device, the MEC network element device completes deployment of the application according to the application deployment request, the terminal device can obtain service data through the application in the MEC network element device, the time delay of the service is reduced, the application server can deploy the application on the MEC network element device as required, and the cost and complexity of application deployment are reduced.
In the embodiment shown in fig. 3, a service address in the service request is a network address of a service provided by an application server, the edge gateway device can determine a corresponding application server according to the service address, how the edge gateway device determines a correspondence between the service address and the application server, and how the MEC location identifier of the MEC network element device connected to the edge gateway device is specifically obtained, which is described below with an embodiment.
Optionally, in some embodiments of the present application, before the edge gateway device receives the service request from the terminal device, the method further includes:
the edge gateway equipment acquires OM information, wherein the OM information comprises an MEC position identifier of MEC network element equipment;
the edge gateway equipment acquires the registration information of the application server, wherein the registration information comprises a network address of a service provided by the application server.
In this embodiment, a mobile operator completes deployment of MEC network element devices in advance, a wireless communication connection may be established between an edge gateway device and an MEC network element device, and one MEC network element device corresponds to at least one edge gateway device, an OM function is management of operation and maintenance of the network device, an OM may allocate an MEC location identifier for the MEC network element device, the MEC location identifier is used to identify a network location of the MEC location identifier, the MEC location identifier may set a unique number for each MEC network element device, or may be a fragment identifier of one network fragment in a 5G network, or may be a combination of a fragment identifier of a network fragment and a unique number, or may correspond to an APN, and so on. The edge gateway device obtains OM information, where the OM information includes an MEC location identifier of the MEC network element device, and then the edge gateway device knows the MEC location identifier of the MEC network element device, and the registration information of the application server includes a network address where the application server provides a service, and then the edge gateway device knows a service address where the application server can provide the service.
In the embodiment shown in fig. 3, the service request may be based on different protocols, such as HTTP, TLS, or TCP, and the header enhancement methods of the different protocols are not consistent, for example, using the HTTP protocol, a location header field may be added to the HTTP request, and the location header field marks the MEC location identifier of the HTTP request; the encrypted TLS protocol is used for transmission, and the MEC position identification can be marked through ALPN field extension; using TCP protocol transmission, the MEC location identifier is carried in the TCP connection request extension, thereby implementing the header enhancement processing of the service request, and obtaining the header enhancement information with the MEC location identifier, optionally, in some embodiments of the present application, the MEC network element device performs the header enhancement processing on the service request, and obtains the header enhancement information, including:
the edge gateway equipment acquires an MEC position identifier of corresponding MEC network element equipment;
the edge gateway equipment adds position header field information in the header information of the service request to obtain header enhancement information, wherein the position header field information comprises position header field identification and MEC position identification.
In this embodiment of the present application, an edge gateway device may obtain, through OM information, an MEC location identifier of a corresponding MEC network element device, where a service request takes an HTTP request as an example, and the HTTP request is composed of 3 parts: request method Uniform Resource Identifier (URI) protocol/version, HTTP header information, and request body. The edge gateway device adds location header field information, such as x-mec-id: the method comprises the steps that abcdefg, position header field information comprises a position header field identifier (x-MEC-id) and an MEC position identifier (abcdefg), and header enhancement information is obtained; if the service request is transmitted by using an encrypted TLS protocol, a position information field can be inserted into the ALPN field, the position information field is equivalent to position header field information, and the position information field comprises a position information identifier and an MEC position identifier; in addition, the header enhancement processing is realized by using TCP protocol transmission and using the expansion capability of TCP and adding an expansion field in the header information to insert the position of the header field information. It should be noted that, in addition to the above-described examples of the head strengthening process, other specific embodiments are possible, and no particular limitation is imposed.
After obtaining the header enhancement information in the above embodiment, the application server may determine that the application needs to be deployed in the MEC network element device according to the header enhancement information, so as to generate an application deployment request, and issue the application deployment request to the MEC network element device, so that the MEC network element device deploys the application according to the application deployment request, which is specifically described with an embodiment shown in fig. 4 below, and includes:
401. the application server determines an application to be deployed of the MEC network element equipment corresponding to the MEC position identification according to the header enhancement information;
in this embodiment, the edge gateway device that sends the header enhancement information to the application server is not limited to one, and may receive multiple header enhancement information sent by multiple edge gateway devices at the same time, and each edge gateway device may also process multiple service requests of multiple terminal devices at the same time, so that the deployment of the application may be determined according to the determination criterion of the hot spot service, and may also be determined according to the user class corresponding to the service request, which is specifically as follows:
(1) the application server firstly analyzes a plurality of pieces of header enhancement information of the edge gateway equipment to obtain a plurality of MEC position identifications aiming at the edge gateway equipment, judges whether the number of the MEC position identifications meets a threshold value, the threshold value is set according to hot spot service criteria, if the number of the MEC position identifications exceeds the threshold value, the service of a service request corresponding to the header enhancement information is represented as a hot spot service, and then the application corresponding to the hot spot service needs to be deployed to MEC network element equipment; if the number of the MEC position identifications does not exceed the threshold value, the fact that the application is not required to be deployed to the MEC network element equipment is indicated, the steps are sequentially carried out on each edge gateway equipment, and then the MEC network element equipment which is required to be deployed with the application can be determined;
(2) the method comprises the steps that a service request of terminal equipment also comprises user information, an application server aims at an MEC network element equipment, first, head enhancement information corresponding to the MEC network element equipment is analyzed to obtain an MEC position identifier, the application server judges whether the user information meets a preset user grade, the user grade is a standard for carrying out grade division on different users by an application service provider, the preset user grade is a key factor for judging whether the application server needs to provide service priority treatment, and if the grade of the user corresponding to the user information meets the preset user grade, the application server determines that the MEC network element equipment corresponding to the MEC position identifier needs to deploy application; and if the user level does not meet the preset user level, the application server determines that the MEC network element equipment corresponding to the MEC position identifier does not need to deploy the application.
It should be noted that, besides the application deployment manners based on the hotspot service and the user level described in (1) and (2), other application deployment manners may also be provided, which are not specifically described herein.
402. The application server generates an application deployment request and sends the application deployment request to the MEC network element equipment;
in this embodiment, after determining that the MEC network element device corresponding to the MEC location identifier needs to deploy an application, the application server may generate an application deployment request according to a pre-deployed program, or an application operator may deploy the application according to a situation that the application needs to be deployed, input the application deployment request to the application server, where the application server sends the application deployment request to the MEC network element device corresponding to the MEC location identifier, the MEC network element device receives the application deployment request sent by the application server, where the application deployment request includes an application identifier for identifying the application, and in addition, the application deployment request further includes a common domain name, where the common domain name is a network address for the application server to process a service, that is, a domain name for the application server to provide the service, and since the operator network is not convenient for exposing an internal network outside based on security reasons, the application mirror image file is obtained from a mirror image file, therefore, the application deployment request also comprises an application storage address, and the application storage address is a storage address in the mirror image file library of the application server.
403. The MEC network element equipment obtains an application identifier, a public domain name and an application storage address according to the application deployment request;
in this embodiment, after receiving an application deployment request sent by an application server, an MEC network element device parses the application deployment request to obtain an application identifier, a public domain name, and an application storage address.
404. The MEC network element equipment obtains an application image file corresponding to the application identifier from an image file library of the application server according to the application storage address;
in this embodiment, because the application image file is stored in the image file library of the application server, the MEC network element device extracts the application image file of the application corresponding to the application identifier from the image file library of the application server according to the application storage address.
405. The MEC network element equipment installs the application according to the application mirror image file;
in this embodiment, after acquiring the application image file, the MEC network element device installs the application image file in a Platform-as-a-Service (PaaS) module of the MEC network element device, where PaaS actually refers to submitting a Platform developed by software as a Service to a user in a saas (software as a Service) mode. After the application image file is installed in the PaaS module of the MEC network element equipment, the service provided by the application server is transferred to the MEC network element equipment.
406. The MEC network element equipment obtains an applied IP address and sends the public domain name and the IP address to a DNS;
in this embodiment, after the MEC network element device installs the application, when the application is started, in order to enable the application installed by the MEC network element device to provide the local service, instead of going to the application server for processing the service, the IP address of the application needs to be provided, and the IP address of the application specifically installed on the physical or virtual module of the MEC network element apparatus is the IP address of the application, so that the MEC network element apparatus can obtain the IP address of the application, and sends the public domain name and IP address to the DNS, it may be a DNS proxy server that provides DNS services, a type of server used to provide DNS resolution functions, i.e. resolving the domain name to an IP address, the DNS proxy may be integrated in the MEC network element device, or may be integrated in the edge gateway device, however, in order to reduce the processing load of the MEC network element device and the edge gateway device, the DNS proxy server generally exists as a separate server in the network.
407. The edge gateway equipment receives a DNS request from terminal equipment;
in this embodiment, after the above steps are completed, when the terminal device needs to acquire service data of a service provided by a specified public domain name, the edge gateway device receives a DNS request from the terminal device, where the DNS request specifies the public domain name, and the public domain name is a domain name address providing the service.
408. The edge gateway device acquires the IP address corresponding to the public domain name and sends the IP address corresponding to the public domain name to the terminal device.
In this embodiment, the edge gateway device sends the public domain name to the DNS proxy server, and since the DNS proxy server has previously obtained the public domain name and the IP address sent by the MEC network element device, the DNS proxy server performs DNS resolution on the public domain name to obtain the IP address, the DNS proxy server feeds back the IP address to the edge gateway device, the edge gateway device receives the IP address of the application fed back by the DNS proxy server, and feeds back the applied IP address to the terminal device as a DNS response, so that the terminal device directly accesses the application according to the IP address in the DNS response, and can establish a service channel with the application of the MEC network element device.
In the embodiment of the application, how the application server is deployed as required is specifically described, and after the MEC network element device deploys the application, a public domain name and an IP address of an application providing service are published, so that when the edge gateway device receives a DNS request of a specified public domain name sent by the terminal device, the edge gateway device can perform DNS resolution on the DNS proxy server and feed back the IP address to the terminal device as a DNS response, and then the terminal device can access the application through the IP address, thereby establishing a service channel, realizing that the application server provides the service and transfers the service to the application of the MEC network element device, obviously shortening a data transmission path of the service, and reducing time delay.
In the above embodiment, the edge gateway device, the MEC network element device, and the application server are described as an integral device, but the edge gateway device, the MEC network element device, and the application server actually consist of a plurality of modular functions and NEFs in a network, and as shown in fig. 5 and fig. 6, a detailed description is made on a deployment method of an application, specifically as follows:
501. taking an OTT service as a live broadcasting of a concert as an example, an application server is an OTT server, the OTT server signs a contract with a network operator, an OTT control end of the OTT server registers a domain name www.aidou.com to a central NEF, the OTT control end can call an operator network providing interface (such as a Restful interface) to notify an MEC network element device to associate a service flow of the OTT service with a specified domain name with an MEC location identifier of the MEC network element device, and an example of a registration message is as follows:
PUT/api/v1/position-markottid＝1122334&domain＝www.aidou.com HTTP/1.1
Host:10086.com
User-Agent:Go-http-client/1.1
Transfer-Encoding:chunked
Content-Type:application/json
Accept-Encoding:gzip
the meaning of the registration message is: the OTT server with the number of 1122334 requests the operator network to perform location identification on the domain name www.aidou.com, that is, www.aidou.com is registered with the MEC network element device;
502. an operator completes MEC network element equipment deployment at the rear end of the RGW, and allocates a unique MEC position identifier for the MEC network element equipment (namely edge NEF), wherein the MEC position identifier can be DNAI specifically;
503. after being started, the edge NEF deployed in the MEC network element equipment registers to the center NEF, and the center NEF returns domain names www.aidou.com registered by all signed OTT servers to be acquired by the edge NEF;
504. the edge NEF in the MEC network element equipment issues the MEC position identification and the registered domain name to a header enhancement function;
505. the head enhanced function requires RGW to transfer the service flow of the appointed domain name to the head enhanced function through an internal interface, and the head enhanced function is that when a mobile operator accesses according to different geographic positions of UE, an MEC position mark is added to a request sent to an OTT server to generate head enhanced information;
506. the UE watches the live broadcasting of the concert through www.aidou.com, the UE accesses at different geographical positions, and the OTT server receives the head enhancement information processed by the head enhancement function of the operator;
507. the OTT server extracts the header enhancement information to complete service hotspot analysis and determines the position identification of the MEC corresponding to the service hotspot, the OTT server can deploy live broadcast service according to different strategies, the hotspot is one of the methods, the same MEC position identification is added by the header enhancement function through the request of the same RGW UE, and the OTT server can easily acquire the MEC network element equipment needing to deploy the live broadcast service; in addition, the OTT server can also be deployed according to other policies, such as a super fan policy, a user of the UE is identified as a super fan by www.aidou.com, the OTT server provides a click speed-up function for the user, and as long as the UE walks anywhere and clicks the speed-up function, the corresponding MEC network element device can be identified to deploy live broadcast service at the MEC location according to the RGW accessed by the UE;
508. the OTT server requests the central NEF to deploy a specific application at the specified MEC network element equipment, and indicates the public domain name corresponding to the OTT service which needs to be processed by the application. For example, the content of the application deployment request of the OTT server calling the application deployment interface provided by the operator is as follows:
Figure BDA0001565336420000141
Figure BDA0001565336420000151
the application deployment request specifically indicates that the OTT server of 1122334 needs to deploy an application called tvshow at the MEC network element device identified as sz at the MEC location, and the application processes all service data up to www.aidou.com;
509. the central NEF locates to the edge NEF according to the MEC position identification, and forwards the application deployment request to the edge NEF;
510. the edge NEF calls a PaaS (kubernets or MANO) of the MEC Network element device to obtain an application image file from an image file library provided by an OTT server, thereby completing application deployment, the kubernets is a Google open-source container cluster Management System, which provides functions of application deployment, maintenance, extension mechanisms and the like, and a Management and organization domain (MANO) is responsible for managing and organizing Network Function Virtualization Infrastructure (NFVI) resources in a Network, mapping and associating service networks and NFVI resources, and implementing an Operation Support System (OSS) service resource flow.
511. The edge NEF obtains an IP address of an application, meanwhile, the public domain name and the IP address are forwarded to the DNS proxy server, after a subsequent RGW receives a DNS request of the UE for the specified public domain name, the IP address after DNS analysis of the public domain name is obtained from the DNS proxy server, and the RGW feeds the IP address back to the UE as a DNS response, so that the UE can obtain live broadcasting data of the concert from the application on MEC network element equipment near the position of the UE, and the live broadcasting data of the concert does not need to be obtained from an OTT server.
The foregoing embodiment describes an application deployment method, and the following describes MEC network element devices, application servers, and edge gateway devices respectively through a modular device embodiment.
Referring to fig. 7, an embodiment of the present application provides an edge gateway device, including:
a receiving module 701, configured to receive a service request sent from a terminal device, where the service request includes a service address;
a header enhancement module 702, configured to perform header enhancement processing on the service request to obtain header enhancement information, where the header enhancement information includes an MEC location identifier, and the MEC location identifier is used to identify a network location of an MEC network element device corresponding to the edge gateway device;
a sending module 703, configured to send the header enhancement information to an application server corresponding to the service address.
In this embodiment of the application, a receiving module 701 receives a service request sent by a terminal device, a header enhancement module 702 performs header enhancement processing on the service request to obtain header enhancement information, and a sending module 703 sends the header enhancement information to an application server corresponding to a service address, so that the application server determines whether the MEC network element device corresponding to the MEC location identifier needs to deploy an application according to the header enhancement information, and if the application server determines that the MEC network element device needs to deploy an application, the application server deploys the application to the MEC network element device, so that the terminal device can establish a service channel with the application deployed in the MEC network element device through an edge gateway device, and therefore, the application server implements deployment application on the MEC network element device as needed, and the cost and complexity of application deployment are reduced.
Alternatively, as shown in fig. 7, in some embodiments of the present application,
a header enhancing module 702, specifically configured to obtain an MEC location identifier of a corresponding MEC network element device;
the header enhancement module 702 is further configured to add location header field information to the header information of the service request to obtain header enhancement information, where the location header field information includes a location header field identifier and an MEC location identifier.
In the embodiment of the present application, the service request may be based on different protocols, such as HTTP, TLS, or TCP, and the methods for performing header enhancement for different protocols are not consistent, for example, if the HTTP protocol is used, a location header field information may be added to the HTTP request, and the location header field information marks the MEC location identifier of the HTTP request; the encrypted TLS protocol is used for transmission, and the MEC position identification can be marked through ALPN field extension; and transmitting by using a TCP protocol, wherein the MEC position identification is carried in the TCP connection request extension, so that the header enhancement processing of the service request is realized, and the header enhancement information with the MEC position identification is obtained.
Alternatively, as shown in fig. 7, in some embodiments of the present application,
the receiving module 701 is further configured to receive a DNS request from the terminal device after the MEC network element device deploys an application corresponding to the service request, where the DNS request includes a public domain name, and the public domain name provides a domain name address of the service for the application server;
the sending module 703 is further configured to obtain an IP address corresponding to the public domain name, and send the IP address corresponding to the public domain name to the terminal device.
In this embodiment of the application, an application is deployed on MEC network element equipment, after the application is started, since a network address provided by the application server for processing a service is a public domain name, if the service is to be transferred to the application of the MEC network element equipment, when a receiving module 701 receives a DNS request of a terminal equipment specifying the public domain name, an IP address obtained after DNS resolution of the public domain name needs to be obtained from a DNS proxy server, and a sending module 703 feeds back the IP address to the terminal equipment as a DNS response, so that the terminal equipment and the application on the MEC network element equipment perform the service.
Alternatively, as shown in fig. 7, in some embodiments of the present application,
the receiving module 701 is further configured to obtain OM information, where the OM information includes an MEC location identifier of the MEC network element device;
the receiving module 701 is further configured to obtain registration information of the application server, where the registration information includes a network address where the application server provides a service.
In this embodiment of the application, the receiving module 701 obtains OM information, where the OM information includes an MEC location identifier of an MEC network element device, and the MEC location identifier may be a unique network location, or a network slice where the MEC network element device is located, or a combination of the network slice and the network location. The registration information of the application server acquired by the receiving module 701 refers to a network address where the application server provides a service, and is generally a network address used for providing a service.
Referring to fig. 8, an embodiment of the present application provides an application server, including:
a receiving module 801, configured to receive header enhancement information sent from an edge gateway device, where the header enhancement information includes an MEC location identifier, and the MEC location identifier is used to identify a network location of an MEC network element device corresponding to the edge gateway device;
a processing module 802, configured to determine, according to the header enhancement information, that the MEC network element device corresponding to the MEC location identifier needs to deploy an application;
a sending module 803, configured to send an application deployment request to the MEC network element device corresponding to the MEC location identifier, where the application deployment request includes an application identifier, and the application identifier is used to identify an application.
In this embodiment, the receiving module 801 receives header enhancement information sent by an edge gateway device, where the header enhancement information is obtained by performing header enhancement processing on a service request by the edge gateway device, the header enhancement information includes an MEC location identifier, the MEC location identifier is used to identify a network location of an MEC network element device corresponding to the edge gateway device, the processing module 802 determines, according to the header enhancement information, that the MEC network element device corresponding to the MEC location identifier needs to deploy an application, the sending module 803 sends an application deployment request to the MEC network element device corresponding to the MEC location identifier, the MEC network element equipment completes the deployment of the application according to the application deployment request, so that the terminal equipment can acquire service data through the application in the MEC network element equipment, reduce the time delay of the service, the method and the device realize the application deployment of the application server on the MEC network element equipment as required, and reduce the cost and the complexity of the application deployment.
Optionally, as shown in fig. 8, in some embodiments of the present application, there is at least one header enhancement information, each header enhancement information includes an MEC location identifier,
the processing module 802 is further configured to obtain at least one MEC location identifier according to the header enhancement information;
the processing module 802 is further configured to determine whether the number of MEC location identifiers meets a threshold;
the processing module 802 is further configured to determine that, when the number of the MEC location identifiers meets a threshold, the MEC network element device corresponding to the MEC location identifier needs to deploy an application.
In this embodiment of the application, edge gateway devices that send header enhancement information to the receiving module 801 are not limited to one, and may receive multiple pieces of header enhancement information sent by multiple edge gateway devices at the same time, and each MEC network element device may also process service requests for multiple services sent by multiple terminal devices at the same time, the processing module 802, for header enhancement information sent by one edge gateway device, the processing module 802 first parses multiple pieces of header enhancement information to obtain multiple MEC location identifiers, and determines whether the number of MEC location identifiers meets a threshold, the threshold is set according to a hot spot service criterion, if the number of MEC location identifiers exceeds the threshold, it indicates that a service requested by the header enhancement information is a hot spot service, and the processing module 802 needs to deploy an application corresponding to the hot spot service to the MEC network element device; if the number of the MEC location identifiers does not exceed the threshold, it indicates that the application does not need to be deployed to the MEC network element device, and the above steps are sequentially performed for each edge gateway device, so that the MEC network element device to which the application needs to be deployed can be determined.
Referring to fig. 9, an embodiment of the present application provides an MEC network element device, including
A receiving module 901, configured to receive an application deployment request sent by an application server, where the application deployment request includes an application identifier, and the application identifier is used to identify an application;
and the application deployment module 902 is configured to deploy the application corresponding to the application identifier according to the application deployment request.
In the embodiment of the application, the application deployment request sent by the application server is obtained according to the header enhancement information, the header enhancement information is obtained by the edge gateway device performing header enhancement processing on the service request sent by the terminal device, and the header enhancement information includes the MEC position identifier of the MEC network element device, if the application server determines that the MEC network element device needs to deploy the application, the application server sends an application deployment request to the MEC network element device, the receiving module 901 receives the application deployment request sent by the application server, the application deployment module 902 implements deployment of the application according to the application deployment request, so that the terminal device can establish a service channel with an application deployed in the MEC network element device through the edge gateway device, therefore, the application server realizes the application deployment on the MEC network element equipment as required, and reduces the cost and complexity of the application deployment.
Optionally, as shown in fig. 9, in some embodiments of the present application, the application deployment request further includes a public domain name and an application storage address, the public address domain name is a network address for providing a service to the application server, the application storage address is a storage address in a mirror file library of the application server,
the application deployment module 902 is specifically configured to obtain an application identifier, a public domain name, and an application storage address according to the application deployment request;
the application deployment module 902 is further configured to obtain an application image file of the application corresponding to the application identifier from an image file library of the application server according to the application storage address;
the application deployment module 902 is further configured to install an application according to the application image file;
the application deployment module 902 is further configured to obtain an IP address of the application when the application is started, and send the public domain name and the corresponding relationship between the IP addresses to the DNS. In this embodiment of the application, if a service is to be transferred from an application server to an application of an MEC network element device, the application deployment module 902 needs to notify the DNS proxy server of a public domain name and an IP address of the application, so that when the edge network element device receives a service that the terminal device requests to specify the public domain name, the DNS proxy server can perform DNS resolution to obtain the IP address, and the IP address of the application is fed back to the terminal device, thereby implementing that the terminal device establishes a service channel with the application, instead of establishing a service channel with the application server.
Fig. 10 is a schematic diagram of a deployment system of an application provided in an embodiment of the present application. The deployment system 1000 of the application includes an edge gateway device 1001, and an MEC network element device 1002 corresponding to the edge gateway device 1001;
the edge gateway device 1001 performs information processing or control operation on the edge gateway device side in the embodiment of the deployment method of the above application;
the MEC network element device 1002 performs information processing or control operations on the MEC network element device side in the embodiment of the deployment method of the above application.
Fig. 11 is a schematic structural diagram of an edge gateway device 1100 according to an embodiment of the present application. The edge gateway device 1100 includes at least one processor 1110 and a transceiver 1130, and the transceiver 1130 and the at least one processor 1110 are interconnected by wires.
Optionally, as shown in fig. 11, in some embodiments of the present application, the edge gateway device 1100 further includes: a memory 1150; the memory 1150 may include both read-only memory and random-access memory, and provides operating instructions and data to the processor 1110. A portion of the memory 1150 may also include non-volatile random access memory (NVRAM). Memory 1150 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof:
in the embodiment of the present application, by calling an operation instruction stored in the memory 1150 (the operation instruction may be stored in an operating system), a corresponding operation is performed. Processor 1110 controls the operation of MEC network element device 1100, and processor 1110 may also be referred to as a Central Processing Unit (CPU). Memory 1150 may include both read-only memory and random-access memory, and provides instructions and data to processor 1110. A portion of the memory 1150 may also include non-volatile random access memory (NVRAM). In particular implementations, various components of the access network device 1100 are coupled together by a bus system 1120, where the bus system 1120 may include a power bus, a control bus, a status signal bus, and the like, in addition to a data bus. For clarity of illustration, however, the various buses are designated in the figure as bus system 1120.
The methods disclosed in the embodiments of the present application may be implemented in the processor 1110 or implemented by the processor 1110. Processor 1110 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 or instructions in the form of software in the processor 1110. The processor 1110 described above may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, 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 module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 1150, and the processor 1110 reads the information in the memory 1150 and performs the steps of the above method in combination with the hardware thereof.
The application server and edge gateway device may also be understood with reference to fig. 11.
Fig. 12 is a schematic structural diagram of a chip system 1200 according to an embodiment of the present disclosure. The system-on-chip 1200 includes at least one processor 1210 and an interface circuit 1230, the interface circuit 1230 and the at least one processor 1210 being interconnected by a wire. .
Optionally, as shown in fig. 12, in some embodiments of the present application, the chip system 1200 further includes: a memory 1250; memory 1250 can include both read-only memory and random-access memory and provides operating instructions and data to processor 1210. A portion of the memory 1250 may also include non-volatile random access memory (NVRAM).
In some embodiments, memory 1250 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof:
in the embodiment of the present application, by calling an operation instruction stored in the memory 1250 (the operation instruction may be stored in an operating system), a corresponding operation is performed.
One possible implementation is: the chip systems used by the application server, the edge gateway device and the MEC network element device have similar structures, but different devices use different chip systems to realize respective functions.
The processor 1210 controls the operation of the application server, the edge gateway device and the MEC network element device, and the processor 1210 may also be referred to as a Central Processing Unit (CPU). Memory 1250 can include both read-only memory and random access memory and provides instructions and data to processor 1210. A portion of the memory 1250 may also include non-volatile random access memory (NVRAM). The various components are coupled together by a bus system 1220 in a particular application, where the bus system 1220 may include a power bus, a control bus, a status signal bus, etc., in addition to a data bus. For clarity of illustration, however, the various buses are designated in the figure as bus system 1220.
The methods disclosed in the embodiments of the present application may be applied to the processor 1210 or implemented by the processor 1210. Processor 1210 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by instructions in the form of hardware, integrated logic circuits, or software in the processor 1210. The processor 1210 may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, 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 module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 1250, and the processor 1210 reads the information in the memory 1250 and performs the steps of the above method in combination with the hardware thereof.
In the above embodiments, the instructions stored by the memory for execution by the processor may be implemented in the form of a computer program product. The computer program product may be written in the memory in advance or may be downloaded in the form of software and installed in the memory.
The present application also provides a computer-readable storage medium having stored therein instructions, which when run on a computer, cause the computer to execute the deployment method of the application described in the above embodiments.
The present application also provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the deployment method of the application described in the above embodiments.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims (20)

1. A deployment method of an application, comprising:
the method comprises the steps that edge gateway equipment receives a service request from terminal equipment, wherein the service request comprises a service address;
the edge gateway device performs header enhancement processing on the service request to obtain header enhancement information, wherein the header enhancement information comprises a mobile edge computing MEC (MEC) position identifier, and the MEC position identifier is used for identifying the network position of the MEC network element device corresponding to the edge gateway device;
and the edge gateway equipment sends the head enhancement information to an application server corresponding to the service address.
2. The method of claim 1, wherein the performing, by the edge gateway device, header enhancement processing on the service request to obtain header enhancement information comprises:
the edge gateway equipment acquires an MEC position identifier of corresponding MEC network element equipment;
and the edge gateway equipment adds position header field information in the header information of the service request to obtain header enhancement information, wherein the position header field information comprises a position header field identifier and the MEC position identifier.
3. The method of claim 2, wherein after the edge gateway device sends the header enhancement information to the application server corresponding to the service address, the method further comprises:
when the MEC network element device deploys an application corresponding to the service request, the edge gateway device receives a Domain Name System (DNS) request from the terminal device, wherein the DNS request comprises a public domain name, and the public domain name provides a domain name address of a service for the application server;
and the edge gateway equipment acquires the IP address corresponding to the public domain name and sends the IP address corresponding to the public domain name to the terminal equipment.
4. The method according to any of claims 1 to 3, wherein before the edge gateway device receives the service request from the terminal device, the method further comprises:
the edge gateway equipment acquires operation and maintenance OM information, wherein the OM information comprises an MEC position identifier of the MEC network element equipment;
the edge gateway equipment acquires registration information of an application server, wherein the registration information comprises a network address of a service provided by the application server.
5. A deployment method of an application, comprising:
an application server receives header enhancement information from edge gateway equipment, wherein the header enhancement information comprises a mobile edge computing MEC position identifier, and the MEC position identifier is used for identifying the network position of MEC network element equipment corresponding to the edge gateway equipment;
the application server determines that the MEC network element equipment corresponding to the MEC position identification needs to deploy the application according to the header enhancement information;
and the application server sends an application deployment request to the MEC network element equipment corresponding to the MEC position identifier, wherein the application deployment request comprises an application identifier, and the application identifier is used for identifying an application.
6. The method of claim 5, wherein there is at least one header enhancement information, each header enhancement information includes an MEC location identifier,
the determining, by the application server, the application to be deployed by the MEC network element device corresponding to the MEC location identifier according to the header enhancement information includes:
the application server obtains at least one MEC position identifier according to the header enhancement information;
the application server judges whether the number of the MEC position identifiers meets a threshold value;
and if the application server meets the threshold, the application server determines that the MEC network element equipment corresponding to the MEC position identifier needs to deploy the application.
7. A deployment method of an application, comprising:
the method comprises the steps that mobile edge computing MEC network element equipment receives an application deployment request sent by an application server, wherein the application deployment request comprises an application identifier, the application identifier is used for identifying an application, the application deployment request is obtained by determining an application to be deployed by the MEC network element equipment corresponding to an MEC position identifier based on head enhancement information by the application server, the head enhancement information comprises the MEC position identifier of the MEC network element equipment, and the head enhancement information is obtained by performing head enhancement processing on a service request sent by edge gateway equipment based on terminal equipment;
and the MEC network element equipment deploys the application corresponding to the application identifier according to the application deployment request.
8. The method of claim 7, wherein the application deployment request further comprises a common domain name and an application storage address, wherein the common domain name is a domain name address for providing services to the application server, and the application storage address is a storage address in a mirror file repository of the application server,
the deployment of the application corresponding to the application identifier by the MEC network element device according to the application deployment request includes:
the MEC network element equipment obtains an application identifier, a public domain name and an application storage address according to the application deployment request;
the MEC network element equipment obtains an application image file of the application corresponding to the application identifier from an image file library of the application server according to the application storage address;
the MEC network element equipment installs an application according to the application image file;
when the application is started, the MEC network element equipment obtains an Internet Protocol (IP) address of the application and sends the public domain name and the corresponding relation of the IP address to a Domain Name System (DNS).
9. An edge gateway device, comprising:
a receiving module, configured to receive a service request from a terminal device, where the service request includes a service address;
a header enhancement module, configured to perform header enhancement processing on the service request to obtain header enhancement information, where the header enhancement information includes a mobile edge computing MEC location identifier, and the MEC location identifier is used to identify a network location of an MEC network element device corresponding to the edge gateway device;
and the sending module is used for sending the header enhancement information to the application server corresponding to the service address.
10. The edge gateway device of claim 9,
the header enhancement module is specifically configured to obtain an MEC location identifier of a corresponding MEC network element device;
the header enhancement module is further configured to add location header field information to the header information of the service request to obtain header enhancement information, where the location header field information includes a location header field identifier and the MEC location identifier.
11. The edge gateway device of claim 10,
the receiving module is further configured to receive a domain name system DNS request from the terminal device when the MEC network element device deploys an application corresponding to the service request, where the DNS request includes a public domain name, and the public domain name provides a domain name address of a service for the application server;
the sending module is further configured to obtain an IP address corresponding to the public domain name, and send the IP address corresponding to the public domain name to the terminal device.
12. The edge gateway device of any of claims 9 to 11,
the receiving module is further configured to obtain operation and maintenance OM information, where the OM information includes an MEC location identifier of the MEC network element device;
the receiving module is further configured to obtain registration information of an application server, where the registration information includes a network address where the application server provides a service.
13. An application server, comprising:
a receiving module, configured to receive header enhancement information from an edge gateway device, where the header enhancement information includes a mobile edge computing MEC location identifier, and the MEC location identifier is used to identify a network location of an MEC network element device corresponding to the edge gateway device;
a processing module, configured to determine, according to the header enhancement information, that the MEC network element device corresponding to the MEC location identifier needs to deploy an application;
a sending module, configured to send an application deployment request to the MEC network element device corresponding to the MEC location identifier, where the application deployment request includes an application identifier, and the application identifier is used to identify an application.
14. The application server of claim 13, wherein the number of the header enhancement information is at least one, each header enhancement information includes an MEC location identifier,
the processing module is further configured to obtain at least one MEC location identifier according to the header enhancement information;
the processing module is further configured to determine whether the number of MEC location identifiers satisfies a threshold;
the processing module is further configured to determine that the MEC network element device corresponding to the MEC location identifier needs to deploy an application when the number of the MEC location identifiers meets a threshold.
15. A mobile edge computing, MEC, network element device, comprising:
a receiving module, configured to receive an application deployment request sent by an application server, where the application deployment request includes an application identifier, where the application identifier is used to identify an application, the application deployment request is obtained by determining, by the application server, an application that needs to be deployed by an MEC network element device corresponding to an MEC location identifier based on header enhancement information, where the header enhancement information includes the MEC location identifier of the MEC network element device, and the header enhancement information is obtained by performing header enhancement processing on, by an edge gateway device, a service request sent by a terminal device;
and the application deployment module is used for deploying the application corresponding to the application identifier according to the application deployment request.
16. The MEC network element device of claim 15, wherein the application deployment request further comprises a common domain name and an application storage address, the common domain name is a domain name address for providing services to the application server, the application storage address is a storage address in a mirror file repository of the application server,
the application deployment module is specifically used for obtaining an application identifier, a public domain name and an application storage address according to the application deployment request;
the application deployment module is further configured to obtain an application image file of the application corresponding to the application identifier from an image file library of the application server according to the application storage address;
the application deployment module is also used for installing the application according to the application image file;
the application deployment module is further configured to obtain an Internet Protocol (IP) address of the application when the application is started, and send the public domain name and the corresponding relationship between the IP addresses to a Domain Name System (DNS).
17. An edge gateway device, comprising: a transceiver and at least one processor, the transceiver and the at least one processor being interconnected by a line, the transceiver being configured to perform the operations of transceiving information at the edge gateway device side in the method of any one of claims 1 to 4;
the at least one processor performs the information processing or control operations performed at the edge gateway device side in the method of any of claims 1-4.
18. An application server, comprising: a transceiver and at least one processor, the transceiver and the at least one processor being interconnected by a line, the transceiver being configured to perform the operations of transceiving information on the application server side in the method of claim 5 or 6;
the at least one processor performs the information processing or control operations at the application server side in the method of claim 5 or 6.
19. A mobile edge computing, MEC, network element device, comprising: a transceiver and at least one processor, the transceiver and the at least one processor being interconnected by a line, the transceiver being configured to perform the operations of transmitting and receiving information at the MEC network element device side in the method of claim 7 or 8;
the at least one processor performs the information processing or control operations performed at the MEC network element device side in the method of claim 7 or 8.
20. A deployment system for an application, the system comprising:
the edge gateway device according to any of claims 9-12, and the mobile edge computing MEC network element device according to any of claims 15-16.
CN201810097147.5A 2018-01-31 2018-01-31 Application deployment method, device and system Active CN110098947B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810097147.5A CN110098947B (en) 2018-01-31 2018-01-31 Application deployment method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810097147.5A CN110098947B (en) 2018-01-31 2018-01-31 Application deployment method, device and system

Publications (2)

Publication Number Publication Date
CN110098947A CN110098947A (en) 2019-08-06
CN110098947B true CN110098947B (en) 2021-01-29

Family

ID=67442915

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810097147.5A Active CN110098947B (en) 2018-01-31 2018-01-31 Application deployment method, device and system

Country Status (1)

Country Link
CN (1) CN110098947B (en)

Families Citing this family (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113489772B (en) * 2019-08-08 2022-09-09 腾讯科技（深圳）有限公司 Network request processing method and device and electronic equipment
WO2021031127A1 (en) * 2019-08-20 2021-02-25 华为技术有限公司 Method and apparatus for obtaining information
CN110582090A (en) * 2019-08-22 2019-12-17 网宿科技股份有限公司 CDN scheduling method, scheduling system and MEC network element
CN110535930A (en) 2019-08-22 2019-12-03 网宿科技股份有限公司 A kind of dispatching method and system of edge C DN node
CN112506524A (en) * 2019-09-16 2021-03-16 ***通信有限公司研究院 Deployment method, device and equipment of AI (Artificial Intelligence) capability engine and storage medium
CN112532669B (en) * 2019-09-19 2023-06-13 贵州白山云科技股份有限公司 Network edge computing method, device and medium
CN112533177A (en) * 2019-09-19 2021-03-19 大唐移动通信设备有限公司 Method, device, apparatus and medium for providing and discovering moving edge calculation
CN114586327A (en) * 2019-10-21 2022-06-03 联想（新加坡）私人有限公司 DNS server selection based on service area in which user equipment is located
CN112953843B (en) * 2019-11-26 2022-12-30 华为技术有限公司 Data transmission method and device
CN110995826B (en) * 2019-11-29 2022-05-03 腾讯科技（深圳）有限公司 Communication processing method and device, computer readable medium and electronic equipment
CN111030914B (en) * 2019-12-19 2021-08-24 腾讯科技（深圳）有限公司 Data transmission method and data transmission system
CN111030875A (en) * 2019-12-25 2020-04-17 浪潮商用机器有限公司 System deployment method and device of data center and computer storage medium
WO2021168714A1 (en) * 2020-02-26 2021-09-02 华为技术有限公司 Application discovery method, apparatus, and system
CN113316158B (en) * 2020-02-27 2023-03-24 华为技术有限公司 Method and device for deploying application instance and readable storage medium
CN111405014B (en) * 2020-03-09 2022-04-22 联想(北京)有限公司 Data processing method and device based on mobile edge computing MEC platform and storage medium
CN113382028B (en) * 2020-03-10 2023-04-07 中国电信股份有限公司 Method and system for realizing content distribution network and edge user plane functional entity
CN111638935B (en) * 2020-04-15 2022-07-01 阿里巴巴集团控股有限公司 Mirror image management method, network system, device, and storage medium
CN113766629B (en) * 2020-06-03 2022-12-27 ***通信集团浙江有限公司 Service processing method and system under 5G edge computing scene
CN111651240A (en) * 2020-06-04 2020-09-11 浙江九州云信息科技有限公司 Multi-access edge computing platform management method and device
CN111866950B (en) * 2020-06-16 2022-03-25 华为技术有限公司 Method and communication device for data transmission in MEC
CN112187867A (en) * 2020-09-02 2021-01-05 广州禹龙信息科技有限公司 Virtual desktop processing method and system combined with edge cloud
CN112130931B (en) * 2020-09-27 2023-01-06 联想(北京)有限公司 Application deployment method, node, system and storage medium
CN114374978A (en) * 2020-10-15 2022-04-19 ***通信有限公司研究院 Method, device and computer readable storage medium for discovering MEC server
CN112511660B (en) * 2020-11-12 2023-11-24 北京软通智慧科技有限公司 Management system, method and device of edge terminal equipment and storage medium
CN114513494B (en) * 2020-11-16 2024-03-19 中国电信股份有限公司 Service scheduling method, system, storage medium and service system
CN112422685B (en) * 2020-11-19 2022-02-01 中国联合网络通信集团有限公司 5G data processing system and method based on mobile edge computing MEC
US20220206772A1 (en) * 2020-12-30 2022-06-30 Accenture Global Solutions Limited Scalable, robust, and secure multi-tenant edge architecture for mission-critical applications
CN112910991B (en) * 2021-01-29 2022-10-04 杭州涂鸦信息技术有限公司 Back-end application calling method and device, computer equipment and readable storage medium
CN115134357A (en) * 2021-03-10 2022-09-30 ***通信有限公司研究院 Capability deployment method and device and edge computing service operation equipment
CN113207081B (en) * 2021-03-29 2022-10-21 网络通信与安全紫金山实验室 Communication method, communication device, electronic equipment and medium
CN115190169A (en) * 2021-04-02 2022-10-14 华为技术有限公司 Communication method, device and system
CN113079488B (en) * 2021-04-07 2022-02-18 中移(上海)信息通信科技有限公司 Information interaction method, device and equipment
CN112867061B (en) * 2021-04-26 2021-09-17 香港中文大学（深圳） Resource allocation method and device
CN115529590A (en) * 2021-06-24 2022-12-27 中移(成都)信息通信科技有限公司 Capacity opening information acquisition method and device and communication equipment
CN115942294A (en) * 2021-07-16 2023-04-07 华为技术有限公司 Communication method and device
CN116088884A (en) * 2021-11-05 2023-05-09 贵州白山云科技股份有限公司 Method, equipment and system for executing control codes based on distributed cloud network
CN114257588B (en) * 2021-11-23 2023-07-18 中国联合网络通信集团有限公司 Communication system
CN114172951B (en) * 2021-12-07 2023-06-06 中国联合网络通信集团有限公司 MEC sharing method, communication device and storage medium
CN113923694B (en) * 2021-12-14 2022-05-03 网络通信与安全紫金山实验室 Network resource arranging method, system, device and storage medium
CN114422477B (en) * 2021-12-30 2023-07-21 联想(北京)有限公司 Domain name resolution method, device and storage medium based on edge cloud architecture

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106231607A (en) * 2016-09-21 2016-12-14 北京佰才邦技术有限公司 The method of a kind of resource distribution and base station
WO2017091934A1 (en) * 2015-11-30 2017-06-08 华为技术有限公司 Capability enablement method, system and related device
CN107018534A (en) * 2016-01-28 2017-08-04 中兴通讯股份有限公司 A kind of method for realizing mobile edge calculations service, apparatus and system
CN107302762A (en) * 2016-04-14 2017-10-27 大唐移动通信设备有限公司 A kind of Operational Visit and its control method, device
CN107566429A (en) * 2016-06-30 2018-01-09 中兴通讯股份有限公司 Base station, the response method of access request, apparatus and system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017091934A1 (en) * 2015-11-30 2017-06-08 华为技术有限公司 Capability enablement method, system and related device
CN107018534A (en) * 2016-01-28 2017-08-04 中兴通讯股份有限公司 A kind of method for realizing mobile edge calculations service, apparatus and system
CN107302762A (en) * 2016-04-14 2017-10-27 大唐移动通信设备有限公司 A kind of Operational Visit and its control method, device
CN107566429A (en) * 2016-06-30 2018-01-09 中兴通讯股份有限公司 Base station, the response method of access request, apparatus and system
CN106231607A (en) * 2016-09-21 2016-12-14 北京佰才邦技术有限公司 The method of a kind of resource distribution and base station

Also Published As

Publication number Publication date
CN110098947A (en) 2019-08-06

Similar Documents

Publication Publication Date Title
CN110098947B (en) Application deployment method, device and system
KR102259804B1 (en) Methods, registration centers and devices for service discovery
US11178062B2 (en) Orchestrating physical and virtual resources for delivering digital contents
WO2020135800A1 (en) Domain name server allocation method and device
WO2021057889A1 (en) Data processing method and apparatus, electronic device, and storage medium
US9549321B2 (en) Remote provisioning of 3GPP downloadable subscriber identity module for virtual machine applications
CN110049022B (en) Domain name access control method and device and computer readable storage medium
CN110381162B (en) Service processing method and related device
US20200169533A1 (en) Method and Apparatuses for Enabling Routing of Data Packets Between a Wireless Device and a Service Provider Based in the Local Service Cloud
KR20200062272A (en) Mobile network interaction proxy
EP2648392A1 (en) Application programming interface routing system and method of operating the same
KR20150121713A (en) Allocating resources between network nodes for providing a network node function
EP3231153B1 (en) Distributing a network access policy
CN114025021B (en) Communication method, system, medium and electronic equipment crossing Kubernetes cluster
US10305853B2 (en) Network, a cloud-based server, and a method of registering for a service
EP4319097A1 (en) Communication method, apparatus, computer-readable medium electronic device, and program product
CN112566164B (en) Communication system and service quality control method
US11558283B2 (en) Information collecting system and information collecting method
CN113037761B (en) Login request verification method and device, storage medium and electronic equipment
CN112104640B (en) Data processing method, device and equipment of gateway and readable storage medium
WO2019071995A1 (en) Content distribution method, device and system
JP2019016070A (en) Device and method for remotely managing device and program therefor
CN114629912B (en) Communication transmission method and device based on MEC
CN112825524B (en) Method, device and system for determining network service node
CN109076381B (en) Service data stream sending method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant