[go: up one dir, main page]

HK1134734A - System and method for handshaking between wireless devices and servers - Google Patents

System and method for handshaking between wireless devices and servers Download PDF

Info

Publication number
HK1134734A
HK1134734A HK10101703.4A HK10101703A HK1134734A HK 1134734 A HK1134734 A HK 1134734A HK 10101703 A HK10101703 A HK 10101703A HK 1134734 A HK1134734 A HK 1134734A
Authority
HK
Hong Kong
Prior art keywords
wireless device
attributes
application
storage space
attribute corresponding
Prior art date
Application number
HK10101703.4A
Other languages
Chinese (zh)
Inventor
J‧B‧肯纳格
R‧D‧布瑞格
G‧M‧伦巴底
M‧斯达斯卡
M‧S‧菲利浦
R‧J‧米勒
Original Assignee
高通股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 高通股份有限公司 filed Critical 高通股份有限公司
Publication of HK1134734A publication Critical patent/HK1134734A/en

Links

Description

System and method for handshaking between a wireless device and a server
This application is a division of the application of chinese patent application No. 200380108122.2 entitled "system and method for handshaking between a wireless device and a server" filed 12/4/2003.
Technical Field
The present invention relates generally to computer device networks and communications. More particularly, the present invention relates to computer device interface protocols and data transfer while bridging an initial communication connection and during ongoing communications between computer devices on a wireless network.
Background
Wireless devices, such as mobile phones, transmit packets including voice and data over a wireless network. In existing wireless networks, upon initial contact between two computer devices on the wireless network, the devices begin to exchange summary information, which is referred to as a "handshake". The handshaking process allows the computer devices to initially synchronize the data channels and communicate the relevant data necessary to maintain a satisfactory connection between the devices. The computer device may also add handshaking activity in order to maintain a satisfactory connection during the communication after the initial contact has been bridged.
In analog or digital wireless cellular networks, there is an initial handshake session between a cellular device and a base station. Typically, when the device is turned on, the mobile switch determines the identity of the device, such as by Mobile Identification Number (MIN), and determines what cell will carry the transmission from the device, and the mobile switch allocates a free channel within the cell to take the voice or data transmission from the device. Preliminary data, such as device pattern recognition, may also be exchanged in the initial registration of the cellular device. Ongoing data exchange also takes place in the cellular network, but typically solely manages "handovers", or physical movement of devices from cell to cell. When the signal of the device falls below the handover threshold, the base station serving the ongoing communication sends a handover request to the mobile exchange.
With complex devices, the data necessary for the exchange can be considerable in order to establish robust communication when device contact is initiated. Moreover, if increasingly complex activities such as data or application transfers are undertaken during the communication, then significant handshaking communications may disrupt or service the current communication connection. Accordingly, the present invention is primarily directed to a system for improving handshaking between computer devices across a wireless network.
Disclosure of Invention
The present invention is a method, system, and computer program for data communication or "handshaking" between a wireless device and a server, such as an application download server, on a wireless network. As soon as the wireless device communicates with the application download server, the server obtains data from the wireless device that represents wireless device attributes during a "handshaking session" and determines to access the application based on the wireless device attributes. The application program may reside on the server or on another computer device of the wireless network.
In selective communication with the wireless network, the interface system includes one or more wireless devices, each wireless device having its attributes and a computer platform for selectively executing computer programs thereon, each wireless device further having an end-user selectively accessible to the computer platform, and one or more application download servers in selective communication with the wireless network, each application download server having at least one resident application and selectively downloading applications to the wireless device. Once the wireless device begins communicating with the application download server over the network, the application download server obtains data from the wireless device representing attributes of the wireless device to determine access by the wireless device to applications, such as computer programs, graphics, menus, etc., resident on or controlled by the application download server.
The method of communication between a wireless device and an application download server on a wireless network includes, inter alia, the steps of: the method includes the steps of communicating from the wireless device to a server over a wireless network, obtaining data from the wireless device representative of attributes of the wireless device, and determining access by the wireless device to an application resident on or controlled by the application download server based on the wireless device attributes. The step of obtaining data from the wireless device may receive wireless device attributes at an application download server where the application intended to be downloaded by the wireless device resides. Further, the step of obtaining data from the wireless device may occur when the wireless device begins to contact the application download server, or when the wireless device attempts to download an application while in communication.
The present invention thus allows the data communication necessary between a sophisticated wireless device and an application download server to manage the device's access to available applications over a wireless network. By transferring attribute data such as hardware and software capabilities and user identity, the risk of the device accessing useless or inappropriate software is minimized. Moreover, if increasingly complex activities are undertaken in the data communication between the wireless device and the server, further non-intrusive handshakes may occur to maintain access control without disrupting existing connections.
Other objects, advantages and features of the present invention will become apparent after review of the hereinafter set forth brief description of the drawings, detailed description of the invention and the claims.
Drawings
FIG. 1 is a representative diagram of a wireless network and a wireless device in bridge communication with a server and other computer devices over the network;
FIG. 2 is a block diagram of the hardware components of a wireless network providing communication between different wireless devices and an application download server over a cellular telecommunications network;
FIG. 3 is a block diagram of a wireless device computer platform that interfaces with an application download server and executes one or more applications on the wireless device platform;
FIG. 4 is a block diagram of an application download server in communication with a wireless device through a load balancing server;
FIG. 5 is a flowchart of a process executing on an application download server that receives a communication attempt from a wireless device and obtains wireless device attributes to determine application access;
fig. 6 is a flow chart of a process executing on a wireless device attempting to contact an application download server and selectively providing wireless device attributes to the server.
Detailed Description
Reference is made to the drawings wherein like reference numerals refer to like parts. Fig. 1 illustrates one embodiment of the handshaking system 10 of the present invention, which is a handshake between one or more wireless devices, such as a mobile telephone 12, in communication over a wireless network 14 with at least one application download server 16, which application download server 16 downloads software applications or other data to the wireless devices through a wireless communication portal or other data access to the wireless network 14. As shown therein, the wireless device may be a mobile telephone 12 with a graphics display 13, a personal digital assistant 18, a pager 20 with a graphics display, which is a two-way text pager in this case, or even a separate computer platform 22 that has a wireless communication portal, and may otherwise have a wired connection 24 to a network or the Internet. The system 10 can be implemented on any form of remote computer module including, but not limited to, a wireless communication portal, a wireless modem, a PCMCIA card, an access terminal, a personal computer, an access terminal, a telephone without a display or keyboard, or any combination or subcombination thereof. The term "application" is used herein to include executable and non-executable software files, raw data, aggregated data, patches, graphics, menus, and other code segments. The application or code segment may reside, run on the wireless device 12, 18, 20, 22, and/or may be used on the wireless device 12, 18, 20, 22 as "client" software, or may be a network-based or distributed application rather than a client-based application.
In the system 10, one or more wireless devices 12, 18, 20, 22 selectively communicate with the wireless network 14, each having an end-user that typically controls the communication connection with the wireless network 14, and that end-user will attempt to download applications or data from the application download server 16 over the wireless network. The application download server 16 typically has at least one resident application and selectively communicates with and selectively downloads applications to one or more wireless devices 12, 18, 20, 22 over a network, such as the mobile telephone network shown in fig. 2. The server 16 may also control access by the wireless devices 12, 18, 20, 22 to applications residing on other data stores, such as the database 28, the second application download server 30, or a separate server 32. The system 10 facilitates an application download process, which is: data representing wireless device attributes is obtained from the wireless devices 12, 18, 20, 22 by the application download server 16, and then access to accessible applications by the wireless devices is determined by the application download server 16 based on the wireless device attributes. The handshake may communicate the device attributes at the beginning of contact, or as soon as the wireless device 12, 18, 20, 22 attempts to access the application while in communication.
The system 10 thus addresses the desire that end users be able to run applications on their wireless devices, such as 3G mobile phones, that are different from the applications used to make the phones. It is apparent to the system 10 that the available applications are filtered to the wireless devices 12, 18, 20, 22, i.e., no knowledge/awareness of the end user is required. For example, the wireless devices 12, 18, 20, 22 may be manufactured with address books that are not user-friendly and/or synchronized with the address book used by the user on a separate personal computer. The end user thus wishes to download an address book that is more user friendly and has the desired synchronization capabilities. Other examples of programs are games, mapping applications (position location applications), and "bluetooth" remote controls. Since the end-user may be charged a start time to download the application, the end-user desires a way to determine whether the application will actually run on the end-user wireless device 12, 18, 20, 22 prior to the application being downloaded. Without such a determination prior to application download, the end-user may spend time downloading useless applications. Also, if the end user cannot determine why the application is not running, the end user fails, which will generate a customer service call. Thus, when an end-user attempts to download an application over the data interface, handshaking is utilized to determine the performance of the wireless device before actual downloading is allowed. If, and only if, the handshake agrees that the wireless device 12, 18, 20, 22 supports all of the requirements of the application, the application is downloaded. Further, instead of denying the download, other results may also occur, such as multi-level results, e.g., "impossible," possible, "" not recommended, "and" additional suggestions.
One or more application download servers 16, such as the application download server 16 that provides applications to the wireless devices 12, 18, 20, 22, are shown on the local server side network 26 with other computer components in communication with the wireless network 14. The stored application database 28 may contain software applications and data that may be executed on the wireless devices 12, 18, 20, 22 either directly or through the application download server 16. There is also a separate server 32, a second application download server 30 that provides applications and other functionality to the wireless devices 12, 18, 20, 22. All of the components may work in tandem to provide application access, as will be further described. However, it should be noted that all server-side functions may also be performed on one server, such as the application download server 16. Moreover, any computer or server-side computer platform may provide separate services and programs to the wireless devices 12, 18, 20, 22 across the wireless network 14.
Fig. 2 is a block diagram that more fully describes the interrelation of the components of the wireless network 14 and the components of the system 10 on a cellular telecommunications network. The wireless network 14 is merely exemplary and can include a system whereby remote modules, such as wireless devices 12, 18, 20, 22, communicate over the air between and among each other and/or between and among components of a wireless network 14, including, without limitation, wireless network carriers and/or servers. A series of application download servers 40 (which will be described further below) communicate with a series of load balancing servers 42 to help manage the flow of data to the series of servers 42. The load balancing server 42 communicates with a series of routers 44 that ultimately connect to a carrier network 46, which may be a Virtual Private Network (VPN) router. The other server-side component will be located on the cellular data network with any other components necessary to provide cellular telecommunications services. Thus, by adding components, the server-side support is easily upgraded.
The router 44 communicates with the carrier network 46 over a data link, such as the internet, a secure Local Area Network (LAN), a Wide Area Network (WAN), or other network. The carrier network 46 controls messages (typically in the form of data packets) sent to a messaging service controller ("MSC") 48. The carrier network 46 communicates with the MSC48 by a network, the internet and/or POTS (plain ordinary telephone system). The network or internet connection between the carrier network 46 and the MSC48 typically transfers data, and the POTS transfers voice information. The MSC48 is coupled to a plurality of base stations ("BTSs") 50. The MSC48 is connected to the BTS 50, typically by a network and/or the internet that transmits data and a POST that transmits voice information, in the same manner as being connected to the carrier network. The BTS 50 ultimately broadcasts messages wirelessly to wireless devices, such as mobile telephones 12, via short message service ("SMS"), or other over-the-air methods known in the art.
Referring to fig. 3, shown is a block diagram of a wireless device computer platform 60 that can receive and execute one or more software applications in an application layer 68, wherein the applications are transferred from the application download server 16. The computer platform 60 includes, among other components, an application specific integrated circuit ("ASIC") 62, or other processor, microprocessor, logic circuit, programmable gate array, or other data processing device. The ASIC 62 is installed at the time of manufacture of the wireless device, and the ASIC 62 is typically not upgradeable. The ASIC 62 or other processor executes an application program interface ("API") layer 64 that interfaces with a device operating layer 66 that supports the execution of any resident programs in the memory of the wireless device 12, 18, 20, 22. The memory can be comprised of read-only or random-access memory (RAM or ROM), EPROM, EEPROM, flash cards, or any memory common to computer platforms. The computer platform 60 also communicates with a local database that may hold infrequently used software applications in memory, such as software applications downloaded from the application download server 16. The local database is typically comprised of one or more flash memory cells, but may be any secondary or tertiary storage device as known in the art, such as magnetic media, EPROM, EEPROM, optical media, tape, or soft or hard disk. The OS layer 66 is embedded and contacts the application download server 16 through HTTP/SSL and TCP/IP exchanges that occur through the carrier network 46.
Fig. 4 illustrates one embodiment of the data interface where the application download server 16 is a "thin" server that interfaces with the load balancing interface server 68. The load balancing server ultimately supports communication with wireless devices, such as mobile telephones 12. It should be noted that while the application download server 16 is shown in an IP connection operating over CDMA, the system 10 may support different connections operating over different wireless interfaces, such as a wireless interface based on the bluetooth protocol. The application download server 16 includes a JAVA servlet engine that includes active servlet threads and cached program threads, which are contacted by the cache 74 with a web server 76. It can thus be seen that a separate computer device may include the application download server 16, if desired. The web server 76 interfaces with the load balancer 68 through the cache 78 and the load balancing system 70, which may also be a separate computer device. The load balancer ultimately contacts the wireless devices 12, 18, 20, 22 to distribute the data load to the sequence of application download servers (40 in fig. 2) in the most efficient manner.
In operation, when either an initial handshake is selected or an application is selected to be downloaded by a handshake when a download is attempted between the wireless device 12, 18, 20, 22 and the application download server 16, information about the application requirements is compared in the application download server 16 to the available capabilities of the wireless device. In one embodiment, the application download server 16 includes an information file that specifies application requirements such as the characteristics and categories of application requirements. For example, a mapping application may require access to a class of locations and places to query the device's current latitude and longitude, parameters to display a bitmap drawn on the device's display, menu capabilities to generate a drop-down menu, end-user input capabilities, and network capabilities such as TCP/IP connections. Another example of an attribute is accessing a third party library. In order to properly use a drawing program in a drawing application instance, it is necessary to access a third party library of drawings. The information file may also contain a specific file system and also require RAM memory. For example, a particular information file may describe an application program that is 100K in size, so the wireless device must have 100K of file system space to store the download and 100K of RAM is required to load the application program during runtime. The information file may also contain other hardware requirements such as the number of colors required on the display, the display screen size, the processor speed, or any other criteria that may affect the successful download and execution of the application.
In one embodiment, the handshake has the contents of an information file transmitted from the application download server 16 to the wireless device 12, 18, 20, 22. In such an embodiment, the wireless device determines whether it supports all of the requirements outlined in the information file. If the wireless device 12, 18, 20, 22 allows these features of the application to be supported, the application begins to be downloaded after the handshake. Otherwise if not all necessary features are supported, a message will be displayed to the end user: applications cannot be downloaded because the wireless device does not meet certain requirements. Such a message may be automatically generated by the wireless device 12, 18, 20, 22 or may be obtained from a server, such as the second server 32 or other server on the wireless network 14. If such an error message embedded therein is sent from a server 16, 30, 32, the network operator may customize the message for user care purposes.
It should also be noted that there may be additional steps on the wireless device 12, 18, 20, 22 to remedy the reason that the application cannot be downloaded. For example, if the only reason for the download failure is that certain software classes or libraries are not resident on the wireless device platform 60 necessary to support the application, the wireless device 12, 18, 20, 22 may attempt to download these classes or libraries rather than immediately issue a download failure message. If these classes/libraries download is successful, the application can then be downloaded.
In another embodiment, rather than transmitting the information file from the application download server 16 to the wireless device 12, 18, 20, 22, the wireless device transmits the attributes of the wireless device to the application download server 16. As an example, the wireless device transmits to the application download server that it has 400K of RAM available, 1MB of flash available, a 60 x 75 display screen with an 8-bit color display, and that it has the network category-bluetooth category. In this case, the application is downloaded only if the application download server 16 determines that the wireless device 12, 18, 20, 22 supports everything that is required for the application. Otherwise, the application download server 16 may return an error to the wireless device attempting the download.
Fig. 5 depicts a flowchart of one embodiment of the process executing on the application download server 16 that contacts a wireless device, such as the mobile telephone 12. As shown at step 80, the application download server 16 receives a connection attempt from the wireless device 12, 18, 20, 22 and sends a request to the wireless device to obtain wireless device attributes, as shown at step 82. In this embodiment, the application download server 16 then determines whether permission has been received for the end-user of the wireless device 12, 18, 20, 22 to obtain the attributes, as shown at decision 84, or else returns an error to the end-user, refuses the requested access, as shown at step 86, and then the process returns to await the connection attempt at step 80. If the end-user of the wireless device 12, 18, 20, 22 does grant permission to access the wireless device attributes at decision 84, then the wireless device attributes are obtained from the wireless device, as shown at step 90, which may occur through the file exchange between the application download server 16 and the wireless device 12, 18, 20, 22 as described above. It should be noted that the decision 84 is only to avoid unnecessary wireless device access by the application download server 16 and is not necessary to implement the system 10.
Once the wireless device attributes are obtained, a determination is made as to whether the wireless device has access to the requested application, as shown at decision 90. If the wireless device cannot access the application for some reason, such as insufficient hardware or software capacity, an error is returned to the end user as shown in step 86 and the process returns to await further connection attempts from the wireless device at step 80. If the wireless device 12, 18, 20, 22 can download the application, the requested application is provided to the wireless device, as shown at step 92, and then a determination is made as to whether the end-user requests access to the new application, as shown at decision 100. If the end-user has not requested a new application, the process enters a wait state at decision 100, which is associated with a particular thread of contact with the wireless device. Otherwise if the end user requests another application, the process repeats step 80 and treats the request as if it were a new connection attempt.
Fig. 6 illustrates a parallel process that occurs at the wireless device 12, 18, 20, 22, wherein the wireless device contacts the application download server 16 of fig. 5. The wireless device attempts to access the application as shown at step 102 and connects with any server on the wireless network 14 indicating that it provides access to the requested application. The wireless device then determines whether the application download server 16 has sent a request to access wireless device attributes, as shown in decision 104. If the request has not been sent, the wireless device assumes that no comparison is needed and waits for access to the application at decision 114. If permission to access the wireless device attributes has been requested at decision 104, end user permission is requested at shown step 106, and it is then determined whether the end user allows attribute access, as shown at decision 108.
If the end user does not allow attribute access at decision 108, an error is returned to the end user as shown at step 110 indicating that the requested application cannot be accessed and the thread of execution of the process terminates. Otherwise, if the end-user allows access to the attributes, the attributes are sent to the application download server 16, as shown at step 112. Step 112 is just one embodiment of this process and the wireless device 12, 18, 20, 22 does not have to send its attributes to the application download server 16 via a file or other data, but can only provide access to the attributes to a proxy server so that the attributes are searchable, or by any other data gathering method known in the art. After the attributes have been sent at step 112, a determination is made as to whether the wireless device accessed the requested application as shown at decision 114, otherwise an error is returned to the end user at step 110 and the application access thread terminates. Otherwise, if access is allowed at decision 114, the process thread terminates only on the wireless device 12, 18, 20, 22. Once the end-user requests access to another application over the network, the process will begin again at step 102.
The system 10 thus provides a method of communicating between a wireless device 12, 18, 20, 22 and an application download server 16 on a wireless network 14, comprising the steps of communicating from the wireless device 12, 18, 20, 22 to the application download server 16 across the wireless network 14, wherein the wireless device has an attribute and a computer platform 60 that selectively executes computer programs thereon, and the wireless device further has an end user that can selectively access the computer platform 60, and the application download server 16 has at least one downloadable application resident thereon. The method further includes the step of obtaining data from the wireless device 12, 18, 20, 22 representative of attributes of the wireless device and then determining, by the application download server 16, access by the wireless device 12, 18, 20, 22 to the accessible applications based on the wireless device attributes. The step of obtaining data from the wireless device 12, 18, 20, 22 may be obtaining attributes of the wireless device including data related to the computer platform 60 and/or software resident on the wireless device computer platform 60.
The step of obtaining data from the wireless device 12, 18, 20, 22 may be receiving wireless device attributes at the application download server 16, with the application download server 16 having resident thereon the application that the wireless device 12, 18, 20, 22 desires to download. The step of obtaining data from the wireless device 12, 18, 20, 22 may occur when contact with the application download server 16 is initiated by the wireless device or, alternatively, may occur when the wireless device attempts to download an application. The method may further comprise the steps of: in attempting to download the application, the end-user of the wireless device 12, 18, 20, 22 is prompted to request access to the wireless device attributes, and the wireless device attributes are transmitted to the application download server 16 upon granting permission to the user.
If the system 10 is such, the method may further include the step of transmitting to the wireless device 12, 18, 20, 22 the requirements of the application requested for download, and indicating whether a download is possible based on the received requirements. Optionally, the method may comprise: the step of transmitting the requirements of the application requested to be downloaded to the wireless device 12, 18, 20, 22 may be transmitting the requirements from the application download server 16 on which the application resides, and the step of indicating whether the download is possible is transmitting data from the wireless device 12, 18, 20, 22 to the application download server 16 to indicate whether the download is possible.
Upon failure of the download by the wireless device 12, 18, 20, 22, the method may include the step of notifying the end user of the download failure.
In view of the method being performed on the computer platform of the wireless device 12, 18, 20, 22, the present invention includes a program resident in a computer readable medium, where the program directs a server or other computer device having a computer platform to perform the steps of the method. The computer readable medium may be the memory of the application download server 16 or may be in a connection database such as database 28. Moreover, the computer readable medium can be in a secondary storage media that is carried on the wireless device computer platform, such as a magnetic disk or tape, optical disk, hard disk, flash memory, or other storage media as is known in the art.
In the case of fig. 5 and 6, for example, the method may be implemented by operating portions of the wireless network 14 such as the wireless device computer platform 60, the application download server 16 and the separate server 32 to execute a series of machine readable instructions. The instructions may reside in different types of primary, secondary, or tertiary media. The media may comprise, for example, RAM (not shown) accessible by, or residing within, the components of the wireless network 14. Whether contained in RAM, a diskette, or other secondary storage media, the instructions may be stored on a variety of machine-readable data storage media, such as DASD storage (e.g., a conventional "hard disk" or a RAID array), magnetic tape, electronic read-only memory (e.g., ROM, EPROM, or EEPROM), flash memory cards, an alternative storage device (e.g., a CD-ROM, WORM, DVD, or digital optical disk), paper punch cards (paper punch cards), or other suitable data storage media including digital and analog transmission media.
The foregoing disclosure describes illustrative embodiments of the present invention and it is noted that various changes and modifications can be made herein without departing from the scope of the invention as defined by the appended claims. Furthermore, although elements of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claims (46)

1. A wireless device, comprising:
a wireless communication interface providing communication between the wireless device and a server over a wireless network; and
a computer platform connected to the wireless communication interface and for controlling the wireless communication interface, the computer platform further for maintaining an application runtime environment for downloaded applications, the computer platform comprising data processing circuitry supporting an operating system and a first set of attributes;
wherein
The first set of attributes representing performance of the wireless device;
the operating system includes first logic that causes the computer platform to perform a comparison between the first set of attributes and a second set of attributes received from the wireless communication interface in response to an application download request made by the wireless device to a server for an application;
the second set of attributes represents requirements of the application requesting download, and
the operating system includes a second logic that causes the computer platform to prevent downloading of the application from the server to the wireless device if the comparison indicates that the application is not compatible with the during-application-run environment, and causes the computer platform to download the application if the comparison indicates that the application is compatible with the during-application-run environment.
2. The wireless device of claim 1, wherein the second set of attributes is received by the wireless device as part of a file sent to the wireless device from a server.
3. The wireless device of claim 1, wherein the preventing operation is performed by refraining from initiating a download operation for an application and displaying an associated error message on the wireless device.
4. The wireless device of claim 1, wherein the first set of attributes comprises: at least one attribute corresponding to a plurality of classes available in an environment during execution of the application.
5. The wireless device of claim 1, wherein the first set of attributes comprises:
at least one attribute corresponding to a plurality of libraries available in an environment during execution of the application.
6. The wireless device of claim 1, wherein the first set of attributes comprises:
at least one attribute corresponding to a plurality of libraries that are environmentally accessible during the running of the application.
7. The wireless device of claim 1, wherein the first set of attributes comprises:
an attribute identifying a size of available storage space of an environment during execution of the application.
8. The wireless device of claim 7, wherein the size of the available storage space is a size of available storage space in a random access memory portion of the storage space.
9. The wireless device of claim 7, wherein the size of the available storage space is the size of the available storage space in a file system portion of the storage space.
10. The wireless device of claim 1, wherein the second set of attributes comprises:
at least one attribute corresponding to a plurality of classes required to support execution of the application.
11. The wireless device of claim 1, wherein the second set of attributes comprises: at least one attribute corresponding to a plurality of libraries required to support execution of the application.
12. The wireless device of claim 1, wherein the second set of attributes comprises: at least one attribute corresponding to a plurality of third party libraries required to support execution of the application.
13. The wireless device of claim 1, wherein the second set of attributes comprises:
an attribute identifying a size of available storage space required to support execution of the application program.
14. The wireless device of claim 13, wherein the size of the available storage space is a size of available storage space in a random access memory portion of the storage space.
15. The wireless device of claim 13, wherein the size of the available storage space is the size of the available storage space in a file system portion of the storage space.
16. The wireless device of claim 4, wherein the plurality of classes available in the environment during the application run comprise: a class of locations and localities operable when querying the latitude and longitude of the wireless device.
17. The wireless device of claim 1, further comprising a display device operable by the computer platform, the display device further having display device characteristics available in an environment during execution of the application program, wherein the first set of attributes comprises: at least one attribute corresponding to a characteristic of the display device.
18. The wireless device of claim 1, wherein at least one of the first set of attributes and the second set of attributes comprises at least one attribute corresponding to a network connection characteristic.
19. The wireless device of claim 1, wherein at least one of the first set of attributes and the second set of attributes comprises at least one attribute corresponding to a processor speed characteristic.
20. The wireless device of claim 1, wherein at least one of the first set of attributes and the second set of attributes comprises at least one attribute corresponding to a characteristic of an end-user input means.
21. The wireless device of claim 1, wherein at least one of the first set of attributes and the second set of attributes comprises at least one attribute corresponding to a characteristic related to execution of an application program.
22. The wireless device of claim 1, wherein at least one of the first set of attributes and the second set of attributes comprises a plurality of attributes corresponding to a plurality of characteristics related to execution of an application.
23. The wireless device of claim 1, wherein at least one of the first set of attributes and the second set of attributes comprises at least one attribute corresponding to a menu generation characteristic.
24. A method operational on a wireless device, the method managing requests for download of applications stored on a server over a wireless network, the method comprising:
sending a request for downloading an application program to a server;
receiving a second set of attributes representing requirements of the application requesting download;
comparing the second set of attributes to a first set of attributes representing performance of a wireless device to determine whether an application is compatible with the application runtime environment;
if the comparison result indicates that the application program is not compatible with the environment during the running of the application program, the downloading operation of the application program is prevented; and is
And downloading the application program if the comparison result indicates that the application program is compatible with the environment during the running of the application program.
25. The method of claim 24, wherein the second set of attributes is received in a file sent by a server.
26. The method of claim 24, wherein the step of preventing comprises:
avoiding starting an operation of downloading an application program from a server; and
displaying an error message on the wireless device.
27. The method of claim 24, wherein the first set of attributes comprises: at least one attribute corresponding to a plurality of classes available in the runtime environment.
28. The method of claim 24, wherein the first set of attributes comprises:
at least one attribute corresponding to a plurality of libraries available in the runtime environment.
29. The method of claim 24, wherein the first set of attributes comprises:
at least one attribute corresponding to a plurality of libraries accessible to the runtime environment.
30. The method of claim 24, wherein the first set of attributes comprises:
an attribute identifying a size of available storage space of an environment during execution of the application.
31. The method of claim 30, wherein the size of the available storage space is the size of the available storage space in a random access memory portion of the storage space.
32. The method of claim 30, wherein the size of the available storage space is the size of the available storage space in a file system portion of the storage space.
33. The method of claim 24, wherein the second set of attributes comprises:
at least one attribute corresponding to a plurality of classes required to support execution of the application.
34. The method of claim 24, wherein the second set of attributes comprises:
at least one attribute corresponding to a plurality of libraries required to support execution of the application.
35. The method of claim 24, wherein the second set of attributes comprises:
at least one attribute corresponding to a plurality of third party libraries required to support execution of the application.
36. The method of claim 24, wherein the second set of attributes comprises:
an attribute identified as a size of available storage space required to support execution of the application program.
37. The method of claim 36, wherein the size of the available storage space is the size of the available storage space in a random access memory portion of the storage space.
38. The method of claim 36, wherein the size of the available storage space is the size of the available storage space in a file system portion of the storage space.
39. The method of claim 27, wherein the plurality of classes available in the application runtime environment comprise: a class of locations and localities operable when querying the latitude and longitude of the wireless device.
40. The method of claim 24, wherein at least one of the first set of attributes and the second set of attributes comprises: at least one attribute corresponding to a characteristic of the display device.
41. The method of claim 24, wherein at least one of the first set of attributes and the second set of attributes comprises: at least one attribute corresponding to a network connection characteristic.
42. The method of claim 24, wherein at least one of the first set of attributes and the second set of attributes comprises at least one attribute corresponding to a processor speed characteristic.
43. The method of claim 24, wherein at least one of the first set of attributes and the second set of attributes comprises at least one attribute corresponding to an end user input device characteristic.
44. The method of claim 24, wherein at least one of the first set of attributes and the second set of attributes comprises at least one attribute corresponding to a characteristic related to execution of an application program.
45. The method of claim 24, wherein at least one of the first set of attributes and the second set of attributes comprises a plurality of attributes corresponding to a plurality of characteristics about execution of an application.
46. The method of claim 24, wherein at least one of the first set of attributes and the second set of attributes comprises at least one attribute corresponding to a menu generation characteristic.
HK10101703.4A 2002-12-09 2006-10-11 System and method for handshaking between wireless devices and servers HK1134734A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10/315,800 2002-12-09

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
HK06111142.8A Addition HK1090774A (en) 2002-12-09 2003-12-04 System and method for handshaking between wireless devices and servers

Related Child Applications (1)

Application Number Title Priority Date Filing Date
HK06111142.8A Division HK1090774A (en) 2002-12-09 2003-12-04 System and method for handshaking between wireless devices and servers

Publications (1)

Publication Number Publication Date
HK1134734A true HK1134734A (en) 2010-05-07

Family

ID=

Similar Documents

Publication Publication Date Title
JP5175025B2 (en) System and method for handshaking between a wireless device and a server
US7881745B1 (en) Electronic device network employing provisioning techniques to update firmware and/or software in electronic devices
JP4571675B2 (en) Method and apparatus for carrier customization in a communication system
US7149510B2 (en) Security access manager in middleware
TW200524394A (en) Dynamically distributed portal-based application processing system
JP4336051B2 (en) Wireless communication terminal, calling restriction method and program
WO2009003385A1 (en) Methods, apparatus and systems for updating equipment
AU2003280551A1 (en) Method and network for establishing or cancelling service connection between the wireless local area network and user terminal
JP5161244B2 (en) System and method for sharing common location related information between communication devices
US8312151B2 (en) Communication systems and methods for dynamic and secure simplification of equipment networking
CN101925158A (en) System and method for obtaining number detail
US7174333B2 (en) Data obtaining method and terminals
JP4592694B2 (en) Database synchronization
JP2000184462A (en) Method for performing access to service, server from mobile station and subscriber identification module and terminal at mobile station corresponding to the method
HK1134734A (en) System and method for handshaking between wireless devices and servers
HK1090774A (en) System and method for handshaking between wireless devices and servers
KR20050095058A (en) Method for downloading multimedia contents in the mobile communication terminal