US20150163098A1 - Method, Apparatus and Computer Program Product for Providing Confirmed Over-The-Air Terminal Configuration - Google Patents
Method, Apparatus and Computer Program Product for Providing Confirmed Over-The-Air Terminal Configuration Download PDFInfo
- Publication number
- US20150163098A1 US20150163098A1 US14/624,101 US201514624101A US2015163098A1 US 20150163098 A1 US20150163098 A1 US 20150163098A1 US 201514624101 A US201514624101 A US 201514624101A US 2015163098 A1 US2015163098 A1 US 2015163098A1
- Authority
- US
- United States
- Prior art keywords
- mobile terminal
- server
- configuration data
- request
- device management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
- H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
- H04L41/0886—Fully automatic configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
Definitions
- Embodiments of the present invention relate generally to mobile electronic device technology and, more particularly, relate to methods, apparatuses, and a computer program product for providing over-the-air confirmation of configurations received at mobile electronic devices.
- the services may be in the form of a particular media or communication application desired by the user, such as a music player, a game player, an electronic book, short messages, email, etc.
- the services may also be in the form of interactive applications in which the user may respond to a network device in order to perform a task or achieve a goal.
- the services may be provided from applications stored at a network server or other network device, or even at the mobile terminal such as, for example, a mobile telephone, a mobile television, a mobile gaming system, etc.
- the configuration settings may be sent over-the-air (OTA) via a wireless communication network. Accordingly, if a new application is downloaded at the mobile terminal, the network will typically transmit corresponding configuration settings to the mobile terminal which will enable the mobile terminal to launch the application in the future. However, it is currently common that if the network sends configuration settings for a new application to the user based on either a user or network initiated request, the network will not know whether the configuration settings have been properly received at the mobile terminal unless the network is notified of such failure by the user.
- OTA over-the-air
- the user may call a network help desk to request retransmission of the settings.
- the confirmation is essentially merely a confirmation that the mobile terminal received at least some settings and not that correct settings have been received.
- a failure to verify that proper configuration settings have been received at the mobile terminal can lead to user dissatisfaction and increase consumption of network resources in order to resolve trouble reports resulting from situations in which proper configuration settings are not received at the mobile terminal.
- a device management system is provided that is capable of transmitting service configuration data to a mobile terminal and subsequently initiating a confirmation sequence to verify that the service configuration data has been correctly received at the mobile terminal Accordingly, in some situations, proper configuration may automatically be ensured prior to a failed user attempt to launch an application, thereby increasing user satisfaction and decreasing impacts upon network resources due to user trouble reporting.
- a method of providing confirmed OTA terminal configuration includes communicating configuration data to a mobile terminal, initiating a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal, and receiving information indicating whether he configuration data was properly received at the mobile terminal.
- a computer program product for providing confirmed OTA terminal configuration includes at least one computer-readable storage medium having computer-readable program code portions stored therein.
- the computer-readable program code portions include first, second and third executable portions.
- the first executable portion is for communicating configuration data. to a mobile terminal.
- the second executable portion is for initiating a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal.
- the third executable portion is for receiving information indicating whether the configuration data was properly received at the mobile terminal.
- a method of providing confirmed OTA terminal configuration includes receiving a request for establishing a server initiated session with a mobile terminal from a network device, sending a connection request to the mobile terminal in response to receipt of the request for establishing the server initiated session, communicating a sample message to the mobile terminal in response to an indication of a connection with the mobile terminal, and communicating a notification to the network device in response to acknowledgment from the mobile terminal, the notification including information indicating whether the configuration data was properly received at the mobile terminal.
- an apparatus for providing confirmed OTA terminal configuration includes a processing element configured to communicate configuration data to a mobile terminal, initiate a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal, and receive information indicating whether the configuration data was properly received at the mobile terminal.
- an apparatus for providing confirmed OTA terminal configuration includes a processing element configured to receive a request for establishing a server initiated session with a mobile terminal from a network device, send a. connection request to the mobile terminal in response to receipt of the request for establishing the server initiated session, communicate a sample message to the mobile terminal in response to an indication of a connection with the mobile terminal, and communicate a notification to the network device in response to acknowledgment from the mobile terminal, the notification including information indicating whether the configuration data was properly received at the mobile terminal.
- an apparatus for providing confirmed OTA terminal configuration includes a means for communicating configuration data to a mobile terminal, a means for initiating a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal, and a means for receiving information indicating whether the configuration data was properly received at the mobile terminal.
- FIG. 1 is a schematic block diagram of a mobile terminal according to an exemplary embodiment of the present invention
- FIG. 2 is a schematic block diagram of a wireless communications system according to an exemplary embodiment of the present invention.
- FIG. 3 illustrates a block diagram of portions of a system for providing confirmed over-the-air (OTA) terminal configuration according to an exemplary embodiment of the present invention
- FIG. 4 illustrates a control flow diagram for a method of providing confirmed OTA terminal configuration according to an exemplary embodiment of the present invention
- FIG. 5 illustrates a control flow diagram for a method of providing confirmed OTA terminal configuration according to an exemplary embodiment of the present invention
- FIG. 6 is a block diagram according to an exemplary method for providing confirmed OTA terminal configuration according to an exemplary embodiment of the present invention.
- FIG. 7 is a block diagram according to an exemplary method for providing confirmed OTA terminal configuration according to an exemplary embodiment of the present invention.
- FIG. 1 illustrates a block diagram of a mobile terminal 10 that would benefit from embodiments of the present invention.
- a mobile telephone as illustrated and hereinafter described is merely illustrative of one type of mobile terminal that would benefit from embodiments of the present invention and, therefore, should not be taken to limit their scope. While several embodiments of the mobile terminal 10 are illustrated and will be hereinafter described for purposes of example, other types of mobile terminals, such as portable digital assistants (PDAs), pagers, mobile televisions, laptop computers, gaming devices and other types of voice and text communications systems, can readily employ embodiments of the present invention.
- PDAs portable digital assistants
- pagers mobile televisions
- laptop computers laptop computers
- gaming devices and other types of voice and text communications systems
- the mobile terminal 10 includes an antenna 12 in operable communication with a transmitter 14 and a receiver 16 .
- the mobile terminal 10 further includes a controller 20 or other processing element that provides signals to and receives signals from the transmitter 14 and receiver 16 , respectively.
- the signals include signaling information in accordance with the air interface standard of the applicable cellular system, and also user speech and/or user generated data.
- the mobile terminal 10 is capable of operating with one or more air interface standards, communication protocols, modulation types, and access types.
- the mobile terminal 10 is capable of operating in accordance with any of a number of first, second and/or third-generation communication protocols or the like.
- the mobile terminal 10 may be capable of operating in accordance with second-generation (2G) wireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA), or with third-generation (3G) wireless communication protocols, such as UMTS, CDMA2000, and TD-SCDMA.
- 2G second-generation
- 3G third-generation
- the controller 20 includes circuitry required for implementing audio and logic functions of the mobile terminal 10 .
- the controller 20 may be comprised of a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and other support circuits. Control and signal processing functions of the mobile terminal 10 are allocated between these devices according to their respective capabilities.
- the controller 20 thus may also include the functionality to convolutionally encode and interleave message and data prior to modulation and transmission.
- the controller 20 can additionally include an internal voice coder, and may include an internal data. modern.
- the controller 20 may include functionality to operate one or more software programs, which may be stored in memory.
- the controller 20 may be capable of operating a connectivity program, such as a conventional Web browser.
- the connectivity program may then allow the mobile terminal 10 to transmit and receive Web content, such as location-based content, according to a Wireless Application Protocol (WAP), for example.
- WAP Wireless Application Protocol
- the controller 20 may be capable of operating a software application capable of analyzing text and selecting music appropriate to the text.
- the music may be stored on the mobile terminal 10 or accessed as Web content.
- the mobile terminal 10 also comprises a user interface including an output device such as a conventional earphone or speaker 24 , a ringer 22 , a microphone 26 , a display 28 , and a user input interface, all of which are coupled to the controller 20 .
- the user input interface which allows the mobile terminal 10 to receive data, may include any of a number of devices allowing the mobile terminal 10 to receive data, such as a keypad 30 , a touch display (not shown) or other input device.
- the keypad 30 may include the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the mobile terminal 10 .
- the keypad 30 may include a conventional QWERTY keypad arrangement.
- the mobile terminal 10 further includes a battery 34 , such as a vibrating battery pack, for powering various circuits that are required to operate the mobile terminal 10 , as well as optionally providing mechanical vibration as a detectable output.
- the mobile terminal 10 may further include a universal identity module (UIM) 38 .
- the UIM 38 is typically a memory device having a processor built in.
- the UIM 38 may include, for example, a subscriber identity module (SIM), a universal integrated circuit card (UICC), a universal subscriber identity module (USIM), a removable user identity module (R-UIM), etc.
- SIM subscriber identity module
- UICC universal integrated circuit card
- USIM universal subscriber identity module
- R-UIM removable user identity module
- the UIM 38 typically stores information elements related to a mobile subscriber.
- the mobile terminal 10 may be equipped with memory.
- the mobile terminal 10 may include volatile memory 40 , such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data.
- RAM volatile Random Access Memory
- the mobile terminal 10 may also include other non-volatile memory 42 , which can be embedded and/or may be removable.
- the non-volatile memory 42 can additionally or alternatively comprise an EEPROM, flash memory or the like, such as that available from the SanDisk Corporation of Sunnyvale, California, or Lexar Media Inc. of Fremont, Calif.
- the memories can store any of a number of pieces of information, and data, used by the mobile terminal 10 to implement the functions of the mobile terminal 10 .
- the memories can include an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying the mobile terminal 10 .
- IMEI international mobile equipment identification
- the system includes a plurality of network devices.
- one or more mobile terminals 10 may each include an antenna. 12 for transmitting signals to and for receiving signals from abuse site or base station (BS) 44 .
- the base station 44 may be a part of one or more cellular or mobile networks each of which includes elements required to operate the network, such as a mobile switching center (MSC) 46 .
- MSC mobile switching center
- the mobile network may also be referred to as a Base Station/MSC/Interworking function (BMI).
- BMI Base Station/MSC/Interworking function
- the MSC 46 is capable of routing calls to and from the mobile terminal 10 when the mobile terminal 10 is making and receiving calls.
- the MSC 46 can also provide a connection to landline trunks when the mobile terminal 10 is involved in a call.
- the MSC 46 can be capable of controlling the forwarding of messages to and from the mobile terminal 10 , and can also control the forwarding of messages for the mobile terminal 10 to and from a messaging center. It should be noted that although the MSC 46 is shown in the system of FIG. 2 , the MSC 46 is merely an exemplary network device and embodiments of the present invention are not limited to use in a network employing an MSC.
- the MSC 46 can be coupled to a data network, such as a local area network (LAN), a metropolitan area network (MAN), and/or a wide area network (WAN).
- the MSC 46 can be directly coupled to the data network.
- the MSC 46 is coupled to a GTW 48
- the GTW 48 is coupled to a WAN, such as the Internet 50 .
- devices such as processing elements (e.g., personal computers, server computers or the like) can be coupled to the mobile terminal 10 via the Internet 50 .
- the processing elements can include one or more processing elements associated with a computing system 52 (two shown in FIG. 2 ), origin server 54 (one shown in FIG. 2 ) or the like, as described below.
- the BS 44 can also be coupled to a signaling GPRS (General Packet Radio Service) support node (SGSN) 56 .
- GPRS General Packet Radio Service
- the SGSN 56 is typically capable of performing functions similar to the MSC 46 for packet switched services.
- the SGSN 56 like the MSC 46 , can be coupled to a data network, such as the Internet 50 .
- the SGSN 56 can be directly coupled to the data network.
- the SGSN 56 is coupled to a packet-switched core network, such as a GPRS core network 58 .
- the packet-switched core network is then coupled to another GTW 48 , such as a.
- GTW GPRS support node (GGSN) 60 and the GGSN 60 is coupled to the Internet 50 .
- the packet-switched core network can also be coupled to a GTW 48 .
- the GGSN 60 can be coupled to a messaging center.
- the GGSN 60 and the SGSN 56 like the MSC 46 , may be capable of controlling the forwarding of messages, such as MMS messages.
- the GGSN 60 and SGSN 56 may also be capable of controlling the forwarding of messages for the mobile terminal 10 to and from the messaging center.
- devices such as a computing system 52 and/or origin server 54 may be coupled to the mobile terminal 10 via the Internet 50 , SGSN 56 and GGSN 60 .
- devices such as the computing system 52 and/or origin server 54 may communicate with the mobile terminal 10 across the SGSN 56 , GPRS core network 58 and the GGSN 60 .
- the mobile terminals 10 may communicate with the other devices and with one another, such as according to the Hypertext Transfer Protocol (HTTP), to thereby carry out various functions of the mobile terminals 10 .
- HTTP Hypertext Transfer Protocol
- the mobile terminal 10 may be coupled to one or more of any of a number of different networks through the BS 44 .
- the network(s) can be capable of supporting communication in accordance with any one or more of a number of first-generation (1G), second-generation (2G), 2.5G and/or third-generation (3G) mobile communication protocols or the like.
- one or more of the network(s) can be capable of supporting communication in accordance with 2G wireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA).
- one or more of the network(s) can be capable of supporting communication in accordance with 2.5G wireless communication protocols GPRS, Enhanced Data GSM Environment (EDGE), or the like. Further, for example, one or more of the network(s) can be capable of supporting communication in accordance with 3G wireless communication protocols such as Universal Mobile Telephone System (UMTS) network employing Wideband Code Division Multiple Access (WCDMA) radio access technology.
- UMTS Universal Mobile Telephone System
- WCDMA Wideband Code Division Multiple Access
- Some narrow-band AMPS (NAMPS), as well as TACS, network(s) may also benefit from embodiments of the present invention, as should dual or higher mode mobile stations (e.g., digital/analog or TDMA/CDMA/analog phones).
- the mobile terminal 10 can further be coupled to one or more wireless access points (APs) 62 .
- the APs 62 may comprise access points configured to communicate with the mobile terminal 10 in accordance with techniques such as, for example, radio frequency (RF), Bluetooth (BT), infrared (IrDA) or any of a number of different wireless networking techniques, including wireless LAN (WLAN) techniques such as IEEE 802.11 (e.g., 802.11a, 802.11b, 802.11g, 802.11n, etc.), WiMAX techniques such as IEEE 802.16, and/or ultra wideband (UWB) techniques such as IEEE 802.15 or the like.
- the APs 62 may be coupled to the Internet 50 .
- the APs 62 can be directly coupled to the Internet 50 . In one embodiment, however, the APs 62 are indirectly coupled to the Internet 50 via a GTW 48 . Furthermore, in one embodiment, the BS 44 may be considered as another AP 62 . As will be appreciated, by directly or indirectly connecting the mobile terminals 10 and the computing system 52 , the origin server 54 , and/or any of a number of other devices, to the Internet 50 , the mobile terminals 10 can communicate with one another, the computing system, etc,, to thereby carry out various functions of the mobile terminals 10 , such as to transmit data, content or the like to, and/or receive content, data or the like from, the computing system 52 .
- the terms “data,” “content,” “information” and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of the embodiments of the invention.
- the mobile terminal 10 and computing system 52 may be coupled to one another and communicate in accordance with, for example, RF, BT. IrDA or any of a number of different wireline or wireless communication techniques, including LAN, WLAN, WiMAX and/or UWB techniques.
- One or more of the computing systems 52 can additionally, or alternatively, include a removable memory capable of storing content, which can thereafter be transferred to the mobile terminal 10 .
- the mobile terminal 10 can be coupled to one or more electronic devices, such as printers, digital projectors and/or other multimedia capturing, producing and/or storing devices (e.g., other terminals).
- the mobile terminal 10 may be configured to communicate with the portable electronic devices in accordance with techniques such as, for example, RF, BT. IrDA or any of a number of different wireline or wireless communication techniques, including USB, LAN, WLAN, WiMAX and/or UWB techniques.
- techniques such as, for example, RF, BT. IrDA or any of a number of different wireline or wireless communication techniques, including USB, LAN, WLAN, WiMAX and/or UWB techniques.
- FIG. 3 An exemplary embodiment of the invention will now be described with reference to FIG. 3 , in which certain elements of a system for providing confirmed over-the-air (OTA) terminal configuration are displayed.
- the system of FIG. 3 may include, for example, the mobile terminal 10 of FIG. 1 .
- the system of FIG. 3 may also be employed in conjunction with a variety of other devices, both mobile and fixed, and therefore, the embodiments of the present invention should not be limited to application with devices such as the mobile terminal 10 of FIG. 1 .
- FIG. 3 illustrates one example of a configuration of a system for providing efficient evaluation in feature transformation, numerous other configurations may also be used to implement embodiments of the present invention.
- the system includes the mobile terminal 10 and network devices including a device management element 70 , and a server 72 such as a value added server.
- a device management element 70 such as a separate element from the server 72
- the device management element 70 and the server 72 may also be collocated or embodied in a single module, apparatus or device capable of performing the functions of bath the device management element 70 and the server 72 .
- communication between the mobile terminal 10 , the device management element 70 and the server 72 may be either wired or wireless.
- communication between either the device management element 70 or the server 72 and the mobile terminal 10 are conducted wirelessly (i.e., OTA), for example, in accordance with any of the communication mechanisms described above.
- communication between the device management element 70 and the server 72 may be either wired or wireless.
- the device management element 70 may be any device or means embodied in either hardware, software, or a combination of hardware and software capable of transmitting configuration data to the mobile terminal 10 and subsequently initiating a confirmation sequence.
- the device management element 70 may be embodied in software as instructions that are stored on a memory of a network device and executed by a processing element.
- the device management element 70 may include a memory device 74 and a processing element 76 capable of executing instructions stored on the memory device 74 in which the instructions include code portions for initiating the confirmation sequence and transmitting configuration data (i.e. service configuration settings) to the mobile terminal 10 .
- the device management element 70 may include storage for configuration data for transmission to the mobile terminal 10 .
- the device management element 70 may be capable of accessing the configuration data at another network element or device, and thereafter, transmitting the configuration data to the mobile terminal 10 .
- the device management element 70 may be capable of transmitting the configuration data, for example, in response to a user request initiated at the mobile terminal 10 , in response to input by a network operator, or automatically in response to network side or user end originated stimuli.
- the configuration data may be either pulled from the device management element 70 by the mobile terminal 10 or pushed to the mobile terminal 10 from the device management element 70 .
- the server 72 may be any device or means embodied in either hardware, software, or a combination of hardware and software capable of providing a service for which corresponding configuration data stored or otherwise accessible at an external device enables the external device to access the service.
- the server 72 may be an abstract server that provides a service such as, for example, wireless application protocol (WAP), multimedia message service (MMS), Push-to-talk over cellular (PoC), session initiation protocol (SIP), etc.
- WAP wireless application protocol
- MMS multimedia message service
- PoC Push-to-talk over cellular
- SIP session initiation protocol
- the server 72 may include a memory device 80 and a processing element 82 capable of executing instructions stored on the memory device 80 . Accordingly, the memory device 80 may store instructions for execution by the processing element 82 in order to early out particular functions or applications associated with the server 72 .
- the server 72 may include an application program interface (API) for communicating with the device management element 70 in order to enable the server 72 to trigger a server initiated session with the mobile terminal 10 in response to a request from the device management element 70 .
- the server 72 may include an API for initiating a confirmation sequence in response to a request from the device management element 70 .
- the server 72 may request a connection with the mobile terminal 10 , which, if opened, enables the server 72 to send a sample message or sample content to the mobile terminal 10 in order to verify proper receipt of the configuration data. The server 72 may then notify the device management element 70 of the proper receipt of the configuration data at the mobile terminal 10 .
- processing elements 76 and 82 may be embodied in many ways.
- the processing elements 76 and 82 may be embodied as a processor, a coprocessor, a controller or various other processing means or devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit).
- ASIC application specific integrated circuit
- FIGS. 4 and 5 each illustrate a control flow diagram according to an exemplary method for providing confirmed OTA terminal configuration.
- FIG. 4 illustrates an example in which configuration data is properly received at the mobile terminal 10 .
- configuration data i.e., settings for service configuration
- a service or an application e.g., WAP, MMS, PoC, SIP, etc.
- the user may call a particular phone number, send a short message service (SMS) message, activate a link at a particular website, etc., in order to request the configuration data directly, or request the application or service which requires associated configuration data in order for the application or service to be accessible by the mobile terminal 10 .
- SMS short message service
- a network operator or other network device may initiate transmission of the configuration data, for example, to send configuration data corresponding to an upgraded application, a free application, a trial application, a repair, a bug fix, etc. to the mobile terminal 10 .
- the device management element 70 transmits or otherwise communicates configuration data 100 to the mobile terminal 10 .
- the device management element 70 waits a predetermined period of time before initiating a confirmation sequence by sending a session request message 102 to the server 72 .
- the predetermined period of time may be any time period. However, relatively short seconds or minutes) or relatively long time periods (i.e. days) may not be practical. For example, if the predetermined period of time is too short, the configuration data 100 may not be fully received at the mobile terminal 10 due to network delays.
- the user of the mobile terminal 10 may launch or attempt to launch the application corresponding to the configuration settings 100 during the predetermined period of time, thereby either obviating any need or desire to confirm proper receipt of the configuration data 100 (since a successful launch of the application will confirm proper receipt) or subject the user to undesirable aggravation (if the application fails to launch due to failure to properly receive the configuration data).
- the confirmation sequence may be terminated or preempted, since confirmation of proper receipt of the configuration data 100 will have been provided by the successful launch of the application.
- the confirmation sequence which in this exemplary embodiment includes each of the messages exchanged and described below in connection with reference numerals 102 to 112 , confirms OTA proper receipt of the configuration data 100 at the mobile terminal 10 .
- the session request message 102 requests that the server 72 establish a session with the mobile terminal 10 to enable confirmation that the configuration data 100 was properly received at the mobile terminal 10 .
- the server 72 may send an indication 104 to the mobile terminal 10 .
- the indication 104 may request a server initiated session with the mobile terminal 10 .
- the indication 104 may be an MMS message indicating to the mobile terminal 10 that the server 72 has information for the mobile terminal 10 .
- the mobile terminal 10 may establish a connection with the server 72 , For example, the mobile terminal 10 may send a receive MMS 106 to the server 72 requesting the information from the server 72 via the connection.
- the server 72 may transmit sample content 108 to the mobile terminal 10 via the connection.
- the sample content 108 may be, for example, pre-recorded information such as a sample MMS.
- the mobile terminal 10 may send an acknowledgment 110 which is indicative that the sample content 108 has been received at the mobile terminal 10 .
- the server 72 sends a notification message 112 to the device management element 70 to indicate that the configuration data 100 has been properly received at the mobile terminal 10 .
- the device management element 70 may refrain from any further attempts to transmit the configuration data 100 to the mobile terminal 10 ,
- the device management element 70 may itself execute the confirmation sequence.
- messages described above as originating at the server 72 may instead originate at the device management element 70 and communication between the server 72 and the device management element 70 would not be necessary.
- the mobile terminal 10 may receive the request for the server initiated session and the sample content from the device management element 70 and subsequently acknowledge receipt of the sample content to the device management element 70 .
- FIG. 5 illustrates an example in which configuration data is not properly received at the mobile terminal 10 .
- the device management element 70 transmits or otherwise communicates the configuration data 100 to the mobile terminal 10 .
- the device management element 70 waits the predetermined period of time before initiating the confirmation sequence by sending the session request message 102 to the server 72 .
- the server 72 may send the indication 104 to the mobile terminal 10 such as the MMS message indicating to the mobile terminal 10 that the server 72 has information for the mobile terminal 10 .
- the mobile terminal 10 may not establish a connection with the server 72 .
- the server 72 may include (or otherwise be in communication with) a timer 90 capable, for example, of “timing out” in response to expiration of a predetermined period of time between sending the indication 104 and receiving a connection with the mobile terminal 10 . Accordingly, if the timer 90 times out before the connection is established, the timer 90 may send a failure notification message 120 to the device management element 70 indicating that the configuration data 100 has not been properly received at the mobile terminal 10 , Accordingly, the device management element 70 may retransmit the configuration data 100 to the mobile terminal 10 and, after the predetermined period of time, initiate another confirmation sequence as described above.
- a timer 90 capable, for example, of “timing out” in response to expiration of a predetermined period of time between sending the indication 104 and receiving a connection with the mobile terminal 10 . Accordingly, if the timer 90 times out before the connection is established, the timer 90 may send a failure notification message 120 to the device management element 70 indicating that the configuration data 100 has not been properly received at the mobile terminal
- the device management element 70 may include a timing element 92 instead of or in addition to the timer 90 disposed in communication with the server 72 . Accordingly, the timing element 92 of the device management element 70 may “time out” if the notification message 112 is not received from the server 72 within a predetermined period of time from the transmission of the session request message 102 . Additionally or alternatively, in an exemplary embodiment, the timing element 71 may be configured to send an inquiry 122 to the server 72 to check whether the acknowledgment 110 has been received by the server 72 at predetermined intervals.
- the server 72 may be configured to send the notification message 112 in response to receipt of the inquiry 122 instead of sending the notification message 112 in response to receipt of the acknowledgment 110 .
- the processing element 76 may be configured to send a predetermined number of inquiries at intervals controlled by the timing element 92 and, in response to failing to receive the notification message 112 after sending the predetermined number of inquiries, it may be assumed that the configuration data 100 was not properly received at the mobile terminal 10 . Accordingly, the device management element 70 may retransmit the configuration data 100 .
- the device management element 70 may include a limited number of retries, which specifies a predetermined number of attempts at transmitting the configuration data 100 which the device management element 70 may undertake in response to any of the indications above of a failure to properly receive the configuration data 100 at the mobile terminal 10 .
- FIGS. 6 and 7 are flowcharts of a system, method and program product according to exemplary embodiments of the invention. It will be understood that each block or step of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by various means, such as hardware, firmware, and or software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device of the mobile terminal and executed by a built-in processor in the mobile terminal.
- any such computer program instructions may be loaded onto a computer or other programmable apparatus (i.e., hardware) to produce a machine, such that the instructions which execute on the computer or other programmable apparatus create means for implementing the functions specified in the flowcharts block(s) or step(s).
- These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowcharts block(s) step(s).
- the computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowcharts block(s) or step(s).
- blocks or steps of the flowcharts support combinations of means for performing the specified functions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that one or more blocks or steps of the flowcharts, and combinations of blocks or steps in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.
- FIG. 6 shows one embodiment of a method of providing confirmed OTA terminal configuration which includes communicating configuration data to a mobile terminal at operation 200 .
- a confirmation sequence is initiated to confirm proper receipt of the configuration data at the mobile terminal.
- information is received indicating whether the configuration data was properly received at the mobile terminal.
- the confirmation sequence initiation may include the establishment of a connection with the mobile terminal and the sending of a sample message to the mobile terminal to verify that the configuration data was properly received at the mobile terminal.
- the confirmation sequence may be performed by a network device such as a server. The method may include sending an inquiry to the network device to request information regarding whether the configuration data was properly received at the mobile terminal.
- FIG. 7 shows another embodiment of a method of providing confirmed OTA terminal configuration which includes the confirmation sequence as described above.
- This exemplary method may include receiving a request for establishing a server initiated session with a mobile terminal from a network device at operation 300 .
- a connection request is sent to the mobile terminal in response to receipt of the request for establishing the server initiated session.
- a sample message is communicated to the mobile terminal response to an indication of a connection with the mobile terminal at operation 320 .
- a notification is communicated to the network device in response to acknowledgment from the mobile terminal. The notification includes information indicating whether the configuration data was properly received at the mobile terminal.
- the above described functions may be carried out in many ways. For example, any suitable means for carrying out each of the functions described above may be employed to carry out embodiments of the invention. In one embodiment, all or a portion of the elements of embodiments of the invention generally operate under control of a computer program product.
- the computer program product for performing the methods of embodiments of the invention includes a computer-readable storage medium, such as the non-volatile storage medium, and computer-readable program code portions, such as a series of computer instructions, embodied in the computer-readable storage medium.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Human Computer Interaction (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Cold Air Circulating Systems And Constructional Details In Refrigerators (AREA)
- Measuring Volume Flow (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
An apparatus for providing confirmed OTA terminal configuration includes a processing element configured to communicate configuration data to a mobile terminal. The processing element is also configured to initiate a. confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal, and to receive information indicating whether the configuration data was properly received at the mobile terminal.
Description
- This application is a continuation of U.S. patent application Ser. No. 13/874,812, filed May 1, 2013, which is a continuation of U.S. patent application Ser. No. 11/410,810, filed Apr. 25, 2006, now U.S. Pat. No. 8,137,751, issued May 7, 2013, which include exemplary systems and methods and are incorporated by reference in their entirety.
- Embodiments of the present invention relate generally to mobile electronic device technology and, more particularly, relate to methods, apparatuses, and a computer program product for providing over-the-air confirmation of configurations received at mobile electronic devices.
- The modern communications era has brought about a tremendous expansion of wireline and wireless networks, Computer networks, television networks, and telephony networks are experiencing an unprecedented technological expansion, fueled by consumer demand. Wireless and mobile networking technologies have addressed related consumer demands, while providing more flexibility and immediacy of information transfer.
- Current and future networking technologies continue to facilitate ease of information transfer and convenience to users. One area in which there is a demand to increase case of information transfer relates to the delivery of services to a user of a mobile terminal. The services may be in the form of a particular media or communication application desired by the user, such as a music player, a game player, an electronic book, short messages, email, etc. The services may also be in the form of interactive applications in which the user may respond to a network device in order to perform a task or achieve a goal. The services may be provided from applications stored at a network server or other network device, or even at the mobile terminal such as, for example, a mobile telephone, a mobile television, a mobile gaming system, etc.
- For applications which are not already supported at a mobile terminal or which are supported but not ready to use, it is often necessary for a user of the mobile terminal to receive configuration settings from the network prior to launching an application. The configuration settings may be sent over-the-air (OTA) via a wireless communication network. Accordingly, if a new application is downloaded at the mobile terminal, the network will typically transmit corresponding configuration settings to the mobile terminal which will enable the mobile terminal to launch the application in the future. However, it is currently common that if the network sends configuration settings for a new application to the user based on either a user or network initiated request, the network will not know whether the configuration settings have been properly received at the mobile terminal unless the network is notified of such failure by the user. For example, the user may call a network help desk to request retransmission of the settings. Furthermore, even in certain current systems which “confirm” receipt of configuration settings, the confirmation is essentially merely a confirmation that the mobile terminal received at least some settings and not that correct settings have been received. In any case, a failure to verify that proper configuration settings have been received at the mobile terminal can lead to user dissatisfaction and increase consumption of network resources in order to resolve trouble reports resulting from situations in which proper configuration settings are not received at the mobile terminal.
- In light of the shortcomings described above, there may be a need to develop a configuration mechanism capable of verifying that correct configuration settings are received by a mobile terminal OTA.
- Methods, apparatuses and a computer program product are therefore provided that enable confirmed OTA terminal configuration. In particular, a device management system is provided that is capable of transmitting service configuration data to a mobile terminal and subsequently initiating a confirmation sequence to verify that the service configuration data has been correctly received at the mobile terminal Accordingly, in some situations, proper configuration may automatically be ensured prior to a failed user attempt to launch an application, thereby increasing user satisfaction and decreasing impacts upon network resources due to user trouble reporting.
- In one exemplary embodiment, a method of providing confirmed OTA terminal configuration is provided. The method includes communicating configuration data to a mobile terminal, initiating a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal, and receiving information indicating whether he configuration data was properly received at the mobile terminal.
- In another exemplary embodiment, a computer program product for providing confirmed OTA terminal configuration is provided. The computer program product includes at least one computer-readable storage medium having computer-readable program code portions stored therein. The computer-readable program code portions include first, second and third executable portions. The first executable portion is for communicating configuration data. to a mobile terminal. The second executable portion is for initiating a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal. The third executable portion is for receiving information indicating whether the configuration data was properly received at the mobile terminal.
- In another exemplary embodiment, a method of providing confirmed OTA terminal configuration is provided. The method includes receiving a request for establishing a server initiated session with a mobile terminal from a network device, sending a connection request to the mobile terminal in response to receipt of the request for establishing the server initiated session, communicating a sample message to the mobile terminal in response to an indication of a connection with the mobile terminal, and communicating a notification to the network device in response to acknowledgment from the mobile terminal, the notification including information indicating whether the configuration data was properly received at the mobile terminal.
- In another exemplary embodiment, an apparatus for providing confirmed OTA terminal configuration is provided. The apparatus includes a processing element configured to communicate configuration data to a mobile terminal, initiate a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal, and receive information indicating whether the configuration data was properly received at the mobile terminal.
- In another exemplary embodiment, an apparatus for providing confirmed OTA terminal configuration is provided. The apparatus includes a processing element configured to receive a request for establishing a server initiated session with a mobile terminal from a network device, send a. connection request to the mobile terminal in response to receipt of the request for establishing the server initiated session, communicate a sample message to the mobile terminal in response to an indication of a connection with the mobile terminal, and communicate a notification to the network device in response to acknowledgment from the mobile terminal, the notification including information indicating whether the configuration data was properly received at the mobile terminal.
- In another exemplary embodiment, an apparatus for providing confirmed OTA terminal configuration is provided. The apparatus includes a means for communicating configuration data to a mobile terminal, a means for initiating a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal, and a means for receiving information indicating whether the configuration data was properly received at the mobile terminal.
- Having thus described an embodiment of the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
-
FIG. 1 is a schematic block diagram of a mobile terminal according to an exemplary embodiment of the present invention; -
FIG. 2 is a schematic block diagram of a wireless communications system according to an exemplary embodiment of the present invention; -
FIG. 3 illustrates a block diagram of portions of a system for providing confirmed over-the-air (OTA) terminal configuration according to an exemplary embodiment of the present invention; -
FIG. 4 illustrates a control flow diagram for a method of providing confirmed OTA terminal configuration according to an exemplary embodiment of the present invention; -
FIG. 5 illustrates a control flow diagram for a method of providing confirmed OTA terminal configuration according to an exemplary embodiment of the present invention; -
FIG. 6 is a block diagram according to an exemplary method for providing confirmed OTA terminal configuration according to an exemplary embodiment of the present invention; and -
FIG. 7 is a block diagram according to an exemplary method for providing confirmed OTA terminal configuration according to an exemplary embodiment of the present invention. - Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not embodiments of the invention are shown. Indeed, examples of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout.
-
FIG. 1 illustrates a block diagram of amobile terminal 10 that would benefit from embodiments of the present invention. It should be understood, however, that a mobile telephone as illustrated and hereinafter described is merely illustrative of one type of mobile terminal that would benefit from embodiments of the present invention and, therefore, should not be taken to limit their scope. While several embodiments of themobile terminal 10 are illustrated and will be hereinafter described for purposes of example, other types of mobile terminals, such as portable digital assistants (PDAs), pagers, mobile televisions, laptop computers, gaming devices and other types of voice and text communications systems, can readily employ embodiments of the present invention. - In addition, while several embodiments of the method of the present invention are performed or used by a
mobile terminal 10, the method may be employed by other than a mobile terminal. Moreover, the system and method of various embodiments will be primarily described in conjunction with mobile communications applications. It should be understood, however, that the system and method of the various embodiments can be utilized in conjunction with a variety of other applications, both in the mobile communications industries and outside of the mobile communications industries. - The
mobile terminal 10 includes anantenna 12 in operable communication with atransmitter 14 and areceiver 16. Themobile terminal 10 further includes acontroller 20 or other processing element that provides signals to and receives signals from thetransmitter 14 andreceiver 16, respectively. The signals include signaling information in accordance with the air interface standard of the applicable cellular system, and also user speech and/or user generated data. In this regard, themobile terminal 10 is capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, themobile terminal 10 is capable of operating in accordance with any of a number of first, second and/or third-generation communication protocols or the like. For example, themobile terminal 10 may be capable of operating in accordance with second-generation (2G) wireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA), or with third-generation (3G) wireless communication protocols, such as UMTS, CDMA2000, and TD-SCDMA. - It is understood that the
controller 20 includes circuitry required for implementing audio and logic functions of themobile terminal 10. For example, thecontroller 20 may be comprised of a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and other support circuits. Control and signal processing functions of themobile terminal 10 are allocated between these devices according to their respective capabilities. Thecontroller 20 thus may also include the functionality to convolutionally encode and interleave message and data prior to modulation and transmission. Thecontroller 20 can additionally include an internal voice coder, and may include an internal data. modern. Further, thecontroller 20 may include functionality to operate one or more software programs, which may be stored in memory. For example, thecontroller 20 may be capable of operating a connectivity program, such as a conventional Web browser. The connectivity program may then allow themobile terminal 10 to transmit and receive Web content, such as location-based content, according to a Wireless Application Protocol (WAP), for example. Also, for example, thecontroller 20 may be capable of operating a software application capable of analyzing text and selecting music appropriate to the text. The music may be stored on themobile terminal 10 or accessed as Web content. - The
mobile terminal 10 also comprises a user interface including an output device such as a conventional earphone orspeaker 24, aringer 22, amicrophone 26, adisplay 28, and a user input interface, all of which are coupled to thecontroller 20. The user input interface, which allows themobile terminal 10 to receive data, may include any of a number of devices allowing themobile terminal 10 to receive data, such as akeypad 30, a touch display (not shown) or other input device. In embodiments including thekeypad 30, thekeypad 30 may include the conventional numeric (0-9) and related keys (#, *), and other keys used for operating themobile terminal 10. Alternatively, thekeypad 30 may include a conventional QWERTY keypad arrangement. Themobile terminal 10 further includes abattery 34, such as a vibrating battery pack, for powering various circuits that are required to operate themobile terminal 10, as well as optionally providing mechanical vibration as a detectable output. - The
mobile terminal 10 may further include a universal identity module (UIM) 38. TheUIM 38 is typically a memory device having a processor built in. TheUIM 38 may include, for example, a subscriber identity module (SIM), a universal integrated circuit card (UICC), a universal subscriber identity module (USIM), a removable user identity module (R-UIM), etc. TheUIM 38 typically stores information elements related to a mobile subscriber. In addition to theUIM 38, themobile terminal 10 may be equipped with memory. For example, themobile terminal 10 may includevolatile memory 40, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. Themobile terminal 10 may also include othernon-volatile memory 42, which can be embedded and/or may be removable. Thenon-volatile memory 42 can additionally or alternatively comprise an EEPROM, flash memory or the like, such as that available from the SanDisk Corporation of Sunnyvale, California, or Lexar Media Inc. of Fremont, Calif. The memories can store any of a number of pieces of information, and data, used by themobile terminal 10 to implement the functions of themobile terminal 10. For example, the memories can include an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying themobile terminal 10. - Referring now to
FIG. 2 , an illustration of one type of system that would benefit from embodiments of the present invention is provided. The system includes a plurality of network devices. As shown, one or moremobile terminals 10 may each include an antenna. 12 for transmitting signals to and for receiving signals from abuse site or base station (BS) 44. Thebase station 44 may be a part of one or more cellular or mobile networks each of which includes elements required to operate the network, such as a mobile switching center (MSC) 46. As well known to those skilled in the art, the mobile network may also be referred to as a Base Station/MSC/Interworking function (BMI). In operation, theMSC 46 is capable of routing calls to and from themobile terminal 10 when themobile terminal 10 is making and receiving calls. TheMSC 46 can also provide a connection to landline trunks when themobile terminal 10 is involved in a call. In addition, theMSC 46 can be capable of controlling the forwarding of messages to and from themobile terminal 10, and can also control the forwarding of messages for themobile terminal 10 to and from a messaging center. It should be noted that although theMSC 46 is shown in the system ofFIG. 2 , theMSC 46 is merely an exemplary network device and embodiments of the present invention are not limited to use in a network employing an MSC. - The
MSC 46 can be coupled to a data network, such as a local area network (LAN), a metropolitan area network (MAN), and/or a wide area network (WAN). TheMSC 46 can be directly coupled to the data network. In one typical embodiment, however, theMSC 46 is coupled to aGTW 48, and theGTW 48 is coupled to a WAN, such as theInternet 50. In turn, devices such as processing elements (e.g., personal computers, server computers or the like) can be coupled to themobile terminal 10 via theInternet 50. For example, as explained below, the processing elements can include one or more processing elements associated with a computing system 52 (two shown inFIG. 2 ), origin server 54 (one shown inFIG. 2 ) or the like, as described below. - The
BS 44 can also be coupled to a signaling GPRS (General Packet Radio Service) support node (SGSN) 56. As known to those skilled in the art, theSGSN 56 is typically capable of performing functions similar to theMSC 46 for packet switched services. TheSGSN 56, like theMSC 46, can be coupled to a data network, such as theInternet 50. TheSGSN 56 can be directly coupled to the data network. In a more typical embodiment, however, theSGSN 56 is coupled to a packet-switched core network, such as aGPRS core network 58. The packet-switched core network is then coupled to anotherGTW 48, such as a. GTW GPRS support node (GGSN) 60, and theGGSN 60 is coupled to theInternet 50. In addition to theGGSN 60, the packet-switched core network can also be coupled to aGTW 48. Also, theGGSN 60 can be coupled to a messaging center. In this regard, theGGSN 60 and theSGSN 56, like theMSC 46, may be capable of controlling the forwarding of messages, such as MMS messages. TheGGSN 60 andSGSN 56 may also be capable of controlling the forwarding of messages for themobile terminal 10 to and from the messaging center. - In addition, by coupling the
SGSN 56 to theGPRS core network 58 and theGGSN 60, devices such as acomputing system 52 and/ororigin server 54 may be coupled to themobile terminal 10 via theInternet 50,SGSN 56 andGGSN 60. In this regard, devices such as thecomputing system 52 and/ororigin server 54 may communicate with themobile terminal 10 across theSGSN 56,GPRS core network 58 and theGGSN 60. By directly or indirectly connectingmobile terminals 10 and the other devices (e.g.,computing system 52,origin server 54, etc.) to theInternet 50, themobile terminals 10 may communicate with the other devices and with one another, such as according to the Hypertext Transfer Protocol (HTTP), to thereby carry out various functions of themobile terminals 10. - Although not every element of every possible mobile network is shown and described herein, it should be appreciated that the
mobile terminal 10 may be coupled to one or more of any of a number of different networks through theBS 44. In this regard, the network(s) can be capable of supporting communication in accordance with any one or more of a number of first-generation (1G), second-generation (2G), 2.5G and/or third-generation (3G) mobile communication protocols or the like. For example, one or more of the network(s) can be capable of supporting communication in accordance with 2G wireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA). Also, for example, one or more of the network(s) can be capable of supporting communication in accordance with 2.5G wireless communication protocols GPRS, Enhanced Data GSM Environment (EDGE), or the like. Further, for example, one or more of the network(s) can be capable of supporting communication in accordance with 3G wireless communication protocols such as Universal Mobile Telephone System (UMTS) network employing Wideband Code Division Multiple Access (WCDMA) radio access technology. Some narrow-band AMPS (NAMPS), as well as TACS, network(s) may also benefit from embodiments of the present invention, as should dual or higher mode mobile stations (e.g., digital/analog or TDMA/CDMA/analog phones). - The
mobile terminal 10 can further be coupled to one or more wireless access points (APs) 62. TheAPs 62 may comprise access points configured to communicate with themobile terminal 10 in accordance with techniques such as, for example, radio frequency (RF), Bluetooth (BT), infrared (IrDA) or any of a number of different wireless networking techniques, including wireless LAN (WLAN) techniques such as IEEE 802.11 (e.g., 802.11a, 802.11b, 802.11g, 802.11n, etc.), WiMAX techniques such as IEEE 802.16, and/or ultra wideband (UWB) techniques such as IEEE 802.15 or the like. TheAPs 62 may be coupled to theInternet 50. Like with theMSC 46, theAPs 62 can be directly coupled to theInternet 50. In one embodiment, however, theAPs 62 are indirectly coupled to theInternet 50 via aGTW 48. Furthermore, in one embodiment, theBS 44 may be considered as anotherAP 62, As will be appreciated, by directly or indirectly connecting themobile terminals 10 and thecomputing system 52, theorigin server 54, and/or any of a number of other devices, to theInternet 50, themobile terminals 10 can communicate with one another, the computing system, etc,, to thereby carry out various functions of themobile terminals 10, such as to transmit data, content or the like to, and/or receive content, data or the like from, thecomputing system 52. As used herein, the terms “data,” “content,” “information” and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of the embodiments of the invention. - Although not shown in
FIG. 2 , in addition to or in lieu of coupling themobile terminal 10 tocomputing systems 52 across theInternet 50, themobile terminal 10 andcomputing system 52 may be coupled to one another and communicate in accordance with, for example, RF, BT. IrDA or any of a number of different wireline or wireless communication techniques, including LAN, WLAN, WiMAX and/or UWB techniques. One or more of thecomputing systems 52 can additionally, or alternatively, include a removable memory capable of storing content, which can thereafter be transferred to themobile terminal 10. Further, themobile terminal 10 can be coupled to one or more electronic devices, such as printers, digital projectors and/or other multimedia capturing, producing and/or storing devices (e.g., other terminals). Like with thecomputing systems 52, themobile terminal 10 may be configured to communicate with the portable electronic devices in accordance with techniques such as, for example, RF, BT. IrDA or any of a number of different wireline or wireless communication techniques, including USB, LAN, WLAN, WiMAX and/or UWB techniques. - An exemplary embodiment of the invention will now be described with reference to
FIG. 3 , in which certain elements of a system for providing confirmed over-the-air (OTA) terminal configuration are displayed. The system ofFIG. 3 may include, for example, themobile terminal 10 ofFIG. 1 . However, it should be noted that the system ofFIG. 3 , may also be employed in conjunction with a variety of other devices, both mobile and fixed, and therefore, the embodiments of the present invention should not be limited to application with devices such as themobile terminal 10 ofFIG. 1 . It should also be noted, however, that whileFIG. 3 illustrates one example of a configuration of a system for providing efficient evaluation in feature transformation, numerous other configurations may also be used to implement embodiments of the present invention. - Referring now to
FIG. 3 , a system for providing confirmed OTA terminal configuration is provided. The system includes themobile terminal 10 and network devices including adevice management element 70, and aserver 72 such as a value added server. It should be noted that althoughFIG. 3 illustrates thedevice management element 70 as being a separate element from theserver 72, thedevice management element 70 and theserver 72 may also be collocated or embodied in a single module, apparatus or device capable of performing the functions of bath thedevice management element 70 and theserver 72. Additionally, communication between themobile terminal 10, thedevice management element 70 and theserver 72 may be either wired or wireless. However, according to an exemplary embodiment, communication between either thedevice management element 70 or theserver 72 and themobile terminal 10 are conducted wirelessly (i.e., OTA), for example, in accordance with any of the communication mechanisms described above. Meanwhile, communication between thedevice management element 70 and theserver 72 may be either wired or wireless. - The
device management element 70 may be any device or means embodied in either hardware, software, or a combination of hardware and software capable of transmitting configuration data to themobile terminal 10 and subsequently initiating a confirmation sequence. In an exemplary embodiment, thedevice management element 70 may be embodied in software as instructions that are stored on a memory of a network device and executed by a processing element. Alternatively, thedevice management element 70 may include amemory device 74 and aprocessing element 76 capable of executing instructions stored on thememory device 74 in which the instructions include code portions for initiating the confirmation sequence and transmitting configuration data (i.e. service configuration settings) to themobile terminal 10. Accordingly, thedevice management element 70 may include storage for configuration data for transmission to themobile terminal 10. Alternatively, thedevice management element 70 may be capable of accessing the configuration data at another network element or device, and thereafter, transmitting the configuration data to themobile terminal 10. Thedevice management element 70 may be capable of transmitting the configuration data, for example, in response to a user request initiated at themobile terminal 10, in response to input by a network operator, or automatically in response to network side or user end originated stimuli. In other words, the configuration data. may be either pulled from thedevice management element 70 by themobile terminal 10 or pushed to the mobile terminal 10 from thedevice management element 70. - The
server 72 may be any device or means embodied in either hardware, software, or a combination of hardware and software capable of providing a service for which corresponding configuration data stored or otherwise accessible at an external device enables the external device to access the service. In an exemplary embodiment, theserver 72 may be an abstract server that provides a service such as, for example, wireless application protocol (WAP), multimedia message service (MMS), Push-to-talk over cellular (PoC), session initiation protocol (SIP), etc. Theserver 72 may include amemory device 80 and aprocessing element 82 capable of executing instructions stored on thememory device 80. Accordingly, thememory device 80 may store instructions for execution by theprocessing element 82 in order to early out particular functions or applications associated with theserver 72. In an exemplary embodiment, theserver 72 may include an application program interface (API) for communicating with thedevice management element 70 in order to enable theserver 72 to trigger a server initiated session with themobile terminal 10 in response to a request from thedevice management element 70. In other words, theserver 72 may include an API for initiating a confirmation sequence in response to a request from thedevice management element 70. According to an exemplary embodiment, during the confirmation sequence, theserver 72 may request a connection with themobile terminal 10, which, if opened, enables theserver 72 to send a sample message or sample content to themobile terminal 10 in order to verify proper receipt of the configuration data. Theserver 72 may then notify thedevice management element 70 of the proper receipt of the configuration data at themobile terminal 10. - It should be noted that the
processing elements processing elements -
FIGS. 4 and 5 each illustrate a control flow diagram according to an exemplary method for providing confirmed OTA terminal configuration. In this regard,FIG. 4 illustrates an example in which configuration data is properly received at themobile terminal 10. It will be assumed in describingFIGS. 4 and 5 , that configuration data (i.e., settings for service configuration) to support a service or an application (e.g., WAP, MMS, PoC, SIP, etc.) have been requested or otherwise indicated to be delivered to themobile terminal 10. For example, the configuration data may be requested by the user of themobile terminal 10 via an initiation event or trigger as part of a self service program. Accordingly, the user may call a particular phone number, send a short message service (SMS) message, activate a link at a particular website, etc., in order to request the configuration data directly, or request the application or service which requires associated configuration data in order for the application or service to be accessible by themobile terminal 10. As an alternative example, a network operator or other network device may initiate transmission of the configuration data, for example, to send configuration data corresponding to an upgraded application, a free application, a trial application, a repair, a bug fix, etc. to themobile terminal 10. - Accordingly, following receipt of any such initiation event or trigger as described above or otherwise suitable at the
device management element 70, thedevice management element 70 transmits or otherwise communicatesconfiguration data 100 to themobile terminal 10. Following communication of theconfiguration data 100 to themobile terminal 10, thedevice management element 70 waits a predetermined period of time before initiating a confirmation sequence by sending asession request message 102 to theserver 72. The predetermined period of time may be any time period. However, relatively short seconds or minutes) or relatively long time periods (i.e. days) may not be practical. For example, if the predetermined period of time is too short, theconfiguration data 100 may not be fully received at themobile terminal 10 due to network delays. Meanwhile, if the predetermined period of time is too long, the user of themobile terminal 10 may launch or attempt to launch the application corresponding to theconfiguration settings 100 during the predetermined period of time, thereby either obviating any need or desire to confirm proper receipt of the configuration data 100 (since a successful launch of the application will confirm proper receipt) or subject the user to undesirable aggravation (if the application fails to launch due to failure to properly receive the configuration data). Regardless of a length of the predetermined period of time, if the user successfully launches the application at any time between transmission of theconfiguration data 100 and completion of the confirmation sequence, the confirmation sequence may be terminated or preempted, since confirmation of proper receipt of theconfiguration data 100 will have been provided by the successful launch of the application. Unsuccessful user attempts to launch the application may have no effect on the confirmation sequence. The confirmation sequence, which in this exemplary embodiment includes each of the messages exchanged and described below in connection withreference numerals 102 to 112, confirms OTA proper receipt of theconfiguration data 100 at themobile terminal 10. - The
session request message 102 requests that theserver 72 establish a session with themobile terminal 10 to enable confirmation that theconfiguration data 100 was properly received at themobile terminal 10. In response to receipt of thesession request message 102, theserver 72 may send anindication 104 to themobile terminal 10. Theindication 104 may request a server initiated session with themobile terminal 10. For example, theindication 104 may be an MMS message indicating to themobile terminal 10 that theserver 72 has information for themobile terminal 10. In response to receipt of theindication 104, themobile terminal 10 may establish a connection with theserver 72, For example, themobile terminal 10 may send a receiveMMS 106 to theserver 72 requesting the information from theserver 72 via the connection. In response to receipt of the receiveMMS 106, theserver 72 may transmitsample content 108 to themobile terminal 10 via the connection. Thesample content 108 may be, for example, pre-recorded information such as a sample MMS. In response to receipt of thesample content 108, themobile terminal 10 may send anacknowledgment 110 which is indicative that thesample content 108 has been received at themobile terminal 10. By virtue of themobile terminal 10 being able to properly communicate with theserver 72 to acknowledge receipt of thesample content 108, proper receipt of theconfiguration data 100 at themobile terminal 10 is confirmed, - In response to receipt of the
acknowledgment 110, theserver 72 sends anotification message 112 to thedevice management element 70 to indicate that theconfiguration data 100 has been properly received at themobile terminal 10. In response to receipt of thenotification message 112, thedevice management element 70 may refrain from any further attempts to transmit theconfiguration data 100 to themobile terminal 10, - It should be noted that although the preceding was described in the context of an embodiment in which the
device management element 70 requests that theserver 72 conducts the confirmation sequence, other embodiments are also possible. For example, in one exemplary embodiment, thedevice management element 70 may itself execute the confirmation sequence. In other words, messages described above as originating at theserver 72 may instead originate at thedevice management element 70 and communication between theserver 72 and thedevice management element 70 would not be necessary. Furthermore, according to this exemplary embodiment, themobile terminal 10 may receive the request for the server initiated session and the sample content from thedevice management element 70 and subsequently acknowledge receipt of the sample content to thedevice management element 70. -
FIG. 5 illustrates an example in which configuration data is not properly received at themobile terminal 10. Following receipt of any initiation event or trigger as described above, thedevice management element 70 transmits or otherwise communicates theconfiguration data 100 to themobile terminal 10. Following communication of theconfiguration data 100, thedevice management element 70 waits the predetermined period of time before initiating the confirmation sequence by sending thesession request message 102 to theserver 72. In response to receipt of thesession request message 102, theserver 72 may send theindication 104 to themobile terminal 10 such as the MMS message indicating to themobile terminal 10 that theserver 72 has information for themobile terminal 10. In a case in which theconfiguration data 100 is not properly received at themobile terminal 10, themobile terminal 10 may not establish a connection with theserver 72. Theserver 72 may include (or otherwise be in communication with) atimer 90 capable, for example, of “timing out” in response to expiration of a predetermined period of time between sending theindication 104 and receiving a connection with themobile terminal 10. Accordingly, if thetimer 90 times out before the connection is established, thetimer 90 may send afailure notification message 120 to thedevice management element 70 indicating that theconfiguration data 100 has not been properly received at themobile terminal 10, Accordingly, thedevice management element 70 may retransmit theconfiguration data 100 to themobile terminal 10 and, after the predetermined period of time, initiate another confirmation sequence as described above. - It should be noted that although e preceding exemplary embodiment described the
timer 90 disposed in communication with theserver 72, in an alternative exemplary embodiment, thedevice management element 70 may include atiming element 92 instead of or in addition to thetimer 90 disposed in communication with theserver 72. Accordingly, thetiming element 92 of thedevice management element 70 may “time out” if thenotification message 112 is not received from theserver 72 within a predetermined period of time from the transmission of thesession request message 102. Additionally or alternatively, in an exemplary embodiment, the timing element 71 may be configured to send aninquiry 122 to theserver 72 to check whether theacknowledgment 110 has been received by theserver 72 at predetermined intervals. In such an exemplary embodiment, theserver 72 may be configured to send thenotification message 112 in response to receipt of theinquiry 122 instead of sending thenotification message 112 in response to receipt of theacknowledgment 110. Furthermore, theprocessing element 76 may be configured to send a predetermined number of inquiries at intervals controlled by thetiming element 92 and, in response to failing to receive thenotification message 112 after sending the predetermined number of inquiries, it may be assumed that theconfiguration data 100 was not properly received at themobile terminal 10. Accordingly, thedevice management element 70 may retransmit theconfiguration data 100. In an exemplary embodiment, thedevice management element 70 may include a limited number of retries, which specifies a predetermined number of attempts at transmitting theconfiguration data 100 which thedevice management element 70 may undertake in response to any of the indications above of a failure to properly receive theconfiguration data 100 at themobile terminal 10. -
FIGS. 6 and 7 are flowcharts of a system, method and program product according to exemplary embodiments of the invention. It will be understood that each block or step of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by various means, such as hardware, firmware, and or software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device of the mobile terminal and executed by a built-in processor in the mobile terminal. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (i.e., hardware) to produce a machine, such that the instructions which execute on the computer or other programmable apparatus create means for implementing the functions specified in the flowcharts block(s) or step(s). These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowcharts block(s) step(s). The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowcharts block(s) or step(s). - Accordingly, blocks or steps of the flowcharts support combinations of means for performing the specified functions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that one or more blocks or steps of the flowcharts, and combinations of blocks or steps in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.
- In this regard,
FIG. 6 shows one embodiment of a method of providing confirmed OTA terminal configuration which includes communicating configuration data to a mobile terminal atoperation 200. Atoperation 210, a confirmation sequence is initiated to confirm proper receipt of the configuration data at the mobile terminal. Atoperation 220, information is received indicating whether the configuration data was properly received at the mobile terminal. In an exemplary embodiment, as described above, the confirmation sequence initiation may include the establishment of a connection with the mobile terminal and the sending of a sample message to the mobile terminal to verify that the configuration data was properly received at the mobile terminal. In an alternative exemplary embodiment, the confirmation sequence may be performed by a network device such as a server. The method may include sending an inquiry to the network device to request information regarding whether the configuration data was properly received at the mobile terminal. -
FIG. 7 shows another embodiment of a method of providing confirmed OTA terminal configuration which includes the confirmation sequence as described above. This exemplary method may include receiving a request for establishing a server initiated session with a mobile terminal from a network device atoperation 300. Atoperation 310, a connection request is sent to the mobile terminal in response to receipt of the request for establishing the server initiated session. A sample message is communicated to the mobile terminal response to an indication of a connection with the mobile terminal atoperation 320. Atoperation 330, a notification is communicated to the network device in response to acknowledgment from the mobile terminal. The notification includes information indicating whether the configuration data was properly received at the mobile terminal. - The above described functions may be carried out in many ways. For example, any suitable means for carrying out each of the functions described above may be employed to carry out embodiments of the invention. In one embodiment, all or a portion of the elements of embodiments of the invention generally operate under control of a computer program product. The computer program product for performing the methods of embodiments of the invention includes a computer-readable storage medium, such as the non-volatile storage medium, and computer-readable program code portions, such as a series of computer instructions, embodied in the computer-readable storage medium.
- Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which embodiments of these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that embodiments of the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Claims (24)
1. A method comprising:
receiving configuration data at a mobile terminal from a device management element;
receiving, from a server, a request for a connection between the mobile terminal and the server, the request generated by the server in response to initiation of a confirmation sequence by the device management element, the device management element being a separate element from the server;
sending, by the mobile terminal, information indicating whether the configuration data was properly received at the mobile terminal; and
receiving, at the mobile terminal, re-communication of the configuration data from the device management element in response to an indication that the configuration data was not properly received at the mobile terminal.
2. The method of claim 1 , wherein the information indicating whether the configuration data was properly received at the mobile terminal is sent by the mobile terminal to the server.
3. The method of claim 1 , wherein the information indicating whether the configuration data was properly received is information sent during the execution of an application supported by the configuration data.
4. The method of claim 1 , wherein the request for the connection between the mobile terminal and the server is initiated in response to an expiration of a timer associated with the transmission of the configuration data to the mobile terminal.
5. The method of claim 1 , further comprising requesting, by the mobile terminal, the configuration data from the device management element and wherein the configuration data is sent to the mobile terminal in response to the request by the mobile terminal.
6. The method of claim 1 , wherein the request for connection between the mobile terminal and the server comprises a multimedia messaging service (MMS) message.
7. The method of claim 6 , further comprising sending a message from the mobile terminal to the server in response to receiving the request for the connection from the server, the message from the mobile terminal requesting information from the server.
8. The method of claim 7 , further comprising:
receiving, at the mobile terminal, sample content; and
sending, to the server, an acknowledgement indicating that the sample content was received.
9. A computer program product comprising at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising instructions executable by a processor for:
receiving configuration data at a mobile terminal from a device management element;
receiving, from a server, a request for a connection between the mobile terminal and the server, the request generated by the server in response to initiation of a confirmation sequence by the device management element, the device management element being a separate element from the server;
sending, by the mobile terminal, information indicating whether the configuration data was properly received at the mobile terminal; and
receiving, at the mobile terminal, re-communication of the configuration data from the device management element in response to an indication that the configuration data was not properly received at the mobile terminal.
10. The computer program product of claim 9 , wherein the information indicating whether the configuration data was properly received at the mobile terminal is sent by the mobile terminal to the server.
11. The computer program product of claim 9 , wherein the information indicating whether the configuration data was properly received is information sent during the execution of an application supported by the configuration data.
12. The computer program product of claim 9 , wherein the request for the connection between the mobile terminal and the server is initiated in response to an expiration of a timer associated with the transmission of the configuration data to the mobile terminal.
13. The computer program product of claim 9 , wherein the computer-readable program code portions further comprise instructions executable by a processor for: requesting, by the mobile terminal, the configuration data from the device management element and wherein the configuration data is sent to the mobile terminal in response to the request by the mobile terminal.
14. The computer program product of claim 9 , wherein the request for connection between the mobile terminal and the server comprises a multimedia messaging service (MMS) message.
15. The computer program product of claim 14 , wherein the computer-readable program code portions further comprise instructions executable by the processor for: sending a message from the mobile terminal to the server in response to receiving the request for the connection from the server, the message from the mobile terminal requesting information from the server.
16. The computer program product of claim 15 , wherein the computer-readable program code portions further comprise instructions executable by the processor for:
receiving, at the mobile terminal, sample content; and
sending, to the server, an acknowledgement indicating that the sample content was received.
17. An apparatus comprising:
a processing element;
memory coupled to the processing element, the memory storing instructions executable by the processing element for:
receiving configuration data at a mobile terminal from a device management element;
receiving, from a server, a request for a connection between the mobile terminal and the server, the request generated by the server in response to initiation of a confirmation sequence by the device management element, the device management element being a separate element from the server;
sending, by the mobile terminal, information indicating whether the configuration data was properly received at the mobile terminal; and
receiving, at the mobile terminal, re-communication of the configuration data from the device management element in response to an indication that the configuration data was not properly received at the mobile terminal.
18. The apparatus of claim 17 , wherein the information indicating whether the configuration data was properly received at the mobile terminal is sent by the mobile terminal to the server.
19. The apparatus of claim 17 , wherein the information indicating whether the configuration data was properly received is information sent during the execution of an application supported by the configuration data.
20. The apparatus of claim 17 , wherein the request for the connection between the mobile terminal and the server is initiated in response to an expiration of a timer associated with the transmission of the configuration data to the mobile terminal.
21. The apparatus of claim 17 , wherein the computer-readable program code portions further comprise instructions executable by a processor for: requesting, by the mobile terminal, the configuration data from the device management element and wherein the configuration data is sent to the mobile terminal in response to the request by the mobile terminal.
22. The apparatus of claim 17 , wherein the request for connection between the mobile terminal and the server comprises a multimedia messaging service (MMS) message.
23. The apparatus of claim 22 , further comprising instructions executable by the processing element for: sending a message from the mobile terminal to the server in response to receiving the request for the connection from the server, the message from the mobile terminal requesting information from the server.
24. apparatus of claim 23 , further comprising instructions executable by the processing element for:
receiving, at the mobile terminal, sample content; and
sending, to the server, an acknowledgement indicating that the sample content was received.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/624,101 US20150163098A1 (en) | 2006-04-25 | 2015-02-17 | Method, Apparatus and Computer Program Product for Providing Confirmed Over-The-Air Terminal Configuration |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/410,810 US8437751B2 (en) | 2006-04-25 | 2006-04-25 | Method, apparatus and computer program product for providing confirmed over-the-air terminal configuration |
US13/874,842 US8983510B2 (en) | 2006-04-25 | 2013-05-01 | Method, apparatus, and computer program product for providing confirmed over-the-air terminal configuration |
US14/624,101 US20150163098A1 (en) | 2006-04-25 | 2015-02-17 | Method, Apparatus and Computer Program Product for Providing Confirmed Over-The-Air Terminal Configuration |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/874,842 Continuation US8983510B2 (en) | 2006-04-25 | 2013-05-01 | Method, apparatus, and computer program product for providing confirmed over-the-air terminal configuration |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150163098A1 true US20150163098A1 (en) | 2015-06-11 |
Family
ID=38620772
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/410,810 Active 2030-12-07 US8437751B2 (en) | 2006-04-25 | 2006-04-25 | Method, apparatus and computer program product for providing confirmed over-the-air terminal configuration |
US13/874,842 Expired - Fee Related US8983510B2 (en) | 2006-04-25 | 2013-05-01 | Method, apparatus, and computer program product for providing confirmed over-the-air terminal configuration |
US14/624,101 Abandoned US20150163098A1 (en) | 2006-04-25 | 2015-02-17 | Method, Apparatus and Computer Program Product for Providing Confirmed Over-The-Air Terminal Configuration |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/410,810 Active 2030-12-07 US8437751B2 (en) | 2006-04-25 | 2006-04-25 | Method, apparatus and computer program product for providing confirmed over-the-air terminal configuration |
US13/874,842 Expired - Fee Related US8983510B2 (en) | 2006-04-25 | 2013-05-01 | Method, apparatus, and computer program product for providing confirmed over-the-air terminal configuration |
Country Status (5)
Country | Link |
---|---|
US (3) | US8437751B2 (en) |
EP (1) | EP2011351A4 (en) |
KR (1) | KR101038534B1 (en) |
CN (1) | CN101461265A (en) |
WO (1) | WO2007122467A2 (en) |
Families Citing this family (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7844287B2 (en) * | 2006-05-11 | 2010-11-30 | Sony Ericsson Mobile Communications Ab | Automatic spread of applications |
CN101355524B (en) | 2007-07-24 | 2013-10-09 | 华为技术有限公司 | Method, system, server and terminal for processing information |
US8819447B2 (en) * | 2010-03-10 | 2014-08-26 | Sprint Communications Company L.P. | Secure storage of protected data in a wireless communication device |
US8726095B2 (en) * | 2010-12-02 | 2014-05-13 | Dell Products L.P. | System and method for proactive management of an information handling system with in-situ measurement of end user actions |
US8559910B2 (en) * | 2011-04-05 | 2013-10-15 | General Motors Llc. | OTA initiation method for telematics system in 2G GSM/3G WCDMA network |
CN102860049A (en) * | 2011-04-27 | 2013-01-02 | 华为技术有限公司 | Method for processing short messages, related device and system |
GB2492060A (en) * | 2011-06-15 | 2012-12-26 | Blyk Services Oy | Multimedia message delivery platform |
CN102629943B (en) * | 2012-04-05 | 2015-12-09 | 华为终端有限公司 | A kind of method of mobile broadband equipment and mobile broadband service process thereof |
US9124655B2 (en) | 2013-01-30 | 2015-09-01 | Dell Products L.P. | Information handling system operational management through near field communication device interaction |
US9569294B2 (en) * | 2013-01-30 | 2017-02-14 | Dell Products L.P. | Information handling system physical component inventory to aid operational management through near field communication device interaction |
US9198060B2 (en) | 2013-01-30 | 2015-11-24 | Dell Products L.P. | Information handling system physical component maintenance through near field communication device interaction |
CN104219081B (en) * | 2013-06-05 | 2018-11-30 | 富泰华工业(深圳)有限公司 | Network connection management equipment and network connection management method |
US10171501B2 (en) * | 2013-09-20 | 2019-01-01 | Open Text Sa Ulc | System and method for remote wipe |
US10824756B2 (en) | 2013-09-20 | 2020-11-03 | Open Text Sa Ulc | Hosted application gateway architecture with multi-level security policy and rule promulgations |
EP2851833B1 (en) | 2013-09-20 | 2017-07-12 | Open Text S.A. | Application Gateway Architecture with Multi-Level Security Policy and Rule Promulgations |
CN105264943A (en) * | 2013-11-29 | 2016-01-20 | 华为技术有限公司 | Maintenance management method and device, and device maintenance system |
US11593075B2 (en) | 2015-11-03 | 2023-02-28 | Open Text Sa Ulc | Streamlined fast and efficient application building and customization systems and methods |
US11388037B2 (en) | 2016-02-25 | 2022-07-12 | Open Text Sa Ulc | Systems and methods for providing managed services |
CN109844715A (en) * | 2016-11-01 | 2019-06-04 | 惠普发展公司,有限责任合伙企业 | It is realized via the service of resource protocol |
CN108307330B (en) * | 2017-01-13 | 2021-06-18 | 深圳云游四海信息科技有限公司 | Terminal OTA message processing method and system |
CN115103422A (en) * | 2022-06-17 | 2022-09-23 | 北京奔图信息技术有限公司 | Network distribution method, electronic device and readable storage medium |
Citations (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020083331A1 (en) * | 2000-12-21 | 2002-06-27 | 802 Systems, Inc. | Methods and systems using PLD-based network communication protocols |
US20020099842A1 (en) * | 2001-01-19 | 2002-07-25 | Chuck Jennings | System and method for routing media |
US20030204406A1 (en) * | 2002-04-26 | 2003-10-30 | Reardon George R. | System and method for distributing information |
US20040033798A1 (en) * | 2002-08-14 | 2004-02-19 | Robin John F. | Over-the-air programming method for wireless communication device |
US20040087320A1 (en) * | 2002-08-16 | 2004-05-06 | Samsung Electronics Co., Ltd. | Method of transmitting/receiving control message in a mobile communication system providing multimedia broadcast/ multicast service |
US20050030973A1 (en) * | 2000-08-29 | 2005-02-10 | Takuya Kitamura | Media convert service providing method |
US20050114315A1 (en) * | 2003-11-24 | 2005-05-26 | Tanner David A. | Approach for managing network device configuration data |
US20050124367A1 (en) * | 2003-12-08 | 2005-06-09 | Hassan Tariq A. | Optimized push-to-talk call setup |
US20050124366A1 (en) * | 2003-12-08 | 2005-06-09 | Hassan Tariq A. | Directed flood of push-to-talk announce message |
US20050156735A1 (en) * | 2004-01-16 | 2005-07-21 | Humphries L. S. | Method and system for remotely configuring mobile telemetry devices |
US20050228847A1 (en) * | 2004-03-18 | 2005-10-13 | International Business Machines Corporation | Method, system and program product for using open mobile alliance (OMA) alerts to send client commands/requests to an OMA DM server |
US20060059224A1 (en) * | 2004-09-13 | 2006-03-16 | Oki Electric Industry Co., Ltd. | Message reception confirmation method, communications terminal and message reception confirmation system |
US7031267B2 (en) * | 2000-12-21 | 2006-04-18 | 802 Systems Llc | PLD-based packet filtering methods with PLD configuration data update of filtering rules |
US20060165060A1 (en) * | 2005-01-21 | 2006-07-27 | Robin Dua | Method and apparatus for managing credentials through a wireless network |
US20060274696A1 (en) * | 2005-06-07 | 2006-12-07 | Govindarajan Krishnamurthi | Signaling for administrative domain change during location tracking |
US20070110046A1 (en) * | 2003-09-10 | 2007-05-17 | Farrell Richard S | Internet protocol optimizer |
US20070130290A1 (en) * | 2003-11-10 | 2007-06-07 | Ramon Van Der Winkel | Method and system for data transmission between a client and a server, wherein the client selects one out of several physical links |
US20070149226A1 (en) * | 2003-12-23 | 2007-06-28 | Martin De Vries | Controlling reconfiguration in a cellular communication system |
US20070171871A1 (en) * | 2006-01-04 | 2007-07-26 | Nokia Corporation | Secure distributed handover signaling |
US20070180089A1 (en) * | 2006-01-31 | 2007-08-02 | Kenny Fok | Apparatus and methods for providing configurable task management of a wireless device |
US20070254648A1 (en) * | 2006-04-14 | 2007-11-01 | Zhang David X | Fixed mobile roaming service solution |
US20080305773A1 (en) * | 2004-11-30 | 2008-12-11 | Frank Hundscheidt | Method for Delivering Multimedia Files |
US7610239B1 (en) * | 1999-10-06 | 2009-10-27 | Goldman Sachs & Co. | Order centric tracking system and protocol for communications with handheld trading units |
US20090300141A1 (en) * | 2004-09-10 | 2009-12-03 | Samuel Frentzel-Beyme | Self-Distribution Methods, Coded Self-Distribution Methods, and Systems for Distributing Information |
US7653200B2 (en) * | 2002-03-13 | 2010-01-26 | Flash Networks Ltd | Accessing cellular networks from non-native local networks |
US20100122325A1 (en) * | 2005-08-26 | 2010-05-13 | Research In Motion Limited | Data Session Authentication Credentials Update For A Wireless Communication Device |
US20110216726A1 (en) * | 2000-03-10 | 2011-09-08 | Robert Skog | Server and system for mapping a temporary ip address of a mobile device to a subscriber identity number |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5509050A (en) * | 1991-04-16 | 1996-04-16 | Quadphase Corporation | Facsimile radio communication system having multiple data speeds |
JP3033081B2 (en) * | 1992-05-21 | 2000-04-17 | 日本電気株式会社 | Console connection method |
US5603084C1 (en) | 1995-03-02 | 2001-06-05 | Ericsson Inc | Method and apparatus for remotely programming a cellular radiotelephone |
CN1158886C (en) | 1995-10-10 | 2004-07-21 | 奈尔柯姆股份有限公司 | Method and system for over-the-air service programming |
US5887254A (en) | 1996-04-26 | 1999-03-23 | Nokia Mobile Phones Limited | Methods and apparatus for updating the software of a mobile terminal using the air interface |
US6308061B1 (en) * | 1996-08-07 | 2001-10-23 | Telxon Corporation | Wireless software upgrades with version control |
DE69806704T2 (en) | 1997-03-12 | 2003-03-13 | Koninkl Philips Electronics Nv | MONITOR WITH TUBULAR SPEAKERS TO REDUCE THE VIBRATIONS OF THE CATHODE RADIO MASK |
US6195546B1 (en) | 1997-03-14 | 2001-02-27 | Nortel Networks Limited | Method and apparatus for network initiated parameter updating |
FI112427B (en) * | 1999-11-05 | 2003-11-28 | Nokia Corp | A method for determining the capabilities of a wireless terminal in a multimedia messaging service, a multimedia messaging service, and a multimedia terminal |
US6629285B1 (en) * | 2000-01-04 | 2003-09-30 | Nokia Corporation | Data transmission |
US7043530B2 (en) * | 2000-02-22 | 2006-05-09 | At&T Corp. | System, method and apparatus for communicating via instant messaging |
US6622017B1 (en) | 2000-02-25 | 2003-09-16 | Cellco Parntership | Over-the-air programming of wireless terminal features |
US6954448B2 (en) * | 2001-02-01 | 2005-10-11 | Ipr Licensing, Inc. | Alternate channel for carrying selected message types |
US6725040B2 (en) * | 2001-07-09 | 2004-04-20 | Asustek Computer Inc. | Lossless SRNS relocation procedure in a wireless communications system |
US7023876B2 (en) * | 2001-07-09 | 2006-04-04 | Quantum Corporation | Point-to-point protocol |
CA2410143C (en) * | 2001-11-02 | 2010-02-02 | Nippon Telegraph And Telephone Corporation | Optical dynamic burst switch |
US7015817B2 (en) * | 2002-05-14 | 2006-03-21 | Shuan Michael Copley | Personal tracking device |
KR100594110B1 (en) * | 2003-03-08 | 2006-07-03 | 삼성전자주식회사 | System and method for implementing a handoff in a traffic state in a broadband wireless access communication system |
ES2223271B1 (en) * | 2003-06-11 | 2006-04-16 | Diseño De Sistemas En Silicio, S.A. | PROCEDURE TO RELEASE DATA TRANSMITTED BY RECOGNITION IN RECEPTION OR TRANSMISSION. |
US7277416B1 (en) * | 2003-09-02 | 2007-10-02 | Cellco Partnership | Network based IP address assignment for static IP subscriber |
RU2346996C2 (en) | 2004-06-29 | 2009-02-20 | ЮРОПИЭН НИКЕЛЬ ПиЭлСи | Improved leaching of base metals |
US7266106B2 (en) * | 2004-08-31 | 2007-09-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Frame size adaptation in real-time transport protocol |
US7672272B2 (en) * | 2004-08-31 | 2010-03-02 | Telefonaktiebolaget L M Ericsson (Publ) | Frame size adaptation in real-time transport protocol |
US20060083199A1 (en) * | 2004-10-15 | 2006-04-20 | Yang Jianhao M | System, method, and device for handing off between voice over internet protocol over wireless access sessions and CDMA circuit switched voice sessions |
BRPI0419170A (en) | 2004-10-28 | 2008-03-11 | Telecom Italia Spa | network architecture, method for configuring at least one reconfigurable radio terminal, configurable radio terminal, network node, and computing program product |
KR100664180B1 (en) * | 2004-11-22 | 2007-01-04 | 엘지전자 주식회사 | Remote data download apparatus and method for mobile communication device |
US7986665B2 (en) * | 2005-09-23 | 2011-07-26 | Research In Motion Limited | Conferencing PSTN gateway methods and apparatus to facilitate heterogeneous wireless network handovers for mobile communication devices |
US7558950B2 (en) * | 2005-10-27 | 2009-07-07 | Sony Ericsson Mobile Communications Ab | Methods of configuring an electronic device to be operable with an electronic apparatus based on automatic identification thereof and related devices |
-
2006
- 2006-04-25 US US11/410,810 patent/US8437751B2/en active Active
-
2007
- 2007-04-17 EP EP07734321A patent/EP2011351A4/en not_active Withdrawn
- 2007-04-17 WO PCT/IB2007/001002 patent/WO2007122467A2/en active Application Filing
- 2007-04-17 KR KR1020087028661A patent/KR101038534B1/en not_active IP Right Cessation
- 2007-04-17 CN CNA2007800208262A patent/CN101461265A/en active Pending
-
2013
- 2013-05-01 US US13/874,842 patent/US8983510B2/en not_active Expired - Fee Related
-
2015
- 2015-02-17 US US14/624,101 patent/US20150163098A1/en not_active Abandoned
Patent Citations (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7610239B1 (en) * | 1999-10-06 | 2009-10-27 | Goldman Sachs & Co. | Order centric tracking system and protocol for communications with handheld trading units |
US20110216726A1 (en) * | 2000-03-10 | 2011-09-08 | Robert Skog | Server and system for mapping a temporary ip address of a mobile device to a subscriber identity number |
US20050030973A1 (en) * | 2000-08-29 | 2005-02-10 | Takuya Kitamura | Media convert service providing method |
US7031267B2 (en) * | 2000-12-21 | 2006-04-18 | 802 Systems Llc | PLD-based packet filtering methods with PLD configuration data update of filtering rules |
US20020083331A1 (en) * | 2000-12-21 | 2002-06-27 | 802 Systems, Inc. | Methods and systems using PLD-based network communication protocols |
US20020099842A1 (en) * | 2001-01-19 | 2002-07-25 | Chuck Jennings | System and method for routing media |
US7653200B2 (en) * | 2002-03-13 | 2010-01-26 | Flash Networks Ltd | Accessing cellular networks from non-native local networks |
US20030204406A1 (en) * | 2002-04-26 | 2003-10-30 | Reardon George R. | System and method for distributing information |
US20040033798A1 (en) * | 2002-08-14 | 2004-02-19 | Robin John F. | Over-the-air programming method for wireless communication device |
US20040087320A1 (en) * | 2002-08-16 | 2004-05-06 | Samsung Electronics Co., Ltd. | Method of transmitting/receiving control message in a mobile communication system providing multimedia broadcast/ multicast service |
US20070110046A1 (en) * | 2003-09-10 | 2007-05-17 | Farrell Richard S | Internet protocol optimizer |
US20070130290A1 (en) * | 2003-11-10 | 2007-06-07 | Ramon Van Der Winkel | Method and system for data transmission between a client and a server, wherein the client selects one out of several physical links |
US20050114315A1 (en) * | 2003-11-24 | 2005-05-26 | Tanner David A. | Approach for managing network device configuration data |
US20050124367A1 (en) * | 2003-12-08 | 2005-06-09 | Hassan Tariq A. | Optimized push-to-talk call setup |
US20050124366A1 (en) * | 2003-12-08 | 2005-06-09 | Hassan Tariq A. | Directed flood of push-to-talk announce message |
US20070149226A1 (en) * | 2003-12-23 | 2007-06-28 | Martin De Vries | Controlling reconfiguration in a cellular communication system |
US20050156735A1 (en) * | 2004-01-16 | 2005-07-21 | Humphries L. S. | Method and system for remotely configuring mobile telemetry devices |
US20050228847A1 (en) * | 2004-03-18 | 2005-10-13 | International Business Machines Corporation | Method, system and program product for using open mobile alliance (OMA) alerts to send client commands/requests to an OMA DM server |
US20090300141A1 (en) * | 2004-09-10 | 2009-12-03 | Samuel Frentzel-Beyme | Self-Distribution Methods, Coded Self-Distribution Methods, and Systems for Distributing Information |
US20060059224A1 (en) * | 2004-09-13 | 2006-03-16 | Oki Electric Industry Co., Ltd. | Message reception confirmation method, communications terminal and message reception confirmation system |
US20080305773A1 (en) * | 2004-11-30 | 2008-12-11 | Frank Hundscheidt | Method for Delivering Multimedia Files |
US20060165060A1 (en) * | 2005-01-21 | 2006-07-27 | Robin Dua | Method and apparatus for managing credentials through a wireless network |
US20060274696A1 (en) * | 2005-06-07 | 2006-12-07 | Govindarajan Krishnamurthi | Signaling for administrative domain change during location tracking |
US20100122325A1 (en) * | 2005-08-26 | 2010-05-13 | Research In Motion Limited | Data Session Authentication Credentials Update For A Wireless Communication Device |
US20070171871A1 (en) * | 2006-01-04 | 2007-07-26 | Nokia Corporation | Secure distributed handover signaling |
US20070180089A1 (en) * | 2006-01-31 | 2007-08-02 | Kenny Fok | Apparatus and methods for providing configurable task management of a wireless device |
US20070254648A1 (en) * | 2006-04-14 | 2007-11-01 | Zhang David X | Fixed mobile roaming service solution |
Also Published As
Publication number | Publication date |
---|---|
US8437751B2 (en) | 2013-05-07 |
CN101461265A (en) | 2009-06-17 |
WO2007122467A2 (en) | 2007-11-01 |
US8983510B2 (en) | 2015-03-17 |
EP2011351A4 (en) | 2012-10-17 |
US20070250614A1 (en) | 2007-10-25 |
US20130244704A1 (en) | 2013-09-19 |
KR101038534B1 (en) | 2011-06-02 |
KR20090007607A (en) | 2009-01-19 |
EP2011351A2 (en) | 2009-01-07 |
WO2007122467A3 (en) | 2008-01-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8983510B2 (en) | Method, apparatus, and computer program product for providing confirmed over-the-air terminal configuration | |
RU2442295C2 (en) | Apparatus and methods for network identification of open market wireless devices | |
US7752618B2 (en) | Apparatus and method for remote DLL linking of software upgrades for a wireless mobile station | |
CN100484288C (en) | Terminal software for downloading and upgrading wireless device over the air conveying | |
US8750212B2 (en) | Method, apparatus and computer program product for preserving a signaling connection | |
US20100112997A1 (en) | Local triggering methods, such as applications for device-initiated diagnostic or configuration management | |
US10135906B2 (en) | UICC SMS routing to device application | |
US8965339B2 (en) | Automatic oscillating BIP session for SIM self-reactivation | |
US7925258B2 (en) | Method of roaming in broadcast service and system and terminal thereof | |
US20070220498A1 (en) | Method, mobile terminal and computer program product for interworking via a card application toolkit | |
KR20040019838A (en) | System and method for application and application metadata filtering based on wireless device capabilities | |
JP2007512602A (en) | Terminal device settings | |
JP2008067399A (en) | Method for efficiently distributing supplementary services to multi-technology capable wireless transmit/receive units | |
JP2008537868A (en) | Apparatus and method for requesting start of communication session using performance configuration parameters by card application toolkit | |
US20060135165A1 (en) | System and method for proactive, early network switching | |
CN105723778A (en) | Method and apparatus for controlling D2D discovery process | |
US8867726B2 (en) | Methods and systems for authorizing call forwarding | |
KR101148488B1 (en) | Methods, apparatuses, and computer program products, for automatically finding configuration settings for services | |
JP2019154071A (en) | Communication control device and communication setting method | |
JP2008109202A (en) | Mobile communication terminal and control method of mobile communication terminal | |
JP2007208517A (en) | Packet repeater | |
TW201328399A (en) | Apparatus and methods for network identification of open market wireless devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |