WO2019100266A1 - 移动边缘主机服务通知方法和装置 - Google Patents

移动边缘主机服务通知方法和装置 Download PDF

Info

Publication number
WO2019100266A1
WO2019100266A1 PCT/CN2017/112378 CN2017112378W WO2019100266A1 WO 2019100266 A1 WO2019100266 A1 WO 2019100266A1 CN 2017112378 W CN2017112378 W CN 2017112378W WO 2019100266 A1 WO2019100266 A1 WO 2019100266A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile edge
service
host
edge platform
platform
Prior art date
Application number
PCT/CN2017/112378
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 PCT/CN2017/112378 priority Critical patent/WO2019100266A1/zh
Priority to EP17932687.1A priority patent/EP3703337B1/en
Priority to CN201780096776.XA priority patent/CN111345008B/zh
Publication of WO2019100266A1 publication Critical patent/WO2019100266A1/zh
Priority to US16/879,361 priority patent/US11432137B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/04—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • the present invention relates to the field of communications, and in particular, to a service notification method and apparatus for a mobile edge host.
  • Mobile edge computing provides users with cloud-based capabilities on the wireless network side close to mobile users, which users can use to deploy applications at the edge of the network.
  • Mobile edge computing can also provide real-time wireless network information (such as user location, base station load, etc.), which allows users to develop differentiated applications.
  • cloud computing capabilities By deploying cloud computing capabilities to the edge of the network, you can create a carrier-class service environment with high performance, low latency and high bandwidth to accelerate the distribution and download of various content, services and applications in the network, so that consumers can enjoy higher Quality network experience.
  • Ultra-low latency services are sensitive to delays, and both the transmission path and the forwarding node increase latency.
  • Mobile edge computing enables content and services to be deployed close to users, and the transmission path has fewer short forwarding nodes. Therefore, mobile edge computing is a necessary condition for ultra-low service implementation. Typical scenes of car networking, industrial control, telemedicine, virtual reality / augmented reality, etc.
  • the near-end deployment of mobile edge computing (such as the mobile edge host shown in Figure 1) enables the processing of large bandwidth traffic to be close, which can greatly reduce the impact of large bandwidth on the backbone network.
  • Typical scenes include live broadcasts of stadiums, live concerts, and distribution of mobile content.
  • the European Telecommunications Standardization Organization defines a reference architecture for mobile edge computing in its specification ETSI GS MEC 003.
  • the architecture consists of two main components: the mobile edge host and the mobile edge management system.
  • the mobile edge host includes a mobile edge platform and a virtualized infrastructure that provides virtualized compute, storage, and network resources for mobile edge applications, and mobile edge applications deployed as virtual machines or containers on mobile edge hosts.
  • a mobile edge platform is also deployed on each mobile edge host, which includes some public services, such as terminal location services, wireless network information services, DNS servers or DNS proxy services, etc., which can be used by mobile edge applications.
  • the mobile edge management system includes a mobile edge orchestrator, a mobile edge platform manager, a virtualized infrastructure manager, and the like.
  • the mobile edge orchestrator maintains an overall view of all mobile edge hosts, available resources, available mobile edge services in the mobile edge system, triggering instantiation and termination of the application.
  • the Mobile Edge Platform Manager is used to manage the mobile edge platform, manage the lifecycle of mobile edge applications, manage application flow rules and DNS rules.
  • the Virtualization Infrastructure Manager manages the virtualized resources required for mobile edge applications.
  • Mobile edge applications such as car networking applications, Internet of Things applications, video caching applications, etc.
  • applications can have multiple copies, become application instances, and are deployed on different mobile edge hosts.
  • Terminal devices such as smart cars, IoT devices, mobile phones, etc. access these application instances through the access network of the telecom operator.
  • Some applications can provide certain capabilities for other applications, providers of capabilities are called services, and services can have multiple instances.
  • a car network application needs to know the specific location of the vehicle, and the location application can provide the specific location of the vehicle, providing the ability to locate the specific location of the vehicle, then the location application is the provider of the location service; the vehicle networking application calls the location service, then the location Service consumers.
  • one or more location service instances can be deployed on each mobile edge host.
  • the mobile edge platform on the mobile edge host provides service registration and discovery.
  • Mobile edge applications and services can register their own services with the mobile edge platform, as well as query the information of other services from the mobile edge platform and subscribe to the status of other services to the mobile edge platform.
  • the embodiment of the present invention provides a service notification method and device, so that a service on a mobile edge host cannot provide services for some reasons, and does not affect the normal operation of the application instance on the mobile edge host. .
  • a service notification method provided by the embodiment of the present invention is used for a first mobile edge host and a second mobile edge host, where the first mobile edge host includes a first mobile edge platform and a first application instance, and the second mobile edge host includes a first Second mobile edge platform,
  • the first mobile edge platform receives a service registration message from the first application instance
  • the first mobile edge platform sends a service notification message to the second mobile edge platform.
  • the service registration message carries a service usage indication identifier, where the indication identifier indicates whether the service can be used by an application instance on another mobile edge host;
  • the first mobile edge platform sends a service notification message to the second mobile edge platform according to the identifier.
  • the method before the first mobile edge platform receives the service registration message from the first application instance, the method includes: the first mobile edge platform receives a service availability subscription message sent by the second mobile edge platform to the first mobile edge platform; or The first mobile edge platform pre-configures the second mobile edge platform as an object to receive the service notification message.
  • the second mobile edge host further includes a second application instance, where the method includes:
  • the second application instance sends a service availability subscription message to the second mobile edge primary platform
  • the second mobile edge platform After receiving the service notification message sent by the first mobile edge platform, the second mobile edge platform sends a service notification message to the second application instance.
  • the service availability subscription message sent by the second application instance to the second mobile edge platform includes a location constraint identifier indicating that the second application instance subscribes to the availability of services running on the first and second mobile edge hosts.
  • An embodiment of the present invention provides another service notification method, where the method is used by a first mobile edge host, where the first mobile edge host includes a first mobile edge platform, a first application instance, and other application instances.
  • the first mobile edge platform receives a service registration message from the first application instance; the service registration message carries a service usage indication identifier, the indication identifier indicating whether the service can be used by an application instance on another mobile edge host;
  • the first mobile edge platform sends a service notification message to other application instances that are subscribed to service availability within the first mobile edge host.
  • the method is further configured for a second mobile edge host, the second mobile edge host includes a second mobile edge platform, and the method includes:
  • the second mobile edge platform sends a service availability subscription message to the first mobile edge platform
  • the first mobile edge platform determines whether to send a service notification message to the second mobile edge platform on the second mobile edge host according to the indication identifier.
  • the embodiment of the invention provides a mobile edge host, including a mobile edge platform, a first application instance, and other application examples.
  • the first application instance is used to send a service registration message to the mobile edge platform, where the service registration message carries the service Using an indication identifier indicating whether the service can be used by an application instance on another mobile edge host;
  • the mobile edge platform is used to send service notification messages to other application instances that are subscribed to service availability within the mobile edge host.
  • An embodiment of the present invention provides a mobile edge communication system, including a first mobile edge host and a second mobile edge host, where the first mobile edge host includes a first mobile edge platform and a first application instance, and the second mobile edge host includes a first Second mobile edge platform,
  • the first mobile edge platform is configured to receive a service registration message from the first application instance
  • the first mobile edge platform is configured to send a service notification message to the second mobile edge platform.
  • the service registration message carries a service usage indication identifier, the indication identifier indicating whether the service can be used by an application instance on another mobile edge host.
  • the first mobile edge platform is configured to send a service notification message to the second mobile edge platform according to the identifier.
  • Embodiments of the present invention provide a computer readable storage medium storing executable program instructions for executing the method steps described above when the executable program instructions are executed.
  • Embodiments of the present invention also provide a computer program product for performing the method steps described above when the computer product is executed.
  • an application instance on a mobile edge host can not only discover and use services on the mobile edge host where it is located, but also discover and use services on other mobile edge hosts, even on the mobile edge host. If the service is faulty, you can also use the services on other mobile edge hosts to ensure that the applications on the mobile edge host are working properly. In addition, it is not necessary to deploy a service instance on each edge host to realize sharing of different mobile edge host resources, thereby saving resources.
  • FIG. 1 is a schematic diagram of a mobile version of an edge host deployed in the prior art
  • FIG. 3 is a schematic diagram of a full interconnection mode of a host cluster according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a hierarchical registration mode of a host cluster according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a service notification method in a single mobile edge host according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a service notification method between different mobile edge hosts according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a mobile edge host according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a mobile edge communication system according to an embodiment of the present invention.
  • FIG. 9 is a hardware diagram of a mobile edge host in accordance with an embodiment of the present invention.
  • the embodiment of the invention provides a host cluster composed of adjacent mobile edge hosts, and hosts in the cluster exchange relevant information that the host can provide various services.
  • hosts in the cluster exchange relevant information that the host can provide various services.
  • each mobile edge platform or part of the mobile edge platform stores address information of other mobile edge platforms in the cluster, and can communicate with other mobile edge platforms. After the mobile edge platform starts, it first queries the other mobile edge platforms in the cluster for the service information registered on these platforms, and then subscribes to the service availability change notification to other mobile edge platforms in the cluster.
  • Service availability changes include service registration and changes in service status, where changes in service status include changing from "available" to "unavailable” or from "unavailable” to “available.”
  • the central service registration discovery function is deployed in each cluster as shown in FIG.
  • the service registers and publishes the status of the service to the mobile edge platform of the mobile edge host.
  • the local mobile edge platform registers with the central service registration discovery function, publishes the status of the local service, and subscribes to services registered on other mobile edge platforms.
  • the central service registration discovery feature saves all information within the cluster that can be used by applications on other mobile edge hosts and can respond to queries and subscription requests from the mobile edge platform. In extreme cases, all mobile edge hosts are in a single cluster, and there is only one central service registration feature in the system.
  • the mobile edge platform on the mobile edge host can store related information of different services located on different mobile edge hosts.
  • the related information may include information about whether the service instance is deployed on the same mobile edge host as the mobile edge platform, and the address, version, instance status, category, and the like of the service instance.
  • Specific information can refer to the following table:
  • Embodiment 1 provides a service notification method in a single mobile edge host, that is, how an application instance in a single mobile edge host discovers a service in the platform, as follows:
  • the first mobile edge host includes a first mobile edge platform, a first application instance, and other application examples.
  • the other application instance sends a service availability event subscription request to the first mobile edge platform.
  • the subscription request carries a filter condition of the subscription event, which may be a service instance identifier, a service name, a service category, a service status, a location constraint identifier of the service, or a combination of these attributes, the location constraint identifier indicating that the application instance only subscribes to run locally.
  • the local host refers to the mobile edge host where the application instance that sends the subscription request is located. In this embodiment, the local host refers to the first mobile edge host.
  • the first mobile edge platform sends a response message indicating that the subscription request is accepted.
  • the service instance provided by the first application instance is deployed, and after first being available, sends a service registration message to the first mobile edge platform, registers the service instance, and provides a service externally.
  • the registration message carries the service name, service category, service version, and transmission information used by the service.
  • the registration message carries a service usage indication identifier indicating whether the service instance can only be used by an application on the mobile edge host.
  • the first mobile edge platform registers the service instance in the service registration discovery function and saves whether the service instance can only be used for the indication identifier used by the application on the mobile edge host. Whether the service instance can only be used by the application on the mobile edge host can also be described in the descriptor of the application providing the service, and is sent by the mobile edge platform manager to the first mobile during the application instantiation process. The edge platform is saved by the first mobile edge platform.
  • the first mobile edge platform identifies an application instance that subscribes to the service state, in this embodiment, other application instances.
  • the first mobile edge platform sends a service availability notification to the other application instance, where the information of the service instance is included, the information of the service instance includes one or more of the following information: service name, service version, service category , service status, transmission information used by the service, whether the service instance can only be used by the application on the mobile edge host, whether the service instance and the application instance subscribed to the service status run on the same mobile edge host .
  • subsequent application instances may send a service availability query request to the first mobile edge platform.
  • the query request includes a service location constraint identifier indicating whether other application instances only query instances of services running on the local host. Service service.
  • the first mobile edge platform sends a reply message to other application instances. If the location constraint identifier in the previous step indicates that the other application instance only queries the instance of the service running on the local host, the response message contains only the information of the service instance running on the first mobile edge host. If the location constraint identifier in the previous step instructs other application instances to query instances of all services, the response message contains both the information of the service instance running on the first mobile edge host and the other mobile edge hosts (such as the second). Instance information for the service on the mobile edge host).
  • the information of the service instance includes one or more of the following information: a service name, a service version, a service category, a service status, transmission information used by the service, and whether the service instance can only be used by an application on the mobile edge host.
  • the first application instance sends a service update message to the first mobile edge platform
  • the first mobile edge platform receives the service update message and sends a service update notification message to other application instances that are subscribed to the service availability located in the first mobile edge platform.
  • Another application instance When another application instance receives the service availability notification or the service query response message, it selects a service instance to initiate the call in the list of available service instances. When an application instance finds that a service instance is "unavailable”, it will be removed from the list of available service instances. When a service instance changes from "unavailable” to "available”, the application instance adds the service instance to the list of available service instances.
  • Another embodiment 2 below provides a service notification method between different mobile edge hosts, that is, how the application instance in the mobile edge host discovers services in other mobile edge hosts, as follows:
  • the first mobile edge host and the second mobile edge host are included, where the first mobile edge host includes a first mobile edge platform and a first application instance, and the second mobile edge host includes a second mobile edge platform and The second application example.
  • the other application instance sends a service availability event subscription request to the first mobile edge platform
  • the second application instance sends a service availability event subscription request to the second mobile edge platform.
  • the subscription request carries a filter condition for the subscription event, which may be a service instance identifier, a service name, a service category, a service status, a location constraint identifier of the service, or a combination of these attributes.
  • the location constraint identifier indicates whether the application instance only subscribes to the availability of instances of services running on the local host, or to the availability of instances of all services, including service instances running on other mobile edge hosts.
  • the first mobile edge platform and the second mobile edge platform respectively send a response message indicating that the subscription request is accepted.
  • the second mobile edge platform sends a service availability event subscription request to the first edge.
  • the subscription request carries a filter condition for the subscription event, which may be a service instance identifier, a service name, a service category, a service status, a location constraint identifier of the service, or a combination of these attributes.
  • the location constraint identifier indicates that only the availability of an instance of the service running on the first mobile edge host is subscribed.
  • the first mobile edge platform sends a response message to the second mobile edge platform, indicating that the subscription request is accepted.
  • the configuration may be configured on the first mobile edge platform by other means, such as by configuration. Which mobile edge platforms need to send notification messages when the service is registered or when the availability of the service changes.
  • the service instance provided by the first application instance is deployed, and after first being available, sends a service registration message to the first mobile edge platform, registers the service instance, and provides services externally.
  • the registration message carries the service name, service category, service version, and transmission information used by the service.
  • the registration message carries a service usage indication identifier indicating whether the service instance can only be used by an application on the mobile edge host.
  • the indication flag indicates that the service can be used by application instances on other mobile edge hosts.
  • the first mobile edge platform registers the service instance in the service registration discovery function and saves whether the service instance can only be used for the indication identifier used by the application on the mobile edge host. Whether the service instance can only be used by the application on the mobile edge host can also be described in the descriptor of the application providing the service, and is sent by the mobile edge platform manager to the first mobile during the application instantiation process. The edge platform is saved by the first mobile edge platform.
  • the first mobile edge platform identifies an application instance that subscribes to the service state, which in this embodiment is another application instance.
  • the first mobile edge platform sends a service availability notification to other application instances indicating that a new service instance is available.
  • the first mobile edge platform determines, according to the indication identifier in the foregoing step, whether the service instance can be used by an application instance on another mobile edge host. If so, the first mobile edge platform identifies an associated mobile edge platform that subscribes to the service state, and the mobile edge platform identified in this embodiment is the second mobile edge platform.
  • the first mobile edge platform sends a service availability notification to the second mobile edge platform indicating that the service instance is available.
  • An identifier may be carried in the message, indicating that the location of the service instance is non-local, that is, the service instance is from a non-local The second mobile edge host.
  • the second mobile edge platform registration service instance identifies the location of the service instance as non-local and sends a service notification to the local application instance that subscribed to the service status and can use the non-local service.
  • the second mobile edge platform sends a response message to the first mobile edge platform.
  • the second mobile edge platform sends a service availability notification to the second application instance indicating that the new service instance is available.
  • the second application instance is an application instance located on the second mobile edge host that satisfies the service state in step 612 and can use the non-local service condition.
  • the second application instance sends a response message to the second mobile edge platform.
  • other application instances that are subsequently located on the first mobile edge host may send a service availability query request to the first mobile edge platform.
  • a service location constraint identifier is included in the query request, the location constraint identifier indicating whether other application instances only query instances of services running on the local host.
  • the first mobile edge platform sends a response message to the other application instance, where the response message includes information of the new service instance. If the location constraint identifier in the previous step indicates that the other application instance only queries the instance of the service running on the local host, the response message contains only the information of the service instance running on the first mobile edge host. If the location constraint identifier in the previous step instructs other application instances to query instances of all services, the response message contains both the information of the service instance running on the first mobile edge host and the other mobile edge hosts (such as the second). Instance information for the service on the mobile edge host).
  • the information of the service instance includes one or more of the following information: a service name, a service version, a service category, a service status, transmission information used by the service, and whether the service instance can only be used by an application on the mobile edge host.
  • the subsequent second application instance may send a query service availability query request to the second mobile edge platform.
  • the query request includes a service location constraint identifier indicating whether the second application instance queries only instances of services running on the local host.
  • the second mobile edge platform sends a response message to the second application instance. If the location constraint identification parameter in step 618 indicates that the second application instance only queries an instance of the service running on the local host, then there is no information for any service instance in the response message. If the location constraint identification parameter in step 618 indicates that the second application instance queries the service instance located on all mobile edge hosts, the response message contains information of the service instance in the above step.
  • the information of the service instance includes one or more of the following information: a service name, a service version, a service category, a service status, transmission information used by the service, and whether the service instance can only be used by an application on the mobile edge host. The identity of the service, and whether the service instance runs on the same mobile edge host as the application that subscribes to the service state.
  • the first application instance sends a service update message to the first mobile edge platform; similar to the registration process, the first mobile edge platform receives the service update message. Sending a service update notification message to the second mobile edge platform on the second mobile edge host, and sending a service update notification message to other application instances subscribed to the service availability located in the first mobile edge platform.
  • the second application instance selects a service instance to initiate the call in the list of available service instances.
  • a service instance finds that a service instance is "unavailable”, it will be removed from the list of available service instances.
  • a service instance changes from "unavailable” to "available” the application instance adds the service instance to the list of available service instances.
  • Embodiment 2 is applicable to the full interconnection mode, and also to the hierarchical registration mode. If it is a hierarchical registration In this manner, the messages sent by the first mobile edge platform and the second mobile edge platform are mutually transited by the central service registration discovery function, which can avoid the interconnection of different mobile edge hosts in the full interconnection mode, thereby reducing the complexity of the connection. degree.
  • the application instance on the mobile edge host can not only discover and use the service on the mobile edge host where it is located, but also discover and use services on other mobile edge hosts, such as the second in the foregoing embodiment.
  • the second application instance on the mobile edge host can discover the service provided by the first application instance located on the first mobile edge host. Therefore, even if the service on the mobile edge host fails, the services on other mobile edge hosts can be used to ensure that the applications on the mobile edge host are running normally. In addition, it is not necessary to deploy a service instance on each edge host to realize sharing of different mobile edge host resources, thereby saving resources.
  • FIG. 7 is a mobile edge host according to an embodiment of the present invention, which may be used to perform various steps performed by a mobile edge host in the foregoing various methods, where the mobile edge host may include a mobile edge platform, a first application instance, and other Application example, mainly,
  • the first application instance is configured to send a service registration message to the first mobile edge platform, where the service registration message carries a service usage indication identifier, where the indication identifier indicates whether the service can be used by an application instance on another mobile edge host;
  • the first mobile edge platform is configured to send a service notification message to other application instances that are subscribed to service availability within the first mobile edge host.
  • the first mobile edge platform determines, according to the indication identifier, whether to send a service notification message to a mobile edge platform on another mobile edge host.
  • the indication identifier indicates that the service cannot be used by an application instance on another mobile edge host
  • the first mobile edge platform determines to not send a service notification message to a mobile edge platform on another mobile edge host according to the indication identifier.
  • the indication identifier indicates that the service can be used by an application instance on another mobile edge host
  • the first mobile edge platform determines to send a service notification to other mobile edge platforms on other mobile edge hosts according to the indication identifier. Message.
  • the precondition for the transmission is that the other mobile edge host has previously sent a service availability subscription message to the first mobile edge platform or configured to move to the other mobile when the service registration or status change is configured on the first mobile edge platform.
  • Other mobile edge platforms on the edge host send notification messages.
  • an embodiment of the present invention further provides a mobile edge communication system, including a first mobile edge host and a second mobile edge host, where the system is configured to perform the first and second movements in Embodiment 2 above.
  • a mobile edge communication system including a first mobile edge host and a second mobile edge host, where the system is configured to perform the first and second movements in Embodiment 2 above.
  • the various steps performed by the edge host primarily,
  • the first mobile edge host includes a first mobile edge platform and a first application instance
  • the second mobile edge host includes a second mobile edge platform.
  • the first mobile edge platform is configured to receive a service registration message from the first application instance
  • the first mobile edge platform sends a service notification message to the second mobile edge platform
  • the service registration message carries a service usage indication identifier, where the indication identifier indicates that the service can be used by an application instance on another mobile edge host; the first mobile edge platform is configured to perform a second according to the identifier The mobile edge platform sends a service notification message.
  • the first mobile edge platform before the first mobile edge platform receives the service registration message from the first application instance, the first mobile edge platform is configured to receive a service availability subscription message sent by the second mobile edge platform to the first mobile edge platform; or first The mobile edge platform pre-configures the second mobile edge platform as an object to receive the service notification message.
  • FIG. 9 is a hardware diagram of a mobile edge host according to another embodiment of the present invention, where the mobile edge master can package Includes: processor, communication interface, and memory.
  • the processor 91 may include one or more processing units, which may be a central processing unit (CPU) or a network processor (NP).
  • processing units may be a central processing unit (CPU) or a network processor (NP).
  • CPU central processing unit
  • NP network processor
  • the communication interface 94 is used for connection and information exchange with other communication devices, including receiving and transmitting corresponding messages; the network device 90 may further include a memory 93, and the processor 91 may be connected to the memory 93 and the communication interface 94 via a bus.
  • Memory 93 can be used to store software programs that can be executed by processor 91 to implement the method steps in the embodiments shown in Figures 5 and 6.
  • the memory 93 can also store various types of service data or user data, including various application examples and status data of the service in the above method steps.
  • the network device 90 may further include an output device 95 and an input device 97.
  • Output device 95 and input device 97 are coupled to processor 91.
  • the output device 95 can be a display for displaying information, a power amplifier device for playing sound, or a printer, etc.
  • the output device 95 can also include an output controller for providing output to a display screen, a power amplifier device, or a printer.
  • the input device 97 may be a device such as a mouse, a keyboard, an electronic stylus or a touch panel for inputting information by the user, and the input device 97 may further include an output controller for receiving and processing from the mouse, the keyboard, the electronic Input from devices such as stylus or touch panel.
  • an embodiment of the present invention further provides a computer program product and a storage medium storing the above computer program.
  • the computer program product includes program code stored in a computer readable storage medium, and the program code is loaded by a processor to implement the above method.

Abstract

本发明实施例公开了一种服务通知方法以及移动边缘主机，所述方法用于第一移动边缘主机和第二移动边缘主机，其中第一移动边缘主机包括第一移动边缘平台和第一应用实例，第二移动边缘主机包括第二移动边缘平台，第一移动边缘平台接收第二移动边缘平台向第一移动边缘平台发送的服务可用性订阅消息，以及接收来自第一应用实例的服务注册消息，然后第一移动边缘平台向第二移动边缘平台发送服务通知消息。通过上述方法，本移动边缘主机上即使存在服务故障，也可以使用其他移动边缘主机上的服务，从而保证本移动边缘主机上的应用正常运行。

Description

移动边缘主机服务通知方法和装置 技术领域
本发明涉及通信领域，尤其涉及一种移动边缘主机的服务通知方法和装置。
背景技术
移动边缘计算是在靠近移动用户的无线网络侧为用户提供基于云计算的能力，用户可以采用该能力在网络边缘部署应用。移动边缘计算还可以提供实时的无线网络信息(如用户位置、基站负载等)，采用这些信息，用户可以开发差异化的应用。将云计算能力部署到网络边缘后，可以创造出一个具备高性能、低延迟与高带宽的电信级服务环境，加速网络中各项内容、服务及应用的分发和下载，让消费者享有更高质量网络体验。
超低时延的业务对延迟很敏感，而传输路径和转发节点都会增加时延。移动边缘计算使内容和业务靠近用户部署，传输路径短转发节点少，因此移动边缘计算是超低业务实现的必要条件。典型场景车联网、工业控制、远程医疗、虚拟现实/增强现实等。
对于超大带宽的业务，通过移动边缘计算(如图1所示的移动边缘主机)的就近部署，使超大带宽流量就近处理，能极大减轻大带宽对骨干网络的冲击。典型场景如体育馆比赛直播、演唱会直播、移动内容分发等。
欧洲电信标准化组织(ETSI)在其规范ETSI GS MEC 003中定义了移动边缘计算的参考架构，如图2所示，架构主要由两部分组成：移动边缘主机和移动边缘管理系统。移动边缘主机包含移动边缘平台和虚拟化基础设施，虚拟基础设施为移动边缘应用提供虚拟化的计算、存储和网络资源，移动边缘应用以虚拟机或者容器的形式部署在移动边缘主机上。每个移动边缘主机上还部署了移动边缘平台，该平台中包含了一些公共服务，如终端位置服务、无线网络信息服务、DNS服务器或者DNS代理服务等等，移动边缘应用可以使用这些公共服务。移动边缘管理系统包含移动边缘编排器、移动边缘平台管理器、虚拟化基础设施管理器等。移动边缘编排器维护移动边缘系统中所有的移动边缘主机、可用资源、可用移动边缘服务的总体视图，触发应用的实例化和终结。移动边缘平台管理器用于管理移动边缘平台、管理移动边缘应用的生命周期、管理应用的流规则和DNS规则。虚拟化基础设施管理器管理移动边缘应用所需的虚拟化资源。
移动边缘应用(以下简称应用)，如车联网应用、物联网应用、视频缓存应用等，可以有多个副本，成为应用实例，分别部署在不同移动边缘主机上。终端设备如智能汽车、物联网设备、手机等通过电信运营商的接入网络就近访问这些应用实例。某些应用可以提供某些能力为其他应用所消费，能力的提供者称为服务，服务也可以有多个实例。例如车联网应用需要知道车辆的具体位置，而位置应用可以提供车辆的具体位置,提供了定位车辆具体位置的能力，那么位置应用是位置服务的提供者；车联网应用调用位置服务，则是位置服务的消费者。另外，每个移动边缘主机上可以部署一个或者多个位置服务实例。
移动边缘主机上的移动边缘平台提供服务注册和发现功能。移动边缘应用和服务可以向移动边缘平台注册自己所能提供的服务，也可以从移动边缘平台查询其他服务的信息，以及向移动边缘平台订阅其他服务的状态。
在当前的移动边缘系统架构中，应用或者服务只能发现其所在移动边缘主机上的服 务。如果本移动边缘主机上的服务由于某些原因(如软件Bug、服务所在VM故障)不能提供服务，就会影响应用的运行，甚至业务的中断。
发明内容
为解决上述技术问题，本发明实施例提供了一种服务通知方法及装置，使得一个移动边缘主机上的服务由于某些原因不能提供服务，不会影响该移动边缘主机上的应用实例的正常运行。
本发明实施例提供的一种服务通知方法用于第一移动边缘主机和第二移动边缘主机，其中第一移动边缘主机包括第一移动边缘平台和第一应用实例，第二移动边缘主机包括第二移动边缘平台，
第一移动边缘平台接收来自第一应用实例的服务注册消息；
第一移动边缘平台向第二移动边缘平台发送服务通知消息。
所述服务注册消息携带服务使用指示标识，所述指示标识指示该服务是否能被其他移动边缘主机上的应用实例所使用；
所述第一移动边缘平台根据所述标识向第二移动边缘平台发送服务通知消息。
另外，在第一移动边缘平台接收来自第一应用实例的服务注册消息之前，所述方法包括：第一移动边缘平台接收第二移动边缘平台向第一移动边缘平台发送的服务可用性订阅消息；或第一移动边缘平台预先配置第二移动边缘平台作为接收所述服务通知消息的对象。
进一步地，所述第二移动边缘主机还包括第二应用实例，所述方法包括：
第二应用实例向第二移动边缘主平台发送服务可用性订阅消息；
第二移动边缘平台接收到第一移动边缘平台发送的服务通知消息后，向所述第二应用实例发送服务通知消息。
所述第二应用实例向第二移动边缘平台发送的服务可用性订阅消息包括位置约束标识，所述标识指示第二应用实例订阅运行在第一和第二移动边缘主机上的服务的可用性。
本发明实施例提供了另一种服务通知方法，所述方法用于第一移动边缘主机，其中第一移动边缘主机包括第一移动边缘平台、第一应用实例和其他应用实例，
第一移动边缘平台接收来自第一应用实例的服务注册消息；所述服务注册消息携带服务使用指示标识，所述指示标识指示该服务是否能被其他移动边缘主机上的应用实例所使用；
第一移动边缘平台向位于第一移动边缘主机内的其他订阅了服务可用性的应用实例发送服务通知消息。
所述方法还用于第二移动边缘主机，所述第二移动边缘主机包括第二移动边缘平台，所述方法包括：
第二移动边缘平台向第一移动边缘平台发送服务可用性订阅消息；
所述第一移动边缘平台根据所述指示标识确定是否向第二移动边缘主机上的第二移动边缘平台发送服务通知消息。
本发明实施例提供了一种移动边缘主机，包括移动边缘平台、第一应用实例和其他应用实例，
第一应用实例用于向移动边缘平台发送服务注册消息，所述服务注册消息携带服务 使用指示标识，所述指示标识指示该服务是否能被其他移动边缘主机上的应用实例所使用；
移动边缘平台用于向位于移动边缘主机内的其他订阅了服务可用性的应用实例发送服务通知消息。
本发明实施例提供了一种移动边缘通信系统，包括第一移动边缘主机和第二移动边缘主机，第一移动边缘主机包括第一移动边缘平台和第一应用实例，第二移动边缘主机包括第二移动边缘平台，
第一移动边缘平台用于接收来自第一应用实例的服务注册消息；
第一移动边缘平台用于向第二移动边缘平台发送服务通知消息。
所述服务注册消息携带服务使用指示标识，所述指示标识指示该服务是否能被其他移动边缘主机上的应用实例所使用。
所述第一移动边缘平台用于根据所述标识向第二移动边缘平台发送服务通知消息。
本发明实施例提供了一种计算机可读存储介质，该计算机可读存储介质存储有可执行程序指令，所述可执行程序指令被运行时，用于执行上面所述的方法步骤。
本发明实施例还提供了一种计算机程序产品，当该计算机产品被执行时，用于执行上面所述的方法步骤。
通过以上实施例提供的方法和装置，移动边缘主机上的应用实例不仅可以发现并使用其所在移动边缘主机上的服务，也可以发现并使用其他移动边缘主机上的服务，即使本移动边缘主机上的服务故障，也可以使用其他移动边缘主机上的服务，从而保证本移动边缘主机上的应用正常运行。另外，可以不必要在每一个边缘主机上都部署服务实例，实现各个不同的移动边缘主机资源共享，节约了资源。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是现有技术一种就近部署的移动版边缘主机示意图；
图2是现有技术一种移动边缘计算参考架构图；
图3是本发明实施例主机集群的全互联方式示意图；
图4是本发明实施例主机集群的分层注册方式示意图；
图5是本发明实施例单个移动边缘主机内的服务通知方法流程图；
图6是本发明实施例不同移动边缘主机之间的服务通知方法流程图；
图7是本发明实施例移动边缘主机结构示意图；
图8是本发明实施例移动边缘通信系统示意图；
图9是本发明实施例移动边缘主机硬件图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例提供了一种相邻的移动边缘主机构成的主机集群，集群内的主机之间交换本主机所能提供各种服务的相关信息。主机集群的互联方式主要有如下两种：
一、全互联方式
如图3所示，每个移动边缘平台或部分移动边缘平台保存集群内其他移动边缘平台的地址信息，可以和其他移动边缘平台联通。移动边缘平台启动后首先向集群内其他移动边缘平台查询注册在这些平台上的服务信息，然后再向集群内其他移动边缘平台订阅服务可用性变化通知。服务可用性变化包括服务注册和服务状态的变化，其中服务状态的变化包括从“可用”变为“不可用”，或从“不可用”变为“可用”。
二、分层注册方式
如图4所示在每个集群内部署中心服务注册发现功能。服务向本移动边缘主机的移动边缘平台注册、发布服务的状态。本地的移动边缘平台向中心服务注册发现功能注册、发布本地服务的状态、订阅注册在其他移动边缘平台上的服务。中心服务注册发现功能保存集群内的所有可以为其他移动边缘主机上的应用所使用的服务的信息，并可以响应移动边缘平台的查询和订阅请求。在极端情况下，所有移动边缘主机都在一个集群内，此时系统内只有一个中心服务注册功能。
通过上述方式，移动边缘主机上的移动边缘平台可以保存位于不同移动边缘主机的不同服务的相关信息。例如，所述相关信息可以包括该服务实例是否和本移动边缘平台部署在同一移动边缘主机上，以及服务实例的地址、版本、实例状态、类别等信息。具体信息可以参考下表：
移动边缘平台保存的各种服务的相关信息：
Figure PCTCN2017112378-appb-000001
下面实施例1提供了单个移动边缘主机内的服务通知方法，即单个移动边缘主机内的应用实例如何发现本平台内的服务的流程，具体如下：
实施例1：
请参考图5，图中第一移动边缘主机包括第一移动边缘平台、第一应用实例和其他应用实例。
501.其他应用实例向第一移动边缘平台发送服务可用性事件订阅请求。订阅请求携带订阅事件的过滤条件，这些过滤条件可以是服务实例标识、服务名称、服务类别、服务状态、服务的位置约束标识或者这些属性的组合，该位置约束标识指示应用实例只订阅运行在本地主机的服务的实例的可用性，还是订阅所有服务(包括运行在其他移动边缘主机上的服务实例)的实例的可用性。其中，本地主机是指发出订阅请求的应用实例所在的移动边缘主机，在本实施例中本地主机是指第一移动边缘主机。
502.第一移动边缘平台发送应答消息，表示接受了订阅请求。
503.第一应用实例所提供的服务实例部署完成、首次可用后向第一移动边缘平台发送服务注册消息，注册服务实例，对外提供服务。在注册消息中携带服务名称、服务类别、服务版本、服务使用的传输信息。另外，该注册消息携带服务使用指示标识，该指示标识指示所述服务实例是否只能为本移动边缘主机上的应用所使用。
504.第一移动边缘平台在服务注册发现功能中注册服务实例，并保存该服务实例是否只能为本移动边缘主机上的应用所使用的指示标识。服务实例是否只能为本移动边缘主机上的应用所使用的标识也可以在提供该服务的应用的描述符中进行描述，在应用实例化过程中由移动边缘平台管理器下发给第一移动边缘平台，由第一移动边缘平台保存。
505.第一移动边缘平台识别订阅了该服务状态的应用实例，在该实施例中为其他应用实例。
506.第一移动边缘平台向其他应用实例发送服务可用性通知，在该通知中包含服务实例的信息，所述服务实例的信息包括以下信息的一种或多种：服务名称、服务版本、服务类别、服务状态、服务使用的传输信息、该服务实例是否只能为本移动边缘主机上的应用所使用的标识、该服务实例是否和订阅该服务状态的应用实例运行在同一移动边缘主机上的标识。
507.其他应用实例给第一移动边缘平台发送应答消息。
508.可选地，后续其他应用实例可以向第一移动边缘平台发送服务可用性查询请求。所述查询请求包括服务位置约束标识，该位置约束标识指示其他应用实例是否只查询运行在本地主机的服务的实例。服务服务。
509.第一移动边缘平台向其他应用实例发送应答消息。如果上一步中的位置约束标识指示其他应用实例只查询运行在本地主机的服务的实例，则应答消息中仅包含运行在第一移动边缘主机上的服务实例的信息。如果上一步中的位置约束标识指示其他应用实例查询所有服务的实例，则应答消息中既包含运行在第一移动边缘主机上的服务实例的信息，也包含运行在其他移动边缘主机(如第二移动边缘主机)上的服务的实例信息。所述服务实例的信息包括以下信息的一种或多种：服务名称、服务版本、服务类别、服务状态、服务使用的传输信息、该服务实例是否只能为本移动边缘主机上的应用所使用的标识、以及该服务实例是否和订阅该服务状态的应用实例运行在同一移动边缘主机上的标识。
如果后续所述第一应用实例的服务的可用性有更新，那么第一应用实例会向第一移动边缘平台发送服务更新消息；
和上述注册流程类似，第一移动边缘平台收到所述服务更新消息，会向位于第一移动边缘平台内的其他订阅了服务可用性的应用实例发送服务更新通知消息。
当其他应用实例收到服务可用性通知或者服务查询应答消息后，会在可用的服务实例列表中选择一个服务实例发起调用。当应用实例发现某个服务实例“不可用”的时候，将从可用服务实例列表中删除该服务实例。当某个服务实例从“不可用”状态变为“可用”时，应用实例把该服务实例添加到可用服务实例列表中。
进一步地，下面另一实施例2提供了不同移动边缘主机之间的服务通知方法，即移动边缘主机内的应用实例如何发现其他移动边缘主机内的服务的流程，具体如下：
实施例2：
请参考图6，图中包括第一移动边缘主机和第二移动边缘主机，其中第一移动边缘主机包括第一移动边缘平台和第一应用实例，第二移动边缘主机包括第二移动边缘平台和第二应用实例。
601.其他应用实例向第一移动边缘平台发送服务可用性事件订阅请求，第二应用实例向第二移动边缘平台发送服务可用性事件订阅请求。订阅请求携带订阅事件的过滤条件，这些过滤条件可以是服务实例标识、服务名称、服务类别、服务状态、服务的位置约束标识或者这些属性的组合。其中，该位置约束标识指示应用实例只订阅运行在本地主机的服务的实例的可用性，还是订阅所有服务(包括运行在其他移动边缘主机上的服务实例)的实例的可用性。
602.第一移动边缘平台和第二移动边缘平台分别发送应答消息，表示接受了订阅请求。
603.可选地，第二移动边缘平台向第一边缘发送服务可用性事件订阅请求。订阅请求携带订阅事件的过滤条件，这些过滤条件可以是服务实例标识、服务名称、服务类别、服务状态、服务的位置约束标识或者这些属性的组合。其中，所述位置约束标识指示只订阅运行在第一移动边缘主机上的服务的实例的可用性。
604.可选地，第一移动边缘平台向第二移动边缘平台发送应答消息，表示接受了订阅请求。
如果没有上述步骤603和604中的第二移动边缘平台和第一移动边缘平台之间的服务可用性事件订阅请求和应答过程，则可以通过其他方式，比如通过配置的方式在第一移动边缘平台配置当服务注册时或服务的可用性发生变化时需要向哪些移动边缘平台发送通知消息。
605.第一应用实例所提供的服务实例部署完成、首次可用后向第一移动边缘平台发送服务注册消息，注册服务实例并对外提供服务。在注册消息中携带服务名称、服务类别、服务版本、服务使用的传输信息。另外，该注册消息携带服务使用指示标识，该指示标识指示所述服务实例是否只能为本移动边缘主机上的应用所使用。在本实施例中，该指示标识指示该服务能被其他移动边缘主机上的应用实例所使用。
606.第一移动边缘平台在服务注册发现功能中注册服务实例，并保存所述服务实例是否只能为本移动边缘主机上的应用所使用的指示标识。服务实例是否只能为本移动边缘主机上的应用所使用的标识也可以在提供该服务的应用的描述符中进行描述，在应用实例化过程中由移动边缘平台管理器下发给第一移动边缘平台，由第一移动边缘平台保存。
607.第一移动边缘平台识别订阅了服务状态的应用实例，在该实施例中为其他应用实例。
608.第一移动边缘平台向其他应用实例发送服务可用性通知，指示新服务实例可用。
609.其他应用实例给第一移动边缘平台发送应答消息。
610.第一移动边缘平台根据上述步骤中的指示标识判断该服务实例是否可以被其他移动边缘主机上的应用实例所使用。如果可以，则第一移动边缘平台识别订阅了该服务状态的相关移动边缘平台，在该实施例中识别出的移动边缘平台为第二移动边缘平台。
611.第一移动边缘平台向第二移动边缘平台发送服务可用性通知，指示服务实例可用。在该消息中可以携带标识，指示服务实例的位置为非本地，即所述服务实例来自非 第二移动边缘主机。
612.第二移动边缘平台注册服务实例，标识服务实例的位置为非本地，并向订阅了该服务状态并且可以使用非本地服务的本地应用实例发送服务通知。
613.第二移动边缘平台向第一移动边缘平台发送应答消息。
614.第二移动边缘平台向第二应用实例发送服务可用性通知，指示新服务实例可用。在本实施例中，所述第二应用实例即为满足步骤612中的订阅了该服务状态并且可以使用非本地服务条件的位于第二移动边缘主机上的应用实例。
615.第二应用实例给第二移动边缘平台发送应答消息。
616.可选地，后续位于第一移动边缘主机上的其他应用实例可以向第一移动边缘平台发送服务可用性查询请求。在所述查询请求中包括服务位置约束标识，该位置约束标识指示其他应用实例是否只查询运行在本地主机的服务的实例。
617.第一移动边缘平台向其他应用实例发送应答消息，应答消息中包含新服务实例的信息。如果上一步中的位置约束标识指示其他应用实例只查询运行在本地主机的服务的实例，则应答消息中仅包含运行在第一移动边缘主机上的服务实例的信息。如果上一步中的位置约束标识指示其他应用实例查询所有服务的实例，则应答消息中既包含运行在第一移动边缘主机上的服务实例的信息，也包含运行在其他移动边缘主机(如第二移动边缘主机)上的服务的实例信息。所述服务实例的信息包括以下信息的一种或多种：服务名称、服务版本、服务类别、服务状态、服务使用的传输信息以及该服务实例是否只能为本移动边缘主机上的应用所使用的标识，以及该服务实例是否和订阅该服务状态的应用实例运行在同一移动边缘主机上的标识。
618.可选地，后续第二应用实例可以向第二移动边缘平台发送查询服务可用性查询请求。所述查询请求包括服务位置约束标识，该位置约束标识指示第二应用实例是否只查询运行在本地主机的服务的实例。
619.第二移动边缘平台向第二应用实例发送应答消息。如果步骤618中的位置约束标识参数指示第二应用实例只查询运行在本地主机的服务的实例，则应答消息中没有任何服务实例的信息。如果步骤618中的位置约束标识参数指示第二应用实例查询位于所有移动边缘主机上的服务实例，则应答消息中包含上述步骤中服务实例的信息。所述服务实例的信息包括以下信息的一种或多种：服务名称、服务版本、服务类别、服务状态、服务使用的传输信息、该服务实例是否只能为本移动边缘主机上的应用所使用的标识，以及该服务实例是否和订阅该服务状态的应用运行在同一移动边缘主机上的标识。
如果后续所述第一应用实例的服务的可用性有更新，那么第一应用实例会向第一移动边缘平台发送服务更新消息；和上述注册流程类似，第一移动边缘平台收到所述服务更新消息，会向所述第二移动边缘主机上的第二移动边缘平台发送服务更新通知消息，以及向位于第一移动边缘平台内的其他订阅了服务可用性的应用实例发送服务更新通知消息。
当其他应用实例收和第二应用实例收到服务可用性通知或者服务查询应答消息后，会在可用的服务实例列表中选择一个服务实例发起调用。当应用实例发现某个服务实例“不可用”的时候，将从可用服务实例列表中删除该服务实例。当某个服务实例从“不可用”状态变为“可用”时，应用实例把该服务实例添加到可用服务实例列表中。
另外，实施例2描述的步骤适用全互联方式，也适用分层注册方式。如果是分层注册 方式，则第一移动边缘平台和第二移动边缘平台互相发送的消息通过中心服务注册发现功能进行中转，这种方式可以避免全互联方式中的不同移动边缘主机两两互联，可降低连接的复杂度。
通过以上实施例提供的方法，移动边缘主机上的应用实例不仅可以发现并使用其所在移动边缘主机上的服务，也可以发现并使用其他移动边缘主机上的服务，例如上述实施例中的第二移动边缘主机上的第二应用实例能够发现位于第一移动边缘主机上的第一应用实例提供的服务。所以即使本移动边缘主机上的服务故障，也可以使用其他移动边缘主机上的服务，从而保证本移动边缘主机上的应用正常运行。另外，可以不必在每一个边缘主机上部署服务实例，实现各个不同的移动边缘主机资源共享，节约了资源。
图7是本发明实施例提供的一种移动边缘主机，可以用于执行上述各种方法中由移动边缘主机执行的各个步骤，所述移动边缘主机可以包括移动边缘平台、第一应用实例和其他应用实例，主要地，
第一应用实例用于向第一移动边缘平台发送服务注册消息，所述服务注册消息携带服务使用指示标识，所述指示标识指示该服务是否能被其他移动边缘主机上的应用实例所使用；
第一移动边缘平台用于向位于第一移动边缘主机内的其他订阅了服务可用性的应用实例发送服务通知消息。
其中，所述第一移动边缘平台根据所述指示标识确定是否向其他移动边缘主机上的移动边缘平台发送服务通知消息。当所述指示标识指示该服务不能被其他移动边缘主机上的应用实例所使用时，所述第一移动边缘平台根据所述指示标识确定不向其他移动边缘主机上的移动边缘平台发送服务通知消息；当所述指示标识指示该服务能被其他移动边缘主机上的应用实例所使用时，所述第一移动边缘平台根据所述指示标识确定向其他移动边缘主机上的其他移动边缘平台发送服务通知消息。不过，发送的前提条件是其他移动边缘主机之前已经向所述第一移动边缘平台发送了服务可用性订阅消息或者在第一移动边缘平台上配置了当服务注册或者状态变化时需要向所述其他移动边缘主机上的其他移动边缘平台发送通知消息。
参考图8，本发明实施例还提供了一种移动边缘通信系统，包括第一移动边缘主机和第二移动边缘主机，所述系统用于执行上述实施例2中的由第一和第二移动边缘主机执行的各个步骤，主要地,
第一移动边缘主机包括第一移动边缘平台和第一应用实例，第二移动边缘主机包括第二移动边缘平台，
第一移动边缘平台用于接收来自第一应用实例的服务注册消息；
第一移动边缘平台向第二移动边缘平台发送服务通知消息；
具体地，所述服务注册消息携带服务使用指示标识，所述指示标识指示该服务能被其他移动边缘主机上的应用实例所使用；所述第一移动边缘平台用于根据所述标识向第二移动边缘平台发送服务通知消息。
进一步地，在第一移动边缘平台接收来自第一应用实例的服务注册消息之前，第一移动边缘平台用于接收第二移动边缘平台向第一移动边缘平台发送的服务可用性订阅消息；或第一移动边缘平台预先配置第二移动边缘平台作为接收所述服务通知消息的对象。
图9是本发明另一实施例提供的一种移动边缘主机硬件图，所述移动边缘主可以包 括：处理器、通信接口以及存储器。
处理器91可以包括一个或者一个以上处理单元，该处理单元可以是中央处理单元(英文：central processing unit，CPU)或者网络处理器(英文：network processor，NP)等。
通信接口94用于跟其他通信设备连接和信息交互，包括接收和发送相应的消息；该网络设备90还可以包括存储器93，处理器91可以通过总线与存储器93和通信接口94相连。存储器93可用于存储软件程序，该软件程序可以由处理器91执行，以实现图5和图6中所示的实施例中的方法步骤。此外，该存储器93中还可以存储各类业务数据或者用户数据,包括上述方法步骤中的各种应用实例和服务的状态数据等。
可选地，该网络设备90还可以包括输出设备95以及输入设备97。输出设备95和输入设备97与处理器91相连。输出设备95可以是用于显示信息的显示器、播放声音的功放设备或者打印机等，输出设备95还可以包括输出控制器，用以提供输出到显示屏、功放设备或者打印机。输入设备97可以是用于用户输入信息的诸如鼠标、键盘、电子触控笔或者触控面板之类的设备，输入设备97还可以包括输出控制器以用于接收和处理来自鼠标、键盘、电子触控笔或者触控面板等设备的输入。
本领域普通技术人员可以理解实现上述实施例由处理器执行的全部或部分步骤可以通过硬件来完成，也可以通过指令来控制相关的硬件完成，所述的指令可以存储于一种计算机可读存储介质中，上述提到的计算机可读存储介质可以是只读存储器，磁盘或光盘等。另外，本发明实施例还提供了计算机程序产品以及存储有上述计算机程序的存储介质。该计算机程序产品包括在计算机可读存储介质中存储的程序代码，并且该程序代码通过处理器进行加载来实现上述方法。
以上所述，仅为能够实现本发明的一种或多种具体实施方式，但权利要求的保护范围并不局限于上述实施例，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (21)

  1. 一种服务通知方法，所述方法用于第一移动边缘主机和第二移动边缘主机，其中第一移动边缘主机包括第一移动边缘平台和第一应用实例，第二移动边缘主机包括第二移动边缘平台，其特征在于，
    第一移动边缘平台接收来自第一应用实例的服务注册消息；
    第一移动边缘平台向第二移动边缘平台发送服务通知消息。
  2. 根据权利要求1所述的方法，其特征在于，
    所述服务注册消息携带服务使用指示标识，所述指示标识指示该服务能被其他移动边缘主机上的应用实例所使用；
    所述第一移动边缘平台根据所述标识向第二移动边缘平台发送服务通知消息。
  3. 根据权利要求1所述的方法，其特征在于，在第一移动边缘平台接收来自第一应用实例的服务注册消息之前，所述方法包括：
    第一移动边缘平台接收第二移动边缘平台向第一移动边缘平台发送的服务可用性订阅消息；或
    第一移动边缘平台预先配置第二移动边缘平台作为接收所述服务通知消息的对象。
  4. 根据权利要求1所述的方法，其特征在于，所述第二移动边缘主机还包括第二应用实例，所述方法包括：
    第二应用实例向第二移动边缘主平台发送服务可用性订阅消息；
    第二移动边缘平台接收到第一移动边缘平台发送的服务通知消息后，标识所述服务实例的位置为非本地，并向所述第二应用实例发送服务通知消息。
  5. 根据权利要求4所述的方法，其特征在于，
    所述第二应用实例向第二移动边缘平台发送的服务可用性订阅消息包括位置约束标识，所述标识指示第二应用实例订阅运行在第一和第二移动边缘主机上的服务的可用性。
  6. 根据权利要求1所述的方法，其特征在于，所述方法进一步包括：
    第一移动边缘平台向位于第一移动边缘主机内的其他订阅了服务可用性的应用实例发送服务通知消息。
  7. 根据权利要求1所述的方法，其特征在于，所述方法进一步包括：
    第一移动边缘平台接收位于第一移动边缘主机内的应用实例的服务可用性查询请求，该查询请求包括服务位置约束标识，该位置约束标识指示应用实例是否只查询运行在第一移动边缘主机上的服务的实例。；
    第一移动边缘平台向其返回符合查询条件的服务实例信息，所述服务实例信息包括该服务实例是否和订阅该服务状态的应用实例运行在同一移动边缘主机上的标识。
  8. 根据权利要求1所述的方法，其特征在于，如果所述第一应用实例的服务的可用性有更新，所述方法进一步包括：
    第一移动边缘平台接收来自第一应用实例的服务更新消息；
    第一移动边缘平台向所述第二移动边缘主机上的第二移动边缘平台发送服务更新通知消息；以及
    向位于第一移动边缘主机内的其他订阅了服务可用性的应用实例发送服务更新通知消息。
  9. 一种服务通知方法，所述方法用于第一移动边缘主机，其中第一移动边缘主机包括第一移动边缘平台、第一应用实例和其他应用实例，其特征在于，
    第一移动边缘平台接收来自第一应用实例的服务注册消息；所述服务注册消息携带服务使用指示标识，所述指示标识指示该服务是否能被其他移动边缘主机上的应用实例所使用；
    第一移动边缘平台向位于第一移动边缘主机内的其他订阅了服务可用性的应用实例发送服务通知消息。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还用于第二移动边缘主机，所述第二移动边缘主机包括第二移动边缘平台，所述方法包括：
    第二移动边缘平台向第一移动边缘平台发送服务可用性订阅消息；
    所述第一移动边缘平台根据所述指示标识确定是否向第二移动边缘主机上的第二移动边缘平台发送服务通知消息。
  11. 根据权利要求10所述的方法，其特征在于，
    当所述指示标识指示该服务不能被其他移动边缘主机上的应用实例所使用时，所述第一移动边缘平台根据所述指示标识确定不向第二移动边缘主机上的第二移动边缘平台发送服务通知消息；
    当所述指示标识指示该服务能被其他移动边缘主机上的应用实例所使用时，所述第一移动边缘平台根据所述指示标识确定向第二移动边缘主机上的第二移动边缘平台发送服务通知消息。
  12. 根据权利要求9所述的方法，其特征在于，所述方法进一步包括：
    第一移动边缘平台接收位于第一移动边缘主机内的应用实例的服务可用性查询请求，该查询请求包括位置约束标识，该位置约束标识指示应用实例是否只查询运行在第一移动边缘主机上的服务的实例；
    第一移动边缘平台向其返回符合查询条件的服务实例信息，所述服务实例信息包括该服务实例是否和订阅该服务状态的应用实例运行在同一移动边缘主机上的标识。
  13. 一种移动边缘主机，包括移动边缘平台、第一应用实例和其他应用实例，其特征在于，
    第一应用实例用于向移动边缘平台发送服务注册消息，所述服务注册消息携带服务 使用指示标识，所述指示标识指示该服务是否能被其他移动边缘主机上的应用实例所使用；
    移动边缘平台用于向位于移动边缘主机内的其他订阅了服务可用性的应用实例发送服务通知消息。
  14. 根据权利要求13所述的移动边缘主机，其特征在于，
    所述移动边缘平台接收其他移动边缘主机上的移动边缘平台发送的服务可用性订阅消息；
    所述移动边缘平台根据所述指示标识确定是否向其他移动边缘主机上的移动边缘平台发送服务通知消息。
  15. 根据权利要求14所述的移动边缘主机，其特征在于，
    当所述指示标识指示该服务不能被其他移动边缘主机上的应用实例所使用时，所述移动边缘平台根据所述指示标识确定不向其他移动边缘主机上的移动边缘平台发送服务通知消息；
    当所述指示标识指示该服务能被其他移动边缘主机上的应用实例所使用时，所述移动边缘平台根据所述指示标识确定向其他移动边缘主机上的移动边缘平台发送服务通知消息。
  16. 一种移动边缘通信系统，包括第一移动边缘主机和第二移动边缘主机，第一移动边缘主机包括第一移动边缘平台和第一应用实例，第二移动边缘主机包括第二移动边缘平台，其特征在于，
    第一移动边缘平台用于接收来自第一应用实例的服务注册消息；
    第一移动边缘平台用于向第二移动边缘平台发送服务通知消息。
  17. 根据权要求16所述的移动边缘通信系统，其特征在于，
    所述服务注册消息携带服务使用指示标识，所述指示标识指示该服务能被其他移动边缘主机上的应用实例所使用；
    所述第一移动边缘平台用于根据所述标识向第二移动边缘平台发送服务通知消息。
  18. 根据权要求16所述的移动边缘通信系统，其特征在于，
    在第一移动边缘平台用于接收来自第一应用实例的服务注册消息之前，所述第一移动边缘平台还用于接收第二移动边缘平台向第一移动边缘平台发送的服务可用性订阅消息；或
    所述第一移动边缘平台预先配置第二移动边缘平台作为接收所述服务通知消息的对象。
  19. 根据权要求16所述的移动边缘通信系统，其特征在于，
    所述第二移动边缘主机还包括第二应用实例，第二应用实例向第二移动边缘平台发送服务可用性订阅消息；
    第二移动边缘平台用于接收到第一移动边缘平台发送的服务通知消息后，向所述第二应用实例发送服务通知消息。
  20. 据权要求19所述的移动边缘通信系统，其特征在于，
    所述第二应用实例向第二移动边缘主机发送的服务可用性订阅消息包括位置约束标识，所述标识指示第二应用实例不只是订阅运行在第二移动边缘主机上的服务的可用性。
  21. 一种计算机可读存储介质，该计算机可读存储介质存储有可执行程序指令，所述可执行程序指令被运行时，用于执行上述1-12中的任一权利要求所述的步骤。
