Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F15/00—Digital computers in general; Data processing equipment in general
  • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
  • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
• • 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• • 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/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
  • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
  • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/03—Protecting confidentiality, e.g. by encryption
  • H04W12/033—Protecting confidentiality, e.g. by encryption of the user plane, e.g. user's traffic
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/06—Authentication

Definitions

• the herein described systems and methods relate to a mobile computing technologies, and more importantly, to a mobility device management server that allows for secure, remote mobile computing.
• a computer user may wish to have their financial planning and management data from his/her financial planning and management computing application (e.g. Quicken, Microsoft Money) with them at all times to address any payments that might spring up (e.g. a lapsed bill).
• his/her financial planning and management computing application e.g. Quicken, Microsoft Money
• the computing user is relegated to install the financial planning and management computing application and data on each of his/her computmg environments (including his/her corporate computer - which may be in violation of corporate computing policies and procedures) so that he/she can have access to this desired data.
• enterprises may wish to effectively and immediately terminate all access to sensitive corporate data from employees who are to be terminated.
• an exemplary mobility device platform comprises a mobility device operable to communicate with at least one computing environment through a communications interface and wherein the mobility device is operable to process and store secure web services, a communications network operable to communicate data and computing applications using web services, and a mobility device management server operable to generate, process, store, communicate and encrypt web services to the mobility device.
• the mobility device management server is operable to perform one or more mobility device management functions to provide encryption keys to cooperating mobility devices and to authenticate and verify cooperating mobility devices requesting web services from the mobility device management server.
• the mobility device management server and mobility device may further operate to perform authentication and verification using user identification and password information.
• the mobility device management server further may operate to perform metering functions and operations on web services being processed and executed on the mobility device platform. Furthermore, the mobility device management server may operate to support intermittent connections between itself and cooperating mobility devices.
• the exemplary mobility device is configured for use on a cooperating computing environment. Further the mobility device establishes communications with cooperating one or more mobility device management servers and attempts to be authenticated and verified by the cooperating one or more mobility device management servers using selected authentication and verification information. Upon authentication and verification, the cooperating one or more mobility device management servers process requests for data and computing applications from the cooperating exemplary mobility device using web services. The web services are encrypted by the cooperating one more mobility device management servers using the exemplary selected authentication and verification information (e.g. keys) to allow secure communications of requested data and computmg applications from the cooperating one more mobility device management servers and the exemplary mobility device. [0010] Other features of the herein described systems and methods are further described below.
• Figure 1 is a block diagram of an exemplary computing environment in accordance with an implementation of the herein described systems and methods
• Figure 2 is a block diagram of an exemplary computing network environment in accordance with the herein described system and methods;
• Figure 3 is a block diagram showing the interaction between exemplary computing components in accordance with the herein described systems and methods;
• FIG. 4 is a block diagram of an illustrative implementation of a mobility device platform in accordance with the herein described systems and methods;
• FIG. 5 is a block diagram of an exemplary architecture of an illustrative mobility device management server in accordance with the herein described systems and methods ;
• FIG. 6 is a flow diagram of the processing performed by an illustrative mobility device management server to handle user and device management in accordance with the herein described systems and methods;
• FIG. 7 is a flow diagram of the processing performed by an illustrative mobility device management server when processing web services requests in accordance with the herein described systems and methods;
• Figure 8 is a flow diagram of the processing performed by an illustrative mobility device management server when translating web services during web services processing in accordance with the herein described systems and methods;
• Figure 9 is a flow diagram of the processing performed by an illustrative mobility device management server when performing metering and intermittent connection processing in accordance with the herein described systems and methods.
• the herein described systems and methods offer a "user-centric" approach to computing and mobile computing.
• Current computmg solutions, enterprise or individual are generally designed using a "device-centric” model.
• the device-centric model aims at managing and tracking users based on device assignments and designations.
• the enterprise computing environment may comprise a number of server computing environments and numerous client computing environments.
• each user in the enterprise is provisioned client computing environment (e.g. personal computer or laptop computer) that is generally networked to the server computing environment through the ente ⁇ rise communications interface or, if the user is remote to the ente ⁇ rise communications network, through a virtual private network (VPN).
• VPN virtual private network
• the users are provided user identification information and password information through a directory services structure that associates user rights and privileges to certain ente ⁇ rise data and computing applications.
• the mobility device may cooperate with one or more computing environments invoking one or more work spaces to process web services.
• the web services may be executed from data and computing applications local to the MD, or the MD may cooperate with one or more MDMS to obtain the desired web service.
• the MDMS may operate to authenticate requesting MDs to ensure that they have the rights and privileges to the requested web services. Additionally, the MDMS may cooperate with third party web service providers to obtain requested web services. In such context, the MDMS may act to translate the web service from a non-MD native web service format to a native MD web service.
• the MDMS and MD engage in 1028 bit and/or 2056 bit encryption (e.g.
• the web services provided by the MDMS to the MD may include but are not limited to computing applications and desired data. Additionally, the MD may operate to store the participating user's customized settings and preferences local to the MD so they are available to the user at all times.
• XML XML Language
• Client applications use web services at another site, often referred to as the client side, by first inte ⁇ reting one or more WSDL documents. Once inte ⁇ reted, the clients can understand the characteristics of the associated service(s). For example, service characteristics may include service API specifications such as (a) input data type, (b) service input data format,
• Client applications prepare their data in manners in which various particular web services understand.
• Client applications invoke a particular service according to the manner specified for the service, such as in an associated WSDL document.
• the herein described system and methods aim to ameliorate such disparity by offering a mobility device platform having a mobile device management server which includes, among other things, a web services translation module operative to accept data from web services web services providers and present them in a web service model native to cooperating mobility devices.
• a mobile device management server which includes, among other things, a web services translation module operative to accept data from web services web services providers and present them in a web service model native to cooperating mobility devices.
• SOAP Simple Object Access Protocol
• SOAP Simple Object Access Protocol
• RPC Remote Procedure Call style
• a SOAP message consists of a SOAP envelope that encloses two data structures, the SOAP header and the SOAP body, and information about the name spaces used to define them.
• the header is optional; when present, it conveys information about the request defined in the SOAP body. For example, it might contain transactional, security, contextual, or user profile information.
• the body contains a Web Service request or reply to a request in XML format.
• the high-level structure of a SOAP message is shown in the following figure.
• WSDL can define the SOAP message used to access the Web Services, the protocols over which such SOAP messages can be exchanged, and the Internet locations where these Web Services can be accessed.
• the WSDL descriptors can reside in UDDI or other directory services, and they can also be provided via configuration or other means such as in the body of SOAP request replies.
• the SOAP client sends the document to a SOAP server, and the SOAP servlet running on the server handles the document using, for example, HTTP or HTTPS.
• the Web service receives the SOAP message, and dispatches the message as a service invocation to the application providing the requested service. [0047] A response from the service is returned to the SOAP server, again using the SOAP protocol, and this message is returned to the originating SOAP client.
• SOAP is described herein as a communication protocol for the herein described systems and methods that such description is merely illustrative as the herein described systems and methods may employ various communication protocols and messaging standards.
• FIG. 1 depicts an exemplary computing system 100 in accordance with herein described system and methods.
• Computing system 100 is capable of executing a variety of operating systems 180 and computing applications 180' (e.g. web browser and mobile desktop environment) operable on operating system 180.
• Exemplary computing system 100 is controlled primarily by computer readable instructions, which may be in the form of software, where and how such software is stored or accessed. Such software may be executed within central processing unit (CPU) 110 to cause data processing system 100 to do work.
• CPU central processing unit
• central processing unit 110 is implemented by micro-electronic chips CPUs called microprocessors.
• Coprocessor 115 is an optional processor, distinct from main CPU 110, that performs additional functions or assists CPU 110.
• CPU 110 may be connected to co-processor 1 15 through interconnect 112.
• coprocessor One common type of coprocessor is the floating-point coprocessor, also called a numeric or math coprocessor, which is designed to perform numeric calculations faster and better than general- pu ⁇ ose CPU 110.
• computing environment 100 may comprise a number of CPUs 110. Additionally computing environment 100 may exploit the resources of remote CPUs (not shown) through communications network 160 or some other data communications means (not shown).
• CPU 110 fetches, decodes, and executes instructions, and transfers information to and from other resources via the computer's main data-transfer path, system bus 105.
• system bus 105 Such a system bus connects the components in computing system 100 and defines the medium for data exchange.
• System bus 105 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus.
• An example of such a system bus is the PCI (Peripheral Component Interconnect) bus.
• PCI Peripheral Component Interconnect
• Some of today's advanced busses provide a function called bus arbitration that regulates access to the bus by extension cards, controllers, and CPU 110. Devices that attach to these busses and arbitrate to take over the bus are called bus masters.
• Bus master support also allows multiprocessor configurations of the busses to be created by the addition of bus master adapters containing a processor and its support chips.
• Memory devices coupled to system bus 105 include random access memory (RAM) 125 and read only memory (ROM) 130. Such memories include circuitry that allows information to be stored and retrieved. ROMs 130 generally contain stored data that cannot be modified. Data stored in RAM 125 can be read or changed by CPU 110 or other hardware devices. Access to RAM 125 and/or ROM 130 may be controlled by memory controller 120. Memory controller 120 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 120 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes.
• computing system 100 may contain peripherals controller 135 responsible for communicating instructions from CPU 110 to peripherals, such as, printer 140, keyboard 145, mouse 150, and data storage drive 155.
• peripherals controller 135 responsible for communicating instructions from CPU 110 to peripherals, such as, printer 140, keyboard 145, mouse 150, and data storage drive 155.
• Display 165 which is controlled by display controller 163, is used to display visual output generated by computing system 100. Such visual output may include text, graphics, animated graphics, and video. Display 165 may be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, a touch-panel, or other display forms. Display controller 163 includes electronic components required to generate a video signal that is sent to display 165.
• computing system 100 may contain network adaptor 170 which may be used to connect computing system 100 to an external communication network 160.
• Communications network 160 may provide computer users with means of communicating and transferring software and information electronically. Additionally, communications network 160 may provide distributed processing, which involves several computers and the sharing of workloads or cooperative efforts in performing a task. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the . computers may be used.
• exemplary computer system 100 is merely illustrative of a computing environment in which the herein described systems and methods may operate and does not limit the implementation of the herein described systems and methods in computing environments having differing components and configurations as the inventive concepts described herein may be implemented in various computing environments having various components and configurations.
• Computing system 100 can be deployed as part of a computer network.
• the above description for computing environments applies to both server computers and client computers deployed in a network environment.
• Figure 2 illustrates an exemplary illustrative networked computmg environment 200, with a server in communication with client computers via a communications network, in which the herein described systems and methods may be employed.
• server 205 may be interconnected via a communications network 160 (which may be either of, or a combination of a fixed-wire or wireless LAN, WAN, intranet, extranet, peer-to-peer network, the Internet, or other communications network) with a number of client computing environments such as tablet personal computer 210, mobile telephone 215, telephone 220, personal computer 100, and personal digital assistance 225. Additionally, the herein described systems and methods may cooperate with automotive computing environments (not shown), consumer electronic computing environments (not shown), and building automated control computing environments (not shown) via communications network 160.
• a communications network 160 which may be either of, or a combination of a fixed-wire or wireless LAN, WAN, intranet, extranet, peer-to-peer network, the Internet, or other communications network
• client computing environments such as tablet personal computer 210, mobile telephone 215, telephone 220, personal computer 100, and personal digital assistance 225.
• client computing environments such as tablet personal computer 210, mobile telephone 215, telephone 220, personal computer 100, and personal digital assistance 225.
• server 205 can be dedicated computing environment servers operable to process and communicate web services to and from client computing environments 100, 210, 215, 220, and 225 via any of a number of known protocols, such as, hypertext transfer protocol (HTTP), file transfer protocol (FTP), simple object access protocol (SOAP), or wireless application protocol (WAP).
• HTTP hypertext transfer protocol
• FTP file transfer protocol
• SOAP simple object access protocol
• WAP wireless application protocol
• Each client computing environmet 100, 210, 215, 220, and 225 can be equipped with browser operating system 180 operable to support one or more computmg applications such as a web browser (not shown), or a mobile desktop environment (not shown) to gain access to server computing environment 205.
• a user may interact with a computing application running on a client computing environments to obtain desired data and/or computing applications.
• the data and/or computing applications may be stored on server computing environment 205 and communicated to cooperating users through client computing environments 100, 210, 215, 220, and 225, over exemplary communications network 160.
• a participating user may request access to specific data and applications housed in whole or in part on server computing environment 205 using web services transactions. These web services transactions may be communicated between client computing environments 100, 210, 215, 220, and 220 and server computing environments for processing and storage.
• the systems and methods described herein can be utilized in a computer network environment having client computmg environments for accessing and interacting with the network and a server computing environment for interacting with client computing environments.
• the systems and methods providing the mobility device platform can be implemented with a variety of network-based architectures, and thus should not be limited to the example shown.
• the herein described systems and methods will now be described in more detail with reference to a presently illustrative implementation.
• FIG. 3 shows an exemplary interaction between the components of an exemplary mobility device platform.
• exemplary mobility device platform 300 in simple terms, may comprise mobility device 310 cooperating with client computing environment 100 using communications interface 305 operating on a selected communications protocol (not shown). Additionally, exemplary mobility device platform 300 may further comprise communications network 160 (of Figure 1) and server computing environment 205.
• mobility device may cooperate with client computing environment 100 through communications interface 305 to execute one or more computing applications 180' originating from mobility device 310 and displayable for user interaction on client computing environment 100.
• Computing applications 180' may include but are not limited to, a browser application offering the look and feel of conventional operating systems, word processing applications, spreadsheets, database applications, web services applications, and user management/preference applications.
• mobility device 310 may cooperate with server computmg environment 205 via communications network 160 using client computing environment 100 to obtain data and/or computing applications in the form of web services.
• Figure 4 shows the interaction of components for exemplary mobility device platform 400.
• exemplary mobility device platform 400 comprises mobility device (MD) 405, computing environment 410, communications network 435, mobility device management server (MDMS) 420 and third party web service providers 440.
• MD 405 further comprises processing unit (PU), • operating system (OS), storage memory (RAM/ROM), and an MD communications interface.
• MDMS 420 further comprises translation engine 425, web services 430, and encryption engine 445.
• MD 405 communicates with computing environment 415 using one or more of MD components PU, OS, RAM/ROM and MD communications interface through MD/computing environment communications interface 410.
• MD 405 may launch one or more computing applications (not shown) that may include but are not limited to, a mobile desktop environment, user customization and authentication manager, and web services applications as part of configuration.
• computing applications may include but are not limited to, a mobile desktop environment, user customization and authentication manager, and web services applications as part of configuration.
• MD 405 may further cooperate with computmg environment 415 to process one or more web services (e.g. web service data and/or computing applications).
• MD 405 may also request web services data and/or computing applications from cooperating MDMS 420 using communications network 435 to process such web services.
• MDMS 420 may operate to authenticate MD 405 to ensure that the participating user (not shown) and mobility device 405 have the correct privileges to the requested data and/or computing applications.
• MDMS 420 may further operate to locate the requested data and/or computing applications locally at MDMS 420 and provide such requested data and/or computing applications (e.g. web services) to the authenticate MD 405 over communications network 435, or operate to cooperate with third party services providers 440 to obtain the requested web services for communication to the authenticated MD 405.
• MDMS 420 may operate to translate the web services 430 originating from third party web services providers 440 to an MD native format using translation engine 425. Additionally, MDMS 420 may operate to encrypt requested web services using encryption engine 445 when satisfying requests for web services from authenticated MD 405.
• MDMS 420 may further operate to cooperate with a file system (not shown) using a selected encryption protocol (e.g. PKI encryption) to obtain the requested data for communication to MD 405.
• the cooperating file system may include but is not limited to file allocation table (FAT) file systems and new technology files system (NTFS).
• FAT file allocation table
• NTFS new technology files system
• FIG 5 is block diagram showing exemplary components of an illustrative mobility device management server (MDMS) deployed in an illustrative networked computing environment. As is shown, illustrative networked computing environment comprises Site A, Site B, and Site C, respectively, having exemplary MDMSs and components.
• Site A comprises MDMS 502 which itself comprises operating system 504.
• Operating system (OS) 504 is shown to support Java virtual machine (JVM) 506 which, in turn, supports MDMS.java code 508.
• MDMS.java code 508 therein comprises SOAP chaining 538 and services 548.
• Operating system 504 is operative to support and cooperate with user database 510, key database 512, and file storage 514.
• Operating system 504 is operative to support and cooperate with resident applications 550, JVM 552, and JVM 554.
• OS 504 is operative to support and cooperate with encryption drivers, communication interface drivers and network drivers.
• Mirroring OS 504, MDMS 502 maintains hardware such as hardware accelerator, communications interface port, and network interface cards (NICs) that cooperate with the encryption drivers, communications interface drivers, and network drivers during MDMS 502 operation.
• NICs network interface cards
• MDMS comprises storage area network (SAN)/network attached storage (NAS) interface 516 that is operable to connect MDMS 502 to cooperating file/data stores 518 and cooperating MDMSs 520 and 522.
• SAN/NAS interface 516 may be coupled to cooperating file/data storage and MDMSs 520 and 522 through communications network 519.
• MDMS 502 may cooperate with other MDMS environments 536 and 528 that may reside local to or geographically disparate from MDMS 502.
• MDMS environment 536 may comprise MDMS 534 and file/data store 522.
• MDMS environment 528 may comprise MDMS 526 and MDMS 530 operatively coupled to file/data store 524.
• SOAP chaining module 538 there may reside a number of sub-modules that include but are not limited to, a packet sniffer operative to monitor data communications, security enforcement operative to maintain data privileges and access, usage/monitor operative to meter services usage, and a web services proxy operative to cache web services for cooperation with requesting components (e.g. authenticated MD, not shown).
• These sub-modules may be controllable by one or more sub-module applications that may include but are not limited to administration debugger operating on the packet sniffer sub-module, security manager operative on the seucurity/enforcement sub-module, metering manager operative on the usage/monitor sub- module, and proxy manager operative on the web services proxy.
• a number of service may include but are not limited to a mobility device manager, an encryption manager (PKCS manager), a file transfer service, a web services manager, web services access control service, a web services metering service, a universal, description, discovery, and integration directory (UDDI directory) service, a UDDI repository service, a files system (e.g. Omni file system), a SOAP proxy service, a web services translator service, and a quality of service operation that is operative to perform functions including but not limited to load balancing, MDMS hot swapping, and failover.
• Resident apps 550 may include but are not limited to security, router, SAN/NAS control, and encryption control.
• JVM 552 may comprise code to operate on and process encryption information (e.g. key information), user authentication, service allocation, and MDMS Java operations.
• JVM 554 may comprise Java code that allow it to emulate a mobility device hardware configuration.
• MDMS 501 provides secure management of user data, registry of applications and services, and coordination of storage.
• MDMS 501 supports both user access and administrative functions. For example, mobile desktop users may connect to their applications and data through MDMS 501.
• MDMS 501 checks for user authentication and preferences. Access controls may be automatically imposed and "skins" may be applied to applications and services such that they fit in to a participating user's environment. Requests for applications and data may be processed with the speed of local devices and may be monitored for system improvement.
• MDMS 502 is operative to enable users to access file stores (e.g.
• MDMS 502 may employ various MDMS components to provide management of files, applications/services (548 and 550), and mass storage. Moreover, MDMS 502 allows for more robust administration as it provides administrators the ability to connect to MDMS 502 from remote locations using a cooperating mobility device (not shown). [0074] As is illustrated by Figure 5, MDMS 502 may comprise a number of functional components and modules. These components and modules may operate to provide functions including, but not limited to, security, mobility device management, encryption key tracking and management, metering of transactions, file system management, application/service management, application subscriptions management, web services monitoring, legacy infrastructure extension, data storage management, and cluster deployment and management.
• Figure 6 shows the processing performed by exemplary MDMS 502 when cooperating with cooperating MDMS and MDs to process web services. As is shown, processing begins at block 600 and proceeds to block 605 where a check is performed to determine if a cooperating MD authorization needs to be created or updated. If the check at block 605 indicates that the MD authorization does not need to be established or updated, processing reverts to block 600 and continues from there.
• processing proceeds to block 610 where a check is performed to determine if the cooperating MD is new to the MDMS and requires initial authentication by the MDMS. If the check at block 610 indicates that authentication for a new MD is required, processing proceeds to block 615 where the MDMS generates authentication information for the new MDs. From there processing proceeds to block 620 where encryption keys are generated and communicated to the MD(s) being authenticated. The authentication and encryption information is then communicated to the cooperating MD(s) being authenticated at block 625. The MDMS then associates group memberships for the MD(s) on cooperating file system(s) using the authentication and encryption information.
• a check is then performed at block 635 to determine if the authentication was successful. If the check was not deemed successful at check 635, processing proceeds to block 640 where an error is generated. The authentication mistakes may then be rectified at block 645. From there processing reverts back to the input of block 635 and proceeds from there.
• processing proceeds to block 650 where a check is performed to determine if permission changes are required for cooperating MDs. If the check at block 650 indicates that permission changes are required, processing proceeds to block 655 where the authentication and/or encryption information is updated. Form there processing reverts back to the input of block 635 and continues from there.
• Figure 7 shows the processing performed by exemplary mobility device management server 502 in an illustrative implementation of processing web services.
• processing begins at block 700 and proceeds to block 705 where a check is performed to determine if the MDMS has engaged in communications with a cooperating communications network. If the check at block 700 indicates that communications have not been engaged, processing reverts back to block 700 and continues from there. However, if at block 705 it is determined that communications have been engaged by MDMS with a cooperating communications network, processing proceeds to block 710 where a check is performed to determine if one or more cooperating MDs have requested one or more web service from the MDMS. If the check at block 710 indicates that there are no MD requests for web services, processing reverts to the input of block 710 and continues from there.
• Figure 8 shows the processing performed by exemplary mobility device management server 502 in another implementation of web services processing. As is shown in Figure 8, processing begins at block 800 and proceeds to block 805 where a check is performed to determine if one or more authenticated MDs have requested one or more web services. If at block 805 it is determined that there are no requests for web services from authenticated MDs, processing reverts to block 800 and proceeds from there.
• MD operations are metered to obtain usage, behavior, affinity, and similar metrics by MDMS at block 835.
• the meter data is then stored at block 840 for subsequent use.
• a check is then performed at block 845 to determine whether the stored meter data is to be reported. If the check at block 845 indicates that the meter data is to be reported, processing proceeds to block 850 where, the meter data is analyzed to generate meter reports. Processing then terminates at block 855.
• the check at block 815 indicates that translation is required, processing proceeds to block 820 where the requested web services is translated into an MD native web service. From there, processing proceeds to block 825 and continue from there.
• Figure 9 shows the processing performed by exemplary MDMS 502 in another implementation of web services processing.
• processing begins at block 900 and proceeds to block 905 where a check is performed to determine if one or more authenticated MDs have requested one or more web services. If at block 905 it is determined that there are no requests for web services from authenticated MDs, processing reverts to block 900 and proceeds from there. However, if at block 905 it is determined that there are requests for web services from one or more authenticated MDs, processing proceeds to block 910 where the MDMS retrieves data and/or computing applications from any of a cooperating file store, cooperating web services providers and other cooperating MDMS. From there a check is performed at block 915 to determine if the retrieved web service requires translation into an MD native web service format.
• processing proceeds to block 940 where the requested web services are cached . From there processing proceeds to the input of block 935 and continues there from. Also, if the check at block 915 indicates that translation is required, processing proceeds to block 920 where the requested web services is translated into an MD native web service. From there, processing proceeds to block 925 and continue from there.
• the herein described systems and methods provide a mobility device management server for use as part of a mobility device platform. It is understood, however, that the invention is susceptible to various modifications and alternative constructions. There is no intention to limit the invention to the specific constructions described herein. On the contrary, the invention is intended to cover all modifications, alternative constructions, and equivalents falling within the scope and spirit of the invention.
• the present invention may be implemented in a variety of computer environments (including both non-wireless and wireless computer environments), partial computing environments, and real world environments.
• the various techniques described herein may be implemented in hardware or software, or a combination of both.
• the techniques are implemented in computing environments maintaining programmable computers that include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device.
• Computing hardware logic cooperating with various instructions sets are applied to data to perform the functions described above and to generate output information.
• the output information is applied to one or more output devices.
• Programs used by the exemplary computing hardware may be preferably implemented in various programming languages, including high level procedural or object oriented programming language to communicate with a computer system.
• the herein described apparatus and methods may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or inte ⁇ reted language.
• Each such computer program is preferably stored on a storage medium or device (e.g., ROM or magnetic disk) that is readable by a general or special pu ⁇ ose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to perform the procedures described above.
• the apparatus may also be considered to be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Security & Cryptography (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• Computer Hardware Design (AREA)
• General Engineering & Computer Science (AREA)
• Computing Systems (AREA)
• Theoretical Computer Science (AREA)
• Software Systems (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Information Transfer Between Computers (AREA)
• Mobile Radio Communication Systems (AREA)
• Telephonic Communication Services (AREA)

Priority Applications (1)

Applications Claiming Priority (16)

Publications (2)

Family

ID=34437818

Family Applications (3)

Family Applications After (2)

Country Status (3)

Families Citing this family (30)

Family Cites Families (61)

• 2004
  • 2004-04-30 WO PCT/US2004/013504 patent/WO2005036304A2/en not_active Ceased
  • 2004-04-30 WO PCT/US2004/013503 patent/WO2005036411A1/en not_active Ceased
  • 2004-04-30 JP JP2006527962A patent/JP2007519066A/ja active Pending
  • 2004-04-30 JP JP2006527961A patent/JP2007509382A/ja active Pending
  • 2004-04-30 WO PCT/US2004/013505 patent/WO2005036305A2/en not_active Ceased
  • 2004-04-30 JP JP2006527963A patent/JP2007507768A/ja active Pending
• 2008
  • 2008-10-16 US US12/253,067 patent/US20090044259A1/en not_active Abandoned
• 2012
  • 2012-12-20 US US13/722,720 patent/US20130124695A1/en not_active Abandoned

Also Published As

Similar Documents

Legal Events