KR100390405B1 - method for controlling interface between RNC and NodeB in UMTS - Google Patents

Abstract

The present invention relates to the next generation mobile communication, and more particularly, in a basic structure of a universal mobile telecommunication system (hereinafter, referred to as UMTS), a base station in a UTS Terrestrial Radio Access Network (hereinafter, referred to as UTRAN). The present invention relates to a method for more effectively operating an interface implemented between a NodeB and a control station (RNC).

On the other hand, the present invention provides a method for more effectively operating the interface between the RNC-RRC and the NodeB-PHY implemented differently without modifying the protocol hierarchy structure for the air interface of the existing UMTS.

Description

Method for controlling interface between RNC and NodeB in UMTS in general mobile communication system

The present invention relates to the next generation mobile communication, and more particularly, to a method of more effectively operating an interface implemented between a base station (NodeB) and a control station (RNC) in the UTRAN in the basic structure of UMTS.

In general, the UMTS structure includes a user equipment (hereinafter referred to as UE) 30, a UTRAN 20, and a core network 10 (hereinafter referred to as CN) 10, which is illustrated in FIG. 1. Shown in

FIG. 2 is a block diagram showing the connection between CN 10 and UTRAN 20 in the basic structure of UMTS and the basic structure of UTRAN 20. The UTRAN 20 is connected to CN 10 via a logical interface called Iu. It consists of several Radio Network Subsystems (hereinafter referred to as RNS) (21, 22) connected to.

One RNS 21 or 22 is one Radio Network Controller (hereinafter abbreviated as RNC) 21a or 22a and one or more logical nodes 21b, 21c, 22b, 22c. It is composed of Each logical node (hereinafter abbreviated as NodeB) 21b, 21c, 22b, 22c is responsible for radio transmissions with several UEs 30 located within its service area, and NodeBs 21b, 21c, 22b, 22c It is connected to the RNC 21a or 22a in its RNS 21 or 22 through an interface called Iub.

The NodeBs 21b, 21c, 22b, and 22c may support Frequency Division Duplex (FDD) and Time Division Duplex (TDD) modes, and may also support dual mode operation including these two modes. Can be.

The RNC 21a or 22a is responsible for controlling the use and integrity of radio resources, and is responsible for handover requiring signal processing to various UEs, and different NodeBs 21b, 21c, 22b, and 22c. It consists of combining / separating functional blocks to support large-scale diversity.

Also within the UTRAN 20 each RNC 21a or 22a of different RNS 21, 22 is connected via a logical interface called Iur.

The air interface between these system components (UE and UTRAN) is basically layered from upper layer to upper layer layer, third layer layer, second layer layer and first layer layer protocol as shown in FIG. 3.

The lowest of the sub-layers belonging to the third layer is a radio resource control layer (hereinafter referred to as RRC), and the second layer is a radio link control sub-layer. (Hereinafter, abbreviated as RLC) and a medium access control sub-layer (hereinafter, abbreviated as MAC). In addition, the first layer is a physical layer (hereinafter, abbreviated as PHY).

The RRC controls the logical connection of the lower layers providing the service selected in the upper layer. To this end, RRC and each lower layer (RLC, MAC, and PHY) are connected to a Control-Service Access Point (C-SAP), and RRC control is performed through several primitives (C-SAP). by exchanging primitives).

Among the RRC control, the primitive communication procedure for conventional PHY control is shown in FIG. 4.

In the above-described conventional UMTS structure and protocol layering structure for a radio interface, each RNC 21a, 22a of the components of the UTRAN 20 has an RRC (hereinafter referred to as RNC-RRC) 50 in the protocol layer. The NodeBs 21b, 21c, 22b, and 22c correspond to the PHY 40 (hereinafter referred to as NodeB-PHY) 40.

The RNC-RRC 50 controls the NodeB-PHY 40 to provide information transfer services to higher layers including the MAC, and the RNC-RRC 50 controls from the NodeB-PHY 40. Receive a response.

More specifically, referring to FIG. 4, first, the RNC-RRC 50 transmits a control primitive and a CPHY-Primitive for requesting a status report for the control of the NodeB-PHY 40 (S1).

The NodeB-PHY 40 transmits the CPHY-Primitive, which is a control and status reporting primitive, to the RNC-RRC 50 and reports its status to the RNC-RRC 50 (S2).

However, the conventional primitive communication between the RNC-RRC and the NodeB-PHY is defined as an abstract concept, and specific rules have not been determined yet.

Therefore, when the manufacturer of the RNC is different from the manufacturer of the NodeB, the implementation method is different between the manufacturers may not be compatible with the control of the NodeB-PHY by the RNC-RRC.

In this case, the interface between the RNC and the NodeB may be impossible. As an alternative, the modification of the protocol hierarchy for the air interface of the existing UMTS is necessary.

SUMMARY OF THE INVENTION An object of the present invention has been made in view of the above, and provides a method for more effectively operating an Iub interface between RNC-RRC and NodeB-PHY implemented differently without modifying a protocol hierarchy for a conventional UMTS air interface. do.

In order to achieve the above object, a characteristic of the interface operation method between RNC and NodeB of UMTS is that in UMTS including UTRAN and UE that are air interfaced by a protocol having a hierarchical structure of PHY, MAC, RLC, and RRC. In the UTRAN, converting each request primitive according to its control type into a NodeB Application Protocol (hereinafter abbreviated as NBAP) request message corresponding to the primitive, and the converted NBAP Converting a request message into a request primitive suitable for the PHY control and forwarding the request primitive to the PHY; converting the response primitive to the PHY received by the request primitive into a NBAP response message type corresponding to the primitive; Convert the converted NBAP response message into a response primitive suitable for the PHY control request. And a step of transmission by the RRC.

Advantageously, the RRC converts each request primitive into a corresponding NBAP request message corresponding to each corresponding request for radio resource allocation, reconfiguration, and release, and forwards the request to the PHY. The response primitive is converted into each corresponding NBAP response message and forwarded to the RRC.

In addition, the RRC converts each request primitive into a corresponding NBAP request message corresponding to the corresponding NBAP request message for each control on radio link establishment, resetting, and release, and transmits each response primitive for each control request. The NBAP response message is converted into the corresponding NBAP response message and transmitted to the RRC.

In addition, the RRC converts the request primitive into a corresponding NBAP request message to the PHY to measure the quality of the PHY, and the PHY converts the response primitive to notify the quality measurement result into a corresponding NBAP response message. Convert and forward to the RRC.

Another feature of the method of operating the interface between the RNC and the NodeB of the UMTS according to the present invention for achieving the above object, UTRAN and UE that is air interfaced by a protocol having a hierarchy of PHY, MAC, RLC, and RRC from the bottom In the UMTS comprising: converting each notification primitive in the UTRAN for the PHY to notify its status in the form of an NBAP notification message corresponding to the primitive, and converts the converted NBAP notification message to the RRC notification Converting to appropriate notification primitives and forwarding them to the RRC.

Here, when the PHY has a service error and a synchronization error, the PHY converts a notification primitive for notifying the RRC to an NBAP message and delivers the notification primitive to the RRC.

1 is a block diagram showing the basic structure of a UMTS.

Figure 2 is a block diagram showing the basic structure of UTRAN and the connection of the core network (CN) and UTRAN in the basic structure of UMTS.

3 is a block diagram illustrating a protocol layering structure for a radio interface of a user equipment (UE) or UTRAN in the basic structure of UMTS.

4 is a flowchart illustrating a primitive communication procedure for conventional physical layer control.

5 is a flowchart illustrating a primitive communication procedure for controlling physical layer of the present invention.

* Description of the symbols for the main parts of the drawings *

40: NodeB-PHY 50: RNC-RRC

60: NodeB 70: RNC

Hereinafter, a preferred embodiment of a method for operating an interface between an RNC and a NodeB of a UMTS according to the present invention will be described with reference to the accompanying drawings.

In the present invention, an ambiguous Iub interface between RNC-RRC and NodeB-PHY is newly defined.

In other words, in the present invention, the RNC-RRC and the NodeB-PHY communicate with each other using NBAP, which is an application protocol for its NodeB.

NBAP utilized in the present invention is responsible for call distribution between RNC and NodeB, system information broadcasting, request / complete / release of dedicated resources for NodeB, and management of logical resources.

5 is a flowchart illustrating a primitive communication procedure for controlling physical layer of the present invention.

Referring to FIG. 5, the RNC-RRC 50 transmits a CPHY-Primitive to the RNC-NBAP 70 for controlling the NodeB-PHY 40 (S10).

After receiving the CPHY-Primitive, the RNC-NBAP 70 is driven, and then the RNC-NBAP 70 converts the received CPHY-Primitive into an NBAP message and sends it to the opposite NodeB-NBAP 60 (S20).

The NodeB-NBAP 60 receiving the NBAP message from the RNC side 50, 70 converts the received message back to CPHY-Primitive and sends it to the NodeB-PHY 40 (S30).

