WO2018085374A1 - Informations de système spécifiques à un point d'émission/réception - Google Patents

Informations de système spécifiques à un point d'émission/réception Download PDF

Info

Publication number
WO2018085374A1
WO2018085374A1 PCT/US2017/059502 US2017059502W WO2018085374A1 WO 2018085374 A1 WO2018085374 A1 WO 2018085374A1 US 2017059502 W US2017059502 W US 2017059502W WO 2018085374 A1 WO2018085374 A1 WO 2018085374A1
Authority
WO
WIPO (PCT)
Prior art keywords
trp
system information
specific system
cell
information
Prior art date
Application number
PCT/US2017/059502
Other languages
English (en)
Inventor
Candy YIU
Ralf Bendlin
Hwan-Joon Kwon
Alexei Davydov
Dae Won Lee
Yujian Zhang
Sudeep Palat
Youn Hyoung Heo
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 WO2018085374A1 publication Critical patent/WO2018085374A1/fr

Links

Classifications

    • 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
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering

Definitions

  • the present disclosure relates to wireless technology.
  • the present disclosure relates to techniques for signaling transmission/reception point (TRP, T/Rx point, or T/RP) specific system information (SI) (TRP-specific SI).
  • TRP transmission/reception point
  • SI system information
  • a base station can include a RAN node such as an evolved universal terrestrial radio access network (E-UTRAN) node B (also commonly denoted as evolved node B, enhanced node B, eNodeB, or eNB) and a radio network controller (RNC) in an E-UTRAN, which communicate with a wireless communication device known as a user equipment (UE) device, or simply UE.
  • E-UTRAN evolved universal terrestrial radio access network
  • UE user equipment
  • legacy LTE system information is broadcast per cell.
  • NR Fifth generation new radio
  • 5G NR is the global standard for a new orthogonal frequency division multiplexing (OFDM)-based air interface designed to support the wide variation of 5G device-types, services, deployments, and spectrum.
  • RAN nodes can include a 5G Node (e.g., 5G eNB or gNB), which is analogous to LTE (4G) eNBs.
  • gNBs include an antenna array (i.e., one or more antenna elements called TRPs) available to the network located at a specific geographical location.
  • TRPs antenna array
  • an NR cell is established by one or more TRP(s).
  • FIG. 1 is a block diagram of a RAN including LTE and NR cells.
  • FIG. 2 is a block diagram showing an enlarged view of an NR small cell of FIG. 1 , showing multiple UE beams of UEs, and multiple TRP beams of TRPs, in a wireless communication system, in accordance with various embodiments.
  • FIG. 3 is a block diagram of a wireless network architecture.
  • FIG. 4 illustrates a block diagram of an implementation for TRPs, eNBs, and/or UEs, in accordance with various embodiments.
  • FIG. 5 is a block diagram showing example interfaces of baseband processing circuitry.
  • FIG. 6 is a block diagram of components of a core network.
  • FIG. 7 is a block diagram of components able to read instructions from a computer readable medium.
  • Legacy LTE provides the same system information across a cell. And previously in NR, all system information transmitted from TRPs was expected to be identical, notwithstanding potential differences in TRPs or associated resources. System information was to be broadcast jointly by multiple TRPs, and each TRP was to be beamformed or single-frequency network (SFN) broadcasts the system information. In contrast, embodiments herein relate to TRP-specific system information and include different techniques to transmit it to the UE. Additional aspects and advantages will be apparent from the following detailed description of embodiments, which proceeds with reference to the accompanying drawings.
  • NR Unlike the earlier technologies, in NR it is expected that at least some cells of a RAN may include multiple TRPs per cell using beamforming for a high frequency band. Thus, in NR, there are advantages of and use cases for having system information that is not cell specific, in which case the system information is TRP specific or even beam specific.
  • the resources for conveying system information may vary and include as possible options minimum system information, system information block (SIB) 1 or 2, and dynamically allocated resources when the UE requests system information (called system information on demand).
  • SIB system information block
  • TRP-specific system information that is not cell specific is desirable, irrespective of whether such TRP-specific system information is encoded in a master information block (MIB), SIB, a TRP information block, or elsewhere in another design choice.
  • MIB master information block
  • SIB SIB
  • TRP information block a TRP information block
  • TRP hardware for each TRP is not the same, or the configurations are not the same.
  • antenna port information could be TRP specific since it depends on hardware (e.g., number of panels) and would impact the beamforming capability both in terms of beam shape and number of different beams available for one or more UEs.
  • the design of TRPs' multiplexing scheme e.g., frequency division multiplex (FDM) or time division multiplex (TDM) of access points (APs) may be different among several TRPs in a cell such that TRP-specific system information is beneficial for a UE.
  • beam reference signals(BRS) APs could be either FDMed (staggered BRS) or TDMed (beam-sweep).
  • SS synchronization signal
  • CSI-RS channel state information reference signal
  • a CSI-RS is not for RRM measurements— it is a cell-specific CSI-RS configuration for configuring a comb and other use cases.
  • they may send synchronization signals (similar to PSS and SSS) encoding a same cell ID.
  • PSS/SSS of LTE are defined for measurements: there is also the CSI-RS, which is similar to CSI-RS of conventional LTE, but in NR since CSI-RS also can be configured to the UE to perform RRM measurements for handover.
  • PSS/SSS is coded for cell ID and measurement is on CRS; in NR, cell ID will be coded in NR SS (similar to PSS/SSS) and measurement will be either on NR SS or CSI-RS.
  • each CSI-RS resource might be sent from a different TRP.
  • TRP-specific system information may include one or more of the following: TRP ID, cell ID, beams IDs, antenna port information depending on the hardware (number of panels), multiplexing (e.g., FDM or TDM), CRS REs for antenna port one after PSS/SSS, an antenna port for RRM, BRS which may be TDM and beam sweep which may be TDM, random access channel (RACH) information (including preamble and resource), different
  • numerologies e.g., duration
  • number of TRP panels e.g., TRP on/off information
  • TRP load information e.g., TRP load information
  • TRP ID is an identifier for a particular TRP. According to some embodiments,
  • the TRP ID is a name or number that uniquely identifies one TRP from other TRPs forming a cell.
  • cell ID is an identifier for a particular NR cell.
  • the cell ID is a name or number that uniquely identifies one cell from other cells that may have overlapping or spaced apart coverage areas.
  • Beams IDs are identifiers for the beams formed by a TRP. As described later with reference to FIG. 2, TRPs may produce multiple beams, and the beams IDs provide names or numbers uniquely identifying these beams or timing index to identify the beams.
  • Antenna port information is a TRP-specific type of information.
  • Multiplexing indicates whether a TRP uses FDM, TDM, or other multiplexing technologies for uplink and downlink data.
  • CRS REs for antenna port one after PSS/SSS is information that identifies the physical resource elements for CRS of antenna port one of a TRP.
  • PSS/SSS is used for PCI coding (cell ID) and CRS is the RS for measurement.
  • An antenna port for RRM is indicated because different TRPs can use different antenna ports for RRM.
  • BRS may be TDM and beam sweep may be TDM.
  • Random access information including, for example, preamble or resources for a RACH, may be different for various TRPs. This information, generally referred to as RACH information, also may indicate the pertinent resources in the time and frequency domain.
  • NR provides support for different numerologies, i.e., subcarrier spacing and frequency domain structure.
  • Each TRP may have a different numerology derived by scaling a basic subcarrier spacing.
  • the TRP-specific system information may include an indication of a numerology for a TRP.
  • Sweeping schedule or timing (e.g., duration) information is also optionally included in TRP-specific system information.
  • Sweeping schedule indicates when a reference signal is sent or the duration of this sweeping.
  • sweeping schedule is provided "SS block burst set.” And there is a sweeping schedule block duration and periodicity.
  • Number of TRP panels is another optional piece of TRP-specific system information.
  • the number of panels impacts beamforming, so this information is also useful for a UE.
  • TRP on/off information is also optionally provided because TRPs may occasionally turn on or off dynamically.
  • the UE is provided this information so that it can be aware of the TRP's scheduled on and off times.
  • TRP load information is optionally provided to a UE. For example, when the UE hands over from one cell to the data cell, the network might seek to control which TRP the UE may access, or the UE may seek a connection with a TRP that is least loaded. Load information, therefore, is made available so that the UE can pick TRP with less load.
  • Slicing information is another optional piece of TRP-specific system information. It is possible that different TRPs might have different slicing technology. If that is the case, it means that, from the UE point of view, the UE seeking to move from one TRP to another TRP would also entail some protocol setup changes. Thus, slicing information for TRPs is useful for the UE to know so that the UE may correctly perform beam switching (e.g., transitioning from one TRP beam to a beam of another TRP).
  • a handover between the TRPs entails a change in slicing configuration in terms of which portion of the network protocol stack— i.e., PDCP, RLC, MAC, and physical layer— is handled by the TRP, or which portion is handled at a high layer.
  • the TRP could have the MAC layer and the physical layer and then the eNodeB will have PDCP and RLC layers as one slicing option.
  • a heterogeneous deployment scenario 100 where both NR cells 108 and LTE cells 1 12 exist in a geographical area, are shown in terms of cell layout and RAN node (eNB or gNB 1 18) locations.
  • a heterogeneous deployment is where cells of different size are overlapped, e.g., macro and small cells, providing a mix of different sized coverage areas.
  • LTE cells 1 12 and NR cells 108 are overlaid and may be co- located (i.e., as indicated by ideal backhaul lines) 120 or not co-located 126.
  • a co- located cell refers to a small cell together with a macro cell for which their eNB or gNB 136 is installed at a common location.
  • a non-co-located cell refers to a small cell together with a macro cell for which the eNB or gNB 140 is installed at the different location.
  • LTE serves macro cells
  • NR serves small cells.
  • standalone (i.e., non-LTE anchored) 5G systems are also within the scope of this disclosure.
  • a homogeneous deployment (not shown) is also within the scope of this disclosure and means that overlapping cells provide the similar coverage areas, e.g. all macro or small cell.
  • one 5G cell is potentially formed from hundreds of TRPs, each having (and providing in TRP-specific system information) a unique TRP ID and an optional cell ID that is common to an NR cell.
  • FIG. 1 shows an NR small cell 150 established by a first TRP 152, a second TRP 158, and a third TRP 160, at least one of which is in wireless communication with a UE 166 through an NR wireless connection.
  • the NR small cell 150 includes multiple TRPs 152, 158, 160, which may be assumed to be the same or different types of hardware synchronized within the NR small cell 150.
  • a cell corresponds to its coverage area shown in FIG.
  • each TRP in the area transmits a common cell ID
  • the multiple TRPs need not necessarily transmit it or other data using the same multiplexing scheme or physical resource blocks.
  • only one NR cell is shown with multiple TRPs, but other co-located or non- co-located cells may also include multiple TRPs.
  • each TRP is considered to have beamforming capability toward the UE 166.
  • Beamforming in some embodiments, is one beam emitted at the antenna, or it could have a number of beams emitted by the TRP.
  • FIG. 2 illustrates links between multiple UE beams of UEs, and multiple TRP beams of TRPs in the cell 150, in accordance with various embodiments.
  • the TRPs e.g., TRP A, TRP B, and TRP C, may belong to (or otherwise be associated with) the same or different gNBs.
  • the TRP A, TRP B, and TRP C are, respectively, the first TRP 152, the second TRP 158, and the third TRP 160 of FIG. 1 .
  • a UE may include multiple UE beams, and a TRP may include multiple TRP beams.
  • the UE 1 may have a UE beam 202 and a UE beam 204
  • the UE 2 may have a UE beam 210 and a UE beam 214
  • the UE 3 may have a UE beam 220.
  • the TRP A may have a TRP beam 226 and a TRP beam 230
  • the TRP B may have a TRP beam 240 and a TRP beam 244
  • the TRP C may have a TRP beam 248.
  • the UE beams and the TRP beams may be numbered (i.e., a beam ID).
  • the UE beam 202 of the UE 1 may be the #1 beam of the UE 1
  • the TRP beam 230 may be the #2 beam of the TRP A.
  • beams IDs information produced in connection with TRP- specific information identifies individual beams. This information can also be mapped to NR synchronization signal (NRSS) or CSI-RS resources, which are indicated in the TRP-specific system information.
  • NRSS NR synchronization signal
  • CSI-RS resources which are indicated in the TRP-specific system information.
  • a link may be formed by a combination of a TRP beam and a UE beam.
  • the TRP beam 230 and the UE beam 214 may form a wireless link (also called a connection) 252
  • the TRP beam 230 and the UE beam 220 may form a link 256
  • the TRP beam 226 and the UE beam 202 may form a link 260.
  • More connections can be formed in similar fashions.
  • a link may be identified by a link identification (ID), or more simply by a beam ID, or a link ID.
  • FIG. 2 shows a number of actual or possible connections including, for example, links 266, 270, 280, 282, and 288.
  • a link may also be described as ⁇ (TRP #, Beam #)-(UE #, Beam #) ⁇ .
  • the link 252 may be described as ⁇ (TRP A, Beam 2)-(UE 2, Beam 2) ⁇ .
  • TRP-specific system information is contained within the system information.
  • system information contains both cell-specific and TRP-specific system information identified per each TRP.
  • each TRP has its TRP-specific system information identified by a TRP ID so that the UE can correlate the TRP-specific system information to the corresponding TRP based on the provided TRP ID.
  • the UE may read, for example, the system information and it will have all the TRP
  • the SI is transmitted by all the TRPs; e.g., in a SIB by a gNB.
  • a gNB when system information is transmitted by an eNB, each cell has its own information.
  • system information when system information is transmitted by the gNB that connects multiple TRPs, the signals it transmits are actually provided by the individual TRP antenna ports.
  • the actual transmission by a gNB comes from multiple TRP antenna ports of, e.g., TRP A, B, and C (FIG. 2), all transmitting the same system information for a cell.
  • system information does not contain TRP- specific system information but instead each TRP broadcasts it locally.
  • the system information includes cell-specific information but there is also TRP-specific system information, different for each TRP, that each TRP broadcasts in a separate resource location. Then, if the UE is interested or needs to read TRP-specific system information for a particular TRP, the UE will obtain the corresponding resources and the associated TRP-specific system information.
  • system information contains the location of the TRP-specific system information, and the actual TRP-specific system information will be broadcast in TRP locally.
  • system information contains the resource location (time or frequency) of the TRP-specific system information and then TRP basically will broadcast that information within the system information pointer to the location where it is supposed to broadcast.
  • FIG. 3 illustrates an architecture of a system 300 of a network in
  • the system 300 is shown to include the user equipment (UE) 301 and a UE 302.
  • the UEs 301 and 302 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 or any computing device including a wireless communications interface.
  • any of the UEs 301 and 302 can comprise an Internet of Things (loT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections.
  • An loT 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 loT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • loT network describes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.
  • the UEs 301 and 302 may be configured to connect, e.g.,
  • the RAN 310 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 301 and 302 utilize connections 303 and 304, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 303 and 304 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 3GPP 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 301 and 302 may further directly exchange communication data via a ProSe interface 305.
  • the ProSe interface 305 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
  • PSDCH Physical Sidelink Broadcast Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 302 is shown to be configured to access an access point (AP) 306 via connection 307.
  • the connection 307 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 1 protocol, wherein the AP 306 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 306 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 310 can include one or more access nodes that enable the connections 303 and 304.
  • These access nodes 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 310 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 31 1 (e.g., an LTE TRP), and one or more RAN nodes or TRPs 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 312 or 5G TRP.
  • macro RAN node 31 1 e.g., an LTE TRP
  • 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 31 1 and 312 can terminate the air interface protocol and can be the first point of contact for the UEs 301 and 302.
  • any of the RAN nodes 31 1 and 312 can fulfill various logical functions for the RAN 310 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 301 and 302 can be configured to communicate using Orthogonal Frequency-Division Multiplexing
  • OFDMMA Orthogonal Frequency- Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the 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 31 1 and 312 to the UEs 301 and 302, 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 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. There are several different physical downlink channels that are conveyed using such resource blocks.
  • the physical downlink shared channel may carry user data and higher-layer signaling to the UEs 301 and 302.
  • 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 301 and 302 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 302 within a cell) may be performed at any of the RAN nodes 31 1 and 312 based on channel quality information fed back from any of the UEs 301 and 302.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 301 and 302.
  • 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 1 , 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 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 enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 310 is shown to be communicatively coupled to a core network (CN) 320 -via an S1 interface 313.
  • the CN 320 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 S1 interface 313 is split into two parts: the S1 -U interface 314, which carries traffic data between the RAN nodes 31 1 and 312 and a serving gateway (S-GW) 322, and an S1 -mobility management entity (MME) interface 315, which is a signaling interface between the RAN nodes 31 1 and 312 and MMEs 321 .
  • S-GW serving gateway
  • MME S1 -mobility management entity
  • the CN 320 comprises the MMEs 321 , the S-GW 322, a Packet Data Network (PDN) Gateway (P-GW) 323, and a home subscriber server (HSS) 324.
  • the MMEs 321 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 321 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 324 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 320 may comprise one or several HSSs 324, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 324 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 322 may terminate the S1 interface 313 towards the RAN 310, and routes data packets between the RAN 310 and the CN 320.
  • the S- GW 322 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 323 may terminate an SGi interface toward a PDN.
  • the P-GW 323 may route data packets between the CN 320 (e.g., an EPC network) and external networks such as a network including the application server 330
  • an application server 330 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.).
  • the P-GW 323 is shown to be communicatively coupled to an application server 330 via an IP communications interface 325.
  • the application server 330 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 301 and 302 via the CN 320.
  • VoIP Voice-over-Internet Protocol
  • the P-GW 323 may further be a node for policy enforcement and charging data collection.
  • a Policy and Charging Enforcement Function (PCRF) 326 is the policy and charging control element of the CN 320.
  • 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 326 may be communicatively coupled to the application server 330 via the P-GW 323.
  • the application server 330 may signal the PCRF 326 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 326 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 330.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 4 illustrates example components of a device 400 in accordance with some embodiments.
  • the device 400 may include application circuitry 402, baseband circuitry 404, Radio Frequency (RF) circuitry 406, front-end module (FEM) circuitry 408, one or more antennas 410, and power management circuitry (PMC) 412 coupled together at least as shown.
  • the components of the illustrated device 400 may be included in a UE or a RAN node.
  • RF Radio Frequency
  • FEM front-end module
  • PMC power management circuitry
  • the device 400 may include fewer elements (e.g., a RAN node may not utilize application circuitry 402, and instead include a processor/controller to process IP data received from an EPC).
  • the device 400 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)
  • the application circuitry 402 may include one or more application processors.
  • the application circuitry 402 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 400.
  • processors of application circuitry 402 may process IP data packets received from an EPC.
  • the baseband circuitry 404 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 404 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 406 and to generate baseband signals for a transmit signal path of the RF circuitry 406.
  • Baseband processing circuity 404 may interface with the application circuitry 402 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 406.
  • the baseband circuitry 404 may include a third generation (3G) baseband processor 404A, a fourth generation (4G) baseband processor 404B, a fifth generation (5G) baseband processor 404C, or other baseband processor(s) 404D 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 404 e.g., one or more of baseband processors 404A-D
  • baseband processors 404A-D may be included in modules stored in the memory 404G and executed via a Central Processing Unit (CPU) 404E.
  • 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 404 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 404 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC)
  • LDPC Low Density Parity Check
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 404 may include one or more audio digital signal processor(s) (DSP) 404F.
  • the audio DSP(s) 404F 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 404 and the application circuitry 402 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 404 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 404 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), or 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 404 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 406 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 406 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • the RF circuitry 406 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 408 and provide baseband signals to the baseband circuitry 404.
  • RF circuitry 406 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 404 and provide RF output signals to the FEM circuitry 408 for transmission.
  • the receive signal path of the RF circuitry 406 may include mixer circuitry 406A, amplifier circuitry 406B and filter circuitry 406C.
  • the transmit signal path of the RF circuitry 406 may include filter circuitry 406C and mixer circuitry 406A.
  • RF circuitry 406 may also include
  • synthesizer circuitry 406D for synthesizing a frequency for use by the mixer circuitry 406A of the receive signal path and the transmit signal path.
  • the mixer circuitry 406A of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 408 based on the synthesized frequency provided by synthesizer circuitry 406D.
  • the amplifier circuitry 406B may be configured to amplify the down-converted signals and the filter circuitry 406C 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.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 404 for further processing.
  • the output baseband signals may be zero- frequency baseband signals, although this is not a requirement.
  • the mixer circuitry 406A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 406A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 406D to generate RF output signals for the FEM circuitry 408.
  • the baseband signals may be provided by the baseband circuitry 404 and may be filtered by the filter circuitry 406C.
  • the mixer circuitry 406A of the receive signal path and the mixer circuitry 406A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 406A of the receive signal path and the mixer circuitry 406A 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 406A of the receive signal path and the mixer circuitry 406A may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 406A of the receive signal path and the mixer circuitry 406A 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 406 may include analog-to- digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 404 may include a digital baseband interface to communicate with the RF circuitry 406.
  • 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 406D may be a fractional- N synthesizer or a fractional N/N+1 synthesizer, although the scope of the
  • synthesizer circuitry 406D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 406D may be configured to synthesize an output frequency for use by the mixer circuitry 406A of the RF circuitry 406 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 406D may be a fractional N/N+1 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 404 or the application circuitry 402 (such as an applications processor) 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 application circuitry 402.
  • Synthesizer circuitry 406D of the RF circuitry 406 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • DLL delay-locked loop
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+1 (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. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
  • the synthesizer circuitry 406D 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 406 may include an IQ/polar converter.
  • FEM circuitry 408 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 410, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 406 for further processing.
  • the FEM circuitry 408 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 406 for transmission by one or more of the one or more antennas 410.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 406, solely in the FEM circuitry 408, or in both the RF circuitry 406 and the FEM circuitry 408.
  • the FEM circuitry 408 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 408 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 408 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 406).
  • the transmit signal path of the FEM circuitry 408 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry 406), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 410).
  • PA power amplifier
  • the PMC 412 may manage power provided to the baseband circuitry 404.
  • the PMC 412 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 412 may often be included when the device 400 is capable of being powered by a battery, for example, when the device 400 is included in a UE.
  • the PMC 412 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 4 shows the PMC 412 coupled only with the baseband circuitry 404.
  • the PMC 412 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry 402, the RF circuitry 406, or the FEM circuitry 408.
  • the PMC 412 may control, or otherwise be part of, various power saving mechanisms of the device 400. For example, if the device 400 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 400 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 400 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 400 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 400 may not receive data in this state, and in order to receive data, it transitions back to an 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 402 and processors of the baseband circuitry 404 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 404 alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 402 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g.,
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • 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. 5 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 404 of FIG. 4 may comprise processors 404A-404E and a memory 404G utilized by said processors.
  • Each of the processors 404A-404E may include a memory interface, 504A-504E, respectively, to send/receive data to/from the memory 404G.
  • the baseband circuitry 404 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 512 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 404), an application circuitry interface 514 (e.g., an interface to send/receive data to/from the application circuitry 402 of FIG. 4), an RF circuitry interface 516 (e.g., an interface to send/receive data to/from RF circuitry 406 of FIG. 4), a wireless hardware connectivity interface 518 (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
  • NFC Near Field Communication
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components
  • a power management interface 520 e.g., an interface to send/receive power or control signals to/from the PMC 412.
  • FIG. 6 illustrates components of a core network in accordance with some embodiments.
  • the components of the CN 320 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non- transitory machine-readable storage medium).
  • Network Functions Virtualization NFV is utilized to virtualize any or all of the above described network node functions via executable instructions stored in one or more computer readable storage mediums (described in further detail below).
  • a logical instantiation of the CN 320 may be referred to as a network slice 601.
  • a logical instantiation of a portion of the CN 320 may be referred to as a network sub-slice 602 (e.g., the network sub-slice 602 is shown to include the PGW 323 and the PCRF 326).
  • NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches.
  • NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.
  • FIG. 7 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • FIG. 7 shows a diagrammatic representation of hardware resources 700 including one or more processors (or processor cores) 710, one or more
  • a hypervisor 702 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 700.
  • the processors 710 may include, for example, a processor 712 and a processor 714.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory/storage devices 720 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 720 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • the communication resources 730 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 704 or one or more databases 706 via a network 708.
  • the communication resources 730 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular
  • NFC components NFC components
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components Wi-Fi components
  • Instructions 750 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 710 to perform any one or more of the methodologies discussed herein.
  • the instructions 750 may reside, completely or partially, within at least one of the processors 710 (e.g., within the processor's cache memory), the memory/storage devices 720, or any suitable combination thereof.
  • any portion of the instructions 750 may be transferred to the hardware resources 700 from any combination of the peripheral devices 704 or the databases 706.
  • the memory of processors 710, the memory/storage devices 720, the peripheral devices 704, and the databases 706 are examples of computer-readable and machine- readable media.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • a memory interface configured to receive TRP-specific system information pertaining to the at least one of the multiple TRPs, the TRP-specific system information being different from that of one or more other TRPs of the multiple TRPs in the cell of the RAN.
  • RAN radio access network
  • TRPs transmission/reception points
  • An apparatus for a user equipment (UE) for wireless communications with at least one of multiple transmission/reception points (TRPs) providing a cell comprising: a memory interface configured to receive cell-specific system information defining the cell and TRP-specific system information
  • processors configured to: decode the cell-specific system information broadcast in the cell by one or more TRPs of the multiple TRPs, and decode first TRP-specific system information broadcast in the cell by the first TRP, the first TRP-specific system information being different from second TRP-specific system information broadcast in the cell by a second TRP of the multiple TRPs defining the cell, the first TRP being different from the second TRP.
  • An apparatus for a user equipment (UE) for wireless communications with multiple transmission/reception points (TRPs) forming a new radio (NR) cell comprising: a memory interface configured to receive system information and a set of TRP-specific system information, different members of the set corresponding to different TRPs of the multiple TRPs; and one or more processors to decode the system information and obtain from it indications of different resource locations at which the different TRPs transmit corresponding TRP-specific system information.
  • the TRP-specific system information includes a cell identifier.
  • the TRP-specific system information includes beams identifiers.
  • [0104] 1 1 The apparatus of any one of examples 1-4, in which the TRP-specific system information indicates an antenna port for radio resource management (RRM).
  • RRM radio resource management
  • TRP-specific system information includes TRP on/off information.
  • TRP-specific system information includes TRP load information.
  • RAN node is an evolved Node B (eNB).
  • eNB evolved Node B
  • gNB fifth generation new radio (NR) node
  • TRP-specific system information comprises one or more of a TRP identification, a cell
  • a beams identification identification, a beams identification, antenna port information, a number of panels, a multiplexing scheme of a TRP, cell-specific reference signal (CRS) resource element (RE) locations corresponding to antenna port, an antenna port for radio resource management, a multiplexing scheme for a beam reference signal (BRS), a
  • RACH random access channel
  • TRPs transmission/reception points
  • RAN radio access network
  • RAN radio access network
  • TRPs transmission/reception points
  • a method, performed by a user equipment (UE), for wireless communications with at least one of multiple transmission/reception points (TRPs) providing a cell comprising: receiving, via a memory interface, cell- specific system information defining the cell and TRP-specific system information corresponding to a first TRP of the multiple TRPs providing the cell; decoding the cell-specific system information broadcast in the cell by one or more TRPs of the multiple TRPs; decoding first TRP-specific system information broadcast in the cell by the first TRP, the first TRP-specific system information being different from second TRP-specific system information broadcast in the cell by a second TRP of the multiple TRPs defining the cell, the first TRP being different from the second TRP.
  • TRPs transmission/reception points
  • TRPs transmission/reception points
  • TRP-specific system information indicates resource elements of a channel reference signal (CRS) for antenna port one.
  • RRM radio resource management
  • the information indicates a first resource location of the first TRP-specific system information and a second resource location of the second TRP-specific information, in which the first resource location is different from the second resource location.
  • a beams identification identification, a beams identification, antenna port information, a number of panels, a multiplexing scheme of a TRP, cell-specific reference signal (CRS) resource element (RE) locations corresponding to antenna port, an antenna port for radio resource management, a multiplexing scheme for a beam reference signal (BRS), a
  • RACH random access channel
  • Machine-readable storage including machine-readable instructions, when executed, to implement a method or realize an apparatus as described in any preceding example.
  • a machine readable medium including code, when executed, to cause a machine to perform the method as described in any in any preceding example.

Landscapes

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

Abstract

Des informations de système spécifiques à un TRP comprennent un ou plusieurs des éléments suivants : un ID de TRP, un ID de cellule, des ID de faisceaux, des informations de port d'antenne en fonction du matériel (nombre de panneaux), le multiplexage (p. ex., FDM ou TDM), des RE de CRS pour port d'antenne, l'un après PSS/SSS, un port d'antenne de RRM, un BRS qui peut être TDM et un balayage de faisceau qui peut être TDM, des informations de canal d'accès aléatoire (RACH) (comprenant un préambule et une ressource), des numérologies différentes, une programmation ou une synchronisation de balayage (p. ex., une durée), un nombre de panneaux de TRP, des informations de marche/arrêt de TRP, des informations de charge de TRP ou des informations de tranchage. Des informations de système spécifiques à un TRP sont fournies dans une ressource physique dédiée avec des informations spécifiques à une cellule, dans des ressources séparées transmises localement par chaque TRP, ou des informations de système contiennent des emplacements de ressources séparées transmises par des TRP correspondants.
PCT/US2017/059502 2016-11-04 2017-11-01 Informations de système spécifiques à un point d'émission/réception WO2018085374A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662418117P 2016-11-04 2016-11-04
US62/418,117 2016-11-04

Publications (1)

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

Family

ID=60574704

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/059502 WO2018085374A1 (fr) 2016-11-04 2017-11-01 Informations de système spécifiques à un point d'émission/réception

Country Status (1)

Country Link
WO (1) WO2018085374A1 (fr)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020134383A1 (fr) * 2018-12-27 2020-07-02 维沃移动通信有限公司 Procédé de transmission, terminal, dispositif de réseau, et support d'informations lisible par ordinateur
US20200267748A1 (en) * 2019-02-14 2020-08-20 Qualcomm Incorporated Dynamic switching between different multi-transmission/reception point schemes
CN112470512A (zh) * 2018-07-31 2021-03-09 高通股份有限公司 用于不同发送接收点的单独测量和报告
CN113453338A (zh) * 2020-03-24 2021-09-28 维沃移动通信有限公司 接收方法、发送方法、终端及网络侧设备
CN114339958A (zh) * 2020-09-29 2022-04-12 维沃移动通信有限公司 网络接入方法、网络接入装置、终端和网络侧设备
CN114340031A (zh) * 2020-09-29 2022-04-12 维沃移动通信有限公司 随机接入方法、装置、终端及可读存储介质
WO2023075667A1 (fr) * 2021-10-28 2023-05-04 Telefonaktiebolaget Lm Ericsson (Publ) Calcul de l'utilisation de blocs de ressources physiques dans une transmission de multiples points de transmission
WO2023079506A1 (fr) * 2021-11-05 2023-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Systèmes et procédés de fourniture d'informations de temps de référence pour une synchronisation temporelle
EP4132078A4 (fr) * 2020-03-24 2023-08-23 Vivo Mobile Communication Co., Ltd. Procédé de mesure, terminal, et dispositif côté réseau
US12081307B2 (en) 2021-12-08 2024-09-03 Samsung Electronics Co., Ltd. Method for setting reception beam in electronic device receiving signals transmitted from plurality of TRPs and electronic device

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130028180A1 (en) * 2011-07-28 2013-01-31 Research In Motion Limited Method and system for access and uplink power control for a wireless system having multiple transmit points
WO2015109153A1 (fr) * 2014-01-17 2015-07-23 Interdigital Patent Holdings, Inc. Architecture de système de liaison d'accès mmw 3gpp

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130028180A1 (en) * 2011-07-28 2013-01-31 Research In Motion Limited Method and system for access and uplink power control for a wireless system having multiple transmit points
WO2015109153A1 (fr) * 2014-01-17 2015-07-23 Interdigital Patent Holdings, Inc. Architecture de système de liaison d'accès mmw 3gpp

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "NR cell for idle state", vol. RAN WG2, no. Kaohsiung; 20161010 - 20161014, 9 October 2016 (2016-10-09), XP051150743, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20161009] *
INSTITUTE FOR INFORMATION INDUSTRY (III): "Discussion on System Information Delivery in NR", vol. RAN WG1, no. Lisbon, Portugal; 20161010 - 20161014, 9 October 2016 (2016-10-09), XP051150226, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20161009] *

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112470512A (zh) * 2018-07-31 2021-03-09 高通股份有限公司 用于不同发送接收点的单独测量和报告
WO2020134383A1 (fr) * 2018-12-27 2020-07-02 维沃移动通信有限公司 Procédé de transmission, terminal, dispositif de réseau, et support d'informations lisible par ordinateur
US12047128B2 (en) 2018-12-27 2024-07-23 Vivo Mobile Communication Co., Ltd. Transmission method of TRP control information, terminal, network device, and computer-readable storage medium
US11563514B2 (en) * 2019-02-14 2023-01-24 Qualcomm Incorporated Dynamic switching between different multi-transmission/reception point schemes
US20200267748A1 (en) * 2019-02-14 2020-08-20 Qualcomm Incorporated Dynamic switching between different multi-transmission/reception point schemes
US11611407B2 (en) 2019-02-14 2023-03-21 Qualcomm Incorporated Dynamic switching between different multi-trans mission/reception point schemes
CN113453338A (zh) * 2020-03-24 2021-09-28 维沃移动通信有限公司 接收方法、发送方法、终端及网络侧设备
EP4132078A4 (fr) * 2020-03-24 2023-08-23 Vivo Mobile Communication Co., Ltd. Procédé de mesure, terminal, et dispositif côté réseau
CN113453338B (zh) * 2020-03-24 2023-09-05 维沃移动通信有限公司 接收方法、发送方法、终端及网络侧设备
CN114340031A (zh) * 2020-09-29 2022-04-12 维沃移动通信有限公司 随机接入方法、装置、终端及可读存储介质
CN114339958B (zh) * 2020-09-29 2023-07-07 维沃移动通信有限公司 网络接入方法、网络接入装置、终端和网络侧设备
CN114339958A (zh) * 2020-09-29 2022-04-12 维沃移动通信有限公司 网络接入方法、网络接入装置、终端和网络侧设备
WO2023075667A1 (fr) * 2021-10-28 2023-05-04 Telefonaktiebolaget Lm Ericsson (Publ) Calcul de l'utilisation de blocs de ressources physiques dans une transmission de multiples points de transmission
WO2023079506A1 (fr) * 2021-11-05 2023-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Systèmes et procédés de fourniture d'informations de temps de référence pour une synchronisation temporelle
US12081307B2 (en) 2021-12-08 2024-09-03 Samsung Electronics Co., Ltd. Method for setting reception beam in electronic device receiving signals transmitted from plurality of TRPs and electronic device

Similar Documents

Publication Publication Date Title
US10925066B2 (en) Quasi co-location (QCL) for antenna ports in new radio (NR)
US10849152B2 (en) Beam management for carrier aggregation (CA)
US11012966B2 (en) Location positioning protocol based positioning for UEs in idle mode
US11864016B2 (en) Measurement design for next radio (NR) and long term evolution (LTE)
US20190357303A1 (en) Transmission scheme for common control message with multi-beam operation
US11044626B2 (en) Systems, methods, and apparatuses for configuring measurement gap per frequency group and per cell
WO2018085374A1 (fr) Informations de système spécifiques à un point d&#39;émission/réception
US11831494B2 (en) UE (user equipment) assisted measurement gap in NR (new radio)
US10848231B2 (en) User equipment measurements for new radio
US11082901B2 (en) Signaling of support for network controlled small gap, NCSG, for interruption control
US10856169B2 (en) Beam measurement and reporting in cellular networks
US20210385681A1 (en) Measurement Gap Enhancements
US20240196236A1 (en) Physical-layer cell identifier (pci) configuration and mobility robustness optimization for fifth generation self-organizing networks (5g son)
US11044660B2 (en) System information block (SIB) transmission for wide coverage enhancement (WCE)
US20190357068A1 (en) Reporting a number of effective frequencies for radio resource management purposes
US11096247B2 (en) System information in unlicensed narrowband internet of things (NB-IOT) systems
US20240206004A1 (en) Multiple cdrx configurations and dynamic configuration switching for xr traffic
US20230344492A1 (en) Fast measurement with multiple concurrent beams
US11930460B2 (en) SMTC2-LP based RRM enhancement
WO2018085727A1 (fr) Bidiffusion d&#39;informations à un équipement utilisateur d&#39;un réseau de télécommunication sans fil
US20240187916A1 (en) Configured grant enhancement
US20240064760A1 (en) Pdcch reliability enhancement for multi-trp operation
WO2024065505A1 (fr) Conception d&#39;intervalle de mesure pour atg
US20230180091A1 (en) Radio resource management relaxation for user equipment based on mobility state
US20210314854A1 (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: 17809082

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

Country of ref document: EP

Kind code of ref document: A1