U.S. patent application number 12/941205 was filed with the patent office on 2011-03-03 for generic bootstrapping protocol (gbp).
Invention is credited to Pouya Taaghol.
Application Number | 20110055411 12/941205 |
Document ID | / |
Family ID | 40254050 |
Filed Date | 2011-03-03 |
United States Patent
Application |
20110055411 |
Kind Code |
A1 |
Taaghol; Pouya |
March 3, 2011 |
GENERIC BOOTSTRAPPING PROTOCOL (GBP)
Abstract
Embodiments of methods and apparatus for discovering a
bootstrapping server by a mobile station, and bootstrapping the
mobile station are disclosed. In some embodiments, a mobile station
discovers a remotely disposed bootstrapping server; transmits
wirelessly a bootstrap request to the bootstrapping server; and
receive wirelessly a bootstrap response from the bootstrapping
server in response to the transmitted bootstrap request. Additional
variants and embodiments are also disclosed.
Inventors: |
Taaghol; Pouya; (San Jose,
CA) |
Family ID: |
40254050 |
Appl. No.: |
12/941205 |
Filed: |
November 8, 2010 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
12036947 |
Feb 25, 2008 |
7840687 |
|
|
12941205 |
|
|
|
|
60949192 |
Jul 11, 2007 |
|
|
|
Current U.S.
Class: |
709/228 |
Current CPC
Class: |
G06F 9/4416 20130101;
H04L 67/16 20130101; H04L 67/04 20130101; H04L 67/34 20130101 |
Class at
Publication: |
709/228 |
International
Class: |
G06F 15/16 20060101
G06F015/16 |
Claims
1. A Worldwide Interoperability for Microwave Access (WiMAX)
initial bootstrap procedure comprising: using a Domain Name System
(DNS) Service Record (SRV) to discover wirelessly, by a device
operating in a WiMAX network, a remotely disposed bootstrapping
server; and conducting a provisioning over-the-air (OTA) protocol
negotiation with the bootstrapping server using Hyper Text Transfer
Protocol (HTTP).
2. The WiMAX initial bootstrap procedure of claim 1, wherein:
wirelessly discovering the bootstrapping server comprises obtaining
an Internet Protocol (IP) address for the bootstrapping server
using Dynamic Host Configuration Protocol (DHCP).
3. The WiMAX initial bootstrap procedure of claim 2, wherein:
conducting the provisioning OTA protocol negotiation comprises
providing information regarding protocols supported by the device
to the bootstrapping server using HTTP.
4. The WiMAX initial bootstrap procedure of claim 3, wherein:
conducting the provisioning OTA protocol negotiation comprises
receiving an HTTP response from the bootstrapping server.
5. The WiMAX initial bootstrap procedure of claim 4, wherein:
receiving the HTTP response comprises receiving bootstrap
information stored on the bootstrapping server, wherein the
bootstrap information includes information regarding a selected
protocol that is supported by both the device and the bootstrapping
server.
6. The WiMAX initial bootstrap procedure of claim 4, wherein:
receiving the HTTP response comprises receiving from the
bootstrapping server information regarding another server that can
deliver bootstrap information, wherein the bootstrap information
includes information regarding a selected protocol that is
supported by both the device and the bootstrapping server.
7. A WiMAX initial bootstrap procedure comprising: receiving at a
bootstrapping server a DNS SRV record from a device operating in a
WiMAX network, the DNS SRV record sent by the device in order to
wirelessly discover the bootstrapping server; and conducting a
provisioning OTA protocol negotiation with the device using HTTP in
response to the receipt of the DNS SRV record.
8. The WiMAX initial bootstrap procedure of claim 7, wherein:
conducting the provisioning OTA protocol negotiation comprises
receiving at the bootstrapping server information sent using HTTP
regarding protocols supported by the device.
9. The WiMAX initial bootstrap procedure of claim 8, wherein:
conducting the provisioning OTA protocol negotiation comprises
transmitting, by the bootstrapping server, an HTTP response to the
device.
10. The WiMAX initial bootstrap procedure of claim 9, wherein:
transmitting the HTTP response comprises transmitting bootstrap
information stored on the bootstrapping server, wherein the
bootstrap information includes information regarding a selected
protocol that is supported by both the device and the bootstrapping
server.
11. The WiMAX initial bootstrap procedure of claim 9, wherein:
transmitting the HTTP response comprises transmitting from the
bootstrapping server information regarding another server that can
deliver bootstrap information, wherein the bootstrap information
includes information regarding a selected protocol that is
supported by both the device and the bootstrapping server.
12. A provisioning process for a device in a Worldwide
Interoperability for Microwave Access (WiMAX) network, the
provisioning process comprising: successfully executing a WiMAX
initial bootstrap procedure, the WiMAX initial bootstrap procedure
comprising: using a Domain Name System (DNS) Service Record (SRV)
record to discover wirelessly, by a device operating in a WiMAX
network, a remotely disposed bootstrapping server; conducting a
provisioning over-the-air (OTA) protocol negotiation with the
bootstrapping server using Hyper Text Transfer Protocol (HTTP);
establishing a communications link with the bootstrapping server;
and engaging in an OTA provisioning process specific to a protocol
identified during the provisioning OTA protocol negotiation.
13. The WiMAX initial bootstrap procedure of claim 12, wherein:
wirelessly discovering the bootstrapping server comprises obtaining
an Internet Protocol (IP) address for the bootstrapping server
using Dynamic Host Configuration Protocol (DHCP).
14. The WiMAX initial bootstrap procedure of claim 13, wherein:
conducting the provisioning OTA protocol negotiation comprises
providing information regarding protocols supported by the device
to the bootstrapping server using HTTP.
15. The WiMAX initial bootstrap procedure of claim 14, wherein:
conducting the provisioning OTA protocol negotiation comprises
receiving an HTTP response from the bootstrapping server.
16. The WiMAX initial bootstrap procedure of claim 15, wherein:
receiving the HTTP response comprises receiving bootstrap
information stored on the bootstrapping server, wherein the
bootstrap information includes information regarding a selected
protocol that is supported by both the device and the bootstrapping
server.
17. The WiMAX initial bootstrap procedure of claim 15, wherein:
receiving the HTTP response comprises receiving from the
bootstrapping server information regarding another server that can
deliver bootstrap information, wherein the bootstrap information
includes information regarding a selected protocol that is
supported by both the device and the bootstrapping server.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] The present application claims priority to U.S. patent
application Ser. No. 12/036,947 filed Feb. 25, 2008 entitled,
"GENERIC BOOTSTRAPPING PROTOCOL (GBP)," which claims priority to
U.S. Provisional Patent Application No. 60/949,192 filed Jul. 11,
2007 entitled, "GENERIC BOOTSTRAPPING PROTOCOL (GBP)."
TECHNICAL FIELD
[0002] The present disclosure relates generally to wireless
communication systems, and more particularly, to methods and
apparatus for providing a generic bootstrap protocol.
BACKGROUND
[0003] There is ongoing interest in developing and deploying mobile
networks which may facilitate transfer of information at broadband
rates. These networks are colloquially referred to herein as
broadband wireless access (BWA) networks and may include networks
operating in conformance with one or more protocols specified by
the 3rd Generation Partnership Project (3GPP) and its derivatives
or the Institute for Electrical and Electronic Engineers (IEEE)
802.16 standards (e.g., IEEE 802.16-2005 Amendment), although the
embodiments discussed herein are not necessarily so limited. IEEE
802.16 compatible BWA networks are sometimes referred to as WiMAX
networks, an acronym that stands for Worldwide Interoperability for
Microwave Access, which is a certification mark for products that
pass conformity and interoperability tests for the IEEE 802.16
standards.
[0004] It is predicted that many different device types may be
enabled by mobile broadband wireless technologies. Such devices may
include notebooks, ultra mobile PCs (UMPCs), handheld mobile
devices, and other consumer electronics such as MP3 players,
digital cameras, etc. A mobile broadband service provider may
desire to activate and enable subscriptions for these device
types.
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Embodiments of the invention will be described by way of
exemplary embodiments, but not limitations, illustrated in the
accompanying drawings in which like references denote similar
elements, and in which:
[0006] FIG. 1 is an exemplary block diagram illustrating a
broadband wireless access (BWA) network architecture in accordance
with various embodiments of the present invention.
[0007] FIG. 2 is an exemplary flow diagram illustrating an
over-the-air (OTA) bootstrapping and provisioning process in
accordance with various embodiments of the present invention.
[0008] FIG. 3 is an exemplary flow diagram illustrating a
bootstrapping process in accordance with various embodiments of the
present invention.
[0009] FIG. 4 is an exemplary flow diagram illustrating an
integrated bootstrapping and subscription and signup process in
accordance with various embodiments of the present invention.
[0010] FIG. 5 is an exemplary block diagram representation of an
example processor based system that may be used to practice various
embodiments of the present invention.
DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS
[0011] Illustrative embodiments of the invention include, but are
not limited to, methods and apparatuses for providing a generic
bootstrap protocol.
[0012] Various aspects of the illustrative embodiments will be
described using terms commonly employed by those skilled in the art
to convey the substance of their work to others skilled in the art.
However, it will be apparent to those skilled in the art that
alternate embodiments may be practiced with only some of the
described aspects. For purposes of explanation, specific numbers,
materials, and configurations are set forth in order to provide a
thorough understanding of the illustrative embodiments. However, it
will be apparent to one skilled in the art that alternate
embodiments may be practiced without the specific details. In other
instances, well-known features are omitted or simplified in order
not to obscure the illustrative embodiments.
[0013] Further, various operations will be described as multiple
discrete operations, in turn, in a manner that is most helpful in
understanding the illustrative embodiments; however, the order of
description should not be construed as to imply that these
operations are necessarily order dependent. In particular, these
operations need not be performed in the order of presentation.
[0014] The phrase "in some embodiments" is used repeatedly. The
phrase generally does not refer to the same embodiments; however,
it may. The terms "comprising," "having," and "including" are
synonymous, unless the context dictates otherwise. The phrase "A
and/or B" means (A), (B), or (A and B). The phrase "A/B" means (A),
(B), or (A and B), similar to the phrase "A and/or B". The phrase
"at least one of A, B and C" means (A), (B), (C), (A and B), (A and
C), (B and C) or (A, B and C). The phrase "(A) B" means (B) or (A
and B), that is, A is optional.
[0015] Although specific embodiments have been illustrated and
described herein, it will be appreciated by those of ordinary skill
in the art that a wide variety of alternate and/or equivalent
implementations may be substituted for the specific embodiments
shown and described, without departing from the scope of the
embodiments of the invention. This application is intended to cover
any adaptations or variations of the embodiments discussed herein.
Therefore, it is manifestly intended that the embodiments of the
invention be limited only by the claims and the equivalents
thereof.
[0016] While example embodiments may be described herein in
relation to broadband wireless access for wireless metropolitan
area networks (WMANs) such as WiMAX networks, embodiments of the
invention are not limited thereto and can be applied to other types
of wireless networks where similar advantages may be obtained. Such
networks include, but are not limited to, wireless local area
networks (WLANs), wireless personal area networks (WPANs) and/or
wireless wide area networks (WWANs) such as cellular networks and
the like.
[0017] The following embodiments may be used in a variety of
applications including transmitters and receivers of a mobile
wireless radio system. Radio systems specifically included within
the scope of the embodiments of the present invention include, but
are not limited to, network interface cards (NICs), network
adaptors, base stations, access points (APs), gateways, bridges,
hubs and satellite radiotelephones. Further, the radio systems
within the scope of embodiments of the invention may include
satellite systems, personal communication systems (PCS), two-way
radio systems, global positioning systems (GPS), two-way pagers,
personal computers (PCs) and related peripherals, personal digital
assistants (PDAs), personal computing accessories and all existing
and future arising systems which may be related in nature and to
which the principles of the embodiments could be suitably
applied.
[0018] In conventional cellular communication models, a
communication device (e.g. a cell phone or a network interface card
(NIC)) is typically manufactured for a specific service provider
(SP), which in turn sells the device to end users. SPs operate
network infrastructure and provide wireless access to subscribers.
At the time of sale, a device is typically set up for accessing the
SP's network, which is referred to as "provisioning." This
conventional model is thus predicated on the SP's control of
manufactured equipment which may be used in its wireless network(s)
as well as provisioning these devices for the user at the point of
sale (POS).
[0019] However, in anticipation of many different types of
equipment, such as those mentioned previously, being used in BWA
networks (such as WiMAX networks), an SP is less likely to have
complete control over the manufacture of all devices which may
potentially be used in its BWA network. Furthermore, since this
wide variety of devices may be made available by many different
vendors, a POS provisioning approach may not be adequate.
Accordingly, a dynamic over-the-air (OTA) provisioning approach may
be used to enable these devices to communicate over a SP's BWA
network.
[0020] Before a BWA compatible communication device connects to a
provisioning server over an OTA link to get provisioned, it is
often necessary for the communication device to be bootstrapped
with initial information relating to the provisioning server (e.g.,
provisioning server Uniform Resource Identifier (URI), Internet
Protocol (IP) address, security settings etc.) and credentials that
may be used to connect to the provisioning server. The information
to be received by the BWA compatible device during the
bootstrapping process may then be used to configure the device to
receive service from the provisioning server during the
provisioning process.
[0021] In conventional BWA communication models, bootstrapping
mechanisms are typically designed specifically for handsets (e.g.,
a cell phone), and may not be equally effective in bootstrapping
other BWA compliant communication devices and operating systems.
For example, in the Open Mobile Alliance--Device Management
(OMA-DM) protocol (e.g., OMA-DM version 1.2), a provisioning server
sends an unsolicited bootstrap message to the communication devices
on a user datagram protocol (UDP) port 2948. A conventional handset
(e.g., a cell phone) may be able to receive such an unsolicited
bootstrap message on its UDP port 2948. However, the UDP port 2948
may not be a well known port for firewalls and host intrusion
detection systems (HIDS) that may be operating on other
communication devices, e.g., personal computers and laptops.
Furthermore, a provisioning client on the communication device may
not have full control over these firewalls/HIDS. As a result, the
bootstrap message may be blocked by the firewall/HIDS of some of
these other communication devices, thereby hindering the
provisioning process.
[0022] Accordingly, some of the embodiments of the present
invention employ a generic bootstrapping mechanism that would allow
various device types (e.g., universal integrated circuit card
(UICC), notebooks, personal computer (PC), ultra mobile PC (UMPC),
or any other BWA compatible device) to receive a bootstrap message
and would also allow provisioning protocol negotiation.
[0023] FIG. 1 is an exemplary block diagram illustrating a BWA
network architecture 10 in accordance with various embodiments of
the present invention. The network 10 of FIG. 1 includes a service
provider (SP) network having one or more radio access networks
(RANs) 20 and a core network 25.
[0024] A mobile station (MS) 15 may access the core network 25 via
a radio link with a base station (BS) (e.g. BS 40, 42, etc.) in the
RAN 20. The MS 15 may, for example, be a subscriber station using
protocols compatible with the IEEE 802.16 standards (e.g., IEEE
802.16-2005 Amendment) or WiMAX standards. While FIG. 1 generally
depicts the MS 15 as a cellular phone, in various embodiments the
MS 15 may be a notebook, an ultra mobile PC (UMPC), a handheld
mobile device, an universal integrated circuit card (UICC), a
personal digital assistant (PDA), a Customer Premise Equipment
(CPE), or other consumer electronics such as MP3 players, digital
cameras, etc.
[0025] In some embodiments, communication with the MS 15 via RAN 20
may be facilitated via one or more access service network gateways
(ASN-GWs) 45, although the embodiments are not limited to this
specific type of network implementation. ASN-GW 45 (or other
similar type of network node) may act as an interface between the
core network 25 and its RANs 20. Thus, ASN-GW 45 may be connected
to a plurality of base stations 40, 42 and may function as a type
of BS controller and/or mobile switching center (MSC) to facilitate
handover control and other functions for RAN 20, although the
embodiments are not so limited.
[0026] The core network 25 may further include a provisioning
server 50, a bootstrapping server 55, and/or a subscription server
60. In some embodiments, the provisioning server 50 may also act as
a bootstrapping server, thereby eliminating the need of a separate
bootstrapping server 55. Although not shown, the core network 25
may further include several other components, such as an
authentication, authorization and accounting (AAA) server.
[0027] FIG. 2 is an exemplary flow diagram illustrating a
bootstrapping and an over-the-air (OTA) provisioning process in
accordance with various embodiments of the present invention.
Referring to FIGS. 1 and 2, a non-provisioned device (e.g., the MS
15) may enter an SP's BWA network 110 at 115. The network entry 115
may include several operations (not shown) known to those skilled
in the art, e.g., authenticating the MS 15. At 120, the ASN-GW 45
of the BWA network may hot-line the MS 15 to the bootstrapping
server 55 and/or the provisioning server 50. Through the hot-lining
process 120, the MS 15 may be directed to, and be able to access
the bootstrapping server 55 and/or the provisioning server 50. At
125, the MS 15 may exchange bootstrap information with the
bootstrapping server 55. At 130, the MS 15 may optionally subscribe
to, and sign up with, the SP through the subscription server 60.
The MS 15 may then exchange provisioning information with the
provisioning server 50 during a provisioning process 135.
[0028] In some embodiments, bootstrapping 125 may be performed
concurrently with the subscription and signup process 130, as will
be discussed in further detail below.
[0029] FIG. 3 is an exemplary flow diagram illustrating a
bootstrapping process in more details in accordance with various
embodiments of the present invention. Referring to FIGS. 1-3, at
115, the MS 15 may enter the BWA network 110. At 220, various other
operations may be performed, including but not limited to,
authenticating the MS 15, determining whether the MS 15 has been
provisioned earlier, etc.
[0030] At 225, the MS 15 may discover the bootstrapping server 55.
Discovering the bootstrapping server 55 may include, but is not
limited to, obtaining the bootstrapping server 55 address (e.g., IP
address, URI, etc.) and obtaining other details about the server.
The discovery of the server may be achieved by using, for example,
a Domain name system (DNS) Service Record (SRV). The discovery of
the servers may also be achieved employing other techniques, for
example, by using a vendor specific option (e.g., option 43) in
Dynamic Host Configuration Protocol (DHCP). Using a DNS SRV or a
vendor specific option in DHCP is well known to those skilled in
the art, and hence, will not be discussed in further detail. In
some embodiments, the provisioning server 50 may also act as a
bootstrapping server; in those cases, the provisioning server 50
may be discovered at 225 instead of discovering the bootstrapping
server.
[0031] Once the MS 15 is aware (as a result of the discovery at
225) of the bootstrapping server 55 address and other details, the
MS 15 may send a bootstrap request to the bootstrapping server 55
at 230. In some embodiments, the bootstrap request may include
information such as the MS 15 identity (e.g., WiMAX--Media Access
Control (MAC) address), one or more protocol(s) supported by MS 15
(e.g., OMA-DM, DSL Forum's Technical Report 069 protocol (TR069),
native Extensible Markup Language (native XML), etc.), notification
and polling capabilities supported by the MS 15 (e.g., Wireless
Application Protocol-PUSH (WAP-PUSH), periodic-poll, checking at
attachment-only, etc.), a type of the MS 15 (e.g. a notebook, a
handheld mobile device, a PC, a PDA, a CPE, etc.), and/or an
operating system (OS) of the MS 15 (e.g., Windows, Linux, etc.)
and, optionally, its associated version.
[0032] In some embodiments, the bootstrap request may be
transmitted using an appropriate protocol (e.g., Hyper Text
Transfer Protocol (HTTP)) that is not blocked by any firewall/HIDS
of the MS 15 (or any other firewall/HIDS between the MS 15 and the
bootstrapping server 55).
[0033] When the bootstrap request is transmitted using HTTP, the MS
15 may utilize an HTTP header field (e.g., comment fields in the
user agent of the header), a message body field, and/or other
appropriate fields in the HTTP request to transmit some or all the
bootstrap request information.
[0034] Once the bootstrapping server 55 receives such a request,
the bootstrapping server 55 may select an appropriate provisioning
protocol for provisioning the MS 15. The provisioning protocol
selection may be based on some or all the information about the MS
15 received in the bootstrap request and/or a preference (or
capabilities) of the SP. For example, in some embodiments, the
selection of the provisioning protocol may be based at least in
part on one or more protocol(s) supported by the MS 15 (e.g.
OMA-DM, TR069, native XML, etc.) and the protocol(s) supported by
the SP's network 10.
[0035] At 235, the bootstrapping server 55 may generate a bootstrap
response. The bootstrap response may include the selected
provisioning protocol, a bootstrap message, and/or other network
related information. Some or all the information included in the
bootstrap response may be encrypted using, for example, a bootstrap
encryption key (BEK). The bootstrap message may include, for
example, various information about the provisioning server (e.g.,
provisioning server URI, IP address, security settings etc.),
security parameters, and/or any other appropriate information for
provisioning the MS 15.
[0036] In some embodiments, the bootstrap response may be sent
using any appropriate protocol (e.g., HTTP) that is not blocked by
any firewall/HIDS of the MS 15 (or any other firewall/HIDS between
the bootstrapping server 55 and MS 15). In some embodiments, the
bootstrap response is transmitted using the HTTP. One or more
appropriate fields (e.g., the header field, message field, etc.) of
the HTTP bootstrap response may be utilized to transmit some or all
the bootstrap response information.
[0037] In some embodiments, the bootstrapping process 125 (see FIG.
2) may be combined with (or embedded in) the subscription and
signup process 130. FIG. 4 is an exemplary flow diagram
illustrating an integrated bootstrapping and subscription and
signup process in accordance with various embodiments of the
present invention. Referring to FIGS. 1 and 4, at 305, the MS 15 or
the user of the MS 15 may select an SP via an appropriate
connection manager and transmit the selection to the selected SP's
network. For example, the MS 15 may select the SP of the network 10
of FIG. 1. At 310, the MS 15 may be authenticated and hot-lined by
the SP's network.
[0038] At 315, a browser may be activated in the MS 15 and the MS
15 may be redirected to a subscription portal residing in the
subscription server 60 of the selected SP. In some embodiments, the
browser may provide the MS 15 or its user a choice of different
types of subscriptions. For example, a lower priced subscription
may allow the MS 15 or its user access to the SP's network for a
specific period of time (say, 6 or 12 hours), whereas a higher
priced subscription may allow access to the network for a longer
period of time (say, a week, or a month, i.e., a weekly or a
monthly subscription). As would be readily appreciated by someone
skilled in the art, numerous other subscription types may be
envisioned. At 320, the MS 15 or its user selects an appropriate
subscription using the activated browser, and the selection is
transmitted to the subscription server 60.
[0039] In some embodiments, the MS 15 may also transmit (not shown
in the figure) a bootstrap request to the subscription server 60
integrally or along with the transmission of the selection of the
subscription at 320. The MS 15 may use the same browser connection
to transmit the bootstrap request along with transmitting the
selected subscription information. In some embodiments, during the
subscription process, the MS 15 user may be requested to input (not
shown in the figure) a variety of information (e.g., an user name,
address, credit card number, contact details etc.) in the browser,
and the bootstrap request may be transmitted to the subscription
server 60 while transmitting the variety of information.
[0040] The subscription server 60 may pass (not shown in the
figure) the bootstrap request to the bootstrapping server 55. In
response to receiving the bootstrap request, the bootstrapping
server 55 may select an appropriate provisioning protocol and
generate (not shown in the figure) an appropriate bootstrap
response, as discussed with respect to FIG. 3.
[0041] At 325, the subscription portal may retrieve the bootstrap
response generated by the bootstrapping server 55. In the meantime,
the browser in the MS 15 may display a confirmation page, at 330,
to confirm and activate the selected subscription. Once the MS 15
or its user confirms the activation of the subscription, the
subscription server 60 may transmit the bootstrap response to the
MS 15. In some embodiments, the subscription portal may transmit a
subscription confirmation page to the MS 15 confirming the
subscription (or a thank-you page thanking the user of the MS 15
for the subscription, or any other appropriate page), which the MS
15 may display in the browser; the subscription server 60 may use
the same browser connection to transmit the bootstrap response
along with transmitting the subscription confirmation page
information (or the thank-you page information) to MS 15.
[0042] Once the MS 15 receives the bootstrap response, provisioning
server 50 may start the provisioning process, at 340, using an
appropriate provisioning protocol (e.g. OMA-DM, TR069, native XML)
selected during the generation of the bootstrap response. As
discussed earlier, the bootstrap request and/or the bootstrap
response may be sent using any appropriate protocol (e.g., HTTP)
that is not blocked by the MS 15 firewall/HIDS (or any
firewall/HIDS between the MS 15 and the subscription server
60/bootstrapping server 55).
[0043] In some embodiments, the provisioning server 50 may also act
as the bootstrapping server. In these embodiments, the provisioning
server may perform both the bootstrapping and the provisioning
processes.
[0044] FIG. 5 is an exemplary block diagram representation of an
example processor based system 2000 that may be used to practice
various embodiments of the present invention. The processor system
2000 may be a desktop computer, a laptop computer, a handheld
computer, a tablet computer, a PDA, a server, an Internet
appliance, and/or any other type of computing device. In some
embodiments, the processor system 2000 may be capable of
functioning as the MS 15, the provisioning server 50, the
bootstrapping server 55, and/or the subscription server 60.
[0045] The processor system 2000 illustrated in FIG. 5 includes a
chipset 2010, which includes a memory controller 2012 and an
input/output (I/O) controller 2014. The chipset 2010 may provide
memory and I/O management functions as well as a plurality of
general purpose and/or special purpose registers, timers, etc. that
are accessible or used by a processor 2020. The processor 2020 may
be implemented using one or more processors, WLAN components, WMAN
components, WWAN components, and/or other suitable processing
components. The processor 2020 may include a cache 2022, which may
be implemented using a first-level unified cache (L1), a
second-level unified cache (L2), a third-level unified cache (L3),
and/or any other suitable structures to store data.
[0046] The memory controller 2012 may perform functions that enable
the processor 2020 to access and communicate with a main memory
2030 including a volatile memory 2032 and a non-volatile memory
2034 via a bus 2040. The volatile memory 2032 may be implemented by
synchronous dynamic random access memory (SDRAM), dynamic random
access memory (DRAM), RAMBUS dynamic random access memory (RDRAM),
and/or any other type of random access memory device. The
non-volatile memory 2034 may be implemented using flash memory,
read only memory (ROM), electrically erasable programmable read
only memory (EEPROM), and/or any other desired type of memory
device.
[0047] The processor system 2000 may also include an interface
circuit 2050 that is coupled to the bus 2040. The interface circuit
2050 may be implemented using any type of interface standard such
as an Ethernet interface, a universal serial bus (USB), a third
generation input/output interface (3GIO) interface, and/or any
other suitable type of interface. In various embodiments, the
interface circuit 2050 may be incorporated with the earlier
describe generic bootstrap teachings. In various embodiments, some
of the teachings may be implemented in other components, e.g. I/O
controller 2014.
[0048] One or more input devices 2060 may be connected to the
interface circuit 2050. The input device(s) 2060 permit an
individual to enter data and commands into the processor 2020. For
example, the input device(s) 2060 may be implemented by a keyboard,
a mouse, a touch-sensitive display, a track pad, a track ball, an
isopoint, and/or a voice recognition system.
[0049] One or more output devices 2070 may also be connected to the
interface circuit 2050. For example, the output device(s) 2070 may
be implemented by display devices (e.g., a light emitting display
(LED), a liquid crystal display (LCD), a cathode ray tube (CRT)
display, a printer and/or speakers). The interface circuit 2050 may
include, among other things, a graphics driver card.
[0050] The processor system 2000 may also include one or more mass
storage devices 2080 to store software and data. Examples of such
mass storage device(s) 2080 include floppy disks and drives, hard
disk drives, compact disks and drives, and digital versatile disks
(DVD) and drives.
[0051] The interface circuit 2050 may also include a communication
device such as a modem or a network interface card to facilitate
exchange of data with external computers via a network. The
communication link between the processor system 2000 and the
network may be any type of network connection such as an Ethernet
connection, a digital subscriber line (DSL), a telephone line, a
cellular telephone system, a coaxial cable, etc.
[0052] In some embodiments, the processor system 2000 may be
coupled to an antenna structure (not shown in the figure) to
provide access to other devices of a network. In some embodiments,
the antenna structure may include one or more directional antennas,
which radiate or receive primarily in one direction (e.g., for 120
degrees), cooperatively coupled to one another to provide
substantially omnidirectional coverage; or one or more
omnidirectional antennas, which radiate or receive equally well in
all directions. In some embodiments, the antenna structure may
include one or more directional and/or omnidirectional antennas,
including, e.g., a dipole antenna, a monopole antenna, a patch
antenna, a loop antenna, a microstrip antenna or any other type of
antennas suitable for OTA transmission/reception of RF signals.
[0053] Access to the input device(s) 2060, the output device(s)
2070, the mass storage device(s) 2080 and/or the network may be
controlled by the I/O controller 2014. In particular, the I/O
controller 2014 may perform functions that enable the processor
2020 to communicate with the input device(s) 2060, the output
device(s) 2070, the mass storage device(s) 2080 and/or the network
via the bus 2040 and the interface circuit 2050.
[0054] While the components shown in FIG. 5 are depicted as
separate blocks within the processor system 2000, the functions
performed by some of these blocks may be integrated within a single
semiconductor circuit or may be implemented using two or more
separate integrated circuits. For example, although the memory
controller 2012 and the I/O controller 2014 are depicted as
separate blocks within the chipset 2010, the memory controller 2012
and the I/O controller 2014 may be integrated within a single
semiconductor circuit.
[0055] Although certain example methods, apparatus, and articles of
manufacture have been described herein, the scope of coverage of
this disclosure is not limited thereto. On the contrary, this
disclosure covers all methods, apparatus, and articles of
manufacture fairly falling within the scope of the appended claims
either literally or under the doctrine of equivalents. For example,
although the above discloses example systems including, among other
components, software or firmware executed on hardware, it should be
noted that such systems are merely illustrative and should not be
considered as limiting. In particular, it is contemplated that any
or all of the disclosed hardware, software, and/or firmware
components could be embodied exclusively in hardware, exclusively
in software, exclusively in firmware or in some combination of
hardware, software, and/or firmware.
* * * * *