WO2019179372A1 - 业务切换处理方法、相关产品及计算机存储介质 - Google Patents

业务切换处理方法、相关产品及计算机存储介质 Download PDF

Info

Publication number
WO2019179372A1
WO2019179372A1 PCT/CN2019/078364 CN2019078364W WO2019179372A1 WO 2019179372 A1 WO2019179372 A1 WO 2019179372A1 CN 2019078364 W CN2019078364 W CN 2019078364W WO 2019179372 A1 WO2019179372 A1 WO 2019179372A1
Authority
WO
WIPO (PCT)
Prior art keywords
mec platform
channel
service data
indication information
target
Prior art date
Application number
PCT/CN2019/078364
Other languages
English (en)
French (fr)
Inventor
甘璐
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19771907.3A priority Critical patent/EP3761603B1/en
Publication of WO2019179372A1 publication Critical patent/WO2019179372A1/zh
Priority to US17/029,542 priority patent/US11445411B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40Support for services or applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/148Migration or transfer of sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a service switching processing method, a related device, and a computer storage medium.
  • the mobile edge computing (the mobile edge computing, which is deployed near the UE side) is designed.
  • MEC MEC platform for processing service data of the UE.
  • the corresponding application app is designed in the MEC platform to process the service data of the UE.
  • the UE when the UE sends a service processing request to the server AS in the network, it is routed to the target application in the MEC platform for processing.
  • the target application in the MEC platform for processing.
  • one or more base station eNBs can share (co-deploy) one MEC platform for cost savings. Therefore, it is found in practice that when the UE switches to a base station that is not deployed by the MEC platform, or switches to a base station corresponding to the target application that processes the service data of the UE without the MEC platform, the handover process This causes service interruption between the UE and the source MEC platform, reducing the reliability and efficiency of service processing.
  • the embodiments of the present invention disclose a service switching processing method, a related product, and a computer storage medium, which can solve the problem of service interruption between the UE and the source MEC platform that occurs in the UE handover process in the prior art.
  • an embodiment of the present invention provides a service switching processing system, where the system includes a source mobile edge computing MEC platform and a cloud server AS, where:
  • the source MEC platform is configured to send first indication information to the AS, where the target application is to stop processing the service data of the user equipment UE, where the first indication information is used to indicate that the information is to be Processing the service data of the UE in the AS, where the target application is deployed in the source MEC platform, where the target application is an application for processing service data of the UE;
  • the AS is configured to send, by using the first indication information, a first response message to the source MEC platform, where the first response message is used to indicate that the AS is ready to process service data of the UE.
  • the determining that the target application will stop processing the service data of the UE includes: the source MEC platform acquiring an operation instruction for the target application, or the source MEC platform receives a handover notification sent by the base station; wherein the operation instruction includes at least one of the following: an update instruction, an uninstall instruction, and a reconfiguration instruction.
  • the update instruction as an example, when the source MEC platform detects an update operation, such as upgrading, patching, etc., for the target application deployed thereon, the target application cannot provide the corresponding service service during the update process, Determining that the source MEC platform will stop processing the service data of the UE.
  • the first indication information is used to indicate that the AS switches a user state to an active state to wait for processing service data of the UE, where a user status in the AS is used to indicate Whether to process the service data of the UE in the AS;
  • the AS is specifically configured to switch the user state to an active state according to the indication of the first indication information, and send the first response message to the source MEC platform; where the first response message is Also used to indicate that the AS has switched the user state to an active state.
  • the first indication information is further used to indicate that a data synchronization function between the source MEC platform and the AS is initiated to be used to store the UE in the source MEC platform.
  • the service data is synchronized to the processing in the AS; the first response message is further used to indicate that the data synchronization function between the source MEC platform and the AS is allowed to be started.
  • the source MEC platform is further configured to send the stored service data of the UE to the AS, where the AS is further configured to receive the location sent by the source MEC platform. Describe the service data of the UE, and process the service data of the UE.
  • the first indication information is further used to indicate that the AS applies for a first resource, where the first resource is a resource used by the AS to process service data of the UE (specifically, Computing resources and storage resources, such as resources such as memory and threads);
  • the AS is specifically configured to apply, by the UE, the first resource according to the indication of the first indication information, and send the first response message to the source MEC platform; where the first response is The message is further used to indicate that the AS has applied for the first resource.
  • the system further includes a UE, where the source MEC platform sends the first indication information to the AS, and the UE is further configured to send a first creation request to the AS, where The first creation request carries a first channel parameter, and is used to request to create a first channel used for communication between the UE and the AS; the AS is further configured to respond to the first creation request to the UE Sending a first creation response for notifying that the first channel has been successfully created.
  • the source MEC platform before the source MEC platform sends the first indication information to the AS,
  • the UE is configured to send a second creation message to the source MEC platform, where the second creation message carries a second channel parameter, and is used to request to create a communication between the UE and the source MEC platform.
  • a second channel configured to send the service data of the UE to the source MEC platform by using the second channel;
  • the source MEC platform is configured to send the second indication information to the AS after receiving the second creation message, where the second indication information is used to indicate that the service data of the UE is not processed in the AS,
  • the second creation message is used to request to create a second channel used when communication between the UE and the source MEC platform is performed;
  • the AS in response to the second indication information, sends a second response message to the source MEC platform, where the second response message is used to indicate that the AS has determined that the service data of the UE is not processed;
  • the source MEC platform is further configured to: after receiving the second response message, send a second creation response to the UE, where the second creation response is used to indicate that the second channel has been successfully created.
  • first channel is created in preference to the second channel.
  • the second indication information is used to indicate that the AS switches the user state to an idle state to not process the service data of the UE in the AS.
  • the AS is specifically configured to switch the user state to an idle state according to the indication of the second indication information, and send the second response message to the source MEC platform; the second response message is further used.
  • the second indication information is further used to indicate that the AS releases a second resource, where the second resource is a resource used by the AS to process service data of the UE;
  • the AS is configured to: release the second resource according to the indication of the second indication information, and send the second response message to the source MEC platform; the second response message is further used to indicate The AS has released the second resource.
  • the AS is further configured to send third indication information to the UE, where the The third indication information is used to send the service data of the UE to the AS, and the UE is further configured to send a third response message to the AS, in response to the third indication information, the third The response message is used to notify the UE that it has determined to send the service data of the UE to the AS for processing.
  • the third indication information is used to indicate that the UE switches the second channel to the first channel, to send the service data of the UE to the AS by using the first channel.
  • the first channel is a channel used for communication between the UE and the AS
  • the second channel is a channel used for communication between the UE and the source MEC platform
  • the first channel is created in preference to the second channel;
  • the third response message is used to indicate that the UE has switched the second channel to the first channel.
  • the UE is further configured to send the service data of the UE to the AS for processing; and the AS is further configured to receive and process service data of the UE.
  • the AS is further configured to send fourth indication information to the source MEC platform, where The fourth indication information is used to indicate that the communication between the source MEC platform and the UE is disconnected; the source MEC platform is further configured to wait for the source MEC platform according to the indication of the fourth indication information. The communication with the UE is disconnected.
  • the fourth indication information is used to indicate that the source MEC platform switches a user state in the target application to a waiting state to wait between the source MEC platform and the UE.
  • the source MEC platform is specifically configured to switch the user state of the target application to a waiting state according to the indication of the fourth indication information.
  • the fourth indication information is further used to indicate that the source MEC platform releases a third resource, where the third resource is used by the source MEC platform to process service data of the UE.
  • the source MEC platform is specifically configured to release the third resource according to the indication of the fourth indication information.
  • the source MEC platform is further configured to: after detecting that the UE leaves the source MEC platform, or the target application in the source MEC platform stops processing service data of the UE, And determining that the communication between the source MEC platform and the UE has been disconnected.
  • the source MEC platform is further configured to release channel resources occupied between the source MEC platform and the UE after detecting that the UE leaves the source MEC platform, for example, Socket resources, etc.
  • system further includes a target MEC platform
  • the UE is further configured to: when the UE is switched from the source MEC platform to the target MEC platform, or the target application in the target MEC platform re-supports processing service data of the UE, Sending a third creation request to the target MEC platform, where the third creation request carries a third channel parameter, and is used to request to create a third channel used for communication between the UE and the target MEC platform to pass the Transmitting, by the third channel, the service data of the UE to the target MEC platform for processing; the target MEC platform deploying the target application;
  • the target MEC platform is configured to receive the third creation request, create the third channel according to the third channel parameter, and send a third creation response to the UE, where the third creation response is used to indicate The third channel has been created successfully.
  • the target MEC platform is further configured to send a data synchronization request to the AS, to request to synchronize service data of the UE stored in the AS to the target MEC platform.
  • the AS is further configured to receive the data synchronization request, and send a data synchronization response to the target MEC platform, where the data synchronization response is used to indicate that the target MEC platform and the AS are allowed to synchronize.
  • UE's business data is further configured to send a data synchronization request to the AS, to request to synchronize service data of the UE stored in the AS to the target MEC platform.
  • the AS is further configured to send the stored service data of the UE to the target MEC platform for processing; the target MEC platform is further configured to receive and process the UE. Business data.
  • the target MEC platform is further configured to send a fifth indication information to the UE, where The fifth indication information is used to send the service data of the UE to the target MEC platform for processing; the UE is further configured to send a fifth response to the target MEC platform in response to the fifth indication information.
  • the message, the fifth response message is used to notify the UE that the service data of the UE has been determined to be sent to the target MEC platform for processing.
  • the fifth indication information is used to indicate that the UE switches the second channel to the third channel, to send the service data of the UE to the third channel by using the third channel. Processing in the target MEC platform;
  • the UE is specifically configured to switch the second channel to the third channel according to the indication of the fifth indication information, and send a fifth response message to the target MEC platform; the fifth response message And configured to indicate that the UE has switched the second channel to the third channel.
  • the target MEC platform is further configured to send sixth indication information to the AS, where The sixth indication information is used to indicate that the service data of the UE is not processed in the AS; the AS is further configured to respond to the sixth indication information, and send a sixth response message to the target MEC platform, where The sixth response message is used to indicate that the AS has determined that the service data of the UE is not processed.
  • the sixth indication information is used to indicate that the AS switches the user state to an idle state to not process the service data of the UE in the AS.
  • the AS is specifically configured to switch the user state to an idle state according to the indication of the sixth indication information, and send the sixth response message to the target MEC platform; the sixth response message is further used.
  • the sixth indication information is further used to indicate that the AS releases a fourth resource, where the fourth resource is a resource used by the AS to process service data of the UE (specifically, Computing resources and storage resources);
  • the AS is configured to: release the fourth resource according to the indication of the sixth indication information, and send the sixth response message to the target MEC platform; the sixth response message is further used to indicate The AS has released the fourth resource.
  • the application provides a service switching processing method, which is applied to a source mobile edge computing MEC platform, where the method includes:
  • the source MEC platform receives a first response message returned by the AS, where the first response message is used to notify that the AS is ready to process service data of the UE.
  • the present application provides a service switching processing method, which is applied to a cloud server AS, and the method includes:
  • the AS Receiving, by the AS, the first indication information sent by the source MEC platform, where the first indication information is used to indicate that the service data of the user equipment UE is to be processed in the AS;
  • the application provides another service switching processing method, which is applied to a target MEC platform, where the method includes:
  • the target MEC platform Receiving, by the target MEC platform, a third creation request sent by the UE, where the third creation request carries a third channel parameter, and is used to request to create a third channel used for communication between the UE and the target MEC platform. Transmitting, by the third channel, the service data of the UE to the target MEC platform; the target MEC platform is deployed with a target application, where the target application is used to process service data of the UE. application;
  • Creating the third channel according to the third channel parameter and sending a third creation response to the UE, where the third creation response is used to notify that the third channel has been successfully created.
  • the present application provides a service switching processing method, which is applied to a user equipment UE, where the method includes:
  • a creation request to a target device, where the creation request carries a channel parameter preset in the UE, and is used to request to create a channel used for communication between the UE and the target device;
  • the creation response being used to notify that the channel has been successfully created.
  • the creation request is a first creation request
  • the first creation request carries a first channel parameter, and is used to request to create a communication between the UE and the cloud server AS.
  • the first channel is configured to send the service data of the UE to the AS by using the first channel;
  • the second creation request carries a second channel parameter, configured to request to create a second channel used when communication between the UE and the source MEC platform, to pass the Transmitting, by the second channel, the service data of the UE to the source MEC platform for processing;
  • the third creation request carries a third channel parameter, and is used to request to create a third channel used for communication between the UE and the target MEC platform to pass the The third channel sends the service data of the UE to the target MEC platform for processing.
  • the determining that the target application will stop processing the service data of the UE includes: obtaining, by the source MEC platform The operation instruction for the target application, or the source MEC platform receives the handover notification sent by the base station; wherein the operation instruction includes at least one of the following: an update instruction, an uninstall instruction, and a reconfiguration instruction.
  • the first indication information is used to indicate that the AS switches a user state to an active state to wait for processing The service data of the UE, where the user status in the AS is used to indicate whether the service data of the UE is processed in the AS;
  • the AS switches the user state to an active state according to the indication of the first indication information, and sends the first response message to the source MEC platform; wherein the first response message is further used to indicate The AS has switched the user state to an active state.
  • the first indication information is further used to indicate that the data between the source MEC platform and the AS is requested to be initiated.
  • a synchronization function to synchronize the service data of the UE stored in the source MEC platform to the AS; the first response message is further used to indicate that the source MEC platform and the AS are allowed to be started.
  • Data synchronization feature to indicate that the source MEC platform and the AS are allowed to be started.
  • the source MEC platform sends the stored service data of the UE to the AS for processing; accordingly,
  • the AS receives the service data of the UE sent by the source MEC platform, and processes the service data of the UE.
  • the first indication information is further used to indicate that the AS applies for a first resource, where the first resource is
  • the AS is configured to process the resource of the service data of the UE; correspondingly, the AS applies, according to the indication of the first indication information, the first resource to the UE, and sends the first resource to the source MEC platform.
  • the first response message is further configured to indicate that the AS has applied for the first resource.
  • the method before the source MEC platform sends the first indication information to the AS, the method further includes: the UE Sending a first creation request to the AS, where the first creation request carries a first channel parameter, and is used to request to create a first channel used for communication between the UE and the AS; correspondingly, the AS response
  • the first creation request sends a first creation response to the UE, to notify that the first channel has been successfully created.
  • the UE receives the first creation response message sent by the AS.
  • the source MEC platform before the source MEC platform sends the first indication information to the AS,
  • the source MEC platform after receiving the second creation message, sends second indication information to the AS, where the second indication information is used to indicate that the service data of the UE is not processed in the AS,
  • the second creation message is used to request to create a second channel used when communication between the UE and the source MEC platform is performed;
  • the AS receives the second indication information, and sends a second response message to the source MEC platform in response to the second indication information, where the second response message is used to indicate that the AS has determined not to process the UE.
  • Business data ;
  • the source MEC platform after receiving the second response message, sends a second creation response to the UE, where the second creation response is used to indicate that the second channel has been successfully created.
  • the UE receives the second creation response sent by the source MEC platform.
  • the second indication information is used to indicate that the AS switches the user state to an idle state, so as not to Processing the service data of the UE in the AS; the AS switches the user state to an idle state according to the indication of the second indication information, and sends the second response message to the source MEC platform; The second response message is further used to indicate that the AS has switched the user state to an idle state.
  • the second indication information is further used to indicate that the AS releases a second resource, where the second resource is The AS is configured to process the resource of the service data of the UE; the AS releases the second resource according to the indication of the second indication information, and sends the second response message to the source MEC platform; The second response message is further used to indicate that the AS has released the second resource.
  • the method further includes: the AS sending third indication information to the UE, where the third indication information is used to indicate that the service data of the UE is sent to the AS for processing; and accordingly, the UE responds to the The third indication information is sent to the AS, where the third response message is used to notify the UE that the service data of the UE has been determined to be sent to the AS for processing.
  • the AS receives the third response message sent by the UE.
  • the third indication information is used to indicate that the UE switches the second channel to the first channel to pass the Transmitting, by the first channel, the service data of the UE to the AS, where the first channel is a channel used for communication between the UE and the AS, and the second channel is the a channel used for communication between the UE and the source MEC platform, and the first channel is created in preference to the second channel; the third response message is used to indicate that the UE has switched the second channel For the first channel.
  • the method further includes: the UE sending the service data of the UE to the AS for processing; corresponding The AS receives and processes the service data of the UE.
  • the AS After the service data of the UE is successfully synchronized between the source MEC platform and the AS, the AS Sending, to the source MEC platform, fourth indication information, where the fourth indication information is used to indicate waiting for communication disconnection between the source MEC platform and the UE; correspondingly, the source MEC platform is configured according to the The indication of the four indication information waits for the communication disconnection between the source MEC platform and the UE.
  • the fourth indication information is used to indicate that the source MEC platform switches a user state in the target application to Waiting for a state to wait for communication disconnection between the source MEC platform and the UE; the source MEC platform switches the user state of the target application to a waiting state according to the indication of the fourth indication information.
  • the fourth indication information is further used to indicate that the source MEC platform releases a third resource, where the third resource And the source MEC platform is configured to process the computing resource and the storage resource of the service data of the UE; and the source MEC platform releases the third resource according to the indication of the fourth indication information.
  • the method further includes: the source MEC platform detecting that the UE leaves the source MEC platform, or After the target application in the source MEC platform stops processing the service data of the UE, it is determined that the communication between the source MEC platform and the UE is disconnected.
  • the method further comprises: switching from the source MEC platform to the target MEC platform, or If the target application in the target MEC platform re-supports processing the service data of the UE, the UE sends a third creation request to the target MEC platform, where the third creation request carries the third channel parameter. And a third channel used for requesting to establish communication between the UE and the target MEC platform, to transmit the service data of the UE to the target MEC platform by using the third channel;
  • the target MEC platform is deployed with the target application;
  • the target MEC platform receives the third creation request, creates the third channel according to the third channel parameter, and sends a third creation response to the UE, where the third creation response is used to indicate The third channel has been created successfully.
  • the method further includes: the target MEC platform sending a data synchronization request to the AS, for requesting The service data of the UE stored in the AS is synchronized to the target MEC platform; the AS receives the data synchronization request, and sends a data synchronization response to the target MEC platform, where the data synchronization response is used to indicate The service data of the UE is allowed to be synchronized between the target MEC platform and the AS.
  • the method further includes: the AS transmitting the stored service data of the UE to the target MEC platform Processing; correspondingly, the target MEC platform receives and processes the service data of the UE.
  • the method after starting to synchronize the service data of the UE between the target MEC platform and the AS, the method also includes:
  • the target MEC platform sends a fifth indication information to the UE, where the fifth indication information is used to indicate that the service data of the UE is sent to the target MEC platform for processing; accordingly, the UE responds to the The fifth indication information is sent to the target MEC platform, where the fifth response message is used to notify the UE that the service data of the UE has been determined to be sent to the target MEC platform for processing.
  • the fifth indication information is used to indicate that the UE switches the second channel to the third channel Transmitting, by the third channel, the service data of the UE to the target MEC platform; the UE switching the second channel to the third according to the indication of the fifth indication information Channel, and sending a fifth response message to the target MEC platform; the fifth response message is used to indicate that the UE has switched the second channel to the third channel.
  • the method After the service data of the UE is successfully synchronized between the target MEC platform and the AS, the method also includes:
  • the target MEC platform sends a sixth indication information to the AS, where the sixth indication information is used to indicate that the service data of the UE is not processed in the AS; accordingly, the AS responds to the sixth indication information. And sending a sixth response message to the target MEC platform, where the sixth response message is used to indicate that the AS has determined that the service data of the UE is not processed.
  • the sixth indication information is used to indicate that the AS switches the user state to an idle state, so as not to Processing the service data of the UE in the AS; the AS switches the user state to an idle state according to the indication of the sixth indication information, and sends the sixth response message to the target MEC platform; The sixth response message is further used to indicate that the AS has switched the user state to an idle state.
  • the sixth indication information is further used to indicate that the AS releases a fourth resource, where the fourth resource is The AS is configured to process the resource of the service data of the UE; the AS releases the fourth resource according to the indication of the sixth indication information, and sends the sixth response message to the target MEC platform; The sixth response message is further used to indicate that the AS has released the fourth resource.
  • an embodiment of the present invention provides a source MEC platform, including a functional unit for performing the method of the second aspect above.
  • the embodiment of the present invention provides a cloud server AS, including a functional unit for performing the method of the foregoing third aspect.
  • an embodiment of the present invention provides a target MEC platform, including a functional unit for performing the method of the foregoing fourth aspect.
  • the embodiment of the present invention provides a user equipment UE, including a functional unit for performing the method of the foregoing fifth aspect.
  • an embodiment of the present invention provides a network device, including a memory, a communication interface, and a processor coupled to the memory and a communication interface; the memory is configured to store an instruction, and the processor is configured to execute the An instruction, the communication interface is configured to communicate with other devices (eg, a user equipment, a cloud server AS, a network device deploying a source MEC platform, or a network device of a target MEC platform) under control of the processor; wherein the processor performs The instructions perform the method described in any of the second to fourth aspects above.
  • devices eg, a user equipment, a cloud server AS, a network device deploying a source MEC platform, or a network device of a target MEC platform
  • an embodiment of the present invention provides a user equipment, including a memory, a communication interface, and a processor coupled to the memory and a communication interface; the memory is configured to store an instruction, and the processor is configured to execute the
  • the communication interface is configured to communicate with other devices (specifically, a cloud server, a network device deploying a target MEC platform or a source MEC platform, etc.) under the control of the processor; wherein the processor performs The instructions described above perform the method described in the fifth aspect above.
  • a computer readable storage medium storing program code for a service switching process.
  • the program code includes instructions for performing the method described in any of the second to fifth aspects above.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method described in any one of the second to fifth aspects above.
  • FIG. 1 is a schematic flowchart of a service switching processing method provided by the prior art.
  • FIG. 2 is a schematic diagram of a network framework according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a service switching processing method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart diagram of still another service switching processing method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart diagram of still another service switching processing method according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a first device according to an embodiment of the present invention.
  • FIG. 6B is a schematic structural diagram of another first device according to an embodiment of the present invention.
  • the target application is deployed in the MEC platform, and is used to process service data of the UE.
  • the UE does not perceive the existence of the MEC platform.
  • the service processing request sent by the UE to the network will be routed to the target application on the MEC platform for processing.
  • one or more base station eNBs can share one MEC platform.
  • the handover of the MEC platform may also occur, which may result in the following situations: the UE switches to the base station without the MEC platform deployment, or switches to the MEC platform deployment but the target application does not exist on the platform.
  • the corresponding base station will cause service interruption between the UE and the source MEC platform.
  • FIG. 1 is a schematic flowchart of a service switching processing method provided in the prior art. The method as described in FIG. 1 includes the following implementation steps:
  • the UE reports a signal measurement report to the source base station eNB.
  • the source base station receives a signal measurement report reported by the UE.
  • the source base station eNB may determine that the UE needs to be handed over to the target base station eNB according to parameters (such as cell signal quality, etc.) in the signal measurement report.
  • the source base station may obtain context information of the UE to be switched, and send a handover notification to the source MEC platform corresponding to the source base station, where the handover notification is used to notify the UE to switch to The target base station eNB.
  • the handover notification may carry information such as an identifier of the target base station, an identifier of the UE, and an identifier of the source base station. Accordingly, the source MEC platform receives the handover notification.
  • the source MEC platform searches for a target MEC platform corresponding to the target base station according to the identifier of the target base station. Specifically, the source MEC platform searches for a target MEC platform corresponding to the target base station from a locally configured mapping table according to the identifier of the target base station.
  • the mapping table is configured by the user side or the source MEC platform side, and the mapping table may include an MEC platform corresponding to each of the multiple base stations, where the multiple base stations may include but are not limited to the source base station. Adjacent cell base stations, etc.
  • the plurality of base stations include at least the target base station, that is, the mapping table includes at least a mapping relationship between the target base station and the target MEC platform.
  • the source MEC platform searches for service data (also referred to as application data) of the UE stored in the source MEC platform according to the identifier of the UE.
  • service data also referred to as application data
  • the source MEC platform sends the service data of the UE to the target MEC platform; correspondingly, the target MEC platform receives the service data of the UE.
  • the target MEC platform synchronously receives the service data of the UE, sends a first response message to the source MEC platform, where the service data of the UE is synchronized.
  • the source MEC platform receives the first response message.
  • the source MEC platform after the source MEC platform receives the first response message, send a second response message to the source base station, to indicate that the UE is allowed to perform handover of the source base station or the source MEC platform.
  • the source base station receives the second response message.
  • the UE After receiving the handover instruction, the UE switches from the source base station to the target base station.
  • FIG. 1 shows a current service switching process flow for the MEC platform, in which the following problems exist:
  • the UE may be switched to the base station where the target MEC platform is not deployed, or may be switched to the base station where the target MEC platform is deployed, but there is no target application in the target MEC platform, and the service of the UE cannot be processed. data.
  • the service between the UE and the source MEC platform is interrupted, and the lossless processing of the service cannot be implemented, thereby reducing the reliability of the service processing.
  • the source MEC platform needs to store a mapping table, which includes information such as the MEC platform deployed by the neighboring base stations, so as to determine the location during the UE handover process.
  • the target MEC platform corresponding to the target base station. It can be understood that the information in the mapping table is usually manually configured by the user, and depends on the active behavior of the user, and the configuration operation is quite complicated, the maintenance cost is high, and it is difficult to promote.
  • the target MEC platform since the target MEC platform does not have the service data (or application data) of the UE, the target MEC platform needs to complete synchronization with the source MEC platform for the service data of the UE.
  • the service data for example, video data
  • the handover duration of the UE for the source base station or the source MEC platform may be increased, and the UE may not access the target base station or the target MEC platform in time.
  • the signal quality of the base station is degraded, which will also cause problems such as communication interruption.
  • FIG. 2 shows a schematic diagram of a possible network framework, which includes a user equipment UE 100, a source access network device 102, a source MEC platform 104, a target access network device 106, a target MEC platform 108, and a cloud server AS. 110.
  • the number of devices or platforms in the schematic diagram of the network framework is not limited in this application.
  • the UE 100 is configured to access the network through an access network device (the illustration may specifically be the source access network device 102 or the target access network device 106), and then communicate with the MEC platform or the cloud server AS.
  • an access network device such as a base station
  • the UE may establish a communication connection with the target application through an access network device (such as a base station), thereby performing data interaction with each other to
  • the service data of the UE is processed by means of the target application.
  • the target application is an application for processing service data of the UE, and may be installed on a MEC platform (the illustration may be a source MEC platform 104 and/or a target MEC platform 108), a cloud server AS 110, and the like. in.
  • the UE does not perceive whether the target application is deployed in the cloud server AS or the MEC platform.
  • the UE may be a mobile phone, a tablet personal computer, a personal digital assistant (PDA), a mobile internet device (MID), or a wearable device.
  • PDA personal digital assistant
  • MID mobile internet device
  • the terminal side device does not limit the specific form or type of the UE.
  • the access network device (specifically, the source access network device 102 or the target access network device 106) is a network device that accesses the UE to the network. It can be used to determine whether the UE needs to switch the access network device according to the signal measurement report reported by the UE. If necessary, a handover notification may be sent to the MEC platform that is correspondingly deployed by the access network device, to notify the UE that the access network device is to be switched.
  • one or more access network devices may be deployed corresponding to one or more MEC platforms, or may not deploy the MEC platform.
  • the source access network device and the target access network device in the illustration may be the same type or different types of access network devices, including but not limited to terrestrial wireless access.
  • Evolved NodeB eNB
  • HeNB Home Evolved NodeB
  • RNC Radio Network Controller
  • BSC Base station controller
  • the MEC platform (specifically, the source MEC platform 104 or the target MEC platform 108) is configured to be deployed close to the UE.
  • the MEC platform is deployed with a target application for processing service data of the UE.
  • the MEC platform may route the service processing request to the target application in the MEC platform for processing according to a preset routing rule.
  • the cloud server AS 110 is an application server deployed in the cloud network, and can also be used to process service data of the UE.
  • the target application is deployed in the AS, and the target application is used to process the service data of the UE.
  • the UE is pre-configured with the AS's connection information, such as the IP address of the AS, the communication port, and the like.
  • the access network device such as the base station eNB or the MEC platform corresponding to the access network device may be involved, but the address of the cloud server AS does not change, and does not affect the UE and the application layer on the application layer. Data interaction between ASs.
  • FIG. 3 is a schematic flowchart diagram of a service switching processing method according to an embodiment of the present invention. The method as described in FIG. 3 may include the following steps:
  • the source MEC platform sends a first indication information to the cloud server AS, where the source MEC platform determines that the target application will stop processing the service data of the user equipment UE, where the first indication information is used to indicate that the AS is to wait for processing. UE's business data.
  • the AS receives the first indication information.
  • the target application is deployed in the source MEC platform, and is configured to process service data of the UE.
  • the source MEC platform determines that the target application will stop processing the service data of the UE in the following two ways:
  • the first type after receiving the handover notification sent by the source eNB, the source MEC platform may determine that the target application deployed by itself is about to stop processing the service data of the UE.
  • the handover notification is used to notify the UE to switch from the source base station to the target base station.
  • the UE may report the signal measurement report of the UE to the source base station eNB currently camped by the UE in real time or periodically.
  • the source base station may determine, according to the signal measurement report reported by the UE, that the UE will be handed over from the source base station eNB to the target base station eNB. For example, according to the signal quality of each cell base station in the signal measurement report, it is determined whether the UE needs to be handed over from the source base station to the target base station.
  • the source base station may further send a handover notification to the source MEC platform, to notify the UE to switch from the source eNB to the target eNB.
  • the handover notification may carry information such as an identifier of the UE, an identifier of the source eNB, and an identifier of the target eNB, which is not limited in this application.
  • the second method when the source MEC platform receives the operation instruction for the target application deployed by itself, may determine that the target application is about to stop processing the service data of the UE, and the operation instruction includes any one or more of the following: Combination of items: update instructions, unload/delete instructions, and reconfiguration instructions, or other instructions for making changes to the target application.
  • the reconfiguration command is used to indicate reconfiguration of the target application, such as reconfiguring parameters or communication ports in the target application.
  • the operation instruction is an update instruction
  • the source MEC platform detects that the user performs an operation process such as upgrading, patching, and the like for the target application, an update instruction for the target application is detected.
  • the source MEC platform may determine that the target application will stop processing the service data of the UE, because the service cannot be provided during the target application upgrade or the patching process.
  • the cloud server AS responds to the first indication information, and sends a first response message to the source MEC platform.
  • the first response message is used to notify/instruct the AS that it is ready to process the service data of the UE.
  • the first indication information is specifically used to indicate that the AS switches the user state to the active state to wait for processing the service data of the UE.
  • the target application is also deployed in the AS, and is used to process service data of the UE.
  • the target application corresponds to several user states, and the meanings/indicators of each user state are different.
  • the activation status here is used to indicate that the target application is about to process the service data of the UE. This will be explained in more detail below when it comes to individual user status.
  • the AS may switch the user state (specifically, the user state corresponding to the target application in the AS) to an active state according to the indication of the first indication information.
  • the first response message is sent to the source MEC platform. The first response message is further used to notify the AS that the user state has been switched to an active state to wait for processing the service data of the UE.
  • the first indication information is further used to indicate that a data synchronization function between the source MEC platform and the AS is initiated, that is, start service data synchronization, to store the source MEC platform.
  • the service data of the UE is synchronized to the processing in the AS.
  • the first indication information may be regarded as a synchronization request message.
  • the AS may send the first response message to the source MEC platform in response to the first indication information.
  • the first response message is further used to notify that the data synchronization function is enabled between the source MEC platform and the AS.
  • data synchronization can be performed between the source MEC platform and the AS.
  • the source MEC platform may send the service data of the UE stored by itself to the AS for processing.
  • the AS receives the service data of the UE sent by the source MEC platform, and performs corresponding processing, where the service data is video data, and the AS can cache the video data. Describe video data and more.
  • the first indication information is further used to indicate that the AS applies for a first resource, where the AS processes the service data of the UE.
  • the first resource is used to process the service data of the UE, which may be a computing resource, a storage resource, and other resources related to the UE, such as resources such as memory and threads.
  • the AS may apply for the first resource for the UE according to the indication of the first indication information, for processing service data of the UE. And transmitting the first response message to the source MEC platform.
  • the first response message is further used to notify the AS that the AS has applied for processing the first resource of the service data of the UE.
  • step S101 the following implementation steps may also be included:
  • Step S1001 The UE sends a first creation request to the AS, where the first creation request carries a first channel parameter, and is used to request to create a first channel required for communication between the UE and the AS.
  • Step S1002 After receiving the first creation request, the AS creates the first channel according to the second channel parameter, and sends a first creation response to the UE.
  • the first creation response is used to notify that the first channel has been successfully created.
  • the first channel parameter is a parameter required for creating the first channel, and may be the docking information deployed by the target application in the AS, where the connection information includes but is not limited to the AS Information such as an internet protocol (IP) address, a logical port, a username, a cryptographic communication protocol, and a communication key (or a target application in the AS).
  • IP internet protocol
  • the first channel is a channel used when the UE and the AS communicate, and data interaction between the UE and the AS can be implemented through the channel.
  • the UE sends the service data of the UE to the AS process by using the first channel.
  • step S101 the following implementation steps may be further included:
  • Step S1003 The user equipment UE sends a second creation request to the source MEC platform, where the second creation request carries a second channel parameter, when requesting to establish communication between the UE and the source MEC platform.
  • the second channel required.
  • the second channel parameter is a parameter required for creating the second channel, where the target application may be deployed in the source MEC platform, and the docking information may participate in the foregoing
  • the target application may be deployed in the source MEC platform, and the docking information may participate in the foregoing
  • the second channel is a channel used when the UE and the source MEC platform communicate, and data interaction between them can be realized through the channel.
  • the UE may send the service data of the UE to the source MEC platform for processing by using the second channel.
  • Step S1004 After receiving the first creation request, the source MEC platform creates the first channel according to the first channel parameter, and sends second indication information to the AS.
  • the second indication information is used to indicate that the service data of the UE is not processed in the AS.
  • the AS receives the second indication information.
  • Step S1005 The AS sends a second response message to the source MEC platform in response to the second indication information, where the second response message is used to notify the AS that the AS has determined/not learned that the service data of the UE is not processed. .
  • Step S1006 After receiving the second response message, the source MEC platform sends a first creation response to the UE, where the first creation response is used to notify that the second channel has been successfully created.
  • the second indication information is specifically used to indicate that the AS switches the user state to an idle idle state to notify that the service data of the UE is not processed in the AS.
  • the AS responds to the second indication information, switches the user state to an idle state according to the indication of the second indication information, and sends the second response message to the source MEC.
  • the second response message is further used to notify the AS that the user state has been cut into an idle state.
  • the second indication information is further used to indicate that the AS releases the second resource, and reserves the static resource to reserve/maintain communication between the UE and the AS, and supports transmission between the AS.
  • Handshake messages that is, request and response messages.
  • the second resource is a resource in the AS for processing service data of the UE, and may be a computing resource, a storage resource, or the like.
  • the static resource may refer to account information, rights information, and other information resources that are not changed in real time.
  • the AS in response to the second indication information, releases the second resource according to the indication of the second indication information, and sends the second response message to the source MEC platform.
  • the second response message is further used to indicate that the AS has released the second resource.
  • the UE may further send a third creation request to the target MEC platform corresponding to the target eNB for requesting to create a third channel required for establishing communication between the UE and the target MEC platform. Specifically, it will be explained in detail below.
  • the foregoing first creation request to the third creation request are all channel creation requests sent by the UE to the target device, to request a channel corresponding to the communication between the UE and the target device,
  • the channel sends the service data of the UE to the target device for processing.
  • the target device is any one or more of an AS, a source MEC platform, and a target MEC platform.
  • the method may further include the following implementation steps:
  • Step S103 The AS sends third indication information to the UE, where the third indication information is used to instruct the UE to send the service data of the UE to the AS for processing.
  • the UE receives the third indication information.
  • Step S104 The UE sends a third response message to the AS in response to the third indication information, where the third response message is used to indicate that the UE has determined/known that the service data of the UE is sent to the Said in the AS.
  • a third indication is sent to the UE. information.
  • the data synchronization stability here may be that the rate at which the source MEC platform sends data to the AS reaches a preset rate, or is within a preset rate range.
  • the third indication information may be specifically used to indicate that the UE switches the original second channel to the first channel, so as to subsequently send the service data of the first channel to the AS through the first channel. .
  • the UE switches the second channel to the first channel according to the indication of the third indication information, and sends the third response message to the AS.
  • the third response message is specifically configured to notify the UE that the second channel is switched to the first channel, and subsequently send the service data of the first channel to the AS for processing.
  • the UE and the AS may implement data interaction by using the first channel.
  • the UE sends the service data of the UE to the AS through the first channel; correspondingly, the AS receives and processes the service data of the UE, and further may pass the A channel feeds back the processing result to the UE or the like.
  • the method may further include:
  • Step S105 The AS sends fourth indication information to the source MEC platform, where the fourth indication information is used to indicate waiting for communication disconnection between the source MEC platform and the UE.
  • the source MEC platform receives the fourth indication information.
  • Step S106 The source MEC platform waits for the communication disconnection with the UE in response to the fourth indication information.
  • the AS may send the source MEC to the source MEC.
  • the platform sends a fourth indication message.
  • the fourth indication information is used to indicate that the source MEC platform stops synchronizing the service data of the UE, that is, the service data of the UE is synchronized, and the user state of the target application is switched to wait for the dying state to wait.
  • the communication between the source MEC platform and the UE is disconnected.
  • the source MEC platform also maintains communication with the UE, that is, the second channel used when the source MEC platform and the UE communicate, and can support transmission of simple handshake messages, waiting for them to be disconnected. Then, the channel resources occupied by the second channel are released.
  • the source MEC platform switches the user state to a waiting state according to the indication of the fourth indication information, to wait for the source MEC platform and the UE to communicate disconnected. .
  • the fourth indication information is further used to indicate that the source MEC platform releases the third resource, and reserves the channel resource of the second channel that is communicated by the source MEC platform and the UE, and waits for the disconnection. Release again.
  • the third resource is a resource used by the source MEC platform to process service data of the UE, and may be a computing resource, a storage resource, or the like.
  • the source MEC platform releases the third resource according to the indication of the fourth indication information.
  • the source MEC platform may determine that The communication connection has been disconnected between the source MEC platform and the UE, that is, the communication has been disconnected.
  • the UE and the source MEC platform may periodically exchange handshake messages according to the second channel of the communication between the source MEC platform and the UE, indicating that there is still a channel between them.
  • the source MEC platform may not received the handshake message sent by the UE within a preset duration, it may be determined that the UE has switched off the source MEC platform, and communication between them has been disconnected.
  • the service service cannot be provided at this time, that is, the processing of the service data of the UE is stopped, It may be determined that communication to the source MEC platform and the UE has been disconnected.
  • the channel resources occupied by the source MEC platform and the UE may be released, that is, The second channel occupancy channel resource.
  • the channel resource herein may refer to a resource occupied when the second channel is created, such as a socket connection resource and the like.
  • the method may further comprise the following steps:
  • Step S107 The UE sends a third creation request to the target MEC platform, where the third creation request carries a third channel parameter, and is used to request to create a communication between the UE and the target MEC platform. Three channels.
  • the target MEC platform receives the third creation request.
  • Step S108 After receiving the third creation request, the target MEC platform creates the third channel according to the third channel parameter, and sends a third creation response to the UE, to notify the third channel. Successfully created.
  • the service data of the UE is reprocessed.
  • the target MEC platform is deployed with the target application for processing service data of the UE.
  • the UE may try to communicate with the target MEC platform corresponding to the target eNB in real time or periodically, and create a third channel, so as to subsequently transmit the service data of the UE to the target through the third channel. Processing in the MEC platform.
  • the third channel parameter is a parameter required for creating the third channel, which may specifically be the docking information of the target application in the target MEC platform.
  • the third channel is a channel used for communication between the UE and the target MEC platform, and data interaction between the UE and the target MEC platform can be implemented through the channel.
  • Step S109 The target MEC platform sends a data synchronization request to the AS, to request to synchronize the service data of the UE stored in the AS to the target MEC platform. Accordingly, the AS receives the data synchronization request.
  • Step S110 After receiving the data synchronization request, the AS sends a data synchronization response to the target MEC platform.
  • the data synchronization response is for notifying that data is allowed to be synchronized between the AS and the target MEC platform.
  • the target MEC platform may send a data synchronization request to the AS to request the stored service of the UE by the AS.
  • the data is synchronized to the processing in the target MEC platform.
  • the service data of the UE stored in the AS may be synchronously sent to the target MEC platform for processing.
  • the target MEC platform receives and processes the service data of the UE.
  • the method may further comprise the following steps:
  • Step S111 The target MEC platform sends a fifth indication information to the UE, where the fifth indication information is used to instruct the UE to send the service data of the UE to the target MEC platform for processing.
  • the UE receives the fifth indication information.
  • Step S112 The UE sends a fifth response message to the target MEC platform in response to the fifth indication information, where the fifth response message is used to notify the UE that the service data of the UE is determined/obtained. Send to the target MEC platform for processing.
  • the target MEC platform may The UE sends a fifth indication message.
  • the data synchronization is stable, that is, the rate at which the AS sends data to the target MEC platform reaches a preset rate, or is in a preset rate range.
  • the fifth indication information is specifically used to instruct the UE to switch the first channel of the original communication to the third channel, so as to subsequently send the service data of the UE to the third channel. Processed in the target MEC platform.
  • the UE switches the first channel to a third channel according to the indication of the fifth indication information, and sends the fifth response message to the target MEC platform.
  • the fifth response message is specifically configured to notify the UE that the first channel is switched to the third channel, and subsequently send the service data of the third channel to the target MEC platform for processing. .
  • the UE and the target MEC platform may implement data interaction by using the third channel.
  • the UE sends the service data of the UE to the target MEC platform through the third channel; correspondingly, the target MEC platform receives and processes the service data of the UE, and further The processing result is fed back to the UE or the like through the third channel.
  • the method may further include:
  • Step S113 The target MEC platform sends sixth indication information to the AS, where the sixth indication information is used to indicate that the service data of the UE is not processed in the AS.
  • the AS receives the sixth indication information.
  • Step S114 The AS sends a sixth response message to the target MEC platform in response to the sixth indication information, where the sixth response message is used to notify the AS that the AS has determined/not learned that the service data of the UE is not processed. .
  • the sixth indication information may be sent to the AS.
  • the sixth indication information is used to instruct the AS to notify the target MEC platform to synchronize the service data of the UE, that is, the service data of the UE has been synchronized, and the user state may be switched to an idle idle state. To indicate that the data of the UE is not being processed.
  • the AS switches the user state to an idle state according to the indication of the sixth indication information, to indicate that the service data of the UE is not processed in the AS. And sending the sixth response message to the target MEC platform, where the sixth response message is used to indicate that the AS has switched the user state to an idle state.
  • the sixth indication information is further used to indicate that the AS releases the fourth resource, and reserves the channel resource when the AS and the UE communicate, that is, the channel resource of the first channel, so as to be followed by
  • the target application in the target MEC platform stops processing the service data of the UE the first channel is enabled again, and the service data of the UE is processed by using the AS.
  • the fourth resource is a resource used by the AS to process service data of the UE, and may be a computing resource, a storage resource, or the like.
  • the AS sends the sixth response message to the target MEC platform.
  • the sixth response message is further used to indicate that the AS has released the fourth resource.
  • the foregoing first to fourth resources may include, but are not limited to, computing resources, storage resources, or other resources related to the UE, such as memory and process resources, and the like.
  • the channel created between the UE and the MEC platform it is possible to preferentially use the channel created between the UE and the MEC platform to send the service data of the UE to the MEC platform for processing; when the MEC platform stops processing the service data of the UE, The service data of the UE is sent to the AS for processing by using a channel created between the UE and the AS.
  • FIG. 4 is a schematic flowchart diagram of still another service switching processing method according to an embodiment of the present invention.
  • the method shown in FIG. 4 includes the following implementation steps:
  • Step S201 The user equipment UE pre-configures a channel parameter, where the channel parameter is used to create a channel used by the UE to communicate with a target device (such as a cloud server AS or a network device deploying the MEC platform).
  • a target device such as a cloud server AS or a network device deploying the MEC platform.
  • the channel parameter includes a first channel parameter and a second channel parameter, where the first channel parameter is used to create a first channel used by the UE to communicate with a cloud server AS, and the second channel parameter is used to create The second channel used by the UE to communicate with the source MEC platform.
  • the channel parameter may further include a third channel parameter, configured to create a third channel used by the UE to communicate with the target MEC platform.
  • the target device (here, the AS, the source MEC platform, or the target MEC platform) may be deployed/installed with a target application for processing service data of the UE.
  • the UE may transmit the service data of the UE to the target device by using a corresponding channel (specifically, any one of the first channel to the third channel).
  • the first channel parameter to the third channel parameter may be the same or different channel parameters.
  • the channel parameter may be the docking information required when creating the channel, and may also be understood as the docking information of the target application; it may include, but is not limited to, a network protocol IP address, a logical port used for communication, a username, a password, and the like.
  • Step S202 The UE sends a first creation request to the AS, where the first creation request carries a first channel parameter, and is used to request to create a first channel used by the UE and the AS to communicate.
  • Step S203 After receiving the first creation request, the AS sends a first creation response to the UE, to notify that the first channel has been successfully created.
  • the AS After receiving the first creation request, the AS creates a first channel used by the UE and the AS to communicate with each other according to the first channel parameter, and then feeds back the first creation to the UE. response.
  • Step S204 The UE sends a second creation request to the source MEC platform, where the second creation request carries the second channel parameter, and is used to request to create a second channel used by the UE to communicate with the source MEC platform. .
  • Step S205 After receiving the second creation request, the source MEC platform sends a second indication information to the cloud server AS, where it is used to instruct the AS to switch the user state to an idle state, to indicate/notify subsequent absence of the AS. Processing the service data of the UE.
  • the second channel used by the UE and the source MEC platform to communicate with each other may be created according to the second channel parameter, and the AS is sent to the AS.
  • the second indication information is described.
  • Step S206 After the second indication information is received by the AS, the computing resources and storage resources related to the UE may be released, and the first channel is reserved (that is, the channel resources occupied by the first channel are reserved).
  • the static resource herein refers to a resource that is not changed at any time, such as a user account, a password, and the like, and also retains the channel resource occupied by the first channel, and supports the transmission of a handshake message between the UE and the source MEC platform, that is, the transmission is simple. Request and response (or promise) messages.
  • Step S207 The AS sends a second response message to the source MEC platform, to indicate that the AS has switched the user state to an idle state.
  • Step S208 After the source MEC platform receives the second response message, send a second creation response to the UE, to indicate that the second channel has been successfully created.
  • Step S209 After the second channel is successfully created, the service initialization is successful.
  • the UE and the source MEC platform may perform data interaction through the second channel. For example, the UE sends the service data of the UE to the source MEC platform through the second channel, and the source MEC platform may feed back the processing result to the UE or the like.
  • Step S210 The source MEC platform receives a handover notification sent by the source base station eNB, where the handover notification is used to notify the UE to switch from the source base station to the target base station.
  • Step S211 after the source MEC platform determines, according to the handover notification, that the source MEC platform needs to be switched, sending, to the AS, first indication information, configured to start between the UE and the AS.
  • the data synchronization function is instructed, and the AS is instructed to switch the user state to an active state to notify subsequent processing of the service data of the UE in the AS.
  • the source MEC platform may further determine whether the target MEC platform corresponding to the target base station eNB is the same as the source MEC platform, and if they are the same, the process ends. If they are different, the subsequent process is continued, and the first indication information is sent to the AS.
  • Step S212 After receiving the first indication information, the AS, in response to the first indication information, initiate a data synchronization function between the source MEC platform and the AS, and switch the user state to an active state.
  • the UE may also apply for related computing resources and storage resources, such as memory and thread resources, to process the service data of the UE by using the applied resources.
  • Step S213 The AS sends a first response message to the source MEC platform, to notify that the data synchronization function between the AS and the source MEC platform has been started.
  • the AS is further configured to notify the AS that the user state is switched to an active state, to wait for processing the service data of the UE.
  • the method may further be used to notify that the related computing resources and storage resources have been requested for the UE.
  • Step S214 After the data synchronization function is started between the source MEC platform and the AS, data synchronization between the source MEC platform and the AS may be implemented.
  • the source MEC platform may synchronously send the service data of the UE stored therein to the AS to process the service data of the UE in the AS.
  • Step S215 The AS sends third indication information to the UE, where the UE is configured to switch the second channel in the original communication to the first channel, so as to subsequently perform the service of the UE by using the first channel.
  • the data is sent to the AS for processing.
  • Step S216 After receiving the third indication information, the UE sends a third response message to the AS, in response to the third indication information, to indicate that the UE has switched the second channel to the first One channel.
  • the AS sends the third indication information to the UE. And indicating that the UE subsequently sends the service data of the UE to the AS by using the first channel.
  • the UE receives the third indication information, switches the second channel to the first channel according to the indication of the third indication information, and feeds back a third response message to the AS.
  • Step S217 After the channel is switched, data interaction between the UE and the AS may be implemented by using the first channel. For example, the UE may send the service data of the UE to the AS by using the first channel.
  • the fourth indication information is further used to indicate that the source MEC platform stops and the service data of the UE and the like are synchronized between the ASs.
  • Step S219 After receiving the fourth indication information, the source MEC platform switches the user state to a waiting state according to the indication of the fourth indication information.
  • the source MEC platform may also release the computing resources and storage resources related to the UE, and reserve channel resources occupied by the second channel to support transmission of a simple handshake message, and wait for the communication to be disconnected.
  • the channel resources occupied by the second channel such as socket resources.
  • Step S220 After determining that the UE switches away from the source MEC platform, disconnect the communication connection between the source MEC platform and the UE, that is, disconnect the second channel.
  • the UE may switch to leave the source MEC platform, that is, the UE has switched off the source.
  • Base station eNB The set duration is customized on the user side or the platform side, for example, 10s or the like, and is not limited.
  • Step S222 After the UE is switched from the source MEC platform to the target MEC platform, the third creation request may be sent to the target MEC platform, where the third creation request carries a third channel parameter, and is used to request to create a location.
  • the third channel used for communication between the UE and the target MEC platform.
  • the target application is used to process the service data of the UE, where the UE may A communication attempt is established in real time or periodically with the target MEC platform, ie the UE sends a third creation request to the MEC platform to create the third channel.
  • Step S223 after the third MEB platform receives the third creation request, create the third channel according to the third channel parameter, and send a third creation response to the UE, to notify the third channel. Successfully created.
  • the first channel parameter, the second channel parameter, and the third channel parameter may be referred to the related description in the foregoing embodiment, and details are not described herein again.
  • Step S224 The target MEC platform sends a data synchronization request to the AS, where it is requested to initiate a data synchronization function between the target MEC platform and the AS.
  • Step S225 After receiving the data synchronization request, the AS sends a data synchronization response to the target MEC platform, to notify that the data synchronization function between the target MEC platform and the AS is enabled, the target Data synchronization can be performed between the MEC platform and the AS.
  • Step S226, data synchronization between the AS and the target MEC platform is implemented.
  • the AS sends the service data of the UE stored therein to the target MEC platform for processing or the like.
  • Step S227 The target MEC platform sends a fifth indication information to the UE, where the UE is configured to switch the first channel used by the original communication to a third channel, so that the UE subsequently passes the third channel.
  • the channel sends the service data of the UE to the target MEC platform for processing.
  • Step S228 After receiving the fifth indication information, the UE sends a fifth response message to the target MEC platform, in response to the fifth indication information, to notify the UE that the first channel has been switched. For the third channel.
  • the target MEC platform sends a fifth to the UE.
  • the indication information is used to indicate that the UE subsequently sends the service data of the UE to the target MEC platform by using a third channel.
  • the UE receives the fifth indication information, switches the first channel to a third channel according to the indication of the fifth indication information, and feeds back a fifth response message to the target MEC platform.
  • Step S229 after the channel switching, the UE and the target MEC platform may implement data interaction through the third channel.
  • the UE may send the service data of the UE to the target MEC platform through the third channel for processing.
  • the target MEC platform may feed back the processing result to the UE or the like.
  • Step S230 after the target MEC platform determines that the service data of the UE is synchronized with the AS, the sixth indication information is sent to the AS, and is used to instruct the AS to switch the user status to The idle idle state is used to notify subsequent processing of the service data of the UE in the AS.
  • the sixth indication information is further used to indicate that the AS stops and the service data of the UE and the like are synchronized between the target MEC platform.
  • Step S231 After receiving the sixth indication information, the AS switches the user state to an idle state according to the indication of the sixth indication information.
  • the AS may also release the computing resources and storage resources related to the UE, and reserve channel resources (such as socket resources, etc.) occupied by the first channel, so as to support transmission of a simple handshake message, waiting for the next time.
  • the first channel is enabled to process the service data of the UE by using the AS.
  • Step S232 The AS sends a sixth response message to the target MEC platform, to notify the AS that the user state has been switched to an idle state.
  • the AS may also be used to notify the AS that the relevant computing resources, storage resources, and the like of the UE are released.
  • FIG. 5 is a schematic flowchart diagram of still another service switching processing method according to an embodiment of the present invention.
  • the method shown in FIG. 5 includes the following implementation steps:
  • Step S301 The user equipment UE pre-configures a channel parameter, where the channel parameter is used to create a channel required for the UE to communicate with the target device.
  • the channel parameter may include a preferred channel parameter and an alternate channel parameter, where the preferred channel parameter is used to create a preferred communication when the UE and the MEC platform communicate, such as the second channel and the first in the foregoing embodiment. Three channels and so on.
  • the alternate channel parameter is used to create an alternate channel for communication between the UE and the AS, such as the first channel in the previous embodiment, and the like.
  • a target application is deployed/installed in the target device (here, the AS or the MEC platform) for processing the service data of the UE.
  • the service data of the UE can be transmitted to the target device for processing through a channel (specifically, a preferred channel or an alternate channel).
  • the preferred channel parameter and the candidate channel parameter may be channel parameters required for creating a channel, and may also be understood as docking information of the target application in the target device, which may include but is not limited to Network protocol IP address, logical port used for communication, user name, password, etc.
  • Step S302 The UE sends an alternative creation request to the cloud server AS, where the candidate creation request carries an alternate channel parameter, and is used to request an alternate channel required for the UE and the AS to communicate with each other.
  • Step S303 After receiving the candidate creation request, the AS sends an alternative creation response to the UE, to notify that the candidate channel has been successfully created. Specifically, after the AS receives the candidate creation request, the candidate channel is created according to the candidate channel parameter, so that the AS and the UE subsequently implement data interaction through the candidate channel.
  • Step S304 The UE sends a preferred creation request to the MEC platform, where the preferred creation request carries a preferred channel parameter, and is used to request to create a preferred channel required for communication between the UE and the MEC platform.
  • the MEC platform in this embodiment includes, but is not limited to, a source MEC platform and a target MEC platform, or other platforms that support processing of service data of the UE.
  • Step S305 After receiving the preferred creation request, the MEC platform sends second indication information to the cloud server AS, where it is used to instruct the AS to switch the user state to an idle state, to indicate/notify subsequent processing in the AS.
  • the service data of the UE After receiving the preferred creation request, the MEC platform sends second indication information to the cloud server AS, where it is used to instruct the AS to switch the user state to an idle state, to indicate/notify subsequent processing in the AS.
  • the service data of the UE The service data of the UE.
  • Step S306 after the second indication information is received by the AS, the computing resources and storage resources related to the UE may be released, and the candidate channel is reserved (that is, the channel resources occupied by the candidate channel are reserved).
  • Step S307 The AS sends a second response message to the MEC platform, to indicate that the AS has switched the user state to an idle state.
  • Step S308 After receiving the second response message, the MEC platform sends a second creation response to the UE, to indicate that the candidate channel has been successfully created.
  • Step S309 after the creation of the preferred channel is successful, the service initialization is successful.
  • the UE and the MEC platform can perform data interaction through the preferred channel.
  • Step S310 The MEC platform determines that the target application will stop processing the service data of the UE.
  • the operation instructions include, but are not limited to, a combination of any one or more of the following: an update instruction, a delete/unload instruction, a reconfiguration instruction, and other instructions for making changes to the target application, and the like.
  • an update instruction when the MEC platform detects that the user/system periodically upgrades or patches the target application, it detects an update instruction for the target application, because the target application is being upgraded/played. If the service service cannot be provided during the patching process, it may be determined that the target application will stop processing the service data of the UE.
  • step S311 after the MEC platform determines that the target application will stop processing the service data of the UE, the first indication information is sent to the AS, where the data synchronization function between the UE and the AS is started. And instructing the AS to switch the user state to an active state to notify subsequent processing of the service data of the UE in the AS.
  • Step S312 After receiving the first indication information, the AS, in response to the first indication information, initiates a data synchronization function between the MEC platform and the AS, and switches the user state to an active state.
  • the UE may also apply for related computing resources and storage resources for processing the service data of the UE.
  • Step S313 The AS sends a first response message to the MEC platform, to notify that the data synchronization function between the AS and the MEC platform has been started.
  • Step S314 After the data synchronization function is started between the MEC platform and the AS, data synchronization between the MEC platform and the AS may be implemented.
  • the MEC platform may synchronously send the service data of the UE stored therein to the AS to process the service data of the UE in the AS.
  • Step S315 the AS sends third indication information to the UE, to indicate that the UE switches the preferred channel in the original communication to an alternate channel, so that the service data of the UE is subsequently passed through the candidate channel. Send to the AS for processing.
  • Step S316 After receiving the third indication information, the UE sends a third response message to the AS, in response to the third indication information, to indicate that the UE has switched the preferred channel to an alternative. aisle.
  • Step S317 After the channel is switched, data interaction between the UE and the AS may be implemented by using the first channel. For example, the UE may send the service data of the UE to the AS by using the first channel.
  • Step S319 After receiving the fourth indication information, the MEC platform switches the user state to a waiting state according to the indication of the fourth indication information.
  • the MEC platform may also release computing resources and storage resources related to the UE, and reserve channel resources occupied by the preferred channel.
  • Step S320 After the MEC platform determines that the target application has stopped processing the service data of the UE, disconnect the communication connection between the MEC platform and the UE, that is, disconnect the preferred channel.
  • Step S321 The MEC platform detects that the target application reprocesses the service data of the UE.
  • Step S322 The UE sends a preferred creation request to the MEC platform, where the preferred creation request carries a preferred channel parameter, and is used to request to create the preferred channel used when the UE communicates with the MEC platform.
  • the UE may try to communicate with the MEC platform again periodically/in real time.
  • the MEC platform detects that the target application is used to process the service data of the UE, the UE and the MEC platform may successfully establish a communication connection again.
  • Step S323 After the MEC platform receives the preferred creation request, the preferred channel is created according to the preferred channel parameter, and a preferred creation response is sent to the UE, to notify that the preferred channel has been successfully created.
  • Step S324 The MEC platform sends a data synchronization request to the AS, where it is requested to initiate a data synchronization function between the MEC platform and the AS.
  • Step S325 After receiving the data synchronization request, the AS sends a data synchronization response to the MEC platform, to notify that the data synchronization function between the MEC platform and the AS is enabled, the MEC platform and Data synchronization can be performed between the ASs.
  • Step S326 data synchronization between the AS and the MEC platform is implemented.
  • the AS sends the service data of the UE stored therein to the MEC platform for processing or the like.
  • Step S327 the MEC platform sends a fifth indication information to the UE, to indicate that the UE switches the backup channel used by the original communication to a preferred channel, so that the UE subsequently performs the The service data of the UE is sent to the MEC platform for processing.
  • Step S328 After receiving the fifth indication information, the UE sends a fifth response message to the MEC platform, in response to the fifth indication information, to notify the UE that the candidate channel has been switched to Preferred channel.
  • Step S329 after the channel switching, the UE and the MEC platform may implement data interaction through the preferred channel.
  • Step S330 after the MEC platform determines that the service data of the UE is successfully synchronized with the AS, sending the sixth indication information to the AS, where the AS is instructing the AS to switch the user state to idle.
  • the idle state is used to notify subsequent processing of the service data of the UE in the AS.
  • Step S331 After receiving the sixth indication information, the AS switches the user state to an idle state according to the indication of the sixth indication information.
  • the AS may also release the computing resources and storage resources related to the UE, and reserve channel resources (such as socket resources, etc.) occupied by the candidate channel.
  • Step S332 The AS sends a sixth response message to the MEC platform, to notify the AS that the user state has been switched to an idle state.
  • the AS may also be used to notify the AS that the relevant computing resources, storage resources, and the like of the UE are released.
  • the service interruption may occur after the target application in the MEC platform stops processing the service data of the UE (ie, stops the service service).
  • the MEC platform (which may be a source MEC platform and/or a target MEC platform) may be deployed as a network device in a network.
  • the first device specifically, the user equipment or the network device, where the network device may be a cloud server or a network device for deploying the source MEC platform or the target MEC platform
  • the first device includes The corresponding hardware structure and/or software modules for each function are executed.
  • the embodiments of the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present invention.
  • the embodiment of the present invention may divide the functional unit into the first device according to the foregoing method example.
  • each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 6A shows a possible structural diagram of the first device involved in the above embodiment.
  • the first device 700 includes a processing unit 702 and a communication unit 703.
  • the processing unit 702 is configured to perform control management on the action of the first device 700.
  • the processing unit 702 when the first device 700 is the user equipment 700, the processing unit 702 is configured to support the first device 700 to perform steps S201 and S216 in FIG. 4, steps S301 and S316 in FIG. 5, and / or other steps for performing the techniques described herein.
  • the communication unit 703 is configured to support communication between the first device 700 and other devices.
  • the communication unit 703 is configured to support the first device 700 to perform steps S1001, S1003, S1006, S104, S107, and S111 in FIG. 3, step S202 in FIG.
  • the processing unit 702 is configured to support the first device 700 to perform S102 and S104 in FIG. 3, steps S206, S212, and S231 in FIG. Steps S306, S312, and S331 in FIG. 5, and/or other steps for performing the techniques described herein.
  • the communication unit 703 is configured to support communication between the first device 700 and other devices.
  • the communication unit 703 is configured to support the first device 700 to perform S1002, S1005, S104, S105, S110, and S114 in FIG. 3, step S207 in FIG.
  • the processing unit 702 is configured to support the first device 700 to perform S106 in FIG. 3, step S210 in FIG. Steps S310, S319, and S321, and/or other steps for performing the techniques described herein.
  • the communication unit 703 is configured to support communication between the first device 700 and other devices.
  • the communication unit 703 is configured to support the first device 700 to perform steps S1004 and S1006 in FIG. 3, steps S205, S209, and S211 in FIG. S305, S309, S311, S327, S329, and S330, and/or other steps for performing the techniques described herein.
  • the processing unit 702 is configured to support the first device 700 to perform S108 in FIG. 3, S223 in FIG. Step S323 in Figure 5, and/or other steps for performing the techniques described herein.
  • the communication unit 703 is configured to support communication between the first device 700 and other devices.
  • the communication unit 703 is configured to support the first device 700 to perform S109, S111, and S113 in FIG. 3, and steps S224, S226, S227, and S229 in FIG. S230, steps S305, S308, S311, S314, S324, S326, S327, S329, and S330 in FIG. 5, and/or other steps for performing the techniques described herein.
  • the first device 700 may further include a storage unit 701, configured to store program codes and data of the first device 700.
  • the processing unit 702 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application specific integrated circuit. (English: Application-Specific Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 703 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces, such as an interface between the network device and other devices.
  • the storage unit 701 can be a memory.
  • the processing unit 702 is a processor
  • the communication unit 703 is a communication interface
  • the storage unit 701 is a memory
  • the first device involved in the embodiment of the present invention may be the first device shown in FIG. 6B.
  • the first device 710 includes a processor 712, a communication interface 713, and a memory 77.
  • the first device 710 may further include a bus 714.
  • the communication interface 713, the processor 712, and the memory 77 may be connected to each other through a bus 714;
  • the bus 714 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard structure (English: Extended Industry) Standard Architecture (EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 714 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 6B, but it does not mean that there is only one bus or one type of bus.
  • FIG. 6A or FIG. 6B may also refer to the corresponding description of the foregoing method embodiments, and details are not described herein again.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions can be composed of corresponding software modules, which can be stored in random access memory (English: Random Access Memory, RAM), flash memory, read only memory (English: Read Only Memory, ROM), erasable and programmable. Read only memory (English: Erasable Programmable ROM, EPROM), electrically erasable programmable read only memory (English: Electrically EPROM, EEPROM), registers, hard disk, mobile hard disk, compact disk (CD-ROM) or well known in the art Any other form of storage medium.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a network device. Of course, the processor and the storage medium may also reside as a discrete component in the first device.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例公开了业务切换处理方法、相关产品、系统及计算机存储介质,其中所述系统包括:源MEC平台,用于在确定到目标应用将停止处理用户设备UE的业务数据的情况下,向所述AS发送第一指示信息,用于指示在所述AS中处理所述UE的业务数据,所述源MEC平台中部署有所述目标应用,所述目标应用为用于处理所述UE的业务数据的应用;云服务器AS,用于响应所述第一指示信息,向所述源MEC平台发送第一响应消息,用于指示所述AS已准备好处理所述UE的业务数据。采用本发明实施例,能够解决现有技术中在UE切换离开源MEC平台后,导致UE和源MEC平台之间出现业务中断等问题,进而提升了业务处理的可靠性和高效性。

Description

业务切换处理方法、相关产品及计算机存储介质
本申请要求于2018年3月23日提交中国国家知识产权局、申请号为201810251267.6、发明名称为“业务切换处理方法、相关产品及计算机存储介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域,尤其涉及业务切换处理方法、相关设备及计算机存储介质。
背景技术
为降低应用服务器(application service,AS)的计算负荷,同时降低用户设备(user equipment,UE)和服务器AS之间的传输时延,特设计出就近UE端部署的移动边缘计算(mobile edge computing,MEC)平台,用于处理UE的业务数据。具体的,在MEC平台中设计对应的应用app来处理UE的业务数据。
在实际应用中,UE向网络中的服务器AS发送的业务处理请求时,会被路由到MEC平台中的目标应用处进行处理。通常情况下,为节省成本,一个或多个基站eNB可共用(共同部署)一个MEC平台。由此在实践中发现,当UE切换到没有MEC平台部署的基站,或者切换到有MEC平台但该平台没有部署用于处理UE的业务数据的目标应用所对应的基站时,在切换过程中会造成UE和源MEC平台之间的业务中断,降低业务处理的可靠性和高效性。
发明内容
本发明实施例公开了业务切换处理方法、相关产品及计算机存储介质,能够解决现有技术中在UE切换过程中出现的UE和源MEC平台之间的业务中断等问题。
第一方面,本发明实施例公开提供了一种业务切换处理系统,所述系统包括源移动边缘计算MEC平台以及云服务器AS,其中:
所述源MEC平台,用于在确定到目标应用将停止处理用户设备UE的业务数据的情况下,向所述AS发送第一指示信息;其中,所述第一指示信息用于指示将在所述AS中处理所述UE的业务数据,所述源MEC平台中部署有所述目标应用,所述目标应用为用于处理所述UE的业务数据的应用;
所述AS,用于响应所述第一指示信息,向所述源MEC平台发送第一响应消息,所述第一响应消息用于指示所述AS已准备好处理所述UE的业务数据。
通过实施本发明实施例,能够解决现有技术中在UE切换过程中,出现UE和源MEC平台之间的业务中断等问题。
在一些可能的实施例中,所述确定到目标应用将停止处理所述UE的业务数据,包括:所述源MEC平台获取到针对所述目标应用的操作指令,或者所述源MEC平台接收到基站发送的切换通知;其中,所述操作指令包括以下中的至少一项:更新指令、卸载指令以及重配置指令。以所述更新指令为例,当所述源MEC平台检测到针对其上部署的目标应用进行升级、打补丁等更新操作,由于所述目标应用在更新过程中不能提供相应地业务服务,则可确定所述源MEC平台将停止处理所述UE的业务数据。
在一些可能的实施例中,所述第一指示信息用于指示所述AS将用户状态切换为激活状态,以等待处理所述UE的业务数据;其中,所述AS中的用户状态用于指示是否在所述AS中处理所述UE的业务数据;
所述AS,具体用于根据所述第一指示信息的指示,将所述用户状态切换为激活状态,并向所述源MEC平台发送所述第一响应消息;其中,所述第一响应消息还用于指示所述AS已将所述用户状态切换为激活状态。
在一些可能的实施例中,所述第一指示信息还用于指示请求启动所述源MEC平台和所述AS之间的数据同步功能,以将所述源MEC平台中存储的所述UE的业务数据同步至所述AS中处理;所述第一响应消息还用于指示允许启动所述源MEC平台和所述AS之间的数据同步功能。
在一些可能的实施例中,所述源MEC平台,还用于将存储的所述UE的业务数据发送至所述AS中处理;所述AS,还用于接收所述源MEC平台发送的所述UE的业务数据,并处理所述UE的业务数据。
在一些可能的实施例中,所述第一指示信息还用于指示所述AS申请第一资源,所述第一资源为所述AS用于处理所述UE的业务数据的资源(具体可为计算资源和存储资源,例如内存和线程等资源);
所述AS,具体用于根据所述第一指示信息的指示,为所述UE申请所述第一资源,并向所述源MEC平台发送所述第一响应消息;其中,所述第一响应消息还用于指示所述AS已申请所述第一资源。
在一些可能的实施例中,所述系统还包括UE,所述源MEC平台向所述AS发送第一指示信息之前,所述UE,还用于向所述AS发送第一创建请求,所述第一创建请求携带第一通道参数,用于请求创建所述UE和所述AS之间通信时所用的第一通道;所述AS,还用于响应所述第一创建请求,向所述UE发送第一创建响应,用于通知所述第一通道已创建成功。
在一些可能的实施例中,所述源MEC平台向所述AS发送第一指示信息之前,
所述UE,用于向所述源MEC平台发送第二创建消息,所述第二创建消息携带有第二通道参数,用于请求创建所述UE和所述源MEC平台之间通信时所用的第二通道,以通过所述第二通道将所述UE的业务数据发送至所述源MEC平台中处理;
所述源MEC平台,用于在接收所述第二创建消息后,向所述AS发送第二指示信息,所述第二指示信息用于指示不在所述AS中处理所述UE的业务数据,所述第二创建消息用于请求创建所述UE和所述源MEC平台之间通信时所用的第二通道;
所述AS,用于响应所述第二指示信息,向所述源MEC平台发送第二响应消息,所述第二响应消息用于指示所述AS已确定不在处理所述UE的业务数据;
所述源MEC平台,还用于在接收所述第二响应消息后,向所述UE发送第二创建响应,所述第二创建响应用于指示所述第二通道已创建成功。
需要说明的是,所述第一通道优先于所述第二通道创建。
在一些可能的实施例中,所述第二指示信息用于指示所述AS将所述用户状态切换为空闲状态,以不在所述AS中处理所述UE的业务数据;
所述AS,具体用于根据所述第二指示信息的指示,将所述用户状态切换为空闲状态,并向所述源MEC平台发送所述第二响应消息;所述第二响应消息还用于指示所述AS已将所述用户状态切换为空闲状态。
在一些可能的实施例中,所述第二指示信息还用于指示所述AS释放第二资源,所述第二资源为所述AS用于处理所述UE的业务数据的资源;
所述AS,具体用于根据所述第二指示信息的指示,释放所述第二资源,并向所述源MEC平台发送所述第二响应消息;所述第二响应消息还用于指示所述AS已释放所述第二资源。
在一些可能的实施例中,在所述源MEC平台和所述AS之间开始同步所述UE的业务数据后,所述AS,还用于向所述UE发送第三指示信息,所述第三指示信息用于指示将所述UE的业务数据发送至所述AS中处理;所述UE,还用于响应所述第三指示信息,向所述AS发送第三响应消息,所述第三响应消息用于通知所述UE已确定将所述UE的业务数据发送至所述AS中处理。
在一些可能的实施例中,所述第三指示信息用于指示所述UE将第二通道切换为第一通道,以通过所述第一通道将所述UE的业务数据发送至所述AS中处理;其中,所述第一通道为所述UE和所述AS之间通信时所用的通道,所述第二通道为所述UE和所述源MEC平台之间通信时所用的通道,且所述第一通道优先于所述第二通道创建;
所述第三响应消息用于指示所述UE已将所述第二通道切换为第一通道。
在一些可能的实施例中,所述UE,还用于将所述UE的业务数据发送至所述AS中处理;所述AS,还用于接收并处理所述UE的业务数据。
在一些可能的实施例中,在所述源MEC平台和所述AS之间同步完成所述UE的业务数据后,所述AS,还用于向所述源MEC平台发送第四指示信息,所述第四指示信息用于指示等待所述源MEC平台和所述UE之间的通信断连;所述源MEC平台,还用于根据所述第四指示信息的指示,等待所述源MEC平台和所述UE之间的通信断连。
在一些可能的实施例中,所述第四指示信息用于指示所述源MEC平台将所述目标应用中的用户状态切换为等待状态,以等待所述源MEC平台和所述UE之间的通信断连;
所述源MEC平台,具体用于根据所述第四指示信息的指示,将所述目标应用的用户状态切换为等待状态。
在一些可能的实施例中,所述第四指示信息还用于指示所述源MEC平台释放第三资源,所述第三资源为所述源MEC平台用于处理所述UE的业务数据的计算资源和存储资源;
所述源MEC平台,具体用于根据所述第四指示信息的指示,释放所述第三资源。
在一些可能的实施例中,所述源MEC平台,还用于在检测到所述UE离开所述源MEC平台,或者所述源MEC平台中所述目标应用停止处理所述UE的业务数据后,确定所述源MEC平台和所述UE之间的通信已断连。
在一些可能的实施例中,所述源MEC平台,还用于在检测到所述UE离开所述源MEC平台后,释放所述源MEC平台和所述UE之间所占用的通道资源,例如socket资源等。
在一些可能的实施例中,所述系统还包括目标MEC平台,
所述UE,还用于在所述UE从所述源MEC平台切换至所述目标MEC平台,或者所述目标MEC平台中的所述目标应用重新支持处理所述UE的业务数据的情况下,向所述目标MEC平台发送第三创建请求,所述第三创建请求携带第三通道参数,用于请求创建所述UE和所述目标MEC平台之间通信时所用的第三通道,以通过所述第三通道将所述UE的业务数据传输至所述目标MEC平台中处理;所述目标MEC平台部署有所述目标应用;
所述目标MEC平台,用于接收所述第三创建请求,根据所述第三通道参数创建所述第三通道,并向所述UE发送第三创建响应,所述第三创建响应用于指示所述第三通道已创建成功。
在一些可能的实施例中,所述目标MEC平台,还用于向所述AS发送数据同步请求,用于请求将所述AS中存储的所述UE的业务数据同步至所述目标MEC平台中处理;所述AS,还用于接收所述数据同步请求,向所述目标MEC平台发送数据同步响应,所述数据同步响应用于指示允许所述目标MEC平台和所述AS之间同步所述UE的业务数据。
在一些可能的实施例中,所述AS,还用于将存储的所述UE的业务数据发送至所述目标MEC平台中处理;所述目标MEC平台,还用于接收并处理所述UE的业务数据。
在一些可能的实施例中,在所述目标MEC平台和所述AS之间开始同步所述UE的业务数据后,所述目标MEC平台,还用于向所述UE发送第五指示信息,所述第五指示信息用于指示将所述UE的业务数据发送至所述目标MEC平台中处理;所述UE,还用于响应所述第五指示信息,向所述目标MEC平台发送第五响应消息,所述第五响应消息用于通知所述UE已确定将所述UE的业务数据发送至所述目标MEC平台中处理。
在一些可能的实施例中,所述第五指示信息用于指示所述UE将所述第二通道切换为所述第三通道,以通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理;
所述UE,具体用于根据所述第五指示信息的指示,将所述第二通道切换为所述第三通道,并向所述目标MEC平台发送第五响应消息;所述第五响应消息用于指示所述UE已将所述第二通道切换为所述第三通道。
在一些可能的实施例中,在所述目标MEC平台和所述AS之间同步完成所述UE的业务数据后,所述目标MEC平台,还用于向所述AS发送第六指示信息,所述第六指示信息用于指示不在所述AS中处理所述UE的业务数据;所述AS,还用于响应所述第六指示信息,并向所述目标MEC平台发送第六响应消息,所述第六响应消息用于指示所述AS已确定不在处理所述UE的业务数据。
在一些可能的实施例中,所述第六指示信息用于指示所述AS将所述用户状态切换为空闲状态,以不在所述AS中处理所述UE的业务数据;
所述AS,具体用于根据所述第六指示信息的指示,将所述用户状态切换为空闲状态,并向所述目标MEC平台发送所述第六响应消息;所述第六响应消息还用于指示所述AS已将所述用户状态切换为空闲状态。
在一些可能的实施例中,所述第六指示信息还用于指示所述AS释放第四资源,所述第四资源为所述AS用于处理所述UE的业务数据的资源(具体可为计算资源和存储资源);
所述AS,具体用于根据所述第六指示信息的指示,释放所述第四资源,并向所述目标MEC平台发送所述第六响应消息;所述第六响应消息还用于指示所述AS已释放所述第四资源。
第二方面,本申请提供一种业务切换处理方法,应用于源移动边缘计算MEC平台中,所述方法包括:
所述源MEC平台在确定到目标应用将停止处理用户设备UE的业务数据的情况下,向所述AS发送第一指示信息;其中,所述第一指示信息用于指示将在所述AS中处理所述UE的业务数据,所述源MEC平台中部署有所述目标应用,所述目标应用为用于处理所述UE的业务数据的应用;
所述源MEC平台接收所述AS返回的第一响应消息,所述第一响应消息用于通知所述AS已准备好处理所述UE的业务数据。
在第三方面,本申请提供又一种业务切换处理方法,应用于云服务器AS,所述方法包括:
所述AS接收源MEC平台发送的第一指示信息,所述第一指示信息用于指示将在所述AS 中处理用户设备UE的业务数据;
响应所述第一指示信息,向所述源MEC平台发送第一响应消息,所述第一响应消息用于通知所述AS已准备好处理所述UE的业务数据。
第四方面,本申请提供又一种业务切换处理方法,应用于目标MEC平台,所述方法包括:
所述目标MEC平台接收所述UE发送的第三创建请求,所述第三创建请求携带第三通道参数,用于请求创建所述UE和所述目标MEC平台之间通信时所用的第三通道,以通过所述第三通道将所述UE的业务数据传输至所述目标MEC平台中处理;所述目标MEC平台部署有目标应用,所述目标应用为用于处理所述UE的业务数据的应用;
根据所述第三通道参数创建所述第三通道,并向所述UE发送第三创建响应,所述第三创建响应用于通知所述第三通道已创建成功。
第五方面,本申请提供又一种业务切换处理方法,应用于用户设备UE,所述方法包括:
所述UE向目标设备发送创建请求,所述创建请求携带所述UE中预置的通道参数,用于请求创建所述UE和所述目标设备之间通信时所用的通道;
接收所述目标设备返回的创建响应,所述创建响应用于通知所述通道已创建成功。
在一些可能的实施例中,在所述创建请求为第一创建请求的情况下,所述第一创建请求携带第一通道参数,用于请求创建所述UE和云服务器AS之间通信时所用的第一通道,以通过所述第一通道将所述UE的业务数据发送至所述AS中处理;
在所述创建请求为第二创建请求的情况下,第二创建请求携带第二通道参数,用于请求创建所述UE和源MEC平台之间通信时所用的第二通道,以通过所述第二通道将所述UE的业务数据发送至所述源MEC平台中处理;
在所述创建请求为第三创建请求的情况下,所述第三创建请求携带第三通道参数,用于请求创建所述UE和目标MEC平台之间通信时所用的第三通道,以通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述确定到目标应用将停止处理所述UE的业务数据,包括:所述源MEC平台获取到针对所述目标应用的操作指令,或者所述源MEC平台接收到基站发送的切换通知;其中,所述操作指令包括以下中的至少一项:更新指令、卸载指令以及重配置指令。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第一指示信息用于指示所述AS将用户状态切换为激活状态,以等待处理所述UE的业务数据;其中,所述AS中的用户状态用于指示是否在所述AS中处理所述UE的业务数据;
所述AS根据所述第一指示信息的指示,将所述用户状态切换为激活状态,并向所述源MEC平台发送所述第一响应消息;其中,所述第一响应消息还用于指示所述AS已将所述用户状态切换为激活状态。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第一指示信息还用于指示请求启动所述源MEC平台和所述AS之间的数据同步功能,以将所述源MEC平台中存储的所述UE的业务数据同步至所述AS中处理;所述第一响应消息还用于指示允许启动所述源MEC平台和所述AS之间的数据同步功能。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述源MEC平台将存储的所述UE的业务数据发送至所述AS中处理;相应地,所述AS接收所述源MEC平台发送的所述UE的业务数据,并处理所述UE的业务数据。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第一指示信息还用于指示所述AS申请第一资源,所述第一资源为所述AS用于处理所述UE的业务数据的资源;相应地,所述AS根据所述第一指示信息的指示,为所述UE申请所述第一资源,并向所述源MEC平台发送所述第一响应消息;其中,所述第一响应消息还用于指示所述AS已申请所述第一资源。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述源MEC平台向所述AS发送第一指示信息之前,所述方法还包括:所述UE向所述AS发送第一创建请求,所述第一创建请求携带第一通道参数,用于请求创建所述UE和所述AS之间通信时所用的第一通道;相应地,所述AS响应所述第一创建请求,向所述UE发送第一创建响应,用于通知所述第一通道已创建成功。所述UE接收所述AS发送的所述第一创建响应消息。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述源MEC平台向所述AS发送第一指示信息之前,
所述UE向所述源MEC平台发送第二创建消息,所述第二创建消息携带有第二通道参数,用于请求创建所述UE和所述源MEC平台之间通信时所用的第二通道,以通过所述第二通道将所述UE的业务数据发送至所述源MEC平台中处理;
相应地,所述源MEC平台在接收所述第二创建消息后,向所述AS发送第二指示信息,所述第二指示信息用于指示不在所述AS中处理所述UE的业务数据,所述第二创建消息用于请求创建所述UE和所述源MEC平台之间通信时所用的第二通道;
所述AS接收所述第二指示信息,响应所述第二指示信息,向所述源MEC平台发送第二响应消息,所述第二响应消息用于指示所述AS已确定不在处理所述UE的业务数据;
相应地,所述源MEC平台在接收所述第二响应消息后,向所述UE发送第二创建响应,所述第二创建响应用于指示所述第二通道已创建成功。所述UE接收所述源MEC平台发送的所述第二创建响应。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第二指示信息用于指示所述AS将所述用户状态切换为空闲状态,以不在所述AS中处理所述UE的业务数据;所述AS根据所述第二指示信息的指示,将所述用户状态切换为空闲状态,并向所述源MEC平台发送所述第二响应消息;所述第二响应消息还用于指示所述AS已将所述用户状态切换为空闲状态。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第二指示信息还用于指示所述AS释放第二资源,所述第二资源为所述AS用于处理所述UE的业务数据的资源;所述AS根据所述第二指示信息的指示,释放所述第二资源,并向所述源MEC平台发送所述第二响应消息;所述第二响应消息还用于指示所述AS已释放所述第二资源。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,在所述源MEC平台和所述AS之间开始同步所述UE的业务数据后,所述方法还包括:所述AS向所述UE发送第三指示信息,所述第三指示信息用于指示将所述UE的业务数据发送至所述AS中处理;相应地,所述UE响应所述第三指示信息,向所述AS发送第三响应消息,所述第三响应消息用于通知所述UE已确定将所述UE的业务数据发送至所述AS中处理。所述AS接收所述UE发送的所述第三响应消息。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第三指示信息用于指示所述UE将第二通道切换为第一通道,以通过所述第一通道将所述UE的业 务数据发送至所述AS中处理;其中,所述第一通道为所述UE和所述AS之间通信时所用的通道,所述第二通道为所述UE和所述源MEC平台之间通信时所用的通道,且所述第一通道优先于所述第二通道创建;所述第三响应消息用于指示所述UE已将所述第二通道切换为第一通道。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述方法还包括:所述UE将所述UE的业务数据发送至所述AS中处理;相应地,所述AS接收并处理所述UE的业务数据。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,在所述源MEC平台和所述AS之间同步完成所述UE的业务数据后,所述AS向所述源MEC平台发送第四指示信息,所述第四指示信息用于指示等待所述源MEC平台和所述UE之间的通信断连;相应地,所述源MEC平台根据所述第四指示信息的指示,等待所述源MEC平台和所述UE之间的通信断连。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第四指示信息用于指示所述源MEC平台将所述目标应用中的用户状态切换为等待状态,以等待所述源MEC平台和所述UE之间的通信断连;所述源MEC平台根据所述第四指示信息的指示,将所述目标应用的用户状态切换为等待状态。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第四指示信息还用于指示所述源MEC平台释放第三资源,所述第三资源为所述源MEC平台用于处理所述UE的业务数据的计算资源和存储资源;所述源MEC平台根据所述第四指示信息的指示,释放所述第三资源。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述方法还包括:所述源MEC平台在检测到所述UE离开所述源MEC平台,或者所述源MEC平台中所述目标应用停止处理所述UE的业务数据后,确定所述源MEC平台和所述UE之间的通信已断连。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述方法还包括:在所述UE从所述源MEC平台切换至所述目标MEC平台,或者所述目标MEC平台中的所述目标应用重新支持处理所述UE的业务数据的情况下,所述UE向所述目标MEC平台发送第三创建请求,所述第三创建请求携带第三通道参数,用于请求创建所述UE和所述目标MEC平台之间通信时所用的第三通道,以通过所述第三通道将所述UE的业务数据传输至所述目标MEC平台中处理;所述目标MEC平台部署有所述目标应用;
相应地,所述目标MEC平台接收所述第三创建请求,根据所述第三通道参数创建所述第三通道,并向所述UE发送第三创建响应,所述第三创建响应用于指示所述第三通道已创建成功。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述方法还包括:所述目标MEC平台向所述AS发送数据同步请求,用于请求将所述AS中存储的所述UE的业务数据同步至所述目标MEC平台中处理;所述AS接收所述数据同步请求,向所述目标MEC平台发送数据同步响应,所述数据同步响应用于指示允许所述目标MEC平台和所述AS之间同步所述UE的业务数据。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述方法还包括:所述AS将存储的所述UE的业务数据发送至所述目标MEC平台中处理;相应地,所述目标MEC平台接收并处理所述UE的业务数据。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,在所述目 标MEC平台和所述AS之间开始同步所述UE的业务数据后,所述方法还包括:
所述目标MEC平台向所述UE发送第五指示信息,所述第五指示信息用于指示将所述UE的业务数据发送至所述目标MEC平台中处理;相应地,所述UE响应所述第五指示信息,向所述目标MEC平台发送第五响应消息,所述第五响应消息用于通知所述UE已确定将所述UE的业务数据发送至所述目标MEC平台中处理。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第五指示信息用于指示所述UE将所述第二通道切换为所述第三通道,以通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理;所述UE根据所述第五指示信息的指示,将所述第二通道切换为所述第三通道,并向所述目标MEC平台发送第五响应消息;所述第五响应消息用于指示所述UE已将所述第二通道切换为所述第三通道。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,在所述目标MEC平台和所述AS之间同步完成所述UE的业务数据后,所述方法还包括:
所述目标MEC平台向所述AS发送第六指示信息,所述第六指示信息用于指示不在所述AS中处理所述UE的业务数据;相应地,所述AS响应所述第六指示信息,并向所述目标MEC平台发送第六响应消息,所述第六响应消息用于指示所述AS已确定不在处理所述UE的业务数据。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第六指示信息用于指示所述AS将所述用户状态切换为空闲状态,以不在所述AS中处理所述UE的业务数据;所述AS根据所述第六指示信息的指示,将所述用户状态切换为空闲状态,并向所述目标MEC平台发送所述第六响应消息;所述第六响应消息还用于指示所述AS已将所述用户状态切换为空闲状态。
结合前述第二方面至第五方面中任一方面或多方面,在一些可能的实施例中,所述第六指示信息还用于指示所述AS释放第四资源,所述第四资源为所述AS用于处理所述UE的业务数据的资源;所述AS根据所述第六指示信息的指示,释放所述第四资源,并向所述目标MEC平台发送所述第六响应消息;所述第六响应消息还用于指示所述AS已释放所述第四资源。
第六方面,本发明实施例公开提供了一种源MEC平台,包括用于执行上述第二方面的方法的功能单元。
第七方面,本发明实施例公开提供了一种云服务器AS,包括用于执行上述第三方面的方法的功能单元。
第八方面,本发明实施例公开提供了一种目标MEC平台,包括用于执行上述第四方面的方法的功能单元。
第九方面,本发明实施例公开提供了一种用户设备UE,包括用于执行上述第五方面的方法的功能单元。
第十方面,本发明实施例提供了又一种网络设备,包括存储器、通信接口及与所述存储器和通信接口耦合的处理器;所述存储器用于存储指令,所述处理器用于执行所述指令,所述通信接口用于在所述处理器的控制下与其他设备(例如用户设备、云服务器AS、部署源MEC平台或目标MEC平台的网络设备)进行通信;其中,所述处理器执行所述指令时执行上述第二方面至第四方面中任一方面所描述的方法。
第十一方面,本发明实施例提供了又一种用户设备,包括存储器、通信接口及与所述存储器和通信接口耦合的处理器;所述存储器用于存储指令,所述处理器用于执行所述指令, 所述通信接口用于在所述处理器的控制下与其他设备(具体可为云服务器,部署目标MEC平台或者源MEC平台的网络设备等)进行通信;其中,所述处理器执行所述指令时执行上述第五方面描述的方法。
第十二方面,提供了一种计算机可读存储介质,所述计算机可读存储介质存储了用于业务切换处理的程序代码。所述程序代码包括用于执行上述第二方面至第五方面中任一方面所描述的方法的指令。
第十三方面,提供了一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第二方面至第五方面中任一方面所描述的方法。
通过实施本发明实施例,能够解决现有技术中在UE切换离开源MEC平台后,导致UE和源MEC平台之间出现业务中断等问题,进而提升了业务处理的可靠性和高效性。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
图1是现有技术提供的一种业务切换处理方法的流程示意图。
图2是本发明实施例提供的一种网络框架示意图。
图3是本发明实施例提供的一种业务切换处理方法的流程示意图。
图4是本发明实施例提供的又一种业务切换处理方法的流程示意图。
图5是本发明实施例提供的又一种业务切换处理方法的流程示意图。
图6A是本发明实施例提供的一种第一设备的结构示意图。
图6B是本发明实施例提供的另一种第一设备的结构示意图。
具体实施方式
下面将结合本发明的附图,对本发明实施例中的技术方案进行详细描述。
申请人在提出本申请的过程中发现:为降低UE和云服务器AS之间的传输时延,推出MEC平台的概念。具体的,在MEC平台中部署目标应用,用于处理所述UE的业务数据。其中,UE不感知MEC平台的存在。当网络中部署有包括所述目标应用的MEC平台后,UE向网络中发送的业务处理请求将被路由至所述MEC平台上的目标应用中处理。通常为节省成本,一个或多个基站eNB可共用一个MEC平台。
相应地,在UE切换基站的过程中,也会出现MEC平台的切换,这将出现以下可能情况:UE切换到没有MEC平台部署的基站,或者切换到有MEC平台部署但该平台不存在目标应用所对应的基站,这时将导致UE和源MEC平台之间的业务中断。
此外,现有针对MEC平台间的切换流程为:在基站eNB切换流程中叠加针对MEC平台的业务切换处理流程。具体的,如图1是现有技术中提供的一种业务切换处理方法的流程示意图。如图1所述的方法包括如下实施步骤:
S1,UE向源基站eNB上报信号测量报告。相应地,所述源基站接收所述UE上报的信号测量报告。
S2,所述源基站eNB收到UE上报的信号测量报告后,可根据信号测量报告中的参数(如小区信号质量等)确定所述UE需要切换至目标基站eNB。
S3,进一步地,所述源基站可获取待切换的所述UE的上下文信息,并向所述源基站对应部署的源MEC平台发送切换通知,所述切换通知用于通知所述UE将切换至所述目标基站eNB。可选的,所述切换通知可携带有所述目标基站的标识、所述UE的标识以及所述源基站的标识等信息。相应地,所述源MEC平台接收所述切换通知。
S4,所述源MEC平台根据所述目标基站的标识查找到所述目标基站对应部署的目标MEC平台。具体的,所述源MEC平台根据所述目标基站的标识,从本地配置的映射表中查找出所述目标基站对应的目标MEC平台。其中,所述映射表为用户侧或源MEC平台侧自定义配置的,所述映射表可包括有多个基站各自对应的MEC平台,所述多个基站可包括但不限于所述源基站的相邻小区基站等。所述多个基站至少包括有所述目标基站,即所述映射表中至少包括有所述目标基站和所述目标MEC平台之间的映射关系。
S5,进一步地,所述源MEC平台根据所述UE的标识,查找所述源MEC平台中存储的所述UE的业务数据(也可称应用数据)。
S6,进一步地,所述源MEC平台将所述UE的业务数据发送给所述目标MEC平台;相应地,所述目标MEC平台接收所述UE的业务数据。
S7,在所述目标MEC平台同步接收完所述UE的业务数据后,向所述源MEC平台发送第一响应消息,用于指示所述UE的业务数据已同步完成。相应地,所述源MEC平台接收所述第一响应消息。
S8,在所述源MEC平台接收所述第一响应消息后,向所述源基站发送第二响应消息,用于指示允许所述UE进行所述源基站或源MEC平台的切换。相应地,所述源基站接收所述第二响应消息。
S9,在所述源基站接收所述第二响应消息后,向所述UE发送切换指令,用于指示允许所述UE从所述源基站切换至所述目标基站,即是允许所述UE从所述源MEC平台切换至所述目标MEC平台。
S10、所述UE接收所述切换指令后,从所述源基站切换至所述目标基站。
图1示出现有针对MEC平台的业务切换处理流程,其中存在以下几个问题:
第一、在UE移动过程中,会切换到没有部署目标MEC平台的基站中,或者切换到部署有目标MEC平台的基站中,但该目标MEC平台中没有目标应用,不能处理所述UE的业务数据。这时将导致UE和源MEC平台之间的业务中断,无法实现业务的无损处理,降低了业务处理的可靠性。
第二、现有针对MEC平台的业务切换处理流程中,源MEC平台需存储有映射表,该映射表中包括有相邻基站对应部署的MEC平台等信息,以便于在UE切换过程中确定所述目标基站对应的目标MEC平台。可理解的,映射表中的信息通常是由用户手工配置的,取决于用户主动行为,且配置操作相当复杂,维护成本较高,不易推广。
第三、由于目标MEC平台没有所述UE的业务数据(或应用数据),在UE切换过程中所述目标MEC平台需和所述源MEC平台之间完成针对所述UE的业务数据的同步。当所述UE的业务数据(例如视频数据)比较多时,会增加所述UE针对所述源基站或源MEC平台的切换时长,UE无法及时接入目标基站或目标MEC平台中,此时由于源基站的信号质量降低,还将导致出现通信中断等问题。
为解决上述问题,本申请提出一种业务切换处理方法以及该方法所适用的网络框架。下 面首先介绍本申请涉及的网络框架。如图2示出一种可能的网络框架示意图,该网络框架示意图包括用户设备UE 100、源接入网设备102、源MEC平台104、目标接入网设备106、目标MEC平台108以及云服务器AS 110。其中,该网络框架示意图中的各设备或平台的数量,本申请并不做限定,图示分别以一个为例。
所述UE 100,用于通过接入网设备(图示具体可为源接入网设备102或目标接入网设备106)接入到网络中,进而与MEC平台或云服务器AS通信。当所述MEC平台和所述AS中均安装/部署有目标应用时,所述UE可通过接入网设备(如基站)与所述目标应用建立通信连接,进而进行相互间的数据交互,以借助所述目标应用来处理所述UE的业务数据。其中,所述目标应用为用于处理所述UE的业务数据的应用程序,其可安装在MEC平台(图示可为源MEC平台104和/或目标MEC平台108)、云服务器AS 110等设备中。其中,所述UE并不感知所述目标应用是部署在所述云服务器AS还是MEC平台中的。
可选的,所述UE可以是手机、平板电脑(table personal computer)、个人数字助理(personal digital assistant,PDA)、移动上网装置(mobile internet device,MID)或可穿戴式设备(wearable device)等终端侧设备,本申请不限定所述UE的具体形式或类型。
所述接入网设备(具体可为源接入网设备102或目标接入网设备106),是将UE接入到网络的网络设备。其可用于根据UE上报的信号测量报告,确定所述UE是否需要切换接入网设备。如果需要,还可向所述接入网设备对应部署的MEC平台发送切换通知,用于通知所述UE将切换接入网设备。可选的,一个或多个接入网设备可对应部署一个或多个MEC平台,也可不部署MEC平台。
可选的,图示中的所述源接入网络设备和所述目标接入网设备可为相同类型或者不同类型的接入网设备,所述接入网设备包括但不限于陆地无线接入网中的演进型NodeB(Evolved NodeB,eNB)、家庭演进型NodeB(Home Evolved NodeB,HeNB)、无线接入网中的无线网络控制器(radio network controller,RNC)以及无线接入网中的基站控制器(base station controller,BSC)等等。本申请下文将以所述接入网设备为基站eNB为例,进行相关内容的阐述。
所述MEC平台(具体可为源MEC平台104或目标MEC平台108),用于靠近所述UE端部署,该MEC平台中部署有目标应用,以用于处理所述UE的业务数据。当UE向网络中发送业务处理请求时,MEC平台可根据预设的路由规则将所述业务处理请求路由至所述MEC平台中的目标应用中进行处理。
所述云服务器AS 110,为部署在云端网络中的应用服务器,同样可用于处理所述UE的业务数据。在实际应用中,在所述AS中部署所述目标应用,进而利用该目标应用来处理所述UE的业务数据。通常,所述UE中预先配置有所述AS的对接信息,例如所述AS的IP地址、通信端口等等。在UE移动过程中会涉及接入网设备(如基站eNB)或者该接入网设备对应的MEC平台的切换,但云服务器AS的地址不发生变化,不影响应用层上所述UE和所述AS间的数据交互。
基于图2所示的网络框架示意图,下面介绍本申请涉及的业务切换处理方法的相关实施例。参见图3,是本发明实施例提供的一种业务切换处理方法的流程示意图。如图3所述的方法可包括如下实施步骤:
S101、源MEC平台在确定到目标应用将停止处理用户设备UE的业务数据的情况下,向云 服务器AS发送第一指示信息,所述第一指示信息用于指示所述AS将等待处理所述UE的业务数据。相应地,所述AS接收所述第一指示信息。其中,所述源MEC平台中部署有所述目标应用,用于处理所述UE的业务数据。
所述源MEC平台确定目标应用将停止处理UE的业务数据的实施方式存在以下两种:
第一种,所述源MEC平台接收到源基站eNB发送的切换通知后,可确定自身部署的目标应用即将停止处理UE的业务数据。其中,所述切换通知用于通知UE将从所述源基站切换至目标基站。
具体的,UE可实时或周期性地向当前所述UE驻留的源基站eNB上报所述UE的信号测量报告。所述源基站可根据所述UE上报的信号测量报告,确定所述UE将从所述源基站eNB切换至目标基站eNB。例如,根据信号测量报告中各小区基站的信号质量,确定所述UE是否需要从所述源基站切换至目标基站处。进一步地,所述源基站还可向所述源MEC平台发送切换通知,用于通知所述UE将从所述源eNB切换至目标eNB。可选的,所述切换通知可携带有所述UE的标识、所述源eNB的标识以及所述目标eNB的标识等信息,本申请不做限定。
第二种,所述源MEC平台在接收到针对自身部署的目标应用的操作指令时,可确定所述目标应用即将停止处理UE的业务数据,所述操作指令包括以下中的任一项或多项的组合:更新指令、卸载/删除指令以及重配置指令、或者其他用于对所述目标应用进行更改操作的指令等。所述重配置指令用于指示对所述目标应用进行重新配置,例如对所述目标应用中的参数或通信端口进行重配置等。
以所述操作指令为更新指令为例,当所述源MEC平台检测到用户针对所述目标应用进行升级、打补丁等操作处理,即检测到针对所述目标应用的更新指令。由于目标应用升级或打补丁过程中无法提供业务服务,此时所述源MEC平台可确定到所述目标应用将停止处理UE的业务数据。
S102、所述云服务器AS响应所述第一指示信息,并向所述源MEC平台发送第一响应消息。所述第一响应消息用于通知/指示所述AS已准备好等待处理所述UE的业务数据。
在可选实施例中,所述第一指示信息具体用于指示所述AS将用户状态切换为激活active状态,以等待处理所述UE的业务数据。具体的,所述AS中同样也部署有所述目标应用,用于处理所述UE的业务数据。所述目标应用对应有几个用户状态,每个用户状态所表征/指示的含义有所不同。例如,这里的激活状态用于指示所述目标应用即将处理所述UE的业务数据。下文将在涉及到各个用户状态时进行详细阐述。
相应地,所述AS可根据所述第一指示信息的指示,将所述用户状态(具体是所述AS中目标应用对应的用户状态)切换为激活状态。进一步地,向所述源MEC平台发送所述第一响应消息。此时所述第一响应消息还用于通知所述AS已将所述用户状态切换为激活状态,以等待处理所述UE的业务数据。
在可选实施例中,所述第一指示信息还用于指示请求启动所述源MEC平台和所述AS之间的数据同步功能,即启动业务数据同步,以将所述源MEC平台中存储的所述UE的业务数据同步至所述AS中处理。此时所述第一指示信息可视为同步请求消息。
相应地,所述AS接收到所述第一指示信息后,可响应该第一指示信息,向所述源MEC平台发送所述第一响应消息。此时所述第一响应消息还用于通知允许所述源MEC平台和所述AS之间启动数据同步功能。
进一步可选的,所述源MEC平台和所述AS之间可进行数据同步。例如,所述源MEC平台 可将自身存储的所述UE的业务数据发送至所述AS中处理。相应地,所述AS接收所述源MEC平台发送的所述UE的业务数据,以进行对应的处理,以所述业务数据为视频数据为例,所述AS接收所述视频数据后可缓存所述视频数据等等。
在可选实施例中,所述第一指示信息还用于指示所述AS申请第一资源,以用于所述AS处理所述UE的业务数据。这里的第一资源主要用于处理所述UE的业务数据,其可为计算资源、存储资源以及其他与所述UE相关的资源等,例如内存和线程等资源。
相应地,所述AS可根据所述第一指示信息的指示,为所述UE申请所述第一资源,以用于处理所述UE的业务数据。进一步向所述源MEC平台发送所述第一响应消息。此时所述第一响应消息还用于通知所述AS已申请用于处理UE的业务数据的所述第一资源。
下面阐述本申请涉及的一些可选实施例。
在可选实施例中,步骤S101之前,还可包括如下实施步骤:
步骤S1001、所述UE向所述AS发送第一创建请求,所述第一创建请求携带第一通道参数,用于请求创建所述UE和所述AS之间通信时所需的第一通道。
步骤S1002、所述AS接收所述第一创建请求后,根据所述第二通道参数创建所述第一通道,并向所述UE发送第一创建响应。所述第一创建响应用于通知所述第一通道已创建成功。
其中,所述第一通道参数为用于创建所述第一通道所需的参数,其可为所述目标应用部署在所述AS中的对接信息,所述对接信息包括但不限于所述AS(或所述AS中目标应用)的网络协议(internet protocol,IP)地址、逻辑端口、用户名、密码通信协议以及通信密钥等信息。
所述第一通道为所述UE和所述AS之间通信时所使用的通道,通过该通道可实现所述UE和所述AS之间的数据交互。例如,所述UE通过所述第一通道将所述UE的业务数据发送给所述AS处理。
可选的,步骤S101之前,还可包括如下实施步骤:
步骤S1003、所述用户设备UE向所述源MEC平台发送第二创建请求,所述第二创建请求携带第二通道参数,用于请求在所述UE和所述源MEC平台之间创建通信时所需的第二通道。
具体的,所述第二通道参数为用于创建所述第二通道所需的参数,其可为所述目标应用部署在所述源MEC平台中的对接信息,关于所述对接信息可参加前述实施例中的相关阐述,这里不再赘述。
所述第二通道为所述UE和所述源MEC平台之间通信时所使用的通道,通过该通道可实现它们之间的数据交互。例如,所述UE通过所述第二通道可将所述UE的业务数据发送给所述源MEC平台处理。
步骤S1004、所述源MEC平台在接收所述第一创建请求后,根据所述第一通道参数创建所述第一通道,并向所述AS发送第二指示信息。其中,所述第二指示信息用于指示不在所述AS中处理所述UE的业务数据。相应地,所述AS接收所述第二指示信息。
步骤S1005、所述AS响应所述第二指示信息,向所述源MEC平台发送第二响应消息,所述第二响应消息用于通知所述AS已确定/获知不在处理所述UE的业务数据。
步骤S1006、所述源MEC平台在接收所述第二响应消息后,向所述UE发送第一创建响应,所述第一创建响应用于通知所述第二通道已创建成功。
在可选实施例中,所述第二指示信息具体可用于指示所述AS将所述用户状态切换为空闲idle状态,以通知后续不在所述AS中处理所述UE的业务数据。相应地,所述AS响应所述 第二指示信息,根据所述第二指示信息的指示将所述用户状态切换为空闲状态,并向所述源MEC发送所述第二响应消息。此时所述第二响应消息还用于通知所述AS已将所述用户状态切花为空闲状态。
在可选实施例中,所述第二指示信息还用于指示所述AS释放第二资源,保留静态资源,以保留/维持所述UE和所述AS之间的通信,支持它们之间传输握手消息,即请求和响应消息。其中,所述第二资源为所述AS中用于处理所述UE的业务数据的资源,其可为计算资源和存储资源等。所述静态资源可以是指UE的账户信息、权限信息以及其他不会实时更改的信息资源。相应地,所述AS响应所述第二指示信息,根据所述第二指示信息的指示释放所述第二资源,并向所述源MEC平台发送所述第二响应消息。此时所述第二响应消息还用于指示所述AS已释放所述第二资源。
可选的,所述UE还可向所述目标eNB对应部署的目标MEC平台发送第三创建请求,用于请求在所述UE和所述目标MEC平台之间创建通信时所需的第三通道,具体将在下文进行详细阐述。
需要说明的是,上述第一创建请求至第三创建请求均为所述UE向目标设备发送的通道创建请求,以请求对应创建所述UE和所述目标设备之间通信时所用的通道,通过该通道将所述UE的业务数据发送至所述目标设备中处理。所述目标设备为AS、源MEC平台以及目标MEC平台中的任一个或多个。
在可选实施例中,步骤S102之后,所述方法还可包括如下实施步骤:
步骤S103、所述AS向所述UE发送第三指示信息,所述第三指示信息用于指示所述UE将所述UE的业务数据发送至所述AS中处理。相应地,所述UE接收所述第三指示信息。
步骤S104、所述UE响应所述第三指示信息,向所述AS发送第三响应消息,所述第三响应消息用于指示所述UE已确定/获知将所述UE的业务数据发送至所述AS中处理。
具体的,在所述源MEC平台和所述AS之间开始同步所述UE的业务数据后,或者所述源MEC平台和所述AS之间数据同步稳定后,向所述UE发送第三指示信息。这里的数据同步稳定可以是指所述源MEC平台向所述AS发送数据的速率达到预设速率,或处于预设速率范围内。其中,所述第三指示信息可具体用于指示所述UE将原来的所述第二通道切换为第一通道,以便后续通过所述第一通道将自身的业务数据发送至所述AS中处理。
相应地,所述UE接收所述第三指示信息后,根据所述第三指示信息的指示将所述第二通道切换为第一通道,并向所述AS发送所述第三响应消息。此时所述第三响应消息具体用于通知所述UE已将所述第二通道切换为第一通道,后续通过该第一通道将自身的业务数据发送至所述AS中处理。
可选的,在所述UE切换第一通道后,所述UE和所述AS可通过所述第一通道实现数据交互。例如,所述UE通过所述第一通道将所述UE的业务数据发送至所述AS中处理;相应地,所述AS接收并处理所述UE的业务数据,进一步地还可通过所述第一通道将处理结果反馈给所述UE等。
在所述源MEC平台和所述AS之间同步完成所述UE的业务数据后,所述方法还可包括:
步骤S105、所述AS向所述源MEC平台发送第四指示信息,所述第四指示信息用于指示等待所述源MEC平台和所述UE之间的通信断连。相应地,所述源MEC平台接收所述第四指示信息。
步骤S106、所述源MEC平台响应所述第四指示信息,等待和所述UE之间的通信断连。
具体的,在所述源MEC平台将存储的所述UE的业务数据全部发送给所述AS后,即所述AS同步接收完所述UE的业务数据之后,所述AS可向所述源MEC平台发送第四指示信息。所述第四指示信息用于指示所述源MEC平台停止同步所述UE的业务数据,即所述UE的业务数据已同步完成,将所述目标应用的用户状态切换为等待dying状态,以等待所述源MEC平台和所述UE之间的通信断连。此时所述源MEC平台还保持和所述UE之间的通信,即保留所述源MEC平台和所述UE通信时所使用的第二通道,可支持传输简单的握手消息,等待它们断连后再释放所述第二通道所占用的通道资源。
相应地,所述源MEC平台接收所述第四指示信息后,根据所述第四指示信息的指示将所述用户状态切换为等待状态,以等待所述源MEC平台和所述UE通信断连。
在可选实施例中,所述第四指示信息还用于指示所述源MEC平台释放第三资源,保留所述源MEC平台和所述UE通信的第二通道的通道资源,等待断连后再释放。其中,所述第三资源为所述源MEC平台用于处理所述UE的业务数据的资源,其可为计算资源和存储资源等。相应地,所述源MEC平台接收所述第四指示信息后,根据所述第四指示信息的指示释放所述第三资源。
在可选实施例中,当所述源MEC平台在检测到所述UE切换离开自身平台后,或者所述源MEC平台中的所述目标应用停止处理所述UE的业务数据后,可确定到所述源MEC平台和所述UE之间已断开通信连接,即通信已断连。
具体的,由于之前所述源MEC平台和所述UE之间还保留通信的第二通道,所述UE和所述源MEC平台可周期性地交互握手消息,表示它们间还存在通道。相应地,当所述源MEC平台在预设时长内还未接收到所述UE发送的握手消息后,可确定所述UE已切换离开所述源MEC平台,它们之间的通信已断连。
或者,当所述MEC平台中的目标应用正在进行升级、打补丁等更新操作,或者所述目标应用被删除/卸载等,此时无法提供业务服务,即停止处理所述UE的业务数据,也可确定到所述源MEC平台和所述UE通信已断连。
进一步可选的,当所述源MEC平台检测/确定到所述UE切换离开所述源MEC平台后,可释放所述源MEC平台和所述UE之间通信时所占用的通道资源,即所述第二通道占用额通道资源。这里的通道资源可以是指创建所述第二通道时所占用的资源,例如socket连接资源等等。
在可选实施例中,所述方法还可包括如下实施步骤:
步骤S107、所述UE向所述目标MEC平台发送第三创建请求,所述第三创建请求携带第三通道参数,用于请求创建所述UE和所述目标MEC平台之间通信时所用的第三通道。相应地,所述目标MEC平台接收所述第三创建请求。
步骤S108、所述目标MEC平台接收所述第三创建请求后,根据所述第三通道参数创建所述第三通道,并向所述UE发送第三创建响应,用于通知所述第三通道已创建成功。
具体的,当所述UE从所述源MEC平台切换至所述目标MEC平台后,或者之前所述目标MEC平台中目标应用停止处理所述UE的业务数据,现在重新处理所述UE的业务数据后,所述目标MEC平台部署有所述目标应用,用于处理所述UE的业务数据。此时所述UE可实时或周期性地尝试和所述目标eNB对应部署的目标MEC平台通信,创建第三通道,以便后续通过所述第三通道将所述UE的业务数据传输至所述目标MEC平台中处理。
其中,所述第三通道参数为用于创建所述第三通道所需的参数,其具体可为所述目标应 用在所述目标MEC平台中的对接信息,关于所述对接信息可参见前述实施例中的相关介绍,这里不再赘述。所述第三通道为所述UE和所述目标MEC平台之间通信时所用的通道,通过该通道可实现UE和目标MEC平台之间的数据交互。
步骤S109、所述目标MEC平台向所述AS发送数据同步请求,用于请求将所述AS中存储的所述UE的业务数据同步至所述目标MEC平台中。相应地,所述AS接收所述数据同步请求。
步骤S110、所述AS接收所述数据同步请求后,向所述目标MEC平台发送数据同步响应。所述数据同步响应用于通知允许所述AS和所述目标MEC平台之间同步数据。
具体的,在所述目标MEC平台和所述UE之间创建好第三通道后,所述目标MEC平台可向所述AS发送数据同步请求,以请求所述AS将存储的所述UE的业务数据同步至所述目标MEC平台中处理。
进一步可选的,所述AS发送所述数据同步响应后,还可将所述AS中存储的所述UE的业务数据同步发送给所述目标MEC平台进行处理。相应地,所述目标MEC平台接收并处理所述UE的业务数据。
在可选实施例中,所述方法还可包括如下实施步骤:
步骤S111、所述目标MEC平台向所述UE发送第五指示信息,所述第五指示信息用于指示所述UE将所述UE的业务数据发送至所述目标MEC平台中处理。相应地,所述UE接收所述第五指示信息。
步骤S112、所述UE响应所述第五指示信息,向所述目标MEC平台发送第五响应消息,所述第五响应消息用于通知所述UE已确定/获知后续将所述UE的业务数据发送至所述目标MEC平台中处理。
具体的,在所述目标MEC平台和所述AS之间开始同步所述UE的数据后,或者所述目标MEC平台和所述AS之间数据同步稳定后,所述目标MEC平台可向所述UE发送第五指示信息。这里的数据同步稳定是指所述AS向所述目标MEC平台发送数据的速率达到预设速率,或者处于预设速率范围。其中,所述第五指示信息具体用于指示所述UE将原来通信的所述第一通道切换为所述第三通道,以便后续通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理。
相应地,所述UE接收所述第五指示信息后,根据所述第五指示信息的指示将所述第一通道切换为第三通道,并向所述目标MEC平台发送所述第五响应消息。此时所述第五响应消息具体用于通知所述UE已将所述第一通道切换为所述第三通道,后续通过该第三通道将自身的业务数据发送至所述目标MEC平台中处理。
可选的,在所述UE切换所述第三通道后,所述UE和所述目标MEC平台可通过所述第三通道实现数据交互。例如,所述UE通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理;相应地,所述目标MEC平台接收并处理所述UE的业务数据,进一步地还可通过所述第三通道将处理结果反馈给所述UE等。
在可选实施例中,在所述目标MEC平台和所述AS之间同步完成所述UE的业务数据后,所述方法还可包括:
步骤S113、所述目标MEC平台向所述AS发送第六指示信息,所述第六指示信息用于指示不在所述AS中处理所述UE的业务数据。相应地,所述AS接收所述第六指示信息。
步骤S114、所述AS响应所述第六指示信息,向所述目标MEC平台发送第六响应消息,所述第六响应消息用于通知所述AS已确定/获知不在处理所述UE的业务数据。
具体的,在所述目标MEC平台完成和所述AS之间针对所述UE的业务数据的同步后,可向所述AS发送第六指示信息。所述第六指示信息用于指示所述AS通知向所述目标MEC平台同步所述UE的业务数据,即所述UE的业务数据已同步完成,可将所述用户状态切换为空闲idle状态,以指示不在处理所述UE的数据。
相应地,所述AS接收所述第六指示信息后,根据所述第六指示信息的指示将所述用户状态切换为空闲状态,以指示后续不在所述AS中处理所述UE的业务数据。进一步地向所述目标MEC平台发送所述第六响应消息,此时所述第六响应消息用于指示所述AS已将所述用户状态切换为空闲状态。
在可选实施例中,所述第六指示信息还用于指示所述AS释放第四资源,保留所述AS和所述UE通信时的通道资源,即第一通道的通道资源,以便后续所述目标MEC平台中目标应用停止处理所述UE的业务数据后再次启用第一通道,利用所述AS处理所述UE的业务数据。其中,所述第四资源为所述AS用于处理所述UE的业务数据的资源,其可为计算资源和存储资源等。相应地,所述AS向所述目标MEC平台发送所述第六响应消息。此时所述第六响应消息还用于指示所述AS已释放所述第四资源。
在可选实施例中,上述第一资源至第四资源均可包括但不限于计算资源、存储资源或其他和所述UE相关的资源,例如内存和进程资源等等。
通过实施本发明实施例,能够优先考虑利用UE和MEC平台之间创建的通道,将所述UE的业务数据发送至MEC平台中处理;当所述MEC平台停止处理所述UE的业务数据后,再利用UE和AS之间创建的通道,将所述UE的业务数据发送至所述AS中处理。这样能够解决现有技术中在UE切换离开源MEC平台后,导致UE和源MEC平台之间出现业务中断等问题,进而提升了业务处理的可靠性和高效性。
基于前述实施例,下面介绍本申请具体涉及的两种业务切花处理方法的相关实施例。请参见图4是本发明实施例提供的又一种业务切换处理方法的流程示意图。如图4所示的方法包括如下实施步骤:
步骤S201、用户设备UE预先配置通道参数,所述通道参数用于创建所述UE和目标设备(如云服务器AS,或部署MEC平台的网络设备等)通信时所用的通道。
其中,所述通道参数包括第一通道参数和第二通道参数,所述第一通道参数用于创建所述UE和云服务器AS通信时所用的第一通道,所述第二通道参数用于创建所述UE和源MEC平台通信时所用的第二通道。可选的,所述通道参数还可包括第三通道参数,用于创建所述UE和目标MEC平台通信时所用的第三通道。
所述目标设备(这里即为AS、源MEC平台或者目标MEC平台)中可部署/安装有目标应用,以用于处理所述UE的业务数据。相应地,所述UE通过相应地通道(具体可第一通道至第三通道中的任一个)可将所述UE的业务数据传输至所述目标设备中处理。
相应地,所述第一通道参数至所述第三通道参数可为相同的或者不同的通道参数。所述通道参数可为创建通道时所需的对接信息,也可理解为目标应用的对接信息;其可包括但不限于网络协议IP地址、通信使用的逻辑端口、用户名以及密码等。
步骤S202、所述UE向所述AS发送第一创建请求,所述第一创建请求携带第一通道参数,用于请求创建所述UE和所述AS通信时所用的第一通道。
步骤S203、所述AS在接收所述第一创建请求后,向所述UE发送第一创建响应,用于通 知所述第一通道已创建成功。
具体的,所述AS接收所述第一创建请求后,根据所述第一通道参数创建所述UE和所述AS相互通信时所用的第一通道,然后向所述UE反馈所述第一创建响应。
步骤S204、所述UE向源MEC平台发送第二创建请求,所述第二创建请求携带所述第二通道参数,用于请求创建所述UE和所述源MEC平台通信时所用的第二通道。
步骤S205、所述源MEC平台接收所述第二创建请求后,向云服务器AS发送第二指示信息,用于指示所述AS将用户状态切换为空闲状态,以指示/通知后续不在所述AS中处理所述UE的业务数据。
具体的,所述源MEC平台接收所述第二创建请求后,可根据所述第二通道参数创建所述UE和所述源MEC平台相互通信所用的第二通道,并向所述AS发送所述第二指示信息。
步骤S206、在所述AS接收所述第二指示信息后,可释放所述UE相关的计算资源和存储资源,保留所述第一通道(即保留所述第一通道所占用的通道资源)。这里的静态资源是指用户账号、密码等不随时更改的资源,同时还可保留所述第一通道占用的通道资源,支持所述UE和所述源MEC平台之间传输握手消息,即传输简单的请求和响应(或答应)消息。
步骤S207、所述AS向所述源MEC平台发送第二响应消息,用于指示所述AS已将所述用户状态切换为空闲状态。
步骤S208、在所述源MEC平台接收所述第二响应消息后,向所述UE发送第二创建响应,用于指示所述第二通道已创建成功。
步骤S209、在所述第二通道创建成功后,业务初始化成功。所述UE和所述源MEC平台可通过所述第二通道进行数据的交互。例如,所述UE通过所述第二通道将所述UE的业务数据发送给所述源MEC平台处理,所述源MEC平台可将处理结果反馈给所述UE等。
步骤S210、所述源MEC平台接收源基站eNB发送的切换通知,所述切换通知用于通知所述UE将从所述源基站切换到目标基站。
步骤S211、在所述源MEC平台依据所述切换通知确定到需进行所述源MEC平台的切换后,向所述AS发送第一指示信息,用于指示启动所述UE和所述AS之间的数据同步功能,并指示所述AS将用户状态切换为激活状态,以通知后续再所述AS中处理所述UE的业务数据。
具体的,所述源MEC平台在接收到所述切换通知后,可进一步确定所述目标基站eNB对应部署的目标MEC平台是否和所述源MEC平台相同,如果相同,则结束流程。如果不同,则继续后续流程,向所述AS发送第一指示信息。
步骤S212、所述AS在接收所述第一指示信息后,响应所述第一指示信息,启动所述源MEC平台和所述AS之间的数据同步功能,将所述用户状态切换为激活状态。可选的,还可为所述UE申请相关的计算资源和存储资源,例如内存和线程资源等,以便后续利用申请的资源处理所述UE的业务数据。
步骤S213、所述AS向所述源MEC平台发送第一响应消息,用于通知已启动所述AS和所述源MEC平台之间的数据同步功能。可选的,还可用于通知所述AS已将所述用户状态切换为激活状态,以等待处理所述UE的业务数据。可选的,还可用于通知已为所述UE申请了相关的计算资源和存储资源。
步骤S214、在所述源MEC平台和所述AS之间已启动数据同步功能后,可实现所述源MEC平台和所述AS之间的数据同步。例如,所述源MEC平台可将其内存储的所述UE的业务数据同步发送给所述AS,以在所述AS中处理所述UE的业务数据。
步骤S215、所述AS向所述UE发送第三指示信息,用于指示所述UE将原来通信时的第二通道切换为第一通道,以便后续通过所述第一通道将所述UE的业务数据发送至所述AS中处理。
步骤S216、所述UE在接收所述第三指示信息后,响应所述第三指示信息,向所述AS发送第三响应消息,用于指示所述UE已将所述第二通道切换为第一通道。
具体的,在所述源MEC平台和所述AS之间开始同步数据(即所述UE的业务数据)后,或者它们之间数据同步稳定之后,所述AS向所述UE发送第三指示信息,用于指示所述UE后续通过第一通道将所述UE的业务数据发送至所述AS中处理。相应地,所述UE接收所述第三指示信息,根据所述第三指示信息的指示将所述第二通道切换为第一通道,并向所述AS反馈第三响应消息。
步骤S217、在通道切换后,所述UE和所述AS之间可通过所述第一通道实现数据的交互。例如,所述UE可通过所述第一通道将所述UE的业务数据发送至所述AS中处理。
步骤S218、在所述AS确定到和所述源MEC平台之间同步完成所述UE的业务数据后,向所述源MEC平台发送第四指示信息,用于指示所述源MEC平台将所述用户状态切换为等待dying状态,以等待所述源MEC平台和所述UE之间的通信断连。可选的,所述第四指示信息还用于指示所述源MEC平台停止和所述AS之间同步所述UE的业务数据等。
步骤S219、在所述源MEC平台接收所述第四指示信息后,根据所述第四指示信息的指示将所述用户状态切换为等待状态。可选的,所述源MEC平台还可释放所述UE相关的计算资源和存储资源,保留所述第二通道所占用的通道资源,以支持传输简单的握手消息,等待通信断连时释放所述第二通道所占用的通道资源,如socket资源。
步骤S220、在确定到所述UE切换离开所述源MEC平台后,断开所述源MEC平台和所述UE之间的通信连接,即断开所述第二通道。
具体的,当所述源MEC平台在设定时长内没有接收到所述UE发送的握手消息后,可确定所述UE已切换离开所述源MEC平台,即所述UE已切换离开所述源基站eNB。所述设定时长为用户侧或平台侧自定义设置的,例如10s等,不作限定。
步骤S221、进一步地,所述源MEC平台释放所述第二通道占用的通道资源。
步骤S222、在所述UE从所述源MEC平台切换至目标MEC平台后,可向所述目标MEC平台发送第三创建请求,所述第三创建请求携带第三通道参数,用于请求创建所述UE和所述目标MEC平台之间通信时所用的第三通道。
具体的,在所述UE切换至目标基站对应部署的目标MEC平台后,如果所述目标MEC平台中部署有目标应用,该目标应用用于处理所述UE的业务数据,此时所述UE可实时或周期性地尝试和所述目标MEC平台建立通信,即所述UE向所述MEC平台发送第三创建请求,以创建所述第三通道。
步骤S223、在所述目标MEC平台接收所述第三创建请求后,根据所述第三通道参数创建所述第三通道,向所述UE发送第三创建响应,用于通知所述第三通道已创建成功。
本申请中,所述第一通道参数、第二通道参数以及第三通道参数可参见前述实施例中的相关介绍,这里不再赘述。
步骤S224、所述目标MEC平台向所述AS发送数据同步请求,用于请求启动所述目标MEC平台和所述AS之间的数据同步功能。
步骤S225、所述AS在接收所述数据同步请求后,向所述目标MEC平台发送数据同步响 应,用于通知允许启动所述目标MEC平台和所述AS之间的数据同步功能,所述目标MEC平台和所述AS之间可以进行数据的同步。
步骤S226、所述AS和所述目标MEC平台之间可实现数据的同步。例如,所述AS将其内存储的所述UE的业务数据同步发送至所述目标MEC平台中处理等。
步骤S227、所述目标MEC平台向所述UE发送第五指示信息,用于指示所述UE将原来通信使用的所述第一通道切换为第三通道,以便后续所述UE通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理。
步骤S228、所述UE在接收所述第五指示信息后,响应所述第五指示信息,向所述目标MEC平台发送第五响应消息,用于通知所述UE已将所述第一通道切换为第三通道。
具体的,在所述目标MEC平台和所述AS之间开始同步数据(即所述UE的业务数据)后,或者它们之间数据同步稳定之后,所述目标MEC平台向所述UE发送第五指示信息,用于指示所述UE后续通过第三通道将所述UE的业务数据发送至所述目标MEC平台中处理。相应地,所述UE接收所述第五指示信息,根据所述第五指示信息的指示将所述第一通道切换为第三通道,并向所述目标MEC平台反馈第五响应消息。
步骤S229、在通道切换后,所述UE和所述目标MEC平台可通过所述第三通道实现数据的交互。例如,后续所述UE可通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理。相应地,所述目标MEC平台可将处理结果反馈给所述UE等。
步骤S230、在所述目标MEC平台确定到和所述AS之间同步完成所述UE的业务数据后,向所述AS发送第六指示信息,用于指示所述AS将所述用户状态切换为空闲idle状态,以通知后续不在所述AS中处理所述UE的业务数据。可选的,所述第六指示信息还用于指示所述AS停止和所述目标MEC平台之间同步所述UE的业务数据等。
步骤S231、所述AS接收所述第六指示信息后,根据所述第六指示信息的指示将所述用户状态切换为空闲状态。可选的,所述AS还可释放所述UE相关的计算资源和存储资源,保留所述第一通道所占用的通道资源(如socket资源等),以支持传输简单的握手消息,等待下次UE切换所述目标MEC平台时,再次启用第一通道利用所述AS处理所述UE的业务数据。
步骤S232、所述AS向所述目标MEC平台发送第六响应消息,用于通知所述AS已将所述用户状态切换为空闲状态。可选的,还可用于通知所述AS已释放所述UE的相关计算资源和存储资源等。
通过实施本发明实施例,能够解决由于UE切换基站eNB,导致业务数据需从源MEC平台迁移至目标MEC平台中处理,中间可能出现的业务中断或通信中断等问题。
请参见图5是本发明实施例提供的又一种业务切换处理方法的流程示意图。如图5所示的方法包括如下实施步骤:
步骤S301、用户设备UE预先配置通道参数,所述通道参数用于创建所述UE和目标设备通信时所需的通道。
其中,所述通道参数可包括优选通道参数和备选通道参数,所述优选通道参数用于创建所述UE和MEC平台之间通信时的优选通信,例如前述实施例中的第二通道和第三通道等。所述备选通道参数用于创建所述UE和所述AS之间通信时所用的备选通道,例如前述实施例中的第一通道等。
所述目标设备(这里即AS或MEC平台)中部署/安装有目标应用,用于处理所述UE的业 务数据。相应地,通过通道(具体可优选通道或备选通道)可将所述UE的业务数据传输至所述目标设备中处理。
相应地,所述优选通道参数和所述备选通道参数可为用于创建通道时所需的通道参数,也可理解是所述目标应用在目标设备中的对接信息,其可包括但不限于网络协议IP地址、通信使用的逻辑端口、用户名以及密码等。
步骤S302、所述UE向云服务器AS发送备选创建请求,所述备选创建请求携带有备选通道参数,用于请求创建所述UE和所述AS相互通信时所需的备选通道。
步骤S303、所述AS接收到所述备选创建请求后,向所述UE发送备选创建响应,用于通知所述备选通道已创建成功。具体的,所述AS接收所述备选创建请求后,根据所述备选通道参数创建所述备选通道,以便后续所述AS和所述UE通过所述备选通道实现数据的交互。
步骤S304、所述UE向MEC平台发送优选创建请求,所述优选创建请求携带优选通道参数,用于请求创建所述UE和所述MEC平台之间相互通信时所需的优选通道。
需要说明的是,本实施例中所述MEC平台包括但不限于源MEC平台以及目标MEC平台、或者其他支持处理所述UE的业务数据的平台等。
步骤S305、所述MEC平台接收所述优选创建请求后,向云服务器AS发送第二指示信息,用于指示所述AS将用户状态切换为空闲状态,以指示/通知后续不在所述AS中处理所述UE的业务数据。
步骤S306、在所述AS接收所述第二指示信息后,可释放所述UE相关的计算资源和存储资源,保留所述备选通道(即保留所述备选通道所占用的通道资源)。
步骤S307、所述AS向所述MEC平台发送第二响应消息,用于指示所述AS已将所述用户状态切换为空闲状态。
步骤S308、在所述MEC平台接收所述第二响应消息后,向所述UE发送第二创建响应,用于指示所述备选通道已创建成功。
步骤S309、在所述优选通道创建成功后,业务初始化成功。所述UE和所述MEC平台可通过所述优选通道进行数据的交互。
步骤S310、所述MEC平台确定目标应用将停止处理所述UE的业务数据。
具体的,在所述MEC平台检测/接收到针对所述目标应用的操作指令后,可确定所述MEC平台中的目标应用即将停止处理所述UE的业务数据。其中,所述操作指令包括但不限于以下中的任一项或多项的组合:更新指令、删除/卸载指令、重配置指令以及其他用于对所述目标应用进行更改的指令等等。以更新指令为例,当所述MEC平台检测到用户/系统周期性对所述目标应用进行升级或打补丁操作后,即检测到针对所述目标应用的更新指令,由于目标应用正在升级/打补丁过程中不能提供业务服务,则可确定目标应用将停止处理所述UE的业务数据。
步骤S311、在所述MEC平台确定到目标应用将停止处理所述UE的业务数据后,向所述AS发送第一指示信息,用于指示启动所述UE和所述AS之间的数据同步功能,并指示所述AS将用户状态切换为激活状态,以通知后续再所述AS中处理所述UE的业务数据。
步骤S312、所述AS在接收所述第一指示信息后,响应所述第一指示信息,启动所述MEC平台和所述AS之间的数据同步功能,将所述用户状态切换为激活状态。可选的,还可为所述UE申请相关的计算资源和存储资源,以用于处理所述UE的业务数据。
步骤S313、所述AS向所述MEC平台发送第一响应消息,用于通知已启动所述AS和所述 MEC平台之间的数据同步功能。
步骤S314、在所述MEC平台和所述AS之间已启动数据同步功能后,可实现所述MEC平台和所述AS之间的数据同步。例如,所述MEC平台可将其内存储的所述UE的业务数据同步发送给所述AS,以在所述AS中处理所述UE的业务数据。
步骤S315、所述AS向所述UE发送第三指示信息,用于指示所述UE将原来通信时的优选通道切换为备选通道,以便后续通过所述备选通道将所述UE的业务数据发送至所述AS中处理。
步骤S316、所述UE在接收所述第三指示信息后,响应所述第三指示信息,向所述AS发送第三响应消息,用于指示所述UE已将所述优选通道切换为备选通道。
步骤S317、在通道切换后,所述UE和所述AS之间可通过所述第一通道实现数据的交互。例如,所述UE可通过所述第一通道将所述UE的业务数据发送至所述AS中处理。
步骤S318、在所述AS确定到和所述MEC平台之间同步完成所述UE的业务数据后,向所述MEC平台发送第四指示信息,用于指示所述MEC平台将所述用户状态切换为等待dying状态。
步骤S319、在所述MEC平台接收所述第四指示信息后,根据所述第四指示信息的指示将所述用户状态切换为等待状态。可选的,所述MEC平台还可释放所述UE相关的计算资源和存储资源,保留所述优选通道所占用的通道资源。
步骤S320、在所述MEC平台确定到所述目标应用已停止处理所述UE的业务数据后,断开所述MEC平台和所述UE之间的通信连接,即断开所述优选通道。
步骤S321、所述MEC平台检测所述目标应用重新处理所述UE的业务数据。
步骤S322、所述UE重新向所述MEC平台发送优选创建请求,所述优选创建请求携带优选通道参数,用于请求创建所述UE和所述MEC平台之间通信时所用的所述优选通道。
具体的,在所述UE和所述MEC平台通信断连后,所述UE可周期性地/实时地尝试再次和所述MEC平台的通信。在所述MEC平台检测到所述目标应用重新用于处理所述UE的业务数据后,所述UE和所述MEC平台可再次成功建立通信连接。
步骤S323、在所述MEC平台接收所述优选创建请求后,根据所述优选通道参数创建所述优选通道,向所述UE发送优选创建响应,用于通知所述优选通道已创建成功。
步骤S324、所述MEC平台向所述AS发送数据同步请求,用于请求启动所述MEC平台和所述AS之间的数据同步功能。
步骤S325、所述AS在接收所述数据同步请求后,向所述MEC平台发送数据同步响应,用于通知允许启动所述MEC平台和所述AS之间的数据同步功能,所述MEC平台和所述AS之间可以进行数据的同步。
步骤S326、所述AS和所述MEC平台之间可实现数据的同步。例如,所述AS将其内存储的所述UE的业务数据同步发送至所述MEC平台中处理等。
步骤S327、所述MEC平台向所述UE发送第五指示信息,用于指示所述UE将原来通信使用的所述备用通道切换为优选通道,以便后续所述UE通过所述优选通道将所述UE的业务数据发送至所述MEC平台中处理。
步骤S328、所述UE在接收所述第五指示信息后,响应所述第五指示信息,向所述MEC平台发送第五响应消息,用于通知所述UE已将所述备选通道切换为优选通道。
步骤S329、在通道切换后,所述UE和所述MEC平台可通过所述优选通道实现数据的交 互。
步骤S330、在所述MEC平台确定到和所述AS之间同步完成所述UE的业务数据后,向所述AS发送第六指示信息,用于指示所述AS将所述用户状态切换为空闲idle状态,以通知后续不在所述AS中处理所述UE的业务数据。
步骤S331、所述AS接收所述第六指示信息后,根据所述第六指示信息的指示将所述用户状态切换为空闲状态。可选的,所述AS还可释放所述UE相关的计算资源和存储资源,保留所述备选通道所占用的通道资源(如socket资源等)
步骤S332、所述AS向所述MEC平台发送第六响应消息,用于通知所述AS已将所述用户状态切换为空闲状态。可选的,还可用于通知所述AS已释放所述UE的相关计算资源和存储资源等。
通过实施本发明实施例,能够解决当MEC平台中目标应用停止处理所述UE的业务数据(即停止提高业务服务)后,可能导致出现的业务中断等问题。
上述主要从设备(可为用户设备UE和云服务器AS)和MEC平台相互交互的角度出发对本发明实施例提供的方案进行了介绍。在实际应用中,所述MEC平台(本申请可为源MEC平台和/或目标MEC平台)可作为网络设备,部署在网络中。可以理解的是,第一设备(具体可为用户设备或者网络设备,这里的网络设备具体可为云服务器,或者用于部署源MEC平台或目标MEC平台的网络设备)为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。结合本发明中所公开的实施例描述的各示例的单元及算法步骤,本发明实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能,但是这种实现不应认为超出本发明实施例的技术方案的范围。
本发明实施例可以根据上述方法示例对第一设备进行功能单元的划分,例如,可以对应各个功能划分各个功能单元,也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。需要说明的是,本发明实施例中对单元的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
在采用集成的单元的情况下,图6A示出了上述实施例中所涉及的第一设备的一种可能的结构示意图。第一设备700包括:处理单元702和通信单元703。处理单元702用于对第一设备700的动作进行控制管理。
在一种可能的实施例中,当所述第一设备700为用户设备700时,处理单元702用于支持第一设备700执行图4中步骤S201和S216,图5中步骤S301和S316,和/或用于执行本文所描述的技术的其它步骤。通信单元703用于支持第一设备700与其它设备的通信,例如,通信单元703用于支持第一设备700执行图3中步骤S1001、S1003、S1006、S104、S107以及S111,图4中步骤S202、S204、S208、S209、S215、S217、S222、S227以及S229,图5中步骤S302、S304、S308、S309、S315、S317、S322、S327以及S329,和/或用于执行本文所描述的技术的其它步骤。
在一种可能的实施例中,当所述第一设备700为云服务器700时,处理单元702用于支持第一设备700执行图3中S102和S104,图4中步骤S206、S212以及S231,图5中步骤 S306、S312以及S331,和/或用于执行本文所描述的技术的其它步骤。通信单元703用于支持第一设备700与其它设备的通信,例如,通信单元703用于支持第一设备700执行图3中S1002、S1005、S104、S105、S110以及S114,图4中步骤S207、S213、S214、S215、S217、S218、S225、S226以及S232,图5中步骤S307、S313、S314、S315、S317、S318、S325、S326以及S332,和/或用于执行本文所描述的技术的其它步骤。
在一种可能的实施例中,当所述第一设备700为用于部署源MEC平台的网络设备700时,处理单元702用于支持第一设备700执行图3中S106,图4中步骤S210、S219以及S221,图5中步骤S310、S319以及S321,和/或用于执行本文所描述的技术的其它步骤。通信单元703用于支持第一设备700与其它设备的通信,例如,通信单元703用于支持第一设备700执行图3中S1004和S1006,图4中步骤S205、S209和S211,图5中步骤S305、S309、S311、S327、S329以及S330,和/或用于执行本文所描述的技术的其它步骤。
在一种可能的实施例中,当所述第一设备700为用于部署目标MEC平台的网络设备700时,处理单元702用于支持第一设备700执行图3中S108,图4中S223,图5中步骤S323,和/或用于执行本文所描述的技术的其它步骤。通信单元703用于支持第一设备700与其它设备的通信,例如,通信单元703用于支持第一设备700执行图3中S109、S111以及S113,图4中步骤S224、S226、S227、S229以及S230,图5中步骤S305、S308、S311、S314、S324、S326、S327、S329以及S330,和/或用于执行本文所描述的技术的其它步骤。
可选的,第一设备700还可以包括存储单元701,用于存储第一设备700的程序代码和数据。
其中,处理单元702可以是处理器或控制器,例如可以是中央处理器(英文:Central Processing Unit,CPU),通用处理器,数字信号处理器(英文:Digital Signal Processor,DSP),专用集成电路(英文:Application-Specific Integrated Circuit,ASIC),现场可编程门阵列(英文:Field Programmable Gate Array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信单元703可以是通信接口、收发器、收发电路等,其中,通信接口是统称,可以包括一个或多个接口,例如网络设备与其他设备之间的接口。存储单元701可以是存储器。
当处理单元702为处理器,通信单元703为通信接口,存储单元701为存储器时,本发明实施例所涉及的第一设备可以为图6B所示的第一设备。
参阅图6B所示,该第一设备710包括:处理器712、通信接口713、存储器77。可选地,第一设备710还可以包括总线714。其中,通信接口713、处理器712以及存储器77可以通过总线714相互连接;总线714可以是外设部件互连标准(英文:Peripheral Component Interconnect,简称PCI)总线或扩展工业标准结构(英文:Extended Industry Standard Architecture,简称EISA)总线等。所述总线714可以分为地址总线、数据总线、控制总线等。为便于表示,图6B中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
上述图6A或图6B所示的第一设备的具体实现还可以对应参照前述方法实施例的相应描述,此处不再赘述。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现,也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成,软件模块 可以被存放于随机存取存储器(英文:Random Access Memory,RAM)、闪存、只读存储器(英文:Read Only Memory,ROM)、可擦除可编程只读存储器(英文:Erasable Programmable ROM,EPROM)、电可擦可编程只读存储器(英文:Electrically EPROM,EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器,从而使处理器能够从该存储介质读取信息,且可向该存储介质写入信息。当然,存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外,该ASIC可以位于网络设备中。当然,处理器和存储介质也可以作为分立组件存在于第一设备中。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程,是可以通过计算机程序来指令相关的硬件来完成,所述的程序可存储于计算机可读取存储介质中,该程序在执行时,可包括如上述各方法的实施例的流程。而前述的存储介质包括:ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (45)

  1. 一种业务切换处理系统,其特征在于,所述系统包括源移动边缘计算MEC平台以及云服务器AS,其中:
    所述源MEC平台,用于在确定到目标应用将停止处理用户设备UE的业务数据的情况下,向所述AS发送第一指示信息;其中,所述第一指示信息用于指示将在所述AS中处理所述UE的业务数据,所述源MEC平台中部署有所述目标应用,所述目标应用为用于处理所述UE的业务数据的应用;
    所述AS,用于响应所述第一指示信息,向所述源MEC平台发送第一响应消息,所述第一响应消息用于指示所述AS已准备好处理所述UE的业务数据。
  2. 根据权利要求1所述的系统,其特征在于,所述确定到目标应用将停止处理所述UE的业务数据,包括:所述源MEC平台获取到针对所述目标应用的操作指令,或者所述源MEC平台接收到基站发送的切换通知;其中,所述操作指令包括以下中的至少一项:更新指令、卸载指令以及重配置指令。
  3. 根据权利要求1或2所述的系统,其特征在于,所述第一指示信息用于指示所述AS将用户状态切换为激活状态,以等待处理所述UE的业务数据;其中,所述AS中的用户状态用于指示是否在所述AS中处理所述UE的业务数据;
    所述AS,具体用于根据所述第一指示信息的指示,将所述用户状态切换为激活状态,并向所述源MEC平台发送所述第一响应消息;其中,所述第一响应消息还用于指示所述AS已将所述用户状态切换为激活状态。
  4. 根据权利要求1-3中任一项所述的系统,其特征在于,所述系统还包括UE,所述源MEC平台向所述AS发送第一指示信息之前,
    所述源MEC平台,用于在接收创建消息后,向所述AS发送第二指示信息,所述第二指示信息用于指示不在所述AS中处理所述UE的业务数据,所述创建消息用于请求创建所述UE和所述源MEC平台之间通信时所用的通道;
    所述AS,用于响应所述第二指示信息,向所述源MEC平台发送第二响应消息,所述第二响应消息用于指示所述AS已确定不在处理所述UE的业务数据。
  5. 根据权利要求4所述的系统,其特征在于,所述第二指示信息用于指示所述AS将所述用户状态切换为空闲状态,以不在所述AS中处理所述UE的业务数据;
    所述AS,具体用于根据所述第二指示信息的指示,将所述用户状态切换为空闲状态,并向所述源MEC平台发送所述第二响应消息;所述第二响应消息还用于指示所述AS已将所述用户状态切换为空闲状态。
  6. 根据权利要求1-5中任一项所述的系统,其特征在于,所述系统还包括所述UE,在所述源MEC平台和所述AS之间开始同步所述UE的业务数据后,
    所述AS,还用于向所述UE发送第三指示信息,所述第三指示信息用于指示将所述UE的业务数据发送至所述AS中处理;
    所述UE,还用于响应所述第三指示信息,向所述AS发送第三响应消息,所述第三响应消息用于通知所述UE已确定将所述UE的业务数据发送至所述AS中处理。
  7. 根据权利要求6所述的系统,其特征在于,
    所述第三指示信息用于指示所述UE将第二通道切换为第一通道,以通过所述第一通道将 所述UE的业务数据发送至所述AS中处理;其中,所述第一通道为所述UE和所述AS之间通信时所用的通道,所述第二通道为所述UE和所述源MEC平台之间通信时所用的通道;
    所述第三响应消息用于指示所述UE已将所述第二通道切换为第一通道。
  8. 根据权利要求1-7所述的系统,其特征在于,在所述源MEC平台和所述AS之间同步完成所述UE的业务数据后,
    所述AS,还用于向所述源MEC平台发送第四指示信息,所述第四指示信息用于指示等待所述源MEC平台和所述UE之间的通信断连;
    所述源MEC平台,还用于根据所述第四指示信息的指示,等待所述源MEC平台和所述UE之间的通信断连。
  9. 根据权利要求8所述的系统,其特征在于,所述第四指示信息用于指示所述源MEC平台将所述目标应用中的用户状态切换为等待状态,以等待所述源MEC平台和所述UE之间的通信断连;
    所述源MEC平台,具体用于根据所述第四指示信息的指示,将所述目标应用的用户状态切换为等待状态。
  10. 根据权利要求9所述的系统,其特征在于,
    所述源MEC平台,还用于在检测到所述UE离开所述源MEC平台后,释放所述源MEC平台和所述UE之间所占用的通道资源。
  11. 根据权利要求1-10中任一项所述的系统,其特征在于,所述系统还包括目标MEC平台,
    所述UE,还用于在所述UE从所述源MEC平台切换至所述目标MEC平台,或者所述目标MEC平台中的所述目标应用重新支持处理所述UE的业务数据的情况下,向所述目标MEC平台发送创建请求,所述创建请求携带通道参数,用于请求创建所述UE和所述目标MEC平台之间通信时所用的第三通道;所述目标MEC平台部署有所述目标应用;
    所述目标MEC平台,用于接收所述创建请求,根据所述通道参数创建所述第三通道,并向所述UE发送创建响应,所述创建响应用于指示所述第三通道已创建成功。
  12. 根据权利要求11所述的系统,其特征在于,在所述目标MEC平台和所述AS之间开始同步所述UE的业务数据后,
    所述目标MEC平台,还用于向所述UE发送第五指示信息,所述第五指示信息用于指示将所述UE的业务数据发送至所述目标MEC平台中处理;
    所述UE,还用于响应所述第五指示信息,向所述目标MEC平台发送第五响应消息,所述第五响应消息用于通知所述UE已确定将所述UE的业务数据发送至所述目标MEC平台中处理。
  13. 根据权利要求12所述的系统,其特征在于,所述第五指示信息用于指示所述UE将所述第二通道切换为所述第三通道,以通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理;
    所述UE,具体用于根据所述第五指示信息的指示,将所述第二通道切换为所述第三通道,并向所述目标MEC平台发送第五响应消息;所述第五响应消息用于指示所述UE已将所述第二通道切换为所述第三通道。
  14. 根据权利要求12或13所述的系统,其特征在于,在所述目标MEC平台和所述AS之间同步完成所述UE的业务数据后,
    所述目标MEC平台,还用于向所述AS发送第六指示信息,所述第六指示信息用于指示不 在所述AS中处理所述UE的业务数据;
    所述AS,还用于响应所述第六指示信息,并向所述目标MEC平台发送第六响应消息,所述第六响应消息用于指示所述AS已确定不在处理所述UE的业务数据。
  15. 根据权利要求14所述的系统,其特征在于,所述第六指示信息用于指示所述AS将所述用户状态切换为空闲状态,以不在所述AS中处理所述UE的业务数据;
    所述AS,具体用于根据所述第六指示信息的指示,将所述用户状态切换为空闲状态,并向所述目标MEC平台发送所述第六响应消息;所述第六响应消息还用于指示所述AS已将所述用户状态切换为空闲状态。
  16. 一种业务切换处理方法,其特征在于,应用于源移动边缘计算MEC平台中,所述方法包括:
    所述源MEC平台在确定到目标应用将停止处理用户设备UE的业务数据的情况下,向所述AS发送第一指示信息;其中,所述第一指示信息用于指示将在所述AS中处理所述UE的业务数据,所述源MEC平台中部署有所述目标应用,所述目标应用为用于处理所述UE的业务数据的应用;
    所述源MEC平台接收所述AS返回的第一响应消息,所述第一响应消息用于通知所述AS已准备好处理所述UE的业务数据。
  17. 根据权利要求16所述的方法,其特征在于,所述确定到目标应用将停止处理所述UE的业务数据,包括:所述源MEC平台获取到针对所述目标应用的操作指令,或者所述源MEC平台接收到基站发送的切换通知;其中,所述操作指令包括以下中的至少一项:更新指令、卸载指令以及重配置指令。
  18. 根据权利要求16或17所述的方法,其特征在于,所述第一指示信息用于指示所述AS将用户状态切换为激活状态,以等待处理所述UE的业务数据;其中,所述AS中的用户状态用于指示是否在所述AS中处理所述UE的业务数据;
    所述第一响应消息还用于通知所述AS已将所述用户状态切换为激活状态。
  19. 根据权利要求16-18中任一项所述的方法,其特征在于,所述方法还包括:
    在接收到所述UE发送的创建请求的情况下,向所述AS发送第二指示信息;其中,所述第二指示信息用于指示不在所述AS中处理所述UE的业务数据,所述创建消息用于请求创建所述UE和所述源MEC平台之间通信时所用的通道;
    接收所述AS返回的第二响应消息,所述第二响应消息用于通知所述AS已确定不在处理所述UE的业务数据。
  20. 根据权利要求16-19中任一项所述的方法,其特征在于,在所述源MEC平台和所述AS之间同步完成所述UE的业务数据后,所述方法还包括:
    接收所述AS发送的第四指示信息,所述第四指示信息用于指示等待所述源MEC平台和所述UE之间的通信断连。
  21. 一种业务切换处理方法,其特征在于,应用于目标移动边缘计算MEC平台中,所述方法包括:
    所述目标MEC平台接收所述UE发送的创建请求,所述创建请求携带通道参数,用于请求创建所述UE和所述目标MEC平台之间通信时所用的第三通道;
    根据所述通道参数创建所述第三通道,并向所述UE发送创建响应,所述创建响应用于通知所述第三通道已创建成功。
  22. 根据权利要求21所述的方法,其特征在于,所述创建请求为所述UE切换到部署有目标应用的所述目标MEC平台后发送的,或者所述UE确定到所述目标MEC平台中目标应用重新支持处理所述UE的业务数据后发送的;其中,所述目标MEC平台部署有所述目标应用,所述目标应用为用于处理所述UE的业务数据的应用。
  23. 根据权利要求21或22所述的方法,其特征在于,在所述目标MEC平台和所述UE之间开始同步所述UE的业务数据后,所述方法还包括:
    所述目标MEC平台向所述UE发送第五指示信息,用于指示所述UE将所述UE的业务数据发送至所述目标MEC平台中处理;
    接收所述UE返回的第五响应消息,用于通知所述UE已确定将所述UE的业务数据发送至所述目标MEC平台中处理。
  24. 根据权利要求23所述的方法,其特征在于,所述第五指示信息用于指示所述UE将第二通道切换为所述第三通道,以通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理;所述第二通道为所述UE和所述源MEC平台之间通信时所用的通道;
    所述第五响应消息还用于通知所述UE已将所述第二通道切换为第三通道。
  25. 根据权利要求21-24中任一项所述的方法,其特征在于,在所述目标MEC平台和所述AS之间同步完成所述UE的业务数据后,所述方法还包括:
    所述目标MEC平台向所述AS发送第六指示信息,用于指示不在所述AS中处理所述UE的业务数据;
    接收所述AS返回的第六响应消息,用于通知所述AS已确定不在处理所述UE的业务数据。
  26. 一种业务切换处理方法,其特征在于,应用于云服务器AS中,所述方法包括:
    所述AS接收源MEC平台发送的第一指示信息,所述第一指示信息用于指示将在所述AS中处理用户设备UE的业务数据;
    响应所述第一指示信息,向所述源MEC平台发送第一响应消息,所述第一响应消息用于通知所述AS已准备好处理所述UE的业务数据。
  27. 根据权利要求26所述的方法,其特征在于,所述响应所述第一指示信息包括:
    在所述第一指示信息用于指示所述AS将用户状态切换为激活状态的情况下,所述AS根据所述第一指示信息的指示,将所述用户状态切换为激活状态,以等待处理所述UE的业务数据;其中,所述AS中的用户状态用于指示是否在所述AS中处理所述UE的业务数据;
    所述第一响应消息还用于通知所述AS已将所述用户状态切换为激活状态。
  28. 根据权利要求26或27所述的方法,其特征在于,所述AS接收所述第一指示信息之前,还包括:
    接收所述源MEC平台发送的第二指示信息,所述第二指示信息用于指示不在所述AS中处理所述UE的业务数据;
    响应所述第二指示信息,向所述源MEC平台发送第二响应消息,所述第二响应消息用于指示所述AS已确定不在处理所述UE的业务数据。
  29. 根据权利要求26-27中任一项所述的方法,在所述源MEC平台和所述AS之间开始同步所述UE的业务数据后,所述方法还包括:
    所述AS向所述UE发送第三指示信息,所述第三指示信息用于指示将所述UE的业务数据发送至所述AS中处理;
    接收所述UE返回的第三响应消息,所述第三响应消息用于通知所述UE已确定将所述UE的业务数据发送至所述AS中处理。
  30. 根据权利要求26-29中任一项所述的方法,其特征在于,在所述源MEC平台和所述AS之间同步完成所述UE的业务数据后,所述方法还包括:
    所述AS向所述源MEC平台发送第四指示信息,所述第四指示信息用于指示等待所述源MEC平台和所述UE之间的通信断连。
  31. 根据权利要求26-30中任一项所述的方法,其特征在于,所述UE从所述源MEC平台切换至部署有目标应用的目标MEC平台,所述目标应用用于处理所述UE的业务数据,且所述目标MEC平台和所述AS之间同步完成所述UE的业务数据后,所述方法还包括:
    接收所述目标MEC平台发送的第六指示信息,所述第六指示信息用于指示不在所述AS中处理所述UE的业务数据;
    响应所述第六指示信息,向所述目标MEC平台发送第六响应消息,所述第六响应消息用于指示所述AS已确定不在处理所述UE的业务数据。
  32. 一种业务切换处理方法,其特征在于,应用于用户设备UE中,所述方法包括:
    所述UE向目标设备发送创建请求,所述创建请求携带所述UE中预置的通道参数,用于请求创建所述UE和所述目标设备之间通信时所用的通道;
    接收所述目标设备返回的创建响应,所述创建响应用于通知所述通道已创建成功。
  33. 根据权利要求32所述的方法,其特征在于,
    在所述创建请求携带第一通道参数的情况下,所述第一通道参数用于创建所述UE和云服务器AS之间通信时所用的第一通道,以通过所述第一通道将所述UE的业务数据发送至所述AS中处理;
    在所述创建请求携带第二通道参数的情况下,所述第二通道参数用于创建所述UE和源MEC平台之间通信时所用的第二通道,以通过所述第二通道将所述UE的业务数据发送至所述源MEC平台中处理;
    在所述创建请求携带第三通道参数的情况下,所述第三通道参数用于创建所述UE和目标MEC平台之间通信时所用的第三通道,以通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理。
  34. 根据权利要求33所述的方法,其特征在于,在所述源MEC平台和所述AS之间开始同步所述UE的业务数据,以在所述AS中处理所述UE的业务数据之后,所述方法还包括:
    接收所述AS发送的第三指示信息,所述第三指示信息用于指示将所述UE的业务数据发送至所述AS中处理;
    向所述AS返回第三响应消息,所述第三响应消息用于通知所述UE已确定将所述UE的业务数据发送至所述AS中处理。
  35. 根据根据权利要求34所述的方法,其特征在于,所述第三指示信息用于指示所述UE将所述第二通道切换为所述第一通道,以通过所述第一通道将所述UE的业务数据发送至所述AS中处理;
    所述第三响应消息用于指示所述UE已将所述第二通道切换为第一通道。
  36. 根据权利要求32-35中任一项所述的方法,其特征在于,在所述UE从所述源MEC平台切换至目标MEC平台,且所述目标MEC平台和所述AS之间开始同步所述UE的业务数据后,所述方法还包括:
    接收所述目标MEC平台发送的第五指示信息,用于指示所述UE将所述UE的业务数据发送至所述目标MEC平台中处理;
    向所述目标MEC平台发送第五响应消息,用于通知所述UE已确定将所述UE的业务数据发送至所述目标MEC平台中处理。
  37. 根据权利要求36所述的方法,其特征在于,所述第五指示信息用于指示所述UE将第二通道切换为所述第三通道,以通过所述第三通道将所述UE的业务数据发送至所述目标MEC平台中处理;所述第二通道为所述UE和所述源MEC平台之间通信时所用的通道;
    所述第五响应消息还用于通知所述UE已将所述第二通道切换为第三通道。
  38. 一种网络设备,器特征在于,包括存储器、通信接口及与所述存储器和通信接口耦合的处理器;所述存储器用于存储指令,所述处理器用于执行所述指令,所述通信接口用于在所述处理器的控制下与其他设备进行通信;其中,所述处理器执行所述指令时执行如上权利要求16-20中任一项所述的方法。
  39. 一种网络设备,其特征在于,包括存储器、通信接口及与所述存储器和通信接口耦合的处理器;所述存储器用于存储指令,所述处理器用于执行所述指令,所述通信接口用于在所述处理器的控制下与其他设备进行通信;其中,所述处理器执行所述指令时执行如上权利要求21-25中任一项所述的方法。
  40. 一种网络设备,其特征在于,包括存储器、通信接口及与所述存储器和通信接口耦合的处理器;所述存储器用于存储指令,所述处理器用于执行所述指令,所述通信接口用于在所述处理器的控制下与其他设备进行通信;其中,所述处理器执行所述指令时执行如上权利要求26-31中任一项所述的方法。
  41. 一种用户设备,其特征在于,包括存储器、通信接口及与所述存储器和通信接口耦合的处理器;所述存储器用于存储指令,所述处理器用于执行所述指令,所述通信接口用于在所述处理器的控制下与其他设备进行通信;其中,所述处理器执行所述指令时执行如上权利要求32-37中任一项所述的方法。
  42. 一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现如权利要求16至20任一项所述方法。
  43. 一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现如权利要求21至25任一项所述方法。
  44. 一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现如权利要求26至31任一项所述方法。
  45. 一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现如权利要求32至37任一项所述方法。
PCT/CN2019/078364 2018-03-23 2019-03-15 业务切换处理方法、相关产品及计算机存储介质 WO2019179372A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19771907.3A EP3761603B1 (en) 2018-03-23 2019-03-15 Service switching processing method, related product, and computer readable storage medium
US17/029,542 US11445411B2 (en) 2018-03-23 2020-09-23 Service switching processing method, related product, and computer storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810251267.6 2018-03-23
CN201810251267.6A CN110300143B (zh) 2018-03-23 2018-03-23 业务切换处理方法、相关装置及计算机存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/029,542 Continuation US11445411B2 (en) 2018-03-23 2020-09-23 Service switching processing method, related product, and computer storage medium

Publications (1)

Publication Number Publication Date
WO2019179372A1 true WO2019179372A1 (zh) 2019-09-26

Family

ID=67988200

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/078364 WO2019179372A1 (zh) 2018-03-23 2019-03-15 业务切换处理方法、相关产品及计算机存储介质

Country Status (4)

Country Link
US (1) US11445411B2 (zh)
EP (1) EP3761603B1 (zh)
CN (1) CN110300143B (zh)
WO (1) WO2019179372A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2021259515B2 (en) * 2020-04-23 2024-02-29 International Business Machines Corporation Sharing geographically concentrated workload among neighboring mec hosts of multiple carriers

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113572797B (zh) * 2020-04-29 2024-05-31 阿里巴巴集团控股有限公司 数据处理方法、装置、系统及电子设备
CN113778463B (zh) * 2020-06-09 2023-01-06 华为技术有限公司 一种业务服务部署方法及装置
CN112130931B (zh) * 2020-09-27 2023-01-06 联想(北京)有限公司 一种应用部署方法、节点、系统及存储介质
CN113507733B (zh) * 2021-06-18 2023-10-24 新华三技术有限公司 一种基于mec的用户切换方法、服务器和存储介质
KR20230044690A (ko) * 2021-09-27 2023-04-04 삼성전자주식회사 복수의 기기들을 제어하는 방법 및 장치
CN114172951B (zh) * 2021-12-07 2023-06-06 中国联合网络通信集团有限公司 Mec共享方法、通信装置及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170086049A1 (en) * 2015-09-18 2017-03-23 Huawei Technologies Co., Ltd. System and methods for reliable communication with mobility along a predictable route
WO2017091960A1 (zh) * 2015-11-30 2017-06-08 华为技术有限公司 切换移动边缘平台的方法、装置和系统
WO2017197564A1 (zh) * 2016-05-16 2017-11-23 华为技术有限公司 切换过程中的通信方法和装置

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3355615B1 (en) 2015-10-21 2019-08-28 Huawei Technologies Co., Ltd. Mec platform handover
US20190058767A1 (en) * 2016-01-22 2019-02-21 Nokia Solutions And Networks Oy Application relocation between clouds
CN107454632B (zh) * 2016-05-30 2020-04-24 中国移动通信有限公司研究院 一种切换过程中的业务处理方法、基站及终端
CN107484210A (zh) * 2016-06-07 2017-12-15 大唐移动通信设备有限公司 一种数据传输方法及装置
CN107566437B (zh) * 2016-07-01 2020-04-14 大唐移动通信设备有限公司 信息传输方法及装置
CN106358245B (zh) * 2016-11-07 2019-12-27 北京佰才邦技术有限公司 移动边缘计算应用负荷分担的方法和控制器
US10440096B2 (en) * 2016-12-28 2019-10-08 Intel IP Corporation Application computation offloading for mobile edge computing
US20180352038A1 (en) * 2017-05-30 2018-12-06 Intel Corporation Enhanced nfv switching
US10037231B1 (en) * 2017-06-07 2018-07-31 Hong Kong Applied Science and Technology Research Institute Company Limited Method and system for jointly determining computational offloading and content prefetching in a cellular communication system
CN107404733B (zh) * 2017-08-22 2020-04-24 山东省计算中心(国家超级计算济南中心) 一种基于mec和分层sdn的5g移动通信方法及系统
US10517020B2 (en) * 2017-12-15 2019-12-24 Industrial Technology Research Institute Mobile edge platform servers and user equipment context migration management methods thereof
CN111684774B (zh) * 2017-12-25 2022-08-19 诺基亚通信公司 移动边缘计算(mec)中的服务质量(qos)控制方法、系统
US10715633B2 (en) * 2018-01-10 2020-07-14 Cisco Technology, Inc. Maintaining reachability of apps moving between fog and cloud using duplicate endpoint identifiers
CN111480322B (zh) * 2018-02-22 2022-09-16 中兴通讯股份有限公司 普适计算

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170086049A1 (en) * 2015-09-18 2017-03-23 Huawei Technologies Co., Ltd. System and methods for reliable communication with mobility along a predictable route
WO2017091960A1 (zh) * 2015-11-30 2017-06-08 华为技术有限公司 切换移动边缘平台的方法、装置和系统
WO2017197564A1 (zh) * 2016-05-16 2017-11-23 华为技术有限公司 切换过程中的通信方法和装置

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2021259515B2 (en) * 2020-04-23 2024-02-29 International Business Machines Corporation Sharing geographically concentrated workload among neighboring mec hosts of multiple carriers

Also Published As

Publication number Publication date
CN110300143B (zh) 2021-10-15
EP3761603A4 (en) 2021-01-06
EP3761603B1 (en) 2024-07-10
CN110300143A (zh) 2019-10-01
US20210007018A1 (en) 2021-01-07
EP3761603A1 (en) 2021-01-06
US11445411B2 (en) 2022-09-13

Similar Documents

Publication Publication Date Title
WO2019179372A1 (zh) 业务切换处理方法、相关产品及计算机存储介质
KR102443633B1 (ko) 네트워크 액세스 제어 방법, 컴퓨터 판독 가능 매체 및 전자 디바이스
US10659979B2 (en) Method and device for handling cell outage
US11019536B2 (en) Communication method and apparatus
US11019540B2 (en) User equipment path transfer method, user equipment state conversion control method, user equipment, and base station
CN101583144B (zh) 无线控制器业务信息的备份方法和设备
WO2017193825A1 (zh) 一种进行数据传输的方法和设备
CN107919994B (zh) 实现网络服务双机热备的方法及服务器
CN109803279B (zh) 一种切片管理方法、基站及终端
CN105677380B (zh) 一种双主控隔离的逐板升级的方法及装置
JP2010063022A (ja) アクセスゲートウェイ装置の制御方法及び通信システム
WO2018014783A1 (zh) 一种传输数据方法和设备
CN114303441A (zh) 5g中的rrc非活动的高效上下文处理
WO2013075283A1 (zh) 一种lte基站中基带资源池的实现方法及装置
RU2665210C1 (ru) Устройство и способ создания интерфейса
WO2020085177A1 (ja) 通信装置、通信装置の制御方法、およびプログラム
CN107105501B (zh) 一种基于网络分片的寻呼方法、装置和系统
WO2021088642A1 (zh) 一种辅基站变更方法、主基站、辅基站和终端
JP7013474B2 (ja) コンテキスト解放方法、機器及びシステム
WO2020164470A1 (zh) 通信方法及其装置、系统
EP3876599B1 (en) Data forwarding method and apparatus, and master base station and slave base station
EP3477995B1 (en) Method for accessing inter-rat cell and related device
CN114071801B (zh) 一种终端设备的状态指示方法及通信装置
CN114208390A (zh) 甚至在站点运转中断之后也维持正在进行的通信的方法
WO2024210511A2 (en) Handling deregistration procedure in wireless network

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

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

Country of ref document: EP

Effective date: 20201001