WO2018058682A1 - 一种业务传输方法、设备及*** - Google Patents
一种业务传输方法、设备及*** Download PDFInfo
- Publication number
- WO2018058682A1 WO2018058682A1 PCT/CN2016/101404 CN2016101404W WO2018058682A1 WO 2018058682 A1 WO2018058682 A1 WO 2018058682A1 CN 2016101404 W CN2016101404 W CN 2016101404W WO 2018058682 A1 WO2018058682 A1 WO 2018058682A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network element
- user plane
- plane network
- tunnel endpoint
- resource management
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/22—Manipulation of transport tunnels
-
- 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/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5061—Pools of addresses
-
- 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/08—Access point devices
-
- 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
- H04L2012/4629—LAN interconnection over a backbone network, e.g. Internet, Frame Relay using multilayer switching, e.g. layer 3 switching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/668—Internet protocol [IP] address subnets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a service transmission method, device, and system.
- the user equipment (English: User Equipment, UE) accesses the mobile communication network through a local wireless access network
- the control plane English: Control Plane, CP, or
- the core control function (CCF) network element is responsible for connection management, security authentication, mobility management, and location management of user equipment.
- User planes (English: User Plane, UP) are responsible for forwarding user service data.
- the user plane network element responsible for forwarding user service data in Figure 1 may be faulty. In this case, a method is needed to prevent the user service data from being affected in the case of a user plane network element failure. transmission.
- the user plane network element of the next-generation mobile communication network is faulty, it is usually referred to the processing method of the data gateway (English: Packet Data Network Gateway, P-GW) in the fourth generation (English: 4Generation, 4G) communication network.
- P-GW Packet Data Network Gateway
- 4G 4Generation, 4G
- the control plane network element 2 includes: 1) when the control plane network element detects that the user plane network element 1 is faulty, the affected user equipment is notified, and the user equipment is notified to re-establish the data connection; 2) the user equipment receives After the notification of the control plane network element, a connection establishment request is initiated, requesting to re-establish the data connection; 3) after receiving the request of the user equipment, the control plane network element selects a new user plane network element 2 to establish a data connection; 4) the user plane The network element 2 replies to the connection establishment response, and allocates a network protocol (English: Internet Protocol, IP) address to the user equipment; 5) the control plane network element replies to the user equipment with a connection establishment response. In this way, the user equipment establishes a data connection on the new user plane network element, and the new user plane network element forwards the service data of the user equipment.
- a network protocol English: Internet Protocol, IP
- the user equipment can establish a data connection with other user plane network elements to ensure normal transmission of user service data.
- the IP address of the user equipment that communicates with the application is redistributed because the user plane network element is temporarily unavailable to forward the user service data and the data connection is established. This will cause the service interruption of the user equipment and affect the user's business experience.
- the present application provides a service transmission method, device, and system to solve the problem of service interruption of a user equipment caused by a user plane network element failure.
- the present invention provides a service transmission method, which is performed by a resource management node, and may include: acquiring a user equipment IP address pool, and dividing the user equipment IP address pool into at least one user equipment IP address segment, according to at least one The user equipment IP address segment determines at least one tunnel endpoint identifier index, and allocates at least one user equipment IP address segment and at least one tunnel endpoint identifier index to the at least one user plane network element.
- the IP address pool of the user equipment is referred to as the IP address pool.
- the IP address segment of the user equipment is referred to as the IP address segment.
- the IP address and the tunnel endpoint identifier are managed by the newly added resource management node in the network, and the correspondence between the tunnel endpoint identifier index, the user equipment IP address segment, and the user plane network element is maintained, and the user equipment IP address, tunnel endpoint identifier, and There is no necessary binding relationship between the user plane network elements.
- the resource management node can dynamically adjust the user equipment IP address, tunnel endpoint identifier, and user plane network according to the conditions in the network (such as user plane network element fault/overload). In the case of the meta-relationship, the user service data is forwarded through the new user plane network element without changing the user equipment IP address and the tunnel endpoint identifier.
- the user equipment and the user plane network element are not required to re-establish the data connection, and the user equipment is avoided.
- the method does not need to perform the configuration of the service data forwarding on the user plane network element, simplifies the configuration of the user plane network element, and realizes the configuration of the user plane network element, thereby supporting the plug and play of the user plane network element.
- the method may further include:
- the resource management node notifies the correspondence between the IP address segment and the user plane network element And notifying the forwarding node, and notifying the correspondence between the tunnel endpoint identifier index and the user plane network element to the second forwarding node.
- the resource management node can directly notify the forwarding node of the corresponding relationship, and the forwarding node sends the service data of the user equipment to the corresponding user plane network element according to the corresponding relationship to implement the forwarding of the service data.
- the method may further include:
- the resource management node notifies the transmission control node of the correspondence between the IP address segment, the tunnel endpoint identifier index, and the user plane network element; the correspondence relationship is used to notify the transmission control node to notify the correspondence between the IP address segment and the user plane network element
- the first forwarding node notifies the second forwarding node of the correspondence between the tunnel endpoint identifier index and the user plane network element.
- the mapping between the IP address segment, the tunnel endpoint identifier, and the user plane NE refers to the mapping between the IP address segment, the tunnel endpoint identifier, and the user plane NE identifier.
- the user plane NE identifier includes the user plane NE. IP address, or the ID of the user plane network element.
- the resource management node may first notify the transmission control node of the correspondence between the IP address segment, the tunnel endpoint identifier index, and the user plane network element, and then the transmission control node notifies the corresponding node to the forwarding node, and the forwarding node responds according to the correspondence.
- the relationship sends the service data of the user equipment to the corresponding user plane network element to implement forwarding of the service data.
- the resource management node allocates at least one IP address segment and at least one tunnel endpoint identifier index to the at least one user plane network.
- the yuan can include:
- the resource management node allocates at least one IP address segment and at least one tunnel endpoint identifier to the at least one user plane network element according to the information of the user plane network element.
- the information of the user plane network element includes: the resource management node is located in the network. The number of user plane network elements and/or the capacity of the user plane network element.
- IP address segment and the tunnel endpoint identifier index determined according to the IP address segment are allocated to the same user plane network element.
- the IP address segments assigned by different user plane network elements are different.
- IP address segment and the tunnel endpoint identifier are allocated according to the number and capacity of the user plane network elements in the network, and load balancing of each user plane network element is implemented.
- the resource management node may allocate the divided at least one IP address segment and the at least one tunnel endpoint identifier index to the newly added user plane network element.
- the service of the user equipment is not interrupted, and the IP address and tunnel endpoint identifier associated with the user equipment are allocated to the newly added user plane network element, and at the same time, a new user is added to the network.
- the configuration of the network element is free of configuration, and the plug-and-play of the newly added user plane network element is achieved.
- the IP address segment and the tunnel corresponding to the user plane network element may be used.
- the endpoint identifier index is allocated to other available user plane network elements, and the service data is forwarded through other available user plane network elements.
- the first aspect or the first aspect is combined.
- the resource management node may obtain part or all of the IP address segments allocated to the first user plane network element, and use part or all of the IP address segments allocated to the first user plane network element as the IP address pool;
- the resource management node allocates at least one IP address segment and at least one tunnel endpoint identification index to at least one user plane network element other than the first user plane network element.
- the first user plane network element may be a user plane network element that is faulty or overloaded.
- the user equipment IP address segment and the tunnel endpoint identification index assigned to the faulty or overloaded user plane network element can be reassigned to other normal user plane network elements through the resource management node, so that the user plane network element fails/ In the case of overload or the like, the user plane network element that forwards the service data packet of the user equipment is changed without interrupting the service of the user equipment.
- the present invention provides a service transmission method, which is performed by a transmission control node, and the method may include: acquiring an IP address segment and a tunnel end sent by a resource management node Notifying the correspondence between the IP address segment and the user plane network element to the first forwarding node, and notifying the correspondence between the tunnel endpoint identifier index and the user plane network element to the corresponding relationship between the point identifier index and the user plane network element Two forwarding nodes.
- the mapping between the IP address segment, the tunnel endpoint identifier, and the user plane network element includes: an IP address segment, a tunnel endpoint identifier, and a user plane NE identifier; the user plane NE identifier includes the user plane network element. IP address, or the ID of the user plane network element.
- the resource management node may first notify the transmission control node of the correspondence between the IP address segment, the tunnel endpoint identifier index, and the user plane network element, and then the transmission control node notifies the corresponding node to the forwarding node, and the forwarding node responds according to the correspondence.
- the relationship sends the service data of the user equipment to the corresponding user plane network element to implement forwarding of the service data.
- the present invention provides a service transmission method, which is performed by a first forwarding node.
- the method may include: obtaining a correspondence between an IP address segment and a user plane network element, according to the IP address segment and the user plane network element.
- the correspondence between the two ends forwards the downlink service data sent by the packet data network to the user plane network element.
- the first forwarding node may be a forwarding node between the user plane network element and the packet data network in the network where the resource management node is located.
- the first forwarding node can forward the downlink service data sent by the received packet data network to the corresponding user plane network element according to the corresponding relationship acquired by the first forwarding node.
- the first forwarding node may directly obtain the correspondence between the IP address segment notified by the resource management node and the user plane network element; The correspondence between the IP address segment notified by the transmission control node and the user plane network element.
- the present invention provides a service transmission method, which is performed by a second forwarding node, and the method may include: obtaining a correspondence between a tunnel endpoint identifier index and a user plane network element, according to the tunnel endpoint identifier index and the user plane network.
- the correspondence between the elements forwards the uplink service data sent by the access network to the user plane network element.
- the second forwarding node can be implemented according to the corresponding relationship acquired by itself.
- the received uplink service data sent by the access network is forwarded to the corresponding user plane network element.
- the second forwarding node may directly obtain the correspondence between the tunnel endpoint identifier index notified by the resource management node and the user plane network element; Obtain a correspondence between the tunnel endpoint identifier index notified by the transmission control node and the user plane network element.
- the present invention provides a resource management node, where the resource management node includes:
- An obtaining unit configured to obtain an IP address pool
- a determining unit configured to divide the IP address pool obtained by the obtaining unit into at least one IP address segment, and determine at least one tunnel endpoint identifier index according to the at least one IP address segment;
- an allocating unit configured to allocate at least one IP address segment and the at least one tunnel endpoint identification index determined by the determining unit to the at least one user plane network element.
- the resource management node provided by the fifth aspect can achieve the same advantageous effects as the first aspect.
- the present invention provides a resource management node, where the resource management node includes:
- a transceiver for obtaining an IP address pool
- a processor configured to divide the IP address pool obtained by the transceiver into at least one IP address segment, and determine at least one tunnel endpoint identifier index according to the at least one IP address segment;
- the resource management node provided by the sixth aspect can achieve the same advantageous effects as the first aspect.
- the present invention provides a non-transitory computer readable storage medium storing one or more programs, the one or more programs including instructions, when included
- the resource management node described in the fifth aspect or the sixth aspect or any of the foregoing possible implementation manners is executed, the resource management node is caused to perform the following events:
- IP address pool Obtaining an IP address pool, dividing the IP address pool into at least one IP address segment, determining at least one tunnel endpoint identifier index according to at least one IP address segment, and assigning at least one IP address segment and at least one tunnel endpoint identifier index to at least one user plane Network element.
- the specific implementation manner of the seventh aspect may refer to the behavior function of the resource management node in the service transmission method provided by the first aspect or the possible implementation manner of the first aspect, and details are not repeatedly described herein. Therefore, the resource management node provided by the seventh aspect can achieve the same advantageous effects as the first aspect.
- the present invention provides a transmission control node, where the transmission control node includes: an acquisition unit, configured to acquire an IP address segment, a tunnel endpoint identifier index, and a correspondence between user plane network elements sent by the resource management node;
- a notification unit configured to notify the first forwarding node of the correspondence between the IP address segment acquired by the acquiring unit and the user plane network element, and notify the second forwarding node of the correspondence between the tunnel endpoint identifier index and the user plane network element .
- the specific implementation manner of the eighth aspect may refer to the behavior function of the transmission control node in the service transmission method provided by the second aspect or the possible implementation manner of the second aspect, and details are not repeatedly described herein. Therefore, the transmission control node provided by the eighth aspect can achieve the same advantageous effects as the second aspect.
- the present invention provides a transmission control node, where the transmission control node includes: a transceiver, configured to acquire an IP address segment, a tunnel endpoint identification index, and a correspondence between user plane network elements sent by the resource management node;
- the specific implementation manner of the ninth aspect may refer to the behavior function of the transmission control node in the service transmission method provided by the second aspect or the possible implementation manner of the second aspect, and details are not repeatedly described herein. Therefore, the transmission control node provided by the ninth aspect can achieve the same advantageous effects as the second aspect.
- the present invention provides a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, when included in the eighth aspect or the ninth aspect or any of the above
- the transmission control node is caused to perform the following events:
- the specific implementation manner of the tenth aspect may refer to the behavior function of the transmission control node in the service transmission method provided by the second aspect or the possible implementation manner of the second aspect, and details are not repeatedly described herein. Therefore, the transmission control node provided by the tenth aspect can achieve the same advantageous effects as the second aspect.
- the present invention provides a first forwarding node, where the first forwarding node includes: an obtaining unit, configured to acquire a correspondence between an IP address segment and a user plane network element;
- the sending unit is configured to forward the downlink service data sent by the packet data network to the user plane network element according to the correspondence between the IP address segment acquired by the acquiring unit and the user plane network element.
- the specific implementation manner of the eleventh aspect may refer to the behavior function of the first forwarding node in the service transmission method provided by the third aspect or the possible implementation manner of the third aspect, and details are not repeatedly described herein. Therefore, the first forwarding node provided by the eleventh aspect can achieve the same advantageous effects as the third aspect.
- the present invention provides a first forwarding node, where the first forwarding node includes: a transceiver, configured to obtain a correspondence between an IP address segment and a user plane network element;
- the specific implementation manner of the twelfth aspect may refer to the behavior function of the first forwarding node in the service transmission method provided by the third aspect or the possible implementation manner of the third aspect, and details are not repeatedly described herein. Therefore, the first forwarding node provided by the twelfth aspect can achieve the same advantageous effects as the third aspect.
- the present invention provides a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, when included in the eighth aspect or the ninth aspect or
- the first forwarding node is caused to perform the following events:
- the specific implementation manner of the thirteenth aspect may refer to the behavior function of the first forwarding node in the service transmission method provided by the third aspect or the possible implementation manner of the third aspect, and details are not repeatedly described herein. Therefore, the first forwarding node provided by the thirteenth aspect can achieve the same advantageous effects as the third aspect.
- the present invention provides a second forwarding node, where the second forwarding node may include: an acquiring unit, configured to acquire a correspondence between a tunnel endpoint identifier and a user plane network element;
- the sending unit is configured to forward the uplink service data sent by the access network to the user plane network element according to the correspondence between the tunnel endpoint identifier index and the user plane network element acquired by the acquiring unit.
- the specific implementation manner of the fourteenth aspect may refer to the behavior function of the second forwarding node in the service transmission method provided by the fourth aspect or the possible implementation manner of the fourth aspect, and details are not repeatedly described herein. Therefore, the second forwarding node provided by the fourteenth aspect can achieve the same advantageous effects as the fourth aspect.
- the present invention provides a second forwarding node, where the second forwarding node may include: a transceiver, configured to acquire a correspondence between a tunnel endpoint identifier and a user plane network element;
- the specific implementation manner of the fifteenth aspect may refer to the behavior function of the second forwarding node in the service transmission method provided by the fourth aspect or the possible implementation manner of the fourth aspect, and details are not repeatedly described herein. Therefore, the second forwarding node provided in the fifteenth aspect may In order to achieve the same beneficial effects as the fourth aspect.
- the present invention provides a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, when included in the eighth or ninth aspect or
- the second forwarding node is configured to perform the following events:
- the specific implementation manner of the sixteenth aspect may refer to the behavior function of the second forwarding node in the service transmission method provided by the fourth aspect or the possible implementation manner of the fourth aspect, and details are not repeatedly described herein. Therefore, the second forwarding node provided by the sixteenth aspect can achieve the same advantageous effects as the fourth aspect.
- the present invention provides a service transmission system, comprising the resource management node according to the fifth aspect or the sixth aspect or the seventh aspect or any one of the foregoing aspects, such as the eighth aspect or the ninth aspect or the tenth
- the transmission control node according to any one of the preceding aspects, the first forwarding node according to the eleventh or twelfth aspect or the thirteenth aspect or any one of the foregoing, the fourteenth aspect or the fifteenth
- the service transmission system provided in the seventeenth aspect can implement the service transmission method shown above, and therefore, the same advantageous effects as the above-described service transmission method can be achieved.
- FIG. 1 is a schematic diagram of a structure of a conventional next generation mobile communication network
- FIG. 2 is a schematic diagram of a process for resetting a user plane network element
- FIG. 3 is a schematic structural diagram of a next-generation mobile communication network according to an embodiment of the present invention.
- FIG. 4 is a structural diagram of a resource management node according to an embodiment of the present invention.
- FIG. 5 is a flowchart of a service transmission method according to an embodiment of the present invention.
- FIG. 6 is a flowchart of still another service transmission method according to an embodiment of the present invention.
- FIG. 7 is a flowchart of still another service transmission method according to an embodiment of the present invention.
- FIG. 8 is a flowchart of still another service transmission method according to an embodiment of the present invention.
- FIG. 9 is a structural diagram of a resource management node 10 according to an embodiment of the present invention.
- FIG. 10 is a structural diagram of a transmission control node 20 according to an embodiment of the present invention.
- FIG. 11 is a structural diagram of a first forwarding node 30 according to an embodiment of the present invention.
- FIG. 12 is a structural diagram of a second forwarding node 40 according to an embodiment of the present invention.
- FIG. 13 is a structural diagram of a service transmission system according to an embodiment of the present invention.
- the principle of the present invention is: adding a resource management node in the original network architecture, segmenting multiple tunnel endpoint identifiers and multiple user equipment IP addresses through the resource management node, and segmenting the tunnel endpoint identifier index and The user equipment IP address segment is allocated to the user plane network element, and the corresponding relationship between the tunnel endpoint identifier index, the user equipment IP address segment, and the user plane network element is notified to the transmission control node, and the transmission control node notifies the forwarding node, so that The forwarding node forwards the service data including the tunnel endpoint identifier or the service data including the user equipment IP address to the corresponding user plane network element, and the user plane network element performs forwarding of the service data.
- the service transmission method of the present invention can be applied to the next generation mobile shown in FIG.
- a communication network (English: Next Generation Network, NGN), as shown in FIG. 3, the network may include: multiple forwarding nodes between the access network, the access network, and the user plane network element (eg, forwarding node 1, forwarding) Node 2), resource management node, transmission control node, control plane network element, multiple user plane network elements, multiple forwarding nodes between the user plane network element and the packet data network (eg, forwarding node 3, forwarding node 4) ), as well as the message data network.
- FIG. 3 is only a schematic diagram, and the nodes shown in FIG. 3 are only examples, and the number thereof is not limited to the solution described in this application, especially the forwarding node, and the number thereof is not limited to several shown in FIG. Different forwarding nodes different from those shown in FIG. 3 can be deployed in the network during actual deployment.
- the access network in FIG. 3 may be an enhanced long term evolution (eLTE) network, or a third generation partner program of the next generation network access network (English NextGen RAN).
- the 3rd Generation Partnership Project (3GPP) access network can also be an access network such as a Wireless Local Area Network (WLAN) or a fixed access.
- the forwarding node between the access network and the user plane network element (for example, the forwarding node 1 and the forwarding node 2) is mainly responsible for forwarding service data between the access network and the user plane network element, and the user plane network element and the packet data.
- the forwarding node between the network (for example, the forwarding node 3 and the forwarding node 4) is mainly responsible for forwarding the service data between the user plane network element and the packet data network, and the forwarding node may be a routing device such as a switch or a load balancing node.
- the transmission control node monitors the forwarding node to understand the network status and simultaneously schedules and controls the forwarding of traffic.
- the resource management node can be a management server, which is mainly responsible for segmenting the Internet Protocol (IP) address of the user equipment and the Tunnel Endpoint Identifier (TEID) to generate the user equipment address IP segment and the tunnel endpoint.
- IP Internet Protocol
- TEID Tunnel Endpoint Identifier
- the index is identified, and the correspondence between the user equipment IP address segment, the tunnel endpoint identifier index, and the user plane network element is established.
- the control plane network element and the user plane network element are introduced in Figure 1.
- the user plane network element is mainly responsible for forwarding user service data.
- the control plane network element is mainly responsible for connection management, security authentication, mobility management, and location management of user equipment.
- the control plane network element may be modularly split, and the split functional modules may be considered as independent network elements, for example, splitting the CP or CCF into sessions.
- Function modules such as session management (English: Session Management, SM) and mobility management (English: Mobily Management, MM). Under this logical architecture, the functions of the control plane network elements in the embodiment are managed by the session. :Session Management, SM) Execution.
- each forwarding node may be independent of other network elements in the network.
- Deployed in a transport network such as a switch, it can also be deployed in the core network independently of other network elements in the network, such as load balancing nodes. It can also integrate multiple forwarding nodes into existing nodes in the network to implement forwarding nodes.
- the forwarding node between the user plane network element and the packet data network can be integrated into the user plane network element, and the function of the forwarding node is performed by the user plane network element, which is not limited in this embodiment of the present invention.
- the resource management node can also be deployed in the network independently of other network elements in the network, and the resource management node can be integrated into an existing node (such as a control plane network element) in the network to implement the function of the resource management node.
- each node and network element in FIG. 3 may include: a processor, a memory, a communication unit, and at least one communication bus, wherein the communication bus is used to implement connection and mutual communication between the devices.
- the resource management node is taken as an example, and the components of the resource management node are specifically introduced in conjunction with FIG. 4, and the components of other nodes or network elements may refer to the resource management node, and details are not described herein again.
- the resource management node 10 can include a processor 1011, a memory 1012, a transceiver 1013, and at least one communication bus 1014 for implementing connections and mutual communication between the devices.
- the processor 1011 may be a central processing unit (CPU), a network processor (in English: network processor, NP), a hardware chip, or any combination thereof.
- the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
- ASIC application-specific integrated circuit
- PLD programmable logic device
- the above PLD can be a complex programmable logic device (English: complex programmable logic device, CPLD), field-programmable gate array (FPGA), general array logic (GAL) or any combination thereof.
- the memory 1012 may be a volatile memory (English: Volatile Memory), such as a random access memory (RAM), or a non-volatile memory (English: Non-volatile Memory), such as read only. Memory (English: Read-only Memory, ROM), flash memory (English: Flash Memory), hard disk (English: Hard Disk Drive, HDD) or solid state drive (English: Solid-state Drive, SSD); or the above types A combination of memories.
- the processor 1011 can implement various functions of the resource management node by running or executing program code stored in the memory 1012, as well as invoking data stored in the memory 1012.
- the transceiver 1013 can be used for data interaction with an external network element, and the transceiver 1013 can be an antenna.
- the communication bus 1014 can be divided into an address bus, a data bus, a control bus, etc., and can be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnection (English: Peripheral Component, PCI) bus, or an extended industry standard. Architecture (English: Extended Industry Standard Architecture, EISA) bus. For ease of representation, only one thick line is shown in Figure 4, but it does not mean that there is only one bus or one type of bus.
- Industry Standard Architecture ISA
- FIG. 5 is a flowchart of a service transmission method according to an embodiment of the present invention.
- the device in the network shown in Figure 3 is interactively executed.
- the method may include the following steps:
- Step S101 The resource management node acquires an IP address pool.
- the IP address pool may contain a large number of user equipment IP addresses (referred to as IP addresses), and the IP address segment may also contain multiple IP addresses, but the number of IP addresses included in the IP address segment may be much smaller than the IP address included in the IP address pool.
- IP addresses can be the IP address that the UE communicates with the message data network.
- the resource management node may be obtained from an operation and maintenance network element (English: Operation and maintenance, O&M).
- O&M Operation and maintenance
- Step S102 The resource management node divides the IP address pool into at least one IP address segment, and determines at least one tunnel endpoint identifier index according to the at least one IP address segment.
- the resource management node may divide multiple user equipment IP addresses in the user equipment IP address pool into multiple user equipment IP address segments as needed, for example, the number of IP addresses that can be included in the IP address segment may be preset.
- the user equipment IP address in the user equipment IP address pool is divided into a plurality of user equipment IP address segments according to the preset number, wherein the preset number can be set as needed, which is not performed by the embodiment of the present invention. limited.
- the user equipment IP address can be used.
- the IP address of the user equipment in the pool is divided into 1000 user equipment IP address segments, and each user equipment IP address segment contains 50,000 user equipment IP addresses.
- the IP address segment in the step S102 is in one-to-one correspondence with the tunnel endpoint identifier index.
- each IP address segment may be assigned an index, and the IP address segment is identified by the index.
- the index is placed in a number of bits of the tunnel endpoint identifier to generate a tunnel endpoint identifier index, so that the tunnel endpoint identifier index is determined according to the IP address segment, and the service data of any IP address included in the IP address segment needs to pass through the tunnel.
- the tunnel identified by the tunnel endpoint identifier contained in the endpoint identifier index is forwarded.
- association information may be allocated to the IP address segment, and the tunnel endpoint identifier index corresponding to the IP address segment is determined by using the association information, which is not limited by the present invention; This is not limited to the embodiment of the present invention.
- the IP address segment 10.184.228.0 to 10.184.228.255 is assigned to the user plane network element 1
- the index assigned to the IP segment is a binary number 0001
- the first bit to the 4th of the 16 bits of the tunnel endpoint identifier are specified.
- the bit is a bit for placing information associated with the IP address segment, and the tunnel endpoint identification index corresponding to the IP address segment assigned to the user plane network element 1 is 0001xxxxxxxxxxxx.
- the algorithm for the resource management node to allocate an index or other related information to the IP address segment is not limited in the present invention, but each IP address segment is required to have a unique index or associated information, and an index corresponding to the different IP address segments or The associated information is different.
- the tunnel endpoint identifier is used to identify a tunnel, and the tunnel is a channel between the access network and the user plane network element, and is used to forward service data between the access network and the user plane network element.
- the tunnel endpoint identifier may be assigned to any user plane network element, and the tunnel endpoint identifier is used to identify a tunnel of the access network and the user plane network element.
- the tunnel endpoint identifier A identifies a tunnel between the access network and the user plane network element 1
- the tunnel endpoint identifier A identifies a tunnel between the access network and the user plane network element 2.
- Step S103 The resource management node allocates at least one IP address segment and at least one tunnel endpoint identification index to at least one user plane network element.
- IP address segment and the tunnel endpoint identifier index determined according to the IP address segment are allocated to the same user plane network element, and one or more IP address segments that each user plane network element can be divided into, and different user plane network element assignments.
- the IP address segment is different.
- the resource management node allocates the tunnel endpoint identifier to the user plane network element, and the service data of the tunnel identified by the tunnel endpoint identifier included in the tunnel endpoint identifier index is forwarded to the packet data network through the user plane network element;
- the management node allocates an IP address segment to the user plane network element, it indicates that the service data sent by the packet data network to any IP address included in the IP address segment is forwarded to the UE through the user plane network element.
- the resource management node may allocate, according to the information of the user plane network element in the network shown in FIG. 3, at least one user equipment IP address segment and at least one tunnel endpoint identifier index to each user plane network element in the network.
- the information of the user plane network element may include: the number of user plane network elements, or the user plane network element capacity, or the number of user plane network elements and the user plane network element capacity.
- the resource management node may uniformly allocate at least one user equipment IP address segment to each user plane network element in the network according to the information of the user plane network element, and may further at least one according to different user plane network element capacity levels.
- the user equipment IP address segment is allocated to each user plane network element in the network.
- the resource management node can divide 1000 user equipment IP address segments into user plane network elements according to the number of user plane network elements. For example, if there are 10 user plane network elements, each user plane network element is allocated to 100 users.
- the IP address segment of the device for example, the resource management node may allocate 1000 user equipment IP address segments to each user plane network element according to the capacity of each user plane network element, wherein the user plane network element with higher capacity is allocated.
- Multiple user equipment IP address segments, lower-capacity user plane network elements allocate fewer user equipment IP address segments, for example, there are 30 user plane network elements, of which 10 user plane network elements have the same capacity, and another 20 users
- the capacity of the surface network element is the same. The capacity of the former is twice that of the latter.
- For each of the 10 user plane network elements 50 user equipment IP address segments are allocated, and for the other 20 user plane network elements, 25 users are allocated.
- Device IP address segment for each of the 10 user plane network elements, 50 user equipment IP address segments are allocated, and for the other 20 user plane network
- the user equipment IP address in the user equipment IP address pool may be divided into multiple user equipment IP address segments according to the information of the user plane network element, and the tunnel endpoint is determined according to the IP address segment.
- the identifier is indexed, and the IP address segment and the corresponding tunnel endpoint identifier are assigned to each user plane network element.
- the resource management node can evenly divide the IP address in the IP address pool of the user equipment into the number of copies corresponding to the number of user plane NEs according to the number of user plane NEs; or the resource management node according to the capacity of the network element of different user planes
- the IP address in the IP address pool is divided into the number of copies corresponding to the number of user plane NEs, and the user plane NEs with high capacity are allocated more user equipment IP addresses.
- Step S104 The resource management node notifies the first forwarding node of the correspondence between the IP address segment assigned to the user plane network element and the user plane network element, and the first forwarding node receives the IP of the user plane network element notified by the resource management node.
- the correspondence between the address segment and the user plane network element is not limited to the resource management node.
- the first forwarding node may be any forwarding node located between the user plane network element and the packet data network in the network where the resource management node is located. As shown in Figure 3, forwarding node 3 and forwarding node 4.
- Step S105 The resource management node notifies the second forwarding node of the correspondence between the tunnel endpoint identifier index assigned to the user plane network element and the user plane network element, and the second forwards the tunnel of the user plane network element notified by the receiving resource management node. Correspondence between the endpoint identification index and the user plane network element.
- the second forwarding node may be any forwarding node located between the access network and the user plane network element in the network where the resource management node is located. As shown in Figure 3, forwarding node 1 or forwarding node 2.
- step S104 and step S105 may be changed, may be performed simultaneously, or may be performed sequentially without depending on the order in FIG. 5.
- the resource management node may between the IP address segment, the tunnel endpoint identifier index, and the user plane network element.
- the corresponding relationship is notified to the transmission control node, and the correspondence between the IP address segment allocated to the user plane network element and the user plane network element is notified to the first forwarding node and the network element to be allocated to the user plane network element by the transmission control node.
- the correspondence between the tunnel endpoint identifier index and the user plane network element is notified to the second forwarding node.
- the corresponding relationship between the IP address segment of the transmission control node, the tunnel endpoint identifier index, and the user plane network element is notified to the corresponding relationship between the IP address segment of the first forwarding node and the user plane network element, and the notification is notified.
- Step 106 The second forwarding node forwards the uplink service data sent by the access network to the user plane network element according to the correspondence between the tunnel endpoint identifier and the user plane network element.
- Step 107 The first forwarding node forwards the downlink service data sent by the packet data network to the user plane network element according to the correspondence between the IP address segment and the user plane network element.
- the service data sent from the UE to the packet data network is referred to as uplink service data
- the service data sent from the packet data network to the UE is referred to as downlink service data.
- the configuration of the service data forwarding on the user plane network element is not required, and there is no necessary binding relationship between the user equipment IP address and the user plane network element.
- the resource management node manages the user equipment IP address and the tunnel endpoint identifier, and maintains the correspondence between the tunnel endpoint identifier index, the user equipment IP address segment, and the user plane network element, and notifies the corresponding relationship to the forwarding through the transmission control node.
- the node sends the service data of the user equipment to the corresponding user plane network element according to the corresponding relationship to implement the forwarding of the service data.
- the resource management node can dynamically adjust the correspondence according to the situation in the network, and keep the user equipment in the IP.
- the user service data is forwarded through the new user plane network element.
- the user equipment is not required to re-establish a data connection with the user plane network element, thereby avoiding the problem of service interruption of the user equipment.
- the method can simplify the user plane network element. Configure to implement configuration-free configuration of user plane NEs to support plug-and-play of user plane NEs.
- FIG. 5 can be applied to network initialization, user plane network element reset/overload, or any scenario in which a user plane network element is added, to implement the user plane free configuration, and reset/overload/ Add business continuity under the scenario.
- FIG. 6 is a flowchart of a service transmission method according to an embodiment of the present invention, which is performed by a device in the network shown in FIG. 3, and is used for each user plane network element in the network shown in FIG. 3 during network initialization.
- the resource management node obtains an IP address pool from the O&M.
- the resource management node divides the IP address pool into at least one IP address segment, and determines at least one tunnel endpoint identifier index according to the at least one IP address segment.
- Step S201 is the same as step S102, and details are not repeated herein.
- S202 The resource management node allocates an IP address segment and a tunnel endpoint identifier index to each user plane network element shown in FIG. 3.
- step S202 is the same as the process of the step S103, and the details are not repeated here.
- S203 The resource management node notifies each user plane network element, the assigned user equipment IP address segment and the tunnel endpoint identifier index.
- the resource management node may directly notify each user plane network element, the assigned IP address segment and the tunnel endpoint identifier index, and may also notify each user plane network element by using the control plane network element, and the assigned IP address segment. And the tunnel endpoint identification index.
- step S203 may or may not be performed, that is, the user equipment IP address segment and the tunnel endpoint identifier index allocated by the user plane network element may be known or unknown to the user plane network element. It is possible, and the present invention does not limit this.
- the resource management node notifies the forwarding node 3 of the correspondence between the user plane network element and the IP address segment, and notifies the forwarding node 1 of the correspondence between the user plane network element and the tunnel endpoint identifier index.
- the resource management node can also notify the forwarding node 4 of the correspondence between the user plane network element and the IP address segment, and notify the forwarding node 2 of the correspondence between the user plane network element and the tunnel endpoint identifier index, or the user.
- the correspondence between the surface network element and the IP address segment is simultaneously notified to the forwarding nodes 1 and 4, and the correspondence between the user plane network element and the tunnel endpoint identifier index is simultaneously notified to the forwarding nodes 1 and 2.
- the embodiment of the present invention does not limit this.
- the present invention notifies the forwarding node 3 of the correspondence between the user plane network element and the IP address segment, and notifies the forwarding node 1 of the correspondence between the user plane network element and the tunnel endpoint identifier index.
- the resource management node may directly pair the user plane network element and the IP address segment.
- the forwarding node 3 is notified of the relationship, and the correspondence between the user plane network element and the tunnel endpoint identifier index is notified to the forwarding node 1.
- the corresponding relationship between the user plane network element, the user equipment IP address segment, and the tunnel endpoint identifier index may be notified to the transmission control node, where the corresponding relationship is the identifier of each user plane network element, and the user equipment IP to which it is assigned.
- An address segment and a tunnel end identifier, where the user plane network element identifier may be a user plane network element IP address, or a user plane network element ID, such as information that can uniquely identify the user plane network element;
- the transmission control node After receiving the correspondence between the user plane network element, the user equipment IP address segment, and the tunnel endpoint identifier index sent by the resource management node, the transmission control node notifies the forwarding node 3 of the correspondence between the user plane network element and the IP address segment, and The correspondence between the user plane network element and the tunnel endpoint identifier index is notified to the forwarding node 1.
- S205 The UE sends a connection establishment request to the control plane network element, where the connection establishment request is used to establish a connection with the packet data network.
- the UE may send a connection establishment request to the control plane network element through the access network.
- connection establishment request After the control plane network element receives the connection establishment request, if the user plane network element 1 is determined to forward the service data between the UE and the packet data network, the tunnel endpoint identifier of the user plane network element 1 is allocated to the access network. And returning a connection establishment response message to the UE, where the connection establishment response message includes an IP address allocated by the control plane network element to the UE.
- the UE is established through the connection channel between the user plane network element 1 and the packet data network. After the control plane network element completes the connection establishment, step S207 is performed.
- the tunnel endpoint identifier of the user plane network element 1 is included in the tunnel endpoint identifier included in the tunnel endpoint identifier index allocated by the resource management node for the user plane network element 1.
- a tunnel endpoint identifier may be randomly specified in the tunnel endpoint identifier index allocated by the resource management node for the user plane network element 1, and the tunnel endpoint identifier is used as the tunnel endpoint identifier of the user plane network element 1 of the connection that the UE requests to establish.
- the tunnel endpoint identifier of the user plane network element 1 can be used to identify a unique tunnel of the user plane network element 1.
- the control plane network element selects the user plane network element 1 to forward the service data of the connection 1, and the resource management node includes the tunnel endpoint identifier index allocated to the user plane network element 1 50 tunnel endpoint identifiers, then The tunnel endpoint identifier is selected from the endpoint identifiers of the 50 tunnels, and the selected tunnel endpoint identifier is used as the tunnel endpoint identifier of the user plane network element 1.
- the IP address of the UE is included in the IP address segment allocated by the resource management node for the user plane network element 1; optionally, the control plane network element may be randomly selected from the IP address segment allocated by the resource management node for the user plane network element 1 Select an IP address as the IP address of the UE.
- each user plane network element may be divided into multiple user equipment IP address segments, and multiple tunnel endpoint identifier indexes determined according to multiple user equipment IP address segments.
- a user equipment IP address segment and a tunnel endpoint identification index determined according to it are referred to as a pair relationship.
- the tunnel endpoint identifier of the user plane network element 1 and the IP address of the UE are allocated in this step, the tunnel endpoint identifier index including the tunnel endpoint identifier, and the user equipment IP address segment including the IP address of the UE are in a pair relationship. .
- the tunnel endpoint identifier of the user plane network element 1 may be directly allocated to the access network by the control plane network element. And assigning an IP address to the UE; otherwise, if the control plane network element and the resource management node are separate functional network elements, the tunnel endpoint identifier of the user plane network element 1 is allocated to the access network, and the function of assigning an IP address to the UE may be Executed by the resource management node, for example, the control plane network element may request the resource management node to request the tunnel endpoint identifier of the user plane network element 1 and the IP address of the UE, and the resource management node allocates the tunnel endpoint identifier of the user plane network element 1 to the resource management node. The network is assigned, and the IP address is allocated to the UE.
- the method for allocating the resource management network element is the same as the method for assigning the network element of the control plane.
- the control plane network element notifies the user plane network element 1 of the established connection context, where the connection context includes the tunnel endpoint identifier of the user plane network element 1 allocated to the access network and the IP address allocated to the UE.
- S208 The UE sends uplink service data to the access network.
- the access network After receiving the uplink service data, the access network encapsulates the tunnel end identifier of the user plane network element 1 in the uplink service data, and sends the encapsulated uplink service data to the forwarding node 1.
- the forwarding node 1 After receiving the uplink service data, the forwarding node 1 obtains the data according to step 204. The corresponding relationship between the user plane network element and the tunnel endpoint identifier index and the tunnel endpoint identifier in the uplink service data are sent to the user plane network element 1 for uplink service data.
- the forwarding node 1 may query the correspondence between the user plane network element and the tunnel endpoint identifier index, and find the user plane network element corresponding to the tunnel endpoint identifier index of the tunnel endpoint identifier in the uplink service data, that is, the user plane network element. 1. Send uplink service data to the user plane network element 1.
- the user plane network element 1 After receiving the uplink service data, the user plane network element 1 matches the information of the tunnel endpoint identifier in the uplink service data to the connection context, decapsulates the protocol layer including the tunnel endpoint identifier, and forwards the uplink service data to the packet. Data network.
- the user plane network element 1 receives the uplink service data, the information such as the tunnel endpoint identifier in the uplink service data does not match the connection context, and the uplink service data is not forwarded to the packet data network.
- the UE may also receive downlink service data sent by the packet data network, as shown in FIG. 6 :
- the packet data network sends downlink service data to the forwarding node 3, where the downlink service data includes an IP address of the UE.
- the forwarding node 3 After receiving the downlink service data, the forwarding node 3 sends the downlink service data to the user plane network element 1 according to the correspondence between the user plane network element and the IP address segment obtained in step 104 and the IP address of the UE in the downlink service data. .
- the forwarding node 3 can query the corresponding relationship between the user plane network element and the IP address segment, and find the user plane network element corresponding to the IP address segment where the IP address of the UE is located in the downlink service data, that is, the user plane network element 1,
- the downlink service data is sent to the user plane network element 1.
- the user plane network element 1 After receiving the downlink service data, the user plane network element 1 matches the information of the IP address of the UE in the downlink service data to the connection context, and forwards the downlink service data to the UE according to the information in the connection context.
- the downlink service data is not forwarded to the access network.
- the service data of the UE can be realized by the user plane through the scheme shown in FIG. 6.
- NE 1 forwards.
- the resource management node may reassign the user equipment IP address segment and the tunnel endpoint identifier index originally assigned to the user plane node 1 by using the user equipment IP address segment of the user plane node 1 as the address pool for segmentation reallocation.
- the user equipment IP address segment and the tunnel endpoint identification index of all or part of the user plane node 1 are reassigned to other normal user plane nodes.
- the implementation process is as shown in FIG. 7:
- the resource management node detects that the user plane network element 1 is faulty.
- the fault of the user plane network element 1 may be the user plane network element 1 or may be overloaded for the user plane network element 1.
- the specific detection method is not limited in the embodiment of the present invention, and may be controlled by the network element of the plane.
- the other nodes are aware that the user plane network element 1 is faulty, and the user plane network element 1 may be faulty through the detection and monitoring between the resource management node and the user plane network element 1.
- the overload of the user plane network element 1 may be: the load on the user plane network element 1 (such as the number of accessed service data packets) is greater than or equal to a preset threshold, or the central processing unit on the user plane network element 1 (English: Central The load of the processing unit (CPU) is greater than or equal to the preset threshold, or the memory consumption on the user plane network element 1 is greater than or equal to the preset threshold.
- the preset threshold may be set as needed, which is not limited in this embodiment of the present invention.
- the resource management node divides the IP address segment originally allocated to the user plane network element 1 into an IP address pool, divides the IP address pool into at least one IP address segment, and determines at least one tunnel endpoint identifier index according to at least one IP address segment. .
- the resource management node may re-divide the IP address segment originally allocated to the user plane network element 1 into at least one IP address segment by using the same steps as the step S102, and determine at least one tunnel endpoint identifier index according to the at least one IP address segment. process.
- the resource management node may not perform the re-segmentation of the IP address segment, and directly obtain the already-divided IP address segment of the user plane network element 1 and the tunnel endpoint identifier index corresponding to the IP address segment as at least one IP address. Segment and at least one tunnel end Point identification index.
- the resource management node allocates at least one IP address segment and at least one tunnel endpoint identifier index in step S302 to other user plane network elements except the user plane node 1 in FIG.
- At least one IP address segment and at least one tunnel endpoint identifier may be reassigned to the user plane network element 2, the user plane network element 3, and the user plane network element 4.
- the allocation process in step S303 is the same as the process in step S103.
- the details of the user plane network elements other than the first user plane node may be one or more user plane network elements.
- the resource management node may reassign all IP address segments and tunnel endpoint identifier indexes of the user plane network element 1 to other normal user plane networks. yuan.
- the resource management node may allocate the partial IP address segment of the user plane network element 1 and the tunnel endpoint identifier index to other user plane network elements, so as to alleviate the overload state of the user plane network element 1.
- the resource management node notifies other user plane network elements, the assigned user equipment IP address segment and the tunnel endpoint identifier index.
- step S304 is the same as the process in step S203, and details are not repeated herein.
- the resource management node notifies the forwarding node 3 of the correspondence between the user plane network element and the IP address segment, and notifies the forwarding node 1 of the correspondence between the user plane network element and the tunnel endpoint identifier index.
- the resource management node may directly notify the forwarding node 3 of the correspondence between the user plane network element and the IP address segment, and notify the forwarding node 1 of the correspondence between the user plane network element and the tunnel endpoint identifier index.
- the corresponding relationship between the user plane network element, the user equipment IP address segment, and the tunnel endpoint identifier index may be notified to the transmission control node, where the corresponding relationship is the identifier of each user plane network element, and the user equipment IP to which it is assigned.
- An address segment and a tunnel endpoint identifier, where the user plane network element identifier may be a user plane network element IP address or a user plane network element ID Information that uniquely identifies the user plane network element;
- the transmission control node After receiving the correspondence between the user plane network element, the user equipment IP address segment, and the tunnel endpoint identifier index sent by the resource management node, the transmission control node notifies the forwarding node 3 of the correspondence between the user plane network element and the IP address segment, and The correspondence between the user plane network element and the tunnel endpoint identifier index is notified to the forwarding node 1.
- step S305 is the same as the process in step S204, and details are not repeated herein.
- the resource management node notifies the control plane network element of the correspondence between the IP address segment, the tunnel endpoint identifier index, and the user plane network element.
- step S305 and step S306 may be changed, and does not depend on the order in the figure.
- S307 The UE sends uplink service data to the access network.
- the access network After receiving the uplink service data, the access network encapsulates the tunnel end identifier of the user plane network element 1 in the uplink service data, and sends the encapsulated uplink service data packet to the forwarding node 1.
- the user plane network element 2 After receiving the uplink service data, the user plane network element 2 matches the information of the tunnel endpoint identifier in the uplink service data to the connection context, decapsulates the protocol layer including the tunnel endpoint identifier, and forwards the uplink service data to the packet. Data network.
- the UE may also receive downlink service data sent by the packet data network, as shown in FIG. 5:
- the packet data network sends downlink service data to the forwarding node 3, where the downlink service data includes an IP address of the UE.
- the user plane network element 2 After receiving the downlink service data packet, the user plane network element 2 matches the information of the IP address of the UE in the downlink service data to the connection context, and forwards the downlink service data to the UE according to the information in the connection context.
- connection context in step S310 and step S313 can be obtained in the following two ways:
- the control plane network element After receiving the corresponding relationship between the IP address segment, the tunnel endpoint identifier index, and the user plane network element, the control plane network element sends the affected connection context to the new user plane network element.
- the affected connection context is the connection context originally established in the user plane network element 1, because the context-related user equipment IP address and the tunnel endpoint identifier are reassigned to the user plane network element 2, so the connection context is also Send to user plane network element 2.
- the user plane network element 2 After receiving the uplink service data, the user plane network element 2 cannot obtain the corresponding connection context according to the tunnel endpoint identifier, and the user plane network element 2 obtains the connection context from the control plane network element.
- the user plane network element 2 carries the tunnel endpoint identifier in the message and sends the message to the control plane network element.
- the control plane network element searches for the corresponding connection context according to the tunnel endpoint identifier, and sends the corresponding connection context to the user plane network element 2.
- the user plane network element 2 After receiving the downlink service data, the user plane network element 2 cannot query the corresponding connection context according to the information such as the IP address of the UE, and the user plane network element 2 acquires the connection context from the control plane network element.
- the user plane network element 2 carries the IP address of the UE in the message and sends the message to the control plane network element.
- the control plane network element searches for the corresponding connection context according to the IP address of the UE, and sends the corresponding connection context to the user plane network element 2.
- the resource management node reassigns the user equipment IP address segment and the tunnel endpoint identification index assigned to the faulty or overloaded user plane network element to other user plane network elements that communicate normally, and transmits the assigned correspondence relationship through the transmission.
- the control node notifies the forwarding node that the service data packet of the UE is forwarded by the new user plane network element according to the corresponding relationship, so that the service of the user equipment is not interrupted in the case of the user plane network element failure/overload. In the case of changing the service data packet of the forwarding user equipment User network element.
- the management node may reassign the user equipment IP address segment and the tunnel endpoint identification index originally assigned to the user plane nodes 1, 2, and 3 to the user plane network element 4.
- the resource management node may adopt A variety of principles redistribute user equipment IP address segments and tunnel endpoint identification indexes.
- the node with excessive load is selected, and the user equipment IP address segment and the tunnel endpoint identification index of the original user plane node are allocated to the newly added user plane node 4.
- the node with the smallest capacity is selected among the user plane nodes 1, 2, and 3.
- the user equipment IP address segment and the tunnel endpoint identification index of the original user plane node are allocated to the newly added user plane node 4.
- the technical solution provided by the embodiment of the present invention is introduced, for example, by assigning a part of the IP address segment and the tunnel end point identification index originally assigned to the user plane network element 1 to the newly added user plane network element 4.
- the method may include:
- the resource management node uses a partial IP address segment originally allocated to the user plane network element 1 as an IP address pool, divides the IP address pool into at least one IP address segment, and determines at least one tunnel endpoint identifier according to at least one IP address segment. index.
- the step S401 may re-divide the partial IP address segment originally allocated to the user plane network element 1 into at least one IP address segment by using the same process as step S102, and determine at least one tunnel endpoint according to the re-divided at least one IP address segment. Identification index.
- the resource management node may also perform the re-segmentation of the IP address segment, and directly obtain the part of the IP address segment of the user plane network element 1 and the tunnel endpoint identifier index corresponding to the IP address segment as at least one IP address.
- the segment and at least one tunnel endpoint identify the index.
- the user plane network element 1 has five IP address segments and five IP address segments.
- the tunnel endpoint identifies the index, and the resource management node directly obtains the three IP address segments and the tunnel endpoint identifier index corresponding to the three IP address segments.
- the resource management node allocates at least one IP address segment and at least one tunnel endpoint identifier index in step S301 to the user plane network element 4.
- step S302 is the same as the process of the step S103, and details are not described herein again.
- the resource management node notifies the user plane network element 1 and the user plane network element 4, the assigned user equipment IP address segment and the tunnel endpoint identifier index.
- step S403 is the same as the process in step S203, and details are not repeated herein.
- the resource management node notifies the forwarding node 3 of the correspondence between the user plane network element and the IP address segment, and notifies the forwarding node 1 of the correspondence between the user plane network element and the tunnel endpoint identifier index.
- the resource management node may notify the forwarding node 3 of the correspondence between the user plane network element and the IP address segment by the transmission control node, and notify the forwarding node 1 of the correspondence between the user plane network element and the tunnel endpoint identifier index.
- step S404 is the same as the process in step S304, and details are not described herein again.
- the resource management node notifies the control plane network element of the correspondence between the IP address segment, the tunnel endpoint identifier index, and the user plane network element.
- step S404 and step S405 may be changed, and does not depend on the order in the figure.
- S406 The UE sends uplink service data to the access network.
- the access network After receiving the uplink service data, the access network encapsulates the tunnel end identifier of the user plane network element 1 in the uplink service data, and sends the encapsulated uplink service data to the forwarding node 1.
- the forwarding node 1 obtains the user plane network element and the tunnel endpoint identifier index obtained in step 404. Correspondence relationship and uplink business The tunnel endpoint identifier in the data sends uplink service data to the user plane network element 4.
- the user plane network element 4 After receiving the uplink service data packet, the user plane network element 4 matches the information of the tunnel endpoint identifier in the uplink service data to the connection context, decapsulates the protocol layer including the tunnel endpoint identifier, and forwards the uplink service data to the report. Text data network.
- the UE may also receive downlink service data sent by the packet data network, as shown in FIG. 8:
- the packet data network sends downlink service data to the forwarding node 3, where the downlink service data includes an IP address of the UE.
- the user plane network element 4 After receiving the downlink service data packet, the user plane network element 4 matches the information of the IP address of the UE in the downlink service data to the connection context, and forwards the downlink service data to the UE according to the information in the connection context.
- connection context in step S409 and step S412 can be obtained by the following two methods:
- the control plane network element After receiving the corresponding relationship between the IP address segment, the tunnel endpoint identifier index, and the user plane network element, the control plane network element sends the affected connection context to the new user plane network element. That is, the connection context originally established in the user plane network element 1, after the context-related user equipment IP address and the tunnel endpoint identifier are reassigned to the user plane network element 4, the connection context is also sent to the user plane network element 4.
- the user plane network element 4 After receiving the uplink service data, the user plane network element 4 cannot obtain the corresponding connection context according to the tunnel endpoint identifier, and the user plane network element 4 obtains the connection context from the control plane network element.
- the user plane network element 4 carries the tunnel endpoint identifier in the message and sends the message to the control plane network element.
- the control plane network element searches for the corresponding connection context according to the tunnel endpoint identifier, and sends the corresponding connection context to the user plane network element 4.
- the user plane network element 4 After receiving the downlink service data, the user plane network element 4 cannot query the corresponding connection context according to the information such as the IP address of the UE, and then the user plane network element 4 is directed to the control plane.
- the network element obtains the connection context.
- the user plane network element 4 carries the IP address of the UE in the message and sends the message to the control plane network element.
- the control plane network element searches for the corresponding connection context according to the IP address of the UE, and sends the corresponding connection context to the user plane network element 4.
- the IP address of the original user plane network element and the tunnel endpoint identifier can be assigned to other newly added user plane network elements without interrupting the service of the user equipment, and after being allocated,
- the corresponding relationship is notified to the forwarding node by the transmission control node, and the forwarding node forwards the service data packet of the UE to the user plane network element according to the corresponding relationship, thereby realizing load sharing between the user plane network elements, and at the same time,
- the configuration can be implemented when the user plane network element is added to the network, and the plug-and-play of the newly added user plane network element is achieved.
- the service transmission method provided by the embodiment of the present invention is introduced from the perspectives of the resource management node, the transmission control node, the user plane network element, the control plane network element, the forwarding node, the access network, the UE, and the packet data network.
- the above-mentioned nodes or network elements include corresponding hardware structures and/or software modules for performing respective functions.
- the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
- the embodiment of the present invention may divide the functional modules of the resource management node, the transmission control node, the first forwarding node, and the second forwarding node according to the foregoing method example, and with reference to FIG. 9 to FIG. 12, for example, each function module may be divided according to each function. It is also possible to integrate two or more functions into one processing module.
- the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
- FIG. 9 is the present invention.
- the resource management node 10 may be used to implement a method performed by the resource management node in the foregoing method embodiment, and the resource management node 10
- the method may include: an obtaining unit 101, a determining unit 102, an allocating unit 103, such as: the obtaining unit 201 is configured to support the resource management node to execute the process S101 in FIG. 5, and the determining unit 102 is configured to support the resource management node to perform the process S102 in FIG.
- the allocating unit 103 is configured to support the resource management node to execute the processes S104 and S105 in FIG.
- the resource management node 10 may further include: a notification unit 104, corresponding to performing some processes in the foregoing method embodiments.
- the obtaining unit 101, the determining unit 102, and the allocating unit 103 shown in FIG. 9 can be integrated together as a processing module for controlling and managing the actions of the resource management node 10,
- the processing module is configured to support the resource management node to perform processes S101-S105 in FIG. 5, and/or other processes for the techniques described herein.
- the notification unit 104 can be integrated in the communication module for supporting communication of the resource management node 10 with other network entities.
- the resource management node 10 may also include a storage module for storing program code and data of the resource management node 10.
- the processing module may be the processor 1011 in the physical structure of the resource management node 10 shown in FIG.
- the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
- the communication module may be the transceiver 1013 in the physical structure of the resource management node 10 shown in FIG. 4, or may be a transceiver circuit or a communication interface or the like.
- the storage module may be a memory in the physical structure of the resource management node 10 shown in FIG.
- FIG. 10 is the present invention.
- the transmission control node 20 may be used to implement a method performed by a transmission control node in the foregoing method embodiment, the transmission control node 20
- the acquiring unit 201 and the notifying unit 202 are configured to support the transmission control node 20 to acquire the correspondence between the IP address notified by the resource control node 10, the tunnel endpoint identifier index, and the user plane network element, and the notification unit.
- the 202 is configured to support the transmission control node 20 to notify the first forwarding node of the correspondence between the IP address and the user plane network element, and to notify the transmission control node 20 of the correspondence between the tunnel endpoint identifier index and the user plane network element.
- the second forwarding node is configured to support the transmission control node 20 to notify the first forwarding node of the correspondence between the IP address and the user plane network element, and to notify the transmission control node 20 of the correspondence between the tunnel endpoint identifier index and the user plane network element.
- the obtaining unit 201 and the notifying unit 202 shown in FIG. 10 may be integrated in the communication module for supporting communication between the transmission control node 20 and other network entities.
- the transmission control node 20 may further include a processing module, a storage module, and a processing module for implementing a control function in the transmission control node 20 for storing program codes and data of the transmission control node 20.
- the processing module may be a processor in the physical structure of the transmission control node 20, and may be a processor or a controller, such as a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, and a transistor logic device. , hardware components, or any combination thereof.
- the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
- the communication module may be a transceiver in a physical structure of the transmission control node, or may be a transceiver circuit or a communication interface or the like.
- the storage module can be a memory in the physical structure of the transport control node.
- FIG. 11 is a schematic structural diagram of a first forwarding node involved in the embodiment of the present invention.
- the first forwarding node 30 may be used in the case of dividing each functional module by using corresponding functions.
- the method performed by the first forwarding node in the foregoing method embodiment, the first forwarding node 30 may include: an obtaining unit 301 and a sending unit 302.
- the obtaining unit is configured to support the first forwarding node 30 to perform the method shown in FIG.
- the sending unit 302 is configured to support the first forwarding node 30 to perform step S107 shown in FIG.
- the obtaining unit 301 and the transmitting unit 302 shown in FIG. 11 may be integrated in the communication module for supporting communication between the first forwarding node 30 and other network entities.
- the first forwarding node 30 may further include a processing module and a storage module.
- the processing module is configured to implement a control function in the first forwarding node 30 for storing program codes and data of the first forwarding node 30.
- the processing module may be a processor in the physical structure of the first forwarding node 30, and may be a processor or a controller, such as a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, and a transistor logic. Device, hardware component, or any combination thereof.
- the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
- the communication module may be a transceiver in a physical structure of the first forwarding node, or may be a transceiver circuit or a communication interface or the like.
- the storage module may be a memory in the physical structure of the first forwarding node.
- FIG. 12 is a schematic structural diagram of a second forwarding node involved in the embodiment of the present invention.
- the second forwarding node 40 may be used.
- the method performed by the second forwarding node in the foregoing method embodiment is implemented.
- the second forwarding node 40 may include: an obtaining unit 401 and a sending unit 402.
- the acquiring unit is configured to support the second forwarding node 40 to perform step S104 shown in FIG.
- the transmitting unit 402 is configured to support the second forwarding node 40 to perform step S106 shown in FIG.
- the obtaining unit 401 and the transmitting unit 402 shown in FIG. 12 may be integrated in the communication module for supporting communication between the second forwarding node 40 and other network entities.
- the second forwarding node 40 may further include a processing module and a storage module.
- the processing module is configured to implement a control function in the second forwarding node 40 for storing program codes and data of the second forwarding node 40.
- the processing module may be a processor in a physical structure of the second forwarding node 40, and may be a processor or a controller, such as a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, and a transistor logic. Device, hardware component, or any combination thereof.
- the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
- the communication module may be a transceiver in a physical structure of the second forwarding node, or may be a transceiver circuit or a communication interface or the like.
- the storage module may be a memory in the physical structure of the second forwarding node.
- the embodiment of the present invention further provides a service transmission system.
- the service transmission system may include: the resource management node 10, the transmission control node 20, and the first forwarding according to any of the foregoing embodiments.
- a device such as a node 30, a second forwarding node 40, a UE, a user plane network element, and a packet data network.
- the service transmission system provided by the embodiment of the present invention implements the foregoing service transmission method shown in FIG. 5 to FIG. 8 , and therefore, the same beneficial effects as the foregoing service transmission method can be achieved, and details are not repeatedly described herein.
- the disclosed system, apparatus, and method may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.
- the unit described as a separate component may or may not be physically divided
- the components displayed as the unit may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network devices. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each functional unit may exist independently, 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 hardware plus software functional units.
- the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
- the software functional units described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform portions of the steps of the methods described in various embodiments of the present invention.
- the foregoing storage medium includes: Universal Serial Bus (USB) flash drive (English: USB flash drive), mobile hard disk, read-only memory (English: read-only memory, ROM), random access
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明提供一种业务传输方法、设备及***,涉及通信技术领域,以解决用户面网元故障时,导致的用户设备的业务中断的问题。该方法包括:资源管理节点获取IP地址池,将所述IP地址池分为至少一个IP地址段,根据所述至少一个IP地址段确定至少一个隧道端点标识索引,将所述至少一个IP地址段和所述至少一个隧道端点标识索引分配给至少一个用户面网元。
Description
本发明涉及通信技术领域,尤其涉及一种业务传输方法、设备及***。
在图1所示的下一代移动通信网络的逻辑架构中,用户设备(英文:User Equipment,UE)通过本地的无线接入网络接入移动通信网络,控制面(英文:Control Plane,CP,或者Core Control Function,CCF)网元负责用户设备的连接管理、安全认证、移动性管理和位置管理等,用户面(英文:User Plane,UP)网元负责用户业务数据的转发。在实际网络部署中,图1中负责用户业务数据的转发的用户面网元可能会出现故障,这时,则需要一种方法,能够在用户面网元故障的情况下不影响用户业务数据的传输。
目前,下一代移动通信网络的用户面网元故障时,通常参考***(英文:4Generation,4G)通信网络中数据网关(英文:Packet Data Network Gateway,P-GW)故障时的处理方法,采用图2所示方案来保证用户业务数据的正常传输。具体的,图2所示的方案包括:1)当控制面网元检测到用户面网元1故障后,获知受影响的用户设备,通知这些用户设备重新建立数据连接;2)用户设备收到控制面网元的通知后,发起连接建立请求,请求重新建立数据连接;3)控制面网元收到用户设备的请求后,选择一个新的用户面网元2建立数据连接;4)用户面网元2回复连接建立响应,并给用户设备分配网络协议(英文:Internet Protocol,IP)地址;5)控制面网元向用户设备回复连接建立响应。如此,用户设备在新的用户面网元上建立数据连接,由新的用户面网元转发用户设备的业务数据。
虽然,现有在用户面网元故障的情况下,用户设备可以通过与其他的用户面网元建立数据连接来保证用户业务数据的正常传输,
但是,在用户设备与用户面网元建立数据连接的过程,因暂无可用的用户面网元来转发用户业务数据、以及建立数据连接的过程中与应用通讯的用户设备的IP地址被重新分配,这会导致用户设备的业务中断,影响用户的业务体验。
发明内容
本申请提供一种业务传输方法、设备及***,以解决用户面网元故障时,导致的用户设备的业务中断的问题。
为达到上述目的,本申请采用如下技术方案:
第一方面,本发明提供一种业务传输方法,该方法由资源管理节点执行,可以包括:获取用户设备IP地址池,将用户设备IP地址池分为至少一个用户设备IP地址段,根据至少一个用户设备IP地址段确定至少一个隧道端点标识索引,将至少一个用户设备IP地址段和至少一个隧道端点标识索引分配给至少一个用户面网元。用户设备IP地址池简称为IP地址池,用户设备IP地址段简称为IP地址段。
如此,通过网络中新增的资源管理节点管理IP地址和隧道端点标识,维护隧道端点标识索引、用户设备IP地址段以及用户面网元三者的对应关系,用户设备IP地址、隧道端点标识和用户面网元之间没有必然的绑定关系,资源管理节点可以根据网络内的情况(如:用户面网元故障/过载等情况)动态的调整用户设备IP地址、隧道端点标识、用户面网元对应关系,在保持用户设备IP地址和隧道端点标识不变的情况下,通过新的用户面网元转发用户业务数据,不需要用户设备与用户面网元重新建立数据连接,避免了用户设备的业务中断的问题。同时,该方法不需要在用户面网元上进行业务数据转发的相关配置,简化用户面网元的配置,实现用户面网元的免配置,从而支持用户面网元的即插即用。
在第一方面的一种可实现方式中,结合第一方面,该方法还可以包括:
资源管理节点将IP地址段与用户面网元的对应关系通知给第
一转发节点、以及将隧道端点标识索引与用户面网元间的对应关系通知给第二转发节点。
如此,可以实现资源管理节点直接将对应关系通知给转发节点,由转发节点根据对应关系将用户设备的业务数据发送至相应的用户面网元来实现业务数据的转发。
在第一方面的又一种可实现方式中,结合第一方面,该方法还可以包括:
资源管理节点将IP地址段、隧道端点标识索引、用户面网元间的对应关系通知给传输控制节点;该对应关系用于通知传输控制节点将IP地址段与用户面网元的对应关系通知给第一转发节点,将隧道端点标识索引与用户面网元间的对应关系通知给第二转发节点。
其中,IP地址段、隧道端点标识索引、用户面网元间的对应关系具体指:IP地址段、隧道端点标识索引、用户面网元标识的对应关系;用户面网元标识包括用户面网元的IP地址,或者用户面网元的标识ID。
如此,可以由资源管理节点先将IP地址段、隧道端点标识索引、用户面网元间的对应关系通知给传输控制节点,再由传输控制节点将对应关系通知给转发节点,由转发节点根据对应关系将用户设备的业务数据发送至相应的用户面网元来实现业务数据的转发。
在第一方面的又一种可实现方式中,结合第一方面或第一方面的任意可实现方式,资源管理节点将至少一个IP地址段和至少一个隧道端点标识索引分配给至少一个用户面网元可以包括:
资源管理节点根据用户面网元的信息,将至少一个IP地址段和至少一个隧道端点标识索引分配给至少一个用户面网元;其中,用户面网元的信息包括:资源管理节点所在网络内可用的用户面网元的数量和/或用户面网元的容量。
其中,同一IP地址段,以及根据该IP地址段确定的隧道端点标识索引分配给同一个用户面网元。不同的用户面网元分配的IP地址段是不同的。
如此,可以根据网络中用户面网元的数量、容量来分配IP地址段和隧道端点标识索引,实现了各用户面网元的负载均衡。
此外,当网络中新增用户面网元时,还可以将现有用户面网元对应的部分IP地址段和隧道端点标识索引分配给新增用户面网元,以减轻现有用户面网元的负担,具体的,资源管理节点可以将划分出的至少一个IP地址段和至少一个隧道端点标识索引分配给新增的用户面网元。
如此,可以在新增用户面网元的情况下,不中断用户设备的业务,将该用户设备相关的IP地址和隧道端点标识分配给新增的用户面网元,同时,在网络新增用户面网元时实现免配置,达到新增用户面网元的即插即用。
进一步的,当网络中出现故障/过载的用户面网元时,为了使原来承载在该类用户面网元上的业务数据正常转发,可以将该类用户面网元对应的IP地址段、隧道端点标识索引分配给其他可用的用户面网元,通过其他可用的用户面网元转发业务数据,具体的,在第一方面的再一种可实现方式中,结合第一方面或第一方面的任意可实现方式,资源管理节点可以获取分配给第一用户面网元的部分或者全部IP地址段,将分配给第一用户面网元的部分或者全部IP地址段作为IP地址池;
资源管理节点将至少一个IP地址段和至少一个隧道端点标识索引分配给除第一用户面网元之外的至少一个用户面网元。
其中,第一用户面网元可以为出现故障或过载的用户面网元。
如此,可以通过资源管理节点将分配给出现故障或过载的用户面网元的用户设备IP地址段和隧道端点标识索引重分配给其他通信正常的用户面网元,使得在用户面网元故障/过载等情况下,在不中断用户设备的业务的情况下,改变转发用户设备的业务数据包的用户面网元。
第二方面,本发明提供一种业务传输方法,由传输控制节点执行,该方法可以包括:获取资源管理节点发送的IP地址段、隧道端
点标识索引、用户面网元间的对应关系,将IP地址段与用户面网元的对应关系通知给第一转发节点、以及将隧道端点标识索引与用户面网元间的对应关系通知给第二转发节点。
其中,IP地址段、隧道端点标识索引、用户面网元间的对应关系具体包括:IP地址段、隧道端点标识索引、用户面网元标识的对应关系;用户面网元标识包括用户面网元的IP地址,或者用户面网元的标识ID。
如此,可以由资源管理节点先将IP地址段、隧道端点标识索引、用户面网元间的对应关系通知给传输控制节点,再由传输控制节点将对应关系通知给转发节点,由转发节点根据对应关系将用户设备的业务数据发送至相应的用户面网元来实现业务数据的转发。
第三方面,本发明提供一种业务传输方法,由第一转发节点执行,该方法可以包括:获取IP地址段与用户面网元之间的对应关系,根据IP地址段与用户面网元之间的对应关系,向用户面网元转发报文数据网络发送的下行业务数据。
其中,第一转发节点可以为资源管理节点所在网络中,位于用户面网元与报文数据网络之间的转发节点。
如此,可以实现第一转发节点根据自身获取到的对应关系,将接收到的报文数据网络发送的下行业务数据转发给相应的用户面网元。
可选的,在第三方面的一种可实现方式中,结合第三方面,第一转发节点可以直接获取资源管理节点通知的IP地址段与用户面网元之间的对应关系;也可以获取传输控制节点通知的IP地址段与用户面网元之间的对应关系。
第四方面,本发明提供一种业务传输方法,由第二转发节点执行,该方法可以包括:获取隧道端点标识索引与用户面网元之间的对应关系,根据隧道端点标识索引与用户面网元之间的对应关系,向用户面网元转发接入网发送的上行业务数据。
如此,可以实现第二转发节点根据自身获取到的对应关系,将
接收到的接入网发送的上行业务数据转发给相应的用户面网元。
可选的,在第四方面的一种可实现方式中,结合第四方面,第二转发节点可以直接获取资源管理节点通知的隧道端点标识索引与用户面网元之间的对应关系;也可以获取传输控制节点通知的隧道端点标识索引与用户面网元之间的对应关系。
第五方面,本发明提供一种资源管理节点,该资源管理节点包括:
获取单元,用于获取IP地址池;
确定单元,用于将获取单元获取到的IP地址池分为至少一个IP地址段,根据至少一个IP地址段确定至少一个隧道端点标识索引;
分配单元,用于将确定单元确定出的至少一个IP地址段和所述至少一个隧道端点标识索引分配给至少一个用户面网元。
其中,第五方面的具体实现方式可以参考第一方面或第一方面的可能的实现方式提供的业务传输方法中资源管理节点的行为功能,在此不再重复赘述。因此,第五方面提供的资源管理节点可以达到与第一方面相同的有益效果。
第六方面,本发明提供一种资源管理节点,该资源管理节点包括:
收发器,用于获取IP地址池;
处理器,用于将收发器获取到的IP地址池分为至少一个IP地址段,根据至少一个IP地址段确定至少一个隧道端点标识索引;
以及,将处理器确定出的至少一个IP地址段和所述至少一个隧道端点标识索引分配给至少一个用户面网元。
其中,第六方面的具体实现方式可以参考第一方面或第一方面的可能的实现方式提供的业务传输方法中资源管理节点的行为功能,在此不再重复赘述。因此,第六方面提供的资源管理节点可以达到与第一方面相同的有益效果。
第七方面,本发明提供一种存储一个或多个程序的非易失性计算机可读存储介质,该一个或多个程序包括指令,指令当被包括第
五方面或第六方面或上述任一种可能的实现方式所述的资源管理节点执行时,使资源管理节点执行以下事件:
获取IP地址池,将IP地址池分为至少一个IP地址段,根据至少一个IP地址段确定至少一个隧道端点标识索引,将至少一个IP地址段和至少一个隧道端点标识索引分配给至少一个用户面网元。
其中,第七方面的具体实现方式可以参考第一方面或第一方面的可能的实现方式提供的业务传输方法中资源管理节点的行为功能,在此不再重复赘述。因此,第七方面提供的资源管理节点可以达到与第一方面相同的有益效果。
第八方面,本发明提供一种传输控制节点,该传输控制节点包括:获取单元,用于获取资源管理节点发送的IP地址段、隧道端点标识索引、用户面网元间的对应关系;
通知单元,用于将获取单元获取到的IP地址段与用户面网元的对应关系通知给第一转发节点、以及将隧道端点标识索引与用户面网元间的对应关系通知给第二转发节点。
其中,第八方面的具体实现方式可以参考第二方面或第二方面的可能的实现方式提供的业务传输方法中传输控制节点的行为功能,在此不再重复赘述。因此,第八方面提供的传输控制节点可以达到与第二方面相同的有益效果。
第九方面,本发明提供一种传输控制节点,该传输控制节点包括:收发器,用于获取资源管理节点发送的IP地址段、隧道端点标识索引、用户面网元间的对应关系;
以及,将收发器获取到的IP地址段与用户面网元的对应关系通知给第一转发节点、以及将隧道端点标识索引与用户面网元间的对应关系通知给第二转发节点。
其中,第九方面的具体实现方式可以参考第二方面或第二方面的可能的实现方式提供的业务传输方法中传输控制节点的行为功能,在此不再重复赘述。因此,第九方面提供的传输控制节点可以达到与第二方面相同的有益效果。
第十方面,本发明提供一种存储一个或多个程序的非易失性计算机可读存储介质,该一个或多个程序包括指令,指令当被包括第八方面或第九方面或上述任一种可能的实现方式所述的传输控制节点执行时,使传输控制节点执行以下事件:
获取资源管理节点发送的IP地址段、隧道端点标识索引、用户面网元间的对应关系,将获取到的IP地址段与用户面网元的对应关系通知给第一转发节点、以及将隧道端点标识索引与用户面网元间的对应关系通知给第二转发节点。
其中,第十方面的具体实现方式可以参考第二方面或第二方面的可能的实现方式提供的业务传输方法中传输控制节点的行为功能,在此不再重复赘述。因此,第十方面提供的传输控制节点可以达到与第二方面相同的有益效果。
第十一方面,本发明提供一种第一转发节点,该第一转发节点包括:获取单元,用于获取IP地址段与用户面网元之间的对应关系;
发送单元,用于根据获取单元获取到的IP地址段与用户面网元之间的对应关系,向所述用户面网元转发报文数据网络发送的下行业务数据。
其中,第十一方面的具体实现方式可以参考第三方面或第三方面的可能的实现方式提供的业务传输方法中第一转发节点的行为功能,在此不再重复赘述。因此,第十一方面提供的第一转发节点可以达到与第三方面相同的有益效果。
第十二方面,本发明提供一种第一转发节点,该第一转发节点包括:收发器,用于获取IP地址段与用户面网元之间的对应关系;
以及,根据收发器获取到的IP地址段与用户面网元之间的对应关系,向所述用户面网元转发报文数据网络发送的下行业务数据。
其中,第十二方面的具体实现方式可以参考第三方面或第三方面的可能的实现方式提供的业务传输方法中第一转发节点的行为功能,在此不再重复赘述。因此,第十二方面提供的第一转发节点可以达到与第三方面相同的有益效果。
第十三方面,本发明提供一种存储一个或多个程序的非易失性计算机可读存储介质,该一个或多个程序包括指令,指令当被包括第八方面或第九方面或上述任一种可能的实现方式所述的第一转发节点执行时,使第一转发节点执行以下事件:
获取IP地址段与用户面网元之间的对应关系,根据获取到的IP地址段与用户面网元之间的对应关系,向所述用户面网元转发报文数据网络发送的下行业务数据。
其中,第十三方面的具体实现方式可以参考第三方面或第三方面的可能的实现方式提供的业务传输方法中第一转发节点的行为功能,在此不再重复赘述。因此,第十三方面提供的第一转发节点可以达到与第三方面相同的有益效果。
第十四方面,本发明提供一种第二转发节点,该第二转发节点可以包括:获取单元,用于获取隧道端点标识索引与用户面网元之间的对应关系;
发送单元,用于根据获取单元获取到的隧道端点标识索引与用户面网元之间的对应关系,向所述用户面网元转发接入网发送的上行业务数据。
其中,第十四方面的具体实现方式可以参考第四方面或第四方面的可能的实现方式提供的业务传输方法中第二转发节点的行为功能,在此不再重复赘述。因此,第十四方面提供的第二转发节点可以达到与第四方面相同的有益效果。
第十五方面,本发明提供一种第二转发节点,该第二转发节点可以包括:收发器,用于获取隧道端点标识索引与用户面网元之间的对应关系;
以及,根据收发器获取到的隧道端点标识索引与用户面网元之间的对应关系,向所述用户面网元转发接入网发送的上行业务数据。
其中,第十五方面的具体实现方式可以参考第四方面或第四方面的可能的实现方式提供的业务传输方法中第二转发节点的行为功能,在此不再重复赘述。因此,第十五方面提供的第二转发节点可
以达到与第四方面相同的有益效果。
第十六方面,本发明提供一种存储一个或多个程序的非易失性计算机可读存储介质,该一个或多个程序包括指令,指令当被包括第八方面或第九方面或上述任一种可能的实现方式所述的第二转发节点执行时,使第二转发节点执行以下事件:
获取隧道端点标识索引与用户面网元之间的对应关系,根据获取到的隧道端点标识索引与用户面网元之间的对应关系,向所述用户面网元转发接入网发送的上行业务数据。
其中,第十六方面的具体实现方式可以参考第四方面或第四方面的可能的实现方式提供的业务传输方法中第二转发节点的行为功能,在此不再重复赘述。因此,第十六方面提供的第二转发节点可以达到与第四方面相同的有益效果。
第十七方面,本发明提供一中业务传输***,包括如第五方面或第六方面或第七方面或上述任一方式所述的资源管理节点、如第八方面或第九方面或第十方面或上述任一方式所述的传输控制节点、如第十一方面或第十二方面或第十三方面或上述任一方式所述的第一转发节点、如第十四方面或第十五方面或第十六方面或上述任一方式所述的第一转发节点、用户面网元、UE以及报文数据网络。
第十七方面提供的业务传输***,可以实现上述所示的业务传输方法,因此,可以达到与上述业务传输方法相同的有益效果。
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为现有下一代移动通信网络架构示意图;
图2为一种用户面网元复位处理流程示意图;
图3为本发明实施例提供的下一代移动通信网络架构示意图;
图4为本发明实施例提供的一种资源管理节点的结构图;
图5为本发明实施例提供的一种业务传输方法的流程图;
图6为本发明实施例提供的又一种业务传输方法的流程图;
图7为本发明实施例提供的再一种业务传输方法的流程图;
图8为本发明实施例提供的再一种业务传输方法的流程图;
图9为本发明实施例提供的一种资源管理节点10的结构图;
图10为本发明实施例提供的一种传输控制节点20的结构图;
图11为本发明实施例提供的一种第一转发节点30的结构图;
图12为本发明实施例提供的一种第二转发节点40的结构图;
图13为本发明实施例提供的一种业务传输***的结构图。
本发明的原理是:在原有的网络架构中新增资源管理节点,通过资源管理节点对多个隧道端点标识、以及多个用户设备IP地址进行分段,将分段后的隧道端点标识索引以及用户设备IP地址段分配给用户面网元,并将隧道端点标识索引、用户设备IP地址段以及用户面网元三者的对应关系通知给传输控制节点,由传输控制节点通知给转发节点,使转发节点根据自身获知的对应关系将包含隧道端点标识的业务数据或包含用户设备IP地址的业务数据转发至相应的用户面网元,由该用户面网元进行该业务数据的转发。
下面结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
在本发明的描述中,需要理解的是,术语“第一”、“第二”、“另一”等指示的***或元件为基于实施例描述的具有一定功能的***或元件,仅是为了便于描述本发明和简化描述,而不是指示或暗示所指的***或元件必须有此命名,因此不能理解为对本发明的限制。
本发明所述的业务传输方法可以应用于图3所示的下一代移动
通信网络(英文:Next Generation Network,NGN),如图3所示,该网络可以包括:接入网、接入网与用户面网元之间的多个转发节点(如:转发节点1、转发节点2)、资源管理节点、传输控制节点、控制面网元、多个用户面网元、用户面网元与报文数据网络之间的多个转发节点(如:转发节点3、转发节点4)、以及报文数据网络。需要说明的是,图3仅为示意图,图3所示节点只是示例,其个数对本申请所述方案不构成限制,尤其是转发节点,其个数不局限于图3所示的几个,在实际部署时网络内可以部署不同于图3所示的多个转发节点。
其中,图3中的接入网可以为增强的长期演进(英文:evolved Long Term Evolution,eLTE)网络,也可以为下一代网络接入网(英文NextGen RAN)的第三代合作伙伴计划(英文:3rd Generation Partnership Project,3GPP)接入网,还可以为无线局域网(英文:Wireless Local Area Networks,WLAN)或者固定接入等接入网。接入网与用户面网元之间的转发节点(如:转发节点1、转发节点2)主要负责接入网和用户面网元之间的业务数据的转发,用户面网元与报文数据网络之间的转发节点(如:转发节点3、转发节点4)主要负责用户面网元和报文数据网络之间的业务数据的转发,转发节点可以为交换机或者负荷均衡节点等路由设备。传输控制节点通过监控转发节点了解网络状况,同时调度和控制流量的转发。资源管理节点可以是一个管理服务器,主要负责将用户设备因特网协议(英文:Internet Protocol,IP)地址和隧道端点标识(英文:Tunnel Endpoint Identifier,TEID)分段,生成用户设备地址IP段和隧道端点标识索引,并建立用户设备IP地址段、隧道端点标识索引、用户面网元三者间的对应关系。控制面网元和用户面网元如图1中介绍,用户面网元主要负责用户业务数据的转发。控制面网元主要负责用户设备的连接管理、安全认证、移动性管理和位置管理等。下一代移动通信网络中可能会将控制面网元进行模块化拆分,拆分出来的功能模块可以认为是独立的网元,例如,将CP或者CCF拆分为会
话管理功能(英文:Session Management,SM)、移动性管理功能(英文:Mobily Management,MM)等功能模块,在此逻辑架构下,实施例中的控制面网元的功能由会话管理功能(英文:Session Management,SM)执行。
需要说明的是,图3中对于转发节点的部署是示意性的,仅仅为一种可行性部署方案,实际实现时可以有不同的部署方式,即各个转发节点可以独立于网络中的其他网元部署在传输网络,如交换机,还可以独立于网络中的其他网元部署在核心网络中,如负荷均衡节点,还可以将多个转发节点集成在网络中的现有节点中来实现转发节点的功能,如:可以将用户面网元与报文数据网络之间的转发节点集成在用户面网元中,由用户面网元执行该转发节点的功能,本发明实施例对此不进行限定。同样,资源管理节点也可以独立于网络中的其他网元部署在网络中,还可以将资源管理节点集成在网络中的现有节点(如控制面网元)中来实现资源管理节点的功能。
具体的,图3中的各个节点、网元均可以包含:处理器、存储器、通信单元以及至少一个通信总线等部件,其中,通信总线用于实现这些装置之间的连接和相互通信。为了便于描述,下面仅以资源管理节点为例,结合图4对资源管理节点的各个构成部件进行具体的介绍,其他节点或网元的构成部件可以参考资源管理节点,在此不再详细赘述。
如图4所示,该资源管理节点10可以包括:处理器1011、存储器1012、收发器1013以及至少一个通信总线1014,通信总线1014用于实现这些装置之间的连接和相互通信;
其中,处理器1011可以是中央处理器(英文:central processing unit,CPU),网络处理器(英文:network processor,NP),硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(英文:application-specific integrated circuit,ASIC),可编程逻辑器件(英文:programmable logic device,PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文:complex programmable logic device,
CPLD),现场可编程逻辑门阵列(英文:field-programmable gate array,FPGA),通用阵列逻辑(英文:generic array logic,GAL)或其任意组合。
存储器1012,可以是易失性存储器(英文:Volatile Memory),例如随机存取存储器(英文:Random-Access Memory,RAM);或者非易失性存储器(英文:Non-volatile Memory),例如只读存储器(英文:Read-only Memory,ROM),快闪存储器(英文:Flash Memory),硬盘(英文:Hard Disk Drive,HDD)或固态硬盘(英文:Solid-state Drive,SSD);或者上述种类的存储器的组合。处理器1011可以通过运行或执行存储在存储器1012内的程序代码,以及调用存储在存储器1012内的数据,实现资源管理节点的各种功能。
收发器1013可用于与外部网元之间进行数据交互,收发器1013可以为天线。
通信总线1014可以分为地址总线、数据总线、控制总线等,可以是工业标准体系结构(英文:Industry Standard Architecture,ISA)总线、外部设备互连(英文:Peripheral Component,PCI)总线或扩展工业标准体系结构(英文:Extended Industry Standard Architecture,EISA)总线等。为便于表示,图4中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
为便于描述,以下实施例以步骤的形式示出并详细描述了本发明提供的保证业务连续性的过程,其中,示出的步骤也可以在一组可执行指令的计算机***中执行。此外,虽然在图中示出了逻辑顺序,但是在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤。
图5为本发明实施例提供的一种业务传输方法的流程图,由图3所示网络中的设备交互执行,如图5所示,该方法可以包括以下步骤:
步骤S101:资源管理节点获取IP地址池。
其中,IP地址池可以包含大量的用户设备IP地址(简称IP地址),IP地址段也可以包含多个IP地址,只是IP地址段包含的IP地址的数量可以远小于IP地址池包含的IP地址的数量,IP地址可以为UE与报文数据网络之间进行通信的IP地址。
可选的,在网络初始化过程中,资源管理节点可以从操作维护网元(英文:Operation and maintenance,O&M)处获取。
步骤S102:资源管理节点将IP地址池分为至少一个IP地址段,并根据至少一个IP地址段确定至少一个隧道端点标识索引。
可选的,资源管理节点可以根据需要将用户设备IP地址池中的多个用户设备IP地址划分到多个用户设备IP地址段,如:可以预先设定IP地址段可包含的IP地址的数量,并按照这个预设数量将用户设备IP地址池中的多个用户设备IP地址划分为多个用户设备IP地址段,其中,预设数量可以根据需要进行设置,本发明实施例对此不进行限定。
例如,假设预设数量为5万个,即每5万个用户设备IP地址为一个用户设备IP地址段,用户设备IP地址池共包含5000万个用户设备IP地址,则可以将用户设备IP地址池中的用户设备IP地址分成1000个用户设备IP地址段,每个用户设备IP地址段包含5万个用户设备IP地址。
其中,步骤S102中的IP地址段与隧道端点标识索引一一对应,可选的,在本发明实施例中可以为每个IP地址段分配一个索引,用该索引标识该IP地址段的同时,并将该索引放在隧道端点标识的若干比特中,生成隧道端点标识索引,以此根据IP地址段确定隧道端点标识索引,实现该IP地址段包含的任一IP地址的业务数据需要通过此隧道端点标识索引包含的隧道端点标识所标识的隧道进行转发。需要说明的是,除上述索引之外,还可以为IP地址段分配其他关联信息,用该关联信息确定与该IP地址段对应的隧道端点标识索引,本发明对比不进行限定;此外,将索引放在隧道端点标识的哪些比特位置上,本发明实施例对此是不限定的。
例如,若IP地址段10.184.228.0~10.184.228.255分给了用户面网元1,且为该IP段分配的索引为二进制数0001,且规定隧道端点标识的16bit中的第1比特~第4比特为放置与IP地址段相关联的信息的比特,则分配给用户面网元1的与该IP地址段对应的隧道端点标识索引为0001xxxxxxxxxxxx。需要说明的是,资源管理节点为IP地址段分配索引或者其他关联信息的算法本发明不予以限定,但要求每个IP地址段对应一个唯一的索引或者关联信息,不同IP地址段对应的索引或者关联信息不同。
其中,隧道端点标识用于标识一个隧道,隧道是指接入网与用户面网元之间的通道,用于转发接入网与用户面网元之间的业务数据。在本发明中,可以将隧道端点标识分配给任一用户面网元,用该隧道端点标识标识接入网与该用户面网元的一个隧道。例如:若将隧道端点标识A分配给用户面网元1,则表示隧道端点标识A标识接入网与用户面网元1之间的一个隧道,若将隧道端点标识A分配给用户面网元2,则表示隧道端点标识A标识接入网与用户面网元2之间的一个隧道。
步骤S103:资源管理节点将至少一个IP地址段和至少一个隧道端点标识索引分配给至少一个用户面网元。
其中,IP地址段,以及根据此IP地址段确定的隧道端点标识索引分配给同一个用户面网元,每个用户面网元可以分的一个或多个IP地址段,不同用户面网元分配的IP地址段是不同的。
资源管理节点为用户面网元分配隧道端点标识索引,则表示经过该隧道端点标识索引包含的隧道端点标识所标识的隧道的业务数据都要通过该用户面网元转发至报文数据网络;资源管理节点为用户面网元分配IP地址段,则表示报文数据网络发往该IP地址段包含的任一IP地址的业务数据都要通过该用户面网元转发至UE。
可选的,资源管理节点可以根据图3所示网络中用户面网元的信息,将至少一个用户设备IP地址段、以及至少一个隧道端点标识索引分配给网络中每个用户面网元。
其中,用户面网元的信息可以包括:用户面网元数量、或者用户面网元容量、或者用户面网元数量和用户面网元容量。
可选的,资源管理节点可以根据用户面网元的信息将至少一个用户设备IP地址段均匀地分配给网络中的各个用户面网元,还可以根据不同用户面网元容量的高低将至少一个用户设备IP地址段分配给网络中的各个用户面网元。
例如:资源管理节点可以根据用户面网元数量,将1000个用户设备IP地址段平分给各个用户面网元,比如有10个用户面网元,则每个用户面网元分配到100个用户设备IP地址段;又比如,资源管理节点还可以根据各个用户面网元的容量,将1000个用户设备IP地址段分配给各个用户面网元,其中,容量较高的用户面网元分配较多的用户设备IP地址段,容量较低的用户面网元分配较少的用户设备IP地址段,比如共有30个用户面网元,其中10个用户面网元的容量相同,另外20个用户面网元的容量相同,前者的容量是后者的2倍,则给10个用户面网元每个分配50个用户设备IP地址段,给另外20个用户面网元每个分配25个用户设备IP地址段。
此外,在本发明的又一可行性方案中,还可以根据用户面网元的信息将用户设备IP地址池内的用户设备IP地址划分为多个用户设备IP地址段,根据IP地址段确定隧道端点标识索引,再将IP地址段以及对应的隧道端点标识索引分给各个用户面网元。例如:资源管理节点可以根据用户面网元数量,将用户设备IP地址池内的IP地址均匀分成与用户面网元数量相对应的份数;或者资源管理节点根据不同用户面网元容量的高低将IP地址池内的IP地址分成与用户面网元数量对应的份数,且容量高的用户面网元分配较多的用户设备IP地址。
步骤S104:资源管理节点将分配给用户面网元的IP地址段与用户面网元之间的对应关系通知给第一转发节点,第一转发节点接收资源管理节点通知的用户面网元的IP地址段与用户面网元之间的对应关系。
其中,第一转发节点可以为资源管理节点所在网络内、位于用户面网元与报文数据网络之间的任意转发节点。如图3中转发节点3和转发节点4所示。
步骤S105:资源管理节点将分配给用户面网元的隧道端点标识索引与用户面网元之间的对应关系通知给第二转发节点,第二转发接收资源管理节点通知的用户面网元的隧道端点标识索引与用户面网元之间的对应关系。
其中,第二转发节点可以为资源管理节点所在网络内、位于接入网与用户面网元之间的任意转发节点。如图3中转发节点1或转发节点2所示。
需要说明的是,步骤S104和步骤S105的顺序可以发生变化,可以同时执行,也可以不依赖于图5中的顺序先后执行。
可选的,在将至少一个IP地址段和至少一个隧道端点标识索引分配给至少一个用户面网元之后,资源管理节点可以将IP地址段、隧道端点标识索引以及用户面网元三者之间的对应关系通知给传输控制节点,通过传输控制节点将分配给用户面网元的IP地址段与用户面网元之间的对应关系通知给第一转发节点、以及将分配给用户面网元的隧道端点标识索引与用户面网元之间的对应关系通知给第二转发节点。
其中通知给传输控制节点的IP地址段、隧道端点标识索引以及用户面网元三者之间的对应关系,通知给第一转发节点的IP地址段与用户面网元之间的对应关系,通知给第二转发节点的隧道端点标识索引与用户面网元之间的对应关系中,与用户面网元之间的关系为与用户面网元标识的关系,所述用户面网元标识包括所述用户面网元的IP地址,或者所述用户面网元的标识ID。
步骤106:第二转发节点根据隧道端点标识索引与用户面网元之间的对应关系,向用户面网元转发接入网发送的上行业务数据。
步骤107:第一转发节点根据IP地址段与用户面网元之间的对应关系,向用户面网元转发报文数据网络发送的下行业务数据。
其中,在本发明实施例中,将从UE发往报文数据网络的业务数据称之为上行业务数据,将从报文数据网络发往UE的业务数据称之为下行业务数据。
与现有技术相比,在图5所示的技术方案中,不需要在用户面网元上进行业务数据转发的相关配置,用户设备IP地址和用户面网元之间没有必然的绑定关系,而是由资源管理节点管理用户设备IP地址和隧道端点标识,维护隧道端点标识索引、用户设备IP地址段以及用户面网元三者的对应关系,并将对应关系通过传输控制节点通知给转发节点,由转发节点根据对应关系将用户设备的业务数据发送至相应的用户面网元来实现业务数据的转发,资源管理节点可以根据网络内的情况动态的调整对应关系,在保持用户设备在IP地址和隧道端点标识不变的情况下,通过新的用户面网元转发用户业务数据。如此,可以在用户面网元故障/过载等情况下,不需要用户设备与用户面网元重新建立数据连接,避免了用户设备的业务中断的问题,同时,该方法可以简化用户面网元的配置,实现用户面网元的免配置,从而支持用户面网元的即插即用。
需要说明的是,图5所示的技术方案可以应用于网络初始化、用户面网元复位/过载,或者新增用户面网元的任意场景下,以实现户面免配置、以及复位/过载/新增场景下的业务连续性。
为使本发明的方案更清楚、目的更明确,下面在图3所示的网络结构下,结合图6~8对本发明所述方案进行详细介绍:
图6为本发明实施例提供的一种业务传输方法的流程图,由图3所示网络中的设备交互执行,用于在网络初始化过程中为图3所示网络中的各个用户面网元分配相应的IP地址段以及隧道端点标识索引,并将分配后的用户面网元、IP地址段、以及隧道端点标识索引之间的对应关系通知给相应的转发节点,由转发节点根据接收到的对应关系,将接收到的上行/下行业务数据转发至相应的用户面节点,由用户面网元进行业务传输;如图6所示,该方法可以包括以下步骤:
资源管理节点从O&M处获取IP地址池。
S201:资源管理节点将IP地址池分为至少一个IP地址段,并根据至少一个IP地址段确定至少一个隧道端点标识索引。
其中,步骤S201与步骤S102相同,在此不再重复赘述。
S202:资源管理节点为图3所示的各个用户面网元分配IP地址段以及隧道端点标识索引。
其中,步骤S202与步骤S103的分配过程相同,在此不再重复赘述。
S203:资源管理节点通知各个用户面网元,其被分配的用户设备IP地址段和隧道端点标识索引。
可选的,资源管理节点可以直接通知各个用户面网元,其被分配的IP地址段和隧道端点标识索引;也可以通过控制面网元通知各个用户面网元,其被分配的IP地址段和隧道端点标识索引。
需要说明的是,在本发明实施例中,步骤S203可以执行也可以不执行,即用户面网元分配的用户设备IP地址段和隧道端点标识索引,对于用户面网元而言可知或者不可知都是可以的,本发明对此不进行限定。
S204:资源管理节点将用户面网元和IP地址段的对应关系通知给转发节点3,将用户面网元和隧道端点标识索引的对应关系通知给转发节点1。
可理解的是,资源管理节点也可以将用户面网元和IP地址段的对应关系通知给转发节点4,将用户面网元和隧道端点标识索引的对应关系通知给转发节点2,或者将用户面网元和IP地址段的对应关系同时通知给转发节点1和4,将用户面网元和隧道端点标识索引的对应关系同时通知给转发节点1和2。本发明实施例对此不进行限定,本发明仅以将用户面网元和IP地址段的对应关系通知给转发节点3,将用户面网元和隧道端点标识索引的对应关系通知给转发节点1为例进行说明。
可选的,资源管理节点可以直接将用户面网元和IP地址段的对
应关系通知给转发节点3,将用户面网元和隧道端点标识索引的对应关系通知给转发节点1。
还可以将用户面网元、用户设备IP地址段、隧道端点标识索引三者间的对应关系通知给传输控制节点,所述对应关系即各个用户面网元标识,及其被分配的用户设备IP地址段和隧道端点标识索引,所述用户面网元标识可以为用户面网元IP地址,或者用户面网元ID等可以唯一标识用户面网元的信息;
传输控制节点收到资源管理节点发送的用户面网元、用户设备IP地址段、和隧道端点标识索引的对应关系后,将用户面网元和IP地址段的对应关系通知给转发节点3,将用户面网元和隧道端点标识索引的对应关系通知给转发节点1。
S205:UE向控制面网元发送连接建立请求,该连接建立请求用于请求与报文数据网络间建立连接。
可选的,UE可以通过接入网向控制面网元发出连接建立请求。
S206:控制面网元接收到该连接建立请求后,若确定用户面网元1来转发该UE与报文数据网络间的业务数据,则分配用户面网元1的隧道端点标识给接入网,同时向UE回复连接建立响应消息,该连接建立响应消息中包含控制面网元分配给UE的IP地址。
至此UE通过用户面网元1与报文数据网络间的连接通道建立,控制面网元完成连接建立后,执行步骤S207。
用户面网元1的隧道端点标识包含在资源管理节点为用户面网元1分配的隧道端点标识索引包含的隧道端点标识内。
可选的,可以从资源管理节点为用户面网元1分配的隧道端点标识索引内随机指定一个隧道端点标识,将该隧道端点标识作为UE请求建立的连接的用户面网元1的隧道端点标识,该用户面网元1的隧道端点标识可以用于标识用户面网元1的唯一一条隧道。
例如,若UE1请求与报文数据网络间建立连接,控制面网元选择用户面网元1来转发该连接1的业务数据,资源管理节点为用户面网元1分配的隧道端点标识索引内包含50个隧道端点标识,则可
以从这50个隧道端点标识内选择任意隧道端点标识,将选择出的隧道端点标识作为用户面网元1的隧道端点标识。
其中,UE的IP地址包含在资源管理节点为用户面网元1分配的IP地址段内;可选的,控制面网元可以从资源管理节点为用户面网元1分配的IP地址段内随机选择一个IP地址作为该UE的IP地址。
需要说明的是,每一个用户面网元可能被分到多个用户设备IP地址段,以及根据多个用户设备IP地址段确定的多个隧道端点标识索引。把一个用户设备IP地址段以及根据其确定的隧道端点标识索引称为成对关系。在本步骤分配用户面网元1的隧道端点标识,以及UE的IP地址时,包含该隧道端点标识的隧道端点标识索引,以及包含该UE的IP地址的用户设备IP地址段是成对关系的。
需要说明的是,本步骤中,如果控制面网元和资源管理节点为集成在一起的功能网元,则可以由控制面网元直接分配用户面网元1的隧道端点标识给接入网,以及给UE分配IP地址;否则,如果控制面网元和资源管理节点为分离的功能网元,则分配用户面网元1的隧道端点标识给接入网,以及给UE分配IP地址的功能可以由资源管理节点来执行,如:控制面网元可以向资源管理节点请求用户面网元1的隧道端点标识和UE的IP地址,由资源管理节点分配用户面网元1的隧道端点标识给接入网,以及给UE分配IP地址,其中,资源管理网元的分配方法和控制面网元分配的方法相同。
S207:控制面网元将建立的连接上下文通知给用户面网元1,该连接上下文包含分配给接入网的用户面网元1的隧道端点标识和分配给UE的IP地址。
S208:UE向接入网发送上行业务数据。
S209:接入网接收到该上行业务数据后,将用户面网元1的隧道端点标识封装在该上行业务数据中,并将封装后的上行业务数据发往转发节点1。
S210:转发节点1接收到上行业务数据后,根据步骤204中获
取的用户面网元和隧道端点标识索引的对应关系、以及上行业务数据中的隧道端点标识,向用户面网元1发送上行业务数据。
可选的,转发节点1可以查询用户面网元和隧道端点标识索引的对应关系,找到上行业务数据中的隧道端点标识所在的隧道端点标识索引所对应的用户面网元,即用户面网元1,向用户面网元1发送上行业务数据。
S211:用户面网元1收到上行业务数据后,通过上行业务数据中的隧道端点标识等信息匹配到连接上下文,将包含隧道端点标识的协议层解封装后,转发该上行业务数据给报文数据网络。
否则,若用户面网元1收到上行业务数据后,通过上行业务数据中的隧道端点标识等信息未匹配到连接上下文,则不转发该上行业务数据给报文数据网络。
相对应的,作为发送上行业务数据的逆过程,UE还可以接收报文数据网络发送的下行业务数据,具体如图6所示:
S212:报文数据网络向转发节点3发送下行业务数据,该下行业务数据包含UE的IP地址。
S213:转发节点3接收到下行业务数据后,根据步骤104中获取的用户面网元和IP地址段的对应关系、以及下行业务数据中UE的IP地址,向用户面网元1发送下行业务数据。
可选的,转发节点3可以查询用户面网元和IP地址段的对应关系,找到下行业务数据中UE的IP地址所在的IP地址段所对应的用户面网元,即用户面网元1,向用户面网元1发送下行业务数据。
S214:用户面网元1收到下行业务数据后,通过下行业务数据中的UE的IP地址等信息匹配到连接上下文,并根据连接上下文中的信息,转发该下行业务数据给UE。
否则,若用户面网元1收到下行业务数据后,下行业务数据中的UE的IP地址等信息未匹配到连接上下文,则不转发该下行业务数据给接入网。
如此,通过图6所示的方案可以实现UE的业务数据由用户面
网元1进行转发。
然而,在实际应用中,用户面网元1可能出现异常(如故障或过载)现象,导致用户面网元1不能正常转发UE的业务数据,此时,为了保证业务数据传输不中断,在本发明实施例中,资源管理节点可以将原先分配给用户面节点1的用户设备IP地址段和隧道端点标识索引重新分配,即将用户面节点1的用户设备IP地址段作为地址池进行分段重分配,将所有或部分用户面节点1的用户设备IP地址段和隧道端点标识索引重新分配给其他正常的用户面节点,具体的,其实现过程如图7所示:
S301:资源管理节点检测到用户面网元1出现故障。
可选的,用户面网元1出现故障可以为用户面网元1宕机,或者可以为用户面网元1过载,其具体检测方法本发明实施例不进行限定,可以通过控制面网元等其他节点获知用户面网元1出现故障,也可以通过资源管理节点和用户面网元1之间的探测和监控获知用户面网元1出现故障。
其中,用户面网元1过载可以指:用户面网元1上的负载(如接入的业务数据包数量)大于等于预设阈值,或者用户面网元1上的中央处理器(英文:Central Processing Unit,CPU)负荷大于等于预设阈值,或者用户面网元1上的内存消耗大于等于预设阈值,预设阈值可以根据需要进行设置,本发明实施例对此不进行限定。
S302:资源管理节点将原来分配给用户面网元1的IP地址段作为IP地址池,将该IP地址池分为至少一个IP地址段,并根据至少一个IP地址段确定至少一个隧道端点标识索引。
其中,资源管理节点可以采用与步骤S102相同的步骤重新将原来分配给用户面网元1的IP地址段划分为至少一个IP地址段,并根据至少一个IP地址段确定至少一个隧道端点标识索引的过程。
可理解的是,资源管理节点也可以不执行IP地址段的重新分段,直接获取用户面网元1的已经分好的IP地址段以及IP地址段对应的隧道端点标识索引作为至少一个IP地址段和至少一个隧道端
点标识索引。
S303:资源管理节点将步骤S302中的至少一个IP地址段和至少一个隧道端点标识索引分配给图3中除用户面节点1之外的其他用户面网元。
例如:可以将至少一个IP地址段和至少一个隧道端点标识索引重新分配给用户面网元2、用户面网元3以及用户面网元4。
其中,步骤S303中的分配过程与步骤S103所述过程雷同,在此不再重复赘述,除第一用户面节点之外的其他用户面网元可以为一个或多个用户面网元。
需要说明的是,对于用户面网元1完全故障(即宕机)的场景,资源管理节点可以将用户面网元1的所有IP地址段和隧道端点标识索引重新分配给其他正常的用户面网元。对于用户面网元1过载的场景,资源管理节点可以将用户面网元1的部分IP地址段和隧道端点标识索引分配给其他用户面网元,以便减轻用户面网元1的过载状态。
S304:资源管理节点通知其他各个用户面网元,其被分配的用户设备IP地址段和隧道端点标识索引。
其中,步骤S304中的通知过程与步骤S203所述过程雷同,在此不再重复赘述。
S305:资源管理节点将用户面网元和IP地址段的对应关系通知给转发节点3,将用户面网元和隧道端点标识索引的对应关系通知给转发节点1。
可选的,资源管理节点可以直接将用户面网元和IP地址段的对应关系通知给转发节点3,将用户面网元和隧道端点标识索引的对应关系通知给转发节点1。
还可以将用户面网元、用户设备IP地址段、隧道端点标识索引三者间的对应关系通知给传输控制节点,所述对应关系即各个用户面网元标识,及其被分配的用户设备IP地址段和隧道端点标识索引,所述用户面网元标识可以为用户面网元IP地址,或者用户面网元ID
等可以唯一标识用户面网元的信息;
传输控制节点收到资源管理节点发送的用户面网元、用户设备IP地址段、和隧道端点标识索引的对应关系后,将用户面网元和IP地址段的对应关系通知给转发节点3,将用户面网元和隧道端点标识索引的对应关系通知给转发节点1。
其中,步骤S305中的通知过程与步骤S204所述过程雷同,在此不再重复赘述。
S306:资源管理节点将IP地址段、隧道端点标识索引、以及用户面网元三者间的对应关系通知给控制面网元。
需要说明的是,步骤S305和步骤S306的顺序可以变化,不依赖于图中的顺序。
S307:UE向接入网发送上行业务数据。
S308:接入网接收到该上行业务数据后,将用户面网元1的隧道端点标识封装在该上行业务数据中,并将封装后的上行业务数据包发往转发节点1。
S309:若原来分配给用户面网元1的隧道端点标识重新分配给用户面网元2,则转发节点1接收到上行业务数据后,根据步骤305中获取的用户面网元和隧道端点标识索引的对应关系、以及上行业务数据中的隧道端点标识,向用户面网元2发送上行业务数据。
S310:用户面网元2收到上行业务数据后,通过上行业务数据中的隧道端点标识等信息匹配到连接上下文,将包含隧道端点标识的协议层解封装后,转发该上行业务数据给报文数据网络。
相对应的,作为发送上行业务数据的逆过程,UE还可以接收报文数据网络发送的下行业务数据,具体如图5所示:
S311:报文数据网络向转发节点3发送下行业务数据,该下行业务数据包含UE的IP地址。
S312:若原来分配给用户面网元1的包含UE的IP地址的IP地址段重新分配给用户面网元2,则转发节点3接收到下行业务数据后,根据步骤305中获取的用户面网元和IP地址段的对应关系、
以及下行业务数据中UE的IP地址,向用户面网元2发送下行业务数据。
S313:用户面网元2收到下行业务数据包后,通过下行业务数据中的UE的IP地址等信息匹配到连接上下文,并根据连接上下文中的信息,转发该下行业务数据给UE。
其中,步骤S310和步骤S313中的连接上下文可以通过下述两种方式获取:
一、控制面网元接收到IP地址段、隧道端点标识索引、以及用户面网元三者间的对应关系后,将受影响的连接上下文发送给新的用户面网元。其中,受影响的连接上下文为原先在用户面网元1建立的连接上下文,因该上下文相关的用户设备IP地址和隧道端点标识被重新分配给用户面网元2,所以,将该连接上下文也发送给用户面网元2。
二、用户面网元2在接收到上行业务数据后,根据隧道端点标识无法查询到对应的连接上下文,则用户面网元2向控制面网元获取该连接上下文。可选的,用户面网元2将隧道端点标识携带在消息中发送给控制面网元,控制面网元根据隧道端点标识查找对应的连接上下文,并发送给用户面网元2。
三、用户面网元2在接收到下行业务数据后,根据UE的IP地址等信息无法查询到对应的连接上下文,则用户面网元2向控制面网元获取该连接上下文。可选的,用户面网元2将UE的IP地址携带在消息中发送给控制面网元,控制面网元根据UE的IP地址查找对应的连接上下文,并发送给用户面网元2。
如此,通过资源管理节点将分配给出现故障或过载的用户面网元的用户设备IP地址段和隧道端点标识索引重分配给其他通信正常的用户面网元,并将分配后的对应关系通过传输控制节点通知给转发节点,由转发节点根据对应关系将UE的业务数据包通过新的用户面网元进行转发,使得在用户面网元故障/过载等情况下,在不中断用户设备的业务的情况下,改变转发用户设备的业务数据包的用
户面网元。
然而,在实际应用中,随着网络的发展,网络内会新增用户面网元,如:网络内原先只有用户面节点1、2和3,后来新增用户面节点4,此时,资源管理节点可以将原先分配给用户面节点1、2和3的用户设备IP地址段和隧道端点标识索引重新分配,分给用户面网元4一些。其中,在将原有用户面网元的IP地址段和隧道端点标识索引重新分配给新增的用户面网元的过程中,为了尽量减少对原有用户面节点的影响,资源管理节点可以采用多种原则重新分配用户设备IP地址段和隧道端点标识索引。例如,在用户面节点1、2和3中选择负载过高的节点,将原先该用户面节点的用户设备IP地址段和隧道端点标识索引,分配一部分给新增的用户面节点4。又例如,在用户面节点1、2和3中选择容量最小的节点,将原先该用户面节点的用户设备IP地址段和隧道端点标识索引,分配一部分给新增的用户面节点4。
下面结合图8,以将原来分配给用户面网元1的IP地址段和隧道端点标识索引分配一部分给新增的用户面网元4为例,对发明实施例提供的技术方案进行介绍,如图8所示,该方法可以包括:
S401:资源管理节点将原来分配给用户面网元1的部分IP地址段作为IP地址池,将该IP地址池分为至少一个IP地址段,并根据至少一个IP地址段确定至少一个隧道端点标识索引。
其中,步骤S401可以采用与步骤S102相同的过程将原来分配给用户面网元1的部分IP地址段重新划分为至少一个IP地址段,并根据重新划分的至少一个IP地址段确定至少一个隧道端点标识索引。
可选的,资源管理节点也可以不执行IP地址段的重新分段,直接获取用户面网元1的已经分好的部分IP地址段以及IP地址段对应的隧道端点标识索引作为至少一个IP地址段和至少一个隧道端点标识索引。
比如,用户面网元1有5个IP地址段以及5个IP地址段对应
的隧道端点标识索引,则资源管理节点直接获取其中的3个IP地址段以及3个IP地址段对应的隧道端点标识索引。
S402:资源管理节点将步骤S301中的至少一个IP地址段和至少一个隧道端点标识索引分配给用户面网元4。
其中,步骤S302的分配过程与步骤S103所述过程雷同,在此不再详细赘述。
S403:资源管理节点通知用户面网元1和用户面网元4,其被分配的用户设备IP地址段和隧道端点标识索引。
其中,步骤S403的通知过程与步骤S203所述过程雷同,在此不再重复赘述。
S404:资源管理节点将用户面网元和IP地址段的对应关系通知给转发节点3,将用户面网元和隧道端点标识索引的对应关系通知给转发节点1。
资源管理节点可以通过传输控制节点将用户面网元和IP地址段的对应关系通知给转发节点3,将用户面网元和隧道端点标识索引的对应关系通知给转发节点1。
其中,步骤S404中的通知过程与步骤S304所述过程雷同,在此不再详细赘述。
S405:资源管理节点将IP地址段、隧道端点标识索引、以及用户面网元三者间的对应关系通知给控制面网元。
需要说明的是,步骤S404和步骤S405的顺序可以变化,不依赖于图中的顺序。
S406:UE向接入网发送上行业务数据。
S407:接入网接收到该上行业务数据后,将用户面网元1的隧道端点标识封装在该上行业务数据中,并将封装后的上行业务数据发往转发节点1。
S408:若原来分配给用户面网元1的隧道端点标识分配给用户面网元4,则转发节点1接收到上行业务数据后,根据步骤404中获取的用户面网元和隧道端点标识索引的对应关系、以及上行业务
数据中的隧道端点标识,向用户面网元4发送上行业务数据。
S409:用户面网元4收到上行业务数据包后,通过上行业务数据中的隧道端点标识等信息匹配到连接上下文,将包含隧道端点标识的协议层解封装后,转发该上行业务数据给报文数据网络。
相对应的,作为发送上行业务数据的逆过程,UE还可以接收报文数据网络发送的下行业务数据,具体如图8所示:
S410:报文数据网络向转发节点3发送下行业务数据,该下行业务数据包含UE的IP地址。
S411:若原来分配给用户面网元1的包含UE的IP地址的IP地址段分配给用户面网元4,则转发节点3接收到下行业务数据后,根据步骤404中获取的用户面网元和IP地址段的对应关系、以及下行业务数据中UE的IP地址,向用户面网元4发送下行业务数据。
S412:用户面网元4收到下行业务数据包后,通过下行业务数据中的UE的IP地址等信息匹配到连接上下文,并根据连接上下文中的信息,转发该下行业务数据给UE。
其中,步骤S409和步骤S412中的连接上下文可以通过下述两种方式获取:
一、控制面网元接收到IP地址段、隧道端点标识索引、以及用户面网元三者间的对应关系后,将受影响的连接上下文发送给新的用户面网元。即原先在用户面网元1建立的连接上下文,该上下文相关的用户设备IP地址和隧道端点标识被重新分配给用户面网元4后,将该连接上下文也发送给用户面网元4。
二、用户面网元4在接收到上行业务数据后,根据隧道端点标识无法查询到对应的连接上下文,则用户面网元4向控制面网元获取该连接上下文。可选的,用户面网元4将隧道端点标识携带在消息中发送给控制面网元,控制面网元根据隧道端点标识查找对应的连接上下文,并发送给用户面网元4。
三、用户面网元4在接收到下行业务数据后,根据UE的IP地址等信息无法查询到对应的连接上下文,则用户面网元4向控制面
网元获取该连接上下文。可选的,用户面网元4将UE的IP地址携带在消息中发送给控制面网元,控制面网元根据UE的IP地址查找对应的连接上下文,并发送给用户面网元4。
如此,在新增用户面网元的情况下,可以不中断用户设备的业务,将原有用户面网元的IP地址和隧道端点标识分配给其他新增的用户面网元,并将分配后的对应关系通过传输控制节点通知给转发节点,由转发节点根据对应关系将UE的业务数据包通过新增的用户面网元进行转发,以此实现用户面网元之间的负荷分担,同时,通过本发明的方法,可以在网络新增用户面网元时实现免配置,达到新增用户面网元的即插即用。
上述主要从资源管理节点、传输控制节点、用户面网元、控制面网元、转发节点、接入网、UE以及报文数据网络交互的角度对本发明实施例提供的业务传输方法进行了介绍。可以理解的是,上述节点或网元为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例、结合附图9~12对资源管理节点、传输控制节点、第一转发节点以及第二转发节点进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。需要说明的是,本发明实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下,图9为本发
明实施例中所涉及的资源管理节点的一种可能的结构示意图,如图9所示,资源管理节点10可以用于实施上述方法实施例中资源管理节点所执行的方法,该资源管理节点10可以包括:获取单元101、确定单元102、分配单元103、如:获取单元201用于支持资源管理节点执行图5中的过程S101,确定单元102用于支持资源管理节点执行图5中的过程S102,分配单元103用于支持资源管理节点执行图5中的过程S104和S105。进一步可选的,如图9所示,该资源管理节点10还可以包括:通知单元104,对应执行上述方法实施例中的一些过程。
其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再重复赘述。
在采用集成的单元的情况下,图9所示的获取单元101、确定单元102、分配单元103可以集成在一起作为一个处理模块,该处理模块用于对资源管理节点10的动作进行控制管理,例如,处理模块用于支持资源管理节点执行图5中的过程S101~S105、和/或用于本文所描述的技术的其它过程。通知单元104可以集成在通信模块中,用于支持资源管理节点10与其他网络实体的通信。资源管理节点10还可以包括存储模块,用于存储资源管理节点10的程序代码和数据。其中,处理模块可以为图4所示的资源管理节点10的实体结构中的处理器1011,可以是处理器或控制器,例如可以是CPU,通用处理器,DSP,ASIC,FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信模块可以是图4所示的资源管理节点10的实体结构中的收发器1013,或者可以是收发电路或通信接口等。存储模块可以是图4所示的资源管理节点10的实体结构中的存储器。
在采用对应各个功能划分各个功能模块的情况下,图10为本发
明实施例中所涉及的传输控制节点的一种可能的结构示意图,如图10所示,传输控制节点20可以用于实施上述方法实施例中传输控制节点所执行的方法,该传输控制节点20可以包括:获取单元201、通知单元202;获取单元用于支持传输控制节点20获取资源控制节点10通知的IP地址、隧道端点标识索引、以及用户面网元三者之间的对应关系,通知单元202用于支持传输控制节点20将IP地址与用户面网元间的对应关系通知给第一转发节点,以及用于支持传输控制节点20隧道端点标识索引与用户面网元间的对应关系通知给第二转发节点。
其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再重复赘述。
在采用集成的单元的情况下,图10所示的获取单元201、通知单元202可以集成在通信模块中,用于支持传输控制节点20与其他网络实体的通信。传输控制节点20还可以包括处理模块、存储模块,处理模块用于实现传输控制节点20中的控制功能,用于存储传输控制节点20的程序代码和数据。其中,处理模块可以为传输控制节点20的实体结构中的处理器,可以是处理器或控制器,例如可以是CPU,通用处理器,DSP,ASIC,FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信模块可以是传输控制节点的实体结构中的收发器,或者可以是收发电路或通信接口等。存储模块可以是传输控制节点的实体结构中的存储器。
在采用对应各个功能划分各个功能模块的情况下,图11为本发明实施例中所涉及的第一转发节点的一种可能的结构示意图,如图11所示,第一转发节点30可以用于实施上述方法实施例中第一转发节点所执行的方法,该第一转发节点30可以包括:获取单元301、发送单元302;获取单元用于支持第一转发节点30执行图5所示的
步骤S105,发送单元302用于支持第一转发节点30执行图5所示的步骤S107。
其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再重复赘述。
在采用集成的单元的情况下,图11所示的获取单元301、发送单元302可以集成在通信模块中,用于支持第一转发节点30与其他网络实体的通信。第一转发节点30还可以包括处理模块、存储模块,处理模块用于实现第一转发节点30中的控制功能,用于存储第一转发节点30的程序代码和数据。其中,处理模块可以为第一转发节点30的实体结构中的处理器,可以是处理器或控制器,例如可以是CPU,通用处理器,DSP,ASIC,FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信模块可以是第一转发节点的实体结构中的收发器,或者可以是收发电路或通信接口等。存储模块可以是第一转发节点的实体结构中的存储器。
在采用对应各个功能划分各个功能模块的情况下,图12为本发明实施例中所涉及的第二转发节点的一种可能的结构示意图,如图12所示,第二转发节点40可以用于实施上述方法实施例中第二转发节点所执行的方法,该第二转发节点40可以包括:获取单元401、发送单元402;获取单元用于支持第二转发节点40执行图5所示的步骤S104,发送单元402用于支持第二转发节点40执行图5所示的步骤S106。
其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再重复赘述。
在采用集成的单元的情况下,图12所示的获取单元401、发送单元402可以集成在通信模块中,用于支持第二转发节点40与其他网络实体的通信。第二转发节点40还可以包括处理模块、存储模块,
处理模块用于实现第二转发节点40中的控制功能,用于存储第二转发节点40的程序代码和数据。其中,处理模块可以为第二转发节点40的实体结构中的处理器,可以是处理器或控制器,例如可以是CPU,通用处理器,DSP,ASIC,FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信模块可以是第二转发节点的实体结构中的收发器,或者可以是收发电路或通信接口等。存储模块可以是第二转发节点的实体结构中的存储器。
再一方面,本发明实施例还提供一种业务传输***,如图13所示,该业务传输***可以包括:上述任一实施例所述的资源管理节点10、传输控制节点20、第一转发节点30、第二转发节点40、UE、用户面网元以及报文数据网络等设备。
本发明实施例提供的业务传输***,实现上述图5~图8所示的业务传输方法,因此,可以达到与上述业务传输方法相同的有益效果,此处不再重复赘述。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的***,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的***,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分
开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络设备上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本发明各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个功能单元独立存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元,可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本发明各个实施例所述方法的部分步骤。而前述的存储介质包括:通用串行总线(英文:Universal Serial Bus,USB)闪存驱动器(英文:USB flash drive)、移动硬盘、只读存储器(英文:read-only memory,ROM)、随机存取存储器(英文:random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是:以上实施例仅用以说明本发明的技术方案,而非对其限制;尽管参照前述实施例对本发明进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案脱离权利要求的范围。
Claims (33)
- 一种业务传输方法,其特征在于,所述方法包括:资源管理节点获取IP地址池;所述资源管理节点将所述IP地址池分为至少一个IP地址段,根据所述至少一个IP地址段确定至少一个隧道端点标识索引;所述资源管理节点将所述至少一个IP地址段和所述至少一个隧道端点标识索引分配给至少一个用户面网元。
- 根据权利要求1所述的方法,其特征在于,所述方法还包括:所述资源管理节点将所述IP地址段与所述用户面网元的对应关系通知给第一转发节点;所述资源管理节点将所述隧道端点标识索引与所述用户面网元间的对应关系通知给第二转发节点。
- 根据权利1所述的方法,其特征在于,所述方法还包括:所述资源管理节点将所述IP地址段、所述隧道端点标识索引、所述用户面网元间的对应关系通知给传输控制节点;所述对应关系用于:通知所述传输控制节点将所述IP地址段与所述用户面网元的对应关系通知给第一转发节点,将所述隧道端点标识索引与所述用户面网元间的对应关系通知给第二转发节点。
- 根据权利要求3所述的方法,其特征在于,所述IP地址段、所述隧道端点标识索引、所述用户面网元间的对应关系包括:所述IP地址段、所述隧道端点标识索引、所述用户面网元标识的对应关系;所述用户面网元标识包括所述用户面网元的IP地址,或者所述用户面网元的标识ID。
- 根据权利要求1-4任一项所述的方法,其特征在于,所述资源管理节点将所述至少一个IP地址段和所述至少一个隧道端点标识索引分配给至少一个用户面网元,包括:所述资源管理节点根据用户面网元的信息,将所述至少一个IP地址段和所述至少一个隧道端点标识索引分配给所述至少一个用户 面网元;所述用户面网元的信息包括:所述资源管理节点所在网络内可用的用户面网元的数量和/或用户面网元的容量。
- 根据权利要求1-4任一项所述的方法,其特征在于,所述资源管理节点将所述至少一个IP地址段和所述至少一个隧道端点标识索引分配给至少一个用户面网元,包括:所述资源管理节点将所述至少一个IP地址段和所述至少一个隧道端点标识索引分配给新增的用户面网元。
- 根据权利要求1所述的方法,其特征在于,所述资源管理节点获取IP地址池,包括:所述资源管理节点从操作维护网元O&M获取所述IP地址池。
- 根据权利要求1所述的方法,其特征在于,所述资源管理节点获取IP地址池,包括:所述资源管理节点获取分配给第一用户面网元的部分或者全部IP地址段,将分配给所述第一用户面网元的部分或者全部IP地址段作为所述IP地址池。
- 根据权利要求8所述的方法,其特征在于,所述资源管理节点将所述至少一个IP地址段和所述至少一个隧道端点标识索引分配给至少一个用户面网元,包括:所述资源管理节点将所述一个IP地址段和所述至少一个隧道端点标识索引分配给除第一用户面网元之外的至少一个用户面网元。
- 根据权利要求1-9任一项所述的方法,其特征在于,所述IP地址段,以及根据所述IP地址段确定的隧道端点标识索引分配给同一个用户面网元。
- 一种业务传输方法,其特征在于,所述方法包括:传输控制节点获取资源管理节点发送的IP地址段、隧道端点标识索引、用户面网元间的对应关系;所述传输控制节点将所述IP地址段与所述用户面网元的对应关系通知给第一转发节点;所述传输控制节点将所述隧道端点标识索引与所述用户面网元间的对应关系通知给第二转发节点。
- 根据权利要求11所述的方法,其特征在于,所述IP地址段、所述隧道端点标识索引、所述用户面网元间的对应关系包括:所述IP地址段、所述隧道端点标识索引、所述用户面网元标识的对应关系;所述用户面网元标识包括所述用户面网元的IP地址,或者所述用户面网元的标识ID。
- 一种业务传输方法,其特征在于,所述方法包括:第一转发节点获取IP地址段与用户面网元之间的对应关系;所述第一转发节点根据所述IP地址段与所述用户面网元之间的对应关系,向所述用户面网元转发报文数据网络发送的下行业务数据。
- 根据权利要求13所述的方法,其特征在于,所述第一转发节点获取IP地址段与用户面网元之间的对应关系,包括:所述第一转发节点获取资源管理节点通知的IP地址段与用户面网元之间的对应关系;或者,所述第一转发节点获取传输控制节点通知的IP地址段与用户面网元之间的对应关系。
- 一种业务传输方法,其特征在于,所述方法包括:第二转发节点获取隧道端点标识索引与用户面网元之间的对应关系;所述第二转发节点根据所述隧道端点标识索引与所述用户面网元之间的对应关系,向所述用户面网元转发接入网发送的上行业务数据。
- 根据权利要求15所述的方法,其特征在于,所述第二转发节点获取隧道端点标识索引与用户面网元之间的对应关系,包括:所述第二转发节点获取资源管理节点通知的隧道端点标识索引与用户面网元之间的对应关系;或者,所述第二转发节点获取传输控制节点通知的隧道端点标识索引与用户面网元之间的对应关系。
- 一种资源管理节点,其特征在于,所述资源管理节点包括:获取单元,用于获取IP地址池;确定单元,用于将所述获取单元获取到的IP地址池分为至少一个IP地址段,根据所述至少一个IP地址段确定至少一个隧道端点标识索引;分配单元,用于将所述确定单元确定出的至少一个IP地址段和所述至少一个隧道端点标识索引分配给至少一个用户面网元。
- 根据权利要求17所述的资源管理节点,其特征在于,所述资源管理节点还包括:通知单元,将所述分配单元分配好的IP地址段与用户面网元的对应关系通知给第一转发节点;以及,所述分配单元分配好的隧道端点标识索引与用户面网元间的对应关系通知给第二转发节点。
- 根据权利17所述的资源管理节点,其特征在于,所述资源管理节点还包括:通知单元,用于将所述分配单元分配好的IP地址段、隧道端点标识索引、用户面网元间的对应关系通知给传输控制节点;所述对应关系用于:通知所述传输控制节点将所述IP地址段与所述用户面网元的对应关系通知给第一转发节点,将所述隧道端点标识索引与所述用户面网元间的对应关系通知给第二转发节点。
- 根据权利要求19所述的资源管理节点,其特征在于,所述IP地址段、所述隧道端点标识索引、所述用户面网元间的对应关系包括:所述IP地址段、所述隧道端点标识索引、所述用户面网元标识的对应关系;所述用户面网元标识包括所述用户面网元的IP地址,或者所述用户面网元的标识ID。
- 根据权利要求17-20任一项所述的资源管理节点,其特征在于,所述分配单元具体用于:根据用户面网元的信息,将所述至少一个IP地址段和所述至少一个隧道端点标识索引分配给所述至少一个用户面网元;所述用户面网元的信息包括:所述资源管理节点所在网络内可用的用户面网元的数量和/或用户面网元的容量。
- 根据权利要求17-20任一项所述的资源管理节点,其特征在于,所述资源管理节点具体用于:将所述至少一个IP地址段和所述至少一个隧道端点标识索引分配给新增的用户面网元。
- 根据权利要求17所述的资源管理节点,其特征在于,所述获取单元具体用于:从操作维护网元O&M获取所述IP地址池。
- 根据权利要求17所述的资源管理节点,其特征在于,所述获取单元具体用于:获取分配给第一用户面网元的部分或者全部IP地址段,将分配给所述第一用户面网元的部分或者全部IP地址段作为所述IP地址池。
- 根据权利要求24所述的资源管理节点,其特征在于,所述分配单元具体用于:将所述一个IP地址段和所述至少一个隧道端点标识索引分配给除第一用户面网元之外的至少一个用户面网元。
- 根据权利要求17-25任一项所述的资源管理节点,其特征在于,所述IP地址段,以及根据所述IP地址段确定的隧道端点标识索引分配给同一个用户面网元。
- 一种传输控制节点,其特征在于,所述传输控制节点包括:获取单元,用于获取资源管理节点发送的IP地址段、隧道端点标识索引、用户面网元间的对应关系;通知单元,用于将所述获取单元获取到的IP地址段与用户面网元的对应关系通知给第一转发节点、以及将隧道端点标识索引与用户面网元间的对应关系通知给第二转发节点。
- 根据权利要求27所述的传输控制节点,其特征在于,所述IP地址段、所述隧道端点标识索引、所述用户面网元间的对应关系包括:所述IP地址段、所述隧道端点标识索引、所述用户面网元标识的对应关系;所述用户面网元标识包括所述用户面网元的IP地址,或者所述用户面网元的标识ID。
- 一种第一转发节点,其特征在于,所述第一转发节点包括:获取单元,用于获取IP地址段与用户面网元之间的对应关系;发送单元,用于根据所述获取单元获取到的IP地址段与用户面网元之间的对应关系,向所述用户面网元转发报文数据网络发送的下行业务数据。
- 根据权利要求29所述的第一转发节点,其特征在于,所述获取单元,具体用于:获取资源管理节点通知的IP地址段与用户面网元之间的对应关系;或者,获取传输控制节点通知的IP地址段与用户面网元之间的对应关系。
- 一种第二转发节点,其特征在于,所述第二转发节点包括:获取单元,用于获取隧道端点标识索引与用户面网元之间的对应关系;发送单元,用于根据所述获取单元获取到的隧道端点标识索引与用户面网元之间的对应关系,向所述用户面网元转发接入网发送的上行业务数据。
- 根据权利要求31所述的第二转发节点,其特征在于,所述获取单元,具体用于:获取资源管理节点通知的隧道端点标识索引与用户面网元之间的对应关系;或者,获取传输控制节点通知的隧道端点标识索引与用户面网元之间的对应关系。
- 一种业务传输***,其特征在于,包括:如权利要求17-26任一项所述的资源管理节点、如权利要求27-28任一项所述的传输控制节点、如权利要求29-30任一项所述的第一转发节点、如权利要求31-32任一项所述的第二转发节点、接入网、报文数据网络以及用户设备UE。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201680089779.6A CN109804710B (zh) | 2016-09-30 | 2016-09-30 | 一种业务传输方法、设备及*** |
EP16917432.3A EP3512300B1 (en) | 2016-09-30 | 2016-09-30 | Service transmission based on correspondence among tunnel endpoint identifier index, user equipment ip address segment and user plane network element |
PCT/CN2016/101404 WO2018058682A1 (zh) | 2016-09-30 | 2016-09-30 | 一种业务传输方法、设备及*** |
US16/370,638 US10979285B2 (en) | 2016-09-30 | 2019-03-29 | Service transmission method, device, and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2016/101404 WO2018058682A1 (zh) | 2016-09-30 | 2016-09-30 | 一种业务传输方法、设备及*** |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/370,638 Continuation US10979285B2 (en) | 2016-09-30 | 2019-03-29 | Service transmission method, device, and system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018058682A1 true WO2018058682A1 (zh) | 2018-04-05 |
Family
ID=61762421
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2016/101404 WO2018058682A1 (zh) | 2016-09-30 | 2016-09-30 | 一种业务传输方法、设备及*** |
Country Status (4)
Country | Link |
---|---|
US (1) | US10979285B2 (zh) |
EP (1) | EP3512300B1 (zh) |
CN (1) | CN109804710B (zh) |
WO (1) | WO2018058682A1 (zh) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11659611B2 (en) * | 2018-03-26 | 2023-05-23 | Telefonaktiebolaget LM Ericsson (pub!) | Detection and handling of failure on user plane path |
WO2020181746A1 (en) * | 2019-03-08 | 2020-09-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for user plane path failure and recovery handling |
CN111131062B (zh) * | 2019-12-31 | 2023-09-05 | 深信服科技股份有限公司 | 分组优化方法、终端、装置及存储介质 |
CN111556112A (zh) * | 2020-04-21 | 2020-08-18 | 成都安易迅科技有限公司 | 数据传输方法、装置、电子设备及存储介质 |
CN114079649A (zh) * | 2020-08-19 | 2022-02-22 | 华为技术有限公司 | 地址分配方法、设备及*** |
CN113766569B (zh) * | 2021-09-09 | 2024-03-15 | 阿里巴巴达摩院(杭州)科技有限公司 | 数据传输方法、设备、***及存储介质 |
US20240223477A1 (en) * | 2022-01-21 | 2024-07-04 | Rakuten Mobile, Inc. | System and method for rogue user plane detection |
CN116847475A (zh) * | 2022-03-24 | 2023-10-03 | 华为技术有限公司 | 一种发送数据包的方法、通信装置及通信*** |
CN115065602B (zh) * | 2022-06-10 | 2024-06-18 | 上海赛连信息科技有限公司 | 分布式***网元控制方法及其装置 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7191235B1 (en) * | 2002-11-26 | 2007-03-13 | Cisco Technology, Inc. | System and method for communicating data in a loadbalancing environment |
CN101640894A (zh) * | 2008-08-01 | 2010-02-03 | ***通信集团公司 | 拥塞检测方法及媒体网关、移动交换中心服务器 |
CN102014039A (zh) * | 2009-09-07 | 2011-04-13 | 华为技术有限公司 | 数据传输方法和接入点 |
CN103139752A (zh) * | 2011-12-01 | 2013-06-05 | 中兴通讯股份有限公司 | 传输通道表修改方法及装置 |
CN103945560A (zh) * | 2013-01-17 | 2014-07-23 | 中兴通讯股份有限公司 | 小数据传输路径的建立方法及***、基站、服务网关 |
Family Cites Families (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB0011913D0 (en) * | 2000-05-17 | 2000-07-05 | Nokia Networks Oy | Connections in a communication system |
AU2000250743A1 (en) * | 2000-05-31 | 2001-12-11 | Nokia Corporation | Method and apparatus for generating a connection identification |
US7155740B2 (en) * | 2000-07-13 | 2006-12-26 | Lucent Technologies Inc. | Method and apparatus for robust NAT interoperation with IPSEC'S IKE and ESP tunnel mode |
NO20014865D0 (no) * | 2001-10-05 | 2001-10-05 | Ericsson Telefon Ab L M | Optimalisering av handover-prosedyrer i GPRS |
NO20020290D0 (no) * | 2002-01-18 | 2002-01-18 | Ericsson Telefon Ab L M | Fremgangsmåte ved roaming i mobilnett |
NO20020667D0 (no) * | 2002-02-11 | 2002-02-11 | Ericsson Telefon Ab L M | Fremgangsmåte for å unngå unödig okkupering av ressurser i pakkesvitsjede mobilnett |
US8824430B2 (en) * | 2004-01-31 | 2014-09-02 | Athonet Srl | Wireless mobility gateway |
US7864686B2 (en) * | 2004-05-25 | 2011-01-04 | Cisco Technology, Inc. | Tunneling scheme for transporting information over a cable network |
US20070213058A1 (en) * | 2006-03-08 | 2007-09-13 | Interdigital Technology Corporation | Method and apparatus for supporting handoff and serving radio network subsystem relocation procedures in a single tunnel gprs-based wireless communication system |
TW200746760A (en) * | 2006-04-19 | 2007-12-16 | Interdigital Tech Corp | Method and apparatus for supporting routing area update procedures in a long term evolution general packet radio service tunneling protocol-based system |
US8036230B2 (en) * | 2007-11-05 | 2011-10-11 | Cisco Technology, Inc. | System and method for providing single IP tunnel |
CN101459905A (zh) * | 2008-06-27 | 2009-06-17 | 中兴通讯股份有限公司 | Isr去激活方法及isr去激活指示装置 |
US20100260098A1 (en) * | 2009-04-10 | 2010-10-14 | Qualcomm Incorporated | Header compression for ip relay nodes |
CN101945429B (zh) * | 2009-07-08 | 2014-09-17 | 华为技术有限公司 | 移动网络用户面数据路由的方法、装置和*** |
US8259571B1 (en) * | 2010-03-26 | 2012-09-04 | Zscaler, Inc. | Handling overlapping IP addresses in multi-tenant architecture |
US8578035B2 (en) * | 2010-09-27 | 2013-11-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Technique for relocating a serving gateway associated to a user equipment |
EP2687047B1 (en) * | 2011-03-18 | 2018-11-07 | Alcatel Lucent | System and method for session restoration at geo-redundant gateways |
US8650279B2 (en) * | 2011-06-29 | 2014-02-11 | Juniper Networks, Inc. | Mobile gateway having decentralized control plane for anchoring subscriber sessions |
US8635326B1 (en) * | 2011-09-29 | 2014-01-21 | Juniper Networks, Inc. | Mobile gateway having reduced forwarding state for anchoring mobile subscribers |
US9883441B2 (en) * | 2011-11-10 | 2018-01-30 | Nokia Technologies Oy | Method and apparatus to route packet flows over two transport radios |
US8923863B2 (en) * | 2011-12-19 | 2014-12-30 | Cisco Technology, Inc. | Maintaining signaling reduction mode in communication networks |
US8855071B1 (en) * | 2012-01-04 | 2014-10-07 | Juniper Networks, Inc. | Handling errors in subscriber session management within mobile networks |
WO2013161172A1 (ja) * | 2012-04-27 | 2013-10-31 | 日本電気株式会社 | 通信システム及び経路制御方法 |
CN103636283B (zh) * | 2012-06-29 | 2018-06-05 | 华为技术有限公司 | 网关***、设备和通信方法 |
WO2014000304A1 (zh) * | 2012-06-30 | 2014-01-03 | 华为技术有限公司 | 一种控制和转发解耦架构下的转发面隧道资源的管理方法 |
ES2869306T3 (es) * | 2014-03-19 | 2021-10-25 | Alcatel Lucent | Conmutación del punto de terminación del plano de usuario de enlace ascendente de una puerta de enlace de servicio para un portador en operación de conectividad dual |
EP3205178B1 (en) * | 2014-10-07 | 2018-02-28 | Telefonaktiebolaget LM Ericsson (publ) | Routing in a communications network having a distributed s/pgw architecture |
JPWO2016079989A1 (ja) * | 2014-11-21 | 2017-09-07 | 日本電気株式会社 | 通信装置及び通信方法 |
WO2016190641A1 (ko) * | 2015-05-22 | 2016-12-01 | 엘지전자(주) | 무선 통신 시스템에서 데이터 송수신 방법 및 이를 위한 장치 |
US11265935B2 (en) * | 2016-01-18 | 2022-03-01 | Samsung Electronics Co., Ltd. | Resource assignment for general packet radio service tunneling protocol (GTP) entities in 5G |
WO2017201722A1 (zh) * | 2016-05-26 | 2017-11-30 | 华为技术有限公司 | 一种通信控制的方法及相关网元 |
-
2016
- 2016-09-30 CN CN201680089779.6A patent/CN109804710B/zh active Active
- 2016-09-30 EP EP16917432.3A patent/EP3512300B1/en active Active
- 2016-09-30 WO PCT/CN2016/101404 patent/WO2018058682A1/zh unknown
-
2019
- 2019-03-29 US US16/370,638 patent/US10979285B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7191235B1 (en) * | 2002-11-26 | 2007-03-13 | Cisco Technology, Inc. | System and method for communicating data in a loadbalancing environment |
CN101640894A (zh) * | 2008-08-01 | 2010-02-03 | ***通信集团公司 | 拥塞检测方法及媒体网关、移动交换中心服务器 |
CN102014039A (zh) * | 2009-09-07 | 2011-04-13 | 华为技术有限公司 | 数据传输方法和接入点 |
CN103139752A (zh) * | 2011-12-01 | 2013-06-05 | 中兴通讯股份有限公司 | 传输通道表修改方法及装置 |
CN103945560A (zh) * | 2013-01-17 | 2014-07-23 | 中兴通讯股份有限公司 | 小数据传输路径的建立方法及***、基站、服务网关 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3512300A4 * |
Also Published As
Publication number | Publication date |
---|---|
US20190230060A1 (en) | 2019-07-25 |
EP3512300A1 (en) | 2019-07-17 |
CN109804710B (zh) | 2021-10-01 |
EP3512300B1 (en) | 2021-04-28 |
EP3512300A4 (en) | 2019-07-17 |
US10979285B2 (en) | 2021-04-13 |
CN109804710A (zh) | 2019-05-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018058682A1 (zh) | 一种业务传输方法、设备及*** | |
EP3557902B1 (en) | Information transmission method and apparatus | |
US9204361B2 (en) | Method and system for scalable and manageable non-access stratum (NAS) node selection function for evolved packet system | |
CN110365727B (zh) | 通信方法和相关装置 | |
EP3742785B1 (en) | Session management method and device | |
BR112020016723A2 (pt) | Sistema e método para contexto de ue e gerenciamento de contexto de sessão de pdu | |
WO2019158010A1 (zh) | 资源管理的方法、设备及*** | |
KR102392120B1 (ko) | Nf 구성요소의 예외를 처리하기 위한 방법 및 시스템, 그리고 기기 | |
EP3410752B1 (en) | Mobility management method, apparatus and system | |
CN106533973B (zh) | 分发业务消息的方法、设备和*** | |
CN113206894A (zh) | Dns服务器的发现方法、装置、计算机设备及存储介质 | |
EP4387287A1 (en) | Service processing method, apparatus and system | |
US10225191B2 (en) | Service packet distribution method and apparatus | |
JP6623268B1 (ja) | 制御プレーン機器、プログラム、システム及び情報処理装置 | |
JP2020022053A (ja) | 通信制御装置 | |
RU2679184C1 (ru) | Способ распределения ip-адресов в d2d коммуникации и устройство пользователя | |
US11108734B2 (en) | Error indication processing and system, and device | |
JP7344220B2 (ja) | アドレス割当方法および装置、コアネットワーク、ノード、ネットワークシステムならびに媒体 | |
CN105830408B (zh) | 脑裂情况期间的资源的分配 | |
JP2011130194A (ja) | Ipアドレス割当装置、補助装置、ipアドレス割当システム、ipアドレス割当方法、及びプログラム | |
WO2017128315A1 (zh) | 创建链路的方法及装置 | |
KR20220036614A (ko) | 네트워크장치 및 그 장치에서 수행되는 세션 로드 제어방법 | |
WO2018201305A1 (zh) | 无线接入技术类型的选择方法及接入网节点 | |
CN117858068A (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: 16917432 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: 2016917432 Country of ref document: EP Effective date: 20190411 |