Eventually, the NodeB-PHY 40, which has received the CPHY-Primitive from the RNC-RRC 50, drives its NodeB-NBAP 60 and sends a response to the received CPHY-Primitive to the RNC-RRC 50. (S40 to S60).

In more detail, the NodeB-PHY 40 transmits its CPHY-Primitive to the NodeB-NBAP 60 in response to the CPHY-Primitive for its control (S40).

The NodeB-NBAP 60 receiving the CPHY-Primitive is driven, and then the NodeB-NBAP 60 converts the received CPHY-Primitive into an NBAP message and sends it to the counterpart RNC-NBAP 70 (S50).

The RNC-NBAP 70, which has received the NBAP message from the NodeB side 40, 60, converts the received message back to CPHY-Primitive and sends it to the RNC-PHY 50 (S60).

In particular, according to the type of the RNC-RRC 50 controls the NodeB-PHY 40, a number of NBAP messages corresponding to each CPHY-Primitive are used as shown in Table 1 below.

CPHY-Primitive NBAP message CPHY-TrCH-Config-REQ / CNFCPHY-RL-Setup-REQ / CNF Common Transport Channel Setup Request / Response Common Transport Channel Reconfigure Request / Response CPHY-TrCH-Delete-REQ / CNFCPHY-RL-Release-REQ / CNF Common Transport Channel Delete Request / Response CPHY-TrCH-Config-REQ / CNFCPHY-RL-Setup-REQ / CNF Radio Link Setup Request / Response CPHY-TrCH-Delete-REQ / CNFCPHY-RL-Release-REQ / CNF Radio Link Deletion Request / Response CPHY-Modify-REQ / CNFCPHY-TrCH-Config-REQ / CNF Radio Link Reconfiguraion Request / Response CPHY-Error-INDCPHY-Out-of-Sync-IND NodeB Failure CPHY-Measurement-REQ / IND Quality Request / Report CPHY-Sync-IND Status Report (New)

As can be seen from each CPHY-Primitive and various NBAP messages according to each control type of Table 1, RRC performs connection control for radio resource control. That is, the RRC services the identification, maintenance, and release of a connection for radio resource control, and is in charge of radio resource allocation, reconfiguration, and release of resources for this connection.

The following describes various control procedures for each type of RNC-RRC 50 using each primitive and each NBAP message of Table 1 above.

Firstly, the procedure for setting the common transport channel is as follows.

The RNC-RRC 50 delivers CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives to the RNC-NBAP 70 requiring various common transport channel settings.

After receiving the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives, the RNC-NBAP 70 converts the received primitives into a message for setting a common transport channel (Common Transport Channel Setup Request). -Send to NBAP 60.

The NodeB-NBAP 60, which has received the common transport channel setup message from the RNC side 50, 70, converts the received message back into the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives. Send to PHY 40.

Subsequently, the NodeB-PHY 40 sends a CPHY-TrCH-Config-CNF for notifying the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives of the result of its common transport channel setup request. The CPHY-RL-Setup-CNF primitive is forwarded to the NodeB-NBAP 60.

After receiving the CPHY-TrCH-Config-CNF and CPHY-RL-Setup-CNF primitives, the NodeB-NBAP 60 establishes a common transport channel for the received CPHY-TrCH-Config-CNF and CPHY-RL-Setup-CNF primitives. It converts the response message (Common Transport Channel Setup Response) to the opponent RNC-NBAP 70.

The RNC-NBAP 70, which has received the common transport channel setup response message from the NodeB side 40 and 60, converts the received message back into the CPHY-TrCH-Config-CNF and CPHY-RL-Setup-CNF primitives. Send to PHY (50).

The procedure for resetting the second allocated common transport channel is as follows.

The RNC-RRC 50 uses the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives even when several common transport channel resets are required.

First, the RNC-RRC 50 transmits CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives requesting the common transport channel reset to the RNC-NBAP 70.

After receiving the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives, the RNC-NBAP 70 resets the received CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives to the common transport channel. It converts the message to the Common Transport Channel Reconfigure Request and sends it to the other NodeB-NBAP 60.

The NodeB-NBAP 60, which has received the common transport channel reset message from the RNC side 50 and 70, converts the received message back into the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives. Send to PHY 40.

The NodeB-PHY 40 then sends a CPHY-TrCH-Config-CNF to notify the result of its common transport channel reset request in response to the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives. The CPHY-RL-Setup-CNF primitive is forwarded to the NodeB-NBAP 60.

After receiving the CPHY-TrCH-Config-CNF and CPHY-RL-Setup-CNF primitives, the NodeB-NBAP 60 resets the received CPHY-TrCH-Config-CNF and CPHY-RL-Setup-CNF primitives to the common transport channel. It converts the response message (Common Transport Channel Reconfigure Response) to the partner RNC-NBAP (70).

The RNC-NBAP 70, which has received the common transport channel reset response message from the NodeB side 40, 60, converts the received message back into the CPHY-TrCH-Config-CNF and CPHY-RL-Setup-CNF primitives. Send to PHY (50).

Third, the procedure for releasing the allocated common transport channel is as follows.

First, the RNC-RRC 50 transmits to the RNC-NBAP 70 CPHY-TrCH-Delete-REQ and CPHY-RL-Release-REQ primitives requesting the release of the allocated common transport channel.

After receiving the CPHY-TrCH-Delete-REQ and CPHY-RL-Release-REQ primitives, the RNC-NBAP 70 releases the received CPHY-TrCH-Delete-REQ and CPHY-RL-Release-REQ primitives. The message is converted into a common transport channel delete request and sent to the opposite nodeB-NBAP 60.

The NodeB-NBAP 60 receiving the common transport channel release message from the RNC side 50, 70 converts the received message back into the CPHY-TrCH-Delete-REQ and CPHY-RL-Release-REQ primitives. Send to PHY 40.

The NodeB-PHY 40 then sends a CPHY-TrCH-Delete-CNF to notify the result of its common transport channel release request in response to the CPHY-TrCH-Delete-REQ, CPHY-RL-Release-REQ primitives. The CPHY-RL-Release-CNF primitive is forwarded to the NodeB-NBAP 60.

After receiving the CPHY-TrCH-Delete-CNF and CPHY-RL-Release-CNF primitives, the NodeB-NBAP 60 releases the received CPHY-TrCH-Delete-CNF and CPHY-RL-Release-CNF primitives. It converts the response message to the common transport channel delete response and sends it to the opposite RNC-NBAP 70.

The RNC-NBAP 70, which has received the common transport channel release response message from the NodeB side 40, 60, converts the received message back into CPHY-TrCH-Delete-CNF and CPHY-RL-Release-CNF primitives. Send to PHY (50).

Next, the procedure for setting, resetting, and releasing a radio link is as follows.

The RNC-RRC 50 forwards the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives requesting radio link setup to the RNC-NBAP 70.

After receiving the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives, the RNC-NBAP 70 sets the received CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives. The message is converted into a Radio Link Setup Request and sent to the opposite NodeB-NBAP 60.

The NodeB-NBAP 60, which has received the radio link setup message from the RNC side 50, 70, converts the received message back into the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives. Send to 40.

The NodeB-PHY 40 then sends a CPHY-TrCH-Config-CNF and CPHY-RL to notify the result of the radio link setup request in response to the CPHY-TrCH-Config-REQ and CPHY-RL-Setup-REQ primitives. Pass the Setup-CNF primitive to the NodeB-NBAP 60.

After receiving the CPHY-TrCH-Config-CNF and CPHY-RL-Setup-CNF primitives, the NodeB-NBAP 60 sends the received CPHY-TrCH-Config-CNF and CPHY-RL-Setup-CNF primitives to the radio link configuration. It converts the response message (Radio Link Setup Response) to the counterpart RNC-NBAP 70.

The RNC-NBAP 70, which has received the radio link setup response message from the NodeB side 40 and 60, converts the received message back into the CPHY-TrCH-Config-CNF and CPHY-RL-Setup-CNF primitives, Send to PHY (50).

The radio link reset and radio link release procedures are almost similar to each other, except that the primitives and NBAP message types used are different. That is, the CPHY-Modify-REQ / CNF, CPHY-TrCH-Config-REQ / CNF primitives, a radio link reconfiguration request message and a radio link reconfiguration response message (Radio Link Reconfiguration Request / Response) are used for radio link reconfiguration. CPHY-TrCH-Delete-REQ / CNF, CPHY-RL-Release-REQ / CNF primitives, a radio link release request message and a radio link release response message (Radio Link Deletion Request / Response) are used for the link release.

Fifth, the procedure for measuring call quality or service quality of NodeB is as follows.

The RNC-RRC 50 sends to the RNC-NBAP 70 a CPHY-Measurement-REQ primitive that requires quality measurement.

After receiving the CPHY-Measurement-REQ primitive, the RNC-NBAP 70 converts the received CPHY-Measurement-REQ primitive into a message requesting quality measurement (Measurement Request) and sends it to the opposite NodeB-NBAP 60.

