Terminal, communication method, and wireless communication system

Abstract

This terminal comprises a reception unit that receives Msg4 or MsgB in a random access procedure, and a control unit that controls, after reception of the Msg4 or MsgB, reception processing for a downlink shared channel that is unicast-transmitted from a base station. When a prescribed function has been reduced from the terminal, the control unit does not perform the reception processing for the downlink shared channel scheduled for over a prescribed frequency resource.

Description

Terminal, communication method, and wireless communication system

[0001] The present invention relates to a terminal, a communication method, and 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] In LTE or NR, UE categories or UE capabilities for IoT (Internet of Things) are defined that reduce functions that are mandatory for normal terminals, such as functions related to transmission and reception bandwidth and the number of antennas. For example, in LTE, eMTC (enhanced Machine Type Communication) and NB-IoT (Narrow Band IoT) are defined, and in NR, RedCap (Reduced Capability) and the like are defined.

[0004] Furthermore, studies have begun on future systems beyond 5G, or 6G, which are expected to further improve communication performance and diversify use cases.

[0005] 3GPP TS 38.300 V17.5.0 (2023-06)3GPP TR 38.822 V17.1.0 (2023-06)3GPP TS 38.331 V17.5.0 (2023-06)

[0006] In future systems (e.g., NR Release 18 and 6G, the successor system to NR), eRedCap (enhanced Reduced Capability) is being considered, which has even fewer functions than RedCap, which is being considered in NR Release 17. For example, an eRedCap terminal may support at least one of a baseband bandwidth reduction function and a peak data rate reduction function. Here, even before a base station acquires capability information of an eRedCap terminal, it is necessary to set a channel with an appropriate bandwidth to an eRedCap terminal that supports only the peak data rate reduction function.

[0007] The present invention has been made in view of the above points, and has as its object to set a channel with an appropriate bandwidth for a terminal with reduced functionality in a wireless communication system.

[0008] According to the disclosed technology, a terminal includes a receiving unit that receives Msg4 or MsgB in a random access procedure, and a control unit that controls reception processing of a downlink shared channel that is unicast transmitted from a base station after receiving the Msg4 or MsgB, and when the terminal is a terminal with a reduced predetermined function, the control unit does not perform reception processing of the downlink shared channel that is scheduled beyond a predetermined frequency resource.

[0009] According to the disclosed technology, in a wireless communication system, a channel with an appropriate bandwidth can be set for a terminal with reduced functionality.

[0010] 1 is a diagram illustrating an example of the configuration of a wireless communication system. FIG. 1 is a sequence diagram illustrating an example of an operation in which a four-step random access procedure and PUSCH transmission are performed in the first embodiment. FIG. 2 is a sequence diagram illustrating an example of an operation in which a two-step random access procedure and PUSCH transmission are performed in the first embodiment. FIG. 3 is a diagram illustrating an example of an implementation of the operation of option 1 in the first embodiment into the specification. FIG. 4 is a diagram illustrating an example of an implementation of the operation of option 1 in the first embodiment into the specification. FIG. 5 is a diagram illustrating an example of an implementation of the operation of option 1 in the first embodiment into the specification. FIG. 6 is a diagram illustrating an example of an implementation of the operation of option 1 in the second embodiment into the specification. FIG. 7 is a diagram illustrating an example of an implementation of the operation of option 1 in the second embodiment into the specification. FIG. 8 is a diagram illustrating an example of an implementation of the operation of option 1 in the second embodiment into the specification.

[0011] The present embodiment will be described below 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.

[0012] In the operation of the wireless communication system of this embodiment, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems after LTE-Advanced (e.g., NR), unless otherwise specified.

[0013] In addition, in the present embodiment 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-".

[0014] In addition, in this embodiment, 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.).

[0015] Furthermore, in this embodiment, "configuring" radio parameters etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0016] Fig. 1 is a diagram showing a configuration example (1) of a wireless communication system according to this embodiment. As shown in Fig. 1, the wireless communication system according to this embodiment 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.

[0017] 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. 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 resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal may be, 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 can apply MIMO (Multiple Input Multiple Output) communication to 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 communicate 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.

[0019] The terminal 20 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (Component Carriers)) to communicate with the base station 10. In carrier aggregation, one PCell (Primary cell) and one or more SCells (Secondary cells) are used. Also, a PUCCH-SCell having a PUCCH may be used.

