[0001]The disclosure herein relates to a wireless communication system that performs communication control for coverage improvement.
BACKGROUND
[0002]In 3GPP Long Term Evolution (LTE), improvement and standardization of technology for the realization of higher speed communications decrease in communication quality due to rapid increase in recent mobile traffic is being performed. Moreover, it is also being standardized technique to avoid an increase in control signaling load due connection to the vast number of Machine-to Machine (M2M) terminal of LTE networks expected future (Non-patent Document 1). Here, M2M terminal refers to a terminal that performs communication such as a human does not intervening. M2M terminal machine (eg, vending machines, gas meters, electric meters, automobiles, railway vehicles, ships) and the sensor is mounted on a variety of devices such as (eg, environmental, agricultural, sensors about traffic, etc.). In LTE, referred to communication by M2M terminal and Machine Type Communication (MTC), referred to as terminal MTC terminal for MTC (MTC User Equipment (MTC UE)).
[0003]
　M2M service operators there is a need to distribute a large number of M2M terminals on the market, but there is a limit to the cost applied to the per M2M terminal. For this purpose, M2M terminal to be implemented at low cost, that can communicate with low power consumption, etc. is required. Further, as one use case of MTC UE, when performing communication while being fixed or statically installed in a building (e.g., a building) it is assumed. In this case, there is always less likely radio quality of the MTC UE, usually of the UE, which generally have a mobility compared to (eg, mobile phone, smart phone, tablet computer, a notebook personal computer (notebook PC)) technology for coverage improvement is needed. As the function restriction for cost reduction, for example, the maximum transmission power is small, the number of receiving antennas is small, it does not support the high-order modulation scheme (eg 64 Quadrature Amplitude Modulation (64QAM)), the available radio bandwidth is a narrow-band (eg 1.25 MHz), and the like are considered, thereby the maximum transmission rate of the MTC UE is reduced. Accordingly, the communication characteristics of the MTC UE is expected to be inferior In LTE, the normal UE (i.e., coverage) standardization of techniques for improving is performed (Non-Patent Document 2). Hereinafter, an example of a technology for improving the coverage of the MTC UE being considered in LTE. Note that coverage improvement technologies (coverage improvement process) for the MTC UE described below, can also be referred to as processing for improving or enhancing the communication characteristics or communication quality of MTC UE. UE state to apply these special coverage improvement technique is called coverage improvement mode (Enhanced Coverage Mode (ECM)).
[0004]
　Characteristics that are improved by the ECM (detection characteristics in other words eNB) transmitting characteristics of the reception characteristics, Physical Random Access Channel (PRACH) preamble Physical Broadcast Channel (PBCH), Physical Downlink Shared reception characteristics Channel (PDSCH), Physical Uplink transmission characteristics of the Shared Channel (PUSCH), and the like. PBCH is a downlink broadcast channel used for transmitting the cell common broadcast information by eNB. PRACH is a physical uplink channel used for initial access to the UE in the radio base station (eNB). PDSCH is a downlink physical channel used for data reception by the UE. PUSCH is a physical uplink channel used for data transmission by UE.
[0005]
　One of the process that is being considered to improve the reception characteristics of the PBCH is to repeat the transmission of the notification information by a predetermined number of times extra PBCH than normal (non-patent document 3). One of the processes has been studied to improve the transmission characteristics of the PRACH is to repeat the transmission of the PRACH (i.e. preamble) a predetermined number of times (non-patent document 4). Furthermore, one of the processing that has been studied to improve the transmission characteristics of the reception characteristics and PUSCH of PDSCH is to repeatedly transmit the PDSCH and PUSCH over a plurality subframes (Non-Patent Document 5). By these processes, it is expected that normally be degraded from UE to improve the communication characteristics of the MTC UE expected.
[0006]
　These coverage improvement process in the ECM, be performed as an object the MTC UE performing delay-insensitive access (delay tolerant access) is assumed. delay tolerant access is defined as a new EstablishmentCause specified by RRC Connection Request message, it is used to control, for example, overload. delay tolerant access is the MTC UE to perform delay tolerant of MTC application is intended primarily. For example, the metering service (meter reading service), the transmission to the meter reading report remote system (or in strict communication cycle) in real time without the need to perform might tolerate long delays in the transmission of meter reading report. The eNB, delay tolerant when applying the overload control for access, may reject the RRC Connection Request sent by the RRC Connection Request message with an EstablishmentCause specified in delay tolerant access.
CITATION
Non-patent literature
[0007]
非特許文献1 : 3GPP TR 37.868 V11.0.0 (2011-09), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on RAN Improvements for Machine-type Communications; (Release 11)”, 2011年9月
非特許文献2 : 3GPP TR 36.888 V12.0.0 (2013-06), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on provision of low-cost Machine-Type Communications (MTC) User Equipments (UEs) based on LTE (Release 12)”, 2013年6月
非特許文献3 : 3GPP R1-135943, Vodafone, “Way Forward on P-BCH for MTC enhanced coverage”, 3GPP TSG RAN WG1 #75, San Francisco, USA, 11-15 November 2013
非特許文献4 : 3GPP R1-135944, Vodafone, “Way Forward on PRACH for MTC enhanced coverage”, 3GPP TSG RAN WG1 #75, San Francisco, USA, 11-15 November 2013
非特許文献5 : 3GPP R1-136001, Vodafone et al. “Way forward on PDCCH, PDSCH, PUCCH and PUSCH for MTC enhanced coverage”, 3GPP TSG RAN WG1 #75, San Francisco, USA, 11-15 November 2013
Summary of the Invention
Problems that the Invention is to Solve
[0008]
　Present invention have studied about various problems when applying the coverage improvement process in ECM in MTC UE (M2M terminal). For example, the repetition of PBCH for being applied in common to MTC UE in a cell, repeating the repetitive and PDSCH / PUSCH of the RACH is applied separately to each MTC UE.
[0009]
　In one example, ECM, particularly MTC UE individual coverage improvement process (eg, repetition of RACH, repetition of PDSCH / PUSCH), Whether or not is needed for a particular MTC UE may be determined by the eNB . For example, the repetition of PDSCH / PUSCH, since that requires allocation of radio resources by eNB, might have relevance to the need for MTC UE individual coverage improvement process is determined at eNB.
[0010]
　However, considering from another viewpoint, is likely to cause problems that the need for ECM is determined at eNB. For example, if the need for ECM (especially MTC UE individual coverage improvement process) for a particular MTC UE is the MTC UE until it is determined by the eNB and can not be started ECM, that certain MTC UE in communication characteristics due to ECM You can not enjoy improve until the end of the judgment in the eNB. Therefore, there is a possibility that the delay time of the MTC UE until enjoy improved communication characteristics by ECM increases. Furthermore, considering the worst case, the first access from the MTC UE to eNB (eg, random access using the PRACH, or a wireless connection (establishment procedure Radio Resource Control (RRC) Connection)) may even result in failure unknown.
[0011]
　Therefore, one of the objective to be achieved is the embodiment disclosed herein, the determination special coverage improvement process for MTC UE the need (eg, coverage improvement process in ECM) in MTC UE be as MTC UE that is modified to the (M2M terminal), it is to provide a base station, a method, and a program. Incidentally, this objective should more embodiments disclosed herein is noted that only one of several objects of it and to achieve. Other objects or problems and novel features will become apparent from the description, or the accompanying drawings of this specification.
Means for Solving the Problems
[0012]
　In one embodiment, M2M terminal includes a wireless communication unit and a control unit. The wireless communication unit is configured to communicate with the base station. Wherein the control unit, together with the first notification received from the base station, the when establishing a wireless connection with the base station after receiving the first notification, or after reception of the first notification M2M during the procedure of establishing a bearer between the terminal and the core network is performed, and is configured to transmit a second notification to the base station. Wherein the first notification indicates whether or not a predetermined coverage improvement process in the cell of the base station that the M2M terminal stays are supported. The second notification indicates that the predetermined coverage improvement process is that or run is required by the M2M terminal.
[0013]
　In one embodiment, the base station includes a radio communication unit and control unit. The wireless communication unit is configured to communicate with M2M terminal. Wherein the control unit, to transmit a first notification that the predetermined coverage improvement process for the M2M terminal in the cell of the base station that the M2M terminal stays are supported via the wireless communication unit It is configured.
[0014]
　In one embodiment, the method performed by the M2M terminal establishes a wireless connection with the (a) to the first notification received from the base station, and (b) said base station after receiving the first notification when the, or during the procedure for establishing a bearer between the M2M terminal and the core network after receiving the first notification is performed, comprising, transmitting a second notification to the base station. Wherein the first notification indicates whether or not a predetermined coverage improvement process in the cell of the base station that the M2M terminal stays are supported. The second notification indicates that the predetermined coverage improvement process is that or run is required by the M2M terminal.
[0015]
　In one embodiment, the method performed by the base station, in the cell a first notification that the predetermined coverage improvement process is supported for the M2M terminal in the cell of the base station M2M terminal stays It includes transmitting to.
[0016]
　In one embodiment, the program includes the when loaded into a computer, instructions for performing any of the methods described above to a computer (software code).
Effect of the invention
[0017]
　According to the above-described embodiment, MTC UE that is modified to a special need coverage improvement process for MTC UE to be determined in MTC UE (M2M terminal), a base station, a method, and a program It can be provided. This effect should be noted that only one of the plurality of effects are expected to be provided by a plurality of embodiments disclosed herein.
BRIEF DESCRIPTION OF THE DRAWINGS
[0018]
FIG. 1 is a diagram illustrating a configuration example of a wireless communication system according to the first embodiment.
[2] is a sequence diagram showing an example of a communication procedure according to the first embodiment.
3 is a sequence diagram showing another example of a communication procedure according to the first embodiment.
4 is a sequence diagram showing an example of a communication procedure according to the second embodiment.
5 is a sequence diagram showing an example of a communication procedure according to the third embodiment.
6 is a sequence diagram showing an example of a communication procedure according to the fourth embodiment.
7 is a block diagram showing a configuration example of a M2M terminal (MTC UE) according to an embodiment of the present invention.
Is a block diagram showing a configuration example of FIG. 8 base station according to an embodiment of the present invention (eNB).
DESCRIPTION OF THE INVENTION
[0019]
　Hereinafter, specific embodiments will be described in detail with reference to the drawings. In the drawings, the same or corresponding components are denoted by the same reference numerals, for clarity of description, repeated explanation is omitted as appropriate.
[0020]
　A plurality of embodiments described below can can either be carried out independently, also be implemented in appropriate combination. These several embodiments have different novel features together. Accordingly, the plurality of embodiments, contribute to solving the different purpose or task to each other, which contributes to achieve different effects from each other.
[0021]

　FIG 1 shows a configuration example of a wireless communication system according to this embodiment. The wireless communication systems provide communication services, both for example, voice communication or packet data communication, or these. Referring to FIG. 1, the wireless communication system includes M2M terminal 11 (11A, 11B, 11C) , normal radio terminal 12 is not a M2M terminal, the base station 13, and a core network 14. Wireless terminal 12 is, for example, a mobile phone, a smart phone, a tablet computer or a notebook PC,. M2M terminal 11A, 11B, and 11C, and the radio terminal 12 is located in the cell 130 of the base station 13. In the present embodiment, the wireless communication system is described as a 3GPP LTE system. That, M2M terminal 11 corresponds to the MTC UE, the radio terminal 12 corresponds to a normal UE not MTC UE, the base station 13 corresponds to the eNodeB (eNB), the core network 14 to the Evolved Packet Core (EPC) Equivalent to.
[0022]
　In Figure 1, MTC UE11A, in order to away the distance from eNB13 compared to MTC UE11B, it is assumed that propagation loss is deteriorated greatly radio quality. Further, MTC UE11C is installed in a building (e.g. building), it is assumed that the radio quality is deteriorated as compared with the case of being installed outdoors. Also, if MTC UE 11 (11A, 11B, and 11C) are limiting capability or capabilities than ordinary UE 12 (eg, the maximum transmission power is small, the number of reception antennas is small, supports higher order modulation city, etc.) when having a radio quality degradation is expected to be more pronounced. Thus, MTC UE 11 according to this embodiment, it supports the above Enhanced Coverage Mode (ECM), and is configured to be able to perform a coverage improvement process in ECM.
[0023]
　As already mentioned, the coverage improvement process in ECM may also be referred to as processing for improving or enhancing the communication characteristics of the MTC UE (communication quality). Coverage improvement processing in the ECM, as already mentioned, the following (a) may comprise - at least one of (d), include other different processing from these, for example, the (e) ~ (f) But good:
(a) repeating the transmission of the broadcast information by only extra PBCH predetermined number of times than normal,
(b) PPACH repeating a predetermined number of times transmission of the (PRACH preamble),
the PDSCH over (c) a plurality subframes repeating transmission,
(d) repeating the transmission of the PUSCH over multiple sub-frames,
(e) PDSCH or PUSCH or both power spectral density (power spectral density (PSD)) to be higher that (PSD boosting),
(f ) to the frequency hopping between the PDSCH or PUSCH or both repeated transmission.
[0024]
　Here, the sub-frame is a unit constituting the LTE radio frame. The length of one radio frame is 10 ms, one radio frame consists of 10 subframes (subframe). Therefore, the length of one subframe is 1 ms. One subframe includes 14 symbols in the time domain (if the uplink single carrier frequency division multiple access (SC-FDMA) symbols, if the downlink orthogonal frequency division multiplexing (OFDM) symbols).
[0025]
　Then hereinafter, a description will be given of a communication control for the ECM according to the present embodiment. eNB13 according to the present embodiment, the predetermined coverage improvement processing (i.e., coverage improvement process in ECM) cell a first notification that is supported in the cell 130 of eNB13 for MTC UE (M2M terminal) to send to 130. In the first notification, whether ECM is supported, may be indicated by the base station units (i.e. supported by all the cells in the eNB13), it may be indicated on a cell-by-cell basis. Meanwhile, MTC UE 11 receives the first notification from the eNB13. The MTC UE 11 transmits a second notification to the eNB13 after receiving the first notification. MTC UE 11 in response to receiving the first notification from the eNB13, may transmit the second notification. Here, the second notification while the when establishing a wireless connection (RRC Connection) with the eNB13, or procedure for establishing a bearer between the MTC UE 11 and EPC14 (Evolved Packet System (EPS) bearer) is performed It is sent from the MTC UE11 to eNB13 to. Furthermore, the second notification indicates that it is possible or run is required by the coverage improvement process MTC UE 11 in ECM.
[0026]
　According to the present embodiment, following effects are expected. That is, if ECM for MTC UE 11 (in particular, individual coverage improvement process specific MTC UE 11) when the need of the MTC UE 11 can not start an ECM to be determined by eNB13, MTC UE 11 is improved communication characteristics by ECM can not enjoy until the end of the determination at eNB13. Therefore, there is a possibility that the delay time of the MTC UE 11 until enjoy improved communication characteristics by ECM increases. Furthermore, considering the worst case, the first access from the MTC UE 11 to eNB13 (e.g., establishing procedure of the random access using the PRACH, or a wireless connection (RRC Connection)) even might result in failure.
[0027]
　To address these problems, eNB13 according to the present embodiment transmits the first notification described above in the cell 130. Thus, MTC UE 11 according to the present embodiment, it is possible to know that the cell 130 of eNB13 supports ECM, upon establishment of the wireless connection (RRC Connection), or between the EPS bearer establishment procedure, coverage improvement processing in the ECM of the second notification indicating that it is possible or run is required by MTC UE 11 can notify the eNB13. UE including MTC UE 11 is generally before consisting idle (RRC_IDLE) in response to a periodic or non-periodic communication opportunities arrives to Connected state (RRC_CONNECTED), measures the radio qualities in the idle state doing. Thus, MTC UE 11 is the first notification received from the eNB in ​​the idle state, the radio quality measured in the idle state may be determined in advance prior necessity of ECM the advent of communication opportunities with. That way, it is possible to contribute to a reduction of the incoming and eNB13 ECM delay time due to waiting for the determination of the necessity of the following communication opportunity (delay time until the ECM starts).
[0028]
　Here, describing the definition of idle and Connected state as used herein the term. An idle state is a state where the wireless connection is released between the UE and eNB. Thus, eNB has no information about the UE in an idle state (UE context). Location of the UE in the idle state, the location registration area in the core network (eg, tracking area or routing area) is grasped in units. The core network can be reached by paging the UE in an idle state. Further, UE in idle state can not perform a unicast data transfer between the eNB. Therefore, UE in an idle state must transition to Connected state in order to perform unicast data transfer. Examples of idle, (1) Universal Terrestrial Radio Access Network RRC in (UTRAN) idle state, (2) RRC_IDLE in Evolved UTRAN (E-UTRAN) state and, (3) WiMAX (IEEE 802.16-2004), Mobile WiMAX (IEEE 802.16e-2005), and a Idle state in WiMAX2 (IEEE 802.16m).
[0029]
　Connected state with respect to this is the state the UE has connected to the eNB. Thus, eNB holds information (UE Context) related to the UE Connected state. Location of the UE in the Connected state is grasped by the cell unit in the core network (or base station units). UE of Connected state, generally, it is possible to perform the unicast data transfer between the eNB. However, CELL_PCH state and URA_PCH state in the UTRAN, but the UE context is held by the base station (NodeB), a state that has not been assigned a dedicated channel to the UE for both uplink and downlink. Examples of Connected state includes a Connected state in the RRC connected state, (2) RRC_CONNECTED state in E-UTRAN, and (3) WiMAX, Mobile WiMAX and WiMAX2 in (1) UTRAN. Incidentally, RRC the connected state in the UTRAN includes a CELL_DCH state, CELL_FACH state, CELL_PCH sate, and URA_PCH state.
[0030]
　Then, in the following description the eNB13 of first notification mentioned above transmission method to MTC UE 11, and in order for a specific example of a method of transmitting from a second notification MTC UE 11 to eNB13.
[0031]
　First notification, the wireless connection to the eNB13 do not have a (RRC connection), i.e. are preferably transmitted in a receivable broadcast channel in MTC UE 11 is idle. In other words, the first notification is preferably idle MTC UE 11 is capable of broadcast information received. Specifically, it may be used for transmission, one of the LTE logical channel Broadcast Control Channel (BCCH) of the first notification.
[0032]
　Further by way, first notification is preferably sent in receivable broadcast channels even in the MTC UE 11 is idle (RCC_IDLE) and the detached state (EMM-DEREGISTERED). Detached state (EMM-DEREGISTERED) represents the EPS Mobility Management (EMM) state of the LTE. That is, the detached state (EMM-DEREGISTERED) is, UE core network (eg, EPC) have not been registered in the mobility management element in (eg, Mobility Management Entity (MME)), have been carried out mobility management of the UE It means there is no state. UE detached state, the position information in the MME is not grasped, not reachable by paging from a core network (EPC) (unreachable). UE detached state, in order to communicate, the initial cell selection (i.e., the initial cell search) is performed to establish a eNB and radio connection must be performed the location registration to the core network (EPC). Incidentally, BCCH can be received even in the MTC UE 11 is idle (RCC_IDLE) and the detached state (EMM-DEREGISTERED).
[0033]
　BCCH is mapped to a transport channel Broadcast Channel (BCH) or Downlink Shared Channel (DL-SCH). Furthermore, BCH the BCCH is mapped is transmitted from eNB13 using a physical channel Physical Broadcast Channel (PBCH). PBCH is transmitted using a predetermined resource blocks of the first subframe of each radio frame is updated at 40 millisecond period (fourth radio frame periods). Broadcast information that is transmitted using the PBCH is a Master Information Block (MIB). Accordingly, the first notification may be included in the MIB.
[0034]
　On the other hand, DL-SCH which BCCH is mapped is transmitted from eNB13 using a physical channel Physical Downlink Shared Channel (PDSCH). Normal applications of PDSCH is a transmission of user data, transmission of BCCH (i.e. broadcast information) is defined as one of the particular application (special the uses) the PDSCH. Resource blocks used for the BCCH (broadcast information) is represented by the Physical Downlink Control Channel (PDCCH) in the control message. Broadcast information that is transmitted using the PDSCH is a System Information Blocks (SIBs). Thus, the first notice, either existing SIBs, may be included, for example, System Information Block Type 1 (SIB1). The first notification, M2M, MTC UE, or may be included in the newly defined SIB for ECM.
[0035]
　First notification may be explicitly indicates whether the ECM Support of the cell 130 of eNB13 (eg, flag bit), may be implicitly indicated. In the first notification, whether ECM is supported, may be indicated by the base station units (i.e. supported by all the cells in the eNB13), it may be indicated on a cell-by-cell basis. Implicit first notification may include configuration information (ECM radio resource configuration or ECM configuration) for coverage improvement process in ECM.
[0036]
　ECM configuration or ECM configuration may include, for example, at least one of information shown below:
and setting information related to the reception of the broadcast information (PBCH),
settings for the reception of system information (System Information Block (SIB)) information,
setting information relating to the reception of the paging (paging Channel (PCH)),
the setting information concerning the reception of the & downlink control information (Physical downlink control Channel (PDCCH) ),
setting information related to the reception of, downlink data (PDSCH),
- uplink setting information on the transmission of control information (Physical uplink control Channel (PUCCH) ),
setting information relating to the transmission of the-uplink data (PUSCH),
setting related-radio quality measurement report (measurement report) information.
[0037]
　Setting information related to the reception of the setting information and the system information about the reception of the broadcast information (PBCH) (SIB), for example, which sub-frame and / or broadcast information and (what kind of) the system information in which OFDM symbols are transmitted repeatedly and either may be information that shows that. Setting information related to the reception of the paging may be, for example, information indicating which paging subframe is transmitted repeatedly. Or configuration information about the reception of the reception and downlink data (PDSCH) of the downlink control information (PDCCH), for example, may be information indicating whether they are transmitted many times repeatedly, it is repeatedly transmitted in every subframe it may be information that shows. Or configuration information about the transmission of the transmission and the uplink data (PUSCH) in the uplink control information (PUCCH) is, for example, may be information indicating whether they are transmitted many times repeatedly, it is repeatedly transmitted in every subframe it may be information that shows. Configuration information about the radio quality measurement report may be the offset value and the threshold for application to the radio quality of the measurement result (Measurement result) while running the ECM, the radio quality to be applied during execution of an ECM or an offset value or the threshold in the determination of the measurement result report.
[0038]
　Next, a description will be given of the second notification. The second notice, for example, a request message for requesting the establishment of a radio connection (RRC connection), i.e. may be transmitted with the RRC Connection Request message. RRC Connection Request message, because a message is sent to the first RRC connection establishment procedure, the second notification may also be referred to be transmitted during the establishment procedure of a wireless connection (RRC connection). Incidentally, when viewed from another perspective, RRC Connection Request message is transmitted in the third step of the random access procedure (Random Access Channel (RACH) procedure). Therefore, if the RRC Connection Request message is utilized, the second notification may also be referred to be transmitted during the random access procedure (RACH procedure).
[0039]
　In another example, the second notification completion message indicating establishment completion of wireless connection (RRC connection), i.e. may be transmitted with the RRC Connection Setup Complete message. RRC Connection Setup Complete message, because it is the last message sent by the established procedures of the RRC connection, the second notification may also be referred to be transmitted during the establishment procedure of a wireless connection (RRC connection). Further, RRC Connection Setup Complete message, NAS message including (eg, NAS: Attach Request: Service Request, NAS). RRC Connection Setup Complete message includes NAS message is the first message sent by the establishment procedure of the EPS bearers. Therefore, if the RRC Connection Setup Complete message is used, the second notification may also be referred to be transmitted during the bearer establishment procedure.
[0040]
　By using the RRC Connection Request message or RRC Connection Setup Complete message for transmission of the second notification, MTC UE 11 is that it is possible or execution itself is in need of ECM, establishment procedure of the wireless connection it is possible to quickly notify the eNB13 between. Thus, for example, eNB13 may include ECM set in the setting of the wireless connection established for the MTC UE 11, the communication with the MTC UE 11 with a coverage improvement process of ECM can be started promptly. Incidentally, from the viewpoint of establishing a radio connection (RRC connection), similar to the RRC Connection Setup Complete message, RRC Connection Reestablishment Complete that a message may be performed to transmit the second notification utilizing course.
[0041]
　In yet another example, the second notification may be transmitted in the radio connection random access procedure is performed prior to the establishment of (RRC connection) (RACH procedure). Specifically, it may be transmitted in the PRACH preamble in the first step of the random access procedure (RACH procedure) is utilized for the second notification. In this case, the second notification, among the plurality of radio resources for the PRACH, the use special radio resource allocated for the ECM (eg, time, frequency, code, or a preamble sequence), and it may imply that it or is running ECM is required by MTC UE1.
[0042]
　Because PRACH preamble the PRACH can only send, MTC UE1 details of ECM required or performed by (for example, which of the plurality of coverage improvement process or a specifically required) it may be difficult to show a. Accordingly, this application might aforementioned RRC Connection Request message or RRC Connection Setup Complete message are suitable. However, by using the PRACH preamble for the second notification, as compared with the case of using the RRC Connection Request message or RRC Connection Setup Complete message, telling sooner eNB13 necessity or progress of ECM in MTC UE1 there is the advantage that it is possible.
[0043]
　Then, in the following, a specific example of a process for determining the necessity of ECM in MTC UE 11. MTC UE 11, when the cell 130 of eNB13 based on the first notification from the eNB13 recognizes that it supports the ECM, the MTC UE 11 ECM (i.e., improved treatment coverage with ECM) is required whether a it may be determined.
[0044]
　MTC UE 11, when judging that the ECM is required, may initiate a possible execution of the plurality of coverage improvement process in ECM. For example, MTC UE 11 may receive the PBCH that is repeatedly transmitted, or in a random access procedure to transmit repeatedly PRACH preamble, or may start both. Accordingly, the first notification may indicate that the ECM is performed by MTC UE 11.
[0045]
　On the other hand, for example, repeating the PDSCH / PUSCH requires allocation of radio resources by eNB13. Therefore, the addressed coverage improvement process necessary (eg, repetition of PDSCH / PUSCH) of the eNB13, MTC UE 11 may be reported that need to eNB13. It is also feasible process (eg, repeated reception of the PBCH, repeated transmission of the PRACH preamble) with respect to coverage improvement process in all of the ECM including, MTC UE 11 may report their need to eNB13. Thus, the first notice may indicate that it is the ECM needed by MTC UE 11.
[0046]
　Determining necessity of ECM in MTC UE 11 (coverage improvement process in the ECM), for example, access factor (Access cause) of MTC UE 11, terminal capability (UE capability data), the terminal information (UE information), communication characteristics (Communication performance ), and at least one may be performed in consideration of radio quality (radio quality).
[0047]
　Access factors, terminal capability, terminal information, described communication characteristics, and specific examples of the radio quality below. However, the access factor, terminal capability, terminal information, communication characteristics, and the contents of the radio quality is not limited to these examples.
[0048]
　Access factors may include, for example, at least one the following two of.
· RRC connection establishment of the purpose (Establishment Cause)
· type of service (Service type)
[0049]
　The purpose of the RRC connection establishment, for example, (a) emergency call (emergency), (b) high priority access (highPriorityAccess), (c) access for the terminal end communication (mt-Access), signaling by the terminal originating ( mo-Signalling), (d) the terminal transmitting the data transmission by (mo-data), (e) delay-insensitive access (delayTolerantAccess), (f) low priority access (lowPriorityAccess), (g) access for small data communication (smallDataAccess), (h) access for small packet communication (smallPacketAccess), (i) limited access (limitedAccess), (j) access for limited services (limitedService), (k) M2M-type access (m2mAccess), or (l) access by ECM (ecmAccess), may be specified.
[0050]
　Service type, for example, (a) real-time service may be designated non-real time service, or (c) M2M communication, (b).
[0051]
　Terminal capabilities may include, for example, at least one of the following three.
- radio access capability (Radio access capability data)
, device capability (Device capability data)
, the terminal category (UE category)
[0052]
　Whether the radio access capability, for example, supports (a) UE information indicating whether it supports the terminal function defined in 3GPP LTE (e.g. flag bit), or (b) UE is ECM information indicating whether may contain. To indicate whether the UE supports ECM, for example, "EcmSupport" that information element (Information Element (IE)) may be defined. For example, true value of "EcmSupport" is, ECM indicates that it is supported (the Supported), the false value is not ECM supports showing a (NotSupported). In addition, IE called "EnhancedCoverageMode" may be defined. For example, when the EcmSupport is set to the Supported, indicating that the UE supports ECM. Also, if the UE has not been support ECM, to EcmSupport may set a NotSupported, may indicate unsupported by the IE is not transmitted.
[0053]
　Device capabilities, for example, information indicating that (a) UE is MTC UE, (b) UE communication performance (usually compared to UE) information indicating that it is limited, or (c) a specific information indicating that performing only communication (e.g. M2M communication) may contain.
[0054]
　Terminal category, include information, which indicates one of (a) information indicating any of the terminal category defined by 3GPP LTE, or (b) access is defined in 3GPP LTE classes (Access Class) good. Terminal category or access classes may be newly defined for MTC UE performing M2M communication. For example, new categories for MTC UE which is function restriction to implement at a low cost (eg, category 0) is may be defined, only the communication or infrequent to assume that communicating infrequently allow access class (AC) may be newly defined.
[0055]
　Terminal information may include, for example, at least one of the following three.
- terminal type (UE type)
, device type (Device type)
, the terminal context (UE context)
[0056]
　Terminal type, for example, (a) UE information indicating which normal UE (non MTC UE) and MTC UE, the information (or UE indicating whether the moving (b) UE does not move information indicating that), or (c) information indicating whether there is a power supply to the UE (power supply), may contain.
[0057]
　Device type, for example, a, (a) information indicating the type of the UE implemented Operating System (OS), or (b) information indicating the type of M2M communication the UE performed (i.e., M2M sub-category information) it may also include a.
[0058]
　Terminal context, for example, (a) information of the above terminal capabilities, (b) set RRC control information to the UE (information contained in RadioResrouceConfigCommon IE and ArueiioResourceConfigDediacted IE, etc.), (c) information on the UE mobility (mobility information), indicating whether running ECM in (d) of the information indicating whether the UE is running ECM (ECM execution information), or (e) when the UE is the previous (e.g., last RRC_CONNECTED) information (ECM status information), may include a.
[0059]
　Communication characteristics may include, for example, at least one the following two of.
· Characteristic measurement results (Performance Measurement result (eg, L2 Measurement))
· communication statistics quality (Statistical communication quality (eg, KPI ))
[0060]
　Characteristic measurements, (a) the block error rate measurement (Block Error Rate), (b) packet error rate measurement results (Packet Error Rate), (c) Throughput measurement result (eg, Scheduled IP Throughput), (d) packet loss measurements (packet loss Rate), or may contain (e) a packet discard measurement results (packet discard Rate).
[0061]
　Communication statistics quality, for example, (a) a handover attempts or handover attempt rate, (b) a handover success rate or handover failure rates, (c) a communication distance or a communication frequency, (d) the packet generation intervals or packet occurrence frequency, ( e) packet arrival intervals (packet inter-arrival time) or packet arrival rate (packet inter-arrival rate), a, (f) access interval or access frequency, or (g) spacing or frequency of the RRC connection establishment or NAS connection establishment it may also include a.
[0062]
　Radio quality may include, for example, at least one the following two of.
And the reference signal reception quality (Reference Signal (RS) received The quality)
, channel quality indicator (CQI)
[0063]
　Reception quality of the reference signal (RS), for example, received power of the downlink RS in UE (RSRP), (b) the reception quality (RSRQ), or received signal strength (RSSI), may contain.
[0064]
　The timing determines the necessity of MTC UE 11 is ECM has many variations. For example, MTC UE 11, when the power of the MTC UE 11 is turned ON, MTC UE 11 initial cell selection in idle (RRC_IDLE) (i.e., initial cell search) when performing, or MTC UE 11 is idle (RRC_IDLE when performing cell reselection in), it may determine the necessity of ECM. MTC UE 11 that is determined in advance whether or not the ECM when in idle state, the delay time due to waiting for the determination of the necessity of the ECM in eNB13 after arrival of communication opportunities (delay time until the ECM starts) It can contribute to the reduction.
[0065]
　Alternatively, MTC UE 11 periodically or non-periodic communication opportunities (e.g., periodic communication permission period, aperiodic generation of uplink transmission data or reception of paging) when arrives, radio it may determine the necessity of ECM prior to accessing the eNB13 for establishing a connection. Further, MTC UE 11 during accessing the eNB13 for establishing a wireless connection (eg, during RACH access procedure, or RRC Connection establishment between the procedure) in may determine the necessity of ECM. Furthermore, MTC UE 11 may determine the necessity of ECM after the wireless connection (RRC connection) is established.
[0066]
　The operation to be performed with respect to ECM (i.e., control of the reception or transmission of MTC UE 11 or eNB13) may be defined by subdividing the previously multistage (multilevel). In this case, MTC UE 11 is not only determined whether the ECM is required (or whether or not to execute ECM), which step (level) operation is necessary or the (or any stage of operation determines whether to perform), the determined step (level) may be reported to the eNB13 in the second notification. eNB13, based on the second notification from MTC UE 11, may be allowed operating phase of the reported ECM (level) from MTC UE 11, and the operation phase of the ECM reported from MTC UE 11 (level) determining the different stages, the determined step may notify the MTC UE 11. That, eNB13 may have the authority to finally determine the operating phase of the ECM should MTC UE 11 does.
[0067]
　Also, if the MTC UE 11 determines to execute the ECM, or when eNB13 determines that to perform the ECM to MTC UE 11, MTC UE 11 can be performed to continue ECM after it became RRC_IDLE from RRC_CONNECTED good. Further, MTC UE 11, when the MTC UE 11 determines to execute the ECM, or when eNB13 determines that to perform the ECM to MTC UE 11, to continue the ECM during performing delay-insensitive access (delay tolerant access) it may be executed.
[0068]
　Further, MTC UE 11, after judging whether ECM is required (or whether to perform ECM) First, whether to continue running, ECM based on communication characteristics or radio quality of its own it may be determined. For example, MTC UE 11 is block obtains an error rate or packet error rate, or both as the communication characteristics of the MTC UE 11, may be interrupted ECM if they were determined to be smaller than the predetermined threshold value (or discontinued). In combination or with which Alternatively, MTC UE 11 obtains the RSRP or RSRQ or both as radio quality may be interrupted ECM if they were determined to be greater than the predetermined threshold value (or discontinued) .
[0069]
　Figure 2 is a sequence diagram showing an example of the operation of the MTC UE 11 and eNB13 according to the present embodiment. Incidentally, Figure 2 describes only messages necessary for explanation of this embodiment, it is omitted several messages included in the procedure defined in LTE.
[0070]
　In step S101 in FIG. 2, eNB13 broadcasts the first notification indicating that it supports the ECM to the cell 130 (System Information Block Type 1x). First notification, as shown in FIG. 2, may be included in any of the SIBs. Moreover, as already mentioned, the first notification may be explicitly indicates whether the ECM Support of eNB13 (or cell 130 of eNB13) (eg, flag bit), even implicitly indicated good. Implicit first notification may include the setting of a radio resource information (ECM radio resource configuration) used in ECM.
[0071]
　In step S102, MTC UE 11 determines (ECM decision) ECM is (whether or not to execute or ECM) whether it is necessary. As already mentioned, MTC UE 11, for example, periodic or non-periodic communication opportunities (e.g., periodic communication permission period, aperiodic generation of uplink transmission data or reception of paging) that has arrived depending on, determination may be performed in step S102. Alternatively, MTC UE 11, when the power of the MTC UE 11 is turned ON, when the MTC UE 11 initial cell selection in idle (RRC_IDLE) (i.e., initial cell search) is performed, or MTC UE 11 is idle when performing cell reselection in a state (RRC_IDLE), determination may be performed in step S102.
[0072]
　Determination in step S102 is, as already mentioned, can be performed in consideration of various parameters. For example, the determination may be made based on whether ECM in cell 130 MTC UE 11 stays (or eNB13 managing the cell) is supported. This determination may be made based on whether or not support ECM as MTC UE 11 itself terminal capability (or device capabilities). This determination is access factors to eNB13 may be performed based on whether the delay-insensitive access (delay tolerant access). This determination is the radio quality of the MTC UE 11 may be performed based on whether less than a predetermined threshold value.
[0073]
　Figure 2 shows the case where ECM is required by the MTC UE 11. Accordingly, in step S103, MTC UE 11 initiates execution of ECM (ECM start). Then, in step S104 ~ S108, MTC UE 11 has access to eNB13 while ECM of operation (coverage improvement process).
[0074]
　Specifically, in step S104, MTC UE 11 performs preamble transmission of random access (PRACH Preamble). In the example of FIG. 2, for the transmission of PRACH preamble radio resources (e.g. time-frequency or code, such as a preamble sequence) specific to the ECM has been assigned, or is available. Thus, MTC UE 11 transmits a PRACH preamble using specific radio resource to the ECM.
[0075]
　In step S105, eNB13, in response to the detection of the PRACH preamble, transmits a random access response (Random Access Response). Incidentally, eNB13, by PRACH preamble is received in the specific radio resources to ECM, we can recognize that the source UE of the preamble is running ECM. Therefore, the radio resources also used for transmission of the random access response transmitted form of the random access response (eg, repeated transmission of the PDCCH or PDSCH) may be specific to the ECM. However, eNB13 is, at the time of PRACH preamble detection, it is not possible to identify the source UE of the preamble. PRACH preamble is because it does not include an identifier of the source UE.
[0076]
　In step S106, MTC UE 11 in response to receiving the random access response, and transmits the establishment request message of the radio connection (RRC connection) (RRC Connection Request). In step S106, MTC UE 11 may report to the eNB13 be delay-insensitive access (delay tolerant access). Further, MTC UE 11, for the transmission of RRC Connection Request message, may be utilized a unique radio resource or transmission mode (eg, repeated transmission of the PDSCH) to ECM.
[0077]
　In step S107, eNB13, in response to the RRC Connection Request from the MTC UE 11, transmits the setting information necessary for establishing the radio connection (RRC connection) (RRC Connection Setup). In step S108, MTC UE 11 sends a completion message indicating the establishment completion of wireless connection (RRC connection) (RRC Connection Setup Complete). At steps S107 and S108, it may be utilized specific radio resource or transmission form ECM.
[0078]
　In step S109, eNB13 transmits a radio resource configuration information (Radio Resource Configuration) to MTC UE 11. Transmission of step S108 is, NAS message from MTC UE 11 not shown (eg, NAS: Service Request, NAS: Attach Request) carried out in the EPS bearer establishment procedure based on. Radio resource configuration information transmitted in step S108 may include ECM setting information necessary for executing the ECM (ECM configuration). Coverage ECM setting information (ECM configuration), for example, to be applied for the transmission of user data or control data after establishment EPS bearer (eg, Hybrid Automatic Repeat Request (HARQ) ACK / NACK, and Channel State Information (CSI)) including the setting information regarding improvement processing (eg, repetition of PDSCH / PUSCH).
[0079]
　In step S110, MTC UE 11 in accordance with the radio resource configuration information and the ECM setting information, performs data communication with the coverage improvement process in ECM (M2M data with ECM).
[0080]
　Figure 3 is a sequence diagram showing another example of the operation of the MTC UE 11 and eNB13 according to the present embodiment. Incidentally, Figure 3 describes only messages necessary for explanation of this embodiment, it is omitted several messages included in the procedure defined in LTE.
[0081]
　Processing in steps S201 ~ S203 in FIG. 3 is the same as the processing in steps S101 ~ S103 in FIG. In step S204, MTC UE 11 performs preamble transmission of random access (PRACH Preamble). In the example of FIG. 3, for transmission of PRACH preamble unavailable specific radio resource to the ECM. Thus, MTC UE 11 transmits a PRACH preamble by using the same resource as the normal UE 12. In step S205, eNB13, in response to the detection of the PRACH preamble, transmits a random access response (Random Access Response).
[0082]
　In step S206, MTC UE 11 in response to receiving the random access response, and transmits the establishment request message of the radio connection (RRC connection) (RRC Connection Request). In step S206, MTC UE 11 may report to the eNB13 be delay-insensitive access (delay tolerant access). Furthermore, MTC UE 11 uses the RRC Connection Request message in step S206, and transmit a second notification that running the ECM (ECM activated). To send the second notification, for example, ECM status (or ECM process, ECM flag) that the information element (Information Element (IE)) may be defined. For example, when the ECM status is set to a true value or "Activated", indicating that the MTC UE 11 is performing the ECM. Conversely, when the ECM status is set to false value or "Not-activated", it may indicate that the ECM is not running. The second notification may be a 1-bit flag indicates that the ECM is running when the value is 1, also indicates that the ECM is not running when the value is 0 good.
[0083]
　During step S201 ~ S206 are, MTC UE 11 may be received using a process-specific predetermined downlink message (eg, paging, broadcast information (PBCH or SIB), etc.) to ECM.
[0084]
　In step S207, eNB13, in response to the RRC Connection Request from the MTC UE 11, transmits the setting information necessary for establishing the radio connection (RRC connection) (RRC Connection Setup). In step S208, MTC UE 11 sends a completion message indicating the establishment completion of wireless connection (RRC connection) (RRC Connection Setup Complete). The second notification (ECM activated), instead of the RRC Connection Request message in step S206, may be transmitted using an RRC Connection Setup Complete message in step S208.
[0085]
　Processing in steps S209 and S210 is the same as the processing in steps S109 and S110 in FIG.
[0086]

　configuration example of a wireless communication system according to this embodiment may be the same as in FIG. 1 as described for the first embodiment. In the present embodiment, modification of the detailed sequence described in the first embodiment is described. In the embodiment shown in FIGS. 2 and 3, until the execution of the ECM is determined in MTC UE 11, eNB13 showed an example to follow basically determined by the MTC UE 11. However, it may be the determination by the MTC UE 11 is always correct and is not necessarily the case. ENB23 according to this embodiment, rather than in full compliance determination by MTC UE 21, additionally it determines whether ECM which is required by the MTC UE 21 is truly needed.
[0087]
　Figure 4 is a sequence diagram showing an example of the operation of the MTC UE 21 and eNB23 according to the present embodiment. Incidentally, FIG. 4 describes only messages necessary for explanation of this embodiment, it is omitted several messages included in the procedure defined in LTE.
[0088]
　Processing in step S301 in FIG. 4 is the same as the processing in step S101 in FIG. In step S302, MTC UE 21 determines whether the ECM is required (ECM decision). Figure 4 shows the case where ECM is required by the MTC UE 21. Therefore, in step S303, MTC UE 21 transmits an establishment request message of the radio connection (RRC connection) (RRC Connection Request). In FIG. 4, the first and second steps of the random access procedure (i.e., transmission of PRACH preamble and Random replies Access Response) shown are omitted.
[0089]
　In step S303, MTC UE 21 may report to the eNB23 be delay-insensitive access (delay tolerant access). Furthermore, MTC UE 21 uses the RRC Connection Request message in step S303, and transmit a second notification that the ECM is required by itself (ECM Request). The second notification (ECM Request) requests the execution of the ECM (coverage improvement process in the ECM) for MTC UE 21 to ENB23.
[0090]
　In step S304, ENB23 in response to RRC Connection Request from the MTC UE 21, transmits the setting information necessary for establishing the radio connection (RRC connection) (RRC Connection Setup). In step S305, MTC UE 21 sends a completion message indicating the establishment completion of wireless connection (RRC connection) (RRC Connection Setup Complete). The second notification (ECM Request), instead of the RRC Connection Request message in step S303, may be transmitted using an RRC Connection Setup Complete message in step S305.
[0091]
　In step S306, eNB23 is, (ECM decision) determines whether it is necessary to ECM (or whether to execute the ECM for MTC UE 21) for MTC UE 21. In the determination of step S306, ENB23 may be used the same parameters and determination of necessity ECM in MTC UE 11 described in the first embodiment.
[0092]
　Figure 4 shows the case where it is determined in the ECM is required (or performs ECM) ENB23 for MTC UE 21. Therefore, in step S307, ENB23 transmits a radio resource configuration information (Radio Resource Configuration) in MTC UE21 (RRC Connection Reconfiguration). Transmission of step S307 is, NAS message from MTC UE 21 not shown (eg, NAS: Service Request, NAS: Attach Request) may be performed in the establishment procedure of the EPS bearer based on. Radio resource configuration information transmitted in step S307 may include ECM setting information necessary for executing the ECM (ECM configuration). Also, radio resource configuration information transmitted in step S307 may include an explicit indication information to execute the ECM against MTC UE 21.
[0093]
　In step S308, MTC UE 21 in response to an explicit or implicit indication of the eNB23 at step S307, it starts execution of the ECM (ECM start). In step S309, MTC UE 21 in accordance with the radio resource configuration information and the ECM setting information, performs data communication with the coverage improvement process in ECM (M2M data with ECM).
[0094]

　configuration example of a wireless communication system according to this embodiment may be the same as in FIG. 1 as described for the first embodiment. In the present embodiment, modification of the detailed sequence described in the first and second embodiments (FIGS. 2, 3, and 4) are described.
[0095]
　Procedures described in this embodiment can be said to be a combination of the steps of FIG. 2 (or FIG. 3) and FIG. That, MTC UE31 according to the present embodiment, (it is being executed or ECM) determines by itself the necessity of ECM, starts the execution of the ECM on the basis of the determination, it ECM is required the notifying the ENB33 (second notification). eNB33 determines necessity of ECM for MTC UE31 in response to the second notification from the MTC UE31. eNB33 sends ECM setting information to MTC UE31 when ECM is determined to be necessary, and transmits the interruption of ECM (or stop) instruction to the MTC UE31 when ECM is determined to be unnecessary. According to the control procedure of such ECM, MTC UE31 will promptly can begin ECM based on own judgment. Furthermore, ENB33 can verify the validity of the ECM necessity determination in MTC UE31, cancel the decision not valid (i.e., stop ECM) can.
[0096]
　Figure 5 is a sequence diagram showing an example of the operation of the MTC UE31 and eNB33 according to the present embodiment. Incidentally, Figure 5 describes only messages necessary for explanation of this embodiment, it is omitted several messages included in the procedure defined in LTE.
[0097]
　Processing in steps S401 ~ S403 in FIG. 5 is the same as the processing in steps S101 ~ S103 in FIG. In step S404, MTC UE31 transmits a completion message indicating the establishment completion of wireless connection (RRC connection) (RRC Connection Setup Complete). In FIG. 5, is omitted in the first to fourth steps of the random access procedure (i.e., the transmission of PRACH preamble by MTC UE31 until the transmission of the RRC Connection Setup message by the eNB33).
[0098]
　MTC UE31, using the RRC Connection Setup Complete message in step S404, and transmit a second notification that the ECM is required by itself (ECM Request). The second notification (ECM Request) requests the execution of the ECM (coverage improvement process in the ECM) for MTC UE31 to ENB33. The second notification (ECM Request), instead of the RRC Connection Setup Complete message in step S404, may be transmitted using an RRC Connection Request message are not shown.
[0099]
　In step S405, eNB33 is, (ECM decision) determines whether it is necessary to ECM (or whether to execute the ECM for MTC UE31) for MTC UE31. In the determination of step S405, ENB33 may be used the same parameters and determination of necessity ECM in MTC UE 11 described in the first embodiment.
[0100]
　Step S406 ~ S407, it is necessary ECM for MTC UE31 (or performs ECM) and shows are cases determined in ENB33 (Case 1 in Fig. 5). In step S406, ENB33 transmits a radio resource configuration information (Radio Resource Configuration) in MTC UE31 (RRC Connection Reconfiguration). Radio resource configuration information transmitted in step S406 may include ECM setting information necessary for executing the ECM (ECM configuration). Also, radio resource configuration information transmitted in step S406 may include an explicit indication information to execute the ECM against MTC UE31. In step S407, MTC UE31 according radio resource configuration information and the ECM setting information, performs data communication with the coverage improvement process in ECM (M2M data with ECM).
[0101]
　On the other hand, steps S408 ~ S410 is not required ECM for MTC UE31 (or interrupting or withdraw ECM) and shows are cases determined in ENB33 (Case 2 in FIG. 5). In step S408, eNB33 will transmit a radio resource configuration information (Radio Resource Configuration) in MTC UE31 (RRC Connection Reconfiguration). Radio resource configuration information transmitted in step S408 includes interrupt the execution of the ECM (or cancel) instructing (ECM deactivated-). In step S409, MTC UE31 may interrupt the execution of the ECM (or stop) to (ECM stop). In step S410, MTC UE31 performs data communication without coverage improvement process in ECM (M2M data without ECM).
[0102]

　configuration example of a wireless communication system according to this embodiment may be the same as in FIG. 1 as described for the first embodiment. In the present embodiment, modification of the detailed sequence described in the third embodiment (FIG. 5) is described.
[0103]
　MTC UE 41 according to the present embodiment, similarly to the MTC UE31 according to the third embodiment, it is determined in its necessity of ECM, starts the execution of the ECM on the basis of the determination, it is necessary ECM it (or is being run ECM) and notifies the ENB43 (second notification). However Thereafter, MTC UE 41 is to wait for the judgment by ENB43, interrupt the execution of the ECM (or aborted) for. In this respect, this embodiment differs from the third embodiment. For example, MTC UE 41, the period from accessing the eNB43 until establishing a radio connection (RRC connection) coverage improvement process in ECM (eg, repeated reception of the PBCH, repeated transmission of the PRACH preamble repetition of PDSCH / PUSCH ) is performed, then it may be interrupted the execution of the ECM. In other words, MTC UE 41 performs the ECM during at least the random access procedure (RACH procedure) and RRC connection establishment procedure, then it may be interrupted to execute the ECM.
[0104]
　eNB43 according to the present embodiment, similarly to the eNB33 according to the third embodiment determines the necessity of ECM for MTC UE 41 in response to the second notification from MTC UE 41. Then, ENB43 transmits the ECM setting information to MTC UE 41 when the ECM is determined to be necessary, and transmits the interruption of ECM (or stop) instruction to the MTC UE 41 when the ECM is determined to be unnecessary. MTC UE 41 in response to reception of the ECM setting information from ENB43, initiates an ECM that has been suspended (stopped) again.
[0105]
　According to the control procedure of such ECM, as in the third embodiment, MTC UE 41 promptly can start an ECM based on own judgment. In particular, by temporarily running the ECM in until establishing at least a radio connection (RRC connection), the first access (eg, random access using the PRACH of MTC UE 41 is to ENB43, or the establishment of RRC Connection It can be avoided to fail). Meanwhile, ENB43 can verify the validity of the ECM necessity determination in MTC UE 41, it can be started selectively ECM only if it is valid.
[0106]
　Figure 6 is a sequence diagram showing an example of the operation of the MTC UE 41 and eNB43 according to the present embodiment. Note that Figure 6 describes only messages necessary for explanation of this embodiment, it is omitted several messages included in the procedure defined in LTE.
[0107]
　Processing in steps S501 ~ S504 in FIG. 6 is the same as the processing in steps S401 ~ S404 in FIG. In step S505, MTC UE 41, after step S504, i.e. after establishment of the RRC connection, ECM (i.e., coverage improvement process in ECM) suspend or cancel the execution of the (ECM Stop).
[0108]
　Processing in step S506 is the same as the processing in step S405 in FIG. That, ENB43 is, (ECM decision) determines whether it is necessary to ECM (or whether to execute the ECM for MTC UE 41) for MTC UE 41.
[0109]
　Step S507 ~ S509, it is necessary ECM for MTC UE 41 (or performs ECM) and shows are cases determined in ENB43 (Case 1 in FIG. 6). Processing in step S507 is the same as the processing in step S406 in FIG. That, ENB43 transmits a radio resource configuration information (Radio Resource Configuration) in MTC UE41 (RRC Connection Reconfiguration). In step S508, MTC UE 41 in response to an instruction from ENB43, starts execution of the ECM (or restart) to (ECM start). In step S509, MTC UE 41 in accordance with the radio resource configuration information and the ECM setting information, performs data communication with the coverage improvement process in ECM (M2M data with ECM).
[0110]
　On the other hand, steps S510 and S511 show a are cases determined in eNB43 the ECM is not required for MTC UE 41 (Case 2 in FIG. 6). In step S510, eNB43 will transmit a radio resource configuration information (Radio Resource Configuration) in MTC UE41 (RRC Connection Reconfiguration). Radio resource configuration information transmitted in step S511 may be explicitly indicated that ECM is not executed. In step S511, MTC UE 41 performs data communication without coverage improvement process in ECM (M2M data without ECM).
[0111]
　Finally MTC UE and an example of the configuration of the eNB will be described according to the above-described embodiment. Each MTC UE11,21,31, and 41 described in the first to fourth embodiments, the transceiver for communicating with eNB, and may also include a controller coupled to the transceiver. The controller performs communication control relating to ECM by MTC UE11,21,31 or 41, which is described in the first to fourth embodiments.
[0112]
　eNB13,23,33 described in the first to fourth embodiments, and 43 each includes a transceiver for communicating with a plurality of UE including MTC UE, and may include a controller coupled to the transceiver . The controller performs communication control relating to ECM by eNB13,23,33 or 43, which is described in the first to fourth embodiments.
[0113]
　7 and 8 is a block diagram showing a configuration example of a MTC UE 11 and eNB13 according to the first embodiment. Referring to FIG. 7, MTC UE 11 includes a transceiver 111 and a controller 112. The transceiver 111 is configured to communicate with eNB13. The controller 112 in accordance with an instruction from the eNB13, is configured to control the execution of coverage improvement process related ECM in MTC UE 11. Specifically, the controller 112 is first notified from the eNB13 is configured to receive via the transceiver 111. Furthermore, the controller 112, while when establishing a wireless connection with the eNB13 after receiving the first notification (RRC connection), the or establishment procedure first notification EPS bearer after receiving the is performed, the second It is configured to transmit via the transceiver 111 to notify the eNB13.
[0114]
　Referring to FIG. 8, eNB13 includes a transceiver 131 and a controller 132. The transceiver 131 is configured to communicate with a plurality of UE including MTC UE 11 and the normal UE 12. The controller 132 is configured to control the communication with the coverage improvement process related ECM between MTC UE1 and eNB13. Specifically, the controller 132, via a predetermined coverage improvement processing (i.e., coverage improvement process in ECM) transceiver 131 a first notification that is supported in the cell 130 of eNB13 for MTC UE 11 It is configured to transmit Te.
[0115]
　Each controller having the MTC UE and eNB according to the embodiment described above, at least one processor by causing a computer to execute a program containing a (eg microprocessor, Micro Processing Unit (MPU), Central Processing Unit (CPU)) it may be realized. Specifically, it may be supplied to one or more program including instructions for causing algorithms for MTC UE and eNB that is described with reference to a sequence diagram or the like to the computer.
[0116]
　This program is stored using a non-transitory computer readable media of various types (non-transitory computer readable medium), it can be supplied to the computer. Non-transitory computer readable media include with various types of entities (tangible storage medium). Examples of non-transitory computer readable media include magnetic storage media (such as floppy disks, magnetic tape, hard disk drive), magneto-optical recording medium (e.g., magneto-optical disk), Compact Disc Read Only Memory (CD-ROM), CD- R, including CD-R / W, a semiconductor memory (e.g., a mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access memory (RAM)). The program may be provided to a computer using a temporary computer readable media of various types (transitory computer readable medium). Examples of transitory computer readable media include electric signals, optical signals, and electromagnetic waves. Transitory computer readable media, wired communication path such as electrical wires and optical fibers, or via a wireless communication path can provide the program to a computer.
[0117]

