U.S. patent application number 16/545985 was filed with the patent office on 2020-02-13 for system and method for programmatic device connectivity.
The applicant listed for this patent is Twilio Inc.. Invention is credited to Chetan Chaudhary, Evan Cummack, Brian Tarricone.
Application Number | 20200053226 16/545985 |
Document ID | / |
Family ID | 60331019 |
Filed Date | 2020-02-13 |
![](/patent/app/20200053226/US20200053226A1-20200213-D00000.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00001.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00002.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00003.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00004.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00005.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00006.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00007.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00008.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00009.png)
![](/patent/app/20200053226/US20200053226A1-20200213-D00010.png)
United States Patent
Application |
20200053226 |
Kind Code |
A1 |
Chaudhary; Chetan ; et
al. |
February 13, 2020 |
SYSTEM AND METHOD FOR PROGRAMMATIC DEVICE CONNECTIVITY
Abstract
A system and method for programmatically managing device
connectivity to a network that includes provisioning connectivity
devices with an account of a communication platform, where for a
set of the connectivity devices, provisioning includes uniquely
associating network operating identifiers of each of the
connectivity devices with a corresponding programmatic device
resource in the communication platform, setting communication
metering properties in a programmatic connectivity plan resource in
the communication platform and associating the connectivity plan
resource to at least a subset of the device resources of the
connectivity devices, and activating network communication status
of the connectivity devices; servicing communications from the
connectivity devices; and programmatically managing the
communications from the connectivity devices through at least the
device resources and the connectivity plan resources.
Inventors: |
Chaudhary; Chetan; (San
Francisco, CA) ; Cummack; Evan; (San Francisco,
CA) ; Tarricone; Brian; (San Francisco, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Twilio Inc. |
San Francisco |
CA |
US |
|
|
Family ID: |
60331019 |
Appl. No.: |
16/545985 |
Filed: |
August 20, 2019 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
16042823 |
Jul 23, 2018 |
10440192 |
|
|
16545985 |
|
|
|
|
15602809 |
May 23, 2017 |
10063713 |
|
|
16042823 |
|
|
|
|
62340333 |
May 23, 2016 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04W 4/14 20130101; H04M
15/887 20130101; H04M 2215/54 20130101; H04W 8/265 20130101; H04W
4/50 20180201; H04M 15/715 20130101 |
International
Class: |
H04M 15/00 20060101
H04M015/00; H04W 4/14 20060101 H04W004/14; H04W 8/26 20060101
H04W008/26; H04W 4/50 20060101 H04W004/50 |
Claims
1. A method comprising: provisioning a first connectivity device
and a second connectivity device with an account of a communication
platform, the first connectivity device associated with first
communication metering properties and the second connectivity
device associated with second communication metering properties;
activating network communication status of the first connectivity
device and the second connectivity device, after which
communications received from the first connectivity device are
serviced by the communication platform according to the first
communication metering properties, and communications received from
the second connectivity device are serviced by the communication
platform according to the second communication metering properties;
receiving, from a computing device of an administrator of the
account of the communication platform, a request to modify the
first communication metering properties, wherein the request is
received via an Application Programming Interface (API) exposed by
the communication platform; and modifying the first communication
metering properties based on the request, yielding modified first
communication metering properties, wherein modifying the first
communication metering properties causes communications received
from the first connectivity device to be serviced by the
communication platform according to the modified first
communication metering properties.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of and claims the benefit
of U.S. patent application Ser. No. 16/042,823, filed on 23 Jul.
2018, which is a continuation of and claims the benefit of U.S.
patent application Ser. No. 15/602,809, filed on 23 May 2017, which
claims the benefit of U.S. Provisional Application No. 62/340,333,
filed on 23 May 2016, both of which are incorporated herein by
reference.
TECHNICAL FIELD
[0002] This invention relates generally to the communication field,
and more specifically to a new and useful system and method for
programmatic device connectivity in the communication field.
BACKGROUND
[0003] More and more devices are becoming network enabled. Personal
computing devices such as phones, tablets, watches, and laptops may
be accompanied with SIM cards or other mechanisms to connect to a
carrier network. However, such connectivity is not limited to
personal computers. The internet of things trend has led to various
devices like gas meters, cars, and other devices to use internet
connectivity. Developing and managing such connectivity devices can
be complicated and expensive. In some cases, an individual will
have to establish a new long-term contract with a telecomm provider
to activate usage. This is not only cumbersome but can be
impractical for some applications where the data usage is very low.
There are numerous barriers that act as hurdles for developers and
companies. Thus, there is a need in the communication field to
create a new and useful system and method for programmatic device
connectivity. This invention provides such a new and useful system
and method.
BRIEF DESCRIPTION OF THE FIGURES
[0004] FIG. 1 is a schematic representation of a system of a
preferred embodiment;
[0005] FIG. 2 is an exemplary representation of an API response to
a request to a device usage resource;
[0006] FIG. 3 is a flowchart representation of a method of a
preferred embodiment;
[0007] FIG. 4 is a flowchart representation of processes of
provisioning a connectivity device;
[0008] FIG. 5 is an exemplary representation of an API response to
a request to a device resource;
[0009] FIG. 6 is an exemplary representation of enabled
capabilities of a connectivity plan resource;
[0010] FIG. 7 is an exemplary representation of usage limits of a
connectivity plan resource;
[0011] FIG. 8 is an exemplary communication flow diagram for
activating a connectivity device;
[0012] FIG. 9 is an exemplary communication flow diagram of
offering programmable communications using a callback URI;
[0013] FIG. 10 is an exemplary communication flow diagram of
forwarding communications to an outside service; and
[0014] FIG. 11 is an exemplary communication flow diagram for
deactivating a connectivity device.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0015] The following description of preferred embodiments of the
invention is not intended to limit the invention to these preferred
embodiments, but rather to enable any person skilled in the art to
make and use this invention.
1. Overview
[0016] A method and system for programmatic device connectivity
functions to enable connected devices to be programmatically
controlled, monitored, and/or otherwise managed. The method and
system preferably enable a programmatic approach to managing
cellular-connected IoT (Internet of Things) devices, phones,
tablets, and other computing devices, and enabling the ability to
program each call, text, and/or data packet. The method and system
are preferably implemented in connection with distributed SIM cards
(i.e. subscriber identity module cards) that operate with one or
more mobile cores used in providing data, SMS/MMS messaging, voice,
and other communication channels. The SIM cards are preferably
programmatically managed from a communication platform, which may
enable various administrative interfaces including an administrator
dashboard and/or programmatic interfaces. Programmatic interfaces
can include an API, application logic processing routines, callback
events, and/or other suitable programmatic interfaces.
[0017] The system and method are preferably implemented by a
communication platform. The communication platform is preferably a
multi-tenant platform where users are managers of different
implementations using the programmatic cellular connectivity
capabilities of the system and method. In one variation, the
communication platform is an independent computing platform that
provides functionality in cooperation with a cellular network. In
another variation, the communication platform is a component of a
cellular network system.
[0018] As one potential benefit, the system and method may enable
simplified management of device connectivity. The system and method
offer remote provisioning and ordering of SIM cards. This can be
particularly applicable when managing multiple devices. In one
application, a business may utilize the communication platform of
the system and method to manage a fleet of worker phones. The
business could control activation/deactivation of worker-used
phones, define custom functionality, programmatically augment
functionality, and/or collect data on usage. In another
application, a deployment of IoT devices could use a communication
platform's implementation of the system and method for a unified
data plan for the IoT devices that simplifies the deployment,
addition of devices, and/or billing.
[0019] As another potential benefit, the system and method can
facilitate offering a programmable mobile network, wherein various
processes of a communication network can be programmatically
controlled and customized. Where traditional wireless customers are
limited to standard features of a carrier, a programmable wireless
network could offer opportunities for any entity to build custom
rules and features that are enabled within their network.
Additionally such customization can be compatible out of network.
While a phone number may or may not be associated with a SIM card
connectivity device, the origin phone number during outbound calls
could be dynamically set through the communication platform.
Additionally, the routing of communications to a destination
address could additionally be dynamically set. In one example, a
business could use this to setup customized internal routing
options for a fleet of workers. For example, the system and method
could provide an easy approach to setting up custom phone numbers
that when dials are routed to different departments. For example, a
company could configure an implementation where dialing one directs
the caller to one department, and dialing two to another
department. Furthermore, these customized routing rules can be
customized per SIM card.
[0020] As another potential benefit, the system and method may
enable a command communication channel that can be utilized for
machine-to-machine communications. The command communication
channel can be useful for IoT and other device applications.
[0021] The method and system can be applied to a variety of use
cases. Generally, the system and method is implemented in a
multitenant platform that serves multiple entities. Through the
platform, the various entities may apply the method and system to
their own particular use cases.
[0022] In one exemplary use of the system and method, a business
may want to provide its employees with company managed phones. SIM
cards can be provisioned for all employees through the system and
method. Depending on the needs of the business, different features
may be enabled.
[0023] In one implementation, the system and method can be used in
monitoring usage. In another implementation, the system and method
could be used to simulate a virtual carrier. The connected devices
can be set to appear to be connected to the business's own carrier,
wherein the actual carrier is transparent to the end user.
[0024] In another implementation, the system and method can be used
for remotely activating, suspending, and/or deactivating devices.
This can be useful with a dynamic work force where people join and
leave.
[0025] In another implementation, the system and method could be
used for automatically encrypting all communications or
communications matching particular properties (e.g., communications
between employees or with customers). The programmatic capabilities
can detect messages and/or communications satisfying some
condition, and the message or communication could be encrypted or
otherwise converted.
[0026] In another implementation, the system and method could be
used to set custom data or communication rules. For example,
particular endpoints may be whitelisted or blacklisted for a
device. Similarly, some websites and/or network-accessed services
can be blocked for internet data communications.
[0027] In another implementation, the system and method could be
used to build custom features such as changing what phone number is
associated with a device based on various conditions such as the
location of the device or the time of day. The phone number used to
call a worker may change based on location, which may be useful for
contextually making a worker available.
[0028] In another implementation, the system and method could be
used to bridge different communication channels. For example, an
SMS sent to a fellow employee may be converted to an IP message
using a private IP messaging channel of the business.
[0029] While the system and method can be used for more traditional
phone communication use cases, the system and method could
additionally be beneficial to alternative device communication
challenges such as building an internet of things device. SIM cards
could be provisioned for a set of different computing devices. In
one aspect, the system and method can make provisioning of a SIM
card for a device a straightforward procedure for a developer or
manufacturer. The system and method can be used to enable simple
distribution of IoT devices because of a streamlined provisioning
process. The developer or manufacturer of the IoT product can
provision a SIM for a device. Then, when a customer or the IoT
device is ready to be used, the SIM card could be activated with a
data usage plan set by the customer or the developer. The developer
and the customer can be alleviated of contacting a carrier and
setting up a new carrier subscription. The system and method can
additionally enable highly customizable usage plans. Some IoT
products use very little data, and a data plan could be assigned to
that device accordingly through the system and method.
[0030] The system and method could alternatively be used for other
use cases. The examples described herein are to provide
illustrative scenarios that leverage some possible capabilities of
different implementations of the system and method.
2. System for Programmatic Device Connectivity
[0031] As shown in FIG. 1, a system for programmatic device
connectivity can include a communication platform 110, at least one
connectivity device 120, and a mobile core 130.
[0032] The communication platform 110 is preferably a multitenant
service platform. The communication platform 110 can enable
multiple distinct accounts, sub-accounts, or other entities to
utilize the platform independently. Generally, the accounts using
the communication platform 110 will be implementing some
functionality that will serve a plurality of end users. For
example, a business may create an account within the communication
platform 110 so that they can use the programmable device
connectivity features as an IT solution for the employees of the
company. In another example, an IoT device company may use the
communication platform 110 to provide the connectivity to their
devices. In a preferred implementation, the communication platform
110 can facilitate a set of communication capabilities such as PSTN
calls, IP/SIP based voice or video calls, SMS or MMS messaging, IP
messaging, third party communication channel integrations,
notifications, internet data communications, and/or other
communication operations. The communication platform 110 can
include an API service 112, an event callback system 114, and/or
application logic processing system 116.
[0033] The API service 112 functions as a programmatic interface
for managing and interacting with configuration and operational
management of connectivity devices. The API service 112 is
preferably a RESTful API but may alternatively be any suitable API
such as SOAP or custom protocol. The RESTful API works according to
an application layer request and response model. An application
layer request and response model may use an HTTP-based protocol
(HTTP or HTTPS), SPDY, or any suitable application layer protocol.
Herein, HTTP may be used, but should not be interpreted as being
limited to the HTTP protocol. HTTP requests (or any suitable
request communication) to the communication platform no preferably
observe the principles of a RESTful design. RESTful is understood
in this document to describe a Representational State Transfer
architecture as is known in the art. The RESTful HTTP requests are
preferably stateless, thus each message communicated contains all
necessary information for processing the request and generating a
response. The API service 112 can include various resources, which
act as API endpoints that can act as a mechanism for specifying
requested information or requesting particular actions. The
resources can be expressed as URI's or resource paths. In one
exemplary instance, a GET request (or other suitable method of an
application layer protocol request) can be transmitted to a URI
specifying a particular API resource. The response to the request
can include properties of the specified resource. In another
exemplary instance, a POST request (or other suitable method of an
application layer request) can be transmitted to a URI specifying a
particular resource. Properties of that request can initialize some
action and/or change in data within the communication platform.
Different resources can expose different channels to information
and/or control of the communication platform and the managed
connectivity devices. In one variation, the API service 112 can
expose a device resource, device usage resource, a connectivity
plan resource, a commands resource, and/or other resources used in
programmatically managing and interacting with connectivity devices
120.
[0034] The device resource functions to represent a physical
connectivity device capable of connecting to a wireless network. As
described below, a physical connectivity device is preferably a SIM
card used by a computing device in authenticating with a cellular
network. An individual device resource is preferably created for
each connectivity device 120. A device resource can have a number
of properties that can be set and used to augment operation of an
associated connectivity device.
[0035] The device resource will preferably include various
identifying properties such as a unique identifier and/or a
friendly name.
[0036] The device resource can additionally include a status
property. The status property can indicate the current operating
state of the associated connectivity device. The status will impact
capabilities and metering of the connectivity device. In one
variation, the different possible statuses can include "new",
"ready", "active", "suspended", "deactivated", "canceled",
"scheduled", and/or "updating". Other statuses could alternatively
be used.
[0037] During a `new` status, the connectivity device is waiting to
be activated so that it can join the network. A connectivity device
could exist in new status indefinitely at no charge. After
transitioning to read or active, the connectivity status can
preferably not return to new.
[0038] During a `ready` status, the connectivity device can connect
to the network and is capable of consuming network resources in
accordance with its connectivity plan, but no monthly fee will be
charged. Once the connectivity device has consumed some threshold
of data (e.g., 250 KB of data) and/or some time window has passed
(e.g., three months), the connectivity device can be transitioned
automatically to active status. In one exemplary use case, a
connectivity device could be set to a ready status when a
manufacturer is shipping their product using connectivity device to
a customer if the manufacturer is not sure when the device will
begin active use.
[0039] During an `active` status, the connectivity device can
connect to the network and is preferably capable of consuming
network resources in accordance with its connectivity plan.
[0040] During a `suspended` status, the connectivity device can be
blocked from connecting to the network.
[0041] During a `deactivated` status, the connectivity device can
be blocked from connecting to the network. After some time window
(e.g., 72 hours), the connectivity device can be transitioned
automatically to the terminal status canceled. This status can be
used when a customer never wants the connectivity device to
reconnect (for example a phone or IoT device has been lost or
stolen).
[0042] A `canceled` status can be a terminal status, and the
connectivity device can be blocked from connecting to the network
and can no longer be reactivated.
[0043] During a `scheduled` status, an upstream network operator
may be temporarily unable to update the status of this connectivity
device. During this state, the connectivity device status will
preferably be automatically updated to the requested status when
the upstream network operator resumes accepting transactions.
[0044] During an `updating` status, the connectivity device is in
the process of being asynchronously updated. While the connectivity
device is updating, it may not be possible to modify some fields. A
status callback URI can be used during changes in status.
[0045] Some of the statuses will be read only, but some may be set
or requested programmatically. Setting the status property of a
device resource can be used as a mechanism for requesting a
transition of the connectivity device to a new status. Exemplary
mutable statuses can include the "ready", "active", "suspended",
and "deactivated" statuses. Accordingly, the device resource can be
used for activating, suspending, or deactivating a connectivity
device through an API request to the appropriate device
resource.
[0046] The device resource can additionally include a connectivity
plan reference which functions to set a connectivity plan for the
connectivity device. The connectivity plan reference is preferably
a unique identifier of a connectivity plan resource.
[0047] The device resource can additionally include callback
references that function to define actions or functionality that is
invoked on different events. The callback references are preferably
used in connection with the event callback system 114. The callback
references are more preferably callback URIs (Universal Resource
Identifier) such as a URL (Universal Resource Locator) to a
webserver hosting application logic. There can be different types
of callback references for different aspects of the connectivity
device. Preferably, there is one that can be set for each mode of
communication such as voice, messaging, and data. Different
callback references may additionally be set for incoming versus
outgoing or other suitable aspects of connectivity. There could be
a voice callback URI, a messaging callback URI, a data callback
URI, a command callback URI, and the like. The voice callback URI
can be used for PSTN, SIP, or other forms of synchronous
communications. The messaging callback URI can be for SMS, MMS,
and/or IP messages. Additionally there could be a status callback
URI that is used during changes in status of the connectivity
device. A callback method property could additionally be set for
each callback URI so that application layer protocol communications
can use appropriate methods. For example, when using an HTTP-based
protocol (e.g., HTTP/HTTPS), GET or POST can be specified for each
callback reference.
[0048] The device usage resource can be used to programmatically
access usage of the connectivity device as shown in the exemplary
device usage resource of FIG. 2.
[0049] The connectivity plan resource functions to at least
partially specify operational capabilities and permissions and also
the metering and billing options of the connectivity device. The
connectivity plan can include various properties that can be used
to set capabilities of the connectivity devices. Capabilities such
as data communications, SMS messages, MMS messages, PSTN calls,
national roaming, international roaming and other capabilities
could be enabled, disabled, capped/limited, and/or otherwise
controlled. As one additional property, a billing mode could be set
through the connectivity plan resource. A billing mode can set
different ways in which connectivity devices are metered and/or
billed. In a pooled billing mode all the usage of a connectivity
devices associated with the connectivity plan are summed (i.e.,
pooled) when billing, evaluating progress against pricing tiers,
evaluating usage limits, and/or assessing usage. In an individual
billing mode, usage of connectivity devices associated with the
connectivity plan are treated individually.
[0050] Alternative architectures of programmatic resources could
alternatively be used. As an exemplary alternative, the
connectivity plan could be directly specified within the device
resource. As another exemplary alternative, the callback references
and capabilities could be specified in the connectivity plan
resource.
[0051] The API service 112 may additionally include a commands
resource that can be used to create and access machine-to-machine
communications. A command resource can be used for sending a data
message to the connectivity device. In one implementation, message
content can be transmitted through an SMS protocol. However, any
suitable medium of communication or protocol could be used. The
command resource can be used in delivering inbound communications.
Outbound messages could be handled differently. As mentioned above,
a device resource could specify a command callback, which would
make an asynchronous application layer request to the command
callback URI with outbound command or message communications.
[0052] The event callback system 114 can function to enable event
triggers or webhooks to be activated in response to different state
changes or events. Event callbacks may be triggered at particular
stages of a communication. When an event callback condition is
satisfied, a configured event is executed. The event could be an
internal operation, a callback event, or any suitable action. An
internal operation can be a closed action that may not be fully
exposed to an account holder. A URI callback event preferably
includes making an application layer protocol communication to an
external resource located at the specified URI. A callback event
may alternatively be configured by account for any suitable event
such as when a connectivity device 120 is activated, when a
communication associated with a device is received, or any suitable
condition. Callback URIs may be setup to retrieve application logic
to synchronously manage a communication.
[0053] The application logic processing system 116 may enable
business logic to be defined through an executable document.
Preferably, application logic is specified through a structured
document. In one variation, a markup language document can be used
in specifying a set of instructions and conditions that can be
sequentially executed. The application logic may be retrieved from
a remote server. For example, the event callback system 114 may
retrieve application logic from a URI, which is then processed in
association with a conversation. Application logic may
alternatively be stored within the communication platform 110.
[0054] The connectivity device 120 functions as a connectivity
destination or endpoint for communications. In a preferred
implementation, the connectivity device of the system can be a SIM
card or subscriber identity module card. The SIM card when used
with a telecommunications module can authenticate a device as a
subscriber and participant on a network. The connectivity device
can be a SIM card, as one knowledgeable in the art would
understand. The SIM card could include a unique serial number
(e.g., integrated circuit card identifier (ICCID)), international
mobile subscriber identity (IMSI) number, and/or other information
such as service access credentials, PIN numbers, and the like. In
one implementation, SIM cards can be distributed in combination
with activation codes, wherein the activation codes can be
communicated with the communication platform and used by the
communication platform for altering the status of the connectivity
devices. In other variations, the connectivity devices could be
other types of devices such as phones, tablets, or other suitable
devices. Such devices will preferably include a SIM card,
integrated SIM data, or otherwise be capable of connecting to a
network.
[0055] A mobile core 130 is the set of network infrastructure used
in facilitating communications with the device. In one
implementation, a network carrier with the mobile core 130 could be
implementers of the system and can integrated the mobile core 130
with the communication platform. In an alternative implementation,
the mobile core 130 can be enabled through an outside partner, and
the system could include a mobile core 130 interface such that the
communication platform 110 can interface with an outside mobile
core 130. For example, the communication platform may interface
with multiple carrier networks, where the devices have
communications using the carrier networks as at least an
intermediary resource for communications. Communications are
preferably routed through the communication platform for at least a
subset of communication types.
3. Method for Programmatic Device Connectivity
[0056] As shown in FIG. 3, a method for programmatic device
connectivity of a preferred embodiment can include provisioning a
connectivity device S110, servicing communications of the
connectivity device S120, and programmatically managing the
connectivity device S130. The method preferably functions to enable
connectivity devices to be activated, deactivated, and/or otherwise
managed. Additionally, the management of the connectivity devices
can be facilitated through an interface of a communication platform
and, more preferably, a programmatic interface such as an API. The
programmatic interfaces could be used in augmenting communications
of the connectivity device. By exposing a programmatic interface to
the management of connectivity devices, services and applications
can provided automated management of cellular connectivity of one
or more devices. The connectivity devices are preferably SIM cards
or SIM-enabled devices that use a SIM card in enabling connectivity
to a cellular network. The method is preferably implemented by a
system such as the one described above, but any suitable system may
alternatively be used.
[0057] The method can be particularly applicable to managing a
plurality of connectivity devices, wherein provisioning servicing,
and managing are applied across multiple connectivity devices.
Subsets of the multiple connectivity devices could be individually
configured with distinct connectivity plans and customized
functionality. The method could similarly be applied to a single
connectivity device.
[0058] Block S110, which includes provisioning a connectivity
device, functions to enroll and setup data connectivity for a
device. A connectivity device is preferably provisioned with an
account of a communication platform. The communication platform can
be one as described above and is preferably a multitenant
communication platform such that distinct entities could
independently provision connectivity devices through the
communication platform. A connectivity device is preferably any
device with capability to authenticate with a telecommunications
network and participate as a subscribed entity. More specifically,
provisioning a connectivity device can include provisioning a SIM
card. A SIM card can enable identification of a computing device
connecting to a network, and communications described in the method
can be SIM card originated communications. In SIM card originated
communications, the computing device transmitting and receiving
telecommunication signals is identified as an endpoint as
prescribed by the SIM card. In alternative implementations, the
connectivity devices can be computing devices with included SIM
cards or have digital equivalent of a SIM card. For example, a
connectivity device may not have a removable SIM card but have
identifiers and set within software or hardware of the device.
[0059] In one variation, provisioning can include providing
connectivity devices, wherein the operator of the method can manage
a known supply of connectivity devices. In providing connectivity
devices, the communication platform can have a set of
pre-registered connect devices (e.g., SIM cards) with known
identifiers. In one implementation, a set of SIM cards can be
issued by a carrier network to the communication platform, wherein
the issued SIM cards are managed by the mobile core of the carrier
network in a way compatible with the method. In this variation,
only SIM cards provided by the communication platform are capable
of operation with the method. Alternatively or additionally, ad-hoc
registration of connectivity devices can enable outside
connectivity devices to be migrated and enrolled for use with the
method.
[0060] Providing connectivity devices can additionally relate to
the physical transfer of the connectivity devices to an account
holder. In one variation, the communication platform or other
outlets could sell the connectivity devices. In another variation,
the communication platform could expose a programmatic provisioning
API that enables ordering of SIM cards. For example, an API can be
exposed enabling an entity to order new SIM cards programmatically.
An API request could specify the number, the SIM card type, and an
address for SIM card delivery. In one variation, the SIM cards can
arrive ready for use. Alternatively, a SIM card may be provisioned
once the user has the SIM card in hand. This may be used to onboard
SIM cards that a user already possesses.
[0061] Provisioning a connectivity device preferably includes
uniquely associating network operating identifiers of the
connectivity device with a corresponding programmatic device
resource S122, setting communication metering properties in a
programmatic connectivity plan resource S124; and activating
network communication status of the connectivity device S126 as
shown in FIG. 4. The processes of blocks S122, S124, and S126
function to setup a connectivity device and transition the
connectivity device to an active state where communication and
metering can be executed. The connectivity plan resource and the
device resource are preferably programmatic resources exposed
through an API of the communication platform. Setting and
augmenting of programmatic resources can preferably be facilitated
through block S130. Additionally, as with block S130, programmatic
resources may additionally be set or changed through any suitable
interface such as a user interface exposed on a control portal on a
website or application of the communication platform.
[0062] Block S122, which includes uniquely associating network
operating identifiers of the connectivity device with a
corresponding programmatic device resource, functions to setup
endpoint access and link identity of a connectivity device with an
account. The device resource, along with other associated
resources, can define state and settings of an associated
connectivity device as shown in an exemplary API information
request of FIG. 5. Preferably, the network operating identifier is
one of a SIM card. The identifier for a SIM card could be an
integrated circuit card identifier (ICCID). The international
mobile subscriber identity (IMSI) and/or other network identifier
may additionally or alternatively be associated with the device
resource. In some variations, the SIM card can be associated with a
phone number, which could additionally be associated with the
device resource. In other variations, the phone number addressing
can be provided through the communication platform. In this
variation, a human facing endpoint address such as the phone number
for the connectivity device can be set within the communication
platform, wherein the actual device endpoint address can be
transparent or a minor detail to the end user. The actual device
endpoint address can be used internally, but a level of indirection
is introduced so that a phone number is used to reference the
device outside of the platform and mobile core, which functions to
make device management more flexible. For example, the phone number
used to access a device can be set and updated in real-time in
block S130.
[0063] Block S124, which includes setting communication metering
properties in a programmatic connectivity plan resource, functions
to configure billing and/or usage limits for communications from
connectivity devices. Preferably, the connectivity plan is
abstracted away to its own programmatic resource in the
communication platform. As discussed, the communication metering
properties could additionally be properties of a device resource or
represented in any suitable manner. In one variation, connectivity
plan resources can be generated and then associated with a number
of device resources. The act of associating a connectivity plan
resource with a device resource, in one variation, can initialize
or enable activation of the connectivity device. Prior to a device
resource having a connectivity plan, the device is preferably
restricted from activating.
[0064] The communication metering properties preferably relate to
each available communication medium such as data usage, data
machine-to-machine transmissions, SMS messages, MMS messages, PSTN
voice calls, and/or other forms of communication. Additionally, the
connectivity plan resource can define enabled capabilities and/or
usage limits. Limits can relate to caps, tiered billing, rate
limiting, and/or other forms of communication limits. Preferably,
the metering properties will define the options used in measuring
usage and generating a bill based on the measured usage. Setting
communication metering properties in a programmatic connectivity
plan resource can include setting communication metering modes,
communication capabilities, communication limits, and/or other
properties. These different properties may impact billing rates.
Alternatively, billing rate properties can additionally be exposed
for being defined.
[0065] The connectivity plan resource can expose different
communication metering modes. The metering modes could be set by
selecting from a set of offered metering modes such as a pooled
mode and an individual mode. In a pooled mode, a usage from a set
of devices can be measured and billed as a group. A pooled mode may
be beneficial when there are a large number of devices, but each
uses a small amount of data. In an individual mode, usage is
measured on a per-device basis.
[0066] The connectivity plan may additionally include communication
capability properties. A capability property can describe the
network resources that a device is permitted to consume if they are
available. For example, if a device is technically capable of
roaming onto an international partner network, the capabilities
property can define whether this is allowed and for which channels
it is allowed. The capability property can include a set of
different channels such as data, voice, messaging, commands, and/or
other capabilities. Additionally each capability can be scoped to
different areas of usage, which can include home usage,
national-roaming, and international-roaming. Home scope enables
connectivity on the home carrier network. National-roaming can
enable roaming for carrier networks in the same country region.
International-roaming can enable connecting through other carrier
networks internationally. As one example shown in FIG. 6, a device
may be permitted to roam using multiple channels on international
networks but not other domestic networks, and the device may be
prohibited from making machine-to-machine commands by defining a
null command channel.
[0067] The connectivity plan may additionally include communication
limits, which functions to enable restrictions to be placed on the
volume of network resources consumed by the device. In one
variation, a cap communication limit can be used to set an upper
limit of usage. In a cap limit, an optional cap period may be used
to automatically renew a cap. Caps can be placed for different
channels such that voice, messaging, commands, and data may be
individually limited. In one example shown in FIG. 7, a user may
set a cap to limit a device to 50 MB of data and 30 minutes of
voice calling per day, while allowing unlimited SMS messaging and
commands. A cap property could additionally be used in setting
finite, non-renewing usage limits. For, example, a device could be
set so that it could only consume 2 GB of data over it's lifetime
unless a new connectivity plan is created or if the device is
deactivated and reactivated.
[0068] Block S126, which includes activating network communication
status of the connectivity device, functions to enable a
connectivity device for use with a network. Activating a
connectivity device preferably involves some event that triggers
transitioning a connectivity device from its current non-active
state (e.g., a ready status, suspended status, etc.) to an active
state. As shown in the exemplary scenario of FIG. 8, activating
network communication status of the connectivity device can include
receiving a programmatic request to activate the connectivity
device and initiating activation of the connectivity device on the
network. Activation on the network can take some amount of time
that may prevent a readily available response to the activation
request. Accordingly, the programmatic activation request can
include a callback URI and/or a callback URI can be associated with
connectivity device. For example, a status callback URI can be a
property of the device resource. With a callback URI established,
then activating the network communication status can additionally
include transmitting an asynchronous status update on activation of
the connectivity device to the status callback URI. The status
callback URI can similarly be used for any status changes of a
connectivity device. Preferably, an account will set the status
callback URI to a managed URI such that a webserver of the account
holder can detect status changes and take any appropriate
actions.
[0069] Provisioning of the connectivity device will preferably
include some registration process for associating a connectivity
device and an account. In the variation, where the connectivity
devices are provided by the communication platform, the network
identifiers used for instructing a mobile core of how to interact
with the connectivity devices can be established in the
communication platform. A registration process can be used to map a
convenient device identifier with the underlying identifier.
Alternatively, the various network identifiers may be entered
manually or looked up using some alternative mechanism.
[0070] In one variation, connectivity devices can be registered
through a device identifier that accompanies a physical
connectivity device. For example, a SIM card can be provided along
with a uniquely associated activation code. The activation code can
be used in registering and/or activating the SIM card. In this
variation, provisioning the connectivity device can include
providing SIM cards, where each SIM card is uniquely associated
with a provided activation code; and receiving a registration
request with a user-supplied activation code and generating the
device resource. In this variation, the device resource
characterizes configuration of the connectivity device identified
through the user-supplied activation code. The network operating
identifiers of the connectivity device can be searching for a
connectivity device record with an associated activation code that
corresponds to the user-supplied activation code. Setting of a
connectivity plan resource and final activation can be completed
once the connectivity device is registered with the account.
[0071] In another variation, connectivity devices can be
preemptively associated with an account prior to the account holder
having physical access to the connectivity devices. This can be
used such that connectivity devices can be pre-registered and ready
for activation upon receipt of the connectivity devices. This could
be useful when an account holder has a use case where large volumes
of connectivity devices will be used. This variation can include
receiving an order for a connectivity device from the account of
the communication platform, and, in association with fulfillment of
the order of the connectivity devices, generating device resource
accessible through a programmatic interface of the communication
platform. Fulfillment of the order of the connectivity devices can
mean the device resources are generated after confirming the order,
during processing of the order, during shipment of the connectivity
device, or at any point. In one variation, a placeholder device
resource can be created immediately following an order of the
connectivity device. Network operating identifiers could be
associated with the device resource through registration
facilitated by method operators. For example, the registration can
be completed by the communication platform or a partner of the
communication platform prior to shipment of the connectivity
device. Alternatively, a device resource could be created after
registration by the method operators. By pre-registering a
connectivity device, an account holder could obtain faster access
for configuring the connectivity devices for use. For example, once
a device resource is established for the account, the account
holder could begin setting a connectivity plan, requesting
activation, or setting any operating properties of the device.
Pre-registration can additionally lock the connectivity devices to
use by that account, such that one would need access to the account
to activate and/or use the connectivity devices.
[0072] As will be described below, the device resource and/or the
connectivity plan resource can expose various operational options
which can be used for introducing programmatic control of
communications, custom communication rules like routing, and/or
other features. These will be described in more detail in reference
to block S130.
[0073] Block S120, which includes servicing communications of the
connectivity device, functions to enable usage of the device. A
mobile core is preferably used to facilitate the capabilities of a
device. The SIM card is preferably used by a computing device such
as a smart phone, computer, IoT device, or other suitable device in
establishing network connection and sending/receiving
communication. The device may be used for data downloading and
uploading over the internet, SMS messaging, MMS messaging, IP
messaging, voice calls, video calls, and/or other suitable channels
of usage. Outbound and inbound communications can be made.
Servicing communications preferably includes metering and measuring
usage of the connectivity device. Metering can include measuring
data usage, counting communications, counting time of synchronous
communications, and/or creating a record of any suitable metric
that may be used in limiting and/or billing of the usage.
[0074] In one variation, the communication platform can facilitate
exposing programmable communications when servicing communications.
Exposing programmable communications can enable application logic
to be applied in connection with one or more channels of
communication. A communication can be synchronously processed
according to associated application logic. Synchronous application
logic can enable a communication to be controlled in real-time. For
example, a call could be rerouted automatically or a message could
be translated before being sent to a destination. Communication can
alternatively be asynchronously processed, wherein application
logic is executed outside of the communication flow. For example, a
developer may want to receive a notification each time an outgoing
communication is made from the device so asynchronous application
logic could be implemented to notify an application server of the
developer without blocking or stalling the outgoing
communication.
[0075] Programmable communication can involve setting a callback
URI for a connectivity device. Callback URIs are preferably
properties of associated device resources. There could be distinct
callback URIs for different channels of communication such as a
data command callback URI, a SMS/MMS callback URI, a voice callback
URI, and/or any suitable type of callback URI. Fallback callback
URIs could additionally be configured. At different events the
callback URI is processed and used to retrieve application logic.
The application logic can then be processed. A callback may be a
synchronous callback or an asynchronous callback.
[0076] When accessing a callback URI, an application layer protocol
can be used in a request response model to retrieve media that
specifies actions to be taken within the communication platform as
shown in FIG. 9. An application layer protocol is preferably an
HTTP-based protocol like HTTP or HTTPS, but may alternatively be
SPDY or any suitable protocol. An application layer request can be
made to the configured callback URI. That callback URI will
generally direct the request to a server controlled by the entity
managing the device, and will perform any suitable processing task
to determine the response. Communication attributes are preferably
sent with the application layer request such that an application
server processing the application layer request can generate a
dynamic response. The communication attributes can include the
connectivity device identifier, a communication destination
identifier (e.g., the endpoint the communication was directed to by
the device), communication type, communication payload, and/or any
suitable properties. Then a response message is received at the
communication platform. The response message can include a document
with a set of instructions that can be sequentially processed and
executed by the platform. The response message may alternatively
include media, which may be used in the communication. Callback
URIs can be used for outbound communications that originate from
the connectivity device. Instances of outbound communications can
include receiving a communication originating from the connectivity
device at the communication platform; transmitting an application
layer protocol transmission to the configured callback URI of the
device resource; and receiving a response with application logic;
and processing message according to the application logic.
Communication attributes such as communication destination can be
communicated in the application layer protocol transmission such
that the server handling the callback URI can use the attributes in
generating dynamic application logic. Inbound communications to the
connectivity device or to an endpoint mapped to the connectivity
device can similarly include receiving a communication from an
external communication, the communication directed to an endpoint
associated with a device resource within the communication
platform; transmitting an application layer protocol transmission
to a communication callback URI of the device resource; receiving a
response with application logic; and processing the communication
according to the application logic. The application logic can
include various capabilities such as communication routing
instructions, playing media files, performing text-to-speech,
recording communications, establishing conferences, setting up a
call waiting, receiving user input or other suitable
functionality.
[0077] Other mechanisms for programmable communications may
additionally or alternatively be used. In one variation,
communication routing rules could be configured and associated with
a device resource such that outbound and/or inbound communications
could be dynamically modified in accordance with the routing rules.
Servicing a communication can directing communications according to
communication routing configuration of the device resource. These
routing rules could be programmatically configured through an API
or set in a user interface of an account accessed control portal.
For example, a mapping of destination endpoints could be used for
associating device-provided destination endpoints with executed
endpoints. In this way, outbound communications from a device can
be automatically mapped to a set destination. This could be used in
preventing outbound communications with particular endpoints. The
destination endpoint mapping could additionally include mapping
destination endpoints to origin endpoints that are to be used when
contacting a destination endpoint. The origin endpoints are
preferably endpoints allocated to the account for usage. In one
exemplary use case, a user could dial different phone numbers on a
phone and the method could automatically direct communications to
different phone numbers and automatically simulate the
communications from originating from a dynamically selected phone
number. In one example, a business could easily enable company-wide
shortcodes for company managed devices. The short codes could be
customized per connectivity device. For example, each customer
could be enabled to dial `1` to reach their manager, `2` for their
regional HR representative, `3` for regional IT support, and the
like.
[0078] Routing rules could similarly be used for incoming calls.
This can be particularly useful when a number of connectivity
devices are being managed through the method. Inbound
communications could be dynamically routed to appropriate
connectivity devices.
[0079] The routing rule functionality could additionally or
alternatively be implemented through application logic processing
using the callback URI mechanism described above. An application
server at a communication callback URI could render a response such
as the one shown in FIG. 9, where the routing of the communication
and/or mutation of the communication can be affected in any
suitable manner. Highly customized logic could be used within the
application server in determining the destination endpoint, the
origin endpoint, and/or any other functionality in the application
logic.
[0080] In a related variation to routing rules, the method could
enable a device resource to be configured with
communication-to-service routing, which can function to enable
communications, in particular data messages, to be directly
forwarded to an external host. Communication-to-service routing can
be used in forwarding communications to an external database, data
warehousing system, a cloud hosted data storage solution, and/or
any suitable destination. This can be particularly applicable when
the method is used by an account holder in managing connectivity of
IoT devices. The IoT devices could be part of a sensor network
using the network as a transport. This variation could be used in
uploading data from the IoT devices to a particular destination. A
communication-to-service routing variation can include: configuring
credentials of an outside data destination service; receiving a
data message originating from the connectivity device at the
communication platform; and transmitting the data message to the
configured data destination service using the configured
credentials as shown in FIG. 10.
[0081] The method can additionally include enforcing policy when
servicing communications. Enforcing policy can involve metering and
billing for usage of a device. Devices are preferably metered
according to the connectivity plan for the device. At the end of a
billing period, a bill can be calculated and issued for the metered
usage of one or more devices. Enforcing policy can additionally be
used in restricting usage of the connectivity device. During new
activity, the metered usage of the device (or device pool) can be
compared to the caps in the connectivity plan to determine if the
activity is permitted.
[0082] Block S130, which includes programmatically managing the
connectivity device, functions to enable remote configuration of
the connectivity device through an interface that can be integrated
with other applications or services. The device resource and/or
connectivity plan resource can be two programmatically-accessible
resources through which operation and network connection of a
connectivity device can be managed. As described above, callback
URIs and application logic processing can be set through the device
resource and/or connectivity plan resources to programmatically
control or interact with communications. Preferably, properties of
API resources such as the device resource and the connectivity plan
resource can be read and/or updated to trigger changes.
Additionally, a communication resource such as a command resource
can be used for programmatically triggering communications
originating and/or terminating at the connectivity device.
[0083] Additionally, the various configuration and activity of a
connectivity device can be exposed through an interface. The
interface can be a graphical user interface (e.g., a dashboard),
wherein an administrator could review activity and make changes
through a user interface. Alternatively or additionally, an API can
be exposed and more specifically a REST API. Through API resources
are preferably used to alter management of associated connectivity
devices. An account holder could remotely augment the addressing of
a connectivity device. For example, one or more endpoint may be
routed to the connectivity device. The change in routing can be
made in under a minute and may be changed multiple times. An
account holder could alter callback URIs to update how event
callbacks are triggered. The connectivity plan could be remotely
altered to change billing and/or permissions.
[0084] The method may expose an interface for changing operating
status of a connectivity device. This could be used to register,
activate, suspend, deactivate, or set any suitable operating state.
Registering preferably transitions a connectivity device to a ready
state. Status changes can be set by an account holder through a
user interface or a programmatic interface. In a programmatic
interface, an API request can be submitted to an appropriate
resource (e.g., the device resource) with a status property set to
the newly desired status.
[0085] In one variation, activating a connectivity device can
include receiving a programmatic request to activate a connectivity
device and initiating activation of the connectivity device on the
network as shown in FIG. 8. As discussed above, a status callback
URI could be configured for a device resource or otherwise
specified in the request, wherein activating a connectivity device
can include transmitting an asynchronous status update on
activation of the SIM card to the status callback URI. Once a
connectivity device is activated, the device can connect to the
network and participate in communications. Additionally, metering
and/or billing can be activated for the connectivity device. In
some cases, a status update may fail in which case the status
callback URI will receive a message indicating the update
failure.
[0086] In a related variation, deactivating a connectivity device
can include receiving a programmatic request to deactivate a
connectivity device and deactivating the connectivity device on the
network as shown in FIG. 11. Deactivation preferably prevents
communication and/or reactivation of the device. Suspending a
device could be a similar process wherein the connectivity device
could be reactivated.
[0087] During use of the connectivity device, the connectivity plan
could be altered. Altering the connectivity plan can include
receiving a programmatic request changing a current connectivity
plan resource associated to the device resource to an updated
connectivity plan and metering the connectivity device in
accordance with the updated connectivity plan after changing the
current connectivity plan. A connectivity plan could be changed by
associating a new connectivity plan to the device resource. A
connectivity plan could alternatively be changed by updating an
existing connectivity plan resource associated with the device
resource. As above, this could be facilitated through a user
interface or a programmatic interface. As discussed above, a
connectivity plan may enable changes to metering modes, enabled
capabilities, usage limits, and/or other usage aspects. For
example, the connectivity plan could specify a metering mode, an
activation state of voice communication, an activation of message
communication, an activation state of data connectivity, and a data
limit.
[0088] In one variation, the method can expose a command API
resource that is utilized for machine-to-machine communications. A
command using SMS preferably issues commands in a text-based format
and the content is arbitrary, wherein a developer can determine how
the payload is used. Alternatively, MMS or alternative
communication channels may be used to offer alternative payload
formats. Commands, data communications, and/or other forms of
communication can be initiated through a user interface and/or
programmatic interface. Use of a command resource can include
receiving a programmatic communication request to transmit data to
a connectivity device and processing message transmission to the
connectivity device. The communication request can specify the type
of communication and the contents of the communication. The
communication request can additionally include a status callback
URI or the status callback URI may alternatively be specified in
association with the device resource and/or connectivity plan. When
a status callback URI is present transmission of a communication
can additionally include transmitting an asynchronous status update
on completion of processing message transmission. Preferably, the
asynchronous status update will indicate successful transmission,
but may alternatively indicate an error state or other outcomes of
the attempted transmission.
[0089] The system and method of the preferred embodiment and
variations thereof can be embodied and/or implemented at least in
part as a machine configured to receive a computer-readable medium
storing computer-readable instructions. The instructions are
preferably executed by computer-executable components preferably
integrated with the media intelligence platform. The
computer-readable medium can be stored on any suitable
computer-readable media such as RAMs, ROMs, flash memory, EEPROMs,
optical devices (CD or DVD), hard drives, floppy drives, or any
suitable device. The computer-executable component is preferably a
general or application specific processor, but any suitable
dedicated hardware or hardware/firmware combination device can
alternatively or additionally execute the instructions.
[0090] As a person skilled in the art will recognize from the
previous detailed description and from the figures and claims,
modifications and changes can be made to the preferred embodiments
of the invention without departing from the scope of this invention
defined in the following claims.
* * * * *