WO2019056949A1 - 业务重定向方法及装置 - Google Patents

业务重定向方法及装置 Download PDF

Info

Publication number
WO2019056949A1
WO2019056949A1 PCT/CN2018/104327 CN2018104327W WO2019056949A1 WO 2019056949 A1 WO2019056949 A1 WO 2019056949A1 CN 2018104327 W CN2018104327 W CN 2018104327W WO 2019056949 A1 WO2019056949 A1 WO 2019056949A1
Authority
WO
WIPO (PCT)
Prior art keywords
edge
app
network device
dnai
service
Prior art date
Application number
PCT/CN2018/104327
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 EP18859139.0A priority Critical patent/EP3672320B1/en
Publication of WO2019056949A1 publication Critical patent/WO2019056949A1/zh
Priority to US16/817,023 priority patent/US11228950B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/121—Shortest path evaluation by minimising delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a service redirection method and apparatus.
  • MEC Mobile edge computing
  • IT internet technology
  • AN access network
  • the typical architecture of the existing MEC can be seen in Figure 1.
  • the edge application (app, APP for short) can be deployed near the user plane function (UPF).
  • the edge UPF When the edge APP is normal, the edge UPF will be The service request sent by the terminal device to the edge APP is offloaded to the edge APP. If the edge APP is abnormal, the edge UPF offloads the service request sent by the terminal device through the AN to the central APP, and the central APP can be deployed in the data network (DN). Therefore, it can be seen that as the data traffic of the user increases, the pressure of the central APP is greatly increased in the case where the edge APP is abnormal.
  • DN data network
  • the embodiment of the present application provides a service redirection method and device, which are used to reduce the pressure of a central APP.
  • the embodiment of the present application provides the following technical solutions:
  • a first aspect provides a service redirection method, the method comprising: a first network device receiving a service request from a terminal device, the service request for requesting a service related to the first edge APP; the first edge APP is unavailable, the first The second edge APP is available, the first network device redirects the service request to the second edge APP, the first edge APP corresponds to the first DNAI, and the second edge APP corresponds to the second DNAI, and the first DNAI can represent the deployment location of the first edge APP
  • the second DNAI is capable of characterizing the deployment position of the second edge APP, the preset condition is met between the deployment locations characterized by the first DNAI and the second DNAI, and the second edge APP is the edge APP corresponding to the second DNAI.
  • An edge APP is an edge APP with the same service and the same function.
  • the first network device when the first edge APP is unavailable, and the second edge APP is available, when the service request of the service related to the first edge APP is received, the service request is redirected to The second edge APP, because the second edge APP and the first edge APP are the same service provider and have the same function edge APP, therefore, the central APP is not required to process the service related to the first edge APP, and the central APP can be reduced. pressure.
  • the first DNAI and the second DNAI belong to the same resource group, and the base stations covered by the access UPF corresponding to any two DNAIs in one resource group are adjacent base stations; or, in a resource group
  • the tracking area identifiers of the access UPFs corresponding to any two DNAIs are the same or adjacent; or the transmission distance between the DCs corresponding to any two DNAIs in a resource group is less than or equal to a preset threshold.
  • the possible implementation manner can form a resource group with a DNAI with a similarly located location, so that the determined second edge APP can quickly process the service request sent by the terminal device and provide a corresponding service.
  • the method before the first network device redirects the service request to the second edge APP, the method further includes: the first network device sending the indication information to the second network device, where the indication information is used to indicate the second
  • the network device establishes a path between the first edge UPF corresponding to the first edge APP and the second edge UPF corresponding to the second edge APP.
  • a path may be established between the first edge APP and the edge UPF corresponding to the second edge APP, so that the service packet sent by the terminal device reaches the second edge APP or the service message sent by the second edge APP.
  • the text arrives at the terminal device.
  • the method further includes: the first network device receiving the path update completion information from the second network device, the path update completion information being used to indicate The path establishment between the first edge UPF and the second edge UPF is completed.
  • the method further includes: the first network device sending a location request to the third network device, where the third network device acquires the terminal device
  • the accessed edge UPF further acquires a target resource group, the target resource group is a resource group including the first DNAI;
  • the first network device receives all or part of the parameters in the target resource group from the third network device;
  • the first network device is configured according to the target resource All or part of the parameters in the set determine a second DNAI; the first network device determines a second edge APP based on the second DNAI.
  • the method before the first network device redirects the service request to the second edge APP, the method further includes: the first network device determines that the first edge APP is unavailable.
  • the second aspect provides a service redirection method, where the method includes: the second network device receives the indication information from the first network device; and the second network device establishes, according to the indication information, the first edge UPF and the first edge corresponding to the first edge APP.
  • the second edge APP is a service edge APP for the first network device to redirect the service request of the terminal device when the first edge APP is unavailable, and the service request is used for requesting
  • the first edge APP related service the first edge APP corresponds to the first DNAI
  • the second edge APP corresponds to the second DNAI
  • the first DNAI can represent the deployment location of the first edge APP
  • the second DNAI can represent the deployment of the second edge APP Position
  • the deployment location represented by the first DNAI and the second DNAI meets a preset condition
  • the second edge APP is the same service provider in the edge APP corresponding to the second DNAI and has the same function.
  • the method provided by the second aspect may establish a path between the first edge APP and the edge UPF corresponding to the second edge APP, so that the service packet sent by the terminal device reaches the second edge APP or the service report sent by the second edge APP.
  • the text arrives at the terminal device.
  • the first DNAI and the second DNAI belong to the same resource group, and the base stations covered by the access UPF corresponding to any two DNAIs in one resource group are adjacent base stations; or, in a resource group
  • the tracking area identifiers of the access UPFs corresponding to any two DNAIs are the same or adjacent; or the transmission distance between the DCs corresponding to any two DNAIs in a resource group is less than or equal to a preset threshold.
  • the DNAIs whose locations are located close to each other can be grouped into a resource group, so that the determined second edge APP can quickly process the service request sent by the terminal device and provide corresponding services.
  • the service request is a service request of the first service
  • the second network device establishes, between the first edge UPF corresponding to the first edge APP and the second edge UPF corresponding to the second edge APP, according to the indication information.
  • the path includes: the second network device sends the first traffic distribution rule to the first edge UPF, where the first traffic distribution rule is: sending the service message of the first service of the terminal device received from the second edge UPF to the terminal device, The service packet of the first service received from the terminal device is sent to the second edge UPF; the second network device sends the second traffic distribution rule to the second edge UPF, where the second traffic distribution rule is: received from the first edge UPF
  • the service packet of the first service of the terminal device is sent to the second edge APP, and the service packet of the first service of the terminal device received from the second edge APP is sent to the first edge UPF.
  • the service packet sent by the terminal device reaches the second edge APP or the service packet sent by the second edge APP reaches the terminal device
  • the method further includes: The network device sends the path update completion information to the first network device, where the path update completion information is used to indicate that the path establishment between the first edge UPF and the second edge UPF is completed.
  • the method further includes: the second network device receives a location request from the third network device, the location request is used to request an edge UPF of the terminal device access; and the second network device sends the target to the third network device
  • the edge UPF and the target edge UPF are edge UPFs accessed by the terminal device.
  • a service redirection method includes: the third network device receives a target edge UPF from the second network device, the target edge UPF is an edge UPF accessed by the terminal device, and the third network device is configured according to the target edge
  • the UPF obtains a target resource group, the target resource group is a resource group including the first DNAI, the first DNAI can represent the deployment location of the first edge APP, and the third network device sends all or part of the parameters in the target resource group to the first network device.
  • the second edge APP is a service edge APP for the first network device to redirect the service request of the terminal device when the first edge APP is unavailable, and the service request is used for requesting and An edge APP related service
  • the first edge APP corresponds to the first DNAI
  • the second edge APP corresponds to the second DNAI
  • the second DNAI can represent the deployment position of the second edge APP, and the deployment position represented by the first DNAI and the second DNAI
  • the preset condition is met
  • the second edge APP is the same service provider in the edge APP corresponding to the second DNAI and has the same function.
  • Margin of APP may obtain the target resource group, and send all or part of the parameters in the target resource group to the first network device, so that the first network device determines the second edge APP.
  • the first DNAI and the second DNAI belong to the same resource group, and the base stations covered by the access UPF corresponding to any two DNAIs in one resource group are adjacent base stations; or, in a resource group
  • the tracking area identifiers of the access UPFs corresponding to any two DNAIs are the same or adjacent; or the transmission distance between the DCs corresponding to any two DNAIs in a resource group is less than or equal to a preset threshold.
  • the DNAIs whose locations are located close to each other can be grouped into a resource group, so that the determined second edge APP can quickly process the service request sent by the terminal device and provide corresponding services.
  • the method before the third network device receives the target edge UPF from the second network device, the method further includes: the third network device receives the location request from the first network device, and the location request is used to request the terminal device to connect The incoming edge UPF; the third network device sends a location request to the second network device; the third network device receives the target edge UPF from the second network device.
  • the method further includes the third network device determining that the first edge APP is unavailable.
  • the method further includes the third network device receiving the at least one resource group from the MEP manager.
  • a service redirection device having the function of implementing any of the methods provided by the first aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a service redirection device having the function of implementing any of the methods provided by the second aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software package includes one or more units corresponding to the functions described above.
  • a service redirection device having the function of implementing any of the methods provided by the third aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a service redirection apparatus comprising: a memory and a processor; the memory is configured to store a computer execution instruction, and the processor executes a computer-executed instruction stored in the memory to enable the apparatus to implement the first aspect Any method.
  • the device can exist in the form of a chip product.
  • a service redirection device comprising: a memory and a processor; the memory is configured to store a computer execution instruction, and the processor executes a computer-executed instruction stored in the memory to enable the device to implement the second aspect Any method.
  • the device can exist in the form of a chip product.
  • a service redirection device comprising: a memory and a processor; the memory is configured to store a computer execution instruction, and the processor executes a computer-executed instruction stored in the memory to enable the device to implement the third aspect Any method.
  • the device can exist in the form of a chip product.
  • the embodiment of the present application provides a computer readable storage medium, when run on a computer, to enable the computer to perform any one of the methods provided in the foregoing first aspect.
  • the embodiment of the present application provides a computer readable storage medium, when run on a computer, to enable the computer to perform any one of the methods provided in the second aspect above.
  • the embodiment of the present application provides a computer readable storage medium, when run on a computer, to enable the computer to perform any one of the methods provided in the foregoing third aspect.
  • the embodiment of the present application provides a computer program product comprising instructions, which when executed on a computer, enable the computer to perform any of the methods provided in the above first aspect.
  • the embodiment of the present application provides a computer program product comprising instructions, which when executed on a computer, enable the computer to perform any of the methods provided in the second aspect above.
  • the embodiment of the present application provides a computer program product comprising instructions, which when executed on a computer, enable the computer to perform any of the methods provided in the above third aspect.
  • FIG. 1 is a schematic diagram of an edge UPF performing service offloading in the prior art
  • FIG. 2 is a schematic structural diagram of a 5G network according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of an application scenario provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of hardware of a network device according to an embodiment of the present disclosure.
  • FIG. 5 is a flowchart of a service redirection method according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a neighboring base station according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a service flow according to an embodiment of the present application.
  • FIG. 8 is an interaction flowchart of a service redirection method according to an embodiment of the present application.
  • FIG. 9 is an interaction flowchart of a service redirection method according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a deployment edge APP and an edge UPF according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a method for constructing a resource group according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a service redirection device according to an embodiment of the present disclosure.
  • the 5G network may include multiple network functions (NF functions) entities: an authentication server. (authentication server function, AUSF for short) network element, access and mobility management function (AMF) network element, DN, unified data management (UDM) network element, policy control function (policy) Control function (referred to as PCF) network element, (radio) access network (radio access network, referred to as (R) AN) device, UPF network element, terminal device (in Figure 2, the terminal device is user equipment (user equipment, For example, UE) is drawn as an example, an application function (AF) network element, and a session management function (SMF) network element.
  • NF functions network functions
  • FIG. 2 is only an exemplary architecture diagram.
  • the 5G network architecture may include other network elements, for example, between the AF network element and the PCF network element.
  • the network exposure function (NEF) network element the NEF network element has the ability to open some service capabilities of the operator network to a third party. For example, the operator can perceive which base station the user is in, and provide this information based on the policy. Apply to the top (over the top, OTT for short).
  • the control plane (CP) function network element includes: a UDM network element, an AUSF network element, a PCF network element, an AMF network element, and an SMF network element.
  • the main functions of the (R) AN device include: providing a wireless connection; the main functions of the UPF network element include: routing and forwarding data packets, mobility anchors, and uplink classifiers to support routing service flows to the DN to support multi-homed packets. Data unit (PDU) session, etc.; DN can serve operators, Internet access or third-party services; AMF network element main functions include management user registration, reachability detection, SMF node selection, and mobile status.
  • PDU Data unit
  • DN can serve operators, Internet access or third-party services
  • AMF network element main functions include management user registration, reachability detection, SMF node selection, and mobile status.
  • SMF network element main functions include: control session establishment, modification and deletion, user face node selection, etc.
  • PCF network element main functions include: policy decision point, providing service data flow and application detection, gating, Rules for quality of service (QoS) and flow-based charging control
  • the main functions of the AF network element include: interacting with the core network of the 3rd generation partnership project (3GPP) to provide services.
  • 3GPP 3rd generation partnership project
  • AUSF network element main functions include: providing authentication services
  • the main functions of the UDM network element include: storing user subscription data.
  • the UE communicates with the AMF network element through the Next Generation interface 1 (N1 for short), and the (R) AN device communicates with the AMF network element through the N interface 2 (N2 for short), and the (R) AN device passes the N interface 3 (
  • the NFM network element communicates with the UPF network element.
  • the UPF network element communicates with the DN through the N interface 6 (N6 for short).
  • the AMF network element communicates with the SMF network element through the N interface 11 (N11 for short), and the AMF network element passes the N interface 8 (referred to as N8) communicates with the UDM network element.
  • the AMF network element communicates with the AUSF network element through the N interface 12 (N12 for short), and the AMF network element communicates with the PCF network element through the N interface 15 (N15 for short), and the SMF network element passes the N interface 7 ( The NMF communicates with the PCF network element.
  • the SMF network element communicates with the UPF network element through the N interface 4 (N4 for short).
  • the SMF network element communicates with the UDM network element through the N interface 10 (N10 for short), and the UDM network element passes through the N interface 13 (N13 for short) communicates with the AUSF network element, and the PCF network element communicates with the AF network element through the N interface 5 (N5 for short).
  • FIG. 3 is a schematic diagram of an application scenario of the method provided by the embodiment of the present application, where AN1 is an access network of deployment area 1, and when the terminal device is in deployment area 1, the network can be accessed through AN1.
  • AN2 is the access network of the deployment area 2, and the terminal device can access the network through the AN2 when it is in the deployment area 2.
  • the edge APP 11, the edge APP 12, and the edge APP 13 are edge APPs deployed in the deployment area 1, and the edge APP 21, the edge APP 22, and the edge APP 23 are edge APPs deployed in the deployment area 2.
  • the edge APP 11 and the edge APP 21 are applications of the company 1 having the same function.
  • the center APP 1 is an APP of the company 1 deployed on the DN or the non-edge.
  • the center APP 1 generally includes the functions of the edge APP 11 and the edge APP 21 .
  • the edge APP 12 and the edge APP 22 are applications of the company 2 having the same function.
  • the center APP 2 is an APP of the company 2 deployed on the DN or the non-edge.
  • the center APP 2 generally includes the functions of the edge APP 12 and the edge APP 22 .
  • the edge APP 13 and the edge APP 23 are applications of the company 3 having the same function.
  • the center APP 3 is an APP of the company 3 deployed on the DN or the non-edge.
  • the center APP 3 generally includes the functions of the edge APP 13 and the edge APP 23 .
  • the edge UPF1 can offload the service request sent by the terminal device through the AN1 to the edge APP11, the edge APP12, the edge APP13 or the central APP
  • the edge UPF2 can offload the service request sent by the terminal device through the AN2 to the edge APP21, the edge APP22, the edge APP23 or the center.
  • APP, edge UPF1 and edge UPF2 can be connected to the DN through an anchor-user plane function (A-UPF), and the A-UPF can be connected to the CP.
  • A-UPF anchor-user plane function
  • the edge APP11, the edge APP12, the edge APP13, and the edge UPF1 are one MEC node (denoted as MEC node 1), and the edge APP21, the edge APP22, the edge APP23, and the edge UPF2 are another MEC node (denoted as MEC node 2).
  • the architecture shown in Figure 3 is merely an exemplary application scenario diagram. In fact, there may be more MEC nodes in the network.
  • the MEC node (including the edge UPF and the edge APP) deployed in the data center (DC) and the AN list are associated with a data network access identifier (DNAI), exemplary, MEC.
  • DNAI data network access identifier
  • Node 1 will be associated with DNAI1
  • MEC node 2 will be associated with DNAI2
  • AN1 is AN in the AN1 associated with DNAI1
  • AN2 is AN in the AN list associated with DNAI2, and which AN in the AN list can be specifically connected to the edge UPF.
  • Network planning is determined.
  • the correspondence between the DNAI and the associated AN, the edge UPF, the edge APP, and the DC corresponding to the MEC node can be seen in Table 1.
  • FIG. 4 is a schematic diagram showing the hardware structure of a network device 40 according to an embodiment of the present application.
  • the network device 40 includes at least one processor 401, a communication bus 402, a memory 403, and at least one communication interface 404.
  • the network device 40 can be the first network device or the second network device or the third network device in the present application.
  • the processor 401 may be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the program of the present application. Execution of the integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 402 can include a path for communicating information between the components described above.
  • the communication interface 404 can be any device such as a transceiver for communicating with other devices or communication networks, such as Ethernet, AN, wireless local area networks (WLAN), and the like.
  • a transceiver for communicating with other devices or communication networks, such as Ethernet, AN, wireless local area networks (WLAN), and the like.
  • WLAN wireless local area networks
  • the memory 403 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or a device that can store information and instructions.
  • ROM read-only memory
  • RAM random access memory
  • Other types of dynamic storage devices may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical discs.
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • Storage optical storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures And any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 403 is used to store application code for executing the solution of the present application, and is controlled by the processor 401 for execution.
  • the processor 401 is configured to execute application code stored in the memory 403 to implement the method described below.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • network device 40 may include multiple processors, such as processor 401 and processor 408 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • network device 40 may also include an output device 405 and an input device 406.
  • the embodiment of the present application provides a service redirection method, as shown in FIG. 5, the method includes:
  • the first network device receives a service request from the terminal device, where the service request is used to request a service related to the first edge APP.
  • the first network device may be a network device that is loaded with the first center APP, and the first center APP and the first edge APP are APPs of the same service provider, and the first center APP may include the functions of the first edge APP,
  • a network device can be a network device in the DN.
  • the method provided by the embodiment of the present application is exemplified by using the first AN access network (see FIG. 7 in the following) as an example.
  • the first AN is connected to the first edge UPF.
  • the first edge UPF corresponding to the first edge APP may offload the service request sent by the terminal device by using the first AN to the first edge APP, if the first edge APP is unavailable.
  • the first edge UPF offloads the service request sent by the terminal device by using the first AN to the first center APP.
  • the first edge APP is unavailable, the second edge APP is available, and the first network device redirects the service request to the second edge APP.
  • the first edge APP corresponds to the first DNAI
  • the second edge APP corresponds to the second DNAI
  • the first DNAI can represent the deployment position of the first edge APP
  • the second DNAI can represent the deployment position of the second edge APP
  • the first DNAI and The second edge APP is a margin APP that is the same service provider as the first edge APP and has the same function in the edge APP corresponding to the second DNAI.
  • edge APP may be faulty, or the load of the edge APP reaches a certain threshold (for example, the server system resource consumption of the edge APP reaches a critical threshold, and the new computing service cannot be accepted). Or, other circumstances that cause the edge APP to be unable to process the business.
  • a certain threshold for example, the server system resource consumption of the edge APP reaches a critical threshold, and the new computing service cannot be accepted.
  • the first edge APP may be any edge APP, and the edge APP corresponding to the second DNAI may be all or part of the edge APP deployed in the deployment area corresponding to the second DNAI.
  • the first DNAI and the second DNAI belong to the same resource group, and the base stations covered by the access UPF corresponding to any two DNAIs in one resource group are neighboring base stations; or, in a resource group
  • the tracking area identity (TAI) covered by the access UPF corresponding to any two DNAIs is the same or adjacent; or the transmission distance between the DCs corresponding to any two DNAIs in a resource group Less than or equal to the preset threshold.
  • the condition satisfied between any two DNAIs in one resource group is a predetermined condition that is satisfied between the deployment positions characterized by the first DNAI and the second DNAI.
  • the edge APP corresponding to the second DNAI may include the edge APP21, the edge APP22, and the edge APP23, in which case, if the DNAI1 and the DNAI2 are a resource group
  • the DNAI in the first edge APP is the edge APP11, and the second edge APP is the edge APP21.
  • the resource group can be determined according to any of the following ways.
  • the base station covered by the corresponding access UPF is a resource group of the DNAI of the adjacent base station.
  • a resource group can be constructed with each DNAI as a reference point.
  • the base station i (i is an integer greater than 0 and less than or equal to 4) is a base station covered by the UPF corresponding to the DNAIi, the base station 1 is adjacent to the base station 2, the base station 3, and the base station 4, and the base station 2 and the base station 1 are The base station 3 is adjacent, the base station 3 is adjacent to the base station 1 and the base station 2, and the base station 4 is adjacent to the base station 1.
  • Table 2 For the resource group constructed with each DNAI as a reference point, see Table 2.
  • Resource group Reference point DNAI in the resource group 1 DNAI1 DNAI1, DNAI2, DNAI3, DNAI4 2 DNAI2 DNAI2, DNAI1, DNAI3 3 DNAI3 DNAI3, DNAI1, DNAI2 4 DNAI4 DNAI4, DNAI1
  • Mode 2 The corresponding or adjacent DNAIs of the corresponding access UPFs are grouped into one resource group.
  • DNAIs are DNAI1, DNAI2, DNAI3, DNAI4 and DNAI5, DNAI1, DNAI2 and DNAI4 have the same TAI, and DNAI3 and DNAI5 have the same TAI, and the resources are constructed according to DNAI. See Table 3 for the group.
  • Resource group DNAI in the resource group 1 DNAI1, DNAI2, DNAI4 2 DNAI3, DNAI5
  • Manner 3 The DNAI whose packet transmission distance between the corresponding DCs is less than or equal to a preset threshold is formed into a resource group.
  • a DC may correspond to a global positioning system (GPS) information or service area information of the DC, according to the GPS information or service area information of the two DCs, and combined with the transmission networking situation, Calculate the message transmission distance between the two DCs.
  • GPS global positioning system
  • the preset threshold may be determined according to the actual deployment of the edge APP or the network running status.
  • the packet transmission distance between DC1 and DC2 is less than a preset threshold
  • the packet transmission distance between DC3 and DC4 is less than a preset threshold.
  • the message transmission distance between DC1 and DC3, DC1 and DC4, DC2 and DC3, DC2 and DC4 is greater than a preset threshold.
  • Resource group DNAI in the resource group 1 DNAI1, DNAI2 2 DNAI3, DNAI4
  • the resource group constructed in the foregoing manner can form a resource group with the DNAIs whose locations are located close to each other, so that the determined second edge APP can quickly process the service request sent by the terminal device and provide corresponding services.
  • the service request of the service related to the first edge APP is received, the service request is redirected.
  • the center APP is not required to process the service related to the first edge APP, and the center APP can be reduced. pressure.
  • the first network device determines the second DNAI according to the resource group determined by adopting mode 1, and can satisfy the lower delay service compared with the resource group determined by adopting mode 2 and mode 3 to determine the second DNAI. demand.
  • first edge APP and the second edge APP are the edge APPs that are connected on different edge UPFs, referring to FIG. 7, it is required to establish between the first edge APP and the edge UPF corresponding to the second edge APP.
  • the path is such that the service packet sent by the terminal device reaches the second edge APP or the service packet sent by the second edge APP reaches the terminal device.
  • the method may further include:
  • the first network device sends the indication information to the second network device, where the indication information is used to indicate that the second network device establishes a path between the first edge UPF corresponding to the first edge APP and the second edge UPF corresponding to the second edge APP. .
  • the second network device may be an SMF.
  • the path may be a tunnel.
  • the second network device receives the indication information from the first network device.
  • the second network device establishes a path between the first edge UPF corresponding to the first edge APP and the second edge UPF corresponding to the second edge APP according to the indication information.
  • the method may further include:
  • the second network device sends the path update completion information to the first network device, where the path update completion information is used to indicate that the path establishment between the first edge UPF and the second edge UPF is completed.
  • the first network device receives the path update completion information from the second network device.
  • the service request is a service request of the first service
  • the step 13) may include: the second network device sends the first traffic distribution rule to the first edge UPF, where the first traffic distribution rule is: The service packet of the first service received by the terminal device is sent to the terminal device, and the service packet of the first service received from the terminal device is sent to the second edge UPF; the second network device sends the service packet to the second edge UPF.
  • a second offloading rule is: the service packet of the first service of the terminal device received from the first edge UPF is sent to the second edge APP, and the terminal device received from the second edge APP The service packet of a service is sent to the first edge UPF.
  • the first network device further needs to acquire all or part of the DNAI in the target resource group, so as to determine the second DNAI, and further determine the second edge APP, where the target resource group is the resource including the first DNAI. group.
  • the method may further include:
  • the first network device sends a location request to the third network device, where the location request is used to request the edge UPF accessed by the terminal device.
  • the third network device may be an NEF.
  • the third network device receives the location request from the first network device and sends a location request to the second network device.
  • the second network device receives the location request from the third network device, obtains the target edge UPF according to the location request, and the target edge UPF is the edge UPF accessed by the terminal device.
  • the target edge UPF is the first edge UPF.
  • the second network device sends the target edge UPF to the third network device.
  • the third network device receives the target edge UPF from the second network device, and acquires the target resource group according to the target edge UPF.
  • the third network device transmits all or part of the DNAI in the target resource group to the first network device.
  • the first network device receives all or part of the DNAI in the target resource group from the third network device and determines the second DNAI based on all or part of the DNAI in the target resource group.
  • the first network device determines the second edge APP based on the second DNAI.
  • the method may further include: the third network device receiving the at least one resource group from a mobile edge plant form (MEP) manager.
  • the resource group can be built by the MEP manager.
  • the first edge APP may be determined to be unavailable in any one of the following two manners.
  • Manner 1 The first network device determines that the first edge APP is unavailable.
  • the first edge APP may report the first edge device to the first network device, and the first network device determines that the first edge APP is unavailable according to the information reported by the first edge APP. In this case, the first network device can sense the first edge. The APP is not available, therefore, the third network device can transmit all of the DNAI in the target resource group to the first network device, and the first network device selects DNAI other than the first DNAI as the second DNAI.
  • Manner 2 The third network device determines that the first edge APP is unavailable.
  • the MEP manager can monitor the status of the first edge APP, and report the information that the first edge APP is unavailable to the third network device when the first edge APP is unavailable. In this case, the first network device does not perceive the first edge APP. The state, therefore, the third network device can transmit a portion of the DNAI in the target resource group to the first network device, the portion of the DNAI not including the first DNAI, and the first network device selects one of the DNAIs in the portion of the DNAI as the second DNAI.
  • one MAC node corresponds to one MEP
  • the MEP is used to manage MEC nodes
  • the MEP manager can manage multiple MEPs.
  • FIG. 8 and FIG. 9 each illustrate a service redirection method for exemplifying the method provided by the above embodiment.
  • the method can include:
  • the first edge APP reports the fault information to the first center APP.
  • the fault information may be reported to the center APP, and the center APP may determine which edge APP has failed according to the fault information.
  • the terminal device sends a service request of the first service to the first center APP.
  • the first service is a service related to the first edge APP.
  • the first center APP After receiving the service request, the first center APP sends a location request to the NEF.
  • the location request is used to request the edge UPF of the terminal device to access.
  • the edge UPF accessed by the terminal device is taken as an example of the first edge UPF.
  • the NEF sends the received location request to the SMF.
  • the SMF returns the first DNAI to the NEF according to the received location request.
  • the SMF may determine the first DNAI according to the first edge UPF accessed by the terminal device, where the first DNAI is the DNAI associated with the first edge APP and the first edge UPF.
  • the NEF acquires a target resource group according to the received first DNAI.
  • the NEF can obtain the resource group with the first DNAI as a reference point, and the resource group with the first DNAI as the reference point must include the first DNAI, when adopting the mode 2 or manner 3
  • the NEF can acquire the resource group containing the first DNAI.
  • the NEF sends all the DNAIs in the target resource group to the first center APP.
  • the NEF directs the first DNAI, the second DNAI, the third DNAI, and the fourth DNAI to the first center APP. send.
  • the NEF may send all the DNAIs in the target resource group to the first center APP, and the first edge APP determines that the first edge APP is faulty, and if the NEF can sense the first edge APP fault, The NEF may also transmit to the first center APP other DNAIs other than the first DNAI in the target resource group. Specifically, the NEF may determine the first edge APP fault by performing information interaction with the first center APP.
  • the first center APP determines, according to the fault information, that the first edge APP is unavailable, and selects the second DNAI from all the DNAIs in the target resource group, and determines the second edge APP corresponding to the second DNAI.
  • the first center APP sends the indication information to the SMF.
  • the indication information is used to indicate that the SMF establishes a path between the first edge UPF corresponding to the first edge APP and the second edge UPF corresponding to the second edge APP.
  • the SMF sends the first offload rule to the first edge UPF according to the indication information.
  • the first offloading rule is that the service packet of the first service of the terminal device received from the second edge UPF is sent to the terminal device, and the service packet of the first service received from the terminal device is sent to the second edge UPF. .
  • the SMF sends a second offload rule to the second edge UPF according to the indication information.
  • the second offloading rule is that the service packet of the first service of the terminal device received from the first edge UPF is sent to the second edge APP, and the service report of the first service of the terminal device received from the second edge APP is received. The text is sent to the first edge UPF.
  • the SMF sends path update completion information to the first center APP.
  • the path update completion information is used to indicate that the path establishment between the first edge UPF and the second edge UPF is completed.
  • the first center APP determines, according to the received path update completion information, that path establishment between the first edge UPF and the second edge UPF is completed.
  • the first center APP redirects the service request to the second edge APP.
  • the method includes:
  • the MEP monitors the status of the first edge APP. If the status is abnormal, the MEP reports the fault information to the NEF through the MEP manager.
  • the terminal device sends a service request of the first service to the first center APP.
  • the first service may be a service related to the first edge APP.
  • the first center APP After receiving the service request, the first center APP sends a location request to the NEF.
  • the NEF sends the received location request to the SMF.
  • the SMF returns, to the NEF, the first DNAI corresponding to the first edge APP according to the received location request.
  • the NEF acquires a target resource group according to the received first DNAI.
  • the NEF sends a part of the DNAI in the target resource group to the first center APP according to the fault information.
  • the first DNAI is not included in the partial DNAI.
  • the target resource group includes the first DNAI, the second DNAI, the third DNAI, and the fourth DNAI
  • the NEF directs the second DNAI, the third DNAI, and the fourth DNAI.
  • the first center APP sends.
  • the NEF can detect whether the first edge APP is faulty, the NEF can send the DNAI of the target resource group other than the first DNAI to the first center APP, and if the first center APP can sense whether the first edge APP is faulty, The NEF may also send all the DNAIs in the target resource group to the first center APP, and the first center APP determines the first edge APP fault. Specifically, the first center APP may determine whether the first edge APP is faulty by performing information interaction with the NEF.
  • the first center APP selects a second DNAI from a part of the DNAIs in the target resource group, and determines a second edge APP corresponding to the second DNAI.
  • the first center APP sends the indication information to the SMF.
  • the indication information is used to indicate that the second network device establishes a path between the first edge UPF corresponding to the first edge APP and the second edge UPF corresponding to the second edge APP.
  • the SMF sends the first offloading rule to the first edge UPF according to the indication information.
  • the first offloading rule is that the service packet of the first service of the terminal device received from the second edge UPF is sent to the terminal device, and the service packet of the first service received from the terminal device is sent to the second edge UPF. .
  • the SMF sends a second offload rule to the second edge UPF according to the indication information.
  • the second offloading rule is that the service packet of the first service of the terminal device received from the first edge UPF is sent to the second edge APP, and the service report of the first service of the terminal device received from the second edge APP is received. The text is sent to the first edge UPF.
  • the SMF sends path update completion information to the first center APP.
  • the path update completion information is used to indicate that the path establishment between the first edge UPF and the second edge UPF is completed.
  • the first center APP determines, according to the received path update completion information, that the path establishment between the first edge UPF and the second edge UPF is completed.
  • the first central APP redirects the service request to the second edge APP.
  • the MEP manager Before performing the above method, the MEP manager needs to construct a resource group and send the resource group to the third network device.
  • the deployment of the edge UPF may be completed by the slice manager. After the slice manager completes the deployment of the edge UPF, the slice manager may The MEP manager sends the first information (see below for details). After the edge APP is instantiated, the MEP can be registered with the MEP. The MEP sends the second information to the MEP manager (see below for details). The MEP manager uses the first information and The second information builds a resource group.
  • a method for constructing a resource group may include:
  • the slice manager deploys an edge UPF.
  • the slice manager sends the first information to the MEP manager.
  • the first information may be a correspondence between an edge UPF and a DC deployed by the slice manager.
  • the MEP manager receives the first information from the slice manager.
  • the MEP receives the registration message sent by the edge APP.
  • the edge APP is deployed in the DC. After the edge APP is deployed, the registration message can be sent to the MEP.
  • the registration message sent by an edge APP may include the application function-service-identifier of the edge APP, and may also include an edge. APP's internet protocol (IP) address.
  • IP internet protocol
  • the MEP obtains the DNAI of the MEP from the MEP manager.
  • the MEP associates the DNAI of the MEP with the edge APP registered with the MEP, and sends the second information to the MEP manager.
  • the correspondence between the edge APP and the DNAI of the MEP may be included in the second message.
  • the MEP is the MEP corresponding to the MEC1
  • the information included in the second message can be referred to Table 6. If the MEP is the MEP corresponding to the MEC2, the information included in the second message can be found in Table 7.
  • the MEP manager receives the second information from the MEP.
  • the MEP manager can receive the second information from multiple MEPs.
  • the MEP manager establishes a correspondence between the DNAI and the edge APP and the edge UPF according to the first information and the second information.
  • step 1108 the correspondence between DNAI and edge APP and edge UPF is shown in Table 8.
  • the DC relationship can also be included in the correspondence established by the MEP manager.
  • the DC-related context may be pre-configured in the MEP manager, and the DC-related context may include: DC-associated DNAI, TAI of the service area corresponding to the UPF deployed in the DC, and base station identifier (node id), DC Location information and the like, wherein the DC positioning information may be GPS coordinate information of the DC.
  • DC related context can be seen in Table 9.
  • the MEP manager can establish a correspondence between the DNAI and the edge APP and the edge UPF according to the DC-related DNAI and the first information and the second information.
  • the MEP manager constructs at least one resource group.
  • the MEP manager sends at least one resource group to the NEF.
  • the edge APP may be a mobile edge application
  • the edge UPF may be a mobile edge UPF
  • the AN may be a RAN.
  • the method provided by the embodiment of the present application implements resource sharing between MEC nodes, and deploys a high performance computing capability scenario of a graphics processing unit (GPU) in the future. If a resource group is not constructed, there may be insufficient area or regional excess. In the case, by building a resource group, the sharing of edge capabilities is well achieved. For some exception scenarios, a better reliability mechanism is also provided. When the local edge is unavailable, the nearest edge available resource can be used.
  • GPU graphics processing unit
  • the foregoing service redirection device includes a hardware structure and/or a software module corresponding to each function.
  • the present application 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 particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may divide the function module into the service redirection device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 12 is a schematic structural diagram of a service redirection device 120 involved in the foregoing embodiment, where the service redirection device 120 may be a first network device, The second network device or the third network device, the service redirection device 120 includes a processing unit 1201 and a communication unit 1202, and may further include a storage unit 1203.
  • the processing unit 1201 is configured to control and control the action of the first network device.
  • the processing unit 1201 is configured to support the first network device to perform the method shown in FIG. Processes 803, 808, 809, 813, and 814 in process, processes 903, 908, 909, 913, and 914 in FIG. 9, and/or actions performed by the first network device in other processes described in the embodiments of the present application .
  • the communication unit 1202 is configured to support communication of the first network device with other network entities, for example, with NEF or SMF in FIG. 8, and the storage unit 1203 is configured to store program codes and data of the first network device.
  • the processing unit 1201 is configured to control and control the action of the second network device.
  • the processing unit 1201 is configured to support the second network device to perform the processes 805, 810 in FIG. 812, the processes performed by the second network device in the process 905, 910-912, and/or other processes described in the embodiments of the present application.
  • the communication unit 1202 is configured to support communication of the second network device with other network entities, for example, with the first central APP or NEF in FIG. 8, and the storage unit 1203 is configured to store program codes and data of the second network device.
  • the processing unit 1201 is configured to perform control management on the actions of the third network device.
  • the processing unit 1201 is configured to support the third network device to perform the processes 804, 806 and FIG. 807, processes 904, 906, and 907 in FIG. 9, and/or actions performed by a third network device in other processes described in the embodiments of the present application.
  • the communication unit 1202 is configured to support communication of the third network device with other network entities, for example, with the first central APP or SMF in FIG. 9, and the storage unit 1203 is configured to store program codes and data of the third network device.
  • the processing unit 1201 may be a processor or a controller, and the communication unit 1202 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and may include one or more interfaces.
  • the storage unit 1203 may be a memory.
  • the service redirection device involved in the embodiment of the present application can refer to the network device shown in FIG. 4.
  • the processor 401 is configured to perform control management on the action of the first network device, for example, the processor 401 is configured to support the first network device to perform the method shown in FIG. 5, where the first network device is shown in FIG.
  • Processes 803, 808, 809, 813, and 814 in FIG. 8, processes 903, 908, 909, 913, and 914 in FIG. 9, and/or first network devices in other processes described in the embodiments of the present application The action performed.
  • the processor 401 is configured to perform control management on the action of the second network device.
  • the processor 401 is configured to support the second network device to perform the processes 805, 810 in FIG. 812, the processes performed by the second network device in the process 905, 910-912, and/or other processes described in the embodiments of the present application.
  • the processor 401 is configured to perform control management on the action of the third network device.
  • the processor 401 is configured to support the third network device to perform the processes 804, 806 and FIG. 807, processes 904, 906, and 907 in FIG. 9, and/or actions performed by a third network device in other processes described in the embodiments of the present application.
  • the embodiment of the present application also provides a computer readable storage medium, including instructions, when executed on a computer, causing a computer to execute the above method.
  • the embodiment of the present application also provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the above method.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)).
  • SSD Solid State Disk

Abstract

本申请公开了一种业务重定向方法及装置，用于降低中心APP的压力。业务重定向方法包括：第一网络设备从终端设备接收业务请求，业务请求用于请求与第一边缘APP相关的业务；第一边缘APP不可用，第二边缘APP可用，第一网络设备将业务请求重定向至第二边缘APP，第一边缘APP对应第一DNAI，第二边缘APP对应第二DNAI，第一DNAI能够表征第一边缘APP的部署位置，第二DNAI能够表征第二边缘APP的部署位置，第一DNAI和第二DNAI所表征的部署位置之间满足预设条件，第二边缘APP为第二DNAI对应的边缘APP中的、与第一边缘APP为相同服务商、且具备相同功能的边缘APP。本申请涉及通信技术领域。

Description

业务重定向方法及装置
本申请要求于2017年9月21日提交中国专利局、申请号为201710860147.1、发明名称为“业务重定向方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种业务重定向方法及装置。
背景技术
移动边缘计算(mobile edge computing，简称MEC)在距离用户的终端设备最近的接入网(access network，简称AN)内提供互联网技术(internet technology，简称IT)服务环境以及云计算能力，旨在进一步减小时延、提高网络运营效率、提高业务传送能力、优化用户体验。
现有的MEC的典型架构可参见图1，其中，边缘应用(application，简称APP)可以部署在边缘用户面功能(user plane function，简称UPF)附近，在边缘APP正常的情况下，边缘UPF会将终端设备通过AN发送的业务请求分流至边缘APP，若边缘APP异常，边缘UPF会将终端设备通过AN发送的业务请求分流至中心APP，中心APP可以部署在数据网络(data network，简称DN)中，由此可知，随着用户的数据流量的增大，在边缘APP异常的情况下，会大大的增加中心APP的压力。
发明内容
本申请实施例提供了一种业务重定向方法及装置，用于降低中心APP的压力。
为达到上述目的，本申请实施例提供如下技术方案：
第一方面，提供了一种业务重定向方法，该方法包括：第一网络设备从终端设备接收业务请求，业务请求用于请求与第一边缘APP相关的业务；第一边缘APP不可用，第二边缘APP可用，第一网络设备将业务请求重定向至第二边缘APP，第一边缘APP对应第一DNAI，第二边缘APP对应第二DNAI，第一DNAI能够表征第一边缘APP的部署位置，第二DNAI能够表征第二边缘APP的部署位置，第一DNAI和第二DNAI所表征的部署位置之间满足预设条件，第二边缘APP为第二DNAI对应的边缘APP中的、与第一边缘APP为相同服务商、且具备相同功能的边缘APP。第一方面提供的方法，第一网络设备在第一边缘APP不可用，第二边缘APP可用的情况下，当接收到与第一边缘APP相关的业务的业务请求时，将业务请求重定向至第二边缘APP，由于第二边缘APP与第一边缘APP为相同服务商、且具备相同功能的边缘APP，因此，不需要中心APP去处理与第一边缘APP相关的业务，能够降低中心APP的压力。
在一种可能的设计中，第一DNAI和第二DNAI属于同一个资源组，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的基站为相邻基站；或者，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的跟踪区标识相同或相邻；或者，一个资源组中的任意两个DNAI对应的DC之间的报文传输距离小于或等于预设阈值。该种可能的实现方式，能够将表 征的部署位置距离较近的DNAI组成一个资源组，从而使得确定的第二边缘APP能够快速的处理终端设备发送的业务请求并提供相应的服务。
在一种可能的设计中，在第一网络设备将业务请求重定向至第二边缘APP之前，该方法还包括：第一网络设备向第二网络设备发送指示信息，指示信息用于指示第二网络设备建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径。该种可能的实现方式，可以在第一边缘APP和第二边缘APP对应的边缘UPF之间建立路径，从而使得终端设备发送的业务报文到达第二边缘APP或者第二边缘APP发送的业务报文到达终端设备。
在一种可能的设计中，在第一网络设备向第二网络设备发送指示信息之后，该方法还包括：第一网络设备从第二网络设备接收路径更新完成信息，路径更新完成信息用于指示第一边缘UPF与第二边缘UPF之间的路径建立完成。
在一种可能的设计中，在第一网络设备向第二网络设备发送指示信息之前，该方法还包括：第一网络设备向第三网络设备发送位置请求，用于第三网络设备获取终端设备接入的边缘UPF进而获取目标资源组，目标资源组为包括第一DNAI的资源组；第一网络设备从第三网络设备接收目标资源组中的全部或部分参数；第一网络设备根据目标资源组中的全部或部分参数确定第二DNAI；第一网络设备根据第二DNAI确定第二边缘APP。
在一种可能的设计中，在第一网络设备将业务请求重定向至第二边缘APP之前，该方法还包括：第一网络设备确定第一边缘APP不可用。
第二方面，提供了一种业务重定向方法，该方法包括：第二网络设备从第一网络设备接收指示信息；第二网络设备根据指示信息建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径，第二边缘APP为第一网络设备在第一边缘APP不可用时为终端设备的业务请求进行重定向的服务边缘APP，业务请求用于请求与第一边缘APP相关的业务，第一边缘APP对应第一DNAI，第二边缘APP对应第二DNAI，第一DNAI能够表征第一边缘APP的部署位置，第二DNAI能够表征第二边缘APP的部署位置，第一DNAI和第二DNAI所表征的部署位置之间满足预设条件，第二边缘APP为第二DNAI对应的边缘APP中的、与第一边缘APP为相同服务商、且具备相同功能的边缘APP。第二方面提供的方法，可以在第一边缘APP和第二边缘APP对应的边缘UPF之间建立路径，从而使得终端设备发送的业务报文到达第二边缘APP或者第二边缘APP发送的业务报文到达终端设备。
在一种可能的设计中，第一DNAI和第二DNAI属于同一个资源组，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的基站为相邻基站；或者，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的跟踪区标识相同或相邻；或者，一个资源组中的任意两个DNAI对应的DC之间的报文传输距离小于或等于预设阈值。该种可能的实现方式，能够将表征的部署位置距离较近的DNAI组成一个资源组，从而使得确定的第二边缘APP能够快速的处理终端设备发送的业务请求并提供相应的服务。
在一种可能的设计中，业务请求为第一业务的业务请求，第二网络设备根据指示信息建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径，包括：第二网络设备向第一边缘UPF发送第一分流规则，第一分流规则为：将从第二边缘UPF接收到的终端设备的第一业务的业务报文向终端设备发送，将从终端设备接收到的第一业务的业务报文向第二边缘UPF发送；第二网络设备向第二边缘UPF发送第二分流规则，第二 分流规则为：将从第一边缘UPF接收到的终端设备的第一业务的业务报文向第二边缘APP发送，将从第二边缘APP接收到的终端设备的第一业务的业务报文向第一边缘UPF发送。该种可能的实现方式，可以使得终端设备发送的业务报文到达第二边缘APP或者第二边缘APP发送的业务报文到达终端设备。
在一种可能的设计中，在第二网络设备根据指示信息建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径之后，该方法还包括：第二网络设备向第一网络设备发送路径更新完成信息，路径更新完成信息用于指示第一边缘UPF与第二边缘UPF之间的路径建立完成。
在一种可能的设计中，该方法还包括：第二网络设备从第三网络设备接收位置请求，位置请求用于请求终端设备接入的边缘UPF；第二网络设备向第三网络设备发送目标边缘UPF，目标边缘UPF为终端设备接入的边缘UPF。
第三方面，提供了一种业务重定向方法，该方法包括：第三网络设备从第二网络设备接收目标边缘UPF，目标边缘UPF为终端设备接入的边缘UPF；第三网络设备根据目标边缘UPF获取目标资源组，目标资源组为包括第一DNAI的资源组，第一DNAI能够表征第一边缘APP的部署位置；第三网络设备向第一网络设备发送目标资源组中的全部或部分参数，用于第一网络设备确定第二边缘APP，第二边缘APP为第一网络设备在第一边缘APP不可用时为终端设备的业务请求进行重定向的服务边缘APP，业务请求用于请求与第一边缘APP相关的业务，第一边缘APP对应第一DNAI，第二边缘APP对应第二DNAI，第二DNAI能够表征第二边缘APP的部署位置，第一DNAI和第二DNAI所表征的部署位置之间满足预设条件，第二边缘APP为第二DNAI对应的边缘APP中的、与第一边缘APP为相同服务商、且具备相同功能的边缘APP。第三方面提供的方法，第三网络设备可以获取目标资源组，并将该目标资源组中的全部或部分参数向第一网络设备发送，从而使得第一网络设备确定第二边缘APP。
在一种可能的设计中，第一DNAI和第二DNAI属于同一个资源组，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的基站为相邻基站；或者，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的跟踪区标识相同或相邻；或者，一个资源组中的任意两个DNAI对应的DC之间的报文传输距离小于或等于预设阈值。该种可能的实现方式，能够将表征的部署位置距离较近的DNAI组成一个资源组，从而使得确定的第二边缘APP能够快速的处理终端设备发送的业务请求并提供相应的服务。
在一种可能的设计中，在第三网络设备从第二网络设备接收目标边缘UPF之前，该方法还包括：第三网络设备从第一网络设备接收位置请求，位置请求用于请求终端设备接入的边缘UPF；第三网络设备向第二网络设备发送位置请求；第三网络设备从第二网络设备接收目标边缘UPF。
在一种可能的设计中，该方法还包括：第三网络设备确定第一边缘APP不可用。
在一种可能的设计中，该方法还包括：第三网络设备从MEP管理器接收至少一个资源组。
第四方面，提供了一种业务重定向装置，该装置具有实现第一方面提供的任意一种方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。
第五方面，提供了一种业务重定向装置，该装置具有实现第二方面提供的任意一种方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包 括一个或多个与上述功能相对应的单元。
第六方面，提供了一种业务重定向装置，该装置具有实现第三方面提供的任意一种方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。
第七方面，提供了一种业务重定向装置，该装置包括：存储器和处理器；存储器用于存储计算机执行指令，处理器执行存储器存储的计算机执行指令，以使该装置实现第一方面提供的任意一种方法。该装置可以以芯片的产品形态存在。
第八方面，提供了一种业务重定向装置，该装置包括：存储器和处理器；存储器用于存储计算机执行指令，处理器执行存储器存储的计算机执行指令，以使该装置实现第二方面提供的任意一种方法。该装置可以以芯片的产品形态存在。
第九方面，提供了一种业务重定向装置，该装置包括：存储器和处理器；存储器用于存储计算机执行指令，处理器执行存储器存储的计算机执行指令，以使该装置实现第三方面提供的任意一种方法。该装置可以以芯片的产品形态存在。
第十方面，本申请实施例提供了一种计算机可读存储介质，当其在计算机上运行时，使得计算机可以执行上述第一方面中提供的任意一种方法。
第十一方面，本申请实施例提供了一种计算机可读存储介质，当其在计算机上运行时，使得计算机可以执行上述第二方面中提供的任意一种方法。
第十二方面，本申请实施例提供了一种计算机可读存储介质，当其在计算机上运行时，使得计算机可以执行上述第三方面中提供的任意一种方法。
第十三方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面中提供的任意一种方法。
第十四方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第二方面中提供的任意一种方法。
第十五方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第三方面中提供的任意一种方法。
第四方面至第十五方面中任一种设计方式所带来的技术效果可参见第一方面至第三方面中不同设计方式所带来的技术效果，此处不再赘述。
附图说明
图1为现有技术中的一种边缘UPF进行业务分流的示意图；
图2为本申请实施例提供的一种5G网络的组成架构示意图；
图3为本申请实施例提供的一种应用场景示意图；
图4为本申请实施例提供的一种网络设备的硬件组成示意图；
图5为本申请实施例提供的一种业务重定向方法的流程图；
图6为本申请实施例提供的一种相邻基站的示意图；
图7为本申请实施例提供的一种业务流的示意图；
图8为本申请实施例提供的一种业务重定向方法的交互流程图；
图9为本申请实施例提供的一种业务重定向方法的交互流程图；
图10为本申请实施例提供的部署边缘APP和边缘UPF的示意图；
图11为本申请实施例提供的一种构建资源组的方法示意图；
图12为本申请实施例提供的一种业务重定向装置的组成示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本申请的描述中，“多个”是指两个或多于两个。
具体的，本申请实施例提供的方法可以应用于图2所示的5G网络，如图2所示，该5G网络可以包括下述多个网络功能(network functions，简称NF)实体：鉴权服务器功能(authentication server function，简称AUSF)网元、接入和移动管理功能(mobility management function，简称AMF)网元、DN、统一数据管理(unified data management，简称UDM)网元、策略控制功能(policy control function，简称PCF)网元、(无线)接入网((radio)access network，简称(R)AN)设备、UPF网元、终端设备(图2中以终端设备为用户设备(user equipment，简称UE)为例进行绘制)、应用功能(application function，简称AF)网元、会话管理功能(session management function，简称SMF)网元。可以理解的是，图2仅为示例性架构图，除图2所示网元之外，该5G网络架构还可以包括其他网元，例如，在AF网元和PCF网元之间还可以包括网络开放功能(network exposure function，简称NEF)网元，NEF网元具备将运营商网络具备的一些业务能力向第三方开放，比如运营商可以感知用户在哪个基站哪个位置，将此信息基于策略提供给上层(over the top，简称OTT)应用。
控制面(control plane，简称CP)功能网元包括：UDM网元、AUSF网元、PCF网元、AMF网元和SMF网元。
具体的，(R)AN设备主要功能包括：提供无线连接；UPF网元主要功能包括：使数据包路由和转发、移动性锚点、上行分类器来支持路由业务流到DN来支持多归属分组数据单元(packet data unit，简称PDU)会话等；DN可以为运营商服务，互联网接入或者第三方服务；AMF网元主要功能包含管理用户注册、可达性检测、SMF节点的选择、移动状态转换管理等；SMF网元主要功能包括：控制会话的建立、修改和删除，用户面节点的选择等；PCF网元主要功能包括：策略决策点，提供基于业务数据流和应用检测，门控，服务质量(quality of service，简称QoS)和基于流的计费控制等规则；AF网元主要功能包括：与第三代合作伙伴计划(3rd generation partnership project，简称3GPP)核心网交互来提供服务，来影响业务流路由、接入网能力开放、策略控制等；AUSF网元主要功能包括：提供鉴权服务；UDM网元主要功能包括：存储用户签约数据。
UE通过下一代网络(Next generation)接口1(简称N1)与AMF网元通信，(R)AN设备通过N接口2(简称N2)与AMF网元通信，(R)AN设备通过N接口3(简称N3)与UPF网元通信，UPF网元通过N接口6(简称N6)与DN通信，AMF网元通过N接口11(简称N11)与SMF网元通信，AMF网元通过N接口8(简称N8)与UDM网元通信，AMF网元通过N接口12(简称N12)与AUSF网元通信，AMF网元通过N接口15(简称N15)与PCF网元通信，SMF网元通过N接口7(简称N7)与PCF网元通信，SMF网元通过N接口4(简称N4)与UPF网元通信，SMF网元通过N接口10(简称N10)与UDM网元通信，UDM网元通过N接口13(简称N13)与AUSF网元通信，PCF网元通过N接口5(简称N5)与AF网元通信。
示例性的，图3示出了本申请实施例提供的方法的一种应用场景示意图，其中，AN1为部署区域1的接入网，终端设备处于部署区域1内时可以通过AN1接入网络，AN2为部署区域2的接入网，终端设备处于部署区域2内时可以通过AN2接入网络。边缘APP11、边缘APP12和边缘APP13为部署在部署区域1的边缘APP，边缘APP21、边缘APP22和边缘APP23为部署在部署区域2的边缘APP。边缘APP11和边缘APP21为公司1的、具备相同功能的应用，中心APP1为部署在DN或非边缘的公司1的APP，中心APP1一般包含边缘APP11和边缘APP21的功能。边缘APP12和边缘APP22为公司2的、具备相同功能的应用，中心APP2为部署在DN或非边缘的公司2的APP，中心APP2一般包含边缘APP12和边缘APP22的功能。边缘APP13和边缘APP23为公司3的、具备相同功能的应用，中心APP3为部署在DN或非边缘的公司3的APP，中心APP3一般包含边缘APP13和边缘APP23的功能。
边缘UPF1可以将终端设备通过AN1发送的业务请求分流至边缘APP11、边缘APP12、边缘APP13或中心APP，边缘UPF2可以将终端设备通过AN2发送的业务请求分流至边缘APP21、边缘APP22、边缘APP23或中心APP，边缘UPF1和边缘UPF2可以通过锚点用户面功能(anchor-user plane function，简称A-UPF)连接至DN，A-UPF可以与CP连接。
其中，边缘APP11、边缘APP12、边缘APP13以及边缘UPF1为一个MEC节点(记为MEC节点1)，边缘APP21、边缘APP22、边缘APP23以及边缘UPF2为另一个MEC节点(记为MEC节点2)，图3所示的架构仅仅为一种示例性的应用场景示意图，实际上，网络中可以有更多个MEC节点。部署到数据中心(data center，简称DC)的MEC节点(包括其中的边缘UPF和边缘APP)和AN列表会关联一个数据网络接入标识(data network access identifier，简称DNAI)，示例性的，MEC节点1会关联到DNAI1，MEC节点2会关联DNAI2，则AN1为DNAI1关联的AN列表中的AN，AN2为DNAI2关联的AN列表中的AN，边缘UPF具体与AN列表中的哪个AN连接可以通过网络规划确定。
示例性的，DNAI与关联的AN、边缘UPF、边缘APP，以及MEC节点对应的DC的对应关系可以参见表1。
表1
Figure PCTCN2018104327-appb-000001
如图4所示，为本申请实施例提供的一种网络设备40的硬件结构示意图，该网络设备40包括至少一个处理器401，通信总线402，存储器403以及至少一个通信接口404。该网络设备40可以是本申请中的第一网络设备或第二网络设备或第三网络设备。
处理器401可以是一个通用中央处理器(central processing unit，简称CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，简称ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线402可包括一通路，在上述组件之间传送信息。
通信接口404，可以为任何收发器一类的装置，用于与其他设备或通信网络通信，如以 太网，AN，无线局域网(wireless local area networks，简称WLAN)等。
存储器403可以是只读存储器(read-only memory，简称ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，简称RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，简称EEPROM)、只读光盘(compact disc read-only memory，简称CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器403用于存储执行本申请方案的应用程序代码，并由处理器401来控制执行。处理器401用于执行存储器403中存储的应用程序代码，从而实现下文中描述的方法。
在具体实现中，作为一种实施例，处理器401可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
在具体实现中，作为一种实施例，网络设备40可以包括多个处理器，例如图4中的处理器401和处理器408。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，网络设备40还可以包括输出设备405和输入设备406。
本申请实施例提供了一种业务重定向方法，如图5所示，该方法包括：
501、第一网络设备从终端设备接收业务请求，业务请求用于请求与第一边缘APP相关的业务。
其中，第一网络设备可以为装载有第一中心APP的网络设备，第一中心APP与第一边缘APP为相同服务商的APP，并且第一中心APP可以包含第一边缘APP具备的功能，第一网络设备可以为DN中的网络设备。
在本申请实施例中，以终端设备通过第一AN接入网络(可参见下文中的图7)为例对本申请实施例提供的方法作示例性说明，第一AN与第一边缘UPF连接。需要说明的是，在第一边缘APP可用的情况下，第一边缘APP对应的第一边缘UPF会将终端设备通过第一AN发送的业务请求分流至第一边缘APP，若第一边缘APP不可用，第一边缘UPF会将终端设备通过第一AN发送的业务请求分流至第一中心APP。
502、第一边缘APP不可用，第二边缘APP可用，第一网络设备将业务请求重定向至第二边缘APP。
其中，第一边缘APP对应第一DNAI，第二边缘APP对应第二DNAI，第一DNAI能够表征第一边缘APP的部署位置，第二DNAI能够表征第二边缘APP的部署位置，第一DNAI和第二DNAI所表征的部署位置之间满足预设条件，第二边缘APP为第二DNAI对应的边缘APP中的、与第一边缘APP为相同服务商、且具备相同功能的边缘APP。
一个边缘APP不可用可以是指该边缘APP发生故障，或者，该边缘APP的负荷达到一定的阈值(例如，该边缘APP所在的服务器系统资源消耗达到临界门限，已经无法接纳新的计算服务)，或者，其他导致该边缘APP无法处理业务的情况。
其中，第一边缘APP可以为任意一个边缘APP，第二DNAI对应的边缘APP可以为第二DNAI对应的部署区域中部署的全部或部分边缘APP。
可选的，所述第一DNAI和所述第二DNAI属于同一个资源组，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的基站为相邻基站；或者，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的跟踪区标识(tracking area identity，简称TAI)相同或相邻；或者，一个资源组中的任意两个DNAI对应的DC之间的报文传输距离小于或等于预设阈值。一个资源组中的任意两个DNAI之间满足的条件即第一DNAI和第二DNAI所表征的部署位置之间满足的预设条件。
示例性的，基于表1所示的示例，若第二DNAI为DNAI2，则第二DNAI对应的边缘APP可以包括边缘APP21、边缘APP22和边缘APP23，该情况下，若DNAI1和DNAI2为一个资源组中的DNAI，且第一边缘APP为边缘APP11，则第二边缘APP为边缘APP21。
示例性的，可以根据以下方式中的任意一种方式确定资源组。
方式1、将对应的接入UPF所覆盖的基站为相邻基站的DNAI组成一个资源组。
在具体实现时，可以以每个DNAI为参考点构建资源组。
示例性的，参见图6，基站i(i为大于0小于等于4的整数)为DNAIi对应的UPF覆盖的基站，基站1与基站2、基站3和基站4相邻，基站2与基站1和基站3相邻，基站3与基站1和基站2相邻，基站4与基站1相邻。则以各个DNAI为参考点构建的资源组可以参见表2。
表2
资源组 参考点 资源组中的DNAI
1 DNAI1 DNAI1、DNAI2、DNAI3、DNAI4
2 DNAI2 DNAI2、DNAI1、DNAI3
3 DNAI3 DNAI3、DNAI1、DNAI2
4 DNAI4 DNAI4、DNAI1
方式2、将对应的接入UPF的TAI相同或相邻的DNAI组成一个资源组。
示例性的，若有5个接入UPF，其对应的DNAI分别为DNAI1、DNAI2、DNAI3、DNAI4和DNAI5，DNAI1、DNAI2和DNAI4的TAI相同，DNAI3和DNAI5的TAI相同，则根据DNAI构建的资源组可以参见表3。
表3
资源组 资源组中的DNAI
1 DNAI1、DNAI2、DNAI4
2 DNAI3、DNAI5
方式3、将对应的DC之间的报文传输距离小于或等于预设阈值的DNAI组成一个资源组。
需要说明的是，一个DC可以对应一个该DC的全球定位系统(global positioning system，简称GPS)信息或服务区信息，根据两个DC的GPS信息或服务区信息，并结合传输组网情况，可以计算出两个DC之间的报文传输距离。
其中，预设阈值可以根据实际的边缘APP的部署情况或网络运行状况等确定。
示例性的，若有4个DC，分别为DC1、DC2、DC3和DC4，DC1和DC2之间的报文传输距离小于预设阈值，DC3和DC4之间的报文传输距离小于预设阈值，DC1和DC3、DC1和DC4、DC2和DC3、DC2和DC4之间的报文传输距离均大于预设阈值，若四个DC对应 的DNAI分别为DNAI1、DNAI2、DNAI3和DNAI4，则根据DNAI构建的资源组可以参见表4。
表4
资源组 资源组中的DNAI
1 DNAI1、DNAI2
2 DNAI3、DNAI4
通过上述方式构建的资源组，能够将表征的部署位置距离较近的DNAI组成一个资源组，从而使得确定的第二边缘APP能够快速的处理终端设备发送的业务请求并提供相应的服务。
本申请实施例提供的方法，第一网络设备在第一边缘APP不可用，第二边缘APP可用的情况下，当接收到与第一边缘APP相关的业务的业务请求时，将业务请求重定向至第二边缘APP，由于第二边缘APP与第一边缘APP为相同服务商、且具备相同功能的边缘APP，因此，不需要中心APP去处理与第一边缘APP相关的业务，能够降低中心APP的压力。
对于有些应用，比如一些超低时延要求的应用，在构建资源组时，对业务会有较为严格的时延要求，因此资源组内的相邻关系约束的会更严格。上述三种方式中，第一网络设备根据采用方式1确定的资源组确定第二DNAI，与采用方式2和方式3确定的资源组确定第二DNAI相比，可以满足更低延时的业务的需求。
需要说明的是，由于第一边缘APP和第二边缘APP为不同的边缘UPF上对接的边缘APP，因此，参见图7，需要在第一边缘APP和第二边缘APP对应的边缘UPF之间建立路径，从而使得终端设备发送的业务报文到达第二边缘APP或者第二边缘APP发送的业务报文到达终端设备。
可选的，在步骤502之前，该方法还可以包括：
11)第一网络设备向第二网络设备发送指示信息，指示信息用于指示第二网络设备建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径。
其中，第二网络设备可以为SMF，示例性的，路径可以为隧道。
12)第二网络设备从第一网络设备接收指示信息。
13)第二网络设备根据指示信息建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径。
可选的，在步骤13)之后步骤502之前，该方法还可以包括：
14)第二网络设备向第一网络设备发送路径更新完成信息，路径更新完成信息用于指示第一边缘UPF与第二边缘UPF之间的路径建立完成。
15)第一网络设备从第二网络设备接收路径更新完成信息。
可选的，业务请求为第一业务的业务请求，步骤13)在具体实现时可以包括：第二网络设备向第一边缘UPF发送第一分流规则，第一分流规则为：将从第二边缘UPF接收到的终端设备的第一业务的业务报文向终端设备发送，将从终端设备接收到的第一业务的业务报文向第二边缘UPF发送；第二网络设备向第二边缘UPF发送第二分流规则，第二分流规则为：将从第一边缘UPF接收到的终端设备的第一业务的业务报文向第二边缘APP发送，将从第二边缘APP接收到的终端设备的第一业务的业务报文向第一边缘UPF发送。
需要说明的是，在步骤502之前，第一网络设备还需要获取目标资源组中的全部或部分DNAI，以便确定第二DNAI，进而确定第二边缘APP，目标资源组为包括第一DNAI的资源 组。
可选的，该方法还可以包括：
21)第一网络设备向第三网络设备发送位置请求，位置请求用于请求终端设备接入的边缘UPF。
其中，第三网络设备可以为NEF。
22)第三网络设备从第一网络设备接收位置请求，并向第二网络设备发送位置请求。
23)第二网络设备从第三网络设备接收位置请求，根据位置请求获取目标边缘UPF，目标边缘UPF为终端设备接入的边缘UPF。在该实施例中，目标边缘UPF即第一边缘UPF。
24)第二网络设备向第三网络设备发送目标边缘UPF。
25)第三网络设备从第二网络设备接收目标边缘UPF，并根据目标边缘UPF获取目标资源组。
26)第三网络设备向第一网络设备发送目标资源组中的全部或部分DNAI。
27)第一网络设备从第三网络设备接收目标资源组中的全部或部分DNAI，并根据目标资源组中的全部或部分DNAI确定第二DNAI。
28)第一网络设备根据第二DNAI确定第二边缘APP。
在步骤25)之前，该方法还可以包括：所述第三网络设备从移动边缘平台(mobile edge plantform，简称MEP)管理器接收至少一个资源组。其中，资源组可以由MEP管理器构建。
可选的，本申请实施例在具体实现时，可以通过以下两种方式中的任意一种方式确定第一边缘APP不可用。
方式一、第一网络设备确定第一边缘APP不可用。
第一边缘APP可以在不可用时向第一网络设备上报，第一网络设备根据第一边缘APP上报的信息确定第一边缘APP不可用，该情况下，由于第一网络设备可以感知到第一边缘APP不可用，因此，第三网络设备可以向第一网络设备发送目标资源组中的全部DNAI，第一网络设备选择第一DNAI以外的DNAI作为第二DNAI。
方式二、第三网络设备确定第一边缘APP不可用。
MEP管理器可以监测第一边缘APP的状态，当第一边缘APP不可用时，向第三网络设备上报第一边缘APP不可用的信息，该情况下，由于第一网络设备不感知第一边缘APP的状态，因此，第三网络设备可以向第一网络设备发送目标资源组中的部分DNAI，该部分DNAI不包括第一DNAI，第一网络设备选择该部分DNAI中的一个DNAI作为第二DNAI。
需要说明的是，一个MAC节点对应一个MEP，MEP用于管理MEC节点，MEP管理器可以管理多个MEP。
图8和图9各示出了一种业务重定向方法，用于对上述实施例提供的方法做示例性说明。
参见图8，该方法可以包括：
801、第一边缘APP向第一中心APP上报故障信息。
具体的，当边缘APP故障时，可以向中心APP上报故障信息，中心APP可以根据故障信息确定哪个边缘APP发生了故障。
802、终端设备向第一中心APP发送第一业务的业务请求。
第一业务为与第一边缘APP相关的业务。
803、第一中心APP接收到业务请求后，向NEF发送位置请求。
位置请求用于请求终端设备接入的边缘UPF，在该实施例中，以终端设备接入的边缘UPF 为第一边缘UPF为例进行示例性说明。
804、NEF将接收到的位置请求向SMF发送。
805、SMF根据接收到的位置请求向NEF返回第一DNAI。
步骤805在实现时，SMF可以根据终端设备接入的第一边缘UPF确定第一DNAI，第一DNAI为与第一边缘APP和第一边缘UPF相关联的DNAI。
806、NEF根据接收到的第一DNAI获取目标资源组。
具体的，当采用方式1确定资源组时，NEF可以获取以第一DNAI为参考点的资源组，以第一DNAI为参考点的资源组必定是包含第一DNAI的，当采用方式2或方式3确定资源组时，NEF可以获取包含第一DNAI的资源组。
807、NEF向第一中心APP发送目标资源组中的全部DNAI。
示例性的，若目标资源组中包括第一DNAI、第二DNAI、第三DNAI和第四DNAI，则NEF将第一DNAI、第二DNAI、第三DNAI和第四DNAI都向第一中心APP发送。
由于NEF不感知第一边缘APP是否故障，因此，NEF可以向第一中心APP发送目标资源组中的全部DNAI，由第一中心APP确定第一边缘APP故障，若NEF可以感知第一边缘APP故障，NEF也可以向第一中心APP发送目标资源组中的除第一DNAI之外的其他DNAI。具体的，NEF可以通过与第一中心APP进行信息交互确定第一边缘APP故障。
808、第一中心APP根据故障信息确定第一边缘APP不可用，并从目标资源组中的全部DNAI中选择第二DNAI，确定第二DNAI对应的第二边缘APP。
809、第一中心APP向SMF发送指示信息。
指示信息用于指示SMF建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径。
810、SMF根据指示信息向第一边缘UPF发送第一分流规则。
第一分流规则为：将从第二边缘UPF接收到的终端设备的第一业务的业务报文向终端设备发送，将从终端设备接收到的第一业务的业务报文向第二边缘UPF发送。
811、SMF根据指示信息向第二边缘UPF发送第二分流规则。
第二分流规则为：将从第一边缘UPF接收到的终端设备的第一业务的业务报文向第二边缘APP发送，将从第二边缘APP接收到的终端设备的第一业务的业务报文向第一边缘UPF发送。
812、SMF向第一中心APP发送路径更新完成信息。
路径更新完成信息用于指示第一边缘UPF与第二边缘UPF之间的路径建立完成。
813、第一中心APP根据接收到的路径更新完成信息确定第一边缘UPF与第二边缘UPF之间的路径建立完成。
814、第一中心APP将业务请求重定向至第二边缘APP。
参见图9，该方法包括：
901、MEP监测第一边缘APP的状态，若状态异常，MEP通过MEP管理器向NEF上报故障信息。
902、终端设备向第一中心APP发送第一业务的业务请求。
第一业务可以为与第一边缘APP相关的业务。
903、第一中心APP接收到业务请求后，向NEF发送位置请求。
904、NEF将接收到的位置请求向SMF发送。
905、SMF根据接收到的位置请求向NEF返回第一边缘APP对应的第一DNAI。
906、NEF根据接收到的第一DNAI获取目标资源组。
907、NEF根据故障信息向第一中心APP发送目标资源组中的部分DNAI。
部分DNAI中不包括第一DNAI，示例性的，若目标资源组中包括第一DNAI、第二DNAI、第三DNAI和第四DNAI，则NEF将第二DNAI、第三DNAI和第四DNAI向第一中心APP发送。
由于NEF可以感知第一边缘APP是否故障，因此，NEF可以向第一中心APP发送目标资源组中的除第一DNAI之外的其他DNAI，若第一中心APP可以感知第一边缘APP是否故障，NEF也可以向第一中心APP发送目标资源组中全部DNAI，由第一中心APP确定第一边缘APP故障。具体的，第一中心APP可以通过与NEF进行信息交互确定第一边缘APP是否故障。
908、第一中心APP从目标资源组中的部分DNAI中选择第二DNAI，确定第二DNAI对应的第二边缘APP。
909、第一中心APP向SMF发送指示信息。
指示信息用于指示第二网络设备建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径。
910、SMF根据指示信息向第一边缘UPF发送第一分流规则。
第一分流规则为：将从第二边缘UPF接收到的终端设备的第一业务的业务报文向终端设备发送，将从终端设备接收到的第一业务的业务报文向第二边缘UPF发送。
911、SMF根据指示信息向第二边缘UPF发送第二分流规则。
第二分流规则为：将从第一边缘UPF接收到的终端设备的第一业务的业务报文向第二边缘APP发送，将从第二边缘APP接收到的终端设备的第一业务的业务报文向第一边缘UPF发送。
912、SMF向第一中心APP发送路径更新完成信息。
路径更新完成信息用于指示第一边缘UPF与第二边缘UPF之间的路径建立完成。
913、第一中心APP根据接收到的路径更新完成信息确定第一边缘UPF与第二边缘UPF之间的路径建立完成。
914、第一中心APP将业务请求重定向至第二边缘APP。
在执行上述方法之前，MEP管理器需要构建资源组并向第三网络设备发送资源组，参见图10，边缘UPF的部署可以由切片管理器完成，切片管理器对边缘UPF完成部署后，可以向MEP管理器发送第一信息(具体内容参见下文)，边缘APP实例化完成之后，可以向MEP注册，MEP向MEP管理器发送第二信息(具体内容参见下文)，MEP管理器根据第一信息和第二信息构建资源组。
参见图11，构建资源组的方法可以包括：
1101、切片管理器部署边缘UPF。
1102、切片管理器向MEP管理器发送第一信息。
第一信息可以为切片管理器部署的边缘UPF与DC之间的对应关系。
基于表1所示的示例，边缘UPF与DC之间的对应关系可以参见表5。
表5
DC 边缘UPF
DC1 边缘UPF1
DC2 边缘UPF2
1103、MEP管理器从切片管理器接收第一信息。
1104、MEP接收边缘APP发送的注册消息。
其中，边缘APP部署在DC中，边缘APP部署好之后可以向MEP发送注册消息，一个边缘APP发送的注册消息中可以包括该边缘APP的服务标识(application function-service-identifier)，还可以包括边缘APP的互联网协议(internet protocol，简称IP)地址。
1105、MEP从MEP管理器获取MEP的DNAI。
1106、MEP将MEP的DNAI与向MEP注册的边缘APP关联，并向MEP管理器发送第二信息。
第二消息中可以包括边缘APP和MEP的DNAI的对应关系。
基于表1所示的示例，若MEP为MEC1对应的MEP，则第二消息中包括的信息可以参见表6，若MEP为MEC2对应的MEP，则第二消息中包括的信息可以参见表7。
表6
Figure PCTCN2018104327-appb-000002
表7
Figure PCTCN2018104327-appb-000003
1107、MEP管理器从MEP接收第二信息。
具体的，MEP管理器可以从多个MEP接收第二信息。
1108、MEP管理器根据第一信息和第二信息建立DNAI与边缘APP和边缘UPF的对应关系。
步骤1108之后，DNAI与边缘APP和边缘UPF的对应关系参见表8。
表8
Figure PCTCN2018104327-appb-000004
MEP管理器建立的对应关系中还可以包括DC。
需要说明的是，MEP管理器中可以预配置有DC相关的上下文，DC相关的上下文可以包括：DC关联的DNAI、DC中部署的UPF对应的服务区的TAI和基站标识(node id)、DC定位(location)信息等，其中，DC定位信息可以为DC的GPS坐标信息。示例性的，DC相关的上下文可以参见表9。
表9
DC DNAI TAI 基站标识 DC定位
DC1 DNAI1 1 1/2/3/4 GPS坐标1
DC2 DNAI2 2 2/3/4/5 GPS坐标2
MEP管理器可以根据DC相关的DNAI以及第一信息和第二信息建立DNAI与边缘APP和边缘UPF的对应关系。
1109、MEP管理器构建至少一个资源组。
构建资源组的方法可以参见上文，在此不再赘述。
1110、MEP管理器向NEF发送至少一个资源组。
上述实施例中，边缘APP可以为移动边缘应用(mobile edge application)，边缘UPF可以为移动边缘UPF，AN可以为RAN。
本申请实施例提供的方法，实现了MEC节点间的资源共享，在未来部署图形处理器(graphics processing unit，简称GPU)高性能计算能力场景，如果不构建资源组，可能出现区域不够或区域过剩情况，而通过构建资源组，很好的实现了边缘能力的共享。对于一些异常场景，也提供了较好的可靠性机制，实现局部边缘不可用时，可以使用最近的边缘可用资源。
上述主要从方法的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述业务重定向装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对业务重定向装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，图12示出了上述实施例中所涉及的一种业务重定向装置120的一种可能的结构示意图，该业务重定向装置120可以为第一网络设备、第二网络设备或第三网络设备，该业务重定向装置120包括处理单元1201和通信单元1202，还可以包括存储单元1203。
当业务重定向装置120为第一网络设备，处理单元1201用于对第一网络设备的动作进行 控制管理，例如，处理单元1201用于支持第一网络设备执行图5所示的方法，图8中的过程803、808、809、813和814，图9中的过程903、908、909、913和914，和/或本申请实施例中所描述的其他过程中的第一网络设备执行的动作。通信单元1202用于支持第一网络设备与其他网络实体的通信，例如，与图8中的NEF或SMF的通信，存储单元1203用于存储第一网络设备的程序代码和数据。
当业务重定向装置120为第二网络设备，处理单元1201用于对第二网络设备的动作进行控制管理，例如，处理单元1201用于支持第二网络设备执行图8中的过程805、810-812，图9中的过程905，910-912，和/或本申请实施例中所描述的其他过程中的第二网络设备执行的动作。通信单元1202用于支持第二网络设备与其他网络实体的通信，例如，与图8中的第一中心APP或NEF的通信，存储单元1203用于存储第二网络设备的程序代码和数据。
当业务重定向装置120为第三网络设备，处理单元1201用于对第三网络设备的动作进行控制管理，例如，处理单元1201用于支持第三网络设备执行图8中的过程804、806和807，图9中的过程904、906和907，和/或本申请实施例中所描述的其他过程中的第三网络设备执行的动作。通信单元1202用于支持第三网络设备与其他网络实体的通信，例如，与图9中的第一中心APP或SMF的通信，存储单元1203用于存储第三网络设备的程序代码和数据。
其中，处理单元1201可以是处理器或控制器，通信单元1202可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储单元1203可以是存储器。当处理单元1201为处理器，通信单元1202为通信接口，存储单元1203为存储器时，本申请实施例所涉及的业务重定向装置可以参见图4所示的网络设备。其中，当图4所示的为第一网络设备时，处理器401用于对第一网络设备的动作进行控制管理，例如，处理器401用于支持第一网络设备执行图5所示的方法，图8中的过程803、808、809、813和814，图9中的过程903、908、909、913和914，和/或本申请实施例中所描述的其他过程中的第一网络设备执行的动作。当图4所示的为第二网络设备，处理器401用于对第二网络设备的动作进行控制管理，例如，处理器401用于支持第二网络设备执行图8中的过程805、810-812，图9中的过程905，910-912，和/或本申请实施例中所描述的其他过程中的第二网络设备执行的动作。当图4所示的为第三网络设备，处理器401用于对第三网络设备的动作进行控制管理，例如，处理器401用于支持第三网络设备执行图8中的过程804、806和807，图9中的过程904、906和907，和/或本申请实施例中所描述的其他过程中的第三网络设备执行的动作。
本申请实施例还提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，简称DSL))或无线(例如红外、无线、微波等)方式向另一个网 站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，简称SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (22)

  1. 一种业务重定向方法，其特征在于，所述方法包括：
    第一网络设备从终端设备接收业务请求，所述业务请求用于请求与第一边缘应用APP相关的业务；
    所述第一边缘APP不可用，第二边缘APP可用，所述第一网络设备将所述业务请求重定向至所述第二边缘APP，所述第一边缘APP对应第一数据网络接入标识DNAI，所述第二边缘APP对应第二DNAI，所述第一DNAI能够表征所述第一边缘APP的部署位置，所述第二DNAI能够表征所述第二边缘APP的部署位置，所述第一DNAI和所述第二DNAI所表征的部署位置之间满足预设条件，所述第二边缘APP为所述第二DNAI对应的边缘APP中的、与所述第一边缘APP为相同服务商、且具备相同功能的边缘APP。
  2. 根据权利要求1所述的方法，其特征在于，所述第一DNAI和所述第二DNAI属于同一个资源组，一个资源组中的任意两个DNAI对应的接入用户面功能UPF所覆盖的基站为相邻基站；或者，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的跟踪区标识相同或相邻；或者，一个资源组中的任意两个DNAI对应的数据中心DC之间的报文传输距离小于或等于预设阈值。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述第一网络设备将所述业务请求重定向至所述第二边缘APP之前，所述方法还包括：
    所述第一网络设备向第二网络设备发送指示信息，所述指示信息用于指示所述第二网络设备建立所述第一边缘APP对应的第一边缘UPF与所述第二边缘APP对应的第二边缘UPF之间的路径。
  4. 根据权利要求3所述的方法，其特征在于，在所述第一网络设备向第二网络设备发送指示信息之后，所述方法还包括：
    所述第一网络设备从所述第二网络设备接收路径更新完成信息，所述路径更新完成信息用于指示所述第一边缘UPF与所述第二边缘UPF之间的路径建立完成。
  5. 根据权利要求3或4所述的方法，其特征在于，在所述第一网络设备向第二网络设备发送指示信息之前，所述方法还包括：
    所述第一网络设备向第三网络设备发送位置请求，用于所述第三网络设备获取所述终端设备接入的边缘UPF进而获取目标资源组，所述目标资源组为包括所述第一DNAI的资源组；
    所述第一网络设备从所述第三网络设备接收所述目标资源组中的全部或部分参数；
    所述第一网络设备根据所述目标资源组中的全部或部分参数确定所述第二DNAI；
    所述第一网络设备根据所述第二DNAI确定所述第二边缘APP。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，在所述第一网络设备将所述业务请求重定向至所述第二边缘APP之前，所述方法还包括：
    所述第一网络设备确定所述第一边缘APP不可用。
  7. 一种业务重定向方法，其特征在于，所述方法包括：
    第二网络设备从第一网络设备接收指示信息；
    所述第二网络设备根据所述指示信息建立第一边缘应用APP对应的第一边缘用户面功能UPF与第二边缘APP对应的第二边缘UPF之间的路径，所述第二边缘APP为所述第一网络设备在所述第一边缘APP不可用时为所述终端设备的业务请求进行重定向的服务边缘APP，所述业务请求用于请求与所述第一边缘APP相关的业务，所述第一边缘APP 对应第一数据网络接入标识DNAI，所述第二边缘APP对应第二DNAI，所述第一DNAI能够表征所述第一边缘APP的部署位置，所述第二DNAI能够表征所述第二边缘APP的部署位置，所述第一DNAI和所述第二DNAI所表征的部署位置之间满足预设条件，所述第二边缘APP为所述第二DNAI对应的边缘APP中的、与所述第一边缘APP为相同服务商、且具备相同功能的边缘APP。
  8. 根据权利要求7所述的方法，其特征在于，所述第一DNAI和所述第二DNAI属于同一个资源组，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的基站为相邻基站；或者，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的跟踪区标识相同或相邻；或者，一个资源组中的任意两个DNAI对应的数据中心DC之间的报文传输距离小于或等于预设阈值。
  9. 根据权利要求7或8所述的方法，其特征在于，所述业务请求为第一业务的业务请求，所述第二网络设备根据所述指示信息建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径，包括：
    所述第二网络设备向所述第一边缘UPF发送第一分流规则，所述第一分流规则为：将从所述第二边缘UPF接收到的所述终端设备的第一业务的业务报文向所述终端设备发送，将从所述终端设备接收到的所述第一业务的业务报文向所述第二边缘UPF发送；
    所述第二网络设备向所述第二边缘UPF发送第二分流规则，所述第二分流规则为：将从所述第一边缘UPF接收到的所述终端设备的第一业务的业务报文向所述第二边缘APP发送，将从所述第二边缘APP接收到的所述终端设备的所述第一业务的业务报文向所述第一边缘UPF发送。
  10. 根据权利要求7-9任一项所述的方法，其特征在于，在所述第二网络设备根据所述指示信息建立第一边缘APP对应的第一边缘UPF与第二边缘APP对应的第二边缘UPF之间的路径之后，所述方法还包括：
    所述第二网络设备向所述第一网络设备发送路径更新完成信息，所述路径更新完成信息用于指示所述第一边缘UPF与所述第二边缘UPF之间的路径建立完成。
  11. 根据权利要求7-10任一项所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备从第三网络设备接收位置请求，所述位置请求用于请求所述终端设备接入的边缘UPF；
    所述第二网络设备向所述第三网络设备发送目标边缘UPF，所述目标边缘UPF为所述终端设备接入的边缘UPF。
  12. 一种业务重定向方法，其特征在于，所述方法包括：
    第三网络设备从第二网络设备接收目标边缘用户面功能UPF，所述目标边缘UPF为终端设备接入的边缘UPF；
    所述第三网络设备根据所述目标边缘UPF获取目标资源组，所述目标资源组为包括第一数据网络接入标识DNAI的资源组，所述第一DNAI能够表征第一边缘应用APP的部署位置；
    所述第三网络设备向第一网络设备发送所述目标资源组中的全部或部分参数，用于所述第一网络设备确定第二边缘APP，所述第二边缘APP为所述第一网络设备在所述第一边缘APP不可用时为所述终端设备的业务请求进行重定向的服务边缘APP，所述业务请求用于请求与所述第一边缘APP相关的业务，所述第一边缘APP对应第一DNAI，所述第二边缘APP对应第二DNAI，所述第二DNAI能够表征所述第二边缘APP的部署位置， 所述第一DNAI和所述第二DNAI所表征的部署位置之间满足预设条件，所述第二边缘APP为所述第二DNAI对应的边缘APP中的、与所述第一边缘APP为相同服务商、且具备相同功能的边缘APP。
  13. 根据权利要求12所述的方法，其特征在于，所述第一DNAI和所述第二DNAI属于同一个资源组，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的基站为相邻基站；或者，一个资源组中的任意两个DNAI对应的接入UPF所覆盖的跟踪区标识相同或相邻；或者，一个资源组中的任意两个DNAI对应的数据中心DC之间的报文传输距离小于或等于预设阈值。
  14. 根据权利要求12或13所述的方法，其特征在于，在所述第三网络设备从第二网络设备接收目标边缘UPF之前，所述方法还包括：
    所述第三网络设备从所述第一网络设备接收位置请求，所述位置请求用于请求所述终端设备接入的边缘UPF；
    所述第三网络设备向所述第二网络设备发送所述位置请求；
    所述第三网络设备从所述第二网络设备接收所述目标边缘UPF。
  15. 根据权利要求12-14任一项所述的方法，其特征在于，所述方法还包括：
    所述第三网络设备确定所述第一边缘APP不可用。
  16. 根据权利要求12-15任一项所述的方法，其特征在于，所述方法还包括：
    所述第三网络设备从移动边缘平台MEP管理器接收至少一个资源组。
  17. 一种业务重定向装置，其特征在于，所述装置包括：存储器和处理器；
    所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置实现如权利要求1-6中任意一项所述的方法。
  18. 一种业务重定向装置，其特征在于，所述装置包括：存储器和处理器；
    所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置实现如权利要求7-11中任意一项所述的方法。
  19. 一种业务重定向装置，其特征在于，所述装置包括：存储器和处理器；
    所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置实现如权利要求12-16中任意一项所述的方法。
  20. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-6任一项所述的业务流的业务重定向方法。
  21. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求7-11任一项所述的业务流的业务重定向方法。
  22. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求12-16任一项所述的业务流的业务重定向方法。
PCT/CN2018/104327 2017-09-21 2018-09-06 业务重定向方法及装置 WO2019056949A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18859139.0A EP3672320B1 (en) 2017-09-21 2018-09-06 Service redirection method and device
US16/817,023 US11228950B2 (en) 2017-09-21 2020-03-12 Service redirection method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710860147.1A CN109548082B (zh) 2017-09-21 2017-09-21 业务重定向方法及装置
CN201710860147.1 2017-09-21

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/817,023 Continuation US11228950B2 (en) 2017-09-21 2020-03-12 Service redirection method and apparatus

Publications (1)

Publication Number Publication Date
WO2019056949A1 true WO2019056949A1 (zh) 2019-03-28

Family

ID=65811073

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/104327 WO2019056949A1 (zh) 2017-09-21 2018-09-06 业务重定向方法及装置

Country Status (4)

Country Link
US (1) US11228950B2 (zh)
EP (1) EP3672320B1 (zh)
CN (2) CN113115272A (zh)
WO (1) WO2019056949A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110247793A (zh) * 2019-05-29 2019-09-17 暨南大学 一种移动边缘云中的应用程序部署方法
CN112543511A (zh) * 2019-09-20 2021-03-23 大唐移动通信设备有限公司 一种提供、发现移动边缘计算的方法及设备、装置、介质
JP2022532007A (ja) * 2019-05-10 2022-07-13 テンセント・テクノロジー・（シェンジェン）・カンパニー・リミテッド モバイルエッジコンピューティングノードの選択方法、装置及びシステム並びにコンピュータプログラム
EP4075867A4 (en) * 2019-12-31 2023-01-25 Huawei Technologies Co., Ltd. USE CASE DETERMINATION METHOD, DEVICE AND SYSTEM

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111149421B (zh) * 2017-09-29 2023-03-14 富士通株式会社 基站、终端、处理方法和无线通信系统
WO2020200287A1 (en) * 2019-04-02 2020-10-08 Huawei Technologies Co., Ltd. Method, apparatus and systems for supporting packet delivery
US10999756B2 (en) 2019-06-24 2021-05-04 Verizon Patent And Licensing Inc. Integration of radio and core layers
CN112311691B (zh) * 2019-07-26 2024-04-16 华为技术有限公司 策略控制方法、设备及系统
CN110366269B (zh) * 2019-07-30 2021-03-16 中国联合网络通信集团有限公司 会话建立方法及设备
CN112449394B (zh) * 2019-08-28 2022-09-16 中国联合网络通信集团有限公司 一种数据传输方法和核心网设备
CN113630818B (zh) * 2020-05-08 2023-04-07 中国移动通信有限公司研究院 重定向方法、装置、相关设备及存储介质
WO2022000256A1 (en) 2020-06-30 2022-01-06 Ringcentral, Inc. Methods and systems for directing communications
CN113301092B (zh) * 2020-07-31 2022-04-12 阿里巴巴集团控股有限公司 网络重连方法、设备、系统及存储介质
CN114585105A (zh) * 2020-11-28 2022-06-03 华为技术有限公司 一种算力感知的会话管理方法及通信装置
CN113316098B (zh) * 2021-04-20 2022-10-21 新华三技术有限公司 一种建立业务通道、公网对讲的方法和公网对讲设备
US11743953B2 (en) * 2021-05-26 2023-08-29 Amazon Technologies, Inc. Distributed user plane functions for radio-based networks
CN113727380B (zh) * 2021-08-12 2023-06-16 中国联合网络通信集团有限公司 容灾方法及装置
CN116074790B (zh) * 2021-11-02 2024-04-19 中国联合网络通信集团有限公司 Mec业务调度方法、第一mec服务器及存储介质
CN114172951B (zh) * 2021-12-07 2023-06-06 中国联合网络通信集团有限公司 Mec共享方法、通信装置及存储介质
CN116669061A (zh) * 2022-02-16 2023-08-29 中国移动通信有限公司研究院 用户平面功能的选择方法及设备
CN114884819B (zh) * 2022-05-31 2023-08-22 中国联合网络通信集团有限公司 能力开放系统、方法、装置及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104283951A (zh) * 2014-09-29 2015-01-14 华为技术有限公司 一种实例迁移的方法、装置及系统
CN106358245A (zh) * 2016-11-07 2017-01-25 北京佰才邦技术有限公司 移动边缘计算应用负荷分担的方法和控制器
CN106604328A (zh) * 2015-10-15 2017-04-26 中国电信股份有限公司 Mecc区域切换方法和系统
WO2017128702A1 (zh) * 2016-01-27 2017-08-03 中兴通讯股份有限公司 应用的移动性的处理方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8412791B2 (en) * 2001-09-28 2013-04-02 International Business Machines Corporation Apparatus and method for offloading application components to edge servers
WO2017100640A1 (en) * 2015-12-11 2017-06-15 Interdigital Patent Holdings, Inc. Method and apparatus for enabling third party edge clouds at the mobile edge
US10531420B2 (en) * 2017-01-05 2020-01-07 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104283951A (zh) * 2014-09-29 2015-01-14 华为技术有限公司 一种实例迁移的方法、装置及系统
CN106604328A (zh) * 2015-10-15 2017-04-26 中国电信股份有限公司 Mecc区域切换方法和系统
WO2017128702A1 (zh) * 2016-01-27 2017-08-03 中兴通讯股份有限公司 应用的移动性的处理方法及装置
CN106358245A (zh) * 2016-11-07 2017-01-25 北京佰才邦技术有限公司 移动边缘计算应用负荷分担的方法和控制器

Non-Patent Citations (2)

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

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022532007A (ja) * 2019-05-10 2022-07-13 テンセント・テクノロジー・（シェンジェン）・カンパニー・リミテッド モバイルエッジコンピューティングノードの選択方法、装置及びシステム並びにコンピュータプログラム
JP7252356B2 (ja) 2019-05-10 2023-04-04 テンセント・テクノロジー・（シェンジェン）・カンパニー・リミテッド モバイルエッジコンピューティングノードの選択方法、装置及びシステム並びにコンピュータプログラム
CN110247793A (zh) * 2019-05-29 2019-09-17 暨南大学 一种移动边缘云中的应用程序部署方法
CN110247793B (zh) * 2019-05-29 2022-11-11 暨南大学 一种移动边缘云中的应用程序部署方法
CN112543511A (zh) * 2019-09-20 2021-03-23 大唐移动通信设备有限公司 一种提供、发现移动边缘计算的方法及设备、装置、介质
EP4075867A4 (en) * 2019-12-31 2023-01-25 Huawei Technologies Co., Ltd. USE CASE DETERMINATION METHOD, DEVICE AND SYSTEM

Also Published As

Publication number Publication date
CN113115272A (zh) 2021-07-13
EP3672320B1 (en) 2024-01-24
CN109548082B (zh) 2021-03-30
EP3672320A4 (en) 2020-11-25
US20200213914A1 (en) 2020-07-02
CN109548082A (zh) 2019-03-29
US11228950B2 (en) 2022-01-18
EP3672320A1 (en) 2020-06-24

Similar Documents

Publication Publication Date Title
US11228950B2 (en) Service redirection method and apparatus
US11432366B2 (en) Session management method, device, and system
US10743218B2 (en) Session management function entity selection method, apparatus, and system
US11785633B2 (en) Base station radio resource management for network slices
US20210314842A1 (en) Optimal network function data path discovery for 5g core
EP3509253A1 (en) Inter-cloud communication method and related device, inter-cloud communication configuration method and related device
US11528239B2 (en) Time-sensitive networking communication method and apparatus for configuring virtual switching node
US20220346190A1 (en) Session Management Method, Device, and System
US20220264428A1 (en) Method for controlling use of network slice, apparatus, and system
CN110831094B (zh) 一种数据传输通道的处理方法及装置
US20150117209A1 (en) Traffic distribution in heterogenous network environment
WO2018153221A1 (zh) 传输网络中业务服务质量的控制方法、设备及系统
US11973641B2 (en) Deploying edge computing
WO2019062830A1 (zh) 实例业务拓扑的生成方法及装置
EP3790308B1 (en) Business service quality monitoring method, device and system
CN111770545A (zh) 一种业务流路由控制方法、装置及系统
US11689958B2 (en) Communication method, device, and system
WO2020103517A1 (zh) 终端的能力信息的获取方法、装置及系统
US20230070345A1 (en) Communication method and apparatus
US20230156828A1 (en) Session establishment method and apparatus, system, and computer storage medium
CN113543219A (zh) 通信方法和装置
US20240107333A1 (en) Geographically redundant and high availability system architecture for a hybrid cloud cellular network
US10848377B2 (en) Access point instantiation of a mesh network
US20220330080A1 (en) Communication method, apparatus, and system
WO2019052363A1 (zh) 修改网络切片实例的方法及装置

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

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

Country of ref document: EP

Effective date: 20200319