Terminal and communication method

Abstract

A terminal according to the present invention comprises: a reception unit that receives, from a base station, a parameter related to physical random access channel (PRACH) configuration; a control unit that determines a resource in a time domain of a PRACH occasion on the basis of the PRACH configuration; and a transmission unit that transmits the PRACH to the base station using the resource. The control unit determines the resource so that the time during which the base station monitors the PRACH decreases.

Description

Terminal and communication method

[0001] The present invention relates to a terminal and a communication method in a wireless communication system.

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that satisfy the requirements of a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption (for example, Non-Patent Document 1).

[0003] Furthermore, in Release 18 of 3GPP (registered trademark), network energy savings has become increasingly important in order to achieve environmental sustainability, carbon neutrality, SDGs (Sustainable Development Goals), reduced operating costs, etc., and methods for saving energy are being considered (e.g., Non-Patent Document 2).

[0004] 3GPP TS 38.300 V17.7.0 (2023-12)"New WID: Enhancements of network energy savings for NR", RP-234065, 3GPP TSG RAN Meeting #102, December 20233GPP TS 38.211 V17.6.0 (2023-09)3GPP TS 38.331 V17.7.0 (2023-12)3GPP TS 38.213 V17.8.0 (2023-12)

[0005] To achieve carbon neutrality and the SDGs, it is becoming increasingly important to reduce the power consumption of base stations, and the introduction of discontinuous transmission and reception (DTX) in base stations is being considered. To achieve an efficient energy saving (ES) state in base stations, it is necessary to adapt the configuration of the physical random access channel (PRACH). Terminals are required to synchronize with the base station in the energy saving state using the PRACH.

[0006] The present invention has been made in view of the above points, and has as its object to adapt a random access channel to a base station that is transitioning to a power saving state.

[0007] According to the disclosed technology, there is provided a terminal including: a receiving unit that receives parameters related to a PRACH (Physical Random Access Channel) setting from a base station; a control unit that determines time domain resources for PRACH opportunities based on the PRACH setting; and a transmitting unit that transmits the PRACH to the base station using the resources, wherein the control unit determines the resources so as to reduce the time that the base station monitors the PRACH.

[0008] According to the disclosed technology, it is possible to adapt the random access channel to a base station that is transitioning to a power saving state.

[0009] FIG. 10 is a diagram for explaining a wireless communication system according to an embodiment of the present invention. FIG. 11 is a diagram for explaining CDRX in NR Release 15. FIG. 12 is a diagram for explaining WUS in NR Release 16. FIG. 13 is a diagram for explaining discontinuous reception at a base station according to a first embodiment of the present invention. FIG. 14 is a diagram for explaining each parameter according to the first embodiment of the present invention. FIG. 15 is a diagram for explaining discontinuous transmission at a base station according to a fifth embodiment of the present invention. FIG. 16 is a diagram for explaining each parameter according to the fifth embodiment of the present invention. FIG. 17 is a diagram for explaining an example of a PRACH format according to a ninth embodiment of the present invention. FIG. 18 is a diagram for explaining an example of PRACH resources in the time domain according to a ninth embodiment of the present invention. FIG. 19 is a diagram for explaining an example of PRACH resources in the frequency domain according to a ninth embodiment of the present invention. FIG. 19 is a diagram for explaining an example of association of SSBs and PRACH resources according to a ninth embodiment of the present invention. FIG. 19 is a diagram for explaining a modification of SIB1 according to a ninth embodiment of the present invention. FIG. 19 is a diagram for explaining an example of PRACH resources according to a ninth embodiment of the present invention. FIG. 19 is a diagram for explaining an example of PRACH resources according to a ninth embodiment of the present invention. FIG. 10 is a diagram for explaining an example of PRACH resources according to Example 9 of an embodiment of the present invention. FIG. 11 is a diagram for explaining an example of PRACH resources according to Example 9 of an embodiment of the present invention. FIG. 12 is a diagram for explaining an example of PRACH resources according to Example 9 of an embodiment of the present invention. FIG. 13 is a diagram for explaining an example of PRACH resources according to Example 9 of an embodiment of the present invention. FIG. 14 is a diagram for explaining an example of PRACH resources according to Example 9 of an embodiment of the present invention. FIG. 15 is a diagram for explaining an example of PRACH resources according to Example 9 of an embodiment of the present invention. FIG. 16 is a diagram for explaining an example of PRACH resources according to Example 9 of an embodiment of the present invention.FIG. 10 is a diagram for explaining an example of PRACH resources according to a ninth embodiment of the present invention. FIG. 11 is a diagram for explaining an example of PRACH resources per SSB according to a ninth embodiment of the present invention. FIG. 12 is a diagram for explaining an example of PRACH resources associated with SSBs according to a ninth embodiment of the present invention. FIG. 13 is a diagram for explaining an example of PRACH resources associated with SSBs according to a ninth embodiment of the present invention. FIG. 14 is a diagram for explaining an example of a specification change related to RACH configuration in a ninth embodiment of the present invention. FIG. 15 is a diagram for explaining an example of a specification change related to RACH configuration in a ninth embodiment of the present invention. FIG. 16 is a diagram for explaining an example of associating SSBs with ROs in a ninth embodiment of the present invention. FIG. 17 is a diagram for explaining an example of a specification change related to multiple RACH configurations in a ninth embodiment of the present invention. A diagram illustrating an example of a functional configuration of a base station according to an embodiment of the present invention. A diagram illustrating an example of a functional configuration of a terminal according to an embodiment of the present invention. A diagram illustrating an example of a hardware configuration of a base station or a terminal according to an embodiment of the present invention. A diagram illustrating an example of a configuration of a vehicle according to an embodiment of the present invention.

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology may be used as appropriate. The existing technology is, for example, the existing NR or LTE, but is not limited to the existing NR or LTE. In addition, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR), unless otherwise specified.

[0012] In addition, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. In addition, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily stated as "NR-".

[0013] Furthermore, in the embodiment of the present invention, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (for example, flexible duplex, etc.).

[0014] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a base station or a terminal are set.

[0015] (System Configuration) Fig. 1 is a diagram for explaining a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0016] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. Furthermore, a transmission time interval (TTI) in the time domain may be a slot, or a subframe.

[0017] The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may also be referred to as SSB (SS / PBCH block). As shown in FIG. 1, the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to the DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may perform communication via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0018] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in FIG. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures propagation path quality based on the reception results of the reference signals. The terminal 20 may also be referred to as a UE, and the base station 10 may also be referred to as a gNB.

[0019] Next, the status of discussions on base station power saving in NR Release 18 will be described. Techniques for base stations and terminals to improve network energy saving from both the base station's transmission and reception perspectives are being considered. For example, methods are being considered for a base station to more efficiently realize dynamic and / or semi-static finer-granularity adaptation of transmission and / or reception using network energy saving techniques in one or more of the time, frequency, space, and power domains using potential support / feedback and potential assistance information from terminals.

[0020] Next, discontinuous reception (DRX) or connected mode DRX (CDRX) in a conventional terminal will be described.

[0021] 2 is a diagram for explaining CDRX in NR Release 15. In CDRX operation in NR Release 15, the terminal monitors the PDCCH during the DRX on period.

[0022] 3 is a diagram for explaining WUS in NR Release 16. In NR Release 16, a PDCCH-based wake-up signal (WUS: Wake Up Signal) can instruct one or more terminals whether the terminals should monitor the PDCCH within the next DRX-on period.

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

[0024] The WUS monitoring opportunity is set by an offset from the on-duration based on the terminal capabilities. If the WUS indicates "inactive" (i.e., the terminal is not transmitting or receiving data), the terminal can skip monitoring during the on-duration and immediately transition to sleep mode. In addition, a default terminal behavior can be configured for when the PDCCH-based WUS is not detected, for example, due to a detection error.

[0025] DCI format 2_6 includes one bit of activation indication information indicating "active" or "inactive."

[0026] (Problems with the past) Next, we will explain the problems with the past. In order to achieve carbon neutrality and the SDGs, it is becoming increasingly important to reduce the power consumption of base stations. However, there has been a problem in the past in that there is no standardized method for reducing the power consumption of base stations.

[0027] (Outline 1 of the Present Embodiment) In the present embodiment, an example of achieving a reduction in power consumption of a base station from the viewpoint of the time domain will be described. Specific examples will be described below, including Examples 1 to 4.

[0028] (First embodiment) In this embodiment, the operation of a base station when it receives intermittently and the definition of related concepts will be described.

[0029] 4 is a diagram for explaining the discontinuous reception of a base station according to Example 1 of an embodiment of the present invention. The period during which the base station 10 disables / enables the receiving unit is introduced as a discontinuous reception (gNB CDRX) function by the base station (hereinafter referred to as base station discontinuous reception).

[0030] The concept of discontinuous reception of the base station 10 is similar to that of the terminal 20. The reception units and / or parameters to be disabled may be for each port, panel, beam, or carrier (or cell).

[0031] 5 is a diagram for explaining each parameter according to Example 1 of the embodiment of the present invention. The base station CDRX may be defined by a plurality of parameters listed below. The unit of the parameters may be a symbol, a slot, a subframe, a millisecond, a second, or the like. The unit may be different or the same for each parameter. drx-onDurationTimer: the period at the start of the DRX cycle; drx-SlotOffset: the delay before starting the drx-onDurationTimer; drx-InactivityTimer: the period during which the terminal 20 performs uplink transmission after an uplink reception opportunity; drx-LongCycleStartOffset: the long DRX cycle (i.e., drx-LongCycle) and drx-StartOffset, which define when the long and short DRX cycles start; drx-ShortCycle: the short DRX cycle; drx-ShortCycleTimer: the period during which the base station 10 follows the short DRX cycle. drx-RetransmissionTimerUL: maximum period until a grant for an uplink retransmission is received; drx-HARQ-RTT-TimerUL: minimum period until a grant for an uplink retransmission is expected.

[0032] When base station discontinuous reception is enabled, the base station 10 may receive an uplink channel transmitted from the terminal 20 when drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL is executed.

[0033] If discontinuous base station reception is enabled, the terminal 20 may act in one of the following options.

[0034] <Option 1> The terminal 20 may operate assuming discontinuous reception at the base station. Specifically, the terminal 20 identifies the status of discontinuous reception at the base station by RRC, MAC-CE, or DCI. In the case of DCI, it is assumed that the terminal 20 receives DCI indicating the status of discontinuous reception at the base station from the base station 10. Details of the instruction by DCI will be described later in Example 3.

[0035] When the base station discontinuous reception is enabled, the terminal 20 may transmit an uplink channel while the drx-onDurationTimer, the drx-InactivityTimer, or the drx-RetransmissionTimerUL is running.

[0036] Option 2: The terminal 20 may ignore the DBR, specifically, the terminal 20 performs uplink transmissions as scheduled or configured by the base station 10, regardless of the DBR status.

[0037] Note that when discontinuous base station reception is enabled, the base station 10 may perform scheduling or settings that take discontinuous base station reception into consideration, or may perform scheduling or settings regardless of discontinuous base station reception. When scheduling or settings that take discontinuous base station reception into consideration are performed, the discontinuous base station reception function is realized even if the terminal 20 ignores discontinuous base station reception. Conversely, when scheduling or settings that take discontinuous base station reception into consideration are not performed, if the terminal 20 ignores discontinuous base station reception, unnecessary signal transmission occurs, resulting in wasted power consumption by the terminal 20.

[0038] On the other hand, if the base station discontinuous reception is disabled, the base station 10 may receive the uplink channel transmitted from the terminal 20 regardless of the base station discontinuous reception parameter, i.e., the base station 10 may keep the receiving unit turned on and continuously receive the uplink channel from the terminal 20.

[0039] If discontinuous base station reception is disabled, the terminal 20 may act in one of the following options.

[0040] <Option 1> The terminal 20 may operate assuming discontinuous reception at the base station. Specifically, the terminal 20 identifies the status of discontinuous reception at the base station by RRC, MAC-CE, or DCI. In the case of DCI, it is assumed that the terminal 20 receives DCI indicating the status of discontinuous reception at the base station from the base station 10. Details of the instruction by DCI will be described later in Example 3.

[0041] If discontinuous base station reception is disabled, the terminal 20 performs uplink transmissions as scheduled or configured by the base station 10 regardless of the status of discontinuous base station reception.

[0042] Option 2: The terminal 20 may ignore the DBR, specifically, the terminal 20 performs uplink transmissions as scheduled or configured by the base station 10, regardless of the DBR status.

[0043] The base station 10 may also receive terminal assistance information in order to determine the values ​​of the aforementioned parameters that define the wake-up / sleep periods.

[0044] The terminal assistance information may be a period of terminal traffic. The base station 10 may receive the terminal assistance information at a higher layer. The base station 10 determines the value of the parameter by taking into account the terminal assistance information reported by the terminal 20.

[0045] The terminal 20 may transmit terminal assistance information such as the period of terminal traffic to the base station 10 .

[0046] According to this embodiment, the base station 10 can achieve discontinuous reception.

[0047] (Embodiment 2) In this embodiment, an example of a method for triggering discontinuous reception at a base station is shown.

[0048] Enabling / disabling the base station discontinuous reception may be done by one of the following options:

[0049] <Option 1> The base station 10 may enable / disable the discontinuous reception at the base station when an RRC parameter indicating the enable / disable of the discontinuous reception at the base station is set by the terminal 20 or another network node (e.g., a core network, another base station, etc.).

[0050] <Option 2> The base station 10 may enable / disable the base station discontinuous reception when it receives a MAC-CE command indicating the enable / disable of the base station discontinuous reception from the terminal 20 or another network node (e.g., a core network or another base station).

[0051] <Option 3> When the base station 10 receives UCI included in the PUCCH or PUSCH from the terminal 20, the base station 10 may enable / disable the base station discontinuous reception based on an instruction to enable / disable the base station discontinuous reception included in the UCI.

[0052] The UCI including the instruction to enable / disable the base station discontinuous reception may be a UCI of a newly defined UCI type different from the conventional UCI. Also, the UCI may be a UCI of the same type as the conventional UCI, such as HARQ-ACK, CSI, or SR.

[0053] The terminal 20 may transmit a PUCCH or PUSCH to the base station 10 to carry out an instruction (i.e., activation / deactivation) of discontinuous reception at the base station, thereby enabling / disabling discontinuous reception at the base station.

[0054] The terminal 20 may receive DCI indicating the status of the discontinuous reception at the base station from the base station 10, in order to determine whether the instruction by the UCI has been successfully decoded by the base station 10 and whether there is a common understanding of the status of the discontinuous reception at the base station between the base station 10 and the terminal 20. Details of the DCI will be described later in Example 3.

[0055] <Option 4> The base station 10 may enable / disable the base station discontinuous reception when certain conditions are met. For example, the base station 10 may enable the base station discontinuous reception when it does not receive an uplink channel from the terminal 20 for a certain period of time. The certain period of time may be a symbol, a slot, a subframe, a millisecond, a second, or the like.

[0056] The terminal 20 may receive DCI indicating the status of discontinuous reception at the base station from the base station 10 in order to obtain a common understanding of the status of discontinuous reception at the base station between the base station 10 and the terminal 20. Details of the DCI will be described later in Example 3.

[0057] <Option 5> The base station 10 may enable / disable the base station discontinuous reception by a combination of the above options.

[0058] Furthermore, the base station 10 may perform one of the following optional operations as a procedure for enabling / disabling the base station discontinuous reception.

[0059] <Option 1> The base station 10 may immediately enable / disable the discontinuous reception at the base station when any of the above-described options that trigger the enablement / disablement of the discontinuous reception at the base station is executed.

[0060] <Option 2> The base station 10 may receive an instruction on the timing of enabling / disabling the discontinuous reception at the base station at a fixed time interval after receiving the instruction, or at a specified time. The time interval or time may be specified in units of symbols, slots, subframes, milliseconds, seconds, etc. In other words, the base station 10 may enable / disable the discontinuous reception at the base station at a specified time when one of the above-mentioned options that triggers the enabling / disabling of the discontinuous reception at the base station is executed.

[0061] <Option 3> The base station 10 may enable / disable the base station discontinuous reception based on a newly introduced timer. The enable / disable timers may be the same or different. The timer unit may be symbols, slots, subframes, milliseconds, seconds, etc. The base station 10, the terminal 20, or another network node may configure the timer in RRC or specify it in MAC-CE or UCI / DCI.

[0062] That is, when any of the options that trigger the enabling / disabling of the discontinuous base station reception described above is executed, the timer is executed, and when the timer expires, the base station 10 may enable / disable the discontinuous base station reception.

[0063] The advantages of the timer are as follows: Even if the base station discontinuous reception is instructed to be enabled, there are cases where actual uplink transmission from the terminal 20 occurs with a certain delay after the instruction due to processing by the terminal 20, etc. Even in such cases, by introducing a timer, the base station discontinuous reception can be enabled after a certain time, thereby reducing the power consumption of the base station 10.

[0064] Furthermore, even if the discontinuous reception from the base station is instructed to be disabled, actual uplink transmission from the terminal 20 may continue to occur for a while after the instruction due to processing by the terminal 20. Even in such cases, by introducing a timer, the discontinuous reception from the base station can be disabled after a certain period of time, thereby improving the performance of the terminal 20.

[0065] According to this embodiment, it is possible to realize a trigger for base station discontinuous reception, and also to realize an operation for enabling / disabling the reception when the trigger is established.

[0066] Third Embodiment In this embodiment, an example will be described in which a terminal receives an instruction regarding discontinuous reception at a base station by DCI.

[0067] If the terminal 20 identifies the status of discontinuous reception at the base station and the terminal 20 and the base station 10 have a common understanding of the status, it is necessary to consider a mechanism for indicating the status of discontinuous reception at the base station from the base station 10 to the terminal 20. For timely indication, indication by DCI is promising.

[0068] It should be noted that the advantage of having a common understanding is that when base station discontinuous reception is enabled, the terminal 20 can stop uplink transmission, thereby saving power consumption of the terminal 20.

[0069] A new RNTI may be introduced to indicate the status of the base station discontinuous reception. The new RNTI may be, for example, the gNB CDRX-RNTI (GC-RNTI).

[0070] Also, the introduction of the DCI field may be one of the following options:

[0071] <Option 1> A new DCI field may be introduced to indicate the status of the base station discontinuous reception. The bit size of the introduced DCI field may be 1 bit, with a valid state indicated by "1" and an invalid state indicated by "0". The reverse may also be possible.

[0072] <Option 2> A new DCI field does not need to be introduced. That is, the status of the base station discontinuous reception may be indicated by an existing field. For example, if the corresponding DCI format is scrambled with a new RNTI such as a GC-RNTI and the HPN and RV fields are all set to "0", the terminal 20 may identify that the status of the base station discontinuous reception is enabled.

[0073] Also, for example, if the corresponding DCI format is scrambled with a new RNTI such as a GC-RNTI, the HPN and RV fields are all set to "0", and the MCS field is all set to "1", the terminal 20 may identify that the status of base station discontinuous reception is disabled.

[0074] Also, the corresponding DCI format may be one of the following options:

[0075] <Option 1> The DCI may be unique to the terminal 20.

[0076] <Option 1-1> The base station 10 may indicate the status of base station discontinuous reception using a new DCI format that is different from the conventional format.

[0077] <Option 1-2> The base station 10 may indicate the status of base station discontinuous reception using conventional DCI formats 0_1, 0_2, 1_1, 1_2 or other DCI formats.

[0078] <Option 2> The DCI may be common to the group of terminals 20.

[0079] <Option 2-1> The base station 10 may indicate the status of the base station discontinuous reception using a new DCI format different from the conventional one. The above-mentioned new DCI field may be introduced in the new DCI format together with other new DCI fields for the power saving technology of the base station 10. The base station 10 may scramble the new DCI format with the above-mentioned new RNTI (e.g., GC-RNTI).

[0080] <Option 2-2> The base station 10 may indicate the status of base station discontinuous reception using the conventional DCI format 2_6 or another group-common DCI format.

[0081] Assuming that DCI format 2_6 is used, the conventional DCI fields of the DCI format may be reinterpreted to indicate the status of the base station discontinuous reception. For example, the "wake-up indication" may be reinterpreted. A valid state may be indicated by "1" and an invalid state by "0", or vice versa.

[0082] For differentiation, the base station 10 may scramble the DCI format 2_6 with the new RNTI (such as GC-RNTI) described above instead of the PS-RNTI.

[0083] According to this embodiment, the terminal 20 can identify the status of the base station discontinuous reception, and the terminal 20 and the base station 10 can understand it in common.

[0084] Fourth Embodiment In this embodiment, an example will be described in which base stations and terminals mutually report capability information relating to base station discontinuous reception.

[0085] The following capability information may be introduced:

[0086] Base station capability information indicating the capabilities of the base station 10 may be introduced. That is, the base station 10 transmits the base station capability information to the terminal 20 or other network nodes. The terminal 20 or other network nodes that receive the base station capability information may assume the capabilities of the base station 10 based on the received base station capability information.

[0087] The base station capability information may include information indicating whether the base station supports discontinuous reception. Also, the base station capability information may be introduced to indicate whether a DCI indication indicating the status of discontinuous reception is supported.

[0088] The following terminal capability information may also be introduced. For example, terminal capability information indicating whether or not the base station discontinuous reception is supported may be introduced. Furthermore, terminal capability information indicating whether or not the base station discontinuous reception status identification may be introduced.

[0089] When the terminal 20 has a terminal capability that supports identifying the status of the discontinuous reception from the base station, the terminal 20 may identify whether the discontinuous reception from the base station function is enabled or disabled. For example, the terminal 20 may perform the operation of Option 1 described in the first embodiment. Furthermore, when the terminal 20 does not have a terminal capability that supports identifying the status of the discontinuous reception from the base station, the terminal 20 may perform the operation of Option 2 described in the first embodiment.

[0090] In addition, terminal capability information indicating whether or not a DCI indication indicating the status of discontinuous reception at a base station is supported may be introduced. In addition, terminal capability information indicating whether or not a new terminal-specific / group-common DCI format is supported may be introduced.

[0091] The dependency between the base station capability information and the terminal capability information may be one of the following options:

[0092] <Option 1> To apply the base station discontinuous reception, it may be necessary to report both the base station capability information and the terminal capability information indicating that the base station discontinuous reception is supported.

[0093] <Option 2> To apply the base station discontinuous reception, it may be sufficient to report only either the base station capability information or the terminal capability information indicating that the base station discontinuous reception is supported.

[0094] According to this embodiment, the base station and the terminal can mutually report capability information regarding the base station discontinuous reception.

[0095] The terminal capabilities in the above-described embodiments may be limited to cases where the terminal 20 is a reduced-function terminal, or may be applied to cases where the terminal 20 is not a reduced-function terminal.

[0096] (Outline 2 of the present embodiment) Furthermore, cell DTX / DRX is being considered to reduce power consumption in the base station 10. For example, alignment of cell DTX / DRX with UE-DRX in RRC connected mode, information exchange between nodes regarding cell DTX / DRX, etc. are being considered. Note that cell DTX / DRX may be replaced with cell DTX and cell DRX, or may be replaced with cell DTX or cell DRX.

[0097] The mechanism for enabling or disabling the transceiver units of the base station 10 is important to reduce the power consumption in the base station 10. To reduce the power consumption in the base station 10, adaptation of DL transmission and UL reception has been considered.

[0098] Cell DTX / DRX is useful for achieving adaptation of DL transmission and UL reception. However, the details of the operation of cell DTX / DRX have not been clear. Therefore, hereinafter, examples 5 to 8 will be described as specific examples of cell DTX / DRX.

[0099] (Example 5) In Example 5, a definition of cell DTX / DRX will be described. Cell DRX may be defined as in Examples 1 to 4 above. Whether cell DRX is performed is determined by higher layer parameters, and a period, a start slot, an offset, and a duration may be set. Furthermore, whether cell DRX is applicable may be determined based on a semi-static, dynamic, or flexible network state.

[0100] Cell DTX may be defined as described below. Whether cell DTX is performed is determined by higher layer parameters, and the period, start slot, offset, and duration may be configured. Furthermore, whether cell DTX is applicable may be determined by semi-static, dynamic, or flexible network conditions.

[0101] <Option 1> Fig. 6 is a diagram for explaining discontinuous transmission of a base station according to Example 5 of an embodiment of the present invention. As shown in Fig. 6, a period during which the base station 10 disables or enables its own transmission unit may be introduced as cell DTX.

[0102] The transmission units and / or parameters to be disabled may be per port, per panel, per beam, per carrier, or per cell. Cell DTX may be defined by some or all of the parameters listed in 1)-6) below. The units of the parameters may be symbols, slots, subframes, milliseconds, seconds, etc., or other units. The units of the parameters may be the same or different.

