WO2019050143A1 - Procédé permettant d'attribuer des ressources dans un système de communication sans fil et appareil utilisant le procédé - Google Patents

Procédé permettant d'attribuer des ressources dans un système de communication sans fil et appareil utilisant le procédé Download PDF

Info

Publication number
WO2019050143A1
WO2019050143A1 PCT/KR2018/007607 KR2018007607W WO2019050143A1 WO 2019050143 A1 WO2019050143 A1 WO 2019050143A1 KR 2018007607 W KR2018007607 W KR 2018007607W WO 2019050143 A1 WO2019050143 A1 WO 2019050143A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource allocation
band
size
rbg
allocation information
Prior art date
Application number
PCT/KR2018/007607
Other languages
English (en)
Korean (ko)
Inventor
황대성
이윤정
서인권
Original Assignee
엘지전자 주식회사
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
Priority claimed from KR1020180077736A external-priority patent/KR20190027705A/ko
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Priority to CN201880044119.5A priority Critical patent/CN110832931B/zh
Priority to JP2020513744A priority patent/JP7254776B2/ja
Priority to EP21205974.5A priority patent/EP3968719B1/fr
Priority to EP18854713.7A priority patent/EP3664549B1/fr
Publication of WO2019050143A1 publication Critical patent/WO2019050143A1/fr
Priority to US16/717,392 priority patent/US10880869B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present invention relates to wireless communication, and more particularly, to a method of allocating resources in a wireless communication system and an apparatus using the method.
  • MTC Massive Machine Type Communications
  • Next-generation wireless access technologies that take into account improved mobile broadband communications, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) technologies are being discussed as well as communication systems that are sensitive to reliability and latency. It can be called new radio access technology (RAT) or new radio (NR).
  • RAT new radio access technology
  • NR new radio
  • a bandwidth part may be introduced.
  • a band portion can be used to allocate some bands for terminals that are difficult to support the wide band.
  • the size of the resource allocation field in the frequency domain required in each band part may also vary.
  • the bit size (number) of the resource allocation field required for the first band portion is also a requirement (Number of bits) of the resource allocation field. If the first band portion includes fewer resource blocks in the frequency domain than the second band portion, it will be inverse.
  • the resource allocation information also needs to specify how the time domain information of the resource to be allocated is to be provided.
  • the present invention provides a method of allocating resources in a wireless communication system and an apparatus using the same.
  • a method of allocating resources in a wireless communication system includes generating second resource allocation information for scheduling a second bandwidth as a bit size (size) of first resource allocation information used for scheduling a first bandwidth, and allocating the second resource allocation information to the first bandwidth .
  • the first band and the second band may be different frequency bands.
  • the bit size of the second resource allocation information may be larger than a bit size required for analyzing the resource allocation information for the second band.
  • the bit size of the second resource allocation information may be smaller than a bit size required for analyzing the resource allocation information for the second band.
  • the second resource allocation information may include information indicating a start symbol and a length of a data channel transmitted in the second band.
  • the second resource allocation information may indicate a start symbol and a length of a data channel transmitted in the second band by indicating a specific row in the table below.
  • n denotes a natural number
  • K 0 denotes a slot offset
  • S denotes a start symbol of the data channel
  • L denotes the length
  • the type B may indicate that a demodulation reference signal is allocated to a first symbol among resources allocated to the data channel.
  • the second resource allocation information may indicate a start symbol and a length of a data channel transmitted in the second band by indicating a specific row in the table below.
  • K 0 is a slot offset
  • S is a start symbol of the data channel
  • L is the length
  • the type A indicates that a demodulation reference signal is allocated to a fixed symbol based on the start of a slot and the type B indicates that a demodulation reference signal is allocated to a first symbol among resources allocated to the data channel.
  • An apparatus provided in another aspect includes a transceiver for transmitting and receiving a radio signal and a processor operating in conjunction with the transceiver, the processor being operable to transmit second resource allocation information for scheduling a second band to a first (Size) of the first resource allocation information used for scheduling the bandwidth, and transmits the second resource allocation information through the first bandwidth.
  • a band part in which a bandwidth is changed flexibly is introduced.
  • resource allocation information for a band part is transmitted in another band part, the bit size (number) And the bit size of the resource allocation information.
  • the UE can receive the resource allocation information while minimizing the increase in the number of blind decoding times.
  • resource allocation information provides time domain information of an allocated resource, a start symbol and a last symbol may be indicated together to allocate resources clearly.
  • FIG 1 illustrates an existing wireless communication system.
  • FIG. 2 is a block diagram illustrating a radio protocol architecture for a user plane.
  • FIG. 3 is a block diagram illustrating a wireless protocol structure for a control plane.
  • FIG. 4 illustrates a system structure of a next generation radio access network (NG-RAN) to which NR is applied.
  • NG-RAN next generation radio access network
  • Figure 5 illustrates a frame structure that may be applied in NR.
  • FIG. 6 illustrates CORESET.
  • FIG. 7 is a diagram showing the difference between the conventional control area and CORESET in NR.
  • FIG. 8 illustrates a carrier bandwidth part newly introduced in NR.
  • FIG. 9 illustrates a resource allocation method in NR.
  • FIG. 10 shows a resource allocation method according to the present invention.
  • Fig. 12 shows an example of hopping area setting.
  • FIG. 13 is a block diagram illustrating an apparatus in which an embodiment of the present invention is implemented.
  • E-UTRAN Evolved-UMTS Terrestrial Radio Access Network
  • LTE Long Term Evolution
  • the E-UTRAN includes a base station (BS) 20 that provides a user plane (UE) with a control plane and a user plane.
  • the terminal 10 may be fixed or mobile and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT) .
  • the base station 20 is a fixed station that communicates with the terminal 10 and may be referred to as another term such as an evolved NodeB (eNB), a base transceiver system (BTS), an access point, or the like.
  • eNB evolved NodeB
  • BTS base transceiver system
  • access point or the like.
  • the base stations 20 may be interconnected via an X2 interface.
  • the base station 20 is connected to an S-GW (Serving Gateway) through an MME (Mobility Management Entity) and an S1-U through an EPC (Evolved Packet Core) 30, more specifically, an S1-MME through an S1 interface.
  • S-GW Serving Gateway
  • MME Mobility Management Entity
  • EPC Evolved Packet Core
  • the EPC 30 is composed of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway).
  • the MME has information on the access information of the terminal or the capability of the terminal, and this information is mainly used for managing the mobility of the terminal.
  • the S-GW is a gateway having an E-UTRAN as an end point
  • the P-GW is a gateway having a PDN as an end point.
  • the layers of the radio interface protocol between the UE and the network are classified into L1 (first layer), L1 (second layer), and the like based on the lower three layers of the Open System Interconnection (OSI)
  • a physical layer belonging to a first layer provides an information transfer service using a physical channel, and a physical layer (physical layer)
  • An RRC (Radio Resource Control) layer located at Layer 3 controls the radio resources between the UE and the network. To this end, the RRC layer exchanges RRC messages between the UE and the BS.
  • the 2 is a block diagram illustrating a radio protocol architecture for a user plane.
  • 3 is a block diagram illustrating a wireless protocol structure for a control plane.
  • the user plane is a protocol stack for transmitting user data
  • the control plane is a protocol stack for transmitting control signals.
  • a physical layer provides an information transfer service to an upper layer using a physical channel.
  • the physical layer is connected to a MAC (Medium Access Control) layer, which is an upper layer, through a transport channel.
  • Data is transferred between the MAC layer and the physical layer through the transport channel.
  • the transport channel is classified according to how the data is transmitted through the air interface.
  • the physical channel can be modulated by an Orthogonal Frequency Division Multiplexing (OFDM) scheme, and uses time and frequency as radio resources.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the function of the MAC layer includes a mapping between a logical channel and a transport channel and a multiplexing / demultiplexing into a transport block provided as a physical channel on a transport channel of a MAC SDU (service data unit) belonging to a logical channel.
  • the MAC layer provides a service to a Radio Link Control (RLC) layer through a logical channel.
  • RLC Radio Link Control
  • the function of the RLC layer includes concatenation, segmentation and reassembly of the RLC SDUs.
  • the RLC layer includes a Transparent Mode (TM), an Unacknowledged Mode (UM), and an Acknowledged Mode (RB) in order to guarantee various QoSs required by a radio bearer (RB) , And AM).
  • AM RLC provides error correction via automatic repeat request (ARQ).
  • the Radio Resource Control (RRC) layer is defined only in the control plane.
  • the RRC layer is responsible for the control of logical channels, transport channels and physical channels in connection with the configuration, re-configuration and release of radio bearers.
  • RB means a logical path provided by a first layer (PHY layer) and a second layer (MAC layer, RLC layer, PDCP layer) for data transmission between a UE and a network.
  • the functions of the Packet Data Convergence Protocol (PDCP) layer in the user plane include transmission of user data, header compression and ciphering.
  • the functions of the Packet Data Convergence Protocol (PDCP) layer in the control plane include transmission of control plane data and encryption / integrity protection.
  • the setting of the RB means a process of defining characteristics of a radio protocol layer and a channel to provide a specific service, and setting each specific parameter and an operation method.
  • RB can be divided into SRB (Signaling RB) and DRB (Data RB).
  • SRB is used as a path for transmitting the RRC message in the control plane
  • DRB is used as a path for transmitting the user data in the user plane.
  • the UE When an RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in the RRC connected state, and if not, the UE is in the RRC idle state.
  • the downlink transmission channel for transmitting data from the network to the terminal includes a BCH (Broadcast Channel) for transmitting system information and a downlink SCH (Shared Channel) for transmitting user traffic or control messages.
  • BCH Broadcast Channel
  • SCH Shared Channel
  • a traffic or control message of a downlink multicast or broadcast service it may be transmitted through a downlink SCH, or may be transmitted via a separate downlink MCH (Multicast Channel).
  • the uplink transmission channel for transmitting data from the UE to the network includes a random access channel (RACH) for transmitting an initial control message and an uplink SCH (Shared Channel) for transmitting user traffic or control messages.
  • RACH random access channel
  • a logical channel mapped to a transport channel is a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), a multicast traffic Channel).
  • BCCH broadcast control channel
  • PCCH paging control channel
  • CCCH common control channel
  • MCCH multicast control channel
  • a physical channel is composed of several OFDM symbols in the time domain and a plurality of sub-carriers in the frequency domain.
  • One sub-frame is composed of a plurality of OFDM symbols in the time domain.
  • a resource block is a resource allocation unit, and is composed of a plurality of OFDM symbols and a plurality of sub-carriers.
  • each subframe may use specific subcarriers of specific OFDM symbols (e.g., the first OFDM symbol) of the corresponding subframe for PDCCH (Physical Downlink Control Channel), i.e., L1 / L2 control channel.
  • the TTI Transmission Time Interval
  • new radio access technology new RAT
  • NR new radio
  • MTC Massive Machine Type Communications
  • URLLC Ultra-Reliable and Low Latency Communication
  • FIG. 4 illustrates a system structure of a next generation radio access network (NG-RAN) to which NR is applied.
  • NG-RAN next generation radio access network
  • the NG-RAN may include a gNB and / or an eNB that provides a user plane and control plane protocol termination to the terminal.
  • FIG. 4 illustrates a case where only gNB is included.
  • the gNB and the eNB are interconnected by an Xn interface.
  • the gNB and the eNB are connected to the 5G Core Network (5G Core Network: 5GC) via the NG interface.
  • 5G Core Network: 5GC 5G Core Network
  • AMF access and mobility management function
  • UPF user plane function
  • the gNB supports inter cell inter-cell RRM, RB control, connection mobility control, radio admission control, measurement configuration and provisioning, , Dynamic resource allocation, and the like.
  • AMF can provide functions such as NAS security, idle state mobility handling, and so on.
  • the UPF can provide functions such as mobility anchoring, PDU processing, and the like.
  • Figure 5 illustrates a frame structure that may be applied in NR.
  • the frame may be composed of 10 ms (millisecond) and may include 10 subframes composed of 1 ms.
  • one or a plurality of slots may be included according to a subcarrier spacing.
  • the following table illustrates the subcarrier spacing configuration ⁇ .
  • the following table shows the number of slots in a frame (N frame, ⁇ slot ), the number of slots in a subframe (N subframe, ⁇ slot ), and the number of symbols in a slot (N slot symb ) according to a subcarrier spacing configuration ⁇ . .
  • a plurality of orthogonal frequency division multiplexing (OFDM) symbols may be included in the slot.
  • a plurality of OFDM symbols in a slot can be divided into a downlink (denoted by D), a flexible (denoted by X), and an uplink (denoted by U).
  • the format of the slot may be determined according to which of the D, X, and U the OFDM symbols in the slot are configured.
  • the following table shows an example of a slot format.
  • the UE may receive the format of the slot through the upper layer signal, set the format of the slot through the DCI, or set the format of the slot based on the combination of the upper layer signal and the DCI.
  • the physical downlink control channel can be composed of one or more control channel elements (CCEs) as shown in the following table.
  • CCEs control channel elements
  • the PDCCH can be transmitted through a resource consisting of 1, 2, 4, 8, or 16 CCEs.
  • the CCE is composed of six resource element groups (REGs).
  • REGs resource element groups
  • One REG is composed of one resource block in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain.
  • OFDM orthogonal frequency division multiplexing
  • CORESET control resource set
  • FIG. 6 illustrates CORESET.
  • CORESET is composed of N CORESET RB resource blocks in the frequency domain and N CORESET symb ⁇ ⁇ 1, 2, 3 ⁇ symbols in the time domain.
  • N CORESET RB , N CORESET The symb may be provided by the base station via an upper layer signal.
  • a plurality of CCEs (or REGs) may be included in the CORESET.
  • the UE can attempt to detect the PDCCH in units of 1, 2, 4, 8, or 16 CCEs in the CORESET.
  • One or a plurality of CCEs capable of attempting to detect a PDCCH may be referred to as a PDCCH.
  • the terminal can set a plurality of CORESETs.
  • FIG. 7 is a diagram showing the difference between the conventional control area and CORESET in NR.
  • the control region 300 in the conventional wireless communication system (e.g., LTE / LTE-A) is configured over the entire system band used by the base station. All terminals except for some terminals (eMTC / NB-IoT terminal for example) supporting only a narrow band receive radio signals of the entire system band of the base station in order to properly receive / decode the control information transmitted by the base station I should have been able.
  • All terminals except for some terminals eMTC / NB-IoT terminal for example
  • the CORESETs 301, 302, and 303 may be radio resources for control information that the UE should receive, and may use only a part of the system bandwidth.
  • the base station can assign CORESET to each UE and can transmit control information through the assigned CORESET.
  • the first CORESET 301 may be allocated to the UE 1
  • the second CORESET 302 may be allocated to the second UE
  • the third CORESET 303 may be allocated to the UE 3.
  • the terminal in the NR can receive control information of the base station without necessarily receiving the entire system band.
  • CORESET may have a UE-specific CORESET for transmitting UE-specific control information and a common CORESET for transmitting control information common to all UEs.
  • FIG. 8 illustrates a carrier bandwidth part newly introduced in NR.
  • the carrier band portion may be simply referred to as a bandwidth portion (BWP).
  • BWP bandwidth portion
  • various numerologies e.g., various subcarrier intervals
  • NR can define a common resource block (CRB) for a given numerology on a given carrier.
  • CRB common resource block
  • the band portion is a set of consecutive physical resource blocks (PRBs) selected from successive subsets of common resource blocks (CRBs) for given numerology on a given carrier.
  • PRBs physical resource blocks
  • CRBs common resource blocks
  • a common resource block can be defined according to a numerology for a certain carrier band, for example, a certain subcarrier interval is used.
  • a common resource block can be indexed (starting from 0) starting from the lowest frequency of the carrier band, and a resource grid (which can be referred to as a common resource block resource grid) with a common resource block as a unit can be defined .
  • the band portion can be indicated on the basis of a CRB having the lowest index (this is referred to as CRB 0).
  • CRB 0 having the lowest index
  • the CRB 0 having the lowest index may also be referred to as point A.
  • the ith band part can be indicated by N start BWP, i and N size BWP, i .
  • N start BWP, i may indicate the start CRB of the i-th BWP based on CRB 0, and N size BWP, i may indicate the size in the frequency domain of the i-th BWP (e.g., in units of PRB) .
  • PRBs within each BWP may be indexed from zero.
  • a terminal can set up to four downlink band parts in the downlink, but only one downlink band part can be activated at a given time.
  • the UE does not expect to receive PDSCH, PDCCH, CSI-RS, etc. outside the active downlink band portion among the downlink band portions.
  • Each downlink band portion may comprise at least one CORESET.
  • the UE can set up to four uplink band portions in the uplink, but only one uplink band portion can be activated at a given time.
  • the UE does not transmit PUSCH, PUCCH, or the like outside the active uplink band portion among the uplink band portions.
  • the band part (BWP) is a feature that allows a terminal that can not support the above-mentioned wide band to operate.
  • the resource allocation type specifies how the scheduler (e.g., base station) allocates resource blocks for each transmission. For example, when a base station allocates a band composed of a plurality of resource blocks to a terminal, the base station can inform resource blocks allocated to the terminal through a bitmap composed of bits corresponding to each resource block of the band . In this case, although the flexibility of resource allocation will be greatest, there is a disadvantage that the amount of information used for resource allocation increases.
  • Resource allocation type 0 allocates resources through a bitmap, and each bit of the bitmap indicates a resource block group (RBG) instead of a resource block. That is, in the resource allocation type 0, the resource allocation is performed not in the resource block level but in the resource block group unit.
  • RBG resource block group
  • Resource allocation type 1 is a method of allocating resources in units of RBG subset.
  • One RBG subset may be composed of a plurality of RBGs.
  • RBG subset # 0 is RBG # 0, 3, 6, 9 ...
  • RBG subset # 1 is RBG # 1, 4, 7, 10, ...
  • RBG subset # 2 is RBG # 5, 8, 11, ..., and so on.
  • the number of RBGs included in one RBG subset and the number of resource blocks (RB) included in one RBG are set to be the same.
  • Resource allocation type 1 indicates which RBG subset of RBG subsets is used and which RB is used in the RBG subset being used.
  • Resource allocation type 2 is a method of allocating resources in such a manner as to indicate the allocated bandwidth start position (RB number) and the number of consecutive resource blocks.
  • the contiguous resource blocks may start at the starting location.
  • the consecutive resource blocks are not necessarily physically continuous, but may mean that the logical or virtual resource block index is continuous.
  • the number of resource blocks constituting the RBG (or group of RBs) can be changed flexibly.
  • the information for the RBG for example, information indicating the number of resource blocks constituting the RBG may be transmitted through an upper layer signal such as a scheduling DCI or a third physical layer (L1) signaling or an RRC message .
  • the resource allocation information (for example, information on the RBG described above) may include information on a time domain in addition to information on a frequency domain, The manner in which information is included and how it is included can also be changed flexibly.
  • a resource allocation method for a PDSCH and / or a PUSCH is proposed when a field size and / or an analysis method for resource allocation vary.
  • the RBG-based bitmap scheme is assumed when the size of the RBG is flexible for the sake of explanation.
  • the resource allocation granularity of the RBG is changed and / It is also possible to extend the case of changes.
  • the resource allocation scheme (particularly, the RBG size or the content for the grid) may be applied to at least a PDSCH or a PUSCH-only map resource area.
  • Other resource allocation techniques (RBG size or grid) can be applied in other resource areas. For example, when a specific resource in the PDCCH region can be used for PDSCH mapping, the RBG size and other RBG sizes in the corresponding region can be independently set or indicated.
  • the RBG sizes may be differently or independently set / indicated for each carrier or band portion.
  • the size of the RBG is changed (or indicated by the DCI), but the number of RBGs that can be indicated by the resource allocation (RA) ) Can be extended and applied.
  • the RBG may be viewed as a value representative of frequency-domain granularity.
  • the RBG size may be fluidically changing. Therefore, when the RBG is used, the frequency resource allocation field size can also be flexibly changed.
  • RBG size in indicating a wide area (e.g., the entire terminal band or the system band) on the frequency axis.
  • a small RBG size in indicating a small area (e.g., one or several physical resource blocks) on the frequency axis.
  • a smaller RBG size (as compared to a larger RBG size) may cause an excessively large resource allocation field size.
  • the frequency-axis resource allocation field of the bitmap scheme can be composed of 5 bits.
  • the RBG size is 2
  • the frequency axis resource allocation field may be composed of 25 bits.
  • the resource allocation field is included in the DCI. It would be advantageous in terms of blind decoding / detection in terms of the UE to keep the total DCI size or the total resource allocation field size the same.
  • the bits of the resource allocation field that vary depending on the RBG size selection may be those used primarily to perform time domain resource allocation. Depending on the indicated RBG size, the allocation method for time and / or frequency domain resources may be different.
  • the following shows an example of a resource allocation scheme according to RBG size. All or some combinations of the following schemes can be used for time and frequency resource allocation.
  • the RBG size is smaller than or less than a certain level (N low ), what the resource allocation field indicates may be limited to the frequency domain resources.
  • the specific level may be a preset default RBG size or may be set in an upper layer.
  • the resource allocation in the time domain may be predetermined or may be determined over the entire PDSCH mapping area or the PUSCH mapping area (in time axis) Lt; / RTI > Or time-domain resources to which resource allocation is to be performed may be separately indicated by information on upper layer signaling or slot type format.
  • the default time-domain resource is predetermined (e.g., PDSCH or PUSCH across the slot), and if the slottype-related information is dynamically indicated, the time- And may be dynamically changed in the slot according to the slot type related information. Or slot-type related information is transmitted, the start point and the duration of the PDSCH or the PUSCH may be preset by an upper layer signal for reliability. Or slot-type related information is not transmitted, the upper layer signaling can be similarly considered.
  • the resource allocation field indicates may be limited to resources in the time domain. More specifically, the RBG size may be the same as or equivalent to the system band or the terminal band. In this case, resource allocation in the frequency domain can be assigned for either PDSCH or PUSCH transmission (with respect to the indicated RBG size).
  • the resource allocation field may be a time and frequency resource. More specifically, some bits among all bits of the resource allocation field are used to indicate frequency domain resource allocation, and the remaining bits can be used to indicate time domain resource allocation.
  • the frequency domain resource allocation may be to indicate an RBG to be assigned with the indicated RBG size.
  • the time domain resource allocation may be indicative of what is to be assigned to a predetermined or indicated time-domain scheduling unit.
  • the time domain resource allocation may be provided in the form of a pattern, and the number of the patterns may be different according to the change of the bits for the time domain resource allocation.
  • time domain resource allocation and frequency domain resource allocation may be jointly performed.
  • the information on the allocated time and frequency resource pairs can be set in a plurality of pattern types.
  • the bits of the total resource allocation field may indicate the pattern.
  • the UE can set up a plurality of bandwidth parts, and each band part can be set by a set of consecutive PRBs, an RBG size to be used, and a size of a time domain resource allocation. DCI, and the RBG size and time information used in each band part when each band part is indicated can be used for resource allocation.
  • the selection for the band portion may be a representation of the time and / or frequency resource scheduling unit selection at the time of resource allocation.
  • a terminal can be set as a band subgroup for a band part (that is, a band part that can be dynamically changed into one DCI size) among the set band parts, and the largest resource It can be assumed that the bit size of the resource allocation field in the band portion group is determined according to the size of the allocation field.
  • This configuration may be parallel to the dynamically changing band portion. It can be assumed that each band subgroup shares a CORESET. This is because the size of the DCI to be scheduled can be changed when the CORESET is changed, and the case where the resource allocation field is dynamically changed while CORESET is shared.
  • the band subgroup may expect that the UE does not match the baseband bandwidth while sharing CORESET (s). It may be assumed that within the band part group, the baseband of the terminal does not change to match the maximum value of the band part group.
  • higher layer signaling may be possible as to whether the terminal can assume a band change or a retuning delay between the control signal and data can be assumed. If the delay is not set assuming a band change, it can be assumed that the band does not change but fits the maximum value.
  • one band part can be set, and a set of DCI resource allocation time / frequency schemes that can be indicated in the CORESET (s) of the corresponding band part can be set.
  • the set of time / frequency methods may be composed of a band, an RBG size, time domain resource allocation information, and the like.
  • a method of indicating different RBG size or time-frequency resource allocation scheme may be as follows.
  • Explicit bits can be used for DCI.
  • DCI can be interpreted differently depending on the CCE index to which it is mapped. This mapping may be set by the upper layer signal or may be a value that is always set. iii) or scrambling or CRC of the DCI.
  • the terminal can monitor the CORESETs set in several band parts at the same time.
  • the resource allocation method used for each CORESET may be different.
  • a CORESET may be configured for each of the 200 RB and 10 RB bands, and the bit size of the resource allocation field for each CORESET may be as much as necessary for scheduling 200 RB and 10 RB. More generally, bandwidth and resource allocation information of data that can be scheduled for each CORESET may be set.
  • the total bit field size for time and frequency resource allocation for these schemes may be the same.
  • the resource allocation for the frequency domain may indicate allocation of resources allocated through the bitmap scheme for a given RBG size, or may be based on a given RBG size as a basic unit in the RIV scheme (i.e., continuous with the starting RB or RBG index) RB or RBG number) of the received data.
  • the resource allocation for the time domain includes a starting time-domain scheduling unit index, an ending time-domain scheduling unit index, and / or a continuous time-domain scheduling unit index for the PDSCH or the PUSCH.
  • Domain scheduling units which may be time-domain scheduling units.
  • the time-domain scheduling unit may be a symbol (reference numerology or numerology reference to DCI), or may be a plurality of symbols or a mini-slot.
  • the size of the symbol group is set and the scheduling unit is set based on the size, the size of the specific symbol group may be different from the size of the other symbol groups according to the number of symbols constituting the slot.
  • a pattern for a group of symbols in a slot or a plurality of slots may be set in advance according to a base station instruction or a resource allocation may be performed based on a start unit and a corresponding unit number in the unit.
  • the symbol group pattern may differ depending on the control region setting (e.g., the number of symbols in the time domain).
  • a symbol group pattern in a slot composed of seven symbols may be any of the following. (3, 2, 2), (1, 2, 2, 2), (2, 2, 2, 1), (2, 2, 3), (2, 3, 2)
  • Information on the start / end / interval may exist in a pattern form, and a resource allocation bit field may be used to indicate a corresponding pattern. More specifically, the information on the pattern may be that the base station is instructed (via higher layer signaling or a third PDCCH).
  • a RIV scheme (a start symbol index, a scheme for indicating the number of consecutive symbols) can be used. If the bit field size for the time domain resource allocation is changed according to the RBG size, resource allocation may be performed with some bits of the RIV scheme fixed to a specific value (e.g., 0 or 1), or In the RIV scheme, the basic unit may be incremented (e.g., performed based on a plurality of symbols from being performed in one symbol period).
  • the bit size of the resource allocation field is the same. If the size of the RBG is changed, the resource combination that can be allocated may be different.
  • the manner in which the RBG size is changed can be based on at least one of 1) directing from the DCI, 2) changing according to the band part change, or 3) changing according to the bit size of the resource allocation field.
  • a specific RBG size is used as a reference.
  • the size of the bit field may be determined based on a maximum RBG size that can be set.
  • the base station may indicate the bit size of the resource allocation field.
  • the RBG size of the specific RBG size or larger it may be possible to flexibly allocate resources to all the RBGs in the system band, the terminal band, or the set band part.
  • resource allocation may be possible for only some RBG sets. More specifically, when a frequency domain resource allocation is configured with a bitmap for an RBG, a specific RBG size (group) can represent all RBG or RBG combinations within a given band for the corresponding UE. On the other hand, if the size of the RBG is small, it may be possible to allocate resources only for a certain RBG set within a given band to the UE.
  • the number of RBGs is N in the terminal band for the first RBG size
  • the number of RBGs is M in the terminal band for the second RBG size.
  • M the number of RBGs
  • the resource allocation field is set based on the first RBG size, only N of the M RBGs or a subset of the M RBGs can be allocated through the resource allocation field for the second RBG size.
  • setting a larger RBG size may be for allocating more frequency resources, and conversely, setting a smaller RBG size may be for allocating a smaller frequency resource.
  • FIG. 9 illustrates a resource allocation method in NR.
  • a base station may transmit first resource allocation information for scheduling a first band portion through a first band portion.
  • the base station may also transmit the second resource allocation information for scheduling the second band portion through the first band portion.
  • the first resource allocation information and the second resource allocation information may be composed of N bits equally.
  • the resource allocation information may be, for example, a downlink control information (DCI) format transmitted through a PDCCH, and may be a DCI format 0_1 and a DCI format 1_1.
  • DCI downlink control information
  • the DCI format 0_1 is used for the scheduling of the PUSCH in one cell.
  • the DCI format 0_1 includes a carrier indicator (0 or 3 bits), a band portion indicator (0, 1 or 2 bits), frequency domain resource allocation (number of bits based on the size of the frequency domain of the active band portion) (0, 1, 2, 3, or 4 bits), a modulation and coding scheme (5 bits), and a HARQ process number (4 bits).
  • the DCI format 1_1 is used for scheduling the PDSCH in one cell.
  • DCI format 1_1 includes a carrier indicator (0 or 3 bits), a band portion indicator (0, 1 or 2 bits), a frequency domain resource allocation (number of bits based on the size of the frequency domain of the active band portion) (0, 1, 2, 3, or 4 bits), a modulation and coding scheme (5 bits), and a HARQ process number (4 bits).
  • the second band portion may include a band portion to be scheduled, May be referred to as a band portion for scheduling.
  • the bandwidth part can be changed to a dynamic bandwidth.
  • the bit sizes of the resource allocation information required in the scheduling BWP and the scheduled BWP may be different.
  • resource allocation can be performed for a band part to be scheduled with a bit size of resource allocation information (field) in a band part to be scheduled.
  • FIG. 10 shows a resource allocation method according to the present invention.
  • a base station transmits second resource allocation information for scheduling a second band (e.g., a second band portion: 2 nd BWP) to a first band (e.g., a first band portion: 1 st BWP) (S101), and transmits the second resource allocation information through the first band (S102).
  • a second band e.g., a second band portion: 2 nd BWP
  • a first band e.g., a first band portion: 1 st BWP
  • the first and second bands are the band parts (BWP) newly introduced in NR
  • the first band may be referred to as a first band portion
  • the second band may be referred to as a second band portion.
  • the present invention is not limited to the application to the band portion, and the first and second bands may be any other band.
  • the second resource allocation information may comprise a band portion indicator indicating the second band portion.
  • the second resource allocation information may be at least one of a DCI format 0_1 and a DCI format 1_1.
  • the first band portion and the second band portion may have different frequency bands.
  • the bit size of the second resource allocation information may be larger than the bit size required for the interpretation of the resource allocation information for the second band portion.
  • the bit size of the second resource allocation information may be smaller than the bit size required for the interpretation of the resource allocation information for the second band portion.
  • the terminal allocates a band part (first band part) to be scheduled than the bit size required for the analysis of DCI format 0_1 or DCI format 1_1 in the band part to be scheduled (i.e., the band part indicated by the band part indicator, the second band part) It is possible to prepend 0 to the received DCI format 0_1 or DCI format 1_1 if the bit size of the received DCI format 0_1 or DCI format 1_1 is small. Specifically, this operation can be performed for each field of DCI format 0_1 or DCI format 1_1.
  • the terminal can interpret the corresponding field using only the necessary bits from the LSB (least significant bit) in each field of the received DCI format 0_1 or DCI format 1_1 have.
  • the base station transmits a scheduling bandwidth And transmits information about the part. Then, the UE may add 0 to the received information field in front of the information field in accordance with the bit size of the information field required in the scheduled BWP, or interpret the information field using only necessary bits from the LSB have.
  • the DCI formats include a time domain resource allocation field for instructing resource allocation in the time domain of the PUSCH or PDSCH.
  • the time domain resource allocation field may indicate the combination of the start symbol index and the last symbol index of the PUSCH or PDSCH in the RIV scheme.
  • the RIV scheme may be a scheme for indicating a start symbol index and a duration / length.
  • the interval / length may be a value based on the start symbol index.
  • the time-domain resource allocation field may inform a corresponding row in a table defined for each row by a slot offset, a start symbol, and a length (interval) for PDSCH reception (PUSCH transmission). That is, the time domain resource allocation field may be a joint indication of the start symbol index and the last symbol index of the PUSCH / PDSCH.
  • the table in which the slot offset, the start symbol and the length (interval) for the PDSCH reception (PUSCH transmission) are defined for each row may be, for example, Tables 7 and 8 below.
  • the BS may instruct the MS to select the RBG set to reduce the resource allocation.
  • the resource allocation field in the frequency domain can be composed of an RBG size indicator, an RBG set indicator in a band, and / or an RBG indicator in an RBG set.
  • the candidates for the RBG aggregation may be configured such that the base station receives a separate indication (e.g., signaling through an upper layer signal, such as an RRC message, and / or a group common PDCCH) and / ).
  • a separate indication e.g., signaling through an upper layer signal, such as an RRC message, and / or a group common PDCCH
  • a specific candidate among the candidates for the RBG set can be indicated in the DCI scheduling the corresponding PDSCH or PUSCH.
  • the RBGs in the RBG aggregation may be localized (i.e., adjacent to each other) or distributed (i.e., separated from each other) depending on the base station setting.
  • the base station may set the candidate (s) for the RBG set via signaling via an upper layer signal, such as an RRC message, and / or PDCCH and / or a third DCI, May be in bitmap form for RBGs.
  • an upper layer signal such as an RRC message, and / or PDCCH and / or a third DCI, May be in bitmap form for RBGs.
  • the BS may map a plurality of consecutive RBGs to the same RBG set for localized resource allocation, and a plurality of non-contiguous RBGs for distributed resource allocation. RBG) to the same set of RBGs.
  • the RBG to be instructed may include RBGs corresponding to the number of RBGs that can be represented according to the bit size of the resource allocation field of the scheduling BWP from the lowest RBG of the scheduled BWP, . ≪ / RTI >
  • the corresponding RBG may be excluded from the RBG set to be indicated.
  • the relatively small RBG size may mean that the RBG size is smaller than the RBG size set according to the size of the band part (BWP).
  • the resource allocation type of the bitmap scheme a scheme in which the bit size of the resource allocation field required and the bit size of the actual resource allocation field are different may be used as in the above method.
  • the resource allocation type of the RIV scheme may configure the bit size of the resource allocation field based on the largest bandwidth portion or may configure the bit size of the resource allocation field based on the largest bandwidth portion of the set bandwidth portion.
  • the bit size difference of the resource allocation field may be slight depending on the size of the band portion.
  • multiple RBG sizes may be used to indicate resources in the resource allocation. More specifically, when the band portion is composed of a plurality of RBGs, the size of a specific RBG follows the set RBG size (including +/- 1 difference), and the size of another specific RBG includes all the remaining PRBs of the band portion Can be set.
  • the band portion is composed of 50 PRBs
  • the bit size of the resource allocation field is 5 (bits)
  • the RBG size is 5 PRBs.
  • the RBG configuration for the band portion may be composed of four RBGs having a size of 5 PRBs and one RBG having 30 PRBs.
  • the specific RBG size may be excessively large.
  • the RBGs constituting the band portion are arranged such that RBG having Ceil (N / M) (N / M) -N and the RBG having a floor (N / M) size may be M- (M * Ceil (N / M) -N).
  • the order in which the RBGs having different sizes are arranged may be that RBGs having the same RBG size are arranged first and then RBGs having different RBG sizes are arranged.
  • a majority of the RBGs are set to Ceil (N / M) or Floor (N / M)
  • resource allocation (analysis) method according to the RBG size in the frequency domain
  • resource allocation (analysis) method can be extended to a resource allocation (analysis) method according to a scheduling (time) unit in the time domain.
  • resource allocation for a time domain may be set for a specific scheduling unit, and resource allocation may be performed according to a scheduling unit value that is changed flexibly. And more particularly may be represented by a time and / or frequency resource scheduling unit in the case of the RBG set indicator.
  • the RBG aggregation indicator may include information on RBGs constituting the RBG aggregate as well as information on the starting symbol index and / or duration (starting symbol index and / or duration).
  • the basic time and frequency resource units may be selected for each RBG in the scheduling unit of the time domain. Or the resource allocation (or the scheduling unit) is not fluidly changed for the time axis.
  • resource allocation may be performed for a specific RBG set in the frequency domain, and allocation information for the specific RBG set may be applied to a plurality of RBG sets in the same band.
  • allocation information for the specific RBG set may be applied to a plurality of RBG sets in the same band.
  • bitmap information for a specific RBG set is applied to each of the other RBG sets.
  • the frequency domain will be described, but it may be applied to resource allocation in the time domain and may be applied to time / frequency domain resources.
  • Resource allocation type 0 Bitmap with bit size of RBG size K + floor (M / K), where M is the number of PRBs for the band set in the band part.
  • Resource allocation type 1 Bitmap with bit size of RBG size p * K + floor (M / p * K)
  • the resource allocation type 1 increases the size of the RBG, gives a bitmap (RBG indicator) about which RBG is selected among the RBGs, and allocates the bitmap (RBG indicator) within one RBG size RB-level resource allocation is possible by placing an RB indicator in the RB-level. It can be assumed that bitmaps within the RBG size are commonly applicable to selected RBGs.
  • the above-described methods can be used in combination.
  • the set of RBs that can be allocated according to the RBG size may be different, and the resource allocation method of the time domain may be changed.
  • the UE may indicate a start symbol index and / or a last symbol index for a PDSCH or a PUSCH through scheduling DCI (Scheduling DCI) in performing time domain resource allocation.
  • scheduling DCI Service DCI
  • the start symbol index and / or the last symbol index may be indicated in units of a symbol or a symbol group constituting a slot, or may be a joint indication of a start symbol index and a last symbol index It is possible. For example, it is possible to combine the start symbol index and the last symbol index in the RIV scheme.
  • the RIV scheme may be a scheme for indicating a start symbol index and a duration.
  • the terminal may be scheduled to receive the PDSCH by the DCI.
  • the DCI may include a time domain resource allocation field for instructing resource allocation in the time domain of the PDSCH.
  • the time domain resource allocation field may indicate a corresponding row in a table defined for each row by, for example, a slot offset, a start symbol, and a length (interval) for PDSCH reception. This table has been described above.
  • the UE can regard it as a valid PDSCH allocation for the start symbol (S) and length (L) and S + L corresponding to the following table.
  • the base station can set the set (s) for a plurality of time domain resources through RRC signaling, each set including slot index information to which PDSCH / PUSCH is mapped, and / And / or a combination of the last symbol index and the like.
  • time domain resource allocation can be performed by directing through a scheduling DCI (DCI) scheduling one of the established sets.
  • DCI scheduling DCI
  • the set (s) set by the RRC may be set separately from slot format information (SFI) transmitted on the group common PDCCH.
  • SFI indicates the downlink portion, the gap, and / or the uplink portion in the slot.
  • the downlink portion is generally used from the first symbol of the slot, while in the case of the time domain resource allocation, the PDSCH or the PUSCH scheduling is performed in order to avoid overlapping with the CORESET
  • the purpose and the method are different because it does not exclude the method of preventing the mapping during the first few symbols.
  • a set of parameter sets (s) (e.g., slot index information, a start symbol index, and a combination of at least one of the last symbol index) for a time domain resource is a physical broadcast channel (PBCH) and / or remaining minimum system information (RMSI) / Or other system information (OSI).
  • PBCH physical broadcast channel
  • RMSI remaining minimum system information
  • OSI system information
  • a part of the minimum system information may be transmitted through the PBCH, and the remainder, that is, the RMSI may be transmitted via the PDSCH.
  • the time domain resource allocation of the scheme may be when the scheduling DCI belongs to a common search space or a group common search space.
  • the common search space may again be a search space for RMSI and / or OSI transmission.
  • Dynamic time domain resource allocation may not be performed.
  • it may be a fixed value in the case of the slot index, and a different value may be set for the PDSCH and the PUSCH.
  • the PDSCH may be transmitted in the same slot as the PDCCH, and the PUSCH may be transmitted in four slots after the PDCCH.
  • the start symbol index it can be specified by the symbol following the CORESET section. More specifically, for the PUSCH, the start symbol index may be set via higher layer signaling (PBCH and / or RMSI and / or OSI) and / or DCI indication, or may be set to start from the first symbol of the established slot.
  • PBCH and / or RMSI and / or OSI higher layer signaling
  • DCI indication may be set to start from the first symbol of the established slot.
  • the last symbol index may be set via upper layer signaling (PBCH and / or RMSI and / or OSI) and / or DCI indication or may be set to the last symbol of the slot.
  • PBCH and / or RMSI and / or OSI upper layer signaling
  • DCI indication may be set to the last symbol of the slot.
  • the time domain resource allocation of the above scheme may be the case where the DCI scheduling belongs to the common search space or the group common search space.
  • the common search space may again be a search space for RMSI and / or OSI transmission.
  • SSB denotes a block through which a synchronization signal and a physical broadcast channel (PBCH) are transmitted.
  • PBCH physical broadcast channel
  • NR can support an RMSI size of approximately 1700 bits in one transport block for FR1, FR2 with appropriate RMSI settings. It is possible to support a transport block size (TBS) of 2976 bits at maximum for the PDSCH by the SI-RNTI.
  • TBS transport block size
  • the subcarrier spacing of ⁇ SS / PBCH block, PDCCH ⁇ may be [240, 120] kHz, or [120,120] kHz.
  • the initial downlink band portion may be composed of 24 or 48 PRBs.
  • the initial downlink band portion refers to a portion of a downlink band that is valid until the terminal is explicitly set to the bandwidth portion during or after establishment of the RRC connection.
  • the maximum number of available resource elements for the PDSCH mapping may be 864.
  • the coding rate will be approximately 0.98. It may be necessary to support a time domain resource allocation longer than two symbols to support a sufficiently large RMSI size.
  • the time domain resource allocation field included in the DCI may indicate a row index in the 'PDSCH Symbol Allocation' table set by the upper layer.
  • Each row indexed in the table may define a slot offset K 0 , a start symbol (S) and a length (L) indicator (SLIV) and a PDSCH mapping type that is assumed to receive the PDSCH.
  • the PDSCH mapping types are Type A and Type B.
  • the types A and B can be classified according to the manner in which the position of the DM-RS for the PDSCH is determined.
  • the following table is an example of a 'PDSCH symbol allocation' table set by an upper layer indicating a default PDSCH time domain resource allocation.
  • PDSCH mapping types include Type A (Type A) and Type B (Type B).
  • a DM-RS (referred to as a PDSCH DM-RS) is mapped to the PDSCH, and the physical resource to which the PDSCH DM-RS is mapped depends on the types A and B.
  • the first symbol to which the DM-RS is mapped may be the third or fourth symbol based on slot start (i.e., slot based).
  • the first symbol to which the DM-RS is mapped may be the first symbol of the resource to which the PDSCH is allocated. That is, the PDSCH DM-RS is transmitted from the first symbol of the scheduled PDSCH resource, not based on the start of the slot.
  • Type A indicates that a demodulation reference signal is allocated to a fixed symbol based on the start of a slot
  • Type B indicates that a demodulation reference signal is allocated to a first symbol among resources allocated to the data channel.
  • PDSCH allocation of length 6 symbols may be supported .
  • the PDSCH can be transmitted before the PDCCH. It may also be necessary to change the DMRS location of the PDSCH mapping type A, taking into account the overlap of the DMRS and CORESET. Alternatively, a PDSCH allocation starting at the start of the corresponding PDCCH and having four symbols in length can be considered. At this time, if the aggregation level used for PDCCH transmission is smaller than 16, the number of available resource elements for data mapping may increase.
  • the following table is another example of the 'PDSCH symbol allocation' table set by the upper layer indicating the default PDSCH time domain resource allocation.
  • time domain resource allocation may be supported in a combination of subsets for different sets of rows.
  • a fallback operation may be possible independently of the RRC setting.
  • the time domain resource allocation table ('PDSCH symbol allocation' table) may be independent of the RRC settings for handling ambiguity during the RRC reset period.
  • the common search space type is 0 / 0A / 2
  • a plurality of terminals can monitor the same PDCCH / PDSCH without RRC setting.
  • a plurality of terminals which do not have different RRC settings or RRC settings, can receive the same PDCCH / PDSCH for a random access response.
  • the time-domain resource allocation in the DCI in the UE-specific search space can be updated by RRC setting.
  • the time domain resource allocation set for PDSCH or PUSCH may not be changed by RRC setting.
  • the time domain resource allocation set for the PDSCH or PUSCH can be updated by the RRC setting.
  • the RMSI can separately indicate a resource allocation table for OSI / paging, a resource allocation table for random access response / message 4 / unicast, and the like. More specifically, the RMSI may indicate whether a resource allocation table for OSI and / or paging is used, or whether the table indicated by the RMSI is an initial table. The RMSI may indicate whether to use the table (if present) indicated by the RMSI always for the random access response, message 4 and / or unicast, or to use the initial table if the table indicated by the RMSI is not used.
  • PDSCH or PUSCH can be scheduled over a plurality of slots through aggregation of multiple slots.
  • the time domain resource allocation may need to be expanded to point to aggregated slots.
  • the following is a more specific example of a time domain resource allocation method in a multi-slot aggregation situation.
  • RRC signaling to set (s) for time domain resources across multiple slots.
  • Each of the above sets may include a slot index and / or a last slot index at which PDSCH or PUSCH mapping starts, and / or a number of slots to be aggregated and / or a start symbol index for each aggregated slot and / Index, and the like.
  • the RRC setting may be set when the multi-slot aggregation operation is set, and may be set independently of the RRC setting for the time-domain resource allocation for one slot, superset).
  • a set of time-domain resources for one slot case may be utilized for aggregated slots. Characteristically, the start symbol index in the indicated set (finally in the DCI) can be applied in common to each of the aggregated slots. In the case of the CORESET section, it can be regarded as a suitable method since it can not be regarded as being changed in the aggregated slots. The last symbol index in the next indicated set may be to apply to a particular aggregated slot. Characteristically, the particular slot may be the last or first slot of the aggregated slots.
  • the last slot index for the remaining aggregated slots may be (1) RRC signaling, (2) RRC signaling and DCI indication (which may be characteristically in the form of SFI or SFI patterns), (3) SFI , And (4) an SFI pattern for the corresponding slots (received from the group common PDCCH).
  • the amount of DCI transmitted on the PDCCH can be reduced. More specifically, it is necessary to efficiently reduce the size of a specific field (in particular, the resource allocation field) of the contents of the DCI.
  • the resource allocation can be based on the RIV scheme (that is, a starting RB index and a number of consecutive RBs, or a method of representing a set of starting RBs and consecutive RBs for a specific set of RBs). This scheme can reduce the bit size required for resource allocation by expressing only consecutive resource allocations.
  • the RBG size is determined according to the system band, and in the case of the resource allocation type 0, resource allocation can be performed in units of RBG. In the above case, if the resource allocation is not in the RBG unit, waste of resources may occur.
  • the information on the step size or RBG size at the time of compact resource allocation may be set to a specific RBG size (for example, an RBG size set in linkage with a band) (E.g., via at least one of an upper layer signal, a group common PDCCH, or a third DCI).
  • a specific RBG size for example, an RBG size set in linkage with a band
  • the specific RBG may be larger or smaller than the set RBG size.
  • the same RBG can be handled / designated as the same resource as the other RBGs. That is, the RBGs allocated to the RBGs are allocated regardless of the size of the RBGs, and the indicated RBGs may be allocated PRBs according to the size of the RBGs.
  • the total bit size can be set.
  • the scheduling unit in the RIV scheme can be changed according to the RBG size indicated in the above situation. Therefore, when the indicated RBG size is larger than the specific RBG size referred to in the size setting, the bit field for RIV can be padded to match the total bit field size in which a specific value (e.g., 0) is set to the MSB or LSB. On the other hand, if the value is small, it is possible to assume that a single bit or a plurality of bits of the MSB or LSB are cut in the bit field for RIV, and that the cut bits are filled with a specific value (for example, 0) have.
  • a specific value for example, 0
  • Distributed resource allocation and / or frequency hopping may be required to ensure frequency diversity, which may be accomplished by applying interleaving after compact resource allocation.
  • interleaving method a method of inputting data in a matrix of a specific size in a row-by-row or a column-by-column manner and extracting data by columns (or rows) Interleaver method) can be used. Or perform interleaving based on a pseudo-random function. In this case, the position of the frequency resource can be shifted based on the random number.
  • the interleaving may be performed within the size of a scheduled active bandwidth part (BWP) of the PDSCH or PUSCH, or in a separate frequency domain (e.g., And / or via DCI).
  • BWP active bandwidth part
  • the same hopping pattern and inter-transport channel multiplexing can be ensured by aligning hopping regions equally between terminals having different bandwidths.
  • the hopping region may be non-contiguous, and based on this, overlapping resources between different band portions may be prevented.
  • the size of the row of the block interleaver may be set independently of the partial band size (for example, by using the third higher layer signaling). More specifically, it may be set via PBCH or RMSI, and may be updated with RRC.
  • the row size for the block interleaver may be set to be the same between the different partial bands. More specifically, the band of the UE may be divided into X partial regions, and the number of partial regions may be defined as the number of rows of the block interleaver matrix. In this case, the value of the specific region of the matrix may be filled with NULL, and the portion of the NULL may be skipped when extracting the index on a column-by-column basis. That is, the hopping region can be performed by avoiding the specific region through the above method.
  • the method of specifying NULL may be to select a particular row (s) (and / or an offset to elements) for the matrix for the block interleaver, or to select a starting element and a final element It is possible to do.
  • the above information may be an indication (e.g., upper layer signaling) by the base station.
  • Fig. 12 shows an example of hopping area setting.
  • the pseudo-random scheme it may be performed based on a cell ID, partial band specific information, or third signaling (e.g., virtual ID).
  • the above scheme can efficiently support multiplexing between UEs in a cell or a partial band while supporting inter-cell or partial-band randomization.
  • the unit of interleaving can be characteristically an RBG unit.
  • the RBG may be equal to or different from the RBG size at the time of the resource allocation instruction. That is, the BS can separately instruct the MS (e.g., higher layer signaling, group common PDCCH, or third DCI) for the RBG size assumed at the time of resource allocation and the RBG size assumed at the time of interleaving.
  • MS e.g., higher layer signaling, group common PDCCH, or third DCI
  • the frequency domain / resource may be different for each slot or for each symbol group.
  • the location of the PRB may be hopping based on a slot or a symbol index at which the PDSCH or PUSCH starts, or may be performed at a specific point in time Resource allocation may be performed based on the hopsed PRB index calculated based on the start of the frame, the start of the frame, and the like.
  • the hopping interval in the time domain is set to a fixed form (for example, a middle point in the slot or a distinction based on the interval between the seventh symbol and the eighth symbol) in consideration of multiplexing among a plurality of terminals . More specifically, the hopping interval in the time domain may be set to higher layer signaling (e.g., at least one of PBCH, RMSI, RRC) considering multiplexing between PDSCHs or PUSCHs with different number of configuration symbols and / . It may be that intra-slot frequency hopping is applied in non-slot based scheduling, and hopping is not performed in non-slot period.
  • a predetermined hopping region e.g., an active uplink band portion
  • a hopping region signaled by an upper layer e.g., PBCH or RMSI or RRC
  • the PUSCH or the PDSCH transmitted in the PRB N in the first hopping interval may be transmitted in the bandwidth of the ⁇ (PRB N + offset) mod uplink bandwidth portion ⁇ in the second hopping interval.
  • the hopping interval in the time domain is set to a fixed form (for example, a middle point in a slot or a division between a seventh symbol and an eighth symbol) in consideration of multiplexing between a plurality of terminals (E.g., PBCH or RMSI or RRC) considering the multiplexing between PDSCHs or PUSCHs with a different number of configuration symbols and / or may be directed at the DCI.
  • the offset may be a value that is signaled / set by a higher layer signal in a cell-specific manner, an offset value that is set for each band portion, or a hopping region as a parameter (e.g., 1 / N of the hopping region, 2 / N, ... (N-1) / N).
  • subband sizes / offsets and hopping patterns in frequency hopping can be set.
  • the setting may be set differently depending on the band part (BWP) configured.
  • BWP band part
  • a subband size and offset may be configured for each hopping pattern, and the value may be set differently for each band portion.
  • the hopping pattern to be used may be set differently for each band portion, or one of several hopping patterns may be set dynamically.
  • An example of such a hopping pattern is as follows.
  • Type 1 The index of RB or RBG can be increased by an offset value set in a cell-specific manner. This makes it possible to use the same hopping pattern even if the terminals have different band parts, thereby minimizing the occurrence of a collision due to inter-terminal hopping. Or the offset setting itself is performed for each band part, and it may be considered that the network sets the same value for a plurality of band parts.
  • Type 2 It is possible to increase the RB or RBG index by the corresponding value by dividing the hopping band set in the terminal by half as in LTE PUCCH type 1. This can increase the collision by hopping at different offsets between terminals having different band parts, but diversity gain can be obtained. When using this scheme, it is possible to have offset with a specific value rather than dividing the hopping band by half.
  • Type 3 LTE PUCCH It is possible to apply hopping to a hopping band larger than its own band part like type 2. If it is hops to an RB or RBG index that is larger than the band portion by hopping, it may be to move the absolute frequency location of the uplink band portion according to the hopping. Alternatively, multi-level hopping may be performed when hopping is applied. For example, one uplink band part may be divided into several subbands, type 1 or 2 may be performed in the subband, and type 1 or type 2 may be performed again for each subband.
  • the hopping in the initial uplink band portion in which the message 3 is transmitted may also be in accordance with the above scheme, and the hopping scheme may be transmitted in the random access response (RAR).
  • RAR random access response
  • the frequency hopping can be performed within the hopping band set based on the common PRB indexing, and the hopping band can be set by the RSMI or the like.
  • the physical location of the initial uplink band portion may be changed by the corresponding hopping. This may be applicable only for inter-slot hopping, or only for initial transmission or retransmission of message 3.
  • inter-slot hopping can be performed within the cell common or group common hopping band based on the common PRB indexing, and in intra-slot hopping, within the active band portion of the UE .
  • the advantage of this scheme is that when the RBG size is small (e.g., 1 RB granularity), when performing RIV mode resource allocation, it is performed with 1 RB granularity and then only interleaving is performed with RBG size granularity It is a point.
  • An advantage of this scheme is that resource allocation can be performed smaller than the RBG size while simultaneously allocating RBs can be distributed while considering multiplexing with other PDSCHs or PUSCHs (i.e., maintaining the RBG grid).
  • the relationship between possible resource combinations may have a nested structure.
  • the starting RB may be limited.
  • CP-OFDM and DFT-S-OFDM may be supported. And / or for certain situations, only contiguous resource allocation may be allowed in performing resource allocation, or discontinuous resource allocation and / or continuous resource allocation may be allowed.
  • the resource allocation type or method can be set differently according to the waveform.
  • the selection for the waveform may follow the setting of upper layer signaling.
  • the DCI size between different waveforms and / or the resource allocation field size may be set different from each other.
  • the waveform is to be changed flexibly, it may be necessary to match the DCI size and / or the resource allocation field size equally.
  • the resource allocation field may be configured identically regardless of the waveform.
  • the continuous resource allocation can be indicated according to the set value.
  • the scheme can be extended to equalize the size and / or resource allocation field between DCI for PDSCH scheduling and DCI for PUSCH scheduling.
  • the resource allocation field size and / or the DCI size may be different for a type that supports continuous resource allocation only and a type that can support non-contiguous resource allocation.
  • a TM-independent PDSCH DCI that schedules PUSCH that only supports continuous resource allocation or that has a waveform of DFT-S-OFDM is DCI that schedules a PDSCH that is set to the same size and is TM-dependent
  • the DCI that supports the non-contiguous resource allocation or that schedules the PUSCH with a waveform of CP-OFDM may be set to the same size.
  • the UE may change the waveform according to the detected DCI or the resource allocation type included therein.
  • the waveform of the corresponding PUSCH may be DFT-S-OFDM, and otherwise the CP-OFDM.
  • the RBG can be used as a basic unit of a bitmap when allocating frequency resources.
  • PRG is precoder granularity, it can be assumed that the same precoder is applied to PRBs in the same PRG.
  • the PRG can be used as a basic unit for channel estimation based on the PRG.
  • the PRG can be set on the basis of the common resource block regardless of the band part, considering multi-user MIMO (MU-MIMO) among terminals with different band parts set.
  • MU-MIMO multi-user MIMO
  • RBG and PRG are not aligned, a situation may occur in which a single PRG overlaps a plurality of RBGs as described above. Similar to the above situation, interpolation is limited according to the scheduling, so that channel estimation performance may be degraded.
  • both RBG and PRG can be defined / set on the basis of a common resource block (CRB or system band).
  • a common resource block CRB or system band.
  • an RB constituting an RBG can be configured from a CRB # 0 to a frequency increasing order.
  • the first RBG in the band part can be set to ⁇ (indicated RBG size - start of band part) mod indicated RBG size ⁇ .
  • the indicated RBG size may be a value set according to the size of the band portion and / or according to a table set by an upper layer and / or a designated band portion and / or a band portion in which the DCI is transmitted.
  • the last RBG may be ⁇ (band portion start + band portion size) mode (indicated RBG size or indicated RBG size). The resulting value of the above equation may be zero.
  • the remaining RBG may be the indicated RBG size.
  • the starting CRB index for the band portion may be set to a multiple of a specific PRG size (e.g., 2 or 4). That is, the start CRB index of the band portion can be expected to be set such that RBG and PRG are aligned on the boundary side.
  • a specific PRG size e.g. 2 or 4
  • the number of RBGs can be determined according to the band part start RB, the band part size and the indicated RBG size. If the band portion starting RB is divided by the indicated RBG size, the number of RBGs in the band portion can be set to raise ⁇ band portion size / indicated RBG ⁇ . If the band portion starting RB is not divided by the indicated RBG size, the number of RBGs may be increased by ⁇ band portion size / indicated RBG ⁇ + 1.
  • the number of RBGs in a band portion may be expressed as Ceiling (band portion size / indicated RBG size) + Ceiling ((band part start index mod indicated RBG size / indicated RBG size)) , Ceiling ((band portion size + band portion start index mod indicated RBG size) / indicated RBG size).
  • the bit field size of the frequency domain resource allocation type 0 can be determined based on the number of RBGs.
  • the reference band part may be the largest of the set bandwidth parts, the band part where the DCI is transmitted, or the band part where the scheduled PDSCH or PUSCH is transmitted.
  • the interleaved VRB-PDSCH for the PDSCH (hereinafter referred to as RMSI-PDSCH) including the RMSI scheduled by the DCI format 1_0 in the common search space of CORESET 0, You need to define whether to perform to-PRB mapping or how to perform it.
  • N start BWP, i and N size BWP, i can be defined.
  • the UE may not know the above values until receiving the RMSI.
  • the RMSI-PDSCH may consider supporting only non-interleaved VRB-to-PRB mapping. In this case, the reception performance of the RMSI may be degraded due to the lack of frequency diversity.
  • a resource block bundle for the RMSI-PDSCH may be defined in the initial downlink band partial grid.
  • the resource block bundle starts from the first resource block index of the initial downlink band part, and all resource block bundles may be composed of, for example, two consecutive resource blocks.
  • Proposal 1 Interleaved VRB-to-PRB mapping can be used for the PDSCH including the RMSI in the initial downlink band portion.
  • the resource block bundle can be defined in the initial downlink band portion without considering the common resource block grid.
  • the common resource block grid After receiving the RMSI, the common resource block grid is announced to the UE. Then, all the techniques based on the common resource block grid become available. In this case, if the PDSCH including the RMSI is received in a downlink band portion other than the initial downlink band portion, the resource block bundles for the interleaved VRB-to-PRB mapping may be defined to be aligned in the common resource block grid .
  • the UE can receive another PDSCH (i.e., PDSCH not including RMSI) in the initial downlink band portion.
  • PDSCH i.e., PDSCH not including RMSI
  • the definition of the resource block bundle is the same regardless of the RNTI applied to the PDSCH.
  • the RNTI regardless of the RNTI, it can be assumed that all PDSCH mappings in the initial downlink band portion are defined in the initial downlink band portion without consideration of the common resource block grid.
  • the RBG may be defined without considering the common resource block grid.
  • Proposal 2 For PDSCH including OSI, paging, random access response (RAR) in the initial downlink band portion, etc., the resource block bundle can be defined in the initial downlink band portion without consideration of the common resource block grid.
  • the interleaver bundle may be defined / set with respect to the (initial) band portion instead of the CRB in the following exceptional situations.
  • the exception is when the DCI schedules an RMSI or when the DCI belongs to a CORESET # 0 associated with a common search space (CSS) in scheduling an RMSI, or when the DCI belongs to a CSS, or when the DCI is in the CSS of an initial downlink band Or the DCI belongs to the initial downlink band part.
  • the RBG in the resource allocation of the bitmap scheme can be set with the exception of the CRB in the above situation (with the boundaries aligned) based on the band portion.
  • the DCI scrambled by the SI-RNTI may indicate whether the DCI scrambled by the SI-RNTI constitutes a resource block bundle for interleaved VRB-to-PRB mapping.
  • the DCI can indicate whether the size of the first resource block bundle is 1 or 2 according to the starting RB index of the initial downlink band portion / RTI >
  • the resource block bundle may be arranged in the common resource block grid in the RMSI-PDSCH.
  • the DCI scrambled in the SI-RNTI can be used to construct a resource block bundle in the DCI scheduling PDSCH (N start BWP, i mod 2), or the size of the first resource block bundle, And an offset value between block grids.
  • the number of DCI sizes to be monitored by the UE may be limited for the purpose of lowering the complexity of the UE. More specifically, the DCI format 1_0 and the DCI format 0_0 (hereinafter referred to as fallback DCI), when transmitted in a specific search space (for example, a UE-specific search space)
  • the resource allocation bit field may be configured based on the initial (downlink) band portion size (when the number of DCI sizes is sufficient), or the resource allocation bit field may be configured based on the initial (downlink) band portion size Or you want to cross it).
  • the resource allocation bit field when the bit size of the resource allocation field is equal to the size of the resource allocation field required in the band portion to which the DCI belongs (or when the bit size of the resource allocation field is set larger), the lowest resource block The index (lowest RB index) is matched with the smallest RB index of the corresponding band part, and the highest RB index can be matched with the largest RB index of the corresponding band part.
  • the above-mentioned area may be applied to the area to be interleaved equally.
  • the bit size of the resource allocation field is smaller than the resource allocation field size required in the band portion
  • the lowest RB index corresponding to the resource allocation field is matched with the smallest RB index of the corresponding band portion, May be matched to an RB index that is separated by an initial (downlink) band portion from the smallest RB index of the corresponding band portion.
  • This is to perform resource allocation more efficiently due to the bit size limit of the resource allocation field.
  • the area to be interleaved may also be set based on an area set to be smaller than the actual band part. Alternatively, as part of a method for exploiting the advantages of the relatively large activation band portion, it may be considered that the object region of the interleaving is still set to the activation band portion.
  • the zero-padding is set to LSB Or MSB.
  • FIG. 13 is a block diagram illustrating an apparatus in which an embodiment of the present invention is implemented.
  • the apparatus 100 includes a processor 110, a memory 120, and a transceiver 130.
  • the processor 110 implements the proposed functions, processes and / or methods.
  • the memory 120 is connected to the processor 110 and stores various information for driving the processor 110.
  • Transceiver 130 is coupled to processor 110 to transmit and / or receive wireless signals.
  • the device 100 may be a base station or a terminal.
  • the processor 110 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, a data processing device, and / or a converter for converting baseband signals and radio signals.
  • Memory 120 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices.
  • Transceiver 130 may include one or more antennas for transmitting and / or receiving wireless signals.
  • the above-described techniques may be implemented with modules (processes, functions, and so on) that perform the functions described above.
  • the modules may be stored in the memory 120 and executed by the processor 110.
  • the memory 120 may be internal or external to the processor 110 and may be coupled with the processor 110 in a variety of well known ways.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil permettant d'attribuer des ressources dans un système de communication sans fil. Le procédé génère, dans une taille de bit de premières informations d'attribution de ressource utilisées pour planifier une première bande, des secondes informations d'attribution de ressource pour planifier une seconde bande, et transmet les secondes informations d'attribution de ressource à travers la première bande.
PCT/KR2018/007607 2017-09-07 2018-07-05 Procédé permettant d'attribuer des ressources dans un système de communication sans fil et appareil utilisant le procédé WO2019050143A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN201880044119.5A CN110832931B (zh) 2017-09-07 2018-07-05 在无线通信系统中分配资源的方法和使用该方法的设备
JP2020513744A JP7254776B2 (ja) 2017-09-07 2018-07-05 無線通信システムにおけるリソース割当方法及び前記方法を利用する装置
EP21205974.5A EP3968719B1 (fr) 2017-09-07 2018-07-05 Procédé d'attribution de ressources dans un système de communication sans fil et appareil faisant appel audit procédé
EP18854713.7A EP3664549B1 (fr) 2017-09-07 2018-07-05 Procédé et station de base permettant d'attribuer des ressources dans un système de communication sans fil
US16/717,392 US10880869B2 (en) 2017-09-07 2019-12-17 Method for allocating resources in wireless communication system, and apparatus using method

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US201762555624P 2017-09-07 2017-09-07
US62/555,624 2017-09-07
US201762576633P 2017-10-24 2017-10-24
US62/576,633 2017-10-24
US201762588290P 2017-11-17 2017-11-17
US62/588,290 2017-11-17
US201862670017P 2018-05-11 2018-05-11
US62/670,017 2018-05-11
KR1020180077736A KR20190027705A (ko) 2017-09-07 2018-07-04 무선 통신 시스템에서 자원 할당 방법 및 상기 방법을 이용하는 장치
KR10-2018-0077736 2018-07-04

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/717,392 Continuation US10880869B2 (en) 2017-09-07 2019-12-17 Method for allocating resources in wireless communication system, and apparatus using method

