CN101426248B - Method and system for supporting circuit domain service in high-speed data access evolution network - Google Patents

Abstract

An embodiment of the invention discloses a method and a system for supporting circuit switching field (CS) service in a high speed data access (HSDA) evolution network. User equipment (UE) under an evolution base station (NodeB+) initializes a CS calling. The NodeB+ initializes a relocating request to RNC through an interface arranged between the radio network controller (RNC) in the traditional network under standalone carrier scene. The RNC executes wireless parameter collocation and relocating preparation according to the relocating request and informs the container collocated for NodeB+ and RNC. The NodeB confirms initializing physical layer channel re-collocating information to UE according to the informing information. The UE executes radio link re-collocation according to the information in the physical layer channel re-collocating information and accesses the RNC for completing re-collocation. The application of the method and system defined in the embodiment of the invention can shorten the time delay in the establishing process of CS calling.

Description

Method and system for supporting circuit domain services in high-speed data access evolved network

technical field

The invention relates to mobile communication technology, in particular to a method and system for supporting circuit domain services in a high-speed data access evolution network.

Background technique

The Universal Mobile Telecommunications System (UMTS) is a third generation (3G) mobile communication system that adopts Wideband Code Division Multiple Access (WCDMA) air interface technology, and the UMTS system is usually called a WCDMA communication system. The UMTS system adopts a structure similar to that of the second generation mobile communication system, as shown in Figure 1, which is a schematic diagram of the composition and structure of the existing UMTS system. It can be seen from FIG. 1 that the existing UMTS system mainly includes four parts: user terminal (UE), UMTS external radio access network (UTRAN), core network (CN) and external network.

Among them, the CN is used to handle all voice calls and data connections in the UMTS system, and realize the switching and routing functions with the external network. CN can be logically divided into Circuit Switching Domain (CS) and Packet Switching Domain (PS), which include main functional entities such as Mobile Services Switching Center (MSC)/Visitor Location Register (VLR), and General Packet Radio Service Support Node (SGSN) and so on. Among them, MSC/VLR is a functional node in the CS domain, connected to UTRAN through the Iu_CS interface, and is mainly used to provide call control, mobility management, authentication and encryption in the CS domain; SGSN is a functional node in the PS domain, connected to UTRAN through the Iu_PS interface It is connected to provide routing and forwarding, mobility management, session management, authentication and encryption functions of the PS domain.

UTRAN is used to handle all wireless-related functions, and its specific structure is shown in Figure 2, including one or several radio network subsystems (RNS), and each RNS is specifically composed of a radio network controller (RNC) and a or multiple base stations (NodeB). Wherein, the interface between the RNC and the CN is an Iu interface, the interface between the NodeB and the RNC is an Iub interface, and the RNCs are interconnected through the Iur interface. The RNC is used to allocate and control the wireless resources of the NodeB connected or related to it; the NodeB is used to complete the data flow conversion between the Iub interface and the Uu interface, and participate in part of the wireless resource management at the same time. The protocol structure of each interface in UTRAN is designed according to a common protocol model, and the design principle is that layers and planes are logically independent of each other.

On the basis of the network system shown in Figure 1, in 2006, the Third Generation Partnership Project (3GPP) passed the High Speed Data Access (HSPA) evolution research project. The HSPA evolution network architecture is implemented based on the PS domain, which provides higher bit rate user rates and shorter call delays for PS domain services, and will no longer be optimized for CS domain services in the current 3G system.

In the HSPA evolved network, all RNC functions in the existing 3G system are concentrated in the evolved base station, namely NodeB+. Under the HSPA evolution network architecture, NodeB+ is directly connected to the SGSN, and the interface between the two is Iu_PS; while there is only signaling connection between NodeB+ and CS domain nodes in CN, such as MSC/VLR, there is no user plane connection, so NodeB+ Services in the CS domain cannot be provided independently. Therefore, in order to enable the HSPA evolved network to support CS domain call services, it is necessary to realize interconnection between the HSPA evolved network supporting PS domain services and the traditional network supporting both PS domain and CS domain services. In the prior art, there are mainly two schemes for the interconnection between NodeB+ in the HSPA evolved network and the RNC in the traditional network, that is, the evolved HSPA UTRAN (Carrier Sharing Evolved HSPA UTRAN) of the shared carrier and the evolved HSPA UTRAN (Standalone Evolved HSPA UTRAN) of the independent carrier. ).