[0103] 1) dtx-onDurationTimer: A period from the beginning of the DTX cycle. 2) dtx-SlotOffset: A delay period before starting dtx-onDurationTimer. 3) dtx-InactivityTimer: A period that starts after a DL transmission opportunity (an opportunity for the base station 10 to perform DL transmission and for the terminal 20 to receive DL transmission). 4) dtx-LongCycleStartOffset: dtx-StartOffset that defines the long DTX cycle (i.e., dtx-LongCycle) and the start of the long and short DTX cycles. 5) dtx-ShortCycle: A short DTX cycle. This may be optional. 6) dtx-ShortCycleTimer: A period during which the base station 10 performs a short DTX cycle. When DL reception occurs during long DTX, short DTX is started. This may be optional.

[0104] 7 is a diagram for explaining each parameter according to Example 5 of an embodiment of the present invention. As shown in FIG. 7, from the beginning of dtx-LongCycle, the active time is dtx-onDurationTimer after dtx-SlotOffset. If DL reception occurs during drx-LonCycle, the active time ends after dtx-InactivityTimer from the point at which DL reception occurred, and dtx-ShortCycle starts. If DL reception occurs during dtx-ShortCycleTimer, dtx-ShortCycle continues. If DL reception does not occur during dtx-ShortCycleTimer, dtx-LongCycle starts.

[0105] When cell DTX is enabled, the base station 10 may transmit a DL channel or a DL signal while the dtx-onDurationTimer or the dtx-InactivityTimer is running. As an operation of the terminal 20, when cell DTX is enabled, the terminal 20 may receive a DL channel or a DL signal while the dtx-onDurationTimer or the dtx-InactivityTimer is running. The terminal 20 may assume that it receives a DL channel or a DL signal when the dtx-onDurationTimer or the dtx-InactivityTimer is not running.

[0106] When cell DTX is disabled, the terminal 20 may assume that it receives DL channels or DL ​​signals as notified or configured by the base station 10 .

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

[0108] The UL channel or UL signal may be any of PRACH, PUCCH, PUSCH, CG-PUSCH, SRS, PT-RS, and DM-RS.

[0109] Sixth Embodiment In a sixth embodiment, the setting of cell DTX / DRX will be described.

[0110] <Option 1> Joint configuration may be performed. Cell DTX and cell DRX may be jointly configured using common parameters. When the common parameters (e.g., CellDTXDRX-Config) are configured, cell DTX and DRX may be enabled. The terminal 20 may appropriately perform the operation of Example 5.

[0111] The common parameters may include either or both of the information elements 1) and 2) shown below.

[0112] 1) Parameters common to DTX and DRX. Some parameters may be common to DTX and DRX. For example, a parameter indicating an on-duration timer may be common to DTX and DRX. For example, a parameter indicating a cycle may be common to DTX and DRX.

[0113] 2) Parameters Separated for DTX and DRX: Some parameters may be set separately for DTX and DRX. For example, a parameter indicating a slot offset may be set separately for DTX and DRX.

[0114] Option 1 allows for a reduction in RRC signaling overhead.

[0115] <Option 2> Separate configurations may be performed. Cell DTX and cell DRX may be configured individually using separate parameters. When a parameter for DTX (e.g., CellDTX-Config) is configured, cell DTX may be enabled. When a parameter for DRX (e.g., CellDRX-Config) is configured, cell DRX may be enabled. The parameters for DTX may include the parameters described in Example 5. The parameters for DRX may include the parameters described in Example 1.

[0116] Option 2 provides more flexibility in configuration when enabling either cell DTX or cell DRX.

[0117] Example 7 In Example 7, enabling or disabling of cell DTX / DRX is described. When cell DTX and cell DRX are jointly configured (option 1 in Example 6), cell DTX and cell DRX may be enabled or disabled as follows:

[0118] <Option 1> Cell DTX and cell DRX may be enabled or disabled by RRC signaling. When an RRC parameter is configured, cell DTX and cell DRX may be enabled or disabled. For example, the RRC parameter may be the common parameter (e.g., CellDTXDRX-Config) in Example 6.

[0119] <Option 2> Cell DTX and cell DRX may be enabled or disabled by MAC-CE When the terminal 20 receives MAC-CE, cell DTX and cell DRX may be enabled or disabled.

[0120] <Option 3> Cell DTX and cell DRX may be enabled or disabled by DCI. The terminal 20 may be dynamically notified by DCI that cell DTX and cell DRX have been enabled or disabled. The notification by DCI may be performed as shown in 1) to 4) below.

[0121] 1) The DCI format may be a UE-specific DCI format or a group-common DCI format.

[0122] 2) The DCI format may be an existing format (e.g., DCI formats 1_1, 1_2, 2_0) or may be newly defined (e.g., 1_x, 2_x).

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

[0124] 4) The DCI fields may be a set of existing fields and / or a new set of fields. For example, if it is a set of existing fields, some fields may be used to enable or disable cell DTX and cell DRX, as shown in Alt. 1) and Alt. 2) below.

[0125] Alt. 1) When scrambling is performed by an existing RNTI such as a CS-RNTI, and for example, when HPN is set to all "0", RV is set to all "00", and TDRA is set to all "1", the terminal 20 may dynamically enable cell DTX and cell DRX. Also, for example, when HPN is set to all "0", RV is set to all "00", MCS is set to all "1", FDRA is set to all "1", and TDRA is set to all "1", the terminal 20 may dynamically disable cell DTX and cell DRX.

[0126] Alt. 2) When scrambling with a new RNTI and, for example, when HPN is set to all "0"s and RV is set to all "00", the terminal 20 may dynamically enable cell DTX and cell DRX. Also, when, for example, HPN is set to all "0", RV is set to all "00", MCS is set to all "1", and FDRA is set to all "1", the terminal 20 may dynamically disable cell DTX and cell DRX.

[0127] For example, in the case of a new DCI field, cell DTX and cell DRX may be enabled or disabled by the new DCI field. The new DCI field may be referred to as a "cell DTX DRX identifier." For example, if the cell DTX DRX identifier is set to "1," the terminal 20 may dynamically enable cell DTX and cell DRX. Also, for example, if the cell DTX DRX identifier is set to "0," the terminal 20 may dynamically disable cell DTX and cell DRX. Note that the DCI including the new DCI field may be scrambled with either an existing RNTI or a new RNTI.

[0128] Also, when cell DTX and cell DRX are configured separately (option 2 in Example 6), cell DTX and cell DRX may be enabled or disabled as follows.

[0129] <Option 1> Cell DTX or cell DRX may be enabled or disabled by RRC signaling. When an RRC parameter is configured, cell DTX or cell DRX may be enabled or disabled. For example, the RRC parameter may be the separate parameter (e.g., CellDTX-Config, CellDRX-Config) in Example 6.

[0130] <Option 2> Cell DTX or cell DRX may be enabled or disabled by MAC-CE When the terminal 20 receives MAC-CE, cell DTX or cell DRX may be enabled or disabled.

[0131] <Option 3> The terminal 20 may be dynamically notified by a DCI that cell DTX or cell DRX has been enabled or disabled. The notification by the DCI may be performed as shown in 1) to 4) below.

[0132] 1) The DCI format may be a UE-specific DCI format or a group-common DCI format.

[0133] 2) The DCI format may be an existing format (e.g., DCI formats 1_1, 1_2, 2_0) or may be newly defined (e.g., 1_x, 2_x).

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

[0135] 4) The DCI fields may be a set of existing fields and / or a new set of fields. For example, a different set of DCI fields may be used to enable or disable cell DTX or cell DRX, respectively, to indicate either cell DTX or cell DRX. For example, in the case of an existing set of fields, some fields may be used to enable or disable cell DTX and cell DRX, as shown in Alt. 1) and Alt. 2) below.

[0136] Alt. 1) When scrambling is performed by an existing RNTI such as a CS-RNTI, and, for example, when the HPN is set to all "0", the RV is set to all "00", and the PRI is set to all "1", the terminal 20 may dynamically enable cell DTX. Also, for example, when the HPN is set to all "0", the RV is set to all "00", the MCS is set to all "1", the FDRA is set to all "1", and the PRI is set to all "1", the terminal 20 may dynamically disable cell DTX. Also, for example, when the HPN is set to all "0", the RV is set to all "00", and the TDRA is set to all "1", the terminal 20 may dynamically enable cell DRX. Also, for example, when the HPN is set to all "0", the RV is set to all "00", the MCS is set to all "1", the FDRA is set to all "1", and the TDRA is set to all "1", the terminal 20 may dynamically disable cell DRX.

[0137] In addition, the PRI and TDRA fields may additionally be used to indicate whether the DCI to be enabled or disabled is for CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX.

[0138] Note that the same fields as those used above, such as PRI and TDRA (e.g., TDRA), may be used to indicate whether the target is CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX. When different DCI formats are used, the DCI format may indicate whether the target is cell DTX or cell DRX. For example, DCI format 0_0 may enable or disable cell DRX, and DCI format 1_0 may enable or disable cell DTX.

[0139] Alt. 2) When scrambling with a new RNTI, for example, when the HPN is set to all "0", the RV is set to all "00", and the PRI is set to all "1", the terminal 20 may dynamically enable cell DTX. For example, when the HPN is set to all "0", the RV is set to all "00", the MCS is set to all "1", the FDRA is set to all "1", and the PRI is set to all "1", the terminal 20 may dynamically disable cell DTX. For example, when the HPN is set to all "0" and the RV is set to all "00", the terminal 20 may dynamically enable cell DRX. For example, when the HPN is set to all "0", the RV is set to all "00", the MCS is set to all "1", and the FDRA is set to all "1", the terminal 20 may dynamically disable cell DRX.

[0140] Note that, for example, although PRI is used as described above, an additional field may not be used to indicate whether cell DTX or cell DRX is targeted. When different DCI formats are used, the DCI format may signal whether cell DTX or cell DRX is targeted. For example, DCI format 0_0 may enable or disable cell DRX, and DCI format 1_0 may enable or disable cell DTX.

[0141] For example, in the case of a new DCI field, the new DCI field may enable or disable cell DTX or cell DRX, and the new DCI field may be called a "Cell DTX identifier" or a "Cell DRX identifier."

[0142] When the cell DTX and the cell DRX are notified separately in separate fields, for example, if the cell DTX identifier is set to "1", the terminal 20 may dynamically enable the cell DTX. Also, for example, if the cell DTX identifier is set to "0", the terminal 20 may dynamically disable the cell DTX. For example, if the cell DRX identifier is set to "1", the terminal 20 may dynamically enable the cell DRX. Also, for example, if the cell DRX identifier is set to "0", the terminal 20 may dynamically disable the cell DRX.

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

[0144] It should be noted that the DCI including the new DCI field may be scrambled with either the existing RNTI or the new RNTI.

[0145] The timing for applying the enabling or disabling of cell DTX or cell DRX notified by MAC-CE or DCI described above may be 1) or 2) shown below.

[0146] 1) The terminal 20 may immediately activate or deactivate the cell DTX or cell DRX. When activation or deactivation of the cell DTX or cell DRX is notified by MAC-CE or DCI, the terminal 20 may immediately activate or deactivate the cell DTX or cell DRX.

[0147] 2) The terminal 20 may activate or deactivate the cell DTX or cell DRX at the notified time. The time to activate or deactivate the cell DTX or cell DRX may be notified via RRC signaling, MAC-CE, or DCI as an interval or a certain time from the time when the activation or deactivation is notified. The unit of time may be a symbol, a slot, a subframe, a millisecond, a second, or the like. When the activation or deactivation of the cell DTX or cell DRX is notified by MAC-CE or DCI, the terminal 20 may activate or deactivate the cell DTX or cell DRX at the notified time in advance.

[0148] Example 8 In Example 8, a related operation between cell DTX / DRX and UE DRX will be described. If the time positions of cell DTX and UE DRX are not aligned, the terminal 20 may wake up to receive a DL channel or DL ​​signal when no DL transmission is being performed due to cell DTX.

[0149] Therefore, it may operate as shown in Option 1 to Option 5 below.

[0150] <Option 1> When UE DRX is configured (for example, DRX-Config), the terminal 20 does not have to assume that cell DTX is configured.

[0151] <Option 2> When cell DTX is configured, the terminal 20 does not need to assume that UE DRX (e.g., DRX-Config) is configured. Note that the parameters of cell DTX may be the parameters described in Example 6.

[0152] <Option 3> When UE DRX is configured (e.g., DRX-Config), the terminal 20 does not need to assume that cell DTX, whose time position does not match that of the UE DRX, is configured. If the time positions of the cell DTX and the UE DRX are aligned, the cell DTX and the UE DRX may be configured jointly.

[0153] <Option 4> When cell DTX is configured, the terminal 20 does not need to assume that UE DRX (e.g., DRX-Config) that is not time-aligned with the cell DTX is configured. If the cell DTX and UE DRX are time-aligned, the cell DTX and UE DRX may be configured jointly.

[0154] <Option 5> Cell DTX and UE DRX may be configured in the terminal 20 regardless of whether the time positions of the cell DTX and the UE DRX are aligned or not. Furthermore, when the cell DTX is configured in addition to the UE DRX, the parameters of the cell DTX may take priority. The terminal 20 may ignore the parameters of the UE DRX. The terminal 20 may operate as in Example 5. Furthermore, when the cell DTX is configured in addition to the UE DRX, both parameters may be applied. The terminal 20 may wake up during the active times of both the cell DTX and the cell DRX.

[0155] The above "cell DTX and UE DRX are time aligned" may be defined as option 1 or option 2 shown below.

[0156] <Option 1> If the long cycle is the same for cell DTX and UE DRX, the cell DTX and UE DRX may be defined as being aligned in time.

[0157] <Option 1-1> Furthermore, when the long cycle is the same for cell DTX and UE DRX, it may be defined that the time positions of cell DTX and UE DRX are aligned regardless of the active time within the long cycle. In other words, 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 may be defined that the time positions are aligned.

[0158] <Option 1-2> If the long cycle is the same for the cell DTX and the UE DRX, the cell DTX and the UE DRX may be further defined as being time-aligned depending on the active time within the long cycle. If the on-duration timers and slot offsets in the long cycle (e.g., dtx-LongCycle, drx-LongCycle, dtx-onDurationTimer, drx-onDurationTimer, dtx-SlotOffset, drx-SlotOffset) are the same for the cell DTX and the UE DRX, the cell DTX and the UE DRX may be defined as being time-aligned. Furthermore, other parameters (e.g., dtx-InactivityTimer, drx-InactivityTimer, etc.) may be additionally considered to determine whether this definition is met.

[0159] <Option 2> In addition to the long cycle, if the short cycle is the same for the cell DTX and the UE DRX, it may be defined that the cell DTX and the UE DRX are time-aligned. Option 2 may be applied when the conditions of Option 1-1 or Option 1-2 are met.

[0160] <Option 2-1> Furthermore, when the short cycle is the same for cell DTX and UE DRX, the time positions of cell DTX and UE DRX may be defined as being aligned regardless of the active time within the short cycle. In other words, when the short cycle of cell DTX (e.g., dtx-ShortCycle) and the short cycle of UE DRX (e.g., drx-ShortCycle) are the same, the time positions may be defined as being aligned.

[0161] <Option 2-2> If the short cycle is the same for cell DTX and UE DRX, the cell DTX and UE DRX may be defined as being time-aligned depending on the active time within the short cycle. If the short cycle timers and short cycles (e.g., dtx-ShortCycleTimer, drx-ShortCycleTimer, dtx-ShortCycle, drx-ShortCycle) are the same for cell DTX and UE DRX, the cell DTX and UE DRX may be defined as being time-aligned.

[0162] (Outline 3 of this embodiment) (Example 9) In order to achieve NES (Network energy savings), it is being considered to extend the adaptation of PRACH in the time domain and the spatial domain, for example, to set non-uniform PRACH resources per SSB.

[0163] 8 is a diagram showing an example of a PRACH format according to Example 9 of the present invention. In NR, as shown in FIG. 8, PRACH formats 0, 1, 2, 3, A1, A2, A3, B1, B2, B3, B4, C0, and C2 are defined (see Non-Patent Document 3).

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

[0165] Formats A1, A2, A3, B1, B2, B3, B4, C0, and C2 are supported in FR1 (Frequency Range 1) with 15 or 30 kHz SCS and FR2 (Frequency Range 2) with 60 or 120 kHz SCS. The frequency domain of formats A1, A2, A3, B1, B2, B3, B4, C0, and C2 is 15 or 30 kHz for FR1 and 60 or 120 kHz for FR2. In 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.

[0166] 9 is a diagram illustrating an example of PRACH resources in the time domain according to Example 9 of the embodiment of the present invention. The time domain of the PRACH is determined based on the parameter prach-ConfigurationIndex (Non-Patent Document 3). FIG. 9 illustrates an example in which prach-ConfigurationIndex is 103 in FR1. As shown in FIG. 9, when prach-ConfigurationIndex is 103, the preamble format is A1,n ＳＦＮ mod x=y where x=1, y=0, subframe numbers are 2 and 7, start symbol is 0, number of PRACH slots in a subframe is 2, number of PRACH opportunities in a PRACH slot is 6, PRACH period is 2.

[0167] 10 is a diagram illustrating an example of PRACH resources in the frequency domain according to Example 9 of the embodiment of the present invention. The frequency domain of the PRACH is determined based on the parameter msg1-FDM={1, 2, 3, 4}. The example shown in FIG. 10 is for the case where msg1-FDM=4.

[0168] The association of SS / PBCH blocks (hereinafter also referred to as "SSBs") and PRACH is indicated by N and R, which are 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 one PRACH opportunity (hereinafter also referred to as "PRACH occasion", "RACH occasion", or "RO"). R is the number of contention-based preambles per SSB per enabled RO.

[0169] SSBs are mapped to valid ROs in the following order (see Non-Patent Document 5): 1) ascending order of preamble index within a single RO; 2) ascending order of frequency direction resource index of frequency division multiplexed ROs; 3) ascending order of time direction resource index of time division multiplexed ROs within a PRACH slot; and 4) ascending order of PRACH slot index.

[0170] 11 is a diagram illustrating an example of association between SSBs and PRACH resources according to a ninth embodiment of the present invention. In FIG. 11, an example is shown in which msg1-FDM=two, ssb-perRACH-OccasionAndCB-PreamblesPerSSB=oneHalf{n20}, i.e., N=½, and R=20. Therefore, each SSB shown in FIG. 11 is associated with a preamble index {0, 1, 2, ..., R-1}, and two ROs are associated with each SSB.

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

[0172] In the legacy procedure, the SIB is updated as follows:

[0173] The SIB can be updated every modification period, which is defined as 2, 4, 8 or 16 times the paging cycle by the information element modificationPeriodCoeff signaled by SIB1. When SFN mod modification period = 0, SIB1 is modifiable.

[0174] Whether the SIBs will be updated in the next modification period is transmitted by a short message at the paging occasion. If the bit field of systemInfoModification in the short message is 1, BCCH changes other than SIB6, SIB7 and SIB8 are notified.

[0175] 12 is a diagram showing an example of modification of SIB1 according to Example 9 of the embodiment of the present invention. When SFN mod 2=0, SIB1 is modified. Note that the MIB does not need to be modified.

[0176] The base station needs to monitor PRACH transmissions from the UE in each RO. From the NES perspective, when the traffic load is very low, frequent wake-ups and long PRACH monitoring times reduce the deep sleep time of the base station and increase the base station's power consumption. On the other hand, adapting the PRACH settings, such as the periodicity, can reduce the base station's power consumption.

[0177] Therefore, the following operations 1) to 4) may be performed.

[0178] Operation 1) Extending PRACH in terms of time domain: To reduce the RO monitoring time and reduce the wake-up of the base station for PRACH monitoring, continuous RO may be configured and the RO period may be lengthened.

[0179] Operation 2) Expand the PRACH in terms of the spatial domain. Currently, the number of PRACH preambles associated with each SSB is the same. However, in actual deployment, it is assumed that the number of UEs in different SSB beam areas is different. Therefore, it is assumed that the number of preambles required for each SSB is different. Therefore, non-uniform mapping of PRACH resources for each SSB may be performed.

[0180] Operation 3) When traffic changes, PRACH requirements also change. This requires a rapid adaptation of the PRACH configuration, such as the periodicity, FDM setting, and association of SSB and PRACH resources. For example, the PRACH configuration may be adapted by DCI.

[0181] Action 4) The UE action according to action 3) may be performed.

[0182] Operation 1) will be explained below.

[0183] 13 is a diagram illustrating an example of PRACH resources according to a ninth embodiment of the present invention. As shown in FIG. 13, the number of ROs that are frequency-division multiplexed may be increased. The UE may decide to use any of the frequency-division multiplexed ROs.

[0184] A new value may be introduced for the number of ROs frequency-division multiplexed into one RO. The new value may be different from or larger than the current specification. In the current specification, the number of frequency-division multiplexed ROs supported is {1, 2, 4, 8}. A different value may be supported, for example, the number of frequency-division multiplexed ROs may be {1, 2, 4, 6, 8}.

[0185] Larger values ​​for the number of frequency division multiplexed ROs may be supported. The maximum value may be, for example, 10, 12, 14, 16, 20, 24, or 32. For example, if the maximum value is 12, {1, 2, 4, 8, 12} may be supported. For example, if the maximum value is 16, {1, 2, 4, 8, 12, 16} may be supported. For example, if the maximum value is 24, {1, 2, 4, 8, 12, 16, 20, 24} may be supported. For example, if the maximum value is 32, {1, 2, 4, 8, 12, 16, 24, 32} may be supported.

[0186] By the above operation 1-1), it is possible to reduce the PRACH monitoring time for the same number of ROs.

[0187] Operation 1-2) Figure 14 is a diagram illustrating an example of PRACH resources according to Example 9 of the present invention. The location of the RO time domain is determined by a parameter such as prach-ConfigurationIndex. One of the entries in the random access configuration table (see Table 6.3.3.2-2 / 3 / 4 in Non-Patent Document 3) is specified by this parameter. However, the RO time domains in some entries are not contiguous. Therefore, a new entry may be introduced to make the RO time domains contiguous. The UE may decide to use one of the ROs.

[0188] Note that ROs that are continuous in the time domain refer to ROs that have no gap between adjacent ROs or that have a gap of a certain period or less. The certain period may be X symbols, X subframes, X slots, or X ms. For example, when the gap is 7 OFDM symbols or less, adjacent ROs may be considered to be continuous.

[0189] Operation 1-2-1) A random access setting entry may be introduced that allows one or more combinations of the following Alts:

[0190] Alt. 1) Continuous RO may be implemented between adjacent PRACH periods. To achieve continuous RO, adjacent PRACH periods may use different frame offsets y, subframe numbers, and some or all of the starting symbols. For example, two sets of frame offsets y, subframe numbers, and some or all of the starting symbols may be configured. For example, an odd index may correspond to one set of frame offsets y, subframe numbers, and some or all of the starting symbols. For example, an even index may correspond to another set of frame offsets y, subframe numbers, and some or all of the starting symbols.

[0191] Alt. 2) Continuous RO may be implemented between adjacent subframes within one PRACH period. To achieve continuous RO, adjacent subframes may use different frame offsets y, subframe numbers, and starting symbols, in part or in whole. When a 30- or 120-kHz SCS is configured for the PRACH, two PRACH slots exist within a subframe or a 60-kHz SCS. An additional parameter (e.g., paraPRACHCont) may be configured to determine the PRACH location. For example, the additional parameter may specify whether the PRACH is configured in the first or second PRACH slot. The additional parameter may be signaled via DCI, MAC-CE, RRC signaling, or broadcast. For example, when two subframe numbers are configured for a PRACH with a 30 or 120 kHz SCS, and the row for the number of PRACH slots in a subframe or 60 kHz SCS slot is 1, if the additional parameter paraPRACHCont is set to true, the number of PRACH slots in the first subframe may be 1 and the number of PRACH slots in the second subframe may be 0. In other cases, the legacy procedure may be followed.

[0192] Alt. 3) Contiguous ROs may be introduced between adjacent PRACH slots within a subframe or slot. For PRACH format A1 in particular, the number of ROs within a certain PRACH slot may be increased to use all symbols in that PRACH slot. Furthermore, between PRACH slots within a subframe or slot, adjacent PRACH slots may use different frame offsets y, subframe numbers, and some or all of the starting symbols to achieve contiguous RO placement.

[0193] Operation 1-2-2) The selection of the random access configuration entry in the above operation 1-2-1) may be notified by a new information element.

[0194] Table 1 shows an example of a PRACH configuration.

[0195]

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

