WO2014056450A1 - Procédé, dispositif et système de gestion de supports - Google Patents

Procédé, dispositif et système de gestion de supports Download PDF

Info

Publication number: WO2014056450A1
Authority: WO; WIPO (PCT)
Prior art keywords: network; gateway; bearer; controller; forwarding
Prior art date: 2012-10-11
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.): Ceased

Application number

PCT/CN2013/085067

Other languages

English (en)

Chinese (zh)

Inventor

周娜

梁爽

霍玉臻

王静

Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)

ZTE Corp

Original Assignee

ZTE Corp

Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)

2012-10-11

Filing date

2013-10-11

Publication date

2014-04-17

2013-10-11 Application filed by ZTE Corp filed Critical ZTE Corp

2014-04-17 Publication of WO2014056450A1 publication Critical patent/WO2014056450A1/fr

2015-04-11 Anticipated expiration legal-status Critical

Status Ceased legal-status Critical Current

Classifications

- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels

Definitions

the present invention relates to the field of communications, and in particular to a bearer management method, apparatus, and system.
BACKGROUND OF THE INVENTION In order to maintain the competitiveness of the third generation mobile communication system in the communication field, the mobile communication service with faster speed, lower delay and more personalized is provided for the user, and the operating cost of the operator is also reduced, the third generation The 3rd Generation Partnership Project (3GPP) Standards Working Group is working on the Evolved Packet System (EPS).
the entire EPS system can be divided into two parts: the wireless access network and the core network.
a Home Subscriber Server (HSS) a Mobility Management Entity (MME), a Serving GPRS Support Node (SGSN), and a policy are included.
HSS Home Subscriber Server
MME Mobility Management Entity
SGSN Serving GPRS Support Node
policy Policy
the home subscriber server which contains all the functions of the Home Location Register (HLR), is the permanent storage location of the subscriber subscription data, and is located in the home network to which the subscriber subscribes.
the mobility management entity is the location where the user subscription data is stored in the current network, responsible for terminal-to-network non-access layer signaling management, terminal security verification function, terminal mobility management, user idle mode tracking and paging. Management functions and bearer management.
the service GPRS support node is a service support point for GERAN and UTRAN users to access the core network. It is similar in function to the mobility management entity and is responsible for user location update, paging management, and bearer management.
the service gateway is a gateway of the core network to the wireless system, and is responsible for the user plane bearer of the terminal to the core network, the data buffer in the terminal idle mode, the function of initiating the service request by the network side, the lawful interception and the packet data routing and forwarding function; It is responsible for counting the situation in which the user terminal uses the wireless network, and generates the CDR of the terminal using the wireless network, and transmits it to the charging gateway.
the packet data gateway is a gateway of the evolved system and the external packet data network of the system.
the General Packet Radio Service (GPRS) Gateway Support Node (Gateway GPRS Support Node, GGSN for short) supports the edge routing function of the GPRS network. That is, the GGSN is responsible for routing and forwarding data of the GPRS network. Firewall and filtering functions to protect the integrity of GPRS network data; GGSN also has a charging function.
GPRS General Packet Radio Service
the PGW contains all the functions of the GGSN, and the GGSN can be considered as a sub-function of the PGW and embedded in the PGW. Therefore, the SGSN can connect directly to the PGW and use the Gn/Gp interface.
a packet data network is an operator's IP service network, which provides users with the core network of the operator.
the policy charging rule function entity is a server in the evolution system that is responsible for providing rules for charging control, online credit control, threshold control, and quality of service (QoS) policies.
the radio access network includes a radio side network element, such as an E-UTRAN NodeB (eNB), which is mainly responsible for receiving and receiving radio signals, and communicating with the terminal through the air interface to manage radio resources and resource scheduling of the air interface. , access control.
eNB E-UTRAN NodeB
EPS Since the introduction of EPS from the 3GPP R8 phase in 2006, EPS has gradually introduced new functions after six years of development, and the introduction of each function almost involves the modification of these functional network elements. On the one hand, the upgrade cost of the operator network becomes higher. On the other hand, because different devices are provided by different device vendors, it is difficult to unify the different functions of different network elements for different functions.
Stanford University proposed an OpenFlow protocol, which uses a forwarding/control separation architecture.
the external control plane entity uses the OpenFlow protocol to control the forwarding plane device to implement various forwarding logics.
the main function of the forwarding plane device is based on The flow table sent by the OpenFlow controller performs controlled forwarding.
the behavior is standardized: Receive a packet, obtain the field value of the header, and use it as a keyword to search the flow table. After matching the corresponding entry, according to the table.
the instruction set in the item content transforms the message field, and after processing, forwards it to a logical or physical port according to the indication.
the protocol is further evolved to become a Software Defined Network (SDN), which can implement various complex network applications by software programming on the control plane, and the forwarding plane device does not need any change, because the control plane adopts a general-purpose server. + Universal operating system, and can be implemented using a common software programming tool or a scripting language such as Python, which makes the support of the new network protocol very simple, and the new technology deployment cycle is greatly shortened.
SDN Software Defined Network
the mobile communication system in the related art has undergone a series of functional enhancements, including the introduction of a shunting technology, and the enhancement of these functions requires a new protocol specification development period of 1-2 years, which is then implemented by the equipment supplier and performed by the operator. Testing, and then deployment, makes the introduction of new network features very long and costly.
the control separation architecture of OpenFlow is introduced into the mobile network, and the OpenFlow protocol is extended for the requirements of the mobile network. Therefore, in the evolution of the mobile network, the network that supports Openflow after the upgrade will coexist with the traditional network that does not support Openflow. In this case, it is necessary to consider how to communicate between the traditional network and the Openflow-enabled network.
the present invention provides a bearer management scheme to solve at least the problem of how to communicate between a communication network that does not support control and forwarding separation in the related art and a communication network that supports separate control and forwarding.
a bearer management method including: a controller receiving a request for a management bearer from a serving gateway in a first network; the controller according to the request for managing the bearer to the first A gateway management bearer of the forwarding layer in the second network, where the second network is a communication network that supports separation of the control layer from the forwarding layer.
the management bearer includes at least one of the following: establishing a bearer, modifying a bearer, and deleting a bearer.
the controller receives the Modifying a bearer request of the serving gateway in the first network; the controller modifying the bearer to the gateway of the forwarding layer in the second network according to the modify bearer request.
the modifying, by the controller, the bearer to the gateway of the forwarding layer in the second network according to the modify bearer request includes: the controller, according to the modify bearer request, to a forwarding layer in the second network The gateway updates the session with the serving gateway in the first network, and carries the tunnel information of the serving gateway in the first network.
the method further includes: the mobility management entity in the second network replying the context response to the mobility management entity in the first network a message, where the context response message carries the controller address in the second network to And an address of the gateway of the forwarding layer, where the controller address is used as a control plane address of the access gateway of the second network, and an address of the gateway of the forwarding layer is used as a user of the access gateway of the second network Face address.
the method further includes: during the attaching process of the terminal, the controller is configured by the controller The address and the address of the gateway of the forwarding layer are carried in a create session response message and sent to the mobility management entity in the second network.
the controller receives a create session request from the serving gateway in the first network; The controller creates a bearer to the gateway of the forwarding layer in the second network according to the create session request.
the creating, by the controller, the bearer to the gateway of the forwarding layer in the second network according to the create session request includes: the controller according to the create session request to the forwarding layer in the second network
the gateway creates a session with the serving gateway in the first network and carries tunnel information of the serving gateway in the first network.
the gateway of the forwarding layer is an AGW.
the controller is a control layer module separate from the forwarding layer.
a bearer management method including: a controller receiving a management session request from a mobility management entity in a second network or establishing a forwarding tunnel request; the controller according to the management The session request or the establishment of the forwarding tunnel request to the gateway of the forwarding layer in the second network to manage the session or establish a forwarding tunnel, wherein the managed session or the established forwarding tunnel is used to serve the serving gateway in the first network
the bearer is managed, and the second network is a communication network that supports separation of the control layer from the forwarding layer.
the management bearer includes at least one of the following: establishing a bearer, modifying a bearer, and deleting a bearer.
the controller receives an indirect data forwarding tunnel request from a mobility management entity in the second network; the controller is configured according to The creating an indirect data forwarding tunnel request establishes a forwarding tunnel to a gateway of a forwarding layer in the second network.
the controller according to the creating an indirect data forwarding tunnel request, establishing a forwarding tunnel to a gateway of a forwarding layer in the second network, includes: the controller, according to the creating an indirect data forwarding tunnel request, to the first The gateway of the forwarding layer in the second network establishes a session with the serving gateway in the first network, and carries the tunnel information of the serving gateway in the first network.
the method further includes: the controller is wireless to the second network
the side network element establishes a session and carries tunnel information of the gateway of the forwarding layer in the second network.
the method further includes: the controller moving through the second network The sex management entity sends the tunnel information of the gateway of the forwarding layer in the second network to the radio side network element in the second network.
the method further includes: the mobility management entity in the second network is in the first network
the mobility management entity sends a forward relocation request message, where the forward relocation request message carries the controller address in the second network and an address of a gateway of the forwarding layer,
the controller address is used as the control plane address of the access gateway of the second network
the address of the gateway of the forwarding layer is used as the user plane address of the access gateway of the second network.
the controller requests a gateway to a forwarding layer in the second network according to the creating an indirect data forwarding tunnel.
the method further includes: deleting the session between the controller and the mobility management entity in the second network; and deleting, by the controller, the gateway of the forwarding layer in the second network with the terminal relevant information.
the controller receives the tracking area update process when the terminal accesses the network through the access gateway in the first network, and the terminal is moved by the first network to the second network.
a create session request from a mobility management entity in the second network; the controller creates a session to a gateway of a forwarding layer in the second network according to the create session request.
the creating, by the controller, the session to the gateway of the forwarding layer in the second network according to the creating a session request comprises: the controller according to the creating a session request to a forwarding layer in the second network
the gateway creates a session with the access gateway in the first network; the controller sends a modify bearer request message to the access gateway in the first network, and carries a gateway of the forwarding layer in the second network Address and the address of the controller, the controller address is used as a control plane address of the access gateway of the second network, and the address of the gateway of the forwarding layer is used as a user of the access gateway of the second network Face address.
the controller receives a create session request from the mobility management entity in the second network; the controller is created according to the The session request creates a session to the gateway of the forwarding layer in the second network.
the creating, by the controller, the session to the gateway of the forwarding layer in the second network according to the creating a session request comprises: the controller according to the creating a session request to a forwarding layer in the second network The gateway creates a session with the access gateway in the first network.
the method further includes: the controller establishing a wireless side network element in the second network a session, and carrying tunnel information of a gateway of the forwarding layer in the second network.
the method further includes: the controller is used by the mobility management entity in the second network The radio side network element in the second network sends tunnel information of a gateway of the forwarding layer in the second network.
the method further comprises: releasing an indirect data forwarding tunnel between the controller and a mobility management entity in the second network; the controller deleting to a gateway of a forwarding layer in the second network Forward the session.
the controller Receiving a modified bearer request from the mobility management entity in the second network; the controller modifying the bearer to the gateway of the forwarding layer in the second network according to the modify bearer request.
the modifying, by the controller, the bearer to the gateway of the forwarding layer in the second network according to the modify bearer request includes: the controller, according to the modify bearer request, to a forwarding layer in the second network The gateway deletes the session associated with the serving gateway in the first network.
the controller receives a create session request from the mobility management entity in the second network; And the controller sends a setup session request to the access gateway in the first network according to the create session request, and carries an address of a forwarding layer of the second network and an address of the controller, where The controller address is used as the control plane address of the access gateway of the second network, and the address of the gateway of the forwarding layer is used as the user plane address of the access gateway of the second network; The gateway of the forwarding layer in the second network establishes a session with the access gateway in the first network.
the method further includes: the controller and the second network
the session is deleted between the mobility management entities; the controller deletes information related to the terminal to the gateway of the forwarding layer in the second network.
the gateway of the forwarding layer is an AGW.
the controller is a control layer module separate from the forwarding layer.
a bearer management device located in a controller, including: a first receiving module, configured to receive a request for a management bearer from a serving gateway in a first network; And configuring, according to the request for managing the bearer, a bearer to a gateway of a forwarding layer in the second network, where the second network is a communication network that supports a separation between the control layer and the forwarding layer.
the terminal accesses the network through the gateway of the forwarding layer in the second network, and the tracking area that the terminal moves from the second network to the first network
the first receiving module is further configured to receive a modify bearer request from the serving gateway in the first network, where the first management module is further configured to send the request to the second network according to the modify bearer request.
the gateway in the forwarding layer modifies the bearer.
the first receiving module is further configured to receive from the Creating a session request of the serving gateway in the first network; the first management module is further configured to create a bearer to the gateway of the forwarding layer in the second network according to the create session request.
a bearer management system including the bearer management device located in the controller, and further comprising: a mobility management entity located in the second network, wherein the second network
the mobility management entity includes: a first sending module, configured to reply a context response message to the mobility management entity in the first network, where the context response message carries the control in the second network
an address of the gateway of the forwarding layer the controller address is used as a control plane address of the access gateway of the second network
an address of the gateway of the forwarding layer is used as an access gateway of the second network User face address.
the bearer management device further includes: a second sending module, configured to send the controller address and an address of the gateway of the forwarding layer in a create session response message To the mobility management entity in the second network.
a bearer management apparatus located in a controller, comprising: a second receiving module, configured to receive a management session request or establish a forwarding tunnel from a mobility management entity in a second network a second management module, configured to manage a session or establish a forwarding tunnel to a gateway of a forwarding layer in the second network according to the management session request or establish a forwarding tunnel request, where the session or established location is managed
the forwarding tunnel is used to manage bearers to the serving gateway in the first network
the second network is a communication network that supports separation of the control layer from the forwarding layer.
the management bearer includes at least one of the following: establishing a bearer, modifying a bearer, and deleting a bearer.
the second receiving module is further configured to receive the received Establishing an indirect data forwarding tunnel request by the mobility management entity in the second network; the second management module is further configured to establish, according to the request for creating an indirect data forwarding tunnel, to a gateway of a forwarding layer in the second network Forward the tunnel.
the device further includes: a first session establishing module, configured to establish a session to the wireless side network element in the second network, and carry tunnel information of a gateway of the forwarding layer in the second network.
the device further includes: a third sending module, configured to send, by using a mobility management entity in the second network, a forwarding layer in the second network to a wireless side network element in the second network Tunnel information for the gateway.
a third sending module configured to send, by using a mobility management entity in the second network, a forwarding layer in the second network to a wireless side network element in the second network Tunnel information for the gateway.
the device in a case that the terminal accesses the network through the access gateway in the first network, the device further includes: a first deleting module, configured to be a mobility management entity in the second network The session is deleted; the second deletion module is configured to delete information related to the terminal to the gateway of the forwarding layer in the second network.
the management bearer includes at least one of: establishing a bearer, modifying a bearer, and deleting a bearer, the terminal accessing the network by using an access gateway in the first network, and the terminal is used by the first network
the second receiving module is further configured to receive a create session request from the mobility management entity in the second network; the second management module further sets A session is created for the gateway of the forwarding layer in the second network in accordance with the create session request.
the device further includes: a fourth sending module, configured to send a modify bearer request message to the access gateway in the first network, and carry an address and a gateway of the forwarding layer in the second network
the address of the controller, the controller address is used as the control plane address of the access gateway of the second network
the address of the gateway of the forwarding layer is used as the user plane address of the access gateway of the second network.
the management bearer includes at least one of the following: establishing a bearer, modifying a bearer, and deleting a bearer.
the second receiving module is further configured to receive the received Creating a session request of the mobility management entity in the second network; the second management module is further configured to create a session to the gateway of the forwarding layer in the second network according to the create session request.
the device further includes: a second session establishing module, configured to establish a session to the wireless side network element in the second network, and carry tunnel information of a gateway of the forwarding layer in the second network.
the device further includes: a fifth sending module, configured to send, by using a mobility management entity in the second network, a forwarding layer in the second network to a wireless side network element in the second network Tunnel information for the gateway.
the device further includes: a release module, configured to release an indirect data forwarding tunnel between the mobility management entity in the second network; and a third deletion module, configured to forward to the second network
the layer's gateway deletes the forwarding session.
the management bearer includes at least one of: establishing a bearer, modifying a bearer, and deleting a bearer, the terminal accessing the network by using a gateway of a forwarding layer in the second network, and the terminal is configured by the first network
the second receiving module is further configured to receive a modified bearer request from the mobility management entity in the second network; the second management module further And being configured to modify the bearer to the gateway of the forwarding layer in the second network according to the modify bearer request.
the management bearer includes at least one of: establishing a bearer, modifying a bearer, and deleting a bearer, where the terminal is attached to the access gateway in the first network by the second network,
the second receiving module is further configured to receive a create session request from the mobility management entity in the second network; the second management module is further configured to connect to the first network according to the create session request
the ingress gateway sends a setup session request, and carries an address of the gateway of the forwarding layer in the second network and an address of the controller, where the controller address is used as a control plane address of the access gateway of the second network, The address of the gateway of the forwarding layer is used as the user plane address of the access gateway of the second network, and a session is established with the gateway of the forwarding layer in the second network and the access gateway in the first network.
the device further includes: a fourth deleting module, configured to delete a session with the mobility management entity in the second network; and a fifth deleting module, configured to be in a forwarding layer in the second network
the gateway deletes information related to the terminal.
a bearer management system including the bearer management device located in the controller, and a mobility management entity located in the second network, where the second network is
the mobility management entity includes: a sixth sending module, configured to send a forward relocation request message to the mobility management entity in the first network, where the forward relocation request message carries the The controller address in the second network and the address of the gateway of the forwarding layer, the controller address is used as a control plane address of the access gateway of the second network, and the address of the gateway of the forwarding layer is used as the The user plane address of the access gateway of the second network.
the controller receives the request for the management bearer from the serving gateway in the first network; the controller manages the bearer to the gateway of the forwarding layer in the second network according to the request for managing the bearer, wherein the second network
the problem of how to communicate between the communication network that does not support control and forwarding separation and the communication network that supports control and forwarding separation is solved in the related art, and the support is improved. Control and compatibility of communication networks separated and forwarded.
FIG. 1 is a flowchart of a bearer management method according to an embodiment of the present invention
FIG. 2 is a structural block diagram of a bearer management device according to an embodiment of the present invention
FIG. 3 is a bearer management system according to an embodiment of the present invention
FIG. 4 is a block diagram showing a preferred configuration of a bearer management system according to an embodiment of the present invention
FIG. 5 is a flowchart of another bearer management method according to an embodiment of the present invention
FIG. 6 is another flowchart according to an embodiment of the present invention.
FIG. 7 is a block diagram of a preferred structure of another bearer management device according to an embodiment of the present invention
FIG. 8 is a block diagram of a preferred structure of another bearer management device according to an embodiment of the present invention
9 is a block diagram 3 of a preferred structure of another bearer management device according to an embodiment of the present invention
FIG. 10 is a block diagram of a preferred structure of another bearer management device according to an embodiment of the present invention
FIG. 11 is an embodiment of the present invention.
a preferred block diagram of another bearer management device is shown in FIG. 5; FIG.
FIG. 12 is a block diagram of another preferred structure of a bearer management device according to an embodiment of the present invention.
FIG. 13 is a block diagram showing another configuration of a bearer management system according to an embodiment of the present invention;
FIG. 14 is a schematic diagram of a scenario 1 of a wireless communication network according to a preferred embodiment of the present invention;
FIG. 16 is a schematic diagram of a scenario 3 of a wireless communication network in accordance with a preferred embodiment of the present invention;
FIG. 17 is a schematic diagram of a scenario 4 of a wireless communication network according to a preferred embodiment of the present invention;
FIG. 18 is a flowchart of a process for updating a tracking area by a user on the basis of a scenario-based system according to a first embodiment of the present invention
FIG. 20 is a flowchart of a process for updating a tracking area by a user on the basis of the scenario 2 system according to the second embodiment of the present invention
FIG. 22 is a flow chart of the user performing the attachment and tracking area update process on the basis of the scenario three system according to the third embodiment of the present invention
FIG. 23 is a flowchart of a user performing a handover process on the basis of the scenario three system according to the third embodiment of the present invention
FIG. 24 is a diagram showing the user attaching and tracking on the basis of the scenario four system according to the fourth embodiment of the present invention
a region update process flowchart is based on the scenario four system according to the fourth embodiment of the present invention, User switching process flow of FIG. BEST MODE FOR CARRYING OUT THE INVENTION
FIG. BEST MODE FOR CARRYING OUT THE INVENTION User switching process flow of FIG. BEST MODE FOR CARRYING OUT THE INVENTION
Step S102 the controller receives a A request for management of a service gateway in a network.
Step S104 The controller manages the bearer to the gateway of the forwarding layer in the second network according to the request for managing the bearer, where the second network is a communication network that separates the control layer from the forwarding layer.
the controller in the communication network separated by the control and forwarding receives the request for the management bearer from the serving gateway in the traditional network, and the controller goes to the control layer and the forwarding layer.
the forwarding layer gateway management bearer in the separated communication network realizes the management bearer interaction between the traditional communication network that does not support control and forwarding separation and the communication network that supports control and forwarding separation, and solves the traditional unsupported in the related art.
the problem of how to communicate between the communication network separated from the control and the communication network that supports the separation of control and forwarding improves the compatibility and scope of the communication network supporting the separation of control and forwarding.
the gateway of the forwarding layer in the foregoing second network may be an AGW, and the controller may be a control layer module separated from the forwarding layer.
the management bearer may include at least one of the following: establishing a bearer, modifying a bearer, and deleting a bearer.
the manner of modifying the bearer may be: controlling, during the tracking area update process that the terminal accesses the network through the gateway of the forwarding layer in the second network, and the terminal moves from the second network to the first network,
the device may receive a modified bearer request from the serving gateway in the first network; the controller modifies the bearer to the gateway of the forwarding layer in the second network according to the modified bearer request.
the controller may update the session with the serving gateway in the first network to the gateway of the forwarding layer in the second network according to the modify bearer request, and carry the tunnel information of the serving gateway in the first network.
the mobility management entity in the second network may reply the context response message to the mobility management entity in the first network, where
the context response message carries the address of the controller in the second network and the address of the gateway of the forwarding layer, the controller address is used as the control plane address of the access gateway of the second network, and the address of the gateway of the forwarding layer is used as the address of the second network.
User plane address of the access gateway In this way, the service gateway in the first network can conveniently obtain the address of the controller and the address of the gateway of the forwarding layer. Of course, the controller address and the address of the gateway of the forwarding layer can be notified to the first by other means.
a service gateway in the network is notified to the first by other means.
the mobility management entity in the second network may obtain the address of the controller and the address of the gateway of the forwarding layer in the process of attaching the terminal, for example, the controller carries the controller address and the address of the gateway of the forwarding layer at The creation session response message is sent to the mobility management entity in the second network.
the manner of creating a bearer may be: in a process in which the terminal is connected to the gateway of the forwarding layer in the second network by the first network, the controller may receive the serving gateway from the first network. Creating a session request; the controller creates a bearer according to the create session request to the gateway of the forwarding layer in the second network.
the controller may create a session with the serving gateway in the first network to the gateway of the forwarding layer in the second network according to the create session request, and carry the tunnel information of the serving gateway in the first network.
a bearer management device is also provided, which is located in the controller.
FIG. 2 is a structural block diagram of the bearer management device according to the embodiment of the present invention. The method includes: a first receiving module 22 and a first management module 24, and each module is described in detail below.
the first receiving module 22 is configured to receive a request for the management bearer from the serving gateway in the first network.
the first management module 24 is connected to the first receiving module 22, and is configured to be in the second network according to the request for managing the bearer.
the gateway management bearer of the forwarding layer where the second network is a communication network that supports separation of the control layer and the forwarding layer.
the controller in the communication network (referred to as the second network) separated from the control and forwarding receives the request for managing the bearer from the serving gateway in the traditional network through the first receiving module 22, the controller
the forwarding layer gateway management bearer in the communication network separated from the control layer and the forwarding layer by the first management module 24 implements a management bearer between the communication network that does not support control and forwarding separation and the communication network that supports control and forwarding separation.
the interaction solves the problem of how to communicate between the communication network that does not support separation of control and forwarding and the communication network that supports separation of control and forwarding in the related art, and improves the compatibility of the communication network supporting control and forwarding separation. Scope of application.
the first receiving module 22 in the tracking area update process in which the management bearer is the modified bearer, the terminal accesses the network through the gateway of the forwarding layer in the second network, and the terminal moves from the second network to the first network, the first receiving module 22 further It may be configured to receive a modified bearer request from a serving gateway in the first network; the first management module 24 may be further configured to modify the bearer to the gateway of the forwarding layer in the second network according to the modified bearer request.
FIG. 3 is a structural block diagram of a bearer management system according to an embodiment of the present invention. As shown in FIG. 3, the system includes a controller located in the controller as shown in FIG.
the bearer management device 20 further includes a mobility management entity 30 located in the second network, where the mobility management entity in the second network includes: a first sending module 32, configured to move to a mobility management entity in the first network Responding to the context response message, where the context response message carries the address of the controller in the second network and the address of the gateway of the forwarding layer, the controller address is used as the control plane address of the access gateway of the second network, and the gateway of the forwarding layer The address serves as the user plane address of the access gateway of the second network.
4 is a block diagram of a preferred structure of a bearer management system according to an embodiment of the present invention. As shown in FIG.
the bearer management device 20 may further include: a second sending module 26, and a first receiving module 22 And connected to the first sending module 32, configured to carry the controller address and the address of the gateway of the forwarding layer in the create session response message and send the message to the mobility management entity 30 in the second network.
a second sending module 26 and a first receiving module 22 And connected to the first sending module 32, configured to carry the controller address and the address of the gateway of the forwarding layer in the create session response message and send the message to the mobility management entity 30 in the second network.
FIG. 5 is a flowchart of another bearer management method according to an embodiment of the present invention. As shown in FIG. 5, the method includes the following steps: Step S502, The controller receives a management session request from a mobility management entity in the second network or establishes a forwarding tunnel request.
Step S504 The controller manages the session or establishes a forwarding tunnel to the gateway of the forwarding layer in the second network according to the management session request or the establishment of the forwarding tunnel request, where the managed session or the established forwarding tunnel is used to be in the first network.
the serving gateway manages the bearer
the second network is a communication network that supports the separation of the control layer and the forwarding layer.
the controller in the communication network separated from the control and the forwarding receives the management session request from the mobility management entity in the network or establishes a forwarding tunnel request, and the controller separates from the control layer and the forwarding layer.
the forwarding layer gateway management bearer in the communication network realizes the management bearer interaction between the traditional communication network that does not support control and forwarding separation and the communication network that supports control and forwarding separation, and solves the traditional unsupported control in the related art.
the problem of how to communicate with the communication network separated from the forwarding and the communication network supporting the separation of control and forwarding improves the compatibility and scope of the communication network supporting the separation of control and forwarding.
the gateway of the forwarding layer in the foregoing second network may be an AGW, and the controller may be a control layer module separated from the forwarding layer.
the management bearer may include at least one of the following: establishing a bearer, modifying a bearer, and deleting a bearer.
the controller may receive an indirect data forwarding tunnel request from the mobility management entity in the second network;
the controller may establish a session with the gateway of the forwarding layer in the second network according to the create indirect data forwarding tunnel request, and carry the tunnel information of the serving gateway in the first network.
the controller may directly establish a session to the radio side network element in the second network, and carry tunnel information of the gateway of the forwarding layer in the second network.
the controller may also send the tunnel information of the gateway of the forwarding layer in the second network to the radio side network element in the second network by using the mobility management entity in the second network.
the mobility management entity in the second network may further send a forward relocation request message to the mobility management entity in the first network, where the forward relocation request message may be carried in the second network.
the controller address and the address of the gateway of the forwarding layer, the controller address is used as the control plane address of the access gateway of the second network, and the address of the gateway of the forwarding layer is used as the user plane address of the access gateway of the second network. In this way, the mobility management entity in the first network can conveniently obtain the address of the controller and the address of the gateway of the forwarding layer.
the address of the controller and the address of the gateway of the forwarding layer can be notified by other means.
a mobility management entity in the first network Preferably, in a case that the terminal accesses the network through the access gateway in the first network, after the controller establishes a forwarding tunnel to the gateway of the forwarding layer in the second network according to the request for creating the indirect data forwarding tunnel, when the forwarding tunnel is established.
the controller may delete the session with the mobility management entity in the second network and delete the information related to the terminal to the gateway of the forwarding layer in the second network.
the controller receives the second network.
the session management request of the mobility management entity the controller may create a session to the gateway of the forwarding layer in the second network according to the creation session request.
the controller may create a session with the access gateway in the first network according to the create session request to the gateway of the forwarding layer in the second network; the controller sends a modify bearer request message to the access gateway in the first network, And carrying the address of the gateway of the forwarding layer in the second network and the address of the controller, where the controller address is used as the control plane address of the access gateway of the second network, and the address of the gateway of the forwarding layer is used as the access of the second network.
the user plane address of the gateway As a preferred implementation manner, in a process in which the terminal performs handover from the first network to the second network, the controller receives a create session request from the mobility management entity in the second network, and the controller may create a session according to the session.
a request is made to create a session to the gateway of the forwarding layer in the second network.
the controller may create a session with the access gateway in the first network to the gateway of the forwarding layer in the second network according to the create session request.
the session may also be established to the wireless side network element in the second network, and the gateway of the forwarding layer in the second network is carried.
the tunnel information of the forwarding layer in the second network may be sent by the mobility management entity in the second network to the wireless side network element in the second network.
the controller may release the indirect data forwarding tunnel with the mobility management entity in the second network, and delete the forwarding session to the gateway of the forwarding layer in the second network to release the resource.
the controller receives the second network from the second network.
the controller may modify the bearer to the gateway of the forwarding layer in the second network according to the modify bearer request.
the controller may delete the session related to the serving gateway in the first network to the gateway of the forwarding layer in the second network according to the modified bearer request.
the controller may receive a create session request from the mobility management entity in the second network, The controller may send a setup session request to the access gateway in the first network according to the create session request, and carry the address of the gateway of the forwarding layer in the second network and the address of the controller, where the controller address is used as the connection of the second network.
the control plane address of the gateway is used as the user plane address of the access gateway of the second network; the controller establishes a session with the gateway of the forwarding layer in the second network and the access gateway in the first network.
the controller may also delete the session with the mobility management entity in the second network, and The gateway of the forwarding layer in the second network deletes information related to the terminal to release the resources.
another bearer management device is provided in the controller, which is located in the controller.
FIG. 6 is a structural block diagram of another bearer management device according to an embodiment of the present invention, such as As shown in FIG. 6, the device includes: a second receiving module 62 and a second management module 64. Each module will be described in detail below.
the second receiving module 62 is configured to receive a management session request from the mobility management entity in the second network or establish a forwarding tunnel request.
the second management module 64 is connected to the second receiving module 62 and configured to be configured according to the management session. Or establishing a forwarding tunnel request to the gateway management session of the forwarding layer in the second network or establishing a forwarding tunnel, where the managed session or the established forwarding tunnel is used to manage the bearer to the serving gateway in the first network, and the second network is supported.
the controller in the communication network separated from the control and forwarding receives the management session request or the forwarding tunnel request from the mobility management entity in the network through the second receiving module 62, and the controller passes the
the second management module 64 manages the bearer to the forwarding layer gateway in the communication network separated from the control layer and the forwarding layer, and implements a traditional communication network that does not support separation of control and forwarding and supports separation of control and forwarding.
the management of the bearer interaction between the network solves the problem of how the traditional communication network that does not support control and forwarding separation and the communication network that supports control and forwarding are inter-connected in the related art, and improves the separation of support control and forwarding.
FIG. 7 is a block diagram of a preferred structure of another bearer management device according to an embodiment of the present invention. As shown in FIG.
the device may further include: a first session establishing module 72, connected to the second management module 64, configured to Establishing a session with the wireless side network element in the second network, and carrying the tunnel information of the gateway of the forwarding layer in the second network; or, the third sending module 74 is connected to the second management module 64, and is configured to pass through the second network.
the mobility management entity in the middle sends the tunnel information of the gateway of the forwarding layer in the second network to the wireless side network element in the second network.
FIG. 8 is a block diagram of a preferred structure of another bearer management device according to an embodiment of the present invention. As shown in FIG.
the device further includes: A deletion module 82 is connected to the second management module 64 and configured to delete a session with the mobility management entity in the second network.
the second deletion module 84 is connected to the first deletion module 82 and configured to be connected to the second network.
the gateway of the forwarding layer in the middle deletes the information related to the terminal.
the management bearer comprises at least one of the following: establishing a bearer, modifying a bearer, deleting a bearer, accessing the network by the access gateway in the first network, and the tracking area of the terminal moving from the first network to the second network
the second receiving module 62 may also be configured to receive a create session request from the mobility management entity in the second network; the second management module 64 may also be configured to forward to the second network according to the create session request.
the layer's gateway creates a session.
FIG. 9 is a block diagram 3 of a preferred structure of another bearer management device according to an embodiment of the present invention. As shown in FIG.
the device may further include: a fourth sending module 92 connected to the second management module 64, configured to The access gateway in the first network sends a modify bearer request message, and carries the address of the gateway of the forwarding layer in the second network and the address of the controller, and the controller address is used as the control plane address of the access gateway of the second network, and forwards The address of the layer's gateway serves as the user plane address of the access gateway of the second network.
the management module includes at least one of the following: establishing a bearer, modifying a bearer, and deleting a bearer, and the second receiving module 62 is further configured to receive the received from the first network to the second network.
FIG. 10 is a block diagram of a preferred structure of another bearer management device according to an embodiment of the present invention. As shown in FIG. 10, the device may further include: a second session establishing module 102, connected to the second management module 64, configured to Establishing a session to the wireless side network element in the second network, and carrying the tunnel information of the gateway of the forwarding layer in the second network; or, the fifth sending module 104 is connected to the second management module 64, and is configured to pass through the second network.
a second session establishing module 102 connected to the second management module 64, configured to Establishing a session to the wireless side network element in the second network, and carrying the tunnel information of the gateway of the forwarding layer in the second network
the fifth sending module 104 is connected to the second management module 64, and is configured to pass through the second network.
FIG. 11 is a block diagram of a preferred structure of another bearer management device according to an embodiment of the present invention. As shown in FIG. 11, the device may further include: a release module 112, connected to the second management module 64, and configured to be the second The indirect data forwarding tunnel is released between the mobility management entities in the network.
the third deletion module 114 is connected to the release module 112 and configured to delete the forwarding session to the gateway of the forwarding layer in the second network.
the management bearer comprises at least one of the following: establishing a bearer, modifying a bearer, deleting a bearer, accessing the network by the gateway of the forwarding layer in the second network, and tracking the terminal from the first network to the second network
the second receiving module 62 may also be configured to receive the modified bearer request from the mobility management entity in the second network; the second management module 64 may also be configured to modify the bearer request to the second network.
the gateway of the forwarding layer modifies the bearer.
the second receiving module 62 may also be in the process of managing the bearer, including at least one of: establishing a bearer, modifying a bearer, and deleting a bearer, where the terminal is connected to the access gateway in the first network by the second network, and the second receiving module 62 is further Set to receive a create session request from a mobility management entity in the second network; the second management module 64 may be further configured to send a setup session request to the access gateway in the first network according to the create session request, and carry the second network
the address of the gateway of the forwarding layer and the address of the controller, the controller address is used as the control plane address of the access gateway of the second network, and the address of the gateway of the forwarding layer is used as the user plane address of the access gateway of the second network, and A session is established with the gateway of the forwarding layer in the second network with the access gateway in the first network.
FIG. 12 is a block diagram of a preferred structure of another bearer management device according to an embodiment of the present invention.
the device may further include: a fourth deletion module 122 connected to the second management module 64, configured to The session is deleted between the mobility management entities in the second network.
the fifth deletion module 124 is connected to the fourth deletion module 122, and is configured to delete information related to the terminal to the gateway of the forwarding layer in the second network.
Another bearer management system is also provided in this embodiment.
FIG. 13 is a structural block diagram of another bearer management system according to an embodiment of the present invention. As shown in FIG. 13, the system includes FIG. 6, FIG. The illustrated bearer management device 60 (illustrated in FIG. 13 as an example in FIG.
the 13) further includes a mobility management entity 130 located in the second network, wherein mobility management in the second network
the entity 130 includes: a sixth sending module 132, And sending a forward relocation request message to the mobility management entity in the first network, where the forward relocation request message carries the controller address in the second network and the address of the gateway of the forwarding layer, and the controller address As the control plane address of the access gateway of the second network, the address of the gateway of the forwarding layer serves as the user plane address of the access gateway of the second network.
FIG. 14 is a schematic diagram of a scenario 1 of a wireless communication network according to a preferred embodiment of the present invention.
the initial access of the user is non-roaming; the home network supports the OpenFlow protocol, and the visited network is a legacy network, and the OpenFlow is supported.
the gateway in the network of the protocol accesses the Internet.
15 is a schematic diagram of scenario 2 of a wireless communication network according to a preferred embodiment of the present invention. As shown in FIG.
16 is a schematic diagram of scenario three of a wireless communication network in accordance with a preferred embodiment of the present invention. As shown in Figure 16, the initial access of the user is routed to the home location; the home network supports the OpenFlow protocol, and the visited network is a traditional network, and the gateway in the network supporting the OpenFlow protocol accesses the Internet. 17 is a schematic diagram of a scenario 4 of a wireless communication network according to a preferred embodiment of the present invention. As shown in FIG.
a user initially accesses a route to a home location; a home network is a legacy network, and a visited network supports an OpenFlow protocol.
the access gateway in the traditional network accesses the Internet.
the traditional network mentioned above (also referred to as the first network in this paper) is a network that does not support openflow, that is, the access gateway in the network is a combination of forwarding and control, and does not implement separation of forwarding and control.
the network supporting the OpenFlow protocol is also referred to as the second network in this paper. It implements the separation of forwarding and control, and is separated into the controller and the forwarding layer gateway (for example, AGW).
AGW forwarding layer gateway
an interworking mode for forwarding control separation is provided: After the terminal receives the management bearer sent by the serving gateway, the controller manages the bearer to the AGW; or, receives the mobility management entity. Management meeting After the call or the forwarding tunnel request is established, the controller manages the session (flow table) or establishes a forwarding tunnel to the AGW, and manages the bearer (non-flow table) to the service gateway. Preferably, the above management may include establishing, or modifying, or deleting.
E-UTRAN Evolved Universal Terrestrial Radio Access Network
Step S1802 the terminal The tracking area update request message is sent to the mobility management entity via the wireless side network element.
Step S1804 The target mobility management entity sends a context request message to the original mobility management entity.
Step S1806 The original mobility management entity replies to the target mobility management entity with a context response message carrying the AGW address and the controller address.
the AGW address is used as the access gateway user plane address
the controller address is used as the access gateway control plane address.
Step S1810 optionally, the terminal, the mobility management entity, and the authentication authorization server perform an authentication process.
Step S1812 The target mobility management entity sends a context confirmation message to the original mobility management entity.
Step S1814 The target mobility management entity sends a create session request to the target service gateway.
Step S1816 The target serving gateway sends a modify bearer request message to the controller, and the controller responds to modify the bearer response message.
Step S1818 The controller updates the flow table to the AGW, and carries the target service gateway tunnel information, which is used to update the tunnel information between the target service gateway and the AGW.
Step S1820 The target service gateway replies to the target mobility management entity to create a session response.
Step S1822 Perform an update location process between the target mobility management entity and the authentication authorization server.
Step S1824 The location cancellation process is performed between the authentication authorization server and the original mobility management entity.
Step S1826 The target mobility management entity sends a tracking area update accept message to the terminal via the target radio side network element.
Step S1828 The original connection is released between the original mobility management entity, the controller, and the AGW.
the information about the release of the mobility management entity on the controller may be one of the following methods: 1. The timer is triggered according to the location cancellation of the authentication authorization server or the context request/context confirmation, and the original mobility management entity The controller sends a release session. 2.
step S1818 the controller can release the message according to the update flow table and release the connection with the original mobility management entity.
the above process may notify the mobility management entity in the create session response message by the controller during the terminal attaching process by the controller and the controller address and the AGW address.
FIG. 19 is a flowchart of a user performing a handover process on the basis of the scenario 1 system of FIG. 14 according to the embodiment of the present invention. As shown in FIG. 19, the specific steps in this embodiment are described as follows: Step S1902: The wireless side network element needs to determine Initiate an S1 switch.
Step S1904 The original radio side network element sends a handover request to the original mobility management entity.
Step S1906 The forward mobility relocation request message sent by the original mobility management entity to the target mobility management entity carries the AGW address and the controller address.
the AGW address is used as the access gateway user plane address
the controller address is used as the access gateway control plane address.
Step S1908 The target mobility management entity establishes a process to the target service gateway session.
Step S1910 The target mobility management entity requests the target radio side network element to perform handover.
the target radio side network element responds to the target mobility management entity with a handover request acknowledgement message.
Step S1912 An indirect data forwarding tunnel is created between the target mobility management entity and the target service gateway.
Step S1914 The target mobility management entity sends a forward relocation response message to the original mobility management entity.
Step S1916 The original mobility management entity sends a request to create an indirect data forwarding tunnel to the controller.
Step S1918 The controller sends a setup flow table to the AGW, and carries the target service gateway tunnel information, so as to establish a forwarding tunnel.
Step S1920 optionally, the controller establishes a flow table to the original radio side network element, and carries the AGW tunnel information, so as to establish a forwarding tunnel.
Step S1922 The controller sends an indirect data forwarding tunnel response to the original mobility management entity.
Step S1924 The original mobility management entity sends a handover command to the terminal by the original radio side network element.
the original mobility management entity sends the AGW tunnel information to the original radio side network element to establish a forwarding tunnel.
Step S1926 The terminal initiates a handover confirmation message to the target radio side network element.
Step S1928 The target radio side network element notifies the target mobility management entity to perform handover.
Step S1930 The target mobility management entity sends a relocation forward completion notification message to the original mobility management entity.
the original mobility management entity replies to the target mobility management entity with a relocation forward completion confirmation message.
Step S1932 The target mobility management entity sends a modify bearer request to the target serving gateway.
Step S1934 The target serving gateway sends a modify bearer request to the controller, and the controller replies to modify the bearer response.
Step S1936 The controller modifies the flow table to the AGW, and carries the service gateway tunnel information.
Step S1938 The target service gateway replies to the target mobility management entity to modify the bearer response.
Step S1940 continuing the tracking area update process.
Step S1942 the timer for ending the forwarding expires.
Step S1944 optionally, the terminal mobility release is performed between the original mobility management entity and the original wireless side network element.
Step S1946 The indirect data forwarding tunnel is released between the original mobility management entity and the controller.
Step S1950 Optionally, the controller deletes the forwarding flow table from the original wireless side network element.
Step S1944 and step S1950 may be performed one by one.
FIG. 20 is a flowchart of a process of updating a tracking area by a user on the basis of the scenario 2 of FIG. 15 according to the second embodiment of the present invention.
Step S2002 the terminal Access to the mobile communication network through existing attach procedures.
Step S2004 The terminal sends a tracking area update request message to the target mobility management entity via the target wireless side network element.
Step S2006 the target mobility management entity sends a context request message to the original mobility management entity.
Step S2008 the original mobility management entity replies to the target mobility management entity with a context response message.
Step S2010 the target mobility management entity sends a context confirmation message to the original mobility management entity.
Step S2012 the target mobility management entity performs controller selection.
Step S2014 the target mobility management entity sends a create session request to the controller, carrying the user plane address and the control plane address of the access gateway.
Step S2016 the controller establishes a flow table to the AGW, and carries the access gateway user plane address.
Step S2018 The controller sends a modify bearer request message to the access gateway, where the AGW address and the controller address are carried, where the AGW address is used as the user plane of the serving gateway, and the controller address is used as the control plane address of the serving gateway.
the access gateway responds with a modified bearer response message.
Step S2020 the controller replies to the target mobility management entity to create a session response.
Step S2022 The target mobility management entity sends a tracking area update accept message to the terminal via the target radio side network element.
the original connection is released between the original mobility management entity and the original serving gateway.
FIG. 21 is a flowchart of a user performing a handover process on the basis of the scenario 2 of FIG. 15 according to the second embodiment of the present invention. As shown in FIG.
Step S2102 The wireless side network element needs to determine Initiate an S1 switch.
Step S2106 The forward mobility relocation request message sent by the original mobility management entity to the target mobility management entity.
Step S2108 The target mobility management entity performs controller selection.
Step S2110 The target mobility management entity creates a session request to the controller, carrying the user plane address and the control plane address of the access gateway; and the controller replies to create a session response.
Step S2112 Optionally, the controller establishes a flow table to the target radio side network element, and carries the AGW tunnel information, and is used to establish a tunnel between the target radio side network element and the AGW.
Step S2114 the target mobility management entity requests the target radio side network element to perform handover, and carries the AGW tunnel information.
the target radio side network element responds to the target mobility management entity with a handover request acknowledgement message.
the controller needs to carry the AGW tunnel information to the target mobility management entity in step S2110.
the above step S2112 and step S2114 may be selected one by one.
Step S2116 An indirect data forwarding tunnel is created between the target mobility management entity and the controller.
the message sent by the controller to the target mobility management entity carries the AGW forwarding tunnel information, which is used to establish a forwarding tunnel.
Step S2118 The controller establishes a flow table to the AGW, and carries the AGW to forward the tunnel information, and is used to establish a forwarding tunnel.
the message optionally carries the access gateway user plane address.
Step S2120 The target mobility management entity sends a forward relocation response message to the original mobility management entity, and carries the AGW to forward the tunnel information.
Step S2122 The original mobility management entity sends an indirect data forwarding tunnel request to the serving gateway, and carries the AGW to forward the tunnel information.
the service gateway replies with a response message.
Step S2124 The original mobility management entity sends a handover command to the terminal via the original radio side network element.
Step S2126 The terminal initiates a handover confirmation message to the target radio side network element.
Step S2128 The target radio side network element notifies the target mobility management entity to perform handover.
Step S2130 The target mobility management entity sends a forward relocation complete notification message to the original mobility management entity.
the original mobility management entity replies to the target mobility management entity with a forward relocation complete confirmation message.
Step S2132 The target mobility management entity sends a modify bearer request to the controller.
Step S2134 The controller sends a modify bearer request to the access gateway, where the AGW address and the controller address are carried, where the AGW address is used as the user plane address, and the controller address is used as the control plane address.
the access gateway replies to the modified bearer response.
Step S2136 optionally, the controller establishes a flow table to the AGW, and carries the access gateway user plane address.
Step S2118 The step and the step S2118 message carrying the access gateway user plane address may optionally occur, and the two may be selected.
Step S2138 The controller replies to the target mobility management entity with a modified bearer response.
Step S2140 continuing the tracking area update process.
Step S2142 the timer for ending the forwarding times out.
Step S2144 The resource release is performed between the original mobility management entity, the serving gateway, and the original wireless side network element.
Step S2148 The indirect data forwarding tunnel is released between the original or target mobility management entity and the controller.
Step S2150 The controller deletes the forwarding flow table to the AGW, and is used to release the forwarding tunnel.
Step S2202 The terminal sends an attach request to the mobility management entity via the radio side network element.
Step S2204 The update location is performed between the mobility management entity and the authentication authorization server.
Step S2206 When the mobility management entity performs the access gateway selection, the controller address is obtained. At this time, the DNS server of the home network needs to provide the controller address according to the mobility management entity information.
Step S2208 The mobility management entity creates a session request to the serving gateway.
Step S2210 The serving gateway sends a create session request to the controller.
the controller replies with a session response message, and carries the AGW information, where the information is used as the access gateway user plane information to the serving gateway.
Step S2212 The controller establishes a flow table to the AGW, and carries the service gateway information.
Step S2214 The serving gateway creates a session response to the mobility management entity.
the attach process is continued.
Step S2218 The mobility management entity sends a modify bearer request to the serving gateway.
Step S2220 The serving gateway returns a mobility management entity to modify the bearer response.
Step S2222 The terminal sends a tracking area update request message to the target mobility management entity via the target wireless side network element.
Step S2224 The target mobility management entity sends a context request message to the original mobility management entity.
Step S2226 The original mobility management entity replies to the target mobility management entity with a context response message.
Step S2228 The target mobility management entity sends a context confirmation message to the original mobility management entity.
Step S2230 the target mobility management entity performs controller selection.
Step S2232 The target mobility management entity sends a modify bearer request to the controller.
Step S2234 The controller modifies the flow table to the AGW, and is used to delete the flow table related to the service gateway.
Step S2236 The controller sends a modify bearer response message to the target mobility management entity.
Step S2238 an update location process is performed between the target mobility management entity and the authentication authorization server.
Step S2240 Perform a location cancellation process between the authentication authorization server and the original mobility management entity.
Step S2242 The target mobility management entity sends a tracking area update accept message to the terminal.
Step S2244 The timer expired according to the cancellation location of the authentication authority server or the context request/context confirmation.
Step S2246 The original connection is released between the original mobility management entity and the serving gateway.
FIG. 23 is a flowchart of a user performing a handover process on the basis of the scenario 3 system of FIG. 16 according to the third embodiment of the present invention. As shown in FIG.
Step S2302 the wireless side network element needs to determine Initiate an S1 switch.
Step S2304 The original radio side network element sends a handover request to the original mobility management entity.
Step S2306 The forward mobility relocation request message sent by the original mobility management entity to the target mobility management entity.
Step S2308 The target mobility management entity determines that the serving gateway needs to perform relocation.
Step S2310 The target mobility management entity modifies the bearer request to the controller; the controller replies with a response message.
Step S2312 The target mobility management entity requests the target radio side network element to perform handover.
the target radio side network element responds to the target mobility management entity with a handover request acknowledgement message.
Step S2314 An indirect data forwarding tunnel is created between the target mobility management entity and the controller.
the message sent by the controller to the target mobility management entity carries the AGW forwarding tunnel information, which is used to establish a forwarding tunnel.
Step S2316 The controller establishes a flow table to the AGW, and carries the target wireless side network element forwarding tunnel information, so as to establish a forwarding tunnel.
Step S2318 The target mobility management entity sends a forward relocation response message to the original mobility management entity, and carries the AGW to forward the tunnel information.
Step S2320 The original mobility management entity sends an indirect data forwarding tunnel request to the serving gateway, and carries the AGW to forward the tunnel information.
the service gateway replies with a response message.
Step S2322 The original mobility management entity sends a handover command to the terminal via the original radio side network element.
Step S2324 The terminal initiates a handover confirmation message to the target radio side network element.
Step S2326 The target radio side network element notifies the target mobility management entity to perform handover.
Step S2328 the switching process is continued.
FIG. 24 is a flowchart of a process for an attachment and tracking area update of a user on the basis of the scenario 4 of FIG. 17 according to Embodiment 4 of the present invention. As shown in FIG. 24, the specific steps of this embodiment are described as follows: S2402 to step S2416 describe the attaching process: Step S2402: The terminal sends an attach request to the mobility management entity via the radio side network element.
Step S2404 The update location is performed between the mobility management entity and the authentication authorization server.
Step S2406 The mobility management entity determines that the home location is a legacy network, and then selects a controller and an access gateway.
Step S2410 The controller sends a setup session request to the access gateway, where the AGW address and the controller address are carried, where the AGW address is used as the service gateway user plane address, and the controller address is used as the serving gateway control plane address.
the access gateway replies with a response message.
Step S2412 The controller establishes a flow table to the AGW, and carries the access gateway address information.
Step S2414 the controller creates a session response to the mobility management entity.
Step S2416 continuing to execute the remaining attachment process of Openflow, including flow table establishment.
the tracking area update process is described in the following steps S2418 to S2434: Step S2418: The terminal sends a tracking area update request message to the target mobility management entity via the target radio side network element.
Step S2420 The target mobility management entity sends a context request message to the original mobility management entity.
Step S2422 The original mobility management entity replies to the target mobility management entity with a context response message.
Step S2424 The target mobility management entity sends a context confirmation message to the original mobility management entity.
Step S2426 The target mobility management entity determines that the serving gateway needs to perform relocation. In step S2428, the tracking area process is continued.
Step S2430 The timer expired according to the cancellation location of the authentication authority server or the context request/context confirmation.
Step S2432 The original mobility management entity and the controller delete the original session.
Step S2434 the controller deletes the flow table from the AGW, and deletes all information about the terminal in the AGW.
25 is a flowchart of a user performing a handover process on the basis of the scenario 4 system of FIG. 17 according to Embodiment 4 of the present invention. As shown in FIG. 25, the specific steps in this embodiment are described as follows: Step S2502, the wireless side network element determines that it needs to Initiate an S1 switch.
Step S2504 The original radio side network element sends a handover request to the original mobility management entity.
Step S2506 The forward mobility relocation request message sent by the original mobility management entity to the target mobility management entity.
Step S2508 The target mobility management entity determines that the service gateway needs to perform relocation.
Step S2510 The target mobility management entity sends a create session request to the serving gateway; the service gateway replies with a response message.
Step S2512 The target mobility management entity requests the target radio side network element to perform handover.
the target radio side network element responds to the target mobility management entity with a handover request acknowledgement message.
Step S2514 An indirect data forwarding tunnel is created between the target mobility management entity and the controller.
the message sent by the controller to the target mobility management entity carries the AGW forwarding tunnel information, which is used to establish a forwarding tunnel.
Step S2516 The controller establishes a flow table to the AGW, and carries the service gateway to forward the tunnel information, and is used to establish a forwarding tunnel.
Step S2518 The target mobility management entity sends a forward relocation response message to the original mobility management entity, and carries the AGW to forward the tunnel information.
Step S2520 The original mobility management entity sends a handover command to the terminal via the original radio side network element. The message sent by the original mobility management entity to the original radio side network element may optionally carry the AGW forwarding tunnel information.
Step S2522 optionally, the controller establishes a flow table to the original radio side network element, and carries the AGW to forward the tunnel information.
Step S2522 and step S2520 carrying the AGW forwarding tunnel information may be performed, and the two may be selected.
step S2524 the switching process is continued.
step S2526 the timer for ending the forwarding expires.
step S2528 the original mobility management entity deletes the session with the controller.
Step S2530 The controller deletes the flow table from the AGW, and deletes all information about the terminal in the AGW.
the radio side network element may be a base station, a home base station, a home base station gateway, and an RNC (Radio Network Controller) data offload function entity.
the mobility management entity may be an MME (Mobility Management Entity) MSC (Mobile Switching Centre), an SGSN (Serving GPRS Support Node), a home base station gateway, or the like.
the serving gateway can be an S-GW or an SGSN.
the access gateway can be a P-GW, an AGW or a GGSN.
the authorization server can be HSS (Home Subscriber Server) or AAA (Authentication, Authorization, Accounting Authorization Accounting).
the tunnel information can include an address and/or an identification.
AGW is a gateway that supports openflow networks, including service gateways and access gateways that support openflow or access gateways that support openflow. For the former, the service gateway and the access gateway can be combined into one device or divided. If the switch is set, the controller sends a flow table to the service gateway and the access gateway respectively.
the steps shown in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions, and, although the logical order is shown in the flowchart, in some cases, The steps shown or described may be performed in an order different than that herein.
Industrial Applicability according to the technical solution provided by the present invention, after receiving a request for a management bearer from a serving gateway in a legacy network, the controller in the communication network separated from the control network may be in a communication network separate from the control layer and the forwarding layer.
the forwarding layer gateway manages the bearer, and thus can realize the management bearer interaction between the communication network that does not support control and forwarding separation and the communication network that supports control and forwarding separation, and can improve the compatibility of the communication network supporting the control and forwarding separation. And the scope of application.
the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.

