Title: Radio access network node and method and non-transitory computer readable medium
Technical field
[0001]
　TECHNICAL FIELD The present disclosure relates to wireless communication systems, and more particularly to the use of one or more bandwidth parts configured within one carrier band.
Background technology
[0002]
　The 3rd Generation Partnership Project (3GPP) is working on the standardization of the 5th generation mobile communication system (5G) for introduction after 2020. 5G is a combination of continuous improvement and evolution (enhancement/evolution) of LTE and LTE-Advanced and innovative improvement and development by introducing a new 5G air interface (new Radio Access Technology (RAT)). It is supposed to be done. The new RAT is, for example, a frequency band higher than the frequency band (eg, 6 GHz or less) targeted for continuous development of LTE/LTE-Advanced, for example, a centimeter wave band of 10 GHz or more and a millimeter wave band of 30 GHz or more. Support wave bands.
[0003]
　In this specification, the fifth-generation mobile communication system is also referred to as a 5G System or a Next Generation (NextGen) System (NG System). The new RAT for 5G System is called New Radio (NR), 5G RAT, or NG RAT. The new Radio Access Network (RAN) for 5G System is called 5G-RAN or NextGen RAN (NG RAN). The new base station in 5G-RAN is called NR NodeB (NR NB) or gNodeB (gNB). The new core network for 5G System is called 5G Core Network (5G-CN or 5GC) or NextGen Core (NG Core). A wireless terminal (User Equipment (UE)) connected to the 5G System is called a 5G UE, a NextGen UE (NG UE), or simply a UE. Formal names such as RAT, UE, radio access network, core network, network entities (nodes), and protocol layers for 5G System will be determined in the future as the standardization work progresses.
[0004]
　The term “LTE” used in the present specification includes improvements and developments of LTE and LTE-Advanced to enable interworking with 5G System, unless otherwise specified. Improvements and developments of LTE and LTE-Advanced for interworking with 5G System are also called LTE-Advanced Pro, LTE+, or enhanced LTE (eLTE). Furthermore, "Evolved Packet Core (EPC)", "Mobility Management Entity (MME)", "Serving Gateway (S-GW)", and "Packet Data Network (PDN) Gateway (P-GW) used in this specification. )” and other terms relating to LTE networks or logical entities include these improvements and developments to enable interworking with 5G Systems unless otherwise noted. The improved EPC, MME, S-GW, and P-GW are, for example, enhanced EPC (eEPC), enhanced MME (eMME), enhanced S-GW (eS-GW), and enhanced P-GW (eP-GW). ) Is also called.
[0005]
　In LTE and LTE-Advanced, bearers for each QoS class and for each PDN connection are RAN (ie, Evolved Universal Terrestrial RAN (E-UTRAN)) and core network (ie, for quality of service (QoS) and packet routing. EPC) used both. That is, in the Bearer-based QoS (or per-bearer QoS) concept, one or more Evolved Packet System (EPS) bearers are set between the UE and the P-GW in the EPC, and a plurality of Evolved Packet System (EPS) bearers having the same QoS class are set. Service Data Flows (SDFs) are transferred through one EPS bearer that satisfies these QoS.
[0006]
　On the other hand, in 5G System, although radio bearers may be used in NG-RAN, it is considered that bearers are not used in the 5GC and at the interface between 5GC and NG-RAN. Specifically, PDU flows are defined instead of EPS bearer, and one or more SDFs are mapped to one or more PDU flows. The PDU flow between the 5G UE and the user plane termination entity (ie, the entity corresponding to the P-GW in EPC) in the NG Core corresponds to the EPS bearer in the EPS Bearer-based QoS concept. PDU flow corresponds to the finest granularity of packet forwarding and treatment within a 5G system. That is, the 5G system adopts the Flow-based QoS (or per-flow QoS) concept instead of the Bearer-based QoS concept. In the Flow-based QoS concept, QoS is handled on a PDU flow basis. The association between the 5G UE and the data network is called a PDU session. The PDU session is a term corresponding to PDN connection (PDN connection) of LTE and LTE-Advanced. Multiple PDU flows can be configured within one PDU session. The 3GPP specifications define 5G QoS Indicator (5QI) corresponding to LTE QCI for 5G System.
[0007]
　The PDU flow is also called "QoS flow". The QoS flow is the finest granularity of the QoS treatment within the 5G system. User plane traffic with the same N3 marking value in the PDU session corresponds to the QoS flow. The N3 marking corresponds to the above-mentioned PDU flow ID and is also called QoS flow Identity (QFI) and also Flow Identification Indicator (FII). Here, there is a one-to-one relationship between at least each 5QI specified in the specifications and the corresponding QFI having the same value (number) as this (ie, one-to-one mapping).
[0008]
　Figure 1 shows the basic architecture of a 5G system. The UE establishes one or more signaling radio bearers (SRBs) and one or more data radio bearers (DRBs) with the gNB. 5GC and gNB establish the control plane interface and the user plane interface for the UE. The control plane interface between 5GC and gNB (ie, RAN) is called N2 interface, NG2 interface, or NG-c interface, which transfers Non-Access Stratum (NAS) information and controls between 5GC and gNB. Used for information (eg, N2 AP Information Element). The user plane interface between the 5GC and the gNB (ie, RAN) is called N3 interface, NG3 interface or NG-u interface, and packets of one or more PDU flows in the PDU session of the UE. Used to transfer.
[0009]
　It should be noted that the architecture shown in FIG. 1 is only one of multiple 5G architecture options (or deployment scenarios). The architecture shown in FIG. 1 is called "Standalone NR (in NextGen System)" or "Option 2". 3GPP is also exploring some network architectures for multi-connectivity operation using E-UTRA and NR radio access technologies. A typical example of multi-connection operation is a dual connection (Dual Connectivity (DC) in which one master node (Master node (MN)) and one secondary node (Secondary node (SN)) cooperate with each other to simultaneously communicate with one UE. )). Dual connection operation using E-UTRA and NR radio access technologies is called Multi-RAT Dual Connectivity (MR-DC). MR-DC is a dual connectivity between an E-UTRA node and an NR node (E-UTRA and NR nodes).
[0010]
　In MR-DC, one of E-UTRA node (ie, eNB) and NR node (ie, gNB) operates as a master node (Master node (MN)), and the other operates as a secondary node (Secondary node (SN)). , And at least the MN is connected to the core network. The MN provides the UE with one or more Master Cell Group (MCG) cells, and the SN provides the UE with one or more Secondary Cell Group (SCG) cells. MR-DC includes “MR-DC with the EPC” and “MR-DC with the 5GC”.
[0011]
　MR-DC with the EPC includes E-UTRA-NR Dual Connectivity (EN-DC). In EN-DC, the UE is connected to the eNB that operates as the MN and the gNB that operates as the SN. Furthermore, eNB (ie, Master eNB) is connected to EPC, gNB (ie Secondary gNB) is connected to Master eNB via X2 interface.
[0012]
　MR-DC with the 5GC includes NR-E-UTRA Dual Connectivity (NE-DC) and NG-RAN E-UTRA-NR Dual Connectivity (NG-EN-DC). In NE-DC, UE is connected to gNB operating as MN and eNB operating as SN, gNB (ie, Master gNB) is connected to 5GC, eNB (ie Secondary eNB) is Master gNB via Xn interface. Connected. On the other hand, in NG-EN-DC, UE is connected to eNB operating as MN and gNB operating as SN, eNB (ie, Master eNB) is connected to 5GC, gNB (ie Secondary gNB) is via Xn interface. Connected to the Master eNB.
[0013]
　2, 3 and 4 respectively show network configurations of the three DC types mentioned above, namely EN-DC, NE-DC and NG-EN-DC. In addition, Secondary gNB (SgNB) in EN-DC of FIG. 2 is also called en-gNB, and Secondary eNB (SeNB) in NE-DC of FIG. 3 and Master eNB (MeNB) in NG-EN-DC of FIG. , Ng-eNB, but is referred to as gNB or eNB in ​​the present specification. In addition, the 5G System supports dual connectivity between two gNBs. Dual connectivity between two gNBs is referred to herein as NR-NR DC. FIG. 5 shows a network configuration of NR-NR DC.
[0014]
　NR is supposed to use different radio parameter sets for multiple frequency bands. Each wireless parameter set is called a "numerology". The OFDM numerology for Orthogonal Frequency Division Multiplexing (OFDM) system is, for example, subcarrier spacing, system bandwidth, transmission time interval (TTI) length, It includes a frame length (subframe duration), a cyclic prefix length (Cyclic prefix length), and a symbol duration (symbol duration). The 5G system includes various types of services with different service requirements such as broadband communication (enhanced Mobile Broad Band: eMBB), highly reliable and low latency communication (Ultra Reliable and Low Latency Communication: URLLC), and multi-connection M2M communication (massive). Machine Type Communication: mMTC) is included. The choice of Numerology depends on the service requirements.
[0015]
　UE and NR gNB of 5G system support aggregation of multiple NR carriers of different numerologies. In 3GPP, aggregation of multiple NR carriers (or NR cells) with different numerologies is a lower layer aggregation such as the existing LTE Carrier Aggregation (CA) or a higher layer aggregation such as the existing Dual Connectivity. (Upper layer aggregation) is being considered.
[0016]
　5G NR supports wider channel bandwidths (eg, 100s of MHz) than that of LTE. One channel band (ie, BW Channel ) is a radio frequency band (RF bandwidth) that supports one NR carrier. The channel band is also called the system band. LTE supports channel bands up to 20 MHz, whereas 5G NR supports channel bandwidths up to, for example, 500 MHz.
[0017]
　In order to efficiently support a plurality of 5G services, for example, a broadband service such as eMBB and a narrowband service such as the Internet of Things (IoT), it is preferable to be able to multiplex these services on one channel band. .. Furthermore, if all 5G UEs have to support transmission and reception in the transmission bandwidth corresponding to the entire channel bandwidth, this is the low cost and low power consumption of UEs for narrowband IoT services. May interfere. Therefore, 3GPP allows one or more bandwidth parts (BWPs) to be set within the carrier band (ie, channel band or system band) of each NR component carrier. Multiple BWPs within one NR channel band may be used for frequency division multiplexing (FDM) of different numerologies (eg, subcarrier spacing (SCS)). The bandwidth part is also called the carrier bandwidth part.
[0018]
　One bandwidth part (BWP) is continuous in frequency (frequency-consecutive) and is composed of contiguous physical resource blocks (PRBs). The bandwidth of one BWP is at least as large as the synchronization signal (SS)/physical broadcast channel (PBCH) block bandwidth. The BWP may or may not include the SS/PBCH block (SSB). The BWP configuration includes, for example, numerology, frequency location, and bandwidth (eg, number of PRBs). Common PRB indexing is used for downlink (DL) BWP configuration in at least Radio Resource Control (RRC) connected state to specify the frequency location. Specifically, the offset from PRB 0 to the lowest PRB of the SSB accessed by the UE is set by higher layer signaling. The reference point "PRB 0" is common to all UEs sharing the same wideband component carrier.
[0019]
　One SS/PBCH block includes basic signals (primary signals) necessary for idle UE, such as NR synchronization signals (NR-SS) and NR physical broadcast channel (NR-PBCH). NR-SS is used by the UE to obtain DL synchronization. A Reference Signal (RS) is transmitted in the SS/PBCH block in order to enable the UE in idle to perform Radio Resource Management (RRM) measurement (eg, RSRP measurement). The RS may be the NR-SS itself or an additional RS. The NR-PBCH broadcasts a part (eg, Master Information Block (MIB)) of minimum system information (Minimum System Information (minimum SI)). The remaining minimum SI (remaining minimum SI (RMSI)) is transmitted on the Physical Downlink Shared Channel (PDSCH).
[0020]
　The network can transmit multiple SS/PBCH blocks in the channel band of one wideband component carrier. In other words, SS/PBCH blocks may be transmitted in multiple BWPs within the channel band. In the first alternative, all SS/PBCH blocks in one wideband carrier are NR-SS (eg, primary SS (PSS) and secondary SS (SSS) corresponding to the same physical-layer cell identity. ))based on. In the second alternative, different SS/PBCH blocks in one wideband carrier may be based on NR-SSs corresponding to different physical-layer cell identities.
[0021]
　From the perspective of the UE, a cell is associated with one SS/PBCH block. Therefore, for the UE, each serving cell has one associated SS/PBCH block in frequency. In addition, each serving cell is a primary cell (PCell) in carrier aggregation (CA) and dual connectivity (DC), a primary secondary cell (PSCell) in DC, or a secondary cell (SCell) in CA and DC. Such SSB is called cell defining SS/PBCH block. The Cell defining SS/PBCH block has an associated RMSI. The Cell defining SS/PBCH block serves as a time reference or a timing reference of the serving cell. The Cell defining SS/PBCH block is used for SS/PBCH block (SSB) based RRM Measurements. The Cell defining SS/PBCH block is defined by “synchronous reconfiguration” for PCell/PSCell (for example, reconfiguration of radio resource configuration information without handover using RRC Reconfiguration procedure) and “SCell release/for SCell”. Can be changed by "add".
[0022]
　One or more BWP configurations for each component carrier are semi-statically signaled to the UE. Specifically, for each UE-specific serving cell, one or more DL BWPs and one or more UL BWPs can be configured for the UE by the dedicated RRC message. Further, one or more BWPs configured for the UE can be activated and deactivated. Activation/deactivation of BWP is determined not by the RRC layer but by lower layers (eg, Medium Access Control (MAC) layer, Physical (PHY) layer). The activated BWP is called an activated BWP (active BWP).
[0023]
　Switching of the active BWP (active BWP) may be performed by, for example, downlink control information (Downlink Control Information (DCI)) (eg, scheduling DCI) transmitted by the NR Physical Downlink Control Channel (PDCCH). In other words, deactivation of the current active BWP and activation of the new active BWP may be performed by DCI of NR PDCCH. Therefore, the network can activate/deactivate the BWP depending on, for example, the data rate or the numerology required by the service and dynamically switch the active BWP for the UE. Activation/deactivation of BWP may be performed by MAC Control Element (CE).
[0024]
　6 and 7 show examples of using BWP. In the example shown in FIG. 6, the channel band of one component carrier is divided into BWP #1 and BWP #2, and these two BWPs are used for FDM with different numerologies (eg, different subcarrier spacing). .. In the example shown in FIG. 7, narrow band BWP #1 is arranged in the channel band of one component carrier, and narrow band BWP #2 is further arranged than BWP #1. When BWP #1 or BWP #2 is activated for the UE, the UE can reduce power consumption by not performing reception and transmission outside the active BWP (but within the channel band).
[0025]
　Non-Patent Documents 1 to 7 disclose the above-described BWP and cell defining SS/PBCH block.
Advanced technical literature
Non-patent literature
[0026]
非特許文献1 : 3GPP R1-1711795, Ericsson, “On bandwidth parts and “RF” requirements”, TSG RAN1 NR Ad-Hoc#2, Qingdao, P.R. China, June 2017
非特許文献2 : 3GPP R2-1707624, “LS on Bandwidth Part Operation in NR”, 3GPP TSG RAN WG2#99, Berlin, Germany, August 2017
非特許文献3 : 3GPP R2-1710012, “LS on Further agreements for Bandwidth part operation”, 3GPP TSG RAN WG2 #99bis, Prague, Czech Republic, October 2017
非特許文献4 : 3GPP R2-1710031, “Reply LS on multiple SSBs within a wideband carrier”, 3GPP TSG RAN WG2 #99bis, Prague, Czech Republic, October 2017
非特許文献5 : 3GPP R2-1711640, ZTE Corporation, Sane Chips, “Initial discussion on the impacts of BWP on RAN2”, 3GPP TSG-RAN WG2 Meeting #99bis, Prague, Czech Republic, October 2017
非特許文献6 : 3GPP R2-1711969, Ericsson, “Text Proposal for L1 parametrs for 38.331”, 3GPP TSG-RAN WG2 #99bis, Prague, Czech Republic, October 2017
非特許文献7 : 3GPP R2-1709861, “LS on multiple SSBs within a wideband carrier”, 3GPP TSG RAN WG2#99, Berlin, Germany, August 2017
Summary of the invention
Problems to be Solved by the Invention
[0027]
　It is not clear how multiple RAN nodes (eg, gNBs) deployed in a radio access network know each other's BWP settings. One of the objects to be achieved by the embodiments disclosed herein is to provide an apparatus, a method, and a program which contribute to improved RAN inter-node (eg, inter-gNB) signaling to handle bandwidth parts. Is to provide. It should be noted that this goal is only one of the goals that the embodiments disclosed herein seek to achieve. Other objects or problems and novel features will become apparent from the description of the present specification or the accompanying drawings.
Means for solving the problems
[0028]
　In a first aspect, a RAN node device includes a memory and at least one processor coupled to the memory. The at least one processor is configured to send, to another RAN node, first control information relating to at least one of one or more bandwidth parts (BWPs) set in a system band.
[0029]
　A second aspect is that the method in the RAN node device includes sending to another RAN node first control information relating to at least one of one or more bandwidth parts (BWPs) set in the system band. ..
[0030]
　In the third aspect, the program includes a group of instructions (software code) for causing the computer to perform the method according to the second aspect, when the program is read by the computer.
Effect of the invention
[0031]
　According to the above aspect, it is possible to provide an apparatus, method, and program that contribute to improved RAN inter-node (eg, inter-gNB) signaling for handling bandwidth parts.
Brief description of the drawings
[0032]
FIG. 1 is a diagram showing a basic architecture of 5G System.
FIG. 2 is a diagram showing an EN-DC network configuration.
FIG. 3 is a diagram showing a network configuration of NE-DC.
FIG. 4 is a diagram showing a network configuration of NG-EN-DC.
FIG. 5 is a diagram showing a network configuration of NR-NR DC.
[Fig. 6] Fig. 6 is a diagram showing a usage example of a Bandwidth part (BWP).
[Fig. 7] Fig. 7 is a diagram illustrating a usage example of a Bandwidth part (BWP).
FIG. 8 is a diagram showing a setting example of BWP and SS/PBCH blocks.
FIG. 9 is a diagram showing a setting example of BWP and SS/PBCH blocks.
FIG. 10 is a diagram showing a configuration example of a wireless communication network according to the first embodiment.
FIG. 11 is a sequence diagram showing an example of signaling between RAN nodes according to the first embodiment.
FIG. 12 is a diagram showing a configuration example of a wireless communication network according to a second embodiment.
FIG. 13 is a sequence diagram showing an example of signaling related to BWP setting according to the second embodiment.
FIG. 14 is a diagram showing an example of a format of a “BWP list” information element (Information Element (IE)).
FIG. 15 is a sequence diagram showing an example of signaling between RAN nodes according to the second embodiment.
FIG. 16 is a sequence diagram showing an example of inter-RAN node signaling according to the second embodiment.
FIG. 17 is a sequence diagram showing an example of signaling between a RAN node and a UE according to the second embodiment.
FIG. 18 is a diagram showing a configuration example of a wireless communication network according to a third embodiment.
FIG. 19 is a sequence diagram showing an example of inter-RAN node signaling according to the third embodiment.
FIG. 20 is a sequence diagram showing an example of signaling between RAN nodes according to the third embodiment.
FIG. 21 is a diagram showing a configuration example of a wireless communication network according to a fourth embodiment.
FIG. 22 is a sequence diagram showing an example of inter-RAN node signaling according to the fourth embodiment.
FIG. 23 is a block diagram showing a configuration example of a RAN node according to some embodiments.
FIG. 24 is a block diagram showing a configuration example of a wireless terminal according to some embodiments.
MODE FOR CARRYING OUT THE INVENTION
[0033]
　Hereinafter, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and for the sake of clarity of explanation, duplicated description will be omitted as necessary.
[0034]
　A plurality of embodiments described below can be implemented independently or can be implemented in combination as appropriate. The plurality of embodiments have novel features different from each other. Therefore, these plurality of embodiments contribute to solving different purposes or problems, and contribute to achieving different effects.
[0035]
　The embodiments described below are mainly described for the 3GPP 5G system. However, these embodiments may be applied to other wireless communication systems.
[0036]
　First, referring to FIGS. 8 and 9, the definition of terms relating to the case where one system band includes a plurality of BWPs will be described. 8 and 9 show setting examples of BWP and SS/PBCH blocks. In the example shown in FIGS. 8 and 9, one channel band includes three BWPs, that is, BWP #1, BWP #2, and BWP #3. BWP #1 and BWP #2 include SS/PBCH block (SSB) #1 and SSB #2, respectively, while BWP #3 does not include SS/PBCH block.
[0037]
　From a network perspective, like the existing LTE, the entire band (ie, channel band or system band) of one component carrier corresponds to one cell. In the example of FIGS. 8 and 9, the Physical Cell Identity (PCI) associated with the cell corresponding to the channel band is “PCIx”.
[0038]
　In this specification, a cell from a network perspective is defined as a "logical cell (logcal cell)". Furthermore, the PCI associated with the network viewpoint cell (ie, logical cell) is defined as the reference PCI. Note that the network viewpoint cell (ie, logical cell) may be associated with one Cell Identity. In this case, the Cell Identity of the network view cell (ie, logical cell) may be associated with (sub)PCIs of a plurality of physical cells described later.
[0039]
　On the other hand, as described above, in the UE perspective, a cell is associated with one SS/PBCH block. In this specification, a cell from the viewpoint of UE is defined as a "physical cell". Furthermore, the PCI associated with the UE viewpoint cell (ie, physical cell) is defined as sub PCI. That is, the plurality of BWPs included in one system band and each including the SS/PBCH block are a plurality of UE viewpoint cells (ie, a plurality of physical cells). The sub PCIs of the plurality of UE viewpoint cells (physical cells) are associated with one reference PCI or one Cell Identity of the network viewpoint cell (ie, logical cell). Furthermore, a BWP that does not include an SS/PBCH block may be defined as a UE viewpoint cell (physical cell), or a group of BWP that does not include an SS/PBCH block and a BWP that includes an SS/PBCH block that this refers to is a UE. It may be defined as a viewpoint cell (physical cell). Also from the network viewpoint, the unit system band actually used by the network (eg, RAN node) for communication with the UE is each UE viewpoint cell (physical cell).
[0040]
　In the example of FIG. 8, three BWPs support the same numerology (ie, numerology #1), and all SS/PBCH blocks (ie, SSB #1 and SSB #2) in one channel band are the same. Based on NR-SS corresponding to (sub)PCI (ie, PCIx). That is, FIG. 8 corresponds to the first scheme described above for the transmission of multiple SS/PBCH blocks in the channel band. In order for the UE to synchronize with BWP #3 that does not include SSB, SSB #1 or SSB #2 sent by other BWPs is referenced. At this time, the referenced SSB #1 or SSB #2 is called a reference SSB (reference SSB), and the UE may be notified of the reference SSB identifier (SSB index, eg, SSB #1 or #2) from the network. ..
[0041]
　In the example of FIG. 9, BWP #1 supports numerology #1, and BWP #2 and BWP #3 support numerology #2. Different SSBs #1 and #2 for different numerologies are based on NR-SS corresponding to different (sub)PCIs (ie, PCIx and PCIy). That is, FIG. 9 corresponds to the second scheme described above for the transmission of multiple SS/PBCH blocks in the channel band. In order for the UE to synchronize to BWP #3 that does not include SSB, for example, SSB #2 of BWP #2 that supports the same numerology as BWP #3 is referenced. Alternatively, the UE may refer to the SSB #1 of the BWP #1 that supports a different numerology from the numerology of the BWP #3, because the UE synchronizes to the BWP #3 that does not include the SSB.
[0042]
　In the example of FIG. 8, the sub-PCIs (ie, PCIx and PCIx) of two UE viewpoint cells (physical cells) are added to the reference PCI (ie, PCIx) or Cell Identity of one network viewpoint cell (ie, logical cell). Associated. In the example of FIG. 9, the reference PCI (ie, PCIx) or Cell Identity of one network viewpoint cell (ie, logical cell) has the sub-PCIs (ie, PCIx and PCIy) of two UE viewpoint cells (physical cells). Associated.
[0043]
　A network (eg, RAN node) may configure a UE with a BWP set including one or more BWPs. In other words, the UE receives setting information (eg, SSB indexes, presence of SSBs, reference SSB indexes, Layer-1 parameters) of one or more BWPs from the network. The BWP set may be individually set for the downlink (DL) and the uplink (UL). That is, a BWP set may include a DL BWP set and a UL BWP set that are separate for DL ​​and UL. Alternatively, UL BWP and DL BWP may be associated in advance, and the BWP set in this case may be common to DL and UL. The UE can activate k (k <= K) BWPs among the K BWPs included in the (DL/UL) BWP set. In other words, up to K (DL/UL) BWP(s) can be activated at one time for a certain UE. In the following description, for simplification, it is assumed that one BWP (ie k=1) is activated. However, the present embodiment and the subsequent embodiments can be appropriately applied even when two or more (k>=2) BWPs are activated at one time.
[0044]
　In addition, this specification introduces the term "BWP group". BWP groups are included in BWP sets. A BWP group consists of one or more BWPs whose active BWP can be changed by the DCI sent on the NR PDCCH. Between one or more BWPs included in the BWP group, the active BWP can be changed without changing the Cell defining SSB. Therefore, a BWP group may be defined as being one or more BWPs associated with one cell defining SSB. A BWP group may include one BWP (eg, standard BWP, initial BWP, default BWP) that includes a cell defining SSB and one or more other BWPs. Each of the other one or more BWPs that are not the reference BWP (or initial BWP, default BWP) may or may not include SSB. The UE may explicitly specify/configure which SSB is the cell defining SSB, or implicitly that the UE is the cell defining SSB of the first BWP SSB when the relevant BWP group is configured ( implicitly).
[0045]
　The BWP group may be individually set for the downlink (DL) and the uplink (UL). That is, a BWP group may include a DL BWP group and a UL BWP group that are separate for DL ​​and UL. Alternatively, UL BWP and DL BWP may be associated in advance, and the BWP group in this case may be common to DL and UL.
[0046]
　In the example of FIG. 8, BWPs #1 to #3 are set in the UE as one BWP set. In the example of FIG. 8, the UE may refer to SSB #1 transmitted in BWP #1 in order to synchronize with BWP #3 (that is, to establish synchronization in BWP #3). In this case, BWP #1 and BWP #3 may correspond to one BWP group, and BWP #2 may correspond to another BWP group. That is, one BWP set (BWPs #1, #2, and #3) may include the first BWP group (BWPs #1 and #3) and the second BWP group (BWP #2). Alternatively, one BWP set (BWPs #1, #2, and #3) may include a first BWP group (BWP #1) and a second BWP group (BWPs #2 and #3). Good. Further alternatively, one BWP set (BWPs #1, #2, and #3) may correspond to one BWP group (BWPs #1, #2, and #3). In this case, one of SSB #1 and SSB #2 is the cell defining SSB for the UE.
[0047]
　Also in the example of FIG. 9, BWPs #1 to #3 are set in the UE as one BWP set. In one example, BWP #1 of numerology #1 may correspond to one BWP group, and BWP #2 and BWP #3 of numerology #2 may correspond to another BWP group. That is, one BWP set (BWPs #1, #2, and #3) may include a first BWP group (BWPs #1) and a second BWP group (BWP #2 and #3). As described above, BWPs of different numerologies may be included in one BWP group. Therefore, in another example, one BWP set (BWPs #1, #2, and #3) has a first BWP group (BWPs #1 and #3) and a second BWP group (BWP #2). May be included. Further alternatively, one BWP set (BWPs #1, #2, and #3) may correspond to one BWP group (BWPs #1, #2, and #3). In this case, one of SSB #1 and SSB #2 is the cell defining SSB for the UE.
[0048]
　As described above, activation/deactivation of the BWP may be performed by lower layers (eg, Medium Access Control (MAC) layer, Physical (PHY) layer) instead of the RRC layer. A timer (eg, BWP Inactivity Timer of MAC layer) may be used for activation/deactivation of DL BWP. The UE may switch the active BWP according to a timer based on the setting value transmitted by the gNB. The period (period or duration) indicated by the timer may be indicated in subframe units. For example, when the UE does not transmit or receive data in the active BWP for a predetermined period (that is, the expiration value of the timer), the active BWP of the predetermined BWP (eg, default BWP, BWP including cell defininig SSB) is changed. You may do it. The network (eg, RAN node) may also determine the active BWP change based on a similar timer.
[0049]

　FIG. 10 shows an example of the configuration of a wireless communication network according to this embodiment. In the example of FIG. 10, the wireless communication network includes a RAN node 11 and a RAN node 12. The RAN node 11 and the RAN node 12 are connected by an interface 1001. The RAN node 11 is, for example, a gNB or an eNB in ​​MR-DC. The RAN node 12 is also, for example, a gNB or an eNB in ​​MR-DC. In this case, the interface 1001 is the Xn interface or the (improved) X2 interface.
[0050]
　One of the RAN nodes 11 and 12 may be a Central Unit (CU) (eg, gNB-CU) in a cloud RAN (C-RAN) deployment, and the other is a Distributed Unit (DU) (eg, gNB-). DU). The Central Unit (CU) is also called Baseband Unit (BBU) or digital unit (DU). Distributed Unit (DU) is also called Radio Unit (RU), Remote Radio Head (RRH), Remote Radio Equipment (RRE), or Transmission and Reception Point (TRP or TRxP). In this case, the interface 1001 is an interface (eg, F1 interface) between the CU and the DU.
[0051]
　FIG. 11 shows an example of RAN inter-node signaling (process 1100). In step 1101, the RAN node 11 sends to the RAN node 12 control information regarding at least one of one or more BWPs set in a band (ie, channel band or system band) of one component carrier. Hereinafter, the control information will be referred to as BWP-related control information. Similarly, the RAN node 12 may also send the BWP-related control information to the RAN node 11.
[0052]
　In some implementations, the RAN node 11 may use the above BWP-related control information to inform the RAN node 12 of the details of one or more BWPs configured in the component carrier associated with the cell in which it operates. May be sent. Additionally or alternatively, in some implementations, the RAN node 11 (eg, CU in C-RAN deployment) should be set to RAN node 12 (eg, DU in C-RAN deployment) 1 or The above BWP-related control information may be sent to instruct the RAN node 12 of the details of further BWPs.
[0053]
　Additionally or alternatively, in some implementations, the RAN node 12 (eg, DU in C-RAN deployment) is configured within the component carrier associated with its operating cell (ie, logical cell). In order to inform the RAN node 11 (eg, CU in C-RAN deployment) of the details of one or more BWPs (ie, one or more physical cells) that can be configured or configured. BWP related control information may be sent. Additionally or alternatively, in some implementations, the RAN node 12 (eg, DU in a C-RAN deployment) configures one or more BWPs for a UE that resides in a (logical) cell in which it operates. BWP-related control information (in other words, UE-specific (UE-specific) BWP setting status information) including information about the status may be sent to the RAN node 11 (eg, CU in C-RAN arrangement).
[0054]
　For example, the RAN node 11 may send the above control information to the RAN node 12 in the setup procedure of the interface 1001. The RAN node 11 may send the above BWP-related control information to the RAN node 12 in the modification procedure of the interface 1001.
[0055]
　This allows the RAN nodes 11 and 12 to contribute to improved RAN inter-node (eg, inter-gNB) signaling to handle BWPs. As a result, the RAN nodes 11 and 12 can know each other's BWP settings by a plurality of RAN nodes (eg, gNBs).
[0056]
　The RAN node 12 uses at least part of the BWP-related control information received from the RAN node 11 as a SCell (ie, Secondary Cell Group (SCG) SCell) for UE handover, interference avoidance/suppression between adjacent cells, or DC. Alternatively, it may be used for determining the SN. For example, the RAN node 12 may determine the BWP of the adjacent cell measured by the UE based on the BWP related control information received from the RAN node 11. The RAN node 12 may determine the BWP (ie, target BWP) of the adjacent cell to which the UE should be handed over, based on the BWP-related control information received from the RAN node 11. The RAN node 12 may determine the BWP used as the SCG SCell for the UE based on the BWP related control information received from the RAN node 11.
[0057]
　Further or alternatively, the RAN node 11 uses at least a part of the same BWP related control information as the BWP related control information transmitted to the RAN node 12 for UE handover, interference avoidance/suppression between adjacent cells, or DC. SCell (ie, Secondary Cell Group (SCG) SCell) or may be used for control related to SN determination.
[0058]
　To enable these radio resource controls for BWP, the BWP related control information may include at least one Information Element (IE) of the following:
is associated with one or more downlink BWPs Information element indicating one or more BWP indexes; information element indicating one or more BWP indexes
associated with one or more uplink BWPs;
carrier frequency associated with each BWP (eg, Information element indicating Absolute Radio Frequency Channel Number (ARFCN);
-Information element indicating whether or not each BWP includes SS/PBCH block (SSB);
-Reference SSB associated with BWP that does not include SSB or the relevant Information element indicating the reference BWP including the reference SSB;
-Information element indicating the configuration of the SSB transmitted by each BWP (eg, SS series or PCI, SSB duration, numerology)-Reference
PRB (eg, PRB0) to each SSB Information element indicating the offset to the lowest PRB of the
BWP ; information element indicating the numerology set for each BWP; and
information element indicating the configuration of the BWP set or BWP group (eg, the index of each BWP group and included in it. BWP index listing information).
[0059]
　These information elements (IE) may indicate information elements (IE) related to BWPs that should be set in the component carrier (or logical cell) operated by the RAN node 12. Additionally or alternatively, these information elements (IE) may indicate information elements (IE) regarding BWPs set in the component carrier (or logical cell) operated by the RAN node 11.
[0060]
　The BWP related control information includes information elements (eg, PRACH Configuration IE) of radio resources (eg, time and frequency resource information, preamble index) used for random access preamble transmission in one or more UL BWPs. May be. Additionally or alternatively, the BWP related control information may include an information element indicating one of one or more UL BWPs indicating an uplink BWP in which a UE preamble transmission of a random access channel is performed. Thereby, for example, the RAN node 12 can avoid or reduce interference between adjacent cells in random access preamble transmission based on the BWP-related control information received from the RAN node 11.
[0061]
　The BWP-related control information includes at least one of an information element indicating the availability of network slicing in each BWP and an information element indicating the quality of service (QoS) applied to each BWP. Good. Instead, the BWP-related control information is an information element indicating the availability of network slicing in each BWP and a quality of service (QoS) supported (or applied to each BWP). ) May be associated with at least one of the information elements. Note that the BWP-related control information may indicate these not for each BWP but for each BWP set or each BWP group.
[0062]
　For example, the network slices provided (or corresponding) in one or more BWPs in the component carrier associated with the (logical) cell operated by the RAN node 11 may be different. In this case, the RAN node 11 sends the information of these network slices to the RAN node 12. For example, the network slice may be indicated by a slice type (eg, Slice Service Type: SST). The SST may be indicated by the service type (eg, eMBB, URLLC, mMTC) or the identifier of the core network node connected to the RAN node. The core network node is, for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), or a User Plane Function (UPF). Thereby, for example, the RAN node 12 can determine the BWP in which the UE stays or the BWP in which the UE is handed over in consideration of which BWP is available or provided in which BWP in the RAN node 11. As a result, the UE can execute the desired service and obtain the expected characteristics (eg, throughput, transmission rate).
[0063]
　When different SS/PBCH blocks in one wideband carrier are based on NR-SS corresponding to different PCIs (eg, the above-mentioned second alternative as in FIG. 9), the BWP-related control information is further added to the system. It also includes an information element indicating a relationship between one reference PCI (or one Cell Identity) associated with a network viewpoint cell (ie, a logical cell) corresponding to a band and a sub PCI associated with each BWP. Good. Explaining using the example of FIG. 9, the BWP-related control information is BWP #1 including SSB #1 based on sub PCI: “PCIx” and BWP including SSB #2 based on sub PCI: “PCIy”. #2 may indicate that the reference PCI: “PCIx” is set in a cell (that is, the entire component carrier) in a network perspective. As a result, if there is no one-to-one mapping between Cell Identity and PCI, then there is no one-to-one mapping between Cell Global Identity (CGI) and PCI in public land mobile network (PLMN). Even in the case, the management and control of the physical cell for the UE can be appropriately performed. The CGI is composed of, for example, PLMN Id and Cell Identity (PLMN Id + Cell Identity). Management or control of the physical cell for the UE, for example, which physical cell the UE is staying, which physical cell is set to the UE, or which physical cell to move the UE to the management or control Including doing.
[0064]

　This embodiment provides a specific example of the BWP-related control information described in the first embodiment. FIG. 12 shows a configuration example of the wireless communication network according to this embodiment. In the example of FIG. 12, the wireless communication network includes gNB21, gNB22, and UE23. An interface 1201 connects between gNB21 and gNB22. The interface 1201 is an Xn interface. The UE 23 is connected to the gNB 21 or the gNB 22 or both via the air interface 1202 or 1203 or both.
[0065]
　FIG. 13 shows an example of RAN inter-node signaling (process 1300). In step 1301, the gNB 21 sends the BWP related control information to the gNB 22 using the Xn SETUP REQUEST message. In step 1302, the gNB 22 sends the BWP related control information to the gNB 21 using the Xn SETUP RESPONSE message. When the BWP related control information is updated, the gNB 22 may send the updated BWP related control information to the gNB 21 using the gNB CONFIGURATION UPDATE message (step 1303). The gNB 21 sends a gNB CONFIGURATION UPDATE ACKNOWLEDGE message to the gNB 22 in response to receiving the gNB CONFIGURATION UPDATE message.
[0066]
　The BWP-related control information may be included in the Served Cell information IE and the Neighbor Information IE in the Xn message (eg, Xn SETUP REQUEST/RESPONSE message (steps 1301/1302)). More specifically, Served Cell information IE may include FDD Info IE or TDD Info IE, FDD Info IE may include UL BWP List IE and DL BWP List IE, and TDD Info IE may include BWP List IE. But it's okay.
[0067]
　Additionally or alternatively, the Served Cell information IE may include a RACH Configuration IE, and the RACH Configuration IE may indicate radio resource information (eg, PRACH resource) used for preamble transmission in each (UL) BWP. Good. Alternatively, the UL BWP List IE may include the RACH Configuration IE as one of the information elements in each UL BWP. UL BWPs may include BWPs that are not used for RACH (preamble transmission).
[0068]
　Similarly, the BWP-related control information may be transmitted in the X2 interface between the eNB (ie MeNB) and the gNB (ie SgNB) in (NG-)EN-DC. For example, the BWP-related control information may be included in the Served Cell information IE and the Neighbor Information IE in the EN-DC (X2) SETUP REQUEST/RESPONSE message or the EN-DC CONFIGURATION UPDATE/ACKNOWLEDGE message.
[0069]
　FIG. 14 shows an example of the format of (DL/UL) BWP List IE. In the example of FIG. 14, the (DL/UL) BWP List IE includes an information element (Bandwidth Part Item IEs) for defining BWP(s). Each Bandwidth Part Item IE includes BWP Index IE, Location IE, Bandwidth IE, and Subcarrier spacing IE as mandatory information elements (mandatory IEs). BWP Index IE indicates the BWP index of each BWP. Location IE indicates the frequency offset from PRB 0 or cell defining SSB to the lowest PRB of each BWP, for example. Bandwidth IE indicates the total number of PRBs of each BWP or the frequency band. Subcarrier spacing IE indicates Subcarrier spacing (SCS) applied to each BWP. The (DL/UL) BWP List IE may include information indicating the carrier frequency (eg, ARFCN) of each BWP.
[0070]
　The Bandwidth Part Item IE shown in FIG. 14 further includes SSB Presence IE and SSB Position IE as option information elements (option IEs). SSB Presence IE indicates whether BWP includes SSB in the case of FDD-DL or TDD. SSB Position IE indicates the time domain position of SSB. If the BWP does not include the SSB, the Bandwidth Part Item IE may include information indicating the reference SSB.
[0071]
　FIG. 15 shows an example of RAN inter-node signaling (process 1500). FIG. 15 relates to the handover of the UE 23. In step 1501, the source gNB 21 sends the BWP related control information to the target gNB 22 using the HANDOVER REQUEST message. The BWP-related control information (step 1501) includes, for example, the BWP setting regarding the UE 23 to be handed over. Specifically, the BWP-related control information (step 1501) is at least one BWP set for the UE 23 in the source gNB21, at least one BWP activated for the UE 23 in the source gNB21, or both of them. May include an information element indicating. Further or alternatively, the BWP-related control information (step 1501) may include an information element indicating at least one BWP candidate to which the UE 23 is handed over among the plurality of BWPs set in the target gNB 22.
[0072]
　In step 1502, the target gNB 22 sends the BWP related control information to the source gNB 21 using the HANDOVER REQUEST ACKNOWLEDGE message. The BWP related control information (step 1502) may include an information element indicating at least one BWP set (or admitted) for the UE 23 in the target gNB 22.
[0073]
　FIG. 16 shows an example of RAN inter-node signaling (process 1600). FIG. 16 relates to the NR-NR DC of the UE 23, where gNB21 is the MN and gNB22 is the SN. In step 1601, the master gNB 21 sends the BWP related control information to the secondary gNB 22 using the SN ADDITION REQUEST message or the SN MODIFICATION REQUEST message. The SN ADDITION REQUEST message is sent by the master gNB 21 to the secondary gNB 22 to request the preparation of resources for dual connectivity for a particular UE. The SN MODIFICATION REQUEST message is sent by the master gNB 21 to the secondary gNB 22 to request the preparation for modification of the secondary gNB resource for the particular UE. The BWP-related control information (step 1601) includes, for example, an information element indicating at least one BWP candidate used as an SCG SCell for NR-NR DC among the plurality of BWPs set in the secondary gNB 22. The information element may be SCG-ConfigInfo IE (ie, RRC message).
[0074]
　In step 1602, the secondary gNB 22 sends the BWP related control information to the master gNB 21 using the SN ADDITION REQUEST ACKNOWLEDGE message or the SN MODIFICATION REQUEST ACKNOWLEDGE message. The SN ADDITION REQUEST ACKNOWLEDGE message is sent by the secondary gNB 22 to the master gNB 21 to confirm the SN addition preparation. Sent. The SN MODIFICATION REQUEST ACKNOWLEDGE message is sent by the secondary gNB 22 to the master gNB 21 to confirm the master gNB's request to modify the secondary gNB resource. The BWP-related control information (step 1602) is, for example, an information element indicating at least one BWP that has been admitted or activated to perform NR-NR DC for the UE 23 in the secondary gNB 22. Includes. The information element may be SCG-Config IE (ie, RRC message).
[0075]
　In step 1603, the master gNB 21 sends the BWP related control information to the secondary gNB 22 using the SN RECONFIGURATION COMPLETE message. The SN RECONFIGURATION COMPLETE message is sent by the master gNB 21 to the secondary gNB 22 to indicate whether the configuration requested by the secondary gNB 22 has been applied by the UE 23. The BWP-related control information (step 1603) includes, for example, an information element indicating the BWP setting applied by the UE 23. The information element may be SCG-ConfigInfo IE (ie, RRC message).
[0076]
　FIG. 17 shows an example of signaling between the gNB 21 and the UE 23 (process 1700). FIG. 17 relates to switching of active BWP in the setting example of BWP and SS/PBCH block shown in FIG. As an initial state, it is assumed that the UE 23 stays in one of the BWPs included in the logic cell (Cell #1) of the gNB 21. In step 1701, the gNB 21 transmits an RRC Reconfiguration message including BWP related control information for BWP setting to the UE 23. The RRC Reconfiguration message includes the BWP configuration regarding BWP #1 included in the logical cell (Cell #1). The BWP setting specifies SSB #1 in cell defining SSB.
[0077]
　When the UE 23 has already stayed in the BWP #1, the UE 23 sets radio parameters (eg, Layer 2 parameters, L1 parameters) based on the BWP related control information. When the UE 23 is staying in a BWP other than BWP #1, the active BWP is changed to BWP #1 according to the BWP related control information, and the wireless parameter is set. Since this is mobility between different BWPs belonging to one logical cell (Cell #1), the UE 23 may simplify reconfiguration of Layer 2. For example, it is not necessary to re-establish the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer, and to reset the MAC layer. This can be expected to reduce the interruption time of data transmission or reception when the BWP is changed, or avoid data packet loss.
[0078]
　In step 1702, the gNB 21 transmits an RRC Reconfiguration message including BWP related control information for BWP reconfiguration to the UE 23. The BWP-related control information triggers a change in cell defining SSB from SSB #1 to SSB #2 and a change in active BWP from BWP #1 to BWP #2. The UE 23 changes the active BWP to BWP #2 according to the BWP related control information. Since this is also the mobility between different BWPs belonging to one logical cell (Cell #1), the UE 23 may simplify the reconfiguration of Layer 2.
[0079]
　In step 1703, the gNB 21 transmits DCI for changing the active BWP on the PDCCH. The DCI triggers the active BWP change from BWP #2 to BWP #3. The UE 23 changes the active BWP to BWP #3 according to the DCI. However, since BWP #3 does not include SSB, cell defining SSB remains unchanged and remains SSB #2. At this time, the MAC layer (or Physical layer) of the UE 23 may notify the RRC layer of the change of the active BWP, and the RRC layer may change the setting of the radio parameter related to the radio link control as necessary.
[0080]
　If the UE 23 is staying in a logical cell other than the logical cell (Cell #1) in the initial state before Step 1701 in FIG. 17, the RRC Reconfiguration message in Step 1701 indicates that the BWP of the logical cell (Cell #1) has been reached. It may also include a handover instruction to #1. The UE 23 may execute handover according to the instruction.
[0081]
　On the other hand, in the initial state before step 1701 in FIG. 17, the preparation period may be a preparation period in which the UE 23 establishes (or changes) the secondary cell group (SCG) in Dual Connectivity with the gNB 21. In this case, the BWP related control information for BWP setting by the gNB 21 in step 1701 may be transmitted to the UE 23 via the RAN node of the master cell group (MCG) not shown. For example, in NR-NR DC, gNB21 which is SgNB may transmit BWP related control information to Master gNB (MgNB) by the SN ADDITION (or MODIFICATION) REQUEST ACKNOWLEDGE message in SN Addition (or Modification) procedure. And MgNB may transmit the said BWP related control information to UE23 by a RRC Reconfiguration message. Alternatively, in (NG-)EN-DC, the gNB 21, which is the SgNB, transmits the BWP-related control information to the Master eNB (MeNB) by the SN ADDITION REQUEST (or MODIFICATION) ACKNOWLEDGE message in the SN Addition (or Modification) procedure. Good. And MeNB may transmit the said BWP related control information to UE23 by a RRC Connection Reconfiguration message. Alternatively, the gNB 21, which is the SgNB, may directly transmit the BWP-related control information to the UE 23 using the signaling bearer (eg, SRB3) in SCG. UE23 may set SCG for Dual Connectivity according to BWP related control information received from the RAN node of MCG, or gNB21 (SgNB).
[0082]
　According to this embodiment, the information required for BWP setting can be shared between gNBs.
[0083]

　This embodiment provides a specific example of the BWP-related control information described in the first embodiment. FIG. 18 shows a configuration example of the wireless communication network according to this embodiment. In the example of FIG. 18, the wireless communication network includes a gNB Central Unit (CU) 31, a plurality of gNB Distributed Units (DUs) 32, and a UE 33. An interface 1801 connects the gNB-CU 31 and each gNB-DU 32. The interface 1801 is an F1 interface. The UE 33 is connected to at least one gNB-DU 32 via at least one air interface 1802.
[0084]
　In some implementations, gNB-CU 31 may provide at least NR RRC functionality and each gNB-DU 32 may provide at least NR PHY and NR MAC functionality. In such a functional arrangement, the gNB-CU31 determines the BWP(s) set in each gNB-DU32 for the UE33, and the gNB-CU31 sets the BWP(s) for the UE33 and sets each gNB- You may notify the DU 32. Further, the gNB-CU 31 may determine the BWP(s) activated for the UE 33 and notify each gNB-DU 32 of this. Note that each gNB-DU 32 may change the activated BWP(s) (ie active BWP(s)) of the BWP(s) for the UE 33 set by the gNB-CU 31. That is, each gNB-DU 32 may determine activation/deactivation of BWP(s).
[0085]
　Alternatively, each gNB-DU 32 may determine the BWP(s) set for the UE 33, and the gNB-CU 31 may be notified of the BWP(s) information determined by each gNB-DU 32. At this time, gNB-DU32 may further determine the BWP(s) activated for the UE33 and notify the gNB-CU31 of information indicating the BWP(s) activated for the UE33. .. Alternatively, the gNB-CU 31 may determine the BWP(s) to be activated for the UE 33, and notify each gNB-DU 32 of this. Furthermore, each gNB-DU32 changes the BWP(s) (ie active BWP(s)) activated for the UE 33 that the gNB-DU32 has determined by itself (or determined by the gNB-CU31). Good.
[0086]
　FIG. 19 shows an example of RAN inter-node signaling (process 1900). FIG. 19 relates to setting (establishment) and updating of an interface (ie, F1 interface) between the gNB-CU 31 and the gNB-DU 32. In step 1901, the gNB-DU 32 sends an F1 SETUP REQUEST message or a GNB-DU CONFIGURATION UPDATE message to the gNB-CU 31. The F1 SETUP REQUEST message is sent from the gNB-DU 32 to the gNB-CU 31 to establish the F1 interface. The GNB-DU CONFIGURATION UPDATE message is sent from the gNB-DU 32 to the gNB-CU 31 to notify the gNB-CU 31 of the established F1 interface update or the setting update of the gNB-DU 32.
[0087]
　In step 1902, the gNB-CU 31 sends an F1 SETUP RESPONSE message or a GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message to the gNB-DU 32. The F1 SETUP RESPONSE message is a response to the F1 SETUP REQUEST message. The GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message is a response to the GNB-DU CONFIGURATION UPDATE message.
[0088]
　The F1 SETUP REQUEST message or the GNB-DU CONFIGURATION UPDATE message in step 1901 may include BWP-related control information. The BWP-related control information sent in step 1901 may include at least one of the information elements (IEs) included in the above-mentioned BWP-related control information. Further or alternatively, the BWP-related control information is a BWP that can be supported by gNB-DU32, a BWP that is determined to be operated by gNB-DU32 (or a BWP that gNB-DU32 should operate), And/or information about BWPs updated by gNB-DU 32.
[0089]
　The F1 SETUP RESPONSE message or GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message of step 1902 may also include BWP related control information. The BWP-related control information sent in step 1902 may include at least one of the information elements (IEs) included in the above-mentioned BWP-related control information. Further or alternatively, the BWP-related control information is information indicating the BWP(s) accepted (or approved) by the gNB-CU31 among the candidates (list) of BWP(s) notified from the gNB-DU32. , Information indicating the BWP(s) that the gNB-CU31 instructs the gNB-DU32 to activate, and the configuration of the BWP(s) by the gNB-CU31 (eg, SS series or PCI, or SSB presence) Information about at least one of the change request may be included.
[0090]
　FIG. 20 shows an example of RAN inter-node signaling (process 2000). In step 2001, the gNB-CU 31 sends the BWP-related control information to the gNB-DU 32 using a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message. The BWP-related control information (step 2001) includes an information element (configured BWP information) indicating one or more BWPs set by the gNB-CU 31 for the UE 33 connected to the gNB-DU 32.
[0091]
　In step 2002, the gNB-DU 32 sends the BWP-related control information to the gNB-CU 31 using the UE CONTEXT SETUP RESPONSE message or the UE CONTEXT MODIFICATION RESPONSE message. The BWP-related control information of step 2002 includes BWP configuration status information (UE-specific) configuration status of the BWP. The BWP setting status information (step 2002) includes, for example, an information element indicating which BWP of one or more BWPs set by the gNB-CU 31 is activated for the UE 33 in the gNB-DU 32. Include.
[0092]
　The message in step 2001 may be called a UE UP CONTEXT SETUP REQUEST message or a UE UP CONTEXT MODIFICATION REQUEST message. Further, the message of step 2002 may be referred to as a UE UP CONTEXT SETUP RESPONSE message or a UE UP CONTEXT MODIFICATION RESPONSE message. Further, the source and destination of these messages may be opposite.
[0093]
　Further or alternatively, the gNB-DU 32 changes (or has changed) the active BWP, for example, when changing the active BWP of the UE 33 with DCI transmitted on the NR PDCCH, or after changing the active BWP. The BWP index may be transmitted to gNB-CU31. In other words, the gNB-DU 32 may notify the gNB-CU 31 of the update of the UE-specific BWP setting status information. This allows the gNB-CU 31 to know which BWP has been activated for the UE 33. Then, the gNB-CU 31 appropriately changes the radio resource configuration (eg, measurement configuration, Layer 2 configuration) in the RRC Reconfiguration message according to the radio environment or the load situation in the active BWP and other BWPs (or cells) ( It is expected to maintain or improve the radio characteristics (eg, throughput characteristics, quality of service) of the UE 33.
[0094]
　Further or alternatively, each gNB-DU 32 provides to the gNB-CU 31 BWP-related control information including an information element indicating the availability (availability) of network slicing that the gNB-DU 32 can support in each BWP. You may send it. The gNB-CU 31 may determine the gNB-DU 32 to which the UE 33 should connect, or may determine the BWP to be used by the UE 33, based on the control information.
[0095]
　According to this embodiment, the information required for BWP setting can be shared between the gNB-CU 31 and each gNB-DU 32.
[0096]

　This embodiment provides a specific example of the BWP-related control information described in the first embodiment. FIG. 21 shows a configuration example of the wireless communication network according to this embodiment. In the example of FIG. 21, the wireless communication network includes a Control Plane (CP) Unit (gNB-CU-CP) 41 of a gNB Central Unit (CU), a User Plane (UP) Unit (gNB-CU-UP) 42, and a gNB Distributed. The unit (DU) 43 and the UE 44 are included.
[0097]
　The gNB-CU-CP 41 and the gNB-CU-UP 42 are connected by the interface 2101. The interface 2101 is an E1 interface. Further, the gNB-CU-CP 41 and the gNB-DU 43 are connected by the interface 2102. The interface 2102 is an F1-C interface. An interface 2103 connects the gNB-CU-UP 42 and the gNB-DU 43. The interface 2103 is an F1-U interface. The UE 44 is connected to at least one gNB-DU 43 via at least one air interface 2104.
[0098]
　In some implementations, the gNB-CU-CP 41 may provide at least NR RRC functionality and at least part of PDCP functionality (RRC, functionality required for NAS signaling). The gNB-CU-UP 42 may provide at least part of the NR PDCP function (function required for UP data). The gNB-DU 43 may provide at least NR PHY and NR MAC functions. In such a functional arrangement, the gNB-CU-CP41 determines the BWP(s) set in the gNB-DU43 for the UE44, and the gNB-CU-CP41 determines the BWP in the gNB-CU-UP42 and the gNB-DU43. (s) may be set. In addition, the exchange and control of information regarding BWP(s) between the gNB-CU-CP41 and the gNB-DU43 may be the same as that between the gNB-CU31 and the gNB-DU32 in the third embodiment (FIG. 18). Good.
[0099]
　FIG. 22 shows an example of RAN inter-node signaling (process 2200). In step 2201, the gNB-CU-CP 41 sends the BWP-related control information to the gNB-CU-UP 42 using the E1 UE CONTEXT SETUP REQUEST message or the E1 UE CONTEXT MODIFICATION REQUEST message. The BWP-related control information (step 2201) is an information element (configured BWP information) indicating one or more BWPs set by the gNB-CU-CP 41 for the UE 44 connected to the gNB-CU-UP 42. Including.
[0100]
　In step 2202, the gNB-CU-UP 42 sends the BWP-related control information to the gNB-CU-CP 41 using the E1 UE CONTEXT SETUP RESPONSE message or the E1 UE CONTEXT MODIFICATION RESPONSE message. The BWP-related control information in step 2202 includes BWP configuration status information regarding the UE-specific configuration status of the BWP.
[0101]
　The message of step 2201 may be called an E1 UE UP CONTEXT SETUP REQUEST message or a UE UP CONTEXT MODIFICATION REQUEST message. Also, the message of step 2202 may be referred to as an E1 UE UP CONTEXT SETUP RESPONSE message or a UE UP CONTEXT MODIFICATION RESPONSE message. Further, the source and destination of these messages may be opposite.
[0102]
　Subsequently, hereinafter, configuration examples of the RAN node 11, gNB21, gNB22, gNB-CU31, gNB-DU32, UE23, UE33, and UE44 according to the above-described plurality of embodiments will be described. FIG. 23 is a block diagram showing a configuration example of the RAN node 11 according to the above embodiment. Referring to FIG. 23, the RAN node 11 includes a Radio Frequency transceiver 2301, a network interface 2303, a processor 2304, and a memory 2305. The RF transceiver 2301 performs analog RF signal processing to communicate with NG UEs. The RF transceiver 2301 may include multiple transceivers. The RF transceiver 2301 is coupled with the antenna array 2302 and the processor 2304. The RF transceiver 2301 receives the modulation symbol data from the processor 2304, generates a transmission RF signal, and supplies the transmission RF signal to the antenna array 2302. The RF transceiver 2301 also generates a baseband received signal based on the received RF signal received by the antenna array 2302, and supplies this to the processor 2304. The RF transceiver 2301 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.
[0103]
　The network interface 2303 is used to communicate with network nodes (eg, NG Core control node and transfer node). The network interface 2303 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.
[0104]
　The processor 2304 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Processor 2304 may include multiple processors. For example, the processor 2304 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 (CPU) that performs control plane processing. MPU)) may be included. Processor 2304 may include a digital beamformer module for beamforming. The digital beamformer module may include a Multiple Input Multiple Output (MIMO) encoder and precoder.
[0105]
　The memory 2305 is composed of a combination of a volatile memory and a 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 Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, hard disk drive, or any combination thereof. Memory 2305 may include storage located remotely from processor 2304. In this case, the processor 2304 may access the memory 2305 via the network interface 2303 or an I/O interface (not shown).
[0106]
　The memory 2305 may store one or more software modules (computer programs) 2306 including a command group and data for performing processing by the RAN node 11 described in the above-described embodiments. In some implementations, the processor 2304 may be configured to perform the processing of the RAN node 11 described in the above embodiments by reading the software module 2306 from the memory 2305 and executing the software module 2306.
[0107]
　Note that the configurations of gNB21, gNB22, gNB-CU31, and gNB-DU32 may be the same as that shown in FIG. However, the gNB-CU 31 may not include the RF transceiver 2301 (and the antenna array 2302).
[0108]
　FIG. 24 is a block diagram showing a configuration example of the UE 23. The configurations of the UE 33 and the UE 44 may be similar to that shown in FIG. Radio Frequency (RF) transceiver 2401 performs analog RF signal processing to communicate with RAN node 11. The RF transceiver 2401 may include multiple transceivers. The analog RF signal processing performed by the RF transceiver 2401 includes frequency up conversion, frequency down conversion, and amplification. RF transceiver 2401 is coupled to antenna array 2402 and baseband processor 2403. The RF transceiver 2401 receives modulated symbol data (or OFDM symbol data) from the baseband processor 2403, generates a transmission RF signal, and supplies the transmission RF signal to the antenna array 2402. The RF transceiver 2401 also generates a baseband reception signal based on the reception RF signal received by the antenna array 2402, and supplies this to the baseband processor 2403. The RF transceiver 2401 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.
[0109]
　The baseband processor 2403 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression/decompression, (b) data segmentation/concatenation, (c) transmission format (transmission frame) generation/decomposition, and (d) transmission channel coding/decoding. , (E) modulation (symbol mapping)/demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). On the other hand, the control plane processing includes layer 1 (eg, transmission power control), layer 2 (eg, radio resource management, and hybrid automatic repeat request (HARQ) processing), and layer 3 (eg, attach, mobility, and call management). Signaling management).
[0110]
　For example, the digital baseband signal processing by the baseband processor 2403 includes signal processing of Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, MAC layer, and PHY layer. May be included. The control plane processing by the baseband processor 2403 may include processing of Non-Access Stratum (NAS) protocol, RRC protocol, and MAC CE.
[0111]
　The baseband processor 2403 may perform MIMO encoding and precoding for beamforming.
[0112]
　The baseband processor 2403 may include a modem processor (eg, DSP) that performs digital baseband signal processing and a protocol stack processor (eg, CPU or MPU) that performs control plane processing. In this case, the protocol stack processor that performs the control plane process may be shared with the application processor 2404 described later.
[0113]
　The application processor 2404 is also called a CPU, MPU, microprocessor, or processor core. The application processor 2404 may include a plurality of processors (a plurality of processor cores). The application processor 2404 is a system software program (Operating System (OS)) read from the memory 2406 or a memory (not shown) and various application programs (for example, call application, WEB browser, mailer, camera operation application, music playback). Various functions of the UE 23 are realized by executing an application.
[0114]
　In some implementations, the baseband processor 2403 and the application processor 2404 may be integrated on a single chip, as shown by the dashed line (2405) in FIG. In other words, the baseband processor 2403 and the application processor 2404 may be implemented as one System on Chip (SoC) device 2405. SoC devices are also sometimes referred to as system large scale integration (LSI) or chipsets.
[0115]
　The memory 2406 is a volatile memory or a non-volatile memory or a combination thereof. Memory 2406 may include multiple physically independent memory devices. Volatile memory is, for example, SRAM or DRAM or a combination thereof. The non-volatile memory is MROM, EEPROM, flash memory, or hard disk drive, or any combination thereof. For example, the memory 2406 may include a baseband processor 2403, an application processor 2404, and an external memory device accessible by the SoC 2405. Memory 2406 may include embedded memory devices integrated within baseband processor 2403, application processor 2404, or SoC 2405. Further, the memory 2406 may include a memory in a Universal Integrated Circuit Card (UICC).
[0116]
　The memory 2406 may store one or more software modules (computer programs) 2407 including a command group and data for performing processing by the UE 23 described in the above-described embodiments. In some implementations, the baseband processor 2403 or the application processor 2404 is configured to read the software module 2407 from the memory 2406 and execute it to perform the processing of the UE 23 described in the above embodiments with reference to the drawings. May be done.
[0117]
　Note that the control plane processing and operation performed by the UE 23 described in the above embodiments are performed by other elements except the RF transceiver 2401 and the antenna array 2402, that is, at least one of the baseband processor 2403 and the application processor 2404, and the software module 2407. And a memory 2406 that stores
[0118]
　As described with reference to FIG. 23 and FIG. 24, each of the processors included in the RAN node 11, gNB21, gNB22, gNB-CU31, gNB-DU32, UE23, and UE33 according to the above-described embodiment uses the drawings. Executes one or more programs containing instructions for causing a computer to perform the described algorithm. This program can be stored using various types of non-transitory computer readable media, and can be supplied to a computer. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer readable media are magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD- R, CD-R/W, semiconductor memory (for example, mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM)) are included. In addition, the program may be supplied to the computer by various types of transitory computer readable media. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. The transitory 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.
[0119]
The
　above-described embodiments may be implemented independently, or all or a part of the embodiments may be implemented in an appropriate combination.
[0120]
　In the above embodiment, switching of active BWP by DCI transmitted on NR PDCCH has been described. However, the switching of the active BWP in the above embodiment may be performed by the MAC CE or the timer (eg, BWP Inactivity Timer).
[0121]
　In the above-described embodiment, the explanation has been made mainly on the assumption that one BWP is activated for each UE (ie 1 active BWP per UE). However, it goes without saying that the method described in the above embodiments can be applied to the case where multiple BWPs are activated for each UE. For example, there may be multiple active BWPs in a BWP set. Furthermore, there may be one active BWP corresponding to each of the plurality of BWP groups set in the BWP set, or there may be multiple active BWPs in the BWP group.
[0122]
　In the above embodiments, the UE 23 (33, 44) may support multiple (DL/UL) active BWPs within the channel band of one component carrier. In this case, the UE 23 (33, 44) performs signal processing (eg, signal Transmission/reception, TB/PDU generation, Baseband processing) may be performed. Alternatively, the UE 23 (33, 44) may perform signal processing in one wide band BWP (or wide band cell) in which a plurality of BWPs are combined. The UE 23 (33, 44) may establish a bearer (ie, SRB, DRB) for a specific active BWP. The UE 23 (33, 44) may duplicately transmit information (ie, control signaling, data) of one bearer in a plurality of active BWPs (ie, duplication). In addition, establishment of a bearer for a specific active BWP and duplicate transmission in a plurality of active BWPs may be set by a logical channel identifier (Logical Channel ID).
[0123]
　The embodiments described above may be used instead of BWP for Supplemental Uplink (SUL) being considered in 3GPP. SUL uses, for example, UL (low) and downlink (DL) carriers in the high frequency band as basic components of the cell, while using UL carriers in the low frequency band as additional carriers (ie, SUL carriers). To do. The SUL carrier is treated as a part of the UL carrier associated with the DL carrier in the high frequency band, not the secondary cell configured with only the UL carrier. Specifically, a plurality of RAN nodes may exchange SUL-related information for setting and switching UL carriers for SUL. For example, the SUL-related information may include information indicating that the BWP corresponding to the SUL carrier is the SUL carrier (eg, BWP Type=SUL, SUL Index). The bandwidth of BWP corresponding to the SUL carrier may be smaller than the SSB bandwidth.
[0124]
　The above embodiments can ensure that the RAN node properly knows and manages the active BWP for the UE. Therefore, when the UE moves from the Connected mode (eg, NR RRC_Connected) to the Idle mode (eg, NR RRC_Idle), information about the active BWP of the UE may be notified from the RAN node to the CN node. In other words, the RAN node (eg, gNB) may send to the CN node (eg, AMF) information about the active BWP of the UE that releases the RRC connection and the NG connection. The information on the active BWP includes, for example, the index of the active BWP at which the UE was last staying or the corresponding PCI, and Cell Identity information including the same. For example, this information may be sent in a UE CONTEXT RELEASE REQUEST message or a UE CONTEXT RELEASE COMPLETE message from the RAN node to the CN node. The information regarding the active BWP may be used (referenced) in the CN node in the transmission of paging to the UE that occurs later. Additionally or alternatively, the CN node may send information about the active BWP together with a paging message to the RAN node, and the RAN node may use (reference) the information in determining the paging destination (cell or BWP). ..
[0125]
　For example, the transmission of the paging message in the first paging occasion may be performed only in the BWP, BWPs associated with the BWP, or a plurality or all BWPs of the logic cells including the BWP. Thereby, while maintaining the probability that the paging message reaches the target UE at a predetermined target value, it is possible to reduce signaling overhead and network power consumption by reducing the cell (BWP) that transmits the paging message. ..
[0126]
　In the above embodiment, the term cell defining SSB is used, but this refers to the BWP corresponding to the cell (physical cell) from the UE perspective, or the SSB representing the BWP group corresponding to the set of the physical cells, May be called cell representative SSB. Alternatively, the cell defining SSB may be referred to as a cell specifying SSB from the viewpoint of specifying a representative cell (physical cell) including the SSB. Further, the cell defining SSB may be referred to as a serving SSB because it is the SSB that the UE should monitor when staying in either the BWP or BWP group that contains it.
[0127]
　The sub PCI described in the above embodiment may be associated with the BWP index.
[0128]
　The reference BWP described in the above embodiments may be referred to as default BWP, initial BWP, reference BWP, primary BWP, anchor BWP, or master BWP. That is, the BWP that stays first when the UE first accesses the RAN node (ie, when transitioning from Idle mode to Connected mode) is the reference BWP, default BWP, initial BWP, reference BWP, primary BWP, anchor BWP. , Or master BWP. Further or alternatively, among the plurality of BWPs included in the system band, the BWP that is not the reference BWP may be referred to as sub BWP, secondary BWP, slave BWP.
[0129]
　Further, the above-described embodiment is merely an example regarding application of the technical idea obtained by the present inventor. That is, the technical idea is not limited to the above-described embodiment, and it goes without saying that various modifications can be made.
[0130]
　The whole or part of the exemplary embodiments disclosed above can be described as, but not limited to, the following supplementary notes.
[0131]
(Supplementary Note 1)
　A radio access network (RAN) node device,
　a memory,
　and at least one processor coupled to said memory,
comprising a
　at least one processor, 1 or set in the system band A
RAN node device configured to send first control information for at least one of the more bandwidth parts (BWPs) to another RAN node.
[0132]
(Supplementary Note 2)
　The first control information includes at least one information element of the following:
- one or more information elements indicating one or more BWP index associated with the downlink behind the bwps;
- An information element indicating one or more BWP indexes associated with one or more uplink BWPs; an information element indicating
an Absolute Radio Frequency Channel Number (ARFCN) associated with
each BWP ; An information element indicating whether to include a block (SSB);
- An information element indicating a reference SSB associated with a BWP that does not include SSB or a reference BWP including the reference SSB;
-The SSB transmitted by each BWP An information element indicating the configuration; and
an information element indicating the numerology set in each BWP,
the RAN node device according to appendix 1.
[0133]
(Supplementary note 3)
　The first control information includes one logical cell identifier associated with a cell corresponding to the system band and a Physical Cell Identity (PCI) associated with each BWP included in the one or more BWPs. )
The RAN node device according to attachment 1 or 2 , which includes an information element indicating a relationship with the RAN node device.
[0134]
(Supplementary Note 4)
　The first control information further includes an information element indicating the availability of network slicing in each BWP or each BWP set and a quality of service supported by each BWP or each BWP set.
The RAN node device according to attachment 2 or 3 , which includes at least one of information elements indicating (QoS) .
[0135]
(Supplementary Note 5) The
　RAN node device includes a Central Unit (CU) that provides at least a Radio Resource Control (RRC) function, and the
　other RAN node has at least a Distributed Unit ( CU) that provides a Medium Access Control (MAC) function. DU),
　wherein the at least one processor is supported by the DU in response to receiving from the other RAN node second control information indicating one or more BWPs supported by the DU. 5. One of
supplementary notes 1 to 4 , which is configured to transmit the first control information including an information element indicating a permitted BWP among one or more BWPs to be transmitted to the other RAN node. RAN node device described in.
[0136]
(Supplementary Note 6) The
　RAN node device includes at least a Central Unit (CU) that provides a Radio Resource Control (RRC) function, and the
　other RAN node includes at least a Distributed Unit ( CU) that provides a Medium Access Control (MAC) function. DU),
　the first control information includes an information element indicating one or more BWPs set by the CU for a wireless terminal connecting to the DU, and the
　at least one processor further comprises: , Third control information including an information element indicating which BWP of the one or more BWPs set by the CU is activated for the wireless terminal in the DU. 5.
The RAN node device according to any one of appendices 1 to 4 , which is configured to transmit to the RAN node.
[0137]
(Supplementary note 7) The
　at least one processor may further include fourth control information including an information element indicating a BWP activated for a wireless terminal connected to the DU, which is determined or changed by the DU.
7. The RAN node device according to appendix 6, which is configured to be received from the RAN node.
[0138]
(Supplementary Note 8) The
　at least one processor is configured to transmit the first control information to the other RAN node when a wireless terminal is handed over from the RAN node device to the other RAN node,
　The first control information is at least one BWP configured for the wireless terminal in the RAN node device, or at least one BWP activated for the wireless terminal in the RAN node device, or these
5. The RAN node device according to any one of appendices 1 to 4 , which includes an information element indicating both .
[0139]
(Supplementary note 9) The
　at least one processor is configured to transmit the first control information to the other RAN node when a wireless terminal is handed over from the RAN node device to the other RAN node,
　The first control information includes an information element indicating at least one BWP candidate to which the wireless terminal is handed over among a plurality of BWPs set in the other RAN node, any one of appendices
1 to 4 RAN node device according to the item.
[0140]
(Supplementary Note 10) The
　at least one processor is configured to transmit the first control information to the other RAN node when a wireless terminal is handed over from the other RAN node to the RAN node device,
　5. The RAN node device according to any one of appendices
1 to 4, wherein the first control information includes an information element indicating at least one BWP set for the wireless terminal in the RAN node device.
[0141]
(Supplementary note 11) The
　at least one processor is configured to transmit the first control information to the other RAN node when performing dual connectivity for a wireless terminal in cooperation with the other RAN node. ,
　The first control information includes an information element indicating at least one BWP candidate used for the dual connectivity among a plurality of BWPs set in the other RAN node
. The RAN node device according to any one of items.
[0142]
(Supplementary Note 12) The
　at least one processor transmits fifth control information including information elements indicating at least one BWP activated to perform the dual connectivity in the other RAN node, to the other RAN node.
The RAN node device according to appendix 11, which is configured to receive from the RAN node device.
[0143]
(Supplementary note 13)
　A method in a radio access network (RAN) node device, wherein
　first control information relating to at least one of one or more bandwidth parts (BWPs) set in a system band is provided to another RAN. A
method comprising sending to a node .
[0144]
(Supplementary Note 14)
　The first control information includes at least one information element of the following:
- one or more information elements indicating one or more BWP index associated with the downlink behind the bwps;
- An information element indicating one or more BWP indexes associated with one or more uplink BWPs; an information element indicating
an Absolute Radio Frequency Channel Number (ARFCN) associated with
each BWP ; Information element indicating whether to include a block (SSB);
- Information element indicating a reference SSB associated with a BWP that does not include SSB or a reference BWP including the reference SSB;
- The information element indicating the configuration; and the information element indicating
the numerology set in each BWP,
the method described in appendix 13.
[0145]
(Supplementary Note 15)
　The first control information includes one logical cell identifier associated with a cell corresponding to the system band and a Physical Cell Identity (PCI) associated with each BWP included in the one or more BWPs. )
The method according to appendix 13 or 14 , which includes an information element indicating a relationship with
[0146]
(Supplementary Note 16)
　The first control information further includes an information element indicating the availability of network slicing in each BWP or each BWP set and a quality of service supported by each BWP or each BWP set.
16. The method according to attachment 14 or 15 , including at least one of information elements indicating (QoS) .
[0147]
(Supplementary Note 17) The
　RAN node device includes a Central Unit (CU) that provides at least a Radio Resource Control (RRC) function, and the
　other RAN node has a Distributed Unit ( CU) that provides at least a Medium Access Control (MAC) function. DU), the
　sending being supported by the DU in response to receiving from the other RAN node second control information indicating one or more BWPs supported by the DU. The method according to any one of appendices
13 to 16, comprising sending the first control information including an information element indicating an allowable BWP among one or more BWPs to the other RAN node .
[0148]
(Supplementary Note 18) The
　RAN node device includes at least a Central Unit (CU) that provides a Radio Resource Control (RRC) function, and the
　other RAN node includes at least a Distributed Unit ( CU) that provides a Medium Access Control (MAC) function. DU),
　the first control information includes an information element indicating one or more BWPs configured by the CU for a wireless terminal connecting to the DU, the
　method further comprising: To the other RAN node, third control information including an information element indicating which BWP of the one or more BWPs set up by the DU is activated for the wireless terminal in the DU. The method according to
any one of appendices 13 to 16 , comprising transmitting .
[0149]
(Supplementary Note 19)
　Receiving fourth control information from the other RAN node, the fourth control information including an information element indicating a BWP activated for the wireless terminal connected to the DU, which is determined or changed by the DU.
19. The method of appendix 18, further comprising .
[0150]
(Supplementary note 20)
　A program for causing a computer to perform a method in a radio access network (RAN) node device, the method
　being at least one of one or more bandwidth parts (BWPs) set in a system band. A
program comprising sending first control information for one to another RAN node .
[0151]
　This application claims the priority on the basis of Japanese application Japanese Patent Application No. 2017-218041 for which it applied on November 13, 2017, and takes in those the indications of all here.
Explanation of symbols
[0152]
11, 12 RAN node
21, 22 gNB
31 gNB-CU
32 gNB-DU
41 gNB-CU-CP
42 gNB-CU-UP
43 gNB-DU
23, 33, 44 UE
1001 interface
1201 Xn interface
1801 F1 interface
2304 processor
2305 Memory
2403 Baseband processor
2404 Application processor
2406 Memory
The scope of the claims
[Request item 1]
　A radio access network (RAN) node device,
　memory and,
　at least one processor coupled to the memory,
provided with,
　at least one processor, one or more of the bandwidth is set in the system band A
RAN node device configured to send first control information for at least one of the parts (BWPs) to another RAN node.
[Request item 2]
　The first control information includes at least one of the following information elements:
an information element indicating one or more BWP indexes associated with one or more downlink BWPs;
one or more An information element indicating one or more BWP indexes associated with the uplink BWPs of the:; an information element indicating
an Absolute Radio Frequency Channel Number (ARFCN) associated with
each BWP ; A synchronization signal block (SSB) for each BWP. information element indicating whether embraces;
- does not encompass SSB references associated with BWP SSB or information element indicating the reference BWP including the reference SSB;
& information indicating the configuration of SSB that is transmitted in each BWP Element; and
an information element indicating the numerology set in each BWP,
the RAN node device according to claim 1.
[Request item 3]
　The first control information is a relationship between one logical cell identifier associated with a cell corresponding to the system band and a physical cell identity (PCI) associated with each BWP included in the one or more BWPs.
The RAN node device according to claim 1 or 2 , which includes an information element indicating sex .
[Request item 4]
　The first control information further includes an information element indicating availability of network slicing in each BWP or each BWP set and a quality of service (QoS) supported by each BWP or each BWP set.
The RAN node device according to claim 2 or 3 , which includes at least one of the information elements shown .
[Request 5]
　The RAN node device includes at least a Central Unit (CU) that provides a Radio Resource Control (RRC) function, and the
　other RAN node includes at least a Distributed Unit (DU) that provides a Medium Access Control (MAC) function. , The
　at least one processor is responsive to receiving from the other RAN node second control information indicating one or more BWPs supported by the DU, 1 or 2 being supported by the DU. 5. The method according to
any one of claims 1 to 4, wherein the first control information including an information element indicating a permitted BWP among more BWPs is configured to be transmitted to the other RAN node . RAN node device.
[Request 6]
　The RAN node device includes at least a Central Unit (CU) that provides a Radio Resource Control (RRC) function, and the
　other RAN node includes at least a Distributed Unit (DU) that provides a Medium Access Control (MAC) function. ,
　The first control information includes an information element indicating one or more BWPs set by the CU for a wireless terminal connecting to the DU, the
　at least one processor further comprising: Send third control information to the other RAN node including an information element indicating which BWP of the one or more BWPs to be configured is activated for the wireless terminal in the DU
The RAN node device according to any one of claims 1 to 4 , which is configured to perform .
[Request 7]
　The at least one processor may provide fourth control information from the other RAN node, the fourth control information including an information element indicating a BWP activated for a wireless terminal connected to the DU, which is determined or changed by the DU.
The RAN node device according to claim 6, wherein the RAN node device is configured to receive .
[Request 8]
　Wherein the at least one processor, when the radio terminal is handed over from the RAN node device to the other RAN node is configured to transmit the first control information to the other RAN node,
　the first The control information is information indicating at least one BWP configured for the wireless terminal in the RAN node device, at least one BWP activated for the wireless terminal in the RAN node device, or both.
The RAN node device according to any one of claims 1 to 4 , which includes elements .
[Request 9]
　Wherein the at least one processor, when the radio terminal is handed over from the RAN node device to the other RAN node is configured to transmit the first control information to the other RAN node,
　the first control information includes an information element indicating at least one BWP candidates said radio terminal is handed among the plurality of BWP set on the other RAN node
according to any one of claims 1 to 4, RAN node equipment.
[Request item 10]
　Wherein the at least one processor, when the radio terminal is handed over from the other RAN node to the RAN node device is configured to transmit the first control information to the other RAN node,
　the first The RAN node device according
to any one of claims 1 to 4 , wherein the control information includes an information element indicating at least one BWP set for the wireless terminal in the RAN node device.
[Request 11]
　Wherein the at least one processor, when performing dual connectivity for wireless terminals in conjunction with the other RAN node is configured to transmit the first control information to the other RAN node,
　the first control information includes an information element indicating at least one BWP candidates used for the dual connectivity among the plurality of BWP set on the other RAN node,
any of claims 1 to 4, 1 RAN node device according to the item.
[Request 12]
　The at least one processor is configured to receive from the other RAN node fifth control information including an information element indicating at least one BWP activated to perform the dual connectivity in the other RAN node.
The RAN node device according to claim 11, which is configured .
[Request 13]
　A method in a radio access network (RAN) node device, wherein
　first control information relating to at least one of one or more bandwidth parts (BWPs) set in a system band is sent to another RAN node. Comprising a
method.
[Request 14]
　The first control information includes at least one of the following information elements:
an information element indicating one or more BWP indexes associated with one or more downlink BWPs;
one or more An information element indicating one or more BWP indexes associated with the uplink BWPs of the:; an information element indicating
an Absolute Radio Frequency Channel Number (ARFCN) associated with
each BWP ; information element indicating whether embraces;
- does not encompass SSB references associated with BWP SSB or information element indicating the reference BWP including the reference SSB;
& information indicating the configuration of SSB that is transmitted in each BWP Element; and
an information element indicating the numerology set for each BWP,
the method according to claim 13.
[Request 15]
　The first control information is a relationship between one logical cell identifier associated with a cell corresponding to the system band and a Physical Cell Identity (PCI) associated with each BWP included in the one or more BWPs. 15.
A method according to claim 13 or 14 including an information element indicating sex .
[Request item 16]
　The first control information further includes an information element indicating the availability of network slicing in each BWP or each BWP set and a quality of service (QoS) supported by each BWP or each BWP set.
16. A method according to claim 14 or 15 including at least one of the indicated information elements .
[Request item 17]
　The RAN node device includes at least a Central Unit (CU) that provides a Radio Resource Control (RRC) function, and the
　other RAN node includes at least a Distributed Unit (DU) that provides a Medium Access Control (MAC) function. , The
　sending is responsive to receiving from the other RAN node second control information indicating one or more BWPs supported by the DU, one or more supported by the DU. 17. The
method according to any one of claims 13 to 16, comprising sending the first control information including an information element indicating a permitted BWP among the BWPs of the other RAN to the other RAN node .
[Request 18]
　The RAN node device includes at least a Central Unit (CU) that provides a Radio Resource Control (RRC) function, and the
　other RAN node includes at least a Distributed Unit (DU) that provides a Medium Access Control (MAC) function. ,
　The first control information includes an information element indicating one or more BWPs set by the CU for a wireless terminal connecting to the DU, and the
　method is further set by the CU Transmitting to the other RAN node third control information including an information element indicating which BWP of the one or more BWPs is activated for the wireless terminal in the DU; comprising,
a method according to any one of claims 13 to 16.
[Request item 19]
　Further comprising receiving a fourth control information including an information element indicating BWP to be activated for the wireless terminal to be connected to the DU determined or changed by the DU from the other RAN node,
wherein Item 18. The method according to Item 18.
[Request item 20]
　A non-transitory computer-readable medium storing a program for causing a computer to perform a method in a radio access network (RAN) node device, the method
　comprising one or more bandwidth parts set within a system band. A
non-transitory computer-readable medium comprising sending first control information for at least one of (BWPs) to another RAN node .