WO2018190678A1 - Procédé et appareil permettant d'effectuer une connexion initiale dans un système de communication sans fil - Google Patents
Procédé et appareil permettant d'effectuer une connexion initiale dans un système de communication sans fil Download PDFInfo
- Publication number
- WO2018190678A1 WO2018190678A1 PCT/KR2018/004347 KR2018004347W WO2018190678A1 WO 2018190678 A1 WO2018190678 A1 WO 2018190678A1 KR 2018004347 W KR2018004347 W KR 2018004347W WO 2018190678 A1 WO2018190678 A1 WO 2018190678A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bwp
- block
- information
- carrier
- offset
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
Definitions
- the present invention relates to wireless communication, and more particularly, to a method and apparatus for performing an initial connection in a wireless communication system.
- 3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communication. Many approaches have been proposed to reduce the cost, improve service quality, expand coverage, and increase system capacity for LTE targets. 3GPP LTE is a high level requirement that requires cost per bit, improved service usability, flexible use of frequency bands, simple structure, open interface and proper power consumption of terminals.
- next-generation communication which considers reliability and delay-sensitive services / terminals (UEs).
- NR new radio access technology
- the wavelength is shortened, and thus a plurality of antennas may be installed in the same area.
- the wavelength is 1 cm, and a total of 100 antenna elements may be installed in a two-dimensional array in a 0.5 ⁇ (wavelength) interval on a panel of 5 ⁇ 5 cm 2. Therefore, in the mmW band, a plurality of antenna elements are used to increase the beamforming gain to increase coverage or to increase throughput.
- Hybrid beamforming with B transceivers which is less than Q antenna elements, may be considered as an intermediate form between digital beamforming and analog beamforming.
- the directions of beams that can be simultaneously transmitted are limited to B or less.
- the structure and / or related features of the physical channel of the NR may differ from existing LTE.
- various schemes can be proposed.
- the present invention provides a method and apparatus for performing an initial connection in a wireless communication system.
- the present invention discusses subband configuration and initial access procedure for wideband operation in new radio access technology (NR).
- NR new radio access technology
- a method of performing physical resource block (PRB) indexing by a user equipment (UE) in a wireless communication system includes receiving information about an offset between a synchronization signal (SS) block and a system bandwidth from a network via an SS block, and performing the PRB indexing on the system bandwidth based on the information about the offset.
- PRB physical resource block
- a user equipment (UE) in a wireless communication system includes a memory, a transceiver, and a processor connected to the memory and the transceiver, wherein the processor is configured to receive information about an offset between a synchronization signal (SS) block and a system bandwidth from the network through the SS block. And controlling the transceiver and performing physical index block (PRB) indexing on the system bandwidth based on the offset information.
- SS synchronization signal
- PRB physical index block
- 1 shows an NG-RAN architecture.
- FIG. 2 shows an example of a subframe structure in NR.
- 3 shows a time-frequency structure of an SS block.
- FIG. 4 shows an example of a system bandwidth and a bandwidth supported by the UE in an NR carrier.
- 5 shows an example of carrier combining.
- FIG 6 illustrates an example in which an anchor subband is configured separately from other subbands according to an embodiment of the present invention.
- FIG. 7 illustrates an example in which different UEs receive an SS block according to an embodiment of the present invention.
- FIG. 8 illustrates a method of performing PRB indexing by a UE according to an embodiment of the present invention.
- FIG. 10 illustrates a wireless communication system in which an embodiment of the present invention is implemented.
- FIG. 11 shows a processor of the UE shown in FIG. 10.
- the present invention will be described based on a new radio access technology (NR) based wireless communication system.
- NR new radio access technology
- the present invention is not limited thereto, and the present invention may be applied to other wireless communication systems having the same features described below, for example, 3rd generation partnership project (3GPP) long-term evolution (LTE) / LTE-A (advanced) or It can also be applied to the Institute of Electrical and Electronics Engineers (IEEE).
- 3GPP 3rd generation partnership project
- LTE long-term evolution
- LTE-A advanced LTE-A
- IEEE Institute of Electrical and Electronics Engineers
- the 5G system is a 3GPP system composed of a 5G access network (AN), a 5G core network (CN), and a user equipment (UE).
- the UE may be called in other terms such as mobile station (MS), user terminal (UT), subscriber station (SS), wireless device (wireless device), and the like.
- the 5G AN is an access network including a non-3GPP access network and / or a new generation radio access network (NG-RAN) connected to the 5G CN.
- NG-RAN is a radio access network that has a common characteristic of being connected to a 5G CN and supports one or more of the following options.
- NR is an anchor with E-UTRA extension.
- E-UTRA is an anchor with NR extension.
- the NG-RAN includes one or more NG-RAN nodes.
- the NG-RAN node includes one or more gNBs and / or one or more ng-eNBs.
- gNB / ng-eNB may be referred to in other terms, such as a base station (BS), an access point.
- the gNB provides NR user plane and control plane protocol termination towards the UE.
- the ng-eNB provides E-UTRA user plane and control plane protocol termination towards the UE.
- gNB and ng-eNB are interconnected via an Xn interface.
- gNB and ng-eNB are connected to 5G CN via NG interface. More specifically, gNB and ng-eNB are connected to an access and mobility management function (AMF) through an NG-C interface, and to a user plane function (UPF) through an NG-U interface.
- AMF access and mobility management function
- UPF user plane function
- gNB and / or ng-eNB provides the following functions.
- Radio resource management dynamic allocation (scheduling) of resources for the UE in radio bearer control, radio admission control, connection mobility control, uplink and downlink;
- IP Internet protocol
- QoS Quality of service
- NAS non-access stratum
- AMF provides the following main functions.
- Idle mode UE reachability (including control and execution of paging retransmission);
- SMF session management function
- Anchor points for intra / inter-radio access technology (RAT) mobility (if applicable);
- PDU protocol data unit
- Uplink classification to support traffic flow routing to the data network
- QoS processing for the user plane eg packet filtering, gating, UL / DL charge enforcement
- Uplink traffic verification QoS flow mapping in service data flow (SDF)
- SMF provides the following main functions.
- Control plane part of policy enforcement and QoS
- a plurality of orthogonal frequency division multiplexing (OFDM) numerology may be supported.
- Each of the plurality of neuralologies may be mapped to different subcarrier spacings.
- a plurality of neuralologies that map to various subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may be supported.
- Downlink (DL) transmission and uplink (UL) transmission in NR are configured within a 10 ms long frame.
- One frame consists of 10 subframes of length 1ms.
- Each frame is divided into two equally sized half-frames, half-frame 0 consists of subframes 0-4, and half-frame 1 consists of subframes 5-9.
- On the carrier there is one frame set in the UL and one frame set in the DL.
- Slots are configured for each numerology in a subframe. For example, in a neuralology mapped to a subcarrier spacing of 15 kHz, one subframe includes one slot. One subframe includes two slots in the neuralology mapped to a subcarrier spacing of 30 kHz. In a neuralology mapped to a subcarrier spacing of 60 kHz, one subframe includes four slots. One subframe includes eight slots in a neuralology mapped to a subcarrier spacing of 120 kHz. In the neuralology mapped to the subcarrier spacing 240 kHz, one subframe includes 16 slots. The number of OFDM symbols per slot may be kept constant. The starting point of the slot in the subframe may be aligned in time with the starting point of the OFDM symbol in the same subframe.
- An OFDM symbol in a slot may be classified as a DL symbol, an UL symbol, or a flexible symbol.
- the UE may assume that DL transmission occurs only in DL symbol or floating symbol.
- the UE may perform UL transmission only in the UL symbol or the floating symbol.
- the subframe structure of FIG. 2 may be used in a time division duplex (TDD) system of NR to minimize delay of data transmission.
- TDD time division duplex
- the subframe structure of FIG. 2 may be referred to as a self-contained subframe structure.
- the first symbol of the subframe includes a DL control channel and the last symbol includes an UL control channel.
- the second to thirteenth symbols of the subframe may be used for DL data transmission or UL data transmission.
- the UE may receive DL data in one subframe and transmit UL HARQ (hybrid automatic repeat request) -ACK (acknowledgement). .
- HARQ hybrid automatic repeat request
- ACK acknowledgement
- a gap may be required for the base station and the UE to switch from the transmission mode to the reception mode or from the reception mode to the transmission mode.
- some symbols at the time of switching from DL to UL in the subframe structure may be configured as a guard period (GP).
- the physical resource in the NR will be described.
- An antenna port is defined such that a channel carrying a symbol on an antenna port can be inferred from a channel carrying another symbol on the same antenna port. If the large-scale nature of the channel through which symbols are carried on one antenna port can be deduced from the channel through which symbols are carried on another antenna port, the two antenna ports may be in a quasi co-located relationship. Large scale characteristics include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial reception parameters.
- a resource grid composed of a plurality of subcarriers and a plurality of OFDM symbols is defined.
- the resource grid starts from a particular common resource block indicated by higher layer signaling.
- each element in the resource grid is called a resource element (RE).
- a resource block is defined as 12 consecutive subcarriers in the frequency domain.
- the reference RB is indexed in an increasing direction starting from zero in the frequency domain.
- Subcarrier 0 of the reference RB is common to all neutrals.
- the subcarrier at index 0 of the reference RB serves as a common reference point for other RB grids.
- the common RB is indexed in an increasing direction starting from zero in the frequency domain for each neutral.
- the subcarriers at index 0 of the common RB of index 0 in each neuralology coincide with the subcarriers of index 0 of the reference RB.
- Physical RBs (PRBs) and virtual RBs are defined within a bandwidth part (BWP) and are indexed in increasing directions starting from zero in the BWP.
- the BWP is defined as a contiguous set of PRBs selected from a contiguous set of common RBs, for a given carrier and given neuralology.
- the UE may be configured with up to four BWPs in the DL, and only one DL BWP may be activated at a given time.
- the UE is expected to not receive a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a channel state information reference signal (CSI-RS), or a tracking RS (TSR) outside the activated BWP.
- PDSCH physical downlink shared channel
- PDCCH physical downlink control channel
- CSI-RS channel state information reference signal
- TSR tracking RS
- the UE may be configured with up to four BWPs in the UL, and only one DL BWP may be activated at a given time.
- the UE may be configured with up to four BWPs in the SUL, and only one DL BWP may be activated at a given time.
- the UE cannot transmit a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) outside the activated BWP.
- PUSCH physical uplink shared channel
- PUCCH physical uplink control channel
- DM closed loop
- Up to eight and twelve orthogonal DL DM-RS ports support Type 1 and Type 2 DM-RSs, respectively.
- Up to eight orthogonal DL DM-RS ports per UE are supported for single-user multiple-input multiple-output (SU-MIMO), and up to four orthogonal DL DM-RS ports per UE are supported for MU-MIMO (multi-user) MIMO).
- the number of SU-MIMO codewords is one for 1-4 layer transmission and two for 5-8 layer transmission.
- the DM-RS and the corresponding PDSCH are transmitted using the same precoding matrix, and the UE does not need to know the precoding matrix to demodulate the transmission.
- the transmitter may use different precoder matrices for different parts of the transmission bandwidth, resulting in frequency selective precoding.
- the UE may also assume that the same precoding matrix is used over a set of PRBs referred to as a precoding RB group (PRG).
- PRG precoding RB group
- DL physical layer processing of a transport channel consists of the following steps:
- LDPC low-density parity-check
- Quadrature phase shift keying QPSK
- quadrature amplitude modulation 16-QAM
- 64-QAM 64-QAM
- 256-QAM 256-QAM
- the UE may assume that at least one symbol with DM-RS exists on each layer where the PDSCH is sent to the UE.
- the number of DM-RS symbols and resource element mapping are configured by higher layers.
- the TRS may be sent on additional symbols to assist receiver phase tracking.
- the PDCCH is used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH.
- Downlink control information (DCI) on the PDCCH includes the following.
- a DL allocation comprising at least a modulation and coding format, resource allocation and HARQ information associated with a DL shared channel (DL-SCH);
- a UL scheduling grant comprising at least a modulation and coding format, resource allocation and HARQ information associated with a UL shared channel (UL-SCH).
- UL-SCH UL shared channel
- the control channel is formed by a set of control channel elements, each control channel element consisting of a set of resource element groups. By combining different numbers of control channel elements, different code rates for the control channel are realized. Polar coding is used for the PDCCH. Each resource element group carrying a PDCCH carries its own DM-RS. QPSK modulation is used for the PDCCH.
- a synchronization signal and a physical broadcast channel (PBCH) block (hereinafter referred to as SS block) are a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) occupying 1 symbol and 127 subcarriers, respectively. signal) and three symbols and a PBCH that spans 240 subcarriers but leaves unused portions in the middle for SSS on one symbol.
- the transmission period of the SS block can be determined by the network, and the time position at which the SS block can be transmitted is determined by the subcarrier interval.
- Polar coding is used for PBCH.
- the UE may assume band specific subcarrier spacing for the SS block, unless the network configures different subcarrier spacing to the UE.
- the PBCH symbol carries its frequency multiplexed DM-RS.
- QPSK modulation is used for the PBCH.
- broadband may be used if the network supports it.
- the bandwidth supported by the network and the UE may be different. At this point, it needs to be clearly defined how the network and the UE will perform transmission and / or reception.
- FIG. 4 shows an example of a system bandwidth and a bandwidth supported by the UE in an NR carrier.
- a bandwidth supported by a network is a system bandwidth.
- the network may combine NR carriers.
- the bandwidth supported by the UE may correspond to the above-described BWP.
- 4- (a) shows a case where the system bandwidth and the bandwidth supported by the UE are the same.
- 4- (b) shows a case where the system bandwidth and the bandwidth supported by the UE are different.
- the bandwidth supported by the UE is smaller than the system bandwidth.
- the bandwidth supported by the UE may be larger than the system bandwidth.
- RF elements may share baseband elements.
- separate baseband elements may be assigned for each RF element. It is assumed herein that multiple RF elements can share baseband elements / capabilities. This may depend on the UE capability.
- the system bandwidth may be changed, and the center frequency may also be changed.
- the DC (direct current) subcarrier may or may not change according to network operation. If the DC subcarrier is changed, it can be instructed to the UE so that the DC subcarrier can be properly processed.
- a synchronization signal (SS) block including a primary synchronization signal / secondary synchronization signal / PBCH (physical broadcast channel)
- the anchor subbands and subbands of the SS block are included. Relationships can vary. The following options may be considered to place the anchor subbands.
- the subband may correspond to the above-described BWP.
- the anchor subband may be called another name, such as an initial BWP.
- the anchor subband may be located only in any one of the determined subbands.
- the subband size is determined based on the system bandwidth, and the anchor subband may be located in only one of them. For example, assuming that the system bandwidth is 400 MHz and the subband size is 100 MHz, the anchor subband may be located in any one of the four subbands.
- the SS block may be located anywhere in the anchor subband fluidly. On the other hand, if there are different bandwidths supported by the network in the same frequency band, it may be desirable to arrange the different bandwidths.
- the subband size of 100 MHz aligns the different bandwidths between the cells in the same frequency band. It can help you.
- the position of the SS block may be limited by this alignment.
- the subband configuration may be defined for each frequency range or for each frequency band.
- the number of subbands may be one, and the subband size may be equal to the system bandwidth. That is, subbands may not be supported in frequency bands that are the same as or overlap with LTE frequency bands.
- the NR frequency band is redefined to span one or more LTE frequency bands, some UE may not support the system bandwidth.
- a fixed subband size eg, 20 MHz or 10 MHz
- the position of the SS block may be limited by the subband size. That is, some sync rasters may not be used for sync signal mapping. This is because the SS block is configured over the subbands (ie, not entirely included in one subband). The UE does not need to find the sync raster because there is no sync signal mapping in the sync raster.
- Anchor subbands may be configured based on initial synchronization. Based on the SS block, it can be assumed that the center of the SS block is the master of the anchor subband, and the anchor subband can be configured implicitly.
- the size of the anchor subband may be predetermined or defined by a master information block (MIB) in the SS block. In this case, when frequencies in which the SS blocks are transmitted are different between neighboring cells, subbands may not be aligned between neighboring cells. In addition, the subcarriers and the RB grid may not be aligned.
- MIB master information block
- Anchor subbands may be configured separately from other subbands. That is, the subband configuration may be configured based on the system bandwidth, or may be preconfigured for each frequency range or frequency band, and the anchor subband in which the SS block is transmitted may not be connected to the subband configuration. Thus, the SS block can be transmitted anywhere, and the anchor subbands can be configured to partially or completely overlap with other subbands.
- FIG. 6 illustrates an example in which an anchor subband is configured separately from other subbands according to an embodiment of the present invention.
- the UE is configured to support three subbands.
- the anchor subband is configured separately from the three configured subbands.
- the anchor subband is configured over subband 1 and subband 2, and the SS block is transmitted through the anchor subband.
- the set of subbands can be known to the UE through group common signaling.
- a plurality of analog beams may be configured for one SS block transmission.
- the UE After detecting the SS block, the UE assumes that the optimal combination of beams detected in the SS block will be used for control channel transmission.
- the best combination of beams detected in the SS block may be called a wide beam. Since there may be a plurality of beams within a wide beam, the same information may be transmitted through different beams. For example, if the UE knows the number of beams in the SS block and the UE detects an optimal beam in a plurality of beams in a wide beam, the UE will only monitor the optimal beam to minimize power consumption for control channel monitoring. Can be.
- the network may configure CSS and / or UE-specific search space (USS) and / or group common SS based on the information. That is, the network may define the CSI-RS resource in the QCL relationship for the control channel based on the corresponding information. That is, before the CSI-RS configuration, the SS block for control channel monitoring may be implicitly configured to the UE. After CSI-RS configuration, the CSI-RS resource to be QCLed for control channel monitoring may be indicated to the UE.
- USS UE-specific search space
- the present invention describes a method of receiving an SS block including a PSS / SSS / PBCH in connection with an initial access procedure and configuration of an NR.
- the initial BWP (or anchor subband) that includes the SS block may be changed based on the UE procedure.
- the BWP1 including the SS block read by UE1 and the BWP including the SS block read by UE2 are different from each other, and both BWPs are smaller than the system bandwidth.
- the centers of the two BWPs are separated by different offsets from the center of the system bandwidth.
- the basic BWP may be configured to include the SS block according to the UE capability. That is, if the UE minimum bandwidth is greater than the sum of the RMSI bandwidth and the SS block bandwidth, and the RMSI CORESET and SS blocks are successively multiplexed by frequency division multiplexing (FDM), the initial BWP can cover both the RMSI CORESET and SS block bandwidth. have. Otherwise, the initial BWP may cover the RMSI CORESET.
- FDM frequency division multiplexing
- the network After the network knows the bandwidth supported by the UE, it can reconfigure the base BWP to the UE, which can include the SS block and the required RMSI CORESET bandwidth. If the UE reads the SS block, the SS block bandwidth can be assumed as the UE bandwidth.
- the PBCH included in the SS block may include at least one of the following information. However, the information described below may be transmitted through RMSI or UE specific signaling as well as PBCH. In particular, for a secondary cell (SCell), UE specific signaling is required to transmit the following information.
- SCell secondary cell
- MIB transmitted over PBCH may include information on carrier bandwidth.
- the information on the carrier bandwidth may have a size of 3 bits.
- the information on the carrier bandwidth may include information on a set of carrier bandwidths. For example, at a bandwidth of 6 GHz or less, 5, 20, 40, 80, 100 MHz may be indicated, and at a bandwidth of 6 GHz or more, 100, 200, 400 MHz may be indicated.
- the actual bandwidth supported by the network may also be indicated.
- the information on the carrier bandwidth may include information on the potential maximum bandwidth on which the carrier is operating. That is, the UE does not need to make any assumptions about the system bandwidth since the indicated carrier bandwidth is the potential maximum bandwidth.
- several states and / or reserved fields may be used for future upward compatibility.
- the reserved field may indicate additional maximum system bandwidth, and the future UE may assume the sum of the original carrier bandwidth and the additional maximum system bandwidth indicated by the reserved field as the maximum system bandwidth.
- MIB transmitted over PBCH may not include information about carrier bandwidth.
- the carrier bandwidth may be indicated in SI such as RMSI.
- SI such as RMSI.
- one or more fields may be used to imply system information.
- no information about system bandwidth may be indicated.
- the PRB index may be performed based on a maximum bandwidth such as 1 GHz or 400 PRBs.
- PRB indexing may be performed in two groups: 0-399 and 400-X.
- the common data / control signal may be scheduled in the PRB with an index of 0-399 shared with the UE supporting the previous release. Other data / control signals can be scheduled to all PRBs.
- PRB indexing may be performed virtually from the lowest frequency.
- the maximum number of PRBs may be different. For example, when the maximum system bandwidth is 400 MHz, the maximum number of PRBs is 278 when based on 120 kHz subcarrier spacing and the maximum number of PRBs is 139 when based on 240 kHz subcarrier spacing.
- the MIB transmitted on the PBCH may include information on the offset between the center of the SS block and the center of the system bandwidth. Since the center of the SS block and the center of the system bandwidth are different from each other, this information may be directed to the UE. This may be included in the PBCH regardless of whether information on the carrier bandwidth is included in the PBCH. If the information about the carrier bandwidth is included in the PBCH, or if the RMSI bandwidth is the same as the PBCH bandwidth, the PBCH may include information about the offset between the center of the SS block and the center of the system bandwidth.
- the PBCH is the center and system bandwidth of the PBCH or RMSI instead of information about the offset between the center of the SS block and the center of the system bandwidth. It may include information about the offset between the center of.
- the MIB transmitted on the PBCH may also include information on the offset between the PRB and the virtual PRB 0 of the lowest index of the SS block. More specifically, the MIB transmitted through the PBCH may include information about the offset between the subcarrier (subcarrier 0) of the lowest index of the SS block and the subcarrier (subcarrier 0) of the lowest index of the common RB.
- Information about the offset between the center of the SS block and the center of the system bandwidth may be expressed as a value for the channel raster (or sync raster). Assuming the channel raster is 100 kHz, the following options can be considered.
- Option 1 Use channel raster with ⁇ 6, 8, 9, 10, 10 ⁇ bits for ⁇ 5, 20, 40, 80, 100 ⁇ MHz bandwidth in frequency bands below 6 GHz
- Option 2 Use synchronous raster and offset with channel raster
- Option 3 Use RB bandwidth and offset using the number of subcarriers.
- offset related information may be omitted.
- the channel raster is assumed to be 240 kHz, or a plurality of subcarriers or one or more RB bandwidths based on the neuralology used for RMSI (or PSS / SSS / PBCH) are used, the following options may be considered.
- Option 1 Use channel raster with ⁇ 9, 10, 11 ⁇ bits for ⁇ 100, 200, 400 ⁇ MHz bandwidth
- Option 2 Use synchronous raster (eg 1440 kHz) with ⁇ 7, 8, 9 ⁇ bits for ⁇ 100, 200, 400 ⁇ MHz bandwidth
- Option 3 Use RB bandwidth and offset using the number of subcarriers.
- offset related information may be omitted.
- the information on the offset between the center of the SS block and the center of the system bandwidth may be expressed as positive or negative depending on whether the center of the system bandwidth is higher or lower than the center of the SS block.
- the information about the carrier bandwidth when the information about the carrier bandwidth is included in the PBCH, the information about the offset between the center of the SS block and the center of the system bandwidth may be the maximum bit assuming the maximum bandwidth supported by the carrier.
- the UE can perform common PRB indexing over the system bandwidth, in addition to the PRB indexing (ie, local PRB indexing) at the BWP configured for it.
- the concept of local / common PRB indexing described above may be used for scrambling of control signals / data / reference signals (RSs) and / or RS generation on initial CSS and / or common data scheduling within a BWP of a UE.
- RSs control signals / data / reference signals
- RS generation and / or common data scheduling on initial CSS may be performed based on system bandwidth and common PRB indexing.
- common PRB indexing may be used for scrambling control signals / data / RSs and / or RS generation on initial CSS and / or scheduling common data. have. If RMSI CORESET is shared for other radio network temporary identifier (RNTI) monitoring, local scrambling / PRB indexing can be used for RMSI control signal / data monitoring, and monitoring of other channels (non-RMSI control signal / data) Common scrambling / PRB indexing may be used for this purpose.
- RNTI radio network temporary identifier
- local scrambling / PRB indexing may always be used if CORESET is configured with wideband and RMSI CORESET is shared with other transmissions. That is, RS sequence related parameters (eg, length, offset, etc.) may be configured for each CORESET. Alternatively, this method can be applied only when broadband is configured. That is, the RS sequence related parameters (eg, length, offset, etc.) may be configured explicitly or implicitly for each CORESET when the broadband is configured. For example, if wideband is used by default, local scrambling / PRB indexing may be used for RMSI CORESET. Similar schemes can be applied to RS sequence generation.
- Different RS sequences may be generated / used depending on whether the UE knows common PRB indexing for data.
- the RMSI PDSCH may use an RS sequence based on local PRB indexing, and another PDSCH may use an RS sequence based on common PRB indexing.
- local scrambling / PRB indexing may be used for all common control signal transmissions.
- Local scrambling / PRB indexing or common scrambling / PRB indexing may be used for common data transmission.
- Common scrambling / PRB indexing may be used for non-common control signal / data transmission, such as group common or UE specific signaling.
- scrambling and / or DM-RS sequence related parameters / configuration may be performed for each BWP, and the initial DL / UL BWP may assume local scrambling / PRB indexing.
- scrambling of control signals / data / RSs and / or RS generation and / or common data scheduling on initial CSS may be performed based on the maximum system bandwidth.
- the maximum system bandwidth may be defined as K times the actual maximum system bandwidth defined for each frequency band or frequency range.
- Resource allocation for data scheduling may be performed based on the configured bandwidth (ie, initial BWP). That is, regardless of common PRB indexing based on system bandwidth or potential maximum system bandwidth, resource allocation for data scheduling can be performed based on local PRB indexing.
- FIG 8 illustrates a method of performing PRB indexing by a UE according to an embodiment of the present invention.
- the present invention described above can be applied to this embodiment.
- the UE receives information about the offset between the SS block and the system bandwidth from the network through the SS block.
- the information about the offset may be information about an offset between the PRB of the lowest index of the SS block and the PRB of the lowest index of the system bandwidth.
- the offset information may be information about an offset between subcarrier 0 of the SS block and subcarrier 0 of the system bandwidth.
- the information about the offset may be information about an offset between the center of the SS block and the center of the system bandwidth.
- the SS block may further include information about the system bandwidth.
- the information about the system bandwidth may include information about the potential maximum bandwidth at which the carrier is operating.
- the SS block may be included in an initial UL BWP.
- the information on the offset may be represented by a value of the channel raster or the sync raster.
- the UE may perform the PRB indexing for the system bandwidth based on the information on the offset.
- the UE may perform common PRB indexing. Scrambling of a control signal, data, or reference signal may be performed based on the PRB indexing with respect to the system bandwidth.
- a reference signal may be generated based on the PRB indexing for the system bandwidth.
- 9 shows an example of reception of an SS block according to an embodiment of the present invention.
- 9- (a) shows a system bandwidth, and common PRB indexing is defined for a PRB included in the system bandwidth.
- the center of the system bandwidth and the center of the SS block do not coincide, so information about the offset between the center of the SS block and the center of the system bandwidth or information about the offset between the PRB of the lowest index of the SS block and PRB 0 of the system bandwidth. May be directed to the UE.
- FIG. 9- (a) it is assumed that the center of the SS block is aligned with the 15 kHz synchronization raster.
- 9- (b) shows a bandwidth configured for a UE, that is, a BWP, and local PRB indexing is defined for a PRB included in the BWP. Regardless of common PRB indexing, resource allocation for data scheduling may be performed based on local PRB indexing.
- PRB indexing / scrambling according to each control signal / data may be as follows.
- PRB indexing / scrambling within system bandwidth or maximum bandwidth (e.g., virtual PRBs based on common PRB indexing)
- PRB indexing / scrambling within the configured BWP which may or may not be the same as the data bandwidth (eg, the bandwidth for the subband).
- PRB indexing / scrambling based on system bandwidth or BWP eg, carrier bandwidth or maximum bandwidth
- BWP carrier bandwidth or maximum bandwidth
- PRB indexing / scrambling may be performed based on the BWP or the allocated PRB. In the case of non-contiguous resource allocation, scrambling or sequence generation may be performed based on the bandwidth between the first PRB and the last PRB of the resource allocation. Alternatively, scrambling or sequence generation may be performed based on common PRB indexing on BWP or maximum system bandwidth.
- PRB indexing / scrambling may be performed based on CORESET or BWP using system bandwidth or shared reference signal.
- scrambling or sequence generation may be performed based on common PRB indexing on BWP or maximum system bandwidth.
- PRB indexing / scrambling may be performed based on CORESET or BWP using system bandwidth or shared reference signal. Alternatively, scrambling or sequence generation may be performed based on common PRB indexing on BWP or maximum system bandwidth.
- indexing the sequence of control signals / data / reference signals starting from the center frequency up to the maximum bandwidth or the maximum PRB index may be considered.
- the maximum PRB index may be predetermined or may be indicated by the PBCH / SIB. Considering the maximum PRB index, the PRB index near the center frequency may be around max_PRB / 2. Otherwise, it can be difficult when UEs with different bandwidths share the same resources for control signals / data / reference signals.
- common scrambling / PRB indexing may be used for at least shared control signals / data / reference signals, and local scrambling / PRB indexing may be used for UE-specific shared control signals / data / reference signals.
- CA carrier aggregation
- the carrier is defined as a basic BWP
- the UE may be configured as a basic BWP for each carrier.
- a plurality of BWPs may be configured based on the basic BWP.
- the basic BWP may be defined as the basic BWP of the carrier on which the SS block is a reference. For example, if an SS block or time / frequency synchronization (coarse synchronization) is obtained from an SS block of another carrier, the basic BWP of one carrier may be defined as a BWP including an SS block of another carrier. That is, the BWP of another frequency band or carrier including the synchronization reference such as SS block may be used as the basic BWP of the carrier.
- the basic BWP may be defined as a set of PRBs configured in the same carrier.
- the basic BWP may or may not include an SS block. If it does not include the SS block, the basic BWP should include a time synchronization criterion, potentially including a CSI-RS or beam management RS or other tracking RS or the like.
- the UE may acquire additional tracking via configured RS such as beam management RS / tracking RS.
- the basic deactivated SCell may be configured, and the configuration of the SCell may be configured of the deactivated basic BWP at the time of configuration.
- the basic BWP may be configured regardless of the position of the SS block. However, this may limit some measurement-related features, similar to a PCell (primary cell).
- the configuration of the carrier may include the frequency position of the DL and UL (or one of the two in the case of an unpaired spectrum).
- the -Basic BWP can be activated when carrier is configured.
- the basic BWP may be used for measurement of RRM (radio resource management), basic beam management, etc. Therefore, the basic BWP may be activated when the carrier is configured.
- the primary BWP may be associated with a CORESET in another carrier or may be associated with one or more configured CORESETs in the configured basic BWP.
- the UE may not assume that one of them is automatically activated when one or more BWPs are further configured. That is, the UE may be explicitly instructed about activation of one or more BWPs among the configured BWPs.
- the period of the monitoring section for each reset may be configured differently. More generally, periods of different monitoring intervals for a given CORESET may be indicated through downlink control information (DCI) or media access control (MAC) control elements (CE). Accordingly, different monitoring intervals may be supported for the base BWP before any active BWP is available, before the BWP is activated and the carrier is activated, or between the discontinuous reception (DRX) inactivity timer and the active timer. Can be. If the period of the monitoring interval is changed, the indication for this may be transmitted through the same DCI without changing the BWP.
- DCI downlink control information
- CE media access control elements
- the period of the monitoring interval of the BWP configured for a given BWP in the activation of the BWP may also be indicated.
- separate DCIs may be used to enable periods of different monitoring intervals.
- DCI or MAC CE for changing the beam direction may be used to reconfigure or change the CORESET related parameters. That is, a DCI for dynamically changing a set of parameters for CORESET including a beam direction, a period of a monitoring interval, scrambling, and the like may be defined.
- the carrier is defined as a center frequency position or a reference frequency position and an offset from the lowest index to the PRB, and may be configured to the UE through SCell configuration.
- a reference neuralology used in the SCell may be configured, and the reference neuralology may be used for offset.
- reference may be made to the SS block or SS block of another carrier for synchronization.
- the UE assumes that the carrier is deactivated.
- the UE may be composed of a plurality of BWPs, and then a switching mechanism of a single carrier or PCell may be used between the plurality of BWPs. It is assumed that SCell activation is performed when at least one BWP is activated in a carrier.
- the reference frequency position may be the frequency position of the SS block if the carrier includes the SS block, or may be a virtual or center frequency position at which the UE will attempt to retune for measurement.
- the UE may be configured with the following information.
- the Cell ID can be obtained by the SS block.
- the reference SS block may use a cell ID different from the cell ID used for the SCell. That is, the cell ID may be given to the UE.
- the position of the SS block may be used to obtain coarse time / frequency synchronization, and another cell ID may be used within the SS block. For example, it is based on SS blocks in other carriers. However, SS blocks in other carriers are from the UE's point of view, and may still be seen as SS blocks in the same carrier from the network point of view.
- PRB 0 may not be the actual PRB 0 of the carrier.
- the PRB grid is constructed from PRB 0, which may not be aligned with the center of the SS block.
- the neuralology can be used for control signals and data.
- SCell can support multiple neutralities.
- the basic neuralology may be configured through the SCell configuration, and another neuralology may be additionally configured through the RRC signaling.
- a cell can be defined as a combination of cell ID, reference point, reference of the SS block (or difference from the reference point), and potential maximum bandwidth.
- the SCell may be configured and the SCell may remain inactive.
- the SCell may not have an activated BWP until the activated BWP is explicitly indicated or the SCell is explicitly activated.
- the UE does not need to monitor the CORESET in the SCell.
- the SCell can be activated when configured as the basic BWP. That is, a CORESET capable of transmitting an activation DCI for each basic BWP configuration may be configured for a cell other than the PCell. If the CORESET is in the same BWP, the UE assumes that the default BWP is active at the time of configuration, and can then switch to another BWP. If the CORESET is in another carrier, the SCell remains inactive and cross carrier or cross BWP scheduling may be used for activation of the BWP in the SCell of that other carrier.
- the base state of the base BWP may be active. That is, there may be at least one BWP that is automatically activated when the SCell is activated, and the BWP may include an associated CORESET configuration in the SCell configuration.
- the CORESET may be cross-carrier scheduled by the PCell or another SCell.
- configuration / reference CORESET for the primary BWP can be used for control channel monitoring.
- the configuration of the CORESET for the basic BWP may follow any one of the following.
- PCell CSS or USS can be considered a CORESET to enable the carrier or BWP in the SCell.
- the configuration of the BWP may include an associated SS block (if not given, assume an SS block for initial connection) or a basic BWP.
- the BWP configuration may include CORESET information that can be monitored by self BWP scheduling or cross BWP scheduling for a given BWP.
- the UE may be configured with one or more BWPs, and at least one BWP may be indicated with a default BWP that is automatically activated upon activation.
- the UE may be configured with a combination of cell ID, reference point, SCell index (if available, for example, at cell activation) for the SCell.
- the UE may be configured with a separate CORESET for each BWP, or may be configured with a CORESET configuration for at least the basic BWP.
- the UE may be configured separately for the measurement target for the SCell.
- the same configuration as the SCell configuration may be given from the BWP perspective.
- the initial BWP for initial connection may be used as the basic BWP. If assistance information from the PCell is considered, the base BWP may also be indicated.
- the UE may assume that the initial connection is performed at the basic BWP. That is, the basic BWP may be indicated for the PSCell, and help information for initial access may be located in the basic BWP.
- the basic BWP needs to have an associated CORESET within the same carrier.
- MAC CE for activation of one or more SCells may be used, and the default BWP may be activated automatically.
- (2) MAC CE activation for activation of one or more BWPs may be simultaneously performed for each SCell for the configured SCell.
- the UE may assume that the SCell is activated when at least one BWP is activated.
- the SCell may be activated only when at least one DL BWP is activated.
- PRACH physical random access channel
- Scheduling DCI may be used to activate one or more BWPs in the configured PCell / SCell. Separate scheduling DCI may be used for each BWP activation, and cross carrier or cross BWP scheduling may be configured to allow activation between BWPs regardless of the carrier to which the BWP belongs. That is, for example, if carrier x has BWP1 and BWP2, BWP1 may be activated by BWP3 in carrier y, and BWP2 may be activated by BWP4 in carrier z. If there are a plurality of BWPs, one or more BWPs may be cross-carrier or cross-BWP scheduled, and the remaining BWPs may be self BWP scheduled. That is, separate cross carrier or cross BWP scheduling may be supported.
- a separate DCI can be used instead of MAC CE.
- a BWP connected during an initial access procedure may be considered a basic BWP.
- the RMSI bandwidth may be considered as DL base BWP.
- the RACH bandwidth may be considered as the UL base bandwidth.
- the UL base bandwidth may be equal to the DL base bandwidth (in addition to the TX-RX or duplex gap).
- a BWP with SS blocks for time / frequency synchronization and SS block based measurements may be configured as a fallback BWP. That is, when the UE transitions to the idle state, the default BWP may be the initial BWP, or a separate fallback BWP may be configured for fallback purposes.
- the BWP may be configured differently for each UE for load balancing of paging, and each BWP may include an SS block that may be different from an SS block to which the UE initially connects. If the UE is directly configured with another BWP including an SS block capable of using a different cell ID than the initial SS block to which the UE is connected, the UE may keep the two SS blocks QCLed. That is, if the UE is reconfigured to a different BWP from the initial BWP connected during the RRC connection establishment or idle state, the UE may assume that the initially connected SS block and the reconfigured SS block have QCL relationships with each other. Alternatively, the QCL relationship may be explicitly indicated. The UE may reacquire or perform the initial access procedure, or may perform handover if the new SS block does not have a QCL relationship with the initially connected SS block.
- the initial BWP may be configured to be activated simultaneously with SCell activation. Assuming that measurements can be performed prior to activation, the initial BWP may not be associated with the SS block in the SCell.
- an initial BWP connected in RRC connection establishment phase or idle state which may include the SS block in the PCell.
- the SCell may not have an initial BWP, and the PSCell needs to have an initial BWP.
- the initial BWP can be considered the default BWP until it is reconfigured.
- the basic BWP may be reconstructed and the reconstructed basic BWP may not have an SS block. If the reconstructed basic BWP has an SS block, the UE may consider the following.
- the UE can switch to the new SS block. This can be done by explicit construction of the QCL relationship. Or, if the UE is reconfigured to the primary BWP, and the new primary BWP is indicated to have an SS block, the UE may assume that there is a QCL relationship between the new BWP and the initial BWP.
- the UE may be instructed that there is no QCL relationship between the two, and the UE may perform rate matching only on the new SS block.
- the UE can automatically assume that the new BWp has a QCL relationship with either the initial BWP or the previous BWp.
- DL carriers may be associated with UL carriers in different bands. This feature can be considered for the following reasons.
- the number of UL carriers is smaller than the number of DL carriers, so one or more DL carriers may be associated with the same UL carrier.
- the DL carrier may be associated with only one UL carrier (ie, UL carrier or SUL carrier in the same band) or may be associated with both UL carriers (such as UL CA).
- UL carrier ie, UL carrier or SUL carrier in the same band
- both UL carriers such as UL CA
- a UL carrier corresponds to a UL spectrum in a paired DL / UL spectrum
- activation / deactivation of the UL carrier may be performed independently. Otherwise, the UL carrier can be changed automatically or simultaneously with the DL carrier in the same frequency band. That is, the DL carrier in the same frequency band becomes the main carrier, and thus UL BWP may be changed.
- the switching command of the UL BWP may be transmitted only on the primary DL carrier. That is, another DL carrier may follow a switching command of UL BWP on the primary DL carrier. However, this may cause ambiguity, especially when the UE misses a switch order of UL BWP and another DL carrier has scheduled PUSCH / PUCCH.
- other DL carriers may also indicate UL BWP, and a network may select the same BWP between different DL carriers.
- the PUCCH offset may change according to the change of the UL BWP. Therefore, if different DL carriers indicate different UL BWPs at different times, it may cause confusion of PUCCH resources. For example, when two UL BWPs are configured and two DL carriers can dynamically indicate switching of UL BWP, the first DL carrier instructs to switch UL BWP from UL BWP 1 to UL BWP 2 and The UE may miss the command. In this case, if the second DL carrier transmits the PDSCH, it is ambiguous which PUCCH resource should be used. This is also the case when the DL carrier and the UL carrier are mapped one to one. To this end, the network may monitor both PUCCH resources, or the scheduling DCI for PDSCH may include PUCCH BWP information as a resource indication. That is, scheduling DCI for PDSCH may be used for switching of UL BWP.
- DL slot n through n + m may be mapped to HARQ-ACK on a single PUCCH resource, and the UL BWP carrying PUCCH may be changed in the middle of DL slot n through n + m.
- switching of the UL BWP carrying the PUCCH may not be allowed during the accumulation of HARQ-ACK on a plurality of slots.
- UL BWP for a new PUCCH may be used during accumulation of HARQ-ACK on a plurality of slots, and resources selected for previous UL BWP may be ignored.
- the DCI for the new UL BWP may include new resources.
- the UE may miss the switch order of UL BWP, the following may be considered in this case.
- a new resource may be selected. If the UE misses a new resource indication, information about the conventional UL BWP may be used. If the UE receives a switch command of the UL BWP after the DCI scheduling the PDSCH, the resources indicated in the DCI may be used for the new UL BWP. Or, the UL BWP and resources carrying the PUCCH may be dynamically indicated.
- DCIs indicating different UL BWPs may not be multiplexed on the same PUCCH.
- a new UL BWP configuration may always be used.
- a plurality of BWPs may be configured for each UL carrier, and one BWP may be activated / deactivated.
- BWP configuration common PRB indexing for the SUL carrier may be performed. For example, information about the center or reference point of the SUL carrier and the offset between the smallest PRBs (virtual PRBs) from the center or reference point of the SUL carrier may be indicated, based on which common PRB indexing for the SUL carrier is Can be performed. If the UL BWP is changed, the PUCCH resource may also be changed.
- the basic UL BWP may be assumed to be the UL BWP used for the RACH procedure.
- the basic BWP may later be reconfigured or changed by a PRACH trigger on another carrier or other UL BWP.
- a PRACH resource used for PRACH trigger can be configured, and the trigger message can include a BWP index for switching of the UL BWP.
- the UE may then perform the RACH procedure in the new initial / base UL BWP. That is, the basic UL BWP may be changed semi-statically or dynamically based on the RACH procedure.
- the necessary information related to the cell ID used in the UL carrier in the same band as the SUL carrier and the DL carrier may be the same as if they are in different BWPs and are in the same carrier.
- the UL BWP switching between the UL carriers in the same band as the SUL carrier and the DL carrier may be used for switching between two UL carriers.
- the PUCCH carrier / cell and the PRACH carrier / cell may be in the same carrier. That is, a basic UL BWP in which a UE performs a PRACH and transmits a PUCCH may be configured in the same UL carrier. That is, for at least the PCell, the PUCCH may not be configured in a carrier / cell in which the PRACH will not be transmitted. In the case of the SCell, the PUCCH may be configured between two UL carriers.
- UL CA including a single DL carrier or DL CA.
- only activation of the UL carrier needs to be supported, and activation of the UL carrier may be performed by carrier activation / deactivation.
- Different carriers may include only DL carriers, only UL carriers, or may include DL / UL carriers connected in pairs.
- paired DL / UL carriers and UL dedicated carriers may be activated.
- At least one activated UL BWP may be configured in a paired DL / UL carrier and a UL dedicated carrier.
- a paired DL / UL carrier does not mean a paired spectrum.
- the paired DL / UL carriers are located at the same frequency.
- the UE may transmit a PRACH on the SUL carrier.
- the SUL carrier may be automatically activated together with the paired UL carriers.
- either one of two UL carriers may be selected, and only the UL carrier selected by the activation message may be activated.
- additional UL carriers may be activated by explicit indication. In the PCell, this may mean that a UL carrier including an UL BWP in which PRACH transmission is initiated is an activated UL carrier.
- the UL BWP can be activated on both the SUL carrier and non-SUL carrier.
- the above procedure can be applied for the initial UL BWP in the PCell.
- the network is PUCCH It may indicate the UL BWP to be activated for transmission.
- the UL BWP indicated in the PUCCH carrier configuration may be activated.
- the initial UL BWP configured by the RMSI or the higher layer may be activated in the PUCCH carrier configuration.
- the activated UL BWP may be changed by RRC reconfiguration or DCI conversion.
- BWP conversion for the SUL carrier may be performed through the UL grant for the SUL carrier. If the dynamic PUSCH change is not configured and the SUL carrier is selected as the PUCCH carrier, only DL BWP conversion may be possible regardless of the BWP pair for DL / UL carriers not connected in pairs.
- the PUCCH resources should also be adapted. For this purpose, the following can be considered.
- UL BWP carrying PUCCH can always be configured based on UL BWP configuration.
- different PUCCH resources may be configured for different UL BWP configurations. This is similar to that CORESET in DL BWP can be configured for each DL BWP.
- the UL BWP carrying the PUCCH can always be configured separately from the UL BWP carrying the PUSCH, and the UE can be sure that the full bandwidth including the UL BWP carrying the PUCCH and the UL BWP carrying the PUSCH is within the UE's capabilities. .
- the UE may be configured / instructed to switch the UL BWP carrying the PUSCH, which may not require switching of the PUCCH resources.
- This is currently supported in CA UE is configured with UL BWP in SCell that does not have PUCCH resources, and PUCCH is transmitted in PCell.
- the PUCCH and the PUSCH may be configured with different UL BWPs.
- the activated UL BWP may be defined as a UL BWP carrying a PUSCH instead of a UL BWP carrying a PUCCH.
- each UL BWP includes only PUCCH, only PUSCH, only PUCCH and PUSCH, only PUSCH / PRACH / SRS (sounding reference signal), or includes both PUCCH / PUSCH / PRACH / SRS It may also be configured. That is, which signal is transmitted within the configured UL BWP may be configured, and a plurality of BWPs may be configured.
- a set of PRBs accessible by resource allocation may also be configured.
- one UL BWP may be configured at 20 MHz for PUCCH diversity, and scheduling may only occur within 5 MHz. In order to reduce the scheduling overhead, it may be considered to configure the PUSCH PRB region separately.
- the signaling proposed in the above description may be transmitted through common signaling such as on-demand SI (RSI) / OSI or UE specific signaling and / or DCI.
- RSI on-demand SI
- OSI on-demand SI
- UE specific signaling e.g., CSI
- DCI digital signaling
- RRC ambiguity may occur. In order to minimize RRC ambiguity, the following can be considered.
- the RRC message When the RRC message is transmitted to change the BWP, the RRC message may include both the DL BWP and the UL BWP, and may also include an enforcement time point at which the configuration is implemented. Prior to enforcement, the network may perform retransmissions to increase reliability.
- the network may consider the new configuration to be enforced after receiving approval from the UE. This can cause ambiguity if the network misses approval.
- the network can retransmit RRC messages from the previous BWP and the currently active BWP to increase reliability.
- the new configuration may be enforced immediately after the UE receives the configuration. Or, a new configuration may be implemented after the RRC message is scheduled and K slots (or k ms) (eg, 20 ms from the RRC message). Ambiguity can be handled by the network. For example, the network may send a plurality of messages and control signals from the previous BWP and the currently active BWP.
- the CORESET to which the fallback DCI is scheduled may not be changed. That is, the newly activated BWP may include at least one CORESET shared with the previously activated BWP. In shared CORESET, resource allocation may be limited to the same as in the previous BWP.
- CORESET 1 of index 1 may be defined as a special CORESET that can be reused even after an RRC connection.
- the monitoring SIB / paging may be reconfigured to CORESET 1 by the RRC configuration.
- CORESET 1 for the RAR configured in the initial DL BWP may have the following characteristics.
- frequency domain information may be configured. If frequency domain information is not available, the same frequency domain as CORESET 0 can be used for CORESET 1. However, unlike CORESET 0, a resource block group (RBG) may be configured based on common PRB indexing based on information on reference PRB 0 signaled in RMSI. Since some PRBs at the beginning and / or end of the frequency domain may be less than a full 6 PRBs, the corresponding fragmented PRBs may not be used as CORESET 1 for convenience. If a bitmap is provided, a bitmap of a size including only full 6 PRBs within the initial DL BWP may be indicated. Unless otherwise indicated, the information for QCL may be equal to CORESET 0. Information about the duration of CORESET 1 may be explicitly configured.
- REG (resource element group) bundle size, precoder granularity, etc. may follow the configuration of CORESET 0 unless explicitly configured otherwise. Except for fragmented PRBs, the interleaver size may always be 2, depending on the reduced RBG size. Alternatively, the interleaver size can be configured to be aligned.
- DM-RS sequence may be generated based on common PRB indexing for CORESET 1.
- the UE may not monitor CORESET 0 and CORESET 1 at the same time. Therefore, after the RRC connection, the UE may be configured with a set of RNTIs monitored in the search area set associated with CORESET 1. Alternatively, once CORESET 1 is configured, the UE may monitor the SI and paging within the corresponding CORESET 1. That is, only the initial SIB according to beam sweeping may be scheduled at CORESET 0, and the remaining common data may be scheduled by CORESET 1.
- the UE may monitor UE specific RRC messages such as Msg 4 on CORESET 1 instead of CORESET 0. After the RRC connection, it can be reconfigured.
- CORESET 1 may be treated differently from CORESET 1 in terms of PRB indexing and PRB grouping.
- the CORESET configured by the SS block and / or RMSI can be handled specially. It may be desirable to use local PRB indexing only before common PRB indexing is possible. Thus, if PRB 0 is indicated in the RMSI, the CORESET configured by RMSI and / or UE specific signaling may follow common PRB indexing.
- the UE may skip monitoring of CORESET 0. That is, once CORESET 1 is configured, the UE may not be required to monitor CORESET 0.
- the UE may rebalance the initial DL BWP. Since the paging search area is associated with CORESET 0, the UE can monitor the search area associated with CORESET 0 in the idle state. If the UE initiates the RACH procedure in the idle state, the UE can monitor CORESET 1.
- the following may be considered for UE monitoring.
- UE in RRC idle state initial DL BWP and CORESET 0
- the UE may regard CORESET 1 as a default CORESET for C-RNTI, semi-persistent scheduling (SPS), transmit power command (TPC), etc. until it is reconfigured to another BWP or another CORESET.
- SPS semi-persistent scheduling
- TPC transmit power command
- UE-specific RNTI or group-specific RNTI may be monitored.
- SI-RNTI system information RNTI
- P-RNTI paging RNTI
- FIG. 10 illustrates a wireless communication system in which an embodiment of the present invention is implemented.
- the UE 1000 includes a processor 1010, a memory 1020, and a transceiver 1030.
- the memory 1020 is connected to the processor 1010 and stores various information for driving the processor 1010.
- the transceiver 1030 is connected to the processor 1010 and transmits a radio signal to the network node 1100 or receives a radio signal from the network node 1100.
- the processor 1010 may be configured to implement the functions, processes and / or methods described herein. More specifically, the processor 1010 may perform the operations S800 to S810 in FIG. 8 or control the transceiver 1030 to perform the same.
- the network node 1100 includes a processor 1110, a memory 1120, and a transceiver 1130.
- the memory 1120 is connected to the processor 1110 and stores various information for driving the processor 1110.
- the transceiver 1130 is connected to the processor 1110 and transmits a radio signal to or receives a radio signal from the UE 1000.
- Processors 1010 and 1110 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices.
- the memories 1020 and 1120 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media and / or other storage devices.
- the transceivers 1030 and 1130 may include a baseband circuit for processing radio frequency signals.
- the above-described technique may be implemented as a module (process, function, etc.) for performing the above-described function.
- the module may be stored in the memories 1020 and 1120 and executed by the processors 1010 and 1110.
- the memories 1020 and 1120 may be inside or outside the processors 1010 and 1110, and may be connected to the processors 1010 and 1110 by various well-known means.
- FIG. 11 shows a processor of the UE shown in FIG. 10.
- the processor 1010 of the UE includes a transform precoder 1011, a subcarrier mapper 1012, an inverse fast Fourier transform (IFFT) unit, and a cyclic prefix inserter (CP).
- IFFT inverse fast Fourier transform
- CP cyclic prefix inserter
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
La présente invention concerne un procédé et un appareil permettant d'effectuer une indexation de bloc de ressources physiques (PRB) dans un système de communication sans fil. Un équipement utilisateur (UE) reçoit des informations sur un décalage entre un bloc de signal de synchronisation (SS) et une bande passante de système à partir d'un réseau par l'intermédiaire du bloc SS et effectue l'indexation de PRB sur la bande passante de système sur la base des informations sur le décalage.
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201880028769.0A CN110574312B (zh) | 2017-04-14 | 2018-04-13 | 在无线通信系统中执行初始连接的方法和设备 |
EP21161712.1A EP3852289B1 (fr) | 2017-04-14 | 2018-04-13 | Procédé et appareil permettant de réaliser une connexion initiale dans un système de communication sans fil |
EP18785078.9A EP3595199B1 (fr) | 2017-04-14 | 2018-04-13 | Procédé et appareil permettant d'effectuer une connexion initiale dans un système de communication sans fil |
JP2019555863A JP7055819B2 (ja) | 2017-04-14 | 2018-04-13 | 無線通信システムにおける初期接続を遂行する方法及び装置 |
US16/064,817 US10944613B2 (en) | 2017-04-14 | 2018-04-13 | Method and apparatus for performing initial access in wireless communication system |
US17/168,976 US11695605B2 (en) | 2017-04-14 | 2021-02-05 | Method and apparatus for performing initial access in wireless communication system |
US18/080,157 US11863364B2 (en) | 2017-04-14 | 2022-12-13 | Method and apparatus for performing initial access in wireless communication system |
Applications Claiming Priority (14)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201762485865P | 2017-04-14 | 2017-04-14 | |
US62/485,865 | 2017-04-14 | ||
US201762516120P | 2017-06-07 | 2017-06-07 | |
US62/516,120 | 2017-06-07 | ||
US201762560167P | 2017-09-18 | 2017-09-18 | |
US62/560,167 | 2017-09-18 | ||
US201762564209P | 2017-09-27 | 2017-09-27 | |
US62/564,209 | 2017-09-27 | ||
US201762572534P | 2017-10-15 | 2017-10-15 | |
US62/572,534 | 2017-10-15 | ||
US201862630243P | 2018-02-14 | 2018-02-14 | |
US62/630,243 | 2018-02-14 | ||
KR1020180043227A KR101975579B1 (ko) | 2017-04-14 | 2018-04-13 | 무선 통신 시스템에서 초기 접속을 수행하는 방법 및 장치 |
KR10-2018-0043227 | 2018-04-13 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/064,817 A-371-Of-International US10944613B2 (en) | 2017-04-14 | 2018-04-13 | Method and apparatus for performing initial access in wireless communication system |
US17/168,976 Continuation US11695605B2 (en) | 2017-04-14 | 2021-02-05 | Method and apparatus for performing initial access in wireless communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018190678A1 true WO2018190678A1 (fr) | 2018-10-18 |
Family
ID=63793572
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2018/004347 WO2018190678A1 (fr) | 2017-04-14 | 2018-04-13 | Procédé et appareil permettant d'effectuer une connexion initiale dans un système de communication sans fil |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2018190678A1 (fr) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109983822A (zh) * | 2019-02-18 | 2019-07-05 | 北京小米移动软件有限公司 | Drx定时器的运行方法、装置、设备及存储介质 |
CN111106912A (zh) * | 2018-10-29 | 2020-05-05 | 中国移动通信有限公司研究院 | 一种辅小区控制方法、网络侧设备及终端 |
CN112042239A (zh) * | 2020-07-31 | 2020-12-04 | 北京小米移动软件有限公司 | 偏移指示确定方法和装置、偏移确定方法和装置 |
CN112205026A (zh) * | 2018-11-14 | 2021-01-08 | Oppo广东移动通信有限公司 | 装置和用于装置的带宽部分适配的方法 |
AU2018261818B2 (en) * | 2017-05-05 | 2021-01-28 | Huawei Technologies Co., Ltd. | Resource allocation method, user equipment, and network device |
WO2021031163A1 (fr) * | 2019-08-21 | 2021-02-25 | Nokia Shanghai Bell Co., Ltd. | Réglage d'une bwp différente plus tôt dans un processus d'établissement de connexion sur un réseau sans fil par un ue lors de la transition d'un état de veille ou inactif |
JP2022506284A (ja) * | 2018-11-02 | 2022-01-17 | 維沃移動通信有限公司 | 無線通信の方法及び機器 |
JP2022511660A (ja) * | 2018-11-02 | 2022-02-01 | 維沃移動通信有限公司 | 情報伝送方法及び通信機器 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017039373A1 (fr) * | 2015-09-02 | 2017-03-09 | Lg Electronics Inc. | Procédé et appareil d'indication de décalage de fréquence centrale pour ue à bande étroite dans un système de communications sans fil |
WO2017053024A1 (fr) * | 2015-09-24 | 2017-03-30 | Qualcomm Incorporated | Conception de canal de synchronisation commun pour des communications à bande étroite |
-
2018
- 2018-04-13 WO PCT/KR2018/004347 patent/WO2018190678A1/fr unknown
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017039373A1 (fr) * | 2015-09-02 | 2017-03-09 | Lg Electronics Inc. | Procédé et appareil d'indication de décalage de fréquence centrale pour ue à bande étroite dans un système de communications sans fil |
WO2017053024A1 (fr) * | 2015-09-24 | 2017-03-30 | Qualcomm Incorporated | Conception de canal de synchronisation commun pour des communications à bande étroite |
Non-Patent Citations (3)
Title |
---|
"Broadcast Channel Design for System Information Acquisition", 3GPP T SG RAN WG1 AH_ NR MEETING, R1-1700151, 20 January 2017 (2017-01-20), XP051207694 * |
ERICSSON: "NB-IOT-NB-MIB Content and Design Considerations", 3GPP TSG-RAN1#84. R1-160440, 6 February 2016 (2016-02-06), XP051064198 * |
SAMSUNG: "SS BW AND Multiplexing", 3GPP TSG RAN WG1 NR AH_1701 , R1-1700884, 9 January 2017 (2017-01-09), XP051203184 * |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU2018261818B2 (en) * | 2017-05-05 | 2021-01-28 | Huawei Technologies Co., Ltd. | Resource allocation method, user equipment, and network device |
US11089594B2 (en) | 2017-05-05 | 2021-08-10 | Huawei Technologies Co., Ltd. | Resource allocation method, user equipment, and network device |
CN111106912A (zh) * | 2018-10-29 | 2020-05-05 | 中国移动通信有限公司研究院 | 一种辅小区控制方法、网络侧设备及终端 |
JP7278374B2 (ja) | 2018-11-02 | 2023-05-19 | 維沃移動通信有限公司 | 情報伝送方法及び通信機器 |
JP2022506284A (ja) * | 2018-11-02 | 2022-01-17 | 維沃移動通信有限公司 | 無線通信の方法及び機器 |
JP2022511660A (ja) * | 2018-11-02 | 2022-02-01 | 維沃移動通信有限公司 | 情報伝送方法及び通信機器 |
JP7346563B2 (ja) | 2018-11-02 | 2023-09-19 | 維沃移動通信有限公司 | 無線通信の方法及び機器 |
US11968699B2 (en) | 2018-11-02 | 2024-04-23 | Vivo Mobile Communication Co., Ltd. | Radio communication method and device |
CN112205026A (zh) * | 2018-11-14 | 2021-01-08 | Oppo广东移动通信有限公司 | 装置和用于装置的带宽部分适配的方法 |
CN112205026B (zh) * | 2018-11-14 | 2023-07-25 | Oppo广东移动通信有限公司 | 装置和用于装置的带宽部分适配的方法 |
CN109983822A (zh) * | 2019-02-18 | 2019-07-05 | 北京小米移动软件有限公司 | Drx定时器的运行方法、装置、设备及存储介质 |
US12004157B2 (en) | 2019-02-18 | 2024-06-04 | Beijing Xiaomi Mobile Software Co., Ltd. | Method and apparatus for operating DRX timer, device and storage medium |
WO2021031163A1 (fr) * | 2019-08-21 | 2021-02-25 | Nokia Shanghai Bell Co., Ltd. | Réglage d'une bwp différente plus tôt dans un processus d'établissement de connexion sur un réseau sans fil par un ue lors de la transition d'un état de veille ou inactif |
CN112042239A (zh) * | 2020-07-31 | 2020-12-04 | 北京小米移动软件有限公司 | 偏移指示确定方法和装置、偏移确定方法和装置 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019216599A1 (fr) | Procédé de transmission et de réception de signaux pour une communication à faible latence ultra-fiable | |
WO2018190678A1 (fr) | Procédé et appareil permettant d'effectuer une connexion initiale dans un système de communication sans fil | |
WO2018226065A1 (fr) | Procédé et appareil pour prendre en charge la double connectivité dans nr | |
WO2019098770A1 (fr) | Procédé de transmission et de réception de canal d'accès aléatoire physique et dispositif associé | |
WO2018194412A1 (fr) | Procédé et appareil d'attribution de ressource dans un système de communication sans fil | |
WO2018199691A1 (fr) | Procédé et appareil de partage de puissance dans un système de communication sans fil | |
WO2018225989A1 (fr) | Procédé de réception d'informations de système dans un système de communication sans fil, et appareil pour cela | |
WO2018151533A1 (fr) | Procédé de transmission / réception de données dans un système de communication sans fil et appareil correspondant | |
WO2018016923A1 (fr) | Procédé et équipement utilisateur permettant de recevoir un canal de liaison descendante, et procédé et station de base permettant de transmettre un canal de liaison descendante | |
WO2018062925A1 (fr) | Procédé et dispositif permettant d'effectuer un accès aléatoire dans un système de communication sans fil | |
WO2017160100A2 (fr) | Procédé d'émission et de réception d'informations de commande dans un système de communication sans fil et appareil correspondant | |
WO2018147700A1 (fr) | Procédé pour un terminal et une station de base, comprenant une pluralité de points d'émission et de réception (trp) pour émettre/recevoir des signaux dans un système de communications sans fil, et dispositif associé | |
WO2016163847A1 (fr) | Procédé d'émission ou de réception de signal de référence de sondage dans un système de communication sans fil et appareil associé | |
WO2018084660A1 (fr) | Procédé d'émission/réception de canal de commande de liaison montante physique entre un terminal et une station de base dans un système de communication sans fil et dispositif prenant en charge ledit procédé | |
WO2021182863A1 (fr) | Procédé et dispositif d'évaluation de qualité de liaison radio dans un système de communication sans fil | |
WO2018199584A1 (fr) | Procédé de réception d'un signal de référence de suivi de phase par un terminal dans un système de communication sans fil et dispositif correspondant | |
WO2019074338A1 (fr) | Procédé et dispositif permettant d'effectuer une connexion initiale dans un système de communication sans fil | |
WO2018026181A1 (fr) | Procédé d'émission et de réception de signaux par un terminal et une station de base dans un système de communication sans fil, système et dispositif le prenant en charge | |
WO2014123388A1 (fr) | Procédé permettant de transmettre des informations de prise en charge réseau pour supprimer le brouillage, et station de base de cellule de desserte | |
WO2019083341A1 (fr) | Procédé de fonctionnement de dispositif dans un système de communication sans fil, et dispositif associé | |
WO2018030708A1 (fr) | Procédé d'émission et de réception d'un signal de liaison descendante dans un système de communication sans fil, et appareil associé | |
WO2022149774A1 (fr) | Procédé et dispositif de récupération de défaillance de faisceau dans un système de communication sans fil | |
WO2021201623A1 (fr) | Procédé et dispositif de transmission et de réception de pdcch dans un système de communication sans fil | |
WO2021230640A1 (fr) | Procédé et dispositif pour la transmission/réception d'un csi-rs dans un système de communication sans fil | |
WO2019050143A1 (fr) | Procédé permettant d'attribuer des ressources dans un système de communication sans fil et appareil utilisant le procédé |
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: 18785078 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2019555863 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2018785078 Country of ref document: EP Effective date: 20191009 |