WO2018068738A1 - 一种连接管理方法及装置、计算机存储介质 - Google Patents

一种连接管理方法及装置、计算机存储介质 Download PDF

Info

Publication number
WO2018068738A1
WO2018068738A1 PCT/CN2017/105778 CN2017105778W WO2018068738A1 WO 2018068738 A1 WO2018068738 A1 WO 2018068738A1 CN 2017105778 W CN2017105778 W CN 2017105778W WO 2018068738 A1 WO2018068738 A1 WO 2018068738A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
terminal device
type
forwarding plane
access
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/105778
Other languages
English (en)
French (fr)
Inventor
孙滔
王丹
蔡慧
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
Research Institute of China Mobile Communication Co Ltd
Original Assignee
Research Institute of China Mobile Communication Co Ltd
China Mobile Communications Corp
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 Research Institute of China Mobile Communication Co Ltd, China Mobile Communications Corp filed Critical Research Institute of China Mobile Communication Co Ltd
Priority to US16/340,107 priority Critical patent/US10785693B2/en
Priority to EP17859735.7A priority patent/EP3525548B1/en
Priority to JP2019514218A priority patent/JP2019530334A/ja
Publication of WO2018068738A1 publication Critical patent/WO2018068738A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/322—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • the present invention relates to connection management technologies in the field of communications, and in particular, to a connection management method and apparatus, and a computer storage medium.
  • the network element (or network function) of the core network is composed of two functions: a control plane and a user plane.
  • a control plane In a traditional network architecture, such as a 3G/4G network, user plane gateways are often deployed centrally at a core layer that is relatively far from the user.
  • the mobile network sinks the user plane function in the design of the 4G network architecture or the new architecture of the 5G network, and deploys it at the edge of the network, thereby reducing the transmission delay and reducing the transmission of the backhaul network. pressure.
  • the main purpose of the present invention is to provide a connection management method and device, and a computer storage medium. Quality, aiming to solve the above problems in the prior art.
  • connection management method comprising:
  • the type of the connection path between the terminal device and the first forwarding plane includes: the first type of path is a connection path directly established between the terminal device and the first forwarding plane by the terminal device;
  • the path is a connection path established between the second forwarding plane of the second forwarding plane and the first forwarding plane by the terminal device through the access network.
  • An embodiment of the present invention provides a connection management apparatus, including:
  • An information acquisition unit that detects related information of the terminal device
  • the path adjustment unit determines, according to the related information of the terminal device, whether to adjust the type of the connection path between the terminal device and the first forwarding plane;
  • the type of the connection path between the terminal device and the first forwarding plane includes: the first type of path is a connection path directly established between the terminal device and the first forwarding plane by the terminal device; The path is a connection path established by the terminal device between the second forwarding plane and the first forwarding plane through the access network.
  • connection management apparatus includes:
  • a communication interface for detecting information about the terminal device
  • the processor determines, according to the related information of the terminal device, whether to adjust a type of a connection path between the terminal device and the first forwarding plane;
  • the type of the connection path between the terminal device and the first forwarding plane includes: the first type of path is a connection path directly established between the terminal device and the first forwarding plane by the terminal device; The path is a connection path established by the terminal device between the second forwarding plane and the first forwarding plane through the access network.
  • the application provides a connection management apparatus, including: a processor and a storage device capable of processing The memory of the computer program running on the device,
  • processor is configured to perform the steps of the foregoing method when the computer program is run.
  • the application provides a computer storage medium storing computer executable instructions that, when executed, implement the aforementioned method steps.
  • connection management method and device and the computer storage medium provided by the present invention can determine whether to adjust the path type between the terminal device and the first forwarding plane based on at least the access network corresponding to the location to which the terminal device moves.
  • the path type may include a first type of path directly connected to the first forwarding plane, and a second type of path connected to the first forwarding plane through the second forwarding plane. In this way, the flexibility and efficiency of the network architecture can be provided.
  • a gateway processing is implemented with a minimum number of hops, and the path type configuration can be performed only on the network side, and no more configuration is required on the terminal device side. Changes can enable access to edge network data.
  • FIG. 1 is a schematic flowchart 1 of a connection management method according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram 1 of a processing scenario according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram 2 of a processing scenario according to an embodiment of the present invention.
  • 4a is a schematic diagram of a first type of path according to an embodiment of the present invention.
  • 4b is a schematic diagram of a second type of path according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram 2 of a processing scenario according to an embodiment of the present invention.
  • FIG. 6 is a second schematic flowchart of a connection management method according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart 3 of a connection management method according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart 4 of a connection management method according to an embodiment of the present invention.
  • FIG. 9 is a schematic flowchart 5 of a connection management method according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart 6 of a connection management method according to an embodiment of the present invention.
  • FIG. 11 is a schematic flowchart 7 of a connection management method according to an embodiment of the present invention.
  • connection management device 12 is a schematic structural diagram 1 of a connection management device according to an embodiment of the present invention.
  • FIG. 13 is a second schematic structural diagram of a connection management apparatus according to an embodiment of the present invention.
  • An embodiment of the present invention provides a connection management method, which is applied to a connection management apparatus, including: detecting related information of a terminal device;
  • the type of the connection path between the terminal device and the first forwarding plane includes: the first type of path is a connection path directly established between the terminal device and the first forwarding plane by the terminal device;
  • the path is a connection path established between the second forwarding plane of the second forwarding plane and the first forwarding plane by the terminal device through the access network.
  • the related information of the terminal device includes: a location of the terminal device, and/or a current service type of the terminal device.
  • Step 101 Detect a location of the terminal device, and/or detect a current service type of the terminal device.
  • Step 102 Determine, according to the location of the terminal device and/or the current service type of the terminal device, whether to adjust the type of the connection path between the terminal device and the first forwarding plane;
  • the type of the connection path between the terminal device and the first forwarding plane includes: the first type of path is a connection path directly established between the terminal device and the first forwarding plane by the terminal device; The path is a connection path established by the terminal device between the second forwarding plane and the first forwarding plane through the access network.
  • connection management device is mainly disposed in the core network, and the specific implementation may be one.
  • the modules are set in one of the devices in the core network, for example, may be set in the MME in the core network.
  • the first forwarding plane is a core user plane
  • the second forwarding plane is an edge user plane.
  • the detecting the location of the terminal device, and/or detecting the current service type of the terminal device, that is, obtaining the location of the terminal device may be obtaining the location to which the terminal device is currently moved, that is, The location of the terminal device is currently described; the specific manner may include: detecting a target access device that the terminal device is currently accessing, and acquiring identification information of the target access device (such as an ID number of the access device); The identification information of the target access device determines an area corresponding to the access device (for example, the core network side can determine an area code corresponding to the access device by using identifier information of the access device); The corresponding area determines the location where the terminal device is currently located.
  • the access device may be a base station, or may be an access point (AP) or the like, and is used to provide a direct access mode device for the terminal device.
  • AP access point
  • the foregoing solution can provide two types of triggering situations, where the first triggering situation is to determine whether the terminal device is in an access network capable of performing local service offloading based on the change of the location of the terminal device, thereby determining whether The path type of the terminal device is adjusted.
  • the second triggering situation is to determine whether the terminal device performs the path type adjustment in combination with whether the terminal device has local service traffic distribution or the service data transmission path optimization requirement.
  • This embodiment is mainly directed to the first type of triggering situation.
  • the terminal When the terminal connects to the session, the terminal only establishes a session connection for a core side gateway.
  • the control plane initiates a new establishment. Tunnel, thereby adding the EGW to the existing session, that is, switching from the first type of path to the second type of path; when the terminal moves out of the coverage of the EGW (the access network does not contain the EGW), the control plane can trigger A new tunnel establishment mechanism removes the EGW from the session path and establishes a second type of path to delete the first type of path.
  • Scenario 1 Before the obtaining the location where the terminal device is located, the method further includes:
  • the terminal device establishes a first type of path with the first forwarding plane by using the first access device, where the first access device and the terminal device are to be accessed at the current location
  • the target access device is different; the coverage area corresponding to the first access device does not have a second forwarding plane or is not suitable for accessing the second forwarding plane;
  • determining, according to the access network corresponding to the location where the terminal device is located, whether to adjust the type of the connection path between the terminal device and the first forwarding plane including:
  • the terminal device and the device are capable of accessing the second forwarding plane (ie, the edge side user plane) or the second forwarding plane suitable for the terminal device when the terminal device is currently located.
  • the path between the first forwarding planes is adjusted by the first type of path to the second type of path. That is to say, the core network side can determine whether the location side edge user plane (second forwarding plane) can be optimized according to the current location of the terminal device (such as the area code).
  • a terminal device such as a UE
  • the access network 1 corresponds to the first access device.
  • the access network 2 corresponds to the access network corresponding to the target access device to be accessed by the UE; correspondingly, when the UE is in the access network 1, the connection management device determines that the UE currently adopts the first type of path, that is, in the figure
  • the access network 1 is connected to the first forwarding plane (such as the core gateway (CGW) in the figure), and finally the core network (specifically, the core public data network (PDN) network) performs data processing;
  • the network side may specifically switch the path type between the UE and the core network for the connection management device.
  • the traffic that needs to be locally offloaded can be offloaded to the edge PDN network.
  • Another part needs The core network PDN service processing performed by the processing core network PDN to the CGW.
  • the first access device is different from the target access device to be accessed by the terminal device at the current location.
  • the first location 31 of the terminal device may be the access network. 1 is a location within the coverage of the first access device, with the terminal device The mobile device moves to the current location 32. (It is to be understood that the mobile device may move in the access network 1 after being moved, and may also be in the access network 2. This embodiment is mainly for generating access.
  • the scene of the network change is described as the scenario shown in FIG.
  • the location 32 is located in the access network 2, that is, the network where the target access device to which the terminal device is to access; further, the access network 1 does not With or without access to the second forwarding plane (for example, the edge gateway EGW in the figure), that is, the access network 1 cannot provide local service offload, and the access network 2 has the second forwarding that can optimize the local service access path.
  • the second forwarding plane for example, the edge gateway EGW in the figure
  • the access network 2 can provide local service offloading
  • the type of connection between the terminal device and the core network can be adjusted based on the access network in which the terminal device is located.
  • the connection management device may be based on whether the access network where the terminal device is located has a second forwarding plane (for example, an edge-side user plane or an edge gateway). Determining the path type initially established by the terminal device. When the access network does not have or is not suitable for accessing the second forwarding plane, when the terminal device first accesses the network, the first type of path is established, as shown in FIG. 4a.
  • the core gateway establishes a connection; when the access network has an edge gateway, when the terminal device first accesses the network, a second type of path as shown in FIG. 4b is established, and the connection is established with the core gateway via the edge gateway, specifically, the edge gateway is connected.
  • the local network is divided into services, and some services are routed to the core gateway to perform data processing through a core network, such as a data network.
  • the control plane that is, the connection management device
  • obtains the current location of the access network determines whether there is a second forwarding plane currently present, and if there is a second forwarding plane, then controls
  • the information of the second access plane (such as its IP address) is obtained through the identifier of the current access network (such as the ID of the access base station or the information of the location area, such as the TA), and a corresponding tunnel is established.
  • the second forwarding plane is selected for the terminal device, and the second forwarding plane is The identification information is sent to the first forwarding plane as information of the downlink tunnel of the first forwarding plane, and The identification information of the second forwarding plane is sent to the access network side as the information of the access side uplink tunnel, so as to establish that the terminal device passes the access device (the access network corresponding to the target access device to be accessed at the location) Connecting a second type of path between the first forwarding planes via the second forwarding plane.
  • the terminal device after determining to adjust the first type of path to the second type of path, the terminal device is also required to perform path type adjustment and notify the channel device of the second forwarding plane to be accessed.
  • the second forwarding plane such as an edge gateway (EGW)
  • EGW edge gateway
  • CGW core side gateway
  • the IP address and tunnel ID of the EGW downlink tunnel are used to inform the CGW as the downlink tunnel endpoint of the CGW; the IP address and tunnel ID of the EGW uplink tunnel are sent to the access network as the uplink tunnel endpoint of the access network.
  • the terminal device moves from the non-MEC region to the MEC region in the idle (IDLE) mode, when the UE initiates the service or the downlink data arrives at the network paging, the UE is triggered to initiate the session establishment, and the network determines whether to proceed according to the current location. Connection updates. If the update of the connection is required, the control plane is not a tunnel between the newly created CGW and the access network (AN, Access Network), but is established as a tunnel between the AN, the EGW, and the CGW.
  • AN Access Network
  • Scenario 2 is different from the scenario 1.
  • the scenario 1 is used to adjust the path of the first type to the path of the second type. This scenario is described for adjusting the path of the second type to the first type of path.
  • the terminal device establishes a second type of path with the first forwarding plane by using the second access device, where the second access device and the target device are to be accessed by the terminal device at the current location.
  • the device is different; the second access device is located at a location with a second forwarding plane or a second forwarding plane suitable for terminal device access;
  • Determining between the terminal device and the first forwarding surface when the location where the terminal device is currently located does not have a second forwarding plane or does not have a second forwarding plane suitable for access by the terminal device
  • the path is adjusted by the second type of path to the first type of path.
  • the second access device is different from the target access device to be accessed by the terminal device at the current location.
  • the second location 51 of the terminal device may be the second A location in the access network 1 of the access device moves to the current location 52 as the terminal device moves.
  • the terminal device may move after being moved or located in the access network 1, It can also be located in the access network 2.
  • This embodiment is mainly for the scenario of generating an access network change, that is, the scenario shown in the figure.
  • the location 52 is located in the access network 2, and the access network 2 corresponds to The target access device to be accessed by the terminal device; further, the access network 1 has a second forwarding plane (for example, the edge gateway EGW in the figure), that is, the access network 1 can provide local service offload and access
  • the network 2 does not have or is not suitable for accessing the second forwarding plane (for example, the edge gateway EGW in the figure), that is, the access network 2 cannot provide local service offload, and then the access network based on the terminal device is different. , you need to put the terminal The device is adjusted by the second type of path to the first type of path.
  • the path between the terminal device and the first forwarding plane needs to be adjusted to the first type of path by the second type of path, notify the first forwarding plane of the corresponding identification information of the access network, and the The identification information of a forwarding plane is notified to the access network to establish a first type of path between the terminal device and the first forwarding plane.
  • the control plane determines that the second forwarding plane of the current session is no longer needed, and the connection update does not include the information of the intermediate EGW, the data of the user plane.
  • the channel becomes an AN directly connected to the CGW.
  • the access network and the CGW are directly used as the opposite end of the tunnel: the corresponding tunnel ID and IP of the access network are sent to the CGW as The downstream tunnel endpoint of the CGW; the IP address and tunnel ID of the CGW tunnel are communicated to the access network as the upstream tunnel endpoint of the access network.
  • the network will further release the user plane tunnel between the EGW and the CGW through the location update.
  • the new tunnel is the AN and the CGW. Direct one-hop tunnel.
  • scenario 3 provides a way to switch back to the first type of path: when the terminal device is in a position that no longer establishes a connection with the original second forwarding plane, the switch back to the first Class path.
  • the method further includes:
  • the terminal device establishes a second type of path with the first forwarding plane via the second forwarding device by using the second access device, where the second access device and the terminal device are in the current location
  • the access target access device is different;
  • determining, according to the current location of the terminal device and/or the current service type of the terminal device, whether to adjust the type of the connection path between the terminal device and the first forwarding plane including:
  • the manner of determining whether the second forwarding plane can be accessed may be determined based on a physical location corresponding to each second forwarding plane saved by the core network side, where the current location of the terminal device, such as the area code, the corresponding coverage. If the second forwarding plane is not included, it can be determined that the second type of path cannot be continuously connected, and then the first type of path is adjusted.
  • the determining manner of the target access device to be accessed by the terminal device in the current location may be that when the terminal device is in the process of switching, the terminal device may obtain multiple connections to the network side through the handover process.
  • the switching request of the incoming access device can finally select a target access device for the terminal device, that is, the target access device to be accessed at the location currently described by the terminal device in the embodiment.
  • the terminal (UE) has established a data transmission channel through the original access network node 1, CGW and to the core PDN network, that is, the first type of path has been established.
  • the access network node 2 When the terminal moves to the coverage of the access network node 2, the access network node 2 initiates a handover request to the control plane.
  • the location request information of the access network node 2 is included in the handover request.
  • the access network node 2 is the target access device to be accessed.
  • the control plane determines whether the area has EGW deployment by accessing the location information of the network node 2. If EGW is deployed, select a suitable EGW to implement local offload based on location information, load balancing, and other policies.
  • the control sends a tunnel update request (for example, a path update request) to the CGW, and the IP address and the tunnel ID of the EGW are used as endpoints of the downlink tunnel of the CGW.
  • a tunnel update request for example, a path update request
  • the control sends a tunnel update request to the access network node 2 (ie, the target access device to which the UE is to access), and uses the EGW IP address and the tunnel ID as the endpoints of the access network node 2 uplink tunnel.
  • the access network node 2 ie, the target access device to which the UE is to access
  • the control sends a tunnel update request to the EGW, and the IP address and the tunnel ID of the CGW are used as the endpoints of the EGW uplink tunnel, and the IP address and the tunnel ID of the access network node 2 are used as the downlink tunnel endpoints of the EGW, that is, the second is established. Class path.
  • the control sends a path switch reply to the access network node 2 to confirm the completion of the handover process.
  • the process of the above embodiment can be extended to the terminal attachment process accordingly.
  • the above access network nodes can be extended to third-party access base stations (eg, EGW based on third-party WLAN selection)
  • the flow is as shown in FIG. 7:
  • the terminal (UE) has established a serial transmission channel as shown.
  • the local offloaded data passes through the access network node 1, EGW to the edge network; other data passes through the access network node 1, EGW, CGW to the core PDN network, that is, the second type of path has been established.
  • the access network node 2 When the terminal moves to the coverage of the access network node 2, the access network node 2 initiates a handover request to the control plane.
  • the location request information of the access network node 2 is included in the handover request.
  • the control plane determines whether the area has EGW deployment by accessing the location information of the network node 2. If there is no EGW deployment, the corresponding tunnel link adjustment is performed.
  • the control sends a tunnel update request to the CGW, and the IP address and the tunnel ID of the access network node 2 are used as endpoints of the downlink tunnel of the CGW.
  • the control sends a tunnel update request to the access network node 2, and uses the IP address and the tunnel ID of the CGW as the endpoint of the uplink tunnel of the access network node 2.
  • the control sends a tunnel update request to the EGW to release the related tunnel resources of the EGW, that is, switch from the second type path to the first type path.
  • the control sends a path switch reply to the access network node 2 to confirm the completion of the handover process.
  • the control sends a tunnel creation or update request to the CGW, and uses the EGW IP address and the tunnel ID as the endpoints of the CGW downlink tunnel.
  • the control sends a tunnel creation request to the access network node, and uses the EGW IP address and the tunnel ID as the uplink tunnel endpoint of the access network node.
  • control for the EGW to send a tunnel creation request the CGW IP address and tunnel ID as the uplink tunnel endpoint, the access network node's IP address and tunnel ID as the downlink tunnel endpoint, that is, switch from the first type of path To the second type of path.
  • the control sends a path switch completion reply to the access network node 2, and confirms that the handover process is completed.
  • Example 4 When the UE moves in the Idle state and moves out of the coverage area of the EGW, the deletion process of the EGW is as shown in FIG. 9:
  • the UE initiates a location update message because the location tracking area changes due to the movement.
  • control plane moves out of the MEC area according to the location update message and the new location area, the control sends a tunnel deletion request to the EGW to release the relevant tunnel resource.
  • the control sends a tunnel deletion request to the CGW, and releases the related tunnel resource, that is, the second type path is replaced with the first type path.
  • the terminal device When the service type corresponding to the terminal device is switched from the first service type to the second service type, and the access network where the terminal device is located has the second forwarding surface coverage, the terminal device may be determined to be The connection path between the first forwarding planes is adjusted by the first type of path to the second type of path.
  • the path type may include direct A first type of path connected to the first forwarding plane and a second type of path hopped to the first forwarding plane by the second forwarding plane.
  • the flexibility and efficiency of the network architecture can be provided.
  • a gateway processing is implemented with a minimum number of hops, and the path type configuration can be performed only on the network side, and no more configuration is required on the terminal device side. Changes can enable access to edge network data.
  • the present embodiment is mainly used for the second triggering situation, where the at least the access device corresponding to the location of the terminal device determines whether the terminal device is the first
  • the type of the connection path between the forwarding planes is adjusted.
  • whether the path switching is triggered may be determined based only on the service type of the terminal device.
  • Whether the second forwarding plane is not included in the coverage of the access network is not a major consideration. If the second forwarding plane is available in the access network, and the terminal equipment service type needs to trigger path optimization, it can be logically accessed.
  • the second forwarding plane that is closer to the network establishes a connection to provide a second type of path for the terminal device.
  • the specific description is as follows: when the service type corresponding to the terminal device is switched from the first service type to the second service type, determining the terminal The connection path between the device and the first forwarding plane is adjusted by the first type of path to the second type of path;
  • the first service type is different from the second service type, the second service type is a service type that needs to be offloaded by the local service, and the first service type is a service type that does not need to be offloaded by the local service.
  • the method further includes: establishing, by the terminal device, a connection between the core network and the core network through a first type of path;
  • the access network corresponding to the location where the terminal device is located is provided with a second forwarding plane that can optimize the local service access path, and detects that the service type corresponding to the terminal device is switched from the first service type to the second service type. Determining that the connection path between the terminal device and the first forwarding plane is adjusted from the first type of path to the second type of path;
  • the first service type is different from the second service type, the second service type is a service type that needs to be offloaded by the local service, and the first service type is a service type that does not need to be offloaded by the local service.
  • connection management device learns that when the UE initiates an edge or local service, it triggers the update of the connection between the access network and the core network gateway, dynamically joins the function of the second forwarding plane (for example, the edge gateway EGW), and establishes the UE and the EGW.
  • the connection forms a network architecture as shown in Figure 4b.
  • connection path between the terminal device and the first forwarding plane is adjusted from the first type of path to the second After the class path is detected, the duration of the information exchange of the second service type is stopped after the terminal device finishes the information exchange of the second service type for the last time;
  • the connection path between the terminal device and the first forwarding plane is adjusted by the second type path to the first type of path.
  • connection management device (the network side control plane) detects that the UE with the second forwarding plane does not access the services of the edge network for a period of time, and deletes the edge network gateway in the path, that is, switches from the second type of path to the first Class path.
  • connection management device learns that the terminal device accesses the edge or the local service includes at least one of the following:
  • the first method is to determine whether the first service type is switched to the second service type by using the service type information reported by the terminal device. That is, the UE informs the network that the signaling sent by the UE to the control plane includes the service type information, and the network side determines that the service of the UE is suitable for the access edge or the local network by using the service type information, and then establishes an EGW connection.
  • connection management device needs to optimize the service access path of the terminal from the network side. Specifically, the connection management device perceives that the service of the UE is suitable for the access edge or the local network. For example, the user plane informs the control plane of the user's IP address through the user plane according to the service target address accessed by the user.
  • the third method is to receive the notification information sent by the server corresponding to the service used by the terminal device to determine the service type of the terminal device. For example, directly or through the capability open interface, the network user is required to establish a link to the edge network.
  • connection management device senses that only the terminal device connected to the core layer needs to establish a data channel to the edge (or local) network or the data packet needs to be split at the edge, and the core network control plane triggers the second forwarding plane (or the network of the user plane) Function) Joins an existing data channel and updates the tunnel.
  • the data that needs to be routed in the edge network is forwarded and split through the second forwarding plane, and the other data flows reach the core layer gateway through the second forwarding plane, and then reach the core PDN network.
  • the terminal does not perceive changes in the network during this process.
  • the network When the network senses that the connection with the second forwarding plane is no longer needed When the edge network data channel is used, the network triggers the update of the connection path and deletes the second forwarding plane in the transmission path (for example, the edge gateway EGW). Enable all data to enter the PDN network through one hop.
  • the UE generates a data service, and the network determines that a second forwarding plane (for example, an edge gateway EGW) needs to be introduced to optimize the data channel, triggering the joining of the second forwarding plane to initiate a session update process for the access network, and the IP address and tunnel of the EGW uplink tunnel.
  • a second forwarding plane for example, an edge gateway EGW
  • the ID tells the access network as the upstream tunnel endpoint of the access network; the IP address and tunnel ID of the EGW downlink tunnel are told to the CGW as the downstream tunnel endpoint of the CGW.
  • the step of deleting the EGW is triggered, which may include:
  • the EGW is added to the flowchart shown in FIG. 10:
  • the terminal has established a data transmission channel through the original access network node 1, CGW and to the core PDN network, that is, the first type of path has been established. That is, the UE has established a first type of path with the first forwarding plane through the access device of the access network.
  • the service type information is carried to the control plane.
  • the network control plane determines whether the service type can be locally offloaded. If the service is an MEC service, the terminal is connected to the EGW, and then to the CGW, as shown in FIG.
  • the steps 3, 4, 5, and 6 are the same as those in FIG. 6 (ie, the first example of the embodiment), and are not described herein again.
  • step of 2 may be: the control plane interacts with the CGW to determine whether the terminal accesses the MEC service. If yes, steps 3, 4, and 5 are consistent with FIG. 4.
  • the step of 2 may also be: the control plane interacts with the capability open platform interface to determine whether the terminal accesses the MEC service, and if so, the steps 3, 4, and 5 are consistent with FIG. 4.
  • the EGW deletion process is as shown in FIG. 11:
  • the terminal (UE) has established a serial transmission channel as shown.
  • the local offloaded data passes through the access network node 1, EGW to the edge network; other data passes through the access network node 1, EGW, CGW to the core PDN network, that is, the second type of path has been established.
  • the control sends a service detection request to the EGW to detect whether the terminal has the MEC service running.
  • the EGW has returned to the control plane that the MEC service has ended.
  • the control plane triggers the process and deletes the EGW. 3, 4, 5, and 6 are consistent with the steps of Figure 7 (Example 2 of the embodiment).
  • the step of 2 may also be that the control plane interacts with the capability open interface to determine whether the terminal ends accessing the MEC service. If it is over, the steps 3, 4, and 5 are the same as those in FIG. 5.
  • the network control plane is in the process of tunnel update, such as the connection state switching or the terminal initiated session establishment process, dynamic Introduce the EGW into the path of the user plane tunnel. That is, from AN ⁇ ->CGW, it becomes AN ⁇ ->EGW ⁇ ->CGW
  • the downlink identification information of the EGW is used to inform the CGW as the downlink tunnel endpoint of the CGW; and the uplink identification information of the EGW may be, but not limited to, the IP address of the uplink tunnel.
  • the tunnel ID informs the access network as the upstream tunnel endpoint of the access network
  • the network control plane When the terminal moves out of the MEC area, the network control plane establishes a tunnel from the AN to the core side gateway in the related process of the tunnel update, such as the connection state switching or the terminal initiated session establishment process, that is, by AN ⁇ ->CGW.
  • the control plane may notify the CGW as the downlink tunnel endpoint of the CGW by using the corresponding identification information of the access network, but not limited to the tunnel ID and the IP address.
  • the identification information of the CGW, the identification information may be, but not limited to, the IP address and the tunnel ID.
  • the above-mentioned direct tunnel or the EGW transit tunnel in addition to the UE moving, the UE initiates related processes for mutual conversion, the network can also judge according to the user service, and the network side triggers the switching between the two types of tunnels.
  • the network side needs to introduce the second forwarding plane to optimize the data channel through the service type:
  • the UE informs the network that the signaling sent by the UE to the control plane includes the service type information, and the network side determines that the service of the UE is suitable for the access edge or the local network by using the service type information, and then establishes an EGW connection.
  • the network autonomously perceives the UE service to be suitable for accessing the edge or the local network: for example, the user plane is based on the service target address accessed by the user.
  • the user plane informs the control plane of the user's IP address.
  • the service side informs the network that a user needs to establish a link to the edge network directly or through the capability open interface.
  • the terminal in this embodiment does not need to introduce multiple IP addresses in order to implement MEC (or local offload) when there is a session connection, and only one IP address anchor point.
  • MEC mobile electronic book
  • the EGW is dynamically deleted, so that the data packet only needs to pass through one CGW, and one hop enters the core PDN network, maintaining the flattening characteristics of the network.
  • the EGW is dynamically added to the network to implement local offloading.
  • the terminal can be made without awareness, which simplifies the behavior of the terminal and facilitates the unified configuration and management of the edge traffic forwarding policy.
  • the path type may include direct A first type of path connected to the first forwarding plane and a second type of path hopped to the first forwarding plane by the second forwarding plane. So you can provide the network
  • the flexibility and efficiency of the architecture enables a gateway to be processed with a minimum number of hops without local offloading, and access to edge network data without requiring more configuration changes on the terminal side.
  • connection management apparatus includes:
  • the information acquiring unit 1201 detects related information of the terminal device
  • the path adjustment unit 1202 determines, according to the related information of the terminal device, whether to adjust the type of the connection path between the terminal device and the first forwarding plane;
  • the type of the connection path between the terminal device and the first forwarding plane includes: the first type of path is a connection path directly established between the terminal device and the first forwarding plane by the terminal device; The path is a connection path established by the terminal device between the second forwarding plane and the first forwarding plane through the access network.
  • the related information of the terminal device includes: a location of the terminal device, and/or a current service type of the terminal device.
  • the information obtaining unit 1201 is configured to acquire a location where the terminal device is currently located, and/or obtain a current service type of the terminal device.
  • the path adjustment unit 1202 is configured to determine, according to the current location of the terminal device and/or the current service type of the terminal device, whether to adjust the type of the connection path between the terminal device and the first forwarding plane;
  • the type of the connection path between the terminal device and the first forwarding plane includes: the first type of path is a connection path directly established between the terminal device and the first forwarding plane by the terminal device; The path is a connection path established by the terminal device between the second forwarding plane and the first forwarding plane through the access network.
  • connection management device is mainly disposed in the core network, and the specific implementation may be one.
  • the modules are set in one of the devices in the core network, for example, may be set in the MME in the core network.
  • the manner of obtaining the location currently described by the terminal device may include: detecting an access device currently accessed by the terminal device, acquiring identifier information of the access device (such as an ID number of the access device); The identification information of the access device determines an area corresponding to the access device (for example, the core network side can determine the area code corresponding to the access device by using the identification information of the access device); The area determines the location at which the terminal device is currently located.
  • the access device may be a base station, or may be an access point (AP) or the like, and is used to provide a direct access mode device for the terminal device.
  • AP access point
  • the foregoing solution can provide two types of triggering situations, where the first triggering situation is to determine whether the terminal device is in an access network capable of performing local service offloading based on the change of the location of the terminal device, thereby determining Whether to adjust the path type of the terminal device; the second triggering situation is to determine whether the terminal device performs the path type adjustment in combination with the requirement of the local device for the local service offloading.
  • This embodiment is mainly directed to the first type of triggering situation.
  • the terminal When the terminal connects to the session, the terminal only establishes a session connection for a core side gateway.
  • the control plane initiates a new establishment. Tunnel, thereby adding the EGW to the existing session, that is, switching from the first type of path to the second type of path; when the terminal moves out of the coverage of the EGW, the control plane can trigger a new tunnel establishment mechanism, and the EGW Remove from the session path, create a second type of path to delete the first type of path.
  • the connection management apparatus further includes: a path management unit 1203, configured to determine that the terminal device establishes a first type of path with the first forwarding plane by using the first access device, where the first access The device is different from the target access device that the terminal device is to access at the current location; the coverage area corresponding to the first access device does not have the second forwarding plane or is not suitable for accessing the second forwarding surface;
  • the path adjusting unit 1202 is configured to: when the terminal device is currently located When the second forwarding plane capable of accessing the second forwarding plane or capable of accessing the terminal device is configured, determining that the path between the terminal device and the first forwarding plane is adjusted from the first type of path to the first Second class path. That is to say, the core network side can determine whether the location has a second forwarding plane that can optimize the local service access path according to the current location of the terminal device (such as the area code).
  • the connection management device may determine the path type initially established by the terminal device based on whether the access network where the terminal device is located has the second forwarding plane.
  • the first type of path is established when the terminal device first accesses the network, and the first forwarding plane is directly connected as shown in FIG. 4a;
  • the second forwarding plane (for example, the edge gateway EGW in the figure), when the terminal device first accesses the network, establishes a second type of path as shown in FIG. 4b, via the second forwarding plane (for example, the edge gateway EGW in the figure) and the first The forwarding plane (such as the core gateway (CGW) in the figure) establishes a connection.
  • CGW core gateway
  • the control plane that is, the connection management device
  • obtains the current location of the access network determines whether there is a second forwarding plane currently present, and if there is a second forwarding plane, then controls
  • the information of the second access plane (such as its IP address) is obtained through the identifier of the current access network (such as the ID of the access base station or the information of the location area, such as the TA), and a corresponding tunnel is established.
  • the identifier information is sent to the first forwarding plane, and the uplink identifier information of the second forwarding plane is sent to the access network side to establish that the terminal device is connected to the first forwarding plane via the second forwarding plane.
  • the second type of path is sent to the first forwarding plane, and the uplink identifier information of the second forwarding plane is sent to the access network side to establish that the terminal device is connected to the first forwarding plane via the second forwarding plane.
  • the terminal device after determining to adjust the first type of path to the second type of path, the terminal device is also required to perform path type adjustment and notify the channel device of the second forwarding plane to be accessed.
  • the second forwarding plane (for example, the edge gateway EGW) may be used as the base station and the first forwarding plane in the handover message (for example, The peer end of the core gateway (CGW) tunnel, which can include:
  • the IP address and tunnel ID of the EGW downlink tunnel are used to inform the CGW as the downlink tunnel endpoint of the CGW; the IP address and tunnel ID of the EGW uplink tunnel are sent to the access network as the uplink tunnel endpoint of the access network.
  • the terminal device moves from the non-MEC region to the MEC region in the idle (IDLE) mode, when the UE initiates the service or the downlink data arrives at the network paging, the UE is triggered to initiate the session establishment, and the network determines whether to proceed according to the current location. Connection updates. If the update of the connection is required, the control plane is not a tunnel between the newly created CGW and the access network (AN, Access Network), but is established as a tunnel between the AN, the EGW, and the CGW.
  • AN Access Network
  • Scenario 2 is different from the scenario 1.
  • the scenario 1 is used to adjust the path of the first type to the path of the second type. This scenario is described for adjusting the path of the second type to the first type of path.
  • a path management unit configured to establish, by the second access device, a second type of path with the first forwarding plane by using the second access device, where the second access device and the terminal device are in a current location
  • the target access device is different in access;
  • the second access device is located at a location with a second forwarding plane or a second forwarding plane suitable for terminal device access;
  • the path adjusting unit is configured to determine that the terminal is not provided when the terminal device is currently located or does not have a second forwarding plane that is suitable for access by the terminal device.
  • the path between the device and the first forwarding plane is adjusted by the second type of path to the first type of path.
  • the path adjustment unit is configured to notify the first forwarding of the corresponding identification information of the access network after determining that the path between the terminal device and the first forwarding plane is adjusted to the first type of path by the second type of path. Notifying the identifier of the first forwarding plane to the access network to establish a first type of path between the terminal device and the first forwarding plane.
  • the control plane determines that the second forwarding plane of the current session (for example, the edge gateway EGW) is no longer needed, and then updates the connection.
  • the information of the intermediate EGW is no longer included, and the data channel of the user plane becomes the direct connection between the AN and the CGW.
  • the access network and the CGW are directly used as the opposite end of the tunnel: the corresponding tunnel ID and IP of the access network are sent to the CGW as The downstream tunnel endpoint of the CGW; the IP address and tunnel ID of the CGW tunnel are communicated to the access network as the upstream tunnel endpoint of the access network.
  • the network will further release the user plane tunnel between the EGW and the CGW through the location update.
  • the new tunnel is the AN and the CGW. Direct one-hop tunnel.
  • the path type may include direct A first type of path connected to the first forwarding plane and a second type of path hopped to the first forwarding plane by the second forwarding plane.
  • the flexibility and efficiency of the network architecture can be provided.
  • a gateway processing is implemented with a minimum number of hops, and the path type configuration can be performed only on the network side, and no more configuration is required on the terminal device side. Changes can enable access to edge network data.
  • This embodiment is mainly used for the second triggering situation, where the path adjusting unit is configured to determine whether the terminal is based on the access network corresponding to the location of the terminal device and the service type of the terminal device. The type of connection path between the device and the first forwarding plane is adjusted.
  • the determining based on the access network corresponding to the location of the terminal device, and the service type of the terminal device, determining whether to adjust the type of the connection path between the terminal device and the first forwarding plane a path management unit, configured to determine that the terminal device establishes a connection with the core network through a first type of path at a location where the terminal device is located;
  • the path adjusting unit is configured to: when the access network corresponding to the location where the terminal device is located, the second forwarding plane that can optimize the local service access path, and detect the terminal setting When the corresponding service type is switched from the first service type to the second service type, it is determined that the connection path between the terminal device and the first forwarding plane is adjusted from the first type path to the second type path;
  • the first service type is different from the second service type, the second service type is a service type that needs to be offloaded by the local service, and the first service type is a service type that does not need to be offloaded by the local service.
  • the path adjustment unit after the connection path between the terminal device and the first forwarding plane is adjusted from the first type of path to the second type of path, detecting that the terminal device completes the second service for the last time until the current time After the information of the type is exchanged, the duration of the information exchange of the second service type is stopped; when the duration exceeds the preset time limit, determining a connection path between the terminal device and the first forwarding plane is determined by the The second type of path is adjusted to the first type of path.
  • the path adjustment unit is configured to learn to trigger the update of the connection between the access network and the core network gateway when the UE initiates the edge or local service, and dynamically join the second forwarding plane (for example, the edge gateway EGW).
  • the UE is connected to the EGW to form a network architecture as shown in FIG. 4b.
  • the duration of information exchange between two types of services is adjusted to the second type of path by the first type of path.
  • the connection path between the terminal device and the first forwarding plane is adjusted by the second type path to the first type of path.
  • connection management device (the network side control plane) detects that the UE with the second forwarding plane does not access the services of the edge network for a period of time, and deletes the edge network gateway in the path, that is, switches from the second type of path to the first Class path.
  • connection management device learns that the terminal device accesses the edge or the local service includes at least one of the following:
  • the first method is to determine whether the first service type is switched to the second service type by using the service type information reported by the terminal device. That is, the UE informs the network: the UE is controlling The signaling sent by the plane includes service type information, and the network side determines that the service of the UE is suitable for the access edge or the local network by using the service type information, and then establishes an EGW connection.
  • connection management device needs to optimize the service access path of the terminal from the network side. Specifically, the connection management device perceives that the service of the UE is suitable for the access edge or the local network. For example, the user plane informs the control plane of the user's IP address through the user plane according to the service target address accessed by the user.
  • the third method is to receive the notification information sent by the server corresponding to the service used by the terminal device to determine the service type of the terminal device. For example, directly or through the capability open interface, the network user is required to establish a link to the edge network.
  • the connection management device senses that only the terminal device connected to the core layer needs to establish a data channel to the edge (or local) network or the data packet needs to be split at the edge, and the core network control plane triggers the second forwarding plane (or the network of the user plane) Function) Joins an existing data channel and updates the tunnel.
  • the data that needs to be routed in the edge network is forwarded and split through the second forwarding plane, and the other data flows reach the core layer gateway through the second forwarding plane, and then reach the core PDN network.
  • the terminal does not perceive changes in the network during this process.
  • the network senses that the connection with the second forwarding plane no longer needs the edge network data channel, the network triggers the update of the connection path, and deletes the second forwarding plane EGW in the transmission path. Enable all data to enter the PDN network through one hop.
  • the UE generates a data service, and the network determines that a second forwarding plane (for example, an edge gateway EGW) needs to be introduced to optimize the data channel, triggering the joining of the second forwarding plane to initiate a session update process for the access network, and the IP address and tunnel of the EGW uplink tunnel.
  • a second forwarding plane for example, an edge gateway EGW
  • the ID tells the access network as the upstream tunnel endpoint of the access network; the IP address and tunnel ID of the EGW downlink tunnel are told to the first forwarding plane (such as the core gateway (CGW) in the figure) as the downstream tunnel endpoint of the CGW.
  • the first forwarding plane such as the core gateway (CGW) in the figure
  • the step of deleting the EGW is triggered, which may include:
  • the path management unit is configured to initiate a session update process to the access network, and notify the access network of the IP address and tunnel ID of the uplink tunnel of the CGW, as an uplink tunnel end point of the access network;
  • the IP address and tunnel ID of the downlink tunnel entering the network tells the CGW to serve as the downstream tunnel endpoint of the CGW.
  • the path type may include direct A first type of path connected to the first forwarding plane and a second type of path hopped to the first forwarding plane by the second forwarding plane.
  • the flexibility and efficiency of the network architecture can be provided, and a gateway processing can be implemented with a minimum number of hops without local offloading, and access to edge network data can be realized without requiring more configuration changes on the terminal device side.
  • connection management device includes:
  • the communication interface 1301 detects related information of the terminal device
  • the processor 1302 determines, according to the related information of the terminal device, whether to adjust the type of the connection path between the terminal device and the first forwarding plane;
  • the type of the connection path between the terminal device and the first forwarding plane includes: the first type of path is a connection path directly established between the terminal device and the first forwarding plane by the terminal device; The path is a connection path established by the terminal device between the second forwarding plane and the first forwarding plane through the access network.
  • the related information of the terminal device includes: a location of the terminal device, and/or a current service type of the terminal device.
  • connection management device is mainly disposed in the core network, and the specific implementation may be set in one device in the core network, for example, may be set in the MME in the core network.
  • the manner of obtaining the location currently described by the terminal device may include: detecting an access device currently accessed by the terminal device, and acquiring identification information of the access device (such as an access device) The ID number of the access device is determined based on the identification information of the access device (for example, the core network side can determine the area code corresponding to the access device by using the identification information of the access device); Determining a location where the terminal device is currently located based on an area corresponding to the access device.
  • the access device may be a base station, or may be an access point (AP) or the like, and is used to provide a direct access mode device for the terminal device.
  • AP access point
  • the foregoing solution can provide two types of triggering situations, where the first triggering situation is to determine whether the terminal device is in an access network capable of performing local service offloading based on the change of the location of the terminal device, thereby determining Whether to adjust the path type of the terminal device; the second triggering situation is to determine whether the terminal device performs the path type adjustment in combination with the requirement of the local device for the local service offloading.
  • the first type of triggering situation when the terminal is connected in the session, the session only establishes a session connection for a core side gateway; when the UE moves to a range that can support the local offload gateway, the control plane initiates the establishment of a new tunnel, thereby The EGW joins the existing session, that is, the first type of path is switched to the second type of path; when the terminal moves out of the coverage of the EGW, the control plane can trigger a new tunnel establishment mechanism to delete the EGW from the session path. Create a second type of path to delete the first type of path.
  • Scenario 1 The processor 1302 determines that the terminal device establishes a first type of path with the first forwarding plane by using the first access device, where the first access device and the terminal device are currently located. The location of the access device to be accessed is different; the coverage area corresponding to the first access device does not have the second forwarding plane or is not suitable for accessing the second forwarding plane;
  • Determining between the terminal device and the first forwarding surface when the location where the terminal device is currently located can access the second forwarding plane or can access the second forwarding plane suitable for the terminal device
  • the path is adjusted from the first type of path to the second type of path. That is to say, the core network side can determine whether the location has a second forwarding plane that can optimize the local service access path according to the current location of the terminal device (such as the area code).
  • the connection management device when the terminal device first accesses the network, the connection management device is installed.
  • the device may determine the path type initially established by the terminal device based on whether the access network where the terminal device is located has a second forwarding plane.
  • the terminal device accesses the device for the first time.
  • the first type of path is established, as shown in FIG. 4a, and the first forwarding plane is directly connected; when the access network has the second forwarding plane, when the terminal device first accesses the network, it is established as shown in FIG. 4b.
  • the second type of path establishes a connection with the first forwarding plane via the second forwarding plane.
  • the control plane that is, the connection management device
  • obtains the current location of the access network determines whether there is a second forwarding plane currently present, and if there is a second forwarding plane, then controls
  • the information of the current access network (such as the ID of the access base station or the information of the location area such as TA) is used to obtain the information of the second forwarding plane (EGW) (such as its IP address), and a corresponding tunnel is established.
  • EGW second forwarding plane
  • the identifier information is sent to the first forwarding plane, and the uplink identifier information of the second forwarding plane is sent to the access network side to establish that the terminal device is connected to the first forwarding plane via the second forwarding plane.
  • the second type of path is sent to the first forwarding plane, and the uplink identifier information of the second forwarding plane is sent to the access network side to establish that the terminal device is connected to the first forwarding plane via the second forwarding plane.
  • the terminal device after determining to adjust the first type of path to the second type of path, the terminal device is also required to perform path type adjustment and notify the channel device of the second forwarding plane to be accessed.
  • the second forwarding plane (eg, EGW) may be used as a peer end of the base station and the first forwarding plane (eg, CGW) tunnel in the handover message, and may include :
  • the IP address and tunnel ID of the EGW downlink tunnel are used to inform the CGW as the downlink tunnel endpoint of the CGW; the IP address and tunnel ID of the EGW uplink tunnel are sent to the access network as the uplink tunnel endpoint of the access network.
  • the terminal device moves from the non-MEC region to the MEC region in the idle (IDLE) mode, when the UE initiates the service or the downlink data arrives at the network paging, the UE is triggered to initiate the session establishment, and the network determines whether to proceed according to the current location. Connection updates. If you need to connect In the subsequent update, the control plane is not a tunnel between the newly created CGW and the access network (AN, Access Network), but is established as a tunnel between the AN, the EGW, and the CGW.
  • AN Access Network
  • Scenario 2 is different from the scenario 1.
  • the scenario 1 is used to adjust the path of the first type to the path of the second type. This scenario is described for adjusting the path of the second type to the first type of path.
  • the processor 1302 the terminal device establishes a second type of path with the first forwarding plane by using the second access device, where the second access device and the terminal device are in the current location
  • the target access device is different in access;
  • the second access device is located at a location with a second forwarding plane or a second forwarding plane suitable for terminal device access;
  • Determining a path between the terminal device and the first forwarding surface when the location where the terminal device is currently located does not have a second forwarding plane or does not have a second forwarding plane suitable for access by the terminal device The second type of path is adjusted to the first type of path.
  • the processor 1302 after determining that the path between the terminal device and the first forwarding plane is adjusted to the first type of path by the second type of path, notifying the first forwarding plane of the corresponding identification information of the access network, Notifying the access network of the first forwarding plane to establish a first type of path between the terminal device and the first forwarding plane.
  • the control plane determines that the second forwarding plane of the current session is no longer needed, and the connection update does not include the information of the intermediate EGW, the data of the user plane.
  • the channel becomes an AN directly connected to the CGW.
  • the access network and the CGW are directly used as the opposite end of the tunnel: the corresponding tunnel ID and IP of the access network are sent to the CGW as The downstream tunnel endpoint of the CGW; the IP address and tunnel ID of the CGW tunnel are communicated to the access network as the upstream tunnel endpoint of the access network.
  • the network will further release the user plane tunnel between the EGW and the CGW through the location update.
  • the new tunnel is the AN and the CGW. Direct one-hop tunnel.
  • the processor 1302 determines whether to adjust the type of the connection path between the terminal device and the first forwarding plane based on the access network corresponding to the location of the terminal device and the service type of the terminal device.
  • the determining based on the access network corresponding to the location of the terminal device, and the service type of the terminal device, determining whether to adjust the type of the connection path between the terminal device and the first forwarding plane a path management unit, configured to determine that the terminal device establishes a connection with the core network through a first type of path at a location where the terminal device is located;
  • the access network corresponding to the location where the terminal device is located is provided with the second forwarding plane that can optimize the local service access path, and the service type corresponding to the terminal device is detected to be switched from the first service type to the second service type. Determining that the connection path between the terminal device and the first forwarding plane is adjusted from the first type path to the second type path;
  • the first service type is different from the second service type, the second service type is a service type that needs to be offloaded by the local service, and the first service type is a service type that does not need to be offloaded by the local service.
  • the processor 1302 after the connection path between the terminal device and the first forwarding plane is adjusted to the second type of path by the first type of path, detecting that the terminal device completes the second service type last time until the current time After the information is exchanged, the duration of the information exchange of the second service type is stopped; when the duration exceeds the preset time limit, the connection path between the terminal device and the first forwarding plane is determined by the second class. The path is adjusted to the first type of path.
  • the processor 1302 learns that when the UE initiates an edge or local service, it triggers the update of the connection between the access network and the core network gateway, dynamically joins the function of the second forwarding plane, and establishes a connection between the UE and the EGW, forming a connection.
  • the solution is the network architecture shown in Figure 4b.
  • the duration of information exchange between two types of services is adjusted to the second type of path by the first type of path.
  • the connection path between the terminal device and the first forwarding plane is adjusted by the second type path to the first type of path.
  • connection management device (the network side control plane) detects that the UE with the second forwarding plane does not access the services of the edge network for a period of time, and deletes the edge network gateway in the path, that is, switches from the second type of path to the first Class path.
  • connection management device learns that the terminal device accesses the edge or the local service includes at least one of the following:
  • the first method is to determine whether the first service type is switched to the second service type by using the service type information reported by the terminal device. That is, the UE informs the network that the signaling sent by the UE to the control plane includes the service type information, and the network side determines that the service of the UE is suitable for the access edge or the local network by using the service type information, and then establishes an EGW connection.
  • the processor 1302 needs to optimize the service access path of the terminal from the network side. Specifically, the connection management device perceives that the service of the UE is suitable for the access edge or the local network. For example, the user plane informs the control plane of the user's IP address through the user plane according to the service target address accessed by the user.
  • the third method is to receive the notification information sent by the server corresponding to the service used by the terminal device to determine the service type of the terminal device. For example, directly or through the capability open interface, the network user is required to establish a link to the edge network.
  • the connection management device senses that only the terminal device connected to the core layer needs to establish a data channel to the edge (or local) network or the data packet needs to be split at the edge, and the core network control plane triggers the second forwarding plane (or the network of the user plane) Function) Joins an existing data channel and updates the tunnel.
  • the data that needs to be routed in the edge network is forwarded and split through the second forwarding plane, and the other data flows reach the core layer gateway through the second forwarding plane, and then reach the core PDN network.
  • the terminal does not perceive changes in the network during this process.
  • the network senses that the connection with the second forwarding plane no longer needs the edge network data channel, the network triggers the update of the connection path, and deletes the second forwarding plane EGW in the transmission path. Enable all data to enter the PDN network through one hop.
  • the UE generates a data service, and the network determines that the second forwarding plane is used to optimize the data channel, and the joining control of the second forwarding plane is triggered to initiate a session update process for the access network, and the IP address and tunnel ID of the EGW uplink tunnel are sent to the access network as The upstream tunnel endpoint of the access network; the IP address and tunnel ID of the EGW downlink tunnel are told to the CGW as the downstream tunnel endpoint of the CGW.
  • the step of deleting the EGW is triggered, which may include:
  • the path management unit is configured to initiate a session update process to the access network, and notify the access network of the IP address and the tunnel ID of the CGW uplink tunnel as the uplink tunnel endpoint of the access network; and the downlink tunnel of the access network
  • the IP address and tunnel ID tell the CGW as the downstream tunnel endpoint of the CGW.
  • the path type may include direct A first type of path connected to the first forwarding plane and a second type of path hopped to the first forwarding plane by the second forwarding plane.
  • the flexibility and efficiency of the network architecture can be provided, and a gateway processing can be implemented with a minimum number of hops without local offloading, and access to edge network data can be realized without requiring more configuration changes on the terminal device side.
  • a connection management apparatus in an embodiment of the present invention includes: a processor and a memory for storing a computer program executable on the processor,
  • a computer storage medium is provided by the embodiment of the present invention.
  • the computer storage medium stores computer executable instructions. When the computer executable instructions are executed, the method steps of the first embodiment or the second embodiment are implemented.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种连接管理方法及装置、计算机存储介质，所述方法包括：检测终端设备的相关信息；基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面第二转发面与第一转发面之间建立的连接路径。

Description

一种连接管理方法及装置、计算机存储介质
相关申请的交叉引用
本申请基于申请号为201610889291.3、申请日为2016年10月11日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明涉及通信领域中的连接管理技术，尤其涉及一种连接管理方法及装置、计算机存储介质。
背景技术
移动网络架构中，核心网的网元(或网络功能)由控制面和用户面两部分功能组成。在传统的网络架构中，如3G/4G的网络中，用户面网关往往集中部署，在离用户相对较远的核心层。移动网络为了满足低时延、大带宽场景，在4G网络架构的优化或5G网络新架构的设计中将用户面功能下沉，部署于网络边缘，从而降低传输时延，减轻回传网络的传输压力。
现有技术中，现有实现边缘业务分流的方案有两类：多会话(连接)方案、以及单会话(或连接)方案。但是，上述两种连接方案要么需要终端设备维持过多的配置信息以维持多个会话连接，要么针对访问核心侧PDN网络的数据来说，增加了网络处理的复杂性和时延。可以看出，现有技术中进行边缘业务分流的网络架构无法进行灵活的调整，并且无法保证减少终端设备侧的配置处理。
发明内容
本发明的主要目的在于提出一种连接管理方法及装置、计算机存储介 质，旨在解决现有技术中存在的上述问题。
为实现上述目的，本发明提供的一种连接管理方法，所述方法包括：
检测终端设备的相关信息；
基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面第二转发面与第一转发面之间建立的连接路径。
本发明实施例提供了一种连接管理装置，包括：
信息获取单元，检测终端设备的相关信息；
路径调整单元，基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面与第一转发面之间建立的连接路径。
本发明实施例提供了一种连接管理装置，所述连接管理装置包括：
通信接口，检测终端设备的相关信息；
处理器，基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面与第一转发面之间建立的连接路径。
本申请提供一种连接管理装置，包括：处理器和用于存储能够在处理 器上运行的计算机程序的存储器，
其中，所述处理器用于运行所述计算机程序时，执行前述方法的步骤。
本申请提供一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实现前述方法步骤。
本发明提出的一种连接管理方法及装置、计算机存储介质，就能够至少基于终端设备所移动至的位置对应的接入网，确定是否对终端设备与第一转发面之间的路径类型进行调整，具体来说，路径类型可以包括有直接连接到第一转发面的第一类路径，以及通过第二转发面连接到第一转发面的第二类路径。如此，就能够提供网络架构的灵活性以及高效性，无本地分流时以最少跳数实现一个网关处理，以及仅在网络侧进行路径类型的配置即可，不需要终端设备侧进行较多的配置改变就能够实现边缘网络数据的访问。
附图说明
图1为本发明实施例连接管理方法流程示意图一；
图2为本发明实施例处理场景示意图一；
图3为本发明实施例处理场景示意图二；
图4a为本发明实施例第一类路径示意图；
图4b为本发明实施例第二类路径示意图；
图5为本发明实施例处理场景示意图二；
图6为本发明实施例连接管理方法流程示意图二；
图7为本发明实施例连接管理方法流程示意图三；
图8为本发明实施例连接管理方法流程示意图四；
图9为本发明实施例连接管理方法流程示意图五；
图10为本发明实施例连接管理方法流程示意图六；
图11为本发明实施例连接管理方法流程示意图七；
图12为本发明实施例连接管理装置组成结构示意图一；
图13为本发明实施例连接管理装置组成结构示意图二。
具体实施方式
下面结合附图和具体实施例对本发明作进一步详细说明。
实施例一、
本发明实施例提供了一种连接管理方法，应用于连接管理装置，包括：检测终端设备的相关信息；
基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面第二转发面与第一转发面之间建立的连接路径。
其中，所述终端设备的相关信息，包括：终端设备的位置、和/或、所述终端设备当前的业务类型。
具体来说，如图1所示，包括：
步骤101：检测终端设备的位置、和/或、检测所述终端设备当前的业务类型；
步骤102：基于所述终端设备的位置和/或所述终端设备当前的业务类型，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面与第一转发面之间建立的连接路径。
这里，所述连接管理装置主要设置在核心网中，具体的实现可以为一 个模块设置在核心网中的某一个设备中，比如，可以设置在核心网中的MME中。所述第一转发面为核心用户面，第二转发面为边缘用户面。
进一步地，上述检测终端设备的位置、和/或、检测所述终端设备当前的业务类型，也就是，获取到终端设备的位置，可以为获取所述终端设备当前移动至的位置，也就是所述终端设备当前所述的位置；具体方式可以包括：检测所述终端设备当前所要接入的目标接入装置，获取到该目标接入装置的标识信息(比如接入装置的ID号)；基于所述目标接入装置的标识信息确定所述接入装置对应的区域(比如，核心网侧能够通过接入装置的标识信息确定所述接入装置对应的区域码)；基于所述接入装置对应的区域确定所述终端设备当前所处的位置。
其中，所述接入装置可以为基站、或者，还可以为接入点(AP)等，用于为终端设备提供直接接入方式的装置。
具体来讲，上述方案中能够具备两种触发情况，其中第一种触发情况就是基于终端设备的位置的变化，来判断终端设备是否处于能够进行本地业务分流的接入网中，从而来确定是否对终端设备的路径类型进行调整；另外第二种触发情况就是结合终端设备是否有本地业务分流，或者有业务数据传输路径优化的需求，来判断终端设备是否进行路径类型的调整。
本实施例主要针对上述第一种触发情况，终端在会话连接时，默认只建立面向一个核心侧网关的会话连接；当UE移动到可支持本地分流网关的范围内时，由控制面发起建立新的隧道，从而将该EGW加入到已有会话中，也就是由第一类路径切换至第二类路径；当终端移动出EGW的覆盖范围(接入网不包含EGW)时，控制面可以触发新的隧道建立机制，将EGW从会话路径中删除，建立第二类路径删除第一类路径。
场景一、所述获取到所述终端设备所处的位置之前，所述方法还包括：
所述终端设备通过第一接入装置与所述第一转发面建立第一类路径；其中，所述第一接入装置与所述终端设备在当前所处的位置所要接入的目 标接入装置不同；所述第一接入装置所对应的覆盖范围内不具备第二转发面或不适合接入到第二转发面；
相应的，所述至少基于所述终端设备所处的位置对应的接入网，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整，包括：
当所述终端设备当前所处的位置处能够接入第二转发面(也就是边缘侧用户面)或能够接入所述终端设备适合的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第一类路径调整为第二类路径。也就是说，核心网侧能够根据终端设备当前所处的位置(比如区域码)来确定该位置处，是否具备可优化本地业务访问路径边缘侧用户面(第二转发面)。
本实施例的处理场景可以参见图2，当终端设备，比如UE，从接入网1到接入网2之间产生移动，其中，接入网1对应的即为第一接入装置，接入网2对应的即为UE所要接入的目标接入装置对应的接入网；相应的，当UE在接入网1的时候，连接管理装置确定UE当前采用第一类路径，即图中所示通过接入网1接入第一转发面(比如图中的核心网关(CGW))，最终由核心网(具体可以为核心公用数据网(PDN，Public Data Network)网络)进行数据处理；另外，当UE移动到接入网2也就是所要接入的目标接入装置所在的网络中的时候，网络侧，具体的可以为连接管理装置对UE与核心网之间的路径类型进行了切换，切换为第二类路径，也就是通过第二转发面(比如，边缘网关EGW)与核心网关CGW建立的连接，通过第二类路径，能够将一部分需要本地分流的业务分流到边缘PDN网中，另外一部分需要核心PDN网络进行处理的业务通过CGW送到核心PDN网络中进行处理。
上述第一接入装置与所述终端设备在当前所处的位置所要接入的目标接入装置不同，具体来说，可以参见图3，终端设备的第一位置31可以为其中的接入网1即第一接入装置覆盖范围内的一个位置，随着终端设备进 行移动，到了当前所处的位置32，(需要理解的是，终端设备进行移动有可能移动之后还是位于接入网1内，也可以处于接入网2内，本实施例主要针对产生接入网改变的场景进行说明也就是图3所示的场景)，位置32位于接入网2内，也就是终端设备所要接入的目标接入装置所在的网络；进一步地，接入网1中不具备或不适合接入第二转发面(比如，图中边缘网关EGW)，也就是说，接入网1不能够提供本地业务分流，接入网2中具备可优化本地业务访问路径第二转发面(比如，图中边缘网关EGW)，也就是说，接入网2能够提供本地业务分流，那么基于终端设备所处的接入网不同，能够调整终端设备与核心网建立连接的类型。
需要理解的是，本场景下，当终端设备初次接入网络时，连接管理装置可以基于终端设备所在接入网是否具备第二转发面(比如，边缘侧用户面，或者为边缘网关)，来确定终端设备初次建立的路径类型，当接入网不具备或不适合接入第二转发面时，那么终端设备初次接入到网络时，就建立第一类路径，如图4a所示直接与核心网关建立连接；当接入网具备边缘网关时，终端设备初次接入网络时，建立如图4b所示的第二类路径，经由边缘网关与核心网关建立连接，具体来说通过边缘网关接入本地网进行业务分流，以及将部分业务路由到核心网关以通过核心网，比如数据网进行数据处理。
终端设备，比如，UE，移动到新的位置后，控制面(也就是连接管理装置)获取接入网当前的位置，判断当前是否有第二转发面存在，如果存在第二转发面，则控制面通过当前接入网的标识(如接入基站的ID或者位置区域的信息如TA)获取第二转发面的信息(如其IP地址)，建立相应的隧道。
若确定所述终端设备与所述第一转发面之间的路径需要由第一类路径调整为第二类路径，则为所述终端设备选取对应的第二转发面，将第二转发面的标识信息发送给第一转发面作为第一转发面下行隧道的信息、并将 所述第二转发面的标识信息发至接入网侧作为接入侧上行隧道的信息，以建立所述终端设备通过接入装置(所在位置所要接入的目标接入装置对应的接入网)经由所述第二转发面连接所述第一转发面之间的第二类路径。
也就是说，确定将第一类路径调整为第二类路径后，还需要通知终端设备进行路径类型的调整以及通知通道设备所要接入的第二转发面。
具体来说，如果终端设备在连接状态下发生移动，则可以在切换消息中，将第二转发面，比如边缘网关(EGW)作为基站和核心侧网关(CGW)隧道的对端，可以包括：
把EGW下行隧道的IP地址和隧道ID告诉CGW作为CGW的下行隧道端点；把EGW上行隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点。
如果终端设备在空闲(IDLE)模式下由非MEC区域移动到MEC区域，当UE主动发起业务或者有下行数据到来网络寻呼后，触发UE发起会话建立时，网络根据当前的位置，判断是否进行连接的更新。如果需要进行连接的更新，则控制面不是新建CGW和接入网(AN，Access Network)间的隧道，而是建立成为一个AN、EGW、CGW间的隧道。
场景二、与场景一不同之处在于，场景一针对第一类路径调整为第二类路径进行的介绍，本场景则针对将第二类路径调整为第一类路径进行说明。
所述终端设备通过第二接入装置与所述第一转发面建立第二类路径；其中，所述第二接入装置与所述终端设备在当前所处的位置所要接入的目标接入装置不同；所述第二接入装置所处的位置处具备第二转发面或具备适合终端设备接入的第二转发面；
当所述终端设备当前所处的位置处不具备第二转发面或不具备适合所述终端设备接入的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
所述第二接入装置与所述终端设备在当前所处的位置所要接入的目标接入装置不同，具体来说，可以参见图5，终端设备的第二位置51可以为其中的第二接入装置的接入网1内的一个位置，随着终端设备进行移动，到了当前所处的位置52，(需要理解的是，终端设备进行移动有可能移动之后还是位于接入网1内，也可以处于接入网2内，本实施例主要针对产生接入网改变的场景进行说明也就是图中所示的场景)，位置52位于接入网2内，接入网2对应的即为终端设备所要接入的目标接入装置；进一步地，接入网1中具备第二转发面(比如，图中边缘网关EGW)，也就是说，接入网1能够提供本地业务分流，接入网2中不具备或不适合接入第二转发面(比如，图中边缘网关EGW)，也就是说，接入网2不能够提供本地业务分流，那么基于终端设备所处的接入网不同，就需要将终端设备由第二类路径调整为第一类路径。
若确定所述终端设备与所述第一转发面之间的路径需要由第二类路径调整为第一类路径后，则将接入网相应的标识信息通知第一转发面、将所述第一转发面的标识信息通知给所述接入网，以建立所述终端设备与所述第一转发面之间的第一类路径。
终端设备移动到新的位置后，通过接入网当前的位置，控制面判断当前会话第二转发面不再需要时，则其连接的更新中不再包含中间的EGW的信息，用户面的数据通道变成AN与CGW直连。
具体说来，连接状态，在发生从MEC区域到MEC外的区域的切换消息中，直接将接入网和CGW互相作为对方的隧道对端：把接入网相应的隧道ID和IP告诉CGW作为CGW的下行隧道端点；把CGW隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点。
UE如果是空闲状态移动到MEC外的区域时，则网络将通过位置更新，进一步释放掉EGW和CGW之间的用户面隧道，在下一次终端由空闲变成Active时，新的隧道是AN和CGW直接的一跳的隧道。
场景三、与场景二不同之处在于，本场景提供了一种切换回第一类路径的判断方式：当终端设备处于不再与原第二转发面建立连接的位置时，就切换回第一类路径。
所述获取终端设备当前所处的位置之前，所述方法还包括：
所述终端设备通过第二接入装置、经由第二转发面与所述第一转发面建立第二类路径；其中，所述第二接入装置与所述终端设备在当前所处的位置所要接入的目标接入装置不同；
相应的，所述基于所述终端设备当前所处的位置和/或所述终端设备当前的业务类型，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整，包括：
当所述终端设备当前所处的位置处不能够接入所述第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
判断是否能够接入到第二转发面的方式可以基于核心网侧保存的每一个第二转发面对应的物理位置来确定，当终端设备当前所述的位置，比如区域码，对应的覆盖范围内不包含有第二转发面时，就可以确定当前无法继续连接第二类路径，那么就调整会第一类路径。
进一步地，上述终端设备当前所处的位置所要接入的目标接入装置的确定方式可以为，当终端设备在切换过程中时，通过切换流程获取到终端设备可以向网络侧发送多个能够接入的接入装置的切换请求，最终能够为终端设备选取一个目标接入装置，也就是本实施例中所述的终端设备当前所述的位置处所要接入的目标接入装置。
下面分别结合附图对本实施例提供的基于终端设备的位置及接入网进行路径类型的调整的示例进行说明：
示例一、
当终端移动，发生第二转发面(比如，图中边缘网关EGW)的动态加 入时，其流程如图6所示：
1、终端(UE)已经建立经过原接入网节点1、CGW并到达核心PDN网络的数据传输通道，也就是已经建立第一类路径。
2、当终端移动到接入网节点2的覆盖范围时，接入网节点2向控制面发起切换请求。此切换请求中包含接入网节点2的位置信息。该实施例中接入网节点2为所要接入的目标接入装置。
3、控制面(具体的比如为连接管理装置)通过接入网节点2的位置信息，判断该区域是否有EGW部署。如有EGW部署，则根据位置信息、负载均衡等策略选择一个合适的EGW实现本地分流。控制面向CGW发送隧道更新请求(比如，可以为路径更新请求)，将该EGW的IP地址和隧道ID作为CGW的下行隧道的端点。
4、控制面向接入网节点2(即UE所要接入的目标接入装置)发送隧道更新请求，将该EGW的IP地址和隧道ID作为接入网节点2上行隧道的端点。
5、控制面向EGW发送隧道更新请求，将该CGW的IP地址和隧道ID作为EGW的上行隧道的端点，将接入网节点2的IP地址和隧道ID作为EGW的下行隧道端点，即建立第二类路径。
6、控制面向接入网节点2发送路径切换回复，确认完成handover过程。
以上实施例流程可相应扩展至终端附着流程。以上接入网节点可扩展至第三方接入基站(如基于第三方WLAN选择EGW)
示例二、
当终端移动发生第二转发面(比如，图中边缘网关EGW)的动态删除，其流程如图7所示：
1、终端(UE)已经建立如图所示的一条串接传输通道。本地分流数据经过接入网节点1、EGW到边缘网络；其他数据经过接入网节点1、EGW、CGW到核心PDN网络，即已建立第二类路径。
2、当终端移动到接入网节点2的覆盖范围时，接入网节点2向控制面发起切换请求。此切换请求中包含接入网节点2的位置信息。
3、控制面(具体的比如为连接管理装置)通过接入网节点2的位置信息，判断该区域是否有EGW部署。如没有EGW部署，则进行相应的隧道链路调整。控制面向CGW发送隧道更新请求，将该接入网节点2的IP地址和隧道ID作为CGW的下行隧道的端点。
4、控制面向接入网节点2发送隧道更新请求，将该CGW的IP地址和隧道ID作为接入网节点2上行隧道的端点。
5、控制面向EGW发送隧道更新请求，释放EGW的相关隧道资源，也就是从第二类路径切换至第一类路径。
6、控制面向接入网节点2发送路径切换回复，确认完成handover过程。
示例三、
当UE以Idle状态移动，并进入了EGW的覆盖区域，若此时从idle状态转变为active状态，其EGW的加入流程如图8所示：
1、控制面向CGW发送隧道创建或更新请求，将该EGW的IP地址和隧道ID作为CGW的下行隧道的端点。
2、控制面向接入网节点发送隧道创建请求，将该EGW的IP地址和隧道ID作为接入网节点的上行隧道端点。
3、4、控制面向EGW发送隧道创建请求，将该CGW的IP地址和隧道ID作为上行隧道端点，将接入网节点的IP地址和隧道ID作为下行隧道端点，也就是从第一类路径切换至第二类路径。
5、控制面向接入网节点2发送路径切换完成回复，确认完成handover过程。
示例四：当UE以Idle状态移动，移动出了EGW的覆盖区域，其EGW的删除流程如图9所示：
1、UE因为移动发生位置跟踪区域的改变，发起位置更新消息
2、控制面根据位置更新消息及新的位置区域，判断移出MEC区域后，控制面向EGW发送隧道删除请求，释放相关隧道资源
3、控制面向CGW发送隧道删除请求，释放相关隧道资源，即由第二类路径替换为第一类路径。
示例五、
可以同时考虑终端设备的位置以及业务类型两个相关信息来进行判断；
比如，可以同时考虑当前终端设备所处位置对应的接入网是否具备第二转发面、以及终端设备的业务类型，来综合判断是否触发路径切换。具体说明如下：
当所述终端设备对应的业务类型由第一业务类型切换为第二业务类型时，并且此时终端设备所处位置的接入网具有第二转发面覆盖，则可确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径。
可见，通过采用上述方案，就能够至少基于终端设备所处位置对应的接入网，确定是否对终端设备与第一转发面之间的路径类型进行调整，具体来说，路径类型可以包括有直接连接到第一转发面的第一类路径，以及通过第二转发面跳接到第一转发面的第二类路径。如此，就能够提供网络架构的灵活性以及高效性，无本地分流时以最少跳数实现一个网关处理，以及仅在网络侧进行路径类型的配置即可，不需要终端设备侧进行较多的配置改变就能够实现边缘网络数据的访问。
实施例二、
与实施例一不同之处在于，本实施例主要针对第二种触发情况进行说明，所述至少基于所述终端设备所处的位置对应的接入网，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整，在本实施例提供的场景下，可以仅基于终端设备的业务类型来判断是否触发路径切换，而 接入网的覆盖范围内是否具备有第二转发面并非主要考虑的因素，假设接入网中具备第二转发面时，而终端设备业务类型需要触发路径优化时，可以从逻辑上距离接入网较近的第二转发面建立连接以为终端设备提供第二类路径，具体说明如下：当所述终端设备对应的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型、所述第一业务类型为不需要进行本地业务分流的业务类型。
进一步地，所述基于所述终端设备所处位置对应的接入网、以及所述终端设备的业务类型，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整之前，所述方法还包括：所述终端设备在所处的位置通过第一类路径与所述核心网之间建立连接；
相应的，所述基于所述终端设备所处位置对应的接入网、以及所述终端设备的业务类型，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整，包括：当所述终端设备所处的位置对应的接入网中具备可优化本地业务访问路径第二转发面、且检测到所述终端设备对应的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型、所述第一业务类型为不需要进行本地业务分流的业务类型。
也就是说，连接管理装置获知当UE发起边缘或本地业务时，触发接入网和核心网网关连接的更新，动态的加入第二转发面(比如，边缘网关EGW)的功能，建立UE与EGW的连接，形成方案如图4b所示的网络架构。
所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二 类路径后，检测截止到当前时刻所述终端设备最后一次完成第二业务类型的信息交互后、停止第二业务类型的信息交互的时长；
当所述时长超过预设时长门限值时，确定将所述终端设备与第一转发面之间的连接路径由所述第二类路径调整为第一类路径。
连接管理装置(网络侧控制面)感知到一个有第二转发面的UE在一段时间内不访问边缘网络的业务时，在路径中删除边缘网络网关，也就是从第二类路径切换至第一类路径。
连接管理装置获知终端设备访问边缘或本地业务的方式包括以下至少之一：
方式一、通过所述终端设备上报的业务类型信息，确定所述终端设备是否有第一业务类型切换为第二业务类型。就是UE告知网络：UE向控制面发送的信令中包含业务类型信息，网络侧通过业务类型信息判断该UE的业务适合访问边缘或本地网络，则建立EGW连接。
方式二、连接管理装置从网络侧感知终端的业务访问路径需要优化。具体的，连接管理装置感知UE的业务适合访问边缘或本地网络，比如，用户面根据用户访问的业务目标地址等，通过用户面告知控制面该用户的IP地址。
方式三、接收所述终端设备使用的业务对应的服务器侧发来的通知信息来确定终端设备的业务类型；比如，直接或通过能力开放接口告知网络某用户需要建立到边缘网络的链路。
连接管理装置感知仅有到核心层连接的终端设备需要建立到边缘(或本地)网络的数据通道或数据包需要在边缘分流时，核心网控制面触发将第二转发面(或用户面的网络功能)加入到已有数据通道中并更新隧道。使得需要在边缘网络路由的数据通过第二转发面转发和分流，其它的数据流则经过第二转发面到达核心层网关，进而到达核心PDN网络。终端在这个过程中不感知网络的变化。当网络感知具有第二转发面的连接不再需要 边缘网络数据通道时，网络触发连接路径的更新，删除传输路径中的第二转发面(比如，边缘网关EGW)。使得所有的数据能够通过一跳进入PDN网络。
UE发生数据业务，网络判断需引入第二转发面(比如，边缘网关EGW)优化数据通道，触发第二转发面的加入控制面向接入网发起会话更新流程，把EGW上行隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点；把EGW下行隧道的IP地址和隧道ID告诉CGW作为CGW的下行隧道端点。
判断该终端设备在一段时间内没有访问本地缓存的业务，则触发删除EGW的步骤，具体可以包括：
A)向接入网(目标接入装置)发起会话更新流程，把CGW的上行隧道的IP地址和隧道ID告诉接入网(目标接入装置)，作为接入网的上行隧道端点；
B)把接入网(目标接入装置)的下行隧道的IP地址和隧道ID告诉CGW作为CGW的下行隧道端点。
下面结合附图针对本实施例提供的场景进行示例说明：
示例一、
当网络侧判断UE发起的业务可以进行本地分流时，其EGW加入流程图10所示：
1、终端(UE)已经建立经过原接入网节点1、CGW并到达核心PDN网络的数据传输通道，也就是已经建立第一类路径。即UE已经通过接入网的接入装置与第一转发面建立第一类路径。
2、当终端UE发起业务建立请求，携带业务类型信息到控制面。网络控制面通过判断该业务类型能否进行本地分流。如该业务为MEC业务，则建立终端到EGW，再到CGW的如图2的网络连接。3、4、5、6步骤与图6(即实施例一种的示例一)相同，这里不再进行赘述。
另外，2的步骤也可以是：控制面与CGW交互，判断终端是否访问MEC业务。若是则3、4、5步骤与图4一致。
2的步骤也可以是：控制面与能力开放平台接口交互，判断该终端是否访问MEC业务，若是则3、4、5步骤与图4一致。
示例二、
当网络侧判断UE发起的业务已经结束本地分流时，其EGW删除流程如图11所示：
1、终端(UE)已经建立如图所示的一条串接传输通道。本地分流数据经过接入网节点1、EGW到边缘网络；其他数据经过接入网节点1、EGW、CGW到核心PDN网络，即已建立第二类路径。
2、控制面向EGW发送业务检测请求，检测终端是否有MEC业务在运行。EGW向控制面回复MEC业务已经结束。控制面触发流程，将该EGW删除。3、4、5、6与图7(实施例一种的示例二)步骤一致。
2的步骤也可以是控制面与能力开放接口交互，判断该终端是否结束访问MEC业务。若结束则3、4、5步骤与图5一致。
当终端移动到有第二转发面(比如，边缘网关EGW)服务的区域(MEC)时，网络控制面在隧道更新的相关流程中，如连接态的切换或者终端发起会话建立的流程中，动态的将EGW引入到用户面隧道的路径中。即，由AN<->CGW,变为AN<->EGW<->CGW
在切换消息流程中，把EGW的下行标识信息，可以但不限于下行隧道的IP地址和隧道ID告知CGW作为CGW的下行隧道端点；把EGW的上行标识信息，可以但不限于上行隧道的IP地址和隧道ID告知接入网，作为接入网的上行隧道端点
当终端移出MEC区域时，网络控制面在隧道更新的相关流程中，如连接态的切换或者终端发起会话建立的流程中，建立一个AN到核心侧网关直达的隧道，即由AN<->CGW
控制面把接入网相应的的标识信息，可以但不限于隧道ID和IP地址，通知CGW作为CGW的下行隧道端点；把CGW的标识信息，标识信息可以但不限于IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点
上述直达隧道或者经过EGW中转的隧道，除了UE发生移动，UE发起相关流程进行相互转化外，网络还可以根据用户业务来判断，由网络侧来触发两类隧道间的切换。
网络侧通过业务类型判断需引入第二转发面优化数据通道：
UE告知网络：UE向控制面发送的信令中包含业务类型信息，网络侧通过业务类型信息判断该UE的业务适合访问边缘或本地网络，则建立EGW连接。
网络自主感知UE业务适合访问边缘或本地网络：如用户面根据用户访问的业务目标地址等。用户面告知控制面该用户的IP地址。
业务侧直接或通过能力开放接口告知网络某用户需要建立到边缘网络的链路
与现有技术相比，本实施例终端在会话连接时，不需要为了实现MEC(或者本地分流)而引入多个IP地址，只有一个IP地址锚点。当终端不在EGW覆盖范围内，或者网络判断不需要进行本地分流，则EGW会被动态删除，从而实现数据包只需要经过一个CGW，一跳进入核心PDN网络，保持了网络扁平化的特性。当终端在EGW覆盖范围内，并且网络判断需要进行本地分流时，则EGW会被动态加入网络，从而实现本地分流。对终端可以做到无感知，简化了终端的行为，同时也便于网络对边缘流量转发策略的统一配置和管理。
可见，通过采用上述方案，就能够至少基于终端设备所处位置对应的接入网，确定是否对终端设备与第一转发面之间的路径类型进行调整，具体来说，路径类型可以包括有直接连接到第一转发面的第一类路径，以及通过第二转发面跳接到第一转发面的第二类路径。如此，就能够提供网络 架构的灵活性以及高效性，无本地分流时以最少跳数实现一个网关处理，以及不需要终端设备侧进行较多的配置改变就能够实现边缘网络数据的访问。
实施例三、
本发明实施例提供了一种连接管理装置，如图12所示，所述连接管理装置包括：
信息获取单元1201，检测终端设备的相关信息；
路径调整单元1202，基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面与第一转发面之间建立的连接路径。
其中，所述终端设备的相关信息，包括：终端设备的位置、和/或、所述终端设备当前的业务类型。
信息获取单元1201，用于获取终端设备当前所处的位置、和/或、获取所述终端设备当前的业务类型；
路径调整单元1202，用于基于所述终端设备当前所处的位置和/或所述终端设备当前的业务类型，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面与第一转发面之间建立的连接路径。
这里，所述连接管理装置主要设置在核心网中，具体的实现可以为一 个模块设置在核心网中的某一个设备中，比如，可以设置在核心网中的MME中。
上述获取到终端设备当前所述的位置的方式可以包括：检测所述终端设备当前所接入的接入装置，获取到该接入装置的标识信息(比如接入装置的ID号)；基于所述接入装置的标识信息确定所述接入装置对应的区域(比如，核心网侧能够通过接入装置的标识信息确定所述接入装置对应的区域码)；基于所述接入装置对应的区域确定所述终端设备当前所处的位置。
其中，所述接入装置可以为基站、或者，还可以为接入点(AP)等，用于为终端设备提供直接接入方式的装置。
具体来讲，上述方案中能够具备两种触发情况，其中第一种触发情况就是基于终端设备所处位置的变化，来判断终端设备是否处于能够进行本地业务分流的接入网中，从而来确定是否对终端设备的路径类型进行调整；另外第二种触发情况就是结合终端设备是否有本地业务分流的需求，来判断终端设备是否进行路径类型的调整。
本实施例主要针对上述第一种触发情况，终端在会话连接时，默认只建立面向一个核心侧网关的会话连接；当UE移动到可支持本地分流网关的范围内时，由控制面发起建立新的隧道，从而将该EGW加入到已有会话中，也就是由第一类路径切换至第二类路径；当终端移动出EGW的覆盖范围时，控制面可以触发新的隧道建立机制，将EGW从会话路径中删除，建立第二类路径删除第一类路径。
场景一、所述连接管理装置还包括：路径管理单元1203，用于确定所述终端设备通过第一接入装置与所述第一转发面建立第一类路径；其中，所述第一接入装置与所述终端设备在当前所处的位置所要接入的目标接入装置不同；所述第一接入装置所对应的覆盖范围内不具备第二转发面或不适合接入到第二转发面；
相应的，所述路径调整单元1202，用于当所述终端设备当前所处的位 置处能够接入第二转发面或能够接入所述终端设备适合的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第一类路径调整为第二类路径。也就是说，核心网侧能够根据终端设备当前所处的位置(比如区域码)来确定该位置处，是否具备可优化本地业务访问路径第二转发面。
需要理解的是，本场景下，当终端设备初次接入网络时，连接管理装置可以基于终端设备所在接入网是否具备第二转发面，来确定终端设备初次建立的路径类型，当接入网不具备或不适合接入第二转发面时，那么终端设备初次接入到网络时，就建立第一类路径，如图4a所示直接与第一转发面建立连接；当接入网具备第二转发面(比如，图中边缘网关EGW)，终端设备初次接入网络时，建立如图4b所示的第二类路径，经由第二转发面(比如，图中边缘网关EGW)与第一转发面(比如图中的核心网关(CGW))建立连接。
终端设备，比如，UE，移动到新的位置后，控制面(也就是连接管理装置)获取接入网当前的位置，判断当前是否有第二转发面存在，如果存在第二转发面，则控制面通过当前接入网的标识(如接入基站的ID或者位置区域的信息如TA)获取第二转发面的信息(如其IP地址)，建立相应的隧道。
当确定所述终端设备与所述第一转发面之间的路径由第一类路径调整为第二类路径后，为所述终端设备选取对应的第二转发面，将第二转发面的下行标识信息发送给第一转发面、并将所述第二转发面的上行标识信息发至接入网侧，以建立所述终端设备经由所述第二转发面连接所述第一转发面之间的第二类路径。
也就是说，确定将第一类路径调整为第二类路径后，还需要通知终端设备进行路径类型的调整以及通知通道设备所要接入的第二转发面。
具体来说，如果终端设备在连接状态下发生移动，则可以在切换消息中，将第二转发面(比如，边缘网关EGW)作为基站和第一转发面(比如 核心网关(CGW))隧道的对端，可以包括：
把EGW下行隧道的IP地址和隧道ID告诉CGW作为CGW的下行隧道端点；把EGW上行隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点。
如果终端设备在空闲(IDLE)模式下由非MEC区域移动到MEC区域，当UE主动发起业务或者有下行数据到来网络寻呼后，触发UE发起会话建立时，网络根据当前的位置，判断是否进行连接的更新。如果需要进行连接的更新，则控制面不是新建CGW和接入网(AN，Access Network)间的隧道，而是建立成为一个AN、EGW、CGW间的隧道。
场景二、与场景一不同之处在于，场景一针对第一类路径调整为第二类路径进行的介绍，本场景则针对将第二类路径调整为第一类路径进行说明。
路径管理单元，用于所述终端设备通过第二接入装置与所述第一转发面建立第二类路径；其中，所述第二接入装置与所述终端设备在当前所处的位置所要接入的目标接入装置不同；所述第二接入装置所处的位置处具备第二转发面或具备适合终端设备接入的第二转发面；
相应的，所述路径调整单元，用于当所述终端设备当前所处的位置处不具备第二转发面或不具备适合所述终端设备接入的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
所述路径调整单元，用于当确定所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径后，将接入网相应的标识信息通知第一转发面、将所述第一转发面的标识信息通知给所述接入网，以建立所述终端设备与所述第一转发面之间的第一类路径。
终端设备移动到新的位置后，通过接入网当前的位置，控制面判断当前会话第二转发面(比如，边缘网关EGW)不再需要时，则其连接的更新 中不再包含中间的EGW的信息，用户面的数据通道变成AN与CGW直连。
具体说来，连接状态，在发生从MEC区域到MEC外的区域的切换消息中，直接将接入网和CGW互相作为对方的隧道对端：把接入网相应的隧道ID和IP告诉CGW作为CGW的下行隧道端点；把CGW隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点。
UE如果是空闲状态移动到MEC外的区域时，则网络将通过位置更新，进一步释放掉EGW和CGW之间的用户面隧道，在下一次终端由空闲变成Active时，新的隧道是AN和CGW直接的一跳的隧道。
可见，通过采用上述方案，就能够至少基于终端设备所处位置对应的接入网，确定是否对终端设备与第一转发面之间的路径类型进行调整，具体来说，路径类型可以包括有直接连接到第一转发面的第一类路径，以及通过第二转发面跳接到第一转发面的第二类路径。如此，就能够提供网络架构的灵活性以及高效性，无本地分流时以最少跳数实现一个网关处理，以及仅在网络侧进行路径类型的配置即可，不需要终端设备侧进行较多的配置改变就能够实现边缘网络数据的访问。
实施例四、
本实施例主要针对第二种触发情况进行说明，所述路径调整单元，用于基于所述终端设备所处位置对应的接入网、以及所述终端设备的业务类型，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整。
具体来说，所述基于所述终端设备所处位置对应的接入网、以及所述终端设备的业务类型，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整之前，路径管理单元，用于确定所述终端设备在所处的位置通过第一类路径与所述核心网之间建立连接；
相应的，所述路径调整单元，用于当所述终端设备所处的位置对应的接入网中具备可优化本地业务访问路径第二转发面、且检测到所述终端设 备对应的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型、所述第一业务类型为不需要进行本地业务分流的业务类型。
所述路径调整单元，用于所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径后，检测截止到当前时刻所述终端设备最后一次完成第二业务类型的信息交互后、停止第二业务类型的信息交互的时长；当所述时长超过预设时长门限值时，确定将所述终端设备与第一转发面之间的连接路径由所述第二类路径调整为第一类路径。
也就是说，所述路径调整单元，用于获知当UE发起边缘或本地业务时，触发接入网和核心网网关连接的更新，动态的加入第二转发面(比如，边缘网关EGW)的功能，建立UE与EGW的连接，形成方案如图4b所示的网络架构。
所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径后，检测截止到当前时刻所述终端设备最后一次完成第二业务类型的信息交互后、停止第二业务类型的信息交互的时长；
当所述时长超过预设时长门限值时，确定将所述终端设备与第一转发面之间的连接路径由所述第二类路径调整为第一类路径。
连接管理装置(网络侧控制面)感知到一个有第二转发面的UE在一段时间内不访问边缘网络的业务时，在路径中删除边缘网络网关，也就是从第二类路径切换至第一类路径。
连接管理装置获知终端设备访问边缘或本地业务的方式包括以下至少之一：
方式一、通过所述终端设备上报的业务类型信息，确定所述终端设备是否有第一业务类型切换为第二业务类型。就是UE告知网络：UE向控制 面发送的信令中包含业务类型信息，网络侧通过业务类型信息判断该UE的业务适合访问边缘或本地网络，则建立EGW连接。
方式二、连接管理装置从网络侧感知终端的业务访问路径需要优化。具体的，连接管理装置感知UE的业务适合访问边缘或本地网络，比如，用户面根据用户访问的业务目标地址等，通过用户面告知控制面该用户的IP地址。
方式三、接收所述终端设备使用的业务对应的服务器侧发来的通知信息来确定终端设备的业务类型；比如，直接或通过能力开放接口告知网络某用户需要建立到边缘网络的链路。
连接管理装置感知仅有到核心层连接的终端设备需要建立到边缘(或本地)网络的数据通道或数据包需要在边缘分流时，核心网控制面触发将第二转发面(或用户面的网络功能)加入到已有数据通道中并更新隧道。使得需要在边缘网络路由的数据通过第二转发面转发和分流，其它的数据流则经过第二转发面到达核心层网关，进而到达核心PDN网络。终端在这个过程中不感知网络的变化。当网络感知具有第二转发面的连接不再需要边缘网络数据通道时，网络触发连接路径的更新，删除传输路径中的第二转发面EGW。使得所有的数据能够通过一跳进入PDN网络。
UE发生数据业务，网络判断需引入第二转发面(比如，边缘网关EGW)优化数据通道，触发第二转发面的加入控制面向接入网发起会话更新流程，把EGW上行隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点；把EGW下行隧道的IP地址和隧道ID告诉第一转发面(比如图中的核心网关(CGW))作为CGW的下行隧道端点。
判断该终端设备在一段时间内没有访问本地缓存的业务，则触发删除EGW的步骤，具体可以包括：
所述路径管理单元，用于向接入网发起会话更新流程，把CGW的上行隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点；把接 入网的下行隧道的IP地址和隧道ID告诉CGW作为CGW的下行隧道端点。
可见，通过采用上述方案，就能够至少基于终端设备所处位置对应的接入网，确定是否对终端设备与第一转发面之间的路径类型进行调整，具体来说，路径类型可以包括有直接连接到第一转发面的第一类路径，以及通过第二转发面跳接到第一转发面的第二类路径。如此，就能够提供网络架构的灵活性以及高效性，无本地分流时以最少跳数实现一个网关处理，以及不需要终端设备侧进行较多的配置改变就能够实现边缘网络数据的访问。
实施例五、
本实施例提供了一种连接管理装置，如图13所示，所述连接管理装置包括：
通信接口1301，检测终端设备的相关信息；
处理器1302，基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面与第一转发面之间建立的连接路径。
具体的，所述终端设备的相关信息，包括：终端设备的位置、和/或、所述终端设备当前的业务类型。
这里，所述连接管理装置主要设置在核心网中，具体的实现可以为一个模块设置在核心网中的某一个设备中，比如，可以设置在核心网中的MME中。
上述获取到终端设备当前所述的位置的方式可以包括：检测所述终端设备当前所接入的接入装置，获取到该接入装置的标识信息(比如接入装 置的ID号)；基于所述接入装置的标识信息确定所述接入装置对应的区域(比如，核心网侧能够通过接入装置的标识信息确定所述接入装置对应的区域码)；基于所述接入装置对应的区域确定所述终端设备当前所处的位置。
其中，所述接入装置可以为基站、或者，还可以为接入点(AP)等，用于为终端设备提供直接接入方式的装置。
具体来讲，上述方案中能够具备两种触发情况，其中第一种触发情况就是基于终端设备所处位置的变化，来判断终端设备是否处于能够进行本地业务分流的接入网中，从而来确定是否对终端设备的路径类型进行调整；另外第二种触发情况就是结合终端设备是否有本地业务分流的需求，来判断终端设备是否进行路径类型的调整。
第一种触发情况：终端在会话连接时，默认只建立面向一个核心侧网关的会话连接；当UE移动到可支持本地分流网关的范围内时，由控制面发起建立新的隧道，从而将该EGW加入到已有会话中，也就是由第一类路径切换至第二类路径；当终端移动出EGW的覆盖范围时，控制面可以触发新的隧道建立机制，将EGW从会话路径中删除，建立第二类路径删除第一类路径。
场景一、所述处理器1302，确定所述终端设备通过第一接入装置与所述第一转发面建立第一类路径；其中，所述第一接入装置与所述终端设备在当前所处的位置所要接入的目标接入装置不同；所述第一接入装置所对应的覆盖范围内不具备第二转发面或不适合接入到第二转发面；
当所述终端设备当前所处的位置处能够接入第二转发面或能够接入所述终端设备适合的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第一类路径调整为第二类路径。也就是说，核心网侧能够根据终端设备当前所处的位置(比如区域码)来确定该位置处，是否具备可优化本地业务访问路径第二转发面。
需要理解的是，本场景下，当终端设备初次接入网络时，连接管理装 置可以基于终端设备所在接入网是否具备第二转发面，来确定终端设备初次建立的路径类型，当接入网不具备或不适合接入第二转发面时，那么终端设备初次接入到网络时，就建立第一类路径，如图4a所示直接与第一转发面建立连接；当接入网具备第二转发面是，终端设备初次接入网络时，建立如图4b所示的第二类路径，经由第二转发面与第一转发面建立连接。
终端设备，比如，UE，移动到新的位置后，控制面(也就是连接管理装置)获取接入网当前的位置，判断当前是否有第二转发面存在，如果存在第二转发面，则控制面通过当前接入网的标识(如接入基站的ID或者位置区域的信息如TA)获取第二转发面(EGW)的信息(如其IP地址)，建立相应的隧道。
当确定所述终端设备与所述第一转发面之间的路径由第一类路径调整为第二类路径后，为所述终端设备选取对应的第二转发面，将第二转发面的下行标识信息发送给第一转发面、并将所述第二转发面的上行标识信息发至接入网侧，以建立所述终端设备经由所述第二转发面连接所述第一转发面之间的第二类路径。
也就是说，确定将第一类路径调整为第二类路径后，还需要通知终端设备进行路径类型的调整以及通知通道设备所要接入的第二转发面。
具体来说，如果终端设备在连接状态下发生移动，则可以在切换消息中，将第二转发面(比如，EGW)作为基站和第一转发面(比如，CGW)隧道的对端，可以包括：
把EGW下行隧道的IP地址和隧道ID告诉CGW作为CGW的下行隧道端点；把EGW上行隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点。
如果终端设备在空闲(IDLE)模式下由非MEC区域移动到MEC区域，当UE主动发起业务或者有下行数据到来网络寻呼后，触发UE发起会话建立时，网络根据当前的位置，判断是否进行连接的更新。如果需要进行连 接的更新，则控制面不是新建CGW和接入网(AN，Access Network)间的隧道，而是建立成为一个AN、EGW、CGW间的隧道。
场景二、与场景一不同之处在于，场景一针对第一类路径调整为第二类路径进行的介绍，本场景则针对将第二类路径调整为第一类路径进行说明。
所述处理器1302，所述终端设备通过第二接入装置与所述第一转发面建立第二类路径；其中，所述第二接入装置与所述终端设备在当前所处的位置所要接入的目标接入装置不同；所述第二接入装置所处的位置处具备第二转发面或具备适合终端设备接入的第二转发面；
所述终端设备当前所处的位置处不具备第二转发面或不具备适合所述终端设备接入的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
所述处理器1302，当确定所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径后，将接入网相应的标识信息通知第一转发面、将所述第一转发面的标识信息通知给所述接入网，以建立所述终端设备与所述第一转发面之间的第一类路径。
终端设备移动到新的位置后，通过接入网当前的位置，控制面判断当前会话第二转发面不再需要时，则其连接的更新中不再包含中间的EGW的信息，用户面的数据通道变成AN与CGW直连。
具体说来，连接状态，在发生从MEC区域到MEC外的区域的切换消息中，直接将接入网和CGW互相作为对方的隧道对端：把接入网相应的隧道ID和IP告诉CGW作为CGW的下行隧道端点；把CGW隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点。
UE如果是空闲状态移动到MEC外的区域时，则网络将通过位置更新，进一步释放掉EGW和CGW之间的用户面隧道，在下一次终端由空闲变成Active时，新的隧道是AN和CGW直接的一跳的隧道。
第二种触发情况：
所述处理器1302，基于所述终端设备所处位置对应的接入网、以及所述终端设备的业务类型，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整。
具体来说，所述基于所述终端设备所处位置对应的接入网、以及所述终端设备的业务类型，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整之前，路径管理单元，用于确定所述终端设备在所处的位置通过第一类路径与所述核心网之间建立连接；
当所述终端设备所处的位置对应的接入网中具备可优化本地业务访问路径第二转发面、且检测到所述终端设备对应的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型、所述第一业务类型为不需要进行本地业务分流的业务类型。
所述处理器1302，所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径后，检测截止到当前时刻所述终端设备最后一次完成第二业务类型的信息交互后、停止第二业务类型的信息交互的时长；当所述时长超过预设时长门限值时，确定将所述终端设备与第一转发面之间的连接路径由所述第二类路径调整为第一类路径。
也就是说，所述处理器1302，获知当UE发起边缘或本地业务时，触发接入网和核心网网关连接的更新，动态的加入第二转发面的功能，建立UE与EGW的连接，形成方案如图4b所示的网络架构。
所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径后，检测截止到当前时刻所述终端设备最后一次完成第二业务类型的信息交互后、停止第二业务类型的信息交互的时长；
当所述时长超过预设时长门限值时，确定将所述终端设备与第一转发面之间的连接路径由所述第二类路径调整为第一类路径。
连接管理装置(网络侧控制面)感知到一个有第二转发面的UE在一段时间内不访问边缘网络的业务时，在路径中删除边缘网络网关，也就是从第二类路径切换至第一类路径。
连接管理装置获知终端设备访问边缘或本地业务的方式包括以下至少之一：
方式一、通过所述终端设备上报的业务类型信息，确定所述终端设备是否有第一业务类型切换为第二业务类型。就是UE告知网络：UE向控制面发送的信令中包含业务类型信息，网络侧通过业务类型信息判断该UE的业务适合访问边缘或本地网络，则建立EGW连接。
方式二、所述处理器1302，从网络侧感知终端的业务访问路径需要优化。具体的，连接管理装置感知UE的业务适合访问边缘或本地网络，比如，用户面根据用户访问的业务目标地址等，通过用户面告知控制面该用户的IP地址。
方式三、接收所述终端设备使用的业务对应的服务器侧发来的通知信息来确定终端设备的业务类型；比如，直接或通过能力开放接口告知网络某用户需要建立到边缘网络的链路。
连接管理装置感知仅有到核心层连接的终端设备需要建立到边缘(或本地)网络的数据通道或数据包需要在边缘分流时，核心网控制面触发将第二转发面(或用户面的网络功能)加入到已有数据通道中并更新隧道。使得需要在边缘网络路由的数据通过第二转发面转发和分流，其它的数据流则经过第二转发面到达核心层网关，进而到达核心PDN网络。终端在这个过程中不感知网络的变化。当网络感知具有第二转发面的连接不再需要边缘网络数据通道时，网络触发连接路径的更新，删除传输路径中的第二转发面EGW。使得所有的数据能够通过一跳进入PDN网络。
UE发生数据业务，网络判断需引入第二转发面优化数据通道，触发第二转发面的加入控制面向接入网发起会话更新流程，把EGW上行隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点；把EGW下行隧道的IP地址和隧道ID告诉CGW作为CGW的下行隧道端点。
判断该终端设备在一段时间内没有访问本地缓存的业务，则触发删除EGW的步骤，具体可以包括：
所述路径管理单元，用于向接入网发起会话更新流程，把CGW的上行隧道的IP地址和隧道ID告诉接入网，作为接入网的上行隧道端点；把接入网的下行隧道的IP地址和隧道ID告诉CGW作为CGW的下行隧道端点。
可见，通过采用上述方案，就能够至少基于终端设备所处位置对应的接入网，确定是否对终端设备与第一转发面之间的路径类型进行调整，具体来说，路径类型可以包括有直接连接到第一转发面的第一类路径，以及通过第二转发面跳接到第一转发面的第二类路径。如此，就能够提供网络架构的灵活性以及高效性，无本地分流时以最少跳数实现一个网关处理，以及不需要终端设备侧进行较多的配置改变就能够实现边缘网络数据的访问
本发明实施例中一种连接管理装置，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
其中，所述处理器用于运行所述计算机程序时，执行前述实施例一或二的方法步骤，这里不再进行赘述。
本发明实施例提供的一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实施前述实施例一或二的方法步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变 体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本发明各个实施例所述的方法。
以上仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。

