WO2019144746A1 - 一种业务管理的方法及相关设备 - Google Patents

一种业务管理的方法及相关设备 Download PDF

Info

Publication number
WO2019144746A1
WO2019144746A1 PCT/CN2018/123459 CN2018123459W WO2019144746A1 WO 2019144746 A1 WO2019144746 A1 WO 2019144746A1 CN 2018123459 W CN2018123459 W CN 2018123459W WO 2019144746 A1 WO2019144746 A1 WO 2019144746A1
Authority
WO
WIPO (PCT)
Prior art keywords
mec
execution
service
information
management device
Prior art date
Application number
PCT/CN2018/123459
Other languages
English (en)
French (fr)
Inventor
任德旺
陆伟
桂小林
张开元
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18902113.2A priority Critical patent/EP3720091A4/en
Publication of WO2019144746A1 publication Critical patent/WO2019144746A1/zh
Priority to US16/938,756 priority patent/US20200358673A1/en

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
    • 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
    • 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/2866—Architectures; Arrangements
    • H04L67/288—Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
    • 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/2866—Architectures; Arrangements
    • H04L67/2885—Hierarchically arranged intermediate devices, e.g. for hierarchical caching
    • 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/52—Network services specially adapted for the location of the user terminal
    • 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/53—Network services using third party service providers
    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
    • H04N7/181—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast for receiving images from a plurality of remote sources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]

Definitions

  • the present application relates to the field of communications, and in particular, to a method and related device for service management.
  • a service deployment method in a distributed computing environment deploying services to a cluster.
  • the cluster is composed of devices with computing capabilities.
  • the devices in the cluster jointly perform services.
  • the computing power and network are generally based on the devices.
  • Bandwidth to select clusters for example, to select devices with greater computing power and greater communication capabilities to deploy services.
  • Current business deployment methods are not suitable for use in mobile edge computing environments.
  • the embodiment of the present application provides a method for service management and related equipment, which is used for automatically deploying a third-party service.
  • the architecture is based on an automatic service deployment architecture, and the architecture includes an open function device, an MEC management device, and an MEC execution device.
  • the terminal the architecture is a hierarchical architecture, which facilitates the rapid and automatic deployment of third-party services on the network edge device (MEC device) by the third-party service, including but not limited to the search and rescue service of the lost contact person, real-time Querying traffic conditions, etc.; providing high-quality services to users through deployed services, which can improve the utilization of MEC device resources, and provide users with diverse business services and improve user experience.
  • MEC device network edge device
  • an embodiment of the present application provides a method for service management, including:
  • the mobile edge computing MEC management device receives the service description information and the service execution information of the service to be deployed sent by the open function device, where the service execution information includes information for executing the service description information; the service description information is used for the specific description of the service to be deployed;
  • the information includes at least one execution program and a business logic relationship, the execution program is configured to execute a function corresponding to the service;
  • the business logic relationship is a relationship between at least two execution programs when the execution program is at least two, the business logic The relationship includes an independent relationship and a dependency relationship;
  • the MEC management device determines the target MEC execution device; then, the MEC management device sends the service description information and the service execution information to the target MEC execution device; the MEC management device receives the service execution information sent by the target MEC execution device The result of the execution is obtained by the target MEC executing device according to the service description information and the service execution information; the MEC management device obtains the service result of the service to be deployed according to the execution result; the MEC management device sends
  • the description information further includes information about a geographical area of the service to be deployed, and the MEC management device may determine the target MEC execution device according to the feature and the geographic area of the service execution information. Attributes with location areas can be deployed to target execution devices for geographically sensitive services, and are suitable for geographically sensitive services in mobile edge computing environments.
  • the determining, by the MEC management device, the MEC execution device according to the feature and the geographic region of the service execution information may include: the MEC management device determining the desired deployment location of the execution information according to the feature of the execution information; the MEC management device is open to the The functional device sends the desired deployment location, the open functional device is responsible for monitoring the performance and status of all MEC devices, and the open functional device stores the location information of all MEC devices, the desired deployment location is used for the open functional device to determine the set of MEC execution devices, and the MEC execution device The coverage of the set includes the geographic area; then, the MEC management device receives the set of MEC execution devices determined by the open function device; the MEC management device selects the target MEC execution device from the set of MEC execution devices.
  • the specific manner in which the MEC management device selects the target MEC execution device from the set of MEC execution devices may be: the MEC management device determines the location of the MEC execution device in the set of MEC execution devices and the desired deployment location. The distance between the MEC management devices selects the target MEC execution device from the set of MEC execution devices according to the distance, for example, the MEC management device selects the MEC execution device closest to the desired deployment location as the target MEC. Executing the device, the method in the embodiment of the present application, based on the geographic location of the target MEC execution device, the target MEC execution device is an MEC device suitable for deploying service execution information, and the method is simple.
  • the method for determining the target MEC execution device may further be: the MEC management device acquires the state information of the MEC execution device; the MEC management device integration distance and the MEC execution device state information are two parameters.
  • the target MEC execution device is selected from the set of MEC execution devices. In the embodiment of the present application, not only the distance factor but also the processing capability of the MEC device is considered, and the target MEC execution device is comprehensively selected through the two parameters.
  • the service execution information includes at least one execution program
  • the number of target MEC execution devices is at least one.
  • the MEC management device may A deployment policy is defined, the deployment strategy includes a correspondence between the at least one execution program and the at least one target MEC execution device; and then, the MEC management device sends the corresponding execution program to the target MEC execution device according to the correspondence relationship.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the MEC management device, which includes a program designed to perform the above aspects.
  • an embodiment of the present invention provides a management device, which has the functions performed by the MEC management device in the foregoing method.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the management device includes a memory, a network interface, and a processor.
  • the memory is used to store computer executable program code and is coupled to a network interface.
  • the program code includes instructions that, when executed by the processor, cause the management device to perform the information or instructions involved in the MEC management device in the above method.
  • the embodiment of the present application provides a method for service management, including:
  • the open function device receives the service description information and the service execution information of the service to be deployed, and the service execution information includes information for executing the service description information, where the service server is a third-party service device, and is configured to send the to-be-deployed to the open function device.
  • the service request is used to request the deployment service to the open function device 102; for example, the service may be a search and rescue service for the lost contact person, a real-time traffic condition query, etc.; the service request includes the service description information and the service execution information, and the service description The information is used for the specific description of the service to be deployed; the open function device sends the service description information and the service execution information to the mobile edge computing MEC management device; the open function device determines the set of the MEC execution device; the open function device sends the set of the MEC execution device to The MEC management device is configured to determine the target MEC execution device from the set of MEC devices, and the service execution information is used by the target MEC execution device to obtain the execution result of the service to be deployed according to the service description information, and the execution result is used by the MEC management device.
  • the MEC management device obtains the service result of the service to be deployed; the open function device receives the service result of the service to be deployed sent by the MEC management device; the open function device is an interface device between the service server and the MEC management device, and is used for receiving and receiving the service.
  • the description information and the service execution information are sent to the MEC management device.
  • the third-party server quickly and automatically deploys the third-party service on the network border device (MEC device) based on the characteristics of the computing, storage, and processing capabilities of the MEC device. To provide users with a variety of business services.
  • the service description information includes information about a geographical area of the service to be deployed, and before the open function device determines that the MEC executes the device set, the open function device receives the desired deployed geographic location sent by the MEC management device, and desires to deploy the geographic location.
  • the MEC management device sends a query request to the open function device for querying the nearby MEC execution device of the desired deployment location; then, the open function device determines the set of MEC execution devices located within the range of the desired deployment geographic location preset.
  • the service description information includes information about a geographical area related to the service
  • the open function device before the open function device sends the service description information to the MEC management device, the open function device selects the MEC management device from the multiple MEC execution devices, The coverage of multiple MEC execution devices includes geographic regions.
  • the open function device selects the MEC management device from the multiple MEC execution devices.
  • the specific manner may be: the open function device acquires information about a geographical area in the service description information, and the coverage of the multiple MEC devices Include a geographic area, determine a plurality of MEC devices whose coverage includes a geographical area, an open function device acquires status information of multiple MEC execution devices, status information is used to indicate that the MEC performs processing capability of the device, and an open function device executes devices from multiple MECs.
  • the MEC execution device having the strongest processing capability is selected as the MEC management device, or the open function device selects the MEC execution device whose processing capability is greater than the threshold from among the plurality of MEC execution devices as the MEC management device.
  • FIG. 1 is a schematic diagram of a scenario structure of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an MEC-based service deployment architecture in an embodiment of the present application
  • FIG. 3 is a schematic flowchart of steps of an embodiment of a method for service management according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of a scenario in an embodiment of the present application.
  • FIG. 5 is a schematic diagram of another scenario in the embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of an embodiment of a management device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of another embodiment of a management device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another embodiment of a management device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another embodiment of a management device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of another embodiment of a management device according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of an embodiment of an open function device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of another embodiment of an open function device according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of another embodiment of an open function device according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of another embodiment of an open function device according to an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of another embodiment of an open function device according to an embodiment of the present application.
  • the embodiment of the present application provides a method, a related device, and a system for service management, which are used for automatically deploying third-party services.
  • MEC Mobile Edge Computing sinks computing power to the edge of the mobile communication network and adds computing, storage, and processing functions to the edge of the network.
  • the MEC device in the embodiment of the present application can be understood as a device deployed to a network edge location close to a terminal location, having computing, storage, and processing capabilities.
  • the MEC device can have attributes of a location area and is more distant from the terminal (roadside camera, etc.). Near features.
  • the MEC device in the embodiment of the present application includes the MEC management device and the MEC execution device. It should be noted that the MEC management device and the MEC execution device in the embodiment of the present application are only functional when performing services, and any MEC management. The device can be used as a MEC management device or as a MEC execution device.
  • FIG. 1 is a schematic diagram of a scenario structure of a communication system according to an embodiment of the present application.
  • the communication system includes a service server 101, an open function device 102, an MEC management device 103, an MEC execution device 104, and a terminal 105.
  • the service server 101 is in communication with the open function device 102
  • the open function device 102 is in communication with the MEC management device 103
  • the open function device 102 is in communication with the MEC execution device 104
  • the MEC management device 103 is in communication with the MEC execution device 104
  • the MEC is executing the device.
  • 104 is communicatively coupled to terminal 105.
  • the service server 101 is a third-party service device, and is configured to send a service request for the service to be deployed to the open function device 102, where the service request is used to request the deployment service from the open function device 102.
  • the service can be a search and rescue service for a lost person, a real-time traffic query, and the like.
  • the service request includes the service description information and the service execution information, and the service description information is used for the specific description of the service to be deployed. If the service to be deployed takes the search and rescue service of the disconnected person as an example, the service description information may include the photo of the lost contact person and the license plate.
  • the number and the like; the service execution information is an execution program related to the service to be deployed, and can be understood as a function module, for example, a face recognition module, a vehicle tracking module, and the like.
  • the open function device 102 is an interface device between the service server 101 and the MEC management device 103, and is configured to receive the service request sent by the service server 101, and send the service description information and the service execution information to the MEC management device 103, and open the function device. 102 is responsible for monitoring the performance and status of all MEC devices and obtaining the geographic location of all MEC devices.
  • the MEC device includes an MEC management device 103 and an MEC execution device 104. The service result of the service to be deployed fed back by the MEC management device 103 is received, and the service result is fed back to the service server 101.
  • the MEC management device 103 is configured to receive the service description information and the service execution information of the service to be deployed sent by the open function device 102, analyze the service requirement, collect the state information of the MEC execution device 104, and select to deploy the service to the MEC execution device 104.
  • the service description information and the service execution information are sent to the MEC execution device 104.
  • the execution results of all the MEC execution devices 104 are collected and aggregated, the final service result is obtained, and the service result is fed back to the open function device 102.
  • the MEC executing device 104 is configured to receive the service description information and the service execution information sent by the MEC management device 103, run the execution program, obtain an execution result according to the service description information and the data uploaded by the terminal 105, and send the execution result to the MEC management device. 103.
  • the terminal 105 includes, but is not limited to, a road surveillance camera, an in-vehicle device on the vehicle, a sensor, etc., for collecting data, and uploading the collected data to the MEC execution device 104.
  • the architecture includes an open function device, an MEC management device, an MEC execution device, and a terminal.
  • the architecture is a hierarchical architecture, and the architecture facilitates a third-party server at a network edge device (MEC device).
  • MEC device network edge device
  • the MEC device is used to quickly and efficiently deploy and manage services, and a method for automatically deploying and managing services is provided.
  • FIG. 2 is a schematic diagram of a service deployment architecture based on the MEC in the embodiment of the present application
  • FIG. 3 is a service management manner provided in the embodiment of the present application.
  • Step 301 The service server sends the service description information and the service execution information of the service to be deployed to the open function device.
  • the service server sends a service request for the service to be deployed to the open function device, where the service request includes the service description information and the service execution information.
  • the service execution information includes at least one execution program and a business logic relationship, where the execution program is used to execute a function corresponding to the service; the business logic relationship is a relationship between at least two execution programs when the execution program is at least two,
  • the business logic relationship includes independent relationships and dependencies.
  • the service execution information includes a first execution program (such as a face recognition module) and a second execution program (such as a vehicle tracking module), and the result of the first execution program and the result of the second execution program are not related.
  • the service execution information includes a first road congestion analysis module and a second road congestion analysis module, and the analysis result of the second road congestion analysis module depends on an analysis result of the first road congestion analysis module, that is, the service logic Relationships are dependencies.
  • the specific execution program included in the service execution information is only an example for convenience of description, and does not cause a limited description of the present application. Specifically, the following steps may be included:
  • the service server sends a service request for the service to be deployed to the open function device, where the service request includes service description information, where the service request is used to request the open function device to deploy the service.
  • the service description information may include information about a geographical area related to the service.
  • the open function device After receiving the service request, the open function device parses the service request by using a deployment request parser to obtain information service description information, and feeds back a response to the service server, where the response is used to indicate that the service is allowed to be deployed.
  • the service server After receiving the response, the service server sends the service execution information to the open function device, where the service execution information includes at least one execution program, and the execution program is used to execute the function corresponding to the service.
  • FIG. 4 is a schematic diagram of a scenario in the embodiment of the present application.
  • the service server sends a service request for the service to be deployed to the open function device, where the service request is a search and rescue request for the lost contact person, the service description information includes a photo of the lost contact person, a license plate number of the vehicle, and a geographical area information, the geographic area The information can be the place where the lost person may go, the place where you often go, or the place where it last appeared before the loss.
  • the open function device feeds back to the service server a response that is allowed to be deployed.
  • the running deployment information is used to indicate that the service server can deploy the service, and after receiving the response, the service server sends the response to the open function device.
  • Business execution information for example, the business execution information includes a first execution program and a second execution program, the first execution program being a face recognition execution program (also referred to as a face recognition module in this example) for the face of the disconnected person
  • the second execution program is a vehicle tracking execution program (also referred to as a vehicle tracking module in this example) for identifying the license plate number of the vehicle in which the lost person is traveling.
  • the business logic relationship between the face recognition module and the vehicle tracking module is an independent relationship.
  • the service to be deployed is an example for convenience of description, and does not cause a limited description of the present application.
  • the third-party service server has sent the same service to be deployed to the open function device, the service execution information does not need to be sent as the open function device, and the service execution information has been stored in the open function device, for example,
  • the service server sends a request for the search and rescue service of the disconnected personnel to the open function device for the first time.
  • the service server has sent the face recognition module and the vehicle tracking module to the open function device, and when the second request for the deployment of the lost contact personnel search and rescue service, The face recognition module and the vehicle final module are not sent to the open function device.
  • Step 302 The open function device receives the service description information and the service execution information, and sends the service description information and the service execution information to the MEC management device.
  • the open function device After receiving the service description information and the service execution information, the open function device selects the MEC management device from the multiple MEC devices.
  • the plurality of MEC devices include MEC 0 , MEC 1 , MEC 2 , . . . MEC 8 and the like.
  • the open function device may designate one MEC device from among multiple MEC devices as the MEC management device.
  • the open function device monitors real-time status information of the MEC device, where the status information is used to indicate processing capability of the MEC device, where the real-time status information includes but is not limited to the CPU status, the current load, and the current storage.
  • the open function device can select a MEC device with a strong processing capability as the MEC management device according to the real-time status information of the MEC device, or the MEC execution device with the processing capability greater than the threshold value from the plurality of MEC execution devices. As a MEC management device.
  • the open function device acquires information about a geographic area in the service description information, where the coverage of the multiple MEC devices includes the geographic area, and the determined coverage includes multiple MECs of the geographic area. The device then selects one of the plurality of MEC devices as the MEC management device according to the processing capability of the plurality of MEC devices.
  • the geographic area in the service description information is the last place where the disconnected person appears to be the door of the F street G shopping street in the F city, and the open function device is determined to be centered on the door of the Q shopping mall with a radius of 5000.
  • Three MEC devices in the range select one of the three MEC devices with the strongest processing power as the MEC management device. It should be noted that, in this example, the method for selecting the MEC management device is only an example, and does not cause a limited description of the application.
  • the open function device sends the service description information and the service execution information to the MEC management device.
  • the open function device transmits the photo of the lost contact person, the license plate number, the face recognition module, the vehicle tracking module, and the business logic relationship between the panel recognition module and the vehicle tracking module to the MEC management device.
  • Step 303 The MEC management device receives the service description information and the service execution information, and the MEC management device determines the target MEC execution device according to the service description information and the service execution information. After receiving the service description information and the service execution information, the MEC management device stores the execution program included in the service execution information in the function module library.
  • the method may include the following steps: C1: The MEC management device analyzes characteristics of the execution program, and determines a desired deployment location of the service execution information according to characteristics and geographic regions of the service execution information.
  • the MEC management device determines the desired deployment location of the execution program according to the characteristics of the execution program, the business logic relationship between the execution programs, and the geographic area integration.
  • a service that is sensitive to a geographical location may be deployed, and is suitable for a service that is geographically sensitive and has high real-time requirements in a mobile edge computing environment.
  • the execution program is also described by taking a facial recognition module and a vehicle tracking module as an example.
  • the MEC management device analyzes features of the facial recognition module and the vehicle tracking module, for example, the facial recognition module is suitable for deployment to a densely populated area, or can be understood as The deployment of the facial recognition module to densely populated areas can more effectively function as a facial recognition module; the vehicle tracking module is suitable for deployment to the road, or it can be understood that the vehicle tracking module can be deployed to the road to more effectively utilize the vehicle.
  • the function of the tracking module which belongs to the geographic area.
  • the business logic relationship between the execution programs is an independent relationship. Therefore, the vehicle tracking module and the face recognition module can be deployed separately and do not affect each other.
  • the MEC management device determines the geographic location that each functional module desires to deploy. For example, the desired deployment location is centered on the Q storefront door and has a radius of 5000.
  • the MEC management device sends a desired deployment location to the open function device, and the desired deployment location is used by the open function device to determine a set of MEC execution devices.
  • the MEC management device sends a query request to the open function device, and the query request carries the desired deployment location Lm.
  • the open function device is responsible for monitoring the performance and status of all MEC devices, and the open function device stores the location information of all MEC devices, and the MEC management device sends a query request to the open function device, the query request is used to query the nearby MEC of the desired deployment location. Execute the device.
  • the open function device receives the query request sent by the MEC management device, and extracts the desired deployment location Lm.
  • the open function device queries the MEC device located in the preset deployment location Lm preset range from the node information base, for example, the MEC device within the preset range of the desired deployment location (x 1 , y 1 ) is MEC 1 , expectation The MEC devices in the preset range of the deployment location (x 2 , y 2 ) are MEC 2 and MEC 3, etc., it should be noted that the number of MEC devices within a preset range of the desired deployment location is not limited, in Lm.
  • the open function device sends the set Le of the MEC execution device to the MEC management device, and the set Le of the MEC execution device can also be understood as a set of initial MEC execution devices.
  • the MEC management device receives the set Le of MEC execution devices sent by the open function device;
  • the MEC management device selects the target MEC execution device from the set of MEC execution devices.
  • the MEC management device determines a distance between a location of the MEC execution device and a desired deployment location in the set of MEC execution devices; the MEC management device selects a target MEC execution device from the set of MEC execution devices according to the distance .
  • the service execution information includes N execution programs, the desired geographic location includes N desired deployment locations; the ith execution program of the N execution programs corresponds to the ith desired deployment location of the N desired deployment locations; MEC The management device compares the distance between the i-th desired deployment location in the desired geographic location and the geographic location of each MEC enforcement device in the set of MEC enforcement devices, i taking each of the values in N.
  • the MEC management device determines that the i-th desired deployment location matches the j-th MEC execution device.
  • the MEC management device establishes a correspondence between the i-th execution program corresponding to the i-th desired deployment location and the j-th MEC execution device.
  • the execution device acts as the target MEC execution device.
  • the MEC management device acquires real-time status information of each MEC execution device from the open function device; the MEC management device selects the target MEC from the set of MEC execution devices according to the distance and the real-time status information of the MEC execution device. Execute the device.
  • the real-time status information includes, but is not limited to, the CPU status of the MEC execution device, load conditions, storage conditions, and the like. For example, if the distance from the jth MEC execution device of the i-th desired deployment location is X, the distance from the kth MEC execution device of the i-th desired deployment location is Y, and the difference between X and Y The parameter is smaller than the threshold.
  • the real-time state information of the two MEC execution devices may be further selected to select the i-th desired deployment.
  • the target MEC execution device that matches the location for example, the processing capability of the current kth MEC execution device is greater than the processing capability of the jth MEC execution device (referred to as "MEC j "), then the kth MEC execution device is selected at this time. (denoted as "MEC k ”) as the target MEC execution device that matches the i-th desired deployment location.
  • Step 304 The MEC management device formulates a deployment policy by using a manager, where the deployment policy includes a correspondence between the execution program and the target MEC execution device.
  • the device After the MEC management device selects the target MEC execution device, the device sends a sub-service deployment request to the target MEC execution device. For example, the MEC management device sends a sub-service deployment request to the k-th target MEC execution device (MEC k ), the sub-service deployment request. For the request to deploy the sub-service, that is, the vehicle tracking service, the target MEC executing device feeds back the deployment confirmation information to the MEC management device according to the sub-service deployment request, and after receiving the deployment confirmation information, the MEC management device determines that the target MEC execution device can The sub-service is executed, and the MEC management device formulates a deployment strategy.
  • MEC k target MEC execution device
  • the number of the execution programs is at least one
  • the number of the target MEC execution devices is at least one
  • the MEC management device determines the target MEC execution device that matches the i-th desired deployment location
  • the MEC management device determines the i-th desired deployment.
  • the corresponding execution program (such as the face recognition module) can determine the correspondence between the execution program and the target MEC execution device, for example, the face recognition module and the jth MEC execution device (MEC j ), the vehicle tracking module and the kth
  • the MEC execution device (MEC k ) has a corresponding relationship.
  • the execution program and the target MEC execution device may have a one-to-one relationship, may be a one-to-many relationship, or may be a many-to-one relationship.
  • the execution programs are a facial recognition module, a vehicle tracking module, and an image recognition module
  • the desired deployment position of the facial recognition module is The densely populated area corresponds to the first desired location, and the desired deployment location of the vehicle tracking module is next to the road, corresponding to the second desired deployment location, and the desired deployment location of the image recognition module can also be the roadside, corresponding to the third desired deployment.
  • MEC k that is, the facial recognition module and the vehicle tracking module correspond to the first k MEC execution devices (MEC k ); of course, in another case, it is also possible that one execution program corresponds to at least two MEC execution devices.
  • the vehicle tracking module requires less resources when identifying a clear license plate number. A single MEC device can be completed independently. If the fuzzy license plate number is identified, the calculation amount is large, and multiple MEC devices need to cooperate, so that the speed can be accelerated. The speed of recognition. It should be noted that the correspondence between the execution program, the execution program, and the desired deployment location in this example is illustrative and does not result in a limited description of the application.
  • Step 305 The MEC management device sends the service description information and the service execution information to the target MEC execution device.
  • the MEC management device extracts an execution program from the function module library, and sends a corresponding execution program to the target MEC execution device according to the deployment policy.
  • the MEC management device transmits the face recognition module to the jth target execution device (MEC j ), and transmits the vehicle tracking module to the kth MEC execution device (MEC k ).
  • Step 306 The target MEC execution device receives the service description information and the execution program sent by the MEC management device, and after the execution of the execution program, obtains the data reported by the terminal, and obtains the execution result according to the data reported by the terminal and the service description information.
  • the target MEC execution device receives a photo of the lost contact person sent by the MEC management device and a face recognition module, and the target MEC execution device runs the face Identifying the module and receiving the image information (such as a photo) acquired by each terminal, and the facial recognition module matches the photo reported by the terminal with the photo of the missing person to obtain an execution result. If the matching is successful, the execution result includes the time when the matching is successful. Poke, and the location where the terminal gets the photo. If the matching is not successful, the execution result includes the geographic location of the photo and the corresponding timestamp of the photo.
  • the target MEC execution device receives a photo of the license plate number sent by the MEC management device and the vehicle tracking module, the target MEC execution device runs the vehicle tracking module, and receives each terminal
  • Step 307 The MEC management device receives the execution result sent by each target MEC execution device, and aggregates the execution result of the device of each target MEC by the aggregator to obtain the service result of the service to be deployed.
  • the MEC management device After receiving the execution result sent by each target MEC executing device, the MEC management device aggregates the execution result of each target MEC execution device according to the service logic relationship, and obtains the service result of the service to be deployed.
  • the business logic relationship between the two execution programs, the face recognition module and the vehicle tracking module is independent.
  • the business result includes: at 12:06 on January 10, 2018, the loss is found at the P location.
  • Step 308 The MEC management device sends the service result to the open function device.
  • the MEC management device may also send the service result and the deployment policy to the open function device, where the open function device stores the deployment policy.
  • Step 309 The open function device sends the service result of the service to be deployed to the service server.
  • the MEC device is used to implement the automatic deployment of the third-party service in the mobile edge environment.
  • the open function device is an interface device between the third-party service server and the MEC management device, and the MEC management device receives the open function device.
  • the service description information and the service execution information of the service to be deployed, the service execution information includes at least one execution program, where the execution program is used to execute the function corresponding to the service to be deployed, and then the MEC management device determines the target MEC execution device, and the target MEC executes
  • the device is a MEC device that specifically performs the service to be deployed; the MEC management device sends the service description information and the service execution information to the target MEC executing device; the MEC management device receives the execution result of the service execution information sent by each target MEC executing device, and the MEC management device
  • the execution result sent by the target MEC execution device is aggregated to obtain the service result of the service to be deployed, and the MEC management device sends the service result to the open function device, and the open function device sends the service result to the third-party service server.
  • the service to be deployed is a search and rescue service for the lost contact personnel, and the cooperation of two dimensions (horizontal dimension and vertical dimension) is realized, that is, facial recognition and vehicle tracking can be performed simultaneously, and different execution programs are sent to corresponding
  • the target MEC executes the device such that multiple MEC execution devices collaborate between the devices.
  • the horizontal dimension deploying the facial recognition module and the vehicle tracking module, the functions performed by the two execution programs are different, the facial recognition module can be used to find the position and time of the recent occurrence of the disconnected person, and the vehicle tracking module is used to track the current suspicious vehicle.
  • the location and corresponding time, the two execution programs jointly detect the location of the lost person and the corresponding time.
  • Each function module may require multiple border devices to cooperate.
  • the vehicle tracking module recognizes the clear license plate number
  • the required resources are small.
  • a single MEC device can be completed independently, and the fuzzy license plate number is recognized. It requires multiple MEC devices to work together to speed up the recognition.
  • the service to be deployed is a service with high real-time requirements and is sensitive to the location.
  • the third-party service can be automatically deployed through the architecture of the open function device, the MEC management device, and the MEC execution device, and can be improved. Resource utilization of MEC devices.
  • the MEC device locally processes the road condition data uploaded by all the cameras in its coverage area, avoids the problems of communication congestion and high transmission cost caused by a large number of road condition data transmissions; and, through the cooperation of multiple MEC execution devices, completes a complete service and improves the overall service. The efficiency of business execution.
  • FIG. 5 is a schematic diagram of a scenario in an embodiment of the present application.
  • Another application scenario provided by the embodiment of the present application is the service description of the service to be deployed in the application scenario: the location-aware feature is adopted by the distributed MEC device, and each MEC device has a certain coverage area characteristic, and the terminal (side roadside) More similar features, such as camera, deploy real-time traffic monitoring services on MEC equipment, real-time processing and analysis of road condition data uploaded from roadside cameras, and obtain current congestion information of urban roads (for example, congestion, congestion, slow and smooth, etc.
  • the MEC device can obtain the congestion information of all the roads in the coverage area by analyzing the road condition data uploaded by the camera in the coverage area; the open function device monitors the status information of all the MEC devices, for example, the status information includes resource remaining information, load information, CPU status information, storage status information, and the like.
  • the third-party service server sends a service deployment request to the open function device, where the service deployment request carries the service description information, where the service description information includes a geographical area, where the geographic area is an area where the road condition to be monitored is located.
  • the open function device receives and parses the service deployment request to obtain a geographic area.
  • the service deployment request is a real-time query request for the road condition
  • the geographical area is “Brunn Road, Shenzhen”.
  • the geographical regions in this example are illustrative and do not result in a limiting description of the application.
  • the open function device query coverage area includes multiple MEC devices in the geographic area, and one MEC is selected from the plurality of MEC devices as the MEC management device, and the specific method for the open function device to select the MEC management may be combined with the B1 in the foregoing embodiment. The steps are understood and will not be described here.
  • the open function device returns a response to the third party service server, where the response is used to indicate that the road condition is allowed to be deployed in real time to query the service;
  • the third-party service server After receiving the response, the third-party service server sends the service execution information to the open function device.
  • the service execution information includes a road congestion analysis execution program (ie, a road congestion analysis module) and a business logic relationship, and the business logic relationship is each road.
  • the business logic relationship between the congestion analysis modules is a road congestion analysis execution program.
  • the MEC management device analyzes the characteristics and geographic area of the road congestion analysis module, and acquires the set of MEC execution devices according to the characteristics of the road congestion analysis module and the geographical area.
  • the MEC management device extracts the road congestion analysis module and the business logic relationship in the service deployment request, and stores the road congestion analysis module in the function module library.
  • the MEC management device analyzes and analyzes the characteristics of the functional module and the business logic relationship, and determines the desired deployment location of the road congestion analysis module. For example, the MEC management device analyzes the characteristics of the road congestion analysis module, which should be deployed to the road, and the desired deployment location is close to "Shenzhen Bulong Road", that is, the road congestion analysis module needs to be deployed to It can cover the MEC equipment of “Brunn Road in Shenzhen”; in one implementation, the roads to be monitored can be segmented, for example, “Bron Road” is divided into M segments, and road congestion analysis modules are deployed according to different road segments. Please refer to FIG. 7 for understanding. FIG. 7 is a schematic diagram of a scenario in the embodiment of the present application.
  • the "Bron Road” includes a road section 1, a road section 2, a road section 3... a road section M, and for the road section 1, the desired deployment position of the road congestion analysis module is (x 1 , y 1 ) and (x 2 , y 2 ); 2.
  • the MEC management device repackages the Lm as a query key into a query request and sends the query request to the open function device.
  • the business logic relationship is a logical relationship between each road congestion analysis module.
  • the road congestion analysis module corresponding to the desired deployment location point (x 1 , y 1 ) deployed by the road segment 1 is the first road congestion analysis module, and the same reason, Deploying a second road congestion analysis module for the desired deployment location point (x 2 , y 2 ); corresponding road segment 2, a desired deployment location point (x 3 , y 3 ) deploying a third road congestion analysis module; corresponding road segment 3, a desired deployment location
  • the point (x 4 , y 4 ) deploys the fourth road congestion analysis module and the like.
  • the direction of the traffic flow is from the road segment 1 to the road segment 5
  • the first road congestion analysis module and the second road congestion analysis are performed.
  • the module is used to analyze the road congestion situation of the road segment 1, and the third road congestion analysis module is used to analyze the road congestion situation of the road segment 2, and for the subsequent road segments, for example, the road congestion situation of the road segment 3 is analyzed for the upper two road segments (ie, the road segment)
  • the analysis result of 1 and the road section 2) has a dependency relationship. Therefore, the business logic relationship between the road congestion analysis modules in this example is a dependency relationship.
  • the open function device parses the query request, extracts the Lm, and obtains the set of the MEC execution device located in the Lm preset range, and the coverage of the MEC execution device includes the geographic area, and obtains the real-time status information of the MEC execution device covering the geographic area and the MEC.
  • the MEC management device receives a set of MEC execution devices sent by the open function device.
  • the MEC management device determines the target MEC execution device according to the location and status information of the MEC execution device.
  • MEC 1 Real-time status information of the MEC execution device (MEC 1 ) of (x 1 ', y 1 ') and real-time status information of the MEC execution device (MEC 2 ) located at (x 2 ', y 2 '), if processing of MEC 1 If the capability is greater than the processing capability of MEC 2 , then MEC 1 is selected as the target MEC execution device.
  • G4 The MEC management device develops a deployment strategy.
  • the MEC management device sends a sub-service deployment request to each target MEC execution device to query whether the road congestion analysis module can be deployed.
  • the target MEC execution device receives the sub-service deployment request, and if it can be deployed, returns the deployment confirmation information to the MEC management device according to the sub-service deployment request.
  • the MEC management device determines the final target MEC execution device according to the received deployment confirmation information, and formulates a deployment policy, where the deployment strategy includes a correspondence between the road congestion analysis module and the target MEC execution device.
  • the MEC management device sends a corresponding road congestion analysis module to the target MEC execution device according to the deployment policy.
  • the MEC management device extracts the road congestion analysis module from the function module library and distributes it to the corresponding target MEC execution device. For example, the first road congestion analysis module is sent to the MEC 1 and the second road congestion analysis module is sent to the MEC 2 .
  • the target MEC execution device receives the road congestion analysis module, and after running the road congestion analysis module, receives the data reported by the terminal (such as the image information acquired by the road surveillance camera), analyzes the data reported by the terminal, and obtains an execution result, and the execution result is obtained. Includes timestamps, congestion information, and geographic location.
  • the target MEC execution device returns an execution result to the deployed MEC management device. For example, the execution result of the MEC 1 feedback is that the vehicle is slow, and the execution result of the MEC 2 feedback is that the vehicle is slow and so on.
  • the MEC management device aggregates the execution results returned by all the target MEC execution devices, obtains the service result, that is, the road congestion situation, and returns the road network congestion situation and the service deployment strategy to the open function device.
  • the result of the business is that the vehicle is slowed down in the first road section and the second road section, and the traffic is blocked in the fourth road section.
  • the overall traffic volume of "Bron Road” is large and the vehicle is slow.
  • G8 Open-function devices return road network congestion in a geographic area to third-party services.
  • the open function device stores the service deployment strategy.
  • the real-time traffic monitoring service is deployed according to the requirements of the user, and the traffic congestion analysis module is deployed to the MEC execution module by using the open function device, the MEC management device, the MEC execution device, and the terminal, thereby implementing the service.
  • the automatic deployment can not only improve the resource utilization of the boundary device, but also improve the processing speed of the road data through the synergy of multiple MEC execution devices.
  • an embodiment of a management device 600 is provided in the embodiment of the present application, including:
  • the first receiving module 601 is configured to receive service description information and service execution information of the service to be deployed sent by the open function device, where the service execution information includes information for executing the service description information.
  • a determining module 602 configured to determine a target MEC execution device
  • the first sending module 603 is configured to send the service description information and the service execution information received by the first receiving module 601 to the target MEC executing device determined by the determining module 602.
  • the second receiving module 607 is configured to receive an execution result of the service execution information sent by the target MEC executing device, where the execution result is obtained by the target MEC executing device according to the service description information and the service execution information.
  • the obtaining module 604 is configured to obtain a service result of the service to be deployed according to the execution result received by the second receiving module 607.
  • the second sending module 605 is configured to send, to the open function device, the service result obtained by the obtaining module 604.
  • the description information includes information about a geographical area of the service to be deployed
  • the determining module 602 is further configured to determine the target MEC execution device according to the feature and geographic area of the service execution information.
  • FIG. 7 another embodiment of the management device 700 is provided on the basis of the embodiment corresponding to FIG.
  • the determining module 602 further includes a determining unit 6021, a sending unit 6022, a receiving unit 6023, and a selecting unit 6024;
  • the determining unit 6021 is further configured to determine, according to a feature of the execution information received by the first receiving module 601, a desired deployment location of the execution information;
  • the sending unit 6022 is configured to send, to the open function device, a desired deployment location determined by the determining unit 6021, where the desired deployment location is used by the open function device to determine a set of MEC execution devices, and the coverage of the set of MEC execution devices includes a geographic region;
  • the receiving unit 6023 is configured to receive a set of MEC executing devices sent by the open function device.
  • the selecting unit 6024 is configured to select a target MEC executing device from the set of MEC executing devices received by the receiving unit 6023.
  • the selecting unit 6024 is further configured to determine a distance between a location of the MEC execution device and a desired deployment location in the set of MEC execution devices; and select a target MEC execution device from the set of MEC execution devices according to the distance.
  • FIG. 8 another embodiment of the management device 800 is provided on the basis of the embodiment corresponding to FIG.
  • the management device further includes an obtaining unit 6025;
  • the obtaining unit 6025 is further configured to acquire state information of the MEC executing device.
  • the selecting unit 6024 is further configured to select the target MEC executing device from the set of MEC executing devices according to the distance and the state information of the MEC executing device.
  • the service execution information includes at least one execution program, and the target MEC executes the device.
  • the number is at least one, the management device further includes a policy formulation module 606;
  • the policy formulation module 606 is configured to formulate a deployment policy, where the deployment policy includes a correspondence between the at least one execution program and the target MEC execution device determined by the at least one determination module 602.
  • the first sending module 603 is further configured to send, to the target MEC executing device, an execution program corresponding thereto according to the correspondence determined by the policy formulation module 606.
  • FIG. 6-9 the management devices in Figures 6-9 are presented in the form of functional modules.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above.
  • ASIC application-specific integrated circuit
  • FIG. 10 the form shown in Figure 10 can be employed in the management device of Figures 6-9.
  • FIG. 10 is a schematic structural diagram of a management device according to an embodiment of the present disclosure.
  • the management device 1000 may generate a large difference due to different configurations or performances, and may include one or more processors 1022 and 1032, one or one.
  • the above storage medium 1030 storing the application 1042 or the data 1044 (for example, one or one storage device in Shanghai).
  • the memory 1032 and the storage medium 1030 may be short-term storage or persistent storage.
  • the program stored on storage medium 1030 may include one or more modules (not shown), each of which may include a series of instruction operations in the management device.
  • the processor 1022 can be configured to communicate with the storage medium 1030 to perform a series of instruction operations in the storage medium 1030 on the management device 1000.
  • Management device 1000 may also include one or more power sources 1026, one or more wired or wireless network interfaces 1050, one or more input and output interfaces 1058, and/or one or more operating systems 1041.
  • the steps performed by the MEC management device in the above method embodiments may be based on the management device structure shown in FIG.
  • the processor 1022 causes the management device to execute the method performed by the MEC management device in the method embodiment corresponding to FIG. 3.
  • an embodiment of an open function device 1100 is provided by an embodiment of the present application, including:
  • the first receiving module 1101 is configured to receive service description information and service execution information of the service server that is to be deployed, where the service execution information includes information for executing the service description information.
  • the first sending module 1102 is configured to send the service description information and the service execution information received by the first receiving module 1101 to the mobile edge computing MEC management device;
  • a determining module 1103, configured to determine a set of MEC execution devices
  • the second sending module 1104 is configured to send the set of MEC executing devices determined by the determining module 1103 to the MEC management device; the set of MEC executing devices is used by the MEC management device to determine the target MEC executing device from the set of MEC devices, and the service execution information
  • the execution result of the service to be deployed is obtained by the target MEC execution device according to the service description information, and the execution result is used by the MEC management device to obtain the service result of the service to be deployed;
  • the second receiving module 1105 is configured to receive a service result of the service to be deployed sent by the MEC management device.
  • FIG. 12 on the basis of the corresponding embodiment of FIG. 11, another embodiment of the open function device 1200 is provided by the present application, including:
  • the service description information includes information about a geographical area of the service to be deployed
  • the open function device further includes a third receiving module 1106;
  • the third receiving module 1106 is configured to receive a desired deployment geographic location sent by the MEC management device, where the desired geographic location is a location to be deployed when the MEC management device executes the service according to the service description information determined by the service description information and the service execution information.
  • the determining module 1103 is further configured to determine a set of MEC executing devices located within a preset range of the desired deployment geographic location received by the third receiving module 1106.
  • the present application provides another embodiment of an open function device 1300 , including: the service description information includes information about a geographical area related to a service,
  • the open function device further includes a selection module 1107;
  • the selection module 1107 is configured to select the MEC management device from the plurality of MEC execution devices, where the coverage of the plurality of MEC execution devices includes the geographical area received by the first receiving module 1101.
  • the selecting module 1107 is further configured to: determine, according to the geographic area, multiple MEC execution devices; acquire state information of the multiple MEC execution devices, where the status information is used to indicate that the MEC performs processing capability of the device; and from multiple MEC execution devices The MEC execution device with the strongest processing capability is selected as the MEC management device, or the open function device selects the MEC execution device whose processing capability is greater than the threshold from among the plurality of MEC execution devices as the MEC management device.
  • another embodiment of the open function device 1400 includes: a third sending module 1108;
  • the third sending module 1108 is configured to send a response to the service server to confirm the deployed service, and the response is used to instruct the service server to send the service execution information of the service to be deployed to the open function device.
  • the embodiment of the present application further provides a computer storage medium for storing computer software instructions used by the management device, which includes a program for executing the MEC management device in the foregoing method embodiment.
  • FIGS. 11-14 are presented in the form of functional modules.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above.
  • ASIC application-specific integrated circuit
  • FIGS. 11-14 can take the form shown in Figure 15.
  • FIG. 15 is a schematic structural diagram of an open function device according to an embodiment of the present disclosure.
  • the open function device 1500 may generate a large difference due to different configurations or performances, and may include one or more processors 1522 and a memory 1532. Or more than one storage medium 1530 storing data 1542 or data 1544 (eg, one or one storage device in Shanghai). Among them, the memory 1532 and the storage medium 1530 may be short-term storage or persistent storage.
  • the program stored on storage medium 1530 may include one or more modules (not shown), each of which may include a series of instruction operations in an open function device. Still further, the processor 1522 can be configured to communicate with the storage medium 1530 to perform a series of instruction operations in the storage medium 1530 on the open function device 1500.
  • the open function device 1500 can also include one or more power sources 1526, one or more wired or wireless network interfaces 1550, one or more input and output interfaces 1558, and/or one or more operating systems 1541.
  • the steps performed by the open function device in the above method embodiments may be based on the open function device structure shown in FIG.
  • the processor 1522 causes the open function device to perform the method performed by the open function device in the above method embodiment.
  • the embodiment of the present application further provides a computer storage medium for storing computer software instructions used by the open function device, which includes a program for executing an open function device in the foregoing method embodiment.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of cells is only a logical function division.
  • multiple units or components may be combined or integrated. Go to another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请实施例公开了一种业务管理的方法及相关设备，本申请实施例方法包括：移动边缘计算MEC管理设备接收开放功能设备发送的待部署业务的业务描述信息和业务执行信息，所述业务执行信息包括执行所述业务描述信息的信息；确定目标MEC执行设备；向所述目标MEC执行设备发送所述业务描述信息和所述业务执行信息；接收所述目标MEC执行设备发送的所述业务执行信息的执行结果,所述执行结果由所述目标MEC执行设备根据所述业务描述信息和所述业务执行信息得到；根据所述执行结果得到所述待部署业务的业务结果；向所述开放功能设备发送所述业务结果，本申请实施例中还提供了一种管理设备和一种开放功能设备，用于自动部署第三方业务。

Description

一种业务管理的方法及相关设备
本申请要求于2018年1月26日提交中国专利局、申请号为201810081437.0、申请名称为“一种业务管理的方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种业务管理的方法及相关设备。
背景技术
分布式计算环境下的业务部署方法，将业务部署到集群上，集群由各种具有计算能力的设备构成，由集群中的设备来共同执行业务，部署业务时，一般根据设备的计算能力及网络带宽来选择集群，例如，选择具有较大计算能力和较大通信能力的设备来部署业务。当前的业务部署方法不适合在移动边缘计算环境下使用。
发明内容
本申请实施例提供了一种业务管理的方法及相关设备，用于自动部署第三方业务，本申请实施例中，基于业务自动部署架构，该架构包括开放功能设备、MEC管理设备、MEC执行设备和终端，该架构为层次化的架构，该架构方便第三方服务在网络边界设备(MEC设备)上快速、自动部署第三方业务，该第三方业务包括但不限定于失联人员搜救业务，实时路况查询等等；通过部署的业务为用户提供高质量的服务，即可以提高MEC设备资源的利用率，又可以为用户提供多样化的业务服务，提高用户体验。
第一方面，本申请实施例提供了一种业务管理的方法，包括：
移动边缘计算MEC管理设备接收开放功能设备发送的待部署业务的业务描述信息和业务执行信息，业务执行信息包括执行业务描述信息的信息；业务描述信息用于对待部署业务的具体描述；该业务执行信息包括至少一个执行程序和业务逻辑关系，该执行程序用于执行该业务对应的功能；该业务逻辑关系为当执行程序为至少两个时，至少两个执行程序之间的关系，该业务逻辑关系包括独立关系和依赖关系；MEC管理设备确定目标MEC执行设备；然后，MEC管理设备向目标MEC执行设备发送业务描述信息和业务执行信息；MEC管理设备接收目标MEC执行设备发送的业务执行信息的执行结果,该执行结果由目标MEC执行设备根据业务描述信息和业务执行信息得到的；MEC管理设备根据执行结果得到待部署业务的业务结果；MEC管理设备向开放功能设备发送业务结果；本申请实施例中，基于MEC设备具有计算，存储和处理能力的特性，第三方服务器在网络边界设备(MEC设备)上快速、自动部署第三方业务，为用户提供多样化的业务服务。
在一种可能的实现方式中，描述信息还包括待部署业务的地理区域的信息，MEC管理设备可以根据业务执行信息的特征和地理区域确定目标MEC执行设备；本申请实施例中基于MEC设备可以具有位置区域的属性，可以向目标执行设备部署对于地理位置较为敏感的业务，适合在在移动边缘计算环境下地理位置敏感的业务。
在一种可能的实现方式中，MEC管理设备根据业务执行信息的特征和地理区域确定MEC 执行设备可以具体包括：MEC管理设备根据执行信息的特征确定执行信息的期望部署位置；MEC管理设备向开放功能设备发送期望部署位置，开放功能设备负责监控所有MEC设备的性能与状态，且开放功能设备存储所有MEC设备的位置信息，期望部署位置用于开放功能设备确定MEC执行设备的集合，MEC执行设备的集合的覆盖范围包括地理区域；然后，MEC管理设备接收开放功能设备确定的MEC执行设备的集合；MEC管理设备从MEC执行设备的集合中选择目标MEC执行设备。
在一种可能的实现方式中，MEC管理设备从MEC执行设备的集合中选择目标MEC执行设备的具体方式可以为：MEC管理设备确定MEC执行设备的集合中MEC执行设备的位置与期望部署位置之间的距离，该距离可以为欧式距离；然后，MEC管理设备按照距离的远近从MEC执行设备的集合中选择目标MEC执行设备，如MEC管理设备选择距离期望部署位置最近的MEC执行设备为目标MEC执行设备，本申请实施例中的方法，基于目标MEC执行设备的地理位置，目标MEC执行设备为适宜部署业务执行信息的MEC设备，方法简便。
在一种可能的实现方式中，进一步的，确定目标MEC执行设备的方法还可以为：MEC管理设备获取MEC执行设备的状态信息；MEC管理设备综合距离和MEC执行设备的状态信息这两个参数，从MEC执行设备的集合中选择目标MEC执行设备，本申请实施例中，不仅考虑到了距离因素，又考虑到了MEC设备的处理能力，通过这两个参数综合选择目标MEC执行设备。
在一种可能的实现方式中，业务执行信息包括至少一个执行程序，目标MEC执行设备的数量为至少一个，MEC管理设备向目标MEC执行设备发送业务描述信息和业务执行信息之前，MEC管理设备可以制定出部署策略，该部署策略包括至少一个执行程序与至少一个目标MEC执行设备的对应关系；然后，MEC管理设备根据对应关系向目标MEC执行设备发送与之对应的执行程序。
第二方面，本申请实施例提供了一种计算机存储介质，用于储存上述MEC管理设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第三方面，本发明实施例提供了一种管理设备，具有实现上述方法中MEC管理设备所执行的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，管理设备的结构中包括存储器，网络接口和处理器。其中存储器用于存储计算机可执行程序代码，并与网络接口耦合。该程序代码包括指令，当该处理器执行该指令时，该指令使该管理设备执行上述方法中MEC管理设备所涉及的信息或者指令。
第五方面，本申请实施例提供了一种业务管理的方法，包括：
开放功能设备接收业务服务器发送待部署业务的业务描述信息和业务执行信息，业务执行信息包括执行业务描述信息的信息；其中，业务服务器，为第三方服务设备，用于向开放功能设备发送待部署业务的业务请求，该业务请求用于向开放功能设备102请求部署业务；例如，该业务可以为失联人员搜救业务，实时路况查询等等；业务请求包括业务描述信息和业务执行信息，业务描述信息用于对待部署业务的具体描述；开放功能设备向移动边缘计算MEC管理设备发送业务描述信息和业务执行信息；开放功能设备确定MEC执行 设备的集合；开放功能设备将MEC执行设备的集合发送至MEC管理设备；MEC执行设备的集合用于MEC管理设备从MEC设备的集合中确定目标MEC执行设备，业务执行信息用于目标MEC执行设备根据业务描述信息得到待部署业务的执行结果，执行结果用于MEC管理设备得到待部署业务的业务结果；开放功能设备接收MEC管理设备发送的待部署业务的业务结果；开放功能设备为业务服务器与MEC管理设备之间的接口设备，用于接收并将业务描述信息和业务执行信息发送给MEC管理设备；本申请实施例中，基于MEC设备具有计算，存储和处理能力的特性，第三方服务器在网络边界设备(MEC设备)上快速、自动部署第三方业务，为用户提供多样化的业务服务。
在一种可能的实现方式中，业务描述信息包括待部署业务的地理区域的信息，开放功能设备确定MEC执行设备集合之前，开放功能设备接收MEC管理设备发送的期望部署地理位置，期望部署地理位置为MEC管理设备根据业务描述信息和业务执行信息确定的业务执行信息执行业务时待部署的位置；开放功能设备负责监控所有MEC设备的性能与状态，且开放功能设备存储所有MEC设备的位置信息，该MEC管理设备向开放功能设备发送查询请求，该查询请求用于查询期望部署位置的附近的MEC执行设备；然后，开放功能设备确定位于期望部署地理位置预置范围内的MEC执行设备的集合。
在一种可能的实现方式中，业务描述信息包括与业务相关的地理区域的信息，开放功能设备向MEC管理设备发送业务描述信息之前，开放功能设备从多个MEC执行设备中选择MEC管理设备，多个MEC执行设备的覆盖范围包括地理区域。
在一种可能的实现方式中，开放功能设备从多个MEC执行设备中选择MEC管理设备具体方式可为：开放功能设备获取业务描述信息中的地理区域的信息，该多个MEC设备的覆盖范围包括地理区域，确定覆盖范围包括地理区域的多个MEC设备，开放功能设备获取多个MEC执行设备的状态信息，状态信息用于指示MEC执行设备的处理能力；开放功能设备从多个MEC执行设备中选择处理能力最强的MEC执行设备作为MEC管理设备，或者，开放功能设备从多个MEC执行设备中选择处理能力大于阈值的MEC执行设备作为MEC管理设备。
附图说明
图1为本申请实施例中的一种通信系统的场景架构示意图；
图2为本申请实施例中的基于MEC的业务部署架构示意图；
图3为本申请实施例中的一种业务管理的方法的一个实施例的步骤流程示意图；
图4为本申请实施例中的一个场景示意图；
图5为本申请实施例中的另一个场景示意图；
图6为本申请实施例中的一种管理设备的一个实施例的结构示意图；
图7为本申请实施例中的一种管理设备的另一个实施例的结构示意图；
图8为本申请实施例中的一种管理设备的另一个实施例的结构示意图；
图9为本申请实施例中的一种管理设备的另一个实施例的结构示意图；
图10为本申请实施例中的一种管理设备的另一个实施例的结构示意图；
图11为本申请实施例中的一种开放功能设备的一个实施例的结构示意图；
图12为本申请实施例中的一种开放功能设备的另一个实施例的结构示意图；
图13为本申请实施例中的一种开放功能设备的另一个实施例的结构示意图；
图14为本申请实施例中的一种开放功能设备的另一个实施例的结构示意图；
图15为本申请实施例中的一种开放功能设备的另一个实施例的结构示意图。
具体实施方式
本申请实施例提供了一种业务管理的方法、相关设备及系统，用于自动部署第三方业务。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
为了方便理解，首先对本申请中涉及的词语进行说明。
移动边缘计算(Mobile Edge Computing，缩写：MEC)：将计算能力下沉到移动通信网络边缘，在网络边缘侧增加计算、存储、处理等功能。
本申请实施例中的MEC设备可以理解为部署到靠近终端位置的网络边缘位置，具有计算，存储和处理能力的设备，MEC设备可以具有位置区域的属性，且距离终端(路旁摄像头等)更近的特性。
本申请实施例中的MEC设备包括MEC管理设备和MEC执行设备，需要说明的是，本申请实施例中的MEC管理设备和MEC执行设备只是在执行业务时，功能上的划分，任一个MEC管理设备可以作为MEC管理设备，也可以作为MEC执行设备。
本申请实施例中提供了一种业务管理的方法，该方法应用于一种通信系统，请参阅图1所示，图1为本申请实施例中一种通信系统的场景架构示意图。该通信系统包括业务服务器101、开放功能设备102、MEC管理设备103、MEC执行设备104和终端105。业务服务器101与开放功能设备102通信连接，开放功能设备102与MEC管理设备103通信连接，开放功能设备102与MEC执行设备104通信连接，MEC管理设备103与MEC执行设备104通信连接，MEC执行设备104与终端105通信连接。
其中，业务服务器101，为第三方服务设备，用于向开放功能设备102发送待部署业务的业务请求，该业务请求用于向开放功能设备102请求部署业务。例如，该业务可以为失联人员搜救业务，实时路况查询等等。业务请求包括业务描述信息和业务执行信息，业务描述信息用于对待部署业务的具体描述，若该待部署业务以失联人员搜救业务为例，该业务 描述信息可以包括失联人员的照片和车牌号码等；该业务执行信息为用于执行与待部署业务相关的执行程序，可以理解为功能模块，例如，人脸识别模块、车辆追踪模块等等。
开放功能设备102，为业务服务器101与MEC管理设备103之间的接口设备，用于接收业务服务器101发送的业务请求，并将业务描述信息和业务执行信息发送给MEC管理设备103，开放功能设备102负责监控所有MEC设备的性能与状态，获取所有MEC设备的地理位置。MEC设备包括MEC管理设备103和MEC执行设备104。接收MEC管理设备103反馈的待部署业务的业务结果，并将该业务结果反馈至业务服务器101。
MEC管理设备103，用于接收开放功能设备102发送的待部署业务的业务描述信息和业务执行信息，可以分析业务需求、收集MEC执行设备104的状态信息、选择将业务部署到MEC执行设备104、将业务描述信息和业务执行信息发送到MEC执行设备104，同时，收集和聚合所有MEC执行设备104的执行结果，获得最终的业务结果，并将该业务结果反馈至开放功能设备102。
MEC执行设备104，用于接收MEC管理设备103发送的业务描述信息和业务执行信息，运行执行程序，根据业务描述信息和终端105上传的数据得到执行结果，并将该执行结果发送至MEC管理设备103。
终端105，包括但不限定于道路监控摄像头，车辆上的车载设备，传感器等等，用于采集数据，并将采集到的数据上传至MEC执行设备104。
本申请实施例中，基于业务自动部署架构，该架构包括开放功能设备、MEC管理设备、MEC执行设备和终端，该架构为层次化的架构，该架构方便第三方服务器在网络边界设备(MEC设备)上快速、自动部署第三方业务，通过部署的业务为用户提供高质量的服务，即可以提高MEC设备资源的利用率，又可以为用户提供多样化的业务服务，提高用户体验。
本申请实施例中利用MEC设备，快捷、高效地部署与管理业务，提供了一种对业务自动部署并管理的方法。
下面对本申请实施例进行详细描述，请结合图2和图3进行理解，图2为本申请实施例中基于MEC的业务部署架构示意图，图3为本申请实施例中提供的一种业务管理的方法的一个实施例的步骤流程示意图。
步骤301、业务服务器向开放功能设备发送待部署业务的业务描述信息和业务执行信息。
业务服务器向开放功能设备发送待部署业务的业务请求，该业务请求包括业务描述信息和业务执行信息。该业务执行信息包括至少一个执行程序和业务逻辑关系，该执行程序用于执行该业务对应的功能；该业务逻辑关系为当执行程序为至少两个时，至少两个执行程序之间的关系，该业务逻辑关系包括独立关系和依赖关系。例如，在一个应用场景中，业务执行信息包括第一执行程序(如面部识别模块)和第二执行程序(如车辆追踪模块)，第一执行程序的结果和第二执行程序的结果没有相关性，也就是说，第一执行程序的执行结果和第二执行程序的执行结果互相不影响，即业务逻辑关系为独立关系。在另一个应用场景中，业务执行信息包括第一道路拥堵分析模块和第二道路拥堵分析模块，第二道路拥堵分析模块的分析结果依赖于第一道路拥堵分析模块的分析结果，即该业务逻辑关系为依 赖关系。需要说明的是，本申请实施例中，对于该业务执行信息中所包括的具体执行程序只是为了方便说明而举的例子，并不造成对本申请的限定性说明。具体的，可以包括如下步骤：
A1：业务服务器向开放功能设备发送待部署业务的业务请求，该业务请求包括业务描述信息；该业务请求用于向开放功能设备请求部署该业务。可选的，该业务描述信息可以包括与该业务相关的地理区域的信息。
A2：开放功能设备接收到该业务请求后，通过部署请求解析器对该业务请求进行解析，得到信息业务描述信息，并向业务服务器反馈响应，该响应用于指示允许部署业务。
A3：业务服务器接收到响应后，向开放功能设备发送业务执行信息，该业务执行信息包括至少一个执行程序，该执行程序用于执行该业务对应的功能。
例如，在一个应用场景中，请结合图4进行理解，图4为本申请实施例中一个场景示意图。业务服务器向开放功能设备发送待部署业务的业务请求，该业务请求为失联人员搜救的请求，该业务描述信息包括失联人员的照片、乘坐车辆的车牌号码和地理区域的信息，该地理区域的信息可以为失联人员可能会去的地方，常去的地方，或者失联前最后出现的地方等等。开放功能设备接收到该查询失联人员的请求后，向业务服务器反馈允许部署的响应，该运行部署信息用于指示业务服务器可以部署该业务，业务服务器接收到该响应后，向开放功能设备发送业务执行信息，例如，该业务执行信息包括第一执行程序和第二执行程序，第一执行程序为面部识别执行程序(本示例中也称为面部识别模块)，用于对失联人员的面部识别，第二执行程序为车辆追踪执行程序(本示例中也称为车辆追踪模块)，用于识别失联人员乘坐的车辆的车牌号码。在本示例中，面部识别模块和车辆追踪模块之间的业务逻辑关系为独立关系。本申请实施例中，待部署的业务为为了方便说明而举的例子，并不造成对本申请的限定性说明。
需要说明的是，若是第三方业务服务器已经向开放功能设备发送过相同的待部署的业务，则不需要像开放功能设备发送业务执行信息，该业务执行信息已经存储至开放功能设备中，例如，业务服务器第一次向开放功能设备发送失联人员搜救业务的请求，业务服务器已经向开放功能设备发送过面部识别模块和车辆追踪模块，则在第二次请求部署失联人员搜救业务时，可以不向开放功能设备发送面部识别模块和车辆最终模块。
步骤302、开放功能设备接收业务描述信息和业务执行信息，并将业务描述信息和业务执行信息向MEC管理设备发送。
B1:开放功能设备接收业务描述信息和业务执行信息后，从多个MEC设备中选择MEC管理设备。
例如，该多个MEC设备包括MEC 0，MEC 1,MEC 2，…MEC 8等等。
在第一种可能的实现方式中，开放功能设备可以从多个MEC设备中指定一个MEC设备作为MEC管理设备。
在第二种可能的实现方式中，开放功能设备监控MEC设备的实时状态信息，该状态信息用于指示MEC设备的处理能力，该实时状态信息包括但不限定于CPU状态，当前负载和当前存储量等等，开放功能设备可以根据MEC设备的实时状态信息选择一个处理能力较强 的MEC设备作为MEC管理设备，或者，开放功能设备从多个MEC执行设备中选择处理能力大于阈值的MEC执行设备作为MEC管理设备。
在第三种可能的实现方式中，开放功能设备获取业务描述信息中的地理区域的信息，该多个MEC设备的覆盖范围包括所述地理区域，确定覆盖范围包括所述地理区域的多个MEC设备，然后根据该多个MEC设备的处理能力从多个MEC设备中选择一个处理能力最强的MEC设备作为MEC管理设备。
例如，在一种应用场景中，业务描述信息中的地理区域为失联人员最后出现的地方为F市L区G街道Q商场门口，开放功能设备确定以该Q商场门口为中心，半径为5000范围内的3个MEC设备，从这3个MEC设备中选择一个处理能力最强的MEC设备作为MEC管理设备。需要说明的是，本示例中，对于选择MEC管理设备的方法只是举例说明，并不造成对本申请的限定性说明。
B2：开放功能设备向MEC管理设备发送所述业务描述信息和业务执行信息。
例如，开放功能设备将失联人员的照片、车牌号码、面部识别模块，车辆追踪模块，及面板识别模块和车辆追踪模块之间的业务逻辑关系发送至MEC管理设备。
步骤303、MEC管理设备接收业务描述信息和业务执行信息，MEC管理设备根据业务描述信息和业务执行信息确定目标MEC执行设备。该MEC管理设备接收到该业务描述信息和业务执行信息后，将业务执行信息包括的执行程序存储于功能模块库中。
具体的，可以包括如下步骤：C1：该MEC管理设备分析执行程序的特征，根据业务执行信息的特征和地理区域确定业务执行信息的期望部署位置。
该MEC管理设备根据执行程序的特征，各执行程序之间的业务逻辑关系及地理区域综合确定执行程序的期望部署位置。本申请实施例中，可以部署对于地理位置较为敏感的业务，适合在在移动边缘计算环境下地理位置敏感、且实时性要求高的业务。
例如，该执行程序还是以面部识别模块和车辆追踪模块为例进行说明，该MEC管理设备分析面部识别模块和车辆追踪模块的特征，如，面部识别模块适合部署到人口密集区，或者可以理解为，将面部识别模块部署到人口密集区更能有效的发挥面部识别模块的功能；而车辆追踪模块适合部署到道路旁，或者可以理解为，将车辆追踪模块部署到道路旁更能有效的发挥车辆追踪模块的功能，该期望部署位置属于该地理区域。本示例中，该各执行程序之间的业务逻辑关系为独立关系，因此，车辆追踪模块和面部识别模块可以分别部署，并不相互影响。
MEC管理设备确定各功能模块期望部署的地理位置。例如，该期望部署位置属于Q商场门口为中心，半径为5000范围内。
C2：MEC管理设备向开放功能设备发送期望部署位置，期望部署位置用于开放功能设备确定MEC执行设备的集合。
MEC执行设备的集合包括至少一个MEC设备，例如，期望部署位置点的集合为Lm＝{(x 1,y 1),…,(x k,y k)}，其中，(x 1,y 1),…,(x k,y k)为期望部署位置的坐标。
C3：MEC管理设备向开放功能设备发送查询请求，该查询请求携带该期望部署位置Lm。
开放功能设备负责监控所有MEC设备的性能与状态，且开放功能设备存储所有MEC设 备的位置信息，该MEC管理设备向开放功能设备发送查询请求，该查询请求用于查询期望部署位置的附近的MEC执行设备。
C4：开放功能设备接收MEC管理设备发送的查询请求，提取期望部署位置Lm。
C5：开放功能设备从节点信息库中查询位于期望部署位置Lm预置范围内的MEC设备，例如，在期望部署位置(x 1,y 1)的预置范围内的MEC设备为MEC 1，期望部署位置(x 2,y 2)的预置范围内的MEC设备为MEC 2和MEC 3等等，需要说明的是，一个期望部署位置预置范围内的MEC设备的数量并不限定，在Lm中每个期望部署位置的预置范围内的MEC设备组成了MEC执行设备的集合，例如，MEC执行设备所在位置的集合为Le＝{(x 1′,y 1′),…,(x n′,y n′)}。
C6：开放功能设备将该MEC执行设备的集合Le发送至MEC管理设备，该MEC执行设备的集合Le也可以理解为初始MEC执行设备的集合。
C7：MEC管理设备接收开放功能设备发送的MEC执行设备的集合Le；
C8：MEC管理设备从MEC执行设备的集合中选择目标MEC执行设备。
在一种可能的实现方式中，MEC管理设备确定MEC执行设备的集合中MEC执行设备的位置与期望部署位置之间的距离；MEC管理设备根据距离从MEC执行设备的集合中选择目标MEC执行设备。
例如，业务执行信息包括N个执行程序，期望地理位置包括N个期望部署位置；N个执行程序中的第i个执行程序与N个期望部署位置中的第i个期望部署位置相对应；MEC管理设备比较期望地理位置中的第i个期望部署位置与MEC执行设备集合中的每个MEC执行设备的地理位置之间的距离，i取遍N中的每一个数值。
若第i个期望部署位置与第j个MEC执行设备之间的距离最短，则MEC管理设备确定第i个期望部署位置与第j个MEC执行设备相匹配。
MEC管理设备建立第i个期望部署位置所对应的第i个执行程序与第j个MEC执行设备的对应关系。
MEC管理设备根据期望部署位置点Lm＝{(x 1,y 1),…,(x k,y k)}以及MEC执行设备的集合Le＝{(x 1′,y 1′),…,(x n′,y n′)}，计算第i个位置点与MEC执行设备的集合中第j个MEC节点之间的距离D ij，选择距离第i个期望部署位置最近的第j个MEC执行设备作为目标MEC执行设备。
在另一个可能的实现方式中，MEC管理设备从开放功能设备获取每个MEC执行设备的实时状态信息；MEC管理设备根据距离和MEC执行设备的实时状态信息从MEC执行设备的集合中选择目标MEC执行设备。该实时状态信息包括但不限定于MEC执行设备的CPU状态，负载情况和存储情况等等。例如，若距离第i个期望部署位置的第j个MEC执行设备的距离为X，距离该第i个期望部署位置的第k个MEC执行设备的距离为Y，而X和Y之间的差异参数小于阈值，可以理解的是，当两个MEC执行设备距离同一个期望部署位置距离的差异较小，则可以进一步根据这两个MEC执行设备的实时状态信息来选择与该第i个期望部署位置相匹配的目标MEC执行设备，例如，当前第k个MEC执行设备的处理能力大于第j个MEC执行设备(记作“MEC j”)的处理能力，则此时选择第k个MEC执行设备(记作“MEC k”) 作为与该第i个期望部署位置相匹配的目标MEC执行设备。
步骤304，MEC管理设备通过管理器制定部署策略，部署策略包括执行程序与目标MEC执行设备的对应关系。
MEC管理设备选择了目标MEC执行设备后，向目标MEC执行设备发送子业务部署请求，例如，MEC管理设备向第k个目标MEC执行设备(MEC k)发送子业务部署请求，该子业务部署请求用于请求部署子业务，即车辆追踪业务，目标MEC执行设备根据该子业务部署请求向MEC管理设备反馈部署确认信息，当MEC管理设备接收到该部署确认信息后，确定该目标MEC执行设备可以执行该子业务，MEC管理设备制定部署策略。
该执行程序的数量为至少一个，该目标MEC执行设备的数量为至少一个，MEC管理设备确定了与第i个期望部署位置相匹配的目标MEC执行设备，MEC管理设备确定了第i个期望部署位置对应的执行程序(如面部识别模块)，便可以确定执行程序与目标MEC执行设备的对应关系，例如，面部识别模块与第j个MEC执行设备(MEC j)，车辆追踪模块与第k个MEC执行设备(MEC k)具有对应关系。
需要说明的是，在实际应用中，执行程序与目标MEC执行设备可以是一对一的关系，可以是一对多的关系，或者也可以是多对一的关系。例如，若执行程序的数量为N个，期望部署位置的数量为N个，N以3为例，执行程序分别为面部识别模块、车辆追踪模块和图像识别模块，面部识别模块的期望部署位置为人口密集区，对应第1个期望位置，而车辆追踪模块的期望部署位置为道路旁，对应第2个期望部署位置，图像识别模块的期望部署位置同样可以为道路旁，对应第3个期望部署位置，根据距离和MEC执行设备的实时状态信息确定与第2个期望部署位置和第3个期望部署位置相匹配的MEC执行设备为MEC k，也就是说，面部识别模块和车辆追踪模块对应第k个MEC执行设备(MEC k)；当然，在另外的情况中，也可能是一个执行程序对应到至少两个MEC执行设备。例如，车辆追踪模块，在识别清晰车牌号时，所需要的资源较小，单个MEC设备可以独立完成，若识别模糊车牌号，计算量较大，需要多个MEC设备协同配合，这样，可以加快识别的速度。需要说明的是，本示例中对于执行程序、执行程序与期望部署位置的对应关系均为举例说明，并不造成对本申请的限定性说明。
步骤305、MEC管理设备向目标MEC执行设备发送业务描述信息和业务执行信息。
MEC管理设备从功能模块库提取执行程序，根据部署策略向目标MEC执行设备发送与之对应的执行程序。
例如，该MEC管理设备将面部识别模块发送至第j个目标执行设备(MEC j)，将车辆追踪模块发送至第k个MEC执行设备(MEC k)。
步骤306、目标MEC执行设备接收MEC管理设备发送的业务描述信息和执行程序，运行该执行程序后，获取终端上报的数据，根据终端上报的数据和该业务描述信息得到执行结果。
例如，在一个应用场景中，其中第j个目标MEC执行设备位于人口密集区，该目标MEC执行设备接收到MEC管理设备发送的失联人员照片和面部识别模块，该目标MEC执行设备运行该面部识别模块，并接收各个终端获取的图像信息(如照片)，面部识别模块将终端上报的照片与失联人员照片进行匹配，得到执行结果，若匹配成功，则该执行结果包括匹配成 功时的时间戳，及终端获取照片的地理位置。若未匹配成功，则该执行结果包括终端获取照片的地理位置及对应的时间戳，虽然没有匹配成功，但是该执行结果指示了在何时何地没有发现失联人员，有助于缩小查找范围，对失联人员的行踪进行下一步排查。再如，第k个目标MEC执行设备位于道路旁，该目标MEC执行设备接收到MEC管理设备发送的车牌号码的照片和车辆追踪模块，该目标MEC执行设备运行该车辆追踪模块，并接收各个终端(如道路监控摄像头)上报的图像信息，车辆追踪模块将接收到的终端上报的照片与待追踪的车辆的车牌号码进行匹配，得到执行结果，若匹配成功，则该执行结果包括匹配成功时的时间戳，及终端获取照片的地理位置。若未匹配成功，则该执行结果包括终端获取照片的地理位置及对应的时间戳。
步骤307、MEC管理设备接收各个目标MEC执行设备发送的执行结果，并通过聚合器对各个目标MEC执行设备的执行结果进行聚合，得到该待部署业务的业务结果。
MEC管理设备接收到各个目标MEC执行设备发送的执行结果后，根据业务逻辑关系对各个目标MEC执行设备的执行结果进行聚合，得到待部署业务的业务结果。
本示例中，面部识别模块和车辆追踪模块这两个执行程序之间的业务逻辑关系是独立的，例如，该业务结果包括：在2018年1月10日12:06分，在P地点发现失联人员，和，在2018年1月10日10:06分，在F地点发现失联人员乘坐的车辆。
步骤308、MEC管理设备将该业务结果发送至开放功能设备。
可选的，该MEC管理设备也可以将业务结果和部署策略发送至开放功能设备，该开放功能设备存储该部署策略。
步骤309、开放功能设备将该待部署业务的业务结果发送至业务服务器。
本申请实施例中，在移动边缘环境下，利用MEC设备实现第三方业务的自动部署，开放功能设备为第三方业务服务器与MEC管理设备之间的接口设备，MEC管理设备接收开放功能设备发送的待部署业务的业务描述信息和业务执行信息，该业务执行信息包括至少一个执行程序，该执行程序用于执行该待部署业务对应的功能，然后，MEC管理设备确定目标MEC执行设备，目标MEC执行设备为具体执行待部署业务的MEC设备；MEC管理设备向目标MEC执行设备发送业务描述信息和业务执行信息；MEC管理设备接收各个目标MEC执行设备发送的业务执行信息的执行结果,MEC管理设备将各个目标MEC执行设备发送的执行结果进行聚合，得到该待部署业务的业务结果，MEC管理设备向开放功能设备发送业务结果，开放功能设备将该业务结果发送至第三方业务服务器。
本示例中，该待部署业务为失联人员搜救业务，实现了两个维度(水平维度和垂直维度)的协同配合，即可以同时进行面部识别和车辆追踪，将不同的执行程序发送到对应的目标MEC执行设备，从而使得多个MEC执行设备之间进行协作。其中，水平维度：部署面部识别模块与车辆追踪模块，两种执行程序所完成的功能不同，面部识别模块可以用于寻找失联人员最近出现的位置与时间，车辆追踪模块用于追踪可疑车辆当前的位置及对应时间，这两种执行程序共同检测失联人员的所在位置及对应的时间。垂直维度：每种功能模块，可能需要多个边界设备协同配合，例如车辆追踪模块识别清晰车牌号时，所需要的资源较小，单个MEC设备可以独立完成，识别模糊车牌号，计算量较大，需要多个MEC设备协同配 合，从而加快识别的速度。本示例中，待部署的业务是实时性要求高且对于位置较为敏感的业务，本申请实施例中通过开放功能设备、MEC管理设备和MEC执行设备的架构可以自动部署第三方业务，而且可以提高MEC设备的资源利用率。MEC设备本地处理其覆盖区域内所有摄像头上传的路况数据，避免大量路况数据传输造成通信拥堵、传输成本高等问题；并且，通过多个MEC执行设备的协同合作，共同完成一个完整的业务，提高了业务执行的效率。
为了更好的理解本申请，下面对本申请所应用的一个具体的应用场景进行详细说明。
请参阅图5所示，图5为本申请实施例中一个场景示意图。
本申请实施例提供的另一个应用场景，该应用场景的待部署业务的业务描述：利用分布式MEC设备具有位置感知的特性，每个MEC设备具有一定的覆盖区域的特性，离终端(路旁摄像头等)更近等特性，在MEC设备上部署实时路况监控的业务，实时处理分析来自路旁摄像头上传的路况数据，获得城市道路当前的拥堵信息(例如，拥堵、拥挤、缓行和畅通等等)，MEC设备通过分析覆盖区域内摄像头上传的路况数据，可以获得覆盖区域内所有道路的拥堵信息；开放功能设备监控所有MEC设备的状态信息，例如，该状态信息包括资源剩余信息、负载信息、CPU状态信息和存储状态信息等。
G1：第三方业务服务器向开放功能设备发送业务部署请求，该业务部署请求携带业务描述信息，该业务描述信息包括地理区域，该地理区域为待监控的路况所在的区域。
开放功能设备接收并解析该业务部署请求，获取地理区域。例如，该业务部署请求为路况实时查询请求，地理区域为“深圳市布龙路”。本示例中地理区域为举例说明，并不造成对本申请的限定性说明。
具体的，开放功能设备查询覆盖区域包括该地理区域内的多个MEC设备，从多个MEC设备中选择一个MEC作为MEC管理设备，开放功能设备选择MEC管理的具体方法可以结合上述实施例中B1步骤进行理解，此处不赘述。
开放功能设备向第三方业务服务器返回响应，该响应用于指示允许部署该路况实时查询业务；
第三方业务服务器接收到该响应后，向开放功能设备发送业务执行信息，例如，该业务执行信息包括道路拥堵分析执行程序(即道路拥堵分析模块)和业务逻辑关系，该业务逻辑关系为各道路拥堵分析模块之间的业务逻辑关系。
G2：MEC管理设备分析道路拥堵分析模块的特征和地理区域，根据路拥堵分析模块的特征和地理区域获取MEC执行设备的集合。
MEC管理设备提取业务部署请求中的道路拥堵分析模块和业务逻辑关系，并将道路拥堵分析模块存储于功能模块库中。
MEC管理设备分析分析功能模块的特征及业务逻辑关系，确定该道路拥堵分析模块的期望部署位置。例如，MEC管理设备分析道路拥堵分析模块的特征，该道路拥堵分析模块应该部署到道路旁，该期望部署位置为靠近“深圳市布龙路”，也就是说，该道路拥堵分析模块需要部署到能够覆盖“深圳市布龙路”的MEC设备上；在一个实现方式中，可以将需要监控的道路进行分段，如将“布龙路”分成M段，根据不同的路段部署道路拥堵分析模块，请结合图7进行理解，图7为本申请实施例中的场景示意图。该“布龙路”包括路段1，路段2， 路段3…路段M，对于路段1，道路拥堵分析模块的期望部署位置为(x 1，y 1)和(x 2，y 2)；对于路段2，道路拥堵分析模块的期望部署位置为(x 3，y 3)和(x 4，y 4)等等，针对每个路段进行分析后，得到期望部署位置的集合Lm＝{(x 1，y 1),…,(x k，y k)}；MEC管理设备将Lm作为查询关键字，重新封装为查询请求，并将该查询请求发送至开放功能设备。该业务逻辑关系为各道路拥堵分析模块之间的逻辑关系，例如，对应路段1部署的期望部署位置点(x 1，y 1)的道路拥堵分析模块为第一道路拥堵分析模块，同理，针对期望部署位置点(x 2，y 2)部署第二道路拥堵分析模块；对应路段2，期望部署位置点(x 3，y 3)部署第三道路拥堵分析模块；对应路段3，期望部署位置点(x 4，y 4)部署第四道路拥堵分析模块等等，此处不一一举例，假设车流的方向为从路段1到路段5，则第一道路拥堵分析模块和第二道路拥堵分析模块用于分析路段1的道路拥堵情况，而第三道路拥堵分析模块用于分析路段2的道路拥堵情况，对于后面的路段，例如路段3的道路拥堵情况的分析对于上两个路段(即路段1和路段2)的分析结果具有依赖关系，因此，本示例中各道路拥堵分析模块之间的业务逻辑关系为依赖关系。
开放功能设备解析查询请求，提取Lm；获取位于Lm预置范围内的MEC执行设备的集合，且MEC执行设备的覆盖范围包括该地理区域，获取覆盖该地理区域MEC执行设备的实时状态信息以及MEC执行设备所在位置L e＝{Le＝{(x 1′,y 1′),…,(x n′,y n′)}；将参与部署的所有MEC执行设备作为初始执行节点集，该初始执行节点集为MEC执行设备的集合，开放功能设备将该MEC执行设备的集合发送至MEC管理设备。MEC管理设备接收开放功能设备发送的MEC执行设备的集合。
G3：MEC管理设备根据MEC执行设备所在位置及状态信息，确定目标MEC执行设备。
根据期望部署位置点Lm＝{(x 1,y 1),…,(x k,y k)}以及MEC执行设备的集合的位置Le＝{(x 1′,y 1′),…,(x n′,y n′)}，计算第i个期望部署位置点与MEC执行设备的集合中第j个MEC执行设备之间的距离Dij，选择距离第i个位置点最近的MEC执行设备，例如，以(x 1，y 1)为例，距离该(x 1，y 1)距离最近的位置点为(x 1′，y 1′)和(x 2′，y 2′)，获取位于(x 1′，y 1′)的MEC执行设备(MEC 1)的实时状态信息和位于(x 2′，y 2′)的MEC执行设备(MEC 2)的实时状态信息，若MEC 1的处理能力大于MEC 2的处理能力，则选择MEC 1为目标MEC执行设备。
G4：MEC管理设备制定部署策略。
具体的，MEC管理设备向每个目标MEC执行设备发送子业务部署请求，询问能否部署道路拥堵分析模块。
目标MEC执行设备接收子业务部署请求，如果可以部署，则根据子业务部署请求向MEC管理设备返回部署确认信息。
MEC管理设备根据接收到的部署确认信息，确定最终的目标MEC执行设备，制定部署策略，该部署策略包括道路拥堵分析模块与目标MEC执行设备的对应关系。
G5：MEC管理设备根据部署策略，向目标MEC执行设备发送对应的道路拥堵分析模块。
MEC管理设备从功能模块库提取道路拥堵分析模块，并分发至对应的目标MEC执行设备。例如，将第一道路拥堵分析模块发送至MEC 1，将第二道路拥堵分析模块发送至MEC 2。
G6：目标MEC执行设备接收道路拥堵分析模块，运行道路拥堵分析模块后，接收终端上 报的数据(如道路监控摄像头获取的图像信息)，对终端上报的数据进行分析，得到执行结果，该执行结果包括时间戳，拥堵信息和地理位置。目标MEC执行设备向部署MEC管理设备返回执行结果。例如，MEC 1反馈的执行结果为车辆缓行，MEC 2反馈的执行结果为车辆缓行等等。
G7：MEC管理设备聚合所有目标MEC执行设备返回的执行结果，获得业务结果，即道路拥堵情况，并向开放功能设备返回路网拥堵情况以及业务部署策略。例如，该业务结果为在第一路段和第二路段车辆缓行，在第四路段拥堵，“布龙路”整体车流量大且车辆缓行。
G8：开放功能设备将地理区域内路网拥堵情况返回至第三方服务。可选的，开放功能设备存储该业务部署策略。
本示例中，在移动边缘环境下，根据用户的需求，部署实时路况监控业务，利用开放功能设备、MEC管理设备、MEC执行设备和终端，向MEC执行模块部署路况拥堵分析模块，从而实现对业务的自动部署，不仅可以提高边界设备的资源利用率，通过多个MEC执行设备的协同作用可以提高对路况数据处理速度。
请参阅图6所示，本申请实施例中提供了一种管理设备600的一个实施例包括：
第一接收模块601，用于接收开放功能设备发送的待部署业务的业务描述信息和业务执行信息，业务执行信息包括执行业务描述信息的信息；
确定模块602，用于确定目标MEC执行设备；
第一发送模块603，用于向确定模块602确定的目标MEC执行设备发送第一接收模块601接收的业务描述信息和业务执行信息；
第二接收模块607，用于接收目标MEC执行设备发送的业务执行信息的执行结果,执行结果由目标MEC执行设备根据业务描述信息和业务执行信息得到；
获取模块604，用于根据第二接收模块607接收的执行结果得到待部署业务的业务结果；
第二发送模块605，用于向开放功能设备发送获取模块604获取的业务结果。
可选的，描述信息包括待部署业务的地理区域的信息；
确定模块602，还用于根据业务执行信息的特征和地理区域确定目标MEC执行设备。
参阅图7所示，在图6对应的实施例的基础上，本申请实施例还提供了一种管理设备700的另一个实施例包括：
确定模块602还包括确定单元6021，发送单元6022，接收单元6023和选择单元6024；
确定单元6021，还用于根据第一接收模块601接收的执行信息的特征确定执行信息的期望部署位置；
发送单元6022，用于向开放功能设备发送确定单元6021确定的期望部署位置，期望部署位置用于开放功能设备确定MEC执行设备的集合，MEC执行设备的集合的覆盖范围包括地理区域；
接收单元6023，用于接收开放功能设备发送的MEC执行设备的集合；
选择单元6024，用于从接收单元6023接收的MEC执行设备的集合中选择目标MEC执行设备。
可选的，选择单元6024，还用于确定MEC执行设备的集合中MEC执行设备的位置与期望部署位置之间的距离；根据距离从MEC执行设备的集合中选择目标MEC执行设备。
参阅图8所示，在图7对应的实施例的基础上，本申请实施例还提供了一种管理设备800的另一个实施例包括：
管理设备还包括获取单元6025；
获取单元6025，还用于获取MEC执行设备的状态信息；
选择单元6024，还用于根据距离和MEC执行设备的状态信息从MEC执行设备的集合中选择目标MEC执行设备。
参阅图9所示，在图6对应的实施例的基础上，本申请实施例还提供了一种管理设备900的另一个实施例包括：业务执行信息包括至少一个执行程序，目标MEC执行设备的数量为至少一个，管理设备还包括策略制定模块606；
策略制定模块606，用于制定部署策略，部署策略包括至少一个执行程序与至少一个确定模块602确定的目标MEC执行设备的对应关系；
第一发送模块603，还用于根据策略制定模块606确定的对应关系向目标MEC执行设备发送与之对应的执行程序。
进一步的，图6-图9中的管理设备是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，图6-图9中的管理设备中可以采用图10所示的形式。
图10是本申请实施例提供的一种管理设备的结构示意图，该管理设备1000可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上处理器1022和存储器1032，一个或一个以上存储应用程序1042或数据1044的存储介质1030(例如一个或一个以上海量存储设备)。其中，存储器1032和存储介质1030可以是短暂存储或持久存储。存储在存储介质1030的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对管理设备中的一系列指令操作。更进一步地，处理器1022可以设置为与存储介质1030通信，在管理设备1000上执行存储介质1030中的一系列指令操作。
管理设备1000还可以包括一个或一个以上电源1026，一个或一个以上有线或无线网络接口1050，一个或一个以上输入输出接口1058，和/或，一个或一个以上操作系统1041。
上述方法实施例中由MEC管理设备所执行的步骤可以基于图10所示的管理设备结构。
处理器1022使管理设备执行图3对应的方法实施例中MEC管理设备所执行的方法。
请参阅图11所示，本申请实施例提供了一种开放功能设备1100的一个实施例包括：
第一接收模块1101，用于接收业务服务器发送待部署业务的业务描述信息和业务执行信息，业务执行信息包括执行业务描述信息的信息；
第一发送模块1102，用于向移动边缘计算MEC管理设备发送第一接收模块1101接收的业务描述信息和业务执行信息；
确定模块1103，用于确定MEC执行设备的集合；
第二发送模块1104，用于将确定模块1103确定的MEC执行设备的集合发送至MEC管 理设备；MEC执行设备的集合用于MEC管理设备从MEC设备的集合中确定目标MEC执行设备，业务执行信息用于目标MEC执行设备根据业务描述信息得到待部署业务的执行结果，执行结果用于MEC管理设备得到待部署业务的业务结果；
第二接收模块1105，用于接收MEC管理设备发送的待部署业务的业务结果。
请参阅图12所示，在图11对应的实施例的基础上，本申请提供了一种开放功能设备1200的另一个实施例包括：
业务描述信息包括待部署业务的地理区域的信息；
开放功能设备还包括第三接收模块1106；
第三接收模块1106，用于接收MEC管理设备发送的期望部署地理位置，期望部署地理位置为MEC管理设备根据业务描述信息和业务执行信息确定的业务执行信息执行业务时待部署的位置；
确定模块1103，还用于确定位于第三接收模块1106接收的期望部署地理位置预置范围内的MEC执行设备的集合。
请参阅图13所示，在图11对应的实施例的基础上，本申请提供了一种开放功能设备1300的另一个实施例包括：业务描述信息包括与业务相关的地理区域的信息，
开放功能设备还包括选择模块1107；
选择模块1107，用于从多个MEC执行设备中选择MEC管理设备，多个MEC执行设备的覆盖范围包括第一接收模块1101接收的地理区域。
可选的，选择模块1107，还用于根据地理区域确定多个MEC执行设备；获取多个MEC执行设备的状态信息，状态信息用于指示MEC执行设备的处理能力；从多个MEC执行设备中选择处理能力最强的MEC执行设备作为MEC管理设备，或者，开放功能设备从多个MEC执行设备中选择处理能力大于阈值的MEC执行设备作为MEC管理设备。
请参阅图14所示，在图11对应的实施例的基础上，本申请提供了一种开放功能设备1400的另一个实施例包括：还包括第三发送模块1108；
第三发送模块1108，用于向业务服务器发送确认部署业务的响应，响应用于指示业务服务器向开放功能设备发送待部署业务的业务执行信息。本申请实施例还提供了一种计算机存储介质，用于储存上述管理设备所用的计算机软件指令，其包含用于执行上述方法实施例中MEC管理设备所执行的程序。
进一步的，图11-图14中的开放功能设备是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，图11-图14中的开放功能设备可以采用图15所示的形式。
图15是本申请实施例提供的一种开放功能设备的结构示意图，该开放功能设备1500可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上处理器1522和存储器1532，一个或一个以上存储应用程序1542或数据1544的存储介质1530(例如一个或一个以上海量存储设备)。其中，存储器1532和存储介质1530可以是短暂存储或持久存储。存 储在存储介质1530的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对开放功能设备中的一系列指令操作。更进一步地，处理器1522可以设置为与存储介质1530通信，在开放功能设备1500上执行存储介质1530中的一系列指令操作。
开放功能设备1500还可以包括一个或一个以上电源1526，一个或一个以上有线或无线网络接口1550，一个或一个以上输入输出接口1558，和/或，一个或一个以上操作系统1541。
上述方法实施例中由开放功能设备所执行的步骤可以基于该图15所示的开放功能设备结构。处理器1522使开放功能设备执行上述方法实施例中开放功能设备所执行的方法。
本申请实施例还提供了一种计算机存储介质，用于储存上述开放功能设备所用的计算机软件指令，其包含用于执行上述方法实施例中开放功能设备所执行的程序。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (24)

  1. 一种业务管理的方法，其特征在于，包括：
    移动边缘计算MEC管理设备接收开放功能设备发送的待部署业务的业务描述信息和业务执行信息，所述业务执行信息包括执行所述业务描述信息的信息；
    所述MEC管理设备确定目标MEC执行设备；
    所述MEC管理设备向所述目标MEC执行设备发送所述业务描述信息和所述业务执行信息；
    所述MEC管理设备接收所述目标MEC执行设备发送的所述业务执行信息的执行结果,所述执行结果由所述目标MEC执行设备根据所述业务描述信息和所述业务执行信息得到；
    所述MEC管理设备根据所述执行结果得到所述待部署业务的业务结果；
    所述MEC管理设备向所述开放功能设备发送所述业务结果。
  2. 根据权利要求1所述的方法，其特征在于，所述描述信息包括所述待部署业务的地理区域的信息，所述MEC管理设备确定目标MEC执行设备，包括：
    所述MEC管理设备根据所述业务执行信息的特征和所述地理区域确定所述目标MEC执行设备。
  3. 根据权利要求2所述的方法，其特征在于，所述MEC管理设备根据所述业务执行信息的特征和所述地理区域确定所述MEC执行设备，包括：
    所述MEC管理设备根据所述执行信息的特征确定所述执行信息的期望部署位置；
    所述MEC管理设备向所述开放功能设备发送所述期望部署位置，所述期望部署位置用于所述开放功能设备确定MEC执行设备的集合，所述MEC执行设备的集合的覆盖范围包括所述地理区域；
    所述MEC管理设备接收所述开放功能设备发送的MEC执行设备的集合；
    所述MEC管理设备从所述MEC执行设备的集合中选择所述目标MEC执行设备。
  4. 根据权利要求3所述的方法，其特征在于，所述MEC管理设备从所述MEC执行设备的集合中选择目标MEC执行设备，包括：
    所述MEC管理设备确定所述MEC执行设备的集合中MEC执行设备的位置与所述期望部署位置之间的距离；
    所述MEC管理设备根据所述距离从所述MEC执行设备的集合中选择所述目标MEC执行设备。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述MEC管理设备获取所述MEC执行设备的状态信息；
    所述MEC管理设备根据所述距离从所述MEC执行设备的集合中选择所述目标MEC执行设备，包括：
    所述MEC管理设备根据所述距离和所述MEC执行设备的状态信息从所述MEC执行设备的集合中选择所述目标MEC执行设备。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述业务执行信息包括至少一个执行程序，所述目标MEC执行设备的数量为至少一个，所述MEC管理设备向所述目标 MEC执行设备发送所述业务描述信息和所述业务执行信息之前，所述方法还包括：
    所述MEC管理设备制定部署策略，所述部署策略包括所述至少一个执行程序与至少一个所述目标MEC执行设备的对应关系；
    所述MEC管理设备向所述目标MEC执行设备发送所述业务描述信息和所述业务执行信息，包括：
    所述MEC管理设备根据所述对应关系向所述目标MEC执行设备发送与之对应的执行程序。
  7. 一种业务管理的方法，其特征在于，包括：
    开放功能设备接收业务服务器发送待部署业务的业务描述信息和业务执行信息，所述业务执行信息包括执行所述业务描述信息的信息；
    所述开放功能设备向移动边缘计算MEC管理设备发送所述业务描述信息和业务执行信息；
    所述开放功能设备确定MEC执行设备的集合；
    所述开放功能设备将所述MEC执行设备的集合发送至所述MEC管理设备；所述MEC执行设备的集合用于所述MEC管理设备从所述MEC设备的集合中确定目标MEC执行设备，所述业务执行信息用于所述目标MEC执行设备根据所述业务描述信息得到所述待部署业务的执行结果，所述执行结果用于所述MEC管理设备得到所述待部署业务的业务结果；
    所述开放功能设备接收所述MEC管理设备发送的所述待部署业务的业务结果。
  8. 根据权利要求7所述的方法，其特征在于，所述业务描述信息包括所述待部署业务的地理区域的信息，所述开放功能设备确定MEC执行设备集合之前，所述方法还包括：
    所述开放功能设备接收所述MEC管理设备发送的期望部署地理位置，所述期望部署地理位置为所述MEC管理设备根据所述业务描述信息和所述业务执行信息确定的所述业务执行信息执行所述业务时待部署的位置；
    所述开放功能设备确定MEC执行设备的集合，包括：
    所述开放功能设备确定位于所述期望部署地理位置预置范围内的MEC执行设备的集合。
  9. 根据权利要求7所述的方法，其特征在于，所述业务描述信息包括与所述业务相关的地理区域的信息，所述开放功能设备向所述MEC管理设备发送所述业务描述信息之前，所述方法还包括：
    所述开放功能设备从多个MEC执行设备中选择MEC管理设备，所述多个MEC执行设备的覆盖范围包括所述地理区域。
  10. 根据权利要求9所述的方法，其特征在于，所述开放功能设备从多个MEC执行设备中选择MEC管理设备，包括：
    所述开放功能设备根据所述地理区域确定多个MEC执行设备；
    所述开放功能设备获取所述多个MEC执行设备的状态信息，所述状态信息用于指示所述MEC执行设备的处理能力；
    所述开放功能设备从所述多个MEC执行设备中选择处理能力最强的MEC执行设备作为 MEC管理设备，或者，所述开放功能设备从所述多个MEC执行设备中选择处理能力大于阈值的MEC执行设备作为MEC管理设备。
  11. 一种管理设备，其特征在于，包括：
    第一接收模块，用于接收开放功能设备发送的待部署业务的业务描述信息和业务执行信息，所述业务执行信息包括执行所述业务描述信息的信息；
    确定模块，用于确定目标MEC执行设备；
    第一发送模块，用于向所述确定模块确定的所述目标MEC执行设备发送第一接收模块接收的所述业务描述信息和所述业务执行信息；
    第二接收模块，用于接收所述目标MEC执行设备发送的所述业务执行信息的执行结果,所述执行结果由所述目标MEC执行设备根据所述业务描述信息和所述业务执行信息得到；
    获取模块，用于根据所述第二接收模块接收的执行结果得到所述待部署业务的业务结果；
    第二发送模块，用于向所述开放功能设备发送所述获取模块获取的所述业务结果。
  12. 根据权利要求11所述的管理设备，其特征在于，所述描述信息包括所述待部署业务的地理区域的信息；
    所述确定模块，还用于根据所述业务执行信息的特征和所述地理区域确定所述目标MEC执行设备。
  13. 根据权利要求12所述的管理设备，其特征在于，所述确定模块还包括确定单元，发送单元，接收单元和选择单元；
    所述确定单元，还用于根据所述执行信息的特征确定所述执行信息的期望部署位置；
    所述发送单元，用于向所述开放功能设备发送所述确定单元确定的所述期望部署位置，所述期望部署位置用于所述开放功能设备确定MEC执行设备的集合，所述MEC执行设备的集合的覆盖范围包括所述地理区域；
    所述接收单元，用于接收所述开放功能设备发送的MEC执行设备的集合；
    所述选择单元，用于从所述接收单元接收的所述MEC执行设备的集合中选择目标MEC执行设备。
  14. 根据权利要求13所述的管理设备，其特征在于，
    所述选择单元，还用于确定所述MEC执行设备的集合中MEC执行设备的位置与所述期望部署位置之间的距离；根据所述距离从所述MEC执行设备的集合中选择目标MEC执行设备。
  15. 根据权利要求14所述的管理设备，其特征在于，还包括获取单元；
    所述获取单元，用于获取所述MEC执行设备的状态信息；
    所述选择单元，还用于根据所述距离和所述MEC执行设备的状态信息从所述MEC执行设备的集合中选择目标MEC执行设备。
  16. 根据权利要求11至15中任一项所述的管理设备，其特征在于，所述业务执行信息包括至少一个执行程序，所述目标MEC执行设备的数量为至少一个，所述管理设备还包括策略制定模块；
    所述策略制定模块，用于制定部署策略，所述部署策略包括所述至少一个执行程序与至少一个所述确定模块确定的所述目标MEC执行设备的对应关系；
    所述第一发送模块，还用于根据所述策略制定模块确定的所述对应关系向所述目标MEC执行设备发送与之对应的执行程序。
  17. 一种开放功能设备，其特征在于，包括：
    第一接收模块，用于接收业务服务器发送待部署业务的业务描述信息和业务执行信息，所述业务执行信息包括执行所述业务描述信息的信息；
    第一发送模块，用于向移动边缘计算MEC管理设备发送所述第一接收模块接收的所述业务描述信息和业务执行信息；
    确定模块，用于确定MEC执行设备的集合；
    第二发送模块，用于将所述确定模块确定的所述MEC执行设备的集合发送至所述MEC管理设备；所述MEC执行设备的集合用于所述MEC管理设备从所述MEC设备的集合中确定目标MEC执行设备，所述业务执行信息用于所述目标MEC执行设备根据所述业务描述信息得到所述待部署业务的执行结果，所述执行结果用于所述MEC管理设备得到所述待部署业务的业务结果；
    第二接收模块，用于接收所述MEC管理设备发送的所述待部署业务的业务结果。
  18. 根据权利要求17所述的开放功能设备，其特征在于，所述业务描述信息包括所述待部署业务的地理区域的信息，所述开放功能设备还包括第三接收模块；
    所述第三接收模块，用于接收所述MEC管理设备发送的期望部署地理位置，所述期望部署地理位置为所述MEC管理设备根据所述业务描述信息和所述业务执行信息确定的所述业务执行信息执行所述业务时待部署的位置；
    所述确定模块，还用于确定位于所述第三接收模块接收的期望部署地理位置预置范围内的MEC执行设备的集合。
  19. 根据权利要求17所述的开放功能设备，其特征在于，所述业务描述信息包括与所述业务相关的地理区域的信息，还包括选择模块；
    所述选择模块，用于从多个MEC执行设备中选择MEC管理设备，所述多个MEC执行设备的覆盖范围包括所述第一接收模块接收的所述地理区域。
  20. 根据权利要求19所述的开放功能设备，其特征在于，
    所述选择模块，还用于根据所述地理区域确定多个MEC执行设备；获取所述多个MEC执行设备的状态信息，所述状态信息用于指示所述MEC执行设备的处理能力；从所述多个MEC执行设备中选择处理能力最强的MEC执行设备作为MEC管理设备，或者，所述开放功能设备从所述多个MEC执行设备中选择处理能力大于阈值的MEC执行设备作为MEC管理设备。
  21. 一种管理设备，其特征在于，包括：
    存储器，用于存储计算机可执行程序代码；
    网络接口，以及
    处理器，与所述存储器和所述网络接口耦合；
    其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述管理设备执行如权利要求1至6中任一项所述的方法。
  22. 一种计算机存储介质，其特征在于，用于储存管理设备所用的计算机软件指令，其包含用于执行如权利要求1至6中任一项所述的方法。
  23. 一种开放功能设备，其特征在于，包括：
    存储器，用于存储计算机可执行程序代码；
    网络接口，以及
    处理器，与所述存储器和所述网络接口耦合；
    其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述开放功能设备执行如权利要求7至10中任一项所述的方法。
  24. 一种计算机存储介质，其特征在于，用于储存开放功能设备所用的计算机软件指令，其包含用于执行如权利要求7至10中任一项所述的方法。
PCT/CN2018/123459 2018-01-26 2018-12-25 一种业务管理的方法及相关设备 WO2019144746A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18902113.2A EP3720091A4 (en) 2018-01-26 2018-12-25 SERVICE MANAGEMENT PROCEDURES AND RELATED DEVICES
US16/938,756 US20200358673A1 (en) 2018-01-26 2020-07-24 Service management method and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810081437.0A CN110086844A (zh) 2018-01-26 2018-01-26 一种业务管理的方法及相关设备
CN201810081437.0 2018-01-26

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/938,756 Continuation US20200358673A1 (en) 2018-01-26 2020-07-24 Service management method and related device

Publications (1)

Publication Number Publication Date
WO2019144746A1 true WO2019144746A1 (zh) 2019-08-01

Family

ID=67395792

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/123459 WO2019144746A1 (zh) 2018-01-26 2018-12-25 一种业务管理的方法及相关设备

Country Status (4)

Country Link
US (1) US20200358673A1 (zh)
EP (1) EP3720091A4 (zh)
CN (1) CN110086844A (zh)
WO (1) WO2019144746A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112399388B (zh) 2019-08-13 2024-06-14 中兴通讯股份有限公司 一种实现边缘计算的方法、装置和系统
CN112217691A (zh) * 2020-02-19 2021-01-12 杜义平 基于云平台的网络诊断处理方法及装置
CN114189431B (zh) * 2020-08-25 2024-06-07 中国移动通信有限公司研究院 边缘计算业务的配置方法及装置
CN112203290B (zh) * 2020-09-30 2022-07-22 中国联合网络通信集团有限公司 Mec节点部署位置确定方法和mec节点部署装置
KR20220065409A (ko) * 2020-11-13 2022-05-20 삼성전자주식회사 에지 컴퓨팅 서비스를 수행하는 전자 장치 및 전자 장치의 동작 방법
CN112799763A (zh) * 2021-01-28 2021-05-14 深圳希施玛数据科技有限公司 一种函数管理方法、管理装置、终端设备及可读存储介质
CN114844865A (zh) * 2021-01-30 2022-08-02 华为技术有限公司 一种算力感知网络中的服务标识分配方法及通信装置
CN115379420A (zh) * 2021-05-21 2022-11-22 华为技术有限公司 用于执行感知任务的通信方法及通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101741885A (zh) * 2008-11-19 2010-06-16 珠海市西山居软件有限公司 分布式系统及分布式系统处理任务流的方法
CN107172666A (zh) * 2017-04-28 2017-09-15 武汉星耀科技有限公司 在移动终端切换通信小区时保持其本地业务的方法及装置
CN107404733A (zh) * 2017-08-22 2017-11-28 山东省计算中心（国家超级计算济南中心） 一种基于mec和分层sdn的5g移动通信方法及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107018534A (zh) * 2016-01-28 2017-08-04 中兴通讯股份有限公司 一种实现移动边缘计算服务的方法、装置及系统
CN107172664B (zh) * 2016-03-07 2020-04-03 大唐移动通信设备有限公司 数据传输方法、装置及系统
CN107172111B (zh) * 2016-03-07 2020-05-05 大唐移动通信设备有限公司 一种数据传输方法、装置及系统
CN107566437B (zh) * 2016-07-01 2020-04-14 大唐移动通信设备有限公司 信息传输方法及装置
CN106059777B (zh) * 2016-08-23 2019-02-15 浪潮电子信息产业股份有限公司 一种云平台的可信中间件设计方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101741885A (zh) * 2008-11-19 2010-06-16 珠海市西山居软件有限公司 分布式系统及分布式系统处理任务流的方法
CN107172666A (zh) * 2017-04-28 2017-09-15 武汉星耀科技有限公司 在移动终端切换通信小区时保持其本地业务的方法及装置
CN107404733A (zh) * 2017-08-22 2017-11-28 山东省计算中心（国家超级计算济南中心） 一种基于mec和分层sdn的5g移动通信方法及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Annexure ETSI MEC analysis", 3GPP TSG-SA WG6 MEETING #17, S 6-170700, vol. SA WG6, 12 May 2017 (2017-05-12), XP051290224 *
See also references of EP3720091A4

Also Published As

Publication number Publication date
CN110086844A (zh) 2019-08-02
US20200358673A1 (en) 2020-11-12
EP3720091A4 (en) 2020-11-18
EP3720091A1 (en) 2020-10-07

Similar Documents

Publication Publication Date Title
WO2019144746A1 (zh) 一种业务管理的方法及相关设备
Narayanan et al. Lumos5G: Mapping and predicting commercial mmWave 5G throughput
US11330511B2 (en) Method and system for multi-access edge computing (MEC) selection and load balancing
Farris et al. Federated edge-assisted mobile clouds for service provisioning in heterogeneous IoT environments
US11483739B2 (en) Method and system for automated dynamic network slice deployment using artificial intelligence
EP3306987A1 (en) Method and system for instantiating a logical network slice for use with an operator-maintained network portion
Iellamo et al. Placement of 5G drone base stations by data field clustering
KR102300124B1 (ko) 코어 vms와 엣지 vms를 구비한 모바일 엣지 컴퓨팅 기반의 영상 관제 시스템
JP2018055663A (ja) クラウド型高度交通制御システムに基づく協同制御方法および装置
KR20210088303A (ko) 무선 통신 시스템에서 네트워크 트래픽을 수집하는 방법 및 장치
Tang et al. An offloading approach in fog computing environment
Chen et al. Key technologies related to C-V2X applications
EP3619937A1 (en) Cellular network management based on automatic social-data acquisition
Ahmed et al. Predicting high delays in mobile broadband networks
US11678290B2 (en) Wireless connection monitoring, classification, and priority
JP7458377B2 (ja) フォグベースのデータ処理を有効にするためのデータサンプルテンプレート（Ｄａｔａ Ｓａｍｐｌｅ Ｔｅｍｐｌａｔｅ：ＤＳＴ）管理
CN116074199B (zh) 6g空天地场景细粒度按需服务方法
US20200260320A1 (en) Ble-based location services in high density deployments
Tang et al. Application of sensor-cloud systems: smart traffic control
CN114895701A (zh) 一种无人机巡检方法及系统
CN110312202B (zh) 一种用户搜索方法、装置、系统和存储介质
Yang et al. An optimized environment-adaptive computation offloading strategy for real-time cross-camera task in edge computing networks
CN214507243U (zh) 车辆监视装置和系统
Isravel et al. Reliable Surveillance Tracking System based on Software Defined Internet of Things
US20230239721A1 (en) Information processing apparatus, information processing method, and non-transitory storage medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18902113

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018902113

Country of ref document: EP

Effective date: 20200701

NENP Non-entry into the national phase

Ref country code: DE