A method, system and device for processing the service in the circuit switching domain

DESCRIPTION

A METHOD, SYSTEM AND DEVICE FOR PROCESSING SERVICE FOR CIRCUIT SWITCHING

TECHNOLOGY FIELD

The present invention relates to the field of mobile communication technologies, and more particularly to a method, system, and device for processing Circuit Switching (CS) service.

BACKGROUND OF THE INVENTION 3.^The Generation (3GPP) specifies that all service flows in a Circuit Switching (CS) domain data plan need to be switched through a Media Gateway (MGW).

FIG. 1 is a schematic view of the service flow in a prior art CS domain data plan. The network system includes a Mobile Switching Center (MSC) and an MGW located on a Network Plane (NC), plane station controllers (e.g., Radio Network Controllers, RNC), and a plurality of plane stations. (e.g. Nodes). Generally, Node, Node, Node2, Node3, Node4, and Node5 are plan stations that communicate directly with User Equipment (UE), and an aggregation plan station (HUB Node) is a plan station used for aggregating. the cascading of lower level nodes. As shown in FIG. 1, solid lines represent physical links, and dashed lines represent service flows in the data plane. As can be seen from Fig. 1, all workflows in the data plan that

<td>are processed by</td><td>Knots</td><td>need</td><td>to be</td><td colspan="2">switched</td>

<td>through MGW.</td><td></td><td></td><td></td><td></td><td></td>

<td>In the prior art,</td><td colspan="2">data exchange</td><td>RNCs</td><td>with</td><td>the</td>

<td colspan="2">devices at CN through</td><td>an interface</td><td>lu e</td><td>exchange</td><td>in</td>

data with the Nodes via a lub interface.

The prior art has at least the following problems. After the data processing form shown in FIG. 1 being adopted, since the MSC needs to process CS data services from all subordinate RNCs, and each RNC needs to process CS data services from all subordinate Nodes, the bandwidth transmission requirements for lub interfaces. and lu are increased. In addition, since the service stream has to be transmitted across a plurality of devices, the transmission delay of the service streams is increased.

WO 2007/069229 discloses the configuration of calls between subscribers at the same transceiver base station by a proxy attached to the transceiver base station and controlled by a base station controller.

WO 2006/126923 An I refers to a telecommunication system, a base radio station and a network radio controller for establishing, launching and controlling local calls in the telecommunications system. The telecommunications system comprises a base network and at least one radio access network, an MSC server, a media center gateway having a point of interconnection to the public switched telecommunications network and at least one radio access gateway for each respective radio access network. At least one local MGW supplied with switching means and geographically separated from the central MGW. The radio access gateway and the MSC server are provided with control logic for establishing and launching local calls on their respective radio access networks using the local MGW as a switch. Local MGW is located at each radio access port at base stations or at an RBS aggregation site, thereby reducing trombone costs and effects.

SUMMARY OF THE INVENTION

The present invention is directed to a method, system and device for processing the service in the CS domain which can reduce bandwidth requirements and reduce the transmission delay of the service stream.

The technical solutions of the present invention are implemented as follows.

According to one aspect of the present invention, a method for CS domain service processing is provided, which includes:

receive a local loopback instruction sent by a base station controller after the base station controller determines that a calling UE and a called UE are served by the same base station or an aggregate base station, switch mode communication between a calling UE and a calling UE for local loopback mode according to the local loopback instruction, wherein switching the mode of communication between a calling UE and a calling UE to local loopback mode according to local loopback instructions comprises:

establish, by the base station or the aggregate base station, an internal transmission channel of a UE called at the base station or the aggregate base station, remove, by the base station or the aggregate base station, a so-called CS channel on a called UE channel established with the base station controller, and establish an internal transmission channel of a calling UE at the base station or aggregate base station, wherein a so-called CS channel on a so-called UE channel is established after the calling UE initiates a CS call and removes according to the local loopback instruction, and establishes, by the base station or aggregate base station, a switching relationship. between the internal transmission channel of a called UE and the internal transmission channel of a calling UE to allow a calling UE and a called UE to communicate in the local loop mode.

According to another aspect of the present invention, a method for processing CS domain service is provided, which includes:

determining, by a base station controller, that a called user equipment, UE, and a called UE are served by the same base station or the same aggregated base station, and sending, by the base station controller, a local loopback instruction to the base station or aggregate base station, to switch the communication mode between a

Calling UE and a UE called for local loopback mode, where switching to communication mode between a calling UE and a UE called for local loopback comprises:

to establish, by the base station or aggregate base station, an internal transmission channel of a UE called at the base station or aggregate base station, to remove, by the base station or aggregate base station, a channel called CS in a channel Called UE established with the base station controller, and establishing an internal transmission channel of a calling UE at the base station or aggregate base station, where the called channel CS on the called UE channel is established after the calling UE initiates a CS call and is removed in accordance with the local loopback instruction, and to establish, by the base station or aggregate base station, a switching relationship. between the called UE internal transmission channel and the calling UE internal transmission channel to allow the calling UE and the called UE to communicate in loopback mode.

According to another aspect of the present invention, a CS domain service processing device is

<td>provided,</td><td colspan="2">which includes: one unit</td><td>in</td><td>reception and</td><td>an</td>

<td>unity of</td><td>switching where</td><td></td><td></td><td></td><td></td>

<td>the unity</td><td>recipient is</td><td>set up</td><td colspan="2">To receive</td><td>an</td>

<td>instruction</td><td>loopback</td><td>place of</td><td>one</td><td>controller</td><td>gives</td>

<td>station of</td><td>base, and</td><td></td><td></td><td></td><td></td>

the switching unit is configured to switch the communication mode between a calling UE and a calling UE for local loopback mode, according to the local loopback instruction, wherein the switching unit comprises: an establishment subunit (210) and a communication subunit, wherein the establishment subunit is configured to establish an internal transmission channel of a called UE on the device, and to remove an established CS call channel with the base station controller. , and establish an internal transmission channel of the calling UE on the device, and establishing a switching relationship between the internal transmission channel of a called UE and the transmission channel of a calling UE, in which the CS calling channel is established after the calling UE initiates a CS call and is removed according to the autoreturn instruction. place, and the communication subunit is configured to allow a calling UE and a called UE to communicate in local loopback mode according to the internal transmission channels established by the establishment subunit.

According to another aspect of the present invention, a system for processing CS domain service is provided, including the above provision and a base station controller, wherein the base station controller is configured to determine that a call user equipment, UE, and a called UE are served by the device, and send a local loopback instruction to the device.

As can be seen, through the technical solutions of the present invention, a base station controller determines that a calling UE and a called UE are served by the same base station or the same aggregated base station, and sends a self-instruction. local return to base station or aggregate base station, and the base station or aggregate base station switches the mode of communication between a calling UE and a called UE to local loopback mode according to the received local loopback instruction.

In comparison with the prior art, in the solutions of the present invention, the mode of communication between a calling UE and a called UE served by the same base station or aggregate base station is switched to local loopback mode, so participation of an MGW is not required, thereby reducing bandwidth requirements and shortening the transmission time of service streams.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic view of service flows in a prior art CS domain data plan;

FIG. 2 is a flow chart of a method according to a first embodiment of the present invention,

FIG. 3 is a flow chart of a method according to a second embodiment of the present invention.

FIG. 4 is a schematic view of data streams before and after switching to local loopback mode according to the second embodiment of the present invention;

FIG. 5 is a flowchart implementation implementation of the non-local loopback mode according to the second embodiment of the present invention;

FIG. 6 is a schematic view of data streams before and after switching to local loopback mode according to the second embodiment of the present invention;

FIG. 7 is a flow chart of a method according to a third embodiment of the present invention.

FIG. 8 is a schematic view of data streams before and after switching to local loopback mode according to the third embodiment of the present invention;

FIG. 9 is a re-switching implementation flowchart for local loopback mode according to the third embodiment of the present invention;

FIG. 10 is a schematic view of data streams before and after recombination to local loopback mode according to the third embodiment of the present invention;

FIG. 11 is a flowchart implementation implementation of the non-local loopback mode according to the third embodiment of the present invention;

FIG. 12 is a schematic view of data streams before and after switching to the non-loopback mode according to the third embodiment of the present invention;

FIG. 13 is a schematic structure view of a system according to an embodiment of the present invention, and

FIG. 14 is a schematic structural view of a device according to an embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

In the present invention, a base station controller determines that a calling UE and a called UE are served by the same base station or the same aggregated base station, and sends a local loopback instruction to the base station or aggregate base station, and the base station or aggregate base station changes the mode of communication between a calling UE and a called UE to local loopback mode according to the received local loopback instruction.

In the following embodiments of the present invention, the solutions of the present invention are described by having a 3GPP defined Node B as an example of the base station, having a 3GPP defined Node B HUB as an example of the aggregate base station, and having a 3GPP-defined RNC as an example of the base station controller. In embodiments of the present invention, the control plane always exists at the lu and lub interfaces, and switching is performed for the data plane only.

In order to fulfill the more understandable objects, technical solutions, and advantages of the present invention, the present invention is described below in more detail with reference to some exemplary embodiments and the accompanying drawings.

FIG. 2 is a flow chart of a method according to the first embodiment of the present invention. As shown in FIG. 2, the method includes the following steps.

In step 201, an RNC determines that a calling UE and a called UE are served by the same NodeB or same NUB HUB, and sends a local loopback instruction to the NodeB or NodeB HUB.

When the calling UE and the calling UE are served by the same NodeB before step 201, the method further includes the following process: The calling UE initiates a call and accesses a CN, and the CN sends an instruction message established on the calling UE channel to the RNC, the RNC establishes a calling UE channel with the CN and a NodeB serving a calling UE. , and instructs NodeB to establish a radio bearer UE call with the calling UE, the CN sends an instruction message established on the called UE channel to the RNC, and the RNC establishes a UE channel called with the CN.

The RNC determines that the calling UE and the called UE are served by the same NodeB according to the calling UE location information performed on an instruction message established on the calling UE channel received from the CN and a transported called UE location information. in an instructional message established on the called UE channel received from the CN. The RNC then instructs the NodeB via an instruction message to establish the called radio bearer UE with the called UE, specified in the instruction message sent by the RNC to the NodeB that a calling UE and a called UE use the mode. loopback for communication, and notifies the HUB Node B of a radio carrier calling UE corresponding to a radio carrier UE.

When the calling UE and the called UE are served by different Nodes but are served by the same Node HUB prior to step 201, the method further includes: the calling UE initiates a call and accesses a CN, and the CN sends an instruction message established on the calling UE channel to the RNC, the RNC establishes a calling UE channel with the CN, and with a Node that serves the calling UE, and instructs the NodeB to establish a radio bearer calling UE with the calling UE, the RNC instructs the Node HUB corresponding to the NodeB that serves the calling UE to establish a calling UE channel with the NodeB that serves the calling UE, the CN sends an instruction message established on the called UE channel to the RNC, and the RNC establishes a calling UE channel with the CN, and instructs a Node that serves the called UE to

<td>establish called.</td><td>one</td><td>EU called support</td><td>in</td><td>radio with the</td><td>HUH</td>

<td colspan="3">The RNC determines the calling UE and</td><td> 0</td><td>EU called</td><td>are</td>

<td>served by</td><td>one</td><td>same HUB NóB according</td><td>with</td><td>the information</td><td>in</td>

<td>location</td><td>of</td><td colspan="2">EU caller carried</td><td>in the message</td><td>in</td>

instruction established on the calling UE channel received from the CN and called UE location information carried in the instruction message established on the called UE channel received from the CN. The RNC then instructs via an instruction message to the Node HUB to establish a called UE channel with the called Node that serves a called UE, specified in the instruction message sent by the RNC to the Node HUB that the calling UE and the UE callers use local loopback mode for communication, and notify HUB NodeB of a calling UE channel corresponding to the called UE channel.

In step 202, the NodeB or HUB NodeB switches the mode of communication between the calling UE and the called UE to the local loopback mode according to the local loopback instruction received.

When the calling UE and the calling UE are serviced by the same NodeB, this step can be specifically implemented as follows: NodeB establishes an internal UE transmission channel called on NodeB, NodeB removes a CS calling channel on a calling UE channel established with RNC, and establishes a calling UE internal transmission channel on NodeB, NodeB establishes a relationship. switching between the called UE internal transmission channel and the calling UE internal transmission channel, i.e. connects the called UE internal transmission channel and the calling UE internal transmission channel to form a channel, and allowing the calling UE and the called UE to communicate in local loopback mode.

When the calling UE and the calling UE are served by different Nodes but are served by the same Node HUB, this step can be implemented specifically as follows: The Node HUB establishes an internal UE transmission channel called on the Node HUB, the Node HUB removes a CS calling channel on a calling UE channel established with the RNC, and establishes a calling UE internal transmission channel on the Node HUB. HUB Node B establishes a switching relationship between the calling UE internal transmission channel and the calling UE internal transmission channel, ie connects the called UE internal transmission channel and the calling UE internal transmission channel to form a channel, and allows the calling UE and the called UE to communicate in local loopback mode.

As can be seen from the technical solutions of the embodiment of the present invention, when UEs at both ends of the CS call are served by the same RNC, it is determined whether the two UEs are located within the service coverage of a same Node or same HUB NoB, and if one of the conditions is met, the two UEs served by the same RNC are switched to a local switching mode, that is, the local loopback mode. If one of the UEs is moved later, the switching mode may also be reset.

The technical solutions of the present invention are described in more detail below by means of other embodiments.

FIG. 3 is a flow chart of a method according to a second embodiment of the present invention. In this embodiment, a calling UE and a called UE are served by the same NodeB. The calling UE accesses a NOB3 shown in Fig. 1, and also the called UE accesses the NOB3 shown in FIG. 1. An RNC determines that the calling UE and the called UE may implement local loopback, and when establishing a radio bearer calling UE, the RNC specifies in a radio link establishment request sent to Node3 that the calling UE and the Called UEs use local loop mode for communication. As shown in FIG. 3, the method includes the following steps.

At step 301, the calling UE initiates a CS call and accesses a CN, and the CN sends an instruction message established on the calling UE channel to the RNC.

In this step, the CN sends an instruction message established on the call channel to the RNC, and a calling UE channel is established between the RNC and the CN, including a 3.4K signaling channel in the control plane and a CS channel in the plane. of data.

The instruction message established on the calling UE channel carries a calling UE ID, configured to identify location information of the calling UE, and the RNC receives and stores the calling UE location information.

At step 302 the RNC sends an instruction message established on the radio bearer calling UE channel to NodeB.

In this step, the RNC sends an instruction message established on the radio bearer calling UE channel to Node B serving the calling UE and the called UE, that is, Node B3 as described in this embodiment. Upon receiving the message, NodeB establishes a calling UE channel with the RNC, including a 3.4K signaling channel in the control plane and a CS channel in the data plane, and establishes a radio bearer calling UE with the calling UE. .

At step 303, Node B returns a response message established on the calling radio bearer UE channel to the RNC.

At step 304, the RNC returns an established message on the calling UE channel to the CN.

answer

In step 305, established on the CN sends a calling UE channel message to the RNC.

of instruction

In this step, the CN sends a message established on the calling UE channel to the instruction RNC and a

The calling UE is established between the RNC and the CN, including a 3.4K signaling channel in the control plane and a CS channel in the data plane.

The instruction message established on the called UE channel carries a calling UE ID, configured to identify called UE location information, and the RNC receives and stores the calling UE location information.

<td>In step 306,</td><td>the RNC</td><td>determines</td><td>why</td><td>HUH</td><td>caller and</td><td>the UE</td>

<td>called may</td><td>use</td><td>the mode of</td><td>self-</td><td colspan="2">local return</td><td>for</td>

<td>to communicate.</td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>In this step,</td><td>the RNC</td><td>determines</td><td>why</td><td>HUH</td><td>caller and</td><td>the UE</td>

Callers are served by the same Node according to the stored location information of the calling UE and the called UE, and thus determines which calling party and the called UE can use local loopback mode to communicate.

In steps 307 to 308, the RNC sends an instruction message established on the UE channel called radio support to Node B, and specifies in the message that the local loopback mode is used to communicate and specifies the calling radio support UE. corresponding with the UE called radio carrier, and Node B establishes the local loopback mode as the calling UE and called UE communication mode.

In this step, the RNC sends an instruction message established on the UE channel called radio bearer to NodeB, prompting NodeB to establish a radio bearer calling UE with the called UE. NodeB establishes a 3.4K signaling channel for the RNC for the called UE, but does not establish any CS channel, and instead establishes an internal transmission channel for the called UE. NodeB then removes a calling UE UE channel between NodeB and RNC and establishes an internal transmission channel of the calling UE and establishes a switching relationship between the internal transmission channel of the calling UE and the internal transmission channel of the calling node. Called UE, that is, connects the calling UE internal transmission channel and the called UE internal transmission channel to form a channel.

At step 309, NodeB returns a response message established on the UE channel called radio support for the RNC.

At step 310, the RNC returns a response message established on the UE channel called radio support for the CN.

Following the above process, the calling UE and the called UE can communicate in local loopback mode.

FIG. 4 is a schematic view of data streams before and after switching to local loopback mode according to the second embodiment of the present invention. As shown in FIG. 4, a thin line represents a 3.4K signaling channel, and a thick line represents a CS channel. It can be seen that the solutions of the present invention are directed only to the data plane, so that, before and after switching, the 3.4K signaling channel does not change, but the CS channel changes after switching, and Service streams sent from the calling UE and the calling UE are transmitted to the peer end through NodeB, without requiring the participation of an RNC or an MGW.

Based on the embodiment shown in FIG. 3, at a time when the calling UE or the called UE is moved out of the Node3 service coverage and enters the service coverage of a new Node, if the new NodeB and Node3 are served by different HUB Nodes, the RNC , while deleting an original radio connection for the moved UE and establishing a new radio connection, you need to send a radio link reconfiguration message to NOB3 to ask NOB3 to establish a radio support link from an EU CS channel that is still resident in the NOB3 service coverage to an RNC channel, ie switch EU resident communication mode to non-local loopback mode. FIG. 5 is a flow chart of the implementation of switching to non-local loopback mode according to the second embodiment of the present invention. As shown in FIG. 5, the process includes the following steps.

In steps 501 to 502, the RNC sends a moved UE radio bearer delete message to NodeB, and Node deletes a radio carrier corresponding to the moved UE, and returns a radio bearer delete response message from the NodeB. UE moved to RNC.

In steps 503 to 504, the RNC determines that the UE resident mode of communication is the local loopback mode, sends a UE resident radio carrier reconfiguration message to Node B, and specifies that it switches to NodeB mode. non-local loopback.

In step 505, Node B switches the UE resident communication mode from local loopback mode to nonlocal loopback mode, excludes the internal transmission channel, and establishes a CS channel between the UE resident and the RNC.

At step 506, Node B sends a reconfiguration message from the UE resident radio bearer response to the RNC.

FIG. 6 is a schematic view of data streams before and after switching to non-local loopback mode according to the second embodiment of the present invention. As shown in FIG. 6, a thin line represents a 3.4K signaling channel, and a thick line represents a CS channel. It can be seen that upon switching, the EU resident communicates via the RNC according to the existing method.

FIGs. 3 to 6 introduce a process for implementing the solutions of the present invention when the calling UE and the called UE are served by the same Node B. A process for implementing the solutions of the present invention when the calling UE and the called UE are served by different Nodes but are served by the same HUB Node B is described below by a third embodiment.

FIG. 7 is a flow chart of a method according to a third embodiment of the present invention. In this embodiment, a calling UE and a called UE are served by the same HUB Node B. The calling UE accesses a NOB4 shown in FIG. 1, and the called UE accesses a NOB5 shown in FIG. 1. An RNC determines that the calling UE and the called UE can implement local loopback, and when establishing a radio bearer calling UE, the RNC specifies in a broadcast channel configuration message sent to the HUB NodeB that the calling UE and The called UE uses local loop mode to communicate. As shown in FIG. 7, the method includes the following steps.

At step 701, the calling UE initiates a CS call and accesses the CN, and the CN sends an instruction message established on the calling UE channel to the RNC.

In this step, the CN sends an instruction message established on the calling UE channel to the RNC, and a calling UE channel is established between the RNC and the CN, including a 3.4K signaling channel in the control plane and a CS channel in the data plan.

The instruction message established on the calling UE channel carries a calling UE ID, configured to identify location information for the calling UE, and the RNC receives and stores the calling UE location information.

At step 702, the RNC sends an instruction message established by the calling UE radio carrier to Node 4.

In this step, the RNC sends the instruction message established by the calling UE radio carrier to Node B serving the calling UE, that is, Node 4 as described in this embodiment. Upon receiving the message, Node 4 establishes a radio bearer calling UE with the calling UE.

At step 703, Node 4 returns a response message established by the calling UE radio carrier to the RNC.

At step 704, the RNC returns a response message established by the calling UE channel to the CN.

In steps 705 through 706, the RNC sends an instruction message established by the calling UE channel to the HUB NodeB, and the HUB NodeB establishes a calling UE channel with the RNC and NodeB4, and returns a response message established by the calling node. calling UE channel to the RNC.

In step 707, the CN sends an instruction message established by the calling channel UE to the RNC.

In this step, the CN sends an instruction message established by the called UE channel to the RNC, and a called UE channel is established between the RNC and CN, including a 3.4K signaling channel in the control plane and a CS channel. in the data plane.

The instruction message established by the called UE channel carries a called UE ID configured to identify location information of the called UE, and the RNC receives and stores the location information of the called UE.

At step 708, the RNC sends an instruction message established by the called UE radio carrier to the N6B5.

At step 709, NodeB5 establishes a called UE radio carrier with the called UE, and returns a response message established by the called UE radio carrier for the RNC.

At step 710, the RNC determines that the calling UE and the called UE can use local loopback mode.

In this step, the RNC determines that the calling UE and the called UE are served by the same HUB NodeB according to the calling UE or calling UE's pre-stored location information, and thus determines that the calling UE and the called UE can use local loop mode to communicate.

In step 711, the RNC sends an instruction message established by the calling UE channel to the HUB Node B, and specifies in the message that the local loopback mode is used to communicate and specifies a calling UE transmission link corresponding to a called UE transmission link, that is, the CS channel.

In this step, the NodeB HUB establishes a called UE channel with Node5 and establishes a 3.4K signaling channel between the NodeB HUB and the RNC for the called UE, but does not establish any CS channel between the NodeB HUB and the RNC.

In step 712, the HUB Node B establishes a loopback transmission channel, and excludes a transmission link between the calling UE and the RNC.

In this step, the Node HUB establishes a called UE internal transmission channel, removes a CS channel from the calling UE between the Node HUB and the RNC and establishes a calling UE internal transmission channel, and establishes a switching relationship between the channel calling UE internal transmission channel and the called UE internal transmission channel.

In step 713, the HUB Node B returns a response message established by the called UE channel to the RNC.

In step 714, the RNC returns a response message established by the called UE channel to the CN.

Following the above process, the calling UE and the called UE can communicate in local loopback mode.

