The present disclosure relates to a wireless communication system, and more particularly to a communication in which a wireless terminal uses a plurality of cells of different Radio Access Technologies (RATs) operated by different radio stations at the same time.
Background technology
[0002]
　The 3rd Generation Partnership Project (3GPP) started standardization work of the 5th generation mobile communication system (5G) for introduction after 2020 as 3GPP Release 14 in 2016 (see Non-Patent Document 1). 5G is realized by a combination of continuous improvement / evolution of LTE and LTE-Advanced and innovative improvement / 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 by the continuous development of LTE / LTE-Advanced, such as a centimeter wave band of 10 GHz or more and a millimeter of 30 GHz or more. Supports wave bands.
[0003]
　As used herein, the 5th 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 the 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 NextGen Core (NG Core). A wireless terminal (User Equipment (UE)) that connects to a 5G System is called a 5G UE, NextGen UE (NG UE), or simply UE. Formal names for RAT, UE, radio access networks, core networks, network entities (nodes), and protocol layers for 5G systems will be determined in the future as standardization work progresses.
[0004]
　In addition, the term “LTE” as used herein includes improvements and developments of LTE and LTE-Advanced to enable interworking with 5G Systems, unless otherwise specified. Improvements and developments of LTE and LTE-Advanced for interworking with 5G Systems are also called LTE-Advanced Pro, LTE +, or enhanced LTE (eLTE). In addition, “Evolved Packet Core (EPC)”, “Mobility Management Entity (MME)”, “Serving Gateway (S-GW)”, and “Packet Data Network (PDN) Gateway (P-GW)” as used herein. ) ”And other terms relating to LTE networks or logical entities include these improvements and developments to enable interworking with 5G Systems, unless otherwise noted. Improved EPC, MME, S-GW, and P-GW include, for example, enhanced EPC (eEPC), enhanced MME (eMME), enhanced S-GW (eS-GW), and enhanced P-GW (eP-GW). ) Also called.
[0005]
　In LTE and LTE-Advanced, for quality of service (QoS) and packet routing, bearers for each QoS class and each PDN connection are RAN (ie, Evolved Universal Terrestrial RAN (E-UTRAN)) and core network (ie, Used in both EPC). That is, in the Bearer-based QoS (or per-bearer QoS) concept, one or more Evolved Packet System (EPS) bearers are configured between the UE and the P-GW in the EPC, and multiple Evolved Packet System (EPS) bearers with the same QoS class. Service Data Flows (SDFs) are transferred through a single EPS bearer that satisfies these QoS. An SDF is one or more packet flows that match an SDF template (ie, packet filters) based on Policy and Charging Control (PCC) rules. Also, for packet routing, each packet sent through the EPS bearer identifies which bearer (ie, General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel) the packet is associated with. ) Includes information for.
[0006]
　In contrast, in 5G Systems, wireless bearers may be used in 5G-RAN, but it is considered that bearers are not used within 5G-CN and in the interface between 5G-CN and 5G-RAN. (See Non-Patent Document 1). 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 in NG Core (ie, the entity equivalent to P-GW in EPC) corresponds to the EPS bearer in the EPS Bearer-based QoS concept. The PDU flow corresponds to the finest granularity of packet forwarding and treatment within the 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. In the 5G system's QoS framework, the PDU flow is identified by the PDU flow ID in the header that encapsulates the Service Data Unit of the tunnel on the NG3 interface. NG3 interface is 5G-CN and gNB (ie, It is a user plane interface between 5G-RAN). The association between the 5G UE and the data network is called the PDU session. PDU session is a term equivalent to LTE and LTE-Advanced PDN connection. Multiple PDU flows can be configured in one PDU session.
[0007]
　The PDU flow is also called "QoS flow". QoS flow is the finest granularity of QoS treatment within a 5G system. User plane traffic with the same NG3 marking value in the PDU session corresponds to the QoS flow. The NG3 marking corresponds to the PDU flow ID described above, is also called a QoS flow ID, and is also called a Flow Identification Indicator (FII).
[0008]
　Further, it is also considered that the 5G System supports network slicing (see Non-Patent Document 1). Network slicing uses Network Function Virtualization (NFV) and software-defined networking (SDN) technologies to enable the creation of multiple virtualized logical networks on top of physical networks. Each virtualized logical network is called a network slice or network slice instance and contains logical nodes and functions for specific traffic. And used for signaling. 5G-RAN and / or 5G-CN have a Slice Selection Function (SSF). The SSF selects one or more network slices suitable for the 5G UE based on the information provided by at least one of the 5G UE and the 5G-CN.
[0009]
　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. 5G-CN and gNB establish control plane interface and user plane interface for UE. The control plane interface between 5G-CN and gNB (ie, RAN) is called the NG2 interface or NG-c interface, which transfers Non-Access Stratum (NAS) information and controls between 5G-CN and gNB. Used for information (eg, NG2 AP Information Element). The user plane interface between 5G-CN and gNB (ie, RAN), called the NG3 or NG-u interface, is the forwarding of one or more PDU flows packets within a UE's PDU session. Used for.
[0010]
　The architecture shown in FIG. 1 is only one of a plurality of 5G architecture options (or deployment scenarios) (see Annex J of Non-Patent Document 1 and Non-Patent Document 2). The architecture shown in FIG. 1 is an architecture called "Standalone NR (in NextGen System)" or "Option 2". In contrast, FIGS. 2 and 3 show architecture options 3 and 3A called "Non-standalone NR in EPS", respectively. In FIGS. 2 and 3, the control plane interface is shown by the dotted line and the user plane interface is shown by the solid line. Architecture options 3 and 3A are Dual connectivity (DC) deployments that include E-UTRA as the anchor RAT (or primary or master RAT) and NR as the secondary RAT. In options 3 and 3A, E-UTRA (LTE eNB) and NR (gNB) are connected to the EPC. The NR user plane connection to the EPC goes through LTE eNB in ​​option 3 but directly through the user plane interface between gNB and EPC in option 3A.
[0011]
　Non-Patent Document 3 proposes that NR gNB supports LTE's DC functions and procedures in architecture options 3 and 3A, that is, DC architectures in which E-UTRA and NR are connected to EPC. doing. Furthermore, Non-Patent Document 3 applies the LTE QoS framework (ie, bearer based QoS) to EPC, LTE eNB, and UE in the DC architecture in which E-UTRA and NR are connected to EPC. I am proposing to do it. More specifically, Non-Patent Document 3 proposes the following items:
・ LTE DC for setting the required QoS service (ie, bearer) when NR gNB is added as a secondary node. Procedures (eg, SeNB addition) apply;
• E-UTRAN Radio Access Bearer (E-RAB) established between EPC and NR gNB for LTE Secondary Cell Group (SCG) bearer option To be done;
• X2-U is established between LTE eNB and gNB for LTE split bearer option;
• NR gNB for LTE SCG bearer and split bearer options A DRB is established between and UE.
[0012]
　Non-Patent Document 4 proposes that in architecture option 3A, there is a one-to-one mapping (1: 1 mapping) between S1-U and DRB (ie, SCG bearer) of SCG. Non-Patent Document 4 further states that the QoS attributes of EPC are used for EPS bearers, and therefore the QoS parameters used in EPC are used in NR for radio bearers. It suggests that it needs to be mapped to parameters).
[0013]
　Also, NR is expected to use different radio parameter sets for multiple frequency bands. Each radio parameter set is called "numerology". OFDM numerology for Orthogonal Frequency Division Multiplexing (OFDM) systems includes, for example, subcarrier spacing, system bandwidth, Transmission Time Interval (TTI) length, and sub. Includes subframe duration, cyclic prefix length, and symbol duration. The 5G system provides various types of services with different service requirements, such as enhanced Mobile Broad Band (eMBB), Ultra Reliable and Low Latency Communication (URLLC), and multi-connection M2M communication (massive). Supports, including Machine Type Communication: mMTC). The choice of Numerology depends on the service requirements.
[0014]
　The UE and NR gNB of the 5G system support the aggregation of multiple NR carriers with different numbers. In 3GPP, the aggregation of multiple NR carriers with different numeratorologies is either lower layer aggregation such as existing LTE Carrier Aggregation (CA) or higher layer aggregation such as existing Dual Connectivity. (See, for example, Non-Patent Document 5-7).
Prior art literature
Non-patent literature
[0015]
Non-Patent Document 1: 3GPP TR 23.799 V14.0.0 (2016-12) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14)”, December 2016
Non-Patent Document 2: 3GPP TR 38.801 V1.0.0 (2016-12) “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology; Radio Access Architecture and Interfaces (Release 14)”, December 2016
Non-Patent Document 3: 3GPP R2-168400, NTT DOCOMO, INC., “QoS and bearer for DC between LTE and NR”, 3GPP TSG-RAN WG2 Meeting # 96, Reno, USA, 14-18 November 2016
Non-Patent Document 4: 3GPP R2-168686, Nokia, Alcatel-Lucent Shanghai Bell, “EPC --NR PDCP interaction for tight interworking: User Plane aspects”, 3GPP TSG-RAN WG2 Meeting # 96, Reno, USA, 14-18 November 2016
Non-Patent Document 5: 3GPP TR 38.804 V0.4.0 (2016-11) “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology; Radio Interface Protocol Aspects (Release 14)”, November 2016
Non Patent Document 6: 3GPP R2-164788, Nokia, Alcatel-Lucent Shanghai Bell, “Carrier Aggregation between carriers of different air interface numerologies”, 3GPP TSG-RAN WG2 Meeting # 95, Gothenburg, Sweden, 22-26 August 2016
Non-Patent Document 7: 3GPP R2-165328, “Aggregation of carriers in NR”, 3GPP TSG-RAN WG2 Meeting # 95, Gothenburg, Sweden, 22-26 August 2016
Outline of the invention
Problems to be solved by the invention
[0016]
　The inventors of the present invention examined the interworking between E-UTRA and NR and found some problems. For example, in a DC architecture (ie, architecture options 3 and 3A) where E-UTRA and NR are connected to an EPC, the Secondary gNB (SgNB) as a secondary node supports multiple numeros. 5G UE can also use multiple numers in one cell or between multiple cells at the same time (that is, in one RRC connection). However, when SgNB supports multiple numerologies and the UE uses them, it is not clear how to configure the radio resource settings for the numerology of the SCG cell (SCG carrier) in the UE.
[0017]
　This issue with Numerology can also occur with other E-UTRA-NR DC architectures (eg, architecture options 7 and 7A). Architecture options 7 and 7A are Dual connectivity (DC) deployments that include E-UTRA as the anchor RAT (or primary or master RAT) and NR as the secondary RAT. In options 7 and 7A, E-UTRA (LTE eNB) and NR (gNB) are connected to 5G-CN. The NR user plane connection to 5G-CN goes through LTE eNB in ​​option 7, but goes directly through the user plane interface between gNB and 5G-CN in option 7A. Also in the case of options 7 and 7A, it is not clear how to configure the radio resource settings for the numerology of the SCG cell (SCG carrier) in the UE when SgNB supports multiple numerologies and the UE uses them.
[0018]
　In addition, similar problems with Numerology can occur with Inter-RAT handovers from E-UTRA to NR. That is, it is not clear how to configure the radio resource settings for the numerology of the target NR cell in the UE when the UE is handed over from the source LTE eNB to the target gNB that supports multiple numeros.
[0019]
　Therefore, one of the objectives to be achieved by the embodiments disclosed herein is the secondary gNB in ​​the Inter-RAT dual connectivity between E-UTRA and NR and the Inter-RAT handover from E-UTRA to NR. Alternatively, it is to provide a device, method, and program that allows the numerology of the cell provided by the target gNB to be set in the UE. It should be noted that this object is only one of the purposes that the plurality of embodiments disclosed herein seek to achieve. Other objectives or issues and novel features will be apparent from the description or accompanying drawings herein.
Means to solve problems
[0020]
　In the first aspect, the second radio access network (RAN) node is used in a radio communication system. The wireless communication system supports a first RAT and a second RAT. The second RAN node includes a memory and at least one processor coupled to the memory. The at least one processor is configured to send the radio resource settings of the second RAT to the radio terminal via the first RAN node associated with the first RAT. The radio resource setting explicitly or implicitly indicates at least one of the plurality of numerologies supported by the second RAT that is different from the reference numerology.
[0021]
　In the second aspect, the first radio access network (RAN) node is used in a radio communication system. The wireless communication system supports a first RAT and a second RAT. The first RAN node includes a memory and at least one processor coupled to the memory. The at least one processor is configured to receive the radio resource settings of the second RAT from the second RAN node associated with the second RAT and send the radio resource settings to the radio terminal. The radio resource setting explicitly or implicitly indicates at least one of the plurality of numerologies supported by the second RAT that is different from the reference numerology.
[0022]
　In a third aspect, the wireless terminal is used in a wireless communication system. The wireless communication system supports a first RAT and a second RAT. The wireless terminal includes at least one wireless transceiver and at least one processor. The at least one radio transceiver is configured to communicate with a first radio access network (RAN) node associated with the first RAT and a second RAN node associated with the second RAT. .. The at least one processor is configured to receive the radio resource settings of the second RAT from the second RAN node via the first RAN node. The radio resource setting explicitly or implicitly indicates at least one of the plurality of numerologies supported by the second RAT that is different from the reference numerology.
[0023]
　In a fourth aspect, the method at the second radio access network (RAN) node transfers the radio resource settings of the second RAT to the radio terminal via the first RAN node associated with the first RAT. Including sending. The radio resource setting explicitly or implicitly indicates at least one of the plurality of numerologies supported by the second RAT that is different from the reference numerology.
[0024]
　In a fifth aspect, the method at the first radio access network (RAN) node receives the radio resource settings of the second RAT from the second RAN node associated with the second RAT and the radio resource. Includes sending settings to wireless terminals. The radio resource setting explicitly or implicitly indicates at least one of the plurality of numerologies supported by the second RAT that is different from the reference numerology.
[0025]
　In a sixth aspect, the method in the radio terminal is to set the radio resource settings of the second RAT via the first radio access network (RAN) node associated with the first RAT. Includes receiving from a second RAN node associated with the RAT. The radio resource setting explicitly or implicitly indicates at least one of the plurality of numerologies supported by the second RAT that is different from the reference numerology.
[0026]
　In a seventh aspect, the program includes instructions (software code) for causing the computer to perform the method according to the fourth, fifth, or sixth aspect described above when loaded into the computer.
The invention's effect
[0027]
　According to the above aspect, the numerology of the cell provided by the secondary gNB or the target gNB in ​​the Inter-RAT dual connectivity between E-UTRA and NR and the Inter-RAT handover from E-UTRA to NR is set to UE. Equipment, methods, and programs that enable this can be provided.
A brief description of the drawing
[0028]
[Fig. 1] Fig. 1 is a diagram showing the basic architecture of the 5G System related to the background technology.
FIG. 2 is a diagram showing architecture option 3 for dual connectivity in which E-UTRA (LTE eNB) and NR (gNB) are connected to EPC according to the background technology.
FIG. 3 illustrates an architectural option 3A for dual connectivity in which E-UTRA (LTE eNB) and NR (gNB) are connected to an EPC, according to background technology.
FIG. 4 is a diagram showing a configuration example of a wireless communication network according to some embodiments.
FIG. 5 is a sequence diagram showing an example of an SCG establishment procedure according to the first embodiment.
FIG. 6 is a sequence diagram showing an example of signaling between MeNB and SgNB according to the second embodiment.
FIG. 7 is a flowchart showing an example of the operation of LTE eNB (MeNB) according to the second embodiment.
FIG. 8 is a flowchart showing an example of the operation of NR gNB (SgNB) according to the third embodiment.
FIG. 9 is a diagram showing a configuration example of a wireless communication network according to a fourth embodiment.
FIG. 10 is a sequence diagram showing an example of an Inter-RAT handover procedure according to a fourth embodiment.
FIG. 11 is a block diagram showing a configuration example of NR gNB according to some embodiments.
FIG. 12 is a block diagram showing a configuration example of a UE according to some embodiments.
Forms for carrying out the invention
[0029]
　Hereinafter, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are designated by the same reference numerals, and duplicate explanations are omitted as necessary for the sake of clarity of explanation.
[0030]
　The plurality of embodiments described below may be implemented independently or in combination as appropriate. These plurality of embodiments have novel features that differ from each other. Therefore, these plurality of embodiments contribute to solving different purposes or problems, and contribute to different effects.
[0031]
　The plurality of embodiments shown below are described mainly for DC architectures in which E-UTRA and NR are connected to EPC. However, these embodiments may be applied to other wireless communication systems that support a DC architecture in which different RATs that employ different QoS frameworks are connected to a common core network.
[0032]

　FIG. 4 shows a configuration example of a wireless communication network according to some embodiments including the present embodiment. In the example of FIG. 4, the wireless communication network includes LTE eNB1, NR gNB2, UE3, and EPC4. The wireless communication network shown in FIG. 4 supports dual connectivity (DC) and supports option 3 and / or option 3A described above. Options 3 and 3A support dual connectivity, including E-UTRA as an anchor RAT (or primary RAT) and NR as a secondary RAT. In options 3 and 3A, E-UTRA (LTE eNB1) and NR (gNB2) are connected to EPC4. The NR user plane connection to the EPC4 goes through the LTE eNB1 in option 3, and the user packet of the UE3 goes through the inter-base station interface 403 and the interface 401 between the eNB1 and the EPC4. On the other hand, in option 3A, the NR userplane connection to EPC4 goes directly through the userplane interface 404 between gNB2 and EPC4.
[0033]
　UE3 has the ability to communicate simultaneously with eNB1 associated with the primary RAT (E-UTRA) and gNB2 associated with the secondary RAT (NR). In other words, UE3 has the ability to aggregate the cell of eNB1 associated with the primary RAT (E-UTRA) and the cell of gNB2 associated with the secondary RAT (NR). In other words, UE3 has the ability to configure both the cell of eNB1 associated with the primary RAT (E-UTRA) and the cell of gNB2 associated with the secondary RAT (NR). In architecture options 3 and 3A, the air interface 402 between eNB1 and UE3 provides a control plane connection and a user plane connection. On the other hand, the air interface 405 between gNB2 and UE3 includes at least a user plane connection, but may not include a control plane connection. In a DC architecture where E-UTRA and NR are connected to EPC4, master eNB (MeNB) 1 provides one or more E-UTRA MCG cells to UE3, and secondary gNB (SgNB) 2 is one or more. Provide the NR SCG cell to UE3.
[0034]
　EPC4 includes a plurality of core network nodes including MME5 and S-GW6. MME5 is a control plane node and S-GW6 is a user plane node. MME5 manages mobility and bearer of UEs that have been attached to the core network (ie, EMM-REGISTERED state). Mobility management is used to keep track of the UE's current position and involves maintaining a mobility management context (MM context) for the UE. Bearer management controls the establishment of EPS bearers for UEs to communicate with external networks (Packet Data Network (PDN)) via E-UTRAN and EPC4 including eNB1 and maintains EPS bearer context for UEs. including. The S-GW6 is a gateway with the E-UTRAN and is connected to the eNB1 and / or gNB2 via the S1-U interface.
[0035]
　gNB2 supports multiple numeros in one or more NR carriers (cells). That is, one or more numeros are associated with one NR cell. Numerology includes subcarrier spacing, system bandwidth, Transmission Time Interval (TTI) length, subframe duration, slot duration, At least one of the number of slots per subframe, the Cyclic prefix length, the symbol duration, and the number of symbols per subframe. Including one. If the system bandwidth corresponds to the bandwidth supported by the aggregation of multiple carriers (ie Carrier Aggregation (CA)) from the UE viewpoints, numerology is the bandwidth and system of the multiple carriers to be aggregated. Further information regarding bandwidth correspondence may be included. The plurality of numerologies includes at least one reference numerology and at least one dedicated or additional numerology that is not a reference numerology. The reference numerology defines the reference subframe configuration (eg, reference subframe length, number of reference OFDM symbols in the subframe, or reference TTI length) for the NR carriers supported by gNB2. Reference numerology information is system information (eg,
[0036]
　Subsequently, the procedure for setting the numerology of the SCG cell provided by the secondary gNB (SgNB) 2 to UE3 in the DC architecture in which E-UTRA and NR are connected to EPC4 will be described below. The gNB 2 according to the present embodiment is configured to send the NR radio resource setting for E-UTRA-NR Dual Connectivity (DC) to the UE 3 via the master eNB (MeNB) 1. The NR radio resource setting explicitly or implicitly indicates at least one individual numerology different from the reference numerology among the multiple numerologies supported by one or more NR cells included in the SCG of SgNB2. That is, the NR radio resource configuration contains at least information about individual numerology. The information about the individual numerology may include an information element that explicitly indicates the individual numerology, or may include an information element that indicates the radio parameters necessary for deriving the individual numerology. Individual numberology can be, for example, subcarrier spacing, system bandwidth, TTI length, subframe length, slot length, number of slots in subframe, cyclic prefix length, symbol duration, or number of symbols in subframe. Alternatively, it may be any combination thereof. The NR radio resource configuration can also be referred to as SCG radio configuration or SCG-Config. MeNB1 is configured to receive NR radio resource settings from SgNB2 and send them to UE3. UE3 is configured to receive NR radio resource settings for E-UTRA-NR DC from SgNB2 via MeNB1.
[0037]
　In some implementations, SgNB2 receives a radio bearer configuration request from MeNB1 and at least one corresponding to the requirement for NR data radio bearer (DRB) for UE3 indicated by the radio bearer configuration request. Individual numerology may be selected. The radio bearer configuration request is a message that causes gNB2 to configure the NR DRB for the E-UTRA-NR DC. The wireless bearer setting request may be referred to as an SgNB Addition Request. Requirements for NR DRBs may include QoS requirements and / or service types. The QoS requirement includes at least one of the priority, Maximum Bit Rate (MBR), and Allocation and Retention Priority (ARP) required for the NR DRB or its associated network bearer or flow. Service types include, for example, enhanced Mobile Broad Band (eMBB), Ultra Reliable and Low Latency Communication (URLLC), and multi-connection M2M communication (massive Machine Type Communication: mMTC). One is shown.
[0038]
　SgNB2 may include an information element indicating at least one selected individual numerology in the NR radio resource setting. In this case, SgNB2 sends an NR radio resource setting that explicitly or implicitly indicates at least one selected numerology to MeNB1 using a response message (eg, SgNB Addition Request Acknowledge message) to the radio bearer setting request. May be good. MeNB1 may transmit the NR radio resource setting received from SgNB2 to UE3 by using the RRC Connection Reconfiguration message.
[0039]
　FIG. 5 is a sequence diagram showing an example (process 500) of the SCG establishment procedure according to the present embodiment. The procedure shown in FIG. 5 basically follows the LTE DC SeNB Addition procedure. In step 501, MeNB1 sends an SgNB Addition Request message to SgNB2. The SgNB Addition Request message requests SgNB2 to configure a radio bearer (SCG DRB) for DCs that use E-UTRA and NR as the primary and secondary RATs, respectively.
[0040]
　The SgNB Addition Request message corresponds to the above-mentioned "wireless bearer setting request". Specifically, the SgNB Addition Request message is the "SgNB Security Key (for SCG bearer)" information element (IE), "E-RAB To Be Added List" IE, and "MeNB to SgNB Container" IE. including. The “E-RAB To Be Added List” IE contains the E-RAB ID and E-RAB Level QoS Parameters for each E-RAB required to be established by MeNB1. “MeNB to SgNB Container” IE contains RRC: SCG-ConfigInfo message. RRC: The SCG-ConfigInfo message is used by MeNB to request SgNB to establish, modify, or release an SCG. The SCG-ConfigInfo message includes, for example, EPS bearer Identity, DRB Identity, and DRB type. The security policy (eg, wireless link, AS layer) used in the secondary RAT (NR) cell (eg, wireless link, Access Stratum (AS) layer) and the primary RAT (E-UTRA) cell (eg, wireless link, AS layer). The security algorithm) may be different. In this case, the SgNB Security Key IE may include security policy information used in the secondary RAT (NR) cell. In addition, SgNB2 may include the security policy information in the RRC: SCG-Config message sent to UE3.
[0041]
　In step 502, SgNB2 sends an SgNB Addition Request Acknowledge message to MeNB1. The SgNB Addition Request Acknowledge message is a response message to the SgNB Addition Request message. The SgNB Addition Request Acknowledge message contains the radio resource settings for the SCG DRB generated by SgNB2. The SCG DRB radio resource setting is sent to UE3 via MeNB1. The SCG DRB radio resource setting indicates at least one individual numerology selected by SgNB2.
[0042]
　Specifically, the SgNB Addition Request Acknowledge message includes "E-RAB Admitted To Be Added List" IE and "SgNB to MeNB Container" IE. “SgNB to MeNB Container” IE contains RRC: SCG-Config message. RRC: The SCG-Config message is used to transfer the radio resource settings generated by SgNB2. RRC: The SCG-Config message indicates at least one individual numerology selected by SgNB2.
[0043]
　In step 503, MeNB1 sends an RRC Connection Reconfiguration message to UE3 in response to receiving the SgNB Addition Request Acknowledge message from SgNB2. The RRC Connection Reconfiguration message includes an RRC: SCG-Config message sent from SgNB2 to MeNB1 using the SgNB Addition Request Acknowledge message. The AS layer of the UE3 primary RAT (ie, E-UTRA (LTE)) receives the RRC Connection Reconfiguration message in the MeNB1 E-UTRA cell (ie, Primary Cell (PCell)). The AS layer of the secondary RAT (ie, NR) of UE3 sets the SCG DRB according to at least one individual numerology selected by SgNB2 based on the RRC: SCG-Config message.
[0044]
　In step 504, UE3 (AS layer of ie, E-UTRA) sends an RRC Connection Reconfiguration Complete message to MeNB1 in the E-UTRA cell (ie, PCell) of MeNB1. In addition, UE3 (AS layer of ie, NR) starts a procedure (eg, Random Access Procedure) for synchronizing with SgNB2.
[0045]
　In step 505, MeNB1 sends an SgNB Reconfiguration Complete message to SgNB2 in response to receiving the RRC Connection Reconfiguration Complete message from UE3.
[0046]
　As can be understood from the above description, the SgNB 2 according to the present embodiment is configured to send the NR radio resource setting for the E-UTRA-NR DC to the UE 3 via the master eNB (MeNB) 1, and the NR radio. The resource setting indicates at least one individual numerology different from the reference numerology among the plurality of numerologies supported by one or more NR cells of SgNB2. This allows SgNB2 to set the numerology of the SCG cell provided by SgNB2 to UE3 in the E-UTRA-NR DC. UE3 can know the numerology to be used in the SCG cell provided by SgNB2.
[0047]

　The configuration example of the wireless communication network according to the present embodiment is the same as in FIG. The present embodiment provides an improvement for making the UE measurement report available to MeNB1 showing the measurement result of the NR cell of SgNB2 based on the reference numerology in the E-UTRA-NR DC.
[0048]
　SgNB2 according to the present embodiment is configured to notify MeNB1 of at least one reference numerology in the procedure for setting up the inter-base station interface (eg, Xn interface or X3 interface) between SgNB2 and MeNB1. As described above, the reference numerology defines the reference subframe length for the NR carriers supported by gNB2.
[0049]
　FIG. 6 is a sequence diagram showing an example (process 600) of signaling between MeNB1 and SgNB2. In step 601 the SgNB 2 uses an Xn Setup Request message or an Xn Setup Response message to notify MeNB 1 of a plurality of numbers supported by one or more NR carriers used by the SgNB 2. The plurality of numerologies supported by SgNB2 includes at least one reference numerology.
[0050]
　In some implementations, MeNB1 may use the reference numerology of SgNB2 for UE measurement. FIG. 7 is a flowchart showing an example (process 700) of the operation of MeNB1. In step 701, MeNB1 generates a measurement configuration indicating the reference numerology of the NR cell provided by SgNB2. In step 702, MeNB1 sends the generated measurement settings to UE3. The measurement setting requires UE3 to measure the NR cell of SgNB2 based on the reference numerology specified by the measurement setting. As a result, MeNB1 can use a UE measurement report showing the measurement result of the NR cell of SgNB2 based on the reference numerology. MeNB1 may utilize the measurement result of the NR cell of SgNB2 based on the reference numerology to determine the start, stop, or modification of the E-UTRA-NR DC.
[0051]

