Terminal, base station, and communication method
Patent Information
- Application Number
- CN202480087539.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-02-16
- Filing Date
- 2024-11-26
- Publication Date
- 2026-09-08
AI Technical Summary
[0019] According to one embodiment of this disclosure, signals can be appropriately transmitted in the uplink.
Smart Images

Figure CN122720118A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to terminals, base stations, and communication methods. Background Technology
[0002] In recent years, against the backdrop of the expansion and diversification of wireless services, the rapid development of the Internet of Things (IoT) is anticipated. The application of mobile communication is expanding beyond information terminals such as smartphones to all areas, including vehicles, homes, home appliances, and industrial equipment. To support this service diversification, in addition to increasing system capacity, significant improvements in the performance and functionality of mobile communication systems are required to meet various necessary conditions such as the increase in the number of connected devices and low latency. Fifth-generation mobile communication systems (5G) feature high capacity and ultra-high speed (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), providing flexible wireless communication to meet diverse needs.
[0003] The 3rd Generation Partnership Project (3GPP), an international standards organization, is developing specifications for New Radio (NR), one of the wireless interfaces for 5G.
[0004] Existing technical documents
[0005] Non-patent literature
[0006] Non-patent document 1: 3GPP TS38.104 V15.19.0, “NR Base Station (BS) radiotransmission and reception (Release 15),” June 2023.
[0007] Non-patent literature 2: RP-202928, “New WID on NR coverage enhancements,” ChinaTelecom, December 2020.
[0008] Non-patent literature 3: RP-220937, “Revised WID on Further NR coverage enhancements,” China Telecom, March 2022.
[0009] Non-patent literature 4: RP-223534, “Revised WID: NR NTN (Non-Terrestrial Networks) enhancements”, Thales, December 2022.
[0010] Non-patent document 5: 3GPP TS38.211 V18.1.0, “NR Physical channels and modulation (Release 18),” December 2023.
[0011] Non-patent document 6: 3GPP TS38.212 V18.1.0, “NR Multiplexing and channelcoding (Release 18),” December 2023.
[0012] Non-patent literature 7: 3GPP TS38.213 V18.1.0, “NR Physical layer procedures for control (Release 18),” December 2023.
[0013] Non-patent literature 8: 3GPP TS38.214 V18.1.0, “NR Physical layer procedures for data (Release 18),” December 2023.
[0014] Non-patent document 9: RP-234078, “New WID: Non-Terrestrial Networks (NTN) for NR Phase 3,” Huawei (Moderator, RAN1 Vice-Chair), December 2023. Summary of the Invention
[0015] However, there is still room for research into the methods for transmitting signals in the uplink.
[0016] The non-limiting embodiments disclosed herein help to provide terminals, base stations, and communication methods capable of appropriately transmitting signals in the uplink.
[0017] A terminal according to an embodiment of this disclosure includes: a control circuit that determines an orthogonal sequence having the following relationship: at least a portion of a frequency domain output result obtained by applying the orthogonal sequence to a signal before a Discrete Fourier Transform (DFT) and applying the DFT to the signal is mapped to a frequency resource for demodulating a reference signal; and a transmission circuit that transmits the signal to which the orthogonal sequence has been applied.
[0018] Furthermore, these broad or specific methods can be implemented by systems, devices, methods, integrated circuits, computer programs, or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.
[0019] According to one embodiment of this disclosure, signals can be appropriately transmitted in the uplink.
[0020] Further advantages and effects of one embodiment of this disclosure will be illustrated by the specification and drawings. These advantages and / or effects are provided by the various embodiments and the features described in the specification and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. Attached Figure Description
[0021] Figure 1 This is a diagram illustrating an example of DFT spreading Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) using the pre Discrete Fourier Transform (DFT) Orthogonal Cover Code (OCC).
[0022] Figure 2 This is a block diagram illustrating a structural example of a portion of a base station.
[0023] Figure 3 This is a block diagram showing a structural example of a portion of a terminal.
[0024] Figure 4 This is a diagram illustrating an application example of pre-DFT OCC.
[0025] Figure 5 This is a diagram illustrating an application example of pre-DFT OCC.
[0026] Figure 6 This is a diagram illustrating an application example of pre-DFT OCC.
[0027] Figure 7 This is a diagram showing an example of a time-domain signal after applying pre-DFT OCC.
[0028] Figure 8 This is a diagram showing an example of an OCC sequence.
[0029] Figure 9 This is a diagram showing an example of an OCC sequence.
[0030] Figure 10 This is a diagram showing an example of an OCC sequence.
[0031] Figure 11 This is a flowchart illustrating an example of terminal operation.
[0032] Figure 12 This is a diagram illustrating an application example of pre-DFT OCC.
[0033] Figure 13 This is a diagram illustrating an application example of pre-DFT OCC.
[0034] Figure 14 This is a diagram showing an example of an OCC sequence.
[0035] Figure 15 This is a flowchart illustrating an example of terminal operation.
[0036] Figure 16 This is a diagram illustrating an example of the relationship between the Downlink Control Information (DCI) bit field and the Demodulation Reference Signal (DMRS) port.
[0037] Figure 17 This is a diagram illustrating an example of the relationship between the DCI bit field and the DMRS port and OCC sequence number.
[0038] Figure 18 This is a diagram illustrating an example of the relationship between the DCI bit field and the DMRS port.
[0039] Figure 19 This is a diagram illustrating an example of the relationship between the DCI bit field and the DMRS port and OCC sequence number.
[0040] Figure 20 This is a flowchart illustrating an example of terminal operation.
[0041] Figure 21 This is a block diagram illustrating an example of the structure of a base station.
[0042] Figure 22 This is a block diagram showing an example of the terminal's structure.
[0043] Figure 23 This is a diagram of an exemplary architecture for a 3GPP NR system.
[0044] Figure 24 This is a diagram of an exemplary functional segmentation in 5G O-RAN. Detailed Implementation
[0045] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
[0046] The basic functionality of eMBB or URLLC was standardized in Release 15. From Release 16 onwards, extensions were made for Industrial IoT (IoT) and Vehicle-to-Everything (V2X) for URLLC, or for Non-Terrestrial Networks (NTN) including satellite. The 3GPP extended specifications have been referred to as "5G-Advanced" since Release 18.
[0047] In NR, for example, in addition to frequency bands below 6 GHz, such as the 700 MHz to 3.5 GHz band previously used for cellular communication (e.g., also referred to as Frequency Range 1 (FR1)), millimeter-wave frequency bands such as 28 GHz or 39 GHz bands that can ensure wideband coverage can also be utilized (e.g., also referred to as Frequency Range 2 (FR2)) (see, for example, Non-Patent Document 1). Furthermore, for example, in FR1, it is possible to use frequency bands such as the 3.5 GHz band, which are higher than the frequency bands used in Long Term Evolution (LTE) or 3rd Generation mobile communication systems (3G).
[0048] The higher the frequency band, the greater the radio wave propagation loss, and the more easily the radio wave reception quality deteriorates. Therefore, in NR, for example, it is desirable to ensure the same level of communication area (or coverage) as Radio Access Technology (RAT) such as LTE or 3G while using a higher frequency band compared to LTE or 3G; in other words, it is desirable to ensure adequate communication quality. For example, methods for improving coverage in NR have been studied in 3GPP Release 17 (e.g., denoted as "Rel.17") and Release 18 (e.g., denoted as "Rel.18") (see, for example, Non-Patent Literature 2 and Non-Patent Literature 3).
[0049] Furthermore, coverage plays a crucial role in supporting NTNs with significantly longer communication distances compared to existing terrestrial networks (TN). NR Rel.15 was standardized as a wireless access technology for terrestrial networks. On the other hand, Rel.17 supported non-terrestrial networks (NTNs) such as those using satellites or high-altitude platform stations (HAPS). In Rel.18, research was conducted on NTN extension technologies, and improvements to the uplink coverage of NTNs were investigated (e.g., see Non-Patent Literature 4).
[0050] In NR, a terminal (e.g., also referred to as user equipment (UE)) transmits and receives data, for example, according to resource allocation indicated by Layer 1 control signals (e.g., DCI: Downlink Control Information) on the downlink control channel (e.g., PDCCH: Physical Downlink Control Channel) from a base station (e.g., also referred to as gNB) or as Layer 3 Radio Resource Control (RRC: Radio Resource Control).
[0051] In NR, repetition can be applied as one of the uplink (UL) coverage extension techniques (e.g., see Non-Patent Document 7 or 8). In NR up to version 18, the channels for which repetition can be applied are: uplink data channels scheduled by DCI format 0-1 or DCI format 0-2 (e.g., PUSCH: PhysicalUplink Shared Channel) (e.g., a PUSCH scheduled after parameters are set via a pusch-Config Information Element (IE) as a terminal-specific RRC), Msg.3 PUSCH (e.g., a PUSCH scheduled by a Random Access Response (RAR), uplink control channels (e.g., PUCCH: Physical UplinkControl Channel), and random access channels (e.g., PRACH: Physical Random Access Channel).
[0052] In scenarios where coverage is limited, such as NTN using handheld terminals, repeated transmissions can be applied to uplink transmissions due to significant propagation loss. However, in repeated transmissions, communication capacity may decrease because the time and frequency resources used for communication increase proportionally with the number of retransmissions.
[0053] Therefore, as another method to improve coverage, research is underway to improve uplink communication capacity and transmission rate by extending the PUSCH application with orthogonal sequences (e.g., orthogonal cover codes (OCC)) (see, for example, non-patent document 9). For example, OCC may include OCC applied between orthogonal frequency domain multiplexing (OFDM) symbols, OCC applied between time slots, or OCC applied within OFDM symbols.
[0054] An example of applying OCC within OFDM symbols could be: Figure 1As shown, in Discrete Fourier Transform spreading OFDM (DFT-s-OFDM), an OCC (hereinafter also referred to as "pre-DFT OCC") is applied to the modulated data symbol before the DFT, followed by DFT precoding (or spreading, transform precoding). In this method, a repetition corresponding to the spreading factor (SF) (or OCC sequence length) is applied to the data symbol (sequence) before DFT precoding and multiplied by the OCC. Furthermore, this method has been introduced in existing NR as PUCCH format 4 (e.g., see Non-Patent Document 5). It should be noted that in PUCCH format 4, an OCC sequence length of 2 or 4 is supported (spreading factor 2 or 4; multiplexing capacity for 2 or 4 terminals). Additionally, PUCCH format 4 only supports resource allocation for a single resource block (RB). In addition, in PUCCH format 4, the OCC sequence used is provided by PUCCH resource allocation.
[0055] However, there is still room for research regarding the transmission and control methods of PUSCH using pre-DFT OCC.
[0056] For example, after applying a pre-DFT OCC using cyclic shift codes as the OCC sequence and then applying DFT precoding, the frequency domain signal (output) becomes a comb structure. Additionally, PUSCH based on DFT-s-OFDM supports Demodulation Reference Signal (DMRS) configuration type 1. DMRS configuration type 1 has a comb structure in the frequency domain (e.g., in a DMRS mapping in the frequency domain).
[0057] Based on the applied OCC sequence (e.g., OCC sequence number, also known as OCC index), the resource is allocated to which comb number (e.g., subcarrier or resource element) in the frequency domain comb structure. Therefore, if the use of pre-DFT OCC is controlled without relying on the DMRS comb structure in the frequency domain, it is possible for the frequency resources (e.g., subcarriers or REs) to which PUSCH is mapped as a result of pre-DFT OCC and DFT to be completely inconsistent with the frequency resources (e.g., subcarriers or REs) to which DMRS is mapped, potentially degrading channel estimation performance. Therefore, when using pre-DFT OCC, it is desirable to consider its relationship with the mapping position of DMRS in the frequency domain (e.g., comb structure).
[0058] Furthermore, when using pre-DFT OCC, it is desirable to support the most flexible and maximum multiplexing capacity possible. Here, the maximum number of ports (e.g., multiplexing number) supported in the existing DMRS configuration type 1 is 4 in the case of single-symbol DMRS and 8 in the case of double-symbol DMRS. If the OCC-based multiplexing capacity is set to not exceed the range of the DMRS multiplexing capacity, then, for example, in the case of DMRS configuration type 1, to support the most flexible and larger multiplexing capacity possible, it is desirable to support at least an OCC sequence length (or extension factor (also known as extension rate), multiplexing capacity) of 8. However, in cases where resource allocation is limited to 1 RB, such as in PUCCH format 4, even with a maximum DMRS multiplexing capacity of 8, it is difficult to support pre-DFT OCC with an OCC sequence length of 8 (extension factor 8, multiplexing capacity 8).
[0059] Furthermore, regarding methods for notifying OCC sequences, for example, for PUSCH data sent according to resource allocation indicated by DCI, dynamically notifying OCC sequences can be achieved by adding a bit field to the DCI for notifying OCC sequences, but this increases DCI overhead. In scenarios where improved coverage is desired, reducing DCI overhead is desirable.
[0060] In one non-limiting embodiment of this disclosure, a method for improving the transmission quality and transmission capacity of PUSCH using pre-DFT OCC, or a method for reducing the notification overhead of pre-DFT OCC sequences, is described.
[0061] The following describes non-limiting embodiments of this disclosure.
[0062] [Overview of Communication Systems]
[0063] The communication systems of various embodiments of this disclosure include, for example, at least one base station and at least one terminal.
[0064] Figure 2 This is a block diagram illustrating a structural example of a base station 100 according to an embodiment of the present disclosure. Figure 3 This is a block diagram illustrating a structural example of a portion of a terminal 200 according to an embodiment of the present disclosure.
[0065] exist Figure 2 In the base station 100 shown, the control unit (e.g., corresponding to the control circuit) determines an orthogonal sequence having the following relationship: at least a portion of the frequency domain output obtained by applying this orthogonal sequence (pre-DFT OCC) to the signal before the DFT and applying the DFT to the signal is mapped to frequency resources for demodulation reference signal (DMRS). The communication unit (e.g., corresponding to the receiving circuit) receives the signal (e.g., PUSCH) to which the orthogonal sequence has been applied.
[0066] exist Figure 3 In the terminal 200 shown, the control unit (e.g., corresponding to the control circuit) determines an orthogonal sequence having the following relationship: at least a portion of the frequency domain output obtained by applying this orthogonal sequence (pre-DFT OCC) to the signal before the DFT and applying the DFT to the signal is mapped to frequency resources for the demodulation reference signal (DMRS). The communication unit (e.g., corresponding to the transmission circuit) transmits a signal (e.g., PUSCH) to which the orthogonal sequence has been applied.
[0067] (Implementation Method 1)
[0068] In this embodiment, pre-DFT OCC is applied to the PUSCH based on DFT-s-OFDM.
[0069] In this embodiment, the base station 100 and the terminal 200 apply (or decide, set) a pre-DFTOCC sequence with the following relationship: at least a portion of the frequency domain output results obtained by applying the pre-DFT OCC (applying OCC to the signal before DFT) and applying DFT to the signal (e.g., referred to as "applying pre-DFT OCC and DFT after DFT") are mapped to frequency resources for DMRS.
[0070] For example, when applying pre-DFT OCC, an OCC with the following relationship between the OCC sequence number and the DMRS port can be applied (or set, determined): "The output results given by the frequency domain comb structure after applying pre-DFT OCC and DFT (e.g., comb number, subcarrier or RE as the mapping destination of the data signal) are mapped to the subcarrier (or RE) used for DMRS."
[0071] For example, imagine (assuming) using PUSCH based on DFT-s-OFDM with pre-DFT OCC and DMRS configuration type 1.
[0072] DMRS configuration type 1 has the following frequency domain comb structure: the DMRS sequences of DMRS ports #0, #1, #4, and #5 are mapped to RE numbers #0, #2, #4, #6, #8, and #10 within RBs (e.g., RE numbers #0 to #11). Additionally, DMRS configuration type 1 has the following frequency domain comb structure: the DMRS sequences of DMRS ports #2, #3, #6, and #7 are mapped to RE numbers #1, #3, #5, #7, #9, and #11 within RBs.
[0073] Figure 4 An example is shown for the case of pre-DFT OCC with an OCC sequence length of 2 (expansion factor 2).
[0074] For example, such as Figure 4 As shown, when applying a pre-DFT OCC with an OCC sequence length of 2 (expansion factor 2), the output results given by the frequency domain comb structure after applying the pre-DFT OCC and DFT can be as follows: when applying OCC sequence number #0, it is RE numbers #0, #2, #4, #6, #8 and #10 within RB (e.g., RE numbers #0 to #11); when applying OCC sequence number #1, it is RE numbers #1, #3, #5, #7, #9 and #11 within RB.
[0075] Therefore, in the case of applying pre-DFT OCC with an OCC sequence length of 2 (expansion factor 2), such as Figure 4 As shown, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #0 of RE#0, #2, #4, #6, #8, and #10, which is mapped to the RE for DMRS ports #0, #1, #4, or #5, and therefore can be used in combination with DMRS ports #0, #1, #4, or #5. Additionally, as... Figure 4As shown, the output results given by the frequency domain comb structure after applying pre-DFT OCC and DFT can become OCC sequence number #1 of RE#1, #3, #5, #7, #9 and #11, which is mapped to RE for DMRS ports #2, #3, #6 or #7, and can therefore be used in combination with DMRS ports #2, #3, #6 or #7.
[0076] Figure 5 An example is shown for the case of pre-DFT OCC with an OCC sequence length of 4 (expansion factor 4).
[0077] For example, such as Figure 5 As shown, when applying a pre-DFT OCC with an OCC sequence length of 4 (expansion factor 4), the output results given by the frequency domain comb structure after applying the pre-DFT OCC and DFT can be RE numbers #0, #4, and #8 within the RB (e.g., RE numbers #0 to #11) when applying OCC sequence number #0; RE numbers #1, #5, and #9 within the RB when applying OCC sequence number #1; RE numbers #2, #6, and #10 within the RB when applying OCC sequence number #2; and RE numbers #3, #7, and #11 within the RB when applying OCC sequence number #3.
[0078] Therefore, in the case of applying pre-DFT OCC with an OCC sequence length of 4 (expansion factor 4), such as Figure 5 As shown, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #0 of RE#0, #4, and #8, which is mapped to the RE for DMRS ports #0, #1, #4, or #5, and therefore can be used in combination with DMRS ports #0, #1, #4, or #5. Additionally, as... Figure 5 As shown, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #1 of RE#1, #5, and #9, which is mapped to REs for DMRS ports #2, #3, #6, or #7, and therefore can be used in combination with DMRS ports #2, #3, #6, or #7. Additionally, as... Figure 5 As shown, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #2 of RE#2, #6, and #10, which is mapped to the RE for DMRS ports #0, #1, #4, or #5, and therefore can be used in combination with DMRS ports #0, #1, #4, or #5. Additionally, as... Figure 5As shown, the output results given by the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #3 of RE#3, #7 and #11, which is mapped to the RE for DMRS ports #2, #3, #6 or #7, and can therefore be used in combination with DMRS ports #2, #3, #6 or #7.
[0079] Figure 6 An example is shown for the case of applying pre-DFT OCC with an OCC sequence length of 6 (expansion factor 6).
[0080] For example, such as Figure 6 As shown, when applying a pre-DFT OCC with an OCC sequence length of 6 (spread factor 6), the output results given by the frequency domain comb structure after applying the pre-DFT OCC and DFT are as follows: when applying OCC sequence number #0, it can be RE numbers #0 and #6 within RB (e.g., RE numbers #0 to #11); when applying OCC sequence number #1, it can be RE numbers #1 and #7 within RB; when applying OCC sequence number #2, it can be RE numbers #2 and #8 within RB; when applying OCC sequence number #3, it can be RE numbers #3 and #9 within RB; when applying OCC sequence number #4, it can be RE numbers #4 and #10 within RB; and when applying OCC sequence number #5, it can be RE numbers #5 and #11 within RB.
[0081] Therefore, in the case of applying pre-DFT OCC with an OCC sequence length of 6 (expansion factor 6), such as Figure 6 As shown, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #0 of RE#0 and #6, which is mapped to the RE for DMRS ports #0, #1, #4, or #5, and therefore can be used in combination with DMRS ports #0, #1, #4, or #5. Additionally, as... Figure 6 As shown, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #1 of RE#1 and #7, which is mapped to REs for DMRS ports #2, #3, #6, or #7, and therefore can be used in combination with DMRS ports #2, #3, #6, or #7. Additionally, as... Figure 6 As shown, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #2 of RE#2 and #8, which is mapped to the RE for DMRS ports #0, #1, #4, or #5, and therefore can be used in combination with DMRS ports #0, #1, #4, or #5. Additionally, as... Figure 6 As shown, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #3 of RE#3 and #9, which is mapped to the REs used for DMRS ports #2, #3, #6, or #7, and therefore can be used in combination with DMRS ports #2, #3, #6, or #7. Additionally, as... Figure 6 As shown, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #4 of RE#4 and #10, which is mapped to the REs used for DMRS ports #0, #1, #4, or #5, and therefore can be used in combination with DMRS ports #0, #1, #4, or #5. Additionally, as... Figure 6 As shown, the output of the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #5 of RE#5 and #11, which is mapped to the RE for DMRS ports #2, #3, #6 or #7, and can therefore be used in combination with DMRS ports #2, #3, #6 or #7.
[0082] Thus, according to this embodiment, the output results (e.g., comb tooth number, subcarrier or RE as the mapping destination of the data signal) given by the frequency domain comb structure after applying pre-DFT OCC and DFT are mapped to the subcarrier (or RE) used for DMRS. Therefore, the transmitting side (e.g., terminal 200) can transmit the data signal (e.g., PUSCH) and DMRS through the same subcarrier or RE, thereby improving the channel estimation accuracy of the receiving side (e.g., base station 100).
[0083] In addition, the time-domain signal y before applying DFT and after applying pre-DFT OCC can be given by, for example, the following equation (1).
[0084] [Equation 1]
[0085] (1)
[0086]
[0087]
[0088]
[0089] Here, d(0), ..., d(M) symb layer -1) is the modulation symbol sequence. Furthermore, M SC PUSCH =M RB PUSCH ·NSC RB , of which M RB PUSCH N is the number of RBs allocated. SC RB This is the number of subcarriers (or REs) per RB. Additionally, M... symb layer N is the number of modulation symbols per layer. SF This is the sequence length or expansion factor of the pre-DFT OCC. n (k) is the OCC sequence of the pre-DFT OCC sequence number n.
[0090] Figure 7 Shown in M RB PUSCH = 1, N SC RB = 12 and N SF An example of a time-domain signal y(t) after applying pre-DFT OCC at time 4. Pre-DFT OCC can be applied per OFDM symbol. The number of data modulation symbols transmitted in one OFDM symbol is M. SC PUSCH / N SF = M RB PUSCH ·N SC RB / N SF One (in) Figure 7 In the example, it is 1 × 12 / 4 = 3. Therefore, the modulation symbol sequence is calculated in terms of the amount corresponding to 1 OFDM symbol, i.e., per M. SC PUSCH / N SF The OFDM symbol is divided into segments, and each OFDM symbol contains M. SC PUSCH / N SF A sequence of data symbols (in) Figure 7 The example uses the set of d(0), d(1) and d(2) and the set of d(3), d(4) and d(5) to apply pre-DFT OCC.
[0091] In addition, the frequency domain signal z after applying pre-DFT OCC and DFT can be given by, for example, the following equation (2).
[0092] [Equation 2]
[0093] (2)
[0094]
[0095]
[0096] Furthermore, cyclic shift sequences are commonly known as OCC sequences where the frequency domain signal becomes a comb structure after applying pre-DFT OCC and performing DFT precoding. As an example of a pre-DFT OCC sequence, Figure 8 This shows an OCC sequence with an OCC sequence length of 2 (expansion factor 2). Figure 9 This shows an OCC sequence with an OCC sequence length of 4 (expansion factor 4). Figure 10 The OCC sequence with an OCC sequence length of 6 (expansion factor 6) is shown.
[0097] It should be noted that, in this embodiment, the OCC sequence number used for pre-DFT OCC can be controlled (e.g., determined, set) or limited according to the subcarrier (or RE) or DMRS port used for DMRS.
[0098] For example, when using DMRS ports #0, #1, #4, or #5, base station 100 and terminal 200 can... Figure 4 In the example (where the OCC sequence length is 2), the OCC sequence number is set to #0. Figure 5 In the example (where the OCC sequence length is 4), the OCC sequence number is set to #0 or #2. Figure 6 In the example (where the OCC sequence length is 6), the OCC sequence number is set to #0, #2, or #4. Additionally, for example, when using DMRS ports #2, #3, #6, or #7, base station 100 and terminal 200 can... Figure 4 In the example (where the OCC sequence length is 2), the OCC sequence number is set to #1. Figure 5 In the example (where the OCC sequence length is 4), the OCC sequence number is set to #1 or #3. Figure 6 In the example (where the OCC sequence length is 6), the OCC sequence number is set to #1, #3, or #5.
[0099] [Operation example of terminal 200]
[0100] Figure 11 This is a flowchart illustrating an example of the operation of determining the OCC sequence in terminal 200.
[0101] exist Figure 11 In the process, terminal 200 obtains at least one of information related to DMRS configuration and information related to DMRS port (S101).
[0102] Terminal 200 obtains information related to the OCC sequence (pre-DFT OCC sequence) (e.g., sequence length or expansion factor) (S102).
[0103] Based on the information obtained related to the DMRS configuration and DMRS port, terminal 200 determines the OCC sequence that can be applied or to be applied (S103). For example, as described above, terminal 200 may determine an OCC with the following relationship: the subcarrier or RE given by the frequency domain comb structure after applying the pre-DFT OCC and DFT is mapped to the subcarrier or RE used for DMRS.
[0104] As described above, in this embodiment, when using the pre-DFT OCC, the terminal 200 considers its relationship with the DMRS's mapping position in the frequency domain (e.g., comb structure). Thus, by controlling the use of the pre-DFT OCC based on the DMRS's comb structure in the frequency domain, the frequency resources (e.g., subcarriers or REs) to which the PUSCH is mapped as the output of the application of the pre-DFT OCC and DFT are consistent with the frequency resources (e.g., subcarriers or REs) to which the DMRS is mapped, thereby improving channel estimation performance.
[0105] Therefore, according to this embodiment, the transmission quality of PUSCH using pre-DFT OCC can be improved. Consequently, terminal 200 can appropriately transmit signals in the uplink.
[0106] (Modification 1 of Implementation Method 1)
[0107] The output results given by the frequency domain comb structure after applying pre-DFT OCC and DFT (e.g., comb tooth number, subcarrier or RE to which the data signal is mapped) may also be inconsistent with the subcarrier or RE to which the DMRS is mapped.
[0108] In this variation, an OCC with the following relationship can be applied: "The output results (e.g., comb tooth number, subcarrier or RE as the mapping destination of the data signal) given by the pre-DFT OCC and the frequency domain comb structure after DFT are mapped as much as possible to the same subcarrier (RE) as the subcarrier (or RE) used for DMRS."
[0109] For example, such as Figure 12As shown, when applying a pre-DFT OCC with an OCC sequence length of 3 (expansion factor 3), the output results given by the frequency domain comb structure after applying the pre-DFT OCC and DFT can be RE numbers #0, #3, #6, and #9 within the RB (e.g., RE numbers #0 to #11) when applying OCC sequence number #0; RE numbers #1, #4, #7, and #10 within the RB when applying OCC sequence number #1; and RE numbers #2, #5, #8, and #11 within the RB when applying OCC sequence number #2.
[0110] In the case of applying pre-DFT OCC with an OCC sequence length of 3 (expansion factor 3), such as Figure 12 As shown, the output of the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #0 of RE#0, #3, #6, and #9, for example, mapped to a portion of the REs used for DMRS ports #0, #1, #4, or #5 (RE#0 and RE#6), and therefore can be used in combination with DMRS ports #0, #1, #4, or #5. Additionally, the output of the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #1 of RE#1, #4, #7, and #10, for example, mapped to a portion of the REs used for DMRS ports #2, #3, #6, or #7 (RE#1 and RE#7), and therefore can be used in combination with DMRS ports #2, #3, #6, or #7. Additionally, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can become the OCC sequence number #2 of RE#2, #5, #8 and #11, for example, mapped to a part of the REs used for DMRS ports #0, #1, #4 or #5 (RE#2 and RE#8), and thus can be used in combination with DMRS ports #0, #1, #4 or #5.
[0111] like Figure 12 As shown, although not all subcarriers (REs) of the frequency domain comb structure after applying pre-DFT OCC and DFT are the same as the subcarriers (REs) that are the mapping destination of DMRS, two of the four subcarriers are mapped to the same subcarriers (REs) as DMRS.
[0112] Therefore, the degradation of channel estimation accuracy can be minimized.
[0113] (Modification 2 of Implementation Method 1)
[0114] As in Variation 1 of Implementation 1, depending on the OCC sequence length (spread factor), the output results (e.g., comb tooth number, subcarrier to which the data signal is mapped, or RE) given by the frequency domain comb structure after applying pre-DFT OCC and DFT may not be consistent with the RE mapping of DMRS.
[0115] In this variation, an OCC sequence with the following relationship can be used: the subcarrier (RE) spacing in the frequency domain comb structure after applying pre-DFT OCC and DFT is an integer multiple of the subcarrier (RE) spacing in the DMRS mapping. Alternatively, an OCC sequence with the following relationship can be used: the subcarrier (RE) spacing in the frequency domain comb structure after applying pre-DFT OCC and DFT is not an integer multiple of the subcarrier (RE) spacing in the DMRS mapping.
[0116] For example, in DMRS configuration type 1, the subcarrier (RE) spacing in the RE mapping of DMRS is 2. Here, a subcarrier (RE) spacing of 2 means that the DMRS sequence is mapped to RE numbers #0, #2, #4, #6, #8, and #10 within the RB, or RE numbers #1, #3, #5, #7, #9, and #11 within the RB, which have a comb structure in the frequency domain.
[0117] The subcarrier (RE) spacing in the frequency domain comb structure after applying pre-DFT OCC and DFT is equivalent to the OCC sequence length (spread factor). Therefore, for example, a pre-DFT OCC with an OCC sequence length (spread factor) that is an integer multiple of the subcarrier (RE) spacing of 2 can be applied to DMRS configuration type 1 (e.g., OCC sequence lengths 2, 4, and 6).
[0118] It should be noted that the pre-DFT OCC with an OCC sequence length (expansion factor) of 8 can also be applied using the implementation method 2 described later.
[0119] According to this variation, the output results (e.g., comb tooth number, subcarrier or RE as the mapping destination of the data signal) given by the frequency domain comb structure after applying pre-DFT OCC and DFT can be mapped to the same subcarrier (RE) as DMRS.
[0120] (Implementation Method 2)
[0121] For example, when applying pre-DFT OCC, if the frequency domain resource allocation granularity (or allocation unit) is 1 RB (e.g., 12 subcarriers), in order to match the frequency domain comb structure after applying pre-DFT OCC and DFT with DMRS configuration type 1, the supported OCC sequence length (spread factor) must be an OCC sequence length that is a multiple of 2 and a divisor of 12. For example, for DMRS configuration type 1, the OCC sequence lengths that satisfy the above conditions are 2, 4, 6, or 12.
[0122] On the other hand, in order to support multiplexing of multiple terminals based on pre-DFT OCC within the same time and frequency resources, it is preferable to consider DMRS multiplexing in addition to data multiplexing based on pre-DFT OCC, and to consider the number of multiplexing ports not exceeding the number of multiplexing ports of DMRS. For example, the maximum number of multiplexing ports for DMRS configuration type 1 is 8.
[0123] Therefore, in order to support the most flexible and larger multiplexing capacity in a given DMRS configuration, for example, for DMRS configuration type 1, in addition to OCC sequence lengths of 2, 4, and 6, it is expected that at least an OCC sequence length (spread factor) of 8 will be supported. However, as mentioned above, with a frequency domain resource allocation granularity of 1 RB (e.g., 12 subcarriers), it is difficult to support an OCC sequence length of 8 because the above conditions are not met.
[0124] In NTN, the primary scenario is a line-of-sight environment between the satellite and the terminal. Under these conditions, the direct wave dominates, resulting in a propagation environment with low frequency selectivity and minimal frequency directional variation. Consequently, OCC orthogonality disruption caused by frequency-selective fading is minimal. Furthermore, it can be assumed that even with OCC extension across multiple base stations (RBs), orthogonality disruption remains relatively small.
[0125] Therefore, in this embodiment, when applying pre-DFT OCC to PUSCH, base station 100 and terminal 200 control the allocation unit (or granularity) of frequency resources (e.g., RB) according to the length (or spread factor) of the OCC sequence, and use the frequency resources allocated based on the allocation unit to send or receive PUSCH.
[0126] For example, when applying pre-DFT OCC, the frequency domain resource allocation is set to a unit of "N" RBs (N units of RBs) based on the OCC sequence length (spread factor). Here, for example, for DMRS configuration type 1, N is the smallest integer that satisfies the following conditions: the OCC sequence length is a multiple of 2 and a divisor of (12 × N).
[0127] For example, when the OCC sequence length is 2, 4, and 6, N=1, and the OCC sequence lengths of 2, 4, and 6 are multiples of 2 and divisors of (12×N)=12, satisfying the above condition. Additionally, when the OCC sequence length is 8, N=2, and the OCC sequence length of 8 is a multiple of 2 and a divisor of (12×N)=24, also satisfying the above condition.
[0128] It should be noted that, in this embodiment, for example, the OCC sequence with the following relationship can be applied in the same way as in embodiment 1: "The output results (e.g., comb tooth number, subcarrier or RE as the mapping destination of the data signal) given by the frequency domain comb structure after applying pre-DFT OCC and DFT are mapped to the subcarrier (or RE) used for DMRS".
[0129] Figure 13 An example is shown for the case of applying pre-DFT OCC with an OCC sequence length of 8 (expansion factor 8).
[0130] For example, such as Figure 13 As shown, when applying a pre-DFT OCC with an OCC sequence length of 8 (expansion factor 8), the output results given by the frequency domain comb structure after applying the pre-DFT OCC and DFT are as follows: When applying OCC sequence number #0, it can be RE numbers #0 and #8 within even RBs (e.g., RE#0 to #11) and RE#4 within odd RBs (e.g., RE#0 to #11); when applying OCC sequence number #1, it can be RE numbers #1 and #9 within even RBs (e.g., RE#0 to #11) and RE#5 within odd RBs; when applying OCC sequence number #2, it can be RE numbers #2 and #10 within even RBs (e.g., RE#2 to #10) and RE#6 within odd RBs; when applying OCC sequence number #3, it can be RE numbers within even RBs (e.g., RE#4 to #11) within even RBs (e.g., RE#0 to #11); E numbers #3, #11 and RE #7 within odd RBs; when applying OCC sequence number #4, it can be RE number #4 within even RBs (units of 2 RBs) and RE #0, #8 within odd RBs; when applying OCC sequence number #5, it can be RE number #5 within even RBs (units of 2 RBs) and RE #1, #9 within odd RBs; when applying OCC sequence number #6, it can be RE number #6 within even RBs (units of 2 RBs) and RE #2, #10 within odd RBs; when applying OCC sequence number #7, it can be RE number #7 within even RBs (units of 2 RBs) and RE #3, #11 within odd RBs.
[0131] Therefore, in the case of applying pre-DFT OCC with an OCC sequence length of 8 (expansion factor 8), such as Figure 13 As shown, the output of the frequency domain comb structure after applying pre-DFT OCC and DFT can be the OCC sequence number #0 for RE numbers #0 and #8 in even-numbered RBs (units of 2 RBs) and RE number #4 in odd-numbered RBs, which can be used in combination with DMRS ports #0, #1, #4, or #5. The output of the frequency domain comb structure after applying pre-DFT OCC and DFT can be the OCC sequence number #1 for RE numbers #1 and #9 in even-numbered RBs (units of 2 RBs) and RE number #5 in odd-numbered RBs, which can be used in combination with DMRS ports #1, #2, #6, or #7. The output of the frequency domain comb structure after applying pre-DFT OCC and DFT can be the OCC sequence number #2 for RE numbers #2 and #10 in even-numbered RBs (units of 2 RBs) and RE number #6 in odd-numbered RBs, which can be used in combination with DMRS ports #0, #1, #4, or #5. The output from the frequency domain comb structure after applying pre-DFT OCC and DFT can be the OCC sequence number #3 for RE numbers #3 and #11 in even-numbered RBs (units of 2 RBs) and RE number #7 in odd-numbered RBs, which can be used in combination with DMRS ports #2, #3, #6, or #7. The output from the frequency domain comb structure after applying pre-DFT OCC and DFT can be the OCC sequence number #4 for RE numbers #4 in even-numbered RBs (units of 2 RBs) and RE number #0 and #8 in odd-numbered RBs, which can be used in combination with DMRS ports #0, #1, #4, or #5. The output from the frequency domain comb structure after applying pre-DFT OCC and DFT can be the OCC sequence number #5 for RE numbers #5 in even-numbered RBs (units of 2 RBs) and RE number #1 and #9 in odd-numbered RBs, which can be used in combination with DMRS ports #2, #3, #6, or #7. The output from the frequency domain comb structure after applying pre-DFT OCC and DFT can be represented as RE number #6 in even-numbered RBs (units of 2 RBs) and OCC sequence number #6 for REs #2 and #10 in odd-numbered RBs, which can be used in combination with DMRS ports #0, #1, #4, or #5. Similarly, the output from the frequency domain comb structure after applying pre-DFT OCC and DFT can be represented as RE number #7 in even-numbered RBs (units of 2 RBs) and OCC sequence number #7 for REs #3 and #11 in odd-numbered RBs, which can be used in combination with DMRS ports #2, #3, #6, or #7.
[0132] For example, a pre-DFT OCC sequence of length 8 (expansion factor 8) can be obtained from... Figure 14The sequence shown is given.
[0133] [Operation example of terminal 200]
[0134] Figure 15 This is a flowchart illustrating an operational example of terminal 200.
[0135] exist Figure 15 In the process, terminal 200 obtains information related to the OCC sequence (pre-DFT OCC sequence) (e.g., sequence length or expansion factor) (S201).
[0136] Based on the obtained information related to the OCC sequence, terminal 200 determines the frequency domain allocation resources (e.g., the granularity of the value of N) corresponding to the length of the OCC sequence (S202). For example, for DMRS configuration type 1, terminal 200 determines the frequency domain allocation resources based on the value of N, which is the smallest integer that satisfies the following conditions: the OCC sequence length is a multiple of 2 and a divisor of (12×N).
[0137] Thus, by setting (or changing) the granularity (allocation unit) of frequency domain resource allocation according to the OCC sequence length (spread factor) of the pre-DFT OCC, the frequency domain comb structure after applying the pre-DFT OCC and DFT can be matched with DMRS configuration type 1 based on the OCC sequence length. For example, even for DMRS configuration type 1 (maximum number of multiplexed ports is 8), an OCC sequence length of 8 can be supported by setting the granularity of frequency domain resource allocation to 2 RBs. Therefore, according to this embodiment, when using pre-DFT OCC, the multiplexing capacity can be supported as flexibly and to the maximum extent possible, and the transmission capacity of PUSCH using pre-DFT OCC can be improved.
[0138] It should be noted that in this embodiment, an example of applying an OCC sequence with the following relationship, similar to Embodiment 1, is described: "The output results (e.g., comb tooth number, subcarrier or RE as the mapping destination of the data signal) given by the frequency domain comb structure after applying pre-DFT OCC and DFT are mapped to the subcarrier (or RE) used for DMRS." However, this is not the only limitation; the application method of the pre-DFT OCC sequence can also be other methods (methods that apply OCC sequences without the above relationship).
[0139] Furthermore, in the above embodiments, the following situation was explained: For DMRS configuration type 1, N used as the RB allocation unit (in units of N RBs) is the smallest integer that satisfies the condition that the OCC sequence length is a multiple of 2 and a divisor of (12×N), but is not limited to this. For example, the parameter related to the multiple of the OCC sequence length ("2" in the above example) and the parameter related to the divisor ("12" in the above example) can be set according to the DMRS setting or the number of REs (or subcarriers) constituting the RB.
[0140] (A variation of Implementation Method 2)
[0141] It should be noted that the frequency domain resource allocation granularity control based on the OCC sequence length (spread factor) in this embodiment (allocation in units of N RBs) is not limited to PUSCH based on DFT-s-OFDM with pre-DFT OCC applied. For example, the frequency domain resource allocation granularity control based on the OCC sequence length (spread factor) in this embodiment can also be applied to PUSCH based on CP-OFDM with frequency domain OCC (FD-OCC).
[0142] (Implementation Method 3)
[0143] In NR, the DMRS port of a PUSCH (DG-PUSCH: DynamicGrant-PUSCH) dynamically scheduled by DCI format 0-1 or DCI format 0-2 is determined based on the information in the antenna port field of the DCI.
[0144] As described above, by associating the output of the frequency domain comb structure (e.g., comb tooth number, subcarrier or RE as the mapping destination of the data signal) given by the pre-DFT OCC and DFT with the subcarrier (or RE) used for DMRS, it is expected to improve the channel estimation accuracy of PUSCH with pre-DFT OCC.
[0145] Therefore, in this embodiment, when applying pre-DFT OCC to the PUSCH, the base station 100 and the terminal 200 determine the sequence of the pre-DFT OCC (e.g., OCC sequence number) based on the value of the field (e.g., antenna port field) included in the DCI for notifying the DMRS port, or the DMRS port notified by the antenna port field, and send or receive the PUSCH with the determined OCC sequence applied. That is, the sequence of the pre-DFT OCC (OCC sequence number) is implicitly notified to the terminal 200 through the antenna port field included in the DCI.
[0146] For example, in a DFT-s-OFDM-based PUSCH, when dmrs-Type=1 (e.g., applying DMRS configuration type 1) and maxLength=1 (e.g., applying single-symbol DMRS), the relationship between the value of the DCI bit field and the DMRS port is as follows: Figure 16 As shown.
[0147] In this embodiment, except Figure 16 In addition to the relationship between the DCI bit field and the DMRS port shown, such as Figure 17 As shown, the DMRS port (or the value of the DCI bit field) is also associated with the OCC sequence number. Therefore, based on the DMRS port (or the value of the antenna port field) notified to terminal 200 via the antenna port field, terminal 200 determines the sequence (OCC sequence number) of the pre-DFT OCC. Figure 17 The relationship between the OCC sequence number and the OCC sequence shown can be, for example, derived from... Figure 8 and Figure 9 The relationship shown is given.
[0148] For example, in a DFT-s-OFDM-based PUSCH, when dmrs-Type=1 (e.g., applying DMRS configuration type 1) and maxLength=2 (e.g., allowing double-symbol DMRS), the relationship between the value of the DCI bit field and the DMRS port is as follows: Figure 18 As shown.
[0149] In this embodiment, except Figure 18 In addition to the relationship between the DCI bit field and the DMRS port shown, such as Figure 19 As shown, the DMRS port (or the value of the DCI bit field) is also associated with the OCC sequence number. Thus, the terminal 200 determines the sequence (OCC sequence number) of the pre-DFT OCC based on the DMRS port (or the value of the antenna port field) notified to the terminal 200 through the antenna port field.
[0150] It should be noted that, Figure 17 and Figure 18The association between the DMRS port and the OCC sequence number shown is an example and is not limited thereto. For example, as described in Implementation 1, the relationship between the DMRS port and the OCC sequence number can be such that the output of the frequency domain comb structure after applying the pre-DFT OCC and DFT (e.g., comb tooth number, subcarrier or RE as the mapping destination of the data signal) is mapped to the subcarrier (or RE) used for DMRS. Alternatively, the association between the DMRS port and the OCC sequence number may not have the above relationship, or it may have a partial relationship as described above.
[0151] [Operation example of terminal 200]
[0152] Figure 20 This is a flowchart illustrating an example of the operation of determining the OCC sequence in terminal 200.
[0153] exist Figure 20 In the process, terminal 200 obtains information related to DMRS configuration and information related to DMRS port (S301).
[0154] Terminal 200 obtains information related to the OCC sequence (pre-DFT OCC sequence) (e.g., sequence length or expansion factor) (S302).
[0155] Terminal 200 receives DCI (S303).
[0156] Based on the information obtained related to the DMRS configuration and DMRS port, as well as the information obtained related to the OCC sequence, the terminal 200 determines the DMRS port and OCC sequence associated with the value of the received DCI bit field (e.g., antenna port field) (S304).
[0157] According to this embodiment, since existing DCI fields (e.g., antenna port fields) can be used to notify the OCC sequence, the OCC sequence can be dynamically notified without increasing the number of DCI bits used to notify the OCC sequence. Therefore, for example, even in scenarios where improved coverage is desired, it is possible to suppress the increase in DCI overhead and dynamically notify the OCC sequence.
[0158] It should be noted that in the CG-PUSCH (Configured Grant-PUSCH), which sends data according to the resource allocation indicated (or set) by Layer 3 RRC, the DMRS port number is notified through the parameter "antennaPort" included in ConfiguredGrantConfig. In this case, it can also be used with... Figure 17 or Figure 19Similarly, terminal 200 determines the sequence (OCC sequence number) of pre-DFT PCC based on the value of the parameter indicated by RRC (e.g., antennaPort).
[0159] Furthermore, in this embodiment, the OCC method is not limited to the OCC within OFDM symbols based on pre-DFT OCC described above. For example, the OCC method applicable to this embodiment can be OCC applied between OFDM symbols, OCC applied between time slots, or a combination thereof.
[0160] [Base station structure]
[0161] Figure 21 This is a block diagram illustrating a structural example of base station 100. Figure 21 In this base station 100, there are a control unit 101, a higher layer control signal generation unit 102, a downlink control information generation unit 103, an encoding unit 104, a modulation unit 105, a signal distribution unit 106, a transmission unit 107, a reception unit 108, an extraction unit 109, a demodulation unit 110, and a decoding unit 111.
[0162] It should be noted that, Figure 21 At least one of the transmitting unit 107 and the receiving unit 108 shown may be included Figure 2 In the communication section shown. Additionally... Figure 21 At least one of the control unit 101, higher-layer control signal generation unit 102, downlink control information generation unit 103, encoding unit 104, modulation unit 105, signal distribution unit 106, receiving unit 108, extraction unit 109, demodulation unit 110, and decoding unit 111 shown may be included. Figure 1 In the control unit shown.
[0163] Control unit 101 determines, for example, information related to uplink transmission (e.g., PUSCH transmission) of terminal 200, and outputs the determined information to at least one of higher-layer control signal generation unit 102 and downlink control information generation unit 103. Information related to PUSCH transmission may include, for example, information related to pre-DFT OCC (e.g., OCC sequence length or spreading factor), information related to DMRS, time-domain resource allocation information (e.g., TDRA), and frequency-domain resource allocation information (e.g., FDRA). Furthermore, control unit 101 outputs the determined information to extraction unit 109, demodulation unit 110, and decoding unit 111.
[0164] Additionally, the control unit 101 may determine, for example, information related to downlink signals used for transmitting higher-layer control signals or downlink control information (e.g., coding and modulation scheme (MCS) and radio resource allocation), and output the determined information to the encoding unit 104, the modulation unit 105, and the signal allocation unit 106. Furthermore, the control unit 101 may output information related to downlink signals (e.g., data signals or higher-layer control signals) to the downlink control information generation unit 103.
[0165] The higher-level control signal generation unit 102 generates a higher-level control signal bit string based on information input from the control unit 101, and outputs the higher-level control signal bit string to the encoding unit 104.
[0166] The downlink control information generation unit 103 generates a downlink control information (e.g., DCI) bit string based on information input from the control unit 101, and outputs the generated DCI bit string to the encoding unit 104. It should be noted that the control information can also be sent to multiple terminals. For example, the downlink control information generation unit 103 can generate a DCI bit string (or DCI sequence) containing information related to the DMRS port and information related to the OCC sequence, according to any of the above embodiments. Additionally, the downlink control information generation unit 103 can append a CRC sequence scrambled by RNTI (e.g., C-RNTI) to the DCI sequence.
[0167] The encoding unit 104 encodes, for example, the bit string input from the higher-layer control signal generation unit 102 or the DCI bit string input from the downlink control information generation unit 103 based on information input from the control unit 101. The encoding unit 104 outputs the encoded bit string to the modulation unit 105.
[0168] The modulation unit 105 modulates the encoded bit string input from the encoding unit 104 based on information input from the control unit 101, and outputs the modulated signal (e.g., symbol string) to the signal distribution unit 106.
[0169] The signal allocation unit 106 maps a symbol string (e.g., containing downlink data signals or control signals) input from the modulation unit 105 to radio resources, for example, based on information representing radio resources input from the control unit 101. The signal allocation unit 106 then outputs the mapped downlink signal to the transmission unit 107.
[0170] The transmitting unit 107 performs transmission waveform generation processing on the signal input from the signal distribution unit 106, for example, using orthogonal frequency division multiplexing (OFDM). Additionally, in the case of OFDM transmission with an added cyclic prefix (CP), the transmitting unit 107 performs inverse fast fourier transform (IFFT) processing on the signal and adds CP to the IFFT-generated signal. Furthermore, the transmitting unit 107 performs RF processing on the signal, such as D / A conversion or up-conversion, and transmits the wireless signal to the terminal 200 via an antenna.
[0171] The receiving unit 108 performs RF processing, such as down-conversion or A / D conversion, on the uplink signal received from the terminal 200 via the antenna. Alternatively, in the case of OFDM transmission, the receiving unit 108 performs Fast Fourier Transform (FFT) processing on the received signal and outputs the resulting frequency domain signal to the extraction unit 109.
[0172] Extraction unit 109 extracts, for example, the radio resource portion that transmits uplink signals (e.g., PUSCH) from the received signal input by receiving unit 108 based on information input from control unit 101, and outputs the extracted radio resource portion to demodulation unit 110.
[0173] The demodulation unit 110 demodulates the uplink signal (e.g., PUSCH) input from the extraction unit 109 based on information input from the control unit 101. The demodulation unit 110 outputs the demodulation result to the decoding unit 111, for example.
[0174] The decoding unit 111 performs error correction decoding on the uplink signal (e.g., PUSCH) based on information input from the control unit 101 and demodulation results input from the demodulation unit 110, and obtains the decoded received bit sequence.
[0175] [Terminal Structure]
[0176] Figure 22 This is a block diagram illustrating a structural example of a terminal 200 according to an embodiment of the present disclosure. For example, in Figure 22 In the terminal 200, there are receiving unit 201, extraction unit 202, demodulation unit 203, decoding unit 204, control unit 205, encoding unit 206, modulation unit 207, signal distribution unit 208 and transmitting unit 209.
[0177] It should be noted that, Figure 22 At least one of the receiving unit 201 and the transmitting unit 209 shown may be included Figure 3 In the communication section shown. Additionally... Figure 22At least one of the extraction unit 202, demodulation unit 203, decoding unit 204, control unit 205, encoding unit 206, modulation unit 207, signal distribution unit 208, and transmission unit 209 shown may be included. Figure 3 In the control unit shown.
[0178] The receiving unit 201 receives downlink signals (e.g., downlink data signals or downlink control information) from the base station 100 via an antenna, and performs RF processing such as down-conversion or A / D conversion on the received wireless signal to obtain a received signal (baseband signal). Alternatively, when receiving OFDM signals, the receiving unit 201 performs FFT processing on the received signal to convert it to the frequency domain. The receiving unit 201 then outputs the received signal to the extraction unit 202.
[0179] For example, the extraction unit 202 extracts radio resource portions that may contain downlink control information from the received signal input by the receiving unit 201 based on radio resource information related to downlink control information input from the control unit 205, and outputs it to the demodulation unit 203. Additionally, the extraction unit 202 extracts radio resource portions containing downlink data signals based on radio resource information related to data signals input from the control unit 205, and outputs it to the demodulation unit 203.
[0180] The demodulation unit 203 demodulates the signal (e.g., PDCCH or PDSCH) input from the extraction unit 202 based on information input from the control unit 205, and outputs the demodulation result to the decoding unit 204.
[0181] The decoding unit 204 uses the demodulation result input from the demodulation unit 203 to perform error correction decoding on the PDCCH or PDSCH, for example, to obtain higher-layer control signals or downlink control information. The decoding unit 204 outputs the higher-layer control signals and downlink control information to the control unit 205. In addition, the decoding unit 204 can generate a response signal (e.g., ACK / NACK) based on the decoding result of the PDSCH.
[0182] The control unit 205, for example, performs uplink transmission control (including determining information related to PUSCH retransmission, such as the DMRS port or pre-DFT OCC sequence for PUSCH transmission) based on information related to PUSCH transmission obtained from signals input from the decoding unit 204 (e.g., higher-layer control signals or downlink control information) according to the method described above. The control unit 205 outputs the determined information to the encoding unit 206 and the signal distribution unit 208, for example.
[0183] The encoding unit 206 encodes, for example, the uplink data signal (UL data signal) or the uplink control signal based on information input from the control unit 205. The encoding unit 206 outputs the encoded bit string to the modulation unit 207.
[0184] The modulation unit 207 modulates, for example, the encoded bit string input from the encoding unit 206, and outputs the modulated signal (symbol string) to the signal distribution unit 208.
[0185] The signal allocation unit 208 maps a signal (e.g., a sequence) input from the modulation unit 207 to radio resources, for example, based on information input from the control unit 205. The signal allocation unit 208 then outputs the mapped uplink signal to the transmission unit 209, for example.
[0186] The transmitting unit 209 generates a transmit signal waveform, such as OFDM, from the signal input from the signal distribution unit 208. Additionally, in the case of OFDM transmission using CP, the transmitting unit 209 performs IFFT processing on the signal and appends CP to the IFFT-generated signal. Alternatively, in the case of generating a single-carrier waveform, the transmitting unit 209 may add a DFT unit (not shown) after the modulation unit 207 or before the signal distribution unit 208. Furthermore, the transmitting unit 209 performs RF processing on the transmit signal, such as D / A conversion and up-conversion, and transmits the wireless signal to the base station 100 via an antenna.
[0187] (Other implementation methods)
[0188] In the above embodiments, the DCI format is not limited to DCI format 0-1 and DCI format 0-2, but can also be other formats. DCI format 0-0 is sometimes referred to as a fallback DCI format, for example. DCI format 0-1 is sometimes referred to as a non-fallback DCI format, for example. In addition, in the above embodiments, the type, number, and size (number of bits) of the information fields included in the DCI are just examples; DCI formats containing other types, numbers, or sizes of information fields can also be used.
[0189] Furthermore, in the above embodiments, the channel used for uplink transmission (or the channel for repeated transmission) is not limited to PUSCH, but can also be other channels. Additionally, the type of information transmitted is not limited to data, but can also be other types of information (e.g., uplink control signals (PUCCH)). Furthermore, one embodiment of this disclosure is not limited to uplink transmission, but can also be applied to downlink transmission or sidelink transmission.
[0190] This disclosure can be applied, for example, to inter-terminal communication such as sidelink communication.
[0191] Furthermore, one embodiment of this disclosure can be applied without relying on satellite types such as geostationary Earth Orbit (GEO), medium Earth Orbit (MEO), low Earth Orbit (LEO), or highly elliptical Orbit (HEO). Additionally, one embodiment of this disclosure can also be applied, for example, to non-terrestrial communications such as HAPS or drone base stations.
[0192] Furthermore, while the above embodiments have been described using an NTN environment (e.g., a satellite communication environment) as an example, this disclosure is not limited thereto. This disclosure can also be applied to other communication environments (e.g., terrestrial cellular environments of at least one of LTE and NR). For example, one embodiment of this disclosure can also be applied to terrestrial communication in environments with large cell sizes and long propagation delays (e.g., above a threshold) between base station 100 and terminal 200.
[0193] Furthermore, in the above embodiments, satellite communication can be a structure where the base station function resides on a satellite (e.g., a "regenerative satellite"), or a structure where the base station function resides on the ground and the satellite relays communication between the base station and the terminal (e.g., a "transparent satellite"). For example, in one embodiment of this disclosure, the downlink and uplink can be links between the terminal and the satellite, or links via the satellite.
[0194] In addition, in this disclosure, the downlink control channel, downlink data channel, uplink control channel, and uplink data channel are not limited to PDCCH, PDSCH, PUCCH, and PUSCH, respectively, and may also be control channels with other names.
[0195] In addition, RRC signaling is envisioned as higher-layer signaling in this disclosure, but it can also be replaced by Medium Access Control (MAC) signaling and notifications in DCI as physical layer signaling.
[0196] Furthermore, in this disclosure, the orthogonal sequence is not limited to the OCC sequence (e.g., a sequence obtained by cyclically shifting the OCC sequence), but may be other sequences. Additionally, the reference signal associated with the orthogonal sequence is not limited to DMRS, but may be other reference signals. Furthermore, in the above embodiments, the output results after applying pre-DFT OCC and DFT, and the frequency resources used for DMRS, have a comb-like structure, but this is not a limitation; at least one of them may not have a comb-like structure.
[0197] The settings for parameters such as the number of RBs allocated, the number of subcarriers (or REs) constituting one RB, the OCC sequence (e.g., sequence length, spread factor, or sequence element), and the number of DMRS ports (e.g., maximum number) are not limited to the examples above and can also be other values. Furthermore, the DMRS settings are not limited to DMRS configuration type 1 and can also be other settings.
[0198] Furthermore, in this disclosure, the extension using pre-DFT OCC can also be combined with other extension methods (e.g., OCC applied between OFDM symbols or OCC applied between time slots). For example, in the case of multiplexing 4 UEs, inter-time slot OCC with an OCC sequence length of 2 and pre-DFT OCC with a sequence length of 2 can be combined.
[0199] (Replenish)
[0200] Information indicating whether terminal 200 supports the functions, operations, or processes shown in the above embodiments and supplements can also be sent (or notified) by terminal 200 to base station 100 as capability information or capability parameters of terminal 200.
[0201] The capability information may also include an information element indicating whether the terminal 200 supports at least one of the functions, operations, and processes described in the above embodiments, variations, and supplements. Alternatively, the capability information may include an information element indicating whether the terminal 200 supports two or more combinations of the functions, operations, and processes described in the above embodiments, variations, and supplements.
[0202] Base station 100 can, for example, determine (or decide or envision) the functions, operations, or processes supported (or not supported) by the source terminal 200, based on capability information received from terminal 200. Base station 100 can implement operations, processes, or controls corresponding to the determination results based on the capability information. For example, base station 100 can control uplink-related processing based on the capability information received from terminal 200.
[0203] It should be noted that terminal 200 does not support some of the functions, operations, or processes shown in the above embodiments, modifications, and supplements. Alternatively, in terminal 200, such functions, operations, or processes may be limited. For example, information or requests related to such limitations may also be notified to base station 100.
[0204] Information related to the capabilities or limitations of terminal 200 may be defined in a standard, or may be implicitly communicated to base station 100 in association with information known to base station 100 or information sent to base station 100.
[0205] The above describes various implementations, modifications, and additions of a non-limiting embodiment of this disclosure.
[0206] (Control signal)
[0207] In this disclosure, the downlink control signal (or downlink control information) associated with an embodiment of this disclosure may be, for example, a signal (or information) transmitted in the Physical Downlink Control Channel (PDCCH) of the physical layer, or a signal (or information) transmitted in a higher-layer Medium Access Control Element (MAC CE) or Radio Resource Control (RRC). Furthermore, the signal (or information) is not limited to being notified by a downlink control signal; it may also be predefined in a specification (or standard) or pre-set in the base station and terminal.
[0208] In this disclosure, the uplink control signal (or uplink control information) associated with an embodiment of this disclosure may be, for example, a signal (or information) transmitted in the physical layer PUCCH, or a signal (or information) transmitted in the higher layer MAC CE or RRC. Furthermore, the signal (or information) is not limited to being notified by the uplink control signal; it may also be predefined in a specification (or standard), or pre-set in the base station and terminal. Additionally, the uplink control signal may be replaced, for example, with uplink control information (UCI), first-stage sidelink control information (SCI), or second-stage SCI.
[0209] (Base station)
[0210] In one embodiment of this disclosure, the base station can be a Transmission Reception Point (TRP), cluster head, access point, Remote Radio Head (RRH), eNodeB (eNB), gNodeB (gNB), Base Station (BS), Base Transceiver Station (BTS), host, gateway, etc. Alternatively, in sidelink communication, the functions of the base station can also be performed by the terminal. Instead of a base station, it can also be a relay device for communication between a high-level relay node and the terminal. Additionally, it can be a roadside device.
[0211] (Uplink / Downlink / Sidelink)
[0212] An embodiment of this disclosure can be applied, for example, to any link in the uplink, downlink, or sidelink. For example, an embodiment of this disclosure can be applied to the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH) of the uplink, the Physical Downlink Shared Channel (PDSCH), PDCCH, Physical Broadcast Channel (PBCH) of the downlink, or the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and Physical Sidelink Broadcast Channel (PSBCH) of the sidelink.
[0213] It should be noted that PDCCH, PDSCH, PUSCH, and PUCCH are examples of downlink control channel, downlink data channel, uplink data channel, and uplink control channel, respectively. Additionally, PSCCH and PSSCH are examples of sidelink control channel and sidelink data channel, respectively. Furthermore, PBCH and PSBCH are examples of broadcast channels, and PRACH is an example of a random access channel.
[0214] (Data channel / Control channel)
[0215] An embodiment of this disclosure can be applied, for example, to any channel in the data channel and the control channel. For example, the channel in an embodiment of this disclosure can also be replaced with one of the data channel's PDSCH, PUSCH, PSSCH, and the control channel's PDCCH, PUCCH, PBCH, PSCCH, PSBCH.
[0216] (Reference signal)
[0217] In one embodiment of this disclosure, the reference signal is, for example, a signal known to both the base station and the mobile station, and is sometimes referred to as "RS (Reference Signal)" or "pilot signal". The reference signal can also be one of the following: Demodulation Reference Signal (DMRS), Channel State Information-Reference Signal (CSI-RS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell-specific Reference Signal (CRS), or Sounding Reference Signal (SRS).
[0218] (Time interval)
[0219] In one embodiment of this disclosure, the unit of time resource is not limited to one or a combination of time slots and symbols. For example, it can be a time resource unit such as a frame, superframe, subframe, time slot, time slot, sub-time slot, micro-time slot, or symbol, Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier-Frequency Division Multiplexing Access (SC-FDMA) symbol, or other time resource units. Furthermore, the number of symbols contained in one time slot is not limited to the number of symbols exemplified in the above embodiments, and can also be other numbers of symbols.
[0220] (frequency band)
[0221] One embodiment of this disclosure can be applied to any band domain, whether it is an authorized band domain or an unauthorized band domain.
[0222] (communication)
[0223] One embodiment of this disclosure can be applied to any communication in base station-terminal communication (Uu link communication), terminal-to-terminal communication (sidelink communication), and vehicle-to-everything (V2X) wireless communication technology. For example, the channel in one embodiment of this disclosure can be replaced with one of PSCCH, PSSCH, Physical Sidelink Feedback Channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.
[0224] Furthermore, one embodiment of this disclosure can be applied to any network, including terrestrial networks and non-terrestrial networks (NTNs) that use satellites or High Altitude Pseudo Satellites (HAPS). Additionally, one embodiment of this disclosure can also be applied to terrestrial networks with transmission delays greater than the symbol length or time slot length, such as networks with large cell sizes and ultra-wideband transmission networks.
[0225] (SBFD)
[0226] In one embodiment of this disclosure, operations on uplink, downlink, and sidelink symbols can also be applied to symbols (e.g., SBFD symbols) used for SBFD (Subband Non-overlapping Full-Duplex) operations or control. In an SBFD symbol, the frequency domain (or frequency resources, frequency band) is divided into multiple frequency domains (e.g., also called subbands, RB sets, sub-bands, sub-BWPs (BandWidth Parts)). The terminal transmits and receives in different directions (e.g., downlink or uplink) based on the divided areas, i.e., subbands. In an SBFD symbol, the terminal can transmit and receive in one direction of the uplink and downlink, but not in the other direction. Alternatively, the base station can also be configured to transmit and receive simultaneously in both the uplink and downlink. It is possible that, compared to symbols that only transmit and receive in the downlink, the SBFD symbol has less frequency domain available for the downlink. Additionally, it is possible that, compared to symbols that only transmit and receive in the uplink, the SBFD symbol has less frequency domain available for the uplink.
[0227] Alternatively, in SBFD symbols, the terminal can simultaneously transmit and receive uplink and downlink signals. In this case, the frequency domain for transmission and reception can be non-adjacent, leaving a frequency gap (also known as a frequency interval).
[0228] In addition, as different transmission and reception directions per sub-band (i.e., segmented area) unit, it may also include transmission and reception of side links.
[0229] (XDD: Cross-segment duplex)
[0230] In one embodiment of this disclosure, the operations for uplink, downlink, and sidelink symbols can also be applied to symbols for full-duplex operation or control (e.g., full-duplex symbols). In a full-duplex symbol, both the terminal and the base station can simultaneously transmit and receive uplink and downlink signals. A full-duplex symbol can employ simultaneous transmission and reception by the terminal and base station in the available frequency domain (or frequency resources, frequency band), or it can employ simultaneous transmission and reception in a portion of the frequency domain (i.e., transmission or reception can be performed in a frequency domain other than the available frequency domain). In this case, the frequency domains for transmission and reception by the base station or terminal may not be adjacent, but rather have a frequency gap (also called a frequency interval). Additionally, for example, for the purpose of reducing interference, operations where one of the terminal and the base station can simultaneously transmit and receive can be employed (i.e., the other party can either transmit or receive).
[0231] Furthermore, full-duplex operation can also be applied to terminals that can simultaneously perform sidelink transmission and reception. Additionally, full-duplex operation can also be applied to terminals that can simultaneously perform sidelink and uplink or downlink transmission and reception.
[0232] (Antenna port)
[0233] In one embodiment of this disclosure, an antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. For example, an antenna port may not necessarily refer to a single physical antenna; sometimes it refers to an array antenna composed of multiple antennas. For instance, instead of specifying how many physical antennas constitute an antenna port, it may be defined as the smallest unit that the terminal station can transmit a reference signal. Additionally, an antenna port is sometimes also defined as the smallest unit multiplied by a precoding vector.
[0234] <5G NR System Architecture and Protocol Stack>
[0235] The overall 5G NR system architecture is envisioned to include the gNB's NG-RAN (Next Generation Radio Access Network). The gNB provides UE-side termination for the NG radio access user plane (SDAP (Service Data Adaptation Protocol) / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY (Physical Layer)) and control plane (RRC) protocols. gNBs are interconnected via the Xn interface. Additionally, the gNB connects to the NGC (Next Generation Core) via the Next Generation (NG) interface, and more specifically, to the AMF (Access and Mobility Management Function) (e.g., a specific core entity implementing the AMF) via the NG-C interface, and to the UPF (User Plane Function) (e.g., a specific core entity implementing the UPF) via the NG-U interface. Figure 23 This refers to the NG-RAN architecture (e.g., refer to 3GPP TS 38.300 v15.6.0, section 4).
[0236] <The process of setting up and reconfiguring RRC connections>
[0237] The following illustrates the interaction between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE (RRC idle) to RRC_CONNECTED (RRC connected) in the NAS section (refer to TS 38.300 v15.6.0).
[0238] RRC is a higher-level signaling (protocol) used for UE and gNB configuration. The AMF prepares UE context data (which may include, for example, PDU session context, security key, UE radio capabilities, and UE security capabilities) and sends it to the gNB along with an initial context setting request. Next, the gNB and UE activate AS security together. This is done by the gNB sending a Security Mode Command message to the UE, which responds with a Security Mode Complete message. Then, the gNB sends an RRC Reconfiguration message to the UE, and receives an RRC Reconfiguration Complete message from the UE for this message. This allows for the reconfiguration of the Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, since SRB2 and DRB are not configured, the steps related to RRC reconfiguration can be omitted. Finally, the gNB notifies the AMF that the configuration process is complete using the Initial Context Setup Reply.
[0239] Therefore, this disclosure provides an entity (e.g., AMF, SMF, etc.) of a fifth-generation core network (5GC), comprising: a control circuit that, during operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmission unit that, during operation, sends an initial context setting message to the gNodeB via the NG connection to set the signaling radio bearer between the gNodeB and the User Equipment (UE). Specifically, the gNodeB sends Radio Resource Control (RRC) signaling containing a Resource Allocation Setting Information Element (IE) to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation settings.
[0240] <QoS Control>
[0241] 5G's QoS (Quality of Service) model is based on QoS flows, supporting both QoS flows that require guaranteed bit rate (GBR) and QoS flows that do not require guaranteed bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows represent the finest granular QoS classification within a PDU session. QoS flows are determined within a PDU session based on the QoS Flow ID (QFI) transmitted via the encapsulation header through the NG-U interface.
[0242] For each UE, the 5GC establishes one or more PDU sessions. For each UE, in conjunction with the PDU session, for example, the NG-RAN establishes at least one Data Radio Bearer (DRB). Additionally, for the QoS flows of this PDU session, additional DRBs can be configured later (when to configure depends on the NG-RAN). The NG-RAN maps packets belonging to various PDU sessions to various DRBs. NAS-level packet filters in the UE and 5GC are used to associate UL packets and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.
[0243] (Open-RAN)
[0244] The base station described in the various embodiments (e.g., a 5G NR base station referred to as gNB) can be composed of three functional modules: a centralized unit (CU), a distributed unit (DU), and a radio unit (RU).
[0245] A CU can be referred to as a centralized node, aggregation node, centralized station, aggregation station, or centralized unit. A DU can be referred to as an O-DU (O-RAN Distributed Unit), distributed node, distributed station, or distributed unit. A RU can be referred to as an O-RU (O-RAN Radio Unit), radio device, radio node, radio station, antenna unit, or radio unit.
[0246] The functional split configuration (or functional split point) between CU, DU, and RU specifies multiple split options. The term "functional split point" is sometimes also referred to as "split", "option", or "split option".
[0247] An example of the “segmentation options” is the following segmentation options 1 to 8. The functions of the base station described in the various embodiments can be segmented into CU, DU, RU by one of the following segmentation options 1 to 8. For example, functional segmentation can be performed between CU, DU, and RU, or only between CU and DU or between DU and RU.
[0248] (1) Split Option 1: Between RRC (Radio Resource Control) and PDCP
[0249] (2) Segmentation Option 2: Between PDCP and RLC (High-RLC)
[0250] (3) Segmentation Option 3: Between High-RLC and Low-RLC
[0251] (4) Segmentation Option 4: Between RLC (Low-RLC) and MAC (High-MAC)
[0252] (5) Splitting option 5: Between High-MAC and Low-MAC
[0253] (6) Segmentation Option 6: Between MAC (Low-MAC) and PHY (High-PHY)
[0254] (7) Splitting option 7: Between High-PHY and Low-PHY
[0255] (8) Splitting option 8: Between PHY (Low-PHY) and RF
[0256] The functional split point between the CU and O-DU can be Split Option 2. The connection between the CU and O-DU is called midhaul, and 3GPP specifies the F1 interface. Alternatively, the connection between the O-DU and O-RU is called fronthaul, and its functional split point can be Split Option 7-2x, which is adopted as the O-RAN fronthaul specification.
[0257] An example of splitting the gNB base station function into CU, O-DU, and O-RU using Split Option 2 and Split Option 7-2x is shown below. Figure 24 .
[0258] For example, a CU can have RRC (Radio Resource Control) functionality, SDAP (Service Data Adaptation Protocol) functionality, and PDCP (Packet Data Convergence Protocol) functionality.
[0259] For example, an O-DU can possess RLC (Radio Link Control) functionality, MAC functionality, and high-PHY functionality. Additionally, the high-PHY functionality can include encoding, scrambling, modulation, layer mapping, precoding, and RE (Resource Element) mapping functions for downlink (DL) transmission. Furthermore, the high-PHY functionality can include decoding, descrambling, demodulation, layer demapping, and RE (Resource Element) demapping functions for uplink (UL) reception.
[0260] For example, an O-RU can possess low-level physical layer (Low-PHY) functionality and RF functionality. Additionally, the Low-PHY functionality can include beamforming, IFFT (Inverse First Fourier Transform) + CP (Cyclic Prefix) addition, and D / A (Digital to Analog) conversion for downlink transmission. Furthermore, the Low-PHY functionality can include A / D (Analog to Digital) conversion, CP removal + FFT (First Fourier Transform), and beamforming for uplink reception.
[0261] In addition, when the O-DU does not have precoding capabilities, the O-RU can have precoding capabilities.
[0262] O-RU can have LBT (listen before talk) related functions.
[0263] As the communication method between O-DU and O-RU in Split Option 7-2x, eCPRI (Evolved Common Public Radio Interface) is specified. In Split Option 7-2x, eCPRI, in addition to transmitting and receiving sampled sequences of in-phase (I) and quadrature (Q) components of OFDM signals in the frequency domain, also transmits and receives information for beamforming in the antenna and timing synchronization signals.
[0264] Information transmitted using the signals (PDCCH, PUCCH, PDSCH, PUSCH, MAC CE, RRC, etc.) described in the various embodiments can be transmitted between O-DU and O-RU via the eCPRI user plane (U-Plan) or control plane (C-Plane).
[0265] When the functions described in the various embodiments are executed in the O-RU through function partitioning, the O-DU can use control signals (e.g., eCPRI) between the O-DU and the O-RU to send information for controlling the function, thereby controlling the O-RU.
[0266] When the functions described in the various embodiments are executed in the O-DU through function partitioning, the O-RU can receive the result of the function being executed in the O-DU through a control signal (e.g., eCPRI) and control the O-RU based on the received result.
[0267] The functions of CU, O-DU, and O-RU can be configured (deployed) in physically different devices connected by optical fibers, or some or all of their functions can be configured in physically identical devices.
[0268] CU and O-DU can be logical entities implemented as virtualized RAN (vRAN: virtual radio access network), or as software running on cloud servers, etc. Furthermore, some or all of the functions of CU and O-DU can be provided as services of Network Functions Virtualization (NFV).
[0269] A transceiver is not necessarily a wireless transceiver; it can be a network transceiver, an optical transceiver, etc. The radio resources allocated by the O-DU can be resources used for wireless communication between the O-RU and the UE.
[0270] This disclosure can be implemented by software, hardware, or software in collaboration with hardware.
[0271] The functional blocks used in the above embodiments are implemented partially or wholly as LSIs (Large Scale Integration) of integrated circuits. The processes described in the above embodiments can also be controlled partially or wholly by a single LSI or a combination of LSIs. An LSI can be composed of individual chips, or it can be composed of a single chip containing part or all of the functional blocks. An LSI may also include data input and output. Depending on the degree of integration, an LSI may also be called an "IC (Integrated Circuit)," a "System LSI," a "Super LSI," or an "Ultra LSI."
[0272] The method of integrating the LSI is not limited to LSI; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Alternatively, it can utilize a programmable FPGA (Field Programmable Gate Array) manufactured using the LSI, or a reconfigurable processor that allows reconfiguration of the connections or configurations of the circuit blocks within the LSI. This disclosure can also be implemented for digital or analog processing.
[0273] Furthermore, if advancements in semiconductor technology or the emergence of other derivative technologies lead to integrated circuit technologies that can replace LSIs, these technologies could also be used to integrate functional blocks. There are also possibilities for applications such as biotechnology.
[0274] This disclosure can be implemented in all kinds of devices, apparatuses, and systems with communication capabilities (collectively referred to as "communication devices"). A communication device may also include a wireless transceiver and processing / control circuitry. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these units. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or similar devices. Non-limiting examples of communication devices include: telephones (mobile phones, smartphones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, laptops, etc.), cameras (digital cameras, digital camcorders, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, e-book readers, remote health / telemedicine (remote healthcare / medical prescription) devices, vehicles or transportation vehicles with communication capabilities (cars, airplanes, ships, etc.), and combinations of the various devices described above.
[0275] Communication devices are not limited to portable or movable devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed. Examples include: smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.
[0276] In addition to data communication via cellular systems, wireless LAN (Local Area Network) systems, and communication satellite systems, communication also includes data communication via a combination of these systems.
[0277] In addition, the communication device also includes devices such as controllers or sensors that are connected or linked to a communication device performing the communication functions described in this disclosure. For example, it includes a controller or sensor that generates control signals or data signals used by the communication device to perform the communication functions of the communication device.
[0278] In addition, the communication device includes infrastructure equipment that communicates with or controls the various devices described above (not limited to these), such as base stations, access points, and all other devices, equipment, and systems.
[0279] A terminal according to an embodiment of this disclosure includes: a control circuit that determines an orthogonal sequence having the following relationship: at least a portion of a frequency domain output result obtained by applying the orthogonal sequence to a signal before a Discrete Fourier Transform (DFT) and applying the DFT to the signal is mapped to a frequency resource for demodulating a reference signal; and a transmission circuit that transmits the signal to which the orthogonal sequence has been applied.
[0280] In one embodiment of this disclosure, the orthogonal sequence is a sequence obtained by cyclically shifting the orthogonal covering code (OCC) sequence.
[0281] In one embodiment of this disclosure, the demodulation reference signal is configured using DMRS configuration type 1.
[0282] In one embodiment of this disclosure, the control circuit determines the orthogonal sequence having the following relationship: the interval of the frequency resources in the comb structure of the output result is an integer multiple of the interval of the frequency resources used for the DMRS.
[0283] A terminal according to one embodiment of this disclosure includes: a control circuit that, when an orthogonal sequence is applied to a signal before a Discrete Fourier Transform (DFT), controls a frequency resource allocation unit based on the length of the orthogonal sequence; and a transmission circuit that transmits the signal using the frequency resources allocated based on the allocation unit.
[0284] In a terminal of one embodiment of this disclosure, the allocation unit is N resource blocks, where N is the smallest integer satisfying the following condition: the length of the orthogonal sequence is a multiple of 2 and a divisor of (12×N).
[0285] A terminal according to one embodiment of this disclosure includes: a control circuit that, when applying an orthogonal sequence to a signal before a Discrete Fourier Transform (DFT), determines the orthogonal sequence based on the value of a field of a port of a notification demodulation reference signal included in downlink control information; and a transmission circuit that transmits the signal to which the orthogonal sequence has been applied.
[0286] A base station according to an embodiment of this disclosure includes: a control circuit that determines an orthogonal sequence having the following relationship: at least a portion of a frequency domain output result obtained by applying the orthogonal sequence to a signal before a Discrete Fourier Transform (DFT) and applying the DFT to the signal is mapped to frequency resources for demodulating a reference signal; and a receiving circuit that receives the signal to which the orthogonal sequence has been applied.
[0287] In a communication method according to an embodiment of this disclosure, a terminal performs the following steps: determining an orthogonal sequence having the following relationship: at least a portion of the frequency domain output obtained by applying the orthogonal sequence to the signal before the Discrete Fourier Transform (DFT) and applying the DFT to the signal is mapped to frequency resources for demodulating a reference signal; and transmitting the signal to which the orthogonal sequence has been applied.
[0288] In a communication method according to an embodiment of this disclosure, a base station performs the following steps: determining an orthogonal sequence having the following relationship: at least a portion of the frequency domain output obtained by applying the orthogonal sequence to the signal before the Discrete Fourier Transform (DFT) and applying the DFT to the signal is mapped to frequency resources for demodulating a reference signal; and receiving the signal to which the orthogonal sequence has been applied.
[0289] The entire contents of the specification, drawings and abstract of the specification contained in Japanese Patent Application No. 2024-022167, filed on February 16, 2024, are incorporated herein by reference.
[0290] Industrial applicability
[0291] One embodiment of this disclosure is useful for wireless communication systems.
[0292] Explanation of reference numerals in the attached figures
[0293] 100 base stations
[0294] 101, 205 Control Department
[0295] 102 High-rise control signal generation unit
[0296] 103 Downlink Control Information Generation Unit
[0297] Coding sections 104 and 206
[0298] Modulation sections 105 and 207
[0299] Signal Distribution Sections 106 and 208
[0300] 107, 209 Sending Department
[0301] Receiving Departments 108 and 201
[0302] Extraction sections 109 and 202
[0303] 110, 203 De-escalation Department
[0304] Decoding sections 111 and 204
[0305] 200 terminals
Claims
1. A terminal, characterized in that, have: The control circuit determines an orthogonal sequence having the following relationship: at least a portion of the frequency domain output obtained by applying the orthogonal sequence to the signal before the Discrete Fourier Transform (DFT) and applying the DFT to the signal is mapped to frequency resources for demodulating the reference signal. as well as The transmitting circuit transmits the signal that applies the orthogonal sequence.
2. The terminal as described in claim 1, wherein, The orthogonal sequence is the sequence obtained by cyclically shifting the orthogonal covering code OCC sequence.
3. The terminal as described in claim 1, wherein, The demodulation reference signal is configured using DMRS configuration type 1.
4. The terminal as described in claim 3, wherein, The control circuit determines the orthogonal sequence having the following relationship: the interval of the frequency resources in the comb structure of the output result is an integer multiple of the interval of the frequency resources used for the DMRS.
5. A terminal, characterized in that, have: The control circuit, when applying an orthogonal sequence to the signal before the Discrete Fourier Transform (DFT), controls the allocation unit of frequency resources based on the length of the orthogonal sequence; and The transmitting circuit transmits the signal using the frequency resources allocated based on the allocation unit.
6. The terminal as described in claim 5, wherein, The allocation unit is N resource blocks, where N is the smallest integer that satisfies the following condition: the length of the orthogonal sequence is a multiple of 2 and a divisor of (12×N).
7. A terminal, characterized in that, have: The control circuit, when applying an orthogonal sequence to the signal before the Discrete Fourier Transform (DFT), determines the orthogonal sequence based on the value of the field of the port notifying the demodulation reference signal contained in the downlink control information; and The transmitting circuit transmits the signal that applies the orthogonal sequence.
8. A base station, characterized in that, have: The control circuit determines an orthogonal sequence having the following relationship: at least a portion of the frequency domain output obtained by applying the orthogonal sequence to the signal before the Discrete Fourier Transform (DFT) and applying the DFT to the signal is mapped to frequency resources for demodulating the reference signal. as well as A receiving circuit that receives the signal to which the orthogonal sequence has been applied.
9. A communication method, characterized in that, The terminal performs the following steps: An orthogonal sequence is determined to have the following relationship: at least a portion of the frequency domain output obtained by applying the orthogonal sequence to the signal before the Discrete Fourier Transform (DFT) and applying the DFT to the signal is mapped to frequency resources for demodulating the reference signal. as well as The signal that applies the orthogonal sequence is sent.
10. A communication method, characterized in that, The base station performs the following steps: An orthogonal sequence is determined to have the following relationship: at least a portion of the frequency domain output obtained by applying the orthogonal sequence to the signal before the Discrete Fourier Transform (DFT) and applying the DFT to the signal is mapped to frequency resources for demodulating the reference signal. as well as The signal that has been applied with the orthogonal sequence is received.
Citation Information
Patent Citations
Power supply device
JP2024022167A