PCT/CN2017/112378 2017-11-22 2017-11-22 移动边缘主机服务通知方法和装置 WO2019100266A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2017/112378 WO2019100266A1 (zh) 2017-11-22 2017-11-22 移动边缘主机服务通知方法和装置
EP17932687.1A EP3703337B1 (en) 2017-11-22 2017-11-22 Mobile edge host-machine service notification method and apparatus
CN201780096776.XA CN111345008B (zh) 2017-11-22 2017-11-22 移动边缘主机服务通知方法和装置
US16/879,361 US11432137B2 (en) 2017-11-22 2020-05-20 Service notification method for mobile edge host and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/112378 WO2019100266A1 (zh) 2017-11-22 2017-11-22 移动边缘主机服务通知方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/879,361 Continuation US11432137B2 (en) 2017-11-22 2020-05-20 Service notification method for mobile edge host and apparatus

Publications (1)

Publication Number Publication Date
WO2019100266A1 true WO2019100266A1 (zh) 2019-05-31

Family

ID=66631336

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/112378 WO2019100266A1 (zh) 2017-11-22 2017-11-22 移动边缘主机服务通知方法和装置

Country Status (4)

Country Link
US (1) US11432137B2 (zh)
EP (1) EP3703337B1 (zh)
CN (1) CN111345008B (zh)
WO (1) WO2019100266A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112788089A (zh) * 2019-11-11 2021-05-11 财团法人工业技术研究院 多边缘云的网络通讯控制方法及边缘运算装置与系统
CN114270789A (zh) * 2019-08-20 2022-04-01 华为技术有限公司 一种获取信息的方法及装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019236083A1 (en) * 2018-06-07 2019-12-12 Nokia Technologies Oy Mobile edge computing applications management for wireless networks
CN112153021B (zh) * 2020-09-10 2023-05-19 中国联合网络通信集团有限公司 一种业务数据的获取方法及装置
CN114844865A (zh) * 2021-01-30 2022-08-02 华为技术有限公司 一种算力感知网络中的服务标识分配方法及通信装置
EP4352941A1 (en) * 2021-06-07 2024-04-17 InterDigital Patent Holdings, Inc. Methods for exporting services generated at cmec to emec applications
CN115987534A (zh) * 2021-10-14 2023-04-18 华为技术有限公司 一种资源访问方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106231607A (zh) * 2016-09-21 2016-12-14 北京佰才邦技术有限公司 一种资源分配的方法及基站
CN106254408A (zh) * 2015-06-12 2016-12-21 财团法人工业技术研究院 移动边缘计算的控制方法、网络系统与服务平台
CN106358245A (zh) * 2016-11-07 2017-01-25 北京佰才邦技术有限公司 移动边缘计算应用负荷分担的方法和控制器
US20170118311A1 (en) * 2015-10-22 2017-04-27 Saguna Networks Ltd. Methods Circuits Devices Systems and Functionally Associated Computer Executable Code for Facilitating Edge Computing on a Mobile Data Communication Network
WO2017091960A1 (zh) * 2015-11-30 2017-06-08 华为技术有限公司 切换移动边缘平台的方法、装置和系统

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100555946C (zh) 2005-08-20 2009-10-28 华为技术有限公司 一种实现通知服务的方法以及分布式网管系统
US8843588B2 (en) * 2009-07-10 2014-09-23 Nokia Siemens Networks Oy Methods, apparatuses, related computer program product and data structure for distributed storage of service provision-related information
EP3355615B1 (en) * 2015-10-21 2019-08-28 Huawei Technologies Co., Ltd. Mec platform handover
CN108353067B (zh) * 2015-11-30 2020-06-02 华为技术有限公司 一种能力开放的实现方法、系统及相关设备
CN108476215B (zh) * 2016-02-04 2020-09-04 华为技术有限公司 服务迁移方法、装置及系统
CA3015632A1 (en) * 2016-02-25 2017-08-31 ACS (US), Inc. Platform for computing at the mobile edge
US10440096B2 (en) * 2016-12-28 2019-10-08 Intel IP Corporation Application computation offloading for mobile edge computing
US10972575B2 (en) * 2017-06-02 2021-04-06 Huawei Technologies Co., Ltd. Method and system for supporting edge computing
WO2019000376A1 (zh) * 2017-06-30 2019-01-03 北京小米移动软件有限公司 一种实现网络边缘计算的方法及装置
US20190075501A1 (en) * 2017-09-05 2019-03-07 Industrial Technology Research Institute Control method for network communication system and multi-access edge computing ecosystem device
US10938736B2 (en) * 2017-10-18 2021-03-02 Futurewei Technologies, Inc. Dynamic allocation of edge computing resources in edge computing centers
US10440559B2 (en) * 2017-10-25 2019-10-08 Futurewei Technologies, Inc. Private mobile edge computing data center in a telecommunication network
US10110495B1 (en) * 2017-11-22 2018-10-23 Intel Corporation Multi-access edge computing (MEC) service provision based on local cost measurements
CN117749793A (zh) * 2018-01-12 2024-03-22 交互数字专利控股公司 提供无线网络信息服务的方法和设备
CN112042167B (zh) * 2018-01-25 2023-04-18 诺基亚通信公司 用于在mec网络中处理用户服务简档信息的方法和装置
US10771569B1 (en) * 2019-12-13 2020-09-08 Industrial Technology Research Institute Network communication control method of multiple edge clouds and edge computing system
US10827329B1 (en) * 2020-02-26 2020-11-03 At&T Mobility Ii Llc Facilitation of dynamic edge computations for 6G or other next generation network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106254408A (zh) * 2015-06-12 2016-12-21 财团法人工业技术研究院 移动边缘计算的控制方法、网络系统与服务平台
US20170118311A1 (en) * 2015-10-22 2017-04-27 Saguna Networks Ltd. Methods Circuits Devices Systems and Functionally Associated Computer Executable Code for Facilitating Edge Computing on a Mobile Data Communication Network
WO2017091960A1 (zh) * 2015-11-30 2017-06-08 华为技术有限公司 切换移动边缘平台的方法、装置和系统
CN106231607A (zh) * 2016-09-21 2016-12-14 北京佰才邦技术有限公司 一种资源分配的方法及基站
CN106358245A (zh) * 2016-11-07 2017-01-25 北京佰才邦技术有限公司 移动边缘计算应用负荷分担的方法和控制器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3703337A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114270789A (zh) * 2019-08-20 2022-04-01 华为技术有限公司 一种获取信息的方法及装置
EP4016961A4 (en) * 2019-08-20 2022-10-12 Huawei Technologies Co., Ltd. METHOD AND MECHANISM FOR OBTAINING INFORMATION
CN114270789B (zh) * 2019-08-20 2023-09-01 华为技术有限公司 一种获取信息的方法及装置
CN112788089A (zh) * 2019-11-11 2021-05-11 财团法人工业技术研究院 多边缘云的网络通讯控制方法及边缘运算装置与系统
CN112788089B (zh) * 2019-11-11 2023-11-07 财团法人工业技术研究院 多边缘云的网络通讯控制方法及边缘运算装置与系统

