EP3101941B1 - Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur - Google Patents

Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur Download PDF

Info

Publication number
EP3101941B1
EP3101941B1 EP14880670.6A EP14880670A EP3101941B1 EP 3101941 B1 EP3101941 B1 EP 3101941B1 EP 14880670 A EP14880670 A EP 14880670A EP 3101941 B1 EP3101941 B1 EP 3101941B1
Authority
EP
European Patent Office
Prior art keywords
terminal
base station
mtc
ecm
enb
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP14880670.6A
Other languages
German (de)
English (en)
Other versions
EP3101941A1 (fr
EP3101941A4 (fr
Inventor
Hisashi Futaki
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Priority to EP18165057.3A priority Critical patent/EP3364681A3/fr
Priority to EP19195447.8A priority patent/EP3595349A1/fr
Publication of EP3101941A1 publication Critical patent/EP3101941A1/fr
Publication of EP3101941A4 publication Critical patent/EP3101941A4/fr
Application granted granted Critical
Publication of EP3101941B1 publication Critical patent/EP3101941B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/26—Cell enhancers or enhancement, e.g. for tunnels, building shadow
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/045—Interfaces between hierarchically different network devices between access point and backbone network device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to a radio communication system which performs a communication control in order to enhance coverage.
  • Non-Patent Literature 1 In the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), standardization of techniques for improving deterioration of communication quality due to recent sharp increase in mobile traffic and for achieving faster communication has been performed. Further, standardization of techniques for avoiding increase in a control signaling load due to connections of an enormous number of Machine to Machine (M2M) terminals to an LTE network has been performed (Non-Patent Literature 1).
  • the M2M terminals are, for example, terminals that perform communication without human intervention.
  • the M2M terminals are placed in various types of equipment including machines (e.g., vending machines, gas meters, electric meters, vehicles, railway vehicles, and ships) and sensors (e.g., environmental, agricultural, and traffic sensors).
  • MTC Machine Type Communications
  • MTC UE MTC User Equipment
  • M2M service providers need to distribute an enormous number of M2M terminals, there is a limit to the cost allowable for each M2M terminal. Therefore, it is required M2M terminals be implemented at a low cost, and M2M terminals be able to perform communication with low power consumption, for example. Further, in one use case, MTC UEs perform communication while they are fixedly or statically installed in buildings. In this case, the radio quality of MTC UEs may be always low and accordingly coverage enhancement technique is especially needed for MTC devices compared to normal UEs having mobility (e.g., mobile telephones, smartphones, tablet computers, and notebook personal computers (notebook PCs)).
  • mobility e.g., mobile telephones, smartphones, tablet computers, and notebook personal computers (notebook PCs)
  • Non-Patent Literature 2 standardization of techniques for enhancing communication characteristics of MTC UEs (i.e., coverage), which are expected to be lower than those of normal UE has been performed.
  • the coverage enhancement techniques (coverage enhancement processing) for MTC UEs described below are processing for enhancing or improving communication characteristics or communication quality of MTC UEs.
  • the state of a UE to which these special coverage enhancement techniques has been applied is referred to as a coverage enhancement mode (Enhanced Coverage Mode (ECM)).
  • ECM Enhanced Coverage Mode
  • the ECM can improve, for example, a reception characteristic of a Physical Broadcast Channel (PBCH), a transmission characteristic of a Physical Random Access Channel (PRACH) preamble (i.e., detection characteristic in an eNB), a reception characteristic of a Physical Downlink Shared Channel (PDSCH), and a transmission characteristic of a Physical Uplink Shared Channel (PUSCH).
  • PBCH Physical Broadcast Channel
  • PRACH Physical Random Access Channel
  • PDSCH Physical Downlink Shared Channel
  • PUSCH Physical Uplink Shared Channel
  • the PBCH is a downlink broadcast channel used by an eNB to transmit broadcast information commonly used within a cell.
  • the PRACH is an uplink physical channel used by a UE for an initial access to a radio base station (eNB).
  • the PDSCH is a downlink physical channel used for data reception by a UE.
  • the PUSCH is an uplink physical channel used for data transmission by a UE.
  • Non-Patent Literature 3 One processing that is being discussed to improve a transmission characteristic of the PRACH is to repeatedly transmit the PRACH (i.e., preamble) a predetermined number of times (Non-Patent Literature 4). Further, one processing that is being discussed to improve a reception characteristic of the PDSCH and a transmission characteristic of the PUSCH is to repeatedly transmit the PDSCH and the PUSCH over multiple subframes (Non-Patent Literature 5). According to the above processing, communication characteristics of MTC UEs that is expected to be lower than that of normal UEs will be improved.
  • the delay tolerant access is defined as being a new EstablishmentCause that is specified in an RRC Connection Request message and is used, for example, to control an overload.
  • the delay tolerant access is mainly intended for MTC UEs that execute a delay-tolerant MTC application. For example, in a metering service (meter reading service), there is no need to send a metering report to a remote system in real time (or in exact communication cycles) and a long delay may be allowed for the transmission of the metering report.
  • the eNB may reject an RRC Connection Request transmitted by a RRC Connection Request message that contains "EstablishmentCause" indicating the delay tolerant access.
  • NTT DOCOMO "Discussion on Multi-level PRACH Coverage Enhancement"; 3GPP Draft R1-135509, 13 November 2013; 3GPP Mobile Competence Centre, 650 Route des Lucioles, Sophia-Antipolis, Cedex , discloses details on the PRACH coverage enhancement, especially multiplexing-related issues, including frequency hopping and multi-level PRACH coverage adapatation during initial access.
  • WO 2008/087524 discloses an approach for context recovery.
  • a radio link failure condition of a wireless link employed by a mobile unit is detected.
  • An identifier of the mobile unit is received.
  • a determination is whether the mobile unit can re-use connection parameters that were established prior to the failure condition.
  • the mobile unit is instructed to re-use the connection parameters based on the determination.
  • the present inventor has examined many problems that are caused when the coverage enhancement processing in the ECM is applied to MTC UEs (M2M terminals). For example, while PBCH repetition is commonly applied to MTC UEs in a cell, RACH repetition and PDSCH/PUSCH repetition are separately applied to each MTC UE.
  • each MTC UE e.g., RACH repetition and PDSCH/PUSCH repetition
  • a large number of radio resources are consumed as the number of MTC UEs performing the ECM increases, which may cause decrease in radio resources that can be used by normal UEs, which are not MTC UEs.
  • the processing separately applied to each MTC UE e.g., PDSCH/PUSCH repetition
  • power consumption of this MTC UE may be unnecessarily increased.
  • MTC UEs that should execute the ECM based on radio quality of these MTC UEs (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), or Channel Quality Indicator (CQI)).
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • CQI Channel Quality Indicator
  • the processing for selecting an MTC UE that should execute the ECM may require some time (e.g., hundreds of ms), which may increase, for example, a time required for completion of a procedure for establishing a radio connection (e.g., RRC Connection Establishment Procedure).
  • RRC_IDLE idle state
  • RRC_CONNECTED connected state
  • an eNB releases (deletes) a context that has been held by the eNB regarding the MTC UE.
  • the eNB may need to repeatedly determine the necessity of the ECM when an MTC UE transitions to the connected state (RRC_CONNECTED) from the idle state (RRC_IDLE) to perform communication.
  • the terms “idle state” and “connected state” used in the specification is defined as follows.
  • the "idle state” is a state in which a radio connection between a UE and an eNB has been released. Accordingly, the eNB has no information (UE context) regarding the UE in the idle state.
  • the location of the UE in the idle state is tracked by a core network at location-registration-area level (e.g., tracking area or routing area).
  • the core network can reach the UE in the idle state by paging. Further, the UE in the idle state cannot perform unicast data transmission to or from the eNB. Accordingly, the UE in the idle state should transition to the connected state in order to perform unicast data transmission.
  • Examples of the idle state include: (1) an RRC idle state in a Universal Terrestrial Radio Access Network (UTRAN); (2) an RRC_IDLE state in an Evolved UTRAN (E-UTRAN); and (3) an Idle state in WiMAX (IEEE 802.16-2004), mobile WiMAX (IEEE 802.16e-2005), and WiMAX2 (IEEE 802.16m).
  • UTRAN Universal Terrestrial Radio Access Network
  • E-UTRAN Evolved UTRAN
  • Idle state in WiMAX
  • WiMAX IEEE 802.16-2004
  • mobile WiMAX IEEE 802.16e-2005
  • WiMAX2 IEEE 802.16m
  • the connected state is a state in which the UE is connected to the eNB.
  • the eNB has information (UE context) regarding the UE in the connected state.
  • the location of the UE in the connected state is tracked by the core network at cell level or base-station level.
  • the UE in the connected state can perform unicast data transmission to and from the eNB.
  • the UE context is held by a base station (NodeB), but no dedicated channel is allocated to the UE either in uplink or in downlink.
  • the connected state examples include: (1) an RRC connected state in the UTRAN; (2) an RRC_CONNECTED state in the E-UTRAN; and (3) a connected state in the WiMAX, the mobile WiMAX, and the WiMAX2.
  • the RRC connected state in the UTRAN includes a CELL DCH state, a CELL_FACH state, a CELL PCH state, and a URA_PCH state.
  • the present invention provides a base station, core network apparatus, associated methods and a programs, as set out in the appended claims, that contribute to improving efficiency of determination regarding whether to apply the ECM (i.e., the coverage enhancement processing in the ECM) to the MTC UE (M2M terminal).
  • ECM i.e., the coverage enhancement processing in the ECM
  • a base station apparatus includes a radio communication unit and a controller.
  • the controller is configured to receive, from a Machine-to-machine (M2M) terminal or a core network, history information indicating whether or not specific coverage enhancement processing was executed in previous communication with the M2M terminal and to control communication using the specific coverage enhancement processing between the M2M terminal and the radio communication unit based on the history information.
  • M2M Machine-to-machine
  • a core network apparatus that is included in a core network includes an interface and a controller.
  • the interface is configured to transmit and receive signaling messages to and from a base station.
  • the controller is configured to send, to the base station via the interface during a procedure for establishing a bearer between a Machine-to-machine (M2M) terminal and the core network, history information indicating whether or not specific coverage enhancement processing was executed in previous communication with the M2M terminal.
  • M2M Machine-to-machine
  • an M2M terminal includes a radio communication unit and a controller.
  • the radio communication unit is configured to communicate with a base station.
  • the controller is configured to transmit, to the base station via the radio communication means when establishing a radio connection with a base station or while a procedure for establishing a bearer between the M2M terminal and a core network via the base station is being performed, history information indicating whether or not specific coverage enhancement processing was executed in previous communication of the M2M terminal.
  • a method performed by a base station includes (a) receiving, from a Machine-to-machine (M2M) terminal or a core network, history information indicating whether or not specific coverage enhancement processing was executed in previous communication with the M2M terminal, and (b) controlling communication using the specific coverage enhancement processing between the M2M terminal and the base station based on the history information.
  • M2M Machine-to-machine
  • a method performed by a core network apparatus that is included in a core network includes sending, to a base station during a procedure for establishing a bearer between a Machine-to-machine (M2M) terminal and the core network, history information indicating whether or not specific coverage enhancement processing was executed in previous communication with the M2M terminal.
  • M2M Machine-to-machine
  • a method performed by an M2M terminal includes transmitting, to a base station when establishing a radio connection with a base station or while a procedure for establishing a bearer between the M2M terminal and a core network via the base station is being performed, history information indicating whether or not specific coverage enhancement processing was executed in previous communication of the M2M terminal.
  • a program contains a set of instructions (software codes) which, when loaded into a computer, causes the computer to perform any one of the aforementioned methods.
  • MTC UE M2M terminal
  • M2M terminal M2M terminal
  • Fig. 1 shows a configuration example of a radio communication system according to this embodiment.
  • This radio communication system provides communication services, such as voice communication or packet data communication or both, for example.
  • the radio communication system includes M2M terminals 11 (11A, 11B, 11C), a normal radio terminal 12 which is not an M2M terminal, a base station 13, and a core network 14.
  • the radio terminal 12 is, for example, a mobile telephone, a smartphone, a tablet computer, or a notebook PC.
  • the M2M terminals 11A, 11B, and 11C, and the radio terminal 12 are located in a cell 130 of the base station 13.
  • the radio communication system is described as being a 3GPP LTE system.
  • the M2M terminals 11 correspond to MTC UEs
  • the radio terminal 12 corresponds to a normal UE which is not an MTC UE
  • the base station 13 corresponds to an eNodeB (eNB)
  • the core network 14 corresponds to an Evolved Packet Core (EPC).
  • EPC Evolved Packet Core
  • the distance between the MTC UE 11A and the eNB 13 is larger than the distance between the MTC UE 11B and the eNB 13. Accordingly, it is assumed that the MTC UE 11A has a large pathloss and its radio quality is degraded. Further, the MTC UE 11C is installed in a building and, accordingly, it is thus assumed that its radio quality is more degraded compared to a case in which the MTC UE 11C is located outdoors.
  • the MTC UEs 11 are configured to support the aforementioned Enhanced Coverage Mode (ECM) and to perform coverage enhancement processing in the ECM.
  • ECM Enhanced Coverage Mode
  • the coverage enhancement processing in the ECM can be said as processing for enhancing or improving communication characteristics (communication quality) of MTC UEs.
  • the coverage enhancement processing in the ECM may include at least one of the following processing (a) to (d) or may include other processing (e.g., (e) and (f)):
  • the subframe is a unit constituting a LTE radio frame.
  • One radio frame has a length of ten milliseconds and is composed of ten subframes. Therefore, one subframe has a length of one millisecond.
  • One subframe includes 14 symbols in a time domain (single carrier frequency division multiple access (SC-FDMA) symbols in uplink and orthogonal frequency division multiplexing (OFDM) symbols in downlink).
  • SC-FDMA single carrier frequency division multiple access
  • OFDM orthogonal frequency division multiplexing
  • the eNB 13 receives, from the EPC 14, history information indicating whether or not the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) was executed in previous communication with the MTC UE (M2M terminal) 11.
  • the eNB 13 controls communication between the MTC UE 11 and the eNB 13 using the coverage enhancement processing regarding the ECM based on the history information received from the EPC 14.
  • the eNB 13 may receive the history information of the MTC UE 11 from a core network node (e.g., Mobility Management Entity (MME)) included in the EPC 14.
  • MME Mobility Management Entity
  • the eNB 13 may determine whether to execute the coverage enhancement processing regarding the ECM in communication between the MTC UE 11 and the eNB 13 based on the received history information. More specifically, in response to the history information indicating that the coverage enhancement processing regarding the ECM was executed for the MTC UE 11, the eNB 13 may transmit to the MTC UE 11 an instruction to execute the coverage enhancement processing regarding the ECM (e.g., ECM configuration). The eNB 13 may communicate with the MTC UE 11 assuming that the ECM is being performed in the MTC UE 11 without transmitting an explicit instruction.
  • ECM ECM configuration
  • the ECM configuration may include, for example, at least one of the following information items:
  • the configuration information regarding reception of the broadcast information (PBCH) and the configuration information regarding reception of the system information (SIB) may be, for example, information indicating which subframe(s) and/or which OFDM symbol(s) is used to repeatedly transmit the broadcast information and (which kind of) system information.
  • the configuration information regarding reception of paging may be, for example, information indicating which subframe(s) is used to repeatedly transmit paging.
  • the configuration information regarding reception of the downlink control information (PDCCH) and reception of the downlink data (PDSCH) may be, for example, information indicating how many times they are repeatedly transmitted or may be information indicating which subframe(s) is used for repeatedly transmitting them.
  • the configuration information regarding transmission of the uplink control information (PUCCH) and the transmission of the uplink data (PUSCH) may be, for example, information indicating how many times they are repeatedly transmitted or may be information indicating which subframe(s) is used for repeatedly transmitting them.
  • the configuration information regarding measurement reporting of radio quality may be an offset value or a threshold applied to the measurement result of the radio quality while the ECM is being executed or may be an offset value or a threshold applied to determination on the report of the measurement result of the radio quality while the ECM is being executed.
  • the ECM configuration may specify the operation level that the MTC UE 11 should execute.
  • the MTC UE 11 may continue holding the ECM configuration and continue executing the ECM even after transitioning from RRC_CONNECTED to RRC_IDLE. Alternatively, even after transitioning to RRC_IDLE, the MTC UE 11 may continue executing the ECM based on the ECM configuration broadcasted in the cell which the MTC UE 11 camps on.
  • the MTC UE 11 may continue executing the ECM autonomously based on the ECM configuration that the MTC UE 11 has already held or the ECM configuration broadcasted in the cell which the MTC UE 11 camps on, or the MTC UE 11 may initiate executing the ECM upon receiving from the eNB 13 an instruction to execute the ECM.
  • the eNB 13 receives from the EPC 14 the history information, which indicates whether the coverage enhancement processing regarding the ECM was executed in previous communication with the MTC UE 11, and controls communication using the coverage enhancement processing with the MTC UE 11 based on this history information, whereby the following effects can be expected. That is, the eNB 13 does not necessarily require acquisition of radio quality of the MTC UE 11 (e.g., RSRP, RSRQ, CQI) and analysis of the acquired radio quality to determine whether to apply the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) to the MTC UE 11.
  • radio quality of the MTC UE 11 e.g., RSRP, RSRQ, CQI
  • the eNB 13 can use the history information to determine whether or not the ECM can be applied (or whether the coverage enhancement processing of the ECM is efficient) to the MTC UE 11, which has established a radio connection with the eNB 13. Therefore, according to this embodiment, it is possible to reduce time (delay) required to determine whether to apply the coverage enhancement processing regarding the ECM to the MTC UE 11.
  • the eNB 13 may acquire the history information of the MTC UE 11 from the EPC 14 when it determines whether to apply the coverage enhancement processing regarding the ECM to the MTC UE 11. For example, the eNB 13 may receive the history information from the EPC 14 when the eNB 13 establishes a radio connection (Radio Resource Control (RRC) Connection) with the MTC UE 11, or in other words, when the MTC UE 11 transitions to the connected state (RRC_CONNECTED) from the idle state (RRC_IDLE).
  • RRC Radio Resource Control
  • the eNB 13 may receive the history information from the EPC 14 during a procedure for establishing a bearer (Evolved Packet System (EPS) bearer) between the MTC UE 11 and the EPC 14 (e.g., attach procedure, service request procedure).
  • EPS Evolved Packet System
  • the eNB 13 can promptly determine whether to apply the coverage enhancement processing regarding the ECM to the MTC UE 11 during the procedure for establishing a radio connection with the MTC UE 11 or during the bearer establishment procedure.
  • EPS Packet System
  • the eNB 13 may send, to the EPC 14, terminal information (UE context) indicating whether the coverage enhancement processing regarding the ECM has been executed for the MTC UE 11.
  • the UE context, which has been sent to the EPC 14, is transmitted as the history information of the MTC UE 11 to the eNB 13 that is the same as or different from the source eNB that has sent the terminal information.
  • the eNB 13 is configured to send to the EPC 14 the UE context regarding the MTC UE 11, which indicates whether the coverage enhancement processing regarding the ECM has been executed in communication between the MTC UE 11 and the eNB 13, in order to store it in the EPC 14, and also configured to read out and use the UE context from the EPC 14.
  • the context of the MTC UE 11 that is held by the eNB 13 while the MTC UE 11 is in the connected state (RRC_CONNECTED) is released (deleted) when the MTC UE 11 transitions to the idle state (RRC_IDLE). Therefore, by storing, in the EPC 14, the UE context (indicating whether the coverage enhancement processing regarding the ECM was executed for the MTC UE 11), which has been held in the eNB 13 while the MTC UE 11 is in the connected state, the eNB 13 can utilize the UE context stored in the EPC 14 as the history information in a future access of the MTC UE 11.
  • each MTC UEs 11 may be a terminal that is fixedly installed and is substantially stationary, as illustrated in Fig. 1 . In this case, each MTC UE 11 repeatedly transitions between the connected state (RRC_CONNECTED) and the idle state (RRC_IDLE) in one cell of one eNB 13.
  • each MTC UE 11 may be a terminal that has mobility (e.g., a terminal that is installed in a transportation machine such as a vehicle, a railway vehicle, or a ship). In this case, the MTC UE 11 may move through cells of one eNB 13 or through cells of different eNBs 13.
  • One scenario regarding the MTC UE 11 with mobility is as follows.
  • the MTC UE 11 is instructed to execute the ECM while it is in RRC_CONNECTED in a cell of one eNB 13, performs data communication using the ECM, and then transitions to RRC_IDLE.
  • the MTC UE 11 reselects another cell (Cell reselection) while it is in RRC_IDLE.
  • the MTC UE 11 again transitions to RRC_CONNECTED in a cell different from the cell in which the MTC UE 11 was previously in RRC_CONNECTED.
  • the EPC 14 sends, to the eNB 13 that manages the cell which the MTC UE 11 newly camps on, information (ECM status, history information) indicating whether the MTC UE 11 executed the ECM.
  • the EPC 14 may notify the eNB 13 of, for example, a physical cell identifier (Physical Cell Identity (PCI)) or a global cell identifier (Cell Global Identity (CGI)) in order to indicate the cell in which the MTC UE 11 previously executed the ECM.
  • PCI Physical Cell Identity
  • CGI Cell Global Identity
  • Fig. 2 is a sequence diagram showing one example of operations of the MTC UE 11, the eNB 13, and a core network node 141 according to this embodiment.
  • the core network node 141 is a node included in the EPC 14.
  • the core network node 141 may be one physical entity or may include a plurality of entities.
  • the core network node 141 may include, for example, an MME or a Home Subscriber Server (HSS), or both.
  • Fig. 2 shows only the messages that are necessary for explanation of this embodiment and some messages included in the procedure specified in the LTE standard are not shown.
  • Step S101 of Fig. 2 the eNB 13 decides to perform the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) for the MTC UE 11 and transmits ECM configuration information (ECM configuration) to the MTC UE 11.
  • ECM configuration is transmitted using an RRC Connection Reconfiguration message.
  • the MTC UE 11 starts executing the ECM (i.e., coverage enhancement processing (e.g., reception of a repeated PDSCH, repeated transmission of a PUSCH)) in accordance with the ECM configuration received from the eNB 13 (ECM start).
  • the MTC UE 11 performs data communication in accordance with the ECM configuration (M2M data with ECM).
  • Step S104 the eNB 13 determines that it is possible to change the state of the MTC UE 11 back to the idle state (RRC_IDLE) and requests the core network node 141 to release the S1-AP signaling connection and the S1 bearer (or the radio access bearer) regarding the MTC UE 11 (SI UE Context Release Request).
  • Step S105 the core network node 141 releases the S1-AP signaling connection and the S1 bearer in response to the request from the eNB 13, but the core network node 141 holds ECM status information (ECM status) indicating that the ECM was executed by the MTC UE 11 (Store ECM status).
  • ECM status information corresponds to the history information stated above.
  • the ECM status information may be held in the MME together with an EPS bearer context of the MTC UE 11.
  • the ECM status information (ECM status) may be sent to the HSS via the MME and may be held in the HSS.
  • the eNB 13 transmits to the MTC UE 11 an instruction to transition to RRC_IDLE (RRC Connection Release). In response to receiving this instruction, the MTC UE 11 transitions from RRC_CONNECTED to RRC_IDLE.
  • Step S107 in response to arrival of a periodic or non-periodic communication opportunity, the MTC UE 11 transmits a request for establishing a radio connection to the eNB 13 in order to start communication (RRC Connection Request).
  • the MTC UE 11 may transmit an RRC Connection Request containing an Establishment cause set to "delayTolerantAccess" in order to indicate a delay tolerant access.
  • the MTC UE 31 transitions to RRC_CONNECTED upon completion of the procedure for establishing the radio connection (RRC Connection) (not shown).
  • Step S108 the eNB 13 sends a request for establishing an EPS bearer for the MTC UE 11 to the core network node 141 (Initial UE message).
  • This Initial UE message encapsulates a Non-Access Stratum (NAS) message (e.g., NAS: Service Request, NAS: Attach Request) from the MTC UE 11.
  • NAS Non-Access Stratum
  • Step S109 in response to receiving the NAS message encapsulated in the Initial UE message, the core network node 141 sends, to the eNB 13, information that is necessary to establish a radio access bearer for the MTC UE 11 (Initial Context Setup Request).
  • NAS Non-Access Stratum
  • the message in Step S109 may include, for example, a terminal capability (UE radio capability) and a UE context.
  • the UE context may include the ECM status information (ECM status) indicating that the MTC UE 11 previously executed the ECM.
  • ECM status ECM status
  • the UE context may include mobility information of the MTC UE 11. If the ECM status information indicates that the MTC UE 11 previously executed the ECM and the mobility information indicates that the MTC UE 11 is a stationary or near-stationary terminal, the eNB 13 may decide to continuously execute the ECM for the MTC UE 11.
  • Step S110 the eNB 13 may transmit the ECM configuration information (ECM configuration) together with radio resource configuration information (RRC Configuration) in order to cause the MTC UE 11 to execute the ECM (RRC Connection Reconfiguration).
  • Step S111 the MTC UE 11 performs data communication based on the ECM configuration information received from the eNB 13 in Step S110 or based on the ECM configuration information that the MTC UE 11 has previously received and held (M2M data with ECM).
  • a configuration example of a radio communication system may be the same as that of Fig. 1 described in the first embodiment.
  • the example in which the eNB 13 receives from the EPC 14 the history information indicating whether the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) was executed in previous communication with the MTC UE 11 has been shown.
  • an eNB 23 receives, from an MTC UE 21, history information indicating whether the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) was executed in previous communication of the MTC UE 21.
  • the eNB 23 then controls communication between the MTC UE 21 and the eNB 23 using the coverage enhancement processing regarding the ECM based on the history information received from the MTC UE 21. For example, when the eNB 23 receives from the MTC UE 21 a notification indicating that the MTC UE 21 previously executed the ECM, the eNB 23 may cause the MTC UE 21 to continuously execute the ECM or may determine whether or not execution of the ECM is necessary again.
  • the MTC UE 21 may hold ECM configuration information (ECM configuration) even after the MTC UE 21 has transitioned to RRC_IDLE from RRC_CONNECTED or may simply memorize that it executed the ECM.
  • ECM configuration ECM configuration information
  • the MTC UE 21 again transitions to the RRC_CONNECTED, the MTC UE 21 notifies the eNB 23 that it executed the ECM before.
  • the MTC UE 21 may transmit and receive messages to transition to the RRC_CONNECTED (i.e., message transmitted during an RRC connection establishment procedure) while executing the ECM (i.e., while performing the ECM-specific coverage enhancement processing regarding the ECM).
  • the MTC UE 21 may use any one of the ECM-specific radio resources to transmit a PRACH preamble. Further, the MTC UE 21 may autonomously repeat transmission of the PRACH preamble.
  • the eNB 23 receives from the MTC UE 21 the history information, which indicates whether the coverage enhancement processing regarding the ECM was executed in previous communication of the MTC UE 21, and controls communication using the coverage enhancement processing with the MTC UE 21 based on this history information. Therefore, the eNB 23 does not necessarily require acquisition of radio quality of the MTC UE 21 (e.g., RSRP, RSRQ, CQI) and analysis of the acquired radio quality to determine whether to apply the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) to the MTC UE 21.
  • radio quality of the MTC UE 21 e.g., RSRP, RSRQ, CQI
  • the eNB 23 can use the history information to determine whether or not the ECM can be applied (or whether the coverage enhancement processing of the ECM is efficient) to the MTC UE 21, which has established a radio connection with the eNB 23. Therefore, according to this embodiment, it is possible to reduce time (delay) required to determine whether to apply the coverage enhancement processing regarding the ECM to the MTC UE 21.
  • the eNB 23 may receive the history information from the MTC UE 21 during a procedure for establishing a radio connection (RRC Connection) with the MTC UE 21, or in other words, when the MTC UE 21 transitions to the connected state (RRC_CONNECTED) from the idle state (RRC_IDLE).
  • the eNB 23 may receive the history information from the MTC UE 21 while a procedure for establishing a bearer between the MTC UE 21 and the EPC (EPS bearer) (e.g., attach procedure, service request procedure) is being performed.
  • EPS bearer EPC
  • the eNB 23 can promptly determine whether to apply the coverage enhancement processing regarding the ECM to the MTC UE 21 during the procedure for establishing a radio connection with the MTC UE 21 or during the bearer establishment procedure.
  • the MTC UE 21 may be a terminal that has mobility (e.g., a terminal that is installed in a transportation machine such as a vehicle, a railway vehicle, or a ship).
  • the MTC UE 21 is instructed to execute the ECM while it is in RRC_CONNECTED in a cell of one eNB 23, performs data communication using the ECM, and then transitions to RRC_IDLE.
  • the MTC UE 21 reselects another cell (Cell reselection) while it is in RRC_IDLE.
  • the MTC UE 21 again transitions to RRC_CONNECTED in a cell different from the cell in which the MTC UE 21 was previously in RRC_CONNECTED.
  • the MTC UE 21 sends, to the eNB 23 that manages the cell which the MTC UE 21 newly camps on, information indicating whether the MTC UE 21 executed the ECM before (ECM status, history information).
  • the MTC UE 21 may notify the eNB 23 of, for example, a physical cell identifier (PCI) or a global cell identifier (CGI) in order to indicate the cell in which the MTC UE 21 previously executed the ECM.
  • PCI physical cell identifier
  • CGI global cell identifier
  • Fig. 3 is a sequence diagram showing one example of operations of the MTC UE 21, the eNB 23, and a core network node 241 according to this embodiment.
  • the core network node 241 is a node that is included in the EPC (e.g., an MME or an HSS or both).
  • Fig. 3 shows only the messages that are necessary for explanation of this embodiment and some messages included in the procedure specified in the LTE standard are not shown.
  • Step S204 the eNB 23 determines to change the state of the MTC UE 21 back to the idle state (RRC_IDLE) and requests the core network node 241 to release the S1-AP signaling connection and the S1 bearer (or radio access bearer) regarding the MTC UE 21 (S1 UE Context Release Request).
  • the core network node 241 releases the S1-AP signaling connection and the S1 bearer in response to the request from the eNB 23.
  • Step S205 the eNB 23 transmits to the MTC UE 21 an instruction to transition to RRC_IDLE (RRC Connection Release). In response to receiving this instruction, the MTC UE 21 transitions from RRC_CONNECTED to RRC_IDLE.
  • Step S206 in response to arrival of a periodic or non-periodic communication opportunity, the MTC UE 21 transmits a request for establishing a radio connection to the eNB 23 in order to start communication (RRC Connection Request).
  • the MTC UE 21 may transmit an RRC Connection Request containing an Establishment cause set to "delayTolerantAccess" in order to indicate a delay tolerant access.
  • Step S207 the MTC UE 21 notifies the eNB 23 of the history information indicating that the MTC UE 21 previously executed the ECM. At this time, the MTC UE 21 may also notify the eNB 23 that the MTC UE 21 is currently executing the ECM.
  • the history information in Step S207 is transmitted using an RRC Connection Setup Complete message. Since the RRC Connection Setup Complete message is the final message that is transmitted during an RRC connection establishment a procedure, it can be said that the history information transmitted in Step S207 is transmitted during an RRC connection establishment procedure. Further, the RRC Connection Setup Complete message contains a NAS message (e.g., NAS: Service Request, NAS: Attach Request). That is, since the RRC Connection Setup Complete message containing a NAS message is the first message transmitted during a bearer establishment procedure, it can also be said that the history information in Step S207 is transmitted during a bearer establishment procedure.
  • NAS message e.g., NAS: Service Request, NAS: Attach Request
  • Step S208 the eNB 23 transmits a request for establishing an EPS bearer for the MTC UE 21 to the core network node 241 (Initial UE message).
  • Step S209 in response to receiving the NAS message encapsulated into the Initial UE message, the core network node 241 sends, to the eNB 23, information that is necessary to establish a radio access bearer for the MTC UE 21 (Initial Context Setup Request).
  • the message in Step S209 may include, for example, a terminal capability (UE radio capability).
  • the eNB 23 may transmit the ECM configuration information (ECM configuration) together with the radio resource configuration information (RRC Configuration) in order to cause the MTC UE 21 to execute the ECM (RRC Connection Reconfiguration).
  • ECM configuration ECM configuration information
  • RRC Configuration radio resource configuration information
  • the MTC UE 21 performs data communication based on the ECM configuration information received from the eNB 23 in Step S210 or based on the ECM configuration information that the MTC UE 21 has previously received and held (M2M data with ECM).
  • a configuration example of a radio communication system according to this embodiment may be the same as that of Fig. 1 described in the first embodiment.
  • a method for determining in an eNB 33 whether to apply the coverage enhancement processing regarding the ECM e.g., PDSCH/PUSCH repetition
  • the technical ideas described in this embodiment may be used alone or combination with the technical ideas described in the first or second embodiment stated above.
  • the eNB 33 controls communication between the MTC UE 31 and the eNB 33 using the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) based on at least one of: a terminal capability of the MTC UE 31 (UE capability); terminal information on the MTC UE 31 (UE information); a communication characteristic of the MTC UE 31 (Communication performance); and radio quality of the MTC UE 31 (Radio quality), and further based on an access cause received from the MTC UE 31 (Access cause).
  • ECM e.g., PDSCH/PUSCH repetition
  • the eNB 33 determines whether to apply the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) to the MTC UE 31 based on at least one of the terminal capability, terminal information, communication characteristic, and radio quality of the MTC UE 31, and further based on the access cause received from the MTC UE 31.
  • the ECM e.g., PDSCH/PUSCH repetition
  • the access cause, terminal capability, terminal information, communication characteristics, and radio quality are described below. However, the contents of the access cause, terminal capability, terminal information, communication characteristics, and radio quality are not limited to them.
  • the access cause may include at least one of the following two items:
  • the purpose of establishing an RRC connection may specify, for example, (a) an emergency call (emergency), (b) a high priority access (highPriorityAccess), (c) an access for mobile terminated communication (mt-Access), mobile originated signaling (mo-Signalling), (d) terminal originated data transmission (mo-Data), (e) a delay tolerant access (delayTolerantAccess), (f) a low priority access (lowPriorityAccess), (g) an access for small data communication (smallDataAccess), (h) an access for small packet communication (smallPacketAccess), (i) a limited access (limitedAccess), (j) an access for a limited service (limitedService), (k) an M2M-type access (m2mAccess), or (1) an access using the ECM (ecmAccess).
  • an emergency call emergency
  • highPriorityAccess high priority access
  • mt-Access mobile terminated communication
  • mo-Signalling mobile originated signaling
  • the service type may specify, for example, (a) a real-time service, (b) a non real-time service, or (c) M2M-type communication.
  • the terminal capability may include, for example, at least one of the following three items:
  • the radio access capability may include, for example, (a) information indicating whether the UE is supporting the terminal function defined in the 3GPP LTE (e.g., flag bit) or (b) information indicating whether the UE is supporting the ECM.
  • an information element (IE) named "EcmSupport” may be defined.
  • the true value of "EcmSupport” indicates that the ECM is supported (Supported) and the false value thereof indicates that the ECM is not supported (NotSupported).
  • an IE named "EnhancedCoverageMode” may be defined. For example, when EcmSupport is set to a value "Supported", it indicates that the UE is supporting the ECM. On the other hand, if the UE does not support the ECM, EcmSupport may be set to a value "NotSupported". Alternatively, no sending of this IE may imply that the UE is not supporting the ECM.
  • the device capability may include, for example, (a) information indicating that the UE is an MTC UE, (b) information indicating that communication capability of the UE is limited (compared to that of a normal UE), or (c) information indicating that the UE performs only a specific communication (e.g., M2M-type communication).
  • the terminal category may include, for example, (a) information indicating one of terminal categories defined in the 3GPP LTE or (b) information indicating one of access classes defined in the 3GPP LTE.
  • New terminal category or new access class may be defined for MTC UEs performing M2M-type communication.
  • a new category e.g., category 0
  • a new access class AC that indicates infrequent communication or allows only infrequent communication may be defined.
  • the terminal information may include at least one of the following three items:
  • the terminal type may include, for example, (a) information indicating whether the UE is a normal UE (non-MTC UE) or an MTC UE, (b) information indicating whether the UE has mobility (or information indicating that the UE has no mobility), or (c) information indicating whether there is a power supply for the UE.
  • the device type may include, for example, (a) information indicating the type of the operating system (OS) installed in the UE or (b) information indicating the type of the M2M-type communication performed by the UE (i.e., sub-category information of the M2M).
  • OS operating system
  • M2M-type communication i.e., sub-category information of the M2M
  • the terminal context may include, for example, (a) information on the aforementioned terminal capability, (b) RRC control information configured in the UE (e.g., information contained in a RadioResrouceConfigCommon IE and a RadioResourceConfigDedicated IE), (c) information regarding the mobility of the UE (mobility information), (d) information indicating whether the UE is executing the ECM (ECM execution information), or (e) information indicating whether the UE executed the ECM before (e.g., when the UE was in the RRC_CONNECTED state last time) (ECM status information).
  • the communication characteristic may include, for example, at least one of the following two items:
  • the performance measurement result may include, for example, (a) measurements result of throughput (e.g., Scheduled IP Throughput) by an eNB 33 (or Operation Administration and Maintenance (OAM)), (b) measurement results of packet loss (Packet Loss Rate), or (c) measurement results of packet discard (Packet Discard Rate).
  • a) measurements result of throughput e.g., Scheduled IP Throughput
  • OAM Operation Administration and Maintenance
  • Packet Loss Rate measurement results of packet loss
  • Packet Discard Rate Packet Discard Rate
  • the statistical communication quality may include, for example, (a) the number of handover attempts or a handover attempt rate, (b) a handover success rate or a handover failure rate, (c) a communication interval or a communication frequency, (d) a packet occurrence interval or a packet occurrence frequency, (e) a packet arrival interval (packet inter-arrival time) or a packet arrival frequency (packet inter-arrival rate), (f) an access interval or an access frequency, or (g) an interval or a frequency of an RRC connection establishment or a NAS connection establishment.
  • the radio quality may include, for example, at least one of the following two items:
  • the received quality of a reference signal may include, for example, received power (RSRP), (b) reception quality (RSRQ), or a received power intensity (RSSI), of a downlink RS at the UE or (b) received power at the eNB 33 of an uplink reference signal (Sounding Reference Signal: SRS) transmitted by the UE.
  • RSRP received power
  • RSRQ reception quality
  • RSSI received power intensity
  • SRS Sounding Reference Signal
  • the eNB 33 may receive the terminal capability or the terminal information of the MTC UE 31 stated above either from the MTC UE 31 or from the EPC.
  • the following effects may be expected. That is, if whether to apply the coverage enhancement processing regarding the ECM to the MTC UE 31 is determined based on only the access cause of the MTC UE 31, it will be impossible to sufficiently consider the status of each MTC UE 31.
  • RACH repetition and PDSCH/PUSCH repetition are separately applied to each MTC UE.
  • consumed radio resources will increase as the number of MTC UEs that is performing the ECM increases. Accordingly, the determination regarding whether to execute the ECM is preferably performed considering the status of each of the MTC UEs.
  • the eNB 33 further considers at least one of the terminal capability, terminal information, communication characteristic, and radio quality of the MTC UE 31 when determining whether to execute the ECM. Therefore, according to this embodiment, it is possible to determine whether to execute the ECM with consideration of the status of each MTC UE.
  • Fig. 4 is a sequence diagram showing one example of operations of the MTC UE 31, the eNB 33, and the core network node 341 according to this embodiment.
  • the core network node 341 is a node that is included in the EPC (e.g., an MME or an HSS or both).
  • the eNB 33 determines whether to apply the coverage enhancement processing regarding the ECM to the MTC UE 31 based on the access cause (e.g., Establishment cause), terminal capability (e.g., UE radio access capability), and terminal information (e.g., UE type) of the MTC UE 31.
  • Fig. 4 shows only the messages that are necessary for explanation of this embodiment and some messages included in the procedure specified in the LTE standard are not shown.
  • the initial state of the MTC UE 31 shown in Fig. 4 is RRC_IDLE.
  • Step S301 in response to an arrival of a periodic or non-periodic communication opportunity, the MTC UE 31 transmits a request for establishing a radio connection to the eNB 23 in order to start communication (RRC Connection Request).
  • the MTC UE 31 may transmit an RRC Connection Request containing an Establishment cause set to "delayTolerantAccess" in order to indicate a delay tolerant access.
  • the MTC UE 31 transitions to RRC_CONNECTED upon completion of the procedure for establishing the radio connection (RRC Connection) (not shown).
  • Step S302 the eNB 33 sends a request for establishing an EPS bearer for the MTC UE 31 to the core network node 341 (Initial UE message).
  • This Initial UE message encapsulates a Non-Access Stratum (NAS) message (e.g., NAS: Service Request) from the MTC UE 31.
  • NAS Non-Access Stratum
  • Step S303 in response to receiving the NAS message encapsulated in the Initial UE message, the core network node 341 sends, to the eNB 33, information that is necessary to establish a radio access bearer for the MTC UE 31 (Initial Context Setup Request).
  • the message in Step S303 may include, for example, one or both of the terminal capability (UE radio capability) and the terminal type (UE type).
  • Step S304 the eNB 33 requests the MTC UE 31 to transmit the terminal capability as necessary (UE Capability Inquiry).
  • Step S305 in response to the request from the eNB 33, the MTC UE 31 notifies the eNB 33 of the terminal capability of the MTC UE 31 (UE Capability Information).
  • the message in Step S305 may contain, for example, UE-EUTRA-capability.
  • Step S306 the eNB 33 determines whether to cause the MTC UE 31 to execute the ECM (in other words, whether to apply the coverage enhancement processing regarding the ECM to the MTC UE 31) (ECM decision). As one example, if the establishment cause of the MTC UE 31 indicates "delayTolerantAccess" and the radio access capability of the MTC UE 31 indicates supporting the ECM, the eNB 33 may decide to make the MTC UE 31 execute the ECM.
  • Step S307 the eNB 33 transmits the ECM configuration information (ECM configuration) together with the radio resource configuration information (RRC Configuration) in order to make the MTC UE 31 execute the ECM.
  • ECM configuration ECM configuration information
  • RRC Configuration radio resource configuration information
  • Step S308 the MTC UE 31 starts executing the ECM in accordance with the radio resource configuration information and the ECM configuration information received from the eNB 13 (ECM start).
  • ECM start ECM start
  • Step S309 the MTC UE 31 performs data communication while performing the coverage enhancement processing regarding the ECM (M2M data with ECM).
  • the procedure shown in Fig. 4 is merely one example.
  • the eNB 33 may further consider one or both of the communication characteristic and the radio quality. Specifically, the eNB 33 may first determine to execute the ECM for the MTC UE 31 based on the information on the MTC UE 31 including the access cause, the terminal capability, and the terminal information. The eNB 33 may then determine whether to continue executing the ECM for the MTC UE 31 based on the communication characteristic of the MTC UE 31 or the radio quality of the MTC UE 31, or both. As stated above, since the eNB 31 considers the communication characteristic or the radio quality of the MTC UE 31, it is possible to determine necessity of performing the ECM more appropriately.
  • the eNB 33 may acquire, for example, the number of handover attempts (or an attempt rate) as the communication characteristic of the MTC UE 31, and if the eNB 33 determines that the MTC UE 31 is stationary or near-stationary based on the acquired information, the eNB 33 may continue executing the ECM. On the other hand, if the eNB 33 determines that the MTC UE 31 is moving, the eNB 33 may suspend (or stop) executing the ECM for the MTC UE 31.
  • the eNB 33 may acquire the RSRP or the CQI as the radio quality of the MTC UE 31, and if the eNB 33 determines that the RSRP or the CQI acquired is smaller than a predetermined threshold, the eNB 33 may continue executing the ECM. On the other hand, if the eNB 33 determines that the radio quality of the MTC UE 31 is larger than the predetermined threshold, the eNB 33 may suspend (or stop) executing the ECM for the MTC UE 31.
  • the eNB 33 may acquire one or both of the communication characteristic and the radio quality of the MTC UE 31, and then determine whether execute the ECM for the MTC UE 31 based on the acquired information.
  • the eNB 31 may use the previous communication characteristic or radio quality stored in the eNB 31 or another network apparatus (e.g., OAM or MME) instead of newly measuring the communication characteristic or radio quality of the MTC UE 31. It is thus possible to avoid degradation of the communication characteristic of the MTC UE 31 caused by the delay time due to waiting for determination of whether to execute the ECM for the MTC UE 31.
  • Fig. 5 shows a configuration example of a radio communication system according to this embodiment.
  • this radio communication system includes an MTC UE 41, an eNB 43, an eNB 45, and an EPC 44.
  • the MTC UE 41 is installed in a transportation machine such as a vehicle, a railway vehicle, or a ship and therefore has mobility.
  • Fig. 5 shows an example of a heterogeneous network (HetNet). That is, the eNB 43 manages a cell 430 and the eNB 45 manages a cell 450 that covers an area smaller than that covered by the cell 430.
  • the eNB 43 is a macro base station and the eNB 45 is a pico base station. This embodiment may, however, be applied to a homogeneous network in which the cell 430 and the cell 450 have the same degree of coverage.
  • the eNB 43 notifies the eNB 45 that the MTC UE 41 is executing the ECM (in other words, the MTC UE 41 is performing the coverage enhancement processing regarding the ECM) when the MTC UE 41 that is executing the ECM is handed over from the cell 430 of the eNB 43 to the neighbouring cell 450.
  • the eNB 43 may notify the eNB 45 that the MTC UE 41 is executing the ECM (in other words, the MTC UE 41 is performing the coverage enhancement processing regarding the ECM) when the eNB 43 sends to the eNB 45 a handover request regarding the MTC UE 41.
  • the eNB 45 may control communication using the ECM between the MTC UE 41 and the eNB 45 based on the notification received from the eNB 43. For example, the eNB 45 may determine whether to apply the ECM to communication between the MTC UE 41 and the eNB 45 based on the notification received from the eNB 43.
  • the handover source base station i.e., eNB 43 informs the target base station (i.e., eNB 45) whether the MTC UE 41 is executing the ECM. Therefore, the target base station (eNB 45) does not necessarily require acquisition of radio quality of the MTC UE 41 (e.g., RSRP, RSRQ, CQI) and analysis of the acquired radio quality in order to determine whether to apply the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) to the MTC UE 41.
  • the target base station eNB 45 does not necessarily require acquisition of radio quality of the MTC UE 41 (e.g., RSRP, RSRQ, CQI) and analysis of the acquired radio quality in order to determine whether to apply the coverage enhancement processing regarding the ECM (e.g., PDSCH/PUSCH repetition) to the MTC UE 41.
  • the target base station (eNB 45) can use the notification received from the source base station (eNB 43) to determine whether or not the ECM can be applied (or whether the coverage enhancement processing of the ECM is efficient) to the MTC UE 41, on which the handover is to be performed. Therefore, according to this embodiment, it is possible to reduce time (delay) required for the target base station (target cell) to determine whether to apply the coverage enhancement processing regarding the ECM to the MTC UE 41, on which the handover is to be performed.
  • Fig. 6 is a sequence diagram showing one example of operations of the MTC UE 41, the eNB 43, and the eNB 45 according to this embodiment.
  • Fig. 6 shows only the messages that are necessary for explanation of this embodiment and some messages included in the procedure specified in the LTE standard are not shown.
  • the MTC UE 41 camps on the cell 430 of the eNB 43.
  • the eNB 43 transmits the ECM configuration information (ECM configuration-1) to the MTC UE 41.
  • ECM configuration-1 is transmitted using the RRC Connection Reconfiguration message.
  • Step S402 the MTC UE 41 starts executing the ECM (i.e., coverage enhancement processing (e.g., reception of a repeated PDSCH, repeated transmission of a PUSCH)) in accordance with the ECM configuration received from the eNB 43 (ECM start).
  • ECM coverage enhancement processing
  • Step S403 the MTC UE 41 performs data communication in accordance with the ECM configuration (M2M data with ECM).
  • Step S404 the eNB 43 determines handover of the MTC UE 41 from the cell 430 of the eNB 43 to the neighbouring cell 450 of the eNB 45 (HO decision).
  • Step S405 the eNB 43 sends a handover request for the MTC UE 41 to the eNB 45 (Handover Request).
  • the handover request in Step S405 contains information indicating that the MTC UE 41, on which the handover to be performed, is executing the ECM (ECM activated).
  • Step S406 if the eNB 45 can accept the MTC UE 41, the eNB 45 sends a message for acknowledging the handover request to the eNB 43 (Handover Request Acknowledge).
  • the acknowledgement message in Step S406 may contain the ECM configuration information that is necessary to execute the ECM in the target cell 450 (ECM configuration-2).
  • Step S407 the eNB 43 transmits a handover instruction to the MTC UE 41 in response to receiving the acknowledgement message from the eNB 45 (RRC Connection Reconfiguration).
  • the message in Step S407 may contain the ECM configuration information that is necessary to execute the ECM in the target cell 450 (ECM configuration-2).
  • Step S408 the MTC UE 41 is handed over from the cell 430 to the cell 450 and transmits a message indicating the completion of the handover to the target eNB 45 (RRC Connection Reconfiguration Complete/Handover confirm).
  • the MTC UE 41 may transmit, to the eNB 45, information indicating that the MTC UE 41 executed the ECM.
  • Step S409 the MTC UE 41 performs data communication in accordance with the ECM configuration information (ECM configuration-2) regarding the target cell 450 received via the source eNB 43 in Step S407 (M2M data with ECM).
  • ECM configuration information ECM configuration information
  • M2M data with ECM M2M data with ECM
  • Fig. 6 shows the example in which the handover request message and the acknowledgement message to the handover request are transmitted via a direct inter-eNB interface (i.e., X2 interface) provided between the source eNB 43 and the target eNB 45.
  • the messages regarding the handover may be transmitted via interfaces (i.e., S1-MME interfaces) between the eNBs 43 and the EPC 44 (i.e., MME) and between the eNB 44 and the EPC 44.
  • the notification (from the source eNB 43 to the target eNB 45) indicating that the MTC UE 41 is executing the ECM and the ECM configuration (from the target eNB 45 to the source eNB 43) regarding the target cell 450 may be transmitted via the EPC 44.
  • an eNB 53 informs an eNB 55 whether a cell 530 of the eNB 53 is supporting the ECM (in other words, the coverage enhancement processing regarding the ECM).
  • the eNB 55 is a base station that manages a neighbouring cell of the cell of the eNB 53. Further, the eNB 53 is informed by the eNB 55 whether a cell 550 of the eNB 55 is supporting the ECM (in other words, the coverage enhancement processing regarding the ECM).
  • the information may indicate support of the ECM on a per-base-station basis (i.e., the ECM is supported in all the cells of the eNB 53 or 55) or on a per-cell basis (i.e., the ECM is supported in one or more of the cells of the eNB 53 or 55 and is not supported in the remaining cell(s)).
  • the serving eNB does not know whether or not a neighbouring eNB (neighbouring cell) is supporting the ECM, the serving eNB possibly cannot adequately determine whether or not the movement to the neighbouring cell by handover or cell-reselection is effective for the MTC UE, which is supporting the ECM or is executing the ECM.
  • the serving eNB serving cell
  • the neighbouring eNB neighboreNB
  • the serving eNB serving cell
  • the neighbouring eNB neighbouring cell
  • the serving eNB should probably allow the MTC UE that is supporting the ECM to move to the neighbouring cell by handover or cell reselection.
  • the eNB 53 can know whether the eNB 55 is supporting the ECM and the eNB 55 can know whether the eNB 53 is supporting the ECM. Therefore, the eNBs 53 and 55 can contribute to residing of the MTC UE 51 that is supporting the ECM in an appropriate cell or to communication of MTC UE 51 in an appropriate cell.
  • the eNB 53 may adjust a handover parameter(s) or a cell reselection parameter(s) to be sent to an MTC UE that is supporting the ECM so that the MTC UE can be easily moved to the neighbouring cell 550. It may be possible, for example, to increase a Cell Individual Offset (CIO) that acts on radio quality of the neighbouring cell 550.
  • CIO is one of the handover parameters in the LTE and increase in CIO makes the transmission condition of a measurement report that triggers handover of the MTC UE 51 become easy to satisfy.
  • Qoffset that acts on radio quality of the neighbouring cell 550 may be decreased.
  • the Qoffset is one of the cell reselection parameters in the LTE and decrease in Qoffset makes the condition that the MTC UE 51 reselects the neighbouring cell 550 become easy to satisfy.
  • Fig. 7 is a sequence diagram showing one example of operations of the eNB 53 and the eNB 55 according to this embodiment. Fig. 7 shows only the messages that are necessary for explanation of this embodiment and some messages included in the procedure specified in the LTE standard are not shown.
  • Step S501 the eNB 53 is triggered to establish a direct interface (X2 interface) with the eNB 55 that manages the neighbouring (or surrounding) cell 550 of the cell 530 managed by the eNB 53 (X2 setup Triggered).
  • Step S502 the eNB 53 sends a request for establishing the X2 interface to the eNB 55 (X2 Setup Request).
  • the message in Step S502 indicates whether the ECM is supported in the cell 530 of the eNB 53.
  • the eNB 53 sends information indicating that the ECM is supported (ECM supported).
  • the information may indicate support of the ECM on a per-base-station basis (i.e., the ECM is supported in all the cells of the eNB 53) or on a per-cell basis (i.e., the ECM is supported in one or more of the cells of the eNB 53 and is not supported in the remaining cell(s)).
  • Step S503 the eNB 55 sends a response message in response to the request for establishing the X2 interface received from the eNB 53 (X2 Setup Response).
  • the response message in Step S503 indicates whether the ECM is supported in the cell 550 of the eNB 55. In the example shown in Fig. 7 , the cell 550 does not support the ECM. Therefore, the response message in Step S503 does not contain information indicating that the ECM is supported. Alternatively, the response message in Step S503 may contain information explicitly indicating that the ECM is not supported.
  • Step S504 the configuration of the eNB 55 is updated and the eNB 55 begins supporting the ECM. Accordingly, in Step S505, the eNB 55 notifies the eNB 53 that the eNB configuration has been updated (ENB Configuration Update).
  • the message in Step S505 contains information indicating that the ECM is supported in the cell 550 of the eNB 55 (ECM supported). The information may indicate support of the ECM on a per-base-station basis (i.e., the ECM is supported in all the cells of the eNB 55) or on a per-cell basis (i.e., the ECM is supported in one or more of the cells of the eNB 55 and is not supported in the remaining cell(s)).
  • the eNB 53 sends a response message in response to the notification from the eNB 53 of the eNB configuration update (ENB Configuration Update Acknowledge).
  • Each of the MTC UEs 11, 21, 31, and 41 described in the first to fifth embodiments may include a transceiver to communicate with an eNB and a controller that is coupled to the transceiver.
  • the controller executes the communication control regarding the ECM performed by the MTC UE 11, 21, 31, or 41 described in the first to fifth embodiments.
  • Each of the eNBs 13, 23, 33, 43, 45, 53, and 55 described in the first to fifth embodiments may include a transceiver to communicate with UEs including MTC UEs and a controller that is coupled to the transceiver.
  • the controller executes the communication control regarding the ECM performed by the eNB 13, 23, 33, 43, 45, 53, or 55 described in the first to fifth embodiments.
  • Each of the core network nodes 141, 241, and 341 described in the first to fifth embodiments may include an interface to communicate with an eNB and a controller that is coupled to the interface.
  • the controller executes the communication control regarding the ECM performed by the core network node 141, 241, or 341 described in the first to fifth embodiments.
  • Figs. 8 to 10 are block diagrams respectively showing configuration examples of the MTC UE 11, the eNB 13, and the core network node 141 according to the first embodiment.
  • the MTC UE 11 includes a transceiver 111 and a controller 112.
  • the transceiver 111 is configured to communicate with the eNB 13.
  • the controller 112 is configured to control execution of the coverage enhancement processing regarding the ECM in the MTC UE 11 in accordance with instructions from the eNB 13.
  • the eNB 13 includes a transceiver 131 and a controller 132.
  • the transceiver 131 is configured to communicate with UEs including the MTC UEs 11 and the normal UE 12.
  • the controller 132 is configured to control communication between the MTC UEs 1 and the eNB 13 using the coverage enhancement processing regarding the ECM.
  • the controller 132 receives from the EPC 14 the history information, which indicates whether the coverage enhancement processing (e.g., PDSCH/PUSCH repetition) regarding the ECM was executed in previous communication with each MTC UE (M2M terminal) 11.
  • the controller 132 controls communication between each MTC UE 11 and the eNB 13 using the coverage enhancement processing regarding the ECM based on the history information received from the EPC 14.
  • the core network node 141 includes an interface 1411 and a controller 1412.
  • the interface 1411 is used to send and receive signaling messages to and from the eNB 13.
  • the controller 1412 is configured to send and receive signaling messages to and from the eNB 13 via the interface 1411.
  • the controller 1412 sends the history information, which indicates whether the specific coverage enhancement processing was executed in previous communication with each MTC UE 11, to the eNB 13 via the interface 1411 during a procedure for establishing an EPS bearer between each MTC UE 11 and the EPC 14.
  • the controllers included in the MTC UEs, the eNBs, and the core network nodes according to the above embodiments may be implemented by causing a computer including at least one processor (e.g., microprocessor, Micro Processing Unit (MPU), Central Processing Unit (CPU)) to execute a program.
  • processor e.g., microprocessor, Micro Processing Unit (MPU), Central Processing Unit (CPU)
  • MPU Micro Processing Unit
  • CPU Central Processing Unit
  • programs containing set of instructions that causes a computer to perform algorithms regarding the MTC UE, the eNB, or the core network node described using the sequence diagrams and the like may be supplied to the computer.
  • Non-transitory computer readable media include any type of tangible storage media.
  • Examples of non-transitory computer readable media include magnetic storage media (such as flexible disks, magnetic tapes, hard disk drives, etc.), optical magnetic storage media (e.g., magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R, CD-R/W, and semiconductor memories (such as mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM), etc.).
  • These programs may be provided to a computer using any type of transitory computer readable media.
  • Transitory computer readable media examples include electric signals, optical signals, and electromagnetic waves.
  • Transitory computer readable media can provide the program to a computer via a wired communication line (e.g., electric wires, and optical fibers) or a wireless communication line.
  • MTC UEs are configured with the special operation mode, i.e., the Enhanced Coverage Mode (ECM) and perform the coverage enhancement processing (e.g., RACH repetition and PDSCH/PUSCH repetition) regarding the ECM.
  • ECM Enhanced Coverage Mode
  • the MTC UEs is only required to execute the special coverage enhancement processing (e.g., RACH repetition and PDSCH/PUSCH repetition) and do not have to be configured with the special operation mode (i.e., ECM).
  • the MTC UEs 11, 21, 31, and 41 may execute the special coverage enhancement processing (e.g., RACH repetition and PDSCH/PUSCH repetition) in accordance with the radio resource configuration without setting the special operation mode such as the ECM or without receiving an instruction regarding the special operation mode.
  • the special coverage enhancement processing e.g., RACH repetition and PDSCH/PUSCH repetition
  • normal terminals UE
  • M2M terminals MTC UEs
  • the LTE system has been mainly described.
  • these embodiments may be applied to radio communication systems other than the LTE system (e.g., 3GPP UMTS, 3GPP2 CDMA2000 system (1xRTT, HRPD), GSM/GPRS system, or WiMAX system).
  • radio communication systems e.g., 3GPP UMTS, 3GPP2 CDMA2000 system (1xRTT, HRPD), GSM/GPRS system, or WiMAX system.
  • the operations of the eNB may be performed by a NodeB, an RNC or the combination thereof.
  • the term "base station” used in the specification and claims means one or more entities installed in a radio access network, for example, any one or combination of a NodeB or an RNC in the UMTS.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (17)

  1. Appareil de station de base (13) comprenant :
    un moyen de radiocommunication (131) ; et
    un moyen de commande (132) pour recevoir, en provenance d'un coeur de réseau (14), des informations historiques indiquant si un traitement de renforcement de couverture spécifique a été exécuté ou non dans une communication antérieure avec un terminal machine-machine, M2M (11) et commander une communication utilisant le traitement de renforcement de couverture spécifique entre le terminal M2M (11) et le moyen de radiocommunication (131) d'après les informations historiques, dans lequel
    le moyen de commande (132) est adapté pour recevoir, en provenance du coeur de réseau (14), des informations de mobilité indiquant un degré de mobilité du terminal M2M (11), et
    le moyen de commande (132) est adapté pour commander la communication entre le terminal M2M (11) et le moyen de radiocommunication (131) selon que les informations de mobilité indiquent que le terminal M2M (11) est sensiblement stationnaire.
  2. Appareil de station de base (13) selon la revendication 1, dans lequel le moyen de commande (132) est adapté pour déterminer s'il faut exécuter le traitement de renforcement de couverture spécifique en communication entre le terminal M2M (11) et le moyen de radiocommunication (131), d'après les informations historiques.
  3. Appareil de station de base (13) selon la revendication 1 ou 2, dans lequel le moyen de commande (132) est adapté pour recevoir les informations historiques en provenance du coeur de réseau (14) lors de l'établissement d'une connexion radio avec le terminal M2M (11) ou pendant qu'une procédure d'établissement d'un porteur entre le terminal M2M (11) et le coeur de réseau (14) est en cours de réalisation.
  4. Appareil de station de base (13) selon la revendication 3, dans lequel, lors de la libération de la connexion radio avec le terminal M2M (11), le moyen de commande (132) est adapté pour envoyer, au coeur de réseau (14), des informations de terminal indiquant si le traitement de renforcement de couverture spécifique a été exécuté ou non pour le terminal M2M (11) dans l'appareil de station de base (13).
  5. Appareil de station de base (13) selon la revendication 1 ou 2, dans lequel le moyen de commande (132) est adapté pour recevoir les informations historiques en provenance du terminal M2M (11) lors de l'établissement d'une connexion radio avec le terminal M2M (11) ou pendant qu'une procédure d'établissement d'un porteur entre le terminal M2M (11) et le coeur de réseau (14) est en cours de réalisation.
  6. Appareil de station de base (13) selon l'une quelconque des revendications 1 à 5, dans lequel le traitement de renforcement de couverture spécifique comprend un traitement réalisé par un terminal radio qui est configuré pour prendre en charge un mode de couverture renforcée, ECM.
  7. Appareil de station de base (13) selon l'une quelconque des revendications 1 à 6, dans lequel le traitement de renforcement de couverture spécifique comprend au moins l'une d'une transmission répétée d'un canal physique partagé de liaison montante, PUSCH, sur de multiples sous-trames et d'une transmission répétée d'un canal physique partagé de liaison descendante, PDSCH, sur de multiples sous-trames.
  8. Appareil de station de base (13) selon l'une quelconque des revendications 1 à 7, dans lequel le moyen de commande (132) est adapté pour notifier à une station de base voisine que le terminal M2M (11) est en train d'exécuter le traitement de renforcement de couverture spécifique lorsque le terminal M2M (11) est transféré d'une cellule (130) de l'appareil de station de base (13) à une cellule voisine (450).
  9. Appareil de station de base (13) selon l'une quelconque des revendications 1 à 8, dans lequel le moyen de commande (132) est adapté pour informer une station de base voisine (45) si le traitement de renforcement de couverture spécifique est supporté dans une cellule (130) de l'appareil de station de base (13), et le moyen de commande (132) est adapté pour être informé par la station de base voisine (45) si le traitement de renforcement de couverture spécifique est pris en charge dans une cellule (450) de la station de base voisine (45).
  10. Appareil de coeur de réseau (141) compris dans un réseau fédérateur, l'appareil de coeur de réseau comprenant :
    une interface (1411) utilisée pour transmettre et recevoir des messages de signalisation vers et depuis une station de base (13) ; et
    un moyen de commande (1412) pour envoyer, à la station de base (13) via l'interface (1411) pendant une procédure d'établissement d'un porteur entre un terminal machine-machine, M2M (11) et le coeur de réseau (14), des informations historiques indiquant si un traitement de renforcement de couverture spécifique a été exécuté ou non dans une communication antérieure avec le terminal M2M (11), dans lequel
    le moyen de commande (132) est adapté pour envoyer, à la station de base (13), des informations de mobilité indiquant un degré de mobilité du terminal M2M (11),
    la communication utilisant le traitement de renforcement de couverture spécifique entre le terminal M2M (11) et le moyen de radiocommunication (131) est commandée par la station de base (13) d'après les informations historiques, et
    la communication entre le terminal M2M (11) et la station de base (13) est commandée par la station de base (13) selon que les informations de mobilité indiquent que le terminal M2M (11) est sensiblement stationnaire.
  11. Appareil de coeur de réseau (141) selon la revendication 10, dans lequel le moyen de commande (1412) est adapté pour envoyer, à la station de base (13) via l'interface (1411), des informations de mobilité indiquant un degré de mobilité du terminal M2M (11).
  12. Appareil de coeur de réseau (141) selon la revendication 10 ou 11, dans lequel le moyen de commande (1412) est adapté pour, lorsqu'une connexion radio avec le terminal M2M (11) est libérée, recevoir, en provenance de la station de base via l'interface, des informations de terminal indiquant si le traitement de renforcement de couverture spécifique a été exécuté ou non pour le terminal M2M (11) dans la station de base (13).
  13. Appareil de coeur de réseau (141) selon la revendication 12, dans lequel le moyen de commande (1412) est adapté pour envoyer les informations de terminal reçues en provenance d'une première station de base (43) à une deuxième station de base (45) différente de la première station de base (43) en tant qu'informations historiques.
  14. Procédé mis en oeuvre par une station de base (13), le procédé comprenant :
    la réception, en provenance d'un coeur de réseau (14), d'informations historiques indiquant si un traitement de renforcement de couverture spécifique a été exécuté ou non dans une communication antérieure avec un terminal machine-machine, M2M (11) ; et
    la commande d'une communication utilisant le traitement de renforcement de couverture spécifique entre le terminal M2M (11) et la station de base (13) d'après les informations historiques,
    dans lequel le procédé comprend en outre :
    la réception, en provenance du coeur de réseau (14), d'informations de mobilité indiquant un degré de mobilité du terminal M2M (11) ; et
    la commande de la communication entre le terminal M2M (11) et la station de base (13) selon que les informations de mobilité indiquent que le terminal M2M (11) est sensiblement stationnaire.
  15. Procédé mis en oeuvre par un appareil de coeur de réseau (141) qui est compris dans un coeur de réseau (14), le procédé comprenant :
    l'envoi, à une station de base (13) pendant une procédure d'établissement d'un porteur entre un terminal machine-machine, M2M (11) et le coeur de réseau (14), d'informations historiques indiquant si un traitement de renforcement de couverture spécifique a été exécuté ou non dans une communication antérieure avec le terminal M2M (11) ; et
    l'envoi, à la station de base (13), d'informations de mobilité indiquant un degré de mobilité du terminal M2M (11), dans lequel
    la communication utilisant le traitement de renforcement de couverture spécifique entre le terminal M2M (11) et le moyen de radiocommunication (131) est commandée par la station de base (13) d'après les informations historiques, et
    la communication entre le terminal M2M (11) et la station de base (13) est commandée par la station de base (13) selon que les informations de mobilité indiquent que le terminal M2M (11) est sensiblement stationnaire.
  16. Support non transitoire lisible par ordinateur stockant un programme pour amener un ordinateur à mettre en oeuvre un procédé concernant une station de base (13), dans lequel le procédé comprend :
    la réception, en provenance d'un coeur de réseau (14), d'informations historiques indiquant si un traitement de renforcement de couverture spécifique a été exécuté ou non dans une communication antérieure avec un terminal machine-machine, M2M (11) ; et
    la commande d'une communication utilisant le traitement de renforcement de couverture spécifique entre le terminal M2M (11) et la station de base (13) d'après les informations historiques,
    dans lequel le procédé comprend en outre :
    la réception, en provenance du coeur de réseau (14), d'informations de mobilité indiquant un degré de mobilité du terminal M2M (11) ; et
    la commande de la communication entre le terminal M2M (11) et la station de base (13) selon que les informations de mobilité indiquent que le terminal M2M (11) est sensiblement stationnaire.
  17. Support non transitoire lisible par ordinateur stockant un programme pour amener un ordinateur à mettre en oeuvre un procédé concernant un coeur de réseau (14), dans lequel le procédé comprend :
    l'envoi, à une station de base (13) pendant une procédure d'établissement d'un porteur entre un terminal machine-machine, M2M (11) et le réseau fédérateur (14), d'informations historiques indiquant si un traitement de renforcement de couverture spécifique a été exécuté ou non dans une communication antérieure avec le terminal M2M (11) ; et
    l'envoi, à la station de base (13), d'informations de mobilité indiquant un degré de mobilité du terminal M2M (11), dans lequel
    la communication utilisant le traitement de renforcement de couverture spécifique entre le terminal M2M (11) et le moyen de radiocommunication (131) est commandée par la station de base (13) d'après les informations historiques, et
    la communication entre le terminal M2M (11) et la station de base (13) est commandée par la station de base (13) selon que les informations de mobilité indiquent que le terminal M2M (11) est sensiblement stationnaire.