[0197] Note that for the offset y and subframe number in Table 1, if the number of PRACH periods is odd, i.e., (n ｆ / x) mod 2 is 1, use the value before the slash and set the number of PRACH periods to an even number, i.e., (n ｆ / x) mod 2 is 0, then use the value after the slash.

[0198] Figure 15 is a diagram illustrating an example of PRACH resources according to Example 9 of the embodiment of the present invention. Figure 15 shows PRACH resources when the PRACH configuration index in Table 1 is 256. As shown in Figure 15, the cycle is 8, with y = 7 and subframe number 9 used in the first cycle and y = 0 and subframe number 0 used in the second cycle. This makes adjacent PRACH resources consecutive.

[0199] Figure 16 is a diagram illustrating an example of PRACH resources according to Example 9 of an embodiment of the present invention. Figure 16 shows PRACH resources when the PRACH configuration index in Table 1 is 257. As shown in Figure 16, the cycle is 4, with y = 3 and subframe number 9 used in the first cycle and y = 0 and subframe number 0 used in the second cycle. This makes adjacent PRACH resources consecutive.

[0200] 17 is a diagram illustrating an example of PRACH resources according to Example 9 of the present invention. FIG. 17 shows PRACH resources when the PRACH configuration index in Table 1 is 283. As shown in FIG. 17, the cycle is 4, with y=3 and subframe number 9 used in the first cycle and y=0 and subframe number 0 used in the second cycle. By setting the number of ROs in the time domain per PRACH slot to 7, the OFDM symbols in the PRACH slot can be occupied by ROs. The number of ROs in the time domain per PRACH slot may also be set to 6. The PRACH formats may be applicable to A1, B1, and C0.

[0201] Table 2 shows an example of a PRACH configuration.

[0202]

[0203] PRACH configuration indexes 259-264 shown in Table 2 correspond to Alt. 1) above, and preamble format 1 or 2 is applicable.

[0204] Note that for the offset y and subframe number in Table 2, if the number of PRACH periods is odd, i.e., (n ｆ / x) mod 2 is 1, use the value before the slash and set the number of PRACH periods to an even number, i.e., (n ｆ / x) mod 2 is 0, then use the value after the slash.

[0205] Figure 18 is a diagram illustrating an example of PRACH resources according to Example 9 of an embodiment of the present invention. Figure 18 shows PRACH resources when the PRACH configuration index in Table 2 is 259. As shown in Figure 18, the cycle is 8, with y = 7 and subframe number 7 used in the first cycle and y = 0 and subframe number 0 used in the second cycle. The preamble format is format 1 with a length of 3 ms. This makes adjacent PRACH resources continuous.

[0206] Figure 19 is a diagram illustrating an example of PRACH resources according to Example 9 of an embodiment of the present invention. Figure 19 shows PRACH resources when the PRACH configuration index in Table 2 is 262. As shown in Figure 19, the cycle is 8, and the first cycle uses y = 7, subframe number 6, and start symbol 7, while the second cycle uses y = 0, subframe number 0, and start symbol 0. The preamble format is format 2 with a length of 3.5 ms. This makes adjacent PRACH resources continuous.

[0207] Table 3 shows an example of a PRACH configuration.

[0208]

[0209] PRACH configuration indexes 265-271 shown in Table 3 correspond to Alt. 2) above, and preamble formats 0, 1, 2, and 3 are applicable.

[0210] Figure 20 is a diagram illustrating an example of PRACH resources according to Example 9 of an embodiment of the present invention. Figure 20 shows PRACH resources when the PRACH configuration index in Table 3 is 268, 270, or 271. As shown in Figure 20, when the PRACH configuration index is 268, the period is 1 and subframe numbers 0, 1, 2, 3, and 4 are used. The preamble format is format 0 or 3 with a length of 1 ms.

[0211] As shown in Figure 20, when the PRACH configuration index is 270, the period is 1 and subframe numbers 0, 3, and 6 are used. The preamble format is format 0 or 3 with a length of 3 ms.

[0212] As shown in Figure 20, when the PRACH configuration index is 271, the period is 1, subframe numbers 0 and 3, and start symbols 0 and 7 are used. The preamble format is 3.5 ms long and is format 0 or 3. Note that the following combinations of (subframe number) and (start symbol) are possible: (0,4) (7,0), (1,4) (0,7), (1,5) (7,0), (2,5) (0,7), (2,6) (7,0), (3,6) (0,7).

[0213] Note that 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). Note that 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). Note that 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). Note that the subframe number (0,3) in Table 3 can be replaced with (1,4), (2,5), (3,6), or (4,7). Note that the subframe number (0,3,6) in Table 3 can be replaced with (1,4,7).

[0214] Table 4 shows an example of a PRACH configuration.

[0215]

[0216] PRACH configuration indexes 272-278 shown in Table 4 correspond to Alt. 1) and Alt. 2) above, and preamble formats 0, 1, 2, and 3 are applicable.

[0217] Note that for the offset y and subframe number in Table 4, if the number of PRACH periods is odd, i.e., (n ｆ / x) mod 2 is 1, use the value before the slash and set the number of PRACH periods to an even number, i.e., (n ｆ / x) mod 2 is 0, then use the value after the slash.

[0218] Figure 21 is a diagram illustrating an example of PRACH resources according to Example 9 of an embodiment of the present invention. Figure 21 shows PRACH resources when the PRACH configuration index in Table 4 is 272. As shown in Figure 21, the cycle is 1, subframe numbers 8 and 9 are used in the first cycle, and subframe numbers 0 and 1 are used in the second cycle. The preamble format is format 0 or 3 with a length of 1 ms.

[0219] Figure 22 is a diagram illustrating an example of PRACH resources according to Example 9 of an embodiment of the present invention. Figure 22 shows PRACH resources when the PRACH configuration index in Table 4 is 278. As shown in Figure 22, the cycle is 1, the first cycle uses subframe numbers 3 and 6 with start symbols 0 and 7, and the second cycle uses subframe numbers 0 and 3 with start symbols 0 and 7. The preamble format is format 2 with a length of 3.5 ms.

[0220] Table 5 shows an example of a PRACH configuration.

[0221]

[0222] PRACH configuration indexes 279-281 shown in Table 5 correspond to Alt. 2) and Alt. 3) above, and format A1 or a 2-symbol duration format is applicable to the preamble format. Note that the number of PRACH slots in a subframe or 60 kHz in Table 5 is 1 for the first subframe and 0 for the second subframe when the SCS is 30 or 120 kHz and the parameter paraPRACHcont is true. Note that other cases are the same as legacy.

[0223] Figure 23 is a diagram illustrating an example of PRACH resources according to Example 9 of an embodiment of the present invention. Figure 23 shows PRACH resources when the PRACH configuration index in Table 5 is 279. As shown in Figure 23, the period is 16, the subframe numbers are 4 and 5, the start symbol is 0, the number of PRACH slots in a subframe is 1, and the number of ROs in a PRACH slot is 7. The preamble format is format A1 with a length of 2 symbols.

[0224] Figure 24 is a diagram illustrating an example of PRACH resources according to Example 9 of an embodiment of the present invention. Figure 24 shows PRACH resources when the PRACH configuration index in Table 5 is 280. As shown in Figure 24, the period is 16, the subframe number is 4, the start symbol is 0, the number of PRACH slots in a subframe is 2, and the number of ROs in a PRACH slot is 7. The preamble format is format A1 with a length of 2 symbols.

[0225] Table 6 shows an example of a PRACH configuration.

[0226]

[0227] The PRACH configuration index 282 shown in Table 6 corresponds to Alt. 3) above, and the preamble format can be format A3 or formats A2, B4, or C2 with 4, 6, or 12 symbol periods.

[0228] Figure 25 is a diagram illustrating an example of PRACH resources according to Example 9 of an embodiment of the present invention. Figure 25 shows PRACH resources when the PRACH configuration index in Table 6 is 282. As shown in Figure 25, the period is 1, the subframe numbers are 3, 4, and 5, the start symbol is 0, the number of PRACH slots in a subframe is 2, and the number of ROs in a PRACH slot is 2. The preamble format is format A3 with a length of 6 symbols. Note that 12 symbols are allocated to each PRACH slot. The subframe numbers can be replaced with (1, 2, 3), (1, 2, 3, 4), or (0, 1, 2, 3, 4).

[0229] Operation 1-3) Figure 26 is a diagram illustrating an example of PRACH resources according to Example 9 of the embodiment of the present invention. As shown in Figure 26, the RO period may be increased. This reduces the number of gNB wakeups and shortens the PRACH monitoring time. The UE may decide to use one of the ROs.

[0230] Operation 1-3-1) A new random access configuration entry with a different or larger PRACH configuration period may be introduced. Hereinafter, the period value may be expressed in units of ms.

[0231] In the current specification, the PRACH configuration periodicity supported is {10, 20, 40, 80, 160}, but larger maximum periods, such as 240, 320, 480, 640, 960, and 1280, may also be supported.

[0232] If the maximum period is 320, then {0, 20, 40, 80, 160, 320} or {0, 20, 40, 80, 160, 240, 320} may be supported, and period 0 may be replaced by period 10.

[0233] If the maximum period is 480, then {0, 20, 40, 80, 160, 320, 480} or {0, 20, 40, 80, 160, 240, 320, 400, 480} may be supported. Note that period 0 may be replaced by period 10.

[0234] If the maximum period is 640, then {0, 20, 40, 80, 160, 320, 640} or {0, 20, 40, 80, 160, 240, 320, 480, 640} may be supported. Note that period 0 may be replaced by period 10.

[0235] If the maximum period is 960, then {0, 20, 40, 80, 160, 320, 640, 960} or {0, 20, 40, 80, 160, 240, 320, 480, 640, 800, 960} may be supported. Note that period 0 may be replaced by period 10.

[0236] If the maximum period is 1280, then {0, 20, 40, 80, 160, 320, 640, 1280} or {0, 20, 40, 80, 160, 240, 320, 480, 640, 960, 1280} may be supported. Note that period 0 may be replaced by period 10.

[0237] A new random access configuration entry may be introduced for the above PRACH configuration period, and the selection of the entry may be signaled by a new information element.

[0238] Operation 1-3-2) The RO association period (PRACH occasion association period) and the association period pattern corresponding to SSB may be extended.

[0239] The RO association period and association period pattern may be extended based on the new PRACH configuration period in operation 1-3-1). The RO association period may be updated based on the maximum PRACH configuration period. The association pattern period may be determined for each maximum PRACH configuration period. When the maximum PRACH configuration period is 320 ms, 480 ms, or 640 ms, the mapping between the PRACH configuration period and the SSB RO association period may be as shown in Tables 7, 8, and 9.

[0240]

[0241]

[0242]

[0243] The association period pattern includes one or more association periods, and the pattern between RO and SSB index is repeated every 320 ms, 480 ms, or 640 ms.

[0244] Table 10 shows an example of a new random access configuration entry for format 0, 1, 2 or 3.

[0245]

[0246] Note that instead of format 0, format 1, 2, or 3 may be used for the preamble. Note that instead of 32, 24, 40, 48, 64, 80, 96, or 128 may be used for the x value. 0, 1, 2, ..., x-1 may be used for the y value. 0, 1, 2, ..., 9 may be used for the subframe number, or any possible combination of multiple values ​​may be used.

[0247] Table 11 shows an example of a new random access configuration entry for formats A1, A2, A3, B1, B4, C0 or C2.

[0248]

[0249] Instead of format A1, the preamble may use other formats or a combination of formats with a length of two symbols. For example, formats A1, B1, B1, and C0 may be used. Instead of 32, the x value may be 24, 40, 48, 64, 80, 96, or 128. The y value may be 0, 1, 2, ..., or x-1. The subframe number may be 0, 1, 2, ..., 9, 10, 11, ..., or any combination of multiple possible values.

[0250] Note that a format with a length of 4 symbols may be used, and A2, A2, and B2 may be used. A format with a length of 6 symbols may be used, and A3, A3, B3, and C2 may be used. The number of PRACH slots in a subframe may be 1 or 2. Other values ​​may be used for the start symbol. The number of time domain ROs per PRACH slot is Start symbol + N ｔ ＲＡ，ｓｌｏｔ ×N ｄｕｒ ＲＡ A number satisfying <=14 may be used.

[0251] Operation 1-4) The settings of the above operations 1-1), 1-2), and 1-3) may be executed.

[0252] The above operations 1-1), 1-2), and 1-3) may be performed independently or in combination. The RO and resources of operation 1) may be different from, the same as, or overlap with the legacy RO and resources, and may be notified by the base station.

[0253] The parameters of the above operations 1-1), 1-2), and 1-3) may be notified by a new information element. Once the new information element is received, the UE may perform configuration based on the new information element and ignore legacy information elements (e.g., information elements without a suffix or information elements with a suffix other than -r19). If the new information element is not received, the UE may refer to the legacy information element.

[0254] For the above operations 1-2) and 1-3), the selection of an entry for the random access configuration may be signaled by a new information element. Multiple tables of random access configurations taking into account frequency bands and duplex modes may be defined, and different or the same information element may be used to specify entries for the tables. The number of entries for the tables may be different. When the same information element is used for the tables, the maximum value of the information element (e.g., maxEntity) may determine the maximum value across all tables. When a different information element is used for the tables, the maximum value of a new information element may be determined based on the table.

[0255] The UE may report the following as UE capabilities: The number and / or maximum number of ROs frequency-multiplexed into one RO time region in operation 1-1) The value and / or maximum value of the PRACH configuration period in operation 1-3)

[0256] Operation 1) may be applied to a contention-based 4-step RACH procedure, a contention-based 2-step RACH procedure, a contention-free 4-step RACH procedure, a contention-free 2-step RACH procedure, or other PRACH transmissions, such as a procedure in which PRACH is transmitted as a WUS (Wake-up signal).

[0257] Operation 1) may be applicable to one or more of the PRACH configurations 1)-4) below.

[0258] 1) PRACH preambles of a specific, subset, or all sequence lengths, e.g., PRACH preambles with sequence lengths of 839, 139, 571, or 1151.

[0259] 2) A specific, subset, or all PRACH formats, for example, some or all of the PRACH formats {0, 1, 2, 3, A1, A2, A3, B1, B2, B3, B4, C0, C2}.

[0260] 3) Subcarrier spacing for a specific, subset, or all PRACHs; 4) Subcarrier spacing for a specific, subset, or all PUSCHs.

[0261] Note that the PRACH configuration index (prach-ConfigurationIndex-r19, msgA-PRACH-ConfigurationIndex) may be a value from 0 to maxEntity or from 256 to maxEntity.

[0262] Action 2) Non-uniform PRACH resources per SSB may be expanded.

[0263] 27 is a diagram illustrating an example of PRACH resources per SSB according to Example 9 of the present invention. As shown in FIG. 27 , in the legacy specifications, the number of SSBs per RO, N, and the number of preambles per SSB, R, were defined. For example, ssb-perRACH-OccasionAndCB-PreamblesPerSSB was used to associate SSBs with PRACHs. The PRACH resources per SSB were uniform.

[0264] 28 is a diagram illustrating an example of PRACH resources associated with SSBs according to Example 9 of the present invention. As shown in FIG. 28, in an example of uniform PRACH resources, 64 preambles may be associated with each SSB. The base station's monitoring time will be longer. The number of PRACH resources may be configured to ensure UE access to the busiest SSB.

[0265] On the other hand, in the example of non-uniform PRACH resources, for example, 64 preambles may be associated with SSB0 and 20 preambles each with the other SSBs, thereby reducing the monitoring time of the base station.

[0266] Non-uniform PRACH resources per SSB may be introduced. For flexibility, different numbers of preambles may be associated with different SSBs. SSBs may be classified into two or more groups, and the number of preambles associated with SSBs in one group may be the same, or the number of preambles associated with SSBs in different groups may be different.

[0267] For example, to signal non-uniform PRACH resources, the legacy parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB may be partially used, or multiple groups may be used. Alternatively, the legacy parameter may not be used, and a new parameter may be used to estimate the number of preambles per SSB. A method for configuring non-uniform PRACH resources per SSB will now be described.

[0268] Operation 2-1) Different SSBs may be associated with different PRACH preamble numbers.

[0269] Operation 2-1-1) The number of PRACH preambles per SSB may be configurable.

[0270] The number of PRACH preambles per SSB may be configurable. The mapping between the number of SSBs and the number of ROs may not be configurable. The number of PRACH preambles per SSB may be selected from legacy configuration values, i.e., one of {4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64, 128, 256, 512}.

[0271] The number of PRACH preambles per SSB may be selected from the legacy settings and additional values, for example, {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}. Values ​​greater than 64 per SSB may be mapped to multiple ROs.

[0272] A new parameter may be introduced to set the number of PRACH preambles per SSB, preambleNumofSSB-r19 / msgAPreambleNumofSSB-r19, for Type 1 / Type 2 RACH procedures, respectively.

[0273] A new parameter may be introduced to configure the maximum number of PRACH preambles per RO, maxPreambleNumPerRO-r19 / msgAMaxPreambleNumPerRO-r19, for Type-1 and Type-2 RACH procedures, respectively. The values ​​of maxPreambleNumPerRO-r19 / msgAMaxPreambleNumPerRO-r19 may be less than or equal to the total number of preambles configured in the UE based on totalNumberOfRA-Preambles for Type-1 RACH procedures and msgA-TotalNumberOfRA-Preambles for Type-2 RACH procedures.

[0274] A new parameter list may specify the number of PRACH preambles for S SSBs. The new parameters, preambleNumofSSBList-r19 / msgA-preambleNumofSSBList-r19, may be introduced into the Type 1 / Type 2 RACH procedure. S may be the number of SSBs actually transmitted. For example, S may be set based on ssb-PositionsInBurst included in SIB1 or ServingCellConfigCommon. The sth entry in the list may correspond to the sth SSB actually transmitted, where s = 0, 1, ..., S-1. The maximum number of entries in the list may be 4, 8, or 64, and may be determined based on a frequency band or other parameters, or based on the SSBs actually transmitted.

[0275] For example, the following information element may be included in RACH-ConfigCommon: preambleNumofSSBList-r19 SEQUENCE (SIZE(1..maxPreambleNumofSSBList-r19)) OF preambleNumofSSB-r19 maxPreambleNumPerRO-r19 INTEGER (1..63)

[0276] Also, the following information element may be set: preambleNumofSSB-r19 ::= SEQUENCE { preambleNum ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64,n96,n128,n160,n192,n224,n256,n320,n384,n448,n512}}

[0277] For example, the following information elements may be included in RACH-ConfigCommonTwoStepRA-R16: msgA-preambleNumofSSBList-r19 SEQUENCE (SIZE(1..maxMsgAPreambleNumofSSBList-r19)) OF msgAPreambleNumofSSB-r19 OPTIONAL -- Need R msgAMaxPreambleNumPerRO-r19 INTEGER (1..63) OPTIONAL,-- Need S

[0278] Alternatively, the following information element may be set: msgAPreambleNumofSSB-r19 ::= SEQUENCE { msgAPreambleNum ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64,n96,n128,n160,n192,n224,n256,n320,n384,n448,n512}}

[0279] Operation 2-1-2) SSB may be mapped to RO and PRACH preambles.

[0280] 29 is a diagram illustrating an example of a PRACH resource associated with an SSB according to Example 9 of the present invention. As shown in FIG. 29, the number of preambles previously mapped to the SSB may be accumulated, and the SSB may be mapped to an RO in which a specific PRACH preamble is set. The following 1) and 2) may be performed.

[0281] 1) The 0th actually transmitted SSB is mapped to preamble index 0 and RO index 0. ｓ −1) / N ｔｏｔａｌ ) and preamble index (n ｓ -1) mod N ｔｏｔａｌ The 0th actually transmitted SSB is mapped until the preamble index is 1st and the RO index is 2nd.

[0282] 2) When s is 1 or more, the sth actually transmitted SSB is the RO index T ｓ－１ / N ｔｏｔａｌ and preamble index T ｓ－１ mod N ｔｏｔａｌ The RO index (T ｓ－１ +n ｓ −1) / N ｔｏｔａｌ and the preamble index (T ｓ－１ +n ｓ -1) mod N ｔｏｔａｌ The sth actually transmitted SSB is mapped until

[0283] However, n based on operation 2-2-1) ｓ is the number of PRACH preambles for the sth valid SSB. ｓ is the accumulated number of PRACH preambles mapped from the 0th SSB to the sth SSB. That is, T ｓ =Σ ｓ＝０ ｓ n ｓ It is. ｔｏｔａｌis the total number of preambles configured for the Type 1 / Type 2 RACH procedure by totalNumberOfRA-Preambles / msgA-TotalNumberOfRA-Preambles based on operation 2-1-1). Alternatively, maxPreambleNumPerRO-r19 / msgAMaxPreambleNumPerRO-r19 may be the maximum number of preambles configured for the Type 1 / Type 2 RACH procedure. The above RO index and SSB index are indexes for the association period, and the index value may exceed the number of valid SSBs due to multiple mapping.

[0284] Operation 2-2) A new parameter for grouping SSBs for association of PRACH resources with SSBs may be introduced.

[0285] Operation 2-2-1) The number of PRACH preambles per SSB may be set as follows:

[0286] The SSBs may be classified into two or more groups. Within a group, each SSB may assume the same number of preambles. Between different groups, the number of preambles associated with the SSBs may differ.

[0287] A new parameter may be introduced to set the number of PRACH preambles per SSB, preambleNumofSSB-r19 / msgAPreambleNumofSSB-r19, for Type 1 / Type 2 RACH procedures, respectively.

[0288] A new parameter may be introduced to configure the maximum number of PRACH preambles per RO, maxPreambleNumPerRO-r19 / msgAMaxPreambleNumPerRO-r19, for Type-1 and Type-2 RACH procedures, respectively. The values ​​of maxPreambleNumPerRO-r19 / msgAMaxPreambleNumPerRO-r19 may be less than or equal to the total number of preambles configured in the UE based on totalNumberOfRA-Preambles for Type-1 RACH procedures and msgA-TotalNumberOfRA-Preambles for Type-2 RACH procedures.

[0289] A new parameter may signal the SSB index of the group. The new parameters, ssbIndexofRoNumGroup-r19 and msgASSBIndexofRoNumGroup-r19, may be introduced into the Type 1 and Type 2 RACH procedures, respectively. A bitmap may be used to signal which SSB belongs to which group. The length of the bitmap may be 4, 8, or 64, and may be determined based on a frequency band or other parameters, or may be determined based on the SSBs actually transmitted. A 1 or 0 in a specific bit of the bitmap may indicate that the corresponding SSB belongs to that group. When signaling that a particular SSB belongs to multiple groups, the group may be signaled using the smallest index, the first group, or the first entry in the list.

[0290] Some or all of the above parameters for one SSB group may be signaled by new parameters, such as roNumGroup-r19 / msgARoNumGroup-r19, which may be introduced into Type 1 / Type 2 RACH procedures, respectively.

[0291] Alt. 1) For multi-group design, a new list parameter may be used to indicate the number of PRACH preambles for each SSB group. As the new list parameters, roNumGroupList-r19 / msgARoNumGroupList-r19 may be introduced into Type 1 / Type 2 RACH procedures, respectively. The supported number or maximum number of the list may be defined in the specification, configured, or signaled by the UE capabilities.

[0292] Alt. 2) For a design of two or a specific number of groups, new parameters may be introduced to indicate the number of PRACH preambles for two SSB groups, such as roNumGroup1-r19 / msgAroNumGroup1-r19 and roNumGroup2-r19 / msgAroNumGroup2-r19, for Type 1 and Type 2 RACH procedures, respectively.

[0293] Action 2-2-2) Action 2-1-2) may be applied to mapping of SSB to RO and PRACH preambles.

[0294] 30 is a diagram illustrating an example of a modification of specifications related to RACH configuration in Example 9 of an embodiment of the present invention. As shown in Fig. 30, in a Type 1 RACH procedure, maxRoNumGroupList-r19 lists roNumGroup-r19 may be configured in RACH-ConfigCommon.

[0295] 31 is a diagram illustrating an example of a modification of specifications related to RACH configuration in Example 9 of the embodiment of the present invention. As shown in Fig. 31, in a Type 1 RACH procedure, two groups, RONumGroup1 and RONumGroup2, may be configured in RACH-ConfigCommon.

[0296] Operation 2-3) When grouping SSBs for association of SSBs with PRACH resources, some legacy parameters may be used.

[0297] Operation 2-3-1) The number of PRACH preambles per SSB may be set as follows:

[0298] The SSBs may be classified into two or more groups. Within a group, each SSB may assume the same number of preambles. Between different groups, the number of preambles associated with the SSBs may differ.