　The configuration example of the wireless communication network according to the present embodiment is the same as in FIG. The present embodiment provides an improvement in the E-UTRA-NR DC to allow SgNB2 to specify UE3 for measurement of the NR cell of SgNB2 based on reference numerology.
[0052]
　SgNB2 according to the present embodiment is configured to send measurement settings according to the reference numerology in the carrier of SgNB2 to UE3 via MeNB1. FIG. 8 is a flowchart showing an example (process 800) of the operation of SgNB2. In step 801 SgNB2 generates a measurement configuration indicating the reference numerology of the NR cell provided by SgNB2. In step 802, SgNB2 sends the generated measurement settings to UE3 via MeNB1. Specifically, MeNB1 may receive the measurement setting from SgNB2 and transmit it to UE3. The measurement setting requires UE3 to measure the NR cell of SgNB2 based on the reference numerology specified by the measurement setting. As a result, MeNB1 can use a UE measurement report showing the measurement result of the NR cell of SgNB2 based on the reference numerology. MeNB1 may utilize the measurement result of the NR cell of SgNB2 based on the reference numerology to determine the start, stop, or modification of the E-UTRA-NR DC.
[0053]

　This embodiment is performed by a secondary gNB or a target gNB in ​​another E-UTRA-NR DC architecture (eg, architecture options 7 and 7A) and an Inter-RAT handover from E-UTRA to NR. Improvements are provided to allow the numerology of the provided cells to be set to UE.
[0054]
　FIG. 9 shows a configuration example of the wireless communication network according to the present embodiment. In one example, the wireless communication network according to this embodiment may provide E-UTRA-NR DC architecture option 7 or 7A. In options 7 and 7A, E-UTRA (LTE eNB1) and NR (gNB2) are connected to 5G-CN7. The NR user plane connection to 5G-CN7 goes through LTE eNB1 in option 7, and the user packet of UE3 goes through the inter-base station interface 403 and the interface 902 between eNB1 and 5G-CN7. On the other hand, in option 7A, the NR user plane connection to 5G-CN7 goes directly through the user plane interface 902 between gNB2 and 5G-CN7.
[0055]
　The procedure for setting the numerology of the SCG cell provided by the secondary gNB (SgNB) 2 to UE3 in the DC architecture in which E-UTRA and NR are connected to 5G-CN7 will be described below. The gNB2 according to the present embodiment may operate in the same manner as the gNB2 according to the first embodiment. That is, in this embodiment, gNB2 is configured to send NR radio resource settings for E-UTRA-NR Dual Connectivity (DC) to UE3 via master eNB (MeNB) 1. The NR radio resource setting indicates at least one individual numerology different from the reference numerology among the plurality of numerologies supported by one or more NR cells included in the SCG of SgNB2.
[0056]
　The operation of MeNB1, SgNB2, and UE3 may be similar to that in the SCG establishment procedure (process 500) described with reference to FIG. That is, SgNB2 may send an SgNB Addition Request Acknowledge message to MeNB1 that includes an RRC: SCG-Config message indicating at least one individual numerology selected by SgNB2 (step 502). MeNB1 may send an RRC Connection Reconfiguration message to UE3 containing an RRC: SCG-Config message indicating at least one individual numerology selected by SgNB2 (step 503). The AS layer of the secondary RAT (ie, NR) of UE3 may configure the SCG DRB according to at least one individual numerology selected by SgNB2 based on the RRC: SCG-Config message (step 504).
[0057]
　Further or instead, the wireless communication network according to the present embodiment may support an Inter-RAT handover from the E-UTRA cell 11 of the LTE eNB 1 to the NR cell 21 of the NR gNB 2. The procedure for setting the numerology of the cell 21 provided by the target NR gNB2 to the UE 3 when the UE 3 is handed over from the source E-UTRA cell 11 to the target NR cell 21 will be described below.
[0058]
　FIG. 10 is a sequence diagram showing an example (process 1000) of the Inter-RAT handover procedure according to the present embodiment. In step 1001, the source LTE eNB1 sends an NR Handover Request message to the target gNB2 on the direct interbase station interface 403 (eg, Xn interface or X3 interface). The NR Handover Request message of step 1001 may include a Handover Type Information Element (IE) indicating that the handover is from LTE to NR. For Handover Type IE, for example, "LTEtoNR" is set.
[0059]
　In step 1002, the target gNB2 creates a UE context and allocates resources based on the NR Handover Request message. Then, the target gNB2 sends an NR Handover Request Acknowledge message to the source eNB1. The NR Handover Request Acknowledge message is a response message to the NR Handover Request message. The NR Handover Request Acknowledge message includes the radio resource configuration of the DRB of the target NR cell 21 generated by the target gNB2. The radio resource setting is sent to UE3 via the source eNB1. The radio resource setting indicates at least one individual numerology selected by the target gNB2.
[0060]
　Specifically, the NR Handover Request Acknowledge message includes the “Target to Source Transparent Container” IE. The “Target to Source Transparent Container” IE contains the radio resource configuration information set up by the target gNB2. The radio resource configuration information indicates at least one individual numerology provided in the target NR cell 21.
[0061]
　In step 1003, the source eNB1 sends an RRC message to the UE3 that includes a Handover Command message containing the radio resource configuration information generated by the target gNB2. The RRC message may be, for example, a Mobility from EUTRA command message or an RRC Connection Reconfiguration message. The source eNB1 may include the radio resource setting information generated by the target gNB2 in the “MobilityControlInfoNR” IE in the RRC Connection Reconfiguration message.
[0062]
　In step 1004, the UE 3 moves to the cell of the target RAN (ie, NR) in response to the reception of the RRC message including the Handover Command message, and performs the handover according to the radio resource setting information supplied in the Handover Command message. do. That is, UE3 establishes a wireless connection with target gNB2 according to at least one individual numerology selected by SgNB2. Here, information on which numerology to use for performing the handover (or what numerology should be assumed in carrying out the handover) may be transmitted in a Handover Command message or an RRC message including the same. .. UE3 performs handover according to the information (eg, establishes a wireless connection).
[0063]
　In step 1005, UE3 successfully synchronizes with target NR cell 21 and then sends a Handover Confirm for NR message to target gNB2. The message in step 1005 may be a (NR) RRC Connection Reconfiguration Complete message.
[0064]
　As can be understood from the above description, in one example, gNB2 according to the present embodiment sets the NR radio resource for E-UTRA-NR DC (ie ,, option 7 or 7A) to UE3 via MeNB1. Configured to send, the NR radio resource configuration indicates at least one individual numerology that differs from the reference numerology of the multiple numerologies supported by one or more NR cells in SgNB2. This allows SgNB2 to set the numerology of the SCG cell provided by SgNB2 to UE3 in E-UTRA-NR DC (ie ,, option 7 or 7A). UE3 can know the numerology to be used in the SCG cell provided by SgNB2.
[0065]
　In another example, gNB2 according to the present embodiment is configured to send the NR radio resource setting for Inter-RAT handover from E-UTRA to NR to UE3 via the source eNB1, and the NR radio resource setting is Indicates at least one individual numerology different from the reference numerology among the plurality of numerologies supported by one or more NR cells of the target gNB2. As a result, the target gNB2 can set the numerology of the target NR cell to UE3 in the Inter-RAT handover from E-UTRA to NR. UE3 can know the numerology to be used in at least one NR cell 21 provided by the target gNB2.
[0066]
　Subsequently, the configuration examples of LTE eNB1, NR gNB2, and UE3 according to the above-described plurality of embodiments will be described below. FIG. 11 is a block diagram showing a configuration example of the NR gNB 2 according to the above embodiment. The configuration of LTE eNB1 may be similar to that shown in FIG. Referring to FIG. 11, gNB2 includes Radio Frequency transceiver 1101, network interface 1103, processor 1104, and memory 1105. RF transceiver 1101 performs analog RF signal processing to communicate with NG UEs including UE3. RF transceiver 1101 may include a plurality of transceivers. The RF transceiver 1101 is coupled with the antenna array 1102 and the processor 1104. The RF transceiver 1101 receives modulation symbol data from the processor 1104, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 1102. Further, the RF transceiver 1101 generates a baseband reception signal based on the reception RF signal received by the antenna array 1102, and supplies the baseband reception signal to the processor 1104. The RF transceiver 1101 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.
[0067]
　The network interface 1103 is used to communicate with network nodes (eg, LTE eNB1, MME5, S-GW6). The network interface 1103 may include, for example, an IEEE 802.3 series compliant network interface card (NIC).
[0068]
　Processor 1104 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Processor 1104 may include a plurality of processors. For example, the processor 1104 is a modem processor (eg, Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (eg, Central Processing Unit (CPU) or Micro Processing Unit (eg, Central Processing Unit (CPU)) that performs control plane processing. MPU)) may be included. Processor 1104 may include a digital beamformer module for beamforming. The digital beamformer module may include a Multiple Input Multiple Output (MIMO) encoder and precoder.
[0069]
　The memory 1105 is composed of a combination of a volatile memory and a non-volatile memory. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. Non-volatile memory can be masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. Memory 1105 may include storage located away from processor 1104. In this case, processor 1104 may access memory 1105 via network interface 1103 or an I / O interface (not shown).
[0070]
　The memory 1105 may store one or more software modules (computer programs) 1106 that include instructions and data for performing processing by gNB2 described in the plurality of embodiments described above. In some implementations, processor 1104 may be configured to read the software module 1106 from memory 1105 and execute it to perform the processing of gNB2 described in the embodiments described above.
[0071]
　FIG. 12 is a block diagram showing a configuration example of UE3. Radio Frequency (RF) transceiver 1201 performs analog RF signal processing to communicate with eNB1 and gNB2. RF transceiver 1201 may include a plurality of transceivers. The analog RF signal processing performed by the RF transceiver 1201 includes frequency up-conversion, frequency down-conversion, and amplification. The RF transceiver 1201 is coupled with the antenna array 1202 and the baseband processor 1203. The RF transceiver 1201 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1203, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 1202. Further, the RF transceiver 1201 generates a baseband reception signal based on the reception RF signal received by the antenna array 1202, and supplies the baseband reception signal to the baseband processor 1203. The RF transceiver 1201 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.
[0072]
　The baseband processor 1203 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression / restoration, (b) data segmentation / concatenation, (c) transmission format (transmission frame) generation / decomposition, and (d) transmission path coding / decoding. , (E) Modulation (symbol mapping) / demodulation, and (f) Generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). Control plane processing, on the other hand, includes layer 1 (eg, transmit power control), layer 2 (eg, radio resource management, and hybrid automatic repeat request (HARQ) processing), and layer 3 (eg, attach, mobility, and call management). Includes communication management of).
[0073]
　For example, digital baseband signal processing by the baseband processor 1203 may include signal processing at the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, MAC layer, and PHY layer. In addition, the control plane processing by the baseband processor 1203 may include the processing of the Non-Access Stratum (NAS) protocol, the RRC protocol, and the MAC CE.
[0074]
　Baseband processor 1203 may perform MIMO encoding and precoding for beamforming.
[0075]
　Baseband processor 1203 may include a modem processor (eg, DSP) for digital baseband signal processing and a protocol stack processor (eg, CPU or MPU) for control plane processing. In this case, the protocol stack processor that performs the control plane processing may be shared with the application processor 1204 described later.
[0076]
　Application processor 1204 is also referred to as CPU, MPU, microprocessor, or processor core. The application processor 1204 may include a plurality of processors (a plurality of processor cores). The application processor 1204 includes a system software program (Operating System (OS)) read from memory 1206 or a memory (not shown) and various application programs (eg, call applications, web browsers, mailers, camera operating applications, music playback). By executing the application), various functions of UE3 are realized.
[0077]
　In some implementations, the baseband processor 1203 and application processor 1204 may be integrated on one chip, as shown by the broken line (1205) in FIG. In other words, the baseband processor 1203 and application processor 1204 may be implemented as one System on Chip (SoC) device 1205. SoC devices are sometimes referred to as system large scale integration (LSI) or chipsets.
[0078]
　The memory 1206 is a volatile memory, a non-volatile memory, or a combination thereof. The memory 1206 may include a plurality of physically independent memory devices. Volatile memory is, for example, SRAM or DRAM or a combination thereof. Non-volatile memory can be MROM, EEPROM, flash memory, or a hard disk drive, or any combination thereof. For example, memory 1206 may include external memory devices accessible from baseband processor 1203, application processor 1204, and SoC 1205. Memory 1206 may include internal memory devices integrated within baseband processor 1203, application processor 1204, or SoC 1205. Further, memory 1206 may include memory in a Universal Integrated Circuit Card (UICC).
[0079]
　The memory 1206 may store one or more software modules (computer programs) 1207 that include instructions and data for performing processing by UE3 described in the plurality of embodiments described above. In some implementations, the baseband processor 1203 or application processor 1204 is configured to read the software module 1207 from memory 1206 and execute it to perform the UE3 processing described with reference to the drawings in the above embodiments. May be done.
[0080]
　As described with reference to FIGS. 11 and 12, each of the processors included in the LTE eNB1, NR gNB2, and UE3 according to the above-described embodiment is an instruction for causing the computer to perform the algorithm described with reference to the drawings. Run one or more programs containing groups. This program can be stored and supplied to a computer using various types of non-transitory computer readable medium. Non-transient computer-readable media include various types of tangible storage media. Examples of non-temporary computer-readable media include magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD- Includes R, CD-R / W, semiconductor memory (eg, mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM)). The program may also be supplied to the computer by various types of transient computer readable medium. Examples of temporary computer-readable media include electrical, optical, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.
[0081]
The
　above-described embodiment shows an example in which the SgNB Addition procedure following the SeNB Addition procedure is used. In the above-described embodiment, the SgNB Modification procedure that follows the SeNB Modification procedure may be used instead of the SgNB Addition procedure. For example, MeNB1 may send an SgNB Modification Request message to SgNB2 instead of the SgNB Addition Request message (eg, step 501 in FIG. 5).
[0082]
　MeNB1 may perform UE Capability Coordination between MeN1B and SgNB2 before sending a wireless bearer setting request (eg, SgNB Addition Request message or SgNB Modification Request message) to SgNB2. For example, MeNB1 may send a UE Capability Coordination Request message to SgNB2 and receive a UE Capability Coordination Response message from SgNB2. In the Coordination, MeN1B and SgNB2 share only fixed UE capabilities such as RF capability (Band combination, measurement capability) (capacity that is almost unchanged during data transmission / reception at eg, DC, or hard split capability) (negotiation). You may. In addition, MeN1B and SgNB2 also share static UE capabilities (capabilities that do not dynamically change or dynamically share during DC) such as capabilities (eg, soft buffer / soft channel bit) associated with the UE category convention. May be good. Alternatively, MeN1B and SgNB2 may share static UE capability in the exchange step of SeNB Addition Request / Acknowledge messages (or SeNB Modification Request / Acknowledge messages).
[0083]
　Various messages described in the above embodiments (eg, SgNB Addition Request message, SgNB Addition Request Acknowledge message, RRC Connection Reconfiguration message, RRC Connection Reconfiguration Complete message, SgNB Reconfiguration Complete message, Xn Setup Request message, Xn Setup Response message, The information element included in the NR Handover Request message and the NR Handover Request Acknowledge message) is not limited to the above. For example, the information element included in the various messages described above is described above for the purpose of performing DC with LTE eNB1 and NR gNB2, or for the purpose of performing a handover from E-UTRA to NR. Communication / sharing may be performed between different nodes in a direction different from that of the embodiment. As a more specific example, at least a part of the information elements included in the SgNB Addition Request message may be included in the SgNB Addition Request Acknowledge message. Further or instead, at least some of the information elements contained in the SgNB Addition Request message are included in the S1AP message (eg, S1AP: E-RAB Setup Request message) sent from EPC4 (MME5) to LTE eNB1. May be good. As a result, the information required for performing DC with LTE eNB1 and NR gNB2 can be shared between the nodes related to DC performed with LTE eNB1 and NR gNB2.
[0084]
　The operation or processing of the UE2, base station (LTE eNB1, NR gNB2), and core network (EPC4, 5G-CN7) described in the above-described embodiment is in the case of Intra-NR Dual Connectivity and Inter-gNB Handover. Is also applicable. For example, numerology settings may not be the same between adjacent cells in the same NR system. Therefore, when executing Dual Connectivity or Handover, what kind of numerology is used in the secondary cell or the target cell may be set for each UE. Specifically, the secondary gNB or target gNB is an NR radio that explicitly or implicitly indicates at least one individual numerology that is different from the reference numerology among the multiple numerologies supported by its own one or more NR cells. Resource settings may be sent to UE3 via the primary gNB or the source gNB.
[0085]
　In the embodiments described above, each numerology may be associated with one or more network slices or network slice instances. For example, the information indicating the individual numerology in the above-described embodiment may be information indicating a predetermined network slice or network slice instance (eg, network slice identity, network slice instance identity). When the UE 2 receives the information indicating the predetermined network slice or network slice instance, the UE 2 may detect the corresponding individual numerology. In addition, the reference Numerology may also be associated with any network slice or network slice instance. At this time, the network slice or network slice instance associated with the reference Numerology may be one that can be set (or can be used) in common with the UE in the cell. In the case of E-UTRA-NR Dual Connectivity in which E-UTRA and NR are connected to EPC, the network slice may be a Dedicated Core network Node (DCN). At this time, the DCN identifier (eg, DCN ID) may be associated with the individual numerology.
[0086]
　The LTE eNB1 and NR gNB2 described in the above embodiments may be implemented based on the Cloud Radio Access Network (C-RAN) concept. C-RAN is sometimes called Centralized RAN. Therefore, the processing and operation performed by each of the eNB1 and gNB2 described in the above embodiments is provided by the Digital Unit (DU) included in the C-RAN architecture or by the combination of the DU and Radio Unit (RU). You may. The DU is called the Baseband Unit (BBU) or Central Unit (CU). The RU is also referred to as the Remote Radio Head (RRH), Remote Radio Equipment (RRE), Distributed Unit (DU), or Transmission and Reception Point (TRP). That is, the processing and operation performed by each of the eNB 1 and gNB 2 described in the above-described embodiment may be provided by any one or more radio stations (or RAN nodes).
[0087]
　Furthermore, the above-described embodiment is merely an example relating to the application of the technical idea obtained by the inventor of the present invention. That is, the technical idea is not limited to the above-described embodiment, and it goes without saying that various changes can be made.
[0088]
　For example, some or all of the above embodiments may also be described, but not limited to:
[0089]
(Appendix 1) A
　second radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT, and the second RAN node is the second RAT. associated,
　the second RAN node,
　a memory,
　and at least one processor coupled to said memory,
　comprising,
　at least one processor is
　a radio resource configuration of the second RAT the first RAT Configured to send to the radio terminal via the first RAN node associated with, the
　radio resource setting will include at least one of the multiple numeros supported by the second RAT that is different from the reference numerology. A
second RAN node , either explicitly or implicitly .
[0090]
(Appendix 2)
　Each number has a subcarrier spacing, a system bandwidth, a transmission time interval length, a subframe duration, and a slot duration. ), Number of slots per subframe, Cyclic prefix length, symbol duration, and number of symbols per subframe. A
second RAN node according to Appendix 1, comprising at least one .
[0091]
(Supplementary Note 3)
　the at least one processor is configured to generate the radio resource configuration of and the second RAT to the first RAT and the primary RAT for dual connectivity to secondary RAT,
Appendix The second RAN node according to 1 or 2.
[0092]
(Appendix 4) The
　at least one processor receives a radio bearer setting request from the first RAN node, and at least one corresponding to the requirement for the radio bearer of the second RAT indicated by the radio bearer setting request.
The second RAN node according to Appendix 3, wherein numerology is selected and information elements that explicitly or implicitly indicate at least one selected numerology are included in the radio resource configuration .
[0093]
(Supplementary Note 5)
　the at least one processor is configured to generate the radio resource configuration for the wireless terminals Inter-RAT handover to the second RAT from the first RAT,
Appendix 1 Or the second RAN node according to 2.
[0094]
(Supplementary
　Note 6)
The second RAN node according to any one of Supplementary note 1 to 5 , wherein the reference numerology defines a reference subframe configuration for a carrier supported by the second RAT .
[0095]
(Appendix 7) The
　at least one processor notifies the first RAN node of the reference numerology in the procedure for setting up the inter-base station interface between the first RAN node and the second RAN node.
The second RAN node according to any one of Appendix 1 to 6 , which is configured .
[0096]
(Supplementary
　Note 8) The second aspect of Appendix 6, wherein the at least one processor is configured to send measurement settings in the carrier according to the reference numerology to the wireless terminal via the first RAN node
. RAN node.
[0097]
(Appendix 9)
　A first radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT, and the first RAN node is the first RAT. associated,
　the first RAN node,
　a memory,
　and at least one processor coupled to said memory,
　comprising,
　the at least one processor,
　wherein the radio resource configuration of the second RAT second RAT The radio resource setting is configured to receive from a second RAN node associated with and send the radio resource setting to the radio terminal, the
　radio resource setting being referred to among the plurality of numeros supported by the second RAT. A
first RAN node that explicitly or implicitly indicates at least one different radiology .
[0098]
(Appendix 10)
　Each number has a subcarrier spacing, a system bandwidth, a transmission time interval length, a subframe duration, and a slot duration. ), Number of slots per subframe, Cyclic prefix length, symbol duration, and number of symbols per subframe.
The first RAN node according to Appendix 9, comprising at least one .
[0099]
(Appendix 11) The
　at least one processor receives the radio resource setting from the second RAN node for dual connectivity with the first RAT as the primary RAT and the second RAT as the secondary RAT.
The first RAN node according to Appendix 9 or 10 , which is configured as such .
[0100]
(Appendix 12) The
　at least one processor receives the radio resource setting from the second RAN node for the Inter-RAT handover of the radio terminal from the first RAT to the second RAT.
The first RAN node according to Appendix 9 or 10 , which is configured .
[0101]
(Supplementary
　Note 13)
The first RAN node according to any one of Supplementary note 9 to 12 , wherein the reference numerology defines a reference subframe configuration for a carrier supported by the second RAT .
[0102]
(Appendix 14) The first RAN node
　according to
Appendix 13, wherein the at least one processor is configured to send measurement settings on the carrier according to the reference numerology to the radio terminal .
[0103]
(Appendix 15) The
　at least one processor receives the reference numerology from the second RAN node in the procedure for setting up the inter-base station interface between the first RAN node and the second RAN node.
The first RAN node according to any one of Appendix 9 to 13 , which is configured .
[0104]
(Appendix 16)
　A wireless terminal used in a wireless communication system, wherein the wireless communication system supports a first RAT and a second RAT, and the
　wireless terminal is
　associated with the first RAT. at least one radio transceiver configured to communicate with a second RAN node associated with a first radio access network (RAN) node and the second RAT,
　and at least one processor,
comprising a
　at least One processor is configured to receive the
　radio resource settings of the second RAT from the second RAN node via the first RAN node, and the radio resource settings are configured to receive the radio resource settings of the second RAT. A
wireless terminal that explicitly or implicitly indicates at least one of the multiple numeologies supported by the reference nume rology that is different from the reference nume rology .
[0105]
(Appendix 17)
　Each number has a subcarrier spacing, a system bandwidth, a transmission time interval length, a subframe duration, and a slot duration. ), Number of slots per subframe, Cyclic prefix length, symbol duration, and number of symbols per subframe.
The wireless terminal according to Appendix 16, including at least one .
[0106]
(Supplementary Note 18)
　the at least one processor is configured to receive the radio resource configuration of and the second RAT to the first RAT and the primary RAT for dual connectivity to secondary RAT,
Appendix The wireless terminal according to 16 or 17.
[0107]
(Supplementary Note 19)
　the at least one processor is configured to receive the radio resource configuration from the first RAT for the wireless terminals Inter-RAT handover to the second RAT,
Appendix 16 Or the wireless terminal according to 17.
[0108]
(Supplementary
　Note 20)
The wireless terminal according to any one of Supplementary note 16 to 19 , wherein the reference numerology defines a reference subframe configuration for a carrier supported by the second RAT .
[0109]
(Appendix 21)
　A method in a second radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT, wherein the second RAN node is the second. Associated with the RAT, the
　method comprises sending the radio resource settings of the second RAT to a radio terminal via a first RAN node associated with the first RAT
　. A method of explicitly or implicitly indicating at least one radiology that is different from the reference radiology among the plurality of radios supported by the second RAT
.
[0110]
(Appendix 22)
　A method in a first radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT, wherein the first RAN node is the first. Associated with the RAT, the
　method comprises receiving the radio resource settings of the second RAT from a second RAN node associated with the second RAT and sending the radio resource settings to a radio terminal.
　A method in which the radio resource configuration explicitly or implicitly indicates at least one of the plurality of numeologies supported by the second RAT that is different from the reference nume rology
.
[0111]
(Appendix 23)
　A method in a wireless terminal used in a radio communication system, wherein the radio communication system supports a first RAT and a second RAT, and the
　method is a radio resource of the second RAT. The
　radio resource comprises receiving the configuration from a second RAN node associated with the second RAT via a first radio access network (RAN) node associated with the first RAT. The setting explicitly or implicitly indicates at least one of the plurality of numeologies supported by the second RAT that is different from the reference nume rology
.
[0112]
(Appendix 24)
　A program for causing a computer to perform a method on a second radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT. The RAN node is associated with the second RAT, and the
　method sends the radio resource settings of the second RAT to the radio terminal via the first RAN node associated with the first RAT. The
　radio resource setting is a
program that explicitly or implicitly indicates at least one of the plurality of numeologies supported by the second RAT that is different from the reference nume rology .
[0113]
(Appendix 25)
　A program for causing a computer to perform a method in a first radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT. The RAN node is associated with the first RAT, and the
　method receives the radio resource settings of the second RAT from the second RAN node associated with the second RAT and sets the radio resource settings.
　A program comprising sending to a radio terminal, wherein the radio resource setting explicitly or implicitly indicates at least one of the plurality of numeologies supported by the second RAT that is different from the reference nume rology
.
[0114]
(Appendix 26)
　A program for causing a computer to perform a method in a wireless terminal used in a wireless communication system, wherein the wireless communication system supports a first RAT and a second RAT
　. The radio resource settings of the second RAT are received from the second RAN node associated with the second RAT via the first radio access network (RAN) node associated with the first RAT. A
　program in which the radio resource configuration explicitly or implicitly indicates at least one of the plurality of numeologies supported by the second RAT that is different from the reference nume rology
.
[0115]
　This application claims priority on the basis of Japanese application Japanese Patent Application No. 2017-000798 filed on January 5, 2017, the entire disclosure of which is incorporated herein by reference.
Code description
[0116]
1 eNodeB (eNB)
2 gNodeB (gNB)
3 User Equipment (UE)
4 Evolved Packet Core (EPC)
5 Mobility Management Entity (MME)
7 5G Core Network (5G-CN)
1101 RF Transceiver
1104 Processor
1105 Memory
1201 RF Transceiver
1203 Baseband processor
1204 application processor
1206 memory
The scope of the claims
[Claim 1]
　A second radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT, wherein the second RAN node is associated with the second RAT and
　said. the second RAN node,
　a memory,
　and at least one processor coupled to said memory,
　comprising,
　at least one processor is
　associated with a radio resource configuration of the second RAT to the first RAT Configured to send to the radio terminal via the first RAN node, the
　radio resource setting explicitly or implies at least one of the plurality of numeologies supported by the second RAT that is different from the reference nume rology. manner shown,
the second RAN node.
[Claim 2]
　Each number is subcarrier spacing, system bandwidth, transmission time interval length, subframe duration, slot duration, subframe. At least one of the number of slots per subframe, the Cyclic prefix length, the symbol duration, and the number of symbols per subframe.
The second RAN node according to claim 1, including the second RAN node.
[Claim 3]
　Wherein the at least one processor is said and said second RAT to the first RAT and the primary RAT for dual connectivity to secondary RAT is configured to generate a radio resource configuration,
according to claim 1 or 2 The second RAN node described in.
[Claim 4]
　The at least one processor receives the radio bearer configuration request from the first RAN node and selects at least one numerology corresponding to the requirement for the radio bearer of the second RAT indicated by the radio bearer configuration request.
The second RAN node according to claim 3, wherein an information element indicating at least one selected numerology, either explicitly or implicitly, is included in the radio resource configuration .
[Claim 5]
　Wherein the at least one processor, said from the first RAT for Inter-RAT handover of the wireless terminal to the second RAT is configured to generate a radio resource configuration,
to claim 1 or 2 The second RAN node described.
[Claim 6]

The second RAN node according to any one of claims 1 to 5 　, wherein the reference numerology defines a reference subframe configuration for a carrier supported by the second RAT .
[Claim 7]
　The at least one processor is configured to notify the first RAN node of the reference numerology in the procedure for setting up the inter-base station interface between the first RAN node and the second RAN node. ,
The second RAN node according to any one of claims 1 to 6.
[Claim 8]

The second RAN node 　according to claim 6, wherein the at least one processor is configured to send measurement settings on the carrier according to the reference numerology to the radio terminal via the first RAN node. ..
[Claim 9]
　A first radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT, wherein the first RAN node is associated with the first RAT and
　said. first RAN node,
　a memory,
　and at least one processor coupled to said memory,
　comprising,
　at least one processor is
　associated with a radio resource configuration of the second RAT to the second RAT The radio resource setting is configured to receive from the second RAN node and send the radio resource setting to the radio terminal, the
　radio resource setting being at least one of the plurality of numeros supported by the second RAT that is different from the reference numerology. A
first RAN node that indicates numerology, either explicitly or implicitly .
[Claim 10]
　Each number is subcarrier spacing, system bandwidth, transmission time interval length, subframe duration, slot duration, subframe. At least one of the number of slots per subframe, the Cyclic prefix length, the symbol duration, and the number of symbols per subframe.
The first RAN node according to claim 9, including the first RAN node.
[Claim 11]
　The at least one processor is configured to receive the radio resource settings from the second RAN node for dual connectivity with the first RAT as the primary RAT and the second RAT as the secondary RAT. are,
first RAN node according to claim 9 or 10.
[Claim 12]
　The at least one processor is configured to receive the radio resource settings from the second RAN node for the Inter-RAT handover of the radio terminal from the first RAT to the second RAT. ,
The first RAN node according to claim 9 or 10.
[Claim 13]