　In the above embodiments, a special operation mode in MTC UE, i.e. set Enhanced Coverage Mode (ECM) is, ECM coverage improvement process related (eg, repetition of RACH, repetition of PDSCH / PUSCH) is It is described on the assumption that performed in MTC UE. However, MTC UE is special coverage improvement process (eg, repetition of RACH, repetition of PDSCH / PUSCH) may be composed to be able to perform the, be set to a special operating mode (i.e., ECM) is it is not always necessary. In other words, MTC UE11,21,31, and 41, without setting a special operating mode such as ECM, or without being instructed special operation mode, special coverage by performing radio resource configuration improvement processing (eg, RACH iteration of the repetition of the PDSCH / PUSCH) may be performed.
[0118]
　Further, although the above embodiment has been assumed the ECM, techniques idea described in these embodiments, any special processing that is different from the ECM to the wireless network (e.g. eNB) is M2M terminal (MTC UE) it may be applied to a case of executing.
[0119]
　Further, in the above embodiment has been described an ordinary terminal (UE) and M2M terminal (MTC UE) as an example, also called respectively the user terminal (user terminal Enter) and the non-user terminal (non-user terminal).
[0120]
　Further, in the embodiment described above, it has been described primarily in the context of a LTE system. However, these embodiments, wireless communication systems other than the LTE system, for example, 3GPP UMTS, 3GPP2 CDMA2000 systems (1xRTT, HRPD), may be applied GSM / GPRS system, or WiMAX system or the like.
[0121]
　If the above-described embodiment is applied to a 3GPP UMTS, the operation of the eNB (eNB13,23,33, or 43) in the above embodiment, it may be performed by NodeB or RNC or a combination thereof. In other words, the term base station as used in the specification and claims, means one or more entities are arranged in a radio access network, a NodeB or RNC or a combination of these UMTS in one example means.
[0122]
　Furthermore, the above-described embodiments are only examples for the application of technical ideas obtained by the present inventor. In other words, the technical idea is not limited to the embodiments described above, it is needless to say various modifications are possible.
[0123]
　This application claims priority based on Japanese Patent Application No. 2014-015866, filed on January 30, 2014, the entire disclosure of which is incorporated herein.
DESCRIPTION OF SYMBOLS
[0124]
11, 21, 31, 41 M2M terminal (MTC
UE) 13, 23, 33, 43 base station
(eNB) 14 Core Network
(EPC) 130 cell
111 transceiver
112 controller
131 transceiver
132 Controller

WE CLAIM

A M2M terminal for Machine-to-machine (M2M) communication,
　a wireless communication means for communicating with a base station,
　and control means,
comprising a
　said control means receives the first notification from the base station together, while the when establishing a wireless connection with the base station after receiving the first notification, or procedure for establishing a bearer between the M2M terminal and the core network after receiving the first notification is performed in the second notification was transmitted to the base station,
　the first notification, the predetermined coverage improvement process in the cell of the base station that the M2M terminal to stay indicates whether supported,
　said first 2 notification indicates that the predetermined coverage improvement process is that or run is required by the M2M terminal,
M2M terminal.
[Requested item 2]
　Wherein the first notification, the does not have a wireless connection with the base station, and receivable broadcast channels in the terminal can not be reached by paging to location registration to the core network that are not in is received, M2M terminal according to claim 1.
[Requested item 3]
　The broadcast channel may include a Broadcast Control Channel (BCCH) of the Long Term Evolution (LTE), M2M terminal according to claim 2.
[Requested item 4]
　Wherein the first notification is included in the Master Information Block (MIB) or System Information Block, M2M terminal according to claim 3.
[Requested item 5]
　Wherein the first notification comprises a setting information for the predetermined coverage improvement process, the predetermined coverage improvement process implies to be supported at the base station, any one of claims 1 to 4, M2M terminal according to.
[Requested item 6]
　The second notice, the wireless connection request for requesting the establishment of a message or transmitted using a completion message said indicating the establishment completion of wireless connection according to any one of claims 1 to 5, M2M terminal.
[Requested item 7]
　The request message comprises a Radio Resource Control (RRC) Connection Request message Long Term Evolution (LTE),
　the completion message comprises an LTE RRC Connection Setup Complete message,
M2M terminal according to claim 6.
[Requested item 8]
　The second notification, the transmitted in a random access procedure performed prior to the establishment of the wireless connection, M2M terminal according to any one of claims 1 to 5.
[Requested item 9]
　The second notification, the predetermined that is transmitted using a special radio resource allocated for the coverage improvement process, said predetermined coverage improvement process is required by the M2M terminal or implying that it is running, M2M terminal according to claim 8.
[Requested item 10]
　It said second notification is transmitted using a Radio Resource Control (RRC) message with Non-access stratum (NAS) message for requesting establishment of the bearer, in any one of claims 1 to 5, M2M terminal according.
[Requested item 11]
　The control means, the M2M determines to perform the predetermined coverage improvement process in the terminal, and controls the communication with the predetermined coverage improvement processing between the base station and the M2M terminal, according to claim 1 M2M terminal according to any one of 10.
[Requested item 12]
　The control means, the explicitly or implicitly instruction specifying the stop of the predetermined coverage improvement process until receiving from the base station, to continue the predetermined coverage improvement processing, M2M terminal according to claim 11 .
[Requested item 13]
　Wherein, the M2M until data transmission of the terminal is completed, continue to the predetermined coverage improvement processing, M2M terminal according to claim 11.
[Requested item 14]
　Wherein, while performing the delay-insensitive access (delay tolerant access), and continues the predetermined coverage improvement processing, M2M terminal according to claim 11.
[Requested item 15]
　Said control means, said until the establishment of the wireless connection is completed, continue to the predetermined coverage improvement processing, M2M terminal according to claim 11.
[Requested item 16]
　Wherein, until said established bearer is completed, continue to the predetermined coverage improvement processing, M2M terminal according to claim 11.
[Requested item 17]
　Wherein, if from the base station is instructed to execute the predetermined coverage improvement process, also continues the prescribed coverage improvement process after releasing the wireless connection with the base station, according to claim 1 to 10 M2M terminal according to any one of.
[Requested item 18]
　Wherein, if from the base station is instructed to execute the predetermined coverage improvement process, also continues the prescribed coverage improvement processing while repeating the establishment and release of wireless connection with the base station, according to claim M2M terminal according to any one of 1-10.
[Requested item 19]
　Wherein, when instructed to execute the predetermined coverage improvement process from the base station, while performing delay-insensitive access (delay tolerant access) continues the predetermined coverage improvement process, according to claim 1 M2M terminal according to any one of 10.
[Requested item 20]
　A base station,
　a wireless communication means for communicating with Machine-to-machine (M2M) device,
　a predetermined coverage improvement process is supported for the M2M terminal in the cell of the base station that the M2M terminal stays and control means for transmitting via the wireless communication unit a first notification that
the base station comprises a.
[Requested item 21]
　Wherein, when establishing a wireless connection with the M2M terminal, or during the procedure for establishing a bearer between the M2M terminal and the core network, the second notification received from the M2M terminal ,
　the second notification indicates that the predetermined coverage improvement process is that or run is required by the M2M terminal,
a base station according to claim 20.
[Requested item 22]
　Wherein the first notification, the does not have a wireless connection with the base station, and receivable broadcast channels in the terminal can not be reached by paging to location registration to the core network that are not in is sent, the base station according to claim 20 or 21.
[Requested item 23]
　The broadcast channel may include a Broadcast Control Channel (BCCH) of the Long Term Evolution (LTE), the base station according to claim 22.
[Requested item 24]
　Wherein the first notification is included in the Master Information Block (MIB) or System Information Block, the base station according to claim 23.
[Requested item 25]
　Wherein the first notification comprises a setting information for the predetermined coverage improvement process, the predetermined coverage improvement process implies to be supported at the base station, any one of claims 20-24 the base station according to.
[Requested item 26]
　The second notification, the wireless request message for requesting the establishment of a connection, or the received with a completion message indicating the establishment completion of wireless connection, the base station according to claim 21.
[Requested item 27]
　The request message comprises a Radio Resource Control (RRC) Connection Request message Long Term Evolution (LTE),
　the completion message comprises an LTE RRC Connection Setup Complete message,
the base station according to claim 26.
[Requested item 28]
　The second notification, the received in a random access procedure performed prior to the establishment of the wireless connection, the base station according to claim 21.
[Requested item 29]
　The second notification, the predetermined that is transmitted using a special radio resource allocated for the coverage improvement process, said predetermined coverage improvement process is required by the M2M terminal or implying that it is executed, the base station according to claim 28.
[Requested item 30]
　The second notification, the received using Radio Resource Control (RRC) message with Non-access stratum (NAS) message for requesting the establishment of a bearer, the base station according to claim 21.
[Requested item 31]
　Said control means is responsive to receipt of the second notification, the M2M predetermined determines to perform coverage improvement process for the terminal, the predetermined between the base station and the M2M terminal It controls the communication with the coverage improvement process, the base station according to any one of claims 21 and 26-30.
[Requested item 32]
　A Machine-to-machine (M2M) method performed by M2M terminal performing communication,
　receiving a first notification from the base station, and
　a wireless connection with the base station after receiving the first notification when establishing or during the procedure for establishing a bearer between the M2M terminal and the core network is performed after the reception of the first notification, sending a second notification to the base station,
equipped with,
　wherein the first notification, the in the cell of the base station M2M terminal stays indicates whether or not a predetermined coverage improvement process is supported,
　the second notification, the predetermined coverage improvement process is the M2M It indicates that it is possible or run is required by the terminal,
the method.
[Requested item 33]
　A method performed by a base station,
　a first notification that the predetermined coverage improvement process for the M2M terminal in Machine-to-machine (M2M) cell of the base station that the terminal stays are supported the comprising transmitting into the cell,
method.
[Requested item 34]
　A Machine-to-machine (M2M) non-transitory computer readable medium storing a program for causing the method to the computer about the M2M terminal that performs communication,
　the method comprising:
　receiving a first notification from the base station to it, and
　the when establishing a wireless connection with the base station after receiving the first notification, or procedures row to establish a bearer between the first notification the M2M terminal and the core network after receiving the during cracking, sending a second notification to the base station,
equipped with,
　whether the first notification, the predetermined coverage improvement process in the cell of the base station that the M2M terminal stays are supported or it indicates,
　the second notification indicates that the predetermined coverage improvement process is that or run is required by the M2M terminal,
non-transitory computer readable media.
[Requested item 35]
　The method for a base station to a non-transitory computer readable medium storing a program for causing a computer,
　the method comprising the in Machine-to-machine (M2M) cell of the base station that the terminal stays M2M given a first notification that the coverage improvement process is supported comprises transmitting in the cell, for the terminal
non-transitory computer readable media.