CN101426248B

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

Info

Publication number: CN101426248B
Application number: CN2007101643573A
Authority: CN
Inventors: 周铮; 蔺波; 薛希俊; 张玲
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2007-10-30
Filing date: 2007-10-30
Publication date: 2010-06-23
Anticipated expiration: 2027-10-30
Also published as: CN101426248A

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 service in high-speed data access evolution network

Technical Field

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

Background

The Universal Mobile Telecommunications System (UMTS) is a third generation (3G) mobile communications system employing Wideband Code Division Multiple Access (WCDMA) air interface technology, and is commonly referred to as a WCDMA communications system. The UMTS system adopts a similar structure to that of the second generation mobile communication system, as shown in fig. 1, and fig. 1 is a schematic diagram of a conventional UMTS system composition structure. As shown in fig. 1, the conventional UMTS system mainly includes four parts, namely, a User Equipment (UE), a UMTS external radio access network (UTRAN), a Core Network (CN), and an external network.

The CN is used to handle all voice calls and data connections within the UMTS system and to implement switching and routing functions with external networks. The CN may be logically divided into a circuit switched domain (CS) and a packet switched domain (PS), and includes major functional entities such as a mobile services switching center (MSC)/Visitor Location Register (VLR), a general packet radio service support node (SGSN), and the like. Wherein, MSC/VLR is CS domain function node, connected with UTRAN through Iu _ CS interface, mainly used for providing call control, mobility management, authentication and encryption of CS domain; the SGSN is a PS domain functional node, is connected with the UTRAN through an Iu _ PS interface, and provides the functions of routing forwarding, mobility management, session management, authentication, encryption and the like of the PS domain.

The UTRAN is used for handling all radio related functions and has a specific structure as shown in fig. 2, including one or several Radio Network Subsystems (RNSs), each of which is in turn specifically composed of a Radio Network Controller (RNC) and one or more base stations (NodeB). The interface between RNC and CN is Iu interface, the interface between NodeB and RNC is Iub interface, and RNC are interconnected through Iur interface. The RNC is used for distributing and controlling the radio resources of NodeB connected with or related to the RNC; the NodeB is then used to complete the conversion of the data flow between the Iub interface and the Uu interface, and at the same time participate in part of the radio resource management. The protocol structure of each interface in UTRAN is designed according to a general protocol model, and the design principle is that the layers and the planes are logically independent from each other.

On the basis of the network system shown in fig. 1, in 2006, the third generation partnership project (3GPP) passed through the high speed data access (HSPA) evolution research project. The HSPA evolution network architecture is realized based on a PS domain, provides a higher bit rate user rate and shorter call delay for PS domain services, and does not optimize CS domain services in the current 3G system.

In the HSPA evolved network, the RNC functions in the existing 3G system are all centralized in the evolved base station, i.e. NodeB +. Under the HSPA evolution network architecture, NodeB + is directly connected with SGSN, and the interface between the NodeB + and the SGSN is Iu _ PS; and only signaling connection exists between NodeB + and CS domain nodes in CN, such as MSC/VLR, and no user plane connection exists, so NodeB + can not provide services of CS domain alone. Therefore, in order to enable the HSPA evolved network to support the CS domain call service, it is necessary to implement interworking between the HSPA evolved network supporting the PS domain service and the conventional network simultaneously supporting the PS domain and the CS domain service. In the prior art, there are two schemes for interconnecting NodeB + in the HSPA Evolved network and RNC in the conventional network, namely Evolved HSPA UTRAN (Carrier Sharing Evolved HSPA UTRAN) for Sharing a Carrier and Evolved HSPA UTRAN (standard Evolved HSPA UTRAN) for independent carriers.

Figure 3 is a schematic diagram of an evolved HSPA UTRAN network architecture of a conventional standalone carrier. As shown in fig. 3, the evolved HSPA UTRAN network of independent carriers is mainly composed of two parts, UTRAN and CN.

The 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 combining, and radio resource management control.

CN, which is responsible for connection with other networks and communication and management of UE, and the main functional entities include: MSC/VLR, which is a functional node of core network CS domain in HSPA evolution network, NodeB + only has optional Iu _ CS signaling connection with NodeB + and has the main functions of providing call control, mobility management, authentication, encryption and the like of CS domain; SGSN, which is a functional node of the core network PS domain, is connected with UTRAN through Iu _ PS interface, and provides the functions of route forwarding, mobility management, session management, authentication and encryption of PS domain. Under the network architecture, the HSPA evolution network and the traditional network adopt different carriers, NodeB + in the HSPA evolution network is connected through an Iur interface, but no interface exists between the NodeB + and RNC of the traditional network.

Fig. 4 is a schematic diagram of an evolved HSPA TURAN network architecture of a conventional shared carrier. As shown in fig. 4, the network architecture has the same network nodes as the network architecture shown in fig. 3, except that there is an Iur interface between NodeB + and the RNC in the legacy network for interacting some control signaling and data between NodeB + and the RNC.

Under the network architecture shown in fig. 3, when a UE under a NodeB + initiates a CS domain call, since the NodeB + itself cannot directly handle the CS domain call, the NodeB + needs to trigger inter-frequency hard handover of the UE to a conventional network supporting a CS domain service. Inter-frequency hard handover includes two procedures, one is Relocation (Relocation) of the Iu interface. In the prior art, for a certain UE, an RNC directly connected to a core network and controlling all resources of the UE is referred to as a serving RNC of the UE, while an RNC not connected to the core network and providing resources only for the UE is referred to as a free RNC of the UE. And Relocation refers to a procedure of transferring the role of a serving RNC of a certain UE from one RNC to another RNC. Before Relocation, the serving RNC of the UE is called the source RNC (source RNC), and the RNC that will take on the role of the serving RNC is called the target RNC (target RNC). Another procedure is air interface handover, which means that the UE radio link changes, and may be from one sector to another sector or from one cell to another cell. Hard handoffs include air interface handoffs accompanied by relocation of the Iu interface. And the pilot frequency means that the service frequency changes before and after the UE is switched. Since the HSPA evolved network and the conventional network use different carriers under the network architecture shown in fig. 3, the handover is an inter-frequency hard handover.

In the existing standby scenario, because NodeB +, hereinafter abbreviated to NB +, and the MSC have only Iu _ CS signaling connection, that is, control plane connection and no user plane connection, and furthermore, NB + in the standby scenario may not configure a Dedicated Channel (DCH) supporting the conventional CS service, and there is no Iur interface capable of communicating with the RNC of the conventional network, the UE must switch to the RNC of the conventional network to complete the entire CS call. However, in the prior art, the switching process must be completed through the core network, so that the transmission delay of the message is increased virtually, and the service experience of the user is affected.

Disclosure of Invention

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

The embodiment of the invention provides a system for supporting circuit domain services in a high-speed data access evolution network, which can shorten the time delay of CS call establishment.

The technical scheme of the embodiment of the invention is realized as follows:

a method for supporting circuit switched domain, CS, services in a high speed data access, HSPA, evolved network, 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.

A system for supporting CS traffic in an HSPA evolved network, 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.

It can be seen that, with the technical solution of the embodiment of the present invention, in a standby scene, when a UE located under a NodeB + initiates a CS call: NodeB + initiates a relocation request to RNC in the traditional network, RNC carries out radio parameter configuration and relocation preparation according to the relocation request, and informs the NodeB + of a container configured by itself; NodeB + determines to initiate physical layer channel reconfiguration message to 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. Compared with the prior art, the scheme of the embodiment of the invention ensures that a plurality of processes in the pilot frequency hard switching process do not need to be forwarded through a core network by arranging the interface between the NodeB + and the RNC in the traditional network, thereby accelerating the speed of the pilot frequency hard switching and further shortening the time delay of the establishment of the CS call.

Drawings

Fig. 1 is a schematic diagram of a conventional UMTS system.

Fig. 2 is a schematic diagram of a conventional UTRAN.

Figure 3 is a schematic diagram of an evolved HSPA UTRAN network architecture of a conventional standalone carrier.

Figure 4 is a diagram of an existing evolved HSPA UTRAN network architecture sharing a carrier.

FIG. 5 is a flow chart of an embodiment of the method of the present invention.

FIG. 6 is a flowchart illustrating a first preferred embodiment of the method of the present invention.

FIG. 7 is a flowchart illustrating a second preferred embodiment of the method of the present invention.

FIG. 8 is a flowchart illustrating a third preferred embodiment of the method of the present invention.

FIG. 9 is a flowchart illustrating a fifth preferred embodiment of the method of the present invention.

FIG. 10 is a schematic diagram of a system according to an embodiment of the present invention.

FIG. 11 is a block diagram of a preferred embodiment of the system of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail below with reference to the accompanying drawings by way of examples.