FIG. 8 is a schematic view of data streams before and after switching to local loopback mode according to the third embodiment of the present invention. As shown in FIG. 8, a thin line represents a 3.4K signaling channel, and a thick line represents a CS channel. It can be seen that after switching, service streams sent from the calling UE and the called UE are transmitted to the peer end via the HUB Node B, without the need for an RNC or MGW to participate.

Based on the embodiment shown in FIG. 8, it is assumed that each time the called UE is moved out of the NOB5 service cover, and enters the NOB3 service cover shown in FIG. 1. Since NBB3 and NBB4 are still served by the same NBB HUB, the RNC needs to reconfigure a local loopback relationship while deleting an original UE channel for the called UE and establishing a new UE channel. FIG. 9th is a flowchart of implementation of switching to local loopback mode according to the third embodiment of the present invention. As shown in FIG. 9, the process includes the following steps.

In steps 901 to 902, the RNC sends a called UE radio bearer exclusion reply message to Node5, and Node5 deletes a radio bearer corresponding to the called UE, and returns a UE bearer exclusion reply message. UE radio called to the RNC.

At steps 903-904, the RNC sends a called UE channel delete message to the Node HUB, and the Node HUB performs a corresponding operation, and returns a called UE channel delete reply message to the RNC.

Steps 905 to 910 are similar to steps 708 to 713 shown in FIG. 7, except that the step of eliminating the transmission link between the called UE and the RNC as shown in step 712 need not be performed at step 909. The remaining steps are substantially the same as shown in FIG. 7, so that the details will not be described here again.

FIG. 10 is a schematic view of the data streams before and after recommitting to local loopback mode according to the third embodiment of the present invention. As shown in FIG. 10, a thin line represents a 3.4K signaling channel, and a thick line represents a CS channel. It can be seen that the communication mode is the local loopback mode before and after switching, and the difference is that the node serving the called UE is changed.

It is assumed that at the same time, the called UE is continuously moved out of the NodeB service cover, and enters the NodeB service cover shown in FIG. 1. Since NodeBl and NodeB are served by different NodeB HUBs, the RNC needs to switch the communication mode from local loopback mode to nonlocal loopback mode, while excluding an original UE channel for Called and establishes a new EU channel. FIG. 11 is a flowchart of the implementation implementation for nonlocal loopback mode according to the third embodiment of the present invention. As shown in FIG. 11, the process includes the following steps.

In steps 1101 to 1102, the RNC sends a called UE radio bearer delete message to Node3 and NBO3 deletes a radio carrier corresponding to the called UE, and returns a UE radio bearer delete reply message. called to the RNC.

In steps 1103 to 1104, the RNC sends a called UE channel delete message to the Node HUB and the Node HUB performs a corresponding operation, and returns a called UE channel delete response message to the RNC.

In steps 1105 to 1106, the RNC sends an instruction message established on the called radio bearer in the called UE to NodeBl and NodeB establishes a called UE radio bearer with the called UE, and returns a reply message established on the called UE bearer. radio in the UE called to the RNC.

In steps 1107 through 1108, the RNC determines that the calling UE and the called UE can no longer use local loopback mode to communicate, but the calling UE is still set to local loopback mode, and therefore sends a caller channel reconfiguration message from the calling UE to the HUB NodeB, and specifies that the switch to nonlocal autoreturn mode.

At step 1109, the HUB Node B deletes the original internal transmission channel and restores the CS channel between the calling UE and the RNC.

In step 1110, the HUB Node B returns a reset message on the calling UE channel to the RNC.

FIG. 12 is a schematic view of data streams before and after switching to non-local loopback mode according to the third embodiment of the present invention. As shown in FIG. 12, a thin line represents a 3.4K signaling channel, and a thick line represents a CS channel. It can be seen that since NodeBl and NodeB are served by different NodeB HUBs, the mode of communication between the calling UE and the calling UE after switching is the existing local loopback mode, and the service flows between the calling UE and the called UE still need to be transmitted via an MGW.

It can be seen from the above introduction that through the technical solutions of the embodiments of the present invention, the mode of communication between the calling UE and the called UE which are served by the same NodeB or even HUB NodeB can be switched to the same. local loopback mode, thereby decreasing bandwidth requirements and shortening the transmission delay of service streams.

It is to be understood that the above embodiments are described by way of example only, but are not intended to limit the technical solutions of the present invention. For example, the above embodiments are only described by way of an example where the called UE is moved, but those skilled in the art can easily understand from the foregoing description that the process is similar when the calling UE is moved, as soon as The details will not be described here again.

It should be noted that by means of the technical solutions of the embodiments of the present invention, adaptive tuning has to be performed by some specific implementations of existing CS domain services. Since CS domain services are generally voice services, voice services are described below as an example.

Since Node B does not have a voice playback function, that is, the one-touch ring playback function, the voice playback function is implemented by the CN in the prior art. This means that when the calling UE initially establishes a connection, a CS voice channel is inevitably established to the CN. After the technical solutions of the embodiments of the present invention are used, the CN still reproduces the ringback for the calling UE, and after the NodeB or HUB NodeB switches the mode of communication between the calling UE and the called UE for the caller. Local loopback mode, the established CS voice channel is released, so normal communication is performed in the local loopback mode.

In practical applications, it is generally necessary that the adaptive multi-rates (AMRS) of two UEs capable of implementing local loopbacks correspond to each other. Since the NodeB cannot obtain the UEs AMRS directly in the embodiments of the present invention, after determining that the calling UE and the called UE are served by the same NodeB or same NodeB HUB according to a message sent from The NCB needs to further determine whether the calling UE and the calling UE AMRS match each other, and sends the local loopback instruction to the NodeB or Node HUB if the calling UE and calling UE AMRS match one to the other. another, if the calling UE and the calling UE AMRS do not match each other, non-local loopback mode is adopted to communicate.

In the above embodiments, the RNC may continue to carry voice packet encoding / decoding parameters in the calling UE radio link established instruction message or called UE radio link established instruction message sent to the Node B serves the calling UE or the called UE while communicating in the local loop mode, the Node serving the calling UE or the called UE parses a network protocol (FP) uplink packet carrying CS voice, decrypts the uplink CS voice packet according to the encoded / decoded voice packet parameters, and converts the uplink CS voice packet to a downlink FP packet format, and to the downlink FP packet obtained after conversion, The downlink converted CS voice packet is encrypted according to the parameters of the voice coding / decoding pact, and then sent out via an air interface.

Furthermore, the technical solutions of the embodiments of the present invention may comprise a smooth transfer function. For example, when the RNC determines that all calls from the calling UE or calling UE are connected to the same NodeB, the RNC instructs the NodeB to perform a smooth transfer function, the selected NodeB from different soft transfer links, and each time selects an uplink FP packet on a smooth transfer link having the best

<td>quality</td><td>of</td><td>signal from</td><td colspan="2">more</td><td>than one</td><td>Link</td>

<td>received</td><td>in</td><td>smooth transfer</td><td>r</td><td>and</td><td>converts and</td><td>send the</td>

<td>FP package</td><td>in</td><td>uplink,</td><td>if</td><td>O</td><td>loopback</td><td>location is</td>

<td colspan="2">implemented</td><td>by NodeB, the package</td><td>FP</td><td>is</td><td colspan="2">processed accordingly</td>

with the encoding / decoding form described above and then transmitted, and if local loopback is not implemented by Node B, the selected FP packet is sent to a lub interface according to an existing process. When the RNC determines that smooth handoff occurs on a plurality of Nodes, but the Nodes are served by the same Node HUB, the RNC instructs each Node to operate in the same way as when the RNC determines that all calls from the calling UE or the UE are connected to the same NodeB, and instructs the NodeB HUB to complete smooth transfer link processing between

Nodes The operation of specifically includes smooth transfer binding the following process: 0 HUB Node selects an uplink FP packet on a smooth handoff link having the best signal quality of smooth handoff links that are connected to different Nodes but belong to the same UE, performs CS voice decryption packets, converts the FP packet uplink in a downlink FP packet format, and then auto-returns the FP packet for a one-node link for a downlink process. Since smooth transfer technology belongs to the prior art, the details will not be described further.

Accordingly, FIG. 13 is a schematic view of the structure of a system according to an embodiment of the present invention, and FIG. 14 is a schematic view of the structure of a device according to an embodiment of the present invention. In both embodiments, description is also given by taking a 3GPP-defined NodeB as an example of the aggregation base station, and having a 3GPP-defined NodeB HUB as an example of the aggregation base station, and having a 3GPP-defined RNC as an example of the base station controller.

FIG. 13 is a schematic view of the structure of a system according to an embodiment of the present invention. As shown in FIG. 13, the system includes an RNC and a NodeB, or an RNC and a NodeB HUB.

RNC is configured to determine that a calling UE and a called UE are served by the same NodeB or same HUB Node, and send a local loopback instruction to the NodeB or NodeB HUB.

NodeB or HUB NodeB is configured to switch the communication mode between the calling UE and the calling UE to local loopback mode according to the received local loopback instruction.

The system may also include a CN.

CN is configured to send an instruction message established on the calling UE channel and an instruction message established on the calling UE channel to the RNC when the calling UE initiates a call. 0 RNC determines that the calling UE and the called UE are served by the same NodeB or same HUB NodeB according to the calling UE location information performed on the instruction message established on the calling UE channel and the called UE location information carried in the instruction message established on the called UE channel.