The first RAN node according to any one of claims 9 to 12 　, wherein the reference numerology defines a reference subframe configuration for a carrier supported by the second RAT .
[Claim 14]

The first RAN node 　according to claim 13, wherein the at least one processor is configured to send measurement settings on the carrier according to the reference numerology to the radio terminal .
[Claim 15]
　The at least one processor is configured to receive the reference numerology from the second RAN node in the procedure for setting up the inter-base station interface between the first RAN node and the second RAN node. ,
The first RAN node according to any one of claims 9 to 13.
[Claim 16]
　A radio terminal used in a radio communication system, wherein the radio communication system supports a first RAT and a second RAT, and the
　radio terminal is a
　first radio associated with the first RAT. It comprises at least one radio transceiver configured to communicate with an access network (RAN) node and a second RAN node associated with said second RAT, and
　at least one processor
,
　said said at least one processor. , The radio resource setting of the second RAT is configured to be received from the second RAN node via the first RAN node, and the
　radio resource setting is supported by the second RAT. A
wireless terminal that explicitly or implicitly indicates at least one of a plurality of numeologies that is different from the reference nume rology .
[Claim 17]
　Each number is subcarrier spacing, system bandwidth, transmission time interval length, subframe duration, slot duration, subframe. At least one of the number of slots per subframe, the Cyclic prefix length, the symbol duration, and the number of symbols per subframe.
The wireless terminal according to claim 16, which includes .
[Claim 18]
　Wherein the at least one processor is said and said second RAT to the first RAT and the primary RAT for dual connectivity to secondary RAT is configured to receive a radio resource configuration,
claim 16 or 17 The wireless terminal described in.
[Claim 19]
　Wherein the at least one processor, said from the first RAT for Inter-RAT handover of the wireless terminal to the second RAT is configured to receive a radio resource configuration,
in claim 16 or 17 The wireless terminal described.
[Claim 20]

The wireless terminal according to any one of claims 16 to 19 　, wherein the reference numerology defines a reference subframe configuration for a carrier supported by the second RAT .
[Claim 21]
　A method in a second radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT, wherein the second RAN node is associated with the second RAT. The
　method comprises sending the
　radio resource settings of the second RAT to the radio terminal via the first RAN node associated with the first RAT, the radio resource settings of the second. A method of explicitly or implicitly indicating at least one of the multiple radios supported by the RAT that is different from the reference radio
.
[Claim 22]
　A method in a first radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT, wherein the first RAN node is associated with the first RAT. ,
　the method includes receiving a radio resource configuration of the second RAT from a second RAN node associated with the second RAT, comprising sending the radio resource set in the wireless terminal,
　the radio resource configuration Is a method of explicitly or implicitly indicating at least one of the plurality of numeologies supported by the second RAT that is different from the reference nume rology
.
[Claim 23]
　A method in a radio terminal used in a radio communication system, wherein the radio communication system supports a first RAT and a second RAT, and the
　method sets the radio resource setting of the second RAT. The
　radio resource setting comprises receiving from a second RAN node associated with the second RAT via a first radio access network (RAN) node associated with the first RAT. A method of explicitly or implicitly indicating at least one radiology that is different from the reference radiology among the plurality of radios supported by the second RAT
.
[Claim 24]
　A non-temporary computer-readable medium containing a program that allows a computer to perform a method on a second radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT. The second RAN node is associated with the second RAT, and the
　method sets the radio resource settings of the second RAT via the first RAN node associated with the first RAT. The radio
　resource setting comprises sending to a radio terminal, the radio resource setting is
non-temporary, indicating at least one of the plurality of numeologies supported by the second RAT that is different from the reference nume rology, either explicitly or implicitly. Computer readable medium.
[Claim 25]
　A non-temporary computer-readable medium containing a program that allows a computer to perform a method at a first radio access network (RAN) node used in a radio communication system that supports a first RAT and a second RAT. The first RAN node is associated with the first RAT, and the
　method receives the radio resource settings of the second RAT from the second RAN node associated with the second RAT. The radio resource setting
　explicitly or implicitly indicates at least one of the plurality of numeologies supported by the second RAT that is different from the reference nume rology. Shown,
non-temporary computer-readable medium.
[Claim 26]
　A non-temporary computer-readable medium containing a program for causing a computer to perform a method in a wireless terminal used in a wireless communication system, the wireless communication system supports a first RAT and a second RAT. and,
　the method, the radio resource configuration of the second RAT, through a first radio access network (RAN) node associated with the first RAT, associated with the second RAT comprises receiving from the second RAN node,
　the radio resource configuration, shown explicitly or implicitly a different at least one numerology is the reference numerology of the plurality of numerologies supported by the second RAT,
non Temporary computer readable medium.