Terminal, base station and communication method
The proposed communication method addresses the overhead issue in carrier aggregation by using virtual CCs and non-contiguous scheduling, enhancing resource allocation efficiency.
Patent Information
- Application Number
- JP2023578321
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-02-04
- Publication Date
- 2026-01-16
- Estimated Expiration
- 2042-02-04
AI Technical Summary
Conventional carrier aggregation functions require scheduling of data resources for each of multiple aggregated component carriers, leading to a large resource allocation overhead.
Implementing a communication method that allocates resources in scheduling units with a granularity different from that of component carriers, utilizing virtual CCs, BWPs, PRBs, or PRB sets, and non-contiguous scheduling to avoid collisions and prioritize resource usage.
Reduces resource allocation overhead by enabling efficient and flexible resource management in carrier aggregation systems.
Smart Images

Figure 0007801371000001 
Figure 0007801371000002 
Figure 0007801371000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to a terminal, a base station, and a communication method in a wireless communication system. [Background technology]
[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1).
[0003] In addition, NR is continuing to be studied for the carrier aggregation (CA) function, which uses wideband to secure data resources, following on from LTE. The carrier aggregation function can secure wideband data resources by aggregating multiple component carriers (CC). [Prior art documents] [Non-patent literature]
[0004] [Non-Patent Document 1] 3GPP TS 38.300 V16.7.0(2021-09) Summary of the Invention [Problem to be solved by the invention]
[0005] Future systems (e.g., NR Release 18 and its successor, 6G) may require more flexible and efficient resource allocation. However, conventional carrier aggregation functions require scheduling of data resources for each of multiple aggregated component carriers, resulting in a large resource allocation overhead.
[0006] The present invention has been made in view of the above points, and has as its object to reduce the overhead of resource allocation. [Means for solving the problem]
[0007] According to the disclosed technology, a communication unit that performs uplink or downlink communication in a frequency band aggregated by carrier aggregation, and a control unit that assumes that scheduling is performed in a unit different from that of a component carrier in the aggregated frequency band, A terminal, wherein the control unit assumes that scheduling is performed for each carrier set that aggregates all or part of frequency resources included in each component carrier among a plurality of component carriers in the aggregated frequency band, and the control unit assumes that scheduling is performed in a plurality of frequency bands of a duplex scheme that includes communications in different directions at the same time. A terminal is provided. [Effects of the Invention]
[0008] The disclosed technology provides a technology that enables reduction of overhead in resource allocation. [Brief explanation of the drawings]
[0009] [Figure 1] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 2] FIG. 1 is a first diagram illustrating an example of a configuration of a virtual CC according to Example 1 of an embodiment of the present invention. [Figure 3] FIG. 10 is a second diagram illustrating an example of the configuration of a virtual CC according to the first embodiment of the present invention. [Figure 4] FIG. 10 is a first diagram illustrating an example of a scenario A of non-contiguous scheduling according to Example 2 of an embodiment of the present invention. [Figure 5] FIG. 10 is a second diagram illustrating an example of scenario A of non-contiguous scheduling according to Example 2 of the embodiment of the present invention. [Figure 6] FIG. 10 is a third diagram illustrating an example of scenario A of non-contiguous scheduling according to Example 2 of the embodiment of the present invention. [Figure 7] FIG. 10 is a fourth diagram illustrating an example of scenario A of non-contiguous scheduling according to Example 2 of the embodiment of the present invention. [Figure 8] FIG. 10 is a first diagram illustrating an example of a scenario B of non-contiguous scheduling according to Example 2 of an embodiment of the present invention. [Figure 9] FIG. 10 is a second diagram illustrating an example of scenario B of non-contiguous scheduling according to Example 2 of the embodiment of the present invention. [Figure 10] FIG. 10 is a third diagram illustrating an example of scenario B of non-contiguous scheduling according to Example 2 of the embodiment of the present invention. [Figure 11] FIG. 10 is a fourth diagram illustrating an example of scenario B of non-contiguous scheduling according to Example 2 of the embodiment of the present invention. [Figure 12] FIG. 2 is a diagram illustrating an example of a functional configuration of a base station according to an embodiment of the present invention. [Figure 13] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal according to an embodiment of the present invention. [Figure 14] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station or a terminal according to an embodiment of the present invention. [Figure 15] 1 is a diagram showing an example of a configuration of a vehicle according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE INVENTION
[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.
[0012] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".
[0013] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).
[0014] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.
[0015] (System Configuration) FIG. 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, a wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.
[0016] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. Furthermore, a TTI (Transmission Time Interval) in the time domain may be a slot, or a TTI may be a subframe.
[0017] The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via the NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as an SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell) and a primary cell (PCell) using Carrier Aggregation (CA). Furthermore, the terminal 20 may perform communication via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).
[0018] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in FIG. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals. The terminal 20 may also be referred to as a UE, and the base station 10 may also be referred to as a gNB.
[0019] In addition, NR is continuing to be studied for a carrier aggregation function that uses wideband to secure data resources, as in LTE. The carrier aggregation function can secure wideband data resources by aggregating multiple component carriers.
[0020] (Previous problems) Conventional carrier aggregation functions require scheduling of data resources for each of a plurality of aggregated component carriers, resulting in a problem of large overhead in resource allocation.
[0021] (Outline of this embodiment) Therefore, in order to solve the above-mentioned conventional problems, a method of allocating resources in a scheduling unit with a granularity different from that of a component carrier will be described. Hereinafter, examples 1 to 3 will be described as specific examples of this embodiment.
[0022] Example 1 In this embodiment, a terminal to which resources are allocated in scheduling units with a granularity different from that of component carriers will be described.
[0023] A framework that performs scheduling or aggregation at a granularity different from that of component carriers is defined as frequency fragmentation.
[0024] In addition, in carrier aggregation, aggregation with a granularity different from that of component carriers is defined as non-contiguous carrier aggregation.
[0025] In addition, in carrier aggregation (discontinuous carrier aggregation), scheduling at a granularity different from that of component carriers is defined as discontinuous scheduling.
[0026] The granularity different from the component carrier may be in units of virtual CCs, BWPs (Bandwidth Parts), PRBs (Physical Resource Blocks), or PRB sets.
[0027] Here, a virtual CC is a carrier set that aggregates all or part of the frequency resources included in each of a plurality of component carriers.
[0028] For example, a virtual CC may be assumed to consist of multiple BWPs.
[0029] Fig. 2 is a first diagram showing an example of the configuration of a virtual CC according to Example 1 of the embodiment of the present invention. The virtual CC#i shown in Fig. 2 is a carrier set that aggregates BWP#a and BWP#b included in each of multiple component carriers (CC#0 and CC#1).
[0030] A virtual CC may also be assumed to consist of multiple PRBs or PRB sets.
[0031] Fig. 3 is a second diagram showing an example of the configuration of a virtual CC according to Example 1 of the embodiment of the present invention. The virtual CC#i shown in Fig. 3 is a carrier set that aggregates multiple PRBs included in each of multiple component carriers (CC#0 and CC#1). Note that the multiple PRBs or PRB sets may be included in one or multiple BWPs.
[0032] The terminal 20 may transmit terminal capability information indicating the configuration of the virtual CC to the base station 10. The terminal capability information indicating the configuration of the virtual CC may be, for example, information indicating that the virtual CC is composed of multiple BWPs, or information indicating that the virtual CC is composed of multiple PRBs.
[0033] Furthermore, the terminal capability information indicating the configuration of a virtual CC may be information indicating that a virtual CC consisting of a plurality of BWPs and a virtual CC consisting of a plurality of PRBs are supported.
[0034] Furthermore, the terminal 20 may assume that an index for identifying each virtual CC is set by the base station 10 via RRC. Furthermore, the terminal 20 may assume that the index for identifying each virtual CC is the minimum value (e.g., i=0 in FIG. 1 or FIG. 2) or the maximum value (e.g., i=1 in FIG. 1 or FIG. 2) of the index of the component carrier.
[0035] The terminal 20 may assume that the scheduling unit in non-continuous scheduling is notified by (i) a virtual CC index, (ii) an index of multiple component carriers + an index of multiple BWPs, (iii) an index of multiple component carriers + an index of multiple PRBs or PRB sets, (iv) an index of multiple component carriers + an index of multiple BWPs + an index of multiple PRBs or PRB sets, etc.
[0036] Furthermore, the terminal 20 may assume that the resource unit of carrier aggregation is a virtual CC, a BWP, a PRB, or a PRB set.
[0037] According to this embodiment, it is possible to realize resource allocation in scheduling units with granularity different from that of component carriers.
[0038] Example 2 In this embodiment, the non-contiguous scheduling method shown in the first embodiment will be described.
[0039] Example 2-1 The terminal 20 may assume non-contiguous scheduling between bands of the same duplex scheme (for example, TDD band + TDD band). The assumed duplex scheme may be one of the following proposals.
[0040] <Plan 1> The terminal 20 may assume a duplex scheme that includes only communications in the same direction at the same time. For example, the terminal 20 may assume non-contiguous scheduling between bands with the same TDD pattern. A TDD pattern is a combination of communication directions for multiple resources in TDD.
[0041] The terminal 20 may assume that there are no downlink and uplink collisions when non-contiguous scheduling is configured by the base station 10. That is, the terminal 20 may assume that it is scheduled in a manner that avoids collisions.
[0042] <Plan 2> The terminal 20 may assume a duplexing scheme that includes communication in different directions at the same time. For example, the terminal 20 may assume non-contiguous scheduling between TDD bands with different TDD patterns. The terminal 20 may operate in one of the following options:
[0043] <Option 1> When non-contiguous scheduling is configured, the terminal 20 may assume that there is no downlink and uplink collision, i.e., the terminal 20 may assume that scheduling is performed to avoid collision.
[0044] <Option 2> When non-continuous scheduling is configured, the terminal 20 may assume that there is a collision between the downlink and the uplink. For example, when there is a collision between the downlink and the uplink, the terminal 20 may perform the operation of Example 3 of Example 2-2 described later.
[0045] The terminal 20 may assume that operation of either Option 1 or Option 2 is configured by the base station 10 in RRC.
[0046] (Example 2-2) The terminal 20 may assume non-contiguous scheduling between bands of different duplexing schemes (for example, TDD band+FDD band). The assumed duplexing scheme may be one of the following proposals.
[0047] When non-continuous scheduling is set, the terminal 20 may perform the operation shown in the following example when there is a collision between the downlink and the uplink.
[0048] <Example 1> When there is a downlink and uplink collision, the terminal 20 may prioritize the TDD band setting and puncture or drop the non-contiguous scheduled resources.
[0049] <Example 2> When there is a downlink and uplink collision, the terminal 20 may prioritize non-contiguous scheduling and puncture or drop resources configured in the TDD band.
[0050] <Example 3> When there is a downlink-uplink collision, the terminal 20 may determine which resources to puncture or drop based on whether the conflicting resources are forward or backward in the time direction. Specifically, when the conflicting resources are forward, the terminal 20 may prioritize the TDD band configuration and puncture or drop the backward resources. Furthermore, when the conflicting resources are backward, the terminal 20 may prioritize non-contiguous scheduled resources and puncture or drop the resources configured in the TDD band.
[0051] Below, scenarios A and B are shown as specific examples of Example 2-2.
[0052] 4 is a first diagram illustrating an example of a scenario A of non-contiguous scheduling according to a second embodiment of the present invention. Scenario A is a scenario in which resources scheduled in the time direction in the order of downlink and uplink duplexing collide with resources scheduled in a non-contiguous manner.
[0053] 5 is a second diagram illustrating an example of scenario A of non-contiguous scheduling according to example 2 of the embodiment of the present invention. FIG. 5 illustrates the operation result of example 1 in scenario A shown in FIG.
[0054] When the non-contiguous scheduled uplink resources collide with the resources scheduled in the time direction in the order of downlink and uplink duplexing, the terminal 20 operating in Example 1 prioritizes the setting of the duplexing method and punctures the non-contiguous scheduled uplink resources.
[0055] Furthermore, if the discontinuously scheduled downlink resources collide with resources scheduled in the downlink and uplink duplex modes in the time direction, the terminal 20 operating in Example 1 prioritizes the duplex mode setting and drops the discontinuously scheduled downlink resources.
[0056] 6 is a third diagram illustrating an example of scenario A of non-contiguous scheduling according to example 2 of the embodiment of the present invention. FIG. 6 illustrates the operation result of example 2 in scenario A shown in FIG.
[0057] When a non-contiguous scheduled uplink resource conflicts with a resource scheduled in a duplex mode in the order of downlink and uplink in the time direction, the terminal 20 operating in Example 2 prioritizes the non-contiguous scheduling and drops the downlink resource set in the duplex mode.
[0058] Furthermore, when discontinuously scheduled downlink resources collide with resources scheduled in the duplex mode in the order of downlink and uplink in the time direction, the terminal 20 operating in Example 2 prioritizes discontinuous scheduling and punctures the uplink resources set in the duplex mode.
[0059] 7 is a fourth diagram illustrating an example of scenario A of non-contiguous scheduling according to example 2 of the embodiment of the present invention. FIG. 7 illustrates the operation result of example 3 in scenario A shown in FIG.
[0060] When a non-contiguous scheduled uplink resource collides with a resource scheduled in a duplex mode in the order of downlink and uplink in the time direction, the terminal 20 operating in Example 3 prioritizes the duplex mode setting and punctures the non-contiguous scheduled uplink resource because the conflicting resource is a later resource in the time direction.
[0061] Furthermore, when a discontinuously scheduled downlink resource collides with a resource scheduled in a duplex mode in the order of downlink and uplink in the time direction, the terminal 20 operating in Example 3 prioritizes the discontinuous scheduling and punctures the uplink resource set in the duplex mode because the conflicting resource is an earlier resource in the time direction.
[0062] 8 is a first diagram illustrating an example of a scenario B of non-contiguous scheduling according to a second embodiment of the present invention. Scenario B is a scenario in which resources scheduled in the time direction in the order of uplink and downlink duplexing collide with resources scheduled in a non-contiguous manner.
[0063] 9 is a second diagram illustrating an example of scenario B of non-contiguous scheduling according to example 2 of the embodiment of the present invention. FIG. 9 illustrates the operation result of example 1 in scenario B shown in FIG.
[0064] When non-contiguous scheduled uplink resources collide with resources scheduled in the uplink and downlink duplex modes in the time direction, the terminal 20 operating in Example 1 prioritizes the duplex mode setting and punctures the non-contiguous scheduled uplink resources.
[0065] Furthermore, if the discontinuously scheduled downlink resources collide with resources scheduled in the uplink and downlink duplex modes in the time direction, the terminal 20 operating in Example 1 prioritizes the duplex mode setting and drops the discontinuously scheduled downlink resources.
[0066] 10 is a third diagram illustrating an example of scenario B of non-contiguous scheduling according to example 2 of the embodiment of the present invention. FIG. 10 illustrates the operation result of example 2 in scenario B shown in FIG.
[0067] When the discontinuously scheduled uplink resources collide with the resources scheduled in the duplex mode in the uplink and downlink order in the time direction, the terminal 20 operating in Example 2 prioritizes the discontinuous scheduling and drops the downlink resources set in the duplex mode.
[0068] Furthermore, when discontinuously scheduled downlink resources collide with resources scheduled in the duplex mode in the order of uplink and downlink in the time direction, the terminal 20 operating in Example 2 prioritizes discontinuous scheduling and punctures the uplink resources set in the duplex mode.
[0069] 11 is a fourth diagram illustrating an example of scenario B of non-contiguous scheduling according to example 2 of the embodiment of the present invention. FIG. 11 illustrates the operation result of example 3 in scenario B shown in FIG.
[0070] When a non-contiguous scheduled uplink resource collides with a resource scheduled in a duplex mode in the order of uplink and downlink in the time direction, the terminal 20 operating in Example 3 prioritizes the non-contiguous scheduling and drops the downlink resource set in the duplex mode because the conflicting resource is an earlier resource in the time direction.
[0071] Furthermore, when a discontinuously scheduled downlink resource collides with a resource scheduled in a duplex mode in the order of uplink and downlink in the time direction, the terminal 20 operating in Example 3 prioritizes the duplex mode setting and drops the discontinuously scheduled downlink resource because the conflicting resource is a later resource in the time direction.
[0072] (Example 2-3) The terminal 20 may assume any of the following as an aggregation band that is the target of non-contiguous scheduling.
[0073] For example, the terminal 20 may assume that the targets of non-contiguous scheduling are frequency bands of the same FR (for example, FR1+FR1).
[0074] Furthermore, the terminal 20 may assume that the targets of non-contiguous scheduling are frequency bands of different FRs (for example, FR1+FR2).
[0075] Furthermore, the terminal 20 may assume that the target of the discontinuous scheduling is a licensed band.
[0076] The terminal 20 may also assume that the target of the non-contiguous scheduling is an unlicensed band.
[0077] The terminal 20 may also assume that the target of non-contiguous scheduling includes licensed bands and unlicensed bands.
[0078] (Examples 2-4) The terminal 20 may assume that the frequency bands that are the subject of non-contiguous scheduling are either co-located or non-co-located.
[0079] For example, the terminal 20 may assume that the frequency bands that are the subject of non-contiguous scheduling are co-located.
[0080] Furthermore, the terminal 20 may assume that the frequency bands that are the subject of non-contiguous scheduling are non-collocated. In this case, the terminal 20 may assume a unique value as the transmission timing (e.g., TA (Timing Advance)) or transmission power (e.g., uplink transmission power) of each frequency band, or may assume a different value for each frequency band.
[0081] When the terminal 20 assumes a unique value as the transmission timing or transmission power for each frequency band, it may assume that the reference frequency band (e.g., reference band) is set by the base station 10 in RRC, or may be determined based on other parameters.
[0082] Here, the terminal 20 may consider the frequency band with the smallest (or largest) subcarrier spacing as the reference band.
[0083] Furthermore, the terminal 20 may consider the frequency band with the smallest (or largest) virtual CC index as the reference band.
[0084] (Examples 2-5) The terminal 20 may assume the subcarrier spacing (numerology indicating the subcarrier spacing) of the frequency band that is the target of non-contiguous scheduling.
[0085] For example, the terminal 20 may assume that the frequency bands that are the subject of non-contiguous scheduling are frequency bands with the same subcarrier spacing.
[0086] Furthermore, the terminal 20 may assume that the frequency bands that are the subject of non-contiguous scheduling are frequency bands with different subcarrier spacings.
[0087] According to the second embodiment, by clarifying the operation of the terminal 20 in non-continuous scheduling, it is possible to realize appropriate transmission and reception operations in non-continuous scheduling.
[0088] Example 3 In this embodiment, an example will be described in which the terminal 20 transmits terminal capability information relating to discontinuous carrier aggregation or discontinuous scheduling to the base station 10.
[0089] The terminal capability information may be information indicating whether or not discontinuous carrier aggregation is supported. Also, the terminal capability information may be information indicating whether or not discontinuous scheduling is supported. The information indicating whether or not discontinuous carrier aggregation or discontinuous scheduling is supported may be information for each frequency band (FR). For example, the terminal capability information may be information indicating that discontinuous carrier aggregation or discontinuous scheduling is supported in only FR1, only FR2, or both FR1 and FR2.
[0090] The terminal capability information may be information indicating whether or not scheduling by virtual CC is supported, and in that case, the terminal capability information may be information including constraints on scheduling by virtual CC.
[0091] For example, the terminal capability information may include information indicating whether intraband aggregation and / or interband aggregation is supported in scheduling using virtual CCs.
[0092] The terminal capability information may also include information indicating the maximum number of virtual CCs, BWPs, or PRBs that are subject to scheduling by virtual CCs.
[0093] Furthermore, the terminal capability information may include information indicating whether or not only the same subcarrier spacing and / or different subcarrier spacings are supported in scheduling using virtual CCs.
[0094] The values included in the above-mentioned terminal capability information may be different between the downlink and the uplink, or may be the same value.
[0095] The above-mentioned terminal capability information may include different values for each interband BC or each intraband frequency band. Also, the above-mentioned terminal capability information may be defined in units different from the conventional ones (for example, for each virtual CC for each BC).
[0096] According to this embodiment, it is possible to realize appropriate non-contiguous carrier aggregation or non-contiguous scheduling according to terminal capabilities.
[0097] In this embodiment, "configured by RRC" may be interpreted as "updated (activated / deactivated) by MAC-CE", "instructed (triggered) by DCI", or the like.
[0098] In this embodiment, "non-contiguous scheduling" may be interpreted as "non-contiguous downlink reception / uplink transmission (non-contiguous DL Rx / UL Tx)", "scheduling type X (X: 0, 1, 2,... or A, B, C,...)", etc.
[0099] In this embodiment, "UE (User Equipment)" may be replaced with "UT (User Terminal)", "Node", "User Node", or the like.
[0100] (Device configuration) Next, an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above will be described.
[0101] <Base station 10> Fig. 12 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 12, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 12 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention. Furthermore, the transmitting unit 110 and the receiving unit 120 may be collectively referred to as a communication unit.
[0102] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of a higher layer from the received signals. The transmitter 110 also has a function of transmitting, to the terminal 20, an NR-PSS, an NR-SSS, an NR-PBCH, a DL / UL control signal, DCI via a PDCCH, data via a PDSCH, and the like.
[0103] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device provided in the setting unit 130, and reads out the information from the storage device as needed.
[0104] The control unit 140 schedules DL reception or UL transmission of the terminal 20 via the transmission unit 110. The control unit 140 also includes a function for performing LBT. The functional unit related to signal transmission in the control unit 140 may be included in the transmission unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the reception unit 120. The transmission unit 110 may also be called a transmitter, and the reception unit 120 may also be called a receiver.
[0105] <Terminal 20> Fig. 13 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 13, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 13 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.
[0106] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, DCI via PDCCH, data via PDSCH, and the like transmitted from the base station 10. For example, the transmitter 210 may transmit a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 120 may receive the PSCCH, PSSCH, PSDCH, PSBCH, and the like from the other terminal 20.
[0107] The setting unit 230 stores various setting information received by the receiving unit 220 from the base station 10 or other terminals in a storage device provided in the setting unit 230, and reads the information from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The control unit 240 controls the terminal 20. The control unit 240 also includes a function for performing LBT.
[0108] The terminal of this embodiment may be configured as the terminals shown in the following items, and may implement the following communication methods.
[0109] <Configuration of this embodiment> (Section 1) a communication unit that performs uplink or downlink communication using frequency bands aggregated by carrier aggregation; a control unit that assumes that scheduling is performed in a unit different from that of a component carrier in the aggregated frequency band; Terminal. (Section 2) It is assumed that the control unit performs scheduling for each carrier set, which aggregates all or a part of frequency resources included in each component carrier among a plurality of component carriers in the aggregated frequency band. 1. The terminal described in paragraph 1. (Section 3) It is assumed that the control unit performs scheduling in a plurality of frequency bands of a duplex method including communications in different directions at the same time. 2. The terminal described in paragraph 2. (Section 4) A transmitter is further provided which transmits, via uplink, terminal capability information relating to carrier aggregation aggregated in units different from component carriers. A terminal according to any one of paragraphs 1 to 3. (Section 5) a communication unit that communicates with terminals using frequency bands aggregated by carrier aggregation; a control unit that assumes that scheduling is performed in a unit different from that of a component carrier in the aggregated frequency band; Base station. (Section 6) performing uplink or downlink communication using frequency bands aggregated by carrier aggregation; and assuming that scheduling is performed in a unit different from that of a component carrier in the aggregated frequency band. The communication method implemented by the device.
[0110] Any of the above configurations provides a technique that enables reducing overhead in resource allocation. According to the second term, it is possible to realize non-contiguous scheduling for each virtual CC. According to the third term, it is possible to realize appropriate transmission and reception operations in non-contiguous scheduling. According to the fourth term, it is possible to realize appropriate non-contiguous carrier aggregation according to terminal capabilities.
[0111] (Hardware configuration) The block diagrams (FIGS. 12 and 13) used in the description of the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.
[0112] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.
[0113] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 14 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0114] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.
[0115] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.
[0116] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.
[0117] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 12 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 13 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.
[0118] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.
[0119] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.
[0120] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.
[0121] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).
[0122] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0123] Furthermore, base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.
[0124] Fig. 15 shows an example configuration of a vehicle 2001. As shown in Fig. 15, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.
[0125] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
[0126] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
[0127] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.
[0128] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001.
[0129] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.
[0130] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.
[0131] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.
[0132] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, which are input to the electronic control unit 2010.
[0133] The communication module 2013 receives various information (traffic information, traffic signal information, inter-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.
[0134] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The division of items in the above description is not essential to the present invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.
[0135] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0136] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).
[0137] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.
[0138] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).
[0139] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.
[0140] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.
[0141] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
[0142] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0143] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.
[0144] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0145] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0146] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0147] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.
[0148] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
[0149] In this disclosure, terms such as "base station (BS)," "radio base station," "base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
[0150] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of a base station and / or base station subsystem that provides communication service within this coverage.
[0151] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.
[0152] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
[0153] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, or the mobile body itself. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
[0154] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.
[0155] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.
[0156] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.
[0157] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
[0158] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
[0159] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0160] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.
[0161] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0162] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.
[0163] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
[0164] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.
[0165] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.
[0166] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.
[0167] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.
[0168] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
[0169] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.
[0170] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0171] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0172] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0173] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
[0174] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.
[0175] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.
[0176] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.
[0177] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.
[0178] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.
[0179] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be set for the terminal 20 within one carrier.
[0180] At least one of the configured BWPs may be active, and the terminal 20 may not expect to transmit or receive a predetermined signal / channel outside the active BWP. Note that the terms "cell," "carrier," and the like in this disclosure may be read as "BWP."
[0181] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.
[0182] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0183] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."
[0184] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).
[0185] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]
[0186] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)
Claims
1. a communication unit that performs uplink or downlink communication using frequency bands aggregated by carrier aggregation; A terminal including: a control unit that assumes that scheduling is performed in a unit different from a component carrier in the aggregated frequency band; the control unit assumes that scheduling is performed for each carrier set, which aggregates all or a part of frequency resources included in each component carrier among a plurality of component carriers in the aggregated frequency band; It is assumed that the control unit performs scheduling in a plurality of frequency bands of a duplex method including communications in different directions at the same time. Terminal.
2. A transmitter is further provided which transmits, via uplink, terminal capability information relating to carrier aggregation aggregated in units different from component carriers. The terminal according to claim 1 .
3. a communication unit that communicates with terminals using frequency bands aggregated by carrier aggregation; A base station comprising: a control unit that assumes that scheduling is performed in a unit different from a component carrier in the aggregated frequency band; the control unit assumes that scheduling is performed for each carrier set, which aggregates all or a part of frequency resources included in each component carrier among a plurality of component carriers in the aggregated frequency band; It is assumed that the control unit performs scheduling in a plurality of frequency bands of a duplex method including communications in different directions at the same time. Base station.
4. performing uplink or downlink communication using frequency bands aggregated by carrier aggregation; a control step of assuming that scheduling is performed in a unit different from that of a component carrier in the aggregated frequency band, It is assumed that, in the control step, the terminal is scheduled for each carrier set in the aggregated frequency band, the carrier set including all or a part of frequency resources included in each component carrier among a plurality of component carriers; It is assumed that in the control step, the terminal is scheduled in a plurality of frequency bands of a duplex method including communications in different directions at the same time. The communication method implemented by the device.
Citation Information
Patent Citations
harq behavior in situations where tdd and fdd cells are included in carrier aggregation
JP2017502543A
Control plane design for bandwidth part in New Radio.
JP2021503762A