WO2017091934A1 - 一种能力开放的实现方法、***及相关设备 - Google Patents
一种能力开放的实现方法、***及相关设备 Download PDFInfo
- Publication number
- WO2017091934A1 WO2017091934A1 PCT/CN2015/095940 CN2015095940W WO2017091934A1 WO 2017091934 A1 WO2017091934 A1 WO 2017091934A1 CN 2015095940 W CN2015095940 W CN 2015095940W WO 2017091934 A1 WO2017091934 A1 WO 2017091934A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mobile edge
- edge platform
- api
- capability information
- platform
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
-
- 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/01—Protocols
Definitions
- the present invention relates to the field of wireless communication technologies, and in particular, to a method, system, and related device for implementing an open capability.
- FIG. 1 is a schematic diagram of an application of a MEC server in the prior art.
- the MEC server in FIG. 1 includes a MEC hosting infrastructure, a MEC application platform, and an edge service server, where the underlying infrastructure includes MEC hardware resources.
- MEC Hardware Resources and MEC Virtualization Layer MEC Hardware Resources and MEC Virtualization Layer.
- the mobile edge platform is the core of the MEC server, including the MEC virtualization management layer (such as IaaS) and the MEC application platform service.
- the location of the MEC virtual management layer is optional or located. Other locations are not implemented in the mobile edge platform.
- the MEC application service platform is used to provide a data offloading service (Traffic Offload Function, TOF), a Radio Network Information Service (RNIS), a communication service (Communication Service), a registration service, and the like.
- TOF Traffic Offload Function
- RNIS Radio Network Information Service
- Communication Service Communication Service
- the TOC service, the RNIS service, and the like are opened to the MEC application (Application, abbreviated as APP) in the virtual machine (VM) of the edge service server through the registration service module.
- APP Virtual Machine
- the deployment of the MEC server is based on the location of the MEC server.
- the first one is to deploy the MEC server on the eNodeB side of the Long-Term Evolution (LTE), an eNodeB.
- LTE Long-Term Evolution
- eNodeB One MEC server is deployed on the side;
- the second is to deploy the MEC server on the aggregation node of LTE or The 3rd Generation Telecommunication (3G), and multiple MEC servers can be used by multiple base stations;
- the MEC server is deployed on a 3G Radio Network Controller (RNC), and multiple MEC servers can be used by multiple base stations.
- RNC Radio Network Controller
- the first type and the third type of MEC server are deployed on the radio access network side to reduce delay, optimize system performance, and improve quality of experience (QoE).
- the second type is in the radio access network.
- the upper layer node such as the 3G aggregation node, can support mobility.
- the above three deployment methods only consider the location of the MEC server, and the deployment method is not flexible enough, which limits the development and application of the MEC server.
- the present invention provides an open source implementation method, system, and related equipment, which are used to implement a more flexible MEC server deployment and improve system performance.
- a first aspect of the present invention provides a method for implementing an open capability, which may include:
- the first mobile edge platform acquires the capability information of the wireless access network device, and configures the application programming interface API and the usage time limit of the foregoing API.
- the API is used by the first mobile edge platform to provide the capability information to the second mobile edge platform.
- the first mobile edge platform triggers a registration function to send registration information to the second mobile edge platform, where the registration information includes an identifier of the API;
- the first mobile edge platform receives the API request sent by the second mobile edge platform, where the API request includes the identifier of the API, and the API request is used to request the capability information from the first mobile edge platform.
- the first mobile edge platform detects whether the usage time of the API is expired
- the first mobile edge platform sends an API response to the second mobile edge platform by using the API, and the API response includes the capability information.
- the deployment of the cascaded mobile edge platform is implemented (specifically by deploying a cascaded MEC server), and the cascaded mobile edge platform includes a first mobile edge platform disposed on the wireless access network and A second mobile edge platform disposed in a node of the upper layer of the radio access network.
- the first mobile edge platform Based on the cascaded first mobile edge platform and the second mobile edge platform, since the first mobile edge platform is close to the radio access network device, the first mobile edge platform can obtain the capability information of the radio access network device and save the information. .
- the first mobile edge platform triggers the registration function, and the capability information of the radio access network device is provided to the second mobile edge platform.
- the first mobile edge platform implements the capability information of the radio access network device through the API interface. Provided to the second mobile edge platform), in addition to reducing the processing load of the radio access network device, improving system performance and implementing flexible service deployment.
- the foregoing capability information includes a channel signal status, a cell load, a terminal location information, a network congestion, and a terminal identifier.
- the identifier of the foregoing API may be a Uniform Resource Locator (URL) or a Uniform Resource Identifier (URI).
- URL Uniform Resource Locator
- URI Uniform Resource Identifier
- the method for implementing the capability of the first aspect further includes: if the usage aging of the API has expired, the first mobile edge platform acquires current capability information of the wireless access network device, where the current The capability information is capability information of the current time of the wireless access network device; the first mobile edge platform resets the usage time of the API, and sends an API response including the current capability information to the second mobile edge platform by using the API. .
- the first mobile edge platform triggering the registration function to send the registration information to the second mobile edge platform includes: the first mobile edge platform transmitting the registration information to the second mobile edge platform.
- the first mobile edge platform triggering the registration function to send the registration information to the second mobile edge platform includes: the first mobile edge platform triggers the management network element, and the registration is performed by using the management network element. Information is sent to the second mobile edge platform described above.
- the method for implementing the capability of the first aspect further includes: the first mobile edge platform providing the capability information to the first edge service server by using the foregoing API, the first edge service server and the foregoing
- the first mobile edge platform is disposed in the first mobile edge computing MEC server.
- a second aspect of the present invention provides a method for implementing an open capability, which may include:
- the second mobile edge platform receives the registration information, where the registration information includes an identifier of the application programming interface API, and the API is used by the first mobile edge platform to provide capability information to the second mobile edge platform, where the capability information is a wireless access network device. Capability information;
- the second mobile edge platform sends an API request to the first mobile edge platform, where the API request includes an identifier of the API, and the API request is used to request the capability information from the first mobile edge platform.
- the second mobile edge platform receives an API response sent by the first mobile edge platform, and the API response includes the capability information.
- the second mobile edge platform After receiving the registration information, requesting the first mobile edge platform to obtain the capability information of the radio access network device by sending an API request including the API in the registration information, to share the processing burden of the radio access network device, and improve System performance and the use of mobile edge platforms (or MEC servers).
- the foregoing capability information includes a channel signal status, a cell load, a terminal location information, a network congestion, and a terminal identifier.
- the second mobile edge platform before the sending, by the second mobile edge platform, the API request to the first mobile edge platform, the second mobile edge platform receives a trigger request sent by the second edge service server, where the trigger request includes the foregoing The identifier of the wireless access network device and/or the ID of the first mobile edge platform, the trigger request is used to trigger the second mobile edge platform to send the API request to the first mobile edge platform, where the second edge service is The server and the second mobile edge platform are disposed in the second mobile edge computing MEC server; the second mobile edge platform is determined according to the identity identifier of the wireless access network device and/or the ID of the first mobile edge platform.
- the second mobile edge platform after the foregoing second mobile edge platform receives the API response sent by the first mobile edge platform, the second mobile edge platform provides the capability information to the second edge service server.
- the receiving, by the second mobile edge platform, the registration information includes: the second mobile edge platform receiving the registration information sent by the first mobile edge platform.
- the receiving, by the second mobile edge platform, the registration information includes: the second mobile edge platform receiving the registration information sent by the management network element.
- a third aspect of the present invention provides a mobile edge platform, which may include:
- a processing module configured to acquire capability information of the wireless access network device, configure an application programming interface API, and set a usage time limit of the foregoing API, where the foregoing API is used by the mobile edge platform to provide the capability information to the second mobile edge platform;
- a registration service module configured to trigger a registration function to send registration information to the second mobile edge platform, where the registration information includes an identifier of the foregoing API
- the processing module is further configured to receive an API request sent by the second mobile edge platform, where the API request includes an identifier of the API, and the API request is used to request the mobile edge platform.
- the capability information is detected; whether the usage time limit of the API is expired, and when it is detected that the usage time of the API is not expired, the API response is sent to the second mobile edge platform by using the API, and the API response includes the capability information.
- the foregoing capability information includes a channel signal status, a cell load, a terminal location information, a network congestion, and a terminal identifier.
- the processing module is further configured to: when detecting that the usage aging of the API has expired, acquiring current capability information of the radio access network device, where the current capability information is the radio access network device The capability information provided at the current time; resetting the usage time of the above API, and transmitting an API response including the current capability information to the second mobile edge platform through the API.
- the registration service module is specifically configured to send the registration information to the second mobile edge platform.
- the registration service module is further configured to: trigger the management network element, and send the registration information to the second mobile edge platform by using the management network element.
- the processing module is further configured to: provide the foregoing capability information to the first edge service server by using the foregoing API, where the first edge service server and the mobile edge platform are disposed on the first mobile edge computing MEC server. in.
- a fourth aspect of the present invention provides a mobile edge platform, which may include:
- a registration service module configured to receive registration information, where the registration information includes an identifier of an application programming interface API, where the API is used by the first mobile edge platform to provide capability information to the mobile edge platform, and the capability information is a capability of the radio access network device. information;
- a processing module configured to send an API request to the first mobile edge platform, where the API request includes an identifier of the API, where the API request is used to request the capability information from the first mobile edge platform; and receive the first mobile edge platform to send The API response, the above API response includes the above capability information.
- the foregoing capability information includes a channel signal status, a cell load, a terminal location information, a network congestion, and a terminal identifier.
- the processing module is further configured to: before sending the foregoing API request to the first mobile edge platform, receive a trigger request sent by the second edge service server, where the touch
- the sending request includes the identifier ID of the wireless access network device and/or the ID of the first mobile edge platform, where the trigger request is used to trigger the mobile edge platform to send the API request to the first mobile edge platform, where the foregoing
- the two edge service servers and the mobile edge platform are disposed in the second mobile edge computing MEC server; and the API is determined according to the identity identifier of the wireless access network device and/or the ID of the first mobile edge platform.
- the processing module is further configured to: after receiving the API response sent by the first mobile edge platform, provide the capability information to the second edge service server.
- the processing module is specifically configured to receive the registration information sent by the first mobile edge platform.
- the processing module is specifically configured to receive the registration information sent by the management network element.
- a fifth aspect of the present invention provides an MEC server, which may include: a mobile edge platform provided by the third aspect or a mobile edge platform provided by the fourth aspect.
- the MEC server provided by the fifth aspect may further include an edge service server, where the mobile edge platform is further configured to provide the edge service server with capability information of the radio access network device.
- a sixth aspect of the present invention provides an open capability implementation system, which may include: a first mobile edge platform and a second mobile edge platform; wherein the first mobile edge platform is the mobile edge platform provided by the first aspect, and the second The mobile edge platform is the mobile edge platform provided by the second aspect above.
- the capability open implementation system provided by the foregoing sixth aspect further includes a radio access network device, where the radio access network device is configured to provide capability information to the first mobile edge platform.
- the implementation system of the capability opening provided by the foregoing sixth aspect further includes a terminal, where the terminal is configured to provide a data packet (IP packet).
- IP packet data packet
- a seventh aspect of the present invention provides a system for implementing an open capability, which may include: a radio access network device, a first mobile edge computing MEC server, and a second MEC server; wherein the first MEC server provides the fifth aspect
- the MEC server, the second MEC server is the MEC server provided for the fifth aspect
- the first MEC server includes the mobile edge platform provided by the third aspect
- the second MEC server includes the mobile edge platform provided by the fourth aspect.
- FIG. 1 is a schematic structural diagram of a MEC server in the prior art
- 2a is a schematic diagram of a deployment scenario of an MEC server provided by the prior art
- Figure 2b is a deployment scenario of a cascaded MEC server according to some embodiments of the present invention.
- 2c is a schematic diagram of a communication interface between a MEC server and a radio access network device according to an embodiment of the present invention
- FIG. 2d is an internal architecture diagram of a cascaded MEC server deployed according to FIG. 2b according to an embodiment of the present invention
- 2e is an architectural diagram of an implementation system for capability opening according to an embodiment of the present invention.
- FIG. 3 is a signaling diagram of a method for implementing capability opening according to some embodiments of the present invention.
- FIG. 4 is another signaling diagram of a method for implementing capability opening according to some embodiments of the present invention.
- FIG. 5 is another signaling diagram of a method for implementing capability opening according to some embodiments of the present invention.
- FIG. 6 is a schematic structural diagram of a mobile edge platform according to some embodiments of the present invention.
- FIG. 7 is a schematic structural diagram of a mobile edge platform according to another embodiment of the present invention.
- FIG. 8 is a schematic structural diagram of an MEC server according to some embodiments of the present invention.
- FIG. 9 is a schematic structural diagram of an MEC server according to another embodiment of the present invention.
- FIG. 10 is a schematic structural diagram of an implementation system for capability opening according to some embodiments of the present invention.
- FIG. 11 is a schematic structural diagram of an implementation system of capability opening according to another embodiment of the present invention.
- FIG. 12 is a schematic structural diagram of an apparatus for implementing capability opening according to an embodiment of the present invention.
- the embodiment of the present invention provides a method for implementing capability development, which implements a cascaded MEC server deployment mode, that is, can obtain capability information of a radio access network device, thereby reducing delay, fast access, and improving QoE. Mobility support is available.
- the embodiment of the invention further provides a system corresponding to the implementation method of the capability development, and a mobile edge platform and an MEC server.
- FIG. 2a is a schematic diagram of a deployment scenario of the MEC server provided by the prior art.
- the MEC server can be deployed on the radio access network side in the first mode, that is, on the S1-U interface of the radio access network device.
- the radio access network device in FIG. 2a takes the eNodeB as an example.
- deployment mode 1 because the MEC server has a natural location advantage, it can be close to the radio access network device to obtain the capability information of the radio access network device, thereby providing low-latency, fast access and high-bandwidth localization innovation. service.
- the MEC server may be deployed on the node between the radio access network and the core network according to the second mode, such as the aggregation node of the aggregation network in the 3G network.
- the MEC server can support base station mobility.
- the deployment mode 1 and the deployment mode 2 of FIG. 2a exist in an alternative manner, that is, the MEC server is deployed in the deployment mode 1 or the MEC server is deployed in the deployment mode 2.
- the MEC server location and deployment are mainly considered during deployment.
- the method is relatively simple, the flexibility is not enough, and the MEC server function cannot be fully utilized to realize service deployment and improve the application range of the MEC server.
- FIG. 2b is a deployment scenario of a cascading MEC server according to some embodiments of the present invention.
- the device is deployed on a radio access network device (the eNodeB is taken as an example in FIG. 2b).
- the MEC server is called a low-level MEC server (Low MEC), and the low-level MEC server is the first MEC server in the embodiment of the present invention, and is deployed at a higher layer (ie, between the radio access network and the core network).
- the node of the MEC server in the upper layer of FIG. 2b is a high-level MEC server (High MEC), which is a service gateway (Serving GateWay, SGW for short) and a packet data network gateway (PDW GateWay).
- High MEC high-level MEC server
- the MEC server is the second MEC server in the embodiment of the present invention. The description is given here, and in the subsequent embodiments of the present invention, it will be explained by a low-level MEC server and a high-level MEC server.
- FIG. 2c is a schematic diagram of a communication interface between a MEC server and a radio access network device according to an embodiment of the present invention
- the MEC server and the radio access network device include two functional interfaces.
- One is a data interface, which is used when transmitting data between the radio access network device and the MEC server (IP packet of the UE); the other is a signaling interface, which is transmitted between the radio access network device and the MEC server.
- Ability information is used.
- the data interface can be implemented in two ways: one is an external interface (that is, one interface is used to reset), and the other is to directly use the S1-U interface.
- the signaling interface one is to reuse the data interface (that is, the data interface is used as both the data interface and the signaling interface), and the other is the external interface (that is, the interface is reset).
- two modes can be classified according to the position of the lower-level MEC server on the data plane: the first one is based on the on-path model, that is, the lower layer.
- the MEC server exists and the low-level MEC server directly uses the S1-U interface to communicate with the radio access network device (using S1-U for data transmission), wherein the IP packet can directly reach the upper MEC server after passing through the lower MEC server; It is an off-path model, that is, a low-level MEC server exists, but the interface is reset to transmit data.
- IP packets need to be sent back to the base station after being sent to the lower-layer MEC server. IP packets to the upper MEC server.
- the capability information of the radio access network device can only be opened to the lower MEC server, but not to the upper MEC server. If the upper MEC server is to use the radio access network device The capability information can only be communicated to the high-level MEC server through the low-level MEC server (that is, the capability information of the radio access network device is opened by the lower-layer MEC server), and the deployment mode is called a cascade MEC server, which is a layered deployment mode. One of them. Using this deployment method not only has the excellent performance of the deployment mode 1 and the deployment mode 2 shown in FIG. 2a in the prior art, but Moreover, the signaling information processed by the radio access network device can be reduced, thereby reducing the processing load of the radio access network device.
- FIG. 2b is only a deployment scenario in the EPS system.
- the cascaded MEC server provided by the embodiment of the present invention can also be applied to a 2G network system, a 3G network system, a 4G network system, a 5G network system, and a future communication network.
- a 2G network system a low-level MEC server disposed in a radio access network is close to a base station controller (BSC).
- BSC base station controller
- the lower layer MEC server set in the radio access network is close to the RNC.
- the embodiment of the present invention focuses on opening the capability information of the radio access network device to the high-level MEC server through the low-level MEC server, and opening the service to the upper-layer MEC server to the edge service server in the high-level MEC server.
- FIG. 2d is an internal architecture diagram of an MEC server according to an embodiment of the present invention.
- the MEC server mainly includes a mobile edge platform, a routing network, and an edge service server, wherein the routing network is used to forward data (such as IP packets) or signaling (such as request for capability information collection and capability information). Feedback, etc.).
- the mobile edge platform provides services, such as registration services, RNIS, TOF, etc., and the registration service, the RNIS service, and the TOF service dynamically generate capability information obtained from the wireless access network device.
- the MEC server provided in FIG. 2d is deployed on the upper layer node of the radio access network in conjunction with FIG. 2b. As a high-level MEC server, the MEC server provided in FIG. 2d is deployed as a low-level MEC server.
- FIG. 2e is a structural diagram of an implementation system for capability opening according to an embodiment of the present invention.
- the mobile edge platform (the first mobile edge platform in the embodiment of the present invention) requests capability information from the radio access network device through the routing network, and then forwards the capability information to the mobile network by the routing network.
- the edge platform, and then the mobile edge platform provides the capability information to the mobile edge platform of the high-level MEC server (the second mobile edge platform in the embodiment of the present invention), and the mobile edge platform of the high-level MEC server provides the capability information to the edge service.
- Server the edge service server in the high-level MEC server.
- the data packet sent by the terminal (the IP packet includes the service request of the terminal, such as requesting location location), and the radio access network device reaches the routing network of the low-level MEC server.
- the routing network of the lower-layer MEC server In the in-band mode, the routing network of the lower-layer MEC server directly forwards the data packet to the routing network of the upper-layer MEC server, and then forwards the routing network of the upper-layer MEC server to the high-level MEC service.
- the edge of the business server In the outband mode, the routing network of the lower MEC server needs to transmit the data packet back to the radio access network device, and then the radio access network device sends the routing network to the upper MEC server, and then the routing network of the upper MEC server. Forwarded to the edge service server of the high-level MEC server.
- the focus is on how to use the low-level MEC server to open the capability information of the radio access network device to the high-level MEC server, and the acquisition and opening of the capability information are performed by the MEC platform of the MEC server.
- the cascading MEC server is actually deployed, only the location of the mobile edge platform in the MEC server is required, and the routing network and the edge service server may be located elsewhere, that is, the mobile edge platform needs to be deployed on the radio access network side. Deploy and deploy the mobile edge platform on the upper layer nodes of the radio access network. In general, the cascading mobile edge platform is actually implemented, but since each mobile edge platform belongs to a different MEC server, it is equivalent to A cascaded MEC server is deployed.
- a high-level MEC server can correspond to multiple low-level MEC servers.
- the capability information is also provided to the internal edge service server through the mobile edge platform, but the technology is prior art and will not be described in detail herein.
- FIG. 3 is a signaling diagram of a method for implementing capability opening according to an embodiment of the present invention. As shown in FIG. 3, an implementation method for capability opening may include:
- the first mobile edge platform sends a capability information request to the radio access network device by using the first routing network.
- the radio access network device includes an RNC, an eNodeB, or a BSC.
- the first mobile edge platform first sends the capability information request to the first routing network, and is forwarded by the first routing network.
- the radio access network device receives the capability information request, and sends the capability information to the first mobile edge platform by using the first routing network.
- the capability information includes channel signal status, cell load, terminal location information, network congestion, terminal identifier, and the like.
- the first mobile edge platform receives capability information, sets an API1 that opens the capability information to the second mobile edge platform, and configures the usage time of the API1.
- the first mobile edge platform is close to the radio access network device and has a location advantage from the radio access network.
- the capability information of the radio access network device is obtained in the device (that is, the radio access network device opens the capability information to the first mobile edge platform), and then saves.
- the first mobile edge platform sets API1 for acquiring the capability information, and the capability information of the radio access network device is further opened to the second mobile edge platform by using the API1, and the second mobile edge platform is provided to the second edge.
- Business server
- the capability information of the radio access network device is also updated, it is necessary to set the usage time of the API1, that is, the API1 is invalid after a certain period of use.
- the capability information request generated by the first mobile edge platform to the radio access network device and the capability information returned by the radio access network device are all considered as signaling, and the first reason network and the radio access network device Let the interface transfer.
- the first mobile edge platform sends registration information to the second mobile edge platform, where the registration information includes an identifier of the API1, an ID of the first mobile edge platform, and/or an ID of the radio access network device.
- the association relationship between the first mobile edge platform, the second mobile edge platform, and the radio access network device is set on the second mobile edge platform.
- the registration information includes an identifier of API1 to tell the second mobile edge platform to provide capability information to it through API1 in the future.
- the ID of the first mobile edge platform and/or the ID of the radio access network device may also be included, so that the second mobile edge platform can clearly determine the API 1 to be called when the capability information needs to be acquired to the first mobile edge platform.
- the identifier of API1 can be a URL or a URI.
- the second mobile edge platform receives the registration information, sets API2, and establishes a correspondence between API1 and API2, and opens the API2 to the second edge service server.
- the second edge service server initiates a request for searching the API2 to the second edge platform, and then the second edge platform will carry the request.
- the information of the identity of API2 is fed back to the second edge service server.
- the terminal sends an IP packet to the radio access network device.
- the radio access network device forwards the IP packet to the first routing network.
- the radio access network device sends the IP packet to the first routing network through the data interface.
- the first routing network forwards the IP packet to the second routing network.
- the second routing network forwards the IP packet to the second edge service server.
- the second edge service server obtains the ID of the radio access network device and/or the ID of the first mobile edge platform from the second mobile edge platform, and then determines the API2;
- the channel for transmitting the IP packet carries the ID of the radio access network device
- the second mobile edge platform can obtain the radio access network device corresponding to the IP packet according to the pre-configuration.
- the ID and/or the ID of the first mobile edge platform are then sent to the second edge service server either actively or at the request of the second edge service server.
- the second edge service server sends an API2 request to the second mobile edge platform, where the API2 request includes an identifier of the API2, an ID of the radio access network device, and/or an ID of the first mobile edge platform.
- API2 can be a URL or a URI.
- the API2 request in the embodiment of the present invention is a trigger request provided in another place, and is used to trigger the second mobile edge platform to request capability information to the first edge platform.
- the second mobile edge platform determines the API1 according to the ID of the radio access network device and/or the ID of the first mobile edge platform.
- the second mobile edge platform determines the API1 used to open the capability information according to the ID of the radio access network device and/or the ID of the first mobile edge platform (since the registration information includes the ID of the first mobile edge platform or the wireless The ID of the access network device, and the API1).
- the second mobile edge platform sends an API1 request to the first mobile edge platform, where the API1 request includes an identifier of the API1.
- the first mobile edge platform determines the usage time of the API1.
- the first mobile edge platform sends a capability information request to the radio access network device.
- the radio access network device receives the capability information request, and sends the capability information to the first mobile edge platform.
- the capability information here is the current capability information of the radio access network device, and the current capability information is the latest capability information before the time point when the first mobile edge platform receives the current capability information, which may be acquired in step 301.
- the capability information is the same or different.
- the first mobile edge platform receives capability information, and resets the usage time of the API1.
- the first mobile edge platform sends an API1 response to the second mobile edge platform, where
- the API1 response includes capability information or current capability information
- the second mobile edge platform receives the API1 response, and then obtains an API2 response, where the API2 response includes capability information included in the API1 response.
- first mobile edge platform sends an API1 response to the second mobile edge platform through the API1, and then the second mobile edge platform sends the API1 response to the second edge service server through the API2.
- the second mobile edge platform sends the API2 response to the second edge service server.
- the second edge service server After receiving the response of the API2, the second edge service server processes the IP packet to obtain a feedback IP packet.
- the second edge service server sends the feedback IP packet to the second routing network.
- the second routing network sends the returned IP packet to the first routing network.
- the first routing network forwards the returned IP packet to the radio access network device.
- the radio access network device sends the returned IP packet to the terminal.
- the in-band mode is mainly used.
- the capability information of the radio access network device is opened to the second mobile edge platform by using the first mobile edge platform.
- the second mobile edge platform sends an API1 request to the first mobile edge platform, because the second edge service server receives the IP packet of the terminal, determines the API2, and is from the second mobile edge platform. Obtaining the ID of the radio access network device corresponding to the IP packet and/or the ID of the first mobile edge platform, and then triggering the capability information to the second mobile edge platform.
- the first mobile edge platform is used to access the capability information of the radio access network device
- the capability information of the second mobile edge platform is used to open the capability information to the edge service server.
- the IP packet mentioned in all the embodiments of the present invention includes a service request of the terminal, for example, the terminal requests a location, a request video, and the like.
- the terminal requests the location location
- the terminal requests the location information from the edge service server of the upper MEC server by sending an IP packet.
- the edge service server After receiving the IP packet forwarded by the radio access network device and the low-level MEC server, the edge service server obtains the mobile edge platform from the lower-layer MEC server through the API2 interface and the API1 interface according to the requested location request in the IP packet. Obtaining the capability information required to locate the location of the terminal, such as the terminal location Set the information.
- the mobile edge platform of the high-level MEC server generates an IP packet feedback to the terminal according to the terminal location information.
- FIG. 4 is another signaling diagram of a method for implementing capability opening according to an embodiment of the present invention.
- an implementation method for capability opening may include:
- the first routing network forwards the IP packet to the radio access network device.
- the radio access network device forwards the IP packet to the second routing network.
- Steps 410 to 426 are the same as steps 409 to 425 described above, and are not described herein again.
- the embodiment of the present invention is applied to the outband mode. Therefore, in the embodiment of the present invention, the routing network of the lower layer MEC server cannot directly forward the IP packet to the routing network of the upper MEC server, and must be used by the radio access network device. The IP packet is forwarded to the routing network of the upper MEC server.
- the second mobile edge platform sends an API1 request to the first mobile edge platform, because the second edge service server receives the IP packet of the terminal, and obtains the IP packet from the second mobile edge platform.
- the ID of the first mobile edge platform and/or the ID of the radio access network device is then determined to be API2, which is triggered by sending an API2 request to the first mobile edge platform.
- FIG. 5 is another signaling diagram of a method for implementing capability opening according to an embodiment of the present invention. As shown in FIG. 5, an implementation method for capability opening may include:
- Steps 501-503 are the same as steps 301-303, and are not described here.
- the management network element sends the registration information to the second mobile edge platform.
- the mobile edge platform of the low-level MEC server actively sends registration information to the mobile edge platform of the high-level MEC server, which is a moving edge of the lower-layer MEC server in the embodiment of the present invention.
- the platform triggers the management network element to send registration information.
- step 505 is the same as step 305;
- the second edge service server sends an API2 request to the second mobile edge platform.
- the second edge service server actively initiates the API2 request, instead of triggering after receiving the IP packet of the terminal.
- the second edge service server may determine the API2 according to the preset association relationship, where the preset association relationship includes the association relationship between the radio access network device, the first mobile edge platform, and the second mobile edge platform, and the API2 and the API1. connection relation.
- steps 311 to 320 are the same as steps 311 to 320.
- the embodiment of the present invention may be applied to the inband mode or the outband mode.
- the registration information is sent by the management network element, and the management network element includes a mobile edge manager, a mobile edge orchestrator, and the like.
- the edge service server of the high-level MEC server actively initiates an API2 request to receive capability information without receiving an IP packet.
- the ID of the radio access network device and/or the ID of the first mobile edge platform may be obtained from the pre-configuration file or from the second mobile edge platform.
- FIG. 6 is a schematic structural diagram of a mobile edge platform according to an embodiment of the present invention. As shown in FIG. 6, a mobile edge platform 600 may include:
- the processing module 610 is configured to acquire capability information of the radio access network device, configure an application programming interface API, and set a usage time limit of the foregoing API, where the API is used by the mobile edge platform to provide the capability information to the second mobile edge platform;
- a registration service module 620 configured to trigger a registration function to send registration information to the second mobile edge platform, where the registration information includes an identifier of the API
- the processing module 610 is further configured to receive an API request sent by the second mobile edge platform, where the API request includes an identifier of the API, where the API request is used to request the capability information from the mobile edge platform, and the usage time of the API is detected. Whether the content is expired, and when it is detected that the usage aging of the API is not expired, the API response is sent to the second mobile edge platform by using the API, and the API response includes the capability information.
- the foregoing capability information includes a channel signal status, a cell load, a terminal location information, a network congestion, and a terminal identifier.
- the processing module 610 is further configured to: when detecting that the usage aging of the API has expired, acquiring current capability information of the radio access network device, where the current capability information is the radio access network. The capability information of the current time of the device; resetting the usage time of the foregoing API, and sending an API response including the current capability information to the second mobile edge platform by using the foregoing API.
- the registration service module 620 is specifically configured to send the registration information to the second mobile edge platform.
- the registration service module 620 is further configured to: trigger the management network element, and send the registration information to the second mobile edge platform by using the management network element.
- the processing module 610 is further configured to: provide the foregoing capability information to the first edge service server by using the foregoing API, where the first edge service server and the mobile edge platform are configured to calculate the MEC at the first mobile edge. In the server.
- FIG. 7 is another schematic structural diagram of a mobile edge platform according to some embodiments of the present invention.
- a mobile edge platform 700 may include:
- the registration service module 710 is configured to receive registration information, where the registration information includes an identifier of an application programming interface API, where the API is used by the first mobile edge platform to provide capability information to the mobile edge platform, where the capability information is a wireless access network device. Capability information;
- the processing module 720 is configured to send an API request to the first mobile edge platform, where the API request includes an identifier of the API, where the API request is used to request the capability information from the first mobile edge platform; and receive the first mobile edge platform.
- the API response sent, the above API response includes the above capability information.
- the foregoing capability information includes a channel signal status, a cell load, a terminal location information, a network congestion, and a terminal identifier.
- the processing module 720 is further configured to: before sending the foregoing API request to the first mobile edge platform, receive a trigger request sent by the second edge service server, where the trigger request includes the wireless access The identifier ID of the network device and/or the ID of the first mobile edge platform, the trigger request is used to trigger the mobile edge platform to send the API request to the first mobile edge platform, and the second edge service server and the mobile edge
- the platform is set in the second mobile edge computing MEC server; the API is determined according to the identity identifier of the wireless access network device and/or the ID of the first mobile edge platform.
- the processing module 720 is further configured to: after receiving the API response sent by the first mobile edge platform, provide the capability information to the second edge service server.
- the processing module 720 is specifically configured to receive the registration information sent by the first mobile edge platform.
- the processing module 720 is specifically configured to receive the foregoing registration information sent by the management network element.
- FIG. 8 is a schematic structural diagram of an MEC server according to an embodiment of the present invention. As shown in FIG. 8, an MEC server 800 includes the above-described mobile edge platform 600.
- the mobile edge platform 600 is the first mobile edge platform introduced in the embodiment of the present invention.
- the MEC server 800 further includes an edge service server 810, such as the first edge service server described above.
- the MEC server 800 also includes a routing network 820. Specifically, it is a first routing network provided in the embodiment of the present invention.
- FIG. 9 is a schematic structural diagram of an MEC server according to another embodiment of the present invention.
- an MEC server 900 includes: the mobile edge platform 700.
- the mobile edge platform 700 is the second mobile edge platform introduced in the embodiment of the present invention.
- the MEC server 900 further includes an edge service server 910, such as the second edge service server described above.
- the MEC server 900 also includes a routing network 920. Specifically, it is a second routing network provided in the embodiment of the present invention.
- FIG. 10 is a schematic structural diagram of an implementation system of an open capability according to an embodiment of the present invention.
- an open capability implementation system 1000 may include:
- the mobile edge platform 600 shown in FIG. 6 and the mobile edge platform 700 shown in FIG. 6 are identical to The mobile edge platform 600 shown in FIG. 6 and the mobile edge platform 700 shown in FIG.
- the above-described capability-enabled implementation system 1000 further includes a radio access network device 1010.
- the radio access network device 1010 is configured to provide capability information to the first mobile edge platform.
- the above-mentioned capability open implementation system 1000 further includes a terminal 1020, wherein the terminal 1020, the specific content may refer to the introduction of the above method embodiment.
- FIG. 11 is a schematic structural diagram of an implementation system of an open capability according to an embodiment of the present invention. As shown in FIG. 11, an open implementation system 1100 may include:
- the capability open implementation system 1100 further includes a terminal 1120.
- a terminal 1120 For details, refer to the introduction of the foregoing method embodiment.
- FIG. 12 is a schematic structural diagram of an apparatus for implementing capability opening according to an embodiment of the present invention, where at least one processor 1201 (for example, a CPU, Central Processing Unit), at least one network interface or other communication interface may be included. a memory 1202, and at least one communication bus, Used to implement connection communication between these devices.
- the processor 1201 is configured to execute an executable module, such as a computer program, stored in a memory.
- the memory 1202 may include a high speed random access memory (RAM), and may also include a non-volatile memory, such as at least one disk storage.
- the communication connection between the system gateway and at least one other network element is implemented by at least one network interface (which may be wired or wireless), and an Internet, a wide area network, a local network, a metropolitan area network, etc. may be used.
- program instructions are stored in the memory 1202, and the program instructions may be executed by the processor 1201.
- the processor 1201 specifically performs the following steps: acquiring capability information of the radio access network device. And configuring an application programming interface API for setting the capability information to the second mobile edge platform; and triggering a registration function to send registration information to the first a mobile edge platform, the registration information includes an identifier of the API, and an API request sent by the second mobile edge platform, where the API request includes an identifier of the API, and the API request is used to move to the mobile device
- the edge platform requests the capability information; detects whether the usage time of the API expires, and sends an API response to the second mobile edge platform by using the API when detecting that the usage time of the API is not expired,
- the API response includes the capability information.
- the registration information includes an identifier of an application programming interface API, where the API is used by the first mobile edge platform to provide capability information to the mobile edge platform, where the capability information is a capability of the radio access network device.
- the processor 1201 may further perform the following steps: acquiring, after detecting that the usage aging of the API has expired, acquiring current capability information of the radio access network device, where the current capability information is Determining capability information of the current time of the wireless access network device; resetting the usage time of the API, and sending an API response including the current capability information to the second mobile edge platform by using the API.
- the processor 1201 may further perform the step of transmitting the registration information to the second mobile edge platform.
- the processor 1201 may further perform the steps of: triggering a management network element, and transmitting, by the management network element, the registration information to the second mobile edge platform.
- the processor 1201 may further perform the step of: providing the capability information to the first edge service server by using the API, where the first edge service server and the mobile edge platform are set A mobile edge is calculated in the MEC server.
- the processor 1201 may further perform the step of: receiving a trigger request sent by the second edge service server before sending the API request to the first mobile edge platform, where the trigger request includes The identifier of the wireless access network device and/or the ID of the first mobile edge platform, the trigger request is used to trigger the mobile edge platform to send the API request to the first mobile edge platform, Setting the second edge service server and the mobile edge platform in the second mobile edge computing MEC server; determining according to the identity identifier of the wireless access network device and/or the ID of the first mobile edge platform Out of the API.
- the processor 1201 may further perform the step of: providing the capability information to the second edge service server after receiving the API response sent by the first mobile edge platform.
- the processor 1201 may further perform the step of receiving the registration information sent by the first mobile edge platform.
- the processor 1201 may further perform the step of receiving the registration information sent by the management network element.
- the disclosed system, apparatus, and method may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
- the coupling or communication connection may be an indirect coupling or communication connection through some interface, device or unit, and may be in electrical, mechanical or other form.
- the units described as separate components may or may not be physically separated, 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 invention 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.
- the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a 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 methods described in various embodiments of the present invention.
- 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)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
一种能力开放的实现方法、***及相关设备,实现了级联MEC服务器的部署,提高***性能。本发明一方法实施例包括:获取无线接入网设备的能力信息,并配置应用编程接口API以及设置上述API的使用时效,上述API用于向第二移动边缘平台提供上述能力信息;触发注册功能以将注册信息发送给上述第二移动边缘平台,上述注册信息包括上述API的标识;接收上述第二移动边缘平台发送的API请求,上述API请求包括上述API的标识;检测上述API的使用时效是否过期;若上述API的使用时效未过期,通过上述API向上述第二移动边缘平台发送API响应,上述API响应包括上述能力信息。
Description
本发明涉及无线通信技术领域,具体涉及一种能力开放的实现方法、***及相关设备。
移动边缘计算(Mobile Edge Computing,简称MEC)服务器在靠近移动用户的无线接入网(Radio Access Network,简称RAN)上提供了信息技术(Information Technology,简称IT)服务环境和云计算能力,创造了一个高度分布的环境用来部署应用和服务。图1为现有技术中MEC服务器的应用示意图,图1中MEC服务器包括底层基础设施(MEC hosting infrastructure)、移动边缘平台(MEC application platform)和边缘业务服务器,其中,底层基础设施包括MEC硬件资源层(MEC Hardware Resources)和MEC虚拟化层(MEC Virtualization Layer)。移动边缘平台是MEC服务器的核心,包括MEC虚拟管理层(MEC Virtualization Manager,如IaaS)和MEC应用服务平台(MEC application platform service),其中,MEC虚拟管理层的位置是可选择的,也可以位于其他位置,不在移动边缘平台中实现。MEC应用服务平台用于提供数据路由服务(Traffic Offload Function,简称TOF)、无线网络信息服务(Radio Network Information Service,简称RNIS)、通信服务(Communication Service)、注册服务等。在移动边缘平台中,通过注册服务模块将TOF服务、RNIS服务等开放给边缘业务服务器的虚拟机(Virtual Machine,简称VM)中的MEC应用程序(Application,简称APP)使用。
目前MEC服务器的部署多是考虑MEC服务器的位置,比如现有技术中存在三种部署场景:第一种是将MEC服务器部署在长期演进(Long-Term Evolution,简称LTE)的eNodeB侧,一个eNodeB侧部署一个MEC服务器;第二种是将MEC服务器部署在LTE或者第3代移动通信技术(The 3rd Generation Telecommunication,简称3G)的汇聚节点上,可以多个基站同用一个MEC服务器;第三种是MEC服务器部署在3G的无线网络控制器(Radio Network Controller,简称RNC)上,可以多个基站同用一个MEC服务器。其
中,第一种和第三种MEC服务器部署在无线接入网侧,可以减少时延、优化***性能,提高用户体验质量(Quality of Experience,简称QoE),第二种是在无线接入网的上一层节点,如3G的汇聚节点上,能够支持移动性。但是,上述三种部署方式都仅考虑MEC服务器位置,部署方式不够灵活,局限了MEC服务器的发展和应用。
发明内容
基于上述介绍,本发明提供了一种能力开放的实现方法、***及相关设备,用于实现更加灵活的MEC服务器部署,提高***性能。
本发明第一方面提供了一种能力开放的实现方法,可包括:
第一移动边缘平台获取无线接入网设备的能力信息,并配置应用编程接口API以及设置上述API的使用时效,上述API用于上述第一移动边缘平台向第二移动边缘平台提供上述能力信息;
上述第一移动边缘平台触发注册功能以将注册信息发送给上述第二移动边缘平台,上述注册信息包括上述API的标识;
上述第一移动边缘平台接收上述第二移动边缘平台发送的API请求,上述API请求包括上述API的标识,上述API请求用于向上述第一移动边缘平台请求上述能力信息;
上述第一移动边缘平台检测上述API的使用时效是否过期;
若上述API的使用时效未过期,上述第一移动边缘平台通过上述API向上述第二移动边缘平台发送API响应,上述API响应包括上述能力信息。
可以看出,在本发明第一方面中实现级联移动边缘平台的部署(具体是通过部署级联MEC服务器实现),级联移动边缘平台包括设置在无线接入网的第一移动边缘平台和设置在无线接入网的上一层节点中的第二移动边缘平台。基于该级联的第一移动边缘平台和第二移动边缘平台,由于第一移动边缘平台靠近于无线接入网设备,因此第一移动边缘平台能够获得无线接入网设备的能力信息并进行保存。之后,通过第一移动边缘平台触发注册功能,将无线接入网设备的能力信息提供给第二移动边缘平台(具体是第一移动边缘平台通过API接口来实现将无线接入网设备的能力信息提供给第二移动边缘平台),在减少无线接入网设备的处理负担外,提高***性能以及实现了灵活业务部署。
可选地,上述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
可选地,上述API的标识可以是统一资源定位符(Uniform Resource Locator,URL)或者统一资源标识符(Uniform Resource Identifier,简称URI)。
在本发明一些实施例中,第一方面提供的能力开放的实现方法还包括:若上述API的使用时效已过期,上述第一移动边缘平台获取上述无线接入网设备的当前能力信息,上述当前能力信息为上述无线接入网设备当前时间具备的能力信息;上述第一移动边缘平台重新设置上述API的使用时效,并通过上述API向上述第二移动边缘平台发送包括上述当前能力信息的API响应。
在本发明一些实施例中,上述第一移动边缘平台触发注册功能以将注册信息发送给上述第二移动边缘平台包括:上述第一移动边缘平台将上述注册信息发送给上述第二移动边缘平台。
在本发明一些实施例中,上述第一移动边缘平台触发注册功能以将注册信息发送给上述第二移动边缘平台包括:上述第一移动边缘平台触发管理网元,通过上述管理网元将上述注册信息发送给上述第二移动边缘平台。
在本发明一些实施例中,第一方面提供的能力开放的实现方法还包括:上述第一移动边缘平台通过上述API将上述能力信息提供给第一边缘业务服务器,上述第一边缘业务服务器与上述第一移动边缘平台设置在第一移动边缘计算MEC服务器中。
本发明第二方面提供了一种能力开放的实现方法,可包括:
第二移动边缘平台接收注册信息,上述注册信息包括应用编程接口API的标识,上述API用于上述第一移动边缘平台向上述第二移动边缘平台提供能力信息,上述能力信息为无线接入网设备的能力信息;
上述第二移动边缘平台向上述第一移动边缘平台发送API请求,上述API请求包括上述API的标识,上述API请求用于向上述第一移动边缘平台请求上述能力信息;
上述第二移动边缘平台接收上述第一移动边缘平台发送的API响应,上述API响应包括上述能力信息。
可以看出,基于在第一方面介绍的级联移动边缘平台,第二移动边缘平台
接收了注册信息后,通过发送包括有注册信息中的API的一个API请求,向第一移动边缘平台请求以获得无线接入网设备的能力信息,以分担无线接入网设备的处理负担,提高***性能以及推广移动边缘平台(或者说MEC服务器)的使用范围。
可选地,上述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
在本发明一些实施例中,上述第二移动边缘平台向上述第一移动边缘平台发送API请求之前包括:上述第二移动边缘平台接收第二边缘业务服务器发送的触发请求,上述触发请求中包括上述无线接入网设备的身份标识ID和/或上述第一移动边缘平台的ID,上述触发请求用于触发上述第二移动边缘平台向上述第一移动边缘平台发送上述API请求,上述第二边缘业务服务器和上述第二移动边缘平台设置在第二移动边缘计算MEC服务器中;上述第二移动边缘平台根据上述无线接入网设备的身份标识ID和/或上述第一移动边缘平台的ID,确定出上述API。
在本发明一些实施例中,上述第二移动边缘平台接收上述第一移动边缘平台发送的API响应之后包括:上述第二移动边缘平台向上述第二边缘业务服务器提供上述能力信息。
在本发明一些实施例中,上述第二移动边缘平台接收注册信息包括:上述第二移动边缘平台接收上述第一移动边缘平台发送的上述注册信息。
在本发明一些实施例中,上述第二移动边缘平台接收注册信息包括:上述第二移动边缘平台接收管理网元发送的上述注册信息。
本发明第三方面提供了一种移动边缘平台,可包括:
处理模块,用于获取无线接入网设备的能力信息,并配置应用编程接口API以及设置上述API的使用时效,上述API用于上述移动边缘平台向第二移动边缘平台提供上述能力信息;
注册服务模块,用于触发注册功能以将注册信息发送给上述第二移动边缘平台,上述注册信息包括上述API的标识;
上述处理模块还用于,接收上述第二移动边缘平台发送的API请求,上述API请求包括上述API的标识,上述API请求用于向上述移动边缘平台请求上
述能力信息;检测上述API的使用时效是否过期,并在检测到上述API的使用时效未过期时,通过上述API向上述第二移动边缘平台发送API响应,上述API响应包括上述能力信息。
可选地,上述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
在本发明一些实施例中,上述处理模块还用于,在检测到上述API的使用时效已过期时,获取上述无线接入网设备的当前能力信息,上述当前能力信息为上述无线接入网设备当前时间具备的能力信息;重新设置上述API的使用时效,并通过上述API向上述第二移动边缘平台发送包括上述当前能力信息的API响应。
在本发明一些实施例中,上述注册服务模块具体用于,将上述注册信息发送给上述第二移动边缘平台。
在本发明一些实施例中,上述注册服务模块还具体用于,触发管理网元,通过上述管理网元将上述注册信息发送给上述第二移动边缘平台。
在本发明一些实施例中,上述处理模块还用于,通过上述API将上述能力信息提供给第一边缘业务服务器,上述第一边缘业务服务器与上述移动边缘平台设置在第一移动边缘计算MEC服务器中。
本发明第四方面提供了一种移动边缘平台,可包括:
注册服务模块,用于接收注册信息,上述注册信息包括应用编程接口API的标识,上述API用于第一移动边缘平台向上述移动边缘平台提供能力信息,上述能力信息为无线接入网设备的能力信息;
处理模块,用于向上述第一移动边缘平台发送API请求,上述API请求包括上述API的标识,上述API请求用于向上述第一移动边缘平台请求上述能力信息;接收上述第一移动边缘平台发送的API响应,上述API响应包括上述能力信息。
可选地,上述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
在本发明一些实施例中,上述处理模块还用于,在向上述第一移动边缘平台发送上述API请求之前,接收第二边缘业务服务器发送的触发请求,上述触
发请求中包括上述无线接入网设备的身份标识ID和/或上述第一移动边缘平台的ID,上述触发请求用于触发上述移动边缘平台向上述第一移动边缘平台发送上述API请求,上述第二边缘业务服务器和上述移动边缘平台设置在第二移动边缘计算MEC服务器中;根据上述无线接入网设备的身份标识ID和/或上述第一移动边缘平台的ID,确定出上述API。
在本发明一些实施例中,上述处理模块还用于,在接收上述第一移动边缘平台发送的API响应之后,向上述第二边缘业务服务器提供上述能力信息。
在本发明一些实施例中,上述处理模块具体用于,接收上述第一移动边缘平台发送的上述注册信息。
在本发明一些实施例中,上述处理模块具体用于,接收管理网元发送的上述注册信息。
本发明第五方面提供了一种MEC服务器,可包括:第三方面提供的移动边缘平台或者第四方面提供的移动边缘平台。
在本发明一些实施例中,第五方面提供的MEC服务器还可以包括边缘业务服务器,其中,该移动边缘平台还用于向上述边缘业务服务器提供无线接入网设备的能力信息。
本发明第六方面提供了一种能力开放的实现***,可包括:第一移动边缘平台和第二移动边缘平台;其中,第一移动边缘平台为上述第一方面提供的移动边缘平台,第二移动边缘平台为上述第二方面提供的移动边缘平台。
在本发明一些实施例中,上述第六方面提供的能力开放的实现***中还包括无线接入网设备,该无线接入网设备用于向上述第一移动边缘平台提供能力信息。
在本发明一些实施例中,上述第六方面提供的能力开放的实现***还包括终端,其中,终端用于提供数据报文(IP报文)。
本发明第七方面还提供了一种能力开放的实现***,可包括:无线接入网设备、第一移动边缘计算MEC服务器和第二MEC服务器;其中,上述第一MEC服务器为第五方面提供的MEC服务器,上述第二MEC服务器为为第五方面提供的MEC服务器,上述第一MEC服务器中包括第三方面提供的移动边缘平台,上述第二MEC服务器包括第四方面提供的移动边缘平台。
为了更清楚地说明本发明实施例的技术方案,下面将对实施例描述所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为现有技术中MEC服务器的架构示意图;
图2a为现有技术提供的MEC服务器的部署场景示意图;
图2b为本发明一些实施例提供的级联MEC服务器的部署场景;
图2c为本发明实施例提供的MEC服务器与无线接入网设备之间通信的通信接口示意图;
图2d为本发明实施例基于图2b所部署的级联MEC服务器的内部架构图;
图2e为本发明实施例提供的能力开放的实现***的架构图;
图3为本发明一些实施例提供的能力开放的实现方法的信令图;
图4为本发明一些实施例提供的能力开放的实现方法的另一信令图;
图5为本发明一些实施例提供的能力开放的实现方法的另一信令图;
图6为本发明一些实施例提供的移动边缘平台的结构示意图;
图7为本发明另一些实施例提供的移动边缘平台的结构示意图;
图8为本发明一些实施例提供的MEC服务器的结构示意图;
图9为本发明另一些实施例提供的MEC服务器的结构示意图;
图10为本发明一些实施例提供的能力开放的实现***的结构示意图;
图11为本发明另一实施例提供的能力开放的实现***的结构示意图;
图12为本发明实施例提供的能力开放的实现装置的结构示意图。
本发明实施例提供了一种能力开发的实现方法,实现一种级联的MEC服务器部署模式,即可以获取无线接入网设备的能力信息,从而减少时延,快速接入,提高QoE,还可以提供移动性支持。本发明实施例还提供了能力开发的实现方法对应的***、以及移动边缘平台、MEC服务器。
为使得本发明的发明目的、特征、优点能够更加的明显和易懂,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行描述,显然,下
面所描述的实施例仅仅是本发明一部分实施例,而非全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例,都属于本发明保护的范围。
本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”“第四”等是用于区别不同的对象,而不是用于描述特定顺序。此外,术语“包括”和“具有”以及它们任何变形,意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、***、产品或设备没有限定于已列出的步骤或单元,而是可选地还包括没有列出的步骤或单元,或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
首先介绍一下常见的MEC服务器的部署方式,请参阅图2a,图2a为现有技术提供的MEC服务器的部署场景示意图。在图2a中,MEC服务器可以按照方式一部署在无线接入网侧,也就是设置于靠近无线接入网设备的S1-U接口上,图2a中无线接入网设备以eNodeB为例。在部署方式一中,由于MEC服务器具有天然的位置优势,能够靠近无线接入网设备以获取到无线接入网设备的能力信息,从而提供低时延、快接入和高带宽的本地化创新服务。或者,MEC服务器可以按照方式二部署在无线接入网与核心网之间的节点上,如3G网络中的汇聚网的汇聚节点上。在部署方式二中,MEC服务器能够支持基站移动性。
然而,图2a的部署方式一和部署方式二是以择一方式存在,即要么为以部署方式一部署MEC服务器,要么以部署方式二部署MEC服务器,在部署时重点考虑MEC服务器的位置,部署方式比较单一,灵活性不够,也不能充分利用MEC服务器功能以实现业务部署,提高MEC服务器的应用范围。
基于现有技术MEC服务器部署方式所存在的缺陷,本发明实施例实现一种级联MEC服务器的部署,级联MEC服务器是指包括两级或两级以上MEC服务器(本发明实施例中以两级MEC服务器实现的级联MEC服务器为例进行说明)。请参阅图2b,图2b为本发明一些实施例提供的级联MEC服务器的部署场景,在图2b中,把部署在无线接入网设备(图2b中以基站(eNodeB)为例)侧的MEC服务器称为低层MEC服务器(Low MEC),低层MEC服务器即本发明实施例中的第一MEC服务器,把部署在高层(即无线接入网与核心网之间
的节点,在图2b中以上一层节点为服务网关(Serving GateWay,简称SGW)以及分组数据网络网关(PDN GateWay,简称PGW)为例)的MEC服务器称为高层MEC服务器(High MEC),高层MEC服务器即本发明实施例中的第二MEC服务器。在此给予说明,在本发明后续实施例中,将以低层MEC服务器和高层MEC服务器进行阐述。
在此,还需要先说明一下MEC服务器与无线接入网设备之间通信时涉及的接口。请参阅图2c,图2c为本发明实施例提供的MEC服务器与无线接入网设备之间通信的通信接口示意图;在图2c中,MEC服务器与无线接入网设备之间包括两种功能接口:一种是数据接口,是无线接入网设备与MEC服务器之间传输数据(UE的IP报文)时使用;另一种是信令接口,是无线接入网设备与MEC服务器之间传输能力信息使用。其中,数据接口有两种实现方式:一种是外挂接口(即重新设置一个接口来使用),另一种是直接使用S1-U接口。信令接口也有两种实现方式:一种是重用数据接口(即数据接口同时用作数据接口和信令接口),另一种是外挂接口(即重新设置接口)。
结合图2c,图2b中在部署有高层MEC服务器的情况下,可以根据低层MEC服务器在数据面的位置分为两种模式:第一种为基于带内模式(On-path model),即低层MEC服务器存在且该低层MEC服务器直接采用S1-U接口与无线接入网设备通信(采用S1-U进行数据传输),其中,IP报文通过低层MEC服务器后可以直接到达高层MEC服务器;第二种为带外模式(Off-path model),即低层MEC服务器存在,但重新设置接口来传输数据,与带内模式相比,IP报文到达低层MEC服务器后需要回传到基站,才能继续转发IP报文到高层MEC服务器。
在图2b所示的带内模式和带外模式下,无线接入网设备的能力信息只能开放给低层MEC服务器,而不能开放给高层MEC服务器,高层MEC服务器如果要使用无线接入网设备的能力信息只能通过低层MEC服务器(即再由低层MEC服务器将无线接入网设备的能力信息开放给高层MEC服务器),进而将这种部署方式称为级联MEC服务器,是分层部署方式中的一种。使用这种部署方式不仅具有现有技术中如图2a所示的部署方式1和部署方式2的优良性能,而
且能够减少无线接入网设备处理的信令信息,从而降低无线接入网设备的处理负担。
上述图2b给出的仅是在EPS***中的部署场景,本发明实施例提供的级联MEC服务器还可以应用在2G网络***、3G网络***、4G网络***、5G网络***以及未来通信网络中。在2G网络***中,设置在无线接入网中的低层MEC服务器靠近基站控制器(Base Station Controller,简称BSC)。在3G网络***中,设置在无线接入网中的低层MEC服务器靠近RNC。
进一步说明,本发明实施例重点是通过低层MEC服务器将无线接入网设备的能力信息开放给高层MEC服务器,而开放给高层MEC服务器即是开放给高层MEC服务器中边缘业务服务器的业务使用。
请参阅图2d,图2d为本发明实施例提供的MEC服务器的内部架构图。在图2d中,MEC服务器中主要包括移动边缘平台、路由网络和边缘业务服务器,其中,路由网络用于转发数据(如IP报文)或者信令(如用于能力信息收集的请求以及能力信息的反馈等)。移动边缘平台提供服务,如注册服务、RNIS、TOF等,该注册服务、RNIS服务、TOF服务为从无线接入网设备获取到能力信息动态生成。结合图2b将图2d所提供的MEC服务器部署在无线接入网的上一层节点,作为高层MEC服务器,将图2d所提供的MEC服务器部署无线接入网侧作为低层MEC服务器。
请参阅图2e,图2e为本发明实施例提供的能力开放的实现***的架构图。在图2e中,在低层MEC服务器中,移动边缘平台(本发明实施例中的第一移动边缘平台)通过路由网络向无线接入网设备请求能力信息,然后由路由网络将能力信息转发到移动边缘平台,然后移动边缘平台将该能力信息提供该高层MEC服务器的移动边缘平台(在本发明实施例中的第二移动边缘平台),高层MEC服务器的移动边缘平台将能力信息再提供给边缘业务服务器(为高层MEC服务器中的边缘业务服务器)。
对于终端发送的数据报文(IP报文且该报文中包括终端的业务请求,如请求位置定位),经无线接入网设备到达低层MEC服务器的路由网络。若为带内模式,由低层MEC服务器的路由网络直接将该数据报文转发给高层MEC服务器的路由网络,再由高层MEC服务器的路由网络转发到高层MEC服务
器的边缘业务服务器上。若为带外模式,低层MEC服务器的路由网络需要将数据报文回传到无线接入网设备,再由无线接入网设备发送到高层MEC服务器的路由网络,再由高层MEC服务器的路由网络转发到高层MEC服务器的边缘业务服务器上。
可以理解,在本发明实施例中重点在于如何利用低层MEC服务器将无线接入网设备的能力信息开放给高层MEC服务器,而能力信息的获取和开放都由MEC服务器的MEC平台来完成,因此,在实际部署级联MEC服务器时,仅对MEC服务器中的移动边缘平台的位置有特殊要求,而路由网络和边缘业务服务器可以位于其它地方,也就是需要满足在无线接入网侧部署移动边缘平台部署和在无线接入网的上一层节点上部署移动边缘平台,总的来说,实际上是实现级联移动边缘平台,但是由于每个移动边缘平台属于不同的MEC服务器,也就等同于部署了级联MEC服务器。
需要说明,一个高层MEC服务器可以对应着多个低层MEC服务器。另外,在低层MEC服务器中,还通过移动边缘平台向其内部边缘业务服务器提供能力信息,但是该技术为现有技术,在此不再详细介绍。
下面将以具体实施例,详细介绍本发明技术方案。
请参阅图3,图3为本发明实施例提供的能力开放的实现方法的信令图;如图3所示,一种能力开放的实现方法可包括:
301、第一移动边缘平台通过第一路由网络向无线接入网设备发送能力信息请求;
其中,无线接入网设备包括RNC、eNodeB或者BSC等。第一移动边缘平台先将能力信息请求发送给第一路由网络,由第一路由网络进行转发。
302、无线接入网设备接收能力信息请求,经过第一路由网络向第一移动边缘平台发送能力信息;
其中,能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识等。
303、第一移动边缘平台接收能力信息,设置向第二移动边缘平台开放该能力信息的API1,并配置该API1的使用时效;
第一移动边缘平台接近无线接入网设备,具备位置优势能够从无线接入网
设备中获取到无线接入网设备的能力信息(即无线接入网设备将能力信息开放给第一移动边缘平台),然后进行保存。第一移动边缘平台针对获取到的能力信息,设置API1,通过该API1将无线接入网设备的能力信息进一步地开放给第二移动边缘平台,而第二移动边缘平台则可以提供给第二边缘业务服务器。
由于无线接入网设备的能力信息也会进行更新,因此,需要设置该API1的使用时效,也就是在一定使用时效后该API1无效。
还可以理解,第一移动边缘平台向无线接入网设备发生的能力信息请求以及无线接入网设备返回的能力信息都被认为是信令,由第一理由网络与无线接入网设备的信令接口传输。
304、第一移动边缘平台发送注册信息给第二移动边缘平台,该注册信息包括该API1的标识、第一移动边缘平台的ID和/或无线接入网设备的ID;
需要说明,本发明实施例在部署级联MEC服务器时,在第二移动边缘平台设置第一移动边缘平台、第二移动边缘平台和无线接入网设备三者的关联关系。注册信息中包括有API1的标识,以告诉第二移动边缘平台以后将通过API1向其提供能力信息。当然,还可以包括第一移动边缘平台的ID和/或无线接入网设备的ID,以便第二移动边缘平台能够清楚在需要向第一移动边缘平台获取能力信息时,确定需要调用的API1。
API1的标识可以是URL或者URI。
305、第二移动边缘平台接收该注册信息,设置API2,并建立API1与API2的对应关系,将该API2开放给第二边缘业务服务器;
需要说明,在第二移动边缘平台接收和保存注册信息后,在高层MEC服务器启动时,第二边缘业务服务器将向第二边缘平台发起查找该API2的请求,然后第二边缘平台将携带有该API2的标识的信息反馈给第二边缘业务服务器。
306、终端向无线接入网设备发送IP报文;
307、无线接入网设备将IP报文转发给第一路由网络;
其中,无线接入网设备通过数据接口将IP报文发送给第一路由网络。
308、第一路由网络将IP报文转发给第二路由网络;
309、第二路由网络将IP报文转发给第二边缘业务服务器;
310、第二边缘业务服务器从第二移动边缘平台中获取无线接入网设备的ID和/或第一移动边缘平台的ID,然后确定出API2;
需要说明,在本发明实施例中,用于传输IP报文的通道中携带着无线接入网设备的ID,第二移动边缘平台可以根据预先配置获取到IP报文对应的无线接入网设备的ID和/或第一移动边缘平台的ID,然后主动的或者在第二边缘业务服务器请求的时候发送给第二边缘业务服务器。
311、第二边缘业务服务器向第二移动边缘平台发送API2请求,该API2请求中包括API2的标识、无线接入网设备的ID和/或第一移动边缘平台的ID;
API2的标识可以是URL或者URI。
本发明实施例中的API2请求即为其它地方提供的触发请求,是用于触发第二移动边缘平台去向第一边缘平台请求能力信息。
312、第二移动边缘平台根据无线接入网设备的ID和/或第一移动边缘平台的ID,确定出API1;
第二移动边缘平台根据无线接入网设备的ID和/或第一移动边缘平台的ID,从而确定出用来开放能力信息的该API1(由于注册信息中包括第一移动边缘平台的ID或者无线接入网设备的ID,以及该API1)。
313、第二移动边缘平台向第一移动边缘平台发送API1请求,该API1请求中包括API1的标识;
314、第一移动边缘平台判断API1的使用时效;
315、如果该API1的使用时效已过期,第一移动边缘平台向无线接入网设备发送能力信息请求;
316、无线接入网设备接收能力信息请求,向第一移动边缘平台发送能力信息;
需要说明,这里的能力信息是无线接入网设备的当前能力信息,当前能力信息是在第一移动边缘平台接收到该当前能力信息的时间点之前的最新能力信息,可以与步骤301中获取的能力信息相同,也可以不同。
317、第一移动边缘平台接收能力信息,重新设置该API1的使用时效;
318、如果该API1的使用时效未过期,或者从无线接入网设备重新获取到当前能力信息后,第一移动边缘平台向第二移动边缘平台发送API1响应,该
API1响应中包括能力信息或者当前能力信息;
319、第二移动边缘平台接收该API1响应,然后得到API2响应,该API2响应包括该API1响应中包括的能力信息;
可以理解,第一移动边缘平台通过API1向第二移动边缘平台发送API1响应,然后第二移动边缘平台通过API2将API1响应发送给第二边缘业务服务器。
320、第二移动边缘平台将API2响应发送给第二边缘业务服务器;
321、第二边缘业务服务器接收到该API2响应后,对IP报文进行处理,得到反馈的IP报文;
322、第二边缘业务服务器将该反馈的IP报文发送给第二路由网络;
323、第二路由网络将反馈的IP报文发送给第一路由网络;
324、第一路由网络将反馈的IP报文转发给无线接入网设备;
325、无线接入网设备将反馈的IP报文发送给终端。
本发明实施例中主要用在带内模式下,在该实施例中,通过第一移动边缘平台将无线接入网设备的能力信息开放到第二移动边缘平台中。
进一步地,在本发明实施例中第二移动边缘平台向第一移动边缘平台发送API1请求,是由于第二边缘业务服务器接收到终端的IP报文,确定出API2,并从第二移动边缘平台获取到IP报文对应的无线接入网设备的ID和/或第一移动边缘平台的ID,然后向第二移动边缘平台请求能力信息而触发。利用第一移动边缘平台接近无线接入网设备的地理位置优势,获取无线接入网设备的能力信息,再利用第二移动边缘平台的地理位置优势,将能力信息开放给边缘业务服务器,即可以获取无线接入网设备的能力信息,从而减少时延,快速接入,提高QoE,还可以提供移动性支持。
本发明所有实施例中所提及的IP报文中包括了终端的业务请求,例如终端请求定位位置、请求视频等。以终端请求定位位置为例,终端通过发送IP报文向高层MEC服务器的边缘业务服务器请求位置信息。边缘业务服务器接收到经过无线接入网设备、低层MEC服务器转发过来的IP报文后,根据IP报文中所请求的定位位置请求,分别经过API2接口、API1接口从低层MEC服务器的移动边缘平台中获取到定位终端位置所需要的能力信息,比如终端位
置信息。最后,高层MEC服务器的移动边缘平台根据该终端位置信息生成IP报文反馈给终端。
请参阅图4,图4为本发明实施例提供的能力开放的实现方法的另一信令图;如图4所示,一种能力开放的实现方法可包括:
401~407;其中,步骤401~407与上述步骤301~307相同,在此不再赘述。
408、第一路由网络将IP报文转发给无线接入网设备;
409、无线接入网设备将IP报文转发给第二路由网络;
410~426;其中,步骤410~426与上述步骤409~425相同,在此不再赘述。
本发明实施例应用于带外模式,因此,在本发明实施例中,低层MEC服务器的路由网络不能直接将IP报文转发到高层MEC服务器的路由网络上,必须得由无线接入网设备将IP报文转发到高层MEC服务器的路由网络上。
还需要说明,在本发明实施例中,第二移动边缘平台向第一移动边缘平台发送API1请求,是由于第二边缘业务服务器接收到终端的IP报文,并从第二移动边缘平台获取到第一移动边缘平台的ID和/或无线接入网设备的ID,然后确定出API2,向第一移动边缘平台发送API2请求而触发。
请参阅图5,图5为本发明实施例提供的能力开放的实现方法的另一信令图;如图5所示,一种能力开放的实现方法可包括:
501~503;其中,步骤501~503与步骤301~303相同,在此不再赘述。
504、管理网元发送注册信息给第二移动边缘平台;
在上述图3及图4所示的实施例中,是由低层MEC服务器的移动边缘平台主动向高层MEC服务器的移动边缘平台发送注册信息,在本发明实施例中是由低层MEC服务器的移动边缘平台触发管理网元发送注册信息。
505与步骤305相同;
506、第二边缘业务服务器向第二移动边缘平台发送API2请求;
需要说明,在本发明中是由第二边缘业务服务器主动发起API2请求,而不是在接收到终端的IP报文后触发。第二边缘业务服务器可以根据预置的关联关系确定出API2,预置的关联关系中有无线接入网设备、第一移动边缘平台和第二移动边缘平台的关联关系,还有API2和API1的关联关系。
507~515与步骤311~320相同。
本发明实施例可以是应用于带内模式或带外模式,在本发明实施例中由管理网元发送注册信息,管理网元包括移动边缘管理器、移动边缘编排器等。而高层MEC服务器的边缘业务服务器在没有接收到IP报文的情况下主动发起API2请求,以请求能力信息。高层MEC服务器在主动发起API2请求时,可以从预配置文件或者从第二移动边缘平台获取无线接入网设备的ID和/或第一移动边缘平台的ID。
请参阅图6,图6为本发明实施例提供的移动边缘平台的结构示意图;如图6所示,一种移动边缘平台600可包括:
处理模块610,用于获取无线接入网设备的能力信息,并配置应用编程接口API以及设置上述API的使用时效,上述API用于上述移动边缘平台向第二移动边缘平台提供上述能力信息;
注册服务模块620,用于触发注册功能以将注册信息发送给上述第二移动边缘平台,上述注册信息包括上述API的标识;
上述处理模块610还用于,接收上述第二移动边缘平台发送的API请求,上述API请求包括上述API的标识,上述API请求用于向上述移动边缘平台请求上述能力信息;检测上述API的使用时效是否过期,并在检测到上述API的使用时效未过期时,通过上述API向上述第二移动边缘平台发送API响应,上述API响应包括上述能力信息。
可选地,上述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
在本发明一些实施例中,上述处理模块610还用于,在检测到上述API的使用时效已过期时,获取上述无线接入网设备的当前能力信息,上述当前能力信息为上述无线接入网设备当前时间具备的能力信息;重新设置上述API的使用时效,并通过上述API向上述第二移动边缘平台发送包括上述当前能力信息的API响应。
在本发明一些实施例中,上述注册服务模块620具体用于,将上述注册信息发送给上述第二移动边缘平台。
在本发明一些实施例中,上述注册服务模块620还具体用于,,触发管理网元,通过上述管理网元将上述注册信息发送给上述第二移动边缘平台。
在本发明一些实施例中,上述处理模块610还用于,通过上述API将上述能力信息提供给第一边缘业务服务器,上述第一边缘业务服务器与上述移动边缘平台设置在第一移动边缘计算MEC服务器中。
请参阅图7,图7为本发明一些实施例提供的移动边缘平台的另一结构示意图;如图7所示,一种移动边缘平台700可包括:
注册服务模块710,用于接收注册信息,上述注册信息包括应用编程接口API的标识,上述API用于第一移动边缘平台向上述移动边缘平台提供能力信息,上述能力信息为无线接入网设备的能力信息;
处理模块720,用于向上述第一移动边缘平台发送API请求,上述API请求包括上述API的标识,上述API请求用于向上述第一移动边缘平台请求上述能力信息;接收上述第一移动边缘平台发送的API响应,上述API响应包括上述能力信息。
可选地,上述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
在本发明一些实施例中,上述处理模块720还用于,在向上述第一移动边缘平台发送上述API请求之前,接收第二边缘业务服务器发送的触发请求,上述触发请求中包括上述无线接入网设备的身份标识ID和/或上述第一移动边缘平台的ID,上述触发请求用于触发上述移动边缘平台向上述第一移动边缘平台发送上述API请求,上述第二边缘业务服务器和上述移动边缘平台设置在第二移动边缘计算MEC服务器中;根据上述无线接入网设备的身份标识ID和/或上述第一移动边缘平台的ID,确定出上述API。
在本发明一些实施例中,上述处理模块720还用于,在接收上述第一移动边缘平台发送的API响应之后,向上述第二边缘业务服务器提供上述能力信息。
在本发明一些实施例中,上述处理模块720具体用于,接收上述第一移动边缘平台发送的上述注册信息。
在本发明一些实施例中,上述处理模块720具体用于,接收管理网元发送的上述注册信息。
请参阅图8,图8为本发明实施例提供的MEC服务器的结构示意图;如
图8所示,一种MEC服务器800包括:上述移动边缘平台600。
移动边缘平台600即本发明实施例中介绍的第一移动边缘平台。
进一步地,该MEC服务器800还包括边缘业务服务器810,如上述介绍的第一边缘业务服务器。
进一步地,MEC服务器800还包括路由网络820。具体为本发明实施例中提供的第一路由网络。
请参阅图9,图9为本发明另一些实施例提供的MEC服务器的结构示意图;如图9所示,一种MEC服务器900包括:上述移动边缘平台700。
移动边缘平台700即本发明实施例中介绍的第二移动边缘平台。
进一步地,该MEC服务器900还包括边缘业务服务器910,如上述介绍的第二边缘业务服务器。
进一步地,MEC服务器900还包括路由网络920。具体为本发明实施例中提供的第二路由网络。
请参阅图10,图10为本发明实施例提供的能力开放的实现***的结构示意图;如图10所示,一种能力开放的实现***1000可包括:
图6所示的移动边缘平台600和图7所示的移动边缘平台700。
进一步地,上述能力开放的实现***1000还包括无线接入网设备1010。其中,无线接入网设备1010用于向所述第一移动边缘平台提供能力信息.
再进一步地,上述能力开放的实现***1000还包括终端1020,其中,终端1020,具体内容可以参照上面方法实施例的介绍。
请参阅图11,图11为本发明实施例提供的能力开放的实现***的结构示意图;如图11所示,一种能力开放的实现***1100可包括:
图8所示的MEC服务器800和图9所示的MEC服务器900,以及无线接入网设备1110。
进一步地,该能力开放的实现***1100还包括终端1120,具体内容可以参照上面方法实施例的介绍。
请参考图12,图12为本发明实施例提供的能力开放的实现装置的结构示意图,其中,可包括至少一个处理器1201(例如CPU,Central Processing Unit),至少一个网络接口或者其它通信接口,存储器1202,和至少一个通信总线,
用于实现这些装置之间的连接通信。所述处理器1201用于执行存储器中存储的可执行模块,例如计算机程序。所述存储器1202可能包含高速随机存取存储器(RAM,Random Access Memory),也可能还包括非不稳定的存储器(non-volatile memory),例如至少一个磁盘存储器。通过至少一个网络接口(可以是有线或者无线)实现该***网关与至少一个其它网元之间的通信连接,可以使用互联网,广域网,本地网,城域网等。
如图12所示,在一些实施方式中,所述存储器1202中存储了程序指令,程序指令可以被处理器1201执行,所述处理器1201具体执行以下步骤:获取无线接入网设备的能力信息,并配置应用编程接口API以及设置所述API的使用时效,所述API用于所述移动边缘平台向第二移动边缘平台提供所述能力信息;触发注册功能以将注册信息发送给所述第二移动边缘平台,所述注册信息包括所述API的标识;接收所述第二移动边缘平台发送的API请求,所述API请求包括所述API的标识,所述API请求用于向所述移动边缘平台请求所述能力信息;检测所述API的使用时效是否过期,并在检测到所述API的使用时效未过期时,通过所述API向所述第二移动边缘平台发送API响应,所述API响应包括所述能力信息。
或者,接收注册信息,所述注册信息包括应用编程接口API的标识,所述API用于第一移动边缘平台向所述移动边缘平台提供能力信息,所述能力信息为无线接入网设备的能力信息;向所述第一移动边缘平台发送API请求,所述API请求包括所述API的标识,所述API请求用于向所述第一移动边缘平台请求所述能力信息;接收所述第一移动边缘平台发送的API响应,所述API响应包括所述能力信息。
在一些实施方式中,所述处理器1201还可以执行以下步骤:在检测到所述API的使用时效已过期时,获取所述无线接入网设备的当前能力信息,所述当前能力信息为所述无线接入网设备当前时间具备的能力信息;重新设置所述API的使用时效,并通过所述API向所述第二移动边缘平台发送包括所述当前能力信息的API响应。
在一些实施方式中,所述处理器1201还可以执行以下步骤:将所述注册信息发送给所述第二移动边缘平台。
在一些实施方式中,所述处理器1201还可以执行以下步骤:触发管理网元,通过所述管理网元将所述注册信息发送给所述第二移动边缘平台。
在一些实施方式中,所述处理器1201还可以执行以下步骤:通过所述API将所述能力信息提供给第一边缘业务服务器,所述第一边缘业务服务器与所述移动边缘平台设置在第一移动边缘计算MEC服务器中。
在一些实施方式中,所述处理器1201还可以执行以下步骤:在向所述第一移动边缘平台发送所述API请求之前,接收第二边缘业务服务器发送的触发请求,所述触发请求中包括所述无线接入网设备的身份标识ID和/或所述第一移动边缘平台的ID,所述触发请求用于触发所述移动边缘平台向所述第一移动边缘平台发送所述API请求,所述第二边缘业务服务器和所述移动边缘平台设置在第二移动边缘计算MEC服务器中;根据所述无线接入网设备的身份标识ID和/或所述第一移动边缘平台的ID,确定出所述API。
在一些实施方式中,所述处理器1201还可以执行以下步骤:在接收所述第一移动边缘平台发送的API响应之后,向所述第二边缘业务服务器提供所述能力信息。
在一些实施方式中,所述处理器1201还可以执行以下步骤:接收所述第一移动边缘平台发送的所述注册信息。
在一些实施方式中,所述处理器1201还可以执行以下步骤:接收管理网元发送的所述注册信息。
在上述实施例中,对各个实施例的描述都各有侧重,某个实施例中没有详述的部分,可以参见其他实施例的相关描述。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的***,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的***,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直
接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本发明各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上对本发明所提供的一种能力开放的实现方法、***及相关设备进行了详细介绍,对于本领域的一般技术人员,依据本发明实施例的思想,在具体实施方式及应用范围上均会有改变之处,综上所述,本说明书内容不应理解为对本发明的限制。
Claims (30)
- 一种能力开放的实现方法,其特征在于,包括:第一移动边缘平台获取无线接入网设备的能力信息,并配置应用编程接口API以及设置所述API的使用时效,所述API用于所述第一移动边缘平台向第二移动边缘平台提供所述能力信息;所述第一移动边缘平台触发注册功能以将注册信息发送给所述第二移动边缘平台,所述注册信息包括所述API的标识;所述第一移动边缘平台接收所述第二移动边缘平台发送的API请求,所述API请求包括所述API的标识,所述API请求用于向所述第一移动边缘平台请求所述能力信息;所述第一移动边缘平台检测所述API的使用时效是否过期;若所述API的使用时效未过期,所述第一移动边缘平台通过所述API向所述第二移动边缘平台发送API响应,所述API响应包括所述能力信息。
- 根据权利要求1所述的方法,其特征在于,所述方法还包括:若所述API的使用时效已过期,所述第一移动边缘平台获取所述无线接入网设备的当前能力信息,所述当前能力信息为所述无线接入网设备当前时间具备的能力信息;所述第一移动边缘平台重新设置所述API的使用时效,并通过所述API向所述第二移动边缘平台发送包括所述当前能力信息的API响应。
- 根据权利要求1或2所述的方法,其特征在于,所述第一移动边缘平台触发注册功能以将注册信息发送给所述第二移动边缘平台包括:所述第一移动边缘平台将所述注册信息发送给所述第二移动边缘平台。
- 根据权利要求1或2所述的方法,其特征在于,所述第一移动边缘平台触发注册功能以将注册信息发送给所述第二移动边缘平台包括:所述第一移动边缘平台触发管理网元,通过所述管理网元将所述注册信息发送给所述第二移动边缘平台。
- 根据权利要求1~4任一项所述的方法,其特征在于,所述方法还包括:所述第一移动边缘平台通过所述API将所述能力信息提供给第一边缘业务服务器,所述第一边缘业务服务器与所述第一移动边缘平台设置在第一移动 边缘计算MEC服务器中。
- 根据权利要求1~5任一项所述的方法,其特征在于,所述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
- 一种能力开放的实现方法,其特征在于,包括:第二移动边缘平台接收注册信息,所述注册信息包括应用编程接口API的标识,所述API用于所述第一移动边缘平台向所述第二移动边缘平台提供能力信息,所述能力信息为无线接入网设备的能力信息;所述第二移动边缘平台向所述第一移动边缘平台发送API请求,所述API请求包括所述API的标识,所述API请求用于向所述第一移动边缘平台请求所述能力信息;所述第二移动边缘平台接收所述第一移动边缘平台发送的API响应,所述API响应包括所述能力信息。
- 根据权利要求7所述的方法,其特征在于,所述第二移动边缘平台向所述第一移动边缘平台发送API请求之前包括:所述第二移动边缘平台接收第二边缘业务服务器发送的触发请求,所述触发请求中包括所述无线接入网设备的身份标识ID和/或所述第一移动边缘平台的ID,所述触发请求用于触发所述第二移动边缘平台向所述第一移动边缘平台发送所述API请求,所述第二边缘业务服务器和所述第二移动边缘平台设置在第二移动边缘计算MEC服务器中;所述第二移动边缘平台根据所述无线接入网设备的身份标识ID和/或所述第一移动边缘平台的ID,确定出所述API。
- 根据权利要求8所述的方法,其特征在于,所述第二移动边缘平台接收所述第一移动边缘平台发送的API响应之后包括:所述第二移动边缘平台向所述第二边缘业务服务器提供所述能力信息。
- 根据权利要求7~9任一项所述的方法,其特征在于,所述第二移动边缘平台接收注册信息包括:所述第二移动边缘平台接收所述第一移动边缘平台发送的所述注册信息。
- 根据权利要求7~9任一项所述的方法,其特征在于,所述第二移动边缘平台接收注册信息包括:所述第二移动边缘平台接收管理网元发送的所述注册信息。
- 根据权利要求7~11任一项所述的方法,其特征在于,所述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
- 一种移动边缘平台,其特征在于,包括:处理模块,用于获取无线接入网设备的能力信息,并配置应用编程接口API以及设置所述API的使用时效,所述API用于所述移动边缘平台向第二移动边缘平台提供所述能力信息;注册服务模块,用于触发注册功能以将注册信息发送给所述第二移动边缘平台,所述注册信息包括所述API的标识;所述处理模块还用于,接收所述第二移动边缘平台发送的API请求,所述API请求包括所述API的标识,所述API请求用于向所述移动边缘平台请求所述能力信息;检测所述API的使用时效是否过期,并在检测到所述API的使用时效未过期时,通过所述API向所述第二移动边缘平台发送API响应,所述API响应包括所述能力信息。
- 根据权利要求13所述的移动边缘平台,其特征在于,所述处理模块还用于,在检测到所述API的使用时效已过期时,获取所述无线接入网设备的当前能力信息,所述当前能力信息为所述无线接入网设备当前时间具备的能力信息;重新设置所述API的使用时效,并通过所述API向所述第二移动边缘平台发送包括所述当前能力信息的API响应。
- 根据权利要求13或14所述的ME平台,其特征在于,所述注册服务模块具体用于,将所述注册信息发送给所述第二移动边缘平台。
- 根据权利要求13或14所述的移动边缘平台,其特征在于,所述注册服务模块还具体用于,触发管理网元,通过所述管理网元将所述注册信息发送给所述第二移动边缘平台。
- 根据权利要求13~16任一项所述的ME平台,其特征在于,所述处理模块还用于,通过所述API将所述能力信息提供给第一边缘业务服务器,所述第一边缘业务服务器与所述移动边缘平台设置在第一移动边缘计算MEC服务器中。
- 根据权利要求13~16任一项所述的移动边缘平台,其特征在于,所述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
- 一种移动边缘平台,其特征在于,包括:注册服务模块,用于接收注册信息,所述注册信息包括应用编程接口API的标识,所述API用于第一移动边缘平台向所述移动边缘平台提供能力信息,所述能力信息为无线接入网设备的能力信息;处理模块,用于向所述第一移动边缘平台发送API请求,所述API请求包括所述API的标识,所述API请求用于向所述第一移动边缘平台请求所述能力信息;接收所述第一移动边缘平台发送的API响应,所述API响应包括所述能力信息。
- 根据权利要求19所述的移动边缘平台,其特征在于,所述处理模块还用于,在向所述第一移动边缘平台发送所述API请求之前,接收第二边缘业务服务器发送的触发请求,所述触发请求中包括所述无线接入网设备的身份标识ID和/或所述第一移动边缘平台的ID,所述触发请求用于触发所述移动边缘平台向所述第一移动边缘平台发送所述API请求,所述第二边缘业务服务器和所述移动边缘平台设置在第二移动边缘计算MEC服务器中;根据所述无线接入网设备的身份标识ID和/或所述第一移动边缘平台的ID,确定出所述API。
- 根据权利要求20所述的移动边缘平台,其特征在于,所述处理模块还用于,在接收所述第一移动边缘平台发送的API响应之后,向所述第二边缘业务服务器提供所述能力信息。
- 根据权利要求19~21任一项所述的移动边缘平台,其特征在于,所述处理模块具体用于,接收所述第一移动边缘平台发送的所述注册信息。
- 根据权利要求19~21任一项所述的移动边缘平台,其特征在于,所述处理模块具体用于,接收管理网元发送的所述注册信息。
- 根据权利要求19~23任一项所述的移动边缘平台,其特征在于,所述能力信息包括信道信号状态、小区负载、终端位置信息、网络拥塞、终端标识。
- 一种MEC服务器,其特征在于,包括:移动边缘计算移动边缘平台;其中,所述移动边缘平台为权利要求13~18任一项所述的移动边缘平台;或,所述移动边缘平台为权利要求19~26任一项所述的移动边缘平台。
- 根据权利要求25所述的MEC服务器,其特征在于,所述MEC服务器还包括边缘业务服务器;所述移动边缘平台还用于向所述边缘业务服务器提供无线接入网设备的能力信息。
- 一种能力开放的实现***,其特征在于,包括:第一移动边缘平台和第二移动边缘平台;其中,所述第一移动边缘平台为权利要求13~18任一项所述的移动边缘平台,所述第二移动边缘平台为权利要求19~26任一项所述的移动边缘平台。
- 根据权利要求27所述的***,其特征在于,所述***还包括无线接入网设备;所述无线接入网设备用于向所述第一移动边缘平台提供能力信息。
- 根据权利要求28所述的***,其特征在于,所述***还包括终端。
- 一种能力开发的实现***,其特征在于,包括:无线接入网设备、第一移动边缘计算MEC服务器和第二MEC服务器;其中,所述第一MEC服务器为权利要求25或26所述的MEC服务器,所述第二MEC服务器为权利要求25或26所述的MEC服务器,所述第一MEC服务器中包括权利要求13~18任一项所述的移动边缘平台,所述第二MEC服务器包括权利要求19~26任一项所述的移动边缘平台。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201580084467.1A CN108353067B (zh) | 2015-11-30 | 2015-11-30 | 一种能力开放的实现方法、***及相关设备 |
PCT/CN2015/095940 WO2017091934A1 (zh) | 2015-11-30 | 2015-11-30 | 一种能力开放的实现方法、***及相关设备 |
EP15909451.5A EP3373542B1 (en) | 2015-11-30 | 2015-11-30 | Capability enablement method, system and related device |
US15/988,019 US10299239B2 (en) | 2015-11-30 | 2018-05-24 | Capability exposure implementation method and system, and related device |
US16/392,100 US10470150B2 (en) | 2015-11-30 | 2019-04-23 | Capability exposure implementation method and system, and related device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2015/095940 WO2017091934A1 (zh) | 2015-11-30 | 2015-11-30 | 一种能力开放的实现方法、***及相关设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/988,019 Continuation US10299239B2 (en) | 2015-11-30 | 2018-05-24 | Capability exposure implementation method and system, and related device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017091934A1 true WO2017091934A1 (zh) | 2017-06-08 |
Family
ID=58796016
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/095940 WO2017091934A1 (zh) | 2015-11-30 | 2015-11-30 | 一种能力开放的实现方法、***及相关设备 |
Country Status (4)
Country | Link |
---|---|
US (2) | US10299239B2 (zh) |
EP (1) | EP3373542B1 (zh) |
CN (1) | CN108353067B (zh) |
WO (1) | WO2017091934A1 (zh) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109495929A (zh) * | 2017-09-12 | 2019-03-19 | 华为技术有限公司 | 一种业务处理方法、移动边缘计算设备及网络设备 |
CN109542458A (zh) * | 2017-09-19 | 2019-03-29 | 华为技术有限公司 | 一种应用程序管理的方法及设备 |
CN109818868A (zh) * | 2017-11-20 | 2019-05-28 | 中兴通讯股份有限公司 | 一种实现边缘网络能力开放的方法、装置、设备及存储介质 |
CN110098947A (zh) * | 2018-01-31 | 2019-08-06 | 华为技术有限公司 | 一种应用的部署方法、设备及*** |
CN110545307A (zh) * | 2019-07-19 | 2019-12-06 | 中移(杭州)信息技术有限公司 | 边缘计算平台、调用方法及计算机可读存储介质 |
CN111345008A (zh) * | 2017-11-22 | 2020-06-26 | 华为技术有限公司 | 移动边缘主机服务通知方法和装置 |
CN111338573A (zh) * | 2020-02-19 | 2020-06-26 | 中国联合网络通信集团有限公司 | 终端数据管理方法及***、服务器和通信终端 |
CN113300899A (zh) * | 2020-04-15 | 2021-08-24 | 阿里巴巴集团控股有限公司 | 网络能力开放方法、网络***、设备及存储介质 |
EP3809766A4 (en) * | 2018-07-16 | 2021-09-01 | Huawei Technologies Co., Ltd. | PROCESS AND DEVICE FOR ACQUIRING INFORMATION MEC |
WO2022057497A1 (zh) * | 2020-09-16 | 2022-03-24 | 中兴通讯股份有限公司 | 网络能力开放方法、设备及存储介质 |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
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 |
US10728744B2 (en) * | 2018-04-27 | 2020-07-28 | Hewlett Packard Enterprise Development Lp | Transmission outside of a home network of a state of a MEC application |
CN111092802B (zh) * | 2018-10-23 | 2022-09-16 | ***通信有限公司研究院 | 一种消息交互方法、发送设备及接收设备 |
TWI674780B (zh) * | 2018-11-23 | 2019-10-11 | 財團法人工業技術研究院 | 網路服務系統及網路服務方法 |
TWI675572B (zh) * | 2018-11-23 | 2019-10-21 | 財團法人工業技術研究院 | 網路服務系統及網路服務方法 |
CN109861867B (zh) * | 2019-02-28 | 2022-04-26 | 新华三技术有限公司 | 一种mec业务处理方法及装置 |
CN110061857B (zh) * | 2019-03-13 | 2022-04-26 | 武汉星耀科技有限公司 | 一种多mec能力开放和共享的方法及*** |
CN111726381A (zh) * | 2019-03-20 | 2020-09-29 | 大唐移动通信设备有限公司 | 一种网络能力开放的实现方法及装置 |
US10819434B1 (en) | 2019-04-10 | 2020-10-27 | At&T Intellectual Property I, L.P. | Hybrid fiber coaxial fed 5G small cell surveillance with hybrid fiber coaxial hosted mobile edge computing |
US10848988B1 (en) | 2019-05-24 | 2020-11-24 | At&T Intellectual Property I, L.P. | Dynamic cloudlet fog node deployment architecture |
CN110661868B (zh) * | 2019-09-25 | 2022-06-21 | 浙江九州云信息科技有限公司 | 一种可拓展的可视化应用部署的解决方法 |
US11019140B1 (en) * | 2019-11-12 | 2021-05-25 | Verizon Patent And Licensing Inc. | Systems and methods for peer-to-peer data exchange via multi-access edge computing |
TWI734270B (zh) * | 2019-11-25 | 2021-07-21 | 財團法人工業技術研究院 | 接取私有網路服務之方法及系統 |
US11770734B2 (en) * | 2020-01-28 | 2023-09-26 | Verizon Patent And Licensing Inc. | Method and system for edge network exposure function with MEC network |
CN111669751B (zh) * | 2020-05-07 | 2022-07-29 | 中国联合网络通信集团有限公司 | 一种数据流的建立方法、装置及通信*** |
CN114844945A (zh) * | 2021-02-01 | 2022-08-02 | ***通信有限公司研究院 | 网络能力管理方法、能力开放平台及网络能力管理*** |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003026319A2 (en) * | 2001-09-21 | 2003-03-27 | Nokia Corporation | System and method for enabling mobile edge services |
CN101431425A (zh) * | 2007-11-09 | 2009-05-13 | 百视通网络电视技术发展有限责任公司 | 一种基于网络共享数据中心的分布式epg***及其业务流程 |
EP2146475A1 (en) * | 2007-05-07 | 2010-01-20 | Vodafone Group PLC | Access to information on a mobile terminal from a remote terminal |
CN102624939A (zh) * | 2011-01-28 | 2012-08-01 | 株式会社Ntt都科摩 | 用于确定应当响应服务请求的服务器的方法与装置 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050273668A1 (en) * | 2004-05-20 | 2005-12-08 | Richard Manning | Dynamic and distributed managed edge computing (MEC) framework |
CN1694480A (zh) * | 2005-05-08 | 2005-11-09 | 中国科学院计算技术研究所 | 一种面向语义关联的异构电信网络业务互联互通方法 |
CN101039315B (zh) * | 2006-03-16 | 2012-01-25 | 华为技术有限公司 | 与业务无关的接入网会话控制***及方法 |
CN101374247A (zh) * | 2007-08-23 | 2009-02-25 | 华为技术有限公司 | 在下一代网络中处理业务的方法、装置及下一代网络 |
CN102196012B (zh) * | 2010-03-17 | 2013-08-07 | 华为技术有限公司 | 服务开放方法及***、服务开放服务器 |
US8844032B2 (en) * | 2012-03-02 | 2014-09-23 | Sri International | Method and system for application-based policy monitoring and enforcement on a mobile device |
CN102624926B (zh) * | 2012-04-11 | 2016-02-10 | 中兴通讯股份有限公司 | 能力聚合开放的方法和*** |
EP2938131B1 (en) * | 2012-12-31 | 2018-11-14 | Huawei Technologies Co., Ltd. | Capability exposure system, gateway, proxy, and method of wireless network |
US9397878B2 (en) * | 2013-01-29 | 2016-07-19 | Qualcomm Incorporated | Cross-platform module that is shared by client applications for access to rich communications suite resources on a client device |
WO2015027246A1 (en) * | 2013-08-23 | 2015-02-26 | Samsung Electronics Co., Ltd. | Mobile software defined networking (mobisdn) |
WO2015141970A1 (en) * | 2014-03-17 | 2015-09-24 | Lg Electronics Inc. | Method and apparatus for handling ran assistance information for cell change in wireless communication system |
US10542482B2 (en) * | 2015-02-12 | 2020-01-21 | Nokia Solutions And Networks Oy | Access control to services in a network |
EP3313027B1 (en) * | 2015-07-31 | 2020-02-26 | Huawei Technologies Co., Ltd. | Routing rule acquisition method and system |
-
2015
- 2015-11-30 CN CN201580084467.1A patent/CN108353067B/zh active Active
- 2015-11-30 EP EP15909451.5A patent/EP3373542B1/en active Active
- 2015-11-30 WO PCT/CN2015/095940 patent/WO2017091934A1/zh active Application Filing
-
2018
- 2018-05-24 US US15/988,019 patent/US10299239B2/en active Active
-
2019
- 2019-04-23 US US16/392,100 patent/US10470150B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003026319A2 (en) * | 2001-09-21 | 2003-03-27 | Nokia Corporation | System and method for enabling mobile edge services |
EP2146475A1 (en) * | 2007-05-07 | 2010-01-20 | Vodafone Group PLC | Access to information on a mobile terminal from a remote terminal |
CN101431425A (zh) * | 2007-11-09 | 2009-05-13 | 百视通网络电视技术发展有限责任公司 | 一种基于网络共享数据中心的分布式epg***及其业务流程 |
CN102624939A (zh) * | 2011-01-28 | 2012-08-01 | 株式会社Ntt都科摩 | 用于确定应当响应服务请求的服务器的方法与装置 |
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109495929A (zh) * | 2017-09-12 | 2019-03-19 | 华为技术有限公司 | 一种业务处理方法、移动边缘计算设备及网络设备 |
US11252259B2 (en) | 2017-09-12 | 2022-02-15 | Huawei Technologies Co., Ltd. | Service processing method, mobile edge computing device, and network device |
EP3668174A4 (en) * | 2017-09-12 | 2020-08-19 | Huawei Technologies Co., Ltd. | SERVICE PROCESSING PROCESS, MOBILE NETWORK PERIPHERAL CALCULATION DEVICE AND NETWORK DEVICE |
AU2018332696B2 (en) * | 2017-09-12 | 2021-08-12 | Huawei Technologies Co., Ltd. | Service processing method, mobile edge computing device, and network device |
CN109542458A (zh) * | 2017-09-19 | 2019-03-29 | 华为技术有限公司 | 一种应用程序管理的方法及设备 |
US11307914B2 (en) | 2017-09-19 | 2022-04-19 | Huawei Technologies Co., Ltd. | Method and device for managing application program |
EP3667489A4 (en) * | 2017-09-19 | 2020-11-11 | Huawei Technologies Co., Ltd. | APPLICATION PROGRAM MANAGEMENT PROCESS AND DEVICE |
CN109818868B (zh) * | 2017-11-20 | 2021-06-22 | 中兴通讯股份有限公司 | 一种实现边缘网络能力开放的方法、装置、设备及存储介质 |
CN109818868A (zh) * | 2017-11-20 | 2019-05-28 | 中兴通讯股份有限公司 | 一种实现边缘网络能力开放的方法、装置、设备及存储介质 |
US11425225B2 (en) | 2017-11-20 | 2022-08-23 | Zte Corporation | Method, apparatus, and equipment for exposing edge network capability, and storage medium |
CN111345008A (zh) * | 2017-11-22 | 2020-06-26 | 华为技术有限公司 | 移动边缘主机服务通知方法和装置 |
EP3703337A4 (en) * | 2017-11-22 | 2020-09-02 | Huawei Technologies Co., Ltd. | EDGE MOBILE HOST MACHINE SERVICE NOTIFICATION PROCESS AND APPARATUS |
CN111345008B (zh) * | 2017-11-22 | 2022-06-10 | 华为技术有限公司 | 移动边缘主机服务通知方法和装置 |
US11432137B2 (en) | 2017-11-22 | 2022-08-30 | Huawei Technologies Co., Ltd. | Service notification method for mobile edge host and apparatus |
CN110098947B (zh) * | 2018-01-31 | 2021-01-29 | 华为技术有限公司 | 一种应用的部署方法、设备及*** |
CN110098947A (zh) * | 2018-01-31 | 2019-08-06 | 华为技术有限公司 | 一种应用的部署方法、设备及*** |
EP3809766A4 (en) * | 2018-07-16 | 2021-09-01 | Huawei Technologies Co., Ltd. | PROCESS AND DEVICE FOR ACQUIRING INFORMATION MEC |
US11540244B2 (en) | 2018-07-16 | 2022-12-27 | Huawei Technologies Co., Ltd. | MEC information obtaining method and apparatus |
CN110545307A (zh) * | 2019-07-19 | 2019-12-06 | 中移(杭州)信息技术有限公司 | 边缘计算平台、调用方法及计算机可读存储介质 |
CN111338573A (zh) * | 2020-02-19 | 2020-06-26 | 中国联合网络通信集团有限公司 | 终端数据管理方法及***、服务器和通信终端 |
CN111338573B (zh) * | 2020-02-19 | 2023-06-06 | 中国联合网络通信集团有限公司 | 终端数据管理方法及***、服务器和通信终端 |
CN113300899A (zh) * | 2020-04-15 | 2021-08-24 | 阿里巴巴集团控股有限公司 | 网络能力开放方法、网络***、设备及存储介质 |
WO2022057497A1 (zh) * | 2020-09-16 | 2022-03-24 | 中兴通讯股份有限公司 | 网络能力开放方法、设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
EP3373542A1 (en) | 2018-09-12 |
US20190253995A1 (en) | 2019-08-15 |
CN108353067A (zh) | 2018-07-31 |
EP3373542A4 (en) | 2018-10-03 |
US10470150B2 (en) | 2019-11-05 |
US10299239B2 (en) | 2019-05-21 |
CN108353067B (zh) | 2020-06-02 |
EP3373542B1 (en) | 2020-07-29 |
US20180270780A1 (en) | 2018-09-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017091934A1 (zh) | 一种能力开放的实现方法、***及相关设备 | |
TWI655877B (zh) | 用以選擇網路切片的使用者設備註冊方法、及使用此方法的網路控制器與網路通訊系統 | |
JP7183416B2 (ja) | 時間依存ネットワーキング通信方法及び装置 | |
JP6692936B2 (ja) | ネットワークスライス発見および選択 | |
KR102445355B1 (ko) | 사용자 그룹에 대한 세션 관리 방법 및 장치 | |
US20170048876A1 (en) | Enabling high-bandwidth, responsive mobile applications in lte networks | |
JP6727341B2 (ja) | 通信制御方法および関連するネットワーク要素 | |
WO2018161803A1 (zh) | 一种网络切片的选择方法及装置 | |
JP2021518075A (ja) | サービス加入方法および装置 | |
EP2717538A1 (en) | Communication method and system, access network device, and application server | |
WO2019105470A1 (zh) | 一种用户群组的建立方法及装置 | |
US20160006606A1 (en) | Customizable mobile broadband network system and method for customizing mobile broadband network | |
KR102469973B1 (ko) | 통신 방법 및 장치 | |
EP2953400A1 (en) | Service providing system, method, mobile edge application server and support node | |
WO2017070958A1 (zh) | 一种网关配置方法和网关设备 | |
WO2019196811A1 (zh) | 通信方法和相关装置 | |
US10623286B2 (en) | Anchor mobility in wireless networks | |
WO2017156706A1 (zh) | 用于处理数据包的方法及设备 | |
EP2700195B1 (en) | Technique for controlling and handling probe tunnel set up | |
JP2021158664A (ja) | 間接通信用のエラー処理のための方法、装置、およびコンピュータプログラム製品 | |
US20200280892A1 (en) | Session context handling method, network element, and terminal device | |
US11082893B2 (en) | Session migration method and device applied to a UE tracking area update | |
WO2019076308A1 (zh) | 终端设备的状态的确定方法、装置及设备 | |
EP4024912A1 (en) | Network slice charging method and device | |
WO2021078792A1 (en) | Mechanism for controlling service migration |
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: 15909451 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015909451 Country of ref document: EP |