[0299] A new parameter may signal the SSB index of the group. The new parameters, ssbIndexofRoNumGroup-r19 and msgASSBIndexofRoNumGroup-r19, may be introduced into the Type 1 and Type 2 RACH procedures, respectively. A bitmap may be used to signal which SSB belongs to which group. The length of the bitmap may be 4, 8, or 64, and may be determined based on a frequency band or other parameters, or may be determined based on the SSBs actually transmitted. A 1 or 0 in a specific bit of the bitmap may indicate that the corresponding SSB belongs to that group. When signaling that a particular SSB belongs to multiple groups, the group may be signaled using the smallest index, the first group, or the first entry in the list.

[0300] Some or all of the above parameters for one SSB group may be signaled by new parameters, such as roNumGroup-r19 / msgARoNumGroup-r19, which may be introduced into Type 1 / Type 2 RACH procedures, respectively.

[0301] Alt. 1) For multi-group design, a new list parameter may be used to indicate the number of PRACH preambles for each SSB group. As the new list parameters, roNumGroupList-r19 / msgARoNumGroupList-r19 may be introduced into Type 1 / Type 2 RACH procedures, respectively. The supported number or maximum number of the list may be defined in the specification, configured, or signaled by the UE capabilities.

[0302] Alt. 2) For a design of two or a specific number of groups, new parameters may be introduced to indicate the number of PRACH preambles for two SSB groups, such as roNumGroup1-r19 / msgAroNumGroup1-r19 and roNumGroup2-r19 / msgAroNumGroup2-r1, for Type 1 and Type 2 RACH procedures, respectively.

[0303] In Alt. 1) and Alt. 2), one or more of the following restrictions a) and / or b) on the configuration of the legacy parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB for the Type 1 RACH procedure / ssb-perRACH-OccasionAndCB-PreamblesPerSSB for the Type 2 RACH procedure may be applied between different groups.

[0304] a) Between different groups, the number of preambles R per RO per SSB may only be set to the same value or a certain multiple, for example, 4, 8, 16, 32 or 64 times.

[0305] b) Between different groups, the number of SSBs N per RO may only be set to the same value, adjacent values, or values ​​at three adjacent levels.

[0306] Operation 2-3-2) When mapping SSB to RO and PRACH preambles, the mapping method may be operation 2-1-2) with the following modifications.

[0307] n ｓ is n ｓ =R, (N>1), n ｓ The s-th PRACH preamble number may be calculated by the following equation: =(1 / N)×R, (N<1), s=0, 1, . . .

[0308] N ｔｏｔａｌ may be one of the following:

[0309] The total number of preambles set in the Type 1 / Type 2 RACH procedure by totalNumberOfRA-Preambles / msgA-TotalNumberOfRA-Preambles, respectively. N or n in the first group ｓ The maximum N or n of all the groups set ｓ Common N or n when b) above applies ｓ

[0310] Fig. 32 is a diagram illustrating an example of modification of specifications related to RACH configuration in Example 9 of the embodiment of the present invention. Fig. 32 shows a case where two groups are configured in a Type 1 RACH procedure, where the legacy parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is partially used to notify association of SSB and PRACH resources, and the number of SSBs per RO is limited to three adjacent levels, and the number of preambles per SSB is set to the same value.

[0311] Fig. 33 is a diagram for explaining an example of associating SSBs and ROs in Example 9 of the embodiment of the present invention. Fig. 33 shows an example of mapping SSBs and ROs to which the settings in Fig. 32 are applied. SSB #0 and SSB #1 belong to group 1, and oneEighth is set, so SSB #0 and SSB #1 are each mapped to 8ROs. SSB #2 and SSB #3 belong to group 1, and oneHalf is set, so SSB #2 and SSB #3 are each mapped to 2ROs.

[0312] Operation 2-4) Operation 2-1), operation 2-2), and operation 2-3) may be performed as follows.

[0313] Operation 2-4-1) Operation 2-1), Operation 2-2), and Operation 2-3) may be applied to a contention-based 4-step RACH procedure, a contention-based 2-step RACH procedure, a contention-free 4-step RACH procedure, a contention-free 2-step RACH procedure, or other PRACH transmission, such as a procedure in which PRACH is transmitted as a WUS (Wake-up signal).

[0314] Action 2-4-2) Action 2-1), Action 2-2), and Action 2-3) may be applicable to one or more PRACH settings 1)-4) shown below.

[0315] 1) PRACH preambles of a specific, subset, or all sequence lengths, e.g., PRACH preambles with sequence lengths of 839, 139, 571, or 1151.

[0316] 2) A specific, subset, or all PRACH formats, for example, some or all of the PRACH formats {0, 1, 2, 3, A1, A2, A3, B1, B2, B3, B4, C0, C2}.

[0317] 3) Subcarrier spacing for a specific, subset, or all PRACHs; 4) Subcarrier spacing for a specific, subset, or all PUSCHs.

[0318] Action 2-4-3) Action 2-1), Action 2-2), and Action 2-3) may be applicable to one or more of the SSB settings 1)-3) shown below.

[0319] 1) SSB in some or all of the frequency bands FR1, FR2, FR2-1 and FR3; 2) SSB in some or all of the maximum numbers 4, 8 and 64; 3) The number of SSBs actually transmitted is less than or equal to a specific value, e.g., 4, 8 or 12.

[0320] Operation 2-4-4) The mapping of PRACH resources per SSB may be switched between uniform and non-uniform. If one or more of the RRC parameters in operation 2-1), operation 2-2), and operation 2-3) are configured or present, the UE may assume that the mapping between PRACH resources and SSBs is non-uniform. That is, the UE may assume that the mapping is performed by operation 2-1), operation 2-2), and operation 2-3), and may ignore legacy parameters (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB, msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB, parameters without a suffix, and parameters with a suffix other than -r19).

[0321] On the other hand, if one or more of the RRC parameters in actions 2-1), 2-2) and 2-3) are not configured or do not exist, the UE may assume a legacy mapping of uniform PRACH resources and SSBs and perform the legacy mapping using the legacy parameters.

[0322] Operation 3) DCI for fast adaptation of adaptive PRACH configuration may be configured as follows: Note that the adaptive PRACH configuration may be the PRACH configuration according to operation 1) and / or operation 2).

[0323] Operation 3-1) The content of the notification of application of the adapted PRACH configuration may be as follows:

[0324] The following may be signaled as PRACH-related parameters: PRACH preamble format Time domain resource Frequency domain resource Root sequence PRACH-ConfigurationIndex Cyclic shift and restriction type (no restriction, restriction set A or restriction set B) PRACH opportunity index Set of PRACH opportunity indices and associated single or mask index PRACH opportunity index or set of PRACH opportunity indices associated with 1 SSB Preamble index or preamble index associated with 1 SSB or 1 RO SSB and PRACH mapping information Received signal strength threshold (e.g. RSRP of a cell in ES state) for selecting a cell or base station to wake up Received signal strength threshold (e.g. RSRP of a cell in ES state) for selecting an SSB of a cell in ES state for determining PRACH parameters Association duration index Random access Msg1 Actually transmitted SSB Other PRACH parameters introduced in operation 1) and / or operation 2)

[0325] The following may be signaled as additional parameters: - Time or time offset for applying the adaptive PRACH configuration (Operation 4-2 described later) See Alt. 3 9 - Validity period for applying the adaptive PRACH configuration

[0326] Operation 3-1-2) RRC signaling for notifying the setting of the parameters of Operation 3-1-1) may be specified. The DCI may select one or more of the setting from multiple settings.

[0327] A new information element may be introduced to notify the parameter setting of operation 3-1-1). For example, a new information element adaptPrachSetting-r19 may include one setting. For example, a new information element adaptPrachSettingList-r19 may include a list of settings. The maximum number of settings in the list may be 1, 2, 4, 8, 16, 32, or any other integer. The UE may report the maximum number of settings in the list that it supports to the base station as UE capability.

[0328] When the UE receives the above new information element relating to the parameters of operation 3-1-1) and has not yet received a DCI to select a configuration, the UE may refer to the first configuration in the list or the configuration notified in the system information.

[0329] When the UE receives a DCI notification selecting the configuration, the UE may assume that the parameters related to operation 3-1-1) are changed or not changed based on the DCI notification. When the parameters related to the configuration are changed, other parameters not included in operation 3-1-1) may not be changed, may refer to the previous configuration, or may refer to the default configuration. The default configuration may be a configuration notified by another new information element, a configuration notified by a legacy information element of the PRACH configuration, or a configuration notified by system information.

[0330] Table 12 is an example showing four settings when the new information element contains a setting list.

[0331]

[0332] FIG. 34 is a diagram for explaining a specification modification example relating to multiple RACH settings in Example 9 of the embodiment of the present invention.

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

[0334] Operation 3-2) Adaptive PRACH configuration may be signaled by DCI as follows:

[0335] Action 3-2-1) It may be notified by the existing DCI format.

[0336] Action 3-2-1-1) It may be notified by a new field in DCI format 1_0 scrambled with the P-RNTI or another RNTI.

[0337] For example, the size of a new field called a PRACH adaptation field may be determined based on the number of settings in operation 3-1-2). For example, the size of the new field is determined by ceil(log ２ M). A value of 0 may indicate setting to the top of the list in action 3-1-2). Table 13 is an example of this field.

[0338]

[0339] For example, the size of the new field is ceil(log ２ M+1). A value of 1 may indicate setting to the top of the list for action 3-1-2). Table 14 is an example of such an action.

[0340]

[0341] Whether a new field exists may be determined by a newly defined parameter. For example, it may be determined by adaptPrachSettingList-r19 in operation 3-1-2). If adaptPrachSettingList-r19 exists, the field may exist, otherwise it may not exist. For example, it may be determined by prachAdaptationConfig. If prachAdaptationConfig=true, the field may exist, otherwise it may not exist.

[0342] The position of the new field included in the DCI may be at the end, at the beginning, after a specific bit field (e.g., TRS availability indication), or after a reserved bit. A short message indicator field may be used to indicate whether a new field is included. Table 15 is an example of this operation.

[0343]

[0344] Operation 3-2-1-2) It may be notified by an existing field of DCI format 1_0 scrambled by P-RNTI or another RNTI. For example, it may be notified by the Short messages field. In the existing Short messages field, the first 4 bits are used and there are 4 reserved bits. Table 16 is an example of this operation.

[0345]

[0346] The 1-bit signaling or the 2-bit signaling shown in Table 16 may be used.

[0347] Operation 3-2-2) The adaptive PRACH configuration may be notified by a new DCI format, such as DCI format 2_x. The new DCI format is used to notify the adaptive PRACH configuration. The new DCI format includes a field for notifying the adaptive PRACH configuration. The design of the field may be the same as in operation 3-2-1-1).

[0348] Operation 3-2-3) The DCI in operation 3-2) may be scrambled with a legacy RNTI or a new RNTI. For example, the legacy RNTI may be a P-RNTI, an SI-RNTI, or a PEI-RNTI. For example, the new RNTI may be a PA-RNTI. The PA-RNTI may be common to all UEs or UE groups. UE grouping may be determined based on UE-IDs and the number of groups.

[0349] Operation 3-3) The setting of operations 3-1) and 3-2) may be performed as follows.

[0350] Operation 3-3-1) Operation 3-1) and operation 3-2) may be applied to a contention-based 4-step RACH procedure, a contention-based 2-step RACH procedure, a contention-free 4-step RACH procedure, a contention-free 2-step RACH procedure, or other PRACH transmission, such as a procedure in which PRACH is transmitted as a WUS (Wake-up signal).

[0351] Action 3-3-2) Action 3-1) and Action 3-2) may be applicable to one or more PRACH configurations 1)-4) shown below.

[0352] 1) PRACH preambles of a specific, subset, or all sequence lengths, e.g., PRACH preambles with sequence lengths of 839, 139, 571, or 1151.

[0353] 2) A specific, subset, or all PRACH formats, for example, some or all of the PRACH formats {0, 1, 2, 3, A1, A2, A3, B1, B2, B3, B4, C0, C2}.

[0354] 3) Subcarrier spacing for a specific, subset, or all PRACHs; 4) Subcarrier spacing for a specific, subset, or all PUSCHs.

[0355] Action 3-3-3) Action 3-1) and Action 3-2) may be applicable to one or more SSB settings 1)-3) shown below.

[0356] 1) SSB in some or all of the frequency bands FR1, FR2, FR2-1 and FR3; 2) SSB in some or all of the maximum numbers 4, 8 and 64; 3) The number of SSBs actually transmitted is less than or equal to a specific value, e.g., 4, 8 or 12.

