WO2012126302A1

WO2012126302A1 - Method and system supporting simultaneous communication for dual-mode, dual-standby terminal

Info

Publication number: WO2012126302A1
Application number: PCT/CN2012/071291
Authority: WO
Inventors: 梁爽; 宗在峰; 卢飞; 朱进国
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-03-18
Filing date: 2012-02-17
Publication date: 2012-09-27
Also published as: CN102685714B; CN102685714A

Abstract

Disclosed are a method and system supporting simultaneous communication for a dual-mode, dual-standby terminal. The method comprises: when a UE is accessing from a first access system, selecting a network element capable of supporting the dual-mode terminal to complete a registration (810); when the UE is accessing from a second access system, a network node within the second access system completing for the UE a load synchronization and bonding (820); and the UE maintaining simultaneously a registered state with the two access systems, thus allowing simultaneously service reception and transmission (830). The method and system of the present invention allow effective support for the dual-mode terminal to access simultaneously different networks, and to simultaneously receive services. The technical solution of the present invention not only allows for data transmission path of increased flexibility on the basis of characteristics of different access technologies, thus allowing reasonable and full utilization of resources, but also prevents the problem of overload on a single access technology causing restricted transmission rate.

Description

Method and system for supporting simultaneous communication of dual mode dual standby terminals

The present invention relates to the field of communications, and in particular, to a method and system for supporting dual mode dual standby (UE) simultaneous communication. Background technique

In the field of mobile communications, EPS (Evolved Packet System) and GPRS (General Packet Radio Service) networks are gradually evolving. The schematic diagram of the EPS system and the interworking between the GPRS system and the EPS system is shown in Figure 1 and Figure 2 (non-roaming architecture;). The EPS mainly includes two parts: E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and EPC (Evolved Packet Core). The EPC of the system can support users' access from GERAN (GSM EDGE radio access network, GSM EDGE radio access network) and UTRAN (Universal Terrestrial Radio Access Network).

In the EPC packet core network, it includes HSS (Home Subscriber Server), MME (Mobility Management Entity), S-GW (SGW, Serving Gateway, Serving Gateway), P-GW ( PGW, PDN Gateway, Packet Data Network Gateway, SGSN (Serving GPRS Support Node) and PCRF (Policy and Charging Enforcement Function) entities, where:

The HSS is the permanent storage location of the user subscription data, and is located in the home network to which the user subscribes. The MME is the location where the user subscription data is stored in the current network, and is responsible for the terminal-to-network NAS layer (Non-Access Stratum, non-access stratum) signaling management. , user tracking in idle mode and Paging management function and bearer management;

The S-GW is a gateway from the core network to the wireless system, and is responsible for user plane loading of the user equipment to the core network, data buffering in the idle mode of the terminal, function of initiating a service request by the network side, legal eavesdropping, and packet data routing and forwarding functions;

The P-GW is the gateway of the EPS and the external network of the system, and is responsible for the functions of IP address allocation, billing function, packet filtering, and policy application of the terminal.

The SGSN is a service support point for GERAN and UTRAN users to access the EPC network. The specific functions are similar to those of the MME. They are responsible for user location update, paging management, and bearer management.

The GPRS Gateway Support Node (GGSN) supports the edge routing function of the GPRS network. That is, the GGSN is responsible for routing and forwarding data of the GPRS network, and protecting the integrity of the GPRS network data through the firewall and filtering functions. The GGSN also has a billing function.

The PGW contains all the functions of the GGSN, and the GGSN can be considered as a sub-function of the PGW and embedded in the PGW. Therefore, the SGSN can connect directly to the PGW and use the Gn/Gp interface.

The HSS/Home Location Register (HLR) is the primary user database that supports invocation/session. Dual-mode or three-mode terminals can access the network through GERAN/UTRAN/EUTRAN, and need to register separately when accessing different networks. In the existing architecture, the process of the terminal accessing from the Long Term Evolution (LTE) system and then accessing the network from the GERAN/UTRAN is as shown in FIG. 3, and the process includes the following steps:

Steps 301 to 302, when the user is powered on, the application attach request initiates an attach process to register in the core network. The non-access stratum message is carried by the base station (eNodeB, eNB) in the initialization user message of the SI interface to the MME.

Step 303: If there is no context information of the user in the network, or the attach request message does not have integrity protection, or the integrity protection fails, the MME in the core network performs the authentication of the user. The right certification process.

Steps 304 to 305, if there is no subscription data of the user in the MME, then an update location request message is sent to the home subscriber server, including information such as mobility management unit identity, user identity, update type, and the like. The user data server sends the subscriber subscription data to the MME in the update location response message, including the subscription APN, and the Quality of Service (QoS) parameters of each APN default bearer.

Steps 306 to 307, in order to support the user to be always online, the MME establishes a default bearer on the core network side between the S-GW and the P-GW by using the QoS parameter of the subscription default bearer. The MME sends a create session request to the PGW through the SGW, which carries related parameters such as QoS parameters and charging characteristics related to the default bearer. The PGW authorizes the requested bearer QoS and sends a create session response to the MME through the SGW.

Step 308: After the default bearer is established on the core network side, the corresponding radio bearer is activated. The MME sends the context of the UE and the established QoS parameter to the base station by using an initial context setup request message, and the attach accept message is also encapsulated in the message. Send it to the user. The attach accept message carries the temporary user identifier assigned by the MME to the UE, and a context request for establishing a bearer for the UE.

Steps 309 to 310: The base station establishes a corresponding air interface bearer according to the bearer information indicated by the core network. Step 311: After the establishment of the air interface bearer is completed, the base station returns an initial context setup response message to the port core network.

Step 312: The UE returns a registration completion message to the MME through the base station.

Step 313, the UE moves to the UTRAN (the GERAN is also applicable, and the process takes the UTRAN as an example). The UE sends a Routing Area Update Request message to the SGSN through the Radio Network Controller (RNC), which carries a valid temporary user identifier.

Step 314: The SGSN finds the MME originally registered by the UE according to the temporary user identifier of the UE, and sends a context request message to the MME. Step 315: The MME checks the UE, and sends the context of the UE to the SGSN after the verification is passed.

Step 316: After receiving the context of the UE, the SGSN returns a context response to the MME.

Steps 317 to 318, if the UE activates the bearer, the SGSN updates the PDP context by sending an Update PDP Context Request to the GGSN (the PGW includes the function of the GGSN). The update PDP context request carries the TEID and IP address of the new SGSN. The GGSN saves the information, returns an update PDP response to the new SGSN, and updates the TEID and IP address of the MME with the TEID and IP address of the SGSN.

Steps 319 to 322, the SGSN sends a location update request to the HSS, where the identifier of the new SGSN is carried, and the HSS will save the identifier. The HSS inserts subscription data into the SGSN.

Step 323: The SGSN confirms that the UE is valid in the current routing area, and sends a routing area update accept message to the UE, where the P-TMSL re-assigned to the UE is carried.

Step 324: The UE returns a routing area update complete message to the SGSN, and confirms that the P-TMSI is valid. The UE will identify the relevant information of the MME as invalid.

Steps 325 to 326, the HSS sends a location cancellation request to the MME, and after the MME returns a response to the HSS, the HSS does not save the identity of the MME.

Steps 325 to 326, the MME sends a delete session request to the SGW. Both the SGW and the MME delete the associated bearer context.

In the early stage of LTE introduction, most of the terminals are multi-mode but single-access terminals because of the interference of the wireless spectrum. This causes the UE to perform services only on one network at a time, or even only in one network. A waste of multiple radio access technologies (RATs) and coverage of regional wireless resources. With the development of technology, the wireless interference problem is no longer an important obstacle to the development of dual-mode terminals. Operators and equipment vendors are studying how to support dual-mode terminals to simultaneously access different networks and receive services at the same time. However, there is no corresponding technical support yet. Summary of the invention

In view of this, the main object of the present invention is to provide a method and system for supporting simultaneous communication of a dual mode dual standby terminal, which supports dual mode terminals simultaneously accessing different networks and receiving services at the same time.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for supporting simultaneous communication of a dual mode dual standby terminal UE includes:

The UE accesses from the first access system, selects a network element capable of supporting the dual mode terminal to complete registration; and the UE accesses from the second access system, and the network node in the second access system completes bearer synchronization and binding for the UE. ;

The UE remains registered in both access systems at the same time so that services can be received and transmitted simultaneously. Among them, the terminal first from the GSM EDGE radio access network GERAN / universal terrestrial radio access network

When the UTRAN is registered, and then registered from the Long Term Evolution (LTE) system, the first access system is GERAN/UTRAN, and the second access system is an LTE system;

The process of the UE accessing the first access system and selecting the network element capable of supporting the dual mode terminal to complete the registration includes:

The UE initiates an attach request to register with the core network; after the authentication and authentication process for the user, the SGSN returns a registration accept message to the UE.

The process in which the UE accesses the second access system, and the network node in the second access system completes bearer synchronization and binding for the UE includes:

The UE initiates an attach/tracking area update TAU procedure to implement registration in the EUTRAN; the mobility management entity MME authenticates the UE and obtains a context, and selects an appropriate serving gateway SGW/packet data network gateway PGW, and The PGW is triggered to perform bearer activation, or the bearer modification process to the PGW is initiated according to the address information of the PGW obtained in the context acquisition process, and the bearer established in the first access system is established or modified in the second access system, and is completed. Bearer binding of two access systems.

After the first access system completes registration, the UE needs to send in the first access system. And the bearer setup process, the method further includes: the UE initiating a PDP context activation process in the first access system.

The first access system is an LTE system, the second access system is a GERAN/UTRAN, and the UE is from the first access system, when the terminal is first registered from the LTE and then registered from the GERAN/UTRAN. Access, the process of selecting a network element capable of supporting a dual-mode terminal to complete registration includes:

The UE attaches the request to register to the core network; after the authentication and authentication process for the user, the MME initiates a session establishment process.

The UE initiates an attach/routing area update RAU request to implement registration in GERAN/UTRAN; the UE sends a RAU request/attach request, and the SGSN performs context acquisition and authentication authentication process for the UE, and initiates a create session/modification bearer. The process of the PGW is also performed to perform the bearer activation, or the bearer modification process to the PGW is initiated according to the address information of the PGW in the context, and the bearer established in the first access system is established or modified in the second access system, and the two are completed. Bearer binding for access systems.

Wherein, the method further comprises:

When the UE accesses the network, it carries an indication of whether to support the simultaneous communication function of the dual mode terminal.

Wherein, the method further comprises:

The TAU request/RAU request/attach request sent by the UE carries an indication that the UE requests to register at the same time in two systems;

The indication is implemented by adding a new information element IE to the request message, or by augmenting the value of an existing IE including a registration/TAU type IE.

Wherein, the method further comprises:

If the UE activates and wants to use the bearer in both access systems, then when the UE accesses from the second When the system is connected, you need to carry the relevant bearer ID.

A mobility management unit including an SGSN or MME performs bearer binding based on the bearer identity.

Wherein, the method further comprises:

The mobility management unit, including the SGSN or the MME, notifies the source SGSN whether the registration, and/or bearer information is valid in the context request message or the context response message in the process of acquiring the context.

A system for supporting dual-mode dual-standby terminal UEs to simultaneously communicate, including a UE, a first access system, and a second access system;

The UE is configured to access from the first access system, select a network element capable of supporting the dual mode terminal to complete registration, and access from the second access system, and simultaneously maintain registration status in the two access systems, so as to enable Accept and send business at the same time;

The second access system is configured to perform bearer synchronization and binding by the network node for the UE. The first access system is GERAN/UTRAN, and the second access system is an LTE system; the UE accesses from the first access when the terminal is first registered from the GERAN/UTRAN and then registered from the LTE system. When the system accesses and selects the NE that can support the dual-mode terminal to complete registration, it is used to:

An attach request is initiated to register with the core network; after the authentication process for the user, the SGSN is triggered to return a registration accept message to the UE.

The UE accesses from the second access system, and when the network node in the second access system completes bearer synchronization and binding for the UE,

The UE is configured to initiate an attach/TAU request to implement registration in the EUTRAN; trigger the MME to perform authentication authentication on the UE and perform context acquisition, select an appropriate PGW and trigger the PGW to perform bearer activation, or acquire the PGW according to the context. The address information initiates a bearer modification process to the PGW, and the bearer already established in the first access system is in the second access system. Establish bearer or modification, and complete bearer binding of two access systems.

After the first access system completes the registration, the UE is further configured to initiate a bearer setup process in the first access system: initiate a PDP context activation process in the first access system.

The first access system is an LTE system, the second access system is a GERAN/UTRAN, and the UE is from the first access system, when the terminal is first registered from the LTE and then registered from the GERAN/UTRAN. Access, when selecting an NE that can support dual-mode terminals to complete registration, it is used to:

An attach request is initiated to register with the core network; after the authentication and authentication process for the user, the MME is triggered to initiate a session establishment process.

The UE, for applying an attach/RAU request to implement registration in the GERAN/UTRAN, triggering the SGSN to perform context acquisition and authentication authentication process for the UE by sending a RAU request/attach request, and initiating a process of creating a session/modifying a bearer; The PGW is also triggered to perform bearer activation, or the bearer modification process to the PGW is initiated according to the address information of the PGW in the context, and the bearer established in the first access system is established or modified in the second access system, and two accesses are completed. The bearer binding of the system.

The UE is further configured to carry an indication of whether to support the dual-mode terminal simultaneous communication function when accessing the network.

The UE is further used to:

In the sent TAU request/RAU request/attach request, carrying an indication that the UE requests simultaneous registration in two systems;

The indication is implemented by adding a new IE to the request message, or by augmenting the value of an existing IE including a registered ATAU type IE. The UE is further used to:

If the UE activates and wants to use the bearer in the two access systems, when the UE accesses from the second access system, carries the relevant bearer identifier; triggering the mobility management unit including the SGSN or the MME to perform according to the bearer identifier Bearer binding.

The mobility management unit, including the SGSN or the MME, is further configured to notify, in the context request message or the context response message, whether the registration, and/or bearer information before the source SGSN is valid.

The method and system of the invention can effectively support the dual mode terminal to simultaneously access different networks and receive services at the same time. It can not only realize more flexible data transmission paths for different access technologies, but also realize reasonable and full utilization of resources, and avoid problems such as excessive load on a single access technology and limited transmission rate. DRAWINGS

Figure 1 is a schematic diagram showing the structure of an EPS in a non-roaming situation;

2 is a schematic structural diagram of interworking between a GPRS network and an EPS network;

3 is a flow chart of accessing multiple access terminals from two access networks in the prior art; FIG. 4 is a system diagram for supporting simultaneous communication of dual mode dual standby terminals according to an embodiment of the present invention; FIG. 6 is a flowchart of supporting simultaneous communication of a dual mode dual standby terminal according to an embodiment of the present invention; FIG. 7 is a flowchart supporting dual mode according to another embodiment of the present invention; Flowchart of simultaneous communication of dual standby terminals; FIG. 8 is a schematic flow chart of simultaneous communication supporting dual mode dual standby terminals according to an embodiment of the present invention. detailed description

In a practical application, the UE may access from the first access system, select a network element capable of supporting the dual mode terminal, and complete registration; and the UE may also access from the second access system, and the second access system is in the network. The node can complete bearer synchronization and binding for the UE; after the above operation succeeds, the UE is the same The two access systems remain registered and can receive and send traffic at the same time. The embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

Embodiment 1:

Referring to Figure 4, Figure 4 is a schematic diagram of the architecture of the application of the method of the present invention.

In Figure 4, the terminal accesses the network through UTRAN/GERAN/LTE. The core network elements accessed by UTRAN and GERAN are Gn/Gp SGSN and GGSN (the PGW includes the function of GGSN). When the terminal accesses from different access networks, if a PDN connection to the same APN is established, the anchor point is at the PGW/GGSN. When the UE accesses the same PDN connection from two RATs, the address allocated by the same PGW/SGSN is used.

Embodiment 2:

Referring to FIG. 5, FIG. 5 is a second schematic diagram of the application of the method of the present invention.

In Figure 5, the terminal accesses the network through UTRAN/GERAN/LTE. The core network elements accessed by UTRAN and GERAN are S4 SGSN, SGW and PGW. When the terminal accesses from a different access network, if a PDN connection to the same APN is established, the anchor point is at the PGW/GGSN. When the UE accesses the same PDN connection from two RATs, the address allocated by the same PGW/SGSN is used.

At this time, the UEs can access the same SGW by accessing different RATs. Of course, different SGWs can also be selected, that is, the MME and the SGSN respectively select the SGW.

Embodiment 3:

Referring to FIG. 6, FIG. 6 is a schematic diagram of a flow of accessing a multimode terminal from two access networks by using the method of the present invention. In this embodiment, it is assumed that the terminal registers with GERAN/UTRAN first, and then registers with LTE. The SGSN in this embodiment is an SGSN supporting a Gn/Gp interface. This embodiment specifically includes the following steps:

Steps 601 to 602, when the user is powered on, the application attach request initiates an attach process to register in the core network. The non-access stratum message is encapsulated by the RRC or the base station subsystem (BSS) and sent to the SGSN. Step 603: If there is no context information of the user in the network, or the attachment request message has no integrity protection, or the integrity protection fails, the SGSN performs an authentication and authentication process for the user.

Step 604: If there is no subscription data of the user in the SGSN, send an update location request message to the home subscriber server, including information such as a mobility management unit identifier, a user identifier, an update type, and the like. The user data server checks the request of the SGSN. If passed, the HSS inserts the subscription data request and sends the subscriber's subscription data to the SGSN, including the subscription APN, and the QoS parameters associated with each APN. After the SGSN returns an insertion contract data response to the HSS, the HSS returns a location update response to the SGSN.

Step 605: The SGSN returns a registration accept message to the UE, where the temporary user identification information allocated for the UE is carried. The UE returns a registration completion message to the SGSN. The registration accept message may also include the function of the network side supporting the simultaneous communication of the dual mode terminal. This indication can be achieved by expanding the IE (information element) value in the message, or by adding a new IE.

If the UE wishes to initiate a service immediately under the RAT, the PDP activation procedure is performed; otherwise, steps 606 to 608 are skipped, and step 609 is performed.

Step 606: The UE initiates a PDP activation process, and sends a PDP context activation request to the SGSN by using the RNC/BSS, where the APN that the UE requests to establish, and the requested QoS parameter are carried.

Step 607: The SGSN selects a suitable GGSN for the UE according to the APN. The SGSN sends a PDP context activation request to the GGSN, which carries the identity of the UE, the requested APN, and the QoS and other related parameters. The GGSN performs an authorization check on the QoS parameters. After successful activation, the GGSN returns a PDP context activation response to the SGSN. It carries the QoS of the authorization, and the parameters such as the IP address of the UE.

Step 608: The SGSN returns a PDP context activation response to the UE through the RNC/BSS, and the RNC/BSS also needs to establish a radio bearer. The PDP context activation response message may also include The network side supports this function of simultaneous communication between dual mode terminals. This indication can be achieved by extending the value of the IE in the existing message or by adding a new IE.

Step 609: The UE moves to the coverage of the EUTRAN. If it is desired to accept the service from the EUTRAN at the same time, the application/TAU (Tracking Area Update) request initiates a tracking area update process or a registration process for registration in the EUTRAN. The attach/TAU request message is encapsulated by the eNB and sent to the MME.

Step 610: The eNB routes the TAU request/attach request to the appropriate MME.

If the UE wants to bind to some of the previous bearers, the UE also needs to carry the bearer identifier of the bound bearer.

Further, the TAU request/attach request sent by the UE may further include an indication that the UE wants to register at the two RATs at the same time. This indication can be achieved by adding a new IE to the request, or by augmenting the value of an existing IE, such as an extended registration/TAU type IE.

Step 611: The MME performs an authentication and authentication process for the user.

In this process, neither the UE nor the network side maps the security context to ensure that the UE is independent of the two RAT authentication and Key generation.

Step 612: The MME determines, according to the registration or TAU type indication carried in the registration or TAU request message, how to obtain the context.

If the indication type carried by the attach request indicates that the UE's request to register with the two RATs is valid, the MME needs to go to the SGSN to acquire the context.

If the TAU process is utilized, since the TAU process is context-acquired, no special judgment is required here.

It can be seen that, in step 612, if the attaching process is utilized, whether the context is obtained according to the request type is determined; if the TAU process is utilized, the context is always obtained. The main purpose of this process is to exchange the core network's capabilities, avoid bearer identity conflicts, and obtain PGW addresses.

The request type may be dual radio, and the purpose of the request is to support establishing a dual pass. Road, but the name of the request type is not limited to this.

Step 613: The MME finds the SGSN originally registered by the UE according to the temporary user identifier of the UE included in the TAU request, and sends a context request message to the UE. The SGSN checks the UE and sends the context of the UE to the MME after the check. After receiving the context of the UE, the MME returns a context response to the SGSN.

In this process, if the UE does not previously notify the MME that the previously registered network supports the dual mode terminal to simultaneously access the functions of the two networks, the SGSN may notify the MME whether the function is supported by the context response message.

The MME needs to notify the source SGSN whether the MME supports the function in the context request message or the context response message. If the MME does not support it, the SGSN performs the deletion of the context after the flow according to the prior art. Otherwise, the SGSN needs to confirm that the previous registration and bearer related information is still valid. This embodiment assumes that the MME supports this function.

Step 614: The MME sends an update location request message to the HSS, where the mobility management unit identifier, the user identifier, the update type, and the like are included. The user data server sends the subscriber subscription data to the MME in the Update Location Response message, including the subscription APN, and the QoS parameters that each APN defaults to bear.

Step 615: The MME determines, according to the context acquired from the SGSN, whether the UE has activated bearer information. If steps 606 through 608 have been previously performed, the UE has an active context and the MME needs to also establish these contexts in the EPS. At this time, the MME selects the same PGW according to the UE context information. Further, the MME selects the SGW based on the location information.

If the UE does not have an active context, the MME must have a context requirement according to the EPS, and the MME establishes a new context for the UE. Then, the manner of selecting the PGW and the SGW supporting the function is the same as the prior art.

Steps 615 to 619, if the new bearer is created, the MME sends a create session request to the PGW through the SGW, where the QoS parameters, charging characteristics, and other related parameters related to the default bearer are carried. Such as If the MME is to establish an existing bearer of the UE in the EPS, the MME sends a create session request message to the SGW, and the SGW sends a modify bearer request message to the PGW, where the RAT information that the PGW currently accesses needs to be indicated, and the two RAT bearers are bound. The specified information. Similarly, the indication can be implemented by extending an existing IE or adding an IE.

Step 621: The PGW determines to perform bearer activation according to the received message type and the indication information contained therein, or establishes and completes binding on the already established bearer in another RAT.

It can be seen that, in step 621, the PGW needs to be able to distinguish between a dual radio or a single radio.

Steps 622 to 623, the PGW authorizes the requested bearer QoS, and sends a create session (or modify bearer) response to the MME through the SGW.

Step 624: The MME returns a TAU/Attachment Accept message to the UE, where the message indicates whether the dual radio is supported, and the temporary user identifier allocated for the UE is carried. After receiving the UE, the UE returns a TAU/Attachment Complete message to the MME. The TAU/Attachment Accept message may also include an indication of whether the network has allowed/has accepted the UE to register with the two RATs.

This step may also be to establish a radio bearer for the UE.

Further, it can also be valid for both RATs, or only for the payload of a certain RAT.

After the process ends, the UE is valid at the same time as the registration of the two RATs, and the service can be initiated separately from the two RATs.

Embodiment 4:

Referring to FIG. 6, FIG. 6 is a schematic diagram of a flow of accessing a multimode terminal from two access networks by using the method according to the present invention. In this embodiment, it is assumed that the terminal registers with GERAN/UTRAN first, and then registers with LTE. The SGSN in this embodiment is an SGSN supporting an S4 interface. The main difference between this embodiment and Embodiment 3 is embodied in the interface between the SGSN and the GGSN. The S4 SGSN needs to be connected to the PGW through the SGW. Therefore, the main difference is as follows: In step 607, the SGSN needs to select the SGW and the PGW.

In step 608, the SGSN sends a create session request to the PGW through the SGW, where the SGSN carries the user identifier, the requested QoS parameter, the charging feature, and the like. The PGW authorizes the requested bearer QoS and sends a create session response to the SGSN through the SGW.

Embodiment 5:

Referring to FIG. 7, FIG. 7 is a schematic diagram showing a flow of accessing a multimode terminal from two access networks by using the method of the present invention. In this embodiment, it is assumed that the terminal first registers from LTE and then registers from GERAN/UTRAN. The SGSN in this embodiment is an SGSN supporting an S4 interface. This embodiment specifically includes the following steps:

Steps 701 to 702, when the user is powered on, the application attach request initiates an attach process to register in the core network. The non-access stratum message is encapsulated by S1 and sent to the MME.

Step 703: If there is no context information of the user in the network, or the attach request message does not have integrity protection, or the integrity protection fails, the MME performs an authentication and authentication process for the user.

Step 704: If the MME does not have the subscription data of the UE, the MME sends an update location request message to the HSS, where the mobility management unit identifier, the user identifier, the update type, and the like are included. The user data server sends the user subscription data to the MME in the update location response message, including the subscription APN, and the QoS parameters of each APN default bearer.

Step 705: The MME needs to select the SGW and the PGW according to the APN and the location information.

Steps 705 to 708, the MME sends a create session request to the PGW through the SGW, where the QoS parameters, charging characteristics and other related parameters related to the default bearer are carried. The PGW authorizes the requested bearer QoS and sends a create session response to the MME through the SGW.

Step 709: The MME returns a registration accept message to the UE, where the temporary user identifier allocated for the UE is carried. After receiving the UE, the UE returns a registration completion message to the MME. Attached to the acceptance message can also An indication of whether the network supports UE registration on both RATs. This indication can be achieved by extending the value of the IE in the existing message or by adding a new IE.

In this step, the radio bearer may also be established for the UE, which is known in the art and is not mentioned.

Steps 710 to 711, the UE moves to the coverage of the GERAN/UTRAN. If it is desired to receive the service from the GERAN/UTRAN at the same time, the application attach/RAU (Routing Area Update) request initiates the routing area update procedure or the registration procedure for performing in the GERAN/ UTRAN registration. The attach/RAU request message is encapsulated by the RNC/BSS and sent to the SGSN.

Further, the UE sends a RAU request/attach request, which may further include indicating that the UE wants to register at the two RATs at the same time. This indication can be achieved by adding a new IE to the request, or by augmenting the value of an existing IE, such as an extended registration /RAU type IE.

Step 712: The SGSN determines how to obtain the context according to the registration or RAU type indication carried in the registration or RAU request message.

If the indication type carried by the attach request is that the UE requests to register with the two RATs, the MME needs to go to the SGSN to acquire the context.

If the RAU process is utilized, since the RAU process is context-acquired, no special judgment is required here.

It can be seen that, in step 710, if the attaching process is utilized, whether the context is acquired according to the request type (dual radio) is determined; if the TAU process is utilized, the context is always acquired. The main purpose of this process is to exchange the core network's capabilities, avoid bearer identity conflicts, and obtain PGW addresses.

The request type may be dual radio. The purpose of the request is to support dual channel establishment, but the name of the request type is not limited thereto. The purpose of the request is to support the establishment of dual channel, but the name of the request type is not limited to this. . Step 713: The SGSN finds the MME originally registered by the UE according to the temporary user identifier of the UE included in the RAU request, and sends a context request message to the MME. The MME checks the UE, and sends the context of the UE to the SGSN after the check is passed. After receiving the context of the UE, the SGSN returns a context response to the MME.

In this process, if the UE does not previously notify the MME that the previously registered network supports the dual mode terminal to simultaneously access the functions of the two networks, the MME may notify the SGSN whether the function is supported by the context response message.

The SGSN needs to notify the source MME whether the function is supported in the context request message or the context response message. If not supported, the MME will perform the deletion of the context after the prior art process. Otherwise, the MME needs to confirm that the previous registration and bearer related information is still valid. This embodiment assumes that the MME supports this function.

Step 714: The SGSN performs an authentication and authentication process for the user. In this process, neither the UE nor the network side maps the security context to ensure that the UE is independent of each other in the two RAT authentication and Key generation.

Step 715: The SGSN accesses and establishes a corresponding bearer in the UTRAN/GERAN according to the bearer information included in the acquired context. At this time, the SGSN may select the same SGW as the MME, or may be different. If it is a newly selected SGW, then the current location information of the UE should also be considered.

If the SGSN reselects the SGW, the SGSN sends a create session request to the new SGW, which carries the identity of the UE, and carries related parameters such as QoS parameters, charging features, and access RAT.

If the SGSN does not select a new SGW, the SGSN sends a modify bearer request to the SGW, which carries the identifier of the UE, the QoS parameters related to the bearer, the charging feature, and the related parameters of the accessed RAT. The modify bearer request needs to indicate that the bearer information of the SGW on another RAT is also valid.

Step 716: The SGW sends a modify bearer request to the PGW, where the identifier of the UE is carried. Relevant parameters such as related QoS parameters, charging characteristics, and access RAT. The RAT information indicating the current access of the PGW and the indication information for binding the two RAT bearers are needed. Similarly, the indication can be implemented by extending an existing IE or adding an IE.

Step 717: The PGW determines to perform bearer activation according to the received message type and the indication information contained therein, or establishes and completes binding on the already established bearer in another RAT.

Steps 718 to 719, the PGW authorizes the requested bearer QoS, and sends a modify bearer (create session) response message to the SGSN through the SGW.

Step 720: If there is no subscription data of the user in the SGSN, send an update location request message to the home subscriber server, including information such as a mobility management unit identifier, a user identifier, and an update type. The user data server checks the request of the SGSN. If passed, the HSS inserts the subscription data request and sends the subscriber's subscription data to the SGSN, including the subscription APN, and the QoS parameters associated with each APN. After the SGSN returns an insertion contract data response to the HSS, the HSS returns a location update response to the SGSN.

Step 721: The SGSN returns a RAU/Registration Accept message to the UE, where the temporary user identification information allocated for the UE is carried.

Step 722: The UE returns a RAU/Registration Complete message to the SGSN. The RAU/Attachment Accept message may also include an indication of whether the network has allowed/has accepted the registration of the UE in both RATs.

Embodiment 6:

Referring to FIG. 7, FIG. 7 is a schematic diagram of a flow of accessing a multimode terminal from two access networks by using the method according to the present invention. In this embodiment, it is assumed that the terminal first registers from LTE and then registers from GERAN/UTRAN. The SGSN in this embodiment is an SGSN supporting a Gn/Gp interface. The main difference between this embodiment and Embodiment 5 is embodied in the interface between the SGSN and the PGW. There is no SGW between the Gn/Gp SGSN and the GGSN. Therefore, the main difference is as follows: Steps 715 to 716, the SGSN sends an update PDP context request to the GGSN, where the user identifier, the requested QoS parameter, the charging feature, and the access RAT are carried. Related parameters. The request needs to indicate that the bearer information of the GGSN on another RAT is also valid.

Steps 718 to 719, the GGSN returns an Update PDP Context Response to the SGSN, which carries the authorized QoS parameters.

As shown in the above embodiments, the operation of the present invention for supporting simultaneous communication of dual-mode dual-standby terminals can represent the flow shown in FIG. 8, and the process includes the following steps:

Step 810: The UE accesses from the first access system, and selects a network element that can support the dual mode terminal to complete registration.

Step 820: The UE accesses from the second access system, and the network node in the second access system completes synchronization and binding for the UE.

Step 830: The UE remains registered in the two access systems at the same time, so that the service can be accepted and sent at the same time.

The system of the present invention includes a UE, a first access system, and a second access system. The UE is configured to access from the first access system, and select a network element capable of supporting the dual mode terminal to complete registration. And accessing from the second access system and simultaneously maintaining registration status in the two access systems, so that the service can be simultaneously received and transmitted; the second access system is configured to complete the bearer for the UE by its network node. Synchronization and binding.

When the terminal is registered from the GERAN/UTRAN and then registered from the LTE system, the first access system is GERAN/UTRAN, the second access system is an LTE system, and the UE is connected from the first access system. When the network element that can support the dual-mode terminal completes the registration, it is used to: initiate an attach request to register to the core network; after the authentication and authentication process for the user, trigger the SGSN The UE accesses from the second access system, and when the network node in the second access system completes bearer synchronization and binding for the UE, the UE is used to initiate an attaching of the ATAU request to implement registration in the EUTRAN; Perform authentication authentication and obtain context, select an appropriate PGW and trigger the PGW to perform bearer activation, or initiate a bearer modification process to the PGW according to the address information of the PGW in the context acquisition process, and establish the bearer modification process in the first access system. The bearer is established or modified in the second access system, and the bearer binding of the two access systems is completed.

After the first access system completes registration, the UE is further configured to initiate a bearer setup procedure in the first access system: initiate a PDP context activation procedure in the first access system.

When the terminal is first registered from the LTE and then registered from the GERAN/UTRAN, the first access system is an LTE system, the second access system is a GERAN/UTRAN, and the UE is accessed from the first access system. When the network element that can support the dual-mode terminal completes the registration, it is used to: initiate an attach request to register to the core network; after the authentication and authentication process for the user, trigger the MME to initiate a session establishment process.

The UE accesses from the second access system, and when the network node in the second access system completes the bearer synchronization and binding for the UE, the UE is used to apply the attach/RAU request to register in the GERAN/UTRAN. Sending the RAU request/attach request triggers the SGSN to perform context acquisition and authentication authentication process for the UE, and initiates a process of creating a session/modifying the bearer; also triggering the PGW to perform bearer activation, or initiating a bearer to the PGW according to the address information of the PGW in the context. The modification process is to establish or modify the bearer established in the first access system in the second access system, and complete the bearer binding of the two access systems.

When the UE accesses the network, it is further used to carry an indication of whether to support the simultaneous communication function of the dual mode terminal.

The UE is further configured to: in the sent TAU request/RAU request/attach request, carry an indication that the UE requests to be simultaneously registered in two systems; the indication is implemented by adding a new IE in the request message, or By extending the existing IE including registration / TAU type IE The value is implemented.

The UE is further configured to: if the UE activates and want to use the bearer in the two access systems, when the UE accesses from the second access system, carry the relevant bearer identifier; trigger the mobility management including the SGSN or the MME The unit performs bearer binding according to the bearer identifier.

The mobility management unit, including the SGSN or the MME, is further used to notify the source SGSN whether the registration, and/or bearer information is valid in the context request message or the context response message when the context is acquired.

In summary, the technology of the dual-mode dual-standby terminal simultaneous communication provided by the present invention can effectively support the dual-mode terminal to simultaneously access different networks and receive services at the same time. It can not only realize more flexible data transmission paths for different access technologies, but also realize reasonable and full utilization of resources, and avoid problems such as excessive load on a single access technology and limited transmission rate.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for supporting dual-mode dual-standby terminal UE simultaneous communication, comprising:

The UE remains registered in both access systems at the same time so that services can be received and transmitted simultaneously.

2. The method according to claim 1, wherein the terminal first registers from the GSM EDGE radio access network GERAN/Universal Terrestrial Radio Access Network UTRAN, and then registers with the Long Term Evolution LTE system, the first access The system is GERAN/UTRAN, and the second access system is an LTE system;

The method according to claim 2, wherein the UE accesses from the second access system, and the process in which the network node in the second access system completes bearer synchronization and binding for the UE includes:

4. The method according to claim 2, wherein after the first access system completes registration, the UE further needs to initiate a bearer setup process in the first access system, the method further comprising: the UE is in the first connection The incoming system initiates a PDP context activation process.

The method of claim 1, wherein the terminal is first registered from the LTE, and then registered from the GERAN/UTRAN, the first access system is an LTE system, and the second access system is a GERAN/ UTRAN;

The method according to claim 5, wherein the UE accesses from the second access system, and the process in which the network node in the second access system completes bearer synchronization and binding for the UE includes:

7. The method according to claim 1, wherein the method further comprises:

8. The method according to claim 3 or 5, wherein the method further comprises:

The method according to claim 3 or 5, wherein the method further comprises: if the UE is activated and wants to use the bearer in the two access systems, when the UE accesses from the second access system, it needs to carry the relevant Bearer identifier The mobility management unit including the SGSN or the MME performs bearer binding according to the bearer identifier.

The method according to claim 3 or 5, wherein the method further comprises: in the process of acquiring the context, the mobility management unit, including the SGSN or the MME, notifying the source SGSN in the context request message or the context response message Whether the previous registration, and / or bearer information is valid.

A system for supporting simultaneous communication between dual-mode dual-standby UEs, including a UE, a first access system, and a second access system;

The second access system is configured to perform bearer synchronization and binding by the network node for the UE.

12. The system according to claim 11, wherein the terminal first registers with the GERAN/UTRAN, and when the LTE system registers, the first access system is GERAN/UTRAN, and the second access system is LTE system;

When the UE accesses from the first access system and selects a network element capable of supporting the dual mode terminal to complete registration, the UE is configured to:

13. The system according to claim 12, wherein the UE accesses from a second access system, and when a network node in the second access system completes bearer synchronization and binding for the UE,

The system according to claim 12, wherein, after the first access system completes registration, the UE is further configured to initiate a bearer setup process in the first access system: in the first access system Initiate a PDP context activation process.

The system according to claim 11, wherein the first access system is an LTE system, and the second access system is a GERAN/ when the terminal first registers with the LTE and then registers with the GERAN/UTRAN. UTRAN;

The system according to claim 15, wherein the UE accesses from the second access system, and when the network node in the second access system completes bearer synchronization and binding for the UE,

The system according to claim 11, wherein the UE is further configured to carry an indication of whether to support the simultaneous communication function of the dual mode terminal when accessing the network.

The system according to claim 13 or 15, wherein the UE is further configured to: in the sent TAU request/RAU request/attach request, carry an indication that the UE requests to register at the two systems simultaneously;

The indication is implemented by adding a new IE to the request message, or by expanding the package The value of the existing IE including the registration/TAU type IE is implemented.

The system according to claim 13 or 15, wherein the UE is further configured to: if the UE activates and wants to use a bearer in two access systems, when the UE accesses from the second access system, Corresponding bearer identifier; triggering, by the mobility management unit, including the SGSN or the MME, to perform bearer binding according to the bearer identifier.

The system according to claim 13 or 15, wherein the mobility management unit including the SGSN or the MME is further configured to notify the source SGSN in the context request message or the context response message when acquiring the context. Whether the registration, and/or bearer information is valid.