Publications (1)

Publication Number Publication Date
WO2019050143A1 true WO2019050143A1 (fr) 2019-03-14

Family

ID=65634323

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/007607 WO2019050143A1 (fr) 2017-09-07 2018-07-05 Procédé permettant d'attribuer des ressources dans un système de communication sans fil et appareil utilisant le procédé

Country Status (1)

Country Link
WO (1) WO2019050143A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111757491A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种资源指示的方法、设备及计算机可读存储介质
CN111867088A (zh) * 2019-04-30 2020-10-30 中国移动通信有限公司研究院 一种物理上行共享信道的传输方法和终端、网络设备
US20210204285A1 (en) * 2018-09-17 2021-07-01 Huawei Technologies Co., Ltd. Data Transmission Method and Communications Apparatus
CN113711673A (zh) * 2019-04-26 2021-11-26 高通股份有限公司 用于无线通信中的增强的反馈的上行链路调度技术
JP2022524647A (ja) * 2019-03-29 2022-05-09 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおけるサイドリンク通信のための制御情報を送受信する方法及び装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101058720B1 (ko) * 2007-10-12 2011-08-22 삼성전자주식회사 통신 시스템에서 자원 할당 정보 송수신 장치 및 방법
KR101445078B1 (ko) * 2007-10-04 2014-11-03 삼성전자주식회사 릴레이 시스템 및 상기 릴레이 시스템을 위한 데이터프레임 구조
KR101479011B1 (ko) * 2008-12-17 2015-01-13 삼성전자주식회사 다중 대역 스케쥴링 방법 및 이를 이용한 방송 서비스 시스템
KR101641803B1 (ko) * 2008-06-12 2016-07-21 애플 인크. Ｓｃ-ｆｄｍａ 전송 다이버시티 시스템 및 방법
KR20170038800A (ko) * 2014-07-30 2017-04-07 퀄컴 인코포레이티드 Lte 공존을 위한 wlan 패킷마다의 대역폭 스케줄링

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101445078B1 (ko) * 2007-10-04 2014-11-03 삼성전자주식회사 릴레이 시스템 및 상기 릴레이 시스템을 위한 데이터프레임 구조
KR101058720B1 (ko) * 2007-10-12 2011-08-22 삼성전자주식회사 통신 시스템에서 자원 할당 정보 송수신 장치 및 방법
KR101641803B1 (ko) * 2008-06-12 2016-07-21 애플 인크. Ｓｃ-ｆｄｍａ 전송 다이버시티 시스템 및 방법
KR101479011B1 (ko) * 2008-12-17 2015-01-13 삼성전자주식회사 다중 대역 스케쥴링 방법 및 이를 이용한 방송 서비스 시스템
KR20170038800A (ko) * 2014-07-30 2017-04-07 퀄컴 인코포레이티드 Lte 공존을 위한 wlan 패킷마다의 대역폭 스케줄링

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3664549A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210204285A1 (en) * 2018-09-17 2021-07-01 Huawei Technologies Co., Ltd. Data Transmission Method and Communications Apparatus
CN111757491A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种资源指示的方法、设备及计算机可读存储介质
JP2022524647A (ja) * 2019-03-29 2022-05-09 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおけるサイドリンク通信のための制御情報を送受信する方法及び装置
CN113711673A (zh) * 2019-04-26 2021-11-26 高通股份有限公司 用于无线通信中的增强的反馈的上行链路调度技术
CN111867088A (zh) * 2019-04-30 2020-10-30 中国移动通信有限公司研究院 一种物理上行共享信道的传输方法和终端、网络设备

