WO2015137699A1 - Method and apparatus for performing mbms mdt in wireless communication system - Google Patents
Method and apparatus for performing mbms mdt in wireless communication system Download PDFInfo
- Publication number
- WO2015137699A1 WO2015137699A1 PCT/KR2015/002297 KR2015002297W WO2015137699A1 WO 2015137699 A1 WO2015137699 A1 WO 2015137699A1 KR 2015002297 W KR2015002297 W KR 2015002297W WO 2015137699 A1 WO2015137699 A1 WO 2015137699A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mbms
- mdt
- timer
- configuration
- network
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 238000004891 communication Methods 0.000 title claims abstract description 20
- 238000012360 testing method Methods 0.000 claims abstract description 11
- 230000015556 catabolic process Effects 0.000 claims abstract description 6
- 238000006731 degradation reaction Methods 0.000 claims abstract description 6
- 238000005259 measurement Methods 0.000 claims description 92
- 238000010187 selection method Methods 0.000 claims description 2
- 230000008859 change Effects 0.000 description 25
- 230000006870 function Effects 0.000 description 21
- 230000004048 modification Effects 0.000 description 21
- 238000012986 modification Methods 0.000 description 21
- 230000005540 biological transmission Effects 0.000 description 16
- 230000015654 memory Effects 0.000 description 10
- 230000011664 signaling Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000007726 management method Methods 0.000 description 9
- 238000012546 transfer Methods 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 6
- 238000003306 harvesting Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 241000084490 Esenbeckia delta Species 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/30—Monitoring; Testing of propagation channels
- H04B17/382—Monitoring; Testing of propagation channels for resource allocation, admission control or handover
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/30—Monitoring; Testing of propagation channels
- H04B17/309—Measuring or estimating channel quality parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/30—Monitoring; Testing of propagation channels
- H04B17/309—Measuring or estimating channel quality parameters
- H04B17/318—Received signal strength
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04H—BROADCAST COMMUNICATION
- H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
- H04H20/12—Arrangements for observation, testing or troubleshooting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/29—Flow control; Congestion control using a combination of thresholds
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/28—Timers or timing mechanisms used in protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/20—Monitoring; Testing of receivers
- H04B17/24—Monitoring; Testing of receivers with feedback of measurements to the transmitter
Definitions
- the present invention relates to wireless communications, and more particularly, to a method and apparatus for performing multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system.
- MBMS multimedia broadcast multicast service
- MDT drive test
- Universal mobile telecommunications system is a 3rd generation (3G) asynchronous mobile communication system operating in wideband code division multiple access (WCDMA) based on European systems, global system for mobile communications (GSM) and general packet radio services (GPRS).
- WCDMA wideband code division multiple access
- GSM global system for mobile communications
- GPRS general packet radio services
- LTE long-term evolution
- 3GPP 3rd generation partnership project
- the 3GPP LTE is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity.
- the 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.
- the 3GPP LTE can provide a multimedia broadcast multicast service (MBMS) service.
- MBMS is a service which simultaneously transmits data packets to multiple users. If a specific level of users exists in the same cell, the respective users can be allowed to share necessary resources so that the plurality of users can receive the same multimedia data, thereby increasing resource efficiency.
- a multimedia service can be used with a low cost from the perspective of users.
- MDT Minimization of drive tests is a feature introduced in 3GPP LTE rel-10 to allow the harvesting of network coverage and quality information from customer user equipments (UEs) as they move within the coverage of the radio access network (RAN). This provides better quality data, at a lower cost, than that produced by the RAN operator performing drive testing of the RAN using test UEs.
- MBMS-MDT The concept of MDT may be applied to MBMS, which may be referred to as MBMS-MDT.
- MBMS-MDT For a user equipment (UE) which is interested to receive MBMS or is receiving MBMS, MBMS-MDT may be configured and performed.
- the purpose of MBMS-MDT is allowing for the network operator harvesting of network coverage and quality information from UEs related to MBMS, which means that UEs can report areas in which MBMS cannot be received without enough quality.
- MBMS-MDT configuration may be provided by a network.
- the UE may stop performing MBMS-MDT. This is against the purpose of performing MBMS-MDT. Accordingly, a method for performing MBMS-MDT even though the UE is in the coverage hole of MBMS may be required.
- the present invention provides a method and apparatus for performing multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system.
- MBMS multimedia broadcast multicast service
- MDT drive test
- the present invention provides a method for performing MBMS-MDT by using a MBMS-MDT timer when a specific condition, which relates to degradation of quality of received MBMS, is met.
- a method for performing, by a user equipment (UE), multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system includes receiving, by the UE, a MBMS-MDT timer configuration from a network, starting, by the UE, a MBMS-MDT timer based on the received MBMS-MDT timer configuration when a specific condition, which relates to degradation of quality of MBMS, is met, and while the MBMS-MDT timer is running, performing, by the UE, MBMS-MDT.
- a user equipment configured to perform multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system.
- the UE includes a radio frequency (RF) unit configured to transmit or receive a radio signal, and a processor coupled to the RF unit, and configured to receive a MBMS-MDT timer configuration from a network, start a MBMS-MDT timer based on the received MBMS-MDT timer configuration when a specific condition, which relates to quality of MBMS, is met, and while the MBMS-MDT timer is running, perform MBMS-MDT.
- RF radio frequency
- MBMS-MDT can be performed even though MBMS cannot be received.
- FIG. 1 shows LTE system architecture.
- FIG. 2 shows a block diagram of architecture of a typical E-UTRAN and a typical EPC.
- FIG. 3 shows a block diagram of a user plane protocol stack of an LTE system.
- FIG. 4 shows a block diagram of a control plane protocol stack of an LTE system.
- FIG. 5 shows an example of a physical channel structure.
- FIG. 6 shows a logged measurement configuration procedure
- FIG. 7 shows MBMS definitions.
- FIG. 8 shows change of MCCH information.
- FIG. 9 shows a MCCH information acquisition procedure.
- FIG. 10 shows an example of a method for performing MBMS-MDT according to an embodiment of the present invention.
- FIG. 11 shows another example of a method for performing MBMS-MDT according to an embodiment of the present invention.
- FIG. 12 shows a wireless communication system to implement an embodiment of the present invention.
- CDMA code division multiple access
- FDMA frequency division multiple access
- TDMA time division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single carrier frequency division multiple access
- the CDMA can be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA-2000.
- UTRA universal terrestrial radio access
- the TDMA can be implemented with a radio technology such as global system for mobile communications (GSM)/general packet ratio service (GPRS)/enhanced data rate for GSM evolution (EDGE).
- GSM global system for mobile communications
- GPRS general packet ratio service
- EDGE enhanced data rate for GSM evolution
- the OFDMA can be implemented with a radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), etc.
- IEEE 802.16m is an evolution of IEEE 802.16e, and provides backward compatibility with an IEEE 802.16-based system.
- the UTRA is a part of a universal mobile telecommunication system (UMTS).
- 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of an evolved UMTS (E-UMTS) using the E-UTRA.
- 3GPP LTE uses the OFDMA in downlink and uses the SC-FDMA in uplink.
- LTE-advance (LTE-A) is an evolution of the 3GPP LTE.
- FIG. 1 shows LTE system architecture.
- the communication network is widely deployed to provide a variety of communication services such as voice over internet protocol (VoIP) through IMS and packet data.
- VoIP voice over internet protocol
- the LTE system architecture includes one or more user equipment (UE; 10), an evolved-UMTS terrestrial radio access network (E-UTRAN) and an evolved packet core (EPC).
- the UE 10 refers to a communication equipment carried by a user.
- the UE 10 may be fixed or mobile, and may be referred to as another terminology, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a wireless device, etc.
- MS mobile station
- UT user terminal
- SS subscriber station
- wireless device etc.
- the E-UTRAN includes one or more evolved node-B (eNB) 20, and a plurality of UEs may be located in one cell.
- the eNB 20 provides an end point of a control plane and a user plane to the UE 10.
- the eNB 20 is generally a fixed station that communicates with the UE 10 and may be referred to as another terminology, such as a base station (BS), an access point, etc.
- BS base station
- One eNB 20 may be deployed per cell.
- a downlink (DL) denotes communication from the eNB 20 to the UE
- an uplink (UL) denotes communication from the UE 10 to the eNB 20.
- a transmitter may be a part of the eNB 20, and a receiver may be a part of the UE 10.
- the transmitter may be a part of the UE 10, and the receiver may be a part of the eNB 20.
- the EPC includes a mobility management entity (MME) and a system architecture evolution (SAE) gateway (S-GW).
- MME mobility management entity
- SAE system architecture evolution gateway
- the MME/S-GW 30 may be positioned at the end of the network and connected to an external network.
- MME/S-GW 30 will be referred to herein simply as a “gateway,” but it is understood that this entity includes both the MME and S-GW.
- the MME provides various functions including non-access stratum (NAS) signaling to eNBs 20, NAS signaling security, access stratum (AS) security control, inter core network (CN) node signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmission), tracking area list management (for UE in idle and active mode), packet data network (PDN) gateway (P-GW) and S-GW selection, MME selection for handovers with MME change, serving GPRS support node (SGSN) selection for handovers to 2G or 3G 3GPP access networks, roaming, authentication, bearer management functions including dedicated bearer establishment, support for public warning system (PWS) (which includes earthquake and tsunami warning system (ETWS) and commercial mobile alert system (CMAS)) message transmission.
- PWS public warning system
- ETWS earthquake and tsunami warning system
- CMAS commercial mobile alert system
- the S-GW host provides assorted functions including per-user based packet filtering (by e.g., deep packet inspection), lawful interception, UE Internet protocol (IP) address allocation, transport level packet marking in the DL, UL and DL service level charging, gating and rate enforcement, DL rate enforcement based on access point name aggregate maximum bit rate (APN-AMBR).
- per-user based packet filtering by e.g., deep packet inspection
- IP Internet protocol
- transport level packet marking in the DL transport level packet marking in the DL
- UL and DL service level charging e.g., gating and rate enforcement
- DL rate enforcement based on access point name aggregate maximum bit rate (APN-AMBR).
- APN-AMBR access point name aggregate maximum bit rate
- Interfaces for transmitting user traffic or control traffic may be used.
- the UE 10 is connected to the eNB 20 via a Uu interface.
- the eNBs 20 are connected to each other via an X2 interface.
- Neighboring eNBs may have a meshed network structure that has the X2 interface.
- a plurality of nodes may be connected between the eNB 20 and the gateway 30 via an S1 interface.
- FIG. 2 shows a block diagram of architecture of a typical E-UTRAN and a typical EPC.
- the eNB 20 may perform functions of selection for gateway 30, routing toward the gateway 30 during a radio resource control (RRC) activation, scheduling and transmitting of paging messages, scheduling and transmitting of broadcast channel (BCH) information, dynamic allocation of resources to the UEs 10 in both UL and DL, configuration and provisioning of eNB measurements, radio bearer control, radio admission control (RAC), and connection mobility control in LTE_ACTIVE state.
- gateway 30 may perform functions of paging origination, LTE_IDLE state management, ciphering of the user plane, SAE bearer control, and ciphering and integrity protection of NAS signaling.
- FIG. 3 shows a block diagram of a user plane protocol stack of an LTE system.
- FIG. 4 shows a block diagram of a control plane protocol stack of an LTE system.
- Layers of a radio interface protocol between the UE and the E-UTRAN may be classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on the lower three layers of the open system interconnection (OSI) model that is well-known in the communication system.
- OSI open system interconnection
- a physical (PHY) layer belongs to the L1.
- the PHY layer provides a higher layer with an information transfer service through a physical channel.
- the PHY layer is connected to a medium access control (MAC) layer, which is a higher layer of the PHY layer, through a transport channel.
- MAC medium access control
- a physical channel is mapped to the transport channel. Data between the MAC layer and the PHY layer is transferred through the transport channel.
- PHY physical
- a MAC layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer belong to the L2.
- the MAC layer provides services to the RLC layer, which is a higher layer of the MAC layer, via a logical channel.
- the MAC layer provides data transfer services on logical channels.
- the RLC layer supports the transmission of data with reliability. Meanwhile, a function of the RLC layer may be implemented with a functional block inside the MAC layer. In this case, the RLC layer may not exist.
- the PDCP layer provides a function of header compression function that reduces unnecessary control information such that data being transmitted by employing IP packets, such as IPv4 or IPv6, can be efficiently transmitted over a radio interface that has a relatively small bandwidth.
- a radio resource control (RRC) layer belongs to the L3.
- the RLC layer is located at the lowest portion of the L3, and is only defined in the control plane.
- the RRC layer controls logical channels, transport channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers (RBs).
- the RB signifies a service provided the L2 for data transmission between the UE and E-UTRAN.
- the RLC and MAC layers may perform functions such as scheduling, automatic repeat request (ARQ), and hybrid ARQ (HARQ).
- the PDCP layer may perform the user plane functions such as header compression, integrity protection, and ciphering.
- the RLC and MAC layers may perform the same functions for the control plane.
- the RRC layer (terminated in the eNB on the network side) may perform functions such as broadcasting, paging, RRC connection management, RB control, mobility functions, and UE measurement reporting and controlling.
- the NAS control protocol (terminated in the MME of gateway on the network side) may perform functions such as a SAE bearer management, authentication, LTE_IDLE mobility handling, paging origination in LTE_IDLE, and security control for the signaling between the gateway and UE.
- FIG. 5 shows an example of a physical channel structure.
- a physical channel transfers signaling and data between PHY layer of the UE and eNB with a radio resource.
- a physical channel consists of a plurality of subframes in time domain and a plurality of subcarriers in frequency domain.
- One subframe which is 1 ms, consists of a plurality of symbols in the time domain.
- Specific symbol(s) of the subframe such as the first symbol of the subframe, may be used for a physical downlink control channel (PDCCH).
- the PDCCH carries dynamic allocated resources, such as a physical resource block (PRB) and modulation and coding scheme (MCS).
- PRB physical resource block
- MCS modulation and coding scheme
- a DL transport channel includes a broadcast channel (BCH) used for transmitting system information, a paging channel (PCH) used for paging a UE, a downlink shared channel (DL-SCH) used for transmitting user traffic or control signals, a multicast channel (MCH) used for multicast or broadcast service transmission.
- BCH broadcast channel
- PCH paging channel
- DL-SCH downlink shared channel
- MCH multicast channel
- the DL-SCH supports HARQ, dynamic link adaptation by varying the modulation, coding and transmit power, and both dynamic and semi-static resource allocation.
- the DL-SCH also may enable broadcast in the entire cell and the use of beamforming.
- a UL transport channel includes a random access channel (RACH) normally used for initial access to a cell, a uplink shared channel (UL-SCH) for transmitting user traffic or control signals, etc.
- RACH random access channel
- UL-SCH uplink shared channel
- the UL-SCH supports HARQ and dynamic link adaptation by varying the transmit power and potentially modulation and coding.
- the UL-SCH also may enable the use of beamforming.
- the logical channels are classified into control channels for transferring control plane information and traffic channels for transferring user plane information, according to a type of transmitted information. That is, a set of logical channel types is defined for different data transfer services offered by the MAC layer.
- the control channels are used for transfer of control plane information only.
- the control channels provided by the MAC layer include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH) and a dedicated control channel (DCCH).
- the BCCH is a downlink channel for broadcasting system control information.
- the PCCH is a downlink channel that transfers paging information and is used when the network does not know the location cell of a UE.
- the CCCH is used by UEs having no RRC connection with the network.
- the MCCH is a point-to-multipoint downlink channel used for transmitting multimedia broadcast multicast services (MBMS) control information from the network to a UE.
- the DCCH is a point-to-point bi-directional channel used by UEs having an RRC connection that transmits dedicated control information between a UE and the network.
- Traffic channels are used for the transfer of user plane information only.
- the traffic channels provided by the MAC layer include a dedicated traffic channel (DTCH) and a multicast traffic channel (MTCH).
- DTCH dedicated traffic channel
- MTCH multicast traffic channel
- the DTCH is a point-to-point channel, dedicated to one UE for the transfer of user information and can exist in both uplink and downlink.
- the MTCH is a point-to-multipoint downlink channel for transmitting traffic data from the network to the UE.
- Uplink connections between logical channels and transport channels include the DCCH that can be mapped to the UL-SCH, the DTCH that can be mapped to the UL-SCH and the CCCH that can be mapped to the UL-SCH.
- Downlink connections between logical channels and transport channels include the BCCH that can be mapped to the BCH or DL-SCH, the PCCH that can be mapped to the PCH, the DCCH that can be mapped to the DL-SCH, and the DTCH that can be mapped to the DL-SCH, the MCCH that can be mapped to the MCH, and the MTCH that can be mapped to the MCH.
- An RRC state indicates whether an RRC layer of the UE is logically connected to an RRC layer of the E-UTRAN.
- the RRC state may be divided into two different states such as an RRC idle state (RRC_IDLE) and an RRC connected state (RRC_CONNECTED).
- RRC_IDLE the UE may receive broadcasts of system information and paging information while the UE specifies a discontinuous reception (DRX) configured by NAS, and the UE has been allocated an identification (ID) which uniquely identifies the UE in a tracking area and may perform public land mobile network (PLMN) selection and cell re-selection.
- ID identification
- PLMN public land mobile network
- the UE In RRC_CONNECTED, the UE has an E-UTRAN RRC connection and a context in the E-UTRAN, such that transmitting and/or receiving data to/from the eNB becomes possible. Also, the UE can report channel quality information and feedback information to the eNB.
- the E-UTRAN knows the cell to which the UE belongs. Therefore, the network can transmit and/or receive data to/from UE, the network can control mobility (handover and inter-radio access technologies (RAT) cell change order to GSM EDGE radio access network (GERAN) with network assisted cell change (NACC)) of the UE, and the network can perform cell measurements for a neighboring cell.
- RAT inter-radio access technologies
- GERAN GSM EDGE radio access network
- NACC network assisted cell change
- the UE specifies the paging DRX cycle. Specifically, the UE monitors a paging signal at a specific paging occasion of every UE specific paging DRX cycle.
- the paging occasion is a time interval during which a paging signal is transmitted.
- the UE has its own paging occasion.
- a paging message is transmitted over all cells belonging to the same tracking area. If the UE moves from one tracking area (TA) to another TA, the UE will send a tracking area update (TAU) message to the network to update its location.
- TAU tracking area update
- MDT Minimization of drive tests
- 3GPP TS 37.320 V11.3.0 2013-03
- Section 5.6.6 and 5.6.8 of 3GPP TS 36.331 V11.5.0 2013-09
- the general principles and requirements guiding the definition of functions for MDT are the following.
- MDT mode There are two modes for the MDT measurements, which are logged MDT and immediate MDT.
- the logged MDT is MDT functionality involving measurement logging by the UE in IDLE mode, CELL_PCH and URA_PCH states (when the UE is in UTRA) for reporting to eNB/radio network controller (RNC) at a later point in time.
- the immediate MDT is MDT functionality involving measurements performed by the UE in CONNECTED state and reporting of the measurements to eNB/RNC available at the time of reporting condition as well as measurements by the network for MDT purposes.
- measurement collection not specified as either immediate or logged MDT, such as accessibility measurements.
- UE measurement configuration It is possible to configure MDT measurements for the UE logging purpose independently from the network configurations for normal radio resource management (RRM) purposes. However, in most cases, the availability of measurement results is conditionally dependent on the UE RRM configuration.
- RRM radio resource management
- UE measurement collection and reporting UE MDT measurement logs consist of multiple events and measurements taken over time. The time interval for measurement collection and reporting is decoupled in order to limit the impact on the UE battery consumption and network signaling load.
- Geographical scope of measurement logging It is possible to configure the geographical area where the defined set of measurements shall be collected.
- the measurements shall be linked to available location information and/or other information or measurements that can be used to derive location information.
- Time information The measurements in measurement logs shall be linked to a time stamp.
- the network may use UE capabilities to select terminals for MDT measurements.
- the subscriber/cell trace functionality is reused and extended to support MDT. If the MDT is initiated toward to a specific UE (e.g., based on international mobile subscriber identity (IMSI), international mobile station equipment identity (IMEI) software version (SV), etc.), the signalling based trace procedure is used, otherwise the management based trace procedure (or cell traffic trace procedure) is used.
- IMSI international mobile subscriber identity
- IMEI international mobile station equipment identity
- SV cell traffic trace procedure
- the UE measurement logging mechanism is an optional feature. In order to limit the impact on UE power consumption and processing, the UE measurement logging should as much as possible rely on the measurements that are available in the UE according to radio resource management enforced by the access network.
- Location information The availability of location information is subject to UE capability and/or UE implementation. Solutions requiring location information shall take into account power consumption of the UE due to the need to run its positioning components.
- Logged MDT procedure is described. Support of logged MDT complies with the principles for idle mode measurements in the UE. Furthermore, measurement logging is differentiated based on UE states in idle mode, i.e. camped normally, any cell selection or camped on any cell. The UE shall perform measurement logging in "camped normally" state. In “any cell selection” and “camped on any cell” state the UE is not required to perform MDT measurement logging (including time and location information). For logged MDT, the configuration, measurement collection and reporting of the concerning measurement will always be done in cells of the same RAT type.
- FIG. 6 shows a logged measurement configuration procedure.
- the purpose of the logged measurement procedure is to configure the UE to perform logging of measurement results while in RRC_IDLE.
- the logged measurement procedure applies to logged measurements capable UEs that are in RRC_CONNECTED.
- the E-UTRAN initiates the logged measurement configuration procedure to the UE in RRC_CONNECTED by sending the LoggedMeasurementConfiguration message, which is used to transfer configuration parameters for logged MDT.
- This is a unidirectional RRC signaling procedure.
- a release operation for logged measurement configuration in the UE is realized only by configuration replacement when the configuration is overwritten or by configuration clearance in case a duration timer stopping or expiration condition is met.
- the UE Upon receiving the LoggedMeasurementConfiguration message, the UE shall:
- plmn-IdentityList in VarLogMeasReport to include the registered PLMN (RPLMN) as well as the PLMNs included in plmn-IdentityList ;
- the UE Upon expiry of T330, the UE shall:
- the UE is allowed to discard stored logged measurements, i.e. to release VarLogMeasReport 48 hours after T330 expiry.
- Release of logged measurement configuration procedure may release the logged measurement configuration as well as the logged measurement information.
- the UE shall initiate the release of logged measurement configuration procedure upon receiving a logged measurement configuration in another RAT.
- the UE shall also initiate the procedure upon power off or detach.
- the UE shall:
- stop timer T330 if running
- Measurements logging procedure specifies the logging of available measurements by a UE in RRC_IDLE that has a logged measurement configuration. While T330 is running, the UE shall:
- VarLogMeasReport when adding a logged measurement entry in VarLogMeasReport , include the fields in accordance with the following:
- 3> set the servCellIdentity to indicate global cell identity of the cell the UE is camping on;
- 3> if available, set the measResultNeighCells , in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements that became available during the last logging interval for at most the following number of neighbouring cells; 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies (GERAN) per RAT;
- GERAN set of frequencies
- MBMS is described. It may be referred to Section 15 of 3GPP TS 36.300 V11.7.0 (2013-09) and Section 5.8 of 3GPP TS 36.331 V11.5.0 (2013-09).
- FIG. 7 shows MBMS definitions.
- MBMS the following definitions may be introduced.
- MBSFN Multicast-broadcast single-frequency network
- An MBSFN transmission from multiple cells within the MBSFN area is seen as a single transmission by a UE.
- an MBSFN area consists of a group of cells within an MBSFN synchronization area of a network, which are coordinated to achieve an MBSFN transmission. Except for the MBSFN area reserved cells, all cells within an MBSFN area contribute to the MBSFN transmission and advertise its availability. The UE may only need to consider a subset of the MBSFN areas that are configured, i.e., when it knows which MBSFN area applies for the service(s) it is interested to receive.
- - MBSFN area reserved cell This is a cell within a MBSFN area which does not contribute to the MBSFN transmission.
- the cell may be allowed to transmit for other services but at restricted power on the resource allocated for the MBSFN transmission.
- Each synchronization protocol data unit contains a time stamp which indicates the start time of the synchronization sequence.
- each synchronization sequence has the same duration which is configured in the broadcast and multicast service center (BM-SC) and the multi-cell/multicast coordination entity (MCE).
- BM-SC broadcast and multicast service center
- MCE multi-cell/multicast coordination entity
- the synchronization period provides the time reference for the indication of the start time of each synchronization sequence.
- the time stamp which is provided in each SYNC PDU is a relative value which refers to the start time of the synchronization period.
- the duration of the synchronization period is configurable.
- One MBSFN area is associated with one MCCH and one MCCH corresponds to one MBSFN area;
- the MCCH is sent on MCH
- - MCCH consists of a single MBSFN area configuration RRC message which lists all the MBMS services with ongoing sessions and an optional MBMS counting request message;
- - MCCH is transmitted by all cells within an MBSFN area, except the MBSFN area reserved cells;
- - MCCH is transmitted by RRC every MCCH repetition period
- a notification mechanism is used to announce changes of MCCH due to either session start or the presence of an MBMS counting request message:
- the notification is sent periodically throughout the modification period preceding the change of MCCH, in MBSFN subframes configured for notification.
- the downlink control information (DCI) format 1C with MBMS radio network temporary identity (M-RNTI) is used for notification and includes an 8-bit bitmap to indicate the one or more MBSFN area(s) in which the MCCH change(s).
- the UE monitors more than one notification subframe per modification period. When the UE receives a notification, it acquires the MCCH at the next modification period boundary;
- the UE detects changes to MCCH which are not announced by the notification mechanism by MCCH monitoring at the modification period.
- the control information relevant only for UEs supporting MBMS is separated as much as possible from unicast control information.
- Most of the MBMS control rmation is provided on a logical channel specific for MBMS common control rmation: the MCCH.
- E-UTRA employs one MCCH logical channel per MBSFN area.
- the UE acquires the MBMS control rmation from the MCCHs that are configured to identify if services it is interested to receive are ongoing.
- An MBMS capable UE may be only required to support reception of a single MBMS service at a time.
- the MCCH carries the MBSFNAreaConfiguration message, which indicates the MBMS sessions that are ongoing as well as the (corresponding) radio resource configuration.
- the MCCH may also carry the MBMSCountingRequest message, when E-UTRAN wishes to count the number of UEs in RRC_CONNECTED that are receiving or interested to receive one or more specific MBMS services.
- a limited amount of MBMS control rmation is provided on the BCCH. This primarily concerns the rmation needed to acquire the MCCH(s). This rmation is carried by means of a single MBMS specific SystemInformationBlock : SystemInformationBlockType13 .
- An MBSFN area is identified solely by the mbsfn-AreaId in SystemInformationBlockType13 .
- the UE considers that the MBSFN area is continuous when the source cell and the target cell broadcast the same value in the mbsfn-AreaId .
- the MCCH rmation is transmitted periodically, using a configurable repetition period. Scheduling rmation is not provided for MCCH, i.e. both the time domain scheduling as well as the lower layer configuration are semi-statically configured, as defined within SystemInformationBlockType13 .
- E-UTRAN For MBMS user data, which is carried by the MTCH logical channel, E-UTRAN periodically provides MSI at lower layers (MAC).
- MSI MSI at lower layers
- This MCH rmation only concerns the time domain scheduling, i.e. the frequency domain scheduling and the lower layer configuration are semi-statically configured.
- the periodicity of the MSI is configurable and defined by the MCH scheduling period.
- the same MCCH rmation may be transmitted a number of times, as defined by its scheduling (which is based on a repetition period).
- SFN system frame number
- the modification period is configured by means of SystemInformationBlockType13 .
- FIG. 8 shows change of MCCH information.
- the network changes (some of) the MCCH rmation, it notifies the UEs about the change during a first modification period. In the next modification period, the network transmits the updated MCCH rmation.
- different colors indicate different MCCH rmation.
- a UE interested to receive MBMS services acquires the new MCCH rmation immediately from the start of the next modification period. The UE applies the previously acquired MCCH rmation until the UE acquires the new MCCH rmation.
- the M-RNTI, on PDCCH is used to rm UEs in RRC_IDLE and UEs in RRC_CONNECTED about an MCCH rmation change.
- the notification on PDCCH indicates which of the MCCHs will change, which is done by means of an 8-bit bitmap. Within this bitmap, the bit at the position indicated by the field notificationIndicator is used to indicate changes for that MBSFN area: if the bit is set to "1", the corresponding MCCH will change. No further details are provided, e.g. regarding which MCCH rmation will change.
- the MCCH rmation change notification is used to rm the UE about a change of MCCH rmation upon session start or about the start of MBMS counting.
- the MCCH rmation change notifications on PDCCH are transmitted periodically and are carried on MBSFN subframes only.
- These MCCH rmation change notification occasions are common for all MCCHs that are configured, and configurable by parameters included in SystemInformationBlockType13: a repetition coefficient, a radio frame offset and a subframe index. These common notification occasions are based on the MCCH with the shortest modification period.
- the E-UTRAN may modify the MBMS configuration rmation provided on MCCH at the same time as updating the MBMS configuration rmation carried on BCCH, i.e. at a coinciding BCCH and MCCH modification period.
- a UE interested to receive one or more MBMS services should acquire the MCCH, unless it knows that the services it is interested in are not provided by the corresponding MBSFN area.
- a UE that is receiving an MBMS service shall acquire the MCCH rmation from the start of each modification period.
- a UE that is not receiving an MBMS service, as well as UEs that are receiving an MBMS service but potentially interested to receive other services not started yet in another MBSFN area shall verify that the stored MCCH rmation remains valid by attempting to find the MCCH rmation change notification at least notificationRepetitionCoeff times during the modification period of the applicable MCCH(s), if no MCCH rmation change notification is received.
- the UE may only need to monitor change notifications for a subset of the MCCHs that are configured, referred to as the 'applicable MCCH(s)' in the above.
- the UE applies the MCCH information acquisition procedure to acquire the MBMS control information that is broadcasted by the E-UTRAN.
- the procedure applies to MBMS capable UEs that are in RRC_IDLE or in RRC_CONNECTED.
- a UE interested to receive MBMS services shall apply the MCCH rmation acquisition procedure upon entering the corresponding MBSFN area (e.g. upon power on, following UE mobility) and upon receiving a notification that the MCCH rmation has changed.
- a UE that is receiving an MBMS service shall apply the MCCH rmation acquisition procedure to acquire the MCCH, which corresponds with the service that is being received, at the start of each modification period.
- the MCCH rmation acquisition procedure overwrites any stored MCCH rmation, i.e. delta configuration is not applicable for MCCH rmation and the UE discontinues using a field if it is absent in MCCH rmation unless explicitly specified otherwise.
- FIG. 9 shows a MCCH information acquisition procedure.
- An MBMS capable UE shall:
- step S90 start acquiring the MBSFNAreaConfiguration message (in step S90) and the MBMSCountingRequest message if present (in step S91), from the beginning of the modification period following the one in which the change notification was received;
- step S90 acquire the MBSFNAreaConfiguration message (in step S90) and the MBMSCountingRequest message if present (in step S91), at the next repetition period;
- step S90 start acquiring the MBSFNAreaConfiguration message (in step S90) and the MBMSCountingRequest message if present (in step S91), that both concern the MBSFN area of the service that is being received, from the beginning of each modification period;
- Logged MDT procedure may be performed for MBMS.
- the logged MDT procedure for MBMS may be referred to as MBMS-MDT.
- the logged measurement configuration procedure for described in FIG. 6 may be performed in order to log of measurement results for MBSFN in both RRC_IDLE and RRC_CONNECTED.
- the measurements logging procedure specifies the logging of available measurements by a UE in RRC_IDLE that has a logged measurement configuration and the logging of available measurements by a UE in both RRC_IDLE and RRC_CONNECTED if targetMBSFN-AreaList is included in VarLogMeasConfig .
- the UE may perform MBSFN measurements, and perform logging at regular time intervals , but only for those intervals for which MBSFN measurement results are available.
- the UE performs MBMS-MDT for an MBSFN area only when the UE is receiving an MBMS from the MBSFN area.
- the quality of MBMS may be degraded.
- the UE stops receiving MBMS or tries to receive corresponding service via unicast bearer, and therefore, also stops performing MBMS-MDT for MBSFN area corresponding to the coverage hole. This is against the purpose of MBMS-MDT. Therefore, the network operator cannot obtain sufficient results of coverage hole.
- the UE needs to keep performing MBMS-MDT even though the UE is in coverage hole of MBMS.
- a method for performing MBMS-MDT by using a MBMS-MDT timer is described.
- the UE keeps performing MBMS-MDT while the MBMS-MDT timer is running when a specific condition is met.
- the MBMS-MDT timer is a newly defined timer for MBMS-MDT, and is a different from the timer used for conventional logged MDT procedure.
- the UE keeps performing MBMS-MDT for a MBSFN area while the corresponding MBMS-MDT timer is running.
- the UE stops performing MBMS-MDT for the MBSFN area. Accordingly, the network operator or service operator can harvest measurement results of MBSFN areas in which quality of MBMS is not good enough, which is actually needed.
- FIG. 10 shows an example of a method for performing MBMS-MDT according to an embodiment of the present invention.
- the UE receives a MBMS-MDT timer configuration from a network.
- the MBMS-MDT timer configuration may configure start/expiry/early termination of the MBMS-MDT timer.
- the MBMS-MDT timer may be configured per MBSFN area.
- the MBMS-MDT timer configuration may be received via the MBMS-MDT configuration.
- the MBMS-MDT timer configuration may be received via broadcast signaling, i.e. system information block (SIB) type 13 along with MBSFN area identities.
- SIB system information block
- the MBMS-MDT timer may be predefined.
- step S110 the UE starts the MBMS-MDT timer based on the received MBMS-MDT timer configuration when a specific condition, which relates to degradation of quality of MBMS, is met.
- the UE starts the MBMS-MDT timer when quality of receiving MBMS is not good enough. More specifically, the UE starts the MBMS-MDT timer when at least one of following conditions is met.
- RSRP reference signal received power
- BLER block error rate
- the RSRP/RSRQ/BLER thresholds may be configured by the network. Or, the RSRP/RSRQ/BLER thresholds may be configured by UE implementation.
- step S120 while the MBMS-MDT timer is running, the UE performs MBMS-MDT based on MBMS-MDT configuration.
- Performing of the MBMS-MDT may include performing MBMS measurements, logging measurement results, and reporting logged results.
- the MBMS measurements to be performed by the UE for the MBMS-MDT may include MBSFN RSRP/RSRQ per MBSFN area, MCH BLER per MCS, per MCH, and per MBSFN area, and/or the amount of received RLC SDUs for a certain period of time.
- the UE may perform sparse MBMS measurements and logging according to the sparse MBMS measurement configuration while the MBMS-MDT timer is running.
- the sparse MBMS measurement configuration may include a sparse interval and a sparse duration.
- the sparse interval may be longer than normal MBMS measurement/logging interval, and the sparse MDT duration may be shorter than normal MBMS measurement/logging duration.
- the sparse MBMS measurement may be configured along with the MBMS-MDT timer.
- the sparse MBMS measurement may be configured per MBMS-MDT timer or per MBSFN area. Or, only one sparse MBMS measurement may be configured for the UE, then the UE may use the one sparse MBMS measurement configuration for all MBSFN area.
- the MBMS-MDT timer may be terminated early before expiry.
- the UE may terminate the MBMS-MDT timer which is running when the UE moves to another frequency by performing handover or cell re-selection procedure. If the UE can measure the MBSFN area even though it moves to another frequency, e.g. carrier aggregation (CA) capable UE, the UE may not terminate the MBMS-MDT timer.
- CA carrier aggregation
- FIG. 11 shows another example of a method for performing MBMS-MDT according to an embodiment of the present invention.
- step S200 the UE is receiving MBMS service #1 and #2 from MBSFN area #1 and #2, respectively.
- the UE is configured to perform MBMS-MDT by receiving the MBMS-MDT configuration form the network.
- the MBMS-MDT configuration includes the MBMS-MDT timer configuration.
- MBMS-MDT timers are set per MBSFN area, i.e. MBMS-MDT timer #1 for MBSFN area #1 and MBMS-MDT timer #2 for MBSFN area #2, respectively, by the MBMSMDT timer configuration.
- the MBMS-MDT configuration includes the sparse MBMS measurements configuration, which includes the sparse interval and sparse duration.
- step S220 the UE starts to perform MBMS-MDT for MBSFN area #1 and #2 based on the received MBMS-MDT configuration.
- step S230 the UE enters a coverage hole of MBSFN area #1.
- the UE detects that the service quality of the MBMS service #1 is degraded rapidly.
- the UE stops receiving the MBMS service #1 and starts the MBMS-MDT timer #1. Accordingly, the UE can keep performing MBMS-MDT for MBSFN area #1.
- the UE may perform MBMS-MDT according to the sparse MBMS measurements configuration for MBSFN area #1 while performing normal MBMS-MDT for MBSFN area #2.
- step S240 the MBMS-MDT timer #1 expires.
- the UE stops performing MBMS-MDT for MBSFN area #1.
- step S250 the UE enters a coverage hole of MBSFN area #2.
- the UE detects that the service quality of the MBMS service #2 is degraded rapidly, e.g. by performing RSRQ measurement.
- the UE stops receiving the MBMS service #2 and starts the MBMS-MDT timer #2. Accordingly, the UE can keep performing MBMS-MDT for MBSFN area #2.
- the UE may perform MBMS-MDT for MBSFN area #2 according to the sparse MBMS measurements configuration.
- step S260 while the MBMS-MDT timer is running, i.e. before the MBMS-MDT timer #2 expires, the UE receives a handover command message and downlink frequency of a target cell which is different from that of the current serving cell.
- step S270 since early termination condition is met, the UE terminates the MBMS-MDT timer #2 and stops performing MBMS-MDT for MBSFN area #2.
- FIG. 12 shows a wireless communication system to implement an embodiment of the present invention.
- An eNB 800 may include a processor 810, a memory 820 and a radio frequency (RF) unit 830.
- the processor 810 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of the radio interface protocol may be implemented in the processor 810.
- the memory 820 is operatively coupled with the processor 810 and stores a variety of information to operate the processor 810.
- the RF unit 830 is operatively coupled with the processor 810, and transmits and/or receives a radio signal.
- a UE 900 may include a processor 910, a memory 920 and a RF unit 930.
- the processor 910 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of the radio interface protocol may be implemented in the processor 910.
- the memory 920 is operatively coupled with the processor 910 and stores a variety of information to operate the processor 910.
- the RF unit 930 is operatively coupled with the processor 910, and transmits and/or receives a radio signal.
- the processors 810, 910 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device.
- the memories 820, 920 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and/or other storage device.
- the RF units 830, 930 may include baseband circuitry to process radio frequency signals.
- the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein.
- the modules can be stored in memories 820, 920 and executed by processors 810, 910.
- the memories 820, 920 can be implemented within the processors 810, 910 or external to the processors 810, 910 in which case those can be communicatively coupled to the processors 810, 910 via various means as is known in the art.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Physics & Mathematics (AREA)
- Electromagnetism (AREA)
- Quality & Reliability (AREA)
- Multimedia (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A method and apparatus for performing multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system is provided. A user equipment (UE) receives a MBMS-MDT timer configuration from a network. A MBMS-MDT timer is newly defined for the MBMS-MDT. The UE starts the MBMS-MDT timer based on the received MBMS-MDT timer configuration when a specific condition, which relates to degradation of quality of MBMS, is met, and while the MBMS-MDT timer is running, the UE performs the MBMS-MDT.
Description
The present invention relates to wireless communications, and more particularly, to a method and apparatus for performing multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system.
Universal mobile telecommunications system (UMTS) is a 3rd generation (3G) asynchronous mobile communication system operating in wideband code division multiple access (WCDMA) based on European systems, global system for mobile communications (GSM) and general packet radio services (GPRS). A long-term evolution (LTE) of UMTS is under discussion by the 3rd generation partnership project (3GPP) that standardized UMTS.
The 3GPP LTE is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.
The 3GPP LTE can provide a multimedia broadcast multicast service (MBMS) service. The MBMS is a service which simultaneously transmits data packets to multiple users. If a specific level of users exists in the same cell, the respective users can be allowed to share necessary resources so that the plurality of users can receive the same multimedia data, thereby increasing resource efficiency. In addition, a multimedia service can be used with a low cost from the perspective of users.
Minimization of drive tests (MDT) is a feature introduced in 3GPP LTE rel-10 to allow the harvesting of network coverage and quality information from customer user equipments (UEs) as they move within the coverage of the radio access network (RAN). This provides better quality data, at a lower cost, than that produced by the RAN operator performing drive testing of the RAN using test UEs.
The concept of MDT may be applied to MBMS, which may be referred to as MBMS-MDT. For a user equipment (UE) which is interested to receive MBMS or is receiving MBMS, MBMS-MDT may be configured and performed. The purpose of MBMS-MDT is allowing for the network operator harvesting of network coverage and quality information from UEs related to MBMS, which means that UEs can report areas in which MBMS cannot be received without enough quality. For configuration of MBMS-MDT, MBMS-MDT configuration may be provided by a network.
If the UE moves to a coverage hole in which MBMS cannot be received without enough quality, the UE may stop performing MBMS-MDT. This is against the purpose of performing MBMS-MDT. Accordingly, a method for performing MBMS-MDT even though the UE is in the coverage hole of MBMS may be required.
The present invention provides a method and apparatus for performing multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system. The present invention provides a method for performing MBMS-MDT by using a MBMS-MDT timer when a specific condition, which relates to degradation of quality of received MBMS, is met.
In an aspect, a method for performing, by a user equipment (UE), multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system is provided. The method includes receiving, by the UE, a MBMS-MDT timer configuration from a network, starting, by the UE, a MBMS-MDT timer based on the received MBMS-MDT timer configuration when a specific condition, which relates to degradation of quality of MBMS, is met, and while the MBMS-MDT timer is running, performing, by the UE, MBMS-MDT.
In another aspect, a user equipment (UE) configured to perform multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system is provided. The UE includes a radio frequency (RF) unit configured to transmit or receive a radio signal, and a processor coupled to the RF unit, and configured to receive a MBMS-MDT timer configuration from a network, start a MBMS-MDT timer based on the received MBMS-MDT timer configuration when a specific condition, which relates to quality of MBMS, is met, and while the MBMS-MDT timer is running, perform MBMS-MDT.
MBMS-MDT can be performed even though MBMS cannot be received.
FIG. 1 shows LTE system architecture.
FIG. 2 shows a block diagram of architecture of a typical E-UTRAN and a typical EPC.
FIG. 3 shows a block diagram of a user plane protocol stack of an LTE system.
FIG. 4 shows a block diagram of a control plane protocol stack of an LTE system.
FIG. 5 shows an example of a physical channel structure.
FIG. 6 shows a logged measurement configuration procedure.
FIG. 7 shows MBMS definitions.
FIG. 8 shows change of MCCH information.
FIG. 9 shows a MCCH information acquisition procedure.
FIG. 10 shows an example of a method for performing MBMS-MDT according to an embodiment of the present invention.
FIG. 11 shows another example of a method for performing MBMS-MDT according to an embodiment of the present invention.
FIG. 12 shows a wireless communication system to implement an embodiment of the present invention.
The technology described below can be used in various wireless communication systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. The CDMA can be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA-2000. The TDMA can be implemented with a radio technology such as global system for mobile communications (GSM)/general packet ratio service (GPRS)/enhanced data rate for GSM evolution (EDGE). The OFDMA can be implemented with a radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), etc. IEEE 802.16m is an evolution of IEEE 802.16e, and provides backward compatibility with an IEEE 802.16-based system. The UTRA is a part of a universal mobile telecommunication system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of an evolved UMTS (E-UMTS) using the E-UTRA. The 3GPP LTE uses the OFDMA in downlink and uses the SC-FDMA in uplink. LTE-advance (LTE-A) is an evolution of the 3GPP LTE.
For clarity, the following description will focus on the LTE-A. However, technical features of the present invention are not limited thereto.
FIG. 1 shows LTE system architecture. The communication network is widely deployed to provide a variety of communication services such as voice over internet protocol (VoIP) through IMS and packet data.
Referring to FIG. 1, the LTE system architecture includes one or more user equipment (UE; 10), an evolved-UMTS terrestrial radio access network (E-UTRAN) and an evolved packet core (EPC). The UE 10 refers to a communication equipment carried by a user. The UE 10 may be fixed or mobile, and may be referred to as another terminology, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a wireless device, etc.
The E-UTRAN includes one or more evolved node-B (eNB) 20, and a plurality of UEs may be located in one cell. The eNB 20 provides an end point of a control plane and a user plane to the UE 10. The eNB 20 is generally a fixed station that communicates with the UE 10 and may be referred to as another terminology, such as a base station (BS), an access point, etc. One eNB 20 may be deployed per cell.
Hereinafter, a downlink (DL) denotes communication from the eNB 20 to the UE 10, and an uplink (UL) denotes communication from the UE 10 to the eNB 20. In the DL, a transmitter may be a part of the eNB 20, and a receiver may be a part of the UE 10. In the UL, the transmitter may be a part of the UE 10, and the receiver may be a part of the eNB 20.
The EPC includes a mobility management entity (MME) and a system architecture evolution (SAE) gateway (S-GW). The MME/S-GW 30 may be positioned at the end of the network and connected to an external network. For clarity, MME/S-GW 30 will be referred to herein simply as a “gateway,” but it is understood that this entity includes both the MME and S-GW.
The MME provides various functions including non-access stratum (NAS) signaling to eNBs 20, NAS signaling security, access stratum (AS) security control, inter core network (CN) node signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmission), tracking area list management (for UE in idle and active mode), packet data network (PDN) gateway (P-GW) and S-GW selection, MME selection for handovers with MME change, serving GPRS support node (SGSN) selection for handovers to 2G or 3G 3GPP access networks, roaming, authentication, bearer management functions including dedicated bearer establishment, support for public warning system (PWS) (which includes earthquake and tsunami warning system (ETWS) and commercial mobile alert system (CMAS)) message transmission. The S-GW host provides assorted functions including per-user based packet filtering (by e.g., deep packet inspection), lawful interception, UE Internet protocol (IP) address allocation, transport level packet marking in the DL, UL and DL service level charging, gating and rate enforcement, DL rate enforcement based on access point name aggregate maximum bit rate (APN-AMBR).
Interfaces for transmitting user traffic or control traffic may be used. The UE 10 is connected to the eNB 20 via a Uu interface. The eNBs 20 are connected to each other via an X2 interface. Neighboring eNBs may have a meshed network structure that has the X2 interface. A plurality of nodes may be connected between the eNB 20 and the gateway 30 via an S1 interface.
FIG. 2 shows a block diagram of architecture of a typical E-UTRAN and a typical EPC. Referring to FIG. 2, the eNB 20 may perform functions of selection for gateway 30, routing toward the gateway 30 during a radio resource control (RRC) activation, scheduling and transmitting of paging messages, scheduling and transmitting of broadcast channel (BCH) information, dynamic allocation of resources to the UEs 10 in both UL and DL, configuration and provisioning of eNB measurements, radio bearer control, radio admission control (RAC), and connection mobility control in LTE_ACTIVE state. In the EPC, and as noted above, gateway 30 may perform functions of paging origination, LTE_IDLE state management, ciphering of the user plane, SAE bearer control, and ciphering and integrity protection of NAS signaling.
FIG. 3 shows a block diagram of a user plane protocol stack of an LTE system. FIG. 4 shows a block diagram of a control plane protocol stack of an LTE system. Layers of a radio interface protocol between the UE and the E-UTRAN may be classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on the lower three layers of the open system interconnection (OSI) model that is well-known in the communication system.
A physical (PHY) layer belongs to the L1. The PHY layer provides a higher layer with an information transfer service through a physical channel. The PHY layer is connected to a medium access control (MAC) layer, which is a higher layer of the PHY layer, through a transport channel. A physical channel is mapped to the transport channel. Data between the MAC layer and the PHY layer is transferred through the transport channel. Between different PHY layers, i.e. between a PHY layer of a transmission side and a PHY layer of a reception side, data is transferred via the physical channel.
A MAC layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer belong to the L2. The MAC layer provides services to the RLC layer, which is a higher layer of the MAC layer, via a logical channel. The MAC layer provides data transfer services on logical channels. The RLC layer supports the transmission of data with reliability. Meanwhile, a function of the RLC layer may be implemented with a functional block inside the MAC layer. In this case, the RLC layer may not exist. The PDCP layer provides a function of header compression function that reduces unnecessary control information such that data being transmitted by employing IP packets, such as IPv4 or IPv6, can be efficiently transmitted over a radio interface that has a relatively small bandwidth.
A radio resource control (RRC) layer belongs to the L3. The RLC layer is located at the lowest portion of the L3, and is only defined in the control plane. The RRC layer controls logical channels, transport channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers (RBs). The RB signifies a service provided the L2 for data transmission between the UE and E-UTRAN.
Referring to FIG. 3, the RLC and MAC layers (terminated in the eNB on the network side) may perform functions such as scheduling, automatic repeat request (ARQ), and hybrid ARQ (HARQ). The PDCP layer (terminated in the eNB on the network side) may perform the user plane functions such as header compression, integrity protection, and ciphering.
Referring to FIG. 4, the RLC and MAC layers (terminated in the eNB on the network side) may perform the same functions for the control plane. The RRC layer (terminated in the eNB on the network side) may perform functions such as broadcasting, paging, RRC connection management, RB control, mobility functions, and UE measurement reporting and controlling. The NAS control protocol (terminated in the MME of gateway on the network side) may perform functions such as a SAE bearer management, authentication, LTE_IDLE mobility handling, paging origination in LTE_IDLE, and security control for the signaling between the gateway and UE.
FIG. 5 shows an example of a physical channel structure. A physical channel transfers signaling and data between PHY layer of the UE and eNB with a radio resource. A physical channel consists of a plurality of subframes in time domain and a plurality of subcarriers in frequency domain. One subframe, which is 1 ms, consists of a plurality of symbols in the time domain. Specific symbol(s) of the subframe, such as the first symbol of the subframe, may be used for a physical downlink control channel (PDCCH). The PDCCH carries dynamic allocated resources, such as a physical resource block (PRB) and modulation and coding scheme (MCS).
A DL transport channel includes a broadcast channel (BCH) used for transmitting system information, a paging channel (PCH) used for paging a UE, a downlink shared channel (DL-SCH) used for transmitting user traffic or control signals, a multicast channel (MCH) used for multicast or broadcast service transmission. The DL-SCH supports HARQ, dynamic link adaptation by varying the modulation, coding and transmit power, and both dynamic and semi-static resource allocation. The DL-SCH also may enable broadcast in the entire cell and the use of beamforming.
A UL transport channel includes a random access channel (RACH) normally used for initial access to a cell, a uplink shared channel (UL-SCH) for transmitting user traffic or control signals, etc. The UL-SCH supports HARQ and dynamic link adaptation by varying the transmit power and potentially modulation and coding. The UL-SCH also may enable the use of beamforming.
The logical channels are classified into control channels for transferring control plane information and traffic channels for transferring user plane information, according to a type of transmitted information. That is, a set of logical channel types is defined for different data transfer services offered by the MAC layer.
The control channels are used for transfer of control plane information only. The control channels provided by the MAC layer include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH) and a dedicated control channel (DCCH). The BCCH is a downlink channel for broadcasting system control information. The PCCH is a downlink channel that transfers paging information and is used when the network does not know the location cell of a UE. The CCCH is used by UEs having no RRC connection with the network. The MCCH is a point-to-multipoint downlink channel used for transmitting multimedia broadcast multicast services (MBMS) control information from the network to a UE. The DCCH is a point-to-point bi-directional channel used by UEs having an RRC connection that transmits dedicated control information between a UE and the network.
Traffic channels are used for the transfer of user plane information only. The traffic channels provided by the MAC layer include a dedicated traffic channel (DTCH) and a multicast traffic channel (MTCH). The DTCH is a point-to-point channel, dedicated to one UE for the transfer of user information and can exist in both uplink and downlink. The MTCH is a point-to-multipoint downlink channel for transmitting traffic data from the network to the UE.
Uplink connections between logical channels and transport channels include the DCCH that can be mapped to the UL-SCH, the DTCH that can be mapped to the UL-SCH and the CCCH that can be mapped to the UL-SCH. Downlink connections between logical channels and transport channels include the BCCH that can be mapped to the BCH or DL-SCH, the PCCH that can be mapped to the PCH, the DCCH that can be mapped to the DL-SCH, and the DTCH that can be mapped to the DL-SCH, the MCCH that can be mapped to the MCH, and the MTCH that can be mapped to the MCH.
An RRC state indicates whether an RRC layer of the UE is logically connected to an RRC layer of the E-UTRAN. The RRC state may be divided into two different states such as an RRC idle state (RRC_IDLE) and an RRC connected state (RRC_CONNECTED). In RRC_IDLE, the UE may receive broadcasts of system information and paging information while the UE specifies a discontinuous reception (DRX) configured by NAS, and the UE has been allocated an identification (ID) which uniquely identifies the UE in a tracking area and may perform public land mobile network (PLMN) selection and cell re-selection. Also, in RRC_IDLE, no RRC context is stored in the eNB.
In RRC_CONNECTED, the UE has an E-UTRAN RRC connection and a context in the E-UTRAN, such that transmitting and/or receiving data to/from the eNB becomes possible. Also, the UE can report channel quality information and feedback information to the eNB. In RRC_CONNECTED, the E-UTRAN knows the cell to which the UE belongs. Therefore, the network can transmit and/or receive data to/from UE, the network can control mobility (handover and inter-radio access technologies (RAT) cell change order to GSM EDGE radio access network (GERAN) with network assisted cell change (NACC)) of the UE, and the network can perform cell measurements for a neighboring cell.
In RRC_IDLE, the UE specifies the paging DRX cycle. Specifically, the UE monitors a paging signal at a specific paging occasion of every UE specific paging DRX cycle. The paging occasion is a time interval during which a paging signal is transmitted. The UE has its own paging occasion. A paging message is transmitted over all cells belonging to the same tracking area. If the UE moves from one tracking area (TA) to another TA, the UE will send a tracking area update (TAU) message to the network to update its location.
Minimization of drive tests (MDT) is described. In may be referred to 3GPP TS 37.320 V11.3.0 (2013-03) and Section 5.6.6 and 5.6.8 of 3GPP TS 36.331 V11.5.0 (2013-09). The general principles and requirements guiding the definition of functions for MDT are the following.
1. MDT mode: There are two modes for the MDT measurements, which are logged MDT and immediate MDT. The logged MDT is MDT functionality involving measurement logging by the UE in IDLE mode, CELL_PCH and URA_PCH states (when the UE is in UTRA) for reporting to eNB/radio network controller (RNC) at a later point in time. The immediate MDT is MDT functionality involving measurements performed by the UE in CONNECTED state and reporting of the measurements to eNB/RNC available at the time of reporting condition as well as measurements by the network for MDT purposes. There are also cases of measurement collection not specified as either immediate or logged MDT, such as accessibility measurements.
2. UE measurement configuration: It is possible to configure MDT measurements for the UE logging purpose independently from the network configurations for normal radio resource management (RRM) purposes. However, in most cases, the availability of measurement results is conditionally dependent on the UE RRM configuration.
3. UE measurement collection and reporting: UE MDT measurement logs consist of multiple events and measurements taken over time. The time interval for measurement collection and reporting is decoupled in order to limit the impact on the UE battery consumption and network signaling load.
4. Geographical scope of measurement logging: It is possible to configure the geographical area where the defined set of measurements shall be collected.
5. Location information: The measurements shall be linked to available location information and/or other information or measurements that can be used to derive location information.
6. Time information: The measurements in measurement logs shall be linked to a time stamp.
7. UE capability information: The network may use UE capabilities to select terminals for MDT measurements.
8. Dependency on self-optimizing network (SON): The solutions for MDT are able to work independently from SON support in the network. Relation between measurements/solution for MDT and UE side SON functions shall be established in a way that re-use of functions is achieved where possible.
9. Dependency on TRACE: The subscriber/cell trace functionality is reused and extended to support MDT. If the MDT is initiated toward to a specific UE (e.g., based on international mobile subscriber identity (IMSI), international mobile station equipment identity (IMEI) software version (SV), etc.), the signalling based trace procedure is used, otherwise the management based trace procedure (or cell traffic trace procedure) is used.
The solutions for MDT shall take into account the following constraints:
1. UE measurements: The UE measurement logging mechanism is an optional feature. In order to limit the impact on UE power consumption and processing, the UE measurement logging should as much as possible rely on the measurements that are available in the UE according to radio resource management enforced by the access network.
2. Location information: The availability of location information is subject to UE capability and/or UE implementation. Solutions requiring location information shall take into account power consumption of the UE due to the need to run its positioning components.
Logged MDT procedure is described. Support of logged MDT complies with the principles for idle mode measurements in the UE. Furthermore, measurement logging is differentiated based on UE states in idle mode, i.e. camped normally, any cell selection or camped on any cell. The UE shall perform measurement logging in "camped normally" state. In "any cell selection" and "camped on any cell" state the UE is not required to perform MDT measurement logging (including time and location information). For logged MDT, the configuration, measurement collection and reporting of the concerning measurement will always be done in cells of the same RAT type.
FIG. 6 shows a logged measurement configuration procedure. The purpose of the logged measurement procedure is to configure the UE to perform logging of measurement results while in RRC_IDLE. The logged measurement procedure applies to logged measurements capable UEs that are in RRC_CONNECTED. In step S60, the E-UTRAN initiates the logged measurement configuration procedure to the UE in RRC_CONNECTED by sending the LoggedMeasurementConfiguration message, which is used to transfer configuration parameters for logged MDT. This is a unidirectional RRC signaling procedure. A release operation for logged measurement configuration in the UE is realized only by configuration replacement when the configuration is overwritten or by configuration clearance in case a duration timer stopping or expiration condition is met.
Upon receiving the LoggedMeasurementConfiguration message, the UE shall:
1>discard the logged measurement configuration as well as the logged measurement information;
1> store the received loggingDuration, loggingInterval and areaConfiguration, if included, in VarLogMeasConfig;
1> if the LoggedMeasurementConfiguration message includes plmn-IdentityList;
2> set plmn-IdentityList in VarLogMeasReport to include the registered PLMN (RPLMN) as well as the PLMNs included in plmn-IdentityList;
1> else:
2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN;
1> store the received absoluteTimeInfo,traceReference,
traceRecordingSessionRef and tce-Id in VarLogMeasReport;
1> start timer T330 with the timer value set to the loggingDuration;
Upon expiry of T330, the UE shall:
1> release VarLogMeasConfig;
The UE is allowed to discard stored logged measurements, i.e. to release VarLogMeasReport 48 hours after T330 expiry.
Release of logged measurement configuration procedure may release the logged measurement configuration as well as the logged measurement information. The UE shall initiate the release of logged measurement configuration procedure upon receiving a logged measurement configuration in another RAT. The UE shall also initiate the procedure upon power off or detach. The UE shall:
1> stop timer T330, if running;
1> if stored, discard the logged measurement configuration as well as the logged measurement information, i.e. release the UE variables VarLogMeasConfig and VarLogMeasReport;
Measurements logging procedure specifies the logging of available measurements by a UE in RRC_IDLE that has a logged measurement configuration. While T330 is running, the UE shall:
1> perform the logging in accordance with the following:
2> if the UE is camping normally on an E-UTRA cell and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport and, if the cell is part of the area indicated by areaConfiguration if configured in VarLogMeasConfig:
3> perform the logging at regular time intervals, as defined by the loggingInterval in VarLogMeasConfig;
2> when adding a logged measurement entry in VarLogMeasReport, include the fields in accordance with the following:
3> set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged measurement configuration was received;
3> if detailed location information became available during the last logging interval, set the content of the locationInfo as follows:
4> include the locationCoordinates;
4> if available, include the uncertainty;
4> if available, include the confidence;
3> set the servCellIdentity to indicate global cell identity of the cell the UE is camping on;
3> set the measResultServCell to include the quantities of the cell the UE is camping on;
3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements that became available during the last logging interval for at most the following number of neighbouring cells; 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies (GERAN) per RAT;
2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330;
MBMS is described. It may be referred to Section 15 of 3GPP TS 36.300 V11.7.0 (2013-09) and Section 5.8 of 3GPP TS 36.331 V11.5.0 (2013-09).
FIG. 7 shows MBMS definitions. For MBMS, the following definitions may be introduced.
- Multicast-broadcast single-frequency network (MBSFN) synchronization area: This is an area of the network where all eNBs can be synchronized and perform MBSFN transmissions. MBSFN synchronization areas are capable of supporting one or more MBSFN areas. On a given frequency layer, an eNB can only belong to one MBSFN synchronization area. MBSFN synchronization areas are independent from the definition of MBMS service areas.
- MBSFN transmission or a transmission in MBSFN mode: This is a simulcast transmission technique realized by transmission of identical waveforms at the same time from multiple cells. An MBSFN transmission from multiple cells within the MBSFN area is seen as a single transmission by a UE.
- MBSFN area: an MBSFN area consists of a group of cells within an MBSFN synchronization area of a network, which are coordinated to achieve an MBSFN transmission. Except for the MBSFN area reserved cells, all cells within an MBSFN area contribute to the MBSFN transmission and advertise its availability. The UE may only need to consider a subset of the MBSFN areas that are configured, i.e., when it knows which MBSFN area applies for the service(s) it is interested to receive.
- MBSFN area reserved cell: This is a cell within a MBSFN area which does not contribute to the MBSFN transmission. The cell may be allowed to transmit for other services but at restricted power on the resource allocated for the MBSFN transmission.
- Synchronization sequence: Each synchronization protocol data unit (SYNC PDU) contains a time stamp which indicates the start time of the synchronization sequence. For an MBMS service, each synchronization sequence has the same duration which is configured in the broadcast and multicast service center (BM-SC) and the multi-cell/multicast coordination entity (MCE).
- Synchronization period: The synchronization period provides the time reference for the indication of the start time of each synchronization sequence. The time stamp which is provided in each SYNC PDU is a relative value which refers to the start time of the synchronization period. The duration of the synchronization period is configurable.
The following principles govern the MCCH structure:
- One MBSFN area is associated with one MCCH and one MCCH corresponds to one MBSFN area;
- The MCCH is sent on MCH;
- MCCH consists of a single MBSFN area configuration RRC message which lists all the MBMS services with ongoing sessions and an optional MBMS counting request message;
- MCCH is transmitted by all cells within an MBSFN area, except the MBSFN area reserved cells;
- MCCH is transmitted by RRC every MCCH repetition period;
- MCCH uses a modification period;
- A notification mechanism is used to announce changes of MCCH due to either session start or the presence of an MBMS counting request message: The notification is sent periodically throughout the modification period preceding the change of MCCH, in MBSFN subframes configured for notification. The downlink control information (DCI) format 1C with MBMS radio network temporary identity (M-RNTI) is used for notification and includes an 8-bit bitmap to indicate the one or more MBSFN area(s) in which the MCCH change(s). The UE monitors more than one notification subframe per modification period. When the UE receives a notification, it acquires the MCCH at the next modification period boundary;
- The UE detects changes to MCCH which are not announced by the notification mechanism by MCCH monitoring at the modification period.
In general, the control information relevant only for UEs supporting MBMS is separated as much as possible from unicast control information. Most of the MBMS control rmation is provided on a logical channel specific for MBMS common control rmation: the MCCH. E-UTRA employs one MCCH logical channel per MBSFN area. In case the network configures multiple MBSFN areas, the UE acquires the MBMS control rmation from the MCCHs that are configured to identify if services it is interested to receive are ongoing. An MBMS capable UE may be only required to support reception of a single MBMS service at a time. The MCCH carries the MBSFNAreaConfiguration message, which indicates the MBMS sessions that are ongoing as well as the (corresponding) radio resource configuration. The MCCH may also carry the MBMSCountingRequest message, when E-UTRAN wishes to count the number of UEs in RRC_CONNECTED that are receiving or interested to receive one or more specific MBMS services.
A limited amount of MBMS control rmation is provided on the BCCH. This primarily concerns the rmation needed to acquire the MCCH(s). This rmation is carried by means of a single MBMS specific SystemInformationBlock: SystemInformationBlockType13. An MBSFN area is identified solely by the mbsfn-AreaId in SystemInformationBlockType13. At mobility, the UE considers that the MBSFN area is continuous when the source cell and the target cell broadcast the same value in the mbsfn-AreaId.
The MCCH rmation is transmitted periodically, using a configurable repetition period. Scheduling rmation is not provided for MCCH, i.e. both the time domain scheduling as well as the lower layer configuration are semi-statically configured, as defined within SystemInformationBlockType13.
For MBMS user data, which is carried by the MTCH logical channel, E-UTRAN periodically provides MSI at lower layers (MAC). This MCH rmation only concerns the time domain scheduling, i.e. the frequency domain scheduling and the lower layer configuration are semi-statically configured. The periodicity of the MSI is configurable and defined by the MCH scheduling period.
Change of MCCH rmation only occurs at specific radio frames, i.e. the concept of a modification period is used. Within a modification period, the same MCCH rmation may be transmitted a number of times, as defined by its scheduling (which is based on a repetition period). The modification period boundaries are defined by system frame number (SFN) values for which SFN mod m=0, where m is the number of radio frames comprising the modification period. The modification period is configured by means of SystemInformationBlockType13.
FIG. 8 shows change of MCCH information. When the network changes (some of) the MCCH rmation, it notifies the UEs about the change during a first modification period. In the next modification period, the network transmits the updated MCCH rmation. In FIG. 8, different colors indicate different MCCH rmation. Upon receiving a change notification, a UE interested to receive MBMS services acquires the new MCCH rmation immediately from the start of the next modification period. The UE applies the previously acquired MCCH rmation until the UE acquires the new MCCH rmation.
Indication of an MBMS specific RNTI, the M-RNTI, on PDCCH is used to rm UEs in RRC_IDLE and UEs in RRC_CONNECTED about an MCCH rmation change. When receiving an MCCH rmation change notification, the UE knows that the MCCH rmation will change at the next modification period boundary. The notification on PDCCH indicates which of the MCCHs will change, which is done by means of an 8-bit bitmap. Within this bitmap, the bit at the position indicated by the field notificationIndicator is used to indicate changes for that MBSFN area: if the bit is set to "1", the corresponding MCCH will change. No further details are provided, e.g. regarding which MCCH rmation will change. The MCCH rmation change notification is used to rm the UE about a change of MCCH rmation upon session start or about the start of MBMS counting.
The MCCH rmation change notifications on PDCCH are transmitted periodically and are carried on MBSFN subframes only. These MCCH rmation change notification occasions are common for all MCCHs that are configured, and configurable by parameters included in SystemInformationBlockType13: a repetition coefficient, a radio frame offset and a subframe index. These common notification occasions are based on the MCCH with the shortest modification period.
The E-UTRAN may modify the MBMS configuration rmation provided on MCCH at the same time as updating the MBMS configuration rmation carried on BCCH, i.e. at a coinciding BCCH and MCCH modification period. Upon detecting that a new MCCH is configured on BCCH, a UE interested to receive one or more MBMS services should acquire the MCCH, unless it knows that the services it is interested in are not provided by the corresponding MBSFN area.
A UE that is receiving an MBMS service shall acquire the MCCH rmation from the start of each modification period. A UE that is not receiving an MBMS service, as well as UEs that are receiving an MBMS service but potentially interested to receive other services not started yet in another MBSFN area, shall verify that the stored MCCH rmation remains valid by attempting to find the MCCH rmation change notification at least notificationRepetitionCoeff times during the modification period of the applicable MCCH(s), if no MCCH rmation change notification is received.
In case the UE is aware which MCCH(s) E-UTRAN uses for the service(s) it is interested to receive, the UE may only need to monitor change notifications for a subset of the MCCHs that are configured, referred to as the 'applicable MCCH(s)' in the above.
The UE applies the MCCH information acquisition procedure to acquire the MBMS control information that is broadcasted by the E-UTRAN. The procedure applies to MBMS capable UEs that are in RRC_IDLE or in RRC_CONNECTED.
A UE interested to receive MBMS services shall apply the MCCH rmation acquisition procedure upon entering the corresponding MBSFN area (e.g. upon power on, following UE mobility) and upon receiving a notification that the MCCH rmation has changed. A UE that is receiving an MBMS service shall apply the MCCH rmation acquisition procedure to acquire the MCCH, which corresponds with the service that is being received, at the start of each modification period.
Unless explicitly stated otherwise in the procedural specification, the MCCH rmation acquisition procedure overwrites any stored MCCH rmation, i.e. delta configuration is not applicable for MCCH rmation and the UE discontinues using a field if it is absent in MCCH rmation unless explicitly specified otherwise.
FIG. 9 shows a MCCH information acquisition procedure. An MBMS capable UE shall:
1> if the procedure is triggered by an MCCH rmation change notification:
2> start acquiring the MBSFNAreaConfiguration message (in step S90) and the MBMSCountingRequest message if present (in step S91), from the beginning of the modification period following the one in which the change notification was received;
1> if the UE enters an MBSFN area:
2> acquire the MBSFNAreaConfiguration message (in step S90) and the MBMSCountingRequest message if present (in step S91), at the next repetition period;
1> if the UE is receiving an MBMS service:
2> start acquiring the MBSFNAreaConfiguration message (in step S90) and the MBMSCountingRequest message if present (in step S91), that both concern the MBSFN area of the service that is being received, from the beginning of each modification period;
Logged MDT procedure may be performed for MBMS. Hereinafter, the logged MDT procedure for MBMS may be referred to as MBMS-MDT. For MBMS-MDT, the logged measurement configuration procedure for described in FIG. 6 may be performed in order to log of measurement results for MBSFN in both RRC_IDLE and RRC_CONNECTED. Further, for MBMS-MDT, the measurements logging procedure specifies the logging of available measurements by a UE in RRC_IDLE that has a logged measurement configuration and the logging of available measurements by a UE in both RRC_IDLE and RRC_CONNECTED if targetMBSFN-AreaList is included in VarLogMeasConfig. For MBSFN areas from which the UE is receiving MBMS service, the UE may perform MBSFN measurements, and perform logging at regular time intervals, but only for those intervals for which MBSFN measurement results are available.
As described above, the UE performs MBMS-MDT for an MBSFN area only when the UE is receiving an MBMS from the MBSFN area. When the UE enters coverage hole of MBMS in which MBMS cannot be received without enough quality, the quality of MBMS may be degraded. In this case, according to the prior art, the UE stops receiving MBMS or tries to receive corresponding service via unicast bearer, and therefore, also stops performing MBMS-MDT for MBSFN area corresponding to the coverage hole. This is against the purpose of MBMS-MDT. Therefore, the network operator cannot obtain sufficient results of coverage hole.
In order to solve the problem described above, the UE needs to keep performing MBMS-MDT even though the UE is in coverage hole of MBMS. Hereinafter, a method for performing MBMS-MDT by using a MBMS-MDT timer according to an embodiment of the present invention is described. According to an embodiment of the present invention, even though the UE stops receiving MBMS, the UE keeps performing MBMS-MDT while the MBMS-MDT timer is running when a specific condition is met. The MBMS-MDT timer is a newly defined timer for MBMS-MDT, and is a different from the timer used for conventional logged MDT procedure. The UE keeps performing MBMS-MDT for a MBSFN area while the corresponding MBMS-MDT timer is running. When the MBMS-MDT timer expires, the UE stops performing MBMS-MDT for the MBSFN area. Accordingly, the network operator or service operator can harvest measurement results of MBSFN areas in which quality of MBMS is not good enough, which is actually needed.
FIG. 10 shows an example of a method for performing MBMS-MDT according to an embodiment of the present invention.
In step S100, the UE receives a MBMS-MDT timer configuration from a network. The MBMS-MDT timer configuration may configure start/expiry/early termination of the MBMS-MDT timer. The MBMS-MDT timer may be configured per MBSFN area. The MBMS-MDT timer configuration may be received via the MBMS-MDT configuration. Or, the MBMS-MDT timer configuration may be received via broadcast signaling, i.e. system information block (SIB) type 13 along with MBSFN area identities. Or, the MBMS-MDT timer may be predefined.
In step S110, the UE starts the MBMS-MDT timer based on the received MBMS-MDT timer configuration when a specific condition, which relates to degradation of quality of MBMS, is met. The UE starts the MBMS-MDT timer when quality of receiving MBMS is not good enough. More specifically, the UE starts the MBMS-MDT timer when at least one of following conditions is met.
- When the UE stops receiving MBMS and the UE does not receive any MBMS from the MBSFN area any more.
- When measured reference signal received power (RSRP) of MBMS received from the MBSFN area is lower than a RSRP threshold.
- When measured reference signal received quality (RSRQ) of MBMS received from the MBSFN area is lower than a RSRQ threshold.
- When measured block error rate (BLER) of MBMS received from the MBSFN area is lower than a BLER threshold.
The RSRP/RSRQ/BLER thresholds may be configured by the network. Or, the RSRP/RSRQ/BLER thresholds may be configured by UE implementation.
In step S120, while the MBMS-MDT timer is running, the UE performs MBMS-MDT based on MBMS-MDT configuration. Performing of the MBMS-MDT may include performing MBMS measurements, logging measurement results, and reporting logged results. The MBMS measurements to be performed by the UE for the MBMS-MDT may include MBSFN RSRP/RSRQ per MBSFN area, MCH BLER per MCS, per MCH, and per MBSFN area, and/or the amount of received RLC SDUs for a certain period of time. Further, if the sparse MBMS measurement is configured, the UE may perform sparse MBMS measurements and logging according to the sparse MBMS measurement configuration while the MBMS-MDT timer is running. The sparse MBMS measurement configuration may include a sparse interval and a sparse duration. The sparse interval may be longer than normal MBMS measurement/logging interval, and the sparse MDT duration may be shorter than normal MBMS measurement/logging duration. The sparse MBMS measurement may be configured along with the MBMS-MDT timer. The sparse MBMS measurement may be configured per MBMS-MDT timer or per MBSFN area. Or, only one sparse MBMS measurement may be configured for the UE, then the UE may use the one sparse MBMS measurement configuration for all MBSFN area.
The MBMS-MDT timer may be terminated early before expiry. The UE may terminate the MBMS-MDT timer which is running when the UE moves to another frequency by performing handover or cell re-selection procedure. If the UE can measure the MBSFN area even though it moves to another frequency, e.g. carrier aggregation (CA) capable UE, the UE may not terminate the MBMS-MDT timer. When the MBMS-MDT timer is terminated, the UE stops performing MBMS-MDT for the corresponding MBSFN area.
FIG. 11 shows another example of a method for performing MBMS-MDT according to an embodiment of the present invention.
In step S200, the UE is receiving MBMS service # 1 and #2 from MBSFN area # 1 and #2, respectively.
In step S210, the UE is configured to perform MBMS-MDT by receiving the MBMS-MDT configuration form the network. The MBMS-MDT configuration includes the MBMS-MDT timer configuration. MBMS-MDT timers are set per MBSFN area, i.e. MBMS-MDT timer # 1 for MBSFN area # 1 and MBMS-MDT timer # 2 for MBSFN area # 2, respectively, by the MBMSMDT timer configuration. Further, the MBMS-MDT configuration includes the sparse MBMS measurements configuration, which includes the sparse interval and sparse duration.
In step S220, the UE starts to perform MBMS-MDT for MBSFN area # 1 and #2 based on the received MBMS-MDT configuration.
In step S230, the UE enters a coverage hole of MBSFN area # 1. The UE detects that the service quality of the MBMS service # 1 is degraded rapidly. The UE stops receiving the MBMS service # 1 and starts the MBMS-MDT timer # 1. Accordingly, the UE can keep performing MBMS-MDT for MBSFN area # 1. The UE may perform MBMS-MDT according to the sparse MBMS measurements configuration for MBSFN area # 1 while performing normal MBMS-MDT for MBSFN area # 2.
In step S240, the MBMS-MDT timer # 1 expires. The UE stops performing MBMS-MDT for MBSFN area # 1.
In step S250, the UE enters a coverage hole of MBSFN area # 2. The UE detects that the service quality of the MBMS service # 2 is degraded rapidly, e.g. by performing RSRQ measurement. The UE stops receiving the MBMS service # 2 and starts the MBMS-MDT timer # 2. Accordingly, the UE can keep performing MBMS-MDT for MBSFN area # 2. The UE may perform MBMS-MDT for MBSFN area # 2 according to the sparse MBMS measurements configuration.
In step S260, while the MBMS-MDT timer is running, i.e. before the MBMS-MDT timer # 2 expires, the UE receives a handover command message and downlink frequency of a target cell which is different from that of the current serving cell.
In step S270, since early termination condition is met, the UE terminates the MBMS-MDT timer # 2 and stops performing MBMS-MDT for MBSFN area # 2.
FIG. 12 shows a wireless communication system to implement an embodiment of the present invention.
An eNB 800 may include a processor 810, a memory 820 and a radio frequency (RF) unit 830. The processor 810 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of the radio interface protocol may be implemented in the processor 810. The memory 820 is operatively coupled with the processor 810 and stores a variety of information to operate the processor 810. The RF unit 830 is operatively coupled with the processor 810, and transmits and/or receives a radio signal.
A UE 900 may include a processor 910, a memory 920 and a RF unit 930. The processor 910 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of the radio interface protocol may be implemented in the processor 910. The memory 920 is operatively coupled with the processor 910 and stores a variety of information to operate the processor 910. The RF unit 930 is operatively coupled with the processor 910, and transmits and/or receives a radio signal.
The processors 810, 910 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device. The memories 820, 920 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and/or other storage device. The RF units 830, 930 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in memories 820, 920 and executed by processors 810, 910. The memories 820, 920 can be implemented within the processors 810, 910 or external to the processors 810, 910 in which case those can be communicatively coupled to the processors 810, 910 via various means as is known in the art.
In view of the exemplary systems described herein, methodologies that may be implemented in accordance with the disclosed subject matter have been described with reference to several flow diagrams. While for purposed of simplicity, the methodologies are shown and described as a series of steps or blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the steps or blocks, as some steps may occur in different orders or concurrently with other steps from what is depicted and described herein. Moreover, one skilled in the art would understand that the steps illustrated in the flow diagram are not exclusive and other steps may be included or one or more of the steps in the example flow diagram may be deleted without affecting the scope and spirit of the present disclosure.
Claims (15)
- A method for performing, by a user equipment (UE), multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system, the method comprising:
receiving, by the UE, a MBMS-MDT timer configuration from a network;
starting, by the UE, a MBMS-MDT timer based on the received MBMS-MDT timer configuration when a specific condition, which relates to degradation of quality of MBMS, is met; and
while the MBMS-MDT timer is running, performing, by the UE, MBMS-MDT. - The method of claim 1, wherein the MBMS-MDT timer configuration is received via a MBMS-MDT configuration.
- The method of claim 1, wherein the MBMS-MDT timer configuration is received via system information.
- The method of claim 1, wherein the MBMS-MDT timer is configured per multicast broadcast single frequency network (MBSFN) area.
- The method of claim 1, wherein the specific condition is that the UE stops receiving the MBMS due to degradation of the quality of the MBMS.
- The method of claim 1, wherein the specific condition is that measured reference signal received power (RSRP), reference signal received quality (RSRQ) or block error rate (BLER) of the MBMS is lower than a specific threshold.
- The method of claim 6, wherein the specific threshold is configured by the network.
- The method of claim 1, the MBMS-MDT timer is terminated while running when the UE moves to another frequency by a handover procedure or a cell re-selection procedure.
- The method of claim 8, further comprising stopping performing the MBMS-MDT upon terminating the MBMS-MDT timer.
- The method of claim 1, wherein performing the MBMS-MDT comprises performing MBMS measurements, logging measurement results and reporting logged results.
- The method of claim 9, wherein the MBMS measurements includes at least one of a MBSFN reference signal received power (RSRP) per MBSFN area, a MBSFN reference signal received quality (RSRQ) per MBSFN area, multicast channel (MCH) block error rate (BLER) per modulation and coding scheme (MCS), per MCH, and per MBSFN area, or amount of received radio link control (RLC) service data units (SDUs) for a certain period of time.
- The method of claim 1, further comprising receiving, by the UE, a sparse MBMS measurement configuration, including a sparse interval and a sparse duration, from the network.
- The method of claim 12, wherein the sparse interval is longer than a normal MBMS measurement or logging interval.
- The method of claim 12, wherein the sparse duration is shorter than a normal MBMS measurement or logging duration.
- A user equipment (UE) configured to perform multimedia broadcast multicast service (MBMS) minimization of drive test (MDT) in a wireless communication system, the UE comprising:
a radio frequency (RF) unit configured to transmit or receive a radio signal; and
a processor coupled to the RF unit, and configured to:
receive a MBMS-MDT timer configuration from a network;
start a MBMS-MDT timer based on the received MBMS-MDT timer configuration when a specific condition, which relates to quality of MBMS, is met; and
while the MBMS-MDT timer is running, perform MBMS-MDT.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP15761775.4A EP3117654B1 (en) | 2014-03-13 | 2015-03-10 | Method and apparatus for performing mbms mdt in wireless communication system |
US15/114,732 US10020902B2 (en) | 2014-03-13 | 2015-03-10 | Method and apparatus for performing MBMS MDT in wireless communication system |
CN201580010733.6A CN106031215B (en) | 2014-03-13 | 2015-03-10 | The method and apparatus of MBMS MDT are executed in a wireless communication system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201461952153P | 2014-03-13 | 2014-03-13 | |
US61/952,153 | 2014-03-13 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015137699A1 true WO2015137699A1 (en) | 2015-09-17 |
Family
ID=54072070
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2015/002297 WO2015137699A1 (en) | 2014-03-13 | 2015-03-10 | Method and apparatus for performing mbms mdt in wireless communication system |
Country Status (4)
Country | Link |
---|---|
US (1) | US10020902B2 (en) |
EP (1) | EP3117654B1 (en) |
CN (1) | CN106031215B (en) |
WO (1) | WO2015137699A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108282893A (en) * | 2017-01-06 | 2018-07-13 | 展讯通信(上海)有限公司 | Transmission method, method of reseptance, base station and the user equipment of public control message |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI603635B (en) * | 2014-05-09 | 2017-10-21 | 諾基亞科技公司 | Minimum measurement requirements for multi-broadcast single-frequency network measurements |
CN107113082B (en) * | 2014-11-21 | 2020-09-04 | 瑞典爱立信有限公司 | Method and apparatus for multimedia broadcast multicast service delivery |
US10716009B2 (en) * | 2015-09-11 | 2020-07-14 | Nec Corporation | Apparatus, method, and system relating to minimization of drive tests (MDT) measurements |
US10772151B2 (en) | 2018-01-05 | 2020-09-08 | Ofinno, Llc | Beam management in discontinuous reception |
EP3742790A4 (en) | 2018-01-22 | 2021-09-15 | Beijing Xiaomi Mobile Software Co., Ltd. | Method, device and system for minimizing road test measurement |
EP3749008A4 (en) | 2018-02-08 | 2021-09-15 | Beijing Xiaomi Mobile Software Co., Ltd. | Mdt configuration method and apparatus |
GB201909462D0 (en) * | 2019-07-01 | 2019-08-14 | Samsung Electronics Co Ltd | eMeas and MDT |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102348219A (en) * | 2010-08-04 | 2012-02-08 | 电信科学技术研究院 | Minimization drive test (MDT) processing method based on coverage hole and equipment |
WO2012047070A2 (en) * | 2010-10-08 | 2012-04-12 | Pantech Co., Ltd. | Method for obtaining information in wireless coommunication system and apparatus thereof using mdt |
US20120315890A1 (en) * | 2010-02-12 | 2012-12-13 | Takashi Suzuki | Methods and apparatus to perform measurements |
US20130045735A1 (en) * | 2010-05-04 | 2013-02-21 | Samsung Electronics Co. Ltd. | Method and apparatus for recording channel measurement information in a mobile communication system |
US20130128756A1 (en) * | 2011-11-17 | 2013-05-23 | Qualcomm Incorporated | Method and apparatus for physical layer measurements in multicast broadcast multimedia service systems |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9107102B2 (en) * | 2010-04-28 | 2015-08-11 | Lg Electronics Inc. | Method and apparatus for reporting a cell quality measurement result for MDT by a terminal |
US9686770B2 (en) * | 2010-06-15 | 2017-06-20 | Mediatek Inc. | Methods to support MBMS service continuity and counting and localized MBMS service |
US9380480B2 (en) * | 2011-08-25 | 2016-06-28 | Kyocera Corporation | Minimization drive test with reduced wireless device memory usage |
US9591501B2 (en) * | 2012-09-28 | 2017-03-07 | Nokia Technologies Oy | Measurement configuration and reporting with diverse traffic |
WO2014126424A1 (en) * | 2013-02-14 | 2014-08-21 | 엘지전자 주식회사 | Method for reporting mbms information in wireless communication system and device for supporting same |
WO2015106439A1 (en) * | 2014-01-17 | 2015-07-23 | 华为技术有限公司 | User equipment, network device, and logged minimization of drive tests measurement method |
-
2015
- 2015-03-10 EP EP15761775.4A patent/EP3117654B1/en active Active
- 2015-03-10 WO PCT/KR2015/002297 patent/WO2015137699A1/en active Application Filing
- 2015-03-10 CN CN201580010733.6A patent/CN106031215B/en not_active Expired - Fee Related
- 2015-03-10 US US15/114,732 patent/US10020902B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120315890A1 (en) * | 2010-02-12 | 2012-12-13 | Takashi Suzuki | Methods and apparatus to perform measurements |
US20130045735A1 (en) * | 2010-05-04 | 2013-02-21 | Samsung Electronics Co. Ltd. | Method and apparatus for recording channel measurement information in a mobile communication system |
CN102348219A (en) * | 2010-08-04 | 2012-02-08 | 电信科学技术研究院 | Minimization drive test (MDT) processing method based on coverage hole and equipment |
WO2012047070A2 (en) * | 2010-10-08 | 2012-04-12 | Pantech Co., Ltd. | Method for obtaining information in wireless coommunication system and apparatus thereof using mdt |
US20130128756A1 (en) * | 2011-11-17 | 2013-05-23 | Qualcomm Incorporated | Method and apparatus for physical layer measurements in multicast broadcast multimedia service systems |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108282893A (en) * | 2017-01-06 | 2018-07-13 | 展讯通信(上海)有限公司 | Transmission method, method of reseptance, base station and the user equipment of public control message |
Also Published As
Publication number | Publication date |
---|---|
US20160344489A1 (en) | 2016-11-24 |
EP3117654B1 (en) | 2019-07-31 |
EP3117654A4 (en) | 2017-10-11 |
US10020902B2 (en) | 2018-07-10 |
CN106031215A (en) | 2016-10-12 |
CN106031215B (en) | 2019-08-02 |
EP3117654A1 (en) | 2017-01-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10075867B2 (en) | Method and apparatus for maintaining MBMS MDT configuration in wireless communication system | |
EP3117652B1 (en) | Method and apparatus for performing selective mbms mdt in wireless communication system | |
US10015641B2 (en) | Method and apparatus for configuring MBMS MDT for multiple MBSFN areas in wireless communication system | |
US10111157B2 (en) | Method and apparatus for reconfiguring MBMS MDT in wireless communication system | |
EP3100500B1 (en) | Method and apparatus for transmitting report message in wireless communication system | |
US9973990B2 (en) | Method and apparatus for transmitting handover report message in wireless communication system | |
EP3117654B1 (en) | Method and apparatus for performing mbms mdt in wireless communication system | |
US10153914B2 (en) | Method and apparatus for indicating usage of MBSFN area in wireless communication system | |
US20170180952A1 (en) | Method and apparatus for supporting broadcast mobile convergence in wireless communication system | |
US10257734B2 (en) | Method and apparatus for indicating logged MBMS measurement availability in wireless communication system | |
US9131406B2 (en) | Method and apparatus for reporting short stay in wireless communication system | |
WO2015115833A1 (en) | Method and apparatus for determining measurement period in wireless communication system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15761775 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15114732 Country of ref document: US |
|
REEP | Request for entry into the european phase |
Ref document number: 2015761775 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015761775 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |