Terminal and communication method

Abstract

A terminal has a reception section that receives a parameter relating to PRACH (Physical random access channel) setting from a base station, a control section that decides a preamble and a resource of a PRACH opportunity based on the PRACH setting, and a transmission section that transmits a PRACH to the base station using the preamble and the resource, the reception section receiving a notification of use of an adapted PRACH setting.

Description

Technical Field

[0001] This invention relates to terminals and communication methods in wireless communication systems. Background Technology

[0002] In NR (New Radio) (also known as "5G"), which is the successor system to LTE (Long Term Evolution), technologies are being researched to meet the requirements of high-capacity systems, high-speed data transmission, low latency, simultaneous connection of multiple terminals, low cost, and power saving (e.g., Non-Patent Literature 1).

[0003] Furthermore, in 3GPP (registered trademark) version 18, in order to achieve environmental sustainability, carbon neutrality, SDGs (Sustainable Development Goals), and reduce operating costs, the importance of network energy savings has increased, and methods for energy saving are being studied (e.g., non-patent literature 2).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent literature 1: 3GPP TS 38.300 V17.7.0 (2023-12)

[0007] Non-patent document 2: "New WID: Enhancements of network energy savings for NR", RP-234065, 3GPP TSG RAN Meeting #102, December 2023

[0008] Non-patent literature 3: 3GPP TS 38.211 V17.6.0 (2023-09)

[0009] Non-patent literature 4: 3GPP TS 38.331 V17.7.0 (2023-12)

[0010] Non-patent literature 5: 3GPP TS 38.213 V17.8.0 (2023-12) Summary of the Invention

[0011] The problem that the invention aims to solve

[0012] To achieve carbon neutrality and the SDGs, the importance of saving base station power consumption has increased, and the introduction of intermittent transmission and reception in base stations is being studied. To achieve an efficient power-saving (ES) state for base stations, the structure of the PRACH (Physical Random Access Channel) needs to be suitable. Terminals are required to use this PRACH to synchronize with the base station in power-saving mode.

[0013] The present invention was made in view of the above-mentioned problems, and its purpose is to make the random access channel suitable for base stations that can migrate to a power-saving state.

[0014] Methods for solving problems

[0015] According to the disclosed technology, a terminal is provided, comprising: a receiving unit that receives parameters related to PRACH (Physical Random Access Channel) settings from a base station; a control unit that determines resources for a preamble and PRACH opportunities based on the PRACH settings; and a transmitting unit that transmits PRACH to the base station using the preamble and the resources, wherein the receiving unit receives a notification using an adapted PRACH setting.

[0016] Invention Effects

[0017] According to publicly available technology, random access channels can be adapted to base stations that can migrate to power-saving states. Attached Figure Description

[0018] Figure 1 This is a diagram illustrating a wireless communication system according to an embodiment of the present invention.

[0019] Figure 2 This is a diagram used to illustrate CDRX in NR version 15.

[0020] Figure 3 This is a diagram used to illustrate WUS in NR version 16.

[0021] Figure 4 This is a diagram illustrating the intermittent reception of a base station according to Embodiment 1 of the present invention.

[0022] Figure 5 This is a diagram illustrating the parameters involved in Embodiment 1 of the present invention.

[0023] Figure 6 This is a diagram illustrating the intermittent transmission of a base station according to Embodiment 5 of the present invention.

[0024] Figure 7This is a diagram illustrating the parameters involved in Embodiment 5 of the present invention.

[0025] Figure 8 This is a diagram illustrating an example of the PRACH format according to Embodiment 9 of the present invention.

[0026] Figure 9 This is a diagram illustrating an example of a time-domain PRACH resource according to Embodiment 9 of the present invention.

[0027] Figure 10 This is a diagram illustrating an example of frequency domain PRACH resources according to Embodiment 9 of the present invention.

[0028] Figure 11 This is a diagram illustrating an example of the association between SSB and PRACH resources according to Embodiment 9 of the present invention.

[0029] Figure 12 This is a diagram illustrating a variation of SIB1 according to Embodiment 9 of the present invention.

[0030] Figure 13 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0031] Figure 14 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0032] Figure 15 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0033] Figure 16 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0034] Figure 17 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0035] Figure 18 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0036] Figure 19 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0037] Figure 20 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0038] Figure 21 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0039] Figure 22 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0040] Figure 23 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0041] Figure 24 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0042] Figure 25 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0043] Figure 26 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention.

[0044] Figure 27 This is a diagram illustrating an example of the PRACH resources of each SSB involved in Embodiment 9 of the present invention.

[0045] Figure 28 This is a diagram illustrating an example of a PRACH resource associated with an SSB, as described in Embodiment 9 of the present invention.

[0046] Figure 29 This is a diagram illustrating an example of a PRACH resource associated with an SSB, as described in Embodiment 9 of the present invention.

[0047] Figure 30 This is a diagram illustrating a specification change example related to the RACH setting in Embodiment 9, which is used to explain the implementation of the present invention.

[0048] Figure 31 This is a diagram illustrating a specification change example related to the RACH setting in Embodiment 9, which is used to explain the implementation of the present invention.

[0049] Figure 32 This is a diagram illustrating a specification change example related to the RACH setting in Embodiment 9, which is used to explain the implementation of the present invention.

[0050] Figure 33 This is a diagram illustrating an example of associating SSB with RO in Embodiment 9, which is used to explain an implementation of the present invention.

[0051] Figure 34 This is a diagram illustrating examples of specification changes involved in multiple RACH settings in Embodiment 9, which is used to explain the implementation of the present invention.

[0052] Figure 35 This is a diagram illustrating an example of the functional structure of a base station according to an embodiment of the present invention.

[0053] Figure 36 This is a diagram illustrating an example of the functional structure of a terminal according to an embodiment of the present invention.

[0054] Figure 37 This is a diagram illustrating an example of the hardware structure of a base station or terminal according to an embodiment of the present invention.

[0055] Figure 38 This is a diagram illustrating an example of the structure of a vehicle according to an embodiment of the present invention. Detailed Implementation

[0056] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Furthermore, the embodiments described below are merely examples, and the application of the present invention is not limited to the embodiments described below.

[0057] In the operation of the wireless communication system according to embodiments of the present invention, existing technologies may be appropriately used. These existing technologies include, for example, existing NR or LTE, but are not limited to, existing NR or LTE. Furthermore, unless otherwise stated, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and subsequent methods (e.g., NR).

[0058] Furthermore, in the embodiments of the present invention described below, the terms SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE systems are used. These are for ease of description, and the same signals and functions may also be referred to by other names. In addition, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily explicitly written as "NR-".

[0059] Furthermore, in embodiments of the present invention, the duplex mode can be TDD (Time Division Duplex), FDD (Frequency Division Duplex), or other modes (e.g., Flexible Duplex).

[0060] Furthermore, in embodiments of the present invention, the "configuration" of wireless parameters, etc., can be a pre-configured value or a wireless parameter notified by a base station or terminal.

[0061] (System Structure)

[0062] Figure 1 This is a diagram illustrating a wireless communication system according to an embodiment of the present invention.

[0063] like Figure 1 As shown, the wireless communication system of the present invention includes a base station 10 and a terminal 20. Figure 1 The image shows one base station 10 and one terminal 20, but this is just an example and there can be multiple terminals.

[0064] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time and frequency domains. The time domain can be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain can be defined by the number of subcarriers or resource blocks. Furthermore, the TTI (Transmission Time Interval) in the time domain can be a time slot or a subframe.

[0065] Base station 10 sends synchronization signals and system information to terminal 20. Synchronization signals may be, for example, NR-PSS and NR-SSS. System information is transmitted via NR-PBCH, also known as broadcast information. Synchronization signals and system information can also be referred to as SSB (SS / PBCH block). Figure 1 As shown, base station 10 sends control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of beamforming for signal transmission and reception. Furthermore, both base station 10 and terminal 20 can apply MIMO (Multiple Input Multiple Output) based communication to DL or UL. Additionally, base station 10 and terminal 20 can also communicate via CA (Carrier Aggregation) based secondary cells (SCell) and primary cells (PCell). Moreover, terminal 20 can also communicate via DC (Dual Connectivity) based primary cells of base station 10 and primary / secondary cells of other base stations 10 (PSCell).

[0066] Terminal 20 is a communication device with wireless communication capabilities, such as a smartphone, mobile phone, tablet computer, wearable terminal, or M2M (Machine-to-Machine) communication module. Figure 1As shown, terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Furthermore, terminal 20 receives various reference signals transmitted from base station 10 and performs propagation path quality measurements based on the reception results of these reference signals. Alternatively, terminal 20 can be referred to as UE, and base station 10 as gNB.

[0067] Next, the discussion on power saving in base stations in NR Release 18 will be explained. From the perspectives of both the transmitting and receiving sides of the base station, methods for improving network power saving in both base stations and terminals are being investigated. For example, methods are being explored for base stations to use potential support / feedback and potential auxiliary information from terminals to achieve more efficient dynamic and / or semi-static and finer-grained adaptation of transmission and / or reception through one or more network power saving techniques in the time, frequency, spatial, and power domains.

[0068] Next, the Discontinuous Reception (DRX) or Connected Mode Discontinuous Reception (CDRX) in conventional terminals will be explained.

[0069] Figure 2 This is a diagram used to illustrate CDRX in NR version 15. In the CDRX action of NR version 15, the terminal monitors the PDCCH during the DRX on-duration.

[0070] Figure 3 This is a diagram used to illustrate WUS in NR Release 16. In NR Release 16, the PDCCH-based Wake Up Signal (WUS) can instruct more than one terminal whether the terminal should monitor the PDCCH during the next DRX activation period.

[0071] DCI format 2_6, which scrambles CRC (Cyclic Redundancy Check) using PS-RNTI (Power Saving-Radio Network Temporary Identifier), is used as a PDCCH-based WUS, also known as DCP (DCI with CRC scrambled by PS-RNTI).

[0072] The monitoring opportunity of WUS is set according to the offset between the period of activation and the period of activation of terminal-based functions. When WUS indicates "inactive" (i.e., when the terminal is not sending or receiving data), the terminal can skip the monitoring during the activation period and immediately switch to sleep mode.

[0073] Additionally, for example, if a PDCCH-based WUS is not detected due to a detection error, a default terminal action can be set.

[0074] DCI format 2_6 includes a 1-bit startup indication message indicating "activated" or "inactive".

[0075] (Existing problems)

[0076] Next, the existing problems will be explained. To achieve carbon neutrality and the SDGs, saving base station power consumption is of increasing importance. However, in the past, there has been a problem that methods for saving base station power consumption have not been standardized.

[0077] (Summary of this implementation method 1)

[0078] Therefore, in this embodiment, an example of reducing the power consumption of the base station from a time-domain perspective will be described. Hereinafter, embodiments 1 to 4 will be described as specific examples.

[0079] (Example 1)

[0080] In this embodiment, the definitions of actions and associated concepts in the case of intermittent base station reception are explained.

[0081] Figure 4 This is a diagram illustrating the intermittent reception of a base station according to Embodiment 1 of the present invention. The period during which the base station 10 disables / enables the receiving unit is introduced as the intermittent reception (gNB CDRX) function of the base station (hereinafter referred to as base station intermittent reception).

[0082] The concept of intermittent reception for base station 10 is the same as that for terminal 20. Invalid receiving units and / or parameters can be set on a per-port, per-panel, per-beam, or per-carrier (or per-cell) basis.

[0083] Figure 5 This diagram illustrates the parameters involved in Embodiment 1 of the present invention. The base station CDRX can be defined by several parameters listed below. Furthermore, the units of the parameters can be symbols, time slots, subframes, milliseconds, or seconds, etc. The units can be different or the same among the parameters.

[0084] • drx-onDurationTimer: The period at the start of the DRX cycle

[0085] • drx-SlotOffset: The delay before drx-onDurationTimer starts

[0086] • drx-InactivityTimer: During the uplink transmission period after the uplink receive opportunity, terminal 20 performs uplink transmission.

[0087] • drx-LongCycleStartOffset: Defines when the long DRX cycle (i.e., drx-LongCycle) and drx-StartOffset begin, and when the short DRX cycle begins.

[0088] •drx-ShortCycle: Short DRX cycle

[0089] • drx-ShortCycleTimer: The period during which base station 10 follows a short DRX cycle.

[0090] ·drx-RetransmissionTimerUL: The maximum period before receiving an uplink retransmission permission.

[0091] ·drx-HARQ-RTT-TimerUL: Minimum period before expecting uplink retransmission permission

[0092] When intermittent reception of the base station becomes valid, the base station 10 can receive the uplink channel transmitted from the terminal 20 when executing drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL.

[0093] When the base station intermittently receives data, the terminal 20 may also perform any of the following actions.

[0094] <Option 1>

[0095] Terminal 20 can also perform actions that envision intermittent reception by the base station. Specifically, terminal 20 identifies the state of intermittent reception by the base station via RRC, MAC-CE, or DCI. In the case of DCI, terminal 20 envisions receiving DCI from base station 10 indicating the state of intermittent reception by the base station. Further details regarding DCI-based instructions will be described later in Embodiment 3.

[0096] Terminal 20 can also transmit uplink channels during the execution of drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL when intermittent reception of the base station becomes valid.

[0097] <Option 2>

[0098] Terminal 20 may also ignore intermittent reception from the base station. Specifically, terminal 20 performs uplink transmission as scheduled or set by base station 10, regardless of the state of intermittent reception from the base station.

[0099] Furthermore, base station 10 can perform scheduling or settings that take into account intermittent base station reception when it is effective, or it can perform scheduling or settings that are unrelated to intermittent base station reception. When scheduling or settings that take intermittent base station reception into account are performed, the intermittent base station reception function is achieved even if terminal 20 ignores intermittent base station reception. Conversely, when scheduling or settings that do not take intermittent base station reception into account are not performed, if terminal 20 ignores intermittent base station reception, useless signals are transmitted, thus wasting the power consumption of terminal 20.

[0100] On the other hand, even when intermittent reception by the base station is ineffective, the base station 10 can still receive the uplink channel transmitted from the terminal 20 regardless of the intermittent reception parameters. That is, the base station 10 can also continuously receive the uplink channel from the terminal 20 while keeping the receiving unit on.

[0101] In the event of intermittent failure of base station reception, terminal 20 may also perform any of the following actions.

[0102] <Option 1>

[0103] Terminal 20 can also perform actions that envision intermittent reception by the base station. Specifically, terminal 20 identifies the state of intermittent reception by the base station via RRC, MAC-CE, or DCI. In the case of DCI, terminal 20 envisions receiving DCI from base station 10 indicating the state of intermittent reception by the base station. Further details regarding DCI-based instructions will be described later in Embodiment 3.

[0104] In the event that the base station intermittent reception is invalid, the terminal 20 performs uplink transmission as scheduled or set by the base station 10, regardless of the state of the intermittent reception.

[0105] <Option 2>

[0106] Terminal 20 may also ignore intermittent reception from the base station. Specifically, terminal 20 performs uplink transmission as scheduled or set by base station 10, regardless of the state of intermittent reception from the base station.

[0107] In addition, base station 10 can receive terminal assistance information to determine the values ​​of the aforementioned parameters that define the wake-up / sleep period.

[0108] Terminal assistance information can be a periodic representation of terminal services. Base station 10 can receive terminal assistance information at higher layers. Base station 10 considers the terminal assistance information reported by terminal 20 to determine the value of parameters.

[0109] Terminal 20 can send terminal auxiliary information such as the period of terminal services to base station 10.

[0110] According to this embodiment, intermittent reception of base station 10 can be achieved.

[0111] (Example 2)

[0112] This embodiment illustrates an example of a method for triggering intermittent reception at a base station.

[0113] The activation / deactivation of intermittent base station reception can also be performed using any of the following options.

[0114] <Option 1>

[0115] Base station 10 can also enable / disable intermittent reception of the base station when the RRC parameter representing the enable / disable of intermittent reception of the base station is set by terminal 20 or other network nodes (such as the core network or other base stations).

[0116] <Option 2>

[0117] When base station 10 receives a MAC CE command indicating the activation / deactivation of intermittent reception from terminal 20 or other network nodes (e.g., core network or other base stations), it can enable / deactivate intermittent reception.

[0118] <Option 3>

[0119] When base station 10 receives a UCI contained in PUCCH or PUSCH from terminal 20, it can enable / disable intermittent reception of base station based on the enable / disable instruction of intermittent reception of base station contained in the UCI.

[0120] The UCI containing the indication of the activation / deactivation of intermittent base station reception can also be a newly defined UCI type, different from the previous ones. Alternatively, the UCI can be the same UCI type as before, such as HARQ-ACK, CSI, SR, etc.

[0121] Terminal 20 can also send a PUCCH or PUSCH to base station 10 to perform intermittent reception of base station (i.e., activation / deactivation), thereby enabling / disabling intermittent reception of base station.

[0122] Terminal 20 can also receive a DCI (Distributed Information Citation) from base station 10 indicating the state of intermittent reception by the base station, in order to identify whether the UCI-based indication has been correctly decoded by base station 10, and whether base station 10 and terminal 20 have a common understanding of the state of intermittent reception by the base station. Further details regarding the DCI will be described later in Embodiment 3.

[0123] <Option 4>

[0124] Under certain conditions, base station 10 can enable / disable intermittent reception. For example, base station 10 can also enable intermittent reception if it does not receive uplink channel data from terminal 20 for a certain period of time. This certain period of time can be a symbol, time slot, subframe, millisecond, second, etc.

[0125] In order to obtain a common understanding between base station 10 and terminal 20 regarding the state of intermittent reception of the base station, terminal 20 may also receive a DCI indicating the state of intermittent reception of the base station from base station 10. Further details regarding the DCI will be described later in Embodiment 3.

[0126] <Option 5>

[0127] Base station 10 can also enable / disable intermittent reception by combining the above options.

[0128] In addition, as a step to enable / disable intermittent reception of the base station, the base station 10 may also perform any of the following actions.

[0129] <Option 1>

[0130] Base station 10 may also immediately enable / disable base station intermittent reception when executing any of the above-mentioned options that trigger the activation / deactivation of base station intermittent reception.

[0131] <Option 2>

[0132] Base station 10 may also receive an instruction to activate / deactivate intermittent reception at a specified time interval or at a designated moment, starting from the time interval received. The unit for specifying the time interval or moment may be a symbol, time slot, subframe, millisecond, second, etc. That is, base station 10 may also activate / deactivate intermittent reception at a specified time when executing any of the above-mentioned options that trigger the activation / deactivation of intermittent reception.

[0133] <Option 3>

[0134] Base station 10 can also enable / disable intermittent reception based on the newly introduced timer. The timers for enabling / disabling reception can be the same or different. The unit of the timer can be a symbol, time slot, subframe, millisecond, second, etc. Other network nodes such as base station 10 or terminal 20 can set the timer through RRC, or specify the timer through MAC-CE or UCI / DCI.

[0135] That is, when any of the above options that trigger the activation / deactivation of intermittent base station reception are executed, the timer is executed. When the timer expires, base station 10 can activate / deactivate intermittent base station reception.

[0136] The advantages of a timer will be explained. Even when intermittent reception by the base station is indicated as valid, due to processing by terminal 20, the actual uplink transmission from terminal 20 may sometimes occur with a certain delay after the indication. Even in such cases, by introducing a timer, intermittent reception by the base station can be made valid after a certain period of time, thus reducing the power consumption of base station 10.

[0137] Furthermore, even if the base station's intermittent reception is indicated as invalid, there may still be instances where actual uplink transmissions from the terminal 20 continue for a period of time after the indication due to processing by the terminal 20. Even in such cases, by introducing a timer, the base station's intermittent reception can be invalidated after a certain period, thus improving the performance of the terminal 20.

[0138] According to this embodiment, it is possible to trigger intermittent reception of the base station, and to perform the action of activating / deactivating when triggered.

[0139] (Example 3)

[0140] In this embodiment, an example is described whereby the terminal receives an instruction related to intermittent reception by the base station via DCI.

[0141] In cases where the state of intermittent reception by the base station is recognized by terminal 20 and is commonly understood in both terminal 20 and base station 10, a mechanism for indicating the state of intermittent reception from base station 10 to terminal 20 needs to be considered. For timely indication, DCI-based indication is promising.

[0142] In addition, as an advantage that is generally understood, when the base station is intermittently receiving data, the terminal 20 can stop uplink transmission, thus saving the power consumption of the terminal 20.

[0143] To indicate the intermittent reception state of the base station, a new RNTI can also be introduced. The new RNTI can be set as gNBCDRX-RNTI (GC-RNTI) for example.

[0144] In addition, the introduction of the DCI field can also be any of the following options.

[0145] <Option 1>

[0146] To indicate the intermittent reception status of the base station, a new DCI field can be introduced. The introduced DCI field can be 1 bit in size, with "1" representing a valid state and "0" representing an invalid state. Alternatively, it can be the other way around.

[0147] <Option 2>

[0148] Alternatively, the new DCI field can be omitted. That is, the intermittent reception status of the base station can be represented by existing fields. For example, even when the corresponding DCI format is scrambled with a new RNTI such as GC-RNTI, and the HPN and RV fields are all set to "0", the terminal 20 can still recognize that the intermittent reception status of the base station is valid.

[0149] Furthermore, for example, when the corresponding DCI format is scrambled by a new RNTI such as GC-RNTI, and the HPN and RV fields are all set to "0" and the MCS field is all set to "1", the terminal 20 can also recognize that the intermittent reception state of the base station is invalid.

[0150] In addition, the corresponding DCI format can be any of the following options.

[0151] <Option 1>

[0152] It could also be the DCI inherent to terminal 20.

[0153] <Option 1-1>

[0154] Base station 10 can also use a new DCI format, different from the previous one, to represent the state of intermittent reception of the base station.

[0155] <Options 1-2>

[0156] Base station 10 can also use the conventional DCI format 0_1, 0_2, 1_1, 1_2 or other DCI formats to represent the intermittent reception state of the base station.

[0157] <Option 2>

[0158] It can also be a group-common DCI for terminal 20.

[0159] <Option 2-1>

[0160] Base station 10 can also use a new DCI format, different from the previous one, to represent the state of intermittent reception by the base station. The aforementioned new DCI field can also be introduced together with other new DCI fields used for power-saving technology of base station 10 through the new DCI format. Base station 10 can also scramble the new DCI format through the aforementioned new RNTI (GC-RNTI, etc.).

[0161] <Option 2-2>

[0162] Base station 10 can also use existing DCI format 2_6 or other common DCI formats to represent the intermittent reception state of the base station.

[0163] If we assume the use of DCI format 2_6, then previous DCI fields in the DCI format can also be reinterpreted to indicate the state of intermittent reception by the base station. For example, the "Wake-up indication" can be reinterpreted. A "1" can be used to represent a valid state, and a "0" to represent an invalid state. Conversely, the opposite can also be used.

[0164] To distinguish them, base station 10 can also replace PS-RNTI and scramble DCI format 2_6 using the new RNTI (GC-RNTI, etc.) mentioned above.

[0165] According to this embodiment, the terminal 20 identifies the intermittent reception state of the base station, which can be commonly understood by both the terminal 20 and the base station 10.

[0166] (Example 4)

[0167] In this embodiment, an example is described of a base station or terminal reporting capability information related to intermittent reception of base stations.

[0168] The following capability information can also be introduced.

[0169] Base station capability information representing the capabilities of base station 10 can be introduced. That is, base station 10 sends base station capability information to terminal 20 or other network nodes. Terminal 20 or other network nodes that receive the base station capability information can also infer the capabilities of base station 10 based on the received base station capability information.

[0170] Base station capability information may also include information indicating whether intermittent reception by the base station is supported. Additionally, base station capability information indicating whether intermittent reception by the base station is supported may also be introduced.

[0171] Additionally, the following terminal capability information may also be introduced. For example, terminal capability information indicating whether intermittent base station reception is supported may also be introduced. Furthermore, terminal capability information indicating the state of whether intermittent base station reception is supported may also be introduced.

[0172] If terminal 20 has the terminal capability to identify the state of intermittent base station reception, it can also identify whether the intermittent base station reception function is effective or ineffective. For example, terminal 20 can also perform the operation of option 1 shown in embodiment 1. Furthermore, if terminal 20 does not have the terminal capability to identify the state of intermittent base station reception, it can also perform the operation of option 2 shown in embodiment 1.

[0173] In addition, terminal capability information indicating whether DCI (Distributed Computational Index) is supported, representing the state of intermittent base station reception, can also be introduced. Furthermore, terminal capability information indicating whether a new terminal-specific / group-common DCI format is supported can also be introduced.

[0174] The dependency relationship between base station capability information and terminal capability information can be any of the following options.

[0175] <Option 1>

[0176] To enable intermittent base station reception, it can also be configured to require separate reports from both the base station capability information and the terminal capability information indicating support for intermittent base station reception.

[0177] <Option 2>

[0178] To utilize intermittent base station reception, it is also possible to report only either the base station capability information or the terminal capability information that indicates support for intermittent base station reception.

[0179] According to this embodiment, the base stations or terminals can report each other's capability information related to intermittent reception by the base station.

[0180] The terminal capabilities in the above embodiments can be limited to the case where terminal 20 is a feature-reduced terminal, or can be applied to the case where terminal 20 is not a feature-reduced terminal.

[0181] (Summary of this implementation method 2)

[0182] Furthermore, to reduce power consumption in base station 10, cell DTX / DRX is being studied. For example, the alignment of cell DTX / DRX with UE-DRX in RRC connection mode and information exchange between nodes related to cell DTX / DRX are being investigated. Additionally, cell DTX / DRX can be replaced by both cell DTX and cell DRX, or by either cell DTX or cell DRX.

[0183] Mechanisms for enabling or disabling the transceiver units of base station 10 are important for reducing power consumption in base station 10. Adaptations for DL ​​transmission and UL reception are being investigated to reduce power consumption in base station 10.

[0184] Cell DTX / DRX is useful for enabling adaptation of DL transmission and UL reception. However, the detailed operation of cell DTX / DRX is not clearly defined. Therefore, embodiments 5 to 8 are described below as specific examples related to cell DTX / DRX.

[0185] (Example 5)

[0186] In Example 5, the definition of cell DTX / DRX is explained. Cell DRX can also be defined as in Examples 1-4 above. Whether to implement cell DRX is determined by higher-layer parameters, and the period, start time slot, offset, and duration can also be set. Furthermore, whether cell DRX can be applied can also be determined by semi-static, dynamic, or flexible network conditions.

[0187] Cell DTX can also be defined as described below. Whether to perform cell DTX is determined by higher-layer parameters, and the period, start time slot, offset, and duration can also be set. Furthermore, whether cell DTX can be applied can be determined by semi-static, dynamic, or flexible network conditions.

[0188] <Option 1>

[0189] Figure 6 This is a diagram illustrating the intermittent transmission of a base station according to Embodiment 5 of the present invention. (See diagram below.) Figure 6 As shown, the period during which the base station 10 invalidates or activates its own transmission unit can also be introduced as cell DTX.

[0190] The invalidated transmission units and / or parameters can be per port, per panel, per beam, per carrier, or per cell. Cell DTX can be defined by some or all of the parameters shown in 1)-6) below. The unit of this parameter can be a symbol, time slot, subframe, millisecond, or second, or other units. The units of these parameters can be the same or different.

[0191] 1) dtx-onDurationTimer: The period starting from the beginning of the DTX cycle.

[0192] 2) dtx-SlotOffset: The delay period before the start of dtx-onDurationTimer.

[0193] 3) dtx-InactivityTimer: The period that begins after the DL transmission opportunity (the opportunity for base station 10 to perform DL transmission and terminal 20 to receive DL transmission).

[0194] 4) dtx-LongCycleStartOffset: Defines the dtx-StartOffset for the start of the long DTX cycle (i.e., dtx-LongCycle) and the long and short DTX cycles.

[0195] 5) dtx-ShortCycle: Short DTX cycle. This can also be optional.

[0196] 6) dtx-ShortCycleTimer: The period during which base station 10 performs a short DTX cycle. Short DTX begins when DL reception occurs during long DTX. This can also be optional.

[0197] Figure 7 This is a diagram illustrating the parameters of Embodiment 5, which relates to the embodiments of the present invention. For example... Figure 7 As shown, starting from the beginning of dtx-LongCycle, only dtx-onDurationTimer becomes active after dtx-SlotOffset. If a DL reception occurs within dtx-LonCycle, the active time ends after dtx-InactivityTimer from the point of DL reception, and dtx-ShortCycle begins. If a DL reception occurs within dtx-ShortCycleTimer, dtx-ShortCycle continues. If no DL reception occurs within dtx-ShortCycleTimer, dtx-LongCycle begins.