Claims (29)

  1. 一种连接管理方法，所述方法包括：
    检测终端设备的相关信息；
    基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
    其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面第二转发面与第一转发面之间建立的连接路径。
  2. 根据权利要求1所述的方法，其中，所述终端设备的相关信息，包括：终端设备的位置、和/或、所述终端设备当前的业务类型。
  3. 根据权利要求1所述的方法，其中，所述检测终端设备的相关信息之前，所述方法还包括：
    所述终端设备通过第一接入装置与所述第一转发面建立第一类路径；所述第一接入装置所对应的覆盖范围内不具备第二转发面或不适合接入到第二转发面；
    所述基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整，包括：
    当所述终端设备的位置处能够接入第二转发面或能够接入所述终端设备适合的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第一类路径调整为第二类路径。
  4. 根据权利要求1所述的方法，其中，所述检测终端设备的相关信息之前，所述方法还包括：
    所述终端设备通过第二接入装置、经由第二转发面与所述第一转发面建立第二类路径；所述第二接入装置所处的位置处具备第二转发面或具备 适合终端设备接入的第二转发面；
    所述基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整，包括：
    当所述终端设备的位置处不具备第二转发面或不具备适合所述终端设备接入的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
  5. 根据权利要求1所述的方法，其中，所述检测终端设备的相关信息之前，所述方法还包括：
    所述终端设备通过第二接入装置、经由第二转发面与所述第一转发面建立第二类路径；
    所述基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整，包括：
    当所述终端设备的位置处不能够接入所述第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
  6. 根据权利要求1所述的方法，其中，所述基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整，包括：
    当所述终端设备当前的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
    其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型，所述第一业务类型为不需要进行本地业务分流的业务类型。
  7. 根据权利要求1所述的方法，其中，所述基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整之前，所述方法还包括：
    所述终端设备在所处的位置通过第一类路径与所述第一转发面之间建立连接；
    所述基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整，包括：
    当所述终端设备当前所处的位置具备第二转发面或具备适合终端设备接入的第二转发面、且检测到所述终端设备当前对应的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
    其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型、所述第一业务类型为不需要进行本地业务分流的业务类型。
  8. 根据权利要求3、5、6或7所述的方法，其中，所述方法还包括：
    所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径后，检测截止到当前时刻所述终端设备最后一次完成第二业务类型的信息交互后、停止第二业务类型的信息交互的时长；
    当所述时长超过预设时长门限值时，确定将所述终端设备与第一转发面之间的连接路径由所述第二类路径调整为第一类路径。
  9. 根据权利要求2-7任一项所述的方法，其中，所述方法还包括：
    若确定所述终端设备与所述第一转发面之间的路径需要由第一类路径调整为第二类路径时，则为所述终端设备选取对应的第二转发面，将第二转发面的标识信息发送给第一转发面作为第一转发面下行隧道的信息、并将所述第二转发面的标识信息发至接入网侧作为接入侧上行隧道的信息，以建立所述终端设备经由所述第二转发面连接所述第一转发面之间的第二类路径；
    若确定所述终端设备与所述第一转发面之间的路径需要由第二类路径调整为第一类路径时，则将接入网相应的标识信息通知第一转发面、将所 述第一转发面的标识信息通知给所述接入网，以建立所述终端设备与所述第一转发面之间的第一类路径。
  10. 一种连接管理装置，所述连接管理装置包括：
    信息获取单元，检测终端设备的相关信息；
    路径调整单元，基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
    其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面与第一转发面之间建立的连接路径。
  11. 根据权利要求10所述的连接管理装置，其中，所述终端设备的相关信息，包括：终端设备的位置、和/或、所述终端设备当前的业务类型。
  12. 根据权利要求10所述的连接管理装置，其中，所述连接管理装置还包括：
    路径管理单元，确定所述终端设备通过第一接入装置与所述第一转发面建立第一类路径；所述第一接入装置所对应的覆盖范围内不具备第二转发面或不适合接入到第二转发面；
    所述路径调整单元，当所述终端设备当前所处的位置处能够接入第二转发面或能够接入所述终端设备适合的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第一类路径调整为第二类路径。
  13. 根据权利要求10所述的连接管理装置，其中，所述连接管理装置还包括：
    路径管理单元，确定所述终端设备通过第二接入装置与所述第一转发面建立第二类路径；所述第二接入装置所处的位置处具备第二转发面或具备适合终端设备接入的第二转发面；
    所述路径调整单元，当所述终端设备当前所处的位置处不具备第二转 发面或不具备适合所述终端设备接入的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
  14. 根据权利要求10所述的连接管理装置，其中，所述连接管理装置还包括：
    路径管理单元，确定所述终端设备通过第二接入装置、经由第二转发面与所述第一转发面建立第二类路径；
    所述路径调整单元，当所述终端设备当前所处的位置处不能够接入所述第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
  15. 根据权利要求10所述的连接管理装置，其中，
    路径调整单元，当所述终端设备对应的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
    其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型，所述第一业务类型为不需要进行本地业务分流的业务类型。
  16. 根据权利要求10所述的连接管理装置，其中，所述连接管理装置还包括：
    路径管理单元，确定所述终端设备在所处的位置通过第一类路径与所述第一转发面之间建立连接；
    所述路径调整单元，当所述终端设备当前所处的位置具备第二转发面或具备适合终端设备接入的第二转发面、且检测到所述终端设备当前对应的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
    其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型、所述第一业务类型为不需要进行 本地业务分流的业务类型。
  17. 根据权利要求12、14、15或16所述的连接管理装置，其中，所述路径调整单元，所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径后，检测截止到当前时刻所述终端设备最后一次完成第二业务类型的信息交互后、停止第二业务类型的信息交互的时长；当所述时长超过预设时长门限值时，确定将所述终端设备与第一转发面之间的连接路径由所述第二类路径调整为第一类路径。
  18. 根据权利要求12-16任一项所述的连接管理装置，其中，所述路径管理单元，若确定所述终端设备与所述第一转发面之间的路径需要由第一类路径调整为第二类路径时，则为所述终端设备选取对应的第二转发面，将第二转发面的标识信息发送给第一转发面作为第一转发面下行隧道的信息、并将所述第二转发面的标识信息发至接入网侧作为接入侧上行隧道的信息，以建立所述终端设备经由所述第二转发面连接所述第一转发面之间的第二类路径；
    若确定所述终端设备与所述第一转发面之间的路径需要由第二类路径调整为第一类路径时，则将接入网相应的标识信息通知第一转发面、将所述第一转发面的标识信息通知给所述接入网，以建立所述终端设备与所述第一转发面之间的第一类路径。
  19. 一种连接管理装置，所述连接管理装置包括：
    通信接口，检测终端设备的相关信息；
    处理器，基于所述终端设备的相关信息，确定是否对所述终端设备与第一转发面之间连接路径的类型进行调整；
    其中，所述终端设备与第一转发面之间连接路径的类型至少包括有：第一类路径为所述终端设备通过接入网与第一转发面之间直接建立的连接路径；第二类路径为所述终端设备通过所述接入网经由第二转发面与第一转发面之间建立的连接路径。
  20. 根据权利要求19所述的连接管理装置，其中，所述终端设备的相关信息，包括：终端设备的位置、和/或、所述终端设备当前的业务类型。
  21. 根据权利要求19所述的连接管理装置，其中，所述处理器，确定所述终端设备通过第一接入装置与所述第一转发面建立第一类路径；所述第一接入装置所对应的覆盖范围内不具备第二转发面或不适合接入到第二转发面；
    当所述终端设备当前所处的位置处能够接入第二转发面或能够接入所述终端设备适合的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第一类路径调整为第二类路径。
  22. 根据权利要求19所述的连接管理装置，其中，所述处理器，确定所述终端设备通过第二接入装置与所述第一转发面建立第二类路径；所述第二接入装置所处的位置处具备第二转发面或具备适合终端设备接入的第二转发面；
    当所述终端设备当前所处的位置处不具备第二转发面或不具备适合所述终端设备接入的第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
  23. 根据权利要求19所述的连接管理装置，其中，所述处理器，确定所述终端设备通过第二接入装置、经由第二转发面与所述第一转发面建立第二类路径；
    当所述终端设备当前所处的位置处不能够接入所述第二转发面时，确定将所述终端设备与所述第一转发面之间的路径由第二类路径调整为第一类路径。
  24. 根据权利要求19所述的连接管理装置，其中，
    处理器，当所述终端设备对应的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
    其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型，所述第一业务类型为不需要进行本地业务分流的业务类型。
  25. 根据权利要求19所述的连接管理装置，其中，所述处理器，确定所述终端设备在所处的位置通过第一类路径与所述第一转发面之间建立连接；
    当所述终端设备当前所处的位置具备第二转发面或具备适合终端设备接入的第二转发面、且检测到所述终端设备当前对应的业务类型由第一业务类型切换为第二业务类型时，确定将所述终端设备与第一转发面之间的连接路径由第一类路径调整为第二类路径；
    其中，所述第一业务类型与所述第二业务类型不同，所述第二业务类型为需要进行本地业务分流的业务类型、所述第一业务类型为不需要进行本地业务分流的业务类型。
  26. 根据权利要求21、23、24或25所述的连接管理装置，其中，所述处理器，与第一转发面之间的连接路径由第一类路径调整为第二类路径后，检测截止到当前时刻所述终端设备最后一次完成第二业务类型的信息交互后、停止第二业务类型的信息交互的时长；当所述时长超过预设时长门限值时，确定将所述终端设备与第一转发面之间的连接路径由所述第二类路径调整为第一类路径。
  27. 根据权利要求21-25任一项所述的连接管理装置，其中，所述处理器，若确定所述终端设备与所述第一转发面之间的路径需要由第一类路径调整为第二类路径时，则为所述终端设备选取对应的第二转发面，将第二转发面的标识信息发送给第一转发面作为第一转发面下行隧道的信息、并将所述第二转发面的标识信息发至接入网侧作为接入侧上行隧道的信息，以建立所述终端设备经由所述第二转发面连接所述第一转发面之间的第二类路径；
    若确定所述终端设备与所述第一转发面之间的路径需要由第二类路径调整为第一类路径时，则将接入网相应的标识信息通知第一转发面、将所述第一转发面的标识信息通知给所述接入网，以建立所述终端设备与所述第一转发面之间的第一类路径。
  28. 一种连接管理装置，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，所述处理器用于运行所述计算机程序时，执行权利要求1-9任一项所述方法的步骤。
  29. 一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实现权利要求1-9任一项所述的方法步骤。
PCT/CN2017/105778 2016-10-11 2017-10-11 一种连接管理方法及装置、计算机存储介质 Ceased WO2018068738A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US16/340,107 US10785693B2 (en) 2016-10-11 2017-10-11 Connection management method and apparatus, and computer storage medium
EP17859735.7A EP3525548B1 (en) 2016-10-11 2017-10-11 Connection management method and apparatus, and computer storage medium
JP2019514218A JP2019530334A (ja) 2016-10-11 2017-10-11 接続管理方法及び装置、コンピュータ記憶媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610889291.3 2016-10-11
CN201610889291.3A CN108377459B (zh) 2016-10-11 2016-10-11 一种连接管理方法及装置

Publications (1)

Publication Number Publication Date
WO2018068738A1 true WO2018068738A1 (zh) 2018-04-19

Family

ID=61905541

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/105778 Ceased WO2018068738A1 (zh) 2016-10-11 2017-10-11 一种连接管理方法及装置、计算机存储介质

Country Status (5)

Country Link
US (1) US10785693B2 (zh)
EP (1) EP3525548B1 (zh)
JP (1) JP2019530334A (zh)
CN (1) CN108377459B (zh)
WO (1) WO2018068738A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210314264A1 (en) * 2019-01-08 2021-10-07 Mavenir Networks, Inc. Method and apparatus for user plane resource selection for 5g core

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI674780B (zh) * 2018-11-23 2019-10-11 財團法人工業技術研究院 網路服務系統及網路服務方法
CN112398891B (zh) 2019-08-16 2023-04-18 华为技术有限公司 一种通信方法和装置
US11665614B2 (en) * 2019-08-20 2023-05-30 Verizon Patent And Licensing Inc. Multi-access edge computing assisted device state transitions
CN111343657B (zh) * 2020-03-09 2023-02-24 中国联合网络通信集团有限公司 移动性管理方法、装置、终端设备及存储介质
CN111757305B (zh) * 2020-06-16 2023-12-19 西安闻泰电子科技有限公司 业务执行终端的切换方法、装置、系统及存储介质
CN111970635B (zh) * 2020-08-26 2023-07-07 展讯通信（上海）有限公司 定位数据传输方法和装置
CN114630342B (zh) * 2020-12-10 2023-08-08 中盈优创资讯科技有限公司 一种通过upf探测mec状态的方法及装置
WO2023287696A2 (en) * 2021-07-12 2023-01-19 Intel Corporation Sixth generation (6g) system architecture and functions
CN114173358B (zh) * 2021-12-09 2024-07-23 南京邮电大学 5g局域网公网系统及其设计方法
CN114172868B (zh) * 2022-02-14 2022-05-13 武汉慧联无限科技有限公司 一种数据传输方法、装置及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150838A (zh) * 2006-09-18 2008-03-26 大唐移动通信设备有限公司 一种在系统间切换的方法及系统
CN101167392A (zh) * 2005-04-29 2008-04-23 艾利森电话股份有限公司 蜂窝无线电网络与无线数据网络的网络互连
CN101772106A (zh) * 2008-12-30 2010-07-07 华为技术有限公司 数据传输路径的控制方法和系统、移动性管理网元和终端
US20100177686A1 (en) * 2007-03-12 2010-07-15 Nec Europe Ltd Method for performing route optimization between two nodes in network based mobility management

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100388809C (zh) * 2004-12-27 2008-05-14 华为技术有限公司 一种在ip承载网中转发业务流的方法
WO2011038359A2 (en) * 2009-09-26 2011-03-31 Cisco Technology, Inc. Providing services at a communication network edge
US9503970B2 (en) 2009-12-04 2016-11-22 Qualcomm Incorporated Managing a data network connection for mobile communications based on user location
CN102238634B (zh) * 2010-05-05 2015-05-27 中国移动通信集团公司 在无线网络中进行数据分流的方法及其装置
CN102469619B (zh) * 2010-11-12 2016-12-28 中兴通讯股份有限公司 一种移动通信系统及其服务网关重定位的方法
CN102480782B (zh) * 2010-11-25 2016-03-30 中兴通讯股份有限公司 网关重定位方法和源分流网关
CN103139847A (zh) * 2011-12-02 2013-06-05 中国移动通信集团公司 一种数据传输方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101167392A (zh) * 2005-04-29 2008-04-23 艾利森电话股份有限公司 蜂窝无线电网络与无线数据网络的网络互连
CN101150838A (zh) * 2006-09-18 2008-03-26 大唐移动通信设备有限公司 一种在系统间切换的方法及系统
US20100177686A1 (en) * 2007-03-12 2010-07-15 Nec Europe Ltd Method for performing route optimization between two nodes in network based mobility management
CN101772106A (zh) * 2008-12-30 2010-07-07 华为技术有限公司 数据传输路径的控制方法和系统、移动性管理网元和终端

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210314264A1 (en) * 2019-01-08 2021-10-07 Mavenir Networks, Inc. Method and apparatus for user plane resource selection for 5g core
US11805059B2 (en) * 2019-01-08 2023-10-31 Mavenir Networks, Inc. Method and apparatus for user plane resource selection for 5G core
US12177127B2 (en) 2019-01-08 2024-12-24 Mavenir Networks, Inc. Method and apparatus for user plane resource selection for 5G core

Also Published As

Publication number Publication date
CN108377459B (zh) 2020-09-01
CN108377459A (zh) 2018-08-07
US20200053614A1 (en) 2020-02-13
US10785693B2 (en) 2020-09-22
JP2019530334A (ja) 2019-10-17
EP3525548A1 (en) 2019-08-14
EP3525548A4 (en) 2019-08-14
EP3525548B1 (en) 2021-12-08

Similar Documents

Publication Publication Date Title
CN108377459B (zh) 一种连接管理方法及装置
EP3755116B1 (en) Method of processing establishment of ma pdu session, and amf node and smf node
US12302222B2 (en) Network service control method and communications device
JP5820066B2 (ja) Ａｐｎ特定情報又は非ａｐｎ特定情報に基づいて実行されるローカルネットワークを介したトラヒックオフロード
US10779357B2 (en) Method for avoiding handover failure
US11129054B2 (en) Methods, systems and devices for supporting local breakout in small cell architecture
WO2018145669A1 (zh) 一种业务分流实现方法及装置
US11240711B2 (en) Policy control method and system, network element, and storage medium
WO2019024677A1 (zh) 网络切换的方法、装置及系统
WO2009006774A1 (fr) Procédé de transfert intérieur dans un système
WO2009097772A1 (zh) 一种资源释放控制方法及通讯系统以及相关设备
WO2008113235A1 (en) A method for avoiding resourece being released mistakenly during tracking area update or handover process
WO2010031353A1 (zh) 服务请求的处理方法、装置及系统
US10334640B2 (en) Systems, methods, and devices for facilitating wireless communication
WO2017162121A1 (zh) 用户面服务网关选择方法及系统
WO2016180018A1 (zh) 一种接入方法及相应的接入节点、终端和通信网络
EP3506677B1 (en) Method and device for establishing bearer
WO2012130018A1 (zh) 一种ip分流连接移动性支持的方法及系统
WO2019033281A1 (en) METHODS AND COMPUTER DEVICE FOR MODIFYING USER PLAN FUNCTION
WO2016054822A1 (zh) Csfb呼叫建立方法及装置
WO2012103773A1 (zh) 中继系统的过载控制方法及系统
CN102457958B (zh) 一种服务网关重定位的判定方法及系统
WO2016173283A1 (zh) 一种接入业务网络的方法及装置、基站
CN104869575A (zh) 最优路径的建立方法、mme及网关
WO2018001301A1 (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: 17859735

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019514218

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017859735

Country of ref document: EP

Effective date: 20190508