[0020] First, we will explain the RedCap of the conventional NR Release 17. The maximum bandwidth supported by the RedCapUE considered in NR Release 17 is 20 MHz in FR1 (Frequency Range 1) and 100 MHz in FR2 (Frequency Range 2). In addition, RedCapUE is required to coexist with non-RedCapUE (hereinafter also referred to as "non-RedCapUE") within the system.

[0021] In addition, RedCap UE and non-RedCap UE may be able to share the same initial DL-BWP (Downlink Bandwidth part) (including subcarrier spacing, bandwidth, and location) set by the MIB (Master Information Block), while an initial DL-BWP with separate or additional subcarrier spacing, bandwidth, and location may be set for the RedCap UE.

[0022] RedCapUEs can share the initial DL-BWP (hereinafter also referred to as "DL-BWP#0") for non-RedCapUEs if the maximum bandwidth supported by the RedCapUE is not exceeded.

[0023] In addition, in the NR Release 17 specifications, in order to avoid RF retuning, in the case of TDD, the DL-BWP and UL-BWP of the same index must have the same center frequency.

[0024] Also, after (re)establishing a dedicated RRC connection, a RedCapUE assumes that the initial DL-BWP and active DL-BWP are less than or equal to the maximum DL bandwidth supported by the RedCapUE. The RedCapUE is provided with a DL-BWP by "initialDownlinkBWP" in "DownlinkConfigCommonRedCapSIB" and a UL-BWP by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB". If "initialUplinkBWP" in "UplinkConfigCommonSIB" indicates a UL-BWP greater than the maximum UL-BWP supported by the RedCapUE, the RedCapUE assumes that the UL-BWP is provided by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB".

[0025] A RedCapUE may be provided with a DL-BWP by "BWP-DownlinkDedicated" in addition to the initial DL-BWP. A RedCapUE may be provided with a UL-BWP by "BWP-UplinkDedicated" in addition to the initial UL-BWP, which is less than the maximum UL bandwidth supported by the RedCapUE.

[0026] If the RedCapUE is provided with "RACH-ConfigCommon-RedCap" or "RACH-ConfigCommonTwoStepRA-RedCap", the RedCapUE uses the corresponding parameters to perform the initial access and random access procedures. Otherwise, the RedCapUE uses the corresponding parameters provided by "RACH-ConfigCommon" or "RACH-ConfigCommonTwoStepRA".

[0027] If a RedCap UE is provided with "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB" and has no dedicated PUCCH resource configuration, it uses the PUCCH resource set provided by "pucch-ResourceCommonRedCap" to transmit PUCCH using Hybrid automatic repeat request acknowledgement (HARQ-ACK) information. Note that if "disable-FH-PUCCH" is provided in "PUCCH-ConfigCommonRedCap", PUCCH transmission is disabled.

[0028] For the initial DL-BWP provided by "initialDownlinkBWP" in "DownlinkConfigCommonRedCapSIB", if the RedCapUE monitors the PDCCH according to the CSS (Common search space) set of Type1-PDCCH and does not monitor the PDCCH according to the CSS set of Type2-PDCCH, it recognizes that the initial DL-BWP does not contain an SS / PBCH block or a CORESET (Control resource set) with index 0.

[0029] When a RedCapUE monitors the PDCCH according to the CSS set of Type2-PDCCH, it is assumed that the initial DL-BWP includes the SS / PBCH block and a CORESET with index 0 if the RedCapUE used the SS / PBCH block to acquire SIB1, and includes the SS / PBCH block, and does not include a CORESET with index 0 if the initial DL-BWP does not include the SS / PBCH block used by the RedCapUE to acquire SIB1.

[0030] For an active DL-BWP provided by "BWP-DownlinkDedicated", the RedCapUE shall assume that the active DL-BWP contains SS / PBCH blocks and does not contain a CORESET with index 0, unless the RedCapUE indicates the capability to operate in DL-BWP without receiving SS / PBCH blocks.

[0031] Next, the status of study on RedCap for NR Release 18 will be described. In NR Release 18, eRedCap is being studied to further reduce the complexity of RedCapUE for NR Release 17. Hereinafter, the reduced-function terminal for NR Release 17 will be referred to as RedCapUE, and the extended reduced-function terminal for NR Release 18 will be referred to as eRedCapUE, to distinguish between the two. RedCapUE is an example of a first reduced-function terminal. eRedCapUE is an example of a second reduced-function terminal. In other words, the first reduced-function terminal is a terminal in which a first function has been reduced, and the second reduced-function terminal is a terminal in which a second function different from the first function (including cases where some of the functions overlap) has been reduced.

[0032] Issues being considered include the impact on the network, coexistence of RedCap or eRedCap UEs with non-RedCap UEs in a cell, the impact on the UE, the impact on specifications, etc. Potential solutions to reduce device complexity, which may be complementary, focus on:

[0033] A first solution is being considered to reduce the UE bandwidth to 5 MHz in FR1, which may be specified in combination with relaxed UE processing timelines for PDSCH and / or PUSCH and / or CSI.

[0034] A second solution being considered is to reduce the UE peak data rate for FR1, which may involve limited bandwidth for PDSCH and / or PUSCH, possibly specified in combination with relaxed UE processing timelines for PDSCH and / or PUSCH and / or CSI.

[0035] It is considered necessary to pay attention to the following points for eRedCapUE: It is necessary to reuse the SSB specified in NR Release 15 and minimize changes to L1. It is also necessary to consider BWP operation with / without SSB and with / without RF retuning. It is also considered that some FR1 solutions may be applicable to FR2. Finally, it is considered that a type of reduced-function terminal for a single Release 18 will be defined to further reduce the complexity of the UE.

[0036] eRedCapUE may be defined as follows:

[0037] For example, in the random access procedure, a terminal 20 that notifies that it is an eRedCapUE in at least one of Msg1, Msg3, and MsgA may be defined as an eRedCapUE. For example, an eRedCapUE may transmit Msg1 or MsgA using resources defined or configured for the eRedCapUE, or may notify that it is an eRedCapUE in a notification field in Msg3 defined for the eRedCapUE.

[0038] For example, a terminal 20 that supports specific UE capabilities may be defined as an eRedCapUE. The specific UE capabilities may be, for example, 1) to 7) shown below.

[0039] 1) Supporting up to 5 MHz bandwidth for PDSCH and PUSCH in FR1. 2) Supporting relaxed UE processing time for PDSCH, PUSCH, and / or CSI. 3) Supporting reduced UE peak data rates in FR1. 4) Supporting one or two receive branches and the corresponding maximum number of DL-MIMO layers. 5) Supporting FD (Full Duplex)-FDD or Type A HD (Half Duplex)-FDD in the FR1 FDD band. 6) Supporting 64QAM (Quadrature amplitude modulation) or 256QAM in FR1. 7) Not supporting carrier aggregation or dual connectivity.

[0040] Furthermore, the terminal 20 that reports to the base station 10 that it supports the specific UE capability through a UE capability report may be defined as an eRedCapUE. Note that the existing terminal may be a terminal other than an eRedCapUE.

[0041] As described above, the eRedCapUE may be limited to a baseband bandwidth of 5 MHz for PDSCH reception or PUSCH transmission. The RF bandwidth of the eRedCapUE for UL and DL is 20 MHz. Physical channels and signals other than PDSCH or PUSCH may be allowed to use BWPs up to a maximum of 20 MHz bandwidth. The eRedCapUE may also support additional early indication. The eRedCapUE may also support 15 kHz SCS and 30 kHz SCS.

[0042] Here, a terminal that supports both the baseband bandwidth reduction function and the peak data rate reduction function (hereinafter also referred to as a "BW3+PR1 terminal"), or a terminal that supports only the peak data rate reduction function (hereinafter also referred to as a "PR1 terminal") may be defined as an eRedCapUE.

[0043] Furthermore, since the network cannot distinguish between a BW3+PR1 terminal and a PR1 terminal until it receives a UE capability report from the terminal, the initial access procedures for the BW3+PR1 terminal and the PR1 terminal may not need to be distinguished or may be the same.

[0044] The peak data rates of the BW3+PR1 terminal and the PR1 terminal may be the same for unicast and broadcast. The PRB processing capability of the PR1 terminal may not be limited to 25 PRBs at 15 kHz SCS and 12 PRBs at 30 kHz SCS, and the PRB processing capability may be a PRB size corresponding to 20 MHz. The PRB processing capability of the BW3+PR1 terminal may be limited to a maximum of 25 PRBs at 15 kHz SCS and a maximum of 12 PRBs at 30 kHz SCS.

[0045] For example, the BW3+PR1 terminal may be a terminal that has reported only FG (Feature group (see Non-Patent Document 2)) 48-1 to the network. The BW3+PR1 terminal may be a terminal that does not support FG 48-2 or a terminal that has not notified FG 48-2.

[0046] For example, the PR1 terminal may be a terminal that has reported FG48-1 and FG48-2 to the network, or may be a terminal that supports FG48-2 or a terminal that has notified FG48-2.

[0047] For example, a terminal that does not support FG48-2 may not assume that the number of RBs allocated to all PUSCHs exceeds 5 MHz. That is, a terminal that supports both the baseband bandwidth reduction function and the peak data rate reduction function may not assume that the number of RBs allocated to all PUSCHs exceeds 5 MHz.

[0048] For example, a terminal that supports FG48-2 may not assume that the number of RBs allocated to the PUSCH related to random access exceeds 5 MHz. That is, a terminal that supports only the peak data rate reduction function may not assume that the number of RBs allocated to the PUSCH related to random access exceeds 5 MHz.

[0049] Here, a terminal that supports FG48-2, that is, a terminal that supports only the peak data rate reduction function, does not need to assume that a number of RBs exceeding 5 MHz is allocated to the PUSCH / unicast PDSCH that is transmitted / received after receiving the PUSCH and Msg4 / MsgB related to random access until the UE capability report is performed. However, conventional standards (for example, the 3GPP (registered trademark) standard) do not specify restrictions on the number of RBs for the PUSCH / unicast PDSCH after receiving Msg4 / MsgB for terminals that support FG48-2.

[0050] According to this embodiment, it is possible to define restrictions on resource allocation for PUSCH / unicast PDSCH for terminals that support FG48-2 from the time after reception of Msg4 / MsgB until UE capability reporting is performed or completed.

[0051] In this embodiment, reception of Msg4 / B may be interpreted as a case where the contention resolution ID is correctly decoded / received or an ACK in response to Msg4 is transmitted.

[0052] The terminal 20 in this embodiment is, for example, a terminal that supports FG48-2, or a terminal that supports only eRedCapUE or the peak data rate reduction function (PR1 terminal).

[0053] In this embodiment, after the terminal 20 receives Msg4 / MsgB may mean after the random access procedure is completed.

[0054] (First embodiment)

[0055] According to the first embodiment, restrictions on frequency resource allocation for PUSCH transmitted by a terminal supporting FG48-2 after receiving Msg4 / MsgB may be defined.

[0056] 2 is a sequence diagram showing an example of an operation in which a four-step random access procedure and PUSCH transmission are performed in the first embodiment. In the example of FIG. 2, the terminal 20 and the base station 10 perform the four-step random access procedure.

[0057] In step S11, the terminal 20 transmits Msg1 (Random Access Preamble) to the base station 10. In step S12, the base station 10 transmits Msg2 (Random Access Response) to the terminal 20 in response to Msg1. In step S13, the terminal 20 transmits Msg3 (Scheduled Transmission) to the base station 10. In step S14, the base station 10 transmits Msg4 (Contention Resolution) to the terminal 20.

[0058] In step S15, after receiving Msg4, the terminal 20 transmits a PUSCH to the base station 10. A restriction on frequency resource allocation may be applied to the PUSCH in step S15. In step S16, the terminal 20 and the base station 10 perform UE capability reporting.

[0059] 3 is a sequence diagram showing an example of an operation in which a two-step random access procedure and PUSCH transmission are performed in the first embodiment. In the example of FIG. 2, the terminal 20 and the base station 10 perform the two-step random access procedure.

[0060] In step S21, the terminal 20 transmits MsgA (Random Access Preamble+data) to the base station 10. In step S22, the base station 10 transmits MsgB (Random Access Response) to the terminal 20.

[0061] The operations in steps S23 and S24 are the same as the operations in steps S15 and S16 in FIG. 2, respectively.

[0062] The PUSH transmitted by the terminal 20 after receiving Msg4 / MsgB may be any one or a combination of multiple ones of (1-1) to (1-8) shown below, or all of them.

[0063] (1-1) Msg5 PUSCH (1-2) PUSCH scheduled with DCI format 0_0 scrambled with C-RNTI (1-3) PUSCH for transmitting UE capability reporting (1-4) PUSCH transmitted from after receiving Msg4 / MsgB or after transmitting HARQ-ACK for Msg4 / MsgB until receiving RRCSetup, which is a message for establishing an RRC connection and / or a radio bearer (1-5) PUSCH transmitted from after receiving Msg4 / MsgB or after transmitting HARQ-ACK for Msg4 / MsgB until transmitting HARQ feedback corresponding to reception of RRCSetup, which is a message for establishing an RRC connection and / or a radio bearer (1-6) A PUSH transmitted from after receiving Msg4 / MsgB or transmitting HARQ-ACK for Msg4 / MsgB until transmitting RRCSetupComplete, a message notifying that RRC connection establishment has been successfully completed. (1-7) A PUSH that transmits RRCSetupComplete, a message notifying that RRC connection establishment has been successfully completed. (1-8) A PUSH until dedicated configuration of specific RRC parameters is set.

[0064] The Msg5 PUSCH in (1-1) above may be, for example, the PUSCH that is first transmitted from the terminal 20 after the terminal 20 receives the Msg4.

[0065] Depending on which of the above (1-1) to (1-8) PUSHs is used, different options may be applied from among the options shown below.

[0066] Option 1) A terminal that supports FG48-2 does not need to assume that the resources of the PUSCH transmitted after receiving Msg4 / MsgB are scheduled to exceed 5 MHz.

[0067] Option 2) A terminal that supports FG48-2 may assume that the resources of the PUSCH transmitted after receiving Msg4 / MsgB are scheduled to exceed 5 MHz.

[0068] 4A to 4C are diagrams showing an example of implementation of the operation of option 1 in the first embodiment into specifications.

[0069] As shown in Figure 4A, a terminal supporting FG48-2 may not be expected to transmit PUSCH per hop in a slot on a bandwidth exceeding 25 PRBs in a 15 kHz Subcarrier Spacing (SCS) or 12 PRBs in a 30 kHz SCS, which may be a PUSCH scheduled by an RAR UL grant, a DCI scrambled by a TC-RNTI, or a DCI format 0_0 scrambled by a C-RNTI before the UE decodes RRCSetup, or a PUSCH configured for a Type 2 random access procedure.

[0070] As shown in Figure 4C, a terminal supporting FG48-2 may not be expected to transmit a PUSCH per hop in a slot on a bandwidth exceeding 25 PRBs at 15 kHz SCS or 12 PRBs at 30 kHz SCS. The PUSCH may be a PUSCH scheduled by an RAR UL grant, a DCI scrambled by a TC-RNTI, or a DCI format 0_0 scrambled by a C-RNTI before the UE configures a dedicated higher layer configuration including a predetermined field (xxx), or a PUSCH configured for a Type 2 random access procedure. The predetermined field (xxx) may be at least one field included in push-config, MsgA-PUSCH-Config, push-config, or MsgA-PUSCH-Config. However, the predetermined field (xxx) is not limited to this and may be any field.

[0071] As shown in Figure 4B, a terminal supporting FG48-2 may not be expected to transmit PUSCH per hop in a slot on a bandwidth exceeding 25 PRBs at 15 kHz SCS or 12 PRBs at 30 kHz SCS, which may be a PUSCH scheduled by an RAR UL grant, a DCI scrambled by TC-RNTI, or a DCI format 0_0 scrambled by C-RNTI until the UE sends RRCSetupComplete, or a PUSCH configured for a Type 2 random access procedure.

[0072] As described above, the terminal 20 in the first embodiment receives Msg4 or MsgB in the random access procedure, and after receiving Msg4 or MsgB, controls reception processing of the uplink shared channel (PUSCH) transmitted from the base station 10. When the terminal 20 is a terminal with a reduced predetermined function (for example, a terminal supporting FG48-2), the terminal 20 does not perform reception processing of the downlink shared channel scheduled beyond predetermined frequency resources.

[0073] According to the first embodiment described above, it is possible to set a PUSCH bandwidth suitable for a terminal 20 that supports FG48-2 before reporting UE capabilities.

[0074] That is, in a wireless communication system, a channel with an appropriate PUSCH bandwidth can be set for a terminal with reduced functionality.

[0075] Second Embodiment

[0076] According to the second embodiment, restrictions on frequency resource allocation for unicast PDSCHs that a terminal supporting FG48-2 receives after receiving Msg4 / MsgB may be defined.

[0077] Fig. 5 is a sequence diagram showing an example of an operation in which a four-step random access procedure and unicast PDSCH reception are performed in the second embodiment. In the example of Fig. 5, the terminal 20 and the base station 10 perform the four-step random access procedure.

[0078] In step S31, the terminal 20 transmits Msg1 (Random Access Preamble) to the base station 10. In step S32, the base station 10 transmits Msg2 (Random Access Response) to the terminal 20 in response to Msg1. In step S13, the terminal 20 transmits Msg3 (Scheduled Transmission) to the base station 10. In step S34, the base station 10 transmits Msg4 (Contention Resolution) to the terminal 20.

[0079] In step S35, after receiving Msg4, the terminal 20 receives the unicast PDSCH from the base station 10. A restriction on frequency resource allocation may be applied to the unicast PDSCH in step S35. In step S36, the terminal 20 and the base station 10 execute UE capability reporting.

[0080] Fig. 6 is a sequence diagram showing an example of an operation in which a two-step random access procedure and unicast PDSCH reception are performed in the second embodiment. In the example of Fig. 6, the terminal 20 and the base station 10 perform the two-step random access procedure.

[0081] In step S41, the terminal 20 transmits MsgA (Random Access Preamble+PUSCH) to the base station 10. In step S42, the base station 10 transmits MsgB (Random Access Response) to the terminal 20.

[0082] The operations in steps S43 and S44 are the same as the operations in steps S35 and S36 in FIG. 6, respectively.

[0083] The unicast PDSCH received by terminal 20 after receiving Msg4 / MsgB may be any one or a combination of multiple ones of (2-1) to (2-5) shown below, or all of them.

[0084] (2-1) PDSCH scheduled with DCI format 1_0 scrambled with C-RNTI (2-2) Unicast PDSCH received after receiving Msg4 / MsgB or after transmitting HARQ-ACK for Msg4 / MsgB until receiving RRCSetup (2-3) PDSCH received after receiving Msg4 / MsgB or after transmitting HARQ-ACK for Msg4 / B until transmitting HARQ feedback for receiving RRCSetup (2-4) Unicast PDSCH received after receiving Msg4 / MsgB or after transmitting HARQ-ACK for Msg4 / MsgB until transmitting RRCSetupComplete (2-5) Dedicated PDSCH for specific RRC parameters Unicast PDSCH until configuration is set

[0085] Depending on which of the PDSCHs (2-1) to (2-5) above it is, different options may be applied among the options shown below.

[0086] Option 1) A terminal that supports FG48-2 does not need to assume that the resources of the unicast PDSCH received after receiving Msg4 / MsgB are scheduled to exceed 5 MHz.

[0087] Option 2) A terminal supporting FG48-2 may assume that the resources of the unicast PDSCH received after receiving Msg4 / MsgB are scheduled to exceed 5 MHz. The timeline requirement for HARQ feedback transmission for the PDSCH may be extended. For example, the existing requirement may be extended by one slot (N_(T,1) + 1.5 msec for 15 kHz SCS or N_(T,1) + 1.0 msec for 30 kHz SCS).

[0088] 7A to 7C are diagrams illustrating an example of implementation of the operation of option 1 in the second embodiment into specifications.

[0089] As shown in FIG. 7A, a terminal supporting FG48-2 may not be expected to process PDSCH reception scheduled with a DCI format including a CRC scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI over a predetermined number of PRBs before decoding RRCSetup.

[0090] As shown in FIG. 7B, a terminal supporting FG48-2 may not be expected to process PDSCH reception scheduled with a DCI format including a CRC scrambled by a C-RNTI, CS-RNTI, or MCS-C-RNTI over a predetermined number of PRBs until the terminal sends RRCSetupComplete.

[0091] As shown in FIG. 7C , a terminal supporting FG48-2 may not assume that it will process PDSCH reception scheduled by a DCI format including a CRC scrambled by a C-RNTI, CS-RNTI, or MCS-C-RNTI over a predetermined number of PRBs until a dedicated higher layer configuration including a predetermined field (xxx) is configured in the terminal. The predetermined field (xxx) may be a field included in pdsch-config. However, the predetermined field (xxx) is not limited to this and may be any field.

[0092] In Figures 7A-7C, the predetermined number of PRBs is, for example, greater than 25 PRBs for a 15 kHz SCS and greater than 12 PRBs for a 30 kHz SCS within a slot.

[0093] As described above, the terminal 20 in the second embodiment receives Msg4 or MsgB in the random access procedure, and after receiving Msg4 or MsgB, controls reception processing of the downlink shared channel (unicast PDSCH) transmitted by unicast from the base station 10. When the terminal 20 is a terminal with a reduced predetermined function (for example, a terminal supporting FG48-2), the terminal 20 does not perform reception processing of the downlink shared channel scheduled beyond a predetermined frequency resource.

[0094] According to the second embodiment described above, it is possible to set a unicast PDSCH bandwidth suitable for terminal 20 that supports FG48-2 before reporting UE capabilities. That is, in a wireless communication system, it is possible to set a channel with a unicast PDSCH bandwidth suitable for a terminal with reduced functionality.

[0095] That is, in a wireless communication system, a channel with an appropriate unicast PDSCH bandwidth can be set for a terminal with reduced functionality.

[0096] (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 implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0097] <Base Station 10> Fig. 8 is a diagram showing an example of the functional configuration of the base station 10 in this embodiment. As shown in Fig. 8, 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. 8 is merely an example. The names of the functional divisions and functional units may be any names as long as they can execute the operations according to this embodiment.

[0098] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal wirelessly. The transmitter 110 also transmits inter-network node messages to other network nodes. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

[0099] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information related to channel transmission and reception.

[0100] The control unit 140 performs control to realize the functions described in the embodiments. Also, as described in the embodiments, the control unit 140 performs control related to channel transmission and reception. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0101] <Terminal 20> Fig. 9 is a diagram showing an example of the functional configuration of the terminal 20 in this embodiment. As shown in Fig. 9, 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. 9 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations according to this embodiment.

[0102] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 wirelessly receives various signals and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. For example, the transmitter 210 transmits a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 220 receives the PSCCH, PSSCH, PSDCH, or PSBCH, and the like, from the other terminal 20.

[0103] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The setting information includes, for example, information related to channel transmission and reception.

[0104] The control unit 240 performs control to realize the functions described in the embodiments. Also, as described in the embodiments, the control unit 240 performs control related to channel transmission and reception. 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.

[0105] (Hardware Configuration) The block diagrams (FIGS. 8 and 9) 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.

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

[0107] 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. 10 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.

[0108] 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.

[0109] 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.

[0110] 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.

[0111] The processor 1001 also 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. 8 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. For example, the control unit 240 of the terminal 20 shown in FIG. 9 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.

[0112] 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.

[0113] 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.

[0114] 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.

[0115] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives 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).

[0116] 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.

[0117] 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.

[0118] Fig. 11 shows an example configuration of a vehicle 2001. As shown in Fig. 11, 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.

[0119] 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.

[0120] 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).

[0121] 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 front or rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front or rear wheel air pressure signal 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.

[0122] 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 (outputting) 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 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0123] 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.

[0124] 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.

[0125] 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.

[0126] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0127] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from 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.

[0128] (Summary of the embodiment) As described above, according to the present embodiment, there is provided a terminal including: a receiving unit that receives Msg4 or MsgB in a random access procedure; and a control unit that controls reception processing of a downlink shared channel that is unicast transmitted from a base station after receiving the Msg4 or MsgB, wherein when the terminal is a terminal with a predetermined function reduced, the control unit does not perform reception processing of the downlink shared channel that is scheduled beyond a predetermined frequency resource.

[0129] With the above configuration, before the UE capability report, it is possible to set a suitable bandwidth for the terminal 20, which is an eRedCapUE that supports only the peak data rate reduction function. That is, in the wireless communication system, it is possible to set a channel with a suitable bandwidth for the terminal with reduced functions.

[0130] The control unit may not perform reception processing for the downlink shared channel scheduled beyond the predetermined frequency resource before decoding the RRC setup. With this configuration, it is possible to set a suitable bandwidth for the terminal 20 that is an eRedCap UE that supports only a peak data rate reduction function before the UE capability report.

[0131] The control unit may not perform reception processing for the downlink shared channel scheduled beyond the predetermined frequency resource until transmitting an RRC setup complete message. With this configuration, it is possible to set a suitable bandwidth for the terminal 20 that is an eRedCap UE supporting only a peak data rate reduction function before the UE capability report.

[0132] The control unit may not perform reception processing for the downlink shared channel scheduled beyond the predetermined frequency resource before a dedicated higher layer configuration is configured for the terminal. With this configuration, it is possible to set a suitable bandwidth for the terminal 20 that is an eRedCap UE supporting only a peak data rate reduction function before the UE capability report.

[0133] A communication method executed by a terminal in this embodiment may include: receiving Msg4 or MsgB in a random access procedure; and controlling reception processing of a downlink shared channel unicast transmitted from a base station after receiving the Msg4 or MsgB. When the terminal is a terminal with reduced functionality, the controlling step may not require the terminal to perform reception processing of the downlink shared channel scheduled beyond a predetermined frequency resource. With this configuration, a bandwidth suitable for the terminal 20, which is an eRedCap UE supporting only the peak data rate reduction function, can be set before the UE capability report.

[0134] The wireless communication system according to the present embodiment includes a base station and a terminal. The base station may transmit Msg4 or MsgB in a random access procedure. The terminal may receive the Msg4 or MsgB, and after receiving the Msg4 or MsgB, control reception processing of a downlink shared channel unicast transmitted from the base station. When the terminal is a terminal with a reduced predetermined function, the terminal may not perform reception processing of the downlink shared channel scheduled beyond a predetermined frequency resource.

[0135] With the above configuration, before the UE capability report, it is possible to set a suitable bandwidth for the terminal 20, which is an eRedCapUE that supports only the peak data rate reduction function. That is, in the wireless communication system, it is possible to set a channel with a suitable bandwidth for the terminal with reduced functions.

[0136] (Supplementary Notes on the Embodiments) Although the present embodiment has 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 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment 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.

[0137] 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.

[0138] 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).

[0139] 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.

[0140] 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).

[0141] 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.

[0142] 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.

[0143] 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).

[0144] 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.

[0145] 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.

[0146] 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.

[0147] 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.

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

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

[0150] 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.

[0151] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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.

[0152] 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.

[0153] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0155] 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.

[0156] 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 object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 be a device that does 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.

[0157] 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.

[0158] 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.

[0159] 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.

[0160] 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.

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

[0162] 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."

[0163] 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.

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

[0165] 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.

[0166] 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.

[0167] 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 duration, 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.

[0168] 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.

[0169] 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.

[0170] 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.

[0171] 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.

[0172] 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.

[0173] 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.

[0174] 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.

[0175] 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.

[0176] 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.

[0177] 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.

[0178] 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.

[0179] 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.

[0180] 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.

[0181] 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.

[0182] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

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

[0184] 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.

[0185] 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.

[0186] 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."

[0187] 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).

[0188] 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.

[0189] REFERENCE SIGNS LIST 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 30 Core network 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 RPM 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 comprising: a receiving unit that receives Msg4 or MsgB in a random access procedure; and a control unit that controls reception processing of a downlink shared channel that is unicast transmitted from a base station after receiving the Msg4 or MsgB, wherein when the terminal is a terminal with a specified function reduced, the control unit does not perform reception processing of the downlink shared channel that is scheduled beyond a specified frequency resource.

2. The terminal according to claim 1, wherein the control unit does not perform reception processing for the downlink shared channel scheduled beyond the predetermined frequency resource before decoding an RRC (Radio Resource Control) setup.

3. The terminal according to claim 1, wherein the control unit does not perform reception processing for the downlink shared channel scheduled beyond the predetermined frequency resource until an RRC setup complete message is transmitted.

4. The terminal according to claim 1, wherein the control unit does not perform reception processing for the downlink shared channel scheduled beyond the predetermined frequency resources before a dedicated higher layer configuration is set in the terminal.

5. A communications method executed by a terminal, comprising: a step of receiving Msg4 or MsgB in a random access procedure; and a step of controlling reception processing of a downlink shared channel transmitted by unicast from a base station after receiving the Msg4 or MsgB, wherein the control step does not perform reception processing of the downlink shared channel scheduled beyond a specified frequency resource when the terminal is a terminal with a specified function reduced.

6. A wireless communication system comprising a terminal and a base station, wherein the base station transmits Msg4 or MsgB in a random access procedure, the terminal receives the Msg4 or MsgB, and after receiving the Msg4 or MsgB, controls reception processing of a downlink shared channel transmitted by unicast from the base station, and when the terminal is a terminal with a specified function reduced, the terminal does not perform reception processing of the downlink shared channel scheduled beyond a specified frequency resource.

Images