throbber
1111111111111111 IIIIII IIIII 1111111111 11111 1111111111 11111 11111 1111111111 1111111111 11111111
`US 2020011301 lAl
`
`c19) United States
`c12) Patent Application Publication
`Peisa et al.
`
`c10) Pub. No.: US 2020/0113011 Al
`Apr. 9, 2020
`(43) Pub. Date:
`
`(54) METHODS AND APPARATUS FOR
`REQUESTING SYSTEM INFORMATION IN A
`WIRELESS COMMUNICATION NETWORK
`
`(71) Applicant: Telefonaktiebolaget LM Ericsson
`(publ), Stockholm (SE)
`
`(72)
`
`Inventors: Janne Peisa, Espoo (FI); Jens
`Bergqvist, Linkiiping (SE); Johan
`Rune, Lidingii (SE); Henning
`Wiemann, Aachen (DE)
`
`(21) Appl. No.:
`
`16/068,003
`
`(22) PCT Filed:
`
`May 2, 2018
`
`(86) PCT No.:
`
`PCT /SE2018/050448
`
`§ 371 (c)(l),
`(2) Date:
`
`Jul. 3, 2018
`
`Related U.S. Application Data
`
`(60) Provisional application No. 62/502,037, filed on May
`5, 2017.
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`H04W 76127
`H04W72/04
`H04W 74108
`H04L 5100
`(52) U.S. Cl.
`CPC ........... H04W 76127 (2018.02); H04L 510055
`(2013.01); H04W 7410833 (2013.01); H04W
`72104 (2013.01)
`
`(2006.01)
`(2006.01)
`(2006.01)
`(2006.01)
`
`ABSTRACT
`(57)
`Embodiments disclosed herein provide methods and appa(cid:173)
`ratus for requesting system information in a wireless com(cid:173)
`munications network. The method comprises in a user
`equipment for a wireless network receiving, from a base
`station of the wireless network, a first portion of system
`information comprising an indication of a second portion of
`system information which is available upon request; and
`transmitting, to the base station, a first request requesting
`that the second portion of system information be transmitted
`to the user equipment. The method further comprises
`responsive to a determination that the requested second
`portion of system information has not been received suc(cid:173)
`cessfully by the user equipment, transmitting, to the base
`station, a second request for the second portion of system
`information.
`
`( 103
`
`UE
`
`r 102
`
`gNB
`
`-
`
`r-101
`Minimum Svstem information
`always present and broadcast periodically
`/'104
`f,,lt- _ _ _ _ _ Other SY§.tem Information ______
`optionally present and broadcast periodically
`~104
`f,,lt- ___ On-Demand Other S.1.stem Information ____
`broadcast or dedicated signalling
`
`Ex.1014
`APPLE INC. / Page 1 of 20
`
`

`

`Patent Application Publication
`
`Apr. 9, 2020 Sheet 1 of 7
`
`US 2020/0113011 Al
`
`f 103
`
`UE
`
`( 102
`
`gNB
`
`r-101
`Minimum Svstem information
`always present and broadcast periodically
`r-104
`f,,it- _ _ _ _ _ Other SY§.tem Information ______
`optionally present and broadcast periodically
`"104
`f,,it- _ _ _ On-Demand Other S_y_stem Information ____
`broadcast or dedicated signalling
`
`Figure 1
`
`Ex.1014
`APPLE INC. / Page 2 of 20
`
`

`

`Patent Application Publication
`
`Apr. 9, 2020 Sheet 2 of 7
`
`US 2020/0113011 Al
`
`1Q
`
`18
`
`20
`
`Core network
`
`Backhaul network
`
`((<
`I
`
`12
`
`>))
`
`~
`
`16
`
`Figure 2
`
`Ex.1014
`APPLE INC. / Page 3 of 20
`
`

`

`Patent Application Publication
`
`Apr. 9, 2020 Sheet 3 of 7
`
`US 2020/0113011 Al
`
`Receive, from a network node of the wireless
`network, a first portion of system information
`comprising an indication of a second portion of
`system information which is available upon request
`
`,,..,.,.- 301
`
`1J
`Transmit, to the network node, a first request
`requesting that the second portion of system
`information be transmitted to the terminal device
`
`,,,-- 303
`
`Responsive to a determination that the requested ,,,-- 305
`second portion of system information has not been
`received successfully by the terminal device,
`transmit, to the network node, a second request for
`the second portion of system information
`
`Figure 3
`
`Ex.1014
`APPLE INC. / Page 4 of 20
`
`

`

`Patent Application Publication
`
`Apr. 9, 2020 Sheet 4 of 7
`
`US 2020/0113011 Al
`
`[401
`
`,:.~····································································"" .
`
`Terminal device receives
`first portion of SI with
`indication of second
`portion of SI
`----.......-----,~ ...... ~
`
`403
`
`Terminal device transmits
`request for second
`portion of SI
`
`... ~ .................................. : ................................. >...:.
`
`409
`
`N = N +1
`
`No
`
`-····""'····-····""'·····""'····-····""'·····-····""·····""'····-····""'·····""'····-····""'·····-··' _ .. ~
`
`Cell barred, limited
`service or one or
`more unavailable
`services
`
`411
`
`. 1 No
`
`413
`
`Second portion of system
`information received
`successfully
`
`Figure 4
`
`Ex.1014
`APPLE INC. / Page 5 of 20
`
`

`

`~
`
`> ....
`....
`0 ....
`....
`0 --- 0 ....
`
`N
`0
`N
`rJJ
`c
`
`0 ....
`Ul
`.....
`rJJ =(cid:173)
`
`('D
`('D
`
`-....J
`
`0
`N
`0
`N
`~\,Ci
`
`t :-:
`.... 0 =
`""O = O" -....
`.... 0 =
`t "e -....
`
`~ .....
`
`(')
`
`('D = .....
`~ .....
`""O
`
`~ .....
`
`(')
`
`(514
`533
`Assume preamble not received
`
`S1-RNTI not received -
`
`backoff delay)
`stepwise increased
`ramping (possibly with
`preamble" with power
`Prepare to retransirnit
`

`\
`
`·-
`
`539
`
`~'~~~,\.,
`
`Monitor SI window
`
`(no backoff delay}
`power ramping
`preamble* without
`Prepare to retransirnit
`
`successfully
`ended
`Procedure
`
`515
`
`537
`
`SI not received
`
`SI received
`
`\ ;
`
`I
`
`Assume preamble received
`
`SI-RNTI received _.
`
`-··
`/
`
`535
`
`531
`
`-
`
`529
`
`507
`
`. .,,,,,41.---__ _
`
`·,,,,.,,.,.,,,,,_,
`
`.,,,,,,,,
`
`Transmit preamble
`
`' l .. 1.
`
`,,,,,,,,,,,,,,),! Set initial TX power and select preamble
`
`Start
`
`Figure 5
`
`•mmm,m,mmummHmmum,mHHm
`
`mm,mm. j i!IJ
`1
`
`t ,mHHmmmm,mm,m,mmmmmm,mmmmHmmmmmmHHmmHmmmHmmmmmHmHmmHmummmm,f~ Hmum,mmm,mummmum,muHmmmmmum,m,m,NHH.
`l
`l
`l
`.I
`
`519 Prepare to retransimit
`
`backoff delay)
`power ramping (no
`preamble* without
`
`successfully
`ended
`Procedure
`
`525
`
`;
`> <,
`~\ ,,
`SI not received
`
`5231 SI recei!d"
`
`~
`
`received
`S1-RNTI received
`S1-RNTI not
`~ "
`/ .i
`Monitor Sl window
`
`521
`
`\.
`\~
`\
`
`f i."
`~·
`
`\
`
`513
`
`517
`rs11
`
`j ' ' ~ .
`
`;
`
`Assume preamble received
`
`Broadcast flag set .... ,.
`
`Broadcast flag cleared -
`I
`Check broadcast flag
`
`Assume preamble not received
`
`509
`
`! ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
`j
`'
`i
`ba~k off delay)
`steowise increased
`ramping (possibly with
`preamble* with power
`:~ ' :~ *
`I Prepare to retransmit
`
`
`.l
`
`~ :~ '
`~ ' ' :~ ' !
`• !
`l
`' l
`' ' ' ' ' ' ' ' i ' ' ' ' :~ ' i
`
`i
`~
`~
`~
`' i
`' j .,
`' ' ~ ' ' ' ' .~
`
`i
`f
`
`Ex.1014
`APPLE INC. / Page 6 of 20
`
`

`

`~
`
`> ....
`....
`0 ....
`....
`0 --- 0 ....
`
`N
`0
`N
`rJJ
`c
`
`0 ....
`O'I
`.....
`rJJ =(cid:173)
`
`('D
`('D
`
`--:i
`
`0
`N
`0
`N
`~\,Ci
`
`t :-:
`.... 0 =
`""O = O" -....
`.... 0 =
`t "e -....
`
`~ .....
`
`(')
`
`('D = .....
`~ .....
`""O
`
`~ .....
`
`(')
`
`i~m,mnm,m,mnm,mmmmnm! Figure 6
`:I
`.,
`
`!
`,
`
`'
`
`·'
`
`successfully
`ended
`Procedure
`
`:1
`
`629
`
`r-625
`
`1s1 not.re~eived
`
`general gNB error
`erroneous HARQ success, or
`Assume preamble collision,
`
`· .,,,,,,,,,,,,,,,_,,,,,,, S1-RNTI not received -+
`
`it
`\
`Assume tv1sg3 success
`S1-RNTI received
`,,,,,.,,.,..
`
`!
`/
`
`627
`
`623
`
`--------~
`h21
`
`'m,mmm,/yy/ ,mvmm, /'
`
`l.:,.,,_"',,,-,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,.,,,,,,,,,,.,,
`'
`
`i
`j
`Select preamble and 'prepare to retransmit I
`609
`~ !
`~ !
`
`No RAR received
`
`607
`
`!
`
`605
`
`stepwise increased back off delay)
`with power ramping (and possibly
`
`Monitor SI window
`
`619
`
`··\,,,.,, ...
`
`J
`
`}~mumnm,mm,mJ,,j-mmnmmm,mmnm,mmm,mmm,mm,mmmmmmmnm,m,mmm,
`
`Lmm,mmmmmmmmmmmmmmmmmmmuum,mum,mum,mum,mumnm,mnm,m.
`
`I
`I
`
`I
`~
`f
`! 643
`
`successfully
`ended
`Procedure
`' ~~
`
`647
`
`639
`
`received
`S1-RNTI not
`"'~~ •.
`
`S1-RNTI received
`
`f
`
`641
`
`Monitor SI window
`
`637
`
`Assume Msg3 success
`Broadcast flag set
`
`(635
`
`~ ·I:
`~,,,,1 Trasmit Msg3 I
`
`6131 HARQ failure
`
`611
`
`step wise increased backoff de!ay?)
`without power ramping (but possibly witJ;
`Select preamble and prepare to retransmit
`
`[ HARQ success
`
`617
`
`631
`
`·:,,.❖~~~~
`Check broadcast flag
`. .I
`
`I general gNB error
`i
`erroneous HAf~Q success, or
`j Assume preamb1e coi!ision,
`! ! Broadcast flag set deared -,,
`! I 633
`
`Jmmvmmmvmvm,m,mvmvv;J:
`~
`:!:
`
`I
`~ • • • ~
`• • • • • • ~ • • ~ • ~
`
`~
`:;:
`[
`
`~
`~
`~
`
`!
`
`!
`j
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`!
`r.,.,.,.,,,,,.,.,,,.,.,,,,.,.,,,,,.,.,,,.,.,,,,.,.,,,,,.,,,,
`
`Start ,,,,,,,,,,,,,,;z~1 Set initial TX power and select preamble
`
`615
`
`601
`
`Ex.1014
`APPLE INC. / Page 7 of 20
`
`

`

`Patent Application Publication
`
`Apr. 9, 2020 Sheet 7 of 7
`
`US 2020/0113011 Al
`
`702 - -...,
`
`704 - -...,
`
`802 - -...,
`
`804 - -...,
`
`806 - -...,
`
`~ 700
`
`Processing circuitry
`
`~ 800
`
`Memory
`
`Figure 7
`
`First module
`
`Second module
`
`Third module
`
`Figure 8
`
`Ex.1014
`APPLE INC. / Page 8 of 20
`
`

`

`US 2020/0113011 Al
`
`Apr. 9, 2020
`
`1
`
`METHODS AND APPARATUS FOR
`REQUESTING SYSTEM INFORMATION IN A
`WIRELESS COMMUNICATION NETWORK
`
`TECHNICAL FIELD
`
`[0001] The present disclosure relates to methods and appa(cid:173)
`ratus for requesting system information in a terminal device
`for a wireless network.
`
`BACKGROUND
`
`[0002] Efforts are on-going to develop and standardize
`communications networks and protocols intended to meet
`the requirements set out for the fifth generation (5G) of
`wireless systems, as defined by the Next Generation Mobile
`Networks Alliance. The new system (also known as "New
`Radio" or "NR") is being designed to support lean carrier
`operation, where only absolutely necessary information is
`transmitted, preferably in a dedicated manner to the UE.
`This aim has a large impact on the design of the system
`information mechanisms for NR, as system information
`until now has always been transmitted and broadcast to all
`UEs in a cell. Furthermore, system information and initial
`access design is not as easy to modify or enhance in later
`releases as features require primarily dedicated signaling.
`[0003]
`In order to minimize the amount of system infor(cid:173)
`mation broadcast, on-demand delivery of parts of the system
`information may be introduced.
`[0004] FIG. 1 illustrates on-demand signaling for delivery
`of parts of the system information. For this on-demand
`delivery the system information (SI) may be divided into
`Minimum SI and Other SI. Minimum SI 101 is periodically
`broadcast from the Node B 102 and received by the user
`equipment (UE) 103. The Minimum SI 101 comprises basic
`information required for initial access to the network and
`information for acquiring any other SI broadcast periodi(cid:173)
`cally or provisioned on-demand, i.e. scheduling information.
`The Other SI 104 encompasses everything not broadcast in
`the Minimum SI 101 and may either be broadcast, or
`provisioned in a dedicated manner, either triggered by the
`network or upon request from the UE.
`[0005] For UEs operating in a connected state (i.e. RRC_
`CONNECTED), dedicated radio resource control (RRC)
`signaling can be used for the request and delivery of the
`Other SI. The Other SI may be broadcast at a configurable
`periodicity and for a certain duration. It is a network
`decision whether the Other SI is broadcast or delivered
`through dedicated and UE specific RRC signaling.
`[0006] Each cell on which the UE is allowed to camp
`broadcasts at least some contents of the Minimum SI, while
`there may be cells in the system on which the UE cannot
`camp and do not broadcast the Minimum SI.
`[0007] For a cell/frequency that is considered for camping
`by the UE, the UE is not required to acquire the contents of
`the Minimum SI of that cell/frequency from another cell/
`frequency layer. This does not preclude the case that the UE
`applies stored SI from previously visited cell(s).
`[0008]
`If the UE cannot determine the full contents of the
`Minimum SI of a cell (by receiving from that cell or from
`valid stored SI from previous cells), the UE may consider
`that cell as barred.
`[0009]
`In addition, for an on demand request of broadcast
`SI transmission a UE operating in an idle or inactive mode
`the network may control whether the request for Other
`
`system information is transmitted by a random access pre(cid:173)
`amble message or as part of a radio resource control con(cid:173)
`nection message.
`[0010]
`If the Physical Random Access Channel (PRACH)
`preamble and/or PRACH resource specific to each system
`information block (SIB) or set of SIBS which the UE needs
`to acquire is included in minimum SI, then the SI request
`may be indicated using the random access preamble.
`[0011]
`If the PRACH preamble and/or PRACH resource
`specific to each SIB or set of SIBS which the UE needs to
`acquire is not included in the minimum SI, then the SI
`request may be included as part of a radio resource control
`connection message.
`
`SUMMARY
`
`[0012] The current solution does not cover any error cases
`when UE requests on-demand system information. For
`example, the request from the UE may not be received
`correctly by the network, or may collide with a request from
`another UE or the UE may not be able to receive the
`on-demand SIB transmission from the network. Based on
`currently agreed procedure, the UE may not be able to fully
`function in the system even for relatively minor errors in the
`on-demand system information procedure.
`[0013] According to a first aspect of the disclosure there is
`provided a method of requesting system information in a
`terminal device for a wireless network. The method com(cid:173)
`prises receiving, from a network node of the wireless
`network, a first portion of system information comprising an
`indication of a second portion of system information which
`is available upon request. The method also comprises trans(cid:173)
`mitting, to the network node, a first request requesting that
`the second portion of system information be transmitted to
`the terminal device; and responsive to a determination that
`the requested second portion of system information has not
`been received successfully by the terminal device, transmit(cid:173)
`ting, to the network node, a second request for the second
`portion of system information.
`[0014] According to another aspect of the disclosure there
`is provided a terminal device for a wireless network, the
`terminal device configured to carry out the method as
`described above.
`[0015] According to another aspect of the disclosure there
`is provided a terminal device for requesting system infor(cid:173)
`mation. The terminal device comprises: processing circuitry
`and a machine-readable medium storing instructions which,
`when executed by the processing circuitry, cause the termi(cid:173)
`nal device to: receive, from a network node of the wireless
`network, a first portion of system information comprising an
`indication of a second portion of system information which
`is available upon request; transmit, to the network node, a
`first request requesting that the second portion of system
`information be transmitted to the terminal device; and
`responsive to a determination that the requested second
`portion of system information has not been received suc(cid:173)
`cessfully by the terminal device, transmit, to the network
`node, a second request for the second portion of system
`information.
`[0016] According to another aspect of the present disclo(cid:173)
`sure there is provided a terminal device for a wireless
`network, for requesting system information. The terminal
`device comprises: a first module configured to receive, from
`a network node of the wireless network, a first portion of
`system information comprising an indication of a second
`
`Ex.1014
`APPLE INC. / Page 9 of 20
`
`

`

`US 2020/0113011 Al
`
`Apr. 9, 2020
`
`2
`
`portion of system information which is available upon
`request; a second module configured to transmit, to the
`network node, a first request requesting that the second
`portion of system information be transmitted to the terminal
`device; and a third module configured to, responsive to a
`determination that the requested second portion of system
`information has not been received successfully by the ter(cid:173)
`minal device, transmit, to the network node, a second
`request for the second portion of system information.
`[0017] The methods and apparatus disclosed herein allow
`efficient recovery from minor errors in the acquisition of
`system information, and avoids UE not functioning correctly
`due to incomplete system information.
`[0018] Note that the discussion below focuses on a tech(cid:173)
`nical solution for LTE and those networks intended to meet
`the requirements set out for the fifth generation (5G) of
`wireless systems, as defined by the Next Generation Mobile
`Networks Alliance. However, those skilled in the art will
`appreciate that it is also possible to apply the methods and
`apparatus described herein to other networks and access
`technologies. In other networks, nodes and interfaces may
`have different names.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0019] For a better understanding of the present disclo(cid:173)
`sure, and to show how it may be put into effect, reference
`will now be made, by way of example, to the accompanying
`drawings, in which:
`[0020] FIG. 1 illustrates on-demand signaling for delivery
`of parts of the system information;
`[0021] FIG. 2 shows a network according to embodiments
`of the disclosure;
`[0022] FIGS. 3 to 6 are flowcharts of methods according
`to embodiments of the disclosure;
`[0023] FIG. 7 is a schematic drawing of a terminal device
`according to embodiments of the disclosure; and
`[0024] FIG. 8 is a schematic drawing of a terminal device
`according to further embodiments of the disclosure.
`
`DESCRIPTION
`
`[0025] The following sets forth specific details, such as
`particular embodiments for purposes of explanation and not
`limitation. But it will be appreciated by one skilled in the art
`that other embodiments may be employed apart from these
`specific details. In some instances, detailed descriptions of
`well-known methods, nodes, interfaces, circuits, and devices
`are omitted so as not obscure the description with unneces(cid:173)
`sary detail. Those skilled in the art will appreciate that the
`functions described may be implemented in one or more
`nodes using hardware circuitry (e.g., analog and/or discrete
`logic gates interconnected to perform a specialized function,
`ASICs, PLAs, etc.) and/or using software programs and data
`in conjunction with one or more digital microprocessors or
`general purpose computers that are specially adapted to
`carry out the processing disclosed herein, based on the
`execution of such programs. Nodes that communicate using
`the air interface also have suitable radio communications
`circuitry.
`[0026] Thus, for example, it will be appreciated that
`"receiving" and "transmitting" steps performed by a wire(cid:173)
`less terminal or a radio base station are performed, e.g., by
`a processing circuit, using receiver circuitry and transmitter
`circuitry, respectively. Moreover, the technology can addi-
`
`tionally be considered to be embodied entirely within any
`form of computer-readable memory, such as solid-state
`memory, magnetic disk, or optical disk containing an appro(cid:173)
`priate set of computer instructions that would cause a
`processor to carry out the techniques described herein.
`[0027] Hardware implementation may include or encom(cid:173)
`pass, without limitation, digital signal processor (DSP)
`hardware, a reduced instruction set processor, hardware
`( e.g., digital or analog) circuitry including but not limited to
`application specific integrated circuit(s) (ASIC) and/or field
`programmable gate array(s) (FPGA(s)), and (where appro(cid:173)
`priate) state machines capable of performing such functions.
`[0028]
`In terms of computer implementation, a computer
`is generally understood to comprise one or more processors,
`one or more processing modules or one or more controllers,
`and the terms computer, processor, processing module and
`controller may be employed interchangeably. When pro(cid:173)
`vided by a computer, processor, or controller, the functions
`may be provided by a single dedicated computer or proces(cid:173)
`sor or controller, by a single shared computer or processor
`or controller, or by a plurality of individual computers or
`processors or controllers, some of which may be shared or
`distributed. Moreover, the term "processor" or "controller"
`also refers to other hardware capable of performing such
`functions and/or executing software, such as the example
`hardware recited above.
`[0029] Although the description is given for a wireless
`terminal device, or user equipment (UE), it should be
`understood by the skilled in the art that "UE" is a non(cid:173)
`limiting term comprising any mobile or wireless device,
`terminal or node equipped with a radio interface allowing
`for at least one of: transmitting signals in uplink (UL) and
`receiving and/or measuring signals in downlink (DL). AUE
`herein may comprise a UE (in its general sense) capable of
`operating or at least performing measurements in one or
`more frequencies, carrier frequencies, component carriers or
`frequency bands. It may be a "UE" operating in single- or
`multi-radio access technology (RAT) or multi-standard
`mode. As well as "UE", the terms "mobile station" ("MS"),
`"mobile device", "terminal device" and "wireless terminal
`device" may be used interchangeably in the following
`description, and it will be appreciated that such a device
`does not necessarily have to be 'mobile' in the sense that it
`is carried by a user. Examples ofUE are target device, device
`to device (D2D) UE, machine type UE or UE capable of
`machine to machine (M2M) communication, PDA, tablet
`computer, mobile terminals, smart phone, laptop embedded
`equipped (LEE), laptop mounted equipment (LME), USB
`dongles, ProSe UE, V2V UE, V2X UE, MTC UE, eMTC
`UE, FeMTC UE, UE Cat 0, UE Cat Ml, narrowband
`Internet of Things (NB-IoT) UE, UE Cat NB!, etc.
`[0030]
`In some embodiments a more general term "net(cid:173)
`work node" is used and it can correspond to any type of radio
`access node or any network node, which communicates with
`a UE and/or with another network node. Examples of
`network nodes are NodeB, MeNB, SeNB, a network node
`belonging to MCG or SCG, base station (BS), multi-stan(cid:173)
`dard radio (MSR) radio node such as MSR BS, eNodeB,
`gNodeB, network controller, radio network controller
`(RNC), base station controller (BSC), relay, donor node
`controlling relay, base transceiver station (BTS), access
`point (AP), transmission points, transmission nodes, RRU,
`RRH, nodes in distributed antenna system (DAS), core
`network node (e.g. MSC, MME, etc.), O&M, OSS, SON,
`
`Ex.1014
`APPLE INC. / Page 10 of 20
`
`

`

`US 2020/0113011 Al
`
`Apr. 9, 2020
`
`3
`
`positioning node (e.g. E-SMLC), MDT, test equipment, etc.
`Moreover, where the following description refers to steps
`taken in or by a network node or a radio access node, this
`also includes the possibility that some or all of the process(cid:173)
`ing and/or decision making steps may be performed in a
`device that is physically separate from the radio antenna of
`the node, but is logically connected thereto. Thus, where
`processing and/or decision making is carried out "in the
`cloud", the relevant processing device is considered to be
`part of the node for these purposes.
`[0031] The embodiments are described for LTE or LTE
`based systems such as machine-type communication
`(MTC), evolved MTC (eMTC), NB-IoT etc. As an example
`MTC UE, eMTC UE and NB-IoT UE also called UE
`category 0, UE category Ml and UE category NB!. How(cid:173)
`ever, the embodiments are applicable to any RAT or multi(cid:173)
`RAT systems, where the UE receives and/or transmit signals
`(e.g. data) e.g. LTE FDD/TDD, WCDMA/HSPA, GSM/
`GERAN, WLAN, CDMA2000, 5G, NR, etc. It is recalled
`that 5G, the fifth generation of mobile telecommunications
`and wireless technology is not yet fully defined but in an
`advanced draft stage within 3GPP. It includes work on 5G
`New Radio (NR) Access Technology. LTE terminology is
`used in this disclosure in a forward looking sense, to include
`equivalent 5G entities or functionalities although a different
`term is specified in 5G.
`[0032] FIG. 2 illustrates a network 10 that may be utilized
`to explain the principles of embodiments of the present
`disclosure. The network 10 comprises a network node 12
`which is connected, via a backhaul network 20, to a core
`network 18. FIG. 1 also shows a terminal device (or UE,
`wireless terminal, etc) 16 that is in wireless communication
`with a network node 12. Messages transmitted by the
`terminal device 16 to the network node 12 are said to be
`transmitted in the "uplink", while messages transmitted by
`the network node 12 to the terminal device 16 are said to be
`transmitted in the "downlink".
`[0033] Although the terminal device 16 is illustrated as a
`mobile phone, or smartphone, it will be understood by those
`skilled in the art that the terminal device may be any device
`that is configured for communication with the wireless
`communication network 10.
`[0034] The network node 12 may be of a type referred to
`as e.g. radio access nodes, base stations, NodeBs, evolved
`NodeBs (eNB, or eNodeB), gNodeBs, base transceiver
`stations, Access Point Base Stations, base station routers,
`Radio Base Stations (RBSs), macro base stations, micro
`base stations, pica base stations, femto base stations, Home
`eNodeBs, relays and/or repeaters, beacon devices or any
`other network node configured for communication with
`wireless devices over a wireless interface, depending e.g. on
`the radio access technology and terminology used.
`[0035] The present disclosure provides methods and appa(cid:173)
`ratus for requesting system information in a terminal device
`for a wireless network. In particular, the present disclosure
`addresses issues with errors that occur when such requests
`are made, and methods for dealing with those errors when
`they occur.
`[0036] The present disclosure therefore provides a termi(cid:173)
`nal device that is able to detect a problem in the on-demand
`system information request procedure and to apply a series
`of recovery steps, such as trying to receive the on-demand
`system information one or more times and/or retransmitting
`the request one or more times. The proposed solution
`
`therefore allows efficient recovery from minor errors in the
`procedure, and avoids problems caused by a terminal device
`not functioning correctly due to incomplete system infor(cid:173)
`mation.
`[0037] FIG. 3 illustrates a method according to embodi(cid:173)
`ments of the disclosure. The method may be carried out in
`a terminal device, such as the terminal device 16, for
`example. The terminal device may be operating in an idle or
`inactive state, such as RRC_IDLE or RRC_INACTIVE. In
`other words, the terminal device may be operating in a state
`in which it is not fully connected to the network with
`dedicated radio resource control signaling.
`[0038]
`In step 301 the terminal device receives, from a
`network node of the wireless network ( such as the network
`node 12), a first portion of system information comprising an
`indication of a second portion of system information which
`is available upon request.
`[0039] The first portion of system information may be
`minimum system information (SI). The first portion of
`system information may be periodically broadcast from the
`network node and received by the terminal device. The
`minimum SI may comprise basic information required for
`initial access to the network and may also comprise infor(cid:173)
`mation for acquiring the second portion of system informa(cid:173)
`tion, i.e. scheduling information. In some embodiments, the
`first portion of system information comprises an indication
`of resources on which the second portion of system infor(cid:173)
`mation is transmitted. For example the resources on which
`the second portion of system information is transmitted may
`comprise an indication of a transmission window in which
`the second portion of system information is transmitted.
`[0040] The second portion of system information may
`comprise any system information not broadcast in the first
`portion of system information.
`[0041]
`In some embodiments the indication of a second
`portion of system information comprises a list of system
`information blocks or system information messages belong(cid:173)
`ing to the second portion of system information.
`[0042]
`In step 303 the terminal device transmits, to the
`network node, a first request requesting that the second
`portion of system information be transmitted to the terminal
`device.
`[0043] For example in embodiments where the indication
`of a second portion of system information comprises a list of
`system information blocks or system information messages
`belonging to the second portion of system information, the
`terminal device may transmit a first request requesting that
`at least one of the system information blocks or system
`information messages are transmitted to the terminal device.
`In some embodiments all of the available system informa(cid:173)
`tion blocks may be requested.
`[0044] Step 303 may be performed as part of a random
`access procedure. For example, in one embodiment the
`terminal device may send the first request as part of a
`random access preamble message to the network node ( or
`the random-access preamble message may be interpreted by
`the network node as a first request). In other embodiments,
`the terminal device may transmit the first request as part of
`a radio resource control connection message (i.e. where the
`terminal device has previously transmitted a random-access
`preamble message and received a random-access response
`message from the network node).
`[0045]
`In other embodiments the first request may be
`transmitted separately from the random access procedure.
`
`Ex.1014
`APPLE INC. / Page 11 of 20
`
`

`

`US 2020/0113011 Al
`
`Apr. 9, 2020
`
`4
`
`In step 305 the terminal device, responsive to a
`[0046]
`determination that the requested second portion of system
`information has not been received successfully by the ter(cid:173)
`minal device, transmits, to the network node, a second
`request for the second portion of system information.
`[0047]
`In step 305 therefore the terminal device may have
`identified a problem with the transmitted first request, or in
`the reception of transmitted second portion of system infor(cid:173)
`mation. In either case, therefore, the terminal device deter(cid:173)
`mines that the requested second portion of the system
`information has not been received successfully by the ter(cid:173)
`minal device. This determination may be made based on for
`example, a determination that the first request was not
`received by the network node, or a determination that the
`second portion of system information was transmitted by the
`network node, but was not received by the terminal device.
`[0048] The terminal device may therefore reinitiate a
`request for the second portion of system information by
`transmitting a second request for the second portion of
`system information. In some embodiment the second
`request, like the first request, may comprise or be comprised
`within a random-access preamble message or an RRC
`connection request message. Those skilled in the art will
`appreciate that alternative messages may be used to request
`transmission of the second portion of system information.
`[0049] FIG. 4 illustrates a method according to further
`embodiments of the disclosure. The method may be carried
`out in a terminal device, such as the terminal device 16.
`Steps 401 and 403 of FIG. 4 may be substantially similar to
`steps 301 and 303 of FIG. 3.
`[0050]
`In step 401 of FIG. 4 the terminal device receives
`a first portion of system information comprising an indica(cid:173)
`tion of a second portion of system information (SI) which is
`available on request.
`[0051]
`In step 403 the terminal device transmits a request
`for the second portion of system information.
`[0052]
`In step 405 the terminal device listens for the
`transmission of the second portion of system information
`(e.g. using scheduling information contained within the first
`portion of system information), and determines if an error
`has occurred in the request for the second portion of system
`information. The determination of an error occurring may
`occur responsive to a determination that the request second
`portion of system information has not been received suc(cid:173)
`cessfully by the terminal device.
`[0053] The determination that an error has occurred may
`comprise a number of different possibilities. For example, in
`some embodiments the terminal device sets a first timer
`upon transmission of the first request, and determ

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket