I 1111111111111111 1111111111 1111111111 111111111111111 IIIII IIIIII IIII IIII IIII
`US011252643B2
`
`c12) United States Patent
`Futaki et al.
`
`(IO) Patent No.: US 11,252,643 B2
`(45) Date of Patent:
`Feb.15,2022
`
`(54) RADIO ACCESS NETWORK NODE, RADIO
`TERMINAL, AND METHODS AND
`NON-TRANSITORY COMPUTER-READABLE
`MEDIA THEREFOR
`
`(58) Field of Classification Search
`CPC . H04W 48/14; H04W 36/0077; H04W 36/14;
`H04W 88/06; H04W 76/15; H04W 72/04
`See application file for complete search history.
`
`(71) Applicant: NEC CORPORATION, Tokyo (JP)
`
`(72)
`
`Inventors: Hisashi Futaki, Tokyo (JP); Sadafuku
`Hayashi, Tokyo (JP)
`
`(73) Assignee: NEC CORPORATION, Tokyo (JP)
`
`( * ) Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by O days.
`
`(21) Appl. No.:
`
`16/474,337
`
`(22) PCT Filed:
`
`Nov. 21, 2017
`
`(86) PCT No.:
`
`PCT/JP2017/041823
`
`§ 371 (c)(l),
`(2) Date:
`
`Jun. 27, 2019
`
`(87) PCT Pub. No.: WO2018/128019
`
`PCT Pub. Date: Jul. 12, 2018
`
`(65)
`
`Prior Publication Data
`
`US 2019/0342824 Al
`
`Nov. 7, 2019
`
`(30)
`
`Foreign Application Priority Data
`
`Jan. 5, 2017
`
`(JP) ............................. JP2017-000799
`
`(51)
`
`Int. Cl.
`H04W 48114
`H04W36/00
`
`(2009.01)
`(2009.01)
`(Continued)
`
`(52)
`
`U.S. Cl.
`CPC ....... H04W 48114 (2013.01); H04W 36/0077
`(2013.01); H04W 36/14 (2013.01); H04W
`88/06 (2013.01)
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`6,236,860 Bl
`2011/0134774 Al
`
`5/2001 Hagting et al.
`6/2011 Pelletier et al.
`(Continued)
`
`FOREIGN PATENT DOCUMENTS
`
`CN
`CN
`
`11/1998
`1200228 A
`9/2015
`104904254 A
`(Continued)
`
`OTHER PUBLICATIONS
`
`Connnunication dated Nov. 15, 2019 from European Patent Office
`in counterpart EP Application No. 17890048.6.
`(Continued)
`
`Primary Examiner - Asghar H Bilgrami
`(74) Attorney, Agent, or Firm - Sughrue Mion, PLLC
`
`(57)
`
`ABSTRACT
`
`A second RAN node (2) sends to a radio terminal (3), via a
`first RAN node (1), an indication of available on-demand
`system information that is available in a cell of the second
`RAN node (2). It is thus, for example, possible to enabling
`notifying a UE of an indication about on-demand system
`information available in a cell served by a secondary gNB of
`Inter-RAT dual connectivity between E-UTRA and NR, or
`available in a cell served by a target gNB of Inter-RAT
`handover from E-UTRA to NR.
`
`10 Claims, 11 Drawing Sheets
`
`D •---------------•
`
`NG2
`•---------------•
`C-PLANE
`
`NG3
`LI-PLANE
`
`..
`
`NR gNB
`
`..
`
`SRB (s)
`C-PLANE
`ORB (s)
`LI-PLANE
`
`LIE
`
`Ex.1011
`APPLE INC. / Page 1 of 25
`
`

