WO2018035864A1 - 一种网络管理方法和控制器 - Google Patents
一种网络管理方法和控制器 Download PDFInfo
- Publication number
- WO2018035864A1 WO2018035864A1 PCT/CN2016/096998 CN2016096998W WO2018035864A1 WO 2018035864 A1 WO2018035864 A1 WO 2018035864A1 CN 2016096998 W CN2016096998 W CN 2016096998W WO 2018035864 A1 WO2018035864 A1 WO 2018035864A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pdn
- user plane
- plane gateway
- tunnel
- mapping relationship
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
- H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
-
- 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/12—Reselecting a serving backbone network switching or routing node
- H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
-
- 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/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
- H04W36/305—Handover due to radio link failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
- H04W40/28—Connectivity information management, e.g. connectivity discovery or connectivity update for reactive routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/34—Modification of an existing route
- H04W40/36—Modification of an existing route due to handover
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a network management method and controller.
- the user equipment (User Equipment, referred to as UE) Accessing the Packet Data Network (PDN) through the core network and the border gateway.
- the PDN is in the Internet (internet, referred to as internet)
- the core network is responsible for sending data to the border gateway, and the border gateway sends the data to the PDN in the internet.
- the present application provides a network management method and a controller, so that data between UEs in the same local network does not have to go through the core network and the internet, thereby effectively reducing network transmission delay and reducing mobile network pressure.
- a first aspect of the present application provides a network management method, where the method includes:
- the controller When the controller receives the notification of the control plane gateway to determine that the first UE is detached from the first base station, the controller determines, according to the pre-stored IN-PDN distribution information, that the first UE is connected before being detached from the first base station.
- the first IN-PDN and the first user plane gateway; the IN-PDN distribution information is used to indicate a mapping relationship between the IN-PDN, the user plane gateway, and the UE;
- the IN-PDN is a local PDN proposed by the application to meet the requirements of the local networking.
- the data in the IN-PDN does not need to go through the aggregation core layer and the internet, and can directly perform local loopback in the core network, thereby reducing mobility.
- Network pressure reduces transmission delay.
- the foregoing implementation mainly describes that when the first UE accessing the first IN-PDN is detached from the first base station, it is determined whether the IN-PDN is to be scaled according to whether the second UE and the second user plane gateway are present.
- the controller determines whether the second UE exists, that is, whether the UE still exists in the first IN-PDN on the first GW-U after the first UE completes the handover or detach.
- the controller determines whether the second GW-U exists, that is, whether the first IN-PDN is distributed across the first GW-U and other GW-Us.
- the first UE detaching from the first base station may include the following two scenarios:
- the first UE is handed over from the first base station to the second base station;
- the first UE is detached from the first base station.
- the IN-PDN distribution information may be used to indicate a mapping relationship between the IN-PDN and the user plane gateway, a mapping relationship between the user plane gateway and the UE, and between the IN-PDN and the UE. Mapping relations.
- the method before the controller determines, according to the IN-PDN distribution information, whether the second UE and the second user plane gateway are present, the method further includes:
- the controller deletes a mapping relationship between the first UE and the first user plane gateway in the IN-PDN distribution information.
- the judgment result is that the second user plane gateway exists in the IN-PDN distribution information, but the second UE does not exist. ;
- Determining, by the controller, whether there is the second UE and the second user plane gateway Determining whether to update a mapping relationship between the first IN-PDN and a forwarding tunnel, a mapping relationship between the first IN-PDN and the first UE, and the first IN-PDN and user plane Mapping between gateways, including:
- the controller deletes a mapping relationship between the first user plane gateway and the first IN-PDN, and between the first user plane gateway and the first UE in the IN-PDN distribution information. a mapping relationship and a mapping relationship between the first UE and the first IN-PDN;
- the controller acquires the tunnel identifier corresponding to the first IN-PDN, and sends an indication message to the control plane gateway, where the indication message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is deleted,
- the first user plane gateway and the second user plane gateway are forwarding tunnels of the endpoint, and are used to indicate deletion between the first user plane gateway and the second user plane gateway and the first IN- Processing rules and forwarding rules between UEs associated with the PDN.
- the control plane gateway deletes the forwarding tunnel across the first user plane gateway and other user plane gateways for the first IN-PDN, thereby realizing the dynamic contraction of the IN-PDN.
- resource recovery may also be performed on the first IN-PDN on the first GW-U.
- the recovered resources include a first IN-PDN identifier and a tunnel port corresponding to the first IN-PDN on the first GW-U.
- the first IN-PDN identity and tunnel port after the reclaiming can be reused when other IN-PDNs are created, so that the IN-PDN identity and the tunnel port are not enough.
- the method further includes:
- the first IN-PDN has a mapping relationship
- the controller creates the first IN-PDN on the third user plane gateway, and in the And adding, to the IN-PDN distribution information, a mapping relationship between the third user plane gateway and the first IN-PDN, and adding a mapping relationship between the third user plane gateway and the first UE;
- the controller adds the third user plane gateway and the first UE to the IN-PDN distribution information. Mapping relationship.
- Determining, by the controller, whether to update a mapping relationship between the first IN-PDN and the forwarding tunnel, the first IN-PDN, according to whether a judgment result of the second UE and the second user plane gateway is present The mapping relationship between the mapping relationship with the first UE and the first IN-PDN and the user plane gateway includes:
- the controller deletes, in the IN-PDN distribution information, a mapping relationship between the first user plane gateway and the first IN-PDN, and between the first UE and the first IN-PDN Mapping relationship;
- the controller acquires the tunnel identifier corresponding to the first IN-PDN, and sends an indication message to the control plane gateway, where the indication message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is deleted,
- the first user plane gateway and the second user plane gateway are forwarding tunnels of the endpoint, and are used to indicate deletion between the first user plane gateway and the second user plane gateway and the first IN- a processing rule and a forwarding rule between the UEs associated with the PDN, and indicating that the tunnel identifier corresponding to the first IN-PDN is created, and the second user plane gateway and the third user plane gateway are disconnected a forwarding tunnel of the point, and a processing rule and a forwarding rule for instructing creation of the UE associated with the first IN-PDN between the second user plane gateway and the third user plane gateway.
- the control plane gateway deletes the forwarding tunnel across the first user plane gateway and other user plane gateways for the first IN-PDN, and creates a first IN-PDN for the first IN-PDN.
- the dynamic tunneling of the IN-PDN is implemented across the forwarding tunnel of the third user plane gateway and other user plane gateways.
- the determining result is that the second user plane gateway and the second UE are in the IN-PDN distribution information, and the third user plane gateway is opposite to the first IN - When there is no mapping relationship between PDNs;
- Determining, by the controller, whether to update a mapping relationship between the first IN-PDN and the forwarding tunnel, the first IN-PDN, according to whether a judgment result of the second UE and the second user plane gateway is present The mapping relationship between the mapping relationship with the first UE and the first IN-PDN and the user plane gateway includes:
- the controller acquires a tunnel identifier corresponding to the first IN-PDN, and sends an indication message to the control plane gateway, where the indication message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is created as an identifier
- the first user plane gateway and the third user plane gateway are forwarding tunnels of the endpoint, and are used to indicate that the tunnel identifier corresponding to the first IN-PDN is created
- the second user plane gateway is
- the third user plane gateway is a forwarding tunnel of a breakpoint, and is configured to instruct processing between the UE that is associated with the first IN-PDN between the first user plane gateway and the third user plane gateway.
- a rule and a forwarding rule, and a processing rule and a forwarding rule for instructing creation of the UE associated with the first IN-PDN between the second user plane gateway and the third user plane gateway.
- the control plane gateway creates a forwarding tunnel across the third user plane gateway and other user plane gateways for the first IN-PDN, and implements Dynamic expansion of IN-PDN.
- Determining, by the controller, whether to update a mapping relationship between the first IN-PDN and the forwarding tunnel, the first IN-PDN, according to whether a judgment result of the second UE and the second user plane gateway is present The mapping relationship between the mapping relationship with the first UE and the first IN-PDN and the user plane gateway includes:
- the controller acquires a tunnel identifier corresponding to the first IN-PDN, and sends an indication message to the control plane gateway, where the indication message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is created as an identifier,
- the first user plane gateway and the third user plane gateway are forwarding tunnels of the endpoint, and are used to indicate that the first user plane gateway and the third user plane gateway are created and the first IN- Processing rules and forwarding rules between UEs associated with the PDN.
- the control plane gateway creates a forwarding tunnel across the third user plane gateway and other user plane gateways for the first IN-PDN, and implements the IN. - Dynamic expansion of PDN.
- the method before the controller sends an indication message to the control plane gateway, the method further includes:
- the processing rule and the forwarding rule between the UE associated with the first IN-PDN between the second user plane gateway and the third user plane gateway are:
- Adding the second IN-PDN identifier to the packet sent by the UE in the first IN-PDN of the second user plane gateway to the first UE, and adding the second IN- The second IN-PDN identifier in the packet identified by the PDN is replaced with the tunnel identifier corresponding to the first IN-PDN, and the replaced packet is forwarded to the third tunnel by using the second tunnel port. Port; and, by the said The second tunnel port receives the packet from the third tunnel port, and replaces the tunnel identifier corresponding to the first IN-PDN in the packet received by the second tunnel port with the second IN-PDN identifier. And deleting the second IN-PDN identifier in the replaced message;
- Adding the third IN-PDN identifier to the message of the UE in the first IN-PDN sent by the first UE to the second user plane gateway, and adding the third IN- The third IN-PDN identifier in the packet identified by the PDN is replaced with the tunnel identifier corresponding to the first IN-PDN, and the replaced packet is forwarded to the second tunnel through the third tunnel port.
- the foregoing implementation manner defines a processing rule and a forwarding rule between the UE associated with the first IN-PDN between the second GW-U and the third GW-U, thereby ensuring the local networking of the UE.
- the method before the controller sends an indication message to the control plane gateway, the method further includes:
- the processing rule and the forwarding rule between the first user plane gateway and the third user plane gateway that are associated with the first IN-PDN are:
- the foregoing implementation manner defines a processing rule and a forwarding rule between the UE associated with the first IN-PDN between the first GW-U and the third GW-U, thereby ensuring the local networking of the UE.
- the first IN-PDN is implemented through a virtual local area network VLAN
- the tunnel identifier corresponding to the first IN-PDN is represented by a virtual extended local area network identifier VNI;
- the first tunnel port, the second tunnel port, and the third tunnel port are represented by an internet protocol IP address of a virtual extended local area network tunnel endpoint VTEP;
- the first IN-PDN identifier, the second IN-PDN identifier, and the third IN-PDN identifier are represented by a VLAN identifier.
- a controller having the function of implementing the above method.
- the functions may be implemented by hardware or by corresponding software implemented by hardware.
- the hardware or software includes one or more modules or units corresponding to the functions described above.
- the controller includes a determining unit, a determining unit, and a processing unit:
- the determining unit is configured to determine, according to the IN-PDN distribution information, a first IN-PDN and a first access that the first UE accesses before being detached from the first base station, when the first UE is detached from the first base station a user plane gateway; the IN-PDN distribution information is used to indicate a mapping relationship between the IN-PDN, the user plane gateway, and the UE;
- the determining unit is configured to determine, according to the IN-PDN distribution information, whether there is a second UE and a second user plane gateway, where a mapping relationship exists between the second UE and the first IN-PDN, and the A mapping relationship exists between the second UE and the first user plane gateway, and a mapping relationship exists between the second user plane gateway and the first IN-PDN.
- the processing unit is configured to determine, according to the determination result of the determining unit whether the second UE and the second user plane gateway are present, whether to update a mapping relationship between the first IN-PDN and the forwarding tunnel And a mapping relationship between the first IN-PDN and the first UE and a mapping relationship between the first IN-PDN and a user plane gateway.
- the controller includes a processor and a memory for storing the processor executable instructions, and the memory and the processor are connected to each other by a bus system; Do the following:
- - PDN distribution information is used to indicate a mapping relationship between the IN-PDN, the user plane gateway, and the UE;
- the technical solution provided by the present application implements the dynamic scaling of the IN-PDN.
- the UE migrates or detaches, the continuity of the services in the local networking of the UE can be ensured, and the unused IN-PDNs are recovered in time. Resources, avoiding the waste of IN-PDN resources.
- FIG. 1 is a schematic diagram of a conventional PDN network in the prior art
- FIG. 2 is a schematic diagram of a network of an IN-PDN according to an embodiment of the present application.
- FIG. 3 is a schematic diagram of a scenario of an IN-PDN expansion according to an embodiment of the present disclosure
- FIG. 4 is a schematic structural diagram of a system for applying a network management method according to an embodiment of the present application
- FIG. 5 is a flowchart of a network management method according to an embodiment of the present application.
- FIG. 6 is a schematic diagram of signaling interaction between network elements in a UE handover scenario according to an embodiment of the present disclosure
- FIG. 7 is a schematic diagram of signaling interaction between network elements in a UE detachment scenario according to an embodiment of the present disclosure
- FIG. 8 is a schematic structural diagram of a controller according to an embodiment of the present application.
- FIG. 9 is a schematic structural diagram of another controller according to an embodiment of the present application.
- FIG. 2 is a schematic diagram of an IN-PDN.
- An IN-PDN represents a local network, and the UE can identify the UE by using an In-Network Access Point Name (IN-APN). Visited IN-PDN.
- the IN-PDN is deployed at the edge of the mobile network, connecting edge/intranet applications while providing connectivity for local interconnections between UEs. In this way, the data in the IN-PDN does not need to go through the aggregation core layer and the internet, and can directly perform local loopback in the core network, thereby reducing the pressure on the mobile network and reducing the transmission delay.
- IN-PDN can be dynamically created, scalable (or migratable) and can be associated with multiple GateWay of User Plane (GW-U). characteristic.
- GW-U GateWay of User Plane
- the present application introduces a new network element or a logical processing unit IN-PDN controller (Controller).
- the "dynamic creation" of the IN-PDN mainly includes the following process: the IN-PDN controller selects a GW-U for the UE according to the location information and the service information of the UE, and then instructs the Gateway of Controller Plane (GW-: GW- C) Corresponding relationship between the message sent by the UE and the IN-PDN, The corresponding forwarding rule and processing rule are sent to the GW-U, thereby completing the dynamic creation of the IN-PDN.
- GW- Gateway of Controller Plane
- the mapping between the message sent by the UE and the IN-PDN may be jointly represented by the feature point of the message sent by the UE and the feature point of the IN-PDN.
- the feature point of the message sent by the UE may be the tunnel end point (Tunnel Endpoint).
- the Identifier which is called the TEID, the Internet Protocol (IP) address or the destination IP address of the UE, and the feature point of the IN-PDN may be a Virtual Local Area Network Identity (VLAN ID).
- the processing rule is to perform the operations of encapsulating and decapsulating the packet by the GW-U, including adding/deleting an IN-PDN identifier in the packet header, and adding/deleting a tunnel identifier in the packet header.
- the forwarding rule includes the process of forwarding the encapsulated packet from the port, and forwarding the decapsulated packet to the corresponding UE.
- the "scalable" of the IN-PDN means that the IN-PDN can dynamically adjust the coverage of the IN-PDN as the UE moves.
- both UE 1 and UE 2 are in IN-PDN 1 of GW-U 1, and at time t2, since UE 1 moves to GW-U 2, UE 1 and UE 2 are distributed in Under different GW-Us, in order to ensure the continuity of services in the local networking of UE 1, it is necessary to extend IN-PDN 1 to GW-U 2. From time t1 to time t2, it is an extended scene of IN-PDN.
- time t3 as UE 2 moves, UE 1 and UE 2 are again distributed under the same GW-U. In order to recover the related resources of IN-PDN 1, it is necessary to shrink IN-PDN 1 to GW-U 2. From time t2 to time t3, it is the contraction scene of IN-PDN.
- the IN-PDN can be extended to multiple GW-Us, the IN-PDN can be associated with multiple GW-Us simultaneously. For example, at time t2 of FIG. 3, IN-PDN 1 is associated with both GW-U 1 and GW-U 2 .
- the "IN-PDN distribution information" is stored on the IN-PDN controller and is used to indicate the mapping relationship between the IN-PDN, the GW-U, and the UE, and may include a mapping relationship between the IN-PDN and the GW-U.
- the IN-PDN controller adjusts the IN in real time according to the actual situation.
- -PDN distribution information For example, at time t1 in FIG.
- mapping relationship between IN-PDN 1 and GW-U 1 and the mapping relationship between GW-U 1 and UE 1 and UE 2 are respectively stored in the IN-PDN distribution information.
- IN-PDN 1 A mapping relationship with UE 1 and UE 2, respectively.
- first, second, third, etc. may be used to describe various information in this application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
- first information may also be referred to as the second information without departing from the scope of the present application.
- second information may also be referred to as the first information.
- word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
- Local network refers to a certain range of UEs forming a local network that is closer to the user. Data forwarding between UEs is directly performed in the local network without going through the core network and the internet.
- 5G fifth-generation mobile communication technology
- this application proposes a new network, IN-PDN, and proposes a network management method and controller for implementing dynamic scaling of IN-PDN in IN-PDN expansion. How to maintain service continuity in the local network and how to recover the related resources of the IN-PDN in the IN-PDN contraction scenario.
- the network management method provided by the present application is applicable to the system shown in FIG. 4, and includes MME 401, IN-PDN controller 402, GW-C 403, GW-U 404, and base station 405.
- the connection between NEs means that there is an interface between NEs at both ends of the connection.
- the system introduces a new network element or logical processing unit IN-PDN controller 402 based on the existing architecture, and an interface exists between the IN-PDN controller 402 and the GW-C 403, and the IN-PDN controller
- the GW-C 403 controls the GW-U 404 according to the content of the indication message by transmitting an indication message to the GW-C 403.
- the advantage of this architecture is that one can directly use the existing system architecture and implementation methods to reduce the cost of changing the system architecture; second, if the IN-PDN controller 402 is added to the GW-U 404 control, then GW The -U 404 has two control network elements, and the control information between the GW-C 403 and the IN-PDN controller 402 needs to be synchronized, which causes additional overhead.
- the IN-PDN controller 402 can also be integrated in an existing network element, such as integrated in the GW-C 403, so that the IN-PDN controller 402 can be executed by the GW-C 403. The function.
- MME 401 used for access control, mobility management, session management, user authentication and key management, non-access stratum (NAS) signaling encryption and integrity protection, GW-C 403 selection
- MME selection used for access control, mobility management, session management, user authentication and key management, non-access stratum (NAS) signaling encryption and integrity protection, GW-C 403 selection
- TAI Tracking Area Identity
- the IN-PDN controller 402 is configured to save the IN-PDN distribution information, deliver the IN-PDN configuration information to complete the creation of the IN-PDN, and instruct the GW-C 403 to reselect the GW-U 404, where the IN-PDN configuration information is included.
- the IN-PDN identifier assigned by the IN-PDN controller 402 for the IN-PDN to be created is carried.
- the IN-PDN controller 402 is further configured to allocate a forwarding tunnel identifier to the IN-PDN, and indicate to which GW-C 404 the GW-C 403 creates a forwarding tunnel and update processing rules and forwarding rules.
- the IN-PDN controller 402 is also used to indicate to which GW-C 404 the GW-C 403 deletes the forwarding tunnel and updates the processing rules and forwarding rules.
- a "controller” is sometimes used as an abbreviation for the IN-PDN controller 402.
- GW-C 403 configured to send a UE mobile event notification to the IN-PDN controller 402, including a UE handover event and a UE detach event; and for creating between the GW-U 404 according to the indication of the IN-PDN controller 402. Or delete the forwarding tunnel and update the processing rules and forwarding rules on the GW-U 404.
- the GW-U 404 is configured to encapsulate, decapsulate, and forward the packet according to the processing rule and the forwarding rule delivered by the GW-C 403.
- the base station 405 is used for radio resource management, header compression and encryption, MME 401 selection, uplink and downlink quality of service (referred to as QoS) execution, paging message scheduling and transmission, system broadcast message scheduling and transmission, admission control, and the like.
- QoS uplink and downlink quality of service
- one base station 405 can correspond to multiple GW-Us 404.
- the wireless communication system of the base station 405 may include, but is not limited to, Global System of Mobile communication (GSM), Code Division Multiple Access (CDMA) IS-95, and code division multiple access.
- GSM Global System of Mobile communication
- CDMA Code Division Multiple Access
- CDMA Code Division Multiple Access
- 2000 Time Division-Synchronous Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- Time Division Duplexing-Long Term Evolution (TDD LTE) Time Division Duplexing-Long Term Evolution
- FDD LTE Frequency Division Duplexing-Long Term Evolution
- LTE-Enhancement Long Term Evolution-Advanced (LTE-advanced
- PHS Personal Handy-phone System
- WiFi Wireless Fidelity
- 802.11 series protocol and global microwave interconnection Worldwide Interoperability for Microwave Access (WiMAX)
- WiMAX Worldwide Interoperability for Microwave Access
- the embodiment of the present application further provides a network management method. As shown in FIG. 5, the method includes the following steps:
- Step 501 When the first UE is detached from the first base station, the controller determines, according to the pre-stored IN-PDN distribution information, the first IN-PDN and the first access that the first UE accesses before detaching from the first base station.
- One GW-U One GW-U.
- the first UE is detached from the first base station, and may include the following two scenarios:
- Scenario 1 The first UE switches from the first base station to the second base station, so that the controller determines the first IN-PDN that the root first UE accesses before switching from the first base station to the second base station. And the first GW-U.
- Scenario 2 The first UE is detached from the first base station, so that the controller determines the first IN-PDN and the first GW-U that the first UE accesses before detaching from the first base station.
- the mobile event of the first UE may be notified to the controller by the GW-C.
- the controller may further delete the mapping relationship between the first UE and the first GW-U in the IN-PDN distribution information.
- Step 502 The controller determines, according to the IN-PDN distribution information, whether there is a second UE and a second GW-U, and a mapping relationship exists between the second UE and the first IN-PDN, and the There is also a mapping relationship between the second UE and the first GW-U, and a mapping relationship exists between the second GW-U and the first IN-PDN.
- the second GW-U in the present application generally refers to any one of the other GW-Us except the first GW-U that has a mapping relationship with the first IN-PDN.
- the controller further needs to determine that the first UE is switching from the first base station to the first The third GW-U accessed after the second base station. Then, the controller determines, according to the IN-PDN distribution information, whether the third GW-U has a mapping relationship with the first IN-PDN.
- the controller creates the first IN-PDN on the third GW-U, specifically creating an IN-
- the process of the PDN can be referred to the above description, and details are not described herein again.
- the controller further adds a mapping relationship between the third GW-U and the first IN-PDN in the IN-PDN distribution information, and adds the third GW-U and the first Mapping relationship of the UE.
- the controller adds the third GW-U and the first only in the IN-PDN distribution information. Mapping relationship of the UE.
- Step 503 The controller determines whether to update a mapping relationship between the first IN-PDN and the forwarding tunnel according to a determination result of the second UE and the second GW-U, where the first a mapping relationship between the IN-PDN and the first UE and a mapping relationship between the first IN-PDN and the GW-U.
- first UE and the second UE are different UEs, and the first GW-U and the second GW-U are different GW-Us, and the second GW-U And the third GW-U It may be that the same GW-U may also be a different GW-U.
- the controller determines whether the second UE exists, that is, whether there is still a UE in the first IN-PDN on the first GW-U after the first UE completes the handover or detachment.
- the controller determines whether the second GW-U exists, that is, whether the first IN-PDN is distributed across the first GW-U and other GW-Us.
- the following may be subdivided into 10 types as shown in Table 1 to Table 3.
- the scenarios in which the first IN-PDN needs to be performed in the 10 scenarios are also shown in Tables 1 to 3.
- the mapping between the third GW-U to be accessed by the first UE and the first IN-PDN exists.
- the mapping between the third GW-U to be accessed by the first UE and the first IN-PDN does not exist.
- Scenario 1 The first UE migrates to the third GW-U of the second base station, and the third GW-U has established the first IN-PDN required by the first UE. Before the first UE migrates, the first IN- The PDN is distributed across the first GW-U and other GW-Us. After the first UE is migrated, there are still other UEs in the first IN-PDN on the first GW-U.
- the controller since the first IN-PDN on the first GW-U is still used by other UEs, there is no need to perform resource recovery on the first IN-PDN on the first GW-U. And, since the first IN-PDN has covered the first GW-U and the third GW-U, the first UE and other UEs in the first IN-PDN on the first GW-U before the handover may be normal. Communication. Therefore, in the scenario, the controller only needs to add the mapping relationship between the third GW-U and the first UE in the IN-PDN distribution information, and does not need to shrink or expand the first IN-PDN.
- Scenario 2 The first UE migrates to the third GW-U of the second base station, and the third GW-U has established the first IN-PDN required by the first UE. Before the first UE migrates, the first IN- The PDN is distributed across the first GW-U and other GW-Us. After the first UE is migrated, there are no other UEs in the first IN-PDN on the first GW-U.
- scenario 2 since there are no more UEs in the first IN-PDN on the first GW-U, the UEs distributed in the first IN-PDN of other GW-Us are not associated with the first GW-U. UE has business The exchanges. In order to avoid waste of resources, resource recovery may be performed on the first IN-PDN on the first GW-U, and the first IN-PDN may be contracted.
- the recovered resources include a first IN-PDN identifier and a tunnel port corresponding to the first IN-PDN on the first GW-U.
- the first IN-PDN identity and tunnel port after the reclaiming can be reused when other IN-PDNs are created, so that the IN-PDN identity and the tunnel port are not enough.
- the specific process of the controller shrinking the first IN-PDN is as follows: the controller adds a mapping relationship between the third GW-U and the first UE in the IN-PDN distribution information, and is in the IN- The mapping relationship between the first GW-U and the first IN-PDN and the mapping relationship between the first UE and the first IN-PDN are deleted in the PDN distribution information. And the controller may obtain the tunnel identifier corresponding to the first IN-PDN, and send an indication message to the GW-C, where the indication message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is deleted.
- UE1 accesses IN-PDN1 on GW-U1, and IN-PDN1 is distributed on GW-U1, GW-U2, and GW-U3. If UE 1 migrates from GW-U1 to GW-U2, There are no other UEs in the first IN-PDN on the GW-U1, UE2 in the IN-PDN1 of the GW-U2, and UE3 and UE4 in the IN-PDN1 of the GW-U3.
- the GW-U1 and GW-U2 can be deleted. Processing rules and forwarding rules between UE1 and UE2 associated with IN-PDN1, and processing rules and forwarding rules between UE3 and UE4 respectively associated with IN-PDN1 between GW-U1 and GW-U3.
- each IN-PDN has a unique tunnel identifier.
- the tunnel identifier of the IN-PDN and the endpoint information of the forwarding tunnel are stored in the IN-PDN distribution information.
- Scenario 3 The first UE migrates to the third GW-U of the second base station, and the third GW-U has not established the first IN-PDN required by the first UE. Before the first UE migrates, the first IN- The PDN is distributed across the first GW-U and other GW-Us. After the first UE is migrated, there are still other UEs in the first IN-PDN on the first GW-U.
- the first UE has a business relationship with the first GW-U before migration or with other UEs on the GW-U with the first IN-PDN, then only on the migrated third GW-U The creation of a new IN-PDN will result in the interruption of the local networking service of the first UE.
- the specific process of the controller expanding the first IN-PDN in scenario 3 is as follows: the controller creates the first IN-PDN on the third GW-U, and in the IN-PDN The mapping relationship between the third GW-U and the first IN-PDN is added to the distribution information, and the mapping relationship between the third GW-U and the first UE is added. And the controller acquires the tunnel identifier corresponding to the first IN-PDN, and sends an indication message to the GW-C, where the indication message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is created.
- the third user plane gateway is a forwarding tunnel of the breakpoint, and is used to indicate that the UE between the first GW-U and the third GW-U that is associated with the first IN-PDN is created.
- Scenario 4 The first UE migrates to the third GW-U of the second base station, and the third GW-U has not established the first IN-PDN required by the first UE. Before the first UE migrates, the first IN- PDN cross The first GW-U and other GW-Us are distributed. After the first UE is migrated, there are no other UEs in the first IN-PDN on the first GW-U.
- the specific process of the controller shrinking and expanding the first IN-PDN is as follows: the controller creates the first IN-PDN on the third GW-U, in the IN-PDN Adding a mapping relationship between the third GW-U and the first IN-PDN, and adding a mapping relationship between the third GW-U and the first UE, and distributing the IN-PDN in the distribution information The mapping relationship between the first GW-U and the first IN-PDN and the mapping relationship between the first UE and the first IN-PDN are deleted.
- the controller acquires the tunnel identifier corresponding to the first IN-PDN, and sends an indication message to the GW-C, where the indication message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is deleted.
- a forwarding tunnel with the first GW-U and the second GW-U as an endpoint, and for indicating deletion between the first GW-U and the second GW-U and the first
- the processing rule and the forwarding rule associated with the IN-PDN, and the indication that the tunnel identifier corresponding to the first IN-PDN is created, and the second user plane gateway and the third user plane gateway are used as breakpoints a forwarding tunnel, and a processing rule and a forwarding rule for instructing creation of the second GW-U and the third GW-U to be associated with the first IN-PDN.
- Scenario 5 The first UE migrates to the third GW-U of the second base station, and the third GW-U has not established the first IN-PDN required by the first UE. Before the first UE migrates, the first IN- The PDN is only distributed on the first GW-U. After the first UE is migrated, there are still other UEs in the first IN-PDN on the first GW-U.
- the specific process for the controller to extend the first IN-PDN is as follows: the controller creates the first IN-PDN on the third GW-U, and distributes the IN-PDN Adding a mapping relationship between the third GW-U and the first IN-PDN, and adding the third Mapping relationship between the GW-U and the first UE. And the controller acquires the tunnel identifier corresponding to the first IN-PDN, and sends an indication message to the GW-C, where the indication message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is created.
- a forwarding tunnel with the first GW-U and the third GW-U as an endpoint, and configured to indicate that the first GW-U and the third GW-U are created and the first Processing rules and forwarding rules between UEs associated with IN-PDN.
- Scenario 6 The first UE migrates to the third GW-U of the second base station, and the third GW-U has not established the first IN-PDN required by the first UE. Before the first UE migrates, the first IN- The PDN is only distributed on the first GW-U. After the first UE is migrated, there are no other UEs in the first IN-PDN on the first GW-U.
- the first IN-PDN covers only one GW-U, but the coverage of the first IN-PDN is adjusted by the first GW-U to the third GW-U. It can be considered that the first IN-PDN has migrated.
- the specific process for the controller to migrate the first IN-PDN is as follows: the controller creates the first IN-PDN on the third GW-U, and distributes in the IN-PDN Adding a mapping relationship between the third GW-U and the first IN-PDN, and adding a mapping relationship between the third GW-U and the first UE. And the controller deleting, in the IN-PDN distribution information, a mapping relationship between the first GW-U and the first IN-PDN, and the first UE and the first IN-PDN The mapping relationship between them.
- the controller may also recover the resources of the first IN-PDN in scenario 6. Since the first IN-PDN is only distributed on the first GW-U, the first IN-PDN does not have a corresponding forwarding tunnel, so the resources recovered here only include the first IN-PDN on the first GW-U. Corresponding first IN-PDN identifier. The first IN-PDN corresponds to the first IN-PDN identifier on the first GW-U.
- Scenario 7 The first UE is detached from the first GW-U. Before the first UE is detached, the first IN-PDN is distributed across the first GW-U and other GW-Us, and the first GW-U is allocated. There are still other UEs in an IN-PDN.
- the controller since the first IN-PDN on the first GW-U is still used by other UEs, there is no need to perform resource recovery on the first IN-PDN on the first GW-U. Therefore, the controller only needs Deleting a mapping relationship between the first UE and the first IN-PDN and a mapping relationship between the first GW-U and the first UE in the IN-PDN distribution information, without The first IN-PDN is shrunk or expanded.
- Scenario 8 The first UE is detached from the first GW-U. Before the first UE is detached, the first IN-PDN is distributed across the first GW-U and other GW-Us, and the first GW-U is allocated. There are no other UEs in an IN-PDN.
- scenario 8 since there are no more UEs in the first IN-PDN on the first GW-U, the UEs distributed in the first IN-PDN of other GW-Us are not associated with the first GW-U.
- the UE has business contacts.
- resource recovery may be performed on the first IN-PDN on the first GW-U, and the first IN-PDN may be contracted.
- the specific process of the controller shrinking the first IN-PDN is as follows: the controller deletes the first GW-U and the first IN-PDN in the IN-PDN distribution information. a mapping relationship between the first GW-U and the first UE and a mapping relationship between the first UE and the first IN-PDN. And the controller acquires the tunnel identifier corresponding to the first IN-PDN, and sends an indication message to the GW-C, where the indication message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is deleted. a forwarding tunnel with the first GW-U and the second GW-U as an endpoint, and for indicating deletion between the first GW-U and the second GW-U and the first Processing rules and forwarding rules between UEs associated with IN-PDN.
- Scenario 9 The first UE is detached from the first GW-U. Before the first UE is detached, the first IN-PDN is only distributed on the first GW-U, and the first IN- on the first GW-U There are still other UEs in the PDN.
- Scene 9 is similar to scenario 7.
- the controller only needs to delete the mapping relationship between the first UE and the first IN-PDN and the first GW-U and the foregoing in the IN-PDN distribution information.
- the mapping relationship between the first UEs without shrinking or expanding the first IN-PDN.
- Scenario 10 The first UE is detached from the first GW-U. Before the first UE is detached, the first IN-PDN is only distributed on the first GW-U, and the first IN- on the first GW-U There are no other UEs in the PDN.
- the controller may delete the first IN-PDN and reclaim the first IN- after the first UE is detached.
- PDN resources Since the first IN-PDN is only distributed on the first GW-U, the first IN-PDN does not have a corresponding forwarding tunnel, so the resources recovered here only include the first IN-PDN on the first GW-U. Corresponding first IN-PDN identifier.
- the controller since the IN-PDN in this application is only a virtual network, the process of creating an IN-PDN does not need to apply for actual network resources. Therefore, when deleting the first IN-PDN, the controller only needs to delete the mapping relationship between the first GW-U and the first IN-PDN, the first GW, in the IN-PDN distribution information. a mapping relationship between the U and the first UE and a mapping relationship between the first UE and the first IN-PDN.
- the following describes the processing rules and forwarding rules between the second GW-U and the third GW-U and the UE associated with the first IN-PDN mentioned in the foregoing scenario 3 to scenario 5, and the Processing rules and forwarding rules between UEs associated with the first IN-PDN between the first GW-U and the third GW-U.
- the controller may respectively determine, according to the IN-PDN distribution information, a first IN-PDN corresponding to the first IN-PDN on the first GW-U. And the first tunnel port, the first IN-PDN corresponding to the second IN-PDN identifier and the second tunnel port on the second GW-U, and the first IN-PDN in the third A corresponding third IN-PDN identifier and a third tunnel port on the GW-U.
- the processing rule and forwarding rule between the UE associated with the first IN-PDN between the second GW-U and the third GW-U is: in the second GW-U Adding the second IN-PDN identifier to the packet sent by the UE in the first IN-PDN to the first UE, and adding the second in the packet of the second IN-PDN identifier
- the IN-PDN identifier is replaced with the tunnel identifier corresponding to the first IN-PDN, and the replaced packet is forwarded to the third tunnel port by using the second tunnel port; and, through the second tunnel port Receiving a packet from the third tunnel port, replacing the tunnel identifier corresponding to the first IN-PDN in the packet received by the second tunnel port with the second IN-PDN identifier, and deleting The second in the replaced message IN-PDN logo.
- the third IN-PDN identifier in the packet identified by the PDN is replaced with the tunnel identifier corresponding to the first IN-PDN, and the replaced packet is forwarded to the second tunnel through the third tunnel port.
- the processing rule and forwarding rule between the UE associated with the first IN-PDN between the first GW-U and the third GW-U is: in the first part of the first GW-U Adding the first IN-PDN identifier to the packet sent by the UE in the IN-PDN to the first UE, and adding the first IN- in the packet of the first IN-PDN identifier Replacing the PDN identifier with the tunnel identifier corresponding to the first IN-PDN, and forwarding the replaced packet to the third tunnel port by using the first tunnel port; and receiving, by the first tunnel port, The packet of the third tunnel port replaces the tunnel identifier corresponding to the first IN-PDN in the packet received by the first tunnel port with the first IN-PDN identifier, and deletes the replacement The first IN-PDN identifier in the message.
- the IN-PDN can be implemented by a virtual local area network (VLAN) technology, but is not limited to the VLAN technology.
- the IN-PDN can also be implemented by a local area network (LAN) technology.
- VLAN virtual local area network
- LAN local area network
- the forwarding tunnel of the first IN-PDN may pass through a virtual extended local area network (Virtual Extensible LAN, VxLAN for short).
- the tunnel identifier corresponding to the first IN-PDN may be represented by a virtual extended local area network identifier (VxLAN Network Identifier, VNI for short); the first tunnel port, the second tunnel port, and the third The tunnel port may be represented by an IP address of a virtual extended network tunnel endpoint (VTEP); the first IN-PDN identifier, the second IN-PDN identifier, and the third IN-PDN identifier.
- VNI virtual extended local area network identifier
- VTEP virtual extended network tunnel endpoint
- the first IN-PDN identifier, the second IN-PDN identifier, and the third IN-PDN identifier Can be represented by a VLAN ID.
- the first embodiment corresponds to the foregoing scenario 4, that is, the first UE migrates from the first GW-U of the first base station to the third GW-U of the second base station, and the third GW-U does not need to establish the first UE.
- First IN-PDN before the first UE migration, the first IN-PDN is distributed across the first GW-U and other GW-Us, after the first UE migration, within the first IN-PDN on the first GW-U There are no other UEs.
- the target eNB sends a Path Switch Request message to the MME, carrying the GTP address and TEID of the target eNB, and carrying the target TAI information.
- the target eNB here is equivalent to the second base station previously described.
- the MME sends a Modify Bearer Request message to the GW-C, and notifies the GW-C of the General Packet Radio Service Tunneling Protocol (GTP) address and the TEID and the target TAI information of the target eNB.
- GTP General Packet Radio Service Tunneling Protocol
- the GW-C sends a UE mobile event notification to the IN-PDN controller, informing the first UE to move from the source eNB to the target eNB.
- the source eNB here is equivalent to the first base station previously described.
- the IN-PDN controller determines the gateway reselection according to the location information of the first UE and the service and the like.
- the IN-PDN controller sends a gateway reselection request to the GW-C.
- step 5 If the gateway reselection request in step 5 carries the information of the target GW-U, such as the IP address of the target GW-U, then directly jumps to step 7, otherwise the gateway reselection is performed by the GW-C.
- the DNS request may be sent to the domain name system (DNS), and the DNS request carries the IN-APN of the first UE.
- DNS domain name system
- the DNS judges the IN-APN carried in the received DNS request. If it is determined to be in the IN-APN format, the IN-APN of the first UE and the cell information of the first UE are used in the locally stored GW-U information. The matched GW-U is queried, and the matched GW-U is located close to the first UE and the IN-PDN corresponding to the IN-APN of the first UE has been created.
- the DNS will return the matched IP address of the GW-U to the GW-C in the DNS request response.
- the DNS requests the IN-PDN controller to select a new GW-U for the UE.
- the IN-PDN controller determines a new GW-U for the UE, the IN-PDN controller returns the cell information of the first UE, the IN-APN, and the new GW-U information to the DNS, and then the IN-PDN by the DNS.
- the IP address of the selected GW-U is carried back to the GW-C in the DNS request response.
- the GW-C sends a request to the DNS, and the DNS can directly return the corresponding The GW-U no longer needs to request the IN-PDN controller to select the GW-U for the other UE.
- the GW-C sends a gateway reselection response to the IN-PDN controller, and carries the TEID and IP address of the target GW-U that is reselected by the first UE.
- the target GW-U here is equivalent to the third GW-U in the foregoing.
- the IN-PDN controller queries the current IN-PDN distribution information, and finds that the first IN-PDN that the first UE needs to access has not been created on the target GW-U, and the first IN-PDN cross-source GW-U and other GWs. -U distribution, there is no longer any UE other than the first UE in the first IN-PDN on the source GW-U.
- the source GW-U is equivalent to the first GW-U in the foregoing
- the other GW-Us distributed with the first IN-PDN are equivalent to the second GW-U in the foregoing, and the first IN-PDN on the source GW-U.
- the other UEs are equivalent to the second UEs described above.
- the IN-PDN controller sends an IN-PDN configuration notification to the GW-C, and the GW-C forwards the IN-PDN configuration notification to the target GW-U, and the IN-PDN configuration notification carries the IN-PDN configuration information.
- the IN-PDN configuration information includes an IN-PDN identifier of the first IN-PDN allocated by the IN-PDN controller for the first IN-PDN to be configured on the target GW-U.
- the target GW-U After completing the IN-PDN configuration, the target GW-U sends an IN-PDN configuration notification acknowledgement (Ack) to the GW-C, and the GW-C forwards the IN-PDN configuration notification acknowledgement to the IN-PDN controller.
- Ack IN-PDN configuration notification acknowledgement
- the IN-PDN controller queries the tunnel identifier corresponding to the first IN-PDN in the IN-PDN distribution information, and updates the first IN-PDN between the first IN-PDN and the GW-U in the IN-PDN distribution information.
- the information of the source GW-U and the corresponding VLAN ID of the first IN-PDN on the source GW-U are deleted in the IN-PDN distribution information, and the information of the target GW-U is added. And the corresponding VLAN ID of the first IN-PDN on the target GW-U.
- the information of the first UE is deleted in the UE information that is connected to the source GW-U, and the information of the first UE is added to the UE information that is connected to the target GW-U.
- the IN-PDN controller updates the updated distribution of the first IN-PDN to the DNS according to the updated IN-PDN distribution information.
- the IN-PDN controller sends an IN-PDN forwarding tunnel addition and deletion request to the GW-C to the GW-C, and the request carries the tunnel identifier of the first IN-PDN queried by the IN-PDN controller, and is to be added or deleted by the tunnel.
- the tunnel identifier can be represented by VNI
- the IN-PDN identifier can be represented by a VLAN ID
- the GW-U information can be identified by the IP address of the GW-U.
- the IN-PDN controller can be pre-agreed with the GW-C.
- the agreement Flag equals 0 to delete the tunnel and update the forwarding rules and processing rules between the tunnels.
- the Flag indicates that the tunnel is established and the forwarding rules and processing rules between the tunnels are updated.
- Flag equal to 2 indicates that the forwarding rules and processing rules between the tunnels are updated.
- the Flag of the target GW-U is equal to 1
- the Flag of the source GW-U is equal to 0
- the Flag of the other GW-Us of the first IN-PDN is equal to 2.
- the GW-C sends an IN-PDN forwarding tunnel addition and deletion request across the GW-U to the IN-PDN controller. Ack.
- the GW-C receives the tunnel addition and deletion of the target GW-U and the Flag is equal to 1. Therefore, the tunnel establishment request is sent to the target GW-U, and the tunnel establishment request carries the tunnel identifier transmitted by the IN-PDN controller in step 13.
- the target GW-U sends a tunnel establishment response to the GW-C, and the tunnel establishment response carries the port information allocated by the target GW-U for the tunnel.
- the GW-C receives the tunnel addition and deletion of the source GW-U, and the flag is equal to 0. Therefore, the tunnel deletion request is sent to the source GW-U, and the tunnel deletion request carries the tunnel identifier transmitted by the IN-PDN controller in step 13.
- the Source GW-U sends a tunnel deletion response to the IN-PDN controller.
- the GW-C sends a notification of the addition and deletion of the forwarding tunnel to the IN-PDN controller.
- the IN-PDN controller sends a forwarding tunnel addition/deletion completion notification Ack to the GW-C.
- the GW-C sends a forwarding rule update notification to the source GW-U, and updates the forwarding rule and the processing rule on the source GW-U.
- the update of the forwarding rule and the processing rule is specifically performed by deleting the forwarding rule and the processing rule between the source GW-U and the UE related to the first IN-PDN on the other GW-U.
- the source GW-U sends a forwarding rule update Ack to the GW-C.
- the GW-C sends a forwarding rule update notification to other GW-Us, and updates forwarding rules and processing rules on other GW-Us.
- the forwarding rule and the processing rule are updated as follows: deleting the forwarding rules and processing rules between the other GW-Us and the UEs related to the first IN-PDN on the source GW-U . Adding a VLAN ID corresponding to the first IN-PDN on the other GW-U to the packet sent by the UE in the first IN-PDN of the other GW-U to the first UE, and adding the packet with the VLAN ID The VLAN ID is replaced with the VNI of the first IN-PDN, and then the replaced packet is forwarded to the tunnel port created in step 16 through the tunnel port created by the other GW-U for the first IN-PDN.
- the packet forwarded by the tunnel port created in step 16 from the first UE And receiving, by the tunnel port created by the other GW-U for the first IN-PDN, the packet forwarded by the tunnel port created in step 16 from the first UE, and receiving the packet
- the VNI in the packet is replaced with the corresponding VLAN ID of the first IN-PDN on the other GW-U, and then the VLAN ID in the replaced packet is deleted.
- the other GW-U sends a forwarding rule update Ack to the GW-C.
- the GW-C sends a forwarding rule update notification to the target GW-U to update the forwarding rule and the processing rule on the target GW-U.
- the update of the forwarding rule and the processing rule is specifically performed by adding the first IN to the message of the UE in the first IN-PDN sent by the first UE to the other GW-U.
- the corresponding VLAN ID of the PDN on the target GW-U, and the VLAN ID in the packet with the added VLAN ID is replaced with the VNI of the first IN-PDN, and then the replaced packet is created in step 16.
- the tunnel port is forwarded to the tunnel port created by the other GW-U for the first IN-PDN; and the tunnel port created in step 16 is sent to the tunnel port created by the other GW-U for the first IN-PDN.
- the packet of the first UE is replaced with the corresponding VLAN ID of the first IN-PDN on the target GW-U, and then the VLAN ID in the replaced packet is deleted.
- the target GW-U sends a forwarding rule update Ack to the GW-C.
- the existing UE handover process can then be performed.
- the second embodiment corresponds to the foregoing scenario 8, that is, the first UE is detached from the first GW-U, and before the first UE is detached, the first IN-PDN is distributed across the first GW-U and other GW-Us, and the first There are no other UEs in the first IN-PDN on one GW-U.
- the first UE is detached from the source GW-U.
- the IN-PDN controller queries the current IN-PDN distribution information, and finds that there is no other UE except the first UE in the first IN-PDN on the source GW-U, and the first IN-PDN still exists on other GW-Us. distributed. According to the query result, the IN-PDN controller updates the IN-PDN distribution information between the first IN-PDN and the GW-U, between the first IN-PDN and the first UE, and between the first UE and the GW-U. Mapping the relationship, and querying the tunnel identifier corresponding to the first IN-PDN to which the first UE belongs in the IN-PDN distribution information.
- the IN-PDN controller deletes the information of the source GW-U and the corresponding VLAN ID of the first IN-PDN on the source GW-U correspondingly in the IN-PDN distribution information. At the same time, the information of the first UE is deleted in the UE information connected to the source GW-U.
- the IN-PDN controller sends an IN-PDN forwarding tunnel addition and deletion request to the GW-C to the GW-C, and the request carries the tunnel identifier corresponding to the first IN-PDN queried by the IN-PDN controller, and is required to be added or deleted by the tunnel.
- the tunnel identifier can be represented by VNI
- the IN-PDN identifier can be represented by a VLAN ID
- the GW-U information can be represented by the IP address of the GW-U.
- the IN-PDN controller can be pre-agreed with the GW-C.
- the agreement Flag equals 0 to delete the tunnel and update the forwarding rules and processing rules between the tunnels.
- the Flag indicates that the tunnel is established and the forwarding rules and processing rules between the tunnels are updated.
- Flag equal to 2 indicates that the forwarding rules and processing rules between the tunnels are updated.
- the Flag of the source GW-U is equal to 0, and the Flag of the other GW-Us of the first IN-PDN is equal to 2.
- the GW-C sends an IN-PDN forwarding tunnel addition/deletion request Ack across the GW-U to the IN-PDN controller.
- the GW-C receives the tunnel addition and deletion of the source GW-U, and the flag is equal to 0. Therefore, the GW-C sends a tunnel deletion request to the source GW-U.
- the tunnel deletion request carries the tunnel identifier transmitted by the IN-PDN allocator in step 2.
- the source GW-U sends a tunnel deletion response to the GW-C.
- the GW-C sends a notification of the addition and deletion of the forwarding tunnel to the IN-PDN controller.
- the IN-PDN controller sends a forwarding tunnel addition and deletion completion notification Ack to the GW-C.
- the GW-C sends a forwarding rule update notification to other GW-Us to update the forwarding rules and processing rules on other GW-Us.
- the update of the forwarding rule and the processing rule is specifically performed by deleting the forwarding rule and the processing rule between the other GW-U and the UE related to the first IN-PDN on the source GW-U.
- the other GW-U sends a forwarding rule update Ack to the GW-C.
- the GW-C sends a forwarding rule update notification to the source GW-U, and updates the forwarding rule and the processing rule on the source GW-U.
- the update of the forwarding rule and the processing rule is specifically performed by deleting the forwarding rule and the processing rule between the source GW-U and the UE related to the first IN-PDN on the other GW-U.
- the source GW-U sends a forwarding rule update Ack to the GW-C.
- the present application provides a controller 800 for implementing the functions of the controller in the foregoing network management method.
- the controller 800 includes a determining unit 801, and a determining unit. 802 and processing unit 803.
- the determining unit 801 is configured to determine, according to the IN-PDN distribution information, a first IN-PDN and a first access that the first UE accesses before being detached from the first base station, when the first UE is detached from the first base station.
- a user plane gateway the IN-PDN distribution information is used to indicate a mapping relationship between the IN-PDN, the GW-U, and the UE.
- the determining unit 802 is configured to determine, according to the IN-PDN distribution information, whether a second UE and a second GW-U are present, and a mapping relationship exists between the second UE and the first IN-PDN, and the There is also a mapping relationship between the second UE and the first GW-U, and a mapping relationship exists between the second GW-U and the first IN-PDN.
- the processing unit 803 is configured to determine, according to the determining result of the determining unit 802, whether the second UE and the second GW-U are present, whether to update between the first IN-PDN and the forwarding tunnel. a mapping relationship, a mapping relationship between the first IN-PDN and the first UE, and a mapping relationship between the first IN-PDN and the GW-U.
- the first UE is detached from the first base station, and specifically includes the following scenarios: the first UE is handed over from the first base station to the second base station, or the first UE is detached from the first base station.
- the IN-PDN distribution information is used to indicate a mapping relationship between the IN-PDN and the user plane gateway, a mapping relationship between the user plane gateway and the UE, and a mapping relationship between the IN-PDN and the UE.
- the determining unit 802 determines, according to the IN-PDN distribution information, whether the first Before the second UE and the second GW-U, the processing unit 803 is further configured to: delete the mapping relationship between the first UE and the first GW-U in the IN-PDN distribution information.
- the controller 800 further includes a network interface.
- the processing unit 803 is specifically configured to: delete, in the IN-PDN distribution information, a mapping relationship between the first GW-U and the first IN-PDN, the first GW-U, and the a mapping relationship between the first UE and a mapping relationship between the first UE and the first IN-PDN; acquiring a tunnel identifier corresponding to the first IN-PDN, and using the network interface to the GW-
- the C sends an indication message, where the indication message is used to indicate that the forwarding tunnel that uses the tunnel identifier corresponding to the first IN-PDN as the identifier and the first GW-U and the second GW-U as the endpoint is deleted.
- the processing is performed.
- the unit 803 is further configured to: determine a third GW-U that is accessed by the first UE after being switched from the first base station to the second base station; and determine, according to the IN-PDN distribution information, the first Whether the three GW-Us have a mapping relationship with the first IN-PDN.
- mapping relationship between the third GW-U and the first IN-PDN creating the first IN-PDN on the third GW-U, and distributing the IN-PDN Adding a mapping relationship between the third GW-U and the first IN-PDN, and adding a mapping relationship between the third GW-U and the first UE; if the third GW-U is A mapping relationship exists between the first IN-PDNs, and a mapping relationship between the third GW-U and the first UE is added to the IN-PDN distribution information.
- the processing unit 803 is specifically configured to: delete the first GW-U and the first IN in the IN-PDN distribution information - mapping between PDNs a mapping relationship between the first UE and the first IN-PDN; acquiring a tunnel identifier corresponding to the first IN-PDN, and sending an indication message to the GW-C by using the network interface; And the message is used to indicate that the tunnel identifier corresponding to the first IN-PDN is used as the identifier, the forwarding tunnel with the first GW-U and the second GW-U as the endpoint, and the indication is deleted.
- the processing unit 803 is specifically configured to: acquire a tunnel identifier corresponding to the first IN-PDN, and send an indication to the GW-C by using the network interface.
- the processing unit 803 is specifically configured to: acquire a tunnel identifier corresponding to the first IN-PDN, and send the GW to the GW through the network interface.
- the C sends an indication message, where the indication message is used to indicate that a forwarding tunnel that uses the tunnel identifier corresponding to the first IN-PDN as the identifier and the first GW-U and the third GW-U as the endpoint is created. And indicating to create between the first GW-U and the third GW-U between the UEs associated with the first IN-PDN Process rules and forwarding rules.
- the processing unit 803 before the processing unit 803 sends the indication message to the GW-C by using the network interface, the processing unit 803 is further configured to: determine that the first IN-PDN is on the second GW-U Corresponding a second IN-PDN identifier and a second tunnel port, and determining a third IN-PDN identifier and a third tunnel port corresponding to the first IN-PDN on the third GW-U.
- the processing rule and forwarding rule between the UE associated with the first IN-PDN between the second GW-U and the third GW-U is: in the second GW-U Adding the second IN-PDN identifier to the packet sent by the UE in the first IN-PDN to the first UE, and adding the number in the packet of the second IN-PDN identifier
- the second IN-PDN identifier is replaced with the tunnel identifier corresponding to the first IN-PDN, and the replaced packet is forwarded to the third tunnel port by using the second tunnel port; and, through the second tunnel
- the port receives the packet from the third tunnel port, and replaces the tunnel identifier corresponding to the first IN-PDN in the packet received by the second tunnel port with the second IN-PDN identifier, and
- the second IN-PDN identifier in the replaced message is deleted.
- the third IN-PDN identifier in the packet identified by the PDN is replaced with the tunnel identifier corresponding to the first IN-PDN, and the replaced packet is forwarded to the second tunnel through the third tunnel port.
- the processing unit 803 before the processing unit 803 sends the indication message to the GW-C by using the network interface, the processing unit 803 is further configured to: determine that the first IN-PDN is on the first GW-U And corresponding to the first IN-PDN identifier and the first tunnel port, and determining a third IN-PDN identifier and a third tunnel port corresponding to the first IN-PDN on the third GW-U.
- the processing rule and the forwarding rule between the UE associated with the first IN-PDN between the first GW-U and the third GW-U are: in the first GW-U Adding the first IN-PDN identifier to a packet sent by the UE in the first IN-PDN to the first UE, where And replacing the first IN-PDN identifier in the packet with the first IN-PDN identifier with the tunnel identifier corresponding to the first IN-PDN, and passing the replaced packet through the first Forwarding the tunnel port to the third tunnel port; and receiving, by the first tunnel port, a packet from the third tunnel port, the first one of the packets received by the first tunnel port
- the tunnel identifier corresponding to the IN-PDN is replaced with the first IN-PDN identifier, and the first IN-PDN identifier in the replaced packet is deleted.
- the third IN-PDN identifier in the packet identified by the PDN is replaced with the tunnel identifier corresponding to the first IN-PDN, and the replaced packet is forwarded to the first tunnel by using the third tunnel port.
- the tunnel identifier corresponding to the first IN-PDN may be represented by a VNI.
- the first tunnel port, the second tunnel port, and the third tunnel port are represented by an IP address of a VTEP.
- the first IN-PDN identifier, the second IN-PDN identifier, and the third IN-PDN identifier are represented by a VLAN ID.
- the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
- the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
- the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
- the hardware of the entity corresponding to the determining unit 801, the determining unit 802, and the processing unit 803 may be a processor, such as the processor 901 of FIG.
- the controller 800 may correspond to a controller in a network management method according to an embodiment of the present invention, and the above and other operations and/or functions of respective units in the controller 800 In order to implement the corresponding processes of the respective methods in FIG. 3 to FIG. 7 , for brevity, details are not described herein again.
- the present application further provides a controller 900.
- the controller 900 includes a processor 901 and a memory 902.
- the processor 801 and the memory 902 pass through a bus 903. Connected to each other.
- the memory 902 is configured to store executable instructions of the processor 901.
- the processor 901 is configured to: when the first UE is detached from the first base station, determine, according to the IN-PDN distribution information, the first IN-PDN and the first UE that is accessed before being detached from the first base station a first user plane gateway; the IN-PDN distribution information is used to indicate a mapping relationship between the IN-PDN, the user plane gateway, and the UE. Determining whether there is a second UE and a second GW-U according to the IN-PDN distribution information, a mapping relationship between the second UE and the first IN-PDN, and the second UE and the first There is also a mapping relationship between the GW and the GW, and a mapping relationship exists between the second GW-U and the first IN-PDN.
- the technical solution provided by the present application implements the dynamic scaling of the IN-PDN, and ensures the continuity of services in the local networking of the UE when the UE is migrated or detached, and is not reclaimed in time.
- the IN-PDN resources used avoid the waste of IN-PDN resources.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
一种网络管理方法和控制器,在UE发生迁移或去附着的场景下实现网内分组数据网IN-PDN的动态伸缩,并在UE发生迁移或去附着时,仍能保证UE的本地组网内的业务的连续性,并及时回收不再使用的IN-PDN资源,避免了IN-PDN资源的浪费。
Description
本发明涉及通信技术领域,尤其涉及一种网络管理方法和控制器。
如图1所示,在第三代移动通信技术(3rd Generation,简称:3G)或第四代移动通信技术(4th Generation,简称:4G)的网络架构中,用户设备(User Equipment,简称:UE)通过核心网及边界网关接入分组数据网(Packet Data Network,简称:PDN)。在3G/4G的网络架构中,PDN在互联网(internetwork,简称:internet)中,核心网负责把数据发送到边界网关,由边界网关将数据发送给internet中的PDN。
由于internet中数据的传输不受核心网的控制,这会导致网络的传输时延以及可靠性没有保障,以及导致移动网络的压力较大。
发明内容
本申请提供一种网络管理方法和控制器,用以使得处于同一个本地网络内的UE之间的数据不必经过核心网以及internet,有效减少网络传输时延和减轻移动网络压力。
本申请第一方面,提供了一种网络管理方法,该方法包括:
当控制器接收到控制面网关的通知从而确定第一UE从第一基站脱离时,控制器根据预先存储的IN-PDN分布信息确定所述第一UE在从所述第一基站脱离之前所接入的第一IN-PDN和第一用户面网关;所述IN-PDN分布信息用于指示IN-PDN、用户面网关和UE之间的映射关系;
所述控制器根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关,所述第二UE与所述第一IN-PDN之间存在映射关系且所述第二UE与所述第一用户面网关之间也存在映射关系,所述第二用户面网关与所述第一
IN-PDN之间存在映射关系;
所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系。
IN-PDN为本申请为满足本地组网需求而提出的一种本地的PDN,IN-PDN内的数据不需要经过汇聚核心层以及internet,可以直接在核心网中进行本地环回,从而减轻移动网络压力,减少传输时延。上述实现方式主要介绍了当接入第一IN-PDN的第一UE从第一基站脱离时,需要根据是否存在第二UE和第二用户面网关,从而确定是否对IN-PDN进行伸缩。其中,控制器判断是否存在所述第二UE,即是判断当所述第一UE完成切换或去附着之后,所述第一GW-U上的第一IN-PDN内是否仍有UE。控制器判断是否存在所述第二GW-U,即是判断所述第一IN-PDN是否跨所述第一GW-U和其它GW-U分布。
在一个可能的设计中,所述第一UE从第一基站脱离可以包括以下两种场景:
所述第一UE从第一基站切换到第二基站;或
所述第一UE从第一基站去附着。
在一个可能的设计中,所述IN-PDN分布信息可以用于指示IN-PDN与用户面网关之间的映射关系、用户面网关与UE之间的映射关系以及IN-PDN与UE之间的映射关系。
在一个可能的设计中,在所述控制器根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关之前,所述方法还包括:
所述控制器在所述IN-PDN分布信息中删除所述第一UE与所述第一用户面网关之间的映射关系。
在一个可能的设计中,当第一UE从所述第一基站去附着,所述判断结果为所述IN-PDN分布信息中存在所述第二用户面网关但不存在所述第二UE时;
所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结
果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系,包括:
所述控制器在所述IN-PDN分布信息中删除所述第一用户面网关与所述第一IN-PDN之间的映射关系、所述第一用户面网关与所述第一UE之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系;
所述控制器获取所述第一IN-PDN对应的隧道标识,并向控制面网关发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第二用户面网关为端点的转发隧道,以及用于指示删除所述第一用户面网关和所述第二用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
在上述实现方式中,由于第一GW-U上的第一IN-PDN内不再有UE,因此分布在其它GW-U的第一IN-PDN内的UE不会与第一GW-U上的UE有业务上的往来。通过IN-PDN控制器与控制面网关的信息交互,由控制面网关为第一IN-PDN删除了跨第一用户面网关和其它用户面网关的转发隧道,实现了IN-PDN的动态收缩。
此外,对IN-PDN进行收缩后,为避免资源浪费,还可以对第一GW-U上的第一IN-PDN进行资源回收。回收的资源包括第一IN-PDN在第一GW-U上对应的第一IN-PDN标识和隧道端口。回收之后的第一IN-PDN标识和隧道端口在其它IN-PDN创建时可以再利用,从而可以避免出现IN-PDN标识和隧道端口不够用的情况。
在一个可能的设计中,当第一UE从第一基站切换到第二基站时;
在所述控制器根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关之前,所述方法还包括:
所述控制器确定所述第一UE在从所述第一基站切换到所述第二基站之后所接入的第三用户面网关;
所述控制器根据所述IN-PDN分布信息判断所述第三用户面网关是否与所
述第一IN-PDN存在映射关系;
若所述第三用户面网关与所述第一IN-PDN之间不存在映射关系,则所述控制器在所述第三用户面网关上创建所述第一IN-PDN,并在所述IN-PDN分布信息中添加所述第三用户面网关与所述第一IN-PDN的映射关系,以及添加所述第三用户面网关与所述第一UE的映射关系;
若所述第三用户面网关与所述第一IN-PDN之间存在映射关系,则所述控制器在所述IN-PDN分布信息中添加所述第三用户面网关与所述第一UE的映射关系。
在一个可能的设计中,当所述判断结果为所述IN-PDN分布信息中存在所述第二用户面网关但不存在所述第二UE,且所述第三用户面网关与所述第一IN-PDN之间不存在映射关系时;
所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系,包括:
所述控制器在所述IN-PDN分布信息中删除所述第一用户面网关与所述第一IN-PDN之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系;
所述控制器获取所述第一IN-PDN对应的隧道标识,并向控制面网关发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第二用户面网关为端点的转发隧道,以及用于指示删除所述第一用户面网关和所述第二用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二用户面网关和所述第三用户面网关为断点的转发隧道,以及用于指示创建所述第二用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
在上述实现方式中,由于第一GW-U上的第一IN-PDN内不再有UE,为避
免资源的浪费,可以对第一GW-U上的第一IN-PDN进行资源回收,因此对于第一GW-U而言,第一IN-PDN发生了收缩。又由于第三GW-U上尚未创建第一IN-PDN,所述控制器需要在所述第三GW-U上创建所述第一IN-PDN,因此对于第三GW-U而言,第一IN-PDN发生了扩展。通过IN-PDN控制器与控制面网关的信息交互,由控制面网关为第一IN-PDN删除了跨第一用户面网关和其它用户面网关的转发隧道,并为第一IN-PDN创建了跨第三用户面网关和其它用户面网关的转发隧道,实现了IN-PDN的动态伸缩。
在一个可能的设计中,当所述判断结果为所述IN-PDN分布信息中存在所述第二用户面网关和所述第二UE,且所述第三用户面网关与所述第一IN-PDN之间不存在映射关系时;
所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系,包括:
所述控制器获取所述第一IN-PDN对应的隧道标识,并向控制面网关发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第三用户面网关为端点的转发隧道,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二用户面网关和所述第三用户面网关为断点的转发隧道,以及用于指示创建所述第一用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及用于指示创建所述第二用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
在上述实现方式中,由于第一GW-U上的第一IN-PDN仍被其它UE所使用,因此无需对第一GW-U上的第一IN-PDN进行资源回收。而由于第三GW-U上尚未创建第一IN-PDN,因此所述控制器需要在所述第三GW-U上创建所述第一IN-PDN。通过IN-PDN控制器与控制面网关的信息交互,由控制面网关为第一IN-PDN创建了跨第三用户面网关和其它用户面网关的转发隧道,实现了
IN-PDN的动态扩展。
在一个可能的设计中,当所述判断结果为所述IN-PDN分布信息中不存在所述第二用户面网关但存在所述第二UE,且所述第三用户面网关与所述第一IN-PDN之间不存在映射关系时;
所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系,包括:
所述控制器获取所述第一IN-PDN对应的隧道标识,并向控制面网关发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第三用户面网关为端点的转发隧道,以及用于指示创建所述第一用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
在上述实现方式中,通过IN-PDN控制器与控制面网关的信息交互,由控制面网关为第一IN-PDN创建了跨第三用户面网关和其它用户面网关的转发隧道,实现了IN-PDN的动态扩展。
在一个可能的设计中,在所述控制器向控制面网关发送指示消息之前,所述方法还包括:
所述控制器确定所述第一IN-PDN在所述第二用户面网关上对应的第二IN-PDN标识和第二隧道端口,以及确定所述第一IN-PDN在所述第三用户面网关上对应的第三IN-PDN标识和第三隧道端口;
所述第二用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则为:
在由所述第二用户面网关的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第二IN-PDN标识,将增加了所述第二IN-PDN标识的报文中的所述第二IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第二隧道端口转发到所述第三隧道端口;以及,通过所述第
二隧道端口接收来自所述第三隧道端口的报文,将所述第二隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第二IN-PDN标识,并删除替换后的报文中的所述第二IN-PDN标识;
在由所述第一UE发送给所述第二用户面网关的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第二隧道端口;以及,通过所述第三隧道端口接收来自所述第二隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
上述实现方式定义了所述第二GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,从而保证了UE的本地组网内的业务的连续性。
在一个可能的设计中,在所述控制器向控制面网关发送指示消息之前,所述方法还包括:
所述控制器确定所述第一IN-PDN在所述第一用户面网关上对应的第一IN-PDN标识和第一隧道端口,以及确定所述第一IN-PDN在所述第三用户面网关上对应的第三IN-PDN标识和第三隧道端口;
所述第一用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则为:
在由所述第一用户面网关的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第一IN-PDN标识,将增加了所述第一IN-PDN标识的报文中的所述第一IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第一隧道端口转发到所述第三隧道端口;以及,通过所述第一隧道端口接收来自所述第三隧道端口的报文,将所述第一隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第一IN-PDN标识,并删除替换后的报文中的所述第一IN-PDN标识;
在由所述第一UE发送给所述第一用户面网关的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第一隧道端口;以及,通过所述第三隧道端口接收来自所述第一隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
上述实现方式定义了所述第一GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,从而保证了UE的本地组网内的业务的连续性。
在一个可能的设计中,若所述第一IN-PDN通过虚拟局域网VLAN实现;则
所述第一IN-PDN对应的隧道标识通过虚拟扩展局域网网络标识VNI表示;
所述第一隧道端口、所述第二隧道端口和所述第三隧道端口通过虚拟扩展局域网隧道端点VTEP的网际协议IP地址表示;
所述第一IN-PDN标识、所述第二IN-PDN标识和所述第三IN-PDN标识通过VLAN标识表示。
本申请第二方面,提供了一种控制器,所述控制器具有实现上述方法的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块或单元。
一种可能的实现方式中,所述控制器包括确定单元、判断单元和处理单元:
所述确定单元,用于当第一UE从第一基站脱离时,根据IN-PDN分布信息,确定所述第一UE在从第一基站脱离之前所接入的第一IN-PDN和第一用户面网关;所述IN-PDN分布信息用于指示IN-PDN、用户面网关和UE之间的映射关系;
所述判断单元,用于根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关,所述第二UE与所述第一IN-PDN之间存在映射关系且所述第二UE与所述第一用户面网关之间也存在映射关系,所述第二用户面网关与所述第一IN-PDN之间存在映射关系;
所述处理单元,用于根据所述判断单元关于是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系。
另一种可能的实现方式中,所述控制器包括处理器和用于存储所述处理器可执行指令的存储器,所述存储器和所述处理器之间通过总线系统相互连接;所述处理器用于执行以下操作:
当第一UE从第一基站脱离时,根据IN-PDN分布信息,确定所述第一UE在从第一基站脱离之前所接入的第一IN-PDN和第一用户面网关;所述IN-PDN分布信息用于指示IN-PDN、用户面网关和UE之间的映射关系;
根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关,所述第二UE与所述第一IN-PDN之间存在映射关系且所述第二UE与所述第一用户面网关之间也存在映射关系,所述第二用户面网关与所述第一IN-PDN之间存在映射关系;
根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系。
本申请提供的技术方案,实现了IN-PDN的动态伸缩,在UE发生迁移或去附着时,仍能保证UE的本地组网内的业务的连续性,并及时回收不再使用的IN-PDN资源,避免了IN-PDN资源的浪费。
图1为现有技术下一种传统的PDN的网络示意图;
图2为本申请实施例提供的一种IN-PDN的网络示意图;
图3为本申请实施例提供的一种IN-PDN伸缩的场景示意图;
图4为本申请实施例提供的一种网络管理方法应用的系统的架构示意图;
图5为本申请实施例提供的一种网络管理方法的流程图;
图6为本申请实施例提供的一种UE切换场景下各网元之间的信令交互示意图;
图7为本申请实施例提供的一种UE去附着场景下各网元之间的信令交互示意图;
图8为本申请实施例提供的一种控制器的结构示意图;
图9为本申请实施例提供的另一种控制器的结构示意图。
以下,对本申请中的部分用语进行解释说明。
网内分组数据网(In-Network Packet Data Network,简称:IN-PDN),是本申请为满足本地组网的需求而提出的一种本地的PDN。如图2所示为IN-PDN的示意图,一个IN-PDN代表一个本地网络,UE可以通过网内接入点名称(In-Network Access Point Name,简称:IN-APN)来标识该UE想要访问的IN-PDN。IN-PDN部署在移动网络边缘,连接边缘/网内应用,同时为UE之间的本地互联提供连接。这样,IN-PDN内的数据不需要经过汇聚核心层以及internet,可以直接在核心网中进行本地环回,从而减轻了移动网络压力,减少了传输时延。IN-PDN与传统的PDN、局域网的区别在于,IN-PDN具有可动态创建,可伸缩(或可迁移)以及可与多个用户面网关(GateWay of User Plane,简称:GW-U)关联的特性。为实现上述IN-PDN的特性,本申请引入了新的网元或者逻辑处理单元IN-PDN控制器(Controller)。
IN-PDN的“动态创建”,主要包括以下过程:IN-PDN控制器根据UE的位置信息与业务信息为UE选择一个GW-U,然后指示控制面网关(Gateway of Controller Plane,简称:GW-C)将UE发送的报文与IN-PDN的对应关系、
相应的转发规则和处理规则下发给该GW-U,从而完成IN-PDN的动态创建。
其中,UE发送的报文与IN-PDN的对应关系可以用UE发送的报文的特征点与IN-PDN的特征点联合表示,UE发送的报文的特征点可以是隧道端点标识(Tunnel Endpoint Identifier,筒称:TEID)、UE的网际协议(Internet Protocol,简称:IP)地址或者目的IP地址,IN-PDN的特征点可以是虚拟局域网标识(Virtual Local Area Network Identity,简称:VLAN ID)。
处理规则是指GW-U对报文进行封装和解封装的动作,包括在报文头中添加/删除IN-PDN标识,在报文头中添加/删除隧道标识等动作。转发规则包括将封装后的报文从哪个端口转发,将解封装后的报文转发给相应的UE等动作。
IN-PDN的“可伸缩”,是指IN-PDN可以随着UE的移动而动态调整该IN-PDN的覆盖范围。如图3所示,在t1时刻,UE 1和UE 2均处于GW-U 1的IN-PDN 1内,在t2时刻,由于UE 1移动到了GW-U 2,导致UE 1和UE 2分布在不同的GW-U下,为了保证UE 1本地组网内业务的连续性,从而需要将IN-PDN 1扩展到GW-U 2。从t1时刻到t2时刻,即为IN-PDN的扩展场景。在t3时刻,随着UE 2的移动,UE 1和UE 2又分布在相同的GW-U下,为了回收IN-PDN 1的相关资源从而需要将IN-PDN 1收缩到GW-U 2上。从t2时刻到t3时刻,即为IN-PDN的收缩场景。
由于IN-PDN可扩展到多个GW-U,因此IN-PDN可同时与多个GW-U关联。例如,在图3的t2时刻,IN-PDN 1同时关联了GW-U 1和GW-U 2。
“IN-PDN分布信息”,保存在IN-PDN控制器上,用于指示IN-PDN、GW-U和UE之间的映射关系,可以包括IN-PDN与GW-U之间的映射关系、GW-U与UE之间的映射关系以及IN-PDN与UE之间的映射关系。当UE附着到一个GW-U上时,或是从一个GW-U切换到另一个GW-U时,或是从一个GW-U去附着时,IN-PDN控制器会根据实际情况实时调整IN-PDN分布信息。例如,在图3中的t1时刻,IN-PDN分布信息内保存有IN-PDN 1与GW-U 1之间的映射关系、GW-U 1分别与UE 1和UE 2之间的映射关系以及IN-PDN
1分别与UE 1和UE 2之间的映射关系。
应当理解,在本申请使用的术语是仅仅出于描述特定实施例的目的,而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式,除非上下文清楚地表示其他含义。还应当理解,本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
另外,尽管在本申请可能采用术语第一、第二、第三等来描述各种信息,但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如,在不脱离本申请范围的情况下,第一信息也可以被称为第二信息,类似地,第二信息也可以被称为第一信息。取决于语境,如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
为了缓减少网络传输时延和减轻移动网络压力,由此出现了本地组网的需求。本地组网是指某一范围内的UE组成一个离用户较近的本地网络,UE之间的数据转发直接在本地网络内进行,而不必经过核心网以及internet。目前,越来越多的应用场景,如智能办公、体育比赛/演唱会现场实时高清视频/照片分享、灾后应急通讯和自动驾驶等场景,均要求第五代移动通信技术(fifth-generation,简称:5G)网络具备本地组网能力。
为满足本地组网的需求,本申请提出了一种新的网络——IN-PDN,以及提出了一种网络管理方法和控制器,用以实现IN-PDN的动态伸缩,在IN-PDN扩展场景下如何保持本地组网内的业务连续性,以及在IN-PDN收缩场景下如何及时回收IN-PDN的相关资源。
下面结合说明书附图和各实施例对本申请技术方案进行说明。
本申请提供的网络管理方法,可应用于图4所示的系统,该系统包括MME 401,IN-PDN控制器402,GW-C 403、GW-U 404和基站405。网元之间的连线表示连线两端的网元之间存在接口。
本系统在现有架构的基础上引入了新的网元或逻辑处理单元IN-PDN控制器402,IN-PDN控制器402与GW-C 403之间存在接口,IN-PDN控制器
402通过向GW-C 403下发指示消息,由GW-C 403根据指示消息的内容对GW-U 404进行控制。
这种架构的好处在于,一是可以直接沿用现有的系统架构和实现方法,减少改动系统架构带来的成本;二是如果增加IN-PDN控制器402对GW-U 404的控制,那么GW-U 404会有两个控制网元,GW-C 403和IN-PDN控制器402之间的控制信息需要同步,会造成额外的开销。
在本申请的另一实施例中,IN-PDN控制器402也可以集成在现有的网元中,如集成在GW-C 403中,从而可以由GW-C 403执行IN-PDN控制器402的功能。
下面分别对本系统所涉及的各网元的功能进行介绍。
MME 401,用于接入控制,移动性管理,会话管理,用户鉴权和秘钥管理,非接入层(Non-access stratum,NAS)信令的加密和完整性保护,GW-C 403选择,切换过程中的MME选择,信令面合法监听,以及跟踪区标识(Tracking Area Identity,简称:TAI)列表(List)的分配和管理。
IN-PDN控制器402,用于保存IN-PDN分布信息,下发IN-PDN配置信息完成IN-PDN的创建,指导GW-C 403重选GW-U 404,其中,IN-PDN配置信息中携带有IN-PDN控制器402为待创建的IN-PDN分配的IN-PDN标识。在IN-PDN扩展场景中,IN-PDN控制器402还用于为IN-PDN分配转发隧道标识,并指示GW-C 403在哪些GW-U 404之间创建转发隧道以及更新处理规则和转发规则;在IN-PDN收缩场景中,IN-PDN控制器402还用于指示GW-C 403在哪些GW-U 404之间删除转发隧道以及更新处理规则和转发规则。本申请中,有时会使用到“控制器”作为IN-PDN控制器402的简称。
GW-C 403,用于向IN-PDN控制器402发送UE移动事件通知,包括UE切换事件和UE去附着事件;以及用于根据IN-PDN控制器402的指示在GW-U 404之间创建或删除转发隧道并更新GW-U 404上的处理规则和转发规则。
GW-U 404,用于根据GW-C 403下发的处理规则和转发规则对报文进行封装、解封装和转发。
基站405,用于无线资源管理,头压缩和加密,MME401选择,上下行服务质量(简称:QoS)执行,寻呼消息的调度与传输,系统广播消息的调度与传输,准入控制等。本申请中,一个基站405可以对应多个GW-U 404。
基站405的无线通信制式可包括但不限于:全球移动通信系统(Global System of Mobile communication,简称:GSM)、码分多址(Code Division Multiple Access,简称:CDMA)IS-95、码分多址(Code Division Multiple Access,简称:CDMA)2000、时分同步码分多址(Time Division-Synchronous Code Division Multiple Access,简称:TD-SCDMA)、宽带码分多址(Wideband Code Division Multiple Access,简称:WCDMA)、时分双工-长期演进(Time Division Duplexing-Long Term Evolution,简称:TDD LTE)、频分双工-长期演进(Frequency Division Duplexing-Long Term Evolution,简称:FDD LTE)、长期演进-增强(Long Term Evolution-Advanced,简称:LTE-advanced)、个人手持电话系统(Personal Handy-phone System,简称:PHS)、802.11系列协议规定的无线保真(Wireless Fidelity,简称:WiFi)、全球微波互联接入(Worldwide Interoperability for Microwave Access,简称:WiMAX),以及未来演进的各种无线通信系统等。
基于上述图4提供的系统,本申请实施例还提供了一种网络管理方法,如图5所示,该方法包括以下步骤:
步骤501:当第一UE从第一基站脱离时,控制器根据预先存储的IN-PDN分布信息,确定所述第一UE在从第一基站脱离之前所接入的第一IN-PDN和第一GW-U。
其中,第一UE从第一基站脱离,可以包括以下两种场景:
场景一:第一UE从第一基站切换到第二基站,从而控制器确定的是根第一UE在从所述第一基站切换到所述第二基站之前所接入的第一IN-PDN和第一GW-U。
场景二:第一UE从第一基站去附着,从而控制器确定的是第一UE在从所述第一基站去附着之前所接入的第一IN-PDN和第一GW-U。
实际应用中,所述第一UE的移动事件可由GW-C通知给控制器。
可选的,在步骤502之前,所述控制器还可以在所述IN-PDN分布信息中删除所述第一UE与所述第一GW-U之间的映射关系。
步骤502:所述控制器根据所述IN-PDN分布信息判断是否存在第二UE和第二GW-U,所述第二UE与所述第一IN-PDN之间存在映射关系且所述第二UE与所述第一GW-U之间也存在映射关系,所述第二GW-U与所述第一IN-PDN之间存在映射关系。
本申请中的第二GW-U泛指与第一IN-PDN存在映射关系的除所述第一GW-U之外的其它GW-U中的任一个。
可选的,在第一UE从第一基站切换到第二基站的场景下,在步骤502之前,所述控制器还需要确定所述第一UE在从所述第一基站切换到所述第二基站之后所接入的第三GW-U。然后,所述控制器根据所述IN-PDN分布信息判断所述第三GW-U是否与所述第一IN-PDN存在映射关系。
若所述第三GW-U与所述第一IN-PDN之间不存在映射关系,则所述控制器在所述第三GW-U上创建所述第一IN-PDN,具体创建IN-PDN的过程可参见上文描述,此处不再赘述。以及所述控制器还要在所述IN-PDN分布信息中添加所述第三GW-U与所述第一IN-PDN的映射关系,以及添加所述第三GW-U与所述第一UE的映射关系。
若所述第三GW-U与所述第一IN-PDN之间存在映射关系,则所述控制器只在所述IN-PDN分布信息中添加所述第三GW-U与所述第一UE的映射关系。
步骤503:所述控制器根据是否存在所述第二UE和所述第二GW-U的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与GW-U之间的映射关系。
需要说明的是,所述第一UE和所述第二UE是不同的UE,所述第一GW-U和所述第二GW-U是不同的GW-U,所述第二GW-U和所述第三GW-U
可能是相同的GW-U也可能是不同的GW-U。
控制器判断是否存在所述第二UE,即是判断当所述第一UE完成切换或去附着之后,所述第一GW-U上的第一IN-PDN内是否仍有UE。控制器判断是否存在所述第二GW-U,即是判断所述第一IN-PDN是否跨所述第一GW-U和其它GW-U分布。
本申请中,在切换和去附着这两种场景下,根据是否存在所述第二UE和所述第二GW-U的判断结果,可细分为如表1至表3所示的10种场景,这10种场景下需要对所述第一IN-PDN进行的操作也如表1至表3所示。
表1切换场景下,所述第一UE待接入的第三GW-U与所述第一IN-PDN之间存在映射关系
表2切换场景下,所述第一UE待接入的第三GW-U与所述第一IN-PDN之间不存在映射关系
表3去附着场景
下面基于上述10种场景,说明控制器分别在何种场景下需要对IN-PDN进行伸缩,以及控制器如何实现IN-PDN的伸缩。
场景一:第一UE迁移到第二基站的第三GW-U上,第三GW-U已建立所述第一UE所需要的第一IN-PDN,第一UE迁移之前,第一IN-PDN跨第一GW-U和其它GW-U分布,第一UE迁移之后,第一GW-U上的第一IN-PDN内仍有其它UE。
在场景一下,由于第一GW-U上的第一IN-PDN仍被其它UE所使用,因此无需对第一GW-U上的第一IN-PDN进行资源回收。并且,由于第一IN-PDN已经覆盖了第一GW-U和第三GW-U,因此第一UE和其切换之前的第一GW-U上的第一IN-PDN内的其它UE可以正常通信。因此,在场景一下,控制器只需在IN-PDN分布信息中添加第三GW-U与第一UE的映射关系,无需对第一IN-PDN进行收缩或扩展。
场景二:第一UE迁移到第二基站的第三GW-U上,第三GW-U已建立所述第一UE所需要的第一IN-PDN,第一UE迁移之前,第一IN-PDN跨第一GW-U和其它GW-U分布,第一UE迁移之后,第一GW-U上的第一IN-PDN内没有其它UE。
在场景二下,由于第一GW-U上的第一IN-PDN内不再有UE,因此分布在其它GW-U的第一IN-PDN内的UE不会与第一GW-U上的UE有业务上
的往来。为避免资源的浪费,可以对第一GW-U上的第一IN-PDN进行资源回收,并对第一IN-PDN进行收缩。
回收的资源包括第一IN-PDN在第一GW-U上对应的第一IN-PDN标识和隧道端口。回收之后的第一IN-PDN标识和隧道端口在其它IN-PDN创建时可以再利用,从而可以避免出现IN-PDN标识和隧道端口不够用的情况。
在场景二下,控制器对第一IN-PDN进行收缩的具体过程如下:所述控制器会在IN-PDN分布信息中添加第三GW-U与第一UE的映射关系,并在IN-PDN分布信息中删除所述第一GW-U与所述第一IN-PDN之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系。以及,所述控制器会获取所述第一IN-PDN对应的隧道标识,并向GW-C发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一GW-U和所述第二GW-U为端点的转发隧道,以及用于指示删除所述第一GW-U和所述第二GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
例如,假设UE1接入GW-U1上的IN-PDN1内,IN-PDN1在GW-U1、GW-U2和GW-U3上均有分布,如果UE 1从GW-U1迁移到GW-U2后,GW-U1上的第一IN-PDN内没有其它UE,GW-U2的IN-PDN1内存在UE2,GW-U3的IN-PDN1内存在UE3和UE4,则可以删除GW-U1和GW-U2之间与IN-PDN1关联的UE1和UE2间的处理规则和转发规则,以及可以删除GW-U1和GW-U3之间与IN-PDN1关联的UE1分别于UE3和UE4间的处理规则和转发规则。
需要说明的是,每个IN-PDN都有唯一的隧道标识。IN-PDN的隧道标识以及转发隧道的端点信息均保存在IN-PDN分布信息中。
场景三:第一UE迁移到第二基站的第三GW-U上,第三GW-U尚未建立所述第一UE所需要的第一IN-PDN,第一UE迁移之前,第一IN-PDN跨第一GW-U和其它GW-U分布,第一UE迁移之后,第一GW-U上的第一IN-PDN内仍有其它UE。
在场景三下,由于第一GW-U上的第一IN-PDN仍被其它UE所使用,因此无需对第一GW-U上的第一IN-PDN进行资源回收。而由于第三GW-U上尚未创建第一IN-PDN,因此所述控制器需要在所述第三GW-U上创建所述第一IN-PDN。
考虑到如果第一UE和迁移前的第一GW-U或和其它分布有第一IN-PDN的GW-U上的UE有业务上的往来,那么仅仅在迁移后的第三GW-U上创建新的IN-PDN会导致第一UE的本地组网业务的中断。为了避免这种情况发生,还需要在第一GW-U和第三GW-U之间以及在第二GW-U和第三GW-U之间为第一IN-PDN创建转发隧道以及创建相应的处理规则和转发规则,这样这两个GW-U间的第一IN-PDN内的UE间的通信都可以使用该转发隧道,并且之后再有第一IN-PDN内的UE在第一GW-U、第二GW-U和第三GW-U间迁移时,均可以直接使用该转发隧道与其它GW-U上的第一IN-PDN内的UE通信,而无需再创建新的转发隧道。
因此,在场景三下控制器对第一IN-PDN进行扩展的具体过程如下:所述控制器在所述第三GW-U上创建所述第一IN-PDN,并在所述IN-PDN分布信息中添加所述第三GW-U与所述第一IN-PDN的映射关系,以及添加所述第三GW-U与所述第一UE的映射关系。以及,所述控制器获取所述第一IN-PDN对应的隧道标识,并向GW-C发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一GW-U和所述第三GW-U为端点的转发隧道,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二用户面网关和所述第三用户面网关为断点的转发隧道,以及用于指示创建所述第一GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及用于指示创建所述第二GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
场景四:第一UE迁移到第二基站的第三GW-U上,第三GW-U尚未建立所述第一UE所需要的第一IN-PDN,第一UE迁移之前,第一IN-PDN跨
第一GW-U和其它GW-U分布,第一UE迁移之后,第一GW-U上的第一IN-PDN内没有其它UE。
在场景四下,由于第一GW-U上的第一IN-PDN内不再有UE,为避免资源的浪费,可以对第一GW-U上的第一IN-PDN进行资源回收,因此对于第一GW-U而言,第一IN-PDN发生了收缩。又由于第三GW-U上尚未创建第一IN-PDN,所述控制器需要在所述第三GW-U上创建所述第一IN-PDN,因此对于第三GW-U而言,第一IN-PDN发生了扩展。
在场景四下,控制器对第一IN-PDN进行收缩和扩展的具体过程如下:所述控制器在所述第三GW-U上创建所述第一IN-PDN,在所述IN-PDN分布信息中添加所述第三GW-U与所述第一IN-PDN的映射关系,以及添加所述第三GW-U与所述第一UE的映射关系,并在所述IN-PDN分布信息中删除所述第一GW-U与所述第一IN-PDN之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系。以及,所述控制器获取所述第一IN-PDN对应的隧道标识,并向GW-C发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一GW-U和所述第二GW-U为端点的转发隧道,以及用于指示删除所述第一GW-U和所述第二GW-U之间与所述第一IN-PDN关联的处理规则和转发规则,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二用户面网关和所述第三用户面网关为断点的转发隧道,以及用于指示创建所述第二GW-U和所述第三GW-U之间与所述第一IN-PDN关联的处理规则和转发规则。
场景五:第一UE迁移到第二基站的第三GW-U上,第三GW-U尚未建立所述第一UE所需要的第一IN-PDN,第一UE迁移之前,第一IN-PDN只在第一GW-U上分布,第一UE迁移之后,第一GW-U上的第一IN-PDN内仍有其它UE。
在场景五下,控制器对第一IN-PDN进行扩展的具体过程如下:所述控制器在所述第三GW-U上创建所述第一IN-PDN,并在所述IN-PDN分布信息中添加所述第三GW-U与所述第一IN-PDN的映射关系,以及添加所述第三
GW-U与所述第一UE的映射关系。以及,所述控制器获取所述第一IN-PDN对应的隧道标识,并向GW-C发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一GW-U和所述第三GW-U为端点的转发隧道,以及用于指示创建所述第一GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
场景六:第一UE迁移到第二基站的第三GW-U上,第三GW-U尚未建立所述第一UE所需要的第一IN-PDN,第一UE迁移之前,第一IN-PDN只在第一GW-U上分布,第一UE迁移之后,第一GW-U上的第一IN-PDN内没有其它UE。
在场景六下,第一UE发生迁移的前后,第一IN-PDN都仅覆盖一个GW-U,只是第一IN-PDN的覆盖范围由第一GW-U调整到了第三GW-U,因此可视为第一IN-PDN发生了迁移。
在场景六下,控制器对第一IN-PDN进行迁移的具体过程如下:所述控制器在所述第三GW-U上创建所述第一IN-PDN,并在所述IN-PDN分布信息中添加所述第三GW-U与所述第一IN-PDN的映射关系,以及添加所述第三GW-U与所述第一UE的映射关系。以及,所述控制器在所述IN-PDN分布信息中删除所述第一GW-U与所述第一IN-PDN之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系。
可选的,在场景六下控制器还可以回收第一IN-PDN的资源。由于第一IN-PDN仅分布在第一GW-U上,因此第一IN-PDN并不存在相应的转发隧道,因此此处回收的资源仅包括第一IN-PDN在第一GW-U上对应的第一IN-PDN标识。第一IN-PDN在第一GW-U上对应的第一IN-PDN标识。
场景七:第一UE从第一GW-U上去附着,在第一UE去附着之前,第一IN-PDN跨第一GW-U和其它GW-U分布,且第一GW-U上的第一IN-PDN内仍有其它UE。
在场景七下,由于第一GW-U上的第一IN-PDN仍被其它UE所使用,因此无需对第一GW-U上的第一IN-PDN进行资源回收。因此,控制器只需
在所述IN-PDN分布信息中删除所述第一UE与所述第一IN-PDN之间的映射关系和所述第一GW-U与所述第一UE之间的映射关系,而无需对第一IN-PDN进行收缩或扩展。
场景八:第一UE从第一GW-U上去附着,在第一UE去附着之前,第一IN-PDN跨第一GW-U和其它GW-U分布,且第一GW-U上的第一IN-PDN内没有其它UE。
在场景八下,由于第一GW-U上的第一IN-PDN内不再有UE,因此分布在其它GW-U的第一IN-PDN内的UE不会与第一GW-U上的UE有业务上的往来。为避免资源的浪费,可以对第一GW-U上的第一IN-PDN进行资源回收,并对第一IN-PDN进行收缩。
在场景八下,控制器对第一IN-PDN进行收缩的具体过程如下:所述控制器在所述IN-PDN分布信息中删除所述第一GW-U与所述第一IN-PDN之间的映射关系、所述第一GW-U与所述第一UE之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系。以及,所述控制器获取所述第一IN-PDN对应的隧道标识,并向GW-C发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一GW-U和所述第二GW-U为端点的转发隧道,以及用于指示删除所述第一GW-U和所述第二GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
场景九:第一UE从第一GW-U上去附着,在第一UE去附着之前,第一IN-PDN只在第一GW-U上分布,且第一GW-U上的第一IN-PDN内仍有其它UE。
场景九与场景七类似,控制器只需在所述IN-PDN分布信息中删除所述第一UE与所述第一IN-PDN之间的映射关系和所述第一GW-U与所述第一UE之间的映射关系,而无需对第一IN-PDN进行收缩或扩展。
场景十:第一UE从第一GW-U上去附着,在第一UE去附着之前,第一IN-PDN只在第一GW-U上分布,且第一GW-U上的第一IN-PDN内没有其它UE。
在场景十下,由于在第一UE去附着之前第一IN-PDN仅被第一UE所使用,因此在第一UE去附着之后控制器可以删除第一IN-PDN,并回收第一IN-PDN的资源。由于第一IN-PDN仅分布在第一GW-U上,因此第一IN-PDN并不存在相应的转发隧道,因此此处回收的资源仅包括第一IN-PDN在第一GW-U上对应的第一IN-PDN标识。
由于本申请中的IN-PDN只是一种虚拟网络,IN-PDN创建的过程无需去申请实际的网络资源。因此在删除第一IN-PDN时,控制器只需在所述IN-PDN分布信息中删除所述第一GW-U与所述第一IN-PDN之间的映射关系、所述第一GW-U与所述第一UE之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系。
下面说明上述场景三至场景五中提及的所述第二GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及所述第一GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
在所述控制器向GW-C发送指示消息之前,所述控制器可以根据IN-PDN分布信息分别确定所述第一IN-PDN在所述第一GW-U上对应的第一IN-PDN标识和第一隧道端口,所述第一IN-PDN在所述第二GW-U上对应的第二IN-PDN标识和第二隧道端口,以及所述第一IN-PDN在所述第三GW-U上对应的第三IN-PDN标识和第三隧道端口。
从而,所述第二GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则为:在由所述第二GW-U的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第二IN-PDN标识,将增加了所述第二IN-PDN标识的报文中的所述第二IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第二隧道端口转发到所述第三隧道端口;以及,通过所述第二隧道端口接收来自所述第三隧道端口的报文,将所述第二隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第二IN-PDN标识,并删除替换后的报文中的所述第二
IN-PDN标识。在由所述第一UE发送给所述第二GW-U的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第二隧道端口;以及,通过所述第三隧道端口接收来自所述第二隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
所述第一GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则为:在由所述第一GW-U的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第一IN-PDN标识,将增加了所述第一IN-PDN标识的报文中的所述第一IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第一隧道端口转发到所述第三隧道端口;以及,通过所述第一隧道端口接收来自所述第三隧道端口的报文,将所述第一隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第一IN-PDN标识,并删除替换后的报文中的所述第一IN-PDN标识。以及,在由所述第一UE发送给所述第一GW-U的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第一隧道端口;以及,通过所述第三隧道端口接收来自所述第一隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
本申请中,IN-PDN可以通过虚拟局域网(Virtual Local Area Network,简称:VLAN)技术实现,但不限于VLAN技术。例如,IN-PDN还可以通过局域网(Local Area Network,简称:LAN)技术实现。
若所述第一IN-PDN通过VLAN技术实现,相应的,则所述第一IN-PDN的转发隧道可以通过虚拟扩展局域网(Virtual Extensible LAN,简称:VxLAN)
技术实现;所述第一IN-PDN对应的隧道标识可以通过虚拟扩展局域网网络标识(VxLAN Network Identifier,简称:VNI)表示;所述第一隧道端口、所述第二隧道端口和所述第三隧道端口可以通过虚拟扩展局域网隧道端点(Virtual Tunnel End Point,简称:VTEP)的IP地址表示;所述第一IN-PDN标识、所述第二IN-PDN标识和所述第三IN-PDN标识可以通过VLAN ID表示。
为了更清楚地说明本申请的技术方案,下面分别以上述场景四和场景八为例,对上述技术方案做进一步的说明。需要说明的是,这两个实施例仅仅是本申请的两种实现方式,不构成对本申请的限定。
实施例一
本实施例一对应上述场景四,即第一UE从第一基站的第一GW-U迁移到第二基站的第三GW-U上,第三GW-U尚未建立所述第一UE所需要的第一IN-PDN,第一UE迁移之前,第一IN-PDN跨第一GW-U和其它GW-U分布,第一UE迁移之后,第一GW-U上的第一IN-PDN内没有其它UE。
在这种场景下,各网元之间的信令交互流程如图6所示:
1、目标eNB向MME发送路径切换请求(Path Switch Request)消息,携带目标eNB的GTP地址和TEID,同时携带目标TAI信息。
这里的目标eNB相当于前文的第二基站。
2、MME向GW-C发送修改负载请求(Modify Bearer Request)消息,将目标eNB的通用分组无线服务隧道协议(简称:GTP)地址和TEID以及目标TAI信息通知给GW-C。
3、GW-C向IN-PDN控制器发送UE移动事件通告,通知第一UE从源eNB移动到目标eNB。
这里的源eNB相当于前文的第一基站。
4、IN-PDN控制器根据第一UE的位置信息和业务等信息决定网关重选。
5、IN-PDN控制器向GW-C发送网关重选请求。
6、如果第5步的网关重选请求中携带了目标GW-U的信息,如目标GW-U的IP地址,则直接跳转到第7步,否则由GW-C执行网关重选。
GW-C执行网关重选时,可以向域名系统(Domain Name System,简称:DNS)发送DNS请求,DNS请求中携带第一UE的IN-APN。
DNS对收到的DNS请求中携带的IN-APN进行判断,如果确定是IN-APN格式的,则使用第一UE的IN-APN和第一UE的小区信息在本地存储的GW-U信息中查询相匹配的GW-U,该匹配的GW-U与第一UE的位置相近且其上已经创建了与第一UE的IN-APN对应的IN-PDN。
若匹配到合适的GW-U,则DNS将匹配到的GW-U的IP地址携带在DNS请求响应中返回给GW-C。
若未匹配到合适的GW-U,则DNS请求IN-PDN控制器为UE选择新的GW-U。在IN-PDN控制器为UE确定新的GW-U之后,IN-PDN控制器将第一UE的小区信息、IN-APN以及新的GW-U信息返回给DNS,再由DNS将IN-PDN选择的GW-U的IP地址携带在DNS请求响应中返回给GW-C。这样,当再有其它UE附着时,如果该其它UE的小区信息和IN-APN均与第一UE的小区信息和IN-APN相同,则GW-C向DNS发送请求,DNS可直接返回相应的GW-U而不再需要请求IN-PDN控制器为该其它UE选择GW-U。
7、GW-C向IN-PDN控制器发送网关重选响应,携带为第一UE重选的目标GW-U的TEID和IP地址。
这里的目标GW-U相当于前文的第三GW-U。
8、IN-PDN控制器查询当前的IN-PDN分布信息,发现目标GW-U上尚未创建第一UE需要接入的第一IN-PDN,第一IN-PDN跨源GW-U和其它GW-U分布,源GW-U上的第一IN-PDN内不再有除第一UE之外的其它UE。
这里的源GW-U相当于前文的第一GW-U,分布有第一IN-PDN的其它GW-U相当于前文的第二GW-U,源GW-U上的第一IN-PDN内的其它UE相当于前文的第二UE。
9、IN-PDN控制器向GW-C发送IN-PDN配置通知,再由GW-C将该IN-PDN配置通知转发给目标GW-U,IN-PDN配置通知中携带IN-PDN配置信息。
IN-PDN配置信息中包括IN-PDN控制器为待配置的第一IN-PDN分配的第一IN-PDN在目标GW-U上的IN-PDN标识。
10、目标GW-U完成IN-PDN配置后,向GW-C发送IN-PDN配置通知确认(Ack),由GW-C将IN-PDN配置通知确认转发给IN-PDN控制器。
11、IN-PDN控制器在IN-PDN分布信息中查询第一IN-PDN对应的隧道标识,并更新IN-PDN分布信息中第一IN-PDN与GW-U之间、第一IN-PDN与第一UE之间、第一UE与GW-U之间的映射关系。
如果IN-PDN通过VLAN技术实现,则相应地在IN-PDN分布信息中删除源GW-U的信息以及第一IN-PDN在源GW-U上对应的VLAN ID,添加目标GW-U的信息以及第一IN-PDN在目标GW-U上对应的VLAN ID。同时,在源GW-U所连接的UE信息中删除第一UE的信息,在目标GW-U所连接的UE信息中添加第一UE的信息。
12、IN-PDN控制器根据更新后的IN-PDN分布信息,将更新后的第一IN-PDN的分布情况更新到DNS。
13、IN-PDN控制器向GW-C发送跨GW-U的IN-PDN转发隧道增删请求,请求中携带IN-PDN控制器查询到的第一IN-PDN的隧道标识,待作隧道增删的GW-U的信息,以及第一IN-PDN分别在每个待作隧道增删的GW-U上的IN-PDN标识以及每个待作隧道增删的GW-U的隧道增删标示(Flag)。
如果IN-PDN通过VLAN技术实现,那么隧道标识可以用VNI表示,IN-PDN标识可以用VLAN ID表示,GW-U信息可以用GW-U的IP地址标识。
IN-PDN控制器可以事先与GW-C约定,例如,约定Flag等于0表示删除隧道并更新隧道间的转发规则和处理规则,Flag等于1表示建立隧道并更新隧道间的转发规则和处理规则,Flag等于2表示更新隧道间的转发规则和处理规则。
本实施例中,目标GW-U的Flag等于1,源GW-U的Flag等于0,分布有该第一IN-PDN的其它GW-U的Flag等于2。
14、GW-C向IN-PDN控制器发送跨GW-U的IN-PDN转发隧道增删请求
Ack。
15、GW-C收到目标GW-U的隧道增删Flag等于1,因此向目标GW-U发送隧道建立请求,隧道建立请求中携带步骤13中IN-PDN控制器传递来的隧道标识。
16、目标GW-U向GW-C发送隧道建立响应,隧道建立响应中携带目标GW-U为该隧道分配的端口信息。
17、GW-C收到源GW-U的隧道增删Flag等于0,因此向源GW-U发送隧道删除请求,隧道删除请求中携带步骤13中IN-PDN控制器传递来的隧道标识。
18、Source GW-U向IN-PDN控制器发送隧道删除响应。
19、GW-C向IN-PDN控制器发送转发隧道增删完成通知。
20、IN-PDN控制器向GW-C发送转发隧道增删完成通知Ack。
21、GW-C向源GW-U发送转发规则更新通知,更新源GW-U上的转发规则和处理规则。
转发规则和处理规则的更新具体表现为:删除源GW-U到其它GW-U上的与第一IN-PDN相关的UE间的转发规则和处理规则。
22、源GW-U向GW-C发送转发规则更新Ack。
23、GW-C向其它GW-U发送转发规则更新通知,更新其它GW-U上的转发规则和处理规则。
如果转发隧道是通过VxLAN技术实现的,则转发规则和处理规则的更新具体表现为:删除其它GW-U到源GW-U上的与第一IN-PDN相关的UE间的转发规则和处理规则。在由其它GW-U的第一IN-PDN内的UE发送给第一UE的报文中增加第一IN-PDN在其它GW-U上对应的VLAN ID,并将增加了VLAN ID的报文中的该VLAN ID替换为第一IN-PDN的VNI,然后将替换后的报文通过其它GW-U上为第一IN-PDN创建的隧道端口转发到步骤16中创建的隧道端口。以及,通过其它GW-U上为第一IN-PDN创建的隧道端口接收经步骤16中创建的隧道端口转发的来自第一UE的报文,并将接收的
报文中的VNI替换为第一IN-PDN在其它GW-U上对应的VLAN ID,然后删除替换后的报文中的该VLAN ID。
24、其它GW-U向GW-C发送转发规则更新Ack。
25、GW-C向目标GW-U发送转发规则更新通知,更新目标GW-U上的转发规则和处理规则。
如果转发隧道是通过VxLAN技术实现的,则转发规则和处理规则的更新具体表现为:在由第一UE发送给其它GW-U的第一IN-PDN内的UE的报文中增加第一IN-PDN在目标GW-U上对应的VLAN ID,并将增加了VLAN ID的报文中的该VLAN ID替换为第一IN-PDN的VNI,然后将替换后的报文通过步骤16中创建的隧道端口转发到其它GW-U上为第一IN-PDN创建的隧道端口;以及,通过步骤16中创建的隧道端口接收经其它GW-U为第一IN-PDN创建的隧道端口转发的发送给第一UE的报文,并将接收的报文中的VNI替换为第一IN-PDN在目标GW-U上对应的VLAN ID,然后删除替换后的报文中的该VLAN ID。
26、目标GW-U向GW-C发送转发规则更新Ack。
之后便可进行现有的UE切换流程。
实施例二
本实施例二对应上述场景八,即第一UE从第一GW-U上去附着,在第一UE去附着之前,第一IN-PDN跨第一GW-U和其它GW-U分布,且第一GW-U上的第一IN-PDN内没有其它UE。
在这种场景下,各网元之间的信令交互流程如图7所示:
1、第一UE从源GW-U上去附着。IN-PDN控制器查询当前的IN-PDN分布信息,发现源GW-U上的第一IN-PDN内没有除第一UE外的其它UE,第一IN-PDN在其它GW-U上仍有分布。根据查询结果,IN-PDN控制器更新IN-PDN分布信息中第一IN-PDN与GW-U之间、第一IN-PDN与第一UE之间、第一UE与GW-U之间的映射关系,并在IN-PDN分布信息中查询第一UE所属的第一IN-PDN对应的隧道标识。
如果IN-PDN通过VLAN技术实现,则IN-PDN控制器相应地在IN-PDN分布信息中删除源GW-U的信息以及第一IN-PDN在源GW-U上对应的VLAN ID。同时,在源GW-U所连接的UE信息中删除第一UE的信息。
2、IN-PDN控制器向GW-C发送跨GW-U的IN-PDN转发隧道增删请求,请求中携带IN-PDN控制器查询到的第一IN-PDN对应的隧道标识,待作隧道增删的GW-U的信息,以及第一IN-PDN分别在每个待作隧道增删的GW-U上的IN-PDN标识以及每个待作隧道增删的GW-U的隧道增删Flag。
如果IN-PDN通过VLAN技术实现,那么隧道标识可以用VNI表示,IN-PDN标识可以用VLAN ID表示,GW-U的信息可以用GW-U的IP地址表示。
IN-PDN控制器可以事先与GW-C约定,例如,约定Flag等于0表示删除隧道并更新隧道间的转发规则和处理规则,Flag等于1表示建立隧道并更新隧道间的转发规则和处理规则,Flag等于2表示更新隧道间的转发规则和处理规则。
本实施例中,源GW-U的Flag等于0,分布有第一IN-PDN的其它GW-U的Flag等于2。
3、GW-C向IN-PDN控制器发送跨GW-U的IN-PDN转发隧道增删请求Ack。
4、GW-C收到源GW-U的隧道增删Flag等于0,因此向源GW-U发送隧道删除请求,隧道删除请求中携带步骤2中IN-PDN分配器传递来的隧道标识。
5、源GW-U向GW-C发送隧道删除响应。
6、GW-C向IN-PDN控制器发送转发隧道增删完成通知。
7、IN-PDN控制器向GW-C发送转发隧道增删完成通知Ack。
8、GW-C向其它GW-U发送转发规则更新通知,更新其它GW-U上的转发规则和处理规则。
转发规则和处理规则的更新具体表现为:删除其它GW-U到源GW-U上的与第一IN-PDN相关的UE间的转发规则和处理规则。
9、其它GW-U向GW-C发送转发规则更新Ack。
10、GW-C向源GW-U发送转发规则更新通知,更新源GW-U上的转发规则和处理规则。
转发规则和处理规则的更新具体表现为:删除源GW-U到其它GW-U上的与第一IN-PDN相关的UE间的转发规则和处理规则。
11、源GW-U向GW-C发送转发规则更新Ack。
基于本申请上述提供的网络管理方法,本申请提供一种控制器800,用于实现上述网络管理方法中控制器的功能,如图8所示,所述控制器800包括确定单元801,判断单元802和处理单元803。
所述确定单元801,用于当第一UE从第一基站脱离时,根据IN-PDN分布信息,确定所述第一UE在从第一基站脱离之前所接入的第一IN-PDN和第一用户面网关;所述IN-PDN分布信息用于指示IN-PDN、GW-U和UE之间的映射关系。
所述判断单元802,用于根据所述IN-PDN分布信息判断是否存在第二UE和第二GW-U,所述第二UE与所述第一IN-PDN之间存在映射关系且所述第二UE与所述第一GW-U之间也存在映射关系,所述第二GW-U与所述第一IN-PDN之间存在映射关系。
所述处理单元803,用于根据所述判断单元802关于是否存在所述第二UE和所述第二GW-U的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与GW-U之间的映射关系。
可选的,所述第一UE从第一基站脱离,具体可以包括以下两种场景:第一UE从第一基站切换到第二基站,或是第一UE从第一基站去附着。
可选的,所述IN-PDN分布信息用于指示IN-PDN与用户面网关之间的映射关系、用户面网关与UE之间的映射关系以及IN-PDN与UE之间的映射关系。
可选的,在所述判断单元802根据所述IN-PDN分布信息判断是否存在第
二UE和第二GW-U之前,所述处理单元803还可以用于:在所述IN-PDN分布信息中删除所述第一UE与所述第一GW-U之间的映射关系。
可选的,所述控制器800还包括网络接口。
在去附着场景下,当第一UE从所述第一基站去附着,所述判断结果为所述IN-PDN分布信息中存在所述第二GW-U但不存在所述第二UE时;所述处理单元803具体用于:在所述IN-PDN分布信息中删除所述第一GW-U与所述第一IN-PDN之间的映射关系、所述第一GW-U与所述第一UE之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系;获取所述第一IN-PDN对应的隧道标识,并通过所述网络接口向GW-C发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一GW-U和所述第二GW-U为端点的转发隧道,以及用于指示删除所述第一GW-U和所述第二GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
可选的,当第一UE从第一基站切换到第二基站时;在所述判断单元802根据所述IN-PDN分布信息判断是否存在第二UE和第二GW-U之前,所述处理单元803还可以用于:确定所述第一UE在从所述第一基站切换到所述第二基站之后所接入的第三GW-U;根据所述IN-PDN分布信息判断所述第三GW-U是否与所述第一IN-PDN存在映射关系。若所述第三GW-U与所述第一IN-PDN之间不存在映射关系,则在所述第三GW-U上创建所述第一IN-PDN,并在所述IN-PDN分布信息中添加所述第三GW-U与所述第一IN-PDN的映射关系,以及添加所述第三GW-U与所述第一UE的映射关系;若所述第三GW-U与所述第一IN-PDN之间存在映射关系,则在所述IN-PDN分布信息中添加所述第三GW-U与所述第一UE的映射关系。
可选的,在切换场景的一种情况下,当所述判断结果为所述IN-PDN分布信息中存在所述第二GW-U但不存在所述第二UE,且所述第三GW-U与所述第一IN-PDN之间不存在映射关系时;所述处理单元803具体用于:在所述IN-PDN分布信息中删除所述第一GW-U与所述第一IN-PDN之间的映射关系
和所述第一UE与所述第一IN-PDN之间的映射关系;获取所述第一IN-PDN对应的隧道标识,并通过所述网络接口向GW-C发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一GW-U和所述第二GW-U为端点的转发隧道,以及用于指示删除所述第一GW-U和所述第二GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二GW-U和所述第三GW-U为断点的转发隧道,以及用于指示创建所述第二GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
可选的,在切换场景的一种情况下,当所述判断结果为所述IN-PDN分布信息中存在所述第二GW-U和所述第二UE,且所述第三GW-U与所述第一IN-PDN之间不存在映射关系时;所述处理单元803具体用于:获取所述第一IN-PDN对应的隧道标识,并通过所述网络接口向GW-C发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一GW-U和所述第三GW-U为端点的转发隧道,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二GW-U和所述第三GW-U为断点的转发隧道,以及用于指示创建所述第一GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及用于指示创建所述第二GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
可选的,在切换场景的一种情况下,当所述判断结果为所述IN-PDN分布信息中不存在所述第二GW-U但存在所述第二UE,且所述第三GW-U与所述第一IN-PDN之间不存在映射关系时;所述处理单元803具体用于:获取所述第一IN-PDN对应的隧道标识,并通过所述网路接口向GW-C发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一GW-U和所述第三GW-U为端点的转发隧道,以及用于指示创建所述第一GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的
处理规则和转发规则。
可选的,在所述处理单元803通过所述网络接口向GW-C发送指示消息之前,所述处理单元803还用于:确定所述第一IN-PDN在所述第二GW-U上对应的第二IN-PDN标识和第二隧道端口,以及确定所述第一IN-PDN在所述第三GW-U上对应的第三IN-PDN标识和第三隧道端口。
相应的,所述第二GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则为:在由所述第二GW-U的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第二IN-PDN标识,将增加了所述第二IN-PDN标识的报文中的所述第二IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第二隧道端口转发到所述第三隧道端口;以及,通过所述第二隧道端口接收来自所述第三隧道端口的报文,将所述第二隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第二IN-PDN标识,并删除替换后的报文中的所述第二IN-PDN标识。在由所述第一UE发送给所述第二GW-U的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第二隧道端口;以及,通过所述第三隧道端口接收来自所述第二隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
可选的,在所述处理单元803通过所述网络接口向GW-C发送指示消息之前,所述处理单元803还用于:确定所述第一IN-PDN在所述第一GW-U上对应的第一IN-PDN标识和第一隧道端口,以及确定所述第一IN-PDN在所述第三GW-U上对应的第三IN-PDN标识和第三隧道端口。
相应的,所述第一GW-U和所述第三GW-U之间与所述第一IN-PDN关联的UE间的处理规则和转发规则为:在由所述第一GW-U的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第一IN-PDN标识,
将增加了所述第一IN-PDN标识的报文中的所述第一IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第一隧道端口转发到所述第三隧道端口;以及,通过所述第一隧道端口接收来自所述第三隧道端口的报文,将所述第一隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第一IN-PDN标识,并删除替换后的报文中的所述第一IN-PDN标识。在由所述第一UE发送给所述第一GW-U的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第一隧道端口;以及,通过所述第三隧道端口接收来自所述第一隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
可选的,若所述第一IN-PDN通过VLAN实现;则所述第一IN-PDN对应的隧道标识可以通过VNI表示。所述第一隧道端口、所述第二隧道端口和所述第三隧道端口通过VTEP的IP地址表示。所述第一IN-PDN标识、所述第二IN-PDN标识和所述第三IN-PDN标识通过VLAN ID表示。
本实施例中未尽之细节可参考上述图5所示方法中控制器的描述,在此不再赘述。
需要说明的是,本发明实施例中对单元的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
其中,集成的单元采用硬件的形式实现时,所述确定单元801、判断单元802和处理单元803对应的实体的硬件可以是处理器,例如图9的处理器901。
根据本申请实施例的控制器800可对应于根据本发明实施例的网络管理方法中的控制器,并且控制器800中的各个单元的上述和其它操作和/或功能
分别为了实现图3至图7中的各个方法的相应流程,为了简洁,在此不再赘述。
基于上述提供的网络管理方法,本申请还提供一种控制器900,如图9所示,控制器900包括处理器901和存储器902,例如,所述处理器801和所述存储器902通过总线903相互连接。
所述存储器902用于存储所述处理器901的可执行指令。
所述处理器901被配置为:当第一UE从第一基站脱离时,根据IN-PDN分布信息,确定所述第一UE在从第一基站脱离之前所接入的第一IN-PDN和第一用户面网关;所述IN-PDN分布信息用于指示IN-PDN、用户面网关和UE之间的映射关系。根据所述IN-PDN分布信息判断是否存在第二UE和第二GW-U,所述第二UE与所述第一IN-PDN之间存在映射关系且所述第二UE与所述第一GW-U之间也存在映射关系,所述第二GW-U与所述第一IN-PDN之间存在映射关系。根据是否存在所述第二UE和所述第二GW-U的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与GW-U之间的映射关系。
综上所述,本申请提供的技术方案,实现了IN-PDN的动态伸缩,在UE发生迁移或去附着时,仍能保证UE的本地组网内的业务的连续性,并及时回收不再使用的IN-PDN资源,避免了IN-PDN资源的浪费。
本领域内的技术人员应明白,本发明的实施例可提供为方法、系统、或计算机程序产品。因此,本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程
和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例,但本领域内的技术人员一旦得知了基本创造性概念,则可对这些实施例作出另外的变更和修改。所以,所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然,本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的精神和范围。这样,倘若本发明实施例的这些修改和变型属于本发明权利要求及其等同技术的范围之内,则本发明也意图包含这些改动和变型在内。
Claims (25)
- 一种网络管理方法,其特征在于,包括:当第一用户设备UE从第一基站脱离时,控制器根据网内分组数据网IN-PDN分布信息,确定所述第一UE在从第一基站脱离之前所接入的第一IN-PDN和第一用户面网关;所述IN-PDN分布信息用于指示IN-PDN、用户面网关和UE之间的映射关系;所述控制器根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关,所述第二UE与所述第一IN-PDN之间存在映射关系且所述第二UE与所述第一用户面网关之间也存在映射关系,所述第二用户面网关与所述第一IN-PDN之间存在映射关系;所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系。
- 如权利要求1所述的方法,其特征在于,所述第一UE从第一基站脱离,包括:所述第一UE从第一基站切换到第二基站;或所述第一UE从第一基站去附着。
- 如权利要求1或2所述的方法,其特征在于,所述IN-PDN分布信息用于指示IN-PDN与用户面网关之间的映射关系、用户面网关与UE之间的映射关系以及IN-PDN与UE之间的映射关系。
- 如权利要求1-3中任一项所述的方法,其特征在于,在所述控制器根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关之前,所述方法还包括:所述控制器在所述IN-PDN分布信息中删除所述第一UE与所述第一用户面网关之间的映射关系。
- 如权利要求2-4中任一项所述的方法,其特征在于,当第一UE从所述第一基站去附着,所述判断结果为所述IN-PDN分布信息中存在所述第二用户面网关但不存在所述第二UE时;所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系,包括:所述控制器在所述IN-PDN分布信息中删除所述第一用户面网关与所述第一IN-PDN之间的映射关系、所述第一用户面网关与所述第一UE之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系;所述控制器获取所述第一IN-PDN对应的隧道标识,并向控制面网关发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第二用户面网关为端点的转发隧道,以及用于指示删除所述第一用户面网关和所述第二用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
- 如权利要求2-4中任一项所述的方法,其特征在于,当第一UE从第一基站切换到第二基站时;在所述控制器根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关之前,所述方法还包括:所述控制器确定所述第一UE在从所述第一基站切换到所述第二基站之后所接入的第三用户面网关;所述控制器根据所述IN-PDN分布信息判断所述第三用户面网关是否与所述第一IN-PDN存在映射关系;若所述第三用户面网关与所述第一IN-PDN之间不存在映射关系,则所述控制器在所述第三用户面网关上创建所述第一IN-PDN,并在所述IN-PDN分布信息中添加所述第三用户面网关与所述第一IN-PDN的映射关系,以及添加所述第三用户面网关与所述第一UE的映射关系;若所述第三用户面网关与所述第一IN-PDN之间存在映射关系,则所述控制器在所述IN-PDN分布信息中添加所述第三用户面网关与所述第一UE的映射关系。
- 如权利要求6所述的方法,其特征在于,当所述判断结果为所述IN-PDN分布信息中存在所述第二用户面网关但不存在所述第二UE,且所述第三用户面网关与所述第一IN-PDN之间不存在映射关系时;所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系,包括:所述控制器在所述IN-PDN分布信息中删除所述第一用户面网关与所述第一IN-PDN之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系;所述控制器获取所述第一IN-PDN对应的隧道标识,并向控制面网关发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第二用户面网关为端点的转发隧道,以及用于指示删除所述第一用户面网关和所述第二用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二用户面网关和所述第三用户面网关为断点的转发隧道,以及用于指示创建所述第二用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
- 如权利要求6所述的方法,其特征在于,当所述判断结果为所述IN-PDN分布信息中存在所述第二用户面网关和所述第二UE,且所述第三用户面网关与所述第一IN-PDN之间不存在映射关系时;所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之 间的映射关系,包括:所述控制器获取所述第一IN-PDN对应的隧道标识,并向控制面网关发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第三用户面网关为端点的转发隧道,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二用户面网关和所述第三用户面网关为断点的转发隧道,以及用于指示创建所述第一用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及用于指示创建所述第二用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
- 如权利要求6所述的方法,其特征在于,当所述判断结果为所述IN-PDN分布信息中不存在所述第二用户面网关但存在所述第二UE,且所述第三用户面网关与所述第一IN-PDN之间不存在映射关系时;所述控制器根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系,包括:所述控制器获取所述第一IN-PDN对应的隧道标识,并向控制面网关发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第三用户面网关为端点的转发隧道,以及用于指示创建所述第一用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
- 如权利要求7或8所述的方法,其特征在于,在所述控制器向控制面网关发送指示消息之前,所述方法还包括:所述控制器确定所述第一IN-PDN在所述第二用户面网关上对应的第二IN-PDN标识和第二隧道端口,以及确定所述第一IN-PDN在所述第三用户面网关上对应的第三IN-PDN标识和第三隧道端口;所述第二用户面网关和所述第三用户面网关之间与所述第一IN-PDN关 联的UE间的处理规则和转发规则为:在由所述第二用户面网关的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第二IN-PDN标识,将增加了所述第二IN-PDN标识的报文中的所述第二IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第二隧道端口转发到所述第三隧道端口;以及,通过所述第二隧道端口接收来自所述第三隧道端口的报文,将所述第二隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第二IN-PDN标识,并删除替换后的报文中的所述第二IN-PDN标识;在由所述第一UE发送给所述第二用户面网关的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第二隧道端口;以及,通过所述第三隧道端口接收来自所述第二隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
- 如权利要求8或9所述的方法,其特征在于,在所述控制器向控制面网关发送指示消息之前,所述方法还包括:所述控制器确定所述第一IN-PDN在所述第一用户面网关上对应的第一IN-PDN标识和第一隧道端口,以及确定所述第一IN-PDN在所述第三用户面网关上对应的第三IN-PDN标识和第三隧道端口;所述第一用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则为:在由所述第一用户面网关的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第一IN-PDN标识,将增加了所述第一IN-PDN标识的报文中的所述第一IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第一隧道端口转发到所述第三隧道端口;以及,通过所述第一隧道端口接收来自所述第三隧道端口的报文,将所述第一隧道端 口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第一IN-PDN标识,并删除替换后的报文中的所述第一IN-PDN标识;在由所述第一UE发送给所述第一用户面网关的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第一隧道端口;以及,通过所述第三隧道端口接收来自所述第一隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
- 如权利要求10或11所述的方法,其特征在于,若所述第一IN-PDN通过虚拟局域网VLAN实现;则所述第一IN-PDN对应的隧道标识通过虚拟扩展局域网网络标识VNI表示;所述第一隧道端口、所述第二隧道端口和所述第三隧道端口通过虚拟扩展局域网隧道端点VTEP的网际协议IP地址表示;所述第一IN-PDN标识、所述第二IN-PDN标识和所述第三IN-PDN标识通过VLAN标识表示。
- 一种控制器,其特征在于,包括:确定单元,用于当第一用户设备UE从第一基站脱离时,根据网内分组数据网IN-PDN分布信息,确定所述第一UE在从第一基站脱离之前所接入的第一IN-PDN和第一用户面网关;所述IN-PDN分布信息用于指示IN-PDN、用户面网关和UE之间的映射关系;判断单元,用于根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关,所述第二UE与所述第一IN-PDN之间存在映射关系且所述第二UE与所述第一用户面网关之间也存在映射关系,所述第二用户面网关与所述第一IN-PDN之间存在映射关系;处理单元,用于根据所述判断单元关于是否存在所述第二UE和所述第二 用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系。
- 如权利要求13所述的控制器,其特征在于,所述第一UE从第一基站脱离,包括:所述第一UE从第一基站切换到第二基站;或所述第一UE从第一基站去附着。
- 如权利要求13或14所述的控制器,其特征在于,所述IN-PDN分布信息用于指示IN-PDN与用户面网关之间的映射关系、用户面网关与UE之间的映射关系以及IN-PDN与UE之间的映射关系。
- 如权利要求13-15中任一项所述的控制器,其特征在于,在所述判断单元根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关之前,所述处理单元还用于:在所述IN-PDN分布信息中删除所述第一UE与所述第一用户面网关之间的映射关系。
- 如权利要求14-16中任一项所述的控制器,其特征在于,当第一UE从所述第一基站去附着,所述判断结果为所述IN-PDN分布信息中存在所述第二用户面网关但不存在所述第二UE时;所述控制器还包括网络接口;在根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系时,所述处理单元具体用于:在所述IN-PDN分布信息中删除所述第一用户面网关与所述第一IN-PDN之间的映射关系、所述第一用户面网关与所述第一UE之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系;获取所述第一IN-PDN对应的隧道标识,并通过所述网络接口向控制面网 关发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第二用户面网关为端点的转发隧道,以及用于指示删除所述第一用户面网关和所述第二用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
- 如权利要求14-16中任一项所述的控制器,其特征在于,当第一UE从第一基站切换到第二基站时;在所述判断单元根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关之前,所述处理单元还用于:确定所述第一UE在从所述第一基站切换到所述第二基站之后所接入的第三用户面网关;根据所述IN-PDN分布信息判断所述第三用户面网关是否与所述第一IN-PDN存在映射关系;若所述第三用户面网关与所述第一IN-PDN之间不存在映射关系,则在所述第三用户面网关上创建所述第一IN-PDN,并在所述IN-PDN分布信息中添加所述第三用户面网关与所述第一IN-PDN的映射关系,以及添加所述第三用户面网关与所述第一UE的映射关系;若所述第三用户面网关与所述第一IN-PDN之间存在映射关系,则在所述IN-PDN分布信息中添加所述第三用户面网关与所述第一UE的映射关系。
- 如权利要求18所述的控制器,其特征在于,当所述判断结果为所述IN-PDN分布信息中存在所述第二用户面网关但不存在所述第二UE,且所述第三用户面网关与所述第一IN-PDN之间不存在映射关系时;所述控制器还包括网络接口;在根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系时,所述处理单元具体用于:在所述IN-PDN分布信息中删除所述第一用户面网关与所述第一IN-PDN 之间的映射关系和所述第一UE与所述第一IN-PDN之间的映射关系;获取所述第一IN-PDN对应的隧道标识,并通过所述网络接口向控制面网关发送指示消息;所述指示消息用于指示删除以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第二用户面网关为端点的转发隧道,以及用于指示删除所述第一用户面网关和所述第二用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二用户面网关和所述第三用户面网关为断点的转发隧道,以及用于指示创建所述第二用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
- 如权利要求18所述的控制器,其特征在于,当所述判断结果为所述IN-PDN分布信息中存在所述第二用户面网关和所述第二UE,且所述第三用户面网关与所述第一IN-PDN之间不存在映射关系时;所述控制器还包括网络接口;在根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系时,所述处理单元具体用于:获取所述第一IN-PDN对应的隧道标识,并通过所述网络接口向控制面网关发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第三用户面网关为端点的转发隧道,以及用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第二用户面网关和所述第三用户面网关为断点的转发隧道,以及用于指示创建所述第一用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则,以及用于指示创建所述第二用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
- 如权利要求18所述的控制器,其特征在于,当所述判断结果为所述IN-PDN分布信息中不存在所述第二用户面网关但存在所述第二UE,且所述第三用户面网关与所述第一IN-PDN之间不存在映射关系时;所述控制器还包括网络接口;在根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系时,所述处理单元具体用于:获取所述第一IN-PDN对应的隧道标识,并通过所述网路接口向控制面网关发送指示消息;所述指示消息用于指示创建以所述第一IN-PDN对应的隧道标识为标识、以所述第一用户面网关和所述第三用户面网关为端点的转发隧道,以及用于指示创建所述第一用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则。
- 如权利要求19或20所述的控制器,其特征在于,在所述处理单元通过所述网络接口向控制面网关发送指示消息之前,所述处理单元还用于:确定所述第一IN-PDN在所述第二用户面网关上对应的第二IN-PDN标识和第二隧道端口,以及确定所述第一IN-PDN在所述第三用户面网关上对应的第三IN-PDN标识和第三隧道端口;所述第二用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则为:在由所述第二用户面网关的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第二IN-PDN标识,将增加了所述第二IN-PDN标识的报文中的所述第二IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第二隧道端口转发到所述第三隧道端口;以及,通过所述第二隧道端口接收来自所述第三隧道端口的报文,将所述第二隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第二IN-PDN标识,并删除替换后的报文中的所述第二IN-PDN标识;在由所述第一UE发送给所述第二用户面网关的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第二隧道端口;以及,通过所述第三隧道端口接收来自所述第二隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
- 如权利要求20或21所述的控制器,其特征在于,在所述处理单元通过所述网络接口向控制面网关发送指示消息之前,所述处理单元还用于:确定所述第一IN-PDN在所述第一用户面网关上对应的第一IN-PDN标识和第一隧道端口,以及确定所述第一IN-PDN在所述第三用户面网关上对应的第三IN-PDN标识和第三隧道端口;所述第一用户面网关和所述第三用户面网关之间与所述第一IN-PDN关联的UE间的处理规则和转发规则为:在由所述第一用户面网关的所述第一IN-PDN内的UE发送给所述第一UE的报文中增加所述第一IN-PDN标识,将增加了所述第一IN-PDN标识的报文中的所述第一IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第一隧道端口转发到所述第三隧道端口;以及,通过所述第一隧道端口接收来自所述第三隧道端口的报文,将所述第一隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第一IN-PDN标识,并删除替换后的报文中的所述第一IN-PDN标识;在由所述第一UE发送给所述第一用户面网关的所述第一IN-PDN内的UE的报文中增加所述第三IN-PDN标识,将增加了所述第三IN-PDN标识的报文中的所述第三IN-PDN标识替换为所述第一IN-PDN对应的隧道标识,并将替换后的报文通过所述第三隧道端口转发到所述第一隧道端口;以及,通过所述第三隧道端口接收来自所述第一隧道端口的报文,将所述第三隧道端口接收到的报文中的所述第一IN-PDN对应的隧道标识替换为所述第三 IN-PDN标识,并删除替换后的报文中的所述第三IN-PDN标识。
- 如权利要求22或23所述的控制器,其特征在于,若所述第一IN-PDN通过虚拟局域网VLAN实现;则所述第一IN-PDN对应的隧道标识通过虚拟扩展局域网网络标识VNI表示;所述第一隧道端口、所述第二隧道端口和所述第三隧道端口通过虚拟扩展局域网隧道端点VTEP的网际协议IP地址表示;所述第一IN-PDN标识、所述第二IN-PDN标识和所述第三IN-PDN标识通过VLAN标识表示。
- 一种控制器,其特征在于,包括处理器和用于存储所述处理器可执行指令的存储器;其中,所述处理器被配置为:当第一用户设备UE从第一基站脱离时,根据网内分组数据网IN-PDN分布信息,确定所述第一UE在从第一基站脱离之前所接入的第一IN-PDN和第一用户面网关;所述IN-PDN分布信息用于指示IN-PDN、用户面网关和UE之间的映射关系;根据所述IN-PDN分布信息判断是否存在第二UE和第二用户面网关,所述第二UE与所述第一IN-PDN之间存在映射关系且所述第二UE与所述第一用户面网关之间也存在映射关系,所述第二用户面网关与所述第一IN-PDN之间存在映射关系;根据是否存在所述第二UE和所述第二用户面网关的判断结果,确定是否更新所述第一IN-PDN与转发隧道之间的映射关系、所述第一IN-PDN与所述第一UE之间的映射关系和所述第一IN-PDN与用户面网关之间的映射关系。
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2016/096998 WO2018035864A1 (zh) | 2016-08-26 | 2016-08-26 | 一种网络管理方法和控制器 |
| EP16913885.6A EP3500043A4 (en) | 2016-08-26 | 2016-08-26 | NETWORK MANAGEMENT PROCESS AND CONTROL DEVICE |
| CN201680088743.6A CN109644384B (zh) | 2016-08-26 | 2016-08-26 | 一种网络管理方法和控制器 |
| US16/285,898 US11064551B2 (en) | 2016-08-26 | 2019-02-26 | Network management method and controller |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2016/096998 WO2018035864A1 (zh) | 2016-08-26 | 2016-08-26 | 一种网络管理方法和控制器 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US16/285,898 Continuation US11064551B2 (en) | 2016-08-26 | 2019-02-26 | Network management method and controller |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2018035864A1 true WO2018035864A1 (zh) | 2018-03-01 |
Family
ID=61245994
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/096998 Ceased WO2018035864A1 (zh) | 2016-08-26 | 2016-08-26 | 一种网络管理方法和控制器 |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US11064551B2 (zh) |
| EP (1) | EP3500043A4 (zh) |
| CN (1) | CN109644384B (zh) |
| WO (1) | WO2018035864A1 (zh) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200022074A1 (en) * | 2016-09-30 | 2020-01-16 | Ntt Docomo, Inc. | Gateway selection method and communication system |
| WO2020097134A1 (en) * | 2018-11-05 | 2020-05-14 | Parallel Wireless, Inc. | Locally-generated teids for core high availability |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104105143A (zh) * | 2013-04-03 | 2014-10-15 | 北京三星通信技术研究有限公司 | 一种支持sipto业务的方法 |
| CN104349405A (zh) * | 2013-07-23 | 2015-02-11 | 华为技术有限公司 | 传输数据的方法、通信节点和基站 |
| CN104618849A (zh) * | 2013-11-01 | 2015-05-13 | 中兴通讯股份有限公司 | 终端的本地交换方法及系统 |
Family Cites Families (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101646158B (zh) * | 2008-08-05 | 2012-11-21 | 华为技术有限公司 | 移动性管理处理方法、系统和设备 |
| IN2011KN03309A (zh) | 2009-01-09 | 2015-07-10 | Ericsson Telefon Ab L M | |
| CN101720090B (zh) * | 2009-06-16 | 2015-06-03 | 中兴通讯股份有限公司 | 一种实现家用基站远程访问控制的方法及装置 |
| CN102833879B (zh) * | 2009-08-28 | 2015-02-25 | 华为技术有限公司 | 释放连接的方法、装置及系统 |
| EP2477441B1 (en) * | 2009-09-18 | 2014-05-21 | NEC Corporation | Communication system and communication controlling method |
| WO2011038359A2 (en) * | 2009-09-26 | 2011-03-31 | Cisco Technology, Inc. | Providing services at a communication network edge |
| EP2317822A1 (en) * | 2009-10-29 | 2011-05-04 | Panasonic Corporation | Enhancement of the attachement procedure for re-attaching a UE to a 3GPP access network |
| EP2628337B1 (en) * | 2010-10-13 | 2019-08-28 | Telefonaktiebolaget LM Ericsson (publ) | Method in a network node for selecting a gateway in a wireless communications network |
| CN102868994A (zh) * | 2011-07-08 | 2013-01-09 | 北京三星通信技术研究有限公司 | 一种支持用户设备ue移动性的方法 |
| CN102238671B (zh) * | 2011-07-28 | 2014-09-10 | 京信通信系统(中国)有限公司 | Femto网关及其对切换相关信令的处理方法 |
| US8982841B2 (en) * | 2011-10-27 | 2015-03-17 | Spidercloud Wireless, Inc. | Long term evolution architecture and mobility |
| US9144102B2 (en) * | 2013-04-01 | 2015-09-22 | Blackberry Limited | Deactivating or maintaining a packet data network connection |
| CN104185209B (zh) * | 2013-05-24 | 2019-11-19 | 中兴通讯股份有限公司 | 一种小蜂窝基站接入系统及其实现网络接入的方法 |
| CN104469852B (zh) * | 2013-09-13 | 2019-10-11 | 北京三星通信技术研究有限公司 | 建立本地分流承载的方法和设备 |
| US9253810B2 (en) * | 2013-11-21 | 2016-02-02 | Cisco Technology, Inc. | Localizing a mobile data path in a radio access network under control of a mobile packet core in a network environment |
| US9900801B2 (en) * | 2014-08-08 | 2018-02-20 | Parallel Wireless, Inc. | Congestion and overload reduction |
| EP3171635B1 (en) | 2014-08-19 | 2020-11-11 | Huawei Technologies Co., Ltd. | Path switching method, mobile anchor point and base station |
| US10084728B2 (en) * | 2015-05-11 | 2018-09-25 | Futurewei Technologies, Inc. | Localized traffic flow management in a wireless network |
| JP6650535B2 (ja) * | 2016-04-05 | 2020-02-19 | 華為技術有限公司Huawei Technologies Co.,Ltd. | モバイル協働型コミュニケーション方法及び装置 |
| WO2018045501A1 (zh) * | 2016-09-07 | 2018-03-15 | 华为技术有限公司 | 本地分组数据网络的动态创建方法、装置及系统 |
-
2016
- 2016-08-26 EP EP16913885.6A patent/EP3500043A4/en not_active Withdrawn
- 2016-08-26 WO PCT/CN2016/096998 patent/WO2018035864A1/zh not_active Ceased
- 2016-08-26 CN CN201680088743.6A patent/CN109644384B/zh not_active Expired - Fee Related
-
2019
- 2019-02-26 US US16/285,898 patent/US11064551B2/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104105143A (zh) * | 2013-04-03 | 2014-10-15 | 北京三星通信技术研究有限公司 | 一种支持sipto业务的方法 |
| CN104349405A (zh) * | 2013-07-23 | 2015-02-11 | 华为技术有限公司 | 传输数据的方法、通信节点和基站 |
| CN104618849A (zh) * | 2013-11-01 | 2015-05-13 | 中兴通讯股份有限公司 | 终端的本地交换方法及系统 |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP3500043A4 * |
Also Published As
| Publication number | Publication date |
|---|---|
| US20190191479A1 (en) | 2019-06-20 |
| US11064551B2 (en) | 2021-07-13 |
| CN109644384B (zh) | 2021-02-05 |
| CN109644384A (zh) | 2019-04-16 |
| EP3500043A1 (en) | 2019-06-19 |
| EP3500043A4 (en) | 2019-09-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10911990B2 (en) | Network handover method and related device | |
| US10873886B2 (en) | Mobile edge platform switching method, apparatus, and system | |
| CN110149665B (zh) | 一种网元的选择方法及装置 | |
| CN103906262B (zh) | 一种承载分配方法及用户设备、基站和服务网关 | |
| AU2021266341A1 (en) | Session processing method, device, and system | |
| KR102343934B1 (ko) | 소형 셀 시스템에서 데이터 전달 방법 | |
| US20160174285A1 (en) | Method for maintaining service continuity in heterogeneous communications system | |
| CN110650468B (zh) | 一种小小区架构中支持业务本地分流的方法、系统和设备 | |
| WO2018145669A1 (zh) | 一种业务分流实现方法及装置 | |
| BR112021005779A2 (pt) | rede de acesso por rádio e métodos para acesso a rede agilizado | |
| CN111465064A (zh) | 一种切换装置及方法 | |
| KR20210024160A (ko) | 통신 방법 및 장치 | |
| CN111654923A (zh) | 一种通信控制的方法及相关网元 | |
| WO2014086280A1 (zh) | 处理无线网络用户接入的方法、装置及系统 | |
| EP3886500B1 (en) | Mobility management method and apparatus | |
| CN105874756B (zh) | 控制信令的传输方法及设备 | |
| WO2015089791A1 (zh) | 一种载波聚合的实现方法和装置及系统 | |
| CN110636639A (zh) | 一种会话管理方法及装置 | |
| CN110138885A (zh) | 地址分配方法及装置 | |
| US11019546B2 (en) | Switching of uplink user plane termination point of a serving gateway for a bearer in dual connectivity operation | |
| WO2016180018A1 (zh) | 一种接入方法及相应的接入节点、终端和通信网络 | |
| US11064551B2 (en) | Network management method and controller | |
| WO2020173146A1 (zh) | 一种切换处理的方法、相关设备、程序产品以及存储介质 | |
| WO2018045515A1 (zh) | 一种数据分流方法及相关装置 | |
| WO2016173283A1 (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: 16913885 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| ENP | Entry into the national phase |
Ref document number: 2016913885 Country of ref document: EP Effective date: 20190312 |


