WO2018032469A1 - Techniques et appareils pour la configuration de sc-ptm dans la signalisation de transfert intercellulaire pour la continuité de service - Google Patents

Techniques et appareils pour la configuration de sc-ptm dans la signalisation de transfert intercellulaire pour la continuité de service Download PDF

Info

Publication number
WO2018032469A1
WO2018032469A1 PCT/CN2016/095885 CN2016095885W WO2018032469A1 WO 2018032469 A1 WO2018032469 A1 WO 2018032469A1 CN 2016095885 W CN2016095885 W CN 2016095885W WO 2018032469 A1 WO2018032469 A1 WO 2018032469A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
mobile device
ptm
mtch
configuration information
Prior art date
Application number
PCT/CN2016/095885
Other languages
English (en)
Inventor
Kuo-Chun Lee
Sivaramakrishna Veerepalli
Ralph A. Gholmieh
Feilu Liu
Masato Kitazoe
Xipeng Zhu
Daniel Amerga
Muralidharan Murugan
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2016/095885 priority Critical patent/WO2018032469A1/fr
Publication of WO2018032469A1 publication Critical patent/WO2018032469A1/fr

Links

Images

Classifications

    • 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/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information

Definitions

  • aspects of the present disclosure generally relate to wireless communications, and more particularly to techniques and apparatuses for single cell point-to-multipoint (SC-PTM) configuration in handover signaling for service continuity.
  • SC-PTM single cell point-to-multipoint
  • Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc. ) .
  • multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency divisional multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency divisional multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • 3GPP Third Generation Partnership Project
  • LTE is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, using new spectrum, and integrating with other open standards using OFDMA on the downlink (DL) , SC-FDMA on the uplink (UL) , and multiple-input multiple-output (MIMO) antenna technology.
  • a method of wireless communication may be performed by a mobile device.
  • the method may include receiving, via a first cell, a radio resource control (RRC) connection reconfiguration message that includes configuration information for accessing a single cell multicast traffic channel (SC-MTCH) , configured on a second cell, that delivers data for a single cell point-to-multipoint (SC-PTM) service that the mobile device is configured to receive.
  • RRC radio resource control
  • SC-MTCH single cell multicast traffic channel
  • SC-PTM single cell point-to-multipoint
  • the method may include performing a handover to the second cell.
  • the method may include receiving the SC-PTM service via the SC-MTCH on the second cell based at least in part on the configuration information included in the RRC connection reconfiguration message.
  • a mobile device may include one or more processors and a memory coupled to the one or more processors.
  • the one or more processors may be configured to receive, via a first cell, a radio resource control (RRC) connection reconfiguration message that includes configuration information for accessing a single cell multicast traffic channel (SC-MTCH) , configured on a second cell, that delivers data for a single cell point-to-multipoint (SC-PTM) service that the mobile device is configured to receive.
  • RRC radio resource control
  • SC-MTCH single cell multicast traffic channel
  • SC-PTM single cell point-to-multipoint
  • the one or more processors may be configured to perform a handover to the second cell.
  • the one or more processors may be configured to receive the SC-PTM service via the SC-MTCH on the second cell based at least in part on the configuration information included in the RRC connection reconfiguration message.
  • a method of wireless communication may be performed by a base station.
  • the method may include identifying a single cell point-to-multipoint (SC-PTM) service being provided to a mobile device via a first cell of the base station.
  • the method may include identifying a second cell that is configured to provide the SC-PTM service.
  • the method may include transmitting, in connection with a handover of the mobile device from the first cell to the second cell, a radio resource control (RRC) connection reconfiguration message to the mobile device that includes configuration information for accessing a single cell multicast traffic channel (SC-MTCH) , configured on the second cell, that delivers data for the SC-PTM service.
  • RRC radio resource control
  • a base station may include one or more processors and a memory coupled to the one or more processors.
  • the one or more processors may be configured to identify a single cell point-to-multipoint (SC-PTM) service being provided to a mobile device via a first cell of the base station.
  • the one or more processors may be configured to identify a second cell that is configured to provide the SC-PTM service.
  • the one or more processors may be configured to transmit, in connection with a handover of the mobile device from the first cell to the second cell, a radio resource control (RRC) connection reconfiguration message to the mobile device that includes configuration information for accessing a single cell multicast traffic channel (SC-MTCH) , configured on the second cell, that delivers data for the SC-PTM service.
  • RRC radio resource control
  • Fig. 1 is a diagram illustrating an example deployment in which multiple wireless networks have overlapping coverage, in accordance with various aspects of the present disclosure.
  • Fig. 2 is a diagram illustrating an example access network in an LTE network architecture, in accordance with various aspects of the present disclosure.
  • Fig. 3 is a diagram illustrating an example of a downlink frame structure in LTE, in accordance with various aspects of the present disclosure.
  • Fig. 4 is a diagram illustrating an example of an uplink frame structure in LTE, in accordance with various aspects of the present disclosure.
  • Fig. 5 is a diagram illustrating an example of a radio protocol architecture for a user plane and a control plane in LTE, in accordance with various aspects of the present disclosure.
  • Fig. 6 is a diagram illustrating example components of an evolved Node B and a user equipment in an access network, in accordance with various aspects of the present disclosure.
  • Fig. 7 is a diagram illustrating an example of SC-PTM configuration in handover signaling for service continuity, in accordance with various aspects of the present disclosure.
  • Fig. 8 is a diagram illustrating another example of SC-PTM configuration in handover signaling for service continuity, in accordance with various aspects of the present disclosure.
  • Fig. 9 is a diagram illustrating an example process performed, for example, by a mobile device, in accordance with various aspects of the present disclosure.
  • Fig. 10 is a diagram illustrating an example process performed, for example, by a base station, in accordance with various aspects of the present disclosure.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single carrier FDMA
  • a CDMA network may implement a radio access technology (RAT) such as universal terrestrial radio access (UTRA) , CDMA2000, and/or the like.
  • RAT radio access technology
  • UTRA may include wideband CDMA (WCDMA) and/or other variants of CDMA.
  • CDMA2000 may include Interim Standard (IS) -2000, IS-95 and IS-856 standards.
  • IS-2000 may also be referred to as 1x radio transmission technology (1xRTT) , CDMA2000 1X, and/or the like.
  • a TDMA network may implement a RAT such as global system for mobile communications (GSM) , enhanced data rates for GSM evolution (EDGE) , or GSM/EDGE radio access network (GERAN) .
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GERAN GSM/EDGE radio access network
  • An OFDMA network may implement a RAT such as evolved UTRA (E-UTRA) , ultra mobile broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, and/or the like.
  • E-UTRA evolved UTRA
  • UMB ultra mobile broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • UTRA and E-UTRA may be part of the universal mobile telecommunication system (UMTS) .
  • 3GPP long-term evolution (LTE) and LTE- Advanced (LTE-A) are example releases of UMTS that use E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink.
  • UTRA, E-UTRA, UMTS, LTE, LTE-Aand GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • the techniques described herein may be used for the wireless networks and RATs mentioned above as well as other wireless networks and RATs.
  • Fig. 1 is a diagram illustrating an example deployment 100 in which multiple wireless networks have overlapping coverage, in accordance with various aspects of the present disclosure.
  • example deployment 100 may include an evolved universal terrestrial radio access network (E-UTRAN) 105, which may include one or more evolved Node Bs (eNBs) 110, and which may communicate with other devices or networks via a serving gateway (SGW) 115 and/or a mobility management entity (MME) 120.
  • E-UTRAN evolved universal terrestrial radio access network
  • eNBs evolved Node Bs
  • MME mobility management entity
  • example deployment 100 may include a radio access network (RAN) 125, which may include one or more base stations 130, and which may communicate with other devices or networks via a mobile switching center (MSC) 135 and/or an inter-working function (IWF) 140.
  • example deployment 100 may include one or more user equipment (UEs) 145 capable of communicating via E-UTRAN 105 and/or RAN 125.
  • UEs user equipment
  • E-UTRAN 105 may support, for example, LTE or another type of RAT.
  • E-UTRAN 105 may include eNBs 110 and other network entities that can support wireless communication for UEs 145.
  • Each eNB 110 may provide communication coverage for a particular geographic area.
  • the term “cell” may refer to a coverage area of eNB 110 and/or an eNB subsystem serving the coverage area, on a specific frequency channel.
  • SGW 115 may communicate with E-UTRAN 105 and may perform various functions, such as packet routing and forwarding, mobility anchoring, packet buffering, initiation of network-triggered services, and/or the like.
  • MME 120 may communicate with E-UTRAN 105 and SGW 115 and may perform various functions, such as mobility management, bearer management, distribution of paging messages, security control, authentication, gateway selection, and/or the like, for UEs 145 located within a geographic region served by MME 120 of E-UTRAN 105.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • RAN 125 may support, for example, GSM or another type of RAT.
  • RAN 125 may include base stations 130 and other network entities that can support wireless communication for UEs 145.
  • MSC 135 may communicate with RAN 125 and may perform various functions, such as voice services, routing for circuit-switched calls, and mobility management for UEs 145 located within a geographic region served by MSC 135 of RAN 125.
  • IWF 140 may facilitate communication between MME 120 and MSC 135 (e.g., when E-UTRAN 105 and RAN 125 use different RATs) .
  • MME 120 may communicate directly with an MME that interfaces with RAN 125, for example, without IWF 140 (e.g., when E-UTRAN 105 and RAN 125 use a same RAT) .
  • E-UTRAN 105 and RAN 125 may use the same frequency and/or the same RAT to communicate with UE 145.
  • E-UTRAN 105 and RAN 125 may use different frequencies and/or RATs to communicate with UEs 145.
  • the term base station is not tied to any particular RAT, and may refer to an eNB (e.g., of an LTE network) or another type of base station associated with a different type of RAT.
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular RAT and may operate on one or more frequencies.
  • a RAT may also be referred to as a radio technology, an air interface, etc.
  • a frequency or frequency ranges may also be referred to as a carrier, a frequency channel, and/or the like.
  • Each frequency or frequency range may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • UE 145 may be stationary or mobile and may also be referred to as a mobile station, a terminal, an access terminal, a wireless communication device, a subscriber unit, a station, and/or the like.
  • UE 145 may be a cellular phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • UE 145 may search for wireless networks from which UE 145 can receive communication services. If UE 145 detects more than one wireless network, then a wireless network with the highest priority may be selected to serve UE 145 and may be referred to as the serving network. UE 145 may perform registration with the serving network, if necessary. UE 145 may then operate in a connected mode to actively communicate with the serving network. Alternatively, UE 145 may operate in an idle mode and camp on the serving network if active communication is not required by UE 145.
  • UE 145 may operate in the idle mode as follows. UE 145 may identify all frequencies/RATs on which it is able to find a “suitable” cell in a normal scenario or an “acceptable” cell in an emergency scenario, where “suitable” and “acceptable” are specified in the LTE standards. UE 145 may then camp on the frequency/RAT with the highest priority among all identified frequencies/RATs. UE 145 may remain camped on this frequency/RAT until either (i) the frequency/RAT is no longer available at a predetermined threshold or (ii) another frequency/RAT with a higher priority reaches this threshold.
  • UE 145 may receive a neighbor list when operating in the idle mode, such as a neighbor list included in a system information block type 5 (SIB 5) provided by an eNB of a RAT on which UE 145 is camped. Additionally, or alternatively, UE 145 may generate a neighbor list.
  • a neighbor list may include information identifying one or more frequencies, at which one or more RATs may be accessed, priority information associated with the one or more RATs, and/or the like.
  • the number and arrangement of devices and networks shown in Fig. 1 are provided as an example. In practice, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown in Fig. 1. Furthermore, two or more devices shown in Fig. 1 may be implemented within a single device, or a single device shown in Fig. 1 may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) shown in Fig. 1 may perform one or more functions described as being performed by another set of devices shown in Fig. 1.
  • Fig. 2 is a diagram illustrating an example access network 200 in an LTE network architecture, in accordance with various aspects of the present disclosure.
  • access network 200 may include one or more eNBs 210 (also referred to as “base stations” hereinafter) that serve a corresponding set of cellular regions (cells) 220, one or more low power eNBs 230 that serve a corresponding set of cells 240, and a set of UEs 250.
  • eNBs 210 also referred to as “base stations” hereinafter
  • base stations low power eNBs 230 that serve a corresponding set of cells 240
  • UEs 250 a set of UEs 250.
  • Each eNB 210 may be assigned to a respective cell 220 and may be configured to provide an access point to a RAN.
  • eNB 110, 210 may provide an access point for UE 145, 250 to E-UTRAN 105 (e.g., eNB 210 may correspond to eNB 110, shown in Fig. 1) or may provide an access point for UE 145, 250 to RAN 125 (e.g., eNB 210 may correspond to base station 130, shown in Fig. 1) .
  • the terms base station and eNB may be used interchangeably, and a base station, as used herein, is not tied to any particular RAT.
  • UE 145, 250 may correspond to UE 145, shown in Fig. 1.
  • the eNBs 210 may perform radio related functions including radio bearer control, admission control, mobility control, scheduling, security, and network connectivity (e.g., to SGW 115) .
  • one or more low power eNBs 230 may serve respective cells 240, which may overlap with one or more cells 220 served by eNBs 210.
  • the eNBs 230 may correspond to eNB 110 associated with E-UTRAN 105 and/or base station 130 associated with RAN 125, shown in Fig. 1.
  • a low power eNB 230 may be referred to as a remote radio head (RRH) .
  • the low power eNB 230 may include a femto cell eNB (e.g., home eNB (HeNB) ) , a pico cell eNB, a micro cell eNB, and/or the like.
  • HeNB home eNB
  • a modulation and multiple access scheme employed by access network 200 may vary depending on the particular telecommunications standard being deployed.
  • OFDM is used on the downlink (DL)
  • SC-FDMA is used on the uplink (UL) to support both frequency division duplexing (FDD) and time division duplexing (TDD) .
  • FDD frequency division duplexing
  • TDD time division duplexing
  • the various concepts presented herein are well suited for LTE applications. However, these concepts may be readily extended to other telecommunication standards employing other modulation and multiple access techniques. By way of example, these concepts may be extended to Evolution-Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB) .
  • EV-DO Evolution-Data Optimized
  • UMB Ultra Mobile Broadband
  • EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations.
  • 3GPP2 3rd Generation Partnership Project 2
  • these concepts may also be extended to UTRA employing WCDMA and other variants of CDMA (e.g., such as TD-SCDMA, GSM employing TDMA, E-UTRA, and/or the like) , UMB, IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM employing OFDMA, and/or the like.
  • WCDMA Wideband Code Division Multiple Access
  • UMB Universal Mobile Broadband Code Division Multiple Access 2000
  • CDMA2000 and UMB are described in documents from the 3GPP2 organization.
  • the actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.
  • the eNBs 210 may have multiple antennas supporting MIMO technology.
  • MIMO technology enables eNBs 210 to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity.
  • Spatial multiplexing may be used to transmit different streams of data simultaneously on the same frequency.
  • the data streams may be transmitted to a single UE 145, 250 to increase the data rate or to multiple UEs 250 to increase the overall system capacity. This may be achieved by spatially precoding each data stream (e.g., applying a scaling of an amplitude and a phase) and then transmitting each spatially precoded stream through multiple transmit antennas on the DL.
  • the spatially precoded data streams arrive at the UE (s) 250 with different spatial signatures, which enables each of the UE (s) 250 to recover the one or more data streams destined for that UE 145, 250.
  • each UE 145, 250 transmits a spatially precoded data stream, which enables eNBs 210 to identify the source of each spatially precoded data stream.
  • Beamforming may be used to focus the transmission energy in one or more directions. This may be achieved by spatially precoding the data for transmission through multiple antennas. To achieve good coverage at the edges of the cell, a single stream beamforming transmission may be used in combination with transmit diversity.
  • OFDM is a spread-spectrum technique that modulates data over a number of subcarriers within an OFDM symbol.
  • the subcarriers are spaced apart at precise frequencies. The spacing provides “orthogonality” that enables a receiver to recover the data from the subcarriers.
  • a guard interval e.g., cyclic prefix
  • the UL may use SC-FDMA in the form of a DFT-spread OFDM signal to compensate for high peak-to-average power ratio (PAPR) .
  • PAPR peak-to-average power ratio
  • the number and arrangement of devices and cells shown in Fig. 2 are provided as an example. In practice, there may be additional devices and/or cells, fewer devices and/or cells, different devices and/or cells, or differently arranged devices and/or cells than those shown in Fig. 2. Furthermore, two or more devices shown in Fig. 2 may be implemented within a single device, or a single device shown in Fig. 2 may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) shown in Fig. 2 may perform one or more functions described as being performed by another set of devices shown in Fig. 2.
  • Fig. 3 is a diagram illustrating an example 300 of a downlink (DL) frame structure in LTE, in accordance with various aspects of the present disclosure.
  • a frame e.g., of 10 ms
  • Each sub-frame may include two consecutive time slots.
  • a resource grid may be used to represent two time slots, each time slot including a resource block (RB) .
  • the resource grid is divided into multiple resource elements.
  • a resource block includes 12 consecutive subcarriers in the frequency domain and, for a normal cyclic prefix in each OFDM symbol, 7 consecutive OFDM symbols in the time domain, or 84 resource elements.
  • a resource block For an extended cyclic prefix, a resource block includes 6 consecutive OFDM symbols in the time domain and has 72 resource elements. Some of the resource elements, as indicated as R 310 and R 320, include DL reference signals (DL-RS) .
  • the DL-RS include Cell-specific RS (CRS) (also sometimes called common RS) 310 and UE-specific RS (UE-RS) 320.
  • UE-RS 320 are transmitted only on the resource blocks upon which the corresponding physical DL shared channel (PDSCH) is mapped.
  • the number of bits carried by each resource element depends on the modulation scheme. Thus, the more resource blocks that a UE receives and the higher the modulation scheme, the higher the data rate for the UE.
  • an eNB may send a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) for each cell in the eNB.
  • the primary and secondary synchronization signals may be sent in symbol periods 6 and 5, respectively, in each of subframes 0 and 5 of each radio frame with the normal cyclic prefix (CP) .
  • the synchronization signals may be used by UEs for cell detection and acquisition.
  • the eNB may send a Physical Broadcast Channel (PBCH) in symbol periods 0 to 3 in slot 1 of subframe 0.
  • PBCH Physical Broadcast Channel
  • the eNB may send a Physical Control Format Indicator Channel (PCFICH) in the first symbol period of each subframe.
  • the PCFICH may convey the number of symbol periods (M) used for control channels, where M may be equal to 1, 2 or 3 and may change from subframe to subframe. M may also be equal to 4 for a small system bandwidth, e.g., with less than 10 resource blocks.
  • the eNB may send a Physical HARQ Indicator Channel (PHICH) and a Physical Downlink Control Channel (PDCCH) in the first M symbol periods of each subframe.
  • the PHICH may carry information to support hybrid automatic repeat request (HARQ) .
  • the PDCCH may carry information on resource allocation for UEs and control information for downlink channels.
  • the eNB may send a Physical Downlink Shared Channel (PDSCH) in the remaining symbol periods of each subframe.
  • the PDSCH may carry data for UEs scheduled for data transmission on the downlink.
  • the eNB may send the PSS, SSS, and PBCH in the center 1.08 MHz of the system bandwidth used by the eNB.
  • the eNB may send the PCFICH and PHICH across the entire system bandwidth in each symbol period in which these channels are sent.
  • the eNB may send the PDCCH to groups of UEs in certain portions of the system bandwidth.
  • the eNB may send the PDSCH to specific UEs in specific portions of the system bandwidth.
  • the eNB may send the PSS, SSS, PBCH, PCFICH, and PHICH in a broadcast manner to all UEs, may send the PDCCH in a unicast manner to specific UEs, and may also send the PDSCH in a unicast manner to specific UEs.
  • Each resource element may cover one subcarrier in one symbol period and may be used to send one modulation symbol, which may be a real or complex value.
  • Resource elements not used for a reference signal in each symbol period may be arranged into resource element groups (REGs) .
  • Each REG may include four resource elements in one symbol period.
  • the PCFICH may occupy four REGs, which may be spaced approximately equally across frequency, in symbol period 0.
  • the PHICH may occupy three REGs, which may be spread across frequency, in one or more configurable symbol periods. For example, the three REGs for the PHICH may all belong in symbol period 0 or may be spread in symbol periods 0, 1, and 2.
  • the PDCCH may occupy 9, 18, 36, or 72 REGs, which may be selected from the available REGs, in the first M symbol periods, for example. Only certain combinations of REGs may be allowed for the PDCCH.
  • a UE may know the specific REGs used for the PHICH and the PCFICH.
  • the UE may search different combinations of REGs for the PDCCH.
  • the number of combinations to search is typically less than the number of allowed combinations for the PDCCH.
  • An eNB may send the PDCCH to the UE in any of the combinations that the UE will search.
  • Fig. 3 is provided as an example. Other examples are possible and may differ from what was described above in connection with Fig. 3.
  • Fig. 4 is a diagram illustrating an example 400 of an uplink (UL) frame structure in LTE, in accordance with various aspects of the present disclosure.
  • the available resource blocks for the UL may be partitioned into a data section and a control section.
  • the control section may be formed at the two edges of the system bandwidth and may have a configurable size.
  • the resource blocks in the control section may be assigned to UEs for transmission of control information.
  • the data section may include all resource blocks not included in the control section.
  • the UL frame structure results in the data section including contiguous subcarriers, which may allow a single UE to be assigned all of the contiguous subcarriers in the data section.
  • a UE may be assigned resource blocks 410a, 410b in the control section to transmit control information to an eNB.
  • the UE may also be assigned resource blocks 420a, 420b in the data section to transmit data to the eNB.
  • the UE may transmit control information in a physical UL control channel (PUCCH) on the assigned resource blocks in the control section.
  • the UE may transmit only data or both data and control information in a physical UL shared channel (PUSCH) on the assigned resource blocks in the data section.
  • a UL transmission may span both slots of a subframe and may hop across frequencies.
  • a set of resource blocks may be used to perform initial system access and achieve UL synchronization in a physical random access channel (PRACH) 430.
  • the PRACH 430 carries a random sequence and cannot carry any UL data/signaling.
  • Each random access preamble occupies a bandwidth corresponding to six consecutive resource blocks.
  • the starting frequency is specified by the network. That is, the transmission of the random access preamble is restricted to certain time and frequency resources. There is no frequency hopping for the PRACH.
  • the PRACH attempt is carried in a single subframe (e.g., of 1 ms) or in a sequence of few contiguous subframes and a UE can make only a single PRACH attempt per frame (e.g., of 10 ms) .
  • Fig. 4 is provided as an example. Other examples are possible and may differ from what was described above in connection with Fig. 4.
  • Fig. 5 is a diagram illustrating an example 500 of a radio protocol architecture for a user plane and a control plane in LTE, in accordance with various aspects of the present disclosure.
  • the radio protocol architecture for the UE and the eNB is shown with three layers: Layer 1, Layer 2, and Layer 3.
  • Layer 1 (L1 layer) is the lowest layer and implements various physical layer signal processing functions.
  • the L1 layer will be referred to herein as the physical layer 510.
  • Layer 2 (L2 layer) 520 is above the physical layer 510 and is responsible for the link between the UE and eNB over the physical layer 510.
  • the L2 layer 520 includes, for example, a media access control (MAC) sublayer 530, a radio link control (RLC) sublayer 540, and a packet data convergence protocol (PDCP) 550 sublayer, which are terminated at the eNB on the network side.
  • MAC media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • the UE may have several upper layers above the L2 layer 520 including a network layer (e.g., IP layer) that is terminated at a packet data network (PDN) gateway on the network side, and an application layer that is terminated at the other end of the connection (e.g., far end UE, server, etc. ) .
  • IP layer e.g., IP layer
  • PDN packet data network gateway
  • the PDCP sublayer 550 provides retransmission of lost data in handover.
  • the PDCP sublayer 550 also provides header compression for upper layer data packets to reduce radio transmission overhead, security by ciphering the data packets, and handover support for UEs between eNBs.
  • the RLC sublayer 540 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to hybrid automatic repeat request (HARQ) .
  • HARQ hybrid automatic repeat request
  • the MAC sublayer 530 provides multiplexing between logical and transport channels.
  • the MAC sublayer 530 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs.
  • the MAC sublayer 530 is also responsible for HARQ operations.
  • the radio protocol architecture for the UE and eNB is substantially the same for the physical layer 510 and the L2 layer 520 with the exception that there is no header compression function for the control plane.
  • the control plane also includes a radio resource control (RRC) sublayer 560 in Layer 3 (L3 layer) .
  • the RRC sublayer 560 is responsible for obtaining radio resources (i.e., radio bearers) and for configuring the lower layers using RRC signaling between the eNB and the UE.
  • Fig. 5 is provided as an example. Other examples are possible and may differ from what was described above in connection with Fig. 5.
  • Fig. 6 is a diagram illustrating example components 600 of eNB 110, 210, 230 and UE 145, 250 in an access network, in accordance with various aspects of the present disclosure.
  • eNB 110, 210, 230 may include a controller/processor 605, a TX processor 610, a channel estimator 615, an antenna 620, a transmitter 625TX, a receiver 625RX, an RX processor 630, and a memory 635.
  • Fig. 6 is a diagram illustrating example components 600 of eNB 110, 210, 230 and UE 145, 250 in an access network, in accordance with various aspects of the present disclosure.
  • eNB 110, 210, 230 may include a controller/processor 605, a TX processor 610, a channel estimator 615, an antenna 620, a transmitter 625TX, a receiver 625RX, an RX processor 630, and a memory 635.
  • Fig. 6 is a diagram illustrating
  • UE 145, 250 may include a receiver RX, for example, of a transceiver TX/RX 640, a transmitter TX, for example, of a transceiver TX/RX 640, an antenna 645, an RX processor 650, a channel estimator 655, a controller/processor 660, a memory 665, a data sink 670, a data source 675, and a TX processor 680.
  • a receiver RX for example, of a transceiver TX/RX 640
  • a transmitter TX for example, of a transceiver TX/RX 640
  • an antenna 645 for example, an RX processor 650, a channel estimator 655, a controller/processor 660, a memory 665, a data sink 670, a data source 675, and a TX processor 680.
  • controller/processor 605 implements the functionality of the L2 layer.
  • the controller/processor 605 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations to the UE 145, 250 based, at least in part, on various priority metrics.
  • the controller/processor 605 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the UE 145, 250.
  • the TX processor 610 implements various signal processing functions for the L1 layer (e.g., physical layer) .
  • the signal processing functions includes coding and interleaving to facilitate forward error correction (FEC) at the UE 145, 250 and mapping to signal constellations based, at least in part, on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) .
  • FEC forward error correction
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
  • the OFDM stream is spatially precoded to produce multiple spatial streams.
  • Channel estimates from a channel estimator 615 may be used to determine the coding and modulation scheme, as well as for spatial processing.
  • the channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 145, 250.
  • Each spatial stream is then provided to a different antenna 620 via a separate transmitter TX, for example, of transceiver TX/RX 625. Each such transmitter TX modulates an RF carrier with a respective spatial stream for transmission.
  • each receiver RX for example, of a transceiver TX/RX 640 receives a signal through its respective antenna 645.
  • Each such receiver RX recovers information modulated onto an RF carrier and provides the information to the receiver (RX) processor 650.
  • the RX processor 650 implements various signal processing functions of the L1 layer.
  • the RX processor 650 performs spatial processing on the information to recover any spatial streams destined for the UE 145, 250. If multiple spatial streams are destined for the UE 145, 250, the spatial streams may be combined by the RX processor 650 into a single OFDM symbol stream.
  • the RX processor 650 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) .
  • the frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal.
  • the symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB 110, 210, 230. These soft decisions may be based, at least in part, on channel estimates computed by the channel estimator 655.
  • the soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 110, 210, 230 on the physical channel.
  • the data and control signals are then provided to the controller/processor 660.
  • the controller/processor 660 implements the L2 layer.
  • the controller/processor 660 can be associated with a memory 665 that stores program codes and data.
  • the memory 665 may include a non-transitory computer-readable medium.
  • the controller/processor 660 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network.
  • the upper layer packets are then provided to a data sink 670, which represents all the protocol layers above the L2 layer.
  • Various control signals may also be provided to the data sink 670 for L3 processing.
  • the controller/processor 660 is also responsible for error detection using an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support HARQ operations.
  • ACK acknowledgement
  • NACK negative acknowledgement
  • a data source 675 is used to provide upper layer packets to the controller/processor 660.
  • the data source 675 represents all protocol layers above the L2 layer.
  • the controller/processor 660 implements the L2 layer for the user plane and the control plane by providing header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based, at least in part, on radio resource allocations by the eNB 110, 210, 230.
  • the controller/processor 660 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the eNB 110, 210, 230.
  • Channel estimates derived by a channel estimator 655 from a reference signal or feedback transmitted by the eNB 110, 210, 230 may be used by the TX processor 680 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the TX processor 680 are provided to different antenna 645 via separate transmitters TX, for example, of transceivers TX/RX 640. Each transmitter TX, for example, of transceiver TX/RX 640 modulates an RF carrier with a respective spatial stream for transmission.
  • the UL transmission is processed at the eNB 110, 210, 230 in a manner similar to that described in connection with the receiver function at the UE 145, 250.
  • Each receiver RX for example, of transceiver TX/RX 625 receives a signal through its respective antenna 620.
  • Each receiver RX for example, of transceiver TX/RX 625 recovers information modulated onto an RF carrier and provides the information to a RX processor 630.
  • the RX processor 630 may implement the L1 layer.
  • the controller/processor 605 implements the L2 layer.
  • the controller/processor 605 can be associated with a memory 635 that stores program code and data.
  • the memory 635 may be referred to as a computer-readable medium.
  • the control/processor 605 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 145, 250.
  • Upper layer packets from the controller/processor 605 may be provided to the core network.
  • the controller/processor 605 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • One or more components of UE 145, 250 may be configured to perform SC-PTM configuration in handover signaling for service continuity, as described in more detail elsewhere herein.
  • the controller/processor 660 and/or other processors and modules of UE 145, 250 may perform or direct operations of, for example, process 900 of Fig. 9 and/or other processes as described herein.
  • one or more components of eNB 110, 210, 230 may be configured to perform SC-PTM configuration in handover signaling for service continuity, as described in more detail elsewhere herein.
  • the controller/processor 605 and/or other processors and modules of eNB 110, 210, 230 may perform or direct operations of, for example, process 1000 of Fig. 10 and/or other processes as described herein.
  • Fig. 6 The number and arrangement of components shown in Fig. 6 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 6. Furthermore, two or more components shown in Fig. 6 may be implemented within a single component, or a single component shown in Fig. 6 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of components (e.g., one or more components) shown in Fig. 6 may perform one or more functions described as being performed by another set of components shown in Fig. 6.
  • a mobile device which may correspond to UE 145, 250, may subscribe to a single cell point-to-multipoint (SC-PTM) service to receive, for example, evolved multimedia broadcast multicast service (eMBMS) communications.
  • SC-PTM single cell point-to-multipoint
  • eMBMS communications are sent on the PDSCH.
  • MBSFN multicast-broadcast single-frequency network
  • different cells that provide eMBMS communications via SC-PTM may have different configurations.
  • the mobile device needs downlink grants from the PDCCH in order to access SC-PTM information on the PDSCH.
  • the PDSCH includes a logical channel for SC-PTM data traffic, referred to as the single cell multicast traffic channel (SC-MTCH) , and a logical channel for SC-PTM control information, referred to as the single cell multicast control channel (SC-MCCH) .
  • the mobile device uses a group specific radio network temporary identifier (G-RNTI) and a single cell RNTI (SC-RNTI) to identify downlink grants on the PDCCH for communications on the SC-MTCH and the SC-MCCH, respectively.
  • G-RNTI group specific radio network temporary identifier
  • SC-RNTI single cell RNTI
  • the mobile device needs cell-specific information and processing, which must be accommodated during handover to ensure a good user experience.
  • Techniques described herein assist with providing SC-PTM control information during handover, thereby improving the user experience (e.g., by reducing latency, by ensuring that an SC-PTM service is supported by a target cell, and/or the like) .
  • Fig. 7 is a diagram illustrating an example 700 of SC-PTM configuration in handover signaling for service continuity, in accordance with various aspects of the present disclosure.
  • example 700 may include a mobile device 705 (e.g., a UE, such as UE 145, 250) , a first cell 710-1 (e.g., cell 220, 240 of an eNB, such as eNB 110, 210, 230) , and a second cell 710-2 (e.g., cell 220, 240 of an eNB, such as eNB 110, 210, 230) .
  • a mobile device 705 e.g., a UE, such as UE 145, 250
  • a first cell 710-1 e.g., cell 220, 240 of an eNB, such as eNB 110, 210, 230
  • second cell 710-2 e.g., cell 220, 240 of an eNB, such as eNB 110, 210
  • the mobile device 705 may transmit an MBMS Interest Indicator (MII) on the first cell 710-1.
  • the MII may include a temporary mobile group identifier (TMGI) , shown as TMGI1, that identifies an SC-PTM service to which the mobile device 705 is to be subscribed.
  • TMGI temporary mobile group identifier
  • the mobile device 705 may obtain scheduling information from a system information block type 20 (SIB20) on the first cell 710-1.
  • SIB20 system information block type 20
  • the scheduling information from SIB20 may indicate a schedule for the SC-MCCH.
  • the mobile device 705 may acquire the SC-MCCH by monitoring the PDCCH for downlink control information (DCI) messages using the schedule and an SC-RNTI.
  • DCI message for the SC-MCCH may include a downlink grant for accessing the SC-MCCH on the PDSCH.
  • the mobile device 705 may access the SC-MCCH to obtain SC-PTM configuration information (e.g., in an SCPTM Configuration message) .
  • the SC-PTM configuration information may include scheduling information for acquiring the SC-MTCH and accessing one or more SC-PTM services (e.g., all offered SC-PTM services on the SC-MTCH at first cell 710-1) .
  • the scheduling information may indicate a schedule associated with transmission of the SC-MTCH.
  • Different SC-PTM services may be identified by different TMGIs, and the mobile device 705 may use a TMGI to subscribe to a corresponding SC-PTM service, such as by transmitting an MII that includes the TMGI.
  • the mobile device 705 may transmit an MII that includes TMGI1 on the first cell 710-1, as shown.
  • the mobile device 705 may receive the SC-PTM service, identified by TMGI1, using the SC-MTCH on the first cell 710-1.
  • different SC-PTM services may be associated with different group specific RNTIs (G-RNTIs) .
  • G-RNTIs group specific RNTIs
  • the mobile device 705 may monitor the PDCCH for DCI messages using a G-RNTI for the specific SC-PTM service and scheduling information for the SC-MTCH.
  • a DCI message for the SC-MTCH may include one or more downlink grants for accessing the SC-PTM service on the SC-MTCH of the PDSCH.
  • the mobile device 705 may use the downlink grants to receive the SC-PTM service.
  • the mobile device 705 may receive the SC-PTM service identified by TMGI1 on the SC-MTCH, as shown.
  • the mobile device 705 and/or the first cell 710-1 may trigger a handover of the mobile device 705 with service continuity for the SC-PTM service.
  • the mobile device 705 may periodically transmit measurement reports to the eNB, which may trigger a handover when one or more conditions are satisfied.
  • the handover may be an intra-eNB handover (e.g., from one cell to a different cell of the same eNB) and/or an inter-eNB handover (e.g., from a cell of one eNB to a cell of a different eNB) .
  • the eNB may identify an SC-PTM service being provided to the mobile device 705 on the first cell 710-1. For example, the eNB may identify a TMGI of the SC-PTM service accessed by mobile device 705 at first cell 710-1. The eNB may identify a second cell that is configured to provide the SC-PTM service. For example, the eNB may identify the second cell 710-2 that is associated with the same TMGI used to provide the SC-PTM service on the first cell 710-1. The eNB may determine configuration information for accessing the SC-MTCH, on the second cell 710-2, that delivers data for the SC-PTM service. The eNB may use this configuration information to facilitate service continuity for SC-PTM during a handover of the mobile device 705, as described below.
  • the eNB may transmit an RRC connection reconfiguration message that includes the configuration information for service continuity at the second cell 710-2 (e.g., shown as service continuity info) .
  • the configuration information may include information for accessing the SC-MTCH, configured on the second cell 710-2, that delivers data for the SC-PTM service that the mobile device 705 is already configured to receive on the first cell 710-1.
  • the configuration information may include a G-RNTI for the SC-PTM service on the second cell 710-2, scheduling information for the SC-PTM service on the second cell 710-2, a TMGI for the SC-PTM service (e.g., a TMGI which is the same on the first cell 710-1 and the second cell 710-2) , and/or the like.
  • the scheduling information may include, for example, information that indicates whether SC-MTCH can be scheduled in any subframe, information regarding a discontinuous reception (DRX) cycle for the SC-MTCH (e.g., an on duration timer, a DRX inactivity timer, a scheduling cycle, an offset, etc. ) .
  • DRX discontinuous reception
  • a configuration of the SC-MTCH on the second cell 710-2 may be the same as a configuration of the SC-MTCH on the first cell 710-1.
  • the configuration information may indicate that the configurations of the SC-MTCH are the same on the first cell 710-1 and the second cell 710-2.
  • a configuration of the SC-MTCH on the second cell 710-2 may be different from a configuration of the SC-MTCH on the first cell 710-1.
  • a portion of the configuration of the SC-MTCH on the second cell 710-2 may be the same as a corresponding portion of the configuration of the SC-MTCH on the first cell 710-1.
  • the configuration information may indicate a portion of a configuration of the SC-MTCH that is common to the first cell 710-1 and the second cell 710-2.
  • the eNB may provide specific configuration information for accessing the specific SC-PTM services to which the mobile device 705 is subscribed (e.g., the SC-PTM services being provided to the mobile device 705 and/or received by the mobile device 705) .
  • the mobile device 705 may be receiving a single SC-PTM service on the first cell 710-1, which may be, for example, a primary cell (PCell) or a secondary cell (SCell) .
  • the eNB may provide only the specific configuration information for accessing the single SC-PTM service at the second cell 710-2.
  • the configuration information may relate to accessing the service identified by TMGI1 at second cell 710-2 and may omit information relating to additional broadcast services that might be available at second cell 710-2.
  • the mobile device 705 may be receiving multiple SC-PTM services (e.g., on the PCell and the SCell, on multiple SCells, etc. ) .
  • the eNB may provide only the specific configuration information for accessing the multiple SC-PTM services that the mobile device 705 is receiving.
  • the specific configuration information may be a subset of the full configuration information provided on the SC-MCCH for accessing available SC-PTM services.
  • the mobile device 705 may obtain the full configuration information provided on the SC-MCCH by obtaining SIB20 information and the SC-MCCH on the second cell 710-2, as described in more detail below in connection with Fig. 8.
  • the eNB may provide specific configuration information for accessing the specific SC-PTM services being received by the mobile device 705, and may also provide SC-MCCH configuration information for accessing the SC-MCCH on the second cell 710-2 (e.g., to obtain full configuration information for accessing available SC-PTM services) .
  • the SC-MCCH configuration information may indicate, for example, an SC-MCCH modification period, an SC-MCCH duration, an SC-MCCH offset, an SC-MCCH first subframe, and SC-MCCH repetition period, and/or the like, which is typically signaled in SIB20.
  • the mobile device 705 may perform a handover to the second cell 710-2, and may stop reception of eMBMS communications while performing the handover.
  • the mobile device 705 may improve the user experience by providing service continuity for SC-PTM services during handover (e.g., by reducing latency, by ensuring that an SC-PTM service is supported by a target cell, by pre- configuring the mobile device 705 to receive SC-PTM services after handover, and/or the like) .
  • the mobile device 705 may receive a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) for the second cell 710-2, which may be used by the mobile device 705 for detection and acquisition of the second cell 710-2.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • the mobile device 705 may obtain a Physical Broadcast Channel (PBCH) for the second cell 710-2, which may carry a master information block for the second cell 710-2 (e.g., a system frame number) .
  • PBCH Physical Broadcast Channel
  • the mobile device 705 may receive the SC-PTM service (e.g., TMGI1) via the SC-MTCH of the second cell 710-2.
  • the mobile device 705 may use the specific configuration information for the SC-PTM service (e.g., a G-RNTI and scheduling information for the SC-PTM service) to obtain the SC-PTM service via the SC-MTCH and resume eMBMS communications.
  • the mobile device may use the G-RNTI and/or the scheduling information to identify a grant provided via the PDCCH on the second cell.
  • the mobile device may use the grant to obtain data for the SC-PTM service via the PDSCH of the second cell (e.g., on the SC-MTCH, which is a logical channel of the PDSCH) . Because the mobile device 705 received the specific configuration information in the RRC connection reconfiguration message prior to performing handover, the mobile device 705 need not wait to obtain SIB1 information for accessing SIB20, need not wait to obtain SIB20 information for accessing the SC-MCCH, and need not wait to obtain the SC-MCCH with configuration information for accessing the SC-PTM service. In this way, the mobile device 705 improves the user experience for SC-PTM services.
  • the mobile device 705 can access the SC-MCCH (e.g., to obtain updated configuration information) without waiting to obtain SIB1 information for accessing SIB20 and SIB20 information for accessing the SC-MCCH. This further improves the user experience associated with SC-PTM services.
  • Fig. 7 is provided as an example. Other examples are possible and may differ from what was described with respect to Fig. 7.
  • Fig. 8 is a diagram illustrating another example 800 of SC-PTM configuration in handover signaling for service continuity, in accordance with various aspects of the present disclosure.
  • example 800 may include a mobile device 805 (e.g., a UE, such as UE 145, 250) , a first cell 810-1 (e.g., cell 220, 240 of an eNB, such as eNB 110, 210, 230) , and a second cell 810-2 (e.g., cell 220, 240 of an eNB, such as eNB 110, 210, 230) .
  • a mobile device 805 e.g., a UE, such as UE 145, 250
  • a first cell 810-1 e.g., cell 220, 240 of an eNB, such as eNB 110, 210, 230
  • second cell 810-2 e.g., cell 220, 240 of an eNB, such as eNB 110, 210
  • the mobile device 805 may transmit an MBMS Interest Indicator (MII) on the first cell 810-1, in a similar manner as described above in connection with reference number 715 of Fig. 7.
  • MII MBMS Interest Indicator
  • the mobile device 805 may receive the SC-PTM service, identified by TMGI1, using the SC-MTCH on the first cell 810-1, in a similar manner as described above in connection with reference number 720 of Fig. 7.
  • the mobile device 705 and/or the first cell 810-1 may trigger a handover of the mobile device 805 with service continuity for the SC-PTM service, in a similar manner as described above in connection with reference number 725 of Fig. 7.
  • the eNB may transmit an RRC connection reconfiguration message that includes the configuration information (e.g., shown as service continuity info) .
  • the configuration information e.g., shown as service continuity info
  • example 700 of Fig. 7 shows an example where the RRC connection reconfiguration message includes both specific configuration information for SC-PTM service (s) being received by the mobile device and SC-MCCH configuration information for accessing the SC-MCCH on the second cell
  • example 800 of Fig. 8 shows an example where the RRC connection reconfiguration message includes only the specific configuration information for the SC-PTM service (s) being received by the mobile device.
  • the RRC connection reconfiguration message may include specific configuration information for accessing the SC-MTCH, configured on the second cell 810-2, that delivers data for the SC-PTM service that the mobile device 805 is already configured to receive on the first cell 810-1.
  • the specific configuration information may include a G-RNTI for the SC-PTM service on the second cell 810-2, scheduling information for the SC-PTM service on the second cell 810-2, a TMGI for the SC-PTM service (e.g., a TMGI which is the same on the first cell 810-1 and the second cell 810-2) , and/or the like.
  • the scheduling information may include, for example, information that indicates whether SC-MTCH can be scheduled in any subframe on the second cell 810-2, information regarding a discontinuous reception (DRX) cycle for the SC-MTCH on the second cell 810-2 (e.g., an on duration timer, a DRX inactivity timer, a scheduling cycle, an offset, etc. ) .
  • DRX discontinuous reception
  • the mobile device 705 may perform a handover to the second cell 810-2, and may stop reception of eMBMS communications while performing the handover.
  • the mobile device 805 may improve the user experience by providing service continuity for SC-PTM services during handover (e.g., by reducing latency, by ensuring that an SC-PTM service is supported by a target cell, by pre-configuring the mobile device 705 to receive SC-PTM services after handover, and/or the like) .
  • the mobile device 805 may receive a PSS, an SSS, and a PBCH on the second cell 810-2, in a similar manner as described above in connection with reference number 740 of Fig. 7.
  • the mobile device 805 may receive the SC-PTM service (e.g., TMGI1) via the SC-MTCH of the second cell 810-2 without first waiting to receive SIB1, SIB20, and the SC-MCCH, in a similar manner as described above in connection with reference number 745 of Fig. 7.
  • SC-PTM service e.g., TMGI1
  • the RRC connection reconfiguration message may not include the SC-MCCH configuration information.
  • the mobile device 805 may obtain the SC-MCCH by obtaining SIB1 (as shown by reference number 850) , obtaining SIB20 based at least in part on information included in SIB1 (as shown by reference number 855) , and obtaining the SC-MCCH based at least in part on SC-MCCH configuration information included in SIB20 (as shown by reference number 860) .
  • the mobile device 805 may obtain the SC-MTCH on the second cell 810-2 prior to obtaining SIB1, SIB20, and/or the SC-MCCH on the second cell 810-2. In some aspects, the mobile device 805 may obtain the SC-MTCH on the second cell 810-2 in parallel with obtaining SIB1, SIB20, and/or the SC-MCCH on the second cell 810-2. This may conserve network resources of the first cell 810-1 because the first cell 810-1 need not include SC-MCCH configuration information in the RRC connection reconfiguration message, while improving a user experience because the mobile device 805 can still maintain service continuity and access the SC-MTCH without waiting to obtain SIB1, SIB20, and the SC-MCCH.
  • the mobile device 805 may obtain the scheduling information for SC-MCCH from the SIB20 message and then obtain the full SC-MCCH information together with monitoring for any updates to configuration information for the SC-PTM service being received by the mobile device 805, and/or receiving configuration information for other SC-PTM services to which the mobile device 805 may subscribe.
  • Fig. 8 is provided as an example. Other examples are possible and may differ from what was described with respect to Fig. 8.
  • Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a mobile device, in accordance with various aspects of the present disclosure.
  • Example process 900 is an example where a mobile device (e.g., UE 145, 250) performs SC-PTM configuration in handover signaling for service continuity.
  • a mobile device e.g., UE 145, 250
  • SC-PTM configuration in handover signaling for service continuity.
  • process 900 may include receiving, via a first cell, a radio resource control (RRC) connection reconfiguration message that includes configuration information for accessing a single cell multicast traffic channel (SC-MTCH) , configured on a second cell, that delivers data for a single cell point-to-multipoint (SC-PTM) service that a mobile device is configured to receive (block 910) .
  • RRC radio resource control
  • SC-MTCH single cell multicast traffic channel
  • SC-PTM single cell point-to-multipoint
  • a mobile device may receive, via a first cell, an RRC connection reconfiguration message.
  • the RRC connection reconfiguration message may include configuration information for accessing an SC-MTCH, configured on a second cell, that delivers data for an SC-PTM service that the mobile device is configured to receive on the first cell.
  • the configuration information may indicate a schedule associated with transmission of the SC-MTCH.
  • a configuration of the SC-MTCH on the second cell may be different from a configuration of a corresponding SC-MTCH on the first cell.
  • the configuration information may indicate a portion of a configuration of the SC-PTM service that is common to the first cell and the second cell.
  • the configuration information may indicate that the configuration of the SC-PTM on the first cell is the same as the configuration of the SC-PTM on the second cell.
  • the mobile device may subscribe to the SC-PTM service, on the first cell, using a TMGI that identifies the SC-PTM service at the first cell.
  • the mobile device may receive the RRC connection reconfiguration message that includes the configuration information for the SC-PTM service having the same TMGI, at the second cell, as the TMGI used by the mobile device to subscribe to the SC-PTM service on the first cell.
  • the TMGI may be used to identify that the SC-PTM service is the same at the first cell and the second cell.
  • the configuration information may include only specific configuration information for accessing the specific SC-PTM service (s) to which the mobile device is subscribed. In this way, network resources may be conserved by excluding extraneous information not needed by the mobile device to access the SC-PTM service (s) , while enhancing a user experience by permitting service continuity for SC-PTM services during handover.
  • the configuration information may include SC-MCCH configuration information for accessing an SC-MCCH on the second cell (e.g., to obtain full configuration information for accessing other available SC-PTM services, to obtain updated configuration information for accessing the SC-PTM services (s) , etc. ) .
  • the SC-MCCH may provide control information for accessing one or more SC-PTM services on the second cell. In this way, a user experience associated with SC-PTM services may be enhanced by permitting service continuity for SC-PTM services during handover.
  • the configuration information may include cell information associated with the second cell, such as a cell identifier, information that identifies a downlink carrier frequency of the cell, and/or the like.
  • multiple neighbor cells may be capable of providing the SC-PTM service being received by the mobile device.
  • the configuration information may include cell information for the multiple cells, specific configuration information for the multiple cells (e.g., for accessing, on the multiple cells, the specific SC-PTM service (s) to which the mobile device is subscribed) , SC-MCCH configuration information for accessing the SC-MCCH on the multiple cells, and/or the like.
  • the cell information, the specific configuration information, and/or the SC-MCCH configuration information may be different for different cells.
  • process 900 may include performing a handover to the second cell (block 920) .
  • the mobile device may perform a handover to the second cell based at least in part on receiving the RRC connection reconfiguration message with the configuration information.
  • the mobile device may suspend or interrupt SC-PTM services (e.g., eMBMS communications provided via SC-PTM) during handover.
  • SC-PTM services e.g., eMBMS communications provided via SC-PTM
  • the delay associated with suspending or interrupting SC-PTM service (s) may be reduced because the configuration information for accessing the SC-PTM service (s) is included in the RRC connection reconfiguration message received prior to performing handover.
  • the mobile device may perform the handover by receiving a PSS, and SSS, and/or a PBCH from the second cell, as described in more detail elsewhere herein.
  • process 900 may include receiving the SC-PTM service via the SC-MTCH on the second cell based at least in part on the configuration information included in the RRC connection reconfiguration message (block 930) .
  • the mobile device may receive the SC-PTM service via the SC-MTCH on the second cell using the configuration information included in the RRC connection reconfiguration message (e.g., a G-RNTI for the SC-PTM service, scheduling information for the SC-MTCH, and/or the like) .
  • the configuration information may include a G-RNTI associated with the SC-MTCH on the second cell.
  • the mobile device may use the G-RNTI to identify a grant provided via the PDCCH on the second cell.
  • the mobile device may use the grant to obtain data for the SC-PTM service via the PDSCH of the second cell.
  • the mobile device may access the SC-MCCH on the second cell without waiting to obtain information included in SIB1 and/or SIB20. For example, the mobile device may access the SC-MCCH to obtain full configuration information for accessing other available SC-PTM services, to obtain updated configuration information for accessing the SC-PTM services (s) , and/or the like. In this way, the mobile device may conserve network resources of the second cell and may enhance a user experience for SC-PTM services. However, in some aspects, the mobile device may access the SC-MTCH to obtain the SC-PTM service (s) prior to accessing the SC-MCCH, further enhancing the user experience by reducing delays associated with obtaining SC-PTM services.
  • the mobile device may access SIB1 on the second cell to obtain information for accessing SIB20 on the second cell, may access SIB20 on the second cell to obtain information for accessing the SC-MCCH on the second cell, and may access the SC-MCCH on the second cell.
  • the mobile device may access the SC-MTCH to obtain the SC-PTM service (s) prior to or in parallel with accessing one or more of SIB1, SIB20, and/or the SC-MCCH on the second cell, thereby enhancing the user experience by reducing delays associated with obtaining SC-PTM services.
  • process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.
  • Fig. 10 is a diagram illustrating an example process 1000 performed, for example, by a base station, in accordance with various aspects of the present disclosure.
  • Example process 1000 is an example where a base station (e.g., base station 130, eNB 110, 210, 230) performs SC-PTM configuration in handover signaling for service continuity.
  • a base station e.g., base station 130, eNB 110, 210, 230
  • SC-PTM configuration in handover signaling for service continuity.
  • the term base station is not tied to any particular RAT, and may refer to an eNB (e.g., of an LTE network) or another type of base station associated with a different type of RAT.
  • process 1000 may include identifying a single cell point-to-multipoint (SC-PTM) service being provided to a mobile device via a first cell of a base station (block 1010) .
  • a base station may identify an SC-PTM service being provided to a mobile device via a first cell of the base station.
  • the base station may identify the SC-PTM service based at least in part on receiving, from the mobile device, a TMGI that identifies the SC-PTM service (e.g., in an MII message) .
  • process 1000 may include identifying a second cell that is configured to provide the SC-PTM service (block 1020) .
  • the base station may identify a second cell that is configured to provide the SC-PTM service being provided to the mobile device via the first cell.
  • the base station may identify the second cell using the TMGI.
  • the second cell may be associated with the same TMGI received on the first cell, which may indicate that the first cell and the second cell both support the same SC-PTM service.
  • the first cell and the second cell may be different cells of the same base station.
  • the first cell may be a cell of a first base station and the second cell may be a cell of a second base station.
  • the first cell may include, for example, a primary cell or a secondary cell used in carrier aggregation.
  • the secondary cell may include, for example, a primary cell or a secondary cell used in carrier aggregation.
  • process 1000 may include transmitting, in connection with a handover of the mobile device from the first cell to the second cell, a radio resource control (RRC) connection reconfiguration message to the mobile device that includes configuration information for accessing a single cell multicast traffic channel (SC-MTCH) , configured on the second cell, that delivers data for the SC-PTM service (block 1030) .
  • RRC radio resource control
  • SC-MTCH single cell multicast traffic channel
  • the mobile device and/or the base station may trigger a handover.
  • the mobile device may provide a measurement report to the base station, which may include information regarding the first cell and/or the second cell (e.g., signal power measurements, signal quality measurements, etc. ) .
  • the base station may trigger handover from the first cell to the second cell based at least in part on the measurement report.
  • the base station may transmit, to the mobile device and in connection with the handover of the mobile device from the first cell to the second cell, an RRC connection reconfiguration message that includes configuration information for accessing an SC-MTCH, configured on the second cell, that delivers data for the SC-PTM service.
  • the configuration information may include specific configuration information for accessing, on the second cell, the specific SC-PTM service (s) to which the mobile device is subscribed.
  • the configuration information may include SC-MCCH configuration information for accessing an SC-MCCH on the second cell.
  • a user experience associated with SC-PTM services may be enhanced by reducing delays associated with recovering SC-PTM services after handover, by ensuring that an SC-PTM service is supported by the second cell prior to handover, by pre-configuring a mobile device to receive SC-PTM services after handover, and/or the like.
  • process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.
  • the term component is intended to be broadly construed as hardware, firmware, or a combination of hardware and software.
  • a processor is implemented in hardware, firmware, or a combination of hardware and software.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .

Landscapes

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

Abstract

Certains aspects de la présente invention concernent de façon générale les communications sans fil. Selon certains aspects, un dispositif mobile peut recevoir, par l'intermédiaire d'une première cellule, un message de reconfiguration de connexion de commande de ressource radio (RRC) qui comprend des informations de configuration pour accéder à un canal de trafic de multidiffusion à cellule unique (SC-MTCH) configuré sur une deuxième cellule, qui délivre des données pour un service point à multipoint à cellule unique (SC-PTM) que le dispositif mobile est configuré pour recevoir au niveau de la première cellule. Le dispositif mobile peut effectuer un transfert intercellulaire vers la deuxième cellule. Le dispositif mobile peut recevoir le service SC-PTM par l'intermédiaire du SC-MTCH sur la deuxième cellule au moins en partie en fonction des informations de configuration comprises dans le message de reconfiguration de connexion de RRC.
PCT/CN2016/095885 2016-08-18 2016-08-18 Techniques et appareils pour la configuration de sc-ptm dans la signalisation de transfert intercellulaire pour la continuité de service WO2018032469A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/095885 WO2018032469A1 (fr) 2016-08-18 2016-08-18 Techniques et appareils pour la configuration de sc-ptm dans la signalisation de transfert intercellulaire pour la continuité de service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/095885 WO2018032469A1 (fr) 2016-08-18 2016-08-18 Techniques et appareils pour la configuration de sc-ptm dans la signalisation de transfert intercellulaire pour la continuité de service

Publications (1)

Publication Number Publication Date
WO2018032469A1 true WO2018032469A1 (fr) 2018-02-22

Family

ID=61197258

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/095885 WO2018032469A1 (fr) 2016-08-18 2016-08-18 Techniques et appareils pour la configuration de sc-ptm dans la signalisation de transfert intercellulaire pour la continuité de service

Country Status (1)

Country Link
WO (1) WO2018032469A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114158062A (zh) * 2020-09-07 2022-03-08 华硕电脑股份有限公司 用于mac重置相关移动性程序的方法和设备
CN115038049A (zh) * 2021-03-05 2022-09-09 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备
WO2022236722A1 (fr) * 2021-05-11 2022-11-17 Jrd Communication (Shenzhen) Ltd Procédé de transmission de configuration point à multipoint et appareil associé, et support de stockage lisible
CN115442755A (zh) * 2021-06-04 2022-12-06 成都鼎桥通信技术有限公司 信道建立方法、装置、设备、存储介质及程序产品
EP4120792A4 (fr) * 2020-03-13 2023-08-23 Samsung Electronics Co., Ltd. Procédé et appareil de configuration et de réception mbs dans un système de communication mobile
EP4195833A4 (fr) * 2020-08-06 2024-02-07 Vivo Mobile Communication Co Ltd Procédé et appareil de transmission d'informations, terminal et dispositif côté réseau

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090149164A1 (en) * 2007-12-10 2009-06-11 Research In Motion Limited System and method for single cell point-to-multipoint multiplexing and scheduling
CN102056342A (zh) * 2009-10-27 2011-05-11 大唐移动通信设备有限公司 一种多播控制信道mcch的收发方法、装置和系统
US20130107784A1 (en) * 2011-10-31 2013-05-02 Henry Chang Multimedia broadcast multicast service (mbms) idle mode counting procedure
CN104469691A (zh) * 2013-09-25 2015-03-25 电信科学技术研究院 一种组通信方法、设备及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090149164A1 (en) * 2007-12-10 2009-06-11 Research In Motion Limited System and method for single cell point-to-multipoint multiplexing and scheduling
CN102056342A (zh) * 2009-10-27 2011-05-11 大唐移动通信设备有限公司 一种多播控制信道mcch的收发方法、装置和系统
US20130107784A1 (en) * 2011-10-31 2013-05-02 Henry Chang Multimedia broadcast multicast service (mbms) idle mode counting procedure
CN104469691A (zh) * 2013-09-25 2015-03-25 电信科学技术研究院 一种组通信方法、设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"support of single- cell point-to-multipoint trassion in LTE", 3GPP TSG RAN MEETING#68 RP-150721 NEW WI PROPOSAL, 18 June 2015 (2015-06-18), XP055468288 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4120792A4 (fr) * 2020-03-13 2023-08-23 Samsung Electronics Co., Ltd. Procédé et appareil de configuration et de réception mbs dans un système de communication mobile
EP4195833A4 (fr) * 2020-08-06 2024-02-07 Vivo Mobile Communication Co Ltd Procédé et appareil de transmission d'informations, terminal et dispositif côté réseau
CN114158062A (zh) * 2020-09-07 2022-03-08 华硕电脑股份有限公司 用于mac重置相关移动性程序的方法和设备
CN114158062B (zh) * 2020-09-07 2024-04-09 华硕电脑股份有限公司 用于mac重置相关移动性程序的方法和设备
CN115038049A (zh) * 2021-03-05 2022-09-09 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备
CN115038049B (zh) * 2021-03-05 2024-01-23 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备
WO2022236722A1 (fr) * 2021-05-11 2022-11-17 Jrd Communication (Shenzhen) Ltd Procédé de transmission de configuration point à multipoint et appareil associé, et support de stockage lisible
CN115442755A (zh) * 2021-06-04 2022-12-06 成都鼎桥通信技术有限公司 信道建立方法、装置、设备、存储介质及程序产品
CN115442755B (zh) * 2021-06-04 2024-02-20 成都鼎桥通信技术有限公司 信道建立方法、装置、设备、存储介质

Similar Documents

Publication Publication Date Title
EP3329624B1 (fr) Techniques et appareils pour une surveillance de liaison radio virtuelle durant une agrégation de porteuses et une planification inter-porteuses
US11229075B2 (en) Techniques and apparatuses for opportunistically operating a dual receive, dual SIM dual standby (DR-DSDS) device as a dual SIM, dual active (DSDA) device
US10123278B2 (en) Techniques and apparatuses for adjusting transmission power for power-limited uplink carrier aggregation scenarios
WO2018032469A1 (fr) Techniques et appareils pour la configuration de sc-ptm dans la signalisation de transfert intercellulaire pour la continuité de service
US20180359789A1 (en) Techniques and apparatuses for determining a modification of a discontinuous reception cycle length
US10382950B2 (en) Techniques and apparatuses for accessing a header-compressed broadcast transmission
US10200828B2 (en) Techniques and apparatuses for utilizing measurement gaps to perform signal decoding for a multimedia broadcast or multicast service
US20180026903A1 (en) Techniques and apparatuses for connection termination in a multi-subscriber identity module (multi-sim) device
US20180279357A1 (en) Techniques and apparatuses for temporary modification of periodic grants
WO2017218203A1 (fr) Gestion de puissance par modification de la tension de polarisation en fonction du rapport de puissance crête sur moyenne
US10194306B2 (en) Techniques and apparatuses for suppressing network status information notifications
WO2018161856A1 (fr) Techniques et appareils de suppression de demande de planification (sr) pendant une communication multimédia
EP3466022B1 (fr) Techniques et appareils de décompression améliorée de compression d'en-tête robuste (rohc)
WO2018000574A1 (fr) Techniques et appareils de synchronisation de zone de suivi
US20180084469A1 (en) Techniques and apparatuses for reducing delay when obtaining service
US10484836B2 (en) Techniques and apparatuses for long term evolution idle-mode and enhanced multimedia broadcast and multicast service concurrency operation
US10231282B1 (en) Techniques and apparatuses for tune-away management
WO2019050675A1 (fr) Techniques et appareils pour une communication de dispositif à dispositif à l'aide d'une chaîne de communication de porteuse composante secondaire active
WO2018204647A1 (fr) Techniques et appareils de surveillance de canal de liaison descendante
WO2020199226A1 (fr) Libération de connexion de gestion des ressources radio (rrc) basée sur un équipement d'utilisateur (ue)
WO2019033327A1 (fr) Techniques et appareils permettant d'identifier une cellule candidate pour le rétablissement d'une connexion radio

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: 16913226

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16913226

Country of ref document: EP

Kind code of ref document: A1