The NodeB-NBAP 60, which has received the quality measurement request message from the RNC side 50, 70, converts the received message back to the CPHY-Measurement-REQ primitive and sends it to the NodeB-PHY 40.

The NodeB-PHY 40 then forwards the CPHY-Measurement-IND primitive to notify the NodeB-NBAP 60 for notifying the quality measurement result in response to the CPHY-Measurement-REQ primitive.

After receiving the CPHY-Measurement-IND primitive, the NodeB-NBAP 60 converts the received CPHY-Measurement-IND primitive into a quality measurement report message and sends it to the counterpart RNC-NBAP 70.

The RNC-NBAP 70, which has received the quality measurement report message from the NodeB side 40, 60, converts the received message back to the CPHY-Measurement-IND primitive and sends it to the RNC-PHY 50.

The following describes only the control procedure for notifying the RNC-RRC 50 in the NodeB-PHY 40. This is the error notification and status reporting procedure of the NodeB-PHY 40 in Table 1.

First, the NodeB-PHY 40 is a CPHY-Error-IND primitive (or CPHY-Out-of-Sync-IND primitive) to notify the user when an error such as an out of service (or out of sync) condition occurs. ) Is transmitted to the NodeB-NBAP 60.

After receiving the CPHY-Error-IND primitive (or CPHY-Out-of-Sync-IND primitive), the NodeB-NBAP 60 receives the received CPHY-Error-IND primitive (or CPHY-Out-of-Sync-IND primitive). ) Is converted into a message for notifying a NodeB error (NodeB Failure) and sent to the opposite RNC-NBAP 70.

The RNC-NBAP 70 receiving the NodeB error notification message from the NodeB side 40, 60 converts the received message into a CPHY-Error-IND primitive (or CPHY-Out-of-Sync-IND primitive). To the RNC-PHY 50.

Next, the control procedure for reporting the status to the RNC-RRC 50 in the NodeB-PHY 40 corresponds to the CPHY-Sync-IND primitive of the RNC-RRC 50, and then the status of the NodeB-PHY 40 ( As an example, a Status Report message is used to report whether it is currently synchronized with the RNC, which is a new NBAP message.

According to the method of operating the interface between the RNC and NodeB of the UMTS according to the present invention described above, there is no modification of the protocol hierarchy for the air interface of the existing UMTS, and also using the existing NBAP without newly added signal processing to each other Differently implemented interface between RNC and NodeB can be operated more reliably and effectively.

Claims (6)

In the UMTS including the UE and UTRAN that is air interfaced by a protocol having a hierarchical structure of PHY, MAC, RLC, and RRC from below, In the UTRAN, the RRC converting each request primitive according to its control type into an NBAP request message type corresponding to the primitive; Converting the converted NBAP request message into a request primitive suitable for the PHY control and forwarding the converted NBAP request message to the PHY; The PHY receiving the request primitive converts the response primitive to the NBAP response message form corresponding to the primitive; And converting the converted NBAP response message into a response primitive suitable for the PHY control request, and forwarding the converted NBAP response message to the RRC. 2. The RRC of claim 1, wherein the RRC converts each request primitive into a corresponding NBAP request message corresponding thereto for each control on radio resource allocation, resetting, and releasing, and transmits the request primitives to the PHY. And converting each response primitive to an NBAP response message corresponding to the response primitive and transmitting the same to the RRC. 2. The RRC of claim 1, wherein the RRC converts each request primitive into a corresponding NBAP request message corresponding thereto for each control on radio link establishment, reset, and release, and transmits the request to the PHY. And converting each response primitive to an NBAP response message corresponding to the response primitive and transmitting the same to the RRC. The method according to claim 1, wherein the RRC converts the request primitive into a corresponding NBAP request message to the corresponding PHY to measure the quality of the PHY, and the PHY responds with a response primitive for notifying the quality measurement result. Method of operating an interface between the RNC and NodeB, characterized in that for converting the NBAP response message to be transmitted to the RRC. In the UMTS including the UE and UTRAN that is air interfaced by a protocol having a hierarchical structure of PHY, MAC, RLC, and RRC from below, Converting, in the UTRAN, each notification primitive for notifying the PHY of its status into an NBAP notification message form corresponding to the primitive; Converting the converted NBAP notification message into a notification primitive suitable for the RRC notification and transmitting the converted NBAP notification message to the RRC. The interface operation between the RNC and the NodeB according to claim 5, wherein the PHY converts a notification primitive for notifying the RRC to an NBAP message when the service error and synchronization error occur, and transmits the notification primitive to the RRC. Way.