Communication device, base station, communication method, and integrated circuit

Abstract

The present invention makes appropriate uplink signal transmission possible. In this invention, a terminal includes: a reception circuit that receives first control information including information on a plurality of candidates for a sequence length of an orthogonal code, and second control information including information on an orthogonal code corresponding to any of the plurality of candidates for the sequence length; and a control circuit that controls transmission of an uplink signal to which the orthogonal code is applied, on the basis of the first control information and the second control information.

Description

Communication device, base station, communication method, and integrated circuit

[0001] The present disclosure relates to a communication device, a base station, a communication method, and an integrated circuit.

[0002] New Radio access technology (NR) for 5G has been specified by 3GPP, and specifications up to Release 18 (Rel.18) of NR have been published.

[0003] 3GPP, TR 38.821, V16.1.0 “Solutions for NR to support non-terrestrial networks (NTN) (Release 16)”3GPP, TS 38.214, V18.1.0 “NR; Physical layer procedures for data (Release 18)”

[0004] However, there is room for further consideration regarding the method of transmitting the upstream signal.

[0005] Non-limiting embodiments of the present disclosure contribute to providing a communication device, a base station, a communication method, and an integrated circuit that can appropriately transmit an uplink signal.

[0006] A terminal according to one embodiment of the present disclosure includes a receiving circuit that receives first control information including information regarding multiple candidates for the sequence length of an orthogonal code and second control information including information regarding the orthogonal code corresponding to one of the multiple candidates for the sequence length, and a control circuit that controls transmission of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

[0007] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0008] According to an embodiment of the present disclosure, uplink signals can be transmitted appropriately.

[0009] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features.

[0010] Block diagram showing an example of the configuration of a portion of a terminal. Block diagram showing an example of the configuration of a portion of a base station. Block diagram showing an example of the configuration of a terminal. Block diagram showing an example of the configuration of a base station. Diagram showing an example of the relationship between the sequence length of an OCC (Orthogonal Cover Code) and φ. Diagram showing an example of inter-slot OCC. Diagram showing an example of OCC between OFDM (Orthogonal Frequency Division Multiplexing) symbols. Diagram showing an example of OCC within an OFDM symbol. Diagram of an exemplary architecture of a 3GPP NR system. Diagram of an exemplary functional division in a 5G O-RAN.

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0012] <Regarding Non-Terrestrial Networks (NTNs)> NR Rel. 15 is specified as a radio access technology for terrestrial networks. On the other hand, NR is being considered for extension to non-terrestrial networks (NTNs), such as communications using satellites or high-altitude platform stations (HAPSs) (see, for example, Non-Patent Document 1).

[0013] In the case of communications via satellite, the distance between the satellite and the terminal (also called user equipment (UE)) is long, which means that propagation attenuation is likely to be large. To achieve a sufficiently high reception quality at the satellite, it is expected that the terminal will use a method such as repeatedly transmitting multiple pieces of data (e.g., repetition transmission).

[0014] In an NTN environment, satellite coverage areas (e.g., one or more cells) for terminals located on the ground, in the sky, such as aircraft or drones, or at sea are formed by beams from the satellite (also called satellite beams). The size of a single beam on the Earth's surface can be, for example, 50 to 1,000 km in diameter. For this reason, NTNs are expected to accommodate a large number of terminals.

[0015] Therefore, for example, studies are being conducted to increase the number of terminals that can be accommodated by multiplying repeatedly transmitted data on a Physical Uplink Shared Channel (PUSCH) used for uplink data transmission by orthogonal codes (e.g., orthogonal cover codes (OCCs)) that differ between terminals and multiplexing the data onto the same time-frequency resources.

[0016] Three methods of applying OCC are under consideration: (1) "Inter-slot OCC," (2) "Inter-symbol OCC," and (3) "Intra-symbol OCC."

[0017] In inter-slot OCC, PUSCHs between terminals are made orthogonal in units of multiple slots by multiplying by OCC when repetition is performed in units of slots.

[0018] Inter-symbol OCC makes PUSCHs between terminals orthogonal in units of multiple symbols by multiplying by OCC when repetition is performed between OFDM (Orthogonal Frequency Division Multiplexing) symbols.

[0019] Intra-symbol OCC, the modulation symbols before DFT spreading are replicated in the DFT (Discrete Fourier Transform)-S (spread)-OFDM signal generation process and multiplied by OCC, thereby orthogonalizing the PUSCHs between terminals in units of multiple modulation symbols.

[0020] When applying (introducing) OCC, there is room for consideration regarding a method for notifying a terminal of which OCC sequence length (also referred to as OCC length) and which OCC sequence (e.g., OCC sequence, OCC sequence number, OCC number, or OCC index) to use.

[0021] In one non-limiting embodiment of the present disclosure, a method for reporting information about the OCC applied to PUSCH transmission (for example, the OCC sequence length and the OCC sequence) will be described.

[0022] Furthermore, for example, in order to multiplex PUSCHs onto the same time-frequency resources between terminals, it is expected that different ports (DMRS ports) will be used between terminals for demodulation reference signals (DMRS) used for channel estimation. In a non-limiting embodiment of the present disclosure, a method for reporting DMRS ports will also be described in addition to information related to OCC.

[0023] For example, in one non-limiting embodiment of the present disclosure, a base station reports information regarding an OCC sequence length, an OCC sequence (e.g., an OCC sequence number), and a DMRS port via RRC (Radio Resource Control) signaling, a MAC (Medium Access Control Element) CE, or downlink control information (e.g., DCI: Downlink Control Information). Furthermore, terminals transmit PUSCHs using different OCC sequences and DMRS ports between different terminals according to the reported information. This allows the base station to appropriately report information regarding the OCC or DMRS port to terminals.

[0024] [Overview of Communication System] A communication system according to an embodiment of the present disclosure includes a terminal 100 and a base station 200.

[0025] Fig. 1 is a block diagram showing an example configuration of a portion of a terminal 100. In the terminal 100 shown in Fig. 1, a communication unit (e.g., corresponding to a receiving circuit) receives first control information (e.g., RRC signaling or MAC CE) including information on multiple candidates for the sequence length of an orthogonal code (e.g., OCC), and second control information (e.g., DCI) including information on an orthogonal code sequence (e.g., OCC sequence number) corresponding to one of the multiple candidates for the sequence length. A control unit (e.g., corresponding to a control circuit) controls transmission of an uplink signal (e.g., PUSCH) to which the orthogonal code is applied, based on the first control information and the second control information.

[0026] 2 is a block diagram showing a configuration example of a portion of a base station 200. In the base station 200 shown in FIG. 2, a communication unit (e.g., corresponding to a transmission circuit) transmits first control information (e.g., RRC signaling or MAC CE) including information on multiple candidates for the sequence length of an orthogonal code (e.g., OCC), and second control information (e.g., DCI) including information on a sequence (e.g., OCC sequence number) of the orthogonal code corresponding to one of the multiple candidates. A control unit (e.g., corresponding to a control circuit) controls reception of an uplink signal (e.g., PUSCH) to which the orthogonal code is applied, based on the first control information and the second control information.

[0027] In this embodiment, base station 200 notifies (or configures) candidates for OCC sequence lengths by RRC signaling, and notifies at least one of the OCC sequence and the DMRS port explicitly or implicitly by DCI (e.g., DCI for scheduling a PUSCH).

[0028] 3 is a block diagram showing an example of the configuration of terminal 100 according to this embodiment. Terminal 100 has radio receiving section 101, data reception processing section 102, control section 103, data transmission processing section 104, and radio transmitting section 105.

[0029] At least one of the data reception processing unit 102, the control unit 103, and the data transmission processing unit 104 shown in Fig. 3 may be included in the control unit shown in Fig. 1. Also, at least one of the wireless reception unit 101 and the wireless transmission unit 105 shown in Fig. 3 may be included in the communication unit shown in Fig. 1.

[0030] The radio receiving section 101 performs analog receiving processing and digital receiving processing such as down-conversion, A / D conversion, and filtering on a signal received from the base station 200 via an antenna, and outputs the processed signal to the data receiving processing section 102 .

[0031] The data reception processing unit 102 demodulates and decodes downlink signals such as SSB (Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) Block), downlink control channels (e.g., PDCCH: Physical Downlink Control Channel), and downlink shared channels (e.g., PDSCH: Physical Downlink Shared Channel) output from the radio reception unit 101.

[0032] The SSB includes, for example, a synchronization signal and broadcast information to the entire cell.

[0033] The PDSCH may include, in addition to user data, broadcast information such as system information, RRC control information, MAC CE control information, a Random Access Channel (RACH) response (e.g., Msg2), a Timing Advance (TA) command, and the like. Furthermore, the data reception processing unit 102 performs reception processing on the RRC control information (e.g., an RRC Reconfiguration message, and the like), and outputs the RRC control information to the control unit 103. The RRC control information may include, for example, information on the OCC, such as the OCC sequence length, information on the number of slots, or information on DMRS bundling. The information on the number of slots may be, for example, at least one of the following: the number of slots to be transmitted with repetition, the number of repetitions, and the number of slots to which one Transport Block (TBoMS) is mapped (e.g., the number of slots to be transmitted with Transport Block processing over Multiple Slots (TBoMS)). Furthermore, the information on DMRS bundling may include, for example, information on the Time Domain Window (TDW). Furthermore, these pieces of information may be included in the MAC CE or Msg.2 transmitted in the PDSCH. The system information may also include information related to time / frequency synchronization such as satellite ephemeris, common TA parameters, Epoch time, etc. The data reception processing unit 102 may output this control information included in the PDSCH to the control unit 103.

[0034] The PDCCH includes, for example, resource allocation information for the PDSCH, resource allocation information for the PUSCH, and resource allocation information for an uplink control channel (for example, PUCCH: Physical Uplink Control Channel) used for HARQ-ACK transmission for the PDSCH. Furthermore, the PDCCH (for example, DCI) may include information on the OCC, such as an OCC sequence length or an OCC sequence number, and information on the antenna port or DMRS port used for transmitting the PUSCH and PUCCH. Note that examples of notification methods for the OCC and DMRS will be described later.

[0035] The control unit 103 may acquire location information of the terminal 100 from a Global Navigation Satellite System (GNSS) or the like. The control unit 103 may also calculate the orbit and position of a satellite based on information such as satellite ephemeris and epoch time input from the data reception processing unit 102. The control unit 103 may calculate a timing adjustment value (TA value) using a round-trip delay time between the terminal 100 and the satellite calculated from the location information, a round-trip delay time between the satellite and the base station calculated from common TA parameters, and information on a TA command notified from the base station 200, and output the TA value to the wireless transmission unit 105.

[0036] The control unit 103 may calculate the Doppler shift based on the satellite orbit information and the terminal position information of the terminal 100 and output it to the radio transmission unit 105 .

[0037] Here, in a time interval where multiplication by a certain OCC sequence is applied (e.g., also referred to as an OCC interval or an OCC application interval), it may be desirable to maintain continuity of phase and amplitude (or power) in order to maintain orthogonality of the OCC-applied signal. For this reason, the control unit 103 may adjust the transmission timing or frequency at timings other than the time interval where multiplication by a certain OCC sequence is applied.

[0038] Control unit 103 outputs information related to the OCC, information related to the number of slots, and information related to the OCC sequence number or DMRS port input from data reception processing unit 102 to data transmission processing unit 104. Control unit 103 also outputs information related to the time / frequency resources for PUSCH transmission notified from base station 200 (input from data reception processing unit 102 to control unit 103) to data transmission processing unit 104.

[0039] In addition, the control unit 103 may output OCC-related capabilities (UE capability), such as the corresponding OCC sequence length, to the data transmission processing unit 104 (transmitting this as the UE capability via an RRC message), taking into account, for example, the corresponding functions or performance of the data transmission processing unit 104 and the radio transmission unit 105 of the terminal 100.

[0040] The data transmission processing unit 104 may perform coding such as LDPC (Low Density Parity Check) on the transmission data, modulation such as QPSK and 16QAM (Quadrature Amplitude Modulation), DFT-s-OFDM modulation processing, and mapping to time / frequency resources based on information about the PUSCH resource, OCC sequence length, OCC sequence number information, or slot number information input from the control unit 103. Furthermore, the data transmission processing unit 104 may perform data repetition and OCC multiplication based on information about the OCC and information about the slot number.

[0041] Furthermore, the data transmission processing unit 104 may generate a DMRS based on information relating to the antenna port or DMRS port input from the control unit 103 and output the DMRS to the radio transmission unit 105 .

[0042] The radio transmitting unit 105 performs analog transmission processing and digital transmission processing such as D / A conversion, filtering, up-conversion, and amplification on the signal input from the data transmission processing unit 104, and transmits the radio signal from an antenna. The radio transmitting unit 105 may perform either or both of timing adjustment and frequency correction based on timing information (e.g., TA information) and a frequency correction value input from the control unit 103.

[0043] 4 is a block diagram showing an example of the configuration of base station 200 according to this embodiment. Base station 200 has radio receiving section 201, data reception processing section 202, control section 203, data transmission processing section 204, and radio transmitting section 205.

[0044] At least one of the data reception processing unit 202, the control unit 203, and the data transmission processing unit 204 shown in Fig. 4 may be included in the control unit shown in Fig. 2. Also, at least one of the wireless reception unit 201 and the wireless transmission unit 205 shown in Fig. 4 may be included in the communication unit shown in Fig. 2.

[0045] The radio receiving section 201 performs analog and digital receiving processes such as down-conversion, A / D conversion, and filtering on the signal received from the terminal 100 via the antenna, and outputs the processed signal to the data receiving processing section 202 .

[0046] The data reception processing unit 202 performs channel estimation and demodulation / decoding processing on uplink signals such as the PUSCH, PUCCH, and PRACH input from the radio receiving unit 201 to obtain a received data sequence. When receiving a PUSCH to which OCC is applied, the data reception processing unit 202 may perform despreading processing (e.g., adding signals multiplied by the complex conjugate or reciprocal of the OCC sequence) according to an OCC sequence length or an OCC sequence number set by the control unit 203. When the despreading interval of one OCC sequence spans multiple slots, the data reception processing unit 202 may perform joint channel estimation using DMRSs of multiple slots.

[0047] Furthermore, the data reception processing unit 202 outputs the RRC message and MAC CE data included in the PUSCH to the control unit 203. The RRC message may include, for example, terminal capabilities related to OCC.

[0048] The control unit 203 generates system information (broadcast information) such as a master information block (MIB) and a system information block (SIB), and control information such as terminal-specific control information (RRC message). The system information may include, for NTN, information such as satellite ephemeris information, common TA parameters used for terminal TA, and epoch time. The RRC message may include, for example, information related to OCC such as an OCC sequence length, information related to the number of slots to be transmitted in repetition or the number of slots for TBoMS, and information related to DMRS bundling.

[0049] The control unit 203 generates downlink control information (DCI) or a PDCCH associated with PDSCH transmission. The DCI may include, for example, information related to PDSCH retransmission control, such as a New Data Indicator (NDI) and a Redundancy Version (RV), information related to the Modulation and Coding Scheme (MCS) of the PDSCH and the PUSCH, resource allocation information for the PDSCH and the PUSCH, and resource allocation information for the PUCCH used for HARQ-ACK transmission for the PDSCH. The DCI may also include, for example, information related to the OCC, such as an OCC sequence length and an OCC sequence number, or information related to the antenna port or DMRS port used for transmitting the PUSCH and the PUCCH. Examples of methods for notifying the OCC and the DMRS port will be described later.

[0050] The control unit 203 outputs, for example, this control information to the data transmission processing unit 204, and also outputs setting values ​​based on the control information (e.g., PUSCH and PUCCH resources, OCC sequence length, OCC sequence number, number of TBoMS slots, number of repetitions, TDW of DMRS bundling, etc.) to the data reception processing unit 202.

[0051] The data transmission processing unit 204 performs coding such as LDPC on the transmission data and control information input from the control unit 203 , performs modulation such as QPSK and 16QAM, and outputs the result to the radio transmission unit 205 .

[0052] The radio transmitting section 205 performs transmission processing such as D / A conversion, filtering, up-conversion, and amplification on the signal input from the data transmission processing section 204, and transmits the radio signal from the antenna.

[0053] [Example of Operation of Terminal and Base Station] Hereinafter, an example of a method for reporting the OCC sequence length, OCC sequence number, and DMRS port used for multiplexing by OCC between terminals will be described.

[0054] [Method of Notifying OCC Sequence Length] In the NR specifications up to 3GPP Rel. 18, for example, as described in TS38.331 V18.1.0 and TS38.212 V18.1.0, there is a method using the RRC parameter "pusch-TimeDomainResourceAllocationList" (also called "pusch-TDRA list") for allocating resources in the time domain of the PUSCH. The pusch-TDRA list is a list of resource allocation parameters in the time domain, and "PUSCH-Allocation-r16" shown below is a component (parameter set) of the list. PUSCH-Allocation-r16 ::= SEQUENCE { mappingType-r16 ENUMERATED {typeA, typeB} startSymbolAndLength-r16 INTEGER (0..127) startSymbol-r16 INTEGER (0..13) length-r16 INTEGER (1..14) numberOfRepetitions-r16 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} numberOfRepetitionsExt-r17 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16, n20, n24, n28, n32, spare1-4} numberOfSlotsTBoMS-r17 ENUMERATED {n1, n2, n4, n8, spare4, spare3, spare2, spare1} extendedK2-r17 INTEGER (0..128)}

[0055] For example, a pusch-TDRA list including multiple PUSCH-Allocation-r16 (parameter sets) may be notified (or configured) from base station 200 to terminal 100 as RRC control information.

[0056] Furthermore, which parameter set included in the pusch-TDRA list (or an entry in the pusch-TDRA list) is to be used by the terminal 100 may be notified from the base station 200 to the terminal 100 by, for example, DCI. For example, which parameter set (or an entry in the pusch-TDRA list) is to be used by the terminal 100 may be notified to the terminal 100 in, for example, a Time domain resource assignment field using 4 bits of DCI format 0_0 or 0 to 6 bits (bits determined by settings or conditions) of DCI format 0_1.

[0057] In the present embodiment, base station 200 includes OCC sequence length candidates in SIB or RRC control information and notifies terminal 100. Furthermore, base station 200 includes the OCC sequence length (e.g., one of multiple OCC sequence length candidates) and OCC sequence number used by terminal 100 in DCI and notifies terminal 100.

[0058] Here, candidates for the OCC sequence length may be reported to terminal 100 by, for example, a pusch-TDRA list. For example, PUSCH-Allocation-r16 included in the pusch-TDRA list may include the OCC sequence length (for example, parameter name "OCClength") as follows: OCClength ENUMERATED {n2, n4, n8}

[0059] In the above example, OCC sequence lengths of 2, 4, and 8 can be set in terminal 100.

[0060] For example, a case will be described in which OCC sequence lengths 2 and 4 are candidates, and the OCC sequence length to be used in terminal 100 of the two candidate OCC sequence lengths is notified to terminal 100 by DCI. In this case, a parameter set including (n2, n4) as the OCC length is included in the pusch-TDRA list and notified (configured) to terminal 100 by RRC control information. Terminal 100 is then notified by DCI of which of the parameter sets including n2 and n4 to use as the OCC length in terminal 100 (information indicating one of multiple candidate OCC sequence lengths).

[0061] Furthermore, an OCC sequence length including OCC sequence length 1 may be set in PUSCH-Allocation-r16. Then, when OCC sequence length 1 is indicated by DCI, terminal 100 may transmit a PUSCH without using an OCC. This makes it possible to dynamically (for example, for each slot) switch between transmission multiplexed with other terminals using an OCC and transmission not multiplexed with other terminals using an OCC.

[0062] In this way, base station 200 notifies (configures) OCC sequence length candidates to terminal 100 using RRC control information (e.g., upper layer signaling, upper layer parameters), and notifies OCC information corresponding to one of the OCC sequence length candidates (e.g., the OCC sequence length actually used by terminal 100) using DCI. This allows base station 200 to dynamically notify terminal 100 using DCI of information indicating one of multiple OCC sequence length candidates (e.g., information (number, index) identifying multiple candidates), thereby enabling flexibly setting the OCC sequence length while suppressing an increase in the amount of DCI information (number of bits).

[0063] Also, for example, in the case of inter-slot OCC, the OCC is used together with PUSCH repetition and multiplied on a slot-by-slot basis. Therefore, the OCC sequence length can be set to be equal to or less than the number of repetitions. In this embodiment, by using a pusch-TDRA list to signal the OCC sequence length, it becomes possible to configure, as a parameter set, terminal 100 with only an OCC sequence length (e.g., OCClength) that is equal to or less than the number of repetitions (e.g., parameter name "numberOfRepetitions-r16"). This reduces the amount of information to be signaled compared to when the number of repetitions and the OCC sequence length are configured independently for terminal 100.

[0064] For example, a rule for setting an OCC sequence length equal to or less than the repetition number (e.g., the number of times a PUSCH is repeated) may be defined. For example, when an OCC sequence length equal to or less than the repetition number (e.g., a threshold) is notified to terminal 100, terminal 100 may decide to transmit a PUSCH to which the notified OCC is applied, and when an OCC sequence length greater than the repetition number is notified to terminal 100, terminal 100 may ignore the notified information and decide not to transmit a PUSCH.

[0065] Alternatively, for example, base station 200 may implicitly report the OCC sequence length by reporting the repetition count, and terminal 100 may use the OCC sequence length associated with the reported repetition count. For example, possible OCC sequence lengths may be set in advance according to the repetition count, such that an OCC sequence length of 2 is set when the repetition count is 2, and an OCC sequence length of 4 is set when the repetition count is 4 or greater. This reduces the amount of information required to report the OCC sequence length. Alternatively, for example, the relationship between the repetition count and the OCC sequence length may be reported to terminal 100 using SIB or RRC control information so that it can be set according to the propagation environment or operational status.

[0066] Furthermore, a rule for setting an OCC sequence length associated with the TDW of DMRS bundling may be specified. Terminal 100 configured with DMRS bundling performs transmission while ensuring power and phase continuity in slots within the TDW in order to perform channel estimation by combining DMRSs of multiple slots. Furthermore, since both OCC and DMRS bundling are expected to maintain power and phase continuity in terminal 100 for the number of slots of the OCC sequence length and the TDW, it is also possible to explicitly report either the OCC sequence length or the TDW (e.g., report the TDW), and implicitly report information on the other (e.g., the OCC sequence length).

[0067] For example, a rule for setting an OCC sequence length equal to or less than the TDW may be defined. For example, when an OCC sequence length equal to or less than the TDW (e.g., a threshold) is set in terminal 100, terminal 100 may decide to transmit a PUSCH to which the notified OCC is applied, and when an OCC sequence length greater than the TDW is set in terminal 100, terminal 100 may ignore the notified information and decide not to transmit a PUSCH.

[0068] Alternatively, for example, base station 200 may implicitly report the OCC sequence length by reporting the TDW, and terminal 100 may use an OCC sequence length associated with the reported TDW (e.g., an OCC sequence length the same as the TDW). For example, if the TDW is two slots, an OCC sequence length of 2 may be set, and if the TDW is four slots or more, an OCC sequence length of 4 may be set. This reduces the amount of information reporting the OCC sequence length. Furthermore, the relationship between the TDW and the OCC sequence length may be reported to terminal 100 by SIB or RRC control information so that it can be set according to the propagation environment or operation status.

[0069] Furthermore, for example, a rule for setting an OCC sequence length associated with the number of TBoMS slots may be defined. For example, an OCC sequence length of 2 may be set when the number of TBoMS slots is 2, and an OCC sequence length of 4 may be set when the number of TBoMS slots is 4 or greater. Applying OCC reduces the number of information bits (transport block (TB) size) that can be transmitted within a slot compared to when OCC is not applied. However, by using the same number of TBoMS slots as the OCC sequence length, terminal 100 can transmit data of approximately the same TB size as when OCC is not applied. By associating the number of TBoMS slots with the OCC sequence length, it is only necessary to report either the number of TBoMS slots or the OCC sequence length, thereby reducing the amount of information to be reported.

[0070] [Method of Notifying OCC Sequence (OCC Sequence Number)] Next, a method of notifying an OCC sequence number (information for identifying an OCC sequence) will be described.

[0071] <OCC Sequence Notification Method 1> Similar to the above-described method of notifying OCC sequence length, base station 200 notifies (or sets) candidates for OCC sequence numbers to terminal 100 by using RRC control information (e.g., a pusch-TDRA list). Furthermore, base station 200 notifies terminal 100 of the OCC sequence number used by terminal 100 (e.g., one of the candidate OCC sequence numbers) by including it in DCI.

[0072] For example, in the pusch-TDRA list, the OCC sequence number may be included in the parameter set PUSCH-Allocation-r16 as a parameter (e.g., parameter name "OCCsequence") independent of the OCC sequence length (e.g., OCClength) as follows: OCCsequence INTEGER (0 … 7)

[0073] Alternatively, for example, in the pusch-TDRA list, the OCC sequence number may be included in the parameter set PUSCH-Allocation-r16 as a parameter combined with the OCC sequence length (for example, a common parameter (for example, parameter name "OCClengthAndSequence")) as follows: OCClengthAndSequence ENUMERATED {OCClen2-seq0, OCClen2-seq1, OCClen4-seq0, OCClen4-seq1, OCClen4-seq2, OCClen4-seq3}

[0074] OCC sequence notification method 1 can reduce the amount of information to be notified of the OCC sequence.

[0075] <OCC Sequence Reporting Method 2> Base station 200 reports an OCC sequence number in DCI (for example, in a predetermined field within DCI).

[0076] The field in the DCI that reports the OCC sequence number may be a newly defined field for reporting the OCC sequence number, or may be an existing field (e.g., a reuse of a field for reporting a parameter different from the OCC sequence number).

[0077] When reusing existing fields, at least a portion of the notification field or bits of a parameter that is unlikely to be used in an environment where OCC application is effective, such as NTN, may be used (reused) to notify the OCC sequence number.

[0078] For example, fields used to notify the OCC sequence number include the MCS field, the frequency resource allocation field, and the frequency hopping flag field.