Also Published As

Publication number Publication date
EP3703337A4 (en) 2020-09-02
US11432137B2 (en) 2022-08-30
CN111345008A (zh) 2020-06-26
EP3703337B1 (en) 2022-12-21
EP3703337A1 (en) 2020-09-02
CN111345008B (zh) 2022-06-10
US20200288302A1 (en) 2020-09-10

Similar Documents

Publication Publication Date Title
WO2019100266A1 (zh) 移动边缘主机服务通知方法和装置
US11563713B2 (en) Domain name server allocation method and apparatus
US11258667B2 (en) Network management method and related device
US10698717B2 (en) Accelerator virtualization method and apparatus, and centralized resource manager
CN107689882B (zh) 一种虚拟化网络中业务部署的方法和装置
US11088944B2 (en) Serverless packet processing service with isolated virtual network integration
US20210274328A1 (en) Internet of vehicles message notification method and apparatus
US20200344126A1 (en) Network slice deployment method and apparatus
WO2017066931A1 (zh) 网络功能虚拟化架构中证书的管理方法及装置
WO2017185251A1 (zh) Vnfm的确定方法和网络功能虚拟化编排器
US11416267B2 (en) Dynamic hardware accelerator selection and loading based on acceleration requirements
CN109194589B (zh) 一种mdc实现方法及装置
US20220350637A1 (en) Virtual machine deployment method and related apparatus
EP3629160B1 (en) Method and device for managing vnf instantiation
CN110855488A (zh) 一种虚拟机接入方法及装置
CN111615128A (zh) 一种多接入边缘计算方法、平台及系统
CN113608865A (zh) 一种流量控制方法、装置、系统、电子设备及存储介质
WO2021022947A1 (zh) 一种部署虚拟机的方法及相关装置
WO2020249080A1 (zh) 一种虚拟网络功能vnf部署方法及装置
WO2017206092A1 (zh) 一种生命周期管理方法及管理单元
JP2019041241A (ja) 振り分けシステム
CN114124740A (zh) 一种vnf实例化的方法和装置
US20230105269A1 (en) Virtualized network service deployment method and apparatus
CN109731345B (zh) 语音处理方法及装置、电子设备、存储介质
JP2012203421A (ja) 情報処理方法、管理サーバおよび管理プログラム

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: 17932687

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017932687

Country of ref document: EP

Effective date: 20200528