U.S. patent application number 15/156085 was filed with the patent office on 2016-09-08 for wireless communication provisioning using state transition rules.
The applicant listed for this patent is Jasper Technologies, Inc.. Invention is credited to Scott Barkley, Amit Gupta, Zhongling Li.
Application Number | 20160261970 15/156085 |
Document ID | / |
Family ID | 50781401 |
Filed Date | 2016-09-08 |
United States Patent
Application |
20160261970 |
Kind Code |
A1 |
Barkley; Scott ; et
al. |
September 8, 2016 |
WIRELESS COMMUNICATION PROVISIONING USING STATE TRANSITION
RULES
Abstract
A method for wireless communication provisioning is disclosed. A
first wireless communication provisioning state associated with one
or more identifiers is defined. A second wireless communication
provisioning state associated with one or more identifiers is
defined. A state transition rule is defined, wherein the state
transition rule defines a transition between the first wireless
communication provisioning state and the second wireless
communication provisioning state, wherein the first wireless
communication provisioning state and the second wireless
communication provisioning state are based on the lifecycle of the
service of a wireless communication device associated with the
first and second wireless communication provisioning states.
Inventors: |
Barkley; Scott; (San Mateo,
CA) ; Gupta; Amit; (Livermore, CA) ; Li;
Zhongling; (Fremont, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Jasper Technologies, Inc. |
Santa Clara |
CA |
US |
|
|
Family ID: |
50781401 |
Appl. No.: |
15/156085 |
Filed: |
May 16, 2016 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
14793960 |
Jul 8, 2015 |
9338636 |
|
|
15156085 |
|
|
|
|
14226269 |
Mar 26, 2014 |
9084088 |
|
|
14793960 |
|
|
|
|
11804582 |
May 18, 2007 |
8745184 |
|
|
14226269 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04W 12/00514 20190101;
H04W 8/04 20130101; H04W 84/042 20130101; H04W 4/50 20180201; H04M
2215/7231 20130101; H04W 4/24 20130101; H04M 15/80 20130101; H04W
12/06 20130101; H04W 8/02 20130101; H04M 15/7556 20130101 |
International
Class: |
H04W 4/00 20060101
H04W004/00 |
Claims
1. A method for wireless communication provisioning comprising:
defining a first wireless communication provisioning state
associated with one or more identifiers; defining a second wireless
communication provisioning state associated with the one or more
identifiers; and defining a state transition rule wherein the state
transition rule defines a transition between the first wireless
communication provisioning state and the second wireless
communication provisioning state, wherein the first wireless
communication provisioning state and the second wireless
communication provisioning state are based on the lifecycle of the
service of a wireless communication device associated with the
first and second wireless communication provisioning states.
Description
[0001] This application is a continuation of U.S. patent
application Ser. No. 14/793,960 entitled WIRELESS COMMUNICATION
PROVISIONING USING STATE TRANSITION RULES filed on Jul. 8, 2015
which is a continuation of U.S. patent application Ser. No.
14/226,269 filed Mar. 26, 2014 and issued as U.S. Pat. No.
9,084,088 on Jul. 14, 2015, which is based up and claims the
benefit of priority for prior U.S. patent application Ser. No.
11/804,582, filed on May 18, 2007 and issued as U.S. Pat. No.
8,745,184 on Jun. 3, 2014, the entire contents of which are
incorporated herein by reference.
[0002] Mobile data communications can enable a wide variety of
services. However, mobile data providers, such as cell phone
providers, mobile virtual network operators (MVNO's), or mobile
virtual network enablers (MVNE's), have processes--for example,
provisioning processes--that are tailored for standard cell phone
services. In particular, an equipment provider or another type of
customer for mobile data communications may desire to provide
equipment enabled to use mobile data communications. In order to
test that the equipment is fully functional with a mobile data
communications provider, the equipment provider in the current
environment most likely will be required to completely activate the
equipment (i.e. provision it) including establishing a service plan
with customer billing. When the testing is complete, the service
plan will likely be terminated, and the final customer will be
required to reactivate the service plan with customer billing. It
would be beneficial if the mobile data providers' processes--for
example, provisioning--could be tailored for the needs of customers
of mobile data communications.
BRIEF DESCRIPTION OF THE DRAWINGS
[0003] Various embodiments of the invention are disclosed in the
following detailed description and the accompanying drawings.
[0004] FIG. 1 illustrates a block diagram of an embodiment of a
system for mobile data communication provisioning.
[0005] FIG. 2 is a flow diagram illustrating an embodiment of a
process for mobile data communication provisioning.
[0006] FIG. 3 is a block diagram illustrating an embodiment of a
state definition.
[0007] FIG. 4 illustrates an embodiment of a state transition rule
definition.
[0008] FIG. 5 is a flow diagram illustrating an embodiment of
states of a channel sale model for provisioning and the transitions
between the states.
[0009] FIG. 6 is a flow diagram illustrating an embodiment of
states of a retail sale model for provisioning and the transitions
between the states.
[0010] FIG. 7 is a flow diagram illustrating an embodiment of a
process for provisioning wireless communication.
DETAILED DESCRIPTION
[0011] The invention can be implemented in numerous ways, including
as a process, an apparatus, a system, a composition of matter, a
computer readable medium such as a computer readable storage medium
or a computer network wherein program instructions are sent over
optical or electronic communication links. In this specification,
these implementations, or any other form that the invention may
take, may be referred to as techniques. A component such as a
processor or a memory described as being configured to perform a
task includes both a general component that is temporarily
configured to perform the task at a given time or a specific
component that is manufactured to perform the task. In general, the
order of the steps of disclosed processes may be altered within the
scope of the invention.
[0012] A detailed description of one or more embodiments of the
invention is provided below along with accompanying figures that
illustrate the principles of the invention. The invention is
described in connection with such embodiments, but the invention is
not limited to any embodiment. The scope of the invention is
limited only by the claims and the invention encompasses numerous
alternatives, modifications and equivalents. Numerous specific
details are set forth in the following description in order to
provide a thorough understanding of the invention. These details
are provided for the purpose of example and the invention may be
practiced according to the claims without some or all of these
specific details. For the purpose of clarity, technical material
that is known in the technical fields related to the invention has
not been described in detail so that the invention is not
unnecessarily obscured.
[0013] Wireless communication provisioning using state transition
rules associated with an identifier is disclosed. A first state
associated with one or more identifiers is defined. A second state
associated with one or more identifiers is defined. A state
transition rule is defined between the first and second states. In
some embodiments, an identifier of the one or more identifiers is a
subscriber identity module (SIM). In some embodiments, a plurality
of states are defined, a plurality of state transition rules are
defined, and a group of states and transition rules are selected
and associated with one or more identifiers. In some embodiments,
wireless communications comprise mobile data, mobile cellular
communications, or any other appropriate wireless
communications.
[0014] In some embodiments, a customer organization defines a
sequence of states for devices that communicate data with a
customer application server via one or more wireless carrier
networks. The provider enables the communication via the wireless
carrier networks. The plurality of states enables the activity of
provisioning of a customer device or provider device used in the
data communication with appropriate billing, access, and/or
authorization for each activity especially with regard to testing,
activation, deactivation, etc.
[0015] FIG. 1 illustrates a block diagram of an embodiment of a
system for mobile data communication provisioning. In the example
shown, device 100 comprises a mobile device that communicates data.
Device 100 includes a mobile data service (MDS) 102--for example,
general packet radio service--and an identifier (ID) 104--for
example, a subscriber identifier module. Data can be transmitted
and received by device 100 using MDS 102. Device 100 is identified
using ID 104 and associated with a user or customer. Transmissions
and receptions of data communicate with carrier network 112, which
is associated with MDS 102. In various embodiments, the carrier
network associated with MDS 102 comprises a mobile carrier network,
a cell phone network, a messaging network, wireless communication
network, or any other appropriate network for communicating data to
a mobile device.
[0016] Carrier network 112 includes carrier switching network 110
(e.g., SGSN--serving General Packet Radio Services (GPRS) support
node--used in Global System for Mobile Communications (GSM)
networks), carrier data traffic handler 108 (e.g., GRX--a GPRS
roaming exchange and/or SS7--signaling system 7 system), and a
plurality of carrier towers--represented in FIG. 1 by tower 106.
Communications of data traffic to and from device 100 are received
by carrier network 112 by a carrier tower, which communicates the
data traffic with carrier data traffic handler 108. Carrier data
traffic handler 108 communicates data traffic with carrier
switching network 110. Carrier switching network 110 can
communicate with network 114, and Authentication Center/Home
Location Register (HLR) 128 and Authentication, Authorization, and
Accounting (AAA) Server (e.g., a Radius server) 130 of provider
system 124
[0017] Network 114 enables communication with customer system 116,
which includes customer application server 118 and customer
administrator 120. In some embodiments, network 114 comprises the
internet, a local area network, a wide area network, a wired
network, a wireless network, or any other appropriate network or
networks for communicating with customer system 116. Customer
application server 118 receives data from and transmits data to
device 100 regarding the customer's services or products. In
various embodiments, the customer's services includes transaction
related services, monitoring services, and/or location tracking
services. In some embodiments, a state transition rule defining
transition from one provisioning state to another provisioning
state associated with device 100 is implemented on customer
application server 118. In some embodiments, a state transition
rule defining transition from one provisioning state to another
provisioning state associated with device 100 is not known to
device 100.
[0018] Provider system 124 includes HLR 128, AAA server 130,
application server 126, database (DB) 132, administrator 134.
Provider system 124 enables customer services by enabling data
communication services via the carrier network with device 100. HLR
128 enables communication with the provider system by indicating if
device 100 is allowed to have data communication through carrier
network 112 with customer system 116. AAA server 130 enables
specific permissions that are available regarding data
communications between device 100 and customer system 116 via
carrier network 112. Application server 126 enables provisioning
and billing for the provider. Provisioning comprises enabling
devices such as device 100 to have mobile data communication
services using a mobile carrier network. DB 132 includes
information related to provisioning and billing for the provider.
Administrator 134 administrates provider system. Customer system
administrator 120 communicates with provider application server 126
to administrate customer system usage, billing, provisioning for
data communication service of carrier network 112 enable by
provider 124. In some embodiments, functionality of HLR 128 and AAA
server 130 are performed by the same server, are partitioned
between two servers but not exactly as described herein, or any
other server configuration to achieve the same functionality.
[0019] FIG. 2 is a flow diagram illustrating an embodiment of a
process for mobile data communication provisioning. In some
embodiments, the process of FIG. 2 helps provision device 100 of
FIG. 1 such that mobile data and/or wireless communications is
available via carrier network 112 to customer system 116. In the
example shown, in 200 states associated with one or more
identifiers are defined. States that are associated with one or
more identifiers can include test ready, inventory, activation
ready, activated, deactivated, retired, return merchandise
authorization (RMA), suspend, fraud review, purged, and/or any
other appropriate states. In various embodiments, the identifier
comprises a SIM, an International Circuit Card Identifier (ICCID),
an international mobile subscriber identifier (IMSI), a customer
identifier, a user identifier, or a device identifier. In various
embodiments, the one or more identifiers comprises an identifier
associated with a user, a customer, a company, an organization,
etc. or a group of identifiers associated with a user, a customer,
a company, an organization, etc.
[0020] In some embodiments, one or more states are based on the
lifecycle of the service of a wireless communication device.
[0021] A test ready state can be used to allow a manufacturer to
test a SIM, or a device with a SIM, and its network communication
infrastructure before delivering the SIM, or device with a SIM, to
an end user, a retail location, or a distributor. A test ready
state can be a default state for a SIM that allows authentication
and authorization with a provider's HLR and AAA server, but does
not have any billing associated with it. A SIM in a test ready
state is able to conditionally transact data, voice, and/or Short
Message Service (SMS) communications--for example, some limits may
be placed on the communications while in this state such as:
communication may occur up to a maximum data transmitted/received
amount or up to a maximum number of days since the initial data
communication. A test ready state may have no prerequisite state,
have no limitation to a next state (e.g., all states allowed as
next state), have no exclusivity rule, be a required state, and be
allowed to have automatic and/or manual transitions.
[0022] An inventory state can be used to allow a SIM to be placed
in a device and associated with an identifier of the device (e.g.,
a terminal identifier or a point of sale terminal identifier). An
inventory state cannot coexist with an activation ready state. An
inventory state cannot connect with the network and requires a
manual change in order to change state. An inventory state may have
a test ready state as a prerequisite, have no limitation to a next
state (e.g., all states allowed as next state), have an exclusivity
rule in that it cannot coexist with an activation ready state, not
be a required state, and be allowed only to have manual
transitions.
[0023] An activation ready state can be used to allow a SIM to be
ready to be activated. An activation ready state will authenticate
and authorize with the HLR and AAA server of the provider system,
but no billing will occur. After the first data communication
(e.g., first packet data protocol (PDP) context communication), the
SIM state will automatically change to an activated state. An
activation ready state may have a test ready state or inventory
state as a prerequisite, have no limitation to a next state (e.g.,
all states allowed as next state), have an exclusivity rule in that
it cannot coexist with an inventory state, not be a required state,
and be allowed to have an automatic transition to an activated
state or a manual transition to other states.
[0024] An activated state can be used to allow a SIM, or a device
with a SIM, to be used by a user. In an activated state the SIM
will authenticate and authorize on the HLR and AAA server of the
provider system. Billing commences immediately on changing to this
state. The provider system may check to make sure that the proper
information is contained on the HLR and AAA server databases as
well as the billing databases. In some cases, the checks will
include checking the identifiers (e.g., SIM, international mobile
subscriber identifier (IMSI), customer identifier, device
identifier, etc.). An activated state may have a test ready state,
inventory, or activation ready state as a prerequisite, have
possible next states of deactivated, purged, or retired, have no
exclusivity rule, not be a required state, and be only allowed to
have a manual transition to a next state.
[0025] A deactivated state can be used to allow a SIM, or a device
with a SIM, to be deactivated by the user. In a deactivated state
the SIM will not be allowed to authenticate and will not be billed.
The AAA server of the provider system and the gateway GPRS support
node (GGSN) of carrier networks will be sent a notification (e.g.,
a packet) informing them that the SIM has been deactivated. An
deactivated state may have a activated state as a prerequisite,
have possible next states of activated, purged, or retired, have no
exclusivity rule, not be a required state, and be only allowed to
have a manual transition to a next state.
[0026] A retired state can be used to allow a SIM, or a device with
a SIM, to be retired by the provider or the user. In a retired
state the SIM will not be allowed to authenticate and billing ends.
A retired state may have any state as a prerequisite except purged,
have any possible next states (i.e., all states possible), have no
exclusivity rule, not be a required state, and be only allowed to
have a manual transition to a next state.
[0027] A purged state can be used to allow a SIM, or a device with
a SIM, to be purged by the provider. In a purged state the SIM will
not be allowed to authenticate and the SIM is removed from the
system (e.g., IMSI permanently removed from the HLR of the provider
system). A purged state may have any state as a prerequisite, have
no possible next states, have no exclusivity rule, not be a
required state, and be not allowed to have any transitions to a
next state.
[0028] In some embodiments, a state is defined by a customer. In
some embodiments, the state is defined using an Internet-based
service.
[0029] In some embodiments, a state definition does not support
communication sessions and a transition to that state will
terminate existing open communication sessions.
[0030] In some embodiments, a first wireless communication
provisioning state allows a communication device to pass traffic
without incurring any billing charges, and an associated state
transition rule allows an automated transition to a second
provisioning state where the second provisioning state incurs
billing charges. In some embodiments, a first wireless
communication provisioning state allows a communication device to
pass traffic without incurring any billing charges, and an
associated state transition rule allows an automated transition to
the second provisioning state, where the second provisioning state
does not allow the communication device to pass traffic.
[0031] In 202, state transition rule(s) between two states is/are
defined. A transition from one state to another may occur
automatically on a predetermined condition or manually. If the
transition is based on a condition is met (e.g., upon first data
communication--packet data protocol context established), the state
will automatically change from one to another (e.g., activation
ready state to activated state). In various embodiments, the
transition condition is based on one or more of the following: a
predetermined amount of elapsed time since a prior state
transition, an amount of service usage above a predetermined amount
of service usage, one or more service signalings, or any other
appropriate condition. In various embodiments, the condition is
based on an exclusivity rule, a state rule, a communication data
transfer, or any other appropriate condition. A manual change from
one state to another requires an intervention directly from the
provider system--for example, an action through a manager portal,
by uploading a file to the SIM or device with the SIM, or an
application programming interface (API) call.
[0032] In various embodiments, a state transition rule can be
defined for an individual device or a group of devices, or
different rules can be defined for different individual devices or
different groups of devices, or any other appropriate combination
as appropriate for meeting the needs of a supplier of devices.
[0033] In some embodiments, a group of states are defined and a
group of transition rules are defined, and then a selection of
states and transition rules are associated with one or more
identifiers.
[0034] In some embodiments, a customer selects a state transition
rule. In some embodiments, a customer defines a state transition
rule. In various embodiments, the state transition rule is selected
and/or defined using an Internet-based service, using a local
program interface, or any other appropriate manner of selecting and
defining a state transition rule.
[0035] In some embodiments, a state transition rule when activated
terminates existing communication sessions.
[0036] FIG. 3 is a block diagram illustrating an embodiment of a
state definition. In some embodiments, a state is associated with
an identifier--for example, a SIM, a device identifier (e.g., an
international mobile equipment identifier), a vendor identifier, or
any other appropriate identifier. In the example shown, a state
definition includes state name, state description, required state
flag, prerequisite state, allowed next state(s), exclusivity rule,
and transition mode(s) available that describe conditions allowing
transitions between states. For example, a test ready state has: a)
a state name of test ready; b) a state description of SIM is able
to tested in its operation with the network by a manufacturer in a
limited manner without being billed; c) a required state flag
indicating that the test ready state is required; d) there is no
prerequisite state for the test ready state; e) allowed next states
from test ready are inventory, activation ready, activated,
retired, or purged; f) there is no exclusivity rule for the test
ready state; and g) the transition modes available are automatic to
either an inventory state or an activation ready state based on an
exclusivity rule or manual change.
[0037] FIG. 4 illustrates an embodiment of a state transition rule
definition. In various embodiments, a state transition rule
definition is associated with a state associated with an identifier
or an identifier. In the example shown, a state transition rule
definition includes current state, transition condition, state
transitioned to, and transition description. For example, a SIM can
be manually changed from an inventory state to an activation ready
state when the device that the SIM is in is deployed by selling the
unit to a retail customer, by having a service provider place the
unit in the field, or by any other appropriate manner. For another
example, a SIM can be automatically changed from an activation
ready state to an active state when a PDP context is established
and data is communicated to and from the SIM, or device with the
SIM in it.
[0038] FIG. 5 is a flow diagram illustrating an embodiment of
states of a channel sale model for provisioning and the transitions
between the states. In some embodiments, the starting default state
of a SIM is the test ready state. In the example shown, in test
ready state 500 a device is ready for testing. The SIM is shipped
in the test ready state to an original equipment manufacturer
(OEM)--for example, a customer wanting to use the connectivity
services provided by the provider which enables a user's device to
have data communication to the customer via one or more carrier
networks. In test ready state 500, the SIM is allowed to provision
and establish a PDP session (e.g., it can connect to GGSN of a
carrier network, connect to internet, and connect to the customer's
application server). When the SIM is in the test ready state, no
billing to the OEM occurs. This connectivity is allowed for until
the transition 501. Transition 501 from the test ready state is
either a manually triggered transition or an automatically
triggered based on a condition where the condition is the when the
SIM has reached: 1) a maximum number of PDP sessions has
occurred--for example, 10; 2) a maximum amount of data has been
transmitted/received to and from the SIM/device via the carrier
network--for example, 100 Kbytes; or 3) a maximum amount of time
has elapsed since the first PDP context in this test ready
state--for example, 90 days. When the transition is triggered, then
the SIM switches to inventory state 502.
[0039] In inventory state 502, a device is waiting to be
transferred to a user. In this state, no connectivity is enabled,
and no billing occurs. The state is maintained until transition
503. Transition 503 occurs when the OEM or the customer or its
channel service providers manually triggers a state change. When
the state change is triggered, the SIM is changed to activated
state 504. In activated state 504, a device is being used by user.
In activated state 504, the SIM is able to establish a PDP session
and connect and transfer data to a customer application server via
a carrier network. The user is billed for the service provided by
the provider. Billing information is provided to the customer by
gathering the relevant data from the network carriers and the
provider's data bases. The SIM remains in the active state until
triggered to transition. Transition 505 may be triggered manually
or automatically. In various embodiments, transition 505 is
triggered automatically by a maximum number of connections allowed,
a maximum amount of data transferred, a maximum amount of time
since the start of PDP sessions, or any other appropriate automatic
trigger condition. In some embodiments, the user or the customer
can also manually trigger transition 505 to a deactivated state
506.
[0040] In deactivated state 506, a device is finished being used as
requested by an end user or by a customer system request by being
in a deactivated state. In deactivated state 506, the SIM is not
able to connect and establish a PDP session. While in deactivated
state 506, there is no billing for connectivity. Transition 507 can
be triggered automatically (e.g., after a period of time) or
manually (e.g., by the customer). When transition 507 is triggered,
the SIM changes state to purged state 508. In purged state 508, the
SIM and the device the SIM is in, is removed from the system. In
purged state 508, the SIM is not able to connect and establish a
PDP session. There is no billing associated with the trigger or the
state. Accounting for the customer may remove the item from
inventory or asset lists. Purged state 508 automatically removes
the IMSI and International Circuit Card Identifier (ICCID) from the
HLR of the provider system.
[0041] FIG. 6 is a flow diagram illustrating an embodiment of
states of a retail sale model for provisioning and the transitions
between the states. The states and transitions in FIG. 6 are
similar to the states and transitions in FIG. 5 except for the
activation ready state. In some embodiments, the starting default
state of a SIM is the test ready state. In the example shown, in
test ready state 600 a device is ready for testing. The SIM is
shipped in the test ready state to an original equipment
manufacturer (OEM)--for example, a customer wanting to use the
connectivity services provided by the provider which enables a
user's device to have data communication to the customer via one or
more carrier networks. In test ready state 600, the SIM is allowed
to provision and establish a PDP session (e.g., it can connect to
GGSN of a carrier network, connect to internet, and connect to the
customer's application server). When the SIM is in the test ready
state, no billing to the OEM occurs. This connectivity is allowed
for until the transition 601. Transition 601 from the test ready
state is either a manually triggered transition or an automatically
triggered based on a condition where the condition is the when the
SIM has reached: 1) a maximum number of PDP sessions has
occurred--for example, 5; 2) a maximum amount of data has been
transmitted/received to and from the SIM/device via the carrier
network--for example, 1 Mbytes; or 3) a maximum amount of time has
elapsed since the first PDP context in this test ready state--for
example, 1 year. When the transition is triggered, then the SIM
switches to activation ready state 602.
[0042] In activation ready state 602, a device is waiting to be
transferred to a user. In various embodiments, the activation ready
state is set after testing by the OEM when the device is being
shipped from the OEM to retail locations, distribution partners,
directly to end users, or when the SIM, or device with the SIM, is
about to be in the end users hands but is not ready to have
billing/service fully implemented. In this state, SIM connectivity
is enabled, and a PDP session can be established. Upon the first
PDP session occurring transition 603 is triggered. When the state
change is triggered, the SIM is changed to activated state 604. In
activated state 604, a device is being used by user. In activated
state 604, the SIM is able to establish a PDP session and connect
and transfer data to a customer application server via a carrier
network. The user is billed for the service provided by the
provider. Billing information is provided to the customer by
gathering the relevant data from the network carriers and the
provider's data bases. The SIM remains in the active state until
triggered to transition. Transition 605 may be triggered manually
or automatically. In various embodiments, transition 605 is
triggered automatically by a maximum number of connections allowed,
a maximum amount of data transferred, a maximum amount of time
since the start of PDP sessions, or any other appropriate automatic
trigger condition. In some embodiments, the user or the customer
can also manually trigger transition 605 to a deactivated state
606.
[0043] In deactivated state 606, a device is finished being used as
requested by an end user or by a customer system request by being
in a deactivated state. In deactivated state 606, the SIM is not
able to connect and establish a PDP session. While in deactivated
state 606, there is no billing for connectivity. Transition 607 can
be triggered automatically (e.g., after a period of time) or
manually (e.g., by the customer). When transition 607 is triggered,
the SIM changes state to purged state 608. In purged state 608, the
SIM and the device the SIM is in, is removed from the system. In
purged state 608, the SIM is not able to connect and establish a
PDP session. There is no billing associated with the trigger or the
state. Accounting for the customer may remove the item from
inventory or asset lists. Purged state 608 automatically removes
the IMSI and International Circuit Card Identifier (ICCID) from the
HLR of the provider system.
[0044] FIG. 7 is a flow diagram illustrating an embodiment of a
process for provisioning wireless communication. In the example
shown, in 700 definitions for states associated with an identifier
are received. In some embodiments, state definitions and/or
selections are received using an internet-based application. In
various embodiments, state definitions are the same or different
for different identifiers. In various embodiments, a state for
provisioning (e.g., a device) allows billing, allows communication
sessions, allows activation, does not allow billing, does not allow
communication sessions, does not allow activation, or any other
appropriate action associated with a state. In 702, definition(s)
for state transition rule(s) between two states is/are received. In
some embodiments, state transition rule definitions and/or
selections are received using an internet-based application. In
various embodiments, the transitions are automatic or manual and
are triggered with a transition condition. In various embodiments,
the automatic and/or manual transition conditions include an
elapsed time from a prior state, prior transition, or prior
specific/any communication, an absolute time, an absolute date,
after a predetermined amount of traffic, before a predetermined
level of traffic is reached, after communication with a specific
location, number, device, service center, after sending a service
indication, a system message, after receipt of a service message,
condition, communication from a specific location, device, server,
service center, or any other appropriate transition condition. In
704, it is determined if a transition condition associated with a
transition rule for current state is met. In the event that an
appropriate transition condition has not been met, control stays
with 704. In the event that an appropriate transition condition is
met, then in 706 allow transition between the two states as
appropriate for the transition rule. In some embodiment, the
implementation of provisioning states, state transition rule
enforcement, and evaluation of transition conditions takes place on
a server that communicates with a wireless network and wireless
device.
[0045] Although the foregoing embodiments have been described in
some detail for purposes of clarity of understanding, the invention
is not limited to the details provided. There are many alternative
ways of implementing the invention. The disclosed embodiments are
illustrative and not restrictive.
* * * * *