[go: up one dir, main page]

WO2024171520A1 - Station de base, terminal, et procédé de communication - Google Patents

Station de base, terminal, et procédé de communication Download PDF

Info

Publication number
WO2024171520A1
WO2024171520A1 PCT/JP2023/037876 JP2023037876W WO2024171520A1 WO 2024171520 A1 WO2024171520 A1 WO 2024171520A1 JP 2023037876 W JP2023037876 W JP 2023037876W WO 2024171520 A1 WO2024171520 A1 WO 2024171520A1
Authority
WO
WIPO (PCT)
Prior art keywords
band
base station
resource block
resource allocation
transmission direction
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/JP2023/037876
Other languages
English (en)
Japanese (ja)
Inventor
知也 布目
秀俊 鈴木
綾子 堀内
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Panasonic Intellectual Property Corp of America
Original Assignee
Panasonic Intellectual Property Corp of America
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Panasonic Intellectual Property Corp of America filed Critical Panasonic Intellectual Property Corp of America
Priority to JP2025500648A priority Critical patent/JPWO2024171520A1/ja
Publication of WO2024171520A1 publication Critical patent/WO2024171520A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA

Definitions

  • This disclosure relates to a base station, a terminal, and a communication method.
  • the 3rd Generation Partnership Project (3GPP) has completed the formulation of the physical layer specifications for Release 17 NR (New Radio access technology) as a functional extension of 5th generation mobile communication systems (5G).
  • 5G 5th generation mobile communication systems
  • NR will support enhanced mobile broadband (eMBB) to meet the requirements of high speed and large capacity, as well as functions that realize ultra-reliable and low latency communication (URLLC) (see, for example, non-patent literature 1-5).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low latency communication
  • 3GPP TS 38.211 V17.4.0 "NR; Physical channels and modulation (Release 17),” December 2022 3GPP TS 38.212 V17.4.0, “NR; Multiplexing and channel coding (Release 17),” December 2022 3GPP TS 38.213 V17.4.0, “NR; Physical layer procedure for control (Release 17),” December 2022 3GPP TS 38.214 V17.4.0, “NR; Physical layer procedures for data (Release 17),” December 2022 3GPP TS 38.331 V17.3.0, “NR; Radio Resource Control (RRC) protocol specification (Release 17)", December 2022
  • RRC Radio Resource Control
  • Non-limiting examples of the present disclosure contribute to providing a base station, a terminal, and a communication method that can appropriately allocate resources in wireless communication.
  • a base station includes a control circuit that varies resource allocation depending on whether a first band corresponding to a first transmission direction is arranged discontinuously in a physical resource block in a method in which a transmission direction is set for each of a plurality of bands obtained by dividing a frequency band, and a transmission circuit that transmits a signal according to the resource allocation.
  • resource allocation in wireless communication can be performed appropriately.
  • Diagram showing an example of the Duplex method A diagram showing an example of subbands and guard bands in subband non-overlapping full duplex (SBFD).
  • Block diagram showing a partial configuration example of a terminal Block diagram showing a configuration example of a base station Block diagram showing an example of a terminal configuration
  • Diagram showing an example of mapping of Virtual Resource Block (VRB) and Physical Resource Block (PRB) A diagram showing an example of VRB and PRB mapping.
  • a diagram showing an example of resource allocation A diagram showing an example of the mapping between Resource Indication Value (RIV) and resource allocation
  • RRC Radio Resource Control
  • Diagram of an example architecture for a 3GPP NR system Schematic diagram showing functional separation between NG-RAN (Next Generation - Radio Access Network) and 5GC (5th Generation Core) Sequence diagram of Radio Resource Control (RRC) connection setup/reconfiguration procedure
  • RRC Radio Resource Control
  • eMBB enhanced Mobile BroadBand
  • mMTC massive Machine Type Communications
  • URLLC Ultra Reliable and Low Latency Communications
  • SBFD Subband non-overlapping full duplex
  • Figure 1 shows an example of the Duplex method.
  • the vertical axis represents frequency
  • the horizontal axis represents time.
  • “U” represents uplink transmission
  • “D” represents downlink transmission.
  • Figure 1(a) shows an example of half duplex Time Division Duplex (TDD).
  • a terminal UE: User Equipment
  • a base station e.g., a gNB
  • the transmission direction e.g., downlink or uplink
  • the transmission direction in a certain time resource may be common between the base station and the terminal.
  • the transmission direction in a certain time resource does not differ between terminals.
  • Figure 1(b) shows an example of SBFD.
  • SBFD a frequency resource (or a frequency band) is divided into multiple bands (e.g., subbands, RB sets, subbands, or sub-BWPs (Bandwidth parts)), and transmission in different directions (e.g., downlink or uplink) is supported for each subband.
  • a terminal transmits and receives either uplink or downlink in a certain time resource, but does not transmit or receive in the other.
  • SBFD a base station can transmit and receive in uplink and downlink simultaneously.
  • a terminal does not use resources in the transmission direction in a certain time resource (e.g., resources shown by dotted lines in Figure 1(b)).
  • a guard band may be placed between the uplink band (UL sub-band: U) and the downlink sub-band (DL sub-band: D).
  • the guard band may be used to reduce interference (CLI: Cross link interference) between different transmission directions (links).
  • the subband configuration will be written as ⁇ X...X ⁇ , where X represents the UL subband (U) or DL subband (D).
  • X represents the UL subband (U) or DL subband (D).
  • the order of notation corresponds to the order in which the subbands are arranged.
  • the subband configuration in Figure 1(b) will be written as ⁇ DUD ⁇ .
  • Resource allocation method One of the resource allocation methods for the data channel is Resource Allocation Type 1 (RA type 1), which is used, for example, to allocate consecutive resources.
  • RA type 1 Resource Allocation Type 1
  • RB start Resource block (RB) number from which resource allocation begins
  • L RB Length of consecutively allocated RBs (e.g., number of RBs)
  • RIV Resource indication value
  • VRB-to-PRB mapping may be applied to resource allocation.
  • VRB-to-PRB mapping is used to map from a virtual resource block (VRB) to a physical resource block (PRB). There may be two mapping methods: Interleaved VRB-to-PRB mapping, where interleaving is applied, and Non-interleaved VRB-to-PRB mapping, where interleaving is not applied.
  • the VRB and PRB may be the same.
  • VRB#n may be mapped to PRB#n (n indicates the RB number).
  • the VRB In Interleaved VRB-to-PRB mapping, the VRB is mapped to the PRB via an interleaver. Therefore, when RA type 1 and Interleaved VRB-to-PRB mapping are used for resource allocation, the VRB will have contiguous allocation, but the PRB may have discontiguous resource allocation.
  • DL subbands can be arranged non-contiguously, for example, as in ⁇ DUD ⁇ .
  • resource allocation for a data channel e.g., PDSCH: Physical Downlink Shared Channel
  • the guard band may be used to reduce the leakage of CLI from adjacent subbands.
  • Figure 2 shows an example of guard bands in a subband arrangement of ⁇ DUD ⁇ .
  • the size of the guard band that is set may vary depending on, for example, the size of the CLI. For example, when the CLI is large, a wide guard band (e.g., a guard band with a large number of RBs) is expected to be set, and when the CLI is small, a narrow guard band (e.g., a guard band with a small number of RBs) may be sufficient.
  • a wide guard band e.g., a guard band with a large number of RBs
  • a narrow guard band e.g., a guard band with a small number of RBs
  • the CLI is not necessarily constant, and so the required guardband size can change dynamically. Therefore, it is expected that resources can be used efficiently by dynamically setting (or changing or adjusting) the guardband size according to the CLI.
  • the following are some examples of methods for dynamically adjusting the guardband size through resource allocation.
  • Adjustment method 1 is a method of not allocating transmission/reception resources to RBs (eg, one or more) adjacent to other subbands in the DL subband or the UL subband.
  • Adjustment method 1 is, for example, a method for widening the size of the guard band, so the size of the guard band that is set (or defined) in advance can be small.
  • Adjustment method 2 is a method of allocating DL resources or UL resources to RBs within the guard band.
  • RBs e.g., one or more in the guard band adjacent to the DL subband are allocated.
  • RBs e.g., one or more in the guard band adjacent to the UL subband are allocated. Since adjustment method 2 is, for example, a method of narrowing the size of the guard band, the size of the guard band that is set (or defined) in advance may be wide.
  • a communication system may include, for example, a base station 100 (e.g., gNB) shown in Fig. 3 and Fig. 5, and a terminal 200 (e.g., UE) shown in Fig. 4 and Fig. 6.
  • a base station 100 e.g., gNB
  • a terminal 200 e.g., UE
  • a plurality of base stations 100 and a plurality of terminals 200 may exist in the communication system.
  • FIG. 3 is a block diagram showing an example configuration of a portion of a base station 100 according to one aspect of the present disclosure.
  • a control unit e.g., corresponding to a control circuit
  • a transmission unit (e.g., corresponding to a transmission circuit) transmits a signal according to the resource allocation.
  • FIG. 4 is a block diagram showing an example of a configuration of a portion of a terminal 200 according to one aspect of the present disclosure.
  • a control unit e.g., corresponding to a control circuit
  • a receiving unit e.g., a receiving circuit receives a signal according to the resource allocation.
  • FIG. 5 is a block diagram showing a configuration example of a base station 100 according to an embodiment of the present disclosure.
  • the base station 100 includes a receiving unit 101, a demapping unit 102, a demodulation and decoding unit 103, a scheduling unit 104, a resource control unit 105, a control information holding unit 106, a data and control information generating unit 107, an encoding and modulation unit 108, a mapping unit 109, and a transmitting unit 110.
  • the demapping unit 102 demodulation/decoding unit 103, scheduling unit 104, resource control unit 105, control information storage unit 106, data/control information generation unit 107, coding/modulation unit 108, and mapping unit 109 may be included in the control unit shown in FIG. 3, and the transmission unit 110 may be included in the transmission unit shown in FIG. 3.
  • the receiving unit 101 performs reception processing, such as down-conversion or A/D conversion, on a received signal received via an antenna, and outputs the received signal after reception processing to the demapping unit 102.
  • the receiving unit 101 also measures the amount of interference from the downlink signal to the uplink signal, and outputs information about the measurement result (for example, called DL-UL interference information) to the resource control unit 105.
  • the demapping unit 102 performs resource demapping on the received signal (e.g., an uplink signal) input from the receiving unit 101, and outputs the modulated signal to the demodulation and decoding unit 103.
  • the received signal e.g., an uplink signal
  • the demodulation and decoding unit 103 demodulates and decodes the modulated signal input from the demapping unit 102, and outputs the decoded result to the scheduling unit 104.
  • the demodulation and decoding unit 103 outputs the UL-DL interference information to the resource control unit 105.
  • the scheduling unit 104 may, for example, perform scheduling for the terminals 200.
  • the scheduling unit 104 schedules transmission and reception for each terminal 200 based on, for example, at least one of the decoding results input from the demodulation and decoding unit 103 and the control information input from the control information storage unit 106, and instructs the data and control information generation unit 107 to generate at least one of data and control information.
  • the scheduling unit 104 may also output the scheduling information to the resource control unit 105.
  • the scheduling unit 104 may also output control information related to scheduling for the terminals 200 to the control information storage unit 106.
  • the resource control unit 105 may determine the size of the guard band based on the DL-UL interference information input from the receiving unit 101, the UL-DL interference information input from the demodulation and decoding unit 103, and the scheduling information input from the scheduling unit 104. Also, for example, the resource control unit 105 determines the resources to be used by each terminal 200 for downlink transmission based on, for example, the control information input from the control information holding unit 106, the scheduling information input from the scheduling unit 104, and the determined guard band size, and outputs resource allocation information to the data and control information generating unit 107 and the mapping unit 109.
  • the control information storage unit 106 stores, for example, control information set for each terminal 200.
  • the control information may include, for example, downlink data channel settings for each terminal 200 (for example, information related to SBFD or resource allocation).
  • the control information storage unit 106 may output the stored information to each component of the base station 100 (for example, the scheduling unit 104 and the resource control unit 105) as necessary.
  • the data and control information generating unit 107 generates at least one of data and control information, for example, according to instructions from the scheduling unit 104, and outputs a signal including the generated data or control information to the coding and modulation unit 108.
  • the data and control information generating unit 107 may generate control information for the terminal 200, for example, based on resource allocation information input from the resource control unit 105.
  • the encoding and modulation unit 108 encodes and modulates, for example, the signal (e.g., data, control information) input from the data and control information generation unit 107, and outputs the modulated signal to the transmission unit 110.
  • the signal e.g., data, control information
  • the mapping unit 109 performs resource mapping of the modulated signal input from the coding and modulation unit 108 based on, for example, resource allocation information input from the resource control unit 105, and outputs the transmission signal to the transmission unit 110.
  • the transmitting unit 110 performs transmission processing such as D/A conversion, up-conversion, or amplification on the signal input from the mapping unit 109, and transmits the radio signal obtained by the transmission processing from the antenna to the terminal 200.
  • FIG. 6 is a block diagram showing a configuration example of a terminal 200 according to an aspect of the present disclosure.
  • the terminal 200 includes a receiving unit 201, a demapping unit 202, a demodulation and decoding unit 203, a resource determining unit 204, a control unit 205, a control information holding unit 206, a data and control information generating unit 207, an encoding and modulation unit 208, a mapping unit 209, and a transmitting unit 210.
  • the demapping unit 202 demodulation/decoding unit 203, resource determination unit 204, control unit 205, control information storage unit 206, data/control information generation unit 207, coding/modulation unit 208, and mapping unit 209 may be included in the control unit shown in FIG. 4, and the receiving unit 201 may be included in the receiving unit shown in FIG. 4.
  • the receiving unit 201 performs reception processing, such as down-conversion or A/D conversion, on the received signal received via the antenna, and outputs the received signal after reception processing to the demapping unit 202.
  • reception processing such as down-conversion or A/D conversion
  • the demapping unit 202 performs resource demapping on the received signal input from the receiving unit 201 based on, for example, resource allocation information input from the resource determination unit 204, and outputs the modulated signal to the demodulation and decoding unit 203.
  • the demodulation and decoding unit 203 demodulates and decodes the modulated signal input from the demapping unit 202, and outputs the decoded result to the resource determination unit 204 and the control unit 205.
  • the decoded result may include, for example, at least one of upper layer signaling information and downlink control information.
  • the resource determination unit 204 determines the allocated resources based on, for example, the control information input from the control information storage unit 206 or the decoded result of the control information input from the demodulation and decoding unit 203, and outputs the resource allocation information to the demapping unit 202.
  • the control unit 205 may determine whether data or control information is to be transmitted or received, for example, based on the decoding result (e.g., data or control information) input from the demodulation and decoding unit 203 and the control information input from the control information storage unit 206. For example, if the determination result indicates that data or control information is to be transmitted, the control unit 205 may instruct the data and control information generation unit 207 to generate at least one of the data and the control information.
  • the decoding result e.g., data or control information
  • the control unit 205 may instruct the data and control information generation unit 207 to generate at least one of the data and the control information.
  • the control information storage unit 206 stores, for example, control information input from the control unit 205, and outputs the stored information to each component (for example, the resource determination unit 204 and the control unit 205) as necessary.
  • the data and control information generating unit 207 generates data or control information, for example, according to instructions from the control unit 205, and outputs a signal including the generated data or control information to the coding and modulation unit 208.
  • the control information may include, for example, UL-DL interference information measured by the terminal 200 (for example, information regarding the amount of interference from the uplink to the downlink measured by the terminal 200).
  • the encoding and modulation unit 208 for example, encodes and modulates the signal input from the data and control information generation unit 207, and outputs the modulated signal to the mapping unit 209.
  • the mapping unit 209 performs resource mapping on the modulated signal input from the coding and modulation unit 208, and outputs the transmission signal to the transmission unit 210.
  • the transmitter 210 performs transmission processing such as D/A conversion, up-conversion, or amplification on the signal input from the mapping unit 209, and transmits the radio signal obtained by the transmission processing from the antenna to the base station 100.
  • FIG. 7 is a sequence diagram showing an example of the operation of the base station 100 and the terminal 200.
  • the base station 100 determines, for example, information regarding SBFD or resource allocation configuration (S101).
  • the base station 100 transmits, for example, upper layer signaling information including the determined configuration information to the terminal 200 (S102).
  • the base station 100 determines, for the terminal 200, the guard band size to be used for the terminal 200's downlink reception or the base station 100's uplink reception, for example, based on the CLI (S103).
  • the base station 100 schedules the transmission of downlink data (e.g., PDSCH) and allocates resources to the terminal 200, for example, based on the set guard band size (S104).
  • downlink data e.g., PDSCH
  • S104 set guard band size
  • Base station 100 transmits a downlink control signal (e.g., PDCCH: Physical Downlink Control Channel) based on, for example, the scheduling result (S105).
  • a downlink control signal e.g., PDCCH: Physical Downlink Control Channel
  • the terminal 200 identifies (or determines, or identifies) the resource allocation (time/frequency resources) for downlink data (e.g., PDSCH) based on the PDCCH transmitted from the base station 100 (S106).
  • the resource allocation time/frequency resources for downlink data (e.g., PDSCH) based on the PDCCH transmitted from the base station 100 (S106).
  • Base station 100 transmits downlink data (e.g., PDSCH) according to the scheduling result, and terminal 200 receives downlink data (e.g., PDSCH) based on the determined resource allocation (S107).
  • downlink data e.g., PDSCH
  • terminal 200 receives downlink data (e.g., PDSCH) based on the determined resource allocation (S107).
  • a resource allocation method in the base station 100 (e.g., the resource control unit 105) will be described.
  • the terminal 200 e.g., the resource determination unit 204) may determine the allocated resources assuming the resource allocation method implemented by the base station 100.
  • the base station 100 applies RA type 1 to PDSCH resource allocation, for example.
  • the base station 100 transmits to the terminal 200 control information including information (e.g., RB start ) on the start position of an RB (e.g., VRB) including at least a DL subband, and the number of RBs (e.g., the number of VRBs, L RB ) consecutive from the start position.
  • Method 1 As a method for performing discontinuous resource allocation to DL subbands using RA type 1, a UL subband and a VRB that does not include a guard band (for example, a VRB that is composed only of RBs in the DL subband) are defined.
  • a guard band for example, a VRB that is composed only of RBs in the DL subband
  • Figure 8 shows an example of a VRB consisting of a UL subband and a DL subband that does not include a guard band.
  • indices are assigned to the RBs (e.g., 18 RBs) that make up the DL subbands (e.g., DL subbands #0 and #1). In other words, in FIG. 8, VRB indices are not assigned to the RBs that make up the UL subbands and guard bands.
  • the VRBs shown in Figure 8 include RBs in the DL subband, but do not include RBs in the UL subband or guard band, so when mapping from VRBs to PRBs, the DL RBs (VRB) are mapped to the DL PRBs.
  • VRBs #0 to #8 are mapped to PRBs #0 to #8 in DL subband #0
  • VRBs #9 to #17 are mapped to PRBs #21 to #29 in DL subband #1.
  • the guard band size is not adjusted.
  • the guard band is expanded by not allocating resources to the DL subband.
  • resources are not allocated to PRBs (e.g., PRB#8 and PRB#21) adjacent to the guard band in the DL subband.
  • PRBs e.g., PRB#8 and PRB#21
  • the base station 100 allocates resources while avoiding VRB#8 and VRB#9 corresponding to PRB#8 and PRB#21.
  • RA type 1 the base station 100 allocates resources to consecutive RBs, making it difficult to allocate resources while avoiding VRB#8 and VRB#9.
  • the order in which the VRB is mapped to the PRB is changed.
  • the base station 100 makes the order in which the multiple DL subbands in the VRB are mapped different from the order in which the multiple DL subbands in the PRB are mapped.
  • the order in which the subbands are arranged on the VRB and the order in which the subbands are arranged on the PRB may be swapped.
  • some VRBs that are contiguous with the first VRB (VRB#0) and belong to the same subband as the first VRB may be mapped to a PRB (e.g., an adjacent PRB) that is contiguous with the last RB of the guard band in the PRB (e.g., the RB on the boundary with the DL subband).
  • some VRBs that are contiguous with the last VRB and belong to the same subband as the last VRB may be mapped to a PRB (e.g., an adjacent PRB) that is contiguous with the last RB of the guard band in the PRB (e.g., the RB on the boundary with the DL subband).
  • Figure 9 shows an example of a VRB that includes DL subbands and has a permuted mapping order.
  • the VRB is mapped to RBs in the order of ⁇ DL subband #1, DL subband #0 ⁇ in the PRB. Therefore, the order in which the subbands are arranged on the VRB ⁇ DL subband #1, DL subband #0 ⁇ is different from the order in which the subbands are arranged on the PRB ⁇ DL subband #0, DL subband #1 ⁇ .
  • RBs located at the ends of a VRB are mapped to PRBs (e.g., PRB#21 and PRB#8) that are adjacent to the guard band in the PRB.
  • PRB#0 which is the start position of the VRB
  • PRB#17 which is the end position of the VRB
  • PRB#21 and PRB#8 which are positions adjacent to the guard band in the PRB, respectively.
  • PRB#8 and PRB#21 are PRBs that are close to the UL subband among the PRBs that make up the DL subband, and therefore tend to be more affected by CLI than the other PRBs that make up the DL subband.
  • the CLI from the UL subband tends to be larger in the RBs located at the edge of the VRB compared to the RBs located in the center of the VRB. This characteristic is effective when using the RBs of the DL subband as guard bands based on CLI when performing continuous resource allocation such as RA type 1.
  • slot#0 and VRB#1 to VRB#22 are assigned as PDSCH resources, and VRB#0 and VRB#17 are not assigned as PDSCH resources.
  • PRB#0 to PRB#7 and PRB#21 to PRB#29 are assigned as PDSCH resources.
  • PRB#8 and PRB#21 corresponding to VRB#0 and VRB#17, respectively are not used by other terminals, these PRBs can be used as substantial guard bands. Therefore, in the example of FIG. 9, in slot#0, a guard band of 4 RBs can be used between DL subband#0 and UL subband, and between DL subband#1 and UL subband.
  • mapping order By changing the mapping order in this way, it is possible to achieve both non-contiguous resource allocation to DL subbands and adjustment of the guard band size.
  • the VRB includes a DL subband and does not include a guard band, but this is not limited thereto, and for example, the VRB may include a DL subband and a guard band.
  • the VRB includes a DL subband and a guard band, but does not include a UL subband.
  • some VRBs that are contiguous with the first VRB (VRB#0) and belong to the same guard band as the first VRB and the DL subband that is contiguous with the guard band may be mapped to a PRB that is contiguous with the last RB of the UL subband in the PRB (e.g., an adjacent PRB) (e.g., an RB on the boundary with the guard band).
  • some VRBs that are contiguous with the last VRB and belong to the same guard band as the last VRB and the DL subband that is contiguous with the guard band may be mapped to a PRB that is contiguous with the last RB of the UL subband in the PRB (e.g., an adjacent PRB) (e.g., an RB on the boundary with the guard band).
  • the guard band can be reduced, for example by allocating DL resources to the RBs of the guard band as in guard band size adjustment method 2.
  • Figure 10 shows an example of a VRB that includes DL subbands and guard bands and has a swapped mapping order.
  • the VRB maps RBs in the order of ⁇ guard band #1, DL subband #1, DL subband #0, guard band #0 ⁇ in the PRB. Therefore, the order in which the DL subbands and guard bands are arranged on the VRB ⁇ guard band #1, DL subband #1, DL subband #0, guard band #0 ⁇ is different from the order in which the DL subbands and guard bands are arranged on the PRB ⁇ DL subband #0, guard band #0, guard band #1, DL subband #1 ⁇ .
  • RBs located at the ends of a VRB are mapped to PRBs (e.g., PRB#18 and PRB#11) that are adjacent to the UL subband in the PRB.
  • PRB#0 which is the start position of the VRB
  • VRB#23 which is the end position of the VRB
  • PRB#18 and PRB#11 are mapped to PRB#18 and PRB#11, respectively, which are positions adjacent to the UL subband in the PRB.
  • PRB#11 and PRB#18 are adjacent to the UL subband, and therefore are more likely to be affected by CLI than other PRBs that make up the DL subband and guard band.
  • the CLI from the UL subband has the characteristic that it is more likely to be large in RBs located at the edge of the VRB than in RBs located in the center of the VRB. This characteristic is useful when allocating continuous resources, such as with RA type 1, and allocating and using resources (e.g., DL resources) to RBs in the guard band based on CLI.
  • slot#0 and VRB#2 to VRB#21 are assigned as PDSCH resources, and VRB#0, VRB#1, VRB#22, and VRB#23 are not assigned as PDSCH resources.
  • PRB#0 to PRB#9 and PRB#20 to PRB#29 are assigned as PDSCH resources.
  • PDSCH resources are assigned to PRB#9 and PRB#20 within the guard band, so the guard band can be considered to be reduced. Therefore, in the example of FIG. 10, in slot#0, 2RBs can be used as guard bands between DL subband#0 and UL subband, and between DL subband#1 and UL subband.
  • mapping order makes it possible to both allocate non-contiguous resources to DL subbands and adjust the guard band size.
  • a VRB may include DL subbands, UL subbands, and guard bands (i.e., all subbands).
  • a VRB includes a DL subband, a guard band, and a UL subband.
  • the UL subband may be located in the first RB of the VRB, or in the last RB.
  • Figure 11 shows an example of a VRB that includes a DL subband, a UL subband, and a guard band, with the mapping order swapped.
  • the VRB is mapped to RBs in the order of ⁇ guard band #1, DL subband #1, DL subband #0, guard band #0, UL subband ⁇ in the PRB. Therefore, the order in which the DL subbands, UL subbands, and guard bands are arranged on the VRB ⁇ guard band #1, DL subband #1, DL subband #0, guard band #0, UL subband ⁇ is different from the order in which the DL subbands, UL subbands, and guard bands are arranged on the PRB ⁇ DL subband #0, guard band #0, UL subband, guard band #1, DL subband #1 ⁇ .
  • VRB#0 which is the start position of the VRB
  • PRB#18 which is the position adjacent to one end of the UL subband in the PRB
  • VRB#29 which is the end position of the VRB
  • PRB#17 which is the aforementioned end of the UL subband in the PRB.
  • the guard band size can be adjusted while realizing discontinuous allocation to DL subbands, just as in the case where a VRB includes DL subbands and guard bands.
  • resources e.g., PDSCH resources
  • PDSCH resources can also be allocated to the RBs of the UL subband when DL transmission and reception are possible on the UL subband.
  • the existing notification method can be reused as RA type 1, so the overhead of downstream control information does not increase.
  • Method 2 when RA type 1 is applied, a case will be described in which the rate matching function is reused as one method for excluding RBs of the UL subband and guard band as PRBs to which resources are allocated.
  • Rate matching is a function that does not assign PDSCH to some resources, for example to avoid interference with other base stations.
  • a rate match pattern (RateMatchPattern) is set in signaling information from base station 100 to terminal 200, and the resources set in the rate match pattern (for example, resource elements (RE) specified by RB numbers and symbol numbers) can be set so as not to be used for transmitting and receiving PDSCH.
  • RE resource elements
  • Rate matching may also be applied to resources other than those specified by the rate match pattern, for example, to RBs on which SSBs (Synchronization Signal (SS)/Physical Broadcast Channel (PBCH) blocks) are transmitted.
  • SSBs Synchronization Signal (SS)/Physical Broadcast Channel (PBCH) blocks
  • this rate matching function is utilized to treat (or explicitly set) the RBs of the UL subband or guard band as resources not used for transmitting and receiving PDSCH.
  • the subband configuration is ⁇ DUD ⁇ and all RBs including the UL subband and guard band are set by RA Type 1
  • the RBs of the DL subband are used for transmitting and receiving PDSCH, and the RBs of the UL subband and guard band are not used for transmitting and receiving PDSCH. Therefore, using RA type 1, it becomes possible to allocate non-contiguous resources to the DL subband.
  • the guard band size adjustment method 2 (a method of allocating DL resources or UL resources within the guard band) is not applied. Therefore, for example, the following rules may be used to determine whether or not to apply rate matching.
  • rule 1 when DL subbands are arranged non-contiguous, the base station 100 determines whether or not to apply rate matching based on the start or end position of resource allocation in the PRB.
  • the base station 100 determines to apply rate matching when the start and end positions of the PDSCH resource allocation (e.g., RA type 1) are included in each of multiple DL subbands that are arranged non-contiguously (e.g., span multiple DL subbands).
  • the start and end positions of the PDSCH resource allocation e.g., RA type 1
  • the start and end positions of the PDSCH resource allocation e.g., RA type 1
  • Case 1 in Figure 12 shows an example of applying Rule 1.
  • the example in Figure 12 shows an example of frequency resource allocation for a subband configuration of ⁇ DUD ⁇ .
  • the resource allocation notification by DCI shown in Figure 12(a) indicates the allocation of PDSCH resources to the entire band spanning two DL subbands.
  • the start position of the resource allocation by DCI shown in Figure 12(a) is included in DL subband #0, and the end position is included in DL subband #1.
  • Figure 12(b) shows an example of an actual PDSCH resource allocation.
  • rate matching is applied, so the actual PDSCH resource allocation does not include the UL subband and guard band. Therefore, the actual PDSCH resource allocation is the PDSCH resource allocation shown in Figure 12(a) minus the resources corresponding to the UL subband and guard band.
  • PDSCH resources can be allocated simultaneously to non-contiguous DL subbands using RA type 1. This allows for more efficient data transmission and reception by allocating more resources when the data size is large.
  • rule 2 when DL subbands are arranged non-contiguous, the base station 100 determines whether or not to apply rate matching based on the start or end position of resource allocation in the PRB.
  • the base station 100 determines not to apply rate matching when the start or end position of the PDSCH resource allocation (e.g., RA type 1) is included in a band different from the DL subband (e.g., the guard band or UL subband).
  • the start or end position of the PDSCH resource allocation e.g., RA type 1
  • the guard band or UL subband e.g., the guard band or UL subband
  • Case 2 in Figure 12 shows an example of applying rule 2.
  • the resource allocation notification by DCI shown in Figure 12(c) indicates that the PDSCH resources start from DL subband #0 and end within guard band #0.
  • FIG. 12 shows an example in which rule 1 is applied.
  • rate matching is applied, so resources within the guard band are not used for the PDSCH. In this case, the guard band size cannot be adjusted.
  • FIG. 12 shows the case where rule 2 is applied.
  • rate matching is not applied, and resources are allocated within the guard band. Therefore, for example, when the CLI is small, the resource utilization efficiency can be improved by allocating the guard band resources to the PDSCH.
  • rule 3 when the frequency domain resource allocation (FDRA) field or the RIV is set to a specific value in the downlink control information (DCI), a semi-statically configured or predefined resource allocation is applied.
  • FDRA frequency domain resource allocation
  • DCI downlink control information
  • how many patterns of RIV values exist depends on the combination of RB start and L RB in RA type 1. Therefore, there may be cases where the maximum combination of RB start and L RB does not exist for the number of bits allocated to RIV. For example, when the number of RBs in BWP is 20, 8 bits are used for RIV, so that 256 patterns can be notified as resource allocation. On the other hand, out of the 256 patterns, there are 210 patterns that can be associated with RIV. Therefore, out of the 256 patterns that can be notified, 46 values of RIV are unused.
  • rule 3 for example, a value represented by multiple bits used to notify an RIV in RA type 1 that is different from the value associated with the combination of RB start and L RB notified by the RIV is associated with an allocation pattern in multiple subbands.
  • FIG. 13 shows an example of resource allocation according to a specific pattern using the RIV value.
  • FIG. 14 shows an example of application of resource allocation according to a specific pattern using the RIV value shown in FIG. 13.
  • "All "1”” is associated with allocation of PDSCH resources to all RBs including the UL subband, as shown in Fig. 14. For example, when rule 1 is applied, PDSCH resources cannot be allocated to the entire band, but in the case of "All "1", PDSCH resources can be allocated to the entire band.
  • "All "1"-1” corresponds to allocation of PDSCH resources to all RBs in the DL subband (two DL subbands #0 and #1 in Fig. 14) and one RB in each guard band (guard bands #0 and #1 in Fig. 14), as shown in Fig. 14.
  • the above description describes an operation in which no resources are allocated to the UL subband and guard band due to rate matching, but the method may be applied to methods other than rate matching.
  • the above method can be applied even to an operation in which the rate matching function is not used and PDSCH resources are not allocated to the UL subband and guard band.
  • the base station 100 may switch between and apply at least two of rules 1 to 3 depending on certain conditions.
  • method 2 can achieve non-contiguous resource allocation and guard band size adjustment even in contiguous resource allocation such as RA type 1, thereby improving resource utilization efficiency.
  • existing instructions for RA type 1 can be reused, so DCI overhead does not increase.
  • method 2 does not require additional VRB to PRB mapping, reducing complexity compared to method 1.
  • the base station 100 and the terminal 200 allocate resources differently depending on whether or not the DL subbands are arranged discontinuously in the PRB.
  • the base station 100 and the terminal 200 may use a different VRB-PRB mapping when the DL subbands are arranged discontinuously compared to when the DL subbands are not arranged discontinuously.
  • the base station 100 and the terminal 200 may determine whether or not to apply rate matching depending on the PDSCH resource allocation when the DL subbands are arranged discontinuously.
  • guard band size such as by expanding or reducing the guard band. This makes it possible, for example, to allocate non-consecutive resources to DL subbands and to appropriately adjust the guard band size according to the CLI, thereby improving resource utilization efficiency.
  • resource allocation in wireless communication can be appropriately controlled.
  • method 1 and method 2 may be applied to uplink data (for example, PUSCH).
  • RA type 1 and VRB-to-PRB mapping can also be used in PUSCH. Therefore, when multiple UL subbands are supported, resource allocation may be difficult as in PDSCH.
  • the method may be applied to PUSCH by replacing PDSCH with PUSCH, exchanging DL subband and UL subband, and exchanging reception and transmission.
  • values such as the number of subbands, the number of DL subbands, the number of UL subbands, the number of guard bands, the number of RBs (the number of VRBs or the number of PRBs), the number of slots, the RIV value, and the number of bits for notifying the RIV are merely examples and are not limited to these.
  • the subband configuration e.g., ⁇ DUD ⁇
  • the number of subbands and the arrangement order of the DL subbands and the UL subbands are not limited to these.
  • (supplement) Information indicating whether terminal 200 supports the functions, operations or processes described in the above-mentioned embodiments may be transmitted (or notified) from terminal 200 to base station 100, for example, as capability information or capability parameters of terminal 200.
  • the capability information may include information elements (IEs) that individually indicate whether the terminal 200 supports at least one of the functions, operations, or processes shown in the above-described embodiments.
  • the capability information may include information elements that indicate whether the terminal 200 supports a combination of any two or more of the functions, operations, or processes shown in the above-described embodiments.
  • the base station 100 may, for example, determine (or decide or assume) the functions, operations, or processing that are supported (or not supported) by the terminal 200 that transmitted the capability information.
  • the base station 100 may perform operations, processing, or control according to the results of the determination based on the capability information.
  • the base station 100 may control resource allocation to the terminal 200 based on the capability information received from the terminal 200.
  • the terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiment may be interpreted as meaning that such some of the functions, operations, or processes are restricted in the terminal 200. For example, information or requests regarding such restrictions may be notified to the base station 100.
  • the information regarding the capabilities or limitations of the terminal 200 may be defined in a standard, for example, or may be implicitly notified to the base station 100 in association with information already known at the base station 100 or information transmitted to the base station 100.
  • a downlink control signal (or downlink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a Physical Downlink Control Channel (PDCCH) in a physical layer, or a signal (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) in a higher layer.
  • the signal (or information) is not limited to being notified by a downlink control signal, and may be predefined in a specification (or standard), or may be preconfigured in a base station and a terminal.
  • the uplink control signal (or uplink control information) related to one embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a PUCCH in the physical layer, or a signal (or information) transmitted in a MAC CE or RRC in a higher layer.
  • the signal (or information) is not limited to being notified by an uplink control signal, but may be predefined in a specification (or standard), or may be preconfigured in a base station and a terminal.
  • the uplink control signal may be replaced with, for example, uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.
  • UCI uplink control information
  • SCI 1st stage sidelink control information
  • 2nd stage SCI 2nd stage SCI.
  • the base station may be a Transmission Reception Point (TRP), a cluster head, an access point, a Remote Radio Head (RRH), an eNodeB (eNB), a gNodeB (gNB), a Base Station (BS), a Base Transceiver Station (BTS), a parent device, a gateway, or the like.
  • TRP Transmission Reception Point
  • RRH Remote Radio Head
  • eNB eNodeB
  • gNB gNodeB
  • BS Base Station
  • BTS Base Transceiver Station
  • a terminal may play the role of a base station.
  • a relay device that relays communication between an upper node and a terminal may be used.
  • a roadside unit may be used.
  • An embodiment of the present disclosure may be applied to, for example, any of an uplink, a downlink, and a sidelink.
  • an embodiment of the present disclosure may be applied to a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH) in the uplink, a Physical Downlink Shared Channel (PDSCH), a PDCCH, a Physical Broadcast Channel (PBCH) in the downlink, or a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Control Channel (PSCCH), or a Physical Sidelink Broadcast Channel (PSBCH) in the sidelink.
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PRACH Physical Random Access Channel
  • PDSCH Physical Downlink Shared Channel
  • PDCCH Physical Broadcast Channel
  • PBCH Physical Broadcast Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSCCH Physical Sidelink Control Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel, respectively.
  • PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel.
  • PBCH and PSBCH are examples of a broadcast channel, and PRACH is an example of a random access channel.
  • An embodiment of the present disclosure may be applied to, for example, any of a data channel and a control channel.
  • the channel in an embodiment of the present disclosure may be replaced with any of the data channels PDSCH, PUSCH, and PSSCH, or the control channels PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.
  • the reference signal is, for example, a signal known by both the base station and the mobile station, and may be called a Reference Signal (RS) or a pilot signal.
  • the reference signal may be any of a Demodulation Reference Signal (DMRS), a Channel State Information - Reference Signal (CSI-RS), a Tracking Reference Signal (TRS), a Phase Tracking Reference Signal (PTRS), a Cell-specific Reference Signal (CRS), or a Sounding Reference Signal (SRS).
  • DMRS Demodulation Reference Signal
  • CSI-RS Channel State Information - Reference Signal
  • TRS Tracking Reference Signal
  • PTRS Phase Tracking Reference Signal
  • CRS Cell-specific Reference Signal
  • SRS Sounding Reference Signal
  • the unit of time resource is not limited to one or a combination of slots and symbols, but may be, for example, a time resource unit such as a frame, a superframe, a subframe, a slot, a time slot, a subslot, a minislot, a symbol, an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier-Frequency Division Multiplexing Access (SC-FDMA) symbol, or another time resource unit.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier-Frequency Division Multiplexing Access
  • the number of symbols included in one slot is not limited to the number of symbols exemplified in the above embodiment, and may be another number of symbols.
  • An embodiment of the present disclosure may be applied to either a licensed band or an unlicensed band.
  • An embodiment of the present disclosure may be applied to any of communication between a base station and a terminal (Uu link communication), communication between terminals (Sidelink communication), and Vehicle to Everything (V2X) communication.
  • the channel in an embodiment of the present disclosure may be replaced with any of PSCCH, PSSCH, Physical Sidelink Feedback Channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.
  • an embodiment of the present disclosure may be applied to either a terrestrial network or a non-terrestrial network (NTN: Non-Terrestrial Network) using a satellite or a High Altitude Pseudo Satellite (HAPS: High Altitude Pseudo Satellite).
  • NTN Non-Terrestrial Network
  • HAPS High Altitude Pseudo Satellite
  • an embodiment of the present disclosure may be applied to a terrestrial network in which the transmission delay is large compared to the symbol length or slot length, such as a network with a large cell size or an ultra-wideband transmission network.
  • an antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas.
  • an antenna port does not necessarily refer to one physical antenna, but may refer to an array antenna consisting of multiple antennas.
  • an antenna port may be defined as the minimum unit by which a terminal station can transmit a reference signal, without specifying how many physical antennas the antenna port is composed of.
  • an antenna port may be defined as the minimum unit by which a weighting of a precoding vector is multiplied.
  • 5G fifth generation of mobile phone technology
  • NR radio access technology
  • the system architecture as a whole assumes an NG-RAN (Next Generation - Radio Access Network) comprising gNBs.
  • the gNBs provide the UE-side termination of the NG radio access user plane (SDAP/PDCP/RLC/MAC/PHY) and control plane (RRC) protocols.
  • the gNBs are connected to each other via an Xn interface.
  • the gNBs are also connected to the Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to the Access and Mobility Management Function (AMF) (e.g., a specific core entity performing AMF) via an NG-C interface, and to the User Plane Function (UPF) (e.g., a specific core entity performing UPF) via an NG-U interface.
  • the NG-RAN architecture is shown in Figure 15 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).
  • the NR user plane protocol stack includes the PDCP (Packet Data Convergence Protocol (see, for example, TS 38.300, section 6.4)) sublayer, the RLC (Radio Link Control (see, for example, TS 38.300, section 6.3)) sublayer, and the MAC (Medium Access Control (see, for example, TS 38.300, section 6.2)) sublayer, which are terminated on the network side at the gNB.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • SDAP Service Data Adaptation Protocol
  • a control plane protocol stack is also defined for NR (see, for example, TS 38.300, section 4.4.2).
  • An overview of Layer 2 functions is given in clause 6 of TS 38.300.
  • the functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are listed in clauses 6.4, 6.3, and 6.2 of TS 38.300, respectively.
  • the functions of the RRC layer are listed in clause 7 of TS 38.300.
  • the Medium-Access-Control layer handles multiplexing of logical channels and scheduling and scheduling-related functions, including handling various numerologies.
  • the physical layer is responsible for coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources.
  • the physical layer also handles the mapping of transport channels to physical channels.
  • the physical layer provides services to the MAC layer in the form of transport channels.
  • a physical channel corresponds to a set of time-frequency resources used for the transmission of a particular transport channel, and each transport channel is mapped to a corresponding physical channel.
  • the physical channels include the PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel) as uplink physical channels, and the PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel) as downlink physical channels.
  • PRACH Physical Random Access Channel
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PDSCH Physical Downlink Shared Channel
  • PDCCH Physical Downlink Control Channel
  • PBCH Physical Broadcast Channel
  • NR use cases/deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communication (mMTC), which have diverse requirements in terms of data rate, latency, and coverage.
  • eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates that are about three times higher than the data rates offered by IMT-Advanced.
  • URLLC stricter requirements are imposed on ultra-low latency (0.5 ms for user plane latency in UL and DL, respectively) and high reliability (1-10 ⁇ 5 within 1 ms).
  • mMTC may require preferably high connection density (1,000,000 devices/km 2 in urban environments), wide coverage in adverse environments, and extremely long battery life (15 years) for low-cost devices.
  • OFDM numerology e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval
  • OFDM numerology e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval
  • low latency services may preferably require a shorter symbol length (and therefore a larger subcarrier spacing) and/or fewer symbols per scheduling interval (also called TTI) than mMTC services.
  • deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with short delay spreads.
  • Subcarrier spacing may be optimized accordingly to maintain similar CP overhead.
  • NR may support one or more subcarrier spacing values. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz... are currently considered.
  • a resource grid of subcarriers and OFDM symbols is defined for the uplink and downlink, respectively.
  • Each element of the resource grid is called a resource element and is identified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).
  • Figure 16 shows the functional separation between NG-RAN and 5GC.
  • the logical nodes of NG-RAN are gNB or ng-eNB.
  • 5GC has logical nodes AMF, UPF, and SMF.
  • gNBs and ng-eNBs host the following main functions: - Radio Resource Management functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink; - IP header compression, encryption and integrity protection of the data; - Selection of an AMF at UE attach time when routing to an AMF cannot be determined from information provided by the UE; - Routing of user plane data towards the UPF; - Routing of control plane information towards the AMF; - Setting up and tearing down connections; - scheduling and transmission of paging messages; Scheduling and transmission of system broadcast information (AMF or Operation, Admission, Maintenance (OAM) origin); - configuration of measurements and measurement reporting for mobility and scheduling; - Transport level packet marking in the uplink; - Session management; - Support for network slicing; - Management of QoS flows and mapping to data radio bearers; - Support for UEs in RRC_INACTIVE state; - NAS
  • the Access and Mobility Management Function hosts the following main functions: – the ability to terminate Non-Access Stratum (NAS) signalling; - NAS signalling security; - Access Stratum (AS) security control; - Core Network (CN) inter-node signaling for mobility between 3GPP access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Managing the registration area; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization, including checking roaming privileges; - Mobility management control (subscription and policy); - Support for network slicing; – Selection of Session Management Function (SMF).
  • NAS Non-Access Stratum
  • AS Access Stratum
  • CN Core Network
  • the User Plane Function hosts the following main functions: - anchor point for intra/inter-RAT mobility (if applicable); - external PDU (Protocol Data Unit) Session Points for interconnection with data networks; - Packet routing and forwarding; - Packet inspection and policy rule enforcement for the user plane part; - Traffic usage reporting; - an uplink classifier to support routing of traffic flows to the data network; - Branching Point to support multi-homed PDU sessions; QoS processing for the user plane (e.g. packet filtering, gating, UL/DL rate enforcement); - Uplink traffic validation (mapping of SDF to QoS flows); - Downlink packet buffering and downlink data notification triggering.
  • PDU Protocol Data Unit Session Points for interconnection with data networks
  • Packet routing and forwarding Packet inspection and policy rule enforcement for the user plane part
  • Traffic usage reporting - an uplink classifier to support routing of traffic flows to the data network
  • - Branching Point to support multi-homed PDU
  • Session Management Function hosts the following main functions: - Session management; - Allocation and management of IP addresses for UEs; - Selection and control of UPF; - configuration of traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination; - Control policy enforcement and QoS; - Notification of downlink data.
  • Figure 17 shows some of the interactions between the UE, gNB, and AMF (5GC entities) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS portion (see TS 38.300 v15.6.0).
  • RRC is a higher layer signaling (protocol) used for UE and gNB configuration.
  • the AMF prepares UE context data (which includes, for example, PDU session context, security keys, UE Radio Capability, UE Security Capabilities, etc.) and sends it to the gNB with an INITIAL CONTEXT SETUP REQUEST.
  • the gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE and the UE responding with a SecurityModeComplete message to the gNB.
  • the gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the RRCReconfiguration steps are omitted, since SRB2 and DRB are not set up. Finally, the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.
  • SRB2 Signaling Radio Bearer 2
  • DRB Data Radio Bearer
  • a 5th Generation Core (5GC) entity e.g., AMF, SMF, etc.
  • a control circuit that, during operation, establishes a Next Generation (NG) connection with a gNodeB
  • a transmitter that, during operation, transmits an initial context setup message to the gNodeB via the NG connection such that a signaling radio bearer between the gNodeB and a user equipment (UE) is set up.
  • the gNodeB transmits Radio Resource Control (RRC) signaling including a resource allocation configuration information element (IE) to the UE via the signaling radio bearer.
  • RRC Radio Resource Control
  • IE resource allocation configuration information element
  • Figure 18 shows some of the use cases for 5G NR.
  • the 3rd generation partnership project new radio (3GPP NR) considers three use cases that were envisioned by IMT-2020 to support a wide variety of services and applications.
  • the first phase of specifications for enhanced mobile-broadband (eMBB) has been completed.
  • Current and future work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to expanding support for eMBB.
  • Figure 18 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see, for example, ITU-R M.2083 Figure 2).
  • the URLLC use cases have stringent requirements for performance such as throughput, latency, and availability. It is envisioned as one of the enabling technologies for future applications such as wireless control of industrial or manufacturing processes, remote medical surgery, automation of power transmission and distribution in smart grids, and road safety.
  • URLLC's ultra-high reliability is supported by identifying technologies that meet the requirements set by TR 38.913.
  • key requirements include a target user plane latency of 0.5 ms for UL (uplink) and 0.5 ms for DL (downlink).
  • the overall URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a packet size of 32 bytes with a user plane latency of 1 ms.
  • BLER block error rate
  • NR URLLC can be improved in many possible ways.
  • Current room for reliability improvement includes defining a separate CQI table for URLLC, more compact DCI formats, PDCCH repetition, etc.
  • this room can be expanded to achieve ultra-high reliability as NR becomes more stable and more developed (with respect to the key requirements of NR URLLC).
  • Specific use cases for NR URLLC in Release 15 include Augmented Reality/Virtual Reality (AR/VR), e-health, e-safety, and mission-critical applications.
  • AR/VR Augmented Reality/Virtual Reality
  • e-health e-safety
  • mission-critical applications mission-critical applications.
  • the technology enhancements targeted by NR URLLC aim to improve latency and reliability.
  • Technology enhancements for improving latency include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition in data channel, and pre-emption in downlink.
  • Pre-emption means that a transmission for which resources have already been allocated is stopped and the already allocated resources are used for other transmissions with lower latency/higher priority requirements that are requested later. Thus, a transmission that was already allowed is preempted by a later transmission. Pre-emption is applicable regardless of the specific service type. For example, a transmission of service type A (URLLC) may be preempted by a transmission of service type B (eMBB, etc.).
  • Technology enhancements for improving reliability include a dedicated CQI/MCS table for a target BLER of 1E-5.
  • the mMTC (massive machine type communication) use case is characterized by a very large number of connected devices transmitting relatively small amounts of data that are typically not sensitive to latency.
  • the devices are required to be low cost and have very long battery life. From an NR perspective, utilizing very narrow bandwidth portions is one solution that saves power from the UE's perspective and allows for long battery life.
  • the scope of reliability improvement in NR is expected to be broader.
  • One of the key requirements for all cases, e.g. for URLLC and mMTC, is high or ultra-high reliability.
  • Several mechanisms can improve reliability from a radio perspective and a network perspective.
  • these areas include compact control channel information, data channel/control channel repetition, and diversity in frequency, time, and/or spatial domains. These areas are generally applicable to reliability improvement regardless of the specific communication scenario.
  • NR URLLC For NR URLLC, further use cases with more stringent requirements are envisaged, such as factory automation, transportation and power distribution, with high reliability (up to 10-6 level of reliability), high availability, packet size up to 256 bytes, time synchronization up to a few ⁇ s (depending on the use case, the value can be 1 ⁇ s or a few ⁇ s depending on the frequency range and low latency of the order of 0.5 ms to 1 ms (e.g. 0.5 ms latency on the targeted user plane).
  • high reliability up to 10-6 level of reliability
  • high availability packet size up to 256 bytes
  • time synchronization up to a few ⁇ s (depending on the use case, the value can be 1 ⁇ s or a few ⁇ s depending on the frequency range and low latency of the order of 0.5 ms to 1 ms (e.g. 0.5 ms latency on the targeted user plane).
  • minislot refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot comprises 14 symbols).
  • TTI Transmission Time Interval
  • QoS Quality of Service
  • the 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (GBR QoS flows) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows).
  • GRR QoS flows Guarantee flow bit rate
  • non-GBR QoS flows QoS flows that do not require a guaranteed flow bit rate
  • QoS flows are the finest granularity of QoS partitioning in a PDU session.
  • QoS flows are identified within a PDU session by a QoS Flow ID (QFI) carried in the encapsulation header over the NG-U interface.
  • QFI QoS Flow ID
  • 5GC For each UE, 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) for the PDU session, e.g. as shown above with reference to Figure 17. Additional DRBs for the QoS flows of that PDU session can be configured later (when it is up to the NG-RAN).
  • DRB Data Radio Bearer
  • the NG-RAN maps packets belonging to different PDU sessions to different DRBs.
  • the NAS level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, whereas the AS level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.
  • FIG 19 shows the non-roaming reference architecture for 5G NR (see TS 23.501 v16.1.0, section 4.23).
  • An Application Function e.g. an external application server hosting 5G services as illustrated in Figure 18
  • NEF Network Exposure Function
  • PCF Policy Control Function
  • Figure 19 further shows further functional units of the 5G architecture, namely Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN, e.g. operator provided services, Internet access, or third party provided services). All or part of the core network functions and application services may be deployed and run in a cloud computing environment.
  • NSF Network Slice Selection Function
  • NRF Network Repository Function
  • UDM Unified Data Management
  • AUSF Authentication Server Function
  • AMF Access and Mobility Management Function
  • SMSF Session Management Function
  • DN Data Network
  • All or part of the core network functions and application services may be deployed and run in a cloud computing environment.
  • an application server e.g., an AF in a 5G architecture
  • a transmitter that, in operation, transmits a request including QoS requirements for at least one of a URLLC service, an eMMB service, and an mMTC service to at least one of 5GC functions (e.g., a NEF, an AMF, an SMF, a PCF, an UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements; and a control circuit that, in operation, performs a service using the established PDU session.
  • 5GC functions e.g., a NEF, an AMF, an SMF, a PCF, an UPF, etc.
  • Each functional block used in the description of the above embodiments may be realized, in part or in whole, as an LSI, which is an integrated circuit, and each process described in the above embodiments may be controlled, in part or in whole, by one LSI or a combination of LSIs.
  • the LSI may be composed of individual chips, or may be composed of one chip that contains some or all of the functional blocks.
  • the LSI may have data input and output. Depending on the degree of integration, the LSI may be called an IC, system LSI, super LSI, or ultra LSI.
  • the integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells inside the LSI, may be used.
  • FPGA field programmable gate array
  • the present disclosure may be realized as digital processing or analog processing.
  • the present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) having communications capabilities.
  • the communications apparatus may include a radio transceiver and processing/control circuitry.
  • the radio transceiver may include a receiver and a transmitter, or both as functions.
  • the radio transceiver (transmitter and receiver) may include an RF (Radio Frequency) module and one or more antennas.
  • the RF module may include an amplifier, an RF modulator/demodulator, or the like.
  • Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones, etc.), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks, etc.), cameras (e.g., digital still/video cameras), digital players (e.g., digital audio/video players, etc.), wearable devices (e.g., wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth/telemedicine devices, communication-enabled vehicles or mobile transport (e.g., cars, planes, ships, etc.), and combinations of the above-mentioned devices.
  • telephones e.g., cell phones, smartphones, etc.
  • tablets personal computers (PCs) (e.g., laptops, desktops, notebooks, etc.)
  • cameras e.g., digital still/video cameras
  • digital players e.g., digital audio/video players, etc.
  • wearable devices e.g., wearable cameras, smartwatches, tracking
  • Communication devices are not limited to portable or mobile devices, but also include any type of equipment, device, or system that is non-portable or fixed, such as smart home devices (home appliances, lighting equipment, smart meters or measuring devices, control panels, etc.), vending machines, and any other "things” that may exist on an IoT (Internet of Things) network.
  • smart home devices home appliances, lighting equipment, smart meters or measuring devices, control panels, etc.
  • vending machines and any other “things” that may exist on an IoT (Internet of Things) network.
  • IoT Internet of Things
  • Communications include data communication via cellular systems, wireless LAN systems, communication satellite systems, etc., as well as data communication via combinations of these.
  • the communication apparatus also includes devices such as controllers and sensors that are connected or coupled to a communication device that performs the communication functions described in this disclosure.
  • a communication device that performs the communication functions described in this disclosure.
  • controllers and sensors that generate control signals and data signals used by the communication device to perform the communication functions of the communication apparatus.
  • communication equipment includes infrastructure facilities, such as base stations, access points, and any other equipment, devices, or systems that communicate with or control the various non-limiting devices listed above.
  • a base station includes a control circuit that varies resource allocation depending on whether a first band corresponding to a first transmission direction is arranged discontinuously in a physical resource block in a method in which a transmission direction is set for each of a plurality of bands obtained by dividing a frequency band, and a transmission circuit that transmits a signal according to the resource allocation.
  • the transmission circuit transmits control information regarding the resource allocation, including a starting position of a virtual resource block including at least the first band and the number of the virtual resource blocks that are consecutive from the starting position, and when the first bands are arranged non-consecutively, the control circuit makes the order in which the first bands are mapped in the virtual resource block different from the order in which the first bands are mapped in the physical resource block.
  • the virtual resource block includes the first band, does not include a second band corresponding to a second transmission direction different from the first transmission direction, and does not include a guard band between the first band and the second band, and the start position and end position of the virtual resource block are mapped to positions adjacent to the guard band in the physical resource block.
  • the virtual resource block includes the first band and a guard band between the first band and a second band corresponding to a second transmission direction different from the first transmission direction, but does not include the second band, and the start position and end position of the virtual resource block are mapped to positions adjacent to the second band in the physical resource block.
  • the virtual resource block includes the first band, a second band corresponding to a second transmission direction different from the first transmission direction, and a guard band between the first band and the second band, and the start position is mapped to a position adjacent to one end of the second band in the physical resource block, and the end position of the virtual resource block is mapped to the one end of the second band in the physical resource block.
  • the control circuit determines whether or not to apply rate matching based on the start or end position of resource allocation in the physical resource block.
  • control circuit determines to apply the rate match when the start position and the end position are included in each of the first bands.
  • control circuit determines not to apply the rate match if the start position or the end position is included in a band different from the first band.
  • the transmission circuit transmits control information regarding the resource allocation, including a starting position of a virtual resource block including at least the first band and the number of the virtual resource blocks consecutive from the starting position, and among values represented by a plurality of bits used to notify the control information, a value different from a value associated with a combination of the starting position and the number of the virtual resource blocks is associated with an allocation pattern in the plurality of bands.
  • a terminal includes a control circuit that varies resource allocation depending on whether a first band corresponding to a first transmission direction is arranged discontinuously in a physical resource block in a method in which a transmission direction is set for each of a plurality of bands obtained by dividing a frequency band, and a receiving circuit that receives a signal according to the resource allocation.
  • a base station in a method in which a transmission direction is set for each of a plurality of bands obtained by dividing a frequency band, a base station varies resource allocation depending on whether a first band corresponding to a first transmission direction is arranged discontinuously in a physical resource block, and transmits or receives a signal according to the resource allocation.
  • a terminal in a method in which a transmission direction is set for each of a plurality of bands obtained by dividing a frequency band, a terminal varies resource allocation depending on whether a first band corresponding to a first transmission direction is arranged discontinuously in a physical resource block, and receives a signal according to the resource allocation.
  • An embodiment of the present disclosure is useful in wireless communication systems.
  • Base station 101 201 Receiving section 102, 202 Demapping section 103, 203 Demodulation and decoding section 104 Scheduling section 105 Resource control section 106, 206 Control information storage section 107, 207 Data and control information generation section 108, 208 Coding and modulation section 109, 209 Mapping section 110, 210 Transmitting section 200 Terminal 204 Resource determination section 205 Control section

Landscapes

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

Abstract

L'invention concerne une station de base d'une forme dans laquelle une direction de transmission est définie pour chacune d'une pluralité de bandes obtenues par division d'une bande de fréquences, la station de base comprenant un circuit de commande qui amène une attribution de ressources à varier selon qu'une première bande correspondant à une première direction de transmission est disposée de manière discontinue dans un bloc de ressources physiques, et un circuit de transmission qui transmet un signal conformément à l'attribution de ressources.
PCT/JP2023/037876 2023-02-15 2023-10-19 Station de base, terminal, et procédé de communication Ceased WO2024171520A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2025500648A JPWO2024171520A1 (fr) 2023-02-15 2023-10-19

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2023-021552 2023-02-15
JP2023021552 2023-02-15

Publications (1)

Publication Number Publication Date
WO2024171520A1 true WO2024171520A1 (fr) 2024-08-22

Family

ID=92421173

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/037876 Ceased WO2024171520A1 (fr) 2023-02-15 2023-10-19 Station de base, terminal, et procédé de communication

Country Status (2)

Country Link
JP (1) JPWO2024171520A1 (fr)
WO (1) WO2024171520A1 (fr)

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
MARTIN BEALE, SONY: "Considerations on Subband Full Duplex TDD Operations", 3GPP DRAFT; R1-2211610; TYPE DISCUSSION; FS_NR_DUPLEX_EVO, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052222174 *
MIN ZHU, CATT: "Discussion on subband non-overlapping full duplex", 3GPP DRAFT; R1-2211196; TYPE DISCUSSION; FS_NR_DUPLEX_EVO, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052221761 *
SHARP: "Discussion on subband non-overlapping full duplex", 3GPP DRAFT; R1-2209930, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20221010 - 20221019, 30 September 2022 (2022-09-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052259403 *
TOMOYA NUNOME, PANASONIC: "Discussion on subband non-overlapping full duplex", 3GPP DRAFT; R1-2300918; TYPE DISCUSSION; FS_NR_DUPLEX_EVO, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052248061 *
YOUNGSOO YUK, NOKIA, NOKIA SHANGHAI BELL: "On subband non-overlapping full duplex for NR", 3GPP DRAFT; R1-2212284; TYPE DISCUSSION; FS_NR_DUPLEX_EVO, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052222843 *
YU DING, SPREADTRUM COMMUNICATIONS: "Discussion on subband non-overlapping full duplex", 3GPP DRAFT; R1-2211233; TYPE DISCUSSION; FS_NR_DUPLEX_EVO, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052221798 *

Also Published As

Publication number Publication date
JPWO2024171520A1 (fr) 2024-08-22

Similar Documents

Publication Publication Date Title
JP7670677B2 (ja) 端末、通信方法及び集積回路
JP7733186B2 (ja) 基地局、通信方法及び集積回路
WO2022014272A1 (fr) Terminal, station de base et procédé de communication
JP2025134753A (ja) 基地局、通信方法及び集積回路
WO2023013191A1 (fr) Dispositif et procédé de communication
WO2023188913A1 (fr) Station de base, terminal, et procédé de communication
WO2022208989A1 (fr) Dispositif de communication et procédé de communication
WO2022201652A1 (fr) Terminal, station de base et procédé de communication
WO2024157643A1 (fr) Terminal, station de base et procédé de communication
WO2023188912A1 (fr) Station de base, terminal et procédé de communication
WO2023243614A1 (fr) Terminal, station de base et procédé de communication
WO2023204061A1 (fr) Dispositif et procédé de communication
WO2023181556A1 (fr) Terminal, station de base et procédé de communication
WO2023119756A1 (fr) Dispositif de communication et procédé de communication
WO2023013192A1 (fr) Terminal, station de base et procédé de communication
WO2022239289A1 (fr) Dispositif de communication et procédé de communication
JP7757388B2 (ja) 端末、通信方法及び集積回路
WO2024171520A1 (fr) Station de base, terminal, et procédé de communication
WO2024219190A1 (fr) Terminal, station de base et procédé de communication
WO2024171521A1 (fr) Station de base, terminal et procédé de communication
WO2024024259A1 (fr) Terminal, station de base, et procédé de communication
WO2025033052A1 (fr) Station de base, terminal, et procédé de communication
WO2023203938A1 (fr) Terminal, station de base, procédé de communication, et circuit intégré
WO2025033046A1 (fr) Station de base, terminal et procédé de communication
WO2025069635A1 (fr) Terminal, station de base et procédé de communication

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2025500648

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2025500648

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE