WO2018072174A1 - 网络切换方法、控制器、网关及系统 - Google Patents

网络切换方法、控制器、网关及系统 Download PDF

Info

Publication number
WO2018072174A1
WO2018072174A1 PCT/CN2016/102709 CN2016102709W WO2018072174A1 WO 2018072174 A1 WO2018072174 A1 WO 2018072174A1 CN 2016102709 W CN2016102709 W CN 2016102709W WO 2018072174 A1 WO2018072174 A1 WO 2018072174A1
Authority
WO
WIPO (PCT)
Prior art keywords
controller
network
terminal
connection
identifier
Prior art date
Application number
PCT/CN2016/102709
Other languages
English (en)
French (fr)
Inventor
诸华林
李欢
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/102709 priority Critical patent/WO2018072174A1/zh
Publication of WO2018072174A1 publication Critical patent/WO2018072174A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface

Definitions

  • the present invention relates to the field of communications, and in particular, to a network switching method, a controller, a gateway, and a system.
  • the terminal can access two communication networks at the same time, that is, the primary network and the secondary network, and accessing the two communication networks at the same time means that the terminal can also access the secondary network when the state of the terminal in the primary network is idle.
  • the terminal cannot transmit data through the primary network and the secondary network at the same time, that is, the terminal can be connected to the secondary network when the state in the primary network must be idle, and the terminal is When the state in the primary network is switched from the idle state to the connected state, it must be disconnected from the secondary network.
  • the terminal when the terminal accesses the primary network and the secondary network at the same time, and the terminal needs to switch its state in the primary network from the idle state to the connected state, the terminal needs to first request disconnection from the controller in the secondary network.
  • the connection from the network, and after disconnection from the slave network requests the controller of the primary network to switch from the idle state to the connected state.
  • the terminal since the terminal is not a trusted device, there are various uncertainties in its behavior. Therefore, in the process of switching the state of the terminal in the primary network from the idle state to the connected state, the terminal is likely to be in the process. In the case of disconnection from the network, the operation of requesting the controller of the primary network to switch from the idle state to the connected state is performed, and this may cause an error to occur, causing the state switching of the terminal to fail, resulting in a lower success rate of the terminal network handover. .
  • the terminal needs to perform two sets of processes of disconnecting and disconnecting from the network and switching between the state and the state to realize the purpose of switching the state in the main network from the idle state to the connected state, and therefore, in the process, Excessive signaling wastes network resources.
  • the embodiment of the present invention provides a network switching method, a controller, a gateway, and a system.
  • the technical solution is as follows:
  • the first aspect provides a network switching method, which is used in a first controller in a network switching system, where the network switching system includes: a primary network and a secondary network, where the first controller is in the secondary network Controller, the method includes:
  • the first controller disconnects the terminal from the secondary network.
  • the second controller is a controller in the primary network
  • the first controller causes the second controller to switch the state of the terminal in the primary network from an idle state to a connected state.
  • the connection between the terminal and the slave network is disconnected by the first controller in the network, and after the connection between the terminal and the slave network is disconnected, the first The controller instructs the second controller in the primary network to switch the state of the terminal in the primary network from an idle state to a connected state. Therefore, the terminal only needs to send a service request to the second controller to complete the network handover, and does not need the terminal to first send a disconnection request from the first controller to the slave network, and then requests the second controller to The state of the main network can be switched from the idle state to the connected state to complete the network handover. This avoids the problem of low network handover success rate due to the uncertainty of the terminal behavior. On the other hand, the terminal only needs to go through a set. The process can complete the network switch, which saves signaling and network resources.
  • the technical process that the first controller disconnects the terminal from the slave network may be: Receiving, by the controller, a disconnection request sent by the second controller, where the disconnection request is that the second controller receives the service request, and determining that the terminal accesses the primary network at the same time And transmitting, after the slave network, the disconnection request carries an identifier of the terminal or an identifier of a connection of the terminal; and according to the disconnection request, the first controller disconnects the terminal The connection to the slave network.
  • the technical process that the first controller causes the second controller to switch the state of the terminal in the primary network from the idle state to the connected state may be: the terminal and the slave network After disconnecting, the first controller sends a disconnection receipt to the second controller, so that the second controller, after receiving the disconnection receipt, places the terminal in the main The state in the network is switched from the idle state to the connected state.
  • the first controller and the second controller are the same controller.
  • the second controller receives the service request sent by the terminal, and determines the After the terminal accesses the primary network and the secondary network
  • the technical process of the first controller disconnecting the terminal from the secondary network may be: the first controller receives the After the service request sent by the terminal, and determining that the terminal accesses the slave network and the primary network at the same time, the first controller disconnects the terminal from the slave network.
  • the embodiments of the present invention may complete the technical process of disconnecting the terminal from the slave network by using the following steps. Specifically, the first controller deletes a connection context of the slave network corresponding to an identifier of the terminal or an identifier of the connection of the terminal in the first controller; when the security node in the slave network The first controller sends a first connection deletion request to the security node, where the first connection deletion request carries the terminal, when there is no control plane signaling transmission channel with the packet data protocol gateway in the slave network.
  • the identifier of the connection or the identifier of the connection, the first connection deletion request is used to instruct the security node to delete an identifier of the terminal or a connection context corresponding to the identifier of the connection; the first controller sends the packet to the group
  • the data protocol gateway sends a second connection deletion request, where the second connection deletion request carries an identifier of the terminal or an identifier of the connection, and the second connection deletion request Instructing the packet data protocol gateway to delete an identifier of the terminal or a connection context corresponding to the identifier of the connection; when the security node and the packet data protocol gateway have a control plane signaling transmission channel, the first The controller sends a third connection deletion request to the security node, where the third connection deletion request carries the identifier of the terminal or the identifier of the connection, and the third connection deletion request is used to indicate that the security node deletes the The identifier of the terminal or the connection corresponding to the identifier of the connection And instructing the security node to send a
  • the request is used to instruct the controller to delete an identifier of the terminal or a connection context corresponding to the identifier of the connection, and is used to instruct the controller to control a gateway of the local network, a base station of the local network, and the terminal At least one of deleting the identity of the terminal or the connection context corresponding to the identity of the connection.
  • the first controller when the first controller and the second controller are not the same controller, after the terminal is disconnected from the slave network, the first controller sends the second controller to the second controller.
  • the technical process of disconnecting the receipt may be: when the security node and the packet data protocol gateway do not have a control plane signaling transmission channel, the first controller receives the security node based on the first connection Deleting a first connection deletion receipt sent by the request, the first connection deletion receipt is used to indicate that the security node deletes an identifier of the terminal or a connection context corresponding to the identifier of the connection; the first controller receives the a second connection deletion receipt sent by the packet data protocol gateway based on the second connection deletion request, where the second connection deletion receipt is used to indicate that the packet data protocol gateway deletes the identifier of the terminal or the identifier of the connection Corresponding connection context; when the security node and the packet data protocol gateway have a control plane signaling transmission channel, the first controller receives a third connection deletion receipt sent by the security node based on the third
  • the fourth connection deletion receipt is used to indicate that the packet data protocol gateway deletes an identifier of the terminal or a connection context corresponding to the identifier of the connection, where the third connection deletion receipt is used to indicate the security node and The packet data protocol gateway deletes an identifier of the terminal or a connection context corresponding to the identifier of the connection; when the terminal accesses the slave through the local network
  • the first controller receives a fifth connection deletion receipt sent by the controller based on the fifth connection deletion request, where the fifth connection deletion receipt is used to indicate the gateway of the local network, the At least one of the base station of the local network, the terminal, and the controller deletes an identifier of the terminal or a connection context corresponding to the identifier of the connection; the first controller deletes the first connection After the receipt, the second connection deletion receipt, the third connection deletion receipt, and the fifth connection deletion receipt are sent, the disconnection receipt is sent to the second controller.
  • a network switching method is provided, which is used in a second controller in a network switching system, where the network switching system includes: a primary network and a secondary network, and the second controller is in the primary network. Controller, the method includes:
  • the second controller receives a service request sent by the terminal, where the service request is sent after the terminal receives the paging request of the primary network or detects a specified operation, and the specified operation is required to pass the The operation of transmitting data on the primary network;
  • the second controller After receiving the service request and determining that the terminal accesses the slave network and the primary network at the same time, the second controller causes the first controller to disconnect the terminal from the slave network.
  • the first controller is a controller in the slave network;
  • the second controller switches the state of the terminal in the primary network from an idle state to a connected state.
  • the second controller in the primary network instructs to disconnect the terminal from the first controller in the network.
  • the second controller switches the state of the terminal in the primary network from the idle state to the connected state. Therefore, the terminal only needs to send a service request to the second controller to complete the network handover, and does not need the terminal to first send a disconnection request from the first controller to the slave network, and then requests the second controller to The state of the main network can be switched from the idle state to the connected state to complete the network handover. This avoids the problem of low network handover success rate due to the uncertainty of the terminal behavior.
  • the terminal only needs to go through a set. The process can complete the network switch, which saves signaling and network resources.
  • the second controller when the first controller and the second controller are different controllers, when the service request carries the identifier of the terminal or the identifier of the connection of the terminal, the second controller
  • the technical process of the first controller disconnecting the connection between the terminal and the slave network may specifically include: the second controller sends a disconnect request to the first controller, where the disconnect request is carried The identifier of the terminal or the identifier of the connection, so that the first controller disconnects the terminal from the slave network based on the disconnect request.
  • the technical process that the second controller switches the state of the terminal in the primary network from the idle state to the connected state after the terminal is disconnected from the secondary network may include: After receiving the disconnection receipt sent by the first controller, the second controller switches the state of the terminal in the primary network from an idle state to a connected state, where the disconnected receipt is used And indicating that the terminal has disconnected from the slave network.
  • the technical process of the second controller to enable the first controller to disconnect the terminal from the slave network may specifically include: The second controller sends a terminal connection status query request to the first controller, where the terminal connection status query request carries the identifier of the terminal or the identifier of the connection, so that the first controller returns to the terminal and a connection state of the slave network, the connection state including one of a connected and a disconnected state; the second controller receiving a connection state of the terminal and the slave network sent by the first controller, And if the connection state is connected, the second controller causes the first controller to disconnect the terminal from the slave network.
  • the service request carries an identifier of the terminal or an identifier of a connection of the terminal, where the service request is received and the terminal is determined.
  • the second controller may be: the second controller Searching in the terminal connection status database of the second controller based on the identifier of the terminal or the identifier of the connection Inquiring the connection state between the terminal and the slave network, when the connection state is connected, the second controller causes the first controller to disconnect the terminal from the slave network.
  • the service request may further carry the macro network conversion information or the identifier of the first controller, where the macro network conversion information is used to indicate that the terminal accesses the primary network and the secondary network at the same time.
  • the second controller causes the first controller to disconnect the terminal and
  • the technical process of the connection of the slave network may specifically include: when receiving the macro network conversion information or the identifier of the first controller, the second controller causes the first controller to disconnect the The connection between the terminal and the slave network.
  • the technical process that the foregoing second controller switches the state of the terminal in the primary network from the idle state to the connected state may include: the second controller passes the base station of the primary network and the terminal Establishing an air interface connection; the second controller sends a modify bearer request to the packet data protocol gateway in the primary network, so that the packet data protocol gateway acquires an identifier of the base station of the primary network.
  • a network switching method for a packet data protocol gateway in a network switching system, where the network switching system includes: a primary network and a secondary network, and the packet data protocol gateway simultaneously accesses the primary In the network and the slave network, the method includes:
  • the modify bearer request carries an identifier of the terminal or an identifier of the connection of the terminal, where the modify bearer request is that the second controller is in a base station that passes the primary network After the terminal establishes an air interface connection, the second controller is a controller of the primary network;
  • the packet data protocol gateway may receive the modify bearer request sent by the second controller in the primary network, where the modify bearer request indicates that the state of the terminal in the primary network has been switched.
  • the packet data protocol gateway can disconnect the terminal from the secondary network when determining that the terminal accesses the primary network and the secondary network at the same time, and then the terminal can perform data transmission through the primary network. Therefore, the terminal does not need to first send a disconnect request to the first controller to disconnect from the network.
  • the second controller is requested to switch its state in the primary network from the idle state to the connected state to complete the network switching, and when the state in the primary network is switched to the connected state, the connection with the secondary network can be disconnected.
  • the network switching can be completed, so as to avoid the problem that the network switching success rate is low due to the uncertainty of the terminal behavior, on the other hand, the terminal only needs to go through a set of processes to complete the network switching, thereby Save signaling and network resources.
  • the technical process of disconnecting the connection between the terminal and the slave network may be: deleting the identifier corresponding to the identifier of the terminal or the identifier of the connection in the packet data protocol gateway. a connection context of the network; sending a first disconnection request to the first controller, where the first disconnection request carries an identifier of the terminal or an identifier of the connection, where the first controller is the slave network
  • the first disconnection request is used to instruct the first controller to delete a connection context in the first controller corresponding to an identifier of the terminal or an identifier of the connection, and is used to indicate
  • the first controller controls at least one of a security node in the network switching system, a controller of a local network in the slave network, a gateway of a local network, a base station of a local network, and the terminal to delete the terminal
  • the identity or the connection context corresponding to the identity of the connection may be: deleting the identifier corresponding to the identifier of the terminal or the identifier of the connection in the
  • the technical process of disconnecting the connection between the terminal and the slave network may further be: deleting a connection context of the slave network corresponding to the identifier of the terminal in the packet data protocol gateway; Transmitting, to the security node in the network switching system, a second disconnection request, where the second disconnection request carries an identifier of the terminal or an identifier of the connection, where the second disconnection request is used to indicate
  • the security node deletes a connection context of the security node corresponding to the identifier of the terminal or the identifier of the connection, and is used to instruct the security node to control the controller of the first controller and the local network in the slave network
  • At least one of a gateway of the local network, a base station of the local network, and the terminal deletes an identifier of the terminal or a connection context corresponding to the identifier of the connection, where the first controller is a controller in the slave network .
  • the technical process of disconnecting the terminal from the secondary network may be Is based on the identifier of the terminal or the identifier of the connection at the terminal of the packet data protocol gateway
  • the connection state database queries the connection state of the terminal and the slave network, and when the connection state is connected, disconnects the terminal from the slave network.
  • the modified bearer request further carries the macro network conversion information or the identifier of the first controller, where the macro network conversion information is used to indicate that the terminal accesses the primary network and the secondary network at the same time.
  • the first controller is a controller in the slave network. In this case, after the receiving the modified bearer request and determining that the terminal accesses the primary network and the secondary network simultaneously, the technical process of disconnecting the terminal from the secondary network is performed. The method may further include: disconnecting the terminal from the slave network when receiving the macro network conversion information or the identifier of the first controller.
  • a controller which is a controller in a slave network in a network switching system, the controller comprising at least one module, the at least one module being used to implement the first aspect or the first aspect A network switching method provided by any of the implementations.
  • a controller which is a controller in a main network in a network switching system, the controller includes at least one module, and the at least one module is used to implement the second aspect or the second aspect.
  • a network switching method provided by any of the implementations.
  • a packet data protocol gateway is provided, where the packet data protocol gateway simultaneously accesses a slave network and a primary network of the network switching system, where the packet data protocol gateway includes at least one module, and the at least one module is configured to implement the foregoing The network switching method provided by any one of the third aspect or the third aspect.
  • a network switching system comprising the controller as provided in the fourth aspect above and the controller as provided in the fifth aspect above.
  • a network switching system comprising the packet data protocol gateway as provided in the sixth aspect, the controller in the primary network, and the controller in the secondary network.
  • a controller comprising: a memory, a processor, a communication interface, and a bus.
  • the communication interface and the memory are respectively connected to the processor through a bus.
  • the processor is configured to execute program instructions stored in the memory, and the processor implements the network switching method provided by any one of the first aspect or the first aspect of the first aspect by executing the program instructions.
  • a controller comprising: a memory, a processor, a communication interface, and a bus.
  • the communication interface and the memory are respectively connected to the processor through a bus.
  • the processor is configured to execute program instructions stored in the memory, and the processor implements the network switching method provided by any of the possible implementations of the second aspect or the second aspect by executing the program instructions.
  • a packet data protocol gateway comprising: a memory, a processor, a communication interface, and a bus.
  • the communication interface and the memory are respectively connected to the processor through a bus.
  • the processor is configured to execute program instructions stored in the memory, and the processor implements the network switching method provided by any of the possible implementations of the third aspect or the third aspect by executing the program instructions.
  • the second controller in the primary network is at the first The state of the terminal in the primary network is switched from the idle state to the connected state under the instruction of the controller. Therefore, the terminal only needs to send a service request to the second controller to complete the network handover, and does not need the terminal to first send a disconnection request from the first controller to the slave network, and then requests the second controller to The state of the main network can be switched from the idle state to the connected state to complete the network handover. This avoids the problem of low network handover success rate due to the uncertainty of the terminal behavior. On the other hand, the terminal only needs to go through a set. The process can complete the network switch, which saves signaling and network resources.
  • FIG. 1A is a schematic diagram of a networking manner of a primary network according to an embodiment of the present invention.
  • FIG. 1B is a schematic diagram of a networking manner of a slave network according to an embodiment of the present invention.
  • FIG. 1C is a schematic structural diagram of a controller according to an embodiment of the present invention.
  • FIG. 1D is a schematic structural diagram of a packet data protocol gateway PGW according to an embodiment of the present invention.
  • FIG. 2A is a flowchart of a network switching method according to an embodiment of the present invention.
  • FIG. 2B is a flowchart of disconnecting a terminal from a slave network according to an embodiment of the present invention.
  • FIG. 2C is a flowchart of disconnecting a terminal from a slave network according to an embodiment of the present invention.
  • FIG. 2D is a flowchart of disconnecting a terminal from a slave network according to an embodiment of the present invention.
  • FIG. 2E is a flowchart of a first controller sending a disconnection receipt to a second controller according to an embodiment of the present invention.
  • FIG. 2F is a flowchart of a first controller sending a disconnection receipt to a second controller according to an embodiment of the present invention.
  • FIG. 3A is a flowchart of a network switching method according to an embodiment of the present invention.
  • FIG. 3B is a flowchart of disconnecting a terminal from a slave network according to an embodiment of the present invention.
  • FIG. 3C is a flowchart of disconnecting a terminal from a slave network according to an embodiment of the present invention.
  • FIG. 4 is a block diagram of a controller 400 according to an embodiment of the present invention.
  • FIG. 5 is a block diagram of a controller 500 according to an embodiment of the present invention.
  • FIG. 6 is a block diagram of a PGW 600 according to an embodiment of the present invention.
  • FIG. 7 is a block diagram of a network switching system 700 according to an embodiment of the present invention.
  • FIG. 8 is a block diagram of a network switching system 800 according to an embodiment of the present invention.
  • the embodiment of the invention provides a network switching method, which is suitable for network switching of a network switching system including a primary network and a secondary network.
  • the primary network may be an evolved packet system (English: Evolved Packet System; EPS) network
  • the secondary network may be a second access long term evolution (English: Second Access Long Term Evolution; SALTE) network.
  • EPS Evolved Packet System
  • SALTE Second Access Long Term Evolution
  • LTE Long Term Evolution
  • GSM Global System for Mobile
  • WCDMA Wideband Code Division Multiple Access
  • the present invention will briefly describe the networking mode of the primary network and the secondary network by taking the primary network as the EPS network and the secondary network as the SALTE network as an example.
  • FIG. 1A is a schematic diagram of a networking manner of a primary network, where the primary network may include an access device 101, a controller 102, a serving gateway (English: Serving GateWay; SGW) 103, and a packet data protocol gateway. : Packet Data Protocol Gateway; abbreviation: PGW) 104.
  • the controller 102 may be a Mobility Management Entity (MME) or an Authentication Authorization Accounting Server (AAA).
  • MME Mobility Management Entity
  • AAA Authentication Authorization Accounting Server
  • the mobile network control plane network element, the access device 101 may be a base station, etc., which is not specifically limited in the present invention. As shown in FIG.
  • the terminal can access the primary network through the access device 101, the access device 101 can communicate with the controller 102 and the SGW 103, the controller 102 can communicate with the SGW 103, and the SGW 103 can The PGW 104 communicates.
  • the solid line part is the user plane of the main network (the transmission service, the application data is called the user plane, the user plane carries the user application data), and the dotted line part is the control plane of the main network (transmission)
  • the signaling information is called the control plane, and the control plane carries the interactive control information of the user and the network).
  • FIG. 1B is a schematic diagram of a networking manner of a slave network, where the slave network may include a local network 11 and an operator network 12, and the local network 11 may include an access device 111, a controller 112, and a gateway 113.
  • the commerce network 12 may include a controller 121, a security node 122, a PGW 123, and a Home Subscriber Server (HSS) 124.
  • the controller 121 and the controller 112 may be an MME or a mobile network control plane network element such as an AAA server, which is not specifically limited in the present invention.
  • the access device 111 can communicate with the controller 112 and the gateway 113, and can be performed between the controller 112 and the gateway 113.
  • the security node 122 can communicate with the controller 121 and the PGW 123, communication between the controller 121 and the PGW 123 can be performed, communication between the controller 121 and the HSS 124 can be performed, and the controller 121 and the controller 112 Communication is possible between the local gateway 113 and the secure node 122.
  • the solid line portion is the user plane of the slave network
  • the dotted line portion is the control plane of the slave network.
  • the controller 102 and the controller 121 may include a memory 131, a processor 132, a communication interface 133, and a bus 134.
  • Communication interface 133 and memory 131 are coupled to processor 132 via bus 134, respectively.
  • the memory 131 may include a volatile memory (English: Volatile Memory), such as a random access memory (English: Random-access Memory, abbreviation: RAM); the memory 131 may also include a non-volatile memory (English: Non- Volatile memory), such as flash memory (English: Flash Memory), hard disk (English: Hard Disk Drive, abbreviated: HDD) or solid state drive (English: Solid-state Drive, abbreviation: SSD); memory 131 can also include the above categories a combination of memory.
  • the memory 131 can be used to store program instructions. Specifically, the memory 131 can store an operating system 1311 and an application 1312 required for at least one function.
  • the processor 132 may be a central processing unit (English: Central Processing Unit, abbreviated: CPU), a network processor (English: Network Processor, abbreviated: NP) or a combination of a CPU and an NP.
  • Processor 132 may include one or more processing cores, and processor 132 executes the program instructions stored by memory 131 to execute the steps that the controller can perform.
  • the communication interface 133 can be a wired communication access port, a wireless communication interface, or a combination thereof, wherein the wired communication interface can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless communication interface can be a wireless local area network interface, a cellular network communication interface, or a combination thereof.
  • the bus 134 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 134 can be divided into an address bus, a data bus, a control bus, and the like.
  • the PGW 104 and the PGW 123 may include: The memory 141, the processor 142, the communication interface 143, and the bus 144. Communication interface 143 and memory 141 are coupled to processor 142 via bus 144, respectively.
  • the memory 141 may include a volatile memory such as a RAM; the memory 141 may also include a non-volatile memory such as a flash memory, an HDD or an SSD; and the memory 141 may also include a combination of the above types of memories.
  • the memory 141 can be used to store program instructions. Specifically, the memory 141 can store the operating system 1411 and the application 1412 required for at least one function.
  • Processor 142 can be a CPU, NP or a combination of CPU and NP.
  • Processor 142 may include one or more processing cores, and processor 142 executes the program instructions stored by memory 141 to perform the steps that PGW can perform.
  • the communication interface 143 can be a wired communication access port, a wireless communication interface, or a combination thereof, wherein the wired communication interface can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless communication interface can be a wireless local area network interface, a cellular network communication interface, or a combination thereof.
  • the bus 144 can be a PCI bus or an EISA bus or the like.
  • the bus 144 can be divided into an address bus, a data bus, a control bus, and the like.
  • FIG. 2A is a flowchart of a network switching method according to an exemplary embodiment. As shown in FIG. 2A, the network switching method may be applied to the network architecture shown in FIG. 1A and FIG. 1B. The method includes the following steps. :
  • Step 201 The terminal sends a service request to a second controller in the primary network.
  • the terminal may send a service request to the second controller in the primary network after receiving the paging request of the access device 101 in the primary network, where the second controller may be the control described above. 102.
  • the terminal may further send a service request to the second controller after detecting the specified operation, where the specified operation refers to an operation that needs to transmit data through the primary network, for example, the specified operation may be an operation of browsing a web page, etc.
  • the present invention does not specifically limit this.
  • Step 202 The second controller receives a service request sent by the terminal.
  • Step 203 The second controller determines whether the terminal accesses the primary network and the secondary network at the same time, and if yes, performs At step 204, if not, the process is exited.
  • the second controller may determine whether the terminal accesses the primary network and the secondary network at the same time after receiving the foregoing service request.
  • the second controller may perform the foregoing step 203 in multiple manners, specifically:
  • the service request may carry the macro network conversion information or the identifier of the first controller in the network, where the macro network conversion information is used to indicate that the terminal accesses the primary network and the secondary network at the same time.
  • the second controller may determine that the terminal accesses the primary network and the secondary network simultaneously when receiving the macro network conversion information or the identifier of the first controller, and vice versa, the second controller determines that the terminal does not simultaneously Access to the primary and secondary networks.
  • the foregoing first controller may be the controller 121 described above.
  • the service request carries an identifier that may also carry the identifier of the terminal or the connection of the terminal, and the first controller and the second controller may be different controllers.
  • the second controller may send a terminal connection status query request to the first controller, where the terminal connection status query request carries the identifier of the terminal or the identifier of the connection; the first controller receives the terminal connection status query request.
  • the connection state includes one of connected and unconnected; the first controller sends the connection state to the second controller; the second control Receiving a connection status between the terminal and the slave network sent by the first controller, if the connection status is connected, the second controller determines that the terminal accesses the primary network and the secondary network at the same time; otherwise, the second controller determines that the terminal does not It is connected to the primary network and the secondary network at the same time.
  • the service request may also carry the identifier of the terminal or the identifier of the connection of the terminal, but the first controller and the second controller are the same controller.
  • the second controller may query the connection state between the terminal and the slave network in the terminal connection state database of the second controller based on the identifier of the terminal or the identifier of the connection, and when the connection state is connected, the second control The device determines that the terminal accesses the primary network and the secondary network at the same time. Otherwise, the second controller determines that the terminal does not access the primary network and the secondary network at the same time.
  • Step 204 The second controller instructs to disconnect the terminal from the network from the first controller in the network.
  • the second control The manner in which the controller instructs the first controller to disconnect the terminal from the slave network can be divided into the following two types:
  • the second controller and the first controller are different controllers, and the second controller instructing the first controller to disconnect the terminal from the network may include: sending, by the second controller, the first controller Disconnecting the connection request, the disconnection request carrying the identifier of the terminal or the identifier of the connection of the terminal; after receiving the disconnection request sent by the second controller, the first controller disconnects the terminal and the slave based on the disconnection request Network connection.
  • the second controller and the first controller are the same controller, and the second controller instructing the first controller to disconnect the terminal from the network may include: the first controller receives the service sent by the terminal. After requesting and determining that the terminal is simultaneously connected to the slave network and the master network, the disconnect terminal is connected to the slave network.
  • Step 205 The first controller disconnects the connection between the terminal and the slave network based on the indication of the second controller.
  • the first controller can complete the operation of disconnecting the terminal from the slave network by performing the following steps. Specifically, according to whether the security node and the PGW have a control plane signaling transmission channel, the manner in which the first controller disconnects the terminal from the network may be classified into the following two types. It should be noted that the foregoing PGW may be the above The PGW 123 described above may be the security node 122 described above.
  • the embodiment of the present invention may disconnect the terminal from the secondary network by the following steps:
  • Step 21 The first controller deletes a connection context (English: Context) of the slave network corresponding to the identifier of the terminal or the identifier of the connection of the terminal in the first controller.
  • a connection context English: Context
  • the first controller can delete the connection data of the terminal in the local, and the connection data corresponds to the identifier of the terminal or the connection identifier of the terminal.
  • Step 22 The first controller sends a first connection deletion request to the security node, where the first connection deletion request carries the identifier of the terminal or the identifier of the connection.
  • Step 23 After receiving the first connection deletion request, the security node deletes the identifier of the terminal in the security node or the connection context corresponding to the connected identifier.
  • Step 24 The first controller sends a second connection deletion request to the PGW, and the second connection deletion request The identifier of the carrying terminal or the identifier of the connection.
  • Step 25 After receiving the second connection deletion request, the PGW deletes the identifier of the terminal in the PGW or the connection context corresponding to the connected identifier.
  • the first controller may disconnect the terminal from the secondary network by the following steps:
  • Step 31 The first controller deletes a connection context of the slave network corresponding to the identifier of the terminal or the identifier of the connection of the terminal in the first controller.
  • Step 32 The first controller sends a third connection deletion request to the security node, where the third connection deletion request carries the identifier of the terminal or the identifier of the connection.
  • Step 33 After receiving the third connection deletion request, the security node deletes the identifier of the terminal in the security node or the connection context corresponding to the connected identifier.
  • Step 34 The security node sends a fourth connection deletion request to the PGW, and the fourth connection deletion request carries the identifier of the terminal or the identifier of the connection.
  • Step 35 After receiving the fourth connection deletion request, the PGW deletes the identifier of the terminal in the PGW or the connection context corresponding to the connected identifier.
  • the first controller needs to perform the steps of 21 to 25 or 31 to 35 above. Perform steps 41 through 42 below, as shown in Figure 2D:
  • Step 41 The first controller sends a fifth connection deletion request to the controller of the local network, where the fifth connection deletion request carries the identifier of the terminal or the identifier of the connection.
  • controller of the above local network may be the controller 112 described above.
  • Step 42 After receiving the fifth connection deletion request, the controller of the local network deletes the controller.
  • the connection context corresponding to the identity of the terminal or the identity of the connection, and controlling at least one of the gateway of the local network, the base station of the local network, and the terminal to delete the identity of the terminal in the terminal or the connection context corresponding to the identity of the connection.
  • the gateway of the local network may be the gateway 113 described above, and the base station of the local network may be the access device 111 described above.
  • Step 206 After the connection between the terminal and the slave network is disconnected, the first controller instructs the second controller to switch the state of the terminal in the primary network from the idle state to the connected state.
  • the step 206 may specifically include: after the terminal is disconnected from the slave network, the first controller is controlled to the second controller.
  • the device sends a disconnection receipt; after receiving the disconnection receipt, the second controller switches the state of the terminal in the primary network from the idle state to the connected state.
  • the embodiment of the present invention can perform the operation of the first controller to send a disconnection receipt to the second controller by performing the following steps.
  • the manner in which the first controller sends the disconnection receipt to the second controller may be classified into the following two types:
  • the embodiment of the present invention may complete the first controller sending a disconnection receipt to the second controller by the following steps. operating:
  • Step 51 The security node sends a first connection deletion receipt to the first controller according to the first connection deletion request, where the first connection deletion receipt is used to indicate that the security node deletes the identifier of the terminal or the connection context corresponding to the connected identifier.
  • Step 52 The PGW sends a second connection deletion receipt to the first controller according to the second connection deletion request, where the second connection deletion receipt is used to instruct the PGW to delete the identifier of the terminal or the connection context corresponding to the connected identifier.
  • Step 53 After receiving the first connection deletion receipt and the second connection deletion receipt, the first controller sends a disconnection receipt to the second controller.
  • the embodiment of the present invention may complete the operation of the first controller sending a disconnection receipt to the second controller by the following steps. :
  • Step 61 The PGW sends a fourth connection deletion receipt to the security node according to the fourth connection deletion request, where the fourth connection deletion receipt is used to instruct the PGW to delete the identifier of the terminal or the connection context corresponding to the connected identifier.
  • Step 62 The security node sends a third connection deletion receipt to the first controller according to the third connection deletion request, where the third connection deletion receipt is used to indicate that the security node and the PGW delete the connection identifier of the terminal or the connection context corresponding to the connected identifier.
  • Step 63 After receiving the third connection deletion receipt, the first controller sends a disconnection receipt to the second controller.
  • the embodiment of the present invention performs the above 51 to 53 or In addition to the steps of 61 to 63, the following steps are further performed: the first controller receives a fifth connection deletion receipt sent by the controller in the local network based on the fifth connection deletion request, and the fifth connection deletion receipt is used to indicate the local network. At least one of the gateway, the base station of the local network, and the controller deletes the identity of the terminal or the connection context corresponding to the identifier of the connection.
  • step 53 or step 63 the first controller receives the first connection deletion receipt, the second connection deletion receipt, and the fifth connection deletion receipt, or only receives the third connection deletion receipt. After the receipt is deleted from the fifth connection, the disconnection receipt can be sent to the second controller.
  • the first controller and the second controller may be the same controller.
  • the second controller may receive the security node, the PGW, and the local network in the same manner as the first controller.
  • the controller sends a connection deletion receipt.
  • the second controller can receive the first connection deletion receipt, the second connection deletion receipt, and the fifth connection deletion receipt, or can receive the third connection deletion receipt and After the fifth connection deletes the receipt, or can be deleted after receiving the first connection After the receipt and the second connection delete the receipt, or after receiving the third connection deletion receipt, the state of the terminal in the primary network is switched from the idle state to the connected state.
  • the second controller can complete the operation of switching the state of the terminal in the main network from the idle state to the connected state by using the following manner:
  • the second controller establishes an air interface connection between the base station and the terminal of the primary network;
  • the second controller sends a modify bearer request to the PGW in the primary network, so that the PGW acquires the identifier of the base station of the primary network.
  • the PGW may send data through the base station of the primary network when the data is sent to the terminal.
  • the base station of the foregoing primary network may be the access device 101 described above, and the PGW in the primary network may be the PGW 104 described above.
  • the network switching method provided by this embodiment is configured to disconnect the terminal from the secondary network by the first controller in the secondary network during the network switching process, and disconnect the connection between the terminal and the secondary network.
  • the second controller in the primary network switches the state of the terminal in the primary network from the idle state to the connected state under the instruction of the first controller. Therefore, the terminal only needs to send a service request to the second controller to complete the network handover, and does not need the terminal to first send a disconnection request from the first controller to the slave network, and then requests the second controller to The state of the main network can be switched from the idle state to the connected state to complete the network handover. This avoids the problem of low network handover success rate due to the uncertainty of the terminal behavior.
  • the terminal only needs to go through a set. The process can complete the network switch, which saves signaling and network resources.
  • FIG. 3A is a flowchart of a network switching method according to an exemplary embodiment. As shown in FIG. 3A, the network switching method may be applied to the network architecture shown in FIG. 1A and FIG. 1B. The method includes the following steps. :
  • Step 301 The terminal sends a service request to a second controller in the primary network.
  • the terminal may send a service request to the second controller in the primary network after receiving the paging request of the access device 101 in the primary network, where the second controller may be the foregoing control Controller 102.
  • the terminal may further send a service request to the second controller after detecting the specified operation, where the specified operation refers to an operation that needs to transmit data through the primary network, for example, the specified operation may be an operation of browsing a web page, etc.
  • the present invention does not specifically limit this.
  • the foregoing service request may carry the identifier of the terminal, the identifier of the connection of the terminal, or the macro network conversion information, where the macro network conversion information is used to indicate that the terminal accesses the primary network and the secondary network at the same time.
  • Step 302 After receiving the service request, the second controller establishes an air interface connection between the base station of the primary network and the terminal.
  • Step 303 The second controller sends a modify bearer request to the PGW, so that the PGW acquires the identifier of the base station of the primary network, where the modified bearer request carries the identifier of the terminal or the identifier of the connection of the terminal.
  • the state of the terminal in the primary network has been switched from the idle state to the connected state, but since the connection between the terminal and the secondary network has not been disconnected at this time, the terminal cannot pass the primary.
  • the network transmits data, and the terminal can transmit data through the main network only after the connection between the terminal and the slave network is disconnected.
  • the second controller in the foregoing primary network may be the controller 102 described above, and the base station of the primary network may be the access device 101 described above, and the PGW may simultaneously access the primary device.
  • the PGW 104 and the PGW 123 described above may be the same device, that is, the PGW in step 301.
  • Step 304 The PGW receives the modify bearer request.
  • Step 305 After receiving the modification bearer request and determining that the terminal accesses the primary network and the secondary network at the same time, the PGW disconnects the terminal from the secondary network.
  • the PGW can determine that the terminal accesses both the primary network and the secondary network in the following two ways, specifically:
  • the modified bearer request may also carry the macro network conversion information or the identifier of the first controller, and the first controller is a controller in the slave network, that is, the controller 121 described above.
  • the PGW receives the macro network conversion information or the identifier of the first controller, it can be determined that the terminal accesses the primary network and the secondary network at the same time.
  • the second controller may query the local terminal connection status database based on the identifier of the terminal carried in the service request or the identifier of the connection of the terminal. If the connection status between the terminal and the slave network is connected, the second controller may determine that the terminal accesses the primary network and the secondary network at the same time. At this time, the second controller may generate macro network conversion information, and carry the macro network conversion information in the modified bearer request sent by the PGW.
  • the PGW queries the connection status between the terminal and the slave network in the local terminal connection state database based on the identifier of the terminal or the identifier of the connection of the terminal.
  • the PGW can determine that the terminal accesses the master at the same time. Net and from the net.
  • the PGW may not include the macro network conversion information in the modified bearer request, and the PGW may query the connection state between the terminal and the slave network based on the identifier of the terminal in the modification bearer request or the connection identifier of the terminal, thereby Determine whether the terminal accesses both the primary network and the secondary network.
  • the PGW can disconnect the terminal from the slave network in the following two ways, specifically:
  • the embodiment of the present invention can disconnect the terminal from the network by the following steps:
  • Step 71 The PGW deletes the connection context of the slave network corresponding to the identifier of the terminal or the identifier of the connection in the UE.
  • Step 72 The PGW sends a first disconnect request to the first controller, where the first disconnect request carries an identifier of the terminal or an identifier of the connection.
  • Step 73 After receiving the first disconnection request, the first controller deletes the connection context corresponding to the identifier of the terminal or the identifier of the connection in the local.
  • Step 74 The first controller sends a third disconnect request to the security node, where the third disconnect request carries an identifier of the terminal or an identifier of the connection.
  • Step 75 After receiving the third disconnection request, the security node deletes the connection context corresponding to the identifier of the terminal or the identifier of the connection in the local.
  • Step 76 The first controller sends a fourth disconnect request to the controller of the local network, where the fourth disconnect request carries an identifier of the terminal or an identifier of the connection.
  • Step 77 After receiving the fourth disconnection request, the controller of the local network deletes the connection context corresponding to the identifier of the terminal or the identifier of the connection in the local network, and controls at least the gateway of the local network, the base station of the local network, and the terminal. A connection context that deletes the identity of the terminal or the identity of the connection.
  • the embodiment of the present invention may disconnect the terminal from the network by the following steps:
  • Step 81 The PGW deletes the connection context of the slave network corresponding to the identifier of the terminal in itself.
  • Step 82 The PGW sends a second disconnect request to the security node, where the second disconnect request carries the identifier of the terminal or the identifier of the connection.
  • Step 83 After receiving the second disconnection request, the security node deletes the connection context corresponding to the identifier of the terminal or the identifier of the connection in the local.
  • Step 84 The security node sends a fifth disconnection request to the first controller, where the fifth disconnection request carries the identifier of the terminal or the identifier of the connection.
  • Step 85 After receiving the fifth disconnection request, the first controller deletes the connection context corresponding to the identifier of the terminal or the identifier of the connection in the local.
  • Step 86 The first controller sends a sixth disconnect request to the controller of the local network, where the sixth disconnect request carries an identifier of the terminal or an identifier of the connection.
  • Step 87 After receiving the sixth disconnection request, the controller of the local network deletes the connection context corresponding to the identifier of the terminal or the identifier of the connection in the local network, and controls the gateway of the local network, the base station of the local network, and the terminal. At least one deletes the identity of the terminal or the connection context corresponding to the identifier of the connection.
  • the security node may be the security node 122 described above, the local network.
  • the controller may be the controller 112 described above, the gateway of the local network may be the gateway 113 described above, and the base station of the local network may be the access device 111 described above.
  • first controller and the second controller may be the same controller or different controllers, which is not specifically limited in the present invention.
  • the PGW in the network switching process, can receive the modify bearer request sent by the second controller in the primary network, where the modified bearer request indicates that the state of the terminal in the primary network has been Switching to the connected state, at this time, the PGW can disconnect the terminal from the secondary network when determining that the terminal accesses the primary network and the secondary network at the same time, and then the terminal can perform data transmission through the primary network.
  • the terminal does not need to send the disconnection request from the network to the first controller first, and then requests the second controller to switch the state in the main network from the idle state to the connected state to complete the network switching, and
  • the connection with the secondary network can be disconnected, that is, the network switching can be completed, so that the network switching success rate due to the uncertainty of the terminal behavior is avoided on the one hand.
  • the terminal only needs to go through a set of processes to complete the network switch, which saves signaling and network resources.
  • FIG. 4 is a block diagram of a controller 400, according to an exemplary embodiment.
  • the controller 400 is a controller in the slave network.
  • the controller 400 includes a disconnect module 401 and an indication module 402.
  • the disconnecting module 401 is configured to perform the operations performed by the first controller in the above step 205.
  • the indication module 402 is configured to perform the operations performed by the first controller in the foregoing step 206.
  • the controller provided in this embodiment indicates that the second controller in the main network is instructed by disconnecting the terminal from the network during the network switching process and disconnecting the connection between the terminal and the slave network.
  • the state of the terminal in the primary network is switched from the idle state to the connected state. Therefore, the terminal only needs to send a service request to the second controller to complete the network handover, and does not need the terminal to first send a disconnection request from the first controller to the slave network, and then requests the second controller to
  • the state of the main network can be switched from the idle state to the connected state to complete the network handover. This avoids the problem of low network handover success rate due to the uncertainty of the terminal behavior.
  • the terminal only needs to go through a set. The process can be completed Network switching, which saves signaling and network resources.
  • FIG. 5 is a block diagram of a controller 500, according to an exemplary embodiment.
  • the controller 500 is a controller in the primary network.
  • the controller 500 includes a receiving module 501, an indicating module 502, and a switching module 503.
  • the receiving module 501 is configured to perform the operations of step 202 above.
  • the indication module 502 is configured to perform the operations performed by the second controller in the foregoing steps 203 and 204.
  • the switching module 503 is configured to perform the operations performed by the second controller in the foregoing step 206.
  • the controller provided in this embodiment indicates that the first controller disconnects the connection between the terminal and the slave network during the network switching process, and after the terminal is disconnected from the slave network, the first control is performed.
  • the state of the terminal in the primary network is switched from the idle state to the connected state under the indication of the device. Therefore, the terminal only needs to send a service request to the second controller to complete the network handover, and does not need the terminal to first send a disconnection request from the first controller to the slave network, and then requests the second controller to
  • the state of the main network can be switched from the idle state to the connected state to complete the network handover. This avoids the problem of low network handover success rate due to the uncertainty of the terminal behavior.
  • the terminal only needs to go through a set. The process can complete the network switch, which saves signaling and network resources.
  • FIG. 6 is a block diagram of a PGW 600, according to an exemplary embodiment.
  • the PGW 600 is simultaneously connected to the primary network and the secondary network.
  • the PGW 600 includes a receiving module 601 and a disconnecting module 602.
  • the receiving module 601 is configured to perform the operation of the PGW in the above step 304.
  • the disconnecting module 602 is configured to perform the operation of the PGW in the above step 305.
  • the PGW may receive a modify bearer request sent by the second controller in the primary network during the network handover process, where the modify bearer request indicates that the state of the terminal in the primary network has been switched to the connection.
  • the PGW can disconnect the terminal from the secondary network when determining that the terminal accesses the primary network and the secondary network at the same time, and then the terminal can perform data transmission through the primary network. Thereby making the terminal There is no need to first send a connection request to the first controller to disconnect from the network, and then request the second controller to switch its state in the primary network from the idle state to the connected state to complete the network switching, and in the primary network.
  • the connection with the slave network can be disconnected, that is, the network switch can be completed, thereby avoiding the problem that the network switching success rate is low due to the uncertainty of the terminal behavior.
  • the terminal only needs to go through a set of processes to complete the network switching, thereby saving signaling and network resources.
  • FIG. 7 is a block diagram of a network switching system 700, according to an exemplary embodiment.
  • the network switching system 700 includes a first controller 701 and a second controller 702.
  • the first controller 701 is configured to perform the operations performed by the first controller in the embodiment shown in FIG. 2A.
  • the second controller 702 is configured to perform operations performed by the second controller in the embodiment shown in FIG. 2A.
  • the network switching system 700 may further include one or more of a security node, a PGW, a local network controller, a gateway of a local network, a base station of a local network, and a terminal, which are not specifically limited by the present invention.
  • the network switching system disconnects the terminal from the secondary network by the first controller in the secondary network during the network switching process, and disconnects the connection between the terminal and the secondary network.
  • the second controller in the primary network switches the state of the terminal in the primary network from the idle state to the connected state under the instruction of the first controller. Therefore, the terminal only needs to send a service request to the second controller to complete the network handover, and does not need the terminal to first send a disconnection request from the first controller to the slave network, and then requests the second controller to The state of the main network can be switched from the idle state to the connected state to complete the network handover. This avoids the problem of low network handover success rate due to the uncertainty of the terminal behavior.
  • the terminal only needs to go through a set. The process can complete the network switch, which saves signaling and network resources.
  • FIG. 8 is a block diagram of a network switching system 800, according to an exemplary embodiment.
  • the network switching system 800 includes a second controller 801 and a PGW 802.
  • the second controller 801 is configured to perform operations performed by the second controller in the embodiment shown in FIG. 3A.
  • the PGW 802 is configured to perform the operations performed by the PGW in the embodiment shown in FIG. 3A.
  • the network switching system 800 may further include one or more of a security node, a first controller, a local network controller, a gateway of a local network, a base station of a local network, and a terminal, and the present invention does not Specifically limited.
  • the PGW may receive the modify bearer request sent by the second controller in the primary network, where the modified bearer request indicates that the state of the terminal in the primary network has been Switching to the connected state, at this time, the PGW can disconnect the terminal from the secondary network when determining that the terminal accesses the primary network and the secondary network at the same time, and then the terminal can perform data transmission through the primary network.
  • the terminal does not need to send the disconnection request from the network to the first controller first, and then requests the second controller to switch the state in the main network from the idle state to the connected state to complete the network switching, and
  • the connection with the secondary network can be disconnected, that is, the network switching can be completed, so that the network switching success rate due to the uncertainty of the terminal behavior is avoided on the one hand.
  • the terminal only needs to go through a set of processes to complete the network switch, which saves signaling and network resources.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Abstract