[0198] When cell DTX is activated, and dtx-onDurationTimer or dtx-InactivityTimer is active, base station 10 can also transmit DL channel or DL ​​signal. As an action of terminal 20, when cell DTX is activated, and dtx-onDurationTimer or dtx-InactivityTimer is active, terminal 20 can also receive DL channel or DL ​​signal. Terminal 20 can also be designed to receive DL channel or DL ​​signal when dtx-onDurationTimer or dtx-InactivityTimer is not active.

[0199] When the cell DTX is disabled, terminal 20 can also be expected to receive the DL channel or DL ​​signal as if it were notifying or setting the base station 10.

[0200] The DL channel or DL ​​signal can be any one of PDCCH, PDSCH, SPS (Semi Persistent Scheduling)-PDSCH, CSI-RS (Channel State Information-Reference Signal), PT-RS (Phase Tracking-Reference Signal), or DM-RS (Demodulation-Reference Signal).

[0201] The UL channel or UL signal can be any one of PRACH, PUCCH, PUSCH, CG-PUSCH, SRS, PT-RS, or DM-RS.

[0202] (Example 6)

[0203] In Example 6, the cell DTX / DRX settings are explained.

[0204] <Option 1>

[0205] Joint configuration can also be performed. Cell DTX and cell DRX can also be jointly configured through common parameters. When common parameters (such as CellDTXDRX-Config) are set, cell DTX and DRX can be enabled. Terminal 20 can also appropriately perform the actions of Embodiment 5.

[0206] Public parameters may include any one or both of the information elements shown in 1) and 2) below.

[0207] 1) Parameters common to both DTX and DRX. Some parameters are common to both DTX and DRX. For example, parameters indicating the on-duration timer are common to both DTX and DRX. Similarly, parameters indicating the period are also common to both DTX and DRX.

[0208] 2) Separate parameters in DTX and DRX. Some parameters can also be set independently in DTX and DRX. For example, the parameter representing the slot offset can also be set independently in DTX and DRX.

[0209] Option 1 can reduce the overhead of RRC signaling.

[0210] <Option 2>

[0211] Separate settings can also be performed. Cell DTX and cell DRX can also be set individually according to separate parameters. When DTX-oriented parameters (e.g., CellDTX-Config) are set, cell DTX can be enabled. When DRX-oriented parameters (e.g., CellDRX-Config) are set, cell DRX can be enabled. DTX-oriented parameters can also include the parameters described in Example 5. DRX-oriented parameters can also include the parameters described in Example 1.

[0212] Option 2 increases the flexibility of configuration when enabling either cell DTX or cell DRX.

[0213] (Example 7)

[0214] In Example 7, the activation or deactivation of cell DTX / DRX is explained. When cell DTX and cell DRX are jointly set (Option 1 of Example 6), cell DTX and cell DRX can also be activated or deactivated as follows.

[0215] <Option 1>

[0216] Cell DTX and cell DRX can also be enabled or disabled via RRC signaling. With RRC parameters set, cell DTX and cell DRX can be enabled or disabled. For example, these RRC parameters can be common parameters from Example 6 (e.g., CellDTXDRX-Config).

[0217] <Option 2>

[0218] Cell DTX and cell DRX can be enabled or disabled via MAC-CE. When terminal 20 receives MAC-CE, it can also enable or disable cell DTX and cell DRX.

[0219] <Option 3>

[0220] The DCI can be used to enable or disable cell DTX and cell DRX. Terminal 20 can also dynamically notify the activation or deactivation of cell DTX and cell DRX via DCI. The notification based on this DCI can be executed as shown in 1)-4) below.

[0221] 1) The DCI format can be either a UE-specific DCI format or a group-common DCI format.

[0222] 2) The DCI format can be an existing format (e.g., DCI format 1_1, 1_2, 2_0) or a newly defined one (e.g., 1_x, 2_x).

[0223] 3) RNTI can be an existing RNTI (e.g., C-RNTI, SFI-RNTI) or a new RNTI can be defined.

[0224] 4) DCI fields can be a combination of existing fields and / or new fields. For example, in the case of a combination of existing fields, as shown in Alt.1) and Alt.2) below, some fields can be used to enable or disable cell DTX and cell DRX.

[0225] Alt.1) When scrambling is performed using an existing RNTI such as CS-RNTI, and for example, when all HPNs are set to "0", all RVs are set to "00", and all TDRAs are set to "1", terminal 20 can also dynamically enable cell DTX and cell DRX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all TDRAs are set to "1", terminal 20 can also dynamically disable cell DTX and cell DRX.

[0226] Alt.2) When scrambled by a new RNTI, and for example, when all HPNs are set to "0" and all RVs are set to "00", terminal 20 can also dynamically enable cell DTX and cell DRX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", and all FDRAs are set to "1", terminal 20 can also dynamically disable cell DTX and cell DRX.

[0227] For example, in the case of a new DCI field, the cell DTX and cell DRX can be enabled or disabled through this new DCI field. This new DCI field can be called the "Cell DTX / DRX identifier". For example, when the cell DTX / DRX identifier is set to "1", the terminal 20 can dynamically enable the cell DTX and cell DRX. Furthermore, for example, when the cell DTX / DRX identifier is set to "0", the terminal 20 can also dynamically disable the cell DTX and cell DRX. Additionally, the DCI including this new DCI field can be scrambled using either an existing RNTI or a new RNTI.

[0228] Furthermore, when cell DTX and cell DRX are configured separately (option 2 of embodiment 6), cell DTX and cell DRX can also be enabled or disabled as follows.

[0229] <Option 1>

[0230] Cell DTX or cell DRX can also be enabled or disabled via RRC signaling. With RRC parameters set, cell DTX or cell DRX can be enabled or disabled. For example, these RRC parameters can be the separate parameters from Example 6 (e.g., CellDTX-Config, CellDRX-Config).

[0231] <Option 2>

[0232] MAC-CE can be used to enable or disable cell DTX or cell DRX. When terminal 20 receives MAC-CE, it can enable or disable cell DTX or cell DRX.

[0233] <Option 3>

[0234] Terminal 20 can also dynamically notify the cell DTX or cell DRX of being activated or deactivated via DCI. The notification based on this DCI can be executed as shown in 1)-4) below.

[0235] 1) The DCI format can be either a UE-specific DCI format or a group-common DCI format.

[0236] 2) The DCI format can be an existing format (e.g., DCI format 1_1, 1_2, 2_0) or a newly defined one (e.g., 1_x, 2_x).

[0237] 3) RNTI can be an existing RNTI (e.g., C-RNTI, SFI-RNTI) or a new RNTI can be defined.

[0238] 4) DCI fields can be combinations of existing fields and / or new fields. For example, different combinations of DCI fields can be used to enable or disable cell DTX or cell DRX, respectively, to represent either cell DTX or cell DRX. For example, in the case of combinations of existing fields, as shown in Alt.1) and Alt.2) below, some fields can be used to enable or disable cell DTX and cell DRX.

[0239] Alt.1) When scrambling using an existing RNTI such as CS-RNTI, and for example, when all HPNs are set to "0", all RVs are set to "00", and all PRIs are set to "1", terminal 20 can dynamically enable cell DTX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all PRIs are set to "1", terminal 20 can dynamically disable cell DTX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", and all TDRAs are set to "1", terminal 20 can also dynamically enable cell DRX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all TDRAs are set to "1", terminal 20 can also dynamically disable cell DRX.

[0240] Alternatively, the PRI and TDRA fields can be added to indicate which of the following is the target of the activated or deactivated DCI: CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX.

[0241] Additionally, fields identical to those used as described above in PRI and TDRA (e.g., TDRA) can be used to indicate which of the following is the object: CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX. When using different DCI formats, the DCI format can also indicate whether the cell DTX or cell DRX is the object. For example, DCI format 0_0 can enable or disable cell DRX, while DCI format 1_0 can enable or disable cell DTX.

[0242] Alt.2) When scrambling using the new RNTI, for example, when all HPNs are set to "0", all RVs are set to "00", and all PRIs are set to "1", terminal 20 can dynamically enable cell DTX. For example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all PRIs are set to "1", terminal 20 can dynamically disable cell DTX. For example, when all HPNs are set to "0" and all RVs are set to "00", terminal 20 can also dynamically enable cell DRX. For example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", and all FDRAs are set to "1", terminal 20 can also dynamically disable cell DRX.

[0243] Additionally, while using, for example, PRI as described above, it is also possible to omit the additional field to indicate whether the cell DTX or cell DRX is the object. When using different DCI formats, the DCI format can also indicate whether the cell DTX or cell DRX is the object. For example, DCI format 0_0 can enable or disable the cell DRX, while DCI format 1_0 can enable or disable the cell DTX.

[0244] For example, in the case of a new DCI field, the cell DTX or cell DRX can be enabled or disabled through this new DCI field. This new DCI field can also be called the "Cell DTX identifier" or the "Cell DRX identifier".

[0245] When cell DTX and cell DRX are notified separately using separate fields, for example, when the cell DTX identifier is set to "1", terminal 20 can dynamically enable cell DTX. Furthermore, for example, when the cell DTX identifier is set to "0", terminal 20 can also dynamically disable cell DTX. Similarly, when the cell DRX identifier is set to "1", terminal 20 can also dynamically enable cell DRX. Furthermore, for example, when the cell DRX identifier is set to "0", terminal 20 can also dynamically disable cell DRX.

[0246] Furthermore, this new DCI field can also be referred to as the "Cell DTX DRX Identifier". When the cell DTX and cell DRX are jointly notified through a common field, for example, when the cell DTX DRX identifier is set to "01", terminal 20 can dynamically enable or disable the cell DTX. For example, when the cell DTX DRX identifier is set to "10", terminal 20 can dynamically enable or disable the cell DTX. For example, when the cell DTX DRX identifier is set to "11", terminal 20 can dynamically enable both cell DTX and cell DRX. For example, when the cell DTX DRX identifier is set to "00", terminal 20 can dynamically enable both cell DTX and cell DRX. The bit mapping of cell DTX and cell DRX described above can also be reversed.

[0247] In addition, the DCI including this new DCI field can be scrambled using either the existing RNTI or the new RNTI.

[0248] The timing for the activation or deactivation of the application cell DTX or cell DRX notified via MAC-CE or DCI as described above can be either 1) or 2) as shown below.

[0249] 1) Terminal 20 can be immediately activated or deactivated. When the activation or deactivation of cell DTX or cell DRX is notified via MAC-CE or DCI, cell DTX or cell DRX can be immediately activated or deactivated.

[0250] 2) Terminal 20 can activate or deactivate at the notified time. The activation or deactivation of cell DTX or cell DRX can be notified via RRC signaling, MAC-CE, or DCI at an interval or at a specific time from the time the activation or deactivation is notified. The unit of time can be a symbol, time slot, subframe, millisecond, or second, etc. When the activation or deactivation of cell DTX or cell DRX is notified via MAC-CE or DCI, the cell DTX or cell DRX can be activated or deactivated at the pre-notified time.

[0251] (Example 8)

[0252] In Example 8, the associated operation of cell DTX / DRX and UE DRX is described. When the time positions of cell DTX and UE DRX are not aligned, and DL transmission is not performed due to cell DTX, terminal 20 may be woken up by receiving DL channel or DL ​​signal.

[0253] Therefore, the actions can also be performed as shown in options 1-5 below.

[0254] <Option 1>

[0255] If UE DRX (e.g., DRX-Config) is configured, terminal 20 may not assume that cell DTX is configured.

[0256] <Option 2>

[0257] If cell DTX is configured, terminal 20 may not necessarily have UE DRX (e.g., DRX-Config) configured. Alternatively, the parameters for cell DTX can be those described in Example 6.

[0258] <Option 3>

[0259] When a UE DRX (e.g., DRX-Config) is configured, terminal 20 may not assume that a cell DTX with a time location that is not aligned with the UE DRX is configured. When the time locations of the cell DTX and the UE DRX are aligned, the cell DTX and UEDRX can be configured jointly.

[0260] <Option 4>

[0261] When a cell DTX is configured, terminal 20 may not assume that a UE DRX (e.g., DRX-Config) with a time position misaligned with the cell DTX is configured. When the time positions of the cell DTX and UE DRX are aligned, the cell DTX and UE DRX can be configured jointly.

[0262] <Option 5>

[0263] The cell DTX and UE DRX can be set for terminal 20 regardless of whether their time positions are aligned. Furthermore, if cell DTX is set in addition to UE DRX, the cell DTX parameters can be prioritized. Terminal 20 can also ignore the UE DRX parameters. Terminal 20 can also operate as in Embodiment 5. Furthermore, if cell DTX is set in addition to UE DRX, the parameters of both can be applied. Terminal 20 can also wake up at the activation time of both cell DTX and cell DRX.

[0264] The aforementioned "time position alignment of cell DTX and UE DRX" can also be defined as option 1 or option 2 as shown below.

[0265] <Option 1>

[0266] When the long cycle is the same in both the cell DTX and UE DRX, it can also be defined as the time position alignment of the cell DTX and UE DRX.

[0267] <Option 1-1>

[0268] Furthermore, when the long cycle is the same in both cell DTX and UE DRX, it can also be defined as time alignment between cell DTX and UE DRX, regardless of the activation time within the long cycle. That is, when the long cycle of cell DTX (e.g., dtx-LongCycle) and the long cycle of UE DRX (e.g., drx-LongCycle) are the same, it can also be defined as time alignment.

[0269] <Options 1-2>

[0270] When the long cycle is the same in both the cell DTX and UE DRX, it can be further defined as time alignment between the cell DTX and UE DRX, depending on the activation time within the long cycle. Similarly, if the timers and slot offsets (e.g., dtx-LongCycle, drx-LongCycle, dtx-onDurationTimer, drx-onDurationTimer, dtx-SlotOffset, drx-SlotOffset) during the on-time period of the long cycle are the same in both the cell DTX and UE DRX, it can also be defined as time alignment between the cell DTX and UE DRX. Furthermore, other parameters (e.g., dtx-InactivityTimer, drx-InactivityTimer, etc.) can be additionally considered to determine whether this definition is satisfied.

[0271] <Option 2>

[0272] Besides the long cycle, when the short cycle is the same in both cell DTX and UE DRX, it can also be defined as time position alignment between cell DTX and UE DRX. Option 2 can also be applied to situations that satisfy the conditions of Option 1-1 or Option 1-2.

[0273] <Option 2-1>

[0274] Furthermore, when the short cycle is the same in both cell DTX and UE DRX, it can be defined as time alignment between cell DTX and UE DRX, regardless of the activation time within the short cycle. That is, when the short cycle (e.g., dtx-ShortCycle) of cell DTX is the same as the short cycle (e.g., drx-ShortCycle) of UE DRX, it can also be defined as time alignment.

[0275] <Option 2-2>

[0276] When the short cycle is the same in both the cell DTX and UE DRX, it can be further defined as time alignment between the cell DTX and UE DRX, depending on the activation time within the short cycle. Similarly, when the short cycle timer and short cycle (e.g., dtx-ShortCycleTimer, drx-ShortCycleTimer, dtx-ShortCycle, drx-ShortCycle) are the same in both the cell DTX and UE DRX, it can also be defined as time alignment between the cell DTX and UE DRX.

[0277] (Summary of this implementation method 3)

[0278] (Example 9)

[0279] To achieve NES (Network Energy Saving), research is underway on the adaptation of extended PRACH in the time domain and the adaptation of extended PRACH in the spatial domain, such as setting resources for non-uniform PRACH for each SSB.

[0280] Figure 8 This is a diagram illustrating an example of the PRACH format according to Embodiment 9 of the present invention. In NR, as... Figure 8 As shown, the PRACH formats 0, 1, 2, 3, A1, A2, A3, B1, B2, B3, B4, C0 and C2 are specified (see Non-Patent Literature 3).

[0281] Formats 0, 1, 2, and 3 are supported only in Frequency Range 1 (FR1). Format 0 consists of a 1.25kHz, 1ms resource. Format 1 consists of a 1.25kHz, 3ms resource. Format 2 consists of a 1.25kHz, 3.5ms resource. Format 3 consists of a 5kHz, 1ms resource.

[0282] Formats A1, A2, A3, B1, B2, B3, B4, C0, and C2 are supported in FR1 with a 15 or 30 kHz SCS and FR2 with a 60 or 120 kHz SCS (Frequency Range 2). The frequency range for formats A1, A2, A3, B1, B2, B3, B4, C0, and C2 is 15 or 30 kHz in FR1 and 60 or 120 kHz in FR2. Regarding the time domain, formats A1, B1, and C0 are 2 OS (Orthogonal symbol), formats A2 and B2 are 4 OS, formats A3, B3, and C2 are 6 OS, and format B4 is 12 OS.

[0283] Figure 9 This is a diagram illustrating an example of a time-domain PRACH resource according to Embodiment 9 of the present invention. The time domain of PRACH is determined based on the parameter prach-ConfigurationIndex (Non-Patent Document 3). Figure 9 This example shows the case where prach-ConfigurationIndex is 103 in FR1. For example... Figure 9 As shown, when prach-ConfigurationIndex is 103, the preamble format is A1,n SFNIn mod x=y, x=1, y=0, subframe numbers are 2 and 7, the start symbol is 0, the number of PRACH slots in the subframe is 2, the number of PRACH opportunities in the PRACH slots is 6, and the PRACH period is 2.

[0284] Figure 10 This is a diagram illustrating an example of a frequency domain PRACH resource according to Embodiment 9 of the present invention. The frequency domain of the PRACH is determined based on the parameter msg1-FDM={1,2,3,4}. Figure 10 The example shown is the case where msg1-FDM=4.

[0285] The association between the SS / PBCH block (hereinafter also referred to as "SSB") and the PRACH is represented by N and R specified by ssb-perRACH-OccasionAndCB-PreamblesPerSSB included in the parameter RACH-ConfigCommon (see Non-Patent Document 4). N is the number of SSBs associated with a PRACH occasion (hereinafter also referred to as "PRACH occasion", "RACHoccasion", "RO"). R is the number of contention-based preambles for each SSB of each valid RO.

[0286] SSBs are mapped to valid ROs in the following order (see Non-Patent Literature 5).

[0287] 1) Ascending order of the preamble index within a single RO

[0288] 2) Ascending order of frequency-direction resource indexes of ROs used in frequency division multiplexing

[0289] 3) Ascending order of time-division multiplexed RO time-direction resource indexes within the PRACH time slot

[0290] 4) Ascending order of the PRACH slot index

[0291] Figure 11 This is a diagram illustrating an example of the association between SSB and PRACH resources in Embodiment 9 of the present invention. Figure 11 The example shown is msg1-FDM=two, ssb-perRACH-OccasionAndCB-PreamblesPerSSB=oneHalf{n20}, i.e., N=1 / 2, R=20. Therefore, Figure 11 Each SSB shown is associated with a preamble index {0,1,2,...,R-1}, and each SSB is associated with 2RO.

[0292] SIB1 notifies PRACH-related settings such as time-domain settings (e.g., prach-ConfigurationIndex), frequency-domain settings (e.g., msg1-FDM), and SSB-PRACH association settings (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB).

[0293] In the traditional process, the SIB is updated as follows.

[0294] The SIB can be updated according to each modification period. The modification period is defined as 2, 4, 8, or 16 times the paging cycle through the information element modificationPeriodCoeff notified by SIB1. SIB1 may be modified when SFN mod modification period = 0.

[0295] Whether the SIB will be updated in the next change cycle is sent via a short message during the paging opportunity. If the bit field of systemInfoModification in the short message is 1, the BCCH change is notified to all SIBs except SIB6, SIB7, and SIB8.

[0296] Figure 12 This diagram illustrates a modification of SIB1 according to Embodiment 9 of the present invention. SIB1 is modified when SFN mod2 = 0. Alternatively, MIB may remain unchanged.

[0297] The base station needs to monitor PRACH transmissions from the UE in each RO. From the NES perspective, under very low traffic load conditions, frequent wake-ups and long PRACH monitoring are considered to reduce the base station's deep sleep time and increase its power consumption. On the other hand, by properly configuring PRACH settings such as period, the base station's power consumption can be reduced.

[0298] Therefore, the actions shown in actions 1) to 4) can also be performed.

[0299] Action 1) From a time-domain perspective, extend PRACH. In order to shorten RO monitoring time and reduce the wake-up of base stations used for PRACH monitoring, continuous RO can be set and the RO period can be extended.

[0300] Action 2) From a spatial perspective, extend the PRACH. Currently, the number of PRACH preambles associated with each SSB is the same. However, in a real-world configuration, it is assumed that the number of UEs in different SSB beam regions is different. Therefore, it is assumed that the number of preambles required for each SSB is different. Therefore, a non-uniform mapping of PRACH resources can be performed for each SSB.

[0301] Action 3) When business operations change, PRACH requirements also change. It is necessary to quickly adapt the cycle, FDM settings, SSB and PRACH resource associations, and PRACH settings. For example, this can be achieved through DCI.

[0302] Action 4) can also execute UE actions related to Action 3).

[0303] The following is an explanation of action 1).

[0304] Action 1-1) Figure 13 This is a diagram illustrating an example of the PRACH resource involved in Embodiment 9 of the present invention. (See diagram for example.) Figure 13 As shown, the number of RO frequency division multiplexing can also be increased. The UE can decide to use any of the frequency division multiplexed ROs.

[0305] New values ​​can also be introduced for the number of frequency-division multiplexed ROs within a single RO. These new values ​​can differ from or be larger than the current specification. In the current specification, the number of frequency-division multiplexed ROs supports {1, 2, 4, 8}. Different values ​​can be supported; for example, the number of frequency-division multiplexed ROs can support {1, 2, 4, 6, 8}.

[0306] The number of ROs used in frequency division multiplexing can support larger values. Maximum values ​​can be, for example, 10, 12, 14, 16, 20, 24, or 32. For example, with a maximum value of 12, {1,2,4,8,12} can be supported. For example, with a maximum value of 16, {1,2,4,8,12,16} can be supported. For example, with a maximum value of 24, {1,2,4,8,12,16,20,24} can be supported. For example, with a maximum value of 32, {1,2,4,8,12,16,24,32} can be supported.

[0307] By using the above action 1-1), the PRACH monitoring time can be shortened for the same number of ROs.

[0308] Actions 1-2) Figure 14This is a diagram illustrating an example of PRACH resources according to Embodiment 9 of the present invention. The temporal location of the RO is determined based on parameters such as prach-ConfigurationIndex. An entry in the random access configuration table (refer to Tables 6.3.3.2-2 / 3 / 4 of Non-Patent Document 3) is specified by this parameter. However, in some entries, the temporal domains of the ROs are not continuous. Therefore, new entries may be introduced to make the temporal domains of the ROs continuous. The UE can decide to use any of the ROs.

[0309] Furthermore, a temporally continuous RO is one where there is no gap between adjacent ROs, or where the gap is less than a certain period. This period can be X symbols, X subframes, X time slots, or X ms. For example, when the gap is less than 7 OFDM symbols, adjacent ROs can be considered continuous.

[0310] Action 1-2-1) can introduce an entry that allows one or more combinations of the following Alt random access settings.

[0311] Alt.1) Continuous ROs between adjacent PRACH cycles can also be introduced. To achieve continuous ROs within adjacent PRACH cycles, different frame offsets y, subframe numbers, and a portion or all of the start symbol can be used. For example, two sets of frame offsets y, subframe numbers, and a portion or all of the start symbol can be set. For example, odd indices can correspond to one set of frame offsets y, subframe numbers, and a portion or all of the start symbol. For example, even indices can correspond to another set of frame offsets y, subframe numbers, and a portion or all of the start symbol.

[0312] Alt.2) Continuous ROs between adjacent subframes within a PRACH cycle can also be introduced. To achieve continuous ROs in adjacent subframes, different frame offsets (y), subframe numbers, and part or all of the start symbol can be used. With a 30 or 120 kHz SCS set for PRACH, two PRACH slots exist within a subframe or a 60 kHz SCS. An additional parameter (e.g., paraPRACHCont) can also be set to determine the PRACH location. For example, this additional parameter can specify whether the PRACH is set in the first or second PRACH slot. This additional parameter can be communicated via DCI, MAC-CE, RRC signaling, or broadcast. For example, when two subframe numbers are set for PRACH in a 30 or 120 kHz SCS, and the row indicating the number of PRACH slots within a subframe or 60 kHz SCS slot is 1, with the additional parameter paraPRACHCont set to true, the number of PRACH slots in the first subframe can be 1 and the number of PRACH slots in the second subframe can be 0. In other cases, the conventional procedure can be followed.

[0313] Alt.3) Continuous ROs can also be introduced between adjacent PRACH slots within a subframe or slot. Specifically for PRACH format A1, the number of ROs can be increased to allow the use of all symbols of a given PRACH slot within that slot. Furthermore, between PRACH slots within a subframe or slot, adjacent PRACH slots can utilize different frame offsets y, subframe numbers, and part or all of the start symbol to achieve adjacent RO configurations.

[0314] Action 1-2-2) The selection of the random access setting entry in Action 1-2-1 above can be notified through a new information element.

[0315] Table 1 shows an example of PRACH settings.

[0316] [Table 1]

[0317] Table 1 shows PRACH configuration indexes 256, 257, and 258, which correspond to Alt.1 above. The preamble format can be format 0 or 3. PRACH configuration index 283 corresponds to Alt.1 and Alt.3 above, and the preamble format can be format A1, A2, A3, B1, B4, C0, or C2.

[0318] Additionally, regarding the offset y and subframe number in Table 1, the number of times in the PRACH cycle is odd, i.e. (nf When / x) mod2 is 1, the value before the forward slash is used, and the number of PRACH cycles is even, i.e. (n f When / x)mod2 is 0, use the value after the forward slash.

[0319] Figure 15 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 15 The table shows the PRACH resources when the PRACH setting index is 256. For example... Figure 15 As shown, the period is 8. The first period uses y=7 and subframe number 9, and the second period uses y=0 and subframe number 0. Thus, adjacent PRACH resources are continuous.

[0320] Figure 16 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 16 The table shows the PRACH resources when the PRACH setting index is 257. For example... Figure 16 As shown, the period is 4. The first period uses y=3 and subframe number 9, and the second period uses y=0 and subframe number 0. Thus, adjacent PRACH resources are continuous.

[0321] Figure 17 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 17 The table shows the PRACH resources when the PRACH setting index is 283. For example... Figure 17 As shown, the period is 4. The first period uses y=3 and subframe number 9, and the second period uses y=0 and subframe number 0. By setting the number of ROs in the time domain of each PRACH slot to 7, OFDM symbols within the PRACH slot can be occupied by ROs. Alternatively, the number of ROs in the time domain of each PRACH slot can be set to 6. The PRACH format can also be applied to A1, B1, and C0.

[0322] Table 2 shows an example of PRACH settings.

[0323] [Table 2]

[0324] Table 2 shows PRACH setting indexes 259-264 (corresponding to Alt.1 above). The preamble format can apply format 1 or 2.

[0325] Additionally, regarding the offset y and subframe number in Table 2, the number of times in the PRACH cycle is odd, i.e. (n fWhen / x) mod2 is 1, the value before the forward slash is used, and the number of PRACH cycles is even, i.e. (n f When / x)mod2 is 0, use the value after the forward slash.

[0326] Figure 18 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 18 The table in Table 2 shows the PRACH resources when the PRACH setting index is 259. For example... Figure 18 As shown, the period is 8, with the first period using y=7 and subframe number 7, and the second period using y=0 and subframe number 0. The preamble format is 3ms long, format 1. Therefore, adjacent PRACH resources are contiguous.

[0327] Figure 19 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 19 The table in Table 2 shows the PRACH resources when the PRACH setting index is 262. For example... Figure 19 As shown, the period is 8. The first period uses y=7, subframe number 6, and start symbol 7. The second period uses y=0, subframe number 0, and start symbol 0. The preamble format is 3.5ms long format 2. Therefore, adjacent PRACH resources are contiguous.

[0328] Table 3 shows an example of PRACH settings.

[0329] [Table 3]

[0330] Table 3 shows that PRACH setting indexes 265-271 correspond to Alt.2 above, and the preamble format can use format 0, 1, 2 or 3.

[0331] Figure 20 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 20 The table in Table 3 shows the PRACH resources when the PRACH settings are 268, 270, and 271. For example... Figure 20 As shown, with the PRACH index set to 268, the period is 1, and subframe numbers 0, 1, 2, 3, and 4 are used. The preamble format is 1ms long, format 0 or 3.

[0332] like Figure 20 As shown, with the PRACH index set to 270, the period is 1, and subframe numbers 0, 3, and 6 are used. The preamble format is 3ms long, format 0 or 3.

[0333] like Figure 20 As shown, with the PRACH index set to 271, the period is 1, using subframe numbers 0 and 3, and start symbols 0 and 7. The preamble format is 3.5ms long format 0 or 3. Additionally, (subframe number) (start symbol) can be one of the following groups: (0,4)(7,0), (1,4)(0,7), (1,5)(7,0), (2,5)(0,7), (2,6)(7,0), (3,6)(0,7).

[0334] Additionally, subframe number (0,1) in Table 3 can be replaced with (1,2), (2,3), (3,4), (4,5), (5,6), (6,7), (7,8), and (8,9). Furthermore, subframe number (0,1,2) in Table 3 can be replaced with (1,2,3), (2,3,4), (3,4,5), (4,5,6), (5,6,7), (6,7,8), and (7,8,9). Additionally, subframe number (0,1,2,3) in Table 3 can be replaced with (1,2,3,4), (2,3,4,5), (3,4,5,6), (4,5,6,7), (5,6,7,8), and (6,7,8,9). Furthermore, subframe number (0,3) in Table 3 can be replaced with (1,4), (2,5), (3,6), and (4,7). Additionally, the subframe number (0,3,6) in Table 3 can be replaced with (1,4,7).

[0335] Table 4 shows an example of PRACH settings.

[0336] [Table 4]

[0337] Table 4 shows that PRACH setting indexes 272-278 correspond to Alt.1) and Alt.2) above. The preamble format can use format 0, 1, 2 or 3.

[0338] Additionally, regarding the offset y and subframe number in Table 4, the number of times in the PRACH cycle is odd, i.e. (n f When / x) mod2 is 1, the value before the forward slash is used, and the number of PRACH cycles is even, i.e. (n f When / x)mod2 is 0, use the value after the forward slash.

[0339] Figure 21 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 21 The table shows the PRACH resources when the PRACH setting index is 272. For example... Figure 21As shown, the period is 1. The first period uses subframe numbers 8 and 9, and the second period uses subframe numbers 0 and 1. The preamble format is 1ms long, format 0 or 3.

[0340] Figure 22 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 22 The table in Table 4 shows the PRACH resources when the PRACH setting index is 278. For example... Figure 22 As shown, the period is 1. The first period uses subframe numbers 3 and 6, and the start symbols use 0 and 7. The second period uses subframe numbers 0 and 3, and the start symbols use 0 and 7. The preamble format is Format 2, which is 3.5ms long.

[0341] Table 5 shows an example of PRACH settings.

[0342] [Table 5]

[0343] Table 5 shows PRACH setting indices 279-281, which correspond to Alt.2) and Alt.3) above. The preamble format can apply format A1 or a format for two symbol periods. Furthermore, when the number of PRACH slots within a subframe in Table 5 is 30 or 120kHz SCS at 60kHz, and the parameter paraPRACHcont is true, the first subframe is set to 1, and the second subframe is set to 0. Otherwise, the situation is the same as in the conventional case.

[0344] Figure 23 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 23 The table shows the PRACH resources when the PRACH setting index is 279. For example... Figure 23 As shown, the period is 16, the subframe numbers are 4 and 5, the start symbol is 0, the number of PRACH slots within the subframe is 1, and the number of ROs within the PRACH slot is 7. The preamble format is format A1, which is two symbol lengths.

[0345] Figure 24 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 24 The table in Table 5 shows the PRACH resources when the PRACH setting index is 280. For example... Figure 24 As shown, the period is 16, the subframe number is 4, the start symbol is 0, the number of PRACH slots within the subframe is 2, and the number of ROs within the PRACH slots is 7. The preamble format is format A1, which is two symbol lengths.

[0346] Table 6 shows an example of PRACH settings.

[0347] [Table 6]

[0348] The PRACH setting index 282 shown in Table 6 corresponds to Alt.3 above. The preamble format can apply format A3 or 4, 6 or 12 code elements of format A2, B4, C2.

[0349] Figure 25 This is a diagram illustrating an example of a PRACH resource related to Embodiment 9 of the present invention. Figure 25 The table in Table 6 shows the PRACH resources when the PRACH setting index is 282. For example... Figure 25 As shown, the period is 1, the subframe numbers are 3, 4, and 5, the start symbol is 0, the number of PRACH slots within the subframe is 2, and the number of ROs within the PRACH slots is 2. The preamble format is format A3 with a length of six symbols. In addition, each PRACH slot is configured with 12 symbols. The subframe number can be permuted as (1,2,3), (1,2,3,4), and (0,1,2,3,4).

[0350] Actions 1-3) Figure 26 This is a diagram illustrating an example of the PRACH resource involved in Embodiment 9 of the present invention. (See diagram for example.) Figure 26 As shown, the RO cycle can also be increased. This reduces the number of gNB wake-ups and shortens the PRACH monitoring time. The UE can choose to use any of the ROs.

[0351] Action 1-3-1) can also introduce new random access settings entries with different or larger PRACH setting periods. Hereinafter, the unit for the period value can be milliseconds (ms).

[0352] In the current specification, PRACH supports period settings of {10, 20, 40, 80, 160}. Therefore, larger maximum periods can be supported, such as 240, 320, 480, 640, 960, and 1280.

[0353] With a maximum period of 320, it can support {0,20,40,80,160,320} or {0,20,40,80,160,240,320}. In addition, period 0 can also be replaced with period 10.

[0354] With a maximum period of 480, it can support {0,20,40,80,160,320,480} or {0,20,40,80,160,240,320,400,480}. In addition, period 0 can also be replaced with period 10.

[0355] With a maximum period of 640, it can support {0,20,40,80,160,320,640} or {0,20,40,80,160,240,320,480,640}. In addition, period 0 can also be replaced with period 10.

[0356] With a maximum period of 960, it can support {0,20,40,80,160,320,640,960} or {0,20,40,80,160,240,320,480,640,800,960}. Furthermore, period 0 can also be replaced with period 10.

[0357] With a maximum period of 1280, it can support {0,20,40,80,160,320,640,1280} or {0,20,40,80,160,240,320,480,640,960,1280}. Furthermore, period 0 can also be replaced with period 10.

[0358] New random access configuration entries can also be introduced for the aforementioned PRACH configuration cycle. The selection of this entry can also be notified through new information elements.

[0359] Action 1-3-2) can also be extended to the RO association period (PRACH occasion association period) corresponding to SSB and the pattern of the association period.

[0360] The RO association period and its pattern can be extended based on the new PRACH setting period in action 1-3-1). The RO association period can be updated based on the maximum PRACH setting period. The association pattern period can be determined for each maximum PRACH setting period. The mapping between the PRACH setting period and the SSB's RO association period is shown in Tables 7, 8, and 9 when the maximum PRACH setting period is 320ms, 480ms, and 640ms.

[0361] [Table 7]

[0362] [Table 8]

[0363] [Table 9]

[0364] The association period pattern contains one or more association periods, and the pattern between the RO and SSB indexes repeats every 320ms, 480ms, or 640ms.

[0365] Table 10 shows examples of entries for new random access settings for formats 0, 1, 2, or 3.

[0366] [Table 10]

[0367] Additionally, regarding the preamble, formats 1, 2, or 3 can be used instead of format 0. Furthermore, regarding the x-value, 24, 40, 48, 64, 80, 96, or 128 can be used instead of 32. The y-value can be 0, 1, 2, ..., x-1. The subframe number can be 0, 1, 2, ..., 9, or a possible combination of multiple values.

[0368] Table 11 shows examples of entries for new random access settings for formats A1, A2, A3, B1, B4, C0, or C2.

[0369] [Table 11]

[0370] Additionally, regarding the preamble, other formats or combinations of formats with two symbol lengths can be used instead of format A1. For example, format A1, B1, and C0 can also be used. Furthermore, regarding the x-value, 24, 40, 48, 64, 80, 96, and 128 can be used instead of 32. The y-value can be 0, 1, 2, ..., x-1. The subframe number can be 0, 1, 2, ..., 9, 10, 11, ..., or a possible combination of multiple values.

[0371] Additionally, the format can use a 4-symbol length format, or A2, A2, and B2. The format can also use a 6-symbol length format, or A3, A3, B3, and C2. The number of PRACH slots within a subframe can be 1 or 2. Other values ​​can also be used for the start symbol.

[0372] The number of time-domain ROs for each PRACH slot can be determined by satisfying the start symbol + N. t RA,slot ×N dur RA Numbers less than or equal to 14.

[0373] Actions 1-4 can also execute the settings of Actions 1-1, 1-2, and 1-3.

[0374] Actions 1-1), 1-2), and 1-3 above can be performed independently or in combination. The resources of the RO and action 1) can be different from, the same as, or overlap with traditional ROs and resources, and can also be notified from the base station.

[0375] The parameters for actions 1-1), 1-2), and 1-3 above can also be notified via new information elements. Upon receiving this new information element, the UE can perform settings based on it and ignore traditional information elements (e.g., information elements without a suffix or those with a suffix other than -r19). If the new information element is not received, traditional information elements can be referenced.

[0376] Regarding actions 1-2) and 1-3) above, the selection of random access configuration entries can be notified through new information elements. Multiple random access configuration tables considering frequency bands and duplex modes can also be specified, with different or identical information elements used for entry specification in these tables. The number of entries in these tables can also vary. When the same information element is used in this table, the maximum value of that information element (e.g., maxEntity) can also determine the maximum value across all tables. When different information elements are used in this table, the maximum value of new information elements can be determined based on this table.

[0377] The UE can report the following as UE capabilities.

[0378] • The number and / or maximum number of ROs that are frequency-multiplexed in the time domain of one RO in Action 1-1).

[0379] • The PRACH setting cycle value and / or maximum value in actions 1-3)

[0380] Action 1) can also be applied to contention-based 4-step RACH processes, contention-based 2-step RACH processes, contention-free 4-step RACH processes, contention-free 2-step RACH processes, and processes that send other PRACH signals, such as sending PRACH as WUS (Wake upsignal).

[0381] Action 1) can be applied to one or more PRACH settings shown in 1)-4) below.

[0382] 1) PRACH preambles of specific, subset, or full sequence lengths. For example, PRACH preambles of lengths of 839, 139, 571, or 1151.

[0383] 2) Specific, subset, or complete PRACH formats. For example, a portion or all of the PRACH format {0,1,2,3,A1,A2,A3,B1,B2,B3,B4,C0,C2}.

[0384] 3) Specific, subset, or full PRACH subcarrier spacing.

[0385] 4) Subcarrier spacing of specific, subset, or all PUSCHs.

[0386] Additionally, the PRACH configuration index (prach-ConfigurationIndex-r19, msgA-PRACH-ConfigurationIndex) can be from 0 to maxEntity or from 256 to maxEntity.

[0387] Action 2) can expand the non-uniform PRACH resources of each SSB.

[0388] Figure 27 This is a diagram illustrating an example of the PRACH resources of each SSB involved in Embodiment 9 of the present invention. (See diagram below.) Figure 27 As shown, in traditional specifications, the number of SSBs N per RO and the number of preambles R per SSB are defined. For example, ssb-perRACH-OccasionAndCB-PreamblesPerSSB is used for associating SSBs with PRACHs. The PRACH resources for each SSB are uniform.

[0389] Figure 28 This is a diagram illustrating an example of a PRACH resource associated with an SSB, as described in Embodiment 9 of the present invention. Figure 28 As shown, in the example of uniform PRACH resources, 64 preambles can also be associated with each SSB. This increases the base station's monitoring time. The number of PRACH resources can be configured to ensure UE access in the most congested SSB.

[0390] On the other hand, in the case of non-uniform PRACH resources, for example, 64 preambles can be associated with SSB0, and 20 preambles can be associated with each of the other SSBs. As a result, the monitoring time of the base station is shortened.

[0391] Non-uniform PRACH resources can also be introduced for each SSB. Due to flexibility, different numbers of preambles can be associated with different SSBs. SSBs can be classified into two or more groups, and the number of preambles associated with SSBs within the same group can be the same, while the number of preambles associated with SSBs in different groups can also be different.

[0392] For example, to signal non-uniform PRACH resources, the traditional parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB can be used in part, or multiple groups can be used. Alternatively, new parameters can be used to determine the number of preambles per SSB, instead of the traditional parameters. The following describes how to configure non-uniform PRACH resources for each SSB.

[0393] Action 2-1) can also associate different numbers of PRACH preambles with different SSBs.

[0394] Action 2-1-1) can also set the number of PRACH preambles for each SSB.

[0395] The number of PRACH preambles per SSB can also be set. Alternatively, the mapping between the number of SSBs and the number of ROs can be left undefined. The number of PRACH preambles per SSB can be selected from conventional settings. That is, it can be selected from {4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64, 128, 256, 512}.

[0396] The number of PRACH preambles for each SSB can be selected from conventional set values ​​and appended values. For example, it can be selected from {4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,96,128,160,192,224,256,320,384,448,512}. For an SSB, values ​​exceeding 64 can also be mapped to multiple ROs.

[0397] The number of PRACH preambles for each SSB can also be set using a new parameter. This new parameter allows `preambleNumofSSB-r19` and `msgAPreambleNumofSSB-r19` to be introduced into Type 1 and Type 2 RACH procedures, respectively.

[0398] The maximum number of PRACH preambles for each RO can also be set using new parameters. As this new parameter, `maxPreambleNumPerRO-r19 / msgAMaxPreambleNumPerRO-r19` can be introduced into Type 1 and Type 2 RACH procedures respectively. The value of `maxPreambleNumPerRO-r19 / msgAMaxPreambleNumPerRO-r19` can be less than the total number of preambles set for the UE based on `totalNumberOfRA-Preambles` for Type 1 RACH procedures and `msgA-TotalNumberOfRA-Preambles` for Type 2 RACH procedures.

[0399] The number of PRACH preambles for S SSBs can also be specified using a new list of parameters. This new parameter can be introduced into Type 1 / Type 2 RACH procedures using `preambleNumofSSBList-r19 / msgA-preambleNumofSSBList-r19`. S can be the actual number of SSBs transmitted. For example, S can be set based on `ssb-PositionsInBurst` contained in `SIB1` or `ServingCellConfigCommon`. The s-th entry in this list can also correspond to the s-th actually transmitted SSB. Here, s = 0, 1, ..., S-1. The maximum number of entries in the list can be 4, 8, or 64, determined based on the frequency band or other parameters, or based on the actual number of transmitted SSBs.

[0400] For example, the following information elements can be included in RACH-ConfigCommon.

[0401]

[0402] Alternatively, the following information elements can also be set.

[0403]

[0404] For example, the following information elements can be included in RACH-ConfigCommonTwoStepRA-R16.

[0405]

[0406] Alternatively, information elements as shown below can also be set.

[0407]

[0408] }

[0409] (Action 2-1-2) SSBs can also be mapped to ROs and PRACH preambles. Different RO numbers can also be associated with different SSBs.

[0410] Figure 29 This is a diagram illustrating an example of a PRACH resource associated with an SSB, as described in Embodiment 9 of the present invention. Figure 29 As shown, the number of preambles mapped to SSBs in the past can also be accumulated, with SSBs mapped to ROs that have a specific PRACH preamble set. Alternatively, steps 1) and 2) shown below can also be performed.

[0411] 1) The 0th actually transmitted SSB is mapped to preamble index 0 and RO index 0. Mapping the 0th actually transmitted SSB continues until it becomes the RO index ((n s -1) / N total And the preamble index (n) s -1) mod N total Until then. The mapping order can be that the preamble index is first (1st) and the RO index is second (2nd).

[0412] 2) When s is 1 or more, the s-th actually sent SSB is mapped to the RO index T. s-1 / N total And the preamble index T s-1 mod N total Map the s-th actually sent SSB until it becomes the RO index (T). s-1 +n s -1) / N total And the preamble index (T) s-1 +n s -1) mod N total until.

[0413] Among them, n is based on action 2-2-1). s T is the number of PRACH preambles for the s-th valid SSB. s It is the cumulative number of PRACH preambles mapped to SSBs 0 through s. That is, T s =Σ s=0 s n s N total This is the total number of preambles set during the Type 1 / Type 2 RACH process based on action 2-1-1's `totalNumberOfRA-Preambles` / `msgA-TotalNumberOfRA-Preambles`. Alternatively, it can be the maximum number of preambles set during the Type 1 / Type 2 RACH process using `maxPreambleNumPerRO-r19` / `msgAMaxPreambleNumPerRO-r19`. The RO index and SSB index mentioned above are indices during association, and the index values ​​can exceed the number of valid SSBs through multiple mappings.

[0414] Action 2-2) can also introduce new parameters for grouping SSBs based on the association between PRACH resources and SSBs.

[0415] Action 2-2-1) The number of PRACH preambles per SSB can be set as follows.

[0416] SSBs can also be classified into two or more groups. Within a group, the same number of preambles can be assumed for each SSB. Between different groups, the number of preambles associated with an SSB can also be different.

[0417] The number of PRACH preambles for each SSB can also be set using a new parameter. This new parameter allows `preambleNumofSSB-r19` and `msgAPreambleNumofSSB-r19` to be introduced into Type 1 and Type 2 RACH procedures, respectively.

[0418] The maximum number of PRACH preambles for each RO can also be set using new parameters. As this new parameter, `maxPreambleNumPerRO-r19 / msgAMaxPreambleNumPerRO-r19` can be introduced into Type 1 and Type 2 RACH procedures respectively. The value of `maxPreambleNumPerRO-r19 / msgAMaxPreambleNumPerRO-r19` can be less than the total number of preambles set for the UE based on `totalNumberOfRA-Preambles` for Type 1 RACH procedures and `msgA-TotalNumberOfRA-Preambles` for Type 2 RACH procedures.

[0419] A new parameter can be used to notify the SSB index of a group. This new parameter can be introduced into the Type 1 / Type 2 RACH procedure as ssbIndexofRoNumGroup-r19 / msgASSBIndexofRoNumGroup-r19, respectively. A bitmap can be used to indicate which SSB belongs to which group. The length of this bitmap can be 4, 8, or 64, determined based on the frequency band or other parameters, or based on the actual SSB being transmitted. A 1 or 0 in a specific bit of the bitmap indicates that the corresponding SSB belongs to that group. When notifying that a particular SSB belongs to multiple groups, the group notification can be made using any of the following: the smallest index, the first group, or the first entry in the list.

[0420] Alternatively, some or all of the above parameters can be used to notify an SSB group. As this new parameter, roNumGroup-r19 / msgARoNumGroup-r19 can be introduced into the Type 1 / Type 2 RACH procedure, respectively.

[0421] Alt.1) As a design with multiple groups, the number of PRACH preambles for each SSB group can also be notified through parameters of a new list. As parameters of this new list, roNumGroupList-r19 / msgARoNumGroupList-r19 can be introduced into Type 1 / Type 2 RACH procedures respectively. The number or maximum number supported by this list can be defined by the specification, set, or notified through UE capabilities.

[0422] Alt.2) For designs involving two or a specific number of groups, a new parameter can be used to inform the number of PRACH preambles for the two SSB groups. As this new parameter, roNumGroup1-r19 / msgAroNumGroup1-r19 and roNumGroup2-r19 / msgAroNumGroup2-r19 can be introduced into the Type 1 / Type 2 RACH procedure, respectively.

[0423] Action 2-2-2) can also be applied in the mapping of SSB to RO and PRACH preambles.

[0424] Figure 30 This is a diagram illustrating an example of specification changes related to the RACH setting in Embodiment 9 of the present invention. (See diagram below.) Figure 30 As shown, in the Type 1 RACH process, a list of roNumGroup-r19 elements can be set in RACH-ConfigCommon as maxRoNumGroupList-r19.

[0425] Figure 31 This is a diagram illustrating an example of specification changes related to the RACH setting in Embodiment 9 of the present invention. (See diagram below.) Figure 31 As shown, in the Type 1 RACH process, two groups, RONumGroup1 and RONumGroup2, can be set in RACH-ConfigCommon.

[0426] Actions 2-3) When grouping SSBs based on the association between PRACH resources and SSBs, some traditional parameters can be used.

[0427] Action 2-3-1) The number of PRACH preambles per SSB can be set as follows.

[0428] SSBs can also be classified into two or more groups. Within a group, the same number of preambles can be assumed for each SSB. Between different groups, the number of preambles associated with an SSB can also be different.

[0429] A new parameter can be used to notify the SSB index of a group. This new parameter can be introduced into Type 1 / Type 2 RACH procedures as ssbIndexofRoNumGroup-r19 / msgASSBIndexofRoNumGroup-r19, respectively. A bitmap can be used to indicate which SSB belongs to which group. The length of this bitmap can be 4, 8, or 64, determined based on frequency bands or other parameters, or based on the actual SSB being transmitted. A 1 or 0 in a specific bit of the bitmap indicates that the corresponding SSB belongs to that group. When notifying that a particular SSB belongs to multiple groups, group notification can be done using any of the following: the smallest index, the first group, or the first entry in the list.

[0430] Alternatively, some or all of the above parameters can be used to notify a single SSB group. As this new parameter, roNumGroup-r19 / msgARoNumGroup-r19 can be introduced into Type 1 / Type 2 RACH procedures, respectively.

[0431] Alt.1) As a design with multiple groups, the number of PRACH preambles for each SSB group can also be notified through parameters of a new list. As parameters of this new list, roNumGroupList-r19 / msgARoNumGroupList-r19 can be introduced into Type 1 / Type 2 RACH procedures respectively. The number or maximum number supported by this list can be defined by the specification, set, or notified through UE capabilities.

[0432] Alt.2) For designs involving two or a specific number of groups, a new parameter can be used to indicate the number of PRACH preambles for the two SSB groups. This new parameter allows roNumGroup1-r19 / msgAroNumGroup1-r19 and roNumGroup2-r19 / msgAroNumGroup2-r1 to be introduced into Type 1 / Type 2 RACH procedures, respectively.

[0433] In Alt.1) and Alt.2) above, one or more of the following restrictions a) and / or b) set for the Type 1 RACH procedure ssb-perRACH-OccasionAndCB-PreamblesPerSSB / Type 2 RACH procedure ssb-perRACH-OccasionAndCB-PreamblesPerSSB as a conventional parameter can be applied between different groups.

[0434] a) Across different groups, the number of preambles R for each SSB of each RO can also be set to the same value, or a multiple of a value such as 4, 8, 16, 32 or 64.

[0435] b) Between different groups, the SSB number N for each RO can also only be set to the same value, adjacent values, or values ​​of the three adjacent levels.

[0436] Action 2-3-2) When mapping SSB to RO and PRACH preamble, the mapping method can also be Action 2-1-2 with the following changes applied.

[0437] n s It can be through n s =R、(N>1)n s = (1 / N) × R, (N<1), s=0,1,… The number of the s-th PRACH preamble is calculated.

[0438] N total It can be any of the following.

[0439] • The total number of preambles set in the Type 1 / Type 2 RACH process respectively via totalNumberOfRA-Preambles / msgA-TotalNumberOfRA-Preambles.

[0440] • The initial group of N or n s

[0441] • The maximum N or n of all groups set s

[0442] • The common N or n under the conditions described in b) above s

[0443] Figure 32 This is a diagram illustrating a specification change example related to the RACH setting in Embodiment 9, which is used to explain the implementation of the present invention. Figure 32 The diagram illustrates that, in the case of setting two groups during a Type 1 RACH process, in order to notify the association of SSBs with PRACH resources, the traditional parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is partially used, and the number of SSBs for each RO is limited to three adjacent levels, with the number of preambles for each SSB set to the same value.

[0444] Figure 33 This is a diagram illustrating an example of associating SSB with RO in Embodiment 9, which is used to explain an implementation of the present invention. Figure 33 The application is shown. Figure 32Here's an example of the SSB and RO mapping settings. SSB#0 and SSB#1 are group 1. Since oneEighth is set, SSB#0 and SSB#1 are each mapped to 8 ROs. SSB#2 and SSB#3 are group 1. Since oneHalf is set, SSB#2 and SSB#3 are each mapped to 2 ROs.

[0445] Actions 2-4, 2-1, 2-2, and 2-3 can also be performed as follows.

[0446] Actions 2-4-1, 2-2, and 2-3 can also be applied to contention-based 4-step RACH processes, contention-based 2-step RACH processes, contention-free 4-step RACH processes, contention-free 2-step RACH processes, and processes that send other PRACH signals, such as sending PRACH as a WUS (Wake up signal).

[0447] Actions 2-4-2) Actions 2-1), 2-2), and 2-3) can be applied to one or more PRACH settings shown in 1)-4) below.

[0448] 1) PRACH preambles of specific, subset, or full sequence lengths. For example, PRACH preambles of lengths of 839, 139, 571, or 1151.

[0449] 2) Specific, subset, or complete PRACH formats. For example, a portion or all of the PRACH format {0,1,2,3,A1,A2,A3,B1,B2,B3,B4,C0,C2}.

[0450] 3) Specific, subset, or full PRACH subcarrier spacing.

[0451] 4) Subcarrier spacing of specific, subset, or all PUSCHs.

[0452] Actions 2-4-3) Actions 2-1), 2-2), and 2-3) can be applied to one or more SSB settings shown in 1)-3) below.

[0453] 1) SSBs in part or all of the frequency bands of FR1, FR2, FR2-1, and FR3

[0454] 2) SSBs in part or all of the largest numbers 4, 8, and 64

[0455] 3) The actual number of SSBs sent is below a specific value, such as 4, 8, or 12.

[0456] Action 2-4-4) can also switch between uniform and non-uniform mapping of PRACH resources for each SSB. With one or more RRC parameters from Actions 2-1), 2-2), and 2-3) set or present, the UE can assume that the mapping of PRACH resources to SSBs is non-uniform. That is, the UE can assume that the mapping is performed via Actions 2-1), 2-2), and 2-3), or it can ignore conventional parameters (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB, msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB, parameters without suffixes, and parameters with suffixes other than -r19).

[0457] On the other hand, if one or more of the RRC parameters in Actions 2-1), 2-2), and 2-3) are not set or do not exist, the UE can envision a uniform mapping of PRACH resources to SSBs and perform the traditional mapping using the traditional parameters.

[0458] Action 3) The DCI for fast adaptation of PRACH settings can be configured as follows. Additionally, PRACH adaptation can be based on PRACH settings from Action 1) and / or Action 2).

[0459] Action 3-1) The content of the notification for the application of adapted PRACH configuration can be as follows.

[0460] As a parameter associated with PRACH, the following can also be notified.

[0461] ·PRACH preamble format

[0462] Time-domain resources

[0463] Frequency domain resources

[0464] ·Root sequence

[0465] ·prach-ConfigurationIndex

[0466] • Cyclic shift and restricted types (unrestricted, restricted set A, or restricted set B)

[0467] PRACH Opportunity Index

[0468] • A collection of PRACH opportunity indexes and associated single indexes or mask indexes

[0469] • A collection of PRACH opportunity indices associated with a PRACH opportunity index or a single SSB

[0470] • Preamble index associated with a preamble index or a single SSB or a single RO

[0471] • Mapping information for SSB and PRACH

[0472] • A threshold used to select the received signal strength (e.g., RSRP of an ES-state cell) for waking up the cell or base station.

[0473] • A threshold used to select the received signal strength (e.g., RSRP of an ES-state cell) of the SSB of a cell used to determine PRACH parameters.

[0474] • Indexes during association

[0475] Msg1 with random access

[0476] • Actual SSB sent

[0477] • Introduce additional PRACH parameters for action 1) and / or action 2).

[0478] The following can also be notified as additional parameters.

[0479] • Apply the time or time offset set to adapt to PRACH (action 4-2 described later). Alt.3 Refer to 9.

[0480] • Validity period of PRACH settings for application adaptation

[0481] Action 3-1-2) can also specify RRC signaling that notifies settings related to the parameters of Action 3-1-1). DCI can also select one or more of these settings.

[0482] New information elements can also be introduced to notify the setting of parameters in action 3-1-1). For example, the new information element adaptPrachSetting-r19 can include a setting. For example, the new information element adaptPrachSettingList-r19 can include a list of settings. The maximum value of the settings in the list can also be 1, 2, 4, 8, 16, 32, or other integers. The UE can also report the maximum value of the supported list settings to the base station as a UE capability.

[0483] When the UE receives the new information element mentioned above related to the parameters of action 3-1-1) but has not yet received the DCI for selecting settings, the UE can refer to the initial settings in the list or the settings notified by the system information.

[0484] When the UE receives a DCI notification indicating that the setting has been selected, the UE may decide whether to change or not change the parameters in action 3-1-1) based on the DCI notification. If the parameters related to the setting are changed, other parameters not included in action 3-1-1) may remain unchanged, or refer to the preceding setting, or refer to the default setting. The default setting may be a setting notified by other new information elements, a setting notified by traditional information elements set by PRACH, or a setting notified by system information.

[0485] Table 12 shows four examples of settings when a new information element contains a settings list.

[0486] [Table 12]