The RNC can be further configured to determine if the calling UE and called UE AMRS coincide with each other, and send the local loopback instruction to the NodeB or HUB NodeB, if the calling UE or called UE AMRS match one another. with the other one.

FIG. 14 is a schematic view of the structure of a device according to an embodiment of the present invention. As shown in FIG. 14, the device includes a receiver unit 10 and a switching unit 20.

Receiver unit 10 is configured to receive a local loopback instruction from an RNC.

Switching unit 20 is configured to switch the communication mode between a calling UE and a called UE to local loopback mode according to the local loopback instruction.

The receiving unit 10 further includes: a first receiving sub-unit 110 and a second receiving sub-unit 120.

The first receive subunit 110 is configured to receive an established RNC calling UE radio support instruction message, and establish a calling UE radio support with the calling UE according to the instruction message.

The second receive subunit 120 is configured to receive an established UE radio support instruction message called from the RNC, and establish a calling UE radio support with the UE called according to the message instruction, wherein the message The instruction manual carries the local loopback instruction, and information from the calling UE radio carrier corresponding to the called UE radio carrier.

Or, the first receiving subunit 110 is configured to receive an instruction message established on the RNC calling UE channel, and to establish a calling UE channel with a Node B serving the calling UE according to the instruction message.

The second receive subunit 120 is configured to receive an instructional message established on the channel of the

UE called from the RNC, and establish a calling UE channel with a Node B serving the calling UE according to the instruction message, wherein the instruction message carries the local loopback instruction, and UE call channel information corresponding to the calling UE channel.

The switching unit 20 further comprises: an established subunit 210 and a communication subunit 220.

The established subunit 210 is configured to establish a calling UE internal transmission channel on the device, and remove a previously established CS calling channel with the RNC, and establish a calling UE internal transmission channel on the device, and establish a relationship. between the called UE internal transmission channel and the calling UE internal transmission channel.

The communication subunit 220 is configured to allow the calling UE and the called UE to communicate in local loopback mode according to the internal transmission channels established by the established subunit 210.

When the device is a NodeB, the receiving unit 10 further includes: a third receive subunit 130, configured for when the calling UE or the called UE is moved out of NodeB service coverage, delete a radio carrier corresponding to the UE moved according to an instruction received from the RNC, and instruct the switch unit 20 to switch the local resident UE communication mode to the non-local loopback mode, the established subunit 210 establishes a CS channel between NodeB and RNC, and communication subunit 220 communicates in nonlocal loopback mode.

When the device is a NoB HUB, the receiving unit 10 further includes: a third receiving sub-unit 130 and a fourth receiving sub-unit 140. The third receive sub-unit 130 is configured for when the calling UE or the called UE is moved to service coverage of a new NodeB, and the calling UE and the called UE are still served by the same HUB NodeB after the movement, instructs a node corresponding to the moved UE to delete a radio carrier corresponding to the moved UE according to an instruction received from the RNC, and delete a CS channel with the node corresponding to the moved UE, and receives a new local loopback instruction sent by the RNC, and the switch unit 20 restores a local loopback communication mode between the calling UE and the called UE for communication. The fourth receive subunit 140 is configured for when the calling UE or the called UE is moved to the service coverage of a new NodeB, and the calling UE and the calling UE are located within the service coverage of different HUB Nodes after the movement instructs a moved UE-corresponding NodeB to delete a moved UE-corresponding radio carrier according to an instruction received from the RNC and excludes a CS channel with the moved UE-corresponding NodeB, and instructs the switch unit 20 to switch the local resident UE communication mode to the non-local autoreturn mode, the established subunit 210 establishes a CS channel between the corresponding node NB to the resident UE and the RNC, and the communication subunit 220 communicates in nonlocal loopback mode.

For the specific workflows of the system and device embodiments shown in Figs. 13 and 14, reference is made to the description in the method portion, and the details will not be described here again.

Based on the above description, using the technical solutions of the embodiments of the present invention, the transmission bandwidth requirements for the lub and lu interfaces are reduced and the data transmission delay is shortened. In addition, the ideas of embodiments of the present invention are equally applicable to Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) or similar scenarios.

Through descriptions of the above embodiments, those skilled in the art can understand that the present invention may be implemented only by hardware or software and a required universal hardware platform. Based on such understandings, the technical solution of the present invention may be realized in the form of a software product. 0 The software product may be stored on a nonvolatile storage medium, which may be a Compact Read-Only Memory Disk (CD-ROM), a USB flash drive, or a removable hard disk. The software product includes a series of instructions that enable a computer device (personal computer, server, or network device) to perform the methods provided in the embodiments of the present invention.

Although the present invention has been described by various exemplary embodiments, the invention is not limited to such embodiments. Any modification, equivalent substitution or improvement made without departing from the principle of the present invention must fall within the scope of the present invention as defined by the appended claims.