Similar Documents

Publication Publication Date Title
WO2020222575A1 (fr) Procédé et appareil pour la transmission et la réception de rétroaction de liaison latérale dans un système de communication sans fil
WO2018226054A1 (fr) Procédé de signalisation associé à l'attribution de ressources dans un système de communications sans fil, et dispositif l'utilisant
WO2019139207A1 (fr) Procédé de réception d'un signal de liaison descendante par un terminal dans un système de communication sans fil, et terminal utilisant ce procédé
WO2018199685A1 (fr) Procédé de transmission et de réception d'un canal de liaison descendante et d'un signal de référence dans un système de communication
WO2019216599A1 (fr) Procédé de transmission et de réception de signaux pour une communication à faible latence ultra-fiable
WO2019139436A1 (fr) Procédé de réalisation de transmission de canal de commande physique en liaison montante dans un système de communication sans fil et terminal utilisant le procédé
WO2019139444A1 (fr) Procédé, dispositif et système d'attribution de ressources pour système de communication sans fil
WO2020197215A1 (fr) Procédé et appareil de réception de canal de commande dans des systèmes de communication sans fil
WO2018030858A1 (fr) Procédé destiné à un terminal de transmission d'informations de commande de liaison montante et terminal utilisant ce procédé
WO2018182263A1 (fr) Procédé de communication v2x d'un terminal dans un système de communication sans fil, et terminal utilisant ledit procédé
WO2020145769A1 (fr) Procédé de transmission de canal partagé de liaison montante dans un système de communication sans fil et dispositif faisant appel à celui-ci
WO2019050371A1 (fr) Procédé de transmission et procédé de réception de données pour système de communication sans fil et appareil utilisant les procédés
WO2011084020A2 (fr) Procédé et appareil permettant de transmettre des informations de commande de liaison montante dans un système de communication sans fil pour supporter de multiples porteuses
WO2019031787A1 (fr) Procédé et dispositif permettant de recevoir un signal 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é
WO2020197354A1 (fr) Procédé et appareil d'émission et de réception de données multiples dans un système de communication coopératif sans fil
WO2018190678A1 (fr) Procédé et appareil permettant d'effectuer une connexion initiale dans un système de communication sans fil
WO2019083341A1 (fr) Procédé de fonctionnement de dispositif dans un système de communication sans fil, et dispositif associé
WO2021145640A1 (fr) Procédé et appareil permettant de transmettre et de recevoir des informations de commande de liaison descendante dans un système de communication sans fil
WO2012039570A2 (fr) Procédé d'affectation d'une ressource pucch pour l'émission d'un signal ack/nack, et appareil d'émission l'utilisant
WO2021158087A1 (fr) Procédé et appareil de transmission d'informations de commande pour une communication collaborative en réseau
WO2021066449A1 (fr) Procédé et appareil de transmission et de réception répétées dans un système de communication sans fil
WO2020231182A1 (fr) Procédé et dispositif de transmission d'informations de commande dans un système de communication sans fil
WO2019098748A1 (fr) Procédé et dispositif de réception de signal dans un système de communication sans fil
WO2020222576A1 (fr) Procédé et appareil permettant de déterminer une procédure d'accès au canal dans un système de communication sans fil

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020513744

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

Country of ref document: EP

Effective date: 20200306