TOYA AAA
`
`US 20030084177A1
`
`as United States
`a2) Patent Application Publication co) Pub. No.: US 2003/0084177 A1
`
` Mulligan (43) Pub. Date: May1, 2003
`
`
`(54) MOBILE CLIENT PROVISIONING WEB
`SERVICE
`
`(52) US. Cheeeneeesteseeeennees 709/230; 709/203
`
`(75)
`
`Inventor: Michael Mulligan, Tampere (FI)
`
`(57)
`
`ABSTRACT
`
`Correspondence Address:
`Steven R. Funk
`Crawford PLLC
`.
`Suite 390
`1270 Northland Drive
`St. Paul, MN 55120 (US)
`
`(73) Assignee: Nokia Corporation, Espoo (FI)
`
`(21) Appl. No.:
`(22)
`Filed:
`
`10/036,058
`Oct. 26, 2001
`Publication Classification
`
`(SV)
`
`Tint, C07 ieeeeeeeseeesccceeennnnteeeeeeceeccecnnee GO6F 15/16
`
`A system and method for provisioning mobile clicnts on a
`network for use of network service applications via a
`we
`:
`.
`toa
`provisioning Web service. At least one mobile terminal is
`4s
`1.
`coupled to at least one network service via the mobile client
`provisioning Web service. The provisioning Web service
`providesa single pointof interface to the network service for
`provisioning the mobile terminal. The mobile terminal is
`provisioned by the provisioning Web service for use of at
`least one application provided by the network services
`where the provisioning includes at
`least configuring the
`mobile terminal for use of the application, and delivering the
`application to the mobile terminal.
`
`
`
` TERMINAL
`MANAGEMENTSERVICE
`
`616
`
`
`PRESENCE
`SERVICE
`
`600
`604
`
`SERVICE
`
`
`
`LOGIC
`
`
`610
`
`
`NOTIFICATIONS
`
`SERVICE ~-
`
`
`oo
`
`DELIVERY
`
`SERVICE
`
`612
`
`
`
`
`Roku Exhibit 1006
`Roku Exhibit 1006
`Roku v. Videolabs
`Roku v. Videolabs
`
`

`

`Patent Application Publication May 1,2003 Sheet 1 of 6
`
`US 2003/0084177 Al
`
`100
`
`
`
`MOBILE CLIENT
`
`
`
`PROVISIONING WEB
`APPLICATION
`
`SERVICE
`
`
`106
`
`FIG. 1
`
`202
`
`200
`
`“A
`
`
`
`
`
`
`MOBILE CLIENT
`PROVISIONING
`WEB
`SERVICE
`
`APPLICATION
`
`FIG, 2
`
`

`

`Patent Application Publication May 1,2003 Sheet 2 of 6
`
`US 2003/0084177 Al
`
`300
`
`\ P
`
`
`
` TERMINAL
`
`MANAGEMENT
`SERVICE
`
`
`RESENCE
`SERVICE
`
`
`
`
`
`NOTIFICATION
`SERVICE
`
`
`DELIVERY
`
`SERVICE
`
`
`FIG. 3
`
`

`

`Patent Application Publication
`
`May1, 2003 Sheet3 of6
`
`US 2003/0084177 Al
`
`
`
`
`
`SYSLAWVaVdSSAODOVVLVd
`
`:ozy8?Pogre
`
`ClV
`
`a|d|oo|WNIWYAL
`
`
`
`INSANOdWO9SOIAYSSGSM
`
`NOLLVNITYOOD
`
`bOIA
`
`OLY AYLSIDSY
`
`OLY
`
`
`
`
`
`SASSAYGVLOsardoVLVA
`
`WX
`
`ONIDVSSAN
`
`ANIONS
`
`dllH
`
`YsAdas
`
`80
`
`
`
`©:LNIOdGNASSOIANASGM
`
`O0v
`
`TasMviadn
`
`SOIANAS
`
`
`
`