本发明公开了一种网络切换方法、控制器、网关及系统，属于通信技术领域。所述方法包括：在网络切换过程中，由从网中的第一控制器断开终端与从网的连接，并在终端与从网的连接断开后，由主网中的第二控制器在该第一控制器的指示下将该终端在主网中的状态由空闲态切换至连接态。从而使得终端只需要向第二控制器发送服务请求即可完成网络切换，而不需要终端先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。

Description

网络切换方法、控制器、网关及系统 技术领域
本发明涉及通信领域，特别涉及一种网络切换方法、控制器、网关及系统。
背景技术
在实际应用中，终端可以同时接入两个通信网络，即主网和从网，同时接入两个通信网络指的是终端在主网中的状态为空闲态时终端也可以接入从网，然而，基于技术及商业上的限制，终端却无法同时通过主网和从网进行数据传输，也即是，终端在主网中的状态必须为空闲态时才能与从网连接，而终端在主网中的状态由空闲态切换至连接态时，必须与从网断开连接。
相关技术中，在终端同时接入主网和从网中，且终端需要将其在主网中的状态由空闲态切换至连接态时，终端需要先向从网中的控制器请求断开与从网的连接，并在与从网的连接断开后向主网的控制器请求由空闲态切换至连接态。
在实现本发明的过程中，发明人发现现有技术至少存在以下问题：
实际应用中，由于终端并不是一个可以信任的设备，其行为存在着各种不确定性，因此在将终端在主网中的状态由空闲态切换至连接态的过程中，终端很可能在未与从网断开连接的情况下即执行向主网的控制器请求由空闲态切换至连接态的操作，而这会导致错误产生，使终端的状态切换失败，导致终端网络切换成功率较低。此外，相关技术中，终端需要经过断开与从网的连接和状态切换两套流程才能实现将自身在主网中的状态由空闲态切换至连接态的目的，因此，在这个过程中会产生过多的信令，对网络资源造成浪费。
发明内容
为了解决现有技术中终端网络切换成功率较低和网络资源浪费的问题，本发明实施例提供了一种网络切换方法、控制器、网关及系统。所述技术方案如下：
第一方面，提供了一种网络切换方法，用于网络切换系统中的第一控制器中，所述网络切换系统包括：主网和从网，所述第一控制器为所述从网中的控制器，所述方法包括：
在第二控制器接收到终端发送的服务请求，并确定所述终端同时接入所述主网和所述从网中后，所述第一控制器断开所述终端与所述从网的连接，所述第二控制器为所述主网中的控制器；
所述第一控制器令所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态。
本发明实施例所示的技术方案，在网络切换过程中，由从网中的第一控制器断开终端与从网的连接，并在终端与从网的连接断开后，由上述第一控制器指示主网中的第二控制器将该终端在主网中的状态由空闲态切换至连接态。从而使得终端只需要向第二控制器发送服务请求即可完成网络切换，而不需要终端先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
在实际应用中，当上述第一控制器和第二控制器为不同的控制器时，上述第一控制器断开所述终端与所述从网的连接的技术过程具体可以为：所述第一控制器接收所述第二控制器发送的断开连接请求，所述断开连接请求为所述第二控制器在接收到所述服务请求，并确定所述终端同时接入所述主网和所述从网中后发送的，所述断开连接请求携带所述终端的标识或所述终端的连接的标识；基于所述断开连接请求，所述第一控制器断开所述终端与所述从网的连接。
对应地，上述第一控制器令所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态的技术过程具体可以为：在所述终端与所述从网断开连接后，所述第一控制器向所述第二控制器发送断开连接回执，使得所述第二控制器在接收到所述断开连接回执后，将所述终端在所述主网中的状态由空闲态切换至连接态。
当然，在实际应用中，还存在所述第一控制器与所述第二控制器为同一控制器的情况，此时，上述在第二控制器接收到终端发送的服务请求，并确定所述终端同时接入所述主网和所述从网中后，所述第一控制器断开所述终端与所述从网的连接的技术过程具体可以为：所述第一控制器接收所述终端发送的所述服务请求，并确定所述终端同时接入所述从网和所述主网中后，所述第一控制器断开所述终端与所述从网连接。
此外，无论上述第一控制器与第二控制器是否为同一控制器，本发明实施例均可以通过下述步骤完成第一控制器断开所述终端与所述从网的连接的技术过程，具体地：所述第一控制器删除所述第一控制器中与所述终端的标识或者所述终端的连接的标识对应的所述从网的连接上下文；当所述从网中的安全节点与所述从网中的分组数据协议网关不存在控制面信令传输通道时，所述第一控制器向所述安全节点发送第一连接删除请求，所述第一连接删除请求携带所述终端的标识或者所述连接的标识，所述第一连接删除请求用于指示所述安全节点删除所述终端的标识或者所述连接的标识对应的连接上下文；所述第一控制器向所述分组数据协议网关发送第二连接删除请求，所述第二连接删除请求携带所述终端的标识或者所述连接的标识，所述第二连接删除请求用于指示所述分组数据协议网关删除所述终端的标识或者所述连接的标识对应的连接上下文；当所述安全节点与所述分组数据协议网关存在控制面信令传输通道时，所述第一控制器向所述安全节点发送第三连接删除请求，所述第三连接删除请求携带所述终端的标识或者所述连接的标识，所述第三连接删除请求用于指示所述安全节点删除所述终端的标识或者所述连接的标识对应的连接上下 文，并用于指示所述安全节点在接收到所述第三连接删除请求后向所述分组数据协议网关发送第四连接删除请求，所述第四连接删除请求携带所述终端的标识或者所述连接的标识，所述第四连接删除请求用于指示所述分组数据协议网关删除所述终端的标识或者所述连接的标识对应的连接上下文；当所述终端通过本地网络接入所述从网中时，所述第一控制器向所述本地网络的控制器发送第五连接删除请求，所述第五连接删除请求携带所述终端的标识或者所述连接的标识，所述第五连接删除请求用于指示所述控制器删除所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述控制器控制所述本地网络的网关、所述本地网络的基站和所述终端中的至少一个删除所述终端的标识或者所述连接的标识对应的连接上下文。
对应地，当上述第一控制器与第二控制器不为同一控制器时，上述在所述终端与所述从网断开连接后，所述第一控制器向所述第二控制器发送断开连接回执的技术过程具体可以为：当所述安全节点与所述分组数据协议网关不存在控制面信令传输通道时，所述第一控制器接收所述安全节点基于所述第一连接删除请求发送的第一连接删除回执，所述第一连接删除回执用于指示所述安全节点删除了所述终端的标识或者所述连接的标识对应的连接上下文；所述第一控制器接收所述分组数据协议网关基于所述第二连接删除请求发送的第二连接删除回执，所述第二连接删除回执用于指示所述分组数据协议网关删除了所述终端的标识或者所述连接的标识对应的连接上下文；当所述安全节点与所述分组数据协议网关存在控制面信令传输通道时，所述第一控制器接收所述安全节点基于所述第三连接删除请求发送的第三连接删除回执，所述第三连接删除回执为所述安全节点在接收到所述分组数据协议网关发送的第四连接删除回执后发送的，所述第四连接删除回执用于指示所述分组数据协议网关删除了所述终端的标识或者所述连接的标识对应的连接上下文，所述第三连接删除回执用于指示所述安全节点和所述分组数据协议网关删除了所述终端的标识或者所述连接的标识对应的连接上下文；当所述终端通过所述本地网络接入所述从 网中时，所述第一控制器接收所述控制器基于所述第五连接删除请求发送的第五连接删除回执，所述第五连接删除回执用于指示所述本地网络的网关、所述本地网络的基站、所述终端中的至少一个和所述控制器删除了所述终端的标识或者所述连接的标识对应的连接上下文；所述第一控制器在接收到所述第一连接删除回执、第二连接删除回执、第三连接删除回执和第五连接删除回执中的至少一个后，向所述第二控制器发送所述断开连接回执。
第二方面，提供了一种网络切换方法，用于网络切换系统中的第二控制器中，所述网络切换系统包括：主网和从网，所述第二控制器为所述主网中的控制器，所述方法包括：
所述第二控制器接收终端发送的服务请求，所述服务请求为所述终端在接收到所述主网的寻呼请求或者检测到指定操作后发送的，所述指定操作为需要通过所述主网传输数据的操作；
当接收到所述服务请求并确定所述终端同时接入所述从网和所述主网中后，所述第二控制器令第一控制器断开所述终端与所述从网的连接，所述第一控制器为所述从网中的控制器；
在所述终端与所述从网断开连接后，所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态。
本发明实施例所示的技术方案，在网络切换过程中，主网中的第二控制器在确定终端同时接入主网和从网中后，指示从网中的第一控制器断开终端与从网的连接，并在终端与从网的连接断开后，第二控制器将该终端在主网中的状态由空闲态切换至连接态。从而使得终端只需要向第二控制器发送服务请求即可完成网络切换，而不需要终端先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
在实际应用中，当上述第一控制器和第二控制器为不同的控制器时，所述服务请求携带所述终端的标识或者所述终端的连接的标识时，上述第二控制器令所述第一控制器断开所述终端与所述从网的连接的技术过程具体可以包括：所述第二控制器向所述第一控制器发送断开连接请求，所述断开连接请求携带所述终端的标识或者所述连接的标识，使得所述第一控制器基于所述断开连接请求，断开所述终端与所述从网的连接。
对应地，上述在所述终端与所述从网断开连接后，所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态的技术过程具体可以包括：在接收到所述第一控制器发送的断开连接回执后，所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态，所述断开连接回执用于指示所述终端与所述从网已经断开了连接。
此外，当上述第一控制器和第二控制器为不同的控制器时，所述服务请求携带所述终端的标识或者所述终端的连接的标识，上述当接收到所述服务请求并确定所述终端同时接入从网和所述主网中后，所述第二控制器令所述第一控制器断开所述终端与所述从网的连接的技术过程具体可以包括：所述第二控制器向所述第一控制器发送终端连接状态查询请求，所述终端连接状态查询请求携带所述终端的标识或者所述连接的标识，以使所述第一控制器返回所述终端与所述从网的连接状态，所述连接状态包括已连接和未连接中的一种；所述第二控制器接收所述第一控制器发送的所述终端与所述从网的连接状态，若所述连接状态为已连接，则所述第二控制器令所述第一控制器断开所述终端与所述从网的连接。
而当上述第一控制器和第二控制器为同一控制器时，所述服务请求携带所述终端的标识或者所述终端的连接的标识，上述当接收到所述服务请求并确定所述终端同时接入从网和所述主网中时，所述第二控制器令所述第一控制器断开所述终端与所述从网的连接的技术过程可以为：所述第二控制器基于所述终端的标识或者所述连接的标识在所述第二控制器的终端连接状态数据库中查 询所述终端与所述从网的连接状态，当所述连接状态为已连接时，所述第二控制器令所述第一控制器断开所述终端与所述从网的连接。
在实际应用中，所述服务请求还可以携带宏网转换信息或所述第一控制器的标识，所述宏网转换信息用于指示所述终端同时接入所述主网和所述从网中；此时，上述当接收到所述服务请求并确定所述终端同时接入从网和所述主网中后，所述第二控制器令所述第一控制器断开所述终端与所述从网的连接的技术过程具体可以包括：当接收到所述宏网转换信息或所述第一控制器的标识时，所述第二控制器令所述第一控制器断开所述终端与所述从网的连接。
此外，上述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态的技术过程具体可以包括：所述第二控制器通过所述主网的基站与所述终端建立空口连接；所述第二控制器向所述主网中的分组数据协议网关发送修改承载请求，以使所述分组数据协议网关获取所述主网的基站的标识。
第三方面，提供了一种网络切换方法，用于网络切换系统中的分组数据协议网关中，所述网络切换系统包括：主网和从网，所述分组数据协议网关同时接入所述主网和所述从网中，所述方法包括：
接收第二控制器发送的修改承载请求，所述修改承载请求携带终端的标识或者所述终端的连接的标识，所述修改承载请求为所述第二控制器在通过所述主网的基站与所述终端建立了空口连接后发送的，所述第二控制器为所述主网的控制器；
在接收到所述修改承载请求并确定所述终端同时接入所述主网和所述从网中后，断开所述终端与所述从网的连接。
本发明实施例所示的技术方案，在网络切换过程中，分组数据协议网关可以接收主网中的第二控制器发送的修改承载请求，该修改承载请求表明终端在主网中的状态已经切换至连接态，此时，分组数据协议网关可以在确定终端同时接入主网和从网中时，断开终端与从网的连接，而后终端即可通过主网进行数据传输。从而使得终端不需要先向第一控制器发送断开与从网的连接请求， 而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，而在主网中的状态切换至连接态时即可断开与从网的连接，也即是即可完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
在实际应用中，上述断开所述终端与所述从网的连接的技术过程具体可以为：删除所述分组数据协议网关中与所述终端的标识或者所述连接的标识对应的所述从网的连接上下文；向第一控制器发送第一断开连接请求，所述第一断开连接请求携带所述终端的标识或者所述连接的标识，所述第一控制器为所述从网中的控制器，所述第一断开连接请求用于指示所述第一控制器删除所述第一控制器中与所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述第一控制器控制所述网络切换系统中的安全节点、所述从网中本地网络的控制器、本地网络的网关、本地网络的基站和所述终端中的至少一个删除所述终端的标识或者所述连接的标识对应的连接上下文。
在实际应用中，上述断开所述终端与所述从网的连接的技术过程具体还可以为：删除所述分组数据协议网关中与所述终端的标识对应的所述从网的连接上下文；向所述网络切换系统中的安全节点发送第二断开连接请求，所述第二断开连接请求携带所述终端的标识或者所述连接的标识，所述第二断开连接请求用于指示所述安全节点删除所述安全节点中与所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述安全节点控制第一控制器、所述从网中本地网络的控制器、本地网络的网关、本地网络的基站和所述终端中的至少一个删除所述终端的标识或者所述连接的标识对应的连接上下文，所述第一控制器为所述从网中的控制器。
在实际应用中，上述在接收到所述修改承载请求并确定所述终端同时接入所述主网和所述从网中后，断开所述终端与所述从网的连接的技术过程可以为：基于所述终端的标识或者所述连接的标识在所述分组数据协议网关的终端 连接状态数据库中查询所述终端与所述从网的连接状态，当所述连接状态为已连接时，断开所述终端与所述从网的连接。
此外，在实际应用中，上述修改承载请求还携带宏网转换信息或第一控制器的标识，所述宏网转换信息用于指示所述终端同时接入所述主网和所述从网中，所述第一控制器为所述从网中的控制器。在这种情况下，上述在接收到所述修改承载请求并确定所述终端同时接入所述主网和所述从网中后，断开所述终端与所述从网的连接的技术过程还可以包括：当接收到所述宏网转换信息或者所述第一控制器的标识时，断开所述终端与所述从网的连接。
第四方面，提供了一种控制器，该控制器为网络切换系统中从网中的控制器，该控制器包括至少一个模块，该至少一个模块用于实现上述第一方面或第一方面中任意一种实现方式所提供的网络切换方法。
第五方面，提供了一种控制器，该控制器为网络切换系统中主网中的控制器，该控制器包括至少一个模块，该至少一个模块用于实现上述第二方面或第二方面中任意一种实现方式所提供的网络切换方法。
第六方面，提供了一种分组数据协议网关，该分组数据协议网关同时接入网络切换系统的从网和主网中，该分组数据协议网关包括至少一个模块，该至少一个模块用于实现上述第三方面或第三方面中任意一种实现方式所提供的网络切换方法。
第七方面，提供了一种网络切换系统，该网络切换系统包括如上述第四方面所提供的控制器和如上述第五方面所提供的控制器。
第八方面，提供了一种网络切换系统，该网络切换系统包括如上述第六方面所提供的分组数据协议网关、主网中的控制器和从网中的控制器。
第九方面，提供了一种控制器，该控制器包括：存储器、处理器、通信接口和总线。其中，通信接口和存储器分别通过总线与处理器连接。处理器被配置为执行存储器中存储的程序指令，处理器通过执行程序指令来实现上述第一方面或第一方面中任意一种可能的实现方式所提供的网络切换方法。
第十方面，提供了一种控制器，该控制器包括：存储器、处理器、通信接口和总线。其中，通信接口和存储器分别通过总线与处理器连接。处理器被配置为执行存储器中存储的程序指令，处理器通过执行程序指令来实现上述第二方面或第二方面中任意一种可能的实现方式所提供的网络切换方法。
第十一方面，提供了一种分组数据协议网关，该分组数据协议网关包括：存储器、处理器、通信接口和总线。其中，通信接口和存储器分别通过总线与处理器连接。处理器被配置为执行存储器中存储的程序指令，处理器通过执行程序指令来实现上述第三方面或第三方面中任意一种可能的实现方式所提供的网络切换方法。
本发明实施例提供的技术方案的有益效果是：
通过在网络切换过程中，由从网中的第一控制器断开终端与从网的连接，并在终端与从网的连接断开后，由主网中的第二控制器在该第一控制器的指示下将该终端在主网中的状态由空闲态切换至连接态。从而使得终端只需要向第二控制器发送服务请求即可完成网络切换，而不需要终端先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1A是本发明实施例提供的主网的组网方式的示意图。
图1B是本发明实施例提供的从网的组网方式的示意图。
图1C是本发明实施例提供的控制器的结构示意图。
图1D是本发明实施例提供的分组数据协议网关PGW的结构示意图。
图2A是本发明实施例提供的一种网络切换方法的流程图。
图2B是本发明实施例提供的一种断开终端与从网的连接的流程图。
图2C是本发明实施例提供的一种断开终端与从网的连接的流程图。
图2D是本发明实施例提供的一种断开终端与从网的连接的流程图。
图2E是本发明实施例提供的一种第一控制器向第二控制器发送断开连接回执的流程图。
图2F是本发明实施例提供的一种第一控制器向第二控制器发送断开连接回执的流程图。
图3A是本发明实施例提供的一种网络切换方法的流程图。
图3B是本发明实施例提供的一种断开终端与从网的连接的流程图。
图3C是本发明实施例提供的一种断开终端与从网的连接的流程图。
图4是本发明实施例提供的一种控制器400的框图。
图5是本发明实施例提供的一种控制器500的框图。
图6是本发明实施例提供的一种PGW 600的框图。
图7是本发明实施例提供的一种网络切换系统700的框图。
图8是本发明实施例提供的一种网络切换系统800的框图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
本发明实施例提供了一种网络切换方法，适用于对包含主网和从网的网络切换系统进行网络切换。其中，该主网可以为演进的分组系统(英文：Evolved Packet System；简称：EPS)网络，该从网可以为第二接入长期演进(英文：Second Access Long Term Evolution；简称：SALTE)网络。当然，在实际应用 中，该主网和从网还可以为其他形式的网络，如长期演进(英文：Long Term Evolution；简称：LTE)网络、家庭基站网络、无线局域网、全球移动通信系统(英文：Global System for Mobile Communication；简称：GSM)网络、宽带码分多址(英文：Wideband Code Division Multiple Access；简称：WCDMA)网络等，对此本发明不做具体限定。下面，本发明将以主网为EPS网络，从网为SALTE网络为例对主网和从网的组网方式进行简要说明。
如图1A所示为主网的组网方式的示意图，其中，主网可以包括接入设备101、控制器102、服务网关(英文：Serving GateWay；简称：SGW)103和分组数据协议网关(英文：Packet Data Protocol Gateway；简称：PGW)104。在实际应用中，该控制器102可以为移动性管理网元(英文：Mobility Management Entity；简称：MME)或者为如鉴权授权计费服务器(英文：Authentication Authorization Accounting Server；简称：AAA Server)的移动网络控制面网元，该接入设备101可以为基站等，本发明对此不做具体限定。如图1A所示，终端可以通过接入设备101接入该主网中，接入设备101可以与控制器102和SGW 103进行通信，控制器102可以和SGW 103进行通信，而SGW 103可以和PGW 104进行通信。如同1A所示，实线部分为该主网的用户面(传输业务、应用数据的叫做用户面，用户面上承载的是用户的应用数据)，而虚线部分为该主网的控制面(传输信令信息的叫做控制面，控制面上承载的是用户和网络的交互控制信息)。
如图1B所示为从网的组网方式的示意图，其中，从网可以包括本地网络11和运营商网络12，该本地网络11可以包括接入设备111、控制器112和网关113，该运营商网络12可以包括控制器121、安全节点122、PGW 123和归属签约用户服务器(英文：Home Subscriber Server；简称：HSS)124。在实际应用中，该控制器121和控制器112可以为MME或者为如AAA Server的移动网络控制面网元，本发明对此不做具体限定。如图1B所示，接入设备111可以和控制器112及网关113进行通信，控制器112和网关113之间可以进行 通信，安全节点122与控制器121和PGW 123之间可以进行通信，控制器121和PGW 123之间可以进行通信，控制器121和HSS 124之间可以进行通信，控制器121和控制器112之间可以进行通信，本地网关113和安全节点122之间可以进行通信。如同1B所示，实线部分为该从网的用户面，而虚线部分为该从网的控制面。
如图1C所示，在实际应用中，上述控制器102和控制器121可以包括：存储器131、处理器132、通信接口133和总线134。通信接口133和存储器131分别通过总线134与处理器132连接。
其中，存储器131可以包括易失性存储器(英文：Volatile Memory)，例如随机存取存储器(英文：Random-access Memory，缩写：RAM)；存储器131也可以包括非易失性存储器(英文：Non-volatile Memory)，例如快闪存储器(英文：Flash Memory)，硬盘(英文：Hard Disk Drive，缩写：HDD)或固态硬盘(英文：Solid-state Drive，缩写：SSD)；存储器131还可以包括上述种类的存储器的组合。存储器131可用于存储程序指令，具体的，存储器131可存储操作系统1311和至少一个功能所需的应用程序1312。
处理器132可以是中央处理器(英文：Central Processing Unit，缩写：CPU)，网络处理器(英文：Network Processor，缩写：NP)或者CPU和NP的组合。处理器132可以包括一个或者一个以上处理核心，处理器132通过运行存储器131存储的程序指令以执行控制器所能执行的步骤。
通信接口133可以为有线通信接入口，无线通信接口或其组合，其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为无线局域网接口，蜂窝网络通信接口或其组合等。
总线134可以是外设部件互连标准(Peripheral Component Interconnect，简称：PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称：EISA)总线等。总线134可以分为地址总线、数据总线、控制总线等。
如图1D所示，在实际应用中，上述PGW 104和PGW 123可以包括：存 储器141、处理器142、通信接口143和总线144。通信接口143和存储器141分别通过总线144与处理器142连接。
其中，存储器141可以包括易失性存储器，例如RAM；存储器141也可以包括非易失性存储器，例如快闪存储器，HDD或SSD；存储器141还可以包括上述种类的存储器的组合。存储器141可用于存储程序指令，具体的，存储器141可存储操作系统1411和至少一个功能所需的应用程序1412。
处理器142可以是CPU，NP或者CPU和NP的组合。处理器142可以包括一个或者一个以上处理核心，处理器142通过运行存储器141存储的程序指令以执行PGW所能执行的步骤。
通信接口143可以为有线通信接入口，无线通信接口或其组合，其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为无线局域网接口，蜂窝网络通信接口或其组合等。
总线144可以是PCI总线或EISA总线等。总线144可以分为地址总线、数据总线、控制总线等。
图2A是根据一示例性实施例示出的一种网络切换方法的流程图，如图2A所示，该网络切换方法可以应用于如图1A和1B所示的网络架构中，该方法包括以下步骤：
步骤201、终端向主网中的第二控制器发送服务请求。
在实际应用中，终端可以在接收到主网中接入设备101的寻呼请求后向主网中的第二控制器发送服务请求，其中，上述第二控制器可以为上文所述的控制器102。此外，终端还可以在检测到指定操作后向该第二控制器发送服务请求，其中，指定操作指的是需要通过主网传输数据的操作，例如，该指定操作可以为浏览网络页面的操作等，本发明对此不作具体限定。
步骤202、第二控制器接收终端发送的服务请求。
步骤203、第二控制器判断终端是否同时接入主网和从网中，若是，则执 行步骤204，若不是，则退出流程。
第二控制器可以在接收到上述服务请求后判断终端是否同时接入主网和从网中，实际应用中，第二控制器可以通过多种方式执行上述步骤203，具体地：
第一种方式，上述服务请求可以携带宏网转换信息或从网中的第一控制器的标识，其中，宏网转换信息用于指示终端同时接入主网和从网中。在这种情况下，第二控制器可以在接收到宏网转换信息或第一控制器的标识时，确定终端同时接入主网和从网中，反之，则第二控制器确定终端没有同时接入主网和从网中。需要说明的是，上述第一控制器可以为上文所述的控制器121。
第二种方式，上述服务请求携带还可以携带终端的标识或者终端的连接的标识，而且上述第一控制器和第二控制器可以为不同的控制器。在这种情况下，第二控制器可以向第一控制器发送终端连接状态查询请求，该终端连接状态查询请求携带终端的标识或者连接的标识；第一控制器接收到该终端连接状态查询请求后，在本地的终端连接状态数据库中查询终端与从网的连接状态，该连接状态包括已连接和未连接中的一种；第一控制器向第二控制器发送该连接状态；第二控制器接收第一控制器发送的终端与从网的连接状态，若该连接状态为已连接，则第二控制器确定终端同时接入主网和从网中，反之，第二控制器确定终端没有同时接入主网和从网中。
第三种方式，上述服务请求同样可以携带终端的标识或者终端的连接的标识，但是，上述第一控制器和第二控制器为同一控制器。在这种情况下，第二控制器可以基于终端的标识或者连接的标识在第二控制器的终端连接状态数据库中查询终端与从网的连接状态，当连接状态为已连接时，第二控制器确定终端同时接入主网和从网中，反之，第二控制器确定终端没有同时接入主网和从网中。
步骤204、第二控制器指示从网中的第一控制器断开终端与从网的连接。
在实际应用中，根据第一控制器和第二控制器是否为同一控制器，第二控 制器指示第一控制器断开终端与从网的连接的方式可以分为以下两种：
第一种，第二控制器和第一控制器为不同的控制器，则第二控制器指示第一控制器断开终端与从网的连接可以包括：第二控制器向第一控制器发送断开连接请求，该断开连接请求携带终端的标识或者终端的连接的标识；第一控制器接收到第二控制器发送的断开连接请求后，基于该断开连接请求断开终端与从网的连接。
第二种，第二控制器和第一控制器为同一控制器，则第二控制器指示第一控制器断开终端与从网的连接可以包括：第一控制器在接收到终端发送的服务请求，并确定终端同时接入从网和主网中后，断开终端与从网连接。
步骤205、第一控制器基于第二控制器的指示断开终端与从网的连接。
在实际应用中，无论第一控制器和第二控制器是否为同一控制器，第一控制器都可以通过执行下述步骤以完成断开终端与从网连接的操作。具体地，根据安全节点与PGW是否存在控制面信令传输通道，第一控制器断开终端与从网的连接的方式可以分为以下两种，需要说明的是，上述PGW可以为上文所述的PGW 123，上述安全节点可以为上文所述的安全节点122。
第一种方式，如图2B所示，当安全节点与PGW不存在控制面信令传输通道时，本发明实施例可以通过以下步骤断开终端与从网的连接：
步骤21、第一控制器删除第一控制器中与终端的标识或者终端的连接的标识对应的从网的连接上下文(英文：Context)。
简而言之，第一控制器可以删除本地中终端的连接数据，而该连接数据与终端的标识或者终端的连接标识相对应。
步骤22、第一控制器向安全节点发送第一连接删除请求，第一连接删除请求携带终端的标识或者连接的标识。
步骤23、安全节点接收到该第一连接删除请求后，删除安全节点中终端的标识或者连接的标识对应的连接上下文。
步骤24、第一控制器向PGW发送第二连接删除请求，第二连接删除请求 携带终端的标识或者连接的标识。
步骤25、PGW接收到该第二连接删除请求后，删除PGW中终端的标识或者连接的标识对应的连接上下文。
需要说明的是，在实际应用中，本发明实施例可以以任意顺序执行上述步骤21至25，本发明对此不作具体限定。
第二种方式，如图2C所示，当安全节点与PGW存在控制面信令传输通道时，第一控制器可以通过以下步骤断开终端与从网的连接：
步骤31、第一控制器删除第一控制器中与终端的标识或者终端的连接的标识对应的从网的连接上下文。
步骤32、第一控制器向安全节点发送第三连接删除请求，第三连接删除请求携带终端的标识或者连接的标识。
步骤33、安全节点接收到第三连接删除请求后，删除安全节点中终端的标识或者连接的标识对应的连接上下文。
步骤34、安全节点向PGW发送第四连接删除请求，第四连接删除请求携带终端的标识或者连接的标识。
步骤35、PGW接收到该第四连接删除请求后，删除PGW中终端的标识或者连接的标识对应的连接上下文。
需要说明的是，在实际应用中，本发明实施例可以以任意顺序执行上述步骤31至35，本发明对此不作具体限定。
此外，在实际应用中，若终端是通过本地网络接入从网中时，为了断开终端与从网的连接，第一控制器除了执行上述21至25或者31至35的步骤以外，还需要执行下述步骤41至42，如图2D所示：
步骤41、第一控制器向本地网络的控制器发送第五连接删除请求，第五连接删除请求携带终端的标识或者连接的标识。
需要说明的是，上述本地网络的控制器可以为上文所述的控制器112。
步骤42、本地网络的控制器接收到该第五连接删除请求后，删除该控制器 中终端的标识或者连接的标识对应的连接上下文，并控制本地网络的网关、本地网络的基站和终端中的至少一个删除自身中终端的标识或者连接的标识对应的连接上下文。
需要说明的是，上述本地网络的网关可以为上文所述的网关113，上述本地网络的基站可以为上文所述的接入设备111。
步骤206、在终端与从网的连接断开后，第一控制器指示第二控制器将终端在主网中的状态由空闲态切换至连接态。
与步骤204中的说明对应的，当第二控制器和第一控制器为不同的控制器时，步骤206具体可以包括：在终端与从网断开连接后，第一控制器向第二控制器发送断开连接回执；第二控制器接收到断开连接回执后，将终端在主网中的状态由空闲态切换至连接态。
在上述这种情况下，本发明实施例可以通过执行下述步骤以完成第一控制器向第二控制器发送断开连接回执的操作。具体地，根据安全节点与PGW是否存在控制面信令传输通道，第一控制器向第二控制器发送断开连接回执的方式可以分为以下两种：
第一种方式，如图2E所示，当安全节点与PGW不存在控制面信令传输通道时，本发明实施例可以通过以下步骤完成第一控制器向第二控制器发送断开连接回执的操作：
步骤51、安全节点基于第一连接删除请求向第一控制器发送第一连接删除回执，该第一连接删除回执用于指示安全节点删除了终端的标识或者连接的标识对应的连接上下文。
步骤52、PGW基于第二连接删除请求向第一控制器发送第二连接删除回执，该第二连接删除回执用于指示PGW删除了终端的标识或者连接的标识对应的连接上下文。
步骤53、第一控制器在接收到第一连接删除回执和第二连接删除回执后，向第二控制器发送断开连接回执。
第二种方式，如图2F所示，当安全节点与PGW存在控制面信令传输通道时，本发明实施例可以通过以下步骤完成第一控制器向第二控制器发送断开连接回执的操作：
步骤61、PGW基于第四连接删除请求向安全节点发送第四连接删除回执，第四连接删除回执用于指示PGW删除了终端的标识或者连接的标识对应的连接上下文。
步骤62、安全节点基于第三连接删除请求向第一控制器发送第三连接删除回执，第三连接删除回执用于指示安全节点和PGW删除了终端的标识或者连接的标识对应的连接上下文。
步骤63、第一控制器在接收到第三连接删除回执后，向第二控制器发送断开连接回执。
此外，在实际应用中，若终端是通过本地网络接入从网中时，为了完成第一控制器向第二控制器发送断开连接回执的操作，本发明实施例除了执行上述51至53或者61至63的步骤以外，还需要执行下述步骤：第一控制器接收本地网络中的控制器基于第五连接删除请求发送的第五连接删除回执，第五连接删除回执用于指示本地网络的网关、本地网络的基站、终端中的至少一个和控制器删除了终端的标识或者连接的标识对应的连接上下文。
在这种情况下，步骤53或步骤63中，第一控制器只有在接收到第一连接删除回执、第二连接删除回执和第五连接删除回执，或者，只有在接收到第三连接删除回执和第五连接删除回执后，才可以向第二控制器发送断开连接回执。
当然，在实际应用中，第一控制器和第二控制器可以为同一控制器，在这种情况下，第二控制器可以与上述第一控制器同理地接收安全节点、PGW和本地网络的控制器发送的连接删除回执，此时，第二控制器可以在接收到第一连接删除回执、第二连接删除回执和第五连接删除回执，或者，可以在接收到第三连接删除回执和第五连接删除回执后，或者，可以在接收到第一连接删除 回执和第二连接删除回执后，或者，可以在接收到第三连接删除回执后，将终端在主网中的状态由空闲态切换至连接态。
在实际应用中，无论第一控制器和第二控制器是否为同一控制器，第二控制器都可以通过以下方式完成将终端在主网中的状态由空闲态切换至连接态的操作：第二控制器通过主网的基站与终端建立空口连接；第二控制器向主网中的PGW发送修改承载请求，以使该PGW获取主网的基站的标识。PGW在获取上述主网的基站标识后，可以在向终端下发数据时，通过上述主网的基站下发数据。
需要说明的是，上述主网的基站可以为上文所述的接入设备101，主网中的PGW可以为上文所述的PGW 104。
综上，本实施例提供的网络切换方法，通过在网络切换过程中，由从网中的第一控制器断开终端与从网的连接，并在终端与从网的连接断开后，由主网中的第二控制器在该第一控制器的指示下将该终端在主网中的状态由空闲态切换至连接态。从而使得终端只需要向第二控制器发送服务请求即可完成网络切换，而不需要终端先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
图3A是根据一示例性实施例示出的一种网络切换方法的流程图，如图3A所示，该网络切换方法可以应用于如图1A和1B所示的网络架构中，该方法包括以下步骤：
步骤301、终端向主网中的第二控制器发送服务请求。
在实际应用中，终端可以在接收到主网中接入设备101的寻呼请求后向主网中的第二控制器发送服务请求，其中，上述第二控制器可以为上文所述的控 制器102。此外，终端还可以在检测到指定操作后向该第二控制器发送服务请求，其中，指定操作指的是需要通过主网传输数据的操作，例如，该指定操作可以为浏览网络页面的操作等，本发明对此不作具体限定。
需要说明的是，上述服务请求可以携带终端的标识、终端的连接的标识，或者宏网转换信息，该宏网转换信息用于指示终端同时接入主网和从网中。
步骤302、第二控制器接收到该服务请求后通过主网的基站与终端建立空口连接。
步骤303、第二控制器向PGW发送修改承载请求，以使PGW获取上述主网的基站的标识，该修改承载请求携带终端的标识或者终端的连接的标识。
需要说明的是，经过步骤302和303之后，终端在主网中的状态已经从空闲态切换至连接态，但是由于此时终端与从网的连接还未断开，因此，终端还无法通过主网传输数据，只有在终端与从网的连接断开后，终端才可以通过主网进行数据传输。
还需要说明的是，上述主网中的第二控制器可以为上文所述的控制器102，上述主网的基站可以为上文所述的接入设备101，上述PGW可以同时接入主网和从网中，也即是，上文所述的PGW 104和PGW 123可以为同一设备，也即是步骤301中的PGW。
步骤304、PGW接收修改承载请求。
步骤305、PGW在接收到该修改承载请求并确定终端同时接入主网和从网中后，断开终端与从网的连接。
在实际应用中，PGW可以通过以下两种方式确定终端同时接入主网和从网中，具体地：
第一种方式，该修改承载请求还可以携带宏网转换信息或第一控制器的标识，第一控制器为从网中的控制器，也即是上文所述的控制器121。在这种情况下，当PGW接收到宏网转换信息或者第一控制器的标识时，即可确定终端同时接入主网和从网中。
需要说明的是，在实际应用中，若第二控制器接收到的服务请求中携带宏网转换信息，则第二控制器向PGW发送的修改承载请求中可以携带该宏网转换信息。然而，若第二控制器接收到的服务请求中不包含宏网转换信息，则第二控制器可以基于服务请求中携带的终端的标识或者终端的连接的标识在本地的终端连接状态数据库中查询终端与从网的连接状态，若终端与从网的连接状态为已连接，则第二控制器可以确定终端同时接入主网和从网中。此时，第二控制器可以生成宏网转换信息，并在其向PGW发送的修改承载请求中携带该宏网转换信息。
第二种方式，PGW基于终端的标识或者终端的连接的标识在本地的终端连接状态数据库中查询终端与从网的连接状态，当连接状态为已连接时，PGW即可确定终端同时接入主网和从网中。
实际应用中，PGW接收到的修改承载请求中可以不包括该宏网转换信息，则PGW可以基于修改承载请求中的终端的标识或者终端的连接的标识自行查询终端与从网的连接状态，从而确定终端是否同时接入主网和从网中。
此外，在实际应用中，PGW可以通过以下两种方式断开终端与从网的连接，具体地：
第一种方式，如图3B所示，本发明实施例可以通过以下步骤断开终端与从网的连接：
步骤71、PGW删除自身中与终端的标识或者连接的标识对应的从网的连接上下文。
步骤72、PGW向第一控制器发送第一断开连接请求，第一断开连接请求携带终端的标识或者连接的标识。
步骤73、第一控制器接收到第一断开连接请求后，删除本地中与终端的标识或者连接的标识对应的连接上下文。
步骤74、第一控制器向安全节点发送第三断开连接请求，该第三断开连接请求携带终端的标识或者连接的标识。
步骤75、安全节点接收到该第三断开连接请求后，删除本地中与终端的标识或者连接的标识对应的连接上下文。
步骤76、第一控制器向本地网络的控制器发送第四断开连接请求，该第四断开连接请求携带终端的标识或者连接的标识。
步骤77、本地网络的控制器接收到第四断开连接请求后，删除本地中与终端的标识或者连接的标识对应的连接上下文，并控制本地网络的网关、本地网络的基站和终端中的至少一个删除终端的标识或者连接的标识对应的连接上下文。
第二种方式，如图3C所示，本发明实施例可以通过以下步骤断开终端与从网的连接：
步骤81、PGW删除自身中与终端的标识对应的从网的连接上下文；
步骤82、PGW向安全节点发送第二断开连接请求，第二断开连接请求携带终端的标识或者连接的标识。
步骤83、安全节点在接收到该第二断开连接请求后，删除本地中与终端的标识或者连接的标识对应的连接上下文。
步骤84、安全节点向第一控制器发送第五断开连接请求，该第五断开连接请求携带终端的标识或者连接的标识。
步骤85、第一控制器接收到第五断开连接请求后，删除本地中与终端的标识或者连接的标识对应的连接上下文。
步骤86、第一控制器向本地网络的控制器发送第六断开连接请求，该第六断开连接请求携带终端的标识或者连接的标识。
步骤87、本地网络的控制器接收到该第六断开连接请求后，删除本地中与终端的标识或者连接的标识对应的连接上下文，并控制本地网络的网关、本地网络的基站和终端中的至少一个删除终端的标识或者连接的标识对应的连接上下文。
需要说明的是，该安全节点可以为上文所述的安全节点122，本地网络的 控制器可以为上文所述的控制器112，本地网络的网关可以为上文所述的网关113，本地网络的基站可以为上文所述的接入设备111。
还需要说明的是，在实际应用中，上述第一控制器和第二控制器可以为同一控制器，也可以为不同的控制器，本发明对此不做具体限定。
综上所示，本实施例提供的网络切换方法，在网络切换过程中，PGW可以接收主网中的第二控制器发送的修改承载请求，该修改承载请求表明终端在主网中的状态已经切换至连接态，此时，PGW可以在确定终端同时接入主网和从网中时，断开终端与从网的连接，而后终端即可通过主网进行数据传输。从而使得终端不需要先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，而在主网中的状态切换至连接态时即可断开与从网的连接，也即是即可完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
图4是根据一示例性实施例示出的一种控制器400的框图。该控制器400为从网中的控制器。参照图4，该控制器400包括断开模块401和指示模块402。
该断开模块401，用于执行上述步骤205中第一控制器执行的操作。
该指示模块402，用于执行上述步骤206中第一控制器执行的操作。
综上所述，本实施例提供的控制器，通过在网络切换过程中，断开终端与从网的连接，并在终端与从网的连接断开后，指示主网中的第二控制器将该终端在主网中的状态由空闲态切换至连接态。从而使得终端只需要向第二控制器发送服务请求即可完成网络切换，而不需要终端先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成 网络切换，从而节约了信令及网络资源。
图5是根据一示例性实施例示出的一种控制器500的框图。该控制器500为主网中的控制器。参照图5，该控制器500包括接收模块501、指示模块502和切换模块503。
该接收模块501，用于执行上述步骤202的操作。
该指示模块502，用于执行上述步骤203和204中第二控制器执行的操作。
该切换模块503，用于执行上述步骤206中第二控制器执行的操作。
综上所述，本实施例提供的控制器，通过在网络切换过程中，指示第一控制器断开终端与从网的连接，并在终端与从网的连接断开后，在第一控制器的指示下将该终端在主网中的状态由空闲态切换至连接态。从而使得终端只需要向第二控制器发送服务请求即可完成网络切换，而不需要终端先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
图6是根据一示例性实施例示出的一种PGW 600的框图。该PGW 600同时接入主网和从网中。参照图6，该PGW 600包括接收模块601和断开模块602。
该接收模块601，用于执行上述步骤304中PGW的操作。
该断开模块602，用于执行上述步骤305中PGW的操作。
综上所述，本实施例提供的PGW，在网络切换过程中，可以接收主网中的第二控制器发送的修改承载请求，该修改承载请求表明终端在主网中的状态已经切换至连接态，此时，PGW可以在确定终端同时接入主网和从网中时，断开终端与从网的连接，而后终端即可通过主网进行数据传输。从而使得终端 不需要先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，而在主网中的状态切换至连接态时即可断开与从网的连接，也即是即可完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
图7是根据一示例性实施例示出的一种网络切换系统700的框图。该网络切换系统700包括第一控制器701和第二控制器702。
该第一控制器701，用于执行图2A所示实施例中第一控制器执行的操作。
该第二控制器702，用于执行图2A所示实施例中第二控制器执行的操作。
在实际应用中，该网络切换系统700还可以包括安全节点、PGW、本地网络控制器、本地网络的网关、本地网络的基站及终端中的一个或多个，本发明对此不做具体限定。
综上所述，本实施例提供的网络切换系统，通过在网络切换过程中，由从网中的第一控制器断开终端与从网的连接，并在终端与从网的连接断开后，由主网中的第二控制器在该第一控制器的指示下将该终端在主网中的状态由空闲态切换至连接态。从而使得终端只需要向第二控制器发送服务请求即可完成网络切换，而不需要终端先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
图8是根据一示例性实施例示出的一种网络切换系统800的框图。该网络切换系统800包括第二控制器801和PGW 802。
该第二控制器801，用于执行图3A所示实施例中第二控制器执行的操作。
该PGW 802，用于执行图3A所示实施例中PGW执行的操作。
在实际应用中，该网络切换系统800还可以包括安全节点、第一控制器、本地网络控制器、本地网络的网关、本地网络的基站及终端中的一个或多个，本发明对此不做具体限定。
综上所述，本实施例提供的网络切换系统，在网络切换过程中，PGW可以接收主网中的第二控制器发送的修改承载请求，该修改承载请求表明终端在主网中的状态已经切换至连接态，此时，PGW可以在确定终端同时接入主网和从网中时，断开终端与从网的连接，而后终端即可通过主网进行数据传输。从而使得终端不需要先向第一控制器发送断开与从网的连接请求，而后向该第二控制器请求将自身在主网中的状态由空闲态切换至连接态才能完成网络切换，而在主网中的状态切换至连接态时即可断开与从网的连接，也即是即可完成网络切换，这样一方面避免了由于终端行为的不确定性导致的网络切换成功率较低的问题，另一方面，终端只需要经过一套流程即可完成网络切换，从而节约了信令及网络资源。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (30)

  1. 一种网络切换方法，其特征在于，用于网络切换系统中的第一控制器中，所述网络切换系统包括：主网和从网，所述第一控制器为所述从网中的控制器，所述方法包括：
    在第二控制器接收到终端发送的服务请求，并确定所述终端同时接入所述主网和所述从网中后，所述第一控制器断开所述终端与所述从网的连接，所述第二控制器为所述主网中的控制器；
    所述第一控制器令所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态。
  2. 根据权利要求1所述的方法，其特征在于，所述第一控制器断开所述终端与所述从网的连接，包括：
    所述第一控制器接收所述第二控制器发送的断开连接请求，所述断开连接请求为所述第二控制器在接收到所述服务请求，并确定所述终端同时接入所述主网和所述从网中后发送的，所述断开连接请求携带所述终端的标识或所述终端的连接的标识；
    基于所述断开连接请求，所述第一控制器断开所述终端与所述从网的连接。
  3. 根据权利要求2所述的方法，其特征在于，所述第一控制器令所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态，包括：
    在所述终端与所述从网断开连接后，所述第一控制器向所述第二控制器发送断开连接回执，使得所述第二控制器在接收到所述断开连接回执后，将所述终端在所述主网中的状态由空闲态切换至连接态。
  4. 根据权利要求1所述的方法，其特征在于，所述第一控制器与所述第二 控制器为同一控制器；所述在第二控制器接收到终端发送的服务请求，并确定所述终端同时接入所述主网和所述从网中后，所述第一控制器断开所述终端与所述从网的连接，包括：
    所述第一控制器接收所述终端发送的所述服务请求，并确定所述终端同时接入所述从网和所述主网中后，所述第一控制器断开所述终端与所述从网连接。
  5. 根据权利要求1所述的方法，其特征在于，所述第一控制器断开所述终端与所述从网的连接，包括：
    所述第一控制器删除所述第一控制器中与所述终端的标识或者所述终端的连接的标识对应的所述从网的连接上下文；
    当所述从网中的安全节点与所述从网中的分组数据协议网关不存在控制面信令传输通道时，所述第一控制器向所述安全节点发送第一连接删除请求，所述第一连接删除请求携带所述终端的标识或者所述连接的标识，所述第一连接删除请求用于指示所述安全节点删除所述终端的标识或者所述连接的标识对应的连接上下文；所述第一控制器向所述分组数据协议网关发送第二连接删除请求，所述第二连接删除请求携带所述终端的标识或者所述连接的标识，所述第二连接删除请求用于指示所述分组数据协议网关删除所述终端的标识或者所述连接的标识对应的连接上下文；
    当所述安全节点与所述分组数据协议网关存在控制面信令传输通道时，所述第一控制器向所述安全节点发送第三连接删除请求，所述第三连接删除请求携带所述终端的标识或者所述连接的标识，所述第三连接删除请求用于指示所述安全节点删除所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述安全节点在接收到所述第三连接删除请求后向所述分组数据协议网关发送第四连接删除请求，所述第四连接删除请求携带所述终端的标识或者所述连接的标识，所述第四连接删除请求用于指示所述分组数据协议网关删除所述终端的标识或者所述连接的标识对应的连接上下文；
    当所述终端通过本地网络接入所述从网中时，所述第一控制器向所述本地网络的控制器发送第五连接删除请求，所述第五连接删除请求携带所述终端的标识或者所述连接的标识，所述第五连接删除请求用于指示所述控制器删除所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述控制器控制所述本地网络的网关、所述本地网络的基站和所述终端中的至少一个删除所述终端的标识或者所述连接的标识对应的连接上下文。
  6. 根据权利要求3或5所述的方法，其特征在于，所述在所述终端与所述从网断开连接后，所述第一控制器向所述第二控制器发送断开连接回执，包括：
    当所述安全节点与所述分组数据协议网关不存在控制面信令传输通道时，所述第一控制器接收所述安全节点基于所述第一连接删除请求发送的第一连接删除回执，所述第一连接删除回执用于指示所述安全节点删除了所述终端的标识或者所述连接的标识对应的连接上下文；所述第一控制器接收所述分组数据协议网关基于所述第二连接删除请求发送的第二连接删除回执，所述第二连接删除回执用于指示所述分组数据协议网关删除了所述终端的标识或者所述连接的标识对应的连接上下文；
    当所述安全节点与所述分组数据协议网关存在控制面信令传输通道时，所述第一控制器接收所述安全节点基于所述第三连接删除请求发送的第三连接删除回执，所述第三连接删除回执为所述安全节点在接收到所述分组数据协议网关发送的第四连接删除回执后发送的，所述第四连接删除回执用于指示所述分组数据协议网关删除了所述终端的标识或者所述连接的标识对应的连接上下文，所述第三连接删除回执用于指示所述安全节点和所述分组数据协议网关删除了所述终端的标识或者所述连接的标识对应的连接上下文；
    当所述终端通过所述本地网络接入所述从网中时，所述第一控制器接收所述控制器基于所述第五连接删除请求发送的第五连接删除回执，所述第五连接删除回执用于指示所述本地网络的网关、所述本地网络的基站、所述终端中的 至少一个和所述控制器删除了所述终端的标识或者所述连接的标识对应的连接上下文；
    所述第一控制器在接收到所述第一连接删除回执、所述第二连接删除回执、所述第三连接删除回执和所述第五连接删除回执中的至少一个后，向所述第二控制器发送所述断开连接回执。
  7. 一种网络切换方法，其特征在于，用于网络切换系统中的第二控制器中，所述网络切换系统包括：主网和从网，所述第二控制器为所述主网中的控制器，所述方法包括：
    所述第二控制器接收终端发送的服务请求，所述服务请求为所述终端在接收到所述主网的寻呼请求或者检测到指定操作后发送的，所述指定操作为需要通过所述主网传输数据的操作；
    当接收到所述服务请求并确定所述终端同时接入所述从网和所述主网中后，所述第二控制器令第一控制器断开所述终端与所述从网的连接，所述第一控制器为所述从网中的控制器；
    在所述终端与所述从网断开连接后，所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态。
  8. 根据权利要求7所述的方法，其特征在于，所述服务请求携带所述终端的标识或者所述终端的连接的标识，所述第二控制器令所述第一控制器断开所述终端与所述从网的连接，包括：
    所述第二控制器向所述第一控制器发送断开连接请求，所述断开连接请求携带所述终端的标识或者所述连接的标识，使得所述第一控制器基于所述断开连接请求，断开所述终端与所述从网的连接。
  9. 根据权利要求8所述的方法，其特征在于，所述在所述终端与所述从网 断开连接后，所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态，包括：
    在接收到所述第一控制器发送的断开连接回执后，所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态，所述断开连接回执用于指示所述终端与所述从网已经断开了连接。
  10. 根据权利要求7所述的方法，其特征在于，所述服务请求携带宏网转换信息或所述第一控制器的标识，所述宏网转换信息用于指示所述终端同时接入所述主网和所述从网中；所述当接收到所述服务请求并确定所述终端同时接入从网和所述主网中后，所述第二控制器令所述第一控制器断开所述终端与所述从网的连接，包括：
    当接收到所述宏网转换信息或所述第一控制器的标识时，所述第二控制器令所述第一控制器断开所述终端与所述从网的连接。
  11. 根据权利要求7所述的方法，其特征在于，所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态，包括：
    所述第二控制器通过所述主网的基站与所述终端建立空口连接；
    所述第二控制器向所述主网中的分组数据协议网关发送修改承载请求，以使所述分组数据协议网关获取所述主网的基站的标识。
  12. 一种网络切换方法，其特征在于，用于网络切换系统中的分组数据协议网关中，所述网络切换系统包括：主网和从网，所述分组数据协议网关同时接入所述主网和所述从网中，所述方法包括：
    接收第二控制器发送的修改承载请求，所述修改承载请求携带终端的标识或者所述终端的连接的标识，所述修改承载请求为所述第二控制器在通过所述主网的基站与所述终端建立了空口连接后发送的，所述第二控制器为所述主网 的控制器；
    在接收到所述修改承载请求并确定所述终端同时接入所述主网和所述从网中后，断开所述终端与所述从网的连接。
  13. 根据权利要求12所述的方法，其特征在于，所述断开所述终端与所述从网的连接，包括：
    删除所述分组数据协议网关中与所述终端的标识或者所述连接的标识对应的所述从网的连接上下文；
    向第一控制器发送第一断开连接请求，所述第一断开连接请求携带所述终端的标识或者所述连接的标识，所述第一控制器为所述从网中的控制器，所述第一断开连接请求用于指示所述第一控制器删除所述第一控制器中与所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述第一控制器控制所述网络切换系统中的安全节点、所述从网中本地网络的控制器、本地网络的网关、本地网络的基站和所述终端中的至少一个删除所述终端的标识或者所述连接的标识对应的连接上下文。
  14. 根据权利要求12所述的方法，其特征在于，所述断开所述终端与所述从网的连接，包括：
    删除所述分组数据协议网关中与所述终端的标识对应的所述从网的连接上下文；
    向所述网络切换系统中的安全节点发送第二断开连接请求，所述第二断开连接请求携带所述终端的标识或者所述连接的标识，所述第二断开连接请求用于指示所述安全节点删除所述安全节点中与所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述安全节点控制第一控制器、所述从网中本地网络的控制器、本地网络的网关、本地网络的基站和所述终端中的至少一个删除所述终端的标识或者所述连接的标识对应的连接上下文，所述第一控制 器为所述从网中的控制器。
  15. 根据权利要求12所述的方法，其特征在于，所述修改承载请求还携带宏网转换信息或第一控制器的标识，所述宏网转换信息用于指示所述终端同时接入所述主网和所述从网中，所述第一控制器为所述从网中的控制器；所述在接收到所述修改承载请求并确定所述终端同时接入所述主网和所述从网中后，断开所述终端与所述从网的连接，包括：
    当接收到所述宏网转换信息或者所述第一控制器的标识时，断开所述终端与所述从网的连接。
  16. 一种控制器，其特征在于，所述控制器为网络切换系统中从网中的控制器，所述网络切换系统包括：主网和所述从网，所述控制器包括：
    断开模块，用于在第二控制器接收到终端发送的服务请求，并确定所述终端同时接入所述主网和所述从网中后，断开所述终端与所述从网的连接，所述第二控制器为所述主网中的控制器；
    指示模块，用于指示所述第二控制器将所述终端在所述主网中的状态由空闲态切换至连接态。
  17. 根据权利要求16所述的控制器，其特征在于，所述断开模块用于：
    接收所述第二控制器发送的断开连接请求，所述断开连接请求为所述第二控制器在接收到所述服务请求，并确定所述终端同时接入所述主网和所述从网中后发送的，所述断开连接请求携带所述终端的标识或所述终端的连接的标识；
    基于所述断开连接请求，断开所述终端与所述从网的连接。
  18. 根据权利要求17所述的控制器，其特征在于，所述指示模块用于：
    在所述终端与所述从网断开连接后，向所述第二控制器发送断开连接回执，使得所述第二控制器在接收到所述断开连接回执后，将所述终端在所述主网中 的状态由空闲态切换至连接态。
  19. 根据权利要求16所述的控制器，其特征在于，所述控制器与所述第二控制器为同一控制器；所述断开模块用于：
    接收所述终端发送的所述服务请求，并确定所述终端同时接入所述从网和所述主网中后，断开所述终端与所述从网连接。
  20. 根据权利要求16所述的控制器，其特征在于，所述断开模块用于：
    删除所述控制器中与所述终端的标识或者所述终端的连接的标识对应的所述从网的连接上下文；
    当所述从网中的安全节点与所述从网中的分组数据协议网关不存在控制面信令传输通道时，向所述安全节点发送第一连接删除请求，所述第一连接删除请求携带所述终端的标识或者所述连接的标识，所述第一连接删除请求用于指示所述安全节点删除所述终端的标识或者所述连接的标识对应的连接上下文；向所述分组数据协议网关发送第二连接删除请求，所述第二连接删除请求携带所述终端的标识或者所述连接的标识，所述第二连接删除请求用于指示所述分组数据协议网关删除所述终端的标识或者所述连接的标识对应的连接上下文；
    当所述安全节点与所述分组数据协议网关存在控制面信令传输通道时，向所述安全节点发送第三连接删除请求，所述第三连接删除请求携带所述终端的标识或者所述连接的标识，所述第三连接删除请求用于指示所述安全节点删除所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述安全节点在接收到所述第三连接删除请求后向所述分组数据协议网关发送第四连接删除请求，所述第四连接删除请求携带所述终端的标识或者所述连接的标识，所述第四连接删除请求用于指示所述分组数据协议网关删除所述终端的标识或者所述连接的标识对应的连接上下文；
    当所述终端通过本地网络接入所述从网中时，向所述本地网络的控制器发 送第五连接删除请求，所述第五连接删除请求携带所述终端的标识或者所述连接的标识，所述第五连接删除请求用于指示所述控制器删除所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述控制器控制所述本地网络的网关、所述本地网络的基站和所述终端中的至少一个删除所述终端的标识或者所述连接的标识对应的连接上下文。
  21. 根据权利要求18或20所述的控制器，其特征在于，所述指示模块用于：
    当所述安全节点与所述分组数据协议网关不存在控制面信令传输通道时，接收所述安全节点基于所述第一连接删除请求发送的第一连接删除回执，所述第一连接删除回执用于指示所述安全节点删除了所述终端的标识或者所述连接的标识对应的连接上下文；接收所述分组数据协议网关基于所述第二连接删除请求发送的第二连接删除回执，所述第二连接删除回执用于指示所述分组数据协议网关删除了所述终端的标识或者所述连接的标识对应的连接上下文；
    当所述安全节点与所述分组数据协议网关存在控制面信令传输通道时，接收所述安全节点基于所述第三连接删除请求发送的第三连接删除回执，所述第三连接删除回执为所述安全节点在接收到所述分组数据协议网关发送的第四连接删除回执后发送的，所述第四连接删除回执用于指示所述分组数据协议网关删除了所述终端的标识或者所述连接的标识对应的连接上下文，所述第三连接删除回执用于指示所述安全节点和所述分组数据协议网关删除了所述终端的标识或者所述连接的标识对应的连接上下文；
    当所述终端通过所述本地网络接入所述从网中时，接收所述控制器基于所述第五连接删除请求发送的第五连接删除回执，所述第五连接删除回执用于指示所述本地网络的网关、所述本地网络的基站、所述终端中的至少一个和所述控制器删除了所述终端的标识或者所述连接的标识对应的连接上下文；
    在接收到所述第一连接删除回执、所述第二连接删除回执、所述第三连接 删除回执和所述第五连接删除回执中的至少一个后，向所述第二控制器发送所述断开连接回执。
  22. 一种控制器，其特征在于，所述控制器为网络切换系统中主网中的控制器，所述网络切换系统包括：所述主网和从网，所述控制器包括：
    接收模块，用于接收终端发送的服务请求，所述服务请求为所述终端在接收到所述主网的寻呼请求或者检测到指定操作后发送的，所述指定操作为需要通过所述主网传输数据的操作；
    指示模块，用于当接收到所述服务请求并确定所述终端同时接入所述从网和所述主网中后，指示第一控制器断开所述终端与所述从网的连接，所述第一控制器为所述从网中的控制器；
    切换模块，用于在所述终端与所述从网断开连接后，将所述终端在所述主网中的状态由空闲态切换至连接态。
  23. 根据权利要求22所述的控制器，其特征在于，所述服务请求携带所述终端的标识或者所述终端的连接的标识，所述指示模块用于：
    向所述第一控制器发送断开连接请求，所述断开连接请求携带所述终端的标识或者所述连接的标识，使得所述第一控制器基于所述断开连接请求，断开所述终端与所述从网的连接。
  24. 根据权利要求23所述的控制器，其特征在于，所述切换模块用于：
    在接收到所述第一控制器发送的断开连接回执后，将所述终端在所述主网中的状态由空闲态切换至连接态，所述断开连接回执用于指示所述终端与所述从网已经断开了连接。
  25. 根据权利要求22所述的控制器，其特征在于，所述服务请求携带宏网转换信息或所述第一控制器的标识，所述宏网转换信息用于指示所述终端同时 接入所述主网和所述从网中；所述指示模块用于：
    当接收到所述宏网转换信息或所述第一控制器的标识时，指示所述第一控制器断开所述终端与所述从网的连接。
  26. 根据权利要求22所述的控制器，其特征在于，所述切换模块用于：
    通过所述主网的基站与所述终端建立空口连接；
    向所述主网中的分组数据协议网关发送修改承载请求，以使所述分组数据协议网关获取所述主网的基站的标识。
  27. 一种分组数据协议网关，其特征在于，所述分组数据协议网关同时接入网络切换系统中的主网和从网中，所述分组数据协议网关包括：
    接收模块，用于接收第二控制器发送的修改承载请求，所述修改承载请求携带终端的标识或者所述终端的连接的标识，所述修改承载请求为所述第二控制器在通过所述主网的基站与所述终端建立了空口连接后发送的，所述第二控制器为所述主网的控制器；
    断开模块，用于在接收到所述修改承载请求并确定所述终端同时接入所述主网和所述从网中后，断开所述终端与所述从网的连接。
  28. 根据权利要求27所述的分组数据协议网关，其特征在于，所述断开模块用于：
    删除所述分组数据协议网关中与所述终端的标识或者所述连接的标识对应的所述从网的连接上下文；
    向第一控制器发送第一断开连接请求，所述第一断开连接请求携带所述终端的标识或者所述连接的标识，所述第一控制器为所述从网中的控制器，所述第一断开连接请求用于指示所述第一控制器删除所述第一控制器中与所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述第一控制器控 制所述网络切换系统中的安全节点、所述从网中本地网络的控制器、本地网络的网关、本地网络的基站和所述终端中的至少一个删除所述终端的标识或者所述连接的标识对应的连接上下文。
  29. 根据权利要求27所述的分组数据协议网关，其特征在于，所述断开模块用于：
    删除所述分组数据协议网关中与所述终端的标识对应的所述从网的连接上下文；
    向所述网络切换系统中的安全节点发送第二断开连接请求，所述第二断开连接请求携带所述终端的标识或者所述连接的标识，所述第二断开连接请求用于指示所述安全节点删除所述安全节点中与所述终端的标识或者所述连接的标识对应的连接上下文，并用于指示所述安全节点控制第一控制器、所述从网中本地网络的控制器、本地网络的网关、本地网络的基站和所述终端中的至少一个删除所述终端的标识或者所述连接的标识对应的连接上下文，所述第一控制器为所述从网中的控制器。
  30. 根据权利要求27所述的分组数据协议网关，其特征在于，所述修改承载请求还携带宏网转换信息或第一控制器的标识，所述宏网转换信息用于指示所述终端同时接入所述主网和所述从网中，所述第一控制器为所述从网中的控制器；所述断开模块用于：
    当接收到所述宏网转换信息或者所述第一控制器的标识时，断开所述终端与所述从网的连接。
