WO2019052376A1 - 一种业务处理方法、移动边缘计算设备及网络设备 - Google Patents
一种业务处理方法、移动边缘计算设备及网络设备 Download PDFInfo
- Publication number
- WO2019052376A1 WO2019052376A1 PCT/CN2018/104032 CN2018104032W WO2019052376A1 WO 2019052376 A1 WO2019052376 A1 WO 2019052376A1 CN 2018104032 W CN2018104032 W CN 2018104032W WO 2019052376 A1 WO2019052376 A1 WO 2019052376A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- computing device
- edge computing
- service
- mobile edge
- service request
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
-
- 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
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Definitions
- the present application relates to the field of communications technologies, and in particular, to a service processing method, a mobile edge computing device, and a network device.
- MEC In the capability open architecture shown in Figure 1, some of the data processing and storage functions are advanced to the MEC.
- An MEC is set in each preset area, and the MEC in the area performs centralized processing on the service request of the terminal equipment in the area.
- the service processing method in the prior art may cause the resource utilization of the MEC to be low.
- the embodiments of the present application provide a service processing method, a mobile edge computing device, and a network device, which are used to solve the technical problem of low resource utilization of the MEC existing in the prior art.
- the embodiment of the present application provides a service processing method, where the method may be applied to a first mobile edge computing device, where the first mobile edge computing device may be any mobile edge computing device in a capability open architecture.
- the second mobile edge computing device may send a second service request, where the second service request includes the At least part of the service type of the service type and/or at least part of the service content of the service content, and the identification information of the first mobile edge computing device, and finally receiving the second service from the second mobile edge computing device Request the corresponding business data.
- the mobile edge computing device may forward part of the service or all services in the service request to other mobile edge computing devices for processing, so that when a mobile edge computing device receives a large number of When the service is requested, the service request may be forwarded to the idle mobile edge computing device for processing, so that the multiple mobile edge computing devices can cooperate to process the service request, which can improve the resource utilization of the mobile edge computing device.
- the first mobile edge computing device calculates the service type deployed by the device according to the first mobile edge computing device. And/or the service content, determining that the first mobile edge computing device needs to send the second service request to the second mobile edge computing device.
- the mobile edge computing device may determine whether the mobile edge computing device itself can process according to the locally deployed service type and/or service content, and if not, determine that forwarding is required. Processing other mobile edge computing devices and then forwarding the service request to other mobile edge computing devices can improve business processing efficiency.
- the first mobile edge computing device determines the second according to the information list of the mobile edge computing device. a mobile edge computing device; wherein the information of the second mobile edge computing device is included in the information list of the mobile edge computing device.
- the mobile edge computing device may first determine, according to the information list of the mobile edge computing device, the second mobile edge computing device capable of processing the service request, and then forward the service request to The determined mobile edge computing device, thereby saving signaling resources between the mobile edge computing devices, can improve service processing efficiency.
- the information list of the mobile edge computing device includes the identification information of the at least one mobile edge computing device; or the information list of the mobile edge computing device includes the identification information of the at least one mobile edge computing device and the corresponding The type of business and/or business content deployed by the mobile edge computing device.
- the information list of the mobile edge computing device may be identification information including only some or all of the mobile edge computing devices.
- the information list of the mobile edge computing device locally stored by the first mobile edge computing device may only include the information list.
- the identification information of the neighbor mobile edge computing device can save the storage space of the mobile edge computing device;
- the information list of the mobile edge device may also include the identification information of some or all of the mobile edge computing devices and the service type and/or service content deployed by the corresponding mobile edge computing device, such that the first mobile edge computing device may list the information according to the information. Accurately determining the second mobile edge computing device capable of processing the service request can improve service processing efficiency.
- the information list of the mobile edge computing device is deployed in the first mobile edge computing device, and the first mobile edge computing device queries the information list of the mobile edge computing device, and determines that the At least one mobile edge computing device of the second service request, the first mobile edge computing device then transmitting a first query message to the at least one mobile edge computing device, the first query message including at least a portion of the traffic type of the service type and And/or at least part of the business content of the business content, and receiving a response message from the at least one mobile edge computing device, and finally determining the second mobile edge computing device from the at least one mobile edge computing device based on the received response message.
- the first mobile edge computing device may determine the second mobile edge computing device according to the information list of the locally deployed mobile edge computing device by sending an inquiry message, so that each mobile edge computing device may perform current processing according to the current processing.
- the actual situation of the service determining whether the service request can be processed, and feeding back the response message, so that the second mobile edge computing device determined by the first mobile edge computing device may be preferred, for example, the second mobile edge computing device
- the amount of business processing is small, which can reduce the waiting time of the service request and improve the efficiency of business processing.
- the information list of the mobile edge computing device is deployed on the management device, and the first mobile edge computing device first sends a query request to the management device, where the query request includes at least part of the service type of the service type. And/or at least part of the service content of the service content, and then receiving, by the management device, at least one piece of identification information corresponding to the at least one mobile edge computing device, where the information list of the mobile edge computing device includes the at least one piece of identification information, and finally The first mobile edge computing device determines the second mobile edge computing device from the at least one mobile edge computing device based on the at least one identification information.
- the first mobile edge computing device may determine the second mobile edge computing device by sending a query message according to the information list of the mobile edge computing device deployed by the management device.
- the first mobile edge computing device obtains service data corresponding to the first service request according to the service data corresponding to the second service request, where the first mobile edge computing device sends The service data corresponding to the first service request.
- the service data may be directly used as the service data corresponding to the first service request; After the processing, the service data corresponding to the first service request is obtained.
- the service data sent by the multiple second mobile edge computing devices may be aggregated and the like, thereby obtaining the final The service data, the first mobile edge computing device can flexibly determine the service data corresponding to the first service request according to actual conditions.
- the embodiment of the present application provides a service processing method, where the method is applied to a management device, where the management device first receives a first service request from a first mobile edge computing device, where the first service request includes a service type and/or Or service content, and then the management device sends the service data corresponding to the first service request to the first mobile edge computing device.
- the management device may receive the service request sent by the mobile edge computing device, and send the service data corresponding to the service request to the mobile edge computing device, so that when a certain mobile edge computing device receives a large number of services
- the service request can be forwarded to the management device for processing, so that the mobile edge computing device can process the service request in cooperation with the management device, and the resource utilization of the mobile edge computing device and the management device can be improved.
- the management device may send a second service request to the second mobile edge computing device, where the second service request includes at least part of the service type of the service type and/or at least part of the service content of the service content. Content, and then receiving service data corresponding to the second service request from the second mobile edge computing device.
- the management device may forward the second service request corresponding to the service request to the other mobile edge computing device, and process the second service request by using the other mobile edge computing device, thereby
- the plurality of mobile edge computing devices can be cooperatively processed for the service request, and resource utilization of the plurality of mobile edge computing devices can be improved.
- the management device determines the second mobile according to the information list of the mobile edge computing device deployed by the management device.
- An edge computing device the information list of the mobile edge computing device includes information of the second mobile edge computing device.
- the management device may first determine, according to the information list of the mobile edge computing device, the second mobile edge computing device capable of processing the second service request, and then the second The service request is forwarded to the determined mobile edge computing device, thereby saving signaling resources between the management device and the mobile edge computing device, which can improve service processing efficiency.
- the information list of the mobile edge computing device includes the identification information of the mobile edge computing device and the service type and/or service content deployed by the corresponding mobile edge computing device.
- the information list of the mobile edge device may also include part or all of the identification information of the mobile edge computing device and the service type and/or service content deployed by the corresponding mobile edge computing device, so that the management device may The information list accurately determines the second mobile edge computing device capable of processing the second service request, which can improve service processing efficiency.
- the management device first obtains service data corresponding to the first service request according to the service data corresponding to the second service request, and then sends the data to the first mobile edge computing device.
- the service data corresponding to the first service request is obtained.
- the service data may be directly used as the service data corresponding to the first service request; after the service processing is processed, Obtaining the service data corresponding to the first service request.
- the service data sent by the multiple second mobile edge computing devices may be aggregated and the like to obtain the final service data.
- the management device can flexibly determine the service data corresponding to the first service request according to actual conditions.
- the embodiment of the present application provides a mobile edge computing device, which has the function of implementing the behavior of the first mobile edge computing device in the method of the foregoing first aspect.
- the functions may be implemented by hardware or by corresponding software implemented by hardware.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the structure of the mobile edge computing device includes a processor and a transmitter configured to support the mobile edge computing device to perform the corresponding functions of the first aspect method described above.
- the transmitter is configured to support communication between the mobile edge computing device and other devices, and to transmit information or instructions involved in the method of the first aspect described above to other devices.
- the mobile edge computing device can also include a memory for coupling with a processor that holds the necessary program instructions and data.
- the embodiment of the present application provides a network device, where the network device has a function of implementing the behavior of the management device in the method in the foregoing second aspect.
- the functions may be implemented by hardware or by corresponding software implemented by hardware.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the structure of the network device includes a processor and a transmitter configured to support the network device to perform the corresponding function in the method of the second aspect described above.
- the transmitter is configured to support communication between the network device and other devices, and transmit information or instructions involved in the method of the first aspect described above to other devices.
- the network device can also include a memory for coupling with the processor that holds the necessary program instructions and data.
- the embodiment of the present application provides a capability open architecture, where the architecture includes the mobile edge computing device and/or the second aspect and the network device of the fourth aspect described in the first aspect and the third aspect.
- the embodiment of the present application provides a computer storage medium, configured to store computer software instructions for performing the foregoing first aspect, any one of the first aspect, and the foregoing second aspect, and includes A program designed to perform any of the above first aspect, the first aspect, and the method of the second aspect described above.
- the embodiment of the present application provides a computer program product, where the computer program product includes instructions, when the instruction is run on a computer, causing the computer to perform any of the first aspect and the first aspect.
- the computer program product includes instructions, when the instruction is run on a computer, causing the computer to perform any of the first aspect and the first aspect.
- the embodiment of the present application further provides a chip system, where the chip system includes a processor, configured to support a mobile edge computing device to implement the method described in the foregoing first aspect, or to support a network device to implement the foregoing second aspect.
- the method for example, generates or processes data and/or information involved in the above methods.
- the chip system also includes a memory for storing program instructions and data necessary for the mobile edge computing device or network device.
- the chip system can be composed of chips, and can also include chips and other discrete devices.
- the mobile edge computing device may forward part of the service or all services in the service request to other mobile edge computing devices or management devices for processing, so that when a mobile edge calculation is performed
- the device may forward the service request to the management device or the idle mobile edge computing device for processing, so that the multiple mobile edge computing devices and the management device can jointly process the service request, which can improve the mobile edge calculation. Resource utilization of the device.
- FIG. 1 is a schematic diagram of a capability open architecture in the prior art
- FIG. 2 is a flow chart of a method for processing a service in the prior art
- FIG. 3 is a schematic diagram of a capability open architecture provided by an embodiment of the present application.
- FIG. 4 is a schematic diagram of functional modules of a management device and an MEC in an open capability architecture provided in an embodiment of the present application;
- 5A-5B are flowcharts of a service processing method provided in an embodiment of the present application.
- 6A-6B are flowcharts showing a specific implementation process of the fourth sending mode in step 503 when the service processing method shown in FIG. 5A is used in the embodiment of the present application;
- FIG. 7 is a flowchart of determining a second MEC by using a neighbor node information table when the service processing method shown in FIG. 5A is used in the embodiment of the present application;
- FIG. 8 is a flowchart of determining a second MEC by using a node information table in the NEF when the service processing method shown in FIG. 5A is adopted in the embodiment of the present application;
- FIG. 9 is a flowchart of determining a second MEC by using a neighbor node information table when the service processing method shown in FIG. 5B is adopted in the embodiment of the present application;
- FIG. 10 is a flowchart of determining a second MEC by using a node information table in the NEF when the service processing method shown in FIG. 5B is used in the embodiment of the present application;
- FIG. 11 is a flowchart of a service processing method according to another embodiment of the present application.
- FIGS. 12A-12B are flowcharts showing a specific implementation manner of a third sending manner of step 1102 in another embodiment of the present application.
- FIG. 13 is a schematic structural diagram of a mobile edge computing device according to an embodiment of the present application.
- FIG. 14 is a schematic structural diagram of a network device according to an embodiment of the present application.
- 15 is another schematic structural diagram of a mobile edge computing device according to an embodiment of the present application.
- FIG. 16 is another schematic structural diagram of a network device according to an embodiment of the present application.
- the embodiment of the present application provides a service processing method, which may be applied to a communication system, such as a 4G network or a 5G network.
- a communication system such as a 4G network or a 5G network.
- a new wireless (NR) system wireless.
- Wifi Worldwide Interoperability for Microwave Access (WiMAX), Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, broadband Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE) -A) a system, a Universal Mobile Telecommunication System (UMTS), and a cellular system related to the 3rd Generation Partnership Project (3GPP), which may be in the above communication system Any two.
- GSM Global System of Mobile communication
- CDMA Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- GPRS General Packet Radio Service
- LTE Long Term Evolution
- LTE Advanced
- the method is also applicable to the communication technology of the future, and the system described in the embodiment of the present application is for the purpose of more clearly explaining the technical solution of the embodiment of the present application, and does not constitute a limitation of the technical solution provided by the embodiment of the present application.
- the technical solutions provided by the embodiments of the present application are applicable to similar technical problems as the network architecture evolves.
- An Evolved Node B which may also be referred to as a network device, may refer to a device in an access network that communicates with a wireless terminal device over one or more cells on an air interface.
- the base station can be used to convert the received air frame to the IP packet as a router between the terminal device and the rest of the access network, wherein the rest of the access network can include an IP network.
- the base station can also coordinate attribute management of the air interface.
- the base station may include an evolved base station (NodeB or eNB or e-NodeB, evolutional Node B) in a Long Term Evolution (LTE) system or an evolved LTE system (LTE-A), or
- NodeB or eNB or e-NodeB, evolutional Node B in a Long Term Evolution (LTE) system or an evolved LTE system (LTE-A), or
- LTE Long Term Evolution
- LTE-A evolved LTE system
- the next generation node B (gNB) in the 5G system may be included in the embodiment of the present application.
- a terminal device including a device that provides voice and/or data connectivity to a user, for example, may include a handheld device having a wireless connection function, or a processing device connected to a wireless modem.
- the terminal device can communicate with the core network via a Radio Access Network (RAN) to exchange voice and/or data with the RAN.
- the terminal device may include a user equipment (User Equipment, UE), a wireless terminal device, a mobile terminal device, a Subscriber Unit, a Subscriber Station, a mobile station, a mobile station, and a remote station. Station (Remote Station), Access Point (AP), Remote Terminal, Access Terminal, User Terminal, UserAgent, or User Equipment (User Device), etc.
- a mobile phone or "cellular” phone
- a computer with a mobile terminal device a portable, pocket, handheld, computer built-in or in-vehicle mobile device, smart wearable device, and the like.
- PCS Personal Communication Service
- SIP Session Initiation Protocol
- WLL Wireless Local Loop
- PDA Personal Digital Assistant
- Smart Watches smart helmets, smart glasses, smart bracelets, and other equipment.
- restricted devices such as devices with lower power consumption, or devices with limited storage capacity, or devices with limited computing capabilities. Examples include information sensing devices such as bar codes, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners.
- RFID radio frequency identification
- GPS global positioning systems
- MEC Mobile Edge Computing
- a device that is close to the base station can acquire data packets of the UE, process the data packets, and then route the processing results to provide the terminal equipment. Required service.
- the third-party application integration can also be provided.
- the MEC device can route the data packets of the terminal device to the corresponding third-party application server and process it locally, for example, obtaining the load information on the access network side and the wireless on the MEC.
- the link quality information is fed back to the content optimization processing unit for dynamic adjustment (mainly for video bit rate adjustment), thereby improving the user experience and reducing the delay and the number of jams.
- SGW Serving Gateway
- Packet Data Network GateWay is the entry of data sent by the external network to the terminal device, responsible for IP address allocation of the terminal device, data packet filtering, rate control, and generation of the terminal device. Fee information, etc.
- the terminal device can access the external PDN network by connecting to the PGW to create a Packet Data Network (PDN) connection, which may be the Internet, a virtual private network (VPN), or an IP multimedia service. (IP Multi-media Service, IMS) network, or Wireless Application Protocol (WAP) network provided by the operator.
- PDN Packet Data Network
- VPN virtual private network
- IMS IP Multi-media Service
- WAP Wireless Application Protocol
- system and “network” in the embodiments of the present application may be used interchangeably.
- Multiple means two or more.
- a plurality can also be understood as “at least two” in the embodiment of the present application.
- the character "/” unless otherwise specified, generally indicates that the contextual object is an "or" relationship.
- the capability open architecture in the communication system is mainly shown in FIG. 1.
- the service processing process of the communication system is as shown in FIG. 2.
- Step 201 The terminal device sends a service request to the base station.
- Step 202 After receiving the service request, the base station forwards the service request to the MEC corresponding to the area where the terminal device is located.
- Step 203 The MEC determines whether the service request can be processed. If the MEC can process the service request, the service request is added to the MEC request queue and waits for processing. After the processing is completed, steps 206-207 are performed. If the MEC cannot process the service request, step 204-207 is performed.
- Step 204 The MEC determines that the service request cannot be processed, and the MEC sends the service request to the cloud for processing via the SGW and the PGW.
- Step 205 The MEC receives the service data corresponding to the service request from the cloud.
- Step 206 The MEC feeds back the service data corresponding to the service request to the base station.
- Step 207 The base station sends the service data corresponding to the service request to the terminal device, and completes the processing of the service request.
- the embodiment of the present application proposes a service processing method based on the capability open architecture shown in FIG. 3 to improve resource utilization of the MEC.
- the embodiment of the present application provides a capability open architecture.
- the capability open architecture includes at least one management device and multiple MECs.
- Each MEC of the multiple MECs is configured to analyze, match, distribute, reconstruct, process, and cache service data corresponding to the service request, and the management device is mainly used to identify multiple MECs. And management, including managing the state of each MEC node and the type of business deployed.
- the management device may be a Network Exposure Function (NEF) device, or may be another device or a control node that can manage the multiple MECs, and is not limited herein.
- the management device is an NEF device as an example.
- the capability open architecture may further include multiple base stations, and multiple base stations and multiple MECs may be preset corresponding relationships.
- a plurality of base stations and a plurality of MECs have a one-to-one correspondence, that is, each MEC manages a service request sent by one base station; of course, each base station may include multiple serving cells, and therefore, multiple base stations and multiple MECs
- the preset correspondence may also be a correspondence between each serving cell of the plurality of base stations and the MEC.
- the base station includes three serving cells, which are the serving cell 1 - the serving cell 3, and the serving cell 1 and the serving cell 2 can be set to correspond to the MEC1 shown in FIG.
- the serving cell 3 corresponds to the MEC2 shown in FIG.
- the service request sent by each terminal device from the serving cell 1 and the serving cell 2 is processed by the MEC1
- the service request sent by each terminal device from the serving cell 3 is processed by the MEC2.
- other correspondences may be set between multiple base stations and multiple MECs, which are not limited herein.
- an application parsing module may be set in each MEC for analyzing a service request of the terminal device, determining a service type and feature of the service request, extracting key data of the service request, and the like, and simultaneously, in order to accelerate
- the service processing process may also be configured with multiple information tables in each MEC, for example, a service type table, a node information table, a data resource table, a function module table, and an original request queue, where the deployed application is stored in the service type table.
- the service information; the node information table stores the state information of the neighboring device of the MEC, the resource usage, the existing service type, and the like; the data resource table is used to store the data resource, including the sensing data from the terminal device, the obtained service data, The resource transmitted by the cloud; the original request queue is used to store unresolved service requests; and the function module table is used to store the functional modules currently deployed by the MEC.
- the service type table can be configured in the NEF to store the service type of the NEF deployment.
- the node information table is used to store the node information of each MEC of the multiple MECs it manages, including the resource usage of each MEC and the deployed service type. .
- the M_ID is the number of the MEC, and the value is any integer of 1, 2, 3, ... N, where N is the total number of MECs managed by the NEF;
- the identifier is another symbol, the corresponding description can be referred to Table 1, which is not mentioned here.
- the NEF can interact with each MEC.
- the MEC can send a query request to the NEF, so that the NEF queries the node status information of other MECs, the deployed service type, and the current load status according to the query request. And feedback the query results to the MEC.
- each MEC can also be configured to interact with each other.
- each MEC is configured with at least one neighbor device and at least one non-neighbor device.
- the neighbor device and the non-neighbor device may be manually configured, or may be configured by each MEC.
- the preset rule is automatically determined, for example, according to a rule whose distance value is smaller than the threshold, and is not limited herein.
- MEC2-MEC5 is the neighboring device of MEC1
- MEC6-MEC9 is the non-neighboring device of MEC2.
- MEC1 can directly interact with any MEC in MEC2-MEC5.
- MEC1 encapsulates the received service request into a new one. The service request is sent to the MEC2, and the MEC2 feeds back the service data to the MEC1 after processing the new service request.
- the MEC1 may first send a query request to the NEF, and then the NEF feeds back the MEC6 node information to the MEC1, and the MEC1 uses the node information fed back by the NEF. MEC6 interacts.
- the MEC1 may first send a query request to the NEF, and then the NEF feeds back the MEC6 node information to the MEC1, and the MEC1 uses the node information fed back by the NEF.
- MEC6 interacts.
- other information interactions can be performed between the MECs and the NEFs. For details, refer to Table 2, which is not mentioned here.
- the number of NEFs and MECs included in the capability open architecture shown in FIG. 3 is merely an example, and the embodiment of the present application is not limited thereto. For example, more NEFs may be included or more MECs may be included. For the sake of brevity, they are not described in the drawings.
- the capability open architecture shown in FIG. 3 although the terminal device, the base station, the NEF, the MEC1-MEC9, the SGW, the PGW, and the cloud are shown, the capability open architecture may not be limited to including the terminal device.
- Base station may also include a core network device or a device for carrying virtualized network functions, etc., as will be apparent to those skilled in the art. No longer one case.
- the content and the number of the function modules set in the MEC and the NEF shown in FIG. 4, the contents and the number of the plurality of information tables shown in Table 1, the contents and the number of the interactive information in Table 2 are merely examples. It is to be noted that those skilled in the art can also set other content or quantity of function modules, information tables, and interaction information, and are not limited thereto in the embodiment of the present application.
- the first mobile edge computing device receives the included service, because the service processing method in the prior art causes the resource utilization of the MEC to be low.
- the second service request may be sent to the second mobile edge computing device, where the second service request includes at least part of the service type of the service type and/or the service content. At least part of the service content, and the identification information of the first mobile edge computing device, and finally receiving the service data corresponding to the second service request from the second mobile edge computing device.
- the mobile edge computing device may forward part of the service or all services in the service request to other mobile edge computing devices for processing, so that when a mobile edge computing device receives a large number of When the service is requested, the service request may be forwarded to the idle mobile edge computing device for processing, so that the multiple mobile edge computing devices can cooperate to process the service request, which can improve the resource utilization of the mobile edge computing device.
- the technical solution provided by the embodiment of the present application is described in the following with reference to the accompanying drawings.
- the technical solution provided by the present application is applied to the capability open architecture shown in FIG. 3, and the management device is NEF, and the terminal device is used.
- the first MEC is the MEC for processing the service request corresponding to the UE in the multiple MECs shown in FIG. 3, for example, the MEC1
- the interaction information between the devices in the capability open architecture is Table 1 and Table 2.
- the information shown in the example is an example.
- FIG. 5A and FIG. 5B are a service processing method according to an embodiment of the present application.
- the process of the method is described as follows:
- Step 501 The UE sends a first service request to the base station.
- the first service request may be a purely computational request, such as a request for online translation, and may be a pure storage type request, such as a request for network storage, or a calculation and storage integrated request, for example,
- the request for navigation or the request for online game is not limited herein.
- the service request Req_Service is taken as an example for the first service request.
- Step 502 The base station receives the first service request, and sends the first service request to the MEC1.
- the correspondence between each serving cell and the MEC of the base station may be pre-stored.
- the base station is composed of three serving cells, namely, the serving cell 1, the serving cell 2, and the serving cell 3.
- the MEC corresponding to the serving cell 1 and the serving cell 2 is the MEC1 in FIG. 3, and the MEC corresponding to the serving cell 3 is shown in FIG. 3. MEC2 in.
- the base station After receiving the service request Req_Service sent by the UE, the base station first determines the serving cell where the UE is located. For example, if the serving cell where the UE is located is the serving cell 2, the MEC corresponding to the UE is determined to be MEC1, so that the service is performed. Request Req_Service to send to MEC1.
- the storage unit of the base station may also directly store the identifier information of the MEC corresponding to the MEC1. For example, if the identifier information of the MEC stored in the base station is the MEC1, the UEs in all the serving cells of the base station correspond to the MEC1, as long as the When receiving the service request of the UE, the base station directly sends the service request to the MEC1.
- the base station can also determine to send to the MEC1 by other means. For example, the base station can directly send the service request to the MEC closest to the base station, which is not limited herein.
- step 501 and step 502 are not necessary, that is, step 501 and step 502 may not be performed.
- step 501 and step 502 are not performed at this time.
- Step 503 The MEC1 sends a second service request to the second MEC.
- the second service request includes at least part of the service type of the service type of the first service request and/or at least part of the service content of the service content of the first service request, and the first mobile edge computing device Identification information.
- step 503 may specifically select any one of the following four transmission modes to send the second MEC.
- the first type of transmission the identifier information of the second MEC is pre-stored in the MEC1, for example, the number M_3 of the second MEC is stored, so that when the MEC1 receives the service request Req_Service, it directly sends the service request Req_Service to the MEC3. Corresponding second business request.
- the second sending mode MEC1 first determines the second MEC according to the information list of the mobile edge computing device, and then sends the second service request to the second MEC.
- the information list of the mobile edge computing device includes identification information of at least one mobile edge computing device, for example, a number of the second MEC; or the information list of the mobile edge computing device includes at least one mobile The identification information of the edge computing device and the service type and/or service content deployed by the corresponding mobile edge computing device.
- the MEC1 may include the number of each MEC of the MEC2-MEC5 and the service type and/or each of the MEC deployments. Business content in the MEC resource data table.
- the information list of the mobile edge computing device may be set in the MEC1, for example, may be the neighbor node information table M_NeigNodeTable of the MEC in Table 1; or may be set in the NEF, for example, may be the node information table of the NEF in Table 1. N_MECTable.
- the information list of the mobile edge computing device may also be another type of list, and the information list of the mobile edge computing device may include one or more of the foregoing lists, which are not limited herein.
- the information list of the mobile edge computing device is taken as an example of the MEC neighbor node information table M_NeigNodeTable and the NEF node information table N_MECTable.
- the MEC1 may determine the second MEC by querying its neighbor node information table M_NeigNodeTable; when the information list of the mobile edge computing device is the node information of the NEF
- the MEC1 sends a query request to the NEF, and after determining the second MEC by the NEF query node information table N_MECTable, the node information of the second MEC is fed back to the MEC1, so that the MEC1 determines the second MEC according to the node information fed back by the NEF. .
- the third sending mode is: after receiving the service request Req_Service, the MEC1 first determines that the second service request needs to be sent to the second MEC according to the service type and/or the service content deployed by the MEC1, and then is pre-stored according to the MEC1.
- the identification information of the second MEC for example, stores the number M_3 of the second MEC, and transmits a second service request corresponding to the service request Req_Service to the MEC3.
- the MEC1 may parse the service request, determine the service type Req_Type of the service request Req_Service and the request content Req_KeyContent, and then determine whether a second service request needs to be sent to the second MEC, for example, Determining whether the service type deployed by the MEC1 itself includes the service type Req_Type and/or the resource data table of the MEC1 itself has the same service data as the request content Req_KeyContent. If the determination result is no, it is determined that the second service request needs to be sent to the second MEC. The MEC1 sends a second service request corresponding to the service request Req_Service to the MEC3.
- the fourth sending mode after receiving the service request Req_Service, the MEC1 first determines that the second service request needs to be sent to the second MEC according to the service type and/or service content deployed by the MEC1, and then the MEC1 calculates the device according to the mobile edge. The information list determines the second MEC and finally sends a second service request to the second MEC.
- the method for determining that the MEC1 needs to send the second service request to the second MEC according to the service type and/or the service content deployed by the MEC1 is the same as the determining method in the third mode, and the MEC1 is based on the mobile edge computing device.
- the method for determining the second MEC of the information list is the same as the method for determining the second mode, and details are not described herein again.
- the number of the second MECs may be one or multiple, and is not limited in the embodiment of the present application.
- the implementation process of the first transmission mode is relatively simple, and will not be described in detail in the following description. Since the fourth transmission mode includes the main steps in the second transmission mode and the third transmission mode, only the implementation process of the fourth transmission mode is described in detail below, and the second transmission mode and the third method are described in detail. For the implementation process in the transmission mode, reference may be made to the description of the corresponding steps in the fourth transmission mode, and details are not described in the embodiment of the present application.
- FIG. 6A-6B is a flowchart of a specific implementation process of the fourth transmission mode, and the specific steps are as follows:
- Step 601 The MEC1 receives the service request Req_Service and parses it, and determines that the second service request needs to be sent to the second MEC.
- the MEC1 after receiving the service request Req_Service, the MEC1 first parses the service request Req_Service, determines the service type Req_Type of the service request Req_Service, extracts the request content Req_KeyContent, and stores the service request Req_Service into the original request queue M_ReqServiceTable. Then, according to one or more factors in the service type Req_Type, the request content Req_KeyContent, and the current load situation M_Workload of the service request Req_Service, it is determined that the second service request needs to be sent to the second MEC. For example, it may be determined that the service type deployed by the MEC1 itself includes the service type Req_Type.
- the MEC1 determines that the service volume processed by the MEC1 has been determined according to the current load situation M_Workload. When the maximum value is reached, it is determined that a second service request needs to be sent to the second MEC.
- M_Workload the current load situation
- different service requests may require different processing procedures.
- the processing required by the service request Req_Service may be determined, and then according to the service request.
- the required processing determines whether a second service request needs to be sent to the second MEC. Determining whether a second service request needs to be sent to the second MEC according to the processing required by the service request may be classified into the following three cases:
- the first case Business requests can be handled separately by a single MEC.
- the MEC1 may query the service type table M_AppTypeTable or the data resource table M_ResourceTable, and the current The load situation M_Workload, the comprehensive decision needs to send a second service request to the second MEC. For example, it is determined whether the service type matching the service type Req_Type is deployed in the service type table M_AppTypeTable, and if yes, it is determined that the second service request is not required to be sent to the second MEC, otherwise it is determined that the second MEC needs to be sent.
- the MEC1 determines whether the data in the data resource table M_ResourceTable is the same as the content of the request content Req_KeyContent, and if so, determines that the second service request does not need to be sent to the second MEC, otherwise it is determined that the second MEC needs to be sent.
- the second service request; or the MEC1 may determine whether the current load of the MEC1 has reached the preset upper limit. If the current load does not reach the preset upper limit, it is determined that the second MEC does not need to be sent.
- a service request otherwise determining to determine that a second service request needs to be sent to the second MEC. Of course, it is also possible to judge together with the above three factors.
- the second service request includes all service types of the service request Req_Service and/or all service contents of the service request Req_Service, and the number of the MEC1.
- the second case the business request requires multiple MECs to co-process. Each of the plurality of MECs that are co-processed provides the same type of service.
- the service request Req_Service is a road congestion situation query.
- the MEC1 parses the service request Req_Service, it is determined that a single MEC cannot be completed according to the service content of the service request Req_Service, and the queryed route includes multiple MECs. All MECs on the route work together to get the congestion of the entire road. At this time, the MEC1 determines that it is necessary to send a second service request to the second MEC.
- the MEC1 may further determine whether it is on the route that the service requests Req_Service queries, thereby determining the content included in the second service request. For example, if the MEC1 is on the queried route, the MEC1 determines that the second service request includes part of the service type of the service request Req_Service and/or part of the service content of the service request Req_Service, and the number of the MEC1; if the MEC1 is not in the queried route The MEC1 determines that the second service request includes all service types of the service request Req_Service and/or all service contents of the service request Req_Service, and the number of the MEC1.
- the second service request may be multiple sub-service requests, and each sub-service request is processed by the MEC, and each sub-service request includes the service type and/or service content of the sub-service request. , and the number of MEC1.
- the third case the request content of the service request needs to be split into multiple independent service requests for processing.
- the service request Req_Service is a business request of an attraction guide
- the attraction guide information itself may include a scenic route, an attraction shopping, and a parking space of the attraction. Therefore, after the MEC1 parses the service request Req_Service, the service type of the Req_Service is requested according to the service. And the business content, determining that the service request Req_Service can be split into: a query request of the attraction route, a query request for the attraction shopping, and a parking space query request of the attraction, so that the service request Req_Service is split into multiple sub-service requests, for different The sub-service request can request different MEC processing, thereby speeding up the processing speed of the service request processing by the capability open architecture and reducing the service delay.
- the MEC1 may separately determine the three sub-service requests to determine whether it is necessary to send the second service request to the second MEC. If the MEC1 can process the three sub-service requests, it is determined that the second service request does not need to be sent to the second MEC; if the MEC1 can only process one or both of the three sub-service requests, it is determined that the second MEC needs to be sent.
- the second service request at this time, the second service request includes a part of the service type of the service request Req_Service and/or part of the service content of the service request Req_Service, and the number of the MEC1. For details on how to determine each sub-service request, refer to the MEC1 in the first case to determine the method for determining the service request Req_Service in the first case, and details are not described herein.
- the second service request may be multiple sub-service requests, and each sub-service request is processed by the MEC, and each sub-service request includes the service type and/or service content of the sub-service request. , and the number of MEC1.
- step 601 After step 601 is performed, steps 602-603 are performed.
- Step 602 The MEC1 determines the second MEC from other MECs.
- step 602 is as follows.
- mode A includes:
- Step 701 The MEC1 queries the neighbor node information table M_NeigNodeTable to determine a neighbor device that can process the service request.
- the MEC1 queries the keyword in the neighbor node information table M_NeigNodeTable, and the keyword includes at least the service type Req_Type and/or the request content Req_KeyContent of the service request Req_Service, and searches for a node of the neighbor MEC that matches the keyword. information.
- the neighboring MEC in which the service type Req_Type and/or the requested content Req_KeyContent are stored may be configured in the query neighbor node information table M_NeigNodeTable.
- the keyword is the service type Req_Type.
- the MEC1 determines that the MEC2 and the MEC3 deploy the service type Req_Type, and determines that the MEC2 and the MEC3 are neighbor devices capable of processing the service request.
- Step 702 The MEC1 sends an inquiry message to a neighbor device capable of processing the service request.
- the inquiry message includes a service type of the service request and/or a request content of the service request.
- the query information carrying the service type Req_Type and/or the request content Req_KeyContent is transmitted to the MEC2 and the MEC3. It should be noted that, in the embodiment of the present application, the naming of the inquiry information is not limited.
- Step 703 The neighbor device capable of processing the service request feeds back a response message to the MEC1.
- the MEC2 and the MEC3 After the MEC2 and the MEC3 receive the inquiry message sent by the MEC1, the MEC2 and the MEC3 respectively query the service type and the current load situation of the respective deployment, and determine whether the service request Req_Service can be processed.
- the determining process may refer to step 601. Let me repeat. For example, if MEC2 determines that the service request Req_Service can be processed, it sends an acknowledgement message to MEC1; if MEC3 determines that the service request Req_Service cannot be processed, it sends a reject message to MEC1.
- the specific form and content of the confirmation message and the rejection message are not limited.
- Step 704 The MEC1 determines the second MEC based on the response message.
- the MEC1 determines that the neighbor MEC of the feedback acknowledgement message is the second MEC. For example, the MEC1 determines that the MEC2 is the second MEC.
- the MEC1 may select one of the MECs as the second MEC according to the preset selection rule, and the preset rule may be the closest selection, etc., and is not limited herein.
- the second MEC is determined by the node information table N_MECTable in the NEF.
- mode B includes:
- Step 801 The MEC1 sends the query information to the NEF.
- the query information includes at least a service type Req_Type and/or a request content Req_KeyContent of the service request Req_Service.
- Step 802 The NEF determines, according to the query information, a non-neighbor device capable of processing the service request.
- the non-neighbor device is a non-neighbor MEC of the MEC1.
- the NEF after receiving the query message, queries the keyword in the node information table N_MECTable, and the keyword includes at least the service type Req_Type and/or the request content Req_KeyContent of the service request Req_Service, and searches for the keyword.
- the node information of the matched non-neighbor MEC Specifically, the service type Req_Type and/or the non-neighbor MEC storing the request content Req_KeyContent may be deployed in the query node information table N_MECTable.
- the keyword is the service type Req_Type.
- the NEF determines that the MEC6 and the MEC7 deploy the service type Req_Type, and determines that the MEC6 and the MEC7 are non-neighbor devices capable of processing the service request.
- Step 803 The NEF sends the node information of the non-neighbor device capable of processing the service request to the MEC1.
- the NEF may send the number of the non-neighbor device capable of processing the service request to the MEC1. For example, M_6 and M_7 are sent to MEC1.
- Step 804 The MEC1 receives the node information, and sends an inquiry message to the MEC corresponding to the node information.
- the inquiry message includes a service type of the service request and/or a request content of the service request.
- the MEC1 After receiving the M_6 and M_7 transmitted by the NEF, the MEC1 transmits the inquiry information carrying the service type Req_Type and/or the request content Req_KeyContent to the MEC 6 and the MEC 7. It should be noted that, in the embodiment of the present application, the naming of the inquiry information is not limited.
- Step 805 The non-neighboring device capable of processing the service request feeds back a response message to the MEC1.
- the MEC6 and the MEC7 After the MEC6 and the MEC7 receive the inquiry message sent by the MEC1, the MEC6 and the MEC7 respectively query the service type deployed and the current load status, determine whether the service request Req_Service can be processed, and feed back the response information to the MEC1. This step is the same as step 703, and details are not described herein again.
- Step 806 The MEC1 determines the second MEC based on the response message.
- the MEC1 determines that the non-neighbor MEC of the feedback acknowledgement message is the second MEC. This step is the same as step 704, and details are not described herein again.
- the MEC1 may determine the second MEC by using any one of the foregoing two manners.
- the above two ways can be combined to determine the second MEC. That is, the second MEC is determined from the neighbor MEC by the mode A. If the neighbor MEC cannot process the service request, the mode 2 determines the second MEC from the non-neighbor MEC.
- step 602 the MEC1 determines the second MEC, and then step 603 is performed.
- Step 603 The MEC1 sends a second service request to the second MEC.
- the second service request is generated according to the service type Req_Type of the service request Req_Service and/or the request content Req_KeyContent, and the identification information of the MEC1, and then the second service request is sent to the second MEC.
- the source of multiple service requests can be distinguished, and the secondary analysis of the service request by other MECs can be avoided, and the MEC processing and response speed can be accelerated.
- MEC1 completes step 503.
- MEC1 performs steps 504-506 after performing step 503.
- Step 504 The second MEC processes the second service request, and sends the service data corresponding to the second service request to the MEC1.
- the second MEC After receiving the second service request, the second MEC processes the second service request, obtains the service result Req_Result, and sends the service result Req_Result to the MEC1.
- the service result Req_Result is the service data corresponding to the second service request.
- Step 505 The MEC1 receives the service data corresponding to the second service request, and feeds back the service data to the base station.
- Step 506 The base station feeds back the service data to the UE.
- steps 505-506 are not performed, and the MEC1 directly feeds the service data to the third-party application. That is, steps 505-506 are not required.
- the MEC1 determines that the second service request is not required to be sent to the second MEC, the MEC1 directly processes the service request Req_Service to obtain a service result Req_Result, where the service result Req_Result is the service corresponding to the service request Req_Service. The data is then fed back to the UE or the third-party application, and the details are not described here.
- Step 604 The MEC1 determines that only part of the service of the service request can be processed, and then re-packages the remaining part of the service that cannot be processed into multiple sub-service requests.
- the sub-service request Req_SubService uses the number M_ID of the MEC1 and the service type Req_Type of each sub-request as the service identifier.
- the route to be queried by the service request Req_Service can be divided into three road segments, wherein the MEC1 only covers the road segment 1. Therefore, the MEC1 encapsulates the road congestion situation query of the road segment 2 into the sub-service request 1, and the road segment of the road segment 3 is congested.
- the situation query is encapsulated as a sub-service request 2.
- the road congestion situation query of the road segment 2 and the road congestion situation query of the road segment 3 can also be encapsulated into a sub-service request, which is not limited herein.
- the road congestion status query of the road segment 2 is encapsulated into the sub-service request 1 by the MEC1
- the road congestion situation query of the road segment 3 is encapsulated into the sub-service request 2 as an example for description.
- Step 605 Determine, from other MECs, a second MEC for processing the multiple sub-service requests.
- step 605 can be as follows.
- mode A the second MEC is determined by the neighbor node information table M_NeigNodeTable.
- mode A includes:
- Step 901 The MEC1 queries the neighbor node information table M_NeigNodeTable to determine a set of neighbor devices that can process the multiple sub-service requests.
- step 901 The specific implementation steps of step 901 are the same as step 701, and details are not described herein again.
- MEC1 determines, in step 901, that the set of neighbor devices capable of processing the plurality of sub-service requests is MEC2-MEC5.
- Step 902 The MEC1 broadcasts a coordination request message to a set of neighbor devices capable of processing the multiple sub-service requests.
- the collaborative request message includes a service type of each sub-service request and/or a request content of each sub-service request.
- the naming of the collaborative request message is not limited.
- Step 903 Each neighbor device in the set of neighbor devices capable of processing the multiple sub-service requests feeds back a response message to the MEC1.
- the MEC2-MEC5 After receiving the cooperation request message, the MEC2-MEC5 separately queries the service type deployed and the current load status to determine whether the sub-service request 1 and/or the sub-service request 2 can be processed. For the determination process, reference may be made to the first case in step 503, and details are not described herein again. For example, the MEC2 determines that the sub-service request 1 can be processed, and sends an acknowledgement message corresponding to the sub-service request 1 to the MEC1; the MEC3 determines that the sub-service request 2 can be processed, and sends an acknowledgement message corresponding to the sub-service request 2 to the MEC1; If MEC5 cannot process any sub-service request, it sends a reject message to MEC1.
- the specific form and content of the confirmation message and the rejection message are not limited.
- MEC may also be able to process multiple sub-service requests. For example, if MEC3 can process sub-service request 1 and sub-service request 2, it may send two acknowledgment messages to MEC1, or carry the identifiers of two sub-service requests in one acknowledgment message. Information, no restrictions here.
- Step 904 The MEC1 determines the target MEC based on the response message.
- step 904 The specific implementation steps of the step 904 are the same as the step 704, and details are not described herein again.
- mode B the target MEC is determined by the node information table N_MECTable in the NEF.
- mode B includes:
- Step 1001 The MEC1 sends the query information to the NEF.
- the query information includes at least a service type and/or a request content of multiple sub-service requests.
- Step 1002 The NEF determines, according to the query information, a non-neighbor device capable of processing the multiple sub-service requests.
- Step 1003 The NEF sends a node information set of the non-neighbor device capable of processing the service request to the MEC1.
- steps 1002-1003 For the specific implementation steps of the steps 1002-1003, refer to steps 802-803, and details are not described herein again.
- the NEF determines, by the steps 1002-1003, that the non-neighbor device set capable of processing the multiple sub-service requests is the MEC6-MEC9.
- Step 1004 The MEC1 receives the node information set, and broadcasts a coordination request message to multiple MECs corresponding to the node information set.
- the collaborative request message includes a service type of each sub-service request and/or a request content of each sub-service request.
- the naming of the collaborative request message is not limited.
- Step 1005 The non-neighboring device in the non-neighbor device set feeds back a response message to the MEC1.
- the MEC6-MEC9 After receiving the cooperation request message, the MEC6-MEC9 separately queries the service type deployed and the current load status, determines whether the sub-service request 1 and/or the sub-service request 2 can be processed, and feeds back the response message to the MEC1.
- the form and content of the response message are the same as those of step 803, and details are not described herein again.
- Step 1006 The MEC1 determines the second MEC based on the response message.
- step 1006 The specific implementation steps of step 1006 are the same as step 704, and details are not described herein again.
- the MEC1 may determine the second MEC by using any one of the foregoing two manners.
- the above two ways can be combined to determine the second MEC. That is, the second MEC is determined from the neighbor MEC by the mode A. If the neighbor MEC cannot process the multiple sub-service requests, the mode 2 determines the second MEC from the non-neighbor MEC.
- step S605 the MEC1 determines the second MEC, and then step 606 is performed.
- Step 606 The MEC1 sends a sub-service request to the second MEC.
- the sub-service request Req_SubService that the second MEC can process is sent to the second MEC.
- MEC1 determines that the second MEC is MEC6 and MEC7, and MEC6 is used to process sub-service request 1, MEC7 is used to process sub-service request 2, MEC1 sends sub-service request 1 to MEC6, and sub-service request 2 is sent to MEC7. .
- MEC1 completes step 503. It should be noted that, in this implementation manner, the second service request is a plurality of sub-service requests. Referring to FIG. 5B, MEC1 performs steps 507-506 after performing step 503.
- Step 507 The second MEC processes the sub-service request, and sends the service data corresponding to the sub-service request to the MEC1.
- the second MEC After receiving the sub-service request Req_SubService, the second MEC processes the sub-service request Req_SubService, acquires the service result Req_SubResult corresponding to the sub-service request Req_SubService, and sends the sub-service result Req_SubResult to the MEC1.
- the sub-service result Req_SubResult is the service data corresponding to the sub-service request.
- the MEC 6 processes the sub-service request 1 to obtain the service result 1 and sends the service result 1 to the MEC 1;
- the MEC 7 processes the sub-service request 2 to obtain the service result 2, and sends the service result 2 to the MEC 1.
- Step 508 The MEC1 obtains service data corresponding to the first service request according to the received service data corresponding to the sub-service request.
- the MEC1 When the MEC1 receives the service result corresponding to the sub-service request sent by the target MEC, for example, receiving multiple service results sent by the multiple target MECs, the multiple service results may be aggregated to obtain the service data corresponding to the first service request. .
- Step 509 Feed the service data to the base station.
- Step 510 The base station feeds back the service data to the terminal device.
- steps 509-510 are not performed, and the MEC1 directly feeds the service data to the third-party application. That is, steps 509-510 are not required.
- the MEC1 determines that the second service request is not required to be sent to the second MEC, the MEC1 directly splits the service request Req_Service into multiple sub-service requests, and processes each sub-service request separately.
- the service result of the multiple sub-services is aggregated, and the service result Req_Result corresponding to the service request Req_Service is obtained, and the service result Req_Result is finally fed back to the UE or the third-party application, and details are not described herein again.
- the MEC1 can determine whether the storage capacity can cache the service result Req_Result, and if so, add the service result Req_Result to the data resource table M_ResourceTable; if not, query the neighbor node information table M_NeigNodeTable to find the neighbor that can store the service result Req_Result If the MEC is found to meet the requirements of the neighboring MEC, the service result Req_Result is sent to the MEC for storage. If the neighbor MEC cannot cache the service result Req_Result, the MEC1 may send the service result Req_Result to the NEF for storage.
- the MEC1 when the MEC1 cannot process the service request, the other MEC may be requested to process, or multiple MECs may process the same service request, thereby implementing the effect of coordinated cooperation between multiple MECs. Can improve the resource utilization of the MEC. Moreover, since multiple MECs can co-process the same service request, the processing time of the service request can be shortened, and the user's access experience can be improved.
- the management device Since the management device is also provided in the capability open architecture as shown in FIG. 3, the management device also has a service type table, that is, the management device itself can also process the service request.
- a service type table that is, the management device itself can also process the service request.
- FIG. 11 Another embodiment of the present application provides a For a business processing method, please refer to FIG. 11. The flow of the method is described as follows:
- Step 1101 The MEC1 sends a first service request to the NEF.
- the MEC1 can receive the first service request by referring to the implementation manner of the steps 501-503, and details are not described herein again.
- the first service request may be the original service request received by the MEC1, or may be the service request after the MEC1 processes the original service request.
- the specific process may be: after the MEC1 receives the original service request, The original service request is parsed, the service type of the original service request and the requested service content are obtained, and then re-encapsulated according to any one or more factors in the service type of the original service request, the requested service content, and the identification information of the MEC1,
- the encapsulated service request is used as the first service request, and is not limited herein.
- the MEC1 may send the first service request to the NEF in any of the following two manners.
- the specific process is as follows:
- the first way to send is
- the MEC1 directly sends the first service request to the NEF.
- the MEC1 may first determine whether the first service request can be processed by the neighbor MEC or whether the first service request can be performed by the non-neighbor MEC by using the method described in FIG. 7 and/or FIG. 8. If the neighboring MEC and the non-neighboring MEC are unable to process the first service request, the MEC1 sends the first service request to the NEF.
- Step 1102 The NEF receives the first service request, and acquires service data corresponding to the first service request.
- the step 1102 may specifically include the following three implementation manners, and in the specific implementation process, one of the implementations may be selected:
- the first implementation manner is: after receiving the first service request, the NEF directly processes the first service request, thereby acquiring service data corresponding to the first service request.
- the second implementation manner is: the identifier information of the second MEC may be pre-stored in the NEF, for example, the number M_3 of the second MEC is stored, so that when the NEF receives the first service request, the second service is directly sent to the MEC3.
- the request is then processed by the second MEC to process the second service request, and the service data corresponding to the second service request is fed back to the NEF, and the NEF obtains the service corresponding to the first service request according to the service data corresponding to the second service request.
- the second service request includes at least part of the service type of the service type of the first service request and/or at least part of the service content of the service content of the first service request, and may also include the identifier information of the MEC1.
- the third implementation manner is: first, the NEF first determines the second MEC according to the information list of the mobile edge computing device deployed by the NEF, and then sends the second service request to the second MEC, and then processes the second service request by the second MEC.
- the service data corresponding to the second service request is fed back to the NEF, and the NEF obtains the service data corresponding to the first service request according to the service data corresponding to the second service request.
- the second service request includes at least part of the service type of the service type of the first service request and/or at least part of the service content of the service content of the first service request, and may also include the identifier information of the MEC1.
- the information list of the mobile edge computing device includes the information of the second MEC, for example, the information list of the mobile edge computing device includes the number of the second MEC or the number of all the MECs, of course, the information list of the mobile edge computing device.
- the identification information of the mobile edge computing device and the service type and/or service content deployed by the corresponding mobile edge computing device are also not limited herein.
- the number of the second MECs may be one or multiple, and is not limited in the embodiment of the present application.
- the implementation process of the first transmission mode is relatively simple, and will not be described in detail in the following description. Since the third transmission mode includes the main steps of the second transmission mode, only the implementation process of the third transmission mode is described in detail below, and the implementation process of the second transmission mode may refer to the third transmission mode. The description of the corresponding steps in the manner may be omitted in the embodiment of the present application.
- the service request is mainly divided into three cases: the first case: the service request may be One MEC is processed separately; the second case: the service request requires multiple MECs to co-process, wherein each MEC of the multiple MECs that are co-processed provides the same service type; the third case: the request content of the service request needs It is split into multiple independent business requests for processing.
- the third transmission mode of the step 1102 can be implemented in the following two manners. In the specific implementation process, any one of the implementation manners can be selected, and the specific implementation manner is as follows:
- FIG. 12A is a flowchart of a first implementation manner of the third sending mode of step 1102. The specific steps are as follows:
- Step 1201 The NEF determines a second MEC for processing the second service request.
- the NEF After receiving the first service request, the NEF queries the keyword in the node information table N_MECTable, and the keyword includes at least the service type Req_Type and/or the request content Req_KeyContent of the new service request Req_Service, and searches for the keyword. Node information for the MEC. Specifically, the service type Req_Type and/or the MEC storing the requested content Req_KeyContent may be deployed in the query node information table N_MECTable.
- the keyword is the service type Req_Type
- the NEF determines that the MEC6 deploys the service type Req_Type, and determines that the MEC6 is the target MEC.
- Step 1202 The NEF sends a second service request to the second MEC.
- the second service request and the first service request may be identical, that is, the second service request is the first service request, and the second service request includes all service types of the service type of the first service request and / or the entire business content of the business content requested by the first business.
- the first service request is directly forwarded to the second MEC.
- the NEF may also encapsulate the entire service type of the service type of the first service request and/or the service content of the first service request and the identification information of the MEC1, and obtain the same substance, but the package. Different second service requests are then sent to the second MEC, which is not limited herein.
- Step 1203 The second MEC receives and processes the second service request, and sends the service data corresponding to the second service request to the NEF.
- the second service request may be directly processed; or the service type Req_Type, the request content Req_KeyContent, and the current One or more factors in the load situation M_Workload determine whether the second service request can be processed. If the second service request can be processed, the second service request is processed, and then the service data corresponding to the second service request is sent to the NEF.
- Step 1204 The NEF receives the service data corresponding to the second service request.
- the second MEC since the second service request includes all service types of the service type of the first service request and/or all service content of the service content of the first service request, the second MEC sends the The service data corresponding to the service request, that is, the service data corresponding to the first service request, so that the NEF obtains the service data corresponding to the first service request.
- the reject message may be sent to the NEF, and when the NEF receives the reject message sent by the second MEC, the second service is performed by the NEF.
- the request is processed to obtain the service data corresponding to the second service request.
- FIG. 12B is a flowchart of the second implementation manner of the third sending mode in step 1102 .
- the specific steps are as follows:
- Step 1205 The NEF splits the first service request into multiple sub-service requests, where the multiple sub-service requests are the second service request.
- the first service request can be determined to be split into multiple independent service requests by the service type and/or the service content of the first service request, and the NEF repackages the first service request into multiple The sub-service request, where each sub-service request Req_SubService includes the service type Req_Type of the sub-service request and/or the request content Req_KeyContent of the sub-service request.
- each sub-service request Req_SubService may also include the identification information of the MEC1.
- the second service request is characterized by the plurality of sub-service requests.
- Step 1206 The NEF determines a second MEC for processing the multiple sub-service requests.
- the NEF after splitting the first service request into multiple sub-service requests, queries the keyword in the node information table N_MECTable, and the keyword includes at least the service type Req_Type and/or of the multiple sub-service requests. Or request the content Req_KeyContent to find the node information of the MEC that matches the keyword.
- a MEC set that can be used to process the plurality of sub-service requests is thus determined from all MECs.
- the NEF broadcasts a coordination request message to each MEC corresponding to the MEC set that can be used to process the plurality of sub-service requests, and determines a second MEC according to the response message of each MEC.
- step 1206 For the specific implementation of the step 1206, refer to steps 1002-1006, and details are not described herein again.
- the second MEC may be multiple MECs, for example, one sub-service request requires one MEC processing.
- Step 1207 The NEF sends a corresponding sub-service request to the second MEC.
- Step 1208 The second MEC receives the corresponding sub-service request, processes the sub-service request, and sends the service data corresponding to the sub-service request to the NEF.
- Step 1209 The NEF obtains service data corresponding to the service request according to the service data sent by the second MEC.
- the NEF may aggregate the service data sent by each MEC to obtain service data corresponding to the service request.
- step 1103 is performed.
- Step 1103 The NEF sends the service data corresponding to the first service request to the MEC1.
- the service data may also be cached.
- the specific implementation is the same as the foregoing embodiment, and details are not described herein again.
- the MEC1 after receiving the service request, the MEC1 first pre-processes the service request, including extracting the service feature, the service type, the key data, and the like, re-encapsulating into a new service request, and then sending the request to the NEF.
- the NEF performs centralized scheduling on new service requests, performs service matching according to each MEC deployment service type, function module, and workload, and selects the appropriate optimal MEC node to improve the resource utilization of the MEC.
- the embodiment of the present application further provides a mobile edge computing device, which can implement corresponding steps performed by the MEC 1 in the embodiment shown in FIG. 5A to FIG. 12B.
- the mobile edge computing device includes a receiver, a processor, and a transmitter.
- the processor 1302 may be a central processing unit (CPU) or an application specific integrated circuit (ASIC), and may be one or more integrated circuits for controlling program execution, may be a baseband chip, and the like.
- CPU central processing unit
- ASIC application specific integrated circuit
- the receiver 1301 and the transmitter 1303 may be connected to the processor 1302 via a bus structure or a star structure or other structure, or may be separately connected to the processor 1302 through a dedicated connection line.
- the network device can also include a memory that can be coupled to the processor 1302 via a bus structure or a star structure or other structure.
- the number of memories may be one or more, and the memory may be a read only memory (ROM), a random access memory (RAM), or a disk memory, and the like.
- the memory can be used to store the program code required by the processor 1302 to perform tasks, and can also be used to store data.
- the receiver 1301 is configured to receive a first service request, where the first service request includes a service type and/or a service content;
- the transmitter 1303 is configured to send, to the second mobile edge computing device, the second service request generated by the processor 1302, where the second service request includes at least part of the service type of the service type and/or the service content. At least part of the service content, and the identification information of the first mobile edge computing device;
- the receiver 1301 is further configured to receive, by the second mobile edge computing device, service data corresponding to the second service request.
- the processor 1302 is configured to:
- the sender Before the sender sends the second service request to the second mobile edge computing device, determining, according to the service type and/or service content deployed by the mobile edge computing device, that the mobile edge computing device needs to The second mobile edge computing device sends the second service request.
- the processor 1302 is configured to:
- the transmitter 1303 Before the transmitter 1303 sends the second service request to the second mobile edge computing device, determining the second mobile edge computing device according to the information list of the mobile edge computing device; wherein, the information list of the mobile edge computing device The information of the second mobile edge computing device is included in the information.
- the information list of the mobile edge computing device includes the identifier information of the at least one mobile edge computing device;
- the information list of the mobile edge computing device includes the identification information of the at least one mobile edge computing device and the service type and/or service content deployed by the corresponding mobile edge computing device.
- the processor 1302 is configured to:
- the processor 1302 is configured to:
- the control transmitter 1303 sends a query request to the management device; the query request includes at least part of the service type of the service type and/or at least part of the service content of the service content;
- the control receiver 1301 receives, from the management device, at least one piece of identification information corresponding to the at least one mobile edge computing device, where the information list of the mobile edge computing device includes the at least one piece of identification information;
- the processor 1302 is configured to:
- the control transmitter 1303 transmits the service data corresponding to the first service request.
- the code corresponding to the foregoing service processing method is solidified into the chip, so that the chip can execute the foregoing service processing method during operation, and how to the receiver
- the 1301, the processor 1302, and the transmitter 1303 perform design programming and are well known to those skilled in the art, and are not described herein again.
- the embodiment of the present application further provides a network device, which can implement corresponding steps performed by the NEF in the embodiment shown in FIG. 5A to FIG. 12B.
- the network device includes a receiver 1401, a processor 1402, and a transmitter 1403.
- the hardware structure, the connection relationship, the number, and the like of the receiver 1401, the processor 1402, and the transmitter 1403 can be referred to the receiver, the processor, and the transmitter in the mobile edge computing device shown in FIG. 13, and details are not described herein.
- the receiver 1401 is configured to receive a first service request from the first mobile edge computing device, where the first service request includes a service type and/or service content;
- the transmitter 1403 is configured to send, according to the control of the processor 1402, the service data corresponding to the first service request to the first mobile edge computing device.
- the transmitter 1403 is configured to:
- Receiver 1401 is used to:
- the processor 1402 is configured to:
- the information list of the mobile edge computing device includes the identification information of the mobile edge computing device and the service type and/or service content deployed by the corresponding mobile edge computing device.
- the processor 1402 is configured to:
- the control transmitter 1403 transmits the service data corresponding to the first service request to the first mobile edge computing device.
- the code corresponding to the foregoing service processing method is solidified into the chip, so that the chip can execute the foregoing service processing method during operation, and how to the receiver
- the 1401, the processor 1402, and the transmitter 1403 are designed and programmed by those skilled in the art, and are not described herein again.
- the embodiment of the present application further provides a simplified functional block diagram of a mobile edge computing device, which can implement corresponding steps performed by the MEC 1 in the embodiment shown in FIGS. 5A-12B.
- the mobile edge computing device includes a receiving unit 1501, a processing unit 1502, and a transmitting unit 1503.
- the network element device corresponding to the receiving unit 1501 may be the receiver 1301 in FIG. 13
- the network element device corresponding to the sending unit 1503 may be the transmitter 1303 in FIG. 13
- the network element device corresponding to the processing unit 1502 may be Is the processor 1302 in FIG.
- the receiving unit 1501 is configured to receive a first service request, where the first service request includes a service type and/or a service content.
- the sending unit 1503 is configured to send, to the second mobile edge computing device, the second service request generated by the processing unit 1502, where the second service request includes at least part of the service type of the service type and/or the service content. At least part of the service content, and the identification information of the first mobile edge computing device;
- the receiving unit 1501 is further configured to receive, by the second mobile edge computing device, service data corresponding to the second service request.
- the processing unit 1502 is configured to:
- the sending unit 1503 Before the sending unit 1503 sends the second service request to the second mobile edge computing device, determining, according to the service type and/or service content deployed by the mobile edge computing device, that the mobile edge computing device needs to The second mobile edge computing device sends the second service request.
- the processing unit 1502 is configured to:
- the sending unit 1503 Before the sending unit 1503 sends the second service request to the second mobile edge computing device, determining, according to the information list of the mobile edge computing device, the second mobile edge computing device; wherein, the information list of the mobile edge computing device The information of the second mobile edge computing device is included in the information.
- the information list of the mobile edge computing device includes the identifier information of the at least one mobile edge computing device;
- the information list of the mobile edge computing device includes the identification information of the at least one mobile edge computing device and the service type and/or service content deployed by the corresponding mobile edge computing device.
- the processing unit 1502 is configured to:
- the control sending unit 1503 sends a first query message to the at least one mobile edge computing device; wherein the first query message includes at least part of the service type of the service type and/or at least part of the service content of the service content;
- the control receiving unit 1501 receives a response message from the at least one mobile edge computing device
- the processing unit 1502 is configured to:
- the control sending unit 1503 sends a query request to the management device; the query request includes at least part of the service type of the service type and/or at least part of the service content of the service content;
- the control receiving unit 1501 receives, from the management device, at least one piece of identification information corresponding to the at least one mobile edge computing device, where the information list of the mobile edge computing device includes the at least one piece of identification information;
- the processing unit 1502 is configured to:
- the control transmitting unit 1503 transmits the service data corresponding to the first service request.
- the embodiment of the present application further provides a simplified functional block diagram of a network device, which can implement corresponding steps performed by the NEF in the embodiment shown in FIG. 5A to FIG. 12B.
- the network device includes a receiving unit 1601, a processing unit 1602, and a sending unit 1603.
- the network element device corresponding to the receiving unit 1601 may be the receiver 1401 in FIG. 14
- the network element device corresponding to the sending unit 1603 may be the transmitter 1403 in FIG. 14
- the network element device corresponding to the processing unit 1602 may be Is the processor 1402 in FIG.
- the receiving unit 1601 is configured to receive, by the first mobile edge computing device, a first service request, where the first service request includes a service type and/or a service content.
- the sending unit 1603 is configured to send, according to the control of the processing unit 1602, the service data corresponding to the first service request to the first mobile edge computing device.
- the sending unit 1603 is configured to:
- the receiving unit 1601 is configured to:
- processing unit 1602 is configured to:
- the information list of the mobile edge computing device includes the identification information of the mobile edge computing device and the service type and/or service content deployed by the corresponding mobile edge computing device.
- processing unit 1602 is configured to:
- the control transmitting unit 1603 transmits the service data corresponding to the first service request to the first mobile edge computing device.
- the mobile edge computing device and the network device provided by the present application may be a chip system, and the chip system may include at least one chip, and may also include other discrete devices.
- the chip system can be placed in a mobile edge computing device or a network device, and the method for supporting the mobile edge computing device or the network device to complete the service processing provided in the embodiment of the present application is supported.
- the embodiment of the present application provides a computer storage medium, where the computer storage medium stores an instruction, and when the instruction is run on a computer, causes the computer to perform the foregoing service processing method.
- Embodiments of the present application provide a computer program product, the computer program product comprising instructions, when the instructions are run on a computer, causing the computer to perform the foregoing method of service processing.
- the mobile edge computing device may forward part of the service or all services in the service request to other mobile edge computing devices for processing, so that when a mobile edge computing device receives a large number of When the service is requested, the service request may be forwarded to the idle mobile edge computing device for processing, so that the multiple mobile edge computing devices can cooperate to process the service request, which can improve the resource utilization of the mobile edge computing device.
- the computer program product includes one or more computer instructions.
- the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
- the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another readable storage medium, for example, the computer instructions can be passed from a website site, computer, server or data center Wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
- the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
- the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)) or the like.
- a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
- an optical medium eg, a DVD
- a semiconductor medium eg, a solid state disk (SSD)
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (26)
- 一种业务处理方法,其特征在于,包括:第一移动边缘计算设备接收第一业务请求;其中,所述第一业务请求包含业务类型和/或业务内容;所述第一移动边缘计算设备向第二移动边缘计算设备发送第二业务请求;其中,所述第二业务请求包含所述业务类型的至少部分业务类型和/或所述业务内容的至少部分业务内容,以及所述第一移动边缘计算设备的标识信息;所述第一移动边缘计算设备从所述第二移动边缘计算设备接收与所述第二业务请求对应的业务数据。
- 根据权利要求1所述的方法,其特征在于,在所述第一移动边缘计算设备向第二移动边缘计算设备发送第二业务请求之前,所述方法还包括:所述第一移动边缘计算设备根据所述第一移动边缘计算设备部署的业务类型和/或业务内容,确定所述第一移动边缘计算设备需要向所述第二移动边缘计算设备发送所述第二业务请求。
- 根据权利要求1或2所述的方法,其特征在于,所述第一移动边缘计算设备向第二移动边缘计算设备发送第二业务请求之前,所述方法还包括;所述第一移动边缘计算设备根据移动边缘计算设备的信息列表,确定所述第二移动边缘计算设备;其中,所述移动边缘计算设备的信息列表中包含所述第二移动边缘计算设备的信息。
- 根据权利要求3所述的方法,其特征在于,移动边缘计算设备的信息列表包括至少一个移动边缘计算设备的标识信息;或者,所述移动边缘计算设备的信息列表包括所述至少一个移动边缘计算设备的标识信息以及对应的移动边缘计算设备部署的业务类型和/或业务内容。
- 根据权利要求4所述的方法,其特征在于,所述移动边缘计算设备的信息列表部署在所述第一移动边缘计算设备,所述第一移动边缘计算根据移动边缘计算设备的信息列表,确定所述第二移动边缘计算设备,包括:所述第一移动边缘计算设备查询所述移动边缘计算设备的信息列表,确定能够用于处理所述第二业务请求的至少一个移动边缘计算设备;所述第一移动边缘计算设备向所述至少一个移动边缘计算设备发送第一询问消息;其中,所述第一询问消息包含所述业务类型的至少部分业务类型和/或所述业务内容的至少部分业务内容;所述第一移动边缘计算设备从所述至少一个移动边缘计算设备接收应答消息;所述第一移动边缘计算设备根据所述应答消息,从所述至少一个移动边缘计算设备中确定所述第二移动边缘计算设备。
- 根据权利要求4所述的方法,其特征在于,所述移动边缘计算设备的信息列表部署在管理设备,所述第一移动边缘计算根据移动边缘计算设备的信息列表,确定所述第二移动边缘计算设备,包括:所述第一移动边缘计算设备向所述管理设备发送查询请求;所述查询请求包含所述业务类型的至少部分业务类型和/或所述业务内容的至少部分业务内容;所述第一移动边缘计算设备从所述管理设备接收与至少一个移动边缘计算设备对应的至少一个标识信息;其中,所述移动边缘计算设备的信息列表中包含所述至少一个标识信息;所述第一移动边缘计算设备根据所述至少一个标识信息,从所述至少一个移动边缘计算设备确定所述第二移动边缘计算设备。
- 根据权利要求1-6中的任一项所述的方法,其特征在于,所述方法还包括:所述第一移动边缘计算设备根据与所述第二业务请求对应的业务数据,获得与所述第一业务请求对应的业务数据;所述第一移动边缘计算设备发送与所述第一业务请求对应的业务数据。
- 一种业务处理方法,其特征在于,包括:管理设备从第一移动边缘计算设备接收第一业务请求;其中,所述第一业务请求包含业务类型和/或业务内容;所述管理设备向所述第一移动边缘计算设备发送与所述第一业务请求对应的业务数据。
- 根据权利要求8所述的方法,其特征在于,所述方法还包括:所述管理设备向第二移动边缘计算设备发送第二业务请求;其中,所述第二业务请求包含所述业务类型的至少部分业务类型和/或所述业务内容的至少部分业务内容;所述管理设备从所述第二移动边缘计算设备接收与所述第二业务请求对应的业务数据。
- 根据权利要求9所述的方法,其特征在于,在所述管理设备向第二移动边缘计算设备发送所述第二业务请求之前,所述方法还包括:所述管理设备根据所述管理设备部署的移动边缘计算设备的信息列表,确定所述第二移动边缘计算设备;其中,所述移动边缘计算设备的信息列表中包含所述第二移动边缘计算设备的信息。
- 根据权利要求10所述的方法,其特征在于,移动边缘计算设备的信息列表包括移动边缘计算设备的标识信息以及对应的移动边缘计算设备部署的业务类型和/或业务内容。
- 根据权利要求9-11中任一项所述的方法,其特征在于,所述方法还包括:所述管理设备根据所述与所述第二业务请求对应的业务数据,获得与所述第一业务请求对应的业务数据;所述管理设备向所述第一移动边缘计算设备发送与所述第一业务请求对应的业务数据。
- 一种移动边缘计算设备,其特征在于,包括接收器、处理器以及发送器,其中:所述接收器用于接收第一业务请求;其中,所述第一业务请求包含业务类型和/或业务内容;所述发送器用于向第二移动边缘计算设备发送由所述处理器生成的第二业务请求;其中,所述第二业务请求包含所述业务类型的至少部分业务类型和/或所述业务内容的至少部分业务内容,以及所述第一移动边缘计算设备的标识信息;所述接收器还用于从所述第二移动边缘计算设备接收与所述第二业务请求对应的业务数据。
- 根据权利要求13所述的设备,其特征在于,所述处理器用于:在所述发送器向所述第二移动边缘计算设备发送所述第二业务请求之前,根据所述移动边缘计算设备部署的业务类型和/或业务内容,确定所述移动边缘计算设备需要向所述第二移动边缘计算设备发送所述第二业务请求。
- 根据权利要求13或14所述的设备,其特征在于,所述处理器用于:在所述发送器向第二移动边缘计算设备发送所述第二业务请求之前,根据移动边缘计算设备的信息列表,确定所述第二移动边缘计算设备;其中,所述移动边缘计算设备的信息列表中包含所述第二移动边缘计算设备的信息。
- 根据权利要求15所述的设备,其特征在于,移动边缘计算设备的信息列表包括至少一个移动边缘计算设备的标识信息;或者,所述移动边缘计算设备的信息列表包括所述至少一个移动边缘计算设备的标识信息以及对应的移动边缘计算设备部署的业务类型和/或业务内容。
- 根据权利要求16所述的设备,其特征在于,所述处理器用于:查询所述移动边缘计算设备的信息列表,确定能够用于处理所述第二业务请求的至少一个移动边缘计算设备;控制所述发送器向所述至少一个移动边缘计算设备发送第一询问消息;其中,所述第一询问消息包含所述业务类型的至少部分业务类型和/或所述业务内容的至少部分业务内容;控制所述接收器从所述至少一个移动边缘计算设备接收应答消息;根据所述应答消息,从所述至少一个移动边缘计算设备中确定所述第二移动边缘计算设备。
- 根据权利要求16所述的设备,其特征在于,所述处理器用于:控制所述发送器向所述管理设备发送查询请求;所述查询请求包含所述业务类型的至少部分业务类型和/或所述业务内容的至少部分业务内容;控制所述接收器从所述管理设备接收与至少一个移动边缘计算设备对应的至少一个标识信息;其中,所述移动边缘计算设备的信息列表中包含所述至少一个标识信息;根据所述至少一个标识信息,从所述至少一个移动边缘计算设备确定所述第二移动边缘计算设备。
- 根据权利要求13-18中的任一项所述的设备,其特征在于,所述处理器用于:根据与所述第二业务请求对应的业务数据,获得与所述第一业务请求对应的业务数据;控制所述发送器发送与所述第一业务请求对应的业务数据。
- 一种网络设备,其特征在于,包括接收器、处理器以及发送器,其中:所述接收器用于从第一移动边缘计算设备接收第一业务请求;其中,所述第一业务请求包含业务类型和/或业务内容;所述发送器用于根据所述处理器的控制,向所述第一移动边缘计算设备发送与所述第一业务请求对应的业务数据。
- 根据权利要求20所述的设备,其特征在于,所述发送器用于:根据所述处理器的控制,向第二移动边缘计算设备发送第二业务请求;其中,所述第二业务请求包含所述业务类型的至少部分业务类型和/或所述业务内容的至少部分业务内容;所述接收器用于:从所述第二移动边缘计算设备接收与所述第二业务请求对应的业务数据。
- 根据权利要求21所述的设备,其特征在于,所述处理器用于:在所述发送器向第二移动边缘计算设备发送所述第二业务请求之前,根据所述网络设备部署的移动边缘计算设备的信息列表,确定所述第二移动边缘计算设备;其中,所述移动边缘计算设备的信息列表中包含所述第二移动边缘计算设备的信息。
- 根据权利要求22所述的设备,其特征在于,移动边缘计算设备的信息列表包括移动边缘计算设备的标识信息以及对应的移动边缘计算设备部署的业务类型和/或业务内容。
- 根据权利要求20-23中任一项所述的设备,其特征在于,所述处理器用于:根据所述与所述第二业务请求对应的业务数据,获得与所述第一业务请求对应的业务数据控制所述发送器向所述第一移动边缘计算设备发送与所述第一业务请求对应的业务数据。
- 一种计算机可读存储介质,其特征在于,所述介质上存储有指令,当其在计算机上运行时,使得计算机实现如权利要求1-7或8-12任一项所述的方法。
- 一种计算机程序产品,其特征在于,所述计算机程序产品包含有指令,当所述指令在计算机上运行时,使得所述计算机执行如权利要求1-7或8-12任一项所述的方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP18856799.4A EP3668174B1 (en) | 2017-09-12 | 2018-09-04 | Service processing method, mobile edge computing device, and network device |
AU2018332696A AU2018332696B2 (en) | 2017-09-12 | 2018-09-04 | Service processing method, mobile edge computing device, and network device |
US16/817,342 US11252259B2 (en) | 2017-09-12 | 2020-03-12 | Service processing method, mobile edge computing device, and network device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710817825.6A CN109495929B (zh) | 2017-09-12 | 2017-09-12 | 一种业务处理方法、移动边缘计算设备及网络设备 |
CN201710817825.6 | 2017-09-12 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/817,342 Continuation US11252259B2 (en) | 2017-09-12 | 2020-03-12 | Service processing method, mobile edge computing device, and network device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019052376A1 true WO2019052376A1 (zh) | 2019-03-21 |
Family
ID=65687708
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/104032 WO2019052376A1 (zh) | 2017-09-12 | 2018-09-04 | 一种业务处理方法、移动边缘计算设备及网络设备 |
Country Status (5)
Country | Link |
---|---|
US (1) | US11252259B2 (zh) |
EP (1) | EP3668174B1 (zh) |
CN (1) | CN109495929B (zh) |
AU (1) | AU2018332696B2 (zh) |
WO (1) | WO2019052376A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112153147A (zh) * | 2020-09-25 | 2020-12-29 | 南京大学 | 一种移动边缘环境中基于实体共享的链式服务实体的放置方法 |
Families Citing this family (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11196837B2 (en) * | 2019-03-29 | 2021-12-07 | Intel Corporation | Technologies for multi-tier prefetching in a context-aware edge gateway |
WO2020200268A1 (en) * | 2019-04-02 | 2020-10-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for service discovery |
CN110290506B (zh) * | 2019-04-17 | 2020-08-14 | 中国联合网络通信集团有限公司 | 一种边缘云移动性管理方法及设备 |
US11310148B2 (en) * | 2019-06-03 | 2022-04-19 | At&T Intellectual Property I, L.P. | Methods, systems, and computer programs for intelligent content delivery using a software defined network and edge computing |
CN112448827B (zh) * | 2019-08-27 | 2022-07-19 | 中国移动通信有限公司研究院 | 一种信息处理方法、装置、设备及计算机可读存储介质 |
WO2021087778A1 (zh) * | 2019-11-05 | 2021-05-14 | 北京小米移动软件有限公司 | 数据处理系统、方法、装置、设备及可读存储介质 |
CN110850957B (zh) * | 2019-11-12 | 2021-04-30 | 北京工业大学 | 一种边缘计算场景下通过休眠降低系统功耗的调度方法 |
TWI734270B (zh) * | 2019-11-25 | 2021-07-21 | 財團法人工業技術研究院 | 接取私有網路服務之方法及系統 |
CN113055820B (zh) * | 2019-12-28 | 2022-09-06 | 中移(上海)信息通信科技有限公司 | 数据存储方法、装置、系统和存储介质 |
CN113271215B (zh) * | 2020-02-14 | 2022-06-03 | 中移(苏州)软件技术有限公司 | 网络分层控制方法、装置和存储介质 |
CN116390103A (zh) * | 2020-02-27 | 2023-07-04 | 华为技术有限公司 | 一种通信方法、装置及系统 |
CN111405014B (zh) * | 2020-03-09 | 2022-04-22 | 联想(北京)有限公司 | 一种基于移动边缘计算mec平台的数据处理方法、装置及存储介质 |
CN113472822A (zh) * | 2020-03-30 | 2021-10-01 | 中移(上海)信息通信科技有限公司 | 数据分流方法、装置、设备及介质 |
CN111669751B (zh) * | 2020-05-07 | 2022-07-29 | 中国联合网络通信集团有限公司 | 一种数据流的建立方法、装置及通信系统 |
CN113660726A (zh) * | 2020-05-12 | 2021-11-16 | 华为技术有限公司 | 资源分配方法和装置 |
CN113778463B (zh) * | 2020-06-09 | 2023-01-06 | 华为技术有限公司 | 一种业务服务部署方法及装置 |
CN112019604B (zh) * | 2020-08-13 | 2023-09-01 | 上海哔哩哔哩科技有限公司 | 边缘数据传输方法和系统 |
US11700309B2 (en) | 2020-08-13 | 2023-07-11 | Alibaba Group Holding Limited | Network parameter provisioning for instantiation of a network entity |
CN114080061A (zh) * | 2020-08-17 | 2022-02-22 | 华为技术有限公司 | 一种基于数据边缘协议的通信方法 |
SE545771C2 (en) * | 2020-08-28 | 2024-01-09 | Stream Analyze Sweden Ab | Method and system for data processing |
SE545286C2 (en) | 2020-08-28 | 2023-06-20 | Stream Analyze Sweden Ab | Method and system for data processing |
CN112188548B (zh) * | 2020-09-09 | 2022-05-06 | 中国联合网络通信集团有限公司 | 一种业务处理方法及装置 |
CN112202847B (zh) * | 2020-09-14 | 2022-03-22 | 重庆邮电大学 | 一种基于移动边缘计算的服务器资源配置方法 |
CN112130931B (zh) * | 2020-09-27 | 2023-01-06 | 联想(北京)有限公司 | 一种应用部署方法、节点、系统及存储介质 |
CN116097904A (zh) * | 2020-09-30 | 2023-05-09 | 华为技术有限公司 | 一种网络边缘计算方法及通信装置 |
TWI746278B (zh) * | 2020-11-23 | 2021-11-11 | 中華電信股份有限公司 | 用於個人化影視服務之系統、方法及電腦可讀媒介 |
CN112584439A (zh) * | 2020-11-27 | 2021-03-30 | 重庆邮电大学 | 一种边缘计算中的缓存方法 |
CN112565404A (zh) * | 2020-12-02 | 2021-03-26 | 中国联合网络通信集团有限公司 | 数据处理方法、边缘服务器、中心服务器和介质 |
CN114697342A (zh) * | 2020-12-30 | 2022-07-01 | 华为云计算技术有限公司 | 任务处理方法、装置及系统、计算机存储介质 |
CN114938348A (zh) * | 2021-02-04 | 2022-08-23 | 北京金山云网络技术有限公司 | 一种数据流转发方法、装置、电子设备及存储介质 |
CN113194425B (zh) * | 2021-04-27 | 2022-08-19 | 蘑菇物联技术(深圳)有限公司 | LoRa通信方法、系统和计算机可读存储介质 |
CN113259359B (zh) * | 2021-05-21 | 2022-08-02 | 重庆紫光华山智安科技有限公司 | 一种边缘节点能力补充方法、系统、介质及电子终端 |
CN113452763B (zh) * | 2021-06-11 | 2024-01-30 | 青岛海尔科技有限公司 | 智慧家庭业务注册的方法、装置和智慧家庭系统 |
CN116010041A (zh) * | 2021-10-21 | 2023-04-25 | 伊姆西Ip控股有限责任公司 | 用于调度导览资源的方法、设备和计算机程序产品 |
CN113691879B (zh) * | 2021-10-25 | 2022-03-15 | 通号通信信息集团有限公司 | 视频数据处理方法、电子设备、计算机可读存储介质 |
CN113992715B (zh) * | 2021-10-26 | 2023-09-26 | 广东卓维网络有限公司 | 一种在线状态云监测及边缘计算装置及方法 |
CN113992690B (zh) * | 2021-10-26 | 2023-10-27 | 北京百度网讯科技有限公司 | 消息传递方法、装置、设备和存储介质 |
CN116074790B (zh) * | 2021-11-02 | 2024-04-19 | 中国联合网络通信集团有限公司 | Mec业务调度方法、第一mec服务器及存储介质 |
CN113934545A (zh) * | 2021-12-17 | 2022-01-14 | 飞诺门阵(北京)科技有限公司 | 一种视频数据调度方法、系统、电子设备及可读介质 |
CN116709416A (zh) * | 2022-02-26 | 2023-09-05 | 华为技术有限公司 | 一种通信方法及装置 |
CN117729585A (zh) * | 2023-12-14 | 2024-03-19 | 阳光凯讯(北京)科技股份有限公司 | 一种基于5g通信的天基信息分发方法及系统 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106231607A (zh) * | 2016-09-21 | 2016-12-14 | 北京佰才邦技术有限公司 | 一种资源分配的方法及基站 |
US20160366244A1 (en) * | 2015-06-12 | 2016-12-15 | Industrial Technology Research Institute | Controlling method, network system and service platform for mobile-edge computing |
CN106358245A (zh) * | 2016-11-07 | 2017-01-25 | 北京佰才邦技术有限公司 | 移动边缘计算应用负荷分担的方法和控制器 |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103188721B (zh) | 2011-12-28 | 2017-08-04 | 华为技术有限公司 | 一种数据传输方法及装置 |
CN103619042B (zh) * | 2013-10-21 | 2016-09-07 | 大唐移动通信设备有限公司 | 一种小区容量负荷均衡方法及装置 |
CN103648130A (zh) * | 2013-12-27 | 2014-03-19 | 大唐移动通信设备有限公司 | 一种负荷均衡方法及基站 |
CN104581831B (zh) * | 2014-12-30 | 2018-11-06 | 大唐移动通信设备有限公司 | 一种基站间的负荷均衡方法和系统 |
US9900725B2 (en) * | 2015-07-29 | 2018-02-20 | Intel Corporation | Technologies for an automated application exchange in wireless networks |
WO2017042813A1 (en) * | 2015-09-10 | 2017-03-16 | Vimmi Communications Ltd. | Content delivery network |
US10021172B2 (en) * | 2015-09-23 | 2018-07-10 | Nec Corporation | Software driven long-term-evolution core network for mobile access |
US9998563B2 (en) * | 2015-10-12 | 2018-06-12 | Fujitsu Limited | Vertex-centric service function chaining in multi-domain networks |
US20170118311A1 (en) * | 2015-10-22 | 2017-04-27 | Saguna Networks Ltd. | Methods Circuits Devices Systems and Functionally Associated Computer Executable Code for Facilitating Edge Computing on a Mobile Data Communication Network |
CN108028783B (zh) | 2015-11-30 | 2020-07-24 | 华为技术有限公司 | 切换移动边缘平台的方法、装置和系统 |
WO2017091934A1 (zh) * | 2015-11-30 | 2017-06-08 | 华为技术有限公司 | 一种能力开放的实现方法、系统及相关设备 |
GB2547426A (en) * | 2016-02-16 | 2017-08-23 | Vodafone Ip Licensing Ltd | Telecommunications network communication sessions |
CN106412905A (zh) * | 2016-12-12 | 2017-02-15 | 中国联合网络通信集团有限公司 | 网络切片选择方法、ue、mme和系统 |
CN106900011B (zh) * | 2017-02-28 | 2020-04-07 | 重庆邮电大学 | 一种基于mec的蜂窝基站间任务卸载方法 |
US9942825B1 (en) * | 2017-03-27 | 2018-04-10 | Verizon Patent And Licensing Inc. | System and method for lawful interception (LI) of Network traffic in a mobile edge computing environment |
US10439820B2 (en) * | 2017-06-19 | 2019-10-08 | Dell Products, Lp | Method and apparatus for secure access to a mobile edge computing gateway device based on a subscriber location fingerprint |
US10326766B2 (en) * | 2017-07-13 | 2019-06-18 | Dell Products, Lp | Method and apparatus for optimizing mobile edge computing for nomadic computing capabilities as a service |
-
2017
- 2017-09-12 CN CN201710817825.6A patent/CN109495929B/zh active Active
-
2018
- 2018-09-04 EP EP18856799.4A patent/EP3668174B1/en active Active
- 2018-09-04 WO PCT/CN2018/104032 patent/WO2019052376A1/zh unknown
- 2018-09-04 AU AU2018332696A patent/AU2018332696B2/en active Active
-
2020
- 2020-03-12 US US16/817,342 patent/US11252259B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160366244A1 (en) * | 2015-06-12 | 2016-12-15 | Industrial Technology Research Institute | Controlling method, network system and service platform for mobile-edge computing |
CN106231607A (zh) * | 2016-09-21 | 2016-12-14 | 北京佰才邦技术有限公司 | 一种资源分配的方法及基站 |
CN106358245A (zh) * | 2016-11-07 | 2017-01-25 | 北京佰才邦技术有限公司 | 移动边缘计算应用负荷分担的方法和控制器 |
Non-Patent Citations (1)
Title |
---|
HUAWEI: "Annexure ETSI MEC analysis", 3GPP TSG-SA WG6 MEETING #17, S6-170700, 12 May 2017 (2017-05-12), XP051290224 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112153147A (zh) * | 2020-09-25 | 2020-12-29 | 南京大学 | 一种移动边缘环境中基于实体共享的链式服务实体的放置方法 |
Also Published As
Publication number | Publication date |
---|---|
CN109495929A (zh) | 2019-03-19 |
EP3668174B1 (en) | 2023-08-23 |
AU2018332696A1 (en) | 2020-04-16 |
EP3668174A1 (en) | 2020-06-17 |
CN109495929B (zh) | 2021-08-03 |
EP3668174A4 (en) | 2020-08-19 |
US11252259B2 (en) | 2022-02-15 |
AU2018332696B2 (en) | 2021-08-12 |
US20200213419A1 (en) | 2020-07-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019052376A1 (zh) | 一种业务处理方法、移动边缘计算设备及网络设备 | |
US11778493B2 (en) | Data collection method, device, and system | |
US11832173B2 (en) | Data transmission method, terminal, and access-network network element | |
WO2019029643A1 (zh) | 通信方法、基站、终端设备和系统 | |
WO2020108002A1 (zh) | 一种传输策略确定方法、策略控制方法及装置 | |
US10999768B2 (en) | Session context handling method, network element, and terminal device | |
WO2021243837A1 (zh) | 基于ursp规则的应用数据路由方法及用户设备 | |
WO2018148893A1 (zh) | 数据传输方法和设备 | |
WO2017028289A1 (zh) | 一种网络终端设备进行通信的方法及装置 | |
US11102116B2 (en) | Method and device for hosting application by access node | |
CN113285827B (zh) | 数据传输方法、系统及相关装置 | |
WO2019085728A1 (zh) | 通信方法及装置 | |
JP7192140B2 (ja) | ポリシー管理方法及び装置 | |
WO2021004191A1 (zh) | 一种支持时间敏感网络的方法及装置 | |
WO2018113504A1 (zh) | 一种用户面锚点选择方法及装置 | |
WO2019154160A1 (zh) | 一种通信方法及装置 | |
WO2021097858A1 (zh) | 一种通信方法及装置 | |
US20230275872A1 (en) | Communication method and apparatus, and computer-readable storage medium | |
EP3659386B1 (en) | Method and device for device-to-device (d2d) communication | |
WO2015143763A1 (zh) | 一种负荷信息传递方法、系统、网元及计算机存储介质 | |
EP4038846A1 (en) | Dynamic activation of local breakout with coordination between application domain and mobile network | |
WO2018174790A1 (en) | User equipment, core network node, radio network node and methods for handling application layer measurements | |
US12034821B2 (en) | Computing aware-session management method and communication apparatus | |
US20230300210A1 (en) | Computing aware-session management method and communication apparatus | |
US20230345347A1 (en) | Method for determining mec access point and apparatus |
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: 18856799 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2018856799 Country of ref document: EP Effective date: 20200311 |
|
ENP | Entry into the national phase |
Ref document number: 2018332696 Country of ref document: AU Date of ref document: 20180904 Kind code of ref document: A |