USOO7881745B1
`
`(12) Unlted States Patent
`(10) Patent No.:
`US 7,881,745 B1
`
`Rao et al.
`(45) Date of Patent:
`*Feb. 1, 2011
`
`(54) ELECTRONIC DEVICE NETWORK
`EMPLOYING PROVISIONING TECHNIQUES
`351%,? fggrgggggofig/ggms
`.
`InventorSI Bindu Rama Rao, Laguna ngueL CA
`(US); Karl W. Hammerberg, Overland
`P k KS US
`ar ’
`(
`)
`(73) Assignee: Hewlett-Packard Development
`Company, L.P., Houston, TX (US)
`
`(75)
`
`( * ) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 589 days.
`
`Thls patent ls subJeCt to a terminal (115-
`claimer.
`
`5,442,771 A
`5,479,637 A
`5,579,522 A
`A
`5,598,534 A
`5,608,910 A
`5,623,604 A
`5,666,293 A
`
`................ 395/650
`8/1995 Filepp etal.
`12/1995 Lisimaque et a1.
`.......... 395/430
`11/1996 Christeson et al.
`.......... 395/652
`......
`
`1/1997 Haas ..........
`. 395/200.09
`
`3/1997 Shimakura .............. 395/670
`
`4/1997 Russell etal.
`395/2001
`
`............... 395/2005
`9/1997 Metz et a1.
`(Continued)
`FOREIGN PATENT DOCUMENTS
`2339923
`3/2000
`
`CA
`
`d
`C t
`( on 1nue )
`OTHER PUBLICATIONS
`“Focus on OpenView A guide to Hewlett-Packard’s Network and
`Systems Management Platform”, Nathan J. Muller, pp. 1-291, CBM
`Books, published 1995.
`
`(21) Appl. No.: 10/797,176
`.
`.
`,
`(22) File(1‘
`Mar 10 2004
`
`(Continued)
`
`Primary ExamineriPierre-Louis Desir
`
`Related US. Application Data
`
`(57)
`
`ABSTRACT
`
`(60) Provisional application No. 60/4 533 13a filed on Mar.
`10a 2003.
`
`(51)
`
`Int. C1.
`(2009.01)
`H04 W 4/00
`(52) US. Cl.
`....................... 455/551; 455/417; 455/419;
`455/418; 455/4141; 455/5501; 709/203;
`717/173; 717/170; 717/171
`(58) Field of Classification Search ................. 455/419,
`455/418, 414.45 420, 451, 417a 5501, 414.1;
`395/662; 709/203; 717/173, 1703 171
`See application file for complete search history.
`
`(56)
`
`References Clted
`US. PATENT DOCUMENTS
`
`Disclosed herein is a network for managing one of a firmware
`update service option and a software update service option in
`electronic devices such as, for example, a mobile handset.
`The network is capable of determining whether a mobile
`handset is capable of facilitating firmware updates based
`upon, for example, firmware update service options (FUSO)
`and associated FUSO numbers. When a new mobile phone is
`used for the first time in the electronic deVice network, an
`OTAPA Process may be employed not only to program num-
`ber assignment module parameters but also for initiating one
`of a firmware or software update or for setting flags and
`parameters that facilitate subsequent firmware or software
`updates. A mobile handset, may periodically or as necessary,
`communicate ability to update firmware and/or software to
`the electronic deVice network.
`
`5,261,055 A
`
`11/1993 Moran et a1.
`
`................ 395/275
`
`30 Claims, 4 Drawing Sheets
`
`321
`
`303
`
`Capability using Prosodol
`
`Capabilily requesi
`
`Muse
`Base Sufism Sends n
`
`General Page Messnge in
`
`Mobile Hondseiwith
`323
`
`Mobile Hsndser responds
`Hrrnwne Updne Service
`
`0iion
`mm sPmtocol Cspswizy
`
`
`Response Message
`
` Bus: SimianVerifies Em Sum. u
`
`
`s Msc,
`325
`Mobile Handmldemhy
`m “E
`, ““3““an
`
`using Sundud
`“pups“ preksseis)
`329
`AudunliufimPmcess
`
`Firmwm Updoie
`Security Code or
`Passwordverified
`- Mobil: Hondsei
`
`
`
`Mobile Hondser Checks
`
`Finnwm Update Service
`Opt—inn
`
`Mesenge i'o
`Subscriber w
`Mobile Handset
`
`Seek lniuoiion
`Responds will. Page
`ow. .are
`
`
`Response Memosacknowledging ruse
`
`
`
`
`Bsse 5min" Transmit:
`cnsnnei Axiom-rein
`
`Mung:
`
`Mobile Handsei moves in
`
`Tnd'fic Channel as
`inns-med
`
`
`1
`
`APPLE 1009
`
`1
`
`APPLE 1009
`
`

`

`US 7,881,745 B1
`
`Page 2
`
`U.S. PATENT DOCUMENTS
`
`.................... 700/234
`10/2002 Bagnordi
`2002/0152005 A1
`10/2002 Peng ...........
`709/217
`2002/0156863 A1
`
`................... 717/178
`10/2002 Anton, Jr.
`2002/0157090 A1
`2/2003 Rajaram et al.
`............. 717/173
`2003/0033599 A1
`2/2003 Hannigan et al.
`..
`707/500
`2003/0037075 A1
`
`.................... 709/245
`3/2003 Nakatani
`2003/0061384 A1
`2003/0186695 A1* 10/2003 Bridges et al.
`.............. 455/432
`2004/0031029 A1*
`2/2004 Lee et al.
`.................... 717/171
`
`FOREIGN PATENT DOCUMENTS
`
`JP
`KR
`KR
`
`8202626
`2002-0034228
`2001-0100328
`
`8/1996
`5/2000
`11/2001
`
`OTHER PUBLICATIONS
`
`“Client Server computing in mobile environments”, J. Jing et al,
`ACM Computing Surveys, vol. 31, Issue 2, pp. 117-159, ACM Press,
`Jul. 1999.
`“ESW4: enhanced scheme for WW computing in wireless com-
`munication environments”, S. Hadjiefthymiades,
`et al, ACM
`SIGCOMM Computer Communication Review, vol. 29, Issue 5, pp.
`24-35, ACM Press, Oct. 1999.
`“Introducing quality-of—service and traffic classes in wireless mobile
`networks”, J. Sevanto, et al, Proceedings ofthe 15’ ACM international
`workshop on Wireless mobile multimedia, pp. 21-29, ACM Press,
`1998.
`“Any Network, Any Terminal, Anywhere”, A. Fasbender et al, IEEE
`Personal Communications, Apr. 1999, pp. 22-30, IEEE Press, 1999.
`TINEINIS-683 -A: Over-the-Air Service Provisioning of Mobile
`Stations in Spread Spectrum Systems; May 1998.
`3GPP2 C.R1001-A 2.0; Administration of Parameter Value Assign-
`ments for cdma2000 Spread Spectrum Standards, Release A; Jul. 14,
`2000.
`
`* cited by examiner
`
`>>>>>>>>>>>>>>>>>>>>>
`
`5,752,039
`5,778,440
`5,790,974
`5,878,256
`5,960,445
`6,009,497
`6,029,065
`6,038,636
`6,047,071
`6,064,814
`6,073,206
`6,073,214
`6,088,759
`6,105,063
`6,112,024
`6,112,197
`6,126,327
`6,128,695
`6,144,849
`6,157,559
`6,163,274
`6,198,946
`6,279,153
`6,311,322
`6,438,585
`6,615,038
`6,725,056
`2001/0029178
`2001/0047363
`2001/0048728
`2002/0028673
`2002/0078209
`2002/0116261
`2002/0131404
`
`*
`
`*
`
`....... 395/712
`Tanimura .............
`5/1998
`. 711/154
`Yiu et al.
`..
`7/1998
`
`8/1998
`. 701/204
`Tognazzini
`
`Bealkowski et al.
`3/1999
`. 395/652
`Tamori et al.
`..
`9/1999
`. 707/203
`
`..
`Wells et al.
`12/1999
`711/103
`
`Shah .............
`2/2000
`. 455/4144
`
`3/2000
`711/103
`Brown, III et al.
`.
`
`Shah .............
`4/2000
`. 380/273
`5/2000
`. 395/701
`
`Capriles et al.
`.
`Piwonka et al.
`6/2000
`.
`. 711/102
`
`Fawcett
`.........
`6/2000
`. 711/133
`
`Hasbun et al.
`7/2000
`. 711/103
`
`8/2000
`. 709/223
`Hayes, Jr.
`
`Almond et al.
`.
`8/2000
`. 395/703
`8/2000
`....... 707/3
`
`Chatterj ee et al.
`10/2000 Bi et a1.
`.. 395/200.51
`
`10/2000 Estakhri et
`.
`.
`711/103
`
`* 11/2000 Nodoushani et al.
`. 455/419
`
`12/2000 Yoo .................
`........ 365/52
`340/825.44
`12/2000 Lindgren .
`
`3/2001 Shin et a1.
`.
`455/561
`8/2001 Bi et a1.
`717/11
`
`10/2001 Ikeda et al.
`..
`717/1
`
`8/2002 Mousseau et al.
`. 709/206
`9/2003 Moles et al.
`.
`. 455/418
`
`4/2004 Moles et al.
`.
`. 455/524
`
`10/2001 Criss et al.
`455/419
`707/1041
`
`11/2001 Peng
`375/354
`12/2001 Peng ..........
`
`455/419
`.
`3/2002 Chang et a1.
`
`. 709/227
`6/2002 Peng ................
`8/2002 Moskowitz et al.
`705/14
`
`9/2002 Mehta et a1.
`.........
`....... 370/352
`
`B1
`B1
`B1
`B2
`B1 *
`B1 *
`A1
`A1
`A1
`A1*
`A1
`A1
`A1
`
`2
`
`

`

`US. Patent
`
`Feb. 1, 2011
`
`Sheet 1 014
`
`US 7,881,745 B1
`
`105
`
`Applications
`
`139
`
`137
`
`135
`
`133
`
`131
`
`129
`
`107
`
`
`
`111
`
`
`
`41
`
`I Provisioning I
`I
`Server
`I
`V _ _
`143
`
`3
`
`

`

`US. Patent
`
`Feb. 1, 2011
`
`Sheet 2 014
`
`US 7,881,745 B1
`
`
`
`Figure 2
`
`4
`
`

`

`U.S. Patent
`
`Feb. 1, 2011
`
`Sheet 3 of 4
`
`US 7,881,745 B1
`
`307
`
`Base Station Sends a
`
`0 tion
`
`General Page Message to
`Mobile Handset with
`
`Firmware Update Service
`
`309
`
`Base Station Verifies
`
`Mobile Handset Identity
`using Standard
`Authentication Process
`
`
`
`
`
`Base Station checks
`Mobile Handset 's FOTA
`
`Messa e
`
`Capability using Protocol
`Capability request
`
`321
`
`303
`
`
`
`Mobile Handset responds
`with a Protocol Capability
`
`
`Response Message,
`
`323
`
`
`Base Station updates MSC,
`etc., determines availability
`
`of Update package(s)
`
`
`
`
`
`
`325
`I
`
`329
`
`311
`
`Yes
`
`Mobile Handset Checks
`
`
`Firmware Update Service
`
`Option
`
`No
`
`313
`
`®
`
`Firmware Update
`
`Security Code or
`
`Password verified
`b Mobile Handset
`
`Download
`Update
`
`Package and
`
`Saved in NV
`Memory
`
`
`
`
`Message To
`Subscriber to
`of U date
`Seek Initiation
`
`
`
`
`339
`
`N°
`
`
`
`31 5
`
`Yes
`
`Mobile Handset
`
`
`Responds with Page
`Response Message
`acknowledging FUSO
`
`317
`
`Base station Transmits
`
`Channel Assignment
`Message
`
`
`
`
`31 9
`
`
`
`Mobile Handset moves to
`Traffic Channel as
`instructed
`
`
`
`
`
`
`Register with Network
`
`337
`
`343
`
`Normal Usage
`
`End
`
`345
`
`Figure 3
`
`5
`
`

`

`US. Patent
`
`Feb. 1, 2011
`
`Sheet 4 014
`
`US 7,881,745 B1
`
`403
`
`
`
`Mobile Handset's
`
`communicates FOTA
`
`Capability to Base Station
`
`409 Base Station Gathers Mobile
`
`Handset details, Updates
`
`MSC, customer care, etc.
`
`411
`
`Base Station determines
`availability of Update
`
`package(s)
`
`Download
`
`Update
`Package and
`, Saved in NV .
`
`Memory
`
`
`
` Message To
`
`Subscriber to
`
`Seek Initiation
`of U date
`
`
`
`
`Figure 4
`
`6
`
`

`

`US 7,881,745 B1
`
`1
`ELECTRONIC DEVICE NETWORK
`EMPLOYING PROVISIONING TECHNIQUES
`TO UPDATE FIRMWARE AND/OR
`SOFTWARE IN ELECTRONIC DEVICES
`
`CROSS-REFERENCE TO OTHER
`APPLICATIONS
`
`The present application claims the benefit of priority of
`US. Provisional Patent Application having Ser. No. 60/453,
`313, filed on Mar. 10, 2003, and hereby incorporates herein by
`reference the complete subject matter thereof, in its entirety.
`The present application also hereby incorporates herein by
`reference the complete subject matter of PCT Application
`having publication number WO/02/41147 A1, and having
`application number PCT/USOl/44034, filed on Nov. 19,
`2001, in its entirety.
`
`FEDERALLY SPONSORED RESEARCH OR
`DEVELOPMENT
`
`[Not Applicable]
`
`MICROFICHE/COPYRIGHT REFERENCE
`
`[Not Applicable]
`
`BACKGROUND OF THE INVENTION
`
`Electronic devices, such as mobile phones and personal
`digital assistants (PDA’s), often contain firmware and appli-
`cation software that are either provided by the manufacturers
`of the electronic devices, by telecommunication carriers, or
`by third parties. These firmware and application software
`often contain software bugs. New versions of the firmware
`and software are periodically released to fix the bugs, intro-
`duce new features, or both. Electronic devices, such as for
`example, mobile handsets, access servers to retrieve updates
`that may be needed to update firmware and/or software.
`Further limitations and disadvantages of conventional and
`traditional approaches will become apparent to one of skill in
`the art,
`through comparison of such systems with some
`aspects ofthe present invention as set forth in the remainder of
`the present application with reference to the drawings
`appended hereto.
`
`SUMMARY OF THE INVENTION
`
`2
`
`In an embodiment according to the present invention, the
`service broker may comprise a software component in the
`electronic device.
`
`In an embodiment according to the present invention, one
`of the plurality of servers may comprise a download server
`capable of receiving a request for an update package. The
`download server may be capable of sending the requested
`update package to one of the plurality of software compo-
`nents in the electronic device.
`
`In an embodiment according to the present invention, the
`update package may comprise a set of executable instructions
`for converting a first version of a software component to a
`second version of the software component.
`In an embodiment according to the present invention, the
`service broker may forward the update package to at least one
`of the plurality of software components in the electronic
`device.
`
`In an embodiment according to the present invention, one
`of the plurality of software applications in the electronic
`device may comprise an update agent capable of processing
`an update package. The update agent may be capable ofbeing
`invoked by the service broker when an update package is
`communicated to the electronic device.
`
`In an embodiment according to the present invention, the
`update package may comprise a set of executable instructions
`for converting a first version of a software component to a
`second version of the software component.
`In an embodiment according to the present invention, the at
`least one request for service may comprise an asynchronous
`request and the service broker may be capable of communi-
`cating a response received from one ofthe plurality of servers
`back to the one of the plurality of software components.
`In an embodiment according to the present invention, the at
`least one request for service may comprise an asynchronous
`request for one of the plurality of software components reg-
`isters callback information from the service broker. The ser-
`
`vice broker may communicate a response received from one
`of the plurality of servers back to the one of the plurality of
`software applications based upon the registered callback
`information.
`
`In an embodiment according to the present invention, the
`service broker may be a server communicatively coupled to
`the electronic device.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`50
`
`In an embodiment according to the present invention, the
`5 service broker server may determine which one of the plural-
`ity of servers is available and capable ofprocessing the at least
`one service request, and subsequently may forward the
`request to the determined one of the plurality of servers.
`In an embodiment according to the present invention, the
`determined one of the plurality of servers may be forwarded
`the at least one request for processing, and a response from the
`determined one of the plurality of servers may be forwarded
`to the one of the plurality of software components.
`In an embodiment according to the present invention, the
`determined one of the plurality of servers may process the at
`least one service request. The at least one service request may
`comprise a request for a software update from the one of the
`plurality of software components and may retrieve an update
`package and associated information and may communicate
`the update package and associated information to the elec-
`tronic device.
`
`55
`
`Aspects ofthe present invention may be found in a network
`facilitating interactions between one of a plurality of software
`components in a electronic device and an associated one of a
`plurality of servers in the network. The network may com-
`prise a service broker capable ofreceiving at least one request
`for service associated with one of the plurality of software
`components. The service broker may be capable of determin-
`ing one of the plurality of servers associated with one of the
`plurality of software components, based upon at least one
`request for service. The service broker may also be capable of 60
`forwarding the at least one request for service to a determined
`one of the plurality servers.
`In an embodiment according to the present invention, the
`network the service broker may be capable of selectively
`communicating a response from the determined one of the
`plurality of servers to one of the plurality of software com-
`ponents in the electronic device.
`
`65
`
`In an embodiment according to the present invention, the
`plurality of software components may comprise a download
`agent and an update agent. The download agent may be
`capable of requesting a software update from the service
`broker server and receiving in response an update package
`from the service broker server. The update agent may be
`
`7
`
`

`

`US 7,881,745 B1
`
`3
`capable of processing the received update package for updat-
`ing at least one of firmware and software in the electronic
`device.
`
`In an embodiment according to the present invention, a
`wireless network mat support at least one electronic device.
`The network may comprise a service broker, a plurality of
`service providers, wherein each of the plurality of service
`providers may be communicatively coupled to the service
`broker and a client-side component in the electronic device
`requesting a software update from one of the plurality of
`service providers. The service broker may determine an
`appropriate one of the plurality of service providers capable
`of responding to the software update request.
`In an embodiment according to the present invention, the
`wireless network may further comprise a generic intelligent
`responsive agent in the electronic device. The generic intel-
`ligent responsive agent may be communicatively coupled to
`the service broker. The generic intelligent responsive agent
`may be capable ofestablishing a communication link with the
`service broker server and may also be capable of forwarding
`the software update request and associated information from
`the client-side component to the service broker. The service
`broker server may determine one of the plurality of service
`providers as a target server capable ofprocessing the software
`update request and forwarding the software update request to
`the target server.
`In an embodiment according to the present invention, the
`target server may process the received software update
`request, retrieve an appropriate update package and associ-
`ated information, and communicate the appropriate update
`package and associated information back to the generic intel-
`ligent responsive agent for subsequent communication to an
`associated client-side component.
`In an embodiment according to the present invention, the
`generic intelligent responsive agent may act as a proxy for the
`client-side component and provide one ofasynchronous com-
`munication and synchronous communication facilities for
`interactions with the target server.
`In an embodiment according to the present invention, the
`electronic device may further comprise a registration client
`capable ofmaintaining a plurality ofregi stration entries. Each
`registration entry may be associated with a client-side soft-
`ware component, and each entry may also comprise at least
`one of a name, version, plurality of dependencies, status
`specifying a current operational status, plurality of callback
`functions, an associated parameter, an event, and a return
`type. Each registration entry may also comprise a set of con-
`figuration parameters and a client-side software component
`specific update agent capable of updating at least one of the
`set of configuration parameters and the client-side software
`component. Each registration entry may also comprise a
`server URL specifying a service provider and associated rel-
`evant information.
`
`In an embodiment according to the present invention, the
`electronic device may further comprise security information.
`Aspects of the present invention may also be found in a
`method for updating at least one of a software component and
`software component configuration information in a electronic
`device communicatively coupled to a service broker. The
`method may comprise registering at least one call-back func-
`tion available in the software component under the control of
`the electronic device. The method may also comprise com-
`municating a request for updating of at least one of the soft-
`ware component and software component configuration to
`the service broker. The method may also comprise receiving
`results from a remote service provider and invoking the at
`least one call-back function using the received results. The
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`
`method may also comprise receiving an update request under
`the control of the service broker, determining a service pro-
`vider based upon the update request, invoking update func-
`tionality on the determined service provider, and transmitting
`results of the invoked update functionality to the electronic
`device.
`
`In an embodiment according to the present invention, the
`received results may be communicated to an update agent
`capable of updating the at least one of the software compo-
`nent and software component configuration under the control
`of the electronic device.
`
`In an embodiment according to the present invention, a
`request may be communicated by the software component to
`a generic intelligent responsive agent under the control ofthe
`electronic device. The request may comprise a command to
`be invoked on a remote service provider and parameters to be
`passed thereto. The request may be communicated to the
`service broker and the received results may be communicated
`to the software component. An update request may be
`received and based upon the update request a service provider
`may be determined. The update functionality may be invoked
`on the determined service provider and results of the invoked
`update functionality may be transmitted to the generic intel-
`ligent responsive agent.
`These and various other advantages and features ofnovelty
`which may characterize the invention are pointed out with
`particularity in the claims annexed hereto and that form a part
`hereof. However, for a better understanding of the invention,
`its advantages, and the objects obtained by its use, reference
`should be made to the drawings which form a further part
`hereof, and to accompanying descriptive matter, in which
`there are illustrated and described specific examples of an
`apparatus in accordance with the invention.
`
`BRIEF DESCRIPTION OF SEVERAL VIEWS OF
`THE DRAWINGS
`
`FIG. 1 is a block diagram illustrating an electronic device
`network capable of provisioning firmware updates to a plu-
`rality ofelectronic devices according to an embodiment ofthe
`present invention;
`FIG. 2 is a block diagram illustrating an electronic device
`network employing a general page message according to an
`embodiment of the present invention;
`FIG. 3 is a flow chart illustrating an exemplary operation of
`an electronic device network according to an embodiment of
`the present invention; and
`FIG. 4 is a flow chart illustrating an exemplary operation of
`an electronic device network according to an embodiment of
`the present invention.
`
`DETAILED DESCRIPTION OF THE INVENTION
`
`Electronic devices may be adapted to access servers to
`retrieve updates for updating at least one of firmware and
`software. An electronic device may be, for example, a mobile
`electronic device having software/firmware, such as, mobile
`cellular phone handsets, personal digital assistants (PDA’s),
`pagers, MP3 players, digital cameras, etc. An update may
`comprise firmware and software updates that modify or
`change the version of a particular firmware or software
`installed in the electronic device, for example, upgrading to a
`newer version, repairing a bug in the firmware/software, etc.
`An update may also add new services to the electronic device
`or delete services, as desired by a service provider, device
`manufacturer, or an end-user.
`
`8
`
`

`

`US 7,881,745 B1
`
`5
`An electronic device requesting access to a server may
`transmit an access request to the network using a first type of
`communication and the network may respond using the same
`type of communication. Alternatively, the electronic device
`may transmit an access request to the network using a first
`type of communication and the network may respond using a
`different type of communication. For example, the electronic
`device may transmit a request to the network using a short
`message service (SMS) and the network may respond to the
`request using a circuit switched or packet switched commu-
`nication service, or the reverse may occur.
`Aspects ofthe present invention may be found in a wireless
`electronic device network adapted to determine whether indi-
`vidual electronic devices may be updated. In an embodiment
`according to the present invention, the wireless electronic
`device network may be adapted to facilitate downloading of
`update packages by an electronic device. In order to change
`specific parameters in an electronic device, the electronic
`device may be either physically connected to a system
`adapted to change such parameters, or alternatively, the elec-
`tronic device may be manually modified by an end-user as
`desired.
`
`In an embodiment according to the present invention, a
`wireless electronic device network may be adapted to change
`specific parameters ofthe electronic device via wireless com-
`munication. Wireless communication may also be referred to
`as Over-The-Air Parameter Administration (OTAPA).
`OTAPA is disclosed in IS-725-A, pages 1-78, published Apr.
`13, 1999 and PCT Application number WO 98/41044 by
`Northern Telecom® Inc., the entirety of the respective docu-
`ments incorporated herein in their respective entireties.
`According to the publication IS-725-A, an authentication
`procedure for accessing a communication network may be
`included in the OTAPA process. However, an authentication
`procedure for accessing a wireless electronic device served
`by such a network may not be provided. Updating firmware in
`particular electronic devices may also not be covered by
`OTAPA specifications or by other similar specifications. Reli-
`ability in updating firmware of electronic devices presents at
`least one major shortcoming of over the air related specifica-
`tions.
`
`An OTAPA-based mechanism for setting or changing
`parameters of an electronic device, has been disclosed by
`Nokia® in US. Pat. No. 6,047,071 (Nokia) issued onApr. 4,
`2000. However, the Nokia patent does not suggest or disclose
`techniques to update firmware in electronic devices. The
`Parameter Administration Service Option (PASO) concept
`and other related concepts require significant enhancement to
`support firmware update in electronic devices.
`FIG. 1 is a block diagram illustrating an electronic device
`network 105 capable of provisioning firmware updates to a
`plurality of wireless electronic devices, such as for example,
`mobile handset 107 according to an embodiment of the
`present invention.
`FIG. 1 illustrates an electronic device network 105 capable
`of provisioning firmware updates to a plurality of electronic
`devices, such as for example, mobile handset 107, wherein
`the mobile handsets may be communicatively coupled to one
`of a plurality of device servers 119 via a Mobile Switching
`Center (MSC) 111 and one ofa plurality ofbase stations, such
`as a base station 109. The device server 119 may be capable of
`dispensing update packages, which may be employed to
`update firmware in the plurality of mobile handsets during a
`provisioning process. The update package may be dispensed
`to the mobile handset 107 based upon characteristics of, for
`example, the individual mobile handset 107 or subscriber
`using mobile handset 107.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`The mobile handset 107 may comprise an update agent
`capable ofupdating firmware, software applications, etc. The
`mobile handset may also comprise a download agent 133, a
`device server 119, a random access memory (RAM) 145,
`firmware 135, operating system 137, applications 139, down-
`loaded update package 149, Number Assignment Module
`(NAM) 147, upload agent 131, and an update application
`(UA) loader 129. The download agent 133 may be capable of
`downloading update packages from external systems, such as
`device server 119, for example. The elements ofmobile hand-
`set 107, illustrated in FIG. 1, may be provisioned by the
`electronic device network 105 when the mobile handset 107
`
`is initially set-up and operated.
`The MSC 111 is a network element that may be responsible
`for the actual circuit switched connection of the voice chan-
`
`nels. The MSC 111 generally makes very few routing deci-
`sions, obtaining the routing decisions ordinarily from the
`Service Control Point (SCP) applications. The MSC 111 may
`make some basic routing decisions. The Home Location Reg-
`ister (HLR) 115 may act as a central repository of profiles for
`each electronic device, e.g., mobile handset 107, and main-
`tain current network location and status of the electronic
`
`device. TheVisitor Location Register (VLR) 113 is a database
`that may be located within the MSC 111 and may contain a
`temporary copy of electronic device profiles obtained from
`the HLR 115. The VLR 113 may also be stored in close
`proximity, either physically or logically, to the HLR 115 in
`order to improve device performance.
`The electronic device, for example mobile handset 107,
`and base station 109 may communicate via particular radio
`frequencies mandated by appropriate regulatory bodies.
`Dedicated trunk lines may serve as links between the base
`station 109 and the MSC 111. Alternatively, an interface
`between MSC’s within the same system (same cellular car-
`rier) and the base stations may be provided by dedicated land
`lines. Data links may connect the MSC 111 to VLR 113, and
`also to HLR 115. The HLR 115 may be located at the MSC
`111 or at a remote location. Each HLR 115 may serve more
`than one MSC, for example MSC 111. The VLR 113, how-
`ever, may be dedicated to the MSC 111 that is currently in
`control of and communicating with the electronic device, for
`example, mobile handset 107. The VLR 113 is normally
`located at the MSC 111. The HLR 115 may be located
`remotely therefrom.
`A subscriber record, created when the MSC 111 is han-
`dling the mobile handset 107, may be erased when the mobile
`handset 107 is no longer active or has moved to the region
`controlled by another MSC. The HLR 115 is a location reg-
`ister and may contain user identity information, such as,
`directory number, profile information (feature list),
`last
`known network location, and validation period. The VLR 1 13
`may also comprise another location register in which the
`MSC 111 may temporarily store and retrieve information
`regarding visiting subscribers or users. A difference between
`the VLR 113 and the HLR 115 may be that the HLR 115 may
`comprise a central storage place for subscriber records,
`whereas the VLR 113 may comprise a temporary storage
`place that may be used during a configurable period of time.
`Using the VLR 113 may reduce the amount of network sig-
`naling required to process call handling.
`To perform Over-The-Air Parameter Administration
`(OTAPA), various functions may be implemented in each
`electronic device, for example, mobile handset 107, and each
`element of a wireless communication network. The mobile
`
`handset 107 and the electronic device network 105 may have
`a capacity to internally generate a random number when
`necessary, and may also store a secret key (A_KEY), as well
`
`9
`
`

`

`US 7,881,745 B1
`
`8
`In one related embodiment, the electronic device network
`105 may possess means for determining whether the mobile
`handset 107 is OTAPA capable. The base station 109 may, for
`example, page the mobile handsets 107, (i.e., send a General
`Page Message to the mobile handset 107), using the PASO
`number. After verifying the message identity using standard
`Authentication processes,
`if the mobile handset 107 is
`OTAPA capable, the mobile handset set may respond with a
`Page Response Message, indicating support for PASO by
`sending the PASO number. Ifthe mobile handset 107 does not
`support PASO, the response may indicate that the option is
`unavailable.
`PASO enables determination of whether the mobile hand-
`
`set 107 supports NAM 147 programming, as well as firmware
`updating. Once PASO capability/support is confirmed, the
`base station 109 may transmit a Channel Assignment Mes-
`sage, enabling the mobile handset 107 to activate a Traffic
`Channel.
`
`For security reasons, Signaling Message Encryption
`(SME) may be used in a Channel Assignment Message. Use
`of encryption may be enforced. Where encryption is optional,
`if the encryption mode is not enabled, the mobile handset 107
`may enter into a Service Negotiation process on the Traffic
`Channel and may request another service option, indicating
`that PASO is not supported. Alternatively, the mobile handset
`107 may terminate the call according to a Call Release Pro-
`cedure.
`Once the mobile handset 107 has activated the Traffic
`
`10
`
`15
`
`20
`
`25
`
`30
`
`Channel, an OTASP Data Message may be sent containing a
`Parameter Change Code (PCC). If the PCC received by the
`mobile handset 107 matches the PCC for the mobile handset
`
`7
`as, shared secret data (SSD). The A_KEY may comprise a 64
`bit pattern stored in a mobile handset 107 and in one of HLR
`115 or an authentication center. The A_KEY may be used to
`generate or update the electronic device’s SSD, which may be
`a 128 bit pattern stored in the electronic device, and may also
`be known by the base station 109. The HLR 115 may indicate
`whether an electronic device supports the OTAPA function.
`In an embodiment according to the present invention, the
`OTAPA-related activity supported by the electronic device
`network 105 may also implement updating of firmware in
`electronic devices based upon a firmware update service
`option (FUSO) that may be accessible by OTAPA-related
`functions in the electronic device network 105. The FUSO,
`for example, may be set-up or loaded into the mobile handset
`107 by the manufacturer when programming (i.e., flashing)
`the mobile handset 107.
`
`In an embodiment according to the present invention an
`aspect ofthe invention may be found in a means for providing
`network-initiated over-the-air access to mobile station 107
`
`firmware update service option and firmware update service
`functions (based upon update agent 131) while initializing (or
`updating) the NumberAssignment Module (NAM) 147 in the
`mobile handset 107, without requiring us