WO2018085335A1 - Améliorations pour une transmission d'informations système dans d'autres services de diffusion/multidiffusion multimédia évolués - Google Patents

Améliorations pour une transmission d'informations système dans d'autres services de diffusion/multidiffusion multimédia évolués Download PDF

Info

Publication number
WO2018085335A1
WO2018085335A1 PCT/US2017/059456 US2017059456W WO2018085335A1 WO 2018085335 A1 WO2018085335 A1 WO 2018085335A1 US 2017059456 W US2017059456 W US 2017059456W WO 2018085335 A1 WO2018085335 A1 WO 2018085335A1
Authority
WO
WIPO (PCT)
Prior art keywords
subframe
fembms
transmitted
message
cas
Prior art date
Application number
PCT/US2017/059456
Other languages
English (en)
Inventor
Jeongho Jeon
Hyung-Nam Choi
Seunghee Han
Original Assignee
Intel IP Corporation
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 Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2018085335A1 publication Critical patent/WO2018085335A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery

Definitions

  • Evolved Multimedia Broadcast Multicast Service provides an efficient way to deliver download data as well as streaming content to multiple users.
  • Mobile video streaming especially is foreseen to generate a major volume of network data traffic in the future.
  • Commercial deployments of eMBMS also known as LTE Broadcast, are generating increasing interest. In order to meet the industry and operators' demand, eMBMS may be enhanced even further.
  • the Third Generation Partnership Project (3 GPP) is currently endeavoring to provide enhancements for television (TV) application support wherein 3 GPP networks can provide unicast and broadcast transport to support distribution of TV programs. It can support the three types of TV services including Free-to-air (FTA), Free-to- view (FTV), and Subscribed services. Each type of TV service has different requirements in order to meet regulatory obligations and public service and commercial broadcaster' s requirements regarding content distribution.
  • FTA Free-to-air
  • FTV Free-to- view
  • Subscribed services Subscribed services.
  • Each type of TV service has different requirements in order to meet regulatory obligations and public service and commercial broadcaster' s requirements regarding content distribution.
  • Some LTE specifications support a downlink orthogonal frequency-division multiplexing (OFDM) mode using 7.5 kHz subcarrier spacing and a long cyclic prefix (CP) of 33.3 microseconds ( ⁇ 8). There is, however, no signaling defined indicating the use of this mode and hence it cannot be implemented.
  • OFDM orthogonal frequency-division multiplexing
  • MMSFNs multicast-broadcast single-frequency networks
  • ISDs inter-site distances
  • FIG. 1 is a diagram of a network to implement a further evolved multimedia multibroadcast system (FeMBMS) in accordance with one or more embodiments;
  • FeMBMS evolved multimedia multibroadcast system
  • FIG. 2 is a diagram of a one-hundred percent multicast-broadcast single-frequency network (MBSFN) configuration including a cell acquisition subframe in accordance with one or more embodiments;
  • MMSFN multicast-broadcast single-frequency network
  • FIG. 3 is a diagram of a system information acquisition processing including a
  • SIB System Information Block
  • FeMBMS evolved multimedia multibroadcast system
  • FIG. 4 is a diagram of a cell acquisition subframe resource block structure in accordance with one or more embodiments
  • FIG. 5 illustrates an architecture of a system of a network in accordance with some embodiments
  • FIG. 6 illustrates example components of a device in accordance with some embodiments.
  • FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • network 100 may implement a further evolved multimedia multibroadcast system (FeMBMS) which is a further enhancement to an evolved multimedia multibroadcast MBMS (eMBMS) system.
  • FeMBMS further evolved multimedia multibroadcast system
  • eMBMS evolved multimedia multibroadcast MBMS
  • an Evolved Universal Terrestrial Radio Access Network (EUTRAN) 110 may include one or more evolved NodeB (eNB) devices such as eNB 112 and eNB 114 operating in accordance with a Third Generation Partnership Project (3GPP) standard.
  • eNB evolved NodeB
  • the one or more eNBs such as eNB 112 and eNB 114 transmit the same content to one or more user equipment (UE) devices such as UE 116, UE 118, and UE 120 via broadcast or multicast transmission.
  • UE user equipment
  • Such an arrangement of network 100 may comprise a multicast-broadcast single - frequency network (MBSFN) in which multicast or broadcast information is transmitted to the UE devices in a synchronized manner using a single frequency by using a sufficient cyclic prefix (CP) to avoid inter-symbol interference (ISI) such that the transmissions from the multiple eNBs of EUTRAN 110 appear to be transmitted from a single cell.
  • MBSFN multicast-broadcast single - frequency network
  • CP sufficient cyclic prefix
  • ISI inter-symbol interference
  • FIG. 2 a diagram of a one-hundred percent multicast-broadcast single-frequency network (MBSFN) configuration including a cell acquisition subframe in accordance with one or more embodiments will be discussed.
  • MBSFN subframes for an evolved multimedia multibroadcast system (eMBMS) system is shown in the structure of frame 200.
  • allocation of MBSFN subframes 212 is limited to subframe 1, subframe 2, subframe 3, subframe 6, subframe 7, and subframe 8 of frame 200.
  • the other subframes of frame 200 may be used for paging and/or sync paging. In some instances, there may be scenarios in which a larger allocation of MBSFN subframes 212 may be used.
  • eMBMS deployed on a supplementary downlink (SDL) carrier which may be utilized to avoid wasting uplink capacity on a frequency division duplex (FDD) uplink/downlink carrier pair.
  • SDL supplementary downlink
  • FDD frequency division duplex
  • eMBMS traffic may be concentrated on as few SDL carriers as possible.
  • MBSFN subframes 212 for an eMBMS system have a unicast control region of one or two orthogonal frequency-division multiplexing (OFDM) symbols. These unicast control symbols, however, present a large overhead.
  • OFDM orthogonal frequency-division multiplexing
  • a further evolved multimedia multibroadcast system may be implemented by providing a one-hundred percent configuration of MBSFN subframes 216 in frame 214 in which all subframes 0 through 9 of frame 214 are configured as MBSFN subframes 216.
  • subframe 0 may comprise a cell acquisition subframe (CAS) subframe 218 in which system information may be transmitted as discussed in further detail herein. Details of such a CAS subframe 218 are shown in and described with respect to FIG. 4, below.
  • SIB modified system information block
  • FIG. 3 a diagram of a system information acquisition processing including a System Information Block (SIB) Type 1 adapted for a further evolved multimedia multibroadcast system (FeMBMS) in accordance with one or more embodiments will be discussed.
  • EUTRAN 110 may transmit a Master Information Block (MIB) to UE 116 at operation 310.
  • MIB Master Information Block
  • EUTRAN 110 also may transmit a System Information Block (SIB) Typel to UE 116 at operation 312.
  • SI System Information
  • Additional SIBs may be transmitted from EUTRAN 110 to UE 116.
  • the first SI may be a combination of multiple SIBs.
  • information for the MBSFN carrier inside SIB1, SIB2, and SIB 13 may be provided on the FeMBMS carrier.
  • SIB 15 and SIB 16 may be delivered on the FeMBMS carrier in addition to SIB10, SIB11, and SIB12.
  • a new SIB1 adapted for FeMBMS may be transmitted as SystemlnformationBlockTypel operation 312 wherein the new SIB 1 may comprise a combination of eMBMS related information included in any of the legacy SIBs such as SIB1, SIB2, SIB13, SIB15, and/or SIB16.
  • the new SIB1 includes information contained in SIB1 and SIB2 including information relevant to eMBMS.
  • the new SIB1 may include information contained in the legacy SIB1 which is relevant to eMBMS.
  • the new SIB1 may be identical or substantially identical to the legacy SIB 1.
  • Other types of information and other combinations of system information also may be included in the new SIB1.
  • the size of the legacy SIB messages may be estimated as follows.
  • a legacy SIB1 message that only contains optional information that is relevant for the FeMBMS carrier has a size of approximately 42 bytes when describing six public land mobile networks (PLMNs) and scheduling of six different SI messages.
  • a legacy SIB2 message that only contains optional information that is relevant for the FeMBMS carrier has a size of approximately 57 bytes when describing eight different MBSFN frame allocations.
  • a legacy SIB13 message describing eight different MBSFN areas has a size of approximately 34 bytes.
  • FIG. 4 a diagram of a cell acquisition subframe resource block structure in accordance with one or more embodiments will be discussed.
  • the resource blocks for the CAS subframe 218 are shown in FIG. 4.
  • the system information may be provided by the physical downlink shared channel (PDSCH) in one or more CAS subframes 218 transmitted in subframe 0 and used for a one-hundred percent MBSFN configuration as shown for example in FIG. 2.
  • PDSCH physical downlink shared channel
  • CAS subframe 218 supports the primary synchronization signal (PSS), the secondary synchronization signal (SSS), the cell-specific reference signal (CRS), the physical broadcast channel (PBCH), the physical downlink control channel (PDCCH), and the physical downlink shared channel (PDSCH) for transmission of system information.
  • Example resource blocks are shown, for example CRS antenna ports (APs) 0/1 resource blocks 410, CRS APs 2/3 resource blocks 412, PSS/SSS resource blocks 414, PBCH symbol 1 resource blocks 416, PBCH symbol 2 resource blocks 418, PBCH symbol 3 resource blocks 420, and PBCH symbol 4 resource blocks 422.
  • the PDSCH resource blocks are indicated by the white resource blocks in CAS subframe 218. It should be noted that the arrangement of the resource blocks shown is merely one example, and the scope of the claimed subject matter is not limited in this respect.
  • a system bandwidth of 1.4 MHz may be used.
  • symbol 2 and symbol 3 in slot 0 and symbol 4 and symbol 5 in slot 1 are available for PDSCH transmission.
  • the total number of REs available for PDSCH is 44 per RB, which results in 264 REs over 6 RBs. Therefore, with quadrature phase-shift keying (QPSK) modulation for SI, a total 582 bits, or 66 bytes, can be transmitted in CAS PDSCH.
  • QPSK quadrature phase-shift keying
  • the FeMBMS carrier may be configured for a carrier bandwidth equal to or larger than 3 MHz, and in another embodiment, FeMBMS carrier may be configured for carrier bandwidth equal to or larger than 5 MHz, although the scope of the claimed subject matter is not limited in this respect.
  • the CAS subframe 218 may indicate the presence of a periodic subframe other than a CAS subframes in which system information may be transmitted.
  • T subframe number
  • Y subframe offset
  • T X
  • Y subframe offset
  • T, X, and/or Y may be hard coded and therefore would not need to be signaled.
  • the PSS/SSS may be transmitted.
  • PSS/SSS may not be transmitted.
  • the CAS subframe 218 may not be used as there is no unicast transmission with the one-hundred percent MBSFN configuration as shown in FIG. 2.
  • the SI messages are transmitted within periodically occurring Si-windows and the Si-windows of different SI messages do not overlap with each other. In other words, within one Si-window only the corresponding SI is transmitted, which may be inefficient and may not be an optimal utilization of the CAS subframe 218 resource for large system bandwidth.
  • the transmission of multiple different SI messages within one CAS subframe 218 may be utilized.
  • SIB1 SI- window related information
  • SIB1 SI- window related information
  • SIB2 SI- window related information
  • the CAS subframe 218 is always transmitted in subframe 0 with a period of 40 milliseconds (ms).
  • the MIB may indicate additional subframes other than the CAS subframe 218.
  • the MIB may contain a system frame number systemFrameN umber equal to the six most significant bits of the SFN.
  • the first system information may be a combination of two or more SIBs, and multiple system information messages may be transmitted in the same subframe by using different radio network temporary identifiers (RNTIs).
  • RNTIs radio network temporary identifiers
  • FIG. 5 illustrates an architecture of a system of a network in accordance with some embodiments.
  • the system 500 is shown to include a user equipment (UE) 501 and a UE 502.
  • the UEs 501 and 502 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non- mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless handsets
  • any of the UEs 501 and 502 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UEs 501 and 502 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 510—
  • the RAN 510 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E- UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E- UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 501 and 502 utilize connections 503 and 504, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 503 and 504 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UEs 501 and 502 may further directly exchange communication data via a ProSe interface 505.
  • the ProSe interface 505 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 502 is shown to be configured to access an access point (AP) 506 via connection 507.
  • the connection 507 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 506 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 506 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 510 can include one or more access nodes that enable the connections 503 and 504. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 510 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 511, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 512.
  • macro RAN node 511 e.g., macro RAN node 511
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes 511 and 512 can terminate the air interface protocol and can be the first point of contact for the UEs 501 and 502.
  • any of the RAN nodes 511 and 512 can fulfill various logical functions for the RAN 510 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UEs 501 and 502 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 511 and 512 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC- FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 511 and 512 to the UEs 501 and 502, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time- frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the physical downlink shared channel may carry user data and higher- layer signaling to the UEs 501 and 502.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 501 and 502 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 511 and 512 based on channel quality information fed back from any of the UEs 501 and 502.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 501 and 502.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 510 is shown to be communicatively coupled to a core network (CN) 520 — via an SI interface 513.
  • the CN 520 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 513 is split into two parts: the Sl-U interface 514, which carries traffic data between the RAN nodes 511 and 512 and the serving gateway (S-GW) 522, and the Sl-mobility management entity (MME) interface 515, which is a signaling interface between the RAN nodes 511 and 512 and MMEs 521.
  • S-GW serving gateway
  • MME Sl-mobility management entity
  • the CN 520 comprises the MMEs 521, the S-GW 522, the Packet Data Network (PDN) Gateway (P-GW) 523, and a home subscriber server (HSS) 524.
  • the MMEs 521 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 521 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 524 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 520 may comprise one or several HSSs 524, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 524 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 522 may terminate the SI interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520.
  • the S-GW 522 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 523 may terminate an SGi interface toward a PDN.
  • the P-GW 523 may route data packets between the EPC network 523 and external networks such as a network including the application server 530 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 525.
  • the application server 530 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 523 is shown to be communicatively coupled to an application server 530 via an IP communications interface 525.
  • the application server 530 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 501 and 502 via the CN 520.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 523 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 526 is the policy and charging control element of the CN 520.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF 526 may be communicatively coupled to the application server 530 via the P-GW 523.
  • the application server 530 may signal the PCRF 526 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 526 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 530.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 6 illustrates example components of a device in accordance with some embodiments.
  • the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown.
  • the components of the illustrated device 600 may be included in a UE or a RAN node.
  • the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPC).
  • the device 600 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud- RAN (C-RAN) implementations).
  • C-RAN Cloud- RAN
  • the application circuitry 602 may include one or more application processors.
  • the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 600.
  • processors of application circuitry 602 may process IP data packets received from an EPC.
  • the baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606.
  • Baseband processing circuity 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606.
  • the baseband circuitry 604 may include a third generation (3G) baseband processor 604 A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 604 e.g., one or more of baseband processors 604A-D
  • baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • encoding/decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604F.
  • the audio DSP(s) 604F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 604 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604.
  • RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.
  • the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
  • the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
  • RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
  • the mixer circuitry 606a of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
  • the amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band- pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 604 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
  • the baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to- analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.
  • ADC analog-to-digital converter
  • DAC digital-to- analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input.
  • the synthesizer circuitry 606d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a lookup table based on a channel indicated by the applications processor 602.
  • Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 606 may include an IQ/polar converter.
  • FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing.
  • FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.
  • the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606).
  • the transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).
  • PA power amplifier
  • the PMC 612 may manage power provided to the baseband circuitry 604.
  • the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 612 may often be included when the device
  • 600 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604.
  • the PMC 6 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.
  • the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power. [00064] If there is no data traffic activity for an extended period of time, then the device 600 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • DRX Discontinuous Reception Mode
  • the device 600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 600 may not receive data in this state, in order to receive data, it must transition back to RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 604 alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 604 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors.
  • Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.
  • the baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
  • a memory interface 712 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604
  • an application circuitry interface 714 e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6
  • an RF circuitry interface 716 e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
  • a wireless hardware connectivity interface 718 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 720 e.g., an interface to send/receive power or control signals to/from the PMC 612.
  • an apparatus of a user equipment comprises one or more baseband processors to configure a SystemlnformationBlockTypel (SIBl) message for further evolved multimedia broadcast multicast service (FeMBMS), wherein the SIBl message for FeMBMS includes eMBMS information from any one or more SIBs and wherein the SIBl message for FeMBMS information is configured in a cell acquisition subframe (CAS) subframe to be transmitted in subframe 0 of a frame configured for one -hundred percent multicast-broadcast single-frequency network (MBSFN) transmission, a memory to store the SIBl message for FeMBMS.
  • SIBl SystemlnformationBlockTypel
  • FeMBMS further evolved multimedia broadcast multicast service
  • Example two may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure the SIB 1 message for FeMBMS to include a combination of eMBMS information from one or more eMBMS system information blocks including SIBl, SIB2, SIB13, SIB15, or SIB16, or a combination thereof.
  • Example three may include the subject matter of example one or any of the examples described herein, wherein the SIBl message for FeMBMS is identical to the eMBMS SIBl.
  • Example four may include the subject matter of example one or any of the examples described herein, wherein the CAS subframe indicates the presence of a periodic subframe other than the CAS subframe in which system information is to be transmitted.
  • Example six may include the subject matter of example one or any of the examples described herein, wherein T, X, or Y, or a combination thereof are fixed.
  • Example seven may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • Example eight may include the subject matter of example one or any of the examples described herein, wherein the one or more base band processors are to configure a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to not be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5.
  • Example nine may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure multiple different system information messages to be included in one CAS subframe.
  • Example ten may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure the CAS subframe to not include system information window related information for the SIB1 message for FeMBMS.
  • Example eleven may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure the CAS subframe to include information on additional periodic subframes for system information transmission.
  • one or more machine-readable media may have instructions thereon that, if executed by an apparatus of a user equipment (UE), result in configuring a SystemlnformationBlockTypel (SIB1) message for further evolved multimedia broadcast multicast service (FeMBMS), wherein the SIB1 message for FeMBMS includes eMBMS information from any one or more SIBs and wherein SIB1 message for FeMBMS information is configured in a cell acquisition subframe (CAS) subframe to be transmitted in subframe 0 of a frame configured for one-hundred percent multicast-broadcast single-frequency network (MBSFN) transmission, and storing the SIB1 message for FeMBMS.
  • SIB1 message for FeMBMS includes eMBMS information from any one or more SIBs
  • SIB1 message for FeMBMS information is configured in a cell acquisition subframe (CAS) subframe to be transmitted in subframe 0 of a frame configured for one-hundred percent multicast-broadcast single-frequency network (MBSFN) transmission, and storing the SI
  • Example thirteen may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring the SIB 1 message for FeMBMS to include a combination of eMBMS information from one or more eMBMS system information blocks including SIB1, SIB2, SIB13, SIB15, or SIB16, or a combination thereof.
  • Example fourteen may include the subject matter of example twelve or any of the examples described herein, wherein the SIB1 message for FeMBMS is identical to the eMBMS SIB1.
  • Example fifteen may include the subject matter of example twelve or any of the examples described herein, wherein the CAS subframe indicates the presence of a periodic subframe other than the CAS subframe in which system information is to be transmitted.
  • Example seventeen may include the subject matter of example twelve or any of the examples described herein, wherein T, X, or Y, or a combination thereof are fixed.
  • Example eighteen may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configurating a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • Example nineteen may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to not be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5.
  • Example twenty may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring multiple different system information messages to be included in one CAS subframe.
  • Example twenty-one may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring the CAS subframe to not include system information window related information for the SIB1 message for FeMBMS.
  • Example twenty-two may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring the CAS subframe to include information on additional periodic subframes for system information transmission.
  • an apparatus of a user equipment comprises means for configuring a SystemlnformationBlockTypel (SIB1) message for further evolved multimedia broadcast multicast service (FeMBMS), wherein the SIB1 message for FeMBMS includes eMBMS information from any one or more SIBs and wherein SIB1 message for FeMBMS information is configured in a cell acquisition subframe (CAS) subframe to be transmitted in subframe 0 of a frame configured for one -hundred percent multicast-broadcast single-frequency network (MBSFN) transmission, and means for storing the SIB1 message for FeMBMS.
  • SIB1 message for FeMBMS includes eMBMS information from any one or more SIBs and wherein SIB1 message for FeMBMS information is configured in a cell acquisition subframe (CAS) subframe to be transmitted in subframe 0 of a frame configured for one -hundred percent multicast-broadcast single-frequency network (MBSFN) transmission
  • CAS cell acquisition subframe
  • Example twenty-four may include the subject matter of example twenty-three or any of the examples described herein, means for configuring the SIB1 message for FeMBMS to include a combination of eMBMS information from one or more eMBMS system information blocks including SIB1, SIB2, SIB13, SIB15, or SIB16, or a combination thereof.
  • Example twenty-five may include the subject matter of example twenty-three or any of the examples described herein, wherein the SIB 1 message for FeMBMS is identical to the eMBMS SIB1.
  • Example twenty-six may include the subject matter of example twenty-three or any of the examples described herein, wherein the CAS subframe indicates the presence of a periodic subframe other than the CAS subframe in which system information is to be transmitted.
  • Example twenty- eight may include the subject matter of example twenty-three or any of the examples described herein, wherein T, X, or Y, or a combination thereof are fixed.
  • Example twenty-nine may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configurating a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • Example thirty may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configuring a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to not be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5.
  • Example thirty-one may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configuring multiple different system information messages to be included in one CAS subframe.
  • Example thirty-two may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configuring the CAS subframe to not include system information window related information for the SIB1 message for FeMBMS.
  • Example thirty-three may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configuring the CAS subframe to include information on additional periodic subframes for system information transmission.
  • machine-readable storage may include machine-readable instructions, when executed, to realize an apparatus as claimed in any preceding claim.
  • Coupled may mean that two or more elements are in direct physical and/or electrical contact. Coupled, however, may also mean that two or more elements may not be in direct contact with each other, but yet may still cooperate and/or interact with each other.
  • Coupled may mean that two or more elements do not contact each other but are indirectly joined together via another element or intermediate elements.
  • on may be used in the following description and claims.
  • “On,” “overlying,” and “over” may be used to indicate that two or more elements are in direct physical contact with each other. It should be noted, however, that “over” may also mean that two or more elements are not in direct contact with each other. For example, “over” may mean that one element is above another element but not contact each other and may have another element or elements in between the two elements.
  • the term “and/or” may mean “and”, it may mean “or”, it may mean “exclusive-or”, it may mean “one”, it may mean “some, but not all”, it may mean “neither", and/or it may mean “both”, although the scope of claimed subject matter is not limited in this respect.

Landscapes

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

Abstract

L'information concerne un appareil d'un équipement d'utilisateur (UE) comprenant un ou plusieurs processeurs de bande de base pour configurer un message de type 1 de bloc d'informations système (SIB1) pour un autre service de diffusion/multidiffusion multimédia évolué (FeMBMS), le message SIB1 pour un FeMBMS comprenant des informations eMBMS provenant d'un ou plusieurs SIB et le message SIB1 pour des informations FeMBMS étant configuré dans une sous-trame de sous-trame d'acquisition de cellule (CAS) à transmettre dans la sous-trame 0 d'une trame configurée pour une transmission de réseau mono-fréquence de diffusion/multidiffusion (MBSFN) à cent pour cent. Le message SIB1 pour un FeMBMS peut être stocké dans une mémoire.
PCT/US2017/059456 2016-11-04 2017-11-01 Améliorations pour une transmission d'informations système dans d'autres services de diffusion/multidiffusion multimédia évolués WO2018085335A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662417927P 2016-11-04 2016-11-04
US62/417,927 2016-11-04

Publications (1)

Publication Number Publication Date
WO2018085335A1 true WO2018085335A1 (fr) 2018-05-11

Family

ID=60480403

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/059456 WO2018085335A1 (fr) 2016-11-04 2017-11-01 Améliorations pour une transmission d'informations système dans d'autres services de diffusion/multidiffusion multimédia évolués

Country Status (1)

Country Link
WO (1) WO2018085335A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110830408A (zh) * 2019-11-13 2020-02-21 天津德力仪器设备有限公司 一种应用于embms系统中快速捕获cas的方法
US11419041B2 (en) * 2019-04-24 2022-08-16 Qualcomm Incorporated Cell acquisition subframe enhancements for cellular broadcast services

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "FeMBMS System Information", vol. RAN WG2, no. Kaohsiung, Taiwan; 20161010 - 20161014, 30 September 2016 (2016-09-30), XP051161928, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_95bis/Docs/> [retrieved on 20160930] *
QUALCOMM INCORPORATED: "Open Issues on System Information for FeMBMS", vol. RAN WG2, no. Reno, NV, USA; 20161114 - 20161118, 5 November 2016 (2016-11-05), XP051193298, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_96/Docs/> [retrieved on 20161105] *
QUALCOMM INCORPORATED: "System Information for FeMBMS", vol. RAN WG2, no. Kaohsiung, Taiwan; 20161010 - 20161014, 1 October 2016 (2016-10-01), XP051162468, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_95bis/Docs/> [retrieved on 20161001] *
SESSION CHAIRMAN (NOKIA): "Chairman's Notes of Agenda Item 7.2.4 eMBMS enhancements for LTE", vol. RAN WG1, no. Lisbon, Portugal; 20161010 - 20161014, 18 October 2016 (2016-10-18), XP051160336, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_86b/Docs/> [retrieved on 20161018] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11419041B2 (en) * 2019-04-24 2022-08-16 Qualcomm Incorporated Cell acquisition subframe enhancements for cellular broadcast services
CN110830408A (zh) * 2019-11-13 2020-02-21 天津德力仪器设备有限公司 一种应用于embms系统中快速捕获cas的方法
CN110830408B (zh) * 2019-11-13 2022-02-22 天津德力仪器设备有限公司 一种应用于embms系统中快速捕获cas的方法

Similar Documents

Publication Publication Date Title
CN115174029B (zh) 在新空口（nr）中支持灵活的pdcch监视
US12022280B2 (en) Network selection and service continuity in non-public networks
US10886993B2 (en) Inter-cell beam management
US11895547B2 (en) Network controlled small gap configuration
US11006425B2 (en) Mechanisms to handle DL (downlink) control and data channels with different numerologies in NR (new radio)
WO2018145019A1 (fr) Transmission de pdcch (canal de commande de liaison descendante physique) commun de groupe pour nr (nouvelle radio)
US20190357303A1 (en) Transmission scheme for common control message with multi-beam operation
US11489637B2 (en) Downlink waveform type and guard interval adaptation for wireless system
US20210392616A1 (en) Paging Cause Determination for an Inactive Device in a 5G System
WO2018144781A1 (fr) Mesure de rsrp pour norme nouvelle radio
US20210243766A1 (en) Bandwidth Part Switching Delay for Uplink Transmission
US10966067B2 (en) Increase of spectral capacity of eMBMS-cell when deployed as a supplementary downlink carrier
US20210212138A1 (en) SERVICE ANNOUNCEMENT AND DISCOVERY CONSIDERATIONS FOR SIDELINK UNICAST CONNECTION ESTABLISHMENT FOR eV2X
WO2018085660A1 (fr) Améliorations apportées à des sous-trames d&#39;acquisition de cellule de service de diffusion/multidiffusion multimédia évolué (fembms)
WO2018144670A1 (fr) Mesures à large bande dans des systèmes de nouvelle radio
US11991610B2 (en) Long term evolution (LTE) control region for downlink transmissions for enhanced machine type communications (eMTC)
US11102846B2 (en) Downlink control information to support uplink partial subframe transmission on licensed assisted access secondary cell
WO2018085335A1 (fr) Améliorations pour une transmission d&#39;informations système dans d&#39;autres services de diffusion/multidiffusion multimédia évolués
WO2017192371A1 (fr) Émission de rs (signal de référence) de csi (informations d&#39;état de canal) avec un récepteur à ic (annulation de brouillage) de csi-rs
US11930443B2 (en) Enhancement for SMTC configuration for new 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: 17805022

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

Country of ref document: EP

Kind code of ref document: A1