[0079] For example, since OCC is applied together with repetition, it is expected to be used in poor propagation environment situations (e.g., situations where reception quality (e.g., SNR: Signal to Noise Ratio) is low). For this reason, when OCC is applied, a higher MCS (e.g., a higher modulation level or a higher coding rate) is less likely to be used. For this reason, only a low MCS (e.g., an MCS equal to or lower than a threshold) may be reported, and a high MCS (e.g., an MCS higher than a threshold) may not be reported. In this case, the OCC sequence number may be reported using the remaining bits (e.g., part of the MCS field) other than the bits used to report the low MCS.

[0080] Furthermore, for example, due to an upper limit on the transmittable power of terminal 100, the wider the bandwidth (e.g., the more resource blocks (RBs)) used in transmission, the lower the transmission power per bandwidth (PSD: Power Spectral Density). For this reason, in long-distance transmission such as NTN, transmission with increased transmission power per bandwidth is expected, and many RBs are unlikely to be used for transmission. For this reason, the frequency resource allocation field may be capable of notifying only allocations of a small number of RBs (e.g., a number of RBs equal to or less than a threshold), and allocations of a large number of RBs (e.g., a number of RBs greater than a threshold) may not be notified. In this case, the OCC sequence number may be notified using the remaining bits (e.g., part of the frequency resource allocation field) other than the bits used to notify the small number of RBs.

[0081] Furthermore, for example, since the propagation paths of distant frequencies may be different, when frequency hopping is performed, in the case of inter-slot OCC, the orthogonality of the OCC may be lost. For this reason, when OCC is applied, frequency hopping is unlikely to be used. For this reason, for example, when OCC is applied, a setting may be made such that frequency hopping is not applied, and the OCC sequence number may be notified using a frequency hopping field.

[0082] Furthermore, the OCC sequence number may be signaled using other existing fields, without being limited to the above-described fields. For example, the granularity of the signaling information in other fields may be reduced (e.g., the number of bits used for signaling may be reduced), and the OCC sequence number may be signaled using part of the other fields. Furthermore, OCC sequence information may be signaled by combining multiple fields.

[0083] Furthermore, when the use (application) of OCC is notified by RRC control information or DCI, the above field may be read as a notification field of the OCC sequence number.

[0084] <OCC Sequence Reporting Method 3> An OCC sequence number and a DMRS port number (information for identifying a DMRS port) may be associated in advance. In this case, base station 200 reports the OCC sequence number implicitly using the DMRS port number reported in control information (e.g., DCI). Terminal 100 identifies the OCC sequence number based on the DMRS port number included in the control information (e.g., DCI).

[0085] For example, the DMRS port number may be notified by the antenna port field of DCI format 0_1 ​​or 0_2.

[0086] For example, OCC sequence n may be associated with DMRS port n as follows: The association between DMRS port numbers and OCC sequence numbers may be defined in a specification (standard), or may be notified (or set) to terminal 100 by SIB or RRC control information. DMRS port 0: OCC sequence 0 DMRS port 1: OCC sequence 1 DMRS port 2: OCC sequence 2 DMRS port 3: OCC sequence 3

[0087] Also, a DMRS port number and an OCC sequence number may be associated with each value of the antenna port field. For example, the values ​​of the antenna port field and the corresponding DMRS port numbers and OCC sequence numbers may be defined in a specification (standard) as follows, and may be notified (or set) to terminal 100 by SIB or RRC control information: 0: DMRS port 0, OCC sequence 0 1: DMRS port 1, OCC sequence 1 2: DMRS port 2, OCC sequence 2 3: DMRS port 3, OCC sequence 3

[0088] For example, applying OCCs with different sequences (numbers) to multiple terminals 100 enables multiplexing transmission between different terminals using the same time / frequency resources. Here, since OCCs are not applied to DMRSs, it is desirable to assign DMRSs with different sequences or resources to different terminals that perform OCC multiplexing. For example, DMRSs with different sequences or resources are defined by DMRS ports. Therefore, it is expected that different DMRS ports will be notified to different terminals 100. Therefore, as described above, by previously associating OCC sequence numbers with DMRS port numbers and notifying different terminals 100 of different DMRS ports, it becomes possible to notify different terminals 100 of different OCC sequence numbers. This eliminates the need for OCC sequence number notification bits, making it possible to reduce the amount of control information.

[0089] [DMRS Port Number Notification Method] Next, a DMRS port number notification method will be described.

[0090] <DMRS Notification Method 1> Base station 200 notifies the DMRS port number by including it in DCI (for example, antenna port field). Terminal 100 identifies the DMRS port number based on, for example, the DCI.

[0091] For example, the antenna port number defined in the antenna port field may be associated with a DMRS port number. For example, terminals notified of different antenna port numbers use different DMRS ports (e.g., different DMRS sequences or DMRS resources).

[0092] <DMRS Signaling Method 2> DMRS port numbers and OCC sequence numbers may be associated in advance. In this case, base station 200 implicitly signals the DMRS port number using the OCC sequence number signaled by control information (e.g., DCI). Terminal 100 identifies the DMRS port number based on the OCC sequence number included in the control information (e.g., DCI).

[0093] For example, DMRS port n may be associated with OCC sequence n as follows: The association between OCC sequence numbers and OCC sequence numbers may be defined in a specification (standard), or may be notified (or set) to terminal 100 by SIB or RRC control information. OCC sequence 0: DMRS port 0 OCC sequence 1: DMRS port 1 OCC sequence 2: DMRS port 2 OCC sequence 3: DMRS port 3

[0094] Furthermore, an OCC sequence number and a DMRS port number may be associated with each value of the field that reports an OCC sequence. For example, the values ​​of the OCC sequence reporting field and the corresponding OCC sequence numbers and DMRS port numbers may be defined in a specification (standard) as follows, and may be reported (or set) to terminal 100 by SIB or RRC control information: 0: OCC sequence 0, DMRS port 0 1: OCC sequence 1, DMRS port 1 2: OCC sequence 2, DMRS port 2 3: OCC sequence 3, DMRS port 3

[0095] This allows different terminals 100 to be notified of different OCC sequences without using DMRS port notification information, thereby allowing terminals 100 that multiplex PUSCHs with OCC applied to use different DMRSs, thereby reducing the overhead of control information.

[0096] Furthermore, for example, although DCI format 0_0 does not have a field for indicating a DMRS port, base station 200 can implicitly indicate different DMRS ports between terminals using DCI format 0_0 by indicating different OCC sequences to different terminals 100 without adding a DMRS port indication field.

[0097] <DMRS Signaling Method 3> Base station 200 combines DMRS signaling method 1 and DMRS signaling method 2 described above to signal a DMRS port number and an OCC sequence number.

[0098] For example, in control information (e.g., DCI), a portion of the information on the DMRS port number may be notified in the OCC sequence number notification field, and the remaining information on the DMRS port number may be notified in the DMRS port number (or antenna port number) notification field.

[0099] For example, in the case of 2-bit DMRS port information, the OCC sequence number notification field may notify the first bit of information of the DMRS port number (e.g., either the first half (0 / 1) or the second half (2 / 3) of the DMRS port number (e.g., 0 to 3)). Also, for example, the DMRS port number notification field may notify the second bit of information of the DMRS port number (e.g., either an even number (e.g., 0 or 2) or an odd number (1 or 3)). Note that the DMRS port information notified in the OCC sequence number notification field and the DMRS port number notification field may be reversed (the first and second bits may be reversed).

[0100] By different terminals 100 using the same OCC sequence number but different DMRS port numbers, transmission can be performed using MU-MIMO (Multi-User MIMO) using the same OCC sequence, thereby improving system capacity.

[0101] Note that a portion of the OCC sequence number information (e.g., the first bit in the case of a 2-bit OCC sequence number) may be reported in the DMRS port notification field, and the remaining OCC sequence number information (e.g., the second bit in the case of a 2-bit OCC sequence number) may be reported in the OCC sequence number notification field. Note that the OCC sequence number information reported in the DMRS port notification field and the OCC sequence number notification field may be reversed (the first bit and the second bit may be reversed).

[0102] The above describes examples of methods for reporting OCC sequence lengths, OCC sequence numbers, and DMRS ports.

[0103] The method of reporting the OCC sequence number and DMRS port number is not limited to the above-described reporting method, and other reporting methods may be used. For example, the OCC sequence number and DMRS port number may be reported to terminal 100 by individual RRC control information. Base station 200 may multiplex and transmit signals between terminals with different OCC sequence numbers and DMRS port numbers using OCC.

[0104] Furthermore, the DMRS port number may be implicitly signaled by, for example, time-frequency resources (e.g., CCE (Control Channel Element) numbers or search spaces) of a control channel (e.g., PDCCH) to which a PUSCH is allocated. Since PDCCH resources to which a PUSCH is allocated differ for different terminals 100, it becomes possible to signal a different DMRS port for each terminal 100 without additional control information.

[0105] Similarly, the OCC sequence number may be implicitly signaled by, for example, time-frequency resources (e.g., CCE numbers or search spaces) of a control channel (e.g., PDCCH) that allocates a PUSCH. Because PDCCH resources that allocate PUSCHs to different terminals 100 are different, it is possible to signal a different OCC sequence number for each terminal 100 without additional control information.

[0106] Note that any combination of the above-described methods of reporting the OCC sequence length, OCC sequence number, and DMRS port may be used.

[0107] As described above, in the present embodiment, terminal 100 receives RRC control information or MAC CE control information including information on multiple OCC sequence length candidates, and DCI including OCC information (e.g., an OCC sequence number and an OCC sequence) corresponding to one of the multiple OCC sequence length candidates, and controls transmission of a PUSCH to which an OCC is applied based on the received information. In this way, information on the OCC applied to PUSCH transmission (e.g., the OCC sequence length and the OCC sequence) is appropriately reported from base station 200 to terminal 100.

[0108] Furthermore, in this embodiment, in addition to information about the OCC, information about the DMRS port is explicitly or implicitly reported from base station 200 to terminal 100. This makes it possible to apply different DMRS ports between terminals.

[0109] Therefore, according to this embodiment, the upstream signal can be transmitted appropriately.

[0110] The notification of terminal capability (UE capability) may be a notification that terminal 100 that supports OCC also supports repetition, or a notification that base station 200 can assume that terminal 100 that supports OCC supports repetition. Furthermore, the notification of terminal capability may be a notification that terminal 100 that supports OCC also supports DMRS bundling, or a notification that base station 200 can assume that terminal 100 that supports OCC supports DMRS bundling.

[0111] Here, it may be assumed that the OCC sequence length and the TDW of DMRS bundling supported by terminal 100 are the same. For both OCC and DMRS bundling, terminal 100 is expected to maintain power and phase continuity for only the number of slots of the OCC sequence length and the TDW. Therefore, by reporting one of the OCC sequence length and the number of slots of the TDW (e.g., the TDW), the terminal capability of the other (e.g., the OCC sequence length) can be estimated, which makes it possible to reduce the amount of information to be reported.

[0112] Furthermore, for example, when terminal 100 receives an SIB indicating that PUSCH using OCC is supported in the serving cell and terminal 100 notifies that it supports OCC as a terminal capability, the notification of the OCC sequence length, OCC sequence number, and DMRS port number may be considered valid.

[0113] In addition, in the above embodiment, a case where OCC is applied to PUSCH has been described, but the channel or signal to which OCC is applied is not limited to PUSCH and may be other channels or signals. For example, OCC may be applied to PUCCH or SRS. Furthermore, OCC may be applied to PDSCH or PDCCH of DL.

[0114] Furthermore, in the above-described embodiment, a case has been described in which the OCC sequence length, the OCC sequence number, or the DMRS port number is notified by DCI (PDCCH), but this is not limiting. For example, at least one of the OCC sequence length, the OCC sequence number, and the DMRS port number may be notified by MAC CE or RRC control information. Furthermore, for example, when OCC is applied to a Configured Grant (CG) PUSCH, information on the OCC sequence length, the OCC sequence number, and the DMRS port number may be notified by RRC control information that notifies parameters such as the periodicity of the CG-PUSCH, or by MAC CE or PDCCH for activation. Furthermore, in CG-PUSCH type 1, information on the OCC sequence length, OCC sequence number, and DMRS port number may be included in RRC control information and signaled, and in CG-PUSCH type 2, information on the OCC sequence length, OCC sequence number, and DMRS port number may be signaled by including it in RRC control information (e.g., PUSCH-Aggergation-r16 or TDRA list), and information on the OCC sequence length, OCC sequence number, and DMRS port number may be signaled by MAC CE or PDCCH for activation. Similarly, when OCC is applied to a PDSCH for semi-persistent scheduling (SPS), information on the OCC sequence length, OCC sequence number, and DMRS port number may be signaled by RRC control information that signals parameters such as the periodicity of the SPS PDSCH, or by MAC CE or PDCCH for activation.

[0115] (Explanation of OCC Application Options) Furthermore, the following three types of methods for applying OCC to PUSCH (for example, OCC multiplication methods) have been considered, and an embodiment of the present disclosure can be applied to any of these methods. The three OCC application methods will be described below.

[0116] Although the present disclosure will be described here with reference to a case where DFT-s-OFDM modulation is performed on an uplink PUSCH, it is also applicable to, for example, CP (Cyclic Prefix)-OFDM or single-carrier transmission. Furthermore, OCC sequences include Walsh sequences, DFT sequences, and cyclic shift sequences, and an embodiment of the present disclosure can be applied to any of these sequences.

[0117] For example, the sequence described below may be used.

[0118] sequence length n OCC The OCC sequence m is expressed by the following equation (see, for example, TS38.211 V15.10.0 Table 6.3.2.4.1-2):

[0119] However, ψ(m) may be set to a value in the table shown in FIG. OCC When =4, there are four OCC sequences: [1 1 1 1], [1 -1 1 -1], [1 1 -1 -1], and [1 -1 -1 1].

[0120] 6, terminal 100 performs modulation such as QPSK or 16QAM on a transmission data bit sequence, performs DFT (DFT-s-OFDM modulation), maps the result to frequency resources, and then performs IFFT to generate OFDM symbols (or DFT-s-OFDM symbols). Terminal 100 then forms slots in which the generated OFDM symbols and RS signals (e.g., DMRS and SRS) are allocated.