`

`Patent Application Publication
`
`May1, 2003 Sheet4 of 6
`
`US 2003/0084177 Al
`
`
`
`ADCSMYOMLAN
`
`AHOVO
`
`00S
`
`Z0S
`
`» hes
`
`AYVdWOD
`
`+80E:
`chyco7
`
`
`*NOLLVNINYSL30
`
`LNVYVALOAPaOVLC
`
`
`
`TWNINYSLLOArad
`
`FdALLNVINYA
`
`viva
`
`clSOLS
`
`SOIAYAS
`
`JONSASSMdNOILVONdd¥
`
`
`
`AMAA|
`
`§DOA
`
`
`
`
`
`LOsraoVLVdv0S
`
`
`
`
`
`
`
`

`

`
`US 2003/0084177 Al
`
` May 1, 2003 Sheet5of 6Patent Application Publication
`
`JOIAYAS
`
`91907
`
`O19
`
`
`
`JOIANASLNANS9DVNVA
`
`TWNIWYSL
`
`919
`
`JONAS
`
`AOINNAS
`
`09
`
`SNOLLVOISLLON
`
`
`
`70-.FOINMAS
`
`AMSANSC
`
`JOINYAS
`
`z19
`
`9DTA
`
`
`
`
`
`
`
`

`

`Patent Application Publication May 1,2003 Sheet 6 of 6
`
`US 2003/0084177 A1
`
`
`MOBILE TERMINAL(S) CONNECTS TO NETWORK AND
`ATTEMPTS TO ACCESS APPLICATION(S) PROVIDED BY
`NETWORK SERVICE(S)
`
` 700
`
`
`704
` USE
`
`
`| APPLICATION(S)
`
`
`
` MOBILE TERMINAL(S)
`
`PROVISIONED FOR USE OF
`APPLICATION(S)?
`
`NO|
`
`‘a 706
`
`INTERFACE MOBILE TERMINAL(S) TO NETWORK
`SERVICE(S) VIA PROVISIONING WEB SERVICE, THE
`PROVISIONING WEB SERVICE PROVIDING A SINGLE
`POINT OF INTERFACE TO THE NETWORK SERVICE FOR
`PROVISIONING THE MOBILE TERMINAL
`
`PROVISION THE MOBILE TERMINAL(S) AT THE PROVISIONING
`WEB SERVICE FOR USE OF AN APPLICATION(S) PROVIDED BY
`THE NETWORKSERVICE(S)
`
`APPLICATION(S)
`
`710
`
`CONFIGURE MOBILE
`TERMINAL(S) SETTINGS
`FOR USE OF
`
`DELIVER APPLICATION(S)
`TO MOBILE TERMINAL(S)
`
`FIG. 7
`
`

`

`US 2003/0084177 Al
`
`May 1, 2003
`
`MOBILE CLIENT PROVISIONING WEB SERVICE
`
`FIELD OF THE INVENTION
`
`[0001] The present invention relates generally to network
`communications systems, and more particularly, to a system
`and methodfor provisioning mobile clients on a network via
`a provisioning Web service.
`
`BACKGROUND OF THE INVENTION
`
`[0002] The modern communicationsera has brought about
`a tremendous expansion of wireline and wireless networks.
`Computer networks,
`television networks, and telephony
`networks are experiencing an unprecedented technological
`expansion,
`fueled by consumer demand. Wireless and
`mobile networking technologies have addressed related con-
`sumer demands, while providing moreflexibility and imme-
`diacy of information transfer.
`
`[0003] Current and future networking technologies con-
`tinue to facilitate ease of information transfer and conve-
`nience to users. ‘The proliferation of local, regional, and
`global networks such as the Internet has availed a sea of
`information to society. These networking technologies have
`expanded to increasingly include wireless and mobile tech-
`nologies. Through these networks,
`information can be
`downloaded to desktop systems, wircless systems, mobile
`systems, etc. For example,
`information available via the
`Internet can now be downloaded onto mobile wireless units,
`such as cellular
`telephones, personal digital assistants
`(PDAs), laptop computers, etc. One such technologyfacili-
`tating the transfer of Internet content to and from wireless
`devices is the Wireless Application Protocol (WAP), which
`integrates the Internet and other networks with wireless
`network platforms. Generally, WAP is a set of protocols that
`accounts for characteristics and functionality of both Inter-
`net standards and standards for wireless services.
`It
`is
`independent of wireless network standards, and is designed
`as an open standard. WAP bridges the gap between the
`wireline Internet paradigm and the wireless domain, to allow
`wireless device users to enjoy the benefits of the Internet
`across both platforms.
`
`[0004] Second generation wireless service, often referred
`to as 2G wireless service, is a current wireless service based
`on circuit-switched technology. 2G systems, such as Global
`System for Mobile communications (GSM) and Personal
`Communications Services (PCS), use digital radio technol-
`ogy for improved quality and a broader range of services
`over first generation mobile technologies. 3G, or
`third
`generation, refers to a set of digital technologies that prom-
`ises improvements in capacity, speed and efficiency by
`deploying new packet-based transmission methodologies
`between terminals and the network. Users of 3G devices and
`networks will have access to multimedia services such as
`
`video-on-demand, video conferencing, fast web access and
`file transfer. Existing and future services are, and will
`continue to be, provided by network service operators who
`make services and applications available to mobile device
`users via the network.
`
`[0005] With the introduction of new mobile services such
`as WAP, Multimedia Messaging Service (MMS), calendar
`and contact synchronization, as well as a multitude of other
`possibilities, the number of servers and portals providing
`services for mobile Internet terminals continues to expand.
`
`Further, there is an increasing numberof features associated
`with these services, such as support for multimedia, loca-
`tion-based services, electronic payments, etc. Thus, new
`terminals supporting new network technologies and mobile
`Internet services will continuously be taken into use, often
`as replacement devices for existing subscribers. The new
`terminals will increasingly require newor updated configu-
`ration settings before they can successfully connect to the
`network servers that offer applications over the network.
`
`[0006] However, mobile terminals are by nature limited
`devices. Theytypically have limited memory, storage, and
`processing, capabilities. Therefore, mobile devices do not
`include all of the components required to access new or
`upgraded services that may be available on the network.
`When a mobile user wants to utilize new services available
`
`on the network, the terminal must be configured to use those
`new services. Configuring a terminal to use a service on a
`network is generally referred to as “provisioning” the ter-
`minal. Provisioning may be performed upon initial setup of
`a mobile device, or may also be performed to upgrade
`services and applications already being used at that mobile
`device.
`
`[0007] One traditional provisioning methodology in use
`today requires that a retail establishment provision the
`terminal for the user. This, however, is inconvenient for the
`user. Further, if the user decided to purchase a different
`terminal or upgrade services, the user is forced to return to
`the dealer to provision, or re-provision the terminal. More
`recent and advanced provisioning systems have madeit
`possible to allow the user to initiate provisioning from the
`device. For example, a user may manually initiate provi-
`sioning from the device to be provisioned. Further, remote
`servers may instigate a communications session with a
`provisioning server device, and provide the provisioning
`server with provisioning information. For example,
`two
`existing standards for remote configuration of terminals are
`the WAP provisioning protocol and the SyncML device
`management protocol. However, both of these standards
`assume that components required to be configured are
`already cxisting on the mobile terminal. Other systems focus
`solely on the delivery of data objects to the mobile terminal.
`
`[0008] Existing methodologies for provisioning mobile
`terminals thus currently involve multiple actions and mul-
`tiple interfaces to the network service providing the appli-
`cation. This complicates provisioning, particularly where
`new service and utility network elements increasingly pro-
`liferate the networks.
`
`[0009] Accordingly, there is a need in the network com-
`munications industry to unify various provisioning proce-
`dures in a commonnetwork system, in order to expedite and
`simplify the provisioning procedures for the network ser-
`vices providing applications. The present invention solves
`these and other shortcomings of the prior art, and otters
`numerous advantages over prior art provisioning systems
`and methodologies.
`SUMMARYOF THE INVENTION
`
`[0010] The present invention is directed to a system and
`method for provisioning mobile clients on a network via a
`provisioning Webservice.
`
`In accordance with one embodiment of the inven-
`(0011]
`tion, a methodis provided for provisioning mobile terminals
`
`

`

`US 2003/0084177 Al
`
`May 1, 2003
`
`for use of applications offered by one or more network
`services on a network. The method includesinterfacing at
`least one mobile terminalto at least one network service via
`
`a provisioning Web service. The provisioning Web service
`providesa single pointof interface to the network service for
`provisioning the mobile terminal. The mobile terminal is
`provisioned by the provisioning Web service for use of at
`least one application provided bythe network service, where
`the provisioning includes at least configuring the mobile
`terminal for use of the application, and delivering the
`application to the mobile terminal.
`
`the data object via a push operation, the notification Web
`service delivers to the mobile terminal an addressof the data
`object stored at the delivery Web service.
`
`[0015] The above summaryofthe present invention is not
`intended to describe each illustrated embodiment or imple-
`mentation of the present invention. Thisis the purpose ofthe
`figures and the associated discussion which follows.
`
`BRIEF DESCRIPTION OF ‘THE DRAWINGS
`
`In accordance with another embodiment of the
`(0012]
`invention, a system is provided for provisioning mobile
`terminals for use of applications provided by network ser-
`vice providers on a network. The system includes a Web
`service interface coupled between the mobile terminals to be
`provisioned and the network service providers. The Web
`service interface serves as a single interface to the network
`service providers providing the applications, and serves to
`control
`the provisioning procedures. The system also
`(0019] FIG.3is ablock diagram illustrating an exemplary
`includes a Web service mobile terminal configuration mod-
`ule coupled to the Web service interface, to configure the
`embodimentof a mobile client provisioning Web service in
`accordance with the invention;
`mobile terminals for use of the applications as part of the
`provisioning procedures. A Web service data object delivery
`moduleis also provided, whichis coupled to the Web service
`interface to deliver the applications to successfully config-
`ured mobile terminals as part of the provisioning proce-
`dures.
`
`[0016] The invention is described in connection with the
`embodiments illustrated in the following diagrams.
`
`[0017] FIG. 1 is an exemplary embodiment of a network
`system providing a provisioning interface for controlling a
`provisioning process;
`
`[0018] FIG. 2 illustrates an exemplary embodiment of a
`network system architecture providing a mobile client pro-
`visioning Webservice in accordance with the present inven-
`tion;
`
`[0020] FIG. 4 is a block diagram of a more particular
`embodiment of a service logic module in accordance with
`the present invention;
`
`{0021] FIG. 5 is a block diagram of a more particular
`embodiment of a delivery service module in accordance
`with the present invention;
`
`FIG.6 is a block diagram of an exemplary provi-
`[0022]
`sioning procedure carried out in accordance with the mobile
`client provisioning Web service in accordance with the
`present invention; and
`
`[0023] FIG. 7 is a flow diagram of one embodimentof a
`method for provisioning mobile terminals using a Web
`service in accordance with the present invention.
`
`DETAILED DESCRIPTION OF THE
`ILLUSTRATED EMBODIMENTS
`
`In the following description of the various embodi-
`[0024]
`ments, reference is made to the accompanying drawings
`which form a part hereof, and in which is shown by way of
`illustration various embodiments in which the invention
`
`may be practiced. It is to be understood that other cmbodi-
`ments may be utilized, and structural and functional modi-
`fications may be made without departing from the scope of
`the present invention.
`
`[0025] The present invention is directed to a system and
`method for provisioning mobile clients on a network via a
`provisioning Web service. The provisioning Web service in
`accordance with the present invention provides a single
`interface to network services wanting to effect provisioning
`procedures for mobile terminals requesting network service
`applications. The provisioning Web service unifies provi-
`sioning procedures, such as configuring mobile terminals
`and delivering requested applications, into a common Web
`service. The provisioning Web service of the present inven-
`tion may be used in connection with network service appli-
`cations employing Web service applications, but is also
`equally applicable to network service applications that do
`not employ Webservice applications.
`
`In accordance with another embodiment of the
`{0013]
`invention, a system is provided for provisioning mobile
`terminals operable on a network. The system includes at
`least one mobile terminal coupled to the network, and at
`least one network service coupled to the network to provide
`an application via the network. A provisioning Web service
`is provided, which is coupled to the mobile terminal and the
`network service to control provisioning of the terminal via
`a single interface to the network service. The provisioning
`Web service carries out the provisioning by configuring
`application use settings on the mobile terminal and deliver-
`ing the application to the mobile terminal.
`
`In accordance with yet another embodimentof the
`(0014]
`invention, a system including a suite of Web services is
`provided to provision a terminal for use of an application on
`a network. The suite of Web services includes a client
`
`provisioning Web service to interface at least one mobile
`terminal to at least one network service. The client provi-
`sioning Web service provides a single point of interface to
`the network service for provisioning the mobile terminal for
`use of the application provided by the network service. A
`terminal management Web service configures application
`use settings on the mobile terminal to enable use of the
`application. A presence Web service connected via the
`network to the mobile terminal receives a terminal type of
`the mobile terminal. A delivery Web service is coupledto the
`presence Webservice to receive the terminal type from the
`presence Web service, and to identify a data object for
`delivery corresponding to the terminal type upon successful
`configuration of the application use settings on the mobile
`terminal. A notification Web service is coupled to the deliv-
`ery Web service to deliver the data object to the mobile
`terminal
`if the terminal
`type indicates that
`the mobile
`terminal is capable of receiving the data object via a push
`operation. If the mobile terminal is not capable of receiving
`
`

`

`US 2003/0084177 Al
`
`May 1, 2003
`
`[0026] FIG.1is an exemplary embodiment of a network
`HTTP aspreviously described,
`in which XML messages
`system 100 which provides a provisioning interface for
`may be communicated. An XML messaging layer, such as
`Simple Object Access Protocol (SOAP) also represents a
`controlling a provisioning process. The invention provides a
`single interface to services desiring to correctly manage and
`core layer of Web services. SOAP is a protocol specification
`configure mobile terminals. For example, a terminal 102 that
`that defines a uniform manner of passing XML-encoded
`is not currently configured for use of an application 104 can
`data, as well as defines a manner to perform RPCs using
`be configured for such use, through a provisioning process.
`HTTPas the underlying communication protocol.
`A provisioning interface 106 manages the provisioning
`process between the application 104 and the terminal 102.
`
`[0027] Provisioning generally refers to activating one or
`more telecommunication services for use on a device, and
`involves programming various network databases with the
`user’s information. It is the creation of an active subscriber
`
`account, or modification of parameters for an existing sub-
`scriber account, to configure the terminal for use with the
`desired service(s). For example, provisioning of a subscriber
`account may include subscriber account registration and
`device activation.
`
`In accordance with an exemplary embodiment of
`[0028]
`the present
`invention,
`the provisioning interface 106 is
`providedin the context of a “Web service.” Web Services are
`network-based (particularly Internet-based) modular appli-
`cations that perform a specific task and conform to a specific
`technical format. Web services are represented by a stack of
`emerging standards that describe a service-oriented, com-
`ponent-based application architecture, collectively provid-
`ing a distributed computing paradigm having a particular
`focus on delivering services across the Internet. Generally,
`Web services are self-contained modular applications that
`can be published in a ready-to-use format,
`located, and
`invoked across the World Wide Web. When a Webserviceis
`deployed, other applications and Webservices can locate
`and invoke the deployed service. They can perform a variety
`of functions, ranging from simple requests to complicated
`business processes.
`
`[0029] Advantageously, Web services are accessed via
`ubiquitous Web protocols and data formats, such as Hyper-
`text Transfer Protocol (HTTP) and Extensible Markup Lan-
`guage (XML). Thus, at present,
`the basic Web service
`platform is XML plus HTTP. XMLis a text-based markup
`language that is currently used extensively for data inter-
`change on the Web. As with HTML,datais identified using
`tags, which are collectively known as “markup”. XML tags
`identify the data, and act as a field name in the program.
`XML is
`a
`language that allows complex interactions
`between clients and services, as well as between compo-
`nents of a composite service, to be expressed. HTTP is an
`application protocol, and more particularly is a set of rules
`for exchangingfiles (text, graphic images, sound,video, and
`other multimediafiles) on a network such as the World Wide
`Web. While the examples set forth herein are generally
`described in connection with XMLand IITTP, it should be
`recognized that this is for illustrative purposes, and current
`and future types of protocols and data formats may also be
`employed.
`
`[0030] More specifically, Web services represent a collec-
`tion of several related technologies, and involve connections
`between at least two applications, such as a remote proce-
`dure call
`(RPC),
`in which queries and responses are
`exchanged in XML over HTTP. Web service technologies
`may be defined in terms of various technology layers. The
`core layers include a transport layer, such as TCP/IP or
`
`layers of the Web services stack
`[0031] Higher level
`include a service discovery layer, which may include tech-
`nologies such as the Web Services Description Language
`(WSDL) and Universal Description, Discovery, and Inte-
`gration (UDDI). WSDLis an XML-based description defin-
`ing how to connect to a particular Web service, and thus
`indicates how service providers arc to describe the basic
`format of Web service requests over different protocols or
`encodings. It is used to describe what a Web service can do,
`where it resides, and how to invoke it. UDDI provides a
`manner in which clients can dynamically locate other Web
`services.
`It represents a set of protocols and a public
`directory for the registration and real-time location of Web
`services and other business processes. UDDI provides a
`manner for Web service providers to register themselves,
`and provides a mannerfor an applicationto find, connectto,
`and interact with a particular Web service.
`
`[0032] Other higher level layers of the Web services stack
`may include a workflow layer. A workflow layer may
`include a technology such as the Web Services Flow Lan-
`guage (WSFL). WSFLis an XMLlanguage for the descrip-
`tion of Web Services compositions. It allows for recursive
`compositions of Web services within others to create more
`complex features built upon existing Web services.
`
`[0033] The aforementioned, and other, technologies, pro-
`tocols, data formats, etc. may be used in employing Web
`services. However, these known technologiesare referenced
`in order to provide exemplary technologies currently avail-
`able in the development and use of Web services. The
`invention thus may utilize these knowntechnologies, butis
`also applicable to other existing and/or future technologies,
`as will be readily apparent to those skilled in the art from an
`understanding of the description provided herein.
`
`In accordance with one embodimentof the inven-
`[0034]
`tion, the provisioning interface 106 of FIG. 1 is a mobile
`clicnt provisioning Web scrvicc. The Web service 106 is
`capable of provisioning mobile clients 102 to use applica-
`tions/services 104 on the Internet/intranet.
`
`(0035] FIG. 2 illustrates an exemplary embodiment of a
`network system architecture 200 providing a mobile client
`provisioning Web service in accordance with the present
`invention. ‘he exemplary embodiment of FIG. 2 includes
`one or more mobile terminals 202, at least one application
`204, and the mobile client provisioning Web service 206.
`These network elements communicate over any one or more
`cooperating wireless and landline networks 208.
`[0036] The wireless terminals 202 mayinclude anytype of
`mobile computing device. For example, the wireless termi-
`nal 202 may represent any of a number of mobile commu-
`nication devices, such asa cellular telephone 210, a personal
`digital assistant (PDA) 212, a notebook or laptop computer
`214, or any other type of terminal represented by device 216.
`An unprovisioned terminal 202 is one that has not undergone
`a configuration of initial device/infrastructure connection
`parameters from a storage location to the terminal.
`
`

`

`US 2003/0084177 Al
`
`May 1, 2003
`
`[0037] The application 204 can be any application that a
`mobile terminal (e.g.,
`terminal 202) wishes to use. The
`application 204 thus may, but need not, be a Web service
`itself. For example, the application 204 may be a Java™
`application which is accessed by a MIDIet on the mobile
`terminal 202. As is known in the art, a MIDIet
`is an
`application that conforms to the MIDP standard. MIDP
`(Mobile Information Device Profile) is a set of Java Appli-
`cation Programming Interfaces (APIs) that define how soft-
`ware applications interface with mobile devices such as
`wireless telephones, pagers, Personal Digital Assistants
`(PDAs), etc. Applications conforming to this standard are
`referred to as MIDIets, which are applications written using
`the MIDP framework that can be stored and operated on a
`mobile device. A variety of other types of applications 204
`capable of using Web service technologies may also be used
`in connection with the invention.
`
`[0038] The mobile client provisioning Web service 206
`serves as an interface for the application(s) 204 to provision
`the terminal(s) 202. The provisioning Web service 206
`providesa single pointof interface to the application(s) 204,
`and manages automatic configuration of the terminals 202,
`including providing the appropriate configurations to the
`terminal as well as providing the appropriate applications to
`the terminal. Thus, in accordance with the invention,
`the
`provisioning service 206 provisions the mobile client 202 on
`behalf of the application 204, resulting in a terminal 202
`provisioned to use the service provided by the application
`204.
`
`type of parameters includes existing parameters on the
`terminal that may require some sort of modification. For
`example, a banking application may require a terminal to
`have Wireless Application Protocol
`(WAP) connectivity
`settings that allow connectivity through the bank’s WAP
`gateway for security reasons.
`
`[0043] The notification service 308 works in conjunction
`with the delivery service 304 to deliver data objects to the
`terminal. In one embodiment, the notification service 308
`can be used as the delivery channel directly to deliver the
`data object to the terminal. This is possible, for example,
`where the terminalis capable of receiving the data object via
`a push channel, such as via Multimedia Messaging Service
`(MMS) messaging. MMSis a standard being defined for use
`in advanced wireless terminals, which allows for non-real-
`time transmission of various kinds of multimedia contents
`
`such as images, audio, video clips, etc. In a second embodi-
`ment, the notification service 308 delivers a notification to
`the terminal indicating an address where the data object can
`be retrieved via a pull channel. The notification service 308
`may provide additional types of notifications in accordance
`with the invention.
`
`[0044] Also part of an exemplary embodiment of the
`mobile client provisioning Web service 300 is a presence
`service 310. The presence service 310 provides information
`to the other services in the system. One primary piece of
`information provided by the presence service 310 is the
`terminal type which is to be provisioned. In one embodi-
`ment, the presence service 310 provides its services to the
`[0039] FIG.3is a block diagram illustrating an exemplary
`delivery service 304, the notification service 308, and the
`embodiment of a mobile client provisioning Web service
`terminal managementservice 306.
`300 in accordance with the invention. The internal architec-
`
`ture of the illustrated Web service 300 includes service logic
`302, a delivery service 304, a terminal management service
`306, a notification service 308, and a presence service 310.
`
`[0040] The service logic 302 provides various functional-
`ity for the mobile client provisioning Web service 300. One
`function is to provide the Web scrviccs endpoint, which
`terminates the Web services protocols. Another function of
`the service logic 302 is to provide the logic that ties the
`components of the Web service 300 together to ultimately
`provide the Web service 300. This includes making use of
`the component services,
`in the appropriate sequence,
`to
`ensure that the mobile terminal is correctly provisioned.
`
`[0041] The delivery service 304 is responsible for ensur-
`ing the correct delivery of objects required by the mobile
`terminal to access the application for which the provisioning
`is taking place. Various functions are associated with this
`task. A first function includes determining the correct variant
`of the data object to deliver, based on the type of the mobile
`terminal. Another function includes delivering the data
`object to the terminal, and provides for various delivery
`options including push delivery, pull delivery, etc. The
`delivery service 304 may also provide network edge caching
`facilities for the mobile terminal
`in connection with the
`delivery of the data objects.
`
`[0042] The terminal managementservice 306 is respon-
`sible for remotely configuring parameters in the terminal in
`order to allow it to access the application. These parameters
`may be of multiple varieties. For example, a first type of
`parameters includes those parameters associated with any
`data objects delivered by the delivery service 304. A second
`
`[0045] FIG. 4 is a block diagram of a more particular
`embodiment of a service logic module 400 in accordance
`with the present invention. In the illustrated embodiment,
`the service logic module 400 includes a Web services
`endpoint module 402 and the Web service component coor-
`dination module 404. The Web services endpoint module
`402 terminates the Web services protocols. In one embodi-
`ment,
`the Web services endpoint module 402 includes a
`transport layer server, such as an HTTP server 406. The Web
`services endpoint also includes an XML messaging engine
`408, such as that provided by SOAP to parse incoming
`requests and generate appropriate responses. The Web ser-
`vices endpoint module 402 of FIG.4 also interfaces with a
`service registry 410 in order to advertise the mobile client
`provisioning Web service using, for example,
`the UDDI
`protocol and the WSDLdefinition language.
`
`[0046] The Web service endpoint module 402 allows
`applications to make requests to provision mobile clients.
`The provisioning requests, such asthe illustrated provision-
`ing request 412, may include various items. These request
`items may include an identification of the provisioned
`terminal, including known or future terminal identification
`parameters. For example, this terminal identification (ID)
`414 mayinclude an IP address, a user name, an International
`Mobile Subscriber Identity (IMSI),an International Mobile
`Equipment Identity (MEI), a Mobile Station ISDN/PSTN
`Number (MSISDN), or any other identification associated
`with the terminal. For example, the IMEIis a parameter that
`uniquely identifies an individual wireless phone or commu-
`nicator. Generally, the IMEI appears on the label located on
`the back of the phone, and is automatically transmitted by
`
`

`

`US 2003/0084177 Al
`
`May 1, 2003
`
`the phone when the network asks for it. The IMSI generally
`refers to the primary numberused to identify a user on a
`GSM network,and is typically used in conjunction with the
`mobile telephone network for call routing. The MSISDNis
`a mobile number used by GSM/DCSnetworksthat contains
`information such as the country code, national destination
`code, HLRidentifier and a subscriber number. Anyofthese
`types of terminal IDs may be included in the provisioning
`request
`to identify the terminal, as can other
`types of
`terminal IDs. Thus,
`the aforementioned terminal IDs are
`representative, but the invention is clearly not limited to
`these particular examples described.
`
`[0047] Other items included in the provisioning requests
`include addresses 416 of data objects that are to be delivered
`in order to provision the terminal. For example a mobile
`games service could be accessed via a MIDIet on the
`terminal. This data object address field would contain the
`address where the MIDIet is located on the network. In one
`
`embodiment, this address may be provided via a URL. In
`addition,
`there may be different addresses provided to
`account for variants in the data objects to accommodate
`different terminal types.
`
`[0048] Still other items that may be included in the pro-
`visioning requests include data parameters 418 for
`the
`terminal to access the application. This may include, for
`example,
`the address of the application.
`In a Wireless
`Application Protocol (WAP) context, these data parameters
`may include the WAP settings required to provide connec-
`tivity to the application.
`
`items 420 may also be
`[0049] Any number of other
`included in the provisioning request, depending on the
`particular protocols, data formats, networking environ-
`ments, or other conditions relevant to the particularsetting.
`
`[0050] Another function ofthe service logic module 400 is
`to provide the l