In the embodiment of the invention, in order to solve the problems in the prior art, a certain modification is performed on the HSPA evolution network architecture in the existing standby scene, so that the HSPA evolution network architecture can better support the CS service while providing a high-speed data service for a user. Specifically, in the embodiment of the present invention, the HSPA evolved network in the existing standby scene is modified, an interface between the NB + and the RNC in the conventional network is added, and the added interface assists in completing the inter-frequency hard handover procedure, thereby accelerating the inter-frequency hard handover.

The added interface can be only used for doing operations related to mobility of some control planes, and the establishment of user plane load bearing is not involved, so that the influence caused by the added interface is reduced. Since adding interfaces may increase the link budget for NB + and RNC, not involving the user plane makes the link bandwidth unnecessarily large, with less overhead. Of course, the interface may also have user plane functionality.

FIG. 5 is a flow chart of an embodiment of the method of the present invention. As shown in fig. 5, when a UE located under NB + initiates a CS call, the method includes the following steps:

step 501: NB + sends relocation request to RNC, RNC carries out radio parameter configuration and relocation preparation according to received relocation request, and informs NB + of the configured container.

Step 502: and the NB + determines to initiate 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: and the UE performs wireless link reconfiguration according to the information in the received physical layer channel reconfiguration message, accesses the information into the RNC and completes the relocation.

In this embodiment, the interface between NB + and the RNC may be an interface having only a control plane function, or may be an interface having both a control plane function and a user plane function. For example, the interface may be a complete Iur interface or a simplified Iur interface, i.e. only comprising control signaling and no user plane signaling. Of course, the interface may also be a completely new interface. How to arrange the interfaces is well known in the art and is not described here.

Therefore, by adopting the technical scheme of the embodiment of the invention, the interface is arranged between the NB + and the RNC in the traditional network, so that a plurality of processes in the pilot frequency hard switching process do not need to be forwarded through the core network, and the speed of the pilot frequency hard switching is accelerated. The CS call setup delay is caused by the existing CS call delay plus the pilot frequency hard handoff delay, so that the pilot frequency hard handoff speed is increased, and the CS call setup delay is inevitably reduced. The solution according to the invention is further illustrated in detail by the preferred embodiments below:

the preferred embodiment 1

FIG. 6 is a flow chart of a first preferred embodiment of the method of the present invention. In this embodiment, it is assumed that a source RNC of the UE is an NB + in a standby scene in the evolved HSPA UTRAN network, and a target RNC of the UE is an RNC in the UMTS network. Wherein, NB + is connected to the core network through Iu _ CS signaling interface; NB + is connected to the target RNC through a newly added interface, such as an Iur interface. When a UE residing under NB + initiates a CS traffic call, NB + and a target RNC in a UMTS network supporting CS traffic perform inter-frequency hard handover. For convenience of description, the target RNC will be simply referred to as RNC hereinafter. As shown in fig. 6, the method comprises the following steps:

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

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

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

And after the NB + receives the initial direct transfer message from the UE, determining that the service is the CS service according to the indication information carried in the initial direct transfer message. The initial direct transfer message usually uses a bit to identify the service type, for example, 0 is used to represent CS service, 1 is used to represent PS service, and NB + can determine whether the service is CS service by reading the bit.

After the CS service is determined, since NB + itself can not support the CS service, an initial direct transfer message is sent to the MSC in the core network through the Iu _ CS signaling interface between the NB + and the MSC, so as to trigger the switching from the evolved HSPA UTRAN network to the traditional network supporting the CS service.

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

In the subsequent process, the NB + can perform handover from the evolved HSPA UTRAN to the conventional network supporting the CS service, i.e., the UMTS network in this embodiment.

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

The relocation request message in this step carries a transparent container from the active RNC to the target RNC, which includes: an identification of the source RNC, an identification of the target RNC, a list of Radio Access Bearers (RABs) to be established, etc. The RAB list may include: RAB ID, transport layer address, and user plane information, etc.

The RAB, as referred to herein, refers to a logical connection that the MSC or SGSN instructs the UTRAN to establish between the MSC or SGSN and the UE when a user plane connection needs to be established. The established RAB inherits the requirements of the requested UMTS service, such as quality of service, etc. Based on the inheritance requirement of the RAB, the RNC can utilize the core network and the UE to establish the user platform connection. Here, a connection between the RNC and the core network is referred to as an Iu bearer, and a connection between the RNC and the UE is referred to as a Radio Bearer (RB). These bearers each represent a further logical channel, and the mapping between them is done by the RNC. These bearers themselves are mapped to the appropriate transport channels for transmission over different interfaces. A UE may connect to one or more RABs, e.g., a UE connects to two RABs, one for establishing a voice call and the other for establishing a data call. The RNC may use the RAB identifier assigned by the core network to distinguish between different RABs.

In this step, NB + may determine, according to a preset configuration or according to information reported by the UE, to which RNC in the UMTS network a relocation request needs to be sent, that is, determine which RNC assists in processing the CS service of itself, and then send the relocation request to the RNC.

Step 605: after receiving the relocation request, the RNC configures Radio Resource Control (RRC), Radio Link Control (RLC), Medium Access Control (MAC), a mapping relation between a logical channel and a transmission channel and a mapping relation between physical layer resources and the transmission channel according to information content carried in the container, allocates a new temporary mobile user identity (U-RNTI) for the UE, and then sends a relocation response to the NB + to inform the NB + of the configured container established on the RNC and inform the NB + RNC of the U-RNTI allocated for the UE.

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

The physical layer channel reconfiguration message carries related information of the UE, such as a U-RNTI allocated to the UE by the RNC, an information unit of an RB, a physical layer channel information unit, an uplink radio resource information unit, and a downlink radio resource information unit. Each radio bearer information unit, namely the RB information unit, includes an RB identity, an RLC identity, and RB mapping information.

Step 607: the UE reconfigures the wireless link according to the content in the received physical layer channel reconfiguration message, completes the search of a new cell, namely a target NodeB under the RNC, and completes the synchronization with the NodeB.

Step 608: and after the UE is successfully accessed into the RNC, sending a physical layer reconfiguration completion message to the RNC.

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

Step 609: RNC sends relocation complete message to SGSN to inform SGSN of completion of relocation.

The RNC may also send a relocation complete message to the MSC to inform the MSC of the completion of the relocation, if needed.

Step 610: and after receiving the relocation completion message, the SGSN sends a relocation completion response message to the RNC.

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

Step 612 to 613: and carrying out the wireless access bearing establishment of the CS service and the call establishment process of the CS service.

The second preferred embodiment

FIG. 7 is a flowchart of a second preferred embodiment of the method of the present invention. In this embodiment, it is assumed that a source RNC of the UE is an NB + in a standby scene in the evolved HSPA UTRAN network, and a target RNC of the UE is an RNC in the UMTS network. It is assumed that there is no In _ CS signaling connection between NB + and the MSC, but NB + and RNC are connected through a newly added interface, such as the Iur interface. When a UE residing under 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 fig. 7, the method comprises the following steps:

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

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

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

After the CS service is determined, since NB + itself cannot support the CS service, a handover to a conventional network supporting the CS service, that is, a UMTS network in this embodiment is required. In this step, NB + sends a relocation request message to the RNC in the UMTS network via the newly added Iur interface. The relocation request message carries the transparent container from the active RNC to the target RNC, and the information necessary for establishment of the non-access stratum (NAS) Protocol Data Unit (PDU) and the CS connection carried in the initial direct transfer message. Wherein, transparent container includes: the identity of the source RNC, the identity of the target RNC, the list of RABs that need to be established, etc.

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

The initial direct transfer message carries information required by the establishment of the NAS PDU and the CS connection.

Step 704: after receiving the initial direct transfer message, the MSC sends back an SCCP connection confirmation message to the RNC.

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

Steps 706-713 are the same as steps 606-613 and will not be described again.

Preferred embodiment three

FIG. 8 is a flowchart illustrating a third preferred embodiment of the method of the present invention. In this embodiment, it is assumed that a source RNC of the UE is an NB + in a standby scene in the evolved HSPA UTRAN network, and a target RNC of the UE is an RNC in the UMTS network. It is assumed that there is no In _ CS signaling connection between NB + and the MSC, but NB + is connected to the RNC through a newly added interface, such as the Iur interface. When a UE residing under 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 fig. 8, the difference between the preferred embodiment and the second preferred embodiment is only that the Iu bearer between the RNC and the MSC is established at the same time of the radio link bearer establishment, i.e., step 712 shown in fig. 7 is performed before 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 are not described herein again.

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

The fourth preferred embodiment

In the prior art, since the NB + in the standby scenario in the evolved HSPA UTRAN network is not configured with a conventional Dedicated Channel (DCH), the NB + in the standby scenario can only carry CS traffic (CS over HSPA) over a high-speed shared channel. By adding an Iur interface between an NB + and an RNC in a traditional network, the NB + in a Standalone scene can adopt a method for supporting CS services by the NB + in a Carrier Sharing scene in an evolved HSPA UTRAN network in the prior art, CS services or CS + PS services are relocated to the RNC in the traditional network, the NB + is taken as a free RNC for providing resources for UE, the RNC in the traditional network is taken as a service RNC, and the radio resources of the NB +, namely a high-speed shared channel, are utilized to support the CS services. It should be noted that the CS service bearer described in the preferred embodiment can only be provided to the UE supporting CS communication over HSPA channel, and the UE capable of performing CS service only using the conventional DCH channel cannot enjoy this service.

Preferred embodiment five

In the prior art, since the NB + in the standby scenario in the evolved HSPA UTRAN network is not configured with the conventional DCH channel, the NB + in the standby scenario can only carry CS traffic (CS over HSPA) over the high-speed shared channel. In this case, NB + in the standby scenario may add a complete Iu _ CS interface, that is, an Iu _ CS interface including both control plane and user plane functions, to better support CS services of the UE without relocation or handover to the RNC in the legacy network. As with the fourth preferred embodiment, the UEs in this preferred embodiment are limited to UEs that support CS communications over HSPA channels.

FIG. 9 is a flowchart illustrating a fifth preferred embodiment of the method of the present invention. As shown in fig. 9, the method comprises the following steps:

step 901: the UE initiates a CS call and establishes RRC connection with the NB +.

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

Step 903: the MSC sends a command id (command id) message to NB +.

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

Step 904-907: the MSC sets a security mode required for the UE to perform CS communication.

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

After this step, the MSC performs a procedure to retrieve the international mobile subscriber identity (IMEI) of the UE, if necessary.

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

Steps 910 to 914: RAB establishment procedures for the UE and the MSC are performed.

If necessary, after this step, a temporary management mobile identity (TMSI) reallocation procedure is performed.

Step 915-917: ringing, and completing the call establishment process.

Compared with the support mode of the RNC and the NodeB for the CS service in the prior art, the mode described in this embodiment is to combine the functions of the existing RNC and NodeB to the NB +, thereby omitting the signaling interaction process between the existing RNC and NodeB, and the remaining specific implementation steps are the same as those in the prior art and are not described again.

The same procedure as shown In fig. 9 can be used if there is a complete In _ CS interface between NB + and MSC In Carrier Sharing scenario.

Based on the above method, fig. 10 is a schematic diagram of a composition structure of an embodiment of the system of the present invention. As shown in fig. 10, the system includes: 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,

NodeB + is used for initiating a relocation request to RNC after 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;

RNC, used for carrying out wireless parameter configuration and relocation preparation according to relocation request received from NodeB +, and informing the container configured by NodeB + RNC itself;

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

The interface between the NodeB + and the RNC may be an interface having only a control plane function, or may be an interface having both a control plane function and a user plane function. Typically, the interface is an Iur interface.

The system shown in fig. 10 may further include: MSC, used for receiving initial direct-transmitting message from NodeB + and sending SCCP connection confirmation message back to NodeB +; after receiving the SCCP connection acknowledge message, the NodeB + initiates a relocation request to the RNC.

Or, the MSC is configured to receive an initial direct transfer message sent by the RNC after receiving the relocation request message from the NodeB +, and send an SCCP connection acknowledgement message back to the RNC; after receiving the SCCP connection acknowledge message, the RNC sends a relocation response message back to the NodeB +.

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

Of course, those skilled in the art should understand 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 structural diagram of a preferred embodiment of the system of the present invention. Compared with the existing evolved HSPA UTRAN network architecture of independent carriers as shown in fig. 3, the NB + in the preferred embodiment is connected to the RNC in the legacy network through an added Iur interface. For the specific workflow of the preferred embodiment of the system, please refer to the description of the corresponding part of the method, which is not described herein again.

Therefore, by adopting the technical scheme of the embodiment of the invention, the interface is arranged between the NB + and the RNC in the traditional network, so that a plurality of processes in the pilot frequency hard switching process do not need to be forwarded through the core network, the speed of the pilot frequency hard switching is accelerated, and the CS call establishment delay is further reduced.

In summary, the above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

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;

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,

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.