[0121] In inter-slot OCC, terminal 100 performs OCC multiplication on a slot-by-slot basis. That is, terminal 100 multiplies the same OCC sequence within a slot. For example, as shown in FIG. 6 , terminal 100 multiplies RV0 data mapped to one slot by the OCC sequence length n OCC (In the example of Figure 6, n OCC = 4), and the OCC sequence w k ((k=1,2,.., n OCC ) is multiplied.

[0122] Furthermore, when OCC is applied, the terminal 100 may use TBoMS. In this case, the terminal 100 may perform the same process for multiple slots corresponding to TBoMS.

[0123] <Inter-OFDM Symbol OCC> As shown in Fig. 7, the terminal 100 performs modulation such as QPSK or 16QAM on a transmission data bit string, performs DFT (DFT-s-OFDM modulation), maps the bit string to frequency resources, and then performs IFFT to generate OFDM symbols (or DFT-s-OFDM symbols). Then, as shown in Fig. 7, the terminal 100 divides the generated OFDM symbol string (hereinafter also referred to as "OFDM symbol block") into n OCC times, and the OCC sequence w k (k=1,2,.., n OCC ) where n OCC is the OCC sequence length.

[0124] Here, the case where an OFDM symbol sequence is repeated in the OCC between OFDM symbols (in the example of FIG. 7, an OFDM symbol sequence including three OFDM symbols is repeated four times) has been described, but the present invention is not limited to this. For example, the terminal 100 may repeat each OFDM symbol n OCC For example, in the example of Fig. 7, terminal 100 may perform the process of multiplying each OFDM symbol by the OCC sequence four times for three OFDM symbols, thereby generating a total of 12 symbols of data.

[0125] Then, terminal 100 forms slots in which the generated OFDM symbols and RS signals (for example, DMRS and SRS) are allocated.

[0126] Furthermore, the terminal 100 may use TBoMS when OCC is applied. In this case, the terminal 100 may perform the same process for multiple slots corresponding to TBoMS. For example, the terminal 100 may perform the same process for a sequence length n OCC When using the OCC sequence of n OCCDo the same for slot n OCC The slot is used to transmit the TB.

[0127] <OCC in OFDM Symbol> After modulating the transmission data bit string using QPSK, 16QAM, or the like, the terminal 100 divides the generated symbol string (hereinafter also referred to as "symbol block") into n OCC times, and the OCC sequence w k (k=1,2,..,n OCC ) where n OCC is the OCC sequence length.

[0128] Then, the terminal 100 generates OFDM symbols (or DFT-s-OFDM symbols) by performing DFT (DFT-s-OFDM modulation), mapping to frequency resources, and then performing IFFT.The terminal 100 then forms slots in which the generated OFDM symbols and RS signals (e.g., DMRS and SRS) are allocated.

[0129] Furthermore, the terminal 100 may use TBoMS when OCC is applied. In this case, the terminal 100 may perform the same process for multiple slots corresponding to TBoMS. For example, the terminal 100 may perform the same process for a sequence length n OCC When using the OCC sequence of n OCC Do the same for slot n OCC The slot is used to transmit the TB.

[0130] The above describes an example of how to apply OCC.

[0131] Although the above description is directed to an example in which an OCC sequence number is used as information for identifying an OCC sequence, the information for identifying an OCC sequence is not limited to this and may be other information. For example, the information for identifying an OCC sequence may be information related to a cyclic shift amount or a value used in sequence generation.

[0132] Furthermore, OCC may be interpreted as an orthogonal code, a spreading code, a spreading sequence, a spreading code, etc. Furthermore, OCC sequence length may be interpreted as a spreading factor, a spreading code length, etc. Furthermore, the code used for multiplexing signals between terminals is not limited to OCC, and other orthogonal codes may be used. Furthermore, the OCC sequence may be a sequence such as a cyclic shift sequence.

[0133] Furthermore, the loss of orthogonality may be interpreted as inter-code interference.

[0134] The transmission unit may be a slot, a frame, or a symbol. When TBoMS is applied, a TBoMS slot, which is a group of multiple slots, may be used as the transmission unit instead of a slot.

[0135] The OCC sequence length may be interpreted as the time interval (OCC application interval) during which multiplication by one OCC sequence is applied.

[0136] An embodiment of the present disclosure can be applied to both mapping type A, which is allocation in slot units, and mapping type B, which is allocation in symbol units. Also, the repetition can be applied to both type A and type B.

[0137] The control information regarding the OCC may include information regarding the OCC application method (inter-slot, inter-symbol, intra-symbol).

[0138] Furthermore, the present disclosure is not limited to the case where OCC is applied to PUSCH, and may also be applied to the case where OCC is applied to DMRS.

[0139] Furthermore, the base station may be read as a network or a RAN (Radio Access Network).

[0140] Furthermore, the above embodiment may be applied to networks other than NTN.

[0141] An embodiment of the present disclosure can be used for different types of satellite communications, such as Low Earth Orbit satellites (LEO), Medium Earth Orbit satellites (MEO), Highly Elliptical Orbit satellites (HEO), or Geostationary Earth Orbit satellites (GEO), which are located at different altitudes above the Earth's surface.

[0142] In each of the above-described embodiments, satellite ephemeris information, which is information related to satellite positions, may be reported by system information or may be stored in advance by the terminal 100. Furthermore, the satellite ephemeris information may be updated when communication is possible. Furthermore, the terminal 100 may identify satellite positions using information other than the satellite ephemeris information.

[0143] In the above-described embodiments, examples have been described in which GNSS such as GPS (for example, position detection using satellite signals) is used, but the present invention is not limited to this. For example, position detection may be performed using a terrestrial cellular base station, a Wi-Fi (registered trademark) signal or a Bluetooth (registered trademark) signal, an acceleration sensor, or a combination of these detection methods. Furthermore, altitude information may be obtained from a barometric pressure sensor, etc.

[0144] In the above-described embodiments, "report" may be read as "notification," and "notification" may be read as "report." "Calculation" may be read as "determination" or "generation."

[0145] Furthermore, in each of the above-described embodiments, the transmission of an uplink signal from a terminal to a base station has been described, but the present invention may also be applied to the transmission of a downlink signal from a base station to a terminal.

[0146] An embodiment of the present disclosure may be applied regardless of the type of satellite, such as GEO, MEO, LEO, or HEO. Furthermore, an embodiment of the present disclosure may be applied to non-terrestrial communications, such as HAPS or drone base stations.

[0147] Although the above-described embodiment has been described using an NTN environment (e.g., a satellite communication environment) as an example, the present disclosure is not limited thereto. The present disclosure may be applied to other communication environments (e.g., a terrestrial cellular environment of at least one of LTE and NR). For example, one embodiment of the present disclosure may be applied to terrestrial communications in an environment where the cell size is large and the propagation delay between the base station 200 and the terminal 100 is longer (e.g., above a threshold).

[0148] In the above-described embodiment, the satellite communication may be in the form of a configuration in which the base station functions are located on a satellite (e.g., a "regenerative satellite"), or a configuration in which the base station functions are located on the ground and a satellite relays communication between the base station and a terminal (e.g., a "transparent satellite"). For example, in one embodiment of the present disclosure, the downlink and the uplink may be links between a terminal and a satellite, or links via a satellite.

[0149] The method of notifying the control information from the base station 200 to the terminal 100 is not limited to the above-mentioned example, and may be notified (or reported, indicated, or set) by at least one of system information such as MIB and SIB, RRC control information, MAC control information, and downlink control information (DCI), or may be pre-set in the terminal 100 or may be pre-defined in a standard.

[0150] The base station may be referred to as a gNodeB or a gNB, and the terminal may be referred to as a UE.

[0151] The time resource units such as symbols and slots may be replaced with system frames, time slots, minislots, frames, subframes, and the like.

[0152] Furthermore, parameters such as the OCC sequence length, the OCC sequence number, the time interval to which the OCC is applied (for example, the number of slots), and the DMRS port number are not limited to the above examples, and may be other values.

[0153] Furthermore, the notation "... section" in the above-described embodiments may be replaced with other notations such as "... circuitry," "... device," "... unit," or "... module."

[0154] (Supplementary Note) Information indicating whether the terminal 100 supports the functions, operations, or processes described in the above-described embodiments may be transmitted (or notified) from the terminal 100 to the base station 200, for example, as capability information or capability parameters of the terminal 100.

[0155] The capability information may include an information element (IE) that individually indicates whether or not the terminal 100 supports at least one of the functions, operations, or processes described in the above-described embodiments. Alternatively, the capability information may include an information element that indicates whether or not the terminal 100 supports a combination of any two or more of the functions, operations, or processes described in the above-described embodiments.

[0156] For example, the base station 200 may determine (or decide or assume) the functions, operations, or processes that the terminal 100 that transmitted the capability information supports (or does not support) based on the capability information received from the terminal 100. The base station 200 may perform operations, processes, or controls according to the determination result based on the capability information. For example, the base station 200 may control communications based on the capability information received from the terminal 100.

[0157] Note that the fact that the terminal 100 does not support some of the functions, operations, or processes described in the above-described embodiments may be interpreted as meaning that such some of the functions, operations, or processes are restricted in the terminal 100. For example, information or a request regarding such restrictions may be notified to the base station 200.

[0158] Information regarding the capabilities or limitations of the terminal 100 may, for example, be defined in a standard, or may be implicitly notified to the base station 200 in association with information known at the base station 200 or information transmitted to the base station 200.

[0159] (Control Signal) In the present disclosure, a downlink control signal (or downlink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a Physical Downlink Control Channel (PDCCH) of a physical layer, or a signal (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) of a higher layer. Furthermore, the signal (or information) is not limited to being notified by a downlink control signal, but may be predefined in a specification (or standard) or preconfigured in a base station and a terminal.

[0160] In the present disclosure, an uplink control signal (or uplink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a PUCCH of a physical layer, or a signal (or information) transmitted in a MAC CE or RRC of a higher layer. Furthermore, the signal (or information) is not limited to being notified by an uplink control signal, but may be predefined in a specification (or standard) or preconfigured in a base station and a terminal. Furthermore, the uplink control signal may be replaced with, for example, uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.

[0161] (Base Station) In an embodiment of the present disclosure, the base station may be a Transmission Reception Point (TRP), a cluster head, an access point, a Remote Radio Head (RRH), an eNodeB (eNB), a gNodeB (gNB), a Base Station (BS), a Base Transceiver Station (BTS), a parent device, a gateway, or the like. In sidelink communication, a terminal may play the role of a base station. Instead of a base station, a relay device that relays communication between an upper node and a terminal may be used. Alternatively, a roadside unit may be used.

[0162] (Uplink / Downlink / Sidelink) An embodiment of the present disclosure may be applied to, for example, any of the uplink, downlink, and sidelink. For example, an embodiment of the present disclosure may be applied to a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), or a Physical Random Access Channel (PRACH) in the uplink, a Physical Downlink Shared Channel (PDSCH), a PDCCH, or a Physical Broadcast Channel (PBCH) in the downlink, or a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Control Channel (PSCCH), or a Physical Sidelink Broadcast Channel (PSBCH) in the sidelink.

[0163] The PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel, respectively. The PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. The PBCH and PSBCH are examples of a broadcast channel, and the PRACH is an example of a random access channel.

[0164] (Data Channel / Control Channel) An embodiment of the present disclosure may be applied to, for example, either a data channel or a control channel. For example, the channel in an embodiment of the present disclosure may be replaced with any of the data channels PDSCH, PUSCH, and PSSCH, or the control channels PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0165] (Reference Signal) In one embodiment of the present disclosure, a reference signal is, for example, a signal known by both a base station and a mobile station, and may also be called a Reference Signal (RS) or a pilot signal. The reference signal may be any of a Demodulation Reference Signal (DMRS), a Channel State Information - Reference Signal (CSI-RS), a Tracking Reference Signal (TRS), a Phase Tracking Reference Signal (PTRS), a Cell-specific Reference Signal (CRS), or a Sounding Reference Signal (SRS).

[0166] (Time Interval) In one embodiment of the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may be, for example, a time resource unit such as a frame, a superframe, a subframe, a slot, a time slot, a subslot, a minislot, a symbol, an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier-Frequency Division Multiplexing Access (SC-FDMA) symbol, or another time resource unit. Furthermore, the number of symbols included in one slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be another number of symbols.

[0167] (Frequency Band) An embodiment of the present disclosure may be applied to either a licensed band or an unlicensed band.

[0168] (Communication) An embodiment of the present disclosure may be applied to communication between a base station and a terminal (Uu link communication), communication between terminals (Sidelink communication), or Vehicle to Everything (V2X) communication. For example, the channel in an embodiment of the present disclosure may be replaced with any of PSCCH, PSSCH, Physical Sidelink Feedback Channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, or PBCH.

[0169] An embodiment of the present disclosure may be applied to a terrestrial network, a non-terrestrial network (NTN) using a satellite or a high altitude pseudo satellite (HAPS), or a terrestrial network in which transmission delay is large compared to the symbol length or slot length, such as a network with a large cell size or an ultra-wideband transmission network.

[0170] (SBFD) In ​​one embodiment of the present disclosure, operations on uplink, downlink, and sidelink symbols may be applied to symbols (e.g., SBFD symbols) on which SBFD (Subband Non-Overlapping Full Duplex, Subband Full Duplex) operations or controls are performed. In SBFD symbols, a frequency domain (or frequency resource, frequency band) is divided into multiple frequency domains (e.g., subbands, RB sets, subbands, or sub-BWPs (Bandwidth Parts)). A terminal transmits and receives in different directions (e.g., downlink or uplink) in units of subbands, which are the divided domains. In SBFD symbols, a terminal may transmit and receive in one direction, either uplink or downlink, but not in the other direction. On the other hand, a base station may be capable of transmitting and receiving on both the uplink and downlink simultaneously. SBFD symbols may have a smaller frequency domain available for downlink transmission than symbols that transmit and receive only downlink transmission. Also, SBFD symbols may have a smaller frequency domain available for uplink transmission than symbols that transmit and receive only uplink transmission.

[0171] In addition, in the SBFD symbol, a terminal may transmit and receive uplink and downlink simultaneously. In this case, the frequency domain in which the terminal transmits and the frequency domain in which the terminal receives may not be adjacent, but may be separated by a frequency interval (also called a frequency gap).

[0172] In addition, different transmission and reception directions in subband units, which are divided areas, may include transmission and reception of side links.

[0173] (XDD: Cross Division Duplex) In one embodiment of the present disclosure, the operation for uplink, downlink, and sidelink symbols may be applied to symbols (e.g., full duplex symbols) where full duplex operation or control is performed. In a full duplex symbol, both the terminal and the base station can simultaneously transmit and receive on the uplink and downlink. In a full duplex symbol, the terminal and the base station may simultaneously transmit and receive in an available frequency region (or frequency resource, frequency band), or may simultaneously transmit and receive in a partial frequency region (i.e., transmission or reception may be performed in other frequency regions). In this case, the frequency region in which the base station or terminal transmits and receives may not be adjacent, but may have a frequency interval (also called a frequency gap). Furthermore, for the purpose of, for example, reducing interference, either the terminal or the base station may simultaneously transmit and receive (i.e., the other may transmit or receive).

[0174] In addition, full duplex operation may be applied to an operation in which a terminal can simultaneously transmit and receive sidelinks, or to an operation in which a terminal can simultaneously transmit and receive sidelinks and uplinks or downlinks.

[0175] (Antenna Port) In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas. For example, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna consisting of multiple antennas. For example, the number of physical antennas that an antenna port is composed of is not specified, and the antenna port may be specified as the smallest unit by which a terminal station can transmit a reference signal. Furthermore, an antenna port may also be specified as the smallest unit by which a weighting of a precoding vector is multiplied.

[0176] <5G NR System Architecture and Protocol Stack> The 5G NR system architecture generally assumes an NG-RAN (Next Generation - Radio Access Network) including gNBs. The gNBs provide UE-side termination of the NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols. The gNBs are connected to each other via an Xn interface. The gNBs are also connected to the Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to the Access and Mobility Management Function (AMF) (e.g., a specific core entity that performs AMF) via an NG-C interface, and to the User Plane Function (UPF) (e.g., a specific core entity that performs UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 9 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0177] <RRC connection setup and reconfiguration procedure> This shows the NAS part of the interaction between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED (see TS 38.300 v15.6.0).

[0178] RRC is a higher layer signaling protocol used to configure the UE and gNB. The AMF prepares UE context data (including, for example, PDU session context, security keys, UE radio capabilities, UE security capabilities, etc.) and sends it to the gNB along with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding with a SecurityModeComplete message to the gNB. The gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the steps related to RRCReconfiguration are omitted because SRB2 and DRB are not set up. Finally, the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0179] Therefore, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) that includes: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, upon operation, transmits an initial context setup message to the gNodeB via the NG connection so that a signaling radio bearer between the gNodeB and a user equipment (UE) is set up. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, including a resource allocation configuration information element (IE), to the UE via the signaling radio bearer. The UE then transmits in uplink or receives in downlink based on the resource allocation configuration.

[0180] <QoS Control> The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (Guaranteed Bit Rate QoS flows (GBR)) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Thus, at the NAS level, a QoS flow is the finest granularity of QoS classification in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over the NG-U interface.

[0181] For each UE, 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes, for example, at least one Data Radio Bearer (DRB) for each PDU session. Additional DRBs for the QoS flows of that PDU session can be configured later (when this is up to the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0182] (Open-RAN) The base station described in each embodiment (for example, a 5G NR base station called a gNB) may be configured with three functional modules: a Centralized Unit (CU), a Distributed Unit (DU), and a Radio Unit (RU).

[0183] A CU may be referred to as a centralized node, aggregation node, central station, aggregation station, or centralized unit. A DU may be referred to as an O-RAN Distributed Unit (O-DU), distributed node, distributed station, or distributed unit. An RU may be referred to as an O-RAN Radio Unit (O-RU), radio equipment, radio node, radio station, antenna unit, or radio unit.

[0184] There are several split options for the functional split configuration (or functional split point) between CU, DU, and RU. The term "functional split point" is sometimes referred to as "split," "option," or "split option."

[0185] Examples of "division options" include the following division options 1 to 8. The functions of the base station described in each embodiment may be divided into a CU, a DU, and an RU by any of the following division options 1 to 8. For example, the CU, DU, and RU may be functionally divided, or the functions may be divided only between the CU and DU or only between the DU and RU. (1) Segmentation option 1: Between RRC (radio resource control) and PDCP (2) Segmentation option 2: Between PDCP and RLC (High-RLC) (3) Segmentation option 3: Between High-RLC and Low-RLC (4) Segmentation option 4: Between RLC (Low-RLC) and MAC (High-MAC) (5) Segmentation option 5: Between High-MAC and Low-MAC (6) Segmentation option 6: Between MAC (Low-MAC) and PHY (High-PHY) (7) Segmentation option 7: Between High-PHY and Low-PHY (8) Segmentation option 8: Between PHY (Low-PHY) and RF

[0186] The functional split point between the CU and O-DU may be split option 2. The section between the CU and O-DU is called midhaul, and the F1 interface is specified by 3GPP. The section between the O-DU and O-RU is called fronthaul, and the functional split point may be split option 7-2x, which is adopted as the O-RAN fronthaul specification.

[0187] Figure 10 shows an example of functional division of the gNB base station functions into CU, O-DU, and O-RU using Split Option 2 and Split Option 7-2x.

[0188] The CU may have, for example, a radio resource control (RRC) function, a service data adaptation protocol (SDAP) function, and a packet data convergence protocol (PDCP) function.

[0189] The O-DU may include, for example, a radio link control (RLC) function, a MAC function, and a higher physical layer (HIGH-PHY) function. The HIGH-PHY function may include an encoding function, a scrambling function, a modulation function, a layer mapping function, a precoding function, and a resource element (RE) mapping function for downlink (DL) transmission. The HIGH-PHY function may also include a decoding function, a descrambling function, a demodulation function, a layer demapping function, and a resource element (RE) demapping function for uplink (UL) reception.

[0190] The O-RU may have, for example, a LOW-PHY function and an RF function. The LOW-PHY function may also have, for downlink transmission, a beamforming function, an IFFT (Inverse First Fourier Transform) + CP (Cyclic Prefix) assignment function, and a D / A (Digital to Analog) conversion function. The LOW-PHY function may also have, for uplink reception, an A / D (Analog to Digital) conversion function, a CP removal + FFT (First Fourier Transform) function, and a beamforming function.

[0191] In addition, if the O-DU does not have a precoding function, the O-RU may have a precoding function.

[0192] The O-RU may have a function related to LBT (listen before talk). The evolving common public radio interface (eCPRI) is specified as the communication method between the O-DU and the O-RU in Split Option 7-2x. In Split Option 7-2x, eCPRI transmits and receives sampling sequences of the in-phase (I) and quadrature (Q) components of the OFDM signal in the frequency domain, as well as information used for beamforming in the antenna and time synchronization signals.

[0193] Information transmitted by the signals described in each embodiment (PDCCH, PUCCH, PDSCH, PUSCH, MAC CE, RRC, etc.) may be transmitted between the O-DU and the O-RU via the eCPRI User Plane (U-Plane) or Control Plane (C-Plane).

[0194] When the functions described in each embodiment are performed in the O-RU by functional division, the O-DU may control the O-RU by transmitting information for controlling the functions via a control signal (e.g., eCPRI) between the O-DU and the O-RU.

[0195] When the functions described in each embodiment are performed in the O-DU by functional division, the O-RU may receive the results of the functions performed in the O-DU via a control signal (e.g., eCPRI) and control the O-RU based on the received results.

[0196] The CU, O-DU, and O-RU may be deployed in physically different devices with their respective functions connected by optical fiber or the like, or some or all of their functions may be deployed in the same physical device.

[0197] The CU and O-DU may be logical entities implemented as software running on a server in the cloud or the like as a virtualized RAN (virtual Radio Access Network: vRAN). Also, some or all of the functions of the CU and O-DU may be provided as a virtualized network function (Network Functions Virtualization: NFV) service.

[0198] The transceiver does not have to be a radio transceiver, but may be, for example, a network transceiver, an optical transceiver, etc. The radio resources allocated by the O-DU may be resources for wireless communication between the O-RU and the UE.

[0199] The present disclosure can be realized in software, hardware, or software in conjunction with hardware.

[0200] Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may also be called an IC, system LSI, super LSI, or ultra LSI.

[0201] The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.

[0202] Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology may be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0203] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both functions. The radio transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0204] The communication devices are not limited to portable or mobile devices, but also include any kind of non-portable or fixed equipment, devices, and systems, such as smart home devices (such as home appliances, lighting equipment, smart meters or measuring devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0205] Communications include data communications via cellular systems, wireless LAN systems, communication satellite systems, and the like, as well as data communications via combinations of these.

[0206] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0207] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0208] A terminal according to one embodiment of the present disclosure includes a receiving circuit that receives first control information including information regarding multiple candidates for the sequence length of an orthogonal code and second control information including information regarding the orthogonal code corresponding to one of the multiple candidates for the sequence length, and a control circuit that controls transmission of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

[0209] In an embodiment of the present disclosure, the second control information includes information indicating any one of a plurality of candidates for the sequence length.

[0210] In one embodiment of the present disclosure, the control circuit determines to transmit the uplink signal when the sequence length of the orthogonal code specified by the first control information and the second control information is equal to or less than a threshold, and determines not to transmit the uplink signal when the sequence length of the orthogonal code specified by the first control information and the second control information is greater than the threshold.

[0211] In one embodiment of the present disclosure, the threshold is the number of repetitions of the uplink signal or a time domain window (TDW) of a demodulation reference signal (DMRS) bundling.

[0212] In one embodiment of the present disclosure, the first control information includes information regarding a plurality of candidates for the orthogonal code sequence, and the second control information includes information indicating any one of the plurality of candidates for the sequence.

[0213] In one embodiment of the present disclosure, the second control information includes information identifying a sequence of the orthogonal code.

[0214] In one embodiment of the present disclosure, the information identifying the sequence is included in at least a part of a field in the second control information for notifying a parameter different from the sequence.

[0215] In one embodiment of the present disclosure, the field is at least one of a Modulation and Coding Scheme (MCS) field, a frequency resource allocation field, and a frequency hopping flag field.

[0216] In one embodiment of the present disclosure, the information for identifying the sequence of the orthogonal code is associated with information for identifying a port of the demodulation reference signal.

[0217] In an embodiment of the present disclosure, the control circuit identifies the information for identifying the sequence based on information for identifying the port that is included in the second control information.

[0218] In an embodiment of the present disclosure, the control circuit identifies the information for identifying the port based on information for identifying the sequence that is included in the second control information.

[0219] In one embodiment of the present disclosure, the second control information includes information for identifying a port of a demodulation reference signal.

[0220] In one embodiment of the present disclosure, in the second control information, a field notifying information identifying the sequence of the orthogonal code includes a portion of the information identifying a port of the demodulation reference signal, and a field notifying information identifying the port includes the remaining information identifying the port.

[0221] In one embodiment of the present disclosure, in the second control information, a field notifying information identifying the sequence of the orthogonal code includes a portion of the information identifying the sequence, and a field notifying information identifying a port of the demodulation reference signal includes the remaining information identifying the sequence.

[0222] A base station according to one embodiment of the present disclosure includes a transmitting circuit that transmits first control information including information on multiple candidates for the sequence length of an orthogonal code and second control information including information on the orthogonal code corresponding to one of the multiple candidates, and a control circuit that controls reception of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

[0223] In a communication method according to one embodiment of the present disclosure, a terminal receives first control information including information regarding multiple candidates for the sequence length of an orthogonal code, and second control information including information regarding the orthogonal code corresponding to one of the multiple candidates for the sequence length, and controls transmission of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

[0224] In one embodiment of the present disclosure, a base station transmits first control information including information on multiple candidates for the sequence length of an orthogonal code, and second control information including information on the orthogonal code corresponding to one of the multiple candidates, and controls reception of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

[0225] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2024-127682, filed on August 2, 2024, are incorporated herein by reference in their entirety.

[0226] One aspect of the present disclosure is useful in wireless communication systems.

[0227] 100 Terminal 101, 201 Radio receiving unit 102, 202 Data receiving processing unit 103, 203 Control unit 104, 204 Data transmitting processing unit 105, 205 Radio transmitting unit 200 Base station

Claims

1. A communication device comprising: a receiving circuit that receives first control information including information on multiple candidates for the sequence length of an orthogonal code and second control information including information on the orthogonal code corresponding to one of the multiple candidates for the sequence length; and a control circuit that controls the transmission of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

2. The communication device according to claim 1, wherein the second control information includes information indicating one of a plurality of candidates for the sequence length.

3. The communication device according to claim 1, wherein the control circuit determines to transmit the uplink signal when the sequence length of the orthogonal code specified by the first control information and the second control information is equal to or less than a threshold, and determines not to transmit the uplink signal when the sequence length of the orthogonal code specified by the first control information and the second control information is greater than the threshold.

4. The communication device according to claim 3, wherein the threshold is the number of repetitions of the uplink signal or a time domain window (TDW) of a demodulation reference signal (DMRS) bundling.

5. The communication device according to claim 1, wherein the first control information includes information relating to a plurality of candidates for the orthogonal code sequence, and the second control information includes information indicating any one of the plurality of candidates for the sequence.

6. The communication device according to claim 1, wherein the second control information includes information for identifying the sequence of the orthogonal code.

7. The communication device according to claim 6, wherein the information identifying the sequence is included in at least a part of a field in the second control information for notifying a parameter different from the sequence.

8. The communication device according to claim 7, wherein the field is at least one of an MCS (Modulation and Coding Scheme) field, a frequency resource allocation field, and a frequency hopping flag field.

9. The communication device according to claim 1, wherein information for identifying a sequence of the orthogonal code is associated with information for identifying a port of a demodulation reference signal.

10. The communication device according to claim 9, wherein the control circuit specifies the information for identifying the group based on the information for identifying the port included in the second control information.

11. The communication device according to claim 9, wherein the control circuit specifies the information for identifying the port based on information for identifying the sequence included in the second control information.

12. The communication device according to claim 1, wherein the second control information includes information for identifying a port of a demodulation reference signal.

13. The communication device of claim 1, wherein in the second control information, a field notifying information identifying the orthogonal code sequence includes a portion of the information identifying a port of a demodulation reference signal, and a field notifying information identifying the port includes the remaining information identifying the port.

14. A communication device as described in claim 1, wherein in the second control information, a field notifying information identifying the orthogonal code sequence includes a portion of the information identifying the sequence, and a field notifying information identifying a port of a demodulation reference signal includes the remaining information identifying the sequence.

15. A base station comprising: a transmitting circuit that transmits first control information including information on multiple candidates for the sequence length of an orthogonal code and second control information including information on the orthogonal code corresponding to one of the multiple candidates; and a control circuit that controls reception of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

16. A communication method in which a communication device receives first control information including information on multiple candidates for the sequence length of an orthogonal code and second control information including information on the orthogonal code corresponding to one of the multiple candidates for the sequence length, and controls transmission of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

17. A communication method in which a base station transmits first control information including information on multiple candidates for the sequence length of an orthogonal code and second control information including information on the orthogonal code corresponding to one of the multiple candidates, and controls reception of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

18. An integrated circuit that controls the processing of a communication device, the processing including: receiving first control information including information on multiple candidates for the sequence length of an orthogonal code and second control information including information on the orthogonal code corresponding to one of the multiple candidates for the sequence length; and controlling the transmission of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

19. An integrated circuit that controls the processing of a base station, the processing including: a process of transmitting first control information including information on multiple candidates for the sequence length of an orthogonal code and second control information including information on the orthogonal code corresponding to one of the multiple candidates; and a process of controlling the reception of an uplink signal to which the orthogonal code is applied based on the first control information and the second control information.

Images