System and method for assigning a permanent personal identification number (PIN) to a mobile communication device

CROSS-REFERENCE TO RELATED APPLICATION(S)

This patent application discloses subject matter related to the subject matter disclosed in the following commonly owned co-pending patent applications: (i) "SYSTEM AND METHOD FOR PORTING A PERSONALIZED INDICIUM ASSIGNED TO A MOBILE COMMUNICATIONS DEVICE," filed _, Application No. _ (RIM No. ID-1126, Attorney Docket No. 1400-1001US), in the name(s) of: Graeme Whittington, Allan David Lewis, James Godfrey, Herb A. Little, and Marc Plumb; (ii) "SYSTEM AND METHOD FOR SECURING A PERSONALIZED INDICIUM ASSIGNED TO A MOBILE COMMUNICATIONS DEVICE," filed _, Application No. _ (RIM No. ID-1127, Attorney Docket No. 1400-1002US), in the name(s) of: David Bajar, Herb A. Little, James Godfrey, Allan David Lewis, Wen Gao, Marc Plumb, Michael Brown, Graeme Whittington, and Neil Adams; and (iii) "SYSTEM AND METHOD FOR MANAGING SECURE REGISTRATION OF A MOBILE COMMUNICATIONS DEVICE," filed _, Application No. _ (RIM No. ID-1128, Attorney Docket No. 1400-1003US), in the name(s) of: David Bajar, Allan David Lewis, Wen Gao, Herb A. Little, James Godfrey, Marc Plumb, Michael Brown, and Neil Adams; all of which are incorporated by reference herein.

FIELD OF THE APPLICATION

The present patent application generally relates to wireless packet data service networks. More particularly, and not by way of any limitation, the present patent application is directed to a system and method for assigning a personalized indicium to a mobile communications device operable to be disposed in a wireless packet data service network.

BACKGROUND

It is becoming commonplace to use wireless packet data service networks for effectuating data sessions with mobile communications devices. In some implementations, unique indicia need to be assigned to the devices in order to facilitate certain aspects of service provisioning, e.g., security, validation and authentication, et cetera. In such scenarios, it becomes imperative that no two devices have the same indicium (i.e., collision). Further, provisioning of such indicia should be flexible so as to maintain the entire pool of indicia to a manageable level while allowing for their widespread use in multiple service environments.

SUMMARY

In one embodiment, a scheme is provided for assigning a personalized indicium to a mobile communications device, comprising: transmitting a request by the mobile communications device to a network node, the request including a temporary Personal Information Number (PIN) and at least one device/subscriber identifier relating to the mobile communications device; and upon validating the request, providing a response by the network node to the mobile communications device, the response including a permanent PIN assigned to the mobile communications device.

In another embodiment, a mobile communications device is disclosed which comprises: logic means operable to generate a temporary PIN for transmitting in a request for assignment of a personalized indicium, the request being directed to a network node interfaced with a wireless network; and logic means operable to execute a registration procedure with the network node using the personalized indicium upon receipt thereof, the personalized indicium comprising a permanent PIN assigned to the mobile communications network that is provided via a response by the network node.

In yet another embodiment, a network system is disclosed for dynamically assigning PINs to mobile communications devices, which comprises: means for validating a request transmitted by a mobile communications device to a network node, the request including a temporary PIN and at least one of a device identifier and a subscriber identifier relating to the mobile communications device; and means for assigning a permanent PIN to the mobile communications device upon validating the request, the permanent PIN being provided to the mobile communications device via a response from the network node.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the embodiments of the present patent application may be had by reference to the following Detailed Description when taken in conjunction with the accompanying drawings wherein:

FIG. 1 depicts an exemplary network environment including a wireless packet data service network wherein an embodiment of the present patent application may be practiced;

FIG. 2 depicts additional details of an exemplary relay network operable with a mobile communications device in accordance with an embodiment;

FIG. 3 depicts a software architectural view of a mobile communications device according to one embodiment;

FIG. 4 depicts a flowchart of an embodiment for dynamically assigning a Personal Information Number (PIN) indicium to a mobile communications device;

FIG. 5 depicts a message flow diagram with respect to an exemplary dynamic PIN assignment mechanism according to one embodiment;

FIG. 6A depicts a flowchart of an embodiment of a PIN management mechanism according to one embodiment;

FIG. 6B depicts a flowchart of an embodiment for registering a mobile communications device using a dynamically assigned PIN; and

FIG. 7 depicts a block diagram of a mobile communications device according to one embodiment.

DETAILED DESCRIPTION OF THE DRAWINGS

A system and method of the present patent application will now be described with reference to various examples of how the embodiments can best be made and used. Like reference numerals are used throughout the description and several views of the drawings to indicate like or corresponding parts, wherein the various elements are not necessarily drawn to scale. Referring now to the drawings, and more particularly to FIG. 1, depicted therein is an exemplary network environment 100 including a wireless packet data service network 112 wherein an embodiment of the present patent application may be practiced. An enterprise network 102, which may be a packet-switched network, can include one or more geographic sites and be organized as a local area network (LAN), wide area network (WAN) or metropolitan area network (MAN), et cetera, for serving a plurality of corporate users. A number of application servers 104-1 through 104-N disposed as part of the enterprise network 102 are operable to provide or effectuate a host of internal and external services such as email, video mail, Internet access, corporate data access, messaging, calendaring and scheduling, information management, and the like. Accordingly, a diverse array of personal information appliances such as desktop computers, laptop computers, palmtop computers, et cetera, although not specifically shown in FIG. 1, may be operably networked to one or more of the application servers 104-i, i = 1, 2,...,N, with respect to the services supported in the enterprise network 102.

Additionally, a remote services server 106 may be interfaced with the enterprise network 102 for enabling a corporate user to access or effectuate any of the services from a remote location using a suitable mobile communications device (MCD) 116. A secure communication link with end-to-end encryption may be established that is mediated through an external IP network, i.e., a public packet-switched network such as the Internet 108, as well as the wireless packet data service network 112 operable with MCD 116 via suitable wireless network infrastructure that includes a base station (BS) 114 . In one embodiment, a trusted relay network 110 may be disposed between the Internet 108 and the infrastructure of wireless packet data service network 112. In another embodiment, the infrastructure of the trusted relay network 110 may be integrated with the wireless packet data service network 112, whereby the functionality of the relay infrastructure, certain aspects of which will be described in greater detail below, is consolidated as a separate layer within a "one-network" environment. Additionally, by way of example, MCD 116 may be a data-enabled mobile handheld device capable of receiving and sending messages, web browsing, interfacing with corporate application servers, et cetera, regardless of the relationship between the networks 110 and 112. Accordingly, a "network node" may include both relay functionality and wireless network infrastructure functionality in some exemplary implementations.

For purposes of the present patent application, the wireless packet data service network 112 may be implemented in any known or heretofore unknown mobile communications technologies and network protocols, as long as a packet-switched data service is available therein for transmitting packetized information. For instance, the wireless packet data service network 112 may be comprised of a General Packet Radio Service (GPRS) network that provides a packet radio access for mobile devices using the cellular infrastructure of a Global System for Mobile Communications (GSM)-based carrier network. In other implementations, the wireless packet data service network 112 may comprise an Enhanced Data Rates for GSM Evolution (EDGE) network, an Integrated Digital Enhanced Network (IDEN), a Code Division Multiple Access (CDMA) network, a Universal Mobile Telecommunications System (UMTS) network, or any 3^rd Generation (3G) network. As will be seen hereinbelow, the embodiments of the present patent application for assigning and managing a personalized indicium such as a PIN with respect to MCD 116 will be described regardless of any particular wireless network implementation.

FIG. 2 depicts additional details of an exemplary relay network infrastructure 200 operable as part of relay network 110 interfacing with the wireless packet data service network 112 described above. A relay services node 202 is operable, at least in part, for providing connectivity between MCDs and various data application services (enterprise services, external IP data services, et cetera), regardless of the geographic location of the MCDs and their respective wireless carriers. Also, since multiple relay services nodes can co-exist in a distributed network architecture, a relay bridge 208 may be provided in operable connection with the relay services node 202 for supporting inter-relay connectivity. In one implementation, relay bridge 208 connects with separate relay node sites, forming tunnels between relays over which MCD messages can flow to and from services, irrespective of the region where the MCD is in.

Communication between the relay services node 202 and various application gateways and servers is effectuated using any suitable protocol, e.g., Server Relay Protocol (SRP), preferably over IP links. By way of illustration, remote services server 106 associated with the enterprise network 102 (shown in FIG. 1) communicates with the relay using SRP for effectuating internal data services with respect to the enterprise's mobile subscribers. Likewise, reference numerals 204 and 206 refer to external application gateways, such as Internet Service Provider (ISP) or Internet Access Provider (IAP) servers, and other gateways, respectively, which are also interfaced with the relay node 202 using SRP. A peer-to-peer server 210 may also be provided in operable connection with the relay node 202 for handling peer-level messaging between two MCDs using their respective PIN indicia.

Additionally, a database 211 may be provided in operable connection with the relay node 202 for handling and managing MCD location information. Preferably, this location information is stored by PIN indicia of the MCDs, wherein the records maintain a particular device's last known location. A registration server 216 is operable for providing registration services for MCDs when they are initially activated or when the user re-registers due to moving to a different wireless network coverage area. In one implementation, the location information of registration server 216 may be programmed into an MCD. When the MCD registers successfully, registration server 216 is operable to provide the serving relay node's location, whereupon data sessions may be engaged by the MCD.

One or more wireless transport (WT) interfaces are provided as part of relay services node 202 for connecting with wireless carrier networks that service MCDs. By way of illustration, WT 212A and WT 212B communicate with respective packet routers 214A and 214B using TCP/IP links, which route data packets to and from respective wireless packet data service networks, exemplified in FIG. 2 as carrier network 220A and carrier network 220B. Although not specifically shown, registration server 216, which handles administration and registration services for MCDs, may be provided with separate WT and packet routing for interfacing with the carrier networks 220A, 220B.

A provisioning system (PRV) 218 may be co-located or otherwise associated with the relay services node 202 for setting up and managing various service providers (i.e., carrier networks), subscribers, MCD manufacturers, resellers, and other entities in order to support any number of service and market differentiation requirements. Additionally, the provisioning system 218 may include logic for provisioning personalized indicia (e.g., PIN assignment and management) with respect to the MCDs. Also, subscriber validation logic may be provided as part of the provisioning system 208. Accordingly, the provisioning system 208 may be implemented with a plurality of interfaces with respect to the various modules of the relay services node 202, e.g., interfaces to registration servers, peer-to-peer servers, location databases, et cetera, in addition to including attendant service logic processing that may be realized in suitable hardware, firmware and/or firmware logic blocks as well as database structures.

FIG. 3 depicts a software architectural view of a mobile communications device operable according to one embodiment for requesting a personalized indicium (such as a PIN) in a dynamic manner. A multi-layer transport stack (TS) 306 is operable to provide a generic data transport protocol for any type of corporate data, including email, via a reliable, secure and seamless continuous connection to a wireless packet data service network. As illustrated in the embodiment of FIG. 3, an integration layer 304A is operable as an interface between the MCD's radio layer 302 and the transport stack 306. Likewise, another integration layer 304B is provided for interfacing between the transport stack 306 and the user applications 307 supported on the MCD, e.g., email 308, calendar/scheduler 310, contact management 312 and browser 314. Although not specifically shown, the transport stack 306 may also be interfaced with the MCD's operating system. In another implementation, the transport stack 306 may be provided as part of a data communications client module operable as a host-independent virtual machine on a mobile device.

The bottom layer (Layer 1) of the transport stack 306 is operable as an interface to the wireless network's packet layer. Layer 1 handles basic service coordination within the exemplary network environment 100 shown in FIG. 1. For example, when an MCD roams from one carrier network to another, Layer 1 verifies that the packets are relayed to the appropriate wireless network and that any packets that are pending from the previous network are rerouted to the current network. The top layer (Layer 4) exposes various application interfaces to the services supported on the MCD. The remaining two layers, Layer 2 and Layer 3, are responsible for datagram segmentation/reassembly and security, compression and routing, respectively.

A PIN logic module 316 provided as part of the MCD's software environment is disposed in operable communication with the transport stack 306 as well as the OS environment. In one embodiment, the PIN logic module 316 comprises logic operable to generate a temporary PIN for transmission in a "PIN request" message to a network node, e.g., a relay node and associated registration server, since PIN may be a required parameter in communications between an MCD and the serving relay node. Further, as will be shown below, appropriate network logic (provided as part of the relay node's registration servers, provisioning system, etc.) is operable to assign a more persistent PIN to the requesting MCD based on the parametric information of the PIN request message. In one exemplary implementation, the PIN logic means 316 includes logic for randomly generating a temporary PIN (TPIN) that is in conformity with service provisioning requirements regardless of the manufacturer of the MCD or the wireless service provider. For example, the PIN logic means 316 may comprise logic for randomly generating a TPIN within a select range of numbers such as the [0xF1xxxxxx] range. Alternatively, the PIN logic may comprise logic for generating the TPIN based on such techniques as hashing of at least one hardware device identifier or subscriber identifier associated with the MCD in order to reduce the probability of two MCDs having the same TPIN. As one of ordinary skill in the art should appreciate, such identifiers comprise International Mobile station Equipment Identity (IMEI) parameters, International Mobile Subscriber Identity (IMSI) parameters, Electronic Serial Number (ESN) parameters, Mobile Identification Number (MIN) parameters, et cetera, that are hard-coded into MCDs depending on the wireless network technologies and protocols. Additionally, IP addresses corresponding to the MCDs may also operate as device identifiers for purposes of the present patent application.

Continuing to refer to FIG. 3, a registration logic module 317 provided as part of the MCD's software environment is disposed in operable communication with the transport stack 306 as well as the OS environment for effectuating registration procedures, as and when needed, with the serving relay network. In one implementation, where a PIN is not provided otherwise, the registration logic module 317 includes logic means operable to execute a registration procedure with the serving relay node using a PIN indicium returned from the relay in response to the MCD's PIN request.

FIG. 4 depicts a flowchart of an embodiment for dynamically assigning a personalized indicium such as PIN indicium to an MCD. When the MCD is manufactured, it may not be assigned any PIN indicium (i.e., a "blank" MCD) suitable for engaging in data sessions mediated via a relay network, although it is typically coded with one or more device identifiers. Additionally, once the MCD is deployed, it may be provided with an IP address since it is an IP appliance operable with a wireless packet data service network. Upon activation, a PIN request may be transmitted by the MCD to a network node with registration services for assignment of a PIN (block 402). In one implementation, such a request may be effectuated prior to any registration procedure required of the MCD. As explained hereinabove, appropriate PIN logic provided with the MCD is operable to generate a TPIN, preferably based on the MCD's device/subscriber identifier(s) in order to reduce collisions, which is transmitted as a parameter in the PIN request message. One or more device/subscriber identifiers such as IP address, IMEI, IMSI, ESN, MIN, et cetera, are also transmitted via the PIN request. Responsive thereto, the registration server queries a provisioning system in order to validate the PIN request, including the parametric information therein (block 404). Upon validating the request, a PIN response message is provided by the relay network node that includes a "permanent" PIN (which may be generated dynamically or selected from a pool of provisioned PINs) assigned to the MCD (blocks 406, 408), In one implementation, the PIN response message may include a pending time window (i.e., a "lifetime" parameter) associated with the "permanent" PIN such that if the MCD fails to execute a successful registration procedure using the assigned PIN within the pending time window, the assigned PIN may be disassociated by the provisioning logic. On the other hand, if a successful registration procedure is executed within the time window, the provisioning logic may persistently bind the assigned PIN to one or more device and/or subscriber identifiers of the MCD in its device/subscriber tables. It should therefore be appreciated that such flexibility in dynamically assigning PINs imparts additional PIN management capability to the provisioning logic of a network not only with respect to avoiding PIN collisions but also where security and reliability issues are involved, e.g., a permanent PIN is lost or an unauthorized MCD attempts to gain access to the network using a stolen PIN.

FIG. 5 depicts a message flow diagram with respect to an exemplary dynamic PIN assignment mechanism according to one embodiment. A PIN request message 502 is transmitted by MCD 116 to a network node, e.g., registration server 216, wherein the request message 502 includes TPIN as well as device/subscriber identifier indicia as parametric information. Registration server 216 queries suitable service logic, which may be embodied as the provisioning system 218 associated with the relay services network described above, by issuing a PIN query 504 thereto, which includes the parametric information received in the PIN request 502. The provisioning system's validation logic 506 is operable to authenticate the request (if encrypted), validate the identifier information, and ensure that the TPIN is within a select range, etc. Upon successful validation, a "permanent" PIN (PPIN) is provided via a query reply 508 to the registration server 216, from where it is transmitted to MCD 116 via a PIN response message 510. As alluded to previously, additional parametric information (e.g., PIN lifetime) may be provided as part of the response message 510. A registration request 512 using PPIN may then be executed by MCD 116. In response, the registration server 216 is operable to interrogate the provisioning system via a registration validation query 514 for PIN validation and permanent assignment 516. Upon successful validation, the PPIN is persistently bound to one or more identifiers of the MCD, e.g., its IMEI (if GPRS or IDEN) or ESN (if CDMA). Otherwise, the assigned PIN is disassociated from the MCD's identifiers and returned to the PIN pool for recycling. A validation reply message 518 is thereafter provided to the registration server 216, which then transmits an appropriate registration response message 520 to MCD 116.

In one embodiment, the interface between the provisioning system and the relay node modules for effectuating dynamic PIN request messaging may be implemented as a HyperText Transfer Protocol (HTTP) interface, using any Markup Language. However, it should be apparent that other messaging interfaces may also be provided for such purposes in accordance with the teachings of the present patent application. The following tables set forth exemplary payload formats of dynamic PIN request and response messages according to one implementation: <tables id="tabl0001" num="0001"><table frame="all"><title>TABLE I (Dynamic PIN Request)</title><tgroup cols="4" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="30mm" colsep="1" /><colspec colnum="2" colname="col2" colwidth="36mm" colsep="1" /><colspec colnum="3" colname="col3" colwidth="41mm" colsep="1" /><colspec colnum="4" colname="col4" colwidth="60mm" colsep="1" /><thead><row><entry namest="col1" nameend="col1" align="left" valign="top"><b>Parameter Name</b></entry><entry namest="col2" nameend="col2" align="left" valign="top"><b>Content Format</b></entry><entry namest="col3" nameend="col3" align="left" valign="top"><b>Examples</b></entry><entry namest="col4" nameend="col4" align="left" valign="top"><b>Notes</b></entry></row></thead><tbody><row><entry namest="col1" nameend="col1" align="left" valign="top">IMEI</entry><entry namest="col2" nameend="col2" align="left" valign="top">String</entry><entry namest="col3" nameend="col3" align="left" valign="top">001004100300790</entry><entry namest="col4" nameend="col4" align="left" valign="top">Mandatory when the device is GPRS or IDEN</entry></row><row><entry namest="col1" nameend="col1" align="left" valign="top">ESN</entry><entry namest="col2" nameend="col2" align="left" valign="top">String (ddd/dddddddd)</entry><entry namest="col3" nameend="col3" align="left" valign="top">076/00319130</entry><entry namest="col4" nameend="col4" align="left" valign="top">Mandatory when the device is CDMA</entry></row><row><entry namest="col1" nameend="col1" align="left" valign="top">IMSI</entry><entry namest="col2" nameend="col2" align="left" valign="top">String</entry><entry namest="col3" nameend="col3" align="left" valign="top">302720200027430</entry><entry namest="col4" nameend="col4" align="left" valign="top">Optional</entry></row><row><entry namest="col1" nameend="col1" align="left" valign="top">MSISDN</entry><entry namest="col2" nameend="col2" align="left" valign="top">String</entry><entry namest="col3" nameend="col3" align="left" valign="top">9054445555</entry><entry namest="col4" nameend="col4" align="left" valign="top">Optional</entry></row><row><entry namest="col1" nameend="col1" align="left" valign="top">ICCID</entry><entry namest="col2" nameend="col2" align="left" valign="top">String</entry><entry namest="col3" nameend="col3" align="left" valign="top">893027203020005 51500</entry><entry namest="col4" nameend="col4" align="left" valign="top">Optional</entry></row><row><entry namest="col1" nameend="col1" align="left" valign="top">MDN</entry><entry namest="col2" nameend="col2" align="left" valign="top">String</entry><entry namest="col3" nameend="col3" align="left" valign="top">9056294746</entry><entry namest="col4" nameend="col4" align="left" valign="top">Optional (CDMA)</entry></row><row><entry namest="col1" nameend="col1" align="left" valign="top">SIMID</entry><entry namest="col2" nameend="col2" align="left" valign="top">String</entry><entry namest="col3" nameend="col3" align="left" valign="top">000800525601300</entry><entry namest="col4" nameend="col4" align="left" valign="top">Optional (IDEN)</entry></row></tbody></tgroup></table></tables><tables id="tabl0002" num="0002"><table frame="all"><title>TABLE II (Dynamic PIN Response)</title><tgroup cols="6" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="28mm" colsep="1" /><colspec colnum="2" colname="col2" colwidth="28mm" colsep="1" /><colspec colnum="3" colname="col3" colwidth="27mm" colsep="0" /><colspec colnum="4" colname="col4" colwidth="28mm" colsep="0" /><colspec colnum="5" colname="col5" colwidth="28mm" colsep="1" /><colspec colnum="6" colname="col6" colwidth="29mm" colsep="1" /><thead><row><entry namest="col1" nameend="col1" align="left" valign="top"><b>Parameter Name</b></entry><entry namest="col2" nameend="col2" align="left" valign="top"><b>Content Format</b></entry><entry namest="col3" nameend="col5" colsep="1" rowsep="1" align="left" valign="top"><b>Examples</b></entry><entry namest="col6" nameend="col6" align="left" valign="top"><b>Notes</b></entry></row></thead><tbody><row><entry namest="col1" nameend="col1" align="left" valign="top">DynamicPin</entry><entry namest="col2" nameend="col2" align="left" valign="top">PIN native format</entry><entry namest="col3" nameend="col5" colsep="1" rowsep="1" align="left" valign="top">20AA0055</entry><entry namest="col6" nameend="col6" align="left" valign="top">When the request is successful</entry></row><row rowsep="0"><entry namest="col1" nameend="col1" morerows="5" rowsep="1" align="left" valign="top">ErrorCode</entry><entry namest="col2" nameend="col2" morerows="5" rowsep="1" align="left" valign="top">Decimal String</entry><entry namest="col3" nameend="col5" colsep="1" rowsep="0" align="left" valign="top">3 Possible Values:</entry><entry namest="col6" nameend="col6" morerows="5" rowsep="1" align="left" valign="top">When PRV failed to fulfill the request</entry></row><row rowsep="0"><entry namest="col3" nameend="col3" align="left" valign="top">•</entry><entry namest="col4" nameend="col5" colsep="1" rowsep="0" align="left" valign="top">- 100 - Missing ESN or IMEI in</entry></row><row rowsep="0"><entry namest="col3" nameend="col4" align="left" valign="top">request</entry><entry namest="col5" nameend="col5" align="left" valign="top" /></row><row rowsep="0"><entry namest="col3" nameend="col3" align="left" valign="top">•</entry><entry namest="col4" nameend="col4" align="left" valign="top">-100-ESN or IMEI</entry><entry namest="col5" nameend="col5" align="left" valign="top">of</entry></row><row rowsep="0"><entry namest="col3" nameend="col4" colsep="0" rowsep="0" align="left" valign="top">MCD suitable</entry><entry namest="col5" nameend="col5" align="left" valign="top">without software</entry></row><row><entry namest="col3" nameend="col3" align="left" valign="top">•</entry><entry namest="col4" nameend="col5" colsep="1" rowsep="1" align="left" valign="top">-200-PRV system error</entry></row><row><entry namest="col1" nameend="col1" align="left" valign="top">Lifetime</entry><entry namest="col2" nameend="col2" align="left" valign="top">Decimal String</entry><entry namest="col3" nameend="col5" colsep="1" rowsep="1" align="left" valign="top">Minutes</entry><entry namest="col6" nameend="col6" align="left" valign="top">Pending lifetime of PIN</entry></row><row><entry namest="col1" nameend="col1" align="left" valign="top">ErrorDescr</entry><entry namest="col2" nameend="col2" align="left" valign="top">String</entry><entry namest="col3" nameend="col5" colsep="1" rowsep="1" align="left" valign="top">A detailed description of the error such as "ESN or IMEI not recognized as provisioned MCD"</entry><entry namest="col6" nameend="col6" align="left" valign="top">When PRV failed to fulfill the request</entry></row></tbody></tgroup></table></tables>

FIG. 6A depicts a flowchart of an embodiment of a PIN pool management mechanism according to one embodiment wherein PIN indicia are dynamically assigned. Upon receiving a dynamic PIN assignment request by an MCD (block 602), the network service logic makes a determination whether a device identifier (e.g., IMEI) is provided (block 604). If so, a device table is queried (block 606) to determine if any PIN is already associated with the IMEI parameter (block 608). If affirmative, a further determination is made as to whether the PIN was dynamically assigned (block 618). If the PIN was not dynamically assigned or if there was no IMEI, the flow control returns an error (block 620). On the other hand, if the PIN was already associated with IMEI and the PIN was dynamically assigned, the validation is complete and the PIN is returned (block 622).

If the device's IMEI is not associated with any PIN (as determined by block 608), the service logic determines whether there are any recycled PINs (block 610). If so, one of the PINs from the recycled PIN pool is removed (block 616) for creating a PIN-IMEI association (e.g., an entry in the devices table) (block 614), whereupon the PIN is returned (block 622). If no recycled PIN is available, a new PIN is allocated from one of the PIN ranges configured (block 612). Thereafter, a PIN-IMEI association is created and the PIN is returned (blocks 614, 422).

FIG. 6B depicts a flowchart of an embodiment for registering an MCD using a dynamically assigned PIN. Upon issuing a registration request by the MCD (block 650), which includes PIN and device identifier information such as, e.g., IMEI, the network service logic determines if IMEI is associated with a provisioned MCD (block 652). If so, a further determination is made whether the PIN in the registration request is the same as the PIN dynamically assigned to the IMEI parameter (block 654). If affirmative, the flow control proceeds with the registration process in normal manner (block 656). If the PIN in the registration request is different from the PIN dynamically assigned to the IMEI parameter, yet another determination is made whether the PIN in the registration request exists in the provisioning database (block 658). If not, the registration as well as the PIN is blocked in the serving relay node (block 660). Otherwise, the registration process continues (block 662), signifying that the MCD was assigned a valid PIN via some other mechanism (e.g., a "non-blank" MCD).

FIG. 7 depicts a block diagram of a mobile communications device operable according to one embodiment. It will be recognized by those skilled in the art upon reference hereto that although an embodiment of MCD 116 may comprise an arrangement similar to one shown in FIG. 7, there can be a number of variations and modifications, in hardware, software or firmware, with respect to the various modules depicted. Accordingly, the arrangement of FIG. 7 should be taken as illustrative rather than limiting with respect to the embodiments of the present patent application. A microprocessor 702 providing for the overall control of an embodiment of MCD 116 is operably coupled to a communication subsystem 704 which includes a receiver 708 and transmitter 714 as well as associated components such as one or more local oscillator (LO) modules 710 and a processing module such as a digital signal processor (DSP) 712. As will be apparent to those skilled in the field of communications, the particular design of the communication module 704 may be dependent upon the communications network with which the mobile device is intended to operate. In one embodiment, the communication module 704 is operable with both voice and data communications. Regardless of the particular design, however, signals received by antenna 706 through BS 114 are provided to receiver 708, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, analog-to-digital (A/D) conversion, and the like. Similarly, signals to be transmitted are processed, including modulation and encoding, for example, by DSP 712, and provided to transmitter 714 for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification and transmission over the air-radio interface via antenna 716.

Microprocessor 702 also interfaces with further device subsystems such as auxiliary input/output (I/O) 718, serial port 720, display 722, keyboard 724, speaker 726, microphone 728, random access memory (RAM) 730, a short-range communications subsystem 732, and any other device subsystems generally labeled as reference numeral 733. To control access, a Subscriber Identity Module (SIM) or Removable user Identity Module (RUIM) interface 734 is also provided in communication with the microprocessor 702. In one implementation, SIM/RUIM interface 734 is operable with a SIM/RUIM card having a number of key configurations 744 and other information 746 such as identification and subscriber-related data.

Operating system software and transport stack software may be embodied in a persistent storage module (i.e., non-volatile storage) such as Flash memory 735. In one implementation, Flash memory 735 may be segregated into different areas, e.g., storage area for computer programs 736 as well as data storage regions such as device state 737, address book 739, other personal information manager (PIM) data 741, and other data storage areas generally labeled as reference numeral 743. Additionally, a PIN logic module 748 is provided for generating a temporary PIN according to the teachings set forth hereinabove.

It is believed that the operation and construction of the embodiments of the present patent application will be apparent from the Detailed Description set forth above. While the exemplary embodiments shown and described may have been characterized as being preferred, it should be readily understood that various changes and modifications could be made therein without departing from the scope of the present invention as set forth in the following claims.