EP14880670.6A 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur Active EP3101941B1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18165057.3A EP3364681A3 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur
EP19195447.8A EP3595349A1 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2014015868 2014-01-30
PCT/JP2014/004549 WO2015114695A1 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur

Related Child Applications (4)

Application Number Title Priority Date Filing Date
EP18165057.3A Division EP3364681A3 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur
EP18165057.3A Division-Into EP3364681A3 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur
EP19195447.8A Division EP3595349A1 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur
EP19195447.8A Division-Into EP3595349A1 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur

Publications (3)

Publication Number Publication Date
EP3101941A1 EP3101941A1 (fr) 2016-12-07
EP3101941A4 EP3101941A4 (fr) 2017-10-11
EP3101941B1 true EP3101941B1 (fr) 2019-10-23

Family

ID=53756321

Family Applications (3)

Application Number Title Priority Date Filing Date
EP18165057.3A Pending EP3364681A3 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur
EP14880670.6A Active EP3101941B1 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur
EP19195447.8A Pending EP3595349A1 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP18165057.3A Pending EP3364681A3 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP19195447.8A Pending EP3595349A1 (fr) 2014-01-30 2014-09-04 Station de base, terminal machine-machine (m2m), procédé et support lisible par ordinateur

Country Status (6)

Country Link
US (5) US10652757B2 (fr)
EP (3) EP3364681A3 (fr)
JP (4) JP6390625B2 (fr)
KR (5) KR102023446B1 (fr)
CN (3) CN106851533B (fr)
WO (1) WO2015114695A1 (fr)

Families Citing this family (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI683563B (zh) 2014-01-29 2020-01-21 日商新力股份有限公司 在無線電信系統中與基地台通訊的電路、終端裝置、基地台及其操作方法
CN109618310B (zh) * 2014-10-20 2021-10-22 华为技术有限公司 一种寻呼方法及设备
CN107211417A (zh) * 2015-01-28 2017-09-26 株式会社Ntt都科摩 用户终端及无线通信方法
JP6785664B2 (ja) * 2015-01-28 2020-11-18 シャープ株式会社 端末装置、基地局装置および方法
JP2016167697A (ja) * 2015-03-09 2016-09-15 富士通株式会社 無線通信装置、接続制御方法、及び、無線通信システム
US10454521B2 (en) * 2015-06-24 2019-10-22 Lg Electronics Inc. Method and apparatus for randomization of interference in cellular internet of things (IOT) system
CN108141880B (zh) * 2015-10-05 2021-08-31 瑞典爱立信有限公司 提供对无线装置的增强覆盖的移动性支持的系统和方法
WO2017077979A1 (fr) * 2015-11-05 2017-05-11 株式会社Ｎｔｔドコモ Dispositif utilisateur, station de base, et procédé d'établissement de connexion
JP6123009B1 (ja) * 2015-11-05 2017-04-26 株式会社Ｎｔｔドコモ ユーザ装置、基地局、及び接続確立方法
CN106686723B (zh) * 2015-11-06 2019-09-17 电信科学技术研究院 释放ue上下文及其控制方法及装置、寻呼方法及装置
US10454646B2 (en) 2015-11-14 2019-10-22 Qualcomm Incorporated Sounding reference signal transmissions in enhanced machine type communication
CN106961703B (zh) * 2016-01-11 2021-07-23 中兴通讯股份有限公司 一种信息传输方法、装置和系统
EP3403445B1 (fr) * 2016-01-13 2020-09-16 Telefonaktiebolaget LM Ericsson (PUBL) Configuration d'intervalles autonomes en fonction du niveau de répétition dans une couverture améliorée
US10887805B2 (en) * 2016-04-01 2021-01-05 Htc Corporation Device and method of handling handover
CN107484211B (zh) 2016-06-08 2020-06-26 华为技术有限公司 切换接入点的方法及装置
EP3264804B1 (fr) * 2016-06-27 2020-08-05 Vodafone GmbH Distribution d'un message à un dispositif mobile dans un réseau de communication mobile
RU2018118851A (ru) 2016-07-22 2019-11-25 Бейджин Сяоми Мобайл Софтвеа Ко., Лтд. Способ, устройство и система для приема и передачи информации
CN108702810B (zh) * 2016-07-29 2021-09-14 Lg 电子株式会社 用于第一无线电接入网络节点的方法和装置
KR20180092787A (ko) 2017-02-10 2018-08-20 삼성전자주식회사 이동 통신 시스템에서 다중연결을 사용한 핸드오버 시 보안키를 처리하는 방법 및 장치
EP3361820B1 (fr) * 2017-02-10 2020-10-28 Samsung Electronics Co., Ltd. Procédé et appareil de fonctionnement en mode inactif dans un système de communication sans fil
CN108737016B (zh) * 2017-04-17 2021-10-01 上海诺基亚贝尔股份有限公司 用于wce模式的激活和去激活的方法、设备和计算机可读介质
CA3065401A1 (fr) * 2017-06-30 2019-01-30 Huawei Technologies Co., Ltd. Procede et dispositif de communication
US11290931B2 (en) 2017-12-07 2022-03-29 Sony Corporation Electronic device, infrastructure equipment and methods
JP2019121834A (ja) * 2017-12-28 2019-07-22 シャープ株式会社 端末装置、基地局装置、通信方法、および、集積回路
EP3664559B1 (fr) * 2018-04-16 2022-01-05 LG Electronics Inc. Procédé de transmission et de réception de canal physique partagé de commande de liaison montante dans un système de communication sans fil, et dispositif prenant en charge ce procédé
CN110831054B (zh) 2018-08-07 2023-04-07 维沃移动通信有限公司 确定小区支持的组网类型的方法和设备
US11838870B2 (en) * 2018-08-30 2023-12-05 Mediatek Singapore Pte. Ltd. Methods for reducing power consumption of a communication apparatus and a communication apparatus utilizing the same
CN109413715A (zh) * 2018-11-05 2019-03-01 深圳市有方科技股份有限公司 快速接入物联网的实现方法、实现设备及计算机可读存储介质
JPWO2022079861A1 (fr) * 2020-10-15 2022-04-21

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7640008B2 (en) 2002-10-18 2009-12-29 Kineto Wireless, Inc. Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system
WO2006075677A1 (fr) 2005-01-17 2006-07-20 Sharp Kabushiki Kaisha Systeme de commande de reseau de communication
RU2433572C2 (ru) * 2007-01-15 2011-11-10 Нокиа Корпорейшн Способ и устройство для восстановления контекста
CN101369912B (zh) * 2007-08-13 2011-04-06 大唐移动通信设备有限公司 一种用户设备上下文更新方法与装置
US9247420B2 (en) * 2007-12-12 2016-01-26 Lg Electronics Inc. Method of managing user equipment capabilities
JP5155819B2 (ja) * 2008-10-30 2013-03-06 パナソニック株式会社 無線送受信装置および方法、ならびに、端末装置、基地局装置および無線通信システム
JP4772910B1 (ja) 2010-04-05 2011-09-14 株式会社エヌ・ティ・ティ・ドコモ 移動通信システムにおける基地局及び方法
WO2012028199A1 (fr) 2010-09-03 2012-03-08 Nokia Siemens Networks Oy Système de relais coopérants
US20120071200A1 (en) * 2010-09-22 2012-03-22 Infineon Technologies Ag Method and device for selecting a serving base station, mobile communication network, base station, and method for determining transmission characteristics
CN103155686B (zh) * 2010-10-08 2016-04-06 诺基亚通信公司 用于通信的装置和方法
WO2012050493A1 (fr) 2010-10-13 2012-04-19 Telefonaktiebolaget L M Ericsson (Publ) Procédé dans un noeud de réseau d'un réseau de communications sans fil
US8838110B2 (en) * 2010-12-03 2014-09-16 Futurewei Technologies, Inc. System and method for user equipment mobility support in a heterogeneous network
JP5921446B2 (ja) * 2011-01-07 2016-05-24 三菱電機株式会社 通信システム
TW201603506A (zh) * 2011-01-10 2016-01-16 內數位專利控股公司 在肌器對機器或行動輔助佈署中呼叫方法及裝置
EP2724581A1 (fr) * 2011-06-22 2014-04-30 Telefonaktiebolaget LM Ericsson (PUBL) Procédé pour réduire un n ud de signalisation
GB2493347B (en) * 2011-07-29 2016-01-20 Sca Ipla Holdings Inc Mobile communications network, infrastructure equipment and method
US9232540B2 (en) * 2011-09-30 2016-01-05 Qualcomm Incorporated Random access channel design for narrow bandwidth operation in a wide bandwidth system
EP3490320B1 (fr) 2011-09-30 2023-08-23 InterDigital Patent Holdings, Inc. Communication de dispositif utilisant une largeur de bande de canal réduite
CN102348259B (zh) 2011-10-18 2014-06-04 大唐移动通信设备有限公司 一种初始ue消息的处理方法及装置
EP2603030B1 (fr) 2011-12-09 2014-12-24 Fujitsu Limited Gestion d'interférence dans les réseaux de communication sans fil
US9143984B2 (en) * 2012-04-13 2015-09-22 Intel Corporation Mapping of enhanced physical downlink control channels in a wireless communication network
CN107071705B (zh) 2012-05-23 2021-02-23 华为技术有限公司 寻呼窄带终端的方法、网络设备、基站及系统
JP5922511B2 (ja) 2012-07-06 2016-05-24 株式会社山田製作所 制御バルブ
JP5410591B2 (ja) 2012-10-24 2014-02-05 パナソニック株式会社 無線送受信装置および無線送受信方法
EP2725852B1 (fr) 2012-10-29 2016-07-20 Alcatel Lucent Optimisation d'une charge de signalisation de réseau et/ou de la consommation d'énergie d'équipement utilisateur dans un système mobile de paquets
US9264966B2 (en) * 2013-03-11 2016-02-16 Alcatel Lucent Method and apparatus for LTE handover reduction
CN104113851B (zh) * 2013-04-16 2019-04-16 中兴通讯股份有限公司 一种d2d发现方法及基站、用户设备
US10091763B2 (en) * 2013-08-21 2018-10-02 Telefonaktiebolaget L M Ericsson (Publ) Paging in coverage extension mode
EP2903363B1 (fr) 2014-01-30 2023-08-16 Alcatel Lucent Indiquer des propriétés d'un équipement utilisateur à un noeud de commande de réseau

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US20170238193A1 (en) 2017-08-17
CN111556470A (zh) 2020-08-18
JPWO2015114695A1 (ja) 2017-03-23
US20180234858A1 (en) 2018-08-16
EP3364681A3 (fr) 2018-10-31
EP3595349A1 (fr) 2020-01-15
JP6465238B2 (ja) 2019-02-06
US20160345119A1 (en) 2016-11-24
KR20170064557A (ko) 2017-06-09
JP2018129857A (ja) 2018-08-16
JP7176557B2 (ja) 2022-11-22
KR20180095949A (ko) 2018-08-28
EP3101941A1 (fr) 2016-12-07
JP6816752B2 (ja) 2021-01-20
KR20180129965A (ko) 2018-12-05
US10652757B2 (en) 2020-05-12
KR101851976B1 (ko) 2018-04-25
WO2015114695A1 (fr) 2015-08-06
CN106851533B (zh) 2021-07-06
KR101744666B1 (ko) 2017-06-08
JP2019068463A (ja) 2019-04-25
EP3101941A4 (fr) 2017-10-11
CN105940704B (zh) 2020-05-15
KR101923399B1 (ko) 2018-11-29
US20210337396A1 (en) 2021-10-28
US10412596B2 (en) 2019-09-10
CN111556470B (zh) 2023-11-24
CN105940704A (zh) 2016-09-14
KR102023446B1 (ko) 2019-09-20
KR20180042461A (ko) 2018-04-25
KR101891571B1 (ko) 2018-08-27
JP6390625B2 (ja) 2018-09-19
EP3364681A2 (fr) 2018-08-22
US20190357058A1 (en) 2019-11-21
US10039010B2 (en) 2018-07-31
JP2021048635A (ja) 2021-03-25
CN106851533A (zh) 2017-06-13
US11917423B2 (en) 2024-02-27
KR20160110423A (ko) 2016-09-21

Similar Documents

Publication Publication Date Title
US11917423B2 (en) Base station, machine-to-machine (M2M) terminal, method, and computer readable medium
US10440718B2 (en) Machine-to-machine (M2M) terminal, base station, method, and computer readable medium
EP3370451B1 (fr) Terminal machine-machine (m2m), station de base, procédé et support lisible par ordinateur

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20160818

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20170912

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/08 20090101ALI20170906BHEP

Ipc: H04W 24/04 20090101AFI20170906BHEP

Ipc: H04W 92/04 20090101ALI20170906BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20180927

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20190503

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602014055762

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1195084

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191115

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20191023

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200123

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200123

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200124

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200224

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200224

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602014055762

Country of ref document: DE

PG2D Information on lapse in contracting state deleted

Ref country code: IS

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200223

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1195084

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191023

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

26N No opposition filed

Effective date: 20200724

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200904

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200904

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200930

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200930

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230920

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230928

Year of fee payment: 10

Ref country code: DE

Payment date: 20230920

Year of fee payment: 10