`

`US 11,252,643 B2
`Page 2
`
`(51)
`
`Int. Cl.
`H04W36/14
`H04W 88/06
`H04W 76115
`H04W72/04
`
`(2009.01)
`(2009.01)
`(2018.01)
`(2009.01)
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`11/2015 Lee et al.
`2015/0327094 Al
`12/2015 Zhang et al.
`2015/0351139 Al
`2016/0128006 Al
`5/2016 Ji et al.
`2016/0234736 Al *
`8/2016 Kubota
`8/2016 Kubota et al.
`2016/02347 59 Al
`2017/0331577 Al* 11/2017 Parkvall ................ H04L 5/1469
`2018/0092085 Al *
`H04W36/14
`3/2018 Shaheen
`2018/0192438 Al*
`7/2018 John Wilson .
`H04B 7/088
`2019/0104449 Al*
`4/2019 Oketani
`H04W 36/0085
`2019/0174554 Al*
`6/2019 Deenoo ................. H04L 5/0098
`
`H04W 48/12
`
`FOREIGN PATENT DOCUMENTS
`
`CN
`WO
`WO
`
`105306187 A
`2015/094914 Al
`2016/195617 Al
`
`2/2016
`6/2015
`12/2016
`
`OTHER PUBLICATIONS
`
`"3rd Generation Partnership Project; Technical Specification Group
`Services and System Aspects; Study on Architecture for Next
`Generation System (Release 14)", 3GPP Tr 23.799 Vl4.0.0, Dec.
`2016, 1-522 pgs.
`"3rd Generation Partnership Project; Technical Specification Group
`Radio Access Network; Study on New Radio Access Technology;
`Radio Access Architecture and Interfaces (Release 14)", 3GPP TR
`38.801 vi.0.0, Dec. 2016, pp. 1-72.
`NTT Docomo, Inc., "QoS and bearer for DC between LTE and NR",
`3GPP TSG-RAN2#96, Rl-168400, Nov. 12-18, 2016, pp. 1-3,
`Reno, USA.
`
`Nokia et al., "EPC-NR PDCP interaction for tight interworking:
`User Plane aspects", 3GPPTSG-RANWG2 Meeting#96, Rl-168686,
`Nov. 14-18, 2016, 7 pgs., Reno, USA.
`Catt, "On-demand system information delivery mechanism", 3GPP
`TSG-RANWG2 Meeting #95bis, R2-166120, Oct. 10-14, 2016, pp.
`1-6, Kaohsiung.
`Huawei et al., "Delivery of "Other SI" in NR", 3GPP TSG-RAN2
`Meeting #95bis, Rl-166203, Oct. 10-14, 2016, 5 pgs., Kaohsiung.
`Zte et al., "Consideration on the Minimum SI delivery in NR",
`3GPP TSG-RAN WG2 Meeting #95bis, Rl-166342, Oct. 10-14,
`2016, 3 pgs., Kaohsiung.
`Zte et al., "Consideration on the Other SI delivery in NR", 3GPP
`TSG-RAN WG2 Meeting #95bis, Rl-166343, Oct. 10-14, 2016, 6
`pgs., Kaohsiung.
`NTT Docomo, Inc., "System Information handling for LTE-NR
`Dual Connectivity", 3GPP TSG-RAN WG2#96, Rl-168091-
`Revision ofRl-164950, Nov. 14-18, 2016, pp. 1-2, Reno, USA.
`Samsung, "Comparison of index based approaches", 3GPP TSG(cid:173)
`RAN WG2 Meeting #96, Rl-168086, Nov. 14-18, 2016, 6 pgs.,
`Reno, Nevada.
`Samsung, "Essential System Information (SI) and on-demand SI",
`3GPPTSG RAN WG1#87, RI-1612457, Nov. 14-18, 2016, 3pgs.,
`Reno, USA.
`International Search Report for PCT/JP2017 /041823 dated, Feb. 20,
`2018 (PCT/ISA/210).
`Chinese Office Action for CN Application No. 201780088061.X
`dated Feb. 9, 2021 with English Translation.
`Institute for Information Industry, "Discussion on System Informa(cid:173)
`tion Delivery in NR", 3GPP TSG RAN WGl meeting #86bis,
`Rl-1610207, Lisbon, Portugal, Oct. 10-14, 2016.
`Chinese Office Communication for CN Application No.
`201780088061.X dated Aug. 11, 2021 with English Translation.
`Cloud platform construction of Guizhou Power Grid CSGII system
`under the background of large concentration, China Computer
`&Communication, 2016, Jan. 23, 2016.
`Japanese Office Action for JP Application No. 2020-116195 dated
`Nov. 2, 2021 with English Translation.
`Nokia, Alcatel-Lucent Shanghai Bell, "Distribution of System Infor(cid:173)
`mation in NR", 3GPP TSG-RAN WG2 Meeting #96, Rl-168690,
`Nov. 5, 2016, USA.
`
`* cited by examiner
`
`Ex.1011
`APPLE INC. / Page 2 of 25
`
`

`

`U.S. Patent
`
`Feb.15,2022
`
`Sheet 1 of 11
`
`US 11,252,643 B2
`
`NG2
`•---------------•
`C-PLANE
`
`LIE
`
`NR gNB
`
`NG3
`LI-PLANE
`
`►
`
`Fig. 1
`
`EPC
`
`Sl-LI
`
`Sl-MME +
`
`I
`I
`
`I
`I
`I
`I
`
`LTE eNB
`' '
`LTE Liu
`
`'
`
`gNB
`
`LIE
`
`Fig. 2
`
`Ex.1011
`APPLE INC. / Page 3 of 25
`
`

`

`U.S. Patent
`
`Feb.15,2022
`
`Sheet 2 of 11
`
`US 11,252,643 B2
`
`EPC
`
`S1-U
`
`S1-U
`
`S1-MME +
`
`I
`I
`
`I
`I
`I
`I
`
`LTE eNB
`
`--------
`
`gNB
`
`LTE Uu
`
`UE
`
`Fig. 3
`
`Ex.1011
`APPLE INC. / Page 4 of 25
`
`

`