Figure 3 is a schematic diagram of the evolved HSPA UTRAN network architecture of the existing independent carrier. As shown in Figure 3, the evolved HSPA UTRAN network with independent carriers is mainly composed of two parts, namely UTRAN and CN.

Among them, NodeB+ in UTRAN includes all the functions of the original NodeB and RNC, and is used to complete the processing of the Uu interface physical layer protocol, connection establishment and disconnection, handover, macro-diversity combination, and radio resource management and control functions.

CN is responsible for the connection with other networks and the communication and management of the UE. The main functional entities include: MSC/VLR, which is the functional node of the CS domain of the core network in the HSPA evolution network. NodeB+ only has an optional Iu_CS signaling connection with it , the main function is to provide call control, mobility management, authentication and encryption in the CS domain; SGSN is a functional node in the PS domain of the core network, connected to UTRAN through the Iu_PS interface, and provides routing forwarding and mobility management in the PS domain , session management, authentication and encryption functions. Under this network architecture, the HSPA evolution network and the traditional network use different carriers, and the NodeB+ in the HSPA evolution network is connected through the Iur interface, but there is no interface with the RNC of the traditional network.

Figure 4 is a schematic diagram of the evolved HSPA TURAN network architecture of the existing shared carrier. As shown in Figure 4, this network architecture has the same network nodes as the network architecture shown in Figure 3. The difference is that there is an Iur interface between NodeB+ and the RNC in the traditional network, which is used to exchange some control information between NodeB+ and RNC. order and data.

Under the network architecture shown in Figure 3, when a UE under the NodeB+ initiates a CS domain call, since the NodeB+ itself cannot directly handle the CS domain call, the NodeB+ needs to trigger an inter-frequency hard handover from the UE to a traditional network that supports CS domain services. Inter-frequency hard handover includes two processes, one is the relocation of the Iu interface (Relocation). In the prior art, for a certain UE, the RNC that is directly connected to the core network and controls all resources of the UE is called the serving RNC of the UE, and is not connected to the core network, and only provides resources for the UE The RNC of the UE is called the free RNC of the UE. Relocation refers to the process of transferring the role of the serving RNC of a certain UE from one RNC to another. Before Relocation, the serving RNC of the UE is called the source RNC (Source RNC), and the RNC that will assume the role of the serving RNC is called the target RNC (Target RNC). Another process is the handover of the air interface. The handover of the air interface refers to the change of the radio link of the UE, which may be handover from one sector to another sector, or handover from one cell to another. Hard handover includes handover of the air interface accompanied by relocation of the Iu interface. The frequency difference means that the service frequency of the UE changes before and after handover. Since the HSPA evolution network and the traditional network use different carriers under the network architecture shown in FIG. 3 , the handover is an inter-frequency hard handover.

In the existing Standalone scenario, because the NodeB+, hereinafter referred to as NB+, has only Iu_CS signaling connection with the MSC, that is, the control plane connection, there is no user plane connection, and the NB+ in the Standalone scenario may not be configured to support traditional CS services Dedicated channel (DCH), there is no Iur interface that can communicate between NB+ and the RNC of the traditional network. Therefore, the UE must switch to the RNC of the traditional network to complete the entire CS call. However, in the prior art, the switching process must be completed through the core network, thus virtually increasing the transmission delay of the message and affecting the service experience of the user.

Contents of the invention

An embodiment of the present invention provides a method for supporting circuit domain services in a high-speed data access evolved network, which can shorten CS call establishment delay.

Embodiments of the present invention provide a system for supporting circuit domain services in a high-speed data access evolved network, which can shorten CS call establishment delay.

The technical scheme of the embodiment of the present invention is realized like this:

A method for supporting circuit switching domain CS services in a high-speed data access HSPA evolution network, comprising:

A user terminal UE located under the evolved base station NodeB+ initiates a CS call;

The NodeB+ initiates a relocation request to the RNC through the interface set between the independent carrier Standalone scenario and the radio network controller RNC in the traditional network, and the RNC performs wireless parameter configuration and relocation according to the relocation request. Locating preparations, and notifying the NodeB+RNC of the container configured by itself;

The NodeB+ initiates a physical layer channel reconfiguration message to the UE according to the notification message, and performs air interface switching and Iu interface relocation;

The UE performs radio link reconfiguration according to the information in the physical layer channel reconfiguration message, and accesses the RNC to complete relocation.

A system supporting CS services in an HSPA evolution network, comprising: a NodeB+ and a UE located in a Standalone scenario in an HSPA evolution network, and an RNC located in a traditional network; an interface is provided between the NodeB+ and the RNC; wherein,

The NodeB+ is configured to initiate a relocation request to the RNC after the UE initiates a CS call, receive a notification message sent back by the RNC, and determine to initiate physical layer channel reconfiguration to the UE according to the notification message message, to switch over the air interface and relocate the Iu interface;

The RNC is configured to perform wireless parameter configuration and relocation preparation according to the relocation request received from the NodeB+, and notify the NodeB+RNC itself of the configured container;

The UE is configured to initiate a CS call to the NodeB+, perform radio link reconfiguration according to information in a physical layer channel reconfiguration message received from the NodeB+, access the RNC, and complete relocation.

It can be seen that, adopting the technical solution of the embodiment of the present invention, in the Standalone scenario, when the UE under the NodeB+ initiates a CS call: the NodeB+ sends a relocation request to the RNC in the traditional network, and the RNC performs wireless parameter configuration and communication according to the relocation request. Prepare for relocation, and notify NodeB+ of the container configured by itself; NodeB+ determines to send a physical layer channel reconfiguration message to UE according to the notification message, and performs air interface switching and Iu interface relocation; UE according to the physical layer channel reconfiguration message information to perform wireless link reconfiguration, and access to the RNC to complete relocation. Compared with the prior art, the solution described in the embodiment of the present invention sets up an interface between the NodeB+ and the RNC in the traditional network, so that many processes in the inter-frequency hard handover process no longer need to be forwarded through the core network, thus speeding up inter-frequency handover. The speed of frequency hard handover is shortened, thereby shortening the CS call setup delay.

Description of drawings

FIG. 1 is a schematic diagram of the composition and structure of an existing UMTS system.

FIG. 2 is a schematic diagram of the composition and structure of the existing UTRAN.

Figure 3 is a schematic diagram of the evolved HSPA UTRAN network architecture of the existing independent carrier.

FIG. 4 is a schematic diagram of an evolved HSPA UTRAN network architecture of an existing shared carrier.

Fig. 5 is a flowchart of a method embodiment of the present invention.

Fig. 6 is a flow chart of the first preferred embodiment of the method of the present invention.

Fig. 7 is a flow chart of the second preferred embodiment of the method of the present invention.

Fig. 8 is a flow chart of the third preferred embodiment of the method of the present invention.

Fig. 9 is a flow chart of the fifth preferred embodiment of the method of the present invention.

Fig. 10 is a schematic diagram of the composition and structure of the system embodiment of the present invention.

Fig. 11 is a schematic diagram of the composition and structure of a preferred embodiment of the system of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and examples.

In the embodiment of the present invention, in order to solve the problems existing in the prior art, certain modifications are made to the existing HSPA evolution network architecture in the Standalone scenario, so that it can better support CS while providing high-speed data services for users. business. Specifically, in the embodiment of the present invention, the HSPA evolution network in the existing Standalone scenario is modified, and the interface between the NB+ and the RNC in the traditional network is added, and the inter-frequency hard handover process is assisted through the added interface, Thereby speeding up the speed of inter-frequency hard switching.

The added interface can only be used for some mobility-related operations on the control plane, without involving the establishment of the user plane bearer, thereby reducing the impact of adding the interface. Because increasing the interface may increase the link budget of NB+ and RNC, and not involving the user plane, the link bandwidth does not need to be large, and the additional overhead caused is small. Certainly, the interface may also have a user plane function at the same time.

Fig. 5 is a flowchart of a method embodiment of the present invention. As shown in Figure 5, when a UE under NB+ initiates a CS call, the following steps are included:

Step 501: NB+ initiates a relocation request to RNC, and RNC configures wireless parameters and prepares for relocation according to the received relocation request, and notifies NB+ of the container configured by itself.

Step 502: The NB+ determines to send a physical layer channel reconfiguration message to the UE according to the received notification message, and performs air interface switching and Iu interface relocation.

Step 503: UE performs radio link reconfiguration according to the information in the received physical layer channel reconfiguration message, and accesses to RNC to complete relocation.

In this embodiment, the interface between the NB+ and the RNC may be an interface that only has a control plane function, or an interface that has both control plane and user plane functions. For example, the interface may be a complete Iur interface, or a simplified Iur interface, which includes only control signaling but no user plane signaling. Of course, the interface can also be a completely new interface. How to set the interface is well known in the art, and will not be introduced here.

It can be seen that by adopting the technical solution of the embodiment of the present invention, by setting an interface between the NB+ and the RNC in the traditional network, many processes in the inter-frequency hard handover process no longer need to be forwarded through the core network, thereby speeding up the inter-frequency hard handover speed. The CS call setup delay is caused by the existing CS call delay plus the inter-frequency hard handoff delay, so speeding up the inter-frequency hard handover will inevitably reduce the CS call setup delay. Below by preferred embodiment, described scheme of the present invention is described in further detail:

Preferred Embodiment One

Fig. 6 is a flow chart of the first preferred embodiment of the method of the present invention. In this embodiment, it is assumed that the source RNC of the UE is the NB+ in the Standalone scenario in the evolved HSPA UTRAN network, and the target RNC of the UE is the RNC in the UMTS network. Among them, the NB+ is connected to the core network through the Iu_CS signaling interface; the NB+ is connected to the target RNC through a newly added interface, such as an Iur interface. When a UE camped on NB+ initiates a CS service call, NB+ and the target RNC in the UMTS network supporting CS services perform inter-frequency hard handover. For the convenience of description, the target RNC is referred to as RNC for short below. As shown in Figure 6, the following steps are included:

Step 601: UE sends an initial direct transfer message to NB+.

In this step, the UE initiates a CS call under the cell (CELL) controlled by the NB+, and sends an initial direct transfer message to the NB+.

Step 602: NB+ determines that the service is a CS service according to the received initial direct transfer message, and sends an initial direct transfer message to the MSC.

After receiving the initial direct transfer message from the UE, the NB+ determines that the service is a CS service according to the indication information carried therein. In the initial direct transmission message, a bit is usually used to identify the service type. For example, 0 is used to indicate the CS service, and 1 is used to indicate the PS service. NB+ can determine whether the service is a CS service by reading this bit.

When it is determined to be a CS service, since NB+ itself cannot support CS services, it sends an initial direct transmission message to the MSC in the core network through the Iu_CS signaling interface between the NB+ and the MSC to trigger the transition from the evolved HSPA UTRAN network to support CS services switching of the traditional network.

Step 603: After receiving the initial direct transfer message, the MSC sends back an SS7 Signaling Connection Control Part (SCCP) connection confirmation message to the NB+.

In the subsequent process, the NB+ can switch from the evolved HSPA UTRAN to the traditional network supporting the CS service, that is, the UMTS network in this embodiment.

Step 604: NB+ sends a relocation request message to RNC through the newly added Iur interface, and initiates a relocation request process.

The relocation request message in this step carries the transparent container from the source RNC to the target RNC, including: source RNC identification, target RNC identification, radio access bearer (RAB) list to be established, etc. Wherein, the RAB list may include: RAB ID, transport layer address and user plane information, etc.

The RAB mentioned here means that when a user platform connection needs to be established, the MSC or SGSN instructs the UTRAN to establish a logical connection between the MSC or SGSN and the UE. The established RAB inherits the requirements of the requested UMTS service, such as service quality, etc. Based on the inherited requirements of the RAB, the RNC can use the core network to establish a user platform connection with the UE. Wherein, the connection between the RNC and the core network is called an Iu bearer, and the connection between the RNC and the UE is called a radio bearer (RB). These bearers represent logical channels at a deeper level, and the RNC completes the mapping between them. These bearers are themselves mapped to appropriate transport channels via different interfaces for transmission. One UE can be connected to one or more RABs. For example, a certain UE is connected to two RABs, one of which is used to establish a voice call, and the other is used to establish a data call. The RNC can use the RAB identifier assigned by the core network to distinguish different RABs.

In this step, NB+ can determine which RNC in the UMTS network needs to send a relocation request according to the pre-configuration or according to the information reported by the UE, that is, determine which RNC is to assist in processing its own CS service, and then send a relocation request to the RNC Relocation request.

Step 605: After receiving the relocation request, the RNC configures the mapping relationship between radio resource control (RRC), radio link control (RLC), medium access control (MAC), logical channels and transport channels according to the information carried in the container , and the mapping relationship between physical layer resources and transport channels, and assign a new temporary mobile user identity (U-RNTI) to UE, and then send a relocation response to NB+ to notify NB+ of these configured containers established on RNC, And inform the NB+RNC of the U-RNTI allocated for the UE.

Step 606: The NB+ determines to send a physical layer channel reconfiguration message to the UE according to the information in the container.

The physical layer channel reconfiguration message carries relevant information of the UE, such as the U-RNTI allocated by the RNC to the UE, RB information elements, physical layer channel information elements, uplink radio resource information elements, and downlink radio resource information elements. Wherein, each radio bearer information unit, that is, the RB information unit includes RB identifier, RLC identifier and RB mapping information.

Step 607: The UE reconfigures the radio link according to the content in the received physical layer channel reconfiguration message, completes the search for the new cell, that is, the target NodeB under the RNC, and completes synchronization with the NodeB.

Step 608: After successfully accessing the RNC, the UE sends a physical layer reconfiguration complete message to the RNC.

The physical layer reconfiguration complete message carries UE-related information elements, RB information elements, and the like.

Step 609: The RNC sends a relocation complete message to the SGSN to notify the SGSN that the relocation is complete.

If necessary, the RNC can also send a relocation complete message to the MSC to notify the MSC that the relocation is complete.

Step 610: After receiving the relocation complete message, the SGSN sends a relocation complete response message to the RNC.

Step 611: RNC sends an Iu resource release message to NB+, and NB+ releases the Iu connection with the core network and related resources.

Steps 612-613: Perform the establishment of the radio access bearer of the CS service and the call establishment process of the CS service.

Preferred Embodiment Two

Fig. 7 is a flow chart of the second preferred embodiment of the method of the present invention. In this embodiment, it is assumed that the source RNC of the UE is the NB+ in the Standalone scenario in the evolved HSPA UTRAN network, and the target RNC of the UE is the RNC in the UMTS network. It is assumed that there is no In_CS signaling connection between the NB+ and the MSC, but the NB+ and the RNC are connected through a newly added interface such as an Iur interface. When a UE camped on NB+ initiates a CS service call, NB+ and the RNC in the UMTS network supporting CS services perform inter-frequency hard handover. As shown in Figure 7, the following steps are included:

Step 701: UE sends an initial direct transfer message to NB+.

In this step, the UE initiates a CS call under the CELL controlled by the NB+, and sends an initial direct transfer message to the NB+.

Step 702: NB+ determines that the service is a CS service according to the received initial direct transmission message, and sends a relocation request message to RNC.

When it is determined to be a CS service, since the NB+ itself cannot support the CS service, it needs to switch to a traditional network that supports the CS service, that is, the UMTS network in this embodiment. In this step, the NB+ sends a relocation request message to the RNC in the UMTS network through the newly added Iur interface. The relocation request message carries the transparent container from the source RNC to the target RNC, as well as the non-access stratum (NAS) protocol data unit (PDU) carried in the initial direct transfer message and information necessary for CS connection establishment. Wherein, the transparent container includes: the identification of the source RNC, the identification of the target RNC, the list of RABs to be established, and the like.

Step 703: RNC sends an initial direct transfer message to MSC.

The initial direct transmission message carries NAS PDU and information required for CS connection establishment.

Step 704: After receiving the initial direct transfer message, the MSC returns an SCCP connection confirmation message to the RNC.

Step 705: The RNC configures the mapping relationship between RRC, RLC, MAC, logical channels and transport channels, as well as the mapping relationship between physical layer resources and transport channels according to the information carried in the relocation request received in step 702, and allocates a The new U-RNTI, after receiving the SCCP connection confirmation message from the MSC, sends a relocation response to the NB+ to notify the NB+ of these configured containers established on the RNC, and inform the NB+RNC of the U-RNTI allocated for the UE.

Steps 706-713 are the same as steps 606-613, and will not be repeated here.

Preferred Embodiment Three

Fig. 8 is a flow chart of the third preferred embodiment of the method of the present invention. In this embodiment, it is assumed that the source RNC of the UE is the NB+ in the Standalone scenario in the evolved HSPA UTRAN network, and the target RNC of the UE is the RNC in the UMTS network. It is assumed that there is no In_CS signaling connection between NB+ and MSC, but NB+ and RNC are connected through a newly added interface, such as an Iur interface. When a UE camped on NB+ initiates a CS service call, NB+ and the RNC in the UMTS network supporting CS services perform inter-frequency hard handover.

As shown in Figure 8, the difference between this preferred embodiment and the second preferred embodiment is that, while the wireless link bearer is established, the Iu bearer between the RNC and the MSC is established, that is, the Iu bearer as shown in Figure 7 Step 712 is performed in advance to step 804a shown in FIG. 8 , and the corresponding radio link reconfiguration can be completed by the RNC after step 808 or 811 is completed. Since the remaining steps in this embodiment are the same as those in the embodiment shown in FIG. 7 , they will not be repeated here.

It should be noted that the idea shown in this preferred embodiment can also be applied to the Carrier Sharing scenario in the evolved HSPA UTRAN network.

Preferred Embodiment Four

In the prior art, since the NB+ in the Standalone scenario in the evolved HSPA UTRAN network does not configure a traditional dedicated channel (DCH), the NB+ in the Standalone scenario can only carry CS services on the high-speed shared channel (CS over HSPA) . By adding an Iur interface between the NB+ and the RNC in the traditional network, the NB+ in the Standalone scenario can adopt the NB+ support method for the CS service in the Carrier Sharing scenario in the evolved HSPA UTRAN network in the prior art, and integrate the CS service or the CS service The +PS service is relocated to the RNC in the traditional network, and the NB+ is used as a free RNC that provides resources for the UE, while the RNC in the traditional network is used as the serving RNC, and the wireless resources of the NB+, that is, the high-speed shared channel, are used to support the CS service. It should be noted that the CS service bearing method described in this preferred embodiment can only be provided to UEs that support CS communication on the HSPA channel, and UEs that can only use traditional DCH channels for CS services cannot enjoy this service .

Preferred Embodiment Five

In the prior art, since the NB+ in the Standalone scenario in the evolved HSPA UTRAN network does not configure traditional DCH channels, the NB+ in the Standalone scenario can only carry CS services (CS over HSPA) on the high-speed shared channel. In this case, NB+ in the Standalone scenario can add a complete Iu_CS interface, that is, an Iu_CS interface that includes both control plane and user plane functions, to better support the CS service of the UE without relocation or switching to traditional Under the RNC in the network. Same as the fourth preferred embodiment, the UEs in this preferred embodiment are limited to UEs that support CS communication on the HSPA channel.

Fig. 9 is a flow chart of the fifth preferred embodiment of the method of the present invention. As shown in Figure 9, the following steps are included:

Step 901: UE initiates a CS call, and establishes an RRC connection with NB+.

Step 902: After the connection is established, the UE sends a service request to the MSC.

Step 903: MSC sends a command ID (Command ID) message to NB+.

If necessary, after this step, the MSC completes the UE authentication process.

Steps 904-907: the MSC sets the security mode required by the UE for CS communication.

Step 908: UE sends a setup (SETUP) request to MSC.

If necessary, after this step, the MSC executes the process of obtaining the UE's International Mobile Subscriber Identity (IMEI).

Step 909: the MSC sends a call connection message to the UE.

Steps 910-914: Execute the RAB establishment process between UE and MSC.

If necessary, after this step, the reallocation process of the Temporary Management Mobile Identity (TMSI) is performed.

Steps 915-917: ringing to complete the call setup process.

Compared with the way in which RNC and NodeB support CS services in the prior art, the way described in this embodiment is to integrate the functions of the existing RNC and NodeB into NB+, thereby omitting the communication between the existing RNC and NodeB. Let the interaction process, and other specific implementation steps be the same as those in the prior art, and will not be repeated here.

If there is a complete In_CS interface between NB+ and MSC in the Carrier Sharing scenario, the process shown in Figure 9 can also be used.

Based on the above method, FIG. 10 is a schematic diagram of the composition and structure of the system embodiment of the present invention. As shown in Figure 10, the system includes: a NodeB+ and a UE located in a Standalone scenario in an HSPA evolved network, and an RNC located in a traditional network; an interface is provided between the NodeB+ and the RNC; wherein,

NodeB+ is used to initiate a relocation request to the RNC after the UE initiates a CS call, and receive a notification message sent back by the RNC, and determine to initiate a physical layer channel reconfiguration message to the UE according to the notification message, and perform air interface switching and Iu interface switching reset;

RNC, a container for performing wireless parameter configuration and relocation preparation according to the relocation request received from NodeB+, and notifying NodeB+RNC of its own configuration;

The UE is used to initiate a CS call to the NodeB, perform radio link reconfiguration according to the information in the physical layer channel reconfiguration message received from the NodeB+, access the RNC, and complete relocation.

The above-mentioned interface between the NodeB+ and the RNC may be an interface that only has the function of the control plane, or an interface that has both the functions of the control plane and the user plane. Usually, this interface is an Iur interface.

The system shown in Figure 10 may further include: MSC, used to receive the initial direct transmission message from NodeB+, and send back an SCCP connection confirmation message to NodeB+; NodeB+ initiates a relocation request to RNC after receiving the SCCP connection confirmation message .

Or, the MSC is used to receive the initial direct transmission message sent by the RNC after receiving the relocation request message from NodeB+, and send back the SCCP connection confirmation message to the RNC; after the RNC receives the SCCP connection confirmation message, send it back to NodeB+ Relocation response message.

In addition, the MSC can be further configured to establish a radio access bearer with the RNC after sending back the SCCP connection confirmation message to the RNC.

Of course, those skilled in the art should know that, in addition to the above network elements, in practical applications, the system shown in FIG. 10 will further include other network elements, such as SGSN and GGSN. As shown in FIG. 11 , FIG. 11 is a schematic diagram of the composition and structure of a preferred embodiment of the system of the present invention. Compared with the evolved HSPA UTRAN network architecture of the existing independent carrier shown in Figure 3, the NB+ in this preferred embodiment is connected to the RNC in the traditional network through the increased Iur interface. For the specific working process of the preferred embodiment of the system, please refer to the description of the corresponding part of the method, and will not be repeated here.

It can be seen that by adopting the technical solution of the embodiment of the present invention, by setting an interface between the NB+ and the RNC in the traditional network, many processes in the inter-frequency hard handover process no longer need to be forwarded through the core network, thereby speeding up the inter-frequency hard handover speed, thereby reducing the CS call setup delay.

To sum up, the above are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (16)

1. A method for supporting CS services in a high speed data access HSPA evolved network, the method comprising:

a user terminal UE under an evolution base station NodeB + initiates a CS call;

the NodeB + initiates a relocation request to a Radio Network Controller (RNC) in a traditional network through an interface arranged between the NodeB + and the RNC in an independent carrier Standalone scene, and the RNC performs radio parameter configuration and relocation preparation according to the relocation request and informs the NodeB + RNC of a container configured by the NodeB + RNC;

the NodeB + initiates a physical layer channel reconfiguration message to the UE according to the notification message, and performs air interface switching and Iu interface relocation;

and the UE performs wireless link reconfiguration according to the information in the physical layer channel reconfiguration message and accesses the RNC to complete the relocation.

2. The method of claim 1, wherein the interface between the NodeB + and the RNC in the legacy network is a control plane only interface or a control plane and user plane interface.

3. The method of claim 2, wherein the interface is an Iur interface.

4. The method of claim 1, wherein before initiating the relocation request to the RNC, further comprising:

the UE sends an initial direct transmission message to the NodeB +;

and the NodeB + determines that the service is the CS service according to the initial direct transfer message, sends the initial direct transfer message to a mobile service switching center (MSC) in a core network, and receives a Signaling Connection Control Part (SCCP) connection confirmation message returned by the MSC, namely SS 7.

5. The method of claim 4, wherein the initiating a relocation request to the RNC, the RNC configuring radio parameters and preparing for relocation according to the relocation request, and the informing the NodeB + RNC of the container of the configuration made by itself comprises:

the NodeB + sends a relocation request message to the RNC, wherein the relocation request message carries a transparent container from the NodeB + to the RNC;

and the RNC performs radio parameter configuration and relocation preparation according to the content in the transparent container, returns a relocation response message to the NodeB + and informs the NodeB + RNC of the self-configured container and the temporary mobile user identifier U-RNTI allocated to the UE.

6. The method of claim 1, wherein the initiating a relocation request to the RNC, the RNC performing radio parameter configuration and relocation preparation according to the relocation request, and the informing the NodeB + RNC of the container of the configuration itself comprises:

the NodeB + receives an initial direct transfer message from the UE, determines that the service is a CS service according to the initial direct transfer message, and sends a relocation request message to the RNC, wherein the relocation request message carries a transparent container from the NodeB + to the RNC and information required by connection establishment;

and the RNC performs radio parameter configuration and relocation preparation according to the relocation request message, returns a relocation response message to the NodeB + after receiving the SCCP connection confirmation message returned by the MSC, and notifies the NodeB + RNC of a container configured by the NodeB + RNC and the U-RNTI allocated to the UE.

7. The method of claim 5 or 6, wherein the UE performs radio link reconfiguration according to the information in the physical layer channel reconfiguration message and accesses to the RNC comprises:

and the UE reconfigures a wireless link according to the U-RNTI, a wireless bearing information unit, a physical layer channel information unit, an uplink wireless resource information unit and downlink wireless resource information unit information which are carried in the physical layer channel reconfiguration message and are distributed to the UE by the RNC, synchronizes with a target NodeB under the RNC, and accesses the RNC.

8. The method of claim 7, wherein the accessing to the RNC further comprises, after the relocation is completed:

the RNC informs a general packet radio service support node SGSN of the completion of relocation and receives a response message returned by the SGSN;

the RNC informs the NodeB + to release Iu connection and related resources;

and executing the radio access bearer establishment of the CS service and the call establishment process of the CS service.

9. The method of claim 6, wherein before the RNC sends a relocation response message back to the NodeB +, further comprising:

and establishing a radio access bearer between the RNC and the MSC.

10. The method of claim 9, wherein after the accessing to the RNC and completing relocation, further comprising:

the RNC informs the SGSN of the completion of relocation and receives a response message returned by the SGSN;

the RNC informs the NodeB + to release Iu connection and related resources;

a call setup procedure for the CS service is performed.

11. A system for supporting CS services in an HSPA evolved network, the system comprising: NodeB + and UE under a Standalone scene in the HSPA evolution network, and RNC in a traditional network; an interface is arranged between the NodeB + and the RNC; wherein,

the NodeB + is used for initiating a relocation request to the RNC after the UE initiates a CS call, receiving a notification message returned by the RNC, determining to initiate a physical layer channel reconfiguration message to the UE according to the notification message, and performing air interface switching and Iu interface relocation;

the RNC is used for configuring wireless parameters and preparing relocation according to the relocation request received from the NodeB + and informing the NodeB + RNC of a container configured by the NodeB + RNC;

and the UE is used for initiating a CS call to the NodeB +, reconfiguring a wireless link according to the information in the physical layer channel reconfiguration message received from the NodeB +, accessing the wireless link to the RNC and finishing the relocation.

12. The system of claim 11, wherein the interface between the NodeB + and the RNC is a control plane only interface or a control plane and user plane interface.

13. The system of claim 12, wherein the interface is an Iur interface.

14. The system of claim 11, further comprising:

MSC, used for receiving the initial direct-transmitting message from NodeB + and sending back SCCP connection confirmation message to NodeB +;

and after receiving the SCCP connection confirmation message, the NodeB + initiates a relocation request to the RNC.

15. The system of claim 11, further comprising:

the MSC is used for receiving an initial direct transfer message sent by the RNC after receiving the relocation request from the NodeB +, and sending back an SCCP connection confirmation message to the RNC;

and after receiving the SCCP connection confirmation message, the RNC returns a relocation response message to the NodeB + node.

16. The system of claim 15 wherein the MSC is further configured to establish a radio access bearer with the RNC after sending an SCCP connection acknowledge message back to the RNC.

Images