JP5211873B2 - Wireless terminal and relay device - Google Patents

Description

  This case relates to a wireless terminal and a relay device that transmit and receive wireless communication status.

Evaluation of connectivity of a mobile terminal (User Equipment: UE) is performed in a commercial network. The evaluation of the connectivity of the UE is performed by tracing the data of the protocol and the communication environment with a monitoring tool capable of communicating the processing inside the UE. In addition, the Operation and Maintenance Center (OMC) that can confirm the operation status on the Radio Access Network (RAN) side can monitor the quality measurement result of the uplink (UL) radio line transmitted from the UE. OMC is a functional block used for indoor and RAN connectivity tests. However, the OMC is used to check the operation status on the RAN side when testing indoor or RAN connectivity, and does not notify the UE of information.
JP 2001-352315 A

  Information monitored by OMC (also referred to as OMC information) is used only on the RAN side. Information monitored by OMC is not notified to the UE side. The UE evaluates the UE and determines the test result based on measurement information of the communication environment of the UE, display of the communication protocol, and trace data.

  When evaluating the connectivity of the UE in the serviced network, the UE cannot grasp the communication status of the RAN and the processing status of the communication protocol. For this reason, the UE monitoring tool may indicate the cause of an event that occurred during the UE connectivity evaluation and needs to be analyzed (for example, a decrease in UE transmission power or a communication protocol failure on the RAN side). If it cannot be determined, the UE cannot determine whether the cause is in the communication environment or due to network processing.

  The purpose of this case is to efficiently evaluate the connectivity of wireless terminals.

  The disclosed wireless terminal and relay apparatus employ the following means in order to solve the above-described problems.

That is, the first aspect is
A wireless terminal that communicates with the relay device using the first plane and the second plane,
A request unit that requests the relay device to transmit uplink wireless communication status information between the device and the relay device to the device using a channel in the first plane;
A receiver that receives the wireless communication status information from the relay device using the channel in the first plane;
It was set as the wireless terminal provided with.

  According to the 1st aspect, the radio | wireless terminal can receive the uplink radio communication status information between an own apparatus and a relay apparatus using the channel in a 1st plane.

The second aspect is
A relay device that communicates with a wireless terminal using a first plane and a second plane,
When the wireless terminal requests the wireless terminal to transmit uplink wireless communication status information between the wireless terminal and its own device to the wireless terminal using the channel in the first plane, the request is wirelessly transmitted. Notifying the operation status confirmation unit that accumulates communication status information, and using the channel in the first plane for the uplink radio communication status information between the wireless terminal and the own device acquired from the operation status confirmation unit And it was set as the relay apparatus provided with the transmission / reception part transmitted to the said radio | wireless terminal.

  According to the second aspect, in response to a request from the wireless terminal, the relay device uses the channel in the first plane to transmit uplink wireless communication status information between the wireless terminal and the own device to the wireless terminal. Can be sent to.

  According to the disclosed embodiment, it is possible to efficiently evaluate the connectivity of a wireless terminal.

  Hereinafter, embodiments will be described with reference to the drawings. The configuration of the embodiment is an exemplification, and is not limited to the configuration of the disclosed embodiment.

Embodiment 1
In the present embodiment, a case where OMC information is bound to U-Plane will be described.

(System configuration)
FIG. 1 is a diagram illustrating a system configuration example of the present embodiment. The system of the present embodiment includes a network 100, a core network (CN) 200 connected to the network 100, a radio access network (RAN) 300 connected to the CN 200, and a radio connected to the RAN 300. It has OMC600 connected to a terminal (UE: User Equipment), CN200, and RAN300.

The CN 200 includes a Home Location Register (HLR) 202, a Service Control Function (SCF) 204, a Visitor Location Register (VLR) 206, a Mobile services Switching Center (MSC) 212, a Gateway MSC (GMSC) 214, and a Serving GPRS Support Node (SGSN). 222, Gateway GPRS Support Node (GGSN) 224.

The MSC 212 and the GMSC 214 are CS domain (Circuit Switching domain). SGSN 222 and GGSN 224 are PS domain (Packet Switching domain).

  The RAN 300 includes a radio network controller (RNC) 400 and a NodeB 500. RNC 400 is connected to CN 200 and Node B. Node B 500 is connected to RNC 400 and UE 700.

  The RNC 400 is a radio network control device. The RNC 400 manages the NodeB 500.

  Node B 500 is a radio base station. The NodeB 500 performs direct wireless communication with the UE 700 and terminates the wireless line. Node B 500 is managed by RNC 400.

  The NodeB 500 can measure the uplink quality between the UE 700 and the NodeB 500. The NodeB 500 can periodically transmit the uplink quality between the UE 700 and the NodeB 500 to the OMC 600.

  Examples of uplink quality include UL-BLER (Uplink Block Error Ratio), DPCH (Dedicated Physical Channel) -RSCP (Received Signal Code Power), DPCH-SIR (Signal to Interference power Ratio), and the like. UL-BLER is a block error ratio of the uplink signal. RSCP is the desired signal power. SIR is the desired signal to interference signal power ratio. DPCH is a dedicated physical channel assigned to each user.

  The interface between CN 200 and RNC 400 is called the Iu interface. Further, the interface between the NodeB 500 and the UE 700 is called a Uu interface.

  The RNC 400 and the NodeB 500 may be realized as one relay device.

FIG. 2 is a diagram illustrating a system configuration example of the RNC and its peripheral devices. The RNC 300 includes a medium access control (MAC) layer unit 410 and a radio link control (RLC).
A layer unit 420 and a radio resource control (RRC) layer unit 430 are included. These functional units may be realized as hardware or software.

  The MAC layer unit 410 divides the signal received from the NodeB 500 for each LCH (logical channel). The MAC layer unit 410 transmits a signal divided for each LCH to the RLC 420. The RLC layer unit 420 processes data of LCH1, LCH2, and LCH3. In this embodiment, control data is bound to LCH1, user data (application data) is bound to LCH2, and OMC information is bound to LCH3.

C-Plane (Control Plane) handles control data such as a connection between the UE and the network. U-Plane (User Plane) handles user data (application data).

  The RRC layer unit 430 performs RRC layer processing. The OMC information transmitted from the OMC 600 is mapped to LCH 3 by the RLC layer unit 420 via the RRC layer unit 430.

  The RRC layer unit 430 performs control processing (communication protocol control) of the Uu interface (communication between the UE 700 and the Node B 500).

  The RNC 400 can transmit the OMC information to the UE 700 by binding the OMC information to the logical channel (LCH) of the transport channel (Trch) to which the U-Plane is mapped. In this embodiment, LCH3 having OMC information is mapped to U-Plane Trch2.

  In RNC 400, transmission / reception data is processed by MAC layer section 410, RLC layer section 420, RRC layer section 430, and the like.

  The OMC 600 can be connected to the CN 200, the RNC 400, and the NodeB 500.

The OMC 600 stores control information between the UE 700 and the RAN 300. The OMC 600 is a functional block used for monitoring the communication status inside the RAN 300, and can be used for testing. OMC 600 is CN200, RNC400, or NodeB50
It may be incorporated as one of zero functional blocks. The OMC 600 can be realized as hardware or software.

  The OMC 600 receives, from the RNC 400, an OMC setting notification for notifying that the UE 700 requests OMC information and an OMC start notification for notifying the start of transmission of OMC information to the UE 700.

  Operation information of UE 700, Node B 500, RNC 400, SGSN 222, MSC 212, VLR 206, etc. is notified to OMC 600. Further, the OMC 600 can receive failure information (error information) and the like from the UE 700, Node B 500, RNC 400, SGSN 222, MSC 212, VLR 206, and the like. The OMC 600 can store the notified information. The OMC 600 transmits data to the RNC 400 in order to notify the UE 700 of the collected information (notified information and the like). Information notified from the OMC 600 to the RNC 400 may be notified to the UE 700 via the NodeB 500.

  The OMC 600 may receive uplink quality information between the UE 700 and the NodeB 500 from the NodeB 500.

  FIG. 3 is a diagram illustrating a configuration example of the UE. The UE 700 includes a physical layer unit 780, a MAC layer unit 710, an RLC layer unit 720, an RRC layer unit 730, a non-access layer unit 740, a control monitor block unit 750, a TAF (Terminal that performs processing such as a voice call, etc. Adaptation Function) section 760 is provided. These functional units may be realized as hardware or software.

The UE 700 may be connected to an application 1010 through the TAF unit 760 and a monitor tool 1020 through the control monitor block unit 750. The monitor tool 1020 can analyze the communication status between the UE 700 and the RAN 300 using the OMC information from the OMC 600. The application 1010 and the monitoring tool 1020 may be realized as software inside or outside the UE 700, or may be realized as hardware inside or outside the UE 700, respectively.

  The MAC layer unit 710 divides the signal received from the NodeB 500 for each LCH. The MAC layer unit 710 transmits the divided signal to the RLC layer unit 720.

  When the RLC layer unit 720 receives the control data of LCH 1, the RLC layer unit 720 executes the RLC process and transmits it to the RRC layer unit 730. Further, when the RLC layer unit 720 receives the user data of LCH2, the RLC layer unit 720 performs the RLC process and transmits the RLC process to the RRC layer unit 730.

  Upon receiving the LMC3 OMC information, the RLC layer unit 720 transfers the OMC information to the control monitor block unit 750 without executing the RLC process. This is because the OMC information is transmitted and received by RLC-TM.

  The OMC information is bound to U-Plane Trch2.

  In UE 700, transmission / reception data is processed by physical layer section 780, MAC layer section 710, RLC layer section 720, RRC layer section 730, and the like.

  The control monitor block unit 750 can collect and store control information, OMC information, control signals in the UE 700, and the like. Information stored in the control monitor block 750 can be used by the monitor tool 1020.

(Operation example)
<Example of normal connection operation>
4 and 5 are diagrams illustrating an example of an operation sequence of normal connection. A, B, C, D, and E in FIG. 4 are connected to A, B, C, D, and E in FIG. 5, respectively.

The UE 700 transmits an RRC connection request (RRC Connection Request) to the RNC 400 (Serving RNC) in order to place a call. The RRC connection request from the UE 700 is received by the RNC 400 via the NodeB 500 (SQ1002).

  The RNC 400 transmits a report (Report) indicating that the RRC connection request has been received from the UE 700 to the OMC 600 (SQ1004). When the OMC 600 is connected to the RAN 300 or the CN 200, the OMC 600 can receive and store the operation status notified from the RAN 300, the CN 200, or the like.

  The RNC 400 maps the LCH (Logical Channel) 1 to the Trch (Transport Channel) 1 (SQ1006). LCH1 is a logical channel for control data.

  The RNC 400 transmits an RRC connection setup for the RRC connection request to the UE 700 via the NodeB 500 (SQ1008).

  The RNC 400 transmits a report (Report) indicating that the RRC connection setup has been transmitted to the UE 700 to the OMC 600 (SQ1010).

  The UE 700 maps LCH1 to Trch1 (SQ1012).

UE700 transmits RRC connection complete (RRC Connection Complete) with respect to RRC connection setup to RNC400. RR from UE700
The C connection complete is received by the RNC 400 via the NodeB 500 (SQ1014). The RRC connection complete is a message notifying that the RRC connection has been established.

  The RNC 400 transmits a report (Report) indicating that the RRC connection complete has been received from the UE 700 to the OMC 600 (SQ1016).

When the RRC connection is established, the UE 700 transmits a service request (Service Request) to an upper network (CN 200 or the like). The service request from the UE 700 is transmitted to the CN 200 via the NodeB 500 and the RNC 400 (SQ1018). A message from the UE 700 always passes through the NodeB 500 and the RNC 400.

  The RNC 400 transmits a report indicating that a service request has been transmitted from the UE 700 to the OMC 600 (SQ1020).

  The RNC 400 maps LCH2 to Trch2 (SQ1022). LCH1 is a logical channel for user data (application data).

  The RNC 400 transmits a radio bearer setup (RADIO BEARER SETUP) to the UE 700 via the NodeB 500 (SQ1024).

  The RNC 400 transmits a report (Report) indicating that the radio bearer setup is transmitted to the UE 700 to the OMC 600 (SQ1026).

  The UE 700 maps LCH2 to Trch2 (SQ1028).

The UE 700 transmits a radio bearer setup complete (RADIO BEARER SETUP Complete) for the radio bearer setup (RADIO BEARER SETUP) to the UE 700 via the NodeB 500 (SQ1030).

  The RNC 400 transmits a report (Report) indicating that the radio bearer setup complete has been received from the UE 700 to the OMC 600 (SQ 1032).

  Thereafter, user data starts to flow to U-Plane (SQ1040).

<Operation example when binding OMC information to U-Plane>
6 and 7 are diagrams illustrating an example of an operation sequence when binding OMC information to U-Plane. F, G, H, I, and J in FIG. 6 are connected to F, G, H, I, and J in FIG. 7, respectively.

FIG. 8 is a diagram illustrating an example of USIM setting (Administrative Data field) of a USIM card.

  A USIM (Universal Subscriber Identity Module) card is a card that is attached to a terminal and stores contractor information, various setting information, and the like. The USIM setting is setting information for a terminal to which a USIM card is attached.

The USIM setting includes, as header information, a terminal operation mode (UE operation mode), additional information (Additional information), and a mobile network code (MNC) length (length of MNC in) in IMSI (International Mobile Subscriber Identity).
the IMSI) etc.

The terminal operation mode (UE operation mode) includes a mode of operation for the terminal (mode of operation for the UE). As illustrated in FIG. 8, the terminal operation mode (UE operation mode) includes a normal operation mode, a type approval operations mode, a maintenance mode, and the like. Each terminal operation mode is specified by a 1-byte value. For example, the normal operation mode is designated by “00”.

In this embodiment, in the terminal operation mode (UE operation mode), the “OMC information on U-Plane” mode for requesting OMC information to the RAN mode, and “C-Plane” An “OMC information on C-Plane” mode is added. Here, the OMC information request (OMC information on U-Plane) mode in U-Plane is designated by “7X”. Also, the OMC information request (OMC information on C-Plane) mode in C-Plane is designated by “7X + 1”. These values are merely examples, and may be designated by other values that do not overlap with already designated values. The OMC information request mode in U-Plane is a mode for requesting acquisition of OMC information in U-Plane. Further, the OMC information request mode in C-Plane is a mode for requesting acquisition of OMC information in C-Plane.

  When the UE 700 is powered on, the UE 700 reads the USIM settings of the USIM card. Here, it is assumed that the terminal operation mode of USIM setting is an OMC information request (OMC information on U-Plane) mode in U-Plane. The UE 700 recognizes that the terminal operation mode of the USIM setting is the OMC information request (OMC information on U-Plane) mode in the U-Plane, and the UEMC information request (OMC information on U-Plane) mode in the U-Plane is set. Process.

Here, the OMC information is requested by the USIM setting. However, the OMC information is requested by a special command, the OMC information is requested by a DTMF (Dual-Tone Multi-Frequency) command during communication, or the like. Good.

  When the UE 700 starts connection with the RAN 300, the UE 700 transmits an RRC connection request message to the RNC 400 (FIG. 6: SQ2002).

FIG. 9 is a diagram illustrating an example of a message configuration of an RRC connection request. The information element (Information Element) of the RRC connection request message includes UE Specific Behavior Information 1 idle. In the OMC information request, UE Specific Behavior Information 1 idle is set to “OMC information on U-Plane (7X)” or “OMC information on C-Plane (7X + 1)”. Here, UE Specific Behavior Information 1 idle is set to “OMC information on U-Plane (7X)”. The RRC connection request is created by the RRC layer unit 730.

  The RRC connection request from the UE 700 is received by the RNC 400 via the NodeB 500 (FIG. 6: SQ2002).

  The RNC 400 transmits a report (Report) indicating that the RRC connection request has been received from the UE 700 to the OMC 600 (SQ2004). The OMC 600 can receive and store the operation status notified from the RAN 300, the CN 200, or the like.

The RNC 400 confirms that UE Specific Behavior Information 1 idle in the RRC connection request message is OMC information on U-Plane. RNC400 is U
Recognize that E700 is requesting OMC information in U-Plane.

  The RNC 400 transmits an OMC setting notification for notifying that the UE 700 requests OMC information to the OMC 600 (SQ2005). The OMC 600 recognizes that the UE 700 is requesting OMC information.

  The RNC 400 maps the LCH (Logical Channel) 1 to the Trch (Transport Channel) 1 (SQ2006). LCH1 is a logical channel for control data.

  The RNC 400 transmits an RRC connection setup for the RRC connection request to the UE 700 via the NodeB 500 (SQ2008).

  The RNC 400 transmits a report (Report) indicating that the RRC connection setup has been transmitted to the UE 700 to the OMC 600 (SQ2010).

  The UE 700 maps LCH1 to Trch1 (SQ2012).

UE700 transmits RRC connection complete (RRC Connection Complete) with respect to RRC connection setup to RNC400. RR from UE700
The C connection complete is received by the RNC 400 via the NodeB 500 (SQ2014). The RRC connection complete is a message notifying that the RRC connection has been established.

  The RNC 400 transmits a report (Report) indicating that the RRC connection complete has been received from the UE 700 to the OMC 600 (SQ2016).

The RNC 400 transmits an OMC start notification requesting the start of transmission of OMC information to the UE 700 to the OMC 600 (SQ2017). The OMC 600 may be incorporated as one of functional blocks of the CN 200, the RNC 400, or the NodeB 500. The OMC 600 can be realized as hardware or software.
When the OMC 600 receives the OMC start notification, the OMC 600 starts to periodically transmit OMC information to the UE 700.

When the RRC connection is established, the UE 700 transmits a service request (Service Request) to an upper network (CN 200 or the like). The service request from the UE 700 is transmitted to the CN 200 via the NodeB 500 and the RNC 400 (SQ2018). A message from the UE 700 always passes through the NodeB 500 and the RNC 400.

  The RNC 400 transmits a report indicating that a service request has been transmitted from the UE 700 to the OMC 600 (SQ2020).

  The RNC 400 maps LCH2 to Trch2 (FIG. 7: SQ2022). LCH2 is a logical channel for user data (application data). The RNC 400 maps LCH3 to Trch2. LCH3 is a logical channel for OMC information.

FIG. 10 shows a transport channel (Trch) in the physical layer.
2 is a diagram illustrating an example of mapping between a logical channel (LCH) and a logical channel.

A MAC header (MAC Header) Trch1 and a MAC header (MAC Header) Trch2 are mapped to the physical layer (Physical Layer). C-Plane (Control Plane)
Assigned to Trch1. U-Plane (User Plane) is assigned to Trch2. C-Plane (Control Plane) handles control information such as a connection between the UE and the network. U-Plane (User Plane) handles user information. Each of U-Plane and C-Plane can include a plurality of logical channels.

  The MAC header Trch1 is mapped with an RLC (Radio Link Control) header (RLC Header) and LCH1 for control data (Control Data).

  LCH2 for RLC header (RLC Header) and application data (Application Data) is mapped to MAC header Trch2. Also, LCH3 for OMC information (OMC Data) is mapped to the MAC header Trch2. Therefore, LCH2 and LCH3 are mapped to the MAC header Trch2. The RLC header is a block that performs operations such as arrival confirmation.

OMC information (OMC Data) is transmitted in RLC-TM (RLC Transparent Mode). RLC-TM is a mode that does not use an RLC header. Therefore, the RLC header is LCH3
Not mapped to RLC-TM is used when arrival confirmation is not required. The reason why RLC-TM is used for the OMC information is that, even if the UE 700 cannot acquire the OMC information, it does not directly affect the communication itself. The RMC header may be mapped on the OMC information side.

  C-Plane and U-Plane data are transmitted and received by multiplexing by time division, code division, and the like. Therefore, C-Plane and U-Plane data are transmitted and received independently without interfering with each other. That is, C-Plane and U-Plane can communicate with each other without affecting the communication of other Planes. Therefore, for example, when a test is performed using C-Plane, transmitting OMC information using U-Plane does not affect the test using C-Plane.

Returning to FIG. 7, the RNC 400 transmits a radio bearer setup (RADIO BEARER SETUP) to the UE 700 via the NodeB 500 (SQ2024). The radio bearer setup is a message for notifying the UE 700 of RAB (Radio Access Bearer) setting from the RNC 400. The RAB setting includes information for binding the OMC information to the U-Plane transport channel (Trch2).

  The RNC 400 transmits a report (Report) indicating that the radio bearer setup is transmitted to the UE 700 to the OMC 600 (SQ2026).

  The UE 700 maps LCH2 to Trch2. Also, the UE 700 maps LCH3 to Trch2. (SQ2028).

The UE 700 transmits a radio bearer setup complete (RADIO BEARER SETUP Complete) for the radio bearer setup (RADIO BEARER SETUP) to the UE 700 via the NodeB 500 (SQ2030).

  The RNC 400 transmits a report (Report) indicating that the radio bearer setup complete has been received from the UE 700 to the OMC 600 (SQ2032).

  Thereafter, user data starts to flow in the U-Plane (SQ2040).

  The UE 700 periodically transmits a measurement report (Measurement Report) including the operation information of the UE 700 to the RNC 400 (SQ2052). The measurement report may include a transmission / reception data amount, a data transmission / reception rate, and position information. The RNC 400 can grasp the operation status and the like of the UE 700 from the measurement report from the UE 700. The RNC 400 transmits a report (Report) indicating that the measurement report (Measurement Report) has been received from the UE 700 (SQ2054).

The NodeB 500 periodically transmits the uplink quality of the UE 700 (UL-BLER (Block Error Ratio), DPCH (Dedicated Physical Channel) -RSCP (Received Signal).
Code Power), DPCH-SIR (Signal to Interference power Ratio), etc.) information is transmitted to the OMC 600 (SQ2060). The OMC 600 can store such information.

  The RNC 400 notifies the OMC 600 of message contents and debug information every time an L3 message is generated.

The OMC 600 periodically transmits information received from the RNC 400, the NodeB 500, etc., as OMC information to the UE 700 via the RNC 400, the NodeB 500. The RNC 400 binds the OMC information received from the OMC 600 to the Trch 2 that is the U-Plane and transmits the OMC information to the UE 700 (SQ2070).

  FIG. 11 is a diagram illustrating an example of OMC information. The OMC information may include UL Transport Channel BLER, UL DPCH RSCP, UL DPCH SIR reported from the Node B 500 to the OMC 600, L3 message reported from the RNC 400 to the OMC 600, failure information, and the like.

  The UE 700 can check the line quality of the currently communicating UL and the communication status between the RNC 500 and the CN 200 in real time by using the OMC information.

  The LCH3 OMC information received by the UE 700 is processed by the physical layer unit 780, the MAC layer unit 710, and the RLC layer unit 720 and input to the control monitor block unit 750.

  The control monitor block unit 750 of the UE 700 can collect and store control information, OMC information, control signals in the UE 700, and the like.

  The monitor tool 1020 can grasp the uplink communication status between the UE 700 and the NodeB 500 by using the control information, the OMC information, and the like stored in the control monitor block unit 750.

  For example, consider a case where communication between the UE 700 and the NodeB 500 is disconnected after the uplink communication status (line quality) between the UE 700 and the NodeB 500 deteriorates. On the UE 700 side, the upstream communication status and the like is grasped from the OMC information, so that the communication status between the UE 700 and the Node B 500 is deteriorated by using the monitor tool 1020 or the like. Easy to estimate.

(Operational effect of this embodiment)
According to the present embodiment, the UE 700 periodically receives OMC information from the OMC 600 via the RAN 300. When there is a communication interruption or a resource request from the network side, the UE 700 can specify the release factor from the network side based on the previous UL communication environment or the like.

  According to the present embodiment, even when a cause-unknown communication disconnection occurs, the UE 700 periodically receives the OMC information message, so it is possible to grasp the UL line quality immediately before disconnection and the communication status of the RNC 400. It becomes possible. Therefore, the UE 700 can perform phenomenon isolation when a failure occurs.

  According to the present embodiment, the UE 700 can receive the control information (communication information) of the RAN 300 as OMC information without changing the physical channel. The RAN 300 can communicate by setting a new LCH, and can notify the control information of the RAN 300 without changing the physical channel. Therefore, it is possible to prevent the communication below the MAC layer from being affected.

  According to the present embodiment, by adding an LCH that transmits OMC information to the U-Plane, a test for confirming the control data of the C-Plane is performed without affecting the control data of the C-Plane. Can do.

According to this embodiment, in order to efficiently evaluate (test) the connectivity of UE 700, R
By notifying the UE 700 to be tested during the communication of the operation status of the AN 300 without affecting the communication function being performed, the UE 700 and the Node B 500 are notified of the uplink communication status and the RAN 300 operation status. Therefore, the analysis of the problem that has been judged by estimation can be performed using the operation status of the RAN 300, and the efficiency of debugging can be increased.

[Embodiment 2]
Next, Embodiment 2 will be described. The second embodiment has common points with the first embodiment. Therefore, differences will be mainly described, and description of common points will be omitted.

  In the present embodiment, a case where OMC information is bound to C-Plane will be described.

(System configuration)
The system configuration of the present embodiment can be the same as the system configuration example shown in FIG.

  The RNC of this embodiment has the same configuration as the RNC shown in FIG. However, in the present embodiment, LCH3 having OMC information is mapped to C-Plane Trch1.

  FIG. 12 is a diagram illustrating a configuration example of the UE. The UE 700 includes a physical layer unit 780, a MAC layer unit 710, an RLC layer unit 720, an RRC layer unit 730, a non-access layer unit 740, a control monitor block unit 750, and a TAF unit 760 that performs processing such as a voice call. Is provided.

The UE 700 receives an application 1010 through the TAF 760,
A monitor tool 1020 may be connected through a control monitor block 750. The monitor tool 1020 can analyze the communication status between the UE 700 and the RAN 300 using the OMC information from the OMC 600.

  The MAC layer unit 710 divides the signal received from the NodeB 500 for each LCH. The MAC layer unit 710 transmits the divided signal to the RLC layer unit 720.

  Upon receiving the LMC3 OMC information, the RLC layer unit 720 transfers the OMC information to the control monitor block without executing the RLC process.

  The OMC information is bound to C-Plane Trch1.

(Operation example)
<Operation example when binding OMC information to C-Plane>
13 and 14 are diagrams illustrating an example of an operation sequence when binding OMC information to C-Plane. K, L, M, N and O in FIG. 13 are connected to K, L, M, N and O in FIG. 14, respectively.

  A USIM (Universal Subscriber Identity Module) card is a card that is attached to a terminal and stores contractor information, various setting information, and the like. The USIM setting is setting information for a terminal to which a USIM card is attached. Similar to the example shown in FIG. 8 of the first embodiment, the USIM setting includes, as header information, terminal operation mode (UE operation mode), additional information (Additional information), and MNC in IMSI (International Mobile Subscriber Identity). (Mobile Network Code) Length (MNC in the IMSI) etc.

The terminal operation mode (UE operation mode) includes a mode of operation for the terminal (mode of operation for the UE). Similar to the example illustrated in FIG. 8 of the first embodiment, the terminal operation mode (UE operation mode) includes a normal operation mode, a type approval operations mode, a maintenance mode, and the like. . Each terminal operation mode is specified by a 1-byte value. For example, the normal operation mode is designated by “00”.

As in the case of the first embodiment, in the terminal operation mode (UE operation mode), the OMC information request (OMC information on U-Plane) is requested to the RAN.
“U-Plane)” mode and “OMC information on C-Plane” mode in C-Plane ”mode. Here, the OMC information request (OMC information on U-Plane) mode in U-Plane is designated by “7X”. Also, the OMC information request (OMC information on C-Plane) mode in C-Plane is designated by “7X + 1”. These values are merely examples, and may be designated by other values that do not overlap with already designated values. The OMC information request mode in U-Plane is a mode for requesting acquisition of OMC information in U-Plane. Further, the OMC information request mode in C-Plane is a mode for requesting acquisition of OMC information in C-Plane.

  When the UE 700 is powered on, the UE 700 reads the USIM settings of the USIM card. Here, it is assumed that the terminal operation mode of USIM setting is an OMC information request (OMC information on U-Plane) mode in C-Plane. The UE 700 recognizes that the terminal operation mode of USIM setting is the OMC information request (OMC information on U-Plane) mode in C-Plane, and the OMC information request (OMC information on U-Plane) mode in C-Plane Process.

Here, the OMC information is requested by the USIM setting. However, the OMC information is requested by a special command, the OMC information is requested by a DTMF (Dual-Tone Multi-Frequency) command during communication, or the like. Good.

  When the UE 700 starts connection with the RAN 300, the UE 700 transmits an RRC connection request message to the RNC 400 (FIG. 6: SQ3002).

The message configuration of the RRC connection request can be the same as that of the example of FIG. The information element (Information Element) of the RRC connection request message includes UE Specific Behavior Information 1 idle. In the OMC information request, UE Specific Behavior Information 1 idle is set to “OMC information on U-Plane (7X)” or “OMC information on C-Plane (7X + 1)”. Here, UE Specific Behavior Information 1 idle is set to “OMC information on C-Plane (7X + 1)”.

  The RRC connection request from the UE 700 is received by the RNC 400 via the NodeB 500 (FIG. 13: SQ3002).

  The RNC 400 transmits a report (Report) indicating that the RRC connection request has been received from the UE 700 to the OMC 600 (SQ3004). The OMC 600 can receive and store the operation status notified from the RAN 300, the CN 200, or the like.

The RNC 400 transmits an OMC setting notification for notifying that the UE 700 requests OMC information to the OMC 600 (SQ3005). The OMC 600 recognizes that the UE 700 is requesting OMC information.

The RNC 400 confirms that UE Specific Behavior Information 1 idle in the RRC connection request message is OMC information on C-Plane. RNC400 is U
Recognize that E700 is requesting OMC information in C-Plane.

  The RNC 400 maps LCH (Logical Channel) 1 to Trch (Transport Channel) 1. The RNC 400 maps LCH3 to Trch1 (SQ3006). LCH1 is a logical channel for control data. LCH3 is a logical channel for OMC information.

In accordance with UE Specific Behavior Information 1 Idle information included in the RRC connection request, the RNC 400 transmits the OMC information data transfer setting and the OMC information to the C-Plan.
RAB setting to bind to the transport channel (Trch1) of e is performed.

  The RNC 400 transmits an RRC connection setup for the RRC connection request to the UE 700 via the NodeB 500 (SQ3008). The RAB setting is notified to the UE 700 by RRC connection setup.

  The RNC 400 transmits a report (Report) indicating that the RRC connection setup has been transmitted to the UE 700 to the OMC 600 (SQ3010).

  The UE 700 maps LCH1 to Trch1 (SQ3012).

UE700 transmits RRC connection complete (RRC Connection Complete) with respect to RRC connection setup to RNC400. RR from UE700
The C connection complete is received by the RNC 400 via the NodeB 500 (SQ3014). The RRC connection complete is a message notifying that the RRC connection has been established. Thereby, OMC information can be transmitted from the OMC 600 to the UE 700.

  The RNC 400 transmits a report (Report) indicating that the RRC connection complete has been received from the UE 700 to the OMC 600 (SQ3016).

  The RNC 400 transmits an OMC start notification requesting the start of transmission of OMC information to the UE 700 to the OMC 600 (SQ3017). When the OMC 600 receives the OMC start notification, the OMC 600 starts to periodically transmit OMC information to the UE 700.

When the RRC connection is established, the UE 700 transmits a service request (Service Request) to an upper network (CN 200 or the like). The service request from the UE 700 is transmitted to the CN 200 via the NodeB 500 and the RNC 400 (SQ3018). A message from the UE 700 always passes through the NodeB 500 and the RNC 400.

  The RNC 400 transmits a report indicating that a service request has been transmitted from the UE 700 to the OMC 600 (SQ3020).

The RNC 400 maps LCH2 to Trch2 (FIG. 14: SQ3022).
LCH2 is a logical channel for user data (application data).

  FIG. 15 is a diagram illustrating an example of mapping between a transport channel (Trch) and a logical channel (LCH) in the physical layer.

  A MAC header (MAC Header) Trch1 and a MAC header (MAC Header) Trch2 are mapped to the physical layer (Physical Layer). C-Plane is assigned to Trch1. U-Plane is assigned to Trch2.

  The MAC header Trch1 is mapped with an RLC (Radio Link Control) header (RLC Header) and LCH1 for control data (Control Data). Also, LCH3 for OMC information (OMC Data) is mapped to the MAC header Trch1. Therefore, LCH1 and LCH3 are mapped to the MAC header Trch1. Here, since the OMC information (OMC Data) is transmitted in RLC-TM (RLC Transparent Mode), the RLC header is unnecessary. The reason why RLC-TM is used is that even if OMC information cannot be acquired, communication itself is not directly affected. The RMC header may be mapped on the OMC information side.

  LCH2 for RLC header (RLC Header) and application data (Application Data) is mapped to MAC header Trch2.

Returning to FIG. 14, the RNC 400 transmits a radio bearer setup (RADIO BEARER SETUP) to the UE 700 via the NodeB 500 (SQ3024). The radio bearer setup is a message for notifying the UE 700 of RAB (Radio Access Bearer) setting from the RNC 400.

  The RNC 400 transmits a report (Report) indicating that the radio bearer setup has been transmitted to the UE 700 to the OMC 600 (SQ3026).

  The UE 700 maps LCH2 to Trch2. Also, the UE 700 maps LCH3 to Trch2. (SQ3028).

The UE 700 transmits a radio bearer setup complete (RADIO BEARER SETUP) for the radio bearer setup (RADIO BEARER SETUP) to the UE 700 via the NodeB 500 (SQ3030).

  The RNC 400 transmits a report (Report) indicating that the radio bearer setup complete has been received from the UE 700 to the OMC 600 (SQ3032).

  Thereafter, user data starts to flow in the U-Plane (SQ3040).

  UE 700 periodically transmits a measurement report (Measurement Report) including operation information of UE 700 to RNC 400 (SQ3052). The measurement report may include a transmission / reception data amount, a data transmission / reception rate, and position information. The RNC 400 can grasp the operation status and the like of the UE 700 from the measurement report from the UE 700. The RNC 400 transmits a report (Report) indicating that the measurement report (Measurement Report) has been received from the UE 700 (SQ3054).

The NodeB 500 periodically transmits the uplink quality of the UE 700 (UL-BLER (Block Error Ratio), DPCH (Dedicated Physical Channel) -RSCP (Received Signal).
Code Power), DPCH-SIR (Signal to Interference power Ratio), etc.) information is transmitted to the OMC 600 (SQ3060).

  The RNC 400 notifies the OMC 600 of a message and debug information every time an L3 message is generated.

  The OMC 600 periodically transmits information received from the RNC 400, the NodeB 500, etc., as OMC information to the UE 700 via the RNC 400, the NodeB 500. The RNC 400 binds the OMC information received from the OMC 600 to the Trch 1 that is the C-Plane, and transmits it to the UE 700 (SQ3070).

  The LCH3 OMC information received by the UE 700 is processed by the physical layer unit 780, the MAC layer unit 710, and the RLC layer unit 720 and input to the control monitor block unit 750.

  The control monitor block unit 750 of the UE 700 can collect and store control information, OMC information, control signals in the UE 700, and the like. The monitor tool 1020 can grasp the uplink communication status between the UE 700 and the NodeB 500 by using the OMC information or the like stored in the control monitor block unit 750.

(Operational effect of this embodiment)
According to the present embodiment, by adding an LCH for transmitting OMC information to the C-Plane, a test for confirming the U-Plane user data without affecting the U-Plane user data is performed. Can do.

[Embodiment 3]
Next, Embodiment 3 will be described. The third embodiment has common points with the second embodiment. Therefore, differences will be mainly described, and description of common points will be omitted.

  In the case of the second embodiment, an example when a failure (error) occurs in the U-Plane will be described.

(System configuration)
The overall system configuration is the same as the configuration of FIG.

  FIG. 16 is a diagram illustrating a configuration example of the RNC and its peripheral devices according to the present embodiment. The RNC 400 and its peripheral devices have the same configuration as the RNC and its peripheral devices of the second embodiment. Here, an example is shown in which the UL (Uplink) radio quality between UE 700 and Node B 500 is degraded.

  When the UL signal transmitted from the UE 700 is received by the NodeB, the uplink communication quality has deteriorated, and the transfer of data to the CN 200 has failed.

  As described in the second embodiment, in the test environment in which the situation can be confirmed by the UE 700, the reception state on the NodeB side can be confirmed. Therefore, even when communication from the RNC 400 is disconnected due to quality degradation, UE700 can grasp this.

FIG. 17 is a diagram illustrating a configuration example of a UE. The UE has the same configuration as the UE of the second embodiment. The UE 700 includes a physical layer unit 780, a MAC layer unit 710, an RLC layer unit 720, an RRC layer unit 730, a non-access layer unit 740, a control monitor block unit 750, and a TAF unit 760 that performs processing such as a voice call. Is provided.

(Operation example)
FIG. 18 is a diagram illustrating an operation example of the present embodiment.

  Until the UE 700 sends an RRC connection request to the RNC, the UE 700 transmits a radio bearer setup complete to the RNC 400, and the RNC 400 transmits a report to the OMC 600, the operation examples (SQ3002 to Since this is the same as SQ3032), it is omitted.

  After the RRC connection is established and the U-Plane data starts to flow, it is assumed that errors increase due to environmental factors of the UL signal. Then, UL synchronization cannot be obtained on the NodeB 500 side (SQ4042). Then, the U-Plane data from the UE 700 does not reach the CN 200 (SQ4044).

  Here, it is assumed that the downlink U-Plane data is normal (SQ4046, SQ4048). Therefore, the UE 700 cannot recognize the increase in the UL signal error from the received U-Plane data.

  The NodeB 500 periodically reports the UL communication environment to the OMC 600 (SQ 4060). Therefore, the NodeB 500 also reports that the error of the UL signal from the UE 700 has increased.

  The OMC 600 periodically transmits OMC information to the UE 700. The UE 700 can recognize from the received OMC information that errors are increasing in the UL signal.

  Further, when the radio quality deteriorates (SQ4080), RNC 400 transmits an RRC connection release to UE 700 and releases the RRC connection (SQ4090).

  At this time, the UE 700 knows that the UL radio quality has deteriorated based on the OMC information, and therefore can recognize that the cause of the release of the RRC connection is the deterioration of the UL radio quality. Become.

It is a figure which shows a system configuration example. It is a figure which shows the system configuration example of RNC and its peripheral devices. It is a figure which shows the structural example of UE. It is a figure which shows the example (1) of the operation sequence of normal connection. It is a figure which shows the example (2) of the operation sequence of normal connection. It is a figure which shows the example (1) of an operation | movement sequence when binding OMC information to U-Plane. It is a figure which shows the example (2) of an operation | movement sequence when binding OMC information to U-Plane. It is a figure which shows the example of the USIM setting (Administrative Data field) of a USIM card. It is a figure which shows the example of a message structure of a RRC connection request. It is a figure which shows the example of the mapping of the transport channel and logical channel in a physical layer. It is a figure which shows the example of OMC information. It is a figure which shows the structural example of UE. It is a figure which shows the example (1) of an operation | movement sequence when binding OMC information to C-Plane. It is a figure which shows the example (2) of an operation | movement sequence when binding OMC information to C-Plane. It is a figure which shows the example of the mapping of the transport channel and logical channel in a physical layer. It is a figure which shows the system configuration example of RNC and its peripheral device. It is a figure which shows the structural example of UE. It is a figure which shows the operation example when a failure (error) generate | occur | produces in U-Plane.

Explanation of symbols

100 network
200 core network
202 HLR
204 SCF
206 VLR
212 MSC
214 GMSC
222 SGSN
224 SCF
300 RAN
400 RNC
410 MAC layer part
420 RLC layer part
430 RRC layer part
500 NodeB
600 OMC
700 UE
710 MAC layer part
720 RLC layer part
730 RRC layer part
740 Non-Access Layer part
750 Control monitor block
760 TAF Department
780 Physical layer part

Claims (4)

A wireless terminal that communicates with the relay device using the first plane and the second plane,
When the USIM setting information acquired from the USIM (Universal Subscriber Identity Module) card attached to the terminal indicates that the uplink wireless communication status information should be requested , the host device is informed to the host device via the relay device. A request unit that requests transmission of uplink wireless communication status information with the relay apparatus to the own apparatus using a channel in the first plane;
A reception unit that receives the wireless communication status information from the host device using the channel in the first plane via the relay device;
The first plane includes a user data channel, and the second plane includes a control data channel.
Wireless terminal. A wireless terminal that communicates with the relay device using the first plane and the second plane,
When the USIM setting information acquired from the USIM (Universal Subscriber Identity Module) card attached to the terminal indicates that the uplink wireless communication status information should be requested , the host device is informed to the host device via the relay device. A request unit that requests transmission of uplink wireless communication status information with the relay apparatus to the own apparatus using a channel in the first plane;
A reception unit that receives the wireless communication status information from the host device using the channel in the first plane via the relay device;
The first plane includes a control data channel, and the second plane includes a user data channel.
Wireless terminal. A relay device that wirelessly communicates with a wireless terminal using the first plane and the second plane and performs wired communication with a host device,
The uplink radio communication status information between the radio terminal and the own apparatus should be transmitted to the radio terminal using the channel in the first plane, and the uplink radio communication status information should be requested.
If requested by the wireless terminal USIM (Universal Subscriber Identity Module) setting information is equipped with a USIM card that is stored indicating a notification to the operating condition confirmation unit that the host device for storing radio communications condition information the request has And transmitting uplink radio communication status information between the radio terminal and the own device acquired from the operation status confirmation unit of the higher-level device to the radio terminal using the channel in the first plane. A transmission / reception unit
The first plane includes a user data channel, and the second plane includes a control data channel.
Relay device. A relay device that wirelessly communicates with a wireless terminal using the first plane and the second plane and performs wired communication with a host device,
Indicates that uplink radio communication status information between the radio terminal and the device itself should be transmitted to the radio terminal using a channel in the first plane, and that uplink radio communication status information should be requested When a request is received from a wireless terminal equipped with a USIM card storing USIM (Universal Subscriber Identity Module) setting information , the request is notified to the operation status confirmation unit of the host device that accumulates wireless communication status information. Transmission / reception of uplink wireless communication status information between the wireless terminal and the own device acquired from the operation status confirmation unit included in the higher-level device to the wireless terminal using the channel in the first plane Part
The first plane includes a control data channel, and the second plane includes a user data channel.
Relay device.

Images