`U.S. Patent
`
`Feb.15,2022
`
`Sheet 3 of 11
`
`US 11,252,643 B2
`
`4
`
`EPC
`
`5
`
`6
`
`0 G
`
`401
`
`1
`
`403
`
`I
`I
`, __ 404
`
`I
`( ( 0))
`
`2
`
`L TE eNB
`
`(MeNB)
`
`NR gNB
`
`(SgNB)
`
`3
`
`□ UE
`
`Fig. 4
`
`Ex.1011
`APPLE INC. / Page 5 of 25
`
`

`

`U.S. Patent
`
`Feb.15,2022
`
`Sheet 4 of 11
`
`US 11,252,643 B2
`
`4
`
`EPC
`
`7
`
`5G-CN
`
`,,,''\
`- - - - - - - - - -,~'~'- - "
`501
`, '
`E-UTRAN
`
`,><:
`'
`
`404
`.......... L
`' ... ...
`
`I
`
`-
`
`' ...
`
`, , '
`
`',,
`...
`
`'\
`
`5G-RAN
`
`11
`
`LTE eNB
`
`_______________ /
`
`I
`
`403
`
`3
`
`LIE
`
`Fig. 5
`
`\. _____________ _
`
`Ex.1011
`APPLE INC. / Page 6 of 25
`
`

`

`U.S. Patent
`
`Feb. 1s, 2022
`
`Sheet 5 of 11
`
`US 11,252,643 B2
`
`3
`
`UE
`
`600 ~
`
`LTE eNB
`
`2
`
`NR gNB
`
`INDICATION OF
`AVAILABLE "ON-DEMAND SI"
`
`INDICATION OF
`AVAILABLE "ON-DEMAND SI"
`
`601
`
`602
`
`Fig. 6
`
`Ex.1011
`APPLE INC. / Page 7 of 25
`
`

`

`U.S. Patent
`
`Feb.15,2022
`
`Sheet 6 of 11
`
`US 11,252,643 B2
`
`700 ~
`
`LTE eNB
`
`2
`
`NR gNB
`
`Xn SETUP REQUEST
`
`701
`
`Xn SETUP REQUEST RESPONSE
`(INDICATION OF AVAILABLE ON-DEMAND SI)
`
`702
`
`gNB CONFIGURATION UPDATE
`(INDICATION OF AVAILABLE ON-DEMAND SI)
`
`703
`
`Fig. 7
`
`Ex.1011
`APPLE INC. / Page 8 of 25
`
`

`

`U.S. Patent
`
`Feb. 1s, 2022
`
`Sheet 7 of 11
`
`US 11,252,643 B2
`
`3
`
`UE
`
`800 ~
`
`LTE eNB
`
`2
`
`NR gNB
`
`ON-DEMAND SI
`
`801
`
`INFORMATION REQUEST
`ON-DEMAND SI STATUS REQUEST
`
`802
`
`ON-DEMAND SI STATUS RESPONSE
`(INDICATION OF AVAILABLE
`ON-DEMAND SI)
`
`803
`
`RRC CONNECTION RECONFIGURATION
`(INDICATION OF AVAILABLE ON-DEMAND SI)
`
`804
`
`SYSTEM INFORMATION BLOCK TYPE-X
`(INDICATION OF AVAILABLE ON-DEMAND SI
`------\- ---------------------1
`805
`
`IN NEIGHBOUR NR CELL)
`
`Fig. 8
`
`Ex.1011
`APPLE INC. / Page 9 of 25
`
`

`

`U.S. Patent
`
`Feb. 1s, 2022
`
`Sheet 8 of 11
`
`US 11,252,643 B2
`
`900~
`
`3
`
`UE
`
`MeNB
`
`2
`
`SgNB
`
`901
`
`SgNB ADDITION REQUEST
`
`SgNB ADDITION REQUEST
`ACKNOWLEDGE
`
`902
`RRC CONNECTION RECONFIGURATION
`
`INDICATION OF
`AVAILABLE llON-DEMAND Sill
`
`903
`
`I ND I CAT ION OF
`AVAILABLE llON-DEMAND Sill
`
`RRC CONNECTION RECONFIGURATION COMPLETE
`
`904
`
`SI REQUEST
`
`SgNB RECONFIGURATION COMPLETE
`
`905
`
`SI REQUEST
`
`Fig. 9
`
`Ex.1011
`APPLE INC. / Page 10 of 25
`
`

`

`U.S. Patent
`
`Feb. 1s, 2022
`
`Sheet 9 of 11
`
`US 11,252,643 B2
`
`1000--.
`
`3
`
`UE
`
`LTE eNB
`
`2
`
`NR gNB
`
`1001
`
`NR HANDOVER REQUEST
`
`NR HANDOVER REQUEST
`ACKNOWLEDGE
`
`MOBILITY FROM EUTRA
`COMMAND
`
`1002
`
`INDICATION OF
`AVAILABLE "ON-DEMAND SI"
`
`1003
`
`INDICATION OF
`AVAILABLE "ON-DEMAND SI"
`
`1004
`.. - ---------------------------------------------------- j_ -------- --,
`:
`NR ACCESS PROCEDURE
`:
`
`~ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - __ 1
`
`HANDOVER CONFIRM FOR NR
`
`1005
`
`SI REQUEST
`
`Fig. 10
`
`Ex.1011
`APPLE INC. / Page 11 of 25
`
`

`

`U.S. Patent
`
`Feb.15,2022
`
`Sheet 10 of 11
`
`US 11,252,643 B2
`
`,-----c 1102
`
`I
`I
`
`2
`
`1101
`
`RF
`TRANSCEIVER
`
`1103
`
`NETWORK
`INTERFACE
`
`1104
`
`PROCESSOR
`
`1105
`
`MEMORY
`
`~--M_o_ou_LE_s _ _ ~rllOG
`
`Fig. 11
`
`Ex.1011
`APPLE INC. / Page 12 of 25
`
`

`

`U.S. Patent
`
`Feb.15,2022
`
`Sheet 11 of 11
`
`US 11,252,643 B2
`
`,-----c 1202
`
`I
`I
`I
`
`3
`
`1201
`·~ - - - - - - ' - ,
`
`•
`•
`•
`
`RF
`TRANSCEIVER
`
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`
`_____ ! ~ - -~ - -~ 1205
`
`~ -----------------------------_ c_ ---
`
`1203
`
`BASEBAND
`PROCESSOR
`
`APPL! CA Tl ON
`PROCESSOR
`
`MEMORY
`
`1204
`
`1206
`
`.___ __ M_o_ou_L_Es _ _ ___.r l Z0
`
`7
`
`Fig. 12
`
`Ex.1011
`APPLE INC. / Page 13 of 25
`
`

`

`US 11,252,643 B2
`
`1
`RADIO ACCESS NETWORK NODE, RADIO
`TERMINAL, AND METHODS AND
`NON-TRANSITORY COMPUTER-READABLE
`MEDIA THEREFOR
`
`CROSS REFERENCE TO RELATED
`APPLICATIONS
`
`This application is a National Stage of International
`Application No. PCT/JP2017/041823 filed Nov. 21, 2017,
`claiming priority based on Japanese Patent Application No.
`2017-000799, filed Jan. 5, 2017, the disclosures of which are
`incorporated herein in their entirety by reference.
`
`TECHNICAL FIELD
`
`The present disclosure relates to a radio communication
`system and, in particular, to communication in which a radio
`terminal simultaneously uses a plurality of cells of different
`Radio Access Technologies (RATs) operated by different
`radio stations.
`
`BACKGROUND ART
`
`The 3rd Generation Partnership Project (3GPP) has
`started in 2016 the standardization for the fifth generation
`mobile communication system (5G), i.e., 3GPP Release 14,
`to make it a commercial reality in 2020 or later. 5G is
`expected to be realized by continuous enhancement/evolu(cid:173)
`tion ofLTE and LTE-Advanced and an innovative enhance(cid:173)
`ment/evolution by an introduction of a new 5G air interface
`(i.e., a new Radio Access Technology (RAT)). The new RAT
`supports, for example, frequency bands higher than the
`frequency bands (e.g., 6 GHz or lower) supported by LTE/
`LTE-Advanced and its continuous evolution. For example,
`the new RAT supports centimeter-wave bands (10 GHz or
`higher) and millimeter-wave bands (30 GHz or higher).
`In this specification, the fifth generation mobile commu(cid:173)
`nication system is referred to as a 5G System or a Next
`Generation (NextGen) System (NG System). The new RAT
`for the 5G System is referred to as a New Radio (NR), a 5G
`RAT, or a NG RAT. Anew Radio Access Network (RAN) for
`the 5G System is referred to as a 5G-RAN or a NextGen
`RAN (NG RAN). A new base station in the NG-RAN is
`referred to as a NR NodeB (NR NB) or a gNodeB (gNB). A 45
`new core network for the 5G System is referred to as a 5G
`Core Network (5G-CN) or a NextGen Core (NG Core). A
`radio terminal (i.e., User Equipment (UE)) capable of being
`connected to the 5G System is referred to as 5G UE or
`NextGen UE (NG UE), or simply referred to as UE. The 50
`official names of the RAT, UE, radio access network, core
`network, network entities (nodes), protocol layers and the
`like for the NG System will be determined in the future as
`standardization work progresses.
`The term "LTE" used in this specification includes 55
`enhancement/evolution of LTE and LTE-Advanced to pro(cid:173)
`vide interworking with the 5G System, unless otherwise
`specified. The enhancement/evolution of LTE and LTE(cid:173)
`Advanced for the interworking with the 5G System is
`referred to as LTE-Advanced Pro, LTE+, or enhanced LTE 60
`(eLTE). Further, terms related to LTE networks and logical
`entities used in this specification, such as "Evolved Packet
`Core (EPC)", "Mobility Management Entity (MME)",
`"Serving Gateway (S-GW)", and "Packet Data Network
`(PDN) Gateway (P-GW))", include their enhancement/evo- 65
`lution to provide interworking with the 5G System, unless
`otherwise specified. Enhanced EPC, enhanced MME,
`
`5
`
`2
`enhanced S-GW, and enhanced P-GW are referred to, for
`example, as enhanced EPC ( eEPC), enhanced MME
`(eMME), enhanced S-GW (eS-GW), and enhanced P-GW
`( eP-GW), respectively.
`In LTE and LTE-Advanced, for achieving Quality of
`Service (QoS) and packet routing, a bearer per QoS class
`and per PDN connection is used in both a RAN (i.e., an
`Evolved Universal Terrestrial RAN (E-UTRAN)) and a core
`network (i.e., EPC). That is, in the Bearer-based QoS (or
`10 per-bearer QoS) concept, one or more Evolved Packet
`System (EPS) bearers are configured between a UE and a
`P-GW in an EPC, and a plurality of Service Data Flows
`(SDFs) having the same QoS class are transferred through
`15 one EPS bearer satisfying this QoS. An SDF is one or more
`packet flows that match an SDF template (i.e., packet filters)
`based on a Policy and Charging Control (PCC) rule. In order
`to achieve packet routing, each packet to be transferred
`through an EPS bearer contains information for identifying
`20 which bearer (i.e., General Packet Radio Service (GPRS)
`Tunneling Protocol (GTP) tunnel) the packet is associated
`with.
`In contrast, with regard to the 5G System, it is discussed
`that although radio bearers may be used in the 5G-RAN, no
`25 bearers are used in the 5G-CN or in the interface between the
`5G-CN and the NG-RAN (see Non-Patent Literature 1).
`Specifically, PDU flows are defined instead of an EPS
`bearer, and one or more SDFs are mapped to one or more
`PDU flows. A PDU flow between a 5G UE and a user-plane
`30 terminating entity in an NG Core (i.e., an entity correspond(cid:173)
`ing to a P-GW in the EPC) corresponds to an EPS bearer in
`the EPS Bearer-based QoS concept. The PDU flow corre(cid:173)
`sponds to the finest granularity of the packet forwarding and
`treatment in the 5G system. That is, the 5G System adopts
`35 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 per PDU flow. In the QoS frame(cid:173)
`work of the 5G system, a PDU flow is identified by a PDU
`flow ID contained in a header encapsulating a Service Data
`40 Unit of a tunnel of a NG3 interface. The NG3 interface is a
`user plane interface between the 5G-CN and the gNB (i.e.,
`5G-RAN). Association between a 5G UE and a data network
`is referred to as a "PDU session". The term "PDU session"
`corresponds to the term "PDN connection" in LTE and
`LTE-Advanced. A plurality of PDU flows can be configured
`in one PDU session.
`The PDU flow is also referred to as a "QoS flow". The
`QoS flow is the finest granularity in QoS treatment in the 5G
`system. User plane traffic having the same NG3 marking
`value in a PDU session corresponds to a QoS flow. The NG3
`marking corresponds to the above-described PDU flow ID,
`and it is also referred to as a QoS flow ID or a Flow
`Identification Indicator (FII).
`FIG. 1 shows a basic architecture of the 5G system. AUE
`establishes one or more Signalling Radio Bearers (SRBs)
`and one or more Data Radio Bearers (DRBs) with a gNB.
`The 5G-CN and the gNB establish a control plane interface
`and a user plane interface for the UE. The control plane
`interface between the 5G-CN and the gNB (i.e., RAN) is
`referred to as an NG2 interface or an NG-c interface and is
`used for transfer of Non-Access Stratum (NAS) information
`and for transfer of control information (e.g., NG2 AP
`Information Element) between the 5G-CN and the gNB. The
`user plane interface between the 5G-CN and the gNB (i.e.,
`RAN) is referred to as an NG3 interface or an NG-u
`interface and is used for transfer of packets of one or more
`PDU flows in a PDU session of the UE.
`
`Ex.1011
`APPLE INC. / Page 14 of 25
`
`

`

`US 11,252,643 B2
`
`4
`random access preamble) of the random access procedure,
`via the third message (Msg3) of the random access proce(cid:173)
`dure, or via dedicated Radio Resource Control (RRC) sig(cid:173)
`nalling after an RRC connection has been established. The
`transmission of the SI response by the gNB may be a unicast
`for the UE that has made the request, a group-cast for a
`group of UEs including the UE that has made a request, or
`a non-periodic broadcast. In the case of unicasting the SI
`response, the SI response containing the Other SI (or On(cid:173)
`demand SI) may be transmitted via the second message
`(Msg2) (i.e., random access response (RAR)) of the random
`access procedure, via the fourth message (Msg3) of the
`random access procedure, or via dedicated Radio Resource
`Control (RRC) signalling after an RRC connection has been
`established. In the case of the group-cast or non-periodic
`broadcast of the SI response, a paging mechanism may be
`used, and the SI response containing the Other SI ( or
`On-demand SI) may be broadcast in a paging occasion
`determined based on an identifier (e.g., Paging Radio Net(cid:173)
`work Temporary Identifier (P-RNTI)) of the UE or the UE
`group.
`
`CITATION LIST
`
`Non Patent Literature
`
`3
`Note that, the architecture shown in FIG. 1 is merely one
`of the 5G architecture options or deployment scenarios (see
`Annex J of Non-Patent Literature 1 and see Non-Patent
`Literature 2). The architecture shown in FIG. 1 is referred to
`as "Standalone NR (in NextGen System)" or "Option 2". In 5
`contrast, FIGS. 2 and 3 show architecture Options 3 and 3A,
`which are referred to as "Non-standalone NR in EPS". In
`FIGS. 2 and 3, control interfaces are shown as dashed lines,
`while user plane interfaces are shown as solid lines. Archi(cid:173)
`tecture Options 3 and 3A are Dual connectivity (DC) 10
`deployments including E-UTRA as the anchor RAT (or the
`primary RAT or the master RAT) and NR as a 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 the LTE eNB in Option 15
`3, whereas in Option 3A, it passes directly through a user
`plane interface between the gNB and the EPC.
`Non-Patent Literature 3 has suggested that in Architecture
`Options 3 and 3A, which are DC architecture where
`E-UTRA and NR are connected to the EPC, the NR gNB 20
`supports the LTE DC functionalities and procedures. Non(cid:173)
`Patent Literature 3 has also suggested that in the DC
`architecture where E-UTRA and NR are connected to the
`EPC, the NR gNB applies the LTE QoS framework (i.e.,
`bearer based QoS) to the EPC, the LTE eNB and the UE. 25
`Further, Non-Patent Literature 3 has suggested the following
`proposals:
`LTE DC procedures (e.g., SeNB addition) are applied when
`adding NR gNB as secondary node, in which necessary
`QoS service (i.e., bearer) are configured;
`E-UTRAN Radio Access Bearer (E-RAB) is established
`between EPC and NR gNB for Secondary Cell Group
`(SCG) bearer option according to LTE;
`X2-U is established between LTE eNB and NR gNB for split
`bearer option according to LTE; and
`DRB is established between NR gNB and UE according to
`SCG bearer option or split bearer option according to
`LTE.
`Non-Patent Literature 4 has suggested that there is one(cid:173)
`to-one mapping (1:1 mapping) between Sl-U and DRB of 40
`SCG (i.e., SCG bearer). Non-Patent Literature 4 has also
`suggested that QoS attributes of EPC are in use for EPS
`bearers and, accordingly, there is a need to map the QoS
`parameters used in EPC to the radio bearer parameters used
`in the NR.
`in the 5G system, the system information
`Further,
`includes system information that is always broadcast and
`system information that is not always broadcast. The system
`information that is always broadcast is referred to as "Mini(cid:173)
`mum SI" or "Essential SI". Meanwhile, the system infor- 50
`mation that is not always broadcast is referred to as "Other
`SI" or "On-demand SI". The Minimum SI needs to be
`periodically broadcast in a cell. The Minimum SI is sup(cid:173)
`posed to include at least information for assisting cell
`selection, information for acquiring On-demand SI, and 55
`information for accessing the cell. The term "Other SI"
`indicates all kinds of system information that are not broad(cid:173)
`cast in the Minimum SI. A part or all of the Other SI
`corresponds to the On-demand SI. The On-demand SI is
`transmitted by the gNB after it has been triggered by a UE 60
`or a network. In other words, in response to an SI request
`from a UE, the gNB sends an SI response containing
`requested system information to the UE.
`There are several proposals regarding a distribution
`mechanism of Other SI (or On-demand SI) (see, for 65
`example, Non-Patent Literature 5-8). The SI request from
`the UE may be transmitted via the first message (Msgl) (i.e.,
`
`35
`
`30
`
`[Non-Patent Literature 1] 3GPP TR 23.799 V14.0.0 (2016-
`12) "3rd Generation Partnership Project; Technical Speci(cid:173)
`fication Group Services and System Aspects; Study on
`Architecture for Next Generation System (Release 14)",
`December 2016
`[Non-Patent Literature 2] 3GPP TR 38.801 Vl.0.0 (2016-
`12) "3rd Generation Partnership Project; Technical Speci(cid:173)
`fication Group Radio Access Network; Study on New
`Radio Access Technology; Radio Access Architecture and
`Interfaces (Release 14)", December 2016
`[Non-Patent Literature 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 Nov. 2016
`[Non-Patent Literature 4] 3GPP R2-168686, Nokia, Alcatel(cid:173)
`Lucent Shanghai Bell, "EPC-NR PDCP interaction for
`tight interworking: User Plane aspects", 3GPP TSG-RAN
`WG2 Meeting #96, Reno, USA, 14-18 Nov. 2016
`45 [Non-Patent Literature 5] 3GPP R2-166120, China Acad(cid:173)
`emy of Telecommunications Technology (CATT), "On(cid:173)
`demand system information delivery mechanism", 3GPP
`TSG-RAN WG2 Meeting #95 bis, Kaohsiung, 10-14 Oct.
`2016
`[Non-Patent Literature 6] 3GPP R2-166203, Huawei, HiSili(cid:173)
`con, "Delivery of "Other SI" in NR", 3GPP TSG-RAN
`WG2 Meeting #95 bis, Kaohsiung, 10-14 Oct. 2016
`[Non-Patent Literature 7] 3GPP R2-166342, ZTE, ZTE
`Microelectronics, "Consideration on the Other SI delivery
`in NR", 3GPP TSG-RAN WG2 Meeting #95 bis, Kaoh(cid:173)
`siung, 10-14 Oct. 2016
`[Non-Patent Literature 8] 3GPP R2-166343, ZTE, ZTE
`Microelectronics, "Consideration on the Other SI delivery
`in NR", 3GPP TSG-RAN WG2 Meeting #95 bis, Kaoh(cid:173)
`siung, 10-14 Oct. 2016
`
`SUMMARY OF INVENTION
`
`Technical Problem
`
`The present inventors have studied interworking between
`E-UTRA and NR and found several problems. In E-UTRA-
`
`Ex.1011
`APPLE INC. / Page 15 of 25
`
`

`

`US 11,252,643 B2
`
`5
`NR Dual Connectivity (DC) architecture in which E-UTRA
`and NR are connected to the EPC (i.e., architecture options
`3 and 3A), the Secondary gNB (SgNB) serving as the
`secondary node supports Other-SI ( or On-demand SI) dis(cid:173)
`tribution described above. However, it is not clear how UEs 5
`know which Other SI (or On-demand SI) is available in the
`SgNB of E-UTRA-NR DC.
`This problem regarding the Other SI (or On-demand SI)
`may occur also in other E-UTRA-NR DC architecture
`options (e.g., architecture options 7 and 7A). The architec- 10
`ture options 7 and 7A are Dual connectivity (DC) deploy(cid:173)
`ments including E-UTRA serving as the anchor RAT ( or the
`primary RAT or the master RAT) and NR serving as the
`secondary RAT. In the options 7 and 7A, E-UTRA (LTE
`eNB) and NR (gNB) are connected to the 5G-CN. The NR 15
`user plane connection to the 5G-CN goes through the LTE
`eNB in the option 7, whereas it directly passes through the
`user plane interface between the gNB and the 5G-CN in the
`option 7 A. In the options 7 and 7 A as well, it is not clear how
`UEs know which Other SI ( or On-demand SI) is available in 20
`the SgNB when the SgNB supports the Other SI (or On(cid:173)
`demand SI) distribution.
`Further, problems similar to the above ones regarding the
`Other SI (or On-demand SI) may occur also in Inter-RAT
`handovers from E-UTRA to NR. Specifically, when a UE is 25
`handed over from a source LTE eNB to a target gNB that
`supports the Other SI (or On-demand SI) distribution, it is
`not clear how the UE knows which Other SI ( or On-demand
`SI) is available in the target NR cell.
`Accordingly, one of the objects to be attained by embodi- 30
`ments disclosed herein is to provide an apparatus, a method,
`and a program that enable notifying a UE of an indication
`about on-demand system information available in a cell
`served by a secondary gNB of Inter-RAT dual connectivity
`between E-UTRA and NR, or available in a cell served by 35
`a target gNB of Inter-RAT handover from E-UTRA to NR.
`It should be noted that this object is merely one of the objects
`to be attained by the embodiments disclosed herein. Other
`objects or problems and novel features will be made appar(cid:173)
`ent from the following description and the accompanying 40
`drawings.
`
`Solution to Problem
`
`6
`In a third aspect, a radio terminal is used in a radio
`communication system. The radio terminal includes at least
`one wireless transceiver and at least one processor. The at
`least one wireless transceiver is configured to communicate
`with a first radio access network (RAN) node and a second
`RAN node. The at least one processor is configured to
`receive from the second RAN node, via the first RAN node,
`an indication of available on-demand system information
`that is available in a cell of the second RAN node. The
`available on-demand system information is to be transmitted
`in the cell of the second RAN node, or transmitted via the
`first RAN node, in response to a request from the radio
`terminal.
`In a fourth aspect, a method for a second radio access
`network (RAN) node includes sending to a radio terminal,
`via a first RAN node, an indication of available on-demand
`system information that is available in a cell of the second
`RAN node. The available on-demand system information is
`to be transmitted in the cell of the second RAN node, or
`transmitted via the first RAN node, in response to a request
`from the radio terminal.
`In a fifth aspect, a method for a first radio access network
`(RAN) node includes: receiving from a second RAN node
`an indication of available on-demand system information
`that is available in a cell of the second RAN node; and
`transmitting the indication to a radio terminal in a cell of the
`first RAN node. The available on-demand system informa(cid:173)
`tion is to be transmitted in the cell of the second RAN node,
`or transmitted via the first RAN node, in response to a
`request from the radio terminal.
`In a sixth aspect, a method for a radio terminal includes
`receiving from a second radio access network (RAN) node,
`via a first RAN node, an indication of available on-demand
`system information that is available in a cell of the second
`RAN node. The available on-demand system information is
`to be transmitted in the cell of the second RAN node, or
`transmitted via the first RAN node, in response to a request
`from the radio terminal.
`In a seventh aspect, a program includes instructions
`(software codes) that, when loaded into a computer, cause
`the computer to perform the method according to the above(cid:173)
`described fourth, fifth, or sixth aspect.
`
`Advantageous Effects of Invention
`
`According to the above-deceived aspects, it is possible to
`provide an apparatus, a method, and a program that enable
`notifying a UE of an indication about on-demand system
`information available in a cell served by a secondary gNB of
`Inter-RAT dual connectivity between E-UTRA and NR, or
`available in a cell served by a target gNB of Inter-RAT
`handover from E-UTRA to NR.
`
`BRIEF DESCRIPTION OF DRAWINGS
`
`In a first aspect, a second radio access network (RAN) 45
`node is used in a radio communication system. 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 to a radio terminal, via a first RAN node,
`an indication of available on-demand system information 50
`that is available in a cell of the second RAN node. The
`available on-demand system information is to be transmitted
`in the cell of the second RAN node, or transmitted via the
`first RAN node, in response to a request from the radio
`terminal.
`In a second aspect, a first radio access network (RAN)
`node is used in a radio communication system. 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 from a second RAN node an indica- 60
`tion of available on-demand system information that is
`available in a cell of the second RAN node; and transmit the
`indication to a radio terminal in a cell of the first RAN node.
`The available on-demand system information is to be trans(cid:173)
`mitted in the cell of the second RAN node, or transmitted via
`the first RAN node, in response to a request from the radio
`terminal.
`
`55
`
`FIG. 1 is a diagram showing basic architecture of the 5G
`System according to the Background Art;
`FIG. 2 is a diagram showing Architecture Option 3 for
`Dual Connectivity where E-UTRA (LTE eNB) and NR
`(gNB) are connected to EPC, according to the Background
`Art;
`FIG. 3 is a diagram showing Architecture Option 3A for
`65 Dual Connectivity where E-UTRA (LTE eNB) and NR
`(gNB) are connected to EPC, according to the Background
`Art;
`
`Ex.1011
`APPLE INC. / Page 16 of 25
`
`

`

`US 11,252,643 B2
`
`7
`8
`FIG. 4 is a diagram showing one configuration example of
`and the EPC. In contrast, in the option 3A, the NR user plane
`a radio communication network according to a plurality of
`connection to the EPC 4 directly passes through a user plane
`interface 404 between the gNB 2 and the EPC 4.
`embodiments;
`The UE 3 has a capability to simultaneously communicate
`FIG. 5 is a diagram showing another configuration
`with the eNB 1 associated with the primary RAT (E-UTRA)
`example of a radio communication network according to a 5
`plurality of embodiments;
`and the gNB 2 associated with the secondary RAT (NR). In
`FIG. 6 is a diagram showing one example of a procedure
`other words, the UE 3 has a capability to aggregate a cell of
`for sending to a UE an indication about available on-demand
`the eNB 1 associated with the primary RAT (E-UTRA) with
`system information according to a first embodiment;
`a cell of the gNB 2 associated with the secondary RAT (NR).
`FIG. 7 is a diagram showing one example of a procedure 10
`Further, in other words, the UE 3 has a capability to be
`for sending to a UE an indication about available on-demand
`configured with both a cell of the eNB 1 associated with the
`system information according to the first embodiment;
`primary RAT (E-UTRA) and a cell of the gNB 2 associated
`FIG. 8 is a diagram showing one example of a procedure
`with the secondary RAT (NR). In the architecture options 3
`for sending to a UE an indication about available on-demand
`15 and 3A, an air interface 402 between the eNB 1 and the UE
`system information according to the first embodiment;
`3 provides a control plane connection and a user plane
`FIG. 9 is a sequence diagram showing an example of an
`connection. Meanwhile, an air interface 405 between the
`SCG establishment procedure according to a second
`gNB 2 and the UE 3 includes at least a user plane connec(cid:173)
`embodiment;
`tion, but it does not need to include a control plane connec-
`FIG. 10 is a sequence diagram showing an example ofan
`Inter-RAT handover procedure according to a third embodi- 20 tion. In th