[0357] Action 4) UE action for early application of adaptive PRACH configuration may be as follows.

[0358] Action 4-1) A PRACH adaptation indication (PAI) may be received in a DCI as follows:

[0359] The UE may receive the DCI of the PAI in a Paging Occasion (PO).

[0360] Alt. 1) The UE may receive the DCI for the PAI in the PO as in operation 3-2. The UE may receive the DCI for the PAI in all or some of the POs. The PO for receiving the PAI may be configured by system information, RRC signaling, or DCI. In case of multi-beam operation, the UE may assume that some PAI is repeated in all transmitted beams, or the selection of the beam for receiving the PAI may be based on the UE implementation.

[0361] Alt. 2) The UE may receive the DCI of the PAI in a Paging Early Indication Occasion (PEI-O) as in operation 3-2. The UE may receive the DCI for the PAI in all or some of the PEI-Os. The PEI-O for receiving the PAI may be configured by system information, RRC signaling, or DCI. In case of multi-beam operation, the UE may assume that some PAIs are repeated in all transmitted beams, or the selection of the beam for receiving the PAI may be based on the UE implementation.

[0362] Alt. 3) The UE may receive DCI of PAI as in operation 3-2 on newly defined occasions. For example, the UE may receive the DCI in PRACH Adaptation Indication Occasions (PAI-O). The setting of PAI-O may be notified by system information, RRC signaling, or DCI. Any of the following 1) to 3) may be configured or supported in the UE.

[0363] 1) The PAI-O setting may be the same for all UEs or may be common to all UEs. 2) The PAI-O setting may be the same within a UE group or may be common to all UEs. UE grouping may be determined based on the UE-ID and the number of groups. 3) The PAI-O setting may be different for each UE. That is, it may be set independently for each UE.

[0364] The UE may monitor multiple PAI-Os per DRX cycle.

[0365] When a PAI is transmittable, one PAI-O may be a set of PDCCH monitoring opportunities and may consist of multiple time slots (eg, subframes or OFDM symbols).

[0366] In multi-beam operation, the UE may assume that some PAIs are repeated in all transmitted beams, and the selection of the beam for receiving the PAI may be based on the UE implementation.

[0367] The number of PAI-Os per SSB is defined as X, which may be set by a parameter or may be 1 if not set.

[0368] The number S of SSBs that are actually transmitted may be determined based on the ssb-PositionsInBurst included in SIB1.

[0369] A PAI-O may be an S x X set of consecutive PDCCH monitoring opportunities. The x x S + K PDCCH monitoring opportunity for a PAI in the PAI-O may correspond to the Kth transmitted SSB, where x = 0, 1, ..., X - 1, K = 1, 2, ..., S. PDCCH monitoring opportunities for PAIs that do not overlap with UL symbols determined based on the tdd-UL-DL-ConfigurationCommon may be numbered sequentially starting at zero from the first PDCCH monitoring opportunity for a PAI in the PAI-O. When a UE detects a PAI in the PAI-O, the UE may not monitor subsequent monitoring opportunities associated with the same PAI-O.

[0370] Action 4-2) After receiving the PAI, the UE may act as follows:

[0371] Operation 4-2-1) Once the UE receives the PAI, it may start PRACH transmissions that apply adaptive PRACH configuration based on the PAI from the following timing:

[0372] Alt. 1) A PRACH transmission that applies an adaptive PRACH configuration based on the PAI may be initiated a predefined time or time offset after receiving the PAI. The time offset may be, for example, X, where X is in units of ms, s, symbols, subframes, radio frames, PRACH period, association period, or association pattern. The time may be the next or next Y, where Y is in units of ms, s, symbols, subframes, radio frames, PRACH period, association period, or association pattern.

[0373] Alt. 2) The time or time offset may be set by the SIB. It may be set or signaled by SIB1, another SIB, or a new SIB. The signaled content may be the same as Alt. 1.

[0374] Alt. 3) Time or time offset may be dynamically notified. Information on time or time offset may be notified together with adaptive PRACH configuration or by DCI in PAI in operation 3-2). The notified content may be the same as in Alt. 1.

[0375] Action 4-2-2) When the UE receives the PAI, the new adaptive PRACH configuration becomes effective from the time based on action 4-2-1), and the old PRACH configuration previously configured in the UE may be used as follows:

[0376] Alt. 1) The UE may assume that the old PRACH configuration is valid until the new PRACH configuration is applied.

[0377] Alt. 2) The UE may assume that the old PRACH configuration is valid until the start or end of, for example, Z, where Z is in ms, s, symbols, subframes, radio frames, PRACH period, association period, or association pattern, before the new PRACH configuration is applied.

[0378] Alt. 3) The UE may assume that the old PRACH configuration is invalid from the time it receives the PAI or is informed of the adaptive PRACH configuration, or that the base station will not receive PRACH transmissions with the old PRACH configuration.

[0379] Alt. 4) After receiving the PAI or being informed of the adaptive PRACH configuration, the UE may assume that the old PRACH configuration is invalid or that the base station will not receive PRACH transmissions according to the old PRACH configuration from the start or end of A, where A is in units of ms, s, symbols, subframes, radio frames, PRACH period, association period, or association pattern.

[0380] Alt. 5) The old PRACH configuration may be assumed to be valid regardless of whether the new PRACH configuration is applied, i.e., both the old and new PRACH configurations may be valid.

[0381] Action 4-2-3) Legacy System Information Update Procedure May Be Able to Change PRACH Settings After a predetermined time has elapsed since the UE received the PAI, the PRACH settings may be changed to update the system information.

[0382] Alt. 1) All parameters of the updated system information may be used and previously received PAI may be ignored.

[0383] Alt. 2) The UE may obtain parameters not signaled by the PAI from updated system information. The UE may use parameters from the most recently received PAI.

[0384] Alt. 3) The UE may ignore parameters changed by system information. Upon receiving a PAI, the UE may update the PRACH configuration based only on other PAIs.

[0385] The RO established by SIB1 and the RO established by PAI may be different, non-overlapping, partially overlapping, or the same.

[0386] The ROs set for different PAIs may be different, non-overlapping, partially overlapping, or identical.

[0387] The above X, Y, Z, and A may be integers.

[0388] Which of the above embodiments is to be used may be set by higher layer parameters, may be reported from the terminal 20 to the base station 10 as UE capabilities, may be defined by specifications, may be reported from the terminal 20 to the base station 10 as UE capabilities and set by higher layer parameters, or may be notified by DCI. A WUS (Wake up signal) for the base station may be used for cell DTX in addition to cell DRX.

[0389] In addition, a UE capability may be defined indicating whether cell DTX and cell DRX are supported, a UE capability may be defined indicating whether dynamic enabling or disabling of cell DTX and cell DRX is supported, and a UE capability may be defined indicating whether cell DTX and cell DRX with UE DRX or CDRX are supported.

[0390] Note that cell DTX / DRX may be replaced with cell DTX and / or cell DRX. Activation / deactivation may be replaced with activation and / or deactivation, activation and / or deactivation, etc.

[0391] The above-described embodiments allow the PRACH to be adapted to support NES.

[0392] That is, a technique is provided for adapting a random access channel to a base station that is transitioning to a power saving state.

[0393] (Device Configuration) Next, a functional configuration example of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. The base station 10 and the terminal 20 include functions for executing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only the proposed functions of any of the embodiments.

[0394] <Base Station 10> Fig. 35 is a diagram showing an example of the functional configuration of a base station. As shown in Fig. 35, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 35 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention. The transmitting unit 110 and the receiving unit 120 may be called a communication unit.

[0395] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of a higher layer from the received signal. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, DL data, etc. to the terminal 20. The transmitter 110 also transmits the setting information, etc., described in the embodiments.

[0396] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads out the information from the storage device as needed. The control unit 140 performs, for example, overall control of the base station 10, including control related to signal transmission and reception. Note that the functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120. The transmitting unit 110 and the receiving unit 120 may also be called a transmitter and a receiver, respectively.

[0397] <Terminal 20> Fig. 36 is a diagram showing an example of the functional configuration of a terminal. As shown in Fig. 36, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 36 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be called a communication unit.

[0398] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The transmitter 210 also transmits HARQ-ACK, and the receiver 220 receives the setting information and the like described in the embodiments.

[0399] 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 out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The control unit 240 performs overall control of the terminal 20, including control related to signal transmission and reception. Note that the function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220. The transmitting unit 210 and the receiving unit 220 may also be called a transmitter and a receiver, respectively.

[0400] The terminal or base station of this embodiment may be configured as a terminal or base station shown in each of the following items. Also, the following communication method may be implemented.

[0401] <Configuration Related to the Present Embodiment> (Item 1) A terminal comprising: a receiver that receives parameters related to PRACH (Physical Random Access Channel) configuration from a base station; a controller that determines time domain resources for PRACH opportunities based on the PRACH configuration; and a transmitter that transmits the PRACH to the base station using the resources, wherein the controller determines the resources so as to reduce the time the base station spends monitoring the PRACH. (Item 2) The terminal according to item 1, wherein the controller determines any resource among frequency-division multiplexed PRACH opportunities. (Item 3) The terminal according to item 1, wherein the controller determines any resource among PRACH opportunities that are consecutive in the time domain. (Item 4) The terminal according to item 1, wherein the controller determines any resource among PRACH opportunities having a period longer than 160 ms. (Item 5) The terminal according to item 1, wherein the controller reports to the base station the number of frequency-division multiplexable PRACH opportunities that it supports and the maximum period of the PRACH opportunities that it supports as capabilities. (Clause 6) A communication method in which a terminal executes the following procedures: receiving parameters related to PRACH (Physical Random Access Channel) configuration from a base station; determining time domain resources for PRACH opportunities based on the PRACH configuration; transmitting PRACH to the base station using the resources; and determining the resources so as to reduce the time the base station spends monitoring the PRACH.

[0402] Any of the above configurations provides a technique for adapting the random access channel to a base station transitioning to a power saving state. According to paragraphs 2 to 5, the PRACH can be adapted to correspond to the NES.

[0403] (Hardware Configuration) The block diagrams (FIGS. 35 and 36) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0404] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0405] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 37 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0406] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0407] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0408] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0409] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 35 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 36 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0410] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0411] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0412] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0413] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0414] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0415] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0416] Fig. 38 shows a configuration example of a vehicle 2001. As shown in Fig. 38, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

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

[0418] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

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

[0420] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

[0421] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

[0423] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0424] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0425] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0426] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0427] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0428] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0429] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0430] In this specification, a specific operation described as being performed by the base station 10 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0431] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0432] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0433] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0434] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0435] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0436] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0437] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0438] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0439] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0440] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0441] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0442] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

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

[0444] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0445] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0446] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0447] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0448] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0449] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0450] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

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

[0452] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0453] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0454] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0455] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0456] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, specific windowing operations performed by the transceiver in the time domain, etc.

[0457] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0458] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0459] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0460] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0461] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0462] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0463] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0464] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0465] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0466] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0467] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0468] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0469] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0470] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0471] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set for the terminal 20 within one carrier.

[0472] At least one of the configured BWPs may be active, and the terminal 20 may not expect to transmit or receive a predetermined signal / channel outside the active BWP. Note that the terms "cell," "carrier," and the like in this disclosure may be read as "BWP."

[0473] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc.

[0474] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0475] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0476] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0477] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0478] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A terminal having a receiving unit that receives parameters related to PRACH (Physical Random Access Channel) settings from a base station; a control unit that determines time domain resources for PRACH opportunities based on the PRACH settings; and a transmitting unit that transmits PRACH to the base station using the resources, wherein the control unit determines the resources so as to reduce the time that the base station monitors the PRACH.

2. The terminal according to claim 1, wherein the control unit determines a resource for one of the frequency-division multiplexed PRACH opportunities.

3. The terminal according to claim 1, wherein the control unit determines a resource for one of consecutive PRACH opportunities in the time domain.

4. The terminal according to claim 1, wherein the control unit determines a resource for any of PRACH opportunities having a period longer than 160 ms.

5. The terminal according to claim 1, wherein the control unit reports to the base station the number of PRACH opportunities that can be frequency-division multiplexed and the maximum period of the PRACH opportunities that can be supported as capabilities.

6. A communication method in which a terminal performs the following procedures: receiving parameters related to PRACH (Physical Random Access Channel) settings from a base station; determining time domain resources for PRACH opportunities based on the PRACH settings; transmitting PRACH to the base station using the resources; and determining the resources so that the base station reduces the time it spends monitoring the PRACH.

Images