Wireless base station and terminal
By assigning distinct identifiers to PSCell and SCell, the ambiguity in UCI multiplexing is resolved, enabling effective UCI transmission on the PSCell, thus clarifying the destination for UCI during carrier aggregation and dual connectivity.
Patent Information
- Application Number
- JP2023510089
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-03-31
- Publication Date
- 2024-12-24
- Estimated Expiration
- 2041-03-31
AI Technical Summary
In 3GPP Release 15, UEs face challenges in determining whether to multiplex uplink control information (UCI) on the Physical Uplink Shared Channel (PUSCH) of the Primary Secondary Cell (PSCell) or Secondary Cell (SCell) when their respective identifiers overlap, leading to ambiguity in UCI transmission during carrier aggregation.
The solution involves assigning unique and non-overlapping secondary cell identifiers (SCellIndex) and serving cell identifiers (servCellIndex) to PSCell and SCell within the same cell group, ensuring clear identification and prioritizing UCI multiplexing on the PSCell when overlaps occur.
This approach allows for accurate multiplexing of UCI onto appropriate PUSCH channels, resolving the ambiguity and ensuring proper UCI transmission within a cell group during carrier aggregation and dual connectivity scenarios.
Smart Images

Figure 0007605965000001 
Figure 0007605965000002 
Figure 0007605965000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a radio base station and a terminal that support carrier aggregation. [Background technology]
[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.
[0003] 3GPP Release 15 (NR) specifies that, during carrier aggregation (CA), a terminal (User Equipment, UE) multiplexes uplink control information (UCI) onto a physical uplink shared channel (PUSCH) transmitted via a serving cell to which a serving cell identifier (servCellIndex) with the smallest value is assigned (Non-Patent Document 1).
[0004] It is specified that a secondary cell (SCell) is configured based on a secondary cell identifier (SCellIndex), and a primary-secondary cell (PSCell), which is a primary cell among multiple secondary cells, is configured based on a serving cell identifier (servCellIndex) (non-patent document 2).
[0005] It is also specified that the SCellIndex assigned to the SCell is also applied to the servCellIndex of the SCell. [Prior art documents] [Non-patent literature]
[0006] [Non-Patent Document 1] 3GPP TS 38.213 V15.12.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15), 3GPP, December 2020 [Non-Patent Document 2] 3GPP TS 38.331 V15.12.0, 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15), 3GPP, December 2020 Summary of the Invention
[0007] The UE multiplexes UCI onto the PUSCH of the serving cell to which the smallest value of servCellIndex is assigned, but there is a possibility that the servCellIndex assigned to the PSCell and the SCellIndex assigned to the SCell overlap.
[0008] For this reason, when the servCellIndex assigned to the PSCell and the SCellIndex assigned to the SCell overlap, the UE cannot determine whether the UCI should be multiplexed into the PUSCH of the PSCell or the PUSCH of the SCell.
[0009] Therefore, the following disclosure has been made in consideration of the above circumstances, and aims to provide a radio base station and a terminal that can realize multiplexing of uplink control information onto an appropriate physical uplink shared channel within a cell group.
[0010] One aspect of the present disclosure is a radio base station (gNB100) comprising a control unit (control unit 140) that sets a secondary cell identifier to be assigned to a secondary cell and a serving cell identifier to be assigned to a primary-secondary cell, which is a primary cell among multiple secondary cells included in the same cell group, to different values, and a transmission unit (RRC processing unit 120) that transmits configuration information including the secondary cell identifier and the serving cell identifier to a terminal.
[0011] One aspect of the present disclosure is a terminal (UE200) including a receiver (RRC processing unit 220) that receives configuration information including a secondary cell identifier assigned to a secondary cell and a serving cell identifier assigned to a primary / secondary cell that is a primary cell among multiple secondary cells included in the same cell group, and a control unit (control unit 240) that multiplexes uplink control information onto a physical uplink shared channel transmitted via the primary / secondary cell when the secondary cell identifier and the serving cell identifier overlap. [Brief description of the drawings]
[0012] [Figure 1] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. As shown in FIG. [Diagram 2] Figure 2 is a functional block diagram of gNB100. [Diagram 3] FIG. 3 is a functional block diagram of UE 200. [Figure 4] FIG. 4 is a diagram showing an example in which the SCellIndex assigned to the SCell and the servCellIndex assigned to the PSCell overlap. [Diagram 5] FIG. 5 is a diagram illustrating an example of a communication sequence between the UE 200 according to the first operation example and a network. [Figure 6] FIG. 6 is a diagram showing an operation flow of multiplexing UCI onto PUSCH in the UE 200 according to the second operation example. [Figure 7]FIG. 7 is a diagram showing an example of the hardware configuration of gNB100 and UE200. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Hereinafter, an embodiment will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and the description thereof will be omitted as appropriate.
[0014] (1) Overall configuration of wireless communication system 1 is a schematic diagram of an overall configuration of a wireless communication system 10 according to the present embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter, UE 200).
[0015] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G. The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG.
[0016] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and the 5GC may be simply referred to as a "network."
[0017] The gNB 100 is a radio base station conforming to NR, and performs radio communication conforming to NR with the UE 200. The gNB 100 and the UE 200 may perform radio communication via a radio bearer, specifically, a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB).
[0018] In addition, gNB100 and UE200 can support Massive MIMO, which generates more directional beams by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which bundles together multiple component carriers (CCs), and Dual Connectivity (DC), which enables simultaneous communication between the UE and multiple NG-RAN Nodes.
[0019] In the DC (and CA), a master cell group (MCG) and a secondary cell group (SCG) may be configured. The MCG may include a primary cell (PCell), and the SCG may include a secondary cell (SCell).
[0020] Furthermore, the SCell may include a primary / secondary cell (PSCell). The PSCell is a type of SCell, but may be interpreted as a special SCell having the same function as the PCell. Alternatively, the PSCell may be interpreted as a CC that ensures connectivity among CCs supported by the SCell (which may be called a secondary radio base station) in DC or Multi-RAT Dual Connectivity (MR-DC).
[0021] In the PSCell, similarly to the PCell, functions such as transmission of a PUCCH (Physical Uplink Control Channel), a contention-based random access procedure (CBRA), and Radio Link Monitoring (downlink radio quality monitoring) may be performed.
[0022] Furthermore, control information may be transmitted and received in downlink (DL) and uplink in the wireless communication system 10. Specifically, downlink control information (DCI) and uplink control information (UCI) are transmitted and received.
[0023] The PUCCH may be interpreted as an UL physical channel used for transmitting UCI. The UCI may be transmitted by either the PUCCH or the PUSCH depending on the situation. Note that the DCI may always be transmitted by the PDCCH (Physical Downlink Control Channel) and may not be transmitted via the PDSCH (Physical Downlink Shared Channel).
[0024] The UCI may include at least one of an acknowledgement (ACK) / negative acknowledgement (NACK) of a hybrid automatic repeat request (HARQ), a scheduling request (SR) from the UE 200, and Channel State Information (CSI).
[0025] Also, when UE 200 configures an SCG, the UCI reporting procedure (3GPP TS38.213, Chapter 9) may be applied to both the MCG and the SCG. When the procedure is applied to the SCG, the terms secondary cell (may include plural) and serving cell (may include plural) may refer to a secondary cell (not including a PSCell) and a serving cell belonging to the SCG, and a PCell may refer to a PSCell of the SCG.
[0026] In addition, the serving cell may be simply interpreted as a cell to which the UE 200 is connected, but more strictly speaking, in the case of an RRC_CONNECTED UE in which CA is not configured, there may be only one serving cell that configures the PCell. In the case of an RRC_CONNECTED UE configured using CA, the serving cell may be interpreted as indicating a set of one or more cells including the PCell and all PCells.
[0027] (2) Functional block configuration of wireless communication system Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of the gNB 100 and the UE 200 will be described.
[0028] (2.1) gNB100 Fig. 2 is a functional block configuration diagram of the gNB 100. As shown in Fig. 2, the gNB 100 includes a radio communication unit 110, an RRC processing unit 120, a CA processing unit 130, and a control unit 140.
[0029] The wireless communication unit 110 transmits a downlink signal (DL signal) conforming to LTE, and also receives an uplink signal (UL signal) conforming to LTE.
[0030] The RRC processing unit 120 executes various processes in a radio resource control layer (RRC). For example, the RRC processing unit 120 can transmit an RRC Reconfiguration to the UE 200. In addition, the RRC processing unit 120 can receive an RRC Reconfiguration Complete from the UE 200, which is a response to the RRC Reconfiguration.
[0031] In addition, the RRC processing unit 120 can transmit and receive other RRC layer messages (RRC Setup Request, RRC Setup, RRC Setup Complete, etc.).
[0032] In this embodiment, the RRC processing unit 120 can transmit configuration information including cell identification information to the UE 200. Specifically, the RRC processing unit 120 can transmit an RRC Reconfiguration including a CellGroupConfig to the UE 200.
[0033] An information element (IE) of CellGroupConfig may include an SCellIndex (secondary cell identifier) that uniquely identifies an SCell in the same cell group, specifically, an SCG, and a servCellIndex (serving cell identifier) that uniquely identifies a serving cell. In this embodiment, the RRC processing unit 120 may configure a transmission unit that transmits configuration information including the secondary cell identifier and the serving cell identifier to the UE 200.
[0034] In addition, SCellIndex may also be applied to the servCellIndex (serving cell identifier) of the SCell. Specifically, the servCellIndex IE is related to a short identifier (ID) used to identify a serving cell (PCell, PSCell, or SCell), and a value of 0 may apply to the PCell and a previously assigned SCellIndex may apply to the SCell.
[0035] Furthermore, the secondary cell identifier and / or the serving cell identifier do not necessarily have to be included in the CellGroupConfig, and may be included in other IEs.
[0036] The CA processing unit 130 executes processing related to carrier aggregation (CA) and dual connectivity (DC).
[0037] Specifically, the CA processing unit 130 may perform configurations related to multiple component carriers (CCs), cells (PCell / PSCell / SCell), and cell groups to support CA (and / or DC).
[0038] Particularly, in this embodiment, the CA processing unit 130 can acquire UCI multiplexed in PUCCH or PUSCH during CA (or DC). As described above, UCI can be transmitted by either PUCCH or PUSCH. In addition, when UCI is multiplexed in PUSCH, it may be determined which cell's PUSCH the UCI is multiplexed in based on cell identification information, specifically, the value of servCellIndex.
[0039] The control unit 140 controls each functional block constituting the gNB 100. In particular, in this embodiment, the control unit 140 can execute control related to setting of identification information assigned to a cell during CA or DC.
[0040] Specifically, the control unit 140 can determine the value of a secondary cell identifier (SCellIndex) to be assigned to a secondary cell (SCell). The value of SCellIndex is typically a numeric value such as a natural number, but is not necessarily limited to a numeric value.
[0041] In addition, the control unit 140 can determine a value of a serving cell identifier (servCellIndex) to be assigned to the serving cell. The value of servCellIndex is typically a numeric value such as a natural number, but is not necessarily limited to a numeric value.
[0042] When determining SCellIndex and servCellIndex, the control unit 140 can set SCellIndex and servCellIndex assigned to SCGs included in the same cell group (specifically, SCG) to different values.
[0043] That is, the control unit 140 determines the value of servCellIndex and the value of SCellIndex so that the servCellIndex to be assigned to a PSCell and the SCellIndex to be assigned to an SCell do not overlap within the same cell group (SCG). For example, when the control unit 140 sets 1 to the servCellIndex to be assigned to a PSCell, the control unit 140 may set a numerical value other than 1 (for example, 2 or greater) to the SCellIndex.
[0044] In this way, the control unit 140 may set the SCellIndex assigned to the SCell and the servCellIndex assigned to the PSCell that is the primary cell among the multiple SCells included in the same cell group to different values.
[0045] (2.2)UE200 3 is a functional block diagram of the UE 200. As shown in FIG. 3, the UE 200 includes a radio communication unit 210, an RRC processing unit 220, a CA processing unit 230, and a control unit 240.
[0046] The wireless communication unit 210 transmits an uplink signal (UL signal) conforming to NR. The wireless communication unit 210 also receives a downlink signal (DL signal) conforming to NR. In other words, the UE 200 can access the gNB 100 (NG-RAN 20) and can support CA and DC.
[0047] The RRC processing unit 220 executes various processes in the radio resource control layer (RRC). Specifically, the RRC processing unit 220 can transmit and receive messages of the radio resource control layer.
[0048] The RRC processing unit 220 can receive RRC Reconfiguration from the network, specifically, from the NG-RAN 20. In addition, the RRC processing unit 220 can transmit RRC Reconfiguration Complete, which is a response to the RRC Reconfiguration, to the network.
[0049] In this embodiment, the RRC processing unit 220 can receive an RRC Reconfiguration including a CellGroupConfig. As described above, an information element (IE) of the CellGroupConfig may include an SCellIndex (secondary cell identifier) that uniquely identifies an SCell in the same cell group, specifically, in the SCG, and a servCellIndex (serving cell identifier) that uniquely identifies a serving cell.
[0050] In this embodiment, the RRC processing unit 220 may constitute a receiving unit that receives CellGroupConfig (setting information) including an SCellIndex assigned to an SCell and a servCellIndex assigned to a PSCell that is a PCell among multiple SCells included in the same cell group.
[0051] The CA processing unit 230 executes processing related to carrier aggregation (CA) and dual connectivity (DC).
[0052] Specifically, the CA processing unit 230 may perform configurations related to multiple component carriers (CCs), cells (PCell / PSCell / SCell), and cell groups to support CA (and / or DC).
[0053] Particularly, in this embodiment, the CA processing unit 230 can perform a process of multiplexing uplink control information (UCI) onto a PUCCH or a PUSCH. As described above, UCI can be multiplexed onto a PUCCH or a PUSCH, but when multiple SCells are configured during CA (and / or DC), the CA processing unit 230 may multiplex UCI onto a PUSCH via any of the SCells (hereinafter, appropriately abbreviated as PUSCH of the SCell).
[0054] Specifically, the CA processing unit 230 may multiplex UCI onto any one of a plurality of PUSCHs under control of the control unit 240.
[0055] The control unit 240 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 240 can execute control related to transmission of uplink control information (UCI).
[0056] Specifically, the control unit 240 can determine a cell in which UCI should be multiplexed, specifically, an uplink channel of the cell, based on cell identification information during CA (and / or DC). More specifically, the control unit 240 can determine a PUSCH of an SCell in which UCI should be multiplexed, based on SCellIndex assigned to the SCell and a serving cell, particularly, servCellIndex assigned to the PSCell.
[0057] Here, control unit 240 may multiplex UCI onto the PUSCH of the serving cell to which the smallest value of servCellIndex is assigned, but there may be cases where the servCellIndex assigned to the PSCell overlaps with the SCellIndex assigned to the SCell.
[0058] In this way, when SCellIndex and servCellIndex overlap, the control unit 240 may multiplex UCI into the PUSCH transmitted via the PSCell. Note that, when a numeric value such as a natural number is used as described above, overlapping of SCellIndex and servCellIndex may be interpreted as a case where the same number is assigned. On the other hand, when a part of SCellIndex is the same as a part of servCellIndex, it may also be interpreted that SCellIndex and servCellIndex overlap.
[0059] Furthermore, the control unit 240 may multiplex UCI by giving priority to the PUSCH transmitted via the PSCell rather than to the SCell to which the SCellIndex overlaps with servCellIndex is assigned. Specifically, when the SCellIndex and the servCellIndex overlap, the control unit 240 may preferentially use the PUSCH of the PSCell for multiplexing UCI rather than the PUSCH of the SCell. In this case, transmission of UCI by the PUSCH of the SCell is not excluded, and may include a state in which more UCI is multiplexed on the PUSCH of the PSCell.
[0060] (3) Operation of wireless communication system Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation related to the setting of cell identification information during CA (and / or DC, the same applies below) and multiplexing uplink control information (UCI) onto a PUSCH based on the identification information.
[0061] (3.1) Premise The UCI reporting procedure (3GPP TS38.213, Chapter 9) specifies that UCI is multiplexed into a PUSCH transmitted via a serving cell to which the smallest value of servCellIndex is assigned.
[0062] When CA is executed, that is, when UE 200 configures an SCG, SCell may be configured by SCellIndex. Also, PSCell may be configured by servCellIndex. Specifically, as described above, servCellIndex may be configured by SpCellConfig included in an IE of CellGroupConfig, and SCellIndex may be configured by SCellConfig (see 3GPP TS38.331, Chapter 6.3.2).
[0063] Also, the SCellIndex assigned to the SCell is also applied to the servCellIndex of the SCell. The servCellIndex IE is related to a short identifier (ID) used to identify a serving cell (PCell, PSCell or SCell), where a value of 0 applies to the PCell and a previously assigned SCellIndex may apply to the SCell.
[0064] In this case, the following problem occurs: When servCellIndex assigned to a PSCell and SCellIndex assigned to a SCell overlap, UE 200 multiplexes UCI onto the PUSCH of the serving cell having the smallest servCellIndex value, but cannot determine whether UCI should be multiplexed onto a PUSCH of the PSCell or onto the corresponding SCell.
[0065] FIG. 4 shows an example in which the SCellIndex assigned to the SCell and the servCellIndex assigned to the PSCell overlap.
[0066] In Example 1, servCellIndex(1) of the PSCell overlaps with SCellIndex(1) of the SCell (the boxed number portion). Note that multiple SCells may be configured, and different SCellIndexes may be assigned to each of them. In this case, UE 200 cannot determine whether UCI should be multiplexed into the PSCell or into the PUSCH of the SCell with SCellIndex(1).
[0067] In Example 2, servCellIndex(3) of the PSCell overlaps with SCellIndex(3) of the SCell (the boxed number portion). In the case of Example 2, there is no problem when UCI is multiplexed onto the PUSCH of the SCell with SCellIndex(2), but when PUSCH transmission of the SCell (PSCell) with SCellIndex(3) occurs, it is not possible to determine onto which PUSCH the UCI should be multiplexed.
[0068] An example of an operation that can solve such a problem will be described below.
[0069] (3.2) Example 1 In this operation example, an operation of avoiding overlap between servCellIndex assigned to a PSCell and SCellIndex assigned to a SCell on the network side will be described.
[0070] 5 shows an example of a communication sequence between UE 200 and a network according to operation example 1. The network (gNB 100) assigns a value (number) to servCellIndex to be assigned to a PSCell that is different from the value (number) of SCellIndex to be assigned to an SCell in the same cell group. In other words, in the same cell group (specifically, SCG), servCellIndex to be assigned to a PSCell and SCellIndex to be assigned to an SCell must not overlap.
[0071] servCellIndex in 3GPP TS38.331 may be defined as follows:
[0072] "The IE ServCellIndex concerns a short identity, used to identify a serving cell (ie the PCell, the PSCell or an SCell). Value 0 applies for the PCell, while the SCellIndex that has previously been assigned applies for SCells. For servCellIndex of PSCell, the value shall be assigned other than SCellIndex used for SCells within SCG." In this way, for servCellIndex of a PSCell, a value other than SCellIndex used for SCells in the SCG may be assigned.
[0073] As shown in Fig. 5, the network sets the servCellIndex assigned to the PSCell (step 1). For example, the network sets the servCellIndex assigned to the PSCell to "1".
[0074] Next, the network sets the SCellIndex to be assigned to the SCell (step 2). For example, the network sets the SCellIndex to be assigned to the SCell to "2". Note that if there are multiple SCells, the same process may be repeated, but an index other than "1" and "2" may be assigned. Also, the order of the operations in step 1 and step 2 may be reversed.
[0075] The network transmits an RRC message including the configured servCellIndex and SCellIndex to the UE 200 (step 3). Specifically, the network transmits an RRC Reconfiguration including a CellGroupConfig, and the CellGroupConfig may include the configured servCellIndex and SCellIndex.
[0076] UE 200 selects a PUSCH into which UCI should be multiplexed, based on the values of servCellIndex(1) and SCellIndex(2) included in the received CellGroupConfig, and multiplexes UCI into the selected PUSCH (step 4).
[0077] Specifically, the UE 200 may multiplex the UCI into the PUSCH of the serving cell to which the smallest value of servCellIndex(1) is assigned, specifically, the PSCell.
[0078] (3.3) Example 2 In this operation example, an operation of multiplexing UCI onto PUSCH in UE 200 in a case where servCellIndex assigned to a PSCell and SCellIndex assigned to a SCell overlap will be described.
[0079] 6 shows an operation flow of multiplexing UCI onto a PUSCH in the UE 200 according to the operation example 2. As described above, the UE 200 can multiplex UCI onto a PUSCH of a cell having a servCellIndex with a smallest value (the smallest servCellIndex cell) in the same cell group.
[0080] Here, when servCellIndex of the PSCell and servCellIndex (SCellIndex) of the SCell overlap, UE 200 may multiplex UCI onto the PUSCH of the PSCell, or may preferentially multiplex UCI onto the PUSCH of the PSCell.
[0081] 6, the UE 200 receives an RRC Reconfiguration including a CellGroupConfig (step 10). As described above, the CellGroupConfig may include a servCellIndex assigned to a PSCell and an SCellIndex assigned to a SCell.
[0082] The UE 200 determines whether or not the servCellIndex of the PSCell overlaps with the SCellIndex of the SCell (step 20). For example, when the servCellIndex of the PSCell is "3" and the SCellIndex of any SCell is "3" (see example 2 in FIG. 4), it may be determined that the servCellIndex of the PSCell overlaps with the SCellIndex of the SCell.
[0083] In this way, when the servCellIndex of a PSCell overlaps with the SCellIndex of an SCell, if PUSCH transmission occurs from an SCell (PSCell) with SCellIndex of "3", a question arises as to which PUSCH the UCI should be multiplexed onto. UE 200 may decide to multiplex the UCI onto the PUSCH of the PSCell (step 30).
[0084] The UE 200 transmits the PUSCH of the PSCell multiplexed with the UCI (step 40). Note that the UE 200 may multiplex the UCI onto all the PUSCHs of the PSCell, or may preferentially use the PUSCH of the PSCell and multiplex the UCI onto the PUSCH of the SCell as well.
[0085] (4) Actions and Effects According to the above-described embodiment, the following advantageous effects can be obtained: Specifically, the network (gNB100) can set the SCellIndex assigned to an SCell and the servCellIndex assigned to a PSCell that is a primary cell among multiple SCells included in the same cell group to different values.
[0086] Furthermore, when the SCellIndex and the servCellIndex overlap, the UE 200 may multiplex or preferentially multiplex the UCI into the PUSCH transmitted via the PSCell.
[0087] Therefore, in a cell group (SCG), multiplexing of UCI to an appropriate PUSCH can be realized. In other words, in NR CA (and / or DC), when UE 200 multiplexes UCI to a PUSCH on a cell with the smallest servCellIndex, it becomes possible to distinguish between a PSCell and an SCell, and the problem that UE 200 cannot determine the multiplex destination of UCI can be solved.
[0088] (5) Other embodiments Although the embodiment has been described above, it will be apparent to those skilled in the art that the present invention is not limited to the description of the embodiment and that various modifications and improvements are possible.
[0089] For example, in the above-described embodiment, an example has been described in which SCellIndex and servCellIndex are included in CellGroupConfig, but at least one of SCellIndex and servCellIndex may be included in another IE.
[0090] Also, in the above description, configure, activate, update, indicate, enable, specify, and select may be interchanged. Similarly, link, associate, correspond, and map may be interchanged, and allocate, assign, monitor, and map may be interchanged.
[0091] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be read as interchangeable terms. Similarly, common, shared, group-common, UE-common, and UE-shared may be read as interchangeable terms.
[0092] Moreover, the block diagrams (FIGS. 2 and 3) used in the description of the above-mentioned 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 by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by using wires, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.
[0093] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. As described above, there is no particular limitation on the method of realization of any of these.
[0094] Furthermore, the above-mentioned gNB100 and UE200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 7 is a diagram showing an example of a hardware configuration of the device. As shown in Fig. 7, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.
[0095] In the following description, the term "apparatus" may be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus 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.
[0096] Each functional block of the device (see FIGS. 2 and 3) is realized by any hardware element of the computer device, or a combination of the hardware elements.
[0097] In addition, each function in the device is realized by loading a specific software (program) onto hardware such as the processor 1001, memory 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 of data in the memory 1002 and storage 1003.
[0098] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.
[0099] Furthermore, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. Furthermore, the above-mentioned various processes may be executed by one processor 1001, or may 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.
[0100] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.
[0101] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.
[0102] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.
[0103] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
[0104] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
[0105] In addition, each device such as the processor 1001 and the memory 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.
[0106] Furthermore, the device 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), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0107] 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., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination of these. Furthermore, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0108] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable systems, and next-generation systems extended based on these. In addition, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) may be applied.
[0109] The order of the steps, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. 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.
[0110] In the present disclosure, a specific operation performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and other network nodes other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case in which there is one other network node other than the base station, it may also be a combination of multiple other network nodes (e.g., MME and S-GW).
[0111] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and may be input and output via multiple network nodes.
[0112] The input / output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information may be overwritten, updated, or appended. The output information may be deleted. The input information may be transmitted to another device.
[0113] The determination may be based on a value represented by a single bit (0 or 1), a Boolean (true or false) value, or a numerical comparison (e.g., comparison with a predetermined value).
[0114] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).
[0115] 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.
[0116] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the 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, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.
[0117] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the 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.
[0118] In addition, the terms described in this disclosure and the 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). Also, a signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0119] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0120] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.
[0121] The names used for the above-mentioned parameters are not limiting in any way. Furthermore, the formulas 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 limiting in any way.
[0122] In this disclosure, terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.
[0123] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).
[0124] The term "cell" or "sector" refers to part or all of the coverage area of a base station and / or a base station subsystem that provides communication services within that coverage.
[0125] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.
[0126] 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.
[0127] 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 moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving 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 include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
[0128] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies below). For example, each aspect / embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel (or side link).
[0129] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station. 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.
[0130] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of a SubCarrier Spacing (SCS), a bandwidth, a symbol length, a Cyclic Prefix length, a Transmission Time Interval (TTI), a number of symbols per TTI, a radio frame structure, a particular filtering operation that the transceiver performs in the frequency domain, a particular windowing operation that the transceiver performs in the time domain, etc.
[0131] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) A slot may be a numerology-based unit of time.
[0132] A slot may include multiple minislots. Each minislot may be composed of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed 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.
[0133] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. The radio frame, the subframe, the slot, the minislot, and the symbol may each be referred to by a different name.
[0134] 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 the 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.
[0135] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.
[0136] 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) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.
[0137] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.
[0138] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc.
[0139] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 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.
[0140] A resource block (RB) is a resource allocation unit in the time domain and the 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 the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.
[0141] In addition, the time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.
[0142] One or more RBs may 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.
[0143] 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.
[0144] 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 numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.
[0145] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.
[0146] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".
[0147] The above-mentioned 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.
[0148] 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 at least one of one or more wires, cables, and 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.
[0149] The reference signal may also be abbreviated as Reference Signal (RS), and may be called a pilot depending on the applicable standard.
[0150] 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."
[0151] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0152] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish 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 therein or that the first element must precede the second element in some way.
[0153] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term "comprising." Further, as used in this disclosure, the term "or" is not intended to be an exclusive or.
[0154] In this disclosure, where articles have been added due to translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0155] 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, search, inquiry (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 a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.
[0156] 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."
[0157] 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 in the present disclosure. 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]
[0158] 10. Wireless communication systems 20 NGRAN 100 gNB 110 Wireless Communication Division 120 RRC processing unit 130 CA Processing Section 140 Control section 200UE 210 Wireless Communication Department 220 RRC Processing Unit 230 CA Processing Section 240 Control Unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output device 1007 Bus
Claims
1. A control unit that sets a secondary cell identifier to be assigned to a secondary cell and a serving cell identifier to be assigned to a primary / secondary cell to different values; A transmitter that transmits the secondary cell identifier and the serving cell identifier to a terminal; A radio base station comprising:
2. The secondary cell and the primary-secondary cell are included in the same cell group. The radio base station according to claim 1.
3. A step of setting a secondary cell identifier to be assigned to a secondary cell and a serving cell identifier to be assigned to a primary / secondary cell to different values; transmitting the secondary cell identifier and the serving cell identifier to a terminal; A wireless communication method comprising:
4. A wireless communication system including a wireless base station and a terminal, The wireless base station A control unit that sets a secondary cell identifier to be assigned to a secondary cell and a serving cell identifier to be assigned to a primary / secondary cell to different values; A transmitter that transmits the secondary cell identifier and the serving cell identifier to the terminal; Equipped with The terminal includes a receiving unit that receives the secondary cell identifier and the serving cell identifier from the radio base station. Wireless communication system.