Landscapes

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

PCT/CN2013/085067 2012-10-11 2013-10-11 Procédé, dispositif et système de gestion de supports Ceased WO2014056450A1 (fr)

Applications Claiming Priority (2)

Application Number	Priority Date	Filing Date	Title
CN201210383322.XA CN103731929B (zh)	2012-10-11	2012-10-11	承载管理方法、装置及系统
CN201210383322.X		2012-10-11

Publications (1)

Publication Number	Publication Date
WO2014056450A1 true WO2014056450A1 (fr)	2014-04-17

Family

ID=50455813

Family Applications (1)

Application Number	Title	Priority Date	Filing Date
PCT/CN2013/085067 Ceased WO2014056450A1 (fr)	2012-10-11	2013-10-11	Procédé, dispositif et système de gestion de supports

Country Status (2)

Country	Link
CN (1)	CN103731929B (fr)
WO (1)	WO2014056450A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
CN105376811B (zh) *	2014-08-25	2019-03-15	中国电信股份有限公司	在软件化移动网络架构下实现切换的方法和系统
WO2017035706A1 (fr) *	2015-08-28	2017-03-09	华为技术有限公司	Dispositif, procédé et système pour le traitement de données d'utilisateur
CN105681191B (zh) *	2016-02-25	2019-04-30	烽火通信科技股份有限公司	基于路由器虚拟化的sdn平台及实现方法
CN107277865B (zh) *	2016-04-07	2019-11-12	中国移动通信有限公司研究院	一种控制面融合时的用户切换方法及系统、网元
WO2017197641A1 (fr) *	2016-05-20	2017-11-23	华为技术有限公司	Procédé, dispositif et système de transmission de message
CN107786613B (zh) *	2016-08-30	2020-05-12	新华三技术有限公司	宽带远程接入服务器bras转发实现方法和装置
CN112910969B (zh)	2017-02-28	2022-07-29	华为技术有限公司	一种业务管理方法及其装置
CN109547507A (zh) *	2017-09-21	2019-03-29	中国移动通信有限公司研究院	一种窄带物联网的接入方法、装置及网元实体
CN112997578B (zh) *	2019-03-08	2024-07-12	瑞典爱立信有限公司	用于通信网络的承载连接处理的网络实体和方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
CN1360797A (zh) *	1999-07-05	2002-07-24	艾利森电话股份有限公司	增加带有分离的呼叫控制和载体控制的通信网的灵活性的方法
CN102045692A (zh) *	2009-10-26	2011-05-04	中兴通讯股份有限公司	一种基于控制面与媒体面分离的网络架构实现的通信网络
WO2011113451A1 (fr) *	2010-03-19	2011-09-22	Nec Europe Ltd.	Procédé de fonctionnement d'un réseau, et réseau

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
ATE297086T1 (de) *	2001-08-29	2005-06-15	Ericsson Telefon Ab L M	Verfahren und vorrichtung zur mehrfachsendung in einem umts-netzwerk
CN1988498A (zh) *	2005-12-25	2007-06-27	华为技术有限公司	一种转发控制分离系统中路由转发的方法

2012
- 2012-10-11 CN CN201210383322.XA patent/CN103731929B/zh not_active Expired - Fee Related
2013
- 2013-10-11 WO PCT/CN2013/085067 patent/WO2014056450A1/fr not_active Ceased

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
CN1360797A (zh) *	1999-07-05	2002-07-24	艾利森电话股份有限公司	增加带有分离的呼叫控制和载体控制的通信网的灵活性的方法
CN102045692A (zh) *	2009-10-26	2011-05-04	中兴通讯股份有限公司	一种基于控制面与媒体面分离的网络架构实现的通信网络
WO2011113451A1 (fr) *	2010-03-19	2011-09-22	Nec Europe Ltd.	Procédé de fonctionnement d'un réseau, et réseau

Also Published As

Publication number	Publication date
CN103731929A (zh)	2014-04-16
CN103731929B (zh)	2019-03-15

Publication	Publication Date	Title
WO2014056450A1 (fr)	2014-04-17	Procédé, dispositif et système de gestion de supports
US9787483B2 (en)	2017-10-10	Method, system, and controller for routing forwarding
WO2018030474A1 (fr)	2018-02-15	Dispositif terminal, passerelle et procédé de commande de communications
WO2011054283A1 (fr)	2011-05-12	Procede pour gerer des connexions d'acces de protocole internet (ip) local
KR102323327B1 (ko)	2021-11-08	단말 장치, SME(Session Management Entity), 및 통신 제어 방법
WO2015184722A1 (fr)	2015-12-10	Procédé et dispositif de sélection de réseau privé
CN101969673A (zh)	2011-02-09	一种承载绑定和事件报告功能的重选方法
JP7785853B2 (ja)	2025-12-15	インジケーション情報送信方法、装置およびシステム、および記憶媒体
WO2018003902A1 (fr)	2018-01-04	Dispositif terminal, dispositif de commande et procédé de commande de communication
JP2021184642A (ja)	2021-12-02	Ｕｅ、通信方法、通信制御方法
CN107079039A (zh)	2017-08-18	集中式位置控制服务器
JP2019149588A (ja)	2019-09-05	端末装置、制御装置、ゲートウェイ、及び通信制御方法
JP2019145864A (ja)	2019-08-29	端末装置、制御装置、ゲートウェイ、及び通信制御方法
CN109076106B (zh)	2022-02-25	用户设备ue以及通信控制方法
WO2011143997A1 (fr)	2011-11-24	Procédé et dispositif de routage
JP6759336B2 (ja)	2020-09-23	Ｕｅ及び通信制御方法
WO2014056449A1 (fr)	2014-04-17	Méthode, dispositif et système de gestion et de vérification de communication entre dispositifs
WO2012041131A1 (fr)	2012-04-05	Procédé et système permettant à un abonné de participer à l'établissement d'une communication en accès local
WO2011134315A1 (fr)	2011-11-03	Procédé, dispositif et système pour une autorisation de service
CN102300194B (zh)	2015-08-12	一种传递分流信息的方法及装置、系统
WO2012146129A1 (fr)	2012-11-01	Procédé et système de gestion de support, et point d'ancrage prenant en charge l'accès multiple
WO2013174188A1 (fr)	2013-11-28	Procédé et système d'optimisation de routage, et élément de réseau sans fil
WO2012129997A1 (fr)	2012-10-04	Procédé et dispositif pour traiter une connexion d'accès à un réseau local
WO2008154856A1 (fr)	2008-12-24	Procédé, entité de passerelle et dispositif de réseau servant à libérer des ressources de réseau
WO2012034474A1 (fr)	2012-03-22	Procédé et système d'obtention d'informations de configuration par un nœud de relais

Legal Events

Date	Code	Title	Description
2014-06-11	121	Ep: the epo has been informed by wipo that ep was designated in this application	Ref document number: 13844687 Country of ref document: EP Kind code of ref document: A1
2015-04-13	NENP	Non-entry into the national phase	Ref country code: DE
2015-11-04	122	Ep: pct application non-entry in european phase	Ref document number: 13844687 Country of ref document: EP Kind code of ref document: A1

Date

Code

Title

Description

2014-06-11

121

Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13844687

Country of ref document: EP

Kind code of ref document: A1

2015-04-13

NENP

Non-entry into the national phase

Ref country code: DE

2015-11-04

122

Ep: pct application non-entry in european phase