Patent Application
20140351075
A purchaser may purchase a device (e.g., a cell phone) at a store associated with a service provider network. The purchaser may also provide subscription information associated with the device (e.g., a subscriber name, a subscriber account number, a contract term, a data plan, a quantity of monthly minutes, etc.) and may activate the device at the time of purchase. A device that has been activated may use services provided by the service provider network.
The following detailed description of example implementations refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
A purchaser of a device (e.g., a cell phone) may wish to begin the purchase of the device using a website associated with a service provider network. The purchaser may provide subscription information (e.g., a subscriber name, a subscriber account number, a contract term, a data plan, a quantity of monthly minutes, etc.) via the service provider network website. However, the purchaser may wish to physically examine the device before completing the purchase. The purchaser may also want to examine the device, complete the purchase of the device, provide subscription information associated with the device, and activate the device without having to visit a store associated with the service provider network. Implementations described herein may allow a purchaser to complete the purchase, setup, and activation of a device at a kiosk without having to visit a store associated with a service provider network.
As shown in
As shown in
Purchase information device 210 may include a device capable of receiving, generating, processing, storing, and/or providing information associated with a purchase of a device (e.g., purchased device 230). For example, purchase information device 210 may include a computing device (e.g., a laptop computer, a desktop computer, a tablet computer, a server computer, etc.), a wireless communication device, a radiotelephone, a personal communications system (“PCS”) terminal (e.g., that may combine a cellular radiotelephone with data processing and data communications capabilities), a personal digital assistant (“PDA”) (e.g., that can include a radiotelephone, a pager, Internet/intranet access, etc.), a smart phone, and/or a similar device. Purchase information device 210 may send information associated with the purchase of the device to one or more other devices (e.g., kiosk device 220, HSS 240, etc.).
Kiosk device 220 may include a device capable of receiving, generating, processing, and/or providing information associated with the purchase of a device (e.g., purchased device 230), subscription information associated with the device, and/or activation information associated with the device. Additionally, or alternatively, kiosk device 220 may include a device capable of dispensing another device to a purchaser. In some implementations, kiosk device 220 may include an apparatus that may house one or more devices that are available for purchase by a purchaser. For example, the kiosk may house a device (e.g., purchased device 230) and may dispense the device to the purchaser based on purchaser input. Kiosk device 220 may receive and/or send information associated with the purchase of the device from and/or to another device (e.g., purchase information device 210, HSS 240, etc.). In some implementations, kiosk device 220 may include a mechanism (e.g., a camera, a display screen, a telephone, etc.) that may allow the purchaser to provide input and/or to communicate with a representative of the service provider network (e.g., a customer service representative). In some implementations, kiosk device 220 may be capable of wireless communication with another device (e.g., HSS 240) via a service provider network, allowing kiosk device 220 to be placed in a variety of locations.
Purchased device 230 may include a device housed in a kiosk (e.g., kiosk device 220). Additionally, or alternatively, purchased device 230 may include a device capable of communicating with a service provider network (e.g., after being activated). For example, purchased device 230 may include a wireless communication device, a radiotelephone, a personal communications system (“PCS”) terminal (e.g., that may combine a cellular radiotelephone with data processing and data communications capabilities), a personal digital assistant (“PDA”) (e.g., that can include a radiotelephone, a pager, Internet/intranet access, etc.), a smart phone, a laptop computer, a tablet computer, a personal gaming system, and/or a similar device. Purchased device 230 may be activated for use on the service provider network based on information provided by another device (e.g., purchase information device 210, kiosk device 220, HSS 240, etc.).
HSS 240 may include one or more devices, such as one or more server devices, capable of managing subscription and/or other information associated with purchased device 230. For example, HSS 240 may receive, store and/or provide profile information associated with purchased device 230 that identifies applications and/or services that are permitted for use by and/or accessible by purchased device 230, information associated with a purchaser of purchased device 230 (e.g., a username, a password, a personal identification number (“PIN”), etc.), activation information, subscription information, rate information, minutes allowed, bandwidth allocation policy information, and/or other information.
Network 250 may include one or more wired and/or wireless networks. For example, network 250 may include a cellular network, a public land mobile network (“PLMN”), a local area network (“LAN”), a wide area network (“WAN”), a metropolitan area network (“MAN”), a telephone network (e.g., the Public Switched Telephone Network (“PSTN”)), an ad hoc network, an intranet, the Internet, a fiber optic-based network, and/or a combination of these or other types of networks.
The number of devices and/or networks illustrated in
Bus 310 may include a path that permits communication among the components of device 300. Processor 320 may include a processor, a microprocessor, and/or any processing component (e.g., a field-programmable gate array (“FPGA”), an application-specific integrated circuit (“ASIC”), etc.) that interprets and/or executes instructions. In some implementations, processor 320 may include one or more processor cores. Memory 330 may include a random access memory (“RAM”), a read only memory (“ROM”), and/or any type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use by processor 320.
Input component 340 may include any component that permits a user to input information to device 300 (e.g., a keyboard, a keypad, a mouse, a button, a switch, etc.). Output component 350 may include any component that outputs information from device 300 (e.g., a display, a speaker, one or more light-emitting diodes (“LEDs”), etc.).
Communication interface 360 may include any transceiver-like component, such as a transceiver and/or a separate receiver and transmitter, that enables device 300 to communicate with other devices and/or systems, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. For example, communication interface 360 may include a component for communicating with another device and/or system via a network. Additionally, or alternatively, communication interface 360 may include a logical component with input and output ports, input and output systems, and/or other input and output components that facilitate the transmission of data to and/or from another device, such as an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (“RF”) interface, a universal serial bus (“USB”) interface, or the like.
Device 300 may perform various operations described herein. Device 300 may perform these operations in response to processor 320 executing software instructions included in a computer-readable medium, such as memory 330. A computer-readable medium may be defined as a non-transitory memory device. A memory device may include memory space within a single physical storage device or memory space spread across multiple physical storage devices.
Software instructions may be read into memory 330 from another computer-readable medium or from another device via communication interface 360. When executed, software instructions stored in memory 330 may cause processor 320 to perform one or more processes that are described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
The number of components illustrated in
As shown in
Device information, as used herein, may refer to information associated with a purchase of a device (e.g., purchased device 230). For example, device information may include information identifying a purchaser of the device (e.g., a name, an address, an email address, a username associated with the service provider network website, etc.), information identifying a service provider network subscriber (e.g., a subscriber account name, a subscriber account number, etc.), information that identifies the device (e.g., a make of the device, a model of the device, a device identifier, such as an international mobile subscriber identity (“IMSI”), a mobile subscriber integrated services digital network-number (“MSISDN”), a mobile directory number (“MDN”), etc.), information associated with subscription services to be provided to the device (e.g., a contract length, a contract type, a data plan, a quantity of monthly minutes, etc.), or the like.
In some implementations, kiosk device 220 may determine the device information based on input, from the purchaser, provided using kiosk device 220. For example, the purchaser may navigate a list of devices displayed on a display screen of kiosk device 220. Kiosk device 220 may display the list of devices based on devices housed within kiosk device 220. Additionally, or alternatively, the purchaser may provide a username and a password associated with the service provider network website, and kiosk device 220 may determine the device information based on input previously provided by the purchaser, via purchase information device 210, using the service provider network website.
In some implementations, the purchaser may request assistance (e.g., via a user interface of kiosk device 220), and may be connected to a customer service representative (e.g., on a video call via kiosk device 220, etc.). The customer service representative may input the device information. Additionally, or alternatively, the customer service representative may provide guidance to the purchaser (e.g., information regarding devices available for purchase, information regarding the operation of kiosk device 220, information regarding the purchase and activation process in general, etc.).
As further shown in
In some implementations, kiosk device 220 may collect the device from the purchaser after kiosk device 220 has dispensed the device (e.g., the purchaser has examined the device and decided not to purchase the device). For example, the purchaser may indicate (by clicking a “Return Device” button on a user interface of kiosk device 220) that the purchaser has decided to return the device to kiosk device 220 (e.g., the purchaser does not want to purchase the device). In some implementations, kiosk device 220 may include a mechanism to collect the device from the purchaser (e.g., a doorway, a receiving slot, an opening, etc.). Additionally, or alternatively, kiosk device 220 may include a mechanism to return the collected device to a particular location within the housing of kiosk device 220 (e.g., a location where the device was dispensed from, etc.) so the device may be dispensed for a future purchase.
In some implementations, kiosk device 220 may dispense a demonstration (“demo”) device (e.g., another device that may be the identical make and model of the device) to the purchaser. In some implementations, the demo device may have limited functionality activated to permit the purchaser to interact with the demo device.
In some implementations, the demo device may be programmed with information associated with purchaser (e.g., information associated with a contact of the purchaser, an application installed on another device associated with the purchaser, etc.) before being dispensed. The information associated with the purchaser may be determined based on information stored by another network device associated with the service provider network (e.g., an application server, etc.).
In some implementations, the demo device may be reprogrammed to include information associated with the current purchaser each time the demo device is dispensed. Additionally, or alternatively, information associated with the purchaser that is programmed onto the demo device may be deleted when the demo device is collected by the kiosk.
In some implementations, a device identifier of the demo device may be stored by a device in the service provider network (e.g., HSS 240) to prevent the demo device from being activated (e.g., if the purchaser does not return the demo device). In some implementations, the purchaser may be charged for a loss of, or damage to, the demo device. Kiosk device 220 may collect the demo device from the purchaser, prior to dispensing the device (e.g., purchased device 230). For example, kiosk device 220 may determine, based on user input provided via a user interface of kiosk device 220, that the purchaser is permitted (e.g., by providing credit card information, by providing a driver's license number, etc.) to examine the demo device prior to completing the purchase of purchased device 230. Kiosk device 220 may dispense the demo device, and may subsequently collect the demo device (e.g., using a doorway, using a receiving slot, etc.) when the purchaser completes the examination. In some implementations, kiosk device 220 may dispense the device (e.g., purchased device 230) to the purchaser after the demo device is collected from the purchaser.
In some implementations, kiosk device 220 may dispense multiple devices to allow the purchaser to compare the multiple devices. In some implementations, kiosk device 220 may limit the quantity of devices that may be dispensed and/or may not allow activation of any dispensed device until all but one of the multiple devices has been collected by kiosk device 220.
As further shown in
In some implementations, the purchase indication may be based on payment information (e.g., credit card information, etc.) provided by the purchaser to complete the purchase of the device. Additionally, or alternatively, the purchase indication may be based on an indication that the device has been dispensed to the purchaser by kiosk device 220. Additionally, or alternatively, the purchase indication may be based on input, from the purchaser (e.g., by clicking on a “Purchase” button, by clicking a “Do Not Purchase” button, etc.), provided via a user interface of kiosk device 220.
As further shown in
As further shown in
In some implementations, the subscription information may be based on the device information and/or based on information received from another device (e.g., purchase information device 210, purchased device 230, HSS 240, etc.). Additionally, or alternatively, the subscription information may be based on input, from the purchaser, provided via a user interface displayed on kiosk device 220. In some implementations, the purchaser of the device may be a user of the device.
Subscription information may include information associated with the purchaser and/or information associated with services to be provided to the device by the service provider network. For example, subscription information may include information identifying the purchaser (e.g., a name, an address, an email address, a telephone number, a subscriber identifier associated with the purchaser, a subscriber account number associated with the purchaser, etc.), information identifying the device (e.g., a make of the device, a model of the device, an IMSI, an MSISDN, an MDN, etc.), information associated with services provided to the device via the service provider network (e.g., a quantity of monthly data, a quantity of monthly minutes, a quantity of monthly text messages, etc.), information associated with the type and/or duration of the subscription (e.g., a contract term, a monthly plan, a prepaid plan, a pay-as-you-go plan, etc.), payment information associated with the purchaser (e.g., a billing address, a checking account number, a credit card number, etc.), or the like.
As further shown in
Activation information, as used herein, may refer to information associated with making a device operable on a service provider network. In some implementations, the activation information may be based on the subscription information received by kiosk device 220. Additionally, or alternatively, the activation information may be based on information received from another device (e.g., purchase information device 210, purchased device 230, etc.). The activation information may be based on the subscription information associated with the device (e.g., purchased device 230).
In some implementations, the device (e.g., purchased device 230) may be activated on a service provider network based on activation information being provided to another device associated with the service provider network. For example, the activation information may be provided to HSS 240, which may store the activation information, perform authentication of the device, and/or perform authorization of the device. Activation of the device may take place when an activation request is received (e.g., from kiosk device 220, purchased device 230, etc.). Upon receiving an activation request, a network device associated with activation (e.g., HSS 240) may authenticate the device, based on the activation information, and may activate the device for use on the service provider network (e.g., may permit the device to access the service provider network).
In some implementations, HSS 240 may activate purchased device 230 (e.g., permit purchased device 230 to access the service provider network) based on storing the activation information. Alternatively, HSS 240 may store the activation information and may not activate purchased device 230 (e.g., based on an indication that purchased device 230 is to be activated in the future).
In some implementations, HSS 240 may activate purchased device 230 based on an indication (e.g., input provided via a user interface of kiosk device 220) received from kiosk device 220 indicating that purchased device 230 is to be activated. Additionally, or alternatively, HSS 240 may activate purchased device 230 based on an indication received from purchased device 230 (e.g., the purchaser wishes to activate purchased device 230 using purchased device 230 itself).
While a series of blocks has been described with regard to
As shown in
As further shown in
As shown in
As further shown in
As shown in
As shown in
As shown in
As shown in
Alternatively, as shown in
As further shown in
As indicated above,
Implementations described herein may allow a purchaser to purchase a device, provide subscription information associated with the device, and activate the device at a kiosk without having to visit a store associated with a service provider network.
The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.
As used herein, the term component is intended to be broadly construed as hardware, firmware, or a combination of hardware and software.
Certain user interfaces have been described herein. In some implementations, the user interfaces may be customizable by a device or a user. Additionally, or alternatively, the user interfaces may be pre-configured to a standard configuration, a specific configuration based on a type of device on which the user interfaces are displayed, or a set of configurations based on capabilities and/or specifications associated with a device on which the user interfaces are displayed.
It will be apparent that systems and/or methods, as described herein, may be implemented in many different forms of software, firmware, and hardware in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods were described without reference to the specific software code—it being understood that software and control hardware can be designed to implement the systems and/or methods based on the description herein.
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set.
No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