[0487] Figure 34 This is a diagram illustrating examples of specification changes related to multiple RACH settings in Embodiment 9 of the present invention.

[0488] adaptPrachSetting-r19 is a new setting information element, and adaptPrachSettingList-r19 is a list of new setting information elements.

[0489] Action 3-2) Adapting PRACH settings can also be done via DCI notification as follows.

[0490] Action 3-2-1) can be notified using the existing DCI format.

[0491] Action 3-2-1-1 can also be notified via a new field in DCI format 1_0 scrambled by P-RNTI or other RNTI.

[0492] For example, the size of a new field called the PRACH adaptation field can be determined based on the setting of action 3-1-2). For example, when the setting of action 3-1-2) is set to M, the size of the new field can be ceil(log2M). The value 0 can also indicate the initial setting of the list of actions 3-1-2). Table 13 shows an example of this field.

[0493] [Table 13]

[0494] For example, when the setting value of action 3-1-2) is set to M, the size of the new field can be ceil(log2M+1). The value 1 can also indicate the initial setting of the list of actions 3-1-2). Table 14 is an example of this action.

[0495] [Table 14]

[0496] The existence of a new field can also be determined based on newly defined parameters. For example, it can be determined by `adaptPrachSettingList-r19` in action 3-1-2. The field may exist if `adaptPrachSettingList-r19` exists, but not otherwise. Alternatively, it can be determined by `prachAdaptationConfig`. The field may exist if `prachAdaptationConfig=true`, but not otherwise.

[0497] The position of a new field included in a DCI can be after the last, the beginning, a specific bit field (such as the TRS availability indication), or a reserved bit. The short message indicator field can be used to indicate whether a new field is included. Table 15 shows an example of this action.

[0498] [Table 15]

[0499] Action 3-2-1-2 can also be notified via existing fields of DCI format 1_0 scrambled by P-RNTI or other RNTI. For example, it can also be notified via the Short messages field. The existing Short messages field uses the first 4 bits and has 4 reserved bits. Table 16 shows an example of this action.

[0500] [Table 16]

[0501] Alternatively, you can use either a 1-bit notification or a 2-bit notification as shown in Table 16.

[0502] Action 3-2-2) can also be notified via a new DCI format, such as DCI format 2_x. This new DCI format is used to notify of PRACH adaptation settings. This new DCI format contains fields for notifying of PRACH adaptation settings. The design of these fields can also be the same as in Action 3-2-1-1).

[0503] Action 3-2-3) The DCI in Action 3-2) can be scrambled using either a traditional RNTI or a new RNTI. For example, a traditional RNTI can be P-RNTI, SI-RNTI, or PEI-RNTI. A new RNTI can be PA-RNTI. PA-RNTI can be common to all UEs or UE groups. UE grouping can be determined based on UE-ID and group number.

[0504] Actions 3-3), 3-1), and 3-2 can also be set up as follows.

[0505] Actions 3-3-1 and 3-2 can also be applied to contention-based 4-step RACH processes, contention-based 2-step RACH processes, contention-free 4-step RACH processes, contention-free 2-step RACH processes, and processes that transmit other PRACH signals, such as PRACH as WUS (Wake up signal).

[0506] Actions 3-3-2), 3-1), and 3-2) can be applied to one or more PRACH settings shown in 1)-4) below.

[0507] 1) PRACH preambles of specific, subset, or full sequence lengths. For example, PRACH preambles of lengths of 839, 139, 571, or 1151.

[0508] 2) Specific, subset, or complete PRACH formats. For example, a portion or all of the PRACH format {0,1,2,3,A1,A2,A3,B1,B2,B3,B4,C0,C2}.

[0509] 3) Specific, subset, or full PRACH subcarrier spacing.

[0510] 4) Subcarrier spacing of specific, subset, or all PUSCHs.

[0511] Actions 3-1 and 3-2 can be applied to one or more SSB settings shown in 1)-3) below.

[0512] 1) SSBs in part or all of the frequency bands of FR1, FR2, FR2-1, and FR3

[0513] 2) SSBs in part or all of the largest numbers 4, 8, and 64

[0514] 3) The actual number of SSBs sent is below a specific value, such as 4, 8, or 12.

[0515] Action 4) The UE actions involved in adapting to PRACH settings in early applications can be as follows.

[0516] Action 4-1) PRACH adaptation indication (PAI) can be received via DCI as follows.

[0517] The UE can receive the DCI of the PAI in the PO (Paging Occasion).

[0518] Alt.1) The UE can receive the DCI of the PAI in the PO as in Action 3-2. The UE can also receive the DCI directed to the device in all or some of the POs. The PO used to receive the PAI can be set through system information, RRC signaling, or DCI. In multi-beam operation, the UE can envision repeating some PAIs in all transmitted beams, or it can select the beams related to the reception of the PAI based on the UE implementation.

[0519] Alt.2) The UE can receive the DCI of the PAI in a PEI-O (Paging Early Indication Occasion) as in Action 3-2. The UE can also receive the DCI directed to itself in all or part of the PEI-Os. The PEI-O used to receive the PAI can be set through system information, RRC signaling, or DCI. In multi-beam operation, the UE can envision repeating some PAIs in all transmitted beams, or it can select the beams related to the reception of the PAI based on the UE implementation.

[0520] Alt.3) The UE can receive the DCI of PAI in newly defined opportunities as in action 3-2. For example, the DCI can be received in PAI-O (PRACH Adaptation Indication Occasions). The PAI-O can be configured via system information, RRC signaling, or DCI. Any of the following 1)-3) can be configured or supported for the UE.

[0521] 1) PAI-O settings can be the same across all UEs, or they can be common across all UEs.

[0522] 2) PAI-O settings can be the same within a UE group, or they can be common within a UE group. UE grouping can be determined based on UE-ID and group number.

[0523] 3) PAI-O settings can vary for each UE. That is, they can also be set independently for each UE.

[0524] The UE can also monitor multiple PAI-Os per DRX cycle.

[0525] When PAI is available to transmit, a PAI-O can be a collection of PDCCH monitoring opportunities or can consist of multiple time slots (e.g., subframes or OFDM symbols).

[0526] In multi-beam operation, the UE can envision repeating some PAIs in all the transmitted beams, or it can select the beams related to the reception of PAIs based on the UE implementation.

[0527] The number of PAI-Os in each SSB is defined as X. X can be set by parameters, and can be 1 if not set.

[0528] The actual number of SSBs S sent can be determined based on the ssb-PositionsInBurst contained in SIB1.

[0529] PAI-O can be a group of S×X consecutive PDCCH monitoring opportunities. The x×S+Kth PDCCH monitoring opportunity of PAI-O facing PAI can correspond to the Kth transmitted SSB, x=0,1,…X-1, K=1,2,…,S. PDCCH monitoring opportunities facing PAI that do not overlap with UL symbols, determined based on tdd-UL-DL-ConfigurationCommon, can be numbered sequentially starting from zero from the first PDCCH monitoring opportunity facing PAI within PAI-O. When the UE detects a PAI within PAI-O, the UE may not monitor subsequent monitoring opportunities associated with the same PAI-O.

[0530] Action 4-2) After receiving the PAI, the UE can perform the following actions.

[0531] Action 4-2-1) Once the UE receives the PAI, it can start sending PRACH based on the PAI application adaptation PRACH settings from the following timing.

[0532] Alt.1) After a predefined time or time offset has elapsed since the PAI was received, PRACH transmission adapted to the PRACH settings can begin based on that PAI. For example, the unit of X can be set to ms, s, symbol, subframe, radio frame, PRACH period, association period, or association mode, and the time offset can be X. The unit of Y can be set to ms, s, symbol, subframe, radio frame, PRACH period, association period, or association mode, and the time can be the next or the next Y.

[0533] Alt.2) Time or time offset can be set via SIB. It can also be set or notified via SIB1, other SIBs, or a new SIB. The notification content can be the same as in Alt.1.

[0534] Alt.3) can also dynamically notify the time or time offset. The time or time offset information can be notified along with the PRACH adaptation settings or via DCI in Action 3-2) within PAI. The notification content can also be the same as Alt.1.

[0535] Action 4-2-2) When the UE receives PAI, the new adapted PRACH setting becomes effective from the time based on Action 4-2-1), and the old PRACH setting set for the UE immediately prior can be used for the following purposes.

[0536] Alt.1) The UE can assume that the old PRACH setting is valid before the new PRACH setting is applied.

[0537] Alt.2) The UE may also set the unit of Z, such as ms, s, symbol, subframe, radio frame, PRACH period, association period or association mode, before the application of the new PRACH setting, assuming that the old PRACH setting is valid before the start or end of Z.

[0538] Alt.3) The UE can assume that the old PRACH setting is invalid based on the time it receives the PAI or is notified to adapt the PRACH setting, or it can assume that the base station does not receive PRACH transmissions based on the old PRACH setting.

[0539] Alt.4) After receiving PAI or being notified to adapt to PRACH settings, the UE can set the unit of A to ms, s, symbol, subframe, radio frame, PRACH period, association period or association mode. It is assumed that from the beginning or end of A, the old PRACH settings are invalid, or the base station can be assumed not to receive PRACH transmissions based on the old PRACH settings.

[0540] Alt.5) Regardless of whether a new PRACH setting is applied, the old PRACH setting can be assumed to be valid. That is, both the old and new PRACH settings can be valid.

[0541] Action 4-2-3) The traditional system information update process can change the PRACH setting. After receiving the PAI, the UE can change the PRACH setting to update the system information after a predetermined time.

[0542] Alt.1) You can use all parameters of the updated system information, or you can ignore the PAI received in the past.

[0543] Alt.2) The UE can obtain parameters that were not notified by the PAI from the updated system information. The UE can use the parameters of the most recently received PAI.

[0544] Alt.3) The UE can ignore parameters that change based on system information. When the UE receives a PAI, it can update the PRACH settings based solely on other PAIs.

[0545] The RO set by SIB1 and the RO set by PAI can be different, can not overlap, can partially overlap, or can be the same.

[0546] The ROs set for different PAIs can be different, non-overlapping, partially overlapping, or the same.

[0547] The X, Y, Z, and A mentioned above can be integers.

[0548] Furthermore, the usage of any of the above embodiments can be set through higher-layer parameters, reported from terminal 20 to base station 10 as a UE capability, specified through a standard, reported from terminal 20 to base station 10 as a UE capability and set through higher-layer parameters, or notified through DCI. The base station-oriented WUS (Wake-up signal) can be used for cell DTX in addition to cell DRX.

[0549] Additionally, you can define whether UE capabilities support cell DTX and cell DRX. You can also define whether UE capabilities support dynamic activation or deactivation of cell DTX and cell DRX. Furthermore, you can define whether UE capabilities support cell DTX and cell DRX accompanied by UE DRX or CDRX.

[0550] Additionally, cell DTX / DRX can be replaced with cell DTX and / or cell DRX. Activation / deactivation can be replaced with activation and / or deactivation, activation and / or deactivation, etc.

[0551] The above embodiments enable PRACH to be adapted to support NES.

[0552] That is, providing a technology that makes random access channels suitable for base stations that can migrate to a power-saving state.

[0553] (Device structure)

[0554] Next, an example of the functional structure of the base station 10 and the terminal 20 performing the processes and actions described above will be explained. The base station 10 and the terminal 20 include the functions of performing the embodiments described above. However, the base station 10 and the terminal 20 may each possess only the functions of any one of the proposed embodiments.

[0555] <Base Station 10>

[0556] Figure 35 This is a diagram illustrating an example of the functional structure of a base station. (For example...) Figure 35 As shown, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130 and a control unit 140. Figure 35 The functional structure shown is merely an example. As long as the actions involved in the embodiments of the present invention can be performed, the functional distinctions and names of the functional units can be arbitrary. The transmitting unit 110 and the receiving unit 120 can also be referred to as communication units.

[0557] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and wirelessly transmitting the signal. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining, for example, higher-level information from the received signals. Furthermore, the transmitting unit 110 has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, DL data, etc., to the terminal 20. Additionally, the transmitting unit 110 transmits setting information, etc., as described in the embodiment.

[0558] The setting unit 130 stores preset setting information and various setting information sent to the terminal 20 into a storage device, and reads it from the storage device as needed. The control unit 140, for example, performs overall control of the base station 10, including control related to signal transmission and reception. Alternatively, the signal transmission-related functions of the control unit 140 may be included in the transmitting unit 110, and the signal reception-related functions of the control unit 140 may be included in the receiving unit 120. Furthermore, the transmitting unit 110 and the receiving unit 120 may be referred to as a transmitter and a receiver, respectively.

[0559] Terminal 20

[0560] Figure 36 This is a diagram illustrating an example of the functional structure of a terminal. (For example...) Figure 36 As shown, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. Figure 36 The functional structure shown is merely an example. As long as the actions involved in the embodiments of the present invention can be performed, the functional distinctions and names of the functional units can be arbitrary. The transmitting unit 210 and the receiving unit 220 can also be referred to as communication units.

[0561] The transmitting unit 210 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains higher-layer signals from the received physical layer signals. Furthermore, the transmitting unit 210 transmits HARQ-ACK, and the receiving unit 220 receives setting information, etc., as described in the embodiment.

[0562] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220 in a storage device and reads it from the storage device as needed. Furthermore, the setting unit 230 also stores pre-set setting information. The control unit 240 performs overall control of the terminal 20, including control related to signal transmission and reception. Alternatively, the signal transmission-related functions of the control unit 240 can be included in the transmitting unit 210, and the signal reception-related functions of the control unit 240 can be included in the receiving unit 220. Alternatively, the transmitting unit 210 and the receiving unit 220 can be referred to as a transmitter and a receiver, respectively.

[0563] The terminal or base station in this embodiment can be configured as shown in the following descriptions. Alternatively, the following communication methods can also be implemented.

[0564] <Structures related to this embodiment>

[0565] (First item)

[0566] A terminal having: The receiving unit receives parameters related to PRACH settings, i.e., physical random access channel settings, from the base station. The control unit, based on the PRACH settings, determines the resources for the preamble and PRACH opportunities; and The transmitting unit uses the preamble and the resources to send PRACH to the base station. The receiving unit receives a notification using the adapted PRACH settings.

[0567] (Second item)

[0568] According to the terminal described in the first item, the receiving unit receives a notification using the adapted PRACH setting during a paging opportunity.

[0569] (Third item)

[0570] According to the terminal described in the first item, the receiving unit receives a notification using the adapted PRACH setting during an early paging notification opportunity.

[0571] (Item 4)

[0572] According to the terminal described in the first item, the control unit receives a notification using the adapted PRACH settings during a dedicated receiving opportunity.

[0573] (Item 5)

[0574] According to the terminal described in the first item, after receiving a notification that the adapted PRACH setting is used, the control unit assumes that the preceding PRACH setting is invalid.

[0575] (Item 6)

[0576] A communication method in which a terminal performs the following steps: Receive parameters related to PRACH settings, i.e., physical random access channel settings, from the base station; Based on the aforementioned PRACH settings, resources for the preamble and PRACH opportunities are determined; Send PRACH to the base station using the preamble and the resources; and Receive notifications using the adapted PRACH settings.

[0577] According to any of the above structures, a technique is provided to adapt the random access channel to a base station capable of migrating to a power-saving state. According to items two through five, the PRACH can be adapted to support NES.

[0578] (Hardware structure)

[0579] The block diagrams used in the description of the above embodiments ( Figure 35 as well as Figure 36 The diagram illustrates blocks organized by function. These functional blocks (components) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software within the aforementioned single or multiple devices.

[0580] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that performs the sending function is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0581] For example, in one embodiment of this disclosure, the base station 10, terminal 20, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 37 This is a diagram illustrating an example of the hardware structure of a base station 10 and a terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 may also be configured as a computer device that physically includes a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0582] Furthermore, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of base station 10 and terminal 20 can be configured to include one or more of the devices shown in the figures, or it can be configured to not include any of them.

[0583] The functions of base station 10 and terminal 20 are implemented by reading predetermined software (program) into hardware such as processor 1001 and storage device 1002, so that processor 1001 performs calculations and controls the communication of communication device 1004 or controls at least one of reading and writing data in storage device 1002 and auxiliary storage device 1003.

[0584] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the control unit 140 and control unit 240 described above can also be implemented using the processor 1001.

[0585] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage devices 1003 and communication devices 1004, and performs various processes accordingly. As a program, a program is used that causes the computer to perform at least a portion of the actions described in the above embodiments. For example, Figure 35 The control unit 140 of the base station 10 shown can be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Alternatively, for example, Figure 36 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Although it has been described that the various processes described above are executed by one processor 1001, the various processes described above can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by more than one chip. In addition, the program can also be sent from the network via a telecommunications line.

[0586] Storage device 1002 is a computer-readable recording medium, and may be composed of at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Storage device 1002 may also be referred to as a register, cache, main memory (main storage device), etc. Storage device 1002 can store programs (program code), software modules, etc., that are executable for implementing the communication method according to one embodiment of this disclosure.

[0587] The auxiliary storage device 1003 is a computer-readable recording medium, such as at least one of the following: CD-ROM (CompactDisc ROM) or other optical discs, hard disks, floppy disks, magneto-optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs), smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. The aforementioned storage medium may, for example, be a database, server, or other suitable media that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0588] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. It may also be referred to as a network device, network controller, network interface card (NIC), communication module, etc. The communication device 1004 may, for example, be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, transceiver antennas, amplifiers, transceiver units, transmission path interfaces, etc., can also be implemented using the communication device 1004. The transceiver unit may also be physically or logically separated into a transmitting unit and a receiving unit.

[0589] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0590] Furthermore, the processor 1001 and storage device 1002, among other devices, are connected via a bus 1007 for communicating information. The bus 1007 can be configured using a single bus or different buses can be used between each device.

[0591] Furthermore, the base station 10 and the terminal 20 can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or a FPGA (Field Programmable Gate Array), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0592] Figure 38 An example of the structure of vehicle 2001 is shown. For example... Figure 38As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gearshift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. The various forms / implementations described in this disclosure can also be applied to communication devices mounted on the vehicle 2001, for example, to the communication module 2013.

[0593] The drive unit 2002 may be composed, for example, an engine, a motor, or a hybrid power system of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a steering wheel) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0594] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O port) 2033. Signals from various sensors 2021 to 2029 of the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

[0595] The signals from various sensors 2021 to 2029 include current signals from current sensor 2021 that monitors the current of the motor, speed signals of the front and rear wheels obtained by speed sensor 2022, air pressure signals of the front and rear wheels obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depress signal obtained by accelerator pedal sensor 2029, brake pedal depress signal obtained by brake pedal sensor 2026, gear lever operation signal obtained by gear lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0596] The Information Service Unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, which provide various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices via communication modules 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0597] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.

[0598] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 2001 via the communication port. For example, the communication module 2013 can send and receive data with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, front wheel 2007, rear wheel 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, memory (ROM, RAM) 2032, and sensors 2021 to 29 in the vehicle 2001 via the communication port 2033.

[0599] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

[0600] The communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. Additionally, the communication module 2013 also transmits the following signals input to the electronic control unit 2010 via wireless communication to external devices: the front and rear wheel speed signals obtained by the speed sensor 2022; the front and rear wheel air pressure signals obtained by the air pressure sensor 2023; the vehicle speed signal obtained by the vehicle speed sensor 2024; the acceleration signal obtained by the acceleration sensor 2025; the accelerator pedal depressor signal obtained by the accelerator pedal sensor 2029; the brake pedal depressor signal obtained by the brake pedal sensor 2026; the gear shift lever operation signal obtained by the gear shift lever sensor 2027; and the detection signals for detecting obstacles, vehicles, pedestrians, etc., obtained by the object detection sensor 2028.

[0601] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 of the vehicle 2001. Furthermore, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gearshift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, and sensors 2021-2029 of the vehicle 2001 based on the information stored in the memory 2032.

[0602] (Supplement to the implementation method)

[0603] The embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments. Those skilled in the art should understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these values ​​are merely examples, and any appropriate values ​​may be used. The distinctions between items in the above description are not essential to the present invention. Items described in two or more items may be combined as needed, and items described in one item may be applied to items described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. Multiple functional units may be operated by a single physical component, or a single functional unit may be operated by multiple physical components. Regarding the processing described in the embodiments, the order of processing may be interchanged unless there is a contradiction. For ease of explanation, a functional block diagram is used to illustrate the base station 10 and terminal 20, but such a device may also be implemented by hardware, software, or a combination thereof. The software operating according to the embodiments of the present invention via the processor of the base station 10 and the software operating according to the embodiments of the present invention via the processor of the terminal 20 may also be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server and other suitable storage media, respectively.

[0604] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, information notification may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, an RRC connection setup message, an RRC connection reconfiguration message, etc.

[0605] The various forms / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The system may include at least one of 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), other suitable systems, and next-generation systems based on, modified, created, or defined by these systems. Furthermore, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).

[0606] The processing procedures, timing, and flow of the various forms / implementations described in this specification may be rearranged in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order for the methods described in this disclosure, but are not limited to the specific order indicated.

[0607] In this specification, certain actions performed by base station 10 may sometimes also be performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having base station 10, it is obvious that various actions performed to communicate with terminal 20 can be performed by at least one of base station 10 and other network nodes besides base station 10 (e.g., considering MME or S-GW, but not limited to these). The above example illustrates the case where there is only one other network node besides base station 10, but other network nodes can also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0608] The information or signals described in this disclosure can be output from a higher (or lower) layer to a lower (or higher) layer. They can also be input or output via multiple network nodes.

[0609] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0610] The determination in this disclosure can be made by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value).

[0611] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0612] In addition, software, commands, information, etc., can be sent and received via a transmission medium. For example, when software is sent from a webpage, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0613] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0614] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.

[0615] The terms “system” and “network” as used in this disclosure are used interchangeably.

[0616] Furthermore, the information, parameters, etc., described in this disclosure can be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources can also be indicated using indexes.

[0617] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, therefore the various names assigned to these channels and information elements are non-limiting in any respect.

[0618] In this disclosure, the terms "base station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0619] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its coverage area can be divided into several smaller areas, each of which can provide communication services through a base station subsystem (e.g., a small indoor base station RRH: Remote Radio Head). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0620] In this disclosure, the terms "Mobile Station (MS)," "User Terminal (user terminal)," "User Equipment (UE)," and "Terminal" can be used interchangeably.

[0621] For mobile stations, those skilled in the art sometimes also use the following terms: subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0622] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Furthermore, at least one of the base station and mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). In addition, at least one of the base station and mobile station also includes devices that do not necessarily move during communication. For example, at least one of the base station and mobile station can be an IoT (Internet of Things) device such as a sensor.

[0623] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, the communication between the base station and the user terminal can be replaced by communication between multiple terminals 20 (e.g., D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.), and various forms / implementations of this disclosure can also be applied. In this case, the terminal 20 can also be configured to have the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc. can also be replaced with side channel.

[0624] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, the base station can also be configured to have the functions of the aforementioned user terminal.

[0625] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" or "determining" may include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" or "determining." Furthermore, "determining" or "determining" may include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory), which are considered as actions of "determining" or "determining." Moreover, "determining" or "determining" may include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" or "determining." That is, "judgment" and "decision" can include situations where certain actions are regarded as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0626] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.

[0627] The reference signal can be simply called RS (Reference Signal), or, depending on the standard applied, pilot.

[0628] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the word "based on" means both "based on only" and "based on at least".

[0629] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to a first element and a second element does not imply that only two elements can be used, or that in any form the first element must precede the second element.

[0630] Alternatively, the term "unit" in the structure of the above devices can be replaced with "section," "circuit," "equipment," etc.

[0631] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.

[0632] A radio frame can consist of one or more frames in the time domain. In the time domain, one or more frames can be called subframes. A subframe can also consist of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0633] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.

[0634] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.

[0635] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Additionally, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type B.

[0636] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can each be referred to by other corresponding names.

[0637] For example, one subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and one time slot or one mini-time slot can also be called a TTI. That is, at least one of the subframe and TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., symbols 1-13), or a period longer than 1ms. In addition, the unit representing TTI can also be called a time slot, mini-time slot, etc., instead of a subframe.

[0638] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each terminal 20) in units of TTI. However, the definition of TTI is not limited to this.

[0639] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than that TTI.

[0640] Furthermore, when one time slot or one mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also become the minimum time unit for scheduling. In addition, the number of time slots (mini-time slots) constituting the minimum time unit for scheduling can also be controlled.

[0641] A TTI with a duration of 1ms can also be called a normal TTI (TTI in LTE Rel.8-12), a regular TTI, a long TTI, a normal subframe, a regular subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0642] Additionally, for long TTIs (e.g., normal TTIs, subframes, etc.), a TTI with a duration of more than 1ms can be used as a replacement, and for short TTIs (e.g., shortened TTIs, etc.), a TTI with a duration of less than a long TTI and more than 1ms can be used as a replacement.

[0643] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0644] Furthermore, the temporal domain of an RB can contain one or more symbols, and can be 1 time slot, 1 mini-time slot, 1 subframe, or 1 TTI in length. 1 TTI, 1 subframe, etc., can each be composed of one or more resource blocks.

[0645] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0646] Furthermore, a resource block can consist of one or more resource elements (REs). For example, 1RE can be a radio resource area with 1 subcarrier and 1 symbol.

[0647] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can also represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0648] A BWP can include a UL BWP and a DL BWP. Terminal 20 can also be configured with one or more BWPs within a single carrier.

[0649] At least one of the configured BWPs can be active, and terminal 20 does not intend to transmit or receive predetermined signals / channels outside of the active BWP. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."

[0650] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained in a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0651] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure may also include cases where the noun following these articles is in a plural form.

[0652] In this disclosure, the phrase "A and B are different" can mean "A and B are not the same." Furthermore, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0653] The various forms / implementations described in this disclosure can be used individually, in combination, or switched during execution. Furthermore, the notification of predetermined information (e.g., a "Yes X" notification) is not limited to being explicit, but can also be implicit (e.g., not being notified of the predetermined information).

[0654] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0655] Label Explanation

[0656] 10 base stations

[0657] 110 Dispatch Department

[0658] 120 Receiving Department

[0659] 130 Setting Department

[0660] 140 Control Department

[0661] 20 terminals

[0662] 210 Sending Department

[0663] 220 Receiving Department

[0664] 230 Setting Department

[0665] 240 Control Department

[0666] 1001 processor

[0667] 1002 Storage device

[0668] 1003 Auxiliary storage device

[0669] 1004 Communication device

[0670] 1005 Input Device

[0671] 1006 Output Device

[0672] Vehicle 2001

[0673] 2002 Drive Unit

[0674] 2003 Steering Unit

[0675] 2004 Accelerator Pedal

[0676] 2005 Brake Pedal

[0677] 2006 gearshift lever

[0678] 2007 front wheel

[0679] 2008 rear wheel

[0680] 2009 axle

[0681] 2010 Electronic Control Department

[0682] 2012 Information Service Department

[0683] 2013 Communication Module

[0684] 2021 Current Sensor

[0685] 2022 Speed ​​Sensor

[0686] 2023 Barometric Pressure Sensor

[0687] 2024 vehicle speed sensor

[0688] 2025 Accelerometer

[0689] 2026 Brake Pedal Sensor

[0690] 2027 Gearshift sensor

[0691] 2028 Object Detection Sensor

[0692] 2029 Accelerator Pedal Sensor

[0693] 2030 Driver Assistance Systems Department

[0694] 2031 microprocessor

[0695] 2032 Memory (ROM, RAM)

[0696] 2033 Communication Port (IO Port)

Claims

1. A terminal having: The receiving unit receives parameters related to PRACH settings, i.e., physical random access channel settings, from the base station. The control unit, based on the PRACH settings, determines the resources for the preamble and PRACH opportunities; and The transmitting unit uses the preamble and the resources to send PRACH to the base station. The receiving unit receives a notification using the adapted PRACH settings.

2. The terminal according to claim 1, wherein, The receiving unit receives a notification using the adapted PRACH settings during a paging opportunity.

3. The terminal according to claim 1, wherein, The receiving unit receives a notification using the adapted PRACH settings during the paging early notification opportunity.

4. The terminal according to claim 1, wherein, The control unit receives a notification using the adapted PRACH settings during a dedicated receiving opportunity.

5. The terminal according to claim 1, wherein, Upon receiving a notification that the adapted PRACH settings are being used, the control unit assumes that the preceding PRACH settings are invalid.

6. A communication method in which a terminal performs the following steps: Receive parameters related to PRACH settings, i.e., physical random access channel settings, from the base station; Based on the aforementioned PRACH settings, resources for the preamble and PRACH opportunities are determined; Send PRACH to the base station using the preamble and the resources; as well as Receive notifications using the adapted PRACH settings.

Images