WO2021161622A1 - Ranノード、無線端末、及びこれらのための方法 - Google Patents
Ranノード、無線端末、及びこれらのための方法 Download PDFInfo
- Publication number
- WO2021161622A1 WO2021161622A1 PCT/JP2020/044537 JP2020044537W WO2021161622A1 WO 2021161622 A1 WO2021161622 A1 WO 2021161622A1 JP 2020044537 W JP2020044537 W JP 2020044537W WO 2021161622 A1 WO2021161622 A1 WO 2021161622A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- initial bwp
- initial
- bwp
- cell
- type
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 81
- 230000011664 signaling Effects 0.000 claims abstract description 27
- 230000004044 response Effects 0.000 claims description 34
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 36
- 238000004891 communication Methods 0.000 description 17
- 230000005540 biological transmission Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 15
- 238000012546 transfer Methods 0.000 description 12
- 230000007704 transition Effects 0.000 description 12
- 101100274486 Mus musculus Cited2 gene Proteins 0.000 description 5
- 101150096622 Smr2 gene Proteins 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 102100035354 Guanine nucleotide-binding protein G(I)/G(S)/G(T) subunit beta-1 Human genes 0.000 description 4
- 101001024316 Homo sapiens Guanine nucleotide-binding protein G(I)/G(S)/G(T) subunit beta-1 Proteins 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 101100533725 Mus musculus Smr3a gene Proteins 0.000 description 3
- 101100411667 Arabidopsis thaliana RAN4 gene Proteins 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- UDHXJZHVNHGCEC-UHFFFAOYSA-N Chlorophacinone Chemical compound C1=CC(Cl)=CC=C1C(C=1C=CC=CC=1)C(=O)C1C(=O)C2=CC=CC=C2C1=O UDHXJZHVNHGCEC-UHFFFAOYSA-N 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000003321 amplification Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 239000013256 coordination polymer Substances 0.000 description 1
- 238000013144 data compression Methods 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008450 motivation Effects 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000000153 supplemental effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
- H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access, e.g. scheduled or random access
- H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
- H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
- H04L5/0092—Indication of how the channel is divided
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
Definitions
- This disclosure relates to wireless communication networks, especially bandwidth part (BWP) settings.
- BWP bandwidth part
- Reduced capability NR devices is also called low complexity NR devices or NR-Light devices.
- the main motivation for Reduced capability NR devices is device cost and complexity compared to high-end enhanced Mobile Broad Band (eMBB) and Ultra Reliable and Low Latency Communication (URLLC) devices (User Equipments (UEs)). complexity) is to be lowered.
- eMBB enhanced Mobile Broad Band
- URLLC Ultra Reliable and Low Latency Communication
- UEs User Equipments
- complexity Radio Frequency
- RF Radio Frequency
- reduced capability NR devices are expected to have reduced UE bandwidth capabilities compared to eMBB and URLLC devices.
- 5GUE needs to receive Minimum System Information (SI) when performing initial access.
- system information System Information (SI)
- MIB Master Information Block
- SIBs System Information Blocks
- SIBs System Information Blocks
- SIB1 SIB type 1
- SIB2 SIB types after SIB type 2
- the MIB is periodically transmitted on Broadcast Channel (BCH) and Physical Broadcast Channel (PBCH).
- BCH Broadcast Channel
- PBCH Physical Broadcast Channel
- the MIB contains information about cell barring and further contains the essential physical layer information of the cell needed to decode SIB1. More specifically, the MIB decodes SystemFrameNumber (SFN), subCarrierSpacingCommon for SIB1, ssb-SubcarrierOffset indicating the position of SS / PBCHblock (SSB) in the frequency domain, and SIB1.
- SFN SystemFrameNumber
- SSB ssb-SubcarrierOffset indicating the position of SS / PBCHblock (SSB) in the frequency domain
- SIB1 Physical Downlink Control Channel
- the pdcch-ConfigSIB1 field (PDCCH-ConfigSIB1 information element) of the MIB contains the settings of Common Resource Set (CORESET) # 0 and common search space (search space # 0).
- the UE can use the controlResourceSetZero field (ControlResourceSetZero information element) in the pdcch-ConfigSIB1 field of the MIB, the CORESET of the Type0-PDCCH common search space (CSS) set, and the continuous resource blocks (a number of consistent resource blocks) and Determine consecutive symbols (a number of consistent symbols).
- the UE determines PDCCH monitoring occurrences from the searchSpaceZero field (SearchSpaceZero information element) in the pdcch-ConfigSIB1 field of the MIB. Then, the UE tries to receive the downlink control information (Downlink Control Information (DCI)) in the determined common search space # 0 (Type0-PDCCH search space).
- the DCI indicates the allocation of the Physical Downlink Shared Channel (PDSCH) resource to which SIB1 is transmitted.
- DCI Downlink Control Information
- SIB1 is also called Remaining Minimum SI (RMSI). SIB1 is periodically transmitted on the Downlink Shared Channel (DL-SCH) and the Physical Downlink Shared Channel (PDSCH). SIB1 contains the information required for initial access. SIB1 further indicates the availability and scheduling (e.g., periodicity and SI window size) of Other SI (Other SIBs). SIB1 further indicates whether Other SIBs are provided via periodic broadcasts or on-demand basis.
- RMSI Remaining Minimum SI
- SIB1 is periodically transmitted on the Downlink Shared Channel (DL-SCH) and the Physical Downlink Shared Channel (PDSCH). SIB1 contains the information required for initial access. SIB1 further indicates the availability and scheduling (e.g., periodicity and SI window size) of Other SI (Other SIBs). SIB1 further indicates whether Other SIBs are provided via periodic broadcasts or on-demand basis.
- SIB1 includes cell-specific serving cell settings (i.e., servingCellConfigCommon field (ServingCellConfigCommonSIB information element)).
- the cell-specific serving cell setting is common to UEs that perform initial access.
- Cell-specific serving cell settings include initial Downlink (DL) bandwidth part (BWP) settings (ie, initialDownlinkBWP field (BWP-DownlinkCommon information element)) and initial ULBWP settings (ie, initialUplinkBWP field (BWP-UplinkCommon information element)). DL) bandwidth part (BWP) settings (ie, initialDownlinkBWP field (BWP-DownlinkCommon information element)) and initial ULBWP settings (ie, initialUplinkBWP field (BWP-UplinkCommon information element)). ..
- BWP bandwidth part
- the initial DL BWP settings broadcast on SIB1 include cell-specific parameters of the initial DL BWP of the serving cell that support Physical Uplink Control Channel (PUCCH) transmission and contention-based random access.
- the common parameter includes parameters indicating the frequency domain position and bandwidth of the initial DL BWP (locationAndBandwidth field in the genericParameters field (BWP information element) in the i.e., BWP-DownlinkCommon information element).
- the common parameter further includes a PDCCH parameter (i.e., pdcch-ConfigCommon field (PDCCH-ConfigCommon information element)).
- the PDCCH parameter sets one or more common search spaces in the initial DL BWP used to send the DCI format indicating the PDSCH resource on which the SIB is broadcast.
- the initial UL BWP settings broadcast on SIB1 include cell-specific parameters of the initial UL BWP of the serving cell that support PUCCH transmission and contention-based random access.
- the common parameters include parameters indicating the frequency domain position and bandwidth of the initial UL BWP (locationAndBandwidth field in the genericParameters field (BWP information element) in the i.e., BWP-UplinkCommon information element).
- the common parameter includes a PUCCH parameter (i.e., pucch-ConfigCommon field (PUCCH-ConfigCommon information element)).
- the PUCCH parameter sets a cell-specific PUCCH parameter / resource set (a set of cell-specific PUCCH resources / parameters). The UE will use these PUCCH resources until a dedicated PUCCH setting is provided on the initial initial uplink BWP.
- the common parameters further include cell-specific random access parameters that UEs use for contention-based random access in the initial UL BWP.
- the network sets at least one initial DL BWP and one or two initial UL BWP (when Supplemental Uplink (SUL) is used).
- the network can configure additional DL BWPs and UL BWPs for serving cells UE individually.
- the initial DL and UL BWPs are the DL and UL BWPs used by the UEs for initial access, and the UEs keep the initial DL and UL BWPs until they receive the dedicated BWP settings. use.
- initial BWP initial BWP
- initial BWP is used for convenience of explanation.
- initial BWP is used to refer to one or both of the initial DL BWP and the initial UL BWP.
- the parameters of the initial BWP are broadcast via SIB1. Therefore, the common parameters (e.g., frequency domain position and bandwidth) of PCell's initial BWP are cell-specific and are common to UEs that perform initial access in the PCell.
- the bandwidth of the initial BWP for normal UEs e.g., eMBB and URLCC devices
- Patent Document 1 discloses that the base station sets the PDCCH region to a different bandwidth for each UE according to the UE capability (see, for example, FIG. 7 and paragraphs 0032 to 0033 and 0037). ). Further, in Patent Document 2, when the base station receives the terminal capability information (UE capability) from the UE and determines that the UE can receive a relatively narrow bandwidth, the notification channel has the relatively narrow bandwidth. Is disclosed to notify the UE of the relatively narrow bandwidth information by means of a synchronization signal (see, for example, paragraph 0067). However, Patent Document 1 and Patent Document 2 do not disclose the initial BWP setting.
- UE capability terminal capability information
- One of the objectives to be achieved by the embodiments disclosed herein is an initial BWP in which a second type wireless terminal having a limited capability compared to that of a first type wireless terminal is suitable for that capability.
- the Radio Access Network (RAN) node includes at least one memory and at least one processor coupled to the at least one memory.
- the at least one processor is configured to broadcast the first initial bandwidth part (BWP) setting via system information. Further, the at least one processor is configured to broadcast the second initial BWP configuration via the system information or transmit via signaling for each wireless terminal.
- the first initial BWP setting includes cell-specific common parameters of the first initial BWP of the cell.
- the second initial BWP setting includes cell-specific common parameters of the second initial BWP of the cell.
- the first initial BWP is used by at least the first type of wireless terminal that performs contention-based random access in the cell.
- the second initial BWP is not used by the first type of radio terminal, has a limited capability as compared to that of the first type of radio terminal, and is contention-based in the cell. Used by a second type of wireless terminal with random access.
- the bandwidth of the second initial BWP is equal to or narrower than the bandwidth of the first initial BWP.
- the wireless terminal comprises at least one memory and at least one processor coupled to said at least one memory.
- the at least one processor is configured to receive system information including a first initial bandwidth part (BWP) setting. Further, the at least one processor is configured to receive the second initial BWP setting via the system information or via signaling of the wireless terminal individual and use the second initial BWP setting.
- the first initial BWP setting includes cell-specific common parameters of the first initial BWP of the serving cell of the wireless terminal.
- the second initial BWP setting includes cell-specific common parameters of the second initial BWP of the serving cell.
- the first initial BWP is used by at least the first type of wireless terminal that performs contention-based random access in the serving cell.
- the second initial BWP is not used by the first type of radio terminal, has a limited capability as compared to that of the first type of radio terminal, and is contention-based in the serving cell. Used by a second type of wireless terminal with random access.
- the bandwidth of the second initial BWP is equal to or narrower than the bandwidth of the first initial BWP.
- the method performed by the Radio Access Network (RAN) node includes the following steps: (A) The first initial bandwidth part (BWP) setting is broadcast via system information, and (b) the second initial BWP setting is broadcast via the system information or individual wireless terminals. Sending via signaling.
- BWP bandwidth part
- the method performed by the wireless terminal comprises the following steps: (A) Receiving system information including the first initial bandwidth part (BWP) setting, (B) Receive the second initial BWP setting via the system information or via the signaling of the wireless terminal individually, and (c) use the second initial BWP setting.
- the program includes an instruction group (software code) for causing the computer to perform the method according to the third or fourth aspect described above when read by the computer.
- a device a method that enables a second type wireless terminal having a limited capability as compared to that of the first type wireless terminal to use an initial BWP suitable for that capability.
- And programs can be provided.
- the plurality of embodiments described below can be implemented independently or in combination as appropriate. These plurality of embodiments have novel features that differ from each other. Therefore, these plurality of embodiments contribute to solving different purposes or problems, and contribute to different effects.
- the plurality of embodiments shown below will be described mainly for the 3rd Generation Partnership Project (3GPP) 5th generation mobile communication system (5G system (5GS)). However, these embodiments may be applied to other cellular communication systems that support multiple types of wireless terminals and support initial BWPs similar to 5GS.
- 3GPP 3rd Generation Partnership Project
- 5GS 5th generation mobile communication system
- these embodiments may be applied to other cellular communication systems that support multiple types of wireless terminals and support initial BWPs similar to 5GS.
- FIG. 1 shows a configuration example of a wireless communication network (ie, 5GS) according to some embodiments including the present embodiment.
- the radio communication network includes a radio access network (RAN) node (ie, gNB) 1 and one or more radio terminals (ie, UEs) 2.
- RAN radio access network
- gNB1 is arranged in RAN (ie, Next Generation (NG) RAN).
- gNB1 may include a gNB Central Unit (gNB-CU) and one or more gNB Distributed Units (gNB-DU) in a cloud RAN (C-RAN) deployment.
- gNB1 provides cell 10 for multiple types of UEs.
- cell 10 may be a serving cell and perform contention based random access (CBRA) in cell 10.
- gNB1 may further provide one or more other cells.
- 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, cell 10 is a cell in which UEs2 performs an initial (RRC) connection establishment procedure or initiates an (RRC) connection reestablishment procedure.
- RRC initial
- GNB1 broadcasts Minimum SI (i.e., MIB and SIB1) in cell 10. gNB1 may further transmit another SI.
- Other SI includes all SIBs that are not broadcast within Minimum SI. These SIBs are broadcast periodically on DL-SCH or on demand on DL-SCH (ie, Radio Resource Control (RRC) _IDLE or RRC_INACTIVE wireless terminal (User Equipments). (In response to a request from UEs), or sent to UEs that are RRC_CONNECTED on DL_SCH in a dedicated manner.
- RRC Radio Resource Control
- Other SI includes at least SIB2 to SIB9.
- Each UE2 performs cell selection or cell reselection when it is in the RRC_IDLE state or the RRC_INACTIVE state. Further, each UE2 may reestablish the RRC connection when it is in the RRC_CONNECTED state.
- Each UE2 receives the MIB and SIB1 in the cell 10 and sets the initial DL BWP and the 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 the SIB 1. Then, each UE 2 performs a random access procedure in the cell 10 using the initial DL BWP and the initial UL BWP, and starts the RRC setup, RRC Resume, or RRC Re-establishment procedure.
- UEs2 is classified into a first type and a second type.
- the second type of UEs are UEs with limited capabilities compared to the first type of UEs.
- the second type of UEs may have limited RF capability compared to that of the first type of UEs.
- the second type of UEs may support a limited UE bandwidth (e.g., UE channel bandwidth, UE carrier bandwidth, UE RF bandwidth) as compared to that of the first type UEs.
- the second type of UEs may be the reduced capability NR devices described above, and the first type of UEs may be ordinary UEs (e.g., eMBB devices or URLLC devices).
- the second type of UEs may be, for example, industrial wireless sensors, wearable devices, or video surveillance devices (e.g., surveillance cameras). Twice
- the GNB1 transmits the first initial BWP setting and the second initial BWP setting.
- the first initial BWP setting includes cell-specific common parameters of the first initial BWP in cell 10.
- the first initial BWP includes the initial DL BWP and the initial UL BWP.
- the first initial BWP is used by at least the first type of UEs that use cell 10 as the serving cell.
- the first initial BWP is used by at least the first type of UEs in accessing cell 10 to transition from the RRC_IDLE state or the RRC_INACTIVE state to the RRC_CONNECTED state. That is, the first initial BWP is a cell-specific BWP commonly used by at least the first type of UEs.
- the first initial BWP may also be used for initial access by the second type of UEs, until the second type of UEs receives the second initial BWP setting or at a predetermined timing. , May be used by a second type of UEs.
- the predetermined timing is, for example, when the second type UE receives a control signal, control information, or RRC message that triggers the activation of the second initial BWP setting in the second type UE from gNB1. But it may be.
- the second initial BWP setting includes cell-specific common parameters of the second initial BWP of cell 10.
- the second initial BWP includes one or both of the initial DL BWP and the initial UL BWP.
- the bandwidth of the second initial DL BWP is narrower than the bandwidth of the first initial DL BWP.
- the bandwidth of the second initial UL BWP is equal to or narrower than the bandwidth of the first initial UL BWP.
- the second initial BWP is not used by the first type of UEs, but by the second type of UEs that use cell 10 as the serving cell. That is, the second initial BWP is a cell-specific BWP commonly used by the second type of UEs.
- the second initial BWP may be used by the second type of UEs in accessing cell 10 to transition from the RRC_IDLE state or the RRC_INACTIVE state to the RRC_CONNECTED state.
- the cell-specific common parameters of the first initial BWP include parameters indicating the frequency domain position and bandwidth of the first initial DL BWP, and the frequency domain of the first initial UL BWP. It may include parameters indicating location and bandwidth.
- the parameters indicating the frequency domain position and bandwidth of the first initial DL BWP may be included in the locationAndBandwidth field in the genericParameters field (BWP information element) in the initialDownlinkBWP field (BWP-DownlinkCommon information element) included in SIB1. ..
- the parameters indicating the frequency domain position and bandwidth of the first initial ULBWP may be included in the locationAndBandwidth field in the genericParameters field (BWP information element) in the initialUplinkBWP field (BWP-UplinkCommon information element) included in SIB1. ..
- the cell-specific common parameters of the second initial BWP are the parameters indicating the frequency domain position and bandwidth of the second initial DL BWP, or the frequency domain position and bandwidth of the second initial UL BWP. May include parameters indicating, or both.
- the parameters indicating the frequency domain position and bandwidth of the second initial DL BWP may be included in the locationAndBandwidth field in the genericParameters field (BWP information element) in the initialDownlinkBWP field (BWP-DownlinkCommon information element) included in SIB1. ..
- the parameters indicating the frequency domain position and bandwidth of the second initial ULBWP may be included in the locationAndBandwidth field in the genericParameters field (BWP information element) in the initialUplinkBWP field (BWP-UplinkCommon information element) included in SIB1. ..
- the initialDownlinkBWP field (and BWP-DownlinkCommon information element) containing the parameters indicating the frequency domain position and bandwidth of the second initial DL BWP may be a conventional one or an extension (branch) of the conventional one.
- the field (and information element) in SIB1 that contains the parameters indicating the frequency domain position and bandwidth of the second initial DLBWP is another field (eg) that corresponds to the initialDownlinkBWP field (and BWP-DownlinkCommon information element).
- InitialDownlinkBWP-ReducedCapability (RedCap) or initialDownlinkBWP-ReducedCapability (RedCap) and BWP-DownlinkCommonReducedCapability (RedCap)
- the genericParameters field (and BWP information element) may be conventional or an extension (branch) of the conventional one.
- the field (and information element) in SIB1 that includes the parameters indicating the frequency domain position and bandwidth of the second initial DLBWP is a field (eg, information element) different from the conventional genericParameters field (and BWP information element). It may be genericParametersReducedCapability (RedCap), or genericParametersReducedCapability (RedCap) and BWP-ReducedCapability (RedCap) information element).
- the cell-specific common parameters of the first initial BWP may include PDCCH parameters.
- the PDCCH parameter is the common searh space (searchSpaceOtherSystemInformation), paging, used by the UE to receive the DCI format indicating the PDSCH resource on which the system information message (eg, one or more of SIB2 to SIB9) is broadcast.
- the cell-specific common parameters of the second initial BWP may include the PDCCH parameter.
- the PDCCH parameter is the common searh space (searchSpaceOtherSystemInformation field), paging used by the UE to receive the DCI format indicating the PDSCH resource on which the system information message (eg, SIB2 to SIB9) is broadcast. •
- the common searh space (pagingSearchSpace field) used by the UE to receive the DCI format indicating the PDSCH resource to which the message will be sent, and one or more common search spaces in the second initial DL BWP. Set.
- the searchSpaceOtherSystemInformation field and the pagingSearchSpace field specified by the PDCCH parameter included in the cell-specific common parameter of the second initial BWP may be a conventional one or an extension (branch) of the conventional one.
- these fields may be fields different from the conventional fields (e.g., searchSpaceOtherSystemInformationReducedCapability (RedCap) and pagingSearchSpaceReducedCapability (RedCap)).
- the cell-specific common parameters of the first initial BWP are the random access that at least the first type of UEs use for contention-based random access in the first initial UL BWP. It may include parameters.
- the random access parameter along with other parameters, may indicate, for example, the total number of random access prints, subcarrier spacing for the first message (Msg1), or both.
- cell-specific common parameters of the second initial BWP may include random access parameters used by the second type of UEs for contention-based random access in the first initial UL BWP. ..
- the random access parameter may indicate, for example, the total number of random access prints, subcarrier spacing for the first message (Msg1), or both.
- the random access parameters of the second initial BWP (e.g., their set values, or the radio resources derived from the set values) may be different from those of the first initial BWP.
- the random access parameters of the second initial BWP may be set (exclusively) so that they do not overlap with the random access parameters of the first initial BWP, or they and parts of the first initial BWP. May be duplicated.
- FIG. 2 shows an example of the operation of gNB1 and UE2.
- gNB1 broadcasts the first initial BWP setting via system information (e.g., SIB1).
- gNB1 broadcasts the second initial BWP configuration via system information (e.g., SIB1) or via UE-dedicated signaling (e.g., RRC message).
- system information e.g., SIB1
- UE-dedicated signaling e.g., RRC message
- UE2 is assumed to be the second type of UE.
- UE2 receives the system information (e.g., SIB1) including the first initial BWP setting (step 201).
- UE2 receives the second initial BWP configuration via system information (e.g., SIB1) or via UE-individual signaling (step 202).
- system information e.g., SIB1
- UE-individual signaling step 202
- UE2 uses the second initial BWP setting.
- the gNB1 is one or both of the first initial BWP (ie, initial DL and UL BWPs) and the second initial BWP (ie, initial DL and UL BWPs). ) Is set in cell 10.
- the first type of UEs and the second type of UEs use cell 10 as a serving cell and perform contention-based random access in cell 10.
- the second initial BWP is not used by the first type of UEs, but by the second type of UEs.
- gNB1 sets the second initial BWP setting indicating the cell-specific common parameter of the second initial BWP of the cell 10, and the first initial BWP indicating the cell-specific common parameter of the first initial BWP of the cell 10.
- send send.
- the second type of UEs selects and uses the second initial BWP. Therefore, according to the present embodiment, it is possible for the second type UEs having a limited ability as compared with that of the first type UEs to use the initial BWP suitable for the ability in the cell 10. ..
- the present embodiment provides a specific example of transmission of the first and second initial BWP settings described in the first embodiment.
- the configuration example of the wireless communication network according to the present embodiment is the same as the example shown in FIG.
- gNB1 broadcasts both the first and second initial BWP settings via system information (e.g., SIB1). If UE2 is a second type of UE, UE2 selects the second initial BWP setting from the received system information and applies the second initial BWP setting.
- system information e.g., SIB1
- UE2 is a second type of UE
- UE2 selects the second initial BWP setting from the received system information and applies the second initial BWP setting.
- the definitions and uses of the first and second initial BWPs are similar to the examples described in the first embodiment. Specific examples of the first and second initial BWP settings are the same as the examples described in the first embodiment.
- FIG. 3 shows an example of the operation of gNB1 and UE2 according to this embodiment.
- UE2 is a second type of UE.
- gNB1 broadcasts both the first and second initial BWP settings via system information (e.g., SIB1).
- the second initial BWP configuration is one or more new branches of the ServingCellConfigCommonSIB information element, DownlinkConfigCommonSIB information element, BWP-DownlinkCommon information element, UplinkConfigCommonSIB information element, and BWP-UplinkCommon information element contained in SIB1. May be defined as.
- a new version of the information element that contains at least some of the configuration information (or parameters) contained in those information elements and that contains the settings for the second initial BWP configuration. It may be specified.
- step 302 if UE2 is the second type of UE, UE2 selects the second initial BWP setting from the received system information and applies the second initial BWP setting.
- UE2 performs a random access procedure (4-Step Random Access (RA)) using the second initial BWP setting, and starts the RRC setup procedure to transition from the RRC_IDLE state to the RRC_CONNECTED state. do.
- RA Random Access
- UE2 may select the random access preamble sent in step 303 according to the random access parameters included in the second initial BWP configuration. For example, UE2 may send a random access preamble based on the settings of the second initial UL BWP.
- UE2 is set by the PDCCH parameter included in the second initial BWP configuration to receive the DCI format indicating the PDSCH resource for which the random access response (Msg2) was scheduled in step 304. You may monitor the common search space. Further or instead, UE2 may monitor the PDSCH resource set by the PDSCH parameter included in the second initial BWP setting to receive the random access response (Msg2) in PDSCH in step 304. good.
- the UE2 performs a third message (Msg3) (eg, the first RRC message (eg, RRC) according to the Physical Uplink Shared Channel (PUSCH) parameter included in the second initial BWP configuration. SetupRequest)) may be sent via Physical Uplink Shared Channel (PUSCH).
- Msg3 eg, the first RRC message (eg, RRC) according to the Physical Uplink Shared Channel (PUSCH) parameter included in the second initial BWP configuration. SetupRequest)
- PUSCH Physical Uplink Shared Channel
- UE2 schedules a fourth message (Msg4) for contention resolution (eg, Contention Resolution MAC Control Element (CE), and RRC message (eg, RRC Setup)) in step 306.
- Msg4 for contention resolution
- CE Contention Resolution MAC Control Element
- RRC message eg, RRC Setup
- the common search space set by the PDCCH parameter included in the second initial BWP setting may be monitored.
- the UE 2 may monitor the PDSCH resource set by the PDSCH parameter included in the second initial BWP setting in order to receive the fourth message (Msg4) on the PDSCH in step 306. .
- UE2 may use the second initial BWP as the First active BWP in response to receiving the fourth message (Msg4) (or after receiving Msg4).
- UE2 indicates the completion of the fifth message (Msg5) (eg, random access procedure (4 Step RA)) according to the PUSCH parameter contained in the second initial BWP configuration. (Eg, RRC Setup Complete)) may be sent by PUSCH.
- Msg5 eg, random access procedure (4 Step RA)
- PUSCH parameter contained in the second initial BWP configuration e.g, RRC Setup Complete
- UE2 is set by the PDSCH parameter included in the second initial BWP configuration to receive DL signaling and DL RRC messages that occur after the RRC Setup message in step 306 on the PDSCH.
- PDSCH resources may be monitored.
- FIG 3 shows an example of RRC setup (RRC establishment), but the transmission of the second initial BWP setting via system information is RRC resume (Msg3: RRC Resume Request, Msg4: RRC Resume, Msg5: RRC Resume). It can also be used for (Complete) and RRC re-establishment (Msg3: RRC Reestablishment Request, Msg4: RRC Reestablishment).
- gNB1 applies the second initial BWP setting to the second type of UEs via the system information. Therefore, the second type of UEs can use the second initial BWP configuration before initiating the random access procedure.
- the second initial BWP setting broadcast in step 301 may imply support for the second type of UEs (e.g., reduced capability UEs) in cell 10. If the cell cannot receive the second initial BWP setting, the second type of UEs may recognize that access to that cell is prohibited.
- the second type of UEs e.g., reduced capability UEs
- UE2 may indicate to gNB1 a unique (specific) logical channel ID (LCID) associated with the second type of UEs (e.g., reduced capability UEs).
- LCID logical channel ID
- gNB1 can identify (or detect) that UE2 is a second type of UE based on the receipt of the unique LCID.
- the UE 2 may include in the RRCSetupComplete message an indication that it is a second type of UE.
- the gNB1 can identify (or detect) that the UE2 is a second type of UE based on the reception of the display.
- gNB1 receives UE capability information from UE2 or the core network (eg, 5G Core Network (5GC) Access and Mobility Management Function (AMF)).
- UE2 may be identified (or detected) as a second type of UE based on UE capability information.
- gNB1 provides UE-specific settings (including dedicated BWP settings) that depend on UE2's capabilities to individual signaling (eg). , RRC Reconfiguration message) may be sent to UE2.
- FIG. 4 shows another example of the operation of gNB1 and UE2 according to the present embodiment.
- UE2 is a second type of UE.
- the example of FIG. 4 differs from the example of FIG. 3 in that a 2-step random access procedure (2-Step RA) is performed instead of the 4-step random access procedure (4-Step RA).
- gNB1 broadcasts both the first and second initial BWP settings via system information (e.g., SIB1).
- step 402 if UE2 is the second type of UE, UE2 selects the second initial BWP setting from the received system information and applies the second initial BWP setting.
- steps 403 to 405 UE2 performs a two-step random access procedure (2-Step RA) using the second initial BWP setting and initiates the RRC setup procedure to transition from the RRC_IDLE state to the RRC_CONNECTED state. ..
- UE2 may choose the random access preamble for message A (MsgA) in 2-Step RACH sent in step 403 according to the random access parameters included in the second initial BWP configuration. good. For example, UE2 may send a random access preamble based on the settings of the second initial UL BWP. Further or instead, in step 403, the UE2 sets the data part (payload) of the message A (MsgA) of 2-Step RA (for example, the first RRC message (eg, RRCSetupRequest)) to the second. It may be transmitted according to the Physical Uplink Shared Channel (PUSCH) parameter included in the initial BWP setting.
- PUSCH Physical Uplink Shared Channel
- UE2 schedules a 2-Step RA random access response (message B (MsgB)) (eg, Contention Resolution MAC CE, and RRC message (eg, RRC Setup)) in step 404.
- MsgB messages B
- RRC message eg, RRC Setup
- the common search space set by the PDCCH parameter included in the second initial BWP setting may be monitored.
- the UE2 uses the PDSCH resource set by the PDSCH parameter included in the second initial BWP setting to receive the 2Step RA random access response (MsgB) in the PDSCH in step 404. You may monitor it.
- UE2 sends, for example, an RRC message (eg, RRCSetupComplete) indicating the completion of the 2-Step random access procedure according to the PUSCH parameter included in the second initial BWP configuration. It may be sent by PUSCH.
- RRC message eg, RRCSetupComplete
- Figure 4 shows an example of RRC setup (RRC establishment), but the transmission of the second initial BWP setting via system information can also be used for RRC resume and RRC re-establishment.
- the present embodiment provides a specific example of transmission of the first and second initial BWP settings described in the first embodiment.
- the configuration example of the wireless communication network according to the present embodiment is the same as the example shown in FIG.
- the definitions and uses of the first and second initial BWPs in this embodiment are the same as those described in the first embodiment.
- Specific examples of the first and second initial BWP settings are the same as the examples described in the first embodiment.
- gNB1 broadcasts the first initial BWP configuration via system information (eg, SIB1) and broadcasts the second initial BWP configuration in a contention-based random access (CBRA) procedure with an RRC message.
- Send to the second type UE via eg, RRC Setup.
- UE2 is the second type of UE, UE2 receives the first initial BWP setting via system information (eg, SIB1) and sends the second initial BWP setting in the RRC message (eg) within the CBRA procedure. , RRCSetup).
- UE2 applies the second initial BWP setting in place of the first initial BWP setting (i.e., updates the initial BWP setting to be used).
- FIG. 5 shows an example of the operation of gNB1 and UE2 according to the present embodiment.
- UE2 is a second type of UE.
- gNB1 broadcasts the first initial BWP configuration via system information (e.g., SIB1).
- gNB1 also broadcasts the Random Access Channel (RACH) settings in the random access procedure (4-Step RA) for the second type of UEs via system information.
- RACH Random Access Channel
- the RACH setting indicates specific RACH resources (i.e., preamble and / or both) for the second type of UEs.
- the broadcast of the RACH setting implies support for a second type of UEs (e.g., reduced capability UEs) in cell 10.
- UE2 receives the system information from gNB1 and applies the received first initial BWP setting.
- UE2 selects a RACH resource based on the Random Access Channel (RACH) configuration for the second type of UEs and sends a random access preamble to gNB1.
- RACH Random Access Channel
- gNB1 detects access from a second type of UE.
- gNB1 sends a random access response (Msg2).
- Msg3 eg, the first RRC message (e.g., RRCSetupRequest)
- gNB1 transmits a fourth message (Msg4) (for example, Contention resolution MAC CE for contention resolution and RRC Setup message) to UE2.
- the RRC Setup message includes a second initial BWP setting.
- gNB1 sets the second initial BWP setting in the RRCSetup message in response to identifying (or detecting) that UE2 is the second type of UE via the RACH resource (step 503).
- UE2 applies the second initial BWP setting in place of the first initial BWP setting in response to receiving the second initial BWP setting (ie, update the initial BWP setting to be used). ..
- UE2 may use the second initial BWP as the First active BWP in response to receiving the fourth message (Msg4) (or after receiving Msg4).
- Msg4 the fourth message
- UE2 sends an RRCSetupComplete message to gNB1 according to the second initial BWP setting.
- the procedure of FIG. 5 can be appropriately modified.
- the procedure of FIG. 5 may be modified to perform a 2-step random access procedure (2-Step RA) instead of the 4-step random access procedure (4-Step RA).
- gNB1 may send an RRC message (e.g., RRCSetup) including the second initial BWP setting as a 2-Step RA random access response (message B (MsgB)).
- RRC message e.g., RRCSetup
- MsgB message B
- FIG. 6 shows another example of the operation of gNB1 and UE2 according to the present embodiment.
- the procedure of FIG. 6 is a specific logical channel ID (LCID) associated with a second type of UEs (eg, reduced capability UEs) to inform gNB1 that UE2 is a second type of UE. ) Is used, which is different from the procedure of FIG.
- LCID logical channel ID
- the gNB1 broadcasts the first initial BWP setting via system information (e.g., SIB1). gNB1 also broadcasts a display indicating support for the second type of UEs via system information.
- UE2 receives system information from gNB1 and applies the received first initial BWP setting.
- UE2 transmits a random access preamble to gNB1.
- gNB1 sends a random access response (Msg2).
- Msg3 for example, the first RRC message (e.g., RRCSetupRequest)) to gNB1.
- UE2 indicates to gNB1 a specific logical channel ID (LCID) associated with the second type of UEs (e.g., reduced capability UEs).
- the unique LCID may be, for example, an LCID that is predetermined to be used for the Common Control CHannel (CCCH).
- CCCH Common Control CHannel
- gNB1 identifies (or detects) that UE2 is a second type of UE based on the receipt of the unique LCID.
- gNB1 transmits a fourth message (Msg4) (for example, Contention resolution MAC CE for contention resolution and RRC Setup message) to UE2.
- the RRC Setup message includes a second initial BWP setting.
- gNB1 has identified (or detected) that UE2 is a second type of UE through a unique LCID associated with the second type of UEs, and thus has a second type of UE. Include the initial BWP settings in the RRC Setup message.
- UE2 applies the second initial BWP setting in place of the first initial BWP setting in response to receiving the second initial BWP setting (ie, update the initial BWP setting to be used). ..
- UE2 sends an RRCSetupComplete message to gNB1 according to the second initial BWP setting.
- the procedure of FIG. 6 can be appropriately modified.
- the procedure of FIG. 6 may be modified to perform a 2-step random access procedure (2-Step RA) instead of the 4-step random access procedure (4-Step RA).
- gNB1 may send an RRC message (e.g., RRCSetup) including the second initial BWP setting as a 2-Step RA random access response (message B (MsgB)).
- RRC message e.g., RRCSetup
- MsgB message B
- the second initial BWP setting sent to UE2 in step 506 of FIG. 5 and step 606 of FIG. 6 is a cell-specific common setting of the initial BWP, not a UE-specific individual setting. It should be noted that.
- the second initial BWP setting includes a cell-specific common setting of the second initial BWP corresponding to (at least a part of) the cell-specific common setting of the first initial BWP.
- the second initial BWP setting is transmitted as a UE-specific RRC message in step 506 of FIG. 5 and step 606 of FIG. 6, but is not a UE-specific individual setting.
- the second initial BWP settings sent in steps 506 and 606 include cell-specific parameters of the initial BWP.
- the second initial BWP setting may include a parameter indicating the frequency domain position and bandwidth of the initial DL BWP, a parameter indicating the frequency domain position and bandwidth of the initial UL BWP, or both. Further or instead, the second initial BWP setting may include a setting of Type 0-PDCCH common search space set (search space # 0) of the initial DL BWP. Type0-PDCCH common search space set (search space # 0) is monitored for receiving Type0-PDCCH for SIB1 decoding.
- UE2 If UE2 moves from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state after receiving the second initial BWP setting, UE2 stores the second initial BWP setting and uses the second initial BWP setting. You may continue. For example, UE2 may continue to use the second initial BWP setting while staying in the same cell 10.
- UE2 initiates the RRCSetup or RRCResume procedure to transition from the RRC_IDLE or RRC_INACTIVE state to the RRC_CONNECTED state again in the same cell 10, it should use the first initial BWP setting broadcast via SIB1. Instead, cell 10 may be accessed using the stored initial BWP settings. Even if UE2 performs these operations only when it receives information from gNB1 that explicitly or implicitly indicates permission to perform the operation by RRC message (eg, RRC Setup, RRC Reconfiguration, RRC Release) or SIB1. good.
- RRC message eg, RRC Setup, R
- UE2 sets the first initial BWP to be broadcast via SIB1 in the new cell if a new cell different from cell 10 supports a second type of UEs. You may access the new cell using the stored initial BWP settings instead of using. UE2 may perform these operations only when it receives information from gNB1 in an RRC message or SIB1 that explicitly or implicitly indicates permission to perform the operation.
- the present embodiment provides a specific example of transmission of the first and second initial BWP settings described in the first embodiment.
- the configuration example of the wireless communication network according to the present embodiment is the same as the example shown in FIG.
- the definitions and uses of the first and second initial BWPs in this embodiment are the same as those described in the first embodiment.
- Specific examples of the first and second initial BWP settings are the same as the examples described in the first embodiment.
- the gNB1 broadcasts the first initial BWP setting via system information (eg, SIB1) and the second initial BWP setting via the RRC Reconfiguration message after the completion of the UE2 RRC (connection) setup. And send it to UE2.
- UE2 is the second type of UE, UE2 receives the first initial BWP configuration via system information (eg, SIB1) and sends the second initial BWP configuration an RRC Reconfiguration message after the RRC setup is complete. Receive via.
- UE2 applies the second initial BWP setting in place of the first initial BWP setting (i.e., updates the initial BWP setting to be used).
- FIG. 7 shows an example of the operation of gNB1 and UE2 according to this embodiment.
- UE2 is a second type of UE.
- gNB1 broadcasts the first initial BWP configuration via system information (e.g., SIB1).
- gNB1 also broadcasts a display indicating support for the second type of UEs via system information.
- Steps 702 to 707 are the same as the normal contention-based random access (CBRA) procedure and RRC Setup procedure.
- UE2 receives system information from gNB1 and applies the received first initial BWP setting.
- UE2 sends a random access preamble to gNB1.
- gNB1 sends a random access response (Msg2).
- UE2 transmits a third message (Msg3) (for example, the first RRC message (e.g., RRCSetupRequest)) to gNB1.
- Msg3 for example, the first RRC message (e.g., RRCSetupRequest)
- gNB1 transmits a fourth message (Msg4) for contention resolution (for example, Contention Resolution MAC CE for contention resolution, and RRC Setup message to UE2.
- Msg4 for contention resolution
- UE2 sends a fourth message (Msg4). Send RRCSetupComplete message to gNB1.
- gNB1 acquires the UE capability information of UE2 from UE2 or the core network (AMF of e.g., 5GC). gNB1 identifies (or detects) that UE2 is a second type of UE based on the acquired UE capability information. Upon identifying (or detecting) that UE2 is a second type of UE, gNB1 generates an RRC Reconfiguration message containing the second initial BWP configuration. In step 709, gNB1 sends an RRC Reconfiguration message containing the second initial BWP configuration to UE2. In step 710, UE2 applies the second initial BWP setting in place of the first initial BWP setting in response to receiving the second initial BWP setting (ie, update the initial BWP setting to use). ..
- the procedure of FIG. 7 can be appropriately modified.
- the procedure of FIG. 7 may be modified to perform a 2-step random access procedure (2-Step RA) instead of the 4-step random access procedure (4-Step RA).
- the second initial BWP setting sent to UE2 in step 709 is a cell-specific common setting for the initial BWP, not a UE-specific individual setting.
- the second initial BWP setting includes a cell-specific common setting of the second initial BWP corresponding to (at least a part of) the cell-specific common setting of the first initial BWP.
- the second initial BWP setting is sent in a UE-specific RRC message in step 709, but is not a UE-specific individual setting.
- the second initial BWP setting sent in step 709 includes cell-specific parameters of the initial BWP.
- the second initial BWP setting may include a parameter indicating the frequency domain position and bandwidth of the initial DL BWP, a parameter indicating the frequency domain position and bandwidth of the initial UL BWP, or both. Further or instead, the second initial BWP setting may include a setting of Type 0-PDCCH common search space set (search space # 0) of the initial DL BWP. Type0-PDCCH common search space set (search space # 0) is monitored for receiving Type0-PDCCH for SIB1 decoding.
- UE2 If UE2 moves from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state after receiving the second initial BWP setting, UE2 stores the second initial BWP setting and uses the second initial BWP setting. You may continue. For example, UE2 may continue to use the second initial BWP setting while staying in the same cell 10.
- UE2 initiates the RRCSetup or RRCResume procedure to transition from the RRC_IDLE or RRC_INACTIVE state to the RRC_CONNECTED state again in the same cell 10, use the first initial BWP setting broadcast via SIB1. Instead, cell 10 may be accessed using the stored initial BWP settings. Even if UE2 performs these operations only when it receives information from gNB1 that explicitly or implicitly indicates permission to perform the operation by RRC message (eg, RRC Setup, RRC Reconfiguration, RRC Release) or SIB1. good.
- RRC message eg, RRC Setup, RRC Re
- UE2 sets the first initial BWP to be broadcast via SIB1 in the new cell if a new cell different from cell 10 supports a second type of UEs.
- the new cell may be accessed using the stored initial BWP settings without using.
- UE2 may perform these operations only when it receives information from gNB1 in an RRC message or SIB1 that explicitly or implicitly indicates permission to perform the operation.
- the configuration example of the wireless communication network according to the present embodiment is the same as the example shown in FIG.
- the definitions and uses of the first and second initial BWPs in this embodiment are the same as those described in the first embodiment.
- Specific examples of the first and second initial BWP settings are the same as the examples described in the first embodiment.
- the present embodiment provides specific examples of the operation of UE2 described in the third and fourth embodiments.
- FIG. 8 shows an example of the operation of UE2 according to this embodiment.
- the UE 2 receives a second initial BWP configuration from the gNB 1 via individual RRC signaling, including cell-specific common parameters.
- Step 801 is similar to step 506 in FIG. 5, step 606 in FIG. 6, or step 709 in FIG.
- UE2 applies the received second initial BWP setting.
- step 803 UE2 transitions from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state.
- step 804 when the UE2 is in the RRC_IDLE state or the RRC_INACTIVE state after receiving the second initial BWP setting, the UE2 stores the second initial BWP setting and continues to use the second initial BWP setting. do. For example, UE2 may continue to use the second initial BWP setting while staying in the same cell 10.
- UE2 initiates the RRCSetup or RRCResume procedure to transition from the RRC_IDLE or RRC_INACTIVE state to the RRC_CONNECTED state again in the same cell 10, it should use the first initial BWP setting broadcast via SIB1. Instead, cell 10 may be accessed using the stored initial BWP settings. Even if UE2 performs these operations only when it receives information from gNB1 that explicitly or implicitly indicates permission to perform the operation by RRC message (eg, RRC Setup, RRC Reconfiguration, RRC Release) or SIB1. good.
- RRC message eg, RRC Setup, RRC Reconfiguration, RRC Release
- UE2 sets the first initial BWP to be broadcast via SIB1 in the new cell if a new cell different from cell 10 supports a second type of UEs. You may access the new cell using the stored initial BWP settings instead of using. UE2 may perform these operations only when it receives information from gNB1 in an RRC message or SIB1 that explicitly or implicitly indicates permission to perform the operation.
- the UE of the second type transitions from the RRC_IDLE state or the RRC_INACTIVE state to the RRC_CONNECTED state again, the UE is the second initial received when it was in the RRC_CONNECTED state in the past.
- BWP settings can be used.
- the configuration example of the wireless communication network according to the present embodiment is the same as the example shown in FIG.
- the definitions and uses of the first and second initial BWPs in this embodiment are the same as those described in the first embodiment.
- Specific examples of the first and second initial BWP settings are the same as the examples described in the first embodiment.
- the present embodiment provides specific examples of the operations of gNB1 and UE2 described in the third and fourth embodiments.
- the RAN including gNB1 can continue to use the second initial BWP received when UE2 is in the RRC_CONNECTED state even after the transition from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state. Defines the cells or areas allowed in.
- FIG. 9 shows an example of the operation of gNB1 according to the present embodiment.
- gNB1 When releasing the RRC connection with UE2, gNB1 allows UE2 to continue to use the second initial BWP setting even after transitioning from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state.
- RAN area information indicating the area is sent to UE2 (step 901).
- the gNB1 may include the RAN area information in the RRC Release message (SuspendConfig in the e.g., RRC Release message).
- Other RRC messages eg, RRC Reconfiguration
- the RAN area information may indicate a list of cells or a list of RAN area codes.
- the RAN area code (ranac) may be newly defined as ranac-Reduced Capability (RedCap).
- the configuration of the RAN Notification Area (RNA) may be reused. ..
- the RNA may be newly defined as RNA-Reduced Capability (Red Cap). Twice
- FIG. 10 shows an example of the operation of RAN4 according to the present embodiment.
- GNB1 belonging to RAN4 and other gNBs supporting the second type of UEs broadcast the RAN area code regarding the continuous use of the second initial BWP setting via the system information (eg, SIB1) (step 1001). ..
- FIG. 11 shows an example of the operation of UE2 according to the present embodiment.
- UE2 receives the second initial BWP setting and the list of RAN area codes when it is in the RRC_CONNECTED state, and then transitions from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state.
- the list of RAN area codes indicates one or more RAN area codes that represent one or more RAN areas that are allowed to continue to use the second initial BWP setting.
- UE2 stores and maintains a list of second initial BWP settings and RAN area codes in memory.
- UE2 receives SIB1 in a new cell when it is in the RRC_IDLE state or the RRC_INACTIVE state.
- the new cell may be a cell provided by the same gNB1 as cell 10 or a cell provided by another gNB.
- UE2 determines whether or not SIB1 received from the new cell indicates any one of the stored 1 or more RAN area codes. If SIB1 in the new cell indicates one of the stored RAN area codes, UE2 will continue to use the stored initial BWP setting in the new cell. For example, when UE2 initiates the RRCSetup or RRCResume procedure to transition from the RRC_IDLE or RRC_INACTIVE state to the RRC_CONNECTED state again in a new cell, use the first initial BWP setting broadcast via SIB1. Instead, access the new cell using the stored initial BWP settings.
- UE2 may receive a list of one or more cells that are allowed to continue using the second initial BWP configuration.
- UE2 may determine whether or not a new cell is included in the list based on SIB1 received from the new cell.
- the UE2 when UE2 receives the second initial BWP setting when it is in the RRC_CONNECTED state and then shifts from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state, the UE2 sets the second initial BWP setting. Can be used continuously.
- the configuration example of the wireless communication network according to the present embodiment is the same as the example shown in FIG.
- the definitions and uses of the first and second initial BWPs in this embodiment are the same as those described in the first embodiment.
- Specific examples of the first and second initial BWP settings are the same as the examples described in the first embodiment.
- the UE2 is a second type in transmitting a third message (Msg3) (eg, RRCSetupRequest) in a random access procedure (eg, RRCSetup procedure).
- Msg3 eg, RRCSetupRequest
- a random access procedure eg, RRCSetup procedure
- the unique (specific) logical channel ID (LCID) associated with the UEs (eg, reduced capability UEs) of is indicated in gNB1.
- UE2 may use the RACH resource associated with the second type of UEs in the random access preamble (Msg1) transmission in the random access procedure.
- UE2 may not use the display of the second UE via the RACH resource or LCID.
- gNB1 acquires the UE context stored in gNB1 or another gNB (gNB that moved eg, UE2 to the RRC_INACTIVE state), and whether or not UE2 is a second type UE based on the UE context. This is because it can be judged.
- the RRC resume for UE2 fails (eg because gNB1 could not get the UE context correctly), gNB1 can fall back to set up a new RRC connection and establish a new RRC connection.
- RRC Setup message can be sent to UE2. In this case, gNB1 may not be able to determine if UE2 is a second type of UE.
- RRC re-establishment RRC connection reestablishment procedure
- gNB1 can use the UE context stored in gNB1 and can determine whether UE2 is a second type UE based on the UE context. ..
- gNB1 can fall back to set up a new RRC connection and send an RRC Setup message to UE2 to establish a new RRC connection. .. In this case, gNB1 may not be able to determine if UE2 is a second type of UE.
- UE2 of the present embodiment sends an RRCSetup message for establishing a new RRC connection to the network (gNB) even though the RRC connection restart procedure or the RRC connection reestablishment procedure is started.
- an RRC Setup Complete message containing a second type of display eg, limited capacity display
- a second type of display eg, limited capacity display
- FIG. 12 shows an example of the operation of gNB1 and UE2.
- UE2 sends an RRCResumeRequest message or an RRCReestablishmentRequest message to gNB1.
- gNB1 decides to fall back to the establishment of a new RRC connection.
- gNB1 sends an RRCSetup message to UE2, which is neither an RRCResume message nor an RRCreestablishment message.
- UE2 sends an RRC Setup Complete message to gNB1 that includes a second type of display (e.g., display of limited capabilities).
- a second type of display e.g., display of limited capabilities
- the configuration example of the wireless communication network according to the present embodiment is the same as the example shown in FIG.
- the definitions and uses of the first and second initial BWPs in this embodiment are the same as those described in the first embodiment.
- Specific examples of the first and second initial BWP settings are the same as the examples described in the first embodiment.
- C-RAN cloud RAN
- gNB1 is composed of Central Unit (CU) and 1 or more Distributed Units (DUs).
- CU Central Unit
- DU Distributed Unit
- C-RAN is sometimes called Centralized RAN or CU-DU split architecture.
- FIG. 13 shows a configuration example of gNB1 according to this embodiment.
- GNB1 in FIG. 13 includes CU11 and one or more DUs12.
- the CU 11 and each DU 12 are connected by an interface 1301 (i.e., F1 interface).
- UE2 is connected to at least one DU12 via at least one air interface 1302.
- the CU 11 may be a logical node that hosts the RadioResourceControl (RRC), ServiceDataAdaptationProtocol (SDAP), and PacketDataConvergenceProtocol (PDCP) protocols of gNB1 (or RRC and PDCP protocols of gNB).
- the CU 11 may include a Control Plane (CP) Unit (i.e., gNB-CU-CP) and one or more User Plane (UP) Units (i.e., gNB-CU-UP).
- the DU12 may be a logical node that hosts the RadioLinkControl (RLC), MediumAccessControl (MAC), and Physical (PHY) layers of gNB1.
- the LCID associated with the second type of UEs (step 503 in FIG. 5) or via the LCID specific to the second type of UEs (FIG. 6).
- UE2 may inform gNB1 that UE2 is a second type of UE.
- gNB1 contains CU11 and one or more DUs12 as shown in FIG. 13, one of the DU12s detects the RACH resource and the LCID, and the CU11 includes the second initial BWP setting RRC Setup.
- Generate a message (step 506 of FIG. 5, step 606 of FIG. 6). Therefore, signaling between CU11 and DU12 is required to make this possible.
- FIG. 14 shows an example of signaling between CU11 and DU12.
- the DU12 is subjected to the RACH resource associated with the second type of UEs (eg, step 503 of FIG. 5) or the LCID specific to the second type of UEs (eg, step of FIG. 6). Through 605), it is detected that UE2 is a second type of UE.
- the DU 12 sends an F1AP message (i.e., INITIAL UL RRC MESSAGE TRANSFER message) including the first RRC message (e.g., RRC Setup Request) received from the UE 2 to the CU 11.
- DU12 includes an indication in the INITIAL UL RRC MESSAGE TRANSFER message that UE 2 is a second type of UE.
- the display may be, for example, a display of limited abilities.
- the display may be defined as a new information element (e.g., Reduced Capability Indication information element (IE)) of the F1AP: INITIAL UL RRC MESSAGE TRANSFER message.
- IE Reduced Capability Indication information element
- the display may be included in the DU to CU RRC Container IE in the F1AP: INITIAL UL RRC MESSAGE TRANSFER message. More specifically, the display may be defined as a new IE in DU to CU RRC Container IE, or as a new IE or field included in CellGroupConfig IE in DU to CU RRC Container IE. May be done.
- CU11 receives the RRCSetupRequest message from UE2 in response to the reception of the F1AP: INITIALULRRCMESSAGETRANSFER message (step 1402), and identifies that UE2 is the second type of UE.
- the CU 11 generates an RRC Setup message including the second initial BWP setting, and sends an F1AP message (i.e., DL RRC MESSAGE TRANSFER message) including the RRC Setup message to the DU 12.
- the DU 12 transmits an RRC Setup message including the second initial BWP setting to the UE 2.
- FIG. 15 shows another example of signaling between CU11 and DU12.
- Step 1501 is the same as step 1401 in FIG.
- the DU 12 sends an F1AP message (i.e., INITIAL UL RRC MESSAGE TRANSFER message) including the first RRC message (e.g., RRC Setup Request) received from the UE 2 to the CU 11.
- DU12 includes an indication in the INITIAL UL RRC MESSAGE TRANSFER message that UE 2 is a second type of UE.
- the display may be, for example, a display of limited abilities.
- the DU12 generates a second initial BWP setting, which is included in the INITIAL UL RRC MESSAGE TRANSFER message.
- the DU 12 may generate a CellGroupConfig that includes the second initial BWP setting, and include this in the DU to CU RRC Container IE in the INITIAL UL RRC MESSAGE TRANSFER message.
- the CU11 receives the RRCSetupRequest message from UE2 in response to the reception of the F1AP: INITIALULRRCMESSAGETRANSFER message (step 1502), and identifies that UE2 is the second type of UE. Further, the CU 11 receives the second initial BWP setting (e.g., CellGroupConfig including the second initial BWP setting) generated by the DU 12. In step 1503, the CU 11 generates an RRC Setup message including the second initial BWP setting, and sends an F1AP message (i.e., DL RRC MESSAGE TRANSFER message) including the RRC Setup message to the DU 12. In response to receiving the DL RRC MESSAGE TRANSFER message (step 1503), the DU 12 transmits an RRC Setup message including the second initial BWP setting to the UE 2.
- the second initial BWP setting e.g., CellGroupConfig including the second initial BWP setting
- F1AP message i.e., DL RRC MESS
- the DU 12 notifies the CU 11 of the second initial BWP setting information (Second Initial BWP Configuration) by the F1 SETUP REQUEST message or the gNB-DU CONFIGURATION UPDATE message, and the CU 11 sets the second initial BWP. Information may be saved.
- the CU11 recognizes that the UE2 is a Reduced capability UE based on the UE Capability of the UE2, and then sets the saved second initial BWP setting information to the DU12. It may be transmitted to UE2 via.
- the DU 12 may transmit the second initial BWP setting information to the CU 11 by another F1AP procedure.
- This F1AP procedure may be, for example, an F1AP procedure associated with a specific UE (UE associated) or a non-UE associated F1AP procedure.
- FIG. 16 is a block diagram showing a configuration example of gNB1 according to the above-described embodiment.
- gNB1 includes a Radio Frequency (RF) transceiver 1601, a network interface 1603, a processor 1604, and a memory 1605.
- the RF transceiver 1601 performs analog RF signal processing to communicate with UEs, including UE2.
- the RF transceiver 1601 may include a plurality of transceivers.
- the RF transceiver 1601 is coupled with the antenna array 1602 and the processor 1604.
- the RF transceiver 1601 receives the modulation symbol data from the processor 1604, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 1602. Further, the RF transceiver 1601 generates a baseband reception signal based on the reception RF signal received by the antenna array 1602, and supplies the baseband reception signal to the processor 1604.
- the RF transceiver 1601 may include an analog beamformer circuit for beamforming.
- the analog beamformer circuit includes, for example, a plurality of phase shifters and a plurality of power amplifiers.
- the network interface 1603 is used to communicate with network nodes (e.g., other gNBs, AMF, Session Management Function (SMF), and User Plane Function (UPF)).
- the network interface 1603 may include, for example, an IEEE 802.3 series compliant network interface card (NIC).
- Processor 1604 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication.
- Processor 1604 may include a plurality of processors.
- the processor 1604 is a modem processor (eg, Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (eg, Central Processing Unit (CPU) or Micro Processing Unit (eg, Central Processing Unit (CPU)) that performs control plane processing. MPU)) may be included.
- DSP Digital Signal Processor
- MPU Central Processing Unit
- MPU Central Processing Unit
- digital baseband signal processing by the processor 1604 is performed by the ServiceDataAdaptationProtocol (SDAP) layer, PacketDataConvergenceProtocol (PDCP) layer, RadioLinkControl (RLC) layer, MediumAccessControl (MAC) layer, and Physical (PHY). ) Layer signal processing may be included. Further, the control plane processing by the processor 1604 may include processing of Non-Access Stratum (NAS) messages, RRC messages, MAC CEs, and DCIs.
- SDAP ServiceDataAdaptationProtocol
- PDCP PacketDataConvergenceProtocol
- RLC RadioLinkControl
- MAC MediumAccessControl
- PHY Physical
- Processor 1604 may include a digital beamformer module for beamforming.
- the digital beamformer module may include a MultipleInputMultipleOutput (MIMO) encoder and precoder.
- MIMO MultipleInputMultipleOutput
- Memory 1605 is composed of a combination of volatile memory and non-volatile memory.
- the volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof.
- the non-volatile memory is a mask ReadOnlyMemory (MROM), Electrically ErasableProgrammableROM (EEPROM), flash memory, or hard disk drive, or any combination thereof.
- Memory 1605 may include storage located away from processor 1604. In this case, processor 1604 may access memory 1605 via network interface 1603 or an I / O interface (not shown).
- the memory 1605 may store one or more software modules (computer programs) 1606 including instruction groups and data for performing processing by gNB1 described in the plurality of embodiments described above.
- the processor 1604 may be configured to read the software module 1606 from memory 1605 and execute it to perform the processing of gNB1 described in the embodiments described above.
- gNB1 When gNB1 is gNB-CU, gNB1 does not have to include the RF transceiver 1601 (and the antenna array 1602).
- FIG. 17 is a block diagram showing a configuration example of UE2.
- Radio Frequency (RF) transceiver 1701 performs analog RF signal processing to communicate with NG-RAN nodes.
- the RF transceiver 1701 may include a plurality of transceivers.
- the analog RF signal processing performed by the RF transceiver 1701 includes frequency up-conversion, frequency down-conversion, and amplification.
- the RF transceiver 1701 is coupled with the antenna array 1702 and the baseband processor 1703.
- the RF transceiver 1701 receives the modulation symbol data (or OFDM symbol data) from the baseband processor 1703, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 1702.
- the RF transceiver 1701 generates a baseband reception signal based on the reception RF signal received by the antenna array 1702, and supplies the baseband reception signal to the baseband processor 1703.
- the RF transceiver 1701 may include an analog beamformer circuit for beamforming.
- the analog beamformer circuit includes, for example, a plurality of phase shifters and a plurality of power amplifiers.
- Baseband processor 1703 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication.
- Digital baseband signal processing includes (a) data compression / restoration, (b) data segmentation / concatenation, (c) transmission format (transmission frame) generation / decomposition, and (d) transmission path coding / decoding. , (E) Modulation (symbol mapping) / demodulation, and (f) Generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT).
- the control plane processing includes layer 1 (eg, transmission power control), layer 2 (eg, wireless resource management, and hybrid automatic repeat request (HARQ) processing), and layer 3 (eg, attach, mobility, and call management). Includes communication management of).
- digital baseband signal processing by the baseband processor 1703 includes the ServiceDataAdaptationProtocol (SDAP) layer, PacketDataConvergenceProtocol (PDCP) layer, RadioLinkControl (RLC) layer, MediumAccessControl (MAC) layer, and Physical. (PHY) layer signal processing may be included.
- SDAP ServiceDataAdaptationProtocol
- PDCP PacketDataConvergenceProtocol
- RLC RadioLinkControl
- MAC MediumAccessControl
- PHY Physical.
- control plane processing by the baseband processor 1703 may include the processing of the Non-Access Stratum (NAS) protocol, the Radio Resource Control (RRC) protocol, and the MAC Control Elements (CEs).
- NAS Non-Access Stratum
- RRC Radio Resource Control
- CEs MAC Control Elements
- the baseband processor 1703 may perform Multiple Input Multiple Output (MIMO) encoding and precoding for beamforming.
- MIMO Multiple Input Multiple Output
- the baseband processor 1703 includes a modem processor (eg, Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (eg, Central Processing Unit (CPU) or Micro Processing Unit (eg, Central Processing Unit (CPU)) that performs control plane processing. MPU)) may be included.
- DSP Digital Signal Processor
- MPU Central Processing Unit
- the protocol stack processor that performs the control plane processing may be shared with the application processor 1704 described later.
- the application processor 1704 is also called a CPU, MPU, microprocessor, or processor core.
- the application processor 1704 may include a plurality of processors (a plurality of processor cores).
- the application processor 1704 includes a system software program (Operating System (OS)) read from memory 1706 or a memory (not shown) and various application programs (eg, call application, web browser, mailer, camera operation application, music playback). By executing the application), various functions of UE2 are realized.
- OS Operating System
- the baseband processor 1703 and application processor 1704 may be integrated on one chip, as shown by the dashed line (1705) in FIG.
- the baseband processor 1703 and the application processor 1704 may be implemented as one System on Chip (SoC) device 1705.
- SoC devices are sometimes referred to as system Large Scale Integration (LSI) or chipsets.
- the memory 1706 is a volatile memory, a non-volatile memory, or a combination thereof.
- the memory 1706 may include a plurality of physically independent memory devices.
- the volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof.
- the non-volatile memory is a mask ReadOnlyMemory (MROM), Electrically ErasableProgrammableROM (EEPROM), flash memory, or hard disk drive, or any combination thereof.
- MROM ReadOnlyMemory
- EEPROM Electrically ErasableProgrammableROM
- flash memory or hard disk drive, or any combination thereof.
- memory 1706 may include external memory devices accessible from baseband processor 1703, application processor 1704, and SoC 1705.
- the memory 1706 may include internal memory devices integrated within the baseband processor 1703, application processor 1704, or SoC 1705. Further, the memory 1706 may include the memory in the Universal Integrated Circuit Card (UICC).
- UICC Universal
- the memory 1706 may store one or more software modules (computer programs) 1707 that include instructions and data for performing processing by UE2 described in the plurality of embodiments described above.
- the baseband processor 1703 or application processor 1704 is configured to read the software module 1707 from memory 1706 and execute it to perform the UE2 processing described with reference to the drawings in the above embodiments. May be done.
- control plane processing and operation performed by UE2 described in the above-described embodiment is performed by other elements other than the RF transceiver 1701 and the antenna array 1702, that is, at least one of the baseband processor 1703 and the application processor 1704 and the software module 1707. It can be realized by the memory 1706 that stores the above.
- each of the processors included in the gNB1 and UE2 includes one or a group of instructions for causing the computer to perform the algorithm described with reference to the drawings. Run multiple programs.
- This program can be stored and supplied to a computer using various types of non-transitory computer readable medium.
- Non-temporary computer-readable media include various types of tangible storage mediums. Examples of non-temporary computer-readable media include magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical disks), CompactDiscReadOnlyMemory (CD-ROM), CD-ROM.
- the program may also be supplied to the computer by various types of temporary computer readable medium.
- temporary computer-readable media include electrical, optical, and electromagnetic waves.
- the temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.
- UE2 may select whether to use the first initial BWP or the second initial BWP. For example, if UE2 supports the first initial BWP (eg is the bandwidth of the first initial BWP) (that is, it has the ability to communicate with the first initial BWP), then UE2 is the first initial BWP. May be selected and the first initial BWP setting may be applied. On the contrary, if UE2 does not support the first initial BWP (eg is the bandwidth of the first initial BWP) (that is, it does not have the ability to communicate with the first initial BWP), UE2 May select the second initial BWP and apply the second initial BWP setting. UE2 may perform this operation depending on the frequency band. This behavior may be specified in the 3GPP specification.
- the second initial BWP setting in the above-described embodiment may be applied when UE2 performs a handover (also referred to as Reconfiguration with Sync).
- the RRC Reconfiguration message is transmitted from the target gNB that manages the target cell to UE2 via the source gNB that manages the source cell.
- the RRC Reconfiguration message includes the cell-common setting information (ServingCellConfigCommon information element) used by UE2 in the target cell.
- the cell-common setting information includes a downlinkConfigCommon information element including frequency information and cell-common initial DLBWP setting information (initial downlink BWP common configuration).
- the traditional downlinkConfigCommon information element indicates the parameters that match the parameters set in the MIB and SIB1.
- the same initial DL BWP setting as that set in SIB1 of the target cell is sent to the UE in the RRC Reconfiguration message.
- the target gNB may include the second initial DLBWP configuration in the downlinkConfigCommon information element for the second type of UEs.
- the target gNB explicitly or implies that the UE to be handed over is a second type UE, and the handover request (HANDOVER REQUEST) message transmitted by the source gNB indicates that the UE is the second type. It may be recognized by including the information indicated by the target, or it may be recognized by the UE Capability information included in the message.
- the RAN node (eg, gNB1) and the first channel bandwidth set for the first type of UE May set a different second channel bandwidth to the second type of UE.
- the second channel bandwidth may be narrower or the same as the first channel bandwidth.
- the notification of the second channel bandwidth may be based on reference information different from the reference information used for the notification of the first channel bandwidth.
- Reference information may indicate the mapping between frequency band, subcarrier spacing (SCS), and channel bandwidth.
- the channel bandwidth may be represented by a list of DL (or UL) channel bandwidths by subcarrier interval (SCS) (downlinkChannelBW-PerSCS-List (or uplinkChannelBW-PerSCS-List)). ..
- the list may be a list of DL (or UL) channel bandwidth information (SCS-Specific Carrier) for each subcarrier interval (SCS).
- the channel bandwidth information may include subcarrier spacing (SCS), carrier bandwidth (carrier bandwidth), and carrier offset (offsetToCarrier).
- the carrier bandwidth may be information in a predetermined physical resource unit (e.g. Physical Resource Block (PRB)).
- the carrier offset may be an offset value from a predetermined frequency reference point (e.g. Point A).
- the second channel bandwidth is set to the second type of UE, for example by the RRC Setup message in the RRC (connection) setup procedure, or by the RRC Reconfiguration message following the procedure (ie, to the second type of UE). May be sent). More specifically, the second channel bandwidth may be included as new information (e.g. field, parameter) in the ServingCellConfig information element (IE).
- IE ServingCellConfig information element
- gNB1 may broadcast information indicating use cases supported by the cell via system information (e.g., SIB1 or otherSI). In this case, UE2 can access the cell if the applicable or intended use case is supported by the cell.
- UE2 may inform gNB1 of applicable or inverted use cases via the first RRC message (Msg3) after the start of random access, such as the RRCSetupRequest message.
- UE2 may inform gNB1 of applicable or inverted use cases via an RRCSetupComplete message (Msg5).
- the core network e.g., 5GC AMF
- 5GC AMF may inform gNB1 of applicable or inverted use cases for UE2.
- the at least one processor is configured to broadcast the first initial bandwidth part (BWP) setting via system information.
- the at least one processor is configured to broadcast a second initial BWP configuration via said system information or via radio terminal individual signaling.
- the first initial BWP setting includes cell-specific common parameters of the cell's first initial BWP.
- the second initial BWP setting includes cell-specific common parameters of the second initial BWP of the cell.
- the first initial BWP is used by at least the first type of wireless terminal that provides contention-based random access in the cell.
- the second initial BWP is not used by the first type of radio terminal, has limited capabilities as compared to that of the first type of radio terminal, and has contention-based random access in the cell. Used by a second type of wireless terminal that does The bandwidth of the second initial BWP is equal to or narrower than the bandwidth of the first initial BWP.
- RAN node. (Appendix 2)
- the cell-specific common parameters of the first initial BWP include parameters indicating the frequency domain position and bandwidth of the first initial BWP.
- the cell-specific common parameters of the second initial BWP include parameters indicating the frequency domain position and bandwidth of the second initial BWP.
- the cell-specific common parameters of the first initial BWP are used to transmit a Downlink Control Information (DCI) format indicating the resource on which the system information message is broadcast. Contains the Physical Downlink Control Channel (PDCCH) parameter that sets the common search space in the initial BWP.
- the cell-specific common parameters of the second initial BWP set the common search space in the second initial BWP used to send the DCI format indicating the resource on which the system information message is broadcast PDCCH. Including parameters, The RAN node according to Appendix 1 or 2.
- the cell-specific common parameters of the first initial BWP include at least the random access parameters used by the first type of radio terminal for contention-based random access in the first initial BWP.
- the cell-specific common parameters of the second initial BWP include random access parameters used by the second type of radio terminal for contention-based random access in the second initial BWP.
- the RAN node according to any one of Appendix 1 to 3.
- the first initial BWP is used for at least the initial access to the cell by the first type of wireless terminal.
- the second initial BWP is used for initial access to the cell by the second type of wireless terminal.
- the RAN node according to any one of Appendix 1 to 4.
- the first initial BWP is a cell-specific BWP commonly used by at least the first type of wireless terminal.
- the second initial BWP is a cell-specific BWP commonly used by the second type of wireless terminal.
- the RAN node according to any one of Appendix 1 to 5.
- the first initial BWP setting is used when the first type of wireless terminal is in the Radio Resource Control (RRC) _IDLE or RRC_INACTIVE state.
- the second initial BWP setting is used when the second type of wireless terminal is in the RRC_IDLE or RRC_INACTIVE state.
- the RAN node according to any one of Appendix 1 to 6.
- the first initial BWP includes a first initial downlink (DL) BWP and a first initial uplink (UL) BWP.
- the second initial BWP includes a second initial downlink (DL) BWP and a second initial uplink (UL) BWP.
- the RAN node according to any one of Appendix 1 to 7. The at least one processor is configured to broadcast the second initial BWP configuration along with the first initial BWP configuration via the system information.
- the RAN node according to any one of Appendix 1 to 8. The at least one processor will send the second initial BWP configuration to the second type of radio terminal via a Radio Resource Control (RRC) Setup message within a contention-based random access procedure.
- RRC Radio Resource Control
- the RAN node according to any one of Appendix 1 to 8. The RAN node includes at least a Central Unit (CU) that provides Radio Resource Control (RRC) functionality and a Distributed Unit (DU) that provides at least Medium Access Control (MAC) functionality.
- RRC Radio Resource Control
- DU Distributed Unit
- the DU is configured to send a first control message to the CU, including an indication of limited capability, in response to detecting access from the second type of wireless terminal.
- the CU is configured to generate the RRC Setup message including the second initial BWP setting and send a second control message including the RRC Setup message to the DU.
- the RAN node according to Appendix 10.
- the DU is configured to include the second initial BWP setting in the first control message.
- the CU is configured to include the second initial BWP configuration retrieved from the first control message in the RRC Setup message.
- the RAN node according to Appendix 11.
- the at least one processor is configured to transmit the second initial BWP configuration via an RRC Reconfiguration message after the RRC setup of the second type of radio terminal is complete.
- the RAN node according to any one of Appendix 1 to 8.
- the at least one processor receives the capability information of the wireless terminal from the core network and includes the second initial BWP configuration in the RRC Reconfiguration message in response to the capability information indicating limited capability. Composed, The RAN node described in Appendix 13.
- the at least one processor is configured to broadcast radio access network (RAN) area information via system information.
- RAN radio access network
- the RAN area information indicates whether or not to continue using the second initial BWP setting when the second type wireless terminal is in the RRC_IDLE state or the RRC_INACTIVE state after receiving the second initial BWP setting.
- Used by the second type of wireless terminal to determine The RAN node according to any one of Appendix 10 to 14.
- the second type of wireless terminal supports a narrower bandwidth than the bandwidth supported by the first type of wireless terminal.
- at least one processor coupled to the at least one memory
- the at least one processor is configured to receive system information including a first initial bandwidth part (BWP) setting.
- BWP bandwidth part
- the at least one processor is configured to receive a second initial BWP configuration via said system information or via radio terminal individual signaling.
- the at least one processor is configured to use the second initial BWP setting.
- the first initial BWP setting includes cell-specific common parameters of the first initial BWP of the serving cell of the wireless terminal.
- the second initial BWP setting includes cell-specific common parameters of the second initial BWP of the serving cell.
- the first initial BWP is used by at least the first type of wireless terminal that provides contention-based random access in the serving cell.
- the second initial BWP is not used by the first type of radio terminal, has limited capabilities as compared to that of the first type of radio terminal, and has contention-based random access in the serving cell.
- the bandwidth of the second initial BWP is equal to or narrower than the bandwidth of the first initial BWP.
- Wireless terminal. The cell-specific common parameters of the first initial BWP include parameters indicating the frequency domain position and bandwidth of the first initial BWP.
- the cell-specific common parameters of the second initial BWP include parameters indicating the frequency domain position and bandwidth of the second initial BWP.
- the wireless terminal according to Appendix 17. The cell-specific common parameters of the first initial BWP are used to transmit a Downlink Control Information (DCI) format indicating the resource on which the system information message is broadcast. Contains the Physical Downlink Control Channel (PDCCH) parameter that sets the common search space in the initial BWP.
- DCI Downlink Control Information
- PDCCH Physical Downlink Control Channel
- the cell-specific common parameters of the second initial BWP set the common search space in the second initial BWP used to send the DCI format indicating the resource on which the system information message is broadcast PDCCH. Including parameters, The wireless terminal according to Appendix 17 or 18.
- the cell-specific common parameters of the first initial BWP include at least the random access parameters used by the first type of radio terminal for contention-based random access in the first initial BWP.
- the cell-specific common parameters of the second initial BWP include random access parameters used by the second type of radio terminal for contention-based random access in the second initial BWP.
- the wireless terminal according to any one of Appendix 17 to 19.
- the first initial BWP is used for initial access to the serving cell by at least the first type of wireless terminal.
- the second initial BWP is used for initial access to the serving cell by the second type of wireless terminal.
- the wireless terminal according to any one of Appendix 17 to 20.
- the first initial BWP is a cell-specific BWP commonly used by at least the first type of wireless terminal.
- the second initial BWP is a cell-specific BWP commonly used by the second type of wireless terminal.
- the wireless terminal according to any one of Appendix 17 to 21.
- the first initial BWP setting is used when the first type of wireless terminal is in the Radio Resource Control (RRC) _IDLE or RRC_INACTIVE state.
- RRC Radio Resource Control
- the second initial BWP setting is used when the second type of wireless terminal is in the RRC_IDLE or RRC_INACTIVE state.
- the wireless terminal according to any one of Appendix 17 to 22.
- the first initial BWP includes a first initial downlink (DL) BWP and a first initial uplink (UL) BWP.
- the second initial BWP includes a second initial downlink (DL) BWP and a second initial uplink (UL) BWP.
- the at least one processor is configured to receive the second initial BWP configuration along with the first initial BWP configuration via the system information.
- the wireless terminal according to any one of Appendix 17 to 24.
- the at least one processor is configured to receive the second initial BWP configuration via a Radio Resource Control (RRC) Setup message within a contention-based random access procedure.
- the wireless terminal according to any one of Appendix 17 to 24.
- the at least one processor is configured to receive the second initial BWP configuration via an RRC Reconfiguration message after the RRC setup is complete.
- the wireless terminal according to any one of Appendix 17 to 24.
- the at least one processor is configured to receive radio access network (RAN) area information via system information. The at least one processor determines whether to continue using the second initial BWP setting when the wireless terminal is in the RRC_IDLE state or the RRC_INACTIVE state after receiving the second initial BWP setting.
- RAN radio access network
- the wireless terminal according to Appendix 26 or 27.
- the at least one processor is restricted in response to receiving an RRC Setup message from the network to establish a new RRC connection despite initiating the RRC connection reopening or RRC connection reestablishing procedure. Configured to send an RRC Setup complete message to the network, including an indication of the capabilities
- the second type of wireless terminal supports a narrower bandwidth than the bandwidth supported by the first type of wireless terminal.
- RAN Radio Access Network
- the first initial bandwidth part (BWP) setting is broadcast via system information
- the second initial BWP setting is broadcast via said system information or transmitted via signaling for each wireless terminal.
- the first initial BWP setting includes cell-specific common parameters of the cell's first initial BWP.
- the second initial BWP setting includes cell-specific common parameters of the second initial BWP of the cell.
- the first initial BWP is used by at least the first type of wireless terminal that provides contention-based random access in the cell.
- the second initial BWP is not used by the first type of radio terminal, has limited capabilities as compared to that of the first type of radio terminal, and has contention-based random access in the cell.
- the bandwidth of the second initial BWP is equal to or narrower than the bandwidth of the first initial BWP.
- Method. It is a method performed by a wireless terminal, Receiving system information, including the first initial bandwidth part (BWP) setting, Receiving the second initial BWP setting via the system information or via the radio terminal individual signaling, and using the second initial BWP setting.
- the first initial BWP setting includes cell-specific common parameters of the first initial BWP of the serving cell of the wireless terminal.
- the second initial BWP setting includes cell-specific common parameters of the second initial BWP of the serving cell.
- the first initial BWP is used by at least the first type of wireless terminal that provides contention-based random access in the serving cell.
- the second initial BWP is not used by the first type of radio terminal, has limited capabilities as compared to that of the first type of radio terminal, and has contention-based random access in the serving cell. Used by a second type of wireless terminal that does The bandwidth of the second initial BWP is equal to or narrower than the bandwidth of the first initial BWP.
- Method. (Appendix 33) A program that lets a computer do the method for a Radio Access Network (RAN) node. The method is The first initial bandwidth part (BWP) setting is broadcast via system information, and the second initial BWP setting is broadcast via said system information or transmitted via signaling for each wireless terminal. matter, With The first initial BWP setting includes cell-specific common parameters of the cell's first initial BWP.
- the second initial BWP setting includes cell-specific common parameters of the second initial BWP of the cell.
- the first initial BWP is used by at least the first type of wireless terminal that provides contention-based random access in the cell.
- the second initial BWP is not used by the first type of radio terminal, has limited capabilities as compared to that of the first type of radio terminal, and has contention-based random access in the cell. Used by a second type of wireless terminal that does The bandwidth of the second initial BWP is equal to or narrower than the bandwidth of the first initial BWP. program.
- the method is Receiving system information, including the first initial bandwidth part (BWP) setting, Receiving the second initial BWP setting via the system information or via the radio terminal individual signaling, and using the second initial BWP setting.
- the first initial BWP setting includes cell-specific common parameters of the first initial BWP of the serving cell of the wireless terminal.
- the second initial BWP setting includes cell-specific common parameters of the second initial BWP of the serving cell.
- the first initial BWP is used by at least the first type of wireless terminal that provides contention-based random access in the serving cell.
- the second initial BWP is not used by the first type of radio terminal, has limited capabilities as compared to that of the first type of radio terminal, and has contention-based random access in the serving cell. Used by a second type of wireless terminal that does The bandwidth of the second initial BWP is equal to or narrower than the bandwidth of the first initial BWP. program.
- gNB 2 UE 11 Central Unit (CU) 12 Distributed Unit (DU) 1504 Processor 1505 Memory 1506 Modules 1603 Baseband Processor 1604 Application Processor 1606 Memory 1607 Modules
Abstract
Description
(a)第1のイニシャルbandwidth part(BWP)設定を、システム情報を介してブロードキャストすること、及び
(b)第2のイニシャルBWP設定を、前記システム情報を介してブロードキャストするか又は無線端末個別のシグナリングを介して送信すること。
(a)第1のイニシャルbandwidth part(BWP)設定を包含するシステム情報を受信すること、
(b)第2のイニシャルBWP設定を、前記システム情報を介して又は無線端末個別のシグナリングを介して受信すること、及び
(c)前記第2のイニシャルBWP設定を使用すること。
図1は、本実施形態を含む幾つかの実施形態に係る無線通信ネットワーク(i.e., 5GS)の構成例を示している。図1の例では、無線通信ネットワークは、無線アクセスネットワーク(Radio Access Network(RAN))ノード(i.e., gNB)1及び1又はそれ以上の無線端末(i.e., UEs)2を含む。gNB1は、RAN(i.e., Next Generation (NG) RAN)に配置される。gNB1は、cloud RAN(C-RAN)配置(deployment)におけるgNB Central Unit(gNB-CU)及び1又は複数のgNB Distributed Unit(gNB-DU)を含んでもよい。gNB1は、セル10を複数のタイプのUEsに提供する。これら複数のタイプのUEsは、セル10をサービングセルとして使用し、コンテンション・ベースド・ランダムアクセス(Contention Based Random Access (CBRA))をセル10において行う。gNB1は、1又はそれ以上の他のセルをさらに提供してもよい。この場合、セル10は、キャリアアグリゲーション(Carrier Aggregation (CA))のprimary cell (PCell)であってもよく、1又はそれ以上の他のセルはsecondary cells(SCells)であってもよい。すなわち、セル10は、は、UEs2が、イニシャル(RRC)コネクション確立手順を行う又は(RRC)コネクション再確立手順を開始するセルである。
本実施形態は、第1の実施形態で説明された第1及び第2のイニシャルBWP設定の送信の具体例を提供する。本実施形態に係る無線通信ネットワークの構成例は、図1に示された例と同様である。
本実施形態は、第1の実施形態で説明された第1及び第2のイニシャルBWP設定の送信の具体例を提供する。本実施形態に係る無線通信ネットワークの構成例は、図1に示された例と同様である。本実施形態での第1及び第2のイニシャルBWPの定義及び用途は、第1の実施形態で説明された例と同様である。第1及び第2のイニシャルBWP設定の具体例も、第1の実施形態で説明された例と同様である。
本実施形態は、第1の実施形態で説明された第1及び第2のイニシャルBWP設定の送信の具体例を提供する。本実施形態に係る無線通信ネットワークの構成例は、図1に示された例と同様である。本実施形態での第1及び第2のイニシャルBWPの定義及び用途は、第1の実施形態で説明された例と同様である。第1及び第2のイニシャルBWP設定の具体例も、第1の実施形態で説明された例と同様である。
本実施形態に係る無線通信ネットワークの構成例は、図1に示された例と同様である。本実施形態での第1及び第2のイニシャルBWPの定義及び用途は、第1の実施形態で説明された例と同様である。第1及び第2のイニシャルBWP設定の具体例も、第1の実施形態で説明された例と同様である。本実施形態は、第3及び第4の実施形態で説明されたUE2の動作の具体例を提供する。
本実施形態に係る無線通信ネットワークの構成例は、図1に示された例と同様である。本実施形態での第1及び第2のイニシャルBWPの定義及び用途は、第1の実施形態で説明された例と同様である。第1及び第2のイニシャルBWP設定の具体例も、第1の実施形態で説明された例と同様である。本実施形態は、第3及び第4の実施形態で説明されたgNB1及びUE2の動作の具体例を提供する。
本実施形態に係る無線通信ネットワークの構成例は、図1に示された例と同様である。本実施形態での第1及び第2のイニシャルBWPの定義及び用途は、第1の実施形態で説明された例と同様である。第1及び第2のイニシャルBWP設定の具体例も、第1の実施形態で説明された例と同様である。
本実施形態に係る無線通信ネットワークの構成例は、図1に示された例と同様である。本実施形態での第1及び第2のイニシャルBWPの定義及び用途は、第1の実施形態で説明された例と同様である。第1及び第2のイニシャルBWP設定の具体例も、第1の実施形態で説明された例と同様である。
上述の実施形態は、各々独立に実施されてもよいし、実施形態全体又はその一部が適宜組み合わせて実施されてもよい。
Radio Access Network(RAN)ノードであって、
少なくとも1つのメモリと、
前記少なくとも1つのメモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、第1のイニシャルbandwidth part(BWP)設定を、システム情報を介してブロードキャストするよう構成され、
前記少なくとも1つのプロセッサは、第2のイニシャルBWP設定を、前記システム情報を介してブロードキャストするか又は無線端末個別のシグナリングを介して送信するよう構成され、
前記第1のイニシャルBWP設定は、セルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記セルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
RANノード。
(付記2)
前記第1のイニシャルBWPの前記セル固有の共通パラメータは、前記第1のイニシャルBWPの周波数ドメイン位置及び帯域幅を示すパラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、前記第2のイニシャルBWPの周波数ドメイン位置及び帯域幅を示すパラメータを含む、
付記1に記載のRANノード。
(付記3)
前記第1のイニシャルBWPの前記セル固有の共通パラメータは、システム情報メッセージがブロードキャストされるリソースを示すダウンリンク制御情報(Downlink Control Information(DCI))フォーマットを送信するために使用される前記第1のイニシャルBWP内のcommon search spaceを設定するPhysical Downlink Control Channel(PDCCH)パラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、システム情報メッセージがブロードキャストされるリソースを示すDCIフォーマットを送信するために使用される前記第2のイニシャルBWP内のcommon search spaceを設定するPDCCHパラメータを含む、
付記1又は2に記載のRANノード。
(付記4)
前記第1のイニシャルBWPの前記セル固有の共通パラメータは、少なくとも前記第1のタイプの無線端末が前記第1のイニシャルBWPにおけるコンテンション・ベースド・ランダムアクセスのために使用するランダムアクセス・パラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、前記第2のタイプの無線端末が前記第2のイニシャルBWPにおけるコンテンション・ベースド・ランダムアクセスのために使用するランダムアクセス・パラメータを含む、
付記1~3のいずれか1項に記載のRANノード。
(付記5)
前記第1のイニシャルBWPは、少なくとも前記第1のタイプの無線端末による前記セルへのイニシャルアクセスのために使用され、
前記第2のイニシャルBWPは、前記第2のタイプの無線端末による前記セルへのイニシャルアクセスのために使用される、
付記1~4のいずれか1項に記載のRANノード。
(付記6)
前記第1のイニシャルBWPは、少なくとも前記第1のタイプの無線端末により共通に使用されるセル固有のBWPであり、
前記第2のイニシャルBWPは、前記第2のタイプの無線端末により共通に使用されるセル固有のBWPである、
付記1~5のいずれか1項に記載のRANノード。
(付記7)
前記第1のイニシャルBWP設定は、前記第1のタイプの無線端末が、Radio Resource Control (RRC)_IDLE状態又はRRC_INACTIVE状態であるときに使用され、
前記第2のイニシャルBWP設定は、前記第2のタイプの無線端末が、RRC_IDLE状態又はRRC_INACTIVE状態であるときに使用される、
付記1~6のいずれか1項に記載のRANノード。
(付記8)
前記第1のイニシャルBWPは、第1のイニシャル・ダウンリンク(DL)BWP及び第1のイニシャル・アップリンク(UL)BWPを含み、
前記第2のイニシャルBWPは、第2のイニシャル・ダウンリンク(DL)BWP及び第2のイニシャル・アップリンク(UL)BWPを含む、
付記1~7のいずれか1項に記載のRANノード。
(付記9)
前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、前記第1のイニシャルBWP設定と共に、前記システム情報を介してブロードキャストするよう構成される、
付記1~8のいずれか1項に記載のRANノード。
(付記10)
前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、前記第2のタイプの無線端末に、コンテンション・ベースド・ランダムアクセス手順内においてRadio Resource Control(RRC)Setupメッセージを介して送信するよう構成される、
付記1~8のいずれか1項に記載のRANノード。
(付記11)
前記RANノードは、少なくともRadio Resource Control(RRC)機能を提供するCentral Unit(CU)と、少なくともMedium Access Control(MAC)機能を提供するDistributed Unit(DU)とを備え、
前記DUは、前記第2のタイプの無線端末からのアクセスを検出したことに応答して、制限された能力を示す表示を含む第1の制御メッセージを前記CUに送るよう構成され、
前記CUは、前記表示の受信に応答して、前記第2のイニシャルBWP設定を包含する前記RRC Setupメッセージを生成し、前記RRC Setupメッセージを包含する第2の制御メッセージを前記DUに送るよう構成される、
付記10に記載のRANノード。
(付記12)
前記DUは、前記第2のイニシャルBWP設定を前記第1の制御メッセージに含めるよう構成され、
前記CUは、前記第1の制御メッセージから取り出された前記第2のイニシャルBWP設定を前記RRC Setupメッセージに含めるよう構成される、
付記11に記載のRANノード。
(付記13)
前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、前記第2のタイプの無線端末のRRCセットアップの完了後にRRC Reconfigurationメッセージを介して送信するよう構成される、
付記1~8のいずれか1項に記載のRANノード。
(付記14)
前記少なくとも1つのプロセッサは、無線端末の能力情報をコアネットワークから受信し、前記能力情報が制限された能力を示すことに応答して、前記第2のイニシャルBWP設定を前記RRC Reconfigurationメッセージに含めるよう構成される、
付記13に記載のRANノード。
(付記15)
前記少なくとも1つのプロセッサは、無線アクセスネットワーク(RAN)エリア情報を、システム情報を介してブロードキャストするよう構成され、
前記RANエリア情報は、前記第2のタイプの無線端末が前記第2のイニシャルBWP設定を受信した後にRRC_IDLE状態又はRRC_INACTIVE状態であるときに、前記第2のイニシャルBWP設定の使用を継続する否かを判定するために前記第2のタイプの無線端末によって使用される、
付記10~14のいずれか1項に記載のRANノード。
(付記16)
前記第2のタイプの無線端末は、前記第1のタイプの無線端末がサポートする帯域幅に比べて狭い帯域幅をサポートする、
付記1~15のいずれか1項に記載のRANノード。
(付記17)
無線端末であって、
少なくとも1つのメモリと、
前記少なくとも1つのメモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、第1のイニシャルbandwidth part(BWP)設定を包含するシステム情報を受信するよう構成され、
前記少なくとも1つのプロセッサは、第2のイニシャルBWP設定を、前記システム情報を介して又は無線端末個別のシグナリングを介して受信するよう構成され、
前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を使用するよう構成され、
前記第1のイニシャルBWP設定は、前記無線端末のサービングセルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記サービングセルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
無線端末。
(付記18)
前記第1のイニシャルBWPの前記セル固有の共通パラメータは、前記第1のイニシャルBWPの周波数ドメイン位置及び帯域幅を示すパラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、前記第2のイニシャルBWPの周波数ドメイン位置及び帯域幅を示すパラメータを含む、
付記17に記載の無線端末。
(付記19)
前記第1のイニシャルBWPの前記セル固有の共通パラメータは、システム情報メッセージがブロードキャストされるリソースを示すダウンリンク制御情報(Downlink Control Information(DCI))フォーマットを送信するために使用される前記第1のイニシャルBWP内のcommon search spaceを設定するPhysical Downlink Control Channel(PDCCH)パラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、システム情報メッセージがブロードキャストされるリソースを示すDCIフォーマットを送信するために使用される前記第2のイニシャルBWP内のcommon search spaceを設定するPDCCHパラメータを含む、
付記17又は18に記載の無線端末。
(付記20)
前記第1のイニシャルBWPの前記セル固有の共通パラメータは、少なくとも前記第1のタイプの無線端末が前記第1のイニシャルBWPにおけるコンテンション・ベースド・ランダムアクセスのために使用するランダムアクセス・パラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、前記第2のタイプの無線端末が前記第2のイニシャルBWPにおけるコンテンション・ベースド・ランダムアクセスのために使用するランダムアクセス・パラメータを含む、
付記17~19のいずれか1項に記載の無線端末。
(付記21)
前記第1のイニシャルBWPは、少なくとも前記第1のタイプの無線端末による前記サービングセルへのイニシャルアクセスのために使用され、
前記第2のイニシャルBWPは、前記第2のタイプの無線端末による前記サービングセルへのイニシャルアクセスのために使用される、
付記17~20のいずれか1項に記載の無線端末。
(付記22)
前記第1のイニシャルBWPは、少なくとも前記第1のタイプの無線端末により共通に使用されるセル固有のBWPであり、
前記第2のイニシャルBWPは、前記第2のタイプの無線端末により共通に使用されるセル固有のBWPである、
付記17~21のいずれか1項に記載の無線端末。
(付記23)
前記第1のイニシャルBWP設定は、前記第1のタイプの無線端末が、Radio Resource Control (RRC)_IDLE状態又はRRC_INACTIVE状態であるときに使用され、
前記第2のイニシャルBWP設定は、前記第2のタイプの無線端末が、RRC_IDLE状態又はRRC_INACTIVE状態であるときに使用される、
付記17~22のいずれか1項に記載の無線端末。
(付記24)
前記第1のイニシャルBWPは、第1のイニシャル・ダウンリンク(DL)BWP及び第1のイニシャル・アップリンク(UL)BWPを含み、
前記第2のイニシャルBWPは、第2のイニシャル・ダウンリンク(DL)BWP及び第2のイニシャル・アップリンク(UL)BWPを含む、
付記17~23のいずれか1項に記載の無線端末。
(付記25)
前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、前記第1のイニシャルBWP設定と共に、前記システム情報を介して受信するよう構成される、
付記17~24のいずれか1項に記載の無線端末。
(付記26)
前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、コンテンション・ベースド・ランダムアクセス手順内においてRadio Resource Control(RRC)Setupメッセージを介して受信するよう構成される、
付記17~24のいずれか1項に記載の無線端末。
(付記27)
前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、RRCセットアップの完了後にRRC Reconfigurationメッセージを介して受信するよう構成される、
付記17~24のいずれか1項に記載の無線端末。
(付記28)
前記少なくとも1つのプロセッサは、無線アクセスネットワーク(RAN)エリア情報を、システム情報を介して受信するよう構成され、
前記少なくとも1つのプロセッサは、前記無線端末が前記第2のイニシャルBWP設定を受信した後にRRC_IDLE状態又はRRC_INACTIVE状態であるときに、前記第2のイニシャルBWP設定の使用を継続する否かを判定するために前記RANエリア情報を使用するよう構成される、
付記26又は27に記載の無線端末。
(付記29)
前記少なくとも1つのプロセッサは、RRCコネクション再開手順又はRRCコネクション再確立手順を開始したにもかかわらず、新たなRRCコネクションの確立のためのRRC Setupメッセージをネットワークから受信したことに応答して、制限された能力を示す表示を含むRRC Setup completeメッセージを前記ネットワークに送信するよう構成される、
付記17~28のいずれか1項に記載の無線端末。
(付記30)
前記第2のタイプの無線端末は、前記第1のタイプの無線端末がサポートする帯域幅に比べて狭い帯域幅をサポートする、
付記17~29のいずれか1項に記載の無線端末。
(付記31)
Radio Access Network(RAN)ノードにより行われる方法であって、
第1のイニシャルbandwidth part(BWP)設定を、システム情報を介してブロードキャストすること、及び
第2のイニシャルBWP設定を、前記システム情報を介してブロードキャストするか又は無線端末個別のシグナリングを介して送信すること、
を備え、
前記第1のイニシャルBWP設定は、セルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記セルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
方法。
(付記32)
無線端末により行われる方法であって、
第1のイニシャルbandwidth part(BWP)設定を包含するシステム情報を受信すること、
第2のイニシャルBWP設定を、前記システム情報を介して又は無線端末個別のシグナリングを介して受信すること、及び
前記第2のイニシャルBWP設定を使用すること、
を備え、
前記第1のイニシャルBWP設定は、前記無線端末のサービングセルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記サービングセルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
方法。
(付記33)
Radio Access Network(RAN)ノードのための方法をコンピュータに行わせるためのプログラムであって、
前記方法は、
第1のイニシャルbandwidth part(BWP)設定を、システム情報を介してブロードキャストすること、及び
第2のイニシャルBWP設定を、前記システム情報を介してブロードキャストするか又は無線端末個別のシグナリングを介して送信すること、
を備え、
前記第1のイニシャルBWP設定は、セルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記セルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
プログラム。
(付記34)
無線端末のための方法をコンピュータに行わせるためのプログラムであって、
前記方法は、
第1のイニシャルbandwidth part(BWP)設定を包含するシステム情報を受信すること、
第2のイニシャルBWP設定を、前記システム情報を介して又は無線端末個別のシグナリングを介して受信すること、及び
前記第2のイニシャルBWP設定を使用すること、
を備え、
前記第1のイニシャルBWP設定は、前記無線端末のサービングセルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記サービングセルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
プログラム。
2 UE
11 Central Unit (CU)
12 Distributed Unit (DU)
1504 プロセッサ
1505 メモリ
1506 モジュール(modules)
1603 ベースバンドプロセッサ
1604 アプリケーションプロセッサ
1606 メモリ
1607 モジュール(modules)
Claims (34)
- Radio Access Network(RAN)ノードであって、
少なくとも1つのメモリと、
前記少なくとも1つのメモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、第1のイニシャルbandwidth part(BWP)設定を、システム情報を介してブロードキャストするよう構成され、
前記少なくとも1つのプロセッサは、第2のイニシャルBWP設定を、前記システム情報を介してブロードキャストするか又は無線端末個別のシグナリングを介して送信するよう構成され、
前記第1のイニシャルBWP設定は、セルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記セルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
RANノード。 - 前記第1のイニシャルBWPの前記セル固有の共通パラメータは、前記第1のイニシャルBWPの周波数ドメイン位置及び帯域幅を示すパラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、前記第2のイニシャルBWPの周波数ドメイン位置及び帯域幅を示すパラメータを含む、
請求項1に記載のRANノード。 - 前記第1のイニシャルBWPの前記セル固有の共通パラメータは、システム情報メッセージがブロードキャストされるリソースを示すダウンリンク制御情報(Downlink Control Information(DCI))フォーマットを送信するために使用される前記第1のイニシャルBWP内のcommon search spaceを設定するPhysical Downlink Control Channel(PDCCH)パラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、システム情報メッセージがブロードキャストされるリソースを示すDCIフォーマットを送信するために使用される前記第2のイニシャルBWP内のcommon search spaceを設定するPDCCHパラメータを含む、
請求項1又は2に記載のRANノード。 - 前記第1のイニシャルBWPの前記セル固有の共通パラメータは、少なくとも前記第1のタイプの無線端末が前記第1のイニシャルBWPにおけるコンテンション・ベースド・ランダムアクセスのために使用するランダムアクセス・パラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、前記第2のタイプの無線端末が前記第2のイニシャルBWPにおけるコンテンション・ベースド・ランダムアクセスのために使用するランダムアクセス・パラメータを含む、
請求項1~3のいずれか1項に記載のRANノード。 - 前記第1のイニシャルBWPは、少なくとも前記第1のタイプの無線端末による前記セルへのイニシャルアクセスのために使用され、
前記第2のイニシャルBWPは、前記第2のタイプの無線端末による前記セルへのイニシャルアクセスのために使用される、
請求項1~4のいずれか1項に記載のRANノード。 - 前記第1のイニシャルBWPは、少なくとも前記第1のタイプの無線端末により共通に使用されるセル固有のBWPであり、
前記第2のイニシャルBWPは、前記第2のタイプの無線端末により共通に使用されるセル固有のBWPである、
請求項1~5のいずれか1項に記載のRANノード。 - 前記第1のイニシャルBWP設定は、前記第1のタイプの無線端末が、Radio Resource Control (RRC)_IDLE状態又はRRC_INACTIVE状態であるときに使用され、
前記第2のイニシャルBWP設定は、前記第2のタイプの無線端末が、RRC_IDLE状態又はRRC_INACTIVE状態であるときに使用される、
請求項1~6のいずれか1項に記載のRANノード。 - 前記第1のイニシャルBWPは、第1のイニシャル・ダウンリンク(DL)BWP及び第1のイニシャル・アップリンク(UL)BWPを含み、
前記第2のイニシャルBWPは、第2のイニシャル・ダウンリンク(DL)BWP及び第2のイニシャル・アップリンク(UL)BWPを含む、
請求項1~7のいずれか1項に記載のRANノード。 - 前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、前記第1のイニシャルBWP設定と共に、前記システム情報を介してブロードキャストするよう構成される、
請求項1~8のいずれか1項に記載のRANノード。 - 前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、前記第2のタイプの無線端末に、コンテンション・ベースド・ランダムアクセス手順内においてRadio Resource Control(RRC)Setupメッセージを介して送信するよう構成される、
請求項1~8のいずれか1項に記載のRANノード。 - 前記RANノードは、少なくともRadio Resource Control(RRC)機能を提供するCentral Unit(CU)と、少なくともMedium Access Control(MAC)機能を提供するDistributed Unit(DU)とを備え、
前記DUは、前記第2のタイプの無線端末からのアクセスを検出したことに応答して、制限された能力を示す表示を含む第1の制御メッセージを前記CUに送るよう構成され、
前記CUは、前記表示の受信に応答して、前記第2のイニシャルBWP設定を包含する前記RRC Setupメッセージを生成し、前記RRC Setupメッセージを包含する第2の制御メッセージを前記DUに送るよう構成される、
請求項10に記載のRANノード。 - 前記DUは、前記第2のイニシャルBWP設定を前記第1の制御メッセージに含めるよう構成され、
前記CUは、前記第1の制御メッセージから取り出された前記第2のイニシャルBWP設定を前記RRC Setupメッセージに含めるよう構成される、
請求項11に記載のRANノード。 - 前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、前記第2のタイプの無線端末のRRCセットアップの完了後にRRC Reconfigurationメッセージを介して送信するよう構成される、
請求項1~8のいずれか1項に記載のRANノード。 - 前記少なくとも1つのプロセッサは、無線端末の能力情報をコアネットワークから受信し、前記能力情報が制限された能力を示すことに応答して、前記第2のイニシャルBWP設定を前記RRC Reconfigurationメッセージに含めるよう構成される、
請求項13に記載のRANノード。 - 前記少なくとも1つのプロセッサは、無線アクセスネットワーク(RAN)エリア情報を、システム情報を介してブロードキャストするよう構成され、
前記RANエリア情報は、前記第2のタイプの無線端末が前記第2のイニシャルBWP設定を受信した後にRRC_IDLE状態又はRRC_INACTIVE状態であるときに、前記第2のイニシャルBWP設定の使用を継続する否かを判定するために前記第2のタイプの無線端末によって使用される、
請求項10~14のいずれか1項に記載のRANノード。 - 前記第2のタイプの無線端末は、前記第1のタイプの無線端末がサポートする帯域幅に比べて狭い帯域幅をサポートする、
請求項1~15のいずれか1項に記載のRANノード。 - 無線端末であって、
少なくとも1つのメモリと、
前記少なくとも1つのメモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、第1のイニシャルbandwidth part(BWP)設定を包含するシステム情報を受信するよう構成され、
前記少なくとも1つのプロセッサは、第2のイニシャルBWP設定を、前記システム情報を介して又は無線端末個別のシグナリングを介して受信するよう構成され、
前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を使用するよう構成され、
前記第1のイニシャルBWP設定は、前記無線端末のサービングセルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記サービングセルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
無線端末。 - 前記第1のイニシャルBWPの前記セル固有の共通パラメータは、前記第1のイニシャルBWPの周波数ドメイン位置及び帯域幅を示すパラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、前記第2のイニシャルBWPの周波数ドメイン位置及び帯域幅を示すパラメータを含む、
請求項17に記載の無線端末。 - 前記第1のイニシャルBWPの前記セル固有の共通パラメータは、システム情報メッセージがブロードキャストされるリソースを示すダウンリンク制御情報(Downlink Control Information(DCI))フォーマットを送信するために使用される前記第1のイニシャルBWP内のcommon search spaceを設定するPhysical Downlink Control Channel(PDCCH)パラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、システム情報メッセージがブロードキャストされるリソースを示すDCIフォーマットを送信するために使用される前記第2のイニシャルBWP内のcommon search spaceを設定するPDCCHパラメータを含む、
請求項17又は18に記載の無線端末。 - 前記第1のイニシャルBWPの前記セル固有の共通パラメータは、少なくとも前記第1のタイプの無線端末が前記第1のイニシャルBWPにおけるコンテンション・ベースド・ランダムアクセスのために使用するランダムアクセス・パラメータを含み、
前記第2のイニシャルBWPの前記セル固有の共通パラメータは、前記第2のタイプの無線端末が前記第2のイニシャルBWPにおけるコンテンション・ベースド・ランダムアクセスのために使用するランダムアクセス・パラメータを含む、
請求項17~19のいずれか1項に記載の無線端末。 - 前記第1のイニシャルBWPは、少なくとも前記第1のタイプの無線端末による前記サービングセルへのイニシャルアクセスのために使用され、
前記第2のイニシャルBWPは、前記第2のタイプの無線端末による前記サービングセルへのイニシャルアクセスのために使用される、
請求項17~20のいずれか1項に記載の無線端末。 - 前記第1のイニシャルBWPは、少なくとも前記第1のタイプの無線端末により共通に使用されるセル固有のBWPであり、
前記第2のイニシャルBWPは、前記第2のタイプの無線端末により共通に使用されるセル固有のBWPである、
請求項17~21のいずれか1項に記載の無線端末。 - 前記第1のイニシャルBWP設定は、前記第1のタイプの無線端末が、Radio Resource Control (RRC)_IDLE状態又はRRC_INACTIVE状態であるときに使用され、
前記第2のイニシャルBWP設定は、前記第2のタイプの無線端末が、RRC_IDLE状態又はRRC_INACTIVE状態であるときに使用される、
請求項17~22のいずれか1項に記載の無線端末。 - 前記第1のイニシャルBWPは、第1のイニシャル・ダウンリンク(DL)BWP及び第1のイニシャル・アップリンク(UL)BWPを含み、
前記第2のイニシャルBWPは、第2のイニシャル・ダウンリンク(DL)BWP及び第2のイニシャル・アップリンク(UL)BWPを含む、
請求項17~23のいずれか1項に記載の無線端末。 - 前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、前記第1のイニシャルBWP設定と共に、前記システム情報を介して受信するよう構成される、
請求項17~24のいずれか1項に記載の無線端末。 - 前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、コンテンション・ベースド・ランダムアクセス手順内においてRadio Resource Control(RRC)Setupメッセージを介して受信するよう構成される、
請求項17~24のいずれか1項に記載の無線端末。 - 前記少なくとも1つのプロセッサは、前記第2のイニシャルBWP設定を、RRCセットアップの完了後にRRC Reconfigurationメッセージを介して受信するよう構成される、
請求項17~24のいずれか1項に記載の無線端末。 - 前記少なくとも1つのプロセッサは、無線アクセスネットワーク(RAN)エリア情報を、システム情報を介して受信するよう構成され、
前記少なくとも1つのプロセッサは、前記無線端末が前記第2のイニシャルBWP設定を受信した後にRRC_IDLE状態又はRRC_INACTIVE状態であるときに、前記第2のイニシャルBWP設定の使用を継続する否かを判定するために前記RANエリア情報を使用するよう構成される、
請求項26又は27に記載の無線端末。 - 前記少なくとも1つのプロセッサは、RRCコネクション再開手順又はRRCコネクション再確立手順を開始したにもかかわらず、新たなRRCコネクションの確立のためのRRC Setupメッセージをネットワークから受信したことに応答して、制限された能力を示す表示を含むRRC Setup completeメッセージを前記ネットワークに送信するよう構成される、
請求項17~28のいずれか1項に記載の無線端末。 - 前記第2のタイプの無線端末は、前記第1のタイプの無線端末がサポートする帯域幅に比べて狭い帯域幅をサポートする、
請求項17~29のいずれか1項に記載の無線端末。 - Radio Access Network(RAN)ノードにより行われる方法であって、
第1のイニシャルbandwidth part(BWP)設定を、システム情報を介してブロードキャストすること、及び
第2のイニシャルBWP設定を、前記システム情報を介してブロードキャストするか又は無線端末個別のシグナリングを介して送信すること、
を備え、
前記第1のイニシャルBWP設定は、セルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記セルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
方法。 - 無線端末により行われる方法であって、
第1のイニシャルbandwidth part(BWP)設定を包含するシステム情報を受信すること、
第2のイニシャルBWP設定を、前記システム情報を介して又は無線端末個別のシグナリングを介して受信すること、及び
前記第2のイニシャルBWP設定を使用すること、
を備え、
前記第1のイニシャルBWP設定は、前記無線端末のサービングセルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記サービングセルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
方法。 - Radio Access Network(RAN)ノードのための方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体であって、
前記方法は、
第1のイニシャルbandwidth part(BWP)設定を、システム情報を介してブロードキャストすること、及び
第2のイニシャルBWP設定を、前記システム情報を介してブロードキャストするか又は無線端末個別のシグナリングを介して送信すること、
を備え、
前記第1のイニシャルBWP設定は、セルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記セルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記セルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
非一時的なコンピュータ可読媒体。 - 無線端末のための方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体であって、
前記方法は、
第1のイニシャルbandwidth part(BWP)設定を包含するシステム情報を受信すること、
第2のイニシャルBWP設定を、前記システム情報を介して又は無線端末個別のシグナリングを介して受信すること、及び
前記第2のイニシャルBWP設定を使用すること、
を備え、
前記第1のイニシャルBWP設定は、前記無線端末のサービングセルの第1のイニシャルBWPのセル固有(cell-specific)の共通パラメータ(parameters)を含み、
前記第2のイニシャルBWP設定は、前記サービングセルの第2のイニシャルBWPのセル固有の共通パラメータを含み、
前記第1のイニシャルBWPは、前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う少なくとも第1のタイプの無線端末によって使用され、
前記第2のイニシャルBWPは、前記第1のタイプの無線端末によって使用されず、前記第1のタイプの無線端末のそれに比べて制限された能力を持ち且つ前記サービングセルにおいてコンテンション・ベースド・ランダムアクセスを行う第2のタイプの無線端末によって使用され、
前記第2のイニシャルBWPの帯域幅(bandwidth)は前記第1のイニシャルBWPの帯域幅と同じかそれよりも狭い、
非一時的なコンピュータ可読媒体。
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR112022015308A BR112022015308A2 (pt) | 2020-02-13 | 2020-11-30 | Nó de ran, ue, e métodos para os mesmos |
JP2022500237A JP7439895B2 (ja) | 2020-02-13 | 2020-11-30 | User Equipment(UE)の方法、UE、及び基地局の方法 |
US17/629,843 US20220287102A1 (en) | 2020-02-13 | 2020-11-30 | Ran node, radio terminal, and methods therefor |
EP20919126.1A EP3993540A4 (en) | 2020-02-13 | 2020-11-30 | RAN NODE, USER DEVICE AND METHOD THEREOF |
CN202080099712.7A CN115428550A (zh) | 2020-02-13 | 2020-11-30 | Ran节点、无线电终端及其方法 |
JP2024018260A JP2024036676A (ja) | 2020-02-13 | 2024-02-09 | Distributed Unit(DU)及びその方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2020022376 | 2020-02-13 | ||
JP2020-022376 | 2020-02-13 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021161622A1 true WO2021161622A1 (ja) | 2021-08-19 |
Family
ID=77291733
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2020/044537 WO2021161622A1 (ja) | 2020-02-13 | 2020-11-30 | Ranノード、無線端末、及びこれらのための方法 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20220287102A1 (ja) |
EP (1) | EP3993540A4 (ja) |
JP (2) | JP7439895B2 (ja) |
CN (1) | CN115428550A (ja) |
BR (1) | BR112022015308A2 (ja) |
WO (1) | WO2021161622A1 (ja) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023039852A1 (zh) * | 2021-09-17 | 2023-03-23 | 北京小米移动软件有限公司 | 系统信息传输方法和装置 |
WO2023054684A1 (ja) * | 2021-09-30 | 2023-04-06 | 株式会社デンソー | 端末、基地局、及び無線通信方法 |
WO2023070680A1 (zh) * | 2021-11-01 | 2023-05-04 | 北京小米移动软件有限公司 | 资源配置、确定方法和装置、通信装置和存储介质 |
WO2023151088A1 (zh) * | 2022-02-14 | 2023-08-17 | 北京小米移动软件有限公司 | 确定信道的资源位置的方法、装置、通信设备及存储介质 |
WO2023199498A1 (ja) * | 2022-04-14 | 2023-10-19 | 株式会社Nttドコモ | 端末、基地局及び通信方法 |
WO2024024969A1 (ja) * | 2022-07-29 | 2024-02-01 | 株式会社デンソー | 装置および方法 |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021010786A1 (en) * | 2019-07-17 | 2021-01-21 | Samsung Electronics Co., Ltd. | Method and device for reporting information, method and device for receiving message |
CN115462141A (zh) * | 2020-05-15 | 2022-12-09 | Lg 电子株式会社 | 用于无线通信的发送/接收信号的方法及其设备 |
CN114071495A (zh) * | 2020-07-31 | 2022-02-18 | 维沃移动通信有限公司 | 初始接入方法及装置、终端及网络侧设备 |
US11683849B2 (en) * | 2021-03-24 | 2023-06-20 | Nokia Technologies Oy | Redcap UE identification |
US20230247708A1 (en) * | 2021-04-01 | 2023-08-03 | Apple Inc. | Configurations for layer 1 and layer 2-centric inter-cell mobility |
WO2024039092A1 (en) * | 2022-08-19 | 2024-02-22 | Lg Electronics Inc. | Method and apparatus for performing bandwidth part operation for system information request by redcap ue in wireless communication system |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2018064252A (ja) | 2016-10-14 | 2018-04-19 | 株式会社Nttドコモ | ユーザ装置及び信号受信方法 |
JP2020022376A (ja) | 2018-08-06 | 2020-02-13 | 株式会社Adeka | 風味成分含有水中油型ロールイン油脂組成物 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP4040712B1 (en) * | 2017-05-05 | 2023-09-06 | Apple Inc. | Bandwidth part configuration and operation for new radio (nr) wideband user equipment (ue) |
AU2018341637B2 (en) | 2017-09-29 | 2022-11-03 | Samsung Electronics Co., Ltd. | Apparatus and method for handling bandwidth part configuration for random access channel procedure in wireless communication system |
WO2019096213A1 (en) | 2017-11-15 | 2019-05-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and devices for load balancing across band-width parts |
CN111713169B (zh) | 2018-02-15 | 2023-06-23 | 瑞典爱立信有限公司 | 随机接入过程 |
US10785804B2 (en) * | 2018-02-17 | 2020-09-22 | Ofinno, Llc | Bandwidth part configuration information |
US11399393B2 (en) * | 2019-01-09 | 2022-07-26 | Ofinno, Llc | Random access backoff indicator |
EP4087344A4 (en) | 2020-01-22 | 2023-04-05 | Huawei Technologies Co., Ltd. | METHOD AND APPARATUS FOR DETERMINING AN INITIAL BANDWIDTH PART (BWP) AND STORAGE MEDIUM |
US11564221B2 (en) * | 2020-02-12 | 2023-01-24 | Qualcomm Incorporated | COREST0 configuration and/or SS0 configuration for reduced capability UES |
-
2020
- 2020-11-30 BR BR112022015308A patent/BR112022015308A2/pt unknown
- 2020-11-30 WO PCT/JP2020/044537 patent/WO2021161622A1/ja unknown
- 2020-11-30 EP EP20919126.1A patent/EP3993540A4/en active Pending
- 2020-11-30 US US17/629,843 patent/US20220287102A1/en active Pending
- 2020-11-30 CN CN202080099712.7A patent/CN115428550A/zh active Pending
- 2020-11-30 JP JP2022500237A patent/JP7439895B2/ja active Active
-
2024
- 2024-02-09 JP JP2024018260A patent/JP2024036676A/ja active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2018064252A (ja) | 2016-10-14 | 2018-04-19 | 株式会社Nttドコモ | ユーザ装置及び信号受信方法 |
JP2020022376A (ja) | 2018-08-06 | 2020-02-13 | 株式会社Adeka | 風味成分含有水中油型ロールイン油脂組成物 |
Non-Patent Citations (4)
Title |
---|
HUAWEI , HISILICON: "Sidelink PHY structure and procedure for NR V2X", 3GPP DRAFT; R1-1810138, vol. RAN WG1, 29 September 2018 (2018-09-29), pages 1 - 15, XP051517553 * |
ITL: "Physical layer structure for NR V2X[ online", 3GPP DRAFT; R1-1907396_V2X_PHY STRUCTURE, vol. RAN WG1, 17 May 2019 (2019-05-17), Reno, USA, pages 1 - 10, XP051709417 * |
SAMSUNG: "Email discussion on RRC triggered BWP activation", 3GPP DRAFT; R2-1808645_EMAIL DISCUSSION ON RRC TRIGGERED BWP ACTIVATION, vol. RAN WG2, 25 May 2018 (2018-05-25), Busan, Korea, pages 1 - 9, XP051520033 * |
See also references of EP3993540A4 |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023039852A1 (zh) * | 2021-09-17 | 2023-03-23 | 北京小米移动软件有限公司 | 系统信息传输方法和装置 |
WO2023054684A1 (ja) * | 2021-09-30 | 2023-04-06 | 株式会社デンソー | 端末、基地局、及び無線通信方法 |
WO2023070680A1 (zh) * | 2021-11-01 | 2023-05-04 | 北京小米移动软件有限公司 | 资源配置、确定方法和装置、通信装置和存储介质 |
WO2023151088A1 (zh) * | 2022-02-14 | 2023-08-17 | 北京小米移动软件有限公司 | 确定信道的资源位置的方法、装置、通信设备及存储介质 |
WO2023199498A1 (ja) * | 2022-04-14 | 2023-10-19 | 株式会社Nttドコモ | 端末、基地局及び通信方法 |
WO2024024969A1 (ja) * | 2022-07-29 | 2024-02-01 | 株式会社デンソー | 装置および方法 |
Also Published As
Publication number | Publication date |
---|---|
JP7439895B2 (ja) | 2024-02-28 |
CN115428550A (zh) | 2022-12-02 |
US20220287102A1 (en) | 2022-09-08 |
JPWO2021161622A1 (ja) | 2021-08-19 |
BR112022015308A2 (pt) | 2022-09-27 |
EP3993540A1 (en) | 2022-05-04 |
EP3993540A4 (en) | 2022-10-12 |
JP2024036676A (ja) | 2024-03-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021161622A1 (ja) | Ranノード、無線端末、及びこれらのための方法 | |
US11843975B2 (en) | Radio access network node, and method and non-transitory computer readable medium therefor | |
JP7063404B2 (ja) | gNB及びUE | |
JP7031644B2 (ja) | 無線端末及びその方法 | |
KR102472292B1 (ko) | 무선 통신 시스템에서 경쟁 및 비경쟁 기반 빔 실패 복구를 수행하는 방법 및 장치 | |
US11283581B2 (en) | Terminal apparatus, base station apparatus, communication method, and integrated circuit | |
WO2018199079A1 (ja) | 端末装置、基地局装置、通信方法、および、集積回路 | |
KR20200036797A (ko) | 무선통신 시스템에서 랜덤 액세스 방법 및 장치 | |
CN116235603A (zh) | 用于小数据传输的方法和装置 | |
JP5595326B2 (ja) | システム情報の受信をハンドリングする方法および関連する通信装置 | |
JP2014513504A (ja) | ランダムアクセス応答のためのクロススケジューリング | |
TW201911935A (zh) | 處理載波聚合及雙連結的裝置及方法 | |
WO2022152003A1 (zh) | 非激活态下数据传输方法及装置 | |
TWI786670B (zh) | 用於無線通訊的方法及使用者設備 | |
KR102536947B1 (ko) | 무선통신 시스템에서 데이터를 송수신하는 방법 및 장치 | |
KR20230048098A (ko) | 스몰 데이터 송신을 위한 유휴/비활성 이동성 | |
CN116134947A (zh) | 无线通信中针对小数据传输的随机接入过程的方法和装置 | |
CN116438916A (zh) | 用于停用和激活无线通信系统中的辅基站的方法和装置 | |
US20220279585A1 (en) | Method and apparatus for performing 2-step random access procedure in wireless communication system | |
CN116057983A (zh) | 用于增强型恢复保护的方法和设备 | |
WO2023068000A1 (ja) | 無線端末及びその方法 | |
KR20210000227A (ko) | 무선통신시스템에서 2단계 랜덤엑세스 절차에서 백오프를 수행하는 방법 및 장치 | |
WO2022137853A1 (ja) | User Equipment、無線アクセスネットワークノード、及びこれらの方法 | |
WO2023067998A1 (ja) | 無線端末、無線アクセスネットワークノード、及びこれらの方法 | |
WO2024048208A1 (ja) | User Equipment、無線アクセスネットワークノード、及びこれらの方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20919126 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022500237 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2020919126 Country of ref document: EP Effective date: 20220128 |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112022015308 Country of ref document: BR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 112022015308 Country of ref document: BR Kind code of ref document: A2 Effective date: 20220802 |