User equipment, radio access network node, and method therefor

Abstract

This radio access network (RAN) node transmits a system information block type 1 (SIB1) including configuration information about a plurality of initial downlink (DL) bandwidth parts (BWPs) and a plurality of initial uplink (UL) BWPs unique to a specific type of user equipment (UE). The foregoing can, for example, contribute to providing a specific method for notifying a specific type of UE about a plurality of initial DL BWPs and a plurality of initial UL BWPs unique to or specialized for that specific type of UE.

Description

User Equipment, Radio Access Network Node, and Methods Thereof

[0001] The present disclosure relates to wireless communication systems, and more particularly to signaling between radio access network nodes and User Equipment (UE).

[0002] The 3rd Generation Partnership Project (3GPP®) Release 17 supports Reduced Capability (RedCap) UEs (see, for example, Section 16.13 of 3GPP 2.0). RedCap UEs have reduced functionality compared to non-RedCap UEs, aiming for low complexity. RedCap UEs are required to support a maximum UE channel bandwidth of 20 MHz in FR1 (i.e., sub-6 GHz bands) and 100 MHz in FR2 (i.e., millimeter wave (mmWave) bands). However, Carrier Aggregation (CA), Multi-Radio Dual Connectivity (MR-DC), Dual Active Protocol Stack (DAPS), and Integrated Access and Backhaul (IAB)-related features are not supported in RedCap UEs.

[0003] For example, RedCap UEs have a reduced or relaxed minimum number of UE reception (Rx) branches and a maximum number of downlink (DL) Multiple Input Multiple Output (MIMO) layers compared to non-RedCap UEs. In FR1, one DL MIMO layer is supported if one Rx branch is supported, and two DL MIMO layers are supported if two Rx branches are supported. In FR2, one or two DL MIMO layers can be supported, and two Rx branches are always supported. In FR1 and FR2, UE functions and corresponding capabilities related to more than two UE Rx branches or more than two DL MIMO layers, and UE functions and capabilities related to more than two UE Tx branches or more than two uplink (UL) MIMO layers are not supported by RedCap UEs.

[0004] RedCap UEs in Radio Resource Control (RRC)_IDLE and RRC_INACTIVE monitor paging only in the initial DL Bandwidth Part (BWP) (default or RedCap-specific) associated with the Cell Defining (CD) Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block (SSB) and perform cell (re)selection and measurements in the CD-SSB. If a RedCap-specific initial UL BWP is configured, RedCap UEs in RRC_IDLE and RRC_INACTIVE must use only the RedCap-specific initial UL BWP to perform random access (Random Access Channel (RACH)).

[0005] Non-Patent Document 2 specifies extensions of RRC messages for RedCap UEs. System Information Block Type 1 (SIB1) includes the configuration of initial DL BWP and initial UL BWP for non-RedCap UEs, and can additionally include the configuration of initial DL BWP and initial UL BWP specific or dedicated for RedCap UEs.

[0006] The RedCap-specific initial UL BWP configuration is indicated by the initialUplinkBWP-RedCap-r17 field or information element (IE) in the UplinkConfigCommonSIB in the ServingCellConfigCommonSIB of SIB1. The initialUplinkBWP-RedCap-r17 field or information element (IE) is the BWP-UplinkCommon IE. The BWP-UplinkCommon IE includes the rach-ConfigCommon field or IE. The rach-ConfigCommon field or IE indicates the cell-specific random access parameter configuration that the UE, i.e., the RedCap UE, uses for contention-based and contention-free random access in this BWP.

[0007] On the other hand, the RedCap-specific initial DL BWP configuration is indicated by the initialDownlinkBWP-RedCap-r17 field or IE in the DownlinkConfigCommonSIB in the ServingCellConfigCommonSIB of SIB1. The initialDownlinkBWP-RedCap-r17 field or IE is the BWP-DownlinkCommon IE. The BWP-DownlinkCommon IE includes the pdcch-ConfigCommon field or IE. The pdcch-ConfigCommon field or IE can specify a Type-1 common search space in the ra-SearchSpace field or IE. Specifically, the pdcch-ConfigCommon field or IE includes a commonSearchSpaceList field or IE that specifies one or more common search spaces (CSSs) within the BWP. The commonSearchSpaceList field or IE is a list of up to four SearchSpace IEs. The SearchSpace IE indicates a SearchSpaceId and defines the search method and search location for Physical Downlink Control Channel (PDCCH) candidates.

[0008] That is, the RedCap-specific initial DL BWP can be configured with a Type-1 common search space for receiving PDCCHs carrying Downlink Control Information (DCI) for random access message 2 (MSG2), message B (MSGB), and message 4 (MSG4), i.e., Physical Downlink Shared Channel (PDSCH). A RedCap UE searches within the Type-1 common search space configured in the RedCap-specific initial DL BWP to receive DCI / PDCCHs indicating PDSCHs carrying MSG2, MSGB, and MSG4, and can receive MSG2, MSGB, and MSG4 based on the received DCI.

[0009] Section 1 of Non-Patent Document 3 states that in a past 3GPP Technical Specification Group Radio Access Network (TSG-RAN) Working Group 1 (WG1) (RAN1) meeting, it was agreed to further study several options to ensure that the best SSB-related Random Access Channel (RACH) occasions fit within the RedCap UE bandwidth. One of these options (Option 2) is one or more separate initial UL BWP(s) for RedCap UEs.

[0010] Non-Patent Document 3 proposes multiple initial DL BWPs for RedCap UEs in Section 2.1 (Figure 1 and Proposal 2 in Non-Patent Document 2). The multiple initial DL BWPs are used for initial access (or random access), specifically for transmitting a Random Access Response (RAR) and paging during initial access. One of these initial DL BWPs is the initial DL BWP configured by the Master Information Block (MIB). The others may be "copies" of the initial DL BWP configured by the MIB, e.g., they may use the same Control Resource Set (CORESET) #0, the same PDCCH search space, the same bandwidth, and the same subcarrier spacing. Only the center frequencies of these initial DL BWPs need to be configured. Different RedCap UEs can be configured to different initial DL BWPs for random access and paging reception.

[0011] Furthermore, Section 2.2 of Non-Patent Document 3 describes multiple initial UL BWPs for RedCap UEs. Specifically, this presents a case where multiple initial UL BWPs are configured corresponding to one initial DL BWP (Figure 3 of Non-Patent Document 3). In this case, it describes that the RedCap UE determines one initial UL from multiple initial UL BWPs based on a selected random access occasion (RO).

[0012] 3GPP TS 38.300 V17.1.0 (2022-06), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 17), July 20223GPP TS 38.331 V17.1.0 (2022-06), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 17), July 2022 OPPO, "Discussion on reduced UE bandwidth", R1-2102402, 3GPP TSG-RAN WG1 Meeting #104b-e, April 12-20, 2021

[0013] Non-patent document 3 does not clearly describe how to configure multiple initial DL BWPs and multiple initial UL BWPs specific to RedCap, in other words, how the network notifies RedCap UEs of these.

[0014] One of the objectives to be achieved by the embodiments disclosed in this specification is to provide an apparatus, a method, and a program that contribute to providing a specific method for notifying a specific type of UE (e.g., RedCap UEs) of multiple initial DL BWPs and multiple initial UL BWPs that are specific to or dedicated to the specific type of UE. It should be noted that this objective is only one of multiple objectives to be achieved by the multiple embodiments disclosed in this specification. Other objectives or problems and novel features will become apparent from the description of this specification or the accompanying drawings.

[0015] In a first aspect, a UE includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to receive an SIB1 containing configuration information for a plurality of initial DL BWPs and a plurality of initial UL BWPs specific to a particular type of UE, and the at least one processor configured to select one initial DL BWP and one initial UL BWP to be used for random access from the plurality of initial DL BWPs and the plurality of initial UL BWPs.

[0016] In a second aspect, a method performed by a UE includes the following steps: (a) receiving an SIB1 containing configuration information of a plurality of initial DL BWPs and a plurality of initial UL BWPs specific to a particular type of UE; and (b) selecting one initial DL BWP and one initial UL BWP to be used for random access from the plurality of initial DL BWPs and the plurality of initial UL BWPs.

[0017] In a third aspect, a first RAN node includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to transmit a SIB1 containing configuration information for a plurality of initial DL BWPs and a plurality of initial UL BWPs specific to a particular type of UE.

[0018] In a fourth aspect, a method performed by a first RAN node includes transmitting a SIB1 containing configuration information for a plurality of initial DL BWPs and a plurality of initial UL BWPs specific to a particular type of UE.

[0019] According to the above-described aspects, an apparatus, a method, and a program can be provided that contribute to providing a specific method for informing a specific type of UE (e.g., RedCap UEs) of multiple initial DL BWPs and multiple initial UL BWPs that are specific to or dedicated to the specific type of UE.

[0020] 1 is a diagram illustrating an example configuration of a wireless communication system according to one or more embodiments; 2 is a sequence diagram illustrating example signaling between a RAN node and a UE according to one or more embodiments; 3 is a diagram illustrating an example message structure or format of SIB1 according to one or more embodiments; 4 is a conceptual diagram illustrating BWP transition according to one or more embodiments; 5 is a flowchart illustrating an example operation of a UE according to one or more embodiments; 6 is a sequence diagram illustrating example signaling between a RAN node and a UE according to one or more embodiments; 7 is a diagram illustrating an example message structure or format of SIB1 according to one or more embodiments; 8 is a block diagram illustrating an example configuration of a RAN node according to one or more embodiments; 9 is a block diagram illustrating an example configuration of a UE according to one or more embodiments;

[0021] Hereinafter, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are designated by the same reference numerals, and for clarity of explanation, duplicate explanations will be omitted as necessary.

[0022] The multiple embodiments described below can be used independently, or two or more embodiments can be combined as appropriate. These multiple embodiments have different novel features. Therefore, these multiple embodiments contribute to solving different purposes or problems and achieve different effects.

[0023] Each drawing is merely an example for describing one or more embodiments. Each drawing may not relate to only one particular embodiment, but may also relate to one or more other embodiments. As will be understood by those skilled in the art, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings to create, for example, an embodiment not explicitly shown or described. Not all features or steps shown in any one drawing are necessary to describe an exemplary embodiment, and some features or steps may be omitted. The order of steps described in any drawing may be changed as appropriate.

[0024] The following embodiments will be described with a focus on the 3GPP Long Term Evolution (LTE) system and the fifth generation mobile communication system (5G system). However, these embodiments may be applied to other wireless communication systems that support technologies similar to those of the 3GPP system. Note that, unless otherwise specified, the term LTE used in this specification includes improvements and developments of LTE and LTE-Advanced that enable interworking with the 5G system.

[0025] As used herein, depending on the context, "if" may be interpreted to mean "when," "at or around the time," "after," "upon," "in response to determining," "in accordance with a determination," or "in response to detecting." These expressions may be interpreted to have the same meaning, depending on the context.

[0026] First, the configuration and operation of several network elements common to several embodiments will be described. Figure 1 shows an example configuration of a wireless communication system according to several embodiments. In the example of Figure 1, the wireless communication system includes a Radio Access Network (RAN) node 1 and one or more UEs 2. Each element (network function) shown in Figure 1 can be implemented, for example, as a network element on dedicated hardware, as a software instance running on the dedicated hardware, or as a virtualized function instantiated on an application platform.

[0027] The RAN node 1 is deployed in the RAN. The RAN node 1 may be an NG-RAN node, specifically a gNB or ng-eNB. The ng-eNB provides E-UTRA user plane and control plane protocol termination to the UE and is connected to the 5G Core Network (5GC) via an NG interface. The RAN node 1 may be a combination of a Central Unit (CU) (e.g., gNB-CU or eNB-CU) and one or more Distributed Units (DUs) (e.g., gNB-DUs or eNB-DUs) in a cloud RAN (C-RAN) deployment.

[0028] The RAN node 1 provides a cell 10 to multiple types of UEs 2. These multiple types of UEs 2 use the cell 10 as a serving cell and perform contention-based random access (CBRA) in the cell 10. The RAN node 1 may also provide one or more other cells. In this case, the cell 10 may be a primary cell (PCell) of Carrier Aggregation (CA), and one or more other cells may be secondary cells (SCells). That is, the cell 10 is the cell from which a UE 2 in an RRC_IDLE state initiates an RRC connection establishment procedure. A UE 2 in an RRC_INACTIVE state may initiate an RRC connection resume procedure with the cell 10. A UE 2 in an RRC_CONNECTED state may initiate an RRC connection re-establishment procedure with the cell 10.

[0029] The RAN node 1 broadcasts Minimum SI (i.e., MIB and SIB1) in the cell 10. The RAN node 1 may also transmit other SI. Other SI includes all SIBs that are not always broadcast within Minimum SI. These SIBs are either broadcast periodically on the DL Shared Channel (DL-SCH), broadcast on demand on the DL-SCH (i.e., upon request from UEs in RRC_IDLE or RRC_INACTIVE), or sent in a dedicated manner on the DL_SCH to UEs in RRC_CONNECTED.

[0030] The UEs 2 may be referred to by other terms, such as wireless terminals, mobile terminals, mobile stations, or wireless transmit receive units (WTRUs). The UEs 2 may be implemented in a machine, vehicle, or device. By way of example and not limitation, the UEs 2 may be implemented in a mobile machine, vehicle, or device, and more specifically, may be implemented in an automated guided vehicle (AGV), a mobile robot, construction equipment, or an unmanned or uncrewed aerial vehicle (UAV).

[0031] Each UE 2 performs cell selection or cell reselection when in RRC_IDLE or RRC_INACTIVE state. Furthermore, each UE 2 may perform RRC connection re-establishment when in RRC_CONNECTED state. Each UE 2 receives MIB and SIB1 in the cell 10 and sets an initial DL BWP and an initial UL BWP based on the cell-specific common parameters of the initial DL BWP and the initial UL BWP of the cell 10 included in SIB1. Then, each UE 2 performs a random access procedure in the cell 10 using the initial DL BWP and the initial UL BWP, and initiates an RRC connection establishment, resumption, or re-establishment procedure.

[0032] UEs 2 are classified into first and second types. The second type UEs are UEs with limited capabilities compared to the first type UEs. The second type UEs may have limited RF capabilities compared to the first type UEs. The second type UEs may be RedCap UEs. In contrast, the first type UEs may be referred to as normal UEs or non-RedCap UEs. In the following description, the second type UEs are considered to be RedCap UEs, and the first type UEs are considered to be normal UEs or non-RedCap UEs.

[0033] As previously mentioned, RedCap UEs have reduced functionality compared to non-RedCap UEs, with the intention of having low complexity. Current 3GPP specifications mandate that RedCap UEs support a maximum UE channel bandwidth of 20 MHz in FR1 (i.e., sub-6 GHz bands) and 100 MHz in FR2 (i.e., millimeter wave (mmWave) bands). However, CA, MR-DC, DAPS, and IAB-related features are not supported by RedCap UEs.

[0034] For example, RedCap UEs have a reduced or relaxed minimum number of UE Rx branches and a relaxed maximum number of DL MIMO layers compared to non-RedCap UEs. In FR1, one DL MIMO layer is supported if one Rx branch is supported, and two DL MIMO layers are supported if two Rx branches are supported. In FR2, one or two DL MIMO layers can be supported, and two Rx branches are always supported. In FR1 and FR2, UE functions and corresponding capabilities related to more than two UE Rx branches or more than two DL MIMO layers, and UE functions and capabilities related to more than two UE Tx branches or more than two UL MIMO layers, are not supported by RedCap UEs. RedCap UEs may support time division duplex (TDD) or half-duplex frequency division duplex (HD-FDD). With HD-FDD, RedCap UEs can share antennas and radio frequency (RF) components for uplink transmission and downlink reception.

[0035] RedCap UEs in RRC_IDLE and RRC_INACTIVE monitor paging only in the initial DL BWP (default or RedCap specific) associated with CD-SSB and perform cell (re)selection and measurements in CD-SSB. If a RedCap-specific, RedCap-specific or RedCap-only initial UL BWP is configured, RedCap UEs in RRC_IDLE and RRC_INACTIVE use only the RedCap-specific initial UL BWP to perform random access (or RACH).

[0036] The initial DL BWP for RedCap, RedCap-specific, or RedCap-only can be configured with a Type-1 common search space for receiving a PDCCH carrying DCI for random access MSG2, MSGB, and MSG4, i.e., PDSCH. This DCI is in a DCI format with Cyclic Redundancy Check (CRC) bits scrambled with a Random Access Radio Network Temporary Identifier (RA-RNTI). A RedCap UE searches within the Type-1 common search space configured in the initial DL BWP for RedCap to receive DCI / PDCCH indicating the PDSCH carrying MSG2, MSGB, and MSG4, and can receive MSG2, MSGB, and MSG4 based on the received DCI.

[0037] A search space for paging may be configured in an initial DL BWP for RedCap, specific to RedCap, or dedicated to RedCap. However, if the initial DL BWP for RedCap does not include CD-SSB and the entire CORESET#0, a search space for paging is not configured in the initial DL BWP for RedCap. If a search space for paging is not configured in the initial DL BWP for RedCap, RedCap UEs will not receive paging in that DL BWP. In this case, RedCap UEs may receive paging in an initial DL BWP used by normal UEs or non-RedCap UEs, i.e., a non-RedCap specific initial DL BWP.

[0038] The RAN node 1 transmits a first initial BWP configuration and a second initial BWP configuration in SIB1. The first initial BWP configuration includes common or cell-specific common parameters of the first initial BWP of the cell 10. The first initial BWP includes an initial DL BWP and an initial UL BWP. The first initial DL BWP and UL BWP are used by a first type of UE, i.e., normal UEs or non-RedCap UEs, that use the cell 10 as a serving cell. The first initial DL BWP and UL BWP are used by normal UEs or non-RedCap UEs in accessing the cell 10 to transition from RRC_IDLE or RRC_INACTIVE to RRC_CONNECTED. The first initial DL BWP may also be used by normal UEs or non-RedCap UEs to receive paging. In other words, the first initial DL BWP may be configured with a search space for receiving a DCI format with CRC bits scrambled by the Paging RNTI (P-RNTI). As already described, the first initial DL BWP may be used by RedCap UEs to receive paging. In other words, RedCap UEs may receive paging in the first initial DL BWP used by normal UEs or non-RedCap UEs, or in a paging search space within the first initial DL BWP.

[0039] The second initial BWP configuration includes cell-specific common parameters of the second initial BWP of the cell 10. The second initial BWP includes an initial DL BWP and an initial UL BWP. The second initial DL BWP and UL BWP are used by a second type of UE that uses the cell 10 as a serving cell, i.e., RedCap UEs. The second initial DL BWP and UL BWP are used by RedCap UEs in accessing the cell 10 to transition from RRC_IDLE or RRC_INACTIVE to RRC_CONNECTED. In other words, the second initial DL BWP and UL BWP are initial DL BWP and UL BWP for RedCap or specific to RedCap.

[0040] In some implementations, the RAN node 1 may configure multiple second initial DL BWPs and multiple second initial UL BWPs in the cell 10. In other words, the RAN node 1 may configure multiple initial DL BWPs and multiple initial UL BWPs specific or dedicated to RedCap UEs in the cell 10. The following embodiments provide details of how to configure multiple initial DL BWPs and multiple initial UL BWPs specific to RedCap UEs and how they are used by RedCap UEs.

[0041] First Embodiment A configuration example of a wireless communication system according to this embodiment may be the same as the example shown in Fig. 1. This embodiment provides an improvement in signaling between a RAN node 1 and UEs 2.

[0042] 2 shows an example of signaling between RAN node 1 and UE 2. In step 201, RAN node 1 transmits SIB1 to UE 2. In other words, RAN node 1 broadcasts SIB1 in cell 10, and UE 2 receives SIB1. This SIB1 contains configuration information for multiple (second) initial DL BWPs and multiple (second) initial UL BWPs that are specific or dedicated to RedCap UEs. Note that this SIB1 also includes configuration information for a (first) initial DL BWP and a (first) initial UL BWP used by normal UEs or non-RedCap UEs.

[0043] In step 202, if the UE 2 is a RedCap UE, the UE 2 selects one initial DL BWP and one initial UL BWP to be used for random access or initial access to the cell 10 from a plurality of RedCap-specific or dedicated initial DL BWPs and a plurality of initial UL BWPs. The UE 2 transmits a Physical PRACH (PRACH) and a Physical Uplink Shared Channel (PUSCH) related to random access in the selected initial UL BWP. In other words, the UE 2 transmits a random access preamble (MSG1, MSGA) and a PUSCH (MSGA, MSG3) in the selected initial UL BWP. The UE 2 also receives a PDCCH and a PDSCH related to random access, i.e., a RAR (MSG2) and a Contention Resolution (MSG4, MSGB), in the selected initial DL BWP.

[0044] According to the operations described with reference to FIG. 2, the RAN node 1 can provide RedCap specific or dedicated configuration information for multiple initial DL BWPs and multiple initial UL BWPs to UEs 2 in the cell 10 via SIB1, i.e., via broadcast.

[0045] 3 shows an example of the message structure or format of SIB1. SIB1 300 includes a servingCellConfigCommon field, i.e., ServingCellConfigCommonSIB IE 310. ServingCellConfigCommonSIB IE 310 includes a downlinkConfigCommon field, i.e., DownlinkConfigCommonSIB IE 320, and an uplinkConfigCommon field, i.e., UplinkConfigCommonSIB IE 330. DownlinkConfigCommonSIB IE 320 includes a frequencyInfoDL field, i.e., FrequencyInfoDL-SIB IE 321, an initialDownlinkBWP field, i.e., BWP-DownlinkCommon IE 322, and an InitialDownlinkBWPList-RedCap field 323.

[0046] The FrequencyInfoDL-SIB IE 321 provides basic parameters for downlink carriers and transmissions thereon, and indicates one or more frequency bands (specifically, one or more NR frequency band numbers) to which the downlink carriers belong.

[0047] The BWP-DownlinkCommon IE 322 is used to configure common parameters for the (first) initial DL BWP used by normal UEs or non-RedCap UEs. These parameters are "cell specific." The BWP-DownlinkCommon IE 322 includes a pdcch-ConfigCommon field or IE. The pdcch-ConfigCommon field or IE can specify a Type-1 common search space in the ra-SearchSpace field or IE. Specifically, the field or IE includes a commonSearchSpaceList field or IE that specifies one or more common search spaces (CSSs) within the BWP. The commonSearchSpaceList field or IE is a list of up to four SearchSpace IEs. The SearchSpace IE indicates a SearchSpaceId and defines how and where to search for PDCCH candidates.

[0048] The InitialDownlinkBWPList-RedCap field 323 is used to configure common parameters for one or more initial DL BWPs specific to or dedicated to RedCap UEs. These parameters are "cell-specific." The InitialDownlinkBWPList-RedCap field 323 is a list of one or more BWP-DownlinkCommon IEs. The maximum number of initial DL BWPs for RedCap that can be configured for a cell 10 (maxNroinitialDownlinkBWP-RedCap) may be specified in the 3GPP specifications. Similar to the BWP-DownlinkCommon IE 322 described above, each BWP-DownlinkCommon IE includes a pdcch-ConfigCommon field or IE.

[0049] On the other hand, the UplinkConfigCommonSIB IE 330 includes a frequencyInfoUL field, i.e., FrequencyInfoUL-SIB IE 331 , an initialUplinkBWP field, i.e., BWP-UplinkCommon IE 332 , and an InitialUplinkBWPList-RedCap field 333 .

[0050] The FrequencyInfoUL-SIB IE 331 provides basic parameters for an uplink carrier and transmissions thereon, and indicates one or more frequency bands (specifically, one or more NR frequency band numbers) to which the uplink carrier belongs.

[0051] The BWP-UplinkCommon IE 332 is used to configure common parameters for the (first) initial UL BWP used by normal UEs or non-RedCap UEs. These parameters are "cell-specific." The BWP-UplinkCommon IE 332 includes a rach-ConfigCommon field or IE, which indicates the configuration of cell-specific random access parameters that UEs use for contention-based or contention-free random access in this BWP.

[0052] The InitialUplinkBWPList-RedCap field 333 is used to configure common parameters for one or more initial UL BWPs specific to or dedicated to RedCap UEs. These parameters are "cell-specific." The InitialUplinkBWPList-RedCap field 333 is a list of one or more BWP-UplinkCommon IEs. The maximum number of initial UL BWPs for RedCap that can be configured for a cell 10 (maxNroinitialUplinkBWP-RedCap) may be specified in the 3GPP specifications. Similar to the BWP-UplinkCommon IE 332 described above, each BWP-UplinkCommon IE includes a rach-ConfigCommon field or IE. The rach-ConfigCommon field or IE indicates the cell-specific random access parameter configuration that the UEs, i.e., RedCap UEs, use for contention-based or contention-free random access in that BWP.

[0053] 3, SIB1 300 includes configuration information for a (first) initial DL BWP used by normal UEs or non-RedCap UEs (BWP-DownlinkCommon IE 322), and also includes configuration information for one or more (second) initial DL BWPs for RedCap (InitialDownlinkBWPList-RedCap field 323). Similarly, SIB1 300 includes configuration information for a (first) initial UL BWP used by normal UEs or non-RedCap UEs (BWP-UplinkCommon IE 332), and also includes configuration information for one or more (second) initial UL BWPs for RedCap (InitialUplinkBWPList-RedCap field 333).

[0054] FIG. 4 is a conceptual diagram illustrating BWP transition or switching of RedCap UEs. In the example of FIG. 4, two RedCap-specific initial BWPs 431 and 432 are configured in cell 10. FIG. 4 assumes a case where cell 10 operates in the TDD band. Therefore, RedCap-specific initial BWP 431 includes a pair of initial DL BWP and initial UL BWP having the same center frequency. In RedCap-specific initial BWP 431, the bandwidth of the initial DL BWP may be the same as or different from that of the initial UL BWP. Similarly, RedCap-specific initial BWP 432 includes a pair of initial DL BWP and initial UL BWP having the same center frequency. In RedCap-specific initial BWP 432, the bandwidth of the initial DL BWP may be the same as or different from that of the initial UL BWP.

[0055] RedCap UEs in RRC_IDLE or RRC_INACTIVE state decode the MIB in CD-SSB 410 and obtain the configuration of CORESET#0 420 from the MIB. Next, the RedCap UEs perform blind decoding to search for DCI / PDCCH for SIB1 reception in CORESET#0 420. If the blind decoding is successful, the RedCap UEs receive the PDSCH carrying SIB1. Then, the RedCap UEs obtain the configuration of two RedCap-specific initial BWPs 431 and 432 from SIB1.

[0056] The RedCap UEs then select one of two RedCap-specific initial BWPs 431 and 432. One RedCap UE (e.g., RedCap UE A) selects the initial BWP 431, and another RedCap UE (e.g., RedCap UE A) selects the initial BWP 432. The RedCap UEs retune their respective RF components to the center frequency of the selected initial BWP and perform random access or initial access to the cell 10 at the selected initial BWP.

[0057] If the random access is successful, each RedCap UE receives an RRC message (e.g., RRC Setup or RRC Resume) indicating a dedicated BWP configuration from the RAN node 1. The UE-specific BWP configuration includes the configuration of the first active BWP (first active DL BWP and first active UL BWP). The first active BWP is the BWP that the UE should use from the time (or immediately after) the establishment of the RRC connection in the serving cell is completed. Each RedCap UE applies the UE-specific BWP configuration and transitions to RRC_CONNECTED in the configured first active BWP.

[0058] In the example of FIG. 4 , a RedCap UE that successfully achieves random access using the initial BWP 431 uses the first active BWP 441, while a RedCap UE that successfully achieves random access using the initial BWP 432 uses the first active BWP 442. In the example of FIG. 4 , the first active BWP 441 has the same center frequency and bandwidth as the initial BWP 431, and similarly, the first active BWP 442 has the same center frequency and bandwidth as the initial BWP 432. This allows RedCap UEs to continue using the initial BWP as the first active BWP without retuning the RF components. However, this is merely an example. One or both of the center frequency and bandwidth of the first active BWP 441 may be different from those of the initial BWP 431. Similarly, one or both of the center frequency and bandwidth of the first active BWP 442 may be different from those of the initial BWP 432.

[0059] 4 may be modified as follows: The RedCap UE-specific initial BWPs 431 and 432 may have different bandwidths. One of the RedCap UE-specific initial BWPs 431 and 432 may be configured to include CD-SSB 410 and CORESET#0 420.

[0060] Second Embodiment A configuration example of a wireless communication system according to this embodiment may be the same as the example shown in Fig. 1. This embodiment provides various specific examples of initial BWP selection by RedCap UEs. The initial BWP selection described in this embodiment can be applied to the first embodiment, specifically to step 202 in Fig. 2.

[0061] If UE 2 is a RedCap UE, UE 2 may select one initial DL BWP and one initial UL BWP to be used for random access from multiple initial DL BWPs and multiple initial UL BWPs specific to RedCap UEs as follows: In other words, UE 2 may select one pair from multiple pairs of initial DL and DL BWPs as follows:

[0062] In a first example, the UE 2 may randomly select one initial DL BWP and one initial UL BWP.

[0063] In a second example, UE 2 may select one initial DL BWP and one initial UL BWP based on a UE identifier of UE 2. The UE identifier may be, for example, but not limited to, part or all of a Subscription Permanent Identifier (SUPI).

[0064] In a third example, the UE 2 may select one initial DL BWP and one initial UL BWP based on a group identifier assigned by a core network (e.g., 5GC), which may be, for example, but not limited to, a Paging Subgroup ID assigned by an Access and Mobility Management Function (AMF).

[0065] In a fourth example, the UE 2 may select one initial DL BWP and one initial UL BWP based on a measurement of the received power or reception quality of the downlink signal. The received power measurement may be a measurement of Reference Signal Received Power (RSRP) of resources within a CD-SSB. The reception quality measurement may be a measurement of Reference Signal Received Quality (RSRQ) of resources within the CD-SSB.

[0066] More specifically, if the measurement value is equal to or exceeds the first threshold, UE 2 may select the initial DL BWP and initial UL BWP (e.g., initial BWP 432 in FIG. 4) that are closest to CD-SSB (e.g., CD-SSB 410 in FIG. 4) in the frequency domain for use in random access. If the measurement value is equal to or exceeds the first threshold, it means that the reception quality of CD-SSB is relatively good. Therefore, by selecting the initial DL BWP and initial UL BWP whose frequency locations are closer to CD-SSB, better communication quality can be expected in random access between RAN node 1 and UE 2. On the other hand, if the measurement value is below a second threshold equal to or lower than the first threshold, UE 2 may select the initial DL BWP and initial UL BWP (e.g., initial BWP 431 in FIG. 4) that are farthest from CD-SSB (e.g., CD-SSB 410 in FIG. 4) in the frequency domain for use in random access. If the measurement value is below the second threshold, it means that the reception quality of CD-SSB is relatively poor. Therefore, by selecting the initial DL BWP and initial UL BWP whose frequency location is farther from CD-SSB, it can be expected that the communication quality of the selected initial DL BWP and initial UL BWP will be better than other pairs closer to NCD-SSB.

[0067] The second threshold may be set lower than the first threshold. In this case, if the measurement value is between the first and second thresholds, the UE 2 may randomly select the initial DL BWP and initial UL BWP to be used for random access. The first threshold, or the first and second thresholds, may be broadcast in the cell 10 by the network (e.g., RAN node 1). The first threshold, or the first and second thresholds, may be included in SIB1.

[0068] In a fifth example, UE 2 utilizes the received power or received quality of resources in each of a plurality of Non-Cell Defining (NCD) SSBs, each of which is included in a respective one of a plurality of initial DL BWPs. Figure 5 shows an example of the operation of UE 2 in the fifth example. In step 501, UE 2 measures the received power or received quality of resources in each of a plurality of NCD-SSBs, each of which is included in a respective one of a plurality of initial DL BWPs. In step 502, UE 2 selects an initial DL BWP and an initial UL BWP to be used for random access based on a comparison between the received power or received quality measurements.

[0069] NCD-SSBs are not associated with an RMSI (or SIB1). Resources within NCD-SSBs transmit downlink signals, such as the PBCH Demodulation Reference Signal (DMRS), that can be used for measuring downlink received power or quality.

[0070] For example, the UE 2 may select a pair of an initial DL BWP and a corresponding initial UL BWP that have the best measured received power or received quality of the resources in the NCD-SSB, and use them for random access, which is expected to improve the communication quality during random access between the RAN node 1 and the UE 2.

[0071] Alternatively, the UE 2 may select a pair of an initial DL BWP and a corresponding initial UL BWP for which the measured value of the received power or the received quality of the resource in the NCD-SSB exceeds a threshold. If multiple BWP pairs exceed the threshold, the UE 2 may select any one of these multiple BWP pairs. Such a selection operation can also contribute to improving the communication quality in random access between the RAN node 1 and the UE 2.

[0072] In the fifth example, UE 2 needs to obtain configuration information of NCD-SSBs included in RedCap specific initial DL BWPs. RAN node 1 may provide the NCD-SSB configuration information to UE 2 via SIB1. In other words, SIB1 may include the configuration information of NCD-SSBs included in RedCap specific initial DL BWPs.

[0073] 6 shows an example of signaling between RAN node 1 and UE 2 for the fifth example. In step 601, RAN node 1 transmits SIB1 to UE 2. In other words, RAN node 1 broadcasts SIB1 in cell 10, and UE 2 receives SIB1. This SIB1 includes configuration information for multiple (second) initial DL BWPs and multiple (second) initial UL BWPs that are specific or dedicated to RedCap UEs. Furthermore, this SIB1 includes configuration information for multiple NCD-SSBs, each of which is included in each of the RedCap-specific initial DL BWPs.

[0074] In step 602, UE2 compares the received power or quality measurements for resources in the NCD-SSBs and, based on the comparison, selects an initial DL BWP and an initial UL BWP to use for random access (or initial access).

[0075] Figure 7 shows an example of the message structure or format of SIB1 sent in step 601. SIB1 700 has a basic structure similar to SIB1 300 shown in Figure 3. Specifically, fields or IEs 710, 720, 721, 722, 723, 730, 731, 732, and 733 shown in Figure 7 correspond to or are similar to fields or IEs 310, 320, 321, 322, 323, 330, 331, 332, and 333 shown in Figure 3, respectively.

[0076] However, the InitialDownlinkBWP-RedCap field 723 includes an InitialDownlinkBWPList-RedCap field 724 similar to the InitialDownlinkBWPList-RedCap field 323 of Figure 3. In addition, the InitialDownlinkBWP-RedCap field 723 includes a NonCellDefiningSSBList field 725.

[0077] The NonCellDefiningSSBList field 725 is used to configure common parameters of one or more initial DL BWPs specific or dedicated to RedCap UEs. These parameters are "cell-specific." The NonCellDefiningSSBList field 725 is a list of one or more NonCellDefiningSSB IEs. The maximum number of RedCap initial DL BWPs (maxNroinitialDownlinkBWP-RedCap) that can be configured for a cell 10 may be specified in the 3GPP specifications. The NonCellDefiningSSB IE indicates the configuration of one or more NCD-SSBs included in one or more RedCap-specific initial DL BWPs indicated in the InitialDownlinkBWPList-RedCap field 323.

[0078] Next, a description will be given below of configuration examples of the RAN node 1 and the UE 2 according to the above-described embodiments. Fig. 8 is a block diagram showing a configuration example of the RAN node 1 according to the above-described embodiments.

[0079] Referring to FIG. 8, the RAN node 1 includes a Radio Frequency (RF) transceiver 801, a network interface 803, a processor 804, and a memory 805. The RF transceiver 801 performs analog RF signal processing for communication with UEs. The RF transceiver 801 may include multiple transceivers. The RF transceiver 801 is coupled to an antenna array 802 and a processor 804. The RF transceiver 801 receives modulation symbol data from the processor 804, generates a transmit RF signal, and provides the transmit RF signal to the antenna array 802. The RF transceiver 801 also generates a baseband receive signal based on the receive RF signal received by the antenna array 802 and provides the baseband receive signal to the processor 804. The RF transceiver 801 may include an analog beamformer circuit for beamforming. The analog beamformer circuit may include, for example, multiple phase shifters and multiple power amplifiers.

[0080] The network interface 803 is used to communicate with network nodes (e.g., other RAN nodes, and control plane nodes and user plane nodes of the core network), and may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.

[0081] The processor 804 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. The processor 804 may include multiple processors. For example, the processor 804 may include a modem processor (e.g., a Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., a Central Processing Unit (CPU) or a Micro Processing Unit (MPU)) that performs control plane processing.

[0082] For example, digital baseband signal processing by the processor 804 may include signal processing for the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer. Control plane processing by the processor 804 may also include processing of Non-Access Stratum (NAS) messages, RRC messages, Medium Access Control (MAC) Control Elements (CEs), and Downlink Control Information (DCI). Control plane processing by the processor 804 may also include processing of application layer signaling protocols such as XnAP, F1AP, and NGAP.

[0083] The processor 804 may include a digital beamformer module for beamforming, which may include a Multiple Input Multiple Output (MIMO) encoder and precoder.

[0084] The memory 805 is configured by a combination of volatile memory and non-volatile memory. The volatile memory is, for example, Static Random Access Memory (SRAM), Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is, for example, Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof. The memory 805 may include storage located remotely from the processor 804. In this case, the processor 804 may access the memory 805 via the network interface 803 or an I / O interface.

[0085] The memory 805 may store one or more software modules (computer programs) 806 including instructions and data for performing the processes of the RAN node 1 described in the above embodiments. In some implementations, the processor 804 may be configured to read and execute the software modules 806 from the memory 805 to perform the processes of the RAN node 1 described in the above embodiments.

[0086] It should be noted that if the RAN node 1 is a Central Unit (CU) (e.g., eNB-CU or gNB-CU) or a CU-CP, the RAN node 1 may not include the RF transceiver 801 (and the antenna array 802).

[0087] FIG. 9 is a block diagram showing an example configuration of a UE 2. An RF transceiver 901 performs analog RF signal processing for communication with a RAN node. The RF transceiver 901 may include multiple transceivers. The analog RF signal processing performed by the RF transceiver 901 includes frequency up-conversion, frequency down-conversion, and amplification. The RF transceiver 901 is coupled to an antenna array 902 and a baseband processor 903. The RF transceiver 901 receives modulation symbol data (or OFDM symbol data) from the baseband processor 903, generates a transmit RF signal, and provides the transmit RF signal to the antenna array 902. The RF transceiver 901 also generates a baseband receive signal based on the receive RF signal received by the antenna array 902 and provides the baseband receive signal to the baseband processor 903. The RF transceiver 901 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.

[0088] The baseband processor 903 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) transmission format (transmission frame) generation / decomposition, (d) transmission path coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) using Inverse Fast Fourier Transform (IFFT). Meanwhile, control plane processing includes communication management for Layer 1 (e.g., transmit power control), Layer 2 (e.g., radio resource management and hybrid automatic repeat request (HARQ) processing), and Layer 3 (e.g., signaling related to attachment, mobility, and call management).

[0089] For example, the digital baseband signal processing by the baseband processor 903 may include signal processing of an SDAP layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer. Also, the control plane processing by the baseband processor 903 may include processing of a Non-Access Stratum (NAS) protocol, an RRC protocol, MAC CEs, and DCIs.

[0090] The baseband processor 903 may perform MIMO encoding and precoding for beamforming.

[0091] The baseband processor 903 may include a modem processor (e.g., DSP) that performs digital baseband signal processing and a protocol stack processor (e.g., CPU or MPU) that performs control plane processing. In this case, the protocol stack processor that performs control plane processing may be shared with the application processor 904, which will be described later.

[0092] The application processor 904 is also referred to as a CPU, MPU, microprocessor, or processor core. The application processor 904 may include multiple processors (multiple processor cores). The application processor 904 executes a system software program (operating system (OS)) and various application programs (e.g., a calling application, a web browser, a mailer, a camera operation application, and a music playback application) read from the memory 906 or a memory not shown, thereby realizing various functions of the UE 2.

[0093] In some implementations, the baseband processor 903 and the application processor 904 may be integrated on a single chip, as indicated by the dashed line (905) in Figure 9. In other words, the baseband processor 903 and the application processor 904 may be implemented as a single System on Chip (SoC) device 905. An SoC device may also be called a system Large Scale Integration (LSI) or chipset.

[0094] The memory 906 is volatile memory, nonvolatile memory, or a combination thereof. The memory 906 may include multiple physically independent memory devices. The volatile memory may be, for example, SRAM, DRAM, or a combination thereof. The nonvolatile memory may be MROM, EEPROM, flash memory, a hard disk drive, or any combination thereof. For example, the memory 906 may include an external memory device accessible from the baseband processor 903, the application processor 904, and the SoC 905. The memory 906 may also include an internal memory device integrated within the baseband processor 903, the application processor 904, or the SoC 905. Furthermore, the memory 906 may include memory within a Universal Integrated Circuit Card (UICC).

[0095] The memory 906 may store one or more software modules (computer programs) 907 including instructions and data for performing the processing by the UE 2 described in the above-described embodiments. In some implementations, the baseband processor 903 or the application processor 904 may be configured to read and execute the software modules 907 from the memory 906 to perform the processing by the UE 2 described in the above-described embodiments using the drawings.

[0096] It should be noted that the control plane processing and operations performed by the UE 2 described in the above embodiment can be realized by elements other than the RF transceiver 901 and the antenna array 902, namely, at least one of the baseband processor 903 and the application processor 904, and the memory 906 storing the software module 907.

[0097] As described with reference to Figures 8 and 9, each of the processors included in the RAN node 1 and the UE 2 according to the above-described embodiments can execute one or more programs including instructions for causing a computer to perform the algorithms described with reference to the drawings. The programs include instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The programs may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable media or tangible storage media include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disk (DVD), Blu-ray disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The programs may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable media or communication media include electrical, optical, acoustic, or other forms of propagated signals.

[0098] Furthermore, the above-described embodiments are merely examples of application of the technical ideas obtained by the inventors of the present invention. In other words, the technical ideas are not limited to the above-described embodiments, and various modifications are possible.

[0099] For example, some or all of the above embodiments may also be described as, but are not limited to, the following appendices. Some or all of the elements (e.g., configurations and functions) described in appendices directed to apparatuses (e.g., UEs and RAN nodes) may naturally also be described as appendices directed to methods and programs. For example, some or all of the elements described in appendices 2-14, which are dependent on appendices 1-14, may also be described as appendices dependent on appendices 15 and 16, due to the same dependency relationship as appendices 2-14. Some or all of the elements described in any appendice may be applied to various hardware, software, recording means for recording software, systems, and methods.

[0100] (Supplementary Note 1) User Equipment (UE) comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to receive a System Information Block Type 1 (SIB1) including configuration information of a plurality of initial downlink (DL) bandwidth parts (BWPs) and a plurality of initial uplink (UL) BWPs specific to a particular type of UE, and select one initial DL BWP and one initial UL BWP to be used for random access from the plurality of initial DL BWPs and the plurality of initial UL BWPs. (Supplementary Note 2) The UE of Supplementary Note 1, wherein the at least one processor is configured to randomly select the one initial DL BWP and the one initial UL BWP. (Supplementary Note 3) The UE of Supplementary Note 1, wherein the at least one processor is configured to select the one initial DL BWP and the one initial UL BWP based on a UE identifier. (Supplementary Note 4) The UE of Supplementary Note 1, wherein the at least one processor is configured to select the one initial DL BWP and the one initial UL BWP based on a group identifier assigned by a core network. (Supplementary Note 5) The UE of Supplementary Note 4, wherein the group identifier is a Paging Subgroup ID. (Supplementary Note 6) The UE of Supplementary Note 1, wherein the at least one processor is configured to select the one initial DL BWP and the one initial UL BWP based on a measurement of received power or received quality of a downlink signal.(Supplementary Note 7) The UE according to Supplementary Note 6, wherein the measured value of received power is a measured value of Reference Signal Received Power (RSRP) of resources within a Cell Defining (CD) Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block (SSB), and the measured value of received quality is a measured value of Reference Signal Received Quality (RSRQ) of resources within the CD-SSB. (Supplementary Note 8) The UE according to Supplementary Note 7, wherein the at least one processor is configured to: select an initial DL BWP and an initial UL BWP closest to the CD-SSB in the frequency domain as the one initial DL BWP and the one initial UL BWP if the measurement value exceeds a first threshold, and select an initial DL BWP and an initial UL BWP farthest from the CD-SSB in the frequency domain as the one initial DL BWP and the one initial UL BWP if the measurement value is below a second threshold that is equal to or lower than the first threshold. (Supplementary Note 9) The UE according to Supplementary Note 8, wherein the second threshold is lower than the first threshold, and the at least one processor is configured to randomly select the one initial DL BWP and the one initial UL BWP if the measurement value is between the first threshold and the second threshold. (Supplementary Note 10) The UE of Supplementary Note 1, wherein the at least one processor is configured to: measure received power or received quality of resources in each of a plurality of Non-Cell Defining (NCD) Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) blocks (SSBs), each of which is included in a respective one of the plurality of initial DL BWPs; and select the one initial DL BWP and the one initial UL BWP based on a comparison between the measured values ​​of received power or received quality.(Supplementary Note 11) The UE according to Supplementary Note 10, wherein the at least one processor is configured to select, as the one initial DL BWP and the one initial UL BWP, a pair of an initial DL BWP and a corresponding initial UL BWP, for which a measurement value of received power or received quality of a resource in an NCD-SSB is best. (Supplementary Note 12) The UE according to Supplementary Note 10, wherein the at least one processor is configured to select, as the one initial DL BWP and the one initial UL BWP, a pair of an initial DL BWP and a corresponding initial UL BWP, for which a measurement value of received power or received quality of a resource in an NCD-SSB exceeds a threshold. (Supplementary Note 13) The UE according to any one of Supplements 10 to 12, wherein the SIB1 includes configuration information of the plurality of NCD-SSBs. (Supplementary Note 14) The UE according to any one of Supplements 1 to 13, wherein the specific type of UE is a Reduced Capability (RedCap) UE. (Supplementary Note 15) A method performed by User Equipment, comprising: receiving a System Information Block Type 1 (SIB1) containing configuration information of a plurality of initial downlink (DL) bandwidth parts (BWPs) and a plurality of initial uplink (UL) BWPs specific to a particular type of UE; and selecting one initial DL BWP and one initial UL BWP to be used for random access from the plurality of initial DL BWPs and the plurality of initial UL BWPs.and (Supplementary Note 16) A program for causing a computer to perform a method for User Equipment, the method comprising: receiving a System Information Block Type 1 (SIB1) including configuration information of a plurality of initial downlink (DL) bandwidth parts (BWPs) and a plurality of initial uplink (UL) BWPs specific to a particular type of UE; and selecting one initial DL BWP and one initial UL BWP to be used for random access from the plurality of initial DL BWPs and the plurality of initial UL BWPs. (Supplementary Note 17) A Radio Access Network (RAN) node, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to transmit a System Information Block Type 1 (SIB1) including configuration information of a plurality of initial downlink (DL) bandwidth parts (BWPs) and a plurality of initial uplink (UL) BWPs specific to a particular type of User Equipment (UE). (Supplementary Note 18) The RAN node of Supplementary Note 17, wherein the configuration information causes the specific type of UE to select one initial DL BWP and one initial UL BWP to be used for random access from the plurality of initial DL BWPs and the plurality of initial UL BWPs. (Supplementary Note 19) The RAN node of Supplementary Note 18, wherein the configuration information causes the specific type of UE to randomly select the one initial DL BWP and the one initial UL BWP. (Supplementary Note 20) The RAN node of Supplementary Note 18, wherein the configuration information causes the specific type of UE to select the one initial DL BWP and the one initial UL BWP based on a UE identifier.(Supplementary Note 21) The RAN node of Supplementary Note 18, wherein the configuration information causes the UE of the specific type to select the one initial DL BWP and the one initial UL BWP based on a group identifier assigned by a core network. (Supplementary Note 22) The RAN node of Supplementary Note 21, wherein the group identifier is a Paging Subgroup ID. (Supplementary Note 23) The RAN node of Supplementary Note 18, wherein the configuration information causes the UE of the specific type to select the one initial DL BWP and the one initial UL BWP based on a measurement of received power or received quality of a downlink signal. (Supplementary Note 24) The RAN node according to Supplementary Note 23, wherein the measured received power is a measured Reference Signal Received Power (RSRP) of resources within a Cell Defining (CD) Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block (SSB), and the measured received quality is a measured Reference Signal Received Quality (RSRQ) of resources within the CD-SSB. (Supplementary Note 25) The RAN node of Supplementary Note 24, wherein the configuration information causes the specific type of UE to: select initial DL BWP and initial UL BWP closest to the CD-SSB in the frequency domain as the one initial DL BWP and the one initial UL BWP if the measurement value exceeds a first threshold; and select initial DL BWP and initial UL BWP farthest from the CD-SSB in the frequency domain as the one initial DL BWP and the one initial UL BWP if the measurement value is below a second threshold that is equal to or lower than the first threshold. (Supplementary Note 26) The RAN node of Supplementary Note 25, wherein the second threshold is lower than the first threshold; and the configuration information causes the specific type of UE to randomly select the one initial DL BWP and the one initial UL BWP if the measurement value is between the first threshold and the second threshold.(Supplementary Note 27) The RAN node of Supplementary Note 18, wherein the configuration information causes the specific type of UE to: measure received power or received quality of resources in each of a plurality of Non-Cell Defining (NCD) Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) blocks (SSBs), each of which is included in a respective one of the plurality of initial DL BWPs; and select the one initial DL BWP and the one initial UL BWP based on a comparison between the measured values ​​of received power or received quality. (Supplementary Note 28) The RAN node of Supplementary Note 27, wherein the configuration information causes the specific type of UE to select, as the one initial DL BWP and the one initial UL BWP, a pair of an initial DL BWP and a corresponding initial UL BWP having the best measured value of received power or received quality of resources in an NCD-SSB. (Supplementary Note 29) The RAN node according to Supplementary Note 27, wherein the configuration information causes the specific type of UE to select, as the one initial DL BWP and the one initial UL BWP, a pair of any initial DL BWP and a corresponding initial UL BWP, for which a measurement value of received power or received quality of a resource in an NCD-SSB exceeds a threshold. (Supplementary Note 30) The RAN node according to any one of Supplements 27 to 29, wherein the SIB1 includes configuration information of the plurality of NCD-SSBs. (Supplementary Note 31) The RAN node according to any one of Supplements 17 to 30, wherein the specific type of UE is a Reduced Capability (RedCap) UE. (Supplementary Note 32) A method performed by a Radio Access Network (RAN) node, comprising transmitting a System Information Block Type 1 (SIB1) containing configuration information for a plurality of initial downlink (DL) bandwidth parts (BWPs) and a plurality of initial uplink (UL) BWPs specific to a particular type of User Equipment (UE).(Supplementary Note 33) A program for causing a computer to perform a method for a radio access network (RAN) node, the method comprising transmitting a System Information Block Type 1 (SIB1) containing configuration information for a plurality of initial downlink (DL) bandwidth parts (BWPs) and a plurality of initial uplink (UL) BWPs specific to a particular type of User Equipment (UE).

[0101] This application claims priority based on Japanese Patent Application No. 2022-139336, filed September 1, 2022, the disclosure of which is incorporated herein in its entirety.

[0102] 1 RAN node 2 UE 804 Processor 805 Memory 806 Modules 903 Baseband processor 904 Application processor 906 Memory 907 Modules

Claims

1. A User Equipment (UE), A means for receiving a System Information Block Type 1 (SIB1) including configuration information of a plurality of initial downlink (DL) bandwidth part (BWPs) and a plurality of initial uplink (UL) BWPs specific to a particular type of UE; means for selecting one initial DL BWP and one initial UL BWP to be used for random access from the plurality of initial DL BWPs and the plurality of initial UL BWPs; A UE equipped with

2. The selecting means is configured to randomly select the one initial DL BWP and the one initial UL BWP. The UE of claim 1.

3. The selecting means is configured to select the one initial DL BWP and the one initial UL BWP based on a UE identifier. The UE of claim 1.

4. The selecting means is configured to select the one initial DL BWP and the one initial UL BWP based on a group identifier assigned by a core network. The UE of claim 1.

5. The selecting means is configured to select the one initial DL BWP and the one initial UL BWP based on a measurement of a received power or a received quality of a downlink signal. The UE of claim 1.

6. The measurement value of the received power is a measurement value of Reference Signal Received Power (RSRP) of a resource in a Cell Defining (CD) Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block (SSB); The measurement value of the reception quality is a measurement value of Reference Signal Received Quality (RSRQ) of the resource in the CD-SSB; The UE of claim 5.

7. The means for selecting includes: If the measurement value exceeds a first threshold, selecting an initial DL BWP and an initial UL BWP that are closest to the CD-SSB in the frequency domain as the one initial DL BWP and the one initial UL BWP; If the measurement value is below a second threshold value that is equal to or lower than the first threshold value, select an initial DL BWP and an initial UL BWP that are farthest from the CD-SSB in the frequency domain as the one initial DL BWP and the one initial UL BWP; It is configured as follows: The UE according to claim 6.

8. A method performed by User Equipment, comprising: receiving a System Information Block Type 1 (SIB1) containing configuration information for a number of initial downlink (DL) bandwidth part (BWPs) and a number of initial uplink (UL) BWPs specific to a particular type of UE; and selecting one initial DL BWP and one initial UL BWP to be used for random access from the plurality of initial DL BWPs and the plurality of initial UL BWPs; A method for providing the above.

9. A program for causing a computer to perform a method for User Equipment, The method comprises: receiving a System Information Block Type 1 (SIB1) containing configuration information for a number of initial downlink (DL) bandwidth part (BWPs) and a number of initial uplink (UL) BWPs specific to a particular type of UE; and selecting one initial DL BWP and one initial UL BWP from the plurality of initial DL BWPs and the plurality of initial UL BWPs to be used for random access; A program that includes:

10. 1. A Radio Access Network (RAN) node, comprising: means for transmitting a System Information Block Type 1 (SIB1) including configuration information of a plurality of initial downlink (DL) bandwidth parts (BWPs) and a plurality of initial uplink (UL) BWPs specific to a particular type of User Equipment (UE); RAN node.