PCT/CN2016/102709 2016-10-20 2016-10-20 网络切换方法、控制器、网关及系统 WO2018072174A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/102709 WO2018072174A1 (zh) 2016-10-20 2016-10-20 网络切换方法、控制器、网关及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/102709 WO2018072174A1 (zh) 2016-10-20 2016-10-20 网络切换方法、控制器、网关及系统

Publications (1)

Publication Number Publication Date
WO2018072174A1 true WO2018072174A1 (zh) 2018-04-26

Family

ID=62018057

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/102709 WO2018072174A1 (zh) 2016-10-20 2016-10-20 网络切换方法、控制器、网关及系统

Country Status (1)

Country Link
WO (1) WO2018072174A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102883384A (zh) * 2011-07-15 2013-01-16 华为技术有限公司 用于改变接入小区的方法、用户设备和基站
CN103477684A (zh) * 2011-04-01 2013-12-25 Lg电子株式会社 在支持多无线电接入技术的无线电接入系统中收发数据的方法及装置
CN105144833A (zh) * 2013-04-23 2015-12-09 Lg电子株式会社 在无线通信系统中发送停用指示的方法和设备
WO2016006936A1 (en) * 2014-07-08 2016-01-14 Lg Electronics Inc. Method and apparatus for performing access control or membership verification for dual connectivity in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103477684A (zh) * 2011-04-01 2013-12-25 Lg电子株式会社 在支持多无线电接入技术的无线电接入系统中收发数据的方法及装置
CN102883384A (zh) * 2011-07-15 2013-01-16 华为技术有限公司 用于改变接入小区的方法、用户设备和基站
CN105144833A (zh) * 2013-04-23 2015-12-09 Lg电子株式会社 在无线通信系统中发送停用指示的方法和设备
WO2016006936A1 (en) * 2014-07-08 2016-01-14 Lg Electronics Inc. Method and apparatus for performing access control or membership verification for dual connectivity in wireless communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
BROADCOM CORPORATION: "Mobility robustness with dual connectivity", R2-132920 3GPP TSG-RAN WG2 MEETING #83, vol. RAN WG2, 23 August 2013 (2013-08-23), XP050718615 *

Similar Documents

Publication Publication Date Title
KR102394891B1 (ko) 무선 통신 방법 및 장치
JP6910445B2 (ja) 通信方法、アクセスネットワークデバイス、及び端末
BR112020016328A2 (pt) Método de comunicação, aparelho de comunicações, sistema de comunicações e um meio legível por computador
US20190373505A1 (en) Access traffic steering/switching/splitting method in a network and network entity performing the same
WO2018202138A1 (zh) 通信方法及相关设备
TWI641273B (zh) Network slice selection method and related equipment
US20220272607A1 (en) Network Access Method and Communication Apparatus
WO2020173137A1 (zh) 一种数据传输方法、相关设备、程序产品以及存储介质
US10827557B2 (en) Network access control method and apparatus
WO2008113235A1 (fr) Procédé pour éviter la libération erronée de ressources pendant une mise à jour de zone de suivi ou un transfert intercellulaire
WO2016197809A2 (zh) 接入点切换方法及装置
WO2012109823A1 (zh) 一种机器类型通信设备的拥塞控制方法及系统
KR20210010358A (ko) 네트워크에서 up 연결을 비활성화하는 방법 및 네트워크에서 up 연결에 대한 비활성화를 제어하는 네트워크 엔터티
WO2021189235A1 (zh) 一种数据传输方法及装置、通信设备
WO2019076308A1 (zh) 终端设备的状态的确定方法、装置及设备
WO2018170707A1 (zh) 控制面连接管理方法和装置
WO2020034802A1 (zh) 一种激活pdu会话的方法及设备
WO2011097989A1 (zh) 一种本地访问寻呼优化方法及装置
KR102505630B1 (ko) 데이터 전송 방법 및 장치
TWI753926B (zh) 無線通信的方法、裝置、接入網實體和終端設備
WO2014101008A1 (zh) Ptt通信方法、服务器、终端及系统
WO2012126319A1 (zh) 一种本地访问业务的切换方法及系统
WO2013113240A1 (zh) 一种传输rn信息、寻呼ue的方法及装置
KR102316348B1 (ko) 통신 방법, 네트워크 기기 및 단말 기기
WO2018072174A1 (zh) 网络切换方法、控制器、网关及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16919200

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16919200

Country of ref document